GSM and LTE Spectrum Concurrency (SRAN15.1)

SingleRAN
GSM and LTE Spectrum

Concurrency Feature Parameter
Description
Issue Draft A
Date 2018-12-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2019. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
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.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. i

SingleRAN
GSM and LTE Spectrum Concurrency Feature Parameter
Description Contents
Contents
1 Change History.............................................................................................................................. 1
1.1 SRAN15.1 Draft A (2018-12-30)................................................................................................................................... 1
2 About This Document.................................................................................................................. 3

2.1 General Statements......................................................................................................................................................... 3
2.2 Features in This Document.............................................................................................................................................4
3 Overview......................................................................................................................................... 5
4 GSM and LTE Spectrum Concurrency...................................................................................... 7
4.1 Principles........................................................................................................................................................................ 7
4.2 Network Analysis......................................................................................................................................................... 10
4.2.1 Benefits...................................................................................................................................................................... 10
4.2.2 Impacts.......................................................................................................................................................................12
4.3 Requirements................................................................................................................................................................ 22
4.3.1 Licenses..................................................................................................................................................................... 22
4.3.2 Software.....................................................................................................................................................................23
4.3.3 Hardware................................................................................................................................................................... 28
4.3.4 Networking................................................................................................................................................................ 29
4.3.5 Others.........................................................................................................................................................................33
4.4 Operation and Maintenance..........................................................................................................................................33
4.4.1 When to Use.............................................................................................................................................................. 33
4.4.2 Data Configuration.................................................................................................................................................... 41
4.4.2.1 Data Preparation..................................................................................................................................................... 41
4.4.2.2 Using MML Commands......................................................................................................................................... 56
4.4.2.3 Using the CME....................................................................................................................................................... 58
4.4.3 Activation Verification.............................................................................................................................................. 59
4.4.4 Network Monitoring.................................................................................................................................................. 61
4.4.5 Possible Issues........................................................................................................................................................... 61
5 GSM and LTE Spectrum Concurrency Phase 2..................................................................... 62

5.1 Principles...................................................................................................................................................................... 62
5.2 Network Analysis......................................................................................................................................................... 63
5.2.1 Benefits...................................................................................................................................................................... 63
5.2.2 Impacts.......................................................................................................................................................................65
5.3 Requirements................................................................................................................................................................ 66
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. ii

SingleRAN
Description Contents
5.3.1 Licenses..................................................................................................................................................................... 66
5.3.2 Software.....................................................................................................................................................................67
5.3.3 Hardware................................................................................................................................................................... 70
5.3.4 Networking................................................................................................................................................................ 70
5.3.5 Others.........................................................................................................................................................................74
5.4 Operation and Maintenance..........................................................................................................................................74
5.4.1 When to Use.............................................................................................................................................................. 74
5.4.2 Data Configuration.................................................................................................................................................... 75
5.4.2.1 Data Preparation..................................................................................................................................................... 75
5.4.2.2 Using MML Commands......................................................................................................................................... 77
5.4.2.3 Using the CME....................................................................................................................................................... 78
5.4.3 Activation Verification.............................................................................................................................................. 79
5.4.4 Network Monitoring.................................................................................................................................................. 79
5.4.5 Possible Issues........................................................................................................................................................... 79
6 Parameters..................................................................................................................................... 80
7 Counters........................................................................................................................................ 81
8 Glossary......................................................................................................................................... 82
9 Reference Documents................................................................................................................. 83
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. iii

SingleRAN
Description 1 Change History
1 Change History
This section describes changes not included in the "Parameters", "Counters", "Glossary", and
"Reference Documents" chapters. These changes include:
l Technical changes
Changes in functions and their corresponding parameters
l Editorial changes
Improvements or revisions to the documentation
1.1 SRAN15.1 Draft A (2018-12-30)

This issue introduces the following changes to SRAN15.0 02 (2018-11-26).
Technical Changes
Change Description Parameter Change Base Station
Model
Added the AAU5973e to the list of RF None 3900 series base

modules that do not support this function. stations and 5900
For details, see 4.3.3 Hardware. series base stations
Added Downlink Massive CA to the None 3900 series base

impacted functions. For details, see 4.2.2 stations and 5900
Impacts. series base stations
Added the mutually exclusive relationship None 3900 series base

with UMTS and LTE Spectrum Sharing stations and 5900
Based on DC-HSDPA, Intelligent Beam series base stations
Shaping, and NPREO Constant
Optimization. For details, see 4.3.2
Software.
Added the RRU5301 and RRU5309 to the None 3900 series base
list of RF modules that do not support this stations and 5900
function. For details, see 4.3.3 Hardware. series base stations
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 1

SingleRAN
Description 1 Change History
Change Description Parameter Change Base Station

Model
Added the mutually exclusive relationship None 3900 series base

with the load-based frequency hopping (FH) stations and 5900
set adaptation and Multi-site Cell functions. series base stations
For details, see 5.3.2 Software.
Editorial Changes
l Modified the description of hardware requirements. For details, see 4.3.3 Hardware.
l Added the description of the simultaneous use with a multi-sector solution on the LTE
side. For details, see 4.3.4 Networking and 4.4.2.2 Using MML Commands.
l Added the description of the multi-RAT scheduling management switch on the GSM
side. For details, see 4.4.2.1 Data Preparation and 4.4.2.2 Using MML Commands.
l Modified the description of MML configuration on the GSM side. For details, see
4.4.2.2 Using MML Commands.
l Modified the description of deactivation command examples on the LTE side. For
details, see 5.4.2.2 Using MML Commands.
l Modified the description of cell power restriction. For details, see 5.2.1 Benefits and
5.4.2.1 Data Preparation.
l Revised descriptions in the document. For details, see descriptions throughout the
document.

SingleRAN
Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
Feature Parameter Description documents are intended to acquaint readers with:
l The technical principles of features and their related parameters
l The scenarios where these features are used, the benefits they provide, and the impact
they have on networks and functions
l Requirements of the operating environment that must be met before feature activation
l Parameter configuration required for feature activation, verification of feature activation,
and monitoring of feature performance
NOTE
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

SingleRAN
Description 2 About This Document
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.
2.2 Features in This Document

This document describes the following multimode features.
Feature ID Feature Name Section
MRFD-130201 GSM and LTE Spectrum 4 GSM and LTE Spectrum

Concurrency (GSM) Concurrency
MRFD-130221 GSM and LTE Spectrum

Concurrency (LTE FDD)
MRFD-131201 GSM and LTE Spectrum 5 GSM and LTE Spectrum

Concurrency Phase 2 (GSM) Concurrency Phase 2
MRFD-131221 GSM and LTE Spectrum

Concurrency Phase 2 (LTE FDD)

SingleRAN
Description 3 Overview
3 Overview
Network performance faces unprecedented challenges with the increasing popularity of data
services and penetration rate of smart terminals. However, some operators are confronted with
insufficient spectrum and long-term existence of GSM users. Consequently, operators cannot
evolve GSM networks into LTE networks to provide better data service experience. This
function enables GSM and LTE to be deployed on the same spectrum band, and determines
the usage of this band based on the GSM service volume. The co-deployment of GSM and
LTE on one spectrum band ensures that a spectrum band can be allocated to more than one
radio access technology (RAT). This improves spectral efficiency.
The GSM and LTE Spectrum Concurrency function applies to the frequency bands supported
by both GSM and LTE: 850 MHz, 900 MHz, 1800 MHz, and 1900 MHz. It enables GSM and
LTE to be deployed on a frequency band covering particular areas, and allows these two RATs
to share this band based on the GSM traffic volume. The BSC and eNodeB implement joint
allocation and scheduling of the shared spectrum band. When GSM does not occupy the
shared spectrum band, LTE can use the shared spectrum band to meet its large bandwidth
requirements.
The example in Figure 3-1 illustrates GSM and LTE using a spectrum band before and after
this function is activated. Before this function is enabled, LTE can only use a comparatively
small standard bandwidth. After it is enabled, GSM and LTE share a part of the spectrum,
during which LTE can have the following:
l A larger non-standard bandwidth during GSM peak hours

l A larger standard bandwidth during GSM off-peak hours
The following explains the terms appearing in Figure 3-1:

l GSM exclusive carriers
GSM exclusive carriers are those that do not overlap with the LTE standard bandwidth.
l GSM shared carriers
GSM shared carriers are those that overlap with the LTE standard bandwidth.
l LTE exclusive resource elements (REs)/resource blocks (RBs)
LTE exclusive REs/RBs are sufficiently spaced away from GSM frequencies in the
frequency domain, and the spacing between them is a guard band.
l LTE shared REs/RBs
LTE shared REs/RBs overlap with GSM frequencies in the frequency domain.

SingleRAN
Description 3 Overview
Figure 3-1 Example of the use of a spectrum band by GSM and LTE before and after this
function is activated

SingleRAN
Description 4 GSM and LTE Spectrum Concurrency
4 GSM and LTE Spectrum Concurrency
4.1 Principles
This function implements joint allocation and scheduling on the shared spectrum band by
interference coordination on the GSM side and by radio resource management (RRM) on the
LTE side.
Architecture
With this function, a communication link is established between the BSC and eNodeB for the
effective exchange of interference coordination information. Figure 4-1 shows the
networking architecture of GSM and LTE Spectrum Concurrency. Table 4-1 describes the
functions of the network elements (NEs) and interfaces involved in the networking
architecture.

SingleRAN
Figure 4-1 Networking architecture of GSM and LTE Spectrum Concurrency
Table 4-1 Functions of the NEs and interfaces in the networking architecture
NE or Function
Interfa
ce
BSC Calculates the interference from LTE to GSM mobile stations (MSs) in real time,
and sends the multiplexing status of GSM shared frequencies to the eNodeB.
BTS Forwards the information between the BSC and eNodeB.
eNode Uses the received multiplexing status of GSM shared frequencies to calculate the
B amount of time-frequency resources available on the shared spectrum. It also
allocates and schedules the resources accordingly.
BE A Huawei proprietary interface introduced between the BSC and eNodeBa

interfac
e
Iur-g The interface between two BSCs. When the GSM cell enabled with this function
interfac is configured with an interfering neighboring cell of another BSC, an Iur-g
e interface must be configured between these two BSCs.

SingleRAN
NE or Function
Interfa
ce
a: The BE interface consists of two parts. The first part is the communication interface
between the BSC and BTS. In addition to the existing Abis transmission links, BSC-BTS/
eNodeB Signal Links (BSLs) are added between the BSC and BTS for the information
exchange between the BSC and eNodeB. A BSL is set up by configuring the BTSBSL MO
on the BSC side. The other part is the communication interface between the BTS and
eNodeB. A proprietary interface is established between the BTS and eNodeB for
information exchange. The interface establishment is controlled by the
BTS_ENODEB_LINK_SETUP_SWITCH option of the eNodeB parameter
GlobalProcSwitch.InterRatLinkSetupSwitch.
Interference Coordination on the GSM Side

This section describes MRFD-130201 GSM and LTE Spectrum Concurrency (GSM).
This function is controlled by the GCELLGLSPECCLOUD.GLSpecConcurSw parameter.
When this parameter is set to ON, the BSC determines whether the interference from LTE to
GSM MSs is tolerable. This is determined based on the GSM and LTE level difference
threshold for timeslot multiplexing, which is configured by the
GCELLGLSPECCLOUD.GLRxLevelGapThd parameter. The GSM MSs that are interfered
by LTE are determined by the co-coverage relationships between GSM and LTE cells
(configured in the GCELLGLCOCOVER MO), as well as by the interference neighboring
cell relationships (configured in the G2GNCELL MO). If the interference level is tolerable,
the BSC instructs the eNodeB to use the shared spectrum. Otherwise, the BSC instructs the
eNodeB not to use the shared spectrum.
RRM on the LTE Side

This section describes MRFD-130221 GSM and LTE Spectrum Concurrency (LTE FDD).
This function is enabled only when the SpectrumCloud.SpectrumCloudSwitch parameter is
set to GL_SPECTRUM_CONCURRENCY.
When this function is enabled, the eNodeB uses the multiplexing status of shared frequencies
received from the BSC in real time to calculate the amount of time-frequency resources
available on the shared spectrum, and allocates and schedules the resources accordingly.
The following describes resource allocation and scheduling for each LTE physical channel:
l Physical control format indicator channels (PCFICHs) and physical HARQ indicator
channels (PHICHs)
The positions of REs occupied by PCFICHs and PHICHs are related to the physical cell
identifier (PCI), which is configured by the Cell.PhyCellId parameter. A PCI that is not
or only slightly interfered by GSM is planned for the LTE cell to ensure the best possible
PCFICH and PHICH performance.
l Physical downlink control channels (PDCCHs)
PDCCHs use only the frequencies that cause no or only little interference to GSM based
on the multiplexing status of shared frequencies received from the BSC. In addition, due
to GSM interference, some resource element groups (REGs) of PDCCHs cannot be used.

SingleRAN
Therefore, to compensate the loss in the demodulation performance of PDCCHs, the

transmit power or aggregation level of PDCCHs is boosted.
l Physical downlink shared channels (PDSCHs)
LTE preferentially schedules LTE exclusive RBs in the downlink. If the number of LTE
exclusive RBs is insufficient to meet service requirements, LTE continues to schedule
LTE shared RBs. LTE schedules them based on the multiplexing status of shared
frequencies received from the BSC. If the shared and exclusive RBs experience a similar
level of interference, LTE jointly schedules them.
l Physical uplink control channels (PUCCHs)
PUCCHs occupy RBs at both ends of a standard LTE bandwidth. When this function is
enabled, PUCCHs occupy LTE exclusive RBs that are not interfered by GSM, rather
than the edge RBs.
l Physical uplink shared channels (PUSCHs)
LTE preferentially schedules LTE exclusive RBs in the uplink. If the number of LTE
exclusive RBs is insufficient to meet service requirements, LTE continues to schedule
LTE shared RBs. LTE schedules them based on the multiplexing status of shared
frequencies received from the BSC.
l Sounding reference signals (SRSs) and physical random access channels (PRACHs)
SRSs and PRACHs occupy LTE exclusive RBs. The resource allocation modes of SRSs
and PRACHs remain unchanged, and SRSs and PRACHs can be multiplexed on the
same RBs.
NOTE
For details on the resource allocation and scheduling for other physical channels, see Physical Channel
Resource Management in eRAN Feature Documentation.
4.2 Network Analysis
4.2.1 Benefits
This function allows full spectrum utilization and improves LTE network capacity under the
condition that the interference from LTE to GSM is at a tolerable amount. Table 4-2 describes
the LTE capacity gains compared with an LTE network using the adjacent lower standard
bandwidth under different total bandwidths, power configurations, and achievable LTE
standard bandwidths.

SingleRAN
Table 4-2 LTE downlink capacity gains

Total Achievable GSM and Adjacent Capacity Capacity
Bandwid LTE Standard LTE Lower Gain Gain
th Bandwidth Power LTE When When
Configurat Standard BCCHs TCHs Are
ion Bandwidt Are Deployed
h Deployed on the
on the Shared
Shared Spectrum
Spectrum
≥ 6.2 5 MHz (LTE GSM: 20 W 3 MHz 15%–57% 15%–83%

MHz supports up to 1.2 LTE: 2 x 20
MHz of shared W
bandwidth.)
≥ 10 MHz 10 MHz (LTE GSM: 20 W 5 MHz 41%–98% 41%–

supports up to 2.4 LTE: 2 x 40 120%
MHz of shared W
bandwidth.)
≥ 15 MHz 15 MHz (LTE GSM: 20 W 10 MHz 18%–58% 18%–65%

supports up to 3.0 LTE: 2 x 40
MHz of shared W
bandwidth.)

MHz of shared W
bandwidth.)
Cell capacity = Number of available RBs in a cell x Spectral efficiency =

L.ChMeas.PRB.DL.Avail x ((L.Traffic.DL.SCH.QPSK.TB.bits + L.Traffic.DL.SCH.
16QAM.TB.bits + L.Traffic.DL.SCH.64QAM.TB.bits + L.Traffic.DL.SCH.
256QAM.TB.bits)/L.ChMeas.PRB.DL.Used.Avg/Statistical period/10^6)
The power configurations listed in Table 4-2 are typical power configurations, and the LTE
cell capacity gains can be achieved only when the power spectrum density (PSD) of GSM and
LTE meet the following requirements:
- When LTE uses a 5 MHz or 10 MHz bandwidth, the PSD difference between GSM and LTE
must be 10.5 dB.
- When LTE uses a 15 MHz bandwidth, the PSD difference between GSM and LTE must be
12.3 dB.
13.5 dB.
PSD difference between GSM and LTE = GSM power (dBm) – LTE power dBm@200 kHz
= GSM power (dBm) – LTE power (dBm) + 10 x lg(LTE bandwidth x 90% ÷ 0.2)
For example, if LTE uses a 5 MHz bandwidth and the power of each GSM TRX is 20 W, the
LTE power configuration must be 2 x 20 W to obtain the 10.5 dB PSD difference, which

