introduction

To work with modern wireless networks such as UMTS and LTE, it essential that the
telecom professional has full understanding of its basic concepts, such as those that
control the call establishment and maintenance, whether it is voice (CS) or data
(PS).

In this scenario, RAB and RRC are two of the most important concepts because they
are responsible for all the negotiation involved in those calls.

What is RRC and RAB?

In addition to RAB and RRC, we still have some other terms directly involved in
context, as RB, SRB, TRB, among others. These terms are also important concepts,
since without them RAB and RRC could not exist.

To start, we can divide a call into two parts: the signaling (or control) and data (or
information). Already ahead of key concepts, we can understand the RRC as
responsible for the control, and the RAB as responsible for the information part.

What is Bearer?

it is a channel that carries Voice or Data, a logical connection between different

points (nodes) that ensures that the packets that are traveling have the same QoS
attributes. Explaining better: for each 'bearer' we have several associated
parameters, such as the maximum delay and packet loss limit and these
attributes that make sure each packet going in the same channel have the same
QoS attributes.

Explanation about RRC and RAB

the seller is the UTRAN, responsible for creating and maintaining the communication
between the UE (buyer) and CN (deposit) so that the QoS requirements of each are
met.

UTRAN: UMTS Terrestrial Radio Access Network

o NodeB

o RNC

UE: User Equipment

CN: Core Network

o MSC: for switched voice services

 o SGSN: for packet-switched services

figure1-General Flowchart

Sending requests and receipts is part of signaling, or the RRC. The shipment of
purchases is the data part, or the RAB. In our scenario, the RRC are the Rails, and
RAB is the full service of sending data between the UE and the CN.

RRC: Radio Resource Control

RAB: Radio Access Bearer

Note: the RRC is in Layer 3 - control plane, while the RAB occurs between the UE
and CN, in the user plane.

The RBs, and convey the information in the radio path. These RBs define what type
of thing will be transported, and in what quantity. Similarly, the RBs define what
type of data will in the RRC, which can be Data or Signaling. When the QoS
attributes change, then the RBs associated with that RRC connection need to be
reconfigured.

The Iu bearer carry information on Iu Interface (between the UTRAN and the CN),
either CS or PS.

RB: Radio Bearer

 Iu bearer: Iu Bearer Interface

Note: RAB is the combination of RB and Iu bearer.

The RB is a layer 2 connection between the UE and the RNC, and can be used for
Signalling and control User Data. When it is used for Signalling or Control Messages
is called SRB. And when it is used for user data is called TRB.

SRB: Signalling Radio Bearer (Control Plane)

TRB: Traffic Radio Bearer (User Plane)

Note: in an optimized network, we can find much of the traffic being handled by
HSPA bearers, even MultiRAB. This option frees resources from CE (Channel
Elements), relieving the load on R99 (that can only use these resources). However,
it should be done with caution, because if improperly configured it can degrade the
Performance Indicators with Blockage (Congestion) and Failures.

why we have two types of carriers -RBs and Iu ? The answer to this is in the very
characteristic of the two existing paths. Being the Iu a more robust interface, and
also because we have major changes in RABs during connections, it is normal that
these bearers are also different for the paths. it's like using a 4x4 pickup truck to
climb a mountain, and a race car to an asphalt race.

A RRC connection exists when an UE performs the call establishment procedure, and
get resources from the UTRAN. When a RRC connection is established, the UE will
also get some SRBs. (If for some reason the initial request is not accepted, the UE
can make a new request after some time).

Since the SRB was established between the UE and the CN, the RNC checks a series
of information such as the UE identity, what is the reason for the request and
whether the UE is able to handle the requested service.

The RNC that maps the requested RABs into RBs, to transfer between the UE and
the UTRAN. In addition it is also check the attributes of the RABs: if they can be met
by the available resources, and even whether to activate or reset radio channels
(reconfiguration of lower layers services ) based on the number of Signaling
Connections and RABs to be transferred.

