ariesoGEO

Huawei UMTS Data Collection Setup Guide

 Notice
Every effort was made to ensure that the information in this manual was accurate at the time of printing.
However, information is subject to change without notice, and Viavi reserves the right to provide an
addendum to this manual with information not available at the time that this manual was created.

Copyright
© Copyright 16 November 2016 Viavi Solutions Inc. All rights reserved. Viavi and the Viavi logo are
trademarks of Viavi Solutions Inc. (“Viavi”). All other trademarks and registered trademarks are the property
of their respective owners. No part of this guide may be reproduced or transmitted, electronically or
otherwise, without written permission of the publisher.

Copyright release
Reproduction and distribution of this guide is authorized for US Government purposes only.

Trademarks
VIAVI and GEOperformance are trademarks or registered trademarks of VIAVI in the United States and/or
other countries.

Microsoft, Windows, Windows Server, and Microsoft Internet Explorer are either trademarks or registered
trademarks of Microsoft Corporation in the United States and/or other countries.

SQL is a trademark or registered trademark of IBM.

Specifications, terms, and conditions are subject to change without notice. All trademarks and registered
trademarks are the property of their respective companies.

Terms and conditions

Specifications, terms, and conditions are subject to change without notice. The provision of hardware,
services, and/or software are subject to Viavi’s standard terms and conditions, available at
www.viavisolutions.com/terms.

Confidential Viavi Solutions Inc. Page 2

 1
Contents
1. Introduction ......................................................................................................................................................... 4
2. Huawei Call trace Collection Guidelines ......................................................................................................... 5
2.1 Overview ................................................................................................................................... 5

2.2 Huawei Data Collection ............................................................................................................. 5

3. Resource Requirements .................................................................................................................................... 6

4. Huawei System Configuration Guide .............................................................................................................. 6
4.1 Legacy UMTS Call Trace Capture (NASTAR Architecture)........................................................ 7

4.1.1 Nastar UMTS Call Trace Collection 7

4.1.2 Subscribing to Northbound data 8

4.1.3 Obtaining Northbound data 8

4.1.4 Location of the Northbound data 9

4.2 New UMTS Call Trace Capture (U2000 Architecture) ................................................................ 9

4.2.1 Procedure to collect Trace Server CHR Files 10

4.2.2 Trace Server CHR Files Content 10

Confidential Viavi Solutions Inc. Page 3

1. Introduction
This document describes the requirements for data collection from the relevant network sources in order to
use ariesoGEO. The document is a practical guide for the ariesoGEO Administrator users, whether internal or
external to Viavi, and outlines the areas that attention should be paid to. These areas include the:

 Network event / messages of interest

 Guidelines for data collection

 File size considerations

 Network configuration files and information

 Troubleshooting.

Confidential Viavi Solutions Inc. Page 4

2. Huawei Call trace Collection Guidelines

2.1 Overview
Huawei CHR Trace information from the network should be setup to run 24 hours a day and continually
through the entire collection period without any gaps and covering 100% of the calls on all collected
eNodeBs.

It is suggested that regular dumps of the collected data are taken for processing in the ariesoGEO
solution to ensure that data continues to be collected correctly. The customer will handle the data
collection with the support of Viavi and Huawei engineers.

2.2 Huawei Data Collection

Huawei are currently migrating away for their historical call trace collection procedures in favour of a
single point of collection for all technologies. As can be seen from the image below, traditionally the data
collection of call trace files (GSM and UMTS) has been through the Nastar server, and these call traces
were enabled via the OSS (M2000 Trace Server). For the new call trace however, Hauwei collect and
enable through a call trace server within the U2000. This latter technique is now being rolled out as the
preferred mechanism for the legacy technology i.e. GSM and UMTS.

With Huawei new call trace strategy all the call trace files are collected and enabled through the call trace
module called Trace Server. This can be deployed in one of two modes – a standalone deployment or as
a co-deployment with the U2000 (the latest version of the M2000). The Hardware requirements of the
Trace Server vary depending on the amount of call data on a network.

Confidential Viavi Solutions Inc. Page 5

