FMA (SRAN16.1 - Draft A)

SingleRAN
FMA Feature Parameter Description
Issue Draft A
Date 2020-01-20
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://www.huawei.com
Email: [email protected]
Issue Draft A Copyright © Huawei Technologies Co., Ltd. i

(2020-01-20)
SingleRAN
FMA Feature Parameter Description Contents
Contents
1 Change History.........................................................................................................................1
1.1 SRAN16.1 Draft A (2020-01-20)........................................................................................................................................ 1
2 About This Document.............................................................................................................3

2.1 General Statements................................................................................................................................................................ 3
2.2 Applicable RAT......................................................................................................................................................................... 3
2.3 Features in This Document.................................................................................................................................................. 4
3 Overview....................................................................................................................................5
3.1 Background................................................................................................................................................................................ 5
3.2 Introduction............................................................................................................................................................................... 5
3.3 Architecture............................................................................................................................................................................... 9
4 Principles................................................................................................................................. 10
4.1 Wireless Fault Management............................................................................................................................................. 10
4.1.1 GSM and UMTS Wireless Fault Management......................................................................................................... 10
4.1.1.1 Fault Overview................................................................................................................................................................ 11
4.1.1.2 Fast Fault Diagnosis...................................................................................................................................................... 13
4.1.1.3 Hierarchical Delimitation.............................................................................................................................................17
4.1.1.4 Information Collection................................................................................................................................................. 21
4.1.1.5 Automatic Fault Diagnosis..........................................................................................................................................23
4.1.1.6 Recovery Confirmation................................................................................................................................................. 27
4.1.1.7 Service Query...................................................................................................................................................................27
4.1.1.8 Service Verification........................................................................................................................................................ 27
4.1.2 LTE Wireless Fault Management.................................................................................................................................. 31
4.1.2.1 Fault Overview................................................................................................................................................................ 34
4.1.2.4 Automatic Fault Detection..........................................................................................................................................50
4.1.2.5 Auxiliary Fault Recovery.............................................................................................................................................. 51
4.1.2.6 Fault Recovery Confirmation......................................................................................................................................52
4.1.3 NR Wireless Fault Management.................................................................................................................................. 52
4.1.3.1 Fault Overview................................................................................................................................................................ 54
Issue Draft A Copyright © Huawei Technologies Co., Ltd. ii

(2020-01-20)
SingleRAN
FMA Feature Parameter Description Contents
4.1.3.4 Auxiliary Fault Recovery.............................................................................................................................................. 64

4.1.3.5 Fault Recovery Confirmation......................................................................................................................................64
4.1.3.6 Automatic Fault Detection..........................................................................................................................................65
4.2 Transmission Fault Management.................................................................................................................................... 66
4.2.1 Fault Overview................................................................................................................................................................... 66
4.2.2 Fast Fault Diagnosis..........................................................................................................................................................72
4.2.3 Information Collection..................................................................................................................................................... 76
4.2.4 Automatic Fault Detection............................................................................................................................................. 76
4.2.5 Auxiliary Fault Recovery.................................................................................................................................................. 77
4.2.6 Fault Recovery Confirmation......................................................................................................................................... 77
5 Network Analysis.................................................................................................................. 79
5.1 Benefits..................................................................................................................................................................................... 79
5.2 Impacts..................................................................................................................................................................................... 79
6 Requirements......................................................................................................................... 80
6.1 Licenses.................................................................................................................................................................................... 80
6.2 Software................................................................................................................................................................................... 80
6.3 Hardware................................................................................................................................................................................. 80
6.4 Others....................................................................................................................................................................................... 81
7 Operation and Maintenance.............................................................................................. 82

7.1 When to Use........................................................................................................................................................................... 82
7.2 Precautions.............................................................................................................................................................................. 83
7.3 Data Configuration...............................................................................................................................................................83
7.3.1 Activation............................................................................................................................................................................. 83
7.3.2 Deactivation........................................................................................................................................................................ 84
7.3.3 Using the MAE-Deployment.......................................................................................................................................... 84
7.4 Activation Verification......................................................................................................................................................... 85
7.5 Network Monitoring............................................................................................................................................................ 85
8 Glossary................................................................................................................................... 86
9 Reference Documents...........................................................................................................87
Issue Draft A Copyright © Huawei Technologies Co., Ltd. iii

(2020-01-20)
SingleRAN
FMA Feature Parameter Description 1 Change History
1 Change History
This section describes changes not included in the "Parameters", "Counters",

"Glossary", and "Reference Documents" chapters. These changes include:
● Technical changes
Changes in functions and their corresponding parameters
● Editorial changes
Improvements or revisions to the documentation
1.1 SRAN16.1 Draft A (2020-01-20)

This issue introduces the following changes to SRAN15.1 02 (2019-08-10).
Technical Changes
Change Description Parameter Change
Added support for fault tree for displaying the diagnosis None
results in NSA networking scenarios. For details, see
4.1.3.2 Fast Fault Diagnosis.
Added support for interference feature identification and None

analysis of abnormally interfered cells on the NR side.
For details, see Interference Fault Scenarios.
Added support for KPI fault tree and diagnosis report on None
the NR side. For details, see Descriptions of Fault Tree
and Diagnosis Report.
Added support for automatic detection of gNodeB KPI None

faults. For details, see 4.1.3.6 Automatic Fault
Detection.
Changed the name of U2020 to MAE-Access, the name None

of CME to MAE-Deployment, and the name of mAOS to
MAE-Evaluation.
Issue Draft A Copyright © Huawei Technologies Co., Ltd. 1

(2020-01-20)
SingleRAN
FMA Feature Parameter Description 1 Change History
Editorial Changes
Revised the description of site diagnosis information for performance KPI faults.
For details, see Table 4-28.

(2020-01-20)
SingleRAN
FMA Feature Parameter Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
Feature Parameter Description documents are intended to acquaint readers with:
● The technical principles of features and their related parameters

● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve the desired gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in Feature
Parameter Description documents apply only to the corresponding software
release. For future software releases, refer to the corresponding updated product
documentation.
2.2 Applicable RAT

This document applies to GSM, UMTS, LTE FDD, LTE TDD, New Radio (NR), and
NB-IoT.
For definitions of base stations described in this document, see section "Base
Station Products" in SRAN Networking and Evolution Overview.

(2020-01-20)
SingleRAN
FMA Feature Parameter Description 2 About This Document
2.3 Features in This Document

This document describes the following features.
Feature ID Feature Name Section
WOFD-0146 Fault Management 4 Principles

00 Assistance (FMA)
7 Operation and Maintenance

(2020-01-20)
SingleRAN
FMA Feature Parameter Description 3 Overview
3 Overview
3.1 Background
On a radio access network (RAN), there are many complicated network elements
(NEs). This leads to the difficulty in fault locating and low efficiency in fault
recovery.
3.2 Introduction
Fault Management Assistance (FMA) allows users to quickly analyze fault causes
and perform troubleshooting when network faults or major emergencies occur.
Table 3-1 describes the functions that the FMA supports. These functions can be
used together to locate wireless faults and transmission faults.
Table 3-1 FMA functions
Function Description Wireless FM Wireless FM Wireless FM Trans FM

(GSM & UMTS) (LTE) (NR)
Fault overview Provides a √ √ √ √

visualized fault
information
overview,
including the
system
operating status.
Once a fault
occurs, users
can quickly
obtain system
fault
information and
engage in
troubleshooting
procedures.

(2020-01-20)
SingleRAN

Fast fault Provides a √ √ √ √

diagnosis comprehensive
analysis of a
persistent fault
on the network
based on
diagnosis rules,
including
configurations,
performance
counters,
alarms, and
operation logs.
An analysis
report is
generated to
help users
quickly rectify
the network
fault.
Hierarchical First analyzes √ √ x x

delimitation abnormal
network KPIs
and breaks
down the fault
object based on
the protocol
layers to identify
and define the
issue into the
minimum
object. The
performance
counters,
alarms, status,
and operation
logs of the
identifiable
object are then
displayed, faults
are identified,
and a fault
analysis report is
offered to users.

(2020-01-20)
SingleRAN

Information Collects onsite √ √ √ √

collection information for
fault
troubleshooting.
Due to fault
information
enormity, fault
information
collection is
complicated and
easily leads to
incorrect results
and repeated
collections,
which prolongs
the fault
recovery time.
This function
can quickly and
accurately
collect onsite
information,
which helps to
reduce the time
required for
fault recovery.
NOTE
Fault
information
collected using
the FMA is
anonymized to
protect user
privacy.
Auxiliary fault Provides fault x √ √ √

recovery recovery
assistance for
specific
configuration
faults displayed
in the fast fault
diagnosis
results.

(2020-01-20)
SingleRAN

Fault recovery Allows users to √ √ √ x

confirmation observe KPIs of
NEs in real time
and checks
whether the
fault has been
rectified after a
fault recovery
solution is
implemented.
This function
only applies to
GSM and UMTS
networks.
Service query Checks whether √ x x x

the service has
been restored
after a fault
recovery
solution is
implemented.
This function
only applies to
GSM networks.
Service Rapidly verifies √ x x x

verification the network
status after a
network
reconstruction is
implemented on
the live network.
This function
only applies to
GSM and UMTS
networks.
NOTE
X: not supported; √: supported
For base stations in integrated deployment mode, different content is displayed for wireless
faults and transmission faults when the functions are supported by both wireless and
transmission fault management (such as fault overview).

(2020-01-20)
SingleRAN
3.3 Architecture
FMA is deployed on different platforms according to radio access technologies
(RATs) and fault types.
FMA functions are deployed as follows:
● For GSM and UMTS, wireless faults are analyzed on the BSC LMT and
transmission faults are analyzed on the MAE.
● For LTE and NR, wireless faults and transmission faults are both analyzed on
the MAE.
Figure 3-1 shows the FMA architecture on the MAE, which is similar to that on
the LMT.
Figure 3-1 FMA architecture on the MAE

(2020-01-20)
SingleRAN
FMA Feature Parameter Description 4 Principles
4 Principles
4.1 Wireless Fault Management
4.1.1 GSM and UMTS Wireless Fault Management

GSM and UMTS wireless fault management aims to rectify network faults and
verify services. It includes the following functions:
● 4.1.1.1 Fault Overview
● 4.1.1.2 Fast Fault Diagnosis
● 4.1.1.3 Hierarchical Delimitation
● 4.1.1.4 Information Collection
● 4.1.1.5 Automatic Fault Diagnosis
● 4.1.1.6 Recovery Confirmation
● 4.1.1.7 Service Query
● 4.1.1.8 Service Verification
● Of these functions, fast fault diagnosis and hierarchical delimitation are applicable to
faults that are generated or cleared within the last 8 hours.
● Fast fault diagnosis and hierarchical delimitation cannot be performed at the same time.
● While information collection is in process, do not run the COL LOG command to collect
logs.
Figure 4-1 shows the troubleshooting process.

(2020-01-20)
SingleRAN
Figure 4-1 GSM and UMTS wireless fault management
Figure 4-2 shows the service verification process of GSM and UMTS FMA after a
network reconstruction.
Figure 4-2 Service verification process after a network reconstruction
GSM and UMTS FMA is implemented on the LMT. This section describes the
principles and application scenarios of GSM and UMTS FMA. For details on the
operation procedure, see BSC6900 GU LMT User Guide and BSC6910 GU LMT User
Guide.
● Ensure that only one LMT performs the FMA function at a time.
● The GSM and UMTS wireless fault management is not applicable to eGBTSs.
4.1.1.1 Fault Overview

Fault overview provides visualized illustration of operating status and fault
information about GSM and UMTS networks. This function allows users to quickly

(2020-01-20)
SingleRAN
identify a fault and start fault troubleshooting. Table 4-1 describes the
information that users can obtain using this function.
Table 4-1 Fault overview user information

Category Description
UMTS KPI Trends of the following KPIs:

● RRC Connection Setup
● CS RAB Setup
● PS RAB Setup
● CS Traffic
● PS Traffic
● CS Service Drop
● PS Service Drop
● Paging
GSM KPI Trends of the following KPIs:

