Simple Case Study Sharing: Compiled by Adriansyah Putra Taufik Senior RNPO Engineer Huawei Indonesia NIS

Simple Case Study Sharing
Compiled by Adriansyah Putra Taufik Senior RNPO Engineer Huawei Indonesia NIS adriansyah.taufik@huawei.com / adriansyahputra.taufik@gmail.com
HUAWEI TECHNOLOGIES CO., LTD.
Huawei Confidential
Huawei Confidential
Drive test Analysis
Configuration Analysis Case Type Alarm Analysis
Performance Analysis
Huawei Confidential
Case 1 : Late 2G Cell Reselection

Country I Project A Region W City B Technology : 2G Vendor : Huawei Case Type : Drive Test Analysis Configuration analysis Description : Improper 2G Idle Parameter make bad coverage in several spot Keyword : Rx Lev Access Min Conclusion : Too high Rx Lev Access Min make limited coverage for selected cell
HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR
Page 4

We found problem during FAC test , which have late cell reselection so Rx Level can not achieve and make bad spot
Cell KB054GB did not want to cell reselection to Cell BD022GA , even the distance nearest from BD022GA and have good signal. Also we must take analysis for this cell selection reselection. Please see BD022GA have better Rx Level , but have worse C1 and C2 from KB054GB
Page 5

So based on Cell Reselection criteria and formula ,we can check parameter which have improper setting Like : Rx Lev_Access_Min , MS_TXPWR_MAX_CCH,CRO , TO and PT
Page 6

After we do parameter checking , we found improper RxLev_Access_min in Cell BD022GA [25] , so we roll back again into default value [8]
Parameter Explanation
Page 7

After parameter roll back (Rx lev_access_min) into default value in Cell BD022 , cell reselection process become normal, and coverage bad spot become better
Page 8
Case 2 : Wrong TRX Parameter

Country I Project A Region W City C Technology : 2G Vendor : Huawei Case Type : Performance Analysis Configuration Analysis Description : Improper 2G TRX Parameter make performance degradation Keyword : TRX Receive Mode and Send Mode BTS 3012 Conclusion : 2G TRX Parameter must be audited (for Huawei BTS 3012 Series) for periodically to avoid performance degradation because wrong parameter
Page 9

We found a cell which have many Handover fail count day per day and make high CDR and low HOSR. After we review Neighbor List relationship is normal , Handover parameter is default. No alarm or hardware issue. Then we check TRU Configuration for that cell and for receive mode is independent receiver (it must be dividing receiver)
TRX / TRU Parameter must be following this rule
Page 10

After revise TRU / TRX Configuration parameter in Cell KC020GA from independent receiver into dividing receiver , there is KPI OSS improvement in CDR and HOSR
KC020GA TCH Drop Rate Vs Number of TCH Drop
8.00% 7.00% 6.00% 5.00% 4.00% 3.00% 2.00% 1.00% 0.00% 30 25 20 15 10 5 0 TCH Drop Rate #Drop TCH
4/ 9/ 2 4/ 01 10 0 /2 4/ 0 1 11 0 /2 4/ 0 1 12 0 /2 4/ 0 1 13 0 /2 4/ 0 1 14 0 /2 4/ 0 1 15 0 /2 4/ 0 1 16 0 /2 4/ 0 1 17 0 /2 4/ 0 1 18 0 /2 4/ 0 1 19 0 /2 4/ 0 1 20 0 /2 4/ 0 1 21 0 /2 01 0
KC020GA HOSR Vs Fail Intra BSC HOSR

105.00% 100.00% 95.00% 90.00% 80 70 60 50 40 30 20 10 0
HOSR Total #Fail IntraBSC
14 April date to change parameter
85.00% 80.00% 75.00%
4/ 9/ 2 4/ 01 10 0 /2 4/ 0 1 11 0 /2 4/ 0 1 12 0 /2 4/ 0 1 13 0 /2 4/ 0 1 14 0 /2 4/ 0 1 15 0 /2 4/ 0 1 16 0 /2 4/ 0 1 17 0 /2 4/ 0 1 18 0 /2 4/ 0 1 19 0 /2 4/ 0 1 20 0 /2 4/ 0 1 21 0 /2 01 0
Page 11
Page 11

