Training Documentation - eRAN TDD 8.0 CA-20141024-A-1.0

Security level: Internal only
LTE eRAN TDD 8.0

Carrier Aggregation
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Contents
1 Overview and Benefits
2 Concepts and Principles
3 FL, Configurations, and Maintenance
4 Key Parameters and Counters
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

Overview
Description
• eNodeBs support aggregation of two contiguous or non-contiguous carriers (referred to as
CA in this document) on the DL with subframe configuration 1 or 2.
• eNodeBs support a maximal bandwidth of 40 MHz.
• The two aggregated carriers serve two independent cells, where UEs complying with
3GPP Release 8 and Release 9 can access the network.
• eNodeBs of eRAN TDD 8.0 support MIMO multiplexing of only two streams.
Benefits
• Increases the resource usage efficiency.
• Improves user experience: The DL peak rate of CA UEs is 100% higher than that of
non-CA UEs.
Dependencies
• CA implementation requires support of commercial UEs.

New Functions Introduced to eRAN TDD 8.0
 Aggregation of two carriers in high-speed mobility scenarios
In high-speed mobility scenarios, carriers serving cells with the same coverage areas can be aggregated.
 Blind SCell configuration is recommended, which shortens the delay caused by measurements and helps
to achieve fast SCell configuration.
 Static configuration is adopted for PUCCH resources, which reduces the system processing workload for
an increase or a decrease in resource demand and thereby, improves user experience.
 Band expansion: Aggregation of 15 MHz carriers is supported.

 Blind SCell configuration
When CA groups have been configured, the eNodeB configures an SCell for a CA UE immediately after a
service of the UE is established. In this way, fast SCC configuration can be achieved. This mechanism applies
to networks with the same coverage area to improve CA UEs' user experience in the case of handovers.

New Functions Introduced to eRAN TDD 7.0
 Aggregation of two carriers selected out of
multiple carriers
An operator with rich spectrum resources possibly
has already deployed an LTE network using three or
four carriers. To improve user experience and CA
values, the operator needs to select two carriers for
aggregation based on the UE capabilities.
 Presetting carriers for PCC configuration
and management
 An operator may require that a certain carrier be preferentially configured as a primary component carrier (PCC). To meet
this requirement, a preferred PCC selection switch and a PCC-oriented carrier priority parameter are added to the
eNodeB.
 If a UE reports its CA capability, the eNodeB checks whether the used carrier is the preset PCC-oriented highest-priority
carrier after RRC connection establishment for initial network access. If the used carrier is not the preset PCC-oriented
highest-priority carrier, the eNodeB instructs the UE to measure the preset carrier. If this carrier meets measurement
criteria, the eNodeB instructs the UE to hand over to this carrier.
 CA in SFN scenarios
 A CA UE using an SFN cell as the SCell has lower scheduling priority in the SCell than non-CA UEs. The eNodeB
performs joint scheduling and uses TM2 (in the case of a single antenna) or TM3 for this UE on the SCC.
 In the PCell, scheduling for the CA UE is the same as that for common UEs.
Application Scenarios
Intra-band carriers Inter-band carriers Complex antenna systems
F1 F2
S1 S2 S3
S4, RRH S5, repeater
UL CA requires multi-TA.
eRAN TDD 8.0 supports CA only in scenarios 1 and 2, and later versions will support CA in the other scenarios.

Benefits
 Better QoS guarantee for CA UEs: CA can be used to serve high-value customers, thereby acquiring higher gains (higher APRU).
 Maximized resource usage efficiency: A CA UE can use idle RBs on the two carriers to minimize the waste of resources.
 Better user experience: The DL peak rate of CA UEs (Category 6) is 100% higher than that of non-CA UEs. In a commercial
network where more than one UE reside, idle resources can be used more efficiently after secondary cells (SCells) are activated for
CA UEs, which improves the network throughput (in non-full loading scenarios) and user experience.
90% PRB usage 95% PRB usage Cell A @

With CA Frequency 1
70% PRB usage 95% PRB usage Cell B @

Frequency 2
3GPP Release 8/9-compliant UE CA UE

Contents

CA Protocol Architecture
A single radio bearer has only one Packet Data

