呼叫流程調(diào)試中常見(jiàn)問(wèn)題的定位

1、調(diào)試中常見(jiàn)問(wèn)題的定位黃志鋼1 概述使用模擬工具RNCCN進(jìn)行呼叫流程測(cè)試時(shí)，經(jīng)常遇到呼叫不成功的情況，本文檔主要介紹呼叫的流程（重點(diǎn)介紹RNC的流程）以及呼叫過(guò)程中經(jīng)常遇到的問(wèn)題，并附上RNC相關(guān)的打印分析。調(diào)試過(guò)程中經(jīng)常用到的調(diào)試工具：CN統(tǒng)一網(wǎng)管的信令跟蹤（包括平臺(tái)信令部分和呼叫業(yè)務(wù)部分）、業(yè)務(wù)觀察（其中的失敗觀察部分）。由于RNC的信令跟蹤還沒(méi)有提供使用，目前RNC的問(wèn)題主要靠前臺(tái)打印來(lái)定位。本文檔適用于對(duì)呼叫流程不熟悉的測(cè)試或開發(fā)人員，用于幫助定位呼叫過(guò)程中的問(wèn)題。2 IMSI附著IMSI附著是通過(guò)位置更新流程來(lái)實(shí)現(xiàn)的，流程比較簡(jiǎn)單，在不做鑒權(quán)、TMSI重分配的情況下，NAS層只有兩條

2、消息交互過(guò)程，如下所示：注：InitUEMsg：初始UE消息，是RANAP協(xié)議的一條信令消息；InitDTMsg：初始直傳消息，是RRC協(xié)議的一條信令消息DT：上行或下行直傳消息，圖中的DT消息應(yīng)該分解成兩條消息來(lái)理解，一條是UE和RNC之間的RRC直傳消息，另一條是RNC和CN之間的RANAP直傳消息。位置更新成功時(shí)，信令跟蹤中MM層捕獲的信令如下：MM: LOCATION UPDATING REQUESTMM: LOCATION UPDATING ACCEPT常見(jiàn)失敗原因分析如下：Ø 如果信令跟蹤中沒(méi)有任何消息，業(yè)務(wù)失敗觀察中也沒(méi)有任何顯示，依次排查下列流程： RRC連接建立、I

3、U連接建立。如果上面兩個(gè)流程都沒(méi)有問(wèn)題，很可能是RNC側(cè)RANAP消息中參數(shù)錯(cuò)誤（如MCC、MNC配置不一致等等）。Ø 位置更新拒絕：信令跟蹤中捕獲到LOCATION UPDATING REJECT，可能的原因包括：模擬工具中配置UE的IMSI號(hào)碼不正確；鑒權(quán)沒(méi)有關(guān)閉（此時(shí)在信令跟蹤中能捕獲到鑒權(quán)消息）；MSCServer與HLR鏈路不通等。Ø 其他情況：調(diào)試過(guò)程中遇到過(guò)LOCATION UPDATING ACCEPT消息無(wú)法發(fā)送到RNC的情況，打印顯示信令點(diǎn)不可達(dá)，請(qǐng)檢查Iu口的信令配置。3 CS域呼叫建立流程3.1 系統(tǒng)流程注：同上圖。3.2 呼叫失敗原因定位借助于CN

4、統(tǒng)一網(wǎng)管的兩大調(diào)試?yán)餍帕罡櫤蜆I(yè)務(wù)失敗觀察，可以快速、粗略的定位出呼叫失敗的原因所在（真的盼望我們的RNC早日開發(fā)出信令跟蹤和業(yè)務(wù)觀察）。但是想要定位出具體的失敗原因，可能需要參考RNC和模擬工具的前臺(tái)打印。正常情況下，一個(gè)完整的呼叫建立流程，信令跟蹤到的消息流程如下：1. MM: CM SERVICE REQUEST2. MM: CM SERVICE ACCEPT3. CC: SETUP (MOBILE STATION TO NETWORK DIRECTION)4. CC: CALL PROCEEDING5. RR: PAGING RESPONSE6. CC: SETUP (NETWORK

5、 STATION TO MOBILE DIRECTION)7. CC: CALL CONFIRMED8. CC: ALERTING (MOBILE STATION TO NETWORK DIRECTION)9. CC: ALERTING (NETWORK STATION TO MOBILE DIRECTION)10. CC: CONNECT (MOBILE STATION TO NETWORK DIRECTION)11. CC: CONNECT ACKNOWLEDGE12. CC: CONNECT (NETWORK STATION TO MOBILE DIRECTION)13. CC: CON

