UDM

21.1.RC1
Product Description
 UDM
Product Description Contents

Contents

1 Background .................................................................................................................................... 1
1.1 Trend ............................................................................................................................................................................. 1
1.2 Challenges .................................................................................................................................................................... 2
1.3 5G Core Solution ..................................................................................................................................................... 2

2 Product Positioning ...................................................................................................................... 7

3 Product Highlights ...................................................................................................................... 10
3.1 Full-Convergent 5G Network ..................................................................................................................................... 10
3.2 Service-based Architecture ......................................................................................................................................... 11
3.3 Smooth Evolution ....................................................................................................................................................... 12

4 Typical Networking .................................................................................................................... 14

4.1 Typical 5G Core Networking ...................................................................................................................................... 14
4.2 Typical VoLTE Networking ........................................................................................................................................ 16
4.3 Typical IoT Networking .............................................................................................................................................. 17

5 Service Functions ........................................................................................................................ 19

5.1 2G/3G/4G Service Functions ...................................................................................................................................... 19
5.2 5G Service Functions .................................................................................................................................................. 26

6 Product Architecture ................................................................................................................... 38

6.1 System Architecture .................................................................................................................................................... 38
6.2 Service Architecture .................................................................................................................................................... 39

7 Operation and Maintenance ..................................................................................................... 42

8 Interfaces and Protocols ............................................................................................................. 45
8.1 UDM Service Interfaces ............................................................................................................................................. 45
8.2 USCDB Service Interfaces ......................................................................................................................................... 54
8.3 Maintenance Interfaces ............................................................................................................................................... 57

9 Reliability ..................................................................................................................................... 60
10 Security........................................................................................Error! Bookmark not defined.
11 Technical Specifications ..........................................................Error! Bookmark not defined.
12 Traffic Model .............................................................................Error! Bookmark not defined.
 UDM
Product Description Contents

13 Reliability Specifications ........................................................................................................ 62

 1 Background

1.1 Trend
Mobile communication has greatly changed people's lives, but the pursuit of high-
performance mobile communication has never stopped. The fifth-generation mobile
communication system (aka 5G) is introduced to cope with the explosive growth of mobile
data traffic, massive device connections, and various new services and application scenarios.
5G supports the enhanced mobile broadband (eMBB), ultra-reliable and low-latency
communications (URLLC), and massive machine-type communications (mMTC) use cases to
fit service requirements of network capability extremism and differentiation as well as
network convergence diversity, enabling a fully connected world.

Figure 1-1 5G service applications

⚫ eMBB
The technological breakthrough in spectrum utilization and bandwidth on the RAN side
enables 5G to provide a transmission rate faster than 4G. For example, only the 5G
 ultra-high bandwidth can meet the requirements of the popular AR/VR and HD video
live streaming. When you use VR to watch HD videos or play interactive games, data is
obtained through wired network cables. However, in the future you will be able to
connect to the 5G network without using network cables, and still experience fast
VR/AR services.
⚫ mMTC
5G can connect to 1 million devices per square kilometer, which may be more of
connection density on 4G. With the rapid development of smart cities, public facilities
such as street lamps, well covers, and water meters have network connection capabilities
and can be remotely managed. However, 5G will be more innovative. Based on the
powerful connection capabilities of 5G networks, public devices in all industries can
be connected to an intelligent management platform, these public facilities collaborate
with each other through the 5G network, and centrally managed by a small number of
maintenance personnel, greatly improving the operations efficiency of cities.
⚫ URLLC
The most typical application of 5G is autonomous driving. Large amounts of data need
to be processed instantaneously for multi-channel communication in common scenarios
of autonomous driving, such as sudden braking, vehicle-to-vehicle (V2V), vehicle-to-
person (V2P), and vehicle-to-infrastructure (V2I). Therefore, the 5G network must
provide ultra-low latency and ultra-high reliability to apply to these scenarios.

1.2 Challenges
During the evolution towards 5G, the core network still faces many challenges:
⚫ Long time to market (TTM) for new services
Traditional core network products are delivered based on the software package of a
single product. The development and testing periods are long, the delivery is slow, and
the impact of the upgrade on the live network is great. These products cannot cater for
diversified, flexible, and changeable 5G services. 5G services require a network that
supports fast service rollout and on-demand service provisioning.
⚫ Complex operations management and high costs
− The increasing service flexibility and complexity bring great challenges to the core
network service operations and network governance. The traditional network
operations management cannot cope with the development of 5G services. 5G
services require a network with full autonomy.
− Coexistence of 2G/3G/4G/5G networks and network evolution increases O&M
difficulties and operating expense (OPEX).
⚫ Bandwidth insufficiency and long latency
Rapid growth of service traffic and new services place higher demands on the core
network in terms of bandwidth and latency.
Evolution towards 5G requires a user-centered, application-driven, and highly autonomous
5G core network for agility, resilience, and robustness.

1.3 5G Core Solution

To bridge the gap in 5G, we has launched a brand new 5G Core solution. The solution is
powered by key technologies, such as Cloud Native, simplified convergence, and multi-access
edge computing (MEC). It is poised to build an intelligent network delivering a wide range of
services on demand, create an open ecosystem, and empower thousands of industries. The 5G
Core solution consists of multiple products, such as the Unified Network Controller (UNC),
Unified Distributed Gateway (UDG), Unified Data Management (UDM), Unified Policy
Control Function (UPCF), and Signaling Service Processing System (SPS). These products
work as different network functions (NFs), such as the AMF, SMF, UPF, NRF, NSSF, UDM,
and PCF, as defined by 3GPP. They also provide the functions of the EPC network through
4G and 5G convergence. In addition, the 5G Core solution provides end-to-end delivery of
everything from hardware to application software.

Figure 1-2 5G Core solution

Cloud Native:
It provides microservice-centric architecture, distributed data storage, stateless design,
and agile deployment that fit the development trends of 5G services. our 5G core network
software architecture inherits Cloud Native design concept to implement microservice-centric
architecture for software, support intelligent and on-demand network deployment, simplify
operations management, and help customers achieve business agility.
Service-based architecture (SBA):
⚫ 3GPP defines a brand-new core network using SBA, in which control plane NFs are fully
decoupled. Without using the point-to-point communication, SBA implements service-
oriented networking and plug-and-play NFs, making networks more agile and
accelerating deployments of required functions.
⚫ Service-based interfaces (SBIs) comply with the serial bus interface protocol, the
transport layer complies with the HTTP/2 protocol, and the application layer transmits
different service messages.
⚫ NFS Discovery
For refined management, 3GPP defines NFSs that each NF provides for the control
plane. These NFSs are used sequentially to complete mobile network signaling processes
from end to end, including registration, session management, mobility management,
authentication, and key negotiation. Take the AMF as an example. The AMF has four
NFSs responsible for communication services, mobile terminated (MT) services, event
exposure services, and location services (LCS), implementing mobility management,
 access control, and other functions. For details about NFSs, see WSFD-011138 SBI
