Cloud native

subscriptionand data
management in 5G
A guide to mastering data and subscriber
handling in multi-access core networks

December 2020
2 Ericsson  |  Cloud native subscription and data management in 5G

Introduction

The new 5G paradigm is transforming

the core network data layer.

The introduction of 5G signals the It will also achieve improved total cost of will enable advanced capabilities such
start of a new era for communications ownership (TCO)1, and higher availability as network slicing and edge computing,
service providers (CSPs), where and security for critical services. and take a significant step forward in
both networks and businesses are However, the 5GC network will network automation, analytics and
evolving and expanding, offering co‑exist and work alongside existing exposure. In parallel, they can make
CSPs a real opportunity to grow 4G Evolved Packet Core (EPC) networks networks more efficient and easier to
revenue and capture more value. for years to come. Many of these EPC operate, significantly reducing the TTM
5G represents a paradigm shift, networks are in the middle of (or yet to for new services with a shorter lifespan.
where the telecom industry is now taking start) their evolution towards network When planning the evolution to a 5GC
substantial steps towards using the same functions virtualization (NFV). This network, it’s easy to look at it as just a
building blocks as the IT industry. The will lead to a hybrid network scenario single “chunk” of the core network, but in
5G Core (5GC) standalone (SA) has a new that CSPs will need to operate with reality, the 5GC contains diverse domains,
Service‑Based Architecture (SBA), which throughout their migration to 5G, such as: user plane, packet core control
is based on IT principles and designed offering multiple challenges for plane, subscription data management
for cloud native implementation. The achieving operational efficiency, but also (SDM) control plane, data layer, policy
SBA is centered around services that can bringing new business opportunities. control and network exposure. Each of
register themselves and subscribe to other When building these new core these domains will play its own vital role in
services. It provides increased robustness, networks for 5G, CSPs must transform the overall core network, ensuring 5G use
scalability, and availability, as well as an their networks by adopting new cases reach their full potential – each with
improved level of security in comparison to connectivity options to deliver lower their own challenges, solutions and paths
today’s mobile core network architecture. latency and higher peak rates, as well to follow on the 5G evolutionary journey.
This new cloud native 5GC is necessary as new interfaces, architecture and In this guide, we will focus on the
to meet market demands, in the form of software deployment models, such as SDM control plane and data layer
new and distributed capabilities, and to continuous integration and delivery. evolution into cloud native Subscription
deliver a faster time to market (TTM). Leveraging on those elements, CSPs and Data Management (cnSDM).

Figure 1: CSPs’ challenges on the path to 5G

Decrease cost per Improve operational Simplify network

bit/connection efficiency architecture
Capex
optimization

Dual-mode
EPC
5G Core Opex
reduction

Secure a smooth Protect the Find new growth

and safe evolution network and monetize Revenue
network assets protection and
increase

|1 2020-02-12 | Ericsson Internal | Page 1

To learn more, read our paper Dual‑mode 5G Core: TCO benefits
3 Ericsson  |  Cloud native subscription and data management in 5G

Figure 2: The role of evolved SDM in 5GC architecture

5G network function EPC network function

Cloud Core Data-Storage Manager

Data
Layer UDR
UDSF DATA LAYER
Cloud
native
SDM Cloud Core Resource Cloud Core Cloud Core Cloud Core
SDM
Controller Subscription Manager Policy Controller Exposure Server
Control
Plane NSSF NRF UDM AUSF PCF NEF
EPC NSSF HSS 5G-EIR PCRF SCEF

SBA architecture
Packet Core Controller Signaling Controller

TDF-U AMF SMF SEPP BSF

MME SGW-C PGW-C DRA* SCP
CONTROL PLANE

Packet Core Gateway

NR SA
LTE/NR NSA TDF-U UPF SGW-U
LTE
GSM/WCDMA PGW-U
USER PLANE

* DA and DEA functions also supported

