Dual-mode 5G Core:

TCO benefits
The total cost of ownership
benefits of Ericsson’s solution

October 2020
 2 Ericsson  | Dual-mode 5G Core: TCO benefits

Introduction

Contents No journey to a future core will be alike. All communications

03 Unpacking the advantages
of Ericsson’s dual-mode service providers will have different needs, strategies and
5G Core solution priorities. But for all options, a holistic view on cost is key.
05 One platform for all EPC and
5GC functionalities
06 Cloud native and microservices: Throughout all critical shifts in technology, Ericsson’s dual-mode 5G Core (5GC)
the future of smarter applications communications service providers (CSPs) solution sets out to address the various
07 Enhanced automation enables will share one key challenge: the need to journeys that today’s CSPs have already
manage total cost of ownership (TCO). embarked upon, to effectively meet their
simplified operations
During the period of migration, new shared needs.
08 Quicker integration of new
and existing systems need to coexist As we saw with 4G, there is a definite
Network Functions
in an effective way for many years. advantage to winning the race for new
09 The probing paradigm shift At the same time, efficiencies need technology. Everyone wants to be the first
10 High user plane scalability to be improved to capture new to deliver 5G, and the first to apply it to the
11 Integrated Packet Core Firewall business opportunities. market. But the migration from 4G to 5G
12 Machine learning assisted paging will not be easy. To transition smoothly
13 Efficient user plane A perilous journey and reap the benefits, the industry needs
throughput handling As seen in Figure 1, there is a lot to to be prepared to completely reinvent
14 More efficient allocation and consider on the journey toward a future traditional ways of working.
control of network resources core network. On top of this, different Ericsson has applied 140 years’
carriers may have different priorities, experience in technological shifts, strong
15 Significant configuration savings
or even be taking different approaches global relationships and long-lasting
16 Centralized authentication
to overcoming the various challenges. customer experiences to an innovative
and mobility management
Managing capex and opex is becoming new solution that enables CSPs to manage
17 Conclusion more important than ever, but CSPs also migration in an effective and cost-efficient
need to find new growth opportunities and way, at a speed that suits them.
balance effective management with Let us begin analyzing this approach
network evolution. to core design by more closely examining
each of its key elements, and how they
were originally named.

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

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

3 Ericsson  | Dual-mode 5G Core: TCO benefits

Unpacking the advantages

of Ericsson’s dual-mode
5G Core solution

The introduction of 5G opens up a new world of opportunities,

but also presents challenges. New value can be created and
captured, but not without changing the way CSPs work.

Cloud native deployment Figure 2: Dual-mode 5G Core

Ericsson’s dual-mode 5G Core solution
delivers cloud native applications that
Cloud Core Data-Storage Manager Data layer
supports Evolved Packet Core (EPC) and
5G Core 3GPP architectures. The main
areas where cloud native implementation
principles bring benefits to CSPs, their Cloud Core Cloud Core Cloud Core Cloud Core
Resource Subscription Policy Exposure
customers and their vendors are speed, Controller Manager Controller Server
agility, efficient operations and
resource utilization.
The decomposition of software into SBA architecture
Signaling
microservices facilitates a fast, low-cost Packet Core Controller
Controller
method of introducing new services at
any scale. It supports easy and effective Control plane
scaling of services from hundreds of users
to millions. This enables CSPs to address
or pursue new business opportunities
that have been difficult to engage with NR SA
until now. LTE/NR NSA
LTE Packet Core Gateway User plane
GSM/W CD MA
5G Core with Service Based
Architecture (SBA)
We are implementing SBA, which is the
new standard from 3GPP (Release 15) By using innovative platforms, frameworks and architecture, the Ericsson
allowing, among other things, the 5G dual-mode 5G Core solution can significantly improve TCO in future Core
New Radio (NR) in a standalone (SA) networks by enabling previously unseen benefits to be realized in unique ways.
fashion to be connected to the Core. With The result is that the core network capex and opex can be significantly reduced,
SBA, a new software architecture based on while user plane (UP), control plane and data layer footprints can be greatly
IT principles is introduced, allowing for mitigated and substantial cost savings can be seen on new network integration.
faster service creation. This architecture
is also the base for the evolution of all
future 3GPP core standards. For more information about dual-mode 5G Core,
read our solution description report by clicking here.
Dual-mode platform
Our implementation of cloud native and
SBA means that we have created one
operational platform for both EPC and
the new 5GC.
This makes things much more
streamlined by letting each CSP migrate
toward 5GC either at the pace that the
market demands, or according to a chosen
strategy – or both. We will next dig deeper
into each of the individual TCO benefits,
by exploring specific examples of how
each benefit works and the exciting
new capabilities it enables.
4 Ericsson  | Dual-mode 5G Core: TCO benefits

Figure 3: TCO reduction opportunities with dual-mode 5G Core

70% opex reduction in LCM,