SingleRAN
equals 10 x lg(20 W/1 mW) – 10 x lg(2 x 20 W/1 mW) + 10 x lg(5 x 90% ÷ 0.2). If the
power of each GSM TRX is 10 W, the LTE power configuration must be 2 x 10 W to obtain
the 11 dB PSD difference.
When the PSD difference between GSM and LTE is greater than the required value, the gain
provided by this function is smaller than those listed in Table 4-2 due to larger GSM
interference. Under these circumstances, the PSD difference must be within the range of
{Required PSD difference, Required PSD difference + 3 dB}. Otherwise, this function may
produce negative gains. When the PSD difference is smaller than the required value, the LTE-
to-GSM interference may increase, but the gain provided by this function is still within the
range listed in Table 4-2.
When GSM uses transmit diversity or LTE uses 4T4R to improve coverage performance,
operators must consider the impact of these functions on power when calculating the PSD
difference.
NOTE
l The gain offered by this function is the LTE capacity gain (that is, the capacity gain achieved after
this function is enabled, as compared with the capacity under the Adjacent Lower LTE Standard
Bandwidth). The GSM capacity remains unchanged. The lower limits of LTE capacity gains are
obtained in GSM peak hours when LTE uses only the LTE exclusive spectrum. The upper limit of
LTE capacity gains in the case of BCCH frequency sharing is achieved when GSM has no traffic,
requires only BCCHs and SDCCHs, and shares all other frequencies to LTE. The upper limit of LTE
capacity gains in the case of TCH frequency sharing is achieved when GSM uses only the spectrum
outside the LTE standard bandwidth and does not occupy the shared spectrum.
l When the shared GSM frequencies do not participate in frequency hopping (FH), GSM
preferentially occupies the spectrum far away from the LTE center frequency. When the shared GSM
frequencies participate in FH, GSM occupies discrete spectrum of the entire shared spectrum.
Assuming that the GSM service volume remains unchanged, the gain provided by this function is
larger when the shared GSM frequencies do not participate in FH, than when the shared GSM
frequencies participate in FH.
l When the communication link between the BSC and eNodeB is interrupted, the achievable gain is
close to the lower limit of the gain range.
4.2.2 Impacts
Network Impacts
l This function has the following impacts on GSM network performance:
– Circuit switched (CS) services
This function involves interference coordination and spectrum sharing between
GSM and LTE. Therefore, the GSM call setup delay, congestion rate, and call drop
rate may increase, and the high quality indicators (HQIs) and mean opinion scores
(MOSs) may decrease.
In this function, the service priorities of GSM exclusive carriers are higher than
those of GSM shared carriers. If the traffic loads of GSM exclusive carriers and
shared carriers change, the number of handovers in the GSM cell may increase.
– Packet switched (PS) services
When the GSM parameter GCELLGLSPECCLOUD.LTEMultiplexPDCHSw is
set to ON, the packet data channel (PDCH) resources of the shared frequencies can
always be multiplexed by LTE. Consequently, the PS service throughput may
decrease, and the call drop rate may increase.
l This function has the following impacts on LTE network performance:

SingleRAN
– When this function is enabled, strong in-band GSM interference exists. LTE UEs,
however, are unaware of the interference and perform processing in the same way
as before. In-band GSM interference affects LTE network performance more
adversely than out-of-band GSM interference. Due to in-band GSM interference,
the following occurs:
n The LTE access success rate and handover success rate decrease.
n The call drop rate increases.
n In-band GSM interference leads to inaccurate measurement results of LTE
quality-related counters that are measured over the full band. The counters, for
example, include the signal to interference plus noise ratio (SINR), reference
signal received quality (RSRQ), full-band channel quality indicator (CQI),
PMI, and rank indication (RI). The received signal strength indicator (RSSI)
and interference in the uplink increase. Therefore, it is recommended that
counters related to the modulation and coding scheme (MCS) or throughput be
used for performance evaluation.
– A proper PCI is planned to avoid the GSM interference on PCFICHs and PHICHs.
This increases the number of times PCIs are reused, as well as the probability of
PCI conflicts and confusion. The PDCCH demodulation performance compensation
algorithm increases the PDCCH overhead.
– When this function is enabled, the throughput of LTE UEs having compatibility
issues with this function will decrease to a certain extent. Therefore, an
intermediate- or small-scale test should be performed in heavy-traffic areas each
time before this function is put into a large-scale commercial use.
Function Impacts
RAT Function Function Reference Description
Name Switch
GSM Enhanced GBTS: Enhanced When the Enhanced

BCCH Power GCELLOTHE BCCH Power BCCH Power
Consumption XT.MAINBCC Consumption Consumption
Optimization HPWRDTEN Optimization Optimization function is
enabled, the calculated
eGBTS: interference level is
GLOCELLEN lower than the actual
ERGYMGTP value, affecting the
ARA.MAINBC interference estimation
CHPWRDTEN precision of the GSM
and LTE Spectrum
Concurrency function.
GSM Frequency GCELLMAG Frequency When enabled on GSM,

Hopping (RF RP.HOPMOD Hopping FH reduces the gain
hopping, E and provided by the GSM
baseband GCELLHOPT and LTE Spectrum
hopping) P.FHMODE Concurrency function.

SingleRAN

Name Switch
GSM BCCH Carrier GCELLFREQ. Frequency When enabled on GSM,

Frequency BCCHTRXHP Hopping FH reduces the gain
Hopping provided by the GSM
and LTE Spectrum
GSM Extended Cell GCELL.EXTT N/A The Extended Cell

P function applies only to
super-distance coverage
scenarios, where the
Concurrency function
can produce only a small
gain.
GSM BCCH Dense GCELLCHM BCCH Dense The BCCH Dense

Frequency GBASIC.TIG Frequency Frequency Multiplexing
Multiplexing HTBCCHSWI Multiplexing function causes a falsely
TCH high measured level in
neighboring cells. The
inaccurate measurement
results reduce the gain
provided by the GSM
and LTE Spectrum

SingleRAN

Name Switch
GSM IBCA II GCELLCHM IBCA II The GSM and LTE

GAD.IBCAAL Spectrum Concurrency
LOWED and function requires GSM
GCELLIBCAI time synchronization.
I.IBCAIIAllow The starting frames must
ed be strictly aligned
without any timeslot
difference among GSM
cells. IBCA II also
requires time
synchronization, and it
uses diversified
measures, including the
configuration of a bit
offset in the frames of the
BTS clock, for
interference reduction.
When the GSM and LTE
Spectrum Concurrency
function is used together
with IBCA II, the bit
offset in the frames of the
BTS clock cannot be
configured, and
consequently IBCA II
may produce smaller
gains than before.
GSM Intelligent GCELLOTHP Intelligent When IBIS is enabled,

BCCH ARA.BCCHInt BCCH the modulation scheme
Interference fSupSw Interference for signals transmitted
Suppression Suppression over idle timeslots on
(IBIS) (IBIS) BCCH carriers is
adjusted. This improves
the downlink quality for
voice services. However,
IBIS may affect the
measurement of
neighboring cells,
consequently affecting
the interference
estimation precision of
the GSM and LTE
function.

SingleRAN

Name Switch
FDD LTE Guardband N/A NB-IoT Basics When both GSM and
Deployment (FDD) NB-IoT are deployed on
the LTE guard band, they
must be deployed
sufficiently far away
from each other. It is
recommended that GSM
be preferentially
deployed on the LTE
guard band to achieve the
best possible overall
performance of LTE.
FDD LTE In-band N/A NB-IoT Basics When the GSM and LTE
Deployment (FDD) Spectrum Concurrency
function is deployed
together with NB-IoT,
operators must first
configure the GSM and
LTE Spectrum
and then reserve RBs for
NB-IoT. The RBs
reserved for NB-IoT
must be as far away from
GSM frequencies as
possible. Operators can
contact Huawei
engineers for assistance.

SingleRAN

Name Switch
FDD Mobility N/A Mobility When the GSM and LTE

Management Management in Spectrum Concurrency
Connected function is enabled, LTE
Mode cell-specific reference
signals (CRSs) are not
always transmitted.
Consequently, the
measured reference
signal received power
(RSRP) may be
inaccurate. The measured
RSSI used for RSRQ
calculation is affected by
GSM interference.
Therefore, the RSRQ,
which equals RSRP
divided by RSSI, may
deviate significantly
from the actual value. It
is recommended that the
RSRP rather than the
RSRQ be used when the
Concurrency function is
enabled.
FDD DL 2x2 MIMO N/A MIMO The SINR measured over

the full band is used for
FDD DL 4x2 MIMO N/A MIMO RI estimation. This SINR
FDD DL 4x4 MIMO N/A MIMO is lower than its actual
value due to GSM
interference.
Consequently, the
reported rank value is
lower than the actual
value.
FDD Extended CP Cell.ULCyclicP Extended CP This function reduces the

refix and gain provided by GSM
Cell.DlCyclicPr and LTE Spectrum
efix Concurrency. It is
recommended that these
two functions not be used
together.

SingleRAN

Name Switch
FDD LoCation ENodeBAlgoS LCS If positioning reference

Services (LCS) witch.LcsSwitc signals (PRSs) are
h configured as the pilot
signals, it is
recommended that the
PRS bandwidth be set to
a value smaller than the
cell bandwidth and that
the PRS configuration
index be set to a value to
avoid GSM interference.
FDD CPRI CELL.CPRICo CPRI CPRI Compression

Compression mpression Compression causes the LTE uplink
noise floor to increase.
When the compression
ratio is set to 2:1, CPRI
Compression has only a
small impact on the LTE
uplink noise floor. Larger
compression ratios lead
to greater impacts on the
LTE uplink noise floor.
Therefore, it is not
compression ratio be set
to 3:1 or 4:1 when this
function is enabled.
FDD Super SuperCombCe Super LTE shared RBs cannot

Combined Cell llSwitch option Combined Cell be used when the GSM
of the (FDD) and LTE Spectrum
CELLALGOS Concurrency function is
WITCH.SfnAl enabled in super
goSwitch combined cells.
parameter
FDD Inter-eNodeB RelaxedBackh Carrier Pre-scheduling can be

CA based on aulCaSwitch Aggregation performed up to 35 ms in
Relaxed option of the advance. When the time
backhaul ENodeBAlgoS of actual scheduling
witch.CaAlgoS arrives, the interference
witch parameter level may have changed,
and the pre-scheduling
decisions may be
inappropriate, affecting
the LTE network
throughput.

SingleRAN

Name Switch
FDD Static shared N/A 3D The GSM and LTE

beam Beamforming Spectrum Concurrency
(FDD) function affects channel
calibration and therefore
affects the performance
of static shared beam.
The GSM and LTE
function is not
recommended for cells
where static shared beam
is used.
FDD Precise AMC PreciseAmcSw eMIMO (FDD) The GSM and LTE
itch option of Spectrum Concurrency
the function affects the
CellAlgoSwitc accuracy of calculated
h.EmimoSwitc interference from
h parameter neighboring cells and
therefore affects the
performance of precise
AMC. If the shared RBs
account for a larger
proportion of the RBs in
the configured LTE
bandwidth, precise AMC
offers lower gains.
FDD GSM and LTE CellAlgoSwitc GSM and LTE When this function is
Dynamic Power h.GLPwrShare Dynamic Power enabled, the use of the
Sharing Sharing shared GSM power by
LTE may increase the
interference to GSM.
FDD eMTC EMTC_SWIT eMTC When an LTE cell uses a

Introduction CH option of 5 MHz bandwidth, the
the GSM and LTE Spectrum
CellEmtcAlgo. Concurrency function
EmtcAlgoSwitc cannot be used together
h parameter with enhanced Machine
Type Communication
(eMTC).
When the LTE cell uses a
10 MHz, 15 MHz, or 20
MHz bandwidth, the
simultaneous use of these
two functions decreases
the peak downlink
throughput of the eMTC.

SingleRAN

Name Switch
FDD Modulation N/A Modulation The in-band GSM

schemes Schemes interference leads to a
decrease in the LTE
SINR. The decreased
SINR may affect the
proportion of UEs using
64QAM or 256QAM and
the gain provided by
64QAM or 256QAM.
For example, the
downlink 256QAM is
decreased, reducing the
gain provided by
256QAM.
FDD SRS resource SRSCfg.SrsCfg Physical In high-speed railway

management Ind Channel scenarios, if the cell
Resource bandwidth is 10 MHz,
Management the cell-specific SRS
bandwidth is 24 RBs, the
UE-specific SRS
bandwidth is 4 RBs, and
the SRS period is 80 ms,
the maximum moving
speed can reach only 151
km/h. In other scenarios,
the maximum moving
speed can reach 300
km/h.
FDD Interference PuschIoTCtrlS Power Control This function applies

control for the witch option of only to scenarios where
PUSCH in the intra-RAT interference is
dynamic CellAlgoSwitc the major interference
scheduling h.UlPcAlgoSwi source on LTE networks.
mode tch parameter Therefore, it is not
recommended that this
function be used together
with the GSM and LTE
function.

SingleRAN

Name Switch
FDD Downlink FreqSelSwitch Scheduling The CQI quantization

frequency option of the precision of subbands is
selective CellAlgoSwitc limited. After the GSM
scheduling h.DlSchSwitch and LTE Spectrum
parameter Concurrency function is
enabled, the variance of
the subband CQIs
calculated by the eNodeB
decreases. Therefore, the
frequency selective
scheduling and the MCS
index decrease.
FDD NPREO CellDlpcPdsch Channel State When GSM and LTE

Constant Pa.CellNpreoA Management Spectrum Concurrency is
Optimization djThreshold or enabled, the accuracy of
CellDlpcPdsch neighboring cell
Pa.UeNpreoAdj interference calculation
Threshold is affected and the
performance of UE-level
NPREO constant
optimization is affected.
The larger the ratio of the
RBs shared by LTE and
GSM to the RBs in the
configured LTE
bandwidth, the lower the
gains of NPREO constant
optimization.

SingleRAN

Name Switch
FDD Downlink l CaDl5CCS Carrier The LTE cells enabled

Massive CA witch option Aggregation with GSM and LTE
of the Spectrum Concurrency
CaMgtCfg. are not recommended as
CellCaAlgo PCells. If these cells act
Switch as PCells, the PUCCH
parameter overhead is so large that
l UeBandCo SRSs cannot be
mbReduced configured.
R13Sw Consequently, the LTE
option of the network throughput
ENodeBAlg decreases.
oSwitch.Ca
AlgoExtSwit
ch
parameter
l DlMassiveC
aSwitch
option of the
CaMgtCfg.
CellCaAlgo
Switch
parameter
4.3 Requirements
4.3.1 Licenses
Feature Feature Name Model License Control NE Sales
ID Item Unit
MRFD- GSM and LTE LGMIGLS GSM and LTE BSC per Cell
130201 Spectrum C Spectrum
Concurrency Concurrency (GSM)
(GSM) (per Cell)
LGMIRFS RF Spectrum BSC/ per Band

SL Sharing License eGBTS per RU
(GSM)(per Band per
RU)
LGMIRFS Spectrum Sharing BSC/ per Band

SLWY License for 5000 eGBTS per RU
Series RF Module
(GSM)(per Band per
RU)

SingleRAN

ID Item Unit
MRFD- GSM and LTE LT1SGLSP GSM and LTE eNodeB per Cell
130221 Spectrum CONC Spectrum
Concurrency Concurrency (LTE
(LTE FDD) FDD)(per Cell)
LT1SRFSP RF Spectrum eNodeB per Band

CS00 Sharing License per RU
(FDD)(per Band per
RU)
LT1S5000 Spectrum Sharing eNodeB per Band

RFSS License for 5000 per RU
Series RF Module
(FDD)(per Band per
RU)
NOTE
When 5000 series RF modules are used, customers must purchase the Spectrum Sharing License for
5000 Series RF Module. When other RF modules are used, customers must purchase the RF Spectrum
Sharing License. When 5000 series RF modules and other RF modules are both used, customers must
purchase both hardware licenses.
4.3.2 Software
Prerequisite Functions
Name Switch
GSM BTS GPS N/A BTS GPS The interference from

Synchronizatio Synchronization GSM frequencies to the
n different REs or RBs of
LTE carriers requires
GSM Clock over IP N/A Synchronization precise calculation. To
Support perform this, timeslots
1588V2 must be aligned among
the TRXs of different
GSM cells. Therefore,
time synchronization
must be achieved on
GSM networks using one
of these functions.
This feature requires any
of the functions of BTS
GPS Synchronization,
Clock over IP support
1588V2, Soft-

SingleRAN

Name Switch
GSM Soft- GBTS: Soft- Synchronized Network,

Synchronized BTSOTHPAR Synchronized and BTS Supporting
Network A.SYNCMETH Network 1588v2 ATR. The BTS
OD and GPS Synchronization
BTSOTHPAR function is
A.AISSOP recommended. When the
Soft-Synchronized
eGBTS: Network function is
BTSOTHPAR enabled, one Global
A.SYNCMETH Positioning System
OD and (GPS) device must be
AISS.FLAG configured for every 20
to 30 BTSs.
GSM BTS Supporting N/A Synchronization
1588v2 ATR
Mutually Exclusive Functions

Name Switch
GSM GSM and LTE CELLGLDSS. GSM and LTE The GSM and LTE
FDD Dynamic GLDSSSw FDD Dynamic Spectrum Concurrency
Spectrum Spectrum function cannot be used
Sharing(GSM) Sharing together with this
function.
GSM GSM and LTE CELLGLDSS. GSM and LTE The GSM and LTE
Zero ZeroBufZoneS Zero Bufferzone Spectrum Concurrency
Bufferzone w function cannot be used
together with this
function.
GSM Satellite BTSTRANS.Tr Satellite The GSM and LTE

Transmission ansMode Transmission Spectrum Concurrency
over Abis function cannot be used
Interface together with this
function, as the BSL
delay cannot be ensured
when satellite
transmission is used.
FDD GSM and LTE GLDynSpectr GSM and LTE The GSM and LTE
FDD Dynamic umShareSwitc FDD Dynamic Spectrum Concurrency
Spectrum h option of the Spectrum function cannot be used
Sharing(LTE CellAlgoSwitc Sharing together with this
FDD) h.DynSpectrum function.
ShareSwitch
parameter