This way, it creates the impression that there is a physical path between the UE and
the CN. Remembering again that no matter how many signaling and RABs
connections there are between the ue and the CN - there is only a single RRC
connection used by the RNC to control and transfer between the UE and the UTRAN.

A RRC connection exists when an UE performs the call establishment procedure, and
get resources from the UTRAN. When a RRC connection is established, the UE will
also get some SRBs. (If for some reason the initial request is not accepted, the UE
can make a new request after some time).
Since the SRB was established between the UE and the CN, the RNC checks a series
of information such as the UE identity, what is the reason for the request and
whether the UE is able to handle the requested service.

The RNC that maps the requested RABs into RBs, to transfer between the UE and
the UTRAN. In addition it is also check the attributes of the RABs: if they can be met
by the available resources, and even whether to activate or reset radio channels
(reconfiguration of lower layers services ) based on the number of Signaling
Connections and RABs to be transferred.

This way, it creates the impression that there is a physical path between the UE and
the CN. Remembering again that no matter how many signaling and RABs
connections there are between the ue and the CN - there is only a single RRC
connection used by the RNC to control and transfer between the UE and the UTRAN.

AS Access Stratum is a group of specific protocols of access network

NAS NON Access Stratum: so, are the other protocols, or those that are not
access network

At this point of view, the AS provides the RAB to the NAS, or information transfer
service.

The UE and CN need to communicate (events/messages) with each other to perform

several procedures with many purposes. And the 'language' of this conversation
between them is called protocols.

The protocols are then responsible for allowing this conversation between the UE
and CN, and cause the CN do not worry about the method of access (be it
GSM/GPRS, UTRAN, LTE). In our case the RNC acts as a protocol - between the
UTRAN and CN.

the RAB is carried:

Between the UE and the UTRAN: within the RRC connection. The RRC Protocol is
responsible for negotiating the (logical) channels of Uu and IuB interfaces, and for
the establishment of signaling dedicated channels as SRBs and RBs among these
interfaces.

Between the RNC and the CN: after being negotiated and mapped, in the RANAP
protocol connection, through Iu interface (CS/PS).

RANAP: Radio Access Network Application Part

The RNC maps requested RABs into RBs using current radio network resources
information, and controls the services of lower layers. To optimize the use of these
resources, as well as the network band and physical resource sharing between
different entities, the UTRAN can also perform the function of CN messages
distribution.

For this, the RRC Protocol transparently transfers messages from CN to the access
network through a direct transfer procedure. When this occurs, a specific indicator
of CN is inserted in these messages, and the entities with the distribution function in
RNC use this same indicator for direct messages to the appropriate CN, and vice
versa.

RRC Connection and RAB example

Whenever the UE needs the UTRAN resources, he asks. So that these resources are
allocated, it establishes a RRC connection with some SRBs.

In this case, a RAB connection is created to enable the transfer of user data. and as
we know the RAB consists of RB + Iu bearer. The RAB is created by CN, with a
specific QoS request.

For a single UE, there may be multiple RAB for NAS service (CS or PS).

But let's just stick to the initial procedure, that is, how is performed the 'RRC Setup'
procedure, from the UE's request.

The following figure shows this more straightforward:

figure2- RRC Connection and RAB example

The RRC has always 3 steps:

1. The UE requests a new connection in the Uplink (RRC CONNECTION

REQUEST);
 2. With sufficient resources available, the 'RRC Downlink CONNECTION SETUP'
message is sent, including the reason, along with the SRB configuration;
(Note: otherwise, if the RRC connection cannot be established, the message
sent is 'RRC CONNECTION SETUP REJECT').

3. If all goes well, the UE sends the message in the Uplink: RRC CONNECTION
SETUP COMPLETE.

And after this, the MEASUREMENT CONTROL message are being sent in the
Downlink, for the communication continuity.

After the RRC connection is established, the UTRAN makes the checks between the
CN and the UE, for example the authentication and security operations.

