6 Lteadvancefeature 160412153349

6.
LTE Advance Feature
Author : Ray Khastur

Title : LTE Optimization Consultant MobileComm Professionals, Inc MobileComm Professionals, Inc
Consulting | Training | Research

Company Confidential - Pinnacle Learning Center
6.1 LTE Broadcast (eMBMS)

Service Orientation & Network Impact
• Area where have similarity • eMBMS Service must be guarantee that

interest same service for in this specific area have only UE with
watching TV by mobile phone capability to decode MBSFN radio frame
to use MBMS service, otherwise
(shoping mall, football match
Incompatible UE will have negative
stadium, residential). effect in MBSFN Service area (SINR
• Operator which providing triple Fluctuated, Access Failure, Throughput
play service and don’t want to Issue.
waste existing radio resource for • If MBSFN Reserved Cell are not planning
Unicast Service can utilize well, great Inter cell interference will be
eMBMS service which consume occur due to TDD Interference from
specified radio resource for Normal CP will be collision with
Broadcast service without Extended CP and UE will confuse to
decode MCCH and make KPI
deteriorate PRB Utilization.
degradation.
MobileComm Professionals, Inc

Related Feature License Required &
MBSFN Review
• TDLOFD-070220 eMBMS Phase 1 based on Centralized MCE
Architecture
– TDLOFD-07022001 Multi-cell transmission in MBSFN area
– TDLOFD-07022002 Mixed transmission of unicast and broadcast
– TDLOFD-07022003 Data synchronization
– TDLOFD-07022004 Session admission control
• TDLOFD-080210 eMBMS Service Continuity
•MBSFN synchronization area

MBSFN is short for Multimedia Broadcast multicast service Single Frequency
Network. Within an MBSFN synchronization area, all eNodeBs must be
synchronized by frequency, time, and phase and must support MBSFN
transmissions. In accordance with 3GPP TS 36.300, on a given frequency
layer, an eNodeB can belong to only one MBSFN synchronization area.
•MBSFN transmission
MBSFN transmission is a simulcast transmission technique achieved
by transmitting identical waveforms at the same time from all cells
within an MBSFN area. A UE regards an MBSFN transmission from
multiple cells as a single transmission, as shown in Left Picture. The
UE combines the MBSFN signals received from multiple cells as
multipath signals from a single cell, thereby mitigating inter-cell
interference and achieving combining gains.

MBSFN Review (Cont’d)
• MBSFN area reserved cell
MBSFN area reserved cells are a type of special cells in
MBSFN areas. The MBSFN subframes in the cells are not
used for MBSFN transmissions. MBSFN area reserved cells
are deployed at the edges of MBSFN areas to control
interference between broadcast cells and neighboring cells.
The neighboring cells may be unicast cells or belong to another
MBSFN area. MBSFN area reserved cells use the same
MBSFN subframe configuration as other cells in the same
MBSFN area.
Take the interference of broadcast cells to neighboring unicast
cells as an example. At the edge of an MBSFN area, broadcast
cells are adjacent to unicast cells. The signals in an MBSFN
subframe from multiple broadcast cells are combined, causing
greater interference on the unicast cells in the subframe than
non-MBSFN cells do. As a result, the coverage areas of the
unicast cells shrink. The unicast cells also cause interference
on the broadcast cells in MBSFN subframes. Therefore,
MBSFN area reserved cells are required at the edges of
MBSFN areas to separate the broadcast cells from the unicast
cells.
As stipulated by 3GPP specifications, MBSFN subframes in
MBSFN area reserved cells are not used for MBSFN
transmissions, but can be used to transmit unicast service data
at limited power. However, Huawei eMBMS does not allow
MBMS or unicast service data transmissions using MBSFN
subframes in MBSFN area reserved cells. Therefore, resources
are wasted if an excessive number of MBSFN area reserved
cells are configured. You are advised to configure the outmost
ring of cells within an MBSFN area as MBSFN area reserved
cells. MobileComm Professionals, Inc

BOLT 4G LTE Radio Frame Configuration
BOLT Subframe Allignment

configuration using SA2 (3:1) with
Special Subframe Pattern 7 (10:2:2)
with Normal Cyclic Prefix

eMBMS Architecture & Interface
3GPP Common Architecture
Brief Summary:
HUAWEI Architecture
• Maximum only 3 MBSN area can be setup in one

carrier.
• Maximum 4 Subframe can be used to transmit
PMCH.

New Channel
MTCH : Multicast Traffic Channel
MCCH : Multicast Control Channel
PHICH : Physical HARQ Indicator Channel PCFICH : Physical Control Format Indicator Channel PDCCH : Physical Downlink Control Channel
PBCH : Physical Broadcast Channel PDSCH : Physical Downlink Shared Channel PMCH : Physical Multicast Channel

eMBMS Frame Structure
HUAWEI
TD-LTE SA2
Config

eMBMS Frame Structure (cont’d)
Normal CP *Hybrid Normal CP *Hybrid
Combination first two symbols Normal CP for PDCCH and 10 symbols Extended CP form
*Hybrid : PMCH transmission
A single MBSFN subframe is

divided into a non-MBSFN region
and an MBSFN region. The non-
Extended CP MBSFN region is used to transmit
Normal CP the physical downlink control
channel (PDCCH) required for
normal-subframe transmission.

MBSFN Subframe Characteristic
• MBSFN reference signals are always transmitted on antenna port

4. R4s in Beside Picture denote the reference signals. For details about
the reference signals, see section 6.10.2 "MBSFN reference signals" in
3GPP TS 36.211 V10.7.0.
• Symbols in an MBSFN subframe are grouped into a non-MBSFN region
and an MBSFN region. The non-MBSFN region may occupy one or two
symbol periods. The other symbol periods in the MBSFN subframe
belong to the MBSFN region.
• Symbols in the non-MBSFN region of an MBSFN subframe use the same
cyclic prefix (CP) length (normal CP in most cases) as the subframe 0 in
the radio frame does. These symbols are used to transmit the PDCCH
that carries the MCCH change notification. The notification informs UEs
that the MCCH will be updated in the next MCCH modification period.
The notification is transmitted on the PDCCH using the downlink control
information (DCI) format 1C and is identified using an MBMS - radio
network temporary identifier (M-RNTI).
• Symbols in the MBSFN region of an MBSFN subframe use extended CP.
These symbols are used to transmit the PMCH.

MBMS Notification Configuration
The MBSFN-AreaInfoList IE in SIB13 conveys the basic information about
MBSFN areas to which individual cells belong. As stipulated in 3GPP TS
36.331, a single cell can concurrently belong to a maximum of eight
MBSFN areas. Currently, Huawei's eMBMS allows each cell to be included
in a maximum of three MBSFN areas.
For TD-LTE SA2 Config,

Maximum only 4
Subframes can be use to
transmit MCCH

MBMS Notification Configuration (cont’d)
𝑀𝑀𝐶𝐻.𝑀𝑜𝑑𝑖𝑓.𝑃𝑒𝑟𝑖𝑜𝑑
SFN=
𝑛𝑜𝑡𝑖𝑓.𝑅𝑒𝑝𝑒𝑡𝑖𝑡𝑖𝑜𝑛.𝐶𝑜𝑒𝑓𝑓
512/2 = 256, so SFN is 256.
SFN Mod MCCH = SFN + Notif.Offset

262 = 256 + 6
SFN Mod MCCH(N) = SFN*(N)+Notif.Offset

•The MCCH modification period is 512 radio frames.
•The maximum number of MBSFN subframes per radio frame is 4. SFN Mod MCCH(2) = 256x2+6
•non-MBSFNregionLength is 1. = 512+6
•notificationRepetitionCoeff is 2. = 518
•notificationOffset is 6.
•notificationSF-Index is 1
From Above Sample, MMCH Modification will appear

on System Frame Number 262, 518, 774, 1030, etc

MBMS Notification Configuration (cont’d)
Radio Frame non MBSFN
0 1 2 3 4 5 6 7 8 9 Remarks
All Subframe use Normal
0 Downlink Channel
1 Special Subframe Cyclic Prefix with allocated
2 Uplink Channel subframe assignment
3
4
5
Radio Frame with MBSFN

0 1 2 3 4 5 6 7 8 9 Remarks
0 Downlink Channel
Subframe 0,1,2 and 5,6,7
1 Special Subframe use Normal Cyclyc Prefix
2 Uplink Channel (7 symbols/slot).
3 MTCH
4 MMCH
5
In PMCH use Extended
: : : : : : : : : : Cyclic (6 symbols/slot).
261
262 MCCH And based on previous
262
262
slide example, Control
262 channel MBMS will
262 appear each 256 System
262 Frame Number with
: : : : : : : : : :
517
Offset 6 SFN.
518 MCCH
519
520
521
522
523
: : : : : : : : : :

6.2 LTE DL CoMP
(Coordinated Multi Point)

Content
 DL CoMP Introduction
 LTE RRC Connection Setup Complete Evolution
 DL CoMP Application :
 Intra BBP
 Inter-eNodeB DL CoMP Based on Relaxed Backhaul
 Downlink Transmission by Multiple Cells
 Network Planning & Network Impact
 Related Counter

Related Concept
Concept Definition
Cluster A set of multiple cells, in which scheduling and pilot information sharing are implemented. A cluster contains all candidate coordinating cells
for CoMP UEs.
CoMP UE UEs that meet the requirements for CoMP in event A3 measurement reports.
Non-CoMP UE UEs other than CoMP UEs in a cell, including coordinating UEs and normal UEs. For a non-CoMP UE, its data is processed by only one cell.
Coordinating UE Non-CoMP UEs that share time and frequency resources with CoMP UEs in coordinating cells if CBF is used.
Normal UE Normal UEs refer to non-CoMP UEs when JT is implemented.
Normal UEs refer to UEs other than CoMP UEs and coordinating UEs in a coordinating cell when CBF is implemented.
Serving cell A cell that keeps connected to CoMP UEs through the physical downlink control channel (PDCCH). A CoMP UE can have only one serving cell at
a time.
Coordinating cell A set of cells in which CoMP UE channel information is measured and PDSCH data is transmitted directly or indirectly to CoMP UEs.
Coordinating cluster A set of cells that support JT or CBF for CoMP UEs, including the serving cell and coordinating cells.
Centralized control node The centralized control node is deployed on a UBBPd in a BBU and exchanges signaling and service data with the eNodeB. Inter-eNodeB DL
CoMP requires a centralized control node for each cluster.
Signaling data includes:
•User information: UE ID and cell ID, which are delivered by the serving cell to coordinating cells
•Scheduling information: priority-calculation parameters, CoMP UE information, pre-allocation information, and pairing information of CoMP
UEs. Priority-calculation parameters and CoMP UE information are collected and sent by cells to the centralized control node. Pre-allocation
information of CoMP UEs and power pattern indication are delivered from the centralized control node to each cell.
eX2 interface Interface for inter-eNodeB coordination

Mixed scheduling mode One type of coordinated scheduling working mode of baseband equipment. The baseband equipment working in this mode can
simultaneously perform baseband processing and centralized scheduling.
Dedicated scheduling One type of coordinated scheduling working mode of baseband equipment. The baseband equipment working in this mode can only perform
mode centralized scheduling.

Related Concept
Concept Definition
JT (Joint Transmission) multiple cells can transmit the same data concurrently by using the same radio resources (frequency and time). Because the same data is sent,
the speed would not double, but reception performance would be improved.
CBF (Coordinated Beam allocates different spatial resources (beam patterns) to UEs at cell edge by using smart antenna technology.
Forming)
DCS (Dynamic The basic idea of DCS is pretty similar to ICIC in that it reduces inter-cell interference by allocating different frequency resources (RBs or sub-
Coordinated Scheduling) carriers) to cell-edge UEs. But from technical perspective, DCS is a more advanced technology that requires a much shorter operation period,
more complicated signal processing and more elaborate algorithm, compared to ICIC. In ICIC, cooperating cells share interference information
of each cell, but in DCS they can share channel information of each user.

eX2 Interface
Similar to the X2 interface, the eX2 interface is a logical interface between eNodeBs. The difference is that the eX2 interface handles only inter-
eNodeB service coordination. X2 and eX2 interfaces can coexist.
eX2 self-management is a process that the eNodeB automatically configures and removes eX2 interfaces according to external or internal
factors. External factors include end-point configuration changes or the situation where an eNodeB initiates service coordination to other
eNodeBs. Internal factors include transmission link aging.
Inter-eNodeB service coordination features include:

• Inter-eNodeB carrier aggregation (CA)
• Inter-eNodeB DL CoMP

DL CoMP Introduction

DL CoMP - Introduction
CoMP was Introduce in LTE Release 11.

The LTE system mainly adopts intra-frequency networking to improve spectral efficiency. However, DL CoMP provides the following benefits:
in this networking mode, cell edge users (CEUs) receive co-channel interference from neighboring
cells. Operators expect to mitigate inter-cell interference and improve CEU throughput. • Increases the downlink throughput of cell edge users (CEUs)
DL CoMP is introduced as PDSCH co-channel interference control technology. DL CoMP increases without decreasing the average cell throughput.
wanted signal power and reduce inter-cell interference, thereby increasing the throughput of CEUs • Increases the handover success rate.
• Reduces the probability of downlink throughput decrease in
handovers

DL CoMP - Introduction
DL CoMP is a coordinated multi-point downlink transmission technology, which enables eNodeBs to use antennas in neighboring cells to
process and transmit PDSCH data of a specific UE by means of joint transmission (JT), coordinated beamforming (CBF), and dynamic
cell selection (DCS). This technology increases wanted signal power and mitigates inter-cell interference. eNodeB can adaptively adopt
an appropriate transmission mode based on the cell load and channel quality.
DL CoMP is classified based on the coordinated transmission scope and transmission bandwidth consumption, as described in
below Table. Intra-BBP DL CoMP reduces co-channel interference from an intra-eNodeB cell. Inter-eNodeB DL CoMP reduces co-
channel interference from an inter-eNodeB cell or both inter- and intra-eNodeB cells.
Table 2-1 DL CoMP application classification
DL CoMP Application Type Transmission Mode Related Feature

Intra-BBP DL CoMP DCS TDLAOFD-001001 LTE-A Introduction
•TDLAOFD-00100103 Intra-eNodeB DL CoMP in DCS Mode
Adaptive (The eNodeB adaptively selects DCS, CBF, or JT.) TDLAOFD-003002 Intra-eNodeB DL CoMP in Adaptive Mode
•TDLAOFD-00300201 Coordinated Beamforming
•TDLAOFD-00300202 Single-User Joint Transmission
•TDLAOFD-00300204 Adaptive Transmission Mode Switching
Inter-eNodeB DL CoMP based on relaxed •DCS TDLAOFD-081411 Inter-eNodeB DL CoMP Based on Relaxed
backhaul (either intra-BBU inter-BBP or •Adaptive (The eNodeB adaptively selects DCS or CBF.) Backhaul
inter-BBU)

LTE category (36.306)

DL CoMP Evolution
Item eRAN TDD 7.0 and eRAN TDD eRAN TDD 8.1
8.0
Transmission •Intra-BBP transmission in DCS •Intra-BBP transmission in DCS mode
mode mode •Intra-BBP adaptive switching among
•Intra-BBP adaptive switching DCS, CBF, and JT modes
among DCS, CBF, and JT •Intra-BBP adaptive switching among
modes DCS, CBF, and JT modes
•Inter-eNodeB adaptive CoMP and
intra-BBP adaptive CoMP
Networking •Supports intra-frequency •Supports intra-frequency networks
networks consisting of macro consisting of macro eNodeBs.
eNodeBs. •Supports coordination among three
•Supports coordination among intra-BBP cells.
three intra-BBP cells. •Supports coordination in inter-
•SFN cells and multi-RRU eNodeB cells.
combination cells cannot be •SFN cells cannot be added to an
added to an intra-eNodeB DL intra-eNodeB DL CoMP cluster.
CoMP cluster. •Multi-RRU combination cells can be
added to an inter-eNodeB DL CoMP
cluster.

RRC DL CoMP
25

RRC DL CoMP
26

RRC DL CoMP
27

Channel Information in CoMP
Channels are transmission routes for data, i.e. between Tx antenna and Rx antenna across air. If base stations know
UE's channel information beforehand, they can transmit precoded data so that UE can get better reception. For this
purpose, UEs measure their channels, and report the resulting Channel State Information (CSI) to their base stations.
Base stations give their UEs an instruction on how and which cell's CSI are to be measured by sending a CSI-RS (CSI
Reference Signal) configuration message. Upon this instruction, UEs measure CSI and report to their serving cells. In
general, CSI information includes Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), and Rank Indicator
(RI).
CQI: An indicator of channel quality. Displayed as a highest modulation and coding rate (MCR) value that satisfies the condition of 'channel block error rate
(BLER) < 0.1'. It is set as a value ranging 0 ~ 15 (4 bits). The better channel quality, the higher MCR is used. Subband CQIs indicate the quality for specific
frequency ranges (subrange) while wideband CQIs indicate that for the entire channel bandwidth.
PMI: Base stations deliver more than one data stream (layer) through Tx antenna. Precoding matrix shows how individual data streams (layers) are
mapped to antennas. To calculate precoding matrix, UEs obtain channel information by measuring the channel quality of each DL antenna. Because
providing feedback on all channel information results in significantly increased overheads, generally a code book is pre-configured at base stations and
UEs. Using this code book, UEs send the index of a corresponding precoding matrix only. Base stations, by referring the reported precoding matrix,
calculate its own precoding matrix, and use the optimal value from it.
RI: Indicates the number of data stream(s) being delivered in DL. For instance, with 2 X 2 MIMO, this value is 1 in case of transmit diversity MIMO where
two antennas at a base station are sending the same data stream, and it is 2 in case of spatial multiplexing MIMO where the antennas are sending different
data streams.
28

