Network automation: 

the journey
to zero-touch
A guide to automating and orchestrating
5G networks and services

October 2020
2 Ericsson  |  Network automation: the journey to zero-touch

5G is designed to be orchestrated

To achieve the full potential of 5G, your network must allow you,
your customers and partners to use the network innovatively.

Imagine building an agile network, where
services can be introduced, managed,
scaled and terminated in a fast and
efficient way – to cut operational costs
and increase revenues. Automation
and orchestration will build that agility
into your operations and network.
To meet the modern business
challenges and provide a diverse range of
services, the 5G environment is expected to
be more complex than earlier generations.
The designers of 5G expect this to be
solved by orchestration. Therefore,
management and orchestration functions
become an integral part of 5G architecture.
Why automation and orchestration
are vital to 5G characteristics
Cloud native resource orchestration
5G NFs are expected to be deployed
in a virtual and, ideally, cloud native
environment, to run in the most optimized
way. However, handling those functions
manually will be unmanageable due to
their complexity. The reduction of manual
tasks not only decreases complexity,
but it also reduces operational costs.
Slice orchestration
5G supports network slicing to create
partitions with specific characteristics
to suit various applications, business
areas or customers. Managing a few
slices manually is possible; however,
ensuring SLAs are met for a large number
of network slices requires orchestration.
Edge sites
5G enables network and application
functions to be close to the end user,
in “edge” data centers. The much greater
number of such facilities, compared to
traditional, centralized data centers,
requires the ability to easily manage
this distributed resource landscape.
API exposure
The 5G standard network exposure
function (NEF) exposes APIs,
allowing application-specific network
control. This enables services to be
composed seamlessly in real time.
Firstly, the network APIs are used
by a higher-level service orchestration
layer that provides features to
partners, such as specific service
characteristics. Secondly, the APIs can
be directly available. This also requires
orchestration to manage API access.
The packaging and bundling of such
value-added network features must
be managed through orchestration to
provide meaningful services to customers
and partners. This means that all the
underlying systems and networks must
be ready to contribute fully automated
functions that support those APIs.
Self-order services
In terms of digital enablement,
customers now demand online channels
that complement traditional sales
channels. It takes more than a website
to enable digital interactions.
To achieve service order automation,
the underlying layers of systems must
be integrated from the top to the bottom
of the stack – from customer-facing
interactions to networks. Automated
design templates and rules that can
translate intent-based customer orders
into network capabilities are needed.
Furthermore, virtualization means
that order provisioning can go far
beyond the simple configuration of
network elements; whole topologies
of network functions (NFs) can be
instantiated in optimally chosen sites
to meet specific customer needs, such
as low latency or high resilience.

Management and orchestration functions are an integral part of 5G architecture

3 Ericsson  |  Network automation: the journey to zero-touch
Figure 1: Ericsson Dynamic Orchestration automation flow
Service creation
Design time
Design
Domains Core network Transport
Network and service automation
In its purest form, the service represents
the outcome to the consumer, independent
of how the CSP chooses to deliver
it. The CSP will secure the service
outcome by constantly optimizing the
network resources.
Therefore, a key responsibility of
orchestration is to compose resources into
topological structures, including network
slices, software-defined networking,
Network Functions Virtualization (NFV)
services and NFs (virtual and cloud
native), to meet the service intent.
The traditional way to do this is via
manual and automated processes. This is
a simple concept, but it becomes complex
when all events impacting a service are
considered; each event or lifecycle step
like scale in-out has to be considered in
Composite Orchestrator
Order automation
Service and Resource Orchestration
Continuous Deployment and Delivery (CI/CD)
Run time
Deploy
End-to-end, cross-domain automation
RAN Edge
the scripts. This becomes unmanageable
when multiplied by extra complexity of
virtual infrastructure and network slicing.
This led to the concept of “infrastructure
as code”, where the desired topology
is explicitly defined in a declarative
language, such as TOSCA, rather than
being implicit as the result of a series
of steps. This creates the role of the
orchestrator to calculate and execute
appropriate steps, resulting in the correct
network topology.
A further job of the orchestration
solution is to ensure that service intent
is maintained, even as circumstances
change, including network faults,
increased service consumption, congestion
of shared resources and opportunities to
optimize how the service is delivered.
Service Assurance
Service Assurance and Analytics
Operate
SD-WAN Others
This requires an ongoing closed-loop
approach. By monitoring the service and
underlying network, events and threshold
violations can be detected to trigger
decisions based on defined policies, to
adjust or redesign the network to continue
to meet the required service levels.
It is also important to monitor the
effectiveness of the policies. Simply scaling
out an NF might be ineffective if it places
more load on the transport network.
Where the service is dependent on
multiple network domains, some or all of
those domains may need to be managed in
tandem to achieve the required outcome.
At some point, the orchestrator might
need to structurally redesign the topology;
for example, to relocate an NF closer to the
source of the traffic.
4 Ericsson  |  Network automation: the journey to zero-touch