6、NECT ACKNOWLEDGE常見(jiàn)呼叫失敗原因分析如下：Ø 如果信令跟蹤中沒(méi)有任何消息，業(yè)務(wù)失敗觀察中也沒(méi)有任何顯示，依次排查下列流程：主叫RRC連接建立、主叫IU連接建立。如果上面兩個(gè)流程都沒(méi)有問(wèn)題，很可能是RNC側(cè)RANAP消息中參數(shù)錯(cuò)誤（如MCC、MNC配置不一致等等）。Ø 收到前4條消息，沒(méi)有收到尋呼響應(yīng)消息（RR: PAGING RESPONSE），業(yè)務(wù)失敗觀察中顯示“等待尋呼響應(yīng)超時(shí)”，依次排查下列流程：尋呼、被叫RRC連接建立、被叫IU連接建立。Ø 收到前7條消息，沒(méi)有收到振鈴（ALERTING），一般都是RAB建立失敗，業(yè)務(wù)失敗觀察中顯示“指配失

7、敗”，請(qǐng)參考RAB建立失敗章節(jié)。Ø 其他情況：出現(xiàn)的概率比較小，一般都是CN內(nèi)部交互時(shí)出了問(wèn)題（如放音失?。?，或者模擬工具側(cè)配置的號(hào)碼不正確。3.2.1 RRC連接建立3.2.1.1 RRC建立過(guò)程1. UCPM_C收到UE發(fā)來(lái)的RRC建立請(qǐng)求后（通過(guò)CCIU過(guò)來(lái)），創(chuàng)建UCIC實(shí)例，給UCIC實(shí)例發(fā)CCIU建立請(qǐng)求；2. UCIC實(shí)例收到CCIU建立的應(yīng)答后，給DPMU發(fā)UCIU建立請(qǐng)求；3. UCIC實(shí)例收到UCIU建立應(yīng)答后，給CCIU發(fā)CCIU配置請(qǐng)求；4. UCIC實(shí)例收到CCIU配置應(yīng)答后，通過(guò)CCIU給UE發(fā)送RRC CONNECTION SETUP；5. UCIC實(shí)例

8、收到UE的RRC CONNECTION SETUP COMPLETE消息；3.2.1.2 對(duì)應(yīng)的OMP打印=UCPM_C=: rcvd RRC Connect Req Msg and Create UCIC Inst 0x803d000f. =UCPM_C= : Proc rcvd EV_STARTUP!-ShowUcpmcSaveInstDataPtr- InstNo 0 Invalid-UCIC- : First TBSize of SCCPCH0 FACH0 is 171-UCIC- : First TBSize of SCCPCH0 FACH1 is 363-UCIC- : Excha

9、nge Fach Order of SCCPCH0, 0 to 0 Ucic: Inst 15 send CCIU SETUP REQ to CCI_U! （上述打印對(duì)應(yīng)于第1步） -UCIC-: Inst 15 receive one CCIU UE SETUP Resp! Ucic: Inst 15 send UCIU INST SETUP REQ To DPM-U! （上述打印對(duì)應(yīng)于第2步） -UCIC-: Inst 15 rcvd UP SETUP RESP! Ucic: Inst 15 send CCIU CONFIG REQ to CCI_U!（上述打印對(duì)應(yīng)于第3步）pu_init

10、Context_u(): ctxt_p->bDynamic = TRUE Ucic: Inst 15 rcvd CCIU CONFIG RESP! Ucic: Inst 15 send RRC CONN SETUP to UE! （上述打印對(duì)應(yīng)于第4步） OK Recived DM_GETUNITPARA Message OK! send DM_GETUNITCFG Message!pu_initContext_u(): ctxt_p->bDynamic = TRUE -UCIC-: Inst 15 rcvd RRC CONN SETUP COMP!（上述打印對(duì)應(yīng)于第5步）3.2.

