Gsm Immediate Assignment Failure Configuring

+200 to +299 Call Processing Device-Specific Error

Last updated: September 1, 2009

These errors are generated when a problem occurs maintaining the link between the test set and the DUT. These errors generally occur as a result of a problem on the link such as if the DUT did not respond to a message, or the user attempted to perform an invalid operation in the current instrument state.

Errors with a description beginning with "GSM call disconnected" mean that the call is dropped when the error occurs. Errors beginning with "GSM protocol failure" mean that the call is not necessarily dropped, these are informational messages.

Error Message

Description

+201 GSM call disconnected; Radio link failure (Timer T100 expiry)

Fixed Timer Messages

+202 GSM call disconnected; Immediate assignment failure (Timer T3101 expiry)

Fixed Timer Messages

+203 GSM call disconnected; Handover failure (Timer T3103 expiry)

Fixed Timer Messages

+204 GSM call disconnected; Channel assignment failure (Timer T3107 expiry)

Fixed Timer Messages

+205 GSM call disconnected; No response to page (Timer T3113 expiry)

Fixed Timer Messages

+206 GSM call disconnected; No answer (Timer T301 expiry)

Fixed Timer Messages

+207 GSM call disconnected; No response to setup (Timer T303 expiry)

Fixed Timer Messages

+210 GSM call disconnected; No response to release 2 times (Timer T308 expiry)

Fixed Timer Messages

+211 GSM call disconnected; No alert from mobile (Timer T310 expiry)

Fixed Timer Messages

+212 GSM call disconnected; No response to connect (Timer T313 expiry)

Fixed Timer Messages

+213 GSM call disconnected; Data link failure (Timer T200 expiry)

Fixed Timer Messages

+214 GSM call disconnected; Physical information repetition failed (Timer T3105 expiry)

Fixed Timer Messages

+217 GSM Call disconnected; TMSI (Temporary Mobile Subscriber Identity) reallocation failed (Timer T3250 expiry)

Fixed Timer Messages

+218 GSM call disconnected; Authentication failed (Timer T3260 expiry)

Fixed Timer Messages

+219 GSM Call disconnected; Mobile not capable of supporting the selected Channel Mode

Indicates that the mobile station cannot support the requested channel mode.

+220 GSM/GPRS operation rejected; Attempting to set BCH parameter while generating a BCH

Indicates the BS Emulator VI cannot be instantiated.

+221 GSM/GPRS operation rejected; SDCCH subchannel required is currently unavailable

This error is generated if an attempt to initiate Cell Broadcast is made and the SDCCH Subchannel is set to 2, or if Cell Broadcast is activated and an attempt is made to set the SDDCH Subchannel to 2.

+226 GSM operation rejected; Only one call can be supported at a time

Indicates an attempt at a second call being activated.

+227 GSM/GPRS operation rejected; Attempting to set MNC while generating a BCH

Indicates that the cell is turned on. The Operating Mode must be Cell Off before setting the MNC.

+228 GSM/GPRS operation rejected; Attempting to set LAC while generating a BCH

Indicates that the cell is turned on. The Operating Mode must be Cell Off before setting the LAC.

+229 GSM/GPRS operation rejected; Attempting to set MCC while generating a BCH

Indicates that the cell is turned on. The Operating Mode must be Cell Off before setting the MCC.

+230 Call operation rejected; Action not possible

Indicates an attempt to perform a BS Emulator action when the BS emulator VI is inactive.

+231 Call operation rejected; Call processing in progress

Indicates the setting Frequency Offset Mode is not allowed to changed while not idle or not attached, and the user setting is rejected. See Frequency Offset .

+232 Call operation rejected; Protocol request ignored

+233 GSM/GPRS operation rejected; Attempting to set BCC while generating a BCH

Indicates that the cell is turned on. The Operating Mode must be Cell Off before setting the BCC.

+234 GSM/GPRS operation rejected; Attempting to set NCC while generating a BCH

