100% found this document useful (1 vote)

1K views83 pages

U2000 Trace Server LTE Standard Signaling Northbound File Interface Developer Guide

Uploaded by

sonny winchester

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

100% found this document useful (1 vote)

1K views83 pages

U2000 Trace Server LTE Standard Signaling Northbound File Interface Developer Guide

Uploaded by

sonny winchester

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

You are on page 1/ 83

U2000

V200R018C10
Trace Server LTE Standard Signaling
Northbound File Interface Developer
Guide
Issue 01
Date 2018-02-05

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2018. 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: http://www.huawei.com

Email: [email protected]

Issue 01 (2018-02-05) Huawei Proprietary and Confidential i

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide About This Document

About This Document

Overview
This document provides information about the LTE Standard Signaling Northbound File
Interface of the Trace Server. It also provides guidance for interconnecting with the network
management system (NMS).

When the Trace Server collects NE data, such as, CHR, MR, and trace data, filters the data,
and provides the data for the U2000, upper-layer applications, and NMSs, collection, storage,
and transmission of personal data, such as MSISDNs, IMSIs, IMEIs, and cell IDs are
involved. If the storage directory space or the storage duration reaches specified thresholds,
data will be automatically deleted. NMSs protect personal data in information sent to NMSs.
NE-provided data supports the anonymization capability for sensitive data sources, and the
Trace Server provides the anonymization capability when data is moved out of the live
network. To ensure personal data security, comply with applicable state laws or enterprise
privacy policies and take sufficient measures.Trace Server.

Product Version
This document applies to the following products and versions.

Product Name Product Version

U2000 V200R018C10

Intended Audience
This document is intended for network management engineers.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential ii

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide About This Document

Change History
01 (2018-02-05)
This is the first commercial release for V200R018C10.

Organization
1 Overview of the Result File Interface
This chapter describes the definition of the northbound interface and the result file interface
provided by the Trace Server.
2 Overview of Result Files
This chapter describes the result files for users to easily locate and obtain the files.
3 Managing Northbound Users in RAN Sharing Scenarios
This section describes how to manage northbound users in RAN sharing scenarios. In such
scenarios, multiple operators can share one radio access network (RAN). Northbound files
reported by one NE contain northbound data from different operators. The Trace Server
identifies different operators according to the PLMN in the northbound files and saves
generated northbound result files in different directories. Operators create specified
northbound users to obtain required northbound result files in FTP mode.
4 Process for Interconnecting the Standard Signaling Northbound Result File Interface
This chapter describes the process for interconnecting the NMS with the Trace Server by
using the standard signaling northbound result file interface.
5 Troubleshooting for the Standard Signaling Northbound Result File Interface
The NMS is interconnected with the Trace Server through the standard signaling northbound
result file interface. If problems occur when getting standard signaling data northbound of
NEs on the network, you can solve problems using the methods described in this section.
6 Appendix

Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.

Symbol Description

Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.

Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential iii

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide About This Document

Symbol Description

Indicates a potentially hazardous situation which, if not

avoided, may result in minor or moderate injury.

Indicates a potentially hazardous situation which, if not

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Calls attention to important information, best practices and
tips.
NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.

General Conventions

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in
boldface. For example, log in as user root.
Italic Book titles are in italics.
Courier New Terminal display is in Courier New.

Command Conventions

Convention Description

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by
vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by
vertical bars. One item is selected or no item is selected.
{ x | y | ... } * Optional items are grouped in braces and separated by
vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ] * Optional items are grouped in brackets and separated by
vertical bars. Several items or no item can be selected.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential iv

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide About This Document

GUI Conventions

Convention Description

Boldface Buttons, menus, parameters, tabs, windows, and dialog titles

are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"
signs. For example, choose File > Create > Folder.

Keyboard Operation

Format Description

Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing
Ctrl+Alt+A means the three keys should be pressed
concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.

Mouse Operation

Action Description

Click Select and release the primary mouse button without moving
the pointer.
Double-click Press the primary mouse button twice continuously and
quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential v

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide Contents

Contents

About This Document....................................................................................................................ii

1 Overview of the Result File Interface........................................................................................1
1.1 Definition of the Northbound Interface..........................................................................................................................1
1.2 Definition of the Northbound Trace Result File Interface..............................................................................................2
1.3 Technical Specifications for the Standard Signaling Northbound Result File Interface................................................2

2 Overview of Result Files..............................................................................................................4

2.1 Types of Standard Signaling Northbound Result Files..................................................................................................4
2.2 Save Path of Standard Signaling Northbound Result Files............................................................................................7
2.3 Naming Conventions of Standard Signaling Northbound Result Files..........................................................................9
2.4 Generation Periods of Standard Signaling Northbound Result Files...........................................................................10
2.5 Formats of Standard Signaling Northbound Result Files.............................................................................................10

3 Managing Northbound Users in RAN Sharing Scenarios..................................................16

3.1 Creating Northbound Users..........................................................................................................................................17
3.2 Viewing Northbound Users..........................................................................................................................................19
3.3 Modifying Northbound User Passwords......................................................................................................................20
3.4 Deleting Northbound Users..........................................................................................................................................21
3.5 Deleting Northbound User PLMNs..............................................................................................................................23
3.6 Configuring the Northbound RAN Sharing Function Switch......................................................................................24

4 Process for Interconnecting the Standard Signaling Northbound Result File Interface
............................................................................................................................................................27
4.1 Negotiating Interconnection Parameters for the Standard Signaling Northbound Result File Interface.....................29
4.2 Delivering the standard signaling northbound Event Subscription..............................................................................33
4.2.1 Subscribing to an LTE NE Trace Task......................................................................................................................33
4.2.2 GUIs for LTE Northbound Interface Trace (OSSii)..................................................................................................34
4.2.3 Parameters for Subscribing to an LTE NE Trace Task (OSSii).................................................................................35
4.3 Commissioning the Interconnection of the Standard Signaling Northbound Result File Interface.............................42
4.4 Optional: Setting the Northbound Push FTP Server (Trace Server Co-deployed with the U2000 in the ATAE Cluster
System)...............................................................................................................................................................................43
4.5 Optional: Setting the Northbound Push FTP Server (ATAE Cluster and Virtual Cluster, Standalone).......................44

5 Troubleshooting for the Standard Signaling Northbound Result File Interface...........48

5.1 Troubleshooting and Information Collection...............................................................................................................48

Issue 01 (2018-02-05) Huawei Proprietary and Confidential vi

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide Contents

5.2 Handle the Problem That No Standard Signaling Northbound Result File Is Generated............................................50
5.3 Setting the SFTP Public and Private Key Authentication for the Northbound Push FTP Server.................................50
5.4 How Do I Set the DST?................................................................................................................................................57

6 Appendix.......................................................................................................................................60
6.1 Supported NE types and versions.................................................................................................................................60
6.2 LTE Event List..............................................................................................................................................................63

Issue 01 (2018-02-05) Huawei Proprietary and Confidential vii

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File Overview of the Result File InterfaceOverview of the
Interface Developer Guide Result File Interface

1 Overview of the Result File Interface

About This Chapter

This chapter describes the definition of the northbound interface and the result file interface
provided by the Trace Server.
1.1 Definition of the Northbound Interface
The northbound interface is the interface between the element management system (EMS)
and the NMS.
1.2 Definition of the Northbound Trace Result File Interface
The northbound trace result file interface provided by the Trace Server is a northbound
interface. Through this interface, the NMS obtains northbound trace result files stored on the
Trace Server.
1.3 Technical Specifications for the Standard Signaling Northbound Result File Interface
This section describes the technical specifications for the standard signaling northbound result
file interface.

1.1 Definition of the Northbound Interface

The northbound interface is the interface between the element management system (EMS)
and the NMS.
The NMS obtains NE data, such as NE trace result data, from the EMS and issues commands
over the northbound interface. Figure 1.1 shows the northbound interface.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 1

Figure 1.1 Northbound interface

1.2 Definition of the Northbound Trace Result File

Interface
The northbound trace result file interface provided by the Trace Server is a northbound
interface. Through this interface, the NMS obtains northbound trace result files stored on the
Trace Server.
The Trace Server supports the following protocols for transferring northbound trace result
files:
 File Transfer Protocol (FTP): the common FTP protocol.
 Secure File Transfer Protocol (SFTP): the SSH-based FTP transmission mode.

You are advised to use the SFTP protocols because the SFTP protocols is more secure than the FTP
protocols.

1.3 Technical Specifications for the Standard Signaling

Northbound Result File Interface
This section describes the technical specifications for the standard signaling northbound result
file interface.
Table 1.1 describes the technical specifications for the LTE standard signaling northbound file
interface provided by the Trace Server.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 2

Table 1.1 Technical specifications for the LTE standard signaling northbound file interface
Specification Value

Maximum period during which standard 72

signaling northbound result files are stored
on the Trace Server (unit: hour)
Maximum size of a standard signaling 180
northbound result file that can be saved on a
Trace Server (unit: GB)
Maximum size of a standard signaling 256
northbound result file that can be saved on NOTE
the shared space (unit: GB)  If the size of files saved on the shared space
is less than 256 GB and the storage period
does not expire, trace result files generated by
the Trace Server are not deleted.
 If the size of files saved on the shared space
is greater than 256 GB and the storage period
does not expire, files generated by application
systems (except the Trace Server) and trace
result files generated by the Trace Server are
deleted in sequence before sizes of the files
are less than their respective storage
specifications or the size of files saved on the
share space is less than 256 GB.

Maximum size of a standard signaling 720

northbound result file that can be saved on a
high-specification VM (unit: GB)
Maximum size of a standard signaling 1024
northbound result file that can be saved on NOTE
the shared space of the high-specification  If the size of files saved on the shared space
VM (unit: GB) of the high-specification VM is less than
1024 GB and the storage period does not
expire, trace result files generated by the
Trace Server are not deleted.
 If the size of files saved on the shared space
of the high-specification VM is greater than
1024 GB and the storage period does not
expire, files generated by application systems
(except the Trace Server) and trace result files
generated by the Trace Server are deleted in
sequence before sizes of the files are less than
their respective storage specifications or the
size of files saved on the share space of the
high-specification VM is less than 1024 GB.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 3

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide Overview of Result FilesOverview of Result Files

2 Overview of Result Files

About This Chapter

This chapter describes the result files for users to easily locate and obtain the files.

To obtain result samples, contact Huawei technical support engineers.

2.1 Types of Standard Signaling Northbound Result Files

The Trace Server generates NE northbound result files based on the corresponding NE data.
2.2 Save Path of Standard Signaling Northbound Result Files
After collecting and processing NE data, the Trace Server saves standard signaling
northbound result files in the /export/home/omc/var/fileint/TSNBI/ path of the server where
the NE is located. The Trace Server creates subdirectories in the directory.
2.3 Naming Conventions of Standard Signaling Northbound Result Files
The Trace Server saves NE data as standard signaling northbound result files.
2.4 Generation Periods of Standard Signaling Northbound Result Files
This section describes the generation periods of standard signaling northbound result files.
2.5 Formats of Standard Signaling Northbound Result Files
This section describes the formats of standard signaling northbound result files.

2.1 Types of Standard Signaling Northbound Result Files

The Trace Server generates NE northbound result files based on the corresponding NE data.
The LTE standard signaling complies with the OSSii protocol and 3GPP specifications.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 4

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide Overview of Result FilesOverview of Result Files

Table 1.2 NE software release and 3GPP specifications complies with the relations
NE Software Release 3GPP Interface 3GPP Release

SRAN11.x S1 3GPP TS 36.413 Release 12

X2 3GPP TS 36.423 Release 12
Uu 3GPP TS 36.331 Release 12
SRAN12.x S1 3GPP TS 36.413 Release 13
X2 3GPP TS 36.423 Release 13
Uu 3GPP TS 36.331 Release 13
Pico 12.0 S1 3GPP TS 36.413 Release 12
X2 3GPP TS 36.423 Release 12
Uu 3GPP TS 36.331 Release 12
SRAN13.x S1 3GPP TS 36.413 Release 14
X2 3GPP TS 36.423 Release 14
Uu 3GPP TS 36.331 Release 14
Pico 13.0 S1 3GPP TS 36.413 Release 13
X2 3GPP TS 36.423 Release 13
Uu 3GPP TS 36.331 Release 13

The 3GPP Release version is confirmed by an eNodeB. When reporting a message, the
eNodeB identifies the UE 3GPP Release version and confirms the 3GPP Release version.
Figure 1.2 shows the procedure for the Trace Server to generate a standard signaling
northbound file.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 5

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide Overview of Result FilesOverview of Result Files

Figure 1.2 Procedure for the Trace Server to generate a standard signaling northbound file

The following scenarios indicate the 3GPP Release version used by the NMS and the 3GPP
Release version defining messages reported by an eNodeB.
 The NMS uses 3GPP Release N, and the eNodeB reports messages defined in 3GPP
Release N – X (X ≥ 1).
The 3GPP Release version is compatible with earlier versions. If the NMS uses the
ASN.1 in 3GPP Release N to decode 3GPP Release N – X (X ≥ 1) data, the NMS can
parse all messages and message fields reported by the eNodeB to obtain all required
information. For example, if the eNodeB reports 10 messages with 100 fields, the NMS
obtains all messages and fields.
 The NMS uses 3GPP Release N, and the eNodeB reports messages defined in 3GPP
Release N.
If the NMS uses the ASN.1 in 3GPP Release N to decode 3GPP Release N data,
indicating that the same 3GPP version is used, the NMS can parse all messages and
message fields reported by the eNodeB to obtain all required information. For example,
if the eNodeB reports 10 messages with 100 fields, the NMS obtains all messages and
fields.
 The NMS uses 3GPP Release N, and the eNodeB reports messages defined in 3GPP
Release N + X (X ≥ 1).

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 6

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide Overview of Result FilesOverview of Result Files

If the NMS uses the ASN.1 in 3GPP Release N to decode 3GPP Release N + X (X ≥ 1)
data, indicating that the 3GPP version used by the NMS is earlier than that defining
messages reported by the eNodeB, the NMS cannot obtain messages and fields reported
by the eNodeB in either of the following cases.
− If the eNodeB reports a message added in 3GPP Release N + X, the NMS cannot
parse this message. For example, if the eNodeB reports 10 messages containing one
message added in 3GPP Release N + X and nine messages defined in 3GPP Release
N, the NMS obtains only these 3GPP Release N-defined messages.
− If an eNodeB-reported message is defined in both 3GPP Release N + X and 3GPP
Release N and a field of this message is added in 3GPP Release N + X, the NMS
cannot obtain this field. For example, if the eNodeB reports a message with 100
fields, including 10 fields added in 3GPP Release N + X and 90 fields defined in
3GPP Release N, the NMS obtains only these 3GPP Release N-defined fields.
The preceding scenarios are described in ASN.1 design specifications. Figure 1.3 displays
ASN encoding and decoding rules for different versions and systems.

Figure 1.3 ASN.1 encoding and decoding rules for different systems

Compared with the eNodeB-dedicated 3GPP Release version, the UE-dedicated 3GPP Release version is
updated slowly. You are advised to configure the latest eNodeB-dedicated 3GPP Release version in the
ASN.1 decoder of the NMS.

2.2 Save Path of Standard Signaling Northbound Result