11、2 IU連接建立觀察RNC前臺(tái)打印，首先確認(rèn)IUCS的信令鏈路狀態(tài)是否正常，如果鏈路狀態(tài)正常，確認(rèn)SCCP連接建立是否成功：包括是否成功發(fā)送CR（Connection Confirm）消息，接收到CC（Connection Confirm）消息。3.2.2.1 IU連接建立過(guò)程1. UCIC發(fā)送初始UE消息給SCPM，SCPM模塊創(chuàng)建SCPI實(shí)例，轉(zhuǎn)發(fā)給SCPI實(shí)例處理；2. SCPI實(shí)例給SCCP模塊發(fā)送建鏈請(qǐng)求，請(qǐng)求建立IU連接；3. SCCP的建鏈過(guò)程，發(fā)送CR請(qǐng)求給對(duì)端，對(duì)端回復(fù)CC；4. SCPI接收到SCCP的IU連接確認(rèn)，給UCIC會(huì)初始UE消息的應(yīng)答；3.2.2.2 對(duì)應(yīng)的OM

12、P打印-UCIC-: Inst 15 receive one INIT UE DIRECT TRANSFER Message From UE! Ucic: Inst 15 send one INIT UE DIRECT TRAN Msg To SCPM! tdScpm_Proc: SCPM rcvd EVENT_TD_UCPMC_SCPM_INIT_UE_MSG from UC. tdScpm_InitUEMsgHandler: SCPM create SCPI instance with InstNo 15. tdScpm_InitUEMsgHandler: SCPM send EVENT_

13、TD_UCPMC_SCPM_INIT_UE_MSG to SCPI 15. tdScpi data size: 1620 . tdScpmInst_Proc: SCPI 15 rcvd EV_STARTUP. Initilize. tdScpm_IdleStateFunc: SCPI 15 rcvd EVENT_TD_UCPMC_SCPM_INIT_UE_MSG from SCPM. tdScpm_InitUeMsgLeaf: Domain: 0.（上述打印對(duì)應(yīng)于第1步）tdScpm_SendConReqtoSccp: SCPI 15 send N_ConnectReqEvent to SCC

14、P. （上述打印對(duì)應(yīng)于第2步）SCCPSCOC receive N_ConnectReqEvent SCCP: scrc received CR_Event SCCP: scrc received MTP_TransEvent SCCPSCOC receive CC_Event （上述打印對(duì)應(yīng)于第3步）RanapCallBackFunc Receives Connection Oritented Msg from SCCP RanapCallBackFunc:the SCPMInst Number is : 15 tdScpm_SendInitUeMsgAckToUc: SCPI 15 sen

15、d EVENT_TD_SCPM_UCPMC_INIT_UE_MSG_ACK to UCI_C. Ucic: Inst 15 receive one INIT UE MSG ACK from SCPM! （上述打印對(duì)應(yīng)于第4步）3.2.3 尋呼在實(shí)際調(diào)試過(guò)程中，很少遇到尋呼不成功的情況。檢查模擬工具的打印，RRC模塊在收到尋呼請(qǐng)求后，會(huì)有如下打?。篟rc1,Idle<- EV_PCCH_PAGING_TYPE1!3.2.4 RAB建立RAB建立是呼叫過(guò)程中比較復(fù)雜的流程，涉及到的交互過(guò)程很多，也比較容易出問(wèn)題，首先我們看一下RAB建立的主要過(guò)程，了解交互流程。3.2.4.1 IUUP建立過(guò)

16、程 3.2.4.1.1 IUUP建立過(guò)程大致如下：1. SCPI實(shí)例收到CN發(fā)來(lái)的RAB指派消息，給RPM發(fā)送RAB指派消息；2. RPM創(chuàng)建RPI實(shí)例，由RPI實(shí)例處理該消息；3. RPI實(shí)例給UCI_U發(fā)送IuUP建立請(qǐng)求（發(fā)給PMU模塊）；4. RPI實(shí)例接收到IuUP建立的應(yīng)答；5. RPI實(shí)例請(qǐng)求Alcap建立IU口承載通道，要求建立AAL2鏈路；6. Alcap建立AAL2鏈路過(guò)程，發(fā)送ERQ請(qǐng)求給對(duì)端，對(duì)端響應(yīng)ECF，成功后通知RPI；7. RPI收到AAL2鏈路建立確認(rèn)，配置IuUP；8. 收到IuUP配置應(yīng)答后，通知SCPI，Iu通道建立完畢；9. SCPI請(qǐng)求UCI_C建立

17、RAB，開始RL建立過(guò)程；3.2.4.1.2 對(duì)應(yīng)的OMP打印分析SCPI 19 rcvd RAB assignment req in SERVING. SCPI 19 send setup to RPM(RABId = 1).（上述打印對(duì)應(yīng)于第1步）tdRpm_Proc: Rpm Create InstProc Success! Rpi data size: 3437 . RPI 11: Rcvd EVENT_SCPM_RPM_RAB_SETUP Msg! Cn Domain: 0（上述打印對(duì)應(yīng)于第2步） RPI 11: IUUP MODE VERSION: 0, 1!tdRpm_SendI

