GSM and LTE FDD Dynamic Spectrum Sharing (SRAN11.1 - 03)

SingleRAN
SRAN11.1
GSM and LTE FDD Dynamic

Spectrum Sharing Feature
Parameter Description
Issue 03
Date 2016-06-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. 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 03 (2016-06-30) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
SingleRAN
GSM and LTE FDD Dynamic Spectrum Sharing Feature
Parameter Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 1
1.4 Differences Between Base Station Types....................................................................................................................... 3
2 Overview......................................................................................................................................... 4
2.1 Background.....................................................................................................................................................................4
2.2 Introduction.................................................................................................................................................................... 4
2.3 Benefits........................................................................................................................................................................... 5
2.4 Architecture.................................................................................................................................................................... 8
3 Optimization of CS/PS Channel Allocation on the GSM Side.......................................... 10

3.1 GSM Dedicated Carriers and Shared Carriers..............................................................................................................11
3.2 GSM CS Channel Allocation Management..................................................................................................................12
3.2.1 GSM TCH Allocation................................................................................................................................................12
3.2.2 GSM CS Channel Migration..................................................................................................................................... 15
3.2.3 GSM Non-Better-Cell Handover...............................................................................................................................16
3.3 GSM PS Channel Allocation Management.................................................................................................................. 16
3.3.1 Static PDCH Configuration Management................................................................................................................. 16
3.3.2 PDCH Allocation.......................................................................................................................................................17
4 Resource Allocation and Scheduling on the LTE Side........................................................ 19

4.1 Downlink Scheduling................................................................................................................................................... 19
4.1.1 Sending the Shared Frequency Usage from the GSM Side.......................................................................................19
4.1.2 Calculating the RB SINR by the eCoordinator......................................................................................................... 20
4.2 Uplink Scheduling........................................................................................................................................................ 21
4.2.1 PUSCH Scheduling Optimization............................................................................................................................. 21
4.2.2 Uplink Narrowband Interference Suppression.......................................................................................................... 21
4.2.3 PUCCH Optimization................................................................................................................................................22
4.2.4 SRS Channel Allocation Optimization......................................................................................................................23
5 Related Features...........................................................................................................................24
5.1 MRFD-090201 GSM and LTE FDD Dynamic Spectrum Sharing(GSM)................................................................... 24
5.2 MRFD-090202 GSM and LTE FDD Dynamic Spectrum Sharing (LTE FDD)........................................................... 28
Issue 03 (2016-06-30) Huawei Proprietary and Confidential ii

SingleRAN
Parameter Description Contents
6 Network Impact........................................................................................................................... 31
6.1 MRFD-090201 GSM and LTE FDD Dynamic Spectrum Sharing(GSM)................................................................... 31
6.2 MRFD-090202 GSM and LTE FDD Dynamic Spectrum Sharing(LTE FDD)............................................................ 32
7 Engineering Guidelines............................................................................................................. 33
7.1 When to Use................................................................................................................................................................. 34
7.2 Required Information................................................................................................................................................... 34
7.3 Planning........................................................................................................................................................................ 47
7.3.1 RF Planning............................................................................................................................................................... 47
7.3.2 Network Planning...................................................................................................................................................... 48
7.3.3 Hardware Planning.................................................................................................................................................... 49
7.4 Deployment.................................................................................................................................................................. 49
7.4.1 Requirements............................................................................................................................................................. 49
7.4.2 Precautions.................................................................................................................................................................51
7.4.3 Data Preparation and Feature Activation...................................................................................................................51
7.4.3.1 Data Preparation..................................................................................................................................................... 51
7.4.3.2 Using the CME....................................................................................................................................................... 60
7.4.3.3 Using MML Commands......................................................................................................................................... 61
7.4.3.4 MML Command Examples.................................................................................................................................... 63
7.4.4 Activation Observation..............................................................................................................................................64
7.4.5 Deactivation...............................................................................................................................................................66
7.4.5.1 Using the CME....................................................................................................................................................... 67
7.4.5.2 Using MML Commands......................................................................................................................................... 67
7.4.5.3 MML Command Examples.................................................................................................................................... 67
7.4.6 Reconfiguration......................................................................................................................................................... 68
7.5 Performance Monitoring...............................................................................................................................................68
7.6 Parameter Optimization................................................................................................................................................ 69
7.7 Possible Issues.............................................................................................................................................................. 70
8 Parameters..................................................................................................................................... 71
9 Counters...................................................................................................................................... 117
10 Glossary..................................................................................................................................... 120
11 Reference Documents............................................................................................................. 121
Issue 03 (2016-06-30) Huawei Proprietary and Confidential iii

SingleRAN
Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes GSM and LTE FDD Dynamic Spectrum Sharing, including its
technical principles, related features, network impact, and engineering guidelines.
This document covers the following features:
l MRFD-090201 GSM and LTE FDD Dynamic Spectrum Sharing(GSM)

l MRFD-090202 GSM and LTE FDD Dynamic Spectrum Sharing(LTE FDD)
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein

l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier
version
SRAN11.1 03 (2016-06-30)
This issue includes the following changes.
Issue 03 (2016-06-30) Huawei Proprietary and Confidential 1

SingleRAN
Change Change Description Paramete

Type r Change
Feature Added descriptions of the LEOFD-111302 Flexible Bandwidth None

change based on Overlap Carriers feature in the "Mutually Exclusive
Features" section in 5.2 MRFD-090202 GSM and LTE FDD
Dynamic Spectrum Sharing (LTE FDD).
Editorial None None

change
SRAN11.1 02 (2016-04-20)
Change Change Description Parameter

Type Change
Feature Added the GSM tight frequency reuse scenario as an None

change unrecommended scenario in 7.1 When to Use.
Editorial Added GBFD-113201 Concentric Cell to the list of impacted None

change features in 5.1 MRFD-090201 GSM and LTE FDD
Dynamic Spectrum Sharing(GSM).
SRAN11.1 01 (2016-02-29)
Change Change Description Parameter Change

Type
Feature None None

change
Editorial Added the following features to the list of None

change mutually exclusive features in 5.2 MRFD-090202
GSM and LTE FDD Dynamic Spectrum
Sharing (LTE FDD):
l LEOFD-111302 Flexible Bandwidth based on
Overlap Carriers
l LOFD-070208 Coordinated Scheduling based
Power Control
SRAN11.1 Draft A (2015-12-30)

Draft A (2015-12-30) of SRAN11.1 includes the following changes to Issue 02 (2015-06-27)
of SRAN10.1.

SingleRAN
Change Change Description Parameter Change

Type
Feature Added flexible exclusive scheduling of Added the following

change shared RBs for LTE on the downlink. parameters:
For details, see 4.1.2 Calculating the l SpecShrPfmOptSwitch
RB SINR by the eCoordinator.
l SinrThdWithoutGsmInterf
Added avoidance of GSM interference
for LTE on the uplink. For details, see l GsmInterfINThd
4.2.1 PUSCH Scheduling
Optimization.
For the engineering guidelines for these
functions, see the following sections:
l 7.4.3.1 Data Preparation
l 7.4.3.4 MML Command Examples
l 7.5 Performance Monitoring
l 7.6 Parameter Optimization
Added the support of this feature by the None

UBBPe boards. For details, see 7.4.1
Requirements.
Editorial Revised descriptions in the "Using the None

change CME" section in engineering guidelines.
Revised the format in 5 Related None

Features.
1.4 Differences Between Base Station Types

The features described in this document apply only to macro base stations.

SingleRAN
Parameter Description 2 Overview
2 Overview
2.1 Background
The popularization of intelligent terminals accelerates the migration of users to next-
generation networks. As CS and PS traffic loads on GSM networks lighten, operators expect
to release some GSM spectrums and reuse them in LTE networks. To achieve this in areas co-
served by GSM and LTE networks, the GSM and LTE FDD Dynamic Spectrum Sharing
feature is applied. This feature fully utilizes idle GSM spectrums during off-peak hours to
improve spectral efficiency and satisfy the bandwidth requirement of LTE networks, thereby
improving the competitiveness of LTE networks.
2.2 Introduction
GL DSS allows some GSM spectrums to be shared by GSM and LTE networks.
The eCoordinator implements joint allocation and scheduling of the shared spectrums. If a
GSM network does not use the shared spectrums or causes minor interference to an LTE
network, the LTE network can use the shared spectrums to meet its high bandwidth
requirements.
The following lists the basic concepts of GL DSS.
l Dedicated spectrum
The GSM dedicated spectrum can be used only by GSM networks, whereas the LTE
dedicated spectrum can be used only by LTE networks.
In the system bandwidth, radio bearers (RBs) that are not shared by high and low LTE
frequency bands through parameter configuration are called statically exclusive RBs.
When flexible exclusive scheduling of shared RBs is enabled, statically shared RBs that
do not experience interference from GSM shared frequencies and can be used with
statically exclusive RBs are called dynamically exclusive RBs. Figure 2-1 shows details.
l Shared spectrum
The shared spectrum can be shared by both GSM and LTE networks. GSM networks can
preferentially use the shared spectrum.
When the GSM network does not use the shared spectrum, the LTE network can
determine whether to carry PDSCHs or PDCCHs on the shared spectrum.

SingleRAN
In the system bandwidth, RBs that are shared by high and low LTE frequency bands
through parameter configuration are called statically shared RBs.
When flexible scheduling of shared spectrum (FlexSpecSchSwitch) is enabled, a
spectrum free from GSM interference among the shared spectrum can be used as an
additional LTE dedicated spectrum, as shown in Figure 2-1.
Figure 2-1 Dedicated and shared spectrums
NOTE
For details about how the LTE network determines whether to carry PDSCHs or PDCCHs on the shared
spectrum, see 4.1.2 Calculating the RB SINR by the eCoordinator.
2.3 Benefits
This feature provides the following benefits:
l Improves spectral efficiency by fully utilizing spectrum resources.
l Increases the LTE network throughput.
If the spectrum available to LTE after refarming is still insufficient, enabling this feature
allows the LTE network to use the shared spectrum to meet its standard bandwidth
requirement.
As shown in Figure 2-2, GSM and LTE networks each occupy 10 MHz on the 1800
MHz frequency band. After 2 MHz GSM spectrum is refarmed for the LTE network, the
LTE spectrum reaches 12 MHz. Then, the GSM network contributes 3 MHz spectrum to
be shared with LTE networks. So a total of 15 MHz, the standard bandwidth, is available
to LTE networks. After this feature is activated in this scenario:
– The LTE downlink network capacity increases by 15% to 45%.
– The GSM call drop rate increases by 0.08% and the MOS decreases by less than
0.12 points.

SingleRAN
Figure 2-2 Spectrum distribution before and after enabling the feature
The gains in LTE throughput depend on the GSM traffic volume on the shared spectrum and
the bandwidth of the shared spectrum, as described in Table 2-1.
Table 2-1 LTE throughput gains

Scenario DL LTE Throughput DL LTE UL LTE Throughput
Gains Throughput Gains
(During Busy Hours Gains
When GSM Occupies (During Off-
90% Shared Peak Hours
Spectrum or Higher) When GSM
Does Not
Occupy the
Shared
Spectrum)
Scenario 1: More than 40% Up to 90% About 15%

l Total
spectrum: 15
MHz
l GSM
dedicated
spectrum: 5
MHz
l LTE dedicated
spectrum: 8
MHz
l Shared
spectrum: 2
MHz
Comparison
scenario: LTE 5
MHz

SingleRAN
Scenario DL LTE Throughput DL LTE UL LTE Throughput

Gains Throughput Gains
(During Busy Hours Gains
When GSM Occupies (During Off-
90% Shared Peak Hours
Spectrum or Higher) When GSM
Does Not
Occupy the
Shared
Spectrum)

l Total
spectrum: 20
MHz
l GSM
dedicated
spectrum: 5
MHz
l LTE dedicated
spectrum: 12
MHz
l Shared
spectrum: 3
MHz
Comparison
scenario: LTE 10
MHz

l Total
spectrum: 30
MHz
l GSM
dedicated
spectrum: 10
MHz
l LTE dedicated
spectrum: 16
MHz
l Shared
spectrum: 4
MHz
Comparison
scenario: LTE 15
MHz

SingleRAN
NOTE
The gains in this table are obtained in typical test scenarios when UEs (model: E392) are used.
Throughput gains vary according to UE models and network scenarios.
2.4 Architecture
Figure 2-3 shows the architecture for information exchange between NEs during the
implementation of GL DSS.
Figure 2-3 Architecture for information exchange between NEs
Table 2-2 describes the functions of NEs during the implementation of this feature.
Table 2-2 Functions of NEs during the implementation of this feature

NE Function
BSC l Sends the GSM frequency usage on the shared spectrum to the
eCoordinator in real time.
l First allocates the GSM dedicated spectrum and then the shared
spectrum to CS or PS services. For details, see 3 Optimization of
CS/PS Channel Allocation on the GSM Side.

SingleRAN
NE Function
eCoordinator l Updates the GSM frequency usage on the shared spectrum in real
time.
l Maintains LTE cell information in real time. The LTE cell
information includes LTE bandwidth, central E-UTRA absolute radio
frequency channel number (EARFCN), number of resource blocks
(RBs) on the high frequency band of the shared spectrum, and
number of RBs on the low frequency band of the shared spectrum.
l Calculates the current signal to interference plus noise ratio (SINR)
on each RB of the shared spectrum in each LTE cell. It then sends the
SINR to the eNodeB, based on the cell-level GL interference matrix
generated from the GSM measurement report (MR) data and the
GSM frequency usage on the shared spectrum.
l Sends the GSM frequency usage on the shared spectrum to the co-
sited eNodeB. The eNodeB then determines the availability of
PDCCH resource elements (PDCCH REs) on the shared spectrum.
eNodeB l Determines whether the shared spectrum is used and how to allocate
the RBs on the shared spectrum based on the SINR value sent from
the eCoordinator.
l Decides not to send symbols corresponding to PDCCH REs of the
shared spectrum to UEs. For details, see 4 Resource Allocation and
Scheduling on the LTE Side.

SingleRAN
GSM and LTE FDD Dynamic Spectrum Sharing Feature 3 Optimization of CS/PS Channel Allocation on the GSM
Parameter Description Side
3 Optimization of CS/PS Channel Allocation

on the GSM Side
To enable GL DSS on the GSM side, set GLDSSSw(BSC6900,BSC6910) to ON(On). After

this feature is enabled, CS/PS channel allocation is optimized.

SingleRAN
3.1 GSM Dedicated Carriers and Shared Carriers

After this feature is enabled in GSM cells, GSM carriers are divided into GSM dedicated
carriers and shared carriers. They are distinguished according to the following rules:
1. Calculate the FDL using the following formula:

FDL = FDL_low + 0.1 (NDL – NOffs-DL)
where
FDL indicates the frequency corresponding to the downlink ARFCN and NDL indicates
the downlink ARFCN, which is the same as the value of
CELLGLDSS.LTEDlCenterFreq(BSC6900,BSC6910).
FDL_low and NOffs-DL can be obtained according to the setting of
CELLGLDSS.LTEDlCenterFreq(BSC6900,BSC6910) and the information listed in
Table 3-1. CELLGLDSS.LTEDlCenterFreq(BSC6900,BSC6910) corresponds to
Range of NDL in the table.
2. Determine the LTE spectrum range based on the value of FDL and the value of
CELLGLDSS.LTEBandWidth. Specifically, the LTE spectrum range is [FDL –
CELLGLDSS.LTEBandWidth(BSC6900,BSC6910)/2, FDL +
CELLGLDSS.LTEBandWidth(BSC6900,BSC6910)/2].
If the frequency corresponding to a GSM ARFCN on a carrier partially or completely falls

within the range [FDL – CELLGLDSS.LTEBandWidth(BSC6900,BSC6910)/2, FDL +
CELLGLDSS.LTEBandWidth(BSC6900,BSC6910)/2], the carrier can be shared. Otherwise,
the carrier is GSM dedicated.
NOTE
This feature applies only to GSM1800 MHz common cell networking. Therefore, set
CELLGLDSS.LTEDlCenterFreq(BSC6900,BSC6910) to a value ranging from 1200 to 1949.
Table 3-1 E-UTRA operating bands
Band Downlink
FDL_low NOffs-DL Range of NDL

(MHz)
1 2110 0 0 – 599
2 1930 600 600 – 1199
3 1805 1200 1200 – 1949
4 2110 1950 1950 – 2399
5 869 2400 2400 – 2649
6 875 2650 2650 – 2749
7 2620 2750 2750 – 3449
8 925 3450 3450 – 3799

SingleRAN
9 1844.9 3800 3800 – 4149
10 2110 4150 4150 – 4749
11 1475.9 4750 4750 – 4999
12 729 5010 5010 – 5179
13 746 5180 5180 – 5279
14 758 5280 5280 – 5379
... ... ... ...
33 1900 26000 26000 – 26199
34 2010 26200 26200 – 26349
35 1850 26350 26350 – 26949
36 1930 26950 26950 – 27549
37 1910 27550 27550 – 27749
38 2570 27750 27750 – 28249
39 1880 28250 28250 – 28649
40 2300 28650 28650 – 29649
In special networking scenarios, only individual GSM BCCH frequencies need to be included
in the LTE bandwidth. These frequencies can be included only in the LTE guard bandwidth on
the shared spectrum. In this situation, the
CELLGLDSS.BCCHFreqShareSw(BSC6900,BSC6910) switch must be turned on on the
GSM side.
NOTE
When GL DSS is enabled, it is not recommended that BCCH frequencies be included in the shared
spectrum. To include BCCH frequencies in the shared spectrum, contact Huawei technical support.
3.2 GSM CS Channel Allocation Management
3.2.1 GSM TCH Allocation

After this feature is enabled, TCH allocation is optimized as follows:
When CELLGLDSS.SharedTrxPwrDecrSw(BSC6900,BSC6910) is set to ON(On), the
BSC decreases the static transmit power of GSM shared carriers to reduce the GSM-to-LTE
interference. If a majority of TCHs on the GSM dedicated carriers are occupied, the BSC
preferentially allocates TCHs on the shared carriers to CS users at the center of a cell. The
details are as follows:
l The BSC decreases the static transmit power of the shared carriers by
CELLGLDSS.SharedTrxPwrDecrLev(BSC6900,BSC6910) multiplied by 0.2.

SingleRAN
l The BSC preferentially allocates a TCH on a shared carrier to a newly admitted CS call
when all of the following conditions are met.
The BSC preferentially allocates a TCH on a GSM dedicated carrier to the newly
admitted call if the following conditions are not met:
– Number of available TCHs on the GSM dedicated carriers ≤
CELLGLDSS.AloneTrxResvChanNum(BSC6900,BSC6910)
– Difference between the downlink receive level and the optimal neighboring cell
level for the call ≥ CELLGLDSS.GlDssAtcbThld(BSC6900,BSC6910)
– Difference between the downlink receive level and
CELLGLDSS.SharedTrxRxLevThld(BSC6900,BSC6910) for the call ≥ 0.2 x
CELLGLDSS.SharedTrxPwrDecrLev(BSC6900,BSC6910)
l Handover from shared carriers to dedicated carriers
If CS calls are allocated TCHs on the GSM dedicated carriers and the number of
available TCHs on the GSM dedicated carriers is less than the value of
CELLGLDSS.AloneTrxResvChanNum(BSC6900,BSC6910), a CS call can be handed
over from a GSM dedicated carrier to a shared carrier when both of the following
conditions are met:
level for the call ≥ CELLGLDSS.GlDssAtcbThld(BSC6900,BSC6910)
– Difference between the downlink receive level and
CELLGLDSS.SharedTrxRxLevThld(BSC6900,BSC6910) for the call ≥ 0.2 x
CELLGLDSS.SharedTrxRxLevThld(BSC6900,BSC6910)
l Handover from shared carriers to dedicated carriers
A CS call can be handed over from a shared carrier to a GSM dedicated carrier when
either of the following conditions is met:
level for the call < CELLGLDSS.GlDssAtcbThld(BSC6900,BSC6910) -
CELLGLDSS.GlDssAtcbHYST(BSC6900,BSC6910)
– Downlink receive level for the call <
CELLGLDSS.SharedTrxRxLevThld(BSC6900,BSC6910) -
CELLGLDSS.SharedTrxRxLevHYST(BSC6900,BSC6910)
When CELLGLDSS.SharedTrxPwrDecrSw(BSC6900,BSC6910) is set to OFF(Off), the
BSC preferentially allocates TCHs on GSM dedicated carriers to CS services. If no TCHs are
available on GSM dedicated carriers, the BSC allocates TCHs on shared carriers to the CS
services.
The priorities of GSM dedicated and shared carriers are as follows:
l All GSM dedicated carriers have the same priority.
l The longer the spacing between the ARFCN of a shared carrier and the central EARFCN
specified by CELLGLDSS.LTEDlCenterFreq(BSC6900,BSC6910), the higher the
priority of the shared carrier. If the respective spacings between the ARFCNs of two
shared carriers and the central EARFCN specified by
CELLGLDSS.LTEDlCenterFreq(BSC6900,BSC6910) are the same, the shared carrier
with the smaller ARFCN has a higher priority.
NOTE
When CELLGLDSS.SharedTrxPwrDecrSw(BSC6900,BSC6910) is set to ON(On), the RRU

will reset, which affects services in GSM and LTE cells on the RRU. Therefore, it is recommended
that this parameter be set to ON(On) at an appropriate time.

SingleRAN
Half-Rate Adjustment for GSM Dedicated Carriers and Shared Carriers

When CELLGLDSS.AloneTrxHrLdThldOffset(BSC6900,BSC6910) is set to a value other
than 0, different TCHF-to-TCHH conversion thresholds are provided for TCH allocation on
shared carriers and GSM dedicated carriers. This setting allows more calls to be carried on
GSM dedicated carriers and enables shared carriers to be used by LTE services, thereby
ensuring LTE data rate gains during peak hours on the GSM network.
When a non-AMR call is initiated or

GCELLCHMGAD.AMRTCHHPRIORALLOW(BSC6900,BSC6910) is set to OFF(Off):
l If the traffic load of GSM dedicated carriers is higher than or equal to the result of
GCELLCHMGAD.TCHBUSYTHRES(BSC6900,BSC6910) minus
CELLGLDSS.AloneTrxHrLdThldOffset(BSC6900,BSC6910), TCHHs are allocated to
calls on GSM dedicated carriers.
NOTE
If GCELLCHMGAD.TCHBUSYTHRES(BSC6900,BSC6910) is less than or equal to

CELLGLDSS.AloneTrxHrLdThldOffset(BSC6900,BSC6910), the result will be 0 or a negative
value. In such a case, the result is considered 0.
l If the traffic load of GSM dedicated carriers is higher than or equal to
calls on shared carriers.
When an AMR call is initiated or

