DEVELOPING A

QoS AWARE
FRAMEWORK FOR LTE
QoS CONTROL AND QoS AWARE SCHEDULER
MAYANK KUMAR RASTOGI
Principal Systems Engineer, Aricent

DEVELOPING A QoS AWARE

FRAMEWORK FOR LTE
A good quality of service (QoS) mechanism enables operators to monetize their networks
effectively, and helps them provide differentiated service offerings. Controlling quality of
service not only improves customer satisfaction and reduces churn, it optimizes the use of
network resources by prioritizing higher valued traffic flows. The 3GPP Release 8 framework
for QoS contains mechanisms to implement these innovations. This whitepaper describes
the QoS control mechanisms required for eNodeB, and provides a description of the 3GPP
QoS concept and mechanism spread across various LTE network nodes for realization of
QoS. Implementation of QoS-aware Packet Scheduler is also covered in detail.

INTRODUCTION

class-based mapping of operator services to packet forwarding

The introduction of flat-rate tariffs, coupled with the availability

and backhaul, and control the radio resource allocation, play an

of smart devices, has made bandwidth-hungry applications such

important role in realization of per-UE or per-bearer QoS needs.

treatment in network nodes. The eNodeBs that sit between UE

as multimedia, video on demand, mobile TV and online gaming

ubiquitous and affordable, resulting in a drastic increase in

This whitepaper covers the QoS architecture in LTE and its

packet traffic volume per subscriber. Each of these services has

various functions spread across different network nodes. The

different performance requirements in terms of bit rate, packet

first part provides a primer of the QoS concept and mechanisms

delay, packet loss tolerance, etc. Moreover, operators are now

available in 3GPP LTE networks, focusing more on the functions

basing their pricing on subscribers individual requirements.

required in eNodeB for QoS realization. In the second part,

Thus, there is a need for a QoS framework that provides

various design principles for the LTE eNodeB packet scheduler

differential treatment based on subscribers, services, and data

are discussed for effective conformance to QoS requirements

traffic flows. Key requirements include:

while allocating radio resources. The last section summarizes the

> Ensuring high Quality of Service, especially for key services,

article and gives a brief overview of Aricent offerings for eNodeB.

in terms of delay, packet loss rate, and throughput

> Enabling user differentiation to provide expensive subscriptions

with higher availability and min and peak bit rates

> Limiting undesired users/applications like excessive

downloads on flat-rate subscriptions

> Prioritizing emergency services to provide highest reliability

> Reducing over-provisioning for guaranteed bit rate services to
ensure efficient use of resources

QoS ARCHITECTURE IN 3GPP LTE NETWORKS

In 3GPP architecture, EPS Bearer or Bearer, in short, is the finest
level of granularity for which QoS control is defined (1). EPS Bearer
is a logical entity that includes all the packet flows that receive a
common QoS treatment between UE and EPS Gateway. The EPS
Bearer is a logical concatenation of the Radio Bearer between UE
and eNodeB, and S1 Bearer between eNodeB and EPC. The EPS
Bearer is set up according to the signaling procedures defined

3GPP Release 8 specification, while primarily targeting the

in (2) and (5). A packet flow is identified by packet filters (5-tuple).

high-throughput, low-latency LTE network, has standardized

Using packet filters configured during bearer setup, UE maps

the QoS framework with mechanisms to fulfill all of the above

packet flow in uplink direction to EPS bearer while Gateway

requirements. It provides extensive specifications ranging from

maps packet flows to EPS bearer in downlink direction.

QoS Control in LTE eNodeB and QoS-Aware Scheduler

The first bearer is set up when UE attaches to network is the

b. Priority: The value of priority ranges for one to nine, with one

default bearer. Unlike previous RANs, in LTE, the default bearer

being the highest value. The priority level is used to differentiate

always remain associated with UE as long as it is attached to the

between bearers with the same UE, as well as between bearers

network and retains the IP address provided by the APN. The

with different UE. The eNodeB scheduler can use this as criteria

default bearer provides the basic best-effort connectivity to the

while scheduling radio resources between different UEs.

UE, which can also be associated with up to seven dedicated

c. Packet Delay Budget (PDB): The PDB defines the upper

