Data Collection by Using the NIC

Data Collection by using the NIC

There are two kinds of NIC tool, Stand-alone Mode and Co-Deployment Mode.

We still recommend using NIC in Co-Deployment Mode.

1. For the NIC stand-alone version, please refer to section "Error: Reference source not found."

2. For the NIC in Co-Deployment Mode, please refer to section 2"Using NIC Stand-Alone Version."

NOTE

All data collected from customers' offices for analysis by the OMStar can be taken out of the customers' offices only after consent is given by the customers.

Obtain the CHR and PCHR data for analysis with written consent of the customer.

Do not transmit raw network data outside EEA area and to China.

Delete data after using it. Do not keep any permanent file that contains plaintext private data, such as raw files, reports, and database.

The plaintext private data, such as IMSI, ESN, and IMEI, should be masked in the report provided for the customer. This type of data should be expressed in such methods as anonymization, division, and code.

Do not execute collection tasks during busy hours.

1 Using NIC in Co-Deployment Mode

The following steps show how to use the NIC in co-deployment mode. For details, see related

sections.

1. Start the NIC in co-deployment mode.

2. Collect data.

1.1 Procedure for Logging In to the NIC in Co-Deployment Mode

a) 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.

2023-4-21 Page 1 of 42


NOTE

If M2000 established SSL to register safely,then need to set certificate in the IE. The method is as follows:

open the IE tool –>Internet option –> content -> certificate -> import the right certificate

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.

b) In the NIC login window, type the user name, password, and verification code.

2023-4-21 Page 2 of 42


NOTE

If the verification code is illegible, you can click Reset to refresh the verification code. After that, you need to type the password again.

c) Click Login. If the login fails, check whether the NIC service has been started by referring

to Error: Reference source not found

----End

Overview of NIC in Co-Deployment Mode

2023-4-21 Page 3 of 42


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.

1.2 Using NIC in Co-Deployment Mode to collection data

After preparations, use the NIC in co-deployment mode to collect data in the specific collection

scenarios by referring to sections "Collecting GSM Data" to "Collecting data for RNC and NodeB

PMI."

After data collection, view data collection results by referring to section "Viewing the Collection

Result."

2 Using NIC Stand-Alone Version

NOTE

The NIC installation path must be an absolute path. It is a combination of English letters, numbers, underlines, and hyphens. It does not

support Chinese characters, garbled characters, and spaces.

The NIC cannot be installed by overlapping the installation path of the previously installed version.

The main program language edition for the NIC installation must be consistent with the NE language edition.

The following section describes the procedure for installing NIC V100R006C00SPC500 and later versions.

The last version of stand-alone is NIC V100R006C00SPC800. The WebNIC is from the version of iManager M2000 V200R11C01SPC230 start. It

does not need to install independently.

2.1 Installing the NIC Tool

Obtain the NIC package NICV100R006C00SPC***.exe, and start the NIC console. Then,

do as follows:

Double-click NICV100R006C00SPC***.exe. In the displayed dialog box, select a

temporary path for decompressing the package, and click OK.

2023-4-21 Page 4 of 42


In the directory saving the decompressed files, click NIC.exe. The NIC Console dialog box is

displayed, as shown in step 3.

When the NIC Console dialog box is displayed, perform related operations on the NIC console:

----End

2.2 Using NIC Stand-Alone Version

The following steps show how to use the NIC stand-alone version. For details, see related

sections.

Obtain and install the mediation matching the NE version.

Start the NIC and create an NE.

Collect data.

2023-4-21 Page 5 of 42


2.3 Installing the Mediation Matching the NE Version

Precautions for Installing the Mediation

The mediation for each NE involved should be installed for SingleRAN check, including the

mediations of GSM NEs (GBSC and GBTS), UMTS NEs (RNC and NodeB), and eNodeB.

NOTE

The main program language edition and mediation language edition for the NIC installation must be consistent with the NE language

edition.

You must install the mediation matching a specific NE version by choosing NIC Tools Suite > Mediation layer manager. Double-clicking the

