RAB and RRC are two of the most important concepts because they are responsible for all

the negotiation
involved in those calls.

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.

So lets try to understand today - the simplest possible way - what is the RRC and RAB role in the calls
of these mobile networks in practice. As it become necessary, we will also talk about other concepts.

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.

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.
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 railcars are the RBs, and convey the information in the radio path. These wagons 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 remote control cars are the Iu bearer, and 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 Conversational RAB and the Interactive RAB can be used together, and in this case we have a case of
MultiRAB.

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)
 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.

Now that we have seen a lot about RRC and RAB, let's learn only a few more concepts today – after
all, we already have enough information presented. Let's talk about the AS and NAS.

 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.

According to what we learned today, 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).
o RANAP: Radio Access Network Application Part

As we have seen above, 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.

But now it started to get more complex, and we have already reached our goal today, which was to
learn the basics of RRC and RAB.

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. We remind you that 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 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.

RRC Connection Request: From UE to RNC

• RRC Connection Setup: RNC assigns traffic channel(i.e. transport channel) and creates SRB(Signaling Radio
Bearer).
• RRC Connection Complete
Difference between RAB vs RB vs SRB

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.

Figure-2 depicts RAB across the UMTS system end to end from UE(i.e. mobile) to MSC/SGSN.
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. There is another term 'TRB' used to refer
Traffic Radio Bearer. TRB is used in User Plane.

Based on circuit switched call (CS call) or packet switched call (PS call), RAB type lu-interface
carry either voice or data information. Following table compares RRC vs RAB.

RRC RAB
Feature
(Radio Resource Control) (Radio Access Bearer)
used for information
Function used for signaling transfer
transfer
Similarity with Same as SDCCH(Standalone Dedicated Control Same as TCH(Traffic
GSM Channel) Channel)

RRC is signalling part and RAB is Data part.

RRC is in layer3 and RAB is in between UE and CN.

RRC is part of control plane and RAB of user Plane.