一、英译中　1、 GSM Radio窗口 参数名称参数描述RXLev Full（dBm）信号场强RXLev Sub（dBm）信号场强，在开通下行DTX情况下使用RX QualFull用来描述无线信道误码率的变化趋势。Full是在数据帧的所有时隙（除空闲的）进行抽样测量RX QualSub用来描述无线信道误码率的变化趋势。仅测量指定帧的信号质量FER Full（%）不开通DTX技术条件下的帧丢失率FER Sub（%）开通DTX技术条件下的帧丢失率TX Power手机发射功率TA时间提前量MOSDown下行MOS值MOSUp上行MOS值HSN跳频序列号MAIO移动分配索引偏置TimeSlot占用的时隙号Channel Type信道类型Channel Mode信道模式DSC_Counter下行信令计数器RLT_Current无线信令超时实际值RLT_Maximum无线信令超时最大值TCH业务信道 2、Serving / Neighbor Information窗口 参数名称参数描述Cell Name小区名称BCCH广播控制信道BSIC基站识别码BCCH Level（dBm）广播控制信道场强C1路径损耗原则参数，用于小区选择或重选。C1 = (A - Max(B,0))C2小区重选信道质量标准参数Cell ID小区名称Distance（m）当前点与基站的距离 3、GSM System Parameters窗口 参数名称参数描述MCC所属移动国家号MNC所属移动网络号LAC所属位置区EFR是否使用增强全速率T3212周期性位置更新定时器CR Hysteresis（dB）小区重选滞后CR Offset小区重选偏移Penalty Time小区重选惩罚时间Temp Offset临时偏置RX LevelAccess Min.（dBm）小区最小接入电平MS TX Power Max CCH（dBm）控制信道最大发射功率DTX是否开通DTX（不连续发射技术）。1为开通、0为不开通Retransmitted随机接入最大重发次数 4、Qos窗口 参数名称参数描述SIGN VAR周期内手机接收场强变化值RXQUAL手机接收信号质量MS_Power手机发射功率BLER误块率C Value手机接收信号场强TS_DL_Num上行链路占用时隙数TS_UL_Num下行链路占用时隙数5、GPRS System Parameters窗口 参数名称参数描述RACRoute Area CodeAttach State附着状态SM State会话管理状态P-TMSI分组域临时用户识别码TLLI临时逻辑链路标志T3314设定了手机在没有数据传输时从Ready状态到Standby状态的等待时间NMO一个重要的系统控制参数，根据网络对电路业务和分组业务的寻呼方式及其配合关系可分为三种工作模式（I、II、III），不同的工作模式反映不同的网络能力SNDCP Header CMPR子网汇聚协议头文件压缩方式SNDCP Data CMPR子网汇聚协议数据压缩方式Ciphering Algorithm加密算法 6、PDP Context窗口 参数名称参数描述SM State会话管理状态Radio Priority无线优先级Reliability Class可靠级别Precedence Class优先类Peak T’Put最高流量Mean T’Put平均流量Delay Class延时级别LLC SAPILLC层服务接入点标志IP AddressIP地址NSAPI网络层服务接入点标志 7、GSM C/I窗口 参数名称参数描述ARFCN载频号C/I（dB）载干比RX Level（dBm）接收电平（场强） 8、GSM RLC/MAC窗口 参数名称参数描述GMMSvrStateGPRS移动管理服务状态CSUp上行链路使用的编码方案CSDown下行链路使用的编码方案UL_TFI上行临时流标志DL_TFI下行临时流标志UL _TBF_State上行TBF状态DL _TBF_State下行TBF状态UL_TimeSlot上行链路占用的时隙数DL_TimeSlot下行链路占用的时隙数MAC Mode上下行链路RLC/MAC控制应答信息类型Access Burst接入脉冲PWR Control Channel功率控制信道CTR ACK Mode控制应答方式NCO网络控制命令 9、GSM RLC/ LLC窗口 参数名称参数描述RLCUpThr（bps）RLC层上行吞吐量RLC DownThr（bps）RLC层下行吞吐量LLCUpThr（bps）LLC层上行吞吐量LLCDownThr（bps）LLC层下行吞吐量RLCUpRR（%）RLC层上行重传率RLCDownRR（%）RLC层下行重传率LLCUpRR（%）LLC层上行重传率LLCDownRR（%）LLC层下行重传率　二、GSM Layer3在空口协议栈里Layer 3 Network Layer分为三子层：CM(connect management)MM(mobile management)RR(Radio resource management)其中CM层又分为三部分：CC呼叫控制，SSS补充业务，SMS短信CM Service Request指的就是CC or SSS or SMS的业务请求，向网络表达手机要干这三种事情之一了。完整通话信令流程1.
UL MM CM ServiceRequest//Outgoing Call Attempt2.
DL RR Immediate Assignment3.
UL RR Classmark Change4.
UL RR GPRS Suspension Request5.
DL MM Authentication Request6.
UL MM Authentication Response7.
DL MM CM Service Accept//TCHAssignment Attempt8.
UL CC Setup9.
DL CC Call Proceeding10.
DL RR Assignment Command11.
UL RR Assignment Complete//TCHAssignment Success12.
DL CC Alerting//Outgoing CallAlerting13.
DL RRHandover Command//Handover Attempt14.
DL RRPhysical Information//Handover Success15.
UL RRHandover Complete16.
DL RRPhysical Information17.
DL CC Connect//Outgoing CallConnected18.
UL CC Connect Acknowledge19.
DL RRHandover Command//Handover Attempt20.
DL RRPhysical Information//Handover Success21.
Ul RRHandover Complete22.
DL RRPhysical Information23.
UL CC Disconnect//CallCompleted24.
DL CC Release25.
UL CC Release Complete26.
DL RR Channel ReleaseBSS——&MSC
SETUP:建立(Setup)
MS在此消息中包括被叫号码。MSC——&BSS
CPROC:呼叫进行 (Call Proceeding)
表示MSC正在处理本次呼叫。MSC——&BSS
ASREQ:分配请求 (Assignment Request)要求分配地面电路和空中信道资源。其包含资源的详细描述（如话音速率、信道类型、数据适配、优先级、或MS的级别信息等），同时指出A口上使用的地面电路。BSS——&MSC
ASCMP分配完成(Assignment Complete)已经成功分配地面电路和空中信道资源。如果在指配过程中发生了小区间内部切换，则其应包含新的小区识别而不需发‘切换执行’信息。MSC——&BSS
ALERT:振铃(Alerting)
让MS发回铃音。MSC——& BSS
CONNECT:连接(Connect)
通知MS被叫已经摘机。BSS——&MSC
CONACK:连接证实 (Connect Acknowledge)
对连接的应答MSC——&BSS
DISC:挂机(Disconnect)
被叫挂机。BSS——&MSC
RELEAS:释放 (Release)
要求结束本次事务处理。MSC——&BSS
RELCMP:释放完成(Release Complete)MSC——&BSS
CLCMD:清除命令 (Clear Command)要求释放本次呼叫中使用的空中和地面资源。其消息由MSC发给BSSMAP，指示释放某一无线资源。MSC——&BSS
CLCMP:清除完成 (Clear Complete)已经完成释放，是对清除命令的应答。BSS启动保护定时器，无线接口及指配的地面电路置清除和空闲，MSC释放地面资源。MSC——&BSS
RLSD:(Released)要求结束SCCP连接。连接释放总是从MSC开始的。此消息不应包含用户数据字段。BSS——&MSC
RLC:(Released Complete)SCCP连接的释放完成，是对RLSD的应答。BSS释放分配给相关MS的所有无线资源，之后发SCCP的RLC。该窗口中的信令指示，可双击显示Cause Value值域进行查询。1&
GSM第三层信息（GSM Layer 3 ）该窗口显示GSM移动无线接口第三层的信息，包括无线资源管理（RR）移动性管理（MM）、呼叫控制（CC）三方面信息。该窗口在有跟踪测试手机时有效。*CC层的主要功能为建立、维持和释放呼叫：a、有关呼叫建立的信息（Call Establishment）:Alerting：告警信息，上下行。从网络到主叫移动台或从被叫移动台到网络，用来指示被叫手机启动告警（即回铃音）。包括进展指示及用户--用户信息等Call confirmed：呼叫确认，呼叫确认，该信息由被叫移动台发出，用来确证收到呼叫请求；Call proceeding：呼叫进程，该信息由网络发向主叫移动台，指示被请求的呼叫建立信息已经被接收,不会再接收更多的呼叫建立信息。Connect：连接，从网络到主叫移动台或从被叫移动台到网络，用来指示连接被接 受；Connect
Acknowledge：连接确认，从网络到被叫移动台或主叫移动台到网络，
指示移动台得到一个呼叫（连接完成）；EnergencySetup：紧急建立，由移动台发出，用来启动一个紧急呼叫的建立；Progress：进展，从网络到移动台，指示呼叫的进程；Setup：建立，上下行，指示启动呼叫建立；b、呼叫信息状态（Call Information Phase）
Modify：修改，上下行，请求改变呼叫的承载能力；ModifyComplete：修改完成，指示对呼叫承载能力修改的完成；ModifyReject：修改拒绝，上下行，指示改变呼叫的承载能力请求的失败；UserInformation：用户信息,由移动台发向网络来传输信息到远端用户或由网络发向移动台传输从远端用户来的信息。c、呼叫清除（Call Clearing）Disconnect：断连，从移动台到网络请求清除端到端的连接，或从网络到移动台,指示端到端的连接已经被清除了；(这是正常的)Release：释放，上下行,指示发该信息的设备将要释放TI(处理识别码),接收到该信息的设备等发送释放完成信息后释放TI(处理识别码)ReleaseComplete：释放完成, 上下行,指示发该信息的设备已经释放TI(处理识 别码),接收到该信息的设备将要释放TI(处理识别码)d、与附加业务有关的呼叫（Call Related SS）Facility：设施Hold：保持HoldAcknowledge：保持确认HoldReject：保持拒绝Retrieve：恢复RetrieveAcknowledge：恢复确认RetrieveReject：恢复拒绝e、其它信息CongestionControl：拥塞控制，上下行，指示在传输用户信息时建立和中止流量控制。Notify：通知，上下行，指示信息属于呼叫Status：状态，上下行，用来响应状态查询信息或报告某些确定的错误信息StatusEnquiry：状态查询，上下行，用来请求状态信息StartDTMF：启动双音多频，从移动台到网络StopDTMF：停止双音多频，从移动台到网络StopDTMF Acknowledge：停止双音多频证实，从网络到移动台StartDTMF Acknowledge：启动双音多频证实,从网络到移动台StartDTMF Reject：启动双音多频拒绝,从网络到移动台
*MM层的功能主要为位置管理：
a、注册（Registration）IMSI DetachIndication：IMSI分离指示,由移动台发往网络,在网络中设置一个无效指示LocationUpdating Accept：位置更新接收,网络发向移动台,指示更新或IMSI(国 际移动用户识别码)的附着完成LocationUpdating Reject：位置更新拒绝,网络到移动台,指示更新或IMSI(国际
移动用户识别码)的附着失败LocationUpdating Request：位置更新请求,从移动台发向网络,请求位置更新或
IMSI(国际移动用户识别码)的附着失败 b、连接管理（Connection Management）CMService Accept：CM业务接受，从网络到移动台，指示被请求的业务已经被
接受CMService Reject：CM业务拒绝，从网络到移动台，指示被请求的业务不能提
供CMService Abort：CM业务中断，从网络到移动台，指示被CM的业务中断CMService Request：CM业务请求，从移动台到网络（包括业务请求的类型：位置更新或呼叫建立）CM ReestablishmentRequest：CM重建请求，Abort：中断,网络到移动台 c、其它信息MM_Status：MM状态 *RR层的主要功能为在无线接口上管理传输路径及切换：a、信道建立AdditionalAssignment：附加指配ImmediateAssignment：立即指配,(只包含一个MS指配信息),包括指配信道的描述、"信道请求"的信息字段和接收到"信道请求"帧的帧号、最初的时间提前量、起始时间指示(可选)ImmediateAssignment Extended：立即指配扩展(同时包含两个MS指配信息),同立即指配扩展.ImmediateAssignment Reject：立即指配拒绝b、切换AssignmentCommand：指配命令,网络发向移动台,指示移动台改变当前信道配置,切换到分配的专用信道,启动低层连接建立AssignmentComplete：指配完成,指示主信令链路成功建立.AssignmentFailure：指配失败,包括指配失败的原因HandoverCommand：切换命令,网络向MS发送"切换命令"启动切换程序,包括新信道的特征;需进行通信的新小区特性,包括允许测量程序中所要求的MS预知同步信息(如BSIC和BCCH频率);功率命令;切换参考号码、可选的起始时间指示HandoverComplete：切换完成,MS发向网络,指示切换成功,网络释放原有信道.HandoverFailure：切换失败,MS发向网络,网络释放新的信道PhysicalInformation：物理信息c、信道释放ChannelRelease：信道释放,包括RR原因指示、BA范围PartialRelease：局部释放PartialRelease Complete：局部释放完成 d、寻呼PagingRequest Type 1：寻呼请求类型1,网络给两个移动台发寻呼,包括寻呼模式、移动台1和2需要的信道、移动识别1、移动识别2等PagingRequest Type 2：寻呼请求类型2,网络给三个移动台发寻呼,包括寻呼模式、移动台1和2需要的信道、移动识别1、移动识别2、移动识别3等PagingRequest Type 3：寻呼请求类型3,网络给四个移动台发寻呼,包括寻呼模式、移动台1和2需要的信道、移动识别1、移动识别2、移动识别3、移动识别4等PagingResponse：寻呼响应,移动台到网络,包括密钥序列号及移动识别 e、系统信息SystemInformation Type 1：系统信息类型1,网络到所有移动台,在BCCH上发送,
指示RACH的控制信息及小区配置信息SystemInformation Type 2：系统信息类型2,网络到所有移动台,在BCCH上发送,
指示RACH的控制信息及邻小区的BCCH信息SystemInformation Type 2bis：系统信息类型2bis, 网络到所有移动台,在BCCH上发送,指示RACH的控制信息及扩展的邻小区的BCCH信息SystemInformation Type 3：系统信息类型3, 网络到所有移动台,在BCCH
上发送,指示RACH的控制信息、小区识别号、位
置区识别号、控制信道信息及小区选择参数等SystemInformation Type 4：系统信息类型4, 网络到所有移动台,在BCCH
上发送,指示RACH的控制信息、位置区识别号、
小区选择参数、CBCH信道描述、CBCH移动配置SystemInformation Type 5：系统信息类型5, 网络到所有移动台,在SACCH
上发送,指示邻小区的BCCH信息SystemInformation Type 5bis：系统信息类型5bis, 网络到所有移动台,在SACCH上发送,指示扩展的邻小区的BCCH信息SystemInformation Type 6：系统信息类型6, 网络到所有移动台,在SACCH
上发送, 小区识别号、位置区识别号、允许的
NCC等SystemInformation Type 7：系统信息类型7,用于小区重选SystemInformation Type 8：系统信息类型8,用于小区重选 f、其他信息ChannelMode Modify：信道模式修改,包括信道描述、信道所采用的新模式ChannelMode Modify ACK：信道模式修改证实FrequencyRedefinition：频率重定义MeasurementReport：测量报告,包括服务小区和六个最强邻小区的Rxlev、Rxqual、BSIC、BCCH频率及DTX等ClassmarkChange：等级改变ClassmarkEnquiry：等级询问RRStatus：RR状态三、Cause Value 值的具体意义处理过程 0:01:27刘业标以下是我知道的常见Disconnect / Release Cause :Cause Value Reason ============================================================== 31 BSS or MSC problem 34(beforeAssignmentCommand) TCH Blocking 34(after Assignment Complete) MSC Blocking 41(after Assignment Command) BSS problem, especially DRI problem 41(after Assignment Complete) MSC problem 42 MSC Congestion 44 BSS problem, especially the CIC blocking 111 BSS or MSC problem
14:55:38罗怀瑾以下为已知的CAUSE VALUE集合1 Unassiagned number(未分配的号码（空号）)3 No route to destination(无至目的地的路由)6 Channel unacceptable(不可接受的信道)16 Normal clearing(正常清除)17 User busy(用户忙)18 No user responding(无用户响应)19 User alerting,no answer(已有用户提醒，但无应答)21 Call rejected(呼叫拒绝)22 Number changed(号码改变)26 Non selected user clearing(清除未选择的用户)27 Destination out of order(终点故障)28 Incomplete number(无效号码格式（不完全的号码）)29 Facility rejected(设施被拒绝)30 Response to status enquiry(对状态询问的响应)31 Normal,unspecified(正常，未规定)34 No circuit/channel available(无电路/信道可用)38 Network out of order(网络故障)41 Temporary failure(临时故障)42 Switching equipment congestion(交换设备拥塞)43 Access information discarded(接入信息被丢弃)44 Requested circuit/channel not available(请求的电路/信道不可用)47 Resources unavailable,unspecified(资源不可用，未规定)49 Quality of service unavailable(服务质量不可用)50 Requested facility not subscribed(未预订所请求的设施)55 Incoming calls barred within the CUG 57 Bearer capability not authorized(承载能力未认可)58 Bearer capability not presently available(承载能力目前不可用)63 Service or option not available,unspecified(无适用的业务或任选项目，未规定)65 Bearer service not implemented(承载业务不能实现)68 ACM equal to or greater than ACMmax 69 Requested facility not implemented(所请求的设施不能实现)70 Only restricted digital information bearer(仅能获得受限数字信息承载能力)79 Service or option not implemented(业务不能实现，未规定)81 Invalid transaction identrfier value(无效处理识别码)87 User not member of CUG 88 Incompatible destination(非兼容目的地址)91 Invalid mandatory information(无效过渡网选择)95 Semantically incorrect message(无效消息，未规定)96 Invalid mandatory information(必选消息单元差错)97 Message type non-existent or not implemented(消息类型不存在或不能实现)98 Message type not compatible with protocol state(消息与控制状态不兼容，消息类型不存在或不能实现)99 Information element non-existent or not implemented(信息单元不存在或不能实现)100 Conditional IE error(无效信息单元内容)101 Message not compatible with protocol state(消息与呼叫状态不兼容)102 Recovery on timer expiry(定时器超时恢复)111 Protocol error,unspecified(协议差错，未规定)127 Interworking,unspecified(互通，未规定) 14:58:49罗怀瑾各种原因引起的DISCONN 和用户感受如下： 被叫TCH拥塞 34: No circurt/channel available录音通知,暂时无法接通主叫TCH拥塞 34: No circurt/channel available连续的嘟嘟嘟嘟有寻呼消息,但没有PAGING_RESPONSE 16: normal clearing录音通知,暂时无法接通被叫SDCCH拥塞 16: normal clearing录音通知,暂时无法接通主叫SDCCH拥塞没有DISCONNECT消息没有任何提示音,直接返回SDCCH 掉话 41：temp failure录音通知,暂时无法接通错误号码 28：Invalid number format主叫在听到一阵杂音后，多来米呼叫无应答 18: alerting,but no answer录音通知,用户无人接听CIC 复位 111：protocol error主叫听见多来米被叫位置更新 41：temp failure录音通知,暂时无法接通连接超时 102 主叫听见多来米，被叫无寻呼信息 16:11:57张凌我觉得交换机不同，出现问题的Cause Value也可能不同。例如：Destination out of order这种现象在西门子交换机下面十分罕见，但是华为交换机较常见。 16:30:19张凌CV：32:service not support手机状态： MS1： Channel Request Immediate Assignment CM service request CM Service Reject MS2： 始终处于空闲状态 问题分析： CM Service被拒绝，原因是位置更新失败，或跨LAC以后手机未进行位置更新，或者交换机问题。 16:34:50张凌CV：41:temporary failure手机状态： MS1： 按照正常流程起呼， 在Assignment Complete 5秒钟以后Disconnect MS2： 被叫手机在做位置更新 问题分析： 被叫位置更新无法响应Paging（这是在西门子交换机下的表现，在华为交换机下CV为Destination out of order） 16:43:25张凌CV：41:temporary failure手机状态： MS1： 按照正常流程起呼， 在Assignment Complete 9秒钟以后Alerting 25秒钟以后Disconnect（DL）MS2： Channel Request Immediate Assignment Paging Resqonse Identity Request Identity Response Setup Call Confirmed Alerting Connect 5秒以后进入Idel状态问题分析： 被叫手机发送Connect信号，但基站没有收到，呼叫无法继续。（这是在西门子交换机下的表现，在华为交换机下CV为Destination out of order）可见，西门子交换机的temporary failure和华为交换机的Destination out of order应用现象类似。 9:57:54高勇Cause Value 47:Resources una ms1:Assignment complete ms2:Altering ms1:Disconnect 被叫MS2 Altering以后　MS1发DISCONNECTCause value 47；在同一个小区多次出现，经分析发现是西门子交换机的LTG板的故障，INSLTG板后故障消除，在这个小区所在的BSC的呼叫建立成功率由85%恢复到正常值95%； 10:22:44罗怀瑾关于被叫在进行位置更新时，主叫试呼引起未接通，有两种不同的说法; 1, 由于位置更新的优先级高，被叫手机可以收到PAGING，但是不会有PAGING RESPONSE。2，由于交换机在原 LAC里找不到手机的TMSI，造成没有PAGING消息下发。 我认为是第 2 种情况导致，如果是第一种情况，可以认为是PAGING消息下发后没有回应, 被叫SDCCH 和TCH拥塞也会导致这种情况，CAUSE VALUE 应该是16而不是 41。另外，尚有一事不明，位置更新优先级到底是否为cm_service里最高的？ 15:37:38罗怀瑾我认为，要保证接通率，做好以下的两个方面就差不多了：1，足够的系统容量，系统不会出现SD TCH和CIC拥塞。2，位置更新，通过调整BA—BCCH，让手机只在900－900，单频段上面做LU，可以减少LU的次数。至于其他的一些影响应该是比较少的：以12小时的测试量为例，一共拨打360个电话，接通率要在98％以上，只能有7次未接通。一般拥塞会有3次，LU3次，其他一次。这样的测试结果很不错了！ 最怕的就是在测试过程中碰到堵车，有时一条路走20分钟，会碰到十几次未接通。 23:31:16虞志荣在湖北十堰，系统相对较小，市区4个BSC，但分别有4个LAC，城区DT测试进行因为位置更新而导致呼损。这个问题应该在长沙、北京、杭州等大城市应该经常出现位置更新，请问最后如何处理。 10:32:04刘雷1.合理规划LAC区肯定是很重要的了啊，尤其是在DT测试线路上的LAC优化！2.依我们的经验，在DT测试由于被叫位置更新造成的未接通出现的概率在0.5%左右，CMCC DT接通率满分指标已经调整到了98%，所以还是有一定空间的。3.Ericsson 交换机有Global paging功能，如果第一次寻呼没有成功，可以在一个MSC内部的所有LAC区发2次寻呼消息。通过优化2次寻呼Timer，也可以提高接通率哟！ 9:50:14罗怀瑾北京市区至少有60个LAC以上，不知道是如何解决LU对接通率的影响的，是否在交换机上有什么功能，可以在一次PAGING不成功时，在所有交换机下重新发PAGING消息。如果这样，可能会影响接续时间，但是对提高呼叫成功率还是有好处的。 0:23:46薛绍辉CV 31,normal,unspecified 这种CV曾经遇到过，后来查出来是因为测试卡开了彩铃造成的 16:07:32阮民As one of main call failure scenarioes,chengdu team had paid every efforts to overcome call failure that caused by LUP of MTC.Attached pls find the technical doc I made.The methdology had ever been applyed in a few of systems. 16:12:12阮民As another main call failure scenarios,chengdu team had ever paid every efforts to overcome paging failure of MTC for 99% call connection rate can be reached.Attached pls find the technical doc I made.The methdology I mentioned applied in a few of system,and have postive result reported.
11:37:36高书平修改被叫手机的ba-bcch的后，个别lac边界存在脱网的问题，也碰到过。后来反复测试证实，其原因基本上都是这些lac边界的小区存在过覆盖的问题。即：不删除ba-bcch时，手机在idle mode 下，通过reselect正常选到另一个lac的某个小区。删除后，手机一直在原来的lac小区中，15秒钟的时间，很可能已经越过了其neighbor，再想切换已经不可能，最终脱网。这种情况，通过适当地覆盖调整，一般可以解决。 18:25:19王永CV＝69，Requested facility not implemented流程： MS1: ....... setup assignment command assignment failure disconnect, cv=69:Requested facility not implemented ....... MS2: ...... setup assignment command assignment complete disconnect,cv=69:Requested facility not implemented ....... 后检查发现是MS1占用的小区其中一块载频 MA_fail很高，更换该载频后解决。 10:26:22阮民Wangyong,it is not meaningful to link a specific message flow with a particular H/W problem,it is exactly significant that the specific message to be isolated with a problem scenario you claimed.In this case,you can say, tch access failure will typically result in a assignmnent failure in A interface,then a DISC message with CV69 will be observed both in A and Um.This scenario call us to check tch_access_failure_rate. 12:53:19龚德强还有硬件问题导致的SD不可用，我的手机就遇到过。这时CV应该是16，提示被叫暂时无法接通，时间长了就提示关机了。 15:01:51岳刚CV有很多解释，可能不同的厂家的理解不同，反应出来的表现就不同。个人觉得华为的CV是最变化多端的，当然这和他们要适应客户市场需要来改CV，来达到某些指标的要求可能有关系。最近在恩施的MOTOvip中碰到了一些感觉不是太规范的A口上的消息流程，也测试，分析了一下，把RF5文件放上来给大家看看，希望高手们能提出一些建议，从哪个角度怎么样去和客户沟通，让客户提出来要华为来规范CV。附件为Huawei-MOTO-A-interface.rar 四、软件操作总结1.操作GSM Layer3时，Event和Chart没有联动，可能是因为调用不同的log。2.map窗口操作 问题一：没有出现A（小区信息）解决方法：更换到最新版本问题二：看不到小区上的信息解决方法：放大才能看到问题三：清除map窗口里的RX QualSub，点击×是没有用的。解决方法：应点击工具，在那里面删除，就可以添加新的RX
LevSub。问题四：加载各种视图解决方法：在左边的系统导航里，点击参数，再点击GSM，再点击Downlink Measurement，就可以看到了。3.工具栏操作问题一：小区管理→小区数据，导入xls文件，可能会出现不匹配，这时候，去找一个最规范的xls，保留最上面的表头，将你要导入的数据复制到该最规范的xls中就可以正确导入了。附录 FGSM 无线资源管理的详尽原因Cause value = 0
N正常释放indicatesthat the channel is released because of a normal event.Cause value = 1
Abnormal release,异常释放，没有具体说明indicatesthat the channel is released because of an abnormal event without specifyingfurther reasons.Cause value = 2
Abnormal release,indicatesthat the channel type or channel characteristics are not acceptable.Cause value = 3
Abnormal release,indicatingthat the release is caused by a timer expiry.Cause value = 4
Abnormal release, no aindicatingthat some supervisory function has detected that channel is not active.Cause value = 5
P indicatesthat the channel is released in order to be allocated to a call with priority(e.g. an emergency call).Cause value = 65 Cindicatingthat a handover is unsuccessful because the connection has been released bythe network or the remote user.Cause value = 95 Invalid message,See Annex H, section H5.10.Cause value = 97 Message type non-existenSee Annex H, section H6.2.Cause value = 98 Message not compatible with call state or message type non-existent or notSeeAnnex H, section H6.3Cause value = 100 Invalid informatSee Annex H, section H6.5Cause value = 111 ProtocSee Annex H, section H6.8.ANNEX G(to Recommendation GSM 04.08)GSM specific cause values for mobilitymanagementG.1
Causes related to MSidentificationCause value = 1
Unallocated TMSI.This cause issent to the MS if the MS identifies itself by a TMSI which is notallocated inthe relevant location area and open identification is not requested.Cause value = 2
IMSI unknown in HLRThis cause issent to the MS if the MS is not known (registered) in the HRL.Cause value = 3
Illegal MSThis cause issent to the MS when the MS does not pass the authentication check, i.e.the SRES received from the MS is different from that generated by the network.Cause value = 4
IMSI unknown in VLRThis cause issent to the MS when the given IMSI is not known at the VLR.Cause value = 5
IMEI not acceptedThis cause issent to the MS if the IMEI given cannot be accepted by the network.G.2
Cause related tosubscription optionsCause value = 11 PLMN not allowedThis cause issent to the MS if it requests location updating in a PLMN where the MS, bysubscription is not allowed to operate.Cause value = 12 Location Area not allowedThis cause issent to the MS if it requests location updating in a Locationn area wherethe MS, by subscription, is not allowed to operate.G.3
Causes related toPLMN specific network failures and congestionCause value = 17 Network failureThis cause issent to the MS if the MSC cannot service an MS generated request because ofPLMN failures, e.g. problems in MAP.Cause value = 22
CongestionThis cause issent if the service request cannot be actioned because of congestion(e.g. no channel, facility busy/congested etc.)G.4
Causes related tonature of requestCause value = 32 Service option not supportedThis cause issent when the MS requests a service/facility in the CM SERVICE REQUESTmessage which is not supported by the PLMN.Cause value = 33 Requested service option not subscribedThis causeist sent when the MS requests a service option for which it has no subscription.Cause value = 34 Service option temporarily out of orderThis cause issent when the MSC cannot service the request because of temporaryoutage of oneor more functions required for supporting the service.Cause value = 38 Call cannot be identifiedThis cause issent when the network cannot identify the call associated with a call re-establishment request.G.5
Causes related toinvalid messagesCause value = 96 Mandatory information element error.See Annex H, sect. H.6.1.Cause value = 97 Message type non-existent or not implemented.see Annex H, sect. H.6.2.Cause value = 98 Message non compatible with call state or message type non-existent or notimplemented.seeAnnex H, sect. H.6.3.Cause value = 99 Information element non-existent or not implemented。See Annex H, sect. H.6.4.Cause value = 100 Invalid information element contents。SeeAnnex H, sect. H.6.5.Cause value = 101 Message not compatible with call state。SeeAnnex H, sect. H.6.6.Cause value = 111 Protocol error, unspecified。SeeAnnex H, sect. H.6.8.Annex H(to Recommendation GSM 04.08)Cause definitions for Call ControlH.1
Normal classH.1.1
Cause No. 1 "unassigned (unallocated) number"This causeindicates that the destination requested by the Mobile Station cannot bereached because, although the number is in a valid format, it is not currentlyassigned (allocated).H.1.2
Cause No. 2 "no route to specified transit network"Note:
For further studyH.1.3
Cause No. 3 "no route to destination"This causeindicates that the called user cannot be reached because the networkthrough whichthe call has been routed does not serve the destination desired.H.1.4
Cause No. 6 "channel unacceptable"This causeindicates the channel most recently identified is not acceptable to the sendingentity for use in this call.H.1.5
Cause No. 7 "call awarded and being delivered in an establishedchannel"Note:
Not supportedH.1.6
Cause No.16 "normal call clearing"This causeindicates that the call is being cleared because one of the users involved inthe call has requested that the call be cleared.Under normalsituation, the source of this cause is not thenetwork.H.1.7
Cause No.17 "user busy"This cause isused when the called user has indicated the inability to accept another call.It is notedthat the user equipment is compatible with the call.H.1.8
Cause No. 18 " no user responding"This cause isused when a user does not respond to a call establishment messagewith eitheran alerting or connect indication within the prescribed period of timeallocated (defined by the expiry of either timer T303 or T310).H.1.9
Cause No. 19 " user alerting, no answer"This cause isused when a user has provided an alerting indication but has not provided aconnect indication within a prescribed period of time.H.1.10
Cause No. 21 "call rejected"This causeindicates that the equipment sending this cause does not wish to accept thiscall, although it could have accepted the call because the equipmentsending this cause is neither busy nor incompatible.H.1.11
Cause No. 22 "number changed"This cause isreturned to a calling Mobile Station when the called party numberindicated bythe calling Mobile Station is no longer assigned. The new called party numbermay optionally be included in the diagnostic field. If a network does notsupport this capability, cause No. 1 "unassigned (unallocated)number" shall beused.H.1.12
Cause No. 26 "non-selected user clearing"Note:
Not supportedH.1.13
Cause No 27 "destinationout of order"目标故障This causeindicates that the destination indicated by the Mobile Station cannot bereached because the interface to the destination is not functioning correctly.The term "not functioning correctly" indicates that a signalling message wasunable to be delivere e.g., a physical layer or data linklayer failure at the remote user, user equipment off-line, etc.H.1.14
Cause No. 28 "invalid number format (incomplete number)"This causeindicates that the called user cannot be reached because the called party numberis not a valid format or is not complete.H.1.15
Cause No. 30 "response to STATUS ENQUIRY"This cause isincluded in STATUS messages if the message is sent in response toa STATUSENQUIRY message. See also section 5.5.3.H.1.17
Cause No. 31 "normal, unspecified"This cause isused to report a normal event only when no other cause in the normal classapplies.H.2
Resource unavailable classH.2.1
Cause No. 34 "no circuit/channel available"This causeindicates that there is no appropriate circuit/channel presently available tohandle the call.H.2.2
Cause No. 38 "network out of order"This causeindicates that the network is not functioning correctly and that thecondition is likelyto last a relatively e.g., immediatelyre-attempting the call is not likely to be successful.H.2.3
Cause No. 41 "temporary failure"This causeindicates that the network is not functioning correctly and that thecondition isnot likely to last a e.g., the Mobile Stationmay wish totry another call attempt almost immediately.H.2.4
Cause No. 42 "switching equipment congestion"This causeindicates that the switching equipment generating this cause is experiencinga period of high traffic.H.2.5
Cause No. 43 "access information discarded"This causeindicates that the network could not deliver access information to the rem i.e., a user-to-user information, low layer compatibility,high layer compatibility, or sub-address as indicated in the diagnostic.It is notedthat the particular type of access information discarded is optionallyincluded in the diagnostic.H.2.6
Cause No. 44 "requested circuit/channel not available"This cause isreturned when the circuit or channel indicated by the requesting entity cannotbe provided by the other side of the interface.H.2.7
Cause No. 47 "resource unavailable, unspecified"This cause isused to report a resource unavailable event only when no other cause in theresource unavailable class applies.H.3
Service or option not available classH.3.1
Cause No. 57 "bearer capability not authorized"This causeindicates that the Mobile Station has requested a bearer capability which isimplemented by the equipment which generated this cause but the MobileStation isnot authorized to use.H.3.2
Cause No. 58 "bearer capability not presently available"This causeindicates that the Mobile Station has requested a bearer capability which isimplemented by the equipment which generated this cause but which is not availableat this time.H.3.3
Cause No. 63 "service or option not available, unspecified"This cause isused to report a service or option not available event only when no othercause in the service or option not available class applies.H.4
Service or option not implemented classH.4.1
Cause No. 65 "bearer service not implemented"This causeindicates that the equipment sending this cause does not support thebearercapability requested.H.4.2
Cause No. 66 "channel type not implemented"Note:
Not supportedH.4.3
Cause No. 70 "only restricted digital information bearer capabilityis available"This causeindicates that one equipment has requested an unrestricted bearer service, butthat the equipment sending this cause only supports the restrictedversion ofthe requested bearer capability.H.4.4
Cause No. 79 "service or option not implemented, unspecified"This cause isused to report a service or option not implemented event only when no othercause in the service or option not implemented class applies.H.5
Invalid message (e.g., parameter out of range) classH.5.1
Cause No. 81 "invalid call reference value"This causeindicates that the equipment sending this cause has received a message witha call reference which is not currently in use on the MS-network interface.H.5.2
Cause No. 82 "identified channel does not exist"Note:
Not supportedH.5.3
Cause No. 83 "a suspended call exists, but this call identity doesnot"Note:
Not supportedH.5.4
Cause No. 84 "call identity in use"Note:
Not supportedH.5.5
Cause No. 85 "no call suspended"Note:
Not supportedH.5.6
Cause No. 86 "call having the requested call identity has beencleared"Note:
Not supportedH.5.7
Cause No. 88 "incompatible destination"This causeindicates that the equipment sending this cause has received a request toestablish a call which has low layer compatibility, high layer compatibility,or other compatibility attributes (e.g., data rate) which cannotbeaccomodated.H.5.8
Cause No. 91 "invalid transit network selection"Note:
For further studyH.5.9
Cause No. 94 "incomplete segmented message"Note:
Not supported, no segmentation at layer 3H.5.10
Cause No. 95 "invalid message, unspecified"This cause isused to report an invalid message event only when no other cause in theinvalid message class applies.H.6
Protocol error (e.g., unknown message) classH.6.1
Cause No. 96 "mandatory information element error"This causeindicates that the equipment sending this cause has received a message wherea mandatory information element is missing and/or has a content error (thetwo cases are undistinguishable).H.6.2
Cause No. 97 "message type non-existent or not implemented"This causeindicates that the equipment sending this cause has received a message witha message type it does not recognize either because this is a message notdefined or defined but not implemented by the equipment sending this cause.H.6.3
Cause No. 98 "message not compatible with call state or messagetype non-existentor not implemented"This causeindicates that the equipment sending this cause has received a message suchthat the procedures do not indicate that this is a permissible message toreceive while in the call state, or a STATUS message was received indicating anincompatible call state.H.6.4
Cause No. 99 "information element non-existent or notimplemented"This causeindicates that the equipment sending this cause has received a message whichincludes information elements not recognized because the informationelement identifier is not defined or it is defined but not implementedby the equipment sending the cause. However, the information element isnot required to be present in the message in order for the equipmentsending thecause to process the message.H.6.5
Cause No. 100 "invalid information element contents"This causeindicates that the equipment sending this cause has received an informationelement whic however, one or more of the fields in theinformation element are coded in such a way which has not been implementedby the equipment sending this cause.H.6.6
Cause No. 101 "message not compatible with call state"This causeindicates that a message has been received which is incompatible with the callstate.H.6.7
Cause No. 102 "recovery on timer expiry"This causeindicates that a procedure has been initiated by the expiry of a timer inassociation with Rec. 04.08 error handling procedures.H.6.8
Cause No. 111 "protocol error, unspecified"This cause isused to report a protocol error event only when no other cause inthe protocolerror class applies.H.7
Interworking classH.7.1
Cause No. 127 "Interworking, unspecified"This causeindicates that there has been interworking with a network which doesnot providecauses
thus, the precise cause for a message which isbeing sent cannot be ascertained.CH1灯不亮，Modem无卡或者天线没有插好，modem卡无数据功能或者欠费，也可能当地网络不好。
如果您想留下此文，您可以将其发送至您的邮箱(将同时以邮件内容&PDF形式发送)
相关文章推荐
(Ctrl+Enter提交) &&
已有0人在此发表见解
&在& 09:13收藏到了
&&在信息爆炸的时代，您的知识需要整理，沉淀，积累！Lai18为您提供一个简单实用的文章整理收藏工具，在这里您可以收藏对您有用的技术文章，自由分门别类，在整理的过程中，用心梳理自己的知识！相信，用不了多久，您收藏整理的文章将是您一生的知识宝库！
· 蜀ICP备号-1}