Convergence Protocol (PDCP) entity and one
Radio Link Control (RLC) entity. In addition, the
number of component carriers (CCs) at the
physical layer is invisible to the RLC layer.
Each CC schedules data independently at the

MAC layer.
Each carrier has its independent initial

transmission and HARQ retransmission
processes.
(1) RRC connection (C-RNTI, NAS) can be established only in the primary cell (PCell).
(2) The PUCCH can be established only in the PCell.
(3) RRC connection reestablishment is triggered if a radio link failure (RLF) occurs in the PCell.

CA Service Process
1. Configuration of CA groups and other CA-

related parameters.
2. Initial RRC connection setup for a CA UE in a cell
Included only if blind SCell Event A4-based measurement configurations on cells in

a CA group
configuration is disabled.
Event A4-based measurement reports
RRC reconfiguration message for Scell configuration.
3. SCell configuration for the UE.
4. SCell activation or deactivation based on the traffic

volume
1. CA groups with cells available for aggregation are configured, and other CA-related parameters are set.
2. A CA UE initiates a service and sets up an initial RRC connection in a cell (PCell). This procedure is similar to that of a common UE (complying with 3GPP Release 8/9).
3. If the blind SCell configuration switch is turned off, the eNodeB instructs the UE to measure the other cells that belong to the same CA group as the PCell. If any cell
meets measurement criteria, the eNodeB sends an RRC reconfiguration message to the UE to configure the cell as the SCell. If the blind SCell configuration switch is
turned on, the eNodeB performs blind SCell configuration.
4. The eNodeB checks the traffic volume. When the traffic increases, the eNodeB timely activates the SCell so that the PCell and SCell transmit data at the same time.
When the traffic decreases, the eNodeB timely deactivates the SCell to save power for the UE.

Carrier Management (1/4)
 A CA UE has three possible statuses:
1. CC_Unconfigured: The SCell has not been configured.

2. CC_Configured_SCC_Deactivated: The SCell has been
configured but not activated.
3. CC_Configured_SCC_Activated: The SCell has been
configured and activated.
 The CA status transitions in the following typical scenarios:
 Scenario 1: SCC configuration triggered based on event A4

 Scenario 2: SCC activation or deactivation triggered based on
the traffic volume
 Scenario 3: SCC removal triggered based on event A2
 Scenario 4: Handovers
Note:
(1) Only the eNodeB can deactivate or delete an SCell.
(2) The SCell can be deactivated, but the PCell cannot.
(3) A handover is required to change the PCell for a CA UE.

Service established
Typical scenarios of CA status transition
Scenario 1: SCC configuration triggered based on event A4

N
 After services are established, the eNodeB delivers event A4- Event A4-based
measurement
based measurement configurations for the SCC. After receiving

Y
an event A4 measurement report, the eNodeB sets the UE state
CC_Configured
to CC_Configured.
8 ms later *
Staying in the
CC_Unconfigured state
SCC Activated
*According to 3GPP specifications, an interval of at least eight subframes must

be reserved between SCC configuration and activation.

Typical scenarios of CA status transition
Scenario 2: SCC activation or deactivation triggered based on the traffic volume
PDCCH
SCC PDSCH SCC
x>=8
PCC eNodeB PCC

UE
n n+x-4 n + x ms
ActivationDeactivation
The eNodeB can activate and deactivate the SCC using MAC control elements.
 When the DL throughput is greater than the threshold for SCC activation, the eNodeB activates the SCC.
 When the DL throughput is less than the threshold for SCC deactivation, the eNodeB deactivates the SCC.

Typical scenarios of CA state transfer
CC_Configured
Scenario 3: SCC removal triggered based on event A2
Y
 The eNodeB removes the SCC and sets the CA UE to the
CC_Unconfigured state after receiving an A2 measurement Event A2-based

measurement
N
report from a CA UE in the CC_Configured state.
Y
Staying in the CC
CC_Unconfigured Configured state

Mobility Management (1/3)
CC_Configured CC_Unconfigured
SCC removal with RRC Connection Recfg

RRC Connection Recfg (for HO)
(for HO)
Scenario 4: Handovers
 After a CA UE in the CC_Configured state sends RRC Connection Recfg Cmp (HO completed)
a handover measurement report and carries the

