SJ-20120828144226-019-ZXC10 BSSB Failure Reason Reference(1X)_450877

ZXC10 BSSBCDMA2000 Base Station SystemFailure Cause Reference(1X)

Version: V8.0.5.100

ZTE CORPORATIONNO. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: +86-755-26771900Fax: +86-755-26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATIONCopyright © 2012 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or

distribution of this document or any portion of this document, in any form by any means, without the prior written

consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by

contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE

CORPORATION or of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions

are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,

title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the

use of or reliance on the information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications

covering the subject matter of this document. Except as expressly provided in any written license between ZTE

CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter

herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 2012-10-20 First Edition

Serial Number: SJ-20120828144226-019

Publishing Date: 2012-10-20 (R1.0)

SJ-20120828144226-019|2012-10-20 (R1.0) ZTE Proprietary and Confidential

ContentsAbout This Manual ......................................................................................... I

Chapter 1 Call Failure Causes................................................................... 1-11.1 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unspecified ..................... 1-1

1.2 ERR_SPS_RLSA_BSSAP_TE_T3230................................................................. 1-2

1.3 ERR_SPS_RLSA_BSSAP_TE_Tassignment ....................................................... 1-2

1.4 ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect .................................. 1-3

1.5 ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSReleaseOrder................................. 1-4

1.6 ERR_SPS_RLSA_BSSAP_TE_Tfchsetup ........................................................... 1-4

1.7 ERR_SPS_RLSA_BSSAP_TE_T303 .................................................................. 1-5

1.8 ERR_SPS_RLSA_BSSAP_TE_Txxp................................................................... 1-6

1.9 ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddrByLogicAddr ................ 1-7

1.10 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_CallProcessing............... 1-7

1.11 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_UserBusy....................... 1-8

1.12 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NormalClearing.............. 1-9

1.13 ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed ........................................... 1-9

1.14 ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail.............................................. 1-10

1.15 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NoAnswer.....................1-11

1.16 ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit .....................................1-11

1.17 ERR_SPS_RLSA_BSSAP_FchSetup_SendChannelAssignment_AllBtsFail ....... 1-12

1.18 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_HandoffSuccessful ....... 1-13

1.19 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_SemiConcurrentService .................................................................................................................. 1-14

1.20 ERR_SPS_RLSA_BSSAP_MsgPara_Origination_InvalidServiceOption............. 1-14

1.21 ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_SccpId2CallRef ........................ 1-15

1.22 ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail ................................. 1-15

1.23 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_EquipmentFailure ......... 1-16

1.24 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_AuthenticationFailure.................................................................................................................... 1-16

1.25 ERR_SPS_RLSA_BSSAP_FchSetup_AllLegAreRemoved ............................... 1-17

1.26 ERR_SPS_RLSA_BSSAP_Other_SpcfSelectTableBad .................................... 1-17

1.27 ERR_SPS_RLSA_BSSAP_Other_RTDOutofRange ......................................... 1-18

1.28 ERR_SPS_RLSA_BSSAP_MultiSP_InvalidMSCOfficeId .................................. 1-19

1.29 ERR_SPS_RLSA_BSSAP_MultiSP_MSCOfficeUnavailable ............................. 1-19

1.30 ERR_SPS_RLSA_BSSAP_MultiSP_A1fAssignReq_InvalidMSCOfficeId ........... 1-20

I


1.31 ERR_SPS_RLSA_BSSAP_MsgPara_MSRejectOrder ...................................... 1-20

1.32 ERR_SPS_RLSA_BSSAP_Other_Encode_A1MsgInBSC................................. 1-21

1.33 ERR_SPS_RLSA_BSSAP_Other_Encode_UmpMsgInBSC .............................. 1-21

1.34 ERR_SPS_RLSA_BSSAP_Other_Decode_UmpMsgInBSC.............................. 1-21

1.35 ERR_SPS_RLSA_BSSAP_TE_Ta1_4 ............................................................. 1-22

1.36 ERR_SPS_RLSA_BSSAP_PoorPilot............................................................... 1-22

1.37 ERR_SPS_RLSA_BSSAP_FchSetup_SendPCHMsg_AllBtsFail ....................... 1-22

1.38 ERR_SPS_RLSA_BSSAP_DB_GetLinkInfo..................................................... 1-23

1.39 ERR_SPS_RLSA_BSSAP_DB_GetValidCarrier ............................................... 1-23

1.40 ERR_SPS_RLSA_BSSAP_DB_GetOPBySysIdCellIdCrId................................. 1-23

1.41 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Twaitorder ................................ 1-23

1.42 ERR_SPS_RLSA_BSSAP_Other_DifferenceInFwdOrRevRC ........................... 1-24

1.43 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNFailure................................. 1-25

1.44 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tpcfinfol3 ................................. 1-25

1.45 ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq ........................... 1-26

1.46 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_Unspecified.............................................................................................................. 1-27

1.47 ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8setup.................................. 1-27

1.48 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_Administratively_Pohibited......................................................................................... 1-28

1.49 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_PDSN_Resource_Unavailable .................................................................................................. 1-29

1.50 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHRequestMsg_FCHNotExisted ......................................................................................... 1-29

1.51 ERR_SPS_RLSA_DSPM_SCHH_ResNotSatisfied_SCHHOnFwdAllBurstResponse_NoCommitedCell ................................................................................. 1-30

1.52 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAcrBSCAddChannelItemAck_AddChannelItemFailed ................................................................... 1-31

1.53 SDM_Activate_Fail_AcquirePreambleFail_Normal............................................ 1-32

1.54 SDM_Activate_Fail_AcquirePreambleFail_NoRevFrm ...................................... 1-32

1.55 SDM_Find_Fail_WaitConfigVTCTimeout ......................................................... 1-33

1.56 SDM_Find_Fail_WaitConfigRLPTimeout.......................................................... 1-34

1.57 SDM_Link_Fail_RSCHLegLinkFail .................................................................. 1-34

1.58 SDM_Activate_Fail_InitVocoderFail ................................................................. 1-35

1.59 SDM_OprVocoder_Fail_WaitStartVocoderCodingAckTimeOut .......................... 1-35

1.60 SDM_Activate_Fail_MsgParaFail .................................................................... 1-36

1.61 DBS_STASTIC_FWDFCHCE_REVCE_LACK.................................................. 1-36

1.62 DBS_STASTIC_FWDFCHCE_LACK ............................................................... 1-37

II


1.63 DBS_STAT_WALSHCODE_LACK .................................................................. 1-37

1.64 DBS_STAT_UID_LACK.................................................................................. 1-38

1.65 DBS_STAT_NO_RESOURCE_LACK.............................................................. 1-38

1.66 FCH_NUMBER_TWO .................................................................................... 1-39

1.67 ARRIVE_TIME_ERROR ................................................................................. 1-39

1.68 NO_SYSTEM_TIME....................................................................................... 1-40

1.69 NO_AVAILABLE_REV_CE ............................................................................. 1-40

1.70 FO_NOT_ENOUGH ....................................................................................... 1-41

1.71 CE_NOT_ENOUGH ....................................................................................... 1-41

1.72 WALSHCODE_NOT_ENOUGH ...................................................................... 1-41

1.73 BEFORE_CPS............................................................................................... 1-42

1.74 UIDWIDTH_NOT_ENOUGH ........................................................................... 1-42

1.75 RS_NOT_EXIST ............................................................................................ 1-43

1.76 ALLOCATE_UID_ERROR .............................................................................. 1-43

1.77 BSC_CICFROMMSC_ERR............................................................................. 1-44

1.78 HO_STAT_SERVICE_FORBID........................................................................ 1-44

1.79 ERR_SPS_RLSA_RCM_DBAccFail_FCHResourceAllocate ............................. 1-44

1.80 ERR_SPS_RLSA_RCM_PCALL_OtherReason_CEC_REMOVEREQ ............... 1-45

1.81 ERR_SPS_RLSA_RCM_FCH_TimerExpired_TconnExpired ............................. 1-46

1.82 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_AddChannelFail........................... 1-47

1.83 ERR_SPS_RLSA_RCM_FSCH_TimerExpired_TfschNotifyExpired ................... 1-47

1.84 ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_SameTimeCellInSameGroupInDiffSetupFlow............................................................... 1-48

1.85 ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_MAbisdMsgDispatch.................................................................................................................... 1-48

1.86 ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_ServiceRestrict .......................................................................................................... 1-49

1.87 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_BurstRequest_ConnInSetup......... 1-50

1.88 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstRequest_SaveToGroupedCellInfoSet_CellNumIsZero ............................................................................. 1-50

1.89 ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft_AbisdfBurstCommit ........................................................................................... 1-51

1.90 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_AddChannelFail .......................... 1-51

1.91 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_GetConnRecordByGroupId........................................................................................................ 1-52

1.92 BSC_NO_CIC ................................................................................................ 1-52

1.93 POWER_NOT_ENOUGH ............................................................................... 1-53

1.94 BSC_NO_SE ................................................................................................. 1-54

III


1.95 BSC_NO_VE ................................................................................................. 1-54

1.96 BSC_NO_IWF................................................................................................ 1-55

1.97 BSC_DSPM_NO_INSTANCE ......................................................................... 1-55

1.98 BSC_NO_RTPPORT...................................................................................... 1-56

1.99 BSC_NO_VALID_RMP................................................................................... 1-57

1.100 ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MCSHConstructAmdfFCHSetup ............................................................................. 1-57

1.101 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_MHandlerAbisdfBTSSetup...................................................................................... 1-58

1.102 ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAck_SoftHandoffLegNoInvalid............................................................................... 1-59

1.103 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_MCDHSaveToCommonData .............................................................................. 1-59

1.104 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CE_IN_USED................. 1-60

1.105 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_REJECT ...... 1-61

1.106 ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_CREATE_PROCESS....... 1-62

1.107 ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_OUTPUT_MSG_TO_CALLHNDL......................................................................................................... 1-62

1.108 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_RSP_TIMER_OUT .......................................................................................................... 1-63

1.109 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_POINTER_NULL.................................................................................................................. 1-64

1.110 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_HANDOFF_TYPE............................................................................................................... 1-64

1.111 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_NUM................................................................................................................... 1-65

1.112 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_FWD_RC.......... 1-66

1.113 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_RC .......... 1-66

1.114 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_ID ................................................................................................................... 1-67

1.115 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_ISNOT_ACTIVE................................................................................................... 1-68

1.116 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_EARLIESTPNOFFSET ........................................................................................................ 1-69

1.117 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_WALSH_INDEX ................................................................................................................... 1-69

1.118 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CE_INDEX ....... 1-70

1.119 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FRAME_OFFSET ............................................................................................................... 1-71

IV


1.120 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CHANNEL_POWER ........................................................................................................... 1-71

1.121 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_FCH_GATING ........................................................................................................... 1-72

1.122 ERR_CES_RLSA_CEC_CALLHNDL_DCCH_SETUP_PARAM_REV_PILOT_GATING....................................................................................................... 1-73

1.123 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_PUNC_MODE ........................................................................................................... 1-74

1.124 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_GAIN ....... 1-74

1.125 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_STEP_SIZE ................................................................................................................ 1-75

1.126 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_RPC_PUNC_MODE ........................................................................................................... 1-76

1.127 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC_SETPOINT ........................................................................................................... 1-77

1.128 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC_PATTERN ............................................................................................................ 1-77

1.129 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_TRAFFIC_FRAME_TYPE.................................................................................................... 1-78

1.130 CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DEST_IP_ADRR_INVALID .................................................................................................................. 1-79

1.131 CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DSCP_PRIIS_INVALID ................................................................................................................... 1-80

1.132 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_CEMCTRL_NULL ........... 1-80

1.133 ERR_SPS_RLSA_BSSAP_SccpDisconnect_Connectref_Incompat_Inf_In_NSDUs............................................................................................................. 1-81

1.134 ERR_SPS_RLSA_BSSAP_SccpDisconnect_End_User_Failure...................... 1-81

1.135 ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail_FCHAndDCCH_AbisdrConnectProccess_AbisdrConnectMsgProccess...................................................... 1-82

1.136 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_CheckIfCellFitToSetup_HOReqCellIsExisted..................................................................................................... 1-82

1.137 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_ReqReleaseingCellIsNotExisted.................................................................................................................... 1-82

1.138 ERR_SPS_RLSA_BSSAP_PTTSetup_ServiceNotify_UserInHigherPriorityService .............................................................................................................. 1-83

1.139 ERR_SPS_RLSA_BSSAP_PTTSetup_A9dfPTTPage_UserInHigherPriority.................................................................................................................... 1-83

Chapter 2 Call Drop Causes ...................................................................... 2-12.1 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInSessionState .......................... 2-1

2.2 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInSessionState_Others ............... 2-1

V


2.3 ERR_SPS_RLSA_BSSAP_HandShake_TimeOut ................................................ 2-2

2.4 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerOn ............. 2-2

2.5 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerDown ......... 2-3

2.6 ERR_SPS_RLSA_BSSAP_UnexptMsg_UmaRegistration..................................... 2-3

2.7 ERR_SPS_RLSA_DSPM_HOH_OtherReason_AbisdHandShakeFailure............... 2-4

2.8 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFEquipmentFailure................... 2-4

2.9 ERR_SPS_RLSA_DSPM_CLH_OtherReason_Thandshakerecv........................... 2-5

2.10 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleaseRSCHbyLegFail_ReleaseRschExistSDMLegFailure ................................................................ 2-6

2.11 SDM_Link_Fail_RevNoFrm............................................................................... 2-6

2.12 SDM_Link_Fail_RevTooManyBadFrm ............................................................... 2-7

2.13 SDM_Link_Fail_FwdA2pNoFrm ........................................................................ 2-7

2.14 SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm ............................................... 2-8

2.15 ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_GetCallProc ................ 2-9

2.16 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInHardHOAdd.......................... 2-9

2.17 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvPageRspInHardHOAdd ................... 2-9

Chapter 3 Call Release Causes................................................................. 3-13.1 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSNormalRelease........................ 3-1

3.2 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSPowerDown............................. 3-1

3.3 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHRequestMsg_ReleasebyMSDTXTime................................................................................. 3-2

3.4 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemoveIndication_RSCHReleasebySDMOtherReason...................................................... 3-2

3.5 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHPNDropIndication_ReleasebyHOH ....................................................................................................... 3-3

3.6 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRelease_RSCHExistedCellReleasebyRCM .................................................................... 3-3

3.7 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHRelease_ReleasebyCLH ..................................................................................................................... 3-4

3.8 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemoveIndication_RSCHReleasebySDMOtherReason...................................................... 3-4

3.9 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemoveIndication_FSCHReleasebySDMDuration ............................................................. 3-5

3.10 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHFSCHHandoff_HardHandoff .............................................................................................................. 3-5

3.11 ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschdrop ................................ 3-6

3.12 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnTfschdroppending_ReleasebyTDropPending .................................................................................. 3-6

VI


3.13 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRelease_FSCHExistedCellReleasebyRCM................................................................... 3-7

3.14 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSGoingIntoDormant ................. 3-7

3.15 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFNormalRelease .................... 3-7

3.16 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMLinkFailure_toDormant ........ 3-8

3.17 ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnA7rTarRemReq_CLHRlsInd ................................................................................................................. 3-9

3.18 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease_FSCHExistedCellReleasebyRCM .................................................................... 3-10

3.19 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease_RSCHExistedCellReleasebyRCM.................................................................... 3-10

3.20 SDM_Find_Fail_NoFCHLeg.............................................................................3-11

3.21 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_RSCH ........................3-11

3.22 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_FSCH........................ 3-12

3.23 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tsch................................ 3-12

3.24 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tbstcomb ........................ 3-12

3.25 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_RevSCHSetupFail ....................... 3-13

3.26 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_FwdSCHSetupFail ....................... 3-14

3.27 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_STATUS_RemovedSCH........................................................................................................... 3-15

3.28 ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_CellNotFoundInRevSCHResourceExtension ................................................................................................ 3-15

3.29 ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tconfigtch .............................. 3-16

3.30 ERR_SPS_RLSA_RCM_FSCH_OtherReason_EndOfDuration ......................... 3-16

Chapter 4 Handoff Failure Causes............................................................ 4-14.1 ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail_TargetBSCHandlerEntry_A7

HOReqMsgProccessForHOWith1X.................................................................... 4-1

4.2 ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit ........................................ 4-1

4.3 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_TargetBSCHandler_A7fHandoffRequestProccess_RecievedA7HOReqWhenSemiHO ............................................. 4-2

4.4 ERR_SPS_RLSA_BSSAP_Other_SBSSRFailure................................................. 4-3

4.5 ERR_SPS_RLSA_BSSAP_DB_GetPeerCellDiscriminator .................................... 4-3

4.6 ERR_SPS_RLSA_BSSAP_UnexptMsg_TSendAssignmentMsgNotInValidState...................................................................................................................... 4-3

4.7 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvSBSSAckNotInSetupState................. 4-4

4.8 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvSBSSAck_bTbssapRlcReqOut .......... 4-4

4.9 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvAvrHORequiredSBSSRInV5System..................................................................................................................... 4-4

VII


4.10 ERR_SPS_RLSA_BSSAP_UnexptMsg_TargetRemovalReqInSBSSRCallSetup...................................................................................................................... 4-5

4.11 ERR_SPS_RLSA_BSSAP_UnexptMsg_TbssapRlcReqNotInSetupState.............. 4-5

4.12 ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRRequestAck_atCellInfoIsInvalid...... 4-5

4.13 ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRRequestAck_ServiceTypeIsNotMatched........................................................................................................... 4-6

4.14 ERR_SPS_RLSA_BSSAP_TE_TbssapRlcReq .................................................. 4-6

4.15 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7HandoffRequestReceived...................................................................................................................... 4-6

4.16 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7DropTargetReceived ........... 4-7

4.17 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A3DropReceived..................... 4-7

4.18 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_TwaitRlcExpired ...................... 4-7

4.19 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_TwaitDrpTgtExpired................. 4-8

4.20 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSoftHOAdd.................................................................................................................... 4-8

4.21 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSoftHODrop.................................................................................................................... 4-8

4.22 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSemiHOAdd.................................................................................................................... 4-9

4.23 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSCHExist....................................................................................................................... 4-9

4.24 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_WrongChannelItemState.......... 4-9

4.25 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_UnexpectedRlcState.............. 4-10

4.26 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_OAMIntervention ........ 4-10

4.27 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_EquipmentFailure ....... 4-10

4.28 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_NoRadioResourceAvailable.............................................................................................................4-11

4.29 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_RTRUnavailable ..........4-11

4.30 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_BSNotEquipped...........4-11

4.31 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_HandoffBlocked...........4-11

4.32 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_RTAUnavailable ......... 4-12

4.33 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_TimeOut..................... 4-12

4.34 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_Unspecified ................ 4-12

4.35 SOFTADD_CELL_ERROR ............................................................................. 4-13

4.36 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SoftHOThocompletion .............. 4-13

4.37 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq .................................... 4-14

4.38 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnUmrCFSearchReport.................................................................................................................. 4-15

4.39 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SemiSoftHOThocompletion ...... 4-16

VIII


4.40 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnA7rHOReqAck ......... 4-16

4.41 ERR_SPS_RLSA_DSPM_HOH_ResourceAllocFail_GetHandoffProc ................ 4-17

4.42 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMSetISLPFailure.................. 4-19

4.43 ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnDBSHOProcACK_PNSConstructFrmDBS .......................................................................................... 4-20

4.44 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thocompletion ......................... 4-20

4.45 HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO............................................. 4-21

4.46 HO_STAT_PILOT_NOT_LOCALBSS .............................................................. 4-21

4.47 HO_Func_GetTargetFromPreCell_ERR........................................................... 4-22

4.48 SOME_CELL_FAIL......................................................................................... 4-22

4.49 CELL_IS_ERROR .......................................................................................... 4-22

4.50 HO_STAT_PILOT_LIMITED............................................................................ 4-23

4.51 ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_SpecifiedCellIsReleasing........................................................................................... 4-23

4.52 ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft_AbisdfBurstRequest .......................................................................................... 4-24

4.53 HO_STAT_PILOT_IS_OTHER_UNLNKBSS .................................................... 4-24

4.54 HO_STAT_PILOT_NO_SAME_FREQ ............................................................. 4-25

4.55 HO_STAT_CARRIER_PWR_OVERLOAD ....................................................... 4-25

4.56 HO_STAT_CARRIER_STATE_MBLOCK ......................................................... 4-26

4.57 HO_STAT_CARRIER_STATE_RFE_BROKEN ................................................ 4-26

4.58 HO_STAT_CARRIER_STATE_RFE_LOWPOWER.......................................... 4-26

4.59 HO_STAT_CARRIER_STATE_BDS_DISCONNECT........................................ 4-27

4.60 HO_STAT_CARRIER_STATE_RFE_POWERDOWN....................................... 4-27

4.61 HO_STAT_CARRIER_RESOURCE_RESERVED ............................................ 4-27

4.62 HO_STAT_CARRIER_LIMITED ...................................................................... 4-28

4.63 HO_STAT_CARRIER_NO_CE........................................................................ 4-28

4.64 HO_STAT_CARRIER_NO_5KCE.................................................................... 4-29

4.65 HO_STAT_PILOT_IS_NOT_NEIGHBOR......................................................... 4-29

4.66 BSC_NO_SE ................................................................................................. 4-30

4.67 BSC_NO_VE ................................................................................................. 4-30

4.68 BSC_NO_IWF................................................................................................ 4-31

4.69 BSC_DSPM_NO_INSTANCE ......................................................................... 4-31

4.70 BSC_NO_RTPPORT...................................................................................... 4-32

4.71 BSC_NO_VALID_RMP................................................................................... 4-33

4.72 HO_STAT_CARRIER_NO_CE_LICENSE........................................................ 4-33

4.73 HO_NoPilotAvailable_ERR ............................................................................. 4-34

IX


4.74 ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MCSHConstructAmdfFCHSetup ............................................................................. 4-34

4.75 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_MHandlerAbisdfBTSSetup ....................................................................................... 4-35

4.76 ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAck_SoftHandoffLegNoInvalid ................................................................................ 4-36

4.77 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_MCDHSaveToCommonData................................................................................. 4-36

4.78 ERR_CES_RLSA_CEC_CALLHANDLER_V_ChannelType_Error ..................... 4-37

Chapter 5 Registration Failure Causes .................................................... 5-15.1 ERR_SPS_RLSA_BSSAP_Reg_Reject_Congestion ............................................ 5-1

5.2 ERR_SPS_RLSA_BSSAP_Reg_Reject_IllegalMs................................................ 5-1

5.3 ERR_SPS_RLSA_BSSAP_Reg_Reject_NetworkFailure....................................... 5-2

5.4 ERR_SPS_RLSA_BSSAP_Reg_Reject_RoamingNotAllowed............................... 5-2

5.5 ERR_SPS_RLSA_BSSAP_Reg_Reject_Other..................................................... 5-3

5.6 ERR_SPS_RLSA_BSSAP_SccpDisconnect_Release_In_Progress ...................... 5-3

5.7 ERR_SPS_RLSA_BSSAP_Reg_Reject_MinImsiUnknown.................................... 5-4

Chapter 6 Other Failure Causes................................................................ 6-16.1 ERR_SPS_RLSA_BSSAP_DiscardMsg_SmsNumOvld ........................................ 6-1

6.2 ERR_SPS_RLSA_BSSAP_MsgPara_A1fPACAUpdate_SBSSRInvalidProcess ..... 6-1

6.3 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7BurstRequestReceived.......... 6-1

6.4 ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVERLOAD................................. 6-2

6.5 INPUT_PARA_ERROR ...................................................................................... 6-2

Glossary .......................................................................................................... I

X


About This ManualPurposeThis manual provides information about the ZXC10 BSSB failure cause reference for the1X service.

Intended AudienceThis manual is intended for:

l Network management engineersl Maintenance engineers

Prerequisite Skill and KnowledgeTo use this document effectively, users should have a general understanding of wirelesstelecommunications technologies. Familiarity with the following is helpful:

l ZXC10 BSSB Base Station Systeml CDMA signaling flow

What Is in This ManualThis manual contains the following chapters:

Chapter Summary

Chapter 1, Call Failure

Causes

Describes the causes of call failures and the handling measures.

Chapter 2, Call Drop

CausesDescribes the causes of call drop failures and the handling measures.

Chapter 3, Call Release

CausesDescribes the causes of call release failures and the handling measures.

Chapter 4, Handoff

Failure CausesDescribes the causes of handoff failures and the handling measures.

Chapter 5, Registration

Failure CausesDescribes the causes of registration failures and the handling measures.

Chapter 6, Other Failure

CausesDescribes the causes of other failures and the handling measures.

Related DocumentationThe following documentation is related to this manual:

l ZXC10 BSSB (V8.0.3.500) CDMA2000 Base Station System Failure CauseReference(DO)

I


l ZXC10 BSSB (V8.0.3.500) CDMA2000 Base Station System Failure CauseReference(PTT)

II


Chapter 1Call Failure Causes

1.1 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unspecified

Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unspecified

Failure Cause During call setup, the MSC sends a ClearCommand message to release the

call. The cause is unknown.

Failure Analysis l A non-standard cause value in A-interface protocol is carried in the

Cause of ClearCommand.

l The cause carried in ClearCommand is Cause_A_CallProcessing. The

cause value carried in Layer 3 is 0x1f. This cause value corresponds to

the BSC internal cause value (ERR_SPS_RLSA_BSSAP_FchSetup_Cl

earCommand_Unspecified). This failure may be caused by an error on

the MSC, such as timer timeout, and access failure.

Possible Solution It is acceptable if the problem occurs occasionally. If the problem occurs

frequently, check the fault probe and take measures after identifying the

cause.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unspecified

失失失败败败原原原因因因值值值含含含义义义呼叫建立时，MSC发送ClearCommand消息释放呼叫，原因未知。

失失失败败败原原原因因因分分分析析析会导致这个失败的原因如下：l ClearCommand中的Cause带了A口协议中非标准的原因值。l ClearCommand中带的Cause是Cause_A_CallProcessing，但是在

Layer3中带的原因值是0x1f，这种情况下，转化成BSC内部的原因值，就是ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unsp

ecified。这种情况常发生在交换这边，例如定时器超时，接入失败等都是由这个原因引起的。

解解解决决决措措措施施施少量出现属正常现象，大量出现需分析异常探针，待确定失败原因后再进行相应处理。

1-1


ZXC10 BSSB Failure Cause Reference(1X)

1.2 ERR_SPS_RLSA_BSSAP_TE_T3230Failure Name ERR_SPS_RLSA_BSSAP_TE_T3230

Failure Analysis During call setup, the BSSAP sends a CMServiceRequest or

PagingResponse message to the MSC but fails to receive a returned

SccpConnect message before T3230 expires.

Possible Solution 1. Verify that No.7 signaling links are stable.

2. If the failure is caused by heavy traffic, add more signaling links.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_TE_T3230

失失失败败败原原原因因因分分分析析析呼叫建立时，BSSAP向MSC发送CMServiceRequest或PagingResponse消息后，没有收到对端的SccpConnect连接证实消息，导致T3230超时。

解解解决决决措措措施施施 1. 检查7号信令链路是否正常，可能是链路不稳定。2. 当前业务量太大，超过当前信令链路所能承载的业务量，需要增

加信令链路。

1.3 ERR_SPS_RLSA_BSSAP_TE_TassignmentFailure Name ERR_SPS_RLSA_BSSAP_TE_Tassignment

Failure Analysis When a mobile station originates a call or is called, the BSSAP sends an

EV_S_AvfServiceAssignment message to the Data Service Management

Platform (DSMP), but fails to receive an EV_S_AvrAssignmentComplete

message or EV_S_AvrAssignmentFailure message from the DSMP before

timer Tassignment expires.

The possible failure causes are as follows:

1. Timer Tassignment expires too early.

2. The DSMP is configured with too many instances (more than the

number of DSMP instances that can be supported).

3. DSMP CPU utilization is too high.

4. SDM activation expires.

Handling Measure 1. Verify that the setting of timer Tassignment on CMP is correct. The

default value is 6000 (6 seconds).

2. Verify that the number of DSMP instances in the association between

RMP and DSMP is within the allowed range. Different DSMP versions

support different numbers of instances.

3. If DSMP CPU utilization is too high, add more DSMP modules.

4. If SDM activation expires, the media stream between SDU and CHM

may be different, or the clock between BSC and BTS is different. Verify

that the optical fiber connections at media plane and the SDU daughter

cards are correct.

1-2


Chapter 1 Call Failure Causes

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_TE_Tassignment

失失失败败败原原原因因因分分分析析析手机作起呼或者被呼时，BSSAP向DSMP发送EV_S_AvfServiceAssignment

指配请求消息后，长时间没有收到DSMP的指配完成消息EV_S_AvrAssign-

mentComplete或指配失败消息EV_S_AvrAssignmentFailure，导致BSSAP

的定时器Tassignment超时，会导致这个失败的原因如下:

l 定时器Tassignment时间太短。l DSMP的实例数配置太大，大于实际支持的DSMP实例数。l DSMP的CPU占用率太高。l 激活SDM时超时。

解解解决决决措措措施施施 1. 检查CMP上的定时器Tassignment是否设置正确，缺省值为6000 （6

秒）。2. 检查RMP与DSMP的关联中DSMP的实例数是否超过允许的范围（不

同的DSMP版本支持的实例数不一样）。3. 确认DSMP的CPU占用率是否太高，若太高则需要扩充DSMP的模

块数。4. 若是激活SDM超时，则可能SDU与CHM间的媒体流不同，或者BSC

与BTS间的时钟不一致，需要检查媒体面的光纤是否连接正确、检查是否存在个别SDU子卡有故障。

1.4 ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect

Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect

Failure Analysis When a mobile station originates a call or is called, it sends a

CMServiceRequest or PagingResponse message to the MSC and receives

a SccpDisconnect message, indicating that the SCCP connection failed to

be established or exceptionally removed.


l No.7 signaling links are unstable or in the wrong state.

l The SSN is in the wrong state.

l The mobile station did not assign numbers correctly on the MSC side.

l The cell CI is different from the CI on the MSC side.

Possible Solution 1. Use a database probe to verify that the signaling point state on the

CMP is 0.

2. Verify that the BSC and the MSC are configured with local and peer