DL CoMP Application
Intra BBP

License Required

Enabling of DL CoMP
MOD CELLALGOSWITCH
31

Intra-BBP DL CoMP
Intra-BBP CoMP corresponds to TDLAOFD-00100103 Intra-eNodeB DL CoMP in DCS

Mode and TDLAOFD-003002 Intra-eNodeB DL CoMP in Adaptive Mode. Intra-BBP
CoMP requires that cells for DL CoMP be configured on the same BBP.
The coordinating cell has the following requirements for the number of antennas:
•JT requires that CoMP UEs support beamforming, and beamforming requires that
cells work in 4T4R or 8T8R mode. Therefore, the serving cell and coordinating cell of a
JT UE must have four or eight TX antennas.
•The coordinating UE of a CBF UE must be a single-stream or dual-stream
beamforming UE. The coordinating cell of a CBF UE must have four or eight TX
antennas.
•The serving cell and coordinating cell of a DCS UE must have two, four, or eight TX
antennas.

Intra-BBP DL CoMP
The following details the basic procedure for DL CoMP:
1.Enabling of DL CoMP
1. Select the IntraDlCompSwitch(IntraDlCompSwitch) check box under
the CellAlgoSwitch.DlCompSwitch parameter.
2. Set the CELLDLCOMPALGO.DlCompA3Offset parameter. It is recommended that this
parameter be set to -12.
2.Selection of a CoMP UE and its coordinating cellsIn intra-BBP DL CoMP, the eNodeB selects a CoMP UE
and its coordinating cell based on the event A3 measurement reports from UEs, reference signal received
power (RSRP) difference between the serving and neighboring cells, and RSRP in the neighboring cell. Then,
the eNodeB notifies the physical layer of the selected UE and cell.
3.Transmission by multiple cellsBased on the information about the CoMP UE, serving cell, and coordinating
cell, the physical layer processes and transmits PDSCH data of the CoMP UE on the antennas of the serving
cell and coordinating cell, by performing JT, CBF, and/or DCS.