18、uupSetupToUp: RPI 11: send IuUPMsg to Iuup successfully! RPI 11: Sent IuUP Setup REQ to UCI_U 4114!（上述打印對(duì)應(yīng)于第3步）RPI 11: Rcvd IuUP SETUP Rsp Msg!（上述打印對(duì)應(yīng)于第4步）RpmSendIuBearSetupToAlcap: SGUR: 16777407 InnerIP: 2139660676 Port: 33 0 18 0 RPI 11: Sent A2SU EST REQ to A2SP!（上述打印對(duì)應(yīng)于第5步）AAL2SP: Get establish

19、 request!Get ANI from dbs with ATM address!It's successful to check atm address!pZDB_AtmRsMgt received EV_ALLOCATECEIDLOCAL_REQ msg!AAL2SP:DBS success to allocate CEID!AAL2SP: To allocate SAID 39! AAL2ND: Starting T_VTC Timer!AAL2SPND:Get VTC correctly!AAL2SPND:STOP VTC timer!AAL2SPDBFUN:Ask dbs

20、 to establish a link on bearer!AAL2SPDBFUN:Starting T_UCREQ Timer!AAL2SP:APBE answers that it's successful to establish a link!AAL2SPND:APBE success to establish a link!AAL2SPND:STOP T_UCREQ timer!AAL2ET: start T_ERQ Timer !AAL2SPMESSAGE: Send ERQ message!AAL2SPMESSAGE: send this message to stcm

21、ain!AAL2SPND:Send establish req to peer!AAL2SPMESSAGE: Receive ECF message!STOP T_ERQ Timer!AAL2ND: Starting T_DEADLOCK Timer!AAL2SP: Send establish confirm to user!（上述打印對(duì)應(yīng)于第6步）RPI 11: Rcvd EV_A2SP_A2SU_ESTABLISH_CON Msg!tdRpm_SendIuupSetupToUp: RPI 11: send IuUPMsg to Iuup successfully! RPI 11: Sen

22、t Iuup Config Req to UCI_U 4114!（上述打印對(duì)應(yīng)于第7步）RPI 11: Rcvd EV_RPM_IUUP_CONFIG_RSP Msg!RPI 11: Sent Setup Cmp to SCPI 19!（上述打印對(duì)應(yīng)于第8步）SCPI 19 rcvd RPI 11 Setup cmp(RABId = 1).SCPI 19 send Rab Setup Assign To UCI_C 19.（上述打印對(duì)應(yīng)于第9步）3.2.4.2 RL建立過(guò)程3.2.4.2.1 RL建立過(guò)程大致如下：1. UCI_C收到SCPI實(shí)例發(fā)送的RAB建立消息，給RLMM發(fā)送RL建立請(qǐng)求

23、；2. RLMM（TdRlmm_ManagerProc）創(chuàng)建RLMI（TdRlmm_WorkerProc）實(shí)例，由RLMI實(shí)例處理該消息；3. RLMI實(shí)例給RRM發(fā)送CAC（Call Admission Control）請(qǐng)求，收到接納控制的正確應(yīng)答；4. RLMI實(shí)例給Nodeb側(cè)RLMM模塊發(fā)送RL建立請(qǐng)求，收到Nodeb側(cè)RLMM模塊的RL建立應(yīng)答；5. RLMI實(shí)例通過(guò)PMU模塊建FP 實(shí)例；6. FP實(shí)例建立成功后，RLMI實(shí)例請(qǐng)求Alcap建立AAL2鏈路；7. Alcap建立AAL2鏈路過(guò)程，發(fā)送ERQ請(qǐng)求給對(duì)端，對(duì)端響應(yīng)ECF，成功后通知RLMI；8. RLMI收到AAL2鏈路

24、建立確認(rèn)，配置FP；9. 收到FP配置應(yīng)答后，通知UCI_C，UCI_C開始RAB建立過(guò)程；3.2.4.2.2 對(duì)應(yīng)的OMP打印分析UCIC <- Inst 19 rcvd Rab Setup Req!<-UCIC-> : Inst 19 Ucpmc send Rl SETUP Msg to Rlmm!（上述打印對(duì)應(yīng)于第1步）TdRlmm_ManagerProc Received "EVENT_TD_UCPMC_RLMM_RL_SETUP_REQ" which sended by TD_RNLC_UCPMC_InstFsm :RLMM:TdRlmm_Man