Indicates that the cell is turned on. The Operating Mode must be Cell Off before setting the NCC.

+235 Call operation rejected; The external device has an invalid configuration for the requested service

  • +236 Call operation rejected; Called MS is not responding
  • +236 GSM/GPRS operation rejected, Attempting to set NMO while generating a BCH
  • Indicates that the cell is turned on. The Operating Mode must be Cell Off before setting the Network Operation Mode.

+237 GSM operation rejected; Attempting to start SMS Cell Broadcast Service while not generating a BCH

+238 GPRS operation rejected; Attempting to set RAC while generating a BCH

Indicates that the cell is turned on. The Operating Mode must be Cell Off before setting the RAC.

+239 Operation rejected; Starting ping not allowed with current configuration

Indicates the CALL:DATA:PING:STARt command was received when the data connection type was not Auto.

+240

  • GSM/GPRS operation rejected; Data connection request rejected due to invalid DUT IP address
  • Operation rejected; Attempting to send SMS submit report after TR2N expired.
  • Indicates DUT IP address is invalid. May be address setting, subnet mask, or incorrect LAN IP address.
  • There are network (TR2N) and mobile station (TR2M) timers associated with the return of a SMS-SUBMIT-REPORT message. You should ensure that the time taken to respond to a SMS-SUBMIT message when using MANUAL mode is well within the limits of these timers (by at least a couple of seconds). If a request to send and SMS-SUBMIT-REPORT is received at the test set outside these time constraints, the message will not be sent to the mobile station.

+241

  • GPRS operation rejected; DUT PDP context request rejected due to data connection type not being Auto
  • Operation rejected; Attempting to send SMS submit report while mode set to Auto
  • Indicates PDP context request occurred when the connection type was not Auto.

+242

  • GPRS operation rejected; DUT and instrument are in incompatible states
  • Operation rejected; Attempting to send SMS status report while mode set to Auto
  • Indicates that the instrument and the DUT were not able to meet the other's requests.

+243

  • GPRS operation rejected; Activate PDP context request procedure failed (Timer T3385 expired 5 times)
  • Operation rejected; Too many outstanding requests, could not send SMS message
  • Context request timed out.

+244 GPRS operation rejected; Modify PDP context request procedure failed (Timer T3386 expired 5 times)

Change request for PDP context timed out.

+245 GPRS operation rejected; Deactivate PDP context request procedure failed (Timer T3395 expired 5 times)

Deactivation request timed out.

+246 GPRS operation rejected; Request PDP context activation rejected by DUT

Request to send PDP activation request rejected by DUT.

+247 DUT IP address has been cleared; PDP Context will be rejected until valid DUT address is entered

+248 GSM/GPRS operation rejected; Attempting to set MS TX Power Max CCH while generating a BCH

Indicates that the cell is turned on. The Operating Mode must be Cell Off before setting the MS TX Power Max CCH parameter.

+249 GPRS protocol failure; Cell Change procedure failed

+250 Protocol failure; Unknown error

+251

  • GSM protocol failure; No response to release (Timer T308 expiry)
  • Warning; DUT's request for the primary DNS server address has been ignored because the setting does not currently contain a valid IP address

 

+252

  • GSM protocol failure; Channel release failed (Timer T3109 expiry)
  • Warning; DUT's request for the secondary DNS server address has been ignored because the setting does not currently contain a valid IP address

 

+253

  • GSM protocol failure; (Timer T3270 expiry)
  • Warning; DUT's request for primary and secondary DNS server addresses has been ignored because both of the settings do not contain valid IP addresses

 

+254 GSM protocol failure; Unknown identity type received from mobile

Indicates that an identity type other than 1, 2, 3 or 4 was received from the MS.

+255 GSM protocol failure; Unexpected identity type received from mobile

Indicates that the MS has responded with an unexpected identity type. Example MS returned IMSI when IMEI was queried.
See CALL:MS:REPorted:IMEI? .

+256 GSM protocol failure; No response to disconnect (Timer T305 expiry)

