ETSI GS ENI 033 V4.1.1 (2024-08)

Experiential Networked Intelligence (ENI); Definition, Requirements and Procedure of Intent Policy Multi-Stage Translating

DGS/ENI-0033v411_MSTranslating

General Information

• Status: Not Published
• Technical Committee: ENI - Experiential Networked Intelligence
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Due Date: 10-Sep-2024
• Completion Date: 27-Aug-2024

Standards Content (Sample)

GROUP SPECIFICATION
Experiential Networked Intelligence (ENI);
Definition, Requirements and Procedure of
Intent Policy Multi-Stage Translating
Disclaimer
The present document has been produced and approved by the Experiential Networked Intelligence (ENI) ETSI Industry
Specification Group (ISG) and represents the views of those members who participated in this ISG.
It does not necessarily represent the views of the entire ETSI membership.

2 ETSI GS ENI 033 V4.1.1 (2024-08)

Reference
DGS/ENI-0033v411_MSTranslating
Keywords
intent management, policy management
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.
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 2024.
All rights reserved.
ETSI
3 ETSI GS ENI 033 V4.1.1 (2024-08)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
Executive summary . 4
Introduction . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definition of terms, symbols and abbreviations . 6
3.1 Terms . 6
3.2 Symbols . 6
3.3 Abbreviations . 6
4 Overview of Intent Policy Multi-Stage Processing . 7
4.1 Introduction . 7
4.2 Description of Intent Policy Multi-Stage Processing . 7
4.2.1 Background . 7
4.2.2 High-Level Description of Intent Policy Multi-Stage Processing. 7
4.3 Functional Architecture . 8
4.4 Procedures of Intent Policy Multi-Stage Processing . 11
4.4.1 Generate Intent-Level templates . 11
4.4.1.1 Overview . 11
4.4.1.2 The Sequence Generation Method . 11
4.4.1.3 Operation Process . 12
4.4.2 Generation of Service-Level Templates . 12
4.4.2.1 Overview . 12
4.4.2.2 Operation Process . 12
4.4.3 Generation of User-Level Templates . 13
4.4.3.1 Overview . 13
4.4.3.2 Operation Process . 13
4.4.3.3 Benefit . 14
4.4.4 Generation of Network Polices . 14
5 Intent Policy Multi-Stage Processing Design Requirements . 15
5.1 Introduction . 15
5.2 Functional Requirements for Intent Policy Multi-Stage Processing . 15
5.3 Non-Functional Requirements for Intent Policy Multi-Stage Processing . 15
6 Use Cases . 16
6.1 Use Case: User intent to the network polices . 16
6.1.1 Use case context . 16
6.1.2 Description of the use case . 16
6.1.2.1 Overview . 16
6.1.2.2 Motivation . 16
6.1.2.3 Actors and Roles . 17
6.1.2.4 Initial context configuration . 17
6.1.2.5 Pre-conditions . 17
6.1.2.6 Trigger conditions . 17
6.1.2.7 Operational Flow of the Actions . 17
6.1.2.8 Post-conditions . 18
7 Summary and Next Steps . 18
7.1 Open Issues for the present document . 18
7.2 Issues for Future Study . 18
History . 19

