ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop Explanation (EV-DO)

ZXC10 BSSBCDMA Base Station System

Call Failure Reason and Call Drop Explanation (EV-DO)

Version 8.0.1.9

ZTE CORPORATION ZTE Plaza, Keji Road South, Hi-Tech Industrial Park, Nanshan District, Shenzhen, P. R. China 518057 Tel: (86) 755 26771900 800-9830-9830 Fax: (86) 755 26772236 URL: http://support.zte.com.cn E-mail: [email protected]

LEGAL INFORMATION Copyright 2006 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. The contents of this document and all policies of ZTE CORPORATION, including without limitation policies related to support or training are subject to change without notice.

Revision History

Date Revision No. Serial No. Reason for Revision

6/11/2007 R1.0 sjzl20071308 First edition

ZTE CORPORATION Values Your Comments & Suggestions! Your opinion is of great value and will help us improve the quality of our product documentation and offer better services to our customers.

Please fax to: (86) 755-26772236; or mail to Documentation R&D Department, ZTE CORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park, Shenzhen, P. R. China 518057.

Thank you for your cooperation!

Document Name ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop Explanation (EV-DO)

Product Version V8.0.1.9 Document Revision Number R1.0

Equipment Installation Date

Presentation: (Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization, Appearance)

Good Fair Average Poor Bad N/A

Accessibility: (Contents, Index, Headings, Numbering, Glossary)


Your evaluation of this documentation

Intelligibility: (Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)


Your suggestions for improvement of this documentation

Please check the suggestions which you feel can improve this documentation: Improve the overview/introduction Make it more concise/brief Improve the Contents Add more step-by-step procedures/tutorials Improve the organization Add more troubleshooting information Include more figures Make it less technical Add more examples Add more/better quick reference aids Add more detail Improve the index Other suggestions __________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

# Please feel free to write any comments on an attached sheet.

If you wish to be contacted regarding your comments, please complete the following:

Name Company

Postcode Address

Telephone E-mail

This page is intentionally blank.

Contents

About this Manual............................................................. i Purpose................................................................................ i Intended Audience ................................................................. i Prerequisite Skill and Knowledge .............................................. i What is in This Manual............................................................ i Related Documentation.......................................................... ii Conventions......................................................................... ii How to Get in Touch............................................................. iii

Chapter 1..........................................................................1

Call Failure .......................................................................1

Chapter 2........................................................................27

Handoff Failure ..............................................................27

Chapter 3........................................................................43

Reasons for Call Drop ....................................................43

Chapter 4........................................................................81

Release Failure...............................................................81

Tables.............................................................................85

Confidential and Proprietary Information of ZTE CORPORATION i

About this Manual

Purpose

This manual describes reasons and explanations for call drop and call failure for ZXC10 BSSB (EV-DO) product. This manual also provides suitable solutions to solve these problems.

Intended Audience

This document is intended for engineers and technicians who perform operation activities on ZXC10 BSSB (EV-DO) product.

Prerequisite Skill and Knowledge

To use this document effectively, users should have a general understanding of wireless telecommunications technology. Familiarity with the following is helpful:

the ZXC10 BSSB system and its various components

local operating procedures

What is in This Manual

This Manual contains the following chapters:

T AB L E 1 C H A P T E R S U M M AR Y

Chapter Summary

Chapter 1

Call Failure

Describes causes and solutions for call failure.

Chapter 2

Handoff Failure

Describes reasons and settlement measures for handoff failure.

Chapter 3

Reasons for Call Drop

Explains the reasons and settlement measures for call drop.

Chapter 4 Describes reasons and solutions for

ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop Explanation (EV-DO)

ii Confidential and Proprietary Information of ZTE CORPORATION

Chapter Summary

Release Failure release failure.

Related Documentation

The following documentation is related to this manual:

ZXC10 BSSB (V8.0.1.9) CDMA2000 Base Station System General Description

Conventions

ZTE documents employ the following typographical conventions.

T AB L E 2 TY P O G R AP H I C AL C O N V E N T I O N S

Typeface Meaning

Italics References to other Manuals and documents.

Quotes Links on screens.

Bold Menus, menu options, function names, input fields, radio button names, check boxes, drop-down lists, dialog box names, window names.

CAPS Keys on the keyboard and buttons on screens and company name.

Constant width Text that you type, program code, files and directory names, and function names.

[ ] Optional parameters.

{ } Mandatory parameters.

| Select one of the parameters that are delimited by it.

Note: Provides additional information about a certain topic.

Checkpoint: Indicates that a particular step needs to be checked before proceeding further.

Tip: Indicates a suggestion or hint to make things easier or more productive for the reader.

T AB L E 3 M O U S E OP E R AT I O N C O N V E N T I O N S

Typeface Meaning

Click Refers to clicking the primary mouse button (usually the left mouse button) once.

Double-click Refers to quickly clicking the primary mouse button

Typographical Conventions

Mouse Operation

Conventions

About this Manual

Confidential and Proprietary Information of ZTE CORPORATION iii

Typeface Meaning

(usually the left mouse button) twice.

Right-click Refers to clicking the secondary mouse button (usually the right mouse button) once.

Drag Refers to pressing and holding a mouse button and moving the mouse.

How to Get in Touch

The following sections provide information on how to obtain support for the documentation and the software.

If you have problems, questions, comments, or suggestions regarding your product, contact us by e-mail at [email protected]. You can also call our customer support center at (86) 755 26771900 and (86) 800-9830-9830.

ZTE welcomes your comments and suggestions on the quality and usefulness of this document. For further questions, comments, or suggestions on the documentation, you can contact us by e-mail at [email protected]; or you can fax your comments and suggestions to (86) 755 26772236. You can also browse our website at http://support.zte.com.cn, which contains various interesting subjects like documentation, knowledge base, forum and service request.

Customer Support

Documentation Support


iv Confidential and Proprietary Information of ZTE CORPORATION


Confidential and Proprietary Information of ZTE CORPORATION 1

C h a p t e r 1

Call Failure

This chapter describes failure cause values, causes and solutions for call failure problems.


2 Confidential and Proprietary Information of ZTE CORPORATION

T AB L E 4 CONNECTION_SETUP_AVBSCCHITEMREQ_TIMEOUT

Failure Cause Value

142

Details

After connection establishing and resource allocating, SP sends an AvrBSCChItemRequired message to BSSAP to request the information of adding channel table. If no response, connection establishing fails.

In the following cases, there may be a large volume of such failures:

1. links between boards fail

2. version mismatch

3. Incorrect data configuration

Solution

If the links between boards fail, reset the suspected board (DOCMP, DOSDU and UIM)

if there is a version mismatch, check the version compatibility of DOCMP and DOSDU

If data configuration is incorrect, check the data configuration and rollback.

T AB L E 5 CONNECTION_SETUP_SETDRCLENTR ANS_FAILURE

Failure Cause Value

141

Details

After resource allocating and before sending TCA, an AbiscfSetDRCAndAckInfo message and an AbiscfSetDRCLengthTransition message is sent to all channel boards for parameter settings. In the received AbiscrSetDRCLengthTransitionAck message, if the field Result0 (0 stands for success), connection establishing fails.

Solution

Check the system parameters in NetNumenTM M3(ZXC10 BSSB). If the DRCLength (in DRC parameter table) that correspond to the different numbers of leg are incorrect, the data configuration may be faulty, consider rollback.

Chapter 1 Call Failure


T AB L E 6 CONNECTION_SETUP_SETDRC AND ACKINFO_F AILURE

Failure Cause Value

140

Details

After resource allocating and before sending TCA, an AbiscfSetDRCAndAckInfo message and an AbiscfSetDRCLengthTransition message is sent to all channel boards for parameter settings. In the received AbiscrSetDRCAndAckInfoAck message, if the field Result0 (0 stands for success), connection establishing fails.

Solution

Check the system parameters in OMC. If the DRCLength, DRCChannelGain, AckChanelGain, and DSCChannelGain and DRCThreshold (in DRC parameter table) that correspond to the different numbers of leg are incorrect, the data configuration may be faulty, consider rollback.

T AB L E 7 CONNECTION_SETUP_AT ACQUIRED_TIMEOUT

Failure Cause Value

139

Details