● CS Call Setup Success Rate
● CS Immediate Assignment Success Rate
● CS Assignment Success Rate
● Uplink PS TBF Establishment Success Rate
● Downlink PS TBF Establishment Success Rate
● CS TCH Call Drop Rate
● Uplink PS TBF Drop Rate
● Downlink PS TBF Drop Rate
● CS Erlang
● Uplink PS Traffic
● Downlink PS Traffic
KPI trend A KPI trend chart that contains three curves illustrating KPI changes
chart in the last eight hours, the same hours from the previous day, and
during the same hours on the same day from the previous week,
respectively. For example, assume that it is now midnight (24:00)
on Tuesday. Curve 1 shows the KPI changes between 16:00 and
24:00 this Tuesday. Curve 2 shows the KPI changes between 16:00
and 24:00 yesterday, and curve 3 shows the KPI changes between
16:00 and 24:00 last Tuesday.
NOTE
The horizontal X-coordinate represents the measurement time (expressed in
the format of HH:MM), and the vertical Y-coordinate represents the counter
value, in corresponding respective units.
When fast fault diagnosis is used to analyze performance data,
performance data generated during a sampling period is not
available if the measurement state was DISABLED in the sampling
period.

(2020-01-20)
SingleRAN
Category Description
KPI trend ● Automatically displays the KPI value corresponding to a point on

value the KPI change trend curve when users select a point using the
mouse pointer.
● Provides KPI filtering on the right of the fault overview interface
to allow viewing the change trend of the selected KPI.
4.1.1.2 Fast Fault Diagnosis

This fast fault diagnosis function comprehensively analyzes network faults from
the perspectives of counters, alarms, configurations, and operation logs based on
the diagnosis rules and then generates a fault diagnosis report. Figure 4-3
illustrates the principle of fast fault diagnosis.
Figure 4-3 Fast fault diagnosis
For details on fast fault diagnosis, see BSC6900 GU LMT User Guide and BSC6910
GU LMT User Guide.
Wireless Fault Diagnosis Scenarios

Table 4-2 lists the scenarios of GSM and UMTS wireless fault diagnosis.
Table 4-2 Wireless fault diagnosis scenarios
Fault Scenario Option

Diagnosis
UMTS KPI RRC Success Rate

fault
diagnosis CS RAB Setup Success Rate
CS Call Drop Rate
PS RAB Setup Success Rate
PS Service Drop Rate
Paging

(2020-01-20)
SingleRAN

Diagnosis
Traffic CS Erlang
PS Traffic
Transmission Site Break Down
Transmission Signaling Analysis
Transmission Connectivity Analysis
Board Board Faults Diagnosis
Communication Failure Between NE and

EMS
OMU Faults Diagnosis
Analysis on the Proportion of Faulty Board

Links
Hardware Sub-health Diagnosis
Health check Equipment Health Check
Others License Faults Diagnosis
RNC in Pool Load Sharing
GSM fault KPI GSM CS Immediate Assignment Success

diagnosis Rate
GSM CS Assignment Success Rate
GSM CS Call Setup Success Rate
GSM TCH Call Drop Rate
GSM PS TBF Establish Success Rate
GSM PS TBF Drop Rate
GSM PS TBF Drop Rate
GSM Paging Success Rate
GSM Location Update Success Rate
GSM Outgoing Inter-Cell Handover

Decrease
Transmission GSM BTS Interruption
GSM Ater Interface Interruption
GSM A Interface Interruption
GSM GB Interface Interruption

(2020-01-20)
SingleRAN

Diagnosis
Transmission Connectivity Analysis
Traffic GSM CS Traffic
GSM GB Interface Traffic
Board GSM Repeated BSC Board Faults
Board Faults Diagnosis
Communication Failure Between NE and

EMS
OMU Faults Diagnosis
Hardware Sub-health Diagnosis
Health check GSM CS Key Parameters Check
GSM PS Key Parameters Check
GSM BSC Board Configuration Check
GSM Equipment Health Check
Others GSM PDCH Fault
GSM Voice Fault Analyse
Table 4-3, Table 4-4, and Table 4-5 lists the fault diagnosis scenarios for RNC in
Pool.
Table 4-3 Fault diagnosis scenarios for RNC in Pool (supporting RNC in Pool Load
Sharing only)
Diagnosis Item Load Sharing Type = Load Sharing Type =
MASTER OVERFLOW
RRC connection setup √ x
CS service setup √ x
CS call drop √ x
PS service setup √ x
PS call drop √ x
CS Erlang √ x
PS traffic √ x
Paging √ x

(2020-01-20)
SingleRAN
Diagnosis Item Load Sharing Type = Load Sharing Type =

MASTER OVERFLOW
A large number of √ x
unavailable cells
Equipment health check √ √
RNC in Pool load sharing √ x

NOTE
Table 4-4 Fault diagnosis scenarios for RNC in Pool (supporting RNC in Pool
Redundancy only)
Diagnosis Item Host Status = MASTER Host Status = BACKUP
RRC connection setup √ x
CS service setup √ x
CS call drop √ x
PS service setup √ x
PS call drop √ x
CS Erlang √ x
PS traffic √ x
Paging √ x
A large number of √ x
unavailable cells
Equipment health check √ √
RNC in Pool load sharing x x

NOTE

(2020-01-20)
SingleRAN
Table 4-5 Fault diagnosis scenarios for RNC in Pool (supporting RNC in Pool Load
Sharing and Redundancy)
Diagnosis Load Sharing Load Sharing Type Load Sharing
Item Type = MASTER = OVERFLOW and Type =
and Host Status = Host Status = OVERFLOW and
MASTER BACKUP Host Status =
MASTER
RRC √ x x
connection
setup
CS service √ x x
setup
CS call drop √ x x
PS service √ x x
setup
PS call drop √ x x
CS Erlang √ x x
PS traffic √ x x
Paging √ x x
A large √ x x
number of
unavailable
cells
Equipment √ √ √
health check
RNC in Pool √ x x
load sharing
NOTE
Fault Diagnosis Report

A fast fault diagnosis report provides the following information: RNC basic
information, KPI trend, FMA dashboard, fault analysis report, and operation logs
of the last 24 hours. For details, see BSC6900 GU LMT User Guide and BSC6910
GU LMT User Guide.
4.1.1.3 Hierarchical Delimitation

Hierarchical delimitation can be used to analyze the fault that cannot be identified
by the fast fault diagnosis function.
Fault delimitation analyzes abnormal network KPIs (as listed in Table 4-1) based
on standard protocol layers. This is to locate and identify minimum objects

(2020-01-20)
SingleRAN
attributable to the network fault, identify and display counters, alarms, status, and
operation logs related to these objects, and finally generate a fault analysis report.
You can query historical analysis reports by selecting the storage duration.
Table 4-6 and Table 4-7 list abnormal UMTS and GSM network KPIs, respectively.
Table 4-6 Abnormal UMTS network KPIs
KPI Interface Type Control Plane or User Plane
RRC Connection Iub Control plane

Setup
CS RAB Setup Iub/Iu-CS Control plane/User plane
PS RAB Setup Iub/Iu-PS Control plane/User plane
CS Traffic Iub/Iu-CS Control plane/User plane
PS Traffic Iub/Iu-PS Control plane/User plane
CS Service Drop Iub/Iu-CS Control plane/User plane
PS Service Drop Iub/Iu-PS Control plane/User plane
Paging Iub/Iu Control plane
Table 4-7 Abnormal GSM network KPIs
Fault Indicator Interface Type Control Plane/User Plane
CS Call Setup Abis/A Control plane/User plane

Success Rate
CS Immediate Abis Control plane

Assignment Success
Rate
CS Assignment Abis/A Control plane/User plane

Success Rate
TBF Establishment Abis/Gb Control plane/User plane

Success Rate
TCH Call Drop Rate Abis/A Control plane/User plane
TBF Drop Rate Abis/Gb Control plane/User plane
CS Erlang Abis/A Control plane/User plane
PS Traffic Abis/Gb Control plane/User plane
Figure 4-4 shows an example of the identification process of the Iu-CS interface
on an IP-based UMTS network based on the protocol stack.

(2020-01-20)
SingleRAN
Figure 4-4 IP protocol stack for the Iu-CS interface
The information contained in a hierarchical delimitation report is described in the

following table.

(2020-01-20)
SingleRAN
Table 4-8 Hierarchical delimitation report information

Item Description
Faulty cells Information about cells affected by a fault is provided.

The following information is included:
● Cell ID: ID of the faulty cell
● Failure rate: proportion of the number of failures in a
faulty cell to that in a base station controller (BSC)
related to a specific counter
● Fault counter: proportion of the number of failures in a
faulty cell to the number of attempts in this cell
● Number of attempts: number of attempts in this cell
● Base station name: name of the base station to which
the faulty cell belongs
● Interface board: interface board where the faulty cell is
configured
● Subsystem: a subsystem where the faulty cell is
configured

(2020-01-20)
SingleRAN
Item Description
Scenario selection Provides the minimum objects after faults are analyzed
based on standard protocol layers. Users can select a fault
object to view related KPIs, alarms, and status. The fault
objects are displayed below.
The interface between BSC and BTS (Iub/Abis interface)
● Control plane
– Wireless layer objects (NBAP)
– Transmission layer objects (SCTPLNK and
ETHPORT)
– Device layer objects (INT board and control plane
subsystem)
● User plane
– Wireless layer objects (Abis)
– Transmission layer objects (ETHPORT)
– Device layer objects (INT board)
The interface between BSC and CN (Iu/A/Gb interface)
● Control plane
– Wireless layer objects (RANAP)
– Transmission layer objects (MTP3LINK, SCTPLNK,
and ETHPORT)
– Device layer objects (INT board and control plane
subsystem)
● User plane
– Wireless layer objects (IUUP and GTPU)
– Transmission layer objects (ETHPORT)
– Device layer objects (INT board)
4.1.1.4 Information Collection

If a fault cannot be decided using the fast fault diagnosis and hierarchical
delimitation functions, onsite fault information must be obtained for fault
troubleshooting. Two methods can be used to collect fault information: fast
information collection and user-defined information collection. UMTS only
supports fast information collection.
Fast Information Collection

The information collected using fast information collection varies with the NE, as
described in Table 4-9.

(2020-01-20)
SingleRAN
Table 4-9 Fast information collection
NE Collection Data Collection File Data Collection Range

Batch
GSM BSC First batch Counter result files 4 hours
Historical alarm files 3 days
Operation logs 48 hours
BSC data configuration Full data

files and MML
command outputs
BSC board last word Within 20 minutes if

logs last word logs are
generated
Second batch Common debugging Between the start time

logs and end time selected
by users
GSM CS single-user CHR Between the start time

by users
GSM CHR logs Between the start time

and end time selected
by users
GSM one-way audio Between the start time

by users
Host running logs Between the start time

by users
MML command outputs Full data
Last word log files One day
Platform CHR logs Between the start time

by users
Transmission path logs 1 hour
GBTS deployment logs 1 hour
RNC First batch Historical alarm files 48 hours
Operation logs 48 hours
BSC data configuration Full data

files
UKPI snapshots 5 minutes or 24 hours

(2020-01-20)
SingleRAN
NE Collection Data Collection File Data Collection Range

Batch
BSC board last word Within 20 minutes if

logs last word logs are
generated
Second batch Counter result files 2 hours
UMTS CHR logs One file for each

subrack
Common debugging One file for each

logs subrack
CALLFAULT logs One file for each

subrack
User-defined Information Collection

User-defined information collection allows user to customize fault information
items before information collection. This information collection mode facilitates
routine O&M.
The following items can be defined by users: the start time and end time of data
collection, collected log file types, and MML query commands.
4.1.1.5 Automatic Fault Diagnosis
Automatic Startup on FMA

The FMA periodically detects KPIs and fault alarms and automatically starts fault
diagnosis based on the preset thresholds. Table 4-10, Table 4-11, Table 4-12, and
Table 4-13 list the triggering conditions.
Table 4-10 Automatic startup on FMA triggered by KPI thresholds (UMTS)
Scenario KPI Name Default Threshold
UMTS fault RRC Setup Success Ratio 95%

diagnosis
CS RAB Setup Success 95%
Ratio
PS RAB Setup Success 95%

Ratio
HSDPA Setup Success 95%

Ratio
HSUPA Setup Success 95%

Ratio

(2020-01-20)
SingleRAN
CS Call Drop Ratio 2%
PS Call Drop Ratio 5%
Security Mode Success 95%

Ratio
Location Update Success 80%

Ratio
Route Area Success Ratio 80%
Attach Success Ratio 70%
PDP Activation Success 70%

Ratio
CS Authentication Success 90%

Ratio
PS Authentication Success 90%

Ratio
CS Service Request Success 90%

Ratio
PS Service Request Success 90%

Ratio
Table 4-11 Automatic startup on FMA triggered by KPI thresholds (GSM)
GSM fault Assignment Success Rate 90%

diagnosis
Call Establishment Success 80%
Rate
Location Update Success 80%

Rate
Call Drop Rate on TCH per 5%

Cell
Uplink TBF Establishment 65%