interface.
Network slicing:
To meet different industry requirements on network resources, 5G Core solution provides
advanced slicing technologies to virtualize a physical network into multiple end-to-end
networks, each of which provides different network functions to meet different service
requirements. This solution flexibly allocates network resources based on service
requirements, provides differentiated connection services for different user groups, and
enables a diverse range of industries.
Various applications in vertical industries have various requirements for network functions,
such as network bandwidth, number of connections, delay, and reliability. These can all be
solved by 5G. The 5G standard classifies network function requirements of different services
into three use cases. The corresponding network slice types are eMBB slices, mMTC slices,
and URLLC slices.

Figure 1-3 Three typical slicing use cases

To fit eMBB and fixed wireless access (FWA) in early commercial scenarios defined by 3GPP
specification, 5GC provides two types of slices: UeMBB and FWA. These eMBB slices
defined by protocols. UeMBB slices are used to provide AR, VR, and HD video services.
FWA slices are used as a supplement to fixed broadband in densely-populated urban areas or
are used to provide last-mile coverage. It provides services for HD IPTV and VoIP services.
Figure 1-4 shows the characteristics of the two types of slices. UeMBB slices are mandatory
network slices that must be deployed by carriers. FWA slices are optional network slices that
can be deployed by carriers if required.

Figure 1-4 Network slices supported by 5G Core solution

Simplified convergence:
⚫ our 5G Core solution implements a simplified and convergent core network that supports
2G/3G/4G/5G network access. It simplifies network O&M and ensures smooth evolution
of existing networks, maximizing carriers' return on investment (ROI).
MEC:
⚫ Services can be distributed locally to help industry users implement local operations of
service data and provide differentiated services for subscribers at the network edge,
delivering an ultra-low latency experience to subscribers.
our 5G Core solution is based on the Cloud Native software architecture and supports key
cloud-based technologies, such as software decoupling, stateless design, cross-DC
deployment, microservice delivery, and A/B test, to provide optimal 5G experience for
customers. This solution involves multiple products, including the UNC, UDG, UPCF, and
UDM.
UDM
Product Description 2 Product Positioning

2 Product Positioning

3GPP has defined two types of network architecture: non-standalone (NSA) and standalone
(SA). Carriers can choose a suitable option to quickly launch their 5G services. UDM is
positioned as a unified user management product in the industry-leading Cloud Native
architecture for future 5G SA networks. It complies with 3GPP. The service-oriented
architecture design provides agile service development and service selection on demand,
enables flexible service orchestration and combination, and makes service innovation more
agile. In addition, to help carriers simplify the networking and facilitate smooth evolution to
the 5G SA network, the UDM integrates the functions of the UDM and AUSF in the emerging
5G network, manages the authentication data of 5G subscribers, and authenticates access for
5G subscribers. The UDM also provides basic network functions, such as mobility
management, access authentication, and service authorization, for traditional 2G/3G, EPS, and
IMS network subscribers. Table 2-1 describes the functions of UDM.

Table 2-1 Functions of UDM

Netwo Function
rk

5GC UDM serves as the UDM providing service processing functions defined by
network the N8 and N10 interfaces in 3GPP specifications. It stores the subscription data
and registration data of subscribers, delivers subscription data to the AMF/SMF,
and stores the address of the AMF serving subscribers.
UDM serves as the AUSF providing the service processing functions defined
by the N12 interface in 3GPP specifications, and receives signaling messages to
authenticate subscribers and networks.
Traditio ⚫ HLR on GSM/UMTS networks
nal ⚫ SAE-HSS on EPS networks
network
⚫ IMS-HSS on IMS networks
The UDM stores all subscriber-relevant data, including identities, authentication
data, subscription data, and location data. In addition, the UDM verifies mobile
terminals when they attempt to access networks.

The 5G core network uses the Service Based Architecture (SBA) to implement NFs plug-and-
play. Figure 2-2 shows the position of UDM on the SBA of 5G networks.
UDM
Product Description 2 Product Positioning

Figure 2-2 Position of UDM in the SBA

Figure 2-3 shows the position of UDM on 2G/3G/4G/5G networks.

UDM
Product Description 2 Product Positioning

Figure 2-3 Position of UDM on 2G/3G/4G/5G networks

 UDM
Product Description 3 Product Highlights

3 Product Highlights

3.1 Full-Convergent 5G Network

Services are diversified and various requirements are proposed on 5G networks, such as ultra-
HD videos, VR/AR, unmanned driving, and IoT. The massive volume of data must be stored,
managed, and intelligently analyzed. The advancement of mobile broadband technologies
during the evolution of traditional 2G/3G/4G networks towards 5G networks makes the
network increasingly complicated. Simplifying networking can efficiently reduce O&M costs.
The UDM, functioning as the unified data management center, provides carriers with
convergent data management for 2G/3G/4G/5G networking scenarios. The UDM features
efficient subscriber data processing, and simplified networking based on which existing
services are compatible and 5G services can be expanded. This reduces carrier operating
expense (OPEX) and capital expenditure (CAPEX). For details, see Figure 3-1.

Figure 3-1 UDM convergent data management

 UDM
Product Description 3 Product Highlights

The UDM supports the following aspects of 2G/3G/4G/5G network convergence:

⚫ Management convergence. With convergent subscriber data management, a unified
service provisioning system can be provided to provision 2G/3G/4G/5G/IMS network
services through a one-time configuration to enable subscribers to quickly register with
the services.
⚫ Storage convergence. The UDM integrates and stores 2G/3G/4G/5G subscriber data in
the HLR, HSS, UDM, and AUSF to implement centralized data management and reduce
losses during data migration between devices.
⚫ Service convergence. Dynamic resources can be shared for 2G/3G/4G/5G/IMS network
services, improving service continuity during handovers between networks.
The full-convergent network design provides the following benefits for carriers:
⚫ Convergent network deployment effectively saves network resources required during the
coexistence of 2G/3G/4G/5G networks.
⚫ Convergent network services ensure service continuity during the evolution from the 4G
network to the 5G network.
⚫ Unified O&M reduces O&M costs.

3.2 Service-based Architecture

To adapt to the scalability and flexibility of the 5G core network, the UDM uses the service-
based architecture. Modularization is used to achieve decoupling and integration between
NFs. With the service-based architecture, the UDM is divided into multiple different
microservices for independent development, deployment, test, upgrade, and O&M, making
the deployment more flexible. The service-based architecture supports agile service policy
development and A/B test, allowing for flexible service policy orchestration and combination,
and more agile service innovation. Figure 3-2 shows the advantages of service-based
architecture.

Figure 3-2 Advantages of service-based architecture