The 5G network creates new needs in control plane, driven by different service handled in mobile networks will change
terms of both the variety of data which options consumed by multiple types significantly in the coming years. 2G/3G
can be stored and managed in the of devices, across many sub‑network services will drastically decline; 4G services
core network, and new use cases to be domains – each with a specific business will continue to have a dominant role;
handled for subscriber authentication and need. Finally, this cnSDM solution should and 5G services will grow faster than
service authorization across the different support different deployment options, previous technology shifts (predicted
network domains. As a consequence, in order to efficiently serve network to grow to 3.5 billion in 20262) .
traditional SDM domains need to step slicing and edge computing use cases. This new business scenario makes
forward, implementing new solutions. The increased capability requirements the evolution of current SDM domains
They should have the ability to handle a for SDM to support the new 5G paradigm towards a cloud native unified data
wider number of data types in a unified should be complemented with a higher storage and subscription management
way, and make them available where level of flexibility, and able to handle the engine essential. The new cnSDM
needed, when needed, and with the right subscription’s shift from legacy service solution is a cornerstone of the required
level of accesses, speed and security. domains into a single hybrid domain evolution in SDM, providing higher
The cnSDM in 5G must also handle in a cost‑efficient way. As illustrated efficiency, robustness and flexibility
the increased complexity in the SDM in Figure 3, the mix of subscriptions into the evolved SDM of 5GC networks.

Figure 3: Subscriptions shift from legacy to 5G

10
CSPs need to evolve their current
8.8 data layer solutions towards a more
billion
9 flexible model, based on cnSDM, to
7.9
billion ensure the proper level of network
8 simplification, operational efficiency
and smooth and secure transition to
7
the new 5G paradigm.
6

5 5G
LTE (4G)
4 WCDMA/HSPA (3G)
GSM/EDGE-only (2G)
3
TD-SCDMA (3G)

2 CDMA-only (2G/3G)

1 Note: IoT connections are

not included in this graph. Fixed wireless
access (FWA) connections are included.
0
2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026

2
Ericsson Mobility Report, November 2020
4 Ericsson  |  Cloud native subscription and data management in 5G

Data layer challenges

in the evolution to 5G

Evolving to a cnSDM solution addresses new challenges

from 5G and tackles old challenges in the SDM domain.

SDM solutions have evolved, moving • one single engine for key subscription Securing a smooth,
from a monolithic to a data‑layered management tasks, like authentication safe evolution to 5G with:
architecture, and from physical into and mobility management, to • an easy, safe and cost‑efficient
virtualized deployment. With cnSDM, we reduce the overall signaling and migration of subscription data
enter the third stage of evolution, into an simplify procedures from legacy databases towards the
SBA based on cloud native deployment. • optimized capacity for the new 5G domain, to avoid long and
This third stage has introduced a different application FEs, avoiding expensive projects
flexible SDM, where unified data storage over‑dimensioning driven by a variable • a tight and standard interworking
and centralized subscription management traffic mix between different application FEs
services are split – thanks to the dataless • flexibility in the allocation of data from different domains to secure full
application Front Ends (FEs) – and fully storage resources, to address different voice/data/SMS service continuity
connected to the rest of the network needs in terms of data sharing and during the transition to 5G
entities through open and standard data distribution • open and standard interfaces
Service‑Based Interfaces (SBI). Both are (REST based) between Back Ends (BEs)
shared across multiple network domains Improving operational efficiency with: and FEs and towards other network
and slices, covering many types of data • easy access to the data stored in the functions/systems to support a full
(structured, unstructured, subscription, common repository, enabled by SBA for multi‑vendor environment
application, network configuration, session external exposure and analytics
and exposure); multiple types of devices • a full separation between data Protecting the network with:
(SIM and non‑SIM based); and multiple storage and application business • advanced security and authentication
types of access (2G/3G/4G/5GNSA/5GSA) logic, for independent life cycle and mechanisms to protect end users and
as part of the same cnSDM domain. performance management networks from malicious attacks and
The new cnSDM addresses the typical • one common point for data provisioning, unauthorized intrusions
CSP challenges in this specific segment reducing risks for data duplication and • end‑to‑end (E2E) solution mechanisms
of the industry. inconsistencies, and avoiding multiple to secure SDM service continuity
provisioning platforms with complex under unexpected signaling
Simplifying the network integration projects overload situations
architecture with: • tools and procedures to automate • greater availability and robustness of
• one common data repository for software Life Cycle Management (LCM) data storage resources, mitigating the
multiple types of network data related to procedures and to reduce the effort risk of loss or damage to network data
different applications, to avoid multiple required to integrate, configure and
databases in different network silos, manage the SDM network functions
with varying technologies and data
access interfaces Figure 4: The evolutionary journey towards cnSDM

SBA

Monolithic Layered architecture

architecture
CaaS

IaaS IaaS

HW HW HW HW HW HW

2G/3G 4G/IMS 2G/3G 4G/IMS IoT 2G/3G/4G/5G/IMS/IoT