SingleRAN

Name Switch
FDD GSM and LTE GLZeroBuffer GSM and LTE The GSM and LTE
Zero ZoneSwitch Zero Bufferzone Spectrum Concurrency
Bufferzone option of the function cannot be used
CellAlgoSwitc together with this
h.DynSpectrum function.
ShareSwitch
parameter
FDD GSM and LTE AvoidGeranInt GSM and LTE The GSM and LTE
Buffer Zone erfSwitch Buffer Zone Spectrum Concurrency
Optimization option of the Optimization function cannot be used
h.AvoidInterfS function.
witch parameter
FDD UL Refarming AvoidUtranInt UL Refarming The GSM and LTE

Zero erfSwitch Zero Bufferzone Spectrum Concurrency
Bufferzone option of the function cannot be used
h.AvoidInterfS function on the same
witch parameter frequency band.
FDD CDMA and AvoidCDMAI CDMA and The GSM and LTE
LTE Zero nterfSwitch LTE Zero Spectrum Concurrency
Bufferzone option of the Bufferzone function cannot be used
h.AvoidInterfS function on the same
witch parameter frequency band.
FDD UMTS and LTE UL_SPECTR UMTS and LTE The GSM and LTE
Spectrum UM_SHARIN Spectrum Spectrum Concurrency
Sharing G option of the Sharing function cannot be used
SpectrumClou together with this
d.SpectrumClo function on the same
udSwitch frequency band.
parameter
FDD UMTS and LTE UMTS_LTE_Z UMTS and LTE The GSM and LTE
Zero ERO_BUFFE Zero Bufferzone Spectrum Concurrency
Bufferzone R_ZONE_SW function cannot be used
option of the together with this
ULZeroBuffer function on the same
zone.ZeroBufZ frequency band.
oneSwitch
parameter

SingleRAN

Name Switch
FDD UMTS and LTE DC_HSDPA_B UMTS and LTE The GSM and LTE
Spectrum ASED_UL_SP Spectrum Spectrum Concurrency
Sharing Based ECTRUM_SH Sharing Based function cannot be used
on DC-HSDPA R option of the on DC-HSDPA together with this
SpectrumClou function on the same
d.SpectrumClo frequency band.
udSwitch
parameter
FDD LTE FDD and LTE_NR_UPL LTE and NR GSM and LTE Spectrum
NR Uplink INK_SPECTR Spectrum Concurrency cannot be
Spectrum UM_SHR Sharing used together with the
Sharing option of the LTE FDD and NR
SpectrumClou Uplink Spectrum Sharing
d.SpectrumClo on the same frequency
udSwitch band.
parameter
FDD Compact Cell.Customize Compact The GSM and LTE

Bandwidth dBandWidthCf Bandwidth Spectrum Concurrency
gInd (FDD) function cannot be used
together with this
function.
FDD Flexible N/A Flexible The GSM and LTE

Bandwidth Bandwidth Spectrum Concurrency
based on based on function cannot be used
Overlap Overlap together with this
Carriers Carriers (FDD) function.
FDD Dynamic N/A 3D The GSM and LTE

dedicated beam Beamforming Spectrum Concurrency
(FDD) function cannot be used
together with this
function.
FDD Adaptive Inter- Activated using Adaptive ICIC The GSM and LTE
Cell the ACT Spectrum Concurrency
Interference AICIC function cannot be used
Coordination command on together with this
the function. This is because
eCoordinator this function requires the
eCoordinator.

SingleRAN

Name Switch
FDD eMBMS CellMBMSCfg eMBMS The GSM and LTE

.MBMSSwitch Spectrum Concurrency
function cannot be used
together with this
function. This is because
this function requires
transmission over the full
band whereas the GSM
and LTE Spectrum
does not support
transmission on the LTE
spectrum that overlaps
with the GSM spectrum.
FDD Inter-eNodeB Cell.EuCellSta SFN The GSM and LTE

SFN Based on ndbyMode Spectrum Concurrency
Coordinated function does not support
eNodeB inter-eNodeB single
frequency network (SFN)
cells.
FDD ePDCCH EpdcchFunctio Physical The GSM and LTE

nSwitch option Channel Spectrum Concurrency
of the Resource function cannot be used
CellPdcchAlgo Management together with this
.EpdcchAlgoSw function. This is because
itch parameter this function does not
support a non-standard
LTE bandwidth.
FDD PUSCH FH CellUlschAlgo. N/A The GSM and LTE

UlHoppingTyp Spectrum Concurrency
e function cannot be used
together with this
function.
FDD Intelligent SfCtrlAsScell N/A The GSM and LTE

subframe option of the Spectrum Concurrency
control in the CellUSParaCf function cannot be used
serving cell g.UsAlgoSwitc together with this
h parameter function.
FDD BBP L2LoadBalanc N/A The GSM and LTE

collaboration eSwitch option Spectrum Concurrency
of the function cannot be used
ENodeBAlgoS together with this
witch.BbpColla function.
borateSwitch
parameter

SingleRAN

Name Switch
FDD Static shared N/A Massive MIMO The GSM and LTE
beam (FDD) Spectrum Concurrency
together with this
function.
FDD Dynamic N/A Massive MIMO The GSM and LTE

dedicated beam (FDD) Spectrum Concurrency
together with this
function.
FDD Intelligent MM_INTELL Massive MIMO The GSM and LTE

Beam Shaping IGENT_BEA (FDD) Spectrum Concurrency
M_SHAPING_ function cannot be used
SW option of together with this
the function.
SectorSplitGro
up.SectorSplitS
witch parameter
FDD In-band relay N/A Relay The GSM and LTE

function cannot be
enabled together with in-
band relay. This is
because in-band relay
does not support non-
standard LTE
bandwidths. (Neither the
DeNB nor ReNB
supports GSM and LTE
Spectrum Concurrency.)
4.3.3 Hardware
l The BSC6900/BSC6910 service processing boards (XPUa/XPUb/XPUc/EGPUa/
EGPUb) support this function. If the average CPU load of the service processing boards
on the live network exceeds 50% before function deployment, new service processing
boards must be added.
l Huawei devices (including the BSC, BTS/eNodeB, U2020, and CME) running
SRAN13.1 or later versions must be used on the radio access network side.
l GSM and LTE must be deployed in 1:1 co-site and co-antenna mode.
l The transmission delay must be less than 70 ms. When this function is implemented on a
single BSC, the transmission delay equals the delay over the BSL. The delay over BSL
before feature activation can be obtained from Huawei engineers. When this function is
implemented across different BSCs, the transmission delay equals the sum of delay over
the Iur-g interface and BSL. The Iur-g delay before function activation can be obtained

SingleRAN
by performing the following operations: Connect BSCs by following the instructions

provided in Connection Inter BSC over IP Feature Parameter Description of GBSS
Feature Documentation. Observe the average delay over the Iur-g interface from the
source BSC to the target BSC through the BSC.IURG.AVR.DELAY.MEAN counter
(ID: 1282459444).
l The base station must be a GL co-MPT or GL separate-MPT multimode base station.
When GSM and LTE are served by different BBUs, these BBUs must be interconnected.
For details on how to interconnect two BBUs, see BBU Interconnection in 3900 & 5900
Series Base Station Product Documentation.
l The other hardware requirements are described in the table below.
Hardware Requirement
Main control l UMPT

boards l LMPT
l GTMUb/GTMUc (These boards do not support this function in
SingleOM scenarios.)
l BBU3910A/BBU3910C
Baseband l UBBPd: UBBPd1 to UBBPd6

processing l UBBPe: UBBPe1 to UBBPe4, and UBBPei
boards
l BBU3910A/BBU3910C
RF modules All RF modules that support GSM or LTE and the 850 MHz, 900
(RRUs/RFUs/ MHz, 1800 MHz, or 1900 MHz frequency band, excluding the
AAUs) DRFU, GRFU V1, GRFU V2, GRFU V2a, MRFU V1, MRFU V2,
MRFU V2a, RRU3004, RRU3008 V1, RRU3008 V2, RRU3908
V1, RRU3908 V2, RRU5204E, RRU5301, RRU5304w, RRU5309,
AAU3902, AAU5711a, AAU5973e, and AAU5972
Antenna 1T1R, 1T2R, 2T2R, 2T4R, and 4T4R

specifications
Base station Macro base stations (configured with the BBU3900, BBU3910,
types BBU3910A, or BBU5900)
NOTE
To prevent cell activation failures due to no baseband processing resources, cells enabled with this
function must be bound to baseband processing boards supporting this function. If cells are not
bound to such baseband processing boards, cell activation may fail when the baseband processing
boards supporting this function are fully occupied and other baseband processing boards do not
support this function.
4.3.4 Networking
RF Modules
l Before function deployment
If the LTE network is newly deployed on a frequency band, RF optimization must be
performed to prevent excessive cell coverage overlap from affecting network
performance. In addition, this function requires that GSM and LTE share the same

SingleRAN
antenna system. If the existing GSM and LTE networks do not share the same antenna
system, network reconstruction must be performed. Operators can contact Huawei
engineers to evaluate the impact of GSM and LTE co-antenna.
l After function deployment
– If the set of GSM interfering frequencies changes, the GSM interfering frequencies
must be reconfigured on the eNodeB side. Otherwise, LTE network performance is
affected. If the set of GSM interfering frequencies remains the same but the
frequencies configured for the involved GSM cell have changed, no reconfiguration
is required.
– In the case of site addition or deletion, cell RF parameter changes, co-coverage
relationship changes between GSM and LTE cells, or changes in interfering
neighboring cells of the GSM cell, reconfiguration must be performed.
– When an LTE multi-sector solution (2T6S or 4T6S) is used at the same time:
n If the multi-sector solution is implemented through combined RF modules and
multi-beam antennas, Multi-site Cell must be enabled on the GSM side (the
load-based FH set adaptation function must be disabled), and co-BCCH
networking is not supported.
n If the 2T6S multi-sector solution is implemented by the split of a 4T4R
module, 2T4R transmit diversity must be configured on the GSM side, and co-
BCCH networking is supported.
When a multi-sector solution is used on the LTE side, the co-coverage relationship
between GSM and LTE cells changes. Therefore, you need to replan and configure
related features. For details, contact Huawei engineers.
Spectrum
Frequency band
This function applies to the frequency bands supported by both GSM and LTE (850 MHz, 900
MHz, 1800 MHz, and 1900 MHz).
System bandwidth, the corresponding continuous spectrum, and shared spectrum
This function supports only LTE FDD 5 MHz, 10 MHz, 15 MHz, and 20 MHz bandwidths.
The uplink bandwidth must be the same as the downlink bandwidth. The continuous spectrum
and shared spectrum in each LTE FDD bandwidth scenario are as follows:
l LTE FDD 5 MHz bandwidth: At least a 6.2 MHz total bandwidth is required, the
continuous bandwidth must be at least 5 MHz, and LTE supports up to 1.2 MHz of
shared bandwidth. The following figure illustrates function application when these
requirements are met.

SingleRAN
l LTE FDD 10 MHz bandwidth: At least a continuous 10 MHz bandwidth is required, and
LTE supports up to 2.4 MHz of shared bandwidth. The following figure illustrates
function application when these requirements are met.

SingleRAN
GSM and LTE spectrum configuration

l The GSM frequencies that fall within LTE bandwidth are preferentially configured in the
LTE guard band. The GSM frequencies that cannot be configured in the LTE guard band
are configured using either of the following methods:
– Method 1: Symmetrically configure these GSM frequencies on both sides of the
LTE available bandwidth.
– Method 2: Configure these GSM frequencies on either side of the LTE available
bandwidth.
Method 2 provides a larger downlink capacity gain than method 1 does, but it also
decreases the uplink single-user throughput. In addition, when method 2 is used, the
RRC connection setup delay in a 5 MHz cell may be larger than that in a 3 MHz cell.
l If multiple LTE carriers operate in the same frequency band or different frequency bands
in the same area, the spectral efficiency can be maximized by allowing as many LTE
cells to use a standard bandwidth as possible. In this case, only one LTE carrier in the
area can use the shared GSM spectrum.
l If the GSM cell is configured with only one carrier and this carrier overlaps with the
effective LTE spectrum, to improve the LTE capacity gain, you are not advised to
configure static PDCHs on this GSM carrier.
l If the GSM frequencies that fall within the LTE bandwidth participate in FH, and if one
GSM frequency in the MA list is occupied, all GSM frequencies in the MA list are
considered occupied. Consequently, the LTE network capacity gain provided by this
function is affected.
l LTE PCIs must be planned in such a way that the interference from GSM frequencies
that fall within the LTE bandwidth is minimized. For details on PCI planning, contact
Huawei technical support.
l LTE PUCCHs, PRACHs, and SRSs must be configured on the LTE exclusive RBs that
are not interfered by GSM. When this function is deployed together with NB-IoT or
eMTC, NB-IoT or eMTC must be deployed on LTE exclusive RBs on the side of LTE
spectrum with fewer shared GSM frequencies. In addition, the following configuration
suggestions must be observed:
– When this function is deployed together with NB-IoT, the interference between NB-
IoT and LTE is lower than that between GSM and LTE. To achieve the best possible
overall performance of LTE, it is recommended that GSM be preferentially
deployed on the LTE guard band and that NB-IoT be deployed in standalone or LTE
in-band mode. When GSM shared frequencies are deployed only on one side of the
LTE guard band, NB-IoT can be deployed on the other side of the guard band. To
avoid interference between GSM and NB-IoT, a sufficient bandwidth must be
reserved between them.

SingleRAN
– When this function is deployed together with eMTC, the LTE 5 MHz bandwidth is
not supported. In the LTE 10 MHz bandwidth scenario, it is recommended that the
GSM frequencies that overlap with the LTE bandwidth be symmetrically configured
on both sides of the LTE bandwidth. If the GSM frequencies are asymmetrically
configured on the two sides of the LTE bandwidth, eMTC cell activation may fail
due to insufficient resources. In addition, the CellCeSchCfg.SiTransEcr parameter
for eMTC must be set to a value greater than or equal to 34, and the
CellCeSchCfg.PagingGroupNum parameter must be set to a value other than
FOURT or TWOT.
– When this function is deployed together with NB-IoT and eMTC, the LTE 5 MHz
bandwidth is not supported. In the LTE 10 MHz bandwidth scenario, it is
recommended that the GSM frequencies that overlap with LTE bandwidth be
symmetrically configured on both sides of the LTE bandwidth, and that NB-IoT be
deployed on the fifth eMTC narrowband.
Network Planning
This function can be enabled on the entire network or specific areas of the network.
l If the function is enabled on specific areas of the network, a buffer zone must be planned
to prevent co-channel interference between GSM and LTE. The method for planning the
buffer zone is the same as that for planning the buffer zone in GL refarming scenarios.
During buffer zone planning, operators must consider the spectrum resources of both
RATs. For more information, contact Huawei engineers.
l If the function is enabled on the entire network, the preceding planning is required.
NOTE
When this function is enabled in specific areas of the network, GSM and LTE co-channel interference
occurs on the shared spectrum if interference coordination is not implemented. This adversely affects
GSM and LTE network performance. If the interference is severe, the throughput may decrease, and
services may even fail to be initiated. In this case, a buffer zone is required between the GSM and LTE
sites on the same frequency band. To avoid mutual interference between GSM cells in the buffer zone
and LTE cells with this function enabled, this function must also be enabled in GSM cells in the buffer
zone.
4.3.5 Others
This function takes effect only when MRFD-130201 GSM and LTE Spectrum Concurrency
(GSM) and MRFD-130221 GSM and LTE Spectrum Concurrency (LTE FDD) are
simultaneously used.
4.4 Operation and Maintenance
4.4.1 When to Use

Recommended Application Scenarios
This function applies to scenarios where an LTE network must be deployed at the earliest time
possible or the capacity of an existing LTE network must be increased, but the GSM traffic
load is low and legacy GSM terminals on the live network will not exit the network within a
short period of time.
This function is not recommended if any of the following is true:

SingleRAN
l Indoor distributed base stations are deployed. In this scenario, the GSM-to-LTE
interference may be severe, causing significant service performance deterioration.
l The GSM configuration reduction analysis shows that GSM capacity requirements
cannot be met after GSM traffic is migrated from the frequency band where this function
is to be enabled, to other frequency bands or networks.
l High-speed or ultra-high-speed scenarios exist. Interference cannot be accurately
determined in these scenarios.
l The spectrum resource requirement of this function is not met. Specifically, the total
amount of spectrum resources is less than 6.2 MHz or the maximum amount of
continuous spectrum resources is less than 5 MHz.
Required Information
Before deploying this function, collect the live network data described in Table 4-3 as well as
the values of BSC and eNodeB counters listed in Table 4-4 and Table 4-5, to evaluate the
performance gains brought by this function.
You can use the function "Quickly Setting Performance Measurement by Feature" on the
U2020 to initiate measurement of counters associated with this function. For details, see
"Quickly Setting Performance Measurement by Feature" in U2020 MBB Network
Management System Product Documentation.
Table 4-3 Data to be collected

Category Data Objective
Engineering Site name, cell name, location area l To determine the area where
parameters code (LAC), cell identity (CI), this function is to be enabled.
longitude, latitude, antenna l To determine the co-coverage
azimuth/downtilt angle/antenna relationship between GSM and
height/gain, GSM frequency plan, LTE.
number of carriers, transmit
power, and whether the site is an l To plan the interfering
indoor site neighbor relationship between
GSM and LTE cells, together
with performance counters of
neighboring GSM cells and
configuration files.
Configuration BSC and eNodeB configuration l To plan the interfering

