Network Control and Management Automation Architecture Standardization Perspective
Network Control and Management Automation Architecture Standardization Perspective
106 2471-2825/21/$25.00 © 2021 IEEE IEEE Communications Standards Magazine • September 2021
FIGURe 1. High-level architecture for integrating machine learning in future networks including IMT-2020.
of each of the five dimensions. Network intelli- three fundamental stages: inference optimization,
gence capability levels are determined based on model deployment, and model inference. In the
whether the function of a dimension is executed inference optimization stage, trained ML models
by a human only, a human and a system, or a sys- are modified to improve the performance when
tem only. Based on the combinations of the intel- executing an inference in a certain deployment
ligence capability levels of individual dimensions, environment according to the requirements of
six intelligence levels are defined, as shown in the use case and the current state of the network.
Table 1. In the lowest network intelligence level of In the model deployment stage, the ready-to-run
L0, which corresponds to a manual network oper- ML model is deployed in a specific deployment
ation, all dimensions are executed by humans. environment. Finally, in the inference stage, the
Similarly, in the highest network intelligence level model inference output result (e.g., prediction or
of L5, which corresponds to full intelligence, all classification) is applied to ML pipelines.
dimensions are autonomously executed by the In addition to the above ITU-T Recom-
system only. In between, there are intermediate mendations produced by enriching FG ML5G
intelligence levels in which the tasks of some deliverables, ITU-T SG13 has also produced Rec-
dimensions require human involvement. ommendations from contributions submitted by
ITU-T Recommendation Y.3074 specifies the its delegates, which are described next.
ML data handling framework to deal with the
diversity of the control data produced by various ITU-T Recommendations from
components in the network. It introduces data SG13 Contributions
models, brokers, and application program inter- From the contributions of its delegates, ITU-T
faces (APIs) in both the user and control planes. SG13 has produced three Recommendations,
It also provides the requirements for input data Y.3175, Y.3177, and Y.3178, which are briefly
collection, processing, and output data. described below.
ITU-T Recommendation Y.3176 describes the ITU-T Recommendation Y.3175 specifies the
challenges, motivations, requirements, and archi- functional architecture of ML-based quality of ser-
tecture for ML marketplace integration in networks. vice (QoS) assurance, including the reference points.
It defines the ML marketplace as a repository of It also describes the procedures for ML-based QoS
interoperable trained AI/ML models. It also spec- assurance in the IMT-2020 network.
ifies a method that uses the ML intent and MLFO By extending the basic ML architecture spec-
to select appropriate ML models from the ML mar- ified in ITU-T Y.3172, ITU-T Recommendation
ketplace, and interfaces to connect the ML market- Y.3177 specifies a high-level architecture of AI/
place with the ML sandbox and the ML pipeline. ML-based network automation for resource and
Similarly, ITU-T Recommendation Y.3179 spec- fault management. Figure 2 shows the architec-
ifies an architectural framework for ML model ture, which is composed of four subsystems. The
serving, that is, the preparation and deployment of management subsystem contains the following
ML models in different deployment environments. three management functions: resource manage-
The ML model service takes place in the following ment, fault management, and other manage-
L1 Assisted network operation Human and system Human and system Human Human Human
L2 Preliminary intelligence System Human and system Human and system Human Human
L3 Intermediate intelligence System System Human and system Human and System Human
ment functions. It also contains the ML functional pre-standardization activities on autonomous net-
orchestrator (MLFO), which takes ML intents as works. The terms of reference of FG AN define
input. The AI/ML pipeline consists of six function- autonomous networks as those that possess the
al groups: data collection, fault detection, fault ability to monitor, operate, recover, heal, protect,
recovery, resource prediction, resource adapta- optimize, and reconfigure themselves. FG AN stud-
tion, and controller. The AI/ML sandbox is com- ies the autonomy of various processes or network
posed of an AI/ML pipeline for the purpose of aspects, such as planning, security, audits, invento-
training AI/ML models by using the data obtained ry, optimization, orchestration, and quality of expe-
from the simulated AI/ML underlay network. The rience. The group studies the various approaches
reader is referred to [10] for a detailed descrip- of exploratory evolution, emergent behavior, and
tion of these functional groups and interfaces. real-time responsive experimentations that can
Similarly, ITU-T Recommendation Y.3178 spec- provide a new layer of abstraction for introducing
ifies a functional framework for AI-based network evolution mechanisms leading to the realization
service provisioning. It starts with a description of of autonomous networks. The group also tries to
the business-role-based model for AI-based net- address the questions associated with accountabil-
work service provisioning, then provides a list of ity for non-human decisions that affect customers
high-level requirements for the roles and their inter- and explore the approaches of exploratory evolu-
actions from an AI-based operational perspective, tion, emergent behavior, and real-time responsive
as well as the functional framework showing the experimentation to enable an autonomous net-
components and their interactions for AI-based work.
operations for network service provisioning. Over the course of a one-year period, FG AN
has planned to produce deliverables defining the
Focus Group on Autonomous Networks characteristics, use cases, requirements, proofs of
ITU-T SG13 established the Focus Group on concepts, high-level architecture, standardization
Autonomous Networks (FG AN) [11] in December gap analysis, specification languages, and repre-
2020 to provide an open platform for conducting sentations of autonomous networks.
FIGURe 2. High-level architecture of AI/ML-based network automation for resource and fault management.
ETSI EXperiential
Networked Intelligence
ETSI’s Experiential Networked Intelligence Indus-
try Specification Group (ENI ISG) is targeting
the development of efficient and extensible
standards-based mechanisms to provide con-
text-aware services. It has specified an experiential
architecture that uses AI/ML and other mecha-
nisms to improve its understanding of the network
environment, and thus the operator experience,
over time. It can adapt its functionality based on
contextual changes in user requirements, network
conditions, and business goals [14].
FIGURe 3. General framework of 3GPP 5G network automation using Figure 4 shows the ETSI ENI system architecture,
network data analytics function. which consists of three modules: the input process-
ing module, analysis module, and output generation
AI/ML Network module. The figure also shows the API broker; how-
ever, the ENI system can function with or without
Standardization in Other SDOs the API broker. The API broker serves as a gateway
This section presents a review of network-automa- between different systems. It possesses the transla-
tion-related activities of 3GPP and ETSI. tion mechanisms to translate data communicated
from the external system into a normalized form that
3GPP Network Automation for 5G all ENI functional blocks can understand, as well as
3GPP has defined the network data analytics func- translate recommendations and commands from
tion (NWDAF) in the 5G service-based architecture the normalized form of the ENI system to a form
(SBA) as the enabler of intelligence and autono- that the external system can understand. Thus, it
mous network operation and management. The enables heterogeneous types of external systems
NWDAF collects data from various modules of the such as infrastructure, applications, and users to
5G system and provides analysis results. interoperate with the ENI system.
3GPP TR 23.791 specifies a general frame- The input processing and normalization mod-
work for 5G network automation [12]. As shown ule possesses data ingestion and normalization
in Fig. 3, the NWDAF collects data from the oper- functional blocks to process the input data such
ation, administration, and maintenance (OAM) that the other functional blocks in an ENI system
module, application functions (AFs), 5G core can interpret and understand the data in a unified
network functions (NFs), and data repositories. and consistent manner.
In addition, 3GPP TS 23.288 specifies the refer- The analysis module includes context-aware,
ence architecture and detailed procedures for knowledge management, cognitive processing,
data analytics [13]. It also provides a description situation-aware, model-driven, and policy manage-
of NWDAF discovery and selection by NFs/AFs, ment functional blocks. The context-aware func-
network performance analytics, and user data tional block describes the state and environment
congestion analytics. in which a set of entities in the controlled or assist-
NWDAF analyzes the data by leveraging AI/ ed system (i.e., the system being assisted and/or
ML models. The analytic results are then delivered controlled by the ENI system) exist. The context
to the NFs/AFs that have requested the NWDAF. consists of measured and inferred knowledge that
The NFs/AFs utilize analytical output data to make may change over time. The knowledge manage-
appropriate decisions for network operation and ment functional block includes the mechanisms for
management actions. NWDAF utilizes existing 5G knowledge representation, inference, and reason-
service-based interfaces to collect data from NFs/ ing to represent information about both the ENI
AFs and OAM, as well as deliver analytical output system and the controlled external system.
data to them. The cognition processing functional block
Because the input data of the NWDAF may includes a mechanism to understand normalized
come from multiple sources, such as mobility ingested data and information, as well as the con-
management, session management, QoS man- text that defines how those data were produced.
agement, application layer, security management, Based on data interpretation results, it determines
and NF life cycle management, the resulting whether any action needs to be taken to ensure
actions that an NF or AF takes according to the that the goals and objectives (e.g., improving or
optimizing the performance, reliability, and/or The ENI architecture can be applied to var-
availability) of the ENI system have been met. ious aspects of network management, such as
The situation awareness functional block includes infrastructure management, network operation,
a mechanism to enable the ENI system to be service orchestration, and the management of
aware of events and behaviors that are relevant numerous use cases.
to the controlled system. It has the capacity to
understand how information, events, and recom- ETSI Zero Touch Network and
mendation commands given by the ENI system Service Management
impact the management and operational goals ETSI ISG Zero Touch Network and Service Man-
and behavior in the short and long terms. agement (ZSM) specifies the architecture, function-
The model-driven engineering functional block al, and operational requirements for E2E networks,
contains a set of models that collectively abstract and service automation based on the closed-loop
all important concepts for managing the control control and integration of AI/ML techniques. The
system governed by the ENI system. The policy ZSM architecture aims to address the challenges of
management functional block provides a set of technological and managerial heterogeneity in E2E
rules to manage the system in such a way that the cross-domain network management by defining
system goals and objectives are met. a holistic management framework that can reuse
Similarly, the denormalization functional block the management capabilities available in various
of the denormalization and output generation standard technologies. It follows the principles of
module includes mechanisms to process and modularity, extensibility, scalability, model-driven
translate policies, recommendations, and data open interfaces, closed-loop management automa-
received from other functional blocks of the ENI tion, support of stateless management functions,
system into an intermediate form that can be sub- resilience, intent-driven interfaces, and simplicity,
sequently translated or transcoded by the output among others [15].
generation functional block into a form that the Figure 5 shows the ETSI ZSM reference archi-
controlled systems are able to understand and tecture, which is composed of a two-layer hier-
use. If an API broker exists, the output is sent to archical structure of management domains. In
the API broker; otherwise, it is sent directly to the the lower layer, there are multiple management
controlled system. domains (MDs), each of which is responsible for
The ENI system architecture was designed managing a domain-managed infrastructure; in
based on the key assumption that the ENI system the upper layer, this is an end-to-end (E2E) ser-
functionality evolves over time to meet emerging vice management domain, which orchestrates the
functional requirements such as network and ser- management services provided by individual man-
vice planning requirements, service provisioning, agement domains to realize E2E cross-domain
deployment, optimization, data collection, model- management. Both the individual and E2E man-
ing, analysis, policy specifications, interoperability agement domains expose a set of management
with other systems, non-functional requirements services that they provide.
of system performance (latency, accuracy, and Management domain services can be cate-
efficiency), and scalability, among other factors. gorized into the following groups. Domain data
works formed by the convergence of network- tion in each management domain is required to
ing and cloud/edge computing infrastructures is expose only the relevant information in the stan-
challenging due to the involvement of different dard form and size.
technologies and administrative domains, such Scalability of Telemetry Data Collection: For
as the domains of mobile operators, edge-com- intelligent and autonomous E2E network and
puting service providers, core network operators, service management, the existence of standard
and cloud-computing service providers. Each of technology for agile monitoring and control of all
these domains may employ different types of net- involved network functions is essential. The moni-
work resource management mechanisms. In a toring and control functions include a process for
multi-vendor E2E communication service deliv- network telemetry data collection, which needs
ery environment, each vendor network may have to be efficient to avoid incurring a high overhead
its own operation and business support system hampering network performance and delaying
(OSS/BSS) with different control interfaces, the execution of control commands. The intelli-
resource virtualization and SDN technologies, gent and autonomous telemetry data collection
AI/ML techniques, and models. To address this may require attaching an AI/ML process to each
issue, the 5G service-based architecture of 3GPP network function to carry out optimal decisions
applies SBI between the NWDAF and other net- regarding the right amount and time of telemetry
work functions; in addition, ZSM has an E2E ser- data collection to ensure the efficiency and scal-
vice management domain, ENI has an API broker, ability of the overall system.
and the ML network architecture of ITU-T has an Data Models: Standard data models are essen-
MLFO. However, they lack detailed specifications tial for sharing cross-domain control data for the
for the design and implementation of an easy-to- realization of autonomous E2E networks and ser-
deploy multi-domain management mechanism vice management. Cross-domain data services in
that autonomously re-composes and reconfigures the ZSM reference architecture and data handling
itself to provide near-optimal performance for framework in ITU-T Y.3174 have been defined
different types of network services. For example, and specified at the conceptual level. The ZSM
the standard representations of ML models, man- framework architecture also provides definitions
aged resources, and management methods to be and requirements for data collection, data stor-
used in each management domain have yet to be age, data persistence, and data processing ser-
defined. Only after having standardized represen- vices. However, they lack detailed specifications
tations can these entities be orchestrated from the of data models that can be followed to implement
overlay E2E service management domain. scalable mechanisms for efficiently exchanging rel-
Abstraction of Hierarchical Management evant data across multiple management domains.
Layers: Hierarchical management layers have AI/ML Pipelining: To realize scalable E2E net-
been proposed for E2E network and service work management, there must be a mechanism
management (e.g., the ZSM architecture con- for collaboration between the AI/ML models
tains open interfaces, model-driven services, used within the same local management domain
and resource abstraction). However, they lack as well as across different management domains.
detailed specifications of interfaces that can The ML pipelining concept has been mentioned
be followed to implement mechanisms for the in the ITU-T ML architecture [9]. Similarly, the
exchange of management capabilities and relat- ZSM framework’s hierarchical management struc-
ed data among multiple management domains. ture also assumes the existence of domain-specif-
Moreover, because the volume of management ic ML or data analytics models [15]. However, the
data produced in each management domain is detailed design of management architecture that
extremely large, an appropriate level of abstrac- can fully leverage AI/ML capabilities for cross-do-