GCELLCHMGAD.AMRTCHHPRIORALLOW(BSC6900,BSC6910) is set to ON(On):
l If the traffic load of GSM dedicated carriers is higher than or equal to the result of
GCELLCHMGAD.AMRTCHHPRIORALLOW(BSC6900,BSC6910) minus
AMR calls on GSM dedicated carriers. If
GCELLCHMGAD.TCHBUSYTHRES(BSC6900,BSC6910) is less than or equal to
CELLGLDSS.AloneTrxHrLdThldOffset(BSC6900,BSC6910), the result will be 0 or a
negative value. In such a case, the result is considered 0.
l If the traffic load of shared carriers is higher than or equal to
GCELLCHMGAD.AMRTCHHPRIORALLOW(BSC6900,BSC6910), TCHHs are
allocated to AMR calls on shared carriers.
Interference Suppression Protection in GSM Handover Scenarios

After the handover decision for a CS call on a shared carrier succeeds, the BSC sends a
message to the eCoordinator if the following condition is met:
(Level of the target cell or level of a neighboring cell – Level of the serving cell) ≥
CELLGLDSS.SharedTrxInterfHoAtcbThld(BSC6900,BSC6910)
This message contains the following information:

l Cell global identification (CGI) of the serving GSM cell
Shared frequency that cannot be used by a co-sited co-coverage LTE cell of the serving
GSM cell, that is, the shared frequency occupied by the target GSM cell
l CGI of the target GSM cell
Shared frequency that cannot be used by a co-sited co-coverage LTE cell of the target
GSM cell, that is, the shared frequency occupied by the serving GSM cell

SingleRAN
l CGIs of candidate neighboring GSM cells

Shared frequencies that cannot be used by co-sited co-coverage LTE cells of the
candidate neighboring GSM cell, that is, the shared frequencies occupied by the serving
GSM cell and the target GSM cell
NOTE
This message can carry a maximum of three candidate neighboring cells with the strongest level except
for the target cell.
As shown in Figure 3-1, upon receipt of a message from the BSC, the eCoordinator instructs
the eNodeB not to schedule the RBs corresponding to the shared frequencies that cannot be
used and starts the timer specified by the RBStatusTimer parameter. When the timer expires,
the eCoordinator sends the eNodeB a message, informing the eNodeB that the RBs can be
scheduled.
Figure 3-1 Interaction between the BSC, eCoordinator, and eNodeB
NOTE
For details about TCH allocation, see Channel Management Feature Parameter Description for GBSS.
3.2.2 GSM CS Channel Migration

If some CS calls occupy the channels on the shared carriers for an extended period, the
spectrum of the shared carriers cannot be released for LTE networks even when the loads on
GSM dedicated carriers lighten. To prevent this situation, GSM CS channel migration is
introduced.
GSM CS channel migration complies with the following rules:
1. For users on the shared carriers, the number of TCH MRs increases by 1 each time an
MR is received on a TCH. The following users are excluded:
– DTM users
– VAMOS FR users
– VAMOS HR users
– Emergency call users
2. A user is handed over from a shared carrier to a GSM dedicated carrier or another
higher-priority shared carrier when both of the following conditions are met:
– Number of TCH MRs ≥ CELLGLDSS.LongCallDetThld(BSC6900,BSC6910)
– Number of idle TCHs on GSM dedicated carriers + Number of idle TCHs on other
higher-priority shared carriers (a shared carrier whose ARFCN is further away from

SingleRAN
the central EARFCN has a higher priority) >

CELLGLDSS.CsRepackingTchIdleNum(BSC6900,BSC6910)
3.2.3 GSM Non-Better-Cell Handover

When making a GSM handover decision, the BSC considers the layer, load, and signal level
of a candidate cell. Therefore, the target cell may not have the highest signal level. When the
GL DSS feature is enabled, the interference from LTE cells to GSM cells causes the handover
success rate to decrease. To suppress the interference from LTE and increase the handover
success rate, the GSM handover algorithm is optimized as follows:
l When CELLGLDSS.GlDssHoOptSw(BSC6900,BSC6910) is set to ON(On) and

GCELLHOBASIC.LoadHoEn(BSC6900,BSC6910) is set to NO(No), the BSC does
not consider the layer information contained in the layer bits (bits 5 to 10) during 16-bit
candidate cell queuing for quality-based handovers and level-based handovers in
handover algorithm I. In this case, the load bit (bit 11) does not take effect.
l When CELLGLDSS.GlDssHoOptSw(BSC6900,BSC6910) is set to ON(On) and
GCELLHOBASIC.LoadHoEn(BSC6900,BSC6910) is set to YES(Yes), the BSC does
not consider the layer information contained in bits 5 to 10 or the load information
contained in bit 11 during 16-bit candidate cell queuing for quality-based handovers and
level-based handovers in handover algorithm I. The BSC always considers the layer and
load bits for handovers other than quality-based and level-based handovers.
In handover algorithm II, when GCELLHOBASIC.HOPRIOMODEN(BSC6900,BSC6910)

is set to OFF(Off), the BSC only considers the signal level regarding bad quality (BQ)
handovers, handovers due to no downlink MRs, and edge handovers. This way, the target cell
has the highest signal level. Therefore, when handover algorithm II is used, it is recommended
that GCELLHOBASIC.HOPRIOMODEN(BSC6900,BSC6910) be set to OFF(Off) and
GCELLHOBASIC.FRINGEHOEN(BSC6900,BSC6910) be set to ON(On).
3.3 GSM PS Channel Allocation Management
3.3.1 Static PDCH Configuration Management

After this feature is introduced, static PDCHs can be configured only on GSM dedicated
carriers. Therefore, the BSC checks whether static PDCHs are mistakenly configured on
shared carriers in a cell in the following scenarios:
l The value of CELLGLDSS.GLDSSSw(BSC6900,BSC6910) is changed from OFF(Off)

to ON(On).
l CELLGLDSS.GLDSSSw(BSC6900,BSC6910) is set to ON(On), and frequency
configuration changes.
l CELLGLDSS.GLDSSSw(BSC6900,BSC6910) is set to ON(On), and the graphic user
interface (GUI) value of CELLGLDSS.LTEBandWidth(BSC6900,BSC6910) changes.
l CELLGLDSS.GLDSSSw(BSC6900,BSC6910) is set to ON(On), and the GUI value of
CELLGLDSS.LTEDlCenterFreq(BSC6900,BSC6910) changes.
If the BSC determines that static PDCHs have been configured on the shared carriers in a cell,
the BSC LMT displays this configuration and prompts users to query the number of the GSM
dedicated carrier in the cell by running the LST GTRX command and then modify the static
PDCH configuration.

SingleRAN
3.3.2 PDCH Allocation

After this feature is introduced, PDCH allocation is optimized as follows:
l When the load of a PDCH group is light, the BSC preferentially allocates PDCHs on
GSM dedicated carriers to PS services.
l The BSC preferentially performs dynamic PDCH conversion on GSM dedicated carriers.
NOTE
For details about PDCH allocation, see GPRS EGPRS Channel Management Feature Parameter
Description for GBSS.
To optimize PDCH allocation, set GCELLPSCHM.EnPDAdminOpt(BSC6900,BSC6910) to

ON(On) to optimize channel allocation and channel conversion.
Channel Allocation Optimization

Channel allocation policies differ in the following situations:
l Average load of a PDCH group in the uplink/downlink channel allocation (including the
load of the current channel allocation) >
CELLGLDSS.GlDssPsUlLoadThd(BSC6900,BSC6910)/
CELLGLDSS.GlDssPsDlLoadThd(BSC6900,BSC6910). In this situation, PDCHs on
GSM dedicated and shared carriers have the same priority, and the existing PDCH
allocation policy is applied.
l Average load of a PDCH group in the uplink/downlink channel allocation (including the
load of the current channel allocation) ≤
CELLGLDSS.GlDssPsUlLoadThd(BSC6900,BSC6910)/
CELLGLDSS.GlDssPsDlLoadThd(BSC6900,BSC6910). In this situation, the PDCHs
on GSM dedicated carriers are preferentially allocated. If no PDCHs are available on the
GSM dedicated carriers, those on shared carriers are allocated. For details about how the
BSC determines the priorities of GSM dedicated and shared carriers, see 3.2.1 GSM
TCH Allocation.
Channel Conversion Optimization

GPRS channel conversion policies are the same as EGPRS. The details are as follows:
l Channel conversion triggered by low multislot capability can be performed only on GSM
dedicated carriers.
l If the uplink and downlink GPRS TBF multiplexing rates in a cell are less than or equal
to the values of CELLGLDSS.GlDssPsUlLoadThd(BSC6900,BSC6910) and
CELLGLDSS.GlDssPsDlLoadThd(BSC6900,BSC6910), respectively, channel
conversion for GPRS services can be performed only on GSM dedicated carriers. The
number of uplink and downlink channels to be converted can be calculated based on the
values of GCELLPSCHM.UPDYNCHNTRANLEV(BSC6900,BSC6910) and
GCELLPSCHM.DWNDYNCHNTRANLEV(BSC6900,BSC6910), respectively.
l If the uplink and downlink GPRS TBF multiplexing rates in a cell are greater than the
value of CELLGLDSS.GlDssPsUlLoadThd(BSC6900,BSC6910) and the value of
CELLGLDSS.GlDssPsDlLoadThd(BSC6900,BSC6910), respectively, channel
conversion for GPRS services can be performed on both GSD dedicated and shared
carriers. The number of uplink and downlink channels to be converted can be calculated
based on the values of CELLGLDSS.GlDssPsUlLoadThd(BSC6900,BSC6910) and
CELLGLDSS.GlDssPsDlLoadThd(BSC6900,BSC6910), respectively.

SingleRAN
– The channel conversion priorities of exclusive and shared carriers that carry PDCHs
are the same.
– If no PDCHs are available on shared carriers or GSM dedicated carriers, channel
conversion is preferentially performed on GSM dedicated carriers. The channel
conversion priorities of GSM dedicated and shared carriers are the same as those of
channel allocation optimization.

SingleRAN
Parameter Description 4 Resource Allocation and Scheduling on the LTE Side
4 Resource Allocation and Scheduling on the

LTE Side
4.1 Downlink Scheduling

Figure 4-1 illustrates the flowchart of downlink scheduling of LTE users.
Figure 4-1 Downlink scheduling of LTE users
4.1.1 Sending the Shared Frequency Usage from the GSM Side
When CS services occupy channels on a shared carrier for the first time or when TCHs on a
shared carrier are converted to PDCHs in a GSM cell and are not occupied by CS services, the
BSC notifies the eCoordinator of the shared frequency usage. In this situation, the BSC sends
a CHANNEL ACT message to the BTS at a delay specified by
CELLGLDSS.TchActDelay(BSC6900,BSC6910).
The BSC notifies the eCoordinator of the shared frequency release status when both of the
following conditions are met:
l The last CS service on the shared carriers is released in a GSM cell.
l The total number of idle TCHs on GSM dedicated carriers and on other higher-priority
shared carriers is greater than or equal to the value of
CELLGLDSS.ECOMSGIdleTchNum(BSC6900,BSC6910). Alternatively, the last
PDCH is converted to a TCH and is not occupied by any call.

SingleRAN
The BSC sends the shared frequency usage to the eCoordinator every 10 minutes.
4.1.2 Calculating the RB SINR by the eCoordinator

The RB SINR for LTE networks is obtained based on the GSM-to-LTE interference matrix,
the shared frequency usage in GSM cells, and the location of users in a cell.
The eCoordinator then sends the LTE RB SINR and the GSM frequency usage on the shared
spectrum to the co-sited eNodeB. The eNodeB then determines the availability of PDCCH
REs on the shared spectrum.
PDSCH Scheduling Optimization

After the GLDynSpectrumShareSwitch(GLDynSpectrumShareSwitch) option under
CellAlgoSwitch.DynSpectrumShareSwitch is selected, LTE PDSCH scheduling is optimized
as follows:
l The eNodeB schedules either the LTE dedicated spectrum or the shared spectrum for
each user in each transmission time interval (TTI).
l The eNodeB preferentially allocates RBs on the LTE dedicated spectrum in each TTI. If
no RBs on the LTE dedicated spectrum are available, the eNodeB allocates those on the
shared spectrum.
l The eNodeB determines the location of users according to the reference signal received
power (RSRP) obtained from the A3 measurement event reported by users. The eNodeB
then queries the RB SINR based on RSRP and user location.
– If the SINR of a shared RB is greater than or equal to the value of the
CELLDSS.NearAreaSinrThd parameter, the shared RB can be scheduled by UEs
in the center of a cell.
CELLDSS.MiddleAreaSinrThd parameter, the shared RB can be scheduled by
UEs between the cell center and cell edge.
CELLDSS.FarAreaSinrThd parameter, the shared RB can be scheduled by UEs at
the edge of a cell.
A spectrum providing shared RBs can be used as the additional LTE dedicated spectrum
when FlexSpecSchSwitch under the CELLDSS.SpecShrPfmOptSwitch parameter is set
to ON and the SINR of the shared RB is greater than the value of the
CELLDSS.SinrThdWithoutGsmInterf parameter.
With GL DSS, the CELLDSS.A3Offset parameter is added to the A3 measurement. This
parameter specifies the level offset between the serving cell and its neighboring cell that
reports RSRP. If the Carrier Aggregation feature is enabled, the A6 measurement event
must be also triggered on the same frequency band to obtain the RSRP values of
secondary serving cells and their neighboring cells on the same frequency band. The
obtained RSRP values are used to determine the attribute range of users in secondary
serving cells in the same way as that of primary cells. With GL DSS, the
CELLDSS.A6Offset parameter is added to the A6 measurement. This parameter
specifies the level offset between the secondary serving cell in CA and its neighboring
cell that reports RSRP. When the value of CELLDSS.A6Offset or CELLDSS.A6Offset
is set to a value as small as possible, UEs can report the RSRP of serving cells and
neighboring cells as often as possible to meet GL DSS measurement requirements.

SingleRAN
NOTE
l GL DSS is not supported in inter-site carrier aggregation scenarios.

l When GL DSS is used in downlink carrier aggregation scenarios, it is recommended that the carrier
enabled with GL DSS be configured as a primary component carrier (PCC). If a secondary
component carrier (SCC) is enabled with GL DSS, UEs incapable of reporting the A6 event cannot
use shared RB resources. GL DSS delivers small gains for such UEs.
PDCCH Optimization
The eNodeB determines whether the PDCCH REs of the shared spectrum in LTE cells are
available based on the GSM frequency usage. If both
CellAlgoSwitch.DynSpectrumShareSwitch and CellDss.REMuteSwitch are set to ON(On),
the eNodeB does not send unavailable PDCCH REs of the shared spectrum to UEs.
NOTE
CellDss.REMuteSwitch controls not only whether the eNodeB sends the PDCCH RE of the shared
spectrum occupied by GSM networks, but also whether the eNodeB sends the cell-specific reference
signal (CRS) of the shared spectrum occupied by the GSM networks.
4.2 Uplink Scheduling
4.2.1 PUSCH Scheduling Optimization

After CellAlgoSwitch.DynSpectrumShareSwitch is set to ON(On), only the bandwidth
resources of the LTE dedicated spectrum are scheduled for uplink PUSCHs. RB resources on
the shared spectrum cannot be scheduled.
When UlSchInterfAvdSwitch under the CellDss.SpecShrPfmOptSwitch parameter is set to
ON and if frequency selection has not started for uplink scheduling, the interference of the
GSM dedicated spectrum on the two ends of the LTE bandwidth is determined based on
CellDss.GsmInterfINThd. PUSCH RBs are allocated from the end with weaker GSM
interference in the LTE bandwidth.
4.2.2 Uplink Narrowband Interference Suppression

During the uplink signal reception by the eNodeB in each TTI, the interference of inband
shared frequencies in GSM cells causes inband interference in LTE cells to increase after Fast
Fourier Transformation (FFT) conversion.
l When CellAlgoSwitch.DynSpectrumShareSwitch is set to ON and
CellDss.UlInterfRestrictionMode is set to
BASEBANDPROCESS(BASEBANDPROCESS), the GSM frequency-domain
interference scope is narrowed and only RBs close to GSM interference sources are
affected. This ensures that RBs far from GSM interference sources and the LTE-
dedicated spectrum work properly and improves LTE performance.
l When CellDss.UlInterfRestrictionMode is set to
ADAPTIVEPROCESS(ADAPTIVEPROCESS), interference can be better suppressed
to further improve LTE performance.
l When CellDss.UlInterfRestrictionMode is set to
INFERIORINTERFPROCESS(INFERIORINTERFPROCESS), only weak GSM
interference is suppressed and eNodeBs are interfered by shared frequencies of only
neighboring GSM BTSs.

SingleRAN
In most cases, it is recommended that CellDss.UlInterfRestrictionMode be set to

ADAPTIVEPROCESS for optimal performance.
The eNodeB must be informed of the interfering frequencies in neighboring GSM cells to
relieve the interference caused by these frequencies in the uplink. When
CellDss.InterfNCellConfigMode is set to ENODEBAIDCONFIG(ENODEBAIDCONFIG)
for the eNodeB, it is recommended that intra-frequency cells under the same site be bound to
the same baseband processing unit. When CellDss.InterfNCellConfigMode is set to
ECOCONFIG(ECOCONFIG), the eCoordinator is configured with neighboring GSM cells
whose frequencies need to be transferred. The eCoordinator can transfer the shared frequency
usage in neighboring GSM cells co-sited with the LTE cell and neighboring GSM cells under
adjacent sites to the eNodeB.
NOTE
On the eCoordinator side, the neighboring GSM cells co-sited with the LTE cell and neighboring GSM
cells under adjacent sites can be configured by running the ADD ELGNCELL command.
4.2.3 PUCCH Optimization

PUCCHs are generally configured at both ends of the LTE operating frequency band. The
GSM power spectrum is denser than the LTE power spectrum and the near-far effect occurs
on the uplink on GSM networks. Therefore, PUCCHs cannot fall into the GSM and LTE
shared spectrum.
After this feature is enabled, PUCCHs are adjusted to the LTE dedicated spectrum.
When the PucchFlexCfgSwitch option under the CellAlgoSwitch.PucchAlgoSwitch
parameter is selected, the number of adjusted RBs is:
MAX{MAX[CellDss.HighFreqShareRbNum, CellDss.LowFreqShareRbNum],
CellDss.PucchExtendedRBNum}
When the PucchFlexCfgSwitch option under the CellAlgoSwitch.PucchAlgoSwitch
parameter is deselected, the number of adjusted RBs is:
MAX{CellDss.HighFreqShareRbNum, CellDss.LowFreqShareRbNum}
When the GLDynSpectrumShareSwitch option under
CellAlgoSwitch.DynSpectrumShareSwitch is selected, the configuration is as follows:
l If the sharing ratio is no greater than 1/5, the number of RBs configured for the PUCCH
is unlimited.
l If the sharing ratio is greater than 1/5, the PucchSwitch option is not selected to ensure
SRS configuration.
When the GLDynSpectrumShareSwitch option under
CellAlgoSwitch.DynSpectrumShareSwitch is selected and the PucchSwitch option under
CellDss.PucchAlgoSwitch is not selected, the number of RBs configured for the PUCCH
must meet the requirements described in Table 4-1, and adaptive adjustment must be
performed on the cell-level SRS bandwidth to ensure SRS configuration.
Table 4-1 Number of RBs configured for the PUCCH

Bandwidth Number of RBs configured for the PUCCH
10 MHz 10
15 MHz 18

SingleRAN
Bandwidth Number of RBs configured for the PUCCH
20 MHz No requirement
If the GUI value of PUCCHCfg.CqiRbNum exceeds the restrictions, the cell-level SRS
bandwidth may fail to be configured, and therefore cells may fail to be established. When GL
DSS is enabled, the eNodeB does not need to verify whether the SRS and PRACH use the
same RB resources.
4.2.4 SRS Channel Allocation Optimization

The uplink sounding reference signal (SRS) for an LTE network is used for uplink TA
measurement and channel estimation. The SRS channel is allocated at the center of the LTE
bandwidth, and the occupied SRS bandwidth is relevant to the PUCCH bandwidth. After GL
DSS is enabled, the PUCCH will be relocated, and the SRS bandwidth will be automatically
adjusted according to available bandwidth.

SingleRAN
Parameter Description 5 Related Features
5 Related Features
5.1 MRFD-090201 GSM and LTE FDD Dynamic Spectrum

Sharing(GSM)
Prerequisite Features
None
Mutually Exclusive Features

Feature ID Feature Name Description
GBFD-117002 IBCA -
GBFD-119511 IBCA II -
GBFD-510104 Multi-site Cell -
Impacted Features
Feature ID Feature Description
Name
GBFD-115 VAMOS GSM CS services preferentially occupy TCHs on the exclusive

830 spectrum. After GL DSS is enabled, the GSM frequency
planning changes. This decreases the number of GSM
frequencies that participate in frequency hopping and therefore
reduces the randomness of GSM intra-network interference. As
a result, GSM network quality deteriorates, the number of users
that meet the VAMOS requirements decreases, and the gains
brought by VAMOS decrease.

SingleRAN

Name
GBFD-111 TRX After GL DSS is enabled, most CS or PS traffic is carried on

602 Power exclusive carriers. As a result, shared carriers become idle. This
Amplifier is more likely to trigger TRX Power Amplifier Intelligent
Intelligent Shutdown. In this case, therefore, the gains brought by TRX
Shutdown Power Amplifier Intelligent Shutdown increase.
GBFD-111 TRX Before GL DSS is enabled, CS or PS traffic is evenly

603 Power distributed on exclusive and shared spectrum. In contrast, after
Amplifier GL DSS is enabled, most CS or PS traffic is carried on the
Intelligent exclusive spectrum. As a result, the probability that timeslots
Shutdown become idle decreases, and the gains brought by TRX Power
on Amplifier Intelligent Shutdown on Timeslot Level decreases
Timeslot accordingly.
Level
GBFD-113 PDCH After GL DSS is enabled, PS services are preferentially

101 Dynamic allocated channels on exclusive carriers, and dynamic channel
Adjustme conversion is also preferentially performed on the exclusive
nt carriers. If a small number of channels are configured on the
exclusive carriers, resources available for PS services decrease,
and consequently the throughput rate deteriorates. If a large
number of channels are configured on the exclusive carriers,
shared resources decrease, and consequently the shared
spectrum resources that can be used by LTE networks lessen.
GBFD-119 Active Before GL DSS is enabled, channel allocation is performed on

407 TBF both exclusive and shared carriers during the implementation of
Allocation Active TBF Allocation. After GL DSS is enabled, channel
allocation is performed only on exclusive carriers if the TBF
multiplexing rate is low in a cell. As a result, the area where the
Active TBF Allocation feature takes effect shrinks and the
gains brought by Active TBF Allocation decrease accordingly.
GBFD-119 PDCH The PDCH Dynamic Adjustment with Two Thresholds feature
505 Dynamic can obtain more PDCHs converted from TCHs to improve user
Adjustme experience on PS services if a large number of channels are idle
nt with in a cell. However, GL DSS aims to reduce the number of
Two occupied PDCHs. Therefore, if both features are enabled,
Threshold PDCH Dynamic Adjustment with Two Thresholds can work
s only on the exclusive carriers.
GBFD-511 IM When radio resource usage exceeds a specific value, these

603 Service features will be triggered. After GL DSS is enabled, PS
Efficiency services are preferentially allocated channels on exclusive
Improvem carriers, and dynamic channel conversion is also preferentially
ent performed on the exclusive carriers. This decreases radio
resource usage and therefore decelerates the triggering of these
features.
If these features are enabled, the formula for calculating the
TBF multiplexing rate changes. If GL DSS is also enabled, the
uplink and downlink TBF multiplexing rates are calculated in

