MOP and Tools Used for LTE Parameter Audit

MOP for LTE Parameter Audit

MOP for LTE Parameter Audit Prepared by: NARENDER KUMAR/00298508 Date: 2016-06-04

(2010-07-0204)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Contents

1. 4G Cell Status Audit.................................................................................................3 1.1

Cell status audit.............................................................................................3

2. 4G Basic Planning, Configuration, EP audit..........................................................5 2.1

Planning and configuration consistency......................................................5

2.2

Configuration and EP consistency...............................................................9

2.3

PCI audit.......................................................................................................9

2.4

PRACH audit...............................................................................................11

2.5

ECGI audit..................................................................................................12

3. 4G Basic Switch and Threshold audit....................................................................16 3.1

4G basic switch and threshold audit...........................................................16

4. 4G External cell and neighbors audit....................................................................20 4.1

4G external cell and neighbors audit..........................................................20

5. 2G/3G basic switch and threshold audit................................................................23 5.1

2/3G basic switch and threshold audit........................................................23

6. 2G/3G external cell and neighbors audit...............................................................28 6.1

2/3G basic switch and threshold audit........................................................28

7. Conclusion……………………………………………………………………………………32


1.4G Cell Status Audit 1.1

Cell status audit

1.1.1 Rules All the live cells need to be active in the network. 1.1.2 Tool Used CME 1.1.3 Process Login U2000, open one planned area.  Export the Cell status: A. On the menu bar of the planned data area, choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode) or CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode). A dialog box is displayed for you to export the data you want to reconfigure in batches. B. Select the batch reconfiguration scenario, base station version, and related base stations, and click next. C. Select Custom MOC, set objects you want to export, and specify a save path for the exported file. D. Click Next. The CME verifies the configuration data to be exported. E. After the export is complete, click Finish.

(2010-07-0204)





Check Cell status:

(2010-07-0204)



2.4G Basic planning, Configuration, EP audit Planning and configuration consistency 2.1.1 Rules The configuration value should be same with planning value. 2.1.2 Tool OMSTAR 2.1.3 Process 

Backup NEs and download the configuration XML files from the M2000. Maintenance > Backup Management > Ne Backup

Select “BTS 3900”, when you choose NES you should select less than 1000 sites.

(2010-07-0204)



After backup all the NES, you should select the latest Backup time for all the NEs.

(2010-07-0204)



Then “Download to OSS Client”, choose a local route to save the configuration XML files..



Create an new project in OMSTAR Open OMSTAR and create a new project file > new project, fill a name. Next

(2010-07-0204)



LTE subject > LTE PCI audit, LTE ZC root sequence audit, LTE neighbors audit.

Import the configuration XML files.



Compare the planning database with configuration. Import the planning database as following way.

(2010-07-0204)



Match the corresponding parameter. Then click “parameter check”

We can see the result as the following. “Updating Engineer Parameters information via Configuration data” or “delete proprietary information about engineering parameters.”

(2010-07-0204)



2.2

Configuration and EP consistency

2.2.1 Rules The EP database should be same with configuration value. 2.2.2 Tool OMSTAR 2.2.3 Process Same with “2.1 planning and configuration consistency”, just choose the “live database” after you import the EP.

2.3

PCI audit

2.3.1 Rules Check the PCI Co FRQ & PCI conflict check, Co FREQ & PCI Distance check, PCI reservation check. Reuse Cell distance=1500m Reserved PCI range: 454 – 503. 2.3.2 Tool OMSTAR

(2010-07-0204)



2.3.3 Process    



Choose Analysis Task Management > Theme Function > LTE Subject, click LTE PCI Check. Double-click LTE PCI Check. The New Task window is displayed. Enter a Task Name. Click Next. In the New Task window, select the base stations whose data is to be analyzed on the NE Selecting tab page and set parameters for PCI checks on the Parameters Setting tab page. Click OK. The task is created and displayed in the task pane. After being created, the task starts to be executed by default. After the task execution is complete, the Status field in the task pane indicates that the task is successfully executed. Double-click or right-click in the task pane, choose Show Result to show the PCI check results. Four tab pages, Co FREQ &PCI Distance Check, Co FREQ& PCI MOD30 Check, Co FREQ& PCI Conflict Check, and PCI Reservation Check are displayed.



Click

to export the check result in a file.