Success Rate
Downlink TBF 65%

Establishment Success
Rate
Uplink EGPRS TBF 65%

Rate

(2020-01-20)
SingleRAN
Downlink EGPRS TBF 65%

Rate
Uplink TBF Drop Rate 10%
Downlink TBF Drop Rate 10%
Uplink EGPRS TBF Drop 10%

Rate
Downlink EGPRS TBF Drop 10%

Rate
Table 4-12 Automatic startup on FMA triggered by alarms (UMTS)

Scenario Product Name Alarm Name
UMTS fault BSC6900/BSC6910 ALM-21531 SAAL Link Fault

diagnosis
ALM-21522 Low SCCP Setup
Success Rate
ALM-21521 SCCP Subsystem

Prohibited
ALM-21552 M3UA Destination

Entity Route Unavailable
ALM-21503 MTP3 DSP

Inaccessible
ALM-21541 SCTP Link Fault
ALM-20241 Board Unavailable
BSC6900 ALM-20737 OMU Disconnected

from Host
Table 4-13 Automatic startup on FMA triggered by alarms (GSM)

GSM fault BSC6900/BSC6910 ALM-20804 BTS Unavailable

diagnosis
BSC6900/BSC6910 ALM-21807 OML Fault
BSC6900/BSC6910 ALM-21825 CSL Link Fault
BSC6900/BSC6910 ALM-22009 NSVL Dynamic

Configuration Procedure Failure

(2020-01-20)
SingleRAN
BSC6900/BSC6910 ALM-22005 NSE Faulty
BSC6900/BSC6910 ALM-22008 PTP BVC Faulty
BSC6900/BSC6910 ALM-21521 SCCP Subsystem

Prohibited
BSC6900/BSC6910 ALM-21552 M3UA Destination

Entity Route Unavailable
BSC6900/BSC6910 ALM-21503 MTP3 DSP

Inaccessible
BSC6900 ALM-20246 Ater RSL Faulty
BSC6900 ALM-20261 Ater OML Faulty
BSC6900/BSC6910 ALM-21541 SCTP Link Fault
BSC6900/BSC6910 ALM-20241 Board Unavailable
BSC6900/BSC6910 ALM-20737 OMU Disconnected

from Host
Automatic Tracing Startup

When the following KPIs reach the threshold of automatic startup on FMA, the
FMA automatically starts tracing signaling over the Iu interface (including SCCP)
based on specific fault scenarios to help locate faults over this interface. You can
use the Download Source Data function to download the automatic tracing file
to a local disk.
● The value of CS/PS RAB Setup Success Rate decreases.
● The value of CS/PS Service Drop Rate increases.
Automatic Startup Report Acquisition

1. Log in to the LMT and click the FMA button to enter the FMA tab page.
2. Click Query Result in the lower part of the FMA tab page, as shown in
Figure 4-5.
3. In the displayed Query Result dialog box, select the time range from the
drop-down list box. In this list box, the files with a suffix of "auto" are
automatic diagnosis reports, and the rest are manual diagnosis reports.
4. Click Start and wait for the generation of a fault diagnosis report.
5. Click Save Report or Download Source Data to download the analysis report
and collected data to a local disk.

(2020-01-20)
SingleRAN
Figure 4-5 Acquiring the automatic startup report
4.1.1.6 Recovery Confirmation

On the fault overview page, users can view the running status of the GSM and
UMTS networks after service recovery solutions are implemented to check
whether a fault is rectified. For details, see 4.1.1.1 Fault Overview.
4.1.1.7 Service Query

This function quickly checks whether services have been restored after a fault
recovery solution is implemented.
Due to the long period of normal KPI checks, the status of restored services is
hardly acquired in time. This sub-function supports the service KPI query within a
short period (5 minutes), allowing users to rapidly obtain the status of restored
services.
4.1.1.8 Service Verification

This function rapidly queries the network status after a network reconstruction is
implemented on the live network.
This function compares performance indicators, alarms, and configuration before

and after a network reconstruction, and displays the service status to rapidly
determine whether a service operates properly after the network reconstruction.
Table 4-14 and Table 4-15 list applicable UMTS and GSM network reconstruction
scenarios and check items, respectively.
Table 4-14 Applicable UMTS network reconstruction scenarios and check items
Scenario Check Item
Common indicator verification RRC connection setup success rate
CS RAB setup success rate
PS RAB setup success rate
CS call drop rate

(2020-01-20)
SingleRAN
Scenario Check Item
PS call drop rate
Traffic volume
Transmission mode Transmission link status

transformation from ATM to IP
over the Iub interface Cell status
RRC connection setup success rate
CS call drop rate
PS call drop rate
Activity factor
Port protection solution
Rehoming Transmission link status
Cell status
RRC connection setup success rate
CS call drop rate
PS call drop rate
Activity factor
Port protection solution
Iur interface reconstruction RRC connection setup success rate
CS call drop rate
PS call drop rate
Traffic volume
Transmission link status
Migration success rate
Iu interface reconstruction RRC connection setup success rate

(2020-01-20)
SingleRAN
Scenario Check Item
CS call drop rate
PS call drop rate
Traffic volume
NAS-layer indicators over the Iu interface
RNC license replacement RRC connection setup success rate
CS call drop rate
PS call drop rate
Traffic volume
IUFLEX RRC connection setup success rate
CS call drop rate
PS call drop rate
Traffic volume
Configuration integrity
NAS-layer indicators over the Iu interface
Table 4-15 Applicable GSM network reconstruction scenarios and check items
Scenario Check Item
IP-based restructuring over the Control-plane alarms over the A interface

A interface
User-plane alarms over the A interface
CS access-related indicators
CS call drop rate
Channel congestion-related indicators

(2020-01-20)
SingleRAN
Scenario Check Item
IP path-related indicators
MSC Pool reconstruction Control-plane alarms over the A interface
Alarms related to core network flow control

and congestion
CS call drop rate
MSC Pool selection-related indicators
IP-based restructuring over the NSVL link-related alarms

Gb interface
PS service-related alarms
TBF establishment success rate
TBF call drop rate
PS traffic-related indicators
SGSN Pool reconstruction NSVL/NSVC link-related alarms
TBF call drop rate
Base station cutover Alarms related to disconnection with a base

station and out-of-service of a cell
Invalid voice service alarm
CS call drop rate
TBF call drop rate

(2020-01-20)
SingleRAN
4.1.2 LTE Wireless Fault Management

LTE wireless fault management is implemented on the MAE to help users
troubleshoot wireless faults on LTE networks.
LTE wireless fault management obtains eNodeB configurations, alarms,
performance counters, and operation logs from the MAE and analyzes the fault.
After an analysis is complete, the fault analysis results are provided to help users
identify potential causes and accelerate service recovery. LTE wireless fault
management provides the following functions:
● Fault overview
Multisite faults are analyzed to help users locate the faulty base station or
cell. Users can continue to perform fast fault diagnosis or information
collection.
● Fast fault diagnosis
After the faulty base station or cell is determined using the fault overview
function, fault diagnosis can be performed on the faulty base station or cell.
● Information collection
function, information about the faulty base station or cell can be collected.
Figure 4-6 shows the relationship between the preceding functions.
Figure 4-6 Relationship between LTE fault management functions
Table 4-16 lists the supported LTE wireless fault scenarios.

(2020-01-20)
SingleRAN
Table 4-16 LTE wireless fault scenarios

Scenario RAT Sub-Scenario Check Item
Performanc FDD/TDD Access RRC Setup Success Rate

e KPI
S1SIG Setup Success Rate
E-RAB Setup Success Rate
RACH Setup Success Rate
Service drop Call Drop Rate
Data transmission UL User Throughput (Kbit/s)
UL Cell Throughput (Kbit/s)
UL User Traffic Thd (bit)
DL User Throughput (Kbit/s)
DL Cell Throughput (Kbit/s)
DL User Traffic Thd (bit)
Interworking CSFB Execution Success Rate
CSFB Preparation Success Rate
Handover Inter-Frequency HO Success

Rate
Intra-Frequency HO Success
Rate
Handover In Success Rate
Handover In Pre Success Rate
X2 HO Out Success Rate
S1 HO Out Success Rate
FDD TDD HO In Success Rate
FDD TDD HO Out Success Rate
FDD TDD HO In Pre Success

Rate
FDD TDD HO Out Pre Success

Rate
Voice E-RAB Setup Success Rate QCI1
E-RAB Setup Success Rate QCI5
Call Drop Rate QCI1
Call Drop Rate QCI5

(2020-01-20)
SingleRAN
Scenario RAT Sub-Scenario Check Item
UL Packet Loss Rate QCI1
DL Packet Loss Rate QCI1
DL PDCP Packet Loss Rate

QCI1
NB-IoT Access NB-IoT RRC Success Rate
Service drop NB-IoT Call Drop Rate
Data transmission NB-IoT DL Packet Loss Rate

(SRB)
NB-IoT UL RBLER
NB-IoT DL RBLER
eMTC Access eMTC RACH Setup Success

Rate
eMTC RRC Setup Success Rate
Service drop eMTC Call Drop Rate
Data transmission eMTC UL RBLER
eMTC DL RBLER
eMTC UL IBLER
eMTC DL IBLER
Handover eMTC Inter-Frequency HO Out

Success Rate
eMTC Intra-Frequency HO Out

Success Rate
eMTC Handover In Success

Rate
Cell Fault N/A Cell unavailable Cell Unavailable
Cell capability Cell Capability Degraded

degraded
RF out of service RF Out of Service
Heavy N/A Heavy traffic Heavy Traffic

Traffic
Interference N/A Interference TDD UL Interference

(2020-01-20)
SingleRAN
Except heavy traffic, all other scenarios support fault overview and fast fault
diagnosis. Heavy traffic generally occurs only in a small number of sites, so users
are advised to select heavy-traffic sites for a fast fault diagnosis.
For details of how to use FMA to handle LTE wireless faults, see Fault
Management > FMA in MAE MBB Network Management System Product
Documentation.

Fault overview provides an overview of overall faults to help users learn the entire
network's operating status.
After users select the fault scenarios (as listed in Table 4-16), LTE sites to be
analyzed, the fault occurrence time, and the comparison time, the fault overview
function performs fault analysis. Fault overview provides different information for
performance KPIs, cell faults, and TDD interference of base stations.
Performance KPI Faults

For performance KPI faults, fault overview displays top sites, KPI trend chart, KPI
deterioration time, KPI failure cause value distribution and comparison with
normal KPI time, and top sites that affect KPIs.
● Top Site
Includes site name, KPIs obtained on the fault occurrence day, and KPIs
obtained at the comparison time, as shown in Figure 4-7.
– Information of base stations is displayed on the Legacy tab page.
– Figure 4-7 Top site example
● KPI Trend Chart

Displays the KPI trends during the 24 hours before the fault occurs, the past
48 hours to the past 24 hours, and the same period on the same day of the
last week.
● KPI Deterioration Time
Displayed on a KPI trend chart.
● Failure Cause Value Distribution and Comparison with Normal KPI Time
According to the KPI calculation formula, KPI failure cause values are
decomposed and linked to related performance counters, and the KPIs at the

(2020-01-20)
SingleRAN
fault occurrence time are compared with those at a specified time, as shown
in Figure 4-8.
Figure 4-8 Failure cause value distribution example
● Top Sites that Affect KPIs

– For base stations in integrated deployment mode that require further
analysis, fast fault diagnosis or information collection can be performed.
Figure 4-9 Example of top sites that affect KPIs (base stations in
integrated deployment mode)

(2020-01-20)
SingleRAN
The FMA provides automatic analysis. The automatic analysis function applies to fault
scenarios that are easily identified. If the KPIs affected by a fault are not easily identified or
multiple KPIs need to be analyzed, automatic analysis is not recommended.
● If Automatic Analysis is selected, FMA automatically performs fault overview and fast
fault diagnosis after you click Analyze. No manual intervention is required.
● If Automatic Analysis is not selected, FMA only performs fault overview after you click
Analyze.
Cell Faults
For cell faults, fault overview displays the following information:
● According to the selected faulty scenario, FMA displays the numbers of sites
and cells where the fault occurs. The alarms are classified into active alarms
and historical alarms. Figure 4-10 shows an example.
Figure 4-10 Example of the number of sites and cells with faults
Only historical alarms generated within 24 hours before the analysis are recorded.
● List of cells that report alarms: displays the number of sites and cells where
an alarm related to the fault is reported. The alarms are classified into active
alarms and historical alarms. Figure 4-11 shows an example.
Figure 4-11 Example of the list of cells that report alarms
● Alarm quantity change trend. Figure 4-12 shows an example.
Figure 4-12 Alarm quantity change trend example