SingleRAN

Name
GBFD-511 Web the same way when GL DSS is not enabled. Then, the obtained
604 Browsing uplink and downlink TBF multiplexing rates are compared with
Service the values of GlDssPsUlLoadThd(BSC6900,BSC6910) and
Efficiency GlDssPsDlLoadThd(BSC6900,BSC6910), respectively.
Improvem Channel conversion is then allowed on the shared carriers when
ent any of the following conditions is met:
l Uplink GPRS TBF multiplexing rate >
GBFD-511 Email
GlDssPsUlLoadThd(BSC6900,BSC6910)
605 Service
Efficiency l Uplink EGPRS TBF multiplexing rate >
Improvem GlDssPsUlLoadThd(BSC6900,BSC6910)
ent l Downlink GPRS TBF multiplexing rate >
GlDssPsDlLoadThd(BSC6900,BSC6910)
GBFD-511 Streaming
l Downlink EGPRS TBF multiplexing rate >
606 Media
GlDssPsDlLoadThd(BSC6900,BSC6910)
Service
Resource
Balancing
GBFD-511 P2P
607 Resource
Balancing

SingleRAN

Name
GBFD-511 Duty- l If Duty-Cycle-based PDCH Management is enabled,

611 Cycle- channels on shared carriers are preferentially rolled back.
based The longer the frequency separation between ARFCNs on a
PDCH shared carrier and the central EARFCN specified by
Managem LTEDlCenterFreq(BSC6900,BSC6910), the higher the
ent rollback priority of the shared carrier. If the frequency
separations between ARFCNs on all the shared carriers and
the central EARFCN are the same, the shared carriers
corresponding to the ARFCNs on the left of the central
EARFCN specified by
LTEDlCenterFreq(BSC6900,BSC6910) have higher
priorities. If ARFCNs on all the shared carriers are on the
left of the central EARFCN specified by
LTEDlCenterFreq(BSC6900,BSC6910) and have the same
frequency separation to the central EARFCN, all the shared
carriers have the same priority. The BSC therefore
randomly selects a shared carrier and rolls back channels on
the shared carrier. The PDCH allocation priorities of
exclusive carriers are the same. If the shared carriers
participate in frequency hopping, the BSC traverses all
ARFCNs on the shared carriers and then determines the
frequency separation between the ARFCN closest to the
central EARFCN on each shared carrier and the EARFCN
specified by LTEDlCenterFreq(BSC6900,BSC6910). The
BSC finally selects a shared carrier with the longest
frequency separation and rolls back channels on the shared
carrier.
l If the uplink TBF multiplexing rate of a cell is less than the
value of GlDssPsUlLoadThd(BSC6910,BSC6900) and the
downlink TBF multiplexing rate is less than the value of
GlDssPsDlLoadThd(BSC6900,BSC6910), duty-cycle-
based channel conversion or channel conversion triggered
by the TBF multiplexing rate exceeding a specified value
can be performed only on exclusive carriers.

SingleRAN

Name
GBFD-119 Packet If the EGPRS/GPRS automatic planning function in the Packet

302 Channel Channel Dispatching feature is enabled, channel planning is
Dispatchi preferentially performed on exclusive carriers. The channel
ng planning priorities of exclusive carriers are the same. The
longer the frequency separation between ARFCNs on a shared
carrier and the central EARFCN specified by
LTEDlCenterFreq(BSC6900,BSC6910), the higher the
channel planning priority of the shared carrier. If the frequency
separations between ARFCNs on all the shared carriers and the
central EARFCN are the same, the shared carriers
corresponding to the ARFCNs on the left of the central
EARFCN specified by
LTEDlCenterFreq(BSC6900,BSC6910) have higher priorities.
If ARFCNs on all the shared carriers are on the left of the
central EARFCN specified by
LTEDlCenterFreq(BSC6900,BSC6910) and have the same
frequency separation to the central EARFCN, all the shared
carriers have the same priority. The BSC therefore randomly
selects a shared carrier for channel planning. If the shared
carriers participate in frequency hopping, the BSC traverses all
ARFCNs on the shared carriers and then determines the
frequency separation between the ARFCN closest to the central
EARFCN on each shared carrier and the EARFCN specified by
LTEDlCenterFreq(BSC6900,BSC6910). The BSC finally
selects a shared carrier with the longest frequency separation
for channel planning.
GBFD-113 Concentri If GBFD-113201 Concentric Cell is activated in co-BCCH

201 c Cell scenarios, activating GL DSS will have negative gains on GSM
and LTE networks. Therefore, do not activate Concentric Cell
and GL DSS together.

Sharing (LTE FDD)
Prerequisite Features
None
Mutually Exclusive Features

LOFD-001051 Compact Bandwidth -
MRFD-231808 GSM and LTE Buffer -

Zone Optimization (LTE)

SingleRAN
LOFD-001076 CPRI Compression -
LOFD-002007 PCI Collision Detection & This feature cannot be used with the
Self-Optimization PCI self-optimization function
provided by the LOFD-002007 PCI
Collision Detection & Self-
Optimization feature.
LOFD-003029 SFN -
LOFD-070205 Adaptive SFN/SDMA -
LOFD-070222 Intra-eNodeB UL CoMP -

Phase II
LOFD-001007 High Speed Mobility -
LOFD-001008 Ultra High Speed -

Mobility
LEOFD-111302 Flexible Bandwidth based l GSM and LTE FDD Dynamic

on Overlap Carriers Spectrum Sharing (GL DSS) can
be enabled for neither cells in the
Double Deck cell group
(hereafter referred to as Double
Deck cells) if any of the
following non-standard
bandwidths is used: 8.9 MHz,
8.6 MHz, 7.6 MHz, 7.3 MHz,
and 5.7 MHz
l GSM and LTE FDD Dynamic
Spectrum Sharing cannot be
enabled for Double Deck cells
with a standard bandwidth of 3
MHz if any of the following non-
standard bandwidths is used:
17.1 MHz, 12.2 MHz, and 4
MHz
l GSM and LTE FDD Dynamic
Spectrum Sharing cannot be
enabled for Double Deck cells
with a standard bandwidth of 10
MHz if either of the following
non-standard bandwidths is used:
28.5 MHz and 27.6 MHz
LOFD-070208 Coordinated Scheduling -

based Power Control
LOFD-121205 LTE Flexible Bandwidth -

SingleRAN
Impacted Features
Name
LOFD-06020 Adaptive After GL DSS is enabled, the available bandwidth for

1 Inter-Cell LTE cells dynamically changes. However, the Adaptive
Interference Inter-Cell Interference Coordination feature requires
Coordination static bandwidth of LTE cells. During the
implementation of the latter feature, static cell
bandwidth is divided into three frequency bands, and
each cell uses a different edge frequency band (1/3 of
total bandwidth) to carry users with high power and
severe interference at the edge of cells.
Therefore, if both GL DSS and LOFD-060201 Adaptive
Inter-Cell Interference Coordination are enabled, the
LTE exclusive spectrum is divided into different
frequency bands, and the shared spectrum is used as the
central frequency band. By default, the power
configurations for users at the center and edge of a cell
are set to –4.77 dB and –1.77 dB, respectively. The
method for determining and scheduling users at the
center and edge of a cell when both features are enabled
is the same as that when only AICIC is enabled. For
details, see Figure 5-1.
Figure 5-1 Frequency division and power configurations when AICIC is enabled

SingleRAN
Parameter Description 6 Network Impact
6 Network Impact

Sharing(GSM)
System Capacity
After this feature is enabled:
l The frequency reuse becomes tight and frequency hopping gains decrease. As a result,
voice quality deteriorates, thereby reducing network capacity.
l PS services are preferentially allocated channels on exclusive carriers and dynamic
PDCH conversion is also preferentially performed on exclusive carriers. As a result, the
TBF multiplexing rate on the exclusive spectrum increases, thereby increasing TBF
congestion rate and decreasing PS traffic.
Network Performance
Enabling this feature has the following impacts on network performance:
l CS services
The frequency reuse becomes tight and frequency hopping gains decrease, thereby
deteriorating voice quality.
l PS services
The TBF multiplexing rate on the exclusive spectrum increases, thereby increasing the
TBF congestion rate and decreasing PS traffic.
l CPU usages
The CPU usages of BSC6900 XPU boards or BSC6910 EGPU boards increase.

SingleRAN
Parameter Description 6 Network Impact

Sharing(LTE FDD)
System Capacity
Enabling this feature improves the LTE bandwidth and network throughput rate, thereby
increasing LTE system capacity.
Network Performance
Enabling this feature increases LTE network throughput.
Enabling flexible exclusive scheduling of shared RBs can improve the LTE single-user
experience if GSM UEs do not completely occupy the shared spectrum.
Enabling avoidance of GSM interference can avoid strong interference from GSM and
improve uplink performance of LTE.
NOTE
When different TCHF-to-TCHH conversion thresholds are provided for TCH allocation on shared
carriers and exclusive carriers, LTE network throughput further increases.
After this feature is enabled, if strong GSM interference exists in the LTE band, the
measurement results of some LTE full-band counters related to the SINR, RSRQ, and full-
band CQI are incorrect and both of the RSSI and interference increase. Therefore, you are
advised to use the counters related to MCS or throughput measurement to evaluate network
performance.
As some LTE UEs are incompatible with this feature, enabling this feature deteriorates the
UEs' throughput to some extent. Therefore, before a large-scale official commercial use of
this feature, it is recommended that this feature be tested at heavy-traffic sites to check
whether the UEs' incompatibility will cause customer complaints.
In addition, UEs support the high-order modulation of 256QAM in 3GPP Release 12 and
later. After this feature is enabled, GSM networks interfere with LTE networks. As a result,
the LTE MCS cannot meet the requirement of 256QAM, and the 256QAM gains cannot be
achieved.

SingleRAN
Parameter Description 7 Engineering Guidelines
7 Engineering Guidelines
To deploy and enable this feature, contact Huawei engineers to obtain the following services:
l RF planning
l Division of GSM exclusive spectrum and shared spectrum based on traffic requirements
in cells
l Generation and import of the GSM-to-LTE interference matrix
l PCI planning to avoid interference on PCFICHs and PHICHs of the LTE network from
the GSM network

SingleRAN
7.1 When to Use

Use this feature if the 1800 MHz bandwidth on a network is insufficient but the LTE and
GSM bandwidth requirements must be met. For example, this feature applies to the following
scenarios:
l Static refarming from a GSM network to an LTE network is complete, and operators
expect to increase LTE bandwidth without decreasing the GSM bandwidth.
l Static refarming from a GSM network to an LTE network has not yet been performed,
and there are difficulties in deploying LTE networks with higher bandwidth requirements
in GSM hot spot areas.
This feature is not recommended in the following scenarios:
l Co-BCCH in GSM concentric cells

l GSM tight frequency reuse
l MOCN or RAN Sharing between GSM and LTE networks
7.2 Required Information

Before deploying GL DSS, collect the counters listed in Table 7-1 to evaluate the
performance gains brought by this feature.
Table 7-1 Counters to be collected
Counter ID Counter Name Counter NE

Description
1278087438 CELL.KPI.TCH.TRAF.ERL.T K3014:Traffic BSC

RAF(GSM BSC6900,GSM Volume on TCH
BSC6910)
1278087445 CELL.KPI.TCHH.TRAF.ERL( K3034: TCHH Traffic BSC

GSM BSC6900,GSM Volume
BSC6910)
1278087422 CELL.KPI.SD.TRAF.ERL(GS K3004: Traffic BSC

M BSC6900,GSM BSC6910) Volume on SDCCH
1278472417 CELL.CH.BUSY.MAX.NUM.S R3560:Maximum BSC

D(BSC6900,BSC6910) Number of Busy
Channels (SDCCH)
1278472418 CELL.CH.BUSY.MAX.NUM.F R3561:Maximum BSC

R(BSC6900,BSC6910) Number of Busy
Channels (TCHF)
1278472419 CELL.CH.BUSY.MAX.NUM. R3562:Maximum BSC

HR(BSC6900,BSC6910) Number of Busy
Channels (TCHH)

SingleRAN

Description
1278087425 CELL.KPI.TCH.REQ.SIG(BS K3020:TCH Seizure BSC

C6900,BSC6910) Requests (Signaling
Channel)
1278087430 CELL.KPI.TCH.ASS.REQ.TR K3010A:TCH Seizure BSC

AF(BSC6900,BSC6910) Requests (Traffic
Channel)
1278087434 CELL.KPI.TCH.HO.REQ.TR K3010B:TCH Seizure BSC

AF(BSC6900,BSC6910) Requests in TCH
Handovers (Traffic
Channel)
1278087431 CELL.KPI.TCH.ASS.CONG.T K3011A:Failed TCH BSC

RAF(BSC6900,BSC6910) Seizures due to Busy
TCH (Traffic
Channel)
1278087435 CELL.KPI.TCH.HO.CONGES K3011B:Failed TCH BSC

T.TRAF(BSC6900,BSC6910) Seizures in TCH
Handovers due to
Busy TCH (Traffic
Channel)
1278087427 CELL.KPI.TCH.SUCC.SIG(B K3023:Successful BSC

SC6900,BSC6910) TCH Seizures
(Signaling Channel)
1278087432 CELL.KPI.TCH.ASS.SUCC.T K3013A:Successful BSC

RAF(BSC6900,BSC6910) TCH Seizures (Traffic
Channel)
1278087436 CELL.KPI.TCH.HO.SUCC.T K3013B:Successful BSC

RAF(BSC6900,BSC6910) TCH Seizures in TCH
handovers (Traffic
Channel)
1278076462 CELL.ASS.FAIL.MSC.CLR.C A3129H:Failed BSC

MD(BSC6900,BSC6910) Assignments (Clear
Commands Sent By
MSC)
1278072498 CELL.TRAF.CH.CALL.DROP CM33:Call Drops on BSC

S(BSC6900,BSC6910) Traffic Channel
1278072515 CELL.TRAF.CH.STATIC.STA CM3302:Call Drops BSC

TE.CALL.DROPS.REL.IND(B on Traffic Channel in
SC6900,BSC6910) Stable State (Release
Indication)
1278077482 CELL.INTRACELL.HO.SUC CH303:Successful BSC

C(BSC6900,BSC6910) Internal Intra-Cell
Handovers

SingleRAN

Description
1278078459 CELL.INTRABSC.INCELL.H CH323:Number of BSC

O.SUCC(BSC6900,BSC6910) Successful Incoming
Internal Inter-Cell
Handovers
1278080467 CELL.INTERBSC.INCELL.H CH343:Successful BSC

O.SUCC(BSC6900,BSC6910) Incoming External
Inter-Cell Handovers
1278082436 CELL.INTERRAN.INCELL.H CH363:Successful BSC

O.SUCC(BSC6900,BSC6910) Incoming Inter-RAT
1278087423 CELL.KPI.SD.AVAIL.NUM(B K3005:Available BSC

SC6900,BSC6910) SDCCHs
1278087419 CELL.KPI.SD.REQ(BSC6900, K3000:SDCCH BSC

BSC6910) Seizure Requests
1278087420 CELL.KPI.SD.CONGEST(BS K3001:Failed BSC

C6900,BSC6910) SDCCH Seizures due
to Busy SDCCH
1278087421 CELL.KPI.SD.SUCC(BSC690 K3003:Successful BSC

0,BSC6910) SDCCH Seizures
1278072520 CELL.SD.CALL.DROPS(BSC CM30: Call Drops on BSC

6900,BSC6910) SDCCH
1278079531 CELL.INTRABSC.OUTCELL CH311:Number of BSC

.HO.CMD(BSC6900,BSC6910) Outgoing Internal
Inter-Cell Handover
Commands
1278081558 CELL.INTERBSC.OUTCELL. CH331: Outgoing BSC

HO.CMD(BSC6900,BSC6910) External Inter-Cell
Handover Commands
1278079528 CELL.INTRABSC.OUTCELL CH313:Number of BSC

.HO.SUCC(BSC6900,BSC6910 Successful Outgoing
) Internal Inter-Cell
Handovers
1278081557 CELL.INTERBSC.OUTCELL. CH333:Successful BSC

HO.SUCC(BSC6900,BSC6910) Outgoing External
1279270419 AVR.AVAIL.PDCH(BSC6900, AR9303: Average BSC

BSC6910) Number of Available
PDCHs

SingleRAN

Description
1279270427 AVR.OCCU.PDCH(BSC6900, AR9311:Average BSC

BSC6910) Number of Occupied
PDCHs
1279270457 TCH.TO.PDTCH.ATMPT(BS R9341:Number of BSC

C6900,BSC6910) TCH to PDTCH
Conversion Attempts
1279270461 DISTRIBUTE.SUCC.PERCE AR9345:Successful BSC

NT(BSC6900,BSC6910) Rate of PDTCH
Distribution
1279183438 TX.UP.GPRS.LLC.PDU.THRP L9422:Throughput of BSC

UT.RATE(BSC6900,BSC6910) Uplink GPRS Users
LLC PDU
1279183440 TX.UP.EGPRS.LLC.PDU.TH L9424:Throughput of BSC

RPUT.RATE(BSC6900,BSC69 Uplink EGPRS Users
10) LLC PDU
1279183437 TX.UP.GPRS.LLC.PDU.TOTA L9421:Total Bytes of BSC

L.BYTE(BSC6900,BSC6910) Uplink GPRS Users
LLC PDUs
1279183439 TX.UP.EGPRS.LLC.PDU.TOT L9423:Total Bytes of BSC

AL.BYTE(BSC6900,BSC6910) Uplink EGPRS Users
LLC PDUs
1279184442 TX.DOWN.GPRS.LLC.PDU.T L9526:Throughput of BSC

HRPUT.RATE(BSC6900,BSC6 Downlink GPRS
910) Users LLC PDU
1279184444 TX.DOWN.EGPRS.LLC.PDU. L9528:Throughput of BSC

THRPUT.RATE(BSC6900,BS Downlink EGPRS
C6910) Users LLC PDU
1279184441 TX.DOWN.GPRS.LLC.PDU.T L9525:Total Bytes of BSC

OTAL.BYTE(BSC6900,BSC69 Downlink GPRS
10) Users LLC PDU
1279184443 TX.DOWN.EGPRS.LLC.PDU. L9527:Total Bytes of BSC

TOTAL.BYTE(BSC6900,BSC6 Downlink EGPRS
910) Users LLC PDU
1278288417 TRX.FR.DOWN.RX.QLTY. NCS412A:Number of BSC

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

TCHF (Receive
Quality Rank 1)

SingleRAN

Description
1278288419 TRX.FR.DOWN.RX.QLTY. NCS412C:Number of BSC

TCHF (Receive
Quality Rank 2)
1278288420 TRX.FR.DOWN.RX.QLTY. NCS412D:Number of BSC

TCHF (Receive
Quality Rank 3)
1278288421 TRX.FR.DOWN.RX.QLTY. NCS412E:Number of BSC

TCHF (Receive
Quality Rank 4)
1278288422 TRX.FR.DOWN.RX.QLTY. NCS412F:Number of BSC

TCHF (Receive
Quality Rank 5)
1278288423 TRX.FR.DOWN.RX.QLTY. NCS412G:Number of BSC

TCHF (Receive
Quality Rank 6)
1278288424 TRX.FR.DOWN.RX.QLTY. NCS412H:Number of BSC

TCHF (Receive
Quality Rank 7)
1278288425 TRX.FR.UP.RX.QLTY. NCS413A:Number of BSC

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

TCHF (Receive
Quality Rank 1)
1278288427 TRX.FR.UP.RX.QLTY. NCS413C:Number of BSC

TCHF (Receive
Quality Rank 2)
1278288428 TRX.FR.UP.RX.QLTY. NCS413D:Number of BSC

TCHF (Receive
Quality Rank 3)

SingleRAN

Description
1278288429 TRX.FR.UP.RX.QLTY. NCS413E:Number of BSC

TCHF (Receive
Quality Rank 4)
1278288430 TRX.FR.UP.RX.QLTY. NCS413F:Number of BSC

TCHF (Receive
Quality Rank 5)
1278288431 TRX.FR.UP.RX.QLTY. NCS413G:Number of BSC

TCHF (Receive
Quality Rank 6)
1278288432 TRX.FR.UP.RX.QLTY. NCS413H:Number of BSC

TCHF (Receive
Quality Rank 7)
1278288433 TRX.HR.DOWN.RX.QLTY. NCS414A:Number of BSC

TCHH (Receive
Quality Rank 0)
1278288434 TRX.HR.DOWN.RX.QLTY. NCS414B:Number of BSC

TCHH (Receive
Quality Rank 1)
1278288435 TRX.HR.DOWN.RX.QLTY. NCS414C:Number of BSC

TCHH (Receive
Quality Rank 2)
1278288436 TRX.HR.DOWN.RX.QLTY. NCS414D:Number of BSC

TCHH (Receive
Quality Rank 3)
1278288437 TRX.HR.DOWN.RX.QLTY. NCS414E:Number of BSC

TCHH (Receive
Quality Rank 4)
1278288438 TRX.HR.DOWN.RX.QLTY. NCS414F:Number of BSC

TCHH (Receive
Quality Rank 5)

SingleRAN

Description
1278288439 TRX.HR.DOWN.RX.QLTY. NCS414G:Number of BSC

TCHH (Receive
Quality Rank 6)
1278288440 TRX.HR.DOWN.RX.QLTY. NCS414H:Number of BSC

TCHH (Receive
Quality Rank 7)
1278288441 TRX.HR.UP.RX.QLTY. NCS415A:Number of BSC

TCHH (Receive
Quality Rank 0)
1278288442 TRX.HR.UP.RX.QLTY. NCS415B:Number of BSC

TCHH (Receive
Quality Rank 1)
1278288443 TRX.HR.UP.RX.QLTY. NCS415C:Number of BSC

TCHH (Receive
Quality Rank 2)
1278288444 TRX.HR.UP.RX.QLTY. NCS415D:Number of BSC

TCHH (Receive
Quality Rank 3)
1278288445 TRX.HR.UP.RX.QLTY. NCS415E:Number of BSC

TCHH (Receive
Quality Rank 4)
1278288446 TRX.HR.UP.RX.QLTY. NCS415F:Number of BSC

TCHH (Receive
Quality Rank 5)
1278288447 TRX.HR.UP.RX.QLTY. NCS415G:Number of BSC

TCHH (Receive
Quality Rank 6)
1278288448 TRX.HR.UP.RX.QLTY. NCS415H:Number of BSC

TCHH (Receive
Quality Rank 7)

SingleRAN

Description
1526729868 L.Traffic.DL.SCH.Shared.TB.b Number of bits of eNodeB

its TBs initially
transmitted on the
downlink SCH in the
shared spectrum in an
LTE cell
1526729869 L.Traffic.DL.SCH.Shared.TB Number of TBs eNodeB

initially transmitted
on the downlink SCH
in the shared
spectrum in an LTE
cell
1526729876 L.Traffic.Schedule.Dedicated.A Number of times of eNodeB

