Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
CA principles
A regular cell is paired with additional logical
cell serving the same site sector.
this dependency could be bi-directional,
this first cell could serve as secondary cell
PCell and SCell have to be collocated
RL50 supports inter-band CA only
RL60 starts with selected intra-band CA
only non-GBR data could be sent via Scell
all CA configured cells serve simultaneously
CA UEs and also regular, non-CA Ues
there is no CA in the uplink direction
CA capable UE
Carrier 1, P.Cell
Carrier 2, S.Cell
DL Carrier Aggregation
Downlink data rates of up to 300Mbps
Downlink carrier aggregation - 40 MHz (RL60)
Challenges
Fragmented spectrum availability with Operators (multiple bands)
Higher throughput / Capacity required to cater exponential growth in mobile broadband
traffic
High churn due low peak data rate
Motivation, Benefits
Doubling the DL peak data rates to 300 Mbps
Very fast load balancing between carriers (on TTi level)
A mix of carrier aggregation UEs and non-carrier aggregation UEs are supported in
downlink
All HO types are supported between CA and Non-CA cells
ARPU increase due to higher data package prices
Mitigates the challenge of fragmented spectrum
The downlink carrier aggregation is applied for
UEs with the related UE capabilities and
UEs having only non GBR e-RABs established
UEs are admitted based on the primary component carrier (PCC) admission
control settings
The mobility for carrier aggregation configured UEs is based on PCC
measurements (HO works with one carrier PCC)
UEs with an activated SCC are scheduled by separate and coordinated downlink
schedulers
Both Inter band and Intra band combination is possible.
The two component carriers can have different MIMO settings, e.g.
2x2 MIMO + 2x2 MIMO
4x2 MIMO + 2x2 MIMO
4x2 MIMO + 4x2 MIMO
Primary
Comp.
Carrier
Seconda
ry
Comp.
Carrier
Band A
150Mbps
20 MHz
Carrier
Aggregation
Band B
20 MHz
40 MHz
150Mbps
300Mbps
DL Carrier Aggregation
RL60 embodiment of Carrier Aggregation functionality
20 MHz
20 MHz
band 1 + band 7
band 2 + band 4
band 2 + band 5
band 2 + band 17
band 3 + band 3
band 3 + band 7
band 3 + band 20
band 4 + band 4
band 4 + band 17
band 5 + band 7
band 7 + band 20
band 4 + band 12
band 3 + band 28
band 4 + band 7
band 7 + band 7
2.6 G
1.8 G
I own
S
I oth N
Required SINR
In order to meet the defined quality requirements (BLER) a certain average required SINR is needed
Required SINR depends on:
Based on the Cell Edge Throughput the number of allocated PRBs and the MCS could be defined see next slides
Channel model is a way to consider UE mobility and environment in the link budget calculation
1Tx 2Rx; 2TX 2RX Transmit Diversity ; 2TX 2RX Spatial Multiplexing (not expected at cell edge)
L1 overhead of the physical channels
-
The impact is the reduced number of resource blocks which could be used for user data
Scheduling gain
see next slides
BLER
TBS =
Transport
Block Size
Output: TBS (Transport Block Size) & Number of Required RBs (Resource Blocks) see next slide
MCS
#RBs =
Number of
Resource
Blocks
DL MCSs
MCS_index
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
MCS
QPSK
QPSK
QPSK
QPSK
QPSK
QPSK
QPSK
QPSK
QPSK
QPSK
16QAM
16QAM
16QAM
16QAM
16QAM
16QAM
16QAM
64QAM
64QAM
64QAM
64QAM
64QAM
64QAM
64QAM
64QAM
64QAM
64QAM
64QAM
64QAM
Mod order
2
2
2
2
2
2
2
2
2
2
4
4
4
4
4
4
4
6
6
6
6
6
6
6
6
6
6
6
6
ITBS
0
1
2
3
4
5
6
7
8
9
9
10
11
12
13
14
15
15
16
17
18
19
20
21
22
23
24
25
26
Assumptions:
Required cell edge throughput = 384Kbps
MCS = 10-16QAM
MCS = 10-16QAM TBS_index = 9
Air Interface User Throughput =
= 384 / (100% - 10%) = 427 kbps
search for TBS in ITBS9 Air Interface User Throughput
#RB_used = 3 TBS = 456 bits
456 bits/TTI = 456 bits/1 ms = 456 kbps 427 kbps
Conclusion: # RB used= 3
Identifies the number of Resource Blocks (RB) required to achieve the target
Cell Edge User Throughput
Uses the already defined MCS to identify the appropriate row within
the transport block size table
The target Cell Edge User Throughput is used to determine the
minimum transport block size requirement
Example:
SINR table for the case DL 2Tx-2Rx, EPA 5Hz Channel Model, BLER
= 10%
EPA 5Hz Doppler frequency=5Hz for 1800MHz and 3km/h
Gain (dB)
3,71
3,64
3,53
3,41
3,25
2,93
2,52
2,11
1,68
0
The more UEs could be scheduled in the same TTI (that means less resource allocation per user), the more certain gain can
be observed.
Example:
Cell edge Throughput is 1024Kbps, Number of allocated PRBs per user is selected to be 13 out of 50 available in 10 MHz (for
MCS = 5-QPSK)
The channel usage per TTI of the user is 26%. Thus, Required SINR = 1,11 dB(Required SINR from table) 2,47 dB (FDPS
gain for 26% channel usage) = -1,36dB
The larger the amount of resources (subcarriers) available for the scheduling of a single user, the higher the chance to avoid
channel quality gaps
For example when 50 PRBs are available (10MHz bandwidth) and 10 full user buffer UEs are scheduled per TTI then it
results 5 PRBs per user that is 10% of resources allocated per UE.
11
UL Required SINR
The selection of MCS in UL is a trade-off between a lower required SINR value and the number of allocated PRBs per
UE:
UE output power is shared between the subcarriers assigned for transmission.
The smaller the number of used subcarriers the higher is the power per subcarrier so the higher the coverage. On the
other hand, lower number of PRBs per UE (lower number of subcarriers) requires a higher order MCS - increasing the
required SINR.
In this case, despite of a higher required SINR, a greater cell range could be obtained due to the accumulation of the total
power on less PRBs used for the transmission.
12