ma_fail_from_ms

合集下载

常见载频故障分析

常见载频故障分析

常见载频故障分析通过对近期网络优化工作的总结,发现网络优化中大部分问题都出现在硬件载频故障上。

通过和资深工程师的探讨,了解到载频故障率远高于基站其它类型故障。

因此如何及时、快速地发现并解决载频问题,将是我们无线网络优化工作的重中之重。

下面就载频一些故障现象进行一些分析、探讨。

1. 载频退服很显然,载频退服可导致小区无线容量丢失,严重时小区会产生拥塞,引起用户大量投诉。

2. 覆盖差、信号不稳或没信号这表明基站发射部分有问题。

原因有载频发射功率小或无发射功率,同小区载频发射功率不平衡,耦合器、天馈线故障等。

3. PATH_BALANCE异常PATH_BALANCE是OMC_R上载频的一个统计项,这个统计主要考察基站收发信系统接收部分性能,其计算公式为:PATH_BALANCE=UPLINK_PATH_LOSS-DOWNLINK_PATH_LOSS+110其中:UPLINK_PASS_LOSS=ACTUAL_MS_TXPWR-RXLEV_UL DOWNLINK_PASS_LOSS=ACTUAL_BTS_TXPWR-RXLEV_DL其统计的正常结果应在110左右。

如果某个载频统计结果远高于或低于此值,则表明这个载频收发信通道存在问题,会影响正常通话,甚至不能通话,这类故障可分为以下两种情况:a. 载频统计结果高于120,则表明可能载频的射频部分的RX通路故障导致上行通道损耗过大。

故障现象:手机无信号或有信号打不了电话。

判断方法:进行基站接收通道调测,未能解决问题,可将故障点定位在SURF或载频上,再通过更换载频即可判定载频是否损坏。

b. 载频统计结果低于100,则表明可能载频的发射部分的TX通路故障导致载频发射功率过低、下行通道损耗过大。

故障现象:手机无信号或信号很差。

判断方法:进行基站发射通道调测,未能解决问题,可将故障点定位在合路器或载频上,再通过更换载频即可判定载频是否损坏。

4. BER高这项统计表明载频的下行通道误码率的大小,在空中接口中,误码率分为0~7共八级,这八级与误码率对应关系如下:0 = 0.14% 1 = 0.28%2 = 0.57%3 = 1.13%4 = 2.26%5 = 4.52%6 = 9.05%7 = 18.10%BER越高表明手机接收到基站的信号质量越差。

PMS公式定义

PMS公式定义
KPI名称
告警类别
下行RLC流量MCS1比例
CELL
下行RLC流量MCS6比例
CELL
下行RLC流量MCS8比例
CELL
下行RLC流量MCS9比例
CELL
下行RLC数据重传率_CSx 上行RLC数据重传率_CSX
CELL CELL
下行RLC数据重传率_MCSX CELL
上行RLC层平均吞吐量
CELL
CARRIER system cell CELL rsl rsl cell cell cell system system mtl mtl
ohoa_adj_chn_intf_ratio nbr air_dl_blks_q3_cs1 air_dl_blks_q3_cs2 ms_class_9_req ms_class_11_req cell cell cell cell
cell cell cell cell cell cell BSS CARRIER CELL CARRIER nbr cell system bss system cell cell
ohoa_powerbdgt cell mean_time_between_ha cell ndovers egprs_avail_pdtch_mean CELL ul_data_flux mtp_re_tx ohoa_powerbdgt_ratio BSS mtl nbr
ohoa_band_reasign_ratio nbr ms_class_1_10_req ms_class_10_req drop_probability dl_busy_pdtch_mean dl_data_flux busy_tch_hr_mean HO_Failure_Recovered_R ate mtu_dcs2000_only GPRS_AVAIL_PDTCH_MA X 上行RLC层cs4 小区上行EGPRS数据总量 KByte cell cell bss cell cell SYSTEM bss cell CELL SYSTEM CELL

labview错误代码

labview错误代码

LabVIE‎W错误代码表‎表1 LabVIE‎W错误代码(Error Codes)的范围错误!未定义书签。

表2 网络(Networ‎k ing)错误代码表.........错误!未定义书签。

表3 仪器驱动(Instru‎m ent Driver‎)错误代码表错误!未定义书签。

表4 VISA错误‎代码表................................错误!未定义书签。

表5 报表生成(Report‎Genera‎t ion)错误代码表错误!未定义书签。

表6 公式翻译器(Formul‎a Parsin‎g)错误代码表错误!未定义书签。

表7 数学(Mathem‎a tics)错误代码表 .......错误!未定义书签。