Click If engineering parameters have been imported, the PCI check result can be displayed geographically in the Geographic Observation window, the location information about source cells and PCI conflict or confusion cells is displayed, and neighboring cells are identified by type using legends of different colors.

After finishing the analysis, you can get the result as the following.

(2010-07-0204)



2.4

PRACH audit

2.4.1 Rules Reuse Cell Radius=1500m Reserved PRACH range: 737 - 837 2.4.2 Tool OMSTAR 2.4.3 Process    



Choose Analysis Task Management > Theme Function > LTE Subject, click LTE ZC Root Check in the subject tree on the left. Double-click LTE ZC Root Check. The New Task window is displayed, enter a task name. Click Next. Select the base stations whose data is to be analyzed on the NE Selecting tab page and set parameters for ZC root checks on the Parameters Setting tab page. Click OK. The task is created and displayed in the task pane. After being created, the task starts to be executed by default. After the task execution is complete, the Status field in the task pane indicates that the task is successfully executed. Double-click or right-click in the task pane, choose Show Result to display the ZC root check result. Three tab pages, Co FREQ &ZC Root Conflict Check, Co FREQ &ZC Root Distance Check, and ZC Root Reservation Check, are displayed.



Click



Click .If engineering parameters have been imported, the ZC root check result can be displayed geographically in the Geographic Observation window, the location information about source cells and ZC root conflict or confusion cells is displayed, and neighboring cells are identified by type using legends of different colors. Right-click the map and choose an item from the shortcut menu to switch the content of the geographic observation.



(2010-07-0204)

to export the check result in a file.



2.5

ECGI audit

2.5.1 Rules Check whether the cell ECGI (MCC + MNC + eNodeBId + CellId) is unique on the entire network. 2.5.2 Tool CME 2.5.3 Process On the menu bar of the planned data area, choose Advanced >Consistency Check. Create a new consistency check, select the all the LTE NES.

(2010-07-0204)



Select the “Check Conflict of ECGI”, then next.

“Select all”, then “finish”

(2010-07-0204)



You can export the result

(2010-07-0204)



3.4G Basic switch and threshold audit 3.1 4G basic switch and threshold audit 3.1.1 Rules Check the values base on the BASIC LINE. You need to maintain the basic line, once the switch or threshold changed we must updated the BASIC LINE. Customer requirement: LTE BASCI LINE-OMSTATR: LTE Baseline -OMstar.xlsx

3.1.2 Tool OMSTAR 3.1.3 Process 

Import the basic line (LTE BASCI LINE-OMSTATR) into OMSTAR

 Choose Parameter > LTE Config Parameters Check on the OMSTAR menu bar to enable the LTE configure Parameters check function.  In the LTE Config Parameters Check setting dialog box, set parameters as required, as shown in following:

(2010-07-0204)



 Original data path: Select the eNodeB configuration data to be checked. You can choose one or more eNodeB configuration files to check. To select multiple eNodeB files, put the files in a folder, and select the folder to perform the check. It is suggested to check the eNodeBs with same version during one process.  Save Path: Specify a path where you want to save the check result.  Language Setting: Set the interface and report language, either Chinese or English.  Select Mode: Select a product mode. Mode FDD and TDD correspond to different configuration parameter baseline templates.  Scene: Select a check scenario based on the actual service networking, we can choose the default for check all the parameters of the whole network. You can choose OPERATOR BASIC line for check the customer’s requirement.  Filter: In the selected scenario, filter parameters according to parameter types. The selected parameters will be checked, and other parameters will not be checked. OMStar V500R010 provides two parameter filtering indicators, Parameter_Type, and Subject. OMStar V500R010 check all parameters by default without filtering..  Combine by MO: In the check report exported, combine the check results of the configuration parameters that are of the same object level. Table 2 lists the managed objects (MOs) that can be combined. For details, see the .xml configuration file OMStarV500R010\client\conf\parameter\lteparameter.xml. Do not modify the file.  Output details: Output all check results, including the items that pass or fail the check. If this function is not enabled, only the failed items (the parameters that are not consistent with those defined in the baseline templates) are shown in the check report, but the items that pass the check (the parameters that are consistent with those defined in the baseline templates) will not be displayed. However, if this function is enabled, all check results are exported.

Result:  The detailed check results are recorded in the PassNum and ParaIDNotFound columns. The PassNum column records the parameters that are configured as the values defined in the baseline templates. The ParaIDNotFound column records the parameters that are not configured as the values defined in the baseline templates, as shown as following: Figure 1 Instruction sheet