vg downlink scheduling
in the dedicated
spectrum in an LTE
cell
1526729875 L.Traffic.Schedule.Shared.Avg Number of times of eNodeB

downlink scheduling
in the shared
spectrum in an LTE
cell
1526729871 L.Traffic.DL.SCH.Shared.Err Number of TBs failed eNodeB

TB.Ibler to be transmitted
during initial
transmission on the
downlink SCH in the
shared spectrum in an
LTE cell
1526729870 L.Traffic.DL.SCH.Shared.Err Number of bits of eNodeB

TB.Ibler.bits TBs failed to be
transmitted during
initial transmission on
the downlink SCH in
the shared spectrum
in an LTE cell
1526729874 L.ChMeas.PRB.Shared.DL.Use Average number of eNodeB

d.Avg used downlink PRBs
in the shared
spectrum in an LTE
cell
1526729463 L.ChMeas.PRB.DL.DLComp. Average number of eNodeB

Used.Avg PRBs used by
downlink CoMP UEs
in a cell

SingleRAN

Description
1526729295 L.ChMeas.CCE.ULUsed.Equiv Number of PDCCH eNodeB

alent CCEs with the CCE
power equivalent to
the reference power
used for uplink DCI
1526729296 L.ChMeas.CCE.DLUsed.Equiv Number of PDCCH eNodeB

alent CCEs with the CCE
power equivalent to
the reference power
used for downlink
DCI
1526729294 L.ChMeas.CCE.DLUsed.MCE Number of PDCCH eNodeB

CCEs used for initial
transmitted downlink
MCEs in a cell
1526729293 L.ChMeas.CCE.DLUsed.SRB Number of PDCCH eNodeB

signaling in a cell
1526729292 L.ChMeas.CCE.DLUsed.DRB Number of PDCCH eNodeB

data in a cell
1526728765 L.ChMeas.CCE.Avail Number of available eNodeB

PDCCH CCEs
1526728764 L.ChMeas.PRB.PUSCH.Avg Average number of eNodeB

used PUSCH PRBs
1526728763 L.ChMeas.PRB.DL.DrbUsed.A Average number of eNodeB

vg PRBs used by
PDSCH DRBs
1526728762 L.ChMeas.PRB.UL.DrbUsed.A Average number of eNodeB

vg PRBs used by
PUSCH DRBs
1526728665 L.ChMeas.PDCCH.DL.DTXN Number of times of eNodeB

um.AggLvl2 DTX for PDCCH
resource allocation
with aggregation level
2 in a cell

SingleRAN

Description

resource allocation
4 in a cell

resource allocation
8 in a cell

resource allocation
1 in a cell
1526728480 L.ChMeas.PRB.DL.CEU.Used. Average number of eNodeB

Avg PRBs used by
downlink CEUs in a
cell
1526728433 L.ChMeas.PRB.DL.Avail Number of available eNodeB

downlink PRBs
1526728484 L.ChMeas.PRB.DL.FSS.Avg Average number of eNodeB

PRBs allocated for
downlink frequency
selective scheduling
1526728545 L.ChMeas.PRB.UL.PreSch.Use Average number of eNodeB

d.Avg PRBs allocated for
uplink pre-scheduling
1526728483 L.ChMeas.PRB.UL.FSS.Avg Average number of eNodeB

PRBs allocated for
uplink frequency
selective scheduling
1526728479 L.ChMeas.PRB.UL.CEU.Used. Average number of eNodeB

Avg PRBs used by uplink
CEUs in a cell
1526728434 L.ChMeas.PRB.UL.Avail Number of available eNodeB

uplink PRBs

SingleRAN

Description
1526728424 L.ChMeas.PRB.DL.PCell.Used Average number of eNodeB

.Avg downlink PRBs
occupied by CA UEs
that use the local cell
as their primary
serving cell
1526728340 L.ULCoMP.RB Average number of eNodeB

scheduled PRBs for
UL CoMP
1526728305 L.ChMeas.CCE.DLUsed Number of PDCCH eNodeB

CCEs used for
downlink DCI in a
measurement period
1526728304 L.ChMeas.CCE.ULUsed Number of PDCCH eNodeB

CCEs used for uplink
DCI in a
measurement period
1526728303 L.ChMeas.CCE.CommUsed Number of PDCCH eNodeB

CCEs used for
common DCI
1526728299 L.ChMeas.PDCCH.SymNum.1 Number of times the eNodeB

PDCCH occupies one
symbol in a
measurement period

PDCCH occupies two
symbols in a
measurement period

PDCCH occupies
three symbols in a
measurement period

PDCCH occupies four
symbols in a
measurement period
1526727483 L.ChMeas.PRB.PUCCH.Avg Average number of eNodeB

used PRBs over the
PUCCH
1526726740 L.ChMeas.PRB.DL.Used.Avg Average number of eNodeB

used PDSCH PRBs

SingleRAN

Description
1526726737 L.ChMeas.PRB.UL.Used.Avg Average number of eNodeB

used uplink PRBs
1526729435 L.Thrp.UL.BitRate.Samp.Inde Number of samples eNodeB

x0 with the uplink
throughput ranging
within index 0

x1 with the uplink
throughput ranging
within index 1

x2 with the uplink
throughput ranging
within index 2

x3 with the uplink
throughput ranging
within index 3

x4 with the uplink
throughput ranging
within index 4

x5 with the uplink
throughput ranging
within index 5

x6 with the uplink
throughput ranging
within index 6

x7 with the uplink
throughput ranging
within index 7

x8 with the uplink
throughput ranging
within index 8

x9 with the uplink
throughput ranging
within index 9

SingleRAN

Description
1526729057 L.Thrp.DL.BitRate.Samp.Inde Number of samples eNodeB

x1 with the downlink
throughput ranging
within index 1

throughput ranging
within index 2

throughput ranging
within index 3

throughput ranging
within index 4

throughput ranging
within index 5

throughput ranging
within index 6

throughput ranging
within index 7

throughput ranging
within index 8

throughput ranging
within index 9

throughput ranging
within index 0

SingleRAN
7.3 Planning
7.3.1 RF Planning
RF planning for enabling this feature consists of RF planning on the entire network and RF
planning in specific areas on the network. The only difference is that a buffer zone is required
for RF planning in specific areas on the network. The method for planning the buffer zone is
the same as that for planning the buffer zone in GL refarming scenarios. For more
information, contact Huawei engineers.
NOTE
After this feature is enabled, GSM and LTE co-channel interference occurs on the shared spectrum. This
adversely affects GSM and LTE network performance. If the interference is severe, call drops may occur
and the throughput rate 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.
RF Planning on the Entire Network

If this feature is enabled on the entire network, the mutual impact between the site enabled
with this feature and its adjacent sites can be ignored. In this situation, a buffer zone is not
required.
The RF planning described in this section involves GSM and LTE frequency planning and
feature activation planning for sites in different areas.
Before enabling this feature, contact Huawei engineers to perform GSM frequency
replanning.
RF Planning in Specific Areas on the Network

If this feature is enabled in specific areas on the network, the mutual impact between the site
enabled with this feature and its adjacent sites must be considered.
l Scenario 1: Static refarming from a GSM network to an LTE network is complete on the
entire network, and higher LTE bandwidth is required in specific areas on the network,
as shown in Figure 7-1.
Figure 7-1 Frequency configuration in scenario 1

SingleRAN
A buffer zone is required between the area enabled with this feature and that not enabled
with this feature to adjust the frequency configuration of GSM cells within the buffer
zone. The GSM frequency configuration in the buffer zone is the same as that in the area
enabled with the feature. In addition, the GSM cells in the buffer zone must be enabled
with this feature.
l Scenario 2: If static refarming from a GSM network to an LTE network has not yet been
performed, higher LTE bandwidth is required and this feature must be enabled in specific
areas on the network, as shown in Figure 7-2.
Figure 7-2 Frequency configuration in scenario 2
A buffer zone is required between the area enabled with this feature and that not enabled
with this feature to adjust the frequency configuration of GSM cells within the buffer
zone. The GSM frequency configuration in the buffer zone is the same as that in the area
enabled with the feature. In addition, the GSM cells in the buffer zone must be enabled
with this feature.
7.3.2 Network Planning

This feature requires the following network planning:
l If the transmission bandwidth before GL DSS is enabled cannot meet the higher LTE
bandwidth requirement after this feature is enabled, more transmission resources are
required.
l The GSM and LTE sites enabled with this feature must have the same site number, cover
the same area, be served by the same base station, and use co-antenna networking (the
same antenna azimuth, tilt, and antenna port). Other sites can be added on the network
(the number of added GSM sites is different from that of added LTE sites) but the added
LTE sites cannot use the shared spectrum.
– GSM-only or LTE-only base stations, micro base stations, and indoor distributed
base stations can only use their respective exclusive spectrum.
– If only GSM sites are added, the call drop rate increases and the access success rate
decreases for the cells under the LTE sites in the vicinity of the GSM sites.
– If only LTE sites are added, network performance is the same as that when the
numbers of GSM and LTE sites are the same.
l The recommended ratio of GSM power to LTE power is 1:1.
Ratio of GSM power to LTE power = GSM power/(LTE power/Bandwidth conversion
coefficient)

SingleRAN
NOTE
The bandwidth conversion coefficient varies with the LTE bandwidth:

l 15 MHz: The coefficient is 1.
l 10 MHz: The coefficient is 0.667.
l 20 MHz: The coefficient is 1.33.
l After this feature is enabled, a 4x3 GSM frequency reuse pattern is recommended on the
shared spectrum. In this situation, if the GSM frequency reuse becomes tighter, GSM
KPIs will deteriorate, and the LTE network throughput rate and KPIs will deteriorate
accordingly.
l The X2 interface between eNodeBs must be configured.
l It is recommended that intra-frequency cells under the same physical site be bound to the
same baseband processing board.
7.3.3 Hardware Planning

None
7.4 Deployment
7.4.1 Requirements
Other Features
For details, see 5 Related Features.
Hardware
l Huawei devices (including the BSC, eCoordinator, multimode base station, U2000, and
CME) of SRAN9.0 or later must be used on the radio access network side.
l The sum of the BSC-eCoordinator transmission delay and the eCoordinator-eNodeB
transmission delay must be shorter than or equal to 50 ms.
l The BSC must be configured with a built-in PCU, PS service processing board, and Gb
interface board.
l A single eCoordinator can be deployed alone or built in to a multimode base station
controller. In areas enabled with this feature, if the coordination of multiple BSCs is
required, it is recommended that an independent eCoordinator be deployed; if the
coordination of multiple BSCs is not required, it is recommended that an eCoordinator
be built in to the BSC.
l If GSM and LTE carriers share the SDR, the following RF modules are supported:
MRFUd (1800 MHz, 2T), RRU3928, RRU3929, RRU3938, RRU3939, RRU3952,
AAU3902, MRFUd V6, MRFUdw V6, RRU3959, RRU3953, RRU3953w, RRU3956,
RRU3952m, AAU3920, RRU3965, and RRU3965d.
l The eNodeB must be configured with a baseband processing board in the following
table.
The following table describes the capabilities of the UBBP boards for GL DSS.

SingleRAN
UBBP 2T2R Capability 4T4R Capability

Board Type
UBBPd3 l LTE only Not supported

3 x 20 MHz 2T2R
l Multi-mode (LTE and other
RATs)
Not supported

3 x 20 MHz 2T2R
RATs)
Not supported

6 x 20 MHz 2T2R
RATs)
Not supported
UBBPd6 l LTE only l LTE only

6 x 20 MHz 2T2R 3 x 20 MHz 4T4R
l Multi-mode (LTE and other l Multi-mode (LTE and other
RATs) RATs)
Not supported Not supported
UBBPe3 l LTE only Not supported

6 x 20 MHz 2T2R
RATs)
3 x 20 MHz 2T2R is supported
if a maximum of three LTE
TDD cells are configured in
LTE FDD and LTE TDD
concurrency scenarios.
UBBPe4 l LTE only l LTE only

6 x 20 MHz 2T2R 3 x 20 MHz 4T4R
l Multi-mode (LTE and other l Multi-mode (LTE and other
RATs) RATs)
Not supported Not supported
Network bandwidth
l After this feature is enabled, only LTE 10 MHz, 15 MHz, and 20 MHz bandwidths are
supported, and the uplink bandwidth must be the same as the downlink bandwidth.
l The proportion of the shared bandwidth to the total LTE bandwidth is less than or equal
to 1/5. The shared spectrums must be symmetrically distributed at both ends of the LTE
bandwidth, and the bandwidth difference between the spectrums on the high and low
frequency bands cannot exceed one RB.

SingleRAN
l The separation between GSM shared frequencies and LTE exclusive RBs must be 3 RBs
or more.
GSM and LTE channel configuration

l The GSM BCCH TRX cannot be configured on the shared spectrum.
l GSM static PDCHs or static SDCCHs cannot be configured on the shared spectrum. If
GL DSS is enabled and static PDCHs or static SDCCHs are configured on the shared
spectrum, the BSC LMT displays this information and prompts users to query the
exclusive carrier number in the cell by running the LST GTRX command and then to
modify the configuration of static PDCHs or static SDCCHs.
l LTE PBCHs, PUCCHs, and PRACHs are configured on the LTE exclusive spectrum.
l The GSM exclusive spectrum and shared spectrum must use different MA groups.
License
Feature ID Feature Name License Control NE Sales
Item Unit
MRFD-090201 GSM and LTE FDD GSM and LTE FDD eCoordi Per Cell
Dynamic Spectrum Dynamic Spectrum nator
Sharing Sharing (GSM)
MRFD-090202 GSM and LTE FDD GSM and LTE FDD eCoordi Per Cell
Dynamic Spectrum Dynamic Spectrum nator
Sharing Sharing (LTE FDD)
Other requirements
None
7.4.2 Precautions
Enabling this feature changes related configurations, and the changes will cause GSM and
LTE cells to reset. Therefore, you are advised to enable this feature when traffic is light, for
example, in the early morning.
7.4.3 Data Preparation and Feature Activation
7.4.3.1 Data Preparation
BSC
Table 7-2 lists data to be prepared for the BSC.

SingleRAN
Table 7-2 Parameters in the CELLGLDSS MO

Parameter Parameter ID Setting Notes Data
Name Source
LTE LTEBandWidth(BSC6900,B Set this parameter Network

Bandwidth SC6910) according to the actual plan
conditions on the LTE
DL Central LTEDlCenterFreq(BSC6900, network. Network
LTE BSC6910) plan
ARFCN
GL DSS GLDSSSw(BSC6900,BSC69 Set this parameter to Network

Switch 10) ON(On) in GSM cells that plan
require this feature.
Channel TchActDelay(BSC6900,BSC6 Set this parameter Network

Activation 910) according to delays in plan
Delay sending messages from the
BSC to the eCoordinator
and from the eCoordinator
to the eNodeB.
Long Call LongCallDetThld(BSC6900, Set this parameter Network

Determinati BSC6910) according to the plan
on distribution of call
Threshold durations in a cell.
Idle TCH CsRepackingTchIdle- Set this parameter Network

Number Num(BSC6900,BSC6910) according to CS traffic plan
Threshold volume.
for CS HO
Number of ECOMSGIdleTchNum(BSC6 Network

Idle TCHs 900,BSC6910) plan
for
Message
Sending to
eCoordinat
or
Shared SharedTrxPwrDecrSw(BSC6 Set this parameter Network

TRX Power 900,BSC6910) according to the GSM-to- plan
Decrease LTE interference.
Switch
Shared SharedTrxPwrDecr- Set this parameter Network

TRX Power Lev(BSC6900,BSC6910) according to the GSM-to- plan
Decrease LTE interference.
Level

SingleRAN

Name Source
Number of AloneTrxResvChan- Set this parameter Network

Reserved Num(BSC6900,BSC6910) according to CS traffic plan
Channels volume.
on
Independen
t TRX
GL DSS GlDssAtcbThld(BSC6900,BS Set this parameter Network

ATCB C6910) according to the plan
Threshold distribution of the
difference between the
GL DSS GlDssAtcbHYST(BSC6900,B downlink receive level and Network
ATCB SC6910) the level of a neighboring plan
Hysteresis cell level of a CS call.
Shared SharedTrxRxLevThld(BSC69 Set this parameter based on Network

TRX 00,BSC6910) the distribution of the plan
Receive downlink receive level for a
Level call.
Threshold
Shared SharedTrxRxLevHYST(BSC Network

TRX 6900,BSC6910) plan
Receive
Level
Hysteresis
Shared SharedTrxInterf- Set this parameter Network

TRX HO HoAtcbThld(BSC6900,BSC6 according to the plan
Interference 910) distribution of the
ATCB difference between the
Threshold downlink receive level and
the level of a neighboring
cell level of a CS call.

SingleRAN

Name Source
Cell PS DL GlDssPsDlLoadThd(BSC690 Set this parameter Network

Load 0,BSC6910) according to the downlink plan
Threshold PS traffic volume.
for GL DSS l If GBFD-113101 PDCH
Dynamic Adjustment is
enabled, set this
parameter to a value
greater than the value of
DWNDYNCHNTRANL
EV(GSM
BSC6900,GSM
BSC6910) but 1 or 2
less than the value of
PSServiceBusyThres-
hold(GSM
BSC6900,GSM
BSC6910) for the peak-
hour single channel
allocation function.
l If GBFD-119408 PS
Access Congestion
Balancing is enabled,
set this parameter to a
value 1 or 2 less than
the value of
RadioResAdaAdjDl-
LoadThd(BSC6900,BS
C6910) for the PS
Access Congestion
Balancing feature.
l If GBFD-511611 Duty-
Cycle-based PDCH
Management is enabled,
the value of
DWNDYNCHNTRANL
EV(BSC6900,BSC6910
).

SingleRAN

Name Source
Cell PS UL GlDssPsUlLoadThd(BSC690 Set this parameter Network

Load 0,BSC6910) according to the uplink PS plan
Threshold traffic volume.
for GL DSS l If GBFD-113101 PDCH
Dynamic Adjustment is
enabled, set this
parameter to a value
greater than the value of
UPDYNCHNTRANLE
V(GSM BSC6900,GSM
BSC6910).
l If GBFD-119408 PS
Access Congestion
Balancing is enabled,
the value of
RadioResAdaAdjUl-
LoadThd(BSC6900,BS
C6910) for the PS
Access Congestion
Balancing feature.
l If GBFD-511611 Duty-
Cycle-based PDCH
Management is enabled,
the value of
UPDYNCHNTRANLE
V(BSC6900,BSC6910).
Independen AloneTrxHrLdThldOff- Set this parameter Network

t TRX HR set(BSC6900,BSC6910) according to the GSM plan
Allocation traffic volume. If the LTE
Load Thld throughput needs to be
Offset increased when the GSM
traffic volume is high, set
this parameter to a value
other than 0.
GL DSS GlDssHoOptSw(BSC6900,BS Set this parameter Network

Handover C6910) according to the LTE-to- plan
Optimizatio GSM interference. If the
n Switch LTE-to-GSM interference
is strong and the GSM
handover success rate is
significantly affected, set
this parameter to ON.

SingleRAN
To quickly perform handovers to reduce the LTE-to-GSM interference, set the following
parameters for features GBFD-110601 Huawei I Handover and GBFD-510501 HUAWEI II
Handover:
l Parameters in the G2GNCELL MO
– Set PBGTSTAT(BSC6900,BSC6910) to 4.
– Set PBGTLAST(BSC6900,BSC6910) to 3.
– Set NCELLPUNLEV(BSC6900,BSC6910) to 0.
l Parameters in the GCELLHOFITPEN MO
– Set DATASTRFLTLEN(BSC6900,BSC6910) to 2.
– Set DATAQUAFLTLEN(BSC6900,BSC6910) to 2.
– Set NCELLFLTLEN(BSC6900,BSC6910) to 2.
You are advised to enable GBFD-117601 HUAWEI III Power Control Algorithm and set
GCELLPWR3.PWRCTRLOPTIMIZEDEN(BSC6900,BSC6910) to YES(Yes). In the
coverage area served by both 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 sending to execution
whereas the LTE RB scheduling period is 1 ms. Therefore, the GSM power control algorithm
does not reflect the interference to GSM networks from LTE networks and GSM intra-
network interference. To accurately reflect the interference, set power control-related
parameters in the GCELLPWR3 MO as follows:
l Set DLREXLEVADJFCTR(BSC6900,BSC6910) to 2.
l Set DLREXQUALADJFCTR(BSC6900,BSC6910) to 8.
l Set DLMAXDOWNSTEP(BSC6900,BSC6910) to 2.
l Set DLMAXUPSTEP(BSC6900,BSC6910) to 8.
l Set DLRXLEVPROTECTFACTOR(BSC6900,BSC6910) to 5.
l Set DLRXQUALPROTECTFACTOR(BSC6900,BSC6910) to 85.
l Set DLADJPRD(BSC6900,BSC6910) to 1.
l Set DLREXQUALEXPFLTLEN(BSC6900,BSC6910) to 1.
l Set DLREXLEVEXPFLTLEN(BSC6900,BSC6910) to 1.
l Set DLFILTADJFACTOR(BSC6900,BSC6910) to 9.
l Set DlMaxDownOptiSw(BSC6900,BSC6910) to ON and
MAXBTSPWRNUM(BSC6900,BSC6910) to 8.
eCoordinator
Table 7-3 lists data to be prepared for the eCoordinator.

SingleRAN
Table 7-3 Parameters in the ELCELLGLDSS MO

Name Source
GL GLDSSSw Set this parameter to Network plan

Dynamic ON(On) in LTE cells that
Spectrum require GL DSS.
Sharing
Switch
Shared RB RBFACTOR1 Set this parameter based on Network plan

Control the level of GSM cells that
Factor 1 interfere with LTE users at
the edge of a cell.

Factor 2 interfere with LTE users in
the middle of a cell.

Factor 3 interfere with LTE users at
the center of a cell.
RB Status RBStatusTimer Set this parameter based on Network plan

Timer the duration from the time
the GSM handover is
started to the time the GSM
handover succeeds.
LTE FBIDX Set this parameter Network plan

Bandwidth according to actual
Index conditions on the LTE
network.
ICS Table ICSIDX Set this parameter based on Network plan

Index the position of a GSM
frequency on LTE
frequency band.
ICS ICSDiffIDX Set this parameter based on Network plan

Frequency the deviation between a
Deviation GSM frequency and the
Index RB central frequency.
ICS Value ICSValue Set this parameter based on Network plan

the separation between a
GSM frequency and the
frequency corresponding to
the RB.

SingleRAN

Name Source
GSM Cell GSMCellIndex Set this parameter based on Network plan

Index the information of GSM
cells served by the same
base station and cover the
same area as LTE cells.
GSM Cell GSMCellName Set this parameter based on Network plan

Name the information of GSM
cells served by the same
Mobile MCC base station and cover the Network plan
Country same area as LTE cells.
Code
Mobile MNC Network plan

Network
Code
Location LAC Network plan

Area Code
Cell CI Network plan

Identity
eNodeB
Table 7-4 and Table 7-5 list data to be prepared for the eNodeB.
Table 7-4 Parameter in the CELLALGOSWITCH MO

Parameter Parameter ID Setting Notes Data Source
Name
Dynamic DynSpectrumShareSwitch Set this parameter to Network plan

