You are on page 1of 10


TBF Timer setting in BSC APO-

Background: to shorten the time in releasing the idle TBF block, resulting to more PDCHs available in the network.

DNTBFRELDELAY : Delay of releasing the downlink TBF. After the last downlink RLC data block is transmitted on the network side and all
the transmitted downlink data blocks are received, the MS is not informed to stop this downlink TBF. Instead, the state of the last data
block is forcibly set to "not received" and the RRBP flag of the last data block is retransmitted continuously so that the downlink TBF is not
released. During the downlink delay release, if the upper layer of the network side needs to transmit downlink data, the downlink RLC
block for unpacking can be transmitted in the downlink TBF for delay release. The state of the downlink TBF is changed from delay
releasing to downlink transmitting. In addition, the MS must respond to the Packet Downlink Ack/Nack message through the uplink data
block of the RRBP to exchange messages with the network side. When the MS needs to send data, the MS can send the uplink request to
the network sides through the Packet Downlink Ack/Nack with the channel request description.

UPEXTTBFINACTDELAY : Inactive period of extended uplink TBF. After the network side receives the last uplink RLC data block
(CountValue=0) of the MS supporting the extended uplink TBF, the uplink TBF is not released immediately. Instead, the uplink TBF is set to
the inactive state. In the inactive period, if the MS needs to transmit the uplink RLC data block, the MS can use the inactive uplink TBF
without rebuilding a new uplink TBF. This inactive uplink TBF is switched to the active state automatically. At the end of the inactive
period, if the MS does not transmit the uplink RLC data block, the network side sends the message Packet Uplink Ack/Nack to notify the
MS of releasing the uplink TBF. When the uplink TBF is inactive, the downlink TBF can be established according to this uplink TBF

DNTBFRELDELAY/ UPEXTTBFINACTDELAY setting in BSC_APO was successfully implemented on August 11, 2014 for BSC APO


Below are the highlights of the improvement:
CSSR improved by 4.42 (%)
HOSR slightly decreased by 0.13 (%)
DCR slightly improve by 0.48 (%)
Data Volume Traffic slightly decrease by 5.90 (Mbps)
TBF Establishment SR improve by 2.06 (%)
TBF Drop Rate improve by 2.32(%)
PDCH Blocking rate improve by 3.80 (%)

Key Performance Indicator Summary Table:

KPI Measurement BEFORE AFTER Differences (%) Remark
CSSR [%] 83.87 88.29 4.42 improve
CDR [%] 2.78 2.30 0.48 improve
TBF Estab SR [%] 94.29 96.35 2.06 improve
TBF Drop Rate [%] 7.30 4.98 2.32 improve
HOSR [%] *Including ISHO 96.55 96.43 -0.13 decrease
Downlink RLC throughput 85798.62 84787.15 -1.18 decrease
Uplink RLC throughput 24627.57 25259.66 2.57 improve
Data Volume [Mbps] 1717.74 1711.84 -0.34 decrease
PDCH Blocking Rate 9.17 5.37 3.80 improve
TCH Traffic Carried 62465.0259 64948.2799 3.98 increase
DNTBFRELDELAY 213 2400 800
In PS service: the number of successful TBF establishments value indicates that the radio environment, network parameter configuration,
network resource configuration, or network equipment.

Figure 1 shows the process of downlink EGPRS TBF establishment failure due to no channel. When the BSC receives a new downlink PDU
request from the SGSN, if the downlink EGPRS TBF establishment fails due to no channel (see measurement point A), the counter is
incremented by one.
Figure 2 The BSC can initiate the downlink EGPRS TBF establishment procedure by sending the PACKET DOWNLINK ASSIGNMENT message on
the uplink or downlink PACCH to the MS. The BSC also reserves the blocks for the MS to respond with the assignment acknowledgement
message. If the BSC receives the PACKET CONTROL ACKNOWLEDGEMENT message from the MS on the reserved blocks, then the downlink
EGPRS TBF establishment is successful. Figure 2 shows the procedure of downlink EGPRS TBF establishment on the PACCH.

Performance Measurement - Sulampapua
CSSR improve by 4.42 (%)

HOSR slightly decrease by

CDR improve by 0.48 (%)

TCH Traffic slightly increase by
3.97 (%)
Performance Measurement - Sulampapua
TBF Establishment SR
slightly improve by 2.06 (%)

TBF Drop Rate improve by
2.32 (%)

PDCH blocking rate
improve 3.80 (%)
Performance Measurement - Sulampapua
implementation implementation
Uplink RLC Throughput
improve by 2.57 (%)

Downlink RLC Throughput
slightly decrease by 1.18 (%)

Data volume (PS traffic)
slightly decrease by 0.34 (%)

TBF Establish attempt

implementation implementation
Thank You
Copyright2014 Huawei Technologies Co., Ltd. All Rights Reserved.
The information in this document may contain predictive statements including, without limitation, statements regarding the future financial and operating results, future
product portfolio, new technology, etc. There are a number of factors that could cause actual results and developments to differ materially from those expressed or implied in
the predictive statements. Therefore, such information is provided for reference purpose only and constitutes neither an offer nor an acceptance. Huawei may change the
information at any time without notice.