60% opex reduction
10% in testing and O&M
20% capex savings in in software upgrades
and 10% capex savings
core network infrastructure with Ericsson CI/CD tools
on infrastructure
with dual-mode cloud and In-Service Software
with Ericsson cloud native
native operations Upgrade (ISSU) for cloud
software design principles and
native applications
NF bundling in one CNF

30% capex savings in 

80% opex savings in
network integration
when expanding with new
TCO reduction NFs in SBA
(core network capex
and opex savings)
20% capex savings in  15% capex savings in control
UP footprint
with single hop to payload and
flow spraying of 5G peak rates
90% opex reduction and
UP footprint 
60% capex savings in probing
with efficient Gi-LAN
with built-in software
consolidation of UP
probe solution
service functions
>50% capex reduction
compared to dedicated user
plane paging resources
plane security solutions
with machine
with integrated
learning-assisted paging
Packet Core Firewall

25% capex savings in

15% capex savings in
70% opex savings in authentication
database infrastructure
configuration of policies signaling resources
with optimized data storage
when using common policy with one common engine
deployment across multiple
configuration tool for authentication and
network slices
mobility management

The core network opex and capex Figure 4: TCO evolution during the migration to dual-mode 5G Core
savings, enabled by the capabilities of
our dual-mode 5G Core as highlighted in Tot. CN TCO Tot. CN opex To. CN capex
Figure 3, can potentially enable more than
a 50 percent reduction in the network TCO 5G NSA support 5G Core maturity Common
5G Core intro Migration to
(EPC software (advanced dual-mode dual-mode
when compared to expenditures in the upgrade)
(interworking)
network slicing) 5G Core
legacy core network (that is, EPC). This
significant cost reduction will be reached
over time, based on the speed of adoption
of each capability and the characteristics of
the evolution path selected by each CSP to
move from EPC to 5GC for standalone NR.
An example can be seen in Figure 4
where we can observe, at first, a smaller
TCO reduction when evolving the >50% CN TCO
ECP network to support 5G NR reduction with
dual-mode
non-standalone (NSA). When introducing 5G Core
5GC, and growing the number of 5G
subscriptions, we should expect a TCO
increase due to the coexistence of two
separated core networks (EPC and 5GC).
However, when migrating toward the
dual-mode 5G Core to consolidate 5G
and 4G users in a single, common Core,
a drastic TCO reduction of up to 50 percent
can be seen. •• •• •• •• •• •• •• •• •• •• •• •• •• •• •• •• •• ••
It is also relevant to mention that each
capability shown in Figure 3 has a different
weight in terms of impact on the TCO,
meaning that the adoption of some will
provide a more immediately visible impact
than others.
5 Ericsson  | Dual-mode 5G Core: TCO benefits

One platform for all EPC

and 5GC functionalities

Dual-mode cloud native operations can save up to 20 percent of capex in core

network infrastructure. Ericsson 5GC introduces dynamic resource usage and
dynamic auto-scaling to the core network, supercharging cloud native operations.

Figure 4:
With dual-mode 5GDual-mode 5G Cloud CoreFigure
Core, one Virtual – dynamic resource5G
5: Dual-mode usage
Core – dynamic resource usage
Network Function (VNF) product can
handle both LTE/EPC and NR/5GC traffic
simultaneously. This eliminates the need
to have two separate Network Functions
(NFs) – one for EPC and one for 5GC –
working separately (for example, Cloud Core Data-Storage Manager
40 percent EPC and 60 percent 5GC).
In the event of a traffic fluctuation in EPC UDR
and/or 5GC because of new services, new UDSF
device capabilities, or mobility between
DATA LAYER
LTE and NR coverage (for example,
20 percent), service providers will need
to over-dimension both EPC and 5GC
NFs to their peak busy
Cloud hour
Core to manage. Cloud Core Cloud Core Cloud Core
However, this will always vary for different
Cloud Core Cloud Core Cloud Core Cloud Core
networks, therefore a detailed analysis will Resource Controller Subscription Manager Policy Controller Exposure Server
be required.
With our solution, however, things NSSF NRFF UDM AUSF PCF NEF
are quite different. Thanks to its EPC NSSF HSS 5G-EIR PCRF SCEF
dual-mode capability and common
cloud native design, our Core can
automatically rebalance the capacity SBA architecture Signaling
Packet Core Controller
of EPC and 5GC NFs within the VNF Controller
DRA*
without the need for extra capacity in TDF-U AMF SMF SEPP BSF
either domain. Put into figures, this DRA *
SCP
MME SGW-C PGW-C
means that a fluctuation of plus or minus
20 percent can result in a saving of CONTROL PLANE
20 percent in network infrastructure
resources, with the additional
consequence of a 20 percent
capex reduction.
Packet Core Gateway

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

* DA and DEA functions also supported

 6 Ericsson  | Dual-mode 5G Core: TCO benefits