表8 信号分析工具‎包(Signal‎Proces‎s ing Toolse‎t)错误代码表 ............................................................................错误!未定义书签。

表9 信号分析(Signal‎Proces‎s ing)错误代码表错误!未定义书签。

表10 逐点分析(Point By Point)错误代码表错误!未定义书签。

表11 数据采集(DAQ)错误代码表 .........错误!未定义书签。

表12 波形(Wavefo‎r m)错误代码表.........错误!未定义书签。

表13 Apple Event错‎误代码表 ....................错误!未定义书签。

表14 PPC错误代‎码表 ................................错误!未定义书签。

表15 注册表访问(Window‎s Regist‎r y Access‎)错误代码表 ... 错误!未定义书签。

表16 GPIB错误‎代码表 ..............................错误!未定义书签。

用户投诉常见问题及分析

用户投诉常见问题及分析

用户投诉常见问题及分析在平时处理用户投诉中经常会碰到的问题分类:1.无网络服务,没有信号或信号很弱;2.无电话建立,做主叫时电话拨不出去,做被叫时“用户不在服务区或用户已关机”;3. 电话没有声音;4. 掉话;5. 通话中有噪音;6.通话中有串话现象等。

通过空中接口的信令流程和话务统计,对上述故障依次分析如下:1 空中接口信令流程2 故障分析2.1. 无网络服务,没有信号或信号很弱:无网络服务是指网络不能给手机提供服务,即手机不能利用随机接入控制信道来发送消息,那么此情况只能是手机的接收电平低于C1值,手机进入盲区即会发生这种情况。

出现这种情况时往往与用户所处的地理位置密切相关,比如处于小区交界处、网络覆盖边沿,地下室等。

2.2. 无电话建立这种情况表现为手机拨了号码之后,马上就跳掉了,手机显示屏上仍回到“中国移动通信”或“中国联通“这样的原始状态。

发生此故障的原因有:(1)没有占用上独立专用控制信道a)当手机占用随机接入信道后,在接入容许控制信道上如果收到“立即分配拒绝”消息,那么应该是由独立专用控制信道拥塞引起的,此时我们可以通过统计值SDCCH_CONGESTION来加以证实,如拥塞确实比较厉害的话,就应该增加独立专用控制信道的配置,特别是对那些LAC 交界处的站更应引起注意。

(在MOTOROLA设备中,通过CHG_ ELEMENT命令修改NUMBER _ SDCCHS _ PREFERRED参数可实现对SDCCH配置,还可通过修改 MAX_ NUMBER_ OF_ SDCCHS参数和其它相关参数实现独立专用控制信道的动态分配以满足独立专用控制信道需求的突发性)。

另外还应该注意独立专用控制信道被吊死的现象,这可通过DISP_ CELL _ STATUS命令来查看独立专用控制信息的总体使用情况,并通过DISP_ RTF_ CHAN命令来查看独立专用控制信道的具体占用情况。

b)基站发送了“立即分配”消息,但是手机没有发送“连接管理服务请求”消息接入独立专用控制信道,这种情况应该来说是极少发生的。

686 RAPID COMMUNICATION nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn n

686 RAPID COMMUNICATION nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn n

important additional findings like common iliac vein or inferior vena cava thrombosis (Fig.4).In two further cases,unknown contralateral thrombosis was seen with True-FISP MR-venog-Fig.1True-FISP MR-venography (TR 5.0ms,TE 2.5ms,860 860 m in-plane resolution)in a 42year old patient without thrombosis.Veins and arteries are displayed with a bright signal.A black rim surrounding the vessel lumen is readily apparent (magnification).True-FISP sequence for MR-venography,which may allow for a high-contrast MR-venography without costly contrast agent.Technical considerations of MR-venography using high resolution True-FISPTrue-FISP sequences demonstrate a T1/T2contrast due to data acquisition in a steady state condition of the transverse magnetization [9].Therefore,the long T2of blood allows for Fig.2True-FISP MR-venography (TR 5.0ms,TE 2.5ms,860 860 m in-plane resolution)in a 31year old pregnant plete left femoral (a )and iliac (b )vein thrombosis is diagnosed because of the dark signal,whereas open superficial and deep right veins show a bright signal.The inferior vena cava is highly compressed due to pregnancy (arrow in c ).in the inferior vena cava(Fig.4),a highly important finding for therapy.In two other patients,tumor masses causing venous compression were diagnosed on the MR-images.This shows the Recently,new MR-approaches for fast detection ofwith fast MR-venography。

GSM告警

GSM告警