DL CoMP Application
Inter- eNodeB DL CoMP Based on Relaxed Backhaul
eRAN 8.1

License Required

Enabling of DL CoMP
MOD CELLALGOSWITCH

Enabling of DL CoMP (eRAN 8.1)
MO CellAlgoSwitch
Parameter ID DlCompSwitch
Parameter Name Downlink CoMP algorithms switch
NE BTS3900, BTS3900 LTE
MML Command MOD CELLALGOSWITCH
LST CELLALGOSWITCH
Meaning Indicates the switch used to enable or disable the DL CoMP algorithm.
IsKey NO
Mandatory NO
Dynamic Attribute NO
Feature ID TDLAOFD-081411
Feature Name Inter-eNodeB DL CoMP based on Relaxed backhaul
Value Type Bit Field Type
GUI Value Range IntraDlCompSwitch(IntraDlCompSwitch), InterDlCompDcsSwitch(InterDlCompDcsSwitch), InterDlCompCbfSwitch(InterDlCompCbfSwitch)
Enumeration Number/Bit IntraDlCompSwitch~0, InterDlCompDcsSwitch~1, InterDlCompCbfSwitch~2
Unit None
Actual Value Range IntraDlCompSwitch, InterDlCompDcsSwitch, InterDlCompCbfSwitch
Default Value IntraDlCompSwitch:Off, InterDlCompDcsSwitch:Off, InterDlCompCbfSwitch:Off
Recommended Value DlCompSwitch:Off
Initial Value Setting Source Engineering Design
Impact CellAlgoSwitch
Parameter Relationship If the InterDlCompCbfSwitch check box under the DlCompSwitch parameter is selected, the InterDlCompDcsSwitch check box cannot be cleared.
Access Read & Write

Service Interrupted After Modification No (And no impact on the UE in idle mode)
Interruption Scope N/A

Interruption Duration (min) N/A
Caution None
Validation of Modification The parameter modification has no impact on the equipment.
Impact on Radio Network Performance If the IntraDlCompSwitch check box is selected, the throughput of edge UEs in intra-eNodeB cells increases but the average throughput of a cell may decrease.
If the InterDlCompDcsSwitch or InterDlCompCbfSwitch check box is selected, the throughput of edge UEs in inter-eNodeB cells in a cluster increases but the average throughput of a cell may
decrease.
If DL CoMP is disabled, the throughput of CEUs decreases due to co-channel interference.
Introduced in Version... BTS3900: V100R008C00

BTS3900 LTE: V100R008C00

Inter- eNodeB DL CoMP Based on
Relaxed Backhaul (eRAN 8.1)
Inter-eNodeB DL CoMP based on relaxed backhaul corresponds to TDLAOFD-081411 Inter-eNodeB DL CoMP Based on Relaxed Backhaul. Inter-eNodeB DL CoMP based on
relaxed backhaul requires that cells for DL CoMP be configured on different BBPs in the same BBU or different BBUs.
Intra-BBU inter-BBP DL CoMP
Inter-BBU inter-BBP DL CoMP
In inter-eNodeB DL CoMP based on relaxed backhaul, BBUs are interconnected using the existing IP
RAN or PTN. Coordination data is transmitted between eNodeBs over the eX2 interface. The eX2
interface shares the transport network with the X2 interface. Therefore, inter-eNodeB DL CoMP based
on relaxed backhaul must consider eX2 transmission bandwidth and transmission delay from
coordinating cells to eNodeBs

Inter- eNodeB DL CoMP Based on
Relaxed Backhaul (eRAN 8.1)
The following details the basic procedure for DL CoMP.
1.Planning of the centralized control node and configuration of the cluster
• Plan the centralized control node.You need to deploy a centralized control node for each cluster to enable transmission of signaling
messages and service data between the eNodeB and centralized control node.
• The centralized control node must be deployed on the UBBPd.
• The BBP on which the centralized control node is deployed can be specified by configuring
the BASEBANDEQM and EuCoSchCfg MOs.
• Add a cluster and cluster cell information.You can set the CLUSTER and CLUSTERCELL MOs to manage backup inter-eNodeB
DL CoMP coordinating cells.
• Configure parameters related to inter-eNodeB DL CoMP.You can determine the value of
the EuCoSchDLCoMPCfg.CordInfoEffDelay parameter based on the transmission delay, which indicates the delay between the
time when the eNodeB reports measurement information and the time when the coordination information received from the
centralized control node takes effect.
• You can set the EuCoSchDLCoMPCfg.InterEnbDlCompSwitch parameter to ON(On) to enable inter-eNodeB DL CoMP.
2.Enabling of DL CoMP
• Set the CellAlgoSwitch.DlCompSwitch parameter as described in Table 4-1.Table 4-1 Mapping between the transmission modes
and parameter settings
Transmission Mode Setting of the CellAlgoSwitch.DlCompSwitch Parameter

