Professional Documents
Culture Documents
Peak L1 throughput values confirm Flexi System Module as compliant with 3GPP Release 8.
Refer to the tables below fot the maximum Transport Block Sizes, which can be set for
2x2MIMO (dual-stream transmission) with all available frequency resources.
Table:
DL peak L1 throughput
Release and max supported MCS
5 MHz 10 MHz
15 MHz 20 MHz
index
RL10 (MCS28)
37
75
--150
RL20 (MCS28)
110
RL30 (MCS28)
RL40 (MCS28)
RL15TD (MCS28)
--- 40.3 (2DL:2UL) --82.3 (2DL:2UL)
54.99
112.47
(3DL:1 UL)
RL25TD (MCS28)
(3DL:1UL)
Table:
UL peak L1 throughput
Release and max supported MCS index 5
10 MHz
15
20 MHz
MHz
MHz
RL10 (MCS20)
10.68
21.38
--43.82
RL20 (MCS20)
32.86
RL30 (MCS24)
13.54
27.38
40.58
55.06
RL40 (MCS24)
RL15TD (MCS20)
--8.6 (2DL:2UL)
17.5 (2DL:2UL)
4.3 (3DL:1UL)
8.8 (3DL:1UL)
RL25TD (MCS24)
--- 10.95 (2DL:2UL)
22.02 (2DL:2UL)
5.48 (3DL:1UL)
11.01 (3DL:1UL)
UL peak L1 throughput (PUSCH only; limited by PUCCH,
Table:
PRACH)
Release and max supported 5 MHz
10 MHz
15 MHz 20 MHz
MCS index
RL10 (MCS20)
8.5
19.1
--43.82
(20 PRBs)
(45 PRBs)
RL20 (MCS20)
20.6
30.6
(48 PRBs)
(72 PRBs)
RL30 (MCS24)
10.7
25.7
39.2
51.0
(20
PBRs)
(48
PBRs)
(72
PBRs)
(96
PBRs)
RL40 (MCS24)
RL15TD (MCS20)
--7.9 (2DL:2UL)
--16.1 (2DL:2UL)
3.8 (3DL:1UL)
8.0 (3DL:1UL)
RL25TD (MCS24)
9.8 (2DL:2UL)
20.2 (2DL:2UL)
4.7 (3DL:1UL)
10 (3DL:1UL)
3GPP Release 8 specifies QPSK, 16QAM and 64QAM for PUSCH. In RL30/RL25TD there
is no support for 64QAM transmission however it is possible to extend MCS range for
16QAM from MCS index 20 to 24. Flexi Rel.2 and Rel.3 are fully capable of handling the
largest possible Transport Blocks. It means that the HW architecture (processing power of
DSP boards) does not limit peak data rates.
UE PER CELL
FSMF+FBBA
(3 sectors per site)
FSMF+FBBA
(6 sectors per site)
FSMF
(3 sectors per site)
FSMF
(6 sectors per site)
FSME
(3 sectors per site)
FSME
(6 sectors per site)
FSMD
(2 sectors per site)
FSMD
(6 sectors per site)
5 MHz
480
10 MHz
600
15 MHz
1030
20MHz
1200
480
600
720
840
40
120
480
600
720
840
420
420
480
600
720
840
420
420
480
600
720
840
420
420
FLEXI systems
RF module
Flexi 3-sector RF Module 2600
Flexi 3-sector RF Module 800EU
Flexi 3-sector RF Module 2100
Flexi 3- sector RF Module1.7/2.1
Flexi RRH 2Tx 800EU
Flexi 3-sector RF Module 1800
Flexi 3-sector RF Module 1600
Flexi RRH 2Tx 1800
Flexi 3-sector for upper 700 MHz
Flexi 3-sector for 800 MHz (Japan)
Flexi RRH for 2600 MHz
Flexi RRH for 2100 MHz
Flexi RRH 2TX 1.7/2.1
Flexi 3-sector RF Module for 1900 MHz
Flexi 3RF Radio Module 1800 MHz, 90W
Flexi Lite BTS 750 MHz (whole eNB)
Flexi RF Module 6TX 2600
Flexi RF Module 6TX 800
Flexi RF Module 6TX 700
Name
FRHA
FRMA
FRGP
FRIE
FRMB
FXEA
FRNA
FHEA
FRBB
FXCA
FRHB
FRGQ
FRIF
FXFA
FXEB
LTE1072
FRHC, FRHF
FRMC
FRPA, FRPB
Release
RL09
RL10
RL10
RL10
RL10
RL20
RL20
RL20
RL30
RL30
RL30
RL30
RL40
RL40
RL40
RL40
RL50
RL50
RL50
RF module
Flexi RF Module 3TX 2100
Flexi RF Module 3TX 900
Flexi 3-sector RF Module 2100 MHz
Flexi RRH 2600 MHz
Flexi RRH 1800 MHz
Name
FRGS, FRGT
FXDA, FXDB
FXDA
FRHD, FRHE
FRED
Release
RL50
RL50
RL50
RL50
RL50
HW LIMITS
FSME
Table:
20 MHz
800
Table:
PDSCH and PUSCH resources and occupy control channel resources as well as processing
resources in the eNB. This active user definition matches well the "always-on" smartphone
with applications triggering constant background activity like heartbeats even when the user
is not actively operating the device. Transition to RRC_idle is typically triggered by an
incativity timer which may never expire in the always-on smartphone case.
The default or user-specific traffic model provides the number of users per cell area.
Depending on the subscriber profile (subscriber service agreement, traffic demand, mobility
characteristic, terminal type), a different number of connected users will be considered as a
percentage of the total amount of users. The more detailed traffic model is provided, the
better estimation can be made. Traffic model provides the parameter Share of Active
Subscribers [%] standing for the amount of subscribers being active during the busy hour.
Table:
Capacity
GSM/EDGE
[transceivers]
WCDMA
528
[channel elements]
HSDPA
756
[Mbps]
HSUPA
115
[Mbps]
LTE DL
450
[Mbps]
LTE UL
150
[Mbps]
LTE BW/cell
20
[MHz]
LTE cells
3
[cell count]
MIMO (HSPA/LTE) yes
Table:
Capacity
Table:
GSM/EDGE
[transceivers]
WCDMA
N/A
[channel elements]
HSDPA
N/A
[Mbps]
HSUPA
N/A
[Mbps]
LTE DL
440
[Mbps]
LTE UL
108
[Mbps]
LTE BW/cell
20
[MHz]
LTE cells
4
[cell count]
MIMO
yes
Single FSIH or FBIH module supports the following configurations:
Table:
Capacity
GSM/EDGE
[transceivers]
WCDMA
[channel elements]
HSDPA
[Mbps]
HSUPA
[Mbps]
LTE DL
[Mbps]
LTE UL
[Mbps]
LTE BW/cell
[MHz]
N/A
N/A
756
N/A
N/A
157
N/A
N/A
450
450
440
150
150
108
20
20
20
Table:
Capacity extension sub-module air interface peak throughput
LTE cells
3
3
4
[cell count]
MIMO (HSPA/LTE) yes
yes
yes
The GSM/EDGE capacity is measured as the number of transceivers. The WCDMA capacity
is measured as the number of Channel Elements, while the HSPA capacity is measured as
megabits per second. WCDMA traffic dimensioning principles are described in other
documents (see Plan and Dimension category in the library). HSPA users and data might have
an impact on the number of AMR calls.
Additionally, LTE has a bandwidth and cell count limitation. For more information, see
Feature Descriptions and Instructions in LTE Operating Documentation library.
For more information, see Flexi Multiradio Base Station and Flexi Multiradio 10 Base Station
Optional Items Description.
Example: UE of category 3
o maxBitRateDl = 120 Mbps
o maxBitRateUl = 20 Mbps
o Maximum DL bit rate: 102.048 Mbp (lower value coming from UE category)
o Maximum UL bit rate: 51.024 Mbps (lower value coming from the operatorconfigurable parameters)
Table:
Summative comparison between UMTS and LTE
Flat Architecture
No (includes RNC) Yes (excludes RNC)
Neighbour Planning Required
Yes
No
Scrambling Code Planning Required Yes
No
Physical Layer Cell Identity
No
Yes
Planning Required
The capability of UMTS is evolving throughout the various releases of the 3GPP
specifications. For example, the use of either 64QAM or MIMO is introduced within
the release 7 version of the specifications. The use of both 64QAM and MIMO is
introduced within the release 8 version of the specifications. Historically, UMTS has
been limited to a 5 MHz channel bandwidth whereas the release 8 version of the
specifications introduces the pairing of two 5 MHz channels to effectively provide a
10 MHz channel band-width. This is limited to HSDPA within the release 8 version of
the specifications but is extended to HSUPA in the release 9 version. This evolution of
the UMTS specifications allows UMTS to remain competitive with LTE although
LTE has the fundamental key advantages of a potential 20 MHz channel bandwidth
and a flat architecture. Furthermore, LTE does not experience intracell interference
compare to UMTS or HSPA system, which results in better spectral efficiency.
Cell capacity improvement was out of primary focus during feature specification and
potential gains in this area will come rather as a "side effect". These gains will come from the
improved scheduling flexibility especially for the traffic with highly bursty nature. Note
however that even without CA the DL scheduler is already dealing with resource allocation in
highly efficient manner.
Figure:
Carrier aggregation cell capacity requirement
One of the significant influences on the baseband capacity is in the area of maximum amount
of active users (so RRC connected UEs with DRB established): still 420 users per cell could
be active (like in non-CA case with 6 cells), however, maximum 50 out of them can have this
cell configured as a primary one. Additionally, maximum other 50 UEs can have this cell
configured as a secondary one.
This means that at maximum 50*6 = 300 users could be configured with Carrier Aggregation
- in such a case the total number of active users per eNB is equal to 6*(420-50) = 2220. The
concept is shown in the following figure.
Link Budget is calculated taking into account achievable DL/UL throughput for the single UE
at certain distance/pathloss from the serving eNB. Considering the fact that the CA UE
receives the data from two carriers the maximum allowable pathloss, for which the DL
service requirements are still satisfied, will be increased. However, note that cause Carrier
Aggregation is introduced solely in the downlink direction, the overall DL/UL budget would
not benefit from CA activation once the service is UL limited.
Figure:
Carrier aggregation cell capacity requirement
Table:
Local cell resource ID of cell to be
aggregated
Activation of downlink carrier aggregation
EARFCN downlink
Cell sector id
Sched Carrier Aggr fairness control factor
SCell activation cycle period
Max number Carrier Aggr configured UEs
double carrier
Min UE-AMBR downlink for carrier
aggregation
SCell activation method
Disable PDCCH outer loop link adaptation
in SCell
SCell and PCell ambiguous HARQ feedback
usage
SCell deactivation timer eNB
Carrier aggregation relation identifier
LNBTS
LNCEL
LCELL
CAREL
LNBTS
LNCEL
caMinDlAmbr
LNBTS
sCellActivationMethod
disableSCellPDCCHOlLa
LNBTS
CAREL
sCellpCellHARQFdbkUsage LNBTS
sCellDeactivationTimereNB LNBTS
caRelId
CAREL