Country I Project A Region W City T Technology : 2G Vendor : Huawei Case Type : Drive Test Analysis Configuration Analysis Description : Improper 2G Idle Parameter make bad coverage in several spot Keyword : CRO Conclusion : CRO value parameter can make selected cell more aggressive or less aggresive
Page 12

We found a not good coverage (Rx Level in idle) in Cell TS022GB and very late to cell reselection to TS018GA (even already very near distance to TS018G) , so we do some method (check 2G idle parameter related)
Cell TS022GB did not want to cell reselection to other cell which have better Rx Level. After Check idle Parameter , because Cell TS022GB have CR0(2dB) : 1
Page 13
Page 13
Case 4 : Failed Inter BSC Handover

Country I Project A Region W City S Technology : 2G Vendor : Huawei Case Type : Performance Analysis Configuration analysis Description : Failed Inter BSC Handover in border between Vendor Huawei with Vendor Ericsson Keyword : Inter BSC Handover - Invalid Cell Conclusion : Before analyze Inter BSC HOSR, please ensure neighbor in source BSC and Destination / Target BSC and also every LAC CI in border must be registered in MSC
Page 14

We found BG405GC have very bad Inter BSC HOSR value in daily , so we try to analyze (This site is border to Ericsson). So We try check via passive measurement counter (M2000) and 2G LMT tracing
After check via PM counter (M2000) , we can see almost handover request is fail
Page 15

From tracing file we can get cause value is invalid cell , so we must create cell / define cell in the Destination BSC and ensure LAC CI already registered in MSC
Check Contain Message from LMT Tracing
Page 16
Case 5 : BTS3900 Series Power Test

Technology : 2G Vendor : Huawei Case Type : Configuration Analysis Description : BTS3900 Power Test to ensure Zero Traffic / Silent Cell Keyword : BTS3900 - Zero Traffic Forward Power / Back Power Conclusion : We can get actual value for Forward and Back Power remotely for BTS 3900 Series
Page 17

One of method to check TRX Quality / Performance / working condition for BTS3900 Series is with Test Site Performance in BSC6000 and test BTS Performance test with MML command in BSC6900.
Press CTRL+Shift+F12 to enter super admin mode so we can get site performance test in BTS Performance Internal Maintenance Test Site Performance
Site Performance Test in BSC6000 system
From TRX Site Performance Test we can get actual value for Forward Power / Back Power and power level. If Forward / Back Power value is zero mean Module is faulty / problem
Page 18

To test BTS Site Performance in BSC6900 (MML Based), first is to write MML Command TST BTSPERFTEST then press Generate Input interface then wait for a moment then add BTS ID and TRX ID based on id type.
Site Performance Test in BSC6900 using MML Command
From TRX Site Performance Test we can get actual value for Forward Power / Back Power and power level. If Forward / Back Power value is zero mean Module is faulty / problem
Page 19
Case 6 : BTS3900 Problem

Country I Project A Region W City K Technology : 2G Vendor : Huawei Case Type : Performance Analysis Drive Test Analysis Configuration Analysis Description : BTS3900 Problem make Zero Traffic / Silent Cell Keyword : BTS3900 - Zero Traffic Forward Power / Back Power Conclusion : To ensure whether there is Zero Traffic / Silent Cell we can analysis with these step : a. Traffic Data from performance measurement b. Call Attempt from performance measurement c. Drive test check d. Power Test (Internal maintenance)
Page 20

We found 2 cell no serving during drive test , these two cells is BTS3900 , se we check site status , The sites look normal (With Green indicator) and no alarm found.
Page 21

After we check that 2 cells have no TCH traffic and no call seizures (K3013A). So we check alarm again , there is no major alarm. Also we check parameter and the all parameter is default. So suspect must be TRX. So we do internal maintenance site performance
Page 22

We do a site performance test . And the result for cell which can not serving is has back power 0 dBm , it means TRX faulty. So the problem found because DRFU Faulty (Hardware Faulty).
Page 23
Case 7 : Power Level make Coverage Degradation

