9 5G Core 20.X Basic O - M ISSUE 2.00

5G Core Basic O&M
www.huawei.com
Copyright © Huawei Technologies Co., Ltd. All rights reserved.

Objectives
 Upon completion of this course, you will be familiar with:

 Vision of 5G Core O&M solution
 Overall architecture of 5G Core O&M solution
 Principles and applications of 5G Core O&M key functions
Copyright © Huawei Technologies Co., Ltd. All rights reserved. 2

Contents
1. 5G Core O&M Design Objectives
2. 5G Core O&M Overall Architecture
3. 5G Core O&M Key Functions
4. 5G Core Common Commissioning Commands

5G Core O&M Design Objectives (Host Side)
Core objectives and principles: build service-
5G O&M Design Objective & Main Principle: Service centered O&M capabilities and experience.
Centered
Better Automation Provides unified O&M and
Ultimate
(Model-driven, data post-analysis)
experience optimized O&M
experience.
Automation Adapts to microservices, containers,
Cooperation Agile
Better experience dynamic slicing, CUPS, and MEC.
architecture
(Scenario-based, multi-
view) netconf/restfui API 5G O&M Framework Implements automatic
Network &Slice
Network & SliceView
view (Flexibility, agility, autonomy, management on the management
open, and multi-tenant)
plane, separation of logic and data,
Northbound Efficiency first
VNF2network model-driven, and what you see is
Interface Action
what you get (WYSIWYG).
VNFview
VNF View yang
Closed loop
Provides one-time full data
policy
Information Model Monitor&Analysis Data-driven source for quick data post-
VNF2ServiceGroup
analysis.
Service
Service Group view Neutral
Data Pipeline Provides scenario-based
(new) Configuration Scenario-
based configuration capabilities to
VNF2MicroService
Microservice
simplify O&M.
View
Supports the YANG model to meet
Micro-service view 5GC Managed Object
(Dynamic orchestration of managed objects, automatic interconnection
(Agile Oriented) self-discovery)
Automation requirements in different scenarios.
Frame
NSSF
work
SMF
UPF
NRF
AMF
Builds the basis for network-level

Evolution O&M and coordination in advance.

Contents

5G Core O&M Architecture Control flow
Network-level O&M center (NF FCAPS, big data, cross-layer demarcation and locating, slice O&M, automation, NBI, and life cycle
EMS (U2020) management)
Data flow
O&M access: API gateway Local web portal (emergency O&M)
O&M service governance

O&M access: interface protocol processing SNMP SFTP/FTPS SOAP NETCONF MML REST
CSR
Southbound interface object Local UI
O&M access: southbound interface management (EMS access and management model switching) Service registration and
management service
discovery
Local web integration
Intelligent fault management center (NF level) Scenario-based O&M center (NF level) SCS scenario-based collaboration service SCF
Self- Service orchestration
Demarcation and (configuration/maintenance) Software management center (NF level)
management and control
locating
self-healing
Backup and Software management process
Data collection Configuration center (service instance group level) Maintenance center (NF MMS
restoration engine service
ACS level) O&M model
ACS
DBMS Atomic ACS
configuration MNT License management service management
Atomic configuration
3rd Atomic
Configuration service configuration
service Maintenance
Monitoring management service group (NF
Performance Configuration database service
(Check/consistency/sub query service
level) (Check/consistency/sub Patch management service
(Check/consistency/sub
scription and release) Security center
measurement service (Service scription and release)
task neutrality) scription and release)
xDR data Gray release service
Post-analysis management HA
service (cluster) service Distributed communication service Reliability arbitration
Performance (control downlink) lighthouse
measurement
calculation Cluster
service (cluster) Business microservice Business microservice Business microservice Platform management
O&M data
service
Storage Alarm
management Third-party
Service Heterogeneou
Micro Service Micro Service Micro Service s service
VNFC Broker
Log
(Interface conversion
Service
and adaptation)
Distributed communication service (data uplink)
PaaS (FusionStage) Container deployment Software/Model repository

U2020 Portal Menu Overview

CSP Local Portal Menu Overview

Contents

Contents

3.1 Configuration Maintenance Function
3.2 Alarm Function
3.3 Performance Measurement Function
3.4 Trace Function
3.5 Log Function
3.6 Information Collection Function
3.7 License Function
3.8 Scaling
3.9 Pool Maintenance

Configuration Maintenance Basic Principles
MML U2020 Portal Service Role in Configuration
configuratio (Centralized NMS O&M) 5GC VNF MML service. It receives MML commands, converts
n MML
them into internal command formats, and delivers them to
U2020 downstream services as defined in the model. It is included in
the framework NF and provides services for other NFs.
SBI (mml) It forwards NETCONF messages and is included in the
OMG
NF (UNC/UDG) framework NF and provides services for other NFs.
5GC VNF configuration center. It stores configuration data