bearers. These dedicated bearers enable the network to provide

limit on the delay experienced by a packet, associated with

different QoS to different packet flows associated with different

a bearer, between UE and Gateway. The packet scheduler,

bearers. The operator can control which packet flows are

while allocating radio resources to different UEs, should try to

mapped onto the dedicated bearer, and the QoS level associated

maximize the compliance to the PDB allowed for the packets of

with the dedicated bearer, through policies provisioned into the

a bearer belonging to a certain QoS class.

Policy and Charging Resource Function (PCRF) node or directly

into the Gateway. Packet flows that do not map to a dedicated

d. Packet Error Loss Rate (PLER): The PLER defines the upper

bearer map to the default bearer.

limit on the rate of non-congestion-related packet losses.

The PLER can be used for configuration of appropriate link

QoS PARAMETERS

layer protocol like RLC mode, max HARQ retransmissions,

The LTE QoS model is class based, with each bearer assigned only

etc. Typically, for PLER below 10-3, bearer control function

one QoS class by the network. The model is made more simple

in eNodeB can decide to use RLC Acknowledged Mode

by the specification by specification of a single scalar, QCI (QoS

(AM), and for PLER above 10-3, can decide to use RLC

Class Identifier), which represents the performance parameters

Unacknowledged mode.

associated with a QoS class. The QCI is the class identifier, which

The 3GPP has published the standardized characteristics

is used as a reference to node-specific parameters that control

associated with a QCI in (1) (see table below). These values are

packet-forwarding treatment like scheduler weights, admission

not signaled on any interface, and should be taken as guidelines

thresholds, queue management thresholds, link layer protocol

for configuration of node-specific parameters for each QCI. The

configuration, etc (1). 3GPP has standardized nine QCI values. Each

QCI and its corresponding characteristics ensures that services

QCI is associated with specific standardized characteristics that

using the same QCI class will receive a minimum level of QoS, even

describe its performance expectations, end to end, between UE

in a multi-vendor deployment and in case of roaming.

and Gateway. The value of QCI and its associated characteristics is

the same in uplink and downlink for each bearer. The following are
some of these characteristics:

Packet
Delay
Budget

Packet
Error Loss
Rate

100 ms

10-2

Conversational
Voice

150 ms

10-3

Conversational Video
(Live Streaming)

50 ms

10-3

Real Time Gaming

300 ms

10-6

Non-Conversational
Video (Buffered
Streaming)

100 ms

10-6

IMS Signaling

Resource
Type

(GBR) bearer carries traffic that requires a minimum bit rate

guarantee from the network. At the time of GBR bearer setup/
modification, through admission control function, resources
at various network nodes (eNodeB, packet Gateways) are

Example Services

Priority

QCI

a. Resource Type (GBR/non-GBR): The Guaranteed Bit Rate

provisioned such that there is no congestion-related packet

drop experienced by the bearer. Conversely, the non-GBR

GBR

bearer caries variable-rate traffic and is offered best-effort

service from the network. There can be congestion-related
packet drops in traffic associated with non-GBR bearers, while
GBR bearers are more costly to service because transmission
resources are blocked for such services. Operators allow the
GBR service when enough resources are available and there is
6

300 ms

10-6

Video (Buffered
Streaming)
TCP-based (e.g.,
www, e-mail, chat, ftp,
p2p file sharing, etc.)

100 ms

10-3

Voice, Video (Live

Streaming)
Interactive Gaming

10-6

Video (Buffered
Streaming)
TCP-based (e.g.,
www, e-mail, chat,
ftp, p2p file sharing,
etc.)

no risk of service degradation to existing sessions. Subscriber

sessions with a non-GBR class can remain established for

longer periods of time. Typically, the default bearer belongs to

the non-GBR class and can be used for services like internet
browsing, while services like IMS voice call require a dedicated
GBR bearer being set up on-demand. Its an operator policy

NonGBR

decision, implemented using PCRF, that specifies whether a

service is realized using a GBR or non-GBR bearer.

8
300 ms

QoS Control in LTE eNodeB and QoS-Aware Scheduler

As part of bearer setup/modification procedures, GBR bearers