ETSI
4 ETSI GS ENI 033 V4.1.1 (2024-08)
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.
Foreword
This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Experiential Networked
Intelligence (ENI).
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.
Executive summary
The present document specifies a high-level functional abstraction of the process of intent policy Multi-Stage
translating in ENI system in terms of Functional Modules, Internal Reference Points and working pipelines.
Introduction
The present document defines a high-level functional abstraction of Intent Policy Multi-Stage Processing. The
organization of the present document is as follows. Clause 1 defines the scope of the present document. Clauses 2 and 3
provide normative and informative references and definition of terms, respectively. Clause 4 provides an informative
overview of Intent Policy Multi-Stage Translating, including its motivation, benefits, important concepts and an
overview of its Functional Modules. Clause 5 defines important design principles of the processing. Clause 6 provides
some use cases of Intent Policy Multi-Stage Processing. Clause 7 gives away some potential future works on the present
document.
ETSI
5 ETSI GS ENI 033 V4.1.1 (2024-08)
1 Scope
The present document augments existing intent policy translating procedure in ENI. The purpose of the present
document is to describe intent policy multi-stage translating in ENI system, and to enhance intent policy multi-stage
translating.
The present document also defines the output(s), input(s), internal process and interaction of every stage during intent
policy multi-stage translating.
Intent policy multi-stage translating is a detailed procedure that can translate an intent policy according to the Policy
Continuum. There is an external knowledge base to be added to provide a set of multi-stage general processing scheme
for intent policy.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI GS ENI 005 (V3.1.1): "Experiential Networked Intelligence (ENI); System Architecture".
[2] ETSI GS ENI 030 (V4.1.1): "Experiential Networked Intelligence (ENI); Transformer
Architecture for Policy Translation".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI GS ENI 019 (V3.1.1): "Experiential Networked Intelligence (ENI); Representing, Inferring,
and Proving Knowledge in ENI".
ETSI
6 ETSI GS ENI 033 V4.1.1 (2024-08)
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
AI model (in the present document): model that is capable of processing the understanding and generation of natural
language
business intent: abstract network intent input by the user
intent-level entity: specific noun element in an intent-level template that represents a network attribute
intent-level template: network intent with fixed format
knowledge base: unified repository encompassing diverse structural resources including knowledge graphs for linking
data contexts and text documents
knowledge graph: data organization model leveraging graph theory and logical frameworks to depict the
interconnectedness and logical associations within information, realized through a graphical structure for coherent
knowledge storage and handling
named entity: word or phrase that refers to an item or process of interest
named entity recognition: information extraction task focused on identifying specific, named elements within text data
network entity: group of network information combination, such as [time and bandwidth], [start time, end time and
packet loss], etc.
network policy: Domain Specific Language (DSL) generated from a user-level template
on-demand service: service that is provisioned and used as needed
part-of-speech tagging: natural language processing technique used to determine the grammatical category of each
word in a sentence, such as nouns, verbs, adjectives, etc.
service-level template: template incorporating Quality of Service, Access Control List, Service-Level Agreements, and
Network Function Virtualisation, etc.
user-level template: service-level template that incorporates user preferences, device information, etc.
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACL Access Control List
AI Artificial Intelligence
CRF Conditional Random Fields
DSL Domain Specific Language
HMM Hidden Markov Model
NER Named Entity Recognition
NFV Network Functions Virtualisation
NLP Natural Language Processing
QoE Quality of Experience
QoS Quality of Service
RNN Recurrent Neural Network
SLA Service Level Agreement
ETSI
7 ETSI GS ENI 033 V4.1.1 (2024-08)
VNF Virtual Network Function
4 Overview of Intent Policy Multi-Stage Processing
4.1 Introduction
This clause provides an informative introduction to Intent Policy Multi-Stage Processing in the ENI Policy Management
Functional Block of ETSI GS ENI 005 [1]. Clause 4.2 describes the background and motivation of Intent Policy
Multi-Stage Processing, and then provides a high-level description of Intent Policy Multi-Stage Processing in the
ENI system. Clause 4.3 describes the functional architecture of Intent Policy Multi-Stage Processing in terms of
Processing Stages. Clause 4.4 introduces each step of Intent Policy Multi-Stage Processing.
4.2 Description of Intent Policy Multi-Stage Processing
4.2.1 Background
With the development of the research of the sixth-generation wireless communication network (6G), the network
business scenarios are increasingly diversified. This evolution is significantly propelled by the synergistic integration of
artificial intelligence with communication technology, which serves as a pivotal pillar supporting the emergence of
novel service paradigms and further driving the development of the network.
The key challenge of current 6G research is to achieve on-demand services in all scenarios. This "on demand" concept
is fundamentally different from the traditional service provisioning model, where services are pre-established and are
typically locked in for a fixed duration. On-demand service refers to the way of providing customized network services
to meet different needs by efficiently allocating network resources across multiple domains according to the specific
characteristics and needs of network scenarios and services. The core of its realization lies in transforming the
traditional network architecture model and establishing a new service-centric model to enhance the comprehensiveness
of network services, optimize the efficiency of resource utilization, and ensure that complex and changing personalized
scenarios are accurately matched with services, thus maximizing the value of the network. In order to achieve this
vision, the network is capable of adapting to the subtle and specific needs of users. This requires a complex
understanding of user intent, including the ability to quickly extract prominent information and translate it into precise
network strategies. This capability is the foundation of the vision for a fully automated network. Furthermore, the core
of the broader objectives of 6G technology is to pursue unparalleled user experiences for all parties, including vertical
industries and individual consumers, through the seamless integration of user intent comprehension and dynamic
network adaptation.
4.2.2 High-Level Description of Intent Policy Multi-Stage Processing
To accommodate this transition to on-demand services, the intent policy multi-stage processing framework became a
key component of the 6G ecosystem. This innovative mechanism aims to interpret and manipulate user intent and
translate them into executable network policies that dynamically adapt to the fluctuating demands of different network
scenarios. This framework employs a hierarchical decomposition methodology to deconstruct the user's natural
language intent into multiple levels. This ensures the accurate, timely and standardized translation of a natural language
intent policy into a multi-level fine-grained network template that supports on-demand services.
NOTE: This hierarchical decomposition methodology is similar to how policy grammar is structured in ETSI
GS ENI 030 [2] and modelled in ETSI GS ENI 019 [i.1].
More specifically:
• Multi-level Fine-grained Network Template: A hierarchical network configuration template system,
including intent-level templates, service-level templates, and user-level templates, enables level-by-level
refinement and personalized configuration.
Each level of the intent policy multi-stage processing framework represents a deeper and more detailed representation
of the user's intent and is customized to support on-demand services. It acts as a bridge that seamlessly connects the
human-centric realm of expression with the intricate configuration of the network, ensuring that the network
infrastructure dynamically adapts to meet the precise and changing needs of users.
ETSI
8 ETSI GS ENI 033 V4.1.1 (2024-08)
4.3 Functional Architecture
Intent Policy Multi-Stage Processing transforms the network requirements in the user's natural language intent into
identifiable and deliverable network policies. Figure 4.3.1 shows the transformation of intent policy, which consists of
four steps: generate intent-level templates, generate service-level templates, generate user-level templates, and generate
network policies.
Figure 4.3.1: Transformation of Intent Policy
The detailed definition of the templates and policies for the Intent Policy Multi-Stage Processing is as follows:
• Intent-level Template: An initial state of a network policy for mining user intent into intent-level entities and
combining them into templates via the knowledge base (e.g. a document) and AI model. The format of
intent-level template has certain restrictions, and it is generally in the form: : Target
Entity, : Target Entity, etc.
• Operation: Operation represents the action or activity that the user intends to perform on or with the Target
Entity within the context of their expressed intent. It signifies the type of task, command, or manipulation the
user desires, such as 'add', 'set', 'block', 'allow', etc.
• Entity Type: A classification of specific information or object types that represent the key elements extracted
from user intent. All intent-level entity types include: Object, Middlebox, Location, Service, Time, Bandwidth,
Src, Dst, Protocol.
• Target Entity: Target Entity refers to the specific object, concept, or piece of information that the user is
directly referring to or interacting with in their expressed intent, serving as a key point for action or retrieval in
a system. For example, 'students' under , (firewall,admit) under , 'video streaming'
under , and [10 Mbps, 20 Mbps] under .
NOTE 1: Not every is preceded by an , e.g. for Object, Time, etc. no is
required.
NOTE 2: Intent-level entities could be expressed in a variety of ways and are not limited to string type expressions,
e.g. tuple form under the type: (firewall,close), list form under the
type: [10 Mbps, 20 Mbps].
• Service-level Template: An intermediate state network policy, which can select the appropriate service-level
templates according to the extracted intent-level entity types and user intent through the AI model, and form an
information structure that meets the business needs and user group characteristics according to the information
of the knowledge base. This typically consists of Quality of Service (QoS) template, Access Control
List (ACL) template, Service-Level Agreement (SLA) template, and Network Functions Virtualisation (NFV)
template.
• QoS Template: An intermediate state network policy framework for defining and guaranteeing performance
levels for specific traffic or services in a network. It typically includes presets for parameters such as
bandwidth, latency, etc. to ensure that critical applications are prioritized on the network to meet user
performance requirements.
• ACL Template: An intermediate state network security policy framework for controlling access to network
traffic. It defines which source IP addresses access which destination IP addresses and at what times. ACL
templates also include rules for handling intermediate network devices, such as firewalls, to allow or deny
specific types of traffic to protect the network from unauthorized access and other security threats.
• SLA Template: A standardized framework of agreements used to clarify expectations between service
providers and customers regarding service quality and availability. It typically includes service level objectives
and service credit or compensation provisions in the event that these objectives are not met.
ETSI
9 ETSI GS ENI 033 V4.1.1 (2024-08)
• NFV Template: A technical framework for defining how to deploy and manage network functions on a
standardized virtualized infrastructure. It includes guidance on the configuration and management of
virtualized network devices and how to implement traditional hardware network functions in a cloud
environment.
• User-level Template: One that combines knowledge base (e.g. knowledge graph) and differentially adapts
decisions based on personalized information such as user devices, ultimately generating customize
...