files files neighbor relationship between
GSM and LTE cells, together
with performance counters of
neighboring GSM cells and
engineering parameters.
l To check whether the related
functions are enabled or
disabled as required.

SingleRAN
Category Data Objective
Transmission Transmission mode, bandwidth, l To determine the current

resources and delay transmission network
conditions, together with the
BSC configuration file and
value of the
BSC.IURG.AVR.DELAY.ME
AN counter (ID: 1282459444).
l To determine whether the
transmission network needs to
be upgraded or reconstructed
based on the current
transmission network
conditions, as well as the
requirements of this function
for the transmission mode,
transmission bandwidth, and
transmission delay.
Performance GSM and LTE performance l To determine whether a cell

counters counters used in routine meets the function deployment
monitoring, which are listed in requirements. Performance
Table 4-4 and Table 4-5 counters together with
engineering parameters help
determine the area where this
function is to be enabled.
l To evaluate the impact of this
function on GSM network
performance and the gain in
LTE network capacity.
Hardware Information about main control To determine whether hardware

boards, baseband processing replacement or reconstruction is
boards, RF modules, and service required, together with the
processing boards hardware requirements of this
function.
Table 4-4 BSC performance counters to be collected
Counter ID Counter Name Counter Description
1278087422 CELL.KPI.SD.TRAF.ERL K3004:Traffic Volume on SDCCH
1278087430 CELL.KPI.TCH.ASS.REQ.TRA K3010A:TCH Seizure Requests

F (Traffic Channel)
1278087434 CELL.KPI.TCH.HO.REQ.TRA K3010B:TCH Seizure Requests in

F TCH Handovers (Traffic Channel)
1278087432 CELL.KPI.TCH.ASS.SUCC.TR K3013A:Successful TCH Seizures

AF (Traffic Channel)

SingleRAN
1278087436 CELL.KPI.TCH.HO.SUCC.TR K3013B:Successful TCH Seizures

AF in TCH handovers (Traffic
Channel)
1278087438 CELL.KPI.TCH.TRAF.ERL.TR K3014:Traffic Volume on TCH

AF
1278087425 CELL.KPI.TCH.REQ.SIG K3020:TCH Seizure Requests

(Signaling Channel)
1278087427 CELL.KPI.TCH.SUCC.SIG K3023:Successful TCH Seizures

(Signaling Channel)
1278075461 CELL.IMM.ASS.REQ CA300J:Channel Requests

(Circuit Service)
1278075462 CELL.IMM.ASS.SUCC CA303J:Call Setup Indications

(Circuit Service)
1278076504 CELL.ASS.SUCC CA313:Successful Assignments
1282448080 CELL.INTRABSC.OUTCELL. CH3109A:Number of Outgoing

HO.REQ.TCH Internal Inter-Cell Handover
Requests(TCH)
1282448082 CELL.INTRABSC.OUTCELL. CH3129A:Number of Failed

HO.FAIL.TCH Outgoing Internal Inter-Cell
Handovers(TCH)
1282448074 CELL.INTRABSC.INCELL.HO CH3209A:Number of Incoming

.REQ.TCH Internal Inter-Cell Handover
Requests (TCH)
1282448076 CELL.INTRABSC.INCELL.HO CH3229A:Number of Failed

.FAIL.TCH Incoming Internal Inter-Cell
Handovers(TCH)
1282448083 CELL.INTERBSC.OUTCELL. CH3309A:Number of Outgoing

HO.REQ.TCH External Inter-Cell Handover
Requests(TCH)
1282448085 CELL.INTERBSC.OUTCELL. CH3329A:Number of Failed

HO.FAIL.TCH Outgoing External Inter-Cell
Handovers(TCH)
1282448077 CELL.INTERBSC.INCELL.HO CH3409A:Number of Incoming

.REQ.TOTAL.TCH External Inter-Cell Handover
Requests(TCH)
1282448079 CELL.INTERBSC.INCELL.HO CH3429A:Number of Failed

.FAIL.TCH Incoming External Inter-Cell
Handovers(TCH)
1278072498 CELL.TRAF.CH.CALL.DROPS CM33:Call Drops on Traffic

Channel

SingleRAN
1278288417 TRX.FR.DOWN.RX.QLTY. NCS412A:Number of MRs on

0.NEW Downlink TCHF (Receive Quality
Rank 0)
1278288418 TRX.FR.DOWN.RX.QLTY. NCS412B:Number of MRs on

Rank 1)
1278288419 TRX.FR.DOWN.RX.QLTY. NCS412C:Number of MRs on

Rank 2)
1278288420 TRX.FR.DOWN.RX.QLTY. NCS412D:Number of MRs on

Rank 3)
1278288421 TRX.FR.DOWN.RX.QLTY. NCS412E:Number of MRs on

Rank 4)
1278288422 TRX.FR.DOWN.RX.QLTY. NCS412F:Number of MRs on

Rank 5)
1278288423 TRX.FR.DOWN.RX.QLTY. NCS412G:Number of MRs on

Rank 6)
1278288424 TRX.FR.DOWN.RX.QLTY. NCS412H:Number of MRs on

Rank 7)
1278288425 TRX.FR.UP.RX.QLTY.0.NEW NCS413A:Number of MRs on

Uplink TCHF (Receive Quality
Rank 0)
1278288426 TRX.FR.UP.RX.QLTY.1.NEW NCS413B:Number of MRs on

Rank 1)
1278288427 TRX.FR.UP.RX.QLTY.2.NEW NCS413C:Number of MRs on

Rank 2)
1278288428 TRX.FR.UP.RX.QLTY.3.NEW NCS413D:Number of MRs on

Rank 3)
1278288429 TRX.FR.UP.RX.QLTY.4.NEW NCS413E:Number of MRs on

Rank 4)

SingleRAN
1278288430 TRX.FR.UP.RX.QLTY.5.NEW NCS413F:Number of MRs on

Rank 5)
1278288431 TRX.FR.UP.RX.QLTY.6.NEW NCS413G:Number of MRs on

Rank 6)
1278288432 TRX.FR.UP.RX.QLTY.7.NEW NCS413H:Number of MRs on

Rank 7)
1278288433 TRX.HR.DOWN.RX.QLTY. NCS414A:Number of MRs on

0.NEW Downlink TCHH (Receive Quality
Rank 0)
1278288434 TRX.HR.DOWN.RX.QLTY. NCS414B:Number of MRs on

Rank 1)
1278288435 TRX.HR.DOWN.RX.QLTY. NCS414C:Number of MRs on

Rank 2)
1278288436 TRX.HR.DOWN.RX.QLTY. NCS414D:Number of MRs on

Rank 3)
1278288437 TRX.HR.DOWN.RX.QLTY. NCS414E:Number of MRs on

Rank 4)
1278288438 TRX.HR.DOWN.RX.QLTY. NCS414F:Number of MRs on

Rank 5)
1278288439 TRX.HR.DOWN.RX.QLTY. NCS414G:Number of MRs on

Rank 6)
1278288440 TRX.HR.DOWN.RX.QLTY. NCS414H:Number of MRs on

Rank 7)
1278288441 TRX.HR.UP.RX.QLTY.0.NEW NCS415A:Number of MRs on

Uplink TCHH (Receive Quality
Rank 0)
1278288442 TRX.HR.UP.RX.QLTY.1.NEW NCS415B:Number of MRs on

Rank 1)

SingleRAN
1278288443 TRX.HR.UP.RX.QLTY.2.NEW NCS415C:Number of MRs on

Rank 2)
1278288444 TRX.HR.UP.RX.QLTY.3.NEW NCS415D:Number of MRs on

Rank 3)
1278288445 TRX.HR.UP.RX.QLTY.4.NEW NCS415E:Number of MRs on

Rank 4)
1278288446 TRX.HR.UP.RX.QLTY.5.NEW NCS415F:Number of MRs on

Rank 5)
1278288447 TRX.HR.UP.RX.QLTY.6.NEW NCS415G:Number of MRs on

Rank 6)
1278288448 TRX.HR.UP.RX.QLTY.7.NEW NCS415H:Number of MRs on

Rank 7)
1279270427 AVR.OCCU.PDCH AR9311:Average Number of

Occupied PDCHs
1278476438 CELL.RATE.SD.CONG RR370:Congestion Rate on

SDCCH per CELL (due to Busy)
1278087448 CELL.KPI.TCH.CONGESTIO K3045:Congestion Rate on TCH

N.RATE (All Channels Busy)
1278072594 CELL.RATE.TCH.CALL.DRO ZTR304:Call Drop Rate on TCH

P.INCLUDE.HO per cell(including Handover)
1278072595 CELL.RATE.TCH.CALL.DRO ZTR304A:Call Drop Rate on TCH

P.EXCLUDE.HO per cell(Excluding Handover)
1278075470 CELL.ESTB.IND.SUCC.RATE. RA303G:Success Rate of

IMM.ASS Immediate Assignments
1278076505 CELL.ASS.SUCC.RATE RCA313:Assignment Success

Rate
1278078483 CELL.HO.SUCC.RATE RH303:Handover Success Rate
1278078484 CELL.RD.HO.SUCC.RATE RH303A:Success Rate of Radio

Handover

SingleRAN
Table 4-5 eNodeB performance counters to be collected

1526728433 L.ChMeas.PRB.DL.Avail Number of available downlink

PRBs
1526726740 L.ChMeas.PRB.DL.Used.Avg Average number of used PDSCH

PRBs
1526728434 L.ChMeas.PRB.UL.Avail Number of available uplink PRBs
1526726737 L.ChMeas.PRB.UL.Used.Avg Average number of used uplink

PRBs
1526727483 L.ChMeas.PRB.PUCCH.Avg Average number of used PRBs

over the PUCCH
1526728259 L.Thrp.bits.UL Total uplink traffic volume for

PDCP PDUs in a cell
1526728998 L.Thrp.Time.Cell.UL.HighPreci Total duration of uplink data

sion transmission in a cell (with the
precision of 1 ms)
1526729415 L.Thrp.bits.UE.UL.SmallPkt Uplink traffic volume of PDCP

PDUs scheduled for small packets
1526729416 L.Thrp.Time.UE.UL.RmvSmall Uplink data transmission duration

Pkt except that for small packets
1526728261 L.Thrp.bits.DL Total downlink traffic volume for

PDCP SDUs in a cell
1526728997 L.Thrp.Time.Cell.DL.HighPreci Total duration of downlink data

sion transmission in a cell (with the
precision of 1 ms)
1526729005 L.Thrp.bits.DL.LastTTI Downlink traffic volume sent in

the last TTI for PDCP SDUs
before the buffer is empty
1526729015 L.Thrp.Time.DL.RmvLastTTI Data transmit duration except the

last TTI before the downlink
buffer is empty
1526728299 L.ChMeas.PDCCH.SymNum.1 Number of times the PDCCH

occupies one symbol in a
measurement period

occupies two symbols in a
measurement period

occupies three symbols in a
measurement period

SingleRAN

occupies four symbols in a
measurement period
4.4.2 Data Configuration

It is recommended that this function be activated when traffic is light, for example, in the
early morning. This is because reconfigurations are required during function activation, which
causes LTE cells to reset.
4.4.2.1 Data Preparation
On the GSM Side

Table 4-6 and Table 4-7 describe the parameters used for function activation and
optimization, respectively. This section does not describe parameters related to cell
establishment.
Table 4-6 Parameters used for activation
Parameter Parameter ID Setting Notes

Name
GSM and LTE GCELLGLSPECCLOUD.G Set this parameter to ON in GSM cells

Spectrum LSpecConcurSw that require this function.
Concurrency
Switch
GSM and LTE GCELLGLSPECCLOUD.G Set this parameter to ADAPTIVE in

DL Spectrum LDLSpectrumShareUnit GSM cells that require this function.
Sharing Unit
DL Central LTE GCELLGLSPECCLOUD.L Set this parameter according to actual

ARFCN TEDLCenterFreq conditions on the LTE network.
LTE Bandwidth GCELLGLSPECCLOUD.L Set this parameter according to actual

TEBandwidth conditions on the LTE network.
Freq. Band DL GCELLGLSPECCLOUD.P Set this parameter to the coverage level

Coverage Level riSecFreDLCoverLevGap difference between the primary and
Difference secondary frequency bands of a co-
BCCH cell. This parameter needs to be
set only when this function is used
together with the Co-BCCH Cell
function.
Cell Index GCELLGLCOCOVER.CE Set this parameter based on the GSM

LLID and LTE cell co-coverage relationship.

SingleRAN

Name
LTE Cell MNC GCELLGLCOCOVER.LTE Set this parameter based on the GSM
MNC and LTE cell co-coverage relationship.
LTE Cell MCC GCELLGLCOCOVER.LTE Set this parameter based on the GSM
MCC and LTE cell co-coverage relationship.
LTE Cell GCELLGLCOCOVER.LTE Set this parameter based on the GSM

Identity CI and LTE cell co-coverage relationship.
LTE Cell Sector GCELLGLCOCOVER.LTE Set this parameter based on the GSM
ID SectorID and LTE cell co-coverage relationship.
Neighbor Cell G2GNCELL.NCELLSCETY Select the

Scenario Type PE GLMEASNEIGHBORCELL option
of this parameter when there is
interference relationship between a
neighboring GSM cell and an LTE cell
that has the same coverage as the GSM
serving cell.
Neighboring G2GNCELL.NCELLTYPE Keep this parameter value unchanged if

Cell Type it is HANDOVERNCELL,
IBCANCELL, or
HANDOVERANDIBCANCELL
before function activation.
If the neighboring cell is none of the
preceding cells and interference occurs
between this neighboring cell and the
LTE cell, set this parameter to NONE.
BSC Index EXTBSC.BSCIDX Set this parameter to the index of the

BSC serving external neighboring
GSM cells.
External BSC EXTBSC.BSCNAME Set this parameter to the name of the

Name BSC serving external neighboring
GSM cells.
External BSC EXTBSC.BSCDPC If the cell that requires this function

DPC and some cells served by an external
BSC are mutually interfering
neighboring cells, this parameter is
mandatory. If this parameter is not set
under these circumstances, function
gains will be affected.
Iur-g Delay EXTBSC.IurgDelayMeasur- If the cell that requires this function

Measure Switch eSw and some cells served by the external
BSC are mutually interfering
neighboring cells, set this parameter to
ON.

SingleRAN

Name
BSC Index EXTBSCCONN.BSCIDX Set this parameter to the index of the

BSC serving external neighboring cells.
SCTP Link ID EXTBSCCONN.SCTPLNKI Set this parameter to the SCTP link ID

D used by the external BSC.
BTS Index BTSBSL.BTSID Set this parameter according to the

transport network plan.
BTS Name BTSBSL.BTSNAME Set this parameter according to the

transport network plan.
BSL Index BTSBSL.BSLIndex The BSC automatically numbers the

BSL index. You can also set this
parameter based on the network plan.
BSL Service BTSBSL.BSLSrvType Set this parameter to LTE.

Type
Table 4-7 Parameters used for optimization

Name
GL RX Level GCELLGLSPECCLOUD.G It is recommended that this parameter

Gap Thd for LRxLevelGapThd be set to its recommended value. When
Timeslot GSM KPIs such as low quality
Multiplexing indicators (LQIs) and the TCH call
drop rate significantly increase, set this
parameter to a larger value. This makes
it difficult for LTE to multiplex GSM
shared frequencies, reducing the
interference from LTE to GSM. If this
parameter is set too large, LTE can
multiplex only a small number of GSM
shared frequencies. This does not help
improve spectrum utilization and LTE
network capacity.
Multi-RAT GCELLCHMGBASIC.Mult Whether to enable the multi-RAT

Scheduling iRatScheduManagSW scheduling management function, so as
Management to support flexible channel allocation
Switch policies for preferentially guaranteeing
GSM, UMTS, or LTE network
performance gains based on the service
and KPI requirements. For details, see
the description of multi-RAT
scheduling management in Channel
Management in GBSS Feature
Documentation.

SingleRAN

Name
Intra-Freq. Cell GCELLGLSPECCLOUD.I It is recommended that this parameter

Interference ntraFreqNeighbCellCoordSw be set to OFF in non-FH scenarios.
Coordination Under these circumstances, the BSC
does not consider the interference
caused by LTE to intra-frequency
neighboring cells, improving LTE
network capacity. When GSM
frequencies join in FH or GSM
network performance needs to be
preferentially ensured, it is
recommended that this parameter be set
to ON.
LTE Multiplex GCELLGLSPECCLOUD.L If LTE capacity improvement is

PDCH Switch TEMultiplexPDCHSw required, GSM PS traffic load is light,
and the requirements for PS
performance counters are low, it is
to ON, and that the
GCELLPRIVATEOPT-
PARA.PSDTX parameter be set to
DTX. Setting this parameter to ON
may reduce the GSM PS throughput
and increase the call drop rate. In
addition, LTE directly multiplexes
PDCHs, regardless of whether PDCHs
suffer from interference. If the GSM PS
traffic load is high, the LTE throughput
may decrease due to GSM interference.

SingleRAN

Name
PS UL Load GCELLGLSPECCLOUD.P When GSM shared carriers are TCH

Threshold sUlLoadThd carriers, optimize the TCH allocation
scheme by adjusting the value of this
parameter. This parameter must be set
based on the uplink PS traffic volume.
l When GBFD-113101 PDCH
Dynamic Adjustment is enabled, set
this parameter to a value greater
than that of the
GCELLPSCHM.UPDYNCHNTR
ANLEV parameter.
l When GBFD-119408 PS Access
Congestion Balancing is enabled, it
is recommended that this parameter
be set to a value either 1 or 2
smaller than that of the
GCELLPSCHM.RadioResAdaAdj
UlLoadThd parameter.
l When GBFD-511611 Duty-Cycle-
based PDCH Management is
enabled, it is recommended that this
parameter be set to a value either 1
or 2 smaller than that of the
GCELLPSCHM.UPDYNCHNTR
ANLEV parameter.