SSNs (0, 1, and 254).

3. Verify that the IMSI and ESN of the mobile station distribute numbers

correctly on the MSC side.

4. Verify that the cell CI in the call origination message CMServiceRequest

is configured correctly on the MSC side.

1-3



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect

失失失败败败原原原因因因分分分析析析手机作起呼或者被呼时，向MSC发送CMServiceRequest或PagingResponse

消息后，收到SccpDisconnect消息，SCCP连接建立失败或异常拆除。会导致这个失败的原因如下：l 7号信令链路不稳定或链路状态不正确。l SSN状态不正确。l 手机在MSC侧没有正确放号。l 小区CI与MSC侧配置的CI不一致。

解解解决决决措措措施施施 1. 通过数据库探针查看CMP上的信令点状态是否为0。2. 检查BSC和MSC侧是否都配置了本端和对端的SSN（0、1、254）。3. 检查手机的IMSI和ESN在MSC侧放号是否正确。4. 检查起呼消息CMServiceRequest中的小区CI在MSC侧是否已正确

配置。

1.5 ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSReleaseOrder

Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSReleaseOrder

Failure Analysis When a call is set up, the mobile station initiates a release on the control

channel.

Possible Solution No troubleshooting is required.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSReleaseOrder

失失失败败败原原原因因因分分分析析析呼叫建立过程中，手机在控制信道发起释放。

解解解决决决措措措施施施属于正常行为，无需处理。

1.6 ERR_SPS_RLSA_BSSAP_TE_TfchsetupFailure Name ERR_SPS_RLSA_BSSAP_TE_Tfchsetup

Failure Cause Timer Tfchsetup expires.

1-4



Failure Analysis When a call is set up, the timer Tfchsetup on CMP expires. The BSC

sends an AbisdfBTSSetup message to BTS to request the fundamental

channel establishment, but the AbisdrBTSSetupAck message that indicates

fundamental channel establishing is successful or unsuccessful is not

received from BTS.


l Timer Tfchsetup expires too soon. The default value is 5000 (5

seconds).

l Fails to establish fundamental channel on BTS.

l CCM CPU usage is too high.

Possible Solution 1. Check the lifecycle of the predefined timer Tfchsetup. If it expires too

soon, change the setting to the default value of 5000.

2. Verify that there are enough CE and FO resources on the BTS.

3. If CCM CPU usage is too high, adjust the CCM CPU overload threshold,

or decrease the antenna transmission power to reduce users.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_TE_Tfchsetup

失失失败败败原原原因因因值值值含含含义义义定时器Tfchsetup超时。

失失失败败败原原原因因因分分分析析析呼叫建立时，BSC向BTS发送了AbisdfBTSSetup消息请求建立基本信道，但是长时间没有收到BTS建立基本信道成功或失败的响应消息AbisdrBTSSetupAck，导致CMP上的定时器Tfchsetup超时。会导致这个失败的原因如下：l 定时器Tfchsetup设置的时长太短，缺省应该是5000（5秒）。l BTS上建立基本信道失败。l CCM的CPU占用率太高。

解解解决决决措措措施施施 1. 检查预定义定时器Tfchsetup的时长是否正确，若设置时长太短则需要修改为缺省值5000。

2. 检查BTS上是否有足够的CE、FO资源。3. 检查CCM的CPU占用率是否过高，如果是则需要调整CCM的CPU过载

控制门限，或通过降低天线发射功率来减少接入用户。

1.7 ERR_SPS_RLSA_BSSAP_TE_T303Failure Name ERR_SPS_RLSA_BSSAP_TE_T303

Failure Cause Timer T303 expires.

1-5



Failure Analysis When a mobile station originates a call or is called, it sends a

CMServiceRequest or PagingResponse message to the MSC. If no returned

AssignmentRequest message from MSC is received, the T303 timer on

the CMP will expire.


l The T303 timer expires too soon.

l The MSC side has a problem in call processing.

Possible Solution 1. Verify that the timer T303 on the CMP is set to the default value 6000

(6 seconds).

2. T303 indicates that the MSC side has a problem in processing the call.

Use MSC tools to locate the failure causes.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_TE_T303

失失失败败败原原原因因因值值值含含含义义义定时器T303超时。

失失失败败败原原原因因因分分分析析析手机作起呼或者被呼时，向MSC发送CMServiceRequest或PagingResponse

消息后，如果长时间没有收到MSC的AssignmentRequest消息，将导致CMP上的T303定时器超时。会导致这个失败的原因如下：l T303定时器设置时长太短。l MSC侧呼叫处理有问题。

解解解决决决措措措施施施 1. 检查CMP上的定时器T303设置是否正确，缺省值为6000（6秒）。2. 从MSC侧查找MSC呼叫失败的原因，出现T303一般都是MSC侧对该呼

叫处理出现问题，问题原因需要通过MSC的工具进行分析。

1.8 ERR_SPS_RLSA_BSSAP_TE_TxxpFailure Name ERR_SPS_RLSA_BSSAP_TE_Txxp

Failure Cause Timer Txxp expires.

Failure Analysis 1. After receiving an assignment complete message, the CallHandler

process sends an A1rAssignmentComplete message to the

MSCe. If the Ap interface is supported, timer Txxp waits for an

A1pfBearerUpdateRequest message from the MSCe.

2. The A1pfBearerUpdateRequest message from the MSCe is not

received before timer Txxp expires. The Txxp timer expires too soon.

3. The MSCe side has a problem in call processing.

Handling Measure 1. Check the setting of timer Txxp on the CMP. The default value is 6

seconds.

2. Locate the call failure causes on the MSCe side.

1-6



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_TE_Txxp

失失失败败败原原原因因因值值值含含含义义义定时器Txxp超时

失失失败败败原原原因因因分分分析析析会导致这个失败的原因如下：l CallHandler进程收到指配完成消息后，向MSCe发送

A1rAssignmentComplet消息，若支持Ap接口，设置定时器Txxp等待MSCe的A1pfBearerUpdateRequest消息。

l 若在Txxp的时间范围内没有收到MSCe的A1pfBearerUpdateRequest消息，则定时器超时，Txxp定时器设置时长太短。

l MSCe侧呼叫处理有问题。

解解解决决决措措措施施施 1. 检查CMP上的定时器Txxp时长是否正确，其默认值为6秒。2. 从MSCe侧查找本次呼叫失败的原因，出现Txxp超时一般都是MSCe侧

对该呼叫处理出现问题，问题原因需要MSCe进行分析。

1.9 ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddrByLogicAddr

Failure Name ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddrByLogicAddr

Failure Cause Failure to retrieve the board network address based on the logical board

address.

Failure Analysis When the BSC sends messages to the BTS, it invokes the database

interface to retrieve the BTS address. If it fails to invoke, the failure cause

will be reported.

Handling Measure Verify that the Abis interface is stable.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddrByLogicAddr

失失失败败败原原原因因因值值值含含含义义义根据单板的逻辑地址获取单板的网络地址失败

失失失败败败原原原因因因分分分析析析 BSC向BTS发送消息时，会调用数据库接口获取BTS的地址，若调用数据库接口返回错误，就会上报该失败原因。

解解解决决决措措措施施施检查Abis接口是否时断时通。如存在Abis口链路不稳定的情况，需要对传输进行检查。

1.10 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_CallProcessing

Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_CallProcessing

1-7



Failure Cause When a call is set up, the BSC receives a ClearCommand message from

the MSC.

Failure Analysis 1. It is caused by the ClearCommand message from CallProcessing

(0x09).

2. A fault occurs in the MSC.

Handling Measure Because ClearCommand is considered as a normal process, the cause

needs to be located on the MSC side. Normally, no troubleshooting is

required.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_CallProcessing

失失失败败败原原原因因因值值值含含含义义义用户在呼叫建立过程中，收到MSC侧的正常呼叫清除消息。

失失失败败败原原原因因因分分分析析析会导致这个失败的原因如下：l 呼叫建立过程中收到MSC侧原因为CallProcessing(0x09)的

ClearCommand消息。l 可能MSC侧处理出现问题。

解解解决决决措措措施施施由于清除呼叫类型为正常清除，所以需要MSC侧查找清除本次呼叫的原因。一般不用处理。

1.11 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_UserBusy

Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_UserBusy

Failure Cause When a call is set up, the BSC receives a ClearCommand message sent

from the MSC, and the cause value in the CauseLayer3 field carried by

this message is 0x11, which indicates that the called user is busy. This

is a normal release.

Failure Analysis The possible failure cause is that the called user is busy.

Handling Measure No troubleshooting is required.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_UserBusy

失失失败败败原原原因因因值值值含含含义义义呼叫建立时，BSC收到MSC发送的ClearCommand消息，消息中携带CauseLayer3字段的原因值为0x11,表明被叫用户正处于业务忙状态，这种情况属于正常的释放。

失失失败败败原原原因因因分分分析析析被叫用户正处于业务忙状态。

解解解决决决措措措施施施正常，无需解决。

1-8



1.12 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NormalClearing

Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NormalClearing


from the MSC, and the cause value in the CauseLayer3 field carried by this

message is 0x10, which indicates it is a normal release.

Failure Analysis The possible failure cause is as follows: the release is initiated on the MSC

side.


失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NormalClearing

失失失败败败原原原因因因值值值含含含义义义呼叫建立时，BSC收到MSC发送的ClearCommand消息，消息中携带CauseLayer3字段原因值为0x10，表明是正常情况下的释放，这种情况属正常现象。

失失失败败败原原原因因因分分分析析析 MSC侧发起的释放。


1.13 ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsedFailure Name ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed

Failure Cause When a call is set up, the BSSAP module detects that the instance number

is used during instance number distribution.

Failure Analysis The BSSAP module recorded a wrong instance number.



cause.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed

失失失败败败原原原因因因值值值含含含义义义呼叫建立时，BSSAP模块在分配业务实例号时，发现该实例号已经被使用。

失失失败败败原原原因因因分分分析析析 BSSAP模块记录的实例号有误。


1-9



1.14 ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFailFailure Name ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail

Failure Cause When a call is set up, the BSC sends an AbisdfBTSSetup message to the

BTS to request the BTS to establish a fundamental channel. However,

all the cells in the AbisdrBTSSetupAck returned by the BTS fail to be

established.

Failure Analysis l CE resource shortage, CE resource is in the wrong state.

l Walsh code shortage.

l FO shortage.

l UID is in the wrong state or the media plane link is incorrect.

l Carrier is in wrong state.

Possible Solution 1. The exact failure causes can be found in the AbisdrBTSSetupAck

message:

l 0x5101 indicates forward fundamental channel CE shortage.

l 0x5102 indicates fundamental channel reverse CE shortage.

l 0x5103 indicates fundamental channel forward shortage and

reverse CE shortage.

l 0x5105 indicates WalshCode shortage.

l 0x5106 indicates that the UID is incorrect.

2. Check the state of CE (normal or blocked).

3. Check the state of carrier (normal or blocked).

4. Check the UID state or media plane link with a database probe.

5. Check the group number of CE on the CHM.

6. Verify that the software versions operating on the BSC and BTS are

the same.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail

失失失败败败原原原因因因值值值含含含义义义呼叫建立时，BSC向BTS发送了AbisdfBTSSetup消息，请求BTS建立基本信道，但BTS返回的AbisdrBTSSetupAck中的所有小区都是建立失败的。

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l CE资源不足，CE资源状态不正确。l WASH码不足。l 帧偏置FO不足。l UID的状态不正确或媒体面链路不正确。l 载频状态不正确。

1-10



解解解决决决措措措施施施 1. AbisdrBTSSetupAck消息失败原因如下：l 0x5101：表示前向基本信道CE不足。l 0x5102：表示基本信道反向CE不足。l 0x5103：表示基本信道前向、反向CE均不足。l 0x5105：表示WalshCode不足。l 0x5106：表示UID不正确。

2. 确认CE状态是否正常，是否被闭塞。3. 确认载频状态是否正常，是否被闭塞。4. 通过数据库探针查看UID状态或者媒体面链路是否正常。5. 检查CHM上配置的CE组号是否正确。6. 查看BSC与BTS运行的软件版本是否一致。

1.15 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NoAnswer

Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NoAnswer


from the MSC, and the cause value in the CauseLayer3 field carried by this

message is 0x13, which indicates it rings without an answer. This is normal.

Failure Analysis The possible failure cause is as follows: Nobody answers the release

initiated by the MSC.


失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NoAnswer

失失失败败败原原原因因因值值值含含含义义义呼叫建立时，BSC收到MSC发送的ClearCommand消息，消息中携带CauseLayer3字段原因值为0x13，表明振铃但无人接听，这种情况属正常现象。

失失失败败败原原原因因因分分分析析析无人接听MSC发起的释放。


1.16 ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit

Failure Name ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit

Failure Cause When a call is being established or a call is being established after hard

handoff, the circuit reset message sent from the MSC is received.

1-11



Failure Analysis l The CIC state on the MSC side and that on the BSC side are different.

l The CIC code on the MSC side and that on the BSC side are different.

Handling Measure 1. Verify that the CIC state on the MSC side and that on the BSC side

are consistent.

2. Verify that the PCM codes on both the MSC and BSC sides are

consistent with the E1 cable.

FurtherTroubleshooting

Contact MSC maintenance personnel for troubleshooting.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit

失失失败败败原原原因因因值值值含含含义义义呼叫建立或者硬切换加建立时，收到MSC发送电路复位消息。

失失失败败败原原原因因因分分分析析析会导致这个失败的原因如下：l MSC侧与BSC侧CIC状态不一致。l MSC侧与BSC侧CIC编码不一致。

解解解决决决措措措施施施 1. 检查MSC侧与BSC侧CIC状态。2. 检查MSC和BSC两侧PCM编号与实际E1接线是否一致。3. 如果仍不能解决问题，请MSC侧协助排查原因。

1.17 ERR_SPS_RLSA_BSSAP_FchSetup_SendChannelAssignment_AllBtsFail

Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_SendChannelAssignment_AllBtsFail

Failure Cause When a call is set up, the Extended Channel Assignment Message to all

BTS fails to be sent.

Failure Analysis l In ECAM/CAM message creation, no established cell is found.

l In ECAM/CAM message creation, the retrieval of power parameters

from database fails.

l Fails to retrieve the system ID/subsystem ID in accordance with PN

when sending the ECAM message.

l There are coding errors when sending the ECAM message.

Fails to retrieve the interface board (ABPM/HGM) address from the

database when sending the ECAM message.

l If there are cross-BSC assignments, the possible cause is failure to

retrieve the address of the BSC interconnection interface board.

1-12



Possible Solution 1. Check more detailed information by checking the fault probe.

2. Check version compatibility.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_FchSetup_SendChannelAssignment_AllBtsFail

失失失败败败原原原因因因值值值含含含义义义呼叫建立时向所有BTS发送Extended Channel Assignment Message都失败。

失失失败败败原原原因因因分分分析析析会导致这个失败的原因如下：l 构造ECAM/CAM消息时发现没有已经建立好的小区。l 构造ECAM/CAM消息时从数据库获取功率参数时失败。l 发送ECAM消息时根据PN获取系统号/子系统号失败。l 发送ECAM消息时编码失败。l 发送ECAM消息时，向数据库获取接口板（abpm/hgm等）地址时

失败。l 如果存在跨BSC指派，可能是获取BSC互联接口板地址失败。

解解解决决决措措措施施施 1. 通过查异常探针，查看更详细的信息。2. 查看各相关板版本是否一致。

1.18 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_HandoffSuccessful

Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_HandoffSuccessful

Failure Cause When a call is being set up or during a call, if a ClearCommand message

sent from the MSC is received, the cause value carried in ClearCommand is

"hard handoff is successful".

Failure Analysis 1. If the hard handoff flow is successful, a Clear Command message will

be received from the MSC.

2. This failure should not occur when a call is being set up.

Handling Measure If the failure occurs when a call is being set up, contact MSC maintenance

personnel for troubleshooting.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_HandoffSuccessful

失失失败败败原原原因因因值值值含含含义义义呼叫建立时或者通话时，收到MSC发送的ClearCommand消息，ClearCom-

mand携带的原因值为“硬切换成功”。

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l 硬切换去流程如果成功，都会收到MSC发送的Clear Command消息。

携带原因为“硬切换去成功”，属于正常现象。l 在呼叫建立过程中不应该出现这种现象。

1-13



解解解决决决措措措施施施如果在呼叫建立过程中出现这个现象，需要联系MSC侧共同解决。

1.19 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_SemiConcurrentService

Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_SemiConcurrent

Service

Failure Cause When a call is set up, during the forward fundamental channel establishment,

the ClearCommand message sent from the MSC is received, and the cause

value carried in ClearCommand is "pseudo concurrent service".

Failure Analysis When the data service is started, there is a new voice incoming call. The

MSC sends a ClearCommand message to request the MS to enter Dormant

state.

Handling Measure This failure is acceptable if it occurs infrequently. If the failure occurs

frequently, contact MSC maintenance personnel for troubleshooting.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_SemiConcurrentSer

vice

失失失败败败原原原因因因值值值含含含义义义呼叫建立时，在前向基本信道建立过程中，收到MSC发送的ClearCommand

消息，ClearCommand携带的原因值为“伪并发业务”。

失失失败败败原原原因因因分分分析析析是刚开始进行数据业务呼叫，有新的语音呼叫到来，MSC发送了ClearCom-

mand，要求MS进入Dormant状态。

解解解决决决措措措施施施属正常情况，若大量出现，与MSC侧配合处理。

1.20 ERR_SPS_RLSA_BSSAP_MsgPara_Origination_InvalidServiceOption

Failure Name ERR_SPS_RLSA_BSSAP_MsgPara_Origination_InvalidServiceOption

Failure Cause The Service Option (SO) carried in the call origination message is invalid.

Failure Analysis Terminal cause. The SO carried in the call origination message is invalid

(not the SO defined in the protocol).

Handling Measure Determine what the SO is in the call origination message and if the terminal

is old or faulty.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_MsgPara_Origination_InvalidServiceOption

1-14



失失失败败败原原原因因因值值值含含含义义义起呼消息中携带的SO非法。

失失失败败败原原原因因因分分分析析析终端原因，起呼消息中携带的SO为非法SO（不是协议中定义的SO）。

解解解决决决措措措施施施确认起呼消息中的SO是什么，终端是否比较老或者有异常。

1.21 ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_SccpId2CallRef

Failure Name ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_SccpId2CallRef

Failure Cause When an SCCP connection number is added into the HASH entry of the

call reference number, the Hash operation fails.

Failure Analysis Hash is probably hung up.

Handling Measure Check the fault probe and take measures after identifying the cause.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_SccpId2CallRef

失失失败败败原原原因因因值值值含含含义义义增加SCCP连接号到呼叫参考号的HASH表项时，Hash操作失败。

失失失败败败原原原因因因分分分析析析可能出现了Hash吊死。

解解解决决决措措措施施施需分析异常探针，待确定失败原因后再进行相应处理。

1.22 ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail

Failure Name ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail

Failure Cause The 97D test fails to obtain the MSID of the terminated call.

Failure Analysis The interface between modules is faulty.

Handling Measure Save fault probe information and contact the local ZTE office.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail

失失失败败败原原原因因因值值值含含含义义义 97D测试获取终呼MSId时出错。

失失失败败败原原原因因因分分分析析析模块间的接口出现了问题。

解解解决决决措措措施施施保存异常探针等相关信息，请联系中兴通讯。

1-15



1.23 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_EquipmentFailure

Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_EquipmentFailure

Failure Cause When a call is set up, the MSC sends a ClearCommand message to release

the call, and the failure cause is equipment failure.

Failure Analysis The MSC has an internal problem, and contact MSC maintenance personnel

for troubleshooting.



cause.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_EquipmentFailure

失失失败败败原原原因因因值值值含含含义义义呼叫建立时，MSC发送ClearCommand消息释放呼叫，失败原因是设备故障。

失失失败败败原原原因因因分分分析析析 MSC侧内部出了问题，具体细节需要联系MSC侧配合查找。


1.24 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_AuthenticationFailure

Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_AuthenticationFai

lure

Failure Cause When a call is set up, the MSC sends a ClearCommand message to release

the call due to authentication failure.

Failure Analysis The terminal is invalid.

Handling Measure Contact MSC maintenance personnel for troubleshooting.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_AuthenticationFailu

re

失失失败败败原原原因因因值值值含含含义义义呼叫建立时，MSC发送ClearCommand消息释放呼叫，原因是鉴权失败。

失失失败败败原原原因因因分分分析析析可能是终端不合法。

解解解决决决措措措施施施需要和MSC侧配合查找原因。

1-16



1.25 ERR_SPS_RLSA_BSSAP_FchSetup_AllLegAreRemoved

Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_AllLegAreRemoved

Failure Cause During call setup, the channel board detects that the RCM sends an

EV_S_AbisdrTargetRemovalRequest message to the BSSAP to release the

call. After receiving the message, the BSSAP releases the call.

Failure Analysis l Timer Tassingment is set to over 6 seconds.

l Transmission at the Abisc port is unstable.

l The clock is wrong.

l The IC of the channel board has a problem.

Possible Solution 1. Check the timer setting.

2. Check the Abisc port transmission.

3. Check the BTS clock.

4. Check the IC of the channel board.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_FchSetup_AllLegAreRemoved

失失失败败败原原原因因因值值值含含含义义义在呼叫建立过程中，信道板检测到前向无帧向RCM模块发起释放，RCM模块向BSSAP发送EV_S_AbisdrTargetRemovalRequest消息释放呼叫，BSSAP

收到后发起释放。

失失失败败败原原原因因因分分分析析析会导致这个失败的原因如下：l Tassingment定时器设置不合理，超过6秒钟。l Abis口传输不稳定。l 时钟不正常。l 信道板芯片有问题。

解解解决决决措措措施施施 1. 检查定时器设置。2. 检查Abis口传输。3. 检查BTS侧时钟。4. 诊断信道板芯片。

1.26 ERR_SPS_RLSA_BSSAP_Other_SpcfSelectTableBad

Failure Name ERR_SPS_RLSA_BSSAP_Other_SpcfSelectTableBad

Failure Cause During data service setup, SPCF is not detected in the normal state.

Failure Analysis l The PCF configuration is incomplete.

l No RP link is available.

l No UPCF is available.

1-17



Possible Solution 1. Verify that the PCF configuration is normal.

2. Verify that the network communication between the PCF and PDSN is

normal and the PDSN is operating properly.

3. Verify that the UPCF board is operating properly.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_Other_SpcfSelectTableBad

失失失败败败原原原因因因值值值含含含义义义数据业务建立时无法选出状态正常的SPCF。

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l PCF配置不全。l 无可用RP链路。l 无可用UPCF。

解解解决决决措措措施施施 1. 检查PCF配置是否正确。2. 检查PCF和PDSN之间网络通信是否正常，PDSN是否运行正常。3. 检查UPCF单板是否运行正常。

1.27 ERR_SPS_RLSA_BSSAP_Other_RTDOutofRangeFailure Name ERR_SPS_RLSA_BSSAP_Other_RTDOutofRange

Failure Cause During call setup, the mobile station is beyond the RTD distance limit of

the cell.

Failure Analysis The possible causes are as follows:

l The distance between the MS and the BTS is out of the specified range.

l The RTD configuration in the cell parameters is unreasonable.

Handling Measure If the mobility restriction function is enabled, ignore the problem; otherwise,

adjust the RTD distance limit parameters on the OMC.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_Other_RTDOutofRange

失失失败败败原原原因因因值值值含含含义义义建立呼叫时，移动台超出了小区的RTD距离限制范围。

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：1. 移动台与基站的距离超出一定范围。2. 小区参数中的RTD配置得不合理。

解解解决决决措措措施施施如果开启了移动性限制功能，则无需关注，否则，需在OMC配置中调整RTD距离限制参数。

1-18



1.28 ERR_SPS_RLSA_BSSAP_MultiSP_InvalidMSCOfficeId

Failure Name ERR_SPS_RLSA_BSSAP_MultiSP_InvalidMSCOfficeId

Failure Cause The network has multiple signaling points, and the correct office direction

number fails to be selected.

Failure Analysis 1. The data service paging response cannot select the correct office

direction number.

2. The voice originating call and paging response, data service originating

call, and other service paging and paging response cannot select the

correct office direction number.

Handling Measure 1. Verify that the office direction selection switch for data paging response

(DataPagingRspOfficeIdSelect) is set correctly.

2. Verify that the selection switch for common office direction

(CallOfficeIdSelect) is set correctly.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_MultiSP_InvalidMSCOfficeId

失失失败败败原原原因因因值值值含含含义义义组网方式为多信令点，无法选择出正确的局向号。

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l 数据业务寻呼响应无法选择出正确的局向号。l 语音起呼和寻呼响应，数据业务起呼，其他业务起呼和寻呼响应无法选

择出正确的局向号。

解解解决决决措措措施施施 1. 检查数据业务寻呼响应局向选择开关（DataPagingRspOfficeIdSelect）设置是否正确。

2. 检查普通业务局向选择开关（CallOfficeIdSelect）设置是否正确。

1.29 ERR_SPS_RLSA_BSSAP_MultiSP_MSCOfficeUnavailable

Failure Name ERR_SPS_RLSA_BSSAP_MultiSP_MSCOfficeUnavailable

Failure Cause The network has multiple signaling points. The state of the selected office

direction is abnormal and results in call failure.

Failure Analysis The abnormal office direction state results in call failure.

Handling Measure Verify that the signaling link configuration and the physical link in the office

direction are normal.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_MultiSP_MSCOfficeUnavailable

1-19



失失失败败败原原原因因因值值值含含含义义义组网方式为多信令点，选择出来的局向状态不正常，导致呼叫失败。

失失失败败败原原原因因因分分分析析析局向状态不正常，导致呼叫失败。

解解解决决决措措措施施施检查该局向的信令链路配置和物理连接是否正常。

1.30 ERR_SPS_RLSA_BSSAP_MultiSP_A1fAssignReq_InvalidMSCOfficeId

Failure Name ERR_SPS_RLSA_BSSAP_MultiSP_A1fAssignReq_InvalidMSCOfficeId

Failure Cause The network has multiple signaling points. The office direction number in

the A1fAssignmentRequest message is wrong.

Failure Analysis The internal flow is abnormal.

Handling Measure Save the signaling track, service observation, and fault probe, and contact

the R&D personnel for troubleshooting.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_MultiSP_A1fAssignReq_InvalidMSCOfficeId

失失失败败败原原原因因因值值值含含含义义义组网方式为多信令点，A1fAssignmentRequest消息中的局向号不正确。

失失失败败败原原原因因因分分分析析析内部流程异常，正常情况不会出现。

解解解决决决措措措施施施保存信令跟踪，业务观察，异常探针，请联系中兴通讯进行解决。

1.31 ERR_SPS_RLSA_BSSAP_MsgPara_MSRejectOrder

Failure Name ERR_SPS_RLSA_BSSAP_MsgPara_MSRejectOrder

Failure Cause During call setup, the terminal refuses the forward message from the BSC.

Failure Analysis l If the user is called while preparing to dial at the fixed station, the

terminal will refuse the ECAM/CAM messages.

l Some terminals refuse the service negotiation messages.

l Make analysis from signaling in other situations.

Possible Solution The occasional occurrence of the above is normal. If the problem occurs


cause.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_MsgPara_MSRejectOrder

失失失败败败原原原因因因值值值含含含义义义呼叫建立过程中终端拒绝基站的前向消息。

1-20



失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l 一些固定台在拿起话筒准备拨号的时候，如果此时该用户做被叫，就

会出现终端拒绝ECAM/CAM消息。l 一些终端拒绝业务协商消息。l 其他情况需要根据信令来具体分析。


1.32 ERR_SPS_RLSA_BSSAP_Other_Encode_A1MsgInBSC

Failure Name ERR_SPS_RLSA_BSSAP_Other_Encode_A1MsgInBSC

Failure Cause Message coding failure of the A interface.

Failure Analysis The coding failure is caused by incorrect A interface message type, format,

and length.

Handling Measure The failure is caused by incorrect A interface message. It is acceptable if

the problem occurs occasionally. If the problem occurs frequently, contact the

R&D personnel for troubleshooting.

1.33 ERR_SPS_RLSA_BSSAP_Other_Encode_UmpMsgInBSC

Failure Name ERR_SPS_RLSA_BSSAP_Other_Encode_UmpMsgInBSC

Failure Cause Air interface message coding failure.

Failure Analysis The coding failure may result from an error in the type, assignment mode,

format or length of the air interface message.

Handling Measure The failure results from multiple factors. Contact MSC maintenance

personnel for troubleshooting.

1.34 ERR_SPS_RLSA_BSSAP_Other_Decode_UmpMsgInBSC

Failure Name ERR_SPS_RLSA_BSSAP_Other_Decode_UmpMsgInBSC

Failure Cause Air interface message decoding failure.

1-21



Failure Analysis The decoding failure may result from an error in the type, format or length of

the air interface message.

Handling Measure The failure results from an incorrect air interface message. If the failure

occurs occasionally, no troubleshooting is required.

If the failure occurs frequently, contact terminal maintenance personnel for

troubleshooting.

1.35 ERR_SPS_RLSA_BSSAP_TE_Ta1_4Failure Name ERR_SPS_RLSA_BSSAP_TE_Ta1_4

Failure Cause The Ta1_4 timer expires.

Failure Analysis After an A1rReset message is sent to the MSC, the MSC does not respond

before the Ta1_4 timer expires. The A1rReset message is retransmitted 30

times at most, and then the system enters the normal operating status.

Handling Measure The failure results from A interface link disconnection. If it occurs

occasionally, it is normal.

If it occurs frequently, check the status of the link connecting the MSC.

1.36 ERR_SPS_RLSA_BSSAP_PoorPilotFailure Name ERR_SPS_RLSA_BSSAP_PoorPilot

Failure Cause The pilot strength is weak when the MS makes a call.

Failure Analysis When the Reject Weak Pilot switch is enabled, the system will report the

exception if the pilot strength carried in the originating call message is lower

than the threshold set in the OMC.

Handling Measure Verify that the setting of the threshold is reasonable. If the exception occurs

frequently, check the local signal or contact the local ZTE office.

1.37 ERR_SPS_RLSA_BSSAP_FchSetup_SendPCHMsg_AllBtsFail

Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_SendPCHMsg_AllBtsFail