Files
After collecting and processing NE data, the Trace Server saves standard signaling
northbound result files in the /export/home/omc/var/fileint/TSNBI/ path of the server where
the NE is located. The Trace Server creates subdirectories in the directory.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 7

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide Overview of Result FilesOverview of Result Files

The rule for creating subdirectories is as follows:

LTE_CELL_TRC/yyyymmdd/NE identifier/ and LTE_SIG/yyyymmdd/NE identifier/.
 yyyymmdd indicates the date when a standard signaling northbound result file is
generated.

 NE identifiers include NEFDN and neName. The FDN is a unique attribute of the NEs, and the
value range is 256 to 2945727. The neName is user-defined and unique in the same EMS.
 The IP address of the server where the NE resides can be queried through the Maintenance > Trace
Server Maintenance > Query Subscription Information function of the U2000 client. For details
about operations in the Query Subscription Information window, press F1 in the window to view
the help information.
 The configuration item can be modified on the U2000 client. For details, see Modifying
Configuration Items in 4.1Negotiating Interconnection Parameters for the Standard Signaling
Northbound Result File Interface.
 After the configuration item is modified or the NE is renamed, historical data will not be modified to
prevent the NMS from collecting data repeatedly.
 When the configuration item is modified to neName as the output directory, neName can not name
as ...
 The dataList subdirectory in the /export/home/omc/var/fileint/TSNBI/LTE_CELL_TRC or
LTE_SIG/ directory stores the index files whose names start with Datalist. These index files help the
FTP server quickly send the standard signaling northbound result files from the Trace Server to the
NMS.

For example:
 When NE identifier is NEFDN, if a result file is generated on May 11, 2014, the
directory is automatically created for saving result files that were generated on May 11,
2014. For details , see Table 3.1.

Table 3.1 The directory for saving standard signaling result file
Event Name Result File Name Saving Directory

UE Period TA LTE_SIG /
UE Period TA MDT export/home/omc/var/filein
t/TSNBI/LTE_SIG/201405
11/NEFDN/
S1 interface event LTE_CELL_TRC /
X2 interface event export/home/omc/var/filein
t/TSNBI/LTE_CELL_TRC/
UU interface event 20140511/NEFDN/

 When NE identifier is neName, if a result file is generated on May 11, 2014, the
directory is automatically created for saving result files that were generated on May 11,
2014. For details , see Table 3.2.

Table 3.2 The directory for saving standard signaling result file
Event Name Result File Name Saving Directory

UE Period TA LTE_SIG /
UE Period TA MDT export/home/omc/var/filein
t/TSNBI/LTE_SIG/201405

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 8

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide Overview of Result FilesOverview of Result Files

Event Name Result File Name Saving Directory

11/neName/
S1 interface event LTE_CELL_TRC /
X2 interface event export/home/omc/var/filein
t/TSNBI/LTE_CELL_TRC/
UU interface event 20140511/neName/

2.3 Naming Conventions of Standard Signaling

Northbound Result Files
The Trace Server saves NE data as standard signaling northbound result files.
the naming conventions are as follows:
 When the NE identifier is NEFDN,
naming conventions for an LTE_CELL_TRC or LTE_SIG result files are
<NEFDN>_<StartTime>_<EndTime>_<SN>.<FilePostfix>.gz.
 When the NE identifier is neName,
naming conventions for an LTE_CELL_TRC or LTE_SIG result file are
<neName>_<StartTime>_<EndTime>_<SN>.<FilePostfix>.gz.

Table 3.3 Parameter of naming conventions

Parameter Description

NEFDN or neName NE identifiers include NEFDN and neName. You can be

modified on the U2000 client. For details, see Modifying
Configuration Items in 4.1Negotiating Interconnection
Parameters for the Standard Signaling Northbound Result File
Interface.
StartTime Start time in the name of an NE-reported file. The format is
YYYYMMDDhhmmssDST, where YYYY indicates the year,
MM indicates the month, DD indicates the day, hh indicates
the hour, mm indicates the minute, and ss indicates the second.
DST is optional, depending on whether the NE is in daylight
saving time (DST) mode.
EndTime End time in the name of an NE-reported file. The format is
YYYYMMDDhhmmssDST, where YYYY indicates the year,
MM indicates the month, DD indicates the day, hh indicates
the hour, mm indicates the minute, and ss indicates the second.
DST is optional, depending on whether the NE is in daylight
saving time (DST) mode.
SN Generated series number of the file. Value range: 0000 to
9999. The serial number ranges from 0000 to 9999 cyclically.
FilePostfix File name extension.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 9

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide Overview of Result FilesOverview of Result Files

Parameter Description
 The extension is sig for LTE_CELL_TRC result files.
 The extension is log for LTE_SIG result files.

If another NE uploads no files or no NEs upload files for a long time, the end time increases by one file
generation period in the name of the last NE-reported file.

For example:
 When the NE identifier is NEFDN, the SN is 1234, the start time in an NE-reported file
is 2014-05-11 17:30:30, the end time in the NE-reported file is 2014-05-11 17:32:40, the
name of the generated LTE_CELL_TRC result file is
NEFDN_20140511173030_20140511173240_1234.sig.gz, the name of the generated
LTE_SIG result file is NEFDN_20140511173030_20140511173240_1234.log.gz.
 When the NE identifier is neName, the SN is 1234, the start time in an NE-reported file
is 2014-05-11 17:30:30, the end time in the NE-reported file is 2014-05-11 17:32:40, the
name of the generated LTE_CELL_TRC result file is
neName_20140511173030_20140511173240_1234.sig.gz, the name of the generated
LTE_SIG result file is neName_20140511173030_20140511173240_1234.log.gz.

2.4 Generation Periods of Standard Signaling Northbound

Result Files
This section describes the generation periods of standard signaling northbound result files.
When the volume or generation period of northbound analysis result LTE_CELL_TRC or
LTE_SIG is greater than those specified in 4.1Negotiating Interconnection Parameters for the
Standard Signaling Northbound Result File Interface, northbound analysis result files are
generated. The default generated file size and generation period are 10 MB and 5 minutes,
respectively.

 If the NE does not report the new data file for at least 30 minutes or the Trace Server service stops,
NE northbound result files are also generated.
 If the NE identifier has been modified, NE northbound result files are also generated.

2.5 Formats of Standard Signaling Northbound Result

Files
This section describes the formats of standard signaling northbound result files.
An LTE standard signaling northbound result file consists of a file header and a file body, as
shown in Figure 1.4. The file header provides the file information. The file body consists of
all events reported from the NE. Each event consists of an event header and the event content.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 10

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide Overview of Result FilesOverview of Result Files

Figure 1.4 Format of an LTE standard signaling northbound result file

Format of an LTE Standard Signaling Northbound Result File Header

Table 1.1 Format of an LTE standard signaling northbound result file header
Field Data Type and Length Description

Data Version N/A File format version

information
>Main Version UINT8 Main version
>Sub Version UINT8 Sub version
Spare OCTET STRING (30) Spare

 If the > symbol is displayed before a field, the field is a sub-field. For example, if the seven fields A,
>B, >C, >>D, >>E, >F, and G are available in the file in sequence, fields B, C, and F are the sub-
fields of field A, and fields D and E are the sub-fields of sub-field C.
 The invalid byte is filled with FF and the invalid bit is filled with 0 in the fields.

Format of an LTE Standard Signaling Northbound Event Header

Table 1.1 Format of an LTE standard signaling northbound event header

Data Type and
Field Description Introduced In
Length

SRAN11.1
Event ID UINT16 Event identifier
Pico11.1
Event length,
excluding lengths of SRAN11.1
Event Length UINT32
Event ID and Event Pico11.1
Length

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 11

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide Overview of Result FilesOverview of Result Files

Data Type and

Field Description Introduced In
Length

SRAN11.1
eNodeB ID UINT32 eNodeB identifier
Pico11.1
Cell identifier
Invalid value: all Fs
For example, the SRAN11.1
Cell ID UINT8 value of this field is Pico11.1
invalid for base
station events or cell
events.
Call identifier
Invalid value: all Fs
SRAN11.1
Call ID UINT32 For example, the
value of this field is Pico11.1
invalid for base
station events.
Time when an event
SRAN11.1
Date Time N/A is triggered
Pico11.1
UTC time
Year
Difference between SRAN11.1
>Year UINT8
the current year and Pico11.1
the year 2000
Month SRAN11.1
>Month UINT8
Value range: 1 to 12 Pico11.1
Day SRAN11.1
>Day UINT8
Value range: 1 to 31 Pico11.1
Hour SRAN11.1
>Hour UINT8
Value range: 0 to 23 Pico11.1
Minute SRAN11.1
>Minute UINT8
Value range: 0 to 59 Pico11.1
Second SRAN11.1
>Second UINT8
Value range: 0 to 59 Pico11.1
Millisecond
Value range: 0 to
999 SRAN11.1
>Millisecond UINT16
The value is 0 for Pico11.1
events accurate to
seconds.
Extend Head Length UINT8 Extension header N/A

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 12

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide Overview of Result FilesOverview of Result Files

Data Type and

Field Description Introduced In
Length

length
Event type
 0000: undefine
 0001: FDD
Item Type BIT STRING (4) SRAN13.1
 0010: TDD
 0101: NB-IoT
 1111: Common
Reserved BIT STRING (4) Reserved bit N/A
C-RNTI
Invalid value: all Fs
For example, the SRAN11.1
C-RNTI UINT16 value of this field is Pico 12.0
invalid for base
station events or cell
events.

System capacity: When the independent MDT function is enabled, reporting measurement
data consumes certain Uu interface resources, causing the CPU usage to increase by up to 5%.
Network performance:
 Enabling the independent MDT function may cause a conflict between intra-
frequency/inter-frequency measurement and handover measurement, causing the access
and handover success rates to decrease by up to 0.5%.
 Inter-frequency measurement causes UEs to enter the GAP state, and some subframes
cannot be adjusted as a result, slightly decreasing the average cell throughput.
If NE-reported data contains the incorrect year, month, and day, the year, month, and day are
0-1-1 in the northbound analysis result. If NE-reported data contains the incorrect hour,
minute, and second, the hour, minute, and second are 23-59-59 in the northbound analysis
result. You are advised to prevent data analysis problems caused by data errors.

Formats of LTE Standard Signaling Event Content

Table 1.1 Format of the LTE standard signaling event content

Data Type and
Field Description Introduced In
Length

Message Direction UINT8 Message direction SRAN11.1

0: receiving Pico11.1
1: sending

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 13

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide Overview of Result FilesOverview of Result Files

Data Type and

Field Description Introduced In
Length

Invalid value: all Fs

SRAN11.1
Message Length UINT32 Message length
Pico11.1
Message content
If there is a Uu
interface message,
the first byte
indicates the type of
the logical channel
where the message
is sent.
Value range:
OCTET STRING  1: DL DCCH SRAN11.1
Message Content
(Message Length) Pico11.1
 2: UL DCCH
 3: DL CCCH
 4: UL CCCH
 18: MCCH
 36: DL DCCH NB
 37: UL DCCH NB
 38: DL CCCH NB
 39: UL CCCH NB

For security purpose, message fields that involve subscriber privacy are anonymized.

Table 1.2 Format of the UE Period TA (0x1211) event content

Data Type and
Field Description Introduced In
Length

TA value
Value range: 0 to
20512
SRAN11.1
TA Value UINT32 Unit: Ts
Pico11.1
See 3GPP TS 36.133
Timing Advance
(TADV): Type 2.

Date Time in the header of an event of this type is accurate to seconds.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 14

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide Overview of Result FilesOverview of Result Files

Table 1.3 Format of the UE Period TA MDT (0x1212) event content

Data Type and
Field Description Introduced In
Length

TA value
Value range: 0 to
20512
TA Value UINT32 Unit: Ts SRAN11.1
See 3GPP TS 36.133
Timing Advance
(TADV): Type 2.

Date Time in the header of an event of this type is accurate to seconds.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 15

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File Managing Northbound Users in RAN Sharing Scenarios
Interface Developer Guide Managing Northbound Users in RAN Sharing Scenarios

3 Managing Northbound Users in RAN

Sharing Scenarios

About This Chapter

This section describes how to manage northbound users in RAN sharing scenarios. In such
scenarios, multiple operators can share one radio access network (RAN). Northbound files
reported by one NE contain northbound data from different operators. The Trace Server
identifies different operators according to the PLMN in the northbound files and saves
generated northbound result files in different directories. Operators create specified
northbound users to obtain required northbound result files in FTP mode.
3.1 Creating Northbound Users
This section describes how to create specified northbound users using the northbound user
configuration tool, helping operators obtain required northbound result files.
3.2 Viewing Northbound Users
This section describes how to view created northbound users, their permissions, and PLMNs
using the northbound user configuration tool.
3.3 Modifying Northbound User Passwords
This section describes how to modify the password of a created northbound user using the
northbound user configuration tool. To improve data security, properly keep the password of
the northbound user and change it periodically.
3.4 Deleting Northbound Users
This section describes how to delete northbound users who are not used any more using the
northbound user configuration tool.
3.5 Deleting Northbound User PLMNs
This section describes how to delete northbound user PLMNs using the northbound user
configuration tool.
3.6 Configuring the Northbound RAN Sharing Function Switch

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 16

This section describes how to configure the RAN function control item on the Trace Server
over the GSM, UMTS, or LTE northbound file interfaces using the northbound user
configuration tool. By default, the RAN sharing function is disabled.

3.1 Creating Northbound Users

This section describes how to create specified northbound users using the northbound user
configuration tool, helping operators obtain required northbound result files.

Prerequisites
You have obtained passwords of users ossuser and root on the U2000 server (Trace Server
co-deployed with the U2000 in the ATAE cluster system) or on the Trace Server (Trace Server
independently deployed in an ATAE cluster system).

Context
To improve security of users' passwords, set passwords based on the following rules:
 A password must contain 8 to 30 characters.
 A password must contain at least one uppercase letter.
 A password must contain at least one lowercase letter.
 A password must contain at least one digit.
 A password must contain at least one special character @%-=_.]{}
 A password must not be the same as the user name or the reverse order of the user name.
 A password cannot contain three or more consecutive characters that are the same (for
example, AAA and 111).
 The number of neighboring digits or letters is limited to four pairs
For example, the password Changeme_121212 does not meet this complexity
requirement because 121212 has a total of five pairs of digits (12 is a pair, 21 is another
pair, and so on).
 A password must not contain any spaces.
 A password must not be one of the 12 passwords that are recently used.

Step 3 Run the following commands to run the RAN sharing northbound user configuration tool:
 For the Trace Server independently deployed, run the following command.
# cd /opt/oss/server/rancn/bin

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 17

 For the Trace Server co-deployed with the U2000 in the ATAE cluster system, run the
following command.
# cd /opt/oss/server/rancn/tools/TSTools
# sh setRANSharingUser.sh
Step 4 When the following information is displayed, enter B or b and press Enter:
Please select an operation type.
A--Show the northbound user list.
B--Create a northbound user.
C--Reconfigure the password of northbound user.
D--Delete a northbound user or a single PLMN.
E--Set the GUL switch.
Q--Exit
Please select:

Step 5 When the following information is displayed, enter the northbound user name and press
Enter:
Please enter your user name.

Step 6 When the following information is displayed, enter the PLMN of the northbound user and
press Enter:
Please enter your PLMN number.