Virtualized User Data Consolidation Cloud Native Subscription and

Physical HLR/HSS
(vUDC) Data Management (cnSDM)
5 Ericsson  |  Cloud native subscription and data management in 5G

Figure 5: Outlining the main challenges in the SDM evolution and how the different solutions address them

Physical HLR/HSS Virtualized UDC (Data Cloud native SDM

Challenges in SDM evolution
(Monolithic arch.) Layered arch.) (Service based arch.)
Unified data repository

Centralized subscription management

Optimized allocation of FE and BE resources

Easy data access

Independent scalability between FE and BE

One common provisioning

Automated SW LCM

Automated Sub. Data migration

Cross domains interworking

Multivendor support

Network security

Overload protection

Data protection

Unified data repository: Automated software LCM: Network security:

mainly addressed in the Data Layered already addressed in DLA with already present in DLA but further
Architecture (DLA) with some limitation virtualization and continuous enhanced in cnSDM, with new
for consolidation of unstructured data integration/continuous deployment standardized mechanisms to encrypt
and for synchronization of the same (CI/CD). Cloud native will bring significant sensitive end‑user data when transferred
data across different domains. further enhancements. in the network.

Centralized subscription management: One common provisioning: Overload protection:

partially addressed in both monolithic and mainly addressed in DLA with some already addressed in DLA via proprietary
DLA, with some proprietary solutions for limitations for unstructured data. solutions. In cnSDM, we will support
common authentication vector generation. standardized mechanisms for this.
Automated subscription data migration:
Optimized allocation of not addressed at all in DLA, as before Data protection:
FE and BE resources: with human‑driven migration projects. already addressed in DLA with many
partially addressed in DLA with the ability A minimum level of automation was only standard and proprietary mechanisms.
to dedicate FE resources to a specific achieved with tailored migration services. Cloud native brings further enhancements
network domain in a static way. with auto‑healing.
Cross‑domains interworking:
Easy data access: already present in DLA, but without a
partially addressed in DLA with complete standardization of interfaces for
proprietary solutions and sometimes interworking between multivendor FE.
with costly integration projects towards
external applications. Multivendor support:
not addressed in DLA because it is based
Independent scalability on Lightweight Directory Access Protocol
between FE and BE: (LDAP) without standardized data model.
mainly addressed in DLA with some
limitation for application FE using
unstructured data.
6 Ericsson  |  Cloud native subscription and data management in 5G

The key role of cloud native

in the new era of SDM

The full cloud native approach in developing the next generation of SDM
solutions is essential for addressing some of CSPs’ most relevant challenges.

Cloud native applications are assembled • high levels of orchestration and Cloud native software deployment
from a combination of individual automation, reducing the need for – also offers a set of orchestration and
microservices (small pieces of software). or time spent on – manual activities, automation mechanisms – like the
This architecture is highly modular. One due to capabilities like auto‑scaling “In Service Software Upgrade” (ISSU)
microservice can be reused by many of microservices, auto‑healing and at microservice level – to significantly
different applications, adding deployment automated tests speed up the software upgrade and
scalability and accelerating software The granular decomposition of the update activities by up to 70 percent when
development 3. This will bring many software in multiple microservices compared to the virtualized deployment.4
benefits including: makes a flexible bundling of different Application resiliency is highly
• software decomposition and improved network functions possible, with different improved in cloud native thanks to
LCM, allowing faster and simpler functional characteristics within the same auto‑healing. This enables cloud native
updates and upgrades in live networks centralized engine. In this way, CSPs can to terminate faulty application instances,
• greater agnosticity between applications simplify the network architecture, reducing and instantiate new ones for higher
and underlying infrastructure, allowing the number of nodes and interfaces. In availability and robustness.
more deployment flexibility, easier addition, by leveraging on the state‑less The combination of all these
implementation and portability design and the auto‑scaling, CSPs can technology aspects, enabled by cloud
• higher levels of application resilience, independently scale the cloud native native in the evolved SDM, helps CSPs to
allowing the system to cope with failures application FEs and BEs at microservice minimize the total infrastructure, improve
without the need for a full restart or level – securing optimal allocation the operational efficiency and increase
service interruption of resources across different network the level of data protection.
domains and network slices.

Figure 6: cnSDM architecture and the flexible distribution of data storage and subscription management resources

OSS/BSS EDA Provisioning NEF Exposure NWDAF Analytics