SCC removal information in the RRC
Staying in the
Event A4-based N
reconfiguration message, the eNodeB removes CC_Unconfigured
measurement
state
the SCC. Then, the CA UE returns to the
Y
CC_Unconfigured state after the handover is
complete. Returning to the CC_Configured state
 In addition, the eNodeB re-sends event A4-based

measurement configurations to reconfigure the
SCC, after the handover is complete. Monitoring the traffic volume to trigger SCC activation

Intra-frequency Handovers of CA UEs
• The intra-frequency handover procedure for

CA UEs is almost the same as that for non-CA
UEs.
• The RRC connection reconfiguration message

contains the information about the SCell to be
removed.
Including CellToReleaseList
for SCell removal

Inter-frequency Handovers of CA UEs
• Inter-frequency handovers of CA UEs

The CA UE
and non-CA UEs are based on events
reports event A5.
A5 and A4, respectively.
• The RRC connection reconfiguration

message contains the information about
the SCell to be removed.
Including CellToReleaseList for

SCell removal

CA Scheduling: Architecture
Two-level scheduling
CA Scheduler
• CA-level scheduling
The eNodeB allocates data to each CC based on the CC-

CC0 Scheduler
specific CQI.
• CC-level scheduling
MAC CC0 PHY CC0
The eNodeB calculates the scheduling priority of each carrier.
CC1 Scheduler
The following policies apply to the scheduling: PDCP RLC MAC CC1 PHY CC2
 Fairness: The data rate of a CA UE is the sum of
transmission rates on each CC. The average rate of a CA UE CCn Scheduler
is equal to that of a non-CA UE that runs same-QCI services
in the PCell of the CA UE.
 r(t) = rcc1(t) + rcc2(t) MAC CCn PHY CCn
 Differentiation: For the data rate of a CA UE, the

transmission rate on the PCC and that on the SCC are Note
measured separately. The average rate of a CA UE is the
sum of average rates of non-CA UEs on the two CCs.
If an SFN cell serves as a PCell or SCell of a CA UE, absolute fairness
cannot be guaranteed when scheduling follows the fairness policy,
 r1(t) = rcc1(t)
because of the percentage limitation on the joint scheduling
 r2(t) = rcc2(t) resources.

CA Scheduling: CA-Level Scheduling
Process for CA-level scheduling:
Step 1: The eNodeB allocates data with the ratio 1:1 to the two carriers regardless of the carrier bandwidth.
Step 2: The eNodeB adjusts the data allocation ratio of the two carriers based on the scheduling in each TTI.
Step 2a: If data scheduling can be completed on each carrier, repeat step 1.
Step 2b: If data scheduling cannot be completed on a carrier, the eNodeB collects the remaining data and data to be
scheduled in the next TTI and allocates all the data with the ratio 1:1 to the two carriers in the next TTI.
Step 2a
RLC Buffer
50
100
50
50 50
CC1 CC2

CA Scheduling: CA-Level Scheduling
Step 1 Step 2b Step 3
RLC Buffer 20 will remain RLC Buffer 30 will remain RLC Buffer 35 will remain
in RLC buffer! 60 in RLC buffer! 65 in RLC buffer!
50
TTI1: TTI2: 120 40
TTI3: 130 35
100 50
20 30
50 30 60 30 65 30
CC1 CC2 CC1 CC2 CC1 CC2
Step… Step N
RLC Buffer 40 will remain

70 in RLC buffer!
TTIn: 140
30 As shown in the figures, more data can be scheduled on CC1 than
40
on CC2:
 The amount of data scheduled on CC1 increases per TTI.
70 30  The final ratio of scheduled data is 7:3 (CC1:CC2).
CC1 CC2

CA Scheduling: CC-Level Scheduling
 Fairness Policy
• The RBs allocated to CA UEs are almost the same as the RBs allocated to non-CA UEs.
40 RB PCC
Case 1 20+20=40 RB SCC
PCC&SCC:
normal load 40 RB Non-CA UE
CA UE
100 / 4=24~25 RB Non-CA UE
Case 2 100 / 2=50 RB
PCC heavy load
SCC light load 100 / 2=50 RB A
100 / 2=50 RB
Case 3
PCC light load 100 / 2=50 RB
SCC heavy load 100 / 4=24~25 RB