Figure 2: CI/CD loop with continuous releases

Analysis and Initial

design deployment

Repository
1 2 3
Continuous Software Software
releases distribution upgrade
0

7 8 9
Acceptance
tests
Vendor Customer 10 4

12 11

Feedback Data
collection

6 5

The importance of Continuous
Integration/Continuous Delivery (CI/CD)
Automating software delivery with
CI/CD, also known as DevOps, will
greatly decrease the time to market.
CI/CD relies on the ability to define
infrastructure as code, where the network
topology and configuration are represented
so they can be repeatedly deployed and
tested. Orchestration provides a complete
toolset for defining and managing
infrastructure and service definitions.
Languages, such as TOSCA, declaratively
represent the network topology and the
orchestrator works out the optimal way
to instantiate the service.
This contrasts with script-based or
robotic approaches where the network
topology is defined as a by-product of
the process or script. If the preferred
composition of the infrastructure or
services changes, the scripts must be
analyzed to determine how to create
the new structure.
Virtual infrastructure can be
instantiated via ETSI management and
orchestration (MANO) architecture to
create network services comprised of VNFs.
Service orchestration generates complex
multi‑domain services and performs
application configuration according to
customer needs.
With these tools, infrastructure and
services can be repeatedly instantiated,
which is ideal for continuous integration
testing. Using orchestration with VNF
validation and testing tools allows an
automated verification pipeline to be
established, vastly reducing the effort
to onboard new NFs and retest new
versions of existing ones. This automation
is not simply a cost-saving; it enables a
more rapid path from development to
deployment, bringing forward time to
market by months in many cases.
Therefore, orchestration should be the
primary means of automating instantiation
of network and service constructs.
Specific process requirements can be
defined as custom scripts, executed by
the orchestrator as part of its overall
framework. The template-based approach
enforces modularity and enables ongoing
enhancement with a much lower risk of
problems. Orchestration can be embedded
into CI/CD processes to enable NF
and service template validation before
deployment in production environments,
while simultaneously keeping a rapid path
from innovation to monetization.

CI/CD relies on the ability to define infrastructure as code

5 Ericsson  |  Network automation: the journey to zero-touch

Enabling transformation
through orchestration

Most CSPs are under market pressure to respond with initiatives

at all levels, including product definition, customer interaction,
operations automation and network capabilities.

Network evolution and digital
transformation are happening in parallel.
Orchestration is a key enabler of these
initiatives, as well as 5G (including network
slicing), which underpins other initiatives.
Figure 3 illustrates typical NFV, 5G and
business initiatives currently occurring in
large CSPs.
In this complex environment, there is
no one-size-fits-all migration path to 5G
and orchestration. However, it is worth
keeping in mind a few principles that lead
to successful transformations:
1. Execute each step in an initiative as a
minimal viable product. Do not introduce
unnecessary features and scope creep
until there is a clear need. Avoid issuing
request for proposals (RFPs) that have
everything included. Conversely, expect
each initiative to be followed by a
maturation phase, where capabilities
evolve based on learnings from
earlier deployments.
2. Each step should have its own business
case. This provides the impetus to
complete the work in a meaningful way.
Keep in mind that the business benefits
may occur indirectly through other
initiatives, such as the ability to compose
high-value products, enabled by
network slicing.
3. Have clear governance. This may
consist of a dedicated program team
with a larger virtual team comprised of
stakeholders from various line business
units. The team must encompass the
full pathway to deliver the benefits
described above.

Figure 3: Large CSPs’ current NFV, 5G and business initiatives

Digital telco

Product and service composition

CI/CD

Automation

Resource orchestration

Single-domain network slicing Multi-domain network slicing

Closed-loop assurance

Network exposure

5G Core (SA)

5G EPC (NSA)

5G RAN

NFVI Cloud native

Transport modernization
6 Ericsson  |  Network automation: the journey to zero-touch

Automate and orchestrate with

Ericsson Dynamic Orchestration

We can be with you every step of

your network automation journey.

The Ericsson Dynamic Orchestration Figure 4: The high-level benefits of Ericsson Dynamic Orchestration
suite combines world-leading products
to create a complete solution for 5G
network orchestration. VNF of choice Multi-vendor, multi‑domain
The components of Dynamic 100-plus orchestrator and Proven deployments of 200-plus
Orchestration provide a complete solution VNFM references. Ranked #1 VNFs on all cloud environments.
and combine harmoniously, but can also by leading analysts.
be substituted with equivalent systems.
Dynamic Orchestration is inherently
Open and standard compliant Intent-driven design
multi‑technology and vendor‑agnostic,
No vendor lock‑in. Open interfaces: Agility and flexibility through
reflecting the reality of telecom
ETSI MANO, TMF, 3GPP and intent‑driven orchestration.
environments and the need for
ONAP alignment.
innovation and differentiation.