Inter-eNodeB DCS Select the InterDlCompDcsSwitch(InterDlCompDcsSwitch) check box.
Inter-eNodeB adaptive DL CoMP Select both
the InterDlCompDcsSwitch(InterDlCompDcsSwitch) andInterDlCompCbfSwitch(InterDlCom
pCbfSwitch) check boxes.
• Set the CELLDLCOMPALGO.DlCompA3Offset parameter. It is recommended that this parameter be set to -12.
3. Selection of CoMP UEs and coordinating cells
• The eNodeB selects CoMP UEs based on the event A3 measurement results reported by UEs, RSRP difference between the serving and
neighboring cells, and RSRP in the neighboring cell.
• The centralized control node calculates the power pattern based on the RSRPs of the serving cell and interference neighboring cells reported by
UEs in each cluster and the load information. When the power pattern P in the neighboring cell of a CoMP UE equals 0, the cell can be selected
as the coordinating cell. When P equals 0, the neighboring cells are silent. At this time, the PDSCH does not transmit data.
4.Transmission by multiple cellsBased on the information about the CoMP UE, serving cell, and coordinating cell, the physical layer processes and transmits
PDSCH data of the CoMP UE on the antennas of the serving cell and coordinating cell, by performing JT, CBF, and/or DCS.

Selection of CoMP UEs and
Coordinating Cells
LST CELLDLCOMPALGO
RSRP N – RSRP S > - 6

-93 – (- 90) = - 3
So -3 dB are greater than -6 dB which is
Cell 1 meet with the criteria to perform DL CoMP
-90 dBm
- 93 dBm
- 97 dBm
Cell 2 -6 dB
Serving
Cell 3 Serving Listed Listed
Neighbor After selecting CoMP UEs, the eNodeB determines the coordinating cell
as follows:
a) Based on event A3 measurement report, the eNodeB selects a
The eNodeB first determines UEs that require and apply to multi-cell maximum of two neighboring cells whose RSRP values meet the
joint processing as follows: requirement specified by
a) When the value of RSRP in the neighboring cell minus RSRP in the the CellDlCompAlgo.DlCoMPA3Offsetparameter and are the largest.
serving cell is greater than the DL CoMP event A3 offset b) CoMP UEs apply for SRS resource reconfiguration on the reserved
(recommended value: –12), the UE reports event A3. SRS resources of the cells selected in .a.
b) The eNodeB selects a UE as the CoMP UE when both of the c) After the SRS resource reconfiguration application succeeds, CoMP
following conditions are met:The RSRP difference between the UEs request that the serving cell sends an RRC reconfiguration
serving and neighboring cells is greater than the event A3 offset message to reconfigure SRS resources for CoMP UEs. For intra-BBP
required by DL CoMP. DL CoMP, a neighboring cell with SRS resources reconfigured
The CQI reported by the UE is smaller than the threshold. successfully is selected as the coordinating cell. For inter-eNodeB DL
CoMP, a neighboring cell with SRS resources reconfigured
c) The eNodeB determines whether CoMP UEs are JT UEs, CBF UEs, successfully and the power pattern P equal to 0 is selected as the
or DCS UEs. JT UEs must be beamforming UEs coordinating cell.

Downlink Transmission by Multiple Cells

Joint Transmission (JT)
In JT mode, all cells in a coordinating cluster transmit PDSCH data to CEUs to obtain power gains and array gains. In JT
implementation, CoMP UEs must support beamforming.
•Cell 2 obtains the weight of UE 1 based on the SRS measurement results. Cell 1 and cell 2 use the same RB resources to simultaneously transmit the
weighted PDSCH data to UE 1.
•UE 1 receives the same PDSCH data from cell 1 and cell 2 simultaneously.

Coordinated Beam Forming (CBF)
UE 1 is paired with UE 2 in cell 2. With CBF

processing, con-channel interference from
cell 2 to UE 1 decreases.
CBF coordinates the beam direction of UEs in intra-frequency neighboring cells so that UEs close to the cell center help CEUs in neighboring
cells to avoid beam interference. In this way, the spectral efficiency of CEUs is improved, and the average cell throughput is not obviously
affected. In CBF implementation, coordinating UEs must support beamforming.
The characteristics of normal beamforming and CBF are as follows:
• In normal beamforming mode, each cell independently processes PDSCH data and calculates the optimal weight based on its performance regardless of other cells.
Therefore, interference may be strong to UEs allocated the same time and frequency resources in different cells.
• In CBF mode, the eNodeB preferentially selects coordinating UEs with the transmission mode of TM7, TM8, or TM9 without PMI and calculates the channel
correlation between coordinating UEs and CoMP UEs. Then, UEs whose channel correlation meets requirement are paired and the weights of coordinating UEs are
adjusted to be orthogonal. Therefore, interference to CoMP UEs decreases.

Dynamic Coordinated Scheduling (DCS)
the eNodeB serving cell 1 transmits processed

PDSCH data to UE 1, but the eNodeB serving cell
2 does not schedule data on the same RB.
Therefore, UE 1 only receives PDSCH data from
cell 1, reducing interference from cell 2 to cell 1
In the case of RBs interfered with by intra-frequency neighboring cells, DCS does not schedule data of other UEs to achieve three purposes: (1)
decrease co-channel interference to CoMP UEs; (2) improve interference suppression performance of CEUs; (3) increase the spectral efficiency
of CEUs.

Network Planning & Network Impact

General Requirement
•Before deploying DL CoMP, ensure that the live network meets the following
requirements:DBS3900 is used to provide contiguous intra-frequency coverage.
•All cells work at the same bandwidth other than 5 MHz.
•All the cells use the same frequency, uplink-downlink subframe configuration, and special
subframe configuration.
•Neighbor relationships have been configured.

In addition to these general requirements, the following describes the specific planning
requirements for DL CoMP deployment.

Planning for Inter-eNodeB DL CoMP Based
on Relaxed Backhaul
1. Plan the cluster.

Principles:
• The cells on the same BBP must be configured in the same cluster.
• The cells in the same cluster provide contiguous coverage.
• A maximum of 36 cells can be configured in each cluster under the same centralized control node. The number of cells in a
cluster depends on the transmission bandwidth reserved by the eNodeB for CoMP information transmission, which is about
2.5 Mbit/s.For example, if the transmission bandwidth reserved for inter-eNodeB DL CoMP is 15 Mbit/s, each cluster under
a centralized control node can include a maximum of nine cells. Three of them are established on the BBP on which the
centralized control node is deployed and do not occupy transmission bandwidth resources.
• 15 Mbit/s/2.5 Mbit/s + 3 = 9
Methods:
• Select the hotspot area. Select an area in which the cell load in busy hours exceeds the recommended value 10%.
• Determine cells in the cluster.a. Analyze engineering parameters in the hotspot area using network planning tools and
check the cell locations in the hotspot area. Plan the cells that are geographically near each other in a cluster.
• b. Measure the transmission delay from cells to the centralized control node. Cells of which the transmission delay is
shorter than or equal to 2 ms are added to the cluster.
2. Plan the centralized control node based on the following principles:
• Preferentially select eNodeBs and BBPs with light service load.
• Preferentially select eNodeBs with large eX2 transmission bandwidth.
• Preferentially select eNodeBs to which the transmission delays from coordinating cells are balanced and shorter than or equal to 2 ms.
• Multiple clusters can be configured under the same centralized control node.
3. Plan the transmission bandwidth between eNodeBs in a cluster.

After eNodeBs in a cluster are determined, an additional bandwidth of 15 Mbit/s is added when calculating transmission bandwidth
between eNodeBs to ensure that inter-eNodeB DL CoMP takes effect. For example, if there are three eNodeBs (eNodeB 1, eNodeB 2, and
eNodeB 3) in a cluster, an additional bandwidth of 15 Mbit/s must be added to the transmission bandwidths between eNodeB 1 and
eNodeB 2, between eNodeB 1 and eNodeB 3, and between eNodeB 2 and eNodeB 3.

Transmission eX2 Bandwidth
There is 15 Mbps
should be reserved as
the capacity of
transmission between
eNB for DL CoMP
Gbps
4

MML Command
Intra-BBP DL CoMP (for Three Cells)
//Enabling DL CoMP for cell 0, cell 1, and cell 2

