ETSI GR ENI 049 V4.1.1 (2025-05)

Experiential Networked Intelligence (ENI); Definition of Data Centre network autonomic levels

DGR/ENI-0049v411_def_DCNAL

General Information

• Status: Not Published
• Technical Committee: ENI - Experiential Networked Intelligence
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Due Date: 22-May-2025
• Completion Date: 13-May-2025

Standards Content (Sample)

GROUP REPORT
Experiential Networked Intelligence (ENI);
Definition of Data Centre Networks autonomic level
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 GR ENI 049 V4.1.1 (2025-05)

Reference
DGR/ENI-0049v411_def_DCNAL
Keywords
6G, closed control loop, data centres, GenAI, LLM,
native AI
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
3 ETSI GR ENI 049 V4.1.1 (2025-05)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definition of terms, symbols and abbreviations . 5
3.1 Terms . 5
3.2 Symbols . 6
3.3 Abbreviations . 6
4 Concept and Method for Autonomicity Classification targeting Data centre Network Operation
and Management . 7
5 Autonomous Workflow for Data centre Network Operation and Management. 7
6 Network Service Scenarios and Autonomous Network Classification Recommendations . 9
6.1 Overview . 9
6.2 Network Design and Provisioning - DC POD Planning and Deployment . 9
6.2.1 Function Requirement Overview . 9
6.2.2 Workflow Process and Task Definition . 10
6.2.3 Classification requirements . 11
6.3 Network Service Automation - Application Rollout and Provisioning . 12
6.3.1 Function Requirement Overview . 12
6.3.2 Workflow Process and Task Definition . 13
6.3.3 Classification requirements . 15
6.4 Network Monitoring and Troubleshooting . 16
6.4.1 Function Requirement Overview . 16
6.4.2 Workflow Process and Task Definition . 17
6.4.3 Classification requirements . 18
6.5 Network Change - Application Policy Change . 20
6.5.1 Function Requirement Overview . 20
6.5.2 Workflow Process and Task Definition . 21
6.5.3 Classification requirements . 22
7 Conclusions . 23
History . 24