an existing bearer to handle a packet flow. The control plane

are associated with GBR and MBR parameters separately for

bearer procedure handling function of MME forwards the bearer

DL and UL. GBR is the guaranteed bit rate that the network

setup/modification request to eNodeB and UE, and co-ordinates

will be able to sustain, while MBR is the maximum bit rate

the setup/modification of EPS Bearer within UE, eNodeB, and

that the traffic of the bearer should not exceed. Through

Gateways.

appropriate Queue Management policies, network nodes

should be able to handle short-term variation in bit rate up to
MBR without packet drop, and at the same time should reserve
transmission resources for GBR rate only. The non-GBR bearers
are associated with Aggregate Maximum Bit Rate (AMBR)
parameter, separately for DL and UL. This is not a per-bearer
parameter, but an aggregate rate of all non-GBR bearers for UE
or for an APN within UE. 3GPP specifies two different AMBR
parameters. The UE-AMBR is a per-UE parameter implemented
at eNodeB and Gateway; APN-AMBR, which is only known to
Gateway, specifies the per-UE and per-APN bit rates. Bit rate
consumption for GBR bearers is not included in either of these
AMBR parameters. UE-AMBR is the upper bit rate limit provided
to UE, and is less than or equal to the total APN-AMBR of all active
APNs to which UE is connected.

During bearer setup/modification procedures, the eNodeB

and Gateway perform both admission and pre-emption control
functions to limit their loads. In eNodeB, RRM performs both
of these functions. As part of the admission control function in
eNodeB, RRM decides whether sufficient radio and processing
resources are available to cater to the new bearer QoS and bit
rate requirements. In a typical implementation, the inputs to the
admission control function are the current load of the entire cell;
the nature of the current request, depending on whether the
bearer belongs to an emergency call, handover, GBR or non-GBR
data radio bearer (DRB), or signaling radio bearer (SRB); the
QCI of the new bearer; and the estimated load increase from the
admission of the new bearer, depending on the bearer bit rate
(GBR, AMBR) and resource type (GBR, non-GBR). The function
admits the bearer if the increment in current cell load due to

Allocation and Retention Priority (ARP) is another parameter

the admission of the new bearer is within the allowed system

associated with each bearer. ARP defines the control plane

capacity threshold for that particular request type. The RRM

treatment related to admitting and retaining bearers. The ARP

may keep separate system capacity thresholds for different

is used by admission control function in eNodeB and Gateway to

QCI classes, ARP values, and types of requests. For example,

decide whether a bearer establishment or modification request

a higher threshold is used for handover requests than for new

be accepted or rejected during overload situations. Also, ARP can

bearers in order to reduce the probability of call dropping. Should

be used by the pre-emption function to decide which bearers to

overload conditions prevent bearers from being admitted, the

release in situations when the system is in overload or resources

pre-emption control function of RRM uses bearer ARP values to

are to be freed (e.g., to admit an emergency call).The only QoS-

identify the specific bearer that needs to be released in order to

related parameters known to UE, other than UL packet filter

free-up resources for higher-priority bearers. During excessive

rules, are related to the UL bearerPrioritized Bit Rate, Priority,

load conditions, the overload control function residing in eNodeB

and Bucket Size Duration. The significance of these parameters

RRM and Gateway can also initiate load shedding by identifying

is discussed in the next section.

bearers to be released based on their ARP value.

While traffic is flowing, UEs perform uplink packet filtering to map

FUNCTIONS FOR REALIZATION OF QoS

packets belonging to an uplink packet flow to a bearer. Similarly,

Gateways perform downlink packet filtering to map packets

The QoS is a distributed functionality whose functions are

belonging to a downlink packet flow to the required bearer. The

spread across all LTE network nodes: UE, eNodeB, backhaul,

Gateway and eNodeB also implement rate-limiting functions to

MME, Gateways (S-GW, P-GW), and PCRF. Figure 1 illustrates the

ensure that the services are sending data in accordance with the

location of QoS functions among LTE network nodes and within

specified maximum bit rates (MBR and AMBR), and to protect

various layers of eNodeB.

the network from being overloaded. For non-GBR bearers, the

