Tech-invite  3GPPspace  IETFspace
◀  ▶  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
Top   in Index   Prev   Next

TS 28.312
Management and Orchestration –
Intent driven Management services for Mobile Networks

3GPP‑Page   ETSI‑search   fToC↓   Partial Content →
V19.4.0 (PDF)  2025/12  … p.
V18.8.0  2025/06  101 p.
V17.8.0  2024/12  59 p.
Rapporteur:
Mr. Xu, Ruiyue
Huawei Tech.(UK) Co.. Ltd

full Table of Contents for  TS 28.312  Word version:  19.3.0

each clause number in 'red' refers to the equivalent title in the Partial Content
Here   Top
0Introduction  p. 9
1Scope  p. 10
2References  p. 10
3Definitions of terms, symbols and abbreviations  p. 11
3.1Terms  p. 11
3.2Symbols  p. 11
3.3Abbreviations  p. 11
4Concepts and Background  p. 11
4.1Intent concept  p. 11
4.1.1Introduction  p. 11
4.1.2Intent categorizes based on user types  p. 12
4.1.3Intent expectations for different types of management needs  p. 13
4.2Intent driven management  p. 13
4.2.1Support for intent driven management  p. 13
4.2.2Intent driven MnS  p. 14
4.2.3Intent translation  p. 15
4.3Intent driven closed-loop  p. 15
4.4Relation between rule, policy and intent  p. 16
4.5General concept of Intent Content  p. 16
4.5.1Intent Expectation  p. 16
4.5.2Expectation Targets  p. 17
4.5.3Expectation Objects  p. 17
4.5.4Context  p. 18
4.6Intent negotiation functionalities |R19|  p. 18
4.6.1Overview  p. 18
4.6.2Intent negotiation functionalities in Intent pre-evaluation phase  p. 18
4.6.3Intent negotiation functionalities in Intent fulfilment phase  p. 19
4.7Intent handling state management |R19|  p. 19
5Specification Level Requirements  p. 20
5.1Use cases  p. 20
5.1.1Intent containing an expectation for delivering radio network  p. 20
5.1.1.1Introduction  p. 20
5.1.1.2Requirements  p. 21
5.1.2Intent containing an expectation for delivering a radio service  p. 21
5.1.2.1Introduction  p. 21
5.1.2.2Requirements  p. 21
5.1.3Intent containing an expectation for delivering a service at the edge.  p. 21
5.1.3.1Introduction  p. 21
5.1.3.2Requirements  p. 22
5.1.4Intent containing an expectation on coverage performance to be assured  p. 22
5.1.4.1Introduction  p. 22
5.1.4.2Requirements  p. 22
5.1.5Intent containing an expectation on radio network performance to be assured  p. 22
5.1.5.1Introduction  p. 22
5.1.5.2Requirements  p. 23
5.1.6Intent containing an expectation for end-to-end network optimization |R18|  p. 24
5.1.6.1Introduction  p. 24
5.1.6.2Requirements  p. 24
5.1.7Intent containing an expectation for RAN energy saving |R18|  p. 24
5.1.7.1Introduction  p. 24
5.1.7.2Requirements  p. 25
5.1.8Intent containing an expectation for 5GC network |R18|  p. 25
5.1.8.1Introduction  p. 25
5.1.8.2Requirements  p. 26
5.2Generic requirements for intent driven MnS  p. 26
5.3Generic use case for intent driven management |R18|  p. 27
5.3.1Intent handling capability obtaining  p. 27
5.3.1.1Introduction  p. 27
5.3.1.1.1Information on supported expectation object and corresponding expectationTargets. |R19|  p. 27
5.3.1.1.2Description of supported expectation targets |R19|  p. 27
5.3.1.1.3Describing alternative expectations |R19|  p. 28
5.3.1.2Requirements  p. 29
5.3.2Intent report  p. 29
5.3.2.1Introduction  p. 29
5.3.2.2Requirements  p. 31
5.3.3Intent fulfilment feasibility check  p. 32
5.3.3.1Introduction  p. 32
5.3.3.2Requirements  p. 33
5.3.4Intent-related conflicts  p. 33
5.3.4.1Introduction  p. 33
5.3.4.2Detecting Intent-related conflicts  p. 33
5.3.4.3Resolving Intent-related conflicts  p. 33
5.3.4.4Requirements  p. 34
5.3.5Intent Exploration |R19|  p. 34
5.3.5.1Introduction  p. 34
5.3.5.2Requirements  p. 35
5.3.6Intent degradation based on expectation preference |R19|  p. 35
5.3.6.1Introduction  p. 35
5.3.6.2Requirements  p. 35
5.3.7Enablers for Intent Fulfilment |R19|  p. 35
5.3.7.1Introduction  p. 35
5.3.7.2Requirements  p. 36
5.3.8Intent Utility Function |R19|  p. 36
5.3.8.1Introduction  p. 36
5.3.8.2Definition  p. 36
5.3.8.3Requirements  p. 38
5.3.9Negotiation on fulfilment of intents |R19|  p. 38
5.3.9.1Introduction  p. 38
5.3.9.2Checking for fulfillable outcomes  p. 39
5.3.9.3Checking for best possible outcome on an intent, intent expectation, or expectation target  p. 39
5.3.9.4MnS producer to provide information about possible fulfilment of the intent  p. 40
5.3.9.5MnS consumer advises on preferred alternatives  p. 40
5.3.9.6Requirements  p. 41
6Stage 2 definition for Intent Driven Management  p. 43
6.1Management operation for intent driven management (MnS component type A)  p. 43
6.2Information model definition for Intent (MnS component typeB)  p. 44
6.2.1Generic Information model definition  p. 44
6.2.1.0Imported information entities and local labels |R18|  p. 44
6.2.1.1Class diagram  p. 44
6.2.1.1.1Relationship  p. 44
6.2.1.1.2Inheritance  p. 45
6.2.1.2Class definition  p. 46
6.2.1.2.1Intent <<InformationObjectClass>>  p. 46
6.2.1.2.2IntentReport <<InformationObjectClass> |R18|  p. 47
6.2.1.2.3IntentHandlingFunction <<InformationObjectClass>> |R18|  p. 49
6.2.1.2.4IntentUtilityFormula <<InformationObjectClass>> |R19|  p. 49
6.2.1.3DataType definition  p. 50
6.2.1.3.1IntentExpectation <<dataType>>  p. 50
6.2.1.3.2ExpectationObject <<dataType>>  p. 51
6.2.1.3.3ExpectationTarget <<dataType>>  p. 51
6.2.1.3.4Context <<dataType>>  p. 52
6.2.1.3.5FulfilmentInfo << dataType >>  p. 52
6.2.1.3.6IntentFulfilmentReport <<dataType>> |R18|  p. 54
6.2.1.3.7ExpectationFulfilmentResult <<dataType>> |R18|  p. 54
6.2.1.3.8TargetFulfilmentResult<<dataType>> |R18|  p. 54
6.2.1.3.9IntentConflictReport << dataType >> |R18|  p. 55
6.2.1.3.10IntentFeasibilityCheckReport <<dataType>> |R18|  p. 56
6.2.1.3.11IntentHandlingCapability <<dataType>> |R18|  p. 56
6.2.1.3.12ValueRangeType<<choice>> |R18|  p. 57
6.2.1.3.13Frequency<<dataType>> |R18|  p. 57
6.2.1.3.14UEGroup <<dataType>> |R18|  p. 58
6.2.1.3.15InFeasibleExpectationInfo <<dataType>> |R19|  p. 58
6.2.1.3.16IntentReportControl <<dataType>> |R19|  p. 59
6.2.1.3.17ReportingConditions <<Choice>> |R19|  p. 60
6.2.1.3.18TargetFulfilmentCondition <<dataType>> |R19|  p. 60
6.2.1.3.19IntentExplorationReport <<dataType>> |R19|  p. 60
6.2.1.3.20ExpectationExplorationResult <<dataType>> |R19|  p. 61
6.2.1.3.21ImplicitIntent <<dataType>> |R19|  p. 61
6.2.1.3.22IntentFulfilmentNegotiationReport <<dataType>> |R19|  p. 62
6.2.1.3.23PossibleIntentOutcome <<dataType>> |R19|  p. 63
6.2.1.3.24IntentFulfilmentNegotiationFeedback <<dataType>> |R19|  p. 63
6.2.1.3.25PossibleImpact <<dataType>> |R19|  p. 64
6.2.1.3.26SupportedExpectationTargetInfo <<dataType>> |R19|  p. 64
6.2.1.3.27UtilityParameter <<dataType>> |R19|  p. 65
6.2.1.3.28UtilityResult <<dataType>> |R19|  p. 66
6.2.1.3.29UtilityDefinition <<dataType>> |R19|  p. 66
6.2.1.3.30IntentUtilityReport <<dataType>> |R19|  p. 66
6.2.1.4Attribute definition  p. 67
6.2.1.5Common notifications  p. 81
6.2.1.5.1Configuration notifications  p. 81
6.2.2Scenario specific IntentExpectation definition  p. 81
6.2.2.1Scenario specific IntentExpectation definition  p. 81
6.2.2.1.1Radio Network Expectation  p. 81
6.2.2.1.2Edge Service Support Expectation  p. 83
6.2.2.1.3End-to-end Network Resource Optimization Expectation |R18|  p. 84
6.2.2.1.45GC Network Expectation |R18|  p. 85
6.2.2.1.5Radio Service Expectation |R18|  p. 86
6.2.2.2Attribute definition  p. 89
6.3Procedures for intent management  p. 101
6.3.1Introduction  p. 101
6.3.2Create an intent  p. 101
6.3.2aIntent feasibility check before intent fulfilment |R19|  p. 103
6.3.3Modify an intent  p. 104
6.3.4Delete an intent  p. 105
6.3.5Query an intent  p. 105
6.3.6Intent conflict resolution |R18|  p. 106
6.3.6.0Procedure  p. 106
6.3.6.1Resolution of an intent conflict based on pre-emption  p. 106
6.3.7Intent Report Management |R18|  p. 107
6.3.7.1Overview of Intent Report Management  p. 107
6.3.8Intent exploration |R19|  p. 107
6.3.9Intent negotiation during fulfilment phase |R19|  p. 108
7Stage 3 definition for Intent Driven Management  p. 110
7.1RESTful HTTP-based solution set  p. 110
7.2OpenAPI specification  p. 112
7.2.1OpenAPI document for provisioning MnS  p. 112
7.2.2OpenAPI document for intent NRM  p. 112
7.2.3OpenAPI document for scenario specific IntentExpectation  p. 112
8Guidelines for using scenario specific intent expectation for intent driven use cases  p. 113
APlantUML source code  p. 117
A.1Procedures for intent management  p. 117
A.1.1Create an intent  p. 117
A.1.2Modify an intent  p. 117
A.1.3Delete an intent  p. 118
A.1.4Query an intent  p. 118
A.1.5Intent Report Management |R18|  p. 118
A.1.5.1Intent report management  p. 118
A.1.5.2Query an intent report  p. 118
A.1.5.3Intent report subscription and notification  p. 119
A.1.6Intent Handling Capability Obtaining |R18|  p. 119
A.1.6.1Query intent handling capability suported by an intentHandlingFunction  p. 119
A.1.7Intent conflict resolution |R18|  p. 119
A.1.8Intent feasibility check before intent fulfilment |R19|  p. 120
A.1.9Intent exploration |R19|  p. 120
A.1.10Intent inegotiation during fulfilment phase |R19|  p. 120
A.2Information model definition for intent  p. 121
A.2.1Relationship UML diagram for intent (figure 6.2.1.1.1-1)  p. 121
A.2.2Relationship UML diagram for intent (figure 6.2.1.1.1-2) |R18|  p. 121
A.2.3Relationship UML diagram for intentReport IOC (figure 6.2.1.1.1-3) |R18|  p. 122
A.2.4Relationship UML diagram for Inheritance UML diagram for intent driven management (figure 6.2.1.1.2-1) |R18|  p. 122
A.3UML |R19|  p. 123
BIntent Life Cycle Management  p. 125
B.1Intent Life Cycle Management  p. 125
CMapping the 3GPP and the TM Forum intent expectation and intent report Models  p. 127
DYAML document examples for scenario specific intent instance |R18|  p. 128
D.0Introduce  p. 128
D.1YAML document example for Intent containing an expectation for delivering radio network  p. 128
D.2YAML document example for Intent containing an expectation for delivering a service  p. 129
D.3YAML document example for Intent containing an expectation on coverage performance to be assured  p. 130
D.4YAML document example for Intent containing an expectation on RAN UE throughput performance to be assured  p. 130
D.5YAML document example for Intent containing an expectation on RAN energy saving  p. 131
D.6YAML document example for Intent containing an expectation on radio network capacity performance to be assured  p. 132
D.7YAML document example for Intent containing an expectation for delivering 5GC network  p. 133
D.8YAML document example for Intent report instance  p. 134
D.9YAML document example for Intent containing an expectation for delivering radio service  p. 135
D.10YAML document example for Intent containing an expectation on radio network traffic assurance |R19|  p. 135
D.11YAML document example for Intent containing an expectation for network maintenance |R19|  p. 136
D.12YAML document examples for intent and intent report instance for intent feasibility check |R19|  p. 137
D.13YAML document examples for intent and intent report instance for intent exploration |R19|  p. 138
D.14YAML document examples for IntentHandlingCapability |R19|  p. 138
EIntent management procedures |R18|  p. 140
E.1Basic intent report management  p. 140
E.1.1Query an intent report  p. 140
E.1.2Intent report subscription and notification  p. 140
E.2Intent Handling Capability obtaining  p. 142
E.2.1Query intent handling capability provided by an intentHandlingFunction  p. 142
FPotential deployment scenarios for intent interface |R18|  p. 143
F.1Description  p. 143
F.2Potential deployment scenario#1  p. 143
F.3Potential deployment scenario#2  p. 143
GGuidelines for using Intent generic information model to support new scenario which is not standardized |R19|  p. 145
HExample Utility Function Usage |R19|  p. 146
H.1Overview  p. 146
H.2Producer capabilities exposure  p. 146
H.3Consumer utility function usage  p. 146
H.4Producer utility function usage  p. 147
H.5Consumer utility function result report  p. 147
$Change history  p. 148

Up   Top