setup program to install the mediation is not allowed.

The following section describes the procedure for installing the mediation of NIC V100R006C00SPC500 and later versions.

You need to configure "Server Proxy Configuration" to collect NodeB data.

Procedure for Installing the Mediation for NIC V100R006C00SPC500 and Later Versions

Choose NIC Console > Mediation Packages Manager.

Use the Mediation Packages Manager to install the mediation of each NE version. If you install a

mediation by double-clicking the mediation package, the mediation may be installed in an

incorrect directory.

Click Install From file.

Select a mediation file to install. Mediation files have three formats: .exe, .tar, and .zip. In the

2023-4-21 Page 6 of 42


Files of Type field, select a required format.

The language of the mediation package whose name contains CHS or ENG must be consistent

with the language of the NIC main program.

After the installation of the mediation package is complete, click Exit.

----End

2.4 Using the NIC to Collect Data

Overview of NIC GUI

2023-4-21 Page 7 of 42


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.

Creating an NE

NOTE

This section describes how to create a BSC manually on the NIC. For details about how to import NEs in batches, see the FAQ.

Start the NIC service.

Click Start NIC in the NIC Console, as shown in the following figure:

Choose NE Management > NE Information Maintenance.

2023-4-21 Page 8 of 42


Select the NE type.

For GSM NEs, select BSC6900 GSM, as shown below:

For UMTS NEs, select BSC6900 UMTS, as shown below:

2023-4-21 Page 9 of 42


For GU dual-mode NEs, select BSC6900 GU, as shown below:

For LTE NEs, select eNodeB, as shown below:

Configure the NE connection information (use UMTS as the example)

2023-4-21 Page 10 of 42


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.

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

2023-4-21 Page 11 of 42


NodeB before selecting yes.

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

Creating a Collection Task

After preparations, use the NIC stand-alone version to collect data in the specific collection

scenarios by referring to sections 2.5"Collecting GSM Data" to 2.9"Collecting data for RNC and

NodeB PMI."

After data collection, view data collection results by referring to section 2.10"Viewing the

Collection Result."

2.5 Collecting GSM Data

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.

2023-4-21 Page 12 of 42


Set Task Name, and select GSM from the Product Type drop-down list box, and select

BSC6900GSM_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.

Task Execution Type: You are recommended to select Instant. If you select Scheduled, you also

need to set the execution time.

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).

2023-4-21 Page 13 of 42


Select Display by NE type. Select a BSC under the BSC6900 GSM node in Optional NEs, and

move the selected BSC 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, when you select a BSC/RNC, the BTSs/NodeBs under the selected

BSC/RNC are also selected. 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

2023-4-21 Page 14 of 42


each NE are correct, and click Next.

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.

After ensuring that the collected information is correct, click Finish to start executing the

collection task.

2023-4-21 Page 15 of 42


----End

2.6 Collecting UMTS Data

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.

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.

2023-4-21 Page 16 of 42






Product type:Choice “UMTS”

Scenario group: Choice “SOP” scenario(RNC and NodeB scenario group name change for

“SOP” after the version of V9R14C00SPC200). Choice “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 scenario and NodeB SOP scenario when you

choice “SOP” scenario, to ensure you can collect the SOP data of RNC and NodeB at the same

time.






2023-4-21 Page 17 of 42


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.




2023-4-21 Page 18 of 42






downloaded packet.

2023-4-21 Page 19 of 42



collection task.

----End

2.7 Collecting GSM and UMTS Data

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.

Set Task Name, and select SingleRAN from the Product Type drop-down list box, and select

2023-4-21 Page 20 of 42


BSC6900GU_SOP from the Scenario(Group) drop-down list box.










2023-4-21 Page 21 of 42


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.




2023-4-21 Page 22 of 42






downloaded packet.

2023-4-21 Page 23 of 42



collection task.

----End

2.8 Collecting LTE Data

If the versions of the eNodeBs to be inspected are all LTE V100R005C00SPC360 or later, see the