persistently and notifies downstream services that subscribe to
ACS
Framework (NF) App Service (NF) the configuration data in case of data changes. It is included in
the framework NF and provides services for other NFs.
CSP Portal
5GC VNF maintenance center. It receives maintenance
(Local emergency Micro commands, processes the commands, and delivers the
O&M) Service MNT commands to the downstream services that subscribe to the
commands. It is included in the framework NF and provides
MML ACS YANG services for other NFs.
schema Business microservice. Each network function (NF) contains a

schema
Macro.ini Micro certain number of business microservices. The microservice
YANG Service subscribes to and obtains configuration data from the ACS or
Process description
MNT.
1. The operator logs in to the NMS or the local CSP portal, edits
App Service (NF)
an MML command, and delivers it.
OMG MNT 2. The configuration maintenance center processes the MML
Micro (data validity check and object relationship check) logic. In
schema schema case of a configuration operation, the configuration
Service
YANG YANG maintenance center writes the configuration data into the
YANG database for persistent storage, and displays a success or
Configuration
schema failure message on the GUI.
command 3. The microservice reads the configuration data from the
Maintenance configuration maintenance center or receives maintenance
command commands for processing based on the subscription and
releasing relationship.

Configuration Maintenance Operation on U2020 Portal
For 5GC 20.0, choose VNF_Type

> VNF_version > VNF_instance.
More NF layers will be added in
the future.

Configuration Maintenance on CSP Portal
Displays the executed

commands, execution results,
and details.
Displays the command scripts to be

delivered. You can also copy multiple
command scripts to this area and
deliver them in batches.
MML navigation bar: displays

all MML commands of a VNF
by domain and function.

Secondary Authorization of High-Risk MML Commands
The U2020 or CSP portal supports secondary authorization of high-risk

MML commands. When a user runs an MML command whose execution
will have a significant impact, the second user who has the secondary
authorization permission needs to confirm the operation. Users are
allowed to:
 Run SET SECAUTH to enable or disable secondary authorization.
 Run LST SECAUTH to check whether the secondary authorization
function is enabled.
 Run ADD SECAUTHMEM to add a secondary authorization MML
command.
 Run RMV SECAUTHMEM to delete a secondary authorization MML
command.
 Run MOD SECAUTHMEM to modify secondary authorization
prompt information.
 Run LST SECAUTHMEM to list secondary authorization MML
command.
If a batch MML script contains multiple high-risk MML commands that
require secondary authorization, secondary authorization authentication
is performed only once.

Introduction to the Offline MML Query Tool
 The offline MML view tool simulates the MML command interface so that users can view
the MML commands, input parameters, and command help of each NF in the 5G Core
solution in offline mode. The tool can be used to perform basic syntax check on input
parameters, but cannot be used to perform semantic check or check the logical relationship
between MML commands.

Contents

3.2 Alarm Function
3.4 Trace Function
3.5 Log Function
3.8 Scaling

Alarm Function Basic Principles
Alarm browse and handling Service Role in Alarm Function
5GC VNF alarm service. It is used to store VNF

FMService alarms, interconnect with the NMS, and report
alarms to the NMS.
U2020 Portal Business microservice. The alarm agent is

U2020 (Centralized NMS deployed in the microservice, and reports
Micro Service
alarms to the alarm service and manages
O&M)
other alarms.
SBI (snmp)
Process description
NF (UNC/UDG) 1. The CSP alarm service FMService manages alarms for
CSP Portal 5GC NFs.
FMService (Local emergency 2. The alarm client is deployed on the new 5GC
O&M) microservice. The alarm client reports alarms to the CSP
alarm service.
3. The CSP alarm service reports alarms to the U2020
through the SNMP interface.
Micro Micro 4. You can view and handle alarms on the U2020 portal or
Service Service CSP portal.

Alarm Operation on U2020 Portal
Click Monitor. The real-time alarm browse page is displayed.
Alarm display: Objects are displayed

by product, and location information
Alarm filter:
is displayed in a structured manner,
Alarm location information such as Service Group and Service.
can be filtered by keyword.

Alarm Operation on CSP Portal
Click Monitoring. The real-time

alarm browse page is displayed.
You can configure alarm

aging policies on the
Expiration page.
You can configure alarm

masking policies on the
Configuration page. Masked
alarms are not displayed on the You can select an alarm on performance
GUI. measurement alarm browse page to mask
the alarm. The alarm will not be displayed
later. You can also set the alarm masking
policy in Configuration in the navigation
tree on the left.

Contents

3.2 Alarm Function
3.4 Trace Function
3.5 Log Function
3.8 Scaling