Upon receiving a reverse capture message, SP sends an AbiscfATAcquired message to channel board to request power control mode change and wait for the response. If not all responses are collected before timer expires, connection establishing fails.


1. links between boards fail

2. version mismatch

Solution

If the links between boards fail, reset the suspected board (DOSDU, CHM and UIM)

If there is a version mismatch, check the version compatibility of CHM and DOSDU



T AB L E 8 CONNECTION_SETUP_AVF_BSCCHITEMREQ ACK_ P AR A_ERROR

Failure Cause Value

138

Details

Connection is established after the completion of resource allocation. SP sends AvrBSCChItemRequired message to BSSAP to request access to channel adding list. If the quantity of ucBSCIPNumber in the received vfBSCChItemRequiredAck message is more than the highest leg number (6), mistakes occurs while saving BSCIP.

Upon completion of connection establishing and resource allocating, SP sends an AvrBSCChItemRequired message to BSSAP to request a connection. This request fails.

Solution

Perhaps BSSAP fails to retrieve data from database. The IP addresses are configured by the system automatically. If there are a large volume of such failures, reset DOCMP board and synchronize the data.

T AB L E 9 CONNECTION_SETUP_RCP_TIMEOUT

Failure Cause Value

137

Details

SP sends a resource allocating request to RCP without receiving reply. The timer expires. The state of the sector that waits for resource allocation will be marked with this reason. If it is the 1st resource allocating request, the connection establishing fails with the cause CONNECTION_SETUP_CARRIER_ALLOCATE_TIMEOUT. Otherwise, the connection establishing will not fail.

Solution


1. Some CEs are abnormal. Solution: check the probe in OMC reset CHM;

2. Perhaps the problem of the links between boards causes message loss. Solution: reset the suspected boards(DOSDU, CCM, UIM and etc.);

3. Version mismatch. Solution: check version compatibility of DOSDU, CCM and CHM

4. BSC and BTS have inconsistent data. Solution: synchronize data towards OMP and CCM

5. Incorrect data configuration. Solution: Check data configuration and rollback.



T AB L E 10 CONNECTION_SETUP_ABNORM AL_RELE ASE

Failure Cause Value

136

Details While establishing a connection, if base station initiates a release because of some reasons, connection establishing fails.

Solution

Reasons for release failure vary. Checking out abnormality in some modules occurs and abnormality probe are suggested.

There are a lot of release causes.

T AB L E 11 CONNECTION_SETUP_TCC_TIMEOUT_WAIT ING_TCC_ COMING

Failure Cause Value

135

Details SP sent a TCA message to handset without receiving the TCC message. TCC waiting timer expiration causes connection establishment failure.

Solution

Confirm one of the following situations on MS side log message when above problems occur.

1. Handset does not receive the RTCAck message. If the parameters in the received TCA message are correct, but the handset does not start sending data at reverse direction, consider the following possibilities:

(1)CHM does not capture the handset, or DOSDU is not notified after capture. This problem may be because of following:

CHM or links between boards fail,

Solution: check CHM or DOSDU according to running information observation or abnormal probe to see if they run normally. Consider resetting CHM and DOSDU.

(2)Handset is captured by base station. But the RTCAck message sent from DOSDU is not received by the handset. Perhaps the forward media stream has problem. Solution: Make sure CHM, DOSDU, ABPM and DSM run normally and are in correct versions. Consider resetting these boards.

2. Handset receives the RTCAck message and sends out the TCC message, but base station does not receive it. Perhaps the reverse media stream has problem. Solution: Make sure CHM, DOSDU, ABPM and DSM run normally and are in correct versions. Consider resetting these boards.



T AB L E 12 CONNECTION_SETUP_AT_TERMINATED

Failure Cause Value

134

Details When establishing a connection, if a handset initiates a call release because of some reasons, connection establishing fails.

Solution Users mishandling. No special handling is needed.

T AB L E 13 CONNECTION_SETUP_SDU_OVERLO AD

Failure Cause Value

130

Details A new call origination request is received, but SDU is overloaded, connection establishing fails.

Solution Overload control is necessary. No special handling is needed.

T AB L E 14 CONNECTION_SETUP_SEND_TC A_F AILURE

Failure Cause Value

129

Details

When connection establishing resources allocating completes, SP creates a TCA message and sends it to handset via control channel, if fail to send it, connection establishing fails.

Solution If there are a large volume of such failures. SP module may be internally faulty. Reset DOSDU board.



T AB L E 15 CONNECTION_SETUP_EXCEED_ONE_PILOT_F AILURE

Failure Cause Value

128

Details

When establishing a connection, if more than one sector suffers from resource allocation failure, but connection establishing does not fail, this reason will be reported by the last service observation.

Solution


1. Some carrier/sectors are abnormal and cause resource allocating failure. Solution: check CEs state with probe. Consider resetting the CHM board.

2. Malfunctions of the links between boards cause message loss. Solution: reset the suspected boards (DOSDU, the CCM that the failed sector is in, UIM and etc.);

3. Version mismatch. Solution: check the version compatibility of DOSDU, the CCM and CHM that the failed sector is in;

4. Incorrect data configuration. Solution: synchronize data towards OMP and the CCM that the failed sector is in, or check data configuration and rollback.

T AB L E 16 CONNECTION_SETUP_RCP_ ADD_CH ANNELITEM_FAILURE

Failure Cause Value

126

Details

When SP requests resource allocation from RCP, RCP has to add channel board information on DSM. If this operation fails, RCP will initiate a release against SP, connection establishing fails.

Solution


1. Version mismatch. Solution: check version compatibility of CCM and DSM

2. Data is not synchronized or data is configured incorrectly. Solution: synchronize data towards OMP and CCM, or check data configuration and rollback.



T AB L E 17 CONNECTION_SETUP_AVF_NEIGHBORLIST_PAR A_ ERROR

Failure Cause Value

125

Details

SP requests neighbor cell information from BSSAP. In the received AvfNeighborListUpdateMsg, if there is a parameter error,(e.g. :ucNumPilots is greater than the maximum number of pilot in active set, or ucBTSNumber is greater than the maximum number of neighbor cell, or the number of ChannelRecord is greater than the maximum number of pilot after saving the ChannelRecord contained in neighbor cell pilot), connection establishing fails.

Solution


1. Version mismatch. Solution: check version compatibility of DOCMP and DOSDU;

2. Incorrect data configuration. Solution: check OMC neighbor cell configuration, synchronize data towards OMP, or check data configuration and rollback.

T AB L E 18 CONNECTION_SETUP_DRCAND ACKINFO_TIMEOUT

Failure Cause Value

124

Details

After resource allocating and before sending TCA, it is needed to send AbiscfSetDRCAndAckInfo and AbiscfSetDRCLengthTransition message to all channel boards for parameter setting. If the timer expires before all replies are collected, connection establishing fails.

Solution


1. Links between boards are faulty. Solution: reset the suspected boards(DOSDU, CHM and UIM);

2. Version mismatch. Solution: check version compatibility of DOSDU, CHM and UIM;

3. Check system parameters in OMC to see if the DRCLength, DRCChannelGain, AckChanelGain, DSCChannelGain and DRCThreshold (in DRC parameter table) that correspond to different numbers of leg are correct. If not, the data configuration may be incorrect. Consider rollback.



T AB L E 19 CONNECTION_SETUP_CARRIER_ALLOCATE_TIMEOUT

Failure Cause Value

123

Details SP sends the 1st resource allocating request to RCP without reply. Connection establishing fails.

Solution


1. Links between boards are faulty. Solution: reset the suspected boards (DOSDU, CCM, UIM and etc.);

2. Version mismatch. Solution: check version compatibility of DOSDU, CCM and UIM;

3. Data is not synchronized or data is configured incorrectly. Solution: Synchronize data towards OMP and CCM, or check data configuration and rollback.

T AB L E 20 CONNECTION_SETUP_CARRIER_ALLOCATE_P AR A_ ERROR

Failure Cause Value

122

Details

SP sends the 1st resource allocating request to RCP, if in the received reply the number of leg is not 1,or the number of sector under the leg is not 1,connection establishing fails.

Solution


1. Version mismatch. Solution: check version compatibility of DOSDU, CCM and UIM;

2. CCM not works normally, reset it;