ETSI
4 ETSI GR ENI 049 V4.1.1 (2025-05)
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.
Foreword
This Group Report (GR) has been produced by ETSI Industry Specification Group (ISG) Experiential Networked
Intelligence (ENI).
Modal verbs terminology
In the present document "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
5 ETSI GR ENI 049 V4.1.1 (2025-05)
1 Scope
The present document defines network autonomous features and levels for Data centre networks, including the
intelligent characteristics at each layer (from Level 1 to Level 5) and closed-loop management process, including:
• The concept, scope, dimension and overall method of IP network operation and management autonomous level
classification, evolving from ETSI GR ENI 007 [i.3] and ETSI GR ENI 010 [i.4]:
- Data centre network operation and management processes and classification method, including service
and resource management.
- Technical requirements for autonomous level classification, and its key technical processes.
2 References
2.1 Normative references
Normative references are not applicable in the present document.
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 may be useful in implementing an ETSI deliverable or add to the reader's
understanding, but are not required for conformance to the present document.
[i.1] TM Forum IG1230: "Autonomous Network Technical Architecture".
[i.2] ETSI GR ENI 004: "Experiential Networked Intelligence (ENI); Terminology for Main Concepts
in ENI".
[i.3] ETSI GR ENI 007: "Experiential Networked Intelligence (ENI); ENI Definition of Categories for
AI Application to Networks".
[i.4] ETSI GR ENI 010: "Experiential Networked Intelligence (ENI); Evaluation of categories for AI
application to Networks".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI GR ENI 004 [i.2] and the following apply:
application fault management: alarm monitoring, correlation, and troubleshooting for connectivity related to data
centre applications
autonomous networks: set of self-governing programmable and explainable systems that seamlessly deliver secure,
context-aware, business-driven services
NOTE: These services are created and maintained using model-driven engineering and administered by using
policies.
ETSI
6 ETSI GR ENI 049 V4.1.1 (2025-05)
Availability Zone (AZ): set of one or more physical data centres
NOTE: Multiple AZs with independent geographical locations, power, and networks are created in a region. AZs
are connected through low-latency networks. Each AZ is not affected by faults in other AZs.
deployment unit Point Of Delivery (POD): minimum equipment unit connected to the data centre network
NOTE: It consists of switches, routers, firewalls, load balancers, and servers, etc. to provide network services and
applications. A POD refers to a physical area connected to a service distribution network.
evaluation dimension: viewpoint that can be divided into five dimensions such as ManMachine Interface, Decision
Making Participation, Data Collection and Analysis, Degree of Intelligence and Environmental Adaptability
NOTE: As defined in ETSI GR ENI 007 [i.3].
evaluation object: AI application or a part of Network Lifecycle, defined from two dimensions: the subsystems and the
network lifecycle
network digital map: basic function of the network digital twin and physical network in operation
NOTE: Topology Models and associates resource model data to provide data centre applications and network
topology association for the network digital twin, supporting network intent management and display.
network lifecycle: work-flow of activities including network planning, network deployment, network service
provisioning, network changes, network maintenance, network optimization in real-time
region: collection of resources divided by the geographical location of a data centre
NOTE: Users can be authorized by region. AZs in the same region can communicate with each other over the
intranet, but not between different regions. A country can be geographically divided into different regions
and regions can be selected based on the service proximity principle.
network element, management system, network platform
subsystem:
technical expert: person in charge of defining or supporting Operational Procedures within a CSP Network
NOTE: This person is in charge of Capacity Planning, Engineering, Designing, and Troubleshooting.
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI GR ENI 004 [i.2], ETSI GR ENI 007 [i.3]
and the following apply:
AI Artificial Intelligence
DC Data Centre
DC-GW Data Centre Gateway
DCN Data Centre Network
KPI Key Performance Indicator
RMA Return Material Authorization
SLA Service Level Agreement
VPC Virtual Private Cloud
ETSI
7 ETSI GR ENI 049 V4.1.1 (2025-05)
4 Concept and Method for Autonomicity Classification
targeting Data centre Network Operation and
Management
Referring to ETSI GR ENI 010 [i.4], and the TMF autonomous network technical architecture [i.1], the Data Centre
Network (DCN) operation and management autonomous level classification framework describes the categorization
dimensions (Intent management, Perception, Analysis, Decision-making, Execution) of evaluating the autonomous level
of specific network operation and management functional characteristics, and the categorization principle (human
participation in the whole process) and qualitative descriptions (operator, system, operator and system).
The goal of the DCN autonomous mode of operation is to reduce and eliminate manual operations on the network
gradually. Customers can gradually evolve into a fully automated and autonomous data centre network by defining
autonomous capabilities. Network automation and intelligent technologies are key enabling technologies of the
autonomous network.
DCN lifecycle management service, generally includes planning and construction, network operations, monitoring and
O&M, and optimization. Table 1 describes the DCN autonomous classification Levels.
Table 1: Overview of DCN Autonomous Classification Levels
L1-L5 Level Level Definition Description
L1 Phase - Manual Management • All network operation management processes are completed
manually and rely heavily on human experience. The efficiency is
closely related to human capabilities and experience.
• Network management and O&M knowledge accumulation rely on
document sharing and human communication, which is low in
efficiency and high in learning costs.
L2 Phase - Tool Management • Some network operations introduce specific tools to improve
productivity in the field. Typical tools include the configuration
automation tool and the traffic collection and analysis tool. The
efficiency is improved.
• Network planning and design requires personnel to participate in
network design and configuration audit, resulting in low efficiency.
L3 Phase - Automatic Network
• Network management systems have network automation
Management capabilities throughout the lifecycle management of network
operation.
• These systems generally deliver automation.
L4 Phase - Intelligent Network
• In some network operation scenarios, network management
Management systems can provide autonomous capabilities.
• The autonomous systems provide user-friendly intent-based
interface, more reliable due to pre-test, post-checks, and
validation.
L5 Phase - Intelligent Network
• The autonomous system is fully independent in all service
Management
scenarios and people are normally outside of the process. No
details will be present in the following Classification Requirement
tables.
5 Autonomous Workflow for Data centre Network
Operation and Management
The DCN of a large organization generally includes multiple data centres across multiple geographic regions. To
support modular management of each data centre, Point of Delivery (POD) as a specific point of delivery or service
point, is designed to group devices to support specific workloads or services. From a functional point of view, these
PODs can be further classified into service PODs, access PODs (Internet access PODs, external access PODs, wide area
access PODs), and transit PODs. These intra-POD and inter-POD interconnection networks are large-scale and
complex. Therefore, autonomous network capabilities are needed to improve automatic management.
ETSI
8 ETSI GR ENI 049 V4.1.1 (2025-05)
When an application encounters problems of poor network quality, joint analysis and diagnosis by the application and
network departments are often required. Since the application department's operation and maintenance system usually
cannot see the network information, the network management software cannot see the application information either.
The two systems operate independently, and data is isolated, resulting in a lack of global perspective and low efficiency
in application network monitoring and insurance. Thus application quality assurance is also a key requirement for DCN
autonomous networks.
General network lifecycle management includes network planning, network construction, network maintenance,
network optimization, and network operation. In the case of DCNs, the typical network design scenario is POD
planning and construction. For O&M, the DCN requires not only network management automation, and also fast
application deployment and application quality assurance.
Regarding network management processes, each process can be further divided into five general network service task
phases, including intent, perception, analysis, decision-making, and execution.
Data Centre Autonomous Networks perform five tasks of common network services at each managed service stage
throughout its lifecycle, as described in Figure 1:

