TDSCDMA 无线网络CS掉话率优化指导书.docx

1、TDSCDMA 无线网络CS掉话率优化指导书产品名称Product name密级Confidentiality levelTDSCDMA内部公开产品版本Product versionTotal 20pages 共20页DRNC820V004R000C01B161NodeB B260TDSCDMA 无线网络CS掉话率优化指导书 (仅供内部使用）For internal use only拟制:Prepared by网络优化组日期：Date2009-4-4审核:Reviewed by日期：Date审核:Reviewed by日期：Date批准:Granted by日期：Date华为技术有限公司Hua

2、wei Technologies Co., Ltd.版权所有 XXAll rights reserved修订记录Revision record日期Date修订版本Revision version修改描述 Change Description作者Author2009-4-6V1.0第一版周应川目 录1 概述 62 CS掉话定义 62.1 话统 62.2 Trace 62.3 CHR 63 掉话原因 73.1 话统掉话原因统计点 73.1.1 RNC请求释放电路域Iu连接对应的RAB 数目对应的原因： 73.1.2 RNC请求释放的按原因分类的电路域RAB 数目对应的原因 83.2 信令流程中的释

3、放原因 84 掉话率指标优化方法 114.1 CS掉话涉及的性能counter 114.2 全网掉话指标分析 144.3 小区掉话指标分析 154.3.1 各种干扰引起的掉话 154.3.2 各种覆盖引起的掉话 175 掉话率指标涉及的参数 186 优化案例 186.1 优化结果 186.2 优化方法 186.2.1 扰码重整 186.2.2 参数调整 207 参考文档列表 20表目录List of Tables表1 Radio Network Layer cause 10表2 Transport Layer caus 10表3 NAS cause 10表4 Protocol cause 10

4、表5 Miscellaneous cause 10图目录List of Figures图2 全网掉话指标分析流程 14TDSCDMA 无线网络CS掉话率优化指导书关键词：掉话 话统 摘 要：本文对商用网络的掉话分析思路、流程和方法进行了描述，从话统分析、IOS Trace和CHR分析等方面开展商用网络的掉话优化进行了介绍。缩略语清单：缩略语英文全名中文解释AMRAdaptive MultiRate自适应多速率CDLCall Detail Log呼叫日志CDRCall Drop Rate掉话率CHRCall History Record呼叫历史记录1 概述本文重点介绍了商用局CS掉话率指标的优化

5、思路、方法、流程以及常见的案例。第二章从话统角度给出了掉话的常见定义。第三章常见的掉话原因，话统掉话原因统计点、话统统计点和实际掉话原因关联、Iu接口掉话原因进行了描述。第四章是采用自顶向下的分析方法从全网、TopN小区、RF优化、负载分析、告警分析对掉话指标的分析方法进行了介绍。第五章给出了掉话率涉及的参数。第六章是一个某个局点实际的掉话指标优化案例。2 CS掉话定义2.1 话统UTRAN侧相关指标就是RNC触发释放的各业务RAB个数。主要包括两个方面：（1）业务建立成功后，RNC向CN发送RAB RELEASE REQUEST消息；（2）业务建立成功后，RNC向CN发送IU RELEASE

6、 REQUEST消息，其后收到CN发送的IU RELEASE COMMAND。CS掉话率（RAB.RelReqCSperCause.sum +IU.NbrRABCSRelIuConnperCause.sum）/ (RAB.SuccEstabCSQueuing.Conv +RAB.SuccEstabCSQueuing.Strm + RAB.SuccEstabCSNoQueuing.Conv + RAB.SuccEstabCSNoQueuing.Strm)*100%2.2 TraceTrace跟踪是分析面向小区掉话率指标的重要手段，Trace能够跟踪Iu、Iur、Iub和Uu接口的信息。对于TOP

7、小区，可跟踪全天信令，观察用户各种异常释放行为，进行分析并找出相应的原因，目前trace只能通过回放工具逐一查看。2.3 CHR目前产品已经支持PCHR数据记录，可通过鼎桥OMSTAR工具进行分析。暂缺。3 掉话原因3.1 话统掉话原因统计点目前话统中提供了掉话原因的细分，CS掉话原因分为：3.1.1 RNC请求释放电路域Iu连接对应的RAB 数目对应的原因：RNC请求释放电路域Iu连接对应的RAB 数目RNC请求释放电路域Iu连接对应的RAB 数目RNC请求释放电路域Iu连接对应的RAB 数目RNC请求释放电路域Iu连接对应的RAB 数目几种失败原因话统中常见比例为：从上图可以看出，RNC请

8、求释放的Iu连接中，RL失步占了绝大多数的比例，而RL失步的判断机制为：这里的RL失步指的是NODEB发起的上行失步，具体的原因为：Node B侧无线链路失败指示过程是对用户Iub接口无线链路状态检测的结果，该过程用于Node B向RNC指示一条无线链路发生了异常或不可用，并且该链路无法恢复。在无线链路已经成功建立后的任何时刻，当Node B检测到无线链路异常时都可以发起Radio Link Failure Indication过程。Radio Link Failure Indication是Iub接口专用过程，其标准流程如下：在用户通信过程中，由于无线网络层原因导致的Radio Link F

9、ailure Indication过程较为常见。从应用的角度看，Radio Link Failure Indication过程主要出现在以下一些情况：（1） RB建立过程中UE无响应，Node B向RNC发送Radio Link Failure，指示同步失败；（2） 切换到目标小区后，源小区基站向RNC发送Radio Link Failure，指示同步失败；（3） 切换过程中网络侧收不到UE的响应，源小区Node B及目标小区Node B向RNC发送Radio Link Failure，指示同步失败；通信保持过程中RL质量恶化，网络侧检测不到UE的有效数据，Node B向RNC发送Radio

10、Link Failure，指示同步失败；3.1.2 RNC请求释放的按原因分类的电路域RAB 数目对应的原因RNC请求释放的按原因分类的电路域RAB 数目RNC请求释放的按原因分类的电路域RAB 数目RNC请求释放的按原因分类的电路域RAB 数目RNC请求释放的按原因分类的电路域RAB 数目RNC请求释放的RAB次数在话统中较少出现，不作分析。3.2 信令流程中的释放原因在Trace跟踪数据分析中，掉话通常是查看Iu接口消息中RNC发起的RAB Release Request或者Iu Release Request，这两个消息的包含了相应的释放原因。原因包括无线网络层原因、传输层原因、NAS原

11、因以及协议原因和其他原因。下表摘录自25413 V8.1.0 (2008-12) 9.2.1.4节。Radio Network Layer causeMeaningDeciphering Keys Not AvailableThe action failed because RNC is not able to provide requested deciphering keys.Conflict with already existing Integrity protection and/or Ciphering informationThe action was not performed

12、 due to that the requested security mode configuration was in conflict with the already existing security mode configuration.Condition Violation For Guaranteed Bit RateThe action was not performed due to condition violation for guaranteed bit rate.Condition Violation For SDU ParametersThe action was

13、 not performed due to condition violation for SDU parameters.Condition Violation For Traffic Handling PriorityThe action was not performed due to condition violation for traffic handling priority.Dedicated Assistance data Not AvailableThe action failed because RNC is not able to successfully deliver

14、 the requested dedicated assistance data to the UE.Directed RetryThe reason for action is Directed RetryFailure In The Radio Interface ProcedureRadio interface procedure has failed.Incoming Relocation Not Supported Due To PUESBINE FeatureThe incoming relocation cannot be accepted by the target RNC b

15、ecause of the PUESBINE feature. Interaction With Other ProcedureRelocation was cancelled due to interaction with other procedure.Invalid RAB IDThe action failed because the RAB ID is unknown in the RNC.Invalid RAB Parameters CombinationThe action failed due to invalid RAB parameters combination.Inva

16、lid RAB Parameters ValueThe action failed due to invalid RAB parameters value.Iu UP FailureThe action failed due to Iu UP failure.No remaining RABThe reason for the action is no remaining RAB.RAB Pre-emptedThe reason for the action is that RAB is pre-empted.Radio Connection With UE LostThe action is

17、 requested due to losing radio connection to the UERelease Due To UE Generated Signalling Connection ReleaseRelease requested due to UE generated signalling connection release.Release Due To UTRAN Generated ReasonRelease is initiated due to UTRAN generated reason.Relocation CancelledThe reason for t

18、he action is relocation cancellation.Relocation Desirable for Radio ReasonsThe reason for requesting relocation is radio related.Relocation Failure In Target CN/RNC Or Target SystemRelocation failed due to a failure in target CN/RNC or target system.Relocation Not Supported In Target RNC Or Target S

19、ystemRelocation failed because relocation was not supported in target RNC or target system.Relocation Target not allowedRelocation to the indicated target cell is not allowed for the UE in question.Relocation TriggeredThe action failed due to relocation.Repeated Integrity Checking FailureThe action

20、is requested due to repeated failure in integrity checking.Request SupersededThe action failed because there was a second request on the same RAB.Requested Ciphering And/Or Integrity Protection Algorithms Not SupportedThe UTRAN or the UE is unable to support the requested ciphering and/or integrity

21、protection algorithms.Requested Guaranteed Bit Rate For DL Not AvailableThe action failed because requested guaranteed bit rate for DL is not available.Requested Guaranteed Bit Rate For UL Not AvailableThe action failed because requested guaranteed bit rate for UL is not available.Requested Guarante

22、ed Bit Rate Not AvailableThe action failed because requested guaranteed bit rate is not available.Requested Information Not AvailableThe action failed because requested information is not available.Requested Maximum Bit Rate For DL Not AvailableThe action failed because requested maximum bit rate fo

23、r DL is not available.Requested Maximum Bit Rate For UL Not AvailableThe action failed because requested maximum bit rate for UL is not available.Requested Maximum Bit Rate Not AvailableThe action failed because requested maximum bit rate is not available.Requested Request Type Not SupportedThe RNC

24、is not supporting the requested location request type either because it doesnt support the requested event or it doesnt support the requested report area.Location Reporting CongestionThe action was not performed due to an inability to support location reporting caused by overload.Requested Traffic C

25、lass Not AvailableThe action failed because requested traffic class is not available.Requested Transfer Delay Not AchievableThe action failed because requested transfer delay is not achievable.Resource Optimisation RelocationThe reason for requesting relocation is resource optimisation.Successful Re

26、locationThe reason for the action is completion of successful relocation.Time Critical RelocationRelocation is requested for time critical reason i.e. this cause value is reserved to represent all critical cases where the connection is likely to be dropped if relocation is not performed.TQUEUING Exp

27、iryThe action failed due to expiry of the timer TQUEUING.TRELOCalloc ExpiryRelocation Resource Allocation procedure failed due to expiry of the timer TRELOCalloc.TRELOCcomplete ExpiryThe reason for the action is expiry of timer TRELOCcomplete.TRELOCoverall ExpiryThe reason for the action is expiry o

28、f timer TRELOCoverall.表1 Radio Network Layer causeTransport Layer causeMeaningIu Transport Connection Failed to EstablishThe action failed because the Iu Transport Network Layer connection could not be established.Signalling Transport Resource FailureSignalling transport resources have failed (e.g.

29、processor reset).表2 Transport Layer causNAS causeMeaningNormal ReleaseThe release is normal.User Restriction Start IndicationA location report is generated due to entering a classified area set by O&M.User Restriction End IndicationA location report is generated due to leaving a classified area set

30、by O&M.表3 NAS causeProtocol causeMeaningAbstract Syntax Error (Reject)The received message included an abstract syntax error and the concerning criticality indicated reject.Abstract Syntax Error (Ignore And Notify)The received message included an abstract syntax error and the concerning criticality indicated ignore and notify.Abstract Syntax Error (Falsely Constructed Message)The received message contained IEs or IE groups in wrong order or with too many occurrences.Message Not Compatible