Cloud native and microservices:
the future of smarter applications
Applying cloud native design principles unlocks operational
benefits and provides up to 10 percent savings in infrastructure.
Our cloud native applications (CNAs)
are built following a set of design
principles to allow deployment in cloud
environments that meet the needs of
the telecommunications industry.
These principles are:
• agnosticity
• decomposed software
• application resilience
• state-optimized design
• orchestration and automation
As our solution’s cloud native architecture
is based on microservices, it has the
unique capability to bundle multiple NFs
into one single Cloud Native Network
Function (CNF) bundle in a flexible
and optimized way.
Figure 6: CNF infrastructure savings
thanks to bundling
Cloud Core Resource Controller without bundling
NRF NSSF
Cloud Core Resource Controller with bundling
NRF NSSF
Common
microservices
SF
In the example in Figure 6, we have
compared two scenarios – one that
takes this bundling approach and one
that does not – addressing the Cloud Core
Resource Controller product in 5GC
(NRF and NSSF NFs).
The sharing of common microservices
in the bundled scenario allows for savings
of 7 percent on Virtual Central Processing
Units (vCPU), 24 percent on memory and
17 percent on disk capacity.¹ This results
in potential capex savings in infrastructure
in the order of 10 percent at CNF level.
Other significant benefits from the
cloud native built dual-mode 5G Core
applications are:
• >50 percent faster NF instantiation time
• >80 percent faster NF scale out and scale
in time
• 70 percent faster NF upgrade time
• >90 percent better resource utilization
with minimal commercial deployments
These benefits are best realized in use
cases like new network slice instantiation,
network scaling in/out, software
upgrades and small-sized deployments.
The capability to bundle different NFs
together within one single CNF bundle,
as described earlier, can also create
significant advantages in the core
network’s operation and maintenance,
with consequent opex reduction.
One key benefit is driven by the fact
that up to 22 percent of mutual operations
between different NFs triggered by most
5G test cases tend to occur within the
bundle. This means that by leveraging
pre-integration tests, it is possible to skip
mid-integration test activities between
NFs within a bundled CNF.
If we consider that, in our experience,
integration testing activities in 5GC
typically make up about 70 percent of
a total integration effort, we can easily
deduct an opex saving of 15 percent
from the overall effort expelled.
A second significant benefit
materializes thanks to the new possibilities
enabled by our solution. One of these is
the ability to unify certain key life cycle
management activities (for example,
configuration, troubleshooting and
software upgrades) toward the different
NFs inside the bundle.
Our research estimates that
35 percent of staff hours usually dedicated
to integration activities can be saved
thanks to this unified operation and
maintenance (O&M). This approximation
is based on a 5GC scenario where the
27 main NFs are bundled in 5GC within
8 different VNFs.
Read more in Ericsson’s guide:
The cloud native transformation –
A guide to cloud native design and
operations principles
7 Ericsson  | Dual-mode 5G Core: TCO benefits

Enhanced automation enables

simplified operations

More than 60 percent opex savings can be achieved for software

upgrades, through Ericsson’s continuous integration and continuous
delivery (CI/CD) tools tools and processes for CNAs.

Today, a typical software upgrade Figure 7: More than 60 percent opex reductions for software
procedure, including all preparation and upgrades with Ericsson’s (CI/CD) for CNAs
testing, can take anywhere from 80 to
400 hours per VNF to complete. Evidently, Continuous Software Software
this represents a massive variation in releases distribution upgrades
timescales, which mainly depend on
the level of testing the CSP chooses to
undertake before the solution goes live,
balanced with the level of automation that Acceptance
their PNF/VNF currently supports. Massive Ericsson Service provider tests
upgrade projects also mean longer lead
times for new software in production
and leave quite some space for human
error with lack of automation. Dev. team Feedback Data
collection
In comparison, Ericsson’s CI/CD tools
and processes enable service providers to
automate this. By doing so, we calculate
that savings of more than 60 percent (in
terms of reduced opex) can be achieved Figure 8: In-service software upgrade (ISSU) with canary testing enabled
through our software upgrades. by cloud native
Our research tells us that a typical
upgrade time of 100 hours per VNF/CNF
can be reduced to just 40 hours – by
applying tools like Software Gateway, µService A µService B Before
Ansible, Jenkins and others. Version x.0 Version y.z
Nevertheless, this level of efficiency can
only be accomplished if CSPs are prepared Fallback
to change their ways of working within
carriers and wait for such TCO benefits
to mature over time. µService A µService B During
Version x.1 Version y.z

>60%
Along with enhanced
µService A
Version x.1
µService B
Version y.z
After

simplification, more than

60 percent savings with software
upgrades can be achieved.
8 Ericsson  | Dual-mode 5G Core: TCO benefits

Quicker integration of
new Network Functions

Up to 80 percent savings in integration costs can

be seen when introducing new NFs in the 5G SBA.