Failure Cause The paging channel message fails to be transmitted.

Failure Analysis The failure may result from intermittent bit error bursts over the Abis link.

Handling Measure Check the Abis link. If it is abnormal, contact the local ZTE office.

1-22



1.38 ERR_SPS_RLSA_BSSAP_DB_GetLinkInfoFailure Name ERR_SPS_RLSA_BSSAP_DB_GetLinkInfo

Failure Cause A failure occurs when the database EV_D_S_GetLinkAndLacNumByMod-

ule_V interface is invoked to get the signaling link message.

Failure Analysis The database is abnormal or a version mismatch occurs.

Handling Measure Verify that the RMP and CMP versions are matched.

1.39 ERR_SPS_RLSA_BSSAP_DB_GetValidCarrierFailure Name ERR_SPS_RLSA_BSSAP_DB_GetValidCarrier

Failure Cause The configured carrier ID of the first carrier fails to be obtained.

Failure Analysis The database is abnormal or the configuration is incorrect.

Handling Measure Verify that the carrier configuration is correct.

1.40 ERR_SPS_RLSA_BSSAP_DB_GetOPBySysIdCellIdCrId

Failure Name ERR_SPS_RLSA_BSSAP_DB_GetOPBySysIdCellIdCrId

Failure Cause An exception occurs when the database is invoked to get the OP value.

Failure Analysis The database is abnormal.

Handling Measure Contact technical personnel of the database.

1.41 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Twaitorder

Failure Name ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Twaitorder

Failure Cause When an MS originates a call or is called, after successfully entering the

traffic channel and capturing the prefix, the air-interface traffic channel

signaling handshake expires.

Failure Analysis l Poor radio condition results in air-interface handshake message loss. It

is acceptable if this failure occurs occasionally.

l If frame number checking is enabled, the BTS and the BSC have

different clocks.

l Other causes: such as bit errors.

1-23



Possible Solution 1. Verify that the transmission power of the cell is normal.

2. Ensure the version compatibility and proper operation of the CHM and

SDU boards.

3. If the failure occurs frequently, check whether the problem is caused

by a single base station, all base stations under an ABPM), or the

whole BSC.

4. After locating the fault, disable the frame number checking on the faulty

BTS. If the situation improves, it indicates that the problem is caused by

different BTS and BSC clocks. Verify that the GPS and clock are normal,

and the GCM boards on the BTS and BSC sides operate properly.

5. Ensure correct versions and proper operation of the ABPM, DTB, and

DSM interface boards.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Twaitorder

失失失败败败原原原因因因值值值含含含义义义在MS起呼或者被呼，进入业务信道，捕获前缀成功后，进行空口业务信道信令握手超时。

失失失败败败原原原因因因分分分析析析导致这个失败的主要原因如下：l 无线环境恶劣导致丢失空口握手消息，少量出现属正常现象。l 打开帧序号校验情况下，BTS和BSC时钟不一致。l 其他原因，例如传输误码等。

解解解决决决措措措施施施 1. 查看小区发射功率是否正常。2. 查看CHM和SDU单板运行版本是否匹配，是否运行正常。3. 如果大量出现该呼叫失败，首先需要确定问题的范围：单站问题、一

个ABPM下挂所有站点的问题、还是整个BSC的问题。4. 确定问题范围后，把出问题的BTS帧序号校验关闭，观察是否有所改

善，如果问题有很大改善，说明是由于BTS时钟和BSC时钟不一致导致的问题；查看GPS和时钟是否正常、BTS侧和BSC侧GCM单版是否正常运行。

5. 检查ABPM、DTB、DSM等接口板版本是否正确，运行是否正常。

1.42 ERR_SPS_RLSA_BSSAP_Other_DifferenceInFwdOrRevRC

Failure Name ERR_SPS_RLSA_BSSAP_Other_DifferenceInFwdOrRevRC

Failure Cause During a call test, the forward RC handoff judgment and reverse RC handoff

judgment of the fundamental channel are different.

Failure Analysis The RC that is configured for the call test and its SO do not match.

1-24



Handling Measure Modify the RC to be an available RC of the corresponding SO. If you are not

clear about the mapping between SOs and RCs, contact ZTE Corporation

for analysis.

1.43 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNFailure

Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNFailure

Failure Cause When an MS originates a call or is called, after entering the traffic channel,

the service negotiation between the base station and the MS fails.

Failure Analysis The possible failure causes are as follows:

1. Poor radio condition causes air-interface negotiation message missing.

It is acceptable if this failure occurs occasionally.

2. The VTC operating mode configured on the BSS has a problem.

Handling Measure 1. Verify that the forward power of the cell is normal.

2. If the negotiation failure occurs frequently on the mobile stations of a

specific model, verify that the VTC operating mode configured on the

BSS is correct (default setting: 8K+EVRC).


If the problem persists, capture the call failure signaling and contact the

local ZTE office.

失败原因值 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNFailure

失败原因值含义在MS起呼或者被呼，进入业务信道后，基站与MS的业务协商失败。

失败原因分析 l 无线环境恶劣导致丢失空口协商消息，少量出现属正常现象。l BSS配置的VTC工作模式有问题。

解决措施 1. 查看小区前向功率是否正常。2. 如果出现某一类型手机总是协商失败，查看BSS配置的VTC工作模式是

否正确（默认为8K+EVRC）。3. 更换几种组合进行测试。4. 如果仍不能解决问题，抓取呼叫失败信令并联系中兴通讯。

1.44 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tpcfinfol3

Failure Name ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tpcfinfol3

1-25



Failure Cause During data service call setup, after the A8 link is established, the DSPM

sends an Abaf_PCFInfoL3 message to the SDM, but fails to receive a

response in Tpcfinfol3 (3s), and timer Tpcfinfol3 expires.

Failure Analysis l Timer Tpcfinfol3 has a problem in setting.

l The corresponding SDU operates improperly.

Possible Solution 1. Verify that the setting of timer Tpcfinfol3 on the DSMP board is correct

(default value: 3 s).

2. Verify that the corresponding SDU operates properly, and there is no

abnormal reset or switchover.

3. Ensure correct version and proper operation of the SDU.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tpcfinfol3

失失失败败败原原原因因因值值值含含含义义义数据业务呼叫建立阶段，A8建链后，DSPM向SDM发送Abaf_PCFInfoL3消息，在Tpcfinfol3（3 s）内收不到应答消息，定时器Tpcfinfol3超时。

失失失败败败原原原因因因分分分析析析 l Tpcfinfol3定时器设置有问题。l 对应的SDU运行异常。

解解解决决决措措措施施施 1. DSMP单版上Tpcfinfol3定时器设置是否正确（默认3 s）。2. 查看出问题时对应的SDU运行是否正常，是否有异常复位或倒换。3. 检查SDU版本是否正确，运行是否正常。

1.45 ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq

Failure Name ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq

Failure Cause In FSCH establishment, after the BSC sends a BurstRequest message,

the BurstResponse message from the BTS is not received, and timer

Tfschbstreq expires.

Failure Analysis The message is lost at the Abis interface. It is acceptable if the problem

occurs occasionally.

Possible Solution 1. Verify that the setting of timer Tfschbstreq is correct (500 ms).

2. Verify that the message is not lost.

3. Ensure correct versions and proper operation of the CCM, ABPM, DTB,

and DSM boards.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq

失失失败败败原原原因因因值值值含含含义义义建立FSCH时，BSC发送BurstRequest消息后，Tfschbstreq定时器超时没有收到BTS的BurstResponse消息。

1-26



失失失败败败原原原因因因分分分析析析 Abis口消息丢失，少量出现属正常现象。

解解解决决决措措措施施施 1. 检查Tfschbstreq定时器设置是否正确（500 ms）。2. 检查是否丢消息。3. 检查CCM、ABPM、DTB、DSM等板版本是否正确，运行是否正常。

1.46 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_Unspecified

Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_Uns

pecified

Failure Cause During data service call setup, the A8 link setup fails. When the cause value

that the PDSN brings to the DSPM is 0x80, the failure cause is reported by

the DSPM.


1. The A10 link setup fails.

2. The corresponding PCF operates improperly. There is abnormal reset

or switchover.

Handling Measure 1. Verify that the A10 link is successfully established.

2. Verify that the corresponding PCF operates properly, and there is no


失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_Un

specified

失失失败败败原原原因因因值值值含含含义义义数据业务呼叫建立阶段，A8链路建立失败，PDSN给DSPM带的失败原因值为0x80时，DSPM上报的失败原因。

失失失败败败原原原因因因分分分析析析 l A10链路建立失败。l 查看出问题时对应的PCF运行是否正常，是否有异常复位或倒换。

解解解决决决措措措施施施检查A10链路是否建立成功。

1.47 ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8setup

Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8setup

Failure Cause During data service call setup, the A8 link establishment expires: The

DSPM sends an A9SetupA8 message to the PCF, but fails to receive a reply

message in Ta8setup (3 s).

1-27



Failure Analysis l In the OMC, the PCF IP address configuration has a problem.

l The physical link is broken.

l The corresponding PCF is faulty.

Possible Solution 1. Verify that the setting of the Ta8setup timer (default value is 3 s) on

the DSMP board is correct.

2. Verify that the PCF IP address configuration in the OMC is correct and

the physical link is normal.

3. Verify that the corresponding PCF operates properly and there is no


失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8setup

失失失败败败原原原因因因值值值含含含义义义数据业务呼叫建立阶段，A8建链超时：DSPM发送A9SetupA8消息给PCF，在Ta8setup（3 s）内收不到任何应答消息。

失失失败败败原原原因因因分分分析析析导致这个失败的主要原因如下：l 在OMC中，PCF IP地址配置有问题。l 物理链路不通。l 对应的PCF异常。

解解解决决决措措措施施施 1. DSMP单版上Ta8setup定时器设置是否正确（默认3 s）。2. 查看OMC中PCF IP地址配置是否正确，物理链路是否正常。3. 查看出问题时对应的PCF运行是否正常，是否有异常复位或倒换。

1.48 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_Administratively_Pohibited

Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason _PDSNDenied_Reason_

Administratively_Pohibited

Failure Cause During data service call setup, the A8 link setup fails when the cause value

that the PDSN brings to the DSPM is 0x81, and the failure cause is reported

by the DSPM.



2. The corresponding PCF operates improperly. There is abnormal reset

or switchover.


2. Verify that the corresponding PCF operates properly, and there is no


1-28



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_CLH_OtherReason _PDSNDenied_Reason_Ad

ministratively_Pohibited

失失失败败败原原原因因因值值值含含含义义义数据业务呼叫建立阶段，A8链路建立失败，PDSN给DSPM带的失败原因值为0x81时，DSPM上报的失败原因。

失失失败败败原原原因因因分分分析析析 l A10链路建立失败。l 查看出问题时对应的PCF运行是否正常，是否有异常复位或倒换。

解解解决决决措措措施施施检查A10链路是否建立成功。

1.49 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_PDSN_Resource_Unavailable

Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_PDSN_Resour

ce_Unavailable

Failure Cause During data service call setup, the A8 link setup fails. The cause value that

the PCF brings to the DSPM is that the PDSN resource is unavailable.



2. The PDSN is faulty.


2. Verify that the corresponding PDSN operates properly, and there is

no abnormal reset or switchover.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_PDSN_Resour

ce_Unavailable

失失失败败败原原原因因因值值值含含含义义义数据业务呼叫建立阶段，A8链路建立失败，PCF给DSPM带的失败原因值，PDSN资源不可用。

失失失败败败原原原因因因分分分析析析 l A10链路建立失败。l PDSN异常。

解解解决决决措措措施施施 1. 检查A10链路是否建立成功。2. 查看出问题时对应的PDSN运行是否正常，是否有异常复位或倒换。

1.50 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHRequestMsg_FCHNotExisted

Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHReques

tMsg_FCHNotExisted

1-29



Failure Cause The data service fundamental channel receives a message from the SCH

for setup.

Failure Analysis The possible failure cause is as follows: The call origination flow has not

finished.

Handling Measure It is acceptable if the problem occurs occasionally. If the problem occurs

frequently, contact the local office of ZTE Corporation.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHReques

tMsg_FCHNotExisted

失失失败败败原原原因因因值值值含含含义义义数据业务基本信道尚未建立时，收到补充信道请求建立消息。

失失失败败败原原原因因因分分分析析析起呼流程尚未走完。

解解解决决决措措措施施施少量出现无需关注,如大量出现请联系中兴通讯。

1.51 ERR_SPS_RLSA_DSPM_SCHH_ResNotSatisfied_SCHHOnFwdAllBurstResponse_NoCommitedCell

Failure Name ERR_SPS_RLSA_DSPM_SCHH_ResNotSatisfied_SCHHOnFwdAllBurstR

esponse_NoCommitedCell

Failure Cause When the BSC applies for establishment of a forward supplementary

channel, there is no successful cell in the BTS response.

Failure Analysis Shortage of BTS resources, such as CE, power, Walsh code, and UID.

Handling Measure Analyze the current traffic of this BTS and check the occupancy of all

resources. If the occupancy state accords with traffic capacity, the resource

shortage is the failure cause of setting up the supplementary channel. If the

occupancy state is greatly different from the traffic capacity,

1. Verify that this BTS operates properly and the version is correct.

2. Verify that the resources are not blocked and the resource state is

correct.

3. If the above are normal, maybe the resources such as CE, power,

Walsh code, and UID are occupied by other requests.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_SCHH_ResNotSatisfied_SCHHOnFwdAllBurstR

esponse_NoCommitedCell

失失失败败败原原原因因因值值值含含含义义义 BSC申请建立前向补充信道时，BTS回的响应中没有成功的小区。

失失失败败败原原原因因因分分分析析析 BTS侧资源不足，例如CE，功率，Walsh码，UID等，导致无法建立补充信道。

1-30



解解解决决决措措措施施施出现该失败时，分析该BTS当前话务量，检查各种资源占用情况，若与话务量大小相符，则是因为资源不足导致前向补充信道无法建立，若有较大出入：1. 检查该BTS运行是否正常。2. 运行版本是否正确。3. 检查是否有资源闭塞，资源状态是否正确。4. 若上述检查无异常，则可能出现资源吊死。

1.52 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAcrBSCAddChannelItemAck_AddChannelItemFailed

Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAcrBSCAddCha

nnelItemAck_AddChannelItemFailed

Failure Cause Adding the forward supplementary channel table fails.

Failure Analysis 1. Failure value 1: The entered parameters are incorrect.

2. Failure value 2: The channel table is not created.

3. Failure value 3: No ENTRY space is available.

4. Failure value 4: No BLOCK space is available.

5. Failure value 5: No ENTRY space is available.

6. Failure value 6: The keyword for adding the channel table is too long.

7. Failure value 7: The number of UIDs is inconsistent with that in the

multicast group.

Handling Measure 1. Verify that the ABPM and IBBE boards are normal.

2. Obtain more details by querying the fault probe.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAcrBSCAddCha

nnelItemAck_AddChannelItemFailed

失失失败败败原原原因因因值值值含含含义义义补充信道通道表添加失败

失失失败败败原原原因因因分分分析析析 l 输入参数错误，对应的原因值为1。l 通道表还未创建，对应的原因值为2。l 已无ENTRY空间，对应的原因值为3。l 已无BLOCK空间，对应的原因值为4。l 已无COLLISION空间，对应的原因值为5。l 加通道表关键字长度过长，对应的原因值为6。l UID数量与组播组中数量不一致，对应的原因值为7。

解解解决决决措措措施施施 1. 检查ABPM和IBBE板是否正常。2. 通过查异常探针，查看更详细的信息。

1-31



1.53 SDM_Activate_Fail_AcquirePreambleFail_NormalFailure Name SDM_Activate_Fail_AcquirePreambleFail_Normal

Failure Analysis The MS capture fails; The BSC has not received Preamble sent by the MS

before timeout, but Idle frames can be received. There are many reasons for

this fault. Any problem in the system can cause failure in MS capture, such

as wrong CHM version, inconsistency in parameters for the MS and those

of the base station, long code error, inconsistent RC, and PN offset error.

Possible Solution 1. Check the CHM version.

2. Check the failure cause submitted to the fault probe.

3. Verify that there are residual forward CEs in the RB_FWDCE list.

4. Verify that the channel board does not block CE.

失失失败败败原原原因因因值值值 SDM_Activate_Fail_AcquirePreambleFail_Normal

失失失败败败原原原因因因分分分析析析捕获手机失败，在定时器超时前没有收到手机发给BSC的Preamble，但能收到Idle帧。该异常原因有很多种，系统中的每个问题都有可能引起捕获手机失败。例如：CHM版本不对、给手机的参数与基站侧的不一致，长码错误、RC不一致、PN偏置错误等。

解解解决决决措措措施施施 1. 检查CHM版本。2. 查看异常探针里上报的失败原因。3. 查看RB_FWDCE表是否还有剩余的前向CE。4. 查看信道板是否闭塞了CE。

1.54 SDM_Activate_Fail_AcquirePreambleFail_NoRevFrm

Failure Name SDM_Activate_Fail_AcquirePreambleFail_NoRevFrm

Failure Analysis The BSC cannot receive the reverse traffic frame sent by the BTS before

the timer expires. There are many possible causes:

l The link for the Abis media flow is blocked.

l The channel list is incorrectly added on either the BTS or the BSC.

Possible Solution 1. Verify that the Abis link is not disconnected.

2. Verify that the addition of channel list (the BSC and BTS sides) in

signaling tracing is successful.

3. Verify that no CE is suspended on the CHM board.

失失失败败败原原原因因因值值值 SDM_Activate_Fail_AcquirePreambleFail_NoRevFrm

1-32



失失失败败败原原原因因因分分分析析析捕获手机失败，在定时器超时前没有收到BTS发给BSC的反向业务帧。BSC连BTS侧发来的业务帧都收不到，原因也有很多种，主要如下：l Abis媒体流链路不通。l BTS或BSC侧任一方通道表加错等。

解解解决决决措措措施施施 1. 检查Abis链路是否断链。2. 查看信令跟踪里添加通道表（BSC及BTS侧）是否成功。3. 查看CHM是否有CE吊死。

1.55 SDM_Find_Fail_WaitConfigVTCTimeoutFailure Name SDM_Find_Fail_WaitConfigVTCTimeout

Failure Cause After SDM activation, the SDM does not receive the EV_S_AbafS-

tartVocoderCoding message sent by the DSPM before the timer expires.

Failure Analysis The possible causes are as follows:

1. Service negotiation between Layer 3 and the MS fails and Layer 3 does

not receive a confirmation message from the MS. Detailed reasons vary:

l The MS does not receive the confirmation message on the BS side,

so it does not return a confirmation message to the BS.

l The MS has received a confirmation message on the BS side, but it

does not return the confirmation to the BS.

l The fault may also be caused by inconsistent parameters between

the MS and the BS side (such as RC inconsistency), which results

in the MS unable to detect the confirmation message on the base

station.

2. Abnormal Layer 3 process. After successful negotiation with the MS,

the EV_S_AbafStartVocoderCoding message is not sent to the SDM.

Handling Measure 1. Verify that there is a handshake message (EV_S_UmfBSOrder or

EV_S_UmrMSOrder) of the traffic channel.

2. If neither messages exists, the reason might be inconsistent parameters

on the MS and BS sides. Check the versions of the MS and BS sides.

3. If the handshake is normal, check whether the signaling has an

EV_S_AbafStartVocoderCoding message; if no, the DSPM has not

sent a message.

失失失败败败原原原因因因值值值 SDM_Find_Fail_WaitConfigVTCTimeout

1-33



失失失败败败原原原因因因分分分析析析 SDM激活成功后，在定时器超时前没有收到DSPM发给SDM的EV_S_AbafStartVocoderCoding消息。该异常可能原因有以下两种：l 层三与手机的业务协商失败，层三没有收到手机的证实消息。具体原

因有很多：比如手机本身没有收到BS侧的证实消息，因此也不会回证实消息给BS。或者手机收到了BS侧的证实消息，但是由于某种原因没有给BS回证实。该异常也有可能是手机和BS侧参数不一致（例如RC

不一致），导致手机解不出基站侧的证实消息等等。l 层三处理异常，与手机协商成功后，仍未发送EV_S_AbafStartVocoder-

Coding消息给SDM，可从信令跟踪中进行判断。

解解解决决决措措措施施施 1. 检查是否有业务信道的握手消息EV_S_UmfBSOrder和EV_S_UmrMSOrder。

2. 如果没有其中任何一条消息，可能是MS和BS侧参数不一致，检查MS

以及BS侧的版本。3. 如果握手正常，查看信令中有没有EV_S_AbafStartVocoderCoding消

息，如果没有，是DSPM没有发消息。

1.56 SDM_Find_Fail_WaitConfigRLPTimeoutFailure Name SDM_Find_Fail_WaitConfigRLPTimeout

Failure Analysis When waiting for an EV_S_AbafPCFInfoL3 message sent by Layer 3 after

successful data service SDM activation, the message is not received before

the timer expires.

Handling Measure 1. Verify that the PCF is correctly configured.

2. Verify that the UPCF board operates properly.

失失失败败败原原原因因因值值值 SDM_Find_Fail_WaitConfigRLPTimeout

失失失败败败原原原因因因分分分析析析数据业务SDM激活成功后，等待层三发来的EV_S_AbafPCFInfoL3消息，定时器超时，没收到该消息。

解解解决决决措措措施施施这种异常一般是因为层三与手机握手超时。

1.57 SDM_Link_Fail_RSCHLegLinkFailFailure Name SDM_Link_Fail_RSCHLegLinkFail

Failure Analysis The RSCH leg does not receive the frames sent from the reverse channel

in 18 s.

Handling Measure 1. Check the signaling and verify that the CHM has released the leg.

2. Verify that the reverse link has no problem.

3. Check CHM statistics for frame receiving and sending.

1-34



失失失败败败原原原因因因值值值 SDM_Link_Fail_RSCHLegLinkFail

失失失败败败原原原因因因分分分析析析反向补充信道腿18 s没有收到反向信道板过来的帧。

解解解决决决措措措施施施 1. 检查信令，CHM是否已经释放该条腿。2. 查看反向链路，看有没有问题。3. 查看CHM的收发帧统计。

1.58 SDM_Activate_Fail_InitVocoderFailFailure Name SDM_Activate_Fail_InitVocoderFail

Failure Cause The SDM fails to send an initialized Vocoder message.

Failure Analysis l The CPU utilization of the SDU board is too high.

l The bottom level has a problem.

Handling Measure 1. If the SDU board utilization ratio is too high, add an additional new

board.

2. If the SDU board is normal but the fault persists, contact the local ZTE

office.

失失失败败败原原原因因因值值值 SDM_Activate_Fail_InitVocoderFail

失失失败败败原原原因因因分分分析析析 SDM发送初始化声码器消息失败。可能原因是：SDU单板CPU利用率太高，消息无法发出，或底层出了问题。

解解解决决决措措措施施施 1. 检查SDU单板利用率，如果SDU单板利用率过高，则需增加单板。2. 如果SDU单板正常但故障依然存在，请联系中兴通讯。

1.59 SDM_OprVocoder_Fail_WaitStartVocoderCodingAckTimeOut

Failure Name SDM_OprVocoder_Fail_WaitStartVocoderCodingAckTimeOut

Failure Cause The SDM cannot receive an ACK message from the VTC after sending a

startVocoderCoding message to the VTC.

Failure Analysis The startVocoderCoding message or the ACK message is lost among

boards.

Handling Measure Contact engineers at local ZTE office.

失失失败败败原原原因因因值值值 SDM_OprVocoder_Fail_WaitStartVocoderCodingAckTimeOut

1-35



失失失败败败原原原因因因分分分析析析 SDM在给VTC发了startVocoderCoding消息后，收不到VTC的ACK消息，可能原因是单板之间有丢消息的现象，丢失startVocoderCoding消息，或是丢失ACK消息。

解解解决决决措措措施施施请联系中兴通讯。

1.60 SDM_Activate_Fail_MsgParaFailFailure Name SDM_Activate_Fail_MsgParaFail

Failure Cause The SDM receives a AbafActivateSDM message sent by Layer 3, but the

parameter(s) in the message are incorrect.

Handling Measure Check the SDM fault probe message to locate the wrong parameter(s).

Check the AbafActivateSDM message in signaling tracing to locate the

fault and determine whether Layer 3 is incorrectly written or it is an SDM

process problem.

失失失败败败原原原因因因值值值 SDM_Activate_Fail_MsgParaFail

失失失败败败原原原因因因分分分析析析 SDM收到层三发的AbafActivateSDM消息，但其中参数不对。

解解解决决决措措措施施施查看SDM异常探针信息，能找到是那个参数不对。在信令跟踪中查看AbafActivateSDM消息，找到不对的地方，确认是层三填的不对还是SDM

处理问题。

1.61 DBS_STASTIC_FWDFCHCE_REVCE_LACKFailure Name DBS_STASTIC_FWDFCHCE_REVCE_LACK

Failure Cause When the MS originates a call or is called, the basic channel fails to be set

up due to inadequate forward or reverse CEs.

Failure Analysis The forward and reverse CE resources are inadequate.

Possible Solution 1. Check the failure cause submitted in the fault probe.

2. Verify that there are residual forward CEs in the RB_FWDCE list,

meaning the CEs with status position of 0 (INDEX is 0-31).

3. Verify that there are residual reverse CEs in the RB_REVCE list,

meaning the CEs with status position of 0 (INDEX is 64-95).

4. Verify that the channel board does not block the CE.

失失失败败败原原原因因因值值值 DBS_STASTIC_FWDFCHCE_REVCE_LACK

失失失败败败原原原因因因值值值含含含义义义在MS起呼或者被呼时，建立基本信道时由于前向、反向CE不足引起的失败。

1-36



失失失败败败原原原因因因分分分析析析前向、反向CE资源不足。

解解解决决决措措措施施施 1. 查看异常探针里上报的失败原因。2. 查看RB_FWDCE表是否还有剩余的前向CE，即状态位为0的CE

（INDEX为0~31）。3. 查看RB_REVCE表是否还有剩余的反向CE，即状态位为0的CE

（INDEX为64~95）。4. 查看信道板是否闭塞了CE。

1.62 DBS_STASTIC_FWDFCHCE_LACKFailure Name DBS_STASTIC_FWDFCHCE_LACK

Failure Cause When the MS originates a call or is called, the basic channel fails to be set

up due to inadequate forward CEs on the 5K channel board.

Failure Analysis The forward CEs on the 5K channel board are inadequate.

Possible Solution 1. Check the failure causes submitted in the fault probe.

2. Verify that there are residual forward CEs in the RB_FWDCE list.

3. Verify that the channel board does not block the CE.

失失失败败败原原原因因因值值值 DBS_STASTIC_FWDFCHCE_LACK

失失失败败败原原原因因因值值值含含含义义义在MS起呼或者被呼时，建立基本信道时由于5K信道板前向CE不足引起的失败。

失失失败败败原原原因因因分分分析析析前向CE资源不足。

解解解决决决措措措施施施 1. 查看异常探针里上报的失败原因。2. 查看RB_FWDCE表是否还有剩余的前向CE。3. 查看信道板是否闭塞了CE。

1.63 DBS_STAT_WALSHCODE_LACKFailure Name DBS_STAT_WALSHCODE_LACK

Failure Cause When the MS originates a call or is called, resource distribution fails due to

WALSH CODE distribution failure when the basic channel is being set up.

Failure Analysis No WALSH CODE is available under the carrier.


2. Use the probe to check whether there is free resource in WALSH CODE.

失失失败败败原原原因因因值值值 DBS_STAT_WALSHCODE_LACK

1-37



失失失败败败原原原因因因值值值含含含义义义在MS起呼或者被呼时，建立基本信道的时候WALSHCODE分配失败导致分配资源失败。

失失失败败败原原原因因因分分分析析析该载扇下没有可用的WALSHCODE。

解解解决决决措措措施施施 1. 查看异常探针里上报的失败原因。2. 用探针查看WALSHCODE是否还有空闲资源。

1.64 DBS_STAT_UID_LACKFailure Name DBS_STAT_UID_LACK

Failure Cause When the MS originates a call or is called, resource distribution fails due

to UID distribution failure when the basic channel is being set up by the

IP platform.

Failure Analysis There is no available broadband under the sector or failure occurs in

bandwidth distribution.


2. Use the probe to check whether the LeftBandWidth field in the R_UID

list is larger than 9.

失失失败败败原原原因因因值值值 DBS_STAT_UID_LACK

失失失败败败原原原因因因值值值含含含义义义在MS起呼或者被呼时，IP平台在建立基本信道的时候UID分配失败导致分配资源失败。

失失失败败败原原原因因因分分分析析析该载扇下没有可用的带宽或者分配带宽失败。

解解解决决决措措措施施施 1. 查看异常探针里上报的失败原因。2. 用探针查看R_UID表的LeftBandWidth字段是否大于9。

1.65 DBS_STAT_NO_RESOURCE_LACKFailure Name DBS_STAT_NO_RESOURCE_LACK

Failure Cause The failure is not caused by inadequate resource.

Failure Analysis This is the default error code of database resource distribution. It indicates

a data error or parameter error in a list in the system.

Possible Solution Check the failure causes submitted in the fault probe.

失失失败败败原原原因因因值值值 DBS_STAT_NO_RESOURCE_LACK

失失失败败败原原原因因因值值值含含含义义义不是由于资源不足引起的失败原因。

1-38



失失失败败败原原原因因因分分分析析析该错误原因码是数据库资源分配的默认的错误码。出现这个错误码，一般是其中某个表的数据错误或者参数错误。

解解解决决决措措措施施施查看异常探针里上报的失败原因。

1.66 FCH_NUMBER_TWOFailure Name FCH_NUMBER_TWO

Failure Cause When a supplementary channel is being set up, the subscriber has two

basic data channels.

Failure Analysis The subscriber is in semi soft handoff status.

Possible Solution 1. As it is stipulated, setting up a supplementary channel is not permitted

when the subscriber is in semi soft handoff status. The BTS resource

distribution error has no influence.

2. Check the DSPM and RCM to solve the problem of originating the

supplementary channel setup in semi soft handoff status.

失失失败败败原原原因因因值值值 FCH_NUMBER_TWO