3. Data is not synchronized or data is configured incorrectly. Solution: synchronize data towards OMP and CCM, or check data configuration and rollback.

T AB L E 21 CONNECTION_SETUP_ALLOC ATE_C AR RIER_ID_ERROR

Failure Cause Value

121

Details

SP sends the 1st resource allocating request to RCP, if the CarrierId in the received reply is not found in the sector information saved in SP, the CarrierId is believed incorrect. Connection establishing fails.

Solution


1. Version mismatch. Solution: check version compatibility of DOSDU, CCM and UIM




T AB L E 22 CONNECTION_SETUP_CARRIER_ALLOCATE_F AILURE

Failure Cause Value

120

Details

SP sends the 1st resource allocating request to RCP, If the resource allocating of the 1st sector under the 1st leg that carried in the in the received reply is not 0 (0 stands for success), connection establishing fails.

Solution


1. Version mismatch. Solution:check version compatibility of DOSDU, CCM and UIM


T AB L E 23 CONNECTION_SETUP_PILOTS_NUMBER_ERROR

Failure Cause Value

119

Details

In the RU message sent over the access channel by a handset, except the reference pilot, if the number of other pilots is greater than the maximum number of pilot (15), connection establishing fails.

Solution Handset reports an error. No special handling is needed.

T AB L E 24 CONNECTION_SETUP_INVALID_PILOT_PN

Failure Cause Value

118

Details

SP cannot find the sector (it is determined by BSSAP parsing) that handsets report RU messages in the sector information carried in Av interface message, or cannot find the reference carrier parsed by BSSAP in the sector information when it processes Av interface connection establishing message, connection establishing fails.

Solution


1.There is data inconsistency between BSC and BTS. It is suggested to synchronize data towards OMP and CCM.

2. BSSAP module has internal malfunctions. It is suggested to reset DOCMP board.



T AB L E 25 CONNECTION_SETUP_CELL_NUMBER_ERROR

Failure Cause Value

117

Details

SP detects that the number of carried sector is greater than the maximum number of sector (16) when it processes Av interface connection establishing message, connection establishing fails.

Solution If there is large volume of such failures, perhaps BSSAP module has internal malfunction. It is suggested to reset DOCMP board

T AB L E 26 CONNECTION_SETUP_BTS_NUMBER_ERROR

Failure Cause Value

116

Details

SP detects that the number of carried BTS information is greater than the maximum number of sector (16) when it processes Av interface connection establishing message, connection establishing fails.

Solution If there is large volume of such failures, perhaps BSSAP module has internal malfunction. It is suggested to reset DOCMP board

T AB L E 27 CONNECTION_SETUP_PILOT_INCREMENT_ERROR

Failure Cause Value

115

Details SP detects that PilotIncrementparameter in Session information is 0 when it processes Av interface connection establishing message, connection establishing fails.

Solution If there is large volume of such failures, possibly BSSAP module has internal malfunction. It is suggested to reset DOCMP board

T AB L E 28 CONNECTION_SETUP_MAX_SOFTH ANDOFF_NUM_ERROR

Failure Cause Value

114

Details

SP detects that MaxSoftHandoffNumparameter is less than 3 or greater than 6 when it processes Av interface connection establishing message, connection establishing fails.

Solution

If there is large volume of such failures, the possible causes:

1. Data configuration is faulty. Solution:check data configuration and rollback the data;

2. BSSAP module has internal malfunction, It is suggested to reset DOCMP board and BSSAP module.



T AB L E 29 CONNECTION_SETUP_MOBILEACQUIRED_ FORW ARDDESIRED _T IMEOUT_FLOWCTRL_RECV

Failure Cause Value

112

Details After SP sends the TCA message to handset, MobileAcquired and ForwardDesired are not received after forward/reverse capture timer expires. Connection establishing fails.

Solution

View the log information at handset side to check if TCA message is received. If it is not received, there may be packet sending problem on forward control channel:timecard 1. Links between boards failed. Solution: reset the suspected boards(DOSDU, CCM, UIM and etc.);

2. Version mismatch. Solution:check version compatibility of DOSDU, CCM and UIM

If the TCA message received by handset passes the verification, the reverse demodulation of CHM is likely faulty. Make sure the chip setting parameters of CHM and the data in the DRC parameter table of system parameters are correct. Consider rollback.

T AB L E 30 CONNECTION_SETUP_FORWARDDESIRED_ T IMEOUT_FLOWCTRL_RECV

Failure Cause Value

110

Details

Upon sending the TCA message to handset, SP receives a MobileAcquired message. But ForwardDesired is not received even after forward/reverse capture timer expires. Connection establishing fails eventually.

Solution

CHM reverse demodulation has problem. The reverse demodulation of CHM is likely to be faulty. Make sure the chip setting parameters of CHM and the data in the DRC parameter table of system parameters are correct. Consider rollback.

T AB L E 31 CONNECTION_SETUP_MOBILEACQUIRED_TIMEOUT

Failure Cause Value

109

Details

Upon sending the TCA message to handset, SP receives a ForwardDesired message. But MobileAcquired is not received even after forward/reverse capture timer expires. Connection establishing fails eventually.

Solution

The reverse demodulation of CHM is likely to be faulty. Make sure the chip setting parameters of CHM and the data in the DRC parameter table of system parameters are correct. Consider rollback.



T AB L E 32 CONNECTION_SETUP_NEIHBOURLIST_TIMEOUT

Failure Cause Value

108

Details SP requests neighbor cell information from BSSAP. If AvfNeighborListUpdateMsg is not received, connection establishing fails.

Solution


1. Links between boards are faulty. Solution: reset the suspected boards(DOCMP, DOSDU, UIM and etc.);

2. Version mismatch. Solution:check version compatibility of DOCMP and DOSDU;


T AB L E 33 CONNECTION_SETUP_NO_PILOT_IN_LAST_ ROUTERUPDATE

Failure Cause Value

106

Details

After processing the Av interface connection establishing message, SP needs to find a sector to create the 1st AbiscfConnectionSetupMsg to send to RCP for requesting carrier resource allocating. If the message creation fails, connection establishing fails.

Solution


1. The RouteUpdate message reported by handset is abnormal. Be confirmed according to the Log information at handset side.

2. BSSAP module has internal malfunction, it is suggested to reset DOCMP board.

T AB L E 34 CONNECTION_SETUP_ADD_CH ANNELITEM_TIMEOUT

Failure Cause Value

105

Details

After connection establishing and resource allocating, SP needs to send an AcfBSCAddChannelItemMsg to the IGWP module on ABPM to request a new channel table. If no reply is received before the timer expires, connection establishing fails.

Solution


1. Version mismatch. Solution:check version compatibility of DOSDU and ABPM;




T AB L E 35 CONNECTION_SETUP_ADD_CH ANNELITEM_FAILURE

Failure Cause Value

104

Details

After connection establishing and resource allocating, SP needs to send an AcfBSCAddChannelItemMsg to the IGWP module on ABPM to request a new channel table. If the field dwCause in the received AcrBSCAddChannelItemAck message is not 0 (0 stands for success), connection establishing fails.

Solution


1. Version mismatch. Solution:check version compatibility of DOSDU and ABPM;


T AB L E 36 CONNECTION_SETUP_ACTIV ATE_TP_F AILURE

Failure Cause Value

103

Details

After connection establishing and resource allocating, SP needs to activate TP module to prepare for data sending. If it fails to invoke the activation function of TP module, connection establishing fails.

Solution If there is large volume of such failures, likely cause is TP module has internal malfunction. It is suggested to reset DOSDU board

T AB L E 37 CONNECTION_SETUP_TCA_ENCODE_FAILURE

Failure Cause Value

102

Details SP needs to code the TCA message before sending it to handsets via air-interface. If it fails to invoke the coding function, connection establishing fails.

Solution If there is large volume of such failures, likely cause is the internal malfunction SP module. It is suggested to reset DOSDU board

T AB L E 38 CONNECTION_SETUP_CARRIER_ALLOCATE_ERROR

Failure Cause Value

101

Details SP detects that there is no pilot in active set when it creates a TCA message, connection establishing fails.

Solution If there is large volume of such failures, likely cause is SP module has internal malfunction It is suggested to reset DOSDU board



