You are on page 1of 12

资料编码

景德镇移动 PRACH 问题根因分析


报告
(标题尽可能体现故障现象)
文档版本 01

发布日期 2010-07-02

华为技术有限公司
版权所有 © 华为技术有限公司 2010。 保留一切权利。
非经本公司书面许可,任何单位和个人不得擅自摘抄、复制本文档内容的部分或全部,并不得以任何形式传播。

商标声明

和其他华为商标均为华为技术有限公司的商标。
本文档提及的其他所有商标或注册商标,由各自的所有人拥有。

注意
您购买的产品、服务或特性等应受华为公司商业合同和条款的约束,本文档中描述的全部或部分产品、服务或
特性可能不在您的购买或使用范围之内。除非合同另有约定,华为公司对本文档内容不做任何明示或默示的声
明或保证。

由于产品版本升级或其他原因,本文档内容会不定期进行更新。除非另有约定,本文档仅作为使用指导,
本文档中的所有陈述、信息和建议不构成任何明示或暗示的担保。

华为技术有限公司
地址: 深圳市龙岗区坂田华为总部办公楼 邮编:518129

网址: http://www.huawei.com

客户服务邮箱: support@huawei.com

客户服务电话: 0755-28560000 4008302118

客户服务传真: 0755-28560111

文档版本 01 (2010-07-02) Huawei Proprietary and Confidential ii


Copyright © Huawei Technologies Co., Ltd
根因分析报告 前 言

前 言[About This Document]

问 题 单 号 3959418
[Trouble Ticket
Number]

作 者 [Prepared 沈健 00126759
by]

审 批 人
[Approved by]

审 批 日 期
[Approval
Date]

文档版本 01 (2010-07-02) Huawei Proprietary and Confidential iii


Copyright © Huawei Technologies Co., Ltd
根因分析报告 1 目 录[Contents]

目 录[Contents]

1 基本信息[Basic Information] ...................................................................................................... 1


2 问题描述[Problem Description] ................................................................................................. 2
3 问题分析[Problem Analysis] ...................................................................................................... 2
4 根本原因[Root Cause] .................................................................................................................. 6
5 解决措施[Corrective Action] ....................................................................................................... 6
5.1 临时解决措施[Workaround] .......................................................................................................................... 7
5.2 最终解决措施[Solution] ................................................................................................................................. 7

6 预防措施[Preventive Action] ...................................................................................................... 8

文档版本 01 (2010-07-02) Huawei Proprietary and Confidential iv


Copyright © Huawei Technologies Co., Ltd
根因分析报告 1 基本信息[Basic Information]

1 基本信息[Basic Information]

Product Name Version


eNB BTS3900 V100R009C00SPC135

文档版本 01 (2010-07-02) Huawei Proprietary and Confidential 1


Copyright © Huawei Technologies Co., Ltd
根因分析报告 2 问题描述[Problem Description]

2 问题描述[Problem Description]

After customers changed the parameter of PrachFreqOffset, Preamble success rate decreased and later recover
automatically, for that we need to do some analysis.

文档版本 01 (2010-07-02) Huawei Proprietary and Confidential 2


Copyright © Huawei Technologies Co., Ltd
根因分析报告 3 问题分析[Problem Analysis]

3 问题分析[Problem Analysis]

First, after confirmation, PrachFreqOffset is useless for TDD system, and for the PRACH frequency offset is
fixed in the code, so the parameter change can not affect anything in fact.
And we checked the cell level performance trend, after changing the parameter, some cells’ Preamble success
rate decreased and some of them increased, so the what effected the whole network performance is the cell
level performance not because of the parameter change.
For next, why some cells’ preamble success rate is low? And for the Preamble success rate low problem is not
always existed, only during some time period.
To solve this problem, front field picked one top cell, and during the problematic time period, we traced the
CELLDT data, and from the performance data, cell of 港逸豪庭-3 had problem during the time of 11:00 on 7th
Jan.
Start NE Cell Name L.RA.GrpA L.RA.GrpA.R L.RA.GrpB L.RA.GrpB.R Pream
time Name .Att esp .Att esp ble
succes
s rate

