Beruflich Dokumente
Kultur Dokumente
Table of Contents
1
Introduction
Conclusion
11
Acknowledgement
12
References
12
Abbreviations
Abbreviation/ Acronym
Expansion
RRM
eNB
RAC
RBC
QoS
Quality of Service
ABC
LTE
GSM
RLC
MAC
RRC
PDCP
CMC
UE
DRA
PS
ICIC
LB
User Equipment
Dynamic Resource Allocation
Packet Scheduling
Inter-Cell Interference Coordination
Load Balancing
GBR
AC
Admission Control
RAN
ARP
ERAB
QCI
BW
Bandwidth
Introduction
This paper provides an insight into the admission and management of bearers for the efficient use of
radio resources. Admission deals with establishment of a new bearer depending on the feasibility and
availability of resources. Management of bearer is taken care of by bearer control, which deals with the
modification or deletion of bearers.
This paper will be useful for design approach and prototype development from developer prospect .
eNodeB Architecture
eNodeB (eNB) is the hardware, which connects to a mobile phone network that communicates directly
with mobile handsets (User Equipment). It is similar to a base transceiver station (BTS) in Groupe Spcial
Mobile/Global System for Mobile Communications (GSM) networks.
Radio link specific protocols, including the Radio Link Control (RLC) and Medium Access Control (MAC)
protocols terminate at the eNodeB. The Packet Data Convergence Protocol (PDCP), which is responsible
for header compression and ciphering, is located in the eNB. In the control plane, the eNB uses the Radio
Resource Control (RRC) protocol for application level RRC.
Figure 1 depicts the eNodeB (eNB) architecture.
S1
S-GW
P-GW
PHY
EPC
eNodeB
Figure 1: eNB Architecture
Shared Data
Notifics
(Access, Qos,
Mobility)
E-UTRAN
UEs
S1 Interfaces
NW
Dynamic Inputs
Measurements
RRM Adaptation
Configuration Inputs
Application RRM as a service function on the eNB can be considered in the following logical realization
form.
XP Interfaces
(Mobility)
Uu Interface
(Access, Profiles, Qos)
Radio Stack
(RRC, MAC, S1, X2 takes
appropriate Procedural
action
Start
Get Available
BW UL/DL?
GBR?
No
Allocate
configured
min non-GBR BW
YES
Allocate Min
BW to all ERABs
YES
Min BW
Configured?
No
Sort the ERAB list
first on priority,
next on GBR basis
End of
ERAB list?
YES
END
No
Is a variable
BW UL/DL<GBR
UL/DL?
Update available
BW UL/DL
YES
Allocate SRB to ERABs
Reject Request
No
YES
Trigger RBC to
allocate on ARP basis?
The figure above depicts an approach according to which GBR is granted based on priority and GBR
requested. The algorithm in contention situation triggers RBC in which case the allocation happens based
on allocation and retention priority (ARP) parameters.
Cons:
Pre-emption would lead to release of lower priority ERABs.
Recommendations for operator use
Operators can set Quality Class Identifier (QCI) (QoS profiles) and priority levels for different customer base,
(privileged and others) and allocation would be done on priority and GBR basis. In contention situation a
higher privilege customer gets priority over lower ones and can pre-empt lower ones.
Initialize
Total Weight = 0
End of
ERAB list?
Yes
Total Weight+=
Weight
No
Calculate Weight
Weight = (15-QoS
Priority Level)
All ERABs
allocated?
Yes
No
Calculate FairShare
FairShare=Avail
BW/Total Weights
Update available
BW UL/DL
Re-calculate Total
Weights = Weights
(Allocated)
Yes
Atleast one
Demand Fully
Satisfied?
No
End
Calculate Fairshare
Fairshare-(Avail EW/Total
Weights)
Ensure that users do not get a resource share larger than their demand.
Ensure that users with un-satisfied demands get an equal share of unused resources proportional to their
weights.
Cons:
The cons of the technique are as follows:
Max-min fairness in communication networks assumes that resources (capacities of communication links)
are allocated to flows in advance, as opposed to best-effort networks.
Recommendations for operator use
Different flows might have different QoS requirements, such as:
n
Customers of video service are willing to pay more to get required BW.
This algorithm helps to categorize users priority and allocate higher BW share to privileged users.
Conclusion
RAC and RBC are vital for eNB operation, session establishment, session continuity and session closure and
network performance optimization while users are on the move or not.
Several studies have shown that users need customized services according to their use and specific
requirements. Users utilizing high BW applications such as online gaming or streaming can have a faster and
an enhanced experience with these algorithms. Users with high privileges in terms of services and QoS will
always get GBR at any point of time.
We consider an optimized access and management approach that can be adapted to engineering
parameters, because accommodating field results is necessary to ensure that system resources are
effectively utilized.
11
Acknowledgement
We (Pundalik Kandolcar and Mukesh Kumar Das) would like to express our gratitude to all those who made it
possible to complete this white paper. We would also like to thank our colleagues from the Next-Gen R&D
Group for all their help and support during the writing of this paper.
References
[1] 3GPP TS 36.101 UE Radio Transmission and Reception http://www.3gpp.org .
[2] 3GPP TS 36.331 RRC Protocol Specification http://www.3gpp.org .
[3] 3GPP TS 36.300 http://www.3gpp.org
[4] 3GPP TS 36.322. E-UTRA radio link control (RLC) protocol specification. ftp://ftp.3gpp.org/Specs/archive/36_series/36.322/
[5] 3GPP TS 36.321. E-UTRA medium access control (MAC) protocol specification. ftp://ftp.3gpp.org/Specs/archive/36_series/36.321/
[6] 3GPP TS 25.913. Requirements for evolved UTRA (E-UTRA) and evolved UTRAN (E-UTRAN). ftp://ftp.3gpp.org/Specs/archive/25_series/25.913/
[7] http://lte-epc.blogspot.in/2012/03/rrm-functions.html
12
Contact
For more information contact global.telecom@tcs.com
Subscribe to TCS White Papers
TCS.com RSS: http://www.tcs.com/rss_feeds/Pages/feed.aspx?f=w
Feedburner: http://feeds2.feedburner.com/tcswhitepapers
IT Services
Business Solutions
Outsourcing
All content / information present here is the exclusive property of Tata Consultancy Services Limited (TCS). The content / information contained here is
correct at the time of publishing. No material from here may be copied, modified, reproduced, republished, uploaded, transmitted, posted or distributed in
any form without prior written permission from TCS. Unauthorized use of the content / information appearing here may violate copyright, trademark and
other applicable laws, and could result in criminal or civil penalties. Copyright 2013 Tata Consultancy Services Limited