Fixed Timer Messages

+257 GSM call disconnected; Invalid TMSI received from MS

Indicates that some of the bits received were not set to their normal or expected value for a TMSI (Temporary Mobile Subscriber Identity).

+258 GSM protocol failure; Out-of-range for timing advance

Indicates that there is a likely issue with the mobile's protocol board which is causing its timing advance to be out of the expected range.

+259 GPRS protocol failure; Received ACK/NACK for a block that has not been sent to the MS

Indicates that there is a likely issue with the mobile's protocol board as it is responding to messages that haven't been sent.

+260 GSM RR Cause; <cause identifier>

The <cause identifier> is a 4 digit hexadecimal number

+261 GSM MM Cause; <cause identifier>

The <cause identifier> is a 4 digit hexadecimal number

+262 GSM CC Cause; <cause identifier>

The <cause identifier> is a 4 digit hexadecimal number

+263 Protocol Error; RRLP Protocol Error Received from MS. Error Code 0

This error is generated if a `Protocol Error' RRLP message is received from the mobile station containing error code 0 (Undefined).

+264 Protocol Error; RRLP Protocol Error Received from MS. Error Code 1

This error is generated if a `Protocol Error' RRLP message is received from the mobile station containing error code 1(Missing Component).

+265 Protocol Error; RRLP Protocol Error Received from MS. Error Code 2

This error is generated if a `Protocol Error' RRLP message is received from the mobile station containing error code 2(Incorrect Data).

+266 Protocol Error; RRLP Protocol Error Received from MS. Error Code 3

This error is generated if a `Protocol Error' RRLP message is received from the mobile station containing error code 3(Missing IE or component element).

+267 Protocol Error; RRLP Protocol Error Received from MS. Error Code 4

This error is generated if a `Protocol Error' RRLP message is received from the mobile station containing error code 4(Message Too Short).

+268 Protocol Error; RRLP Protocol Error Received from MS. Error Code 5

This error is generated if a `Protocol Error' RRLP message is received from the mobile station containing error code 5(Unknown Reference Number).

+269 Configuration Error; Attempting to send RRLP pipe message while pipe mode is Off

+270 Configuration Error; Attempting to send specific RRLP message while pipe mode is On