25、agerProc Create Rlmi Instance 1 TdRlmm_ManagerProc Send "EV_RLMM_RLMI_RL_SETUP_REQ" to TdRlmm_WorkerProc TdRlmm_WorkerProc Received "EV_RLMM_RLMI_RL_SETUP_REQ" which sended by TdRlmm_ManagerProc（上述打印對(duì)應(yīng)于第2步）TdRlmm_WorkerProc Send "EVETN_TD_RLMM_RRM_CAC_REQ" to RRMMP_ENTR

26、Y RRM: MainProc Recv MSG EVETN_TD_RLMM_RRM_CAC_REQ RRM : CACM: CacmAdmissionRequest: CAC Request(RLMI Inst = 1) Admitted!TdRlmm_WorkerProc Received "EVENT_TD_RRM_RLMM_CAC_ACK" which sended by RRMMP_ENTRY（上述打印對(duì)應(yīng)于第3步）TdRlmm_WorkerProc Send "EVENT_TD_RLMM_NBLOMM_MSG_TO_NB_IND" to Rn

27、lcNblommNbmTdRlmm_ManagerProc Received "EVENT_TD_NBLOMM_RLMM_MSG_FROM_NB_IND" which sended by RnlcNblommNbWorkerTdRlmm_ManagerProc Send "EVENT_TD_NBLOMM_RLMM_MSG_FROM_NB_IND" to TdRlmm_WorkerProc TdRlmm_WorkerProc Received "EV_RLMM_RLMI_RL_SETUP_RESPONSE" which sended b

28、y TdRlmm_ManagerProc（上述打印對(duì)應(yīng)于第4步）TdRlmm_WorkerProc Send "EVENT_TD_RLMM_DPMU_MSG" to RnluHPmuProcEntry TdRlmm_WorkerProc Received "EV_RLMM_RLMI_SRNC_FP_SETUP_RESPONSE" which sended by RnluHPmuProcEntry（上述打印對(duì)應(yīng)于第5步）TdRlmm_WorkerProc Send "aal2EstablishReqEvent" to P_AAL2SP（

29、上述打印對(duì)應(yīng)于第6步）AAL2SP: Get establish request!Get ANI from dbs with ATM address!It's successful to check atm address!pZDB_AtmRsMgt received EV_ALLOCATECEIDLOCAL_REQ msg!AAL2SP:DBS success to allocate CEID! AAL2SP: To allocate SAID 43! AAL2ND: Starting T_VTC Timer!AAL2SPND:Get VTC correctly!AAL2SPND:S

30、TOP VTC timer!AAL2SPDBFUN:Ask dbs to establish a link on bearer!AAL2SPDBFUN:Starting T_UCREQ Timer!AAL2SP:APBE answers that it's successful to establish a link! AAL2SPND:APBE success to establish a link! AAL2SPND:STOP T_UCREQ timer! AAL2ET: start T_ERQ Timer ! AAL2SPMESSAGE: Send ERQ message! AA

31、L2SPMESSAGE: send this message to stcmain! AAL2SPND:Send establish req to peer! STC: Send link establishment request!STCMAIN: Received data indication from SSCF AAL2STC: Send Transfer Msg to SP to Inform it decode this Msg! AAL2SPMESSAGE: Receive ECF message! STOP T_ERQ Timer! AAL2ND: Starting T_DEA

32、DLOCK Timer! AAL2SP: Send establish confirm to user!（上述打印對(duì)應(yīng)于第7步）TdRlmm_WorkerProc Received "aal2EstablishCfmEvent" which sended by P_AAL2SPTdRlmm_WorkerProc Send "EVENT_TD_RLMM_DPMU_MSG" to RnluHPmuProcEntry TdRlmm_WorkerProc Received "EV_RLMM_RLMI_SRNC_FP_INIT_RESPONSE" which sended by RnluHPmuProcEntry （上述打印對(duì)應(yīng)于第8步）TdRlmm_WorkerProc Send "EVENT_TD_RLMM_UCPMC_RL_SETUP_RESP" to TD_RNLC_UCPMC_InstFsm -> UCIC <- Inst 18 rcvd RL SETUP RESP from RLMI In RabSetup Status!<- UCIC -> Inst