Professional Documents
Culture Documents
Issue Draft A
Date 2020-01-20
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 RAN3.1 Draft A (2020-01-20)...................................................................................................................................... 1
3 Overview....................................................................................................................................5
4 Hyper Cell.................................................................................................................................. 7
4.1 Principles.................................................................................................................................................................................... 7
4.2 Network Analysis..................................................................................................................................................................... 8
4.2.1 Benefits.................................................................................................................................................................................... 8
4.2.2 Impacts.................................................................................................................................................................................... 8
4.3 Requirements......................................................................................................................................................................... 10
4.3.1 Licenses................................................................................................................................................................................. 10
4.3.2 Software................................................................................................................................................................................11
4.3.3 Hardware.............................................................................................................................................................................. 13
4.3.4 Networking.......................................................................................................................................................................... 14
4.3.5 Others.................................................................................................................................................................................... 14
4.4 Operation and Maintenance............................................................................................................................................. 15
4.4.1 Data Configuration........................................................................................................................................................... 15
4.4.1.1 Data Preparation............................................................................................................................................................ 15
4.4.1.2 Using MML Commands............................................................................................................................................... 15
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 16
4.4.2 Activation Verification..................................................................................................................................................... 16
4.4.3 Network Monitoring......................................................................................................................................................... 17
5 Parameters.............................................................................................................................. 18
6 Counters.................................................................................................................................. 19
7 Glossary................................................................................................................................... 20
8 Reference Documents...........................................................................................................21
1 Change History
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 the desired 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.
Trial Features
Trial features are features that are not yet ready for full commercial release for
certain reasons. For example, the industry chain (terminals/CN) may not be
sufficiently compatible. However, these features can still be used for testing
purposes or commercial network trials. Anyone who desires to use the trial
features shall contact Huawei and enter into a memorandum of understanding
(MoU) with Huawei prior to an official application of such trial features. Trial
features are not for sale in the current version but customers may try them for
free.
Customers acknowledge and undertake that trial features may have a certain
degree of risk due to absence of commercial testing. Before using them, customers
shall fully understand not only the expected benefits of such trial features but also
the possible impact they may exert on the network. In addition, customers
acknowledge and undertake that since trial features are free, Huawei is not liable
for any trial feature malfunctions or any losses incurred by using the trial features.
Huawei does not promise that problems with trial features will be resolved in the
current version. Huawei reserves the rights to convert trial features into
commercial features in later R/C versions. If trial features are converted into
commercial features in a later version, customers shall pay a licensing fee to
obtain the relevant licenses prior to using the said commercial features. If a
customer fails to purchase such a license, the trial feature(s) will be invalidated
automatically when the product is upgraded.
3 Overview
Definition
In linear coverage scenarios, such as subways or railways, when UEs move along
the coverage areas at a high speed, a large number of handovers may occur in
common cells. The handovers may result in service drops or a decrease in
throughput, affecting user experience. The Hyper Cell function is introduced to
reduce the number of handovers and improve user experience in these scenarios.
Each TRP in the hyper cell uses the same physical cell identifier (PCI), cell global
identifier (CGI), frequency, and bandwidth.
As each TRP uses the same PCI and CGI, UEs do not perceive the existence of
multiple TRPs while moving among them. In this case, handovers do not occur
and user experience of UEs in areas between TRPs is improved.
Related Concepts
For details about the concepts related to cells, see Cell Management. The
following concepts are specific to this document only:
● Hyper cell
A hyper cell is formed by combining the continuous coverage areas of
multiple TRPs that use RF modules working on the same frequency. The
4 Hyper Cell
4.1 Principles
Serving TRP Selection upon UE Access
When a UE in the hyper cell accesses the network, the gNodeB selects a TRP with
the highest RSRP value as the serving TRP for the UE based on the preamble RSRP
values. The UE accesses the network through the serving TRP.
The UE-dedicated signaling and data for each TRP in the hyper cell are scheduled
and allocated independently by the serving TRP through which the UE accesses
the network. The total number of PDSCH and PUSCH RBs that can be allocated
remains the same as that before combination.
4.2.1 Benefits
UEs experience few handovers when moving between TRPs in a hyper cell. This
prevents service interruptions and the decrease in UE throughput caused by
frequent handovers. The number of handovers reduced correlates with the number
of combined TRPs. The more combined TRPs, the fewer the handovers. With
common channel joint transmission, the interference on common channels
decreases compared with when TRPs are not combined.
4.2.2 Impacts
Network Impacts
UEs in a hyper cell cannot use bandwidth part (BWP) for power saving. Therefore,
compared with UEs in common cells, UEs in a hyper cell consume more power.
As each TRP in a hyper cell consumes user instance resources, the number of UEs
that a hyper cell supports decreases.
After combination, the number of UEs that need to be served by the hyper cell
increases, which results in increased consumption of common channel resources
(such as SRS resources), and decreased cell throughput in heavy load scenarios.
Function Impacts
Function Function Reference Description
Name Switch
4.3 Requirements
4.3.1 Licenses
Feature ID Feature Model Sales Unit
Name
The sales unit "Per Cell" indicates the number of TRPs. Specifically, the number of
license units consumed by a hyper cell equals the number of TRPs in the hyper
cell. This is the same for other features enabled for TRPs in a hyper cell. If the
sales unit is "Per Cell", the number of consumed license units is equal to the
number of the TRPs in the hyper 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
Function Function Switch Reference
Name
4.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
All NR-capable main control boards and NR TDD-capable baseband processing
units support this function. To learn which main control boards are NR-capable
and baseband processing units are NR TDD-capable, see the related BBU technical
specifications in 3900 & 5900 Series Base Station Product Documentation.
Each hyper cell supports a maximum of 12 TRPs combined. The number of cells
supported by each baseband processing unit is described in the cell specifications
of the corresponding baseband processing unit. For details, see 3900 Series BBU
Technical Specifications or 5900 Series BBU Technical Specifications in 3900 &
5900 Series Base Station Product Documentation.
The configuration requirements on the baseband processing unit are described
below.
● Common and hyper cells cannot be configured on the same baseband
processing unit.
● UBBPfw1: Each UBBPfw1 board supports only one hyper cell and all TRPs in
the hyper cell must be served by the UBBPfw1 board.
● UBBPg series baseband processing units:
– Each UBBPg series baseband processing unit can support two hyper cells
and all TRPs in the hyper cells must be served by the UBBPg series
baseband processing unit.
RF Modules
All NR TDD-capable RF modules that work in low frequency bands support this
function. For details about such RF modules, see the technical specifications of the
related RF modules in 3900 & 5900 Series Base Station Product Documentation.
One of the following requirements must be met for TRPs to form a hyper cell.
● RF modules in a hyper cell are configured with the same number of antennas.
● RF modules in a hyper cell are 2T2R and 8T8R RF modules.
● RF modules in a hyper cell are 32T32R and 64T64R RF modules.
When RF modules serving a hyper cell are connected to two baseband processing
units, the number of antennas of RF modules connecting to the same baseband
processing unit must be the same. The number of cells supported by each
baseband processing unit is described in the cell specifications of the
corresponding baseband processing unit. For details, see 3900 Series BBU
Technical Specifications or 5900 Series BBU Technical Specifications in 3900 &
5900 Series Base Station Product Documentation.
Cells
Common cells and RF combination cells can be combined into a hyper cell.
Combined-RRU cells, cells in multi-carrier sectors, and uplink and downlink
decoupling cells cannot be combined into a hyper cell.
The cells that are combined into a hyper cell must meet the preceding
requirements. For details about the definition of cells, see Cell Management.
4.3.4 Networking
● Hyper cell is applicable to linear coverage scenarios, such as high-speed
railways and subways.
● In LampSite scenarios, if the coverage of one TRP does not meet the
requirements and multiple TRPs are needed to expand the coverage, hyper
cells can be used to reduce the network planning complexity.
4.3.5 Others
UEs in the hyper cell must support at least six sets of TRS resources. Otherwise,
the throughput may decrease and service drops may occur. In addition, UEs must
support UE-level scrambling code. Otherwise, problems such as access failures,
service drops, or increased bit error rate (BER) are likely to occur. If possible UE
compatibility issues such as access failure, frequent service drops, or extremely low
throughput occur, contact Huawei engineers and engineers from UE
manufacturers for handling.
The parameters of the multiple TRPs that form a hyper cell must be set in an
NRDUCellTrp MO when configuring the TRPs for an NR DU cell.
It is recommended that the NRDUCellTrp.NrDuCellTrpId values of physically
adjacent TRPs mod 6 be different. This prevents performance problems such as
service drops and UE throughput decrease caused by TRS interference between
TRPs. For example, the NRDUCellTrp.NrDuCellTrpId values of six adjacent TRPs
can be planned as 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).
MaxTransmitPower=300,CpriCompression=3DOT2_COMPRESSION, PowerConfigMode=TRANSMIT_POWER;
ADD NRDUCELLCOVERAGE: NrDuCellTrpId=0, NrDuCellCoverageId=1, SectorEqmId=1;
//Setting the RSRP difference based on which handovers between TRPs in the hyper cell are triggered
MOD NRDUCELLSRSMEAS: NrDuCellId=215, HyperCellTrpHoDeltaRsrp=2;
//Reserving only one TRP for a common cell and deleting the other TRPs
RMV NRDUCELLCOVERAGE:NrDuCellTrpId=1;
RMV NRDUCELLTRP: NrDuCellTrpId=1;
– N.HyperCell.TRP.User.Schedule.Dl.Sum
– N.HyperCell.TRP.User.Schedule.Ul.Sum
– N.HyperCell.TRP.User.RRCConn.Avg
– N.HyperCell.TRP.User.RRCConn.Max
● Observe the serving TRP of 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 serving TRP information of the UE.
N.HO.IntragNB.ExecSuccIn
N.HO.IntraFreq.IntragNB.PrepAttOut
N.HO.IntraFreq.IntragNB.ExecAttOut
N.HO.IntraFreq.IntragNB.ExecSuccOut
5 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.
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
6 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.
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
7 Glossary
8 Reference Documents
● 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception"
● 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification"
● Channel Management
● Scheduling
● CoMP
● LTE TDD and NR Spectrum Sharing
● Beam Management
● Carrier Aggregation
● UL and DL Decoupling
● UE Power Saving
● Remote Interference Management
● Energy Conservation and Emission Reduction
● LTE and NR Intelligent Carrier Shutdown
● Cell Management
● Technical Specifications in 3900 & 5900 Series Base Station Product
Documentation