Figure 1: 5 Common Task Phases for Network Services
• Intent management: Understands customers' service and management intents and translates them into
specific network configurations and policies. Intent management supports low-level traditional functions, such
as coordinating any required orchestration of configuration operations on the network. It also supports
higher-level abstraction and open modifiable capabilities, allowing customers to adjust solutions based on
actual networking. Intent management also includes the full record of the business intent operation process,
which can be traced and queried.
• Awareness: Monitors data centre network in real-time to detect network service exceptions or SLA problems,
and triggers network analysis and location. Collects original network data and preprocesses the data (such as
data cleaning, enhancement, and statistics collection) to monitor and perceive network information (including
network performance, network exceptions, and network events) and the purpose of visual presentation.
• Analysis: Analyses the current data centre network status and network analysis based on historical data and
customer intents, and generates operation actions, execution policy options, and suggestions that can meet
customer intents.
• Decision-making: Reviews the operation options or suggestions provided by the process to determine the
executable network operations and policies that meet the customer's intent requirements.
• Execution: Generates executable network operations and policies based on the customer intents that have been
decided, automatically implements the network operations and policies deployed on the production network of
the data centre, and verifies the network intents after the network implementation.
ETSI
9 ETSI GR ENI 049 V4.1.1 (2025-05)
6 Network Service Scenarios and Autonomous
Network Classification Recommendations
6.1 Overview
The present document defines the scenarios and requirements for data centre network autonomous in terms of network
design and provisioning, network service automation, network troubleshooting, and optimization. According to network
deployment practices, these scenarios need to be defined first.
6.2 Network Design and Provisioning - DC POD Planning and
Deployment
6.2.1 Function Requirement Overview
Racks are deployed in the POD to install servers, storage, network devices (such as switches, routers, and load
balancers), and power supplies, etc.
POD involves many types of devices. Manual design and deployment of PODs are inefficient and error-prone.
Automatic POD deployment improves the overall efficiency by supporting the E2E automation of design, rollout, and
configuration.
Figure 2: POD network example
ETSI
10 ETSI GR ENI 049 V4.1.1 (2025-05)
6.2.2 Workflow Process and Task Definition

Figure 3: POD network design and provisioning process
The DC POD design, and provisioning process is shown in Figure 3, including intent, analysis, decision-making, and
execution. The detailed management tasks are as follows:
a) Intent management tasks:
POD design intent: the system supports the following design input:
1) Network capacity: number of spine and leaf switches, etc.
2) IP address space management.
3) Network security requirements, including the firewall.
b) Analysis/decision-making task:
Network design and configuration generation for the planned network, the system supports the following
capabilities:
1) Networking topology design: including the network interconnection topology, NE types, NE roles, and
link connections.
2) Network address resources allocation: including IP networks and addresses, VRFs, and VLANs ranges.
3) Network routing protocol configuration: including BGP, OSPF, and ISIS configuration.
4) Interface configuration, such as IP address configuration and VLAN configuration.
5) Service access configuration, such as Layer 2 broadcast domain configuration and Layer 3 gateway
configuration.
6) Reliability configuration.
Network simulation and de
...