Spectrum ON(On) in LTE cells that
Share require GL DSS.
Switch
Table 7-5 Parameters in the CELLDSS MO

Name
Shared RB HighFreqShareRbNum Set this parameter based on Engineering

Number in the shared spectrum on the design
High high frequency band (left
Frequency end of the LTE bandwidth)
and on the low frequency
band (right end of the LTE

SingleRAN

Name
Shared RB LowFreqShareRbNum bandwidth) in LTE cells. Engineering

Number in The difference between the design
Low values of
Frequency HighFreqShareRbNum
and LowFreqShareRbNum
must not exceed one RB.
Otherwise, PUCCHs or
SRS channels cannot be
configured due to PUCCH
symmetry and therefore
cells fail to be added.
A3 Offset A3Offset Set this parameter based on Engineering

the level difference design
between the serving cell
A6 Offset A6Offset and its neighboring cells. Engineering
design
UL UlInterfRestrictionMode It is recommended that this Engineering

Narrowban parameter be set to design
d ADAPTIVEPROCESS(A
Interference DAPTIVEPROCESS).
Restriction
Mode
Mute RE REMuteSwitch It is recommended that this Engineering

Switch parameter be set to design
ON(On).
Near Area NearAreaSinrThd The default value is Engineering

SINR recommended. design
Threshold
Middle MiddleAreaSinrThd Engineering

Area SINR design
Threshold
Far Area FarAreaSinrThd Engineering

SINR design
Threshold
Interference InterfNCellConfigMode It is recommended that this Engineering

Neighbour parameter be set to design
Cell ECOCONFIG(ECOCON
Configurati FIG).
on Mode

SingleRAN

Name
Spectrum SpecShrPfmOptSwitch This parameter includes the Engineering

Sharing FlexSpecSchSwitch and design
Performanc UlSchInterfAvdSwitch
e Opt options.
Switch Turning on the
FlexSpecSchSwitch can
improve the LTE single-
user experience if GSM
UEs do not completely
occupy the shared
spectrum.
Turning on the
UlSchInterfAvdSwitch
can avoid strong
interference from GSM and
improve uplink
performance of LTE.
SINR SinrThdWithoutGsmInterf The default value is Engineering

Threshold recommended. design
Without
GSM
Interference
GSM GsmInterfINThd The default value is Engineering

Interference recommended. design
Noise
Threshold
The LTE mobility management is optimized through parameter configuration. If

CELLALGOSWITCH.DynSpectrumShareSwitch is set to ON(On), the RSRP is the only
condition for triggering handovers.
7.4.3.2 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 (press F1 in an active CME
window).

SingleRAN
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
7.4.3.3 Using MML Commands

Perform the following operations on the BSC, eCoordinator, and eNodeB sides, respectively.
BSC
Step 1 Add an SCTP link between the BSC and eCoordinator.
For details, see "Configuring Control Plane Data over the Sg Interface" in BSC6900 GSM
Initial Configuration Guide or BSC6910 GSM Initial Configuration Guide.
NOTE
When a built-in ECO6910 is deployed, coordination services are configured in the BSC.
When a stand-alone ECO6910 is deployed, coordination services are configured outside the BSC.
Step 2 Enable GL DSS for the BSC.

1. Run the SET GCELLPSCHM command with PDCH Management Optimization set
to on(on).
2. Run the SET GCELLCHMGAD command with Channel Allocation Algorithm
Optimization set to YES(Yes).
3. Run the SET GCELLCHMGBASIC command with Channel Allocate Strategy set to
CONTINUITY(Continuity preferred).
4. Run the SET CELLGLDSS command with parameters set according to the "Setting
Notes" column in Table 7-2.
----End
eCoordinator
Step 1 Add SCTP links between the eCoordinator and the BSC, and between the eCoordinator and
the eNodeB.

SingleRAN
When a built-in ECO6910 is deployed, add SCTP links by referring to the procedures in
"Configuring Control Plane Data over the Sg Interface" and "Configuring Control-Plane Data
over the Se Interface" in Built-in ECO6910 Initial Configuration Guide.
When a stand-alone ECO6910 is deployed, add SCTP links by referring to the procedures in
"Configuring Control Plane Data over the Sg Interface" and "Configuring Control-Plane Data
over the Se Interface" in Stand-alone ECO6910 Initial Configuration Guide.
Step 2 Add GSM and LTE cells.
1. Run the ADD EGSMCELL command to configure MCC, MNC, LAC, and CI
according to the GSM cell plan.
2. Run the ADD ELTECELL command to configure MCC, MNC, CellId, and FddTddInd
according to the LTE cell plan.
Step 3 Import the GSM and LTE interference matrix.
Run the ADD GLDSSINTFM command to import the GSM and LTE interference matrix
into the eCoordinator. Set Mobile Network Code, Mobile Country Code, eNodeB ID, and
Cell ID for LTE cells and GSM Cell MNC, GSM Cell MCC, Cell LAC, and Cell CI for
GSM cells according to the actual network plan. Interference Matrix specifies the GSM and
LTE interference matrix.
Step 4 Add non-co-coverage neighboring GSM cells for an LTE cell.
Run the ADD ELGNCELL command to add co-site non-co-coverage neighboring GSM cells
or non-co-site non-co-coverage neighboring GSM cells that require the transmission of
information about shared frequencies, for an LTE cell.
Step 5 Enable GL DSS.
Run the SET ELCELLGLDSS command. In this step, set GL Dynamic Spectrum Sharing
Switch to ON(ON), and set the CGI (Mobile Network Code+Mobile Country Code+Cell
LAC+Cell CI), shared rb control factor 1, shared rb control factor 2, and shared rb
control factor 3 for GSM cells that are served by the same base station and cover the same
area as LTE cells according to the actual information.
----End
eNodeB
Step 1 Add an SCTP link between the eNodeB and eCoordinator.
1. Run the ADD SCTPLNK command to configure the ID, port number, and IP address of
the SCTP link based on the command prompt and actual network plan.
2. Run the ADD SCTPHOST command to configure the local SCTP object according to
the actual plan.
3. Run the ADD SCTPPEER command to configure the peer SCTP object according to
the actual plan.
4. Run the ADD EPGROUP command to add an end point group.
5. Run the ADD SCTPHOST2EPGRP command to add the local SCTP object to the end
point group.
6. Run the ADD SCTPPEER2EPGRP command to add the peer SCTP object to the end
point group.
7. Run the ADD USERPLANEHOST command to add a user-plane local object.

SingleRAN
8. Run the ADD UPHOST2EPGRP command to add the user-plane local object to the end
point group.
9. Run the ADD ECO command to add an eCoordinator.
Step 2 Configure LTE frequencies and bandwidth.
Run the MOD CELL command to reconfigure Downlink EARFCN and Downlink
bandwidth according to the frequency plan after GL DSS is enabled.
Step 3 Configure the shared bandwidth for GL DSS.
Run the MOD CELLDSS command with parameters set according to the "Setting Notes"
column in Table 7-5.
Step 4 Enable GL DSS.
Run the MOD CELLALGOSWITCH command with parameters set according to the
"Setting Notes" column in Table 7-4.
----End
NOTE
To observe activation of this feature, you are advised to enable Se/Sg interface message tracing before
configuring data.
7.4.3.4 MML Command Examples

An independent eCoordinator is used as an example to illustrate the activation of this feature.
In this example, the LTE bandwidth is 10 MHz (including the shared spectrum), and the
center frequency is 1805.
On the BSC side:
//Turning on the PDCH management optimization switch
SET GCELLPSCHM: IDTYPE=BYID, CELLID=1, EnPDAdminOpt=ON;
//Turning on the channel allocation algorithm optimization switch
SET GCELLCHMGAD: IDTYPE=BYID, CELLID=1, CHALLOCATIONOPTSWITCH=YES;
//Changing the channel allocation policy to continuity preferred
SET GCELLCHMGBASIC: IDTYPE=BYID, CELLID=1, CHALLOCSTRATEGY=CONTINUITY;
//Enabling GL DSS and setting LTE bandwidth and LTE downlink central EARFCN
SET CELLGLDSS: IDTYPE=BYID, CELLID=1, GLDSSSw=ON, LTEBandWidth=20M,
LTEDlCenterFreq =1805;
On the eCoordinator side:

//Adding GSM and LTE cells
ADD EGSMCELL: QueryNeIdType=BYID, MBSCIndex=2, GSMCellIndex=10,
GSMCellName="shanghaigsm10", MCC="510", MNC="52", LAC=8274, CI=10;
ADD ELTECELL: QueryNeIdType=BYID, eNodeBIndex=29, LTECellIndex=10,
LTECellName="BTS0_L0", MCC="302", MNC="220", CellId=0, FddTddInd=FDD;
//Enabling GL DSS and setting the CGI information of GSM cells that are served by
the same base station and cover the same area as LTE cells
SET ELCELLGLDSS: LTECellIdType=BYCGI, MCC="460", MNC="20", eNodeBId=255,
CellId=2, GLDSSSw=ON, GSMCellIdType=BYCGI, GMCC="460", GMNC="10", LAC=10, CI=11,
RBFACTOR1=0, RBFACTOR2=0, RBFACTOR3=0, RBStatusTimer=3;
//Importing the interference matrix
ADD GLDSSINTFM: IDTYPE=BYID, LTECellIndex=10, GSMCellIndex=10,
INTFMATRIX="0074688B 006B088B 0060188B 0074685B 006B085B 0060185B 00746859
006B0859 00601859 00746857 006B0857 00601857 00746855 006B0855 00601855 00746853
006B0853 00601853 00746851 006B0851 00601851 00B4144F 00A6CC4F 0092E04F 00D6104D
00CB844D 00B0904D 00CABC4B 00C2EC4B 00AE384B 00BC4849 00B47849 00A7F849 00ADD447
00A60447 009CA447 00A6CC45 009EFC45 00959C45 009BDC43 00940C43 008AAC43 008E9441
00885441 007EF441 0082DC3F 0080E83F 0077EC3F 00733C3D 0072743D 006E283D 0064643B
0062D43B 0061A83B 0056B839 0055F039 0052D039 00413C37 0040D837 003EE437 0021FC35

SingleRAN
0020D035 001F4035 00157C33 00151833 00132433 001DB031 001DB031 001AF431 00125C2F

00125C2F 00125C2F 001C202F 001A902F 0019C82F 0008FC2F 0008FC2F 0008342F 0008982F
0008982F 0007D02F 0008982F 0008982F 0007D02F 0008342F 0008342F 00076C2F 0008342F
0008342F 0008342F 0008342F 0008342F 0008342F 0008342F 0008342F 0008342F 0008342F
0008342F 0008342F 0008342F 0008342F 0008342F 0008342F 0008342F 0008342F 0008342F
0008342F 0008342F 0008342F 0008342F 0008342F 0008342F 0008342F 0008342F 0008342F
0008342F 0008342F";
//Adding a non-co-coverage neighboring GSM cell for an LTE cell
ADD ELGNCELL: IDTYPE=BYID, LTECellIndex=10, GSMCellIndex=10,
NCellType=CONINTERFGCELL;
On the eNodeB side:

//Adding an SCTP link
ADD SCTPLNK: SCTPNO=1, SN=7, LOCIP="32.132.198.31", LOCPORT=2199,
PEERIP="32.132.198.71", PEERPORT=58090, AUTOSWITCH=ENABLE;
ADD SCTPTEMPLATE: SCTPTEMPLATEID=1, SWITCHBACKFLAG=ENABLE;
ADD SCTPHOST: SCTPHOSTID=1, IPVERSION=IPv4, SIGIP1V4="32.132.198.31",
SIGIP1SECSWITCH=DISABLE, SIGIP2SECSWITCH=DISABLE, PN=2199;
ADD SCTPPEER: SCTPPEERID=1, IPVERSION=IPv4, SIGIP1V4="32.132.198.71",
SIGIP1SECSWITCH=DISABLE, SIGIP2SECSWITCH=DISABLE, PN=58090;
ADD EPGROUP: EPGROUPID=1;
ADD SCTPHOST2EPGRP: EPGROUPID=1, SCTPHOSTID=1;
ADD SCTPPEER2EPGRP: EPGROUPID=1, SCTPPEERID=1;
ADD USERPLANEHOST: UPHOSTID=1, IPVERSION=IPv4, LOCIPV4="32.132.198.31",
IPSECSWITCH=DISABLE;
ADD UPHOST2EPGRP: EPGROUPID=1, UPHOSTID=1;
ADD ECO: EcoId=0, EpGroupCfgFlag=CP_UP_CFG, CpEpGroupId=1, UpEpGroupId=1;
//Configuring LTE frequencies and bandwidth
MOD CELL: LocalCellId=0, UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50;
//Configuring the shared bandwidth for GL DSS and setting Mute RE Switch and UL
Narrowband Interference Restriction Mode
MOD CELLDSS: LocalCellId=0, HighFreqShareRbNum=6, LowFreqShareRbNum=6,
ReMuteSwitch=ON, UlInterfRestrictionMode=BASEBANDPROCESS, A3Offset=-20,
A6Offset=0,SpecShrPfmOptSwitch=FlexSpecSchSwitch-1,SinrThdWithoutGsmInterf=40,GsmI
nterfINThd=8;
//Enabling GL DSS on the eNodeB
MOD CELLALGOSWITCH: LocalCellId=0,
DynSpectrumShareSwitch=GLDynSpectrumShareSwitch-1;
7.4.4 Activation Observation
Message Tracing Mode

The feature is considered enabled if the following messages are received over the Sg interface
between the BSC and the eCoordinator and the Se interface between the eNodeB and the
eCoordinator.
l Messages over the Sg interface

– eCo BSC RESOURCE STATUS REQ
When an interference matrix is imported into the eCoordinator, the eCoordinator
sends an eCo BSC RESOURCE STATUS REQ message to the BSC that controls
the GSM cells, requesting that the BSC sends its resource status.
– BSC RESOURCE STATUS TRANSFER
Upon receiving the eCo BSC RESOURCE STATUS REQ message, the BSC sends
its data configuration to the eCoordinator.
– BSC ARFCN Using STATUS
When the frequency usage in GSM cells changes, the BSC reports the frequency
usage to the eCoordinator.
Figure 7-3 shows examples of messages over the Sg interface.

SingleRAN
Figure 7-3 Examples of messages over the Sg interface
NOTE
When the GSM cell configuration changes, the BSC also sends a BSC RESOURCE STATUS
TRANSFER message to the eCoordinator. Upon receiving this message, the eCoordinator responds with
a BSC RESOURCE STATUS TRANSFER ACK message.
l Messages over the Se interface
– eCo RESOURCE STATUS REQ
When establishing LTE cells on the eCoordinator, the eCoordinator sends its
resource status to the eNodeB.
– eNB RESOURCE STATUS TRANSFER
Upon receiving the eCo RESOURCE STATUS REQ message, the eNodeB sends its
data configuration to the eCoordinator.
– GL DSS Interference Info
After obtaining the interference matrix and GSM frequency usage, the eCoordinator
calculates and sends the RB SINR to the eNodeB through a GL DSS Interference
Info message.
NOTE
When the GSM cell configuration changes, the eNodeB also sends an eNB RESOURCE STATUS
TRANSFER message to the eCoordinator. Upon receiving this message, the eCoordinator responds with
an eNB RESOURCE STATUS TRANSFER ACK message.
Using MML Commands

Use the MML commands on the BSC, eCoordinator, and eNodeB sides to check:
l Whether the links between the BSC and the eCoordinator and between the eNodeB and
eCoordinator are running properly.
l Whether GSM and LTE cells are running properly.
The detailed procedure is as follows:
Step 1 On the BSC side, run the DSP GLDSSSTATUS command to query the GL DSS frequency
status. If the frequency information can be queried, this feature is enabled.
Step 2 On the eNodeB side, run the DSP ECO command to query the status of the interface between
the eNodeB and eCoordinator. If the value of ECO Interface CP Bearer State is Normal,
the interface between the eNodeB and eCoordinator is running properly.
Step 3 On the eCoordinator side, run the DSP GLDSSINFO command to query the status of the GL
DSS feature. If the value of GSM Cell GLDSS State is Normal, the GL DSS running.
----End

SingleRAN
7.4.5 Deactivation
Table 7-6, Table 7-7, and Table 7-8 list the parameters required for deactivating this feature.
Table 7-6 BSC parameters
MO Parameter Name Parameter ID Setting Notes
CELLGLDSS GL Dynamic GLDSSSw(BSC6900, Set this parameter to

Spectrum Sharing BSC6910) OFF(OFF).
Switch
GCELLPSCHM PDCH EnPDAdminOpt(BSC Restore this parameter

Management 6900,BSC6910) to the value before
Optimization feature activation.
Table 7-7 eCoordinator parameters
MO Parameter Name Parameter ID Setting Notes
ELCELLGLDS GL DSS Switch GLDSSSw Set this parameter to

S OFF(OFF).
Table 7-8 eNodeB parameters
MO Parameter Parameter ID Setting Notes

Name
CELLALGOSWITCH Dynamic DynSpectrumShar- Set this parameter

Spectrum eSwitch to OFF(OFF).
Share Switch
CELLDSS Shared RB HighFreqShareRb- Set this parameter

Number in Num to 0.
High
Frequency
CELLDSS Shared RB LowFreqShareRbNu

Number in m
Low
Frequency
CELL UL Bandwidth UlBandWidth Restore the settings

of UlBandWidth
CELL Downlink DlBandWidth and DlBandWidth.
bandwidth
There are two ways of feature deactivation: using the CME and using MML commands

SingleRAN
7.4.5.1 Using the CME

The method of using the CME to deactivate this feature is the same as that of using the CME
to activate this feature. For details, see 7.4.3.2 Using the CME.
7.4.5.2 Using MML Commands

Perform the following operations on the BSC, eCoordinator, and eNodeB sides, respectively.
BSC
Step 1 Run the BSC MML command SET CELLGLDSS with GL DSS Switch set to OFF(Off).
Step 2 Run the BSC MML command SET GCELLPSCHM with PDCH Management
Optimization set to the value configured before this feature is enabled.
----End
eCoordinator
Run the eCoordinator MML command SET ELCELLGLDSS with GL Dynamic Spectrum
Sharing Switch set to OFF(OFF).
eNodeB
Step 1 Run the eNodeB MML command MOD CELLALGOSWITCH with Dynamic Spectrum
Share Switch set to OFF(Off).
Step 2 Run the eNodeB MML command MOD CELLDSS with both Shared RB Number in High
Frequency and Shared RB Number in Low Frequency set to 0.
Step 3 Run the eNodeB MML command MOD CELL to restore the settings of Downlink
EARFCN and Downlink bandwidth.
----End
7.4.5.3 MML Command Examples

On the BSC side:
//Disabling GL DSS
SET CELLGLDSS: IDTYPE=BYID, CELLID=1, GLDSSSw=OFF;
//Disabling the PDCH management optimization algorithm
SET GCELLPSCHM: IDTYPE=BYID, CELLID=1, EnPDAdminOpt=off;
On the eCoordinator side:

//Disabling GL DSS
SET ELCELLGLDSS: Mcc="460", Mnc="20", eNodeBId=255, CellId=2, GLDSSSw=OFF;
On the eNodeB side:

//Disabling GL DSS
MOD CELLALGOSWITCH:
LocalCellId=0,DynSpectrumShareSwitch=GLDynSpectrumShareSwitch-0;
//Setting HighFreqShareRbNum and LowFreqShareRbNum to their default values 0
MOD CELLDSS: LocalCellId=0, HighFreqShareRbNum=0, LowFreqShareRbNum=0;
//Restoring the settings of UlBandWidth and DlBandWidth
MOD CELL: LocalCellId=0, UlBandWidth=CELL_BW_N25, DlBandWidth=CELL_BW_N25;

SingleRAN
7.4.6 Reconfiguration
If the GSM and LTE interference matrix is affected by site addition or deletion, and
adjustment of cell power, antenna azimuth and downtilt, re-calculate the interference matrix.
The interference matrix can be adjusted partially for specific sites.
7.5 Performance Monitoring

After this feature is enabled, compare the cell counters in Table 7-1 with those collected
before feature deployment and observe the throughput improvement in LTE cells and negative
impacts on GSM cells. In addition, observe the common LTE cell counters listed in Table 7-9.
Table 7-9 Common LTE cell counters to be observed
Counter ID Counter Name Counter Description
1526729868 L.Traffic.DL.SCH.Shared. Number of bits of TBs initially

TB.bits transmitted on the downlink SCH in the
shared spectrum
1526729869 L.Traffic.DL.SCH.Shared. Number of TBs initially transmitted on

TB the downlink SCH in the shared
spectrum
1526729870 L.Traffic.DL.SCH.Shared. Number of bits of TBs failed to be

ErrTB.Ibler.bits transmitted during initial transmission
on the downlink SCH in the shared
spectrum
1526729871 L.Traffic.DL.SCH.Shared. Number of TBs failed to be transmitted

ErrTB.Ibler during initial transmission on the
downlink SCH in the shared spectrum
1526729872 L.Thrp.Time.DL.Shared Duration of downlink scheduling in the

shared spectrum
1526729873 L.Thrp.Time.DL.Dedicate Duration of downlink scheduling in the

d dedicated spectrum
1526729874 L.ChMeas.PRB.Shared.D Average number of used downlink PRBs

L.Used.Avg in the shared spectrum
The counters listed in the preceding table can reflect the throughput and throughput rate on
the shared spectrum. In addition, block error rate (BLER) can reflect the quality of shared
RBs.
NOTE
When FlexSpecSchSwitch under the SpecShrPfmOptSwitch parameter is set to ON, the previous
counters are measured for dynamically shared spectrums.
If the throughput rate in LTE cells has minor improvements, check the CS or PS traffic
volume on GSM shared carriers according to the GSM counters listed in Table 7-10.

SingleRAN
l If the total number of GSM shared frequencies is small, GSM CS or PS traffic volume is
high, the shared spectrum that can be used by LTE networks is low, and LTE gains are
low.
l If the total number of occupied TCHs on shared carriers is large, GSM CS traffic volume
is high and LTE gains are low.
l If the total number of occupied PDCHs on shared carriers is large, GSM PS traffic
volume is high and LTE gains are low.
Table 7-10 GSM counters
Counter ID Counter Name Counter Description
1282436391 SHARE.ARFCN.NUM(B Total Number of Shared Frequencies

SC6900,BSC6910) on the GSM Network
1282436392 CELL.OCCUPY.TCH.NU Total Number of Occupied TCHs on

M.IN.SHARE.TRX(BSC6 the Shared TRX
900,BSC6910)
1282436393 CELL.OCCUPY.PDCH.N Total Number of Occupied PDCHs

UM.IN.SHARE.TRX(BSC on the Shared TRX
6900,BSC6910)
7.6 Parameter Optimization