Figure 3-3 shows the service-based architecture. NFs serving as NRFs, such as UDM and
AUSF, can implement self-governance, self-discovery, and self-balancing to build a 5G core
network with full autonomy, helping carriers deploy simplified core networks and reduce
O&M costs. All NFs interact with each other over service-based interfaces. A service type can
be invoked by multiple NFs to reduce coupling defined for interfaces between NFs. This way,
all NFs can be customized on demand to flexibly meet requirements in different service
scenarios.
⚫ Self-governance: When an NF, for example, UDM or AUSF, becomes operative for the
first time, it automatically registers with the NRF and automatically updates its status.
 UDM
Product Description 3 Product Highlights

The NRF provides complete and automatic lifecycle management for the NF to make it
plug and play.
⚫ Self-discovery: An NF, for example, UDM or AUSF, can use the NRF to search for a
proper service producer rather than a fixed peer obtained from local configurations.
⚫ Self-balancing: The NRF detects faulty NFs, such as UDM and AUSF, in real time and
isolates them to prevent the faulty NFs from affecting overall system availability.

Figure 3-3 UDM service-based architecture

3.3 Smooth Evolution

The UDM is an NF in the 5G Core system. During 5G network deployment, carriers are most
concerned about how to reduce the impact on traditional networks, protect carrier
investments, and support smooth evolution from 2G/3G/4G networks to 5G networks. The
UDM provides the hybrid networking-based smooth evolution solution, helping carrier
networks smoothly evolve to 5G networks.

Hybrid Networking Solution

The UDM supports hybrid networking of cloud-based 5G devices and ATCA-based devices
on the live network, implementing smooth evolution from ATCA-based architecture to Cloud
Native architecture and protecting carrier investments. UDMs are added to form hybrid
networking with ATCA-based devices. Figure 3-4 illustrates the networking. The ATCA HSSs
form a service partition (SP), and the new UDMs form a virtualized routing service partition
(vRSP). The hybrid networking solution provides carriers with the following functions:
⚫ Service provisioning data is uniformly delivered from cloud-based 5G devices. Remote
provisioning sites (PSITEs) are deployed, and routing data is obtained based on the
subscriber number and forwarded to the corresponding BEs for processing. Routing data
consistency between the 5G and 4G devices is ensured through the reverse generation
mechanism and verification mechanism.
⚫ Hybrid network signaling can be between FEs. An FE receives a signaling request. If the
subscriber data is available in the local partition, the FE processes the request locally. If
the subscriber data is available in another partition, the FE forwards the request to
another partition's FE, ensuring service continuity.
⚫ Newly defined 5G subscribers are migrated automatically, or subscribers can be migrated
in batches by number segment. This helps carriers plan the upgrade from 2G/3G/4G
networks to 5G networks as required.
UDM
Product Description 3 Product Highlights

Figure 3-4 Hybrid networking

 UDM
Product Description 4 Typical Networking

4 Typical Networking

4.1 Typical 5G Core Networking

To meet the requirements of various services in the future and comply with the Cloud Native
concept for IT systems, the 5G core network architecture is transformed in two aspects
⚫ NFS: The control plane functions are abstracted into multiple network function services
(NFSs). Networks are built through softwarization, modularization, and Service Based
Architecture. NFSs are decoupled from each other.
⚫ CUPS: The user plane functions are decentralized, allowing them to be flexibly deployed
on the core network or deployed close to the radio access network (R)AN where
subscribers access.
To simplify core network O&M and ensure service continuity during handovers between
2G/3G/4G and 5G networks, carriers tend to deploy a 4G/5G convergent network. In this
network, the UDM integrates the functions of the UDM, AUSF, SAE-HSS, and IMS-HSS,
manages subscriber data uniformly, sends subscriber data to the 5G, 4G, and IMS networks as
requested, and manages subscriber authentication. Figure 4-1 shows typical 5G core
networking.
UDM
Product Description 4 Typical Networking

Figure 4-1 Typical 5G core networking

AMF: access and mobility SMF: session management NEF: network exposure
management function function function
NRF: network repository NSSF: network slice AF: application function
function selection function
PCF: policy control function UDM: unified data AUSF: authentication
management server function
SAE-HSS: System IMS-HSS: IP multimedia PCRF: policy and
Architecture Evolution-home subsystem-home subscriber charging rules function
subscriber server server
MME: mobility management SGW-C: serving gateway for PGW-C: PDN gateway
entity control plane for control plane
SGW-U: serving gateway for PGW-U: PDN gateway for UPF: user plane function
user plane user plane
AS: application server I-CSCF: interrogating-call S-CSCF: serving-call
session control function session control function
P-CSCF: proxy-call session eNodeB: E-UTRAN NodeB gNodeB: next generation
control function NodeB
 UDM
Product Description 4 Typical Networking

4.2 Typical VoLTE Networking

Figure 4-2 illustrates the typical networking for the VoLTE solution. VoLTE provides voice,
video, and data services with end-to-end quality of service (QoS) by overlaying the existing
CS network with an IMS and LTE network. The VoLTE solution helps carriers transition from
the existing 2G/3G networks to LTE networks, providing comprehensive voice services
instead of basic voice services. Subscribers can use LTE terminals to connect to LTE or
2G/3G networks. When subscribers move out of LTE coverage areas, the system routes their
calls to the nearest 2G/3G network. The solution also provides centralized service
provisioning, network management, and charging.
In the VoLTE networking, the UDM integrates the functions of the HLR, IMS-HSS, and SAE-
HSS, stores VoLTE subscriber-related data uniformly, sends data to the CS, IMS, and EPS
networks when requested, and manages subscriber authentication.

Figure 4-2 Typical VoLTE networking

EMS: element management SPG: service provisioning CCF: charging collection

 UDM
Product Description 4 Typical Networking

system gateway function

DMS: Data Management MMTel AS: multimedia SCC AS: service
System telephony application centralization and continuity
server application server
Anchor AS: Anchor IM-SSF: IP multimedia IP-SM-GW: IP short
application server service switching function message gateway
RCS AS: rich communication MRFP: multimedia I-CSCF: interrogating-call
suite application server resource function session control function
processor
S-CSCF: serving-call session BGCF: breakout gateway MRFC: multimedia
control function control function resource function controller
MGCF: media gateway BSF: bootstrapping server HLR: home location register
control function function
SAE-HSS: System IMS-HSS: IP multimedia eMSC: enhanced MSC
Architecture Evolution-home subsystem-home server
subscriber server subscriber server
SBC: session border P-CSCF: proxy-call IM-MGW: IP multimedia
controller session control function media gateway
MGW: media gateway S-GW: serving gateway P-GW: PDN gateway
MME: mobility management GGSN: gateway GPRS SGSN: serving GPRS
entity support node support node
E-UTRAN: evolved universal GERAN: GSM/EDGE UTRAN: universal
terrestrial radio access radio access network terrestrial radio access
network network

