Etsi WP 40 Autonomous Networks
Etsi WP 40 Autonomous Networks
40
Autonomous Networks,
supporting tomorrow's ICT
business
1st edition – October 2020
ETSI
06921 Sophia Antipolis CEDEX, France
Tel +33 4 92 94 42 00
info@etsi.org
www.etsi.org
About the Authors
Contributing Organisations and Authors:
China Telecom: Yannan Bai
China Unicom: Bingming Huang
Futurewei: Dong Sun, John Strassner
Huawei: Luigi Licciardi, Hui Li, Lei Wang, Aldo Artigiani
Intel: Dario Sabella, Haining Wang
Orange: Christian Maitre
Portugal Telecom: Francisco Fontes
Samsung: Yue Wang
Telecom Italia: Luca Pesando, Cecilia Corbi
Cadzow: Scott Cadzow
This White Paper is issued for information only. It does not constitute an official or agreed position of
ETSI, nor of its Members. The views expressed are entirely those of the author(s).
The rationale of this White Paper is that Autonomous Networks (AN) are designed to support this
transformation. This technology evolution has now reached a point where a revolution is required in the
way networks are managed, leading to the introduction of new level of automation and intelligence in the
management and provisioning of services and networks. This revolution is termed Autonomous Networks.
In order to gain support, ranging from telecommunications to the extended ecosystem, this White Paper
explores the challenges, business value, vision and the framework around Autonomous Networks. We
also discuss Autonomous Network Levels along with key components associated with the concept of
Autonomous Domain and describe security and privacy capabilities in the evolution of Autonomous
Networks. A small number of use cases, in conjunction with Autonomous Network Levels, are described in
order to illustrate the value proposition of Autonomous Networks and to highlight the contribution of
Standards Development Organisations (SDOs) in driving both the definitions and recommendations
associated with Autonomous Networks. We believe that what is needed is a proper perspective in order
to deliver reliable standards; and to do so successfully, we must solicit feedback from decision makers and
professionals in order to prevent fragmentation in a collaborative environment.
The Autonomous Networks’ objective is to provide a wide variety of autonomous “Network/ICT” services,
infrastructure and capabilities with “Zero-X” (zero wait, zero touch, zero trouble) experience based on
fully automated lifecycle operations of “Self-X” (self-serving, self-fulfilling, self-assuring) to dynamically
accommodate and adapt to customer needs and available resources. These services range from more
efficient versions of current services to mission-critical services to new disruptive services for support of
new business models and innovative user experiences; Autonomous Networks also feature self-evolving
telecom network infrastructures.
The key design principles of Autonomous Networks in order to support tomorrow's ICT systems are:
• Simplification: Componentize the technology into discrete business capabilities to simplify and
accelerate the on-boarding of partners.
• Automation: Create zero touch interactions through closed-loop automation of business and
technology operations.
• Intelligence: Move from pre-programmed to real-time data analysis based on ML and AI.
• Autonomy: each Autonomous Domain can govern its own behaviour in support of business goals.
• Abstraction: each Autonomous Domain hides the details of domain implementation, operations
and the functions of the domain elements from its users.
• Collaboration: Service Operations direct specific Autonomous Domains to cooperate with each
other based on the intent mechanism to fulfil business and customer needs throughout the
service’s lifecycle
The Autonomous Networks will leverage the technology innovation capabilities offered by 5G, artificial
intelligence, virtualization, cloud and edge computing as underlying elements ensuring that the verticals
are an integral component of the telecommunications ecosystem.
ETSI is playing and can play a key role in the recommendation for and standardization of Autonomous
Networks due to its excellence and worldwide recognition as an SDO in Network standardization. A
successful industry-wide adoption of Autonomous Networks requires large consensus in building a
common ecosystem. Therefore, we recommend a coordinated effort by leading SDOs, cross industry and
vertical organisations, open source alliances and regulatory entities in order to succeed in this digital
telecommunication transformation. In some sense, the creation of Autonomous Networks in
telecommunications is similar to the advent of autonomous driving vehicles in the automotive Industry.
Furthermore, automation prevents isolation and addresses complexity; delivering efficiency and growing
revenue. By using AN, customers can benefit from increased network reliability, optimized usage, control,
connectivity and customizable services. For example, customers can have access to more flexible usage
models (e.g., pay per use, pay per active services, etc.) according to their needs with the required
performance and Service Level Agreements (SLAs) that can dynamically scale up and down.
Autonomous Networks are perceived differently, depending on the perspective. Below we describe this
phenomenon for Telcos, acting as core providers; business partners, acting as buyers from Telcos; and
customers, acting as final users:
When the Autonomous Networks is in place, operators will be able to benefit from a strong improvement
in efficiency. And for Telcos, the shared innovative services could present new revenue opportunities in
new markets.
The Autonomous Networks’ model of Figure 1 from the GIO report on Autonomous Digital Infrastructure
Workshop Error! Reference source not found. shows how proper operating model can be developed. The A
utonomous Networks’ capabilities required by the customer are realized in both the network core and
network platform.
Services
32pt • Value-add for vertical-specific use cases vertical or with a revenue share, flat rate, pay-go Telco
: R153 G0 B0 • Partner self-service / on-demand highly innovative
offering • May need heavy up-front investment to
• Raw Cloud / MEC for some cases
黑体 create a market
AN Capabilities
“Integration” Services Sophisticated • Consumption model similar to Cloud
Custom Network services (pay-go, self-service, NaaS)
Services • Highly customized services
Vertical Vert ical Cust om er
22pt Customers • Atomic service offerings which can be
Network-as-a-Service • Focus on ease of consumption and integration Custom
stitched by customer to meet specific need
) :18pt to customers’ business Strong technical Network
On-Demand • End-customer self-service capability to self- • Advisory tech services Services
黑色 • On-Demand flexibility via API, Portal, etc. serve Telco
Self-Service • Tooling and qualification services to assist
: • Packaged Cloud offerings integrated Supported by SI or with integration
Integrated in-house dev team
utigerNext LT Regular network/cloud
: Arial • Incrementally add flexibility to existing
“Classic” Telco Services General
Customers business models (e.g. service terms, on-
Direct
In a manner somewhat akin to the levels of automation in cars (see SAE J3016 [6]) there are several
autonomous network levels. These levels are described in in TM FORUM Whitepaper (2019, May) [2], TM
FORUM IG1193 [3], TM FORUM IG1218 [4]) and are as follows:
Level 1 - assisted management The system runs certain repetitive sub-task based on pre-
configured policy to improve the efficiency, which is not
viewed as Autonomous Networks.
Level 2 - partial Autonomous Network The system runs closed-loop O&M for certain business units
based on the intelligence of certain external environments.
Level 4 - high Autonomous Network The system runs, in a more complicated cross-domain
environment, analyzing and making decision based on
predictive or active closed-loop of services and customer
experience-aware networks.
Level 5 - full Autonomous Network The system runs closed-loop capabilities across multiple
services, multiple domains in the full lifecycle
-3 layers: Base groups of functions for diverse customer need and Autonomous Networks services:
⚫ Business operations layer: supports customer, ecosystem and partner business enablement and
operations.
⚫ Service operations layer supports network planning, design, rollout, provisioning, assurance and
optimization operations across multiple autonomous domains.
⚫ Resource operations layer supports automation of network resources and capabilities in each
autonomous domain level.
-4 closed-loops: To fulfil the full lifecycle of the inter-layer interaction process.
⚫ Business closed-loop enables the interaction between business and service operations layers for
business-service lifecycle
⚫ Service closed-loop enables the interaction between service and network resource operations
layers for service-resource lifecycle
⚫ Resource closed-loop enables the interaction of network resource operations in the granularity
level of autonomous domains.
⚫ User closed-loop enables the interaction across three layers and three closed loops for the E2E full
lifecycle of user service.
In order to support the aforementioned full lifecycle of closed-loops, key capabilities of Autonomous
networks have been described in TM FORUM IG1218 [4] by the TM Forum and are as follows:
Category Sub-category
Self-planning/capability delivery supports the customization (DIY) capabilities of
network/ICT service planning, design and deployment.
In a nutshell, Autonomous Networks use a simplified network architecture along with physical and/or
virtualized components, intelligent agents and decision engines that provide fully automated “Zero-X”
innovative, critical ICT services. These features affect the experiences of users/consumers of vertical
industries and support “Self-X” (self-serving, self-fulfilling and self-assuring) capabilities in order to enable
digital transformation of both vertical and telecom industries.
Figure 4 shows usage of Autonomous Domains to collaboratively ensure that different business needs of
Autonomous Networks’ services are fulfilled.
⚫ Autonomous domain 1 – Access: This AD supports different types of access like cellular and
wireless.
⚫ Autonomous domain 2 – Edge: This AD supports the real-time processing and localization required
for connectivity, control, management, orchestration, analytics and applications for AN services.
⚫ Autonomous domain 3 – Transport: This AD supports various transport networks such as IP and
Optical; in both separate and integrated modes as well as backbone.
⚫ Autonomous domain 4/5 – AD 4 – Core: This AD supports the core network, along with computing
and storage; AD5 – Cloud: This AD supports distributed processing for management and
orchestration applications. Physically these two domains could be separate or collocated as
required.
The Autonomous Network applies three types of interacting closed-loops to ensure full end-to-end
lifecycle operation and management. The detailed process has been described in TM FORUM IG1218 [4]
by the TM Forum and is as follows:
1) Business Closed-Loop:
1a) Business Intent Request: The user described their "Business Intent" to the “Business
Operations (BO)” system that requests AN services.
1b) Business Intent Translation: The BO translates business intent into Service Intentions (SI)
such as connectivity, availability, security, quality of service and/or experience; according to
the organization’s business architecture request to the “Service Operations (SO)” system as SI
requests.
2) Service Closed-Loop:
2a) Service Intent Request: The SO in AD5 distributes the Service Intent to the SOs in AD4,
which then translate the SI into Resource Intent (RI) according to the system architecture of
each SO. This results in resource operation management and monitoring commands.
3) Resource Closed-Loop:
3a) Resource Execution: The RO of each AD manages its resources to meet the needs of each
service that it is supporting. It also transfers applicable data to the local PoP (edge) for real-
time information processing and decision making.
3b) Resource Assurance: Each Autonomous Domain monitors abnormal events such as
performance, fault and security attacks; and alerts other affected Autonomous Domains.
Affected Autonomous Domains collaborate to plan and implement a solution and inform the
BO and SO in AD5 when the solution is implemented, and the problem is resolved. The RO may
report to the SO when the events are beyond the management of a single Autonomous
Domain Level. In this way, the SO will take responsibility for cross-Autonomous Domain events
in real time.
3.3 Key Capabilities
3.3.1 Overview
An Autonomous Network is expected to dynamically adapt to changes in its environment. This dynamic
adaptation is built upon three principles that are present in Autonomous Domains: business awareness,
self-x capabilities and intent-driven interaction. This forms the basis for two key future features:
Knowledge-as-a-Service and explainable decisions. These principles provide dynamic, run-time
intelligence to enable business goals and to determine services offered in a given context. Key benefits
include:
• A modular and extensible framework that enables support for new technologies, business models
and operations.
• The use of business rules to determine the set of resources offered in a specific context.
• The agile, secure and flexible delivery of network services supported by self-governing networks
and networked applications.
An Autonomous Domain translates business goals and customer needs into network functions and
services that support the end-to-end delivery of services for the business; even when the environment
changes. This means Autonomous Domains collaborate to adapt their collective capabilities to maintain
contracted services; thus, dynamically providing new services as required. This business awareness is
achieved using self-x capabilities, intent-driven interaction and modelled knowledge.
Policy can take different forms. Imperative policies are commands that explicitly change the state of a set
of targeted entities, while intent policies use a restricted natural language, such as English, to express a
set of goals to be accomplished without defining how to implement those goals.
Thus, intent simplifies the definition of goals and services for different users and hides their
implementation complexity.
There are two types of intent-driven interaction: (1) human-machine interaction and (2) resource closed-
loop interaction. The first relies on humans selectively guiding and providing goals to different types of
machine learning systems. The second refers to the intelligent distribution of intent to the affected
Autonomous Domains. Each Autonomous Domain interacts with other Autonomous Domains as
necessary in order to collaboratively provide an end-to-end service.
Intent interaction may be provided by dedicated external reference points and APIs, as well as other
means that abstract the functionality of an Autonomous Domain. This creates the abstraction of a single,
simplified network - even though it is made up of different domain-based capabilities.
1) Knowledge-as-a-Service
The scaling of resource and service operations requires retrieving knowledge from each applicable
Autonomous Domain for a given context. Each Autonomous Domain has different users with different
needs, defined by different concepts and vocabularies. The integration of the needs of these different
constituencies and their associated knowledge, create different viewpoints that define the business and
system architectures. A viewpoint is a set of abstractions that enables a set of users to view what is
relevant to their tasks and ignore what is not. Knowledge-as-a-Service (KaaS), delivers knowledge from a
viewpoint to a set of users as needed.
Knowledge takes many forms; two important ones are: (1) facts derived from information processing that
have to do with system state, and (2) inferences derived from reasoning algorithms and logic that reflect
changes to the current state. The commonality of state between the two types of knowledge enables
both to be contextualized and reused in similar situations at a later time. The knowledge repositories are
shared between Autonomous Domains and are updated in a consensual manner to reflect new
knowledge learned.
The modelling of knowledge from different viewpoints enable KaaS to be customized for different
consumers. For example, knowledge obtained by telemetry processing in the Autonomous Network can
In contrast, an Autonomous Network provides both an understanding of how the deployed algorithms
work; as well as explanations for why a set of related decisions were made. Explanations in support of
decisions made by an AI solution are crucial in many applications, including autonomous vehicles,
medicine and financial applications. This has resulted in a field of study called eXplainable Artificial
Intelligence (XAI), whose goal is to ensure that humans are able to understand why a machine makes its
decisions without knowing the details of the structure of the model or how it processes data internally.
Therefore, we anticipate that a much more agile security regime, similar to virtualized networks may be
necessary, where each instance of a service is both uniquely identifiable and authorized while anchored
to a trusted component of the wider underlying system.
In this respect, we expect that Autonomous Networks will build on the security principles that apply to
networks composed of virtual devices and services; such as the principles described in ETSI ISG NFV that
are built on the output of ETSI TC CYBER. Additionally, the work of ISG SAI will be taken into account
wherever the nature of the deployed artificial intelligence could impact the security and functional nature
of Autonomous Networks.
The core concern of AN as regards to security is that as the degree of autonomy increases from L0 to L5
the level of attacker knowledge changes, particularly in the context of insider attack wherein the
Autonomous Network attacks itself. This will require a more intensive role of monitoring for adverse
behaviour but that has to be balanced as every new application is at risk of being ranked as an adversary.
This may require use of technologies such as Functional Cryptography, such as attribute based
cryptography and homomorphic encryption and Permissioned Ledger Technology in order to ensure the
use of non-repudiation functions; acting across various control loops that are central to Autonomous
Networks.
The security and privacy protection technologies applied to Autonomous Networks will therefore be
designed as "by default, always on" capabilities - taking advantage of well understood security
mechanisms to maximize the assurances of each of the CIA paradigm for each stakeholder of an
Autonomous Network.
The presence of a Digital Twin mechanism enables the management of the E2E Transport Services across
the whole Transport Network (e.g., Fronthaul, Backhaul and Backbone), gathering the network behaviour
data, such as topology, configuration and routing, and correlating them based on time and space.
Using AI to continuously analysing metrics from IFIT, predictive SLO breach can prevent service
degradation proactively by adjusting connectivity paths and resources assignment with SRv6 technology.
This enables the creation of a multi-dimensional Transport Autonomous Domain “Visualization and
Reporting”, enhancing all phases of the network lifecycle management.
In the following table, we consider Transport Network underpinning 5G lifecycle management for both
infrastructure and service management. Only autonomy levels 2 to 4 are considered, due to the fact that
either current technologies already have those functionalities, or they will become available in the
foreseeable future.
The key enabler of F5G automation and autonomy is end-to-end management and control system. It
makes optimized use of ultra-high bandwidth resources while efficiently managing massive and dense
communication networks in order to improve the experience of both operators and end users.
As the aforementioned management and control system evolves towards higher levels of automation and
autonomy, it will be able to sense real-time environmental changes, learn, make intelligent analysis and
provide advice to network operators or customers on decision-making, optimization and adjustment of
the F5G network.
To achieve this, an automated management and control system, like a SDN, will be introduced into each
network segment of F5G to form the Autonomous Domain. On top of them, an end-to-end orchestrator is
used for the network resource optimization, service provision, fulfilment and global operation. The APIs
between SDN controllers and end-to-end orchestrator will be specified to enable these features.
Level 2: The end-to-end orchestrator is introduced to perform end-to-end network resource configuration
and service provisioning, which is based on pre-defined rules.
Level 3: The capabilities of intelligent analysis is introduced into the controllers and orchestrator, to
enable the end-to-end closed-loop automation, such as network status monitoring and visualization, and
alarms for root cause analysis.
In F5G, hardware technologies continue to evolve, providing networks with larger and more flexible
bandwidth, lower latency and near zero packet loss. These are the cases for Wi-Fi 6 with lower air
interface latency, 10/50G Passive Optical Networks (PON) and next generation of Optical Transport
Networks (OTN) with support for flexible bandwidth granularity of connections.
Meanwhile, the software technologies continue improving, supporting the quality required by F5G
applications; such as awareness of the service type and service quality requirements; and support for
automated resource allocation. Such systems also support continuous monitoring and optimization on the
qualities of the service to ensure the users’ experiences.
Artificial Intelligence (AI) and Machine Learning (ML) are the key technologies for intelligent service
provisioning and assurance. Embedded AI/ML capabilities are needed in many areas an automated multi-
service network. With AI/ML, the data transportation models of different application services can be
learned so that different kinds of applications can be distinguished automatically, without touching the
inner content - thus protecting user privacy. At the same time, the network status can be continuously
collected and analysed, in order to detect potential service disruption risks in real time, and to provide
input on network resource adjustments in a timely manner.
Level 3: Automated distinction between different kinds of service: intelligently analysing the QoE of the
service and adjusting the service if the service is degraded.
Level 4: Proactive QoE assurance: proactively adjust the service, based on the changing trends of the
network circumstances, before QoE degradation.
As a typical example, in a PON and OTN network, fibre is the most important media for data transmission.
The failure of fibre will adversely impact the network. Therefore, the closed-loop control of fibre failure
prediction, allocation and recovery is very useful for F5G to improve the operator’s experience on
network operation and maintenance.
With AI/ML technologies, physical parameters of the fibre can be collected and analysed to predict the
fibre failure based on pre-trained models. Once a failure is predicted, suggestions can be provided on how
Level 2: Alarm information will be automatically collected and analysed, and decisions on how to recover
from failure need to be made by humans.
Level 3: The network status will be monitored, and the network failure or degradation will be diagnosed,
isolated and fixed automatically after it occurs.
Level 4: Proactive operation: Based on the in-depth monitoring and trend analysis on the network status,
the sub-health status of each components of the network will be identified and the faults will be
predicted and rectified before they occur.
Hierarchical autonomous architecture provides different levels of network autonomy: network elements
layer usually implies high real-time closed-loop operations; single-domain network layer usually implies
low real-time closed-loop operations; cross-domain network layer implies cross-domain orchestration;
and business automation generally indicates an agile and customer centric implementation.
Level 2: system additionally analyses the coverage performance and identify coverage issues based on the
coverage issue rules specified by humans.
Level 4: system additionally determines and updates coverage optimization policies and the coverage
requirements dynamically, based on service assurance intent.
While the capability of "zero bits, zero watts" needs to be constructed, in a typical network, the features
of different scenarios vary greatly. Automatically identifying different scenarios and formulating
appropriate policies becomes key to saving energy.
Level 2: The system can automatically analyse slice running data and resource configuration information.
Based on the analysis, experts can customize some rules to trigger the system to automatically complete
slice adjustment.
Level 3: The system can additionally analyse the slice dynamic adjustment solution, determine the optimal
solution by humans, based on the SLA requirements of industry slice tenants - and then experts
determine whether to automatically implement the solution.
Level 4: The system can additionally determine whether to dynamically adjust slice policies based on the
SLA requirements and running data of industry slice tenants. In addition, the system optimizes the original
dynamic slice adjustment policy based on the slice running status and SLA after the policy is implemented.
From the technical point of view, management of network slicing is not only required to satisfy
differentiated SLAs and isolation requirements for various services, such as those during the creation
stage; it is also required to provide high efficiency in terms of real-time monitoring, analysis, and self-
optimization. These requirements cannot be properly achieved in current network management systems,
which rely on manual operation and static configuration.
To that end, the architecture and key technological innovations are critical for network slicing operations.
The new technical challenges for network management turns AI into a competitive option for handling
different types of complex network slicing scenarios, especially those in which deterministic results
cannot be easily derived from analysis or control.
1) Proof of Concept
The first Proof of Concept (PoC) of ETSI ISG ENI (see ETSI GS ENI 001 V2.1.1 (2019-09) [14]) successfully
demonstrated the use of AI and intent based interface to improve the autonomy of transport network
slicing system.
The Transport Network Slice Manager (TNSM) manages and monitors the transport network slice
instances. Its user interface simplifies input by offering intent-based templates specifying device’s roles
and performance requirements for different scenarios. TNSM converts the intent-based request into
detailed request with unified format. During the conversion, parameters will be supplemented according
to the build-in relationship between the selected template and the unified format of slice creation
requirement. Then the TNSM calculates the optimal result including topology and resources and creates a
slice in the underlying network accordingly.
The intelligent policy generator decides whether the transport network slice instance should be scaled up
or down, as well as the bandwidth adjustment policy, and sends the intelligent policy to the TNSM when
necessary. The TNSM automatically executes the received scale up or down policy by reconfiguring the
port bandwidth of the transport network nodes.
Level 2: The system can automatically create, modify and terminate a transport network slice based on
scripts, pre-configured triggers and awareness of network data.
Level 3: The system can automatically create, modify and terminate a transport network slice based on
collected user intents. And it can also provide suggested optimization options based on comprehensive
analysis of network data.
Level 4: The system can make prediction based on learned knowledge about the network and suggest the
optimal option for transport network management and operation considering human intents.
5.2 TM Forum
The TM Forum was one of the first organizations that recognized the strong value of Autonomous
Networks in terms of business of Digital Transformation.
In May 2019 a successful workshop was organized in Nice DTW 2019, where a TMF white paper, titled
“Autonomous Networks: Empowering Digital Transformation For the Telecoms Industry” [2] was
presented by leading CSPs and vendors, touting the savings that AN can bring in operational cost and
resource usage. The activity was followed successfully with a dedicated project “Autonomous Network
Project”, with webinars, workshops and presentations at major TMF events.
The TMF activities also addressed some significant use cases and exploited the impact of AN in the new
Open Digital Framework (ODF) as well as Open Digital Architecture (ODA).
Some of the use cases are going to be implemented in a few Catalysts - preliminary Proof of Concepts
where CSPs, vendors and technology providers develop interoperable software to be showed at next DTW
2020 in Copenhagen. The major focus, due to the know-how of companies and experts involved, will be IT
and the upper management and business layers.
The TMF also developed significant experience in Open APIs development: in the case, the TMF develops
APIs of interest in AN perspective to evaluate the opportunity of usage, and hopefully, also the
opportunity to commit APIs development according to recommendations and specifications done by ETSI.
5.3 GSMA
The GSMA developed a major study and launched a significant initiative on the role of automation,
supported by AI, regarding network evolution.
At Shanghai MWC, June 2019, a Workshop supported by a White Paper (see GSMA Whitepaper. (2019,
Oct), AI in Network Use Cases in China [7][6]) was successfully organized, where the business and market
value was outlined by reporting the viewpoints of leading Chinese CSPs, vendors and verticals, including
OTTs. The launch of a new project (now limited to the Greater China Region) on Automation in network
evolution was also announced. The exploitation of business value for some leading verticals represents a
key attribute and is viewed as a leading driver in the evolution of Autonomous Networks.
5.4 3GPP
In August 2019, 3GPP SA WG5 initiated the ”Study on concept, requirements and solutions for levels of
autonomous network” (see 3GPP Rel-16 TR28.810 [8]).
The study provides concepts, evaluation dimensions, definitions, workflow in typical scenarios and
detailed classification description of Autonomous Networks. In Jun 2020, a Rel-17 WID on autonomous
network levels was approved to continue the standardization work. The main objective is to develop the
concept and architecture of automatic network, classification of autonomous networks levels and
combine the classification with the existing automation capabilities.
3GPP SA WG5 also carries out a series of automation related standardization projects covering planning,
deployment, maintenance and optimization phases of the entire mobile network life cycle. Rel-17 work
items include intent driven management services for mobile network, management services for
communication service assurance, and studies on enhancement of management data analytics, energy
efficiency on 5G and Self-Organizing Networks (SON) for 5G networks, just to name a few.
3GPP SA WG2 and 3GPP RAN WG3 also initiated research on supporting automatic network intelligence.
3GPP RAN WG3 started the discussion on RAN-centric Data Collection and Utilization in Rel-16 (3GPP TR
37.816 [9]). The objective is to study the wireless data collection and application; oriented toward
network automation and intelligence, such as SON (e.g. ANR) and RRM enhancement.
Linux Foundation Networking (LFN) is an umbrella organisation to harmonize existing initiatives and to
provide building blocks for network infrastructure and services. The Open Network Automation Platform
(ONAP) project (see LFN ONAP (2020), ONAP specifications [11]) officially launched in February 2017 and
is the largest open source networking project that exists today in the industry. It provides an open-source
network automation platform for real-time, policy-driven orchestration and automation of physical and
virtual network functions.
ONAP’s 6th Release (Frankfurt Release) was delivered in June 2020 and it is continuously evolving and
enhancing the platform to satisfy service providers requirements and use cases; such as Cloud Native
application orchestration, 5G Network Slicing, security, edge and O-RAN orchestration. The Frankfurt
Release is the result of a collaborative community consisting of 31 sub-projects, 35 Organisations and
more than 400 developers.
According to the community vision, a key component of an Autonomous Network is the ability to perform
service and resource orchestration to deliver whole automation across different autonomous domains,
across complete service and resource lifecycles; making use of analytics and data-driven machine learning
and artificial intelligence algorithms. The “CLAMP module” used for Service Operations has been created
for designing and managing control loops in an automated way.
ONAP and other LFN projects such as CCNT, OPNFV and OVP, with their reference Implementations can
complement the efforts of the main SDOs in the AN standardization landscape.
5.6 ITU-T
The ITU is addressing aspects of network automation in the Focus Group (FG) ML5G and in the parent
Study Group SG13, in particular in question 20, that has so far produced four recommendations focusing
on application of machine learning to networking in the Y.317x series and is working on the technical
reports produced by the FG to transform them into recommendations or framework documents.
Currently, the most relevant concepts are the identified use cases addressing Autonomous Networks
scenarios, like the “ML-based end-to-end network management”. This use case focuses in the root cause
analysis in a network divided into different domains, each, currently being overlooked by a different
human operator.
• ITU-T SG13 has recently held a joint workshop with ETSI ISG ENI in order to share their vision, and
the fundamental concepts to avoid misalignments and divergence of the specifications produced
by the two groups.
• ITU-T, FG-ML5G (Focus Group on Machine Learning for Future Networks including 5G) was
established in November 2017, with the main objective of producing draft technical reports and
specifications for machine learning (ML) for future networks, including interfaces, network
architectures, protocols, algorithms and data formats. As stated in the group’s Terms of
5.7 ETSI
Some key technologies, solutions and standards under study and development in ETSI can significantly
contribute to the evolution of Autonomous Networks. Given the scale, heterogeneity and complexity of
emerging networks, management solutions need to be highly automated and extremely “intelligent”, in
the sense of a “machine intelligence”, able to collect large amounts of relevant data, process it and act on
it in an automated fashion.
For this reason, and in order to provide a harmonized view of the ETSI activities in this field, recently a
White Paper (see ETSI White Paper 32: Network Transformation [13]) was published to give an insight into
Network Transformation challenges, written by the Chairmen of ISGs ENI, MEC, NFV and ZSM. Specifically,
the authors address the common framework for the management of virtualized network environments,
as defined by ETSI ISG NFV, and extend it to the distributed edge with public-cloud aspects by ETSI ISG
MEC. They discuss how ETSI ISG ENI solutions can be deployed within or across network domains in order
to optimize the processing of data, extract knowledge, and thus enable decision-making. Finally, they
demonstrate how the work of ETSI ISG ZSM is bringing all these and other technologies together into a
single automated management framework.
The following text highlights the main topics addressed by ETSI’s groups towards Autonomous Networks.
⚫ ENI (Experiential Networked Intelligence) Industry Specification Group (ENI ISG) is defining a cognitive
network management architecture to adjust offered services based on user needs, environmental
conditions and business goals. Therefore, 5G networks will benefit from automated service
provisioning, operation, and assurance. The use of Artificial Intelligence techniques in the network will
solve problems of future network deployment and operation. ENI focuses on improving the operator
experience, using closed-loop AI mechanisms and metadata-driven policies to recognize and
incorporate new knowledge. This model gives recommendations to decision-making systems.
ENI has published version 1 of the “System Architecture” (see ETSI GS ENI 005 V1.1.1 [14]), Context
Aware Policy Management and Categorization. Version 2 of the “Use cases, Requirements” (see ETSI
GS ENI 001 V2.1.1 [15]) includes a Terminology and a Proof of Concept (PoC) Framework. ENI has
launched a continuing Proof of Concept demonstrating its work. Published deliverables are listed
in ETSI ENI (2019), Specifications (https://docbox.etsi.org/ISG/ENI/Open/ [16]).
⚫ MEC (Multiaccess Edge Computing) is defining an architecture fully inspired and based on the ETSI
NFV framework (see ETSI MEC (2020), Specifications, https://docbox.etsi.org/ISG/MEC/Open/ [17])
and the published standard demonstrated how ETSI MEC defined entities integrate with NFV. The
Operations Support System (OSS) is a traditional management node included for completeness of the
reference architecture, but ETSI ISG MEC does not specify anything about it. However, as a service-
based approach to management is developed by ETSI ISG ZSM and other organisations, ETSI ISG MEC
expects to align with the emerging zero-touch management entities, such as those in the ETSI ISG
5.8 Takeaways
Figure 8 below shows a simplified mapping of ETSI contributions for the evolution of Autonomous
Networks, as presented at GIO workshop on Autonomous Digital Infrastructure [23}.
It is recommended that we form a synergistic and coordinated activity, first inside ETSI and later extended
to other forums, starting with the most relevant ones already active in the AN field. A significant common
effort is required to work together to facilitate the adoption of common standards what avoiding market
fragmentation.
For this reason, these important AN stakeholders should collaborate in order to synchronize the initiatives
already underway and to promote the engagement and the support of other best-in-class organisations
still not active, in particular verticals associations. Similarly, the Cross-SDO environment GIO (Global
Initiative Organisation) can also facilitate the coordination and synchronization among SDOs and vertical
associations through workshops and round tables.
Therefore, we propose the creation of a sort of “Engagement Roadmap Plan”, where Standard
Organisations can collaborate to produce complementary specifications and open source projects can
target the implementation of the software building blocks and reference implementations based on such
architectural specifications.
[3] TM FORUM IG1193 (2019, October), Cross-Industry Autonomous Networks – Vision and
Roadmap v1.0.
[4] TM FORUM IG1218 (2020, July), Autonomous Networks Business Requirements & Architecture.
[8] 3GPP Rel-16 TR28.810 (2019): Study on concept, requirements and solutions for levels of
autonomous network.
[9] 3GPP Rel-16 TR37.816: Study on RAN-centric data collection and utilization.
[10] 3GPP Rel-16 TR23.791: Study of enablers for Network Automation for 5G. Status: Under
change control.
[13] ETSI White Paper (2019): ETSI White Paper 32: Network Transformation.
[23] Licciardi, L. (2020, July): GIO report on Autonomous Digital Infrastructure Workshop.
This White Paper is issued for information only. It does not constitute an official or agreed position of ETSI, nor of its Members. The
views expressed are entirely those of the author(s).
ETSI declines all responsibility for any errors and any loss or damage resulting from use of the contents of this White Paper.
ETSI also declines responsibility for any infringement of any third party's Intellectual Property Rights (IPR), but will be pleased to
acknowledge any IPR and correct any infringement of which it is advised.
Copyright Notification
Copying or reproduction in whole is permitted if the copy is complete and unchanged (including this copyright statement).
© ETSI 2020. All rights reserved.
DECT™, PLUGTESTS™, UMTS™, TIPHON™, IMS™, INTEROPOLIS™, FORAPOLIS™, and the TIPHON and ETSI logos are Trade Marks of ETSI
registered for the benefit of its Members.
3GPP™ and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
GSM™, the Global System for Mobile communication, is a registered Trade Mark of the GSM Association.