And so, the CN informs the RAB to UTRAN in accordance with requirements of the
service requested by the UE. As we have seen, RAB occurs after the RRC, and
without a RRC connection no RAB may be established.

Low success rate of RRC setup

This section analyzes possible causes of low success rate of RRC setup. It also
describes phenomena of problems about traffic statistics indexes and corresponding
solutions.
In traffic statistics, the major causes of RRC connection setup failure include the
following types:
The RRC connection request is rejected due to lub interface failure
The RRC connection request is rejected due to network congestion
The RRC connection fails due to no response
The RRC connection fails due to redirection
At the RNC side, the RRC connection setup failure includes two situations:
After the RNC receives the RRC Connection Request message from UE, it sends UE
the RRC Connection Reject message. This corresponds to the first two major causes
listed previously.

At the RNC side, the RRC connection setup failure includes two situations:
After the RNC receives the RRC Connection Request message from UE, it sends UE
the RRC Connection Reject message. This corresponds to the first two major causes
listed previously.
 Figure 3: Position for counting point by counter for RRC connection rejection

After the RNC sends the RRC CONNECTION SETUP message, it fails to receive the
RRC CONNECTION SETUP COMPLETE or RRC CONNECTION SETUP FAILED message
from UE. This corresponds to the third cause listed previously.
RRC Connection Request Rejection due to lub Interface Failure

The RRC connection request rejection is rejected due to lub interface failure, with
the following detailed causes:
RRC connection setup rejection due to RL setup failure
RRC connection setup rejection due to AAL2 setup failure
The corresponding traffic statistics counters:

Counter name Counter description

It counts the times that RRC connection setup is rejected due to RL setup
VS.RRC.Rej.RL.Fail
failure

VS.RRC.Rej.AAL2. It counts the times that RRC connection setup is rejected due to AAL2
Fail synchronization failure

Table 1: Counters related to RRC connection request rejection due to lub interface
failure.

RRC connection setup rejection due to RL setup failure RL setup seldom fails. It
might be due to:
Hardware problems of NodeB. For example, power amplifiers are overheated
(seldom).
Restricted number of CEs on NodeB. When the estimation of NodeB credits
are too incorrect to actually reflect the usage conditions of NodeB CEs, the
RNC judges that the NodeB CEs are enough, so the RNC sends NodeB the RL
setup message. Consequently, the NodeB responds RL setup failure due to
restriction of CEs.
When the RL setup failure leads to that RRC connection rejected times is unequal to
0, you must:
1. Check the cell load to confirm that restriction on number of CEs is not
present.
2. Check whether there are equipment alarms.
3. Confirm that there is no failure due to air-conditioner and power amplifier
problems.
RRC Connection Request Rejection due to Network Congestion

Find the type of resource that causes RRC connection request rejection due to
network congestion. The congestion of radio resources includes the following types:
Failure in application for power resource
Failure in application for uplink CE resource
Failure in application for downlink CE resource
Failure in application for code resource
 Others
RRC Connection Request Rejection due to Network Congestion

Find the type of resource that causes RRC connection request rejection due to
network congestion. The congestion of radio resources includes the following types:
Failure in application for power resource
Failure in application for uplink CE resource
Failure in application for downlink CE resource
Failure in application for code resource
Others
Table below lists the counters related to RRC connection request rejection due to
network congestion.

Counter name Counter description

It counts the times that RRC connection setup is rejected due to network
RRC.FailConnEstab.Cong
congestion. It is the total rejection times due to congestion.

It counts the times that RRC connection setup is rejected due to failure in
VS.RRC.Rej.Power.Cong
application for cell power resource.

It counts the times that RRC connection setup is rejected due to failure in
VS.RRC.Rej.UL.CE.Cong
application for uplink CE resource.

It counts the times that RRC connection setup is rejected due to failure in
VS.RRC.Rej.DL.CE.Cong
application for downlink CE resource.

It counts the times that RRC connection setup is rejected due to failure in
VS.RRC.Rej.Code.Cong
application for code resource.

Table 2: Traffic counters for RRC connection request rejection due to network
congestion.