SingleRAN

Name
PS DL Load GCELLGLSPECCLOUD.P When GSM shared carriers are TCH

Threshold sDlLoadThd carriers, optimize the TCH allocation
scheme by adjusting the value of this
parameter. This parameter must be set
based on the downlink PS traffic
volume.
l When GBFD-113101 PDCH
Dynamic Adjustment is enabled:
– It is recommended that this
parameter be set to a value
greater than that of the
GCELLPSCHM.DWNDYNCH
NTRANLEV parameter.
– Set this parameter to a value
either 1 or 2 smaller than that of
the
GCELLPSCHM.PSServiceBus
yThreshold parameter.
l When GBFD-119408 PS Access
Congestion Balancing is enabled, it
is recommended that this parameter
be set to a value either 1 or 2
smaller than that of the
GCELLPSCHM.RadioResAdaAdj
DlLoadThd parameter.
l When GBFD-511611 Duty-Cycle-
based PDCH Management is
enabled, it is recommended that this
parameter be set to a value either 1
or 2 smaller than that of the
GCELLPSCHM.DWNDYNCHNT
RANLEV parameter.
Shared Freq. GCELLGLSPECCLOUD.S When GSM shared carriers are TCH

Receive Level haredFreqRxLevThld carriers, optimize the TCH allocation
Threshold scheme by adjusting the value of this
parameter. This parameter is set based
on the distribution of downlink receive
level of CS services. It is recommended
that this parameter be set to 30.

SingleRAN

Name
Dedicated Freq. GCELLGLSPECCLOUD.D When GSM shared carriers are TCH

HR Allocation edFreqHrAlloLdThldOffset carriers, optimize the TCH allocation
Load Thld scheme by adjusting the value of this
Offset parameter. This parameter is set based
on the GSM traffic volume. When the
GSM traffic volume is high, it is
to 0. Operators can also set this
parameter to a non-zero value when the
LTE network throughput needs to be
improved.
Optimized GCELLGLSPECCLOUD.S When the large interference from LTE

Spectrum pecmConcurHoOptSw to GSM significantly affects the GSM
Concurrency handover success rate, set this
HO Switch parameter to ON to allow GSM non-
better-cell handovers. This reduces the
probability of handover failures.
Non- GCELLGLSPECCLOUD.N It is recommended that this parameter

Interference oninterfStateStatTime be set to 6.
State Statistic
Time
Non- GCELLGLSPECCLOUD.N It is recommended that this parameter

Interference oninterfStateLastTime be set to 4.
State Last Time

SingleRAN

Name
III Power GCELLPWR3.PWRCTRLO When GSM shared carriers are TCH

Control PTIMIZEDEN carriers and interfered by LTE, reduce
Optimized the interference by adjusting GSM
Enable power control parameters. That is, set
this parameter to YES. In the coverage
area served by co-sited GSM and LTE
base stations, LTE networks impose
severe co-channel interference on GSM
networks. The GSM downlink power
control algorithm takes three
measurement report periods
(approximately 1.44s) from command
delivery to execution whereas the LTE
RB scheduling period is 1 ms.
Therefore, the GSM power control
algorithm does not reflect the
interference from LTE networks to
GSM networks and intra-RAT
interference. To accurately reflect the
interference, set power control-related
parameters as follows:
l Set
GCELLPWR3.DLREXLEVADJF
CTR to 2.
l Set
GCELLPWR3.DLREXQUALADJ
FCTR to 8.
l Set
GCELLPWR3.DLMAXDOWNST
EP to 2.
l Set
GCELLPWR3.DLMAXUPSTEP
to 8.
l Set
GCELLPWR3.DLRXLEVPROTE
CTFACTOR to 5.
l Set
GCELLPWR3.DLRXQUALPROT
ECTFACTOR to 85.
l Set GCELLPWR3.DLADJPRD to
1.
l Set
GCELLPWR3.DLREXQUALEXP
FLTLEN to 1.
l Set
GCELLPWR3.DLREXLEVEXPF
LTLEN to 1.

SingleRAN

Name
l Set
GCELLPWR3.DLFILTADJFACT
OR to 9.
l Set
GCELLPWR3.DlMaxDownOptiS
w to ON.
l Set
GCELLPWR3.MAXBTSPWRNU
M to 8.
CS RACH Min. GCELLCCACCESS.RACH When the interference from GSM to

Access Level ACCLEV LTE uplink is too large, adjust the
values of these parameters. These two
PS RACH Min. GCELLCCACCESS.PSRA parameters must be appropriately set.
Access Level CHACCLEV Otherwise, GSM coverage shrinks.
GAMMA GCELLPSPWPARA.GAM You are advised to use the

MA recommended value of this parameter.
ALPHA GCELLPSPWPARA.ALPH You are advised to use the

A recommended value of this parameter.
PBGT Watch G2GNCELL.PBGTSTAT When fast handovers are required to

Time reduce the interference from LTE to
GSM, set the following parameters for
PBGT Valid G2GNCELL.PBGTLAST GBFD-110601 HUAWEI I Handover
Time and GBFD-510501 HUAWEI II
Level Penalty G2GNCELL.NCELLPUNL Handover: The recommended
Value on EV parameter settings are as follows:
Neighboring l Set G2GNCELL.PBGTSTAT to 4.
Cell l Set G2GNCELL.PBGTLAST to 3.
Filter Length GCELLHOFITPEN.DATAS l Set G2GNCELL.NCELLPUNLEV
for TCH Level TRFLTLEN to 0.
l Set
Filter Length GCELLHOFITPEN.DATA GCELLHOFITPEN.DATASTRF
for TCH Qual QUAFLTLEN LTLEN to 2.
Filter Length GCELLHOFITPEN.NCEL l Set
for Ncell LFLTLEN GCELLHOFITPEN.DATAQUAF
RX_LEV LTLEN to 2.
l Set
GCELLHOFITPEN.NCELLFLT
LEN to 2.

SingleRAN

Name
Intracell HO GCELLHOBASIC.INTRAC If GBFD-510501 HUAWEI II

Allowed ELLHOEN Handover has been enabled on the
GSM side, it is recommended that this
parameter be set to YES on the BSC.
When many UEs are handed over from
shared carriers to exclusive carriers at
the same time, the handover failure rate
increases due to insufficient channels
on exclusive carriers. If a handover
fails, the UE will attempt to perform
another one. Consequently, the number
of intra-cell handovers increases.
On the LTE Side

establishment.

Name
Spectrum Cloud SpectrumCloud.SpectrumCl Set this parameter to

Switch oudSwitch GL_SPECTRUM_CONCURRENC
Y in LTE cells that require this
function.
Co-coverage SpectrumCloud.CoCovGsm Set this parameter to the power of the

GSM Sharing SharingCarrierPwr sharing carrier in a co-coverage GSM
Carrier Power cell. If multiple sharing carriers exist in
a co-coverage GSM cell, set this
parameter based on the carrier with the
largest power.
GSM ARFCN SpectrumCloud.GsmArfcnG Set this parameter based on the

Group ID roupId operator's network plan.
GSM ARFCN GsmInterfArfcnCfg.GsmArf Set this parameter based on the

Group ID cnGroupId operator's network plan.

SingleRAN

Name

cn operator's network plan. For the 5
MHz, 10 MHz, 15 MHz, or 20 MHz
standard LTE bandwidth, an ARFCN
group contains a maximum of 6, 22,
25, or 25 shared ARFCNs, respectively.
Ensure that the configured GSM
ARFCNs are the same as the GSM
ARFCNs in use. Otherwise, there may
be interference in the LTE uplink
control channel, affecting LTE network
performance. When NB-IoT is
deployed in in-band mode, NB-IoT
functions may be affected.
Inter RAT Link GlobalProcSwitch.InterRatL Select the

Setup Switch inkSetupSwitch BTS_ENODEB_LINK_SETUP_SWI
TCH option of this parameter before
configuring the BSL on the BSC.
Otherwise, ALM-21840 BSL Fault
may be reported on the BSC side.
PRACH RACHCfg.PrachFreqOffset- Set this parameter to

Frequency Strategy FULLY_AUTOMATIC.
Offset Strategy
SRS ACK/ SRSCfg.AnSrsSimuTrans Set this parameter to

NACK BOOLEAN_TRUE.
simultaneous
transmission
Non-Standard CellAlgoSwitch.NonStandar Select the

Bandwidth dBwAlgoSw PUCCH_SRS_ADAPT_SWITCH
Algorithm option of this parameter.
Switch
PUCCH CellAlgoSwitch.PucchAlgoS Select the PucchSwitch option of this

algorithm witch parameter.
switch

Name
DL schedule CellAlgoSwitch.DlSchSwitch Select the EnAperiodicCqiRptSwitch

switch option of this parameter.

SingleRAN

Name
CQI Adjust CellAlgoSwitch.CqiAdjAlgo Select the RptCqiFltInitSwitch,

Algorithm Switch AdaptiveStepVarySwitch, and
Switch PreciseMcsAdaptSwitch options of
this parameter.
Uplink schedule CellAlgoSwitch. Select the SchedulerCtrlPowerSwitch

switch UlSchSwitch option of this parameter.
FD UE CellDlschAlgo.FDUEEnhAp It is recommended that this parameter

Enhanced erCQITrigPeriod be set to 40ms.
Aperiodic CQI
Trigger Period
RB Damage CellDlschAlgo.RBDamageN It is recommended that this parameter

Cell Near Point earPointIblerTh be set to 80.
User IBLER
Thd
PDCCH CellPdcchAlgo.PdcchCapaci The value ON is recommended.

Capacity tyImproveSwitch
Improve Switch
PDCCH Power CellPdcchAlgo.PdcchPower The value ON is recommended.

Enhanced EnhancedSwitch
Switch
PDCCH Max CellPdcchAlgo.PdcchMaxCo The value 75 is recommended.

Code Rate deRate
PDCCH Out CellPdcchAlgo.PdcchOutLo The value –20 is recommended.

Loop opAdjLowerLimit
Adjustment
Value Lower
Thld
PHICH PHICHCfg.PhichDuration The value NORMAL is recommended.

duration
PHICH PHICHCfg.PhichResource The value ONE is recommended.

resource
Admission CellRacThd.AcUserNumber When the adaptive PUCCH and SRS

Control User resource allocation function is enabled,
Number the setting of this parameter affects the
maximum number of UEs that can be
admitted to a cell, as well as PUCCH
resource allocation. A larger parameter
value indicates that more PUCCH
resources are allocated. A smaller
parameter value indicates that less
PUCCH resources are allocated.

SingleRAN

Name
Format3 RB PUCCHCfg.Format3RbNum Set these parameters to values less than

Number their recommended values in CA
scenarios if the adaptive PUCCH and
Max 2CC ACK PUCCHCfg.Max2CCAckCh SRS resource allocation function is
Channel Num enabled and the resources occupied by
Number the PUCCH still need to be reduced.
The smaller the value of the
PUCCHCfg.Format3RbNum
parameter, the less the number of CA
UEs sending HARQ-ACKs over the
PUCCH format 3 are scheduled in a
single TTI. The smaller the value of the
PUCCHCfg.Max2CCAckChNum
parameter, the less the number of 2CC
CA UEs using the current cell as the
PCell are scheduled in a single TTI.
Measurement CellResel.MeasBandWidth To improve the handover success rate

bandwidth of LTE cells, it is recommended that
the measurement bandwidth for intra-
Measurement EutranInterNFreq.MeasBan frequency handovers and that for inter-
bandwidth dWidth frequency handovers be both set to the
adjacent lower LTE standard
bandwidth.
Near Point User SpectrumCloud.NearPointU When LTE cell center users (CCUs)
Path Loss serPathLossThld suffer from strong GSM interference in
Threshold the uplink, it is recommended that the
value of this parameter be decreased to
reduce the probability of identifying a
UE as a CCU.

SingleRAN

Name
LTE SpectrumCloud.InterfPfmO l It is recommended that the

Interference ptSwitch DL_PFM_PRF_PDCCH_SWITC
Performance H option of this parameter be
Optimize selected when LTE downlink
Switch performance needs to be ensured.
This switch is valid only when
CellPdcchAlgo.PdcchSymNumSwi
tch is not set to OFF or when
CellPdcchAlgo.CceRatioAdjSwitch
is set to ON. When the
DL_PFM_PRF_PDCCH_SWITC
H option is selected, the
CellAlgoSwitch.SfnUlSchSwitch
parameter cannot be set to
ADAPTIVE, that is, uplink ASFN
cannot be enabled.
l When LTE cell edge users (CEUs)
suffer from strong GSM
interference in the downlink, it is
QPSK_RAISE_PWR_SWITCH
option of this parameter be selected.
When this switch is selected, the
eNodeB uses the power of
unavailable RBs to boost the power
of CEUs using the quadrature phase
shift keying (QPSK) modulation
scheme. This improves the
demodulation performance of
CEUs.
l When LTE uplink capacity needs to
be improved, it is recommended
that the
UNCOSITE_UL_SCH_OPT_SW
ITCH option of this parameter be
selected.

SingleRAN

Name
Downlink CCH SpectrumCloud.DlCchSend This parameter specifies the

Send Strategy Strategy transmission strategy of downlink
common channels, and can be set to
any of the following:
l If the parameter is set to
ADAPTIVE, the interference from
LTE to GSM is the least, but LTE
performance is the poorest.
CRS_AVOIDED_PDCCH_ADAP
TIVE, the interference from LTE to
GSM increases and the LTE
performance is improved, compared
with when the parameter is set to
ADAPTIVE. It is recommended
that this parameter be set to this
value when GSM frequencies do
not participate in FH and the LTE
network performance needs to be
improved.
CRS_AND_PDCCH_AVOIDED,
the interference from LTE to GSM
increases and the LTE network
performance is improved, compared
with when the parameter is set to
TIVE. It is recommended that this
parameter be set to this value when
GSM frequencies do not participate
in FH and the LTE network
performance needs to be improved
in LTE heavy traffic scenarios.
l If this parameter is set to
CRS_ALL_PDCCH_ADAPTIVE,
the interference from LTE to GSM
increases and the LTE performance
is improved, compared with when
this parameter is set to ADAPTIVE
or
TIVE. It is recommended that this
parameter be set to this value when
GSM frequencies participate in FH
and the LTE network performance
needs to be improved.

SingleRAN

Name
PDCCH SpectrumCloud.PdcchIntrfR The default value is recommended.

Interferenced eCompRate
RE
Compensation
Rate
4.4.2.2 Using MML Commands
On the GSM Side

NOTE
Configure neighbor relationships between mutually interfering GSM cells on both sides.
Activation command examples

//Adding an external BSC with interfering neighboring cells
ADD EXTBSC: BSCIDX=0, BSCNAME="BSC1", BSCDPC=124, IurgDelayMeasureSw=ON;
//Turning on the Iur-g delay measure switch
MOD EXTBSC: IDTYPE=BYNAME, BSCNAME="BSC2", IurgDelayMeasureSw=ON;
//Adding an SCTP link (BSC6900)
ADD SCTPLNK: SRN=0, SN=0, SCTPLNKN=0, MODE=CLIENT, APP=EXTBSCAP, DSCP=48,
LOCPN=60000, LOCIP1="10.10.10.216", PEERIP1="10.10.10.217", PEERPN=2905,
LOGPORTFLAG=NO, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES;
//Adding an SCTP link (BSC6910)
ADD SCTPLNK: SCTPLNKID=0, MODE=CLIENT, APP=EXTBSCAP, DSCP=48, LOCPN=60000,
LOCIP1="10.10.10.216", PEERIP1="10.10.10.217", PEERPN=2905, LOGPORTFLAG=NO,
SWITCHBACKFLAG=YES;
//Adding an SCTP link connecting the local BSC to the external BSC
ADD EXTBSCCONN: BSCIDX=0, SCTPLNKID=0;
//Adding an external interfering neighboring cell
ADD GEXT2GCELL: EXT2GCELLID=3072, EXT2GCELLNAME="ExtCell_0", MCC="460", MNC="10",
LAC=10, CI=11, BCCH=60, NCC=0, BCC=0, BSCIDX=0;
//Configuring attributes of an external interfering neighboring cell
MOD GEXT2GCELL: IDTYPE=BYID, EXT2GCELLID=2048, BSCIDX=0;
//Adding an interfering neighboring cell of a GSM cell (BSC6900)
ADD G2GNCELL: IDTYPE=BYID, SRC2GNCELLID=1, NBR2GNCELLID=2,
NCELLSCETYPE=GLMEASNEIGHBORCELL-1, NCELLTYPE=NONE;
//Adding an interfering neighboring cell of a GSM cell (BSC6910)
ADD G2GNCELL: IDTYPE=BYID, SRC2GNCELLID=2, NBR2GNCELLID=1, ISNCELL=INNCELL,
NCELLSCETYPE=GLMEASNEIGHBORCELL-1, NCELLTYPE=NONE;
//Configuring a neighboring cell as an interfering neighboring cell (BSC6900)
MOD G2GNCELL: IDTYPE=BYID, SRC2GNCELLID=1, NBR2GNCELLID=2048,
NCELLSCETYPE=GLMEASNEIGHBORCELL-1;
//Configuring a neighboring cell as an interfering neighboring cell (BSC6910)
MOD G2GNCELL: IDTYPE=BYID, SRC2GNCELLID=1, NBR2GNCELLID=2048, ISNCELL=OUTCELL,
NCELLSCETYPE=GLMEASNEIGHBORCELL-1;
//Adding a co-coverage LTE cell for a GSM cell
/If the multi-sector configuration is not used on the LTE side, configure the co-
coverage relationship between one GSM cell and one LTE cell.
ADD GCELLGLCOCOVER: IDTYPE=BYNAME, CELLNAME="GsmCell001", LTEMNC="10",
LTEMCC="460", LTECI=1, LTESectorID=1;
/If the multi-sector configuration is used on the LTE side, configure the co-
coverage relationship between one GSM cell and two LTE cells.
//Adding a BSL
ADD BTSBSL: IDTYPE=BYID, BTSID=100, BSLSrvType=LTE;