(2020-01-20)
SingleRAN
TDD Interference Faults

The Fault Overview window displays TDD uplink interference, if a user selects the
interference fault scenario.
● Automatic Analysis
No support for interference-related counters for LTE TDD networks
● Export Base Station Information
Exports information of the site name, local cell ID, site KPI values at the fault
occurrence time and at the comparison time, and KPI decline of all sites in the
subnet that is being analyzed. Figure 4-13 shows an example.
Figure 4-13 Base station information example
● Site List
Displays the contribution rate of KPI failures or deterioration of LTE TDD cells
served by each eNodeB in the current eNodeB group within the performance
measurement period starting from T0. Sorts the eNodeBs in descending order
by the failure contribution rate. Figure 4-14 shows an example.
Contribution rate of TDD uplink interference KPI failures = Difference in counter values
between the time in the previous period and the current time in each cell/Difference
in counter values between the time in the previous period and the current time in all
cells x 100%

(2020-01-20)
SingleRAN
Figure 4-14 Site list example
● Top Site
Indicates KPIs of top N sites. The number of top N sites is set to 100 by
default. All TDD cells of top 100 sites are displayed. If the total number of
sites on the subnet or in the subzone does not exceed 100, KPI values of the
subnet are the same as those of top N sites. Figure 4-15 shows an example.
Top N sites are screened out by the following principle: compare KPI values at the KPI
deterioration time and the specified time of all sites on the subnet or in the subzone,
and select top 100 sites with the maximum KPI deterioration.
Figure 4-15 Top site list
● High-risk Interference Source Site

Summarizes suspicious sites identified based on analysis results of top N sites,
clock alarms, forcible phase synchronization events, and DA traffic statistics.
Figure 4-16 shows an example.

(2020-01-20)
SingleRAN
Sites where events have occurred are listed first, followed by those with alarms and
other sites.
Figure 4-16 High-risk interference source site example
● Symbol-level Interference Level

Displays performance counter values of all symbol-level interference in the
current eNodeB group during the performance measurement period starting
from T0. Figure 4-17 shows an example.
T0 is the start time of the first performance measurement period with KPI values
changing from stable to dramatic.
Figure 4-17 Symbol-level interference level example

(2020-01-20)
SingleRAN

Fast fault diagnosis analyzes the performance of top sites identified using the fault
overview function. The analysis result provides associated information about KPIs,
active alarms, and operation logs for each of the top sites and each cell served by
the top sites at the time when KPIs deteriorate. By analyzing KPIs, active alarms,
and operation logs, this function helps users identify the minimum faulty units.
For base stations in integrated deployment mode, fast fault diagnosis displays
different diagnosis information for performance KPI, cell, heavy-traffic, and
interference faults.
For the detailed procedure of fast fault diagnosis, see the "Starting Fast Fault
Diagnosis" section under "FMA" in MAE MBB Network Management System
Product Documentation.

For performance KPI faults, the fast fault diagnosis function provides site and cell
diagnosis information, as described in Table 4-17 and Table 4-18.
Table 4-17 Site diagnosis information for performance KPI faults

Function Description
Basic Site ● Site Name indicates the name of a site.

Informatio ● Contribution Rate indicates the ratio of failures in a site to the
n Table total failures, which is analyzed by the Fast fault diagnosis
function at a specific time.
● Version Change Info lists the latest software version updates of
a site.
● License Analysis displays active license-related alarms at the
fault occurrence time.
● Risky Operation displays risky operation records in a specified
period.

(2020-01-20)
SingleRAN
Transmissi The following KPIs involve transmission diagnosis and analysis:

on ● RRC Setup Success Rate
Diagnosis
Info ● eMTC RRC Setup Success Rate
● S1SIG Setup Success Rate
● E-RAB Setup Success Rate
● E-RAB Setup Success Rate QCI1
● E-RAB Setup Success Rate QCI5
● CSFB Execution Success Rate
● X2 HO Out Success Rate
● FDD TDD HO Out Pre Success Rate
Transmission diagnosis information is provided on the Original
Messages and Diagnosis Results tab pages.
The following eNodeB transmission diagnosis information is
displayed:
● Transmission port information (the DSP ETHPORT command
output)
● Address Resolution Protocol (ARP) information learned by the
transmission ports (the DSP ARP command output)
● Configured route information (the output of the following
commands)
– DSP IPRT when the old transmission configuration model is
used
– DSP IPROUTE4 when the new transmission configuration
model is used
● S1 interface transmission quality information (the output of the
PING command output over the S1 interface)
Active Displays the current active alarms of the to-be-analyzed site.

Alarms Known alarms on specific sites can be used to identify other sites
with the same alarms. Statistics on active alarms in a time
segment are collected, and the alarm distribution is displayed.
Fault Tree Displays initial analysis results of each cell in the site. eMTC KPIs
are not included.
Voice This function takes effect only for voice services.

Parameter ● Identifies voice-related core parameters of a specified site,
Check compares the parameter settings of the current eNodeB and
baseline parameter settings, and displays comparison results.
● Allows users to import voice baseline parameter files and
perform simple checks.

(2020-01-20)
SingleRAN
Access This function takes effect only for access services. (eMTC counters
Parameter are not included.)
Check Identifies access-related core parameters of a specified site,
compares the parameter settings of the current eNodeB and
Call Drop This function applies only to the call drop sub-scenario. (eMTC
Parameter counters are not included.)
Check Identifies call drop-related core parameters of a specified site,
compares the parameter settings of the current eNodeB and
The Site tab page about NB-IoT KPI analysis displays only basic site information and active
alarms.

(2020-01-20)
SingleRAN
Table 4-18 Cell diagnosis information for performance KPI faults

Basic Cell ● Cell ID indicates the cell ID.

Informati ● Contribution Rate indicates the ratio of failures in a cell to the
on Table total failures, which is analyzed by the Fast fault diagnosis
● Actual value of a KPI indicates the cell KPI value at the time
when the KPI is analyzed.
● Denominator (number of attempts) of a KPI indicates the
number of setup attempts related to this KPI, if a non-traffic-
volume-related KPI (such as success rate or call drop rate) is
analyzed.
● Heavily Loaded determines whether a cell is highly loaded
based on the CPU usage of the gNodeB board serving the cell
and the number of online users in the cell.
● TDD Interference:
For TDD cells, the FMA determines whether the following
interference types exist based on performance counters related
to uplink interference:
– Clock out-of-synchronization interference or long-distance
interference
– Clock out-of-synchronization interference
– Other interference
If the preceding interference exists, a specific interference type is
displayed. If no interference-related performance counters are
obtained, "Data obtaining error" is displayed. If no interference
exists, "No interference" is displayed.
For FDD cells, the FMA does not analyze TDD interference and
these FDD cells are displayed as "Non-TDD cells".
Coverage ● Coverage level list

Level – Coverage Level ID indicates the coverage level ID.
NOTE
– Contribution Rate indicates the ratio of failures in a cell of
The Cell
tab page each coverage level to the total failures, which is analyzed by
displays the fast fault diagnosis function at a specified time.
the – Actual value of a KPI indicates the cell coverage level at the
coverage
level only
time when the KPI is analyzed.
when it is – Denominator (number of attempts) of a KPI indicates the
used for number of setup attempts related to the coverage level, if a
analyzing non-traffic-volume-related KPI (success rate or call drop rate)
NB-IoT
KPIs in
is analyzed.
fault ● Coverage level trend
scenarios. Provides coverage level trend during an analysis period.

(2020-01-20)
SingleRAN
Cell Provides correlation analysis on the cell KPIs, alarms, and operation
Dashboar logs. After users click a time point when a KPI changes, the alarms
d and operation logs generated at the time will be displayed to help
users quickly find the potential fault cause.
Users can select records generated in the latest two hours before
the fault occurs from operation logs for MAE-Deployment analysis.
For cell faults and heavy-traffic faults, select records generated at
the current time. The MAE-Deployment can only analyze records
generated within two hours before the fault occurrence time, and
can only analyze MOD, RMV, and ADD commands.
Board Displays the CPU usage trends of the main control board and
Diagnosis baseband processing unit (BBP) serving a cell and the trend of the
Info number of connected cell users. This helps users observe the
relationship between the cell KPI changes and the board CPU
usage.
Cell KPI Displays the trends of several cell KPI values. eMTC counters are not
Analysis included.
Fault Tree Displays the preliminary fault analysis result on the current cell. The
result includes the diagnosis result summary and detailed diagnosis
data of each sub-scenario in the fault tree. eMTC counters are not
included.
Cell Faults
For cell faults, the fast fault diagnosis function provides only site diagnosis
information, as described in Table 4-19.
Table 4-19 Diagnosis information for cell faults

Site Key Lists information about each faulty cell served by the site, including:
Configura ● Basic configuration: duplex mode, NB-IoT cell indicator,
tion Table frequency, TX/RX mode, subframe ratio, and others
● Operator information: local tracking area ID, tracking area code
(TAC), operator index, country code, mobile network code
(MNC), and others
● S1 interface information: S1 interface ID, S1 interface status, S1
interface block status, and S1 link fault causes
Cell Includes the numbers of sector devices, channels, baseband

Device processing boards, and carriers on each TX channel.
Info

(2020-01-20)
SingleRAN
Cell Lists the following information about a faulty cell:

Dashboar ● Counters related to cell unavailability, including
d L.Cell.Unavail.Dur.Sys, L.Cell.Unavail.Dur.Manual,
L.Cell.Unavail.Dur.EnergySaving, and
L.Cell.Unavail.Dur.Sys.S1Fail
● Cell alarms
● Cell operation logs (excluding those related to DSP and LST
MML commands)
Fault Displays the DSP CELL command output for cell status analysis,
Diagnosis and provides cell setup failure causes based on cell unavailability
Result of error information. There are no diagnosis results indicating the
Cells degrading of cell serving capability and no diagnosis result
indicating RF unit service unavailability.
Heavy-Traffic Faults
For heavy-traffic faults, the fast fault diagnosis function provides site and cell
diagnosis information, as described in Table 4-20 and Table 4-21.
Table 4-20 Site diagnosis information for heavy-traffic faults


Informati ● RRC Success Rate indicates the site-level RRC setup success rate.
on Table
● E-RAB Setup Success Rate indicates the site-level E-RAB setup
success rate.
● Call Drop Rate indicates the site-level call drop rate.
● DL Cell Throughput (Kbit/s) indicates the site-level downlink
cell throughput.
● UL Cell Throughput (Kbit/s) indicates the site-level uplink cell
throughput.

Alarms Known alarms on specific sites can be used to identify other sites
with the same alarms.
Fault Displays the preliminary fault analysis result on the current site and
Diagnosis provides recovery suggestions.
Result of
Sites

(2020-01-20)
SingleRAN
Table 4-21 Cell diagnosis information for heavy-traffic faults


Informati ● RRC Success Rate indicates the cell-level RRC setup success rate.
on Table
● E-RAB Setup Success Rate indicates the cell-level E-RAB setup
success rate.
● Call Drop Rate indicates the cell-level call drop rate.
● DL Cell Throughput (Kbit/s) indicates the cell-level downlink
cell throughput.
● UL Cell Throughput (Kbit/s) indicates the cell-level uplink cell
throughput.
NOTE
The cell dashboard displays cell data of a maximum of five KPIs.
Fault Displays the preliminary fault analysis result on the current cell and
Diagnosis provides recovery suggestions.
Result of
Cells
Interference
If the TDD interface scenario is selected, the fast fault diagnosis only provides site
diagnosis information, as shown in Table 4-22.
Table 4-22 Site diagnosis information for interference faults

Clock Alarm Displays analysis results of clock alarms on the entire network.
Analysis
Forcible Displays analysis results of forcible phase synchronization events

Phase on the entire network.
Synchroniza
tion Event
Analysis

(2020-01-20)
SingleRAN
Risky Provides the following two types of information:

Operation ● Information of the sites with the following MML command
operation logs on the entire network:
– ACT CELL
– MOD CELLFRAMEOFFSET
– ADD CELLFRAMEOFFSET
– RMV CELLFRAMEOFFSET
– MOD RRU
– MOD CELL
● Information of sites with EVT-26213 NE Startup reported.
DA Traffic Displays analysis results of DA traffic statistics that meet the

Statistics condition on the entire network.
Distribution Provides a distribution of interference characteristics according to

of Symbol- the diagnosis logic, using all TDD cells at all sites based on the
Level analysis results of clock alarms, forcible phase synchronization
Interference events, risky operations, and DA traffic statistics.
Characteristi
cs
Descriptions of Fault Tree and Diagnosis Report