Performance Measurement Basic Principles
U2020 Portal Performance Service Role in Performance Measurement
measurement task
(Centralized Performance 5GC VNF performance management service. It is used to interconnect with the
NMS O&M) measurement data U2020, manage performance measurement tasks, and report performance
PMSMgr
browse measurement files to the U2020. The PMSMgr needs to synchronize tasks to all
the performance measurement clients in the system.
U2020 5GC VNF traffic statistics calculation service. It provides N-way load sharing. It
receives original traffic statistics data reported by downstream services from
PMSCalc the O&M bus, calculates the data based on the counter algorithm in the
SBI (soap+sftp) performance measurement model, and generates performance measurement
result files.
NF (UNC/UDG) Business microservice. The traffic statistics agent is deployed in the service. The
Micro traffic statistics agent collects the original traffic statistics data of the service
Service and sends the data to the O&M bus. The O&M bus forwards the data to the
PMSMgr specified PMSCalc service instance.
Process description
1. O&M personnel select a measurement object or measurement unit on the NMS
PMSCalc and create a performance measurement task.
2. The NMS sends the task to the performance management microservice (task
management) of the NF over the SOAP interface.
3. The microservice proactively reports the status data generated during service
processing (reported in records).
Performance 4. The performance management microservice (performance analysis and
measurement Micro Micro calculation) processes and calculates data, generates measurement results, and
task reports the results to the NMS.
synchronization
Service Service
5. O&M personnel can browse performance measurement results on the NMS.
Performance
Remarks: The CSP portal does not support performance management and
measurement
data reporting browse. Currently, only the 5-minute and 30-minute periods are supported.

Performance Measurement on U2020 Portal
(1) Choose Performance > Measurement
Management. The Measurement
Management page is displayed.
(4) Select the measurement

period and measurement
counter.
(2) Select measurement

counter units by
measurement object or
measurement family.
(3) Select an NF instance. (4) Select

measurement object
instances.

Contents

3.2 Alarm Function
3.4 Trace Function
3.5 Log Function
3.8 Scaling

Trace Function Basic Principles
Service Role in Tracing Function
CSP Portal User trace
(Local O&M) Interface trace
Trace management service of the 5GC VNF, It is used to create,
delete, and browse trace tasks and download trace result files.
MsgTrace In addition, the trace service needs to synchronize trace tasks to
SBI (rest) each trace agent and periodically check the tasks with the trace
agent.
NF (UNC/UDG)
Service micro service. The tracing agent is deployed in the service
micro service. The trace agent sends traced messages of the
Micro Service
service micro service to the trace service. In addition, this module
MsgTrace works with the trace service to check trace tasks.
Process description
1. O&M personnel create tracing tasks (user tracing and interface tracing) on the
local CSP portal and deliver the tasks to the CSP tracing service MsgTrace
through the REST interface.
2. Microservices subscribe to trace tasks. When trace filtering conditions are
matched, the microservices report the tracing results to the tracing
Micro Micro management service.
Service Service 3. The trace management service summarizes the messages reported by the trace
tasks and reports the messages to the U2020 or local web portal.
4. O&M personnel view the tracing result on the CSP portal.
Trace task synchronization Remarks: Currently, the U2020 does not support 5GC NF trace.
Traced message reporting

Trace Operation on CSP Portal (1) Choose Monitoring > Message Trace. The
Message Trace page is displayed.
Click Expiration and set

the parameters related to
the trace function.
(3) View historical trace tasks and

download trace files. You can a task
to browse the traced messages.
(2) Click an object to be traced and

click Add to create a trace task.

Contents

3.2 Alarm Function
3.4 Trace Function
3.5 Log Function
3.8 Scaling

Log Function Basic Principles
Service Role in Log Function
Log browsing
5GC VNF run log management service. It collects and
stores run logs of services in the VNF. It provides log
RunLog
policy configurations, such as log print levels, and
synchronizes the configurations to each log client.
U2020 Portal 5GC VNF operation log and security log management
U2020 (Centralized AuditLog service. It Records and stores various operations and
security events on the VNF.
NMS O&M)
SBI Business microservice. The log agent is deployed in the
(rest) microservice. The log agent sends logs of the service to
NF (UNC/UDG) CSP Portal Micro Service the log service in real time. In addition, it receives the log
print policy and controls the log level printed by the
(Local service.
RunLog
emergency Process description
O&M) 1. Logs are printed during microservice running. The log
AuditLog management service is responsible for unified log collection,
persistency, and periodic clearing.
2. Operation logs and security logs are periodically uploaded to
Micro Micro the U2020 and can be queried by operators. Run logs can be
Service collected using the information collection tool for problem
Service
analysis.
Remarks:
(1) Currently, only log data sources are provided by NFs. The log
analysis system is not deployed.
(2) Large-granularity service logs cannot be reported to the OMB.

(1) Choose Security > Operation
Logs or Security Logs. The
Log Operation on U2020 Portal Operation Logs or Security Logs

page is displayed.
(2) Logs can be filtered and

browsed by date.

Log Operation on CSP Portal
(1) Choose Security > Logs. The operation log
and security log browsing and related
configuration page is displayed.
(2) Logs can be filtered and browsed

by condition.
(2) Logs can be filtered and

browsed by condition.
Click Expiration.
Click Expiration.
You You
can set log
can set log
parameters
parameters
on the on the
displayed
displayed
page. page.

Contents

3.2 Alarm Function
3.4 Trace Function
3.5 Log Function
3.8 Scaling