2.3 Huawei Trace Features Required
The trace features that are required on Huawei infrastructure are identified below. Note that specific
licensing of these features may differ between operators.

 Call flow trace Northbound Interface (GSM Only)

 Post-process MR Northbound Interface (Not currently required – Future maybe)

 Throughput statistics Northbound Interface (UMTS and LTE)

 Standard trace Northbound Interface (GSM, UMTS and LTE)

 MDT trace Northbound Interface (Minimum Drive Test - Not currently required – Future maybe)

Example:

Below are the Huawei UMTS call trace part numbers used by an operator:

Huawei Part Number Description

WM1SCFTDFU00 Call flow trace data BIN file interface – WRAN (per Cell)

WM1SPPMDFU00 Post-process MR data BIN file interface – WRAN (per Cell)

WM1STPSDFU00 Throughput statistics data BIN file interface – WRAN (per Cell)

WM1SSTDFIU00 Standard trace data BIN file interface - WRAN (per Cell)

3. Resource Requirements
Facilitate the provision of Huawei data for each RNC.

Collection & delivery of requisite Huawei CHR data

Data dumps from radio planning tool for network configurations at times during the collection period

4. Huawei System Configuration Guide

The purpose of this chapter is just to guide the reader how to configure the parameters which are related
to the deployment of this feature.

Huawei Operation
Description
unit
This serves as a fundamental support platform for the collection enablement
Nastar
entity.

Confidential Viavi Solutions Inc. Page 6

 This is a data summarization unit and a mandatory component of the Nastar
eSAU system. The eSAU receives northbound CHR data from the SAU and saves
the data during data export over the northbound interface.

This is Huawei’s OSS platform for the management of their Network element.
U2000 During the northbound data export process, the U2000 provides the relay
function for commands and data.
This is an optional component of the Nastar system. The SAU is installed on
the base station controller (BSC) as the board, such as SAUc, and
SAU (Service
preprocesses the raw data from NEs as required by the Nastar system for
aware unit)
analysis. During the northbound data export process, the SAU preprocesses
the data collected from the BSC and upload the data to the eSAU.

4.1 Legacy UMTS Call Trace Capture (NASTAR Architecture)

Nastar versions from 10 and above is believed to provide the optimum level of data richness across both
2G and 3G networks, and therefore allows GEOperformance to provide the most sophisticated level of
analysis.

Nastar requires the addition of a SAU card into the RNC. This overcomes the architectural limitations of
the RAN O&M and provides complete call information for the whole of all calls, including RF
measurements. This enables the full power of GEOperformance to be realised.

Customer
data
and parse the
specified path
from the
(7) Obtain data

client
RNC

(4) Preprocess CHR data

(3) Deliver the data task
transparently (2) Deliver a data (1) Create a data
SAU collection task export task

(5) Upload the

(6) Collect data from
preprocessed data M2000 Nastar Nastar client
the M2000 server
to the M2000 server

In addition to the SAU card, a NASTAR server and software is required. The NASTAR server is
responsible for managing the upload of data from the SAU card and does not carry out any data
processing. Only the UMTS CHR northbound Data Export feature are required out of the wider set of
Nastar capabilities.

4.1.1 Nastar UMTS Call Trace Collection

Two aspects to the collecton of call trace messages:

 Subscribing to the Northbound data

 Obtaining the Northbound data

Confidential Viavi Solutions Inc. Page 7

4.1.2 Subscribing to Northbound data
To subscribe to the Nastar northbound data you must log into a Nastar client and access the Data
Subscription Management menu from the Maintenance view. From within this menu, select the Basic
Subscription Setting Tab and select the required Network Elements from the UMTS navigation tree.

From the Advanced Parameters Type Setting dialogue box, back in the maintenance view, under the All
Signaling Drop Down menu select the “select all” box. This ensures that all interface messages, such as
Uu, Iu, and etc. interface messages are collected.

4.1.3 Obtaining Northbound data