The fault tree displays the complete diagnosis results, as shown in Figure 4-18.
Diagnosis items highlighted in red indicate faults which can be linked to detailed
diagnosis results in the sub-scenario. Diagnosis items highlighted in green indicate
that no faults occur and no detailed results are provided.

(2020-01-20)
SingleRAN
Figure 4-18 Diagnosis result example
Figure 4-19 shows detailed diagnosis results in a sub-scenario.
Figure 4-19 Detailed diagnosis result example in a sub-scenario
Corresponding recovery advice is provided as a reference after fault diagnosis in a

sub-scenario. For details, see Figure 4-20.

(2020-01-20)
SingleRAN
Figure 4-20 Recovery advice example in a sub-scenario
Imported Voice Parameter Check

The FMA allows users to import basic voice parameters on the GUI and perform
simple parameter check on imported parameters without conditions. This function
is controlled by a switch. The voice parameter check can be performed only when
the switch is turned on, as shown in Figure 4-21 and Table 4-23.
Figure 4-21 Voice parameter check tab page
Table 4-23 Description of the voice parameter check tab page

Voice ● If the switch is turned off, voice baseline parameter files cannot
Paramete be imported, and only traditional voice parameter check is
r Check supported.
● If this switch is turned on, voice baseline is imported for
parameter check.
By default, this function is disabled.
Export Export the baseline template for voice parameter check.
Import Import the baseline template for voice parameter check. Only file
types of .xlsx and .xls are supported.
Users need to turn on the voice parameter check switch, export a copy of basic
voice parameters via exporting the voice parameter template, and then modify the

(2020-01-20)
SingleRAN
exported voice parameters. Click Import Template to import the voice parameter
template. The FMA automatically checks the voice parameters in the imported
template. Start fast fault diagnosis and view the check result in the Voice
Parameters on the Fast fault diagnosis window. For details, see Performance KPI
Faults.

This function can quickly and accurately collect onsite information and improve
fault recovery efficiency.
● If collected NEs contain the LTE and NB-IoT sites, LTE eNodeB Urgent
Problem First Batch and LTE NB-IoT Urgent Problem First Batch are
selected by default.
● If collected NEs only contain LTE sites, LTE eNodeB Urgent Problem First
Batch is selected by default.
Table 4-24 lists the collected fault information.
Table 4-24 Collected fault information

Collection Item Scope
NE configuration file One file per NE
MML query output One file per NE
Results of pinging a base One file per NE

station from the MAE
Results of tracing routes from One file per NE

the MAE to a base station
Performance indicators During a specified collection period
Alarm data During a specified collection period
Operation logs saved on the During a specified collection period

MAE
Original operation logs of top One file per NE

3 NEs
For details, see "Network Information Collection" in MAE MBB Network

Management System Product Documentation.
4.1.2.4 Automatic Fault Detection

FMA supports automatic detection of performance KPI faults and cell faults,
followed by automatic fault diagnosis and information collection.
After automatic fault detection is enabled:
● For performance KPI faults, FMA periodically performs automatic
measurement and identifies abnormal network KPIs.

(2020-01-20)
SingleRAN
● For cell faults, FMA automatically obtains the total number of cells with
alarms reported within a specified measurement period. If the number of
alarms exceeds the threshold, it is regarded that a cell accident occurs. The
cell alarms that have been counted and reported will be excluded from the
next measurement period. Measurement periods can be set on the FMA by
choosing Settings > Wireless Settings > Fault Auto Detection > Automatic
Detection of Wireless Faults > Cell Unavailable Self-Detection Conditions.
The FMA automatically performs fault diagnosis and information collection after
detection:
● The FMA implements fault diagnosis on selected NEs and provides a diagnosis
report. The diagnosis reports triggered by automatic detections and manually
triggered are consistent. For details, see 4.1.2.3 Information Collection.
● The collected fault information triggered by automatic detections and
manually triggered on the FMA is consistent. For details, see 4.1.2.3
Information Collection.
Users can log in to the FMA to view and download diagnosis reports and fault
information.
4.1.2.5 Auxiliary Fault Recovery

Auxiliary fault recovery provides fault recovery assistance for configuration faults
displayed in the fast fault diagnosis results. Auxiliary fault recovery provides the
following functions:
● Displaying the historical configuration change track of the faulty NE: After the
fast fault diagnosis function identifies a faulty NE, the FMA displays all the
configuration changes made to the NE two hours before the fault occurs. This
helps users determine whether the fault is caused by changes in
configurations.
● Editing of auxiliary fault recovery scripts: The FMA provides a window for
editing auxiliary fault recovery scripts. Users can edit the MOCs and
parameters to be delivered to faulty NEs on the GUI. In addition, users can
select a configuration change record from the historical configuration change
track, and reconfigure specific parameters.
● Generating auxiliary fault recovery scripts: The FMA can interconnect with the
MAE-Deployment to generate and display auxiliary recovery scripts based on
the MOCs and parameters users specified in the script editing window.
Table 4-25 lists fault tree branches supported by this function.
Table 4-25 Fault tree branches supported by auxiliary fault recovery
Scenario Fault Tree Branch
Call drop Call Drop Rate > TNL Call Drop > Transport Link(SGW
IP)/MME Exception
Handover Inter-Frequency HO Success Rate > Handover Out

Failure > Neighbor Cell Incorrect Parameter
Configurations

(2020-01-20)
SingleRAN
Intra-Frequency HO Out Success Rate > Handover Out

Failure > Neighbor Cell Incorrect Parameter
Configurations
S1 HO Out Success Rate > Handover Out Failure >

Neighbor Cell Incorrect Parameter Configurations
X2 HO Out Success Rate > Handover Out Failure >

Neighbor Cell Incorrect Parameter Configurations
Cell unavailable Cell Unavailable > Abnormal RF Resources > RRU

Carrier Allocation Failure > RRU Channel Switched Off
4.1.2.6 Fault Recovery Confirmation

The FMA supports fault recovery confirmation in fast fault recovery scenarios. It
showcases the changes in KPIs or cell status after the recovery plan is executed.
The changes of NE KPIs, cell status, and alarm status are displayed in charts. Fault
handling personnel can use such data to determine whether a fault is rectified.
Table 4-26 lists the detailed functions of fault recovery confirmation.
Table 4-26 Functions of fault recovery confirmation

Function Sub-Function Description
Fault recovery 1-minute KPI Displays the 1-minute KPI trend of the
confirmation trend faulty site after the recovery plan is
executed, helping users to determine
whether the fault is recovered.
List of alarm Displays the alarm clearance status after

clearance status the recovery plan is executed, helping
users to determine whether the fault is
recovered.
List of cell status Displays the status of the fault scenario

and cell instance after the recovery plan is
executed, helping users to determine
4.1.3 NR Wireless Fault Management

NR wireless fault management is implemented on the MAE to help users
troubleshoot wireless faults on 5G networks.
NR wireless fault management obtains gNodeB configurations, alarms,
performance counters, and operation logs from the MAE and analyzes the fault.
After an analysis is complete, the fault analysis results are provided to help users
identify potential causes and accelerate service recovery. NR wireless fault
management provides the following functions:

(2020-01-20)
SingleRAN
● Fault overview
Multisite faults are analyzed to help users locate the faulty base station or
cell. Users can continue to perform fast fault diagnosis or information
collection.
function or manually selected, fault diagnosis can be performed on the faulty
base station or cell.
● Fault information collection
function or manually selected, information about the faulty base station or
cell can be collected.
Figure 4-22 shows the relationship between the preceding functions.
Figure 4-22 Relationship between NR fault management functions
Table 4-27 lists the supported NR wireless fault scenarios.
Table 4-27 NR wireless fault scenarios
Scenario Sub-Scenario Check Item
Performa Data transmission UL User Throughput (Kbit/s)

nce KPI
UL Cell Throughput (Kbit/s)
DL User Throughput (Kbit/s)
DL Cell Throughput (Kbit/s)
Access RRC Success Rate

(2020-01-20)
SingleRAN
Scenario Sub-Scenario Check Item
NGSIG Connection Setup Success Rate
QoS Flow Setup Success Rate
Service drop Service Drop Rate
Handover Intra-NR Intra-Frequency Handover Out

Success Rate
Intra-NR Handover In Success Rate
Inter-RAT Handover Out Success Rate (NR

to LTE)
Cell Fault Cell unavailable NR Cell Unavailable
Cell capability Cell Capability Degraded
Fault Interference Fault Average interference and noise received on

Scenario each uplink PRB (N.UL.NI.Avg)
For details on how to use FMA to handle NR wireless faults, see Fault
Management > FMA in MAE MBB Network Management System Product
Documentation.
When you group NEs in the topology view, it is recommended that the number of NEs in a
group be less than 200. FMA fault analysis can be performed by group to improve
efficiency.

Fault overview provides an overview of overall faults to help users learn the entire
network's operating status.
After users select the fault scenarios (as listed in Table 4-27), NR sites to be
analyzed, the fault occurrence time, and the comparison time, the fault overview
function performs fault analysis. Fault overview provides different information for
performance KPIs and cell faults.

For performance KPIs, the fault overview displays the following information.
● Top sites
Includes site name, KPIs obtained on the fault occurrence day, and KPIs
obtained at the comparison time, as shown in Figure 4-23.

(2020-01-20)
SingleRAN
Figure 4-23 Top sites example
● KPI trend chart

Includes the KPI changes on the fault occurrence day, the previous day, and
the same day from the previous week.
● KPI deterioration time
Displayed on a KPI trend chart.
● Failure cause value distribution and comparison with normal KPI time
According to the KPI calculation formula, KPI failure cause values are
decomposed and linked to related performance counters, and the KPIs at the
fault occurrence time are compared with those at a specified time, as shown
in Figure 4-24.
Figure 4-24 Failure cause value distribution example
● Top sites that affect KPIs

For the sites that require further analysis, fast fault diagnosis or information
collection can be performed, as shown in Figure 4-25.

(2020-01-20)
SingleRAN
Figure 4-25 Example of top sites that affect KPIs
● The FMA provides automatic analysis. If users select Automatic Analysis and click
Analyze, FMA automatically performs fault overview and fast fault diagnosis. No
manual intervention is required. If users do not select Automatic Analysis but click
Analyze, FMA only performs fault overview.
● "-" in the analysis result indicates that the corresponding counter data does not exist on
the EMS.
Cell Faults
For cell faults, fault overview displays the following information:
● According to the selected faulty scenario, FMA displays the numbers of sites
and cells where the fault occurs. The alarms are classified into active alarms
and historical alarms. Figure 4-26 shows an example.
Figure 4-26 Example of the number of sites and cells with faults
Only historical alarms generated within 24 hours before the analysis are recorded.
● List of cells that report alarms: displays the number of sites and cells where
an alarm related to the fault is reported. The alarms are classified into active
alarms and historical alarms. Figure 4-27 shows an example.
Figure 4-27 Example of the list of cells that report alarms
● Alarm quantity change trend. Figure 4-28 shows an example.

(2020-01-20)
SingleRAN
Figure 4-28 Alarm quantity change trend example
Interference Fault Scenarios
This function applies only to NR TDD.
If a user selects the interference scenario, the Fault Overview window displays the
following information.
● List of top interfered sites
Displays the interference contribution rates of the cells of each gNodeB in the
current NE group in descending order in the performance period starting from
T0. Interference contribution rate = Difference between the interference of a
cell and the interference baseline value/Difference between the interference
of all cells and the interference baseline value x 100%
● Top sites
The number of top N sites is set to 100 by default. All TDD cells of top 100
sites are displayed.
Top N sites are filtered based on the deterioration of interference-related counter values
and the deterioration of service KPIs of the corresponding NEs.
● Interference trend
Displays the trend curve of the interference-related counter values of the top
interfered NEs and the trend curve of the start time and end time of
yesterday and last week.

Fast fault diagnosis analyzes the performance of top sites identified using the fault
overview function. The analysis result provides associated information about KPIs,

(2020-01-20)
SingleRAN
active alarms, and operation logs for each of the top sites and each cell served by
the top sites at the time when KPIs deteriorate. By analyzing KPIs, active alarms,
and operation logs, this function helps users identify the minimum faulty units.
Fast fault diagnosis displays different diagnosis information for KPI faults and cell
faults.
For the detailed procedure of fast fault diagnosis, see the "Starting Fast Fault
Diagnosis" section under "FMA" in MAE MBB Network Management System