In traditional core networks, all the
activities involved in integrating a new NF,
such as HSS-Front End, must be carefully
orchestrated so as not to disrupt vital
interfaces (for example, Cx, Sh, S6a, Ud,
MAP) or protocols (for example, LDAP/
SOAP, Diameter, MAP). They must also not
disrupt the various intricate ways in which
these interfaces and protocols interact
with surrounding nodes or domains
(for example, UDB, HLR/AUC, EPC, IMS).
CSPs need to take great care to ensure
that any integration activities are always
properly tested and reconfigured, which can
be challenging and time-consuming.
If we compare this scenario with a
similar one seen in 5GC, using the Network
Resource Function (NRF) and SBA, the
integration of a new NF involves very few
interfaces (for example, Nudm and Nausf
for UDM/AUSF), only one surrounding node
(just the NRF) and just one integration
protocol (REST). Our estimations show
that this kind of simplification can result
in an opex reduction of up to 80 percent
in terms of staff hours spent on the
integration activity.

Figure 9: Common control of NF resources for system integration savings

4G scenario (EPC): vHSS-FE integrated into 5G Core scenario: UDM and AUSF 5G NFs integrated
a vUDC solution based on Ericsson NFVI into an existing cloud native 5G Core with SBA

CUDB EPC IMS SCEF HLR/AUC NRF NSSF PCF UDR UDSF

SBA

DSC SLF DNS

UDM AUSF SMF AMF

LDAP/SOAP Diameter MAP

Key activities for network integration of a new NF

Integration interfaces toward different Core NFs
Integration test of protocols to be handled for communication between NFs
HSS
Configuration activities to be done in the
existing peer NFs to introduce the new NF
Configuration activities in other signaling and
network configuration nodes to introduce the new NF
Configuration activities related to the new NF to be integrated in the network
9 Ericsson  | Dual-mode 5G Core: TCO benefits
The probing
paradigm shift
Standalone hardware probes are replaced by application built-in probes
dramatically simplifying network architecture and improving operational
efficiency, reducing capex by up to 60 percent and opex by up to 90 percent.
Networks are maintained using
monitoring systems that provide
capabilities like assurance, security and
end-user experience measurements –
for example, Ericsson Expert Analytics.
The data for those systems is provided
by interface mirroring (tapping) and
events that process data before it reaches
the monitoring systems. Today, most
mobile network operators are using the
standalone hardware probe solutions.
These hardware probe solutions,
specifically the tap and probe components,
face challenges in a virtual cloud
infrastructure within several areas such
as security, scalability, footprint and
automation. These challenges are getting
bigger as Packet Core applications move
to cloud native.
We address these challenges by
providing a built-in software-based probe
capability in CNFs included in the Packet
Core Controller (PCC) and Packet Core
Gateway (PCG) products.
Figure 10: Limitations solved with NF inbuilt software probe
MME on VM SGW-C on VM
Virtual layer vSwitch port
mirroring
VNFI vSwitch
Physical layer
3PP probing
3PP probing
MME GW-C PCRF
PGW-U
Physical
3PP probing
3PP probing
The built-in software probe solution
also has TCO advantages compared to
traditional external tapping and probe
solutions. The capex footprint savings from
enabling the software-based probe at PCC
and PCG, compared to deploying physical
tap and probe appliances, are estimated
to be 60 percent and could be higher
depending on the granularity of protocol
and application data exposed.
Opex savings are estimated to be up to
90 percent since lifecycle management
(LCM) handling, such as software
upgrade, resource scaling and automation
support, is covered by LCM handling
within the VNF itself.
The software probe solution is an
evolution of the long-proven functionality of
the event-based monitoring and integrated
traffic capture features available in
products such as SGSN-MME and
Evolved Packet Gateway (EPG).
TCO gains will also come with several of
the features that are added to the solution.
Pr Pr
AMF SMF
Pr
UPF
Pr Pr
MME GW-C
Pr
PGW-U
For example, the consumer-centric
configuration is filtering at the source and
only useful data is captured and streamed,
which leads to a gain in routing and
bandwidth. The stream interface is open,
secured and follows industry standards,
meaning no need for external processing
with mediation and external
brokering functions.
Conclusion
The road ahead is rocky. CSPs need
to balance management, evolution
and TCO – and we are helping them
overcome this.
Ericsson’s dual-mode 5G Core
solution can help CSPs get the most
out of cloud native, microservices,
UP performance and more.
However, CSPs must be prepared to
re-examine their existing processes
to maximize the benefits.
EPC cloud native NF
5GC cloud native NF
Pr Ericsson software
Probe inside NF
Monitoring systems
10
High user
plane scalability
Up to 30 percent capex and opex savings in UP infrastructure
can be achieved with consolidating Gi-LAN functions.
Today, there are several added value
Service Functions (SFs) that are
traditionally placed outside of the
gateway. These cover functionalities
ranging from traffic optimization and
content optimization to, for example,
security, Network Address Translation
and Firewall.
As routers, load balancers are neither
subscriber nor service aware, making it
challenging to steer traffic just to the SFs
required by a specific use case. In a
worst-case scenario, all flows will be sent
to all SFs, even if only a fraction of the
traffic is using the service.
Simplified routing
For existing SFs, the PCG provides
simplified routing, removing unnecessary
East-West traffic (aka “traffic tromboning”).
The service logic and built-in load balancers
then steer and distribute the traffic,
coordinating the uplink and downlink
sessions, while also monitoring the SFs
to ensure they are up and running. In the
case of an SF failure, failover mechanisms
Figure 11: Service chaining saves footprint and integration costs
SFs are usually added after the gateway,
alongside LAN equipment
• All traffic routed to SFs
• Requires external LAN/extra footprint
External service chaining only
steers required traffic flows
• Removes need for external
balancers/routers
• Reduces SF footprint
Internal service chaining for Ericsson
and 3PP value-added services, enabling
flexible function selection
• 40 percent less integration costs
• 30 percent less footprint
will redirect the traffic. There is no need to
deploy load balancers or routers. Integrated
Service Chaining is service and subscriber
aware, meaning that it steers traffic to
integrated SFs only when needed by that
specific use case.
Gi-LAN consolidation
PCG allows the embedding of heterogenous
SF into one packet processing pipeline,
including 3P SF.
With Gi-LAN consolidation, PCG
provides on average a 30 percent footprint
reduction compared to standalone
SF deployments.
It also brings opex reductions through
minimizing integration points and reducing
the number of entities needed to
manage operations.
Tight integration does not put undue
requirements on cloud infrastructure, nor
on SFs. This architecture, based on cloud
native principles, enables SFs to have an
independent life cycle.
Today, it is difficult to optimize footprint
when SFs are deployed in the same host.
PCG
SF1 SF2
Service chaining logic
PCG
SF1 SF2
Service chaining logic
PCG
Ericsson  | Dual-mode 5G Core: TCO benefits
Each SF requires independent CPU and
memory allocation. Therefore, they cannot
share resources in instances where one
is overloaded but the others, in the same
host, have available resources.
The PCG approach creates a host level
complete UP, which is ideal for distribution
and scaling. Communication between the
different functions happens in the user
space without using up IO resources. PCG
maximizes vCPU and memory utilization,
as SFs can scale up or down dynamically,
taking or releasing vCPU and memory when
needed. This solution also provides fast
time-to-market and short latency, as all SFs
share a single IO interworking with cloud
infrastructure.
Since the PCG receives session and
subscription data from PCC and conveys
that information internally, this also reduces
the opex cost for integrating several
Gi-LAN SFs with the Policy and Charging
Rules Function (PCRF) in the control plane
data layer and with the virtual network
functions manager (VNFM) module in the
orchestration layer.
SF1 SF2
Load balancers, routers
11 Ericsson  | Dual-mode 5G Core: TCO benefits