BCUP:0. BCUP: Unexpected Board Type此告警表明BCUP(Base Controller Unit Power)出现问题。

1. BCUP: Serial Bus Connection Failure此表明BCUP与SBUS(Serial Bus)间的连接中断了。

因此SBUS无法完成FM与BCUP间的通讯。

8. BCUP: Output Failure此告警表明BCUP无法正常输出功率。

9. BCUP: Input Failure此告警表明BCUP的电源输入出现问题。

10. BCUP: Over Temperature Warning此告警表明电源模块温度过高。

BSS0. BSS: Last MTL Link Failure - Signalling Point Inaccessible此告警表明BSS和MSC间的最后一条MTL链路也退出服务了。

0. BSS: Paging request from MSC protocol error - PM此告警表明当MSC发送的page request消息中出现协议出错的数目超过了、门限值。

1. BSS: Call Processing Failure - MSC Detected SCCP Down此告警表明在MSC处出现SCCP fail,使得BSS无法处理呼叫,发送消息。

1. BSS: Routing failure - syntax error detected - PM此告警表明在SCCP消息中出现语法错误的数目超出了门限值。

2. BSS: Call Processing Failure - MSC Detected BSSAP Down此告警表明在MSC处出现BSSAP fail,使得BSS无法处理呼叫,发送消息。

2. BSS: Routing failure - reason unknown - PM此告警表明从MSC收到的错误的SPC的数目超出门限值。

PMS告警定义、数量和原因分析

PMS告警定义、数量和原因分析

2 BSS
MOTO
224 单载频高掉话次数(2级)
2
CARRIE rf_losses_tch_total>10 and R rf_losses_tch_total<=20 CARRIE Intf_on_idle_ave>10 and R Intf_on_idle_ave<=20 ho_success_rate<90 and TCH_Erlang>1
告警号 告警名称
级别
告警类别 告警公式
设备类型
123 小区TCH接入失败高(1级) 124 小区呼叫建立成功率低(1 级)
1 CELL 1 CELL
ma_fail_from_ms>100 Call_Setup_Success_Rate <70 and TCH_Erlang >2 Handover_Success_Rate <70 and busy_tch_mean>2 and out_ho_cause_atmpt>400
MOTO
226 IOI高(2级)
2
MOTO
222 BSC切换成功率低(1级)
1 BSS
ቤተ መጻሕፍቲ ባይዱMOTO
225 载频BER高(3级) 228 上行质量差(2级) 229 下行质量差(1级) 230 下行质量差(2级) 231 小区TCH高拥塞(3级)
ber_mean_ave>2.5 and CARRIE ber_mean_ave<=4 and R busy_tch_mean>0.1 CARRIE 上行话音质量0_2级>=50 and 上行话音质 2 R 量0_2级<70 and busy_tch_mean>1.2 CARRIE 下行话音质量0_2级<50 and 1 R busy_tch_mean>1.2 and ber_bin0>0 CARRIE 下行话音质量0_2级>=50 and 下行话音质 2 R 量0_2级<70 and busy_tch_mean>1.2 3 3 CELL Customer_TCH_Block_Rate>10

呼叫信令流程

呼叫信令流程

assignment channel assigned stop T11 alloc_ tch_usage ….
start T10 assignment channel expire T10 release request
clear request
assignment failure ma_fail_from_ms stop T10 release request clear request Only at this time, the MSC begain to send the called address to PSTN assignment completed stop T10 assignment successful stop assign_successful connection required connection response success assignment complete total_call and alloc_tch counter works before alerting signal was sent. For drive test, the drop call should be considered after this point. alerting connect T313 total_call ma_complete_to_msc (total call+intracellHO) stop MSC timer for assignment IFAM (initial and final address) ACM (address complete) PSTN
AGCH
immediate assign. "123 tone" reject T3126 start T3122 expire T3122 channal request RSS channel activation channel activetion acknowledge
  1. 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
  2. 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
  3. 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。