For performance KPI faults, the fast fault diagnosis function provides site- and
cell-level diagnosis information, as described in Table 4-28 and Table 4-29.
For interference faults, the fast fault diagnosis function only provides cell-level
diagnosis information.
Table 4-28 Site diagnosis information for performance KPI faults


Informati ● Contribution Rate indicates the ratio of failures in a site to the
● Version Change Info lists the latest software version updates of
a site.
● License Analysis displays active license-related alarms at the
fault occurrence time.
● Risky Operation displays risky operation records in a specified
period.

(2020-01-20)
SingleRAN
Transmiss Transmission diagnosis information is provided on the Original

ion Messages and Diagnosis Results tab pages.
Diagnosis After the completion of a diagnosis, the following information will
Info be provided:
● Transmission port information (the DSP ETHPORT command
output)
● ARP information learned by the transmission ports (the DSP ARP
command output)
● Configured route information (the output of the following
commands)
– DSP IPRT when the old transmission configuration model is
used
– DSP IPROUTE4 when the new transmission configuration
model is used
● Transmission quality of the Xn and NG interfaces (output of the
PING command)
● NG interface information (the DSP GNBCUNGINTERFACE
command output)
The preceding functions are supported in the scenarios of successful
NG interface signaling connection setup and successful intra-NR
incoming handover.

Alarms NOTE
Known alarms on specific sites can be used to identify other sites with the
same alarms.

(2020-01-20)
SingleRAN
Table 4-29 Cell diagnosis information for performance KPI faults


Informati ● Contribution Rate indicates the ratio of failures in a cell to the
● Actual value of a KPI indicates the cell KPI value at the time
when the KPI is analyzed. In the case of interference faults, the
basic cell information table provides the values of current
analyzed KPIs and associated service KPIs (average uplink PUSCH
MCS of the cell) at the time when the analysis is performed.
● Denominator (number of attempts) of a KPI indicates the
number of setup attempts related to this KPI, if a non-traffic-
volume-related KPI (such as success rate or service drop rate) is
analyzed.
● Heavily Loaded determines whether a cell is highly loaded
based on the CPU usage of the gNodeB board serving the cell
and the number of online users in the cell.
Users can select records generated in the latest two hours before
the fault occurs from operation logs for MAE-Deployment analysis.
For cell faults and heavy-traffic faults, select records generated at
the current time.
NOTE
The MAE-Deployment can only analyze records generated within two hours
before the fault occurrence time, and can only analyze MOD, RMV, and ADD
commands.
Board Displays the CPU usage trends of the main control board and BBP
Diagnosis serving a cell and the trend of the number of connected cell users.
Info This helps users observe the relationship between the cell KPI
changes and the board CPU usage.
Cell KPI Displays the trends of some cell KPIs.

Analysis
Interferen ● SiteName indicates the NE name.

ce ● CellName indicates the cell name.
Feature
Matching ● Cell ID indicates the cell ID.
Informati ● IsInterfered indicates whether interference exists in a cell.
on ● InterferenceType indicates the interference type of a cell. This
version supports only repeater interference and blocking
interference.
● Detail queries and displays the detailed spectrum scanning
waveform of a cell.

(2020-01-20)
SingleRAN
In the case of interference faults, in addition to the diagnosis information in Table 4-29, the
cell-level diagnosis information also displays the interference feature matching information
of all cells in the top interference sites selected by users. The following information is
displayed: site name, cell name, cell ID, whether interference exists in the cell, interference
type, and detailed information. Detailed information can be queried and detailed spectrum
scanning waveform curves can be displayed.
Cell Faults
For cell faults, the fast fault diagnosis function provides only site diagnosis
information, as described in Table 4-30.
Table 4-30 Diagnosis information for cell faults
Site Key Lists information about each faulty cell served by the site, including:
Configura ● Basic configuration: duplex mode, TX/RX mode, subframe ratio,
tion Table and others
● Operator information: local tracking area ID, TAC, operator
index, country code, and MNC, and others
● User-plane interface information: user-plane interface ID, user-
plane interface status, user plane block status, and user-plane
link fault causes
● NSA peer connection information: X2 interface ID, X2 interface
status, X2 interface block status, and X2 link fault causes
Cell Includes the numbers of sector devices, channels, baseband

Device processing boards, and carriers on each TX channel.
Info
Cell Lists the following information about a faulty cell:

Dashboar ● Counters related to cell unavailability
d
● Cell alarms
● Cell operation logs (excluding those related to DSP and LST
MML commands)
Fault Displays the DSP NRCELL command output for cell status analysis,
Diagnosis and provides cell setup failure causes based on cell unavailability
Result of error information. This version only supports cell unavailability
Cells scenarios.
Interference Fault Scenarios

For interference fault scenarios, the fast fault diagnosis function provides only the
Cell tab page and the diagnosis information is as described in Table 4-31.

(2020-01-20)
SingleRAN
Table 4-31 Diagnosis information in interference fault scenarios

Key cell Includes the cell ID, cell interference contribution rate, uplink
information interference, and PUSCH MCS.
table
Cell Dashboard Includes traffic statistics related to the NR cell and the NR
cell alarm.
Cell interference Includes the associated cell ID, indicates whether a cell is
information interfered, and shows the interference type of a cell.
Descriptions of Fault Tree and Diagnosis Report

The fault tree displays the complete diagnosis results, as shown in Figure 4-29.
Diagnosis items highlighted in red indicate faults which can be linked to detailed
diagnosis results in the sub-scenario. Diagnosis items in black indicate that no
faults occur and no detailed results are provided.
For NEs in NSA networking scenarios, the fault diagnosis function supports fault
tree for displaying the diagnosis results of the typical faults in NSA networking
scenarios such as access failures, service drops, and handover failures.
Figure 4-29 Diagnosis result example
Figure 4-30 shows detailed diagnosis results in a sub-scenario.
Figure 4-30 Detailed diagnosis result example in a sub-scenario
Corresponding recovery advice is provided as a reference after fault diagnosis in a

sub-scenario. For details, see Figure 4-31.

(2020-01-20)
SingleRAN
Figure 4-31 Recovery advice example in a sub-scenario

This function can quickly and accurately collect onsite information and improve
fault recovery efficiency.
Table 4-32 lists the collected fault information.
Table 4-32 Collected fault information

NE configuration file One file per NE
MML query output One file per NE
Results of pinging a base One file per NE

station from the MAE
Results of tracing routes from One file per NE

the MAE to a base station
Performance indicators During a specified collection period
MAE operation logs During a specified collection period
Original operation logs of top One file per NE

3 NEs
In NSA networking scenarios, when users select an NR NE, NR wireless fault

management automatically identifies the peer anchor eNodeB and collects

(2020-01-20)
SingleRAN
associated fault information. The collection items for the anchor eNodeB are the
same as that for the NR NE, as listed in Table 4-32.
For details, see "Network Information Collection" in MAE MBB Network

4.1.3.4 Auxiliary Fault Recovery

Auxiliary fault recovery provides fault recovery assistance for specific configuration
faults displayed in the fast fault diagnosis results. You can view the list of faults in
a specific fault scenario, and look up fault recovery suggestions on faults with
special notes, as well as advice on MML commands for fault recovery.
Table 4-33 lists fault tree branches supported by this function.
Cell Unavailable An exception occurs when the NRDUCell is

bound to an NRCell.
The gNBCUF1Interface for an NRCell is faulty.
The frequency band configured for an NRCell

differs from that configured for the
corresponding NRDUCell.
The duplex mode configured for an NRCell

differs from that configured for the
corresponding NRDUCell.
4.1.3.5 Fault Recovery Confirmation

showcases the changes in KPIs or cell status after the recovery plan is executed.
The changes of NE KPIs, cell status, and alarm status are displayed in visualized
graphics on the dashboard. Fault handling personnel can use such data to
determine whether a fault is rectified. The following table lists the detailed
functions.
Fault recovery 1-minute KPI Displays the 1-minute KPI trend after the
confirmation trend recovery plan is executed, helping users to
determine whether the fault is recovered.
List of alarm Displays the alarm clearance status after

clearance the recovery plan is executed, helping
status users to determine whether the fault is
recovered.

(2020-01-20)
SingleRAN
List of cell Displays the status of the cell instance

status after the recovery plan is executed, helping
users to determine whether the fault is
recovered.
Saving of the Saves the KPI monitoring results, cell fault

recovery alarm clearance results, and cell status
confirmation results.
results
4.1.3.6 Automatic Fault Detection

FMA supports automatic detection of cell faults and KPI faults for NR networks.
After the detection, the FMA automatically performs fault diagnosis and
information collection.
After automatic fault detection is enabled:
● FMA automatically obtains the total number of cells with alarms reported
within a specified measurement period. If the number of alarms exceeds the
threshold, it is regarded that a cell accident occurs. The cell alarms that have
been counted and reported will be excluded from the next measurement
period. Measurement periods can be set on the FMA by choosing Wireless
Settings > Fault Auto Detection > Automatic Detection of Wireless Faults
> Cell Unavailable Self-Detection Conditions.
● FMA provides a portal for interconnecting with the MAE-Evaluation which
performs automatic detection of KPI faults. After the detection, the KPI
detection results and the list of abnormal NEs are displayed on the FMA
according to the feedback from the MAE-Evaluation. The IP address of the
MAE-Evaluation and measurement periods can be set on the FMA by
choosing Wireless Settings > Fault Auto Detection > Automatic Detection
of Wireless Faults > KPI Fault Detection Settings.
detection.
● After cells unavailable diagnosis is performed on the entire network, the FMA
automatically generates a diagnosis report based on the default specifications
(three sites and three cells). The diagnosis reports triggered by automatic
detections and manually triggered are consistent. For details, see 4.1.3.2 Fast
Fault Diagnosis.
● For KPI faults automatic detection and diagnosis, the FMA automatically
starts fault overview and fault matching based on the list of abnormal NEs
received from the MAE-Evaluation. The procedure is consistent with that of
the manually triggered fault overview. For details, see 4.1.3.1 Fault Overview.
● The fault information collected by automatic detection is the same as the
data collected by the FMA manually. For details, see 4.1.3.3 Information
Collection.
Users can log in to the FMA to view and download diagnosis reports and fault
information.

(2020-01-20)
SingleRAN
4.2 Transmission Fault Management

The FMA transmission fault management is used to delimit and locate a fault at
the transmission layer of a radio access network (RAN).
● Fault overview
● Information collection
● Automatic fault detection
● Auxiliary fault recovery
● Fault recovery confirmation
Transmission fault management applies to UMTS, LTE, and NR. Table 4-34 lists
the NE types that support transmission fault management.
Table 4-34 NE types supporting transmission fault management
NE Type Model
Macro base stations 3900 and 5900 series base stations
LampSite base stations DBS3900 LampSite
Base station controllers BSC6900

BSC6910
4.2.1 Fault Overview

Fault overview provides a transmission network fault status overview. The base
station controller fault overview and base station fault overview provide the
overall situation of the faulty interfaces for these two NEs, including the interface
status, configuration information, NE RAT, and fault occurrence time. Based on the
information, users can determine the extent of the damage to the NE transmission
interface.
Fault overview includes the following typical fault scenarios in both base stations
and base station controllers: service interruption (normal O&M channel) and O&M
channel disconnection. In each fault scenario, X questions about troubleshooting,
reporting time distribution of active alarms, and detailed fault information are
displayed.
A fault overview table provides the distribution of faults on networks (from X

questions about troubleshooting) and NEs.
● Detailed information of base stations provides the fault information about

the O&M, S1, X2 between a gNodeB and an eNodeB, and Iub interfaces.
● Detailed information of base station controllers provides the fault
information about the O&M, Iu-CS, Iu-PS, and Iur interfaces.

(2020-01-20)
SingleRAN
Based on information in Table 4-35, Table 4-36, Table 4-37 and Table 4-38, FMA
generates a fault overview table listing alarm impacts. UMTS alarms are reported
on base station controllers.
Table 4-35 UMTS alarms
Alarm ID Alarm Name
ALM-21543 SCTP Link IP Address Unreachable
ALM-21521 SCCP Subsystem Prohibited
ALM-21551 M3UA Link Fault
ALM-21552 M3UA Destination Entity Route Unavailable
ALM-21553 M3UA Destination Entity Inaccessible
ALM-21581 Path Fault
ALM-21393 Adjacent Node IP Path Ping Failure
ALM-21580 IP Path Blocked
ALM-22214 NodeB Unavailable
ALM-22204 NCP Faulty
ALM-22205 CCP Faulty
ALM-22213 CCP Information Inconsistency Between the RNC and the

NodeB
ALM-25902 Remote Maintenance Link Running Data and Configuration