Step 7 When the following information is displayed, choose Yy or Nn to determine whether

northbound users need to access the public data and press Enter:
Are you sure you want to view common data? [Yy/Nn]:[default=Y]

Step 8 When the following information is displayed, enter the password of the northbound user and
press Enter. You need to enter the new password twice.
New Password: password of northbound user
Reenter New Password: password of northbound user

Step 9 If the following information is displayed, the RAN sharing northbound user has been created
successfully. Otherwise, contact Huawei technical support.
User Northbound user name created successfully.

----End

Follow-up Procedures
 If the PLMN needs to be separately added for created northbound users, repeat the
operations from Step 1 to Step 7 and enter the PLMN to be added in Step 6. When the
following information is displayed, the PLMN has been added successfully. Otherwise,
contact Huawei technical support.
The northbound user already exists.
User northbound user name created successfully.

 If access permissions of created northbound users on public data need to be changed,

perform the operations from Step 1 to Step 7. Reconfigure the access permissions for
northbound users in Step 7. When the following information is displayed, the

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 18

permissions have been changed successfully. Otherwise, contact Huawei technical

support.
The northbound user already exists.
User northbound user name created successfully.

After the access permissions of northbound users on public data are changed, you must log in to the
Trace Server again to make the change take effect.

3.2 Viewing Northbound Users

This section describes how to view created northbound users, their permissions, and PLMNs
using the northbound user configuration tool.

Step 3 Run the following commands to run the RAN sharing northbound user configuration tool:
 For the Trace Server independently deployed, run the following command.
# cd /opt/oss/server/rancn/bin
 For the Trace Server co-deployed with the U2000 in the ATAE cluster system, run the
following command.
# cd /opt/oss/server/rancn/tools/TSTools
# sh setRANSharingUser.sh
Step 4 When the following information is displayed, enter A or a and press Enter to view the created
RAN sharing northbound users:
Please select an operation type.
A--Show the northbound user list.
B--Create a northbound user.
C--Reconfigure the password of northbound user.
D--Delete a northbound user or a single PLMN.
E--Set the GUL switch.
Q--Exit
Please select:

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 19

Step 5 When information similar to the following is displayed, you can view created northbound
users, their permissions to access public data, and PLMNs of all users:
-----------------------------------------------
Username CommonData PLMN
user1 Y 1111,22222,333333
user2 Y 44444
user3 N 555555
-----------------------------------------------

----End

3.3 Modifying Northbound User Passwords

This section describes how to modify the password of a created northbound user using the
northbound user configuration tool. To improve data security, properly keep the password of
the northbound user and change it periodically.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 20

~> su - root
Password:Password of root

Step 3 Run the following commands to run the RAN sharing northbound user configuration tool:
 For the Trace Server independently deployed, run the following command.
# cd /opt/oss/server/rancn/bin
 For the Trace Server co-deployed with the U2000 in the ATAE cluster system, run the
following command.
# cd /opt/oss/server/rancn/tools/TSTools
# sh setRANSharingUser.sh
Step 4 When the following information is displayed, enter C or c and press Enter:
Please select an operation type.
A--Show the northbound user list.
B--Create a northbound user.
C--Reconfigure the password of northbound user.
D--Delete a northbound user or a single PLMN.
E--Set the GUL switch.
Q--Exit
Please select:

Step 5 When the following information is displayed, enter the northbound user name to be modified
and press Enter:
Please enter the user name.

Step 6 When the following information is displayed, enter the new password of the northbound user
and press Enter. You need to enter the new password twice.
Changing password for Northbound user name.
New Password: password of northbound user
Reenter New Password: password of northbound user

Step 7 If the following information is displayed, the password of the northbound user has been
modified successfully. Otherwise, contact Huawei technical support engineers.
Password changed.

----End

3.4 Deleting Northbound Users

This section describes how to delete northbound users who are not used any more using the
northbound user configuration tool.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 21

Step 3 Run the following commands to run the RAN sharing northbound user configuration tool:
 For the Trace Server independently deployed, run the following command.
# cd /opt/oss/server/rancn/bin
 For the Trace Server co-deployed with the U2000 in the ATAE cluster system, run the
following command.
# cd /opt/oss/server/rancn/tools/TSTools
# sh setRANSharingUser.sh
Step 4 When the following information is displayed, enter D or d and press Enter:
Please select an operation type.
A--Show the northbound user list.
B--Create a northbound user.
C--Reconfigure the password of northbound user.
D--Delete a northbound user or a single PLMN.
E--Set the GUL switch.
Q--Exit
Please select:

Step 5 When the following information is displayed, enter B or b and press Enter:
Please select an operation type.
A--Delete a single PLMN under a user.
B--Delete a northbound user.
Q--Exit
Please select:

Step 6 When the following information is displayed, enter the northbound user name to be deleted,
user1 for example, and press Enter:
Please enter the user name to delete:
user1

Step 7 When the following information is displayed, enter Y or y and press Enter:
User user1 has the following PLMNs:
1111 22222 333333
Are you sure you want to delete all PLMNs under user user1? [Yy/Nn]
The operation will delete all NBI result files under the PLMN.
The operation will take a few minutes.
Please select:

Step 8 If the following information is displayed, the northbound user user1 has been deleted
successfully. Otherwise, contact Huawei technical support engineers.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 22

User user1 deleted successfully.

----End

3.5 Deleting Northbound User PLMNs

This section describes how to delete northbound user PLMNs using the northbound user
configuration tool.

Step 3 Run the following commands to run the RAN sharing northbound user configuration tool:
 For the Trace Server independently deployed, run the following command.
# cd /opt/oss/server/rancn/bin
 For the Trace Server co-deployed with the U2000 in the ATAE cluster system, run the
following command.
# cd /opt/oss/server/rancn/tools/TSTools
# sh setRANSharingUser.sh
Step 4 When the following information is displayed, enter D or d and press Enter:
Please select an operation type.
A--Show the northbound user list.
B--Create a northbound user.
C--Reconfigure the password of northbound user.
D--Delete a northbound user or a single PLMN.
E--Set the GUL switch.
Q--Exit
Please select:

Step 5 When the following information is displayed, enter A or a and press Enter:
Please select an operation type.
A--Delete a single PLMN under a user.
B--Delete a northbound user.
Q--Exit
Please select:

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 23

Step 6 When the following information is displayed, enter the northbound user name to be deleted
that the PLMN belongs to, user1 for example, and press Enter:
Please enter the user name to delete:
user1

Step 7 When the following information is displayed, enter the PLMN to be deleted, 1111 for
example, and press Enter:
User user1 has the following PLMNs:
1111 22222 333333
Please enter the PLMN:
1111

Step 8 When the following information is displayed, enter Y or y and press Enter:
Are you sure you want to delete a single PLMN? [Yy/Nn]
The operation will delete all NBI result files under the PLMN.
The operation will take a few minutes.
Please select:

Step 9 If the following information is displayed, the value 1111 of the PLMN for northbound user
user1 has been deleted successfully. Otherwise, contact Huawei technical support.
Single PLMN under user user1 deleted successfully.

----End

3.6 Configuring the Northbound RAN Sharing Function

Switch
This section describes how to configure the RAN function control item on the Trace Server
over the GSM, UMTS, or LTE northbound file interfaces using the northbound user
configuration tool. By default, the RAN sharing function is disabled.

Context
After the RAN sharing function is enabled, the Trace Server saves northbound analysis result
files in the /export/home/sysm/export/home/omc/var/fileint/TSNBI/shared/ directory and
creates subdirectories under this directory.
 If PLMN values are not all Fs, the subdirectory naming conventions are PLMN
value/Result File Name/yyyymmdd/NE identifier/.
 If PLMN values are all Fs, the subdirectory naming conventions are
commonData/Result File Name/yyyymmdd/NE identifier/.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 24

Step 3 Run the following commands to run the RAN sharing northbound user configuration tool:
 For the Trace Server independently deployed, run the following command.
# cd /opt/oss/server/rancn/bin
 For the Trace Server co-deployed with the U2000 in the ATAE cluster system, run the
following command.
# cd /opt/oss/server/rancn/tools/TSTools
# sh setRANSharingUser.sh
Step 4 When the following information is displayed, enter E or e and press Enter:
Please select an operation type.
A--Show the northbound user list.
B--Create a northbound user.
C--Reconfigure the password of northbound user.
D--Delete a northbound user or a single PLMN.
E--Set the GUL switch.
Q--Exit
Please select:

Step 5 When the following information is displayed, enter C or c and press Enter (enabling the LTE
RAN sharing function is used as an example here):
-----------RAN Sharing Switch Status-----------
A.GSM-------off
B.UMTS------off
C.LTE-------off
-----------------------------------------------
Please select an operation type.
A--Set the GSM switch status.
B--Set the UMTS switch status.
C--Set the LTE switch status.
Q--Exit
Please select:

Step 6 When the following information is displayed, enter ON or on and press Enter (enabling the
LTE RAN sharing function is used as an example here):
Are you sure you want to set the status of the LTE switch? [ON/OFF]

Step 7 If the following information is displayed, the LTE RAN sharing function has been enabled
successfully. Otherwise, contact Huawei technical support.
LTE switch set successfully.
-----------RAN Sharing Switch Status-----------
A.GSM-------off

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 25

B.UMTS------off
C.LTE-------on
-----------------------------------------------
Please select an operation type.
A--Set the GSM switch status.
B--Set the UMTS switch status.
C--Set the LTE switch status.
Q--Exit
Please select:

Step 8 Type Q and press Enter. Return to the RAN sharing northbound user configuration tool main
interface.
Step 9 Type Q and press Enter. Exit the RAN sharing northbound user configuration tool.
Step 10 Run the following commands to restart the Trace Server services.
# exit
~> . /opt/oss/server/svc_profile.sh
 For the Trace Server independently deployed, run the following command.
~> stop_svc
If the command output contains Finished stopping the service., Trace Server services
have been stopped successfully.
~> start_svc
If the command output contains Finished starting the system., the Trace Server service
has been started successfully.
 For the Trace Server co-deployed with the U2000 in the ATAE cluster system, run the
following command.
~> svc_deploy -cmd querysvc | awk '{print $2}' | grep 'TSCollector' | xargs -L1
svc_adm -cmd restartsvc
Step 11 Run the following commands to verify that the Trace Server services are restarted
successfully:
~> svc_adm -cmd status -sysagent all | grep TSCollector | grep "not running"
When there is no information displayed, the Trace Server services are restarted successfully.
----End

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 26

Copyright © Huawei
Technologies Co., Ltd.
Process for Interconnecting the Standard Signaling
U2000 Northbound Result File InterfaceProcess for
Trace Server LTE Standard Signaling Northbound File Interconnecting the Standard Signaling Northbound
Interface Developer Guide Result File Interface

4 Process for Interconnecting the Standard

Signaling Northbound Result File Interface

About This Chapter

This chapter describes the process for interconnecting the NMS with the Trace Server by
using the standard signaling northbound result file interface.
Figure 11.1 lists the process for interconnecting the standard signaling northbound result file
interface.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 27

Figure 11.1 Flow chart of process for interconnecting the standard signaling northbound result file
interface

4.1 Negotiating Interconnection Parameters for the Standard Signaling Northbound Result
File Interface
This section describes the preparations for interconnecting the Trace Server with the NMS.
4.2 Delivering the standard signaling northbound Event Subscription
Before configuring the standard signaling northbound interface, you need to start an event
subscription task. NEs upload the data to the Trace Server and the Trace Server automatically
generates a northbound result file.
4.3 Commissioning the Interconnection of the Standard Signaling Northbound Result File
Interface
The NMS obtains standard signaling northbound result files generated by the Trace Server by
using FTP or SFTP. Based on the files, you can determine whether the standard signaling
northbound result interface meets the requirements for interconnecting with the NMS.
4.4 Optional: Setting the Northbound Push FTP Server (Trace Server Co-deployed with the
U2000 in the ATAE Cluster System)
Before commissioning the XFTP northbound file push function, you need to set an FTP server
to receive data. After the FTP server is set successfully, the Trace Server will scan the
northbound files every 5 minutes and push the scanned files to the specified FTP server.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 28

4.5 Optional: Setting the Northbound Push FTP Server (ATAE Cluster and Virtual Cluster,
Standalone)
Before commissioning the XFTP northbound file push function, you need to set an FTP server
to receive data. After the FTP server is set successfully, the Trace Server will scan the
northbound files every 5 minutes and push the scanned files to the specified FTP server.

4.1 Negotiating Interconnection Parameters for the

Standard Signaling Northbound Result File Interface
This section describes the preparations for interconnecting the Trace Server with the NMS.

Checking the License

Perform the following steps to check whether the U2000 is licensed to use the trace result file
interface:
1. Log in to the M2000 client.
2. Choose License > OSS License Management > License Information (traditional
style). Alternatively, double-click System Management in Application Center and
choose License Management > License Information (application style). The License
Information window is displayed.
3. Click the Resource Control Item tab. If Resource contains the Standard trace data
interface - LTE FDD/TDD item, click the Function Control Item tab. If Function
contains the Trace data BIN file interface item, the standard signaling northbound
result file interface is available. If there is no license, the standard signaling northbound
result file interface is unavailable. If you need to use this function, contact Huawei
technical support engineers.

Negotiated Interconnection Parameters

Table 1.1 describes the parameters.

Table 1.1 Negotiated interconnection parameters

FTP Parameter Parameter Description

(Recommended) If FTP user name Value: ftpuser or the northbound user in

the Trace Server RAN sharing scenery.
serves as an FTP
server, the NMS Password For details about how to obtain the
obtains files from password, contact the Trace Server
the Trace Server. administrator.
FTP port Value: 21
If you use FTP to transfer files, open the
port on the Trace Server.
SFTP port Value: 22
If you use SFTP to transfer files, open the
port on the Trace Server.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 29

FTP Parameter Parameter Description

Path for saving files After collecting and processing NE-reported

data, the Trace Server saves northbound
analysis result files on the server managing
NEs.
 If RAN sharing is enabled, the Trace
Server saves northbound analysis result
files in the
/export/home/omc/var/fileint/TSNBI/s
hared/ directory and creates
subdirectories.
 If RAN sharing is disabled, the Trace
Server saves northbound analysis result
files in the
/export/home/omc/var/fileint/TSNBI/
directory and creates subdirectories.
If the Trace Server FTP user name Provided by the NMS.
serves as an FTP
client, it Password Provided by the NMS.
automatically
FTP port Value: 21
uploads files to the
NMS. If you use FTP to transfer files, open the
port on the NMS.
SFTP port Value: 22
If you use SFTP to transfer files, open the
port on the NMS.
Path for saving files Provided by the NMS.
Trace Server uploads trace result files to this
path of NMS.

Modifying Configuration Items

Prerequisites
 The U2000 has loaded the licenses related to northbound trace.
 You have logged in to the U2000 client.
Procedure
1. Choose Maintenance > Trace Server Maintenance > Trace Server Parameter
Settings (traditional style) or double click Trace and Maintenance in Application
Center and choose Trace Server Maintenance > Trace Server Parameter Settings
(application style).
2. In the navigation tree, choose the LTE Common Trace Server NBI item to set.
3. Select OSSii in the Signaling Format area box.
4. In the navigation tree, choose the OSSii item to set.
5. Set related parameters in the right area box by referring to Table 1.1 and Table 1.2.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 30