4.3 Typical IoT Networking

Narrowband Internet of Things (NB-IoT) is a cellular based narrowband IoT. NB-IoT is a new
technology in the IoT field. It supports the cellular data connection of low-power-
consumption devices in a wide area network (WAN) and is also called Low Power Wide Area
(LPWA). NB-IoT supports the efficient connection of devices with long standby time and
strict network connection requirements.
Figure 4-3 illustrates the typical networking for the IoT solution. In the IoT solution, the
UDM serves as an IoT-dedicated HLR/HSS for M2M terminal communication. It manages
subscription information, synchronizes terminal information, and supports M2M SIM card
theft protection and M2M terminal information sharing.
UDM
Product Description 4 Typical Networking

Figure 4-3 Typical IoT networking

SAE-GW: system architecture MME: mobility UDM: unified data

evolution gateway management entity management
SGSN: serving GPRS support GGSN: gateway GPRS MSC: mobile switching
node support node center
 UDM
Product Description 5 Service Functions

5 Service Functions

5.1 2G/3G/4G Service Functions

The UDM supports flexible subscriber data management and provides carriers with a menu of
services in response to the rapidly changing market.
Table 5-1 and Table 5-2 describe the basic key functions and highlighted service functions of
the UDM. For details about the services and functions, see Error! Reference source not f
ound.Error! Reference source not found..
UDM
Product Description 5 Service Functions

Table 5-1 Basic key functions

UDM
Product Description 5 Service Functions

Basic Description
Function
UDM
Product Description 5 Service Functions

Mobility Provides the access and mobility capabilities for UEs on a network and the
managemen service continuity capabilities for UEs during movement. On the network,
t the UDM stores the subscription data and dynamic data of subscribers,
delivers subscription data to the MME and MSC, and stores the addresses of
the MME and MSC serving subscribers. The UDM can flexibly manage
subscribers' access information. ARD and barring services are used to
flexibly manage subscriber access to networks.
UDM
Product Description 5 Service Functions

Basic Description
Function
UDM
Product Description 5 Service Functions

Basic Description
Function

Security On 2G, 3G, and 4G networks, the UDM supports the following
managemen authentication methods. Carriers can select authentication methods
t according to their policies.
⚫ GSM authentication
GSM authentication is a process of checking the validity of subscribers
who use SIM cards to access GSM networks, ensuring GSM network
security.
⚫ UMTS authentication
UMTS authentication provides mutual authentication between UMTS
networks and subscribers using USIM cards to access UMTS networks.
ensuring UMTS network security.
⚫ EPS-AKA authentication
EPS Authentication and Key Agreement (EPS-AKA) authentication
provides mutual authentication between EPS networks and subscribers
using USIM cards to access EPS networks. It requires that the access
network and the core network use different keys, ensuring the security of
access stratum (AS) and non-access stratum (NAS).
⚫ EAP-AKA/EAP-AKA' authentication
Extensible Authentication Protocol Method for UMTS Authentication
and Key Agreement (EAP-AKA) and EAP-AKA' authentication is used
for authenticating non-3GPP subscribers. When a non-3GPP subscriber
attempts to access an EPC network, the AAA and SAE-HSS exchange
information such as authentication information, subscription data, and
location information over the SWx interface to authenticate the
subscriber.
Subscriber The UDM provides flexible subscriber data management functions, such as
data defining and deleting 2G/3G/4G subscribers, changing SIM/USIM cards,
managemen changing MSISDNs, and modifying and querying subscription data.
t
UDM
Product Description 5 Service Functions

Basic Description
Function

Subscriber On 2G/3G/4G networks, the UDM can process requests for subscribing to or
data unsubscribing from subscription data changes. After the peer NE/NF
subscription subscribes to subscription data changes, the UDM promptly notifies the peer
and NE/NF of data changes. After the peer NE/NF unsubscribes from
notification subscription data changes, the UDM does not notify the peer NE/NF of data
changes. This function enables subscription data changes to be delivered
promptly, ensuring data consistency between NEs/NFs and improving
system reliability.

Table 5-2 Highlighted service functions

Basic Description
Function

Auto- Auto-Provisioning for VoLTE enables the HSS to provide voice over Long
Provisionin Term Evolution (VoLTE) services for 2G/3G or LTE subscribers who have
g for not subscribed to the VoLTE services and attempt to access an LTE or IMS
VoLTE network for the first time. With VoLTE auto-provisioning, subscribers can
use VoLTE services without changing their USIM cards and MSISDNs.
Auto-provisioning automatically enable subscribers with LTE, VoLTE, and
VoWiFi services to accelerate the development of these services.
 UDM
Product Description 5 Service Functions

Basic Description
Function

Supporting The Voice over WiFi (VoWiFi) service enables non-3GPP subscribers to
VoWiFi use IMS services, such as voice, SMS, and supplementary services, over
Wi-Fi connections. VoWiFi provides better indoor coverage and rich voice
service experience.
The VoWiFi service can be provided for a VoWiFi subscriber or a VoWiFi
Multi-SIM subscriber. Different from a VoWiFi subscriber who has only
one USIM card, a VoWiFi Multi-SIM subscriber has multiple terminals that
share one IMPU.

Supplement During LTE development, a carrier's LTE coverage is limited.

ary Service ⚫ When VoLTE subscribers are covered by LTE, they attach to the LTE
Data (IMS) network.
Consistency
⚫ When they are not, they attach to the carrier's 2G/3G (CS) network.
Between
CS and The Supplementary Service Data Consistency Between CS and VoLTE
VoLTE feature helps establish the following legacy 2G/3G services in an LTE
network to maintain consistent subscriber experience when subscribers
move between 2G/3G and LTE networks: supplementary services (SSs),
Operator Determined Barring (ODB), Customized Applications for Mobile
Network Enhanced Logic (CAMEL), Ring Back Tone (RBT), subscriber
category, video call, Local RBT (LRBT), PLMN specific supplementary
services (PLMNSS), enhanced routing, and expand enhanced routing.

5.2 5G Service Functions

The UDM supports flexible subscriber data management and provides carriers with a menu of
services in response to the rapidly changing market.
Table 5-3 and Table 5-4 describe the basic key functions and highlighted service functions of
the UDM. For details about the services and functions provided by the UDM, see Error! R
eference source not found.Error! Reference source not found..
UDM
Product Description 5 Service Functions

Table 5-3 Basic key functions

Basic Description
Function

Mobility Provides the access and mobility capabilities for UEs on a network and the
managemen service continuity capabilities for UEs during movement. On the network,
t the UDM stores the subscription data and registration data of subscribers,
delivers subscription data to the AMF, and stores the address of the AMF
serving subscribers. The UDM can flexibly manage subscribers' access
registration information. ARD and barring services are used to flexibly
manage subscriber access to networks.
UDM
Product Description 5 Service Functions