Integrated Packet
Core Firewall

We can improve service availability and mitigate TCO

implications from traditional core security solutions in
5G Core with the integrated Packet Core Firewall.

5G creates myriad new use cases, but How to get the best TCO while maintaining

these opportunities extend potential threat
sources. The number of distributed denial of
service (DDoS) attacks rose by 542 percent
between Q4 2019 and Q1 2020, where the
majority of attack sources were IoT devices
powered by Linux.
The UP is the Packet Core function
that is most exposed to outside threats
originating from devices within the
network, as well as internet and roaming.
If the UP is compromised, all 5G services
stop functioning – therefore, the UP
function must be proactively protected
and run sustainably.
CSPs usually deploy dedicated security
Packet Core solutions using three to four
different security vendors. This diversity
creates complexity due to multi-vendor
interoperability and an increase in
UP latency.
Moreover, the usage of dedicated
security solutions in adding another type
of network or service function (“security
box”) to the UP have direct implications on
network operations and TCO:
• Higher capex: CSPs need to consider
hardware dependencies and anti-affinity
rules when selecting NFVI for UPF and
security functions.
• Higher opex: the more service functions
5G latency and edge scalability
Packet Core Firewall is a cloud native
product that can be seamlessly integrated
into Ericsson Packet Core Gateway,
providing a fusion of UP security and
advanced security functions, addressing
security use cases in the mobile broadband
and IoT segments. It leverages the
following functionalities: subscriber
firewall, roaming firewall, non-3GPP
access firewall and advanced threat
recognition based on machine learning (ML),
and brings time-to-mitigation closer to 5G
latency demands.
Packet Core Firewall is tightly integrated
with Ericsson PCG in a single CNF, enabling:
• Lower capex: no hardware dependencies
in NFVI, since Packet Core Firewall
operates on the same stack. No East-West
traffic in NFVI, reducing SDN cost by more
than 50 percent.
• Lower opex: no need to orchestrate a
separate NF. Single VNFM and single
connection to MANO and OSS.
• Ensured 5G low latency, while mitigating
Figure 12: The integrated Packet Core Firewall
EPC Network Function
as specified by 3GPP
>50%
Along with enhanced operational
efficiency and low UP latency,
50 percent TCO savings can
be achieved.
80 percent of all DDoS threats thanks
to tight signaling integration between
advanced detection and mitigation
functions. Latency is kept below 100ms.
• High scalability and deployment
flexibility, as it is optimized to scale with
the UP to the edge of the network to cater
for secure core network 5G use cases. The
solution can scale to hundreds of edge
sites, and to specific 5G use cases.
Packet Core Firewall is powered by A10’s
leading security technology, with its
profound expertise in the modern threat
landscape and focus on 5G use cases.

