Technical Poster

U2000 Northbound Interface Series

Performance File Interface (NE-based)
01 Why Is the Northbound
Performance File Interface Required?

Interface Position/Function Overview

NMS
10 NMSs can

concurrently
obtain files at
most.
NMS1 NMS9 NMS10

Obtain Automatically upload

performance files. performance files.

U2000 Before After

starting a performance data starting a
export task performance data export task

Performance file
interface XFTPService

The engineer Obtain

(Optional) Configure
configures performances file
a task for
task parameters from the directory.
automatically
and starts an uploading exported
export task. files. Directory for saving performance files:
/opt/oss/server/var/fileint/

Generate NE
OSMU U2000 Client performance data Generate OSS
files according to performance data
URL address for logging in to the OSMU: files and save them
the settings and
https://U2000 IP:31123 in the specified
save them in the
Portal for configuring task parameters: specified directory. directory.
NBI Management >
Centralized Management >
Mediation
Northbound Configuration PMService
Parameters Settings Service
Configuration files:
MedExpParm.xml-Basic Obtain OSS
MedExpParm.xml-Advanced performance
tbl-MedExportMeas data files from
the database.

Performance database

Upload NE
performance
data.

NE

Note The NMS obtains files from the U2000, or the U2000 automatically uploads files to the NMS.
Either method can be used.

Function Details

Customize Customize the Customize the Customize the Customize the

filtering policies. export period. export path. file compression storage days.
Supports mode.
customizing Supports Supports Supports Supports setting
counter filtering customizing customizing the setting whether the storage days
policies: full the counter path for saving to compress of exported files.
counter export measurement exported files. exported files By default,
or export of only period being in .gz format. exported files are
counter being used on the saved for seven
measured on the client. days.
client.

Configuration method
Configuration file:
/opt/oss/server/etc/MediationService/MedExpParam.xml
Configuration method

Customize the counter Customize the Customize the file Customize the
display mode. deletion time. name. separator.
Supports Customize the fields Supports customizing
Supports setting the
configuration to and field order in the whether a space or
time to delete
enable counters in name of an exported semicolon is used to
expired files in each
the exported file to file. separate a counter
day.
be displayed by name and counter
counter name (in value.
alphabetic order) or
by counter ID (in
ascending order).

Description of an Exported File

Default path for saving exported files:
/opt/oss/server/var/fileint/pmneexport|ebcneexport/[NeTypeDir]/neexport_yyyymmdd/neName

*pmneexport|ebcneexport: By default, pmneexport is used. If event-based counter is performance results are

exported, ebcneexport is used.
*NeTypeDir: It needs to be configured in the MedExpParam.xml file.

Default naming conventions of exported files

<Type><Startdate>.<Starttime>-<Endtime>_<UniqueId>[_-_<RC>][_P<i>].xml

*Type: A indicates that the data of an NE in a measurement period is exported. E indicates the event-based
counter results of an NE in a measurement period are exported.
*Startdate: indicates the start date of a measurement period. The format is YYYYMMDD.
*Starttime: indicates the start time of a measurement period. The format is HHMMshhmm,where s is the
time difference identifier (+/).
*Endtime: indicates the end time of a measurement period. The format is the same as that of Starttime.
*UniqueId: uniquely identify an NE. For NEs rather than NodeBs, the value is an NE name and ID. For
NodeBs, the value is in the format of RNC name_NodeB name.
*-_<RC>: is the identifier for a re-collected file. It exists only in the name of a re-collected file.
*P<i>: is the file splitting identifier. If the following two conditions are met, the exported file is
automatically split. The value of i increases from 001.
1.The NE type is BSC6910GSMNE, BSC6910GUNE, or BSC6910UMTSNE.
2.The size of raw performance results reported by an NE is greater than the preset threshold of the
performance result file size.

Introduction to the format of an exported file

The following is an example of an exported file:

<fileHeader fileFormatVersion="32.435 V7.2" vendorName="Huawei">
fileSender elementType="eNodeB"/>
NE type
<measCollec beginTime="2014-12-08T23:45:00+08:00"/>
Start time of the first measurement period
</fileHeader>
<measData>
<managedElement userLabel="HRailway40"/>
NE name
<measInfo measInfoId="50331648">
ID of a measurement unit
<granPeriod duration="PT900S" endTime="2014-11-28T20:00:00+08:00"/>
Current measurement period Measurement end time
<repPeriod duration="PT900S"/>
Result reporting period
<measTypes>50331654 50331655 50331656 50331657</measTypes>
Measurement counter information. The values correspond to measurement results in measResults.
<measValue measObjLdn="10.144.48.83/ULoCell:NodeB ">
Name of a measured object
<measResults>0 0 0 0</measResults>
Measurement result. The values correspond to measurement counters in measTypes.
<suspect>true</suspect>
Result reliability flag
</measValue>

<measCollec endTime="2014-12-09T00:00:00+08:00"/>
End time of the last measurement period

02 How Does the NMS Interconnect to the

Performance File Interface?
STEP 1 Confirm that the licenses for the performance file interface have
been loaded on the U2000.

(Licenses in the figure are used as examples

only.)

STEP 2 Configure interconnecting information on the U2000 using the

OSMU.
The URL address of the OSMU is https://U2000 IP:31123/.
Portal for the configuration page: NBI Management > Centralized Management
> Northbound Configuration Parameters Settings
The following describes only mandatory parameters. For details about all
parameters, see U2000 Northbound Performance File Interface Developer
Guide (NE-Based).

exported file
d so rt order in an order.
Counter dis
pla y a n
r ID in ascending
display by co u n te betic order.
1: indicates co u n te r n a me in alpha
display by
0: indicates
orted file 0 client.
fi lte r m o de in an exp m e a su re d on the U200
Counte r ters being
nly the coun displayed.
1 indicates o a ll counters are
te s th a t
0 indica be saved
ic h e x p o rted files can
wh
Days during
orted file
u n te r n a m es in an exp
co
etween the
Separator b
pressed
p o rt e d files are com mpressed.
Whethe r e x
fi les are not co format.
at e x p o rte d ressed in .gz
0 indicates th exported files are comp
at
1 indicates th
ed file
th e n a m e of an export
Fields in

files
in each day. Expired
e to d e le te expired files
e tim
Indicates th :0 0+DelDelay
Time.
te d a t 0 0
are dele

e NE type.
d (minute ) based on th
export perio
ormance file
Set the perf

STEP 3 Configure a task for automatically uploading exported files to

the NMS on the U2000.
The U2000 supports automatically uploading exported files to the NMS
using the SFPT service. Connections between the U2000 and NMS can be
set up using either of the following methods:

Password authentication
Public and private key authentication

For details about the configuration method, see Configuring the SFTP for
Actively Transferring Files over the Northbound Interface (Public and
Private Keys) or Configuring the SFTP for Actively Transferring Files over the
Northbound Interface (Password Authentication) in U2000 Northbound
Performance File Interface Developer Guide (NE-Based).

STEP 4 Verify whether performance files can be properly exported on the

OSMU.
Portal for the verification page: NBI Management > Category Management >
File Interface > Performance File (NE-Based) Interface

Click a performance file name,

save the file to a local PC, and
check counters are correct in
the file.

For details, see

U2000 Northbound Performance File Interface Developer
Guide (NE-Based).

Contact Huawei engineers to obtain the preceding

document at http://support.huawei.com.

Copyright Huawei Technologies Co., Ltd.