CA Scheduling: CC-Level Scheduling
 Differentiation Policy
 The eNodeB treats a CA UE as a single UE on each CC for priority calculation and resource allocation.
 Theoretically, the peak rate doubles.
 Different spectral efficiencies between CCs and varied UE locations lead to different system capacities and may lead to
system capacity loss.
PCC
(100/3) = 33 RB
Case1 SCC
33 + 33 = 66 RB
PCC&SCC: Non-CA UE
normal load (100/3) = 33 RB
CA UE
Non-CA UE
100 / 5 = 20 RB
Case2 20 + 50 = 70 RB
PCC: heavy load B
SCC: light load 100 / 2 = 50 RB
100 / 2=50 RB
Case3
PCC: light load 20 + 50 = 70 RB
SCC: heavy load 100 / 5 = 20 RB

CA Admission Control
Admission control is performed based on:
1.UE quantity
2.QoS satisfaction rate
Admission Control Based on the UE Quantity
UE Type Applicable Cell When the UE Quantity Reaches the Limit
 PCC
CA The resources allocated to the CA UEs on the SCC are preempted by non-CA UEs.
 SCC
Non-CA Serving Cell
Admission Control Based on QoS Satisfaction Rate
UE Type Application Applicable Cell Operation After an Admission Failure
CA PCC CA UEs initiate preemption on the PCC.

Only GBR services
Non-CA Serving Cell Non-CA UEs initiate preemption on the serving cell.

CA Congestion Control
Congestion Control
Low-priority GBR services are released to ensure the satisfaction rate of high-priority GBR services.
UE Type Application Applicable Cell Applicable CA UEs
Only GBR services of CA UEs that treat the cell as

CA PCC their PCell and GBR services of non-CA UEs in the
Only GBR services same cell are released.
Non-CA Serving Cell

CA Common DRX
Characteristics Benefits
• The PCell and SCell are configured with the same • The common DRX configurations enable a CA UE to
DRX parameters, including OnDurationTimer, enter or exit DRX mode in the PCell and SCell at the
DRXInactivityTimer, and DRXShortCycleTimer. same time, which helps the UE to save power.

Contents
3 Configurations and Maintenance

Summary
 The eNodeB supports aggregation of two intra-band (contiguous or non-contiguous) carriers on the DL.
 The eNodeB supports aggregation of two inter-band carriers on the DL.
 If scheduling follows the fairness policy, CA UEs have the same scheduling priorities as non-CA UEs, and therefore, CA UEs have
no throughput advantages. If scheduling follows the differentiation policy, CA UEs can obtain throughput gains, and theoretically,
have doubled single-carrier throughput.
 CA UEs can use common DRX configurations to save power.
 Hosting the carrier management function, the eNodeB activates or deactivates the SCell.
Dependencies
 UE: UEs complying with 3GPP Release 10 and later support CA.
 RRU: The time alignment error (TAE) cannot exceed 130 ns between RRUs serving two aggregated contiguous carriers, 260 ns
between RRUs serving two aggregated non-contiguous carriers, and 1300 ns between RRUs serving two aggregated inter-band
carriers.
 EPC: The EPC supports the rate of 224 Mbit/s for a single UE.
License
 An operator must purchase the cell-specific license to activate CA.
 Only the basic license package is required if the total bandwidth of two aggregated carriers is 30 MHz or less.
 Both the basic and enhanced license packages are required if the total bandwidth of two aggregated carriers is greater than 30
MHz and less than or equal to 40 MHz.
 If an operator has deployed three or four carriers, the license for aggregation of two carriers selected out of multiple carriers must
be purchased to implement CA in a multiple carrier scenario.

Guide for Activating CA
Step Command Note
1 ADD CAGROUP Set a CA group (only carriers in the same CA group can be aggregated).
2 ADD CAGROUPCELL Add cells with the same azimuth into a same CA group.
3 ACT CELL If the cell is not being used, perform this step.
If the cell is in use, ignore this step.
Guide for Deactivating CA