layer CNF
REST Nudr, Nudsf Nudr, Nudsf

Data Shared CCDM Dedicated CCDM

data storage
P Policy S Session data storage
layer CNF
E Exposure N Network conf.
UDR UDSF S Subscription (slices, NF serv.)
A Authentication A Application

Ud Nudr, Nudsf Nudr, Nudsf Nudr, Nudsf

CCDM CCDM CCDM
Control HLR HSS EIR UDM/ARPF AUSF HSM
plane CNF AUC
P P
AAA PCRF PCF NRF NSSF
S S N N

User plane/ Dedicated CCDM

edge CNF data
storage
CCDM

MBB (LTE) eMBB uRLLC mIoT/BBIoT Private

network

Optional: CCDM can be dedicated to the network function

3
To learn more, read our paper The cloud native transformation or shared across multiple network functions
4 To learn more, read our paper Dual-mode 5G Core: TCO benefits
7 Ericsson  |  Cloud native subscription and data management in 5G

How to build a cnSDM

solution for efficiency in 5G

Our solution for cnSDM is based on the unified data storage

and centralized subscription management engine.

The cnSDM solution is part of our common data repository for all network at solution level (BE – FE), and the triple
dual‑mode 5GC offering for a common domains can optimize the data storage redundancy mechanisms.
cloud native software platform that resource usage by up to 20 percent, when The CCSM secures authentication
supports EPC and 5GC 3GPP architectures compared to a scenario of coexistence consolidation and mobility management
(see Figure 2). This allows for a between legacy and the new 5G database. procedures in one common engine, to
multi‑access solution, including support The “one common provisioning” is also reduce up to 25 percent of the impact
of 5G NR (NSA and SA) deployments, secured by the external Ericsson Dynamic of signaling processing in the different
as well as all previous generations, Activation (EDA) product for simplified application FEs. We can optimize the
in a single software platform for data management and configuration. common microservice resources and
operational efficiency. 5 The support of a built‑in automated reduce integration test activities by up to
The cnSDM is based on two main migration procedure secures cost‑effective 10 percent, thanks to the flexible bundling
network components: the Cloud Core projects with faster and automated of different application FEs in the same
Data‑storage Manager (CCDM) based subscriber data migration from legacy CCSM product.
on the combination of UDR and UDSF Ericsson databases into the dual‑mode The optimization of different
network functions6 inside the same cloud native common repository. When application FEs’ capacity, enabled by the
product for unified data storage; and the compared to the traditional data migration flexible scaling within the centralized
Cloud Core Subscription Manager (CCSM), activities in legacy SDM solutions, subscription management engine, allows
based on the combination of UDM, CSPs can migrate double the number up to 20 percent of infrastructure savings
AUSF, HSS, EIR NFs and HSM module, of subscribers per day, at any time (not when compared to a scenario with the
inside the same product for centralized only during maintenance windows), co‑existence between legacy SDM and
subscription management. and without stopping provisioning, cnSDM domains.
The CCDM can support multiple types or impacting traffic. The advanced interworking between
of structured and unstructured data, CCDM secures high reliability of stored application FEs enables one common
including multiple standard interfaces data with fast recovery time, and a authentication engine and the proper
to connect both legacy and new 5G minimized service impact in case of service continuity for voice/data and
application FEs. This ability to act as one severe network issues, thanks to SMS when moving from 2G/3G/4G to
auto‑healing, the overload protection 5G network domains.

Figure 7: Unified data storage with common provisioning Figure 8: Centralized subscription management engine

5GC EPC CS/PS Core 5GC EPC CS/PS Core

Common Cloud Core Data Manager (CCDM)
Cloud Core Data Manager (CCDM)
provisioning LDAP for unified data storage
Nudr
BSS Provisioning Cloud Core Subscription Manager (CCSM)
EDA UDR UDSF
REST function for centralized subscription management
API
Ud Ud, Sp Nudr ARPF

HSS UDM AUSF EIR HSM

Ud MAP Diameter SBA

Cloud Core
Interworking layer
Subscription
HLR/AuC, HSS, PCRF, AAA, Manager HLR/AuC, HSS, PCRF, AAA,
EIR, FNR ENUM, EIR (CCSM) EIR, FNR ENUM, EIR

CS/PS CS/PS
EPC/IMS 5GC EPC/IMS 5GC
Core Core

5, 6
To learn more and for network function explanations, read the paper: One core – the best of two worlds – solution description
8 Ericsson  |  Cloud native subscription and data management in 5G