Basic Description
Function

Session Enables UEs to access packet data networks (PDNs) through a network and
managemen enjoy data services. Session management includes the session establishment
t and release. During the session establishment, the SMF sends a registration
request to the UDM to obtain the subscription data of a subscriber and
subscribes to the data from the UDM. The SMF sends a deregistration
request to the UDM during session release.
UDM
Product Description 5 Service Functions

Basic Description
Function

Security ⚫ UE identity confidentiality: The 5G network adopts a UE identity

managemen confidentiality mechanism to prevent transmission of the real identity of
t a UE over a network. The UE is used to encrypt the SUPI to generate a
SUCI. During the authentication procedure, the AUSF decrypts the SUCI
to the SUPI. The SUPI is transmitted only after the security context is
established.

⚫ Authentication: 5G has the unified 3GPP and non-3GPP authentication

methods. The AUSF supports EAP-AKA' and 5G AKA. The 5G AKA
implements the authentication among the UE, roaming network, and
home network, and EAP-AKA' implements bidirectional authentication
between the UE and home network. Carriers can select a required
authentication method based on their own policies.
UDM
Product Description 5 Service Functions

Basic Description
Function

Subscriber The UDM provides flexible subscriber data management functions, such as
data defining and deleting 5G subscribers, changing SIM cards, changing
managemen MSISDNs, and modifying and querying subscription data.
t

Subscriber On the 5G network, the UDM can process requests for subscribing to or
data unsubscribing from subscription data changes. After the peer NF subscribes
subscription to subscription data changes, the UDM promptly notifies the peer NF of data
and changes. After the peer NF unsubscribes from subscription data changes, the
notification UDM does not notify the peer NF of data changes. This function enables
subscription data changes to be delivered promptly, ensuring data
consistency between NFs and improving system reliability.

Network The UDM provides available slices and the default slice list for 5G
slice subscribers. During a service procedure, the AMF/SMF obtains subscribers'
managemen slice information from the UDM based on subscriber attributes and service
t types to manage slices on 5G networks.
UDM
Product Description 5 Service Functions

Table 5-4 Highlighted service functions

UDM
Product Description 5 Service Functions

Function Description
UDM
Product Description 5 Service Functions

4G-5G During the network evolution, carriers need to use existing 4G investments
interworkin to smoothly evolve to 5G networks. Therefore, the 4G and 5G networks will
g coexist for a long time. The UDM supports 4G-5G interworking. This
function ensures service continuity during handovers between 5G networks
and 4G networks, helping improve user experience.
As shown in Figure 5-1, there are two modes for 4G-5G interworking:
single registration and dual registration.
⚫ Single registration mode: When a UE switches between the 4G network
and 5G network, the UE can register with only one network. That is, the
UDM only stores the registration data of either the MME or the AMF.
If a UE has registered with the 4G network, an EPC-to-5GC handover is
triggered when the UE moves to the 5G network. The UE sends a
registration request over the 5G network through the AMF to the UDM.
After receiving the AMF registration information, the UDM clears the
MME registration information of the UE from the 4G network.
If the UE has registered with the 5G network, a 5GC-to-EPC handover is
triggered when the UE moves to the 4G network. The UE sends a
registration request over the 4G network through the MME to the UDM.
After receiving the MME registration information, the UDM clears the
AMF registration information of the UE from the 5G network.
⚫ Dual registration mode: When a UE switches between the 4G network
and 5G network, the UE can register with both networks.
If a UE has registered with the 4G network, an EPC-to-5GC handover is
triggered when the UE moves to the 5G network. The UE sends a
registration request to the AMF on the 5G network and completes the
location update through the SMF on the 5G network. The UDM uses the
PGW-C/SMF address on the 5G network to update the PGW-C address
stored on the 4G network and sends an address update notification to the
MME on the 4G network.
If the UE has registered with the 5G network, a 5GC-to-EPC handover is
triggered when the UE moves to the 4G network. The UE sends a
registration request to the MME on the 4G network and completes the
location update on the 4G network. The UDM uses the PGW-C/SMF
address on the MME of the 4G network to update the PGW-C/SMF
address stored on the 5G network and sends an address update
notification to the SMF on the 5G network.

Figure 5-1 4G-5G interworking procedure

UDM
Product Description 5 Service Functions

Function Description
UDM
Product Description 5 Service Functions

Function Description

5G auto- The 5G auto-provisioning function allows 4G subscribers using 5G

provisionin terminals in the 5G signal coverage area to access the 5G core network.
g When the UDM detects that subscribers have been provisioned with 4G
services, the subscribers are authenticated to ensure they are authorized. In
the AMF registration process, 5G services are automatically provisioned
through MML commands, or the UDM sends the service provisioning
system a notification message instructing the provisioning system to auto-
provision 5G services for the subscribers. For details, see Figure 5-2.
With this function enabled, subscribers can use 5G services without
changing their SIM cards or MSISDNs. When 5G services are provisioned,
subscriber data is migrated to the 5G network, implementing a smooth data
migration from 4G networks to 5G networks. After the provisioning system
auto-provisions 5G services for the subscribers who have subscribed to 4G
services but not to VoLTE services, if VoLTE services need to be
provisioned for the subscribers, the subscribers must be defined and VoLTE
services must be provisioned by the unified policy control function (UPCF),
E.164 number to URI mapping (ENUM), and application function (AF)
using the provisioning systems.

Figure 5-2 5G service auto-provisioning procedure

UDM
Product Description 5 Service Functions

VoNR Although data services drive 5G evolution, voice services are still important
services of carriers. The voice over NR (VoNR) provides the technology of
bearing voice over the 5G New Radio (5G NR), which features short call
setup time. The VoNR is an E2E voice solution based on the 5G NR
network, all-IP network, and IMS network. By deploying the IMS network,
VoNR enables the IMS to process CS services so that both CS and PS
services can be carried over the 5G network.
As shown in Figure 5-3, in the VoNR solution, the UE camps on the NR
network, and CS and PS services are processed on the NR network and
enjoy the 5G bandwidth. When the UE moves to the area with poor NR
coverage, the UE is handed over to the LTE network and VoLTE is used to
provide CS services.

Figure 5-3 VoNR service procedure