Step Command Note
1 RMV CAGROUPCELL Remove cells from a CA group.
2 RMV CAGROUP Remove a CA group.
MOD CELLDLSCHALGO
BASIC_SCHEDULE: default value
DIFF_SCHEDULE: to treat CA UEs as high-priority UEs
MOD CAMGTCFG
OFF: default value
ON: to enable carrier management

Contents

Key Parameters
Parameter
MML Command Meaning ID GUI Value Range Setting Notes
Name
ADD CAGROUP
Specifies a CA group to
LST CAGROUP For one eNodeB, a maximum of 36
CA Group Identity be CaGroupId 0 to 35
MOD CAGROUP CA groups can be configured.
added/modified/removed.
RMV CAGROUP
ADD CAGROUP
Specifies the type of the
CA Group Type LST CAGROUP The value TDD indicates that this CA
CA group to be CaGroupTypeInd FDD, TDD
Indication MOD CAGROUP group is for the TDD system.
added/modified/removed.
RMV CAGROUP
Specifies a cell to be
ADD CAGROUPCELL On one eNodeB, a total of 18 local
CA Group Cell added to or removed from LocalCellId 0 to 17
RMV CAGROUPCELL cells can be configured
the CA group.
The default value is
Downlink CA MOD CELLDLSCHALGO Specifies the scheduling BASIC_SCHEDULE; BASIC_SCHEDULE, and the value
CaSchStrategy
Schedule Strategy LST CELLDLSCHALGO policy for CA UEs. DIFF_SCHEDULE DIFF_SCHEDULE is set to treat CA
UEs as high-priority UEs.
Carrier Specifies whether to The default value is OFF, and the
MOD CAMGTCFG
Management enable carrier CaMgtCfg ON, OFF value ON is set to enable CA carrier
LST CAMGTCFG
Switch management. management.

Key Parameters
GUI Value Recommended
Parameter Name MML Command Meaning ID Range Value
Carrier Aggregation A2 MOD CAMGTCFG Specifies the RSRP threshold used to

CarrAggrA2ThdRsrp -140 to -43 -109 dBm
RSRP threshold LST CAMGTCFG report event A2 for SCell removal.
Carrier Aggregation A4 MOD CAMGTCFG Specifies the RSRP threshold used to

CarrAggrA4ThdRsrp -140 to -43 -105 dBm
RSRP threshold LST CAMGTCFG report event A4 for SCell configuration.
CA Active Buffer Delay Specifies the buffer delay threshold for

MOD CAMGTCFG ActiveBufferDelayThd 10 to 300 50 ms
Threshold SCell activation.
CA Active Buffer Specifies the buffer length threshold for

MOD CAMGTCFG ActiveBufferLenThd 1 to 30 9 KB
Length Threshold SCell activation.
CA Deactive Specifies the service rate threshold for

MOD CAMGTCFG DeactiveThroughputThd 10 to 1000 100 kbit/s
Throughput Threshold SCell deactivation.
CA Deactive Buffer MOD CAMGTCFG Specifies the buffer length threshold for DeactiveBufferLenThd
SCell deactivation. 1 to 10 3 KB
Length Threshold

Counters
Counter Name Meaning
L.ChMeas.PRB.DL.PCell.Used.Avg Number of downlink PRBs occupied by CA UEs that treat the local cell as their PCell
L.ChMeas.PRB.DL.SCell.Used.Avg Number of downlink PRBs occupied by CA UEs that treat the local cell as their SCell
L.Traffic.User.PCell.DL.Avg Average number of downlink CA UEs that treat the local cell as their PCell
L.Traffic.User.PCell.DL.Max Maximum number of downlink CA UEs that treat the local cell as their PCell
L.Traffic.User.SCell.DL.Avg Average number of downlink CA UEs that treat the local cell as their SCell
L.Traffic.User.SCell.DL.Max Maximum number of downlink CA UEs that treat the local cell as their SCell
L.Thrp.bits.DL.CAUser Total traffic volume of PDCP SDUs sent to CA UEs in the local cell
L.Thrp.Time.DL.CAUser Total time spent on sending data to CA UEs in the local cell
L.E-RAB.AbnormRel.CAUser Total number of abnormal service releases for CA UEs in the local cell
L.E-RAB.NormRel.CAUser Total number of normal service releases for CA UEs in the local 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