(2010-07-0204)



Figure 2 Parameters Verification Result sheet

Figure 3 Summary Of Output Result sheet

(2010-07-0204)



 On the MoNotFound sheet, the MOs that exist in the baseline template but are not configured are displayed. (If you check the configuration of multiple eNodeBs at one time and an MO does not exist in one of the eNodeBs, the MO is regarded as the one that exist in the baseline template but are not configured, and is recorded on the MoNotFound sheet.)  Each MO sheet records the detailed MO check results of all eNodeBs. The cells rendered in red are the parameters that are not configured as the values defined in the baseline templates. The cells rendered in yellow are the parameters that exist in the baseline templates but are not configured. The cells that are not rendered but filled in with values are the parameters that are configured as the values defined in the baseline templates. Use LCELL as an example, as shown in Figure 5. Figure 5 MO sheet

(2010-07-0204)



4.4G External cell and neighbors audit 4.1 4G external cell and neighbors audit 4.1.1 Rules  

External cell: Check whether the parameter configuration for external LTE cells is consistent with that for the source cell within the system, redundant external cell. Neighbors: Check and restore unidirectional neighbors, more (50) or less (5) neighbors, overshot neighbors (5km), Co-site missing neighbors. 4.1.2 Tool CME, OMSTAR 4.1.3 Process -- CME

On the menu bar of the planned data area, choose Advanced >Consistency

Check. Then the process is same the ECGI audit (2.5) until “the Select Rules”. Select the following options. Then next. The others are same with the ECGI audit.

(2010-07-0204)



4.1.4 Process – OMSTAR  Select Analysis Task Management > Theme Function > LTE Subject > LTE Neighboring Cell Check.  Double click LTE Neighboring Cell Check. The New Rask window is displayed. Enter a task name. Click Next.  Select NEs about which data is to be analyzed on the NE Selecting tab page and set parameters for neighboring cell check on the Parameters Setting tab page. Click OK.  Then the task is created and displayed in the task pane. After being created, the task starts to be executed by default. After the task execution is complete, the Status field in the task pane changes to Finish.  Double-click a row following the Status field value in the task pane. The neighboring cell check result window is displayed. In the Neighbor LTE Cell Check Summarized Results area, the One-way Neighbors, Over Distance Neighbors, Too Many Too Few Neighbor Cells, External Neighbor Cell Parameter Inconsistency, Co-site Missing Neighbors, LTE Redundancy External Cell, GSM Redundancy External Cell and UMTS Redundancy External Cell and so on pages are displayed.

(2010-07-0204)



(2010-07-0204)



5.2/3G basic switch and threshold audit 5.1 2/3G basic switch and threshold audit 5.1.1 Rules The basic rule for switch and threshold regarding LTE fast return/reselection and other parameters is the Huawei default parameters in BSC and RNC side which are agreed with OPERATOR during Rollout. So every 2g and 3g site should follow this rules and parameters. 2G parameters: SET GCELLHOBASIC: IDTYPE=BYID, CELLID=2251, LTECELLRESELEN=YES; SET OTHSOFTPARA: Send2QuterFlag=YES; Reserved parameter 21=1048576 SET GCELLSOFT: IDTYPE=BYID, CELLID=30, SUPPORTCSFB=SUPPORT; SET GCELLPRIEUTRANSYS:IDTYPE=BYID, CELLID=0, GERANPRI=2, UTRANPRI=3, EUTRANPRI=6, THRUTRANHIGH=7, THRUTRANLOW=7, UTRANQRXLEVMIN=2, THREUTRANHIGH=7, THREUTRANLOW=7, EUTRANQRXLEVMIN=6; ADD GLTENCELL: IDTYPE=BYNAME, SRCLTENCELLNAME="KEN-1119-1_N", NBRLTENCELLNAME="KEN-1005_L-1", SPTRESEL=SUPPORT, SPTRAPIDSEL=SUPPORT; 3G parameters: Reselection MOD UCELLSIBSWITCH: CellId=2251, SibCfgBitMap=SIB19-1; MOD UNODEB: IDTYPE=BYID, NodeBId=0, NodeBProtclVer=R9; MOD UCELLSELRESEL: CellId=2251, SPriority=3; ADD UCELLNFREQPRIOINFO: CellId=2251, EARFCN=1650, NPriority=5, ThdToHigh=7, EQrxlevmin=-64, BlacklstCellNumber=D0; ADD UCELLNFREQPRIOINFO: CellId=2251, EARFCN=2850, NPriority=6, ThdToHigh=7, EQrxlevmin=-64, BlacklstCellNumber=D0; Open fast return SET UCORRMALGOSWITCH: HoSwitch=HO_UMTS_TO_LTE_FAST_RETURN_SWITCH-1; SET UCORRMPARA: PerfEnhanceSwitch3=PERFENH_PS_FAST_RETURN_LTE_SWITCH-1; ADD UCELLHOCOMM: CellId=0, FastReturnToLTESwitch=PERFENH_PS_FAST_RETURN_LTE_SWITCH-1 & HO_UMTS_TO_LTE_FAST_RETURN_SWITCH-1;