CSPs have to operate, the higher the 5GC Network Function

as specified by 3GPP Internet
orchestration cost (separate VNFM, Subscriber threats
multiple connections to NMS, NFVO, etc.). SGi-LAN Function Firewall
• Network latency: if CSPs add security Security Function
threat mitigation to the chain, then the Protected
time-to-mitigation should be within IPv6
a single-millisecond latency. If not, NAT Optimization migration

then the promise of 5G technology is UPF

broken, and the core network is flooded
RAN 3GPP
with malicious traffic, since one user SEG
SGW-U PGW-U
IPUPS
equipment (UE) can generate loads of Packet Core Gateway
up to 20Gbs.
• Footprint efficiency: security boxes can’t Non-3GPP
Access Roaming
be scaled out to the edge. Installing Access
Firewall Roaming
threats Firewall
security boxes in hundreds of edge sites threats
Packet Core Firewall
is simply cost-prohibitive.
12 Ericsson  | Dual-mode 5G Core: TCO benefits

Machine learning
assisted paging

Machine learning reduces the need for

control plane paging resources.

Mobility management is one of the key which is applicable for both 4G and 5G.

services provided by the core network.
The main challenges CSPs face in relation
to mobility and location awareness are:
• network performance (lower signaling
latency and fewer signaling attempts)
• secure customer experience for both
voice and data services
• sustainability with low
infrastructure footprint
ML solves these CSP challenges with
commercially proven use cases, which
include assisted mobility prediction,
assisted edge mobility and assisted
Tracking Area Identity (TAI)
list prediction.
With ML and big data, CSPs can
explore new levels of functionality
for mobility predictions and location
awareness. Assisted mobility prediction
is one of the key core network capabilities
Here, CSPs need to make fewer signaling
attempts for paging and keep lower
latency without introducing new nodes
for ML.
As of today, the core network
judgment on UE location is based on a
pre-configured list of eNB. With the
adoption of ML capabilities, the core
network will be able to continuously
learn about the changes of UE location
patterns without any human intervention
dynamically adapting the “list” for higher
efficiency in this process. We call it a
topology-aware AI network. Therefore,
ML helps to faster identify UE location
with fewer signaling attempts. Based
on the results of a proof of concept –
realized together with one of our major
Tier 1 customers in Asia using data
collected from their commercial network
deployment – we could experience a
15%
ML enables up to 15 percent
capex savings in control plane
paging resources.
signaling reduction of up to 80 percent
and lower vCPU load of up to 15 percent
when applying ML-based paging
algorithms. These can be directly
translated onto capex savings for CSPs.
These assisted mobility prediction
benefits are achieved with the adoption of
an embedded self-learning ML algorithm to
the dual-mode 5G Core control plane nodes,
eliminating the need for dedicated external
nodes to implement ML algorithms as in
traditional market solutions.

Figure 13: Mobility predictions – key highlights

Adapt to planned network topology change without human intervention (human error-proof)

Automation and
error-proof network Adapt to unexpected network failures Topology-aware AI
operation
Minimize time to comply to the changes

Optimize paging per use cases

• Latency and signaling optimization (in 4G and early 5G)
Optimize investment ML-assisted paging
• Potential is immense in 5G per service offering
(network resource) use case

Resources such as footprint and capacity

No additional model training required

Self-learning
No manual configuration required for ML support (decay model) Inexpensive ML
algorithm

No separate system for ML (lowest opex to add ML to the commercial system)

13 Ericsson  | Dual-mode 5G Core: TCO benefits

Efficient user plane

throughput handling

Handling of peak rates of 20/10Gbps (DL/UL) per UE and

ingress steering optimization help minimize UP footprint

Data traffic is destined to grow by
600 percent by 2025. This creates a need to
tame the data tiger and further reduce cost
per bit to maintain a healthy bottom line.
At the same time, cloud native industry
design creates some bottlenecks for
efficient handling of throughput inside a
worker node. One of these bottlenecks is
increased latency as payload is moved
across many pods.
This is also known as East-West
traffic or traffic tromboning.
We have introduced a load balancer
solution to steer payload traffic to final pod
avoiding multiple hops within a worker
node. This helps to minimize the footprint
required to handle a given high throughput.
Another pain point is burst throughput.
5G NR provides individual high throughput
reaching around 20/10Gbps for a single
user. Typically, enforcement of DPI,
charging and QoS require that all flows
belonging to the user run on the same CPU.
Therefore, the support of very high
throughput will usually require an
over-dimensioning in the UP (typically
of anywhere up to 30 percent) to ensure
that there is enough space available
in the CPU, where the high peak user
ends up.
However, our unique solution, which
includes some patents, allows CSPs to use
all available CPU in the UP host to handle
user IP flows, while at the same time
enforcing DPI, charging and QoS.
Crucially, this means that no special
over-dimensioning is required.
Our solution also provides a smooth
traffic distribution among all CPUs,
avoiding any peaks that might increase
latency or jitter.
In addition, our UP was measured
to be processing 200+ Gbps subscriber
traffic on a standard dual-socket x86
server (Skylake), with cloud native
implementation and support for single-root
input/output virtualization (SR-IOV).
This number applies to non-DPI traffic
and can also be applied to fixed wireless
access, assuming a capacity of 2x100GE
NIC in the servers.