The automation journey Distributed cloud DevOps and CD

This section introduces the automation
and orchestration journey, in a sequence
that builds up from basic capabilities to
full network slicing automation, including
closed-loop assurance. Of course, this
sequence can be adapted depending
on business needs.
For the full Dynamic Orchestration
portfolio and its capabilities, visit
ericsson.com/dynamic-orchestration
Single orchestrator for physical, VM and
container workloads across private,
Edge and public cloud.
Closed-loop assurance
Intent-driven, closed-loop automation,
ML-driven anomaly detection and
RC analysis.
A fully automated DevOps pipeline,
from the latest software drop to
production network.
New revenue opportunities
New revenue through private LTE/5G
distributed cloud, SD-WAN and
hyperscale cloud.

NFV orchestration, as well as service orchestration, assurance and analytics, are crucial to evolving orchestration capabilities
 7 Ericsson  |  Network automation: the journey to zero-touch

Figure 5: OSS 5GC capabilities, scenarios and evolution

Analytics-driven
Expert Analytics
CX insights
Cross-layer CENX Service
visualization Assurance
Policy
Network slice Framework
orchestration Service
Orchestration
Capabilities

NW service Cloud Manager

orchestration (NFVO)
Resource
CDD
orchestration
VNF/CNF
Evolved VNFM
management
Dynamic
Service activation
Activation
Network and perf.
Network IQ
management
Network
Multi-domain VNF/CNF Customer
management, Resource Network slice Closed-loop
service lifecycle experience
assurance orchestration automation service assurance
activation automation management
and analytics

Implementation scenarios