T AB L E 39 CONNECTION_SETUP_INVALID_ ABIS_ B ANDWIDTH_DISTRIBUTED

Failure Cause Value

21

Details Abis bandwidth allocating fails

Solution If there is large volume of such failures, likely cause is Abis link has no bandwidth. Solution: wait for restore of Abis bandwidth

T AB L E 40 CONNECTION_SETUP_SDU_OVERLO ADED

Failure Cause Value

20

Details SDU overloads

Solution

There are the following possibilities:

1. On this DOSDU, there are a lot of users in forward data transmission. Solution: wait for the fall of DOSDU CPU, or add DOSDU boards.

2. Overload algorithm on DOSDU has problem. Solution: Collect information and contact local ZTE office.

T AB L E 41 CONNECTION_SETUP_CONNECTIONSETUP_TIMEOUT

Failure Cause Value

19

Details connection establishing expires

Solution Perhaps DOSDU runs abnormally. Solution: Contact local ZTE office and reset DOSDU.

T AB L E 42 CONNECTION_SETUP_INVALID_RSP_PID

Failure Cause Value

18

Details Failed to create the PID of RSP process

Solution Perhaps DOCMP runs abnormally. Solution:reset DOCMP

T AB L E 43 CONNECTION_SETUP_INVALID_PPPSESSION_PID

Failure Cause Value

17

Details the PID that creates PPPSession process fails




T AB L E 44 CONNECTION_SETUP_INVALID_BSSAP_PID

Failure Cause Value

16

Details Failed to retrieve PID of BSSAP process


T AB L E 45 CONNECTION_SETUP_INVALID_DBS_CONFIG

Failure Cause Value

14

Details Failed to retrieve negotiation parameters

Solution OMC does not have parameter configuration, or the configuration is incorrect. Solution: Configure correctly and synchronize data.

T AB L E 46 CONNECTION_SETUP_INVALID_INFO_UPDATE_POLICY

Failure Cause Value

13

Details Fail to retrieve update strategy of connection information

Solution Perhaps OMC is not configured with parameters or configuration is incorrect. Solution: Configure correctly and synchronize data.

T AB L E 47 CONNECTION_SETUP_INVALID_DRCACK_INFO

Failure Cause Value

11

Details fail to retrieve DRC and ACK channel parameters

Solution If there is large volume of such failures, likely cause is OMC is not configured with DRC parameter table. Solution: Configure correctly and synchronize data.

T AB L E 48 CONNECTION_SETUP_INVALID_LOC ATION_P AR AMETER

Failure Cause Value

10

Details Fail to retrieve Location parameters

Solution Perhaps OMC is not configured with parameters or configuration is incorrect. Solution:Configure correctly and synchronize data.



T AB L E 49 CONNECTION_SETUP_INVALID_MAX_SOFTH ANDOFF_NUM

Failure Cause Value

9

Details Fail to retrieve MaxSoftHandoffparameter

Solution Perhaps OMC is not configured with parameters or configuration is incorrect. Solution:Configure correctly and synchronize data.

T AB L E 50 CONNECTION_SETUP_INVALID_CELL_INFO

Failure Cause Value

8

Details Fail to retrieve cell parameters

Solution Likely cause is parameters are not synchronized after modification. Solution:synchronize the parameters in OMC

T AB L E 51 CONNECTION_SETUP_INVALID_RU

Failure Cause Value

7

Details fail to retrieve active pilots from RU

Solution Likely cause is parameters are not synchronized after modification. Solution:synchronize the parameters in OMC

T AB L E 52 CONNECTION_SETUP_INVALID_CELLID

Failure Cause Value

6

Details Fail to retrieve CellIdparameter

Solution Likely cause is data is not synchronized after parameter modification. Solution:synchronize the OMC parameters

T AB L E 53 CONNECTION_SETUP_INVALID_SESSION_INFO

Failure Cause Value

5

Details Fail to retrieve SessionInformationparameter

Solution Likely cause is DOCMP runs abnormally. Solution:contact local ZTE office



T AB L E 54 CONNECTION_SETUP_INVALID_SDU

Failure Cause Value

4

Details Fail to allocate SE resources, or fail to retrieve the ModuleID that SE belongs to

Solution

likely causes:

1. SE is in wrong state. Solution:check parameters in OMC;

2. System call upper limit is reached. Solution:add DOSDU board.

T AB L E 55 CONNECTION_SETUP_INVALID_CALL_PAR AMETER

Failure Cause Value

3

Details Lack of ConnectionRequest message or RouteUpdate message in connection establishment command

Solution Perhaps DOCMP runs abnormally. Solution:reset DOCMP board

T AB L E 56 CONNECTION_SETUP_INVALID_ AT

Failure Cause Value

2

Details Fail to retrieve AT object

Solution Likely cause is DOCMP runs abnormally. Solution:reset DOCMP board

T AB L E 57 CONNECTION_SETUP_NETWORK_BUSY

Failure Cause Value

1

Details Fail to create CallHandler object

Solution

Likely causes:

1. Upper limit of system calls is reached. Solution:add DOCMP board;

2. DOCMP runs abnormally. Solution:reset DOCMP board.



T AB L E 58 CONNECTION_SETUP_AMR_PAR A_ERROR

Failure Cause Value

220

Details When establishing a connection at BTS side, CES returns parameter errors in connection result

Solution

Check the EV_S_AmrConnectSetupAck (or EV_S_AmrSofterAddAck) in signaling tracking of connection establishing and the parameter fields ucCellNumber/aucCarrierCellId in EV_S_AmfConnectionSetup (or EV_S_AmfSofterAdd) to see if they are the same.

In the case they are not the same, check the CarrierCellId to see if it is the same as the OMC configuration. CES processing is not normal if they are the same.

T AB L E 59 CONNECTION_SETUP_CES_SOFTER_HANDOFF_ ADD_TIMEOUT

Failure Cause Value

219

Details

If a handset requests new pilot handoff, SP will send a message to RCP to request BTS resource allocating. In softer handoff adding on BTS, softer handoff adding of CES is timeout.

Solution

Check the signaling tracking when the connection is established to see if there is EV_S_AmrSofterAddAck.

If the problem occurs occasionally, perhaps the communication between boards is faulty. Check the CHM to see if it has alarms of links.

If the problem occurs frequently, check the CHM. If it runs abnormally, It is suggested to reset CHM

T AB L E 60 CONNECTION_SETUP_CES_CONNECTION_SETUP_TIMEOUT

Failure Cause Value

218

Details

Allocating resources for many pilots in connection establishing or handset requests handoff to add new pilots in handoffs. SP will send messages to RCP to request BTS resource allocating. When establishing a connection at BTS side, the soft handoff adding of CES is timeout.

Solution

Check the signaling tracking when the connection is established to see if there is EV_S_AmrConnectSetupAck.

If the problem occurs occasionally, perhaps the communication between boards is faulty. Check the CHM to see if it has alarms of links.

If the problem occurs frequently, check the CHM. If it runs abnormally, It is suggested to reset CHM



T AB L E 61 CONNECTION_SETUP_SECTOR_USER_OVERLO AD

Failure Cause Value

216

Details

Allocating resources for many pilots in connection establishing or handset requests handoff to add new pilots in handoffs. SP will send messages to RCP to request BTS resource allocating. In resource allocating, user overload causes resource allocating failure.

Solution

It is acceptable if the overload policy is reject new connections. However, there must be a problem if the policy is access the new connection and remove the old connection.

T AB L E 62 CONNECTION_SETUP_SECTOR_OVERLO AD_NOT_FIND_BUMP_USER

Failure Cause Value

214

Details

Allocating resources for many pilots in connection establishing or handset requests handoff to add new pilots in handoffs. SP will send messages to RCP to request BTS resource allocating. User overloading is detected in resource allocation, but the user to be removed can not be found according to the removal principle.

Solution

If appear at all times, check how many users are under the carrier/sector. If the number nearly reaches the threshold, and the user should be removed can not be found out, it is believed that the overload policy has problem.

T AB L E 63 CONNECTION_SETUP_CCM_CPU_OVERLO AD

Failure Cause Value

213

Details

Allocating resources for many pilots in connection establishing or handset requests handoff to add new pilots in handoffs. SP will send messages to RCP to request BTS resource allocating. CPU utilization of CCM reaches the threshold will cause resource allocating failure.