Information Collection Basic Principles
Service Role in Information Collection
U2020 Portal
CSP Portal
(Centralized NMS CHR service in the 5GC system. It obtains CHR data
(Local emergency CHR from other services and generates and stores CHR
O&M) files.
O&M)
File transfer service in the 5GC system. All files are
U2020 FileServer transferred to the FileServer first. The FileServer
then transfers files to external systems.
Service used by the local portal to collect
CollectAndCheck
NF (UNC/UDG) information.
Process description
FileServer(FT)
1. On the CSP portal, collect run logs, operation logs, alarm logs, and
CHRs in one-click mode based on fault scenarios and fault
handling scenarios. Accident scenario: The information collected
at a time can be used to recover 80% accidents. Within 5 minutes,
collect less than 10 MB information for each application. The
Auditlog CHR MML Runlog FMService LicMgr PMSMgr collection period is one day. Fault handling scenarios: The
information collected at a time can be used to locate 70% faults.
Within 10 minutes, collect less than 200 MB information for each
OMG application. The collection period is three days.
2. You can run EXP MML to export the configuration to a file and
download the file on the CSP portal.
Micro Service Micro Service 3. Performance measurement data cannot be exported in one-click
mode. You need to view the data on the U2020 or create an
export template to export the data.
Remarks: The 5GC 20.0 release 1 does not support scenario-based
CollectAndCheck one-click collection for 5GC NFs. The 5GC 20.0 release is developing
the one-click collection function on the U2020.

Information Collection on CSP Portal
(1) Choose Monitoring > Data Collection.

The local data collection page is displayed.
(2) Click Create to create an

information collection task.
(3) Select the NF. Currently, the CSP is

deployed in built-in mode and only
one NF can be selected.
(6) View the collection task
and progress.
(4) Select a collection

scenario.
(5) Select the collection

period.

Information collection on the U2020 (1)
Information collection based

on predefined scenarios

Information collection based

on customized collection
items

Selected customized
collection items

View the information

collection progress.
Download the
information collection
result.

Contents

3.2 Alarm Function
3.4 Trace Function
3.5 Log Function
3.8 Scaling

License Function Basic Principles
Service Role in License Function
CSP Portal Viewing
(Local O&M) Management 5GC VNF license management service. It is used to manage license
files, manage ESNs, and perform operations. After license items are
LicMgr
updated, the license management service synchronizes the updated
SBI (rest) license items to each license client.
5GC VNF license control service. It is used to monitor resource
NF (UNC/UDG)
LicCtrl items, generate alarms, and collect peak values. The license control
service obtains license item usage data from the license client.
Business microservice. The license agent synchronizes license item
LicMgr Micro Service information from the license management service and reports
LicCtrl license item usage data to the license control service.
Process description
1. O&M personnel import and activate the license file, and query for the license
information on the local CSP portal.
xx
Micro Micro 2. The license management service is responsible for parsing and verifying the
Service Service validity of the license file, and processing the commands for activating the
license issued on the GUI.
3. The microservice subscribes to license information (control items and resource
items) from the license management service.
Remarks: Currently, the U2020 does not support 5GC NF license management.

License Operation on CSP Portal - License File
Management
Choose Application Lifecycle > Licenses > License

File Management from the main menu. The
License File Management page is displayed.
Upload and export the license file.
View details about the uploaded license file, and

download, delete, revoke, and compare the
license file. The license file that is being activated
cannot be deleted, revoked, or compared.

License Operation on CSP Portal – License Management
Choose Application Lifecycle > Licenses >
License Management. The License
Management page is displayed.
View the basic information about
the activated license. It supports
operations such as activation,
emergency starting, update,
license invalidation and
comparison.
View details about the activated license items.

MML Commands for Viewing License Information
Run DSP LICENSE to view the detailed

information about the activated license
items.

Contents

3.2 Alarm Function
3.4 Trace Function
3.5 Log Function
3.8 Scaling

Basic Scale-Out Principles and Operations (Without a Plan)
The VM scale-out process is as follows:
1. The O&M personnel scale out the application's VM on the LCM O&M client.
2. After creating a VM, the VNFM instructs the PaaS to manage the VM.
VNF VNFM PaaS 3. The PaaS processes the VM node and updates the node status after it starts managing
LCM Portal the node.
4. After verifying that all nodes have been managed, the VNFM returns a message
ScaleOut VM
indicating that VM scale-out has succeeded.
Merger/Add Node
Ack() The pod or application scale-out process is as follows:
[Loop]Query Node Status 1. After VM resources are available, the O&M personnel scale out the pod or application
Ack() on the LCM O&M client.
ScaleOut VM Ack 2. The VNFM sends a pod scale-out pre-notification message to the VNF.
3. The VNF processes the pod scale-out pre-notification message received from the VNFM
ScaleOut Pod
and feeds back the processing progress.
PreScaleOut_Ex(app_list,number)
4. After determining that the VNF has processed the pre-notification message, the VNFM
Ack()
sends a stack pod scale-out message to the PaaS.
[Loop]Notify Completion(100%) 5. The PaaS processes the pod scale-out request and updates the stack status after the
Ack()
DoStackLifeCycle() processing succeeds.
Ack() 6. After verifying that all pods have been created and the stack status is normal, the VNFM
[Loop]QueryStack() sends a pod scale-out post-notification message to the VNF.
Ack()
PostScaleOut_Ex() 7. The VNF processes the pod scale-out notification message received from the VNFM and
Ack() feeds back the processing progress.