Figure 14: A high-performance UP meeting 5G demand Figure 15: 5G peak rates up to 20Gbps per UE avoiding
over-dimensioning of UP footprint

Mobile broadband background load A peak rate user

Bursty High capacity and 20/10Gbps
network load traffic spraying DL/UL per UE
20 cores and 10 flows are examples only

Software with no support for high UE peak rate

+ PCG = Users are distributed over available cores

Gbps
100%
80%
X Gbps

#Cores
SF1 SF2 1 20

Software with support for high UE peak rate

Flows are uniformly distributed over available cores
Service chaining logic
PCG Gbps

Only the value-added service flows requiring certain SFs 100%

are routed to these, resulting in zero need for packet copying 80%
X Gbps

#Cores
1 20
14
More efficient allocation and
control of network resources
Flexible data storage enables up to 15 percent
capex savings in database infrastructure.
Ericsson’s dual-mode 5G Core solution
is capable of allocating data storage
resources across multiple slices in a very
flexible way. This capability enables an
optimization of the total database capacity
in the network, in instances where there are
various slices, each featuring different kinds
of data storage services (for example, data
isolation and data redundancy).
Picture a traditional 4G EPC scenario
with two different network slices – one
slice addressing mobile broadband (MBB)
services and one slice addressing M2M/IoT
services, toward >40 different enterprises. In
this scenario, each of these big network slices
would have a dedicated data storage solution
with, for example, 1+1+1 redundancy.
A similar situation in a 5GC would greatly
benefit from the flexible allocation of data
storage, which would be capable of offering
a much more granular distribution of data
storage resources, based on the unique
Figure 16: Data storage allocation across multiple network slices
4G scenario (EPC): two main network slices with the same
DB redundancy and software feature levels
25m Subs
41 enterprises
0.35m IoT
devices per ent.
20m IoT devices
needs of different enterprises. For example,
we might see the following scenario:
• The MBB slice could contain five different
service slices (for example, standard MBB
services, VR/AR, HD video streaming,
gaming, and so on). All subscription data
using the three service-slices would be
stored in a shared database with 1+1+1
redundancy.
• The first IoT slice could be split in Massive
IoT and BroadBand IoT groups. M-IoT
group is composed of 10 Enterprises in
the Smart City slice and 10 Enterprises
in that Asset Tracking slice; both of them
share the same database with a basic
1+1 redundancy level. BB-IoT group is
composed of seven Enterprises in the
Drone slice and five Enterprises in the
Automotive slice; both of them share the
same database with an advanced 1 + 1 + 1
redundancy level.
5G scenario (5G Core): different DB redundancy and
software feature levels for different type of enterprises
Example: (x) = enterprises per network slice
UDR
UDR
Ericsson  | Dual-mode 5G Core: TCO benefits
• The second IoT slice (Critical IoT)
addressing the remaining nine
enterprises is split in two different
service-slice categories, both requiring
ultra-low latency performances:
Transport and Robotics. In the first
one (Transport), five enterprises would
share the same data storage with 1+1
basic redundancy, and in the second one
(Robotics), four enterprises would have
dedicated data storage (data isolation
service) with 1+1+1 high redundancy.
The flexible distribution of data storage
resources in the above 5GC scenario
generates a 15 percent capex saving in
the total database hardware and software
capacity required to serve each of the
different slices. Using this approach,
CSPs can also monetize the differentiation
of data storage services used by each
enterprise, applying an extra fee for
data isolation and higher 1+1+1
data redundancy.
Operators/internet application
Gaming
UDR HD video streaming
VR/AR
Back-up
Smart city ent. (10)
UDR Asset tracking ent. (10)
Quarantine
Drone ent. (7)
UDR Automotive ent. (5)
UDR
Transport ent. (5)
Robotics ent. (4)
UDR
15 Ericsson  | Dual-mode 5G Core: TCO benefits

Significant
configuration savings

Common policy configuration tools pave the

way for opex savings of up to 80 percent.