The key functions of the UDM in the VoNR solution are as follows:
⚫ 5G domain selection: When a UE initiates or receives a call, a network
must be selected to connect the call. This process is called domain
selection. During 5G domain selection, the SCC AS sends a request to
the UDM to obtain the T-ADS information. The UDM sends a T-ADS
query message to the AMF and MME to obtain the domain which the UE
accesses and the network on which the UE camps. Then, the UDM sends
a message containing the obtained information to the SSC AS.
⚫ 5G subscriber location and status query: Charging and location differ
between subscribers. The AS needs to obtain the current locations and
status of subscribers to implement service control during a call. The AS
obtains the locations and status of 5G subscribers from the UDM to
control, adjust, and provide high-quality services for 5G subscribers.
⚫ UE reachability management: This function is responsible for detecting
whether the UE is reachable and providing the UE location for the
network to reach the UE. When a UE has registered with the IMS
network and the SMSC receives an SMS request, the SMS message
cannot be delivered if the UE is temporarily out of the service area or
unreachable. In this case, the IP-SM-GW sends a UE reachability
subscription request to the UDM to detect the reachability status of the
UDM
Product Description 5 Service Functions

Function Description
UE. When the UE is reachable, the UDM instructs the IP-SM-GW to
trigger the short message resending procedure.
⚫ P-CSCF restoration: In VoNR scenarios, if the UDM detects that the P-
CSCF with which the called party is registered is faulty, the UDM
instructs the registered AMF to trigger the P-CSCF Restoration
procedure to recover the P-CSCF.
 UDM
Product Description 6 Product Architecture

6 Product Architecture

6.1 System Architecture

Figure 6-1 shows the system architecture that complies with the Network Functions
Virtualization (NFV) standards defined by European Telecommunications Standards Institute
(ETSI). Table 6-1 describes the key components.

Figure 6-1 System architecture

Table 6-1 Key components

Category Component

Hardware layer Common COTS devices, including servers, storage devices, and
network devices.
Virtualization Virtualizes hardware resources into virtual resources. The virtual
layer network supports EVS, OVS, and SR-IOV.
 UDM
Product Description 6 Product Architecture

Category Component

VNF layer EMS: a VNF management system. One or more EMSs can be
deployed to meet site requirements.
VNF: virtual network function entities, that is, service NEs hosted on
VMs.
⚫ CSP: provides unified, efficient, web-based, visual O&M functions
for applications.
⚫ USCDB: provides data storage, data management, and data services
for the UDM.
⚫ UDM: integrates and stores 2G/3G/4G/5G subscriber data to
implement centralized data management. The SBA architecture is
used to support quick service rollout and A/B test.
Operations Carrier operations support system and service support system.
support layer
Ma Applicatio VNFM: a VNF lifecycle management component, implementing VNF
nag n instantiation, scaling, and rebuilding.
em manageme
ent nt
Infrastruct FusionStage: a container management platform, implementing
ure container deployment and container resource management.
manageme FusionSphere: includes FusionSphere OpenStack and FusionSphere
nt OpenStack OM, which are used to manage the cloud OS and virtual
resources.
iMaster NCE-Fabric: SDN controller, implementing automatic
network deployment and configuration.
eSight: an NFVI O&M center that manages NFVI hardware and
topologies and provides O&M functions.

6.2 Service Architecture

The UDM consists of the front end (FE), back end (BE), and O&M system.
⚫ The FE functions as the HLR/HSS/UDM/AUSF to process the signaling and services on
2G/3G/4G/5G networks.
⚫ The BE provides data storage, data management, and data service for the FE.
⚫ The cloud service platform (CSP) functions as the O&M system. It provides unified and
efficient web-based visualized O&M functions for upper-layer applications, including
application lifecycle management and routine application O&M. Application lifecycle
management includes service governance and A/B test. Routine application O&M
includes security management, alarm monitoring, service monitoring, and log
management.
Figure 6-2 shows the UDM service architecture.
UDM
Product Description 6 Product Architecture

Figure 6-2 UDM service architecture

Service Description
Name

Convergent Provides the signaling processing subsystem for receiving and processing
HLR/HSS 2G/3G/4G signaling messages.
service
USCDB Provides data storage, data management, and data service of 2G/3G/4G/5G
service subscribers.
CSLB Forwards messages and balances the load at L3 (IP layer) and L4
service (TCP/SCTP/UDP layer).
UDM
Product Description 6 Product Architecture

Service Description
Name

HLB Manages HTTP2 signaling links.

service When the UDM works as the HTTP server, the HLB receives TCP
connection requests initiated by NFs, such as AMF and SMF, and maintains
and monitors the link status of the connections. The HLB forwards service
messages on the links to the UDM/AUSF microservice to share the load.
When the UDM works as the HTTP client, the HLB initiates TCP
connection requests to the NFs, such as AMF and SMF, if required, and
forwards the responses received from the AMF or SMF to the UDM/AUSF.
UDM Provides a unified entry for managing data, and implements the UDM
service function defined in 3GPP specifications.
AUSF Provides a unified entry for managing authentication, and implements the
service AUSF function defined in 3GPP specifications.
NRFClient Serves as an internal control and management service to manage network
service repository function (NRF) registration, update, discovery, and subscription
notification.
DCS service Manages the links of the HTTP client, including sending the link
configurations of the HTTP client to each HLB and receiving the link status
of HLBs. It reports the HTTP link status to the UDM/AUSF microservice
and processes the dynamic link establishment requests from the
microservice.
DBS service Serves as the data access service. It manages interconnection and interface
encapsulation between the FE and BE.
ACS service Serves as the application control service, which delivers the inter-service
communication policy and CSLB policy within an NF.
 UDM
Product Description 7 Operation and Maintenance

7 Operation and Maintenance

System O&M Architecture

On an NFV network, three key O&M components are defined in the O&M network
architecture: U2020/MAE, eSight, and CSP. To improve the O&M efficiency of the live
network, the U2020/MAE is defined as a unified O&M portal, as shown in the figure below.
⚫ The U2020/MAE functions as the unified portal of NFV network alarms and KPIs. It
provides VNF life cycle management, configuration management, performance
management, fault management, security management, log management, topology
management, software management, and system management functions.
⚫ The CSP is used as a local O&M portal of VNFs. Through the CSP, VNFs can
interconnect with the U2020/MAE, and the U2020/MAE can discover and manage VNFs
in a unified manner.
⚫ As a unified, fast NFVI O&M portal on the U2020/MAE, eSight provides O&M
interfaces and allows third-party hardware access.

Figure 7-1 System O&M architecture

 UDM
Product Description 7 Operation and Maintenance

System O&M Channels

The figure below shows key O&M channels between O&M components in the system O&M
architecture.

Figure 7-2 System O&M channels

Key O&M Capabilities of the CSP

In the system O&M architecture, the CSP provides a web-based, visualized O&M system
(hereinafter referred to as OM Portal). Table 7-1 describes the key O&M capabilities of the
OM Portal.

Table 7-1 Key O&M capabilities of the CSP

O&M Capability Description

Upgrade Provides application- or service-level software upgrade and