Mismatch
ALM-40012 NE Is Disconnected
NOTE
ALM-301 NE Is Disconnected is reported by default for a
disconnected NE. Users can select the Locate NE Based on
Disconnection Alarm switch for a certain type of NEs. ALM-40012
NE Is Disconnected is reported for NEs with this switch enabled.
For details of the configuration procedure, choose General > Alarm
Maintenance Tool Management > Locate NE Based on
Disconnection Alarm on the OSMU online help.
Table 4-36 LTE alarms
Alarm ID Alarm Name
ALM-29201 S1 Interface Fault
ALM-25886 IP Path Fault

(2020-01-20)
SingleRAN
Alarm ID Alarm Name
ALM-25952 User Plane Path Fault
ALM-25954 User Plane Fault
ALM-29213 eNodeB S1 Control Plane Transmission Interruption

Mismatch
NOTE
disconnected NE. Users can set the Locate NE Based on
Table 4-37 NR alarms

Alarm ID Alarm Name
ALM-25954 User Plane Fault
ALM-29800 gNBX2 Interface Fault
ALM-29805 gNBF1 Interface Fault
ALM-25886 IP Path Fault
ALM-25952 User Plane Path Fault

Mismatch
NOTE
disconnected NE. Users can set the Locate NE Based on

(2020-01-20)
SingleRAN
Table 4-38 NE disconnection alarms on the MAE

Alarm ID Alarm Name
Fault overview offers the following functions:

● Supports the export of faults for forwarding and offline review.
● Supports scenario-specific cross-domain information export of faulty NEs
(including transmission path information and LLDP notification information
report) to facilitate joint troubleshooting of radio access networks and
transmission networks. LLDP stands for Link Layer Discovery Protocol. It is a
layer 2 discovery protocol defined in IEEE 802.1ab. With the LLDP, the element
management system (EMS) can rapidly obtain the layer 2 network topology
information and changes. LLDP must be enabled on both the NE and FMA to
take effect. For details, see 7.3.1 Activation.
● Supports fast fault diagnosis and fault information collection for selected NEs.
● Allows users to export key transmission data used for node configuration. If
transmission faults occur in a large number of sites, transmission services are
affected. In this way, key transmission configuration information of related
NEs can be quickly generated. This helps wireless and fault handling
personnel to demarcate and locate faults.
● Allows transmission configuration data to be classified based on different
scenarios: signaling plane fault, user plane fault, and OM fault, as shown in
Table 4-39, Table 4-40, and Table 4-41.
Table 4-39 Signaling plane fault scenario

Information Name Description
Type
S1-C basic S1INTERFACE S1InterfaceId

information
CNOPERATOR CnOperatorId, MCC, and MNC of the S1-
C interface
EPGROUP EPGROUP ID of the link in the EP model
SCTPLNK S1-C link SCTPNO, local and peer IP

address, local and peer port numbers
(specified by LOCPORT and PEERPORT),
and fault information
IPRT Next hop information of the S1-C

interface
VLAN and VLAN ID, VLANPRIO, and DSCP value of

QoS the S1-C interface
information

(2020-01-20)
SingleRAN

Type
IPsec-related IPsec Flag YES/NO: Indicates whether the link is

information encrypted by IPsec.
displayed in the
IPsec scenario DEVIP If the IPsec networking is used, the
physical IP address of the link (DEVIP,
when PT is ETH) is displayed.
IKEPEER SeGW IP address and IKEVERSION
IKEPROPOSAL PROPID and AUTHMETH (PSK/IKE

displayed)
ACLRULE ACLID and RULEID specify which ACL

rule to be matched.
APPCERT Name and expiration date of the

certificate used by the current IPsec
tunnel
Physical port ETHPORT Port number, port attribute (optical/

information electrical), MAC address, and MTU
Table 4-40 Signaling plane fault scenario

Type
S1-U basic CNOPERATOR CnOperatorId, MCC, and MNC of the S1-

information U interface
EPGROUP EPGROUP ID of the link in the EP model
USERPLANEH Local/Peer IP address of the S1-U link

OST & and fault information (obtained by
USERPLANEPE running the DSP EPGROUP command)
ER or IPPATH
GTP-U static Whether STATICCHK is enabled for GTP-

detection U static detection
switch status
IPRT Next hop information of the S1-C

interface
VLAN and QoS VLAN ID, VLANPRIO, and DSCP value of

information the S1-U interface

displayed in the
IPsec scenario

(2020-01-20)
SingleRAN

Type
DEVIP If the IPsec networking is used, the

physical IP address of the link (DEVIP,

displayed)

rule to be matched.

tunnel

Table 4-41 O&M fault scenario

Type
OMCH basic OMCH Active/standby flag, local and peer IP

information configuration addresses, and whether routes are
information bound
LST EMS The IP address of the connected MAE is

displayed.
IPRT Next hop information of the OMCH
VLAN and QoS VLAN ID, VLANPRIO, and DSCP value of

information the OMCH
SSL-related Indicates whether the SSL connection is

information used and which authentication mode is
used.

certificate used by the SSL connection

displayed in
the IPsec DEVIP If the IPsec networking is used, the
scenario physical IP address of the link (DEVIP,

(2020-01-20)
SingleRAN

Type

displayed)

rule to be matched.

tunnel

4.2.2 Fast Fault Diagnosis

Users can find typical faulty NEs based on the fault overview of FMA transmission
fault management, and then start fast fault diagnosis (also called one-click fault
diagnosis). The fault diagnosis covers port faults, IP address segment faults, and
cross-NE or single-NE transmission configuration check exceptions.
Fast fault diagnosis includes the following tab pages: topology, fault diagnosis
report, intelligent continuity check (user/signaling plane), intelligent continuity
check (O&M/clock plane), custom continuity check, and custom trace route
(MAE).
Topology
On the Topology tab page, users can view the complete network topology and
quickly understand the networking of the NEs managed by the MAE.
This topology view offers the opportunity to review link information about a
specific NE, quickly query NE status, and perform ping and additional O&M
operations. Table 4-42 describes the topology view types and corresponding
functions.
Table 4-42 Topology view types

Type Function
Network Displays the global connection relationship on the entire network

topology for users to quickly obtain the information, NE quantity, and
association on the transmission network.
Base Displays the topology information about base station controllers.

station The information includes the connection relationships between base
controller station controllers and base stations/core networks, as well as peer
topology devices discovered by LLDP.

(2020-01-20)
SingleRAN
Type Function
Subnet Displays the topology information about security gateways,

topology including the connection relationships with peer devices discovered
of a by LLDP.
security
gateway
Base Displays the topology information about base stations. The

station information includes the connection relationships between base
topology stations and between base stations and base station controllers.
O&M/ Displays the O&M and clock plane topology of base stations for
clock users to query the IP clock, NTP, and O&M information about the
plane base stations.
topology
● A topology view can be saved as an image.

● The O&M/clock plane topology of eNodeBs and gNodeBs does not include NTP
networking information.
● LLDP information cannot be obtained in a non-Ethernet transmission scenario (such as
IP over E1), because LLDP is layer 2 Ethernet protocol and layer 2 packets cannot be
forwarded in cascading and co-transmission scenarios.
● When base stations are directly connected to a router, the gateway IP address on the
network topology generated by FMA is marked on a layer 3 network. This is because
the LLDP protocol cannot determine whether the discovered neighboring device is a
router or not.
● The transmission data about key configuration nodes can be exported. It can help the
wireless and transmission fault handling personnel demarcate and locate faults. For
details about exporting the key transmission data, see 4.2.1 Fault Overview.
If there are faulty NEs in the topology, the ping test function helps users to quickly
identify transmission problems, as shown in Figure 4-32.
Figure 4-32 Ping test function
Table 4-43 describes the ping test function.

(2020-01-20)
SingleRAN
Table 4-43 Ping test description

Function Description Impa Operation
ct on Specificati
Servic ons
es
Intelligent Detects the IP link continuity between the No Each NE

Continuity following NEs. A base station controller, supports
Check eNodeB, or gNodeB can serve as the only one
(User/ source end, and the peer NE is the check
Signaling destination end. command
Plane) ● Between a base station controller and at a time.
the peer NE which can be a GBTS,
NodeB, base station controller, or core
network NE.
● Between an eNodeB and the core
network
● Between a gNodeB and an eNodeB
Intelligent Checks the connectivity of IP links

Continuity between the base station (NodeB,
Check eNodeB, and gNodeB) and the peer NE
(O&M/Clock (MAE). This function allows users to set
Plane) the number of ping packets, ping
detection duration, ping packet size,
timeout value, DSCP, and interval for
sending packets.
Custom Checks the continuity of IP links from the

Continuity MAE to wireless devices or user-defined IP
Check addresses.
(MAE)
Custom Traces the routes from the MAE to wireless

Trace Route devices or user-defined IP addresses based
(MAE) on user-defined parameters to detect
connectivity faults segment by segment
and determine the faulty nodes.
Fault Diagnosis Report

Users can view the one-click diagnosis report on the fault diagnosis report tab
page. One-click diagnosis report provides comprehensive analysis of the on-site
fault information (see Table 4-44).

(2020-01-20)
SingleRAN
Table 4-44 One-click fault diagnosis report
Parameter Description
Topology For a faulty NE, only the peer device of the faulty interface
is displayed. For a non-faulty interface, the peer device is
not displayed in the topology.
● Provides Iub, Abis, S1, X2 between gNodeBs and
eNodeBs (NSA), X2 between gNodeBs and gNodeBs
(NSA), Xn between gNodeBs and gNodeBs (SA), and
O&M interfaces for a faulty base station.
● Provides Iur, Iu-PS, Iu-CS, A, and Gb interfaces for a
faulty base station controller.
NOTE
If the peer devices are in the same type, only one peer device of
the faulty interface is displayed in the topology view.
Summary Reports the potential fault scope or points, and

conclusions.
Segment-based Displays segment-based ping commands by interfaces (Iu-

ping commands PS, Iu-CS, Iur, A, or Gb) and planes (signaling plane, user
and trace routes plane, or O&M plane).
If the ping command fails, tracing route is performed to
further locate the fault.
Active alarm Displays transmission alarms by NEs to help users quickly

locate the root cause of the fault.
Status query Displays the status information about the transmission

object on an NE. The information includes the
configurations, available status, IP address, and subnet
mask of the object.
Radio Automatically checks exceptions in cross-NE or single-NE

configuration transmission configuration, including but not limited to
check bandwidth configuration consistency and VLAN priority.
Operation logs Records logs within 8 hours before and after the fault
occurrence time during one-click fault diagnosis.
Traffic statistics Displays KPI values of base station controllers.

Transmission KPIs are included in an overall tab page. One
tab page is provided for each function subset, displaying
KPI values of all measurement periods for the current NE
within 24 hours.
Fault tree The fault tree branches are provided for auxiliary fault
recovery. The fault scenarios include O&M link
disconnection and service interruption.
This function can diagnose faults in a maximum of 10 sites at a time. Users can
export the one-click fault diagnosis report in the html format for offline view.

(2020-01-20)
SingleRAN
● After report generation, ten reports can be exported within 10s.

● The X2 interface information is not displayed in the one-click fault diagnosis report due
to the large quantity of X2 interfaces.
4.2.3 Information Collection

Information collection for transmission faults is only supported for eNodeBs and
gNodeBs, as shown in Table 4-45.
Table 4-45 Information collection for transmission faults
NE configuration file One file for each NE, five NEs in total
MML query output One file for each NE, five NEs in total
Results of pinging a base station from One file for each NE, five NEs in total
the MAE
Results of tracing routes from the MAE One file for each NE, five NEs in total
to a base station
KPI data During a specified collection period
MAE operation logs During a specified collection period
Original operation logs of top 3 NEs One file for each NE, three NEs in total
4.2.4 Automatic Fault Detection

To enable automatic detection of transmission faults on the FMA, choose Settings
> Transmission Settings, turn on the Automatic Detection switch, and specify
Accident Condition and Alarm Condition.
detection:
● The FMA selects top faulty sites, performs fault diagnosis, and generates a
diagnosis report. The diagnosis reports triggered by automatic detections and
manually triggered are consistent, expect that the former report does not
include topology information. For details, see 4.2.2 Fast Fault Diagnosis.
● The collected fault information triggered by automatic detections and
manually triggered on the FMA is consistent. For details, see 4.2.3
Information Collection.
Users can log in to the FMA to view and download diagnosis reports and
transmission fault information.

(2020-01-20)
SingleRAN
4.2.5 Auxiliary Fault Recovery