The previous indexes are cell-level indexes.

Failure in application for power resource: When application for power resource
fails, you must check whether the configuration of admission parameters is
consistent with the default. If the parameters are properly configured, you
need check the current network load by traffic counter and the counter for
equivalent number of subscriber. If the network load and congestion rate
actually meet the expansion requirements, start network expansion.
Failure in application for uplink/downlink CE resource: When the NodeB CE
resource is inadequate; you must check the configuration of NodeB CE
resource based on the current actual traffic load.
 Failure in application for code resource: When the code resource is
inadequate, you must provide rational expansion methods based on actual
traffic load.
Others: There are few such cases, and they are usually product problems.
Therefore, this part neglects it.
RRC Connection Failure due to No Response

Table below lists the counter related to RRC connection failure due to no response.
Counter related to RRC connection failure due to no response

Counter name Counter description

RRC.FailConnEstab.NoRe
It counts the times that RRC connection setup fails due to no response
ply

Table 3: RRC fail counters due to No Response

The RRC.FailConnEstab.NoReply is a cell-level index.

The major causes of the problem include the following two types:
The UE fails to receive the RRC CONNECTION SETUP message from RNC. The
cause of the problem is irrational configuration of coverage, cell selection and
cell reselection parameters.
After the UE send the RRC CONNECTION SETUP COMPLETE message, but the
RNC does not receive it.
o Maybe the initial transmit power of uplink DCH is over low.
o Change PRACH procedure in order to increase probability of access.
The power allocation of AICH directly affects the demodulation of AI by
UE.
o If the power is over low, the UE cannot demodulate AI correctly;
therefore connection to network fails. The AICH power is set to 12 dB
by default. Change the default AICH power to 6 dB or higher according
to situation.
o The RNC receives the RRC connection request message and sends the
RRC connection setup message. However, the downlink signals are
weak, so the UE fails to receive the RRC connection setup message.
The default FACH power is 1 dB. To raise the receiving success rate
when Ec/Io power is 14 dB, raising the FACH power by 2 dB.
RRC Connection Request Rejection due to Redirection

After the UE sends the RRC connection setup request message, the redirection
algorithm is triggered if the cell is congestion or assigning resources (mainly the
admission and code resource assignment) fails, and the entire RRC direct retrial
algorithms fail. If the serving cell of originating UE has inter-frequency neighbor cell
or GSM cell, the UE is indicated by the IE Redirection info of RRC connection reject
message to redirection to the frequency point of inter-frequency neighbor cell or
GSM cell. If there is no inter-frequency neighbor cell or GSM cell, the IE Redirection
info of RRC connection reject message is not configured.
Counter name Counter description

VS.RRC.Rej.Redir.Inter.Att interfrequency cell

VS.RRC.Reject.Redir.Intrat interfRAT cell info

Table 4: Counters related to RRC connection setup rejection due to redirection

These two indexes are cell-level indexes.

To solve this issue, check original cause of rejection, in order to reduce number of
redirection.

Low success rate of CS RAB setup

The causes of CS RAB assignment setup failure in traffic statistics include:
Radio network problems
Transmission network problems
Other problems

Figure 4: Position for counting point by counter for CS RAB assignment failure in RNC
statistics.

When the RNC sends CN the RAB ASSIGNMENT RESPONSE message with the cause
failure, the corresponding counter starts working according to specific failure
causes. The RB SETUP process is marked in broken line and is optional.

Radio Network Problems

RAB assignment setup fails due to radio network problems with the following
detailed types:
CS RAB assignment setup failure due to relocation
CS RAB assignment setup failure due to air interface failure
CS RAB assignment setup failure due to insufficient capability
 CS RAB assignment setup failure due to other problems of radio networks
Table below shows the traffic statistics counters related to CS RAB assignment setup
failure due to radio network problems.

Counter name Counter description

VS.RAB.FailEstabCS.RN It counts the times that CS RAB assignment setup fails due to radio
L network problems. It counts the total failure times.