eNodeB performs the rate limiting based on the UE-AMBR value,

The operator decides the mapping between services offered to

while the Gateway performs the rate policing based on APN-AMBR

UEs and the QCI and bearer type. The bit rates like MBR/GBR,

value in both uplink and downlink. For GBR bearers, the rate limiting

UE-AMBR, and ARP is also part of the subscriber profile. These

based on MBR is carried out in Gateway and eNodeB for downlink.

operator policies are coded into PCRF and allows operators to

realize both service and subscriber differentiation. Operators

The eNodeB packet scheduler distributes the radio resources

also incorporate semi-static configurations of QoS functions

between established bearers in uplink and downlink direction.

directly into network nodes using O&M system.

directions. The scheduling function is responsible, to a large

extent, for the fulfillment of the QCI characteristics associated

The PCRF in the network determines how each packet flow for

with bearers. The next section provides details regarding decision

each subscriber must be handled in terms of the QoS parameters.

making at the scheduler to address bearers QoS requirements.

It triggers the establishment of a new bearer or modification of

QoS Control in LTE eNodeB and QoS-Aware Scheduler

The bearer control function in eNodeB RRM is also responsible

duration, every bearer is credited tokens equivalent to PBR. The

for configuration of L1 and L2 protocols of the radio bearers in

received grant is allocated to the bearer with highest priority until

accordance with the QCI characteristics. The RLC-acknowledged

all tokens are consumed, followed by another bearer in priority

or -unacknowledged mode is based on the PLER requirement.

until tokens of all bearers in a LCG are served. Surplus grants are

PLER and PDB are considered in configuring the maximum

allocated preferentially to bearers according to priority until the

number of HARQ retransmissions in both uplink and downlink.

pending buffer size reaches zero. Within an LCG, RRM allocates

The PDCP discard timer is configured on the basis of PDB

priority to the bearer as per the QCI priority. The PBR is allocated

associated with the bearer so that packets delayed beyond

in proportion to the GBR rates.

allowed PDB limits, while waiting to be scheduled, can be flushed

out. The RLC downlink transmission queue length is configured
based on the GBR or AMBR bit rate and PDB associated with the
bearer. RRM also configures the scheduler parameters, details of

The Gateway and eNodeB also implement QCI to the DSCP

mapping function to create a transition between bearer-level
QoS to transport-level QoS. Using this function, packets

which are provided in the next section.

on a bearer associated with a specific QCI are marked with

The bearer control function in RRM also configures parameters

QCI to DSCP mapping is based on the operator policies

that are specific to the uplink bearer. The data and signaling
bearers having common QoS requirements and are grouped
by RRM into Logical Channel Groups (LCGs), of which there are
up to four per UE. A typical grouping of bearers to LCG is: LCG
0 (SRB1, SRB2, DRB with QCI 5 used for IMS signaling), LCG
1 (DRB with QCI 1 used for voice call), LCG 2 (GBR DRBs with

specific DSCPs for forwarding to the backhaul network. The

configured using O&M into eNodeB and Gateway. eNodeB
performs this mapping for uplink while Gateway does it for
downlink. The backhaul transport network should implement
its queue management and traffic forwarding functionality
based on DSCP value.

QCI 2, 3, and 4), and LCG 3 (non-GBR DRBs with QCI 6, 7, 8,

The eNodeB RRM Overload Detection function constantly

and 9). This kind of grouping allows the scheduling rules to be

monitors the cell load status and performance statistics

applied per LCG rather than per bearer. For uplink transmission

reported periodically by L2 regarding the level of compliance

resource requests, UE can specify the size the buffer awaiting

per QCI class characteristics like PDB, PLER, and bit rates. If

transmission per LCG. The eNodeB can also communicate the

the compliance of a QCI drops below a certain threshold, overload

per-LCG grant to UE. RRM configures the Priority, Prioritized

control triggers the pre-emption function to release bearers

Bit Rate (PBR), and Bucket Size Duration per uplink bearer. UE

belonging to the QCI class, and the admission control function

uses these parameters to distribute the received uplink grant

stops admitting new bearers to the QCI class. This allows eNodeB

from eNodeB among bearers within LCG. The principals of token

