|
《 空中接口学园 》 >> PHS技术 >>>> 掉話協議,請協助分析 |
|
-- 作者：peter_ch -- 发布时间：2005-12-14 09:02:48 Dear All: 這裡有一個掉話的通訊協議從phs-35c抓到的，請各為協助一下!! 因為這個地方一直有這樣的問題 --- Date/Time[05.11.10/14:46:50] [CS-ID:80801E3CDD8] / [PS-ID:000871767] || 0.00000||0 < PS SCCH: 0102020900 80dBuV || 1199.01375||0 --[>Link Assignment Time's u || 1199.01375||0 --[Wait for a Link Channel R [CS-ID:80801E3CDD8] / [PS-ID:000871767] || 1304.99875||0 < PS SCCH: 0102020900 80dBuV || 1762.50208||0 > CS SCCH: 0102071502 40dBuV (Assigned: Abs.Slot 2 / CarrierNo. 21) || 1804.37083||0 < PS SYNC: 0000000000 80dBuV || 1821.87583||0 > CS SYNC: 0000000000 78dBuV || 1829.18458||0 --<< Sync off || 1829.18458||0 -<- Idle TCH || 1841.68833||0 -->> Sync off || 1841.68833||0 ->- Idle TCH || 1934.18458||0 <[45014505] <CC SETUP CC [Bearer Capability:0403808CA4] CC [Calling Party number:6C0F008030313 CC [Called Party number:7005803834343 || 2161.68833||0 >[4501C502] >CC CALL PROC || 2189.18458||0 <[4304] <RT FRq RT [Encryption:091000] RT [TCH Reassign:1507] RT [Zone Info.Indicat.Func.:C0] || 2346.68792||0 >[4305] >RT FRs RT [Encryption:091000] RT [TCH Reassign:1517] RT [Zone Info.Indicat.Func.:C0] || 2374.18417||0 <[4303] <RT EKS RT [Encryption:091000] RT [Encryption Key Set:0D0200D4] || 2556.68792||0 >[4401] >MM ARq MM [Authentication Type:0601] MM [Authentication Random Pattern:0708 || 2594.18417||0 <[4402] <MM ARs MM [Active Chipherring Pattern:0508006 || 2956.68750||0 >[4501C501] >CC ALERT CC [Progress Indicator:1E028288] || 3016.68750||0 >[4501C507] >CC CONN || 12566.67792||0 >[4501C57B] >CC INFO CC [(Code Group 0) Other:2B0120] || 12669.17417||0 <[4501457D] <CC STAT CC [Cause:08030085E3] CC [Call State:14010A] || 27474.15917||0 --<< TX on [CS-ID:80801E3CD58] / [PS-ID:000871767] || 53790.57083||1 < PS SCCH: 0102020900 80dBuV || 54673.07417||1 > CS SCCH: 0102071D03 77dBuV (Assigned: Abs.Slot 3 / CarrierNo. 29) || 54719.94458||1 < PS SYNC: 0000000000 69dBuV || 54737.44875||1 > CS SYNC: 0000000000 77dBuV || 54744.75792||1 --<< Sync off || 54744.75792||1 -<- Idle TCH || 54757.26125||1 -->> Sync off || 54757.26125||1 ->- Idle TCH || 54929.75792||1 <[45014605] <CC SETUP CC [Bearer Capability:0403808CA4] CC [Facility:1C3291A12F020101060902833 CC [Calling Party number:6C0E803031303 CC [Called Party number:700E803031303 || 55202.26125||1 >[4501C602] >CC CALL PROC || 55229.75750||1 <[4304] <RT FRq RT [Encryption:091000] RT [TCH Reassign:1507] RT [Zone Info.Indicat.Func.:C0] || 55602.26083||1 >[4305] >RT FRs RT [Encryption:091000] RT [TCH Reassign:1517] RT [Zone Info.Indicat.Func.:C0] || 55629.75667||1 <[4303] <RT EKS RT [Encryption:091000] RT [Encryption Key Set:0D0200D4] || 56132.26000||1 >[4501C607] >CC CONN CC [Facility:1C0691A203020101] || 56164.75583||1 --<< TX on [CS-ID:80801E3CD98] / [PS-ID:000871767] || 93750.53458||0 < PS SCCH: 0102020900 80dBuV || 94213.03500||0 > CS SCCH: 0102071403 37dBuV (Assigned: Abs.Slot 3 / CarrierNo. 20) || 94413.81875||0 --[<TCH Synchronize Time's u || 94713.03417||0 > CS SCCH: 0102071303 51dBuV (Assigned: Abs.Slot 3 / CarrierNo. 19) || 94913.81292||0 --[<TCH Synchronize Time's u || 94948.78792||0 --[>Link Assignment Time's u || 94948.78792||0 --[Wait for a Link Channel R [CS-ID:80801E3CD98] / [PS-ID:000871767] || 95130.52792||0 < PS SCCH: 0202023100 80dBuV || 95513.03333||0 > CS SCCH: 0102061903 41dBuV (Assigned: Abs.Slot 2 / CarrierNo. 25) || 95713.84250||0 --[<TCH Synchronize Time's u || 96328.80458||0 --[>Link Assignment Time's u || 96328.80458||0 --[Wait for a Link Channel R [CS-ID:80801E3CD98] / [PS-ID:000871767] || 100965.52458||0 < PS SCCH: 0102020900 80dBuV || 101313.02792||0 > CS SCCH: 0102071F03 41dBuV (Assigned: Abs.Slot 3 / CarrierNo. 31) || 101513.80583||0 --[<TCH Synchronize Time's u || 101713.02750||0 > CS SCCH: 0102071903 30dBuV (Assigned: Abs.Slot 3 / CarrierNo. 25) || 101913.81792||0 --[<TCH Synchronize Time's u || 102163.77375||0 --[>Link Assignment Time's u || 102163.77375||0 --[Wait for a Link Channel R [CS-ID:80801E3CD98] / [PS-ID:000871767] || 102230.52333||0 < PS SCCH: 0202023100 80dBuV || 102613.02708||0 > CS SCCH: 0102061603 32dBuV (Assigned: Abs.Slot 2 / CarrierNo. 22) || 102659.27208||0 < PS SYNC: 0000000000 80dBuV || 102676.77625||0 > CS SYNC: 0000000000 40dBuV || 102684.08542||0 --<< Sync off || 102684.08542||0 -<- Idle TCH || 102701.58875||0 -->> Sync off || 102701.58875||0 ->- Idle TCH || 102969.28250||0 -><< TX off [CS-ID:80801E3CDA0] / [PS-ID:000871767] || 105743.64542||0 < PS SCCH: 0102020900 80dBuV || 106867.21000||1 -->> TX on || 106943.75417||0 --[>Link Assignment Time's u || 106943.75417||0 --[Wait for a Link Channel R || 110259.89958||1 --<< TX off [CS-ID:80801E3CDD8] / [PS-ID:000871767] || 110514.89083||0 < PS SCCH: 0102020900 80dBuV || 110862.39333||0 > CS SCCH: 0102071302 77dBuV (Assigned: Abs.Slot 2 / CarrierNo. 19) || 110904.26250||0 < PS SYNC: 0000000000 80dBuV || 110921.76750||0 > CS SYNC: 0000000000 78dBuV || 110929.07625||0 --<< Sync off || 110929.07625||0 -<- Idle TCH || 110941.58000||0 -->> Sync off || 110941.58000||0 ->- Idle TCH || 110944.92042||1 --<< TX off || 111104.07667||0 <[45014705] <CC SETUP CC [Bearer Capability:0403808CA4] CC [Facility:1C3291A12F020101060902833 CC [Calling Party number:6C0E803031303 CC [Called Party number:700E803031303 || 111406.57958||0 >[4501C702] >CC CALL PROC || 111434.07583||0 <[4304] <RT FRq RT [Encryption:091000] RT [TCH Reassign:1507] RT [Zone Info.Indicat.Func.:C0] || 111691.57958||0 >[4305] >RT FRs RT [Encryption:091000] RT [TCH Reassign:1517] RT [Zone Info.Indicat.Func.:C0] || 111719.07583||0 <[4303] <RT EKS RT [Encryption:091000] RT [Encryption Key Set:0D0200D4] || 112111.57917||0 >[4501C707] >CC CONN || 112214.07542||0 <[4501477D] <CC STAT CC [Cause:08030085E0] CC [Call State:140103] || 112436.57875||0 >[4501C74D] >CC REL CC [Cause:080282E5] || 112479.07500||0 <[4501475A] <CC REL COMP || 112696.57833||0 >[4322] >RT RDi RT [Cause:0680] RT [CS Ident.:0880801E3CDD02] RT [PS Ident.:0E00D4D507] || 112714.07500||0 <[4323] <RT RDiC RT [CS Ident.:0880801E3CDD02] RT [PS Ident.:0E00D4D507] || 112819.27208||0 --<< TX off || 112866.77208||0 ->>< TX off --[Wait for a Link Channel Request]-- [CrNo:36]
-- 作者：tom -- 发布时间：2005-12-15 14:57:37 为什么CS的电平会大幅波动呀？ -- 作者：peter_ch -- 发布时间：2005-12-21 15:13:04 因為本通call是行進間測試的 -- 作者：tom -- 发布时间：2005-12-23 15:22:11 谈点感觉吧： CS的信号不是很好：建立过程就不是很顺利，之后又发生重新呼叫型切换。 过程中比较奇怪的是出现了： || 112214.07542||0 <[4501477D] <CC STAT CC [Cause:08030085E0] CC [Call State:140103] 检查一下是否所有终端的流程中都会有这种消息，其他过程应该是正常的。 -- 作者：peter_ch -- 发布时间：2005-12-23 18:59:37 TOM: 你好: 有關於你所看到的不正常的流程,目前我們也注意到了,基本上我們也認為此訊息是不正常的,因為只有在10Mw RP發話才會發現,500Mw的基站是不會有此訊息的,由於此訊息(CC INFO)是從網路端發起的,所以我們去Trace網路端,似乎發現好像是從V5發起的,內容是訊號反轉的訊息,至於為何會發此訊息就不知道囉!由於目前我們測試結果,雖然發現這訊息是不正確的訊息,但基本上用戶還是可以正常通話,所以我們就將掉話的問題放在後面空中的流程.我們從掉話前的幾個流程分析,我們知道是網路端Release此通Call,為何會Release此通call? 我們發現當網路端發起CC CONNECT的訊息給手機,此時手機回一個CC STAT訊息(140103)給網路端,此訊息與先前從RP發話,網路端發CC INFO訊息,手機回CC STAT(140101A)是不一樣的,我們針對手機發起訊息分析,發現140103的訊息似乎不該在此時發給網路端,由於不是正常的訊息,所以網路端Release此通Call,但為何手機會送CC STAT訊息(140103)的訊息給網路端?我們懷疑是網路端發送CC CONN的訊息給手機時,沒有送Facility的訊息給手機,因Facility內有包含(HO return result)的訊息, 目前我們分析的結果如下:不知是否從此提供訊息給你推斷原因所在? -- 作者：tom -- 发布时间：2005-12-25 09:22:20 因此最好把Q.931的协议也检查一下。 目前已经有6条评论 >>> 发表你的见解 |
|
Powered by：Old version Copyright ©2002 - 2019空中接口学园 , 页面执行时间：172.363毫秒 |