Country I Project A Region W City K Technology : 2G Vendor : Huawei Case Type : Drive Test Analysis Configuration Analysis Description : Power Level Parameter impact to coverage degradation Keyword : Power Level Conclusion : Greater Power Level parameter value can make transmit power reduce by 2 dB for every add 1 level value
Page 24

We found coverage degradation in K area, even customer declare there is new site on air in K area. So we must verify Actual data configuration whether there is new site and check bad spot / problem to analyze
Coverage Before Coverage After
Problem 1
Problem 3
Problem 2
Page 25

First we must ensure from actual data configuration LMT BSC6000 for new site information based on customer information, after check for sites with red circle still off air
Problem 1
Problem 3
Problem 2
Based on LMT BSC, all sites with red circle is still off air, but the problem , why the coverage is still degraded ? Please see next slide
Page 26

Problem Area 1 : We found coverage degradation in problem area 1, then we compare 2 data configuration (parameter consistency check) then we found parameter change in power level, for the newer data configuration power value is 1 which mean BTS transmit power decrease by 2 dB
From Old data we found 0 Power level value
From New data we found 1 Power level value
Page 27

Page 28

Page 29
Power Level Parameter Explanation
Page 30
Case 8 : Site Audit Founding (1)

Country I Project A Region W City C Technology : 2G Vendor : Huawei Case Type : Drive Test Analysis Description : Improper Feeder Type and limitation antenna installation make coverage not optimal Keyword : Azimuth Feeder Type
Page 31

Our team found bad coverage even already optimize power level and power type, but bad coverage still occur. So we proposed to site audit. Then from site audit found discrepancy feeder type and antenna limitation because using Mobile BTS for tower structure.
From site audit , we found feeder type is 7/8 but in design and planning data it must be 5/4
Also we found antenna limitation

Coverage not optimal because these two factor : discrepancy feeder type and antenna limitation
Page 32

Country I Project A Region W City C Technology : 2G Vendor : Huawei Case Type : Drive Test Analysis Description : Improper antenna installation make coverage not optimal Keyword : Antenna azimuth installation
Page 33

Our team found bad coverage even already optimize power level and power type, but bad coverage still occur. So we proposed to site audit. Then from site audit found improper antenna installation
From site audit , we found antenna limitation so coverage can not optimum to serve in several / selected area
Page 34
Case 10 : Can Not Access 2G PS