to prevent and recover from an overload condition and improves

bucket algorithm are applied when, once in every bucket size

the compliance to QCI for ongoing bearers.

OSS/BSS Operator Policies

Configuration
Mgmt

Configuration
Mgmt

Configuration
Mgmt

Bearer Procedure
Signaling

Service to QCI
Mapping

Mgmt Plane

RRM, RRC, S1AP, X2AP

Bearer Procedure
Signaling

Bearer Procedure
Signaling

UL QCI to DSCP
Mapping

Admission Control

Overload Detection
& Control

Bearer Control

Pre-emption
Control

DL QCI to DSCP
Mapping

L2 (Scheduler, MAC, RLC, PDCP)

UL Grant Distribution
(Priority, PBR, BSD)
Real-time Gaming

Cell Load/QoS
Measurement
DL/UL Scheduling
L1, GTPU

User Plane
DL Packet Flow to
Bearer Mapping

L2 Protocol
Functions (RLC
Mode, RLC DL Q
Mgmt, Discard
Timer, HARQ Retx)
Rate Limiting
UL DSCP Packet
Marking

UE

eNodeB

Control Plane

DSCP Aware Q
Mgmt & Traffic
Forwarding
Backhaul

Transport

Rate Limiting
DL DSCP Packet
Marking
Gateway
(MME, S-GW, P-GW)

PCRF

Figure 1: QoS functions across LTE network nodes

QoS Control in LTE eNodeB and QoS-Aware Scheduler

CONSIDERATIONS FOR QoS-AWARE

eNodeB SCHEDULER

while reserving a fixed capacity within the cell for GBR bearers.

A QoS-aware scheduler needs to meet various conflicting

of services like internet browsing, background download and

requirements. For every admitted UE for which traffic is flowing,

are bursty and more tolerant for latency. The scheduler ensures

the scheduler needs to ensure that radio resources are being

that bearers are given a higher priority allocation, but doesnt

allocated such that signaled bit rates (GBR/AMBR) and latency

let non-GBR bearers starve over time. A typical scheduler can

and PLER requirements are sufficiently met while other users

handle this by categorizing bearers into signaling, GBR, and

QoS requirements are also fairly allocated. The scheduler also

non-GBR categories. The signaling category includes signaling

needs to ensure that aggregate cell throughput is maximized,

radio bearers and QCI class 5 for high-priority, low-latency

and that varying user-channel conditions are taken into account

IMS signaling. GBR and non-GBR categories remain QCI-class,

for maximizing cell throughout. For example, UE with low overall

with resource-type GBR and non-GBR. Figure 2 illustrate how

priority might be having good channel conditions and and

the bandwidth is allocated to the different flows. Resources are

require fewer radio resources to transmit the same number of

first allocated to signaling and GBR bearers, up to the marked

bits as a high-priority UE going through bad channel conditions.

dedicated capacity. Non-GBR bearers are then allocated the

Scheduler need to choose the UEs such that the UE with bad

remaining capacity. The dedicated capacity for GBR bearers is

channel conditions. The scheduler needs to choose UEs such

derived from the aggregate GBR rate for each admitted bearer.

that those with bad channel conditions are not starved, while

This scheme can be optimized so that unutilized capacity from

UEs with good channel conditions are preferred, thus maximizing

signaling and the GBR category is utilized for non-GBR. Certain

aggregate cell throughput.

underserved GBR bearers are also considered while scheduling

LTE eNodeB also requires fast schedulingonce every

the capacity for non-GBR bearers. The dedicated capacity for

millisecond. Thus, the number of calculations performed for

every allocation should also be optimized so that within the
available CPU cycles, the processor and scheduler are able to
convey decisions to the MAC with enough space to, in time, send
DL data and DL/UL radio resource allocation information to
Phy for transmission to UE.

GBR bearers, running services like VOIP calls, send packets

of almost equal sizes at the signaled bit rate. Non-GBR bearers

GBR can be tuned based on the over-allocation factor used by

RRM while admitting GBR bearers.
A typical scheduling function will work in conjunction with other
functions, as illustrated in Figure 3. The buffering function
is required to buffer the downlink PDUs waiting for their
transmission opportunity. The per-bearer queue load from the
buffering function is used as an input by the scheduling function

