Analysis on LTE Geographic Observati on in Cit y C For internal use only
Prepared By
Han Haowei, Xiao Qianru
Date
Reviewed By
Date
Reviewed By
Date
Approved By
Date
Huawei Technologies Co., Ltd. All rights reserved
2014-07-09
Analysis on LTE Geographic Observation in City C
INTERNAL
Change History Date
Issue
Description
Author
2014.7.8
1.0
Drafted the case.
Han Haowei
2017-07-28
Huawei confidential. No spreading without permission.
i
Analysis on LTE Geographic Observation in City C
INTERNAL
Contents 1 Site Information ............................................................................................................................ 1 2 Background .................................................................................................................................... 1 3 Manual Neighboring Cell Planning.......................................................................................... 4 3.1 Selecting a Problematic Cell ............................................................................................................................ 4 3.2 Preparing Scripts Based on the Neighboring Cell Replanning Result .............................................................. 6 3.3 Drive Testing Result ......................................................................................................................................... 6
4 Summary......................................................................................................................................... 7
2017-07-28
Huawei confidential. No spreading without permission.
ii
Analysis on LTE Geographic Observation in City C
INTERNAL
1 Site Information In an LTE project (phase 1) in city C, Huawei provides over 200 eNodeBs. Tools used on the live network: U-Net, Probe/Assistant, and OMStar
2 Background All sites are deployed and connected at office L in city C on June 13th, 2014 (except that the indoor distributed sites are not deployed). China Unicom intends to conduct the first round of a drive testing at 00:00 on June 14, 2014. At the later phase of the project, the actual site data is not completely consistent with the planned data. Therefore, the neighboring cells or PCIs of some sites or cells are not planned or are incorrectly planned. To ensure drive testing accuracy, Huawei live network manager requires that rationality of the key information, such as PCIs and neighbor relationships on the live network, be checked before the drive testing. The neighbor relationships are checked by the OMStar. The check result shows that, in some key areas, unidirectional neighboring LTE cells are configured, insufficient neighboring cells are configured, parameters of external neighboring cells are inconsistent, or the configuration of co-site neighboring cells are missing. Therefore, the live network manager decides that all neighboring cell configuration problems be resolved before the drive testing. The following table lists details about the revealed problems.
Neighboring Cell Configuration Problem
Number of Problematic Cells
Unidirectional neighboring cells
30
Insufficient configuration of neighboring cells
26
External neighboring cell parameter inconsistency
5
Missing configuration of co-sited neighboring cells
7
External neighboring cell parameter inconsistency, this problem can be easily resolved by modifying the parameters of the problematic external neighboring cells based on the check result of the OMStar. For other problems, including unidirectional neighboring cells, insufficient configuration of neighboring cells, and missing configuration of co-sited neighboring cells, the following two solutions are proposed: 1.
Use U-Net to replan the problematic areas based on the existing neighbor relationships. Then, prepare the neighboring cell scripts based on the replanned neighboring cell table.
2.
Manually add neighbor relationships using the neighboring cell editing function of the geographic observation module of the OMStar. Then, prepare the neighboring cell scripts based on the neighboring cell table.
Comparison of the preceding solutions: Using the U-Net: Onsite engineers need to manually organize the required data, replan the areas, and verify the planned data. The detailed procedures are as follows: 1.
The U-Net does not support parsing eNodeB configuration files. Onsite engineers need to manually search the neighboring cells on the U2000 and import the neighboring cell table to the U-Net. Because the format of the neighboring cell table exported from the U2000 is not applicable to the U-Net. Therefore, onsite engineers need to manually adjust the table format before importing the table to the U-Net.
2017-07-28
Huawei confidential. No spreading without permission.
1
Analysis on LTE Geographic Observation in City C
INTERNAL
2.
In addition, the base station list, cell list, and antenna list are also required for replanning. As a result, onsite engineers also need to manually adjust the formats of these three lists before importing them to the U-Net.
3.
After the replanning, onsite engineers need to manually verify the replanned cells.
Using the OMStar: Because the neighboring cell check result based on live network eNodeB configuration has been obtained, onsite engineers only need to manually adjust the incorrectly configured neighboring cells using the Geographic Observation function of the OMStar. The neighboring cell configuration of certain areas needs to be configured, involving only a few (around 60) cells. In addition, there are only a few hours left before the drive testing, and manually preparing the data required by the U-Net may lead to errors, affecting the planning result. In this situation, onsite engineers decide to use the neighboring cell editing function of the OMStar to manually plan the neighboring cells in these areas. Screenshots of cells with incorrect neighboring cell configuration on the live network Sample 1: Incomplete neighboring cell configuration: Close and adjacent cells are not configured as neighboring cells.
2017-07-28
Huawei confidential. No spreading without permission.
2
Analysis on LTE Geographic Observation in City C
INTERNAL
Sample 2: Unidirectional neighboring cells exist, and the configuration of neighboring cells in the same direction is missing.
Sample 3: Neighboring cell configuration is insufficient. The surrounding cells within a short range are not configured Figure 1 Neighboring cell configuration of certain problematic cells before replanning
2017-07-28
Huawei confidential. No spreading without permission.
3
Analysis on LTE Geographic Observation in City C
INTERNAL
3 Manual Neighboring Cell Planning 3.1 Selecting a Problematic Cell 1.
On the neighboring cell map of the OMStar, use the Search function to locate the problematic cell based on the cell name. Then, click Adding a neighboring cell on the toolbar to start adding neighboring cells.
Alternatively, you can simply switch to the map on the problematic cell table. Then, the problematic cell is automatically located. Click Adding a neighboring cell to add neighboring cells.
2.
Simply click the surrounding cells that need to be added as neighboring cells. Then, the clicked cells are added as the neighboring cells of the source cell one by one. The neighboring cells are displayed in orange. By default, these cells are added as bidirectional neighboring cells of the source cell by the OMStar. (The live network requires that all neighboring cells in the LTE system be bidirectional neighboring cells.)
2017-07-28
Huawei confidential. No spreading without permission.
4
Analysis on LTE Geographic Observation in City C
3.
After the neighboring cells are added, click following figure.
INTERNAL
to save the added neighboring cells, as shown in the
Then, the neighboring cell replanning of a problematic cell is complete, which takes less than 30 seconds. You can proceed to the replanning of the next problematic cell. Use the Search function to locate the next problematic cell. The manual neighboring cell replanning of 60 cells takes less than 20 minutes, and manual verification is also complete within this period. Click
2017-07-28
to export the replanned neighboring cell list.
Huawei confidential. No spreading without permission.
5
Analysis on LTE Geographic Observation in City C
INTERNAL
3.2 Preparing Scripts Based on the Neighboring Cell Replanning Result Prepare the MML scripts used for adding neighboring cells based on the neighboring cell list exported from the map window (including IDs and names of the source cells and their neighboring cells). Then, deliver the MML scripts to NEs.
3.3 Drive Testing Result After related neighboring cells are added to the problematic site, handovers between cells in the problematic site and the neighboring cells can be properly performed.
2017-07-28
Huawei confidential. No spreading without permission.
6
Analysis on LTE Geographic Observation in City C
INTERNAL
4 Summary Currently, three tools are available for executing the neighboring LTE cell check and planning function, including OMStar, U-Net, and SmartRNO (customized for China Mobile). The advantages of the three tools vary based on the application scenarios: OMStar: canthe beneighbor used to parse eNodeB on configuration files, check neighborparameters. relationshipsInon the liveOMStar network, and display relationships a map based on the engineering addition, allows users to modify (add or delete) incorrectly configured neighbor relationships on a map. The modification result can be saved as a neighboring cell list in Excel format, which can then be used to prepare the neighboring cell scripts. U-Net: can only be used for neighboring cell planning and does not support parsing eNodeB data. Users need to manually prepare data in the formats required by the U-Net before importing the data for planning. The neighboring cell planning data can be displayed on a map and can be edited. The U-Net mainly applies to the entire-network neighboring cell planning scenario at the initial site deployment stage. It is not applicable to sporadic site deployment at the later stage of network construction and network project optimization and maintenance stage. At such stages, only a small part of the neighboring cell configuration needs to be adjusted. Besides, the U-Net cannot parse eNodeB configuration files. SmartRNO: can be used to parse eNodeB configuration files, check the neighboring cell configuration, and display the neighbor relationships on the live network on a map. However, users cannot edit neighbor relationships on the map.
2017-07-28
Huawei confidential. No spreading without permission.
7