To subscribe to the northbound data, the users will need access the CHR Standard Signaling Northbound
Data tab, selecting the Network elements from the UMTS navigation tree. Once the Network Elements
have been selected you will need to select the relevant parameters from the Parameter Settings dialog
box within the on the CHR Standard Signaling Northbound Data tab page. Modify the parameters for
time setting, busy hours and storage position as required.

Confidential Viavi Solutions Inc. Page 8

 After the setting is complete, customize the standard signaling message type to be exported.

4.1.4 Location of the Northbound data

To access the data folders where the Northbound data is stored the user will need to have a user name
and password created. (During the installation of the eSAU server software, user northuser is
automatically created in the system, with default password Changeme_123.)

For details about password-related problems, contact Huawei technical support.

The format of data storage directory:

 /export/home/northdata/UCHRStdSignal/[NeName], in which [NeName] indicates the RNC name.

For example, /export/home/northdata/UCHRStdSignal/RNC16.

The naming convention of the data file can be either of the two formats:

1. RNC%RNCID%_[%PCHR%]%SubrackNo%Log%StartTime%_%EndTime%.log.zip.dat.

2. RNC%RNCID%_[%FILETYPE%]%SubrackNo%SN%SPU_NO%Log%StartTime(DST)%_%EndT
ime(DST)%_%Index%.log.zip.dat

If the data file has been compressed, the file name extension is .gz.

4.2 U2000 UMTS Call Trace Capture (U2000 Architecture)

The U2000 architecture for collection of call trace is through the Huawei Trace Server.

TS U2000 TS Restrictions
Networking Server Server
Mode Model Model
ATAE Sun ATAE In M2000 V200R013 and U2000 V200R014, only one TS board
cluster, can be deployed in the TS independent cluster.
standalone
In U2000 V200R015, multiple TS boards can be deployed in the
TS independent cluster. A maximum of 22 TS boards and one
standby board are supported.

Standalone Sun PC The TS deployed on the PC Server supports only the standard
Server CHR signaling data northbound interface for the LTE system.

ATAE ATAE ATAE In M2000 V200R013, only one TS board can be deployed with the
cluster, co- M2000 in the same ATAE cluster system.
deployed
with the In U2000 V200R014 and later, multiple TS boards can be
U2000 deployed with the U2000 in the same ATAE cluster system. A
maximum of 7 TS boards are supported, and the TS shares the
standby board with the U2000.

Confidential Viavi Solutions Inc. Page 9

4.2.1 Procedure to collect Trace Server CHR Files
The call trace data interface can automatically export as files and save the files to a specified directory for
any external system to access via a FTP or SFTP process. The Files are in a binary format.

4.2.2 Trace Server CHR Files Content

It is understood that the UMTS data source from the Trace Server, has changed to be more aligned to
other vendors where the call is presented as a series of events across multiple files. UMTS NEs
generate standard CHR signalling event data, which complies with the following 3GPP specifications:

 Iu interface: TS 25.413

 Iur interface: TS 5.423

 Iub interface: TS 25.433

 Uu interface: TS 25.331

4.2.3 Trace Server Trace Files Location

The U2000 Trace Server will provide the files generated for Huawei’s ‘Standard Signalling’ with the
location and name format based on the following:

Path /export/home/omc/var/fileint/TSNBI/UMTS_STD/ yyyymmdd/NEFDN/

For example:

If a UMTS_STDM result file is generated on May 11, 2014, and the NEFDN is NE=256, the
/export/home/omc/var/fileint/TSNBI/UMTS_STDM/20140511/NE256/ directory is automatically created
for saving all UMTS_STDM result files that were generated on May 11, 2014.

Filename UMTS_STDM result file: <NEFDN>_<No>_<StartTime>_<EndTime>_<SN>.<FilePostfix>.gz

For example:

NE256_020058_20140511173030_20140511173240_1234.sig.gz

WARNING: The U2000 Trace Server uses NEFDN Identities (Network Element Full Distinguished Name)
in the filename to identify the network element. Care must be taken to ensure the correct RNC name is
used for ftptransfer.exe configurations. This can be checked by examining the CM Bulk XML for the
RNC.

Confidential Viavi Solutions Inc. Page 10