SingleRAN
//Activating GSM and LTE Spectrum Concurrency

SET GCELLGLSPECCLOUD: IDTYPE=BYNAME, CELLNAME="GsmCell001", GLSpecConcurSw=ON,
GLDLSpectrumShareUnit=ADAPTIVE, LTEBandWidth=10M, LTEDlCenterFreq=3600,
LTEMultiplexPDCHSw=OFF, PriSecFreDLCoverLevGap=7;
Optimization command examples

//Configuring the following parameters: GL RX Level Gap Thd for Timeslot
Multiplexing, Intra-Freq. Cell Interference Coordination, LTE Multiplex PDCH
Switch, PS UL Load Threshold, PS DL Load Threshold, Shared Freq. Receive Level
Threshold, Dedicated Freq. HR Allocation Load Thld Offset, Optimized Spectrum
Concurrency HO Switch, Non-Interference State Statistic Time, and Non-
Interference State Last Time
LTEDLCenterFreq=2500, LTEBandwidth=5M, LTEMultiplexPDCHSw=ON,
IntraFreqNeighbCellCoordSw=ON, LTEMultiplexPDCHSw=ON, PsUlLoadThd=50,
PsDlLoadThd=60, SharedFreqRxLevThld=30, DedFreqHrAlloLdThldOffset=0,
SpecmConcurHoOptSw=ON, NoninterfStateStatTime=6, NoninterfStateLastTime=4;
//Configuring the multi-RAT scheduling management switch
SET GCELLCHMGBASIC: IDTYPE=BYID, CELLID=0, MultiRatScheduManagSW=ON,
MulRatSchManaPriGSM=6, MulRatSchManaPriUMTS=0, MulRatSchManaPriLTE=1;
//Configuring the PS DTX function
SET GCELLPRIVATEOPTPARA: IDTYPE=BYNAME, CELLNAME="GsmCell001", PSDTX=DTX;
//Configuring the following parameters: III Power Control Optimized Enable, III
DL RexLev Protect Factor, III DL RexQual Protect Factor, III DL Filter Adjust
Factor, DLRexLevAdjustFactor, DLRexQualAdjustFactor, DLMAXDownStep, DLMAXUpStep,
PwrCtrlDLAdjPeriod, DLRexQualExponentFilterLen, DLRexLevExponentFilterLen, DL
Power Control Max. Amplitude Optimize, and BTS Power Control Max. Level
SET GCELLPWR3: IDTYPE=BYNAME, CELLNAME="GsmCell001", PWRCTRLOPTIMIZEDEN=YES,
DLRXLEVPROTECTFACTOR=5, DLRXQUALPROTECTFACTOR=85, DLFILTADJFACTOR=9,
DLREXLEVADJFCTR=2, DLREXQUALADJFCTR=8, DLMAXDOWNSTEP=2, DLMAXUPSTEP=8,
DLADJPRD=1, DLREXQUALEXPFLTLEN=1, DLREXLEVEXPFLTLEN=1, DlMaxDownOptiSw=ON,
MAXBTSPWRNUM=8;
//Configuring the CS RACH Min. Access Level and PS RACH Min. Access Level
parameters
SET GCELLCCACCESS: IDTYPE=BYNAME, CELLNAME="GsmCell001", RACHACCLEV=-109,
PSRACHACCLEV=-109;
//Configuring the GAMMA and ALPHA parameters
SET GCELLPSPWPARA: IDTYPE=BYNAME, CELLNAME="GsmCell001", GAMMA=14, ALPHA=6;
//Configuring the PBGT Watch Time, PBGT Valid Time, and Level Penalty Value on
Neighboring Cell parameters
MOD G2GNCELL: IDTYPE=BYNAME, CELLNAME="GsmCell001", PBGTSTAT=4, PBGTLAST=3,
NCELLPUNLEV=0;
//Configuring the Filter Length for TCH Level, Filter Length for TCH Qual, and
Filter Length for Ncell RX_LEV parameters
SET GCELLHOFITPEN: IDTYPE=BYNAME, CELLNAME="GsmCell001", DATASTRFLTLEN=2,
DATAQUAFLTLEN=2, NCELLFLTLEN=2;
//Enabling intra-cell handovers
SET GCELLHOBASIC: IDTYPE=BYNAME, CELLNAME="GsmCell001", INTRACELLHOEN=YES;
Deactivation command examples

//Deactivating GSM and LTE Spectrum Concurrency
SET GCELLGLSPECCLOUD: IDTYPE=BYNAME, CELLNAME="GsmCell001", GLSpecConcurSw=OFF;
On the LTE Side

//Binding a cell that requires this function to a BBP supporting this function
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=1, BaseBandEqmId=12;
//Enabling the BE link setup function
MOD GLOBALPROCSWITCH: InterRatLinkSetupSwitch=BTS_ENODEB_LINK_SETUP_SWITCH-1;
//Configuring the LTE EARFCN and bandwidths
MOD CELL: LocalCellId=0, DlEarfcn=3600, DlBandWidth=CELL_BW_N50,
UlBandWidth=CELL_BW_N50;
//Configuring shared ARFCNs for this function
ADD GSMINTERFARFCNCFG: GsmArfcnGroupId=1, GsmArfcn=1;

SingleRAN
//Activating GSM and LTE Spectrum Concurrency

ADD SPECTRUMCLOUD: LocalCellId=0, SpectrumCloudSwitch=GL_SPECTRUM_CONCURRENCY,
NearPointUserPathLossThld=81, CoCovGsmSharingCarrierPwr=65535, GsmArfcnGroupId=1;
//Setting the PRACH frequency offset strategy to fully automatic
MOD RACHCFG: LocalCellId=0, PrachFreqOffsetStrategy=FULLY_AUTOMATIC;
//Enabling the SRS ACK/NACK simultaneous transmission
MOD SRSCFG: LocalCellId=0, AnSrsSimuTrans=BOOLEAN_TRUE;
//Enabling the adaptive PUCCH and SRS resource allocation and PUCCH resource
adjustment
MOD CELLALGOSWITCH: LocalCellId=0, PucchAlgoSwitch=PucchSwitch-1,
NonStandardBwAlgoSw=PUCCH_SRS_ADAPT_SWITCH-1;

//Configuring the following parameters: EnAperiodicCqiRptSwitch,
RptCqiFltInitSwitch, AdaptiveStepVarySwitch, PreciseMcsAdaptSwitch, and
SchedulerCtrlPowerSwitch
MOD CELLALGOSWITCH: LocalCellId=0, DlSchSwitch=EnAperiodicCqiRptSwitch-1,
CqiAdjAlgoSwitch=RptCqiFltInitSwitch-1&AdaptiveStepVarySwitch-1&PreciseMcsAdaptSwi
tch-1, UlSchSwitch=SchedulerCtrlPowerSwitch-1;
//Configuring the FD UE Enhanced Aperiodic CQI Trigger Period and RB Damage Cell
Near Point User IBLER Thd parameters
MOD CELLDLSCHALGO: LocalCellId=0, FDUEEnhAperCQITrigPeriod=40ms,
RBDamageNearPointIblerTh=80;
//Configuring the following parameters: PDCCH Capacity Improve Switch, PDCCH
Power Enhanced Switch, PDCCH Max Code Rate, PDCCH Out Loop Adjustment Value Lower
Thld, PDCCH Symbol Number Adjust Switch, and Cce Ratio Adjust Switch
MOD CELLPDCCHALGO: LocalCellId=0, PdcchCapacityImproveSwitch=ON,
PdcchPowerEnhancedSwitch=ON, PdcchMaxCodeRate=75, PdcchOutLoopAdjLowerLimit=-20,
PdcchSymNumSwitch=ON, CceRatioAdjSwitch=ON;
//Configuring the PHICH duration and resources
MOD PHICHCFG: LocalCellId=0, PhichDuration=NORMAL, PhichResource=ONE;
//Configuring the intra-frequency handover measurement bandwidth
MOD CELLRESEL: LocalCellId=0, MeasBandWidthCfgInd=CFG, MeasBandWidth=MBW25;
//Configuring the inter-frequency handover measurement bandwidth
MOD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=2950, MeasBandWidth=MBW25;
//Configuring the maximum number of UEs that can be admitted to a cell
MOD CELLRACTHD: LocalCellId=0, AcUserNumber=65535;
//Configuring the number of RBs in format 3 and the maximum number of 2CC ACK
channels
MOD PUCCHCFG: LocalCellId=0, Format3RbNum=1, Max2CCAckChNum=MAX_CH_NUM24;
//Configuring the following parameters: Near Point User Path Loss Threshold,
DL_PFM_PRF_PDCCH_SWITCH, QPSK_RAISE_PWR_SWITCH, UNCOSITE_UL_SCH_OPT_SWITCH, and
Downlink CCH Send Strategy
GsmArfcnGroupId=1, NearPointUserPathLossThld=80,
InterfPfmOptSwitch=DL_PFM_PRF_PDCCH_SWITCH-1&QPSK_RAISE_PWR_SWITCH-1&UNCOSITE_UL_S
CH_OPT_SWITCH-1, DlCchSendStrategy=ADAPTIVE, PdcchIntrfReCompRate=100;

//Deactivating GSM and LTE Spectrum Concurrency
MOD SPECTRUMCLOUD: LocalCellId=0, SpectrumCloudSwitch=OFF;
//Modifying the downlink EARFCN, downlink bandwidth, and uplink bandwidth of the
LTE cell
MOD CELL: LocalCellId=0, DlEarfcn=3600, DlBandWidth=CELL_BW_N25,
UlBandWidth=CELL_BW_N25;
4.4.2.3 Using the CME

This feature can be activated using the CME. This section uses the eNodeB as an example.
For detailed operations, see CME-based Feature Configuration or the CME online help (click
in an active CME window).

SingleRAN
Configuration CME Online Help

Type
Single configuration CME Management > CME Guidelines > Getting Started with
the CME > Introduction to Data Configuration Operations
Batch eGBTS CME Management > CME Guidelines > GSM Application
configuration Management > Base Station Related Operations > Importing
and Exporting eGBTS Data for Batch Reconfiguration
Batch NodeB CME Management > CME Guidelines > UMTS Application
configuration Management > NodeB Related Operations > Importing and
Exporting NodeB Data for Batch Configuration
Batch eNodeB CME Management > CME Guidelines > LTE Application
configuration Management > eNodeB Related Operations > Importing and
Exporting eNodeB Data for Batch Configuration
4.4.3 Activation Verification

Checking the License Usage
Step 1 Run the DSP LICUSAGE MML command on the BSC to query the license usage of this
function. If the license usage is not 0, this function has taken effect on the GSM side.
Step 2 Run the DSP LICINFO MML command on the eNodeB to query the license usage of this
function. If the license usage is not 0, this function has taken effect on the LTE side.
----End
Tracing Signaling Messages

Step 1 Check whether this function has been enabled by observing messages traced over the BE
interface on the BSC.
After a BSL is established between the BSC and eNodeB, the BSC receives a BeItf BSC
Resource Status Request message from the eNodeB. When the value of the "GL Dynamic
Spectrum Sharing Feature Status" IE in this message is 1, this function has been enabled on
the LTE side.
Step 2 Check whether this function has been enabled by observing messages traced over the BE
interface on the eNodeB.
When the eNodeB receives a BeItf BSC Resource Status Transfer message from the BSC and
the value of the "Cause" IE in this message is 0, this function has been enabled on the GSM
side.
----End

SingleRAN
NOTE
On the U2020, GSM message tracing is performed as follows:

1. Log in to the U2020. Choose Monitor > Signaling Trace > Signaling Trace Management. In the
navigation tree of the displayed window, expand GSM > CS Abis Trace.
2. In the displayed dialog box, select an NE and BSL, and set related parameters. Then, click Finish to
start a CS Abis tracing task.
On the U2020, LTE message tracing is performed as follows:
1. Log in to the U2020. Choose Monitor > Signaling Trace > Signaling Trace Management. In the
navigation tree of the displayed window, expand LTE > Application Layer > Inter-RAT Huawei-
Proprietary Interface Trace.
2. In the displayed dialog box, select an NE and set related parameters. Then, click Finish to start an
inter-RAT Huawei-proprietary interface tracing task.
Observing Performance Counters

Step 1 View related counters on the BSC to check whether this function has taken effect on the GSM
side. The function has taken effect if the following counters are not always 0:
l Average Number of Downlink Reusable Shared Timeslots of Co-coverage LTE Cells
(counter ID: 1282459445)
l Average Number of Uplink Reusable Shared Timeslots of Co-coverage LTE Cells
(counter ID: 1282459439)
Step 2 View related counters on the eNodeB to check whether this function has taken effect on the
LTE side. This function has taken effect if the following counters are not always equal to the
number of RBs corresponding to the cell bandwidth specified by Cell.DlBandWidth and
Cell.UlBandWidth, respectively:
l Number of available downlink PRBs (counter ID: 1526728433)
l Number of available uplink PRBs (counter ID: 1526728434)
----End
Table 4-10 Counters for activation observation
1282459445 CELL.CO.LTE.DL.SHARED.T R92236:Average Number of

S.AVR.NUM Downlink Reusable Shared
Timeslots of Co-coverage LTE
Cells
1282459439 CELL.CO.LTE.UL.SHARED.T R92237:Average Number of

S.AVR.NUM Uplink Reusable Shared Timeslots
of Co-coverage LTE Cells
1526728433 L.ChMeas.PRB.DL.Avail Number of available downlink

PRBs
1526728434 L.ChMeas.PRB.UL.Avail Number of available uplink PRBs

SingleRAN
4.4.4 Network Monitoring

After this function is enabled, compare the cell counters listed in Table 4-4 and Table 4-5
with those collected before function deployment. Observe the LTE cell downlink capacity
gains and negative impacts on GSM cells.
You can use the function "Quickly Setting Performance Measurement by Feature" on the
U2020 to initiate measurement of counters associated with this function. For details, see
"Quickly Setting Performance Measurement by Feature" in U2020 MBB Network
Management System Product Documentation.
4.4.5 Possible Issues

l BSL or Iur-g link faults
The BSC reports ALM-21840 BSL Fault or ALM-21541 SCTP Link Fault. When either
alarm is reported, the eNodeB allocates only LTE exclusive REs/RBs to LTE UEs to
ensure that the impact on GSM KPIs is within a tolerable level. The gain produced by
this function decreases as a result.
For details about this alarm and alarm handling, see BSC6900 GSM Alarm Reference in
BSC6900 GSM Product Documentation or BSC6910 GSM Alarm Reference in BSC6910
GSM Product Documentation.
l GSM time synchronization failure: Based on the GSM time synchronization mode,
identify the synchronization failure and troubleshoot it by referring to BTS GPS
Synchronization, Synchronization, or Soft-Synchronized Network in GBSS Feature
Documentation.

SingleRAN
Description 5 GSM and LTE Spectrum Concurrency Phase 2
5 GSM and LTE Spectrum Concurrency

Phase 2
5.1 Principles
This function is enabled when the GLSPECCONCURPH2 option of the
GCELLGLSPECCLOUD.GLSpecConcurEnh parameter is selected on the GSM side and
the GL_SPCT_CONCURRENCY_PH2_SW option of the
SpectrumCloud.SpectrumCloudEnhSwitch parameter is selected on the LTE side.
GSM and LTE Spectrum Concurrency Phase 2 supports larger shared spectrum, differentiated
CRS interference coordination, and load-based frequency hopping (FH) set adaptation.
Larger Shared Spectrum

This function supports a larger shared bandwidth in LTE 10 MHz, 15 MHz, and 20 MHz
bandwidth scenarios.
l In the LTE 10 MHz bandwidth scenario, LTE supports up to 4.4 MHz of shared
bandwidth.
bandwidth.
bandwidth.
Differentiated CRS Interference Coordination

The BSC determines whether the interference from LTE CRSs to GSM MSs is acceptable
based on the LTE CRS receive level gap threshold for multiplexing, which is configured by
the GCELLGLSPECCLOUD.LTECRSRxLevelGapThld parameter. If the interference level
is acceptable, LTE is allowed to send CRSs on the shared spectrum occupied by GSM MSs. A
higher CRS transmission proportion results in improved CRS coverage performance.

SingleRAN
Load-based FH Set Adaptation