A smooth migration
into a new era

The evolution towards a cloud native SDM solution is

driven by the best compromise between speed and risk.

The cnSDM enables a smooth Depending on when we position the The cnSDM offers CSPs the opportunity
evolutionary path from EPC to 5GC for BP in the 5G adoption journey, there to support the different evolutionary
the entire data layer. The growing trend are options for a different compromise steps at minimum cost. It also allows
of 5G subscriptions (see the orange between TCO savings (the sooner them to decide the right timing for
portion of the Figure 1 graph) will CSPs jump into the cnSDM, the better the BP in a flexible way: protecting
determine CSPs’ strategy and speed for total capex and opex savings) and investments in legacy SDM, exploring
for evolving the current data layer risk mitigation (delaying full migration new 5G business at the right speed
solutions into cnSDM. We can consider into cnSDM until CSPs are confident in and gradually adopting the new cloud
three significant steps: managing the new solution with the native paradigm.
• A first step where we introduce right level of control).
5G NSA with a simple software
upgrade of legacy SDM.
• A second step where we introduce Figure 9: The evolution strategy towards cnSDM and the BP
the new 5GC for SA accesses, putting
STEP1: STEP2: STEP3:
in place mechanisms for automated
5GNSA 5G SA introduction with Convergence to one
subscriber migration between the introduction tight interworking and smooth dual-mode 5G Core
two domains, and securing two levels migration options
of interworking for service continuity
and mobility management: one
100%
between the legacy database and
UDR, and one between the legacy 90%
FE and UDM.
• A third step where we move the entire 80%
installed base into the final cnSDM.
70%
Breaking
To move from the second to the third 60% point
step, CSPs should decide where to
position the “Breaking Point” (BP) over 50%
time. The BP represents the moment
when the customer decides to move 40%
100 percent of subscribers into the
30%
dual‑mode 5GC and consequently into
the cnSDM solution. The position of 20%
the BP is driven by the speed required
for adoption by the 5G market, and by 10%
the level of risk the CSP is ready to take
with respect to the readiness of the new 0%
network solution and its management. Flexible time smooth migration
9 Ericsson  |  Cloud native subscription and data management in 5G

Improving operational
efficiency

The drastic improvement in cnSDM operational efficiency is enabled

by the adoption of service automation tools and procedures.

Ultimately, it is necessary to have a holistic E2E change, embracing tools, reducing the risk and complexity
a holistic view of the operation and culture and an agile mindset and way of the entire software update
management processes, organization of working. procedure. In addition, the software
and technologies adopted in your DevOps extends the agile software update is performed using a rolling
network, to really achieve full development culture to deployment and approach between all the instances
operational efficiency in 5GC networks. operations, balancing the development of microservices that need upgrading,
This enables the required agility team’s desire for rapid change, with the which definitively reduces the traffic
for designing and launching new operations team’s desire for stability. impact in the network.
services, and to operate and manage By adopting CI/CD, new services or Issues can be detected as early as
the network with high levels of TCO features can be delivered to the market possible in the chain of events and sent
efficiency. Some key areas that should as soon as they are ready, rather than back over as many steps as required
not be overlooked in the migration to taking months, as they do now.7 for fixing.
5G include the following: Software updates can be gradual Network security will increase, as
(rather than major projects) and tested vulnerability is reduced, when the latest
Software automation with with CI/CD automatically. Thanks to the cloud software versions are in place and
To accelerate software upgrades, native architecture, the focus can distributed to customers.
updates and testing, the adoption of just be on the changed microservices, For example, more than 60 percent
DevOps principles such as CI/CD is a minimizing the impact on the complete opex savings can be achieved for
must in 5G Core networks, and requires software application and consequently software upgrades through our CI/CD
tools and processes for CNAs.8

Figure 10: Ericsson’s CI/CD flow

Continuous Software Software

releases distribution upgrades

Acceptance
tests
Ericsson Service provider

Data
Dev. team Feedback
collection

7
To learn more, read our white paper DevOps: fueling the evolution toward 5G networks
8
To learn more, read our paper Dual-mode 5G Core: TCO benefits
10 Ericsson  |  Cloud native subscription and data management in 5G

Moving towards the zero-touch network.

