一、网络释放链接实例网络
4#主叫端看到10:27(1x系统时间+8小时为北京时间)1x系统时间 02:27:28.340拨通电话,被叫端收到寻呼page response接入成功后02:27:32.42收到网络的realease order即被网络释放形成被叫端失败,主叫端随后 02:27:37.400也被网络释放,是被叫端接入成功后被网络释放(释放缘由并未下发,终端也不可得知)形成本次电话失败,是网络缘由形成,终端行为正常。
附贴4#log:
( 1x 02:27:28.340)(!DO 02:09:11.360)> ETS Id=CP Spy, SpyId=CP IOP ATC recvd data, Data=<CR><LF>^CONN:6,0<CR><LF>
( 1x 02:27:37.400)(!DO 02:09:11.360)> ETS Id=CP Spy, SpyId=CP PE ENG_LAYER2_TR 13 57, PREV=0x06, Length=0x08
, >>> Msg Id=FTC - Order
, ACK_SEQ=5//对消息号5的确认
, MSG_SEQ=4//消息号
, ACK_REQ=0
, ENCRYPTION=0
, USE_TIME=0
, ACTION_TIME=0
, ORDER=Release Order
( 1x 02:27:37.500)(!DO 02:09:11.360)> ETS Id=CP Spy, SpyId=CP IOP ATC recvd data, Data=<CR><LF>^CEND:6,9,25<CR><LF>
3#被叫端:
收到寻呼后page response接入成功后02:27:32.42收到网络的realease order即被网络释放
附贴3#log:
( 1x 02:27:31.740)(!DO 00:37:16.213)> ETS Id=CP Trace, TraceId=CP PE ENG_CP_TR 8 1, CP State=Page Response
( 1x 02:27:31.900)(!DO 00:37:16.213)> ETS Id=CP Spy, SpyId=CP PE ENG_ACCESS_PROC_TR 1 40, PREV=0x06, Length=35
, <<< Msg Id=AC - Page Response
, SERIAL_NUMBER=0x4a5c74
, IMSI_S=0x024ff1e2d2
\\接入成功
( 1x 02:27:32.320)(!DO 00:37:16.213)> ETS Id=CP Spy, SpyId=CP PE ENG_LAYER2_TR 13 13, FORCHTYPE=0x00, PREV=0x06, Length=14
, >>> Msg Id=PC - Order Message
, ACK_SEQ=0
, MSG_SEQ=7
, ACK_REQ=0
, VALID_ACK=1//标志这条ack是否有效
, ADDR_TYPE=IMSI
, ADDR_LEN=5
, IMSI_CLASS=CLASS_0
, IMSI_CLASS_0_TYPE=IMSI_S included
, RESERVED=0
, IMSI_S=0x024ff1e2d2
, ORDER=BS Ack Order
\\接入成功后收到网络的realease order即被网络释放
( 1x 02:27:32.420)(!DO 00:37:16.213)> ETS Id=CP Spy, SpyId=CP PE ENG_LAYER2_TR 13 13, FORCHTYPE=0x00, PREV=0x06, Length=14
, >>> Msg Id=PC - Order Message
, ACK_SEQ=0
, MSG_SEQ=0
, ACK_REQ=0
, VALID_ACK=1
, ADDR_TYPE=IMSI
, ADDR_LEN=5
, IMSI_CLASS=CLASS_0
, IMSI_CLASS_0_TYPE=IMSI_S included
, RESERVED=0
, IMSI_S=0x024ff1e2d2
, ORDER=Release Order【被网络释放】
, ADD_RECORD_LEN=0
, PDU_PADDING=0
( 1x 02:27:32.420)(!DO 00:37:16.213)> ETS Id=CP Trace, TraceId=CP PE ENG_CP_TR 8 1, CP State=Idlespa
二、关于终端未收到paging的缘由资源
3次电话提示没法接通分析以下:
去电log中3次电话失败的主叫端拨通时间点:
( 1x 20:17:53.900)(!DO 01:29:12.693)> ETS Id=CP Spy, SpyId=CP IOP ATC recvd data, Data=<CR><LF>^CONN:1,0<CR><LF>
( 1x 20:18:18.740)(!DO 01:29:14.720)> ETS Id=CP Spy, SpyId=CP IOP ATC recvd data, Data=<CR><LF>^CONN:2,0<CR><LF>
( 1x 20:18:43.300)(!DO 01:29:16.933)> ETS Id=CP Spy, SpyId=CP IOP ATC recvd data, Data=<CR><LF>^CONN:3,0<CR><LF>
来电log即被叫端状况:
在283频点PN380小区上20:17:45退出业务态后在283频点PN380小区上每一个1x寻呼周期都正常监听寻呼,3次主叫拨通时间点后的10多秒内的全部寻呼周期的QPCH信道都指示为off即快速寻呼信道都指示没有本终端寻呼,终端始终在PN380小区未作切换中间也未从新作注册到20:19:29收到寻呼并MT成功(即第4次电话成功),RSSI约-85dbm小区导频强度为-5~-8db信号正常,因此应该是网络缘由(具体终端也不可得知)未下发寻呼形成前面3次电话未收到寻呼而失败。
附贴被叫端第2次电话失败(其余2次也是如此)监听寻呼都为off的log:
( 1x 20:18:20.480)(!DO 01:18:51.173)> ETS Id=CP Spy, SpyId=CP PE ENG_LAYER2_TR 13 13, FORCHTYPE=0x00, PREV=0x06, Length=13
, >>> Msg Id=QPCH - Indicator
, PILOT_PN=380
, QPCH_RATE=0 [4800 bps]
, Indicator=PI 1
, Position=135
, Status=0 [Off]
( 1x 20:18:23.040)(!DO 01:18:53.626)> ETS Id=CP Spy, SpyId=CP PE ENG_LAYER2_TR 13 13, FORCHTYPE=0x00, PREV=0x06, Length=13
, >>> Msg Id=QPCH - Indicator
, PILOT_PN=380
, QPCH_RATE=0 [4800 bps]
, Indicator=PI 1
, Position=90
, Status=0 [Off]
( 1x 20:18:25.580)(!DO 01:18:56.133)> ETS Id=CP Spy, SpyId=CP PE ENG_LAYER2_TR 13 13, FORCHTYPE=0x00, PREV=0x06, Length=13
, >>> Msg Id=QPCH - Indicator
, PILOT_PN=380
, QPCH_RATE=0 [4800 bps]
, Indicator=PI 1
, Position=46
, Status=0 [Off]
( 1x 20:18:28.140)(!DO 01:18:58.640)> ETS Id=CP Spy, SpyId=CP PE ENG_LAYER2_TR 13 13, FORCHTYPE=0x00, PREV=0x06, Length=13
, >>> Msg Id=QPCH - Indicator
, PILOT_PN=380
, QPCH_RATE=0 [4800 bps]
, Indicator=PI 1
, Position=1
, Status=0 [Off]
( 1x 20:18:25.600)(!DO 01:18:56.133)> ETS Id=CP Spy, SpyId=CP Search Results Active, Num Act=0x01, Num Cand=0x00, Num Nghbr=0x23
, Stale.0=0, Pilot PN.0=380, Phase.0=24320, Strength.0=-6.1009 //信号质量,
( 1x 20:18:20.480)(!DO 01:18:51.173)> ETS Id=DSPM Spy, SpyId=DSPM Rfc RxAgcDc, rxPath=0x0000, pwrRef(dBm)=-97.00, gainRef(Lg2)=23.78, RxPower(dBm)=-83.84,//RSSIrem
三、SRLTE方案中c2kmodem申请不到RF资源it
主叫端在14:56:52进入链接态RTC - Service Connect Completion,随后网络会下被叫寻呼
被叫端:
14:56:54.700快速寻呼信道指示为非off,14:56:54.800正常醒来准备监听PCH信道但因为与MD1的监听寻呼相冲突而申请不到RF天线资源HSC_RESYNC_DENIED_MSG直到14:56:55.100才收到PCH消息并立刻睡下,因此是C2K监听寻呼使用天线与MD1监听寻呼相冲突而申请不到RF资源致使没收到这次电话寻呼而MT失败。SRLTE方案是会存在这种状况的,是正常状况。
附贴被叫端log:
( 1x 14:56:54.700)( DO 14:56:54.640)> ETS Id=CP Spy, SpyId=CP PE ENG_LAYER2_TR 13 13, FORCHTYPE=0x00, PREV=0x06, Length=13
, >>> Msg Id=QPCH - Indicator
, PILOT_PN=274
, QPCH_RATE=0 [4800 bps]
, Indicator=PI 1
, Position=4
, Status=2 [Undefined]
( 1x 14:56:54.800)( DO 14:56:54.746)> ETS Id=CP Trace, TraceId=CP Report Status, Status=PSW_IND_WAKEUP
( 1x 14:56:54.800)( DO 14:56:54.800)> ETS Id=CP Trace, TraceId=CP CLC MSGID TRACE, MsgName=IDP_HSC_RESYNC_DENIED_MSG
( 1x 14:56:55.100)( DO 14:56:54.800)> ETS Id=CP Spy, SpyId=CP PE ENG_LAYER2_TR 13 13, FORCHTYPE=0x00, PREV=0x06, Length=38
, >>> Msg Id=PC - General Page
, CONFIG_MSG_SEQ=1
, ACC_MSG_SEQ=1
, CLASS_0_DONE=0
( 1x 14:56:55.100)( DO 14:56:54.800)> ETS Id=CP Trace, TraceId=CP HSC MsgId, MsgName=L1D_SLEEP_MSGio
四、小区信号质量变差,网络未指派好的小区到激活集终端
在通话中网络指配了3个激活小区PN126/368/264,而随后激活小区导频强度极差<-20db而候选集PN24变得极好终端申请了将PN24加入到激活集,但还没加上就因激活小区导频强度极差出现5秒内FFCH译码全错即TC_RELEASE_FADE而掉话。因此是小区信号质量骤变且网络指配PN24从激活集移除致使的5秒内FFCH译码全错而掉话。
附贴log:
( 1x 16:05:24.800)(!DO 00:03:38.080)> ETS Id=CP Spy, SpyId=CP Search Results Active, FRCCounter=0x000000001ed57536, Num Act=0x03, Num Cand=0x01, Num Nghbr=0x2c
激活集:
Stale.0=0, Pilot PN.0=24, Phase.0=1536, Strength.0=-21.6134 ,
Stale.1=0, Pilot PN.1=196, Phase.1=12588, Strength.1=-18.7596 ,
Stale.2=0, Pilot PN.2=126, Phase.2=8022, Strength.2=-17.8467 ,
候选集:
, Stale.0=0, Pilot PN.0=104, Phase.0=6691, Strength.0=-16.0911 ,
, <<< Msg Id=RTC - Pilot Strength measurement
, ACK_SEQ=0
, MSG_SEQ=5
, ACK_REQ=1
, ENCRYPTION=0
, REF_PN=24
, PILOT_STRENGTH=43
, KEEP=1
, PILOT_PN_PHASE.0=12588
, PILOT_STRENGTH.0=38
, KEEP.0=1
, PILOT_PN_PHASE.1=8022
, PILOT_STRENGTH.1=36
, KEEP.1=1
, PILOT_PN_PHASE.2=6691
, PILOT_STRENGTH.2=32
, KEEP.2=1
, PILOT_PN_PHASE.3=23552
, PILOT_STRENGTH.3=28
, KEEP.3=1
, PILOT_PN_PHASE.4=16894
, PILOT_STRENGTH.4=28
, KEEP.4=1
\\网络分配了3个激活小区:PN126/368/264
( 1x 16:05:25.040)(!DO 00:03:38.080)> ETS Id=CP Spy, SpyId=CP PE ENG_LAYER2_TR 13 57, FRCCounter=0x000000001ed91ead, PREV=0x06, Length=0x19
, >>> Msg Id=FTC - MEID Universal Handoff Direction //网络分配的三个激活小区未包含信号好的24
, NUM_PILOTS=3
, PILOT_PN.0=126
, ADD_PILOT_REC_INCL.0=0
, PWR_COMB_IND.0=0
, CODE_CHAN_FCH.0=40
, QOF_MASK_ID_FCH.0=0
, PILOT_PN.1=368
, ADD_PILOT_REC_INCL.1=0
, PWR_COMB_IND.1=0
, CODE_CHAN_FCH.1=40
, QOF_MASK_ID_FCH.1=0
, PILOT_PN.2=264
, ADD_PILOT_REC_INCL.2=0
, PWR_COMB_IND.2=0
, CODE_CHAN_FCH.2=33
, QOF_MASK_ID_FCH.2=0
, RESERVED=0
, REV_FCH_GATING_MODE=0
, RESERVED_BLOB_LENGTH8=0
, PLCM_TYPE_INCL=1
, PLCM_TYPE=1
, PLCM_39=0x03a7d275af
( 1x 16:05:28.440)(!DO 00:03:38.080)> ETS Id=CP Spy, SpyId=CP Search Results Active, FRCCounter=0x000000001f0d021a, Num Act=0x03, Num Cand=0x03, Num Nghbr=0x2c
激活集:
Stale.0=0, Pilot PN.0=126, Phase.0=8002, Strength.0=-21.7699 ,
Stale.1=0, Pilot PN.1=368, Phase.1=23535, Strength.1=-21.3887 ,
Stale.2=0, Pilot PN.2=264, Phase.2=16901, Strength.2=-21.5752 ,
候选集:
, Stale.0=0, Pilot PN.0=104, Phase.0=6703, Strength.0=-22.8500 ,
Stale.1=0, Pilot PN.1=24, Phase.1=1553, Strength.1=-2.1394 ,
Stale.2=0, Pilot PN.2=196, Phase.2=12608, Strength.2=-25.7097 ,
( 1x 16:05:30.140)(!DO 00:03:38.080)> ETS Id=CP Trace, TraceId=CP Report Event, FRCCounter=0x000000001f26fe45, Event=EV_TC_RELEASE_FADE//这个消息表示5秒内译码全错,定时器超时
( 1x 16:05:30.160)(!DO 00:03:38.080)> ETS Id=CP Spy, SpyId=CP IOP ATC recvd data, FRCCounter=0x000000001f271c8f, Data=<CR><LF>^CEND:0,4545,22<CR><LF>rsa