You are on page 1of 6

Flow of analysis

Lai Gaorui

RRC SETUP ANALYSIS


1. Whether it is a new site? If it is a new site, check the RNP Progress Status Report send by CICI or contact the corresponding region guy to confirm the single site verification status. If the site failed for verification or has not been verified, push the region to solve it. 2. Check the fail reason. Export statistic data from M2000, enter RNC grade, select RRC item, you can find many counters about various reason of RRC setup fail. Or you can export from NASATR as follow:

3. If fail is mainly caused by the reasons as follow:

It basically means there are transmission faults or other equipment problem with the site. You should check the site status and the history alarm , push the region or the equipment engineering to solve the problem.
4. If fail is mainly caused by the reasons as follow:

Exclude the access parameter configuration first, and then check the traffic volume, confirm whether the cell should be expanded.
5. If fail is mainly caused by the reasons as follow:

It is about the RF reason. a. Check the cell status and the history alarm, exclude the NodeB fault problem; b. Check the geography information from GOOGLE or MAPINFO, whether it is a isolated cell?

Flow of analysis

Lai Gaorui

Check the RTWP value, if larger than -100, it is abnormal, if larger than -90, it maybe affect the cell badly; d. Check the Pilot Pollution; e. Check the neighbor list; f. Check the engineering parameter such as antenna altitude, antenna azimuth and antenna down tilt.
c.

RAB SETUP ANALYSIS


1. Whether it is a new site? If it is a new site, check the RNP Progress Status Report send by CICI or contact the corresponding region guy to confirm the single site verification status. If the site failed for verification or has not been verified, push the region to solve it. Check the fail reason. Export statistic data from M2000, enter RNC grade, select RAB item, you can find many counters about various reason of RAB setup fail. Or you can export from NASATR as follow:
2.

3. If fail is mainly caused by the reasons as follow:

It basically means transmission faults. 4. If fail is mainly caused by the reasons as follow:

It means cell congestion, confirm whether the cell should be expanded.


5. If fail is mainly caused by the reasons as follow:

Flow of analysis

Lai Gaorui

It is about the RF reason. a. Check the cell status and the history alarm, exclude the NodeB fault problem; b. Check the geography information from GOOGLE or MAPINFO, whether it is a isolated cell? c. Check the RTWP value, if larger than -100, it is abnormal, if larger than -90, it maybe affect the cell badly; d. Check the Pilot Pollution; e. Check the neighbor list; f. Check the engineering parameter such as antenna altitude, antenna azimuth and antenna down tilt;

CALL DROP ANALYSIS


1. Whether it is a new site? If it is a new site, check the RNP Progress Status Report send by CICI or contact the corresponding region guy to confirm the single site verification status. If the site failed for verification or has not been verified, push the region to solve it. 2. Check the fail reason. Export statistic data from M2000, enter RNC grade, select RAB item, click the Measurement of RAB release triggered by UTRAN per cell, you can find many counters about call drop analysis. Or you can export from NASATR as follow:

3. If fail is mainly caused by the reason as follow: VS.RAB.RelReqCS.OM It means that fail is caused by operation and maintenance work, actually it is normal call drop. 4. If fail is mainly caused by the reason as follow: VS.RAB.RelReqCS.RABPreempt It happens when heavy traffic load or lack of resource, confirm whether the cell

Flow of analysis

Lai Gaorui

should be expanded.
5. If fail is mainly caused by the reason as follow:

VS.RAB.Loss.CS.Aal2Loss It basically means there are transmission fault or other equipment problem with the site. You should check the site status and the history alarm , push the region or the equipment engineering to solve the problem.
6. If fail mainly caused by the reasons as follow:

VS.RAB.Loss.RF.RLCRst VS.RAB.Loss.RF.ULSync VS.RAB.Loss.RF.UuNoReply VS.RAB.Loss.RF.Oth It is about the RF reason. a. Check the cell status and the history alarm, exclude the NodeB fault problem; b. Check the geography information from GOOGLE or MAPINFO, whether it is a isolated cell? c. Check the RTWP value, if larger than -100, it is abnormal, if larger than -90, it maybe affect the cell badly; d. Check the Pilot Pollution; e. Check the neighbor list; f. Check the engineering parameter such as antenna altitude, antenna azimuth and antenna down tilt; g. Considering the InterRATHO statistics, check whether the call drop caused by the corresponding reason of InterRATHO. 7. If fail mainly caused by the reasons as follow: VS.Call.Drop. Other Considering the corresponding InterRATHO statistics, check whether the call drop caused by the corresponding reason of InterRATHO.

PS InterRATHO ANALYSIS
1. Whether it is a new site? If it is a new site, check the RNP Progress Status Report send by CICI or contact the corresponding region guy to confirm the single site verification status. If the site failed for verification or has not been verified, push the region to solve it. 2. Check the fail reason. Export statistic data from M2000, enter RNC grade, select InterRAT item, click InterRAT Handover Measurement per cell or Measurement between a cell and a intRAT cell, you can find many counters about PS InterRATHO analysis. Or you can export from NASATR as follow:

Flow of analysis

Lai Gaorui

3. If fail mainly caused by the reason as follow:

IRATHO.FailOutPSUTRAN.CfgUnsupp It usually means UE problem. 4. If fail mainly caused by the reason as follow: IRATHO.FailOutPSUTRAN.PhyChFail It is basically caused by the 2G problem, bad signal or interference. 5. If fail mainly caused by the reason as follow: VS.IRATHO.FailOutPSUTRAN.Other It is caused by other reason, often for timer expiry. 7. Measures: a. Check the cell status and the history alarm of correlative 3G and 2G cell, exclude the fault problem of 2G site or 3G site; b. Check the inter-neighbor cell list; c. Check the interference of 2G; d. Check the GPRS status of correlative 2G cell, maybe 2G cell doesnt support GPRS; e. Check the TBF setup rate of correlative 2G cell, may be caused by low TBF setup rate. f. Check the configuration of 2G neighbor cell in the 3G MML script, maybe something wrong with configuration; g. Check the inter-neighbor cell list in the MSC file, maybe some 2G cells are missed to be added as inter-neighbor cell in the MSC configuration; h. Check the parameter of cell InterRAT HO basing on coverage, maybe

Flow of analysis

Lai Gaorui

i.

something unreasonable with the configuration; Check that whether it is caused by a special UE, it may be something wrong with a mobile.

You might also like