失失失败败败原原原因因因值值值含含含义义义建立补充信道时，用户存在两条数据基本信道。

失失失败败败原原原因因因分分分析析析用户正处于半软切换状态。

解解解决决决措措措施施施 1. 按照约定，用户半软切换状态不允许建立补充信道，BTS资源分配返回错误没有什么影响。

2. 请DSPM和RCM解决为什么半软切换状态仍然发起补充信道建立。

1.67 ARRIVE_TIME_ERRORFailure Name ARRIVE_TIME_ERROR

Failure Cause During supplementary channel confirmation, there is not enough time to

configure the channel board before the supplementary channel start time.

Failure Analysis l The link delay on the Abis port is too long.

l The clocks of the BTS and the BSC are inconsistent.

Possible Solution 1. Solve the clock problem of the BTS and the BSC.

2. Optimize the link delay on the Abis port.

失失失败败败原原原因因因值值值 ARRIVE_TIME_ERROR

失失失败败败原原原因因因值值值含含含义义义补充信道确认时，距离补充信道开始时间已经来不及配置信道板。

1-39



失失失败败败原原原因因因分分分析析析 l Abis口链路延迟过大。l BTS和BSC时钟不一致。

解解解决决决措措措施施施 1. 解决BTS和BSC时钟问题。2. 优化Abis口链路延迟抖动。

1.68 NO_SYSTEM_TIMEFailure Name NO_SYSTEM_TIME

Failure Cause When the supplementary channel resources are being reserved, the CCM

DBS has no system time.

Failure Analysis l The HIRS platform does not send the system time to the CCM because

of instantaneous CHM failure.

l The IP platform SCS does not send the system time to the DBS.

Possible Solution Locate the failure cause by checking the fault probe, and then troubleshoot

accordingly.

失失失败败败原原原因因因值值值 NO_SYSTEM_TIME

失失失败败败原原原因因因值值值含含含义义义补充信道资源预留时，CCM DBS没有系统时间。

失失失败败败原原原因因因分分分析析析该失败原因一般在系统复位过程中出现，主要原因有：l HIRS平台可能CHM瞬时故障没有给CCM发送系统时间。l IP平台SCS没有给DBS发送系统时间。


1.69 NO_AVAILABLE_REV_CEFailure Name NO_AVAILABLE_REV_CE

Failure Cause When a reverse supplementary channel is being set up, no reverse CE

is available.

Failure Analysis CE resources are inadequate.

Handling Measure Expand the capacity.

失失失败败败原原原因因因值值值 NO_AVAILABLE_REV_CE

失失失败败败原原原因因因值值值含含含义义义反向补充信道建立时没有可用的反向CE。

失失失败败败原原原因因因分分分析析析 CE不足。

解解解决决决措措措施施施需要扩容。

1-40



1.70 FO_NOT_ENOUGHFailure Name FO_NOT_ENOUGH

Failure Cause When a reverse complementary channel is being set up, no frame offset

is available.


1. Inadequate frame offset because the frame offset of the reverse

supplementary channel is the same as the FCH.

2. The FCH has more data on the same frame offset, and reverse

supplementary channels have been set up.

Handling Measure Expand the capacity.

失失失败败败原原原因因因值值值 FO_NOT_ENOUGH

失失失败败败原原原因因因值值值含含含义义义反向补充信道建立时没有可用的帧偏置。

失失失败败败原原原因因因分分分析析析帧偏置不足：因为反向补充信道帧偏置和FCH相同，可能是同一帧偏置上的数据FCH较多，而且都建立了反向补充信道。


1.71 CE_NOT_ENOUGHFailure Name CE_NOT_ENOUGH

Failure Cause No forward supplementary channel CE is available when a forward

supplementary channel is being set up.

Failure Analysis Too many forward supplementary channels are set up and forward

supplementary channel CEs are insufficient.

Possible Solution Capacity expansion is required.

失失失败败败原原原因因因值值值 CE_NOT_ENOUGH

失失失败败败原原原因因因值值值含含含义义义前向补充信道建立时没有可用的前向补充信道CE。

失失失败败败原原原因因因分分分析析析前向补充信道建立较多，导致前向补充信道CE不足。


1.72 WALSHCODE_NOT_ENOUGHFailure Name WALSHCODE_NOT_ENOUGH

1-41



Failure Cause No Walsh code is available when a forward supplementary channel is being

set up.

Failure Analysis Too many forward supplementary channels are set up and the Walsh code

is insufficient.


失失失败败败原原原因因因值值值 WALSHCODE_NOT_ENOUGH

失失失败败败原原原因因因值值值含含含义义义前向补充信道建立时没有可用的Walsh码。

失失失败败败原原原因因因分分分析析析前向补充信道建立较多，导致Walsh码不足。


1.73 BEFORE_CPSFailure Name BEFORE_CPS

Failure Cause Application for forward supplementary channels is too early during the

process of scheduling and continuous transmission.

Failure Analysis The possible failure cause is as follows: The system clocks of the BTS

and the BSC are inconsistent.

Handling Measure Verify that the GCM board has no alarm.

失失失败败败原原原因因因值值值 BEFORE_CPS

失失失败败败原原原因因因值值值含含含义义义前向补充信道调度续传过程中申请的太早。

失失失败败败原原原因因因分分分析析析 BTS和BSC系统时钟不一致。

解解解决决决措措措施施施检查GCM单板，确认无告警。

1.74 UIDWIDTH_NOT_ENOUGHFailure Name UIDWIDTH_NOT_ENOUGH

Failure Cause UID bandwidth is insufficient during resource distribution of supplementary

channels.

Failure Analysis Abis bandwidth is insufficient.


失失失败败败原原原因因因值值值 UIDWIDTH_NOT_ENOUGH

1-42



失失失败败败原原原因因因值值值含含含义义义补充信道资源分配时UID带宽不足。

失失失败败败原原原因因因分分分析析析 Abis带宽不足。


1.75 RS_NOT_EXISTFailure Name RS_NOT_EXIST

Failure Cause Records to which the RS list corresponds are unavailable during resource

distribution of supplementary channels.

Failure Analysis This failure is caused by the scheduling algorithm of supplementary

channels.


失失失败败败原原原因因因值值值 RS_NOT_EXIST

失失失败败败原原原因因因值值值含含含义义义补充信道资源分配时RS表对应的记录不存在。

失失失败败败原原原因因因分分分析析析补充信道调度算法引起，一个补充信道用户A因为调度需要预约到另一个补充信道用户B上，但后来用户A数据FCH释放，补充信道建立时实际上FCH已经不存在，所以RS表中无对应记录。

解解解决决决措措措施施施因数据用户自己释放引起预约的补充信道无法建立，属于正常的场景。如果不属于上述场景或大量出现,请联系中兴通讯。

1.76 ALLOCATE_UID_ERRORFailure Name ALLOCATE_UID_ERROR

Failure Cause UID distribution fails during resource distribution of supplementary channels.

Failure Analysis Instantaneous UID failure.

Possible Solution Stabilize the UID status.

失失失败败败原原原因因因值值值 ALLOCATE_UID_ERROR

失失失败败败原原原因因因值值值含含含义义义补充信道资源分配时分配UID失败。

失失失败败败原原原因因因分分分析析析 UID瞬时故障。

解解解决决决措措措施施施稳定UID的状态。

1-43



1.77 BSC_CICFROMMSC_ERR失失失败败败原原原因因因值值值 BSC_CICFROMMSC_ERR

失失失败败败原原原因因因值值值含含含义义义 A口MSC指配的CIC错误。

失失失败败败原原原因因因分分分析析析会导致这个失败的原因是MSC指配的CIC在BSC侧找不到。

解解解决决决措措措施施施检查A口配置。

Failure Name BSC_CICFROMMSC_ERR

Failure Cause The CIC that is assigned by the MSC to the A interface is incorrect.

Failure Analysis The CIC that is assigned by the MSC is not available on the BSC side.

Handling Measure Check the A interface configuration.

1.78 HO_STAT_SERVICE_FORBIDFailure Name HO_STAT_SERVICE_FORBID

Failure Cause A service forbids the call to access the carrier.

Failure Analysis During call access, the data service forbids it to access the voice carrier or

the voice service forbids it to access the data carrier.

Handling Measure For voice service, check switch 78 and the attribute of the carrier to be

accessed. For data service, check switch 80 and the attribute of the carrier

to be accessed.

1.79 ERR_SPS_RLSA_RCM_DBAccFail_FCHResourceAllocate

Failure Name ERR_SPS_RLSA_RCM_DBAccFail_FCHResourceAllocate

Failure Cause When the MS originates a call or is called, it fails to invoke the database

interface resource during FCH setup.

Failure Analysis l Input parameter mistake of the database.

l CE resource is not enough or abnormal.

l Walsh codes are not enough.

l FO is not enough.

l UID is not enough.

1-44



Possible Solution 1. Check the failure cause in the EV_S_AbisdrBTSSeupAck message

reported in signal tracing.

l 0x5064: forward channel CE is not enough.

l 0x5065: reverse CE is not enough.

l 0x5066: forward channel CE and reverse CE are not enough.

2. After confirming the failure cause, verify that the CHM board is normal

(the chip-set and CE are normal).

3. If the CHM and CCM are normal, it is possible that the resource is

hung up.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_DBAccFail_FCHResourceAllocate

失失失败败败原原原因因因值值值含含含义义义在MS起呼或者被呼时，在建立基本信道时调用数据库接口分配资源失败。

失失失败败败原原原因因因分分分析析析 l 调用数据库的入参错误。l CE资源不足或者异常。l Walsh码不足。l 帧偏置FO不足。l UID不足。

解解解决决决措措措施施施 1. 查看信令跟踪里上报的EV_S_AbisdrBTSSeupAck消息中的失败小区的失败原因。l 0x5064：表示前向基本信道CE不足。l 0x5065：表示反向CE不足。l 0x5066：表示前向基本信道、反向CE均不足。

2. 查明失败原因后，查看信道板是否异常（芯片状态是否正常，CE是否被闭塞）。

3. 如果CHM正常，CCM也正常，可能是资源吊死，严重故障。

1.80 ERR_SPS_RLSA_RCM_PCALL_OtherReason_CEC_REMOVEREQ

Failure Name ERR_SPS_RLSA_RCM_PCALL_OtherReason_CEC_REMOVEREQ

Failure Analysis During the call process, the CHM board requests to release the current

call after detecting no frame in the forward channel (the default time is 6

s), meaning the CHM does not receive the SDU forward frame, and the

procedure is released. The possible failure causes are as follows:

l The IP or MAC value is invalid.

l Invalid Key value results in searching table address error.

l The channel table position is invalid.

l The SDM does not set up a leg.

l The DSP on the VTC board has a problem.

1-45



Possible Solution 1. Verify that the SDM has set up a leg.

2. Verify that the IP and MAC values are correct.

3. If this problem occurs frequently, the probable cause is that the DSP

has a problem.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_PCALL_OtherReason_CEC_REMOVEREQ

失失失败败败原原原因因因分分分析析析这个失败的原因是在呼叫过程中，信道板在检测到前向6 s无帧后请求释放当前的呼叫。也就是说CHM在6s内没有收到SDU的前向帧（不论是什么速率的帧，都没有收到），都会引发释放流程。导致前向无帧的原因如下：l IP或者MAC值无效。l Key值无效导致查找表地址错误。l 通道表无效位置。l SDM没有建腿。l VTC单板上与本次呼叫相关的DSP故障。

解解解决决决措措措施施施 1. 查看信令中有无SDM建腿消息。2. 查看IP和MAC值设置是否正确。3. 如果频繁出现此类失败，可能是DSP故障。

1.81 ERR_SPS_RLSA_RCM_FCH_TimerExpired_TconnExpired

Failure Name ERR_SPS_RLSA_RCM_FCH_TimerExpired_TconnExpired

Failure Analysis During call setup, the Abis interface timer expires when resources are being

set up. This starts the call release procedure and results in call failure.

The timer is triggered after the BTS assigns the radio resource and service

address and informs the BSC. If a BSC Ack message is not received before

the timer expires, the BTS starts the release procedure.

The reason for the BTS not receiving the Ack message is link and message

blocking and wrong message contents on the BTS.

Possible Solution 1. Verify that the Abis link is normal.

2. Verify that the parameters (such as cell information in tAbisConnectInfo)

in the AbisdrConnect message carried by the BTS to the BSC are

correct.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_FCH_TimerExpired_TconnExpired

1-46



失失失败败败原原原因因因分分分析析析在呼叫建立过程中，建立资源时Abis口定时器超时，引发了呼叫释放流程，导致呼叫失败。这个定时器Tconnb时长为4 s，是BTS侧分配完无线资源以及业务地址，并通知BSC侧后触发的，如果在定时器到时前，没有收到BSC的Ack消息，则BTS侧发起释放流程。BTS侧没有收到Ack消息的原因除了链路和消息拥塞外，还可能是BTS

侧的消息内容有误。

解解解决决决措措措施施施 1. 检查Abis链路是否通信正常。2. 检查BTS侧带给BSC的AbisdrConnect消息中参数是否正确（主要和

AbisdfBTSSetup相比较），主要注意的参数有：tAbisConnectInfo里有关小区的信息。

1.82 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_AddChannelFail

Failure Name ERR_SPS_RLSA_RCM_FSCH_FunCallFail_AddChannelFail

Failure Analysis During call setup, this failure occurs when the IP platform BTS adds a

channel table. The possible reason is that too many channel tables are

added at one time.

Handling Measure 1. If the problem occurs in ordinary voice, verify that the channel table

is not hung up.

2. If the problem occurs during data service procedure, it is normal.

3. If no call adds many channel tables at one time (ordinary voice), it

indicates that the resource is hung up. Contact the local ZTE office.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_AddChannelFail

失失失败败败原原原因因因分分分析析析在呼叫建立的过程中，IP平台BTS侧增加通道表的时候出现失败，可能是同一时间添加大量的通道表导致，一般出现在数据业务补充信道的建立过程中。如果是正常普通语音也出现，检查是否是通道表吊死。

解解解决决决措措措施施施 1. 如果是数据业务过程中出现，属于正常情况。2. 如果没有同一时间一个呼叫大量增加通道表（普通语音），那么是资

源吊死，请联系中兴通讯。

1.83 ERR_SPS_RLSA_RCM_FSCH_TimerExpired_TfschNotifyExpired

Failure Name ERR_SPS_RLSA_RCM_FSCH_TimerExpired_TfschNotifyExpired

1-47



Failure Cause During data service, the timer expires before the notification message of

database resource reservation is received.

Handling Measure Verify that the voice traffic is not too heavy. If this case occurs frequently,

contact the local ZTE office.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_FSCH_TimerExpired_TfschNotifyExpired

失失失败败败原原原因因因分分分析析析数据业务中，等待数据库资源预留的通知消息超时。

解解解决决决措措措施施施 1. 检查是否话务量比较大。2. 如果大量出现，请联系中兴通讯。

1.84 ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_SameTimeCellInSameGroupInDiffSetupFlow

Failure Name ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Sam

eTimeCellInSameGroupInDiffSetupFlow

Failure Analysis During a call, multiple cells in the same leg are not allowed to set up FCHs

in multiple procedures. This results in resource setup failure.

Possible Solution It is normal. The cause is code limitation.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Sam

eTimeCellInSameGroupInDiffSetupFlow

失失失败败败原原原因因因分分分析析析呼叫过程中，不支持同一条腿内的多个小区同时在多个流程中建立FCH，根据约定此次资源建立过程失败。

解解解决决决措措措施施施正常情况，属于代码限制。

1.85 ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_MAbisdMsgDispatch

Failure Name ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_MAbisdMsgD

ispatch

Failure Analysis During call setup, the main RCM process fails to forward messages to the

Handler process.

l All subprocesses of the RCM are busy.

l The RCM has no idle Handler process.

1-48



Possible Solution If the number of calls at one time is more than the upper limit of process

quantity, the failure is normal (upper limits: HIRS CCM is 300, BDM is

75, and IP CCM is 600). If the number of calls is fewer and this problem

occurs, the probable cause is that the OSS has changed the upper limit of

processes. In this case, contact the local ZTE office.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_MAbisdMsgD

ispatch

失失失败败败原原原因因因分分分析析析呼叫建立时，RCM主进程向Handler进程转发消息失败，导致失败的原因为：l RCM的所有子进程都处于忙状态。l RCM没有空闲的Handler进程。

解解解决决决措措措施施施这个失败的出现如果是由于同一时间呼叫数超过进程数上限导致，那么是正常情况（上限：HIRS CCM 300，BDM 75，IP CCM 600）。如果少量呼叫也有这个异常，可能是OSS将进程上限值修改，请联系中兴通讯处理。

1.86 ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_ServiceRestrict

Failure Name ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Ser

viceRestrict

Failure Analysis During handoff, because the service type for handoff is among the restricted

service of the destination cell, the cell handoff fails. The service types

include voice, data, PTT enhanced calls, and private calls.

Handling Measure In OMC configuration management, cancel the service restriction on the

cell node.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Ser

viceRestrict

失失失败败败原原原因因因分分分析析析呼叫切换时，由于进行切换的业务是在业务限制的业务范围内，导致该小区切换加失败。该失败原因的业务可以包括普通语音，数据业务，PTT

增强组呼和私密呼。

解解解决决决措措措施施施正常情况，该业务在切换加的小区是受到业务限制的，在要切换加的小区不允许进行该业务；如果要进行该业务，在网管小区节点中，把该业务限制取消即可。

1-49



1.87 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_BurstRequest_ConnInSetup

Failure Name ERR_SPS_RLSA_RCM_FSCH_FunCallFail_BurstRequest_ConnInSetup

Failure Analysis During forward supplementary channel setup, there is another concurrent

setup flow, causing the channel setup failure.

Handling Measure Finish setting up the previous scheduling before starting the next one.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_BurstRequest_ConnInSetup

失失失败败败原原原因因因分分分析析析建立前向补充信道过程中，并行的建立流程导致建立失败。

解解解决决决措措措施施施正常情况，上一个调度没有建立成功，不允许开始下一个调度。

1.88 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstRequest_SaveToGroupedCellInfoSet_CellNumIsZero

Failure Name ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstRequest_SaveToGroup

edCellInfoSet_CellNumIsZero

Failure Analysis During reverse supplementary channel setup, no valid cell information is

available, causing the channel setup failure.

Handling Measure In setting up the reverse supplementary channel, the cells corresponding

to the CIs specified in the BurstRequest message do not exist, that is, the

cells are invalid. If the failure occurs frequently, contact the local office

of ZTE Corporation.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstRequest_SaveToGroup

edCellInfoSet_CellNumIsZero

失失失败败败原原原因因因分分分析析析建立反向补充信道时，没有有效的小区信息导致失败。

解解解决决决措措措施施施建立反向补充信道时，BurstRequest消息指定的CI都不存在对应的小区，即都是无效的小区。如果大量出现，请联系中兴通讯。

1-50



1.89 ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft_AbisdfBurstCommit

Failure Name ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft

_AbisdfBurstCommit

Failure Analysis During the semi-soft handoff, supplementary channel setup is rejected.


失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft

_AbisdfBurstCommit

失失失败败败原原原因因因分分分析析析半软切换过程中，拒绝建立补充信道。

解解解决决决措措措施施施正常情况，无需处理。

1.90 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_AddChannelFail

Failure Name ERR_SPS_RLSA_RCM_RSCH_FunCallFail_AddChannelFail

Failure Analysis During call setup, adding a channel table on the BTS side fails. The

probable cause is that a large number of channel tables are being added

at the same time. The problem normally occurs during the data service

supplementary channel setup process. If the problem occurs for the voice

service, the probable cause is that the channel table is suspended.

Handling Measure 1. If the problem occurs during data services, it is normal.

2. If the problem occurs during common voice services, and the problem

is not caused by adding a large number of channel tables at the same

time, then the cause is that the resources are suspended. In this case,

contact the local office of ZTE Corporation.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_AddChannelFail

失失失败败败原原原因因因分分分析析析在呼叫建立的过程中，IP平台BTS侧增加通道表的时候出现失败，可能是同一时间添加大量的通道表导致，一般出现在数据业务补充信道的建立过程中。如果是正常普通语音也出现，检查是否是通道表吊死。

解解解决决决措措措施施施 1. 如果是数据业务过程中出现，属于正常情况。2. 如果没有同一时间一个呼叫大量增加通道表（普通语音），那么是资

源吊死，请联系中兴通讯。

1-51



1.91 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_GetConnRecordByGroupId

Failure Name ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_GetConnRe

cordByGroupId

Failure Analysis In the case of data service, after the BurstCommit message is received,

the corresponding leg fails to be found, causing the failure in setting up

the supplementary channel. The cause is that the message is received

after timeout, and the leg has been released. The Abis interface delay may

cause the problem.

Handling Measure If the problem occurs during data services, it is normal.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_GetConnRe

cordByGroupId

失失失败败败原原原因因因分分分析析析数据业务中，在收到BurstCommit消息后，找不到对应的腿导致建立补充信道失败。原因是超时后收到该消息，腿已经释放。Abis口延时会导致该情况发生。

解解解决决决措措措施施施数据业务中出现该失败，是正常情况。

1.92 BSC_NO_CICFailure Name BSC_NO_CIC

Failure Cause No CIC (ground circuit) resource is available in the system.

Failure Analysis No CIC resource available: CIC resource configuration error, CIC resource

status is abnormal or insufficient CIC resource.

Possible Solution 1. Verify that the ground circuit (CIC) configuration of port A is correct.

l Verify that the PCM configuration at port A is consistent with the

PCM No. configuration on the MSS.

l Verify that the trunk configuration is consistent with the timeslot

configuration on the MSS.

l Verify that the DT board to which the CIC corresponds is correctly

attributed to the RMP module.

2. Verify that the DT board to which the CIC corresponds operates properly

and its version is correct.

3. Verify that the E1 physical connection to which the CIC corresponds is

correct.

4. Verify that the CIC resource is manually blocked in dynamic

management.

1-52



5. Verify that the CIC resource quantity meets the requirements of traffic

capacity.

失失失败败败原原原因因因值值值 BSC_NO_CIC

失失失败败败原原原因因因值值值含含含义义义系统无可用的CIC（地面电路）资源。

失失失败败败原原原因因因分分分析析析无可用的CIC资源：CIC资源配置错误，CIC资源状态异常或CIC资源不足。

解解解决决决措措措施施施 1. 检查A口地面电路（CIC）配置是否正确：l 检查A口PCM配置是否正确，注意与交换侧PCM编号配置一致。l 检查PCM中继配置是否正确，注意与交换侧时隙配置一致。l 检查CIC对应的DT单板是否正确的归属到RMP模块。

2. 检查CIC对应的DT单板是否运行正常，版本正确。3. 检查CIC对应的E1物理连接是否正确。4. 动态管理中检查CIC资源是否人工闭塞。5. 检查CIC资源数量是否满足话务容量的需要。

1.93 POWER_NOT_ENOUGHFailure Name POWER_NOT_ENOUGH

Failure Cause Inadequate power.

Failure Analysis l Carrier power surpasses the threshold for supplementary channel

setup.

l Residual power is unable to set up a forward supplementary channel

with a rate of over 2X.

l Subscriber radio condition is relatively poor, and the required power

surpasses the maximum transmission power of the supplementary

channel set by the OMC.


失失失败败败原原原因因因值值值 POWER_NOT_ENOUGH

失失失败败败原原原因因因值值值含含含义义义功率不足。

失失失败败败原原原因因因分分分析析析 l 载扇功率超过补充信道建立门限。l 剩余功率无法建立2X以上速率的前向补充信道。l 用户无线条件比较差，需要的功率超过OMC设置的补充信道最大

发射功率。


1-53



1.94 BSC_NO_SEFailure Name BSC_NO_SE

Failure Cause No SE resource is available in the system.

Failure Analysis No SE resource available: SDU configuration error, SE resource status is

abnormal, or SE resource is insufficient.

Possible Solution 1. Verify that the 1XSDU board is correctly configured.

2. Verify that the SDU board operates properly and its version is correct.

3. If the AP interface is installed in the RTP, verify that the SDU virtual

address configuration is correct.

4. Verify that the status of the daughter card of the SDU board and of

INDEX is normal in dynamic management.

5. Verify that the SE resource quantity meets the requirements of traffic

capacity.

失失失败败败原原原因因因值值值 BSC_NO_SE

失失失败败败原原原因因因值值值含含含义义义系统无可用的SE资源。

失失失败败败原原原因因因分分分析析析无可用的SE资源：SDU配置错误，SE资源状态异常或SE资源不足。

解解解决决决措措措施施施 1. 检查是否正确的配置了1XSDU单板。2. 检查SDU单板是否运行正常，版本正确。3. 对于AP接口RTP内置的情况，检查SDU虚地址是否正确配置。4. 动态管理中检查SDU单板的子卡及INDEX是否状态正常。5. 检查SE资源数量是否满足话务容量的需要。

1.95 BSC_NO_VEFailure Name BSC_NO_VE

Failure Cause No VE resource is available in the system.

Failure Analysis No VE resource available: VTC configuration error, abnormal VE resource

status, or insufficient VE resource.

Possible Solution 1. Verify that the resource frame where the CIC is located is configured

correctly with corresponding quantity of VTC boards.

2. Verify that the VTC board operates properly and the CPU/DSP version

is correct.

3. Verify that the VTC board and INDEX status is normal in dynamic

management.

4. Verify that the VE resource quantity meets the requirements of traffic

capacity.

1-54



失失失败败败原原原因因因值值值 BSC_NO_VE

失失失败败败原原原因因因值值值含含含义义义系统无可用的VE资源。

失失失败败败原原原因因因分分分析析析无可用的VE资源：VTC配置错误，VE资源状态异常或VE资源不足。

解解解决决决措措措施施施 1. 检查CIC所在资源框是否都正确的配置了相应数量的VTC单板。2. 检查VTC单板是否运行正常，CPU/DSP版本正确。3. 动态管理中检查VTC单板及INDEX是否状态正常。4. 检查VE资源数量是否满足话务容量的需要。

1.96 BSC_NO_IWFFailure Name BSC_NO_IWF

Failure Cause No IWF resource is available in the system.

Failure Analysis IWF resource unavailable: IWF configuration error, abnormal IWF resource

status, or insufficient IWF resource.

Handling Measure 1. Verify that the IWFB board is correctly configured, especially in the

case that the CIC is not selected.

2. Verify that the IWFB board operates properly and the CPU/DSP version

is correct.

3. Verify that the status of the IWFB board and INDEX is normal in

dynamic management.

4. Verify that the IWF resource quantity meets the requirements of traffic

capacity.

失失失败败败原原原因因因值值值 BSC_NO_IWF

失失失败败败原原原因因因值值值含含含义义义系统无可用的IWF资源。

失失失败败败原原原因因因分分分析析析无可用的IWF资源：IWF配置错误，IWF资源状态异常或IWF资源不足。

解解解决决决措措措施施施 1. 检查是否正确的配置了IWFB单板，特别在非优选CIC的情况下，检查CIC所在资源框是否都配置了IWFB单板。

2. 检查IWFB单板是否运行正常，CPU/DSP版本是否正确。3. 动态管理中检查IWFB单板及INDEX是否状态正常。4. 检查IWF资源数量是否满足话务容量的需要。

1.97 BSC_DSPM_NO_INSTANCEFailure Name BSC_DSPM_NO_INSTANCE

Failure Cause No DSPM example is available in the system.

1-55



Failure Analysis DSPM example unavailable: DSPM configuration error, DSPM status

abnormal, or insufficient DSPM examples.

Possible Solution 1. Verify that the DSPM module is correctly configured, and a proper

quantity of DSPM examples is configured.

2. Verify that the MP daughter card where the DSPM module is located

operates properly and its version is correct.

3. Check the module list in the probe view, and verify that the DSPM is in

normal status.

4. Verify that the quantity of DSPM examples meet the requirements of

traffic capacity.

失失失败败败原原原因因因值值值 BSC_DSPM_NO_INSTANCE

失失失败败败原原原因因因值值值含含含义义义系统无可用的DSPM实例。

失失失败败败原原原因因因分分分析析析无可用的DSPM实例：DSPM配置错误，DSPM状态异常或DSPM实例不足。

解解解决决决措措措施施施 1. 检查是否正确的配置了DSPM模块，并且配置了相应数量的DSPM

实例。2. 检查DSPM模块所在MP子卡是否运行正常，版本正确。3. 探针视图中查看模块表，检查DSPM模块是否状态正常。4. 检查DSPM实例数量是否满足话务容量的需要。

1.98 BSC_NO_RTPPORTFailure Name BSC_NO_RTPPORT

Failure Cause No RTPPORT resource is available in the system. This failure cause is

submitted only in the case of external RTP.

Failure Analysis Unavailable RTPPORT resource: configuration error, abnormal status of

RTP port, or insufficient RTPPORT resource.

Handling Measure 1. In the case of external RTP, verify that the IPI board and RTP port are

correctly configured.

2. Verify that the IPI board where RTP port is located operates properly


3. Verify that the status of RTPPORT resource is normal during dynamic

management.

4. Verify that the RTPPORT resource quantity meets the requirements of

traffic capacity.

失失失败败败原原原因因因值值值 BSC_NO_RTPPORT

失失失败败败原原原因因因值值值含含含义义义系统无可用的RTPPORT资源（此失败原因只在RTP外置情况下上报）。

1-56



失失失败败败原原原因因因分分分析析析无可用的RTPPORT资源：RTP端口配置错误、状态异常或RTPPORT

资源不足。

解解解决决决措措措施施施 1. RTP外置情况下，检查是否正确的配置了IPI单板及RTP端口。2. 检查RTP端口所在IPI单板是否运行正常，版本正确。3. 动态管理中检查RTPPORT资源是否状态正常。4. 检查RTPPORT资源数量是否满足话务容量的需要。

1.99 BSC_NO_VALID_RMPFailure Name BSC_NO_VALID_RMP

Failure Cause No RMP module is available in the system.

Failure Analysis Unavailable RMP module: RMP module configuration error, or abnormal

RMP status.

Possible Solution 1. Verify that the RMP module is correctly configured in the system.

2. Verify that the MP daughter card where the RMP module is located


3. Check the module list in the probe view, and verify that the RMP module

