OMStar V500R011
UMTS Data Collection Guide
Issue
01
Date
2015-07-10
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2015. 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 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
i
OMStar UMTS Data Collection Guide
About This Document
About This Document Change History Changes between document issues are cumulative. The latest document issue contains all the changes made in earlier issues.
Issue 01 (2015-07-10) This issue is the first official release.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
ii
OMStar UMTS Data Collection Guide
Contents
Contents About This Document .................................................................................................................... ii 1 OMStar Data Source Overview .................................................................................................. 1 1.1 Data Source Description ............................................................................................................................................... 1 1.2 Data Sources Required for UMTS Features and Collection Methods .......................................................................... 2 1.3 Security Precautions ..................................................................................................................................................... 7 1.3.1 Impact of the Anonymous Policy on OMStar Service Features ................................................................................. 7 1.3.2 Enabling the Anonymization Function ...................................................................................................................... 8
2 General Principles for Data Collection ................................................................................... 11 2.1 NIC Data Collection ................................................................................................................................................... 11 2.1.1 Starting the NIC ....................................................................................................................................................... 11 2.1.2 Creating a Collection Task ....................................................................................................................................... 18 2.1.2.1 Collecting UMTS Data ......................................................................................................................................... 18 2.1.2.2 Collecting GSM and UMTS Data ......................................................................................................................... 22 2.1.2.3 Collecting Data for RNC and NodeB PMI ........................................................................................................... 26 2.1.3 Data Collection Based on Customized Collection Items ......................................................................................... 31 2.1.4 Viewing the Collection Result ................................................................................................................................. 37 2.2 Manual Data Collection .............................................................................................................................................. 39 2.2.1 BSC/RNC Configuration Data Collection ............................................................................................................... 39 2.2.2 RNC Performance Data Collection .......................................................................................................................... 42 2.2.3 RNC Alarm Log Collection ..................................................................................................................................... 44 2.2.4 RNC MML Packet Collection.................................................................................................................................. 45 2.2.5 RNC CHR/MR Data Collection............................................................................................................................... 45 2.2.6 RNC Operation Log Collection ............................................................................................................................... 47 2.2.7 UMTS RTWP Data Collection ................................................................................................................................ 48 2.2.8 Co-Site Information Collection................................................................................................................................ 49 2.2.9 Engineering Parameter Collection ........................................................................................................................... 50 2.2.10 NodeB Configuration Data Collection ................................................................................................................... 50 2.2.11 NodeB Performance Data Collection (.mrf) .......................................................................................................... 52 2.2.12 NodeB Alarm Log Collection ................................................................................................................................ 54 2.2.13 NodeB MML Command Collection ...................................................................................................................... 56 2.2.14 NodeB License Collection ..................................................................................................................................... 58 2.2.14.1 NodeB License Collection on the M2000 ........................................................................................................... 58
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
iii
OMStar UMTS Data Collection Guide
Contents
2.2.14.2 NodeB License Collection on the U2000 ........................................................................................................... 59 2.2.15 Property Data Collection ....................................................................................................................................... 61 2.2.15.1 Precautions for Preparing Property Data ............................................................................................................ 61 2.2.15.2 Preparing Property Data ...................................................................................................................................... 62 2.2.15.3 Verifying the Feature Database Based on DT Data ............................................................................................. 68 2.2.15.4 Exporting Property Data ..................................................................................................................................... 68 2.2.16 Terminal Library Data Collection .......................................................................................................................... 69 2.2.17 eNodeB Configuration Data Collection ................................................................................................................. 69 2.2.18 PRS Perf Data Collection ...................................................................................................................................... 73 2.2.19 UMTS Signaling Data Collection .......................................................................................................................... 74
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
iv
OMStar UMTS Data Collection Guide
1
1 OMStar Data Source Overview
OMStar Data Source Overview
1.1 Data Source Description The OMStar V500R011 provides comprehensive analysis of NE configuration, Performance Data, alarm logs, and MML packets. The collected data must meet the interface specifications of the OMStar. The following data lists the data types supported by the OMStar. NE Type
Data
Controller (BSC/RNC)
Configuration data Performance data (original or PRS performance data) Alarm logs MML packets CHR MR Property data Terminal data GSM UL FreqLog data GSM VSWR data Increase factor UMTS OPT data
NodeB
Configuration data Performance data Alarm logs MML packets NodeB License RTWP
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
1
OMStar UMTS Data Collection Guide
EGBTS
1 OMStar Data Source Overview
Configuration data Performance data
eNodeB
Configuration data Performance data (original, M2000, or PRS performance data) Alarm logs MML packets CHR CellRic data (including reverse spectrum CHR data) SIG data Signaling logs FaultLog LTE BrdLog
1.2 Data Sources Required for UMTS Features and Collection Methods Feature
Data Source
Mandat ory (Yes/N o)
Link of Collection Methods
UMTS KPI Subject
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
Performance data
Yes
2.2.2 RNC Performance Data Collection
NodeB Performance data
Yes
2.2.11 NodeB Performance Data Collection (.mrf)
Engineering parameters
No
2.2.9 Engineering Parameter Collection
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
Performance data
Yes
2.2.2 RNC Performance Data Collection
NodeB Performance data
No
2.2.11 NodeB Performance Data Collection (.mrf)
UMTS KPI Analysis
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
2
OMStar UMTS Data Collection Guide
1 OMStar Data Source Overview
Engineering parameters
No
2.2.9 Engineering Parameter Collection
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
Performance data
Yes
2.2.2 RNC Performance Data Collection
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
Performance data
Yes
2.2.2 RNC Performance Data Collection
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
Performance data
Yes
2.2.2 RNC Performance Data Collection
Engineering parameters
No
2.2.9 Engineering Parameter Collection
RTWP
Yes
2.2.7 UMTS RTWP Data Collection
Geographical Display of UMTS Parameters
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
Engineering parameters
Yes
2.2.9 Engineering Parameter Collection
UMTS Configuration Parameter Viewing
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
UMTS Intra-Frequency Neighboring Cell Analysis
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
MR data
Yes
2.2.5 RNC CHR/MR Data Collection
PCHR data
Yes
2.2.5 RNC CHR/MR Data Collection
Engineering parameters
No
2.2.9 Engineering Parameter Collection
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
Performance data
Yes
2.2.2 RNC Performance Data Collection
Engineering parameters
Yes
2.2.9 Engineering Parameter Collection
UMTS KPI Weekly Report
UMTS KPI Daily Report
UMTS Uplink Interference Detection and Recognition
UMTS Antenna Reverse Dectection
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
3
OMStar UMTS Data Collection Guide
1 OMStar Data Source Overview
RNC configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
NodeB configuration data
Yes
2.2.10 NodeB Configuration Data Collection
MML
No
2.2.4 RNC MML Packet Collection
RTWP
No
2.2.7 UMTS RTWP Data Collection
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
Engineering parameters
No
2.2.9 Engineering Parameter Collection
PCHR data
No
2.2.5 RNC CHR/MR Data Collection
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
PCHR data
Yes
2.2.5 RNC CHR/MR Data Collection
Terminal data
No
2.2.16 Terminal Library Data Collection
UMTS Access Failure Deeply Analysis
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
PCHR data
Yes
2.2.5 RNC CHR/MR Data Collection
UMTS Access Call Drop Basic Analysis
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
Performance data
Yes
2.2.2 RNC Performance Data Collection
UMTS Coverage Analysis
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
MR Data
Yes
2.2.5 RNC CHR/MR Data Collection
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
Performance data
Yes
2.2.2 RNC Performance Data Collection
PRS data
Yes
2.2.18 PRS Perf Data Collection
UMTS configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
UMTS Antenna Fault Detection
UMTS PSC Analysis
UMTS Call Drop Deeply Analysis
UMTS Traffic Forecast
UMTS Neighboring Cell
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
4
OMStar UMTS Data Collection Guide
1 OMStar Data Source Overview
Check
UMTS engineering parameters
No
2.2.9 Engineering Parameter Collection
GSM configuration data
No
2.2.1 BSC/RNC Configuration Data Collection
GSM engineering parameters
No
2.2.9 Engineering Parameter Collection
LTE configuration data
No
2.2.17 eNodeB Configuration Data Collection
LTE engineering parameters
No
2.2.9 Engineering Parameter Collection
U2000 handover traffic statistics
No
2.2.2 RNC Performance Data Collection Inter-cell handover counters VS.SHO.SuccASU.NCell and VS.SHO.AttASU.NCell are required in traffic statistics.
UMTS performance data
No
2.2.2 RNC Performance Data Collection
UMTS configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
UMTS MR Data
Yes
2.2.5 RNC CHR/MR Data Collection
UMTS engineering parameter data
No
2.2.9 Engineering Parameter Collection
GSM engineering parameter data
No
2.2.9 Engineering Parameter Collection
UMTS configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
UMTS MR data
Yes
2.2.5 RNC CHR/MR Data Collection
Engineering parameter data
No
2.2.9 Engineering Parameter Collection
UMTS Config Parameters Check
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
UMTS Baseline Config Check
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
UMTS Multicarrier Parameter Check
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
UMTS/GSM Neighboring Cell Analysis
UMTS Inter-Frequency Neighboring Cell Analysis
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
5
OMStar UMTS Data Collection Guide
1 OMStar Data Source Overview
UMTS Config Compare
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
UMTS Engineering Parameter Check
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
Engineering parameter data
Yes
2.2.9 Engineering Parameter Collection
UMTS Network Geographic Observation
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
Engineering parameter data
Yes
2.2.9 Engineering Parameter Collection
Property data
No
2.2.15 Property Data Collection
MR data
Yes
2.2.5 RNC CHR/MR Data Collection
PCHR data
No
2.2.5 RNC CHR/MR Data Collection
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
OMU PCHR
Yes
2.2.5 RNC CHR/MR Data Collection
Engineering parameter data
Yes
2.2.9 Engineering Parameter Collection
MR data
Yes
2.2.5 RNC CHR/MR Data Collection
Property data
No
2.2.15 Property Data Collection
Terminal information
No
2.2.16 Terminal Library Data Collection
UMTS CHR Browsing
PCHR/CallFault data
Yes
2.2.5 RNC CHR/MR Data Collection
UMTS Signaling Browsing
UMTS Signaling Data
Yes
2.2.19 UMTS Signaling Data Collection
UMTS_Indoor_Ce ll_RF_Optimizatio n
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
MR data
Yes
2.2.5 RNC CHR/MR Data Collection
Engineering parameter data
Yes
2.2.9 Engineering Parameter Collection
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
RNC License
Yes
2.2.4 RNC MML Packet Collection
UMTS Terminal Analysis
UMTS_Swap_Roll out_FeatureAuditi ng
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
6
OMStar UMTS Data Collection Guide
1 OMStar Data Source Overview
UMTS_Terminal_ Audit
Configuration data
Yes
2.2.1 BSC/RNC Configuration Data Collection
CHR data
Yes
2.2.5 RNC CHR/MR Data Collection
1.3 Security Precautions
Before collecting data, you must obtain the written authorization from customers. Standard authorization must include the products or issue items, purposes, contents, scopes, time limits, and other stipulations.
Before collecting data, you must obtain anonymized personal data at the NE side. Ensure that collected data has been anonymized.
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.
1.3.1 Impact of the Anonymous Policy on OMStar Service Features Impact of the MSISDN Anonymous Policy on Fuzzy Search The MSISDN anonymization policy affects NDC-based analysis and MSISDN-based fuzzy search. (NDC is short for national destination code.) 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.
Collision Possibility of the IMEI Anonymous Policy The IMEI anonymization policy anonymizes 6 to 8 digits excluding the IMEI TAC of an IMEI. It allows the OMStar to compress an 8-digit code into a 4-byte code and obtain a resulting HASH 32-byte code by using the HMAC-SHA256 algorithm. Then, the OMStar takes and decodes the preceding 4 bytes as the anonymization result.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
7
OMStar UMTS Data Collection Guide
1 OMStar Data Source Overview
In theory, collisions are possible because the obtained HASH codes are one eighth of the original codes in length. A collision occurs if two different 8-digit numbers are converted into the same new 8-digit hexadecimal number after they are anonymized. Based on laboratory data, the probability of collisions is approximately 0.012%. Two different IMEIs might be regarded as the same IMEI in the statistical results if their IMEI TACs are the same. This affects the accuracy of terminal analysis results. Affected features are call drop deeply analysis, access failure deeply analysis, signaling browsing, and CHR browsing.
1.3.2 Enabling the Anonymization Function Before collecting personal data containing IMSIs, enable the anonymization function on the U2000 client and then collect data. Perform the following operations to enable the anonymization function: Step 1 Choose Monitor > Signaling Trace > Anonymous Policy Management.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
8
OMStar UMTS Data Collection Guide
1 OMStar Data Source Overview
Step 2 The Anonymous Policy Management window is displayed. Click Anonymous policy, select Enable anonymous policy, and click OK to enable the anonymization function.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
9
OMStar UMTS Data Collection Guide
Issue 01 (2015-07-10)
1 OMStar Data Source Overview
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
10
OMStar UMTS Data Collection Guide
2
2 General Principles for Data Collection
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 M2000 is used as an example. The operation on the U2000 is almost the same as that on the M2000. If the operations on the M2000 and U2000 greatly differ, they are described separately in specific chapters.
2.1 NIC Data Collection 2.1.1 Starting the NIC Using NIC in Co-Deployment Mode Step 1 Start the Microsoft Internet Explorer (IE). Type http://Server IP address/nic and press Enter. In SSL mode, you need to type https://server IP address: 31040/nic in the address bar of the IE. The server IP address refers to the IP address of the M2000. In the Security Alert dialog box, click Yes. In the Security Information dialog box, click Yes.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
11
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
If M2000 established SSL to register safely, then need to set certificate in the IE. The method is as follows:
1.
Open the IE tool –>Internet option –> content -> certificate -> import the right certificate
2.
You can get the certificate files from the M2000 install path: \client\client\style\defaultstyle\conf\ssl\keyStore\PFX\client.p12 \client\client\style\defaultstyle\conf\ssl\trust\PEM\trust.cer
P.S Consultation the manager of M2000 to get the password of client.p12, please. Step 2 In the NIC login window, type the user name, password, and verification code. Click Login.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
12
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
If the verification code is illegible, you can click Reset to refresh the verification code. After that, you need to type the password again.
Overview of NIC in Co-Deployment Mode
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 M2000.
----End
Using NIC Stand-Alone Version Step 1 Using the NIC to Collect Data. Overview of NIC GUI
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
13
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
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). Scenario Management: Used to customize a collection scenario that the SOP collection is unavailable (optional). NE Management: Used to create or delete an NE. For details about how to create an NE. Upload Management: Used to create an upload task (uploading data to the FTP server automatically (this function can be ignored for SOP) The upload management module is deleted in NIC V100R006C00SPC700 and later versions.
Step 2 Creating an NE This section describes how to create a BSC manually on the NIC. For details about how to import NEs in batches, see the FAQ.
1.
Start the NIC service.
Click Start NIC in the NIC Console, as shown in the following figure:
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
14
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
2.
Choose NE Management > NE Information Maintenance.
3.
Select the NE type.
For GSM NEs, select BSC6900 GSM, as shown in the following figure.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
15
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
For UMTS NEs, select BSC6900 UMTS, as shown in the following figure.
For GU dual-mode NEs, select BSC6900 GU, as shown in the following figure.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
16
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
For LTE NEs, select eNodeB, as shown in the following figure.
4.
Configure the NE connection information (use UMTS as the example)
BSC6900 UMTS: Network element name and Network element IP: Indicates the name and IP address of the NE to be created. Network element name and Network element IP are both unique and identify a unique NE. User type: Indicates the type of the user for logging in to the RNC. The user can be either a domain user or a local user. If you select a domain user to create an NE, the NE must be managed by the M2000.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
17
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
LMT User name and LMT Password: Is equivalent to the LMT login "user name" and "password", the user's operating authority need to be "Administrator" management level. Connect and Authenticate Mode: Sets the RNC connection mode to Plain or SSL. When SSL is selected, the authentication mode can be None or Peer. NodeB user name and NodeB password: Indicates the user name and password of all NodeBs under the current RNC. By default, NodeB user name is admin and NodeB password is NodeB. FTP port, FTP user name, and FTP password: Indicates the port number, user name, password of the FTP server on the current RNC. By default, FTP port is 21 and User name is FtpUsr. Connect NodeB: Indicates whether to connect a NodeB when creating an RNC. If data is only collected on the RNC, you are advised to select no. You need to install the mediation for the NodeB before selecting yes. 5.
Click Apply to create an NE.
SOP data collection will collect configuration data, performance data, alarm data, and MML data from the BSC, NodeB data, and eNodeB data. If data collection of the NodeB and eNodeB fails, check whether Proxy Mode is selected in the Server Proxy Configuration window and whether the NodeB and eNodeB are running properly. NOTE
If NE creation fails, please see the FAQ.
----End
2.1.2 Creating a Collection Task After preparations, use the NIC stand-alone version to collect data in the specific collection scenarios
2.1.2.1 Collecting UMTS Data Step 1 Click the Task Management tab. Select Unfinished Tasks in Navigation Tree, and select Based on Scenario from the Create Task drop-down list box in Task List.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
18
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 2 Set Task Name, and select UMTS from the Product Type drop-down list box, and select BSC6900_SOP from the Scenario(Group) drop-down list box.
Task Name: The name of the collection task for inspection or SOP can contain letters (a to z and A to Z), numbers (0 to 9), spaces, Chinese characters, underline (_), and dashes (-). The name cannot contain more than 64 characters, and spaces before and after task name will be ignored. The task name here must be consistent with the name of the analysis task in OMStar V500R009. Product type: Choose UMTS. Scenario group: Choose SOP scenario (RNC and NodeB scenario group name change for SOP after the version of V9R14C00SPC200). Choose UMTS_SOP scenario. Why the NIC both have UMTS_SOP and SOP scenario in the NE version of R15. Has anything to distinguish? Which data have been collected? Answer: The scene (group) has been unified SOP where is in the following picture. There are contain UMTS SOP scenarios and NodeB SOP scenarios when you choose SOP scenario, ensure that you can collect the SOP data of RNC and NodeB at the same time. Task Execution Type: You are recommended to select Instant. If you select Scheduled, you also need to set the execution time. Step 3 Click Next to set Data collection time range. Data collection time range: You are advised to collect data of three to seven days (if the time range is too large, the collection and analysis efficiency is affected).
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
19
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 4 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.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
20
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 5 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 6 After ensuring that the collected information is correct, click Finish to start executing the collection task.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
21
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
----End
2.1.2.2 Collecting GSM and UMTS Data Step 1 Click the Task Management tab. Select Unfinished Tasks in Navigation Tree, and select Based on Scenario from the Create Task drop-down list box in Task List.
Step 2 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.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
22
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Task Name: The name of the collection task for inspection or SOP can contain letters (a to z and A to Z), numbers (0 to 9), spaces, Chinese characters, underline (_), and dashes (-). The name cannot contain more than 64 characters, and spaces before and after task name will be ignored. The task name here must be consistent with the name of the analysis task in OMStar V500R009. Task Execution Type: You are recommended to select Instant. If you select Scheduled, you also need to set the execution time. Step 3 Click Next to set Data collection time range. Data collection time range: You are advised to collect data of three to seven days (if the time range is too large, the collection and analysis efficiency is affected).
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
23
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 4 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.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
24
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 5 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 6 After ensuring that the collected information is correct, click Finish to start executing the collection task.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
25
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
----End
2.1.2.3 Collecting Data for RNC and NodeB PMI NOTE
The UMTS_SOP V5.2 script package (matched with OMStar V500R008C00SPC200) supports the NodeB preventive maintenance inspection (DBS3900WCDMAV200R013C00/BTS3900WCDMAV200R013C00). The OMStar whose version is earlier than V500R008C00SPC200 does not need to collect the NodeB data. The NIC in co-deployment mode provides the access of all NodeBs in the following versions. The NIC in co-deployment mode in the OMStar of earlier versions does not support the NodeB data collection. iManager M2000 V200R011C01SPC240 and later versions iManager M2000 V200R012C00SPC220 and later versions The following section uses the UMTS NE as an example. The data collection method for the SingleRAN is the same. The method described here also applies to the NICs in stand-alone and co-deployment modes. You are advised to collect data of one RNC and its corresponding NodeBs for the RNC and NodeB preventive maintenance inspection. It is recommended that you create multiple collection tasks for multiple NEs. Before collect the NodeB performance data, you should firstly make sure the M2000 let the NodeB performance to be saved.
Collecting RNC and NodeB Data in One Task
In BSC6900 V900R014C00SPC200 and later versions, the Scenario(Group) names of RNC and NodeB are both SOP. For RNC and NobeB co-collection task, see step 3.
In BSC6900V900R014C00SPC200 earlier versions, As the UMTS_SOP and the NodeB_SOP collection scenarios belong to different groups, they cannot be selected concurrently when you create a collection task. You can modify the groups that the UMTS_SOP and NodeB_SOP collection scenarios belong to ensure that the two
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
26
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
collection scenarios belong to the same group by performing the following operations. Then, the RNC and NodeB data can be collected concurrently in one task.
One task collects the data of 1 RNC and 249 NodeBs at most. (In M2000 V200R012C01SPC230 and later versions, when the NIC is co-deployed with the M2000, a collection task can support the data collection of one RNC and 999 NodeBs, and the NIC automatically divides the task to four subtasks.)
Step 1 Modify the group that the UMTS_SOP scenario belongs to. Choose Scenario Management > UMTO_SOP to view the scenario configuration of the BSC6900UMTS_SOP. Change the default group UMTS_SOP to SOP and click Save As. In the displayed dialog box, change the scenario name to BSC6900UMTS_SOP_NEW. If the number of existing scenarios in the NIC exceeds 200, the modification cannot be saved. Collect data by referring to section "Collecting the RNC and NodeB Data Separately and Creating a Data Package."
Step 2 Modify the group that the NodeB_SOP scenario belongs to. Choose Scenario Management > NodeB_SOP to view the scenario configuration of the NodeB_SOP. Change the default group NodeB_SOP to SOP and click Save As. In the displayed dialog box, change the scenario name to NodeB_SOP_NEW.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
27
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Return to the Task Management window to create a collection task, choose the SOP scenario group, and select the UMTS and NodeB collection scenarios.
----End
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.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
28
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 1 Create a UMTS_SOP collection task and obtain an RNC data package.
Step 2 Create a NodeB_SOP collection task and obtain a NodeB data package. You can select a maximum of 1000 NodeBs in one task. The NIC automatically collects data of 1000 NodeBs per subtask.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
29
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 3 Compress the UMTS_SOP and NodeB_SOP collection results into a data package by performing the following operations. 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.
----End
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
30
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
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.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
31
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 4 Select NEs whose data needs to be collected.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
32
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 5 Select collection items. Collecting configuration data, Performance Data, and internal CHR data is used as an example. The selected collection items are eNodeB configuration, Obtain Performance Data of the U2000, and Call log collection. If you need to collect other data sources, select an item from Available collection items and move it to the list of Selected collection items.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
33
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 6 Set detailed parameters of collection items.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
34
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 7 Set additional information about the task. Do not select Download collection results by NEs during the settings. Otherwise, the OMStar cannot identify the collected data.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
35
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 8 Confirm information about the data collection again and click Finish to start data collection.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
36
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
----End
2.1.4 Viewing the Collection Result NOTE
Do not terminate the FTP service of the tool during data collection; otherwise, the collection will fail.
Check whether configuration data collection fails. The data analysis of the NE where configuration data collection fails will also fail.
During collection, view the progress of the whole collection task and the progress and running status of each NE.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
37
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
The data collection results are saved. The NIC stand-alone version collects and saves data. The save path of NIC V100R006C00SPC500 and later versions is Installation directory of the NIC\NIC\var\nic\task ID.
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:
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
38
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
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.
2.2 Manual Data Collection This section mainly describes how to manually collect RNC data and NodeB data required by the OMStar.
2.2.1 BSC/RNC Configuration Data Collection The BSC/RNC configuration data result files used by the OMStar are MML configuration scripts (*.txt), which are exported from the RNC using MML commands. Step 1 In the address bar of the Internet Explorer, enter the IP address of the BSC, log in to the Web LMT, and click MML.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
39
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
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.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
40
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
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.
----End
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
41
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
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 Dectection, you need to start the Measurement of Neighboring UMTS Cell Performance by M2000. Perform the following steps: Step 1 Login M2000 client, and select Performance > Measurement Management.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
42
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
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.
----End Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
43
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
2.2.3 RNC Alarm Log Collection Step 1 Use the Web LMT to run the COL LOG command. Set Log File Type to HISTORY_ALARM. Retain the default values of other options. The system collects alarm logs of all levels and all time by default.
Step 2 Use the File Manager tool to download alarm logs. The file directory is \bam\version_b\ftp\COLLOGINFO\ALM-LOG. Click Download to download the files.
----End
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
44
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
2.2.4 RNC MML Packet Collection Use the WEB LMT to run the MML commands, such as DSP LICUSAGE. Store the command output information as a .txt file or select Save Result to save the command output information directly.
2.2.5 RNC CHR/MR Data Collection
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\
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
45
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
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.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
46
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
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_I NTRA_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_S WITCH_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_SWIT CH_9-0&MR_LCS_MEAS_SWITCH_10-0&MR_RACH_MEAS_SWITCH_11-0, MRLCSMETHODSWITCH=LCS_AGPS_UEBASED_SWITCH_1-0&LCS_AGPS_STAND ALONE_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.
After the measurement report collecting function is enabled, load congestion is more likely to occur on the Uu and Iub control plane and the number of signaling messages will increase by over 10%. The detail information reference to MML Command Reference please.
2.2.6 RNC Operation Log Collection Step 1 Use the WEB LMT to run the COL LOG command. Select OPT_LOG for Log File Type.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
47
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
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.
----End
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.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
48
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
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_fi le 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
2.2.8 Co-Site Information Collection Step 1 On the M2000 main topology, choose Configuration > Report > MBTS Relationship Report.
In the displayed dialog box, select MBTS(GL) NE Report, MBTS(GU) NE Report, MBTS(GUL) NE Report, and MBTS(UL) NE Report. Then, click OK.
Step 2 Click Save to save the displayed MBTS relationship reports in .xlsx format.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
49
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
----End
2.2.9 Engineering Parameter Collection Engineering parameters are maintained by onsite engineers. The OMStar can identify the engineering parameter files in .xlsx format. Obtain the engineering parameter template using the following method: On the OMStar GUI, choose Template Management > Engineering Parameter Template Export and export the GSM/UMTS/LTE engineering parameter templates separately.
2.2.10 NodeB Configuration Data Collection Step 1 On the M2000 topology, choose Maintenance > Backup Management > NE Backup.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
50
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
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.
----End
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
51
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
2.2.11 NodeB Performance Data Collection (.mrf) The NodeB Performance Data files in .mrf format are stored in a fixed directory on the M2000, /export/home/sysm/ftproot/nbi. You can directly access this directory on the M2000 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 M2000 main topology, right-click a selected NodeB and choose Properties from the shortcut menu to query the FDN of the NodeB.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
52
OMStar UMTS Data Collection Guide
Issue 01 (2015-07-10)
2 General Principles for Data Collection
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
53
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
2.2.12 NodeB Alarm Log Collection Step 1 Choose Topology > Main Topology from the M2000 main menu.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
54
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 2 In the NE tree in the left pane, right-click a selected NodeB and choose Query Alarm/Event > Alarm Logs from the shortcut menu.
Step 3 Right-click in the Query Alarm Logs result page and choose Save > Save All Records from the shortcut menu. In the displayed dialog box, select the .csv file format.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
55
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
----End
2.2.13 NodeB MML Command Collection Step 1 On the main topology of the M2000, right-click any NodeB and choose MML Command from the shortcut menu.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
56
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 2 In the MML Command window, select one or more NodeBs for MML command issuing, and the MML command execution result is displayed in the information display area.
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. Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
57
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
----End
2.2.14 NodeB License Collection 2.2.14.1 NodeB License Collection on the M2000 Step 1 On the M2000 main topology, choose License > NE license Management > NodeB.
Step 2 On the NodeB License Management tab page, select all records in the Shared/BASIC area. Right-click the selected records and choose Export from the shortcut menu.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
58
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
In the displayed dialog box, click Export and the files are exported as .csv files by default.
----End
2.2.14.2 NodeB License Collection on the U2000 Step 1 Log in to the U2000 and choose License > NE License Management > NodeB.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
59
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 2 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.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
60
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
----End
2.2.15 Property Data Collection You can use the U-Net to create property data for Mapinfo interaction. You can also export the planning results from the U-Net to Google Earth.
2.2.15.1 Precautions for Preparing Property Data Before preparing property data, you need to observe related precautions.
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.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
61
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Head of a Property Data File The head of a property data file describes information when the file is generated. A parameter and its value are separated by pressing Tab. For details about the file head format, see Table 2-1. Table 2-1 Format of the property data file head Parameter
Description
type
RAT of the feature data.
timestamp
Time when feature data is exported. Format: hh:mm:ss dd-mm-yyyy.
resolution
Precision of exporting feature data. The unit is meter.
xmin
Northwest longitude of the area from which feature data is exported. Feature data is exported based on the WGS84 coordinate system.
xmax
Southeast longitude of the area from which feature data is exported. Feature data is exported based on the WGS84 coordinate system.
ymin
Northwest latitude of the area from which feature data is exported. Feature data is exported based on the WGS84 coordinate system.
ymax
Southeast latitude of the area from which feature data is exported. Feature data is exported based on the WGS84 coordinate system.
x_num_pixels
Number of grids from which feature data is exported in the horizontal direction.
y_num_pixels
Number of grids from which feature data is exported in the vertical direction.
Body of a Property Data File The body of a property data file records the feature value of each geographic location. Currently, it records the latitude and longitude, cell information, and received signal level of each grid center. Each line in the body of a property data file is organized in the following format: longitude;latitude;index of the cells in the grid located in the preceding longitude and latitude coordinates;LAC-CI;downlink received signal level in the primary BCCH
2.2.15.2 Preparing Property Data You can prepare property data by creating a prediction group and calculating related counters in the group.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
62
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
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.
Step 1 Optional: Set global parameters for prediction. After you set global parameters for prediction, the new prediction groups have the same global parameters. The following figure shows an operation example. Figure 2-1 Properties
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 2 Create a prediction group. The following figure shows an operation example. Figure 2-2 New
Step 3 In the displayed dialog box, set prediction group name, whether to calculate immediately, and select prediction counters. Figure 2-3 shows an operation example (GSM). For counter description, see Table 2-3. Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
63
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Figure 2-3 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-4 shows an operation example. For parameter description, see Table 2-2, Table 2-3, and Table 2-4.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
64
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Figure 2-4 Creating a prediction group (2)
Table 2-2 Parameters on the General tab page in the UMTS Group Properties dialog box Parameter
Description
Resolution(m)
Prediction precision.
Polygon
Area calculated in prediction.
Cell Edge Coverage Probability
Probability of cell edge coverage, which is the probability that the receive signal strength is stronger than the threshold at the edge of a cell.
With Shadow
Specifies whether shadow fading is considered during calculation.
Indoor Coverage
Specifies whether penetration loss is considered during calculation.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
65
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Compare With DT/CW
Specifies whether to compare prediction results with one or more pieces of DT/CW data on the live network. The U-Net compares prediction results with DT/CW data on the live network only when DT/CW data has been imported and the counter Best Server, CPICH RSCP, CPICH Ec/Io, HSUPA RLC Peak Throughput, or HSDPA RLC Peak Throughput is selected. counter(DT/CW) indicates the value of this counter in DT/CW
data. For example, DL RSRP(DT/CW). counter(Prediction - DT/CW) indicates the counter difference
between the value to be planned and the value in DT/CW (the difference is obtained by subtracting the value in DT/CW from the planned value). For example, DL RSRP(Prediction - DT/CW). After this option is selected, the prediction result area is the same as the area of the selected DT/CW data. With MR/DT LinkLoss
Specifies whether to calculate link loss based on MR/DT data on the live network. You can click Advanced LinkLoss Parameter to set path loss parameters. For parameter description, see Table 2-5.
Table 2-3 Parameters on the Condition tab page in the UMTS Group Properties dialog box Parameter
Description
Signal Level(dBm)
Receive threshold of the downlink reference signal.
Terminal
UE type.
Service
Service type.
Mobility
Mobility type.
DLFrequencyBand
Downlink frequency band.
ARFCN
Absolute radio frequency channel number (ARFCN).
Table 2-4 Parameters on the Advanced tab page in the UMTS Group Properties dialog box Parameter
Description
HSUPA Schedule TTI
TTI for HSUPA scheduling.
MacroDiv Gain
Macro diversity gain.
Min CPICH Ec/Io
Threshold for the minimum signal to interference plus noise ratio (SINR).
Pilot Pollution Margin
Threshold for pilot pollution.
SHO Threshold
Threshold for soft handovers.
TopN Signal Level
Number of top receive levels to be ranked.
UL Cell AVG Ioc/Ior
Uplink neighboring cell interference factor.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
66
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Table 2-5 Parameters in the Advanced LinkLoss Parameter dialog box Parameter
Description
LinkLoss Matrix Creation Type
DT / MR: calculation based on DT/MR data. DT / MR + Prediction: calculation based on DT/MR data and propagation model prediction. If a cell has DT/MR data, the link loss matrix for the cell is created based on the DT/MR data. If a cell does not have DT/MR data, the link loss matrix for the cell is calculated using the propagation model.
DT/MR Priority
DT first: preferentially uses DT data. MR first: preferentially uses MR data.
DT/MR Data
Available DT/MR data.
Polygon
Area for calculation.
Source Layer
Source network layer for calculation. The path loss at the source network layer is used as the basis for calculating the path loss of the target network layer.
Target Layer
Target network layer for calculation. The path loss of the target network layer is calculated based on the path loss of the source network layer.
Offset(dB)
Path loss offset of Target Layer relative to Source Layer.
Step 5 Calculate a prediction group. 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.
----End
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
67
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
2.2.15.3 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 1 In the Explorer window, click the
tab.
Step 2 Choose Predictions > Groupx > DL RSRP from the navigation tree. Step 3 Right-click DL RSRP and choose DT Adjust Feature Database from the shortcut menu. The DT Adjust Feature Database dialog box is displayed, as shown inFigure 2-5. Figure 2-5 DT Adjust Feature Database
Step 4 Set related parameters in the displayed dialog box. For details about parameters, see Table 2-6. Table 2-6 Parameters in the DT Adjust Feature Database dialog box Parameter
Description
Drive Test File
DT data file. Selected from a drop-down list. The default value is All.
Clutter Resolution(m)
Indicates the clutter resolution. The default value is 300.
Clutter Shift Threshold(%)
Indicates the clutter shift threshold. The default value is 50.
Step 5 Click Adjust. ----End
2.2.15.4 Exporting Property Data Step 1 In the browser window, click the Operation tab. Step 2 Choose Predictions > Groupx > CPICH RSCP from the navigation tree. Step 3 Right-click DL RSRP and choose Export BIN By > Top Signal Level from the shortcut menu. The dialog box shown in Figure 2-6 is displayed.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
68
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Figure 2-6 Export By Top Signal Level
Step 4 Set the minimum value and the top N maximum receive levels to be exported. Step 5 Click Export. Step 6 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
2.2.16 Terminal Library Data Collection You can click download Terminal LIB and Terminal Type from Rulestore (Choose Help > Script Update from the OMStar main menu).
2.2.17 eNodeB Configuration Data Collection Step 1 Log in to the M2000 client and choose Maintenance > Backup Management > NE Backup.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
69
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 2 In the NE Backup window shown in the following figure, select eNodeB from the NE type drop-down list. After all NEs of the eNodeB type are displayed in the NE navigation tree in the left pane, select the check box of NE to select all NEs and click Backup.
Step 3 click Yes. In the Confirm dialog box shown in the following figure, click Yes to back up data.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
70
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
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.
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 M2000 server and the save path is displayed in the Path column.
Step 4 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 M2000 server to your local PC.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
71
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 5 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.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
72
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
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 M2000. The third-level node is the backup date. The backup XML configuration files are all named M2000.XML. ----End
2.2.18 PRS Perf Data Collection Step 1 Export the corresponding performance data files in CSV format from the PRS according to the data analysis requirements. Step 2 Edit the performance data files. 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. Or, 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.
The levels and formats of the GSM data:
BSC level:
BSCNAME Time TCH Traffic counterA …… counterN
CELL level:
BSCNAM E
BTSNAM E
CELLNAM E
Tim e
TCH Traffi c
counter A
… …
counter N
… …
counter N
The levels and formats of the UMTS data to be imported:
RNC level:
RNCNAME Time AMR Traffic counterA …… counterN
CELL level:
RNCNAM E
NODEBNAM E
CELLNAM E
Tim e
AMR Traffi c
counter A
The levels and formats of the LTE data to be imported:
ENODEB level:
ENODEBNAME Time Traffic_User_Avg counterA …… counterN
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
73
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
CELL level:
ENODEBNAM E
CELLNAM E
Tim e
Traffic_User_Av counter g A
… …
counter N
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.
2.2.19 UMTS Signaling Data Collection Step 1 Select “Monitor->Signaling Trace->Anonymous Policy Management” in the panel of U2000 to set the collection anonymous policy.
Step 2 Select “Anonymous policy” and “Enable anonymous policy” in the Anonymous Policy Management.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
74
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 3 Select “Monitor->Signaling Trace->Signaling Trace Management” in the panel of U2000 to collect signal data.
Step 4 Taking UMTS Standard UE Trace for an example, select Standard UE Trace in UMTS at left tree and click the button “New”.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
75
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 5 Select the NE, Trace Duration and Running Mode in the panel of Standard UE Trace for signal collection, and then click the button of “Next”.
Step 6 Set the RNC ID, Trace type and IMSI for Signal collection, and then click the button “Finish”.
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
76
OMStar UMTS Data Collection Guide
2 General Principles for Data Collection
Step 7 After data collection task running, select a collection task and click the button “Export” to get the signal data.
----End
Issue 01 (2015-07-10)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
77
