Академический Документы
Профессиональный Документы
Культура Документы
1 Overview
2 Principle Concepts
3 CA Configuration Mode
4 CA Application Scenario
5 CA Scheduler
6 DL 3CC CA
7 CA Optimization
8 CA Counters
Single PDCP entity and RLC entity for each radio bearer
* The CA UE still has only one RRC connection with the network (in the PCell) and is allocated only one C-RNTI.
The PCell transmits NAS messages for the UE.
** The PUCCH exists only in the PCell.
*** The number of downlink SCCs is greater than or equal to the number of uplink SCCs.
**** If a radio link failure (RLF) occurs in the PCell, an RRC connection reestablishment procedure is triggered.
F1 F1
F1
Technology F1 (UL) FDD
F2 F2
F2
F2 (UL) TDD
F3 F3
F1 BBU F1
BBU F1
Scenario
F2 F2 F2
F2 BBU F2
1 Overview
2 Principle Concepts
3 CA Configuration Mode
4 CA Application Scenario
5 CA Scheduler
6 DL 3CC CA
7 CA Optimization
8 CA Counters
SCell
A secondary serving cell (SCell) is a cell that works at a different frequency from the PCell. The eNodeB configures an
SCell for a CA UE through an RRC Connection Reconfiguration message. An SCell provides the CA UE with more
radio resources. The CA UE can have only downlink SCells or both downlink and uplink SCells.
CC
Component carriers (CCs) are the carriers that are aggregated for a CA UE.
PCC
The primary component carrier (PCC) is the carrier of the PCell.
SCC
A secondary component carrier (SCC) is the carrier of an SCell.
PCC Anchoring
During PCC anchoring, the eNodeB selects a high-priority cell as the PCell for the UE.
Event A3: indicates that the signal quality of the PCell's neighboring cell becomes higher than that of the PCell.
Event A4: indicates that the signal quality of a neighboring cell becomes higher than a specific threshold.
Event A5: indicates that the signal quality of the PCell becomes lower than a specific threshold and the signal quality of a
neighboring cell becomes higher than another specific threshold.
Event A6: indicates that the signal quality of an SCell's intra-frequency neighboring cell becomes higher than that of the
SCell. If the eNodeB receives an event A6 report, it changes the SCell while keeping the PCell unchanged.
The entering condition for event A6 is as follows: Mn + Ocn - Hys > Ms + Ocs + Off.
PDSCH
PDCCH
3 status for CA UEs: SCC SCC
• Single CC: same as a non-CA UE PCC
PCC
• SCC_Activated
PU CH
PU
PU CH
PU
ActivationDeactivation
CC
•
S
SCC_Deactivated
CC
S
H
PD CH
H
H
PD CH
SC
H
C
SC
PD
C
PD
Activation (by traffic)
RLC buffer length > max (RLC data rate * ActiveBufferDelayThd,
ActiveBufferLenThd)
Delay of the first RLC PDU > ActiveBufferDelayThd
Deactivate (by traffic)
Note: RLC data rate ≤ DeactiveThroughputThd
• Only eNodeBs can deactivate or remove SCells (SCells can RLC buffer length ≤ DeactiveBufferLenThd
be deactivated, but PCells cannot).
Deactivate (by CQI)
CQI ≤ SccDeactCqiThd
HUAWEI TECHNOLOGIES CO., LTD. Page 10
Principle Concepts(SCC Activation Threshold)
SCC activation threshold:
Buffer Length: It indicates how many bits are there in the buffer waiting to be scheduled to send to UE via UU interfac
e. It's not related to Throughput.
When RLC data rate=0 (e.g. due to poor UU quality), suppose the actual buffer length is still 3Mbit as above and A
ctiveBufferLenThd is set to 9KB. In this case we need to compare the actual buffer length and ActiveBufferLenThd.
As 3Mbit > 72Kbit, the first condition is met.
ENodeBAlgoSwitch.CaAlgoSwitch: Example:
SCellBlindConfSwitch = ON When a CA UE initiates an RRC connection in the 2.6 GHz cell, the
PccAnchorSwitch = ON eNodeB changes the PCell to the 2.1 GHz cell for the UE and then
selects the blind-configurable 850 MHz cell as an SCell.
1 Overview
2 Principle Concepts
3 CA Configuration Mode
4 CA Application Scenario
5 CA Scheduler
6 DL 3CC CA
7 CA Optimization
8 CA Counters
* If SCellPriority set to be 0, then the related cell not able to be configured to be SCC for the PCC. For example, as configuration
as above, the cell0 is not able to be configured as SCC for cell1.
* If SCellBlindCfgFlag set to be false, then the Scell is configured by the A4 measurement result. And if it set to be true, then
configure the Scell by blind mode.
1 Overview
2 Principle Concepts
3 CA Configuration Mode
4 CA Application Scenario
5 CA Scheduler
6 DL 3CC CA
7 CA Optimization
8 CA Counters
1 Overview
2 Principle Concepts
3 CA Configuration Mode
4 CA Application Scenario
5 CA Scheduler
6 DL 3CC CA
7 CA Optimization
8 CA Counters
40 40 Case 1 33 33
20 User distribution 33
Case 1
User distribution 20 is even 33
is even 40 40 33 33
25 25 25 25 0 Case 2 20 20 20 20
Case 2 PCC has more
20
PCC has more 50 users 50
users 50 50
1 Overview
2 Principle Concepts
3 CA Configuration Mode
4 CA Application Scenario
5 CA Scheduler
6 DL 3CC CA
7 CA Optimization
8 CA Counters
SCell configuration/removal:
After a 3CC-CA-capable UE accesses or is handed over to a cell, the eNodeB selects two cells based on measureme
nts or in a blind manner and sends an RRCConnectionReconfiguration message to configure the cells as SCells for th
e UE.
If the RSRP of an SCell is lower than the threshold for event A2, the eNodeB removes the SCell. Alternatively, the eNo
deB deactivates but does not remove the SCell.
When a UE is served by one or two carriers, the eNodeB configures an SCell for the UE (either based on measureme
nts or in a blind manner) if the traffic volume meets specific conditions.
SCell activation/deactivation:
If the traffic volume meets specific conditions, the eNodeB delivers an MAC CE to activate or deactivate both SCells.
The traffic volume evaluation criteria and thresholds are the same as those used in SCell activation for DL 2CC CA.
Feature activation
In CA-group-based configuration mode, configure three inter-frequency cells in each CA group.
In frequency-based configuration mode, configure three candidate SCCs for each PCC.
Set CaDl3CCSwitch on.
Feature deactivation
Set CaDl3CCSwitch off.
1 Overview
2 Principle Concepts
3 CA Configuration Mode
4 CA Application Scenario
5 CA Scheduler
6 DL 3CC CA
7 CA Optimization
8 CA Counters
Coverage Threshold CA Traffic Threshold CA Algorithm Threshold Ping-Pong handover PCI Collision
Increase the A2 threshold and Check the network handover
Reduce the traffic activate Adjust the SCC Configuration Interval
SCC Configuration Interval, to Check the PCI collision and
to increase the CA activation ratio. threshold to reduce the ping-
threshold to improve the CA confusion, reduce the probability
increase the CA proportion. pong handover events.
activation ratio. Set the PCC anchor configuration
Decrease the A4 threshold to of unable to configure the CA
according to the field condition to increase Resolve the ping-pong
Reduce the traffic activation
make the UE enter CA state be due to PCI collision & confusion.
the CA throughput. handover issue due to the weak
buffer threshold to improve the
quicker. coverage, non pilot coverage,
CA activation ratio. Set the Differentiated Scheduling to
increase the CA Throughput. etc.
Throughput is
Scell is not DT KPI issue
too low after
configured Scell activation
issue issue.
1 Overview
2 Principle Concepts
3 CA Configuration Mode
4 CA Application Scenario
5 CA Scheduler
6 DL 3CC CA
7 CA Optimization
8 CA Counters
L.ChMeas.PRB.DL.SCell.Used.Avg Average number of downlink PRBs occupied by CA UEs that use the local cell as their secondary serving cell
L.Traffic.User.PCell.DL.Avg Average number of downlink CA UEs that use the local cell as their primary serving cells
L.Traffic.User.PCell.DL.Max Maximum number of downlink CA UEs that use the local cell as their primary serving cells
L.Traffic.User.SCell.DL.Avg Average number of downlink CA UEs that use the local cell as their secondary serving cells
L.Traffic.User.SCell.DL.Max Maximum number of downlink CA UEs that use the local cell as their secondary serving cells
L.Thrp.bits.DL.CAUser Total traffic volume for PDCP SDUs sent to activated CA UEs in a cell
L.Thrp.Time.DL.CAUser Total duration for activated CA UEs transmitting downlink data at the PDCP layer in a cell
L.HHO.PrepAttOut.CAUser.PCC Number of outgoing handover attempts for CA UEs that use the local cell as their PCell
L.HHO.ExecAttOut.CAUser.PCC Number of outgoing handover executions for CA UEs that use the local cell as their PCell
L.HHO.ExecSuccOut.CAUser.PCC Number of successful outgoing handovers for CA UEs that use the local cell as their PCell