Solution CPU optimization is needed if this circumstance occurs frequently.



T AB L E 64 CONNECTION_SETUP_CELLINPAR A_NOTEXIST

Failure Cause Value

212

Details

Allocating resources for many pilots in connection establishing or handset requests handoff to add new pilots in handoffs. SP will send messages to RCP to request BTS resource allocating. CCM detects that the cell ID of new leg that carried in connection request is invalid will cause handoff adding failure of a leg.

Solution

Check signaling tracking to confirm if the aucCellId value (the subscript of the array that corresponds to the parameter atSetupLegInfo in the signaling EV_S_AbiscfConnectionSetup) is a valid configured cell ID

T AB L E 65 CONNECTION_SETUP_MODIFYCARRIERUSER_FAIL

Failure Cause Value

211

Details

Allocating resources for many pilots in connection establishing or handset requests handoff to add new pilots in handoffs. SP will send messages to RCP to request BTS resource allocating. In resource establishing at BTS side, database fails to record number of user will cause handoff adding failure of a leg.

Solution If it always appears, it is suggested to reset CCM board

T AB L E 66 CONNECTION_SETUP_GETDSMIP_FAIL

Failure Cause Value

210

Details

Allocating resources for many pilots in connection establishing or handset requests handoff to add new pilots in handoffs. SP will send messages to RCP to request BTS resource allocating. In resource establishing at BTS side, fail to retrieve DSM IP address from database will cause handoff adding failure of a leg.

Solution If it appears at all times, make sure BSC and BTS are synchronized. Check Abis link to see if it is normal.



T AB L E 67 CONNECTION_SETUP_GETBSCIP_FAIL

Failure Cause Value

209

Details

Allocating resources for many pilots in connection establishing or handset requests handoff to add new pilots in handoffs. SP will send messages to RCP to request BTS resource allocating. In resource establishing at BTS side fail to retrieve BSC IP address from database will cause handoff adding failure of a leg.

Solution If appear at all times, make sure BSC and BTS are synchronized. Check Abis link to see if it is normal.

T AB L E 68 CONNECTION_SETUP_BTSIP ALLOC_F AI L

Failure Cause Value

208

Details

Allocating resources for many pilots in connection establishing or handset requests handoff to add new pilots in handoffs. SP will send messages to RCP to request BTS resource allocating. In resource establishing at BTS side, fail to retrieve BTS IP address from database will cause handoff adding failure of a leg.

Solution If appear at all times, make sure BSC and BTS are synchronized. Check Abis link to see if it is normal.

T AB L E 69 CONNECTION_SETUP_CARRIERINPAR A_NOTEXIST

Failure Cause Value

207

Details

Allocating resources for many pilots in connection establishing or handset requests handoff to add new pilots in handoffs. SP will send messages to RCP to request BTS resource allocating. But the database at BTS side returns carrier parameter errors.

Solution

Confirm whether BSC and BTS have both synchronized data. If it occurs afterwards, firstly check whether tCurrentChannel and wChannelNumber in EV_S_AbiscfConnectionSetup message is an efficient frequency in BSC wireless configuration.

Make sure BSC and BTS have established data synchronization.



T AB L E 70 CONNECTION_SETUP_FOALLOC_F AIL

Failure Cause Value

205

Details

Allocating resources for many pilots in connection establishing or handset requests handoff to add new pilots in handoffs. SP will send messages to RCP to request BTS resource allocating. In connection establishing at BTS side, database fails to distribute frame offsets.

Solution Frame offset allocating failure is mainly caused by channel board malfunction. If this failure occurs frequently, reset the channel board.

T AB L E 71 CONNECTION_SETUP_CHANNELINPARA_NOTEXIST

Failure Cause Value

204

Details

Allocating resources for many pilots in connection establishing or handset requests handoff to add new pilots in handoffs. SP will send messages to RCP to request BTS resource allocating. In connection establishing at BTS side, there is no specified channel number in database records.

Solution

Check signal tracking. If the parameter bChannelIncluded of the signaling EV_S_AbiscfConnectionSetup is1, check the values of the fields of ucSystemType,ucBandClass and wChannelNumber (note: in current systems, ucSystemType and ucBandClass are 0; wChannelNumber stands for channel number)

T AB L E 72 CONNECTION_SETUP_CARRIERALLOC_F AIL

Failure Cause Value

203

Details

Allocating resources for many pilots in connection establishing or handset requests handoff to add new pilots in handoffs. SP will send messages to RCP to request BTS resource allocating. In connection establishing at BTS side, database fails to allocate carriers.

Solution

Check CHM and TRX to see if they run normally. Check CE and carrier to see if they are blocked. Check CEs to see if they are all busy.

Under the circumstance above, the board runs abnormally. Otherwise, it is suggested to reset CCM for further observation.



T AB L E 73 CONNECTION_SETUP_LEGNUMBER_FROM_SP_ERROR

Failure Cause Value

202

Details

Allocating resources for many pilots in connection establishing or handset requests handoff to add new pilots in handoffs. SP will send messages to RCP to request BTS resource allocating. The parameter ucLegNumber carried in connection request sent from SP is invalid (greater than 6)

Solution Check if the parameter ucLegNumber of EV_S_AbiscfConnectionSetup in signaling tracking is greater than 6.

T AB L E 74 CONNECTION_SETUP_CELLNUMBER_FROM_SP_ERROR

Failure Cause Value

201

Details

Allocating resources for many pilots in connection establishing or handset requests handoff to add new pilots in handoffs. SP will send messages to RCP to request BTS resource allocating:

1. The number of cell in new leg information that carried in SPs connection request is invalid (0 or the value greater than 3).

2. Cell quantity in leg message of softer handoff add contained in SP connection requirement message is invalid (0 or a value greater than 3).

Solution Check if the ucCellNumber in the parameter atSetupLegInfo of EV_S_AbiscfConnectionSetup in signaling tracking is 0 or greater than 6

T AB L E 75 CONNECTION_SETUP_GIVENCARRIER_NOUS ABLECE

Failure Cause Value

221

Details no available CE resources

Solution

1. Make sure the channel board runs normally

2. Check if the current channel board reaches the upper limit of users.

3. Confirm if the manual block is activated on the channel board.



T AB L E 76 CONNECTION_SETUP_C R AL L O C F AI L _C R I N P AR AN O T E X I S T

Failure Cause Value

222

Details carrier does not exist

Solution Check the carrier configuration in call origination cell and make sure BSC side and BTS side are synchronized.

T AB L E 77 CONNECTION_SETUP_C R AL L O C F AI L _CHMT Y P E N O T M AT C H

Failure Cause Value

223

Details channel board type mismatch

Solution

The type of channel board that distributes carriers is different from the type of the board in use.

Software has problem. Resolve the problem with BSSAP/SP.

T AB L E 78 CONNECTION_SETUP_C R AL L O C F AI L _C R I S B E AC O N

Failure Cause Value

224

Details The carriers to be allocated are beacons

Solution

1. Normally, handsets originate calls in a critical cell configured with beacons.

2. If no beacon is found in the current cell, check the carrier configurations.

T AB L E 79 CONNECTION_SETUP_C R AL L O C F AI L _C R I S U N N O R M AL

Failure Cause Value

225

Details carrier is abnormal

Solution 1. Check TRX state;

2. Confirm if the manual block is activated on the carrier

T AB L E 80 CONNECTION_SETUP_C R AL L O C F AI L _N O U S AB L E CE

Failure Cause Value

226

Details No available CE resource

Solution

1. Make sure the channel board runs normally

2. Check if the current channel board reaches the upper limit of users.

3. Confirm if the manual block is activated on the channel board.



T AB L E 81 CONNECTION_SETUP_C R AL L O C F AI L _C R I S OV E R L O AD

Failure Cause Value

227

Details carrier overloads

Solution

1. Check the number of users under the carrier and the number of overloaded users in overload parameter setting user-interface to see if the number of users under the sector reaches the overload threshold or not.

2. Adjust overload threshold according to network planning.

T AB L E 82 CONNECTION_SETUP_C R AL L O C F AI L _GE T C E L L AL L C R F AI L E D

Failure Cause Value

228

