Professional Documents
Culture Documents
Issue Draft A
Date 2021-12-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: https://www.huawei.com
Email: support@huawei.com
Contents
1 Change History.........................................................................................................................1
1.1 5G RAN6.1 Draft A (2021-12-30)...................................................................................................................................... 1
3 Overview....................................................................................................................................8
4 Cell Combination..................................................................................................................... 9
4.1 Principles.................................................................................................................................................................................... 9
4.2 Network Analysis.................................................................................................................................................................. 12
4.2.1 Benefits................................................................................................................................................................................. 12
4.2.2 Impacts.................................................................................................................................................................................. 12
4.3 Requirements......................................................................................................................................................................... 20
4.3.1 Licenses................................................................................................................................................................................. 20
4.3.2 Software................................................................................................................................................................................20
4.3.3 Hardware.............................................................................................................................................................................. 28
4.3.4 Networking.......................................................................................................................................................................... 30
4.3.5 Others.................................................................................................................................................................................... 30
4.4 Operation and Maintenance............................................................................................................................................. 30
4.4.1 Data Configuration........................................................................................................................................................... 30
4.4.1.1 Data Preparation............................................................................................................................................................ 30
4.4.1.2 Using MML Commands............................................................................................................................................... 35
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 38
4.4.2 Activation Verification..................................................................................................................................................... 38
4.4.3 Network Monitoring......................................................................................................................................................... 38
5.3 Requirements......................................................................................................................................................................... 45
5.3.1 Licenses................................................................................................................................................................................. 45
5.3.2 Software................................................................................................................................................................................46
5.3.3 Hardware.............................................................................................................................................................................. 52
5.3.4 Networking.......................................................................................................................................................................... 53
5.3.5 Others.................................................................................................................................................................................... 53
5.4 Operation and Maintenance............................................................................................................................................. 53
5.4.1 Data Configuration........................................................................................................................................................... 54
5.4.1.1 Data Preparation............................................................................................................................................................ 54
5.4.1.2 Using MML Commands............................................................................................................................................... 55
5.4.1.3 Using the MAE-Deployment...................................................................................................................................... 57
5.4.2 Activation Verification..................................................................................................................................................... 57
5.4.3 Network Monitoring......................................................................................................................................................... 58
6 Parameters.............................................................................................................................. 59
7 Counters.................................................................................................................................. 60
8 Glossary................................................................................................................................... 61
9 Reference Documents...........................................................................................................62
1 Change History
Technical Changes
Change Description Parameter Change RAT Base Station
Model
Added support for Joint Added the Low- 3900 and 5900
Transmission Cell NRDUCellMultiTrp.D freque series base
Combination. For details, ataTransMode ncy stations
see 5 Joint Transmission parameter. TDD DBS3900 LampSite
Cell Combination. FDD and DBS5900
LampSite
Added support for TRS Modified parameter: Low- 3900 and 5900
configuration Added the freque series base
optimization by Cell TRS_CONFIG_OPT_S ncy stations
Combination. For details, W option to the TDD DBS3900 LampSite
see Enhanced Functions NRDUCellMultiTrp. FDD and DBS5900
in 4.1 Principles. MultiTrpAlgoSwitch LampSite
parameter.
Editorial Changes
Revised descriptions in this document.
Removed the mutually exclusive relationship between Cell Combination and
spectral-efficiency-based connected mode MLB and that between Joint
Transmission Cell Combination and spectral-efficiency-based connected mode
MLB.
This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve optimal gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in Feature
Parameter Description documents apply only to the corresponding software
release. For future software releases, refer to the corresponding updated product
documentation.
3 Overview
In pole site and LampSite scenarios, there is significant coverage overlap between
cells and the inter-cell interference is strong, leading to a large decrease in UE
throughput. In addition, in linear coverage scenarios, such as subways or railways,
when UEs move quickly along the coverage areas, a large number of handovers
may occur between common cells. The handovers may result in service drops or a
decrease in throughput, affecting user experience. Cell Combination is introduced
to reduce interference and the number of handovers, improving user experience.
A combined cell is formed by combining multiple independent transmission
reception points (TRPs) that are working on the same frequency and have the
same bandwidth. The combined cell works as a logical cell to provide radio
communications services. Figure 3-1 shows a combined cell in a typical
continuous linear coverage scenario.
In this document, cells after combination are referred to as combined cells and
cells that are not combined are referred to as common cells.
In Cell Combination networking (with the NRDUCell.NrDuCellNetworkingMode
parameter set to HYPER_CELL_COMBINE_MODE), if the
NRDUCellMultiTrp.DataTransMode parameter is set to BASIC_MODE, basic
transmission mode is used, and the corresponding cell is a combined cell in basic
transmission mode; if the parameter is set to JOINT_MODE, joint transmission
mode is used, and the corresponding cell is a combined cell in joint transmission
mode.
4 Cell Combination
4.1 Principles
A combined cell must correspond to multiple TRPs, which are added to the
combined cell one by one by running the ADD NRDUCELLTRP command. Each
common cell corresponds to only one TRP.
If such a TRP exists, the gNodeB selects it as the new primary TRP, which performs
scheduling and allocates resources to the UE. When a UE is handed over between
the TRPs for a combined cell, the gNodeB does not need to send a handover
command to the UE, and the UE does not need to initiate an access procedure
again under the new TRP.
For a TDD combined cell, if the overshoot-coverage distance of the target TRP relative to
the primary TRP exceeds the value of the NRDUCellMultiTrp.TrgTrpOverCovTaThld
parameter multiplied by 4.8 (m), the SRS RSRP threshold for a handover to the target TRP
changes to the sum of the NRDUCellSrsMeas.HyperCellTrpHoDeltaRsrp and
NRDUCellMultiTrp.TrgTrpOverCovHoRsrpThldOfs parameter values.
For an FDD combined cell, if the overshoot-coverage distance of the target TRP relative to
the primary TRP exceeds the value of the NRDUCellMultiTrp.TrgTrpOverCovTaThld
parameter multiplied by 9.6 (m), the SRS RSRP threshold for a handover to the target TRP
changes to the sum of the NRDUCellSrsMeas.HyperCellTrpHoDeltaRsrp and
NRDUCellMultiTrp.TrgTrpOverCovHoRsrpThldOfs parameter values.
● The NRDUCellMultiTrp.SrcTrpOverCovTaThld parameter which specifies the
overshoot-coverage threshold for a source TRP
● The NRDUCellMultiTrp.SrcTrpOverCovHoRsrpThldOfs parameter which
specifies the offset to the SRS RSRP threshold for a handover from a TRP
identified as an overshoot-coverage TRP to a target TRP
NOTE
For a TDD combined cell, if the overshoot-coverage distance of the source TRP relative to
the target TRP exceeds the value of the NRDUCellMultiTrp.SrcTrpOverCovTaThld
parameter multiplied by 4.8 (m), the SRS RSRP threshold for a handover from the source
TRP changes to the sum of the NRDUCellSrsMeas.HyperCellTrpHoDeltaRsrp and
NRDUCellMultiTrp.SrcTrpOverCovHoRsrpThldOfs parameter values.
For an FDD combined cell, if the overshoot-coverage distance of the source TRP relative to
the target TRP exceeds the value of the NRDUCellMultiTrp.SrcTrpOverCovTaThld
parameter multiplied by 9.6 (m), the SRS RSRP threshold for a handover from the source
TRP changes to the sum of the NRDUCellSrsMeas.HyperCellTrpHoDeltaRsrp and
NRDUCellMultiTrp.SrcTrpOverCovHoRsrpThldOfs parameter values.
Enhanced Functions
● PUSCH scrambling code optimization is enabled by setting the
NRDUCellMultiTrp.PuschScrambleOptSw parameter to ON, allowing UEs
incompatible with UE-level scrambling codes to access the network.
● The TRS_CONFIG_OPT_SW option of the
NRDUCellMultiTrp.MultiTrpAlgoSwitch parameter specifies whether to
4.2.1 Benefits
After the Cell Combination function is enabled, the number of inter-cell handovers
decreases when UEs move between TRPs for a combined cell. This prevents service
interruptions or a decrease in UE throughput caused by frequent handovers. The
reduction in handovers correlates with the number of combined TRPs. The more
combined TRPs, the fewer the handovers.
4.2.2 Impacts
Network Impacts
As each TRP for a combined cell consumes user instance resources, the number of
UEs supported in a combined cell decreases.
After a combined cell is formed, the number of UEs that the cell needs to serve
increases, the consumption of common channel resources (such as SRS resources)
increases, and uplink and downlink PRB usages also increase significantly.
Therefore, the load of each common cell needs to be evaluated before this
function is enabled. If the total RB usage of common cells before the combination
exceeds 60%, you are advised to reduce the number of TRPs to be combined.
After a combined cell is formed, compared with common cells before the
combination, the available air interface resources of the combined cell decrease,
the cell traffic volume may decrease, the UE throughput may decrease, and the
transmission delay at the RLC layer may increase. It may also result in a
deterioration in KPIs related to accessibility and user experience.
After a combined cell is formed, the CPU usage of the baseband processing unit
increases by 1% to 5%, and the data packet scheduling delay may increase by 1
ms due to the unified scheduling.
As UEs in combined cells cannot use the power saving BWP function, they
consume more power than those in common cells.
After a combined cell is formed, the SRS resources of all UEs in the cell are
allocated in a unified manner. The SRS interference between TRPs may decrease,
and the SRS SINR may increase.
Function Impacts
RA Function Function Reference Description
T Name Switch
characteristic-based SRS
period adaptation for the
new cell.
● When there are activated
cells using UE-
characteristic-based SRS
period adaptation on the
base station, SRS period
adaptation cannot be
enabled for the new cell.
Otherwise, the cell setup
fails. In this case, in order
to enable SRS period
adaptation for the new
cell, you must deactivate
all activated cells using
UE-characteristic-based
SRS period adaptation on
the base station. Then,
enable SRS period
adaptation or static SRS
period configuration for
the deactivated cells, and
reactivate these cells.
Lastly, enable SRS period
adaptation for the new
cell.
4.3 Requirements
4.3.1 Licenses
RAT Feature ID Feature Model Sales Unit
Name
Note:
The sales unit "per Cell" indicates the number of TRPs. Specifically, the number
of license units required by a combined cell equals the number of TRPs for the
combined cell. For other features enabled for TRPs for a combined cell, if their
license sales unit is "per Cell", the number of required license units also equals
the number of TRPs for the combined cell.
4.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Prerequisite Functions
RA Function Function Switch Reference Description
T Name
Note:
a: For DBS3900 LampSite and DBS5900 LampSite, Cell Combination can be
enabled together with coordinated interference management. For 3900 and
5900 series base stations, Cell Combination and coordinated interference
management are mutually exclusive.
b: For DBS3900 LampSite and DBS5900 LampSite, Cell Combination can be
enabled together with RF channel intelligent shutdown. For 3900 and 5900
series base stations, Cell Combination and RF channel intelligent shutdown are
mutually exclusive.
c: The mutually exclusive relationship exists only in DBS3900 LampSite and
DBS5900 LampSite.
d: The mutually exclusive relationship between Cell Combination and power
saving BWP applies only to high-speed scenarios, not low-speed scenarios.
4.3.3 Hardware
Boards
A maximum of 12 TRPs can be combined to form a combined cell and all the TRPs
must be configured on baseband processing units in the same BBU. For LampSite
base stations, a maximum of 192 pRRUs can be configured in each combined cell.
For the maximum number of pRRUs that can be configured for each TRP, see
LampSite Pro Solution Description in 3900 & 5900 Series Base Station Product
Documentation.
It is recommended that the RF modules serving the TRPs for a combined cell be
directly connected to a baseband processing unit serving the combined cell.
There is no requirement for the main control board.
RF Modules
In TDD, NR TDD-capable RF modules that work in low frequency bands and adopt
the 8T8R mode or lower support this function. In addition, any one of the
following requirements on the transmit and receive modes of TRPs must be met
for the TRPs to form a combined cell:
Low-speed scenarios:
● The transmit and receive modes of all TRPs are the same (1T1R, 2T2R, 4T4R,
or 8T8R).
● There are only two transmit and receive modes and the supported
combinations are as follows:
– 2T2R and 8T8R
– 2T2R and 4T4R
– 4T4R and 8T8R
High-speed scenarios:
● The transmit and receive modes of all TRPs are the same (1T1R, 2T2R, 4T4R,
or 8T8R).
● The transmit and receive modes of TRPs are 2T2R and 8T8R.
In FDD, only NR FDD-capable 1T1R, 2T2R, 2T4R, 4T4R, or 8T8R RF modules
support this function. In addition, any one of the following requirements on the
transmit and receive modes of TRPs must be met for the TRPs to form a combined
cell:
Low-speed scenarios:
● The transmit and receive modes of all TRPs are the same (1T1R, 2T2R, 2T4R,
or 4T4R).
● There are only two transmit and receive modes and the supported
combinations are as follows:
– 1T1R and 2T2R
– 1T1R and 2T4R
– 1T1R and 4T4R
– 2T2R and 4T4R
– 2T4R and 4T4R
High-speed scenarios:
● The transmit and receive modes of all TRPs are the same (1T1R, 2T2R, 4T4R,
or 8T8R).
● The transmit and receive modes of TRPs are 2T2R and 4T4R.
To form a combined cell, the transmit and receive modes of TRPs configured on
one baseband processing unit must be the same. Therefore, two baseband
processing units are required when TRPs with different transmit and receive modes
form a combined cell. For example, when 2T2R and 8T8R TRPs form a combined
cell, the two types of TRPs must be configured on different baseband processing
units.
Cells
In TDD, distributed massive MIMO cells cannot form a combined cell.
4.3.4 Networking
In linear coverage scenarios, such as high-speed railways and subways, the Cell
Combination function can be used to reduce handovers.
In pole site and LampSite scenarios, the Cell Combination function can be used to
reduce inter-cell interference.
4.3.5 Others
UEs must support at least six sets of TRS resources in order to avoid a decrease in
traffic volume and service drops. In addition, UEs must support UE-level
scrambling codes. Otherwise, problems such as access failures, service drops, or
increased cell BLER are likely to occur. If possible UE compatibility issues such as
access failures, frequent service drops, or extremely low traffic volume occur,
contact Huawei engineers and engineers from UE manufacturers for handling.
The parameters in the NRDUCellTrp MO must be set for each TRP for the same
combined cell when configuring TRPs for an NR DU cell.
It is recommended that the NRDUCellTrp.NrDuCellTrpId mod 6 values of
adjacent TRPs be different in order to prevent performance issues, such as service
drops and UE throughput decrease caused by TRS interference between TRPs. For
example, the NRDUCellTrp.NrDuCellTrpId values can be planned for six adjacent
TRPs as follows: 15 (mod 6 = 3), 16 (mod 6 = 4), 17 (mod 6 = 5), 18 (mod 6 = 0),
19 (mod 6 = 1), and 20 (mod 6 = 2).
Table 4-2 describes the parameters used for function optimization.
The TRS_CONFIG_OPT_SW
option can be selected to
improve the access success
rate of some UEs. When this
option is selected, TRS
information is included in
the RRC Setup message
instead of the RRC
Reconfiguration message.
to be reestablished. For detailed operations and precautions, see the related MML
command reference.
It is recommended that all cells to be served by the BBU be configured before
activating any cell to avoid configuration conflicts.
//Setting the number of RSRP evaluations for an inter-TRP handover in the combined cell
MOD NRDUCELLMULTITRP: NrDuCellId=0, InterTrpHoRsrpEvalTimes=1;
//Setting the number of times the MAC CE is sent during an inter-TRP handover in the combined cell
MOD NRDUCELLMULTITRP: NrDuCellId=0, InterTrpHoMacCeTransTimes=2;
//Setting the offset of the power for sending the MAC CE during an inter-TRP handover in the combined cell
MOD NRDUCELLMULTITRP: NrDuCellId=0, InterTrpHoMacCePwrOfs=0;
//Enabling PUSCH scrambling code optimization when there are UEs incompatible with UE-level scrambling
codes on the network
MOD NRDUCELLMULTITRP: NrDuCellId=0, PuschScrambleOptSw=ON;
//Modifying the CSI-RS configuration policy for the combined cell (FDD)
MOD NRDUCELLCSIRS: NrDuCellId=0, CsirsCellResourceNum=1_RESOURCE, CsiUserPeriod=SLOT40;
MOD NRDUCELLPDSCH: NrDuCellId=0, RateMatchSwitch=ZP_TRS_MODE_SW-1;
MOD NRDUCELLCSIRS: NrDuCellId=0, CsiPeriod=SLOT40, InterTrpCsirsStaggerMode=MOD2_STAGGER;
//Modifying the CSI-RS configuration policy for the combined cell (TDD)
MOD NRDUCELLCSIRS: NrDuCellId=0, CsiPeriod=SLOT40, InterTrpCsirsStaggerMode=MOD2_STAGGER;
//Modifying the inter-TRP handover policy when the transmit power differs between TRPs
MOD NRDUCELLMULTITRP: NrDuCellId=0, HyperCellTrpHoRsrpPolicy=DL_EQ_RSRP;
//Setting the offset to the RSRP threshold for an inter-TRP handover to prevent ping-pong handovers
MOD NRDUCELLMULTITRP: NrDuCellId=0, PingPongHoRsrpThldOfs=4;
//Setting the overshoot-coverage threshold for a target TRP and the offset to the threshold for a handover
to the overshoot-coverage TRP
MOD NRDUCELLMULTITRP: NrDuCellId=0, TrgTrpOverCovTaThld=80;
MOD NRDUCELLMULTITRP: NrDuCellId=0, TrgTrpOverCovHoRsrpThldOfs=0;
//Setting the overshoot-coverage threshold for a source TRP and the offset to the threshold for a handover
from the overshoot-coverage TRP
MOD NRDUCELLMULTITRP: NrDuCellId=0, SrcTrpOverCovTaThld=60;
MOD NRDUCELLMULTITRP: NrDuCellId=0, SrcTrpOverCovHoRsrpThldOfs=0;
//Optimizing the SRS period configuration based on the maximum number of UEs in the cell
MOD NRDUCELLSRS: NrDuCellId=0, SrsPeriod=SL160;
//Retaining only one TRP for a common cell and deleting the other TRPs
RMV NRDUCELLCOVERAGE: NrDuCellTrpId=1, NrDuCellCoverageId=1;
RMV NRDUCELLTRP: NrDuCellTrpId=1;
N.HO.IntragNB.ExecAttIn
N.HO.IntragNB.ExecSuccIn
N.HO.IntraFreq.IntragNB.PrepAttOut
N.HO.IntraFreq.IntragNB.ExecAttOut
N.HO.IntraFreq.IntragNB.ExecSuccOut
N.NsaDc.IntraSgNB.PSCell.Change.Succ
5.1 Principles
In Cell Combination networking, frequent inter-TRP handovers may occur in high-
speed cells due to the overshoot coverage of TRPs, affecting UE throughput. In
high-speed cells, Joint Transmission Cell Combination enables joint data
transmission for downlink channels, improving the reliability of data transmission.
This function is enabled by setting the NRDUCell.NrDuCellNetworkingMode
parameter to HYPER_CELL_COMBINE_MODE and the
NRDUCellMultiTrp.DataTransMode parameter to JOINT_MODE.
NOTE
5.2.1 Benefits
Joint data transmission is adopted in a combined cell in joint transmission mode,
bringing diversity gains for UEs in TRP overlapping areas. In addition, the reliability
of data transmission is improved in TRP overlapping areas, increasing downlink
throughput, indicated by User Downlink Average Throughput (DU), and the UE
access success rate in these areas.
5.2.2 Impacts
Network Impacts
Compared with a combined cell in basic transmission mode, a combined cell in
joint transmission mode centrally processes and transmits data, which increases
system overheads. In heavy-loaded scenarios where the average uplink or
downlink PRB usage exceeds 60% or when PDCCH CCE resources are insufficient,
the uplink and downlink UE throughput, indicated by User Uplink Average
Throughput (DU) and User Downlink Average Throughput (DU), decreases.
After a combined cell in joint transmission mode is formed, at some positions in
the cell, signals transmitted from different TRPs may be out of phase with each
other, resulting in a reduced amplitude and weakened signal strength. In addition,
as the delay difference between TRPs may be large at some positions, multipath
signals may interfere with each other. As a result, the downlink UE throughput,
indicated by User Downlink Average Throughput (DU), decreases.
After a combined cell in joint transmission mode is formed, the energy
consumption of RF modules may increase.
After a combined cell in joint transmission mode is formed, the downlink rank
may increase and downlink MCS index may decrease.
After a combined cell in joint transmission mode is formed, the number of
consumed PDCCH CCEs increases, the average number of PDCCH CCEs used for
transmitting uplink and downlink DCI may increase, the average cell PDCCH CCE
usage may increase, and uplink and downlink CCE aggregation levels may
decrease due to downlink joint transmission.
Compared with a combined cell in basic transmission mode, the interference of a
combined cell in joint transmission mode to neighboring cells may be stronger,
causing downlink UE throughput, indicated by User Downlink Average
Throughput (DU), in the neighboring cells to decrease.
Function Impacts
Some of the function impacts for Joint Transmission Cell Combination are the
same as those for Cell Combination. For details, see Function Impacts in 4.2.2
Impacts. The following table describes only those that are different.
5.3 Requirements
5.3.1 Licenses
RAT Feature ID Feature Model Sales Unit
Name
Note:
The sales unit "per Cell" indicates the number of TRPs. Specifically, the number
of license units required by a combined cell equals the number of TRPs for the
combined cell. For other features enabled for TRPs for a combined cell, if their
license sales unit is "per Cell", the number of required license units also equals
the number of TRPs for the combined cell.
5.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Prerequisite Functions
RAT Function Function Switch Reference Description
Name
Note:
a: For macro base stations with Joint Transmission Cell Combination taking
effect, RF channel intelligent shutdown can be enabled only in non-high-speed
scenarios. After half of RF channels are shut down, the remaining transmit and
receive channel combinations must be compatible with Joint Transmission Cell
Combination. For LampSite base stations, RF channel intelligent shutdown can
be enabled with Joint Transmission Cell Combination.
b: The mutually exclusive relationship exists only in DBS3900 LampSite and
DBS5900 LampSite.
c: The mutually exclusive relationship between Joint Transmission Cell
Combination and power saving BWP applies only to high-speed scenarios, not
low-speed scenarios.
5.3.3 Hardware
Base Station Models
● 3900 and 5900 series base stations. 3900 series base stations must be
configured with the BBU3910.
● DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be
configured with the BBU3910.
Boards
The working mode of a multimode baseband processing unit must be NR only.
For other requirements, see Boards in 4.3.3 Hardware.
RF Modules
In TDD, NR TDD-capable RF modules that work in low frequency bands and adopt
the 8T8R mode or lower support this function. In addition, any one of the
following requirements on the transmit and receive modes of TRPs must be met
for the TRPs to form a combined cell in joint transmission mode:
Low-speed scenarios:
● The transmit and receive modes of all TRPs are the same (1T1R, 2T2R, 4T4R,
or 8T8R).
● Mixed configurations of 2T2R+4T4R, 2T2R+8T8R, or 4T4R+8T8R TRPs are
supported.
High-speed scenarios:
● The transmit and receive modes of all TRPs are the same (1T1R, 2T2R, 4T4R,
or 8T8R).
● The transmit and receive modes of TRPs are 2T2R and 8T8R.
In FDD, NR FDD-capable RF modules that work in low frequency bands and adopt
the 4T4R mode or lower support this function. In addition, any one of the
following requirements on the transmit and receive modes of TRPs must be met
for the TRPs to form a combined cell in joint transmission mode:
Low-speed scenarios:
● The transmit and receive modes of all TRPs are the same (1T1R, 2T2R, 2T4R,
or 4T4R).
● Mixed configurations of 2T2R+4T4R or 2T4R+4T4R TRPs are supported.
High-speed scenarios:
● The transmit and receive modes of all TRPs are the same (1T1R, 2T2R, or
4T4R).
● The transmit and receive modes of TRPs are 2T2R and 4T4R.
To form a combined cell, the transmit and receive modes of TRPs configured on
one baseband processing unit must be the same. Therefore, two baseband
processing units are required when TRPs with different transmit and receive modes
form a combined cell. For example, when 2T2R and 8T8R TRPs form a combined
cell, the two types of TRPs must be configured on different baseband processing
units.
It is recommended that RF modules with the same transmit and receive modes be
of the same model. Otherwise, the downlink transmit power of some RF modules
may decrease.
Cells
The requirements on cells for Joint Transmission Cell Combination are the same as
those for Cell Combination. For details, see Cells in 4.3.3 Hardware.
5.3.4 Networking
● Joint Transmission Cell Combination cannot be enabled for cells operating in
n38 and n40 frequency bands.
● The length of the optical fiber connecting a BBU and an RRU must not exceed
20 km.
● For cells to be reconstructed into a combined cell in joint transmission mode,
if the product of the average CCE usage of all cells and the number of TRPs to
be combined is greater than 60%, CCE resources may be insufficient after the
reconstruction, affecting the access success rate. You are advised to increase
the number of PDCCH symbols before the reconstruction or retain the
networking mode. The CCE usage is calculated by dividing the value of
N.CCE.Used.Avg by that of N.CCE.Avail.Avg, and the number of PDCCH
symbols is specified by the NRDUCellPdcch.OccupiedSymbolNum parameter.
5.3.5 Others
For details, see 4.3.5 Others.
The parameters in the NRDUCellTrp MO must be set for each TRP for the same
combined cell when configuring TRPs for an NR DU cell.
If a new cell fails to be activated when served by a BBU serving combined cells,
and the cause value of the failure is "The hyper cell configuration experiences a
conflict", run the STR NRDUCELLREDEPLOY command to redeploy cells on all
baseband processing units. The STR NRDUCELLREDEPLOY command is used to
redeploy NR DU cells on the baseband equipment in one click. This is a high-risk
MML command and running the command causes some cells served by the BBU
to be reestablished. For detailed operations and precautions, see the related MML
command reference.
//Setting the RSRP difference based on which handovers between TRPs for the combined cell in joint
transmission mode are triggered
MOD NRDUCELLSRSMEAS: NrDuCellId=0, HyperCellTrpHoDeltaRsrp=2;
//Setting the number of RSRP evaluations for an inter-TRP handover in the combined cell in joint
transmission mode
MOD NRDUCELLMULTITRP: NrDuCellId=0, InterTrpHoRsrpEvalTimes=1;
//Modifying the inter-TRP handover policy when the transmit power differs between TRPs
MOD NRDUCELLMULTITRP: NrDuCellId=0, HyperCellTrpHoRsrpPolicy=DL_EQ_RSRP;
//Retaining only one TRP for a common cell and deleting the other TRPs
RMV NRDUCELLCOVERAGE: NrDuCellTrpId=1, NrDuCellCoverageId=1;
RMV NRDUCELLTRP: NrDuCellTrpId=1;
In a combined cell in joint transmission mode, downlink data is transmitted for all
TRPs, and the value of the N.HyperCell.TRP.PRB.DL.Used.Avg counter is the same for
all TRPs. The value of the N.HyperCell.TRP.PRB.DL.Used.Avg counter indicates PRBs
used by the primary TRP in a combined cell in basic transmission mode. Compared
with a combined cell in basic transmission mode, the value of the
N.HyperCell.TRP.PRB.DL.Used.Avg counter increases in a combined cell in joint
transmission mode.
● Observe the primary TRP serving the UE.
Log in to the MAE-Access, choose Monitor > Signaling Trace > Signaling
Trace Management > NR > User Performance Monitoring > User Common
Monitoring, and view the information of the primary TRP serving the UE.
6 Parameters
The following hyperlinked EXCEL files of parameter reference match the software
version with which this document is released.
● Node Parameter Reference: contains device and transport parameters.
● gNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE
You can find the EXCEL files of parameter reference for the software version used on the
live network from the product documentation delivered with that version.
----End
7 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● gNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
----End
8 Glossary
9 Reference Documents
● 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception"
● Channel Management
● Scheduling
● Beam Management
● Carrier Aggregation
● UL and DL Decoupling
● Synchronization
● Interference Avoidance
● Remote Interference Management (Low-Frequency TDD)
● Energy Conservation and Emission Reduction
● MIMO (TDD)
● Super Uplink
● UE Power Saving
● LTE and NR Power Sharing
● Cell Management
● Extended Cell Range
● LTE FDD and NR Spectrum Sharing
● CoMP
● 5G Networking and Signaling
● Mobility Load Balancing
● FWA
● Admission Control
● Network Slicing
● Indoor Coverage
● Virtual Grid-based Multi-Frequency Coordination
● Coordinated Interference Management (Low-Frequency TDD)
● NSA Networking based on EPC
● Smart 8T8R (FDD)