Table 1.1 OSSii parameter settings

Area Box Name Parameter Name Parameter Description

OSSii parameter settings Storage duration Storage duration of the NBI

result file directory on the
server
Value range: 1 to 72 (hour)
Default value: 72
NE identifier NBI result file naming
convention, which can be set
by selecting the NE
identifier
Values: NE Name and NE
FDN
Default value: NE FDN
Generated file size Minimum size of generated
NBI result files
Values: 1, 5, 10, 15, and 30
(MB)
Default value: 10
File generation period Generation period of NBI
result files
Values: 1, 5, and 10 (minute)
Default value: 5
MDT Extended Field This control item is enabled
Display Switch or disabled to report new
parameters or not during
subscription to events with
new parameters.
Default value: Off
If this control item is
enabled, the version number
in file headers is changed to
2.0.
NOTICE
Before enabling this control
item, ensure that the NMS has
updated the data paring tool.
Otherwise, the NMS cannot
parse events with new
parameters.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 31

Area Box Name Parameter Name Parameter Description

Subscription time offset Start subscription time NBI subscription allows you
setting to issue subscription
commands at a time earlier
than the predefined
subscription start time to
ensure integrity of NBI
result data, considering the
subscription issuing
duration.
Values: 0, 5, 10, and 15
(minute)
Default value: 10
Stop subscription time NBI subscription allows you
to stop subscription at a time
later than the predefined
subscription end time to
ensure integrity of NBI
result data, considering
delays in southbound data
reporting and northbound
data processing.
Values: 0, 5, 10, and 15
(minute)
Default value: 15

Table 1.2 Compression parameter settings

Navigation Tree Area Box Name Parameter Name Parameter
Description

LTE Data Compression Data compression  No compression:

Compression Switch Parameter Setting switch After No
NOTICE compression is
This function applies selected, data that
only to LTE NEs the Trace Server
whose version is subscribes to is
eRAN13.0 or later transmitted
and whose MPT type without being
is not LMPT.
compressed.
 Compression:
After
Compression is
selected, data that
the Trace Server
subscribes to is
transmitted with
being
compressed.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 32

6. If other Trace Server parameters need to be set, click Apply and set these parameters. If
the parameter setting is complete, click OK.
7. Re-log in to U2000 client.

4.2 Delivering the standard signaling northbound Event

Subscription
Before configuring the standard signaling northbound interface, you need to start an event
subscription task. NEs upload the data to the Trace Server and the Trace Server automatically
generates a northbound result file.

4.2.1 Subscribing to an LTE NE Trace Task

This section describes how to subscribe to an LTE NE trace task. You can subscribe to an NE
trace task to obtain the trace files that the Trace Server northbound interface has analyzed
from a specified directory on the U2000 for northbound interconnection.

Prerequisites
 You have purchased the license for LTE cell trace.
 You have installed the mediations of LTE NEs and NEs are accessed to U2000
successfully.
 You must have the operation permission for Trace Server NBI.

Context
 After the NE version is upgraded, do not resubscribe to the messages that have been
subscribed to on the U2000 client.

Procedure
Step 1 Choose Monitor > Trace Server NBI > LTE Common Trace Server NBI (traditional style);
alternatively, double-click Trace and Maintenance in Application Center and choose Trace
Server NBI > LTE Common Trace Server NBI (application style).The LTE Common
Trace Server NBI window is displayed.
Step 2 In the NE navigation tree, choose an NE type, an NE version, and NE information.
NE Name, Subscribed Status, Start Time, End Time, Collection State, Collection Time,
and Operation Result are displayed on the right pane.
Step 3 In the right pane, select an NE to which subscription is to be issued, right-click the NE, and
choose Subscribe from the shortcut menu.
Step 4 In the Message Settings area, select the message contents that you want to subscribe to.
The Message Settings area displays the message contents supported by the NE, the message
contents that you have subscribed to, and subscribe to a failed message.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 33

 If many message contents are available, enter the message keywords in the Find Message text box
and click Previous or Next to search for the required message contents.
 To subscribe to all message contents or cancel the subscription of all message contents, you can
right-click in the message list in the Message Settings area and choose Select All or Clear All from
the shortcut menu to quickly subscribe to or cancel the subscription of all message contents.
 For message contents to be subscribed to, right-click the message setting list of the Message
Settings area and choose Export or Import from the shortcut menu to export configured message
contents from existing message configurations or import configured message contents to existing
message configurations.

Step 5 In the displayed dialog box, set required subscription parameters in Time Parameter
Settings, Cell Parameter Settings, Periodic Messages Parameters Settings, and MDT
Parameters Settings areas.

Collection time in the Time Parameter Settings area is used to control the time segment for data
reporting. After this parameter is set to a time segment, the Trace Server processes and reports data
collected within the time segment. For example, if the subscription start time is 2016–07–22 10:05, the
subscription end time is 2016–07–23 10:05, and Collection time is set to 11:00 to 12:00, the Trace
Server processes and reports data collected from 2016–07–22 11:00:00 to 2016–07–22 11:59:59. If
Collection time is not set to a specific value (Collection time is deselected), the Trace Server processes
and reports data collected from the subscription start time to the subscription end time.

Step 6 Click Apply.

The subscription task is started, and NE subscription information is displayed in the right
pane.
After the subscription is successful, The Trace Server northbound interface analyzes the
original data reported by NEs and generates files. For details, see U2000 Trace Server
Northbound Interface Developer Guide . You can contact Huawei technical support to obtain
these documents.
----End

4.2.2 GUIs for LTE Northbound Interface Trace (OSSii)

This section describes the function of each component on the LTE Trace Server NBI page.
Figure 6.1 shows the LTE Trace Server NBI page. Table 1.1 describes the page shown in
Figure 6.1.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 34

Figure 6.1 Main page of LTE Trace Server NBI

Table 1.1 Main page of LTE Trace Server NBI

No. Name Description

1 Auto Provides the automatic subscription function for new

subscribe NEs.
After selecting Auto subscribe new NEs, you need to set
Time Parameter Settings, Cell Parameter Settings,
Periodic Messages Parameters Settings, or MDT
Parameters Settings as required. In this way,
preconfigured subscription tasks are automatically issued
to new NEs. For details about subscription parameters,
see 4.2.3Parameters for Subscribing to an LTE NE Trace
Task (OSSii).
2 NE By default, the NE navigation tree is displayed by
navigation network topology.
tree
3 Import and Allows you to import or export data of NEs in a selected
export state.
buttons
4 Parameter Allows you to set basic parameters for NE trace tasks,
setting area including Time Parameter Settings, Cell Parameter
Settings, Periodic Messages Parameters Settings, and
MDT Parameters Settings.
NOTE
If a parameter setting area is unavailable, the event which is
selected does not support this parameter.

5 Message Allows you to set messages provided by NEs.

setting area NOTE
 If different licenses of Trace Server northbound file
interfaces are loaded, the displayed message list is different.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 35

No. Name Description

6 Detailed Displays detailed subscription information.

subscription
information
area
7 Button bar Provides the message apply and cancel functions.

If the attributes of Cell, eNodeB ID, PLMN, and TAC are modified, you need to reissued subscription of
the entire network.

4.2.3 Parameters for Subscribing to an LTE NE Trace Task (OSSii)

This section describes the parameters for subscribing to LTE NE trace tasks.

When you query multiple NEs. If the parameters of Basic Settings area are different, all
parameters are displayed as default values. If the parameters of Basic Settings area are the
same, all parameters are displayed as specific setting. When you click Apply, Trace Server
will issues the parameters which are displayed to NEs.

Table 1.2 Parameters for subscribing to an LTE NE trace task

Area Parameter Description

NE By default, the NE navigation tree is displayed

by network topology.
Basic Time Start Time Indicates the subscription start time.
Settings Parameter
Settings End Time Indicates the subscription end time.
Collection Indicates the specific hour-level time segment
Time for subscription.
You can specify some hour-level time
segments intersecting with the subscription
start time and end time as the subscription time
segments.
Default value: All day

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 36

Area Parameter Description

Cell Cell-level Indicates the number of cell-level traced UEs

Parameter traced UEs and is used to group measurement report
Settings messages.
Value range: 0 to 400
Default value: 10
NOTE
 0 indicates all the UEs.

 The more the number of UEs to be traced

concurrently, the greater the impact on system
performance and subscriber services.
 After periodic event subscription is issued, the
base station randomly selects X online UEs (X is
the preset number of cell-level traced UEs) and
instructs each UE to periodically measure the
throughput based on the period Y (Y is the
preset measurement reporting period). When the
period arrives, a periodic throughput
measurement event is generated. Each UE
reports the event for consecutive Z times (Z is
the default consecutive reporting times, default
value is 16) when the UE is online. The events
reported are cached in NE memories. When the
cache time reaches five minutes or the cache
size reaches 1 MB, the NE reports the cached
events to the Trace Server.
 After subscription to maximum-level standard
signaling events is issued to a base station, the
base station selects X UEs newly connected to
the base station and reports events of the
selected UEs to the Trace Server. X indicates the
predefined number of cell-level traced UEs. The
base station saves the events in its memory.
When the cache duration reaches 5 minutes or
the cache size reaches 1 MB, the base station
reports the cached events to the Trace Server.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 37

Area Parameter Description

Cell type Indicates the cell type during cell tracing. This
parameter is used to group messages of
different events.
Default value: ALL cell
Values: ALL cell, NB-loT cell, and FDD-TDD
cell.
 ALL cell: indicates configurations take
effect for all cells on NEs.
 NB-loT cell: indicates configurations take
effect for all NB-IoT cells on NEs.
 FDD-TDD cell: indicates configurations
take effect for all FDD-TDD cells on NEs.
NOTE
 Non-cell events and subscriber events are
supported by default without being
distinguished.
 This parameter applies only to LTE NEs whose
version is SRAN13.1 or later.
 The pico NE only support ALL cell parameter.

Periodic Report Select a period from the drop-down list. When

Messages interval the period is select, the NE reports
Parameters measurement events based on this period.
Settings NOTE
If this parameter is set to different values for the
same periodic measurement event on multiple
upper-layer applications, the Trace Server issues the
minimum period to NEs.
Values: 2048 ms, 5120 ms, 10240 ms, and 1
Minute.
Default value: 10240 ms.
Report Values: Eight Times, Sixteen Times, Thirty-
amount two Times, Sixty-four Times, and Infinity
Times.
Default value: Sixteen Times.
NOTE
If this parameter is set to different values for the
same periodic measurement event on multiple
upper-layer applications, the Trace Server issues the
maximum number of times to NEs.

MDT UE Values: Polling and Ability first.

Parameters selection Default value: Polling.
Settings
NOTE
If this parameter is set to different values for the
same periodic measurement event on multiple
upper-layer applications, the Trace Server issues the
polling policy to NEs.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 38

Area Parameter Description

Initiatively Values: YES and NO.

open UE Default value: NO.
GNSS
NOTE
Whether the GPS takes effect also depends on UE
capability and behavior. If this parameter is set to
different values for the same periodic measurement
event on multiple upper-layer applications, the Trace
Server issues the most recent value to NEs.

Subframe Indicates the subframe index of the M3 MDT

index event.
Value range: 0 to 9.
Default value: 2.
Logged Logging Values: 5120 ms, 10240 ms, 20480 ms, 30720
MDT interval ms, 40960 ms, and 61440 ms.
Parameter Default value: 10240 ms.
Logging Values: 10 Minutes, 20 Minutes, 40 Minutes,
duration 60 Minutes, 90 Minutes, and 120 Minutes.
Default value: 10 Minutes.
Area Scope  The Set area scope is clear by default. If the
measurement scope of Logged MDT events
needs to be specified, select Set area
scope. You can select Cell or Tracking
area. A maximum of 32 cells or 8 tracking
areas can be selected for each NE.
− When Cell is selected: You can select
the specified NE from the NE
navigation tree, and the table in the right
pane displays information about the
cells under the NE; you can also
configure the cells.
− When Tracking area is selected: The
system displays information about the
tracking areas. You can configure the
tracking areas.
 If the measurement scope of Logged MDT
events does not need to be specified,
deselect Set area scope. If the
measurement scope has been set by
following Cell or Tracking area, select Set
area scope, delete the original settings, and
deselect Set area scope.
NOTE
When you only switch over to Cell or Tracking
area without modifying other parameters, clicking
OK will not modify parameters.

Message Settings Find You can type the keywords and click Previous
Message or Next to search for the required messages.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 39

Area Parameter Description

Message ID Uniquely identifies a message.

Message Indicates the name of a message.
Name
Message Indicates the type of a message.
Type NOTICE
The following operations have impact on system
performance and user services. Be caution when
performing these operations.
 Select too many periodic MR events at a time.
 Set the period for reporting periodic MR events
too small.
 Set the number of reporting periodic MR events
too large.

Export Allows you to export message events

configured on existing NEs and import them to
message configurations on other NEs to
configure message events quickly. You can
also export a template that is not configured
with message events, set required message
events, and import the configured template to
NE message configurations.
CSV, XLS, and XLSX export files are
available.
Import Allows you to import recently exported
message event configurations or manually
modified message event templates to NE
message configurations to configure message
events quickly.
Message events to be imported are in the
unavailable and selected state. If the message
events are contained in the imported file, the
message events are in the available state.
Otherwise, status of the message events
remains unchanged.
CSV, XLS, and XLSX import files are
available.
Detailed subscription NE Name Indicates the name of the NE whose data needs
information area to be subscribed to.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 40

Area Parameter Description

Subscribed Indicates the existing subscription status.

Status Values of the parameter are as follows:
 Subscribing: indicates that the Trace Server
is issuing subscription to a target NE.
 Subscribed: indicates that the Trace Server
issues subscription to a target NE
successfully.
 Unsubscribed: indicates that the Trace
Server has issued no subscription to a target
NE or canceled subscription to a target NE.
 Unsubscribing: indicates that the Trace
Server is canceling subscription to a target
NE.
Start Time Indicates the subscription start time.
End Time Indicates the subscription end time.
Collection Indicates whether the Trace Server is
State collecting data from a selected NE. Values of
the parameter are as follows:
 Running: indicates that the Trace Server is
collecting data from a target NE.
 Idle: indicates that the Trace Server collects
no data from a target NE.
Collection Indicates the specific hour-level time segment
Time for subscription in a day.
Operation Summarizes successful and failed subscription
Result information.

Table 1.3 Shortcut menus for LTE NE subscription

The portal for LTE NE subscription: Select the NE to be subscribed to in the left NE
navigation tree on the LTE Common Trace Server NBI page and select a subscription record
in the NE subscription information list in the right area.

Shortcut Menu Description

Subscribe Allows you to subscribe to an LTE NE trace task. The Subscribe

page displays events whose subscription is issued on the U2000
client.
Subscribe all NEs Allows you to subscribe to all selected LTE NE trace tasks.
View details Allows you to view the detailed subscription information. Related
parameters cannot be modified. The detailed subscription page
displays events whose subscription has been issued and taken effect.
You can view subscription details on the Subscribe page at off-peak
hours.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 41

Shortcut Menu Description

Unsubscribe Unsubscribes to an LTE NE trace task.

Unsubscribe all Unsubscribes to all selected LTE NE trace tasks.
NEs.

Table 1.4 Shortcut menu for message settings

