CEM Capacity

Agenda

1-INTRODUCTION
2-CCM BOARD OVERVIEW and CAPACITY
3-CEM BOARD OVERVIEW
4-XCEM/ECEM CAPACITY
www.alcatel-lucent.com
5-CAPACITY LICENSING
6-CEM CAPACITY MONITORING
7-MONITORING

2/75 | FSM UA7.0 - 34386 64 QAM for HSDPA | July 2010 Alcatel-Lucent 2008, d.r., XXXXX
1
Introduction

3/75 | FSM UA7.0 - 34386

64 QAM for HSDPA | July
The objective of this document is to provide an engineering view of the CEM
board capacity and associated features.
2
CCM BOARD OVERVIEW AND CAPACITY

5/75 | FSM UA7.0 - 34386

64 QAM for HSDPA | July
CCM is the module that provides the CPU power to manage the NodeB
terminated flows. It is in charge of the NodeB synchronization and the O&M
functions. There are versions of these boards for macro Nodebs and ones to be
used on d2u NodeBs (-u)

CCM CAPACITY :
The xCCM/xCCM-u/eCCM-u board can be equipped with the GigE MDA or with
4E1/T1 MDA.
Throughput capacity limitations are:
-With GigE MDA, it supports a maximum of 400 Mbps of aggregated throughput
(UL+DL) on the MDA IP/Ethernet interfaces. The 400 Mbps refer to user plane
data and are split equally between downlink and uplink (max 200 Mbps DL +
max 200 Mbps UL).
-With 4E1/T1 MDA, it is able to support 30 Mbps DL and 15 Mbps UL (45 Mbps
aggregated) throughput for IP backhauling through the Fast Ethernet port
available on the CCM motherboard.
Capacity load limitations:
FRS 34395 defines Engineering Load of 70% as the average load at which
95% of calls meet KPIs.
3
CEM BOARD OVERVIEW

7/75 | FSM UA7.0 - 34386

64 QAM for HSDPA | July
 xCEM HW architecture is based on 4 OneChip/ASIC (handling DCH trafic) and
3 FPGAs (handling HSxPA traffic).
FPGA = Field-Programmable Gate Array.
ASIC = Application-Specific Integrated Circuit.
Each OneChip/ASIC is considered as a BBU.
FPGA A is used for HSDPA user plane traffic.
FPGA B&C are used for HSUPA user plane traffic.

xCEM HW Architecture
 xCEM functional structure in UA5.1

Each xCEM board can manage up to 6 cells belonging to 2 Local Cell

Groups
 xCEM functional structure in UA6 & UA7
each xCEM board can manage in UA6/UA7 up to 6 cells
belonging to 2 Local Cell Groups.
4
XCEM CAPACITY:

11/75 | FSM UA7.0 -

34386 64 QAM for HSDPA
XCEM/ECEM CAPACITY:

A new BBU function is available for xCEM: the M-BBU.

Before UA6.0, CEM boards have been logically composed of one or more BBU,
each one being capable of supporting one particular service: DCH, HSDPA or
HSUPA. The following BBU types were defined:
D-BBU for DCH services.
H-BBU for HSDPA services .
E-BBU for HSUPA services .

From UA6.0 the xCEM is supporting DCH, HSDPA and HSUPA channel types
on a single BBU (the M-BBU). This includes the support of the following
channel combinations of a given user:
DCH
DCH + HSD
DCH + HSU (for E-DCH Macro-Diversity only)
DCH + HSD + HSU
HSD (if the associated DCH is allocated on a different BBU)
HSD + HSU (if the associated DCH is allocated on a different BBU)

Since UA7.1.3, eCEM-u boards are available. Architecture and figures are
similar to the one described for xCEM.
 xCEM/eCEM M-BBU structure
Maximum Mac-d throughput for an xCEM is 33400 in the case of xCCM with
MDA- 4E1.
Maximum Mac-d throughput for an xCEM is 38900 in the case of xCCM with
MDA-Gige.
1 xCEM / 2 Freqs:

M-BBU M-BBU M-BBU M-BBU

F1+F2 F1+F2 F1+F2 F1+F2
M-BBU HSDPA CAPACITY:
The throughput is provided at xCEM/eCEM board level and it is shared
between the 4 M-BBU.
In addition to this throughput limitation per xCEM/eCEM board, the
throughput limit of the cell and BTS connectivity are also to be
considered
- Cell ->
o Up to UA7.1: 14.4 Mbps at Air interface & 13.4 Mbps at RLC SDU
o From UA7.1: ~21.6 Mbps per cell (at Air interface) with 64QAM support.
-BTS connectivity -> max 8 E1 (ATM Iub Connectivity) / Fast Ethernet
port
(IP Iub Connectivity) / GigaBit Ethernet port with
XCCM/eCCM-GE
The xCEM/eCEM are handling HSDPA service in a shared mode, managing
up to 6 cells. Each cell will be granted with a fraction of the overall
xCEM/eCEM capacity, as described below:
PARAMETERS SETTINGS:
The parameter hsdpaMaxThroughputXcem can be used to reduce the
xCEM/eCEM resources allocated to HSDPA by steps of 6.25% (1800
kbps) from the max board throughput.
This parameter will not impact the HSDPA CAC but only reduce the
xCEM/eCEM throughout available for HSDPA calls.