status is normal.

失失失败败败原原原因因因值值值 BSC_NO_VALID_RMP

失失失败败败原原原因因因值值值含含含义义义系统无可用的RMP模块。

失失失败败败原原原因因因分分分析析析无可用的RMP模块：RMP模块配置错误或RMP状态异常。

解解解决决决措措措施施施 1. 检查系统是否正确的配置了RMP模块。2. 检查RMP模块所在MP子卡是否运行正常，版本正确。3. 探针视图中查看模块表，检查RMP模块是否状态正常。

1.100 ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MCSHConstructAmdfFCHSetup

Failure Name ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MC

SHConstructAmdfFCHSetup

Failure Analysis During call setup or handoff, when channel resources are configured, an

error occurs in the construction of the channel resource configuration

message. The problem normally occurs on the cell where a control channel

is not configured.

1-57



Handling Measure On the OMC configuration management, verify that the control channel is

configured for the cell (sector) with the problem.

If the control channel is not configured, configure the control channel and

synchronize data.

If the control channel is configured, contact the local ZTE office.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MC


失失失败败败原原原因因因分分分析析析呼叫建立或切换过程中，配置信道资源时构造信道资源配置消息出现异常。

解解解决决决措措措施施施该失败原因多见于建立呼叫的小区的控制信道未配置的情况，请在网管OMC配置管理中检查产生上述问题的小区（载扇）是否配置控制信道。如果未配置，增加导频信道的配置，并同步配置数据至网元设备。若产生上述问题的小区（载扇）已经配置控制信道，请联系中兴通讯处理。

1.101 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_MHandlerAbisdfBTSSetup

Failure Name ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_

MHandlerAbisdfBTSSetup

Failure Analysis During call setup or handoff, an error occurs in handling the call setup or

handoff message .

Handling Measure 1. In the case that the BTS is in graceful degradation mode, when the BTS

receives the call setup or handoff message from the BSC, the BTS

reports the failure message. It is a normal case.

2. The RCM does not support concurrent setup flows. If the RCM receives

another call setup or handoff message during the leg setup process, the

RCM reports the failure message. If the problem occurs occasionally,

no troubleshooting is required.

3. If the BSSAP or DSPM handoff type is incorrect, the failure message is

also reported. If the problem occurs occasionally, no troubleshooting

is required.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_


失失失败败败原原原因因因分分分析析析呼叫建立或切换过程中，处理呼叫建立或切换消息出现异常。

1-58



解解解决决决措措措施施施 1. 如果基站为故障弱化模式，收到BSC的呼叫建立或切换消息，会报该失败，此种属于正常情况。

2. RCM不支持并行建立流程。如果在腿的建立过程中，又收到呼叫建立或切换消息，也可能会报该原因的失败，少量无需处理。

3. BSSAP或DSPM带了不正确的切换的类型，也会上报此失败。

1.102 ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAck_SoftHandoffLegNoInvalid

Failure Name ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAc

k_SoftHandoffLegNoInvalid

Failure Analysis During call setup or handoff process, the leg number leg in the

AbisdfConnectAck message exceeds the maximum allowed value. A call

supports up to 12 legs. If the leg number exceeds 12, a call failure may

be caused.

Handling Measure If the problem occurs frequently, contact the local representative office of

ZTE Corporation.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAc


失失失败败败原原原因因因分分分析析析呼叫建立或切换过程中，AbisdfConnectAck消息中腿号超过最大限制值导致失败。

解解解决决决措措措施施施一个呼叫最多支持12条腿，如果腿号超过12，则会导致呼叫失败。如果大量出现，请联系中兴通讯。

1.103 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_MCDHSaveToCommonData

Failure Name ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_

MCDHSaveToCommonData

Failure Analysis An error occurs in saving data during call setup or handoff handling.

1. The handoff type in the call setup or handoff message is incorrect.

2. The CI and frequency point in call setup or handoff message are

incorrect, so the carrier cannot be found based on the CI and frequency

point.

1-59



Handling Measure If the a few such problems occur, ignore them. If a lot of such problems

occur, contact the local office of ZTE Corporation.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_


失失失败败败原原原因因因分分分析析析呼叫建立或切换过程中，处理呼叫建立或切换时保存数据异常。

解解解决决决措措措施施施 1. 呼叫建立或切换消息带了不正确的切换类型。2. 呼叫建立或切换消息带了不正确的CI和频点，导致无法根据CI和频点

找到载频。如果大量出现，请联系中兴通讯。

1.104 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CE_IN_USED

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CE_IN_USED

Failure Cause During FCH setup, the CE is hung up and results in FCH channel setup

failure.

Failure Analysis l The CPU usage ratio of the CHM board is too high.

l An UB alarm exists in the CHM board.

l SDH transmission at the BTS side is not stable.

l Too many CSM daughter cards installed on a single CHM board

(IP-BTS supports 6, and HIRS BTS supports 4 chipsets).

l The CES code is abnormal, and the resource is not released.

l The upper level is abnormal and the release is not started.

Possible Solution 1. If the CPU usage ratio is too high, block some CSM daughter cards.

2. Check the SDH transmission.

3. Check the clock module.

4. Allocate some control channels to other boards.

5. If the problem persists, reset the CHM.

失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CE_IN_USED

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES出现CE吊死的现象，导致基本信道建立失败。

失失失败败败原原原因因因分分分析析析会导致这个失败的原因如下：l 信道板的CPU利用率太高。l 信道板上有UB告警。l 该站的传输不稳定。l 信道板上的子卡太多（目前IP支持6片，HIRS支持4片芯片）。l CES代码异常，没有释放资源。l 上层异常，没有发起释放。

1-60



解解解决决决措措措施施施 1. 若信道板的CPU利用率高，则闭塞部分子卡。2. 检查传输。3. 检查时钟模块。4. 部分控制信道分配到其他板上。5. 以上措施不能缓减情况的话，复位CHM。

1.105 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_REJECT

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_REJECT

Failure Cause During FCH setup, after the CEC layer sends the FCH setup message

to the CEM layer, the CEM layer rejects the message, causing the FCH

setup failure.

Failure Analysis l The CPU usage of the CHM is too high.

l UB alarms exist on the CHM.

l There is a problem with the CHM clock.

l There is a problem with the CES code, and the resources are not

released.

l There is an upper-layer problem, and the resources are not released.

Possible Solution 1. If the CPU usage of the CHM is too high, block some daughter cards.


3. Assign specific control channels to the other boards.

4. If the measures above do not work, reset the CHM.

失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_REJECT

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CEC层向CEM层发建立基本信道消息后，CEM层拒绝，导致基本信道建立失败。

失失失败败败原原原因因因分分分析析析会导致这个失败的原因如下：l 信道板的CPU利用率太高。l 信道板上有UB告警。l 信道板时钟异常。l CES代码异常，没有释放资源。l 上层异常，没有发起释放。

解解解决决决措措措施施施 1. 若信道板的CPU利用率高，则闭塞部分子卡。2. 检查时钟模块。3. 部分控制信道分配到其他板上。4. 以上措施不能缓减情况的话，复位CHM。

1-61



1.106 ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_CREATE_PROCESS

Failure Name ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_CREATE_PROCESS

Failure Cause When FCH channel is in set up, process establishment fails.

Failure Analysis l Error occurs when calling the V_OutputBySrc function.

l The version is incorrect.

Possible Solution 1. Solve the lower level problem.

2. Block the faulty CHM board.

失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_CREATE_PROCESS

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，进程创建失败。

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l 调用V_Create函数出错。l 检查版本是否正确。

解解解决决决措措措施施施 1. 解决底层的问题。2. 闭塞有问题的信道板。

1.107 ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_OUTPUT_MSG_TO_CALLHNDL

Failure Name ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_OUTPUT_MSG_TO_

CALLHNDL

Failure Cause In the case of FCH setup, the CallMain process fails to send message to the

Callhandler process.

Failure Analysis The possible causes may be as follows:

l Error occurs when calling the V_OutputBySrc function.

l Version error.

Handling Measure 1. Solve the bottom-layer problem.

2. Block the channel board with the problem.

失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_OUTPUT_MSG_TO_

CALLHNDL

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CallMain进程向Callhandler进程发送消息失败。

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l 调用V_OutputBySrc函数出错。l 检查版本是否正确。

1-62



解解解决决决措措措施施施 1. 解决底层的问题。2. 闭塞有问题的信道板。

1.108 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_RSP_TIMER_OUT

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_RSP_TI

MER_OUT

Failure Cause During FCH setup, after the CEC layer sends the FCH setup message

to the CEM layer, the CEM layer response times out, causing the FCH

setup failure.


l The CPU ultilization of the CHM is too high.

l There exist UB alarms on the CHM.

l There is a problem with the CHM clock.

l There is a problem with the CES code, and the resources are not

released.

l There is an upper-layer problem, and the resources are not released.

Handling Measure 1. If the CPU ultilization of the CHM is too high, block some daughter cards.


3. Assign specific control channels to the other boards.

4. If the above measures do not work, reset the CHM.

失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_RSP_TI

MER_OUT

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CEC层向CEM层发建立基本信道消息后，等待CEM层应答超时，导致基本信道建立失败。

失失失败败败原原原因因因分分分析析析会导致这个失败的原因如下：l 信道板的CPU利用率太高。l 信道板上有UB告警。l 信道板时钟异常。l CES代码异常，没有释放资源。l 上层异常，没有发起释放。

解解解决决决措措措施施施 1. 若信道板的CPU利用率高，则闭塞部分子卡。2. 检查时钟模块。3. 部分控制信道分配到其他板上。4. 以上措施不能缓减情况的话，复位CHM。

1-63



1.109 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_POINTER_NULL

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_POINTER

_NULL

Failure Cause During FCH setup, the structure pointer is a null pointer in the CES

verification channel setup command, causing the FCH channel setup failure.


l The CHM version and CCM version do not match.

l A CES error occurs.

l An upper-layer error occurs.

Handling Measure 1. Make the CHM version and the CCM version consistent.

2. Soft reset the CHM.

3. If the above measures do not work, reset the CCM.

失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_POINTER

_NULL

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带结构指针为空，导致基本信道建立失败。

失失失败败败原原原因因因分分分析析析会导致这个失败的原因如下：l CHM和CCM版本不匹配。l CES出现异常。l 上层出现异常。

解解解决决决措措措施施施 1. 版本一致。2. 软复位CHM。3. 以上措施不能缓减情况的话，复位CCM。

1.110 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_HANDOFF_TYPE

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_HANDOFF

_TYPE

Failure Cause During FCH setup, the handoff type is incorrect in the CES verification

channel setup command, causing the FCH channel setup failure.





1-64






失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_HANDOFF

_TYPE

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数切换类型错误，导致基本信道建立失败。



1.111 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_NUM

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_N

UM

Failure Cause During FCH setup, the number of sectors is incorrect in the CES verification









失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_N

UM

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数扇区数错误，导致基本信道建立失败。

1-65





1.112 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_FWD_RC

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_FWD_RC

Failure Cause During FCH setup, the forward channel RC type is incorrect in the CES

verification channel setup command, causing the FCH setup failure.








失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_FWD_RC

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数前向信道RC类型错误，导致基本信道建立失败。



1.113 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_RC

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_RC

1-66



Failure Cause During FCH setup, the reverse channel RC type is incorrect in the CES









失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_RC

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数反向信道RC类型错误，导致基本信道建立失败。



1.114 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_ID

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_ID

Failure Cause During FCH setup, the sector ID is incorrect in the CES verification channel

setup command, causing the FCH channel setup failure.








失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_ID

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数扇区ID错误，导致基本信道建立失败。

1-67





1.115 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_ISNOT_ACTIVE

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_I

SNOT_ACTIVE

Failure Cause During FCH setup, the sector is not activated in the CES verification channel









失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_I

SNOT_ACTIVE

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数扇区未激活，导致基本信道建立失败。



1-68



1.116 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_EARLIESTPNOFFSET

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_EARLIEST

PNOFFSET

Failure Cause During FCH setup, EPN is incorrect in the CES verification channel setup

command, causing the FCH channel setup failure.








失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_EARLIEST

PNOFFSET

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数EPN值错误，导致基本信道建立失败。



1.117 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_WALSH_INDEX

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_WALSH_

INDEX

Failure Cause During FCH setup, the WALSH code is incorrect in the CES verification






1-69






失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_WALSH_

INDEX

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数Walsh码错误，导致基本信道建立失败。



1.118 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CE_INDEX

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CE_INDEX

Failure Cause During FCH setup, CEIndex is incorrect in the CES verification channel









失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CE_INDEX

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数CEIndex错误，导致基本信道建立失败。


1-70




1.119 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FRAME_OFFSET

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FRAME_O

FFSET

Failure Cause During FCH setup, the frame offset is incorrect in the CES verification









失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FRAME_O

FFSET

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数帧偏置错误，导致基本信道建立失败。



1.120 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CHANNEL_POWER

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CHANNE

L_POWER

1-71



Failure Cause During FCH setup, channel power is incorrect in the CES verification









失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CHANNE

L_POWER

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数信道功率错误，导致基本信道建立失败。



1.121 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_FCH_GATING

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_FC

H_GATING

Failure Cause During FCH setup, the reverse FCH gating mode is incorrect in the CES









1-72



失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_FC

H_GATING

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数反向FCH门控模式错误，导致基本信道建立失败。



1.122 ERR_CES_RLSA_CEC_CALLHNDL_DCCH_SETUP_PARAM_REV_PILOT_GATING

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_DCCH_SETUP_PARAM_REV_P

ILOT_GATING

Failure Cause During FCH setup, the reverse pilot channel gating mode is incorrect in the

CES verification channel setup command, causing the FCH setup failure.








失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_DCCH_SETUP_PARAM_REV_P

ILOT_GATING

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数反向导频信道门控模式错误，导致基本信道建立失败。



1-73



1.123 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_PUNC_MODE

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_PU

NC_MODE

Failure Cause During basic channel setup, the forward power control mode is incorrect in

the CES verification channel setup command, causing the failure in setting

up the basic channel.

Failure Analysis l The CHM version and CCM version do not match.






失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_PU

NC_MODE

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数前向功控模式错误，导致基本信道建立失败。



1.124 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_GAIN

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_GAIN

Failure Cause During basic channel setup, the forward power control gain is incorrect in







1-74






失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_GAIN

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数前向功控增益错误，导致基本信道建立失败。



1.125 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_STEP_SIZE

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_STE

P_SIZE

Failure Cause During basic channel setup, the forward power control setp is incorrect in










失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_STE

P_SIZE

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数前向功控步长错误，导致基本信道建立失败。

1-75





1.126 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_RPC_PUNC_MODE

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_RPC_PU

NC_MODE

Failure Cause During basic channel setup, the reverse power control mode is incorrect in










失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_RPC_PU

NC_MODE

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数反向功控模式错误，导致基本信道建立失败。



1-76



1.127 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC_SETPOINT

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC_

SETPOINT

Failure Cause During basic channel setup, the reverse out loop setting values are incorrect

in the CES verification channel setup command, causing the failure in

setting up the basic channel.








失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC_

SETPOINT

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数反向外环设置值(SetPoint)错误，导致基本信道建立失败。



1.128 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC_PATTERN

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC

_PATTERN

Failure Cause During basic channel setup, the reverse power control mode is incorrect in



1-77










失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC

_PATTERN

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数反向功控模式错误，导致基本信道建立失败。



1.129 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_TRAFFIC_FRAME_TYPE

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_TRAFFIC_

FRAME_TYPE

Failure Cause During FCH setup, the frame type is incorrect in the CES verification







2. Implement soft reset for the CHM.


1-78



失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_TRAFFIC_

FRAME_TYPE

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带参数帧类型错误，导致基本信道建立失败。



1.130 CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DEST_IP_ADRR_INVALID

Failure Name CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DEST_IP_ADRR_INVA

LID

Failure Cause During FCH setup, the destination IP address carried in the CES channel

setup verification command is incorrect, causing the FCH setup failure.


l The CHM version and CCH version do not match.



Handling Measure 1. Make the CHM version and CCM version consistent.



失失失败败败原原原因因因值值值 CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DEST_IP_ADRR_INVA

LID

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带目的IP地址错误，导致基本信道建立失败。



1-79



1.131 CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DSCP_PRIIS_INVALID

Failure Name CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DSCP_PRIIS_INVALID

Failure Cause During FCH setup, the DSCP priority carried in the CES channel setup

verification command is incorrect, causing the FCH setup failure.


l The CHM version and CCH version do not match.



Handling Measure 1. Make the CHM version and CCH version consistent.



失失失败败败原原原因因因值值值 CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DSCP_PRIIS_INVALID

失失失败败败原原原因因因值值值含含含义义义建立基本信道时，CES校验信道建立命令所带DSCP优先级错误，导致基本信道建立失败。



1.132 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_CEMCTRL_NULL

Failure Name ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_CEMCTRL_NULL

Failure Cause During FCH setup, the pointer to the class CEMCTRL object fails to be

obtained, causing the FCH setup failure.

Failure Analysis There is a problem with the CES code.

Handling Measure 1. Implement soft reset for the CHM.

2. If the above measure does not work, reset the CHM.

失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_CEMCTRL_NULL

1-80



失失失败败败原原原因因因值值值含含含义义义建立基本信道时，获取类CEMCTRL的对象的指针，导致基本信道建立失败。

失失失败败败原原原因因因分分分析析析 CES代码异常。

解解解决决决措措措施施施 1. 软复位CHM。2. 以上措施不能缓减情况的话，复位CHM。

1.133 ERR_SPS_RLSA_BSSAP_SccpDisconnect_Connectref_Incompat_Inf_In_NSDUs

Failure Name ERR_SPS_RLSA_BSSAP_SccpDisconnect_Connectref_Incompat_Inf_In_

NSDUs

Failure Cause SCCPDISConnect occurs, with the cause Disconnect_Access_conges-

tion(1A).

Failure Analysis The cause of SCCPDISConnect is Disconnect_Access_congestion(1A).

Handling Measure On the MSC, trace the SCCP signaling of the user and check the specific

failure cause. The cause is usually an authentication failure, which is

resulted from illegal users.

1.134 ERR_SPS_RLSA_BSSAP_SccpDisconnect_End_User_Failure

Failure Name ERR_SPS_RLSA_BSSAP_SccpDisconnect_End_User_Failure

Failure Cause SCCPDISConnect occurs, with the cause Disconnect_Normal_condi-

tion(13). The SCCPDISConnect is caused by a user.

Failure Analysis During registration, the SCCP link is released by the MSC. This is usually

caused by a user that is not provisioned or by an illegal user.

Handling Measure On the MSC, trace the SCCP signaling of the user to find the specific

failure cause.

1-81



1.135 ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail_FCHAndDCCH_AbisdrConnectProccess_AbisdrConnectMsgProccess

Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail_FCHAndDCCH_Abisdr

ConnectProccess_AbisdrConnectMsgProccess

Failure Cause The target of the inter-BSC soft handoff receives the AbisdrConnect

message processing error.

Failure Analysis After the AbisdrConnect message is received, abnormalities occur. For

example, the creation of corresponding cells is stopped (if the A7fDropTarget

message is received following the A7HandoffRequest message), or leg

allocation fails.

Handling Measure If only a few such faults occur, this is normal, and no handling measure

needs to be taken.

1.136 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_CheckIfCellFitToSetup_HOReqCellIsExisted

Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_Other_CheckIfCellFitToSetup_HOR

eqCellIsExisted

Failure Cause The cell requested by the target of the inter-BSC soft handoff already exists.

Failure Analysis The release flow of the target is not completed owing to such cause as link

delay, while the source initiates the next handoff request.


needs to be taken. If a large number of such faults occur, obtain the

abnormal probe and contact ZTE Corporation for analysis.

1.137 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_ReqReleaseingCellIsNotExisted

Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_Other_ReqReleaseingCellIsNotExi

sted

Failure Cause The cell that the target wants to release in the inter-BSC soft handoff does

not exist.

1-82



Failure Analysis Owing to an internal cause of the target or a cause of the BTS, the cell has

already been released, but the source still requests to release the cell; or

the release message of the source carries an incorrect cell.


needs to be taken. If a large number of such faults occur, obtain the

abnormal probe and contact ZTE Corporation for analysis.

1.138 ERR_SPS_RLSA_BSSAP_PTTSetup_ServiceNotify_UserInHigherPriorityService

Failure Name ERR_SPS_RLSA_BSSAP_PTTSetup_ServiceNotify_UserInHigherPriority

Service

Failure Cause A request of the PTT traditional group call is received, and the current call is

preempted.

Failure Analysis The preemption request of a PTT traditional group call is received.

Handling Measure It is a normal case. On the PHR, you can set not allow voice to be

preempted.

1.139 ERR_SPS_RLSA_BSSAP_PTTSetup_A9dfPTTPage_UserInHigherPriority

Failure Name ERR_SPS_RLSA_BSSAP_PTTSetup_A9dfPTTPage_UserInHigherPriority

Failure Cause A PTT call request is received, and the current call is preempted by the

PTT call.

Failure Analysis A PTT call preemption request is received.

Handling Measure It is a normal case. On the PHR, you can set not allow voice to be

preempted.

1-83



This page intentionally left blank.

1-84


Chapter 2Call Drop Causes

2.1 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInSessionState

Failure Name ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInSessionState

Failure Cause In call status, a call origination message is received.

Failure Analysis The possible failure cause is as follows: When the user originates a call and

the process does not release the message, the call fails.

Handling Measure It is acceptable if the problem occurs occasionally, otherwise, further

analysis is needed.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInSessionState

失失失败败败原原原因因因值值值含含含义义义在通话态收到起呼消息。

失失失败败败原原原因因因分分分析析析通话态异常掉话，进程没有释放的时候用户起呼。

解解解决决决措措措施施施少量出现无需处理，如果大量出现，则需要进一步分析。

2.2 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInSessionState_Others

Failure Name ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_Others

Failure Cause During a call, a registration message is received, such as timing register.

Failure Analysis During a call, other registration messages are received, besides power

on and off registration messages.

Handling Measure If the problem occurs occasionally, it is normal. If the problems occurs


cause.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_Others

失失失败败败原原原因因因值值值含含含义义义在通话态收到登记消息，消息类型为其他类型，例如定时登记等。

失失失败败败原原原因因因分分分析析析在通话态收到除开机、关机以外的登记消息。

2-1




2.3 ERR_SPS_RLSA_BSSAP_HandShake_TimeOutFailure Name ERR_SPS_RLSA_BSSAP_HandShake_TimeOut

Failure Cause Handshake times out between BSSAP and DSPM.

Failure Analysis After entering the session state, timer times out while waiting for DSPM

handshaking message.

Possible Solution 1. Check the terminal call state.

2. Verify that the MP board is normal at BSC front-end.

3. Verify that the timeout duration is normal.

4. Verify that the DSPM module operates properly.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_HandShake_TimeOut

失失失败败败原原原因因因值值值含含含义义义 BSSAP与DSPM握手超时。

失失失败败败原原原因因因分分分析析析进入通话状态后等待DSPM的握手消息的定时器超时。

解解解决决决措措措施施施 1. 查看手机通话状态。2. 检查BSC网元MP板是否异常。3. 检查定时器时长是否有问题。4. 检查DSPM模块是否运行正常。

2.4 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerOn

Failure Name ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerOn

Failure Cause Power-on registration message is received during a call.

Failure Analysis The battery is removed during a call, and the MS is powered on and

registers before the process is released.

Battery runs out during a call, and the MS is powered on and registers

before the process is released.

Handling Measure It is acceptable if the problem occurs occasionally. If the problem occurs


cause.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerOn

2-2


Chapter 2 Call Drop Causes

失失失败败败原原原因因因值值值含含含义义义在通话状态收到开机登记消息。

失失失败败败原原原因因因分分分析析析通话过程中拔了电池，在进程没有释放之前开机登记了，或者通话过程中电池没电了，自动关机后，在进程没有释放之前开机登记了。


2.5 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerDown

Failure Name ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerD

own

Failure Cause Power-off registration message is received during a call.

Failure Analysis l The user originates a Power OFF while the process does not release

and the call fails.

l The user on a call presses the power off button and this is the user’

personal action.

Handling Measure Depending on the terminal processing flow.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerD

own

失失失败败败原原原因因因值值值含含含义义义在通话状态收到关机登记消息。

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l 话态异常掉话了，进程并没有释放，用户关机。l 通话状态用户按了关机按钮，与用户行为有关。

解解解决决决措措措施施施需要视终端的具体处理流程决定。

2.6 ERR_SPS_RLSA_BSSAP_UnexptMsg_UmaRegistration

Failure Name ERR_SPS_RLSA_BSSAP_UnexptMsg_UmaRegistration

Failure Cause A UmaRegistration message is received during the call.

Failure Analysis Some MSs receive the registration message when making calls.

Handling Measure If the exception rarely occurs, it is unnecessary to handle. If it occurs

frequently, contact the local representative office of ZTE Corporation.

2-3



2.7 ERR_SPS_RLSA_DSPM_HOH_OtherReason_AbisdHandShakeFailure

Failure Name ERR_SPS_RLSA_DSPM_HOH_OtherReason_AbisdHandShakeFailure

Failure Cause During a call, the handshake failure between DSPM and RCM originates

call release.

Failure Analysis l The RCM and ABPM relevant to the BTS are operating improperly.

l The setting for timer Tphysical on the DSMP board is wrong.

Possible Solution 1. Verify that the setting for timer Tphysical on the DSMP board is correct

(default 2 minutes).

2. Verify that the RCM and ABPM relevant to the BTS are operating

normally and no abnormal reset or changeover occurs.

3. Verify that the versions of CCM and ABPM boards are correct and

operating properly.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_HOH_OtherReason_AbisdHandShakeFailure

失失失败败败原原原因因因值值值含含含义义义通话状态下，DSPM与RCM握手失败，发起呼叫释放。

失失失败败败原原原因因因分分分析析析导致这个失败的主要原因如下：l 对应BTS的RCM、ABPM运行异常。l DSMP单版上Tphysical定时器设置有问题。

解解解决决决措措措施施施 1. DSMP单版上Tphysical定时器设置是否正确（默认2分钟）。2. 查看出问题时对应BTS的RCM，ABPM运行是否正常，是否有异常

复位或倒换。3. 检查CCM、ABPM等板版本是否正确，运行是否正常。

2.8 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFEquipmentFailure

Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFEquipmentFailure

Failure Cause Abnormal call release initiated by PCF.

Failure Analysis l Corresponding PCF runs abnormally.

l A10 link establishment fails.

Possible Solution 1. Verify that the IMSI, HI and DI carried by A9SetupA8 message are

correct.

2. Check if A10 link establishment failed when the handoff failed.

3. Check the version and operation of the PCF board.

2-4



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFEquipmentFailure

失失失败败败原原原因因因值值值含含含义义义 PCF发起的异常呼叫释放。

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l 对应的PCF运行异常。l A10链路建立失败。

解解解决决决措措措施施施 1. 检查A9SetupA8消息中，带的IMSI、HI、DI是否正确。2. 检查是否切换失败时，A10链路无法建立。3. 检查PCF板版本是否正确，运行是否正常。

2.9 ERR_SPS_RLSA_DSPM_CLH_OtherReason_Thandshakerecv

Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_Thandshakerecv

Failure Cause During a call, there is a handshake between the DSPM, SDU and BSSAP.

When there is no reply message, timer Trecv expires and the SPS releases

the call.

Failure Analysis l The DSPM does not receive a reply message from the SDM when it

sends two handshake messages to the SDM in 5 minutes.

l The DSPM does not receive a reply message from the BSSAP when it

sends two handshake messages to the SDM in 5 minutes.

Possible Solution 1. Verify that the setting of the Trecv timer (default value is 5 minutes) on

the DSMP board is correct.

2. Check the corresponding CMP when the problem occurs. Verify that the

SDU operates properly and there is no abnormal reset or switchover.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_CLH_OtherReason_Thandshakerecv

失失失败败败原原原因因因值值值含含含义义义通话状态下，DSPM与SDU和BSSAP握手的定时器Trecv超时，发起呼叫释放。

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l DSPM在5分钟内给SDM发送2次握手消息都收不到SDM的应答消息。l DSPM在5分钟内给SDM发送2次握手消息都收不到BSSAP的应答

消息。

解解解决决决措措措施施施 1. DSMP单版上Trecv定时器设置是否正确（默认5分钟）。2. 查看出问题时对应的CMP，SDU运行是否正常，是否有异常复位或倒

换。

2-5



2.10 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleaseRSCHbyLegFail_ReleaseRschExistSDMLegFailure

Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleaseRSCHbyLe

gFail_ReleaseRschExistSDMLegFailure

Failure Cause The DSPM receives the LegLinkFailure report from SDM. If RSCH is not

partly soft handoff and the released cell, then the SDM notify different cells.

The failure is reported by DSPM.

Failure Analysis The possible failure cause is as follows: SDM has no reverse frames.

Handling Measure Check Abis interface.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleaseRSCHbyLe

gFail_ReleaseRschExistSDMLegFailure

失失失败败败原原原因因因值值值含含含义义义 DSPM收到SDM上报的LegLinkFailure时，若RSCH不是部分软切换，并且释放小区和SDM通知的小区不一样，DSPM上报的原因值。

失失失败败败原原原因因因分分分析析析 SDM反向无帧。

解解解决决决措措措施施施检查Abis口是否有问题。

2.11 SDM_Link_Fail_RevNoFrmFailure Name SDM_Link_Fail_RevNoFrm

Failure Analysis Link failure. The SDM cannot receive traffic frames sent from the BTS

during a period (default time is 18 s).

Reasons for this failure vary, for example, Abis link problem and CHM

dispatching problem, which are subject to different situations.

The call is released when the failure is reported.

Possible Solution Verify that the Abis link is not broken.

失失失败败败原原原因因因值值值 SDM_Link_Fail_RevNoFrm

失失失败败败原原原因因因分分分析析析链路失败，SDM在一段时间内（默认时间为18 s）收不到BTS发来的业务帧。该异常原因有很多种，比如Abist链路问题，CHM调度问题，需要视情况而定。上报该异常时，呼叫会被释放。

解解解决决决措措措施施施检查Abis链路是否断链。

2-6