Indicates that the BCH ARFCN or Cell Band was changed while the mobile station was attached (thus initiating a cell change. The mobile station had not completed the cell change procedure after 5 seconds.

+271 GPRS data connection terminated; Data connection failed to start

Indicates that the GPRS test application was unable to start the data connection with the DUT (Device Under Test).

+272 GPRS data connection terminated; Detach failure (Timer T3322 expired 5 times)

Indicates that the Detach procedure failed after five attempts. The Data Connection Status will be set to Idle.

+273 GPRS data connection terminated; Attach failure (Timer T3350 expired 5 times)

Indicates that the Attach procedure failed after five attempts. The Data Connection Status will be set to Idle.

+274 GPRS data connection terminated; Routing Area Update failure (Timer T3350 expired 5 times)

Indicates that the Routing Area Update procedure failed after five attempts. The Data Connection Status will not be changed.

+275 GPRS data connection terminated; MS unexpectedly ended TBF

Indicates that the mobile station unexpectedly ended the TBF (temporary block flow).

+276 GPRS data connection terminated; Test set timed out waiting for data from the MS

Indicates that no data was received from the mobile station in the allowed time.

+277 GPRS data connection terminated; MS timed out ACK/NACK exchanges and released the TBF

Indicates that the mobile station timed out ACK (Acknowledged) or NACK (Not Acknowledged) exchanges and released the TBF (temporary block flow). For more details about the cause of this error and suggestions on how to resolve it, see GPRS Data Connection Troubleshooting .

+278 GPRS data connection terminated; MS did not respond to uplink immediate assignment

Indicates that the mobile station did not respond to the uplink immediate assignment.

+279 GPRS data connection terminated; MS did not respond to downlink immediate assignment

Indicates that the mobile station did not respond to the downlink immediate assignment.

+280

  • GPRS data connection terminated; Test set timed out waiting for data from the MS
  • Operation rejected; Digital audio file parsing error in frame
  • Indicates that the mobile station did not respond to the test set within the allowed time
  • Indicates that the Digital audio file uploaded to the test set has parse error in frame. see Digital Audio Interface (DAI) Description

+281

  • GPRS data connection terminated; MS did not respond to packet timeslot reconfigure
  • Operation rejected; Digital audio file is not suitable for selected logical speech channel
  • Indicates that the mobile station did not respond to a packet timeslot reconfiguration request from the test set.
  • Indicates that the type of the Digital audio file is not match with the logical speech channel you have selected in the TCH Parameters. See Digital Audio Interface (DAI) Description

+282

  • The Identity Request procedure has been aborted (Timer T3370 expired 5 times)
  • Operation rejected; Digital audio file contains references to AMR codec rates not specified in the codec set

+283

  • GPRS data connection terminated; No response to network initiated detach procedure (Timer 3193 expired 5 times)
  • Operation rejected; Digital audio file is too long

+284 The Authentication procedure has been aborted (Timer T3360 expired 5 times)

  • The Authentication procedure has been aborted (Timer T3360 expired 5 times)
  • Operation rejected; Digital audio file is not available

+285

  • The PTMSI Allocation procedure has been aborted (Timer T3350 expired 5 times)
  • Operation rejected; Digital audio file playing/recording can not take place while operating mode is not active cell

+286

  • GPRS data connection terminated; MS did not respond to packet downlink assignment
  • Operation rejected; Digital audio file playing/recording can not take place while there is no active call
  • Indicates that the mobile station did not respond to a packet downlink assignment.
  • Indicates that a voice call should be set up between the MS and the test set before playing/recording the Digital audio file. See Digital Audio Interface (DAI) Description

+287

  • GPRS data connection terminated; MS did not respond to packet uplink
  • Operation rejected; Digital audio file not implemented for selected logical speech mode
  • Indicates that the mobile station did not respond to a packet uplink assignment.
  • Indicates that the type of the Digital audio file is not match with the logical speech channel you have selected in the TCH Parameters. Digital Audio Interface (DAI) Description

+288

  • GPRS operation rejected; Attempting to send GPRS SMS message while DUT is not GPRS attached
  • Operation rejected; Digital audio file can not be played as CODEC rate changes occur on both odd and even frames

+289

  • GSM/GPRS operation rejected; Attempting to send SMS message while connection type is not Auto
  • Operation rejected; Digital audio file upload/download in progress

+290

  • GPRS protocol warning; No IMSI received from MS (using default IMSI)
  • Warning; Digital audio file recording has reached maximum capacity and recording has stopped
  • This warning message occurs with some GPRS mobiles and not with others. It is an advisory message only and does not indicate failure of the test set or the mobile.
  • Indicates the test set has reached its maximum record capacity (2MB). See Digital Audio Interface (DAI) Description

+291

  • GPRS operation rejected; Attempting to select fixed allocation mode
  • Warning; Digital audio file recording has stopped due to user setting change
  • This warning message occurs when you attempt to change resource allocation to fixed allocation and the connection type is not Auto.

+292

  • GPRS protocol failure; Data arrived on unknown SAPI and has been ignored
  • Warning; Digital audio file playing has stopped due to user setting change

+293

  • GSM/GPRS Operation Rejected; The PBCCH must be disabled before sending a RRLP message
  • Warning; Digital audio file playing/recording has stopped because the call ended.
  • This error is generated if an attempt is made to send an RRLP message from the test set while the PBCCH is turned on and the mobile station could be monitoring it.
  • See Digital Audio Interface (DAI) Description

+294 GSM/GPRS Operation Rejected; Attempt to send RRLP Message outside of Active Cell operating mode

This error is generated if an attempt is made to send any RRLP message when not in Active Cell operating mode.

+295 Protocol Error; Test set could not decode RRLP message

+296 Protocol Error; Received RRLP message contains unsupported extensions, message not decoded

+297 GPRS operation rejected; Attempting to send SMS message while operating mode is not active cell

+298 Protocol Warning; User operation caused disconnect

+299 GPRS protocol warning; No PTCCH/U access burst received

telecominfo

« Prev     Main     Next »

0 Comments

by , 12-07-2011 at 06:20 PM (11506 Views)
Overview of the Immediate Assignment Success Rate :
Immediate assignment success rate indicates the success rate of the MS accessing the signaling channel. It concerns the procedure from the MS sending a channel required message to the BTS to the MS sending an establish indication message to the network.

Immediate assignment success rate is a key access counter. It directly reflects the success rate of the MS accessing the signaling channel and affects the user experience.

The immediate assignment success rate is calculated from traffic statistics. The recommended formula is as follows:
Immediate Assignment Success Rate = (Successful Immediate Assignments/Immediate Assignment Requests) x 100%

Signaling Procedure and Measurement Points
Immediate Assignment Success Rate-1.JPG

Symptom Description :

If the immediate assignment success rate decreases, the following symptoms may occur:
  1. Call setup success rate decreases.
  2. Congestion occurs frequently on the SDCCH
  3. Traffic volume on the TCH decreases
  4. Short messages cannot be successfully sent


Factors Concerning Immediate Assignment Success Rate:
1. Signaling Factors:
According to the signaling flow, the factors concerning the immediate assignment success rate during each phase are as follows:
(1) Random access request phase: whether the small interference signal on the Um interface is regarded as the random access request by the BSC. Affecting factor: Um interface problems;
(2) SDCCH assignment phase: whether the SDCCH is available after the random access request is accepted. Affecting factor: SDCCH congestion;
(3) Channel activation phase: whether the channel activation is successful after the channel assignment succeeds. Affecting factor: CHAN ACTIV NACK message is received because of equipment faults during SDCCH activation;
(4) Immediate assignment command phase: whether the timer for the acknowledgment of the immediate assignment expires. Affecting factor: Um interface problems;
(5) Link establishment phase: whether the link can be established on the SDCCH after the immediate assignment command is sent. Affecting factor: MS features.
The following analysis is based on these factors.

2 Factor Analyzing According to the Definition of the KPI :
As shown in the previous section, the following four factors are related to immediate assignment success rate: Um interface problems, SDCCH congestion, reception of CHAN ACTIV NACK because of equipment faults during SDCCH activation, MS problems.
These factors are related to the definition of the KPI. There are three formula that can define the immediate assignment success rate, the mapping between formula and factors are as follows:

Immediate Assignment Success Rate-2.JPG

Reasons for Immediate Assignment Failures :

• Answer to paging
• Emergency call
• Call reestablishment
• Other services (Orig. call, SMS, SS)
• Mobile Originating call
• Location update
• Other procedures (IMSI detach, SMS, SS, etc.)

There are three main reasons for immediate assignment failures

1. Unsuccessful Immediate Assignment Procedure, No SDCCH Available “SD Blocking”
2. Unsuccessful Immediate Assignment Procedure, No AGCH Available (AGCH Overload)
“Check for configuration being used in cell. Is it combined BCCH or non combined BCCH.”
3. Unsuccessful Immediate Assignment Procedure, assigned SDCCH is not seized by the MS (Phantom RACH Scenario)
“Check if cell is serving a very large area then we might need to increase ‘RxLevAccessMin’ as the cell is taking traffic from a large distance.

There are two cases when phantom RACHs are rejected

a. Call attempted from a high TA i.e. TA > 63
b. MS received level at the BTS in UL is less than a minimum threshold

Updated 12-31-2011 at 12:55 PM bytelecominfo

Categories
GSM

0 Replies to “Gsm Immediate Assignment Failure Configuring”

Lascia un Commento

L'indirizzo email non verrà pubblicato. I campi obbligatori sono contrassegnati *