Beruflich Dokumente
Kultur Dokumente
V500R012C00SPC200
Release Notes
Issue 01
Date 2016-03-04
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 commercial cont ract made between
Huawei and the customer. All or partial products, services and features described in this document may not
be within the purchased scope or the usage scope. Unless otherwise agreed by the cont ract, 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. E very 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.
Website: http://www.huawei.com
Email: support@huawei.com
OMStar Release Notes About This Document
Author
Prepared By Han Haowei (employee Date 2016-03-04
ID: 00151425)
Reviewed By Guan Qi (employee ID: Date 2016-03-04
00332981)
Tested By Qi Peizhi (employee ID: Date 2016-03-04
00143926)
Approved By Wang Qiang (employee Date 2016-03-04
ID: 00302808)
Change History
Issue Date Author Description
01 2016-03-04 Han Haowei (employee ID: This issue is the first official
00151425) release.
Contents
4 V500R012C00SPC200.................................................................................................................. 11
4.1 Feature Updates..............................................................................................................................................................................11
4.2 Deleted Feature ..............................................................................................................................................................................14
4.3 Resolved Issues ..............................................................................................................................................................................14
4.4 Known Issues..................................................................................................................................................................................14
5 V500R012C00SPC100.................................................................................................................. 15
5.1 Feature Updates..............................................................................................................................................................................15
5.1.1 New Feature ................................................................................................................................................................................15
5.1.2 Updated Feature..........................................................................................................................................................................15
5.1.3 Deleted Feature ...........................................................................................................................................................................15
5.2 Resolved Issues ..............................................................................................................................................................................15
5.3 Known Issues..................................................................................................................................................................................16
5.4 ASP Relation ...................................................................................................................................................................................18
6 V500R012C00................................................................................................................................ 19
6.1 Feature Updates..............................................................................................................................................................................19
6.1.1 New Features...............................................................................................................................................................................19
1 Version Requirements
This chapter describes the versions of the NE, other software, operating system (OS), and
database that match with OMStar V500R012C00SPC200 and antivirus scanning results.
BSC6910 V100R014C00
BSC6900 V900R015C00
BSC6910 V100R015C00
BSC6900 V900R015C01
BSC6910 V100R015C01
BSC6900 V900R016C00
BSC6910 V100R016C00
BSC6900 V900R017C00
BSC6910 V100R017C00
Product Version
BSC6900 V900R017C10
BSC6910 V100R017C10
BSC6900 V900R018C00
BSC6910 V100R018C00
BSC6910 V100R014C00
BSC6900 V900R015C00
BSC6910 V100R015C00
BSC6900 V900R015C01
BSC6910 V100R015C01
BSC6900 V900R016C00
BSC6910 V100R016C00
BSC6900 V900R017C00
BSC6910 V100R017C00
BSC6900 V900R017C10
BSC6910 V100R017C10
BSC6900 V900R018C00
BSC6910 V100R018C00
BTS3900 V100R009C00
BTS3900 V100R010C00
BTS3900 V100R010C10
BTS3900 V100R011C00
BTS3900 V100R011C10
Product Version
BTS3900 V100R009C00
BTS3900 V100R010C00
BTS3900 V100R011C00
BTS3900 V100R011C10
Product Version
Scanning Result OK
Scanning Result OK
Scanning Result OK
Scanning Result OK
Scanning Result OK
2 Version Compatibility
3 Important Notes
Before using OMStar V500R012C00SPC200, verify that Microsoft Office 2007 or 2013
has been installed on the local PC.
You are advised not to open a .doc, .docx, .xls, or .xlsx document when a report is being
generated. Otherwise, the report may not be generated properly.
You are advised not to copy and paste a report when the report is being generated,
ensuring that the report is generated properly.
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 OMStar
projects. Saving raw data or backing up the database is not allowed. Delete the project in
the Project Manager window.
To protect user privacy, you must collect anonymized personal data from source devices.
The OMStar provides a password authorization mechanism for data access and 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.
The OMStar is a Huawei internal tool. Therefore, it should not be released to, introduced
to, and recommended to customers. This document is only for internal use.
The OMStar is a stand-alone tool. Therefore, the OS and antivirus software are not
contained in the released software. You need to periodically update the security patches
of the OS and antivirus software.
The OMStar collects statistics about the use of each service feature and function to learn
each service function and tool performance, facilitating tool optimization. The following
information is collected: ESN of the PC, feature startup time, feature end time, feature
ID, subfeature ID, running status, and user name (domain account). Collected
information is not the data from customers' networks. If the script update function is
enabled, the OMStar automatically performs the feature statistics function and uploads
the results to the RuleStore server.
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.
In theory, collisions are possible because 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 in-depth analysis, access failure in-depth analysis, signaling
browsing, and CHR browsing.
4 V500R012C00SPC200
Modified Features
The following table lists modified features of OMStar V500R012C00SPC200 compared with
OMStar V500R012C00SPC100.
Description The U2000 traffic statistic collection template is provided for LTE
BTS3900.
Implementation For LTE BTS3900, the U2000 traffic statistic collection template is
integrated in the OMStar software packages. After a user installs the
OMStar, the user can export the collection template from the OMStar.
Related 1. Start the OMStar and create a project.
Operation 2. In the U2000 traffic statistic import area, right-click anywhere and
choose U2000 Perf Template Management from the shortcut
menu.
Description All features related to report (Word and Excel files) export support
Microsoft Office 2013.
Implementation When a report is being exported from the OMStar, Microsoft Office
2013 is supported by default. In addition, exported reports can be
opened using Microsoft Office 2013.
Related 1. Start the OMStar and create a project.
Operation 2. Execute a feature and export analysis results.
Description In inter-RAT (UMTS/GSM) analys is, a check box for selecting data
analys is time is added in the task wizard window.
Implementation Before analysis, a user can customize the data analysis time as required.
Related 1. Start the OMStar, create a project, and import required data for
Operation inter-RAT (UMTS/GSM) analys is.
2. Create an inter-RAT (UMTS/GSM) analysis task.
Description In the result analysis window for LTE accurate optimization, operations
related to CHR log browsing are added.
Implementation In the result analysis window for LTE accurate optimization, a user can
right-click an analysis result and choose CHR Log Browsing from the
shortcut menu. This operation allows the user to correlate and query
detailed raw CHR information.
Related 1. Start the OMStar, create a project, and import required data for
Operation LTE accurate optimization analysis.
2. Create an LTE accurate optimization analysis task. In the analysis
result window, right-click an analysis result and choose CHR Log
Browsing from the shortcut menu.
Related 1. Start the OMStar, create a project, and import RNC configuration
Operation data, traffic statistics, and engineering parameters.
2. Create a UMTS antenna fault check task.
Table 4-8 Different locating results after different operations using the same data sources and
locating methods
Problem Number DTS2015102803309
Problem Description In normal cases, the locating results are the same after different
operations using the same data sources and locating methods.
However, when the following two operations are performed, the
locating results are different:
1. Use the comprehensive locating and AGSP database locating
methods. Import MRs, filter out duplicated engineering
parameters, change the locating method to comprehensive
locating, delete MRs, and import the MRs again. During this
operation, no analysis is performed.
2. Use the comprehensive locating method. Import MRs directly
and filter out duplicated engineering parameters. After the
preceding two operations, locating results are different.
Severity Warning
Workaround None
Influence Domain The deviation for the number of MRs is less than 1%, which
does not affect final results.
Progress Fault location is in progress.
5 V500R012C00SPC100
Table 5-1 Abnormal display of the geography window before and after PCI optimization
Workaround Select the geography display before and after PCI optimization
at the same time
Progress Close
2. [DTS2015092505720] [UMTS CHR Browse] After selecting three CHR records with
UE ID and statistic analysis, the result display type is 0 and ffff. The type should be
same.
Problem Description After selecting three CHR records with UE ID and statistic
analys is, the result display type is 0 and ffff. The type should
be same.
Severity Minor
Workaround None
Progress Close
Table 5-4 Inconsistent data records after importing the same RNC data with multiple processes
and a single process
Problem Number DTS2015091711466
Severity Minor
Table 5-5 Inconsistent records when changing the position type after MR import and running the
task
6 V500R012C00
Related 1. Start the OMStar and create a project for LTE Accurate
Operation Optimization.
2. Import the configuration data, performance date, CHR/MR data,
alarm data, and engineering parameters.
3. Create a task for LTE Accurate Optimization.
Feature ID IR-OMStar5.12-001
IR-OMStar5.12-003
IR-OMStar5.12-004
Related 1. Start the OMStar and create a project for VoLTE Subject Manager.
Operation 2. Import the configuration data, performance date, CHR/MR data,
alarm data, and engineering parameters.
3. Create a task for VoLTE Subjects Manager > Accurate
Optimization.
Feature ID IR-OMStar5.12-003
IR-OMStar5.12-004
Description The LTE PCI Optimization feature allows users to accurately locate
and analyze LTE PCI problems based on the LTE configuration data,
performance data, SIG data, and engineering parameters.
Feature ID IR-OMStar5.12-006
IR-0000376763
Feature ID IR-OMStar5.12-007
Related 1. Start the OMStar and create a project for LTE Missing Neighbor
Operation Check.
2. Import the configuration data.
3. Create a task for LTE Missing Neighbor Check and select the
sub-function CA Group Missing Neighbor check and ACA Missing
Neighbor check.
Feature ID IR-OMStar5.12-013
IR-0000377667
Related 1. Start the OMStar and create a project for UMTS KPI analysis.
Operation 2. Import the configuration data, performance data, alarm data, and
operation log.
3. Execute UMTS KPI analysis and select the Object type of UCELL
for analysis. Select the correlation function based on KPI results.
Feature ID IR-OMStar5.12-010
Description The UMTS Voice Quality is a new feature to analyze the voice
silence, negative TOA, speech noise, and UL/DL peer silence from
the user dimension with PCHR/CHR data. Users can obtain detailed
statistic results of call logs with voice problem.
Implementation Add UMTS CHR Data in the data import module; add UMTS Voice
Quality in the Analysis Task Management module. Add UMTS
Voice Quality in the process of creating project. The analysis result
can be exported to files only.
Related 1. Start the OMStar and create a project for UMTS Voice Quality
Operation Analys is.
2. Import the PCHR data and UMTS CHR data.
3. Create a task for UMTS Voice Quality Analysis.
Feature ID IR-OMStar5.12-009
Updated Features
The updated features from OMStar V500R012C00 to V500R011C00SPC100 are as follows.
1. GUL interoperability Parameter Check
Description The interoperability parameter check rules are enhanced in the new
version. Reselection, Ping-Pong handover, fast return, and
coverage-base handover have been enhanced.
Implementation Add check rules in GUL interoperability Parameter Check, and new
check templates have been integrated. The operation is the same as
before. New templates can be imported by Template Management.
The analysis result can be exported to files only.
Related Start the OMStar and choose Parameter > GUL Interoperability
Operation Parameter Check .
Feature ID IR-OMStar5.12-008
Related 1. Start the OMStar and create a project for LTE TDD Uplink
Operation Interference Detection and Recognition.
2. Import the LTE configuration data, performance data, CHR data
and engineering parameters.
3. Create a task for LTE TDD Uplink Interference Detection and
Recognition.
Feature ID IR-0000381415
Description The analysis rules and supported signal type are enhanced in the new
version. It supports analysis CSFB problem with LTE signal only and
standard signal. The display type of results is the same as before.
Implementation Add new analysis rules in CSFB Single User Analys is. Analys is with
LTE Single only is integrated and standard signal is supported. The
operation and result type are the same as before. The analysis result
can be displayed on the GUI.
Deleted Feature
No feature is deleted from OMStar V500R012C00 to V500R011C00SPC100.
7 Related Documentation
NOTE
You must apply for permissions to obtain documentation from the website. If you visit
http://support.huawei.com for the first time, register with the website.
If your registration is successful, you will be informed of your user name and password within
two or three working days.
----End
In the displayed dialog box, enter the user name, password, and verification code and click
Login.
Step 3 After a successful login, choose Support > Software > Global Service > System
Integration Service > Mobile Network Integration Service > OMStar in the Product
Version pane.
Step 4 Select the different product versions, and enter the corresponding pages to download the
documents.
NOTE
You can also enter the product name in the Product Name text box on the home page of
http://support.huawei.com to search for documents specific to a product.
If the file name extension of a documentation package is in .hdx format, use HedEx Lite to view the
documents. You can obtain the software from Huawei customer service engineers.
----End