as well. The majority of bearers admitted in a typical cell will be

in the allocation decision. The buffering function also manages

non-GBR bearers and to maximize number of served bearers,

the queue length with the maximum limit configured by the RRM

admission control function in RRM will do over-allocation while

bearer control function, and drops PDUs beyond the configured

admitting non-GBR. To maximize bearer since such bearers, the

level. It also maintains the arrival time of each PDU. PDUs waiting

admission control function in RRM performs over-allocation and

beyond the discard time, configured by the RRM bearer control

admits non-GBR bearers that dont utilize the capacity uniformly,

function, are dropped.

Aggregate Cell Throughput

There are conflicting demands for GBR and non-GBR bearers

RLC, PDCP

MAC

Flow Control
Buffer
Mgmt

Allocated to non-GBR traffic

Channel Feedback
Scheduler

Allocated to GBR traffic

Resource Allocator
HARQ

Allocated to Signaling traffic

Time
Figure 2: Dividing resources between Signaling, GBR, and non-GBR traffic

QoS Control in LTE eNodeB and QoS-Aware Scheduler

L1
Figure 3: Scheduler and associated functions

A flow control function resides between the buffering and

classs priority, current pending data for transmission, delay of

scheduling functions. Typically, a token-based algorithm can

head-of-the-line packets compared to the allowed delay as per

be implemented to periodically create per-bearer tokens at the

QCI class, the running average GBR throughput achieved with

signaled GBR/UE-AMBR rate, while the scheduling function

respect to the GBR rate agreed in control signaling etc. Weights

limits the transmission opportunity for the bearer by the amount

are configured for each factor by RRM, while the value of each

of tokens left. The channel feedback function maintains the

factor is normalized to a common scale. The aggregate weighted

channel state per UE which is utilized by scheduling function

priority of a bearer is calculated by multiplying the normalized

to prioritize UEs with good channel conditions. This function

value of each factor by the weight corresponding to the factor

utilizes the CQI (Channel Quality Indicator) feedback from UE

and aggregating it. The weighted priority of each bearer with

for estimating downlink channel quality, and SRS (Sounding

a non-zero queue load is calculated and all bearers are sorted

Reference Signal) feedback for estimating uplink channel quality.

in decreasing order of weighted priority. The bearer with the

The HARQ function controls the retransmission of MAC PDUs,

highest weighted priority is allocated resources first, limited by

while the DL HARQ stores the DL-transmitted MAC PDU and, if

the bearers available tokens. Bearers are served in decreasing

negative feedback is received from UE, does the retransmission

weighted priority order until either all resources are allocated

of MAC PDU, up to a limit as configured by RRM-bearer control

or all bearers are served. For bearers served in a TTI, weighted

function. The UL HARQ function sends positive and negative

priority is recalculated. Due to the decrease in both head-of-the-

feedback for UL-transmitted PDU to UE so that UE can

line packet delays and queue load factors, and the increase in

retransmit PDU for which negative feedback is received. The

throughput achieved, their weighted priority and position on the

scheduling function requires feedback from the HARQ function

list move down, thereby improving the chances of allocation for

so that it can schedule resources for retransmissions. A typical

unserved bearers in the previous TTI. For uplink, the algorithm

scheduling function gives priority to retransmissions over new

and the factors considered are similar except that the buffer

transmissions for UE. The Radio Resource Allocation function

status reports from the UE are used as the input for current

allocates the actual frequency resources on PDCCH, PDSCH,

pending data for transmission.

and PUSCH channels.

The scheduling algorithm is the heart of the scheduler. Its
purpose is to select the UEs that best fit a given scheduling
policy for the allocation of both downlink and uplink radio
resources in a TTI, and the amount of opportunity given to
each UE. Consideration of per-bearer characteristics and
requirements are taken into account, but the radio resources
are ultimately allocated per UE. The UEs selected for uplink
transmission can be different from UEs selected for downlink
transmission. There are many well-known standard algorithms:
Round Robin (RR), where equal opportunity is given to each
UE; Proportional Fair (PF), where resources are window; and
Maximum Carrier to Interference Power Ratio (MCIR), where
users with maximum CIR are selected for transmission. RR
is a very simplistic algorithm that doesnt consider channel
conditions and is only useful for comparative purposes. MCIR
is not suitable because it neither guarantees bearer QoS
requirements nor ensures fairness among UEs. PF also is not
appropriate because some guarantees are given between users,
but not between bearers. The performance of each of these