Increased levels of automation a combination of different network Without changing the operating model,
and orchestration towards a functions and network capabilities. the evolution to 5GC and cnSDM will
zero‑touch network9 CSPs need to secure these services for only increase the overall cost and
The 5G environment will be more constant optimization according to network management complexity, as
complex than earlier generations, so a user needs. An orchestration engine well as TTM for new services. This is the
CSP’s network needs to be automated will be crucial for composing resources opposite of what is expected with 5G.
and orchestrated at various levels to into topological structures, including Some business consequences are:
meet modern business challenges and network slices, software‑defined • long cycles for service sales creation
provide a diverse range of services. networking, NFV services and network and fulfilment, limiting enterprises’
Some of these are more closely functions (virtual and cloud native), business success
connected to cnSDM, such as: to meet service demands. • increased TTM and complexity in
• Cloud native resource orchestration: A further job for the orchestration monetizing new technologies
Cloud native network functions, solution (together with the cnSDM) is to • revenue losses, higher expenses and
like the ones included in cnSDM, ensure that service intent is maintained, even churn
are expected to be deployed even as circumstances change, • impossible to achieve zero‑touch
in a virtual – and ideally including network faults, increased automation from selling to billing
cloud native – environment. service consumption, congestion of • degraded user experience
• Network slice orchestration: Although shared resources and opportunities to
managing a few slices manually is optimize how the service is delivered. A good transformation strategy,
possible, orchestration is needed to This requires an ongoing closed‑loop supported by the C‑level, that aligns
meet service level agreements for a approach. Monitoring the service and business and technology needs with the
large number of network slices. The underlying network means events and organization’s current maturity level is
cnSDM network functions can be threshold violations can be detected, imperative for cloud native adoption.
shared or dedicated across different triggering decisions based on defined This strategy should tackle:
network slices and provide various policies to adjust or redesign the • Processes: to manage, automate and
levels of data management services network in order to continue to meet orchestrate this hybrid core network
depending on specific needs. required service levels. in a cost‑efficient way.
• Edge sites: A much greater number • Organization: to adopt a
of edge facilities, compared to Operational transformation10 cross‑domain model by focusing on
traditional, centralized data centers, In our experience, leading CSPs often competences and organizational
requires the ability to easily manage continue their existing approach to borders that match the new
this distributed resource landscape. operations when they move to a cloud process needs.
The flexible deployment capabilities environment, meaning critical pain • Technology: to embrace capabilities
of cnSDM make it possible to address points are carried forward. Manual, in order to achieve high 5G
these types of needs. time‑consuming and inconsistent operational efficiency.
processes, plus a lack of seamlessly
The goal of a cnSDM solution (and integrated operating models,
of the 5G Core network as such) is increase the complexity of managing
to deliver E2E services composed of the network.

9
To learn more, read the paper: Network automation: The journey to zero-touch networks
10
Learn more, read our paper Transforming operations on the way to 5G
11 Ericsson  |  Cloud native subscription and data management in 5G

Summary

Summarising the key advantages

of the cnSDM solution for CSPs.

The overall advantages of the cnSDM solution can be summarized by the four main areas below.

Cloud native subscription and data management (cnSDM)

Increased flexibility A more unified solution Increased efficiency Improved robustness

The advantage of increased A more unified solution Efficiency is increased in The solution is more robust
flexibility can be seen in enhances the data storage the common provisioning in the level of database
the deployment of data for multiple types of data for all network data across protection and in the E2E
storage and subscription and network domains different domains and in the performance in case of
management functions, and in the engine for key automation of subscriber signaling overloads. This
and in the balancing of subscription management data migration procedures, is thanks to the synergies
the capacity of different tasks, like authentication as well as in software LCM between the advanced
application FEs, optimizing and mobility, simplifying activities. This is thanks to cloud native mechanisms for
BE and FE resources up to the SDM network the cloud native deployment application resilience and
20 percent. architecture with fewer of both data layer and SDM the evolution of the standard
network functions, and up control plane products and for network overload
to 25 percent reduction of to the CI/CD processes and protections, increasing
signaling processing load. tools, improving the overall the overall in‑service
operational efficiency of performance of the entire
the SDM solution by up SDM solution for both legacy
to 60 percent. and 5G domains.

Better TCO
 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

Ericsson The content of this document is subject to 5/287 01-FGB 101 147
SE-164 80 Stockholm, Sweden revision without notice due to continued © Ericsson 2020
Telephone +46 10 719 0000 progress in methodology, design and
www.ericsson.com manufacturing. Ericsson shall have no
liability for any error or damage of any kind
resulting from the use of this document