2.12 SDM_Link_Fail_RevTooManyBadFrmFailure Name SDM_Link_Fail_RevTooManyBadFrm

Failure Analysis Link failure. The SDM receives almost all error frames from the BTS side

during receiving period (default time is 18 s).

The reasons for this failure may vary. The reason may be characterized as

normal or abnormal reasons depending upon the actual situation.

For example:

l If the reverse radio link is very bad, the problem will be reported. This

is a normal release.

l During a calling process, MS releases itself spontaneously for some

reason, while BS does not receive release message of the mobile.

After a while, an error is reported. This is a kind of abnormal release.

l Inconsistent parameters setting between the MS and BS side and PN

offset error will cause this failure. This is another kind of abnormal

release.

Possible Solution 1. Check MS and BS side parameters (PN offset, version).

2. If all the parameters are consistent, MS releases itself spontaneously

and this release is a normal release.

失失失败败败原原原因因因值值值 SDM_Link_Fail_RevTooManyBadFrm

失失失败败败原原原因因因分分分析析析链路失败，SDM在一段时间内从BTS侧收到的几乎都是坏帧（默认时间为18 s）。原因有很多种，有可能是正常原因，也有可能是异常原因，视具体情况而定。例如：l 反向空中链路真的非常差时，就会上报该异常，这种情况属正常释放。l 呼叫过程中，由于某种原因手机自行释放自己，此时BS并未得到手机

的释放消息，因此一段时间后就会上报该异常，这样就需要查为什么手机要自行释放自己的原因，这种情况属异常释放。

l 手机和BS侧参数不一致，PN偏置错误等等都有可能引起该异常，这种情况也属异常释放。

解解解决决决措措措施施施 1. 查看MS和BS侧参数（PN偏置、版本）。2. 参数一致，是MS自行释放，属于正常范畴内失败。

2.13 SDM_Link_Fail_FwdA2pNoFrmFailure Name SDM_Link_Fail_FwdA2pNoFrm

Failure Cause SDM cannot receive traffic frame sent from MGW during a period (default

time is 18 s).

2-7



Failure Analysis Reasons for this fault vary, for example, net cable on Ap port has a problem,

MGW process problem (not sending frame), which is subject to actual

situation. While submitting this fault, calling will be released.

Handling Measure Check net cable on Ap port and check BSC side and MGW side

configuration (for example whether packet quantity is the same), if problem

is not found, then analyze MGW side.

失失失败败败原原原因因因值值值 SDM_Link_Fail_FwdA2pNoFrm

失失失败败败原原原因因因分分分析析析 SDM在一段时间内收不到MGW发来的业务帧（默认时间为18 s）。该异常原因有很多种，比如Ap口网线有问题，MGW处理问题（没有发帧），需要视情况而定。上报该异常时，呼叫会被释放。

解解解决决决措措措施施施检查Ap口网线，检查BSC侧与MGW侧配置（比如打包个数是否一致），没有问题则找MGW侧分析。

2.14 SDM_Link_Fail_FwdA2pTooManyErrEncodeFrmFailure Name SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm

Failure Cause Frames without errors received from Media Gateway (MGW) within 18 s

are not sufficient.

Failure Analysis 1. Problem occur during MGW frame sending, i.e. not send frame to SDM.

2. Problem occurs in Ap port link during call; the possibility is relatively

small.

3. SDM process error.

Handling Measure 1. Verify that the Ap port link is normal.

2. If it is not disconnected link, it is normal situation; please contact

engineers at the office.

失失失败败败原原原因因因值值值 SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm

失失失败败败原原原因因因分分分析析析在18 s内SDM没有从MGW收到足够的好帧。可能原因如下：l MGW发帧过程中出现问题，不再给SDM发帧。l 通话过程中Ap口链路出现问题，可能性比较小。l SDM处理错误。

解解解决决决措措措施施施 1. 检查Ap口链路是否正常。2. 如果不是断链，属于异常情况，请联系中兴通讯。

2-8



2.15 ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_GetCallProc

Failure Name ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_GetCallProc

Failure Analysis During supplementary channel setup handling, searching for the handling

process fails. The cause may be that the call has been released or the call

reference number in the BurstRequest is incorrect.



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_GetCallProc

失失失败败败原原原因因因分分分析析析处理建立补充信道流程时，查找处理进程失败。

解解解决决决措措措施施施可能是呼叫已经释放；或是BurstRequest消息所带的呼叫参考号不正确。少量出现无需处理。如果大量出现，请联系中兴通讯。

2.16 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInHardHOAdd

Failure Name ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInHardHOAdd

Failure Cause During the hard handoff process, a call originating message is received

from the terminal.

Failure Analysis Before the process is released, another call originating message is received

from the terminal. If the battery of the terminal is removed and then

re-installed, and the terminal initiates a call again, the fault occurs.

Handling Measure Such faults seldom occur, and therefore no handling measure is required.

2.17 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvPageRspInHardHOAdd

Failure Name ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvPageRspInHardHOAdd

Failure Cause During the hard handoff process, a paging response message is received

from the terminal.

2-9



Failure Analysis Before the process is released, another paging response message is

received from the terminal. If the battery of the terminal is removed and

then re-installed, and the terminal becomes the called party again, the fault

occurs.

Handling Measure Such faults seldom occur, and therefore no handling measure is required.

2-10


Chapter 3Call Release Causes

3.1 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSNormalRelease

Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSNormalRelease

Failure Cause Normal call release is automatically initiated by a mobile station.

Failure Analysis Normal release.

Handling Measure Normal release.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSNormalRelease

失失失败败败原原原因因因值值值含含含义义义手机自行发起的正常呼叫释放。

失失失败败败原原原因因因分分分析析析属于正常释放。

解解解决决决措措措施施施属于正常释放。

3.2 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSPowerDown

Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSPowerDown

Failure Cause Call release is initiated by mobile station power-off.



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSPowerDown

失失失败败败原原原因因因值值值含含含义义义手机关机发起的呼叫释放。



3-1



3.3 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHRequestMsg_ReleasebyMSDTXTime

Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHReq

uestMsg_ReleasebyMSDTXTime

Failure Cause RSCH DTXTime release is initiated by mobile station.



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHReques

tMsg_ReleasebyMSDTXTime

失失失败败败原原原因因因值值值含含含义义义手机发起的RSCH的DTXTime释放

失失失败败败原原原因因因分分分析析析属于正常释放

初初初步步步解解解决决决措措措施施施属于正常释放

3.4 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemoveIndication_RSCHReleasebySDMOtherReason

Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason _SCHHOnAbarSCHRemo

veIndication_RSCHReleasebySDMDTXTime

Failure Cause RSCH DTXTime release initiated by SDM.



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemov

eIndication_RSCHReleasebySDMOtherReason

失失失败败败原原原因因因值值值含含含义义义 SDM发起的RSCH其他原因释放。



3-2


Chapter 3 Call Release Causes

3.5 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHPNDropIndication_ReleasebyHOH

Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHPNDropIndication_

ReleasebyHOH

Failure Cause SCH release triggered by soft handoff on the fundamental channel.



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHPNDropIndication_

ReleasebyHOH

失失失败败败原原原因因因值值值含含含义义义基本信道软切换去触发的SCH释放。



3.6 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRelease_RSCHExistedCellReleasebyRCM

Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRele

ase_RSCHExistedCellReleasebyRCM

Failure Cause RSCH release initiated at BTS side.



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRele

ase_RSCHExistedCellReleasebyRCM

失失失败败败原原原因因因值值值含含含义义义 BTS侧发起的RSCH释放。



3-3



3.7 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHRelease_ReleasebyCLH

Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHRelease_Release

byCLH

Failure Cause SCH release triggered by call release.



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHRelease_Releaseb

yCLH

失失失败败败原原原因因因值值值含含含义义义呼叫释放触发的SCH释放。



3.8 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemoveIndication_RSCHReleasebySDMOtherReason

Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemov

eIndication_ RSCHReleasebySDMOtherReason

Failure Cause SDM initiates RSCH other causes release.




eIndication_ RSCHReleasebySDMOtherReason

失失失败败败原原原因因因值值值含含含义义义 SDM发起的RSCH其它原因释放。



3-4



3.9 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemoveIndication_FSCHReleasebySDMDuration

Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemov

eIndication_FSCHReleasebySDMDuration

Failure Cause When the SCH dispatch timer is timeout, SDM initiates FSCH release.




eIndication_FSCHReleasebySDMDuration

失失失败败败原原原因因因值值值含含含义义义由于SCH调度时间到SDM发起FSCH释放。



3.10 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHFSCHHandoff_HardHandoff

Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHFSCHHandoff_H

ardHandoff

Failure Cause SCH forward judges that a hard HO is to be done, hence there is a SCH

release.



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHFSCHHandoff_Har

dHandoff

失失失败败败原原原因因因值值值含含含义义义 SCH前向切换判决做硬切换，引发的SCH释放。



3-5



3.11 ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschdrop

Failure Name ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschdrop

Failure Cause Release caused by FSCH due to timeout.



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschdrop

失失失败败败原原原因因因值值值含含含义义义 FSCH切换去，引发的释放。



3.12 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnTfschdroppending_ReleasebyTDropPending

Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnTfschdroppendin

g_ReleasebyTDropPending

Failure Cause Release caused by FSCH due to timeout.



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnTfschdroppendin

g_ReleasebyTDropPending

失失失败败败原原原因因因值值值含含含义义义 FSCH切换去，引发的释放。



3-6



3.13 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRelease_FSCHExistedCellReleasebyRCM

Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRele

ase_FSCHExistedCellReleasebyRCM

Failure Cause FSCH release initiated at BTS side.



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRele

ase_FSCHExistedCellReleasebyRCM

失失失败败败原原原因因因值值值含含含义义义 BTS侧发起的FSCH释放。



3.14 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSGoingIntoDormant

Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSGoingIntoDormant

Failure Cause In data service, the call release is autonomously initiated by a mobile station.



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSGoingIntoDormant

失失失败败败原原原因因因值值值含含含义义义数据业务时，手机自行发起的呼叫释放。



3.15 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFNormalRelease

Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFNormalRelease

3-7



Failure Cause In data service, the normal call release initiated by PCF.



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFNormalRelease

失失失败败败原原原因因因值值值含含含义义义数据业务时，PCF发起的正常呼叫释放。



3.16 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMLinkFailure_toDormant

Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMLinkFailure_toDormant

Failure Cause Data service air interface link fails. During a specific time, SDM receives

error frames or no frames from BTS (the default duration is 18 s) and

releases to the Dormant status.

Failure Analysis This failure may be caused by a lot of reasons, be it normal or abnormal. If

the fault is reported due to the really poor reverse air link, this situation is of

normal release. But not all the situations are normal, many of which may

be of hidden system problems. For example, in the call process, the MS

releases itself but BS does not receive the MS release information. The fault

will be reported later and it is necessary to check out the reason. Different

parameters set in MS and BS may cause the fault, so will the PN offset error.

Handling Measure 1. Check the parameters in both MS and BS (PN offset and version).

2. If the parameters are identical and MS releases itself, it is normal .

3. Optimize network coverage.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMLinkFailure_toDormant

失失失败败败原原原因因因值值值含含含义义义数据业务空口链路失败，SDM在一段时间内从BTS侧收到的几乎都是坏帧或者无帧（默认时间为18 s）释放至Dormant状态。

3-8



失失失败败败原原原因因因分分分析析析几乎坏帧或无帧的原因有很多，有可能是正常原因，也可能是异常原因，视具体情况而定。例如：l 反向空中链路真的非常差时，就会上报该异常，这种情况属正常释放。l 呼叫过程中，由于某种原因手机自行释放自己，此时BS并未得到手机

的释放消息，因此一段时间后就会上报该异常，这样就需要查为什么手机要自行释放自己的原因，这种情况属异常释放。

l 手机和BS侧参数不一致，PN偏置错误等等都有可能引起该异常，这种情况也属异常释放。

解解解决决决措措措施施施 1. 查看MS和BS侧参数（PN偏置、版本）。2. 参数一致，是MS自行释放，属于正常范畴内失败。3. 优化网络覆盖。

3.17 ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnA7rTarRemReq_CLHRlsInd

Failure Name ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnA7rTarRemReq_CL

HRlsInd

Failure Cause During inter-BSC soft handoff, the target BSC detects fault, hence initiating

a soft handoff remove.

Failure Analysis l The signal is weak, so the target initiates the release.

l The A3 link is abnormal, so the target initiates the release.

Handling Measure 1. Check the signal strength.

2. If IBBE boards are used for interconnection, verify that the IBBE boards

and the Ethernet cable are well connected.

3. If HGM boards are used for interconnection, verify that the HGM boards

and the E1 cable are properly connected.

4. Verify that the media link on the target side is normal.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnA7rTarRemReq_CL

HRlsInd

失失失败败败原原原因因因值值值含含含义义义 BSC互联软切换，目标BSC检测到异常主动发起软切换去。

失失失败败败原原原因因因分分分析析析 l 信号不好，目标侧主动发起释放，少量属正常现象l A3链路不正常，目标侧发起释放

3-9



初初初步步步解解解决决决措措措施施施 1. 检查信号强度2. IBBE互联时，检查源侧和目标侧的IBBE板运行是否正常，检查网

线是否有松动3. HGM互联时，检查源侧和目标侧的HGM板运行是否正常，检查E1

线是否有松动4. 检测目标侧媒体链路是否正常

3.18 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease_FSCHExistedCellReleasebyRCM

Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease

_FSCHExistedCellReleasebyRCM

Failure Cause In the case of BSC interconnection, the target side initiates the release of

the forward supplementary channel.

Failure Analysis The scheduling time expires, so it is a normal release.

Handling Measure It is a normal case, so no solution is needed.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease

_FSCHExistedCellReleasebyRCM

失失失败败败原原原因因因值值值含含含义义义 BSC互联时目标侧发起前向补充信道的释放。

失失失败败败原原原因因因分分分析析析调度时间到，属于正常释放。

解解解决决决措措措施施施调度时间到，属于正常释放。

3.19 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease_RSCHExistedCellReleasebyRCM

Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease

_RSCHExistedCellReleasebyRCM

Failure Cause In the case of BSC interconnection, the target side initiates the release of

the reverse supplementary channel.

Failure Analysis The scheduling time expires, so it is a normal release.


3-10



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease

_RSCHExistedCellReleasebyRCM

失失失败败败原原原因因因值值值含含含义义义 BSC互联时目标侧发起反向补充信道的释放。

失失失败败败原原原因因因分分分析析析调度时间到，属于正常释放。

解解解决决决措措措施施施调度时间到，属于正常释放。

3.20 SDM_Find_Fail_NoFCHLegFailure Name SDM_Find_Fail_NoFCHLeg

Failure Cause When SDM receives AbafSDMDropLeg message sent by Layer 3, no leg is

found for SDM to remove. Possible reason is message maintained by SDM

is different from that of Level Three.

Handling Measure Check signaling to find out whether Layer 3 has noticed SDM to add this

leg; if it has, then the problem lies in SDM, if not then it lies in Layer 3.

Find the cause by signaling trace.

失失失败败败原原原因因因值值值 SDM_Find_Fail_NoFCHLeg

失失失败败败原原原因因因详详详解解解 SDM在收到层三发的AbafSDMDropLeg消息时，发现SDM并没有要去的腿。原因可能是：SDM与层三维护的信息不一致。

解解解决决决措措措施施施查看信令，看层三是否有通知SDM加过这条腿，如果有，则是SDM问题，如果没有则是层三问题。

3.21 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_RSCH

Failure Name ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_RSCH

Failure Cause Release R-SCH channel: R-SCH channel release notified by database

message.

Handling Measure Normal status.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_RSCH

失失失败败败原原原因因因分分分析析析释放反向补充信道，由数据库通知消息发起的反向补充信道释放。

解解解决决决措措措施施施正常情况，无需解决。

3-11



3.22 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_FSCH

Failure Name ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_FSCH

Failure Cause Release forward SCH channel: forward SCH channel release notified by

database message.

Handling Measure Normal status

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_FSCH

失失失败败败原原原因因因分分分析析析释放前向补充信道，由数据库通知消息发起的前向补充信道释放。


3.23 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tsch

Failure Name ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tsch

Failure Cause During data service procedure, after SCHresource setup, database

configuration timer expires, waiting for the acknowledgement.

Handling Measure Verify that the voice traffic is not too heavy.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tsch

失失失败败败原原原因因因分分分析析析在数据业务过程中，补充信道资源建立完成，等待数据库配置定时器超时。

解解解决决决措措措施施施检查是否话务量比较大。

3.24 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tbstcomb

Failure Name ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tbstcomb

Failure Cause During data service, BTS side SCH channel resource allocation is finished,

waiting for BSC side confirm, BSC side confirm message timeout

Failure Analysis l Confirm message lost.

l After BTS side allocates SCH channel resource, the parameter in reply

message to BSC side is wrong.

3-12



Handling Measure 1. Verify that the Abis link is normal.

2. Verify that the parameter of AbisdrBurstResponse message carried

by BTS side to BSC side is corrected (mainly compared with

AbisdfBurstRequest); mainly, the important parameter is the cell

information.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tbstcomb

失失失败败败原原原因因因分分分析析析数据业务中，建立补充信道时BTS侧补充信道资源分配完毕，等待BSC侧进行确认时，BSC侧的确认消息超时，有以下原因：l 确认消息丢失。l BTS侧分配补充信道资源后回给BSC侧消息中参数错误。

解解解决决决措措措施施施 1. 检查Abis链路是否通信正常。2. 检查BTS侧带给BSC的AbisdrBurstResponse消息中参数是否正确

（主要和AbisdfBurstRequest相比较），主要要注意的参数有：有关小区的信息。

3.25 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_RevSCHSetupFail

Failure Name ERR_SPS_RLSA_RCM_RSCH_FunCallFail_RevSCHSetupFail

Failure Cause During data service, when an SCH channel is being set up, the database

resource is allocated, but the CHM board fails to be configured, and the

reverse SCH channel is released.

Failure Analysis l The CHM board configuration message is lost.

l A CE of an SCH in the CHM is hung up.

l If there is no resource hung up in the CHM, the database may have a

mistake in idle CE queue of database maintenance.

Handling Measure 1. Verify that the CPU of the CHM is not overloaded.

2. Verify that the CHM has no CE hung up.

3. Check the OMC database probe to verify that there is no mistake in idle

CE queue of database maintenance.

3-13



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_RevSCHSetupFail

失失失败败败原原原因因因分分分析析析数据业务中，建立补充信道时数据库资源分配后配置信道板失败（反向补充信道）发起补充信道释放，有以下原因：l 配置信道板消息丢失。l CHM有SCH的CE吊死。l 如果CHM没有资源吊死，那么可能是数据库维护空闲CE队列有误。

解解解决决决措措措施施施 1. 检查CHM的CPU是否处于过载状态。2. 检查CHM是否有CE吊死。3. 察看数据库探针，确认数据库维护的CE空闲队列是否有误。

3.26 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_FwdSCHSetupFail

Failure Name ERR_SPS_RLSA_RCM_FSCH_FunCallFail_FwdSCHSetupFail

Failure Cause During data service, when an channel is being set up and database is in

allocation, CHM board configuration fails and forward SCH channel is

released.

Failure Analysis l CHM board configuration message lost.

l CE of SCH in CHM is hung up.

l If there is no resource hung up in CHM, it is possible that database has

mistake in idle CE queue maintenance.



3. Check OMC database probe, confirm if there is mistake in CE idle

queue of database maintenance.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_FwdSCHSetupFail

失失失败败败原原原因因因分分分析析析数据业务建立补充信道时，数据库资源分配后配置信道板失败，从而发起补充信道释放。有以下原因：l 配置信道板消息丢失。l CHM有SCH的CE吊死。l 如果CHM没有资源吊死，那么可能是数据库维护空闲CE队列有误。

解解解决决决措措措施施施 1. 检查CHM的CPU是否处于过载状态。2. 检查CHM是否有CE吊死。3. 察看数据库探针，确认数据库维护的CE空闲队列是否有误。

3-14



3.27 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_STATUS_RemovedSCH

Failure Name ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_STATUS_Re

movedSCH

Failure Analysis The cell number is 0, or connection status is STATUS_RemovedSCH


2. Verify that the CHM has no hung up.

3. Check the database probe, and verify that there is no mistake in CE idle


失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_STATUS_Re

movedSCH

失失失败败败原原原因因因分分分析析析小区数目为0，或者连接状态是STATUS_RemovedSCH。

解解解决决决措措措施施施 1. 检查CHM的CPU是否处于过载状态。2. 检查CHM是否有CE吊死。3. 查看数据库探针，确认数据库维护的CE空闲队列是否有误。

3.28 ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_CellNotFoundInRevSCHResourceExtension

Failure Name ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_CellNotFoundInRevSCH

ResourceExtension

Failure Cause During data service, after SCH set up and when user transmits data

continuously, there is a newly added cell. This case is softer handoff add in

transmission. It is normal condition.

Handling Measure Normal status.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_CellNotFoundInRevSCH

ResourceExtension

失失失败败败原原原因因因分分分析析析数据业务中，在补充信道建立完成后，用户进行续传时，有新加的小区，这种情况可能是在续传过程中出现了更软加，是正常情况，不属于失败。

解解解决决决措措措施施施属于更软加的正常情况。

3-15



3.29 ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tconfigtch

Failure Name ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tconfigtch

Failure Analysis During data service, when an SCH channel is being set up and database

is in allocation, CHM board configuration fails and forward SCH channel is

released. The possible failure causes are as follows:

l CHM board configuration message is lost.

l CE of SCH in CHM is hung up.

l If there is no resource hung up in CHM, it is possible that database has

a mistake in idle CE queue maintenance.

Possible Solution 1. Verify that the CPU of the CHM is not overloaded.


3. Check OMC database probe, confirm if there is mistake in CE idle


失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tconfigtch

失失失败败败原原原因因因分分分析析析数据业务中，建立补充信道时数据库资源分配后配置信道板失败（前向基本信道）发起补充信道释放，有以下原因：l 配置信道板消息丢失。l CHM有CE吊死。l 如果CHM没有资源吊死，那么可能是数据库维护空闲CE队列有误。

解解解决决决措措措施施施 1. 检查CHM的CPU是否处于过载状态。2. 检查CHM是否有CE吊死。3. 察看OMC数据库探针，确认数据库维护的CE空闲队列是否有误。

3.30 ERR_SPS_RLSA_RCM_FSCH_OtherReason_EndOfDuration

Failure Name ERR_SPS_RLSA_RCM_FSCH_OtherReason_EndOfDuration

Failure Analysis The database notification message initiates the forward supplementary

channel release.


失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_FSCH_OtherReason_EndOfDuration

失失失败败败原原原因因因分分分析析析释放前向补充信道，由数据库通知消息发起的前向补充信道释放。


3-16


Chapter 4Handoff Failure Causes

4.1 ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail_TargetBSCHandlerEntry_A7HOReqMsgProccessForHOWith1X

Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail__TargetBSCHandlerEntry

__A7HOReqMsgProccessForHOWith1X

Failure Cause The target BSC interconnects with the HIRS BSC. The handoff request

processing is abnormal.

Failure Analysis l The number of cells is greater than the maximum number of cells that

a call occupies.

l The neighbor cell is not configured.

Handling Measure 1. Check interconnection configurations.

2. Verify that the PN configuration of the neighbor cell is correct.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail_TargetBSCHandlerEntry_

A7HOReqMsgProccessForHOWith1X

失失失败败败原原原因因因值值值含含含义义义目标BSC与Hirs BSC互联，切换请求消息处理异常。

失失失败败败原原原因因因分分分析析析会导致这个失败的原因如下：l 小区数大于每个呼叫可能占用的最大小区数。l 没有配置临区。

解解解决决决措措措施施施 1. 检查互联配置。2. 邻接小区的PN配置是否合理。

4.2 ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit

Failure Name ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit

Failure Cause When a call is being established or a call is being established after hard

handoff, the circuit reset message sent from the MSC is received.

4-1



Failure Analysis l The CIC state on the MSC side and that on the BSC side are different.

l The CIC code on the MSC side and that on the BSC side are different.

Handling Measure 1. Verify that the CIC state on the MSC side and that on the BSC side

are consistent.

2. Verify that the PCM codes on both the MSC and BSC sides are

consistent with the E1 cable.


Contact MSC maintenance personnel for troubleshooting.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit

失失失败败败原原原因因因值值值含含含义义义呼叫建立或者硬切换加建立时，收到MSC发送电路复位消息。

失失失败败败原原原因因因分分分析析析会导致这个失败的原因如下：l MSC侧与BSC侧CIC状态不一致。l MSC侧与BSC侧CIC编码不一致。

解解解决决决措措措施施施 1. 检查MSC侧与BSC侧CIC状态。2. 检查MSC和BSC两侧PCM编号与实际E1接线是否一致。3. 如果仍不能解决问题，请MSC侧协助排查原因。

4.3 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_TargetBSCHandler_A7fHandoffRequestProccess_RecievedA7HOReqWhenSemiHO

Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_Other_TargetBSCHandler_A7fHandoff

RequestProccess_RecievedA7HOReqWhenSemiHO

Failure Cause In semi-soft handoff, A7 Handoff Requestmessage will be discarded if it

is received.

Failure Analysis Source side initiates a new handoff before semi-soft handoff flow completes.

Handling Measure It is acceptable if the problem occurs occasionally, otherwise, check the

BSC at source side.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_TargetBSCHandler_A7fHandoff

RequestProccess _RecievedA7HOReqWhenSemiHO

失失失败败败原原原因因因值值值含含含义义义在进行半软切换时，收到新的A7 Handoff Request消息，消息会被丢弃。

失失失败败败原原原因因因分分分析析析半软切换流程未完成，源侧又发起新的切换。

解解解决决决措措措施施施少量出现属于正常，若大量出现检查源侧BSC是否有异常。

4-2


Chapter 4 Handoff Failure Causes

4.4 ERR_SPS_RLSA_BSSAP_Other_SBSSRFailureFailure Name ERR_SPS_RLSA_BSSAP_Other_SBSSRFailure

Failure Cause A failure occurs during a transition, and the target side is expected to send a

transition failure message.

Failure Analysis A failure occurs during a transition due to multiple reasons, and the target

side is expected to send a transition failure message.

Handling Measure Some BTSs may report the failure cause. If the failure occurs frequently,

contact the local ZTE office.

4.5 ERR_SPS_RLSA_BSSAP_DB_GetPeerCellDiscriminator

Failure Name ERR_SPS_RLSA_BSSAP_DB_GetPeerCellDiscriminator

Failure Cause The BSC fails to obtain the cell discrimination type of the peer BSC in a

non-network interconnection handoff from the database according to the

office No. of the interconnected BS.

Failure Analysis The database is abnormal or the peer BSC does not support the

non-network interconnection.

Handling Measure Check the configuration.

4.6 ERR_SPS_RLSA_BSSAP_UnexptMsg_TSendAssignmentMsgNotInValidState

Failure Name ERR_SPS_RLSA_BSSAP_UnexptMsg_TSendAssignmentMsgNotInValid-

State

Failure Cause The MS receives a TSendAssignmentMsg timeout message when it is in an

incorrect state.

Failure Analysis TheMS receives a TSendAssignmentMsg timeout message when it is neither

in the S_HardHOAdd_Setup nor in the S_HardHOAdd_AllocationResource

state. The MS may go into another state due to a system allocation failure or

other reasons when receiving the TSendAssignmentMsg timeout message.

Handling Measure If the failure rarely occurs, it is unnecessary to handle. If the failure occurs

frequently, contact the ZTE engineer.

4-3



4.7 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvSBSSAckNotInSetupState

Failure Name ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvSBSSAckNotInSetupState

Failure Cause The MS receives an SBSSAck message when it is not in the Setup State.

Failure Analysis The MS may go into another state due to a system allocation failure or other

reasons when receiving the SBSSAck message.



4.8 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvSBSSAck_bTbssapRlcReqOut

Failure Name ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvSBSSAck_bTbssapRlcReqOut

Failure Cause An SBSSRelocationRequestAck message is received after TbssapRlcReq

expires.

Failure Analysis The trg progress at the target side does not respond in time, or the link is

broken.



4.9 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvAvrHORequiredSBSSRInV5System

Failure Name ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvAvrHORequiredSBSS-

RInV5System

Failure Cause The V5 system receives a transition hard handoff request.

Failure Analysis After receiving a transition hard handoff request, the V5 system returns it

directly without performing transition processing.



4-4



4.10 ERR_SPS_RLSA_BSSAP_UnexptMsg_TargetRemovalReqInSBSSRCallSetup

Failure Name ERR_SPS_RLSA_BSSAP_UnexptMsg_TargetRemovalReqInSBSSR-

CallSetup

Failure Cause The MS receives an AbisdrTargetRemovalReq message when it is in the

CallSetup state.

Failure Analysis The state changes due to some reason, for example, a resource allocation

failure.



4.11 ERR_SPS_RLSA_BSSAP_UnexptMsg_TbssapRlcReqNotInSetupState

Failure Name ERR_SPS_RLSA_BSSAP_UnexptMsg_TbssapRlcReqNotInSetupState

Failure Cause The MS receives a TbssapRlcReq timeout message when it is in an

incorrect state.

Failure Analysis The MS is not in the S_HardHOAdd_Setup state when the timer expires.

Handling Measure If the exception occurs occasionally, it is unnecessary to handle.

4.12 ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRRequestAck_atCellInfoIsInvalid

Failure Name ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRReque stAck_atCellInfoIsIn-

valid

Failure Cause The cell ID (CI) carried by the SBSSRRequestAck message does not

contain the CI that the handoff request message carries.

Failure Analysis The failure may result from a CI configuration error or acute signal

fluctuation.



4-5



4.13 ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRRequestAck_ServiceTypeIsNotMatched

Failure Name ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRRequestAck_ServiceTypeIs-

NotMatched

Failure Cause The service type carried in SBSSRRequestAck is inconsistent with that

in the MSC.

Failure Analysis Concurrence is not supported for A interface transition. The failure occurs

when the service type of the target progress is inconsistent with that of

the MSC.



4.14 ERR_SPS_RLSA_BSSAP_TE_TbssapRlcReqFailure Name ERR_SPS_RLSA_BSSAP_TE_TbssapRlcReq

Failure Cause The relocation timer expires.

