Академический Документы
Профессиональный Документы
Культура Документы
,
Ltd.
Product Name
Security Level
OMStar
INTERNAL
Product Version
Pages
V500R010
Total 45 pages
Prepared By
Date
2014-09-15
Reviewed By
Date
2014-09-15
Approved By
Date
2014-10-20
INTERNA L
Change History
Date
Version
Description
Author
2014-10-20
03
2014-09-15
02
2014-08-15
01
First verison
2014-10-20
INTERNA L
Contents
1 OMStar Data Source Overview .................................................................................................. 1
2 General Principles for Data Collection ..................................................................................... 2
2.1 NIC Data Collection ..........................................................................................................................................................2
2.2 Manual Data Collection ....................................................................................................................................................2
2.2.1 BSC/ RNC Configuration Data Co llect ion ..........................................................................................................2
2.2.2 BSC/ RNC Traffic Statistics Collection................................................................................................................5
2.2.3 BSC/ RNC Alarm Log Collection .........................................................................................................................7
2.2.4 BSC/ RNC MML Packet Co llect ion .....................................................................................................................8
2.2.5 BSC/ RNC CHR/M R Data Co llect ion ..................................................................................................................8
2.2.6 BSC/ RNC Operat ion Log Collection .................................................................................................................11
2.2.7 NodeB Configuration Data Collection...............................................................................................................12
2.2.8 NodeB Traffic Statistics Collection (.csv).........................................................................................................13
2.2.9 NodeB Traffic Statistics Collection (.mrf) ........................................................................................................15
2.2.10 NodeB Alarm Log Co llect ion ...........................................................................................................................18
2.2.11 NodeB MM L Co mmand Collection .................................................................................................................22
2.2.12 NodeB License Collection .................................................................................................................................24
2.2.13 Co-Site Information Collection.........................................................................................................................25
2.2.14 eNodeB Configuration Data Co llect ion ..........................................................................................................26
I. Collecting eNodeB Configurat ion Data Using the M2000
II. Co llecting eNodeB Configuration Data Using the NIC (Co -Dep loyed with the M2000)
26
30
35
36
2014-10-20
ii
INTERNA L
Data
Data Source
Controller (BSC/RNC)
Configuration data
Controller BAM
Traffic statistics
Controller BAM
Alarm logs
Controller BAM
MML packets
WEB LMT
CHR
Controller BAM
MR
Controller BAM
Configuration data
M2000
Traffic statistics
M2000
Alarm logs
M2000
MML packets
M2000
License
M2000
Configuration data
M2000
Traffic statistics
M2000
Alarm logs
M2000
CHR
M2000
MML packets
M2000
NodeB
eNodeB
2014-10-20
INTERNA L
2014-10-20
INTERNA L
Step 2 Enter and execute the EXP CFGMML command. In the command output, the save directory for
configuration data is displayed.
2014-10-20
INTERNA L
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
2014-10-20
INTERNA L
For Neighboring GSM Cell Analys is you need to start the Measurement of Neighboring GSM Cell
Performance by M2000. The operate step as below.
(1) Login M2000 client, and select Performance > Measurement Management.
2014-10-20
INTERNA L
(2) Select the Measurement of Neighboring GSM Cell Performance and BSC 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 GSM Cell Performance.
2014-10-20
INTERNA L
Step 2 Use the File Manager tool to download alarm logs. The file directory is
\bam\version_b\ftp\COLLOGI NFO\ALM-LOG. Click Download to download the files.
----End
2014-10-20
INTERNA L
To use the GSM call drop in-depth analysis function of the OMStar, you are advised to enable the MR
and signaling messages to be contained in the CHR by running the SET GCSCHRCTRL command.
2014-10-20
INTERNA L
2014-10-20
INTERNA L
To use UMTS MR data for neighboring cell analysis, run the SET UMRCTRL and SET UMRSCOPE
commands to enable MR collection of neighboring cells. For details about the commands and the
impacts of the commands on NEs, see the related MML command reference.
In the SET UMRCTRL co mmand, set MR Trace Traffic Type to TRAFFIC_AMR, MR Intra-freq
Measurement period to D12, and MR Report Configure S witch to a proper value according to the actual
situation.
SET UMRCTRL:
RTRAFFICTYPE=TRAFFIC_AMR-1&TRAFFIC_VP-1&TRAFFIC_BE-1&TRAFFIC_OTHER1, MRINTRAFREQPERIOD=D12,
MRRPRTCFGSWITCH= MR_PRD_I NTRA_FREQ_MEAS_SWITCH_1-1&MR_EVT_INTRA_F
REQ_MEAS_SWITCH_2-1&MR_PRD_I NTER_FREQ_MEAS_SWITCH_3-1&MR_EVT_I NTE
R_FREQ_MEAS_SWITCH_4-1&MR_PRD_INTER_RAT_MEAS_SWI TCH_5-1&MR_EVT_I N
TER_RAT_MEAS_SWITCH_6-1&MR_DL_BLER_MEAS_SWITCH_7-0&MR_UE_TX_POWER_
MEAS_SWITCH_8-0&MR_UL_SIR_MEAS_SWITCH_9-0&MR_LCS_MEAS_SWITCH_10-0&MR
_RACH_MEAS_SWITCH_11-0,
MRLCSMET HODSWITCH=LCS_AGPS_UEBASED_SWITCH_1-0&LCS_AGPS_STANDALONE_
SWITCH_2-0&LCS_CELLID_RTT_SWITCH_3-0, MRDLBLERPERIOD=D12,
MRUETPPERIOD=D12, MRULSIRPERIOD=D12, MRLCSPERIOD=D12;
In the SET UMRSCOPE command, specify Scope Type to set the NE objects to be enabled.
For V9R12\V9R13\ V9R14
SET UMRSCOPE: SCOPETYPE=ByRack, SRN=0, SN=0, SSN=0, MRSCOPECTRL=ON;
For V9R15 and the later version
2014-10-20
10
INTERNA L
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.
2014-10-20
11
INTERNA L
Step 2 Use the File Manager tool to download alarm logs. The file directory is
\bam\version_b\ftp\COLLOGI NFO\OPT-LOG. Click Download to download the files to a local PC.
----End
2014-10-20
12
INTERNA L
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.
----End
2014-10-20
13
INTERNA L
Choose Task Management > File Interface > Performance Data Export.
Step 2 On the Task Management tab page, choose File Interface > Performance Data Export.
Step 3 Double-click Performance Data. In the displayed attribute dialog box, check the enabled NodeB
traffic statistics measurement tasks on the M2000 and the FTP directories that store the NodeB traffic
statistics. Navigate to the corresponding FTP directory to obtain the traffic statistics files of the NodeB
in .csv format.
2014-10-20
14
INTERNA L
For traffic statistics files in .csv format, the OMStar supports only the granularity period of 15 minutes,
as shown in the following figure:
----End
2014-10-20
15
INTERNA L
In the folder of each NodeB, the raw and compressed NodeB traffic statistics file in .mrf format is
stored in the gz folder, which can be directly obtained.
2014-10-20
16
INTERNA L
On the M2000 main topology, right-click a selected NodeB and choose Properties from the shortcut
menu to query the FDN of the NodeB.
2014-10-20
17
INTERNA L
2014-10-20
18
INTERNA L
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.
2014-10-20
19
2014-10-20
INTERNA L
20
INTERNA L
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.
----End
2014-10-20
21
INTERNA L
2014-10-20
22
INTERNA L
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.
----End
2014-10-20
23
INTERNA L
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.
2014-10-20
24
INTERNA L
In the displayed dialog box, click Export and the files are exported as .csv files by default.
----End
2014-10-20
25
INTERNA L
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.
----End
2014-10-20
26
INTERNA L
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 In the Confirm dialog box shown in the following figure, click Yes to back up data.
2014-10-20
27
INTERNA L
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.
2014-10-20
28
INTERNA L
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.
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.
2014-10-20
29
INTERNA L
The downloaded configuration files are saved in the structure shown in the following figure.
The first-level node is the name of the folder for saving the configuration files. The second-level node is
the name of a base station displayed on the M2000. The third-level node is the backup date. The backup
XML configuration files are all named M2000.XML.
----End
II. Collecting eNodeB Configuration Data Using the NIC (Co-Deployed with the M2000)
Step 1 Log in to the NIC.
1.
Enter the IP address of the NIC server in the address bar of the Internet Explorer.
2.
If the following page is displayed, click Continue to this website (not recommended).
2014-10-20
30
INTERNA L
3.
4.
Enter the user name and password of the M2000 and the verification code. Then, click Login.
2014-10-20
On the Network Information Collection page, click the drop-down arrow of Create Task and
choose Based on Customize Collection Item from the drop-down list to collect data by collection
item.
31
2.
2014-10-20
INTERNA L
Enter a task name in Task Name and set Product Type to LTE. Then, click Next.
32
3.
2014-10-20
INTERNA L
33
4.
INTERNA L
5.
2014-10-20
34
INTERNA L
Click the Result Information tab and click Download in the Task Result column to download the
collected data to your local PC, as shown in the following figure.
----End
2014-10-20
35
INTERNA L
II. Collecting eNodeB Traffic Statistics Using the NIC (Co-Deployed with the M2000)
Step 1 Customize collection items on the NIC.
2014-10-20
36
INTERNA L
2014-10-20
37
INTERNA L
Step 6 After the collection task is complete, save and download the data to your local PC.
2014-10-20
38
INTERNA L
----End
2014-10-20
39
INTERNA L
If NIC data package is directly imported, the OMStar determines the homing eNodeB based on the NE
folder of the packets when importing MML packets.
If MML packets are manually imported, the information in yellow following three plus signs (+) is the
information used by the OMStar to identify the packet homing eNodeB. By default, the information
indicates the name of the eNodeB. Otherwise, the OMStar cannot identify the MML packets and
therefore fails to import them.
+++
O&M
eNodeB11_JJFA
2014-07-21 14:44:18
#9533
Enable
Port Status =
Number of RX Packets(packet)
Number of RX Discarded Packets(packet)
Number of TX Packets(packet)
Number of TX Discarded Packets(packet)
Up
1634600
0
=
=
5269
0
(Number of results = 1)
---
END
The eNodeB information contained in MML packets needs to be independently set. If the MML packets
fail to be imported because they do not contain eNodeB information, do as follows to set the eNodeB
information before MML packet collection:
For eRAN3.0 and earlier versions:
Run the SET OFFICENAME command with System Name set to the eNodeB name.
The following figure shows detailed information about this command.
2014-10-20
40
INTERNA L
After the preceding settings, the eNodeB name is displayed after three plus signs (+) in collected MML
packets by default. In this case, the OMStar can import MML packets in batches.
2014-10-20
41
INTERNA L
2014-10-20
42