MOD CELLALGOSWITCH:LocalCellId=0,DlCompSwitch=IntraDlCompSwitch-1,HarqAlgoSwitch=TddAckFbModeCfgOptSwitch-1, DLSCHSWITCH=TailPackagePriSchSwitch-1;
//Setting DL CoMP event A3 offset for cell 0, cell 1, and cell 2

MOD CELLDLCOMPALGO:LocalCellId=0,DlCompA3Offset=-12;
TailPackagePriSchSwitch: Indicates the switch that controls the scheduling of downlink connected tail packages in the bearer. If this switch is turned on, the
connected tail package is scheduled preferentially in the next TTI, which reduces the delay and increases the transmission rate. If this switch is turned off, the
scheduling strategy of the connected tail package is the same as other downlink subframes. This switch is dedicated to LTE TDD cells.

MML Command
Inter-eNodeB DL CoMP (for Three Cells Under Three eNodeBs)
The following commands are required only for the eNodeB in which the BBP is configured as the centralized control node.
//Adding baseband equipment
ADD BASEBANDEQM:BASEBANDEQMID=2,BASEBANDEQMTYPE=ULDL,UMTSDEMMODE=NULL,SN1=2;
//Deploying a centralized control node on the specified baseband equipment
MOD EUCOSCHCFG:PRTNODEBASEBANDEQMID=2,WORKMODE=COORDINATED_SCHEDULING_ONLY;
//Adding a cluster
ADD CLUSTER:ClusterId=2;
//Adding a cell to the cluster
ADD CLUSTERCELL:ClusterId=2,Mcc="460",Mnc="01",eNodeBId=32,CellId=1;
//Configuring the inter-eNodeB DL CoMP information effective delay and turning on the inter-eNodeB DL CoMP algorithm switch
MOD EUCOSCHDLCOMPCFG:CORDINFOEFFDELAY=7,INTERENBDLCOMPSWITCH=ON;
The following commands need to be executed for each eNodeB.

//(Optional) Configuring the eX2 interface
For details, see ex2 Self-Management Feature Parameter Description.
//Setting the DL CoMP event A3 offset
//Setting the CSPC CQI filter coefficient
MOD CELLCSPCPARA:LOCALCELLID=1,CSPCCQIFILTERCOEFF=25;
//Enabling DL CoMP
MOD CELLALGOSWITCH:LocalCellId=1,DlCompSwitch=IntraDlCompSwitch-1&InterDlCompCbfSwitch-1&InterDlCompDcsSwitch-1,HarqAlgoSwitch=TddAckFbModeCfgOptSwitch-
1,DLSCHSWITCH=TailPackagePriSchSwitch-1;
TailPackagePriSchSwitch: Indicates the switch that controls the scheduling of downlink connected tail packages in the bearer. If this switch is turned on, the
connected tail package is scheduled preferentially in the next TTI, which reduces the delay and increases the transmission rate. If this switch is turned off, the
scheduling strategy of the connected tail package is the same as other downlink subframes. This switch is dedicated to LTE TDD cells.

System Capacity
Increases the downlink throughput of cell edge users (CEUs) without decreasing the average cell
throughput.
When there is only one CoMP UE in the serving cell, the MCS order in the non-beneficial subframes of
CoMP UEs decreases. However, the expected downlink throughput gains for CEUs can still be achieved
Network Performance
• DL CoMP increases the handover success rate and reduces downlink throughput decreases during
handovers.After DL CoMP is enabled, MCS orders of CEUs increase, which improves the edge
coverage, increases the handover success rate of CEUs, and reduces the possibility that CEU
throughput decreases during handovers.
• DL CoMP has a negative impact on the scheduling fairness of CEUs.The scheduling priority of CEUs
decreases because the average CEU throughput increases.

Related Counter

Counters
Counter ID Counter Name Counter Description Feature ID Feature Name 1526729065 L.Thrp.DL.BitRate.Samp.Index9 Number of samples with the Multi-mode: None Radio Bearer Management
downlink throughput ranging GSM: None Radio Bearer Management
1526727444 L.ChMeas.PDSCH.MCS.0 Number of times MCS Multi-mode: None Basic Scheduling within index 9 UMTS: None Basic Scheduling
LTE: LBFD-002008 Basic Scheduling
index 0 is scheduled on GSM: None Modulation: DL/UL QPSK, TDLBFD-002008
the PDSCH UMTS: None DL/UL 16QAM, DL LBFD-002025
LTE: LBFD-002025 64QAM TDLBFD-002025
LBFD-001005 Basic Scheduling 1526729463 L.ChMeas.PRB.DL.DLComp.Used.A Average number of PRBs used by Multi-mode: None Intra-eNodeB DL CoMP in DCS
TDLBFD-002025 Modulation: DL/UL QPSK, vg downlink CoMP UEs in a cell GSM: None Mode
TDLBFD-001005 DL/UL 16QAM, DL UMTS: None Intra-eNodeB DL CoMP in Adaptive
64QAM LTE: TDLAOFD-00100103 Mode
TDLAOFD-003002
1526727475 L.ChMeas.PDSCH.MCS.31 Number of times MCS Multi-mode: None Basic Scheduling
index 31 is scheduled on GSM: None Modulation: DL/UL QPSK, 1526729464 L.Traffic.User.DLComp.Avg Average number of downlink Multi-mode: None Intra-eNodeB DL CoMP in DCS
the PDSCH UMTS: None DL/UL 16QAM, DL CoMP UEs in a cell GSM: None Mode
LTE: LBFD-002025 64QAM UMTS: None Intra-eNodeB DL CoMP in Adaptive
LBFD-001005 Basic Scheduling LTE: TDLAOFD-00100103 Mode
TDLBFD-002025 Modulation: DL/UL QPSK, TDLAOFD-003002
TDLBFD-001005 DL/UL 16QAM, DL
1526729465 L.Traffic.User.DLComp.Max Maximum number of downlink Multi-mode: None Intra-eNodeB DL CoMP in DCS
64QAM CoMP UEs in a cell GSM: None Mode
1526728261 L.Thrp.bits.DL Total downlink traffic Multi-mode: None Radio Bearer UMTS: None Intra-eNodeB DL CoMP in Adaptive
volume for PDCP SDUs in GSM: None Management LTE: TDLAOFD-00100103 Mode
a cell UMTS: None Radio Bearer TDLAOFD-003002
LTE: LBFD-002008 Management
1526737752 L.Traffic.User.InterEnbDLComp.Avg Average number of DL CoMP UEs Multi-mode: None Intra-eNodeB DL CoMP in DCS
TDLBFD-002008 Basic Scheduling in a cell GSM: None Mode
LBFD-002025 Basic Scheduling UMTS: None Intra-eNodeB DL CoMP in Adaptive
TDLBFD-002025 LTE: TDLAOFD-00100103 Mode
TDLAOFD-003002
1526729005 L.Thrp.bits.DL.LastTTI Downlink traffic volume Multi-mode: None Radio Bearer
sent in the last TTI for GSM: None Management
1526737753 L.ChMeas.PRB.InterEnbDLComp.Us Average number of PRBs used for Multi-mode: None Intra-eNodeB DL CoMP in DCS
PDCP SDUs before the UMTS: None Radio Bearer ed.Avg inter-eNodeB DL CoMP scheduling GSM: None Mode
buffer is empty LTE: LBFD-002008 Management in a cell UMTS: None Intra-eNodeB DL CoMP in Adaptive
TDLBFD-002008 Basic Scheduling LTE: TDLAOFD-00100103 Mode
LBFD-002025 Basic Scheduling TDLAOFD-003002
TDLBFD-002025
1526737755 L.Thrp.bits.DL.BorderUE Downlink PDCP-layer traffic Multi-mode: None Basic Scheduling
1526729015 L.Thrp.Time.DL.RmvLastT Data transmit duration Multi-mode: None Radio Bearer volume sent for CEUs in a cell GSM: None Basic Scheduling
TI except the last TTI before GSM: None Management UMTS: None
the downlink buffer is UMTS: None Radio Bearer LTE: LBFD-002025
empty LTE: LBFD-002008 Management TDLBFD-002025
TDLBFD-002008 Basic Scheduling 1526737758 L.Thrp.bits.DL.LastTTI.BorderUE Downlink PDCP-layer traffic Multi-mode: None Basic Scheduling
LBFD-002025 Basic Scheduling volume sent in the last TTI for CEUs GSM: None Basic Scheduling
TDLBFD-002025 before the buffer is empty in a cell UMTS: None
LTE: LBFD-002025
1526729056 L.Thrp.DL.BitRate.Samp.I Number of samples with Multi-mode: None Radio Bearer TDLBFD-002025
ndex0 the downlink throughput GSM: None Management
ranging within index 0 UMTS: None Radio Bearer
LTE: LBFD-002008 Management
TDLBFD-002008 Basic Scheduling
LBFD-002025 Basic Scheduling
TDLBFD-002025
53