Country I Project A Region W City T Technology : 2G Vendor : Huawei Case Type : Drive Test Analysis Performance Analysis Configuration Analysis Description : NSVC Parameter not defined in PCU outer make all user in one city cant access 2G PS. Keyword : PCU TBF NSEI Conclusion : To verify 2G PS Access Parameter can be check : a. PS Drive Test b. PS Cell Check (PTPBVC) c. NSEI Check d. Gb (From BSC to SGSN) Performance measurement check e. Pb (From BSC to PCU) Performance measurement check (If the PCU is separated or not integrated with BSC
Page 35

Before we analyze, better we must know some parameter in 2G PS
1.Pb Interface : Interface between BSC to PCU
2.Gb Interface : Interface between BSC to SGSN 3.NSVC : Virtual Connection between the BSC and the SGSN 4.PCU : Packet Control Unit
5.PTPBVC: Same like Cell in GSM but use in GPRS

6.TBF: Kind of physical connection used for the transmission of the data between the MS RR entity and the BSS RR entity. It exist during data transmission only
Page 36

We get complaint by customer, one city cant access 2G PS for several days. So we do Drive test and performance analysis in this area.
We try 2G PS Test in Cell A Site A, then we found PS Access Failure which have message The PPP Link Control Terminated
Also we try 2G PS Test in Cell B Site B, then we found same event RAS Error with PS Access Failure which have same message The PPP Link Control Terminated
Page 37

After we get 3 sample cell to do PS Test and we check radio condition, we can temporary summarize the problem is not in Radio Part
Based on coverage Drive Test (Rx Level) , there is no radio problem in Cell C Site C
Finally we try 2G PS Test in Cell C Site C, then we found same event RAS Error with PS Access Failure which have same message The PPP Link Control Terminated
Page 38

From Pb Interface performance analysis, we get all counter related to resource blocking (Blocked circuit) and resource problem (faulty circuit and maintenance problem) have zero counter. So we can temporary summarize there is no problem between PCU to BSC interface
Page 39

From Gb interface performance analysis using TBF establishment analysis, we can see in chart whether there is problem in Gb Link because there is zero downlink TBF establishment attempts meanwhile there is number in uplink TBF establishment attempt.
From TBF establishment analysis, we can conclude whether there is problem in Gb link because there is no TBF establishment in DL which mean there is no data transmission between PS domain to Mobile Station Side direction
Page 40

So next step we check PCU (PCU Outer Model) Data Configuration for every cell (PTPBVC) status like activation and normal state. And as we can see the result is normal and active, so the PTPBVC / cell run normal
From PTP BVC (Cell in PS domain) in PCU data Configuration check all Cell active and normal.
Page 41

So next step is to check NSVC Status to check NSEI (Like LAC in 2G CS). From all PCU Outer only PCUTS01 doesnt have NSVC and NSEI definition which is have complaint in one city and zero downlink TBF establishment attempt.
Actual Data Capture in PCU show NSVC Status in PCUTS01 has empty table which mean NSEI didnt define
Actual Data Capture in PCU show NSVC Status in other PCU has NSEI Table define For every PCU Outer status in W Region, only PCUTS01 doesnt have NSEI Table definition which inline with problem in one city can not access 2G PS.
Page 42

Conclusion : Based on Drive Test Result, we found event RAS Error with PS Access Failure which message The PPP Link Control Terminated and also founding based on performance measurement data there is zero data for downlink TBF establishment attempt . Then based on data configuration as we can see there is no NSEI (like LAC in 2G CS) definition so this make can not access 2G PS
Page 43
Case 11 : Power Control Parameter Set Too Aggressive Make Degradation Coverage during Dedicated Mode
Country I Project A Region W City C Technology : 2G Vendor : Huawei Case Type : Drive Test Analysis Configuration Analysis Description : During drive test in dedicated mode, we get degradation if we compare to idle mode, after we check data configuration we found power control parameter too aggressive so for temporary solution we disable power control to ensure there is no coverage reduction during dedicated Keyword : Huawei Power Control II Conclusion : If we set power control parameter threshold too aggressive can make coverage reduction due to decrease step level from power control adjustment in action zone.
Page 44
Case 11 : Power Control Parameter Set Too Aggressive Make Degradation Coverage during Dedicated Mode (HW PC II Intro)
Before we enter to analysis, better we must know Huawei Power Control II Method. As Per chart below, power control can be applied / start / works whether entering area / criteria of UL/DL Qual Upper Lower Threshold and area / criteria of UL/DL RX_Lev Lower Upper threshold. Then action its depend by it criteria it self
Action Zone
Receive Level
Page 45
Below picture are RX level threshold parameter explanation for power control parameter windowing / prerequisite for action zone
Page 46
Below picture are RX qual threshold parameter explanation for power control parameter windowing / prerequisite for action zone
Page 47
We get Rx Level much reduce during drive test in dedicated mode compare to idle mode in several cells.
Idle mode
Dedicated mode
Page 48
Also snapshot below show there is much reduce for Rx level during dedicated mode compare to idle mode.
Idle mode
Dedicated mode
Page 49
Also snapshot below show there is much reduce for Rx level during dedicated mode compare to idle mode.
Idle mode
Dedicated mode
Page 50
Then we try to temporary disable downlink power control to ensure there is problem in power control algorithm. So we conclude there is improper power control threshold like DL/UL Lower Upper Level / qual threshold which make power control start in good Rx Level / Rx Qual and also maybe power control action like reduction step level is too much (like 8 dB to decrease)
Dedicated Mode with power control enable

Dedicated mode with power control disable

Page 51
Case 12 : 2G Ping-Pong Handover (Too frequent Handover)

Country I Project A Region W City T Technology : 2G Vendor : Huawei Case Type : Drive Test Analysis Description : During drive test we get bad Rx Qual, after do RF analysis we get one cell overshoot and serving site azimuth is not to wide only 30 degree Keyword : Rx Qual - Ping Pong HO Conclusion : To ensure good RX Qual beside we must consider good ARFCN Plan other cell/site overshoot, is to check actual site / cell azimuth/ bearing whether difference between one sector to other sector is too tight or not to wide
Page 52
Problem Spot 1
Problem Spot with many Ping Pong HO Happened
Problem Spot 2
Page 53
Ping-pong HO happened because CM035 Sector A overshoot
This problem spot area must be serve by CM035 Sector B not Sector A, so next step is to do site audit to check azimuth and tilting
Problem Spot 1
Page 54

Ping Pong HO happened because Sector separator too close for CM043GC and CM043GA (Only 35 degree)
Suggestion make CM043GC Azimuth around 300-315 or CM043GA azimuth around 35-45
Azimuth Site ID Problem Date Of Optimization before CM043GA CM043GB CM043GC All DT Item (Change Route) All DT Item (Change Route) All DT Item (Change Route) 30-Apr-09 30-Apr-09 30-Apr-09 35 170 335 after 20 170 335 before 0 0 0
Mechanical after 4 4 0 before 0 0 0
Electrical after 0 2 0
Page 55
Case 13 : External Interference (Uplink Interference) Problem make Call Drop degradation
Country I Project T Region E Technology : 2G Vendor : Huawei Case Type : Configuration Analysis Performance Analysis Description : We found call drop degradation in BSC and in one area, after we check there is increase number interference band in several cell in same area which mean indicate there is external interference Keyword : Interference Band Conclusion : One of way to analyze to check call drop rate degradation is to check interference band (SDCCHTCHH-TCHF)
Page 56
2G Interference Band Explanation
Page 57
There is TDR,HOSR and SDSR degradation from 22 December in BSC_jemberbukit4
Page 58
There is CM330 (Call Drop on radio interface in stable state) and CM331 (Call Drop on radio interface in handover state) increase number in 22 December 2010 and lead to KPI Degradation
Page 59
There is H3028Ca (Failed internal intra-cell handovers) number increase and lead to CM331 Increase, also there is M3201A (Call drop due to Connection fail) number increase and lead to CM330 Increase
Page 60
There is no related alarm to KPI degradation in 22 december 2010, in 23 December 2010 there is alarm related to transmission. So we can conclude there is no related alarm to this case (Call Drop Degradation)
Page 61
- Interference Band give related analysis about interference which is related to SDCCH Success Rate - There is no degradation in In SDCCH/TCHF/TCHH Interference Band Percentage for Band 1+2+3, but there is degradation for Band 1+2 in 22 December 2010
Page 62
-- We make problem cell list based on TDR Performance , so we calculate number of call drop count after 22 december 2010 (when the performance degraded) and before 22 december 2010
Page 63
Scan Frequency Result In Pakusari-1 and Unmuh Jember-0 (Problem Cell)
Highlight : (Find from cell which have high different call drop count from 23 Dec until 21 Dec) -There is main or diversity average RSSI around -92 dBm in Pakusari-1 And Unmuh Jember-0 - Both Pakusari-1 and Unmuh Jember-0 have high different call drop between 23 december and 21 december
64
Page 64
Scan Frequency Result In Arjasa Jember-2 and Jelbuk-2 (Problem Cell)
Highlight : (Find from cell which have high different call drop count from 23 Dec until 21 Dec) -There is main or diversity average RSSI around -92 dBm in Arjasa Jember-2 and Jelbuk-2 - Both Arjasa Jember-2 and Jelbuk-2 have high different call drop between 23 december and 21 december
65
Page 65
Scan Frequency Result In Perum Alfa0 and Sukorambe Relok Jember-0 (Normal Cell)
Highlight : (Find from cell which have no or low different call drop count from 23 Dec until 21 Dec) -There is main or diversity average RSSI around -102 dBm in perum alfa-0 and sukorambe relok jember-0 - Both perum alfa-0 and sukorambe relok jember-0 have low or no different call drop between 23 december and 21 december
66
Page 66
Scan Frequency Result in Jelbuk-0 (Normal Cell)
Highlight : (Find from cell which have no or low different call drop count from 23 Dec until 21 Dec) -There is main or diversity average RSSI around -102 dBm in Jelbuk-0 - Jelbuk-0 has low or no different call drop between 23 december and 21 december
67
Page 67
Interference Band Percentage In Pakusari-1 (Problem Cell)
Highlight : - Interference Band give information about interference which is related to SDCCH Success Rate - There is degradation in In SDCCH/TCHF/TCHH Interference Band Percentage for Band 1+2 from 22 December 2010
68
Page 68
Interference Band Percentage In Unmuh Jember-0 (Problem Cell)
69
Page 69
Interference Band Percentage In Arjasa Jember-2 (Problem Cell)
70
Page 70
Interference Band Percentage In Jelbuk-0 (Normal Cell)
Highlight : - Interference Band give information about interference which is related to SDCCH Success Rate - There is no degradation in In SDCCH/TCHF/TCHH Interference Band Percentage for Band 1+2 from 22 December 2010
71
Page 71
Interference Band Percentage In Jelbuk-0 (Normal Cell)
Highlight : - Interference Band give information about interference which is related to SDCCH Success Rate - There is no degradation in In SDCCH/TCHF/TCHH Interference Band Percentage for Band 1+2 from 22 December 2010
72
Page 72
From analysis chart we can conclude there is TDR and HOSR Degradation meanwhile we found increase number of interference band in several cell
73
Page 73
From analysis chart we can conclude there is SDSR and EMD (Erlang Minute Drop) Degradation meanwhile we found increase number of interference band in several cell which mean indicate external interference in some cell
74
Page 74
Case 14 : Call Drop Due To Equipment Failure because Alarm in A Interface Board
Country I Project T Region E Technology : 2G Vendor : Huawei Case Type : Configuration Analysis Performance Analysis Description : We found call drop degradation in BSC and in one area, after we check there is increase number interference band in several cell in same area which mean indicate there is external interference Keyword : Call Drop due to Equipment Failure Conclusion : One of way to analyze to check call drop rate degradation is to check interference band (SDCCHTCHH-TCHF)
Page 75
Thank you
www.huawei.com
Copyright2010 Huawei Technologies Co., Ltd. All Rights Reserved.

Simple Case Study Sharing: Compiled by Adriansyah Putra Taufik Senior RNPO Engineer Huawei Indonesia NIS

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Simple Case Study Sharing: Compiled by Adriansyah Putra Taufik Senior RNPO Engineer Huawei Indonesia NIS

Caricato da

Copyright:

Formati disponibili

Simple Case Study Sharing

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

Drive test Analysis

Configuration Analysis Case Type Alarm Analysis

HUAWEI TECHNOLOGIES CO., LTD.

Case 1 : Late 2G Cell Reselection

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 1 : Late 2G Cell Reselection

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 1 : Late 2G Cell Reselection

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 1 : Late 2G Cell Reselection

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 1 : Late 2G Cell Reselection

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 2 : Wrong TRX Parameter

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 2 : Wrong TRX Parameter

TRX / TRU Parameter must be following this rule

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 2 : Wrong TRX Parameter

KC020GA HOSR Vs Fail Intra BSC HOSR

HOSR Total #Fail IntraBSC

14 April date to change parameter

85.00% 80.00% 75.00%

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 3 : Late 2G Cell Reselection

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 3 : Late 2G Cell Reselection

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 4 : Failed Inter BSC Handover

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 4 : Failed Inter BSC Handover

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 4 : Failed Inter BSC Handover

Check Contain Message from LMT Tracing

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 5 : BTS3900 Series Power Test

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 5 : BTS3900 Series Power Test

Site Performance Test in BSC6000 system

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 5 : BTS3900 Series Power Test

Site Performance Test in BSC6900 using MML Command

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 6 : BTS3900 Problem

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 6 : BTS3900 Problem

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 6 : BTS3900 Problem

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 6 : BTS3900 Problem

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 7 : Power Level make Coverage Degradation

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 7 : Power Level make Coverage Degradation

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 7 : Power Level make Coverage Degradation

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Case 7 : Power Level make Coverage Degradation

From Old data we found 0 Power level value

From New data we found 1 Power level value