The WP scheduling algorithm chooses users taking into

consideration its buffer occupancies per queue, priority, delay,
and throughput requirements of the QoS class, dynamic token
value of the bearer, and channel conditions reported by the
UE. Its greatest benefit is being highly tunable and modular,
both in terms of behavior and cost of computations. Based on
deployment and the ongoing traffic situations, weights can be
fine tuned to emphasize a particular factor or de-emphasize
the impact of another factor. Segregation of bearer in categories
(signaling, GBR, non-GBR) ensures that bearers in individual
categories can be separately served based on reserved capacity
as well as separate weights. This also reduces the impact of
overload conditions of one category on another, especially
non-GBR categories that are normally over-allocated at the time
of admission. The CPU cycle consumption can also be finely
controlled. The granularity of the normalization function can be
made finer or coarser, which controls the number of times the
factor values need to be collected and calculated. The bearers
weighted priority need not be calculated every TTI, but rather
only for those served in a TTI or for which the queue load has

algorithms is analyzed in (6).

changed substantially due to the arrival of new packets. For the

To meet these challenges, Aricent has developed the Weighted

when the tokens are replenished. For further optimization, the

Priority (WP) algorithm to optimally handle all the QoS

bearers can be batches, with token updates staggered among

requirements as well as keep precise control of computing

batches. Increasing both the token interval and the number of

requirements. This algorithm considers a set of factors

batches reduces CPU cycle consumption, but at the cost of more

in calculating the weighted priority of each bearer having a

precise control in scheduling fast-changing factor values.

res of the bearers, priority can be calculated at a token interval,

non-zero queue load, including channel condition of the UE, QCI

QoS Control in LTE eNodeB and QoS-Aware Scheduler

An important function related to QoS control is the measurement

function in Layer 2.. It maintains time averaged measurements

ARICENT OFFERINGS

including cell time, frequency resource usage, and per-QCI

We offer turnkey LTE radio access solutionsfrom pluggable

class measurements like average packet delay and packet loss

software to pre-integrated and optimized product frameworks

rate. The measurements are made periodically and reported,

to complete product lifecycle services spanning across Product

by request, to the RRM monitoring function, which uses it as

Strategy and Design, Product Development, and Testing and

input for its admission control and overload detection function.

Certification.

The measurements can also be collected and archived by the

OAM Performance Management function and can be used to
derive Key Performance Indicators (KPIs). Table below lists the
measurements specified by 3GPP for eNodeB Layer 2 (7).

Our eNodeB stack portfolio consists of 3GPP Release 8 compliant

stacks including Scheduler, MAC, RLC, PDCP, GTPU, RRC, S1AP,
X2AP, and SCTP. A single eNodeB framework package is also
offered and includes all the stack components pre-integrated
and Layer 2, Layer 3 functionality verified against a referenced
L1 and EPC. Aricents eNodeB framework supports all QoS

Total PRB Usage (DL)

Total PRB Usage (UL)

requirements discussed above, and offers a state-of-the art

QoS-aware scheduler that is highly tunable and scalable for
different platform and deployment requirements.

PRB Usage per traffic class (DL)

PRB Usage per traffic class (UL)
Received Random Access Preambles
Number of Active UEs in DL per QCI
Number of Active UEs in UL per QCI

MAYANK KUMAR RASTOGI

is a Principal Systems Engineer
at Aricent, focusing on wireless
products and services related to

Packet Delay in DL per QCI

LTE eNodeB Stacks and Framework.

Packet Discard Rate in DL per QCI

Mayank has more than 14 years

Packet Uu Loss Rate in the DL per QCI

of experience in product development

Packet Loss Rate in the UL per QCI

and software design for LTE eNodeB,

Scheduled IP Throughput in UL

3G transport solutions, Softswitch,

