what is the stagnat drop, reallocation drop?

please, can you explaine how to reduce the tbf fail and tbf drop, for each cause of drop or fail,, thanks

manish - 14th September 2012

(12:57 GMT)

please provide four reason to improve TBF SUCESS RATE, I AM USIN NOKIA EYESPOT SERVER FOR KPI.

Guru - 13th September 2012

(10:27 GMT)

Setting the higher value for dynamic setting also result high TBF drop

TAPAL ROY BASUNIA - 11th September 2012

(13:14 GMT)

HOW WE IMPROVE TBF SUCCESS RATE IN 2G ,DATA KPI...NOKIA SYSTEM

surendra yadav - 25th August 2011

(15:14 GMT)

i want to know that what is the impact of tbf rejection on DL_mas

bill - 20th June 2011

(05:23 GMT)

i need to improve my nw tbf drop rate, vendor is siemens, current value is b/w 6--8, i need to improve it to 03--04, what should i do? :S

Abhijit - 18th June 2011

(11:17 GMT)

Can any one tell me what is PCU Reject? What is the process to stop this rejection? Please Help me...

sudhar - 20th May 2011

(14:22 GMT)

what is the best value for N3101,N3105

bill - 1st April 2011

(12:41 GMT)

what should be the target value of tbf drop rate? and how can we improve it?

pix - 11th October 2010

hi anand,

(18:36 GMT)

TBF drop means the user looses throughput for a while (few seconds), but that's usually enough to stop the ftp transfer or prevent the webpage from being displayed fully. So yes, in the end, a tbf drop is impacting the subscriber experience. It is mostly due to radio problems (interference, coverage, mobility...), but other reasons can happen : PCU software failure, TCH traffic preempting the TBF's radio timeslots, or abis/ater failures. The failure of

the Gb interface does not impact the TBF drop (but the Gb should never fail, anyway). If it is a DL drop, the PCU will establish a new TBF for that MS in order to retransmit the data. But as I said above, it is probably too late for the MS : the webpage or the download is already stopped. If it is a UL drop, the MS is not obligated to establish the UL TBF again. It is up to the subscriber it establish it again. Regards pix

In the formula we have the accessibility seguintres plots: SDCCH Blocking, Fall and Fail SDCCH channel traffic. I wonder what the relationship between them for this indicator.

Debashis - 23rd June 2010

(13:34 GMT)

What is explain more on RLTIMEOUT and INIT MCS (DL/UL) from 6/5 to 2/1. Reragds, Debashis

van_guen - 1st April 2010

(13:50 GMT)

Hi Pix, could you please, give me more information about drops due to N3101,N3103 and Npolling, because I have problems with high level of TBF Drops in UL. The N3101,N3103 and Npolling drop causes are so high... Is it possible to adjust some parameter related to N3101 and N3103? The problems with TBF_Drop_UL comes after Extended_TBF_UL activation. Thank you in advance and wish you Happy Easter holiday :)) Rado_bg

pix - 23rd March 2010

Vikkas,

(10:02 GMT)

the equivalent for "TBF drop" is called N3101 and N3103. Cheers pix

VIKAS - 23rd March 2010

(07:45 GMT)

WAT IS THE RLTIMEOUT IN GPRS?

Pix - 13th October 2009

Hello,

(19:37 GMT)

Wrong thread... try this one : www.erlang.com/forum/erlang/thread.htx?thread=3476

cheers pix

Hamza - 12th October 2009

(13:34 GMT)

any chance of improving UL TBF Est. Success Rate? what parameters to hit?! all this data for 2.5G is meaningless

Mac - 16th September 2009

(05:20 GMT)

Hi Jacky, INIT MCS parameters are recommended fir TBF drop improvement. Just to share with you, I changed the INIT MCS (DL/UL) from 6/5 to 2/1 & I got good improvement in the Attach Success rate!!! But there was no impact on TBF drop. Perhaps u may try & share the results. Thanks.

Mac - 16th September 2009

(05:03 GMT)

Hi Jacky, Can u pl tel what exactly do u mean by redeclaring NSVCs on SGSN side? And I too am interested to know answer to Anis's querry. Thnx in advance!!

Anis Zayani - 15th June 2009

(08:52 GMT)

hello with drive test tool as TEMS Investigation where can I locate the TBF DROP rate and the TBF Establishement succes rate thanks

Other messages

Activate PDP Context Control

Last updated: November 11, 2010 This section is only applicable to the lab application. You may configure the test set to ignore or reject an Activate PDP Context Request from the UE. You can choose what value is sent in the SM Cause information element

of the Activate PDP Context Reject message using the Activate PDP Context Reject SM Cause setting. Use this function in parallel with Protocol Logging to verify that the UE behaves in a manner conforming to the standards for this situation and for each associated SM Cause value.

Activate PDP Context Reject SM Cause

When Activate PDP Context Reject State is On , you may specify what value is sent in the SM Cause information element using the Activate PDP Context Reject SM Causesetting. From the front panel, you may choose from the valid causes specified in 3GPP TS 24.008 10.5.6.6.
Activate PDP Context Reject SM Cause Cause Value (decimal) Cause Value (bits) 25 26 27 28 29 30 31 32 00011001 00011010 00011011 00011100 00011101 00011110 00011111 00100000 Cause LLC or SNDCP Failure Insufficient Resources Missing or Unknown APN Unknown PDP Address or PDP Type User Authentication Failed Activation Rejected By GGSN Activation Rejected, Unspecified Service Option Not Supported

33
34 35 36 37

00100001
00100010 00100011 00100100 00100101

Requested Service Opt Not Subscribed

Service Opt Temporarily Out of Order NSAPI Already Used Regular Deactivation QoS Not Accepted

Activate PDP Context Reject SM Cause Cause Value (decimal) Cause Value (bits) 38 39 40 41 42 43 44 45 46 00100110 00100111 00101000 00101001 00101010 00101011 00101100 00101101 00101110 Network Failure Reactivation Required Feature Not Supported Semantic Error in TFT Operation Syntactical Error in TFT Operation Unknown PDP Context Semantic Error in Packet Filter(s) Syntactical Errors in Packet Filters(s) PDP Context Without TFT Already Activated Cause

50 51 52 56
81 95 96 97 98 99 100

00110010 00110011 00110100 00111000

01010001 01011111 01100000 01100001 01100010 01100011 01100100

PDP Type IPv4 Only Allowed PDP Type IPv6 Only Allowed Single Address Bearers Only Allowed Collision With Network Initiated Request
Invalid Transaction Identifier Value Semantically Incorrect Message Invalid Mandatory Information Msg Type Non-existent/Not Implemented Msg Type Not Compatible With Protocol State IE Non-existent or Not Implemented Conditional IE Error

101

01100101

Msg Not Compatible With Protocol State

Activate PDP Context Reject SM Cause Cause Value (decimal) Cause Value (bits) 111 01101111 Cause Protocol Error, Unspecified

If you select

Custom Value

from the front panel, a value of 0 is sent to the UE.

The CALL:SERVice:GPRS:REJect:CAUSe command allows you to send any value between 0 and 255 to the UE, even those not mapped to a cause in the standard. If you send a value other than those listed in the above table via the GPIB command, the front panel setting displays CUSTOM .
Related Topics