Auxiliary fault recovery provides fault recovery assistance for specific configuration
faults displayed in the fast fault diagnosis results. Auxiliary fault recovery provides
the following functions:
● Displaying the historical configuration change track of the faulty NE: After the
fast fault diagnosis function identifies a faulty NE, the FMA displays all the
configuration changes made to the NE two hours before the fault occurs. This
helps users determine whether the fault is caused by changes in
configurations.
● Editing of auxiliary fault recovery scripts: The FMA provides a window for
editing auxiliary fault recovery scripts. Users can edit the MOCs and
parameters to be delivered to faulty NEs on the GUI. In addition, users can
select a configuration change record from the historical configuration change
track, and reconfigure specific parameters.
● Generating auxiliary fault recovery scripts: The FMA can interconnect with the
MAE-Deployment to generate and display auxiliary recovery scripts based on
the MOCs and parameters users specified in the script editing window.
Table 4-46 lists the fault tree branches supported by auxiliary fault recovery.

OM Disconnection None
NE Service Interruption NE Service Interruption > NE Report IKE

Negotiate Fail Alarm
4.2.6 Fault Recovery Confirmation

showcases the changes in the status of transmission ports and transmission
alarms using visualized graphics on the dashboard after the recovery plan is
executed. Fault handling personnel can use such data to determine whether a
fault is rectified. Table 4-47 lists the detailed functions of fault recovery
confirmation.
Table 4-47 Functions of fault recovery confirmation

Fault recovery List of Displays the alarm clearance status after

confirmation transmission the recovery plan is executed, helping
alarm status users to determine whether the fault is
recovered.

(2020-01-20)
SingleRAN
List of Displays the status of the transmission

transmission port port instance after the recovery plan is
status executed, helping users to determine
Saving of the Saves the transmission fault alarm

recovery clearance results and transmission ports
confirmation status result.
results

(2020-01-20)
SingleRAN
FMA Feature Parameter Description 5 Network Analysis
5 Network Analysis
5.1 Benefits
● Facilitates fault handling and shortens the duration of the fault impact on
network services, ensuring stable network operation.
● Improves the network or NE fault location efficiency and reduces O&M costs.
● Lowers skill requirements for fault handling.
5.2 Impacts
No impact

(2020-01-20)
SingleRAN
FMA Feature Parameter Description 6 Requirements
6 Requirements
6.1 Licenses
N/A
6.2 Software
Prerequisite Functions
None
Mutually Exclusive Functions

None
6.3 Hardware
Table 6-1 lists the MAE hardware and networking scenarios that support this
feature.
Table 6-1 The MAE hardware and networking scenarios that support FMA feature
Platform Server Scenario Supported Deployment

Type in This Condition
Scenario
ATAE N/A ATAE Cluster Yes If FMA is supported,

cluster (including TS and FMA can be enabled
active MAE co-cluster) when the following
board (less conditions are met:
than 1200 ATAE Cluster Yes
● The available
equivalent Online Remote
memory is at
NEs) HA
least 8.5 GB.

(2020-01-20)
SingleRAN
FMA Feature Parameter Description 6 Requirements
Platform Server Scenario Supported Deployment

Type in This Condition
Scenario
Trace Server No ● The idle CPU

(ATAE cluster, usage exceeds
Standalone) 35%.
ATAE Cluster No
Emergency
System
ATAE N/A ATAE Cluster Yes An independent

cluster (including TS and board, which does
independen MAE co-cluster) not consume the
t boards MAE resources,
ATAE Cluster Yes without any
Online Remote restriction on board
HA resources.
Virtual N/A Cluster System Yes This function is

enabled by default.
6.4 Others
Account and Permission
An FMA user account must be created. For details, see 7.1 When to Use.
Port Requirements
This feature requires that related ports be enabled on the MAE. For details, see
MAE Communication Matrix.

(2020-01-20)
SingleRAN
FMA Feature Parameter Description 7 Operation and Maintenance
7 Operation and Maintenance
7.1 When to Use

It is recommended that FMA be enabled in the post-upgrade health check,
accident drills, and accident handling on the live network.
The hardware required by the FMA feature is automatically deployed together

with the MAE. If the number of equivalent NEs does not exceed 1200, FMA can be
deployed together with the MAE. If the number of equivalent NEs is greater than
1200, an independent board is required to deploy FMA.
The FMA deployment process is as follows:
● Start the FMA service on the MAE OSMU. For details, see "Querying and
Changing FMA Service Status" in MAE MBB Network Management System
● Create the FMA user account on the MAE and grant user permissions.
For details, see "Setting Rights for Related FMA Users" in MAE MBB Network
If GSM and UMTS FMA needs to be used on the MAE, the corresponding
device types must be added to the management domain of the FMA user on
the MAE. The added device types include BSC6900GSM, BSC6900GU,
BSC6900UMTS, BSC6910GSM, BSC6910GU, and BSC6910UMTS. You can add
device types based on actual requirements.
The FMA software can be separately upgraded to a later R/C version for GSM and
UMTS NEs to accelerate urgent fault recovery on the live network.
The FMA and MBSC must be of the same R/C version. For example, if the MBSC
version is V900R018C10SPC530, the FMA version must be V900R018C10 FMA Rules
Update Packet.
The O&M personnel can obtain the separate software package to upgrade FMA from
support.huawei.com. Choose Software > Wireless Network > Wireless Network
Common > SingleRAN > SingleRAN_O&M tools. Click the hyperlink of the required
FMA software package and download it using a Huawei engineer account.
The FMA software can be installed and uninstalled only by running MML commands.

(2020-01-20)
SingleRAN
● For details on how to start the FMA web client on the MAE, see "Logging In
to the Main Window of the FMA" in MAE MBB Network Management System
● For details on how to initialize the FMA (configure the data synchronization
information between the FMA and the MAE), see "Setting Data
Synchronization Between the FMA and MAE" in MAE MBB Network
For deployment process details, see "FMA Operation Process" in MAE MBB
Network Management System Product Documentation.
7.2 Precautions
● If the available resources on the MAE cannot meet the minimum operating
requirements, the feature cannot be enabled.
● If a large number of MAE resources are consumed, the FMA feature is forcibly
disabled to prevent interruption of the MAE operation. If the FMA is disabled
during fault handling, the troubleshooting process is forcibly stopped. After
resources are released, restart the FMA feature on the MAE OSMU. For
details, see "Querying and Changing FMA Service Status" in MAE MBB
● The FMA feature is available only when data processing and calculation are
complete using a data configuration account. A maximum of 48 hours are
required for data processing and calculation, depending on network data
volume.
7.3 Data Configuration

This section describes the deployment of WOFD-014600 Fault Management
Assistant (FMA) on the MAE.
In an integrated deployment, GSM and UMTS wireless fault management is
enabled on the LMT by default. For details, see BSC6900 GU LMT User Guide and
BSC6910 GU LMT User Guide.
7.3.1 Activation
The FMA feature is activated on the MAE OSMU. For details, see "Querying and
Perform the following operations on both the FMA and NE to activate the LLDP
function:
On the FMA:
Step 1 Click Settings and choose Transmission Settings > Synchro Settings.
Step 2 Select Subscribe LLDP Messages.
----End
On the base station controller and base station:

(2020-01-20)
SingleRAN
● Using the MAE-Deployment

On the MAE-Deployment, set LLDP Notify Switch in the LLDPGLOBAL MO
to ENABLE.
– Set port parameters in the LLDPLOCAL MO when the old transmission
configuration model is used.
– Set port parameters in the LLDP MO when the new transmission
configuration model is used.
For detailed operations on the MAE-Deployment, see MAE-Deployment
● Using MML commands
a. Run the SET LLDPGLOBALINFO command. Set NOTIFYSW to ENABLE
and specify other parameters.
b. Run the following command to add a port through which LLDP messages
are reported.
▪ ADD LLDPPORT when the old transmission configuration model is

used
▪ ADD LLDP when the new transmission configuration model is used
7.3.2 Deactivation
The FMA feature is deactivated on the MAE OSMU. For details, see "Querying and
Perform the following operations on both the NE and FMA to deactivate the LLDP
function:
On the base station controller and base station:
Step 1 Run the SET LLDPGLOBALINFO command and set NOTIFYSW to

DISABLE(DISABLE).
Step 2 Run the following commands to delete the information about the LLDP port.
● RMV LLDPPORT when the old transmission configuration model is used
● RMV LLDP when the new transmission configuration model is used
----End
After logging in to the FMA system, perform the following operations:
Step 1 Click Settings and choose Transmission Settings > Synchro Settings.
Step 2 Deselect Subscribe LLDP Messages.
----End
7.3.3 Using the MAE-Deployment

N/A

(2020-01-20)
SingleRAN
7.4 Activation Verification

After the FMA feature is enabled, you can use the following methods to verify if
the FMA is operating properly:
● Check if the FMA is operating properly on the MAE OSMU. For details, see
"Querying and Changing FMA Service Status" in MAE MBB Network
● Check if you can switch from the MAE client to the FMA web client. For
details, see "Logging In to the Main Window of the FMA" in MAE MBB
● Note that you must wait for up to 48 hours to use the FMA feature after the
data is synchronized between the FMA and the MAE. The duration varies
depending on the number of NEs managed by the MAE. For details, see
"Setting Data Synchronization Between the FMA and MAE" in MAE MBB
● Check if you can start fault diagnosis on the wireless fault management
module.
● Check if you can start one-click fault diagnosis on the transmission fault
management module.
● Check if you can view basic information about peer devices in the network
topology. If this function is supported, the LLDP function takes effect.
7.5 Network Monitoring

When the FMA feature is in operation, users can check whether the FMA service is
performing properly on the MAE OSMU.
When a fault occurs on the FMA, no alarm is generated on the MAE client. Users
can check whether the FMA process and services are performing properly on the
MAE OSMU to determine whether the FMA is faulty. For details, see "Querying
and Changing FMA Service Status" in MAE MBB Network Management System

(2020-01-20)
SingleRAN
FMA Feature Parameter Description 8 Glossary
8 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary in the MAE
product documentation.

(2020-01-20)
SingleRAN
FMA Feature Parameter Description 9 Reference Documents
9 Reference Documents
● MAE MBB Network Management System Product Documentation

● MAE Online Help
● MAE Communication Matrix

(2020-01-20)

FMA (SRAN16.1 - Draft A)

Uploaded by

Copyright:

Available Formats

FMA (SRAN16.1 - Draft A)

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

FMA (SRAN16.1 - Draft A)

Uploaded by

Copyright:

Available Formats

SingleRAN

FMA Feature Parameter Description

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.............................................................................................................3

Issue Draft A Copyright © Huawei Technologies Co., Ltd. ii

4.1.3.4 Auxiliary Fault Recovery.............................................................................................................................................. 64

7 Operation and Maintenance.............................................................................................. 82

Issue Draft A Copyright © Huawei Technologies Co., Ltd. iii

This section describes changes not included in the "Parameters", "Counters",

1.1 SRAN16.1 Draft A (2020-01-20)

Added support for interference feature identification and None

Added support for automatic detection of gNodeB KPI None

Changed the name of U2020 to MAE-Access, the name None

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 1

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 2

2 About This Document

2.1 General Statements

● The technical principles of features and their related parameters

2.2 Applicable RAT

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 3

2.3 Features in This Document

Feature ID Feature Name Section

WOFD-0146 Fault Management 4 Principles

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 4

Table 3-1 FMA functions

Function Description Wireless FM Wireless FM Wireless FM Trans FM

Fault overview Provides a √ √ √ √

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 5

Function Description Wireless FM Wireless FM Wireless FM Trans FM

Fast fault Provides a √ √ √ √

Hierarchical First analyzes √ √ x x

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 6

Function Description Wireless FM Wireless FM Wireless FM Trans FM

Information Collects onsite √ √ √ √

Auxiliary fault Provides fault x √ √ √

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 7

Function Description Wireless FM Wireless FM Wireless FM Trans FM

Fault recovery Allows users to √ √ √ x

Service query Checks whether √ x x x

Service Rapidly verifies √ x x x

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 8

Figure 3-1 FMA architecture on the MAE

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 9

4.1 Wireless Fault Management

4.1.1 GSM and UMTS Wireless Fault Management

Figure 4-1 shows the troubleshooting process.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 10

Figure 4-1 GSM and UMTS wireless fault management

Figure 4-2 Service verification process after a network reconstruction

4.1.1.1 Fault Overview

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 11

Table 4-1 Fault overview user information

UMTS KPI Trends of the following KPIs:

GSM KPI Trends of the following KPIs:

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 12

KPI trend ● Automatically displays the KPI value corresponding to a point on