Counters
1526737759 L.Thrp.Time.DL.RmvL Data transmission Multi-mode: None Basic Scheduling

astTTI.BorderUE duration for CEUs GSM: None Basic Scheduling
except the last TTI UMTS: None
before the downlink LTE: LBFD-002025
buffer is empty TDLBFD-002025
1526737775 L.E- Number of normal E- Multi-mode: None Intra-Band Carrier
RAB.NormRel.Relaxe RAB releases for UEs GSM: None Aggregation for
dBackhaulCAUser in the downlink UMTS: None Downlink 2CC in
relaxed-backhaul- LTE: LAOFD-00100101 20MHz
based CA state LAOFD-00100102 Inter-Band Carrier
LAOFD-070201 Aggregation for
LAOFD-070202 Downlink 2CC in
LAOFD-080202 20MHz
LAOFD-080207 Flexible CA from
LAOFD-080208 Multiple Carriers
TDLAOFD-00100111 Inter-eNodeB CA
TDLAOFD-001002 based on
TDLAOFD-00100102 Coordinated BBU
TDLAOFD-081411 Carrier Aggregation
TDLAOFD-070201 for Uplink 2CC
Carrier Aggregation
for Downlink 3CC in
40MHz
Carrier Aggregation
for Downlink 3CC in
60MHz
Intra-band Carrier
Aggregation for
Downlink 2CC in
30MHz
Carrier Aggregation
for Downlink 2CC in
40MHz
Support for UE
Category 6
Inter-eNodeB DL
CoMP based on
Relaxed backhaul
Flexible CA from
Multiple Carriers

6.3 LTE Carrier Aggregation eRAN 8.0

Content
 Carrier Aggregation Introduction
 Carrier Aggregation Setting on U2000:
 Carrier Aggregation Sample Trial
 CA with Default Configuration
 CA with PCC Anchoring
 CA with PCC Anchoring & HOwithSCCCfg
 Carrier Aggregation DL Throughput Comparison
 Carrier Aggregation Counter Measurement
 Carrier Aggregation Parameter Optimization

Abbreviations
PCell
A primary serving cell (PCell) is the cell on which a CA UE camps. In the PCell, the CA UE works in the same way as it does in
a 3GPP Release 8 or Release 9 cell. The physical uplink control channel (PUCCH) of the UE exists only in the PCell.
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.
57

Related Event
Event A2
Event A2 indicates that the signal quality of the serving cell becomes lower than a specific threshold.
Event A3
Event A3 indicates that the signal quality of the PCell's neighboring cell becomes higher than that of the Pcell.
Event A4
Event A4 indicates that the signal quality of a neighboring cell becomes higher than a specific threshold.
Event A5
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 threshold.
Event A6
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. The following explains the variables involved:Mn is
the RSRP measurement result of a neighboring cell.
Ocn is the cell-specific offset for an intra-frequency neighboring cell. The offset is specified by
the EutranIntraFreqNCell.CellIndividualOffset parameter.
Hys is the hysteresis for event A6. The value of this variable is always 0.
Ms is the RSRP measurement result of the serving cell.
Ocs is the cell-specific offset for the serving cell. The offset is specified by the Cell.CellSpecificOffset parameter.
Off is the offset for event A6. The offset is specified by the CaMgtCfg.CarrAggrA6Offset parameter.

Carrier Aggregation Introduction

Carrier Aggregation- Introduction
Based on the frequency bands of component carriers (CCs), CA is

classified as follows:
3GPP requires LTE-Advanced networks to provide a downlink peak data rate of 1 Gbps However,
1) Intra-band CA
radio spectrum resources are scarce, and many operators own only non-contiguous
Intra-band CA aggregates two carriers in the same frequency band
spectrums. Due to limited contiguous bandwidth on the spectrum, the 1 Gbps data rate
for downlink
requirement is hard to meet.
transmission to a UE. It is further classified into contiguous CA
To deal with this situation, 3GPP TR 36.913 Release 10 introduced CA to aggregate contiguous
or non-contiguous carriers in LTE-Advanced networks. CA achieves wider bandwidths (to a
2) Inter-band CA
maximum of 100 MHz) and higher spectral efficiency of non-contiguous spectrums.
Inter-band CA aggregates two carriers in different frequency bands
for downlink
transmission to a UE

Carrier Aggregation – HUAWEI Limitation
Scenario 1 Scenario 3
Scenario 2
Scenario 4
Scenario 5

Carrier Aggregation – Radio Protocol Stack

Carrier Aggregation Signaling Flow
(UE Capability Information)

(UE Capability Information)
UE Cat 6

(RRC Connection Reconfiguration)

(RRC Connection Reconfiguration)
PCell : 39475
SCell : 39325

Carrier Aggregation Establishment - 2CC
(1) is the command (RRC message) to tell the UE to configure the Radio Stack
(PHY, MAC) to establish the aggregated communication (Carrier
Aggregration). You need to look into every details of RRC Connection
Configuration message to fully understand this step.
(2) is the HARQ ACK from UE saying 'I got a PDSCH (carrying RRC Connection
Reconfiguration).
(3) is the step where both UE and Network performs the necessary setup for
Carrier Aggregation.
(4) is the step where UE send SR saying 'I need a physical resource to send some
data (PUSCH carrying RRC Connection Reconfiguration Complete message in
this case)'.
(5) is the step where Network allocate resource in response to step (4).
(6) is the step where UE reporting to network 'I am done with the setup and the
setup is successful'. At this step, the setup has been established only at RRC
layer and MAC layer for the second carrier is not yet activated.
(7) is the step where Network send a command to UE saying 'Now activate MAC
layer for the second carrier as well'.
(8) indicate the status where MAC/PHY for both carrier are fully activated.

Carrier Aggregation Setting on U2000

License Required

How to Configure CA 2CC Scenario 1
LST CELL
F1
F2
1) There should be have two different carrier on co-sector.
(F1 to F2) LST EUTRANINTERFREQNCELL (F2 to F1)
2) Each carrier should have Interfreq NRT (F1<>F2).

3) Change No Remove Indicator, to prevent ANR delete
relationship between carrier.

Local
Sect ID EARFCN Local Cell
EARFCN F1 Cell ID CAGROUP Identity
F2 ID F2
F1
1-Alpha 39475 0 39325 9 0
1-Beta 39475 1 39325 10 1
3) Create CA GROUP Identity as reference ID of this two cell’s 1-Gamma 39475 2 39325 11 2
as on unity
2-Alpha 39475 3 39325 12 3
LST CAGROUP
2-Beta 39475 4 39325 13 4
2-Gamma 39475 5 39325 14 5
3-Alpha 39475 6 39325 15 6
3-Beta 39475 7 39325 16 7
3-Gamma 39475 8 39325 17 8
Alpha Alpha Alpha

Note: CA Group ID follow Local Cell
ID of first carrier, in order to easy
for audit in the future and not
1 2 confuse to determine which ID are
3
Gamma Beta Gamma Beta Gamma Beta available or not.

Creating CAGROUP
Chose TDD Same Subframe

Chose TDD
Alignment Configuration
CA GROUP Id chose from

first carrier Local CID

Local
Sect ID EARFCN Local Cell
EARFCN F1 Cell ID CAGROUP Identity
F2 ID F2
F1
1-Alpha 39475 0 39325 9 0
1-Beta 39475 1 39325 10 1
4) After get CAGROUP ID, now bonding this two cells into one 1-Gamma 39475 2 39325 11 2
CAGROUPCELL
2-Alpha 39475 3 39325 12 3
LST CAGROUPCELL
2-Beta 39475 4 39325 13 4
2-Gamma 39475 5 39325 14 5
3-Alpha 39475 6 39325 15 6
3-Beta 39475 7 39325 16 7
3-Gamma 39475 8 39325 17 8
Alpha Alpha Alpha