You can right-click the Message Settings area on the Subscribe page and choose an item
from the shortcut menu to manage messages.

Shortcut Menu Description

Select ALL Allows you to select all message events

quickly.
Clear ALL Allows you to deselect all message events
quickly.
Export Allows you to export message events
configured on existing NEs and import them
to message configurations on other NEs to
configure message events quickly. You can
also export a template that is not configured
with message events, set required message
events, and import the configured template
to NE message configurations.
CSV, XLS, and XLSX export files are
available.
Import Allows you to import recently exported
message event configurations or manually
modified message event templates to NE
message configurations to configure
message events quickly.
Message events to be imported are in the
unavailable and selected state. If the
message events are contained in the
imported file, the message events are in the
available state. Otherwise, status of the
message events remains unchanged.
CSV, XLS, and XLSX import files are
available.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 42

4.3 Commissioning the Interconnection of the Standard

Signaling Northbound Result File Interface
The NMS obtains standard signaling northbound result files generated by the Trace Server by
using FTP or SFTP. Based on the files, you can determine whether the standard signaling
northbound result interface meets the requirements for interconnecting with the NMS.

Prerequisites
 The NMS and the Trace Server are connected properly.
 You have obtained the IP address of the Trace Server (the FTP server) and the FTP user
name and password.
 You have obtained the standard signaling northbound result file name and save path. For
details, see 2Overview of Result Files.
 You have deliveried an event subscription task. For details, see 4.2.1Subscribing to an
LTE NE Trace Task.
 You have logged in to the NMS server.

Context
The NMS obtains northbound result files from a specified directory on the Trace Server using
FTP or SFTP.

Procedure
Step 1 Log in using FTP or SFTP.

If you need to... Run the following command...

Log in using FTP ftp IP address of the Trace Server

You are advised to use the SFTP protocols because the SFTP protocols is more secure than the FTP
protocols.

Step 2 Type the user name and the password as prompted.

Step 3 Run the following command to set the save path for standard signaling northbound result files
on the Trace Server.
> cd /export/home/omc/var/fileint/TSNBI/FileType/yyyymmdd/NE identifier/

FileType indicates the data type, such as LTE_CELL_TRC or LTE_SIG. yyyymmdd indicates the date
and NE identifier contains neName and NEFDN.

Step 4 Run the following command to set the destination save path for standard signaling northbound
result files on the NMS. (The directory /opt/file is used as an example).
> lcd /opt/file
Step 5 Run the following command to set the transfer mode to binary mode if files are obtained by
using FTP. Otherwise, skip this step.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 43

> bin
Step 6 Run the following command to obtain files.
> get Northbound result file name
Step 7 Run the bye command to exit FTP or SFTP after files have been downloaded.
Step 8 Check the obtained standard signaling northbound files.
1. Based on the file name, check that the NE information and time are consistent with those
of the task issued by a customer.
2. Parse the standard signaling northbound files. For details, see 2.5Formats of Standard
Signaling Northbound Result Files.
The northbound standard signaling northbound result file interface meets the
interconnection conditions if the results in the files are consistent with the signaling
information that a customer subscribes to. Otherwise, contact Huawei technical support
engineer.
----End

4.4 Optional: Setting the Northbound Push FTP Server

(Trace Server Co-deployed with the U2000 in the ATAE
Cluster System)
Before commissioning the XFTP northbound file push function, you need to set an FTP server
to receive data. After the FTP server is set successfully, the Trace Server will scan the
northbound files every 5 minutes and push the scanned files to the specified FTP server.

Prerequisites
 The Trace Server and the U2000 server are connected properly.
 You have logged in to the U2000 client.
 The mediation software of the NE on the LTE network has been installed on the U2000
server.
 The U2000 has loaded the licenses related to northbound trace.
 You must have the permission of file server setting.
 Subscription has been delivered to the Trace Server, and a trace file has been generated
in /export/home/omc/var/fileint/TSNBI/ on the Trace Server boards.

If you need to set the transmission mode between the Trace Server co-deployed with the U2000 in the
ATAE cluster system and the upper-layer NMS for the public and private key authentication to SFTP,
perform the instruction provided in section Configuring the SFTP for Actively Transferring Files
over the Northbound Interface (Public and Private Keys) for a specific U2000 networking mode in
the administrator guide.

Procedure
Step 1 Choose Software > FTP Auto Upload Management > Target Server Settings (traditional
style); alternatively, double-click System Management in Application Center and choose

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 44

Settings > FTP Auto Upload Management > Target Server Settings (application style).
The Target Server Setting window is displayed.
Step 2 Set Module Type to Trace Server NBI and click Add. The Target Server Settings dialog
box is displayed.
Step 3 In the Target Server Settings dialog box, set Server IP, User Name, Password, Server
Directory, Source Directory, and File Compression Type parameters.
Figure 3.1 is the GUI for Target Server Settings

Figure 3.1 GUI for Target Server Settings

----End

4.5 Optional: Setting the Northbound Push FTP Server

(ATAE Cluster and Virtual Cluster, Standalone)
Before commissioning the XFTP northbound file push function, you need to set an FTP server
to receive data. After the FTP server is set successfully, the Trace Server will scan the
northbound files every 5 minutes and push the scanned files to the specified FTP server.

Prerequisites
 The Trace Server software has been installed.
 The PC communicates with the Trace Server properly.
 You have logged in to the master Trace Server as user ossuser using PuTTY.
 To set the transmission mode for the public and private key authentication to SFTP,
follow the instructions provided in 5.3Setting the SFTP Public and Private Key
Authentication for the Northbound Push FTP Server.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 45

Context
You can set information about multiple northbound FTP servers.

Procedure
Step 1 Use PuTTY to log in to the master Trace Server in SSH mode as user ossuser.
Step 2 Run the following commands to run the set_xftp_config.sh script:
~> cd /opt/oss/server/rancn/bin
~> sh set_xftp_config.sh
1. When the following information is displayed, type Y to configure XFTP information, or
type N to exit the configuration.
Are you sure you want to set XFTP push config[Y: enter, N:quit]

2. Type Y to configure XFTP information.

When the following information is displayed, type the IP address of the northbound FTP
server.
Please enter the IP address of FTP server:

If type the IP address of the northbound FTP server to exist in the configuration file, the
system display the following information:
Do you want to modify or delete the exist info[1: modify, 2: delete, 3: cancel]

 Type 1 to modify the northbound FTP server information of this IP address, Type 2 to delete the
northbound FTP server information of this IP address, Type 3 to cancel.
3. When the following information is displayed, type the local path to which the result files
need to be pushed, for example, /export/home/omc/var/fileint/TSNBI.
Please enter the directory of local:

4. When the following information is displayed, type 1 to set the automatic upload of trace
result files.
Please enter the push status[0: disable, 1: enable]:

5. Set the connection mode between the northbound FTP server and the Trace Server as
prompted.
Please enter the FTP type [0: FTP, 1:SFTP, default: 1]:

6. Type the command port number of the northbound FTP server as prompted.
Please enter the port of FTP server [default: 22(sftp)]:

If the SFTP protocol is used, the default value is 22. If the FTP protocol is used, the default value is 21.
7. Type the user name of the northbound FTP server as prompted.
Please enter the username of FTP server:

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 46

 Ensure that users can log in to the northbound FTP server using the specified protocol and
port.
 If public and private key authentication is used, the user name must be the same as that for
logging in to the NMS mentioned in section 5.3Setting the SFTP Public and Private Key
Authentication for the Northbound Push FTP Server.

8. If you set the FTP connection mode to SFTP in Step 2.5, based on the system output, set
whether the public key authentication is used. Y indicates that public key authentication
is used, and N indicates that it is not used. If you do not set the FTP connection mode to
SFTP, go to Step 2.10. For details about how to set the public and private key
authentication, see 5.3Setting the SFTP Public and Private Key Authentication for the
Northbound Push FTP Server.
Use the Public and Private Keys or not [Yy/Nn]?

9. If you select Y to use the public key authentication, based on system output, set whether
the password authentication is used at the same time. If you do not select Y, go to Step
2.10.
Set the password or not? [Yy/Nn]

Select Y to use the password authentication and perform the following steps. Otherwise,
go to Step 2.11.
10. Type the password of the user for the northbound FTP server as prompted.
Please enter the password of FTP user:

11. Set the path to which trace result files are uploaded on the northbound FTP server as
prompted, for example, /TSNBI.
Please enter the directory of FTP server:

Ensure that the specified user has the read and write permission on the path. And special
characters :& * \ " ' < > ? can not appear.

12. When the following information is displayed, you need to determine whether to add
another northbound FTP server.
Are you sure you want to set XFTP push config[Y: enter, N:quit]

If you type Y, the preceding steps are performed again to add another northbound FTP
server. If you type N, the northbound FTP server configuration exits.
Step 3 Select whether to restart the TSXFTPService service as prompted.
Do you want to restart all TSXFTPService?[Y: enter, N:quit]

 If you type Y. the system displays the following information, TSXFTPService service
has been restarted successfully.
restart TSXFTPServices, please wait
restart TSXFTPServices successfully.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 47

 If you type N, the northbound FTP server configuration exits. If you need to restart the
TSXFTPService service manually, perform the following steps.

In order to restart the services more quickly, you are advised to restart the Trace Server
services by Step 4.

Step 4 Run the following commands to restart the Trace Server services:
~> . /opt/oss/server/svc_profile.sh
~> stop_svc
If the command output contains Finished stopping the service., Trace Server services have
been stopped successfully.
~> start_svc
If the command output contains Finished starting the system., the Trace Server service has
been started successfully.
Step 5 Run the following commands to verify that the Trace Server services are restarted
successfully:
~> svc_adm -cmd status -sysagent all | grep TSCollector | grep "not running"
When there is no information displayed, the Trace Server services are restarted successfully.
----End

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 48

Copyright © Huawei
Technologies Co., Ltd.
U2000 Troubleshooting for the Standard Signaling Northbound
Trace Server LTE Standard Signaling Northbound File Result File InterfaceTroubleshooting for the Standard
Interface Developer Guide Signaling Northbound Result File Interface

5 Troubleshooting for the Standard

Signaling Northbound Result File Interface

About This Chapter

The NMS is interconnected with the Trace Server through the standard signaling northbound
result file interface. If problems occur when getting standard signaling data northbound of
NEs on the network, you can solve problems using the methods described in this section.
5.1 Troubleshooting and Information Collection
If faults occur when the NMS attempts to obtain standard signaling data northbound results of
NEs through the standard signaling northbound result file interface, you can handle the faults
by referring to common troubleshooting methods. If uncommon faults occur, you need to
collect information about the faults and contact Huawei technical support engineers.
5.2 Handle the Problem That No Standard Signaling Northbound Result File Is Generated
Either of the following causes may lead to the problem that no standard signaling northbound
result file is generated: NEs are disconnected, or free disk space of the Trace Server is
insufficient. This section describes how to handle this problem in either of the two situations.
5.3 Setting the SFTP Public and Private Key Authentication for the Northbound Push FTP
Server
When the trace server actively uploads files to the NMS over the northbound interface, the
trace server functions as an FTP client and the NMS functions as an FTP server. The plaintext
FTP mode is used by default. To ensure data security during file transmission, you can set the
SFTP encryption mode.
5.4 How Do I Set the DST?
DST is optional, depending on whether the NE is in daylight saving time (DST) mode. The
DST identifier is disabled by default.

5.1 Troubleshooting and Information Collection

If faults occur when the NMS attempts to obtain standard signaling data northbound results of
NEs through the standard signaling northbound result file interface, you can handle the faults

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 49

by referring to common troubleshooting methods. If uncommon faults occur, you need to

collect information about the faults and contact Huawei technical support engineers.

Common Troubleshooting
Table 1.1 lists methods for handling common faults that may occur when the NMS collects
standard signaling data northbound of NEs.

Table 1.1 Common troubleshooting

Common Fault Troubleshooting Method

No standard signaling northbound result file See 5.2Handle the Problem That No
is generated. Standard Signaling Northbound Result File
Is Generated.

Information Collection
If uncommon faults occur when the NMS attempts to obtain the standard signaling data
northbound of the NEs, you need to collect related information to locate the faults. For details
about how to collect fault information, see Table 1.1.

Table 1.1 Information collection

Related Information Description

Operation information Record the operations performed before a

fault occurs and the troubleshooting
measures taken later.
Version information Obtain version information about the Trace
Server, U2000, NE mediations, and NEs.
IP information Obtain IP addresses of the Trace Server and
the U2000 server.
Log information Obtain log file from the Trace Server boards'
/opt/oss/server/var/logs/iMAP.tscollector
XXXX_agent.trace, and
/export/home/omc/var/logs/TS_CBB/XX/
XX/CBB.log paths.
NOTE
 The first two digits XX together of the
tscollectorXXXX indicate the server number
and the last two digits XX together indicate
the number of the service on the server.
 The first two digits XX together of the
/export/home/omc/var/logs/TS_CBB/XX/X
X indicate the server number and the last two
digits XX together indicate the number of the
service on the server.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 50

5.2 Handle the Problem That No Standard Signaling

Northbound Result File Is Generated
Either of the following causes may lead to the problem that no standard signaling northbound
result file is generated: NEs are disconnected, or free disk space of the Trace Server is
insufficient. This section describes how to handle this problem in either of the two situations.

Problem Description
No standard signaling northbound result file is generated in the path, and the NMS cannot
collect standard signaling northbound results of NEs.

Problem Analysis
Either of the following causes can result in the problem:
 NEs are disconnected.
 Free disk space on the Trace Server is insufficient.

Analysis of Disconnected NEs

1. Choose Topology > Main Topology (traditional style); alternatively, double-click Topo
View in Application Center and choose Topology > Main Topology (application style)
on the U2000 client, right-click the disconnected NE, and then choose Enable Ne
Connection from the shortcut menu.
2. Verify that the network connection is normal.
3. Debug the NE mediation.If you need to reinstall the NE mediation, see Commissioning
Guide of the corresponding U2000 networking mode.

Analysis of the Insufficient Free Disk Space of the Trace Server

Clear the disk space of the Trace Server.

You must check whether files can be deleted when clearing the disk space. If you delete the
files by mistake, the system may run improperly.

Solution
Contact Huawei technical support engineers.

5.3 Setting the SFTP Public and Private Key

Authentication for the Northbound Push FTP Server
When the trace server actively uploads files to the NMS over the northbound interface, the
trace server functions as an FTP client and the NMS functions as an FTP server. The plaintext

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 51

FTP mode is used by default. To ensure data security during file transmission, you can set the
SFTP encryption mode.

Prerequisites
 Use Putty to log in to the trace server in SSH mode as user ossuser. For the Trace Server
independently deployed in an ATAE cluster system, log in to all the boards.
 You have logged in to the NMS server as user UserA.
UserA is the NMS server user. Replace it as required.

Context
 To set up an SFTP connection using public or private key authentication, save the trace
server's public key file in the authorized_keys file of the related NMS server user. The
system performs authentication using the trace server's private key and the trace server's
public key stored on the NMS server. After the authentication is successful, the SFTP
connection is set up successfully. It is not required to provide the NMS login password.
 The public and private key authentication files can be encrypted or not. For encrypted
public and private key authentication files, set the password. If you forget the password,
all public and private key authentication files must be generated again, and the new files
will replace the existing files.
 When the XFTP service uploads files in FTP mode, the Linux or Unix operating system