Details failure to retrieve the carrier configured under the current cell

Solution Check OMC configuration. Make sure carriers are correctly configured under the cell, and BSC side is synchronized with BTS side.

T AB L E 83 CONNECTION_SETUP_C R AL L O C F AI L _ GE T C U R C E L LAL L P R E F F AI L E D

Failure Cause Value

229

Details specified carrier allocating failure

Solution Software has problem. Resolve the problem with SP.

T AB L E 84 CONNECTION_SETUP_C R AL L O C F AI L _ GE T GI V E N B A N D C L AS S CRF AI L E D

Failure Cause Value

230

Details Carrier allocating failure in specified frequency bands

Solution Handset and software have problems. Resolve the problem with SP.


C h a p t e r 2

Handoff Failure

This chapter describes failure reason values, reasons and settlement measures for handoff failure problems.



T AB L E 85 CONNECTION_SETUP_AMR_PAR A_ERROR

Failure Reason Value

220

Reason Description

Parameter mistake in CES return results during BTS side connection setup

Settlement Measures

Check if EV_S_AmrConnectSetupAck(or EV_S_AmrSofterAddAck)in signaling tracing is consistent with message parameter field ucCellNumber and aucCarrierCellId in signaling EV_S_AmfConnectionSetup(or EV_S_AmfSofterAdd)during connection setup. If it is not, check if CarrierCellId is consistent with the configuration in OMC. If they are consistent, it means abnormality occurred in CES processing.

T AB L E 86 CONNECTION_SETUP_CES_SOFTER_H ANDOFF_ADD_TIMEOUT


219

Reason Description

While distributing resources for multiple pilots during connection setup or when cell phone requires handoff of newly-added pilot in handoff process, SP sends messages to RCP to request BTS resource distribution, and CES Softer handoff add operation is timeout during Softer handoff add at BTS side.

Settlement Measures

Check if EV_S_AmrSofterAddAck is in signaling tracing during connection setup. If it is occasional, it might be inter-board communication problem and thus check whether there is history alarm of link failure in CHM. If it is frequent, check whether CHM operation is normal. If CES operation is abnormal, resetting CHM is suggested.

Chapter 2 Handoff Failure


T AB L E 87 CONNECTION_SETUP_CES_CONNECTION_SETUP_TIMEOUT


218

Reason Description

While distributing resources for multiple pilots during connection setup or when cell phone requires handoff of newly-added pilot in handoff process, SP sends messages to RCP to request BTS resource distribution and CES soft handoff add operation is timeout in connection setup on BTS side.

Settlement Measures

Check if EV_S_AmrConnectSetupAck is in signaling tracing during connection setup.

If it is occasional, it might be inter-board communication problem and thus check whether there is history alarm of link failure in CHM. If it is frequent, check whether CHM operation is normal. If operation is abnormal, resetting CHM is suggested.

T AB L E 88 CONNECTION_SETUP_SECTOR_USER_OVERLO AD


216

Reason Description

While distributing resources for multiple pilots during connection setup or when cell phone requires handoff of newly-added pilot in handoff process, SP sends messages to RCP to request BTS resource distribution; resource distribution failure occurs because of subscriber overload during resource distribution.

Settlement Measures

This situation is normal when overload strategy is refusing new connection and is abnormal when overload strategy is accessing new connection and kicking away old connection

T AB L E 89 CONNECTION_SETUP_SECTOR_OVERLO AD_NOT_FIND_ BUMP_USER


214

Reason Description

While distributing resources for multiple pilots during connection setup or when cell phone requires handoff of newly-added pilot in handoff process, SP sends messages to RCP to request BTS resource distribution; subscriber overload is found during resource distribution, but the subscriber being kicked away can not be found based on kick-away principle in overload situation.

Settlement Measures

If this continues, check subscriber quantity under the sector; if subscriber quantity approaches threshold, and subscriber that can be kicked away can not be found, the problem lies in overload strategy.



T AB L E 90 CONNECTION_SETUP_CCM_CPU_OVERLO AD


213

Reason Description

While distributing resources for multiple pilots during connection setup or when cell phone requires handoff of newly-added pilot in handoff process, SP sends messages to RCP to request BTS resource distribution; but resource distribution fails because of CCM overload because CPU utilization ratio crosses threshold.

Settlement Measures

If this happen frequently, optimization is needed to reduce CPU utilization ration.

T AB L E 91 CONNECTION_SETUP_CELLINPAR A_NOTEXIST


212

Reason Description

While distributing resources for multiple pilots during connection setup or when cell phone requires handoff of newly-added pilot in handoff process, SP sends messages to RCP to request BTS resource distribution; if CCM finds unlawful cell ID contained in newly-built leg in connection requirement message, handoff add of a certain cell occurs.

Settlement Measures

Check signaling tracing, if aucCellId value in lower mark structure of the corresponding number group of atSetupLegInfo parameter of signaling, EV_S_AbiscfConnectionSetup is a valid cell ID configured.

T AB L E 92 CONNECTION_SETUP_MODIFYCARRIERUSER_FAIL


211

Reason Description

While distributing resources for multiple pilots during connection setup or when cell phone requires handoff of newly-added pilot in handoff process, SP sends messages to RCP to request BTS resource distribution; when database has failure in recording subscriber quantity during resource setup on BTS side, handoff add of a certain leg will occur.

Settlement Measures

If this continues, resetting CCM board is suggested.



T AB L E 93 CONNECTION_SETUP_GETDSMIP_FAIL


210

Reason Description

While distributing resources for multiple pilots during connection setup or when cell phone requires handoff of newly-added pilot in handoff process, SP sends messages to RCP to request BTS resource distribution; failure in accessing DSM IP address from database during resource setup on BTS side, handoff add of a certain leg will occur.

Settlement Measures

If this continues, confirm whether there has been synchronization of BSC and BTS, and check whether Abis link is normal.

T AB L E 94 CONNECTION_SETUP_GETBSCIP_FAIL


CONNECTION_SETUP_GETBSCIP_FAIL

Reason Description

While distributing resources for multiple pilots during connection setup or when cell phone requires handoff of newly-added pilot in handoff process, SP sends messages to RCP to request BTS resource distribution; failure in accessing BSC IP address from database during resource setup on BTS side, handoff add of a certain leg will occur.

Settlement Measures


T AB L E 95 CONNECTION_SETUP_BTSIP ALLOC_F AI L


208

Reason Description

While distributing resources for multiple pilots during connection setup or when cell phone requires handoff of newly-added pilot in handoff process, SP sends messages to RCP to request BTS resource distribution; failure in accessing BTS IP address from database during resource setup on BTS side, handoff add of a certain leg will be resulted in.

Settlement Measures




T AB L E 96 CONNECTION_SETUP_CARRIERINPAR A_NOTEXIST


207

Reason Description

While distributing resources for multiple pilots during connection setup or when cell phone requires handoff of newly-added pilot in handoff process, SP sends messages to RCP to request BTS resource distribution; database returns carrier parameter error.

Settlement Measures

Confirm whether there has been data synchronization for BSC and BTS. If it occurs afterwards, firstly check if wChannelNumber of tCurrentChannel in EV_S_AbiscfConnectionSetup message is effective frequency in BSC wireless configuration.

T AB L E 97 CONNECTION_SETUP_FOALLOC_F AIL


205

Reason Description

While distributing resources for multiple pilots during connection setup or when cell phone requires handoff of newly-added pilot in handoff process SP sends messages to RCP to request BTS resource distribution; database distribution frame offset distribution of data base fails during connection setup on BTS side.

Settlement Measures

Frame offset distribution failure is usually caused by channel board failure. If this continues, please reset channel board.

T AB L E 98 CONNECTION_SETUP_CHANNELINPARA_NOTEXIST


204

Reason Description

While distributing resources for multiple pilots during connection setup or when cell phone requires handoff of newly-added pilot in handoff process SP sends messages to RCP to request BTS resource distribution; there is no appointed frequency in database records during connection setup on BTS side.

Settlement Measures

Check signaling tracing whether the parameter of signaling EV_S_AbiscfConnectionSetup is 1; if it is, then check if these fields the values in structure of parameter tCurrentChannel (ucSystemType,ucBandClass,wChannelNumber)are correct.(note: in current system, ucSystemType and ucBandClass are both 0, while wChannelNumber refers to frequency)