VS.RAB.FailEstCS.Relo It counts the times that CS RAB assignment setup fails due to relocation.

VS.RAB.FailEstCS.RIPF It counts the times that CS RAB assignment setup fails due to air interface
ail failure.

It counts the times that CS RAB assignment setup fails due to insufficient
VS.RAB.FailEstCS.Unsp
capability.

Table 4: Traffic counters for CS RAB assignment setup failure due to radio network problems

The indexes listed in table above are cell-level indexes.

CS RAB assignment setup fails due to relocation: When the RNC carries out
relocation, it receives the RAB ASSISNMENT REQUEST message, and then it
will not respond to the message but respond the RAB ASSISNMENT RESPONSE
message directly to CN (due to Relocation Triggered). This index is seldom
present, so neglect it.
CS RAB assignment setup fails due to air interface failure: After the RNC
receives the RB Setup Failure message from UE, it sends the RAB Assignment
Response message to CN due to Failure in the Radio Interface Procedure. To
analyze CS RAB assignment setup fails due to air interface failure, you must
analyze the causes of RB setup failure.
CS RAB assignment setup fails due to insufficient capability: The detailed
causes of CS RAB assignment setup failure due to insufficient capability
include:
o Requested Traffic Class not Available
o Requested Maximum Bit Rate not Available
o Requested Maximum Bit Rate for DL not Available
o Requested Maximum Bit Rate for UL not Available
o Requested Guaranteed Bit Rate not Available
o Requested Guaranteed Bit Rate for DL not Available
o Requested Guaranteed Bit Rate for UL not Available
o Requested Transfer Delay not Achievable
CS RAB assignment setup fails due to insufficient capability when the cell is
congested, such as Requested Maximum Bit Rate not Available. Note that the
causes of the indexes include the following causes of failure due to radio resource
congestion:
CS RAB is rejected due to inadequate power
 CS RAB is rejected due to uplink CE resource
CS RAB is rejected due to downlink CE resource
CS RAB is rejected due to code resource
CS RAB is rejected due to inadequate IUB bandwidth
Others

Counter name Counter description

VS.RAB.FailEstCs.Power.C It counts the times that CS RAB assignment fails due to power resource
ong congestion

VS.RAB.FailEstCs.ULCE.C It counts the times that CS RAB assignment fails due to uplink CE
ong congestion

VS.RAB.FailEstCs.DLCE.C It counts the times that CS RAB assignment fails due to downlink CE
ong congestion

VS.RAB.FailEstCs.Code.Co It counts the times that CS RAB assignment fails due to code resource
ng congestion

VS.RAB.FailEstCs.IUB.Ban It counts the times that CS RAB assignment fails due to inadequate IUB
d bandwidth

Table 5: Traffic counters for CS RAB assignment setup failure due to insufficient
capability.

The previous indexes are cell-level indexes.

By querying related indexes, determine the type of resource that causes failure and
perform corresponding correction/expansion solutions.
CS RAB assignment setup fails due to other problems of radio networks. Other
causes may lead to CS RAB assignment setup failure, such as no response to RB
setup.

Transmission Network Problems

The detailed causes of CS bearer setup failure which causes RAB assignment
setup failure include:
Signaling Transport Resource Failure
Iu Transport Connection Failed to Establish
Counter name Counter description

It counts the times that CS RAB assignment setup fails due to transmission network
VS.RAB.FailEstabCS.TNL
problems

Table 6: Counter for CS RAB assignment setup failure due to transmission network
problems.

The VS.RAB.FailEstabCS.TNL is a cell-level index.

If VS.RAB.FailEstabCS.TNL is present, there are probably transmission
problems. You must check whether the transmission at lu interface is normal.
Other Causes

The index seldom occurs, so this document neglects it.

Lower success rate PS RAB setup

The causes of PS RAB assignment setup failure in traffic statistics include:
Radio network problems
Transmission network problems
No resource available
Other problems

Figure 5: Position for counting point by counter for PS RAB assignment failure in RNC
statistics.