of the northbound server should use the vsftpd software whose version is 2.0.5 or later.
The northbound server with Windows operating system is not supported.

Procedure
Step 1 Public and private key files are generated on the trace server.

If you need to... Then...

Generate encrypted Only perform Step 1.1 to Step 1.4.

public and private
key files.

Generate non- Only perform Step 1.5 to Step 1.8.

encrypted public and
private key files.

1. Run the following command on the trace server to check whether the .ssh directory
exists in the home directory.
~> cd /export/home/omc/.ssh/
− If No such file or directory is displayed, the .ssh directory is unavailable in the
home directory. Perform Step 1.2 after running the following command:
~> mkdir -p /export/home/omc/.ssh/
~> cd /export/home/omc/.ssh/
− If no command result is displayed, the .ssh directory is available in the home
directory. Perform Step 1.2.
2. Run the following command to modify the rights of the omc directory and the .ssh
directory.
~> chmod 755 /export/home/omc/
~> chmod 755 /export/home/omc/.ssh/

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 52

3. Run the following command to check whether the id_rsa_pwd.pub file exists.
~> ls id_rsa_pwd.pub
− If the system displays id_rsa_pwd.pub: No such file or directory, perform Step
1.4 to create a public key file.
− If the system displays id_rsa_pwd.pub, perform Step 2.
4. Run the following command to create encrypted public and private key files.
~> ssh-keygen -t rsa
If the system displays the following message, enter
/export/home/omc/.ssh/id_rsa_pwd.
Generating public/private rsa key pair.
Enter file in which to save the key (/export/ossuser/.ssh/id_rsa):
If the following message is displayed, enter the password twice. When ~> is displayed,
the encrypted public key file is generated.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:

Keep the password for future use. If the password is lost, all public and private key files must
be generated again, and the new files will replace the existing files.

5. Run the following command on the trace server to check whether the .ssh directory
exists in the home directory.
~> cd /export/ossuser/.ssh/
− If No such file or directory is displayed, the .ssh directory is unavailable in the
home directory. After running the following command, perform Step 1.6.
~> mkdir -p /export/ossuser/.ssh/
− If no command output is displayed, the .ssh directory is available in the home
directory. Perform Step 1.6.
6. Run the following command to modify the rights of the ossuser directory and the .ssh
directory.
~> chmod 755 /export/ossuser/
~> chmod 755 /export/ossuser/.ssh/
7. Run the following command to check whether the id_rsa file exists.
~> ls id_rsa
− If the system displays id_rsa: No such file or directory, perform Step 1.8 to create
public and private key files.
− If the system displays id_rsa, perform Step 2.
8. Run the following command to create non-encrypted public and private key files.
~> ssh-keygen -t rsa -b 1024 -f id_rsa -N ""
If the system displays information similar to the following, the non-encrypted public key
file has been created successfully:

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 53

Generating public/private rsa key pair.

Your identification has been saved in id_rsa.
Your public key has been saved in id_rsa.pub.

Step 2 Enable public key authentication on the NMS.

1. Log in to the NMS server as user UserA. Run the cd ${HOME}/.ssh/ command to check
whether the .ssh directory exists in the home directory.
− If No such file or directory is displayed, the .ssh directory is unavailable in the
home directory. After running the mkdir -p ${HOME}/.ssh/ command, perform
Step 2.2.
− If no command result is displayed, the .ssh directory is available in the home
directory. Perform Step 2.2.

The ${HOME} parameter indicates the home directory of user UserA.

2. Run the following command to modify the rights of the ${HOME} directory and the .ssh
directory.
chmod 755 ${HOME}/
chmod 755 ${HOME}/.ssh/
3. Run the ls authorized_keys command to check whether the authorized_keys file exists.
− If the system displays authorized_keys: No such file or directory, run the touch
authorized_keys command to create the authorized_keys file. Then, perform Step
2.4.
− If the system displays authorized_keys, proceed to Step 2.4.
4. Run the following command to modify the right of the authorized_keys file.
chmod 644 ${HOME}/.ssh/authorized_keys
5. Copy the content of the id_rsa.pub or id_rsa_pwd.pub file on the trace server to the
authorized_keys file on the NMS server.

 For a non-encrypted public key file, copy the id_rsa.pub file's content.
If the id_rsa.pub file does not exist, copy the ${HOME}/.ssh/authorized_keys file's
content on the trace server server.
 For an encrypted public key file, copy the id_rsa_pwd.pub file's content.

a. Run the cat id_rsa.pub or cat id_rsa_pwd.pub command on the trace server. The
content of the id_rsa.pub or id_rsa_pwd.pub file is displayed.
b. Run the vi command on the NMS server to write the content of the id_rsa.pub or
id_rsa_pwd.pub file into the authorized_keys file.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 54

 The content to be written into the authorized_keys file cannot contain any line feed. If
any line feed exists, delete it.
 If the authorized_keys file contains any other data, perform a line feed operation. Then,
write the content.

6. Run the vi command to modify the /etc/ssh/sshd_config file and configure SFTP
parameters on the NMS server.
# su - root
Password: Password of user root
# vi /etc/ssh/sshd_config
Table 1.1 lists the parameters to be configured.

Table 1.1 Parameters to be configured for the SFTP

Parameter Value

RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys
PasswordAuthenticatio yes/no. This parameter specifies whether the password
n authentication is used when the authentication of the public key
and private key fails. You are advised to set this parameter to yes.
 yes: password authentication is used.
 no: password authentication is not used.

7. Perform the following operations on the NMS server to check the SFTP service status.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 55

If... Then...

The NMS server is The # ps -ef | grep sshd | grep -v grep

running Solaris OpenSS root 27748 1 0 Dec 25 ? 2:13
H has /usr/local/sbin/sshd
been root 21923 27748 0 11:11:31 ?
installed 0:02 /usr/local/sbin/sshd -R
Run the  If the command output contains /usr/local/sbin/sshd,
pkginfo the SFTP service is running. Run the following
OpenSS command to restart the SFTP service:
H
comman # /etc/init.d/opensshd restart
d, and  If no command output is displayed, the SFTP service
the has not started. Run the following command to start
followin the SFTP service:
g # /etc/init.d/opensshd start
comman
d output
is
displaye
d:
Securit
y
OpenSSH
OpenSSH
Portabl
e for
Solaris

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 56

If... Then...

No # svcs -a | grep ssh

OpenSS online 17:27:13 svc:/network/ssh:defaul
H has
been  If the command output contains online, the SFTP
installed service is running. Run the following command to
restart the SFTP service:
Run the
pkginfo # svcadm restart svc:/network/ssh:default
OpenSS  If the command output contains disabled, the SFTP
H service has not started. Run the following command
comman to start the SFTP service:
d, and # svcadm enable svc:/network/ssh:default
the
followin
g
comman
d output
is
displaye
d:
ERROR:
informa
tion
for
"OpenSS
H" was
not
found

The NMS server is running # service sshd status

SUSE Linux Checking for service sshd
running
 If the command result contains running, the SFTP
service is running. Run the following command to
restart the SFTP service:
# service sshd restart
 If the command result does not contain running, the
SFTP service is disabled. In this case, contact
Huawei technical support.
The NMS server is running any Contact Huawei technical support.
other OS

Step 3 If the public and private key authentication with a password is used, run the following
commands on the Trace Server to query the password code for the public and private key and
then perform Step 4. If the public and private key authentication without a password is used,
do not run the following commands but go to Step 4.
For the Trace Server independently deployed on an ATAE cluster, run the following
commands:
~> . /opt/oss/server/svc_profile.sh

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 57

~> ssl_adm -cmd encryptpassword Changeme_123

The following message is displayed as the text after encryption:
b273290137C725168F52F3D7E1EA8670

Password Changeme_123 must be the same as that entered in Step 1.4.

Step 4 Run the following commands on the Trace Server to change the XFTP configuration file.
For the Trace Server independently deployed on an ATAE cluster, run the following
commands:
~> cd /opt/oss/server/etc/TSXFTPService
~> vi xftpconfig.xml

Table 1.1 Parameter description

Parameter Description

PrivateKeyFile Set this parameter to the absolute path where the public
key file generated in Step 1.8 is saved, for example,
/export/ossuser/.ssh/id_rsa.
IsSupportEncrpt If the public and private key authentication with a
password is used, the value is 1. If the public and private
key authentication without a password is used, the value
is 0.
PrivateExKeyFile Set this parameter to the absolute path where the public
key file generated in Step 1.4 is saved, for example,
/export/home/omc/.ssh/id_rsa_pwd.
EncrptKey Enter the queried encryption password, for example,
b273290137C725168F52F3D7E1EA8670.

For example:
<commconfig>
……
<PrivateKeyFile>/export/ossuser/.ssh/id_rsa</PrivateKeyFile>
<IsSupportEncrpt>0</IsSupportEncrpt>
<PrivateExKeyFile>/export/home/omc/.ssh/id_rsa_pwd</PrivateExKeyFile>
<EncrptKey></EncrptKey>
……
</commconfig>

If the configuration file xftpconfig.xml does not contain the preceding configuration items, add them
manually, as described in the example.

Step 5 Run the following commands to restart the XFTP service on the trace server.
For the Trace Server independently deployed on an ATAE cluster, run the following
commands to restart the TSXFtpService service:
# . /opt/oss/server/svc_profile.sh

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 58

# svc_adm -cmd status | grep TSXFTPService

If the following information is displayed, the TSXFtpService service name is
TSXFTPServiceXY01.
TSXFTPServiceXY01 [running ]

# svc_adm -cmd restartsvc TSXFTPServiceXY01

If the following information is displayed, TSXFTPServiceXY01 service has been restarted
successfully.
TSXFTPServiceXY01.....................running
svc_adm : info : START finished.

The process whose name contains XY01 is a multi-instance process, where XY01 indicates the process
number. XY varies from the server where the process is deployed.

----End

5.4 How Do I Set the DST?

DST is optional, depending on whether the NE is in daylight saving time (DST) mode. The
DST identifier is disabled by default.

Prerequisites
 You have obtained the IP addresses of the master Trace Server (Trace Server
independently deployed) or the U2000 master server (Trace Server co-deployed with the
U2000 in the ATAE cluster system).
 You have obtained the password of user ossuser.
For ATAE platform, you need to obtain the password of user OSMU Web.
For Virtual platform, you need to obtain the password of user admin.
 You have configured the Trust Relationship Between the Trace Server and the U2000
Server.

Context

The following command output is for reference only.

Procedure
Step 1 Use PuTTY to log in to the U2000 master server (Trace Server co-deployed with the U2000
in the ATAE cluster system) or Trace Server master server (Trace Server independently
deployed) in SSH mode as user ossuser.
Step 2 Run the following commands to modify the configuration file.
 Run the following commands to disable DST.
~> sed -i "/<UsingDST/s/<UsingDST value=\".*\"/<UsingDST
value=\"false\"/g" /opt/oss/server/etc/TSCollector/GUDataHandleCfg.xml

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 59

 Run the following commands to enable DST.

~> sed -i "/<UsingDST/s/<UsingDST value=\".*\"/<UsingDST value=\"true\"/g"
/opt/oss/server/etc/TSCollector/GUDataHandleCfg.xml
Step 3 Run the following commands to confirm that the change was successful.
~> grep UsingDST /opt/oss/server/etc/TSCollector/GUDataHandleCfg.xml
 When information similar to the following is displayed, DST is enabled.
<UsingDST value="true"/>

 When information similar to the following is displayed, DST is disabled.

Step 4 Run the following command to synchronize the configuration file to other server:
~> /opt/oss/server/rancn/bin/copy_file_to_all_board.sh
/opt/oss/server/etc/TSCollector/GUDataHandleCfg.xml
Step 5 Stop Trace Server services.
 For ATAE platform, perform the following operations.
c. Type the following website in the Address bar of the browser on the PC and press
Enter. Then, log in to the OSMU as an OSMU web user.
https://<public IP address of the OSMU server>:30088/osmu or https://private IP
address of the OSMU server>:30084/osmu
d. In the navigation tree, choose Service System > Service Management > Board
Services.
e. On the Board Services tab page in the right pane, confirm that the Trace Server
boards are in the Normal state.
f. Select the check box of the system whose Subsystem contains TS, and click Stop
to stop services.
g. In the displayed confirmation dialog box, click Yes.
h. In the displayed dialog box, click OK.
 For Virtual platform, perform the following operations.
i. Open the browser and type https://Service IP address of the vOSMU:31945 in the
address box. Then, log in to the vOSMU as an admin user.
j. Choose Application > Service Management > Start and Stop Services from the
vOSMU main menu. The Start and Stop Services page is displayed.
k. Click following the Trace Server, check and confirm that the Trace Server
service nodes are in the Running state.
If the service nodes are in other state excluding Running and Stopped, contact
Huawei technical support.
l. Click following Trace Server nodes to stop the Trace Server services.
Step 6 Start Trace Server services.
 For ATAE platform, perform the following operations.
m. In the navigation tree, choose Service System > Service Management > Board
Services.
n. On the Board Services tab page in the right pane, confirm that the Trace Server
boards are in the Normal state.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 60

o. Select the check box of the system whose Subsystem contains TS, and click Start.
p. In the displayed confirmation dialog box, click Yes.
q. In the displayed dialog box, click OK.
 For Virtual platform, perform the following operations.
r. Choose Application > Service Management > Start and Stop Services from the
vOSMU main menu. The Start and Stop Services page is displayed.
s. Click following the Trace Server, whose Trace Server nodes detailed
information is to be viewed.
가 If any board is in the Fault state, contact Huawei technical support.
나 If none of the boards is in the Fault state, go to Step 6.c.
t. Check and confirm that the Trace Server service nodes are in the Stopped state.
u. Click Start and Stop Services on the left navigation tree, back to Start and Stop
Services page.

v. Click following Trace Server to start the Trace Server services.

w. In the displayed Warning dialog box, click OK.
x. In the displayed Prompt dialog box, click OK.
You can click Task Information List in the Prompt dialog box or choose System
> Task Manager > Task Information List from the main menu to view the
progress and execution result of the task.
다 When Task Status is Execution Succeeded, Trace Server services have been
started.
라 When Task Status is Execution Failed, contact Huawei technical support.
----End

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 61

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide AppendixAppendix

6 Appendix

About This Chapter

6.1 Supported NE types and versions
6.2 LTE Event List

6.1 Supported NE types and versions

Table 1.1 lists types and versions of the Supported NE required for the northbound standard
signaling northbound result file.

Table 1.1 Related NE types and versions

NE Type NE Version Remarks

BTS3900 BTS3900 V100R013C10 -

BTS3900 V100R013C00
BTS3900 V100R012C10
BTS3900 V100R012C00
BTS3900 V100R011C10
BTS3900 V100R011C00
BTS5900 BTS5900 V100R013C10 -
BTS5900 V100R013C00
PICO BTS5900 PICO BTS5900 V100R013C10 -
PICO BTS3900 PICO BTS3900 V100R013C10 -
PICO BTS3900 V100R013C00
PICO BTS3900 V100R012C10
PICO BTS3900 V100R012C00
PICO BTS3900 V100R011C10
MICRO BTS3900 MICRO BTS3900 V100R013C10 -

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 62

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide AppendixAppendix

NE Type NE Version Remarks

MICRO BTS3900 V100R013C00