Failure Analysis No response is received after a relocation message is sent.



4.15 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7HandoffRequestReceived

Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7HandoffRequestRe-

ceived

Failure Cause The target side receives a handoff request from the serving side when it

does not finish the current non-network interconnection handoff.

Failure Analysis A message loss occurs during the handoff or a processing exception occurs

on the serving side.

Handling Measure If the failure occurs occasionally, it is unnecessary to handle. If it occurs


4-6



4.16 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7DropTargetReceived

Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7DropTargetReceived

Failure Cause The target side receives a handoff drop request from the serving side when

it has not finished the current non-network interconnection handoff.





4.17 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A3DropReceived

Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A3DropReceived

Failure Cause The target side receives a leg elimination request from the serving side

when it has not finished the current non-network interconnection handoff.





4.18 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_TwaitRlcExpired

Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_TwaitRlcExpired

Failure Cause The soft handoff progress at the target side does not receive the

EV_S_SBSSRelocationComplete message in the timer duration after

sending an EV_S_SBSSRelocationRequestAck message to the hard

handoff progress during a non-network interconnection handoff.

Failure Analysis The message is lost or a processing exception occurs on the hard handoff

progress at the target side during the handoff.



4-7



4.19 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_TwaitDrpTgtExpired

Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_TwaitDrpTgtExpired

Failure Cause The soft handoff progress at the target side does not receive the

A7DropTaregt message from the serving side in the timer duration after

receiving an EV_S_SBSSRelocationComplete message from the hard

handoff progress at the target side during a non-network interconnection

handoff.

Failure Analysis The A7DropTaregt message is lost or a processing exception occurs on the

progress at the serving side.

Handling Measure It is unnecessary to handle. If it occurs frequently, however, report to ZTE

Corporation for analysis.

4.20 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSoftHOAdd

Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSoft-

HOAdd

Failure Cause A non-network interconnection handoff request from the serving side is

received in a soft handoff.

Failure Analysis The failure may result from a message loss or a processing exception at

the serving side.

Handling Measure If it occurs occasionally, it is unnecessary to handle. If it occurs frequently,

contact the ZTE engineer.

4.21 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSoftHODrop

Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSoft-

HODrop


received in a soft handoff drop.


the serving side.

4-8





4.22 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSemiHOAdd

Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSemi-

HOAdd


received in a semi-soft handoff.


the serving side.

Handling Measure Contact ZTE Corporation for analysis.

4.23 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSCHExist

Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhen-

SCHExist

Failure Cause The supplemental channel still exists when a non-network interconnection

handoff request is received.

Failure Analysis A processing exception occurs.


4.24 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_WrongChannelItemState

Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_WrongChannelItemState

Failure Cause After receiving a non-network interconnection handoff, the system finds that

the channel table is in an unexpected state and reject the handoff.

Failure Analysis The message for adding channel tables is lost.

Handling Measure It is unnecessary to handle.

4-9



4.25 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_UnexpectedRlcState

Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_UnexpectedRlcState

Failure Cause A message that is not expected to be received in the current state is

received during a non-network interconnection handoff.

Failure Analysis The failure results from a message loss.



4.26 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_OAMIntervention

Failure Name ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_OAMIntervention

Failure Cause The outgoing hard handoff process is interrupted by the background of the

switch and hence the process is terminated.

Failure Analysis The outgoing hard handoff process is interrupted by the background of the

switch and hence the process is terminated.


4.27 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_EquipmentFailure

Failure Name ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_EquipmentFailure

Failure Cause During the outgoing hard handoff process, an internal processing error

occurs on the switch.

Failure Analysis During the outgoing hard handoff process, an internal processing error

occurs on the switch.


4-10



4.28 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_NoRadioResourceAvailable

Failure Name ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_NoRadioResource

Available

Failure Cause During the outgoing hard handoff process, no radio resource is available.

Failure Analysis Target-side resource setup fails.

Handling Measure Capture the target-side handoff signaling, and contact ZTE Corporation

for analysis.

4.29 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_RTRUnavailable

Failure Name ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_RTRUnavailable

Failure Cause During the outgoing hard handoff process, the required terrestrial circuit

resources are unavailable.

Failure Analysis The terrestrial circuit resources are restricted.


4.30 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_BSNotEquipped

Failure Name ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_BSNotEquipped

Failure Cause During the outgoing hard handoff process, there is a problem with the status

of the target BS.

Failure Analysis There is a problem with the status of the target BS.


4.31 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_HandoffBlocked

Failure Name ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_HandoffBlocked

Failure Cause The outgoing hard handoff is rejected by the switch.

4-11



Failure Analysis The outgoing hard handoff is rejected by the switch.


4.32 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_RTAUnavailable

Failure Name ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_RTAUnavailable

Failure Cause During the outgoing hard handoff process, the required coding/rate are

unavailable.

Failure Analysis The coding/rate are unavailable


4.33 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_TimeOut

Failure Name ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_TimeOut

Failure Cause During the outgoing hard handoff process, the handoff timer of the switch

times out.

Failure Analysis The setup of the target times out.

Handling Measure Capture the handoff signaling on the target of the hard handoff, and contact

ZTE Corporation for analysis.

4.34 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_Unspecified

Failure Name ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_Unspecified

Failure Cause The outgoing hard handoff process is released by the switch.

Failure Analysis There is a problem with the internal flow of the switch.


4-12



4.35 SOFTADD_CELL_ERRORFailure Name SOFTADD_CELL_ERROR

Failure Cause Continuous transmission or softer add for reverse supplementary channel,

cell of DBS given by RCM has error.


l Lost of release message may cause this fault, but the possibility is

comparatively small.

l When basic channel undergoes handoff, as BSC handoff is completed

early, setup application for supplementary channel reaches BTS before

BTS basic channel handoff completes. Which is caused by flow, the

possibility is comparatively large.

Handling Measure Changing flow is suggested. Supplementary channel module of DSPM

makes SCH setup application after FCH module handoff is finished.

失失失败败败原原原因因因值值值 SOFTADD_CELL_ERROR

失失失败败败原原原因因因值值值含含含义义义反向补充信道续传或更软加，RCM带给DBS的小区有误

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l 释放消息丢失也有可能产生此异常，可能性较小。l 当基本信道发生切换时，由于BSC切换完成早，补充信道的建立申

请到达BTS时，BTS基本信道切换并未完成，流程原因导致，此种原因可能性较大。

解解解决决决措措措施施施建议更改流程，DSPM的补充信道模块等待FCH模块切换完成再进行SCH

的建立申请。

4.36 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SoftHOThocompletion

Failure Name ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SoftHOThocompletion

Failure Cause In soft handoffs, the base station sends a handoff indication (HDM). A

Handoff Completes Message (HCM) is not received from the MS after

Thocompletion (default value is 5 s) expires.

Failure Analysis l Poor radio condition causes the air-interface handshake message to be

missing. It is acceptable if this failure occurs occasionally.

l BTS clock is inconsistent with BSC clock when frame number checking

is enabled.

l Transmission bit error.

4-13



Possible Solution 1. Verify that the setting of Thocompletion timer on DSMP board is correct

(default value is 5 s).

2. Check the transmission power of handoff target cell.

3. Check handoff target BTS board and calls under this BTS.

4. Check the versions and operation of ABPM, DTB and DSM.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SoftHOThocompletion

失失失败败败原原原因因因值值值含含含义义义软切换时，基站发送切换指示（HDM），Thocompletion（默认5 s）超时后没有收到MS切换完成消息（HCM），切换超时。

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l 无线环境恶劣导致丢失空口握手消息，少量出现属正常现象。l 打开帧序号校验情况下，BTS和BSC时钟不一致。l 其他原因，如传输误码等。

解解解决决决措措措施施施 1. DSMP单版上Thocompletion定时器设置是否正确（默认5 s）。2. 查看切换目标小区发射功率是否正常。3. 查看切换目标BTS单版运行是否正常，该BTS下呼叫是否正常。4. 检查ABPM、DTB，DSM等接口板版本是否正确，运行是否正常。

4.37 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq

Failure Name ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq

Failure Cause Handoff request response expires.


1. Abis/A3A7 interface link is faulty.

2. Handoff target BTS board runs abnormally.

3. Carrier is faulty.

4. Channel board is faulty.

5. Inter BSC handoff, the A3A7 interface boards (HGM) of the two BSC

run abnormally.

Handling Measure 1. Check the setting of Thoreqtimer on DSMP board (default value is 5s).

2. Check Abis/A3A7 interface link.

3. Check the handoff target BTS board, carrier state and channel board (if

chip is normal, and if CE is blocked).

4. Inter BSC handoff: Check the A3, A7 interface boards (HGM) of the

two BSC and physical links.


Check the version and operation of CCM board.

4-14



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq

失失失败败败原原原因因因值值值含含含义义义切换请求响应超时。

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l Abis/A3A7接口链路异常。l 切换的目标BTS单版运行异常。l 载频状态异常。l 信道板异常。l BSC间切换，两个BSC的A3A7接口板HGM运行异常。

解解解决决决措措措施施施 1. 查看DSMP单版上Thoreq定时器设置是否正确（默认5 s）。2. 查看Abis/A3A7接口链路是否正常。3. 查看切换的目标BTS单版运行是否正常，载频状态是否正常，信道板是

否异常（芯片状态是否正常，CE是否被闭塞）。4. BSC间切换：查看两个BSC的A3、A7接口板HGM运行是否正常，物

理链路是否正常。5. 需要检查CCM板版本是否正确，运行是否正常。

4.38 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnUmrCFSearchReport

Failure Name ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnUmrCFSearc

hReport

Failure Cause In semi-soft handoff, the handoff at target side fails.


l Poor radio condition causes air-interface message missing. It is

acceptable if this failure occurs occasionally.

l Radio condition is poor, target carrier signal is too weak.


Check the versions and operation of ABPM, DTB and DSM.

Handling Measure Check target carrier signal strength.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnUmrCFSearchR

eport

失失失败败败原原原因因因值值值含含含义义义半软切换时，手机在目标侧切换失败。

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l 无线环境恶劣导致丢失空口消息，少量出现属正常现象。l 无线环境恶劣，目标载频信号强度太弱。

解解解决决决措措措施施施 1. 检查目标载频信号强度。2. 需要检查ABPM、DTB、DSM等接口板版本是否正确，运行是否正常。

4-15



4.39 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SemiSoftHOThocompletion

Failure Name ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SemiSoftHOThocompletion

Failure Cause In semi-handoffs, the base station sends a handoff indication (HDM). If the

MS handoff completes message (HCM) is not received when Thocompletion

(default value is 5 s) expires, the handoff will expire.


l Poor radio condition causes air-interface handshake message to be

missing. It is acceptable if this failure occurs occasionally.

l If frame number checking is enabled, BTS and BSC have different

clocks.

l Transmission bit error.

Handling Measure 1. Verify that the setting of the Thocompletion timer of the DSMP board is

correct (default value 5 s).

2. Check the handoff target cell transmission power.

3. Check the handoff target BTS board to see whether the call origination

under this BTS is normal or not.


Check the versions and operation of ABPM, DTB and DSM.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SemiSoftHOThocompletion

失失失败败败原原原因因因值值值含含含义义义半软切换时，基站发送切换指示（HDM），Thocompletion（默认5 s）超时后没有收到MS切换完成消息（HCM），切换超时。

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l 无线环境恶劣导致丢失空口握手消息，少量出现属正常现象。l 打开帧序号校验情况下，BTS和BSC时钟不一致。l 其它原因，如传输误码等。

解解解决决决措措措施施施 1. DSMP单版上Thocompletion定时器设置是否正确（默认5 s）。2. 查看切换目标小区发射功率是否正常。3. 查看切换目标BTS单版运行是否正常，该BTS下呼叫是否正常。4. 需要检查ABPM、DTB、DSM等接口板版本是否正确，运行是否正常。

4.40 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnA7rHOReqAck

Failure Name ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnA7rHOReqAck

Failure Cause Handoff request is rejected by target side.

4-16




l Resource at target BTS/BSC side has problem.

l Flow has problem.

Handling Measure 1. Check Abis/A3A7 interface link.

2. Check the handoff target BTS board, carrier state and channel board

(Verify that the chip is normal and CE is not blocked).

3. Inter BSC handoff: Check the A3A7 interface board (HGM) of the two

BSC and the physical link.


Check the version and operation of CCM board.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnA7rHOReqAck

失失失败败败原原原因因因值值值含含含义义义切换请求被目标侧拒绝

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l 目标BTS/BSC侧资源异常。l 流程异常。

解解解决决决措措措施施施 1. 查看Abis/A3A7接口链路是否正常。2. 查看切换的目标BTS单版运行是否正常，载频状态是否正常，信道板是

否异常（芯片状态是否正常，CE是否被闭塞）。3. BSC间切换：查看两个BSC的A3、A7接口板HGM运行是否正常，物

理链路是否正常。4. 需要检查CCM板版本是否正确，运行是否正常。

4.41 ERR_SPS_RLSA_DSPM_HOH_ResourceAllocFail_GetHandoffProc

Failure Name ERR_SPS_RLSA_DSPM_HOH_ResourceAllocFail_GetHandoffProc

Failure Cause In the process of handoff, the database assignment resource adjusted by

Layer 3 fails.

Failure Analysis l The selected carrier frequency state is wrong, relevant macro value:

HO_STAT_CARRIER_STATE_ERROR (0x00004A03).

l The selected carrier frequency is a pseudo pilot, relevant macro value:

HO_STAT_CARRIER_BEACON (0x00004A04).

l The selected carrier frequency has no CE resource, relevant macro

value: HO_STAT_CARRIER_NO_CE (0x00004A05).

l The selected carrier frequency has no 5KCE resource, relevant macro

value: HO_STAT_CARRIER_NO_CE (0x00004A06).

l The selected carrier frequency does not match FO, relevant macro

value: HO_STAT_CARRIER_FO_NOT_MATCH (0x00004A07).

4-17



l The selected carrier frequency does not match the pilot, relevant macro

value: HO_STAT_PILOT_NO_SAME_FREQ (0x00004A08).

l All carrier frequencies are unable to be used, relevant macro value:

HO_STAT_PILOT_ALLCARRIER_NOT_AVAILABLE (0x00004A09).

l All carrier frequencies have no FO, relevant macro value:

HO_STAT_PILOT_ALLCARRIER_NO_FO (0x00004A0A).

l The pilot does not belong to this BSC, relevant macro value:

HO_STAT_PILOT_NOT_LOCALBSS (0x00004A0B).

l Pilot home is unclear, not configuring neighbor cell, relevant macro

value: HO_STAT_PILOT_IS_NOT_NEIGHBOR (0x00004A0C).

l BSC is not interconnected, relevant macro value: HO_STAT_PILOT_IS

_OTHER_UNLNKBSS (0x00004A0D).

l Target BSC does not support PTT relevant macro value:

HO_STAT_DESTBSC_NOT_SUPPORT_PTT (0x00004A0E).

l Support data service and soft-handoff between IP and HIRS, relevant

macro value: HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO

(0x00004A0F).

l Interconnection state is wrong, relevant macro value:

HO_STAT_DESTBSC_LINKSTATUS_ERROR (0x00004A10).

l Cell modes are wrong, relevant macro value: HO_STAT_PILOT_CELL

MODE_DIFFERENT (0x00004A11).

Possible Solution 1. Check specific information by detecting the fault probe.

2. Check the current carrier frequency state.

3. Check the current neighbor cell configuration.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_HOH_ResourceAllocFail_GetHandoffProc

失失失败败败原原原因因因值值值含含含义义义切换的时候，层三调数据库分配资源失败。

失失失败败败原原原因因因分分分析析析会导致这个失败的原因如下：l 选定的载频状态不对，对应宏值为HO_STAT_CARRIER_STATE_ER-

ROR（0x00004A03）。l 选定的载频为伪导频，对应宏值为HO_STAT_CARRIER_BEACON

（0x00004A04）。l 选定的载频没有CE资源，对应宏值为HO_STAT_CARRIER_NO_CE

（0x00004A05）。l 选定的载频没有5KCE资源，对应宏值为HO_STAT_CARRIER_NO_CE

（0x00004A06）。l 选定的载频FO不匹配，对应宏值为HO_STAT_CAR-

RIER_FO_NOT_MATCH（0x00004A07）。l 导频没有匹配的载频，对应宏值为HO_STAT_PILOT_NO_SAME_FREQ

（0x00004A08）。l 导频所有的载频都不可用，对应宏值为HO_STAT_PILOT_ALLCAR-

RIER_NOT_AVAILABLE（0x00004A09）。

4-18



l 导频所有的载频都没有FO，对应宏值为HO_STAT_PILOT_ALLCAR-

RIER_NO_FO（0x00004A0A）。l 不是本BSC的导频，对应宏值为HO_STAT_PILOT_NOT_LOCALBSS

（0x00004A0B）。l 导频归属不清，没有配置成邻接小区，对应宏值为

HO_STAT_PILOT_IS_NOT_NEIGHBOR（0x00004A0C）。l BSC没有互联，对应宏值为HO_STAT_PILOT_IS_OTHER_UNLNKBSS

（0x00004A0D）。l 目标BSC不支持PTT，对应宏值为HO_STAT_DESTBSC_NOT_SUP-

PORT_PTT（0x00004A0E）。l 数据业务以及并发布支持IP到HIRS的BSC间软切换，对应宏值为

HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO（0x00004A0F）。l 互联状态不对，对应宏值为HO_STAT_DESTBSC_LINKSTATUS_ER-

ROR（0x00004A10）。l 小区模式不对，对应宏值为HO_STAT_PILOT_CELLMODE_DIFFER-

ENT（0x00004A11）。

解解解决决决措措措施施施 1. 通过查异常探针，查看更详细的信息。2. 检查当前载频状态。3. 检查当前邻区配置。

4.42 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMSetISLPFailure

Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMSetISLPFailure

Failure Cause When the military network in encrypted or the telecommunication media is

under transparent transmission, SDM fails to configure ISLP protocol.

Failure Analysis When the conversation gets encrypted, SDM fails to inform VTC to enable

the ISLP protocol.

Handling Measure Verify that the VTC version is normal.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMSetISLPFailure

失失失败败败原原原因因因值值值含含含义义义军网加密或者电信媒体透传业务时，SDM设置ISLP协议失败

失失失败败败原原原因因因分分分析析析在明话转密话时，SDM在通知VTC启动ISLP协议时失败

初初初步步步解解解决决决措措措施施施检查VTC版本是否正常

4-19



4.43 ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnDBSHOProcACK_PNSConstructFrmDBS

Failure Name ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnDBSHOProcACK_PN

SConstructFrmDBS

Failure Cause Error occurs when obtaining new active set during handoff.

Failure Analysis l The database internal status is incorrect.

l Obtaining CCM, ABPM or HGM address of the new cell fails.

l Obtaining the frame type of the new cell fails.

l Obtaining the IBBE address fails.

Handling Measure 1. Verify that the CCM, ABPM, HGM, and IBBE boards are normal.

2. Verify that the A7 link is normal.

3. Verify that the cell node configuration in OMC is correct.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnDBSHOProcACK_PN

SConstructFrmDBS

失失失败败败原原原因因因值值值含含含义义义切换时新获取有效集的信息出错。

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l 数据库内部状态错误。l 获取新加小区的CCM、ABPM或HGM地址失败。l 获取新加小区的帧类型失败。l 获取IBBE地址失败。

解解解决决决措措措施施施 1. 检查CCM、ABPM、HGM和IBBE板运行是否正常。2. 检查A7链路是否正常。3. 检查小区节点的配置是否正确。

4.44 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thocompletion

Failure Name ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thocompletion

Failure Cause Handoff times out.

Failure Analysis l The radio environment is poor, causing the handoff indication message

of the forward air interface to be lost.

l The radio environment is poor, causing the handoff complete message

of the reverse air interface to be lost.

Handling Measure Check the carrier signal strength. If the problem rarely occurs, it is normal.

4-20



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thocompletion

失失失败败败原原原因因因值值值含含含义义义切换完成超时。

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l 无线环境恶劣导致前向空口切换指示消息丢失，少量出现属正常现象。l 无线环境恶劣导致反向空口切换完成消息丢失，少量出现属正常现象。

解解解决决决措措措施施施检查载频信号强度。

4.45 HO_STAT_DESTBSC_IS_HIRS_DATASOFTHOFailure Name HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO

Failure Cause HGM does not support soft handoff within BSC with data service.

Failure Analysis HGM does not support soft handoff within BSC with data service.

Handling Measure Use an IBBE board so that IP BSC and HIRS BSC support soft handoff

within BSC with data service.

失失失败败败原原原因因因值值值 HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO

失失失败败败原原原因因因值值值含含含义义义 HGM不支持数据业务的bsc间软切换。

失失失败败败原原原因因因分分分析析析 HGM不支持数据业务的bsc间软切换。

解解解决决决措措措施施施 IP BSC与HIRS BSC不支持数据业务BSC间软切换，IP BSC与IP BSC只有启用IBBE单板时才支持数据业务BSC间软切换。

4.46 HO_STAT_PILOT_NOT_LOCALBSSFailure Name HO_STAT_PILOT_NOT_LOCALBSS

Failure Cause PN does not belong to the BSC.

Failure Analysis Remove the other BSC PN while performing the hard handoff on the BSC.

Possible Solution Normal flow.

失失失败败败原原原因因因值值值 HO_STAT_PILOT_NOT_LOCALBSS

失失失败败败原原原因因因值值值含含含义义义 PN不是本BSC的。

失失失败败败原原原因因因分分分析析析构造BSC内硬切换时，把其他BSC PN去掉。

解解解决决决措措措施施施属正常现象。

4-21



4.47 HO_Func_GetTargetFromPreCell_ERRFailure Name HO_Func_GetTargetFromPreCell_ERR

Failure Cause The candidate frequency in the active set and the preferred neighbor cell fail

to be obtained during a blind handoff.

Failure Analysis The candidate frequency in the active set and the preferred neighbor cell fail

to be obtained during a blind handoff.

Handling Measure Check the handoff parameters.

4.48 SOME_CELL_FAILFailure Name SOME_CELL_FAIL

Failure Cause In the case of forward supplementary channel soft handoff, the handoff

of specific cells fails.

Failure Analysis l The resources are insufficient.

l The power is insufficient.

l The Ec/Io is insufficient.

Handling Measure Check the CE resource status on the BTS side and the carrier power

overload status.

失败原因值 SOME_CELL_FAIL

失败原因值含义前向补充信道软切换部分小区失败。

失败原因分析前向补充信道软切换部分小区失败：因为资源不足、功率不足、Ec/Io不足。

解决措施查看BTS侧CE资源状况；载频功率过载状况。

4.49 CELL_IS_ERRORFailure Name CELL_IS_ERROR

Failure Cause In the F-SCH soft handoff mode, the number of cells that re-transmit

application requests is smaller than the number of current cells.

Failure Analysis In the F-SCH soft handoff mode, the number of cells that re-transmit

application requests is smaller than the number of current cells.

Handling Measure Verify that the pilot strength of the user active set decreases sharply. If such

problems frequently occur, contact the local office of ZTE.

失失失败败败原原原因因因值值值 CELL_IS_ERROR

4-22



失失失败败败原原原因因因值值值含含含义义义前向补充信道软切换方式下，续传申请的小区数小于当前小区数。

失失失败败败原原原因因因分分分析析析前向补充信道软切换方式下，续传申请的小区数小于当前小区数。

解解解决决决措措措施施施检查用户激活集导频强度存在快速衰弱的情况。如果出现较多，请联系中兴通讯。

4.50 HO_STAT_PILOT_LIMITEDFailure Name HO_STAT_PILOT_LIMITED

Failure Cause During assignment to soft handoff mode, leg setup is forbidden in the cell

that has satisfying resources due to the limit of this mode.

Failure Analysis The failure cause depends on the value of switch 96, as described in the

following:

l When switch 96 is set to 0, all strong legs are set up and leg setup

is forbidden in the cell with weak signals although it has satisfying

resources.

l When switch 96 is set to 1, leg setup is performed in the reference cell

only. Therefore, the non-reference cell cannot set up legs although it

has satisfying resources.

l When switch 96 is set to 2, strong legs with equivalent strength are set

up. In this mode, leg setup is forbidden in the cell with weak signals

although it has satisfying resources.

Handling Measure Check switch 96, absolute threshold of weak pilot ECIO, differential

threshold of weak pilot ECIO and pilot strength of the cell where the failure

occurs.

4.51 ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_SpecifiedCellIsReleasing

Failure Name ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Spec

ifiedCellIsReleasing

Failure Analysis 1. During soft or softer handoff, if handoff happens frequently, handoff has

been started when the release has not been completeed, the problem

may occur.

2. If the problem occurs during normal calls while no handoff is performed,

it is possible that the internal processing is stopped.



cause.

4-23



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Spec

ifiedCellIsReleasing

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：1. 在软或者半软的情况下，如果切换频繁，释放还没有完成又开始切换，

可能会导致该失败原因。2. 如果没有切换，普通呼叫出现此类失败，可能是进程内部处理流程有

挂起。


4.52 ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft_AbisdfBurstRequest

Failure Name ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft

_AbisdfBurstRequest

Failure Analysis During half-soft handoff of data service, if the supplementary channel setup

message is received, the SCH setup message is refused. Failure caused by

this reason is normal.

Possible Solution It is acceptable if the failure occurs occasionally. If the failure occurs

frequently, contact the local office of ZTE Corporation.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft

_AbisdfBurstRequest

失失失败败败原原原因因因分分分析析析在处理数据业务并进行半软切换的过程中，如收到补充信道建立消息，则拒绝该SCH建立消息。此操作导致该失败原因，属于正常失败。

解解解决决决措措措施施施少量出现属正常现象。如果大量出现，请联系中兴通讯。

4.53 HO_STAT_PILOT_IS_OTHER_UNLNKBSSFailure Name HO_STAT_PILOT_IS_OTHER_UNLNKBSS

Failure Cause Pilot is neither in the BSC nor in the other interconnected BSC.

Failure Analysis The MS is in the critical cell and reports that the pilot number is not under

this BSC and not interconnected.

Possible Solution Check the neighboring configuration of the cell.

失失失败败败原原原因因因值值值 HO_STAT_PILOT_IS_OTHER_UNLNKBSS

4-24



失失失败败败原原原因因因值值值含含含义义义导频不在本BSC且不在互联的其他BSC。

失失失败败败原原原因因因分分分析析析手机处于临界区，上报了非本BSC且非互联BSC的导频。

解解解决决决措措措施施施检查小区邻区配置。

4.54 HO_STAT_PILOT_NO_SAME_FREQFailure Name HO_STAT_PILOT_NO_SAME_FREQ

Failure Cause During handoff judge, as there is no suited frequency under the pilot, target

pilot aggregate cannot be added.

Failure Analysis l For soft handoff, this reason means there is no suitable frequency

under the pilot; this should not occur. Because if there is no suitable

carrier, Layer 3 should not submit it; if this does occur, it is an error.

l For semi-soft and hard handoff, the carrier with the smallest

transmission power in the first pilot is selected as the fundamental

carrier. Therefore for other pilots there is probably no such carrier, and

it is normal to submit the reason.

Possible Solution For soft handoff, verify that the frequency for soft handoff is configured

under PN that is to be added.

失失失败败败原原原因因因值值值 HO_STAT_PILOT_NO_SAME_FREQ

失失失败败败原原原因因因值值值含含含义义义在切换判决中，该导频下没有匹配的频率，不能加入目标导频集合。

失失失败败败原原原因因因分分分析析析会导致这个失败的主要原因如下：l 对软切换来说，该原因值表示该导频下没有匹配的频率，这不应该出

现，因为如果没有匹配的载频层三应该不会上报，如果出现就是故障。l 对半软和硬切换来说，因为基础载频是选择第一个导频中发射功率

最小的载频，因此对其他的导频来说可能不存在该载频，上报该原因是正常的。

解解解决决决措措措施施施如果是软切换，检查要加的PN下是否配置了软切使用的频点。

4.55 HO_STAT_CARRIER_PWR_OVERLOADFailure Name HO_STAT_CARRIER_PWR_OVERLOAD

Failure Cause Power of the selected carrier is overloaded.

Failure Analysis During handoff judge, the power of the selected carrier is overloaded. The

reason for this failure is: The carrier has too many subscribers.

Possible Solution Decrease the subscriber quantity of every carrier.

4-25



失失失败败败原原原因因因值值值 HO_STAT_CARRIER_PWR_OVERLOAD

失失失败败败原原原因因因值值值含含含义义义选定的载频功率过载。

失失失败败败原原原因因因分分分析析析在切换判决中，选定的载频功率过载。会导致这个失败的原因是：该载频的用户过多。

解解解决决决措措措施施施降低每个载频的用户量。

4.56 HO_STAT_CARRIER_STATE_MBLOCKFailure Name HO_STAT_CARRIER_STATE_MBLOCK

Failure Cause The selected carrier frequency is manually blocked.

Failure Analysis The carrier frequency is manually blocked, so it is unavailable.

Handling Measure Unblock the carrier frequency.

4.57 HO_STAT_CARRIER_STATE_RFE_BROKENFailure Name HO_STAT_CARRIER_STATE_RFE_BROKEN

Failure Cause The radio frequency of the carrier is faulty.

Failure Analysis The radio frequency of the carrier is faulty, so the carrier status is abnormal.

Possible Solution Check the radio frequency configuration of the carrier.

失失失败败败原原原因因因值值值 HO_STAT_CARRIER_STATE_RFE_BROKEN

失失失败败败原原原因因因值值值含含含义义义载频射频故障。

失失失败败败原原原因因因分分分析析析载频射频故障，导致载频状态异常。

解解解决决决措措措施施施检查载频射频配置。

4.58 HO_STAT_CARRIER_STATE_RFE_LOWPOWERFailure Name HO_STAT_CARRIER_STATE_RFE_LOWPOWER

Failure Cause The power of the carrier is low.

Failure Analysis The power of the carrier is low, so the carrier status is abnormal.

Possible Solution Increase the radio frequency power of the carrier.

失失失败败败原原原因因因值值值 HO_STAT_CARRIER_STATE_RFE_LOWPOWER

4-26



失失失败败败原原原因因因值值值含含含义义义载频低功率。