(Example: If 5.4 Mbps HSDPA throughput Purchased, the value of the

parameter has to be set to 5400).
M-BBU HSUPA CAPACITY:

The xCEM/eCEM capacity for HSUPA is given by the limitation in terms of:
-Maximum number of users (per M-BBU and per xCEM/eCEM board)
-Throughput (per xCEM/eCEM board)
-Number of Cells per xCEM/eCEM board

The M-BBU/xCEM and M-BBU/eCEM board HSUPA capacity figures are given in
the following table:
PARAMETERS SETTINGS:
The parameter edchMaxThroughputXcem can be used to reduce the
xCEM/eCEM resources allocated to HSUPA by steps of 6.25% (480
kbps) from the max board throughput.
This parameter will not impact the HSUPA CAC, but only reduce the
xCEM/eCEM board throughout available for HSUPA calls.

If 3.84 Mbps HSUPA throughput purchased, the value of the

parameter has to be set to 3840)
M-BBU DCH CAPACITY:
PARAMETERS SETTINGS :
With the xCEM/eCEM, we have the possibility to control the number of CE for
DCH (Common channel and Dedicated channels) that can be allocated on
xCEM/eCEM boards through r99MaxNumberCeXcem parameter.

The recommended value for this parameters depends on Capacity

Licensing activation:
1. If Capacity Licensing is activated (finite value of
r99NumberCECapacityLicensing parameter), the
r99MaxNumberCeXcem is no more use by the BTS call admission
control algorithms (CAC), thus no rule for this parameter is needed.
2. If Capacity Licensing is not activated (infinite value of
r99NumberCECapacityLicensing parameter), in order to take full
benefit of the M-BBU DCH capacity, the value of
r99MaxNumberCeXcem parameter should be set following the
If r99MaxNumberCeXcem is modified on line, the new available BTS
CE credit (needed for CEM load in iRM) is calculated and the RNC is
informed about this modification through NBAP RSI message.
If the parameter is decreased online, the calls that have been already
established are not released even if the new value is below the current CE
xCEM/eCEM usage.
5
CAPACITY LICENSING

26/75 | FSM UA7.0 -

34386 64 QAM for HSDPA
The Capacity Licensing feature implies two main
enhancements:
-The control of the resources is done by OMC with a
distribution of tokens purchased by the customer.
-BTS has to manage them at the Node-B level; it has
to control its HW capacity and the allowed capacity.

The distribution of tokens is based on the purchase of

licenses, OMC manages the pool of licensing capacity
dedicated to the pool of BTS it manages; this capacity is
transferred to the BTS.
6
CEM CAPACITY MONITORING

29/75 | FSM UA7.0 -

34386 64 QAM for HSDPA
PRINCIPLE:
The CEM Capacity monitoring is based on two main
elements:
Call Admission blocking (due to lack of CEM resources)
CEM board load which can be separately evaluated
for:
o R99 traffic
o HSxPA traffic

Where the definition of Blocking and Load is:

Call admission Blocking (%) =1 - # Call_Success / #
Call_Request
Board Load (%) = Resources used / Total resources
available
The 3 main states in the above diagram can be described
as:
If no blocking is monitored => No corrective action is
required
If the Blocking appears, an additional level of
investigation is needed:
o Load is Low (below a predefined threshold) => Capacity
analysis and tuning are required (that can be based on
iRM or other UTRAN algorithms)
o Load is High (above a predefined threshold) =>
Capacity analysis and tuning are required and most
probably (depending on tuning results), new CEM
resource addition.
7
MONITORING

33/75 | FSM UA7.0 -

34386 64 QAM for HSDPA
COUNTERS FOR CEM BLOCKING EVALUATION:
CEM HSDPA LOAD EVALUATION:

. xCEM HSDPA Throughput

Scr_3/Scr_NbEvt of these counters will provide the average

throughput during observation period (average over ON and OFF 5
sec periods)
Scr_5 & Scr_6 of these counters will provide the number of TTI
periods (2ms) during which the scheduler restricted the throughput
because the license or HW throughput limit was reached (time of
www.alcatel-lucent.com
www.alcatel-lucent.com

39/75 | FSM UA7.0 -

34386 64 QAM for HSDPA