l When strong GSM interference exists on the LTE uplink, it is recommended that
UlInterfRestrictionMode be set to BASEBANDPROCESS.
l When strong LTE interference exists on the GSM downlink, it is recommended that
REMuteSwitch be set to ON.
l If the throughput of some LTE UEs decreases, it is recommended that
SharedTrxPwrDecrSw(BSC6900,BSC6910) be set to ON(On). If the GSM network is
enabled with GBFD-510501 HUAWEI II Handover, it is recommended that
INTRACELLHOEN(BSC6900,BSC6910) be set to YES(Yes) for the BSC.
After SharedTrxPwrDecrSw(BSC6900,BSC6910) is set to ON(On), the number of
GSM intra-cell handovers increases, especially when a large number of MSs are handed
over from shared carriers to exclusive carriers. This is because the handover success rate
decreases due to insufficient channels on exclusive carriers. After a handover fails, the
UE will attempt to perform another handover. Therefore, the number of intra-cell
handovers increases.
l If performance counters show that the BER of the exclusive spectrum increases after the
FlexSpecSchSwitch is turned on, increase the value of SinrThdWithoutGsmInterf so
that the conditions for identifying shared RBs as exclusive RBs become more strict. In
this way, the quality of the exclusive spectrum will not be degraded by identifying shared
RBs as exclusive RBs by mistake.
l After SharedTrxPwrDecrSw(BSC6900,BSC6910) is set to ON(On), if the throughput of
some LTE UEs significantly decreases, properly increase the LTE pilot transmit power
that is calculated based on the GSM/LTE power distribution ratio of 1:1.2. For details,
see 7.1 When to Use.

SingleRAN
In this situation, LTE inter-cell interference increases, which slightly affects the
throughput of UEs at the cell edge. In addition, interference to the GSM network
increases, which slightly jeopardizes performance on the GSM network.
7.7 Possible Issues

None

SingleRAN
Parameter Description 8 Parameters
8 Parameters
Table 8-1 Parameters

Parame NE MML Feature Feature Description
ter ID Comma ID Name
nd
GLDSS BSC690 SET MRFD- NGSM Meaning:

Sw 0 CELLG 090201 and LTE Whether to enable the GL Dynamic Spectrum Sharing
LDSS FDD feature. If this parameter is set to ON, GSM frequency
Dynami spectrum is divided into shared frequency spectrum
c and independent frequency spectrum. Independent
Spectru frequency spectrum is used only by a GSM network.
m Shared frequency spectrum is used by both GSM and
Sharing( LTE network but the GSM network can preferentially
GSM) use the shared frequency spectrum.
If this parameter is set to OFF, the GL Dynamic
Spectrum Sharing feature is disabled.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)

SingleRAN

nd
GLDSS BSC691 SET MRFD- NGSM Meaning:

Sw 0 CELLG 090201 and LTE Whether to enable the GL Dynamic Spectrum Sharing
LDSS FDD feature. If this parameter is set to ON, GSM frequency
Dynami spectrum is divided into shared frequency spectrum
c and independent frequency spectrum. Independent
Spectru frequency spectrum is used only by a GSM network.
m Shared frequency spectrum is used by both GSM and
Sharing( LTE network but the GSM network can preferentially
GSM) use the shared frequency spectrum.
If this parameter is set to OFF, the GL Dynamic
Spectrum Sharing feature is disabled.
Unit: None
LTEDl BSC690 SET MRFD- NGSM Meaning: Downlink central ARFCN for the LTE,
CenterF 0 CELLG 090201 and LTE which is used with "LTEBandWidth" to specify the
req LDSS FDD range of the shared frequency spectrum.
Dynami GUI Value Range: 1~30000
c
Spectru Unit: None
m Actual Value Range: 1~30000
Sharing( Default Value: 30000
GSM)
LTEDl BSC691 SET MRFD- NGSM Meaning: Downlink central ARFCN for the LTE,
CenterF 0 CELLG 090201 and LTE which is used with "LTEBandWidth" to specify the
req LDSS FDD range of the shared frequency spectrum.
Dynami GUI Value Range: 1~30000
c
Spectru Unit: None
Sharing( Default Value: 30000
GSM)
LTEBa BSC690 SET MRFD- NGSM Meaning: LTE bandwidth, which is used with
ndWidt 0 CELLG 090201 and LTE "LTEDlCenterFreq" to specify the range of the shared
h LDSS FDD frequency spectrum.The enumerated value 5M(5M) is
Dynami not used in the current version.
c GUI Value Range: 10M(10M), 15M(15M),
Spectru 20M(20M), 5M(5M)
m
Sharing( Unit: None
GSM) Actual Value Range: 10M, 15M, 20M, 5M
Default Value: 15M(15M)

SingleRAN

nd
LTEBa BSC691 SET MRFD- NGSM Meaning: LTE bandwidth, which is used with
ndWidt 0 CELLG 090201 and LTE "LTEDlCenterFreq" to specify the range of the shared
h LDSS FDD frequency spectrum.The enumerated value 5M(5M) is
Dynami not used in the current version.
c GUI Value Range: 10M(10M), 15M(15M),
Spectru 20M(20M), 5M(5M)
m
Sharing( Unit: None
GSM) Actual Value Range: 10M, 15M, 20M, 5M
Default Value: 15M(15M)
BCCHF BSC690 SET MRFD- NGSM Meaning: Whether the BCCH frequency can be within
reqShar 0 CELLG 090201 and LTE the shared spectrum scope when the GL Dynamic
eSw LDSS FDD Spectrum Sharing feature is enabled. If this parameter
Dynami is set to ON, the BCCH frequency can be within the
c shared spectrum scope. If this parameter is set to OFF,
Spectru the BCCH frequency cannot be within the shared
m spectrum scope.
Sharing( GUI Value Range: OFF(Off), ON(On)
GSM)
Unit: None
BCCHF BSC691 SET MRFD- NGSM Meaning: Whether the BCCH frequency can be within
reqShar 0 CELLG 090201 and LTE the shared spectrum scope when the GL Dynamic
eSw LDSS FDD Spectrum Sharing feature is enabled. If this parameter
Dynami is set to ON, the BCCH frequency can be within the
c shared spectrum scope. If this parameter is set to OFF,
Spectru the BCCH frequency cannot be within the shared
m spectrum scope.
GSM)
Unit: None

SingleRAN

nd
Shared BSC690 SET MRFD- NGSM Meaning: Whether to enable the shared TRX power
TrxPwr 0 CELLG 090201 and LTE decrease function. When this parameter is set to ON,
DecrSw LDSS FDD the static transmit power of the GSM shared TRX is
Dynami decreased. If the independent TRX is busy, the BSC
c preferentially allocates CS calls near the BTS to the
Spectru shared TRX. When this parameter is set to OFF, the
m shared TRX power decrease function is disabled.
GSM)
Unit: None
Shared BSC691 SET MRFD- NGSM Meaning: Whether to enable the shared TRX power
TrxPwr 0 CELLG 090201 and LTE decrease function. When this parameter is set to ON,
DecrSw LDSS FDD the static transmit power of the GSM shared TRX is
Dynami decreased. If the independent TRX is busy, the BSC
c preferentially allocates CS calls near the BTS to the
Spectru shared TRX. When this parameter is set to OFF, the
m shared TRX power decrease function is disabled.
GSM)
Unit: None
Shared BSC690 SET MRFD- NGSM Meaning:

TrxPwr 0 CELLG 090201 and LTE Level of power decrease when the BSC performs
DecrLe LDSS FDD static power control on the shared TRX. There are 50
v Dynami levels in total, and TRX power is decreased by a step
c of 0.2 dB. When this parameter is set to 0, the level of
Spectru the transmit power of the shared TRX is the highest.
m TRX power is decreased level by level at a step of 0.2
Sharing( dB. The BSC does not perform static power control on
GSM) the shared TRX if the following condition is met:
(2 x POWL + 0.1 x PWRSPNR + 0.2 x
SharedTrxPwrDecrLev) > 20
"POWL" and "PWRSPNR" are parameters in the
"SET GTRXDEV" command.
GUI Value Range: 0~50
Unit: 0.2dB
Actual Value Range: 0~10
Default Value: 15

SingleRAN

nd

TrxPwr 0 CELLG 090201 and LTE Level of power decrease when the BSC performs
DecrLe LDSS FDD static power control on the shared TRX. There are 50
v Dynami levels in total, and TRX power is decreased by a step
c of 0.2 dB. When this parameter is set to 0, the level of
Spectru the transmit power of the shared TRX is the highest.
m TRX power is decreased level by level at a step of 0.2
Sharing( dB. The BSC does not perform static power control on
GSM) the shared TRX if the following condition is met:
(2 x POWL + 0.1 x PWRSPNR + 0.2 x
SharedTrxPwrDecrLev) > 20
"POWL" and "PWRSPNR" are parameters in the
"SET GTRXDEV" command.
Unit: 0.2dB
Default Value: 15
AloneTr BSC690 SET MRFD- NGSM Meaning:

xResvC 0 CELLG 090201 and LTE Number of idle TCHs reserved on an independent
hanNu LDSS FDD TRX. This parameter, "GlDssAtcbThld", and
m Dynami "SharedTrxRxLevThld" constitute the conditions for
c determining whether CS calls can occupy the shared
Spectru TRX.
m
Sharing( If the number of idle TCHHs(An idle TCHF is equal
GSM) to two idle TCHHs) on an independent TRX is less
than or equal to the value of this parameter:
When all of the following conditions are met, the BSC
preferentially allocates the call to the shared TRX for
a new CS call or hands over the call with the largest
ATCB from the independent TRX to the shared TRX
for an ongoing CS call.
1. The ATCB of the call is greater than or equal to the
value of "GlDssAtcbThld".
2. The receive level of the call after power control
compensation is greater than or equal to the value of
"SharedTrxRxLevThld".
Unit: None
Default Value: 4

SingleRAN

nd

xResvC 0 CELLG 090201 and LTE Number of idle TCHs reserved on an independent
hanNu LDSS FDD TRX. This parameter, "GlDssAtcbThld", and
m Dynami "SharedTrxRxLevThld" constitute the conditions for
c determining whether CS calls can occupy the shared
Spectru TRX.
m
than or equal to the value of this parameter:
When all of the following conditions are met, the BSC
Unit: None
Default Value: 4

SingleRAN

nd
GlDssA BSC690 SET MRFD- NGSM Meaning:

tcbThld 0 CELLG 090201 and LTE ATCB threshold for the BSC to allocate new or
LDSS FDD ongoing CS calls to the shared TRX. This parameter,
Dynami "AloneTrxResvChanNum", and
c "SharedTrxRxLevThld" constitute the conditions for
Spectru determining whether CS calls can occupy the shared
m TRX.
Sharing(
GSM) If the number of idle TCHHs(An idle TCHF is equal
to two idle TCHHs) on an independent TRX is less
than or equal to "AloneTrxResvChanNum":
when all of the following conditions are met, the BSC
Unit: dB
Default Value: 3

SingleRAN

nd
GlDssA BSC691 SET MRFD- NGSM Meaning:

tcbThld 0 CELLG 090201 and LTE ATCB threshold for the BSC to allocate new or
LDSS FDD ongoing CS calls to the shared TRX. This parameter,
Dynami "AloneTrxResvChanNum", and
c "SharedTrxRxLevThld" constitute the conditions for
Spectru determining whether CS calls can occupy the shared
m TRX.
Sharing(
GSM) If the number of idle TCHHs(An idle TCHF is equal
to two idle TCHHs) on an independent TRX is less
Unit: dB
Default Value: 3

SingleRAN

nd

TrxRxL 0 CELLG 090201 and LTE Receive level threshold for the BSC to allocate new or
evThld LDSS FDD ongoing CS calls to the shared TRX. This parameter,
Dynami "AloneTrxResvChanNum", and "GlDssAtcbThld"
c constitute the conditions for determining whether CS
Spectru calls can occupy the shared TRX.
m
Unit: dB
Default Value: 30

SingleRAN

nd

TrxRxL 0 CELLG 090201 and LTE Receive level threshold for the BSC to allocate new or
evThld LDSS FDD ongoing CS calls to the shared TRX. This parameter,
Dynami "AloneTrxResvChanNum", and "GlDssAtcbThld"
c constitute the conditions for determining whether CS
Spectru calls can occupy the shared TRX.
m
Unit: dB
Default Value: 30
GlDssA BSC690 SET MRFD- NGSM Meaning: ATCB hysteresis for the BSC to hand over
tcbHYS 0 CELLG 090201 and LTE ongoing CS calls from the shared TRX to the
T LDSS FDD independent TRX. The BSC hands over an ongoing
Dynami call from the shared TRX to the independent TRX
c when the ATCB of the call is less than the difference
Spectru between the values of "GlDssAtcbThld" and this
m parameter.
Sharing( GUI Value Range: 0~63
GSM)
Unit: dB
Default Value: 1

SingleRAN

nd
GlDssA BSC691 SET MRFD- NGSM Meaning: ATCB hysteresis for the BSC to hand over
tcbHYS 0 CELLG 090201 and LTE ongoing CS calls from the shared TRX to the
T LDSS FDD independent TRX. The BSC hands over an ongoing
Dynami call from the shared TRX to the independent TRX
c when the ATCB of the call is less than the difference
Spectru between the values of "GlDssAtcbThld" and this
m parameter.
GSM)
Unit: dB
Default Value: 1
Shared BSC690 SET MRFD- NGSM Meaning: Receive level hysteresis for the BSC to
TrxRxL 0 CELLG 090201 and LTE hand over ongoing CS calls from the shared TRX to
evHYS LDSS FDD the independent TRX. The BSC hands over an
T Dynami ongoing call from the shared TRX to the independent
c TRX when the receive level of the call is less than the
Spectru difference between the values of
m "SharedTrxRxLevThld" and this parameter.
GSM)
Unit: dB
Default Value: 10
Shared BSC691 SET MRFD- NGSM Meaning: Receive level hysteresis for the BSC to
TrxRxL 0 CELLG 090201 and LTE hand over ongoing CS calls from the shared TRX to
evHYS LDSS FDD the independent TRX. The BSC hands over an
T Dynami ongoing call from the shared TRX to the independent
c TRX when the receive level of the call is less than the
Spectru difference between the values of
m "SharedTrxRxLevThld" and this parameter.
GSM)
Unit: dB
Default Value: 10

SingleRAN

nd

xHrLd 0 CELLG 090201 and LTE Load threshold offset used for allocating TCHHs or
ThldOff LDSS FDD triggering TCHF-to-TCHH handovers for calls on an
set Dynami independent TRX.
c
Spectru When this parameter is set to 0, the BSC determines
m whether to allocate TCHHs or trigger TCHF-to-
Sharing( TCHH handovers for calls based on the cell load and
GSM) cell load threshold without distinguishing between the
shared TRX and the independent TRX.
When this parameter is not set to 0, the BSC
determines whether to allocate TCHHs or trigger
TCHF-to-TCHH handovers for calls on the shared
TRX or an independent TRX based on the load and
load threshold of the shared TRX and the independent
TRX, respectively. The independent TRX load
threshold equals the shared TRX load threshold minus
the value of this parameter.
Unit: None
Default Value: 0

xHrLd 0 CELLG 090201 and LTE Load threshold offset used for allocating TCHHs or
ThldOff LDSS FDD triggering TCHF-to-TCHH handovers for calls on an
set Dynami independent TRX.
c
Spectru When this parameter is set to 0, the BSC determines
m whether to allocate TCHHs or trigger TCHF-to-
Sharing( TCHH handovers for calls based on the cell load and
GSM) cell load threshold without distinguishing between the
shared TRX and the independent TRX.
When this parameter is not set to 0, the BSC
determines whether to allocate TCHHs or trigger
TCHF-to-TCHH handovers for calls on the shared
TRX or an independent TRX based on the load and
load threshold of the shared TRX and the independent
TRX, respectively. The independent TRX load
threshold equals the shared TRX load threshold minus
the value of this parameter.
Unit: None
Default Value: 0

SingleRAN

nd
AMRT BSC690 SET GBFD-1 Dynami Meaning:

CHHP 0 GCELL 13402 c Whether channels are assigned and TCHF-to-TCHH
RIORA CHMG Adjustm handover decisions are made on the basis of the AMR
LLOW AD ent TCH/H prior cell load threshold if AMR calls are
Between detected.
FR and
HR When this parameter is set to ON, the channel
assignment algorithm uses the AMR TCH/H prior cell
load threshold to determine whether to assign TCHHs
to AMR calls,
and Handover algorithm generation 1 uses the AMR
TCH/H prior cell load threshold to determine whether
to hand over AMR calls occupying TCHFs to TCHHs;
When this parameter is set to OFF, the AMR TCH/H
prior cell load threshold is not used during channel
assignment,
Handover algorithm generation 1 determines whether
to hand over AMR calls occupying TCHFs to TCHHs
without considering traffic in the corresponding cell.
Unit: None
Default Value: ON(On)

SingleRAN

nd
AMRT BSC691 SET GBFD-1 Dynami Meaning:

CHHP 0 GCELL 13402 c Whether channels are assigned and TCHF-to-TCHH
RIORA CHMG Adjustm handover decisions are made on the basis of the AMR
LLOW AD ent TCH/H prior cell load threshold if AMR calls are
Between detected.
FR and
HR When this parameter is set to ON, the channel
assignment algorithm uses the AMR TCH/H prior cell
load threshold to determine whether to assign TCHHs
to AMR calls,
and Handover algorithm generation 1 uses the AMR
TCH/H prior cell load threshold to determine whether
to hand over AMR calls occupying TCHFs to TCHHs;
When this parameter is set to OFF, the AMR TCH/H
prior cell load threshold is not used during channel
assignment,
Handover algorithm generation 1 determines whether
to hand over AMR calls occupying TCHFs to TCHHs
without considering traffic in the corresponding cell.
Unit: None
TCHBU BSC690 SET None None Meaning: If the current channel seizure ratio reaches
SYTHR 0 GCELL or exceeds this value, the half-rate TCH is assigned
ES CHMG preferentially; otherwise, the full-rate TCH is assigned
AD preferentially.
Unit: %
Default Value: 60
TCHBU BSC691 SET None None Meaning: If the current channel seizure ratio reaches
SYTHR 0 GCELL or exceeds this value, the half-rate TCH is assigned
ES CHMG preferentially; otherwise, the full-rate TCH is assigned
AD preferentially.
Unit: %
Default Value: 60

SingleRAN

nd

TrxInte 0 CELLG 090201 and LTE Threshold of level difference between the serving cell
rfHoAtc LDSS FDD and the neighboring cell of a CS call after the BSC
bThld Dynami performs handover decsion for the CS call on the
c shared TRX.
Spectru
m If the level difference between the target cell or
Sharing( candidate neighboring cell and the serving cell is
GSM) greater than or equal to the value of this parameter, the
BSC determines that the resource blocks (RBs)
(corresponding to the shared frequency occupied by
the serving cell of the CS call) used by the co-site co-
coverage LTE cell of the target cell or candidate
neighboring cell cause interference to the call
handover. The serving cell of the call sends a message
to the eCoordinator. The message indicates the
following information: The co-site co-coverage LTE
cell of the target cell cannot schedule the RBs
corresponding to the shared frequency occupied by the
serving cell of the CS call. The co-site co-coverage
LTE cell of the seving cell cannot schedule the RBs
target cell of the CS call. The co-site co-coverage LTE
cell of the candidate neighboring cell cannot schedule
the RBs corresponding to the shared frequency
occupied by the serving or target cell of the CS call.
If the level difference between the target cell or
candidate neighboring cell and the serving cell is less
than the value of this parameter, the BSC hands over
the CS call by following the original procedure.
Unit: dB
Default Value: 8

SingleRAN

nd

TrxInte 0 CELLG 090201 and LTE Threshold of level difference between the serving cell
rfHoAtc LDSS FDD and the neighboring cell of a CS call after the BSC
bThld Dynami performs handover decsion for the CS call on the
c shared TRX.
Spectru
m If the level difference between the target cell or
Sharing( candidate neighboring cell and the serving cell is
GSM) greater than or equal to the value of this parameter, the
BSC determines that the resource blocks (RBs)
(corresponding to the shared frequency occupied by
the serving cell of the CS call) used by the co-site co-
coverage LTE cell of the target cell or candidate
neighboring cell cause interference to the call
handover. The serving cell of the call sends a message
to the eCoordinator. The message indicates the
following information: The co-site co-coverage LTE
cell of the target cell cannot schedule the RBs
serving cell of the CS call. The co-site co-coverage
LTE cell of the seving cell cannot schedule the RBs
target cell of the CS call. The co-site co-coverage LTE
cell of the candidate neighboring cell cannot schedule
the RBs corresponding to the shared frequency
occupied by the serving or target cell of the CS call.
If the level difference between the target cell or
candidate neighboring cell and the serving cell is less
than the value of this parameter, the BSC hands over
the CS call by following the original procedure.
Unit: dB
Default Value: 8
LongCa BSC690 SET MRFD- NGSM Meaning: Threshold for long Call determination.
llDetThl 0 CELLG 090201 and LTE When the number of received TCH MRs is greater
d LDSS FDD than or equal to the value of this parameter, the call is
Dynami a long-time call.
c GUI Value Range: 0~65535
Spectru
m Unit: None
Sharing( Actual Value Range: 0~65535
GSM) Default Value: 400

SingleRAN

nd
LongCa BSC691 SET MRFD- NGSM Meaning: Threshold for long Call determination.
llDetThl 0 CELLG 090201 and LTE When the number of received TCH MRs is greater
d LDSS FDD than or equal to the value of this parameter, the call is
Dynami a long-time call.
c GUI Value Range: 0~65535
Spectru
m Unit: None
Sharing( Actual Value Range: 0~65535
GSM) Default Value: 400
CsRepa BSC690 SET MRFD- NGSM Meaning: Threshold for the number of idle TCHs to
ckingTc 0 CELLG 090201 and LTE trigger a CS handover. If the total number of idle
hIdleNu LDSS FDD TCHHs(An idle TCHF is equal to two idle TCHHs)
m Dynami on independent TRXs and shared TRXs with a higher
c priority than the TRX where the current CS service is
Spectru processed is greater than the value of this parameter,
m the CS service is handed over to an independent TRX
Sharing( or shared TRX. Otherwise, no handling is required.
GSM) GUI Value Range: 0~16
Unit: None
Default Value: 8
CsRepa BSC691 SET MRFD- NGSM Meaning: Threshold for the number of idle TCHs to
ckingTc 0 CELLG 090201 and LTE trigger a CS handover. If the total number of idle
hIdleNu LDSS FDD TCHHs(An idle TCHF is equal to two idle TCHHs)
m Dynami on independent TRXs and shared TRXs with a higher
c priority than the TRX where the current CS service is
Spectru processed is greater than the value of this parameter,
m the CS service is handed over to an independent TRX
Sharing( or shared TRX. Otherwise, no handling is required.
GSM) GUI Value Range: 0~16
Unit: None
Default Value: 8

SingleRAN

nd
GlDssH BSC690 SET MRFD- NGSM Meaning:

oOptSw 0 CELLG 090201 and LTE Whether to enable the handover optimization function
LDSS FDD when the GL DSS feature is enabled.
Dynami
c When this parameter is set to ON, the handover
Spectru optimization function is enabled. In this case, the BSC
m does not consider factors related to layers and loads
Sharing( when selecting target cells during quality-based and
GSM) level-based handovers.
When this parameter is set to OFF, the handover
optimization function is disabled.
Quality-based handovers include bad quality (BQ)
handovers, interference handovers, and handovers due
to no downlink measurement reports. Level-based
handovers refer to edge handovers.
Unit: None
GlDssH BSC691 SET MRFD- NGSM Meaning:

oOptSw 0 CELLG 090201 and LTE Whether to enable the handover optimization function
LDSS FDD when the GL DSS feature is enabled.
Dynami
c When this parameter is set to ON, the handover
Spectru optimization function is enabled. In this case, the BSC
m does not consider factors related to layers and loads
Sharing( when selecting target cells during quality-based and
GSM) level-based handovers.
When this parameter is set to OFF, the handover
optimization function is disabled.
Quality-based handovers include bad quality (BQ)
handovers, interference handovers, and handovers due
to no downlink measurement reports. Level-based
handovers refer to edge handovers.
Unit: None

SingleRAN

nd
LoadHo BSC690 SET GBFD-1 HUAW Meaning: This parameter specifies whether a traffic
En 0 GCELL 10601 EI I load-sharing handover is enabled. The load handover
HOBAS GBFD-5 Handov helps to reduce cell congestion, improve success rate
IC 10501 er of channel assignment, and balance the traffic load
HUAW among cells, thus improving the network
EI II performance. The load handover is used as an
Handov emergency measure instead of a primary measure to
er adjust abnormal traffic burst in partial areas. If load
handovers occur frequently in a partial area, the cell
and TRX configuration of BTSs and the network
layout should be adjusted.
GUI Value Range: NO(No), YES(Yes)
Unit: None
Actual Value Range: NO, YES
Default Value: NO(No)
LoadHo BSC691 SET GBFD-1 HUAW Meaning: This parameter specifies whether a traffic
En 0 GCELL 10601 EI I load-sharing handover is enabled. The load handover
HOBAS GBFD-5 Handov helps to reduce cell congestion, improve success rate
IC 10501 er of channel assignment, and balance the traffic load
HUAW among cells, thus improving the network
EI II performance. The load handover is used as an
Handov emergency measure instead of a primary measure to
er adjust abnormal traffic burst in partial areas. If load
handovers occur frequently in a partial area, the cell
and TRX configuration of BTSs and the network
layout should be adjusted.
Unit: None
HOPRI BSC690 SET GBFD-5 HUAW Meaning: Whether to adjust handover priority in
OMOD 0 GCELL 10501 EI II handover algorithm II. If this parameter is set to
EN HOBAS Handov YES(Yes), an edge handover using handover
IC er algorithm II is not an emergency handover, cell level,
priority, and load are considered in an emergency
handover, and a better cell handover takes precedence
over an emergency handover. If this parameter is set to
NO(No), the handover priority in handover algorithm
II is not adjusted.
Unit: None

SingleRAN

nd
HOPRI BSC691 SET GBFD-5 HUAW Meaning: Whether to adjust handover priority in
OMOD 0 GCELL 10501 EI II handover algorithm II. If this parameter is set to
EN HOBAS Handov YES(Yes), an edge handover using handover
IC er algorithm II is not an emergency handover, cell level,
priority, and load are considered in an emergency
handover, and a better cell handover takes precedence
over an emergency handover. If this parameter is set to
NO(No), the handover priority in handover algorithm
II is not adjusted.
Unit: None
FRING BSC690 SET GBFD-1 HUAW Meaning: Whether to enable the edge handover
EHOE 0 GCELL 10601 EI I algorithm. When an MS makes a call at the edge of a
N HOBAS GBFD-5 Handov cell, the call drops if the receive signal level is too
IC 10501 er low. To avoid such a call drop, the edge handover
HUAW algorithm is used. When the uplink signal level of the
EI II serving cell is less than "Edge HO UL RX_LEV
Handov Threshold" or the downlink signal level of the serving
er cell is less than "Edge HO DL RX_LEV Threshold",
the edge handover is triggered.
Unit: None
Default Value: YES(Yes)
FRING BSC691 SET GBFD-1 HUAW Meaning: Whether to enable the edge handover
EHOE 0 GCELL 10601 EI I algorithm. When an MS makes a call at the edge of a
N HOBAS GBFD-5 Handov cell, the call drops if the receive signal level is too
IC 10501 er low. To avoid such a call drop, the edge handover
HUAW algorithm is used. When the uplink signal level of the
EI II serving cell is less than "Edge HO UL RX_LEV
Handov Threshold" or the downlink signal level of the serving
er cell is less than "Edge HO DL RX_LEV Threshold",
the edge handover is triggered.
Unit: None

SingleRAN

nd
EnPDA BSC690 SET GBFD-1 PDCH Meaning:

dminOp 0 GCELL 13101 Dynami Whether to enable PDCH management optimization
t PSCH c algorithm.
M Adjustm
ent If the parameter is set to OFF(Off), the BSC uses the
original channel management algorithm.
If the parameter is set to ON(On), the BSC uses the
PDCH management optimization algorithm.
Unit: None
EnPDA BSC691 SET GBFD-1 PDCH Meaning:

dminOp 0 GCELL 13101 Dynami Whether to enable PDCH management optimization
t PSCH c algorithm.
M Adjustm
ent If the parameter is set to OFF(Off), the BSC uses the
original channel management algorithm.
If the parameter is set to ON(On), the BSC uses the
PDCH management optimization algorithm.
Unit: None

SingleRAN

nd
GlDssPs BSC690 SET MRFD- NGSM Meaning:

UlLoad 0 CELLG 090201 and LTE Uplink PS service load threshold for a cell after the
Thd LDSS FDD GL DSS feature is enabled. If the average number of
Dynami MSs multiplexed onto each uplink PDCH in a PDCH
c group multiplied by 10 is greater than the value of this
Spectru parameter, independent and shared TRXs have the
m same priority when the BSC allocates PS services. If
Sharing( the average number of MSs multiplexed onto each
GSM) uplink PDCH in a PDCH group multiplied by 10 is
less than or equal to the value of this parameter, the
BSC preferentially allocates PS services to
independent TRXs.
During a load- or duty-cycle-based TCH-PDCH
conversion, or a pre-conversion:
If the average number of MSs multiplexed onto each
uplink PDCH in a cell multiplied by 10 is greater than
the value of this parameter, the BSC preferentially
allocates PS services to independent TRXs.
uplink PDCH in a cell multiplied by 10 is less than or
equal to the value of this parameter, the BSC cannot
allocate PS services to shared TRXs.
It is recommended that this parameter be set to a value
greater than "UPDYNCHNTRANLEV" and less than
"PSServiceBusyThreshold" and "RadioResAdaAdjUl-
LoadThd".
Unit: None
Default Value: 50

SingleRAN

nd

UlLoad 0 CELLG 090201 and LTE Uplink PS service load threshold for a cell after the
Dynami MSs multiplexed onto each uplink PDCH in a PDCH
c group multiplied by 10 is greater than the value of this
Spectru parameter, independent and shared TRXs have the
m same priority when the BSC allocates PS services. If
Sharing( the average number of MSs multiplexed onto each
GSM) uplink PDCH in a PDCH group multiplied by 10 is
independent TRXs.
uplink PDCH in a cell multiplied by 10 is greater than
the value of this parameter, the BSC preferentially
allocates PS services to independent TRXs.
uplink PDCH in a cell multiplied by 10 is less than or
equal to the value of this parameter, the BSC cannot
allocate PS services to shared TRXs.
greater than "UPDYNCHNTRANLEV" and less than
"PSServiceBusyThreshold" and "RadioResAdaAdjUl-
LoadThd".
Unit: None
Default Value: 50

SingleRAN

nd

DlLoad 0 CELLG 090201 and LTE Downlink PS service load threshold for a cell after the
Dynami MSs multiplexed onto each downlink PDCH in a
c PDCH group multiplied by 10 is greater than the value
Spectru of this parameter, independent and shared TRXs have
m the same priority when the BSC allocates PS services.
Sharing( If the average number of MSs multiplexed onto each
GSM) downlink PDCH in a PDCH group multiplied by 10 is
independent TRXs.
downlink PDCH in a cell multiplied by 10 is greater
than the value of this parameter, the BSC
preferentially allocates PS services to independent
TRXs.
downlink PDCH in a cell multiplied by 10 is less than
or equal to the value of this parameter, the BSC
cannot allocate PS services to shared TRXs.
greater than "DWNDYNCHNTRANLEV" and less
than "PSServiceBusyThreshold" and
"RadioResAdaAdjDlLoadThd".
Unit: None
Default Value: 60

SingleRAN

nd

DlLoad 0 CELLG 090201 and LTE Downlink PS service load threshold for a cell after the
Dynami MSs multiplexed onto each downlink PDCH in a
c PDCH group multiplied by 10 is greater than the value
Spectru of this parameter, independent and shared TRXs have
m the same priority when the BSC allocates PS services.
Sharing( If the average number of MSs multiplexed onto each
GSM) downlink PDCH in a PDCH group multiplied by 10 is
independent TRXs.
downlink PDCH in a cell multiplied by 10 is greater
than the value of this parameter, the BSC
preferentially allocates PS services to independent
TRXs.
downlink PDCH in a cell multiplied by 10 is less than
or equal to the value of this parameter, the BSC
cannot allocate PS services to shared TRXs.
greater than "DWNDYNCHNTRANLEV" and less
than "PSServiceBusyThreshold" and
"RadioResAdaAdjDlLoadThd".
Unit: None
Default Value: 60

SingleRAN

nd
UPDYN BSC690 SET GBFD-1 Adaptiv Meaning:

CHNT 0 GCELL 19501 e Dynamic PDCH application and release policy when
RANLE PSCH GBFD-1 Adjustm the cell load changes.
V M 19505 ent of
Uplink The BSC triggers a dynamic PDCH application if
GBFD-1 and "CHIDLHIGHTHR" is set to 100 and the number of
13101 Downlin users carried on the existing PDCHs exceed the value
GBFD-1 k of this parameter divided by 10.
14201 Channel The BSC triggers a dynamic PDCH application when
GBFD-1 s the available bandwidth on PDCHs is less than the
14101 PDCH value of "PDCHGBR" in the "SET BTSOTHPARA"
Dynami command, the proportion of idle TCHs is greater than
GBFD-1 the value of "CHIDLHIGHTHR", and the number of
19303 c
Adjustm users carried on the PDCHs exceeds the value of this
ent with parameter divided by 10.
Two A dynamic channel release is triggered when the
Threshol following conditions are met:
ds "PSDUALTHROPTSW" is set to OFF.
PDCH "CHIDLHIGHTHR" is not set to 100.
Dynami
c The proportion of idle CS channels is lower than
Adjustm "CHIDLLOWTHR".
ent The number of uplink MSs carried on a PDCH is
EGPRS smaller than Uplink Multiplex Threshold of Dynamic
Channel Conversion/10.
GPRS
If Abis or DSP resources are insufficient, the
Load resources of other cells can be preempted only when
Sharing the cell load is higher than Uplink Multiplex
Threshold of Dynamic Channel Conversion/10, and
the resources and channels can be released only when
the cell load is lower than Uplink Multiplex Threshold
of Dynamic Channel Conversion/10.
To implement timely dynamic channel conversion and
reduce channel multiplexing, you are advised to set
"UPDYNCHNTRANLEV" to a value smaller than
"PDCHUPLEV".
Unit: None
Default Value: 40

SingleRAN

nd
UPDYN BSC691 SET GBFD-1 Adaptiv Meaning:

CHNT 0 GCELL 19501 e Dynamic PDCH application and release policy when
RANLE PSCH GBFD-1 Adjustm the cell load changes.
V M 19505 ent of
13101 Downlin users carried on the existing PDCHs exceed the value
GBFD-1 k of this parameter divided by 10.
19303 c
Adjustm users carried on the PDCHs exceeds the value of this
ent with parameter divided by 10.
Dynami
ent The number of uplink MSs carried on a PDCH is
EGPRS smaller than Uplink Multiplex Threshold of Dynamic
Channel Conversion/10.
GPRS
If Abis or GUPPS subsystem resources are
Load insufficient, the resources of other cells can be
Sharing preempted only when the cell load is higher than
Uplink Multiplex Threshold of Dynamic Channel
Conversion/10, and the resources and channels can be
released only when the cell load is lower than Uplink
Multiplex Threshold of Dynamic Channel
Conversion/10.
To implement timely dynamic channel conversion and
"UPDYNCHNTRANLEV" to a value smaller than
"PDCHUPLEV".
Unit: None
Default Value: 40

SingleRAN

nd
DWND BSC690 SET GBFD-1 Adaptiv Meaning:

YNCH 0 GCELL 19501 e Dynamic PDCH application and release policy when
NTRAN PSCH GBFD-1 Adjustm the cell load changes.
LEV M 19505 ent of
13101 Downlin downlink users carried on the existing PDCHs exceed
GBFD-1 k the value of this parameter divided by 10.
19303 c
Adjustm downlink users carried on the PDCHs exceeds the
ent with value of this parameter divided by 10.
Dynami
ent The number of downlink MSs carried on a PDCH is
EGPRS smaller than Downlink Multiplex Threshold of
Dynamic Channel Conversion/10.
GPRS
If Abis or DSP resources are insufficient, the
Load resources of other cells can be preempted only when
Sharing the cell load is higher than Downlink Multiplex
Threshold of Dynamic Channel Conversion/10, and
the resources and channels can be released only when
the cell load is lower than Downlink Multiplex
Threshold of Dynamic Channel Conversion/10. To
implement timely dynamic channel conversion and
"DWNDYNCHNTRANLEV" to a value smaller than
"PDCHDWNLEV".
Unit: None
Default Value: 40

SingleRAN

nd
DWND BSC691 SET GBFD-1 Adaptiv Meaning:

YNCH 0 GCELL 19501 e Dynamic PDCH application and release policy when
NTRAN PSCH GBFD-1 Adjustm the cell load changes.
LEV M 19505 ent of
13101 Downlin downlink users carried on the existing PDCHs exceed
GBFD-1 k the value of this parameter divided by 10.
19303 c
Adjustm downlink users carried on the PDCHs exceeds the
ent with value of this parameter divided by 10.
Dynami
ent The number of downlink MSs carried on a PDCH is
EGPRS smaller than Downlink Multiplex Threshold of
Dynamic Channel Conversion/10.
GPRS
If Abis or GUPPS subsystem resources are
Load insufficient, the resources of other cells can be
Sharing preempted only when the cell load is higher than
Downlink Multiplex Threshold of Dynamic Channel
Conversion/10, and the resources and channels can be
released only when the cell load is lower than
Downlink Multiplex Threshold of Dynamic Channel
Conversion/10. To implement timely dynamic channel
conversion and reduce channel multiplexing, you are
advised to set "DWNDYNCHNTRANLEV" to a
value smaller than "PDCHDWNLEV".
Unit: None
Default Value: 40

SingleRAN

nd
TchAct BSC690 SET MRFD- NGSM Meaning:

Delay 0 CELLG 090201 and LTE Delay in sending a CHANNEL ACT message from
LDSS FDD the BSC to the BTS. If the BSC allocates channels on
Dynami a shared TRX to GSM services, the BSC sends a
c CHANNEL ACT message to the BTS after the
Spectru frequency spectrum resource is released on the LTE
m network.
Sharing(
GSM) If this parameter is set to 0, the BSC does not delay in
sending a CHANNEL ACT message to the BTS.
Unit: 10ms
Default Value: 10
TchAct BSC691 SET MRFD- NGSM Meaning:

Delay 0 CELLG 090201 and LTE Delay in sending a CHANNEL ACT message from
LDSS FDD the BSC to the BTS. If the BSC allocates channels on
Dynami a shared TRX to GSM services, the BSC sends a
c CHANNEL ACT message to the BTS after the
Spectru frequency spectrum resource is released on the LTE
m network.
Sharing(
GSM) If this parameter is set to 0, the BSC does not delay in
sending a CHANNEL ACT message to the BTS.
Unit: 10ms
Default Value: 10

SingleRAN

nd
ECOM BSC690 SET MRFD- NGSM Meaning:

SGIdle 0 CELLG 090201 and LTE Threshold for the number of idle TCHHs(An idle
TchNu LDSS FDD TCHF is equal to two idle TCHHs) for determining
m Dynami whether shared frequencies are occupied when the
c BSC sends messages to the eCoordinator.
Spectru
m The BSC determines that the frequencies on a shared
Sharing( TRX are idle if the following condition is met:
GSM) Number of idle TCHHs on shared TRXs with a higher
priority than the current shared TRX + Number of idle
TCHHs on independent TRXs >=
"ECOMSGIdleTchNum"
Otherwise, the BSC determines that the frequencies
on the shared TRX are occupied.
Unit: None
Default Value: 0
ECOM BSC691 SET MRFD- NGSM Meaning:

SGIdle 0 CELLG 090201 and LTE Threshold for the number of idle TCHHs(An idle
TchNu LDSS FDD TCHF is equal to two idle TCHHs) for determining
m Dynami whether shared frequencies are occupied when the
c BSC sends messages to the eCoordinator.
Spectru
m The BSC determines that the frequencies on a shared
Sharing( TRX are idle if the following condition is met:
GSM) Number of idle TCHHs on shared TRXs with a higher
priority than the current shared TRX + Number of idle
TCHHs on independent TRXs >=
"ECOMSGIdleTchNum"
Otherwise, the BSC determines that the frequencies
on the shared TRX are occupied.
Unit: None
Default Value: 0

SingleRAN

nd
PSServi BSC690 SET GBFD-1 PDCH Meaning: Threshold of the average number of MSs
ceBusy 0 GCELL 13101 Dynami multiplexed on each PDCH in a cell. When the
Thresho PSCH c average number of uplink or downlink TBFs
ld M Adjustm multiplexed on each PDCH in a cell multiplexed by
ent 10 is greater than or equal to this threshold, the PS
traffic volume in the cell is considered to be high. In
this case, each PS user is assigned only one PDCH.
When the PS traffic volume is not high, the PS users
with only one PDCH is re-assigned a certain number
of PDCHs based on the actual service conditions.
Unit: None
Default Value: 80
PSServi BSC691 SET GBFD-1 PDCH Meaning: Threshold of the average number of MSs
ceBusy 0 GCELL 13101 Dynami multiplexed on each PDCH in a cell. When the
Thresho PSCH c average number of uplink or downlink TBFs
ld M Adjustm multiplexed on each PDCH in a cell multiplexed by
ent 10 is greater than or equal to this threshold, the PS
traffic volume in the cell is considered to be high. In
this case, each PS user is assigned only one PDCH.
When the PS traffic volume is not high, the PS users
with only one PDCH is re-assigned a certain number
of PDCHs based on the actual service conditions.
Unit: None
Default Value: 80

SingleRAN

nd
RadioR BSC690 SET GBFD-1 PS Meaning:

esAdaA 0 GCELL 19408 Access Downlink load threshold for the PS Access
djDlLoa PSCH Congesti Congestion Balancing Feature.
dThd M on
Balancin In a common cell, if the downlink load on the EGPRS
g PDCHs or PDCHs available for GPRS TBFs is greater
than the value of this parameter, the BSC disables the
delayed downlink TBFs release and early downlink
TBF establishment functions for all downlink EGPRS
or GPRS TBFs in the cell and directly releases the
downlink EGPRS or GPRS TBFs in the delayed
release state. If the downlink load on the EGPRS
PDCHs or PDCHs available for GPRS TBFs is less
than or equal to the value of this parameter, the BSC
enables the delayed downlink TBFs release and early
downlink TBF establishment functions for all
downlink EGPRS or GPRS TBFs in the cell.
In a concentric cell, the load on PDCHs in the
underlaid cell and that in the overlaid subcell are
separately considered and calculated. The specific
processing is the same as that in a common cell.
The downlink load on the EGPRS PDCHs or PDCHs
available for GPRS TBFs is calculated using the
following formula: Average number of downlink
TBFs multiplexed on the EGPRS PDCHs or PDCHs
available for GPRS TBFs x 10.
Unit: None
Default Value: 80

SingleRAN

nd

esAdaA 0 GCELL 19408 Access Downlink load threshold for the PS Access
djDlLoa PSCH Congesti Congestion Balancing Feature.
dThd M on
Balancin In a common cell, if the downlink load on the EGPRS
delayed downlink TBFs release and early downlink
TBF establishment functions for all downlink EGPRS
or GPRS TBFs in the cell and directly releases the
downlink EGPRS or GPRS TBFs in the delayed
release state. If the downlink load on the EGPRS
PDCHs or PDCHs available for GPRS TBFs is less
than or equal to the value of this parameter, the BSC
enables the delayed downlink TBFs release and early
downlink TBF establishment functions for all
downlink EGPRS or GPRS TBFs in the cell.
The downlink load on the EGPRS PDCHs or PDCHs
following formula: Average number of downlink
TBFs multiplexed on the EGPRS PDCHs or PDCHs
Unit: None
Default Value: 80

SingleRAN

nd

esAdaA 0 GCELL 19408 Access Uplink load threshold for the PS Access Congestion
djUlLoa PSCH Congesti Balancing Feature.
dThd M on
Balancin In a common cell, if the uplink load on the EGPRS
uplink extended inactive period and the uplink non-
extended delayed release functions for all uplink
EGPRS or GPRS TBFs in the cell and directly
releases the uplink EGPRS or GPRS TBFs in the
uplink extended inactive period or uplink non-
extended delayed release status. If the uplink load on
the EGPRS PDCHs or PDCHs available for GPRS
TBFs is less than or equal to the value of this
parameter, the BSC enables the uplink extended
inactive period and the uplink non-extended delayed
release functions for all uplink EGPRS or GPRS TBFs
in the cell.
The uplink load on the EGPRS PDCHs or PDCHs
following formula: Average number of uplink TBFs
multiplexed on the EGPRS PDCHs or PDCHs
Unit: None
Default Value: 70

SingleRAN

nd

esAdaA 0 GCELL 19408 Access Uplink load threshold for the PS Access Congestion
djUlLoa PSCH Congesti Balancing Feature.
dThd M on
Balancin In a common cell, if the uplink load on the EGPRS
uplink extended inactive period and the uplink non-
extended delayed release functions for all uplink
EGPRS or GPRS TBFs in the cell and directly
releases the uplink EGPRS or GPRS TBFs in the
uplink extended inactive period or uplink non-
extended delayed release status. If the uplink load on
the EGPRS PDCHs or PDCHs available for GPRS
TBFs is less than or equal to the value of this
parameter, the BSC enables the uplink extended
inactive period and the uplink non-extended delayed
release functions for all uplink EGPRS or GPRS TBFs
in the cell.
The uplink load on the EGPRS PDCHs or PDCHs
following formula: Average number of uplink TBFs
multiplexed on the EGPRS PDCHs or PDCHs
Unit: None
Default Value: 70
PBGTS BSC690 ADD GBFD-1 HUAW Meaning: The triggering of PBGT handovers must
TAT 0 G2GNC 10601 EI I meet the P/N criteria. A PBGT handover is triggered
ELL Handov when P of N measurement reports meet the condition
MOD er for PBGT handovers. This parameter corresponds to
G2GNC the N in the P/N criteria.
ELL GUI Value Range: 1~32
Unit: 480ms
Default Value: 8

SingleRAN