Scheduled IP Throughput in DL

VoIP & SIP applications, and carriergrade high-availability solutions.

mayank.rastogi@aricent.com

eNodeB Layer 2 measurements (7)

QoS Control in LTE eNodeB and QoS-Aware Scheduler

ABBREVIATIONS

REFERENCES

AMBR

Aggregate Maximum Bit Rate

1.

APN

Access Point Name

ARP

Allocation and Retention Priority

HARQ

Hybrid Automatic Repeat reQuest

BSD

Bucket Size Duration

BSS

Business Support System

DRB

Data Radio Bearer

DSCP

Differentiated Services Code Point

EPC

Evolved Packet Core

EPS

Evolved Packet System

E-UTRAN

Evolved Universal Terrestrial Radio Access Network

GBR

Guaranteed Bit Rate

Network (E-UTRAN); Radio Resource Control (RRC);

GTPU

GPRS Tunneling Protocol User plane

Protocol Specification.

KPI

Key Performance Indicator

L1

Layer 1 (Phy)

L2

Layer 2

in high speed downlink packet access, Proceedings of the

LCG

Logical Channel Group

13th IEEE Symposium on Personal, Indoor and Mobile Radio

LTE

Long Term Evolution

Communications, Dec,2002.

MAC

Medium Access Control

MBR

Maximum Bit Rate

MME

Mobile Management Entity

O&M

Operations and Management

OSS

Operational Support System

PBR

Prioritized Bit Rate

PCRF

Policing and Charging Resource Function

PDB

Packet Delay Budget

PDCCH

Physical Downlink Control CHannel

PDCP

Packet Data Convergence Protocol

PDSCH

Physical Downlink Shared CHannel

PDU

Protocol Data Unit

PF

Proportional Fair

P-GW

Packet GateWay

PLER

Packet Loss Error Ratio

PUSCH

Physical Uplink Shared CHannel

QoS

Quality of Service

QCI

QoS Class Identifier

RLC

Radio Link Control

RR

Round Robin

RRC

Radio Resource Control

RRM

Radio Resource Management

S1AP

S1 Application Part

S-GW

Serving GateWay

SRB

Signaling Radio Bearer

TTI

Transmission Time Interval

UE

User Equipment

WP

Weighted Priority

QoS Control in LTE eNodeB and QoS-Aware Scheduler

2.

3GPP TS 23.203, Policy and Charging Control Architecture.

3GPP TS 23.401, General Packet Radio Service (GPRS)
Enhancements for Evolved Universal Terrestrial Radio Access
Network (E-UTRAN) Access.

3.

3GPP TS 36.300, Evolved Universal Terrestrial Radio Access

(E-UTRA) and Evolved Universal Terrestrial Radio Access
Network (E-UTRAN): Overall Description.

4.

3GPP TS 36.413, Evolved Universal Terrestrial Radio Access

Network (E-UTRAN); S1 Application Protocol.

5.

6.

3GPP TS 36.331, Evolved Universal Terrestrial Radio Access

Y. Ofuji, A. Morimoto, S. Abeta, M. Sawahashi, Comparison

of packet scheduling algorithms focusing on user throughput

7.

3GPP TS 36.314, Evolved Universal Terrestrial Radio Access

Network (E-UTRAN); Layer 2 Measurements.

INNOVATION
SERVICES
FOR THE
CONNECTED
WORLD
The Aricent Group is a global innovation and technology services
company that helps clients imagine, commercialize, and evolve
products and services for the connected world. Bringing together the
communications technology expertise of Aricent with the creative
vision and user experience prowess of frog, the Aricent Group
provides a unique portfolio of innovation capabilities that seamlessly
combines consumer insights, strategy, design, software engineering,
and systems integration. The client base includes communications
service providers, equipment manufacturers, independent software
vendors, device makers, and many other Fortune 500 brands.
The companys investors are Kohlberg Kravis Roberts & Co.,
Sequoia Capital, The Family Office, Delta Partners, and The Canadian
Pension Plan Investment Board.

aricent.com 2012 Aricent Group. All rights reserved.

All Aricent brand and product names are service marks, trademarks, or
registered marks of Aricent Inc. in the United States and other countries.