Documente Academic
Documente Profesional
Documente Cultură
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.
Specifications, terms, and conditions are subject to change without notice. All trademarks and registered
trademarks are the property of their respective companies.
Troubleshooting.
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.
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.
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:
WM1SCFTDFU00 Call flow trace 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.
Data dumps from radio planning tool for network configurations at times during the collection period
Huawei Operation
Description
unit
This serves as a fundamental support platform for the collection enablement
Nastar
entity.
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.
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
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.
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.
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.
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.
Iu interface: TS 25.413
Uu interface: TS 25.331
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.
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.