RRM functions

Radio Bearer Control (RBC)

The establishment, maintenance and release of Radio Bearers involve the
configuration of radio resources associated with them. When setting up a
radio bearer for a service, radio bearer control (RBC) takes into account the
overall resource situation in E-UTRAN, the QoS requirements of in-progress
sessions and the QoS requirement for the new service. RBC is also concerned
with the maintenance of radio bearers of in-progress sessions at the change
of the radio resource situation due to mobility or other reasons. RBC is
involved in the release of radio resources associated with radio bearers at
session termination, handover or at other occasions. RBC is located in the
eNB.
Radio Admission Control (RAC)
The task of radio admission control (RAC) is to admit or reject the
establishment requests for new radio bearers. In order to do this, RAC takes
into account the overall resource situation in E-UTRAN, the QoS
requirements, the priority levels and the provided QoS of in-progress
sessions and the QoS requirement of the new radio bearer request. The goal
of RAC is to ensure high radio resource utilization (by accepting radio bearer
requests as long as radio resources available) and at the same time to
ensure proper QoS for in-progress sessions (by rejecting radio bearer
requests when they cannot be accommodated). RAC is located in the eNB.
Connection Mobility Control (CMC)
Connection mobility control (CMC) is concerned with the management of
radio resources in connection with idle or connected mode mobility. In idle
mode, the cell reselection algorithms are controlled by setting of
parameters (thresholds and hysteresis values) that define the best cell
and/or determine when the UE should select a new cell.
Also, E-UTRAN broadcasts parameters that configure the UE measurement
and reporting procedures. In connected mode, the mobility of radio
connections has to be supported. Handover decisions may be based on UE
and eNB measurements. In addition, handover decisions may take other
inputs, such as neighbour cell load, traffic distribution, transport and
hardware resources and Operator defined policies into account. CMC is
located in the eNB.
Dynamic Resource Allocation (DRA) - Packet Scheduling (PS)

The task of dynamic resource allocation (DRA) or packet scheduling (PS) is to

allocate and de-allocate resources (including buffer and processing
resources and resource blocks (i.e. chunks)) to user and control plane
packets. DRA involves several sub-tasks, including the selection of radio
bearers whose packets are to be scheduled and managing the necessary
resources (e.g. the power levels or the specific resource blocks used). PS
typically takes into account the QoS requirements associated with the radio
bearers, the channel quality information for UEs, buffer status, interference
situation, etc. DRA may also take into account restrictions or preferences on
some of the available resource blocks or resource block sets due to inter-cell
interference coordination considerations. DRA is located in the eNB.
Inter-cell Interference Coordination (ICIC)
Inter-cell interference coordination has the task to manage radio resources
such that inter-cell interference is kept under control. ICIC mechanism
includes a frequency domain component and time domain component. ICIC
is inherently a multi-cell RRM function that needs to take into account
information (e.g. the resource usage status and traffic load situation) from
multiple cells. The preferred ICIC method may be different in the uplink and
downlink. The frequency domain ICIC manages radio resource, notably the
radio resource blocks.
For the time domain ICIC, Almost Blank Subframes (ABSs) are used to protect
resources receiving strong inter-cell interference. MBSFN subframes can be
used for time domain ICIC when they are also included in ABS patterns. The
eNB cannot configure MBSFN subframes [4] as ABSs when these MBSFN
subframes are used for other usages (e.g., MBMS, LCS). ICIC is located in the
eNB.
You might also like:

RIV is a number to specify PDSCH or PUSCH resource allocation. In more intuitive form,
we normally use two values (i.e, Number of RBs and Start RB) for the resource
allocation. But with RIV, we can represent Number of RBs and Start RB in a single value.
It would have some advantage in terms of number of bits to carry the information.. but
it causes some confusion for us to convert RIV into Number of RBs and Start RB.

Code Rate
In simple words, code rate can be defined as how effectively data can be transmitted in 1ms
transport block or in other words, it is the ratio of actual amount of bits transmitted to the
maximum amount of bits that could be transmitted in one transport block
code rate = (TBS + CRC) / (RE x Bits per RE)
where
TBS = Transport block size as we calculated from Table 7.1.7.2.1-1
CRC = Cyclic redundancy check i.e. Number of bits appended for error detection
RE = Resource elements assigned to PDSCH or PUSCH
Bits per RE = Modulation scheme used
While we know the values of TBS, CRC and bits per RE (modulation order), it is not easy to
calculate the exact amount of RE used for PDSCH or PUSCH since some of the REs are also
used by control channels like PDCCH, PHICH etc
In our case, lets assume that 10% of RE's are assigned for control channels then
TBS = 776
CRC = 24
RE = 2 (RB) x 12 (subcarriers) x 7 (assuming 7 ofdm symbols) x 2 (slots per subframe) x 0.9
(10% assumption as above) = 302 REs
Bits per RE = 6 (Modulation order from table 7.1.7.1-1)
So
code rate = (776 + 24) / (302 * 6 ) = 0.4

Throughput
Throughput is simply = Transport block size*(1000) = 776 *1000 = 776000 bits / seconds = 0.77
mbps (Assuming MIMO not used)
Please check this Throughput Calculator which takes MCS values and number of resource
blocks as input to calculate the downlink throughput

Transport Block Size, Throughput and Code rate

Since the size of transport block is not fixed, often a question comes to mind as to how transport
block size is calculated in LTE.
Back Ground
If we only consider "Uplink direction" and we assume that the UE is already attached to the
network, then data is first received by PDCP (Packet data compression protocol) layer. This layer
performs compression and ciphering / integrity if applicable. This layer will pass on the data to
the next layer i.e. RLC Layer which will concatenate it to one RLC PDU.
RLC layer will concatenate or segment the data coming from PDCP layer into correct block size

and forward it to the MAC layer with its own header. Now MAC layer selects the modulation and
coding scheme configures the physical layer. The data is now in the shape of transport block size
and needed to be transmitted in 1ms subframe.

What type of load balancing you are looking ? Are you looking for SGW load balancing ? PUSCH and
PDSCH physical channels being used for data plane in uplink and downlink respectively. EnodeB
MAC downlink scheduler is responsible to schedule data for set of users per millisecond level of
granularity in downlink and EnodeB MAC uplink scheduler is responsible to allocated resources in
uplink. At the eNodeB, UE's can be categorized into two groups if eNodeB is running in hybrid mode.
1.CSG's
subscriber.
2.Non-CSG subscriber.
Downlink/Uplink scheduler might use priority of bearer's to schedule UE's data. It is upto eNodeB
vendor how they want to implement. I know "Round Robin" and "PFS algorithm" being used by
eNodeB scheduler.

n Mobility Load Balancing (MLB) as part of Self-Optimization feature of SON, there is the 'X2
Resource Update Response' and Update messages that come from eNB 2, when eNB1 sends an 'X2
Resource Update Request' message. As part of this message, S1 Transport Network Layer (TNL)
Load indication is indicated. Standard says the implementation of this is vendor-dependent . So, what
does S1 TNL Load indicate? Is it related to S1-U load?