The Ericsson Dynamic Orchestration
solution enables a step-by-step journey
to complete zero-touch automation and
assurance. As Figure 5 shows, the product
suite builds up from simple NF lifecycle
automation to complete management of
complex network slices and services.
Network IQ
Ericsson Network IQ enables 5G Core
observability to ensure adherence to
KPIs. It collects and processes data for
performance reporting, resource planning
and service assurance, to increase and
enhance your network assets.
Dynamic Activation
Ericsson Dynamic Activation is a
proven provisioning platform for
the rapid and automated activation
of telecommunications services in
heterogeneous network environments.
It provides high availability, resilience and
the scalability to handle high-throughput
service activations.
Evolved VNFM
Ericsson Orchestrator’s Evolved VNF
Manager provides a single solution for
lifecycle management of VM-based
and cloud native NFs across many VIM
and container platforms. Support for
ETSI standards enables interoperability
with third-party packages and
MANO environments.
Cloud Deployment Engine
Ericsson Cloud Deployment Engine
supports the rapid creation of new services
using CI/CD. Cloud Deployment Engine
enables automated onboarding and
verification of third‑party NFs, end-to-end
service design and automated testing.
These services are then transferred to the
catalog for deployment.
NFV orchestration
Ericsson Orchestrator’s NFVO enables
orchestration of your resources across
different VIMs (OpenStack, VMware or
AWS) and Kubernetes, both intra‑ and
inter-data center. Ericsson Orchestrator
automates the deployment or instantiation
of network services, managing specific
and generic VNF managers to enable
lifecycle management of NFs from
multiple vendors.
Service Orchestration
Ericsson Orchestrator’s Service
Orchestration provides network slice
management, including LCM and
configuration by using TOSCA as
the template language. It enables
cross‑domain orchestration across access,
transport and core networks. It interfaces
with multiple domain managers and
third‑party SDN controllers, and provides
multi-vendor support with both standard
and customizable adaptors.
CENX Service Assurance
Ericsson’s CENX Service Assurance
provides multi-layer visibility of network
status, faults and performance, which
can be used for assurance of network
slicing scenarios, if required. Closed‑loop
assurance enables network issues to
be resolved automatically through
policy-driven actions – cloud native
dynamic assurance.
Expert Analytics
Ericsson Expert Analytics offers near
real‑time, multivendor and cross-domain,
big data analytics capabilities tailored
to CSPs.
Exposure
Ericsson’s Core Network Exposure
solutions provide standardized APIs
to expose key 4G and 5G core network
capabilities to ecosystem partners.
Our offerings support a variety of use
cases to drive business in massive IoT,
broadband IoT, critical IoT, industrial
IoT and enhanced mobile broadband
segments. Ericsson Cloud Core Exposure
Server is a cloud native core NEF in
Ericsson’s dual‑mode 5G Core offering,
based on standard APIs for both 4G and
5G networks (catered to by 3GPP NEF and
SCEF standards), with extra capabilities
for device management, device
communication and security.
8 Ericsson  |  Network automation: the journey to zero-touch
Standards and the role of open source
Standards are vital to the telecoms ecosystem, defining a common
architecture and enabling interoperability for a vibrant market
of compatible products.
Stick to standards
3GPP’s 5G standards expect the core
NFs to be virtualized according to NFV
principles. Because this environment
has been successfully standardized by
ETSI, 3GPP concentrates on network
functionality and has mapped out
the existing ETSI NFV standards for
managing virtualization.
The 5G network slicing standard
defines multiple layers that integrate with
the surrounding management systems
at different levels. The top layer is the
Communications Service, which defines
the service provided to the consumer
and, therefore, represents the service
intent. This allows integration into service
fulfillment functions in the operations
support systems (OSS).
Traditionally, this service management
layer, as well as its relationship to
commercial products and customers, has
been defined by the TM Forum’s standard
Frameworx and, more recently, the
ODA. The TM Forum is now developing
principles for aligning its standards
with 5G, captured in papers, including
the IG1211 ODA 5G Management
Implementation Guidelines.
The high capacity of 5G networks
places unprecedented demands on the
transport network, for both fronthaul
(radio unit to baseband unit) and backhaul
(baseband unit to core nodes). Network
slices require separated traffic with specific
quality of service to support the overall
service intent. Therefore, orchestration
needs the means to provision logical
services from the transport domain.
Several bodies have produced standards
in this space, including the IETF (Layer-3
and Layer-2 service models and ACTN)
and MEF.
The role of open source Standardization bodies
Although NFV and 5G standards do not
mandate its use, in practice large parts
of the virtualization and cloud native
stack consist of open-source software.
This includes hypervisors (KVM and
QEMU), VIM (OpenStack), cloud native
container platform (Docker) and manager
(Kubernetes), and SDN controller
(OpenDaylight).
Open-source platforms have been
developed for service orchestration
(ONAP) and NFV orchestration Open source fora
(OSM and, again, ONAP).
The ease in which open-source
software can be composed into working
systems, or built upon to develop new
applications, means that it plays a key
role in IT and communications industry
innovation. Commercial organizations
contribute to open source because the
innovation provided by the community
outweighs the benefits of controlling
a proprietary platform.
Nevertheless, open-source software Industry alliances
is no different from any other software, in
that it takes coordination and resources to
prepare well-validated, production‑ready
systems comprised of a multitude of
components, and to support them in
critical real-life use. For this reason,
most large-scale consumption of open
source software is via commercial
software companies. The fact that the
base software is freely available, and the
similarity of implementations, allows low
switching costs, which then avoids lock-in
to proprietary solutions.
9 Ericsson  |  Network automation: the journey to zero-touch
Recap, the CSP
journey toward 5G
5G was designed
to be orchestrated.
We have seen how 5G enables a range
of new applications and higher‑value
revenue opportunities. Orchestration
fulfills this promise by greatly shortening
the process of releasing new products, and
instantiating and managing network slices.
CSPs are simultaneously moving
to digital customer and partner
interactions, through real‑time,
multi‑channel enablement and API
exposure, implementing CI/CD to slash
the time from innovation to release, and
automating various processes to reduce
operational costs.
In this context, it is important to
treat 5G as a driving force rather than
a distraction. 5G was designed to be
We recommend that 5G automation is treated as an early use case and aligned with other transformation programs
orchestrated, so it is a natural starting point
for such initiatives. We recommend that
5G automation is treated as an early use
case and aligned with other transformation
programs. 5G-related concepts, such as
network slicing, may prove to be a better
solution than other retrofitted approaches.
To keep TCO low, make sure you choose
an orchestration vendor that is building on
open source and industry standards that
understand telco requirements, and keeps
operations together.
Wherever you are in your automation
and orchestration evolution journey, we
can guide you through implementation,
building for today’s network and planning
for future innovation.

Ericsson
SE-164 80 Stockholm, Sweden
Telephone +46 10 719 0000
www.ericsson.com
Ericsson enables communications service providers
to capture the full value of connectivity. The company’s
portfolio spans Networks, Digital Services, Managed
Services, and Emerging Business and is designed to
help our customers go digital, increase efficiency and
find new revenue streams. Ericsson’s investments in
innovation have delivered the benefits of telephony
and mobile broadband to billions of people around
the world. The Ericsson stock is listed on Nasdaq
Stockholm and on Nasdaq New York.
www.ericsson.com
The content of this document is subject to 1/287 01-FGB 101 0907
revision without notice due to continued © Ericsson 2020
progress in methodology, design and
manufacturing. Ericsson shall have no
liability for any error or damage of any kind
resulting from the use of this document