supports hitless, uninterrupted upgrade and rollback.
Patch You can install patches to fix application defects.
Backup and To prevent data loss due to system faults or emergencies, you are
restoration advised to back up key data before performing major operations,
such as upgrades and patch installation on applications. The system
can restore backup data.
UDM
Product Description 7 Operation and Maintenance

O&M Capability Description

License After basic data is configured, a license file needs to be loaded to

control resources and functions and allow customers to obtain the
services promised by the supplier.
MML configuration The system allows users to operate and maintain applications in the
MML window.
Alarms Manages microservice alarms and reports alarms. Allows you to
browse, export, and mask alarms, and configure alarms and their
aging periods.
Performance Provides microservice performance statistics, including
performance statistics tasks, performance model management, and
performance metrics calculation and storage.
Message trace Allows you to capture feature packets transmitted during service
procedures, facilitating fault demarcation and locating. If a service
becomes abnormal, you can create a trace task and use the traced
messages to quickly locate the fault.
Data collection ⚫ Data Collection: Provides a method for collecting information,
such as alarms, resource usages, logs, and configuration data to
assist in locating faults. If a service becomes abnormal, you can
create a collection task and use the collected information to
quickly locate the fault.
⚫ Inspection: Inspects service modules, databases, and devices to
detect potential risks before they cause any major issues.
Log management ⚫ Log Management: Allows you to centrally store service run
logs and download them in batches.
⚫ Service Logs: Collects service run logs generated within 7 days
of a service fault, improving O&M efficiency.
User management ⚫ Users: Displays all the created users. You can create users or
modify user information as required.
⚫ Roles: Displays created roles. You can create or delete roles and
configure users or user permissions for each role.
Security ⚫ Allows you to set accounts and password rules.
management ⚫ Allows you to set login IP address and time control policies.
After the policies are applied, you can log in to the system using
IP addresses within a specified range or within a specified
period.
 8 Interfaces and Protocols

The 5G UDM adopts the Service Based Architecture and introduces service-based interfaces,
in addition to traditional interfaces on 2G/3G/4G networks. All NFs on the control plane
interact with each other over service-based interfaces. A type of service can be invoked by
multiple NFs to reduce coupling for interfaces between NFs. This way, all NFs can be
customized on demand, flexibly meeting requirements in different service scenarios.
Interaction mode between NFs: The interaction modes are simplified as Request-Response
and Subscribe-Notify so that NFs can interact with each other over service-based interfaces.

8.1 UDM Service Interfaces

The UDM provides standard interfaces to flexibly interwork with other NFs using standard
protocols.
Figure 8-1 illustrates the interfaces between the UDM and other NFs.
Figure 8-1 Interfaces between the UDM and other NFs

AMF: access and mobility management SMF: session management function

function
SMSF: short message service function NRF: network repository function
MME: mobility management entity AAA: Authentication, Authorization and
Accounting
S4-SGSN: serving GPRS support node (S4 MSC: mobile switching center
interface)
VLR: visitor location register SMSC: short message service center
USSD center: unstructured supplementary SGSN: serving GPRS support node
service data center
GGSN: gateway GPRS support node HLR: home location register
SCP: service control point GMLC: gateway mobile location center
I-CSCF: interrogating-call session control IM-SSF: IP multimedia service switching
function function
AS: application server BSF: bootstrapping server function
U2020/MAE: iManager U2020/MAE -

Table 8-1 provides interface details.

Table 8-1 Interface details
Netw Int Interface Conn Protocol Interface Function Standar
ork erfa Name ected and ds
Entity ce NF Protocol Complia
Ty Stack nce
pe

UDM Ser N8 AMF HTTP/2 Used for registration 3GPP TS

vice management, mobility 29.503
- management, subscriber
base registration, and
d subscription data
inte delivery.
rfac
e
(SB
I)

N10 SMF HTTP/2 Used for session data 3GPP TS

management and 29.503
registration management.
Netw Int Interface Conn Protocol Interface Function Standar
ork erfa Name ected and ds
Entity ce NF Protocol Complia
Ty Stack nce
pe

N21 SMSF HTTP/2 Used for managing 3GPP TS

subscribers' SMS 29.503
subscription data and
registration information.

Nnrf NRF HTTP/2 Used by the UDM to 3GPP TS

register with or 29.510
deregister from the NRF.
Netw Int Interface Conn Protocol Interface Function Standar
ork erfa Name ected and ds
Entity ce NF Protocol Complia
Ty Stack nce
pe

AUSF SBI N12 AMF HTTP/2 Used to calculate 3GPP TS

authentication vectors 29.509
and select authentication
algorithms during 5G
access.

Nnrf NRF HTTP/2 Used by the AUSF to 3GPP TS

register with or 29.510
deregister from the NRF.

SAE- Non S6a MME Diameter Used to transmit 3GPP TS

HSS - subscription data and 29.272
SBI authentication data
between the MME and
the SAE-HSS to
authenticate subscribers
requesting access to EPS
networks.
Netw Int Interface Conn Protocol Interface Function Standar
ork erfa Name ected and ds
Entity ce NF Protocol Complia
Ty Stack nce
pe

SWx AAA Diameter Used to transmit 3GPP TS

authentication, 29.273
subscription, and
location data between the
3GPP AAA Server and
the SAE-HSS when
mobile stations attempt
to access Non-3GPP
networks.
S6d S4- Diameter Used to transmit 3GPP TS
SGSN subscription data and 29.272
authentication data
between the S4-SGSN
and the SAE-HSS to
authenticate subscribers
requesting access to EPS
networks.

SLh GMLC Diameter Used to transmit routing 3GPP TS

data related to location 29.173
services between the
SAE-HSS and the
GMLC.

HLR Non C MSC/S MAP Used to transmit routing 3GPP TS

- MSC data between the 29.002
SBI MSC/SMSC and the
HLR.
Netw Int Interface Conn Protocol Interface Function Standar
ork erfa Name ected and ds
Entity ce NF Protocol Complia
Ty Stack nce
pe

D VLR MAP Used to transmit location

and subscriber
management data
between the HLR and the
VLR.

Gr SGSN MAP Used to transmit

authentication and
subscription data
between the HLR and the
SGSN to authenticate
subscribers requesting
access to the PS domain.

Gc GGSN MAP Used to transmit

subscription and location
data between the HLR
and the GGSN during
calls in the PS domain.
Netw Int Interface Conn Protocol Interface Function Standar
ork erfa Name ected and ds
Entity ce NF Protocol Complia
Ty Stack nce
pe

J SCP/U MAP ⚫ Used to transmit

SSD location data and
center status information
between the HLR and
the SCP to implement
intelligent services.
⚫ Used to transmit
USSD service
requests and
responses between
the HLR and the
USSD center.

Lh GMLC MAP Used to transmit routing

data related to location
services between the
HLR and the GMLC.

- HLR SSAP Used to deliver 3GPP TS