8. After determining that the VNF has processed the post-notification message, the VNFM
[Loop]Notify Completion(100%) returns a message indicating that pod or application scale-out has succeeded.
Ack()
Remarks
ScaleOut Pod Ack
 To prevent stack exceptions caused by resource insufficiency, scale out VMs and pods
in turn.
 For details about the restrictions and constraints, see a VNF scaling guide.
Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 43

Basic Scale-In Principles and Operations (Without a Plan)
The pod or application scale-in process is as follows:
1. The O&M personnel scale in the pod or application on the LCM O&M client.
VNF VNFM PaaS 2. The VNFM sends a pod scale-in pre-notification message to the VNF.
LCM Portal 3. The VNF processes the pod scale-in pre-notification message received from the VNFM
and feeds back the processing progress.
ScaleIn Pod 4. After determining that the VNF has processed the pre-notification message, the VNFM
PreScaleIn_Ex(app_list,number) sends a stack pod scale-in message to the PaaS.
Ack() 5. The PaaS processes the pod scale-in request and updates the stack status after the
[Loop]Notify Completion(100%) operation succeeds.
Ack() 6. After verifying that all pods have been scaled in and the stack status is normal, the
DoStackLifeCycle()
VNFM sends a pod scale-in post-notification message to the VNF.
Ack()
[Loop]QueryStack() 7. The VNF processes the pod scale-in post-notification message received from the
Ack() VNFM and feeds back the processing progress.
PostScaleIn_Ex()
8. After determining that the VNF has processed the message, the VNFM returns a
Ack()
message indicating that pod or application scale-in has succeeded.
[Loop]Notify Completion(100%) The VM scale-in process is as follows:
Ack() 1. After a pod or application is scaled in, the VM previously used for the pod or
ScaleIn Pod Ack application may be idle. In this situation, the O&M personnel may scale in the VM on the
LCM O&M client as required.
ScaleIn VM 2. The VNFM sends a VM node unmanagement request to the PaaS.
No Merger/Del Node
3. The PaaS cancels the management of the VM node and updates the node status.
Ack()
[Loop]Query Node Status 4. After verifying that all nodes are no longer managed, the VNFM returns a message
Ack() indicating that VM scale-in has succeeded.
ScaleIn VM Ack Remarks
 To prevent stack exceptions caused by resource insufficiency, scale in pods and VMs
in turn.
 For details about the restrictions and constraints, see a VNF scaling guide.

Contents

3.2 Alarm Function
3.4 Trace Function
3.5 Log Function
3.8 Scaling

Creating a Pool
On the U2020, choose Maintenance > CN Pool Management.
Choose Maintenance.
Choose CN Pool
Management.

Creating a Pool (Continued)
1. In the navigation tree, choose AMF Pool.
2. Click + to create a pool.
3. Enter a pool name.
4. View all AMFs on the U2000 and select the AMFs to be used to form a pool.
2. Add a pool.
3. Enter a pool name.
1. Choose AMF
Pool.
4. Select the AMFs to be

used to form a pool.

Pool O&M
Select specific functions to

perform pool O&M.
A pool is created.

Pool O&M Functions
The pool O&M functions include the following:
 Data check
On a network that uses an AMF pool, some configurations must be the same on all AMFs, while some
configurations must be unique on all AMFs, which ensures that the pool runs properly. The U2020 provides
a data check function. Based on the data check results, you can perform O&M operations to ensure that
configurations meet requirements.
 Check rule
If the system's default check rule cannot meet requirements, you can add, modify, enable, or disable the
check rule as required or use a modified check rule as the default one.
 Subscriber migration
The system's load balancing algorithm maintains the load balancing in the AMF pool in normal situations.
However, the load may be imbalanced during VNF upgrades or network adjustment. If this happens, you
can manually migrate subscribers from one AMF to another using the U2020 to balance the load among all
AMFs in the AMF pool.
 Subscriber query
You can use the subscriber query function of the U2020 to quickly locate the AMF to which a subscriber
belongs within an AMF pool.

Contents

5G NFs and interfaces
NSSF NEF NRF PCF UDM AF
Nnssf Nnef Nnrf Npcf Nudm Naf

Nausf Namf Nsmf
AUSF AMF SMF
N2 N4
UE (R)AN N3 UPF N6 DN

External Interface Commissioning and Maintenance
Commands
 PING is the most commonly used method for checking device reachability. ICMP packets are used
to check whether the remote device is reachable and to test the round-trip delay and packet loss
rate.
 Example:
PING: IPVERSION=IPv4, DESTIPV4ADDRESS="10.137.144.1";
Reply From 10.137.144.1: Number of bytes = 56 Sequence number = 1 Time to live = 255 Round trip time = 1 ms
Reply From 10.137.144.1: Number of bytes = 56 Sequence number = 2 Time to live = 255 Round trip time = 1 ms
******
--- 10.137.144.1 ping statistics ---
Number of sent packets: 5
Number of received packets: 5
0.00% packet loss

Commands (Continued)
 LST INTERFACE: This command is used to query information about physical or logical interfaces
on the UDG.
 Example:
%%LST INTERFACE:; %%
RETCODE = 0 Operation succeeded
The result is as follows:
---------
Interface Name Interface Type Interface Type Interface Number Interface Description Management Status
Interface MAC Address VPN Instance Name
Ethernet64/0/5 Main Interface Ethernet 64/0/5 NULL Interface Up FA16-3E0A-0474 _public_
Ethernet64/0/6 Primary interface Ethernet interface 64/0/6 Null interface Up FA16-3E0F-0C04 _public_

 DSP SRROUTE: displays detailed information about configured IPv4 static
routes.
 Example: DSP SRROUTE:;

Address Family = IPv4 Unicast
VPN Instance Name = _public_
Route Prefix = 10.0.0.1
Route Mask Length = 32
Route Interface Name = NULL0
Next-Hop VPN Name = _public_
Route Next Hop = 10.0.0.2
Route Priority = 125
******

 LST AUTOSCALINGSRROUTE: You can run this command to query the added routes if the
automatic route configuration mode is used.
 Example:
%%LST AUTOSCALINGSRROUTE:;%%
Address Family = IPv4 Address Family
Service Name = ServName_Access_2011
VPN Instance Name = VRF_Access
Route Prefix IPv4 = 172.23.1.63
Route Mask Length = 32
IPv4 Route Next Hop Assignment Mode = User Configuration
Route Next Hop IPv4 = 172.22.12.1
Route Priority = 60

NG-AP Interface Commissioning and Maintenance
Commands
 DSP NGAPLINK: used to query the NGAP link information and check whether the NGAP link is normal.
 Example:
%%DSP NGAPLINK: OUTPUTTYPE=Screen;%%
RETCODE = 0 Operation succeeded AMF RAN
--------
SCTP Association ID Local IPv4 Address 1 Local Port No. Peer IPv4 Address 1 Peer Port No. Link Status
1375827 172.22.12.49 38412 172.23.1.63 3914 connected mode

NG-AP Interface Commissioning and Maintenance
 DSP NGPAGING; This command is used to query the NG paging table information of the
UNC system. The NG paging table records information about access network devices
connected to the UNC and TAIs supported by the access network devices.
 Example:
%%DSP NGPAGING:; %%
--------
PLMN NG-RAN Base Station Type NG-RAN Base Station ID Tracking Area ID gNodeB ID
Length (bit)
46088 Global gNB 65 46088000001 22

N3 Interface Commissioning and Maintenance Commands
 TST PATH: This parameter specifies whether the UDG sends heartbeat detection messages
to the peer NE.
 Example:
TST PATH: SPUGROUPID=1, IPVERSION=IPV4, LOCALIPV4="172.22.12.50",

PEERIPV4="172.23.1.65", VPNNAME="VRF_Access", PROTOCOLTYPE=GTPV1
UPF RAN

• Example:
DSP PFCPASSOC: UERYTYPE=All;
 DSP PFCPASSOC: used to The result is as follows:
query the PFCP association Query type = All
UP Unique ID = upf_instance_0
status and local and peer IP
UpNodeId fqdn value
addresses on the SMF. =UPF1.MNC000.MCC460.3GPPNETWORK.ORG
Local IP address1 = 172.22.12.114
Local IP address2 = NULL
Local port number = 8805
Peer IP address 1 = 172.22.12.115
Link 1 state = Normal
SMF UPF ******
Peer port number = 8805
Association status = Normal
Weight = 0

- Continued
 DSP CPINFO: used by the UDG to dynamically query CP information. The query result
includes the CP node ID, CP IP address, and status of the path between the UDG and CP.
 Example:
%%DSP CPINFO: QUERYTYPE=IP, IPVERSION=IPV4, CPIPV4="172.22.12.114";%%
RETCODE = 0 Operation succeeded.
CP information;
--------
CP Information =
CP Node ID CP IP Address CP State
172.22.12.114 172.22.12.114 UP
ALL CPInfo Number = 1

SBI Commissioning and Maintenance Commands
 DSP SBILINKSTATUS: used to check the SBI link status.
 Example:
%%DSP SBILINKSTATUS: ENTITYTYPE=Client;%%
The result is as follows
------------------------
Local Entity Type Link Type Local IP Address Peer IP Address Schema Link Status
Client Dynamic 172.22.32.98:28672 172.22.32.97:8080 HTTP Actived
Client Dynamic 172.22.32.98:28675 172.22.32.97:8080 HTTP Actived