At the point B, when the RNC sends CN the RAB ASSIGNMENT RESPONSE
message with the cause failure, the corresponding counter starts working
according to specific failure causes. The RB SETUP process is marked in
broken line and is optional.

Radio Network Problems

 RAB assignment setup fails due to radio network problems with the following
detailed types:
PS RAB assignment setup failure due to parameter errors
PS RAB assignment setup failure due to relocation
PS RAB assignment setup failure due to air interface failure
PS RAB assignment setup failure due to insufficient capability
PS RAB assignment setup failure due to other problems of radio
networks

Counter name Counter description

It counts the times that PS RAB assignment setup fails due to parameter
VS.RAB.FailEstPS.Par
errors. It counts the total failure times.

VS.RAB.FailEstPS.Relo It counts the times that PS RAB assignment setup fails due to relocation.

VS.RAB.FailEstPS.RIPFai It counts the times that PS RAB assignment setup fails due to air interface
l failure.

It counts the times that PS RAB assignment setup fails due to insufficient
VS.RAB.FailEstPS.Unsp
capability.

Table 7: Traffic counters for PS RAB assignment setup failure due to radio network problems.

PS RAB assignment setup fails due to parameter errors. The index is

seldom present, so this part neglects it. The detailed causes include:
o Invalid RAB Parameters Value
o Invalid RAB Parameters Combination
o Condition Violation for SDU Parameters
o Condition Violation for Traffic Handling Priority
o Condition Violation for Guaranteed Bit Rate.
PS RAB assignment setup fails due to relocation: When the RNC carries
out relocation, it receives the RAB ASSISNMENT REQUEST message,
and then it will not respond to the message but respond the RAB
ASSISNMENT RESPONSE message directly to CN (due to Relocation
Triggered). This index is seldom present, so neglect it.
PS RAB assignment setup fails due to air interface failure
After the RNC receives the RB Setup Failure message from UE, it sends
the RAB Assignment Response message to CN due to Failure in the
Radio Interface Procedure.
To analyze PS RAB assignment setup fails due to air interface failure,
you must analyze the causes of RB setup failure. For details, see RB
setup failure in Error: Reference source not found.
 PS RAB assignment setup fails due to insufficient capability
The detailed causes of PS RAB assignment setup failure due to
insufficient capability include:
o Requested Traffic Class not Available
o Requested Maximum Bit Rate not Available
o Requested Maximum Bit Rate for DL not Available
o Requested Maximum Bit Rate for UL not Available
o Requested Guaranteed Bit Rate not Available
o Requested Guaranteed Bit Rate for DL not Available
o Requested Guaranteed Bit Rate for UL not Available
o Requested Transfer Delay not Achievable
Note that the causes of the indexes include the following causes of
failure due to radio resource congestion:
PS RAB is rejected due to inadequate power. PS RAB is rejected due to
uplink CE resource.
PS RAB is rejected due to downlink CE resource.
PS RAB is rejected due to code resource.
Others

Counter name Counter description

VS.RAB.FailEstPs.Power.Co It counts the times that PS RAB assignment fails due to power resource
ng congestion

VS.RAB.FailEstPs.ULCE.Co It counts the times that PS RAB assignment fails due to uplink CE
ng congestion

VS.RAB.FailEstPs.DLCE.Co It counts the times that PS RAB assignment fails due to downlink CE
ng congestion

VS.RAB.FailEstPs.Code.Con It counts the times that PS RAB assignment fails due to code resource
g congestion

It counts the times that PS RAB assignment fails due to inadequate IUB
VS.RAB.FailEstPs.IUB.Band
bandwidth

Table 8: Traffic counters for PS RAB assignment setup failure due to insufficient capability.

The previous indexes are cell-level indexes.

By querying related indexes, determine the type of resource that causes
failure and carry out corresponding correction/expansion solutions.
PS RAB assignment setup fails due to other problems of radio networks.
 Other causes may lead to PS RAB assignment setup failure, such as no