The adoption of an entirely new 5G
paradigm radically expands the overall
diversity of policies that can be configured
and controlled in the core network.
Traditional EPC scenarios tend to
configure just a few sets of policies for
IP Session Establishment (for example,
QoS, quota, charging, session and service
authorization). In the new 5GC context,
however, we see entirely new policies
for access and mobility, user equipment
and network resource control. We also
see an expansion of existing policies
specifically for IP session establishment
(for example, latency).
This technology shift creates a huge Considering a 5GC scenario based on
opportunity in terms of service more than 40 different service-slices
differentiation, but also introduces a with different policy configurations,
whole new kind of complexity – a need to we estimate about 80 percent of opex
configure about 100 times more policies savings in terms of staff-hours can be
than in a 4G network toward many achieved when using this common tool
different policy decision points spread out for policy configuration.
across different slices in the network.
The adoption of a common policy
configuration tool allows CSPs to execute
just one main policy configuration task for
each business slice, addressing all policy
decision points needed to update and
secure the service level for that specific
business slice simultaneously (as seen
in the figure).

Figure 17: Traditional EPC scenario and policy configuration

Example: HD video streaming business slice – policy configuration

Common policy configuration tool

eMBB HD video streaming

P1 P2 P3 P4

IP flow/service configuration rules Network slice/network resource selection

(QoS, charging, quota) (network behavior)
Policy
User Access and Subs session Network
Slices configurations
equipment mobility (voice, data) functions

eMBB network slice

Operators/internet
application
AMF
NRF Gaming
UPF SMF NSSF
UPF PCF-SM NEF UDM AUSF UDR HD video streaming
SCP
PCF-AM
VR/AR
UPF UPF SMF AMF NRF Back-up
16 Ericsson  | Dual-mode 5G Core: TCO benefits

Centralized authentication
and mobility management

This approach improves service availability and mitigates

TCO implications from traditional core security solutions in 5G Core.

The introduction of 5G Core for NR SA Figure 18: Common authentication and mobility
will add new and stronger requirements management in the dual-mode 5G Core solution
in terms of security, enhancing the
authentication and authorization 5GC EPC CS/PS Core
procedures in the core network to support
different devices (such as SIM- and
non-SIM based), different methods (such Centralized storage of common subscriptions and authentication data
as AUSF for EAP-AKA and non-AKA) and
stronger data protection mechanisms
(such as SUPI concealing and HSM).
In parallel, the existing authentication UDR
methods (AUC, AVG, AAA) used in EPC
must be supported in a harmonized
way, securing the proper coexistence Nudr
with the new ones, across the different
network accesses and domains. The
result is increased network complexity Centralized authentication and mobility management
and a variety of authentication and
authorization use cases. Ericsson’s
dual-mode 5G Core provides a centralized
solution for common authentication and High Security
mobility management (Figure 18) in a Module
single product, merging all mechanisms
for authentication and authorization of ARPF
different devices and all front-end (FE)
HSS EIR UDM AUSF HSM
applications to handle mobility
management for both 4G and 5G. This
approach significantly simplifies the
overall network architecture and the
MAP Diamater SBA
associated signaling, resulting in
25 percent capex savings on signaling Ud
resources for authentication.
HLR/AUC

25%
Capex savings of 25 percent in
CS/PS
Core
EPC 5GC

signaling for authentication and

mobility management are enabled.
17
Conclusion
The introduction of 5G Core will transform
the way core networks are built, managed
and operated. New network elements,
network architecture and technologies
such as cloud native will be introduced into
the core of the mobile networks for the first
time, challenging the status quo. Existing
operational procedures and sometimes
even organizational boundaries will need
to adjust to this new reality. This presents
a great opportunity for CSPs to improve
their TCO.
The adoption of these new technologies
will significantly improve and simplify how
things are done. The use of cloud native
technology and CI/CD tools, for example,
will drastically simplify operational
activities and increase agility to deploy
new software in the network in a way never
seen before. This will significantly reduce
the ttime to market for new services.
The smart packaging of NFs and the
multi-access support from Ericsson’s
dual-mode 5G Core solution will enable
Ericsson  | Dual-mode 5G Core: TCO benefits
infrastructure savings and more efficiency
to manage the existing 4G and the new 5G
traffic needs. It will
also allow for a smooth migration toward
5G Core following different business needs.
With the integration of new network
elements and the configuration of common
policies – activities that normally are
complex and time-consuming – CSPs will
experience a drastic reduction in execution
times, while adding an increased level
of security to protect the network from
potential traffic disruptions that could
impact the end-user experience.
The savings presented in this report
are just the beginning. Different networks
present different characteristics, use
varying operational procedures, provide
different end-user services and will benefit
from these new technologies in unique
ways. Ericsson is ready to support CSPs to
refine these and explore additional TCO
saving opportunities connected to their
specific realities.

Ericsson
SE- 417 56 Göteborg, Sweden
Telephone +46 10 719 0000
www.ericsson.com
Ericsson is one of the leading providers of Information
and Communication Technology (ICT) to service
providers, with about 40 percent of the world’s mobile
traffic carried through our networks. We enable the
full value of connectivity by creating game-changing
technology and services that are easy to use, adopt
and scale, making our customers successful in a fully
connected world. For more than 140 years, our ideas,
technology and people have changed the world: real
turning points that have transformed lives, industries
and society as a whole.
The content of this document is subject to 14/28701-FGB 101 0909
revision without notice due to continued © Ericsson AB 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