MICRO BTS3900 V100R012C10
MICRO BTS3900 V100R012C00
MICRO BTS3900 V100R011C10
MICRO BTS3900 V100R011C00
eNodeB DBS5900 LTE V100R013C10 -
BTS5900L LTE V100R013C10
BTS5900AL LTE V100R013C10
BTS5900A LTE V100R013C10
BTS5900 LTE V100R013C10
DBS3900 LTE V100R013C10
BTS3900L LTE V100R013C10
BTS3900AL LTE V100R013C10
BTS3900A LTE V100R013C10
BTS3900 LTE V100R013C10
BTS3901A LTE V100R013C10
BTS3901E TDLTE V100R013C10
BTS3202B V100R013C10
BTS3202E V100R013C10
BTS3203E LTE V100R013C10
BTS3205E V100R013C10
DBS5900 LTE V100R013C00
BTS5900L LTE V100R013C00
BTS5900AL LTE V100R013C00
BTS5900A LTE V100R013C00
BTS5900 LTE V100R013C00
DBS3900 LTE V100R013C00
BTS3900L LTE V100R013C00
BTS3900AL LTE V100R013C00
BTS3900A LTE V100R013C00
BTS3900 LTE V100R013C00
BTS3901A LTE V100R013C00
BTS3901E TDLTE V100R013C00
BTS3202B V100R013C00
BTS3202E V100R013C00
BTS3203E LTE V100R013C00
BTS3205E V100R013C00
DBS3900 LTE V100R012C10
BTS3900L LTE V100R012C10

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 63

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide AppendixAppendix

NE Type NE Version Remarks

BTS3900AL LTE V100R012C10

BTS3900A LTE V100R012C10
BTS3900 LTE V100R012C10
BTS3901A LTE V100R012C10
BTS3901E TDLTE V100R012C10
BTS3202B V100R012C10
BTS3202E V100R012C10
BTS3203E LTE V100R012C10
BTS3205E V100R012C10
DBS3900 LTE V100R012C00
BTS3900L LTE V100R012C00
BTS3900AL LTE V100R012C00
BTS3900A LTE V100R012C00
BTS3900 LTE V100R012C00
BTS3901A LTE V100R012C00
BTS3901E TDLTE V100R012C00
BTS3202B V100R012C00
BTS3202E V100R012C00
BTS3203E LTE V100R012C00
BTS3205E V100R012C00
DBS3900 LTE V100R011C10
BTS3900L LTE V100R011C10
BTS3900AL LTE V100R011C10
BTS3900A LTE V100R011C10
BTS3900 LTE V100R011C10
BTS3901A LTE V100R011C10
BTS3901E TDLTE V100R011C10
BTS3202B V100R011C10
BTS3202E V100R011C10
BTS3203E LTE V100R011C10
BTS3205E V100R011C10
DBS3900 LTE V100R011C00
BTS3900L LTE V100R011C00
BTS3900AL LTE V100R011C00
BTS3900A LTE V100R011C00
BTS3900 LTE V100R011C00
BTS3202E V100R011C00
BTS3205E V100R011C00

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 64

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide AppendixAppendix

6.2 LTE Event List

Table 1.2 Event list of LTE standard signaling
Event ID Event Name Interface Initial NE Version

E-RAB SETUP SRAN11.1

0x0100 S1
REQUEST Pico 11.1

E-RAB SETUP SRAN11.1

0x0101 S1
RESPONSE Pico 11.1

E-RAB MODIFY SRAN11.1

0x0102 S1
REQUEST Pico 11.1

E-RAB MODIFY SRAN11.1

0x0103 S1
RESPONSE Pico 11.1

E-RAB RELEASE SRAN11.1

0x0104 S1
COMMAND Pico 11.1

E-RAB RELEASE SRAN11.1

0x0105 S1
RESPONSE Pico 11.1

E-RAB RELEASE SRAN11.1

0x0106 S1
INDICATION Pico 11.1
INITIAL SRAN11.1
0x0107 CONTEXT SETUP S1
REQUEST Pico 11.1

INITIAL SRAN11.1
0x0108 CONTEXT SETUP S1
RESPONSE Pico 11.1

INITIAL SRAN11.1
0x0109 CONTEXT SETUP S1
FAILURE Pico 11.1

UE CONTEXT SRAN11.1
0x010a RELEASE S1
REQUEST Pico 11.1

UE CONTEXT SRAN11.1
0x010b RELEASE S1
COMMAND Pico 11.1

UE CONTEXT SRAN11.1
0x010c RELEASE S1
COMPLETE Pico 11.1

UE CONTEXT SRAN11.1
0x010d MODIFICATION S1
REQUEST Pico 11.1

0x010e UE CONTEXT S1 SRAN11.1

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 65

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide AppendixAppendix

Event ID Event Name Interface Initial NE Version

MODIFICATION
Pico 11.1
RESPONSE
UE CONTEXT SRAN11.1
0x010f MODIFICATION S1
FAILURE Pico 11.1

HANDOVER SRAN11.1
0x0110 S1
REQUIRED Pico 11.1

HANDOVER SRAN11.1
0x0111 S1
COMMAND Pico 11.1
HANDOVER SRAN11.1
0x0112 PREPARATION S1
FAILURE Pico 11.1

HANDOVER SRAN11.1
0x0113 S1
REQUEST Pico 11.1
HANDOVER SRAN11.1
0x0114 REQUEST S1
ACKNOWLEDGE Pico 11.1

HANDOVER SRAN11.1
0x0115 S1
FAILURE Pico 11.1

HANDOVER SRAN11.1
0x0116 S1
NOTIFY Pico 11.1

PATH SWITCH SRAN11.1

0x0117 S1
REQUEST Pico 11.1
PATH SWITCH SRAN11.1
0x0118 REQUEST S1
ACKNOWLEDGE Pico 11.1

PATH SWITCH SRAN11.1

0x0119 REQUEST S1
FAILURE Pico 11.1

HANDOVER SRAN11.1
0x011a S1
CANCEL Pico 11.1
HANDOVER SRAN11.1
0x011b CANCEL S1
ACKNOWLEDGE Pico 11.1

eNB STATUS SRAN11.1

0x011c S1
TRANSFER Pico 11.1

MME STATUS SRAN11.1

0x011d S1
TRANSFER Pico 11.1

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 66

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide AppendixAppendix

Event ID Event Name Interface Initial NE Version

SRAN11.1
0x011e PAGING S1
Pico 11.1

INITIAL UE SRAN11.1
0x011f S1
MESSAGE Pico 11.1

DOWNLINK NAS SRAN11.1

0x0120 S1
TRANSPORT Pico 11.1

UPLINK NAS SRAN11.1

0x0121 S1
TRANSPORT Pico 11.1
NAS NON SRAN11.1
0x0122 DELIVERY S1
INDICATION Pico 11.1

SRAN11.1
0x0123 RESET S1
Pico 11.1

RESET SRAN11.1
0x0124 S1
ACKNOWLEDGE Pico 11.1

ERROR SRAN11.1
0x0125 S1
INDICATION Pico 11.1

S1 SETUP SRAN11.1
0x0126 S1
REQUEST Pico 11.1

S1 SETUP SRAN11.1
0x0127 S1
RESPONSE Pico 11.1

S1 SETUP SRAN11.1
0x0128 S1
FAILURE Pico 11.1
ENB SRAN11.1
0x0129 CONFIGURATION S1
UPDATE Pico 11.1

ENB
CONFIGURATION SRAN11.1
0x012a S1
UPDATE Pico 11.1
ACKNOWLEDGE
ENB SRAN11.1
0x012b CONFIGURATION S1
UPDATE FAILURE Pico 11.1

MME SRAN11.1
0x012c CONFIGURATION S1
UPDATE Pico 11.1

0x012d MME S1 SRAN11.1

CONFIGURATION Pico 11.1
UPDATE

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 67

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide AppendixAppendix

Event ID Event Name Interface Initial NE Version

ACKNOWLEDGE
MME SRAN11.1
0x012e CONFIGURATION S1
UPDATE FAILURE Pico 11.1

DOWNLINK S1
0x012f CDMA2000 S1 SRAN11.1
TUNNELING
UPLINK S1
0x0130 CDMA2000 S1 SRAN11.1
TUNNELING

UE CAPABILITY SRAN11.1
0x0131 S1
INFO INDICATION Pico 11.1
SRAN11.1
0x0132 TRACE START S1
Pico 11.1

TRACE FAILURE SRAN11.1

0x0133 S1
INDICATION Pico 11.1

DEACTIVATE SRAN11.1
0x0134 S1
TRACE Pico 11.1
LOCATION SRAN11.1
0x0135 REPORTING S1
CONTROL Pico 11.1

LOCATION SRAN11.1
0x0136 REPORT FAILURE S1
INDICATION Pico 11.1

LOCATION SRAN11.1
0x0137 S1
REPORT Pico 11.1

OVERLOAD SRAN11.1
0x0138 S1
START Pico 11.1
SRAN11.1
0x0139 OVERLOAD STOP S1
Pico 11.1
WRITE-REPLACE SRAN11.1
0x013a WARNING S1
REQUEST Pico 11.1

WRITE-REPLACE SRAN11.1
0x013b WARNING S1
RESPONSE Pico 11.1

eNB DIRECT SRAN11.1

0x013c INFORMATION S1
TRANSFER Pico 11.1

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 68

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide AppendixAppendix

Event ID Event Name Interface Initial NE Version

MME DIRECT SRAN11.1

0x013d INFORMATION S1
TRANSFER Pico 11.1

CELL TRAFFIC
0x013e S1 SRAN11.1
TRACE
eNB SRAN11.1
0x013f CONFIGURATION S1
TRANSFER Pico 11.1

MME SRAN11.1
0x0140 CONFIGURATION S1
TRANSFER Pico 11.1

SRAN11.1
0x0141 KILL REQUEST S1
Pico 11.1
SRAN11.1
0x0142 KILL RESPONSE S1
Pico 11.1
DOWNLINK UE SRAN11.1
0x0143 ASSOCIATED S1
LPPA TRANSPORT Pico 11.1

UPLINK UE SRAN11.1
0x0144 ASSOCIATED S1
LPPA TRANSPORT Pico 11.1

DOWNLINK NON SRAN11.1

0x0145 UE ASSOCIATED S1
LPPA TRANSPORT Pico 11.1

UPLINK NON UE SRAN11.1

0x0146 ASSOCIATED S1
LPPA TRANSPORT Pico 11.1

UE RADIO SRAN11.1
0x0147 CAPABILITY S1
MATCH REQUEST Pico 11.1

UE RADIO
CAPABILITY SRAN11.1
0x0148 S1
MATCH Pico 11.1
RESPONSE
UE CONTEXT
0x0151 MODIFICATION S1 SRAN12.1
CONFIRM
CONNECTION
0x0152 ESTABLISHMENT S1 SRAN12.1
INDICATION
0x0153 UE CONTEXT S1 SRAN12.1
SUSPEND

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 69

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide AppendixAppendix

Event ID Event Name Interface Initial NE Version

REQUEST
UE CONTEXT
0x0154 SUSPEND S1 SRAN12.1
RESPONSE
UE CONTEXT
0x0155 RESUME S1 SRAN12.1
REQUEST
UE CONTEXT
0x0156 RESUME S1 SRAN12.1
RESPONSE
UE CONTEXT
0x0157 RESUME S1 SRAN12.1
FAILURE

HANDOVER SRAN11.1
0x0200 X2
REQUEST Pico 11.1
HANDOVER SRAN11.1
0x0201 REQUEST X2
ACKNOWLEDGE Pico 11.1

HANDOVER SRAN11.1
0x0202 PREPARATION X2
FAILURE Pico 11.1

SN STATUS SRAN11.1
0x0203 X2
TRANSFER Pico 11.1

UE CONTEXT SRAN11.1
0x0204 X2
RELEASE Pico 11.1

HANDOVER SRAN11.1
0x0205 X2
CANCEL Pico 11.1
LOAD
0x0206 X2 SRAN11.1
INFORMATION

ERROR SRAN11.1
0x0207 X2
INDICATION Pico 11.1

X2 SETUP SRAN11.1
0x0208 X2
REQUEST Pico 11.1

X2 SETUP SRAN11.1
0x0209 X2
RESPONSE Pico 11.1

X2 SETUP SRAN11.1
0x020a X2
FAILURE Pico 11.1
0x020b RESET REQUEST X2 SRAN11.1

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 70

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide AppendixAppendix

Event ID Event Name Interface Initial NE Version

Pico 11.1
SRAN11.1
0x020c RESET RESPONSE X2
Pico 11.1
ENB SRAN11.1
0x020d CONFIGURATION X2
UPDATE Pico 11.1

ENB
CONFIGURATION SRAN11.1
0x020e X2
UPDATE Pico 11.1
ACKNOWLEDGE
ENB SRAN11.1
0x020f CONFIGURATION X2
UPDATE FAILURE Pico 11.1

RESOURCE SRAN11.1
0x0210 X2
STATUS REQUEST Pico 11.1
RESOURCE SRAN11.1
0x0211 STATUS X2
RESPONSE Pico 11.1

RESOURCE SRAN11.1
0x0212 X2
STATUS FAILURE Pico 11.1

RESOURCE SRAN11.1
0x0213 X2
STATUS UPDATE Pico 11.1
MOBILITY SRAN11.1
0x0214 CHANGE X2
REQUEST Pico 11.1

MOBILITY SRAN11.1
0x0215 CHANGE X2
ACKNOWLEDGE Pico 11.1

MOBILITY SRAN11.1
0x0216 CHANGE X2
FAILURE Pico 11.1

SRAN11.1
0x0217 RLF INDICATION X2
Pico 11.1

HANDOVER SRAN11.1
0x0218 X2
REPORT Pico 11.1
CELL
0x0219 ACTIVATION X2 SRAN11.1
REQUEST
0x021a CELL X2 SRAN11.1
ACTIVATION

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 71

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide AppendixAppendix

Event ID Event Name Interface Initial NE Version

RESPONSE
CELL
0x021b ACTIVATION X2 SRAN11.1
FAILURE
RETRIEVE UE
0x0221 CONTEXT X2 SRAN12.1
REQUEST
RETRIEVE UE
0x0222 CONTEXT X2 SRAN12.1
RESPONSE
RETRIEVE UE
0x0223 CONTEXT X2 SRAN12.1
FAILURE
CSFBParametersRe
0x0300 Uu SRAN11.1
questCDMA2000
CSFBParametersRes
0x0301 Uu SRAN11.1
ponseCDMA2000
SRAN11.1
0x0302 CounterCheck Uu
Pico 11.1

CounterCheckRespo SRAN11.1
0x0303 Uu
nse Pico 11.1

DLInformationTrans SRAN11.1
0x0304 Uu
fer Pico 11.1
HandoverFromEUT
0x0305 RAPreparationRequ Uu SRAN11.1
est (CDMA2000)
MasterInformationB
0x0306 Uu SRAN11.1
lock
SRAN11.1
0x0307 MeasurementReport Uu
Pico 11.1

MobilityFromEUTR SRAN11.1
0x0308 Uu
ACommand Pico 11.1

RRCConnectionRec SRAN11.1
0x030a Uu
onfiguration Pico 11.1
RRCConnectionRec SRAN11.1
0x030b onfigurationComplet Uu
e Pico 11.1