Note: CA Group ID follow Local Cell
ID of first carrier, in order to easy
for audit in the future and not
1 2 confuse to determine which ID are
3
Gamma Beta Gamma Beta Gamma Beta available or not.

Creating CAGROUPCELL
Local CID of 1st & 2nd Carrier

eNB ID of cell that we want
should be register in the same
to Bonding
CA GROUP ID
CA GROUP Id that we have

creating before on the
same Sector

Overall CA Procedure
1. Configuration of CA groups and CA-related parameters. A CA group is

a set of cells that
can be carrier-aggregated for a CA UE.
2. Initial RRC connection setup for a CA UE in a cell, that is, in the

primary serving cell
(PCell). The PCell is the cell on which the UE camps.
3. Secondary serving cell (SCell) configuration. If blind SCell

configuration is disabled, the
eNodeB delivers A4 measurement configurations to the UE and, based
on measurement
reports from the UE, configures an SCell for the UE. If blind SCell
configuration is enabled,
the eNodeB configures an SCell for the UE without initiating
measurements. The eNodeB
configures an SCell through an RRC Connection Reconfiguration
message. An SCell
provides the CA UE with more radio resources.
4. SCell activation or deactivation based on the traffic volume that is

monitored in real time.
Current configuration not based
on traffic volume

Carrier Aggregation Setting U2000
LST ENODEBALGOSWITCH
Current setting CA UE not implement PCC
Anchoring since there is no wider Bandwidth in
BOLT! LTE Network
Only for LTE FDD Cells, whether to to use

Frequency Prioity or Based on CAGROUP
SCC activation and deactivation not related with the

Traffic Volume
If this Switch turn ON, Source Cell will send

Handover Information to the Target Cell during HO

Carrier Aggregation Setting U2000
(3)
LST CAMGTCFG
(1)
(4)
(2)
(5)

Initial Access Priority
1) Chase when UE do camp on to F1 as the PCC
Without PCC With PCC

Anchoring Anchoring
if we
setting F1
F1 will be have highest Priority as PCC as the
highest
priority
2) Chase when UE do camp on to F2 as the PCC
78

Impacted Features
TDLOFD-001032 Intra-LTE Load Balancing TDLOFD-001003 DL 4x2 MIMO and TDLOFD-001060 DL 4x4 MIMO
CA requires special treatment in mobility load balancing (MLB) execution. UEs in use cannot receive data using four antennas while using CA. There are no plans
When an eNodeB selects UEs for inter-frequency measurements for PRB for
usage-based or commercial use of UEs that can receive data using four antennas while using CA. If this
UE quantity-based inter-frequency MLB, the eNodeB filters out CA UEs. CA
type of UEs will be available in the future, the UE performance needs to be determined
UEs will not
by
perform inter-frequency measurements or be handed over to inter-frequency
neighboring tests.
cells with the same azimuth as the source cell.
TDLBFD-002017 DRX TDLOFD-001016 VoIP Semi-persistent Scheduling

For a CA UE, the PCell and SCell must use the same DRX configurations. According to section 5.10 in 3GPP TS 36.321, semi-persistent scheduling can be used
only
on the PCCs of CA UEs.
TDLOFD-001001 DL 2x2 MIMO
Sounding reference signals (SRSs) are measured in the PCells of CA UEs. Therefore, TDLOFD-002001 Automatic Neighbour Relation (ANR) and TDLOFD-002002 Inter-
beamforming is available in transmission mode 7 (TM7) and TM8 for PCells. In SCells, RAT ANR
however, SRSs are not measured and beamforming is unavailable. The eNodeB uses To reduce algorithm complexity, Huawei eNodeBs do not instruct CA UEs to perform
TM1 measurements for ANR when CA is enabled. In the early stage of LTE network
or TM3 in SCells, regardless of parameter settings. TM1 applies when a single antenna construction, there are only a few CA UEs in the network, and ANR can be performed with
port is used for the SCell. For details about transmission mode selection, see MIMO the assistance of non-CA UEs.
Feature
Parameter Description.

Carrier Aggregation Sample Trial

PCC Anchoring Strategy (CA Group Cell)
PCC Anchoring
F2 F2
F1 F1 F1 F1
A4 PCC
Freq Cover BW (MHz) Priority
(dBm)
F1 (39475) Macro 15 7 -109
F2 (39325) Macro 15 0 -105

PCC Anchoring Strategy (CA Group
Cell) cont’d
RSRP • With default configuration

-100 UE CA find PCell
Both carrier have equal priority as PCell -105 (Priority 0)
randomly due to all
-105 Carrier has same priority
PCell A4 RSRP -105 (Priority 0)
Threshold(dBm) and same A4 PCC
Default
-110 Threshold.
• Considering Device
-115 RSRP Quality (Samsung
Smartphone) are lower
-120 -120 (QrxlevMin) than Mifi, adjust
handover trigger are
-125 required.
-130
-135 F2
F1
Time Domain

PCC Anchoring Strategy
(CA Group Cell) cont’d
RSRP
-100
• To make F1 as basic
-105
-105 (Priority 0)
layer of PCC
Anchoring, need to
-109 (Priority 7)
-110 Easy to enter F1 for make F1 Priority more
PCC Anchoring PCell A4 RSRP higher than F2.
Threshold(dBm)
-115
Proposed • Considering Device
quality of Samsung
-120 -120 (QrxlevMin)
Smartphone, PCC A4
Threshold need to be
-125
decrease into -109
dBm.
-130
-135 F2
F1
Time Domain

Carrier Aggregation Mobility Strategy
PCell Camping
SCell Deactivation
SCell Activation
EventA3-Intrafreq
F2 F2 F2
F1 F1 Case of A2 high F1 F1
EventA3-Intrafreq
• First time UE power ON, UE chose F1 based on PCC Anchoring procedure which have higher priority under one CA
Group Cell.
• When Dual Carrier with CA coverage are missing, SCC assignment deactivated by eNB through CAMGTCFG A2 & A4
value. PCC Still active on F1.
• In some area which threshold of A2EventA4 of InterfreqHOGroup are higher than default value (-109 dBm), CA UE will
do Interfreq Handover to another frequency and PCell will move to F2.
• When SCell RSRP are meet with Carrier Aggregation A4 Threshold, Carrier Aggregation are activated. In this condition
PCC will be keep on Last carrier since PCC Anchoring only applicable for UE in Initial Access procedure only.
• SCC will be deactivate when performing IntrafreqHO/InterfreqHO. To give better performance on SCC, need to be
activate specific switch under MO ENODEBALGOSWITCH for HOwithSCCCfg.

U2000 Setting
(1) (2)
ON
ON
(3)
7 -109
7 -109
7 -109

Duration Performance (Mobility Test)
Default
From the comparison of 3

configuration, PCC
Anchoring with SCC
Handover Information can
give better duration of PCC
& SCC Initial Setup
PCC Anchoring
PCC Anchoring
HOwithSCCCfg
&

Connection Setup Performance
(Static Test)
RRC Setup: 100%

Default
RRCReconfig CA: 100%

PCC Anchoring
RRC Setup: 100%

PCC Anchoring
HOwithSCCCfg
RRC Setup: 100%

&

MAC DL Throughput (CA)

MAC DL Throughput (CC1 & CC2)

Carrier Aggregation with Default Configuration

PCell EARFCN
UE prefer to attach to F2
during Initial Access
With default
configuration, PCC
distribution more
prefer on F2. The test
conduct with ADP
method.
F1 PCC : 6.6%
F2 PCC : 93.4%

SCell Activation

Carrier Aggregation with PCC Anchoring Configuration

PCell EARFCN
With PCC Anchoring

configuration, PCC
distribution more prefer
on F1. The test conduct
with ADP method.
F1 PCC : 94%
F2 PCC : 6%

SCell Activation

Handover Information
Not much Information

related with the SCC
Measurement

Carrier Aggregation with PCC Anchoring Configuration & HOwithSCCCfg
Configuration

Hedex Remarks

PCell EARFCN
With PCC Anchoring

configuration, PCC
distribution more prefer
on F1. The test conduct
with ADP method.
F1 PCC : 99.2%
F2 PCC : 0.8%

SCell Activation

Complete Measurement
Report Send by Source Cell
to the Target Cell & also to
the UE (A1, A2 & A4)
RRC-Reconfig
CA-Init
IntraFreq HO