Completion of Calls to 23.093
Busy Subscriber (CCBS)
service data between
HLRs.
Netw Int Interface Conn Protocol Interface Function Standar
ork erfa Name ected and ds
Entity ce NF Protocol Complia
Ty Stack nce
pe

IMS- Non Cx ⚫ I- ⚫ Diamet ⚫ Used to send the S- ⚫ 3GPP

HSS - CS er/SCT CSCF's capability set TS
SBI CF P requested by the I- 29.22
⚫ S- CSCF from the IMS- 8
CS HSS for the I-CSCF ⚫ 3GPP
CF to select an S-CSCF TS
to serve the calling 29.22
subscriber. 9
⚫ Used to send
restoration data
requested by the S-
⚫ Diamet CSCF from the IMS-
er/TCP HSS for the S-CSCF
to implement network
redundancy.

Gi GGSN RADIUS/ Used to transmit Early 3GPP TS

UDP IMS authentication data 33.978
between the GGSN and
the IMS-HSS.

Sh AS Diameter Used to send ⚫ 3GPP

subscription data TS
requested by the AS 29.32
from the IMS-HSS. 8
⚫ 3GPP
TS
29.32
9
 Netw Int Interface Conn Protocol Interface Function Standar
ork erfa Name ected and ds
Entity ce NF Protocol Complia
Ty Stack nce
pe

Si IM- MAP Used to transmit 3GPP TS

SSF subscribers' CAMEL 23.278
subscription information
(CSI) between the IM-
SSF and the IMS-HSS.

Zh BSF Diameter Used to deliver 3GPP TS

authentication vectors 29.109
and GBA user security
settings (GUSS) from the
IMS-HSS to the UIM
(BSF).

8.2 USCDB Service Interfaces

Figure 8-2 shows the protocol interfaces used by the USCDB to interwork with the peer NFs.
Figure 8-2 Protocol interfaces used by the USCDB to interwork with the peer NFs

Table 8-2 describes protocol interfaces supported by the USCDB.

Table 8-2 Protocol interfaces supported by the USCDB

Net Interfa Inter Protocol Interface Standards
wor ce worki Function Compliance
k ng NF
Ent
ity

US Data FE DCI A proprietary -

CD access interface used by
B interfac FEs to access data
e in the USCDB.
Net Interfa Inter Protocol Interface Standards
wor ce worki Function Compliance
k ng NF
Ent
ity

Subscri FE MCI A proprietary -

ption interface used by
notifica the USCDB for
tion data subscription
interfac notification to FEs.
e

Provisi Provisi SOAP/MML Used to interwork ⚫ SOAP 1.1

oning oning with the ⚫ SOAP 1.2
interfac system provisioning
e system to provision
services for
subscribers.
 Net Interfa Inter Protocol Interface Standards
wor ce worki Function Compliance
k ng NF
Ent
ity

FTP/SF FTP/S FTP/SFTP Used to interwork FTP/SFTP

TP FTP with a third-party
server FTP/SFTP server
to export or upload
database files.

8.3 Maintenance Interfaces

The figure below shows the maintenance interface relationship based on the NFV
architecture. The table below lists the major protocols in use.
Figure 8-3 Maintenance interface diagram

Table 8-3 Supported maintenance interfaces

Maintenance Interfaces Protoc Function
ol

NFVI (including hardware SNMP Allows hardware devices and FusionSphere

devices and FusionSphere v3 OpenStack to report alarms and performance
OpenStack OM) <-> eSight metrics to eSight after they are interconnected
with eSight.
eSight<->U2020/MAE SNMP Allows eSight to report NFVI alarms and
v3 performance metrics to the U2020/MAE. The
U2020/MAE displays the alarm and metric
information.
FusionSphere OpenStack <- REST Allows the VNF LCM to interconnect with
> VNF LCM (U2020 VNF FusionSphere OpenStack for VM life cycle
LCM/MAE-VNF LCM) management.
FusionStage<->VNF LCM REST Allows the VNF LCM to interconnect with
FusionStage for pod and container life cycle
management.
CSP<->OM Portal MML Allows you to deliver O&M commands to VNFs
on the OM Portal.
Maintenance Interfaces Protoc Function
ol

FTP ⚫ Allows you to upload license and system

backup files to the OM Portal.
⚫ Allows you to download logs, trace files, and
performance statistics from the OM Portal to
the local host.
CSP<->VNF LCM REST Allows you to manage VM life cycles.
CSP<->U2020/MAE MML Allows you to deliver O&M commands to VNFs
on the EMS.
SNMP Allows the CSP to report alarms to the EMS.
v3
SOAP Allows the CSP to report performance statistics
to the EMS.
SFTP Allows the CSP to upload license files to the
EMS.
VNF LCM<->U2020/MAE REST Allows the VNF LCM to report alarm and
performance metrics to the EMS.
UDM
Product Description 9 Reliability

9 Reliability

UDM stores subscriber data and its reliability is crucially important. A serious accident, such
as a misoperation, equipment failure, or natural disaster, will cause service interruption in
large areas and immeasurable losses. To ensure the high system reliability of mobile
networks, the UDM uses the distributed architecture, anti-affinity deployment, anti-split-brain
cluster, multi-level data backup, and seamless geographic redundancy.
0 illustrates the UDM reliability design.
UDM
Product Description 9 Reliability
UDM
Product Description 10 Reliability Specifications

10 Reliability Specifications

Table 10-1 lists the reliability specifications of the UDM.

Table 10-1 Reliability specifications

Item Details Remarks

Fault detection rate > 95% -

Mean time to repair (MTTR) <1h -
Return repair rate ≤ 0.3% -
Duration of service interruption ≤10s It takes 10 seconds or less for
caused by an upgrade active/standby switchover during
an upgrade.
Reliability Availability ≥99.9999% -
(redundancy NOTE
deployment) The availability
is calculated
according to the
product
reliability design
and product
usage at more
than 100 live
network sites.

Mean time 1,151,027 MTBF = (MTTR x

between hours/47,959 Availability)/(1 - Availability)
failures days
(MTBF)
Average ≤30s Average service interruption time
service in a year = (1 - 0.999999) x 8760 x
interruption 60
time in a year NOTE
A year is 8760 hours and an hour is 60
minutes.
UDM
Product Description 10 Reliability Specifications

Item Details Remarks

Reliability Availability ≥ 99.9998% -

(standalone NOTE
deployment) The availability
is calculated
according to the
product
reliability design
and product
usage at more
than 100 live
network sites.

Mean time 51,0967 MTBF = (MTTR x

between hours/21,290 Availability)/(1 - Availability)
failures days
(MTBF)
Average ≤30s Average service interruption time
service in a year = (1 - 0.999998) x 8760 x
interruption 60
time in a year NOTE
A year is 8760 hours and an hour is 60
minutes.