response to RB setup.
Transmission Network Problems

The detailed causes of PS bearer setup failure which causes RAB assignment
setup failure include:
Signaling Transport Resource Failure
Iu Transport Connection Failed to Establish

Counter name Counter description

It counts the times that PS RAB assignment setup fails due to transmission network
VS.RAB.FailEstabPS.TNL
problems

Table 9: Counter related to PS RAB assignment setup failure due to transmission network
problems.

The VS.RAB.FailEstabPS.TNL is a cell-level index.

If VS.RAB.FailEstabPS.TNL is present, there are probably transmission
problems. You must check whether the transmission at lu interface is normal.
No Resources Available

Table below shows the counter related to PS RAB setup failure due to no
resource available.

Counter name Counter description

VS.RAB.FlEstPS.Str.NResAv
It counts the times that PS RAB setup fails due to no resource available
ail

Table 10: Counter related to PS RAB setup failure due to no resource available.

VS.RAB.FlEstPS.Str.NResAvail is a cell-level index. The resource referred in

table above includes the equipment resources excluding radio layer
resources (such as power resource, code resource, and CE resource).
VS.RAB.FlEstPS.Str.NResAvail is seldom present, so this document neglects it.

Other Causes

The index seldom occurs, so this document neglects it.

 For HSDPA service, the cause of low success rate of RAB assignment is the
same as that of R99 PS RAB assignment. The traffic statistics indexes of PS
RAB involve R99 PS service and HSDPA service.

Low success rate of RB setup

The major causes of lower success rate of RB setup include the following two types:

RB setup failure
No response to RB setup
RB Setup failure

RB setup failure: after the RNC sends the RB Setup message, it receives the
RB Setup Failure message from UE.
The detailed causes of RB setup failure include:
Unsupported configuration
Physical channel failure
Cell update occurrence
Invalid configuration
In traffic statistics of RNC, the counter for RB setup failure starts counting at
the point A shown in figure below.

Figure 6: Position for counting point by counter for RB setup failure in traffic statistics.

Counter name Counter description

VS.FailRBSetup.CfgUnsup RB setup fails due to unsupported cell configuration

VS.FailRBSetup.PhyChFail RB setup fails due to cell physical channel failure

VS.FailRBSetup.CellUpd RB setup fails due to cell update

VS.FailRBSetup.IncCfg RB setup fails due to invalid cell configuration

Table 11: Traffic statistics counters related to RB setup failure.

The previous indexes are cell-level indexes.

Unsupported configuration: This is due to maloperations by
subscribers. For example, when using downlink 128K data service, a
subscriber receives the RB setup request (originating or terminating
VP) of VP service, the UE directly responds RB setup failure due to
unsupported configuration, namely, most UEs fails to support using VP
and high speed (>= 64K) PS service simultaneously.
Physical channel failure: It seldom occurs.
Cell update occurrence: Cell update occurs during RB setup. It seldom
occurs, so this document neglects it.
Invalid configuration: This is a common cause of RB setup failure. It is
possible that the 3G UE originates VP service to an terminating MS that
camps on GSM cells and that does not support VP service, so after the
RNC receives the RAB assignment request, the CN immediately sends
the Disconnect command with the cause Bearer capability not
authorized after call proceeding. Consequently, the UE receives the
RB_SETUP message and has not completed RB setup, so it responds RB
setup failure upon receiving the Disconnect message, and then the
RNC responds RAB setup failure.
No response to RB Setup

Table below lists the traffic statistics counter related to no response to RB

setup.

Counter name Counter description

VS.FailRBSetup.NoReply RB setup fails due to no response to cell RB setup

Table 12: Traffic statistics counter related to no response to RB setup.

The previous index is a cell-level index.

This is a common cause of RB setup failure. The RB setup fails because that
the UE fails to receive RB SETUP message or the RNC fails to receive
response from UE. This occurs in weak coverage areas due to two causes:
The UE does not originates a call in the best server
The coverage is weak
For both situation a coverage based action is required.