When FH is enabled, the FH sets (also named MA sets) can be adaptively adjusted based on
cell load to enable the use of shared frequencies by LTE. Load-based FH set adaptation is
supported only when the following requirements are met:
l The shared frequencies of a cell belong to the same MA set.
l Load-based FH set adaptation is enabled in all cells at the same site.
l The co-sited cells enabled with this function must all use the same MA set or each use a
different MA set.
If the GSM cell load on each TRX after a TRX using a frequency in the FH set is excluded is
less than the value of the GCELLCHMGBASIC.ShareFreqRlsLdThld parameter for a
number of measurement periods (this number is specified by the
GCELLCHMGBASIC.RlsFreqLdDuration parameter) out of the total number of
measurement periods specified by GCELLCHMGBASIC.LdStatisticsTime, the GSM cell
releases a shared frequency in the MA set.
If the GSM cell load is greater than or equal to the sum of the
GCELLCHMGBASIC.ShareFreqRlsLdThld and
GCELLCHMGBASIC.RclaimSharFreqLdThldOffset parameters for a number of
measurement periods (this number is specified by the
GCELLCHMGBASIC.RclmFreqLdDuration parameter) out of the total number of
measurement periods specified by the GCELLCHMGBASIC.LdStatisticsTime parameter,
the GSM cell reclaims a released shared frequency in the MA set.
The BSC calculates the priority of each frequency in the MA set. When a frequency can be
released, the BSC preferentially releases the frequency with the highest priority in the MA set.
After the frequency is released, the BSC replans and adjusts the MA and mobile allocation
index offset (MAIO) for each timeslot in the cell. In the case of frequency reclamation, the
BSC selects the frequency with the lowest priority among the frequencies that have been
released in the MA set. After the frequency is reclaimed, the BSC replans and adjusts the MA
and MAIO for each timeslot in the cell.
5.2 Network Analysis
5.2.1 Benefits
This function allows full spectrum utilization and improves LTE network capacity under the
condition that the interference from LTE to GSM is at a tolerable amount. Table 5-1 describes
the LTE capacity gains compared with an LTE network using the adjacent lower standard
bandwidth under different total bandwidths, power configurations, and achievable LTE
standard bandwidths.

SingleRAN
Table 5-1 LTE downlink capacity gains

Total Achievable GSM and Adjacent Capacity Capacity
Bandwid LTE Standard LTE Lower Gain Gain
th Bandwidth Power LTE When When
Configurat Standard BCCHs TCHs Are
ion Bandwidt Are Deployed
h Deployed on the
on the Shared
Shared Spectrum
Spectrum
≥ 6.2 5 MHz (LTE GSM: 20 W 3 MHz 15%–57% 15%–83%

MHz supports up to 1.2 LTE: 2 x 20
MHz of shared W
bandwidth.)
≥ 10 MHz 10 MHz (LTE GSM: 20 W 5 MHz 12%–98% 12%–

supports up to 4.4 LTE: 2 x 40 120%
MHz of shared W
bandwidth.)

MHz of shared W
bandwidth.)

MHz of shared W
bandwidth.)
Cell capacity = Number of available RBs in a cell x Spectral efficiency =

L.ChMeas.PRB.DL.Avail x ((L.Traffic.DL.SCH.QPSK.TB.bits + L.Traffic.DL.SCH.
16QAM.TB.bits + L.Traffic.DL.SCH.64QAM.TB.bits + L.Traffic.DL.SCH.
256QAM.TB.bits)/L.ChMeas.PRB.DL.Used.Avg/Statistical period/10^6)
The power configurations listed in Table 5-1 are typical power configurations, and the LTE
cell capacity gains can be achieved only when the PSD of GSM and LTE meet the following
requirements:
- When LTE uses a 5 MHz or 10 MHz bandwidth, the PSD difference between GSM and LTE
must be 10.5 dB.
12.3 dB.
13.5 dB.
PSD difference between GSM and LTE = GSM power (dBm) – LTE power dBm@200 kHz
= GSM power (dBm) – LTE power (dBm) + 10 x lg(LTE bandwidth x 90% ÷ 0.2)
For example, if LTE uses a 5 MHz bandwidth and the power of each GSM TRX is 20 W, the
LTE power configuration must be 2 x 20 W to obtain the 10.5 dB PSD difference, which

SingleRAN
equals 10 x lg(20 W/1 mW) – 10 x lg(2 x 20 W/1 mW) + 10 x lg(5 x 90% ÷ 0.2). If the
power of each GSM TRX is 10 W, the LTE power configuration must be 2 x 10 W to obtain
the 11 dB PSD difference.
When the PSD difference between GSM and LTE is greater than the required value, the gain
provided by this function is smaller than those listed in Table 5-1 due to larger GSM
interference. Under these circumstances, the PSD difference must be within the range of
{Required PSD difference, Required PSD difference + 3 dB}. Otherwise, this function may
produce negative gains. When the PSD difference is smaller than the required value, the LTE-
to-GSM interference may increase, but the gain provided by this function is still within the
range listed in Table 5-1.
When GSM uses transmit diversity or LTE uses 4T4R to improve coverage performance,
operators must consider the impact of these functions on power when calculating the PSD
difference.
To ensure that the PSD difference between GSM and LTE meets the specified requirements,
the cell transmit power must be restricted when the power of RF modules for the LTE side is
insufficient. That is, the PDSCHCfg.CellPowerLimit, PDSCHCFG.Pb, and
PDSCHCFG.EmfPowerLimitSwitch parameters must be set based on the network plan. The
cell power restriction reduces the upper limit of LTE capacity gains.
NOTE
l This function provides only LTE capacity gains. The GSM capacity remains unchanged. The lower
limits of LTE capacity gains are obtained in GSM peak hours when LTE uses only the LTE exclusive
spectrum. The upper limit of LTE capacity gains in the case of BCCH frequency sharing is achieved
when GSM has no traffic, requires only BCCHs and SDCCHs, and shares all other frequencies to
LTE. The upper limit of LTE capacity gains in the case of TCH frequency sharing is achieved when
GSM uses only the spectrum outside the LTE standard bandwidth and does not occupy the shared
spectrum.
l When the shared GSM frequencies do not participate in frequency hopping (FH), GSM
preferentially occupies the spectrum far away from the LTE center frequency. When the shared GSM
frequencies participate in FH, GSM occupies discrete spectrum of the entire shared spectrum.
Assuming that the GSM service volume remains unchanged, the gain provided by this function is
larger when the shared GSM frequencies do not participate in FH, than when the shared GSM
frequencies participate in FH.
l When the communication link between the BSC and eNodeB is interrupted, the achievable gain is
close to the lower limit of the gain range.
5.2.2 Impacts
Network Impacts
l On the GSM side
As more GSM shared frequencies can overlap with the LTE bandwidth, the proportion of
GSM shared frequencies on the entire GSM network increases. Consequently, the GSM
network performance may deteriorate.
l On the LTE side
The use of a larger shared bandwidth leads to inaccurate measurement results of LTE
quality-related counters that are measured over the full band. The counters, for example,
include the SINR, RSRQ, full-band CQI, PMI, and RI. The RSSI and interference in the
uplink increase. Therefore, it is recommended that counters related to the MCS or
throughput be used for performance evaluation.

SingleRAN
Function Impacts
Name Switch (eRAN
Feature
Parameter
Description
Document)
FDD eMTC EMTC_SWIT eMTC In LTE 10 MHz

Introduction CH option of bandwidth scenarios,
the when the number of
CellEmtcAlgo. GSM frequencies
EmtcAlgoSwitc configured on both ends
h parameter of the LTE center
frequency (the number of
overlapped frequencies)
is greater than 6, the PCI
of the cell must be
restricted. Specifically,
the PCI that meets the
following conditions
cannot be used:
l mod (PCI, 6) = 1
l mod (PCI, 6) = 4
5.3 Requirements
5.3.1 Licenses
ID Item Unit
MRFD- GSM and LTE LGMIGLS GSM and LTE BSC Per Cell
131201 Spectrum CP2 Spectrum
Concurrency Concurrency Phase
Phase 2 (GSM) 2 (GSM)(Per Cell)
MRFD- GSM and LTE LT1SGLSP GSM and LTE eNodeB Per Cell
131221 Spectrum CON2 Spectrum
Concurrency Concurrency Phase
Phase 2 (LTE 2 (LTE FDD)(Per
FDD) Cell)

SingleRAN
5.3.2 Software
Prerequisite Functions
Name Switch
GSM GSM and LTE GCELLGLSP GSM and LTE GSM and LTE Spectrum
Spectrum ECCLOUD.G Spectrum Concurrency must be
Concurrency LSpecConcurS Concurrency enabled prior to GSM
(GSM) w and LTE Spectrum
Concurrency Phase 2.
LTE GSM and LTE SpectrumClou GSM and LTE GSM and LTE Spectrum
Spectrum d.SpectrumClo Spectrum Concurrency must be
Concurrency udSwitch Concurrency enabled prior to GSM
(LTE FDD) and LTE Spectrum
Concurrency Phase 2.
Mutually Exclusive Functions

l GSM and LTE Spectrum Concurrency Phase 2 is mutually exclusive with the GSM
functions listed in the following table only when load-based FH set adaptation is
enabled.
l GSM and LTE Spectrum Concurrency Phase 2 is mutually exclusive with the LTE
functions listed in the following table when the PDSCHCfg.CellPowerLimit parameter
is set to an above-zero value to limit the maximum transmit power of a single RF
channel for an LTE cell.
Name Switch
GSM GSM and GDSSPARA.D GSM and The load-based FH set

UMTS SSENABLE UMTS Dynamic adaptation function
Dynamic Spectrum cannot be enabled
Spectrum Sharing together with either of
Sharing(GSM) these functions. This is
because the load-based
GSM Dynamic MA N/A GSM and FH set adaptation
for GU UMTS Dynamic function and these
Dynamic Spectrum functions both use a
Spectrum Sharing dynamic MA set
Sharing(GSM) adjustment scheme but
with conflicting
adjustment policies.

SingleRAN

Name Switch
GSM Flex MAIO GCELL.FLEX Flex MAIO The load-based FH set

MAIO and adaptation function
GCELL.HSNS cannot be enabled
W together with this
function because they
both use a dynamic
MAIO adjustment
scheme but with
conflicting adjustment
policies.
GSM Inter-module BTSRXUBP.R Frequency The load-based FH set

RF frequency ELATEDMOD Hopping adaptation function
hopping FUNC cannot be enabled
together with this
function because their
application scenarios
conflict with each other.
GSM Antenna GCELLHOPA Antenna The load-based FH set

Frequency NT.HPANTM Frequency adaptation function
Hopping ODE Hopping cannot be enabled
together with this
function because these
two functions conflict
with each other.
GSM IBCA GCELLCHM IBCA The load-based FH set

GAD.IBCAAL adaptation function and
LOWED these two functions all
use a dynamic MAIO
GSM IBCAII GCELLCHM IBCA II adjustment scheme but
GAD.IBCAAL with conflicting
LOWED and adjustment policies.
GCELLIBCAI Therefore:
I.IBCAIIAllow
ed l In non-concentric
cells, the load-based
FH set adaptation
function cannot be
enabled together with
either of these two
functions.
l In concentric cells,
the load-based FH set
adaptation function
cannot be enabled
together with either of
these two functions in
the spectrum shared
by GSM and LTE.

SingleRAN

Name Switch
GSM Multi-site Cell N/A Multi-site Cell The Multi-site Cell

together with this
function, because their
application scenarios
conflict with each other.
FDD RF channel CellRfShutdo Energy After the intelligent

intelligent wn.RfShutdow Conservation shutdown of an RF
shutdown nSwitch and Emission channel, the CRS power
Reduction of the remaining RF
channels is boosted and
the maximum number of
RBs that can be
scheduled is reduced.
When the maximum
transmit power limitation
function is enabled, the
maximum number of
RBs that can be
scheduled may be further
reduced. Therefore, these
two functions cannot be
FDD SFN cell Cell.MultiRruC SFN In SFN scenarios, a

ellMode logical cell corresponds
to multiple physical cells.
When the maximum
transmit power limitation
function is enabled in
these physical cells, the
maximum number of
available RBs in these
cells may be different.
Therefore, these two
functions cannot be

SingleRAN

Name Switch
FDD Service UsUeGuarante N/A This function is used to

guarantee for eSwitch option achieve the optimal peak
UEs running of the rate. When the maximum
unlimited CellUSParaCf transmit power limitation
services g.UsAlgoSwitc function is enabled, the
h parameter number of available RBs
may be limited, which
leads to a decrease in the
peak rate. Therefore,
these two functions
cannot be simultaneously
used.
FDD On-Demand TX PDSCHCfg.E On-Demand TX This function is used to

Power mfPowerLimitS Power limit the cell power, and
Allocation witch Allocation therefore is similar to the
Under EME Under EME maximum transmit
power limitation
function. These two
functions cannot be
5.3.3 Hardware
The BSC6900/BSC6910 service processing boards (XPUa/XPUb/XPUc/EGPUa/EGPUb)
support this function. New service processing boards must be added if either of the following
conditions is met:
l The ratio of LTE shared bandwidth to the LTE standard bandwidth is less than or equal
to 24%, but the average CPU load of service processing boards exceeds 50%.
l The ratio of LTE shared bandwidth to the LTE standard bandwidth exceeds 24%, and the
average CPU load of service processing boards exceeds 42%.
5.3.4 Networking
RF Modules
l Before function deployment
If the LTE network is newly deployed on a frequency band, RF optimization must be
performed to prevent excessive cell coverage overlap from affecting network
performance. In addition, this function requires that GSM and LTE share the same
antenna system. If the existing GSM and LTE networks do not share the same antenna
system, network reconstruction must be performed. Operators can contact Huawei
engineers to evaluate the impact of GSM and LTE co-antenna.
l After function deployment
– If the set of GSM interfering frequencies changes, the GSM interfering frequencies
must be reconfigured on the eNodeB side. Otherwise, LTE network performance is
affected. If the set of GSM interfering frequencies remains the same but the

SingleRAN
frequencies configured for the involved GSM cell have changed, no reconfiguration
is required.
– In the case of site addition or deletion, cell RF parameter changes, co-coverage
relationship changes between GSM and LTE cells, or changes in interfering
neighboring cells of the GSM cell, reconfiguration must be performed.
– When an LTE multi-sector solution (2T6S or 4T6S) is used at the same time:
n If the multi-sector solution is implemented through combined RF modules and
multi-beam antennas, Multi-site Cell must be enabled on the GSM side (the
load-based FH set adaptation function must be disabled), and co-BCCH
networking is not supported.
n If the 2T6S multi-sector solution is implemented by the split of a 4T4R
module, 2T4R transmit diversity must be configured on the GSM side, and co-
BCCH networking is supported.
When a multi-sector solution is used on the LTE side, the co-coverage relationship
between GSM and LTE cells changes. Therefore, you need to replan and configure
related features. For details, contact Huawei engineers.
Spectrum
Frequency band
This function applies to the frequency bands supported by both GSM and LTE (850 MHz, 900
MHz, 1800 MHz, and 1900 MHz).
System bandwidth, the corresponding continuous spectrum, and shared spectrum
This function supports only LTE FDD 5 MHz, 10 MHz, 15 MHz, and 20 MHz bandwidths.
The uplink bandwidth must be the same as the downlink bandwidth. The continuous spectrum
and shared spectrum in each LTE FDD bandwidth scenario are as follows:
l LTE FDD 5 MHz bandwidth: At least a 6.2 MHz total bandwidth is required, the
continuous bandwidth must be at least 5 MHz, and LTE supports up to 1.2 MHz of
shared bandwidth. The following figure illustrates function application when these
requirements are met.

SingleRAN
GSM and LTE spectrum configuration

l The GSM frequencies that fall within LTE bandwidth are preferentially configured in the
LTE guard band. The GSM frequencies that cannot be configured in the LTE guard band
are configured using either of the following methods:
– Method 1: Symmetrically configure these GSM frequencies on both sides of the
LTE available bandwidth.
– Method 2: Configure these GSM frequencies on either side of the LTE available
bandwidth.

SingleRAN
Method 2 provides a larger downlink capacity gain than method 1 does, but it also
decreases the uplink single-user throughput. In addition, when method 2 is used, the
RRC connection setup delay in a 5 MHz cell may be larger than that in a 3 MHz cell.
l If multiple LTE carriers operate in the same frequency band or different frequency bands
in the same area, the spectral efficiency can be maximized by allowing as many LTE
cells to use a standard bandwidth as possible. In this case, only one LTE carrier in the
area can use the shared GSM spectrum.
l If the GSM cell is configured with only one carrier and this carrier overlaps with the
effective LTE spectrum, to improve the LTE capacity gain, you are not advised to
configure static PDCHs on this GSM carrier.
l If the GSM frequencies that fall within the LTE bandwidth participate in FH, and if one
GSM frequency in the MA list is occupied, all GSM frequencies in the MA list are
considered occupied. Consequently, the LTE network capacity gain provided by this
function is affected.
l LTE PCIs must be planned in such a way that the interference from GSM frequencies
that fall within the LTE bandwidth is minimized. For details on PCI planning, contact
Huawei technical support.
l LTE PUCCHs, PRACHs, and SRSs must be configured on the LTE exclusive RBs that
are not interfered by GSM. When this function is deployed together with NB-IoT or
eMTC, NB-IoT or eMTC must be deployed on LTE exclusive RBs on the side of LTE
spectrum with fewer shared GSM frequencies. In addition, the following configuration
suggestions must be observed:
– When this function is deployed together with NB-IoT, the interference between NB-
IoT and LTE is lower than that between GSM and LTE. To achieve the best possible
overall performance of LTE, it is recommended that GSM be preferentially
deployed on the LTE guard band and that NB-IoT be deployed in standalone or LTE
in-band mode. When GSM shared frequencies are deployed only on one side of the
LTE guard band, NB-IoT can be deployed on the other side of the guard band. To
avoid interference between GSM and NB-IoT, a sufficient bandwidth must be
reserved between them.
– When this function is deployed together with eMTC, the LTE 5 MHz bandwidth is
not supported. In the LTE 10 MHz bandwidth scenario, it is recommended that the
GSM frequencies that overlap with the LTE bandwidth be symmetrically configured
on both sides of the LTE bandwidth. If the GSM frequencies are asymmetrically
configured on the two sides of the LTE bandwidth, eMTC cell activation may fail
due to insufficient resources. In addition, the CellCeSchCfg.SiTransEcr parameter
for eMTC must be set to a value greater than or equal to 34, and the
CellCeSchCfg.PagingGroupNum parameter must be set to a value other than
FOURT or TWOT.
– When this function is deployed together with NB-IoT and eMTC, the LTE 5 MHz
bandwidth is not supported. In the LTE 10 MHz bandwidth scenario, it is
recommended that the GSM frequencies that overlap with LTE bandwidth be
symmetrically configured on both sides of the LTE bandwidth, and that NB-IoT be
deployed on the fifth eMTC narrowband.
Network Planning
This function can be enabled on either of the following:
l Specific areas of the network
A buffer zone must be planned to prevent co-channel interference between GSM and
LTE. The method for planning the buffer zone is the same as that for planning the buffer