ma_fail_from_ms有几种可能:
MSC refuses the establishment of the SCCP connection through a Connection Refuse message.(MSC拒绝SCCP连接)
TCH Assignment Failures due to TCH blocking at the BSS.(因为拥塞而使TCH指配失败,此时统计为alloc_tch_fail)
The failure of the MS to access the target TCH channel with subsequent successful returning to the SDCCH channel.(未占上tch,返回sdcch)
TCH Assignment Failures (Lost MS) due to the failure of the mobile to access the target TCH channel and failure to re-establish on the SDCCH channel.(未占上tch,返回sdcch失败)
如何鉴别此类问题
The MSC normally responds a Connection Confirmed (CC) to the request of stablishment of the SCCP connection (CR). Nevertheless, if something happened in the MSC (e.g. software failure) or the CR message (e.g. protocol error), a Connection Refuse (CREF) may be returned representing failure of establishing the SCCP connection.
You can easily identify it via statistics. But, be aware of the fact that the MSC may return a CREF in response to the CR with L3 info of IMSI detach, which, in fact, can save the load on A interface.
If there is no TCH available or software error conditions existing in CRM or RRSM, the assignment procedure may also fail with the cause of TCH blocking, which can be measured by raw statistics MA_CMD_TO_MS_BLK(TCH拥塞统计). Check cell status for possible reasons.
When a free TCH has been allocated by the CRM, the RRSM will send an Assignment Command to the MS. Meanwhile, it pegs MA_CMD_TO_MS(有TCH资源,而且向MS发送了指配命令)and starts a timer BSSMAP_T10 guarding for receipt of the Assignment Complete message. If the MS failed in tuning to the new TCH upon receipt the Assignment Command, it would revert to the SDCCH and return an Assignment Failure message, which causes the RRSM to stop the timer and pegs the counter MA_FAIL_FROM_MS(分配了TCH,MS却没有占上).
If both Assignment Complete and Assignment Failure are not received by RRSM before the BSSMAP_T10 expiry, which means the SDCCH is lost while the assignment procedure is undergoing, the procedure aborts with no counters pegged. But, you could still trace the number of times it occurs by following formula, MA_CMD_TO_MS-INTRA_CELL_HO_SUC-MA_COMPLETE_TO_MSC-MA_FAIL_FRO M_MS. The reason why you have to deduct INTRA_CELL_HO_SUC is both MA_CMD_TO_MS and MA_FAIL_FROM_MS not only pegged by original assignment but intra_cell handovers. Meanwhile, you’ll probably see low TOTAL_CALLS compare to OK_ACC_PROC and high RF_LOSSES_SD.
Detailed analysis
如果CONN_REFUSED远远大于IMSI_DETACH,则establishment of SCCP connection 出现问题,进一步跟踪:
Filters
Connection Request (the LCF in which the BTS resides)
fil create tag 00100900h
Connection Confirm (the LCF in which the BTS resides)
fil create tag 00040902h
Connection Reject (the LCF in which the BTS resides)
fil create tag 00080903h
For detailed field description, please refer to ITU Q.713 and GSM specification 04.08/08.08
只通过统计定位问题
跟踪RSS到CP的消息流程是查明问题的快捷方式
Filters
Assignment Command (at the BTP):
fil create tag 0xxxx0201h msg[9] 6 msg[10] 2eh
Assignment Complete (at the BTP)
fil create tag 0xxxx0202h msg[9] 6 msg[10] 29h
Assignment Failure (at the BTP)
fil create tag 0xxxx0202h msg[9] 6 msg[10] 2fh
Remarks: Assignment Command is imbedded as layer 3 info. in RSS-CP message Data Request while Assignment Complete and Assignment Failure are in Data Indication.
Ma_Fail_From_MS/Total_calls的结果大于10%左右的时候,说明当小区资源管理器分配一个空闲TCH信道给手机用户后,手机用户占用不到这个载频。

通常其比例大于总时段呼叫总数的10%的情况下,可认为此小区存在硬件问题。

为判断是哪个载频存在问题,需要使用基站中过滤消息的功能,即根据话务信道分配命令,话务信道分配成功及话务信道分配失败三种信息间的关系来推断出手机无法占用信道的载频。

perl工具的应用
首先通过getpm的rawcel查出哪些小区的MA_FAIL_FROM_MS较高
收集RSS到CP的消息,通过超级终端登陆到BSC上,并capture the log file
例:
tty_rlogin YICBSC01G
chg_l
3stooges
4beatles
set_mmi exec_mon
rl 24 1015h ’(24=站号+1)
fil create tag 0xxxx0201h msg[9] 6 msg[10] 2eh
fil create tag 0xxxx0202h msg[9] 6 msg[10] 29h
fil create tag 0xxxx0202h msg[9] 6 msg[10] 2fh
fil start all
收集数据约20分钟,fil stop all
fil delete all
用perl分析问题出现在哪个频点上
例如将perl放在D盘根目录下,将收到的log文件例如site_name.txt放在perl/bin下,进入DOS操作系统模式,进入D:\perl\bin下,键入perl finder.txt site_name.txt
将有报告产生,便可以查出分配次数高的载频。

查找到RTF所在地载频,将载频更换。

相关文档
最新文档