Complete Measurement
Report Send by Source Cell
to the Target Cell & also to
the UE (A1, A2 & A4)
RRC-Reconfig
CA-Init
IntraFreq HO

Special Treatment of Handovers in CA
Scenarios:
If HoWithSccCfgSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter is off,
then:
The source eNodeB delivers an RRC Connection Reconfiguration message to remove the
SCell and performs an intra- or inter-frequency handover for the UE. After the UE is handed
over to the target cell, the target eNodeB configures an SCell for the UE
If HoWithSccCfgSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter is on,

then:
The source eNodeB includes the current SCell information in the IE sCellToAddModList
of the handover request message, which also contains the IE CandidateCellInfoList, sent
to the target eNodeB. The target eNodeB acquires candidate SCells from the IE
CandidateCellInfoList, arranges them in descending order of priority and RSRP (if
priorities are the same), and determines the new SCell to be configured after the handover.
Then, the target eNodeB updates the IE sCellToAddModList with the new SCell
information and sends the updated information in the handover command to the source
eNodeB. The source eNodeB sends an RRC Connection Reconfiguration message that
contains the IEs mobilityControlInfo, sCellToReleaseList, and sCellToAddModList to
remove the original SCell and configure the new SCell during the handover.
If the SCell configuration fails, no SCell is configured for the UE that has been handed
over to the target cell. In this case, the target eNodeB performs an SCell configuration
Procedure.

Summary of Trial
• With default value, all frequency have equal priority as the Pcell assignment for CA UE.
• With PCC Anchoring, one CA Group members can be selected as the higher priority Local Cell
ID as the main layer to performing PCell selection on the initial state only.
• SCC Activation only happen on the co-sect which have same azimuth and there is no HO in
Scell. Each time Handover Scell will be deactivated.
• To make better measurement report during Handover of CA UE, need to use HO with SCC
Configuration. eNodeB includes the IE reportAddNeighMeas in the handover-related A3, A4, and
A5 measurement configurations delivered to CA UEs.

Carrier Aggregation DL Throughput
Comparison

CA TARGET AREA
CA Implemented
CA not Implemented yet

CA Drive Test Performance
Non CA RSRP CA RSRP
Availability Issue (Mesjid III)
Device info :
- Non CA user =
MF 90
- CA user =
Galaxy Note 4
0.12 %

Non CA SINR CA SINR
Availability
Issue (Mesjid III)
Device info :
- Non CA user =
MF 90
- CA user =
Galaxy Note 4
0.43 %

Non CA DL Throughput CA DL Throughput

Non CA DL Throughput
CA DL Throughput 117 %

Drive Test Result Summary

Carrier Aggregation Counter
Measurement

Monitoring by Counter

Monitoring by Counter
Average DL CA Throughput CA HOSR CA SCell Mod%

($'L.Thrp.bits.DL.CAUser'/1000)/($'L.Thrp.Time.DL.CAUser') $'L.HHO.ExecSuccOut.CAUser.PCC'/$'L.HHO.ExecAttOut.CAUser.PC $'L.CA.DLSCELL.MOD.SUCC '/$'L.CA.DLSCELL.MOD.ATT '
C'
CA DL PCell PRB Utilization% CA SCell Activation% CA SCell RMV%

$'L.ChMeas.PRB.DL.PCell.Used.Avg'/@'PRBAVAILABLEDL' $'L.CA.DLSCELL.ACT.SUCC '/$'L.CA.DLSCELL.ACT.ATT ' $'L.CA.DLSCELL.RMV.MEAS.SUCC '/$'L.CA.DLSCELL.RMV.MEAS.ATT '
CA DL SCell PRB Utilization% CA SCell Add% CA SCell RMV Meas%

$'L.ChMeas.PRB.DL.SCell.Used.Avg'/@'PRBAVAILABLED $'L.CA.DLSCELL.ADD.SUCC '/$'L.CA.DLSCELL.ADD.ATT ' $'L.CA.DLSCELL.RMV.MEAS.SUCC '/$'L.CA.DLSCELL.RMV.MEAS.ATT '
L'
CA Drop Rate CA SCell AddBlind% Max DL Throughput CA User

$'L.E-RAB.AbnormRel.CAUser'/($'L.E- $'L.CA.DLSCELL.ADD.BLIND.SUCC '/$'L.CA.DLSCELL.ADD.BLIND.ATT ' ($'L.Thrp.bits.DL.CAUser'/(1000))/$'L.Thrp.Time.DL.CAUser'
RAB.AbnormRel.CAUser'+$'L.E-RAB.NormRel.CAUser')
CA DeAct% CA SCell Add Meas%

$'L.CA.DLSCELL.DEACT.SUCC '/$'L.CA.DLSCELL.DEACT.ATT ' $'L.CA.DLSCELL.ADD.MEAS.SUCC '/$'L.CA.DLSCELL.ADD.MEAS.ATT '

Carrier Aggregation Parameter
Optimization

Parameter Optimization

Thank You

Author
Ray Khastur, ST.
Educational Background :
 Bachelor of Telecommunication Engineer, Telkom Institute of Technology (2006 –
2010) JPPA-N Acceleration
Professional Experience :
 PI.Works, RAN Consultant (2014 ~ Present)
 China JIESAI, LTE Optimization Consultant (2014)
 Lintas Media Telekomunikasi, LTE RF Team Leader (2013 ~ 2014)
 HUAWEI Tech Investment, CWiL RNP/O Engineer (2011 ~ 2013)
 Transdata Global Network, CDMA RNO Engineer (2010 ~2011)
Achievements :
 RF Network Design & Planning First Commercial LTE Network in Indonesia (BOLT!
Super 4G LTE)-2013 HUAWEI
 NPI & Post Launch Optimization BOLT! Super 4G LTE - 2014 PI.Works
 LTE Technical Expert for HUAWEI Environment
 LTE Planning & Optimization Trainer Floatway Certified-2013
 LTE HUAWEI Trainer for Subcont-2016


6 Lteadvancefeature 160412153349

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

6 Lteadvancefeature 160412153349

Uploaded by

Copyright:

Available Formats

6.

LTE Advance Feature

Author : Ray Khastur

Consulting | Training | Research

Company Confidential - Pinnacle Learning Center

• Area where have similarity • eMBMS Service must be guarantee that

MobileComm Professionals, Inc

Consulting | Training | Research

•MBSFN synchronization area

MobileComm Professionals, Inc

Consulting | Training | Research

Consulting | Training | Research

BOLT Subframe Allignment

MobileComm Professionals, Inc

Consulting | Training | Research

• Maximum only 3 MBSN area can be setup in one

MobileComm Professionals, Inc

Consulting | Training | Research

MCCH : Multicast Control Channel

MobileComm Professionals, Inc

Consulting | Training | Research

MobileComm Professionals, Inc

Consulting | Training | Research

A single MBSFN subframe is

MobileComm Professionals, Inc

Consulting | Training | Research

• MBSFN reference signals are always transmitted on antenna port

MobileComm Professionals, Inc

Consulting | Training | Research

For TD-LTE SA2 Config,

MobileComm Professionals, Inc

Consulting | Training | Research

SFN Mod MCCH = SFN + Notif.Offset

SFN Mod MCCH(N) = SFN*(N)+Notif.Offset

From Above Sample, MMCH Modification will appear

Consulting | Training | Research

Radio Frame with MBSFN

Consulting | Training | Research

Company Confidential - Pinnacle Learning Center

 LTE RRC Connection Setup Complete Evolution

 Inter-eNodeB DL CoMP Based on Relaxed Backhaul

 Downlink Transmission by Multiple Cells

 Network Planning & Network Impact

MobileComm Professionals, Inc

Consulting | Training | Research

eX2 interface Interface for inter-eNodeB coordination

MobileComm Professionals, Inc

Consulting | Training | Research

MobileComm Professionals, Inc

Consulting | Training | Research

Inter-eNodeB service coordination features include:

MobileComm Professionals, Inc

Consulting | Training | Research

MobileComm Professionals, Inc

Consulting | Training | Research

CoMP was Introduce in LTE Release 11.

MobileComm Professionals, Inc

Consulting | Training | Research

DL CoMP Application Type Transmission Mode Related Feature

MobileComm Professionals, Inc

Consulting | Training | Research

MobileComm Professionals, Inc

Consulting | Training | Research