SBI Commissioning and Maintenance Commands
 DSP REGNFINFO: used to check whether an NF is registered with the NRF.
 Example:
%%DSP REGNFINFO: NFINSTANCEID="38303eee-3317-4649-9581-1d2797e0004";%%
------------------------
NF Profile Information = {******
******
"nfServiceStatus": "REGISTERED",
"scheme": "http",
"serviceInstanceId": "service_instance_0",
"serviceName": "namf-comm",
******

Service-related commissioning and maintenance
commands
 ACT NFUPDATE: This command is used to update NF registration information. When
NF information is updated, you can run this command to manually trigger an update
to the NRF.
 Example:
%%ACT NFUPDATE: SWITCHTYPE=PUTSWITCH,

NFINSTANCENAME="AMF_Instance_0";%%
--- END

Service-related Commissioning and Maintenance
Commands (Continued) • Example:
%%DSP NGMMCTX: QUERYOPT=IMSI,
IMSI="460886666660006";%%
 DSP NGMMCTX: This
command is used to query The operation result is as follows:
------------
information about 5G mobility
IMSI = 460886666660006
management (MM) contexts, MSISDN = 8618866660006
5G-GUTI = 64F08800004193714D62
including subscriber
RM Status = Registered
information, subscriber status, CM Status = Connected
current tracking area, and Current TAI = 46088000001
Current gNodeB = 00003F
security information. TAI List = 46088000001
Encryption Algorithm = SNOW 3G Encryption
Algorithm
******

Service-related Commissioning and Maintenance Commands
(2)
• Example:
%%DSP PDUSESSION: QUERYTYPE=IMSI,
 DSP PDUSESSION: This IMSI="46080006", DSPINFOTYPE=SIMPLE;%%
command is used to query The result is as follows:
International mobile subscriber identity = 46080006
the PDU session
Mobile Station International ISDN Number = NULL
information on the SMF. PDU Session ID = 1
Related EPS Bearer ID = 0
Default bearer = No
APN = NULL
APN AMBR uplink bit rate = NULL
APN AMBR downlink bit rate = NULL
QosFlow QFI = 1
QosFlow 5QI = 9
QoS ARP Priority = 1
******

Service-related Commissioning and Maintenance Commands
(3)
• Example:
%%DSP SESSIONINFO: QUERYTYPE=IMSI,
 DSP SESSIONINFO: Used to IMSI="4608006";%%
query the session context of Context information
SESSION Info = PDP context on RU UDG_SP_RU_0064
5G SA UEs on the UPF. IMSI = 4608006
MSISDN = 86188606
APN name = 5gnet
PDP Type = IPv4
IPv4 Address type = UDG ALLOC IP ADDRESS
IPv4 PDP address = 172.23.53.1
RAT Type = NR
User Type = home
User Location Information = Type:NR;TAI(PLMN:46088;
TAC:000001);NCGI(PLMN:46088;CELLID:0000fc001);
CP NodeID = 172.22.12.114
******

 ADD AMFINFO: This command is used to configure the weight of the AMF in the AMF
set.
 MOD AMFINFO: used to modify the weight of the AMF in the AMF set.
 Example:
%%MOD AMFINFO: AMFINSTANCENAME="AMF_Instance_0", CAPACITY=255;%%
--- END

 RMV NGUSR: This command is used by the UNC to remove all information about a
5G subscriber from the AMF. The undo detach-user command is used to delete
user information.
 Example:
%%RMV NGUSR: RMVOPTION=BYIMSI, IMSI="460886666660006",

DEREGMODE=IMPLICIT;%%

 DEA SESSION: used by the UDG to deactivate subscribers. The UDG can deactivate
subscribers using an APN, IMSI, MSISDN, IMEI, user profile, NF, or node ID.
 Example:
%%DEA SESSION: DEATYPE=IMSI, IMSI="460886666660006";%%
RETCODE = 0 Operation succeeded.
--- END

 DSP NGUSERNUM: used to query the number of static and dynamic subscribers in
the AMF and SMF.
 Example:
%%DSP NGUSERNUM:; %%
--------
Pod ID Number of static subscribers Number of dynamic

subscribers
am-pod-75b54fd7d8-hhd5j172-23-0-234 1 1
am-pod-75b54fd7d8-kc97g172-23-1-77 0 0
total
Copyright © Huawei Technologies Co., Ltd. All rights reserved.1 Page170
 EXP MML: used to export all configuration data from the UNC, UDG, UDM, and
UPCF.
 Example:
%%EXP MML:; %%
Progress report
--------
Completed = 100%
Download Address
url = https://3.3.3.3:31943/rest/csp=18fa

 DSP PCCSESSINFO: used to query information about all bearers, PCC rules, rule validity and expiration time,
traffic monitoring, profile space, and PRA for a specified IMSI, MSISDN, or IMEI. This command applies to PCC
subscribers.
 Example:
DSP PCCSESSINFO:USERID=IMSI, IMSI="4600151", DISPLAYMODE=VERBOSE;
Bearer Rule Information [NSAPI/EBI:5]
No. Status Priority Type Name CRBN
1 Active 0 Predefined Rule rule1 NA
Time-related information [1]
Rule-Activation-Time = 2019-08-17 08:20:38 (3651438038)
Rule-Deactivation-Time = 2019-08-17 10:20:38(3651445238)
******

Commands (Continued) • Example:
DSP CPPDPCHGINFO:SUBSCRIBERID=IMSI,
 DSP CPPDPCHGINFO: used to display IMSI="234551";
the context information about the flow- Charging context information
based charging and PDP charging, and IMSI = 234551

MSISDN = 8613801040011
check whether the information in the
IPv4 Address = 192.168.1.1
CDR or CCR message is correct. NSAPI = 5
APN = huawei
User profile = huawei
ChargingType = Prepaid
PDP create time = 2020-03-09 16:01:01
Online chargine info:
Rating group = 100
Service ID = 100

Summary
1. O&M design objectives

 Core objectives and principles
 Seven design objectives
2. Overall O&M architecture

 5GC O&M architecture solution
 U2020 and local portal functions
3. Principles and operations of key O&M functions

 Implementation mechanism of the configuration, alarm, trace, performance measurement, log, information
collection, and license functions in the 5GC architecture
 Entries and operations for configuration, alarm, trace, performance measurement, log, information collection, and
license functions on the U2020 portal and CSP portal

Q&A
 Question 1: What are the features of the 5G Core O&M architecture compared with the NFV
architecture?
 Question 2 (True/false question) The CSP local O&M portal of the 5GC NF provides all O&M
functions.

Thank You
www.huawei.com

9 5G Core 20.X Basic O - M ISSUE 2.00

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

9 5G Core 20.X Basic O - M ISSUE 2.00

Uploaded by

Copyright:

Available Formats

5G Core Basic O&M

Copyright © Huawei Technologies Co., Ltd. All rights reserved.

 Upon completion of this course, you will be familiar with:

Copyright © Huawei Technologies Co., Ltd. All rights reserved. 2

1. 5G Core O&M Design Objectives

2. 5G Core O&M Overall Architecture

3. 5G Core O&M Key Functions

4. 5G Core Common Commissioning Commands

Copyright © Huawei Technologies Co., Ltd. All rights reserved. 3

Builds the basis for network-level

Copyright © Huawei Technologies Co., Ltd. All rights reserved. 4

1. 5G Core O&M Design Objectives

2. 5G Core O&M Overall Architecture

3. 5G Core O&M Key Functions

4. 5G Core Common Commissioning Commands

Copyright © Huawei Technologies Co., Ltd. All rights reserved. 5

O&M access: API gateway Local web portal (emergency O&M)

O&M service governance

PaaS (FusionStage) Container deployment Software/Model repository

Copyright © Huawei Technologies Co., Ltd. All rights reserved. 6

Copyright © Huawei Technologies Co., Ltd. All rights reserved. 7

Copyright © Huawei Technologies Co., Ltd. All rights reserved. 8

1. 5G Core O&M Design Objectives

2. 5G Core O&M Overall Architecture

3. 5G Core O&M Key Functions

4. 5G Core Common Commissioning Commands

Copyright © Huawei Technologies Co., Ltd. All rights reserved. 9

3. 5G Core O&M Key Functions

3.2 Alarm Function

3.3 Performance Measurement Function

3.4 Trace Function

3.5 Log Function

3.6 Information Collection Function

3.7 License Function

3.9 Pool Maintenance

Copyright © Huawei Technologies Co., Ltd. All rights reserved. 10

5GC VNF configuration center. It stores configuration data

schema Business microservice. Each network function (NF) contains a

Copyright © Huawei Technologies Co., Ltd. All rights reserved. 11

For 5GC 20.0, choose VNF_Type

Copyright © Huawei Technologies Co., Ltd. All rights reserved. 12

Displays the executed

Displays the command scripts to be

MML navigation bar: displays

Copyright © Huawei Technologies Co., Ltd. All rights reserved. 13

The U2020 or CSP portal supports secondary authorization of high-risk

Copyright © Huawei Technologies Co., Ltd. All rights reserved. 14

Copyright © Huawei Technologies Co., Ltd. All rights reserved. 15

3. 5G Core O&M Key Functions

3.2 Alarm Function

3.3 Performance Measurement Function

3.4 Trace Function

3.5 Log Function

3.6 Information Collection Function

3.7 License Function

3.9 Pool Maintenance

Copyright © Huawei Technologies Co., Ltd. All rights reserved. 16

5GC VNF alarm service. It is used to store VNF

U2020 Portal Business microservice. The alarm agent is

Copyright © Huawei Technologies Co., Ltd. All rights reserved. 17

Alarm display: Objects are displayed

Copyright © Huawei Technologies Co., Ltd. All rights reserved. 18

Click Monitoring. The real-time