RAB stands for Radio Access Bearer.

AS entity provides NAS to take care of information

transfer between UE and Core Network(CN). This is known as RAB.
Based on functionality and position in the system, RAB are of two main types. RB and lu
bearer. RB(Radio Bearer) is between UE and RNC entities while lu bearer is between RNC
and Core Network(CN).
RB is used for both user data as well as signalling. The RB used only for signaling purpose is
known as SRB(Signaling Radio Bearer) used in control plane.
RAB setup failures for CS voice calls

RAB SETUP FAILURES DUE TO AC FOR CS VOICE

When the RNC decides to reject the CS voice RAB request because the admission control
entity reports a failure (excluding frozen BTS reason). This happens before the RRC: RADIO
BEARER SETUP message would be sent to the UE
RAB SETUP FAILURES DUE TO BTS FOR CS VOICE
RAB assignment fails due to radio link setup or reconfiguration failure. The failure can
happen either in the Iub or in the Iur interface.
RAB SETUP FAILURE CS VOICE WPS
When allocating resources for Wireless Priority Service CS Voice RAB fails and blind InterSystem handover to GSM is not possible for example due to no neighbour cell available. In
this case RNC responds to CN with RANAP: RAB ASSIGNMENT RESPONSE("No
Resource Available").

The below happens before the RRC and RADIO BEARER SETUP message would be sent to the UE
RAB SETUP FAILURES DUE TO TRANSPORT FOR CS VOICE
RNC decides to reject the CS voice RAB request due to transport failure
RAB SETUP FAILURES DUE TO RNC FOR CS VOICE
When the RNC decides to reject the CS voice RAB request due to RNC internal failure
RAB SETUP FAILURES DUE TO FROZEN BTS FOR CS VOICE
When the RNC decides to reject the CS voice RAB request because the admission control
entity blocks the radio link establishment to ensure the setup of high priority calls.
RAB SETUP FAILURES DUE TO IUB AAL2 TRANS FOR CS VOICE
RNC decides to reject the CS voice RAB request due to Iub transport resource shortage
between RNC and WBTS.

Rrc failure extended version

RRC SETUP FAIL DUE TO HC

When the RNC decides to reject the RRC connection request because the handover control
entity reports a failure. Usually a data build issue when cellId does not exist
RRC SETUP FAIL DUE TO failure of Admission Control
When the RNC decides to reject the RRC connection request because the admission control
entity reports a failure (excluding frozen BTS reason).
RRC SETUP FAIL DUE TO BTS REASONS
When the RNC decides to reject the RRC connection request due to unsuccessful radio link
setup.

RRC SETUP FAIL DUE TO TRANS

When the RNC decides to reject the RRC connection request due to transport failure.
RRC SETUP FAIL DUE TO RNC INTERNAL REASONS
When the RNC decides to reject the RRC connection request due to RNC internal failure.
Could be due to parameter mismatch (it is difficult to troubleshoot), parameters such as- timer
expiry, L2 problem.
RRC SETUP FAIL DUE TO FROZEN BTS
When the RNC decides to reject the RRC connection request, because the admission control
entity blocks the radio link establishment, to ensure the setup of high priority calls.
RRC CONN SETUP FAIL DUE TO RNTI ALLO FAIL
When the RNC decides to reject the RRC connection request due to RNTI allocation failure
caused by RRMU overload.
RRC SETUP FAIL DUE TO IUB AAL2 TRANS
When the RNC decides to reject the RRC connection request due to Iub transport resource
shortage between RNC and WBTS.

After any of the above failure, the RNC sends an RRC: RRC CONNECTION REJECT message to the
UE.