T AB L E 99 CONNECTION_SETUP_CARRIERALLOC_F AIL


203

Reason Description

While distributing resources for multiple pilots during connection setup or when cell phone requires handoff of newly-added pilot in handoff process, SP sends messages to RCP to request BTS resource distribution; carrier distribution of database fails during connection setup on BTS side.

Settlement Measures

Check if CHM and TRX operate normally; check if CE and carrier are blocked; check if CE is absolutely busy CE. If the former situation takes place, it means board operation is abnormal. If the former situation does not take place, continuous observation after resetting CCM is suggested.

T AB L E 100 CONNECTION_SETUP_LEGNUMBER_FROM_SP_ERROR


202

Reason Description

While distributing resources for multiple pilots during connection setup or when cell phone requires handoff of newly-added pilot in handoff process, SP sends messages to RCP to request BTS resource distribution; leg number contained in connection requirement message sent by SP is unlawful (bigger than 6)

Settlement Measures

Check if ucLegNumber parameter of EV_S_AbiscfConnectionSetup signaling during signaling tracing is bigger than 6.

T AB L E 101 CONNECTION_SETUP_CELLNUMBER_FROM_SP_ERROR


201

Reason Description

While distributing resources for multiple pilots during connection setup or when cell phone requires handoff of newly-added pilot in handoff process, SP sends messages to RCP to request BTS resource distribution:

1. Cell number in newly-built leg message contained in connection requirement message sent by SP is null (0 or a value bigger than 3)

2. Cell number in leg message of softer handoff add in connection requirement message sent by SP is null (0 or a value bigger than 3).

Settlement Measures

Check if ucCellNumber value of number group structure of parameter atSetupLegInfo of EV_S_AbiscfConnectionSetup in signaling tracing is 0 or bigger than 3.



T AB L E 102 CONNECTION_SETUP_GIVENCARRIER_NOUS ABLECE


221

Reason Description

CE resource unavailable

Settlement Measures

1. Check channel board operation status to confirm whether it operates normally;

2. Check subscriber number under current channel board to confirm whether it has reached maximum subscriber quantity;

3. Confirm whether manual blocking is carried out for the channel board.

T AB L E 103 CONNECTION_SETUP_C RAL L O C F AI L _C R I N P AR AN O T E X I S T


222

Reason Description

carrier does not exist

Settlement Measures

Check carrier configuration of calling cell, and confirm synchronization on BSC and BTS side.

T AB L E 104 CONNECTION_SETUP_C RAL L O C F AI L _CHMT Y P E N O TM AT C H


223

Reason Description

channel board types mismatch

Settlement Measures

Channel board type of allocated distributed carrier is not the same as channel board type in actual configuration.

software problem that needs to be handled through coordinating with BSSAP/SP.

T AB L E 105 CONNECTION_SETUP_C RAL L O C F AI L _C R I S B E AC O N


224

Reason Description

Carrier that is to be distributed is beacon pilot.

Settlement Measures

1. In normal situation, mobile phone calls under critical cell that has beacon pilot;

2. If there is no beacon pilot under current cell, check carrier configuration to confirm whether it is improperly configured.



T AB L E 106 CONNECTION_SETUP_C RAL L O C F AI L _C R I S U N N O R M AL


225

Reason Description

carrier status is abnormal

Settlement Measures

1. Check whether TRX operation status is normal;

2. Check whether manual blocking is carried out on carrier.

T AB L E 107 CONNECTION_SETUP_C RAL L O C F AI L _N O U S AB L E CE


226

Reason Description

CE resource unavailable

Settlement Measures

1. Check if channel board operation status is normal;

2. Check if the subscriber quantity under current channel board has reached the maximum value.

3. Confirm whether manual blocking has been carried out on the channel board.

T AB L E 108 CONNECTION_SETUP_C RAL L O C F AI L _C R I S OV E R L O AD


227

Reason Description

Carrier is overloaded.

Settlement Measures

1. Check subscriber quantity under carrier and overloaded subscriber quantity in overload parameter configuration interface to confirm whether subscriber quantity under sector has reached overload threshold;

2. Adjust overload threshold basing on actual situation and network planning.

T AB L E 109 CONNECTION_SETUP_C RAL L O C F AI L _G E T C E L L AL L C R F AI L E D


228

Reason Description

Failure in accessing carrier configured in current cell

Settlement Measures

Check OMC configuration to confirm that carrier is normally configured under cell and that synchronization on BSC and BTS side has been carried out.



T AB L E 110 CONNECTION_SETUP_CR AL L O C F AI L _GE T C U R C E L LAL L P R E F F AI L E D


229

Reason Description

Failure in allocated carrier distribution

Settlement Measures

Software problem that needs to be solved through associating with SP.

T AB L E 111 CONNECTION_SETUP_CR AL L O C F AI L _GE T GI V E N B A N D C L AS S CRF AI L E D


230

Reason Description

failure in carrier distribution on allocated frequency band

Settlement Measures

Mobile phone and software problem that needs to be solved through associating with SP.

T AB L E 112 HANDOFF_EXCEED_ONE_PILOT_F AILURE


13

Reason Description

While switching newly-added pilot, if resource distribution failure occurs in more than one sector and this switchover does not fail, final switchover observation will submit the reason.

Settlement Measures

Possibilities for frequent failures are as follows:

1. Resource distribution failure resulted by abnormal status of partial sectors. The method is to check CE status using probe, and resetting relevant CHM board can be considered;

2. Partial messages lost because of inter-board link problem. The solving measure is to reset relevant boards (DOSDU, CCM and UIM where failure sector is)

3. Inconsistent versions. The solving method is to check whether the version of DOSDU, CCM and CHM where failure sector are compatible;

4. Abnormal data configuration. The solving method is to synchronize data on OMP and CCM where failed sectors reside, or to check data configuration and backtrack data.



T AB L E 113 HANDOFF_DRC_SETUP_ERROR


12

Reason Description

During handoff, if it is soft or half-soft handoff, sending AbiscfSetDRCAndAckInfo and AbiscfSetDRCLengthTransition message to channel board to configure relevant parameters needs to be done before sending TCA message or after receiving TCC message and wait for response. If w Result field in received Ack message is not 0 (0 means successful parameter configuration), handoff failure of this reason will be resulted in.

Settlement Measures


1. Inconsistent versions. Solving method is to check whether versions of DOSDU, CHM and UIM are compatible.

2. Check configured system parameters in OMC, correctness of DRCLength value, DRCChannelGain value, AckChanelGain value, DSCChannelGain value and DRCThreshold value that correspond to different leg number in DRC parameter list need to be confirmed. If they are incorrect, data configuration might be abnormal and backtracking data should be considered.

T AB L E 114 HANDOFF_ADDLEG_TIMEOUT


11

Reason Description

During adding process of soft handoff or half-soft handoff, newly-added legs information needs to be announced to FSP; if FSP does not return indication of successful leg adding, handoff failure will occur.

Settlement Measures

For frequent failures of this kind, internal abnormality might occur in SP or TP module; resetting DOSDU board is suggested.

T AB L E 115 HANDOFF_ATACQUIRED_TIMEOUT


10

Reason Description

SP has sent TCA message to mobile phone and has received MobileAcquired message, and ATAcquired message needs to be sent to channel board to change power control mode; if not all response messages are collected when timer is timeout, handoff failure of this reason occurs.

Settlement Measures

Several possibilities for frequent failures are as follows:

1. Inter-board link problem; the solving method is to reset relevant boards(DOSDU, CHM, and UIM




10

etc);

2. Inconsistent versions; solving method is to check versions of DOSDU, CHM, and UIM are compatible.

T AB L E 116 HANDOFF_DRC_SETUP_TIMEOUT


8

Reason Description

During handoff, if it is soft or half-soft handoff, sending AbiscfSetDRCAndAck Info and AbiscfSetDRCLengthTransition message to channel board to configure relevant parameters needs to be done before sending TCA message or after receiving TCC message, and wait for response. If not all Ack responses are collected before timer is timeout, handoff failure of this reason occurs.

Settlement Measures

Possibilities for frequent failure are as follows:

1. Inter-board link problem; solving method is to reset relevant boards (DOSDU, CHM, UIM etc);

2. Inconsistent versions; solving method is to check if versions of DOSDU, CHM, and UIM are compatible;

3. Check configured system parameters in OMC, correctness of DRCLength value, DRCChannelGain value, AckChanelGain value, DSCChannelGain value and DRCThreshold value that correspond to different leg number in DRC parameter list need to be confirmed. If those are incorrect, data configuration might be abnormal and backtracking data should be considered.

T AB L E 117 HANDOFF_INVALID_PILOT_PN


7

Reason Description

Receives RU message of mobile phone, but newly-added pilot of certain request cannot be found in neighboring message on base station side or relevant message is incomplete. Then handoff failure of this reason will be submitted to the pilot, but handoff will unnecessarily fail.

Settlement Measures


1. No configuration on neighboring cell, the solving method is to check configuration in OMC;

2. Inconsistent BSC and BTS data, the solving method is to synchronize data on OMP and CCM.

3. Abnormal data configuration, the solving method is to check data configuration, synchronize data or backtrack data.



T AB L E 118 HANDOFF_INVALID_ROUTEUPDATE


6

Reason Description

RU information of mobile phone has been received, but abnormality occurs during processing, such as sector quantity has passed the maximum carrier quantity (8), or pilot quantity under certain carrier passed the maximum pilot quantity (16), or repeated pilot occurs under certain carrier etc; these result in handoff failure of this reason.

Settlement Measures

Possibly RU message submitted by mobile phone is incorrect, which doesnt require handling.

T AB L E 119 HANDOFF_FORWARDDESIRED_TIMEOUT


5

Reason Description

During frequency-changing handoff, AN has sent TCA message to mobile phone but without receiving reverse capture message (MobileAcquired message or TCC message) for all the time until timer is timeout. This results in handoff failure.

Settlement Measures

Check log message on mobile phone side to confirm whether mobile has received TCA message. If it has not, problem might lay in transmission of forward traffic channel packet. There are following possibilities:

1. Inter-board link problem; the solving method is to reset relevant boards (DOSDU, CHM and UIMetc);

2. Inconsistent versions. The solving method is to check whether the version of DOSDU, CCM and CHM are compatible.

If mobile phone has received TCA message and confirmed its correctness, CHM reverse demodulation might have problem; checking the correctness of CHM chip configuration parameters and data in DRC parameter list is suggested and data backtracking should be considered.



T AB L E 120 HANDOFF_ AD D_CH ANNELITEM_FAILURE


4

Reason Description

During adding process of soft handoff or half-soft handoff, adding channel table for new legs is required; if Result field in response message returned by ABPM is not 0 (0 means success), handoff failure because of this reason might be caused.

Settlement Measures


1. Inconsistent versions; the solving method is to check versions of DOSDU and ABPM are compatible.

2. Abnormal data configuration; the solving method is to check data configuration and backtrack data.

T AB L E 121 HANDOFF_RESOURCE_ALLOC ATED_TIMEOUT


3

Reason Description

When base station processes RU message, resource distribution is needed for new-added pilot, and sending resource distribution request to RCP and awaiting response as well. If timer is timeout without collecting all response messages, the status of pilot under awaiting distribution situation will be recorded as that macro.

Settlement Measures

There are several possibilities for frequent failures , such as :

1. Inter-board link problem; solving method is to reset relevant board (DOSDU, CCM and UIM etc);

2. Inconsistent versions; solving method is to check whether the versions of DOSDU, CCM and UIM are compatible;

3. Data is not synchronized or data configuration is abnormal; solving method is to synchronize OMP and CCM data, or check data configuration and backtrack data.



T AB L E 122 HANDOFF_RESOURCE_ALLOC ATED_FAILURE


2

Reason Description

Base station processes mobile phone RU message; for half-soft handoff, if the first carrier distribution fails, handoff failure of this reason will be submitted. For non half-soft handoff and there is new-added pilot, which needs resource distribution, sending resource distribution request and awaiting response, if return failure of response message occurs, the status of corresponding pilot will be recorded as that macro.

Settlement Measures

A few possibilities for frequent failure are as follows:

1. Inconsistent versions; solving method is to check if the versions of DOSDU, CCM and UIM are compatible;

2. Data is not synchronized or data configuration is abnormal; solving method is to synchronize OMP and CCM data, or to check data configuration and backtrack data.

T AB L E 123 HANDOFF_TCC_TIMEOUT


1

Reason Description

AN has sent TCA message to mobile phone, but has not received TCC message, and timeout of TCC waiting timer results in handoff failure.

Settlement Measures

Check log message on mobile phone side, confirm whether mobile phone has received TCA message. If not received, packet sending of forward traffic channel might have problem. There are following possibilities:

1. Inter-board link problem; solving method is to reset relevant board (DOSDU, CHM and UIM etc);

2. Inconsistent versions; solving method is to check if the versions of DOSDU, CHM and UIM are compatible

If mobile phone has received TCA message and has checked correctness of message content, then:

1. For carrier-changing handoff, problem possibly lies in CHM reverse demodulation; checking correctness of CHM chip configuration parameters and data in DRC parameter list of system parameters and backtracking data is suggested;

2. For non carrier-changing handoff, problem possibly lies in reverse media flow; the solving method is to confirm whether CHM, DOSDU, ABPM and DSM board operation is normal and their versions are consistent; resetting these boards may be considered.


C h a p t e r 3

Reasons for Call Drop

The chapter explains the reasons and settlement measures for call drop problems.



T AB L E 124 CONNECTION_RELEASE_SESSIONCONFIG_IDP_ CONFIG_F AIL


127

Description If the negotiation for IDP protocol is failed, it will cause connection release.

Settlement Measure

If the cause occurs in individual AT, it must be the problem in AT processing.

If the cause occurs in the large number of ATs, the configuration data in OMC should be checked. (check path: DO parameternon QoS parameterradio protocol parameterIdle State Protocol parameter)

T AB L E 125 CONNECTION_RELEASE_SESSIONCONFIG_FTCM AC_CONFIG_F AIL


126

Description If the negotiation for FTCMAC protocol is failed, it will cause connection release.

Settlement Measure

If the cause occurs in individual AT, it must be the problem about AT processing.

If the cause occurs in the large number of ATs, the configuration data in OMC should be checked. (check path: DO parameternon QoS parameterradio protocol parameterForward Traffic Channel MAC Protocol parameter)

T AB L E 126 CONNECTION_RELEASE_SESSIONCONFIG_ AUTH_CONFIG_ F AIL


125

Description If the negotiation for AUTH protocol is failed, it will cause connection release.

Settlement Measure


If the cause occurs in the large number of ATs, the configuration data in OMC should be checked. (check path: DO parameternon QoS parameterradio protocol parameterAuthentication Protocol parameter)

Chapter 3 Reasons for Call Drop


T AB L E 127 CONNECTION_RELEASE_SESSIONCONFIG_ ACM AC_ CONFIG_F AIL


124

Explanation If the negotiation for ACMAC protocol is failed, it will cause connection release.

Solution


If the cause occurs in the large number of ATs, the configuration data in OMC should be checked. (check path: DO parameternon QoS parameterradio protocol parameterAccess Traffic Channel MAC Protocol parameter)

T AB L E 128 CONNECTION_RELEASE_SESSIONCONFIG_TX_ CFGCOMPLETE_ T IMEOUT


122

Explanation

The negotiation is failed because AN does not transmit the UmfCfgComplete message at timer timeout. This will cause connection release.

Solution

Generally, some protocols do not send out the negotiation completion message. It is required to analyze the detail reason according to the signaling track or check DOSDU if abnormal probes are reported.

T AB L E 129 CONNECTION_RELEASE_SESSIONCONFIG_SET_ CFGDONE_ FAILURE


121

Explanation

After the negotiation for some protocol completed, the negotiation completion message should be transmitted. Negotiation is not accomplished until SCM receives all indications. If the indication transmission is failed, it will cause negotiation failure and connection release.

Solution

Generally, some protocols do not send out the indication of negotiation completion message. It is required to analyze the detail reason according to the signaling track or check DOSDU if abnormal probes are reported.

ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop Explanation (EV-DO)

Documents

Transcript of ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop Explanation (EV-DO)