Counters
Counter Name Meaning
Number of SCell configuration attempts for CA UEs based on event A4 reports, excluding the attempts triggered by blind
L.CA.DLSCell.Add.Meas.Att
SCell configuration
Number of successful SCell configurations for CA UEs based on event A4 reports, excluding the attempts triggered by blind
L.CA.DLSCell.Add.Meas.Succ
SCell configuration
L.CA.DLSCell.Rmv.Meas.Att Number of SCell removal attempts for CA UEs based on event A2 reports
L.CA.DLSCell.Rmv.Meas.Succ Number of successful SCell removals for CA UEs based on event A2 reports
L.CA.DLSCell.Add.Blind.Att Number of blind SCell configuration attempts for CA UEs
L.CA.DLSCell.Add.Blind.Succ Number of successful blind SCell configurations for CA UEs
L.CA.DLSCell.Mod.Att Number of SCell change attempts for CA UEs based on event A6 reports.
L.CA.DLSCell.Mod.Succ Number of successful SCell changes for CA UEs based on event A6 reports.
L.HHO.InterFddTdd.PrepAttOut.CAUser.
Number of inter-duplex-mode outgoing handover attempts for CA UEs that use the local cell as their PCell
PCC
L.HHO.InterFddTdd.ExecAttOut.CAUser.
Number of inter-duplex-mode outgoing handover executions for CA UEs that use the local cell as their PCell
PCC
L.HHO.InterFddTdd.ExecSuccOut.CAUs
Number of successful inter-duplex-mode outgoing handovers for CA UEs that use the local cell as their PCell
er.PCC

Summary
CA implementation is specific to each UE, and CA UEs may use different cells as their
PCells.
The RRC connection and PUCCH for a CA UE are established only in the PCell.
Differentiated scheduling brings better user experience to CA UEs, and provides CA

UEs with higher rates than non-CA UEs.
CA can improve user experience but cannot increase the network capacity.

Thank you
www.huawei.com

Training Documentation - eRAN TDD 8.0 CA-20141024-A-1.0

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Training Documentation - eRAN TDD 8.0 CA-20141024-A-1.0

Загружено:

Авторское право:

Доступные форматы

Security level: Internal only

LTE eRAN TDD 8.0

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

1 Overview and Benefits

2 Concepts and Principles

3 FL, Configurations, and Maintenance

4 Key Parameters and Counters

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

 Aggregation of two carriers in high-speed mobility scenarios

 Band expansion: Aggregation of 15 MHz carriers is supported.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 4

S4, RRH S5, repeater

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6

90% PRB usage 95% PRB usage Cell A @

70% PRB usage 95% PRB usage Cell B @

3GPP Release 8/9-compliant UE CA UE

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7

1 Overview and Benefits

2 Concepts and Principles

3 FL, Configurations, and Maintenance

4 Key Parameters and Counters

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 8

A single radio bearer has only one Packet Data

Each CC schedules data independently at the

Each carrier has its independent initial

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 9

1. Configuration of CA groups and other CA-

2. Initial RRC connection setup for a CA UE in a cell

Included only if blind SCell Event A4-based measurement configurations on cells in

RRC reconfiguration message for Scell configuration.

3. SCell configuration for the UE.

4. SCell activation or deactivation based on the traffic

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10

1. CC_Unconfigured: The SCell has not been configured.

 The CA status transitions in the following typical scenarios:

 Scenario 1: SCC configuration triggered based on event A4

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11

Scenario 1: SCC configuration triggered based on event A4

based measurement configurations for the SCC. After receiving

*According to 3GPP specifications, an interval of at least eight subframes must

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12

PCC eNodeB PCC

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13

CC_Unconfigured state after receiving an A2 measurement Event A2-based

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14

SCC removal with RRC Connection Recfg

a handover measurement report and carries the

 In addition, the eNodeB re-sends event A4-based

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15

Intra-frequency Handovers of CA UEs

• The intra-frequency handover procedure for

• The RRC connection reconfiguration message

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16

• Inter-frequency handovers of CA UEs

• The RRC connection reconfiguration

Including CellToReleaseList for

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17

The eNodeB allocates data to each CC based on the CC-

 Differentiation: For the data rate of a CA UE, the

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 18

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 19