instructions in section Error: Reference source not found"Collecting Data Based on the Scenarios

of the NIC" Error: Reference source not foundError: Reference source not foundfor data

collection. Otherwise, see the instructions in sections "Editing NIC Scenario" and "Creating a

Collection Task Based on the Scenario."

Editing NIC Scenario

Scenario Management

2023-4-21 Page 24 of 42


Default ScenariosLTECommonOMSTAR_Check.

Add 4 collection items in all eNodeB types. (such as the blue part)

License Information

Querying patch on NE

eNodeB Information Query

Software Version Query

2023-4-21 Page 25 of 42


Save the Customized Scenario.

Creating a collection task based on the Scenario

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.

2023-4-21 Page 26 of 42


Set Task Name, and select LTE from the Product Type drop-down list box, and select Common

from the Scenario(Group) drop-down list box, then choose OMSTAR Check.

Set collection data for the beginning and ending time: 00:00-00:00

2023-4-21 Page 27 of 42


Beginning and ending time for data collection related to the inspection scene,

specific requirements are as follows:

According to the days of inspection, collecting data of the last day;

According to the weeks of inspection, collection of data in the last 7 days;

According to the months of inspection, collection of data in the last 7 days;

According to the Quarters of inspection, collection of data in the last 7 days;(Priority)

Select the selection of the Network Element object: (select about 200-250 eNodeBs every time)

2023-4-21 Page 28 of 42


Next



collection task.

2023-4-21 Page 29 of 42


----End

LTE FDD single-mode inspection data collection

Note: Is suitable for DBS 3900 LTE and BTS 3900 LTE

Click the small triangle behind of“Create Task” ->Select“Based on Scenario”

Write“Task Name”->Select“Product Type”==LTE-> Select“Scenario(Group)”==Common-

>Select“LTE FDD Deep Inspection Scene”-> “Next Step”

2023-4-21 Page 30 of 42


Note：If don’t have LTE FDD Deep Inspection Scene, select OMSTAR_Check(Select

OMSTAR_Check(TDD) when LTE TDD)。

Set collection data for the beginning and ending time：00：00-00：00

Beginning and ending time for data collection related to the inspection scene,

specific requirements are as follows:

collection of data in the last 7 days;( Priority)

Select the selection of the Network Element object:

2023-4-21 Page 31 of 42


Next

Next

Confirm the collected information, and finish.

2023-4-21 Page 32 of 42


LTE FDD multimode inspection data collection(SRAN CO-MPT)

Note: Is suitable for BTS 3900 only

Scenario Management

Create a new scenario task, product type select Single RAN.

2023-4-21 Page 33 of 42


Save as the new scenario.

Use the new scenario to collect the data.

2.9 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.

2023-4-21 Page 34 of 42


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.

2.9.1 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 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.)

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 2.9.2"Collecting the RNC and NodeB Data Separately and

Creating a Data Package."

2023-4-21 Page 35 of 42


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.

Return to the Task Management window to create a collection task, choose the SOP scenario

group, and select the UMTS and NodeB collection scenarios.

2023-4-21 Page 36 of 42


----End

2.9.2 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 2.9.1"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.

Create a UMTS_SOP collection task and obtain an RNC data package.

2023-4-21 Page 37 of 42


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.

2023-4-21 Page 38 of 42


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

2.10 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.

2023-4-21 Page 39 of 42


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.

2023-4-21 Page 40 of 42


NOTE

Task IDs are generated randomly, for example, 10002, 10003, and 10004.

Check whether the task ID folder saves the collection task created by the user based on the

collection task name in the folder.

After data collection by using the NIC in co-deployment mode, collection results are downloaded

and saved through a web page, as shown in the following figure:

Collection results are downloaded in .zip format. The naming convention of the data package is

collection task name_timestamp, as shown in the following figure:

NOTE

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.

2023-4-21 Page 41 of 42


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.

----End

2023-4-21 Page 42 of 42

Documents

Data Collection by Using the NIC