eNodeB
Name=3CJD
CX-港逸豪庭,
Local cell
3CJDC ID=3, cell
01/07/20
Name=3CJD 96.39
15 X-港逸 579 567 168 153
CX-港逸豪庭 %
11:00:00 豪庭
-3, eNodeB
ID=520084,
Cell duplex
mode=CELL_
TDD

According to the product, the site will limit the C-RNTI Preamble sequence number for each RACH access
request based on the CPU load. When Baseband CPU load is lower than 80%, CELLM can only provide
C-RNTI for 4 preamble sequence, for the one apart from the first 4, will neglect them.

After checking the CELL DT T304(Dest_T304_LDT_EVT_CCHP_SEND_CRN) of this cell, some preamble


sequence in PRACH access is more than 4, and the site will discard them randomly. For example, in these 2
pictures below, the preamble sequence number is more than 10 everytime.

文档版本 01 (2010-07-02) Huawei Proprietary and Confidential 3


Copyright © Huawei Technologies Co., Ltd
根因分析报告 3 问题分析[Problem Analysis]

After checking the CELL DT T305 (Dest_T305_LDT_EVT_CCHP_RECV_CRN) of this cell, for these 2
PRACH access es, only the first 4(Index1~3) had response, the others(Index>3) were discarded.

From T305 table, we can see that PreambleId has both GROUP A(less than 28) and GROUP B(more than 28),
and some of the access TA is very big, more than 100, which means 10 kilometers, so we suspect that it is not
normal UE access, which should be false detected.
All in all, the thing is that it doesn’t affect real UE, and no need to pay too much attention.
If we want to increase the KPI, considering to switch on the “PRACHFalseAlarmDetSwitch”, and in the mean
time increase the ratio of RACH threshold. Here, if we change the parameter like this, sometimes some normal
UE’s access will be treated as false detect, and that will affect users’ feelings, which should be paid attention.
Specific parameter changing method:
[PRACH false alarm detecting algorithm switch] PRACHFalseAlarmDetSwitch from OFF to ON.
[RACH threshold increasing ratio] RachThdBoostRatio from 0 to 30.
For this field, we picked several top cell, and changed the parameter.
After changing the parameter, group A and group B’s counters’ summary fluctuates a lot, and in all no obvious
decrease, but the Preamble success rate is turning better.

文档版本 01 (2010-07-02) Huawei Proprietary and Confidential 4


Copyright © Huawei Technologies Co., Ltd
根因分析报告 3 问题分析[Problem Analysis]

文档版本 01 (2010-07-02) Huawei Proprietary and Confidential 5


Copyright © Huawei Technologies Co., Ltd
根因分析报告 4 根本原因[Root Cause]

4 根本原因[Root Cause]

Low Preamble success rate of some cells in some time segment due to false alarm detection.

文档版本 01 (2010-07-02) Huawei Proprietary and Confidential 6


Copyright © Huawei Technologies Co., Ltd
根因分析报告 5 解决措施[Corrective Action]

5 解决措施[Corrective Action]

说明解决该问题的措施,包括应急的补救措施,和最终的解决措施。

5.1 临时解决措施[Workaround]
Specific parameter changing method:
[PRACH false alarm detecting algorithm switch] PRACHFalseAlarmDetSwitch from OFF to ON.
[RACH threshold increasing ratio] RachThdBoostRatio from 0 to 30.

5.2 最终解决措施[Solution]

文档版本 01 (2010-07-02) Huawei Proprietary and Confidential 7


Copyright © Huawei Technologies Co., Ltd
根因分析报告 6 预防措施[Preventive Action]

6 预防措施[Preventive Action]

可选,说明采取哪些预防性的措施使该问题不会发生。

文档版本 01 (2010-07-02) Huawei Proprietary and Confidential 8


Copyright © Huawei Technologies Co., Ltd

You might also like