nd
PBGTS BSC691 ADD GBFD-1 HUAW Meaning: The triggering of PBGT handovers must
TAT 0 G2GNC 10601 EI I meet the P/N criteria. A PBGT handover is triggered
G2GNC the N in the P/N criteria.
Unit: 480ms
Default Value: 8
PBGTL BSC690 ADD GBFD-1 HUAW Meaning: The triggering of PBGT handovers must
AST 0 G2GNC 10601 EI I meet the P/N criteria. A PBGT handover is triggered
G2GNC the P in the P/N criteria.
Unit: 480ms
Default Value: 6
PBGTL BSC691 ADD GBFD-1 HUAW Meaning: The triggering of PBGT handovers must
AST 0 G2GNC 10601 EI I meet the P/N criteria. A PBGT handover is triggered
G2GNC the P in the P/N criteria.
Unit: 480ms
Default Value: 6
NCELL BSC690 ADD GBFD-1 HUAW Meaning: Level for penalties in a neighboring cell
PUNLE 0 G2GNC 10601 EI I during PBGT, concentric cell handover, or
V ELL GBFD-5 Handov hierarchical handovers in the case of Huawei
MOD 10501 er handover algorithm I or during better cell handovers
G2GNC HUAW in the case of Huawei handover algorithm II.
ELL EI II GUI Value Range: 0~63
Handov Unit: dB
er
Default Value: 10

SingleRAN

nd
NCELL BSC691 ADD GBFD-1 HUAW Meaning: Level for penalties in a neighboring cell
PUNLE 0 G2GNC 10601 EI I during PBGT, concentric cell handover, or
V ELL GBFD-5 Handov hierarchical handovers in the case of Huawei
MOD 10501 er handover algorithm I or during better cell handovers
G2GNC HUAW in the case of Huawei handover algorithm II.
ELL EI II GUI Value Range: 0~63
Handov Unit: dB
er
Default Value: 10
DATAS BSC690 SET GBFD-1 HUAW Meaning: Number of measurement reports sampled
TRFLT 0 GCELL 10601 EI I for averaging the signal strength on a speech or data
LEN HOFIT GBFD-5 Handov channel. Averaging the signal strength in multiple
PEN 10501 er measurement reports helps to prevent sharp
HUAW deterioration of the signal level due to Rayleigh fading
EI II and to ensure a comprehensive handover decision.
Handov GUI Value Range: 1~31
er Unit: 480ms
Default Value: 4
DATAS BSC691 SET GBFD-1 HUAW Meaning: Number of measurement reports sampled
TRFLT 0 GCELL 10601 EI I for averaging the signal strength on a speech or data
LEN HOFIT GBFD-5 Handov channel. Averaging the signal strength in multiple
HUAW deterioration of the signal level due to Rayleigh fading
EI II and to ensure a comprehensive handover decision.
Handov GUI Value Range: 1~31
er Unit: 480ms
Default Value: 4
DATAQ BSC690 SET GBFD-1 HUAW Meaning: Number of measurement reports sampled
UAFLT 0 GCELL 10601 EI I for averaging the signal quality on a speech or data
LEN HOFIT GBFD-5 Handov channel. Averaging the signal quality in multiple
HUAW deterioration of the signal quality due to Rayleigh
EI II fading and to ensure a comprehensive handover
Handov decision.
er GUI Value Range: 1~31
Unit: 480ms
Default Value: 4

SingleRAN

nd
DATAQ BSC691 SET GBFD-1 HUAW Meaning: Number of measurement reports sampled
UAFLT 0 GCELL 10601 EI I for averaging the signal quality on a speech or data
LEN HOFIT GBFD-5 Handov channel. Averaging the signal quality in multiple
HUAW deterioration of the signal quality due to Rayleigh
EI II fading and to ensure a comprehensive handover
Handov decision.
Unit: 480ms
Default Value: 4
NCELL BSC690 SET GBFD-1 HUAW Meaning: For the purpose of accurately reflecting the
FLTLE 0 GCELL 10601 EI I radio environment of a network, the measured values
N HOFIT GBFD-5 Handov in several consecutive measurement reports are
PEN 10501 er filtered. This parameter indicates the number of
HUAW measurement reports used when filtering is performed
EI II on neighboring cell signal strength measured on
Handov TCHs.
Unit: 470ms; 480ms
Actual Value Range: 480~14880(TCH);
470~14570(SDCCH)
Default Value: 4
NCELL BSC691 SET GBFD-1 HUAW Meaning: For the purpose of accurately reflecting the
FLTLE 0 GCELL 10601 EI I radio environment of a network, the measured values
N HOFIT GBFD-5 Handov in several consecutive measurement reports are
PEN 10501 er filtered. This parameter indicates the number of
HUAW measurement reports used when filtering is performed
EI II on neighboring cell signal strength measured on
Handov TCHs.
Unit: 470ms; 480ms
Actual Value Range: 480~14880(TCH);
470~14570(SDCCH)
Default Value: 4
PWRC BSC690 SET GBFD-1 HUAW Meaning: Whether to enable the power control
TRLOP 0 GCELL 17601 EI III optimization algorithm III.
TIMIZ PWR3 Power GUI Value Range: NO(No), YES(Yes)
EDEN Control
Algorith Unit: None
m Actual Value Range: NO, YES

SingleRAN

nd
PWRC BSC691 SET GBFD-1 HUAW Meaning: Whether to enable the power control
TRLOP 0 GCELL 17601 EI III optimization algorithm III.
TIMIZ PWR3 Power GUI Value Range: NO(No), YES(Yes)
EDEN Control
Algorith Unit: None
m Actual Value Range: NO, YES
DLREX BSC690 SET GBFD-1 HUAW Meaning:

LEVAD 0 GCELL 17601 EI III This parameter specifies the downlink signal strength
JFCTR PWR3 Power factor multiplied by 10 during the calculation of the
Control downlink power control step.
Algorith
m The downlink signal strength factor is a coefficient
indicating how much the signal strength is considered
during the calculation of the downlink power control
step.
Unit: None
Default Value: 3
DLREX BSC691 SET GBFD-1 HUAW Meaning:

LEVAD 0 GCELL 17601 EI III This parameter specifies the downlink signal strength
JFCTR PWR3 Power factor multiplied by 10 during the calculation of the
Control downlink power control step.
Algorith
m The downlink signal strength factor is a coefficient
indicating how much the signal strength is considered
step.
Unit: None
Default Value: 3

SingleRAN

nd
DLREX BSC690 SET GBFD-1 IBCA Meaning:

QUAL 0 GCELL 17002 (Interfer This parameter specifies the downlink quality level
ADJFC PWR3 GBFD-1 ence factor multiplied by 10 during the calculation of the
TR 17601 Based downlink power control step.
Channel
Allocati The downlink quality level factor is a coefficient
on) indicating how much the quality level is considered
HUAW step.
EI III
Power GUI Value Range: 0~10
Control Unit: None
Algorith Actual Value Range: 0~10
m
Default Value: 4
DLREX BSC691 SET GBFD-1 IBCA Meaning:

QUAL 0 GCELL 17002 (Interfer This parameter specifies the downlink quality level
ADJFC PWR3 GBFD-1 ence factor multiplied by 10 during the calculation of the
TR 17601 Based downlink power control step.
Channel
Allocati The downlink quality level factor is a coefficient
on) indicating how much the quality level is considered
HUAW step.
EI III
Power GUI Value Range: 0~10
Control Unit: None
Algorith Actual Value Range: 0~10
m
Default Value: 4
DLMA BSC690 SET GBFD-1 HUAW Meaning: Maximum step by which to decrease
XDOW 0 GCELL 17601 EI III downlink power according to signal strength.
NSTEP PWR3 Power GUI Value Range: 1~30
Control
Algorith Unit: dB
Default Value: 30
DLMA BSC691 SET GBFD-1 HUAW Meaning: Maximum step by which to decrease
XDOW 0 GCELL 17601 EI III downlink power according to signal strength.
NSTEP PWR3 Power GUI Value Range: 1~30
Control
Algorith Unit: dB
Default Value: 30

SingleRAN

nd
DLMA BSC690 SET GBFD-1 HUAW Meaning: Maximum step by which to increase
XUPST 0 GCELL 17601 EI III downlink power according to signal strength.
EP PWR3 Power GUI Value Range: 1~30
Control
Algorith Unit: dB
Default Value: 30
DLMA BSC691 SET GBFD-1 HUAW Meaning: Maximum step by which to increase
XUPST 0 GCELL 17601 EI III downlink power according to signal strength.
EP PWR3 Power GUI Value Range: 1~30
Control
Algorith Unit: dB
Default Value: 30
DLRXL BSC690 SET GBFD-1 HUAW Meaning: A power control step cannot exceed the step
EVPRO 0 GCELL 17601 EI III computed according to "III DL RexLev Protect
TECTF PWR3 Power Factor" and "III DL RexQual Protect Factor".
ACTO Control GUI Value Range: 0~100
R Algorith
m Unit: None
Default Value: 20
DLRXL BSC691 SET GBFD-1 HUAW Meaning: A power control step cannot exceed the step
EVPRO 0 GCELL 17601 EI III computed according to "III DL RexLev Protect
TECTF PWR3 Power Factor" and "III DL RexQual Protect Factor".
ACTO Control GUI Value Range: 0~100
R Algorith
m Unit: None
Default Value: 20
DLRX BSC690 SET GBFD-1 HUAW Meaning: A power control step cannot exceed the step
QUALP 0 GCELL 17601 EI III computed according to "III DL RexLev Protect
ROTEC PWR3 Power Factor" and "III DL RexQual Protect Factor".
TFACT Control GUI Value Range: 0~100
OR Algorith
m Unit: None
Default Value: 60

SingleRAN

nd
DLRX BSC691 SET GBFD-1 HUAW Meaning: A power control step cannot exceed the step
QUALP 0 GCELL 17601 EI III computed according to "III DL RexLev Protect
ROTEC PWR3 Power Factor" and "III DL RexQual Protect Factor".
TFACT Control GUI Value Range: 0~100
OR Algorith
m Unit: None
Default Value: 60
DLADJ BSC690 SET GBFD-1 HUAW Meaning: Minimum interval between two consecutive
PRD 0 GCELL 17601 EI III downlink power control commands.
PWR3 Power GUI Value Range: 0~255
Control
Algorith Unit: 470ms; 480ms
m Actual Value Range: 0~122400(TCH);
0~119850(SDCCH)
Default Value: 2
DLADJ BSC691 SET GBFD-1 HUAW Meaning: Minimum interval between two consecutive
PRD 0 GCELL 17601 EI III downlink power control commands.
PWR3 Power GUI Value Range: 0~255
Control
Algorith Unit: 470ms; 480ms
m Actual Value Range: 0~122400(TCH);
0~119850(SDCCH)
Default Value: 2
DLREX BSC690 SET GBFD-1 HUAW Meaning: Length of the exponential filter for
QUALE 0 GCELL 17601 EI III downlink signal quality. A single measurement report
XPFLT PWR3 Power cannot reflect the actual network situations accurately.
LEN Control Therefore, the BSC needs to filter the measured values
Algorith in several successive measurement reports to reflect
m the radio environment.
Unit: 470ms; 480ms
Actual Value Range: 0~9120(TCH);0~8930(SDCCH)
Default Value: 3

SingleRAN

nd
QUALE 0 GCELL 17601 EI III downlink signal quality. A single measurement report
XPFLT PWR3 Power cannot reflect the actual network situations accurately.
LEN Control Therefore, the BSC needs to filter the measured values
Algorith in several successive measurement reports to reflect
m the radio environment.
Unit: 470ms; 480ms
Default Value: 3
LEVEX 0 GCELL 17601 EI III downlink signal strength. A single measurement
PFLTL PWR3 Power report cannot reflect the actual network situations
EN Control accurately. Therefore, the BSC needs to filter the
Algorith measured values in several successive measurement
m reports to reflect the radio environment.
Unit: 470ms; 480ms
Default Value: 3
LEVEX 0 GCELL 17601 EI III downlink signal strength. A single measurement
PFLTL PWR3 Power report cannot reflect the actual network situations
EN Control accurately. Therefore, the BSC needs to filter the
Algorith measured values in several successive measurement
m reports to reflect the radio environment.
Unit: 470ms; 480ms
Default Value: 3
DLFIL BSC690 SET GBFD-1 HUAW Meaning: Filter adjustment factor for downlink power
TADJF 0 GCELL 17601 EI III control. Setting this parameter high helps to smooth
ACTO PWR3 Power the filtered values and to reduce the impact of poor
R Control measurement reports on the filtered values. Setting
Algorith this parameter low helps to draw the filtered values
m close to the actual values and to heighten the power
control effect.
Unit: None
Default Value: 3

SingleRAN

nd
DLFIL BSC691 SET GBFD-1 HUAW Meaning: Filter adjustment factor for downlink power
TADJF 0 GCELL 17601 EI III control. Setting this parameter high helps to smooth
ACTO PWR3 Power the filtered values and to reduce the impact of poor
R Control measurement reports on the filtered values. Setting
Algorith this parameter low helps to draw the filtered values
m close to the actual values and to heighten the power
control effect.
Unit: None
Default Value: 3
DlMax BSC690 SET GBFD-1 HUAW Meaning: Whether the downlink power control
DownO 0 GCELL 17601 EI III amplitude pre-evaluation optimization function takes
ptiSw PWR3 Power effect. When this parameter is set to ON, the delivered
Control class of the active or common power control is the
Algorith smaller value between the pre-evaluated downlink
m power control amplitude and the value of
"MaxBtsPwrNum". When this parameter is set to
OFF, this function does not take effect.
Unit: None
DlMax BSC691 SET GBFD-1 HUAW Meaning: Whether the downlink power control
DownO 0 GCELL 17601 EI III amplitude pre-evaluation optimization function takes
ptiSw PWR3 Power effect. When this parameter is set to ON, the delivered
Control class of the active or common power control is the
Algorith smaller value between the pre-evaluated downlink
m power control amplitude and the value of
"MaxBtsPwrNum". When this parameter is set to
OFF, this function does not take effect.
Unit: None
MaxBts BSC690 SET GBFD-1 IBCA Meaning: Maximum degree by which the BSC can
PwrNu 0 GCELL 17002 (Interfer control the power of the BTS dynamically.
m PWR3 ence GUI Value Range: 1~16
Based
Channel Unit: 2dB
Allocati Actual Value Range: 2~32
on) Default Value: 16

SingleRAN

nd
MaxBts BSC691 SET GBFD-1 IBCA Meaning: Maximum degree by which the BSC can
PwrNu 0 GCELL 17002 (Interfer control the power of the BTS dynamically.
m PWR3 ence GUI Value Range: 1~16
Based
Channel Unit: 2dB
Allocati Actual Value Range: 2~32
on) Default Value: 16
INTRA BSC690 SET GBFD-1 HUAW Meaning: Whether to allow intra-cell handovers.
CELLH 0 GCELL 10601 EI I Forced intra-cell handovers or AMR TCHF-to-TCHH
OEN HOBAS GBFD-5 Handov handovers in the case of Huawei handover algorithm I
IC 10501 er are not subject to this parameter.
HUAW GUI Value Range: NO(No), YES(Yes)
EI II Unit: None
Handov
er Actual Value Range: NO, YES
INTRA BSC691 SET GBFD-1 HUAW Meaning: Whether to allow intra-cell handovers.
CELLH 0 GCELL 10601 EI I Forced intra-cell handovers or AMR TCHF-to-TCHH
OEN HOBAS GBFD-5 Handov handovers in the case of Huawei handover algorithm I
IC 10501 er are not subject to this parameter.
HUAW GUI Value Range: NO(No), YES(Yes)
EI II Unit: None
Handov
er Actual Value Range: NO, YES

SingleRAN
Parameter Description 9 Counters
9 Counters
Table 9-1 Counters

Counter ID Counter Counter NE Feature ID Feature Name
Name Description
1282436273 LONGTIME.C R9222C:Numbe BSC6900 MRFD-090201 GSM and LTE

ALL.HANDOV r of Long-Time FDD Dynamic
ER.NUM CS Call Spectrum
Handovers Sharing(GSM)
1282436391 SHARE.ARFC R9222D:Total BSC6900 MRFD-090201 GSM and LTE

N.NUM Number of MRFD-111401 FDD Dynamic
Shared Spectrum
Frequencies on Sharing(GSM)
the GSM GSM and LTE
Network Zero
BufferZone
1282436392 CELL.OCCUP R9222E:Total BSC6900 MRFD-090201 GSM and LTE

Y.TCH.NUM.I Number of FDD Dynamic
N.SHARE.TRX Occupied TCHs Spectrum
on the Shared Sharing(GSM)
TRX
1282436393 CELL.OCCUP R9222F:Total BSC6900 MRFD-090201 GSM and LTE

Y.PDCH.NUM. Number of FDD Dynamic
IN.SHARE.TR Occupied Spectrum
X PDCHs on the Sharing(GSM)
Shared TRX
1282437006 CELL.INTRAC R92230:Numbe BSC6900 MRFD-090201 GSM and LTE

ELL.HO.REQ.I r of Handover FDD Dynamic
NDEPENDENT Requests from Spectrum
.SHARE Independent Sharing(GSM)
TRX to Shared
TRX

SingleRAN

Name Description

ELL.HO.FAIL.I r of Handover FDD Dynamic
NDEPENDENT Failures from Spectrum
TRX to Shared
TRX

ELL.HO.REQ.S r of Handover FDD Dynamic
HARE.INDEPE Requests from Spectrum
NDENT Shared TRX to Sharing(GSM)
Independent
TRX

ELL.HO.FAIL. r of Handover FDD Dynamic
SHARE.INDEP Failures from Spectrum
ENDENT Shared TRX to Sharing(GSM)
Independent
TRX
1282436273 LONGTIME.C R9222C:Numbe BSC6910 MRFD-090201 GSM and LTE

ALL.HANDOV r of Long-Time FDD Dynamic
ER.NUM CS Call Spectrum
Handovers Sharing(GSM)
1282436391 SHARE.ARFC R9222D:Total BSC6910 MRFD-090201 GSM and LTE

N.NUM Number of MRFD-111401 FDD Dynamic
Shared Spectrum
Frequencies on Sharing(GSM)
the GSM GSM and LTE
Network Zero
BufferZone
1282436392 CELL.OCCUP R9222E:Total BSC6910 MRFD-090201 GSM and LTE

Y.TCH.NUM.I Number of FDD Dynamic
N.SHARE.TRX Occupied TCHs Spectrum
on the Shared Sharing(GSM)
TRX
1282436393 CELL.OCCUP R9222F:Total BSC6910 MRFD-090201 GSM and LTE

Y.PDCH.NUM. Number of FDD Dynamic
IN.SHARE.TR Occupied Spectrum
X PDCHs on the Sharing(GSM)
Shared TRX

SingleRAN

Name Description

ELL.HO.REQ.I r of Handover FDD Dynamic
NDEPENDENT Requests from Spectrum
TRX to Shared
TRX

ELL.HO.FAIL.I r of Handover FDD Dynamic
NDEPENDENT Failures from Spectrum
TRX to Shared
TRX

ELL.HO.REQ.S r of Handover FDD Dynamic
HARE.INDEPE Requests from Spectrum
NDENT Shared TRX to Sharing(GSM)
Independent
TRX

ELL.HO.FAIL. r of Handover FDD Dynamic
SHARE.INDEP Failures from Spectrum
ENDENT Shared TRX to Sharing(GSM)
Independent
TRX

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

SingleRAN
Parameter Description 11 Reference Documents
11 Reference Documents
1. Channel Management Feature Parameter Description for GBSS

2. GPRS EGPRS Channel Management Feature Parameter Description for GBSS
3. BSC6910 GSM Initial Configuration Guide/BSC6900 GSM Initial Configuration Guide
4. Stand-alone ECO6910 Initial Configuration Guide
5. Built-in ECO6910 Initial Configuration Guide


GSM and LTE FDD Dynamic Spectrum Sharing (SRAN11.1 - 03)

Загружено:

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

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

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

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

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

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

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

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

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

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

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

GSM and LTE FDD Dynamic Spectrum Sharing (SRAN11.1 - 03)

Загружено:

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

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

SingleRAN

GSM and LTE FDD Dynamic

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2016-06-30) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

3 Optimization of CS/PS Channel Allocation on the GSM Side.......................................... 10

4 Resource Allocation and Scheduling on the LTE Side........................................................ 19

Issue 03 (2016-06-30) Huawei Proprietary and Confidential ii

Issue 03 (2016-06-30) Huawei Proprietary and Confidential iii

1 About This Document

This document covers the following features:

l MRFD-090201 GSM and LTE FDD Dynamic Spectrum Sharing(GSM)

1.2 Intended Audience

l Need to understand the features described herein

1.3 Change History

Issue 03 (2016-06-30) Huawei Proprietary and Confidential 1

Change Change Description Paramete

Feature Added descriptions of the LEOFD-111302 Flexible Bandwidth None

Editorial None None

Change Change Description Parameter

Feature Added the GSM tight frequency reuse scenario as an None

Editorial Added GBFD-113201 Concentric Cell to the list of impacted None

Change Change Description Parameter Change

Feature None None

Editorial Added the following features to the list of None

SRAN11.1 Draft A (2015-12-30)

Issue 03 (2016-06-30) Huawei Proprietary and Confidential 2

Change Change Description Parameter Change

Feature Added flexible exclusive scheduling of Added the following

Added the support of this feature by the None

Editorial Revised descriptions in the "Using the None

Revised the format in 5 Related None

1.4 Differences Between Base Station Types

Issue 03 (2016-06-30) Huawei Proprietary and Confidential 3

Issue 03 (2016-06-30) Huawei Proprietary and Confidential 4

Figure 2-1 Dedicated and shared spectrums

Issue 03 (2016-06-30) Huawei Proprietary and Confidential 5

Table 2-1 LTE throughput gains

Scenario 1: More than 40% Up to 90% About 15%

Issue 03 (2016-06-30) Huawei Proprietary and Confidential 6

Scenario DL LTE Throughput DL LTE UL LTE Throughput

Scenario 2: More than 15% Up to 45% About 8%

Scenario 3: More than 5% Up to 30% About 5%

Issue 03 (2016-06-30) Huawei Proprietary and Confidential 7

Figure 2-3 Architecture for information exchange between NEs

Table 2-2 Functions of NEs during the implementation of this feature

Issue 03 (2016-06-30) Huawei Proprietary and Confidential 8

Issue 03 (2016-06-30) Huawei Proprietary and Confidential 9

3 Optimization of CS/PS Channel Allocation

To enable GL DSS on the GSM side, set GLDSSSw(BSC6900,BSC6910) to ON(On). After

Issue 03 (2016-06-30) Huawei Proprietary and Confidential 10

3.1 GSM Dedicated Carriers and Shared Carriers

1. Calculate the FDL using the following formula:

If the frequency corresponding to a GSM ARFCN on a carrier partially or completely falls

Table 3-1 E-UTRA operating bands

FDL_low NOffs-DL Range of NDL

2 1930 600 600 – 1199

3 1805 1200 1200 – 1949

4 2110 1950 1950 – 2399

5 869 2400 2400 – 2649

6 875 2650 2650 – 2749