RRCConnectionRee SRAN11.1
0x030c Uu
stablishment Pico 11.1

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 72

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide AppendixAppendix

Event ID Event Name Interface Initial NE Version

RRCConnectionRee SRAN11.1
0x030d stablishmentComple Uu
te Pico 11.1

RRCConnectionRee SRAN11.1
0x030e Uu
stablishmentReject Pico 11.1

RRCConnectionRee SRAN11.1
0x030f Uu
stablishmentRequest Pico 11.1

RRCConnectionRej SRAN11.1
0x0310 Uu
ect Pico 11.1

RRCConnectionRel SRAN11.1
0x0311 Uu
ease Pico 11.1

RRCConnectionReq SRAN11.1
0x0312 Uu
uest Pico 11.1

RRCConnectionSetu SRAN11.1
0x0313 Uu
p Pico 11.1

RRCConnectionSetu SRAN11.1
0x0314 Uu
pComplete Pico 11.1

SecurityModeComm SRAN11.1
0x0315 Uu
and Pico 11.1

SecurityModeCompl SRAN11.1
0x0316 Uu
ete Pico 11.1

SecurityModeFailur SRAN11.1
0x0317 Uu
e Pico 11.1

UECapabilityEnquir SRAN11.1
0x031a Uu
y Pico 11.1

UECapabilityInform SRAN11.1
0x031b Uu
ation Pico 11.1
ULHandoverPrepara
0x031c tionTransfer Uu SRAN11.1
(CDMA2000)

ULInformationTrans SRAN11.1
0x031d Uu
fer Pico 11.1

UEInformationRequ SRAN11.1
0x0324 Uu
est Pico 11.1

UEInformationResp SRAN11.1
0x0325 Uu
onse Pico 11.1

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 73

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide AppendixAppendix

Event ID Event Name Interface Initial NE Version

LoggedMeasuremen
0x0327 Uu SRAN11.1
tsConfiguration
MBSFNAreaConfig
0x032c Uu SRAN11.1
uration
RRCConnectionRec
0x0351 Uu SRAN12.1
onfiguration-NB
RRCConnectionRec
0x0352 onfigurationComplet Uu SRAN12.1
e-NB
RRCConnectionRee
0x0353 Uu SRAN12.1
stablishment-NB
RRCConnectionRee
0x0354 stablishmentComple Uu SRAN12.1
te-NB
RRCConnectionRee
0x0355 stablishmentRequest Uu SRAN12.1
-NB
RRCConnectionRej
0x0356 Uu SRAN12.1
ect-NB
RRCConnectionRel
0x0357 Uu SRAN12.1
ease-NB
RRCConnectionReq
0x0358 Uu SRAN12.1
uest-NB
RRCConnectionSetu
0x0359 Uu SRAN12.1
p-NB
RRCConnectionSetu
0x035A Uu SRAN12.1
pComplete-NB
RRCConnectionRes
0x035B Uu SRAN12.1
ume-NB
RRCConnectionRes
0x035C Uu SRAN12.1
umeComplete-NB
RRCConnectionRes
0x035D Uu SRAN12.1
umeRequest-NB
UECapabilityEnquir
0x035E Uu SRAN12.1
y-NB
UECapabilityInform
0x035F Uu SRAN12.1
ation-NB
ULInformationTrans
0x0360 Uu SRAN12.1
fer-NB
0x0361 DLInformationTrans Uu SRAN12.1

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 74

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server LTE Standard Signaling Northbound File
Interface Developer Guide AppendixAppendix

Event ID Event Name Interface Initial NE Version

fer-NB
SRAN11.1
0x1211 UE Period TA -
Pico 11.1
0x1212 UE Period TA MDT - SRAN11.1

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 75

Huawei 9947 MML Command Reference
100% (3)
Huawei 9947 MML Command Reference
8,055 pages
Genex Discovery Tutorial
100% (2)
Genex Discovery Tutorial
60 pages
Procedure For MDT Log Huawei LTE Collection
0% (1)
Procedure For MDT Log Huawei LTE Collection
10 pages
IP Active Performance Measurement (SRAN18.1 - Draft A)
No ratings yet
IP Active Performance Measurement (SRAN18.1 - Draft A)
59 pages
U2000 Trace Server Lte MDT Data Northbound File Interface Developer Guid Compress
No ratings yet
U2000 Trace Server Lte MDT Data Northbound File Interface Developer Guid Compress
102 pages
U2020 Northbound CORBA Interface Developer Guide PDF
50% (2)
U2020 Northbound CORBA Interface Developer Guide PDF
185 pages
LTE CCO Feature Description - RF Based (V100R015C00 - 01) (PDF) - en
No ratings yet
LTE CCO Feature Description - RF Based (V100R015C00 - 01) (PDF) - en
87 pages
Specifications For The IManager U2000 Northbound Interface 07 (20170808)
No ratings yet
Specifications For The IManager U2000 Northbound Interface 07 (20170808)
23 pages
GENEX Discovery V200R002C50 Feature Description 02-En
100% (1)
GENEX Discovery V200R002C50 Feature Description 02-En
160 pages
Northbound Data Export Guide (UMTS CHR Standard Signaling)
100% (1)
Northbound Data Export Guide (UMTS CHR Standard Signaling)
37 pages
Trace Server Parameter Settings
No ratings yet
Trace Server Parameter Settings
5 pages
LTE E2E Trace Guide
50% (2)
LTE E2E Trace Guide
13 pages
RAN Troubleshooting Guide (01) (PDF) - EN PDF
0% (1)
RAN Troubleshooting Guide (01) (PDF) - EN PDF
193 pages
Om MML Ref Nastar
100% (1)
Om MML Ref Nastar
71 pages
ariesoGEO Data Collection Setup - Huawei UMTS PDF
No ratings yet
ariesoGEO Data Collection Setup - Huawei UMTS PDF
10 pages
LTE Network Planning - Huawei Technologies
No ratings yet
LTE Network Planning - Huawei Technologies
54 pages
OMStar V500R011 LTE Data Collection Guide
No ratings yet
OMStar V500R011 LTE Data Collection Guide
100 pages
FMA (SRAN16.1 - Draft A)
No ratings yet
FMA (SRAN16.1 - Draft A)
91 pages
Neighbor Audit With OMStar
No ratings yet
Neighbor Audit With OMStar
8 pages
GENEX Discovery V200R005C00 Geo-Location Technical Paper-Draft B en
No ratings yet
GENEX Discovery V200R005C00 Geo-Location Technical Paper-Draft B en
34 pages
Intra-RAT Mobility Management in Connected Mode (ERAN8.1 - 04)
100% (2)
Intra-RAT Mobility Management in Connected Mode (ERAN8.1 - 04)
383 pages
Layer 3 Messages GSM
100% (2)
Layer 3 Messages GSM
15 pages
Adaptive Intra-LTE Load Balancing
No ratings yet
Adaptive Intra-LTE Load Balancing
7 pages
03 GUL Interoperability Troubleshooting (Drive Test) V1.0
100% (1)
03 GUL Interoperability Troubleshooting (Drive Test) V1.0
34 pages
Capacity Monitoring Guide BSC6910-Based
100% (1)
Capacity Monitoring Guide BSC6910-Based
147 pages
Capacity Monitoring Guide: Issue 01 Date 2016-03-07
No ratings yet
Capacity Monitoring Guide: Issue 01 Date 2016-03-07
50 pages
Huawei IManager SONMaster Solution
100% (5)
Huawei IManager SONMaster Solution
26 pages
2 Application of LTE SON in MAE V100R021
No ratings yet
2 Application of LTE SON in MAE V100R021
74 pages
LTE FDD Test Guideline1
No ratings yet
LTE FDD Test Guideline1
48 pages
Performance Management (SRAN13.1 - 01)
No ratings yet
Performance Management (SRAN13.1 - 01)
29 pages
Basic LTE
100% (1)
Basic LTE
27 pages
ENodeB Configuration SW Commissioning and Alarm Minitoring Guide
No ratings yet
ENodeB Configuration SW Commissioning and Alarm Minitoring Guide
77 pages
OEB537110 LTE ERAN15.1 VoLTE Service Activation and Data Configuration
No ratings yet
OEB537110 LTE ERAN15.1 VoLTE Service Activation and Data Configuration
123 pages
VoLTE Key Configuration Check
No ratings yet
VoLTE Key Configuration Check
214 pages
2 - LTE System Signaling Procedures-20110525-A-1.0
No ratings yet
2 - LTE System Signaling Procedures-20110525-A-1.0
60 pages
Introduction To Huawei GENEX Nastar RAN WCDMA-20070827
No ratings yet
Introduction To Huawei GENEX Nastar RAN WCDMA-20070827
25 pages
5 GSM Radio Network Planning and Optimization - Influence Factors + Troubleshooting Methods and Tools + Deliverables 20121031
No ratings yet
5 GSM Radio Network Planning and Optimization - Influence Factors + Troubleshooting Methods and Tools + Deliverables 20121031
285 pages
Adaptive SFN
No ratings yet
Adaptive SFN
47 pages
SRAN15.0 NR UL and DL Decoupling&LTE FDD and NR Uplink Spectrum Sharing Delivery Guide v0.1
No ratings yet
SRAN15.0 NR UL and DL Decoupling&LTE FDD and NR Uplink Spectrum Sharing Delivery Guide v0.1
73 pages
Huawei Insight of LTE
100% (2)
Huawei Insight of LTE
26 pages
Interoperability Between UMTS and LTE (RAN19.0 - 01) PDF
No ratings yet
Interoperability Between UMTS and LTE (RAN19.0 - 01) PDF
1,393 pages
GSM Mos
No ratings yet
GSM Mos
27 pages
LTE RF Channel Troubleshooting Guide - v1.1
50% (4)
LTE RF Channel Troubleshooting Guide - v1.1
36 pages
Huawei LAC RAC Splitting
No ratings yet
Huawei LAC RAC Splitting
42 pages
MDT Feature Parameter Description: Issue Date
No ratings yet
MDT Feature Parameter Description: Issue Date
28 pages
SmartCare SEQ Analyst V200R001C02 For The LTE
100% (1)
SmartCare SEQ Analyst V200R001C02 For The LTE
22 pages
BNR Intra Lte LM
No ratings yet
BNR Intra Lte LM
23 pages
MAE Optimization MML Command and Parameter Reference
No ratings yet
MAE Optimization MML Command and Parameter Reference
633 pages
LTE KPI Introduction
No ratings yet
LTE KPI Introduction
95 pages
1 - VoLTE KQI Analysis and Optimization ISSUE8.00
100% (1)
1 - VoLTE KQI Analysis and Optimization ISSUE8.00
100 pages
HUAWEI GENEX Discovery PS Collector Configuration Guide V2.0
No ratings yet
HUAWEI GENEX Discovery PS Collector Configuration Guide V2.0
12 pages
Huawei Lte FDD&TDD Integration
No ratings yet
Huawei Lte FDD&TDD Integration
6 pages
Huawei 3g Parameters
100% (2)
Huawei 3g Parameters
201 pages
Diameter Protocol A Complete Guide
From Everand
Diameter Protocol A Complete Guide
Gerardus Blokdyk
No ratings yet
Drive testing The Ultimate Step-By-Step Guide
From Everand
Drive testing The Ultimate Step-By-Step Guide
Gerardus Blokdyk
No ratings yet
U2000 Trace Server All The Northbound Trace Result File Interface Developer Guide
No ratings yet
U2000 Trace Server All The Northbound Trace Result File Interface Developer Guide
344 pages
Huawi
No ratings yet
Huawi
26 pages
U2000 Northbound Performance File Interface Developer Guide (NE-Based)
No ratings yet
U2000 Northbound Performance File Interface Developer Guide (NE-Based)
79 pages
U2000 Northbound Alarm Streaming Interface Developer Guide
No ratings yet
U2000 Northbound Alarm Streaming Interface Developer Guide
79 pages
U2000 Northbound Inventory File Interface Developer Guide
No ratings yet
U2000 Northbound Inventory File Interface Developer Guide
61 pages
RSA Public-Key Encryption and Signature Lab
No ratings yet
RSA Public-Key Encryption and Signature Lab
8 pages
02-A CDR Farmat
No ratings yet
02-A CDR Farmat
232 pages
Acronyms A4 Duplex
No ratings yet
Acronyms A4 Duplex
174 pages
U16sss Inap PM
No ratings yet
U16sss Inap PM
300 pages
Openssl Man
No ratings yet
Openssl Man
467 pages
IEC 61850 Reporting and Deadband Explanation
100% (1)
IEC 61850 Reporting and Deadband Explanation
2 pages
ASN.1 Today and Tomorrow
No ratings yet
ASN.1 Today and Tomorrow
18 pages
As ISO 13584.24-2004 Industrial Automation Systems and Integration - Parts Library Logical Resource - Logical
No ratings yet
As ISO 13584.24-2004 Industrial Automation Systems and Integration - Parts Library Logical Resource - Logical
24 pages
BSR 2000 - Release 1.1 - SNMP Configuration and Management Guide
No ratings yet
BSR 2000 - Release 1.1 - SNMP Configuration and Management Guide
62 pages
ITU-T Security Standard Activities PDF
No ratings yet
ITU-T Security Standard Activities PDF
95 pages
TCAP
No ratings yet
TCAP
3 pages
Simple Network Management Protocol (SNMP)
100% (1)
Simple Network Management Protocol (SNMP)
32 pages
Itu-T: Procedures For Real-Time Group 3 Facsimile Communication Over IP Networks
No ratings yet
Itu-T: Procedures For Real-Time Group 3 Facsimile Communication Over IP Networks
124 pages
The Emergence of ASN.1 As An XML Schema Notation
No ratings yet
The Emergence of ASN.1 As An XML Schema Notation
48 pages
SS.7 As An Agent Platform Message Transport Protocol
No ratings yet
SS.7 As An Agent Platform Message Transport Protocol
14 pages
Vtu 8TH Sem Cse Network Management Systems Notes 10CS834
100% (4)
Vtu 8TH Sem Cse Network Management Systems Notes 10CS834
57 pages
The Testing and Test Control Notation: Curriculum
No ratings yet
The Testing and Test Control Notation: Curriculum
28 pages
Etsi Ttcn3 Tutorial
No ratings yet
Etsi Ttcn3 Tutorial
32 pages
Complete Computer Acronyms
No ratings yet
Complete Computer Acronyms
161 pages
Asn 1
No ratings yet
Asn 1
25 pages
X 509
No ratings yet
X 509
254 pages
Ai 420 MMS
No ratings yet
Ai 420 MMS
37 pages
Euro ISDN Protocol EDSS1
No ratings yet
Euro ISDN Protocol EDSS1
106 pages
Multiple Choice Questions With Answers On Network Management Systems
89% (9)
Multiple Choice Questions With Answers On Network Management Systems
78 pages
CourseOutline - INSE 7120
No ratings yet
CourseOutline - INSE 7120
3 pages
Uml 2.0
No ratings yet
Uml 2.0
50 pages
ISA-50.02 Part 5-1998
No ratings yet
ISA-50.02 Part 5-1998
234 pages
Asn1 Ber
No ratings yet
Asn1 Ber
27 pages
ASN.1 Summary
No ratings yet
ASN.1 Summary
8 pages
IT140 FINAL EXAM Questions
No ratings yet
IT140 FINAL EXAM Questions
3 pages