SingleRAN
zone in GL refarming scenarios. During buffer zone planning, operators must consider
the spectrum of both RATs. For more information, contact Huawei engineers.
l Entire network
No buffer zone is required.
NOTE
When this function is enabled in specific areas of the network, GSM and LTE co-channel interference
occurs on the shared spectrum if interference coordination is not implemented. This adversely affects
GSM and LTE network performance. If the interference is severe, the throughput may decrease, and
services may even fail to be initiated. In this case, a buffer zone is required between the GSM and LTE
sites on the same frequency band. To avoid mutual interference between GSM cells in the buffer zone
and LTE cells with this function enabled, this function must also be enabled in GSM cells in the buffer
zone.
5.3.5 Others
This function takes effect only when MRFD-131201 GSM and LTE Spectrum Concurrency
Phase 2 (GSM) and MRFD-131221 GSM and LTE Spectrum Concurrency Phase 2 (LTE
FDD) are simultaneously used.
5.4 Operation and Maintenance
5.4.1 When to Use
Recommended Application Scenarios

This function applies to scenarios where an LTE network must be deployed at the earliest time
possible or the capacity of an existing LTE network must be increased, but the GSM traffic
load is low and legacy GSM terminals on the live network will not exit the network within a
short period of time.
This function is not recommended if any of the following is true:

l Indoor distributed base stations are deployed. In this scenario, the GSM-to-LTE
interference may be severe, causing significant service performance deterioration.
l The GSM configuration reduction analysis shows that GSM capacity requirements
cannot be met after GSM traffic is migrated from the frequency band where this function
is to be enabled, to other frequency bands or networks.
l High-speed or ultra-high-speed scenarios exist. Interference cannot be accurately
determined in these scenarios.
l The spectrum resource requirement of this function is not met. Specifically, the total
amount of spectrum resources is less than 6.2 MHz or the maximum amount of
continuous spectrum resources is less than 5 MHz.
Required Information
The required information is the same as that for the GSM and LTE Spectrum Concurrency
function. For details, see Required Information.

SingleRAN
5.4.2 Data Configuration

It is recommended that this function be activated when traffic is light, for example, in the
early morning. This is because reconfigurations are required during function activation, which
causes LTE cells to reset.
5.4.2.1 Data Preparation
On the GSM Side

establishment.

Name
GSM and LTE GCELLGLSPECCLOUD.G Select the GLSPECCONCURPH2

Spectrum LSpecConcurEnh option of this parameter for GSM cells
Concurrency requiring this function.
Enhancement
LTE CRS RX GCELLGLSPECCLOUD.L Set this parameter based on the

Level Gap Thld TECRSRxLevelGapThld network plan.
for Multiplex
Load-based GCELLCHMGBASIC.LdFr It is recommended that this parameter

Freq. Hopping eqHopSetAdapSw be set to ON when spectrum sharing is
Set Adaptive implemented in FH scenarios. This
Switch parameter is valid only when the
GLSPECCONCURPH2 option of the
GCELLGLSPECCLOUD.GLSpecCo
ncurEnh parameter is selected.
Load Threshold GCELLCHMGBASIC.Shar Set this parameter based on the

for Shared Freq. eFreqRlsLdThld network plan.
Release
Load Threshold GCELLCHMGBASIC.Rclai Set this parameter based on the

Offset for mSharFreqLdThldOffset network plan.
Reclaim Shared
Freq.

Name
Load Statistics GCELLCHMGBASIC.LdSt Set this parameter based on the

Time atisticsTime network plan.

SingleRAN

Name
Release Freq. GCELLCHMGBASIC.RlsF Set this parameter based on the

Load Duration reqLdDuration network plan.
Reclaim Freq. GCELLCHMGBASIC.Rclm Set this parameter based on the

Load Duration FreqLdDuration network plan.
Freq. Hopping GCELLCHMGBASIC.Freq Set this parameter based on the

Set Adjust HopSetAdjstProtctDur network plan.
Protect
Duration
On the LTE Side

establishment.

Name

Group ID cnGroupId operator's network plan.

cn operator's network plan. For the 5
MHz, 10 MHz, 15 MHz, or 20 MHz
standard LTE bandwidth, an ARFCN
group contains a maximum of 6, 22,
25, or 25 shared ARFCNs, respectively.
Ensure that the configured GSM
ARFCNs are the same as the GSM
ARFCNs in use. Otherwise, there may
be interference in the LTE uplink
control channel, affecting LTE network
performance. When NB-IoT is
deployed in in-band mode, NB-IoT
functions may be affected.
Spectrum Cloud SpectrumCloud.SpectrumCl Select the

Enhancement oudEnhSwitch GL_SPCT_CONCURRENCY_PH2_
Switch SW option of this parameter for LTE
cells requiring this function.

SingleRAN
Table 5-5 Parameter used for optimization

Name
Cell Power PDSCHCfg.CellPowerLimit Set this parameter based on the

Limit network plan.
l When the power of RF modules for
the LTE side is insufficient, the cell
power restriction function is
required. That is, you need to set
this parameter, PDSCHCFG.Pb,
and
PDSCHCFG.EmfPowerLimitSwitc
h based on the network plan.
l When the power of RF modules for
the LTE side is sufficient, the cell
power restriction function is not
required. Under these
circumstances, set this parameter to
0.
5.4.2.2 Using MML Commands
On the GSM Side

//Activating GSM and LTE Spectrum Concurrency Phase 2
GLSpecConcurEnh=GLSPECCONCURPH2-1, GLDLSpectrumShareUnit=ADAPTIVE,
LTEBandWidth=10M, LTEDlCenterFreq=3600, LTEMultiplexPDCHSw=ON,
LTECRSRxLevelGapThld=22, PriSecFreDLCoverLevGap=7;
//Enabling load-based FH set adaptation (This function is optional. It is
recommended in FH scenarios. GSM and LTE Spectrum Concurrency Phase 2 must be
enabled prior to this function.)
SET GCELLCHMGBASIC: IDTYPE=BYID, CELLID=0, LdFreqHopSetAdapSw=ON,
ShareFreqRlsLdThld=50, RclaimSharFreqLdThldOffset=15, LdStatisticsTime=7,
RlsFreqLdDuration=5, RclmFreqLdDuration=3, FreqHopSetAdjstProtctDur=1;

//Disabling load-based FH set adaptation
SET GCELLCHMGBASIC: IDTYPE=BYID, CELLID=0, LdFreqHopSetAdapSw=OFF;
//Deactivating GSM and LTE Spectrum Concurrency Phase 2
LTEDLCenterFreq=3600, LTEBandwidth=10M, GLSpecConcurEnh=GLSPECCONCURPH2-0,
LTECRSRxLevelGapThld=65535;
On the LTE Side

//Configuring shared ARFCNs for this function
//Activating GSM and LTE Spectrum Concurrency Phase 2

SingleRAN

SpectrumCloudEnhSwitch=GL_SPCT_CONCURRENCY_PH2_SW-1,
NearPointUserPathLossThld=81, CoCovGsmSharingCarrierPwr=65535, GsmArfcnGroupId=1;

//Not restricting the cell transmit power when the power of RF modules for the
LTE side is sufficient
MOD PDSCHCFG: LocalCellId=0, CellPowerLimit=0;
//Restricting the cell transmit power when the power of RF modules for the LTE
side is insufficient
MOD PDSCHCFG: LocalCellId=0, Pb=3, EmfPowerLimitSwitch=OFF, CellPowerLimit=3000;

//Deactivating GSM and LTE Spectrum Concurrency Phase 2
MOD SPECTRUMCLOUD: LocalCellId=0, SpectrumCloudSwitch=GL_SPECTRUM_CONCURRENCY,
SpectrumCloudEnhSwitch=GL_SPCT_CONCURRENCY_PH2_SW-0;
//Removing the configurations of shared ARFCNs
RMV GSMINTERFARFCNCFG: GsmArfcnGroupId=1, GsmArfcn=1;
RMV GSMINTERFARFCNCFG: GsmArfcnGroupId=1, GsmArfcn=2;
5.4.2.3 Using the CME

l Fast Batch Activation
This feature can be batch activated using the Feature Operation and Maintenance
function of the CME. For detailed operations, see the following section in the CME
product documentation or online help: CME Management > CME Guidelines >
Enhanced Feature Management > Feature Operation and Maintenance.
l Single/Batch Configuration
This feature can be activated for a single base station or a batch of base stations on the
CME. This section uses the eNodeB as an example. For detailed operations, see CME-
based Feature Configuration or the CME online help (click in an active CME
window).
Configuration CME Online Help
Type
Single CME Management > CME Guidelines > Getting Started

configuration with the CME > Introduction to Data Configuration
Operations
Batch eGBTS CME Management > CME Guidelines > GSM Application
configuration Management > Base Station Related Operations > Importing
and Exporting eGBTS Data for Batch Reconfiguration
Batch NodeB CME Management > CME Guidelines > UMTS Application
configuration Management > NodeB Related Operations > Importing and
Exporting NodeB Data for Batch Configuration
Batch eNodeB CME Management > CME Guidelines > LTE Application
configuration Management > eNodeB Related Operations > Importing and
Exporting eNodeB Data for Batch Configuration

SingleRAN
5.4.3 Activation Verification

Use one of the following methods to verify whether GSM and LTE Spectrum Concurrency
Phase 2 has taken effect:
l Check the license usage.
a. Run the DSP LICUSAGE MML command on the BSC to query the license usage
of this function. If the license usage is not 0, this function has taken effect on the
GSM side.
b. Run the DSP LICINFO MML command on the eNodeB to query the license usage
of this function. If the license usage is not 0, this function has taken effect on the
LTE side.
l Observe one of the following messages over the BE interface on the BSC side: BeItf
BSC Resource Status Response, BeItf BSC Resource Status Update, or BeItf BSC
Resource Status Transfer. If the value of the "Freq Down Avail Status" information
element (IE) in any of these messages is 4, CRS-based differentiated interference
coordination is enabled.
l Run the DSP GCELLLOADMAADAPT command on the BSC to query whether the
load-based FH set adaptation has taken effect. If the command output indicates that the
FH set in use is not always the configured FH set, this function has taken effect.
5.4.4 Network Monitoring

Perform network monitoring after GSM and LTE Spectrum Concurrency Phase 2 and its
related functions are enabled.
l The network monitoring for GSM and LTE Spectrum Concurrency Phase 2 is the same
as that for GSM and LTE Spectrum Concurrency. For details, see 4.4.4 Network
Monitoring.
l When CRS-based differentiated interference coordination is enabled, monitor the
changes in the LTE CRS transmission proportion by observing the value of the eNodeB
counter L.DL.CRS.RateAvg.
l When load-based FH set adaptation is enabled, monitor frequency sharing by running the
DSP GCELLLOADMAADAPT command on the BSC to query the configured FH set
and the FH set in use.
5.4.5 Possible Issues

The fault handling for this function is the same as that for GSM and LTE Spectrum
Concurrency. For details, see 4.4.5 Possible Issues.

SingleRAN
Description 6 Parameters
6 Parameters
There are no specific parameters associated with this feature in this RAT.

SingleRAN
Description 7 Counters
7 Counters
There are no specific counters associated with this feature in this RAT.

SingleRAN
Description 8 Glossary
8 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

SingleRAN
Description 9 Reference Documents
9 Reference Documents
l 3GPP TS 45.005: "3rd Generation Partnership Project; Technical Specification Group

Radio Access Network; GSM/EDGE Radio transmission and reception"
l 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station
(BS) radio transmission and reception"
l 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical
channels and modulation"
l Feature parameter description documents in eRAN Feature Documentation
– NB-IoT Basics (FDD)
– Mobility Management in Connected Mode
– MIMO
– Extended CP
– LCS
– CPRI Compression
– Super Combined Cell (FDD)
– Carrier Aggregation
– 3D Beamforming (FDD)
– GSM and LTE Dynamic Power Sharing
– eMTC
– Modulation Schemes
– Physical Channel Resource Management
– Power Control
– Scheduling
– GSM and LTE FDD Dynamic Spectrum Sharing
– GSM and LTE Zero Bufferzone
– GSM and LTE Buffer Zone Optimization
– UL Refarming Zero Bufferzone
– CDMA and LTE Zero Bufferzone
– UMTS and LTE Spectrum Sharing
– UMTS and LTE Zero Bufferzone

SingleRAN
Description 9 Reference Documents
– LTE and NR Spectrum Sharing

– UMTS and LTE Spectrum Sharing Based on DC-HSDPA
– Compact Bandwidth (FDD)
– Flexible Bandwidth based on Overlap Carriers (FDD)
– Adaptive ICIC
– eMBMS
– Energy Conservation and Emission Reduction
– SFN
– On-Demand TX Power Allocation Under EME
– Massive MIMO (FDD)
– Relay
– Channel State Management
l Feature parameter description documents in GBSS Feature Documentation
– Connection Inter BSC over IP
– Enhanced BCCH Power Consumption Optimization
– Frequency Hopping
– Antenna Frequency Hopping
– BCCH Dense Frequency Multiplexing
– IBCA
– IBCA II
– Intelligent BCCH Interference Suppression (IBIS)
– BTS GPS Synchronization
– Synchronization
– Uu based Soft Synchronization
– GSM and UMTS Dynamic Spectrum Sharing
– GSM and LTE FDD Dynamic Spectrum Sharing
– GSM and LTE Zero Bufferzone
– Satellite Transmission
– Channel Management
– Flex MAIO
– Multi-site Cell
l BBU Interconnection in 3900 & 5900 Series Base Station Product Documentation
l 3900 Series BBU Hardware Description in 3900 & 5900 Series Base Station Product
Documentation
l BBU5900 Hardware Description in 3900 & 5900 Series Base Station Product
Documentation

GSM and LTE Spectrum Concurrency (SRAN15.1)

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

GSM and LTE Spectrum Concurrency (SRAN15.1)

Transféré par

Droits d'auteur :

Formats disponibles

SingleRAN

GSM and LTE Spectrum

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.................................................................................................................. 3

5 GSM and LTE Spectrum Concurrency Phase 2..................................................................... 62

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. ii

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. iii

1.1 SRAN15.1 Draft A (2018-12-30)

Added the AAU5973e to the list of RF None 3900 series base

Added Downlink Massive CA to the None 3900 series base

Added the mutually exclusive relationship None 3900 series base

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 1

Change Description Parameter Change Base Station

Added the mutually exclusive relationship None 3900 series base

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 2

2 About This Document

2.1 General Statements

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 3

2.2 Features in This Document

Feature ID Feature Name Section

MRFD-130201 GSM and LTE Spectrum 4 GSM and LTE Spectrum

MRFD-130221 GSM and LTE Spectrum

MRFD-131201 GSM and LTE Spectrum 5 GSM and LTE Spectrum

MRFD-131221 GSM and LTE Spectrum

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 4

l A larger non-standard bandwidth during GSM peak hours

The following explains the terms appearing in Figure 3-1:

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 5

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 6

4 GSM and LTE Spectrum Concurrency

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 7

Figure 4-1 Networking architecture of GSM and LTE Spectrum Concurrency

BTS Forwards the information between the BSC and eNodeB.

BE A Huawei proprietary interface introduced between the BSC and eNodeBa

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 8

Interference Coordination on the GSM Side

RRM on the LTE Side

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 9

Therefore, to compensate the loss in the demodulation performance of PDCCHs, the

4.2 Network Analysis

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 10

Table 4-2 LTE downlink capacity gains

≥ 6.2 5 MHz (LTE GSM: 20 W 3 MHz 15%–57% 15%–83%

≥ 10 MHz 10 MHz (LTE GSM: 20 W 5 MHz 41%–98% 41%–

≥ 15 MHz 15 MHz (LTE GSM: 20 W 10 MHz 18%–58% 18%–65%

≥ 20 MHz 20 MHz (LTE GSM: 20 W 15 MHz 7%–43% 7%–47%

Cell capacity = Number of available RBs in a cell x Spectral efficiency =

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 11

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 12

GSM Enhanced GBTS: Enhanced When the Enhanced

GSM Frequency GCELLMAG Frequency When enabled on GSM,

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 13

RAT Function Function Reference Description

GSM BCCH Carrier GCELLFREQ. Frequency When enabled on GSM,

GSM Extended Cell GCELL.EXTT N/A The Extended Cell

GSM BCCH Dense GCELLCHM BCCH Dense The BCCH Dense

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 14

RAT Function Function Reference Description

GSM IBCA II GCELLCHM IBCA II The GSM and LTE

GSM Intelligent GCELLOTHP Intelligent When IBIS is enabled,