(2010-07-0204)



5.1.2 Tool CME 5.1.3 Process We need to follow below process and do the audit in order to get the data from CME online.

After That Go to Planned area which your created & export GSM Application

Go to Export and Export Cell Parameter Data

(2010-07-0204)



Choose the BSC for which you want to audit the parameters by selecting NE type

Choose all the specified parameters by writing the MO which we want

(2010-07-0204)



For “OTHSOFTPARA” parameter audit, please “LST OTHSOFTPARA” and export Process for UMTS parameters Export through CME

Choose RNC

(2010-07-0204)



Choose the Specific Parameters for UMTS by searching the MO which we want

Save in to excel or text file always in order to get full export in case of too large data

For “UCORRMPARA, UCORRMALGOSWITCH, UNODEB” parameters audit, please “LST” and export

(2010-07-0204)



6.2/3G external cell and neighbors audit 6.1 2/3G basic switch and threshold audit 6.1.1 Rules The basic rule for switch and threshold regarding LTE fast return/reselection and other parameters is the Huawei default parameters in BSC and RNC side which are agreed with OPERATOR during Rollout. So every 2g and 3g site should follow this rules and parameters. 2G External & NBR cell: ADD GEXTLTECELL: EXTLTECELLNAME="cell", MCC=“604", MNC=“02", ENODEBTYPE=MACRO, CI=x, TAC=X, FREQ=1650, PCID=X, EUTRANTYPE=FDD; ADD GEXTLTECELL: EXTLTECELLNAME="cell", MCC=“604", MNC=“02", ENODEBTYPE=MACRO, CI=x, TAC=X, FREQ=2850, PCID=X, EUTRANTYPE=FDD; ADD GLTENCELL: IDTYPE=BYNAME, SRCLTENCELLNAME="KEN-1119-1_N", NBRLTENCELLNAME="KEN-1005_L-1", SPTRESEL=SUPPORT, SPTRAPIDSEL=SUPPORT; Every GSM cell need to add LTENCELL, this one must be audit 3G External & NBR cell: ADD ULTECELL:LTECELLINDEX=11,LTECELLNAME="RAB-1004_L3",EUTRANCELLID=26625027,MCC="604",MNC="02",TAC=1099,CNOPGRPINDEX=0,CELLPHYID= 338,LTEBAND=3,LTEARFCN=1650; ADD ULTECELL:LTECELLINDEX=11,LTECELLNAME="RAB-1004_L6",EUTRANCELLID=26625032,MCC="604",MNC="02",TAC=1099,CNOPGRPINDEX=0,CELLPHYID= 338,LTEBAND=7,LTEARFCN=2850; ADD ULTENCELL: RNCID=301, CELLID=501, LTECELLINDEX=268; Every UMTS cell need to add LTENFREQ, this one must be audit 6.1.2 Tool CME 6.1.3 Process Open M2000:-CME:-GO to create planned area

(2010-07-0204)



After successful creation, open planned area

For NBR and external information in GSM, we need to go to export & export Radio Network Planning data

(2010-07-0204)



Choose the required external & NBR data as wanted.

For NBR and external information in UMTS, we need to go to export & export Radio Network Planning data.

Choose the required external & NBR data as wanted

(2010-07-0204)



Save in to excel or text file always in order to get full export in case of too large data

(2010-07-0204)



7 Conclusion LTE network parameter audit is key part LTE RF Optimization. We should perform whole network audit on weekly basis or as required. Parameter Audit using OMSTAR tool is very easy and reliable.

Together we can make it!

(2010-07-0204)


MOP and Tools Used for LTE Parameter Audit

Recommend Documents