失失失败败败原原原因因因分分分析析析载频射频功率低，导致载频状态异常。

解解解决决决措措措施施施提升载频的射频功率。

4.59 HO_STAT_CARRIER_STATE_BDS_DISCONNECTFailure Name HO_STAT_CARRIER_STATE_BDS_DISCONNECT

Failure Cause The Abis link is abnormal.

Failure Analysis The link between the BSC and BTS is broken.

Possible Solution Check the Abis link.

失失失败败败原原原因因因值值值 HO_STAT_CARRIER_STATE_BDS_DISCONNECT

失失失败败败原原原因因因值值值含含含义义义 Abis链路异常。

失失失败败败原原原因因因分分分析析析 BSC和BTS之间链路存在断链。

解解解决决决措措措施施施检查Abis链路。

4.60 HO_STAT_CARRIER_STATE_RFE_POWERDOWNFailure Name HO_STAT_CARRIER_STATE_RFE_POWERDOWN

Failure Cause Power amplifier is disabled in case of dynamic power consumption.

Failure Analysis Power amplifier is disabled in case of dynamic power consumption.

Possible Solution Check the dynamic power consumption configuration.

失失失败败败原原原因因因值值值 HO_STAT_CARRIER_STATE_RFE_POWERDOWN

失失失败败败原原原因因因值值值含含含义义义动态功耗关闭功放。

失失失败败败原原原因因因分分分析析析动态功耗关闭功放。

解解解决决决措措措施施施检查动态功耗部分的配置。

4.61 HO_STAT_CARRIER_RESOURCE_RESERVEDFailure Name HO_STAT_CARRIER_RESOURCE_RESERVED

Failure Cause The reserved resources cause the carrier frequency to be unavailable.

4-27



Failure Analysis Particular power or Walsh code resources of the carrier frequency are

reserved for voice or data services, causing the carrier frequency to be

unavailable.

Possible Solution Check the reserved resource parameter configuration of the carrier

frequency.

失失失败败败原原原因因因值值值 HO_STAT_CARRIER_RESOURCE_RESERVED

失失失败败败原原原因因因值值值含含含义义义资源预留导致载频不可用。

失失失败败败原原原因因因分分分析析析由于载频对于语音或数据业务进行了功率或Walshcode资源的预留，导致载频不可用。

解解解决决决措措措施施施检查载频的资源预留参数配置。

4.62 HO_STAT_CARRIER_LIMITEDFailure Name HO_STAT_CARRIER_LIMITED

Failure Cause The service on the carrier frequency is restricted.

Failure Analysis Service based on carrier frequency function. In the fixed allocation mode, in

accordance with the service attributes of the carrier frequency, the carrier

frequency can only be used for the PTT service or non-PTT service.

Possible Solution Check the configuration of the service based on carrier function.

失失失败败败原原原因因因值值值 HO_STAT_CARRIER_LIMITED

失失失败败败原原原因因因值值值含含含义义义载频业务受限。

失失失败败败原原原因因因分分分析析析业务分载频功能，在固定分配模式下，根据载频的业务属性，载频只能用于PTT业务或者非PTT业务。

解解解决决决措措措施施施检查业务分载频功能的相关配置。

4.63 HO_STAT_CARRIER_NO_CEFailure Name HO_STAT_CARRIER_NO_CE

Failure Cause There is no CE in the selected carrier.

Failure Analysis CE resource to which the carrier corresponds has been used up or blocked.

Possible Solution 1. Verify that there is no CE blocked.

2. Decrease the subscriber quantity for every carrier.

4-28



失失失败败败原原原因因因值值值 HO_STAT_CARRIER_NO_CE

失失失败败败原原原因因因值值值含含含义义义选定的载频没有CE。

失失失败败败原原原因因因分分分析析析该载频对应的CE资源已经耗尽或者被闭塞。

解解解决决决措措措施施施 1. 检查有没有CE闭塞。2. 降低每个载频的用户量。

4.64 HO_STAT_CARRIER_NO_5KCEFailure Name HO_STAT_CARRIER_NO_5KCE

Failure Cause No 5K channel board CE for selected carrier.

Failure Analysis The CE is exhausted or blocked in the 5K channel board that corresponds

to the carrier.

Possible Solution 1. Verify that there is no 5K CE blocked.

2. Decrease the subscriber quantity for every carrier.

失失失败败败原原原因因因值值值 HO_STAT_CARRIER_NO_5KCE

失失失败败败原原原因因因值值值含含含义义义选定的载频没有5K信道板CE。

失失失败败败原原原因因因分分分析析析该载频对应的5K信道板CE资源已经耗尽或者被闭塞，但存在15信道板CE。

解解解决决决措措措施施施 1. 检查有没有5K CE闭塞。2. 降低每个载频的用户量。

4.65 HO_STAT_PILOT_IS_NOT_NEIGHBORFailure Name HO_STAT_PILOT_IS_NOT_NEIGHBOR

Failure Cause PN is not configured as neighboring cell.

Failure Analysis PN is not configured as neighboring cell with active set, with no record in

linkcell.

Possible Solution Verify that PN has been configured in the neighboring cell.

失失失败败败原原原因因因值值值 HO_STAT_PILOT_IS_NOT_NEIGHBOR

失失失败败败原原原因因因值值值含含含义义义 PN没有配置为邻区。

失失失败败败原原原因因因分分分析析析 PN没有配置为有效集的小区邻区，在linkcell中没有记录。

解解解决决决措措措施施施检查小区邻区是否配置了该PN。

4-29



4.66 BSC_NO_SEFailure Name BSC_NO_SE

Failure Cause No SE resource is available in the system.

Failure Analysis No SE resource available: SDU configuration error, SE resource status is

abnormal, or SE resource is insufficient.

Possible Solution 1. Verify that the 1XSDU board is correctly configured.

2. Verify that the SDU board operates properly and its version is correct.

3. If the AP interface is installed in the RTP, verify that the SDU virtual

address configuration is correct.

4. Verify that the status of the daughter card of the SDU board and of

INDEX is normal in dynamic management.

5. Verify that the SE resource quantity meets the requirements of traffic

capacity.

失失失败败败原原原因因因值值值 BSC_NO_SE

失失失败败败原原原因因因值值值含含含义义义系统无可用的SE资源。

失失失败败败原原原因因因分分分析析析无可用的SE资源：SDU配置错误，SE资源状态异常或SE资源不足。

解解解决决决措措措施施施 1. 检查是否正确的配置了1XSDU单板。2. 检查SDU单板是否运行正常，版本正确。3. 对于AP接口RTP内置的情况，检查SDU虚地址是否正确配置。4. 动态管理中检查SDU单板的子卡及INDEX是否状态正常。5. 检查SE资源数量是否满足话务容量的需要。

4.67 BSC_NO_VEFailure Name BSC_NO_VE

Failure Cause No VE resource is available in the system.

Failure Analysis No VE resource available: VTC configuration error, abnormal VE resource

status, or insufficient VE resource.

Possible Solution 1. Verify that the resource frame where the CIC is located is configured

correctly with corresponding quantity of VTC boards.

2. Verify that the VTC board operates properly and the CPU/DSP version

is correct.

3. Verify that the VTC board and INDEX status is normal in dynamic

management.

4. Verify that the VE resource quantity meets the requirements of traffic

capacity.

4-30



失失失败败败原原原因因因值值值 BSC_NO_VE

失失失败败败原原原因因因值值值含含含义义义系统无可用的VE资源。

失失失败败败原原原因因因分分分析析析无可用的VE资源：VTC配置错误，VE资源状态异常或VE资源不足。

解解解决决决措措措施施施 1. 检查CIC所在资源框是否都正确的配置了相应数量的VTC单板。2. 检查VTC单板是否运行正常，CPU/DSP版本正确。3. 动态管理中检查VTC单板及INDEX是否状态正常。4. 检查VE资源数量是否满足话务容量的需要。

4.68 BSC_NO_IWFFailure Name BSC_NO_IWF

Failure Cause No IWF resource is available in the system.

Failure Analysis IWF resource unavailable: IWF configuration error, abnormal IWF resource

status, or insufficient IWF resource.

Handling Measure 1. Verify that the IWFB board is correctly configured, especially in the

case that the CIC is not selected.

2. Verify that the IWFB board operates properly and the CPU/DSP version

is correct.

3. Verify that the status of the IWFB board and INDEX is normal in

dynamic management.

4. Verify that the IWF resource quantity meets the requirements of traffic

capacity.

失失失败败败原原原因因因值值值 BSC_NO_IWF

失失失败败败原原原因因因值值值含含含义义义系统无可用的IWF资源。

失失失败败败原原原因因因分分分析析析无可用的IWF资源：IWF配置错误，IWF资源状态异常或IWF资源不足。

解解解决决决措措措施施施 1. 检查是否正确的配置了IWFB单板，特别在非优选CIC的情况下，检查CIC所在资源框是否都配置了IWFB单板。

2. 检查IWFB单板是否运行正常，CPU/DSP版本是否正确。3. 动态管理中检查IWFB单板及INDEX是否状态正常。4. 检查IWF资源数量是否满足话务容量的需要。

4.69 BSC_DSPM_NO_INSTANCEFailure Name BSC_DSPM_NO_INSTANCE

Failure Cause No DSPM example is available in the system.

4-31



Failure Analysis DSPM example unavailable: DSPM configuration error, DSPM status

abnormal, or insufficient DSPM examples.

Possible Solution 1. Verify that the DSPM module is correctly configured, and a proper

quantity of DSPM examples is configured.

2. Verify that the MP daughter card where the DSPM module is located


3. Check the module list in the probe view, and verify that the DSPM is in

normal status.

4. Verify that the quantity of DSPM examples meet the requirements of

traffic capacity.

失失失败败败原原原因因因值值值 BSC_DSPM_NO_INSTANCE

失失失败败败原原原因因因值值值含含含义义义系统无可用的DSPM实例。

失失失败败败原原原因因因分分分析析析无可用的DSPM实例：DSPM配置错误，DSPM状态异常或DSPM实例不足。

解解解决决决措措措施施施 1. 检查是否正确的配置了DSPM模块，并且配置了相应数量的DSPM

实例。2. 检查DSPM模块所在MP子卡是否运行正常，版本正确。3. 探针视图中查看模块表，检查DSPM模块是否状态正常。4. 检查DSPM实例数量是否满足话务容量的需要。

4.70 BSC_NO_RTPPORTFailure Name BSC_NO_RTPPORT

Failure Cause No RTPPORT resource is available in the system. This failure cause is

submitted only in the case of external RTP.

Failure Analysis Unavailable RTPPORT resource: configuration error, abnormal status of

RTP port, or insufficient RTPPORT resource.

Handling Measure 1. In the case of external RTP, verify that the IPI board and RTP port are

correctly configured.

2. Verify that the IPI board where RTP port is located operates properly


3. Verify that the status of RTPPORT resource is normal during dynamic

management.

4. Verify that the RTPPORT resource quantity meets the requirements of

traffic capacity.

失失失败败败原原原因因因值值值 BSC_NO_RTPPORT

失失失败败败原原原因因因值值值含含含义义义系统无可用的RTPPORT资源（此失败原因只在RTP外置情况下上报）。

4-32



失失失败败败原原原因因因分分分析析析无可用的RTPPORT资源：RTP端口配置错误、状态异常或RTPPORT

资源不足。

解解解决决决措措措施施施 1. RTP外置情况下，检查是否正确的配置了IPI单板及RTP端口。2. 检查RTP端口所在IPI单板是否运行正常，版本正确。3. 动态管理中检查RTPPORT资源是否状态正常。4. 检查RTPPORT资源数量是否满足话务容量的需要。

4.71 BSC_NO_VALID_RMPFailure Name BSC_NO_VALID_RMP

Failure Cause No RMP module is available in the system.

Failure Analysis Unavailable RMP module: RMP module configuration error, or abnormal

RMP status.

Possible Solution 1. Verify that the RMP module is correctly configured in the system.

2. Verify that the MP daughter card where the RMP module is located


3. Check the module list in the probe view, and verify that the RMP module

status is normal.

失失失败败败原原原因因因值值值 BSC_NO_VALID_RMP

失失失败败败原原原因因因值值值含含含义义义系统无可用的RMP模块。

失失失败败败原原原因因因分分分析析析无可用的RMP模块：RMP模块配置错误或RMP状态异常。

解解解决决决措措措施施施 1. 检查系统是否正确的配置了RMP模块。2. 检查RMP模块所在MP子卡是否运行正常，版本正确。3. 探针视图中查看模块表，检查RMP模块是否状态正常。

4.72 HO_STAT_CARRIER_NO_CE_LICENSEFailure Name HO_STAT_CARRIER_NO_CE_LICENSE

Failure Cause The selected carrier frequency has no authorized 1x CE.

Failure Analysis The authorized 1x CE relevant to this carrier frequency has been consumed

or blocked.

Handling Measure 1. Verify that the CE_LICENSE is not blocked.

2. Decrease the subscribers' number under this BTS.

失失失败败败原原原因因因值值值 HO_STAT_CARRIER_NO_CE_LICENSE

4-33



失失失败败败原原原因因因值值值含含含义义义选定的载频没有授权的1X CE。

失失失败败败原原原因因因分分分析析析该载频对应BTS的授权1X CE资源已经耗尽或者被闭塞。

解解解决决决措措措施施施 1. 检查有没有CE_LICENSE闭塞。2. 降低该BTS下的用户量。

4.73 HO_NoPilotAvailable_ERRFailure Name HO_NoPilotAvailable_ERR

Failure Cause No pilot is available in handoff decision.

Failure Analysis During handoff decision, no pilot is available in the constructed pilot set.

Handling Measure Trace signaling of handoff decision, and further analyze FailReason of each

cell.

失失失败败败原原原因因因值值值 HO_NoPilotAvailable_ERR

失失失败败败原原原因因因值值值含含含义义义切换判决时，无可用导频。

失失失败败败原原原因因因分分分析析析切换判决时构造的导频集合中无可用导频。

解解解决决决措措措施施施根据信令跟踪中切换判决中出参，每个小区中的FailReason做进一步分析。

4.74 ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MCSHConstructAmdfFCHSetup

Failure Name ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MC


Failure Analysis During call setup or handoff, when channel resources are configured, an

error occurs in the construction of the channel resource configuration

message. The problem normally occurs on the cell where a control channel

is not configured.

Handling Measure On the OMC configuration management, verify that the control channel is

configured for the cell (sector) with the problem.

If the control channel is not configured, configure the control channel and

synchronize data.

If the control channel is configured, contact the local ZTE office.

4-34



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MC


失失失败败败原原原因因因分分分析析析呼叫建立或切换过程中，配置信道资源时构造信道资源配置消息出现异常。

解解解决决决措措措施施施该失败原因多见于建立呼叫的小区的控制信道未配置的情况，请在网管OMC配置管理中检查产生上述问题的小区（载扇）是否配置控制信道。如果未配置，增加导频信道的配置，并同步配置数据至网元设备。若产生上述问题的小区（载扇）已经配置控制信道，请联系中兴通讯处理。

4.75 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_MHandlerAbisdfBTSSetup

Failure Name ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_


Failure Analysis During call setup or handoff, an error occurs in handling the call setup or

handoff message .

Handling Measure 1. In the case that the BTS is in graceful degradation mode, when the BTS

receives the call setup or handoff message from the BSC, the BTS

reports the failure message. It is a normal case.

2. The RCM does not support concurrent setup flows. If the RCM receives

another call setup or handoff message during the leg setup process, the

RCM reports the failure message. If the problem occurs occasionally,

no troubleshooting is required.

3. If the BSSAP or DSPM handoff type is incorrect, the failure message is

also reported. If the problem occurs occasionally, no troubleshooting

is required.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_


失失失败败败原原原因因因分分分析析析呼叫建立或切换过程中，处理呼叫建立或切换消息出现异常。

解解解决决决措措措施施施 1. 如果基站为故障弱化模式，收到BSC的呼叫建立或切换消息，会报该失败，此种属于正常情况。

2. RCM不支持并行建立流程。如果在腿的建立过程中，又收到呼叫建立或切换消息，也可能会报该原因的失败，少量无需处理。

3. BSSAP或DSPM带了不正确的切换的类型，也会上报此失败。

4-35



4.76 ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAck_SoftHandoffLegNoInvalid

Failure Name ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAc


Failure Analysis During call setup or handoff process, the leg number leg in the

AbisdfConnectAck message exceeds the maximum allowed value. A call

supports up to 12 legs. If the leg number exceeds 12, a call failure may

be caused.

Handling Measure If the problem occurs frequently, contact the local representative office of

ZTE Corporation.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAc


失失失败败败原原原因因因分分分析析析呼叫建立或切换过程中，AbisdfConnectAck消息中腿号超过最大限制值导致失败。

解解解决决决措措措施施施一个呼叫最多支持12条腿，如果腿号超过12，则会导致呼叫失败。如果大量出现，请联系中兴通讯。

4.77 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_MCDHSaveToCommonData

Failure Name ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_


Failure Analysis An error occurs in saving data during call setup or handoff handling.

1. The handoff type in the call setup or handoff message is incorrect.

2. The CI and frequency point in call setup or handoff message are

incorrect, so the carrier cannot be found based on the CI and frequency

point.



失失失败败败原原原因因因值值值 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_


失失失败败败原原原因因因分分分析析析呼叫建立或切换过程中，处理呼叫建立或切换时保存数据异常。

4-36



解解解决决决措措措施施施 1. 呼叫建立或切换消息带了不正确的切换类型。2. 呼叫建立或切换消息带了不正确的CI和频点，导致无法根据CI和频点

找到载频。如果大量出现，请联系中兴通讯。

4.78 ERR_CES_RLSA_CEC_CALLHANDLER_V_ChannelType_Error

Failure Name ERR_CES_RLSA_CEC_CALLHANDLER_V_ChannelType_Error

Failure Cause In the case of soft handoff, during FCH setup, the incorrect channel type

causes the FCH setup failure.


1. The CHM version and CCM version do not match.

2. A CES error occurs.

3. An upper-layer error occurs.




失失失败败败原原原因因因值值值 ERR_CES_RLSA_CEC_CALLHANDLER_V_ChannelType_Error

失失失败败败原原原因因因值值值含含含义义义软切换建立基本信道时，信道类型错误，导致基本信道建立失败。



4-37




4-38


Chapter 5Registration Failure Causes

5.1 ERR_SPS_RLSA_BSSAP_Reg_Reject_CongestionFailure Name ERR_SPS_RLSA_BSSAP_Reg_Reject_Congestion

Failure Cause Registration fails due to congestion on the network side.

Failure Analysis The MSC rejects the registration due to congestion.

Handling Measure If the problem occurs occasionally, it is normal. If it occurs frequently, verify

that the corresponding modules on the switch side are normal.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_Reg_Reject_Congestion

失失失败败败原原原因因因值值值含含含义义义由于网络侧拥塞的原因，导致了登记失败。

失失失败败败原原原因因因分分分析析析由于MSC侧拥塞或者其他原因导致了登记拒绝。

解解解决决决措措措施施施如果这种情况非常多，请交换机侧的人员查看相关模块是否运行正常；如果只有少量出现，属于正常情况。

5.2 ERR_SPS_RLSA_BSSAP_Reg_Reject_IllegalMsFailure Name ERR_SPS_RLSA_BSSAP_Reg_Reject_IllegalMs

Failure Cause Registration fails due to invalid IMSI.

Failure Analysis The cause of the invalid IMSI may be:

1. The IMSI is all zeros.

2. The UIM card has been cloned.

Handling Measure Determine whether to block illegal mobile phones according to the actual

situation.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_Reg_Reject_IllegalMs

失失失败败败原原原因因因值值值含含含义义义由于IMSI非法，导致了登记失败。

失失失败败败原原原因因因分分分析析析主要是由于IMSI非法导致的，目前的非法手机体现为如下两种情况：l IMSI全部为0。l 克隆UIM卡。

5-1



解解解决决决措措措施施施根据实际情况决定是否打开封锁非法手机的开关。

5.3 ERR_SPS_RLSA_BSSAP_Reg_Reject_NetworkFailure

Failure Name ERR_SPS_RLSA_BSSAP_Reg_Reject_NetworkFailure

Failure Cause Registration fails due to network failure.

Failure Analysis The IMSI information is not found in VLR/HLR, hence causing the

registration failure.

Handling Measure It is a normal case. Trace it and find the IMSI information on the MSC side.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_Reg_Reject_NetworkFailure

失失失败败败原原原因因因值值值含含含义义义由于网络失败的原因，导致了登记失败。

失失失败败败原原原因因因分分分析析析由于在VLR/HLR中查找不到IMSI信息，导致了登记失败。

解解解决决决措措措施施施可以进行跟踪，并在MSC侧查找一下IMSI相关的信息。

5.4 ERR_SPS_RLSA_BSSAP_Reg_Reject_RoamingNotAllowed

Failure Name ERR_SPS_RLSA_BSSAP_Reg_Reject_RoamingNotAllowed

Failure Cause Registration fails due to lack of roaming rights.

Failure Analysis During registration, when the system wants to find the IMSI information in

VLR/HLR, it finds that the user is roaming in another place and the user has

no roaming rights. Hence, the registration fails.

Handling Measure The user has no roaming rights; therefore, it is normal that the problem

is reported.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_Reg_Reject_RoamingNotAllowed

失失失败败败原原原因因因值值值含含含义义义由于没有漫游权限的原因，导致了登记失败。

失失失败败败原原原因因因分分分析析析登记的时候，查找VLR/HLR中对应的IMSI信息，但发现用户正漫游在其它地方，且没有开通漫游权限，从而导致了登记失败。

解解解决决决措措措施施施 1. 如果用户无漫游权限，上报此原因属于正常情况。2. 根据用户实际情况选择开通漫游权限。

5-2


Chapter 5 Registration Failure Causes

5.5 ERR_SPS_RLSA_BSSAP_Reg_Reject_OtherFailure Name ERR_SPS_RLSA_BSSAP_Reg_Reject_Other

Failure Cause Registration fails due to other unknown causes.

Failure Analysis The registration fails due to a cause other than network congestion, invalid

IMSI, network failure and no roaming rights.

Handling Measure If such problems rarely occur, it is normal. If a lot of such problems occur,


失败原因值 ERR_SPS_RLSA_BSSAP_Reg_Reject_Other

失败原因值含义由于未知的其他原因导致了的登记失败。

失败原因分析不是上述几种失败原因导致的登记失败，均归为这类。

解决措施 1. 如果所占比例不很多，属于正常情况。2. 如果大量出现，请联系中兴通讯。

5.6 ERR_SPS_RLSA_BSSAP_SccpDisconnect_Release_In_Progress

Failure Name ERR_SPS_RLSA_BSSAP_SccpDisconnect_Release_In_Progress

Failure Cause SCCP receives the repeated registration request from the same user,

causing the registration failure.

Failure Analysis Certain MSs sends registration requests frequently, causing the registration

failure.

Handling Measure If such problems rarely occur, it is normal. If a lot of such problems occur,


失失失败败败原原原因因因值值值 ERR_SPS_RLSA_BSSAP_SccpDisconnect_Release_In_Progress

失失失败败败原原原因因因值值值含含含义义义 SCCP处理过程中，又收到了相同用户的登记，从而导致了登记失败。

失失失败败败原原原因因因分分分析析析由于某些终端的问题，导致了频繁的登记，从而引起等级失败。

解解解决决决措措措施施施 1. 这个失败是由于个别用户引起的，少量属于正常。2. 可能存在个别站下上报此失败的原因，失败数量很大时，请联系中兴通

讯。

5-3



5.7 ERR_SPS_RLSA_BSSAP_Reg_Reject_MinImsiUnknown

Failure Name ERR_SPS_RLSA_BSSAP_Reg_Reject_MinImsiUnknown

Failure Cause The MS whose number is not allocated on the HLR initiated a registration, and

the registration fails.

Failure Analysis The number of the MS that initiates a registration is not allocated on the HLR.

Handling Measure The problem rarely occurs. If this occurs, contact the ZTE local office or the

R&D personnel.

5-4


Chapter 6Other Failure Causes

6.1 ERR_SPS_RLSA_BSSAP_DiscardMsg_SmsNumOvld

Failure Name ERR_SPS_RLSA_BSSAP_DiscardMsg_SmsNumOvld

Failure Cause Excess SMS messages are received.

Failure Analysis When receiving a large quantity of forward SMS messages in a short period

of time, the system automatically discards the messages that exceed the

threshold and reports the exception.

Handling Measure Verify that the setting of the SMS overload threshold is reasonable and no

exception occurs during an SMS peak.

6.2 ERR_SPS_RLSA_BSSAP_MsgPara_A1fPACAUpdate_SBSSRInvalidProcess

Failure Name ERR_SPS_RLSA_BSSAP_MsgPara_A1fPACAUpdate_SBSSRInvalidPro-

cess

Failure Cause The update fails due to the absence of the serving side.

Failure Analysis The PACA update fails when the MS transits to the target side completely.

Handling Measure If the failure occurs occasionally, it is unnecessary to handle. If the failure

occurs frequently, contact the ZTE engineer.

6.3 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7BurstRequestReceived

Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7BurstRequestReceived

Failure Cause The target side receives a supplemental channel setup request from the

serving side when it does not finish the current non-network interconnection

handoff.

6-1







6.4 ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVERLOAD

Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVERLOAD

Failure Cause DSMP board CPU overloads.

Failure Analysis DSMP board CPU overloads.

Handling Measure Add another DSMP board.

失失失败败败原原原因因因值值值 ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVERLOAD

失失失败败败原原原因因因值值值含含含义义义 DSMP板CPU过载

失失失败败败原原原因因因分分分析析析 DSMP板CPU过载

初初初步步步解解解决决决措措措施施施如果问题很严重，可以考虑拔掉备板

进进进一一一步步步解解解决决决措措措施施施需要增加DSMP板

6.5 INPUT_PARA_ERRORFailure Name INPUT_PARA_ERROR

Failure Cause Input parameter error.

Failure Analysis It is normally displayed during system reset. The possible failure causes

are as follows:

l The confirmed rate is higher than that of the system reserves.

l The dispatching duration is out of the allowed range.

l The Walsh code is different from that allocated.

Possible Solution Check the fault probe and take measures accordingly after identifying the

cause.

失失失败败败原原原因因因值值值 INPUT_PARA_ERROR

失失失败败败原原原因因因值值值含含含义义义输入参数错误。

6-2


Chapter 6 Other Failure Causes

失失失败败败原原原因因因分分分析析析该失败原因一般在系统复位过程中出现，主要集中在补充信道的建立上，会导致这个失败的原因如下：l 确认速率比系统预留速率大。l 调度时长不在允许范围内。l Walsh码与已分配的不一致。


6-3




6-4


GlossaryABPM- ABis Processing Module- Abis接口处理板

ACK- ACKnowledgement- 应答

Abis- Abis Interface between BSC and BTS- BSC和BTS之间的接口

BDM- Baseband Digital Module

BDM is a board in a micro-BTS, the functions of BDM are same as BDS in amacro-BTS.

- 数字基带模块

BS- Base Station- 基站

BSC- Base Station Controller- 基站控制器

BSSAP- Base Station System Application Part- 基站系统应用部分

BTS- Base Transceiver Station- 基站收发信机

CCM- Communication Control Module- 通信控制模块

CE- Channel Element- 信道单元

CES- Channel Element Subsystem- 信道单元子系统

I



CHM- Channel Processing Module

It completes forward modulation and reverse demodulation for baseband data ofthe cdma2000-1X physical channel. As a concept corresponding to RF, basebandrefers to the signal before carrier modulation or after carrier demodulation.

- 信道处理模块

CIC- Circuit Identification Code- 电路识别码

CMP- Calling Main Processor- 主呼叫处理模块

CPU- Central Processing Unit- 中央处理器

CSM- Central Switching Module- 中心交换模块

DSM- Data Service Module

Implements the Abis interface function between the IP BDS and the IP BSC, andprovides the conversion of IP packets into the E1/T1 signals that are suitable forremote transmission before the signals are transmitted to the remote station.

- 数字服务模块

DSMP- Data Service Management Platform- 数据业务管理平台

DSP- Digital Signal Processor- 数字信号处理器

DTB- Digital Trunk Board- 数字中继板

ESN- Electronic Serial Number- 电子序列号

FO- Frame Offset- 帧偏移量

II


Glossary

HGM- HIRS GateWay Module- HIRS网关单元

HIRS- High-speed Interconnect Router Subsystem- 高速互连路由子系统

HLR- Home Location Register- 归属位置寄存器

IBBE- Interface of BSC and BSC by Ethernet- 通过Ethernet互联的BSC互联处理单元

IMSI- International Mobile Subscriber Identity- 国际移动用户标识

MGW- Media Gateway- 媒体网关

MS- Mobile Station- 移动台

MSC- Mobile Switching Center- 移动交换中心

MSCe- Mobile Switching Center emulator- 移动交换中心仿真

OMC- Operation & Maintenance Center- 操作维护中心

PCF- Packet Control Function

PCF is a board which is responsible for the data selection between multiplereverse traffic channels and data distribution from a forward traffic channel tomultiple cells/sectors during soft handoff.

- 分组控制功能

PCM- Pulse Code Modulation- 脉冲编码调制

III



PDSN- Packet Data Service Node- 分组数据服务节点

R-SCH- Reverse Supplemental Channel- 反向补充信道

RC- Radio Configuration- 无线配置

RCM- Radio Control Module- 无线信道控制模块

RMP- Resource Main Processor- 资源主处理单元

SCCP- Signaling Connection Control Part- 信号连接控制部分

SCCP- Signaling Connection Control Part- 信令连接控制部分

SCH- Supplemental Channel- 补充信道

SDH- Synchronous Digital Hierarchy- 同步数字体系

SDM- Supervisory Division Multiplexing Board- 监控分插复用板

SDU- Selection and Distribution Unit- 选择器单元

SDU- Service Data Unit- 业务数据单元

SO- Service Option- 业务选项

IV


Glossary

SSN- Sub-System Number- 子系统号

UID- User IDentifier- 用户标识符

VLR- Visitor Location Register- 拜访位置寄存器

VTC- Voice Transcoder Card- 语音码型变换板

V


Documents

SJ-20120828144226-019-ZXC10 BSSB Failure Reason Reference(1X)_450877