Professional Documents
Culture Documents
OMStar V5R14C10U3 UMTS Data Collection Guide
OMStar V5R14C10U3 UMTS Data Collection Guide
V5R14C10U3
UMTS Data Collection Guide
Issue 01
Date 2017-09-19
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.
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue 01(2017-04-05)
This issue is used for first office application (FOA).
OMStarV5R14C10U3
UMTS Data Collection Guide Contents
Contents
NE Type Data
RTWP
EGBTS Configuration data
Performance data
eNodeB Configuration data
Performance data (original, U2000, or PRS
performance data)
Alarm logs
MML reports
CHR
CellRic data (including reverse spectrum CHR data)
SIG data
Signaling logs
FaultLog
LTE BrdLog
No 2.2.10NodeB Configuration
NodeB Data Collection
OMStarV5R14C10U3
UMTS Data Collection Guide 1 OMStar Data Source Overview
configuration data
No 2.2.16BSC/RNC
Property data Performance Data Collection
(U2000)
MR data Yes 2.2.5RNC CHR/MR Data
Collection
OMU PCHR Yes 2.2.5RNC CHR/MR Data
Collection
No 2.2.18Terminal Library Data
Terminal Collection
information
No 2.2.16BSC/RNC
Property data Performance Data Collection
(U2000)
MR data Yes 2.2.5RNC CHR/MR Data
Collection
PCHR data No 2.2.5RNC CHR/MR Data
Collection
UMTS Coverage Configuration data Yes 2.2.1BSC/RNC
Analysis Configuration Data
Collection
MR Data Yes 2.2.5RNC CHR/MR Data
Collection
UMTS Traffic Configuration data Yes 2.2.1BSC/RNC
Forecast Configuration Data
Collection
Performance data Yes(one of the 2.2.2RNC Performance Data
two types) Collection
U2000 Performance 2.2.16BSC/RNC
data Performance Data Collection
(U2000)
CHR Data No 2.2.5RNC CHR/MR Data
Collection
No 2.2.18Terminal Library Data
Terminal data Collection
OMStarV5R14C10U3
UMTS Data Collection Guide 1 OMStar Data Source Overview
No 2.2.1BSC/RNC
GSM configuration Configuration Data
data Collection
No 2.2.9Engineering Parameter
GSM engineering Collection
parameter data
No 2.2.19eNodeB Configuration
LTE configuration Data Collection
data
No 2.2.9Engineering Parameter
LTE engineering Collection
parameter data
No 2.2.9Engineering Parameter
GSM engineering Collection
parameter data
No 2.2.10NodeB Configuration
NodeB Data Collection
configuration data
No 2.2.11NodeB Performance
NodeB Performance Data Collection (.mrf)
data
2.2.12NodeB Performance
Data Collection (.csv)
NodeB License data No 2.2.15NodeB License
Collection
UMTS Accurate Configuration data Yes 2.2.1BSC/RNC
Optimization RRC Configuration Data
Function Collection
No 2.2.9Engineering Parameter
Engineering Collection
parameter data
No 2.2.10NodeB Configuration
NodeB Data Collection
configuration data
No 2.2.11NodeB Performance
NodeB Performance Data Collection (.mrf)
data
2.2.12NodeB Performance
Data Collection (.csv)
NodeB License data No 2.2.15NodeB License
Collection
UMTS Accurate Configuration data Yes 2.2.1BSC/RNC
Optimization Configuration Data
Throughput Function Collection
No 2.2.9Engineering Parameter
Engineering Collection
parameter data
OMStarV5R14C10U3
UMTS Data Collection Guide 1 OMStar Data Source Overview
No 2.2.10NodeB Configuration
NodeB Data Collection
configuration data
No 2.2.11NodeB Performance
NodeB Performance
OMStarV5R14C10U3
UMTS Data Collection Guide 1 OMStar Data Source Overview
data
2.2.12NodeB Performance
Data Collection (.csv)
NodeB License data No 2.2.15NodeB License
Collection
UMTS Accurate Configuration data Yes 2.2.1BSC/RNC
Optimization Configuration Data
CallDrop Function Collection
No 2.2.9Engineering Parameter
Engineering Collection
parameter data
No 2.2.10NodeB Configuration
NodeB Data Collection
configuration data
No 2.2.11NodeB Performance
NodeB Performance Data Collection (.mrf)
data
2.2.12NodeB Performance
Data Collection (.csv)
NodeB License data No 2.2.15NodeB License
Collection
UMTS Config Configuration data Yes 2.2.1BSC/RNC
Parameters Check Configuration Data
Collection
UMTS Baseline Configuration data Yes 2.2.1BSC/RNC
Config Check Configuration Data
Collection
UMTS Multicarrier Configuration data Yes 2.2.1BSC/RNC
Parameter Check Configuration Data
Collection
OMStarV5R14C10U3
UMTS Data Collection Guide 1 OMStar Data Source Overview
No 2.2.9Engineering Parameter
Engineering Collection
parameter data
OMStarV5R14C10U3
UMTS Data Collection Guide 1 OMStar Data Source Overview
No
Increment Factor The data is generated by the
data traffic forecast feature on the
OMStar.
No 2.2.16BSC/RNC
Property data Performance Data Collection
(U2000)
UMTS Configuration data Yes 2.2.1BSC/RNC
Capacity Configuration Data
Evaluate Collection
Yes 2.2.9Engineering Parameter
Engineering Collection
parameter data
data
No 2.2.16BSC/RNC
Property data Performance Data Collection
(U2000)
No N/A
Map data
According to data sources required for themes to be analyzed, data collection must
comply with the principle of minimum range collection.
Data can only be used within the authorization scope and time limit. Data use must be
dedicated for a specified person, and records can be queried.
You are advised not to transmit raw network data out of networks of security sensitive
countries and to China.
After an analysis task is complete, yon need to immediately delete raw data and the
OMStar project. Saving raw data or backing up the database is not allowed. Delete the
project in the Project Manager window.
To protect user privacy, the OMStar displays scrambled personal data.
The OMStar can export or save analysis results. Export the analysis results of features
containing personal data with caution. Ensure that the exported analysis results are only
used for network problem analysis. By default, the OMStar exports scrambled analysis
results.
An example is described as follows: With MSISDN-based fuzzy search, users can obtain
8613612345678 and 13612345678 by entering 136. However, after being scrambled, the
preceding numbers might become E806AABCE0B44EC25128DB and
3698FD5BC48C1E36BEBE64 which have nothing in common.
Affected features are CHR browsing and signaling browsing.
Step 2 The Anonymous Policy Management window is displayed. Click Anonymous policy, select
Enable anonymous policy, and click OK to enable the anonymization function.
OMStarV5R14C10U3
UMTS Data Collection Guide 1 OMStar Data Source Overview
2 General Principles for Data Collection
Based on the onsite tool deployment situation, you can use the NIC tool to automatically or
manually collect data. You are advised to use the NIC tool for data collection. If the NIC tool
is not available, you can manually collect the data.
Description of the M2000 and U2000: The U2000 is the network management system on the
RAN side. In versions earlier than V200R014, it is called M2000. The product name M2000
is changed to U2000 from V200R015 and later. In this document, the operation on the U2000 is
used as an example. The operation on the M2000 is almost the same as that on the U2000. If the
operations on the U2000 and M2000 greatly differ, they are described separately in specific
chapters.
1. Task Management: Used to create a collection task (for selecting the collection scenario,
the NEs from which data is collected, and the time range of collection).
2. Scenario Management: Used to customize a collection scenario that the SOP collection is
unavailable (optional).
3. NE Management: In Co-Deployment Mode cannot create or delete an NE.
4. NE Mediation Version Information: Check the NE Mediation Version information on
U2000.
Step 3 Select Display by NE type. Select an RNC under the BSC6900 UMTS node in Optional
NEs, and move the selected RNC to Selected NEs. Then, click Next.
During routine inspection and maintenance SOP, you need to select only BSC/RNC. If
Display by Topo structure is selected, the BTSs/NodeBs under the selected BSC/RNC are
also selected when you select a BSC/RNC. As a result, the total number of NEs may exceed
the upper limit.
For R12 version and earlier, click each NE in the left pane, ensure that the parameter settings
of each NE are correct, and click Next.
Step 4 Set additional information such as Name and Email, and click Next.
Do not select Download collection results by NEs. Otherwise, the OMStar cannot identify
the downloaded packet.
Step 5 After ensuring that the collected information is correct, click Finish to start executing the
collection task.
Collecting GSM and UMTS Data
Step 1 Click the Task Management tab. Select Unfinished Tasks in the Navigation Tree, and select
Based on Scenario from the Create Task drop-down list box in Task List.
Step 6 Set Task Name, and select SingleRAN from the Product Type drop-down list box, and
select BSC6900GU_SOP from the Scenario(Group) drop-down list box.
For R12 version and earlier, click each NE in the left pane, ensure that the parameter settings
of each NE are correct, and click Next.
Step 9 Set additional information such as Name and Email, and click Next.
Do not select Download collection results by NEs. Otherwise, the OMStar cannot identify
the downloaded packet.
Step 10 After ensuring that the collected information is correct, click Finish to start executing the
collection task.
Collecting Data for RNC and NodeB PMI
Return to the Task Management window to create a collection task, choose the SOP scenario
group, and select the UMTS and NodeB collection scenarios.
Step 12 Collecting the RNC and NodeB Data Separately and Creating a Data Package
If you cannot concurrently collect RNC and NodeB data in one task in the methods described
in section "Collecting RNC and NodeB Data in One Task" collect the RNC and NodeB data
separately and manually create a data package to perform the PMI.
You can select a maximum of 1000 NodeBs in one task. The NIC automatically collects data
of 1000 NodeBs per subtask.
3. Compress the UMTS_SOP and NodeB_SOP collection results into a data package by
The UMTS_SOP and NodeB_SOP collection tasks obtain the following two collection
results:
Drag the data folders in the UMTS compression package to the directory of the NodeB
compression package. Then, you obtain a combo data package.
2.1.3 Data Collection Based on Customized Collection
Items
Collecting LTE configuration data, Performance Data, and internal CHR data is used as an
example. The data collecting method for other RATs is similar.
Step 1 Select Based on Customize Collection Item on the Task List tab page.
Step 2 Set the task properties in the Custom Task Creation Wizard window.
Step 3 Set the time range for data collection.
Step 4 Select NEs whose data needs to be collected.
Task IDs are generated randomly, for example, 10002, 10003, and 10004.
Check whether the task ID folder saves the collection task created by the user based on the
collection task name in the folder.
After data collection by using the NIC in co-deployment mode, collection results are
downloaded and saved through a web page, as shown in the following figure:
Collection results are downloaded in .zip format. The naming convention of the data package
is collection task name_timestamp, as shown in the following figure:
The data packet downloaded by the NIC in co-deployment mode from the GUI must be copied to the
directory that is used as the database directory when you create a task in the OMStar V500R009. The
version earlier than OMStar V500R008C00SPC200 does not support the download of data packet by the
NIC in co-deployment mode.
Record the directory for saving the data collection results for the further analysis of the
OMStar in one-click mode.
If the online deployment mode is used (that is, the NIC and the OMStar are installed on the
same PC), record only the directory for saving the collected data.
If the offline deployment mode is used (that is, the NIC and the OMStar are installed on
different PCs), copy the data in the task ID folder to the PC where the OMStar is installed,
and record the directory for saving the collected data.
Step 2 Enter and run the EXP CFGMML command. In the command output, the save directory for
configuration data is displayed.
Step 3 Start the File Manager tool to download configuration files.
In the File Manager window, find the configuration data in the directory displayed in the
EXP CFGMML command output and click Download to download the files to the local PC.
2.2.2 RNC Performance Data Collection
In the File Manager window, BSC and RNC Performance Data are stored in the
\bam\common\MeasResult directory. The Performance Data can be directly downloaded.
You need to download only the files whose names contain EMS-NORMAL.
For Neighboring UMTS Cell Analysis, UMTS Antenna Fault Detection and UMTS Antenna
Reverse Detection, you need to start the Measurement of Neighboring UMTS Cell
Performance by U2000. Perform the following steps:
Step 1 Log in to the U2000 client, and choose Performance > Measurement Management.
Step 2 Select the Measurement of Neighboring UMTS Cell Performance and RNC that you want
to collect, and select all counters in the module of Setting->60 minutes on the right of
window. Click button Apply to start the performance measurement. The performance files on
the next period will contain the counters of Measurement of Neighboring UMTS Cell
Performance.
Raw data contains personal user data (such as IMSI). Before collecting the data, you must obtain
the written authorization from customers and anonymize personal data at the NE side. Ensure
that collected data has been anonymized.
Use the File Manager tool of the Web LMT to download CHR\MR files. The file directories
are as follows. Click Download to download the files to a local PC.
UMTS PCHR data directory: \bam\common\fam\famlogfmt\pchr\
If UMTS PCHR data is used for UMTS in-depth call drop analysis and UMTS access failure
analysis, ensure that the event functions for call drops and access failures in the PCHR have
been enabled. Event functions to be enabled and MML commands to be run are as follows:
Event functions to be enabled:
CONN_SETUP, RRC_RELEASE, RRC_RELEASE_RF, RRC_RELEASE_MSG,
CS_RAB_SETUP, PS_RAB_SETUP, CS_RAB_REL, PS_RAB_REL, SHO, HHO,
SYS_HO_OUT, RELOC, INTRA_FREQ_NET_OPT, INTER_FREQ_NET_OPT, and
INTER_RAT_NET_OPT
MML commands to be run:
SET UCHRCTRL: StateType=ABNORMAL_ONLY-1, DomainType=CS_ONLY-
1&PS_ONLY-0, FlowType=CONN_SETUP-1&RRC_RELEASE-1&RRC_RELEASE_RF-
1&RRC_RELEASE_MSG-1&CS_RAB_SETUP-1&PS_RAB_SETUP-1&CS_RAB_REL-
1&PS_RAB_REL-1&SHO-1&HHO-1&SYS_HO_OUT-1&RELOC-1&DCCC-0&FHHO-
0&INTRA_FREQ_NET_OPT-1&INTER_FREQ_NET_OPT-1&INTER_RAT_NET_OPT-
1&STAT-0&HTTP_P2P_TRAFFIC_STAT-0&VIDEO_STAT-0&SRB2_STAT-
0&CS_RAB_QUALITY_STAT-0&PS_RAB_QUALITY_STAT-
0&SPEECH_METAL_NOISE-0&UL_SPEECH_SILENCE-0&DL_SPEECH_SILENCE1-
0&DL_SPEECH_SILENCE2-0&CELL_LOAD-0&FACH-0&PTT-
0&COMPRESS_MODE_INFO-0
UMTS MR data directory: \bam\common\fam\mr
To use UMTS MR data for neighboring cell analysis, run the SET UMRCTRL and SET
UMRSCOPE commands to enable MR collection of neighboring cells. For details about the
commands and the impacts of the commands on NEs, see the related MML command
reference.
In the SET UMRCTRL command, set MR Trace Traffic Type to TRAFFIC_AMR, MR
Intra-freq Measurement period to D12, and MR Report Configure Switch to a proper
value based on actual situations.
SET UMRCTRL:
RTRAFFICTYPE=TRAFFIC_AMR-1&TRAFFIC_VP-1&TRAFFIC_BE-
1&TRAFFIC_OTHER-1, MRINTRAFREQPERIOD=D12,
MRRPRTCFGSWITCH=MR_PRD_INTRA_FREQ_MEAS_SWITCH_1-
1&MR_EVT_INTRA_FREQ_MEAS_SWITCH_2-
1&MR_PRD_INTER_FREQ_MEAS_SWITCH_3-
1&MR_EVT_INTER_FREQ_MEAS_SWITCH_4-
1&MR_PRD_INTER_RAT_MEAS_SWITCH_5-
1&MR_EVT_INTER_RAT_MEAS_SWITCH_6-1&MR_DL_BLER_MEAS_SWITCH_7-
0&MR_UE_TX_POWER_MEAS_SWITCH_8-0&MR_UL_SIR_MEAS_SWITCH_9-
0&MR_LCS_MEAS_SWITCH_10-0&MR_RACH_MEAS_SWITCH_11-0,
MRLCSMETHODSWITCH=LCS_AGPS_UEBASED_SWITCH_1-
0&LCS_AGPS_STANDALONE_SWITCH_2-0&LCS_CELLID_RTT_SWITCH_3-0,
MRDLBLERPERIOD=D12, MRUETPPERIOD=D12, MRULSIRPERIOD=D12,
MRLCSPERIOD=D12;
In the SET UMRSCOPE command, specify Scope Type to set the NE objects to be enabled.
For V9R12\V9R13\V9R14
SET UMRSCOPE: SCOPETYPE=ByRack, SRN=0, SN=0, SSN=0, MRSCOPECTRL=ON;
For V9R15 and the later version
SET UMRSCOPE: SCOPETYPE=ByRnc, LOGICRNCID=1230, MRSCOPECTRL=ON;
The commands for turning on the switch for detecting missing inter-frequency and inter-RAT
neighboring cells are as follows:
R13: Run the SET UAUTONCELLDETECT command to set the GSM BSIC scope
and BCCH ARFCN scope.
R13.1: Run the SET UAUTONCELLDETECT command to set the switch for
detecting missing neighboring cells and parameters in the SON.
R14: Run the SET UAUTONCELLDETECT command to set the switch for detecting
missing neighboring cells and parameters in the SON.
R15: Run the ADD UCELLAUTONCELLDETECT command to set the switch for
detecting missing neighboring cells and related parameter groups, and run the ADD
UAUTOGSMNCELLGROUP command to set the BSIC scope and BCCH ARFCN
scope.
R16: Run the ADD UCELLAUTONCELLDETECT command to set the switch for
detecting missing neighboring cells and related parameter groups, and run the ADD
UAUTOGSMNCELLGROUP command to set the BSIC scope and BCCH ARFCN
scope.
R17: Run the ADD UCELLAUTONCELLDETECT command to set the switch for
detecting missing neighboring cells and related parameter groups, and run the ADD
UAUTOGSMNCELLGROUP command to set the BSIC scope and BCCH ARFCN
scope.
The impact of enabling the MR collection function by running the SET UMRCTRL
command is as follows:
Enabling the MR collection function increases the processing overhead on the control plane of
an NE. Therefore, you are advised to set the MR period parameter with caution. The
following example is a typical CPU usage scenario: If the MR period is set to 12s, the SPU
CPU usage on the RNC increases by about 10% when all types of cell-level MR collection
functions are enabled on the RNC.
The impact of enabling the MR collection function by running the SET UMRSCOPE
command is as follows:
After the MR collection function is enabled for cells, the amount of control plane data to
be transmitted increases. This increases the probability of congestion exceptions
occurring over the Uu and Iub interfaces for such cells during control plane data
transmission.
If the number of cells for which the MR collecting function is enabled increases, the
processing overhead on the control plane on the RNC increases.
After the MR collection function for specified areas is enabled by running the SET
UMRSCOPE command, the CPU usage increases.
For details, refer to the MML Command Reference.
After the data collection is complete, run the preceding commands one by one to disable each
MR collection function. In addition, the SET UMRSWITCH command is added in RAN15.0
and later, and can be used to enable all MR collection functions at a time.
Step 2 Use the File Manager tool to download alarm logs. The file directory is
\bam\version_b\ftp\COLLOGINFO\OPT-LOG. Click Download to download the files to a
local PC.
2.2.7 UMTS RTWP Data Collection
The RTWP data in the OMStar is used for analysis of the UMTS Uplink Interference
Detection and Recognition and UMTS Antenna Fault Detection themes.
You can obtain UMTS RTWP Data Collection Guide from the following URL:
http://3ms.huawei.com/hi/group/2028955/file_4824153.html?
for_statistic_from=my_group_file
You can obtain the Scripts Maker Tool for RTWP Log Collecting from the following URL:
http://3ms.huawei.com/hi/group/2028955/file_4116945.html
Step 2 In the NE tree in the left pane, select a NodeB and click Backup to back up the configuration
data of the NodeB. The backup process is displayed in the Immediate Task list in the lower
part of the window. After the backup is complete, the FTP directory storing the NodeB
configuration data is displayed in the NE Backup List. You can obtain the configuration files
from this directory using the FTP. The file name is NodeBCfg.xml. The system downloads
the NE description information file neinfo.xml at the same time. You do not need to pay
attention to it.
2.2.11 NodeB Performance Data Collection (.mrf)
The NodeB Performance Data files in .mrf format are stored in a fixed directory on the
U2000, /export/home/sysm/ftproot/nbi. You can directly access this directory on the U2000
using the FTP.
In this directory, the Performance Data files are stored by NodeB. The Performance Data of
each NodeB is saved in one folder named after the NodeB FDN.
In the folder of each NodeB, the raw and compressed NodeB Performance Data file in .mrf
format is stored in the gz folder, which can be directly obtained.
On the U2000 main topology, right-click a selected NodeB and choose Properties from the
shortcut menu to query the FDN of the NodeB.
2.2.12 NodeB Performance Data Collection (.csv)
Currently UMTS Accurate Analysis use NodeB csv performance only. The NodeB
Performance Data files in .csv format can collect on the U2000, the operation as below.
Step 1 On the U2000 topology, choose Performance > Query Result.
Step 2 On the Query Result, choose a user name and right click New Query.
Step 3 On the New Query, set the parameter according to the red region setting as below. And then
select the counter to export the result file.
VS.HSUPA.LoadOutPut.0
Measurement of Local Cell Performance
~VS.HSUPA.LoadOutPut.25
VS.IUB.FlowCtrol.DL.CongTime.LgcPort1
Measurement of NodeB Performance
~VS.IUB.FlowCtrol.DL.CongTime.LgcPort2
VS.IUB.FlowCtrol.DL.DropNum.LgcPort1
Measurement of NodeB Performance
~VS.IUB.FlowCtrol.DL.DropNum.LgcPort2
VS.IUB.FlowCtrol.DL.ReceiveNum.LgcPort1
Measurement of NodeB Performance
~VS.IUB.FlowCtrol.DL.ReceiveNum.LgcPort2
VS.IUB.FlowCtrol.DL.DelayVara.LgcPort1.Avg
Measurement of NodeB Performance
~VS.IUB.FlowCtrol.DL.DelayVara.LgcPort2.Avg
VS.IUB.FlowCtrol.UL.CongTime.LgcPort1
Measurement of NodeB Performance
~VS.IUB.FlowCtrol.UL.CongTime.LgcPort2
VS.IUB.FlowCtrol.UL.DropNum.LgcPort1
Measurement of NodeB Performance
~VS.IUB.FlowCtrol.UL.DropNum.LgcPort2
VS.IUB.FlowCtrol.UL.DelayVara.LgcPort1.Avg
Measurement of NodeB Performance
~VS.IUB.FlowCtrol.UL.DelayVara.LgcPort2.Avg
VS.IUB.FlowCtrol.UL.SendNum.LgcPort1
Measurement of NodeB Performance
~VS.IUB.FlowCtrol.UL.SendNum.LgcPort2
Step 3 Select and right-click the result content and choose Save As from the shortcut menu to save
the result as a default .txt file.
In the displayed dialog box, click Export and the files are exported as .csv files by default.
NodeB License Collection on the U2000
Step 1 Log in to the U2000 and choose License > NE License Management > NodeB.
Step 3 In the NodeB License Management window, select a NodeB to view related license
information. Click Export License. In the displayed Export License File dialog box, select
NEs to be exported in the NE list, choose the save path, and click Confirm to save the license
file on the local PC.
2.2.16 BSC/RNC Performance Data Collection (U2000)
Obtaining a Collection Template
In the data import window of the OMStar, right-click U2000 Perf Data and choose U2000
Pert Template Management from the shortcut menu, as shown in the following figure.
Export the template as required.
I. Precautions
If no geographic data is imported before you calculate property data, the exported
property data is based on ground coordinates. If geographic data has been imported when
you calculate the property data, the exported property data is based on longitude and
latitude coordinates.
The property data is exported as TXT files. Each property data file contains the file head
and file body.
Prerequisites
The geographic data has been imported.
Base station information has been created or imported, including sites, transceivers, and
cells.
The calculation area is created.
Procedure
Create a prediction group and calculate related counters in the group. You need to calculate the
CPICH RSCP prediction counter for UMTS.
The prediction precision affects the reliability of prediction results and the duration of prediction
calculation. A smaller value of prediction precision indicates higher prediction precision and longer
duration of prediction calculation.
You are advised to set the prediction precision to be the same as the path loss calculation precision and
the map precision.
Step 3 In the displayed dialog box, set prediction group name, whether to calculate immediately, and
select prediction counters.
Figure 2.2.17.1.1.3.1.1 shows an operation example (GSM). For counter description, see
Table 2.2.17.1.1.4.1.1.2.
Figure 2.2.17.1.1.3.1.1 Creating a prediction group (1)
In 3, you can right-click a counter and choose the related menu item from the displayed shortcut menu to
show or hide the counter:
To show a hidden counter, choose More Coverage from the shortcut menu.
To hide a counter, choose Clear More from the shortcut menu.
Step 4 In the displayed dialog box, set the prediction group properties.
Figure 2.2.17.1.1.4.1.1 shows an operation example. For parameter description, see Table
2.2.17.1.1.4.1.1.1, Table 2.2.17.1.1.4.1.1.2, and Table 2.2.17.1.1.4.1.1.3.
Figure 2.2.17.1.1.4.1.1 Creating a prediction group (2)
Table 2.2.17.1.1.4.1.1.1 Parameters on the General tab page in the UMTS Group Properties
dialog box
Parameter Description
Table 2.2.17.1.1.4.1.1.2 Parameters on the Condition tab page in the UMTS Group Properties
dialog box
Parameter Description
Table 2.2.17.1.1.4.1.1.3 Parameters on the Advanced tab page in the UMTS Group Properties
dialog box
Parameter Description
If... Then...
Select Calculate now The U-Net automatically calculates the prediction group.
Deselect Calculate now You need to right-click a prediction group in the navigation
tree and choose Calculate from the shortcut menu to start
calculation.
If you right-click a prediction group that is being calculated and choose Stop from the shortcut
menu, counters will not be automatically locked.
After a prediction group is calculated, counters are automatically locked. If all counters in a
prediction group are locked, the prediction group cannot be calculated.
After you modify attributes for a prediction group, all counters in the prediction group are
automatically unlocked.
You can right-click a prediction group or counter and choose Studies Locked from the shortcut
menu to manually lock the prediction group or counter. When prediction needs to be performed
again, you can clear Studies Locked to unlock the prediction group or counter. Then, the prediction
group or counter can be calculated again.
Verifying the Feature Database Based on DT Data
After a coverage prediction group is calculated, you can use DT data to adjust the group to
improve the accuracy of feature data and positioning. If no DT data is to be adjusted, you can
skip this section.
Step 8 Set related parameters in the displayed dialog box. For details about parameters, see Table
2.2.17.1.1.8.1.1.1.
Step 12 Set the minimum value and the top N maximum receive levels to be exported.
Step 13 Click Export.
Step 14 Set the save path, file name, and file type. Then, export the preset information.
To export top N receive levels within the lattice, you must set TopNSignalLevel when creating a
prediction group. This parameter indicates that the top N maximum receive levels will be calculated.
The minimum level value in the exported property data indicates the smaller value between the
value of Min Signal Level (dBm) in the Export By Top Signal Level dialog box and the minimum
level value you have set when creating a prediction group.
----End
You can click download Terminal LIB and Terminal Type from RuleStore (Choose
Help > Script Update from the OMStar main menu).
Step 3 Click Yes. In the Confirm dialog box shown in the following figure, click Yes to back up
data.
It takes an extended period if a large number of NEs are selected for backup. In addition, the backup is
irreversible.
The backup progress is displayed in the Progress column, as shown in the following figure.
Step 4 When the backup progress for all NEs becomes 100% and Succeeded is displayed in the
Information column, the backup is complete. The NEs whose data has been successfully
backed up will be displayed in the NE Backup List in the right pane. After the backup, all
XML configuration files of the NEs are saved on the U2000 server and the save path is
displayed in the Path column.
Step 5 In the NE Backup List, select all NEs and click Download to OMC Client at the right
corner of the window to download the configuration files from the U2000 server to your local
PC.
In the Select Folder dialog box shown in the following figure, specify Directory and click
Save.
The download progress is displayed in the Progress column. When Succeeded is displayed in
the Status column, the configuration files are successfully downloaded to your local PC.
The downloaded configuration files are saved in the structure shown in the following figure.
The first-level node is the name of the folder for saving the configuration files. The second-
level node is the name of a base station displayed on the U2000. The third-level node is the
backup date. The backup XML configuration files are all named U2000.XML.
The default coding format of the exported CSV file is UTF-8. The coding format is changed if the CSV
file is edited in Excel format. The CSV file can be queried by the text editor if the following
requirements are met:
The first line of the file is empty, the seventh line is the header, and the data line starts from the
eighth line. Alternatively, the first line is the header, and the data line starts from the second line. The
rest of the lines cannot be identified.
The header line and data line are separated using a comma (,), and other separation modes are not
supported.
CELL level:
BSCNAME BTSNAME CELLNAME Time TCH counterA … counterN
Traffic
The fields in green in the above tables are mandatory. The NAME columns, such as
ENODEBNAME and CELLNAME, can correspond to the ID columns in the data. The
reference indicators in yellow are optional.
The format of time: MM/dd/YYYY hh:mm:ss (for example: 06/29/2012 21:00:00), or
YYYY/MM/dd hh:mm:ss or MM/dd/YYYY.
Step 2 Select Anonymous policy and Enable anonymous policy in the Anonymous Policy
Management.
Step 3 Select Monitor > Signaling Trace > Signaling Trace Management in the panel of U2000 to
collect signal data.
Step 4 Clicking UMTS Standard UE Trace is used as an example. Select Standard UE Trace in
UMTS at left tree and click New.
Step 5 Select the NE, Trace Duration, and Running Mode in the Standard UE Trace window for
signal collection, and then click Next.
Step 6 Set the RNC ID, Trace type, and IMSI for Signal collection, and then click Finish.
Step 7 After data collection task running, select a collection task and click Export to obtain the
signal data.
----End