GBSS Feature Documentation GBSS21.1 - 08 20210309221351

Handover Re-establishment
Contents
3.6.19 Handover Re-establishment
3.6.21 Radio Resource Management
3.6.24 Dynamic Channel Conversion
3.6.25 Channel Management
3.6.27 Enhanced Measurement Report (EMR)
3.6.28 Assignment and Immediate Assignment
GSM BSS
GBSS18.1
Handover Re-establishment Feature

Parameter Description
Issue 01
Date 2016-02-29
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2020. 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: https:/
Email: support@huawei.com
3.6.19 Contents
1 About This Document
1.1 Scope
1.2 General Statements
1.3 Change History
2 Overview
2.1 Introduction
2.2 NEs Supporting the Feature
3 Technical Description
3.1 Implementation in the BSS
3.2 Impact on the KPI
4 Engineering Guidelines
4.1 Deployment Requirements
4.2 Activation
4.3 Activation Observation
4.4 Deactivation
5 Parameters
6 Counters
7 Glossary
8 Reference Documents
1.1 Scope
This document describes GBFD-510502 Handover Re-establishment, including its technical

principles, related features, network impact, and engineering guidelines.
Purpose
Feature Parameter Description documents are intended to acquaint readers with:

 The technical principles of features and their related parameters
 The scenarios where these features are used, the benefits they provide, and the impact
they have on networks and functions
 Requirements of the operating environment that must be met before feature activation
 Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
This document only provides guidance for feature activation. Feature deployment and feature gains depend
on the specifics of the network scenario where the feature is deployed. To achieve the desired gains, contact
Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in Feature Parameter
Description documents apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.
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:
 Feature change
Changes in features of a specific product version
 Editorial change
Changes in wording or addition of information that was not described in the earlier version
01 (2016-02-29)
This issue does not include any changes.

Draft A (2015-12-31)
Compared with Issue 01 (2013-05-06) of GBSS15.0, Draft A (2015-12-31) of GBSS18.1

includes the following changes.
Change Type Change Description Parameter Change
Feature change Added the Added the

MaxLinkReestabInHO MaxLinkReestabInHO
(BSC6900, BSC6910) parameter (BSC6900, BSC6910)
to specify the maximum parameter.
number of L2 link re-
establishments that can be
initiated when an L2 link
becomes faulty during a
handover.
Modified the following
chapters accordingly:
 3 Technical Description
 4 Engineering Guidelines
 5 Parameters
Editorial change None None
2 Overview
2.1 Introduction
In a general handover procedure, if the BSC receives an Error Indication message from the
BTS instead of a response from an MS after sending the Handover Command to the MS, the
BSC determines that a call drop occurs and then initiates the release procedure. With the
Handover Re-establishment feature enabled, the BSC initiates a procedure for re-establishing
a connection at the data link layer of the Um interface on the original channel. If the
connection re-establishment is successful, the MS continues the call without a call drop.
Handover Re-establishment reduces the call drop rate during handover, improving user
satisfaction and network KPIs.
Handover Re-establishment does not support directed retry.
Table 2-1 NEs supporting the feature

Feature BSC6900 BSC6910 GBTS eGBTS
Handover Re- √ √ √ √
establishment
√ indicates that the NE supports this feature. × indicates that the NE does not support this feature.
The implementation of Handover Re-establishment in the base station subsystem (BSS) is as

follows:
1. If ACTL2REEST (BSC6900, BSC6910) is set to YES(Yes) and the BTS TRXs support
Handover Re-establishment, the BSC can enable Handover Re-establishment.
2. The HOL2REBUILDTIMES (BSC6900, BSC6910) and MaxLinkReestabInHO
(BSC6900, BSC6910) parameters are used to configure the number of L2 link re-
establishments during a handover.
3. After receiving the Error Indication message, the BSC determines the phase at which
the call is being processed.
When the call is waiting for intra-cell handover completion or inter-cell handover
completion, the BSC sends the Establish Request message on the original channel,
requesting the BTS to re-establish the connection at the data link layer of the Um
interface.
4. After receiving the Establish Request message, the BTS initiates a procedure for re-
establishing the connection at the data link layer of the Um interface.
5. The MS cooperates with the BTS to re-establish the connection at the data link layer
of the Um interface.
6. The call is re-assigned to the original channel, and the call continues.
Figure 3-1 shows the signaling procedure of Handover Re-establishment.
Figure 3-1 Signaling procedure of Handover Re-establishment
3.2 Impact on the KPI
Enabling Handover Re-establishment may reduce the call drop rate during handover. The
larger the value of the MaxLinkReestabInHO (BSC6900, BSC6910) parameter, the more
significantly the call drop rate decreases. As a result, TCH congestion deteriorates.
Table 4-1 Deployment requirements
Aspect Requirement
Related features None
BSC None
BTS BTS3900B/E not support Handover Re-establishment

feature.
GSM networking None
MS None
MSC None
License The license controlling this feature has been activated. For
details on how to activate the license, see License Management
Feature Parameter Description. For details about license items,
see License Control Item Description.
Aspect Requirement
Others The cell with this feature enabled has been configured with
available neighboring cells.
4.2 Activation
Using MML Commands
On the BSC LMT, perform the following steps:

1. Run the SET GCELLSOFT command with Activate L2 Re-establishment set to
YES(Yes).
2. Run the SET BSCEXSOFTPARA command with Allowed Layer 2 Rebuild Times
in Handover set to REPETITIOUS(Repetitious Times) and Maximum Number of L2
Reestablishments in HO set to 2.
MML Command Examples
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, ACTL2REEST=YES;

SET BSCEXSOFTPARA: HOL2REBUILDTIMES=REPETITIOUS,
MAXLINKREESTABINHO=2;
Using the CME
For detailed operations, see CME-based Feature Configuration.

1. Configure cell 0 and cell 1 as neighboring cells. The two cells are in the same
frequency band and work properly.
2. On the BSC LMT, trace RSL messages over the Abis interface for cell 0.
3. On the BSC LMT, run the MOD G2GNCELL command with its parameters set as
follows:
 Set Better Cell HO Watch Time to 1.
 Set Better Cell HO Valid Time to 1.
 Set PBGT HO Threshold to 64.
4. Run the SET GCELLHOBASIC command with Current HO Control Algorithm
set to HOALGORITHM2(Handover algorithm II).
5. Run the SET GCELLCCTMR command with its parameters set as follows:
 Set Use LAPDm N200 to ON(On).
 Set T200 FACCH/F to 5.
 Set T200 FACCH/H to 5.
 Set N200 of FACCH/Half Rate to 30.
 Set N200 of FACCH/Full Rate to 34.
6. Use an MS to make a call in cell 0.
7. Rapidly attenuate the signals of cell 0 and initiate a better cell handover from cell 0 to
cell 1.
The BSC sends a Handover Command message to an MS in cell 0, but the MS does not
receive the Handover Command message correctly. In this case, the BSC receives an
Error Indication message from cell 0.
8. Increase the signals of cell 0.
The BSC starts to retransmit handover data and sends an Establishment Request message
to cell 0.
9. Check the result for RSL message tracing over the Abis interface for cell 0.
Expected result: The call is still properly held in cell 0. Handover Command, Error
Indication, Establish Request, and Establish Confirm messages are traced over the Abis
interface for cell 0.
4.4 Deactivation
Using MML Commands
On the BSC LMT, run the SET GCELLSOFT command with Activate L2 Re-
establishment set to NO(No).
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, ACTL2REEST=NO;
Using the CME
5 Parameters
The following hyperlinked EXCEL files of parameter reference match the software version
with which this document is released.
Base station controller parameter reference
 BSC6900 GSM Parameter Reference: contains the parameters related to the BSC6900
equipment, transport, and radio access functions.
eGBTS Parameter reference
 Node Parameter Reference: contains base station equipment and transport parameters.
 GBTSFunction Parameter Reference:
contains all parameters related to radio access
functions, including air interface management, access control, mobility control, and radio
resource management.
You can find the EXCEL files of parameter reference for the software version on the live network from the
product documentation delivered with that version.
FAQ: How do I find the parameters related to a certain feature from parameter
reference?
Step 1: Open the EXCEL file of parameter reference.
Step 2: On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, GBFD-200201.
Step 3: Click OK. All parameters related to the feature are displayed.
6 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
Base station controller performance counter reference
 BSC6900 GSM Performance Counter Reference: contains the counters related to the
BSC6900 equipment, transport, and radio access functions.
 BSC6910 GSM Performance Counter Reference:
contains the counters related to the
eGBTS performance counter reference
 Node Performance Counter Summary: contains base station equipment and transport
counters.
 GBTSFunction Performance Counter Summary:
contains all counters related to radio access
You can find the EXCEL files of performance counter reference for the software version used on the live
network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from performance counter
reference?
Step 1: Open the EXCEL file of performance counter reference.
Step 2: On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, GBFD-200201.
Step 3: Click OK. All counters related to the feature are displayed.
7 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
None.
GSM BSS
GBSS21.1
Radio Resource Managem

Feature Parameter
Description
Issue 01
Date 2019-06-06

Notice
Huawei Industrial Base Bantian, Longgang

Address:
Shenzhen 518129 People's Republic of China
Website: https:/
3.6.21 Contents
1.1 Scope
1.3 Change History
2 NEs Supporting the Feature
3 TRX Management
3.1 Overview
3.2 Technical Description
3.2.1 Radio Resource Indication
3.2.2 SACCH Filling Information Modify
3.2.3 Flow Control
3.2.4 Error Reporting
4 Radio Link Management

4.1 Overview
4.2.1 Link Establishment Indication
4.2.2 Link Establishment Request
4.2.3 Link Release Indication
4.2.4 NeLink Release RequestwNode
4.2.5 Transmission of a Transparent L3-Message in Acknowledged Mode
4.2.6 Reception of a Transparent L3-Message in Acknowledged Mode
4.2.7 Transmission of a Transparent L3-Message in Unacknowledged Mode
4.2.8 Reception of a Transparent L3-Message in Unacknowledged Mode
4.2.9 Link Error Indication
5 Radio Common Channel Management

5.1 Overview
5.2.1 Channel Request by MS
5.2.2 Paging
5.2.3 Delete Indication
5.2.4 CCCH Load Indication
5.2.5 Broadcast Information Modify
5.2.6 Short Message Cell Broadcast
5.2.7 Immediate Assignment
5.2.8 Notification
6 Radio Dedicated Channel Management

6.1 Overview
6.2.1 Channel Activation
6.2.2 Handover Detection
6.2.3 Start of Encryption
6.2.4 Measurement Reporting
6.2.5 SACCH Deactivation
6.2.6 Radio Channel Release
6.2.7 MS Power Control
6.2.8 Transmission Power Control
6.2.9 Connection Failure
6.2.10 SACCH Information Modify
6.2.11 Talker Detection
6.2.12 Listener Detection
7.1 TRX Management
7.2 Radio Link Management
7.2.1 Deploying Radio Link Management
7.2.1.1 Deployment Requirements
7.2.1.2 Activation
7.2.1.3 Activation Observation
7.2.1.4 Deactivation
7.3 Radio Common Channel Management
7.4 Radio Dedicated Channel Management
7.4.1 Pre-processed Measurement Reporting
7.4.2 Channel Mode Modify
7.5 Multiple CCCHs
7.5.1 Deploying Multiple CCCHs
7.5.1.2 Activation
7.6 Performance Monitoring
8 Parameters
9 Counters
10 Glossary
1.1 Scope
This document describes Radio Resource Management, including its technical principles and
engineering guidelines.
This document covers the following features:
 GBFD-111001 TRX Management
 GBFD-111002 Radio Link Management
 GBFD-111003 Radio Common Channel Management
 GBFD-111004 Radio Dedicated Channel Management
 GBFD-511501 Multiple CCCHs
Purpose

Software Interfaces
1.3 Change History
 Feature change
01 (2019-06-06)
Draft A (2018-12-30)

Feature Added independent configuration of TSC Added the following

change correction thresholds for handover access parameters:
so that TSC correction thresholds can be  HOAccErrThldOptS
separately configured for random access w (BSC6900, BSC6910)
and handover access (controlled through a
 HOAccErrThld
switch). For details, 5.2.1 Channel Request by
(BSC6900, BSC6910)
MS.
 CSRACHMinAccLev
CtrlSw (BSC6900,
BSC6910)
 CSRACHMinAccLev
MOC (BSC6900, BSC6910)
 CSRACHMinAccLev
MTC (BSC6900, BSC6910)
 CSRACHMinAccLev
Other (BSC6900, BSC6910)
Editorial None None

change
2 NEs Supporting the Feature
TRX √ √ √ √
Management
Radio Link √ √ √ √
Management
Radio Common √ √ √ √
Channel
Management
Radio Dedicated √ √ √ √
Channel
Management
Multiple CCCHs √ √ √ √
3 TRX Management
3.1 Overview
This section describes the GBFD-111001 TRX Management feature.

TRX Management consists of the following procedures:
 Radio resource indication: used to inform the BSC of the interference levels on idle
channels of a TRX.
 SACCH filling information modify: used by the BSC to indicate to the BTS the new
information to be used as filling information on slow associated control channels
(SACCHs).
 Flow control: used to prevent common control channel (CCCH) overload, associated
control channel (ACCH) overload, and processor overload.
 Error reporting: used by the BTS to report detected errors if they cannot be reported
by any other procedure.
3.2.1 Radio Resource Indication
This procedure is used to inform the BSC of the interference levels on idle channels of a
TRX.
Interference signals are classified into five interference levels according to strength. The TRX
determines the current interference level based on the average interference signal level and
the interference band threshold of each interference level. In the RF Resource Indication
message, TRX reports the interference level for each of the channels which have been idle
(not active) for the whole measurement period.
The interval at which the RF Resource Indication message is sent and the interference band
threshold of each interference level are set by operation and maintenance (O&M) personnel.
3.2.2 SACCH Filling Information Modify
This procedure is used by the BSC to indicate to the BTS the new information to be used as
filling information on SACCHs.
The BSC sends a SACCH FILLING message to the BTS. This message contains the new
broadcast information to be used as filling information on downlink SACCHs.
3.2.3 Flow Control
This procedure is used by the BTS to send the BSC an OVERLOAD message with the
following possible cause values:
 CCCH overload
 ACCH overload
 Processor overload
Flow control protects the TRX processor, downlink CCCH, and ACCH from being
overloaded.
The OVERLOADINTV (BSC6900, BSC6910) parameter specifies the interval at which the
BTS transmits OVERLOAD messages to the BSC. This parameter is used to control the
frequency for sending OVERLOAD messages over channels and on TRXs.
3.2.4 Error Reporting
This procedure is used by the BTS to report detected errors if they cannot be reported by any
other procedure. The involved messages are as follows:
 CHANNEL ACTIVATION NACK in the case of channel activation
 MODE MODIFY NACK in the case of channel mode change
 ERROR REPORT in other cases
When the TRX detects the reception of an erroneous message, it sends an ERROR REPORT
message to BSC with the most appropriate cause value. A complete ERROR REPORT
message, such as CHANNEL ACTIVATION NACK+CHANNEL ACTIVATION, must
include the Message Type, Channel Number, and Link Identifier for message type
identification.
4 Radio Link Management
4.1 Overview
This chapter describes the GBFD-111002 Radio Link Management feature.

Radio link management consists of the following procedures:
 Link establishment indication
 Link establishment request
 Link release indication
 Link release request
 Transmission of a transparent L3-message in acknowledged mode
 Reception of a transparent L3-message in acknowledged mode
 Transmission of a transparent L3-message in unacknowledged mode
 Reception of a transparent L3-message in unacknowledged mode
 Link error indication
4.2.1 Link Establishment Indication
This procedure is used by the BTS to indicate to the BSC that an L2 link on the radio path has
been established in multi-frame mode at the initiative of an MS. The BSC can use this
indication to set up an SCCP connection to the MSC.
Upon reception of a SABM frame on a link on an active channel, the BTS sends an
ESTABLISH INDICATION message to the BSC. The message contains the contents of the
information field of the SABM frame if present.
The procedure is used in all establishment cases, for all channels and all SAPIs.
4.2.2 Link Establishment Request
This procedure is used by the BSC to request the establishment of a link layer connection in
multi-frame mode on the radio path.
The procedure is started by the BSC sending an ESTABLISH REQUEST message to the
BTS. The BTS then establishes the link by sending an SABM frame. Upon reception of the
acknowledgement (UA-frame) from the MS, the BTS sends an ESTABLISH CONFIRM
message to the BSC.
In case of a failure, the BTS sends a RELEASE INDICATION and an ERROR
INDICATION message to the BSC (see GSM 04.06).
4.2.3 Link Release Indication
This procedure is used by the BTS to indicate to the BSC that a link layer connection on the
radio path has been released at the initiative of an MS.
When receiving a DISC frame on a link layer connection in multi-frame mode, the BTS sends
a RELEASE INDICATION message to the BSC. If the link layer is in idle mode, the BTS
sends a DM frame to the MS but does not notify the BSC.
Collision cases are treated as specified in GSM 04.06.
4.2.4 NeLink Release RequestwNode
This procedure is used by the BSC to request the release of a link layer connection on the
radio path.
The procedure is started by the BSC sending a RELEASE REQUEST message to the BTS.
The BTS then sends a DISC frame to the MS. When it has received the acknowledgement
(UA or DM frame), the BTS sends a RELEASE CONFIRM message to the BSC.
Collision cases are treated as specified in GSM 04.06.
If the BTS has repeated the DISC frame N200 times, the BTS sends a RELEASE
INDICATION and an ERROR INDICATION message to the BSC (see GSM 04.06).
4.2.5 Transmission of a Transparent L3-Message in Acknowledged Mode
This procedure is used by the BSC to request the sending of an L3 message to the MS in
acknowledged mode.
The BSC sends a DATA REQUEST message to the BTS. The message contains the complete
L3 message to be sent in acknowledged mode.
4.2.6 Reception of a Transparent L3-Message in Acknowledged Mode
This procedure is used by the BTS to indicate the reception of an L3 message in

acknowledged mode.
The BTS sends a DATA INDICATION message to the BSC. The message contains the
received L3 message.
4.2.7 Transmission of a Transparent L3-Message in Unacknowledged Mode
This procedure is used by the BSC to request the sending of an L3 message to the MS in
unacknowledged mode.
The BSC sends a UNIT DATA REQUEST message to the BTS. The message contains the L3
message to be sent to the MS in unacknowledged mode.
4.2.8 Reception of a Transparent L3-Message in Unacknowledged Mode
This procedure is used by the BTS to indicate the reception of an L3 message in

unacknowledged mode.
The BTS sends a UNIT DATA INDICATION message to the BSC. The message contains
the received L3 message.
4.2.9 Link Error Indication
This procedure is used by the BTS to indicate an abnormal case, such as those described
below:
 A protocol error as specified in GSM 04.06, subclauses 5.6.4, 5.7.3, and annex G
 A link layer failure: that is, the repetition of an I-frame N200 times without an
acknowledgement
 Repetition of an SABM or DISC frame N200 times without an acknowledgement
 Reception of an SABM frame in multi-frame established state
When such an event occurs, the BTS notifies the BSC by sending an ERROR INDICATION
message containing the relevant cause information.
The principles for reporting an ERROR INDICATION message are as follows:

1. The N(R) in the I or S frame received by LAPDm must meet the following
requirement: V(A)=<N(R)=<V(S). Otherwise, the frame sequence is considered
erroneous. In this case, an ERROR INDICATION message is reported with the cause
value "sequence error (0x07)."
2. If the DM frame received by the BTS is not the expected one, the BTS reports an
ERROR INDICATION message with the cause value "unsolicited DM response (0x04)."
3. If the BTS does not receive a response message from the MS after transmitting the I
frame several times (specified by the parameter N200 (BSC6900, BSC6910)), the BTS
reports an ERROR INDICATION message with the cause value "RLM Cause: 1 timer
T200 expired (N200+1) times (0x01)." Using the full-rate TCH as an example, the
default time is T200 x (N200 + 1) = 5 x 50 x (34 + 1) = 8,750 ms.
The T200 (BSC6900, BSC6910) and N200 (BSC6900, BSC6910) parameters can be set on the
LMT. Based on the function and state of links, different parameters must be configured.
The involved parameters are as follows:
 T200SDCCH (BSC6900, BSC6910)
 T200FACCHF (BSC6900, BSC6910)
 T200FACCHH (BSC6900, BSC6910)
 T200SACCT0 (BSC6900, BSC6910)
 T200SACCH3 (BSC6900, BSC6910)
 T200SACCHS (BSC6900, BSC6910)
 T200SDCCH3 (BSC6900, BSC6910)
 N200PARASWITCH (BSC6900, BSC6910)
 N200ESTAB (BSC6900, BSC6910)
 N200REL (BSC6900, BSC6910)
 N200SACCH (BSC6900, BSC6910)
 N200SDCCH (BSC6900, BSC6910)
 N200FHALF (BSC6900, BSC6910)
 N200FFULL (BSC6900, BSC6910)
5 Radio Common Channel Management
5.1 Overview
This chapter describes how to manage the PCH, RACH, AGCH, NCH, PPCH, PRACH, and
PAGCH. Radio common channel management is a basic feature for operators to provide CS
speech services.
 Common control channels
Common control channels include the PCH, RACH, AGCH, NCH, PPCH, PRACH, and
PAGCH. To specify the channel type, set the CHTYPE (BSC6900, BSC6910) parameter.
 Paging Channel (PCH): Downlink channel. The MS listens to the PCH at
intervals to determine whether there is a call request from the MSC.
 Random Access Channel (RACH): Uplink channel. The MS accesses the
network through the RACH and requests the network to assign an SDCCH.
 Access Grant Channel (AGCH): Downlink channel. The network informs the
MS of the assigned dedicated channel (SDCCH or TCH) through the AGCH.
 Notification Channel (NCH): Downlink channel. Used for voice group call
service (VGCS) and voice broadcast service (VBS).
 Packet Paging Channel (PPCH): Downlink channel. The MS listens to the
PPCH at intervals to determine whether there is a packet request from the SGSN.
 Packet Random Access Channel (PRACH): Uplink channel. The MS requests
network access through the PRACH.
 Packet Access Grant Channel (PAGCH): Downlink channel. The network
informs the MS of the assigned packet data channel through the PAGCH.
 Radio common channel management
Radio common channel management includes the signaling procedures of MS access and
assignment and the resource management of the common channel. The involved
procedures are Channel Request by MS, Paging, Delete Indication, CCCH Load
Indication, Broadcast Information Modify, Short Message Cell Broadcast, Immediate
Assignment, and Notification.
5.2.1 Channel Request by MS
This procedure is initiated by a TRX upon detection of a random access from an MS

(CHANNEL REQUEST message from MS). The TRX then sends a CHANNEL REQUIRED
message to the BSC containing the Request Reference parameter (random number selected
by the MS plus some low order bits of the TDMA frame number for the access) and the
measured delay of the Access Burst.
To reduce the number of access conflicts on RACHs during MS access and to increase the
RACH utilization, set the following parameters to appropriate values:
TX (BSC6900, BSC6910)
MSMAXRETRAN (BSC6900, BSC6910)
RACHBUSYTHRED (BSC6900, BSC6910)
RANERRTHRED (BSC6900, BSC6910)
RACHACCLEV (BSC6900, BSC6910)
PSRACHACCLEV (BSC6900, BSC6910)
CSRACHMinAccLevCtrlSw (BSC6900, BSC6910)
CSRACHMinAccLevMOC (BSC6900, BSC6910)
CSRACHMinAccLevMTC (BSC6900, BSC6910)
CSRACHMinAccLevOther (BSC6900, BSC6910)
The PWRDIVIND (BSC6900, BSC6910) parameter specifies whether the power offset is added
to the class 3 MS on the DCS1800 frequency band on the basis of the maximum MS transmit
power if the MS does not receive the initial power command after random access. The
PWRDIV (BSC6900, BSC6910) parameter specifies the power offset to be added.
The FMSMAXOPCC (BSC6900, BSC6910) parameter specifies the maximum MS transmit
power.
5.2.2 Paging
This procedure is used to request the paging of one MS on a given paging subchannel.
The paging of an MS is initiated by the BSC sending a PAGING COMMAND message to
the BTS. The message contains the MS identity (TMSI or IMSI) and the paging population
number of the MS. The message may indicate to the MS which combination of channels will
be needed for the subsequent paging transaction. The message may also indicate the eMLPP
priority of the call.
The PAGING REQUEST messages to be sent on the radio path are built and sent by the BTS.
The BSAGBLKSRES (BSC6900, BSC6910) parameter determines the CCCH usage for the
AGCH and PCH and therefore affects system performance and the paging response time of
MSs. BSPAMFRAMS (BSC6900, BSC6910) determines the paging response delay and the
MS power consumption. The paging success rate can be improved by setting PAGTIMES
(BSC6900, BSC6910).
Of these logical channels, the PCH, AGCH, NCH, and RACH are called CCCHs.
One cell is typically configured with one BCCH physical channel, which is configured on
timeslot 0 of the BCCH TRX. In the GBFD-511501 Multiple CCCHs feature, timeslots 2, 4,
and 6 of the BCCH TRX can be configured as BCCH physical channels. These BCCH
physical channels can be divided into the BCCH, PCH, and AGCH in the downlink, and the
RACH in the uplink. Messages sent on the BCCH logical channel are the same regardless of
whether they are sent on timeslot 0, 2, 4, or 6. Messages sent on the PCH, AGCH, and
RACH, however, can be different on timeslots 0, 2, 4, and 6. Therefore, more messages can
be sent on the PCH, AGCH, and RACH. Configuring multiple BCCH physical channels
expands the CCCH capacity.
The BSC broadcasts the configured number of CCCHs to the MS in system information type
3 messages. The MS determines on which timeslot to monitor the paging message based on
its IMSI.
Configuring multiple CCCHs increases the number of RACHs in the cell because uplink
BCCH physical channels are all RACHs. Therefore, the GBFD-511501 Multiple CCCHs
feature also improves the random access capability of the cell.
5.2.3 Delete Indication
This procedure is used by the BTS to indicate that an IMMEDIATE ASSIGN COMMAND
has been deleted due to overload on the downlink CCCH.
The BTS sends a DELETE INDICATION message to the BSC.
5.2.4 CCCH Load Indication
This procedure is used by a BTS to inform the BSC of the load on a particular CCCH
timeslot.
If the CCCH load exceeds the value of CCCHLOADTHRES (BSC6900, BSC6910), the BTS
sends CCCH LOAD INDICATION messages to the BSC at an interval specified by
CCCHLOADINDPRD (BSC6900, BSC6910) on the PCH and by RACHLDAVERSLOT
(BSC6900, BSC6910) on the RACH.
The RACHLOADALM (BSC6900, BSC6910), RACHLOADALMCNT (BSC6900, BSC6910),

and RACHLOADRSTCNT (BSC6900, BSC6910) parameters jointly control whether to report
ALM-21817 Cell RACH Congestion.
The PAGINGOVERRPTTHRD (BSC6900, BSC6910) and PCHForbidRptLoadSw
(BSC6900, BSC6910, eGBTS) parameters jointly control whether the BTS sends to the BSC the
CCCH LOAD INDICATION message indicating the PCH overload.
When the PagingOvldProcOptSw (BSC6900, BSC6910) parameter is set to ON(On), if
congestion occurs because of PS paging, the BTS reports PACKET CCCH OVLOAD IND
message but does not perform flow control on CS services.
5.2.5 Broadcast Information Modify
This procedure is used by the BSC to indicate new information to be broadcast on BCCH to
the BTS.
The BSC sends a BCCH INFORMATION message to the BTS.
5.2.6 Short Message Cell Broadcast

Short Message Service Cell Broadcast messages are sent to the BTS as SMS BROADCAST
COMMAND messages.
With the SMS BROADCAST COMMAND mode of operation, the BSC can request the
broadcast of a complete Cell Broadcast message. The BSC handles the queuing, repetition,
and transmission of the messages, taking the capacity of the CBCHs (basic and extended
channel [see 3GPP TS 45.002]) into account. The BSC is responsible for the segmentation of
the SMS Cell Broadcast messages on the Radio interface:
5.2.7 Immediate Assignment
This procedure is used by the BSC to request the transmission of an IMMEDIATE ASSIGN
Message on a downlink CCCH. To initiate the immediate assignment, the BSC sends an
IMMEDIATE ASSIGN COMMAND message. The message contains the complete
immediate assignment message as defined in 3GPP TS 44.018 (IMMEDIATE
ASSIGNMENT or IMMEDIATE ASSIGNMENT REJECT) with the "Page Mode" element
set to the value "no change."
The IMMEDIATE ASSIGNMENT message can be sent not only on its own scheduling
occasion but also on the sending occasion of paging messages. The
IMMOccupyPCHOptSw (BSC6900, BSC6910, eGBTS) and IMMOccupyPCHDelay
(BSC6900, BSC6910, eGBTS) parameters are configured to balance the immediate assignment
success rate and number of paging overloads.
The IMMEDIATE ASSIGNMENT REJECT message is either sent by the BTS as received in
the IMMEDIATE ASSIGN COMMAND message or built by the BTS from the contents of
two or more IMMEDIATE ASSIGN COMMAND messages. In the latter case, the BTS may
consider request references with identical contents within the same message as duplicates and
all but one may be suppressed.
5.2.8 Notification
This procedure is used to request that notification be performed by the BTS. The BSC
indicates the exact action required by the BTS in the command indicator.
The NOTIFICATION messages to be sent on the radio path are built and sent by the BTS.
The BSC manages the NCH DRX information, whereas the BTS manages the scheduling of
the messages on the NCH.
If the BTS cannot perform the notification commanded by the BSC, the BTS returns an
ERROR REPORT message with the relevant cause value.
6 Radio Dedicated Channel Management
6.1 Overview
This chapter describes the GBFD-111004 Radio Dedicated Channel Management feature.
Radio dedicated channel management involves the assignment, activation, release,
management, and reporting of dedicated channels, such as the SDCCH, SACCH, and TCH.
These procedures work together to establish, maintain, and release radio links.
The involved procedures are as follows:

 Channel activation: The BSC instructs the BTS to activate a dedicated channel for an
MS. After this channel is activated, the BSC assigns this channel to the MS through an
Immediate Assign, Assign Command, Channel Release (with a channel description), or
Handover Command message.
 Channel mode modify: The BSC instructs the BTS to change the mode of an activated
channel.
 Handover detection: Used between the target BTS and the target BSC to detect the
access of the MS that is handed over.
 Start of encryption: Initiates the encryption procedure specified by TS GSM 04.08.
 Measurement reporting: The BTS reports all the parameters related to handover
decision to the BSC. This procedure consists of the mandatory basic measurement
reporting procedure and the optional measurement reporting procedure with pre-
processing.
 SACCH deactivation: The BSC deactivates the related SACCH of a TRX according
to the requirements of the channel release procedure specified by 3GPP TS 44.018.
 Radio channel release: The BSC instructs the BTS to release a radio channel that is
not in use.
 MS power control: The BSS controls the transmit power of the MS that uses an
activated channel. The MS power control decision must be implemented on the BSC and
can also be implemented on the BTS.
 Transmission power control: The BSS controls the transmit power of the activated
channel on the TRX. Transmission power control must be implemented on the BSC and
can also be implemented on the BTS.
 Connection failure: The BTS informs the BSC that an activated dedicated channel has
been disconnected.
 SACCH information modify: The BSC instructs the BTS to change the filling
information (system information) on an SACCH.
 Talker detection: Upon receiving the Talker uplink access message from the MS on
the idle uplink VGCS channel during a VGCS call, the BTS generates a VGCS UPLINK
GRANT message on the activated dedicated channel and reports the detected MS access
delay to the BSC.
 Listener detection: When there is no listener in the cell, the dedicated radio downlink
channel allocated to the VGCS/VBS must be released in time to improve the resource
utilization. The BSC periodically broadcasts the uplink free message in the cell. After all
the listeners receive this message, a Talker uplink access message is sent to the BTS on the
idle uplink VGCS channel. The BTS generates a VGCS UPLINK GRANT message and
sends this message to the BSC over the activated dedicated channel. In addition, the BTS
sends a listener detection message to the BSC, informing the BSC of the MS access delay.
6.2.1 Channel Activation
This procedure is used to activate a channel at the BTS for an MS which later will be
commanded to this channel by an IMMEDIATE ASSIGN, ASSIGNMENT COMMAND,
NOTIFICATION, CHANNEL RELEASE (with a Channel description), or HANDOVER
COMMAND message.
In the handover case, the procedure is used between the target BSC and the target BTS to
activate a channel for a subsequent handover from the old BTS.
Signaling Procedure
The BSC determines what channel will be used and starts up that channel at the BTS by
sending a CHANNEL ACTIVATION message to the relevant TRX. This message contains
the reason for the activation (immediate assignment, assignment, asynchronous/synchronous
handover), the identification of the channel to be used (channel No.), and a complete
description of the channel (for example, full/half rate, speech/data, coding/rate adaption,
hopping sequence, and encryption key).
If the Encryption Information field is present, the activation is done with ciphering active. If
the Encryption information element is not present, activation is done without ciphering.
After activating the channel, the TRX responds with the CHANNEL ACTIVATION
ACKNOWLEDGE message. This message contains the current frame number at the BTS.
The frame number is used by the BSC to determine the Starting Time parameter to be
included in the subsequent assignment message to the MS. (A suitable number has to be
added to the current frame number to take all possible signaling delays into account).
If the TRX cannot activate the resource as requested by the CHANNEL ACTIVATION
message, the TRX will return a CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE
message with the most appropriate cause value.
Possible cause values may be:
 O&M intervention (for example, channel blocked)
 Resource not available (for example, speech coder, encryption device)
 Equipment failure
 Channel already activated
In the handover case, the procedure is initiated by the target BSC when the BSC receives
the HANDOVER REQUEST message from the MSC (or autonomously by the BSC for
BSC internal handover). The BSC sends a CHANNEL ACTIVATION message to the
relevant TRX. The message contains the Handover Reference value, which can be used by
the BTS to check the Handover Access from the MS. After activation of the channel, the
TRX responds with a CHANNEL ACTIVATION ACKNOWLEDGE message containing
the current frame number at the BTS.
The BSC can then determine the Starting Time parameter to be included in the
HANDOVER REQUEST ACKNOWLEDGE message to the MSC (and the HANDOVER
COMMAND message to the MS).
Activation for Intra-Cell Channel Change
This activation precedes the Immediate Assignment and Assignment procedures. The Timing
Advance element must be included in the CHANNEL ACTIVATION message.
The BTS activates the channel and starts transmission and reception on the main channel in
the indicated mode. Ciphering is started if so indicated in the encryption information.
The reception and transmission on SACCH is also started immediately.
If the BS and/or MS Power elements and/or the Physical Context element are present, the
reception and transmission processes and the L1-header of SACCH are initialized
accordingly.
Activation for Asynchronous Handover
The BTS starts transmission immediately on the main channel in the indicated mode and with
encryption if so indicated. If only the MS Power element is present, the BTS may also start
transmission on the SACCH.
When receiving a correct access burst with the correct handover reference, the BTS starts the
normal reception process on the main channel in the indicated mode and starts receiving (and
sending if not started earlier) on the SACCH. Deciphering is started if so indicated. The
handover detection procedure towards the BSC is also started.
Activation for Synchronous Handover
The BTS starts transmission immediately on the main channel in the indicated mode and with
encryption if so indicated. If the MS Power and Timing Advance element are present, the
BTS needs to also start transmission on SACCH with the timing advance and MS power
control parameters indicated. If only the MS Power element is present, the BTS may also
start transmission on the SACCH.
When receiving a correct access burst with the correct handover reference, the BTS starts the
normal reception process on the main channel in the indicated mode, with deciphering
applied if so indicated, and starts receiving (and sending, if not started earlier) on SACCH.
The handover detection procedure towards the BSC is also started. Alternatively, the
reception of a correctly decoded frame from the MS on the main channel, in the indicated
mode and with deciphering applied if so indicated, allows the start of sending on SACCH (if
not already started) and starts the handover detection procedure towards the BSC.
The activation for synchronous handover can be used for pseudo synchronized handover.
Channel Mode Modify
This procedure is used by the BSC to request a change of the channel mode and/or a change
between uni-directional and bi-directional channel types of an active channel.
The BSC initiates the procedure by sending a MODE MODIFY message to the BTS. The
message contains the new mode to be used. After having changed to the new mode, the BTS
responds with a MODE MODIFY ACKNOWLEDGE message to the BSC.
If the TRX cannot modify the channel as requested in the MODE MODIFY message, the
TRX will return a MODE MODIFY NEGATIVE ACKNOWLEDGE message with the most
appropriate cause value.
6.2.2 Handover Detection
This procedure is used between the target BTS and BSC when a handed over MS accesses the
new BTS.
The procedure is initiated by the BTS upon detection of an MS on a channel activated for
handover.
In case of an asynchronous handover, the BTS builds the PHYSICAL INFORMATION
message as specified in 3GPP TS 44.018, sends the message to the MS in unacknowledged
mode on the main signaling link, and starts timer T3105. A HANDOVER DETECTION
message is sent to the BSC. This message contains the measured delay of the access burst. If
the timer expires before the reception of a correctly decoded frame from the MS, the BTS
repeats the PHYSICAL INFORMATION message to the MS as specified in 3GPP TS
44.018. If the PHYSICAL INFORMATION message has been repeated Ny1 times without a
correctly decoded frame being received from the MS, the BTS needs to send a
CONNECTION FAILURE message to the BSC with the cause value "handover access
failure".
In case of a synchronous handover, the BTS only sends a HANDOVER DETECTION
message to the BSC (no PHYSICAL INFORMATION message sent to the MS). If the
handover detection is based on the detection of a handover access burst with the correct
handover reference, the measured delay of the access burst is included in the HANDOVER
DETECTION message.
6.2.3 Start of Encryption
This procedure is used to start encryption according to the procedure defined in 3GPP TS
44.018.
The procedure is initiated by the BSC upon reception of the CIPHER MODE COMMAND
message from the MSC (see 3GPP TS 48.008).
The BSC sends the ENCRYPTION COMMAND message to the relevant TRX and channel.
The message contains all information required to select and load the user data and encryption
device with the appropriate key as well as the complete Ciphering Mode Command message
to be sent to the MS.
Upon receipt of this message, the TRX sends the CIPHERING MODE COMMAND message
to the MS and starts deciphering. The start of deciphering and the sending of the
CIPHERING MODE COMMAND message to the MS must be done simultaneously.
When receiving the CIPHering MODe CoMmanD, the MS starts both deciphering and
enciphering and sends the CIPHERING MODE COMPLETE message.
The TRX starts enciphering upon reception of any correct L2 frame which is received after
the start of deciphering.
If the TRX cannot perform the enciphering as requested in the ENCRYPTION COMMAND,
the TRX will return an ERROR REPORT message, for example, with the cause value
"Encryption algorithm not implemented."
6.2.4 Measurement Reporting
These procedures are used to report to the BSC all parameters and measurement results
required by the BSC for handover requirement decision.
The MS measures downlink received signal level and quality from the serving cell and
received signal level from surrounding cells as defined in 3GPP TS 45.005 and 3GPP TS
45.008. The measurement results are reported in MEASUREMENT REPORT messages sent
in every SACCH block (every 480 ms).
The TRX measures the received signal level and the quality on the uplink of the current
channel. The averaging period is one SACCH block period (same as the basic period for the
MS).
These measurements made by the MS and the TRX form the basic raw data for the handover
algorithms in the BSC/MSC. The procedure to be used for this basic measurement reporting
is defined in sub-clause Basic Measurement Reporting.
The BTS and the BSC may optionally support some pre-processing in the BTS of these basic
measurements. The additional and optional procedures required to support this pre-processing
are defined in sub-clause Measurement Pre-processing.
Basic Measurement Reporting
This procedure is used by the BTS to report the results of the basic radio measurements made
by the MS and TRX according to 3GPP TS 45.008 and 3GPP TS 45.005.
The TRX reports all these measurements in MEASUREMENT RESULT messages to the
BSC.
If an uplink SACCH block does not contain a MEASUREMENT REPORT from the MS (for
example, when it sends a short message), only the uplink measurement results are included
with an indication that the MS measurements are missing.
Measurement Pre-processing
These procedures are included to support some pre-processing in the BTS of radio
measurement data. They may replace the basic procedure defined in sub-clause Basic
Measurement Reporting.
Pre-processing Configuration
This procedure is used by the BSC to modify the pre-processing parameters according to the
reported communication conditions (for example, degradation of the communication). This
procedure is enabled when the BTSMESRPTPREPROC (BSC6900, BSC6910) parameter is
set to BTS_Preprocessing.
In order to change the parameters, the BSC sends a PREPROCESS CONFIGURE message to
the BTS.
Pre-processed Measurement Reporting
This procedure is used by the BTS to report the results of measurement pre-processing.
To report the results, the BTS sends a PREPROCESSED MEASUREMENT RESULT
message to the BSC. The interval for reporting the results is specified by the
MRPREPROCFREQ (BSC6900, BSC6910) parameter.
6.2.5 SACCH Deactivation
This procedure is used by the BSC to deactivate the SACCH at the BTS according to the
Channel Release procedure defined in 3GPP TS 44.018.
When sending the CHANNEL RELEASE message to the MS, the BSC also sends the
DEACTIVATE SACCH message to the BTS to deactivate the SACCH.
6.2.6 Radio Channel Release
This procedure is used by the BSC to release a radio channel that is no longer needed.
When an activated radio channel is no longer needed, the BSC sends an RF CHANNEL
RELEASE message to the relevant TRX and channel. The BTS sends an RF CHANNEL
RELEASE ACKNOWLEDGE to the BSC after releasing the addressed resources.
6.2.7 MS Power Control
For details, see Power Control Feature Parameter Description.

6.2.8 Transmission Power Control
For details, see Power Control Feature Parameter Description.

6.2.9 Connection Failure
This procedure is used by the BTS to indicate to the BSC that an active connection has been
broken (for example, due to a radio link failure as defined in 3GPP TS 45.008).
When the BTS detects that a connection has been broken, the BTS sends a CONNECTION
FAILURE INDICATION message to the BSC with the most appropriate cause value.
Some possible cause values are:
 Radio link failure (as defined in 3GPP TS 45.008)
To check whether a radio link fault has occurred in the uplink or downlink, query the value of the
SAMULFRM (BSC6900, BSC6910) or RLT (BSC6900, BSC6910) parameter.
 Hardware failure (for example, transcoder failure)
Upon receiving a CONNECTION FAILURE INDICATION message from the BTS, the BSC
sends a CLEAR REQUEST message to the MSC, requesting the MSC to release the related
radio resources.
6.2.10 SACCH Information Modify
This procedure is used by the BSC to modify the SACCH filling information (System
Information) sent on an individual SACCH channel. For this purpose, the BSC sends a
SACCH INFO MODIFY message to the BTS. The SACCH filling information as given in
the SACCH INFO MODIFY message is used on the indicated channel until the channel is
released or the information is changed by another SACCH INFO MODIFY message.
6.2.11 Talker Detection
For details, see VGCS/VBS Feature Parameter Description.

6.2.12 Listener Detection
For details, see VGCS/VBS Feature Parameter Description.
7.1 TRX Management
The related parameters for the radio resource indication procedure must be configured on the
BSC.
You are advised to set the parameters as follows:
 Set RFRESINDPRD (BSC6900, BSC6910) to 10.
 Set INTERFTHRES0 (BSC6900, BSC6910) to 110.
The strength of the current interference is determined by the preset interference band
thresholds and is reported to the BSC. The BSC then compares the number of occupied
channels with the number of idle channels in the measurement report and the radio resource
indication to determine whether a handover is required. As a result, speech quality is ensured.
7.2 Radio Link Management
If T200 (BSC6900, BSC6910) is set to a small value, timer T200 expires before an
acknowledgement message is received from the peer end. In this case, the link is considered
faulty and data transmission fails.
If N200 (BSC6900, BSC6910) is set to a small value, the number of retransmissions is reduced
and the transmission success rate is reduced.
If T200 (BSC6900, BSC6910) and N200 (BSC6900, BSC6910) are set to large values, channels
are occupied when links are faulty. In this case, resources are wasted.
These parameters are set to default values on the Huawei BSC LMT and manual
configuration is generally not required.
7.2.1 Deploying Radio Link Management
None
7.2.1.2 Activation
Using MML Commands

On the BSC LMT, run the SET GCELLCCTMR command with the following parameters
set to appropriate values:
 T200 SDCCH
 T200 FACCH/F
 T200 FACCH/H
 T200 SACCH TCH SAPI0
 T200 SACCH TCH SAPI3
 T200 SACCH SDCCH
 T200 SDCCH SAPI3
 Use LAPDm N200
 N200 of Release
 N200 of Establish
 N200 of SACCH
 N200 of SDCCH
 N200 of FACCH/Half Rate
 N200 of FACCH/Full Rate
SET GCELLCCTMR: IDTYPE=BYID, CELLID=0, T200SDCCH=1, T200FACCHF=1,

T200FACCHH=1, T200SACCT0=1, T200SACCH3=1, T200SACCHS=1, T200SDCCH3=1;
Using the CME

1. On the BSC LMT, run the LST GCELLCCTMR command to query parameters
associated with the call control timer for a cell.
Expected result: The queried parameter values are the same as the values set in the
activation procedure.
2. On the BSC LMT, click Trace. The Abis Interface CS Trace dialog box is
displayed. On the Basic tab page, select RSL under Trace Type. On the RSL tab page,
select RLM under Message Type, select TRX from the Filter Flag dropdown list, and
specify the value of TRX ID.
3. Use an MS to initiate a call, and query the channel occupied by the call. Remove the
battery of the MS during the call.
4. On the BSC LMT, run the SET FHO command to initiate a forced handover on the
MS. In this step, set Handover Scope to FREE(Free).
5. Check the messages traced in step 2. Next, check whether the interval between the
DATA REQ message and the ERROR INDICATION message over the Abis interface is
consistent with the values of N200 and T200 set in the activation procedure. The DATA
REQ message contains the Handover command message, which is transmitted over the
Um interface.
Expected result: The interval between the messages for the full-rate channel equals to the
value of N200 of FACCH/Full Rate multiplied by the value of T200 FACCH/F. The
interval between the messages for the half-rate channel equals to the value of N200 of
FACCH/Half Rate multiplied by the value of T200 FACCH/H.
This feature does not need to be deactivated.

7.3 Radio Common Channel Management
None
7.4 Radio Dedicated Channel Management
The following radio channel management procedures are mandatory for the establishment,
maintenance, and release of radio links and are not controlled by parameters:
 Channel activation
 Channel mode modify
 Handover detection
 Start of encryption
 SACCH deactivation
 Radio channel release
 Connection failure
 SACCH information modify
For details about MS power control and transmission power control, see Power Control Feature
Parameter Description. For details about talker detection and listener detection, see VGCS/VBS
Feature Parameter Description.
7.4.1 Pre-processed Measurement Reporting
If the BTS preprocesses measurement reports before sending them to the BSC, the number of
measurement report messages from the BTS to the BSC is reduced. The RSL bandwidth
required over the Abis interface is therefore reduced. If the RSL multiplexing ratio over the
Abis interface is high, for example, 1:4 (that is, four RSLs are multiplexed on one 64 kbit/s
link), it is recommended that the BTS preprocess the measurement reports.
When measurement reports are preprocessed by the BTS, the MS power control and
transmission power control procedures are processed at the BTS because the power control
algorithms used by the BTS and BSC are the same. Therefore, the load on the BSC is
reduced. When the load on the BSC is heavy, it is recommended that the BTS preprocess the
measurement reports.
MSs cannot be handed over immediately because it takes some time for the BTS to
preprocess the measurement reports.
7.4.2 Channel Mode Modify
The channel mode modify procedure is a basic procedure for implementing radio link
management and is not controlled by parameters.
7.5 Multiple CCCHs
7.5.1 Deploying Multiple CCCHs

Aspect Requirement
BSC None
BTS None
GSM networking None
MS None
MSC None
Feature Parameter Description. For details about license items, see
License Control Item Description.
Others None
7.5.1.2 Activation
Using MML Commands
On the BSC LMT, run the SET GTRXCHAN command with its parameters set as follows:
 Set TRX ID and Channel No. to appropriate values.
 Set Channel Type to BCH(BCH).
The BCCH can be configured only in channel 0, and the extension BCCH can be configured in channel 2, 4, or
6.
If an extension BCCH is configured, the CCCH-related parameters in the system information (SI) must be
configured accordingly. For example, if an extension BCCH is configured in timeslot 2, the CCCH-related
parameters in the SI must be configured as two uncombined CCCHs.
//Activating Multiple CCCHs

SET GTRXCHAN: TRXID=0, CHNO=2, CHTYPE=BCH;
Using the CME

1. Run the SET GTRXCHAN command with its parameter set as follows:
 Set TRX ID to an appropriate value.
 Set Channel No. to 2.
 Set Channel Type to TCHFR(TCH Full Rate) or TCHHR(TCH Half
Rate).
2. Use an MS to initiate a call.
3. Trace RSL messages over the Abis interface and view the paging messages.
Expected result: The value of channel-no. in all paging messages is 0.
4. On the BSC LMT, run the SET GTRXCHAN command with its parameters set as
follows:
 Set TRX ID to an appropriate value.
 Set Channel No. to 2.
 Set Channel Type to BCH(BCH).
5. Use an MS to initiate a call.
6. Trace RSL messages over the Abis interface and view the paging messages.
Expected result: The value of channel-no. in all paging messages is either 0 or 2.
Using MML Commands
Run the SET GTRXCHAN command with its parameter set as follows:
 Set TRX ID and Channel No. to appropriate values.
 Set Channel Type to TCHFR(TCH Full Rate) or TCHHR(TCH Half Rate).
//Deactivating Multiple CCCHs

SET GTRXCHAN: TRXID=0, CHNO=2, CHTYPE=TCHFR;
Using the CME

7.6 Performance Monitoring
Monitor the counter listed in the following table to observe the number of call drops during
location updates.
Counter Name Counter Description
CELL.SD.CALL.DROPS.LOC.UPDATE CM30E:Call Drops on SDCCH (Location

(BSC6900, BSC6910) Updating)
8 Parameters
 GBTSFunction Parameter Reference: contains all parameters related to radio access
reference?
9 Counters
counters.
 GBTSFunction Performance Counter Summary:
contains all counters related to radio access
reference?
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
1. 3GPP TS 08.58: Base Station Controller-Base Transceiver Station(BSC-BTS)

interface; Layer3 specification
2. Power Control Feature Parameter Description
3. Radio Resource Management Feature Parameter Description
4. License Management Feature Parameter Description
GSM BSS
GBSS20.1
Dynamic Channel Convers

Feature Parameter
Description
Issue 02
Date 2019-01-31

Notice

Address:
Website: https:/
3.6.24 Contents
1.1 Scope
1.3 Change History
2 Overview
2.1 Introduction
3.1 SDCCH Dynamic Adjustment
3.1.1 Overview
3.1.2 Dynamic SDCCH Conversion Decision
3.1.3 Dynamic SDCCH Conversion Execution
3.1.4 SDCCH Reversion Decision
3.1.5 SDCCH Reversion Procedure
3.1.6 Impact
3.2 Dynamic Adjustment Between FR and HR
3.2.1 Overview
3.2.2 Dynamic TCH HR/FR Conversion During Channel Allocation
3.2.2.1 Overview
3.2.2.2 Rate Adjustment Algorithm
3.2.2.3 Procedures
3.2.3 Dynamic TCH HR/FR Conversion During a Call
3.2.3.1 Overview
3.2.3.3 Procedures
3.3 Dynamic PDCH Conversion
3.3.1 Overview
3.3.2 Dynamic PDCH Conversion Procedure
3.4 Dynamic Multiple CCCH
3.4.1 Overview
3.4.2 Application Scenario
3.4.3 Adding CCCHs Dynamically
3.4.4 Deleting CCCHs Dynamically
4 Related Features
4.1 GBFD-113001 SDCCH Dynamic Adjustment
4.2 GBFD-113402 Dynamic Adjustment Between FR and HR
4.3 GBFD-511503 Dynamic Multiple CCCH
5 Network Impact
5.1 Dynamic SDCCH Conversion
5.1.1 System Capacity
5.1.2 Network Performance
5.2 Dynamic TCH HR/FR Conversion
6.1 When to Use Dynamic Channel Conversion
6.1.1 Dynamic SDCCH Conversion
6.1.2 Dynamic TCH HR/FR Conversion
6.1.3 Dynamic PDCH Conversion
6.1.4 Dynamic Multiple CCCH
6.2 Required Information
6.3 Planning
6.4 Overall Deployment Procedure
6.5 Deploying Dynamic SDCCH Conversion
6.5.1 Deployment Requirements
6.5.2 Activation
6.5.3 Activation Observation
6.5.4 Deactivation
6.6 Deploying Dynamic TCH HRFR Conversion
6.6.2.1 Data Preparation
6.6.2.2 Activation
6.6.3.1 Activation
6.7 Deploying Dynamic Multiple CCCH
6.7.2 Precautions
6.7.3 Data Preparation
6.7.4 Activation
6.7.6 Deactivation
6.8 Performance Optimization
6.9 Troubleshooting
7 Parameters
8 Counters
9 Glossary
1.1 Scope
This document describes Dynamic Channel Conversion, including its technical principles,
related features, network impact, and engineering guidelines.
 GBFD-113001 SDCCH Dynamic Adjustment
 GBFD-113402 Dynamic Adjustment Between FR and HR
 GBFD-511503 Dynamic Multiple CCCH
Purpose

Software Interfaces
1.3 Change History
 Feature change
02 (2019-01-31)
Compared with Issue 01 (2018-04-10) of GBSS20.1, 02 (2019-01-31) of GBSS20.1 includes

the following changes.
Feature change None None
Editorial change The counter name is changed. For details, None

see 6.7.5 Activation Observation.
01 (2018-04-10)
Draft A (2018-02-05)

Feature change Added the impacted feature GBFD-200201 None

1.2 MHz Networking for BCCH TRXs. For
details, see 4 Related Features.
2 Overview
2.1 Introduction
The Dynamic Channel Conversion feature enables the conversion of a channel from one type
to another based on the actual service requirement in the network. Such a conversion is
temporary and triggered by a combination of certain network conditions. The converted
channel reverts to the original type when the triggering conditions disappear.
Dynamic Channel Conversion includes the following types of conversions:
 Between the traffic channel (TCH) and the standalone dedicated control channel
(SDCCH)
 Between the full-rate TCH (TCHF) and the half-rate TCH (TCHH)
 Between the TCH and the packet data channel (PDCH)
 From the dynamic PDCH to the SDCCH
 Dynamic CCCH conversion
Dynamic Channel Conversion facilitates channel configuration for cells and improves the
service processing capability of cells.
Dynamic √ √ √ √
Adjustment
Between FR and
HR
Dynamic Multiple √ √ √ √
CCCH
SDCCH √ √ √ √
Dynamic
Adjustment
3.1 SDCCH Dynamic Adjustment
3.1.1 Overview
This section describes the GBFD-113001 SDCCH Dynamic Adjustment feature.

Dynamic SDCCH conversion is triggered when the requested SDCCH is not allocated to the
MS. This procedure involves converting a TCHF to the SDCCH, reverting the SDCCH to the
TCHF, and converting the dynamic PDCH to SDCCH. (GBFD-113001 SDCCH Dynamic
Adjustment)
Dynamic SDCCH conversion helps to decrease the SDCCH congestion rate in the network
and reduce the impact of the initial SDCCH configuration on the system performance.
Therefore, it reduces the requirement of evaluating the SDCCH demands accurately.
The process of converting the TCHF to the SDCCH and converting the dynamic PDCH to
SDCCH consists of two phases: SDCCH conversion decision and SDCCH conversion
execution.
An SDCCH can be reverted to a TCHF only. The process of reverting the SDCCH to the
TCHF also consists of two phases: SDCCH reversion decision and SDCCH reversion
execution. Figure 3-1 shows the complete procedure of dynamic SDCCH conversion.
Figure 3-1 Dynamic SDCCH conversion procedure
The BSC preferentially converts an idle TCHF to an SDCCH. If there is no idle TCHF and
the PDCH2SDEN (BSC6900, BSC6910) parameter is set to YES(Yes), the BSC converts a
PDCH to the SDCCH. The PDCH to be converted to the SDCCH must meet the same
requirements as the TCHF. This document uses a TCHF as an example for your reference
only.
3.1.2 Dynamic SDCCH Conversion Decision
The typical decision-making process for dynamic SDCCH conversion consists of three
procedures: trigger of the conversion, decision of the conversion, and TCHF channel
selection.
Dynamic SDCCH conversion can be triggered if the number of idle SDCCHs in the cell is
smaller than or equal to the value of IDLESDTHRES (BSC6900, BSC6910) or the SDCCH
allocation fails during the channel assignment. If the TCHF is converted to the SDCCH after
the SDCCH allocation failure, the converted SDCCH is used for the next SDCCH request.
Trigger of Dynamic SDCCH Conversion
Figure 3-2 shows the trigger process of dynamic SDCCH conversion.

Figure 3-2 Trigger of dynamic SDCCH conversion
Dynamic SDCCH Conversion Decision
Figure 3-3 shows the decision process of dynamic SDCCH conversion.

Figure 3-3 Decision of dynamic SDCCH conversion
After the dynamic SDCCH conversion decision is triggered, the BSC determines whether to
allow the conversion based on the following rules.
1. Whether the BSC internal flow control level is 0
If yes, dynamic SDCCH conversion is allowed. Otherwise, it is not allowed.
The BSC internal flow control is performed based on the CPU usage of the current cell.
If the CPU usage is less than 65% and no emergency event (for example, massive
maintenance operations) occurs, the flow control is not performed, that is, the internal
flow control level is 0.
2. Whether SDDYN (BSC6900, BSC6910) is set to Yes
3. Whether there is another ongoing dynamic SDCCH conversion procedure in the cell
If yes, the new conversion procedure is not allowed. Otherwise, it is allowed.
Only one dynamic SDCCH conversion procedure can be performed at a time, in a cell.
4. Whether the number of idle SDCCHs in the cell is smaller than or equal to the value
of IDLESDTHRES (BSC6900, BSC6910)
5. Whether the number of SDCCHs in the cell plus eight is smaller than or equal to the
value of CELLMAXSD (BSC6900, BSC6910)
One TCHF can be converted into eight SDCCHs. Therefore, the total number of SDCCHs after a
conversion equals the number of current SDCCHs plus eight.
6. Whether there are sufficient idle TCHs for the TRXs in the cell
The decision procedure is as follows:
a. The BSC measures the number of idle TCHFs and the number of idle TCHHs
in the cell.
a. If the SDDynAdjRsvTchSwitch (BSC6900, BSC6910) parameter is set to
ON(On), the BSC proceeds with 6.e.
a. The BSC determines whether the number of idle TCHHs plus twice the
number of idle TCHFs is greater than eight.
If yes, dynamic SDCCH conversion is allowed. Otherwise, the BSC proceeds with
6.d.
b. The BSC determines whether the number of idle TCHHs plus twice the
number of idle TCHFs is greater than twice the number of TRXs in the cell.
If yes, dynamic SDCCH conversion is allowed. Otherwise, dynamic SDCCH
conversion is not allowed.
c. The dynamic SDCCH conversion is not allowed if the number of idle TCHHs
plus twice the number of idle TCHFs is less than or equal to
SDDynAdjRsvTchNum (BSC6900, BSC6910).
4. Whether there is any qualified TCHF for conversion
If yes, dynamic SDCCH conversion is allowed. Otherwise, dynamic SDCCH conversion
is not allowed.
TCHF Selection
After the BSC determines that dynamic SDCCH conversion can be performed, it must select
a TCHF for conversion.
A qualified TCHF that can be converted to the SDCCH must meet the following
requirements:
 The channel must be in the available state.
 If DIFFBANDSDCCHDYNADJ (BSC6900, BSC6910) is set to YES(Yes), a TCHF
carried on a TRX incompatible with the BCCH frequency band can be dynamically
converted to an SDCCH. You can set the number of the timeslots on each TRX that can be
converted into SDCCHs by setting the SDCCHDYNADJTSNUM (BSC6900, BSC6910)
parameter. If DIFFBANDSDCCHDYNADJ (BSC6900, BSC6910) is set to NO(No), only a
TCHF on the BCCH TRX or a TRX compatible with the BCCH frequency band can be
dynamically converted to an SDCCH. The MainBcchSdcchNum (BSC6900, BSC6910)
parameter specifies the number of timeslots corresponding to the TCHFs that can be
converted to SDCCHs. The TCHF frequency band and the corresponding BCCH
frequency band must be mapped as listed in Table 3-1.
 The channel must be an initial TCHF or a TCHF that is converted from TCHHs.
 The number of existing SDCCHs on the TRX carrying the TCHF must be less or
equal than eight x SDCCHDYNADJTSNUM (BSC6900, BSC6910).
If the channel type of a timeslot is SDCCH/8, the timeslot contains eight SDCCHs.
 The current cell must have more than one TRX.

 If the quadruple-transceiver unit (QTRU) board is used, the TCH on the TRX with the
minimum number of SDCCHs is preferentially selected.
Table 3-1 Mapping between the BCCH frequency band and the TCHF frequency band for Dynamic
SDCCH Conversion
BCCH Frequency Band TCHF Frequency Band for Dynamic SDCCH

Conversion
P-GSM900 M P-GSM900 M
E-GSM900 M P-GSM900 M or E-GSM900 M
R-GSM900 M P-GSM900 M, E-GSM900 M, or R-GSM900

BCCH Frequency Band TCHF Frequency Band for Dynamic SDCCH
Conversion
DCS1800 M DCS1800 M
PCS1900 M PCS1900 M
GSM850 M GSM850 M
GSM480 M GSM480 M
GSM450 M GSM450 M
TGSM810 TGSM810
The TCHF selection varies with the cell type.
If... Then...
The cell is a common cell The BSC selects any of the non-BCCH
qualified TCHFs for dynamic SDCCH
conversion.
NOTE:
If the serving cell is a single-frequency cell or served
by a QTRU board, the BSC selects a BCCH qualified
TCHF for dynamic SDCCH conversion.
The cell is a concentric cell The BSC selects a qualified TCHF in a

prioritized order as follows: idle TCHF in the
underlaid subcell; busy TCHF in the
underlaid subcell; idle TCHF in the overlaid
subcell; and busy TCHF in the overlaid
subcell.
The cell is a co-BCCH cell The BSC preferentially selects a qualified

idle TCHF in the underlaid subcell. If such an
idle TCHF is not found, the BSC selects a
qualified busy TCHF.
NOTE:
The TCHFs in the overlaid subcell of a co-BCCH cell
cannot be used for dynamic SDCCH conversion.
3.1.3 Dynamic SDCCH Conversion Execution
After selecting a TCHF, the BSC performs the dynamic SDCCH conversion procedure. The
dynamic SDCCH conversion procedure varies depending on the status of the selected TCHF.
 If the selected TCHF is idle, the procedure is as follows:
1. The BSC adjusts the channel attribute from TCHF to SDCCH.
2. The BSC performs different operations based on whether the channel attribute has
been successfully adjusted.
 If yes, the BSC configures a flag indicating that the cell is under dynamic
channel conversion.
 If no, the BSC terminates the dynamic conversion.
3. The BSC sends the BTS a command instructing the BTS to adjust the channel
attribute and measures the counter R3516A:Number of Channel Conversions (TCH-
SDCCH).
4. Upon receiving the command, the BTS starts converting the channels. After the
channels are converted, the BTS sends the Status Change Report to the BSC.
5. Upon receiving the Status Change Report, the BSC sets the status of the converted
SDCCH/8 to idle and deletes the flag. The dynamic TCHF-to-SDCCH conversion is
complete.
 If the selected TCHF is busy, the procedure is as follows:
1. To prevent the services carried on the selected TCHF from being interrupted, the BSC
initiates a forced intra-cell handover.
2. The BSC sets the flag indicating that the cell is under dynamic channel conversion
and sets the channel status to "TCHF converted to SDCCH, waiting for forced handover
response" to prevent the TCHF from being assigned to other services.
3. The BSC performs different operations based on whether a forced handover response
is received.
 If the BSC receives the forced handover response, it determines whether the
forced handover is successful.
 If the forced handover fails, the TCHF is not released and the BSC deletes the
dynamic conversion ongoing flag of the cell. The channel conversion is terminated.
 If the forced handover is successful, the BSC sets the channel status to
"Waiting for channel release". When the TCHF becomes idle, the BSC follows the
procedure for converting the idle TCHF to the SDCCH.
 If the BSC does not receive any forced handover response, the BSC deletes the
flag. The channel conversion is terminated.
The TCH far from the PDTCH is preferentially selected for dynamic SDCCH conversion.
3.1.4 SDCCH Reversion Decision
After the TCHF is converted to the SDCCH, the SDCCH is reverted to the TCHF if certain
conditions are met.
The BSC determines to revert the SDCCH to the TCHF if the following conditions are met:
 The period in which a TCH or dynamic PDCH is converted to an SDCCH and then
reverted to a TCH is longer than or equal to MINRESTIMETCH (BSC6900, BSC6910).
 The number of idle SDCCHs must be greater than the value of IDLESDTHRES
(BSC6900, BSC6910) plus 8.
 The number of idle SDCCHs must be greater than the value of IDLESDTHRES
(BSC6900, BSC6910) plus 8.
 The selected SDCCH/8 channels are converted from a TCHF.
 One or more of the selected SDCCH/8 channels are idle.
 The channel selection varies with the type of the cell:
 If the cell is not a concentric cell, the SDCCH reversion can be performed
when the previous conditions are met.
 If the cell is a concentric cell, the BSC preferentially selects an SDCCH that
meets the previous conditions on the TRX in the overlaid subcell. If there is no
appropriate SDCCH in the overlaid subcell, the BSC selects an appropriate SDCCH in
the underlaid subcell.
 If the QTRU is used, the SDCCH on the timeslot with the maximum number of
SDCCHs is preferentially selected.
If the above conditions are not met, the reversion from the SDCCH to the TCHF is not
triggered.
3.1.5 SDCCH Reversion Procedure
If the requirements for SDCCH reversion are met, the BSC performs the SDCCH reversion
procedure.
The SDCCH reversion procedure lasts less than three seconds. A busy SDCCH/8 channel can
also be reverted to the TCHF. Therefore, based on the status of the selected SDCCH/8
channels, the SDCCH reversion procedure is classified into the following types:
If all the selected SDCCH/8 channels are idle, the SDCCH reversion procedure is as follows:
1. The BSC adjusts the channel attribute from SDCCH to TCHF.
2. The BSC sends a command to the BTS for adjusting the channel attribute and starts
the relevant performance measurement.
3. Upon receiving the command, the BTS starts converting the channels. After the
channels are converted, the BTS sends the Status Change Report to the BSC.
4. Upon receiving the Status Change Report, the BSC sets the status of the converted
TCHF to idle. The SDCCH-to-TCHF reversion is complete.
If one or more of the selected SDCCH/8 channels are busy, the SDCCH reversion procedure
is as follows:
1. To prevent call disruption on the selected SDCCH/8 channel, the BSC triggers the
timer, waiting for the release of channels.
2. The BSC sets the channel status to "SDCCH/8 converted to TCHF, waiting for idle
channel" to prevent these channels from being assigned before reversion.
3. If the sub-channels are still busy when the timer expires, they are released forcibly.
4. When all the selected SDCCH/8 channels are idle, the BSC follows the related
procedure for reverting the idle SDCCH.
Typically, all the SDCCH/8 channels will be idle before the timer expires, because the SDCCH is occupied
for a short time.
3.1.6 Impact
The dynamic SDCCH conversion affects the system performance mainly in the following
aspects:
 The bearer capacity of TCHs in a cell is reduced because TCHFs are converted to
SDCCHs.
 The intra-cell handovers are increased, if busy TCHFs are converted to SDCCHs.
3.2 Dynamic Adjustment Between FR and HR
3.2.1 Overview
The dynamic TCH HR/FR conversion (GBFD-113402 Dynamic Adjustment Between FR and
HR) consists of the following aspects:
 Dynamic TCH HR/FR conversion during channel allocation
During channel allocation, the BSC adjusts the TCHs allocated to MSs in real time based
on the cell load and requested TCH type.
 Dynamic TCH HR/FR conversion during a call
During a call, the BSC dynamically adjusts TCHs based on the cell load and receive
quality of MSs.
3.2.2.1 Overview
This section describes the GBFD-113402 Dynamic Adjustment Between FR and HR feature.
Dynamic TCH HR/FR conversion is performed in two cases: when the traffic load is high in
a cell, certain full-rate (FR) TCHs are converted to half-rate (HR) TCHs to allow more MSs
to access the network; when the traffic load is low, certain TCHHs are converted to TCHFs to
provide better speech quality to the MS users. This function is performed by using the TCH
HR/FR rate adjustment algorithm.
Dynamic TCH HR/FR conversion is performed in real time during the channel allocation. If a
connection requires a TCHH but no idle TCHH is available in the cell, the BSC selects a
TCHF to convert it into two TCHHs and then allocates one of them to the connection. If a
connection requires a TCHF but no idle TCHF is available, the BSC selects a couple channel
to convert it into a TCHF and then allocates the TCHF to the connection. If there is no couple
channel available in the cell, the BSC selects a single channel, steers the traffic on the peer
busy TCHH to another channel, and then combines two idle single channels into a couple
channel. Then, the BSC converts the couple channel to a TCHF.
Set TCHAJFLAG (BSC6900, BSC6910) to YES(Yes) to start the TCH HR/FR conversion
during channel allocation.
The rate adjustment algorithm varies with different rate of requested channels. The required
channel rate is defined in the channel assignment request as follows:
 TCHF only
 TCHH only/TCHH preferred
 TCHF preferred
TCHF only
shows the channel assignment procedure when the channel rate type in a channel
Figure 3-4
assignment request is TCHF only. The channel request is accepted in the following situations;
otherwise, the channel request is rejected.
 If an idle TCHF is available, the BSC assigns the TCHF directly.
 If no idle TCHF is available but an idle couple channel is available (One timeslot
carries two TCHHs. If both TCHHs are idle, they are called couple channels.), convert
couple channels to TCHFs and allocate the TCHFs.
 If no idle TCHF or idle couple channel is available but an idle single channel is
available (One timeslot carries two TCHHs. If one of them is occupied, the idle TCHH is
called a single channel, channel fragment, or fragment), the BSC determines whether there
is more than one idle and adjustable TCHH in the cell. If there is more than one idle
TCHH in the cell, the BSC initiates the intra-cell handover. Then, the BSC converts the
couple channel generated from the intra-cell handover to the TCHF and assigns the TCHF
accordingly.
Figure 3-4 Channel rate adjustment procedure for TCHF only
TCHH only/TCHH preferred
If the channel rate type in a channel assignment request is TCHH only/TCHH preferred, the
channel request is accepted in the following situations; otherwise, the channel request is
rejected. Figure 3-5 shows the channel rate adjustment procedure.
 If an idle single channel is available, the BSC assigns the single channel directly.
 If no idle single channel is available but an idle couple channel is available, the BSC
assigns the idle TCHH of the couple channel.
 If no idle single channel or couple channel is available but an idle TCHF is available,
the BSC converts the TCHF to the couple channel and assigns the idle TCHH of the
couple channel.
If the BSC assigns single channels preferably, the TCHHs can be utilized optimally with the number of
fragments reduced.
Figure 3-5 Channel rate adjustment procedure for TCHH only/TCHH preferred
When the TCHH preferable policy is used and JudgeRxLevWhenAssignHr (BSC6900,

BSC6910) is set to ON(On), the BSC determines whether the receive signal level is lower than
a specified threshold. If yes, TCHFs are assigned preferentially. If no, TCHHs are assigned
preferentially. The details are as follows:
For adaptive multirate (AMR) speech services: If the receive signal level is lower than
MinRxLevWhenAssignHr (BSC6900, BSC6910), TCHFs are assigned preferentially;
otherwise, TCHHs are assigned preferentially. For non-AMR speech services:
 When HOCTRLSWITCH (BSC6900, BSC6910) is set to
HOALGORITHM1(Handover algorithm I): If the receive signal level is lower than
MinRxLevWhenAssignHr (BSC6900, BSC6910) plus 5, TCHFs are assigned
preferentially; otherwise, TCHHs are assigned preferentially.
 When HOCTRLSWITCH (BSC6900, BSC6910) is set to
HOALGORITHM2(Handover algorithm II): If the receive signal level is lower than
MinRxLevWhenAssignHr (BSC6900, BSC6910) +
(AMRFULLTOHALFHOPATHTHRESH (BSC6900, BSC6910) -
NOAMRFULLTOHALFHOPATHTHRESH (BSC6900, BSC6910)), TCHFs are assigned
preferentially; otherwise, TCHHs are assigned preferentially.
TCHF preferred
If the channel rate type in a channel assignment request is TCHF preferred, the channel
request is accepted when the following requirements are met; otherwise, the channel request
is rejected. Figure 3-6 shows the channel rate adjustment procedure.
 If an idle TCHF is available, the BSC assigns the TCHF directly.
 If no idle TCHF is available but an idle couple channel is available, the BSC converts
the couple channel to the TCHF and then assigns the TCHF.
 If no idle TCHF or couple channel is available but an idle single channel is available,
the BSC determines whether there is more than one idle and adjustable TCHH in the cell.
If there is more than one idle TCHH in the cell, the BSC initiates the intra-cell handover.
Then, the BSC converts the couple channel generated from the intra-cell handover to the
TCHF and assigns the TCHF accordingly. Otherwise, the BSC assigns the idle single
channel.
Figure 3-6 Channel rate adjustment procedure for TCHF preferred
The calls on single channels can be handed over to other channels during the TCHH-to-TCHF conversion only
when ENTCHADJALLOW (BSC6900, BSC6910) is set to Yes.
3.2.2.3 Procedures
This describes the TCHF-to-TCHH conversion and the TCHH-to-TCHF conversion.

TCHF-to-TCHH Conversion
1. If there is no TCHH available for a call that requests a TCHH, the channel request is
queued.
 If the queuing fails, then
For the TCHH-only request, a message is returned, indicating that the channel request
fails.
For the TCHH-preferred request, a less-preferred channel such as the couple channel
or TCHF is allocated.
 If the queuing is successful, then
The BSC converts a TCHF to a couple channel and adjusts the corresponding channel
attributes. Then, it issues the BSC timeslot conversion command, and starts the
relevant performance measurement.
2. The BSC issues a channel type adjustment command to the BTS. The BSC timeslot
adjustment command or the channel type adjustment command will be sent again upon
timeout.
3. On receiving the adjustment command, the BTS starts channel type adjustment. Once
the channel type adjustment is complete, the BTS sends the Status Change Report to the
BSC.
4. On receiving the Status Change Report from the BTS, the BSC sets the couple
channel to the idle state. Therefore, the TCHF-to-TCHH conversion is complete. Then,
the BSC assigns the converted channel to the call in the queue and starts the
measurement of relevant performance statistics.
TCHH-to-TCHF Conversion
1. If a couple channel is available for a call that requests a TCHF, the channel request is
queued.
 For the TCHF-only request, a message is returned, indicating that the channel
request fails.
 For the TCHF-preferred request, a less-preferred channel such as a couple
channel or a single channel is allocated.
The BSC converts the couple timeslots into a TCHF channel. For details about the
subsequent procedures, see TCHF-to-TCHH Conversion.
2. If a single channel is available for a call that requests a TCHF, the channel request is
queued. The duration for queuing is set to 5.5 seconds, including the time for adjusting
the single channels to the couple channel.
 For the TCHF-only request, a message is returned, indicating that the channel
request fails.
 For the TCHF-preferred request, the single channel is allocated.
The BSC steers the traffic in the busy peer TCHH channel of the single channel to
another channel by initiating the forced intra-cell handover regardless of the settings
of handover parameters.
Different operations are performed based on whether a response to the forced
handover is received.
 If the BSC receives the response to the forced handover, it determines whether
the forced handover is successful. If the forced handover fails, the BSC allocates the
single channel to another call in the queue and does not release the busy peer TCHH
channel. If the forced handover is successful, the channel status is set to Waiting for
Releasing the Channel; when the channel status is Service Idle, the BSC converts the
couple channel into a TCHF.
 If the BSC does not receive any response to the forced handover, the handover
failure procedure is triggered.
3.2.3.1 Overview
Dynamic TCHH/TCHF conversion during a call enables the BSC to dynamically adjust
TCHs based on the cell load or receive quality of MSs during a call.
Handovers between a TCHF and a TCHH are classified into the following types:
 AMR TCHF-to-TCHH handover
 Non-AMR TCHF-to-TCHH handover
These types of handovers enable the BSC to hand over calls from TCHFs to TCHHs when
the cell load is high. This increases cell capacity and reduces cell congestion.
 AMR TCHH-to-TCHF handover
 Non-AMR TCHH-to-TCHF handover
These types of handovers enable the BSC to hand over calls from TCHHs to TCHFs when
the cell load is low. This improves voice quality.
Table 3-2 lists the algorithm combinations and how to enable them.
Table 3-2 Usage scenarios for handover algorithms
No. Algorithm Combination How to Enable Algorithm
Combination
1 HUAWEI I Handover and Set HOCTRLSWITCH

Dynamic HR/FR Adaptation (BSC6900, BSC6910) to
HOALGORITHM1(Handover
algorithm I),
INTRACELLFHHOEN
(BSC6900, BSC6910) to
HOBASECAPANDQUAL(H
OBASECAPANDQUAL),
AMRFULLTOHALFHOALL
No. Algorithm Combination How to Enable Algorithm
Combination
OW (BSC6900, BSC6910) to
YES(Yes), and
NOAMRFULLTOHALFHOA
LLOW (BSC6900, BSC6910) to
YES(Yes).
2 HUAWEI II Handover and Set HOCTRLSWITCH

Dynamic HR/FR Adaptation (BSC6900, BSC6910) to
HOALGORITHM2(Handover
algorithm II),
AMRFULLTOHALFHOALL
OW (BSC6900, BSC6910) to
YES(Yes), and
NOAMRFULLTOHALFHOA
LLOW (BSC6900, BSC6910) to
YES(Yes).
Trigger Conditions for an AMR TCHF-TCHH Handover
If AMRFULLTOHALFHOALLOW (BSC6900, BSC6910) is set to YES(Yes), the trigger

conditions for an AMR TCHF-TCHH handover are as follows:
 VOICEVER (BSC6900, BSC6910) used by the call is full-rate speech version 3.
 The proportion of MSs occupying TCHHs is less than
ALLOWHALFRATEUSERPERC (BSC6900, BSC6910).
 When F2HHOLOADSTFSWITCH (BSC6900, BSC6910) is set to ON(On):
 If the cell load is higher than AMRFULLTOHALFHOTHRESH (BSC6900,
BSC6910), the BSC hands over all calls meeting conditions in a cell from TCHFs to
TCHHs within the period specified by FULLTOHALFHODURATION (BSC6900,
BSC6910).
 If the cell load is lower than the value of AMRFULLTOHALFHOTHRESH

(BSC6900, BSC6910) minus FullToHalfHoLoadStf (BSC6900, BSC6910), the BSC stops
the TCHF-to-TCHH handover triggered by the cell load.
 When F2HHOLOADSTFSWITCH (BSC6900, BSC6910) is set to OFF(Off), if the
cell load is higher than AMRFULLTOHALFHOTHRESH (BSC6900, BSC6910), the BSC
hands over all calls meeting conditions in a cell from TCHFs to TCHHs within the period
specified by FULLTOHALFHODURATION (BSC6900, BSC6910).
 Downlink path loss of the call ≤ AMRFULLTOHALFHOPATHTHRESH (BSC6900,
BSC6910) + Path loss offset
Path loss offset = (duration for triggering handover from full rate to half
rate/FULLTOHALFHOPERIOD (BSC6900, BSC6910) + 1) x
AMRFULLTOHALFHOPATHADJSTEP (BSC6900, BSC6910)
 ATCB of the call ≥ AMRFULLTOHALFHOATCBTHRESH (BSC6900, BSC6910) –
ATCB offset
ATCB offset = (duration for triggering handover from full rate to half
AMRFULLTOHALFHOATCBADJSTEP (BSC6900, BSC6910)
 Uplink signal quality of the call ≤ AMRFULLTOHALFHOQUALTHRESH
(BSC6900, BSC6910)
 Downlink signal quality of the call ≤ AMRFULLTOHALFHOQUALTHRESH
(BSC6900, BSC6910)
 The preceding conditions are met for FULLTOHALFHOLASTTIME (BSC6900,
BSC6910) within FULLTOHALFHOSTATTIME (BSC6900, BSC6910).
Trigger Conditions for a Non-AMR TCHF-TCHH Handover
If NOAMRFULLTOHALFHOALLOW (BSC6900, BSC6910) is set to YES(Yes), the trigger

conditions for a non-AMR TCHF-TCHH handover are as follows:
 VOICEVER (BSC6900, BSC6910) used by the call is full-rate speech version 1 or full-
rate speech version 2.
 The proportion of MSs occupying TCHHs is less than
ALLOWHALFRATEUSERPERC (BSC6900, BSC6910).
 If the cell load is higher than NOAMRFULLTOHALFTHRESH (BSC6900,
BSC6910), the BSC hands over all calls meeting conditions in a cell from TCHFs to
TCHHs within the period specified by FULLTOHALFHODURATION (BSC6900,
BSC6910).
 If the cell load is lower than the value of NOAMRFULLTOHALFTHRESH

(BSC6900, BSC6910) minus FullToHalfHoLoadStf (BSC6900, BSC6910), the BSC stops
the TCHF-to-TCHH handover triggered by the cell load.
cell load is higher than NOAMRFULLTOHALFTHRESH (BSC6900, BSC6910), the BSC
hands over all calls meeting conditions in a cell from TCHFs to TCHHs within the period
specified by FULLTOHALFHODURATION (BSC6900, BSC6910).
 Downlink path loss of the call ≤ NOAMRFULLTOHALFHOPATHTHRESH
(BSC6900, BSC6910) + Path loss offset
Path loss offset = (duration for triggering handover from full rate to half
NOAMRFULLTOHALFHOPATHADJSTEP (BSC6900, BSC6910)
 ATCB of the call ≥ NOAMRFULLTOHALFHOATCBTHRESH (BSC6900,
BSC6910) – ATCB offset
ATCB offset = (duration for triggering handover from full rate to half
NOAMRFULLTOHALFHOATCBADJSTEP (BSC6900, BSC6910)
 Uplink signal quality of the call ≤ NOAMRFULLTOHALFHOQUALTHRESH
(BSC6900, BSC6910)
 Downlink signal quality of the call ≤ NOAMRFULLTOHALFHOQUALTHRESH
(BSC6900, BSC6910)
 The preceding conditions are met for FULLTOHALFHOLASTTIME (BSC6900,
BSC6910) within FULLTOHALFHOSTATTIME (BSC6900, BSC6910).
Trigger Conditions for an AMR TCHH-TCHF Handover
If AMRFULLTOHALFHOALLOW (BSC6900, BSC6910) is set to YES(Yes) or

AMRHALFTOFULLHOQUALALLOW (BSC6900, BSC6910) is set to YES(Yes), the trigger
conditions for an AMR TCHH-TCHF handover are as follows:
 VOICEVER (BSC6900, BSC6910) used by the call is half-rate speech version 3.
 If the cell load is lower than AMRHALFTOFULLHOTHRESH (BSC6900,
BSC6910), the BSC hands over all calls meeting conditions in a cell from TCHHs to
TCHFs within the period specified by HALFTOFULLHODURATION (BSC6900,
BSC6910).
 If the cell load is higher than the value of AMRHALFTOFULLHOTHRESH

(BSC6900, BSC6910) plus FullToHalfHoLoadStf (BSC6900, BSC6910), the BSC stops
the TCHH-to-TCHF handover triggered by the cell load.
cell load is lower than AMRHALFTOFULLHOTHRESH (BSC6900, BSC6910), the BSC
hands over all calls meeting conditions in a cell from TCHHs to TCHFs within the period
specified by HALFTOFULLHODURATION (BSC6900, BSC6910).
 Downlink path loss ≥ AMRHALFTOFULLHOPATHTHRESH (BSC6900, BSC6910)
 ATCB of the call ≤ AMRHALFTOFULLHOATCBTHRESH (BSC6900, BSC6910)
 Uplink signal quality of the call ≥ AMRHALFTOFULLHOQUALTHRESH
(BSC6900, BSC6910)
 Downlink signal quality of the call ≥ AMRHALFTOFULLHOQUALTHRESH
(BSC6900, BSC6910)
 The AMR TCHH-TCHF handover is triggered if VOICEVER (BSC6900, BSC6910) is
half-rate speech version 3 and any of the preceding conditions is met for
HALFTOFULLHOLASTTIME (BSC6900, BSC6910) within
HALFTOFULLHOSTATTIME (BSC6900, BSC6910).
Trigger Conditions for a Non-AMR TCHH-TCHF Handover
If NOAMRFULLTOHALFHOALLOW (BSC6900, BSC6910) is set to YES(Yes) or

NOAMRHALFTOFULLHOQUALALLOW (BSC6900, BSC6910) is set to YES(Yes), the
trigger conditions for a non-AMR TCHH-TCHF handover are as follows:
 VOICEVER (BSC6900, BSC6910) used by the call is half-rate speech version 1.
 If the cell load is lower than NOAMRHALFTOFULLTHRESH (BSC6900,
BSC6910), the BSC hands over all calls meeting conditions in a cell from TCHHs to
TCHFs within the period specified by HALFTOFULLHODURATION (BSC6900,
BSC6910).
 If the cell load is higher than the value of NOAMRHALFTOFULLTHRESH

(BSC6900, BSC6910) plus FullToHalfHoLoadStf (BSC6900, BSC6910), the BSC stops
the TCHH-to-TCHF handover triggered by the cell load.
cell load is lower than NOAMRHALFTOFULLTHRESH (BSC6900, BSC6910), the BSC
hands over all calls meeting conditions in a cell from TCHHs to TCHFs within the period
specified by HALFTOFULLHODURATION (BSC6900, BSC6910).
 Downlink path loss of the call ≥ NOAMRHALFTOFULLHOPATHTHRESH
(BSC6900, BSC6910)
 ATCB of the call ≤ NOAMRHALFTOFULLHOATCBTHRESH (BSC6900,
BSC6910)
 Uplink signal quality of the call ≥ NOAMRHALFTOFULLHOQUALTHRESH

(BSC6900, BSC6910)
 Downlink signal quality of the call ≥ NOAMRHALFTOFULLHOQUALTHRESH
(BSC6900, BSC6910)
 The non-AMR TCHH-TCHF handover is triggered if VOICEVER (BSC6900,
BSC6910)
is half-rate speech version 1 and any of the preceding conditions is met for
HALFTOFULLHOLASTTIME (BSC6900, BSC6910) within
HALFTOFULLHOSTATTIME (BSC6900, BSC6910).
TCHH Adjustment
If a large number of MSs occupying TCHHs are available in a cell and TCHHs are not
properly distributed, a large number of single channels will exist in the cell. If
HALFRATEREPACKINGSWITCH (BSC6900, BSC6910) is set to YES(Yes), the BSC
selects an appropriate MS on a single channel (a TCH) and forcibly hands over it to another
single channel. This ensures that sufficient couple channels in the cell can be converted to
idle TCHFs.
Target Cell Selection
Only the serving cell can be selected as the target cell of the TCHF-TCHH handover.
3.2.3.3 Procedures
The dynamic TCH HR/FR conversion consists of TCHH-to-TCHF conversion and TCHF-to-
TCHH conversion. The specific procedure is as follows:
1. The BSC determines whether to send an HR/FR handover request to an MS based on
the triggering conditions.
2. The BSC checks the channel resources in the cell:
 After detecting idle channels in the cell, the BSC sends a handover command
to trigger the HR/FR conversion.
 After detecting no idle channels in the cell and receiving a message, the BSC
increments the number of congestions caused by HR/FR handover by one.
3.3.1 Overview
Dynamic PDCH conversion consists of TCH-to-dynamic PDCH conversion, dynamic PDCH-

to-TCH conversion, and dynamic PDCH-to-SDCCH conversion, wherein the TCH may be
the TCHF or TCHH.
The process of dynamic PDCH conversion consists of two phases: PDCH conversion
decision and PDCH conversion execution. See the GPRS/EGPRS Channel Management
Feature Parameter Description for the detailed information about TCH-to-PDCH
conversion. If a TCH request is received when no idle TCH is available and there are
dynamic PDCHs converted from the TCH in the cell, the BSC initiates a dynamic PDCH-to-
TCH conversion.
The BSC converts a dynamic PDCH to an SDCCH if there is no idle TCHF available. The
SDCCH can be reverted to a TCHF only.
This function enables the dynamic balance between the CS load and the PS load, reducing the
difficulties in planning the PS capacity of the cell. In addition, it lowers the possibility of
PDCH waste and therefore maximizes the utilization of radio channel resources.
3.3.2 Dynamic PDCH Conversion Procedure
Dynamic PDCH conversion includes TCH-to-PDCH conversion, PDCH-to-TCH conversion,

and PDCH-to-SDCCH conversion. For details about dynamic PDCH-to-SDCCH conversion,
see section 3.1 SDCCH Dynamic Adjustment.
The following description is based on the external PCU. If the built-in PCU is configured, then the message
interactions between the BSC and the PCU are not needed. The BSC6910 does not support the built-in PCU.
TCH-to-Dynamic PDCH Conversion
Figure 3-7 shows the TCH-to-dynamic PDCH conversion procedure.

Figure 3-7 TCH-to-dynamic PDCH conversion
1. If there is no PS traffic channel available when an MS initiates the PS services, the

PCU allocates a CS timeslot and retrieves the channel type, usage status, and the
"whether PDCH assignment request can preempt the channels of CS services" flag of the
timeslot.
2. If the CHTYPE (BSC6900, BSC6910) of this timeslot is Dynamic PDCH and the flag
"whether PDCH assignment request can preempt the channels of CS services" is "Yes",
the system proceeds with the following procedures:
 If the timeslot allocated by the PCU is idle, the BSC converts the channel on the
timeslot to a PDCH, and then sends a message to the PCU indicating that the channel
request is successful.
 If the timeslot (half-rate or full-rate) allocated by the PCU is busy, the BSC
determines whether to initiate the intra-cell handover.
The intra-cell handover is not initiated if no idle timeslot is available in the cell or if the
channel allocated by the PCU is a TCHH and only one idle timeslot is available in the cell.
If an intra-cell handover cannot be initiated, the BSC determines whether the priority of the
PS service is higher than that of the CS service.
 If the priority of the PS service is higher, the BSC releases the channel on the
allocated timeslot forcibly and converts the channel to a PDCH.
 If the priority of the CS service is higher, the BSC sends the request failure message
to the PCU.
If there are enough idle timeslots in the cell, the BSC initiates an intra-cell handover to steer
the traffic on the timeslot to other timeslots.
 If the BSC initiates an intra-cell handover and the handover is successful, the channel
on the allocated timeslot is converted to a PDCH.
 If the intra-cell handover fails, the BSC determines whether the priority of the PS
service is higher.
to the PCU.
To avoid the triggering of a new intra-cell handover, during the channel conversion, the dynamic PDCH is
not switched back and the system does not perform half-rate/full-rate adjustment, queuing or preemption.
If the intra-cell handover times out, the system determines whether the priority of the PS
service is higher.
to the PCU.
Dynamic PDCH-to-TCH Conversion
 Factors such as the frequency band and concentric cell attribute are considered during
dynamic PDCH-to-TCH conversion.
 If the channel requested by the CS call is TCHH only and the TRX carrying the
dynamic PDCH to be converted does not support channel rate adjustment, the dynamic
PDCH is not converted to the TCH.
 The BSC should not assign the dynamic PDCH for the CS services.
Figure 3-8 shows the dynamic PDCH-to-TCH conversion procedure.

Figure 3-8 Dynamic PDCH-to-TCH conversion
 During the dynamic conversion process, the calls are queued. Therefore, if a call is placed in the queue
before the BSC sends a channel request message to the PCU, the call will not be released until the queue
timer expires.
 If there is no call in the queue when the PCU releases the PDCH, the BSC converts the dynamic PDCH
to the TCHF.
When TCHBUSYTHRESOPT (BSC6900, BSC6910) is set to OPEN, the BSC preferentially

converts a PDCH to TCHF, and then converts the TCHF to a TCHH. In this case,
LOADSTATYPE (BSC6900, BSC6910) must be set to Count dynamic PDCH(Occupy).
When TCHBUSYTHRESOPT (BSC6900, BSC6910) is set to OPEN and LOADSTATYPE
(BSC6900, BSC6910) is set to Count dynamic PDCH(Occupy), CS services may fail to
occupy a dynamic PDCH if DYNCHNPREEMPTLEV (BSC6900, BSC6910) is set to
LEVEL1(No preempt of CCHs) or LEVEL2(No preempt of service TCHF). As a result,
the KPIs of the CS services will be degraded.
3.4.1 Overview
The paging success rate decreases significantly during holidays or due to emergencies. When
the static multiple CCCH function is enabled, it is difficult to determine the number of static
CCCHs to be configured. If the number of configured static CCCHs is small, the paging
success rate remains low. If the number of configured static CCCHs is large, some TCHs are
wasted.
The GBFD-511503 Dynamic Multiple CCCH feature can be used to resolve this problem.
When the CCCH load is high, the TCHs on timeslots 2, 4, and 6 on the BCCH TRX are
dynamically converted to CCCHs to extend the Um interface capability. When the CCCH
load is low, the CCCHs on timeslots 2, 4, 6 are dynamically converted to TCHs to increase
the channel usage.
CCCHs include access grant channels (AGCHs), paging channels (PCHs), and random access
channels (RACHs). In the case of traffic burst, the Dynamic Multiple CCCH feature
increases the paging success rate, resolves the sharp increase in paging messages, improves
the operation and maintenance (O&M) efficiency, and simplifies the multiple CCCH
configuration.
After the Dynamic Multiple CCCH feature is enabled, the BTS calculates the CCCH load and
determines whether to add or delete CCCHs based on a specified threshold. If yes, the BTS
requests the BSC to add or delete CCCHs. The BSC adds or deletes one CCCH per request.
When a CCCH is added to a timeslot, the timeslot is chosen by the ascending order of
timeslot number. Timeslot 2 is filled before timeslot 4; timeslot 4 is filled before timeslot 6.
When a CCCH is deleted from a timeslot, the timeslot is determined by the descending order
of the timeslot number. Timeslot 6 is emptied before timeslot4; timeslot 4 is emptied before
timeslot 2.
Channel conversion on timeslots 2, 4, and 6 must be performed consecutively in ascending
order. For example, if channel version on timeslot 2 fails, channel conversion on timeslots 4
and 6 cannot proceed. After adding or deleting a CCCH, the BSC delivers a system
information message to an MS so that the MS listens to the timeslot carrying the allocated
CCCH.
To convert a TCH that has calling services, the calling services are handed over to another
TCH in the cell. For a common call, if the handover fails, call drops occur. For a VIP call or
an emergency call that must be guaranteed, if the handover fails, the call is reassigned to the
original channel and therefore call drops do not occur. In this case, a TCH cannot be
converted to a CCCH. The VIP calls can be configured by running the ADD VIPUSR or
RMV VIPUSR command. The emergency calls that must be guaranteed can be configured
using the EMCPRILV (BSC6900, BSC6910) parameter.
To convert a dynamic PDCH, the BSC sends the PCU a request to release this channel. If this
channel is successfully released, it is successfully converted to the CCCH. If this channel
fails to be released, the channel conversion fails.
After receiving a request from the BTS to delete a CCCH, the BSC converts the CCCH into a
TCH. In addition, the BSC reserves the received paging messages within a specified period,
preventing paging message loss caused by channel conversion.
After adding or deleting a CCCH, the BSC sends a System Information 3 (SI3) to notify the
MS to listen to the timeslot carrying the CCCH.
Dynamic CCCH conversion is determined by DynCCCHSwitch (BSC6900, BSC6910).
Dynamic CCCH conversion includes adding and deleting CCCHs dynamically. Figure 3-9
shows the dynamic CCCH conversion procedure.
Figure 3-9 Dynamic CCCH conversion procedure
3.4.2 Application Scenario
Huawei BSS device paging methods are classified into local area code (LAC) paging and
BSC paging.
After purchasing the Dynamic Multiple CCCH feature, you are advised to disable the
configured static broadcast channel (BCH) in a cell.
Multiple CCCHs refer to logical CCCHs on multiple timeslots. Extended CCCHs refer to the CCCHs except the
CCCHs on timeslot 0 on the BCCH TRX. For Huawei BSS devices, the channel type for extended CCCHs is
BCH, which is the same as the channel type of static CCCHs.
On the live network, if 70% of cells under an LAC or a BSC experience paging expiration
during peak hours, you are advised to enable this feature for all the cells under the LAC or
BSC.
If the number of delivered paging messages in a cell exceeds 160,000 per hour during peak
hours, you are advised to enable this feature for all the cells under the LAC or BSC that
serves this cell.
3.4.3 Adding CCCHs Dynamically
Within the period specified by DynCCCHLoadDuration (BSC6900, BSC6910), the BTS

measures the CCCH load once every second. If the CCCH load calculated by the BTS is
greater than DynCCCHLoadIncrThr (BSC6900, BSC6910), CCCH congestion occurs.
Channels on timeslots 2, 4, and 6 of the BCCH TRX are dynamically converted to CCCHs in
sequence. If the number of CCCHs plus one is greater than MaxDynCCCHNum (BSC6900,
BSC6910), channel conversion is not performed. Otherwise, the BTS sends the BSC a request
for applying for a CCCH.
3.4.4 Deleting CCCHs Dynamically
If the interval between two the interval between two consecutive CCCH additions is greater
than DynCCCHReduceInterval (BSC6900, BSC6910), the decision on whether deleting
CCCHs is not made. If the interval between two consecutive CCCH additions is greater than
DynCCCHReduceInterval (BSC6900, BSC6910), the decision on whether deleting CCCHs
is made.
Within the period specified by DynCCCHLoadDuration (BSC6900, BSC6910), the BTS
decides once every second whether the following condition is met: Buffer queue length of N
CCCHs < Maximum buffer queue length of (N – 1) CCCHs x DynCCCHLoadRedcThr
(BSC6900, BSC6910)
where N represents the number of CCCH timeslots. N is greater than 1. Maximum buffer
queue length of one CCCH = Number of paging groups x Number of buffered CCCHs in
each paging group + Allowed length of the AGCH transmission queue
If the preceding condition is met each time the BTS decides during the specified period, the
BTS determines whether to delete a CCCH based on the number of downlink messages
(including paging messages and immediate assignment messages) over the Abis interface and
the capability of transmitting messages (including paging messages and immediate
assignment messages) over the Um interface. If the BTS determines to delete a CCCH, it
sends the BSC a request for deleting a CCCH dynamically.
4 Related Features
4.1 GBFD-113001 SDCCH Dynamic Adjustment
Prerequisite Features
None.
Mutually Exclusive Features
None.
Impacted Features
None.
4.2 GBFD-113402 Dynamic Adjustment Between FR and HR
Feature ID Feature Name Description
GBFD-113401 Half Rate Speech The dynamic TCH HR/FR conversion

during channel allocation depends on
this feature.
GBFD-115504 AMR FR/HR Dynamic The dynamic TCH HR/FR conversion

Adjustment during a call depends on either of the
features.
GBFD-510501 HUAWEI II Handover
None.
Impacted Features
GBFD-200201 1.2 MHz Networking for The AMR FR/HR Dynamic Adjustment
BCCH TRXs feature (controlled by the
HALFRATEREPACKINGSWITCH
(BSC6900, BSC6910) parameter) and the
channel group handover function in the
1.2 MHz Networking for BCCH TRXs
feature are mutually impacted. Ping-
pong handovers will occur when they
are both enabled. You are not advised to
enable AMR FR/HR Dynamic
Adjustment when 1.2 MHz Networking
for BCCH TRXs is enabled.
4.3 GBFD-511503 Dynamic Multiple CCCH
None.
None.
Impacted Features
GBFD-200201 1.2 MHz Networking for When 1.2 MHz Networking for BCCH
BCCH TRXs TRXs is enabled, the transmit power of
TS4 on the BCCH TRX will be
decreased. You are not advised to
configure the BCCH on TS4.
5 Network Impact
5.1 Dynamic SDCCH Conversion
The Dynamic SDCCH Conversion feature increases network signaling traffic and prevents
SDCCH congestion due to signaling burst. Examples of SDCCH congestion due to signaling
burst are abrupt cell location updates at the border of location areas and group sending of
short messages.
After a TCH is successfully converted to SDCCH, the received signal level (RSL) load
increases on this channel.
This feature slightly increases the number of handovers.

5.2 Dynamic TCH HR/FR Conversion
When the traffic in a cell is heavy, the TCH HR/FR conversion enables the BSC to allocate
TCHHs to MSs or convert the TCHFs to TCHHs. This increases the network capacity. When
the traffic in a cell is light, the TCH HR/FR conversion enables the BSC to allocate TCHFs to
MSs or convert TCHHs to TCHFs. This improves the voice quality.
The TCH HR/FR conversion prolongs the assignment duration.

In addition, the TCH HR/FR conversion slightly increases the number of handovers and
thereby affects the voice quality.
When a cell has heavy CS services, they can occupy PDCHs, improving the CS service
capacity. When CS services are light in a cell, PS services can occupy TCHs, improving the
PS service throughput.
The PS service rate may decrease or call drops may occur because some PDCHs are occupied
by CS services.
The Dynamic Multiple CCCH feature eliminates the avalanche effect caused by paging burst.
Compared with the static multiple CCCHs, this feature reduces the operation and
maintenance cost and improves the channel usage.
In addition, this feature decreases the number of paging timeouts. When receiving a large
number of paging messages, the BSC automatically distributes these messages based on the
CCCH load to balance load on CCCHs. This decreases the number of paging timeouts and
minimizes the effect caused by paging or PS traffic burst on the paging efficiency.
If the channel to be converted is carrying a PS call, a direct channel preemption is initiated.

This may cause the PS call to drop.
Static PDCHs may not be configured in timeslot 6 and PDCH continuity is affected.
If the channel to be converted is carrying a CS call, an intra-cell handover is initiated. This
affects the mean opinion score (MOS) of this CS call.
Table 5-1, Table 5-2, and Table 5-3 show the impacts caused by enabling the Dynamic Multiple
CCCH feature.
Table 5-1 Counters on the core network side
Counter Impact
Paging success rate Slightly increases or decreases.

Enabling the Dynamic Multiple CCCH
feature disables the static BCH if any. If
DynCCCHLoadIncrThr or
DynCCCHLoadDuration is set to a large
value, some paging messages may be
discarded during the triggering of dynamic
channel conversion. As a result, the paging
success rate slightly decreases after the
static BCH is disabled.
In other scenarios, this feature increases the
paging capability over the Um interface.
Therefore, the paging success rate
increases.
The paging success rate is not a standard counter name on the CN side. It is named based on its meaning. For
the specific counter name, see the counter documentation provided by the device provider.
Table 5-2 BSS counters

Type Counter Description Counter Name Impact
Number of paging Number of Expiries of CELL.CIRCUIT.PCH. Slightly increases or

timeouts the Paging for CS EXP decreases.
Services on the PCH The cause is the
same as that
Number of Expiries of CELL.PACUIT.PCH.E described in Table 5-1.
the Paging for PS XP
Services on the PCH
CS congestion rate Congestion Rate on CELL.KPI.TCH.CON Slightly increases or

TCH (All Channels GESTION.RATE decreases.
Busy) Enabling the Dynamic
Multiple CCCH
feature disables the
static BCH if any.
This increases the
resource usage and
decreases the
congestion rate. If no
static BCH is
configured, triggering
CCCH channel
adjustment during
peak hours occupies
one or more service
channels. This slightly
increases the PS
congestion rate.
CS call drop rate Call Drop Rate on CELL.RATE.TCH.CA Remains unchanged

TCH per cell LL.DROP.INCLUDE. or slightly increases.
(including Handover) HO During a TCH-to-
CCCH conversion, if
the TCH has been
occupied by a CS
call, the BSC
attempts to hand over
the CS call to another
channel first. If the
handover fails, the
BSC directly
preempts the TCH.
This slightly increases
the call drop rate.
PS service Average Throughput UP.GPRS.RLC.AVG. Increases or slightly

throughput of Uplink GPRS RLC THRPUT.RATE decreases.
Enabling the Dynamic
Average Throughput DOWN.RLC.AVG.TH Multiple CCCH
of Downlink GPRS RPUT.RATE feature deletes the
RLC static BCH if any.
This increases the
Average Throughput UP.EGPRS.RLC.AV
Type Counter Description Counter Name Impact
of Uplink EGPRS G.THRPUT.RATE

RLC
Average Throughput DOWN.EGPRS.RLC.

of Downlink EGPRS AVG.THRPUT.RATE
RLC
resource usage and
the values of these
counters. If no static
BCH is configured,
triggering CCCH
channel adjustment
Table 5-3 BSS KPIs
Type KPI Impact
Uplink/Downlink Uplink TBF Congestion Rate Decreases or slightly

GPRS/EGPRS TBF increases.
congestion rate Downlink TBF Congestion Enabling the Dynamic
Rate Multiple CCCH feature
deletes the static BCH if any.
Uplink EGPRS TBF This increases the resource
congestion rate usage and decreases the
values of these KPIs.
Downlink EGPRS TBF
If no static BCH is
congestion rate
configured, triggering CCCH
channel adjustment during
peak hours occupies one or
more service channels. This
slightly increases the PS
congestion rate or keep the
rate unchanged.
Uplink/Downlink Uplink GPRS TBF Call Drop Remains unchanged or

GPRS/EGPRS TBF call drop Rate slightly increases.
rate During the PDCH-to-CCCH
Downlink GPRS TBF Call conversion, the PCU
Drop Rate releases the PDCH first, and
then converts the PDCH to a
Uplink EGPRS TBF Call CCCH. If the PDCH is used
Drop Rate by a TBF, the TBF release
procedure is triggered. This
Downlink EGPRS TBF Call slightly increases the TBF
Drop Rate call drop rate.
TBF establishment success Downlink TBF Establishment Remains unchanged or

rate Success Rate slightly decreases. During the
PDCH-to-CCCH conversion,
Uplink TBF Establishment the PCU releases the PDCH
Success Rate first, and then converts the
PDCH to a CCCH. This
Type KPI Impact
decreases the TBF
6.1 When to Use Dynamic Channel Conversion
You are advised to enable the Dynamic SDCCH Conversion feature. To relieve SDCCH
congestion, configure certain static SDCCHs in the cells enabled with this feature
You are advised to set DIFFBANDSDCCHDYNADJ (BSC6900, BSC6910) to YES(Yes) if:
 The cell is a co-BCCH cell.
 Some TRXs for a cell whose BCCH TRX is configured on the P-GSM frequency
band work on the E-GSM or R-GSM frequency band.
 Only a few TRXs work on the frequency bands compatible with the BCCH frequency
band.
During immediate assignment, the BSC cannot determine whether an MS supports a specific
frequency band. If an MS does not support a frequency band that is incompatible with the
BCCH frequency band but the BSC allocates an SDCCH on such a frequency band to the
MS, the MS fails to access the network.
For non-AMR calls, if the cell is a common cell, set TCHBUSYTHRES (BSC6900, BSC6910)
based on your individual needs; If the cell is a concentric cell and
HRIUOLDRATESELALLOW (BSC6900, BSC6910) is set to YES(Yes), set
TCHTRICBUSYOVERLAYTHR (BSC6900, BSC6910) and
TCHTRIBUSYUNDERLAYTHR (BSC6900, BSC6910) based on your individual needs. For
AMR calls, in common and concentric cells, set AMRTCHHPRIORLOAD (BSC6900,
BSC6910) based on your individual needs.
If TCHHs are assigned preferentially, set JudgeRxLevWhenAssignHr (BSC6900,

BSC6910) and MinRxLevWhenAssignHr (BSC6900, BSC6910) appropriately to avoid too
low signal level.
In channel assignment algorithms, the BSC determines whether to assign TCHHs or TCHFs
based on the network traffic volume. If the channel usage exceeds TCHBUSYTHRES
(BSC6900, BSC6910), the traffic volume of the current network is high. If the traffic volume of
the current network is high, TCHHs are assigned preferentially. If the traffic volume of the
current network is low, TCHFs are assigned preferentially. If
JudgeRxLevWhenAssignHr (BSC6900, BSC6910) is set to ON(On), TCHHs are assigned
preferentially when the channel usage exceeds TCHBUSYTHRES (BSC6900, BSC6910) and
the receive signal level is greater than or equal to MinRxLevWhenAssignHr (BSC6900,
BSC6910). Otherwise, TCHFs are assigned preferentially.
It is recommended that the TCH HR/FR conversion be used in cells with heavy traffic and a
high proportion of half-rate channels.
Before enabling the Dynamic PDCH Conversion feature in a cell, you are advised to
configure certain static PDCHs in the cell.
None
Before enabling the Dynamic Multiple CCCH feature, check whether all SDCCHs in the cell
are configured in timeslots 2, 4, and 6 of the BCCH TRX. If yes, do not enable this feature. If
no, obtain the paging success rate in the cell. If the paging success rate is low, enable this
feature.
6.3 Planning
If combined BCCH or BCCH + CBCH is configured in timeslot 0 of the BCCH TRX in a

cell, the Dynamic Multiple CCCH feature cannot be enabled.
The following rules are applicable to all the channels involved in baseband FH, the channels
configured as SDCCHs or static PDCHs, and the channels reserved for VIP users:
 If MaxDynCCCHNum (BSC6900, BSC6910) is set to 1, these channels cannot be
configured in timeslot 2. Otherwise, the Dynamic Multiple CCCH feature cannot be
enabled.
configured in timeslot 2 or timeslot 4. Otherwise, the Dynamic Multiple CCCH feature
cannot be enabled.
configured in timeslot 2, timeslot 4, or timeslot 6. Otherwise, the Dynamic Multiple
CCCH feature cannot be enabled.
You are advised to set MaxDynCCCHNum (BSC6900, BSC6910) to the same value as the
number of static CCCHs configured in the cell before this feature is enabled.
If there is no static CCCH in the cell and paging expiration or deletion occurs in 70% of cells
under the LAC where this cell is located, you are advised to set MaxDynCCCHNum
(BSC6900, BSC6910) to 1 or a larger value for all cells under the LAC.
In typical scenarios, the theoretical capability of sending messages over the Um interface per
BCCH is calculated using the following formula:
(9 - BSAGBLKSRES (BSC6900, BSC6910))/0.235 x 2.74 (Unit: integer/s)
The typical scenarios must meet the following requirements:
 The first paging is based on the TMSI, while the second paging is based on the IMSI.
 The paging service distribution model is normal. For example, the one-hour model meets the position
distribution requirement, but not the M2M. A large number of paging messages are sent within 10s during
one hour.
Assume that BSAGBLKSRES (BSC6900, BSC6910) is set to 1, the theoretical capability of

sending messages over the Um interface per BCCH is 334800 per hour, which is calculated
using the following formula:
(9 – 1)/0.235 x 2.74 = 93 (integer/s)
The actual capability, usually, is about 50% to 60% of the theoretical capability. If the
number of paging messages sent during peak hours in a cell reaches 160,000 per hour
(334800 X 50%), set MaxDynCCCHNum (BSC6900, BSC6910) to 1. If the number of paging
messages sent during peak hours in a cell reaches 160,000 x N per hour, set
MaxDynCCCHNum (BSC6900, BSC6910) to N.
Setting MaxDynCCCHNum (BSC6900, BSC6910) to a larger value improves the message
transmission capability over the Um interface. To prevent message congestion over the Abis
interface, increase the RSL bandwidth for the BCCH TRX and set MainBMPMode
(BSC6900, BSC6910) as follows:
Temporary mobile subscriber identity (TMSI) paging: When MaxDynCCCHNum
(BSC6900, BSC6910) plus the number of static BCHs is equal to 1, 2, or 3, you are advised to
set MainBMPMode (BSC6900, BSC6910) to MODE2_1, MODE1_1, or MODE1_1,
respectively.
International mobile subscriber identity (IMSI) paging: When MaxDynCCCHNum
(BSC6900, BSC6910) plus the number of static BCHs is equal to 1, 2, or 3, you are advised to
set MainBMPMode (BSC6900, BSC6910) to MODE4_1, MODE2_1, or MODE1_1,
respectively.
6.4 Overall Deployment Procedure
None
6.5 Deploying Dynamic SDCCH Conversion

Aspect Requirement
Related features See 4 Related Features.
BSC None
BTS None
GSM networking None
MS None
MSC None
Aspect Requirement
License None
Others None
6.5.2 Activation
Using MML Commands

1. Run the SET GCELLBASICPARA command with SDCCH Dynamic Allocation
Allowed and Dynamic PDCH Conversion to SDCCH Allowed set to YES(Yes).
2. Run the SET GCELLCHMGBASIC command with Idle SDCCH Threshold, Cell
SDCCH Channel Maximum, TCH Minimum Recovery Time, Num of TSs
Convertible to SDCCHs per TRX, and Number of TSs Convertible to SDCCHs on
BCCH TRX set to appropriate values.
When TCHs on the BCCH frequency band are insufficient, set Dynamically Adjust Inter-Freq Band
SDCCH to YES(Yes).
3. Run the SET GCELLPSCHM command with Maximum Rate Threshold of

PDCHs in a Cell and Reservation Threshold of Dynamic Channel Conversion set to
appropriate values based on the network planning.
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=1, SDDYN=YES,

PDCH2SDEN=YES;
SET GCELLCHMGBASIC: IDTYPE=BYID, CELLID=1, IDLESDTHRES=17,
CELLMAXSD=100, MINRESTIMETCH=60, SDCCHDYNADJTSNUM=8,
MainBcchSdcchNum=8;
SET GCELLPSCHM: IDTYPE=BYID, CELLID=1, MAXPDCHRATE=100,
DYNCHTRANRESLEV=0, POWTUNIT=W;
Using the CME
When configuring the Dynamic SDCCH Adjustment feature on the CME, you must perform a single
configuration first, and then perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter. You are
advised to perform batch modifications before logging out of the parameter setting interface.
1. Configure a single object on the CME. (CME single configuration)

Set parameters on the CME configuration interface according to the operation sequence
described in Table 6-2.
2. (Optional) Modify objects in batches on the CME. (CME batch modification center)
To modify objects, such as BSCs, BTSs, cells, and TRXs, in batches, click the icon on
the CME configuration interface to start the batch modification wizard.
For instructions on how to perform a batch modification, click on the wizard

interface to obtain online help.
Table 6-2 Configuring parameters on the CME
SN Managed NE Parameter Parameter ID Configurable in

Object (MO) Name CME Batch
Modification
Center
1 GCELLBASIC BSC6900/BS SDCCH SDDYN Yes

PARA C6910 Dynamic
Allocation
Allowed
BSC6900/BS Dynamic PDCH2SDE

C6910 PDCH N
Conversion to
SDCCH
Allowed
2 GCELLCHM BSC6900/BS Idle SDCCH IDLESDTHR Yes

GBASIC C6910 Threshold ES
BSC6900/BS Cell SDCCH CELLMAXS

C6910 Channel D
Maximum
BSC6900/BS TCH MINRESTIM

C6910 Minimum ETCH
Recovery
Time
BSC6900/BS Num of TSs SDCCHDYN

C6910 Convertible to ADJTSNUM
SDCCHs per
TRX
BSC6900/BS Number of MainBcchSd

C6910 TSs cchNum
Convertible to
SDCCHs on
BCCH TRX
3 GCELLPSCH BSC6900/BS Maximum MAXPDCH Yes

M C6910 Rate RATE
Threshold of
SN Managed NE Parameter Parameter ID Configurable in
Object (MO) Name CME Batch
Modification
Center
PDCHs in a
Cell
BSC6900/BS Reservation DYNCHTRA

C6910 Threshold of NRESLEV
Dynamic
Channel
Conversion
Monitor the channel status by referring to section "Monitoring Channel Status" in BSC6900 GSM LMT User
Guide or BSC6910 GSM LMT User Guide.
Two TRXs are configured. For the BCCH TRX, timeslot 0 is configured as the BCCH, timeslot 1 is configured
as the SDCCH, and timeslots 2 thorough 7 are configured TCHFs whose PDCH Channel Priority Type is set
to EGPRSNORCH(EGPRS Normal Channel). For the other TRX, timeslots 1 through 7 are blocked, and
only timeslot 0 is not blocked.
This section describes configuration only to enable this feature to take effect as soon as possible. Commercial
networks must be configured according to the network plan. After this feature is verified, the configuration must
be restored to that before the verification.
1. On the BSC LMT, run the SET GCELLCHMGBASIC command with its
parameters set as follows:
 Set Idle SDCCH Threshold to 17.
 Set Cell SDCCH Channel Maximum to 100.
 Set TCH Minimum Recovery Time to 60.
 Set Num of TSs Convertible to SDCCHs per TRX to 8.
 Set Number of TSs Convertible to SDCCHs on BCCH TRX to 8.
2. Run the SET GCELLPSCHM command with Maximum Rate Threshold of
PDCHs in a Cell set to 100 and Reservation Threshold of Dynamic Channel
Conversion set to 0.
3. Use an MS to initiate a CS call in the cell.
Expected result: A TCH is converted into an SDCCH.
4. Release the CS call. Then, use multiple MSs to simultaneously initiate PS services in
the cell.
Expected result: All full-rate traffic channels (TCHFs) on the BCCH TRX are converted
into PDCHs.
5. Use an MS to initiate a CS call again in the cell.
Expected result: A TCH is converted into an SDCCH, and a PDCH is simultaneously
converted into a TCH. Alternatively, a TCH is occupied by a CS call, and a PDCH is
simultaneously converted into an SDCCH.
6. Enable the cell to remain in the idle state for two minutes. The minimum time
required for converting SDCCHs back to TCHs is 120 seconds.
Expected result: One of the two SDCCHs is converted back to a TCH.
6.5.4 Deactivation
Using MML Commands
On the BSC LMT, run the SET GCELLBASICPARA command with SDCCH Dynamic
Allocation Allowed and Dynamic PDCH Conversion to SDCCH Allowed set to NO(No).
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=1, SDDYN=NO, PDCH2SDEN=NO;
Using the CME

6.6 Deploying Dynamic TCH HRFR Conversion

Aspect Requirement
BSC None
BTS None
GSM networking None
MS None
MSC None
Feature Parameter Description. For details about license items, see
License Control Item Description.
Others None
6.6.2.1 Data Preparation
Table 6-4 lists the data to be prepared for deploying this feature.
Table 6-4 Data preparation
Paramete Paramet NE Setting Notes Data
r Name er ID Source
TCH TCHAJ BSC6900/B Set this parameter to YES(Yes). Network

Rate FLAG SC6910 plan
Adjust
Allow
TCH TCHBU BSC6900/B The default value is recommended. Network

Traffic SYTHR SC6910 To increase the proportion of MSs on plan
Busy ES TCHHs, set this parameter to a small value.
Threshol To reduce the proportion of MSs on TCHHs,
d set this parameter to a large value.
Load of HRIUO BSC6900/B This parameter is required for concentric Network

UL-OL LDRAT SC6910 cells, including co-BCCH cells. plan
Cells ESELA
Rate LLOW
Select
Allowed
Tch TCHTRI BSC6900/B The default value is recommended. Network

Traffic CBUSY SC6910 To increase the proportion of MSs on TCHHs plan
Busy OVERL in the overlaid subcell, set this parameter to a
Overlay AYTHR small value. To reduce the proportion of MSs
Threshol on TCHHs in the overlaid subcell, set this
d parameter to a large value.
Tch TCHTRI BSC6900/B The default value is recommended. Network

Traffic BUSYU SC6910 To increase the proportion of MSs on TCHHs plan
Busy NDERL in the underlaid subcell, set this parameter to
Underlay AYTHR a small value. To reduce the proportion of
Threshol MSs on TCHHs in the underlaid subcell, set
d this parameter to a large value.
AMR AMRTC BSC6900/B The default value is recommended. Network

TCH/H HHPRI SC6910 This parameter is required if the cell enables plan
Prior ORLOA the AMR function. To increase the proportion
Cell D of MSs on AMR TCHHs, set this parameter
Load to a small value. To reduce the proportion of
Threshol MSs on AMR TCHHs, set this parameter to a
d large value.
NOTE:
 This parameter is valid only if
AMRTCHHPRIORALLOW (BSC6900,
BSC6910) is set to ON(On).
 This parameter is invalid for concentric cells
if AMRLOADOPTEN (BSC6900, BSC6910) and
HRIUOLDRATESELALLOW (BSC6900,
BSC6910) are set to YES(Yes) at the same time.
AMR AMRLO BSC6900/B You are advised to set this parameter to Network
Load ADOPT SC6910 YES(Yes) for a concentric cell. plan
r Name er ID Source
Calculati EN For AMR calls in a concentric cell, set this

on parameter to YES(Yes) if the proportion of
Optimiza MSs on TCHHs needs to be accurately
tion controlled in the overlaid and underlaid
subcells.
NOTE:
This parameter is valid only if
AMRTCHHPRIORALLOW (BSC6900, BSC6910) is
set to ON(On).
Threshol INNAM BSC6900/B The default value is recommended. Network

d for OL RTCHH SC6910 To increase the proportion of MSs on TCHHs plan
Load PRIOR in the overlaid subcell for AMR calls, set this
with LOAD parameter to a small value. To reduce the
AMR HR proportion of MSs on TCHHs in the overlaid
Preferre subcell, set this parameter to a large value.
d NOTE:
This parameter is valid only if AMRLOADOPTEN
(BSC6900, BSC6910) and
BSC6910) are set to YES(Yes), and
set to ON(On).
Threshol OUTAM BSC6900/B The default value is recommended. Network

d for UL RTCHH SC6910 To increase the proportion of MSs on TCHHs plan
Load PRIOR in the underlaid subcell for AMR calls, set this
with LOAD parameter to a small value. To reduce the
AMR HR proportion of MSs on TCHHs in the underlaid
Preferre subcell, set this parameter to a large value.
d NOTE:
This parameter is valid only if AMRLOADOPTEN
(BSC6900, BSC6910) and
BSC6910) are set to YES(Yes), and
set to ON(On).
TCHH JudgeR BSC6900/B You are advised to set this parameter to Network
Allocatio xLevWh SC6910 OFF(Off). plan
n enAssig If this parameter is set to ON(On), you need
Consider nHr to consider the signal level when assigning
ing the TCHHs. If the signal level is too low, the
Signal TCHFs are assigned. If this parameter is set
Level to OFF(Off), the signal level is not
considered.
Level MinRxL BSC6900/B The default value is recommended. Network

Threshol evWhen SC6910 This parameter specifies the lowest signal plan
r Name er ID Source
d for Assign level threshold for assigning AMR calls the

TCHH Hr TCHHs. The TCHFs are assigned to MSs if
Allocatio the signal level is lower than the parameter
n value, and otherwise the TCHHs are
assigned to MSs.
This parameter is valid only if
JudgeRxLevWhenAssignHr (BSC6900,
BSC6910) is set to ON(On).
You are advised to set this parameter to a
value smaller than the maximum transmit
power of TRXs in a cell minus the value of
AMRFULLTOHALFHOPATHTHRESH
(BSC6900, BSC6910).
For non-AMR calls, the decision principle is
as follows: If
NOAMRFULLTOHALFHOALLOW (BSC6900,
BSC6910) is set to NO(No), TCHFs are
preferentially assigned if the RX signal level
is lower than the parameter value plus 5.
Otherwise, TCHHs are preferentially
assigned. If
NOAMRFULLTOHALFHOALLOW (BSC6900,
BSC6910) is set to YES(Yes), TCHFs are
preferentially assigned if the RX signal level
is lower than the value calculated using the
following formula: Value of this parameter +
AMRFULLTOHALFHOPATHTHRESH
(BSC6900, BSC6910) –
NOAMRFULLTOHALFHOPATHTHRESH
(BSC6900, BSC6910) Otherwise, TCHHs are
preferentially assigned.
6.6.2.2 Activation
Using MML Commands

1. Run the SET GCELLCHMGAD command to set the threshold for dynamic
adjustment between TCHHs and TCHFs.
 For non-AMR calls in a common cell, set TCH Traffic Busy Threshold to an
appropriate value based on the actual requirement. For non-AMR calls in a concentric
cell whose Load of UL-OL Cells Rate Select Allowed is set to YES(Yes), set Tch
Traffic Busy Overlay Threshold and Tch Traffic Busy Underlay Threshold to
appropriate values.
 For AMR calls, set AMR TCH/H Prior Allowed to ON(On), and set other
parameters as follows:
 For common cells, set AMR TCH/H Prior Cell Load Threshold to
an appropriate value based on the actual requirement.
 For concentric cells, if either Load of UL-OL Cells Rate Select
Allowed or AMR Load Calculation Optimization is set to NO(No), set AMR
TCH/H Prior Cell Load Threshold to an appropriate value based on the actual
requirement. If Load of UL-OL Cells Rate Select Allowed and AMR Load
Calculation Optimization are both set to YES(Yes), set Threshold for OL Load
with AMR HR Preferred for overlaid subcells and Threshold for UL Load with
AMR HR Preferred for underlaid subcells to appropriate values.
 When the BSC preferentially assigns TCHHs, and TCHH Allocation
Considering Signal Level is set to ON(On), the BSC takes into account the RX
signal level in addition to the traffic volume. If the RX signal level is less than the
value for Level Threshold for TCHH Allocation, TCHFs are preferentially assigned.
If the RX signal level is greater than or equal to the value for Level Threshold for
TCHH Allocation, TCHHs are preferentially assigned.
When an MS is being connected to the target cell during an inter-cell handover, the TCHH Allocation
Considering Signal Level parameter takes effect only if all the following conditions are met:
 The A interface uses non-IP transmission.
 The TFO feature has been disabled.
 The Speech Ver Change Optimize in Handover parameter has been set to OFF(Off).
2. Run the SET GTRXDEV command for each TRX you want to configure. In this
step, set TCH Rate Adjust Allow of the TRX to YES(Yes).
SET GTRXDEV: TRXID=0, TCHAJFLAG=YES;

SET GCELLCHMGAD: IDTYPE=BYID, CELLID=0, TCHBUSYTHRES=60,
JudgeRxLevWhenAssignHr=ON, MinRxLevWhenAssignHr=15;
Using the CME (Method 1)
When configuring the Dynamic Adjustment Between FR and HR feature on the CME, you must perform a
single configuration first, and then perform batch modifications if required.


SN Managed NE Parameter Parameter ID Configurable

Object (MO) Name in CME Batch
Modification
Center
1 GTRXDEV BSC6900/BS TCH Rate TCHAJFLAG Yes

C6910 Adjust Allow
2 GCELLCHM BSC6900/BS TCH Traffic TCHBUSYTH Yes

GAD C6910 Busy RES
Threshold
BSC6900/BS Load of UL- HRIUOLDRA

C6910 OL Cells Rate TESELALLO
Select W
Allowed
BSC6900/BS Tch Traffic TCHTRICBU

C6910 Busy Overlay SYOVERLAY
Threshold THR
BSC6900/BS Tch Traffic TCHTRIBUS

C6910 Busy YUNDERLA
Underlay YTHR
Threshold
BSC6900/BS AMR TCH/H AMRTCHHP

C6910 Prior Cell RIORLOAD
Load
Threshold
BSC6900/BS AMR Load AMRLOADO

C6910 Calculation PTEN
Optimization
BSC6900/BS Threshold for INNAMRTCH

C6910 OL Load with HPRIORLOA
AMR HR D
Preferred
BSC6900/BS Threshold for OUTAMRTC

C6910 UL Load with HHPRIORLO
Modification
Center
AMR HR AD
Preferred
BSC6900/BS TCHH JudgeRxLev

C6910 Allocation WhenAssign
Considering Hr
Signal Level
BSC6900/BS Level MinRxLevW

C6910 Threshold for henAssignH
TCHH r
Allocation
This feature can be batch activated using 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.
Assume that non-AMR calls are performed in a common cell. Only the traffic volume,
instead of the RX signal level, is considered in assignment of TCHHs. The observation
procedure is as follows:
1. Monitor channel status.
2. On the BSC LMT, run the SET GCELLCHMGAD command to specify the
corresponding cell. In this step, set TCH Traffic Busy Threshold to 0 to ensure that
new calls are preferentially assigned TCHHs.
3. Use an MS to initiate a call in the cell.
Expected result: The call is successfully initiated, and the communication is normal. A
TCHF is converted into two TCHHs and are occupied by MSs.
4. Terminate the call.
Expected result: The two TCHHs are not converted into a TCHF.
5. Run the SET GTRXCHANADMSTAT command to block all TCHFs in the cell. In
this step, set Administrative State to Lock(Lock).
6. Run the SET GCELLCHMGAD command with TCH Traffic Busy Threshold set
to 100 to ensure that new calls are preferentially assigned TCHFs.
In 6, if the calling party and the called party camp on the same cell, reserve a TCHF to ensure successful
setup of the call.
Expected result: The call is successfully initiated, and the communication is normal. The
MS occupies a TCHF.
Assume that non-AMR calls are performed in a common cell. The traffic volume and RX
signal level are considered in assignment of TCHHs. The observation procedure is as follows:
2. Run the SET GCELLCHMGAD command to specify the corresponding cell. In this
step, set TCH Traffic Busy Threshold and Level Threshold for TCHH Allocation to
0.
MS occupies a TCHH.
4. Terminate the call.
Expected result: The two TCHHs are not converted into a TCHF.
5. Run the SET GCELLCHMGAD command with Level Threshold for TCHH
Allocation of the corresponding cell set to 63.
MS occupies a TCHF.
Using MML Commands
On the BSC LMT, run the SET GTRXDEV command for each TRX you have configured.
In this step, set TCH Rate Adjust Allow of the TRX to NO(No).
SET GTRXDEV: TRXID=0, TCHAJFLAG=NO;

Using the CME
The method of feature deactivation using the CME is the same as that of feature activation
using the CME. For detailed operations, see Using the CME (Method 1) and Using the CME (Method
2).
6.6.3.1 Activation
Using MML Commands (Handover Algorithm I)

1. Run the BSC MML command SET GCELLHOBASIC with Intracell F-H HO
Allowed set to HOBASECAPANDQUAL, Current HO Control Algorithm set to
HOALGORITHM1, and both AMR F-H Ho Allowed and Non-AMR F-H Ho
Allowed set to YES(Yes).
2. Configure FR/HR call conversion.
 Run the BSC MML command SET GCELLCCACCESS with
FULL_RATE_VER1(Full-rate VER 1), FULL_RATE_VER2(Full-rate VER 2),
FULL_RATE_VER3(Full-rate VER 3), HALF_RATE_VER1(Half-rate VER 1),
HALF_RATE_VER3(Half-rate VER 3), and FULL_RATE_VER5(Full-rate VER
5) selected under Speech Version.
MML Command Examples (Handover Algorithm I)
//Activating Dynamic HR/FR Adaptation

SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0,
HOCTRLSWITCH=HOALGORITHM1,
INTRACELLFHHOEN=HOBASECAPANDQUAL,
AMRFULLTOHALFHOALLOW=YES, NOAMRFULLTOHALFHOALLOW=YES;
SET GCELLCCACCESS: IDTYPE=BYID, CELLID=0,
VOICEVER=FULL_RATE_VER1-1&FULL_RATE_VER2-1&FULL_RATE_VER3-
1&HALF_RATE_VER1-1&HALF_RATE_VER3-1&FULL_RATE_VER5-1;
Using MML Commands (Handover Algorithm II)

1. Run the SET GCELLHOBASIC command with its parameters set as follows:
Set Intracell HO Allowed to YES(Yes).
Set Current HO Control Algorithm to HOALGORITHM2(Handover algorithm II).
Set both AMR F-H Ho Allowed and Non-AMR F-H Ho Allowed to YES(Yes).
2. Configure FR/HR call conversion.
 Run the SET GCELLCCACCESS command with
FULL_RATE_VER1(Full-rate VER 1), FULL_RATE_VER2(Full-rate VER 2),
FULL_RATE_VER3(Full-rate VER 3), HALF_RATE_VER1(Half-rate VER 1),
HALF_RATE_VER3(Half-rate VER 3), and FULL_RATE_VER5(Full-rate VER
5) selected under Speech Version.
MML Command Examples (Handover Algorithm II)
//Activating Dynamic HR/FR Adaptation

HOCTRLSWITCH=HOALGORITHM2, INTRACELLHOEN=YES,
AMRFULLTOHALFHOALLOW=YES, NOAMRFULLTOHALFHOALLOW=YES;
SET GCELLCCACCESS: IDTYPE=BYID, CELLID=0,
VOICEVER=FULL_RATE_VER1-1&FULL_RATE_VER2-1&FULL_RATE_VER3-
1&HALF_RATE_VER1-1&HALF_RATE_VER3-1&FULL_RATE_VER5-1;
When configuring the Dynamic HR/FR Adaptation feature on the CME, you must perform a single
configuration first, and then perform batch modifications if required.


SN MO NE Paramete Parameter ID Configurable in

r Name CME Batch
Modification
Center
1 GCELLHOBA BSC6900/BS Intracell INTRACELLHOEN Yes

SIC C6910 HO
Allowed
Current HOCTRLSWITCH
HO
Control
Algorith
m
AMR F- AMRFULLTOHALFHO
H Ho ALLOW
Allowed
Non- NOAMRFULLTOHALF
AMR F- HOALLOW
H Ho
Allowed
2 GCELLCCAC BSC6900/BS Speech VOICEVER Yes

CESS C6910 Version
NOTE:
r Name CME Batch
Modification
Center
Configure this
MO to convert
FR calls to HR
calls.
3 GCELLHOBA BSC6900/BS AMR F- AMRFULLTOHALFHO Yes

SIC C6910 H Ho QUALTHRESH
NOTE: Qual.
Threshol
Configure this
d
MO to convert
FR calls to HR
calls. Non- NOAMRFULLTOHALF
AMR F- HOPATHTHRESH
H Ho
Pathloss
Threshol
d
Non- NOAMRFULLTOHALF
AMR F- HOATCBTHRESH
H Ho
ATCB
Threshol
d
4 GCELLCCAC BSC6900/BS Speech VOICEVER Yes

CESS C6910 Version
NOTE:
Configure this
MO to convert
HR calls to FR
calls.
5 GCELLCHMG BSC6900/BS AMR AMRTCHHPRIORALLO Yes

AD C6910 TCH/H W
NOTE: Prior
Allowed
Configure this
MO to convert
AMR AMRTCHHPRIORLOAD
HR calls to FR
calls. TCH/H
Prior
Cell
Load
Threshol
d
TCH TCHBUSYTHRES
Traffic
r Name CME Batch
Modification
Center
Busy
Threshol
d
6 GCELLHOBA BSC6900/BS AMR H- AMRHALFTOFULLHOT Yes

SIC C6910 F Traffic HRESH
NOTE: Threshol
d
Configure this
MO to convert
AMR H- AMRHALFTOFULLHOP
HR calls to FR
calls. F Ho ATHTHRESH
Pathloss
Threshol
d
Non- NOAMRHALFTOFULL
AMR H- HOATCBTHRESH
F Ho
ATCB
Threshol
d
This feature can be batch activated using 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.
Converting FR calls to HR calls

1. Trace BSSAP messages over the A interface and RSL messages over the Abis
interface in a cell.
2. Use an MS to make a call in the cell.
3. View the BSSAP messages traced over the A interface and the RSL messages traced
over the Abis interface.
Expected result: The call has been set up and the voice quality is good. During the call
setup, the FAMR speech version is used. During the call, the speech version changes to
HAMR. The Handover Detection message is traced over the Abis interface and the
Handover Complete message is traced over the Um interface.
If Assignment Procedure in Intra-Cell HO Allowed in the SET GCELLSOFT command is set to
YES(Yes), the Assignment Complete message can be traced. If this parameter is set to NO(No), the
Handover Complete message can be traced.
Converting HR calls to FR calls

1. Trace BSSAP messages over the A interface and RSL messages over the Abis
interface in a cell.
2. Use an MS to make a call in the cell.
3. View the BSSAP messages traced over the A interface and the RSL messages traced
over the Abis interface.
Expected result: The call has been set up and the voice quality is good. During the call
setup, the HAMR speech version is used. During the call, the speech version changes to
FAMR. The Handover Detection message is traced over the Abis interface and the
Handover Complete message is traced over the Um interface.
If Assignment Procedure in Intra-Cell HO Allowed in the SET GCELLSOFT command is set to

YES(Yes), the Assignment Complete message can be traced. If this parameter is set to NO(No), the
Handover Complete message can be traced.
Using MML Commands (Handover Algorithm I)

1. If handover algorithm I is used, run the BSC MML command SET
GCELLHOBASIC with Intracell F-H HO Allowed set to NO(No).
2. Run the BSC MML command LST GCELLHOBASIC to query the value of
Intracell F-H HO Allowed.
Expected result: The value of Intracell F-H HO Allowed is No.
MML Command Examples (Handover Algorithm I)
//Deactivating Dynamic HR/FR Adaptation

HOCTRLSWITCH=HOALGORITHM1, INTRACELLFHHOEN=NO;
Using MML Commands (Handover Algorithm II)

1. Run the SET GCELLHOBASIC command with AMR F-H Ho Allowed set to
NO(No).
2. Run the LST GCELLHOBASIC command to query the value of AMR F-H Ho
Allowed.
Expected result: The value of AMR F-H Ho Allowed is No.
3. Run the SET GCELLHOBASIC command with Non-AMR F-H Ho Allowed set to
NO(No).
4. Run the LST GCELLHOBASIC command to query the value of Non-AMR F-H Ho
Allowed.
Expected result: The value of Non-AMR F-H Ho Allowed is No.
MML Command Examples (Handover Algorithm II)
//Deactivating Dynamic HR/FR Adaptation

HOCTRLSWITCH=HOALGORITHM2, AMRFULLTOHALFHOALLOW=NO,
NOAMRFULLTOHALFHOALLOW=NO;
Using the CME

6.7 Deploying Dynamic Multiple CCCH

Aspect Requirement
BSC None
BTS Both 3900 series base stations (excluding

BTS3900B and BTS3900E) and 5900 series
base stations support this feature.
GSM networking None
MS None
MSC None
License The license controlling this feature has been

activated. For details on how to activate the
license, see License Management Feature
Parameter Description. For details about license
items, see License Control Item Description.
Others None
6.7.2 Precautions
 If timeslot 0 of the BCCH TRX is combined BCCH or BCCH+CBCH, the Dynamic

Multiple CCCH feature cannot be enabled for the BCCH TRX.
 If the Dynamic Channel Adjustment Policy parameter is set to OFF(Off) when you
enable the Dynamic Multiple CCCH feature, a rollback cannot be performed on the
extended CCCHs dynamically converted.
 You are advised to enable or disable this feature in all the cells under the same
location area or BSC.
The paging mode used by the Huawei BSS can be location area code (LAC) paging or BSC paging.
 Configure the BCCH TRX RSL Multiplexing Mode parameter as follows:

 TMSI paging: When Maximum Number of Dynamic CCCHs plus the
number of static BCHs is 1, 2, or 3, you are advised to set BCCH TRX RSL
Multiplexing Mode to MODE2_1, MODE1_1, and MODE1_1, respectively.
 IMSI paging: When Maximum Number of Dynamic CCCHs plus the
number of static BCHs is 1, 2, or 3, you are advised to set BCCH TRX RSL
Multiplexing Mode to MODE4_1, MODE2_1, and MODE1_1, respectively.
A large value of Maximum Number of Dynamic CCCHs represents a high Um interface capability. To
prevent message delivery congestion over the Abis interface, you need to increase the RSL bandwidth of
BCCHs and set BCCH TRX RSL Multiplexing Mode by referring to the preceding suggestions.
 To support the Dynamic Multiple CCCH feature, configure SDCCHs, static PDCHs,
or channels reserved for VIP users that involve in the baseband frequency hopping in the
cell by complying with the following rules:
 If Maximum Number of Dynamic CCCHs is set to 1, the channels cannot be
configured in timeslot 2.
configured in timeslot 2 or 4.
configured in timeslot 2, 4, or 6.
 For emergency calls that must be guaranteed, set the EMCPRILV (BSC6900, BSC6910)
to a value other than 15. Otherwise, if the emergency call is assigned with a channel that is
to be converted to a CCCH, the emergency call will be handed over to another channel. If
the handover fails, the call cannot return to the original channel. As a result, the
emergency call drops.
6.7.3 Data Preparation
Table 6-8 Data preparation
Parameter Name Parameter ID NE Setting Notes Data Source
Dynamic Multiple DynCCCHSwitc BSC6900/BSC6 If static BCHs Internal plan

CCCHs h 910 are configured in
a cell, delete
static BCHs and
enable the
Dynamic Multiple
CCCH feature in
all cells under
the location area
or BSC. If over
70% of all cells
under a location
area or BSC
experience
paging timeout
during peak
hours on the live
network, disable
this feature in all
the cells under
the location area
or BSC. If over
160,000 paging
messages are
sent in one peak
hour in a cell on
the live network,
enable this
feature in all the
cells under the
location area or
BSC.
Dynamic ChannelDynAdj BSC6900/BSC6 Whether to Default/Recomm

Channel ustOpt 910 enable the ended Value
Adjustment dynamic channel
Policy adjustment
optimization
procedure. If this
parameter is set
to ON(On), the
BSC sends the
BTS a message
indicating
dynamic channel
adjustment over
the RSL. If this
parameter is set
to OFF(Off), the
BSC sends the
BTS a message
indicating
dynamic channel
adjustment over
the OML.
By default, the
configuration
data sent to the
BTS over the
OML is static
configuration,
and a rollback
cannot be
performed on
extended
CCCHs
dynamically
converted.
Therefore, you
must set this
parameter to
ON(On) when
enabling the
Dynamic Multiple
CCCH feature.
Dynamic CCCH DynCCCHLoadI BSC6900/BSC6 Load threshold Network plan

Addition ncrThr 910 for dynamically
Threshold converting a
TCH to an
extended CCCH.
If the CCCH load
is greater than
the value of this
parameter within
the duration
specified by
DynCCCHLoad
Duration
(BSC6900,
BSC6910), a TCH
is dynamically
converted to an
extended CCCH.
The larger the
value of this
parameter, the
smaller the
number of TCHs
dynamically
converted to
extended
CCCHs during
peak hours, and
the lower the
paging
efficiency. The
smaller the value
of this
parameter, the
larger the
number of TCHs
dynamically
converted to
extended
CCCHs during
off-peak hours,
and the lower
the resource
usage.
Dynamic CCCH DynCCCHLoad BSC6900/BSC6 Load threshold Network plan

Removal RedcThr 910 for dynamically
Threshold converting an
extended CCCH
to a TCH. An
extended CCCH
can be
dynamically
converted to a
TCH if the
following
conditions are
met:
The CCCH load
is less than the
value of this
parameter within
the duration
specified by
DynCCCHLoad
Duration
(BSC6900,
BSC6910). The
BSC predicts
that the
message
sending
capability on the
Um interface is
sufficient after
the number of
CCCHs
decreases.
The interval
between two
consecutive
conversions
reaches the
value specified
by
DynCCCHRedu
ceInterval
(BSC6900,
BSC6910).
The larger the
value of this
parameter, the
smaller the
number of
extended
CCCHs
dynamically
converted to
TCHs during
peak hours, and
the lower the
paging
efficiency. The
smaller the value
of this
parameter, the
larger the
number of
extended
CCCHs
dynamically
converted to
TCHs during off-
peak hours, and
the lower the
resource usage.
Dynamic CCCH DynCCCHLoad BSC6900/BSC6 Duration during Network plan

Load Stat. Duration 910 which the CCCH
Duration load is higher
than the value of
DynCCCHLoadI
ncrThr
(BSC6900,
BSC6910) or
lower than the
value of
DynCCCHLoad
RedcThr
(BSC6900,
BSC6910). After
this duration
expires, the BTS
triggers a
dynamic
conversion
between TCHs
and extended
CCCHs. The
larger the value
of this
parameter, the
longer the time
to trigger
dynamic
conversion
between
extended
CCCHs and
TCHs, the
smaller the
number of
dynamic
conversions, and
the lower the
paging
efficiency. The
smaller the value
of this
parameter, the
shorter the time
to trigger
dynamic
conversion
between
extended
CCCHs and
TCHs, the larger
the number of
unnecessary
conversions due
to inaccurate
determination,
and the lower
the resource
usage.
Maximum MaxDynCCCHN BSC6900/BSC6 Maximum Network plan

Number of um 910 number of
Dynamic CCCHs extended
CCCHs that can
be dynamically
converted in a
cell. Each cell
has a maximum
of three
extended
CCCHs,
including
dynamically
converted
CCCHs and
statically
configured
CCCHs. These
CCCHs are
carried by
timeslots 2, 4,
and 6 on the
BCCH TRX.
When the CCCH
load is low, the
channels on
these timeslots
can be occupied
by signaling, CS
services, or PS
services. When
the CCCH load
is high, the
channels on
these timeslots
are dynamically
converted to
extended
CCCHs to
reduce the
CCCH load. The
larger the value
of this
parameter, the
larger the
number of TCHs
dynamically
converted to
CCCHs during
peak hours, the
smaller the
number of
available TCHs,
and the higher
the TCH
congestion rate.
The smaller the
value of this
parameter, the
smaller the
number of TCHs
dynamically
converted to
CCCHs, and the
lower the paging
efficiency.
Interval for DynCCCHRedu BSC6900/BSC6 Period during Network plan

Dynamically ceInterval 910 which the next
Removing dynamic
CCCHs conversion from
extended
CCCHs to TCHs
is prohibited
after a dynamic
conversion.
Specifying such
period prevents
frequent
dynamic
conversions due
to CCCH load
changes. The
larger the value
of this
parameter, the
smaller the
number of
extended
CCCHs
dynamically
converted to
TCHs during off-
peak hours, and
the lower the
resource usage.
The smaller the
value of this
parameter, the
larger the
number of
extended
CCCHs
dynamically
converted to
TCHs, the more
the number of
dynamic
conversions due
to paging burst,
and the lower
the paging
efficiency.
You are advised
to set this
parameter to a
value greater
than or equal to
30 minutes.
Priority of EMCPRILV BSC6900/BSC6 Whether the Network plan

Emergency Call 910 BSC reserves
TCHFs for
emergency calls
and whether
emergency calls
can preempt
TCHFs used by
common calls. If
the parameter is
set to a value
ranging from 1 to
14, the BSC
reserves TCHFs
for emergency
calls after
receiving the
ESTABLISH
INDICATION
message. If the
channel
reservation fails
and
PREEMPTIONP
ERMIT (BSC6900,
BSC6910) is set to
ON(ON), the
BSC uses the
value of this
parameter as the
user priority (1 is
the highest
priority and 14 is
the lowest one)
for emergency
calls to preempt
TCHFs used by
common calls.
After
successfully
preempting the
TCHFs, the BSC
reserves the
TCHFs for
emergency calls.
When this
parameter is set
to a value
ranging from 1 to
14, the TCH
occupied by an
emergency call
cannot be
preempted. The
specific handling
policies are as
follows:
1. The TCHs
occupied by
emergency calls
cannot be
preempted.
2. If
DynCCCHSwitc
h (BSC6900,
BSC6910) is set to
ON(ON),
emergency calls
on channels
corresponding to
timeslots 2, 4,
and 6 on the
BCCH TRX can
be forcibly
handed over to
another
channels. If the
forcible
handover fails,
the emergency
calls can return
to the original
channels and will
not be released.
6.7.4 Activation
Using MML Commands
1. On the BSC LMT, run the SET GCELLCCCH command with its parameters set as
follows:
 Set Dynamic Multiple CCCHs to ON(ON).
 Set Dynamic CCCH Addition Threshold, Dynamic CCCH Removal
Threshold, Dynamic CCCH Load Stat. Duration, Maximum Number of Dynamic
CCCHs, and Interval for Dynamically Removing CCCHs to appropriate values.
2. Run the SET BSCEXSOFTPARA command with Dynamic Channel Adjustment
Policy set to ON(On).
If the BCCH TRX participates in the baseband frequency hopping (FH), timeslots that do not participate in the
frequency hopping vary with the value of Maximum Number of Dynamic CCCHs. The specific mapping is as
follows:
 Value 1: timeslot 2
 Value 2: timeslots 2 and 4
 Value 3: timeslots 2, 4, and 6
When the cell is in the deactivated state, you can run the SET GTRXCHANHOP command on the BSC LMT to
change the FH attributes of timeslots 2, 4, and 6 for BCCH and non-BCCH TRXs.
SET GCELLCCCH: IDTYPE=BYID, CELLID=2, DynCCCHSwitch=ON,

MaxDynCCCHNum=2, DynCCCHLoadIncrThr=90, DynCCCHLoadRedcThr=65,
DynCCCHLoadDuration=10, DynCCCHReduceInterval=30;
SET BSCEXSOFTPARA: ChannelDynAdjustOpt=ON;
Using the CME
When configuring the Dynamic Multiple CCCH feature on the CME, you must perform a single configuration
first, and then perform batch modifications if required.


Modification
Center
1 GCELLCCCH BSC6900/BS Dynamic DynCCCHS Yes

C6910 Multiple witch
CCCHs
BSC6900/BS Dynamic DynCCCHLo

C6910 CCCH adIncrThr
Addition
Threshold

C6910 CCCH adRedcThr
Removal
Threshold

C6910 CCCH Load adDuration
Stat. Duration
BSC6900/BS Maximum MaxDynCCC

C6910 Number of HNum
Dynamic
CCCHs
BSC6900/BS Interval for DynCCCHRe

C6910 Dynamically duceInterval
Removing
CCCHs
2 BSCEXSOFT BSC6900/BS Dynamic ChannelDyn Yes

PARA C6910 Channel AdjustOpt
Adjustment
Policy
Increasing Dynamic CCCHs
1. On the BSC LMT, run the SET GCELLCCCH command with its parameters set as
follows:
 Set Dynamic Multiple CCCHs to ON(ON).
 Set Dynamic CCCH Addition Threshold, Dynamic CCCH Removal
Threshold, and Dynamic CCCH Load Stat. Duration to 0, and Maximum Number
of Dynamic CCCHs to 3.
2. Initiate a large number of calls (including originated calls and terminated calls).
Ensure that more than 100 paging messages are delivered within a second.
3. View the traced CS messages on the Abis interface.
Trace Abis-interface messages over both the OML and RSL when either of the following conditions are
met:
The dynamic CCCH adjustment messages are sent over both the RSL and OML.
The GSM and UMTS Dynamic Spectrum Sharing(GSM) feature is enabled, but the BTS does not report its
capability.
In other cases, the BSC traces Abis-interface messages only over the RSLs.
For details about how to trace Abis-interface messages, see "Tracing CS Domain OML Messages on the
Abis Interface" and "Tracing CS Domain RSL Messages on the Abis Interface" in BSC6900 GSM LMT
User Guide or BSC6910 GSM LMT User Guide.
 RSL message tracing

If all the following messages are traced, the CCCH dynamic adjustment is successful:
 Abis Dynamic Ccch Request
 Abis Dynamic Ccch Request Ack
 OAM in RSL (change-chan-comb)
 OAM in RSL (change-chan-comb-ack)
 RSL and OML message tracing
The following messages are traced over the RSL:
The following messages are traced over the OML:
 Set Channel Attributes
 Set Channel Attributes Ack
The monitoring window on the BSC LMT shows that timeslots 2, 4, and 6 on the BCCH
TRX are converted to BCHs in sequence based on the CCCH load. For details about how
to monitor the channel status, see "Monitoring Channel Status" in BSC6900 GSM LMT
5. Check the related counters.
Check the value of the CELL.CH.AVAIL.NUM.CCCH.AVR counter. If the value of this
counter minus the number of static CCCHs is not 0, the TCH has been converted to an
extended CCCH.
Decreasing Dynamic CCCHs
1. If the number of added dynamic CCCH is greater than 1, run the SET
GCELLCCCH command with its parameters set as follows on the BSC LMT:
 Set Dynamic CCCH Addition Threshold to 90.
 Set Dynamic CCCH Removal Threshold to 90.
 Set Dynamic CCCH Load Stat. Duration to 0.
 Set Interval for Dynamically Removing CCCHs to 1.
2. Stop initiating calls.
3. Trace CS messages over the Abis interface.
Trace Abis-interface messages over both the OML and RSL when either of the following conditions is met:
 The dynamic CCCH adjustment messages are sent over both the RSL and OML.
 The GSM and UMTS Dynamic Spectrum Sharing(GSM) feature is enabled, but the BTS does
not report its capability.
In other cases, the BSC traces the Abis-interface messages only over RSLs.
For details about how to trace Abis-interface messages, see "Tracing CS Domain OML Messages on the
Abis Interface" and "Tracing CS Domain RSL Messages on the Abis Interface" in BSC6900 GSM LMT
 RSL message tracing

If all the following messages are traced, the CCCH dynamic adjustment is successful:
 OAM in RSL (change-chan-comb)
 OAM in RSL (change-chan-comb-ack)
 RSL and OML message tracing
The following messages are traced over the RSL:
The following messages are traced over the OML:
 Set Channel Attributes
 Set Channel Attributes Ack
The monitoring window on the BSC LMT shows that timeslots 6, 4, and 2 on the BCCH
TRX are converted to TCHs in sequence based on the CCCH load. For details about how
to monitor the channel status, see "Monitoring Channel Status" in BSC6900 GSM LMT
5. Check the related counters.
Check the value of the CELL.CH.AVAIL.NUM.CCCH.AVR counter. If the value of this
counter decreases, the CCCH has been dynamically converted to TCHs.
6.7.6 Deactivation
Using MML Commands
If the BCCH TRX participates in the baseband frequency hopping, deactivate the cell and run the BSC MML
command SET GTRXCHANHOP command to set timeslots 2, 4, and 6 of the BCCH TRX to participate in the
baseband frequency hopping before deactivating this feature.
On the BSC LMT, run the SET GCELLCCCH command with Dynamic Multiple CCCHs
set to OFF(OFF).
SET GCELLCCCH: IDTYPE=BYID, CELLID=2, DynCCCHSwitch=OFF;
Using the CME

6.8 Performance Optimization
Monitoring
Table 6-10 Monitoring counters
Description Name
Number of Channel Conversions (TCH- CELL.CH.CONVERT.NUM.TCH.SD

SDCCH)
Number of Channel Conversions (SDCCH- CELL.CH.CONVERT.NUM.SD.TCH

TCH)
Congestion Rate on SDCCH per CELL (due CELL.RATE.SD.CONG

to Busy)
Parameter Optimization
If the counter Congestion Rate on SDCCH per CELL (due to Busy) increases, increase the
value of CELLMAXSD (BSC6900, BSC6910) accordingly.
If PDCH2SDEN (BSC6900, BSC6910) is set to YES(Yes), the value of the K3045:Congestion
Rate on TCH (All Channels Busy) counter increases, indicating the cell provides a large
number of CS services, and the BSC preferentially converts occupied TCHs to SDCCHs.
If PDCHtoSDCCHAdjustPrefSw (BSC6900, BSC6910) is set to ON(On), when the cell has
sufficient dynamic PDCHs, occupied TCHs, and no idle TCH, the BSC preferentially
converts PDCHs to SDCCHs in a dynamic manner.
Monitoring
Description Name
Mean Number of Busy TCHs (TCHH) CELL.CH.BUSY.NUM.HR.TRAF.900.AVR +

CELL.CH.BUSY.NUM.HR.TRAF.1800.AVR
Congestion Rate on TCH (All Channels CELL.KPI.TCH.CONGESTION.RATE

Busy)
Channel Conversion Requests (TCHF- CELL.CH.CONVERT.REQ.NUM.FR.TO.HR

TCHH)
Successful Channel Conversions CELL.CH.CONVERT.SUCC.NUM.FR.TO.HR

(TCHF-TCHH)
Channel Conversion Requests (TCHH- CELL.CH.CONVERT.REQ.NUM.HR.FR

TCHF)
Successful Channel Conversions CELL.CH.CONVERT.SUCC.NUM.HR.FR

(TCHH-TCHF)
If the half-rate traffic is light, and the value of Congestion Rate on TCH (All Channels Busy)
is large, increase the values of TCHBUSYTHRES (BSC6900, BSC6910) and
AMRTCHHPRIORLOAD (BSC6900, BSC6910) to increase the proportion of TCHHs in a
cell, decreasing the congestion rate.
Monitoring
Description Name
Number of Successful Channel CELL.CH.CONVERT.SUCC.NUM.PDCH.HR

Conversions (PDCH to TCHH)
Number of Successful Channel CELL.CH.CONVERT.SUCC.NUM.PDCH.FR

Conversions (PDCH to TCHF)
Number of Successful Channel CELL.CH.CONVERT.SUCC.NUM.HR.PDCH

Conversions (TCHH to PDCH)
Number of Successful Channel CELL.CH.CONVERT.SUCC.NUM.FR.PDCH

Conversions (TCHF to PDCH)
None
Monitoring
Description Name
Mean Number of Available Channels CELL.CH.AVAIL.NUM.CCCH.AVR

(Extended CCCH)
If there is no static CCCH in the cell and paging expiration or deletion occurs in 70% of cells
under the LAC where this cell is located, you are advised to set MaxDynCCCHNum
(BSC6900, BSC6910) to 1 or a larger value for all cells under the LAC.
6.9 Troubleshooting
None
7 Parameters
 GBTSFunction Parameter Reference:contains all parameters related to radio access
reference?
8 Counters
counters.
 GBTSFunction Performance Counter Summary: contains all counters related to radio access
reference?
9 Glossary
1. BSC6900 Feature List

2. BSC6900 Basic Feature Description
3. BSC6900 Optional Feature Description
4. BSC6900 GSM Parameter Reference
5. BSC6900 GSM MML Command Reference
6. BSC6900 Performance Counter Reference
GSM BSS
GBSS20.1
Channel Management
Feature Parameter
Description
Issue 01
Date 2018-04-10

Notice

Address:
Website: https:/
3.6.25 Contents
1.1 Scope
1.3 Change History
2 Overview
2.1 Introduction
3.1 Channel Allocation Procedure
3.2 Channel Allocation in the Immediate Assignment Procedure
3.3 Channel Allocation in the Assignment Procedure
3.4 Channel Allocation in the Handover Procedure
3.5 Huawei Channel Allocation Algorithm
3.5.1 Channel Priorities
3.5.2 Channel Allocation Strategy
3.5.3 Preferentially Allocating Channels on the BCCH TRX to Non-AMR Calls
3.5.4 SDCCH Handover
3.5.5 Channel Allocation Algorithm in Engineering Mode
3.5.6 Multi-RAT Scheduling Management
3.6 Post-Processing of Channel Allocation
4 Related Features
4.1 GBFD-112013 Abis Congestion Trigger HR Distribution
4.2 GBFD-111005 Enhanced Channel Assignment Algorithm
5.2 Data Preparation
5.3 Activation
5.5 Deactivation
6 Parameters
7 Counters
8 Glossary
1.1 Scope
This document describes Channel Management feature, including its technical principles,
related features, network impact, and engineering guidelines.
 GBFD-111005 Enhanced Channel Assignment Algorithm
 GBFD-112013 Abis Congestion Trigger HR Distribution
Purpose

Software Interfaces
1.3 Change History
 Feature change
01 (2018-04-10)
Draft A (2018-02-05)

Change Change Description Parameter Change

Type
Feature Added the multi-RAT scheduling Added the following parameters:

change management function. For details, see  MulRatSchManaPriGSM
3.5.6 Multi-RAT Scheduling Management. (BSC6900, BSC6910)
 MulRatSchManaPriUMTS
(BSC6900, BSC6910)
 MulRatSchManaPriLTE
(BSC6900, BSC6910)
Editorial None None

change
2 Overview
2.1 Introduction
Channel management is a feature that manages all the radio channels. It uses the Huawei
channel allocation algorithm to allocate a suitable channel to the radio service and to adjust
the channel as required. Reasonable channel management guarantees not only the QoS for a
single subscriber but also the performance of the entire network. The channel to be allocated
can be a standalone dedicated control channel (SDCCH), a traffic channel (TCH), or a packet
data channel (PDCH).
Each TCH and each SDCCH is assigned a set of priorities. They are allocated in the order of
priority on the basis of the current channel resource usage. In this way, an available channel
with the highest priority is allocated. In addition, the BSC adjusts the channel rate and
converts the channels of different types based on the channel resource usage.
This document describes only the channel management in the circuit switched (CS) domain. For the description
of the channel management in the packet switched (PS) domain, see GPRS/EGPRS Channel Management
Feature Parameter Description.
Based on the service requirements and the current cell load, full-rate TCHs or half-rate TCHs
are allocated flexibly. This not only meets the communication requirements of the subscribers
but also increases the bandwidth efficiency of the radio channels. The number of full-rate
TCHs and the number of half-rate TCHs are flexibly adjusted to strike a balance between
network quality and network capacity.
For details on the adjustment between full-rate TCHs and half-rate TCHs and the conversion from or to
SDCCH, see Dynamic Channel Conversion Feature Parameter Description.
Abis Congestion √ √ √ √
Trigger HR
Distribution
Enhanced √ √ √ √
Channel
Assignment
Algorithm
3.1 Channel Allocation Procedure
The Base Station Controller (BSC) needs to allocate a suitable channel in the following
situations: a mobile station (MS) initiates a call (immediate assignment); an MS needs to
access a TCH for speech, after a channel for signaling is allocated (assignment); an MS needs
to be handed over to another channel (handover, including the intra-BSC handover, inter-
BSC handover, and inter-RAT handover).
When the MS initiates a new call, an SDCCH or a TCH has to be allocated according to the
call establishment cause. In this case, the TCH is used to carry signaling.
After receiving the channel request from the MS, the Mobile Switching Center (MSC)
instructs the BSC through the Assignment Request message to allocate a suitable channel to
the MS. The channel to be allocated must meet the requirements of the MSC and MS, such as
the channel type, speech version, and MS frequency capability.
During a call, if the MS has to change from one channel to another due to the receive quality,
receive level, timing advance (TA), or load, the BSC needs to allocate a suitable channel to
the call. The channel to be allocated must meet the call requirements, such as the
requirements for frequency and interference.
Within a cell, more than one channel can be chosen. In addition, in different channel
allocation procedures, the principles and conditions of selecting a channel are different.
Therefore, Huawei channel allocation algorithm specifies a set of priorities for each channel.
When channel allocation is required, the BSC refreshes the priorities based on the channel
type required by the call, and then allocates a most suitable channel selected from all the
channels that meet the requirements.
Figure 3-1 shows the procedure for the Huawei channel allocation algorithm.
Figure 3-1 Channel allocation procedure
3.2 Channel Allocation in the Immediate Assignment Procedure
Immediate Assignment Procedure

In the immediate assignment procedure, the MS sends a Channel Request message to the
network. The message contains the information element Establishment Cause. Based on the
Establishment Cause, the BSC determines whether to allocate an SDCCH or a TCH.
For example, if the Establishment Cause indicates an emergency call, the BSC preferentially
allocates a TCH to the call. If the Establishment Cause indicates a paging response, the BSC
preferentially allocates an SDCCH to the call.
Pre-Processing of Channel Allocation
In the immediate assignment procedure, the BSC is unaware of the MS frequency capability.
To ensure the normal access of the MS, the SDCCH or TCH to be allocated must be in the
compatible band of the BCCH.
In a multi-band cell, if SDCCHs are configured on BCCH-incompatible bands, the BSC
preferentially allocates the SDCCHs on the BCCH-compatible band, and then the SDCCHs
on the BCCH-incompatible band. In this case, MSs may be allocated channels on the
frequency band that is not supported by the MSs, causing access failure.
In a multi-band cell, if TCHs are configured on BCCH-incompatible bands:
 When ImmAssDiffBandAllocTCHSw (BSC6900, BSC6910) is set to ON(On), the
BSC preferentially allocates the TCHs on the BCCH-compatible band, and then the TCHs
on the BCCH-incompatible band. In this case, MSs may be allocated channels on the
frequency band that is not supported by the MSs, causing access failure.
 When ImmAssDiffBandAllocTCHSw (BSC6900, BSC6910) is set to OFF(Off), the
BSC can only allocate the TCHs on the BCCH-compatible band. In this case, MSs may
not be allocated any channels when all channels work on different frequency bands.
The GSM900 band consists of the P-GSM900 band, E-GSM900 band, and R-GSM900 band. The R-GSM900
band includes the frequencies in the P-GSM900 and E-GSM900 bands, and the E-GSM900 band includes the
frequencies in the P-GSM900 band. If the BCCH TRX is configured in the R-GSM900 band, then the E-
GSM900 and P-GSM900 bands are the compatible bands of the BCCH; if the BCCH TRX is configured in the
E-GSM900 band, the P-GSM900 band is the compatible band of the BCCH.
3.3 Channel Allocation in the Assignment Procedure
Assignment Procedure
In the assignment procedure, the MSC sends an Assignment Request or Voice Group Call
Service(VGCS)/Voice Broadcast Service(VBS) Assignment Request message that contains
the information element Channel Type to the BSC. The Channel Type indicates the type of
the required traffic channel (for speech or for data), channel rate, and speech version list.
Based on the Channel Type, the BSC allocates a suitable channel to the call.
Pre-Processing of Channel Allocation
When the MSC specifies that the full-rate TCH or half-rate TCH is preferred, the BSC
allocates a full-rate TCH or a half-rate TCH to the call based on the following settings of
TCHRATEMODIFY (BSC6900, BSC6910):
 TCHRATEMODIFY (BSC6900, BSC6910) is set to NO(No).
The BSC uses the channel rate assignment strategy controlled by the MSC.
 If the MSC specifies that the full-rate TCH is preferred and there is an idle
full-rate TCH in the cell, a full-rate TCH is allocated.
 If the MSC specifies that the half-rate TCH is preferred and there is an idle
half-rate TCH in the cell, a half-rate TCH is allocated.
 TCHRATEMODIFY (BSC6900, BSC6910) is set to YES(Yes).
The BSC uses the optimized strategy to determine the channel rate. That is, the BSC
specifies the channel rate based on the channel resource usage. When the channel resource
usage is high, that is, the network is busy, a half-rate TCH is preferably allocated.
Otherwise, a full-rate TCH is preferably allocated.
 If there are sufficient full-rate TCHs, full-rate TCHs are preferably allocated to
guarantee the speech quality, irrespective of whether the MSC specifies the channel
rate preferred.
 If there are insufficient full-rate TCHs, half-rate TCHs are preferably allocated
to guarantee the network capacity, irrespective of whether the MSC specifies the
channel rate preferred.
If one of the following conditions is met, you can infer that the network is busy.
 The channel seizure rate exceeds TCHBUSYTHRES (BSC6900, BSC6910).
Channel seizure rate = (number of busy full-rate channels + number of busy half-rate
channels/2)/(number of available full-rate channels + number of available half-rate channels/2) x 100%
The number of available channels refers to the total number of busy and idle channels. The full-rate
TCHs and half-rate TCHs include those that are configured as dynamic PDCHs but are not carrying any
packet services.
 For the Adaptive Multi Rate (AMR) calls, the AMRTCHHPRIORALLOW

(BSC6900, BSC6910) parameter is set to ON(On) and the channel seizure rate exceeds
AMRTCHHPRIORLOAD (BSC6900, BSC6910).
 In a concentric cell, when HRIUOLDRATESELALLOW (BSC6900, BSC6910)
is set to YES(Yes):
For the calls in the overlaid subcell, the channel seizure rate of the overlaid subcell
exceeds TCHTRICBUSYOVERLAYTHR (BSC6900, BSC6910).
For the calls in the underlaid subcell, the channel seizure rate of the underlaid subcell
exceeds TCHTRIBUSYUNDERLAYTHR (BSC6900, BSC6910).
 In a concentric cell, for AMR calls, when the AMRLOADOPTEN (BSC6900,
BSC6910) parameter is set to YES(Yes):
For the calls in the overlaid subcell, the traffic load exceeds
INNAMRTCHHPRIORLOAD (BSC6900, BSC6910).
For the calls in the underlaid subcell, the traffic load exceeds
OUTAMRTCHHPRIORLOAD (BSC6900, BSC6910).
The traffic load in the overlaid subcell is calculated using the following formula:
(Number of full-rate TCHs during peak hours in the overlaid subcell x 2 + Number of half-rate TCHs
during peak hours in the overlaid subcell)/(Number of available full-rate TCHs in the overlaid subcell x 2
+ Number of available half-rate TCHs in the overlaid subcell)
The traffic load in the underlaid subcell is calculated using the following formula:
(Number of full-rate TCHs during peak hours in the underlaid subcell x 2 + Number of half-rate TCHs
during peak hours in the underlaid subcell)/(Number of available full-rate TCHs in the underlaid subcell
x 2 + Number of available half-rate TCHs in the underlaid subcell)
 AterCongHRFlag is set to Open(Open), the Ater resource usage exceeds

AterCongstRatio.
The BSC6910 does not support the Ater interface.
To ensure the service quality of the network and to restrict the proportion of half-rate
service users in the cell, during the channel allocation procedure, the BSC performs as
follows when a half-rate channel is preferred for the current call (not including the call that
requests the half-rate channel only):
 When the proportion of half-rate service users in the cell exceeds
ALLOWHALFRATEUSERPERC (BSC6900, BSC6910), the system does not allocate a
half-rate channel.
 When the proportion of AMR half-rate service users in the cell exceeds
ALLOWAMRHALFRATEUSERPERC (BSC6900, BSC6910), the system does not
allocate an AMR half-rate channel.
When allocating channels, the BSC determines whether to trigger rate adjustment based on
the channel usage in the cell. To enable real-time rate adjustment, the channels after rate
adjustment are allocated to the current call immediately.
Based on the rate of the allocated channel and the speech version capability of the TRX that
carries the channel, the BSC selects an appropriate speech version from the speech version
list assigned by the MSC. In addition, during channel allocation, if the speech version list
specified by the MSC includes the AMR, the BSC preferentially allocates a channel that
supports the AMR.
For example, the speech version list specified by the MSC includes the full-rate speech
versions 3 and 1 and half-rate speech versions 3 and 1.
 If the allocated channel is of full rate and the TRX that carries the channel supports
the AMR, the BSC selects the full-rate speech version 3, that is, AMR FR.
 If the allocated channel is of full rate and the TRX that carries the channel does not
support the AMR, the BSC selects the full-rate speech version 1, that is, FR.
 If the allocated channel is of half rate and the TRX that carries the channel supports
the AMR, the BSC selects the half-rate speech version 3, that is, AMR HR.
 If the allocated channel is of half rate and the TRX that carries the channel does not
support the AMR, the BSC selects the full-rate speech version 1, that is, HR.
When the BSC receives the assignment request in which the value of "queuing allowed
indicator" is 0 and no idle TCHs can be allocated:
 If the ForceQueueInAss (BSC6900, BSC6910) parameter is set to YES(Yes), the call
is queued. If idle TCHs are available, the BSC allocates an idle TCH to the MS. If the
TCH application is successful before the timer specified by the TIQUEUINGTIMER
(BSC6900, BSC6910) parameter expires, the BSC stops the timer. If the TCH application is
unsuccessful after the timer specified by the TIQUEUINGTIMER (BSC6900, BSC6910)
parameter expires, channel allocation fails.
 If the ForceQueueInAss (BSC6900, BSC6910) parameter is set to NO(No), the call is
not allowed to be queued. If directed retry is allowed, the BSC initiates the directed retry
procedure. Otherwise, channel allocation fails.
3.4 Channel Allocation in the Handover Procedure
Incoming BSC Handover
For an incoming BSC handover, including the inter-BSC handover and the inter-RAT
handover, the channel allocation procedure after the handover is the same as the channel
allocation in the assignment procedure. The Handover Request message contains the
information element Channel Type. The BSC allocates a suitable channel to the call after
handover based on the channel rate and speech version list indicated in the Channel Type. For
details, see 3.3 Channel Allocation in the Assignment Procedure.
Intra-BSC Handover
For an intra-BSC handover, including the intra-cell handover and inter-cell handover, the
BSC allocates a new channel to the call to be handed over according to the MS frequency
capability, current channel rate and speech version list of the call, channel type and speech
version list required by the MSC, and handover cause.
For example, if the ongoing call to be handed over supports the AMR, the BSC preferentially
allocates a channel that supports the AMR to this call. If an intra-cell handover due to
interference is required, the BSC preferentially allocates a channel on other TRXs to this call.
When the BSC selects a channel participating in frequency hopping during a reassignment or
quality-based intra-cell handover:
 If the QUALHOPRIALLOW (BSC6900, BSC6910) parameter is set to ON(On), the
BSC preferentially selects a channel of other timeslots for this call. This increases the high
quality indicator (HQI) and success rate of quality-based handovers, minimizes
interference, and decreases the number of quality-based handovers.
 If the QUALHOPRIALLOW (BSC6900, BSC6910) parameter is set to OFF(Off), the
BSC preferentially selects a channel on other TRXs for this call.
3.5 Huawei Channel Allocation Algorithm
3.5.1 Channel Priorities
According to the Huawei channel allocation algorithm, each channel is assigned a set of
priorities. The BSC refreshes the priorities according to the TRX attributes, configured
frequency, channel type required by the call, and characteristics of the call. During channel
allocation, the BSC selects a channel with the highest priority from all the channels that meet
the requirements and allocates it to the call.
The following priorities are considered during channel allocation:
 Location priority
Location priority is used by the BSC to determine the TRX to which an MS is
preferentially assigned based on the distance between the MS and BTS. For example, upon
receiving an assignment request, the BSC preferentially assigns an MS to a non-BCCH
TRX if the MS receive level on the SDCCH is greater than the value of
AssJdgCenterUsrRxLevThd (BSC6900, BSC6910) When the MS initiates an intra-BSC
or intra-cell request, the BSC preferentially assigns the MS to a non-BCCH TRX if the
target-cell receive level before the MS performs a handover is greater than the value of
HoJdgCenterUsrRxLevThd (BSC6900, BSC6910). Location priority is specified by the
ChanAllocByUsrLocInAss (BSC6900, BSC6910) and ChanAllocByUsrLocInHo
(BSC6910, BSC6900) parameters.
You are advised to enable the location priority function when BCCH TRXs have better quality than TCH
TRXs.
 TRX priority
TRX priority is used to preferentially allocate the channel on a TRX with a higher priority.
For example, to reduce BTS power consumption, the TRX priority can be set and the
channel on the Broadcast Control Channel (BCCH) TRX is preferably allocated to the
call. TRX priority is specified by parameters OPTL (BSC6900, BSC6910) and
TRXPRIALLOW (BSC6900, BSC6910).
 Frequency band capability priority
Frequency band capability priority determines the frequency band capability of the TRX.
In a multi-band cell, frequency band capability priority is used to allocate the channel on a
suitable TRX to the call. For example, if a cell is configured in the P-GSM and E-GSM
bands, the BSC preferentially allocates the channel on the TRX in the E-GSM band to the
MS that supports this band. This ensures more accesses to the cell and protects the MS that
supports only the P-GSM band from access failure.
If an MS simultaneously supports P-GSM, E-GSM, and R-GSM frequency bands and the
cell load is less than or equal to FREQLOADSHARETRAFFTHRSH (BSC6900,
BSC6910), the BSC does not consider the frequency band capability priority.
 Concentric cell priority

In a concentric cell, the concentric cell priority determines whether the channel in the
underlaid subcell or overlaid subcell is allocated.
 History occupation priority
If call drops occur frequently on a channel serving the MS, the history occupation priority
can be set to lower the priority of the channel. A channel without occurrence of call drops
is preferably allocated, reducing the call drop rate. The history occupation priority is
specified by HISPRIOALLOW (BSC6900, BSC6910).
 Interference priority
Interference priority is used to preferentially allocate a channel with lower interference to
the call, improving the speech quality. The interference priority is specified by
INTERFPRIALLOW (BSC6900, BSC6910).
If the INTFBANDENHANCESW (BSC6900, BSC6910) parameter is set to ON(On), the
interference level is reported according to the actual interference level class, and therefore
the reported interference level is more accurate. The period-related parameters are as
follows:
 IntfFilterPeriod (BSC6900, BSC6910) specifies the period for filtering
interference levels.
 IntfReprotPeriod (BSC6910, BSC6900) specifies the period for reporting
interference levels.
 INTERPERIOD (BSC6900, BSC6910) specifies both the period for filtering
interference bands and the period for reporting interference bands.
In heavy-traffic urban areas, if the INTFBANDENHANCESW (BSC6900, BSC6910)
parameter is set to ON(On), the call drop rate decreases, the high quality indicator (HQI)
remains unchanged or slightly increases, and the proportion of average number of
channels in interference bands 4 and 5 remains unchanged.
INTERFPRIALLOW (BSC6900, BSC6910) specifies whether to consider interference
priorities during channel assignment.
 TRX power-saving priority
With the increasingly high TRX integration and the adoption of new power-saving
technology, the TRXs produced in different periods differ in terms of power-saving. TRX
power-saving priority is used to preferentially allocate a channel on an effectively power-
saving TRX to the call, reducing the power consumption of the BTS. The TRX power-
saving priority is specified by PWRPRIORALLOW (BSC6900, BSC6910).
 PS coordination priority
In GPRS/EGPRS, an MS can be allocated multiple successive timeslots. When the
dynamic conversion between the PDCH and TCH is enabled, the current PDCH and
adjacent TCHs are reserved, and other channels are allocated to the call.
 TCH rate priority
When the cell supports the half-rate TCH, the TCH rate priority is used to allocate a
channel of suitable rate to the call. For example, if the current call requires a half-rate
TCH, the priority of the full-rate TCH is lowered and the priority of the half-rate TCH is
raised.
 AMR and frequency reuse priority
The AMR has a higher anti-interference capability than other speech versions. In a cell
with tight frequency reuse, the BCCH TRX is generally configured with the frequency in
loose reuse, and other traffic TRXs are configured with frequencies in tight reuse.
Therefore, the channel on the BCCH TRX is preferably allocated to the non-AMR call and
the channel on the traffic TRX is preferably allocated to the AMR call, improving the
average speech quality in the entire network.
For details of preferentially allocating a channel on the BCCH TRX to the non-AMR call,
see 3.5.3 Preferentially Allocating Channels on the BCCH TRX to Non-AMR Calls.
 Timeslot priority
TSPRIORITY (BSC6900, BSC6910) specifies the timeslot priority. The BSC preferentially
selects a channel with the TSPRIORITY (BSC6900, BSC6910) parameter set to a small
value to the call.
 BCCH priority
BTRXPRIORITYSWITCH (BSC6900, BSC6910) specifies whether the BSC preferentially
allocates a channel on the BCCH TRX to the call.
In scenarios where channel priorities vary with TRXs, if ENTCHADJALLOW (BSC6900, BSC6910) is set to
YES, the traffic volume of the BSC is low, TCHF channels need to be preferentially allocated, and no idle
TCHF channels are available on high-priority TRXs, then the BSC preferentially allocates Couple channels on
high-priority TRXs to MSs (if there are no Couple channels but only single channels in the cell, the calls on the
single channels are switched to other channels so that the single channels are converted to Couple channels) and
converts the Couple channels to TCHF channels to carry the calls. However, TCH congestion and access
failures may occur during this process because some conditions are not met.
If the preceding scenario exists on the live network, you are advised to set ENTCHADJALLOW (BSC6900,
BSC6910) to NO to reduce the congestion rate on TCH.
3.5.2 Channel Allocation Strategy
Huawei channel allocation algorithm classifies the channel priorities into five types by the
impact on the call. In different application scenarios, you can adjust the order of the priorities
to better meet the networking requirements. The five types of priorities are as follows:
 Capacity
The capacity-related priority consists of the frequency capability priority, concentric cell
priority, location priority, and TCH rate priority. These priorities mainly have an impact
on the cell capacity.
 Quality
The quality-related priority consists of the history occupation priority, interference
priority, and AMR and frequency reuse priority. These priorities mainly have an impact on
the speech quality in the cell.
 PS coordination
The PS coordination-related priority determines the coordination relationship between CS
services and PS services in the GSM to guarantee the CS service capacity and PS service
capacity in the cell.
 Management
The management-related priority consists of the TRX priority and TRX power-saving
priority. These priorities are used for management purpose.
 Continuity
The continuity-related priority is associated with the timeslot numbers for idle channels
and number of TCHs. This type of priority is used for consecutively allocating TCHs or
PDCHs.
In channel allocation, CHALLOCSTRATEGY (BSC6900, BSC6910) is set to determine the
order of the five types of priorities. The BSC defines the following strategies:
 Capacity preferred
Capacity > quality > PS coordination > continuity > management
The strategy of capacity preferred is mainly applied to the network with loose frequency
reuse. This strategy can increase the network capacity while ensuring the network quality.
 Quality preferred
Quality > capacity > PS coordination > continuity > management
The strategy of quality preferred is mainly applied to the network with tight frequency
reuse to improve the network quality.
 PS relatively preferred
Capacity > PS coordination > quality > continuity > management
The strategy of PS relatively preferred is applicable to the network with loose frequency
reuse. When the capacity requirement takes precedence over the PS service requirement in
the network, this strategy is applied.
 PS absolutely preferred
PS coordination > capacity > quality > continuity > management
The strategy of PS absolutely preferred is applicable to the network with loose frequency
reuse. When the PS service requirement takes precedence over the capacity requirement in
the network, this strategy is applied.
 Continuity preferred
Capacity > PS coordination > continuity > quality > management
When the continuity preferred strategy is applied, the allocated CS channels are not
adjacent to PDCHs and corresponding to the timeslots with small numbers.
To use the strategy of continuity preferred, set the CHALLOCATIONOPTSWITCH
(BSC6900, BSC6910) parameter to YES(Yes).
 Management preferred
Management > capacity > quality > PS coordination > continuity
When the management preferred strategy is applied, the TRX priority can be configured,
and channels can be allocated based on the TRX priority.
A > B indicates that channel priorities related to A are compared first, and then the channel priorities related to
B.
The strategy of quality preferred is selected during the quality-based handover or reassignment without
considering the setting of CHALLOCSTRATEGY (BSC6900, BSC6910).
LOADSHAREALLOW (BSC6900, BSC6910) specifies the start point for channel allocation.
 If this parameter is set to YES(Yes), the channel allocation algorithm randomly
selects the start point for channel allocation.
 If this parameter is set to NO(No), the BSC selects the channel next to the previously
allocated one as the start point for channel allocation.
3.5.3 Preferentially Allocating Channels on the BCCH TRX to Non-AMR Calls
In a network with tight frequency reuse, loose frequency reuse mode, such as 4x3, is
generally applied to the BCCH TRX; tight frequency reuse mode, such as 1x3, is applied to
the traffic TRX. The AMR has a higher anti-interference capability than the non-AMR,
including the FR, EFR, and HR. Therefore, if the network supports the AMR and
NAMRLFRMTRXALLOWED (BSC6900, BSC6910) is set to YES(Yes), the channel on the
TRX where FREQREUSEMODE (BSC6900, BSC6910) is set to LOOSE(Loose), such as the
BCCH TRX, is preferably allocated to the MS that does not support the AMR, and the
channel on the TRX where FREQREUSEMODE (BSC6900, BSC6910) is set to
TIGHT(Tight) is allocated to MS that supports the AMR. In this way, the average speech
quality in the entire network is improved.
FREQREUSEMODE (BSC6900, BSC6910) of a TRX is determined in the network planning.
3.5.4 SDCCH Handover
The DIFFBANDSDCCHUSINGOPTIMIZE (BSC6900, BSC6910) parameter specifies

whether to allow the BSC to hand over an MS from an SDCCH on a frequency band
compatible with the BCCH frequency band to an SDCCH on a frequency band incompatible
with the BCCH frequency band. This function can relieve the congestion on the SDCCH on a
frequency band compatible with the BCCH frequency band and increase the access success
rate. However, this function increases the number of handovers for SDCCHs and decreases
the speed at which a call accesses the network.
3.5.5 Channel Allocation Algorithm in Engineering Mode
The FACTORYMODE (BSC6900, BSC6910) parameter specifies whether the BSC allocates a
channel on TRXs in a cell in a polling mode so that the BSC can evenly allocate channels on
each TRX in a cell to calls. In this way, the connection between RF modules and the antenna
can be checked without performing dialing tests on BTSs.
3.5.6 Multi-RAT Scheduling Management
CloudAIR Spectrum Sharing involves the GSM and LTE Spectrum Concurrency feature and
the GU@5 MHz feature. These two features have different requirements on the GSM channel
allocation algorithm. To meet customer requirements in different scenarios, the multi-RAT
scheduling management function is introduced to support flexible channel allocation policies
for preferentially guaranteeing GSM, UMTS, or LTE network performance gains as required.
This function is controlled by the MultiRatScheduManagSW (BSC6900, BSC6910)
parameter.
When this function is enabled, GSM TRXs can be exclusively used by GSM networks,
shared by GSM and UMTS networks, or shared by GSM and LTE networks based on the
settings of the UMTSDLCenterFreq (BSC6900, BSC6910), LTEDLCenterFreq (BSC6900,
BSC6910), and LTEBandwidth (BSC6900, BSC6910) parameters. The priorities of GSM TRXs
are controlled by the following parameters:
 MulRatSchManaPriGSM (BSC6900, BSC6910) for GSM TRXs exclusively used by
GSM networks
 MulRatSchManaPriUMTS (BSC6900, BSC6910) for GSM TRXs shared by GSM and
UMTS networks
 MulRatSchManaPriLTE (BSC6900, BSC6910) for GSM TRXs shared by GSM and
LTE networks
Small values of these parameters result in a low priority of GSM TRXs. In this situation, the
channel allocation algorithm on the GSM side allows these low-priority GSM TRXs to
preferentially carry GSM network traffic.
The TRX sharing attribute varies in different scenarios:

 Scenarios not using frequency hopping
It is the same as the frequency sharing attribute.
 Scenarios using frequency hopping
It is the same as the sharing attribute of the frequency with the highest priority in an MA group.
3.6 Post-Processing of Channel Allocation
After channel allocation, further processing is required on the basis of the allocation result,
including selecting the suitable speech version, preemption, queuing, and channel type
conversion.
The typical scenarios after the processing of channel allocation are as follows:
 When the TRX that carries the allocated channel does not support the AMR, the BSC
must select the full-rate speech version 1 or 2 for the call.
 If a call is not allocated a channel and the call supports preemption, the BSC performs
preemption for the call.
 If a call is not allocated a channel and the call supports queuing, the BSC places the
call in the queue.
 If a call requires a half-rate TCH but is allocated a full-rate TCH, the BSC must
convert the full-rate TCH to the half-rate TCH.
After channel allocation, the BSC can measure the interference on the allocated channel and
record traffic statistics.
 The CHANINTERMESALLOW (BSC6900, BSC6910) parameter specifies whether to
measure the interference on the allocated channel.
 The UPINTERLEVLIMIT (BSC6900, BSC6910) and DLINTERFLEVLIMIT (BSC6900,
BSC6910) parameters specify the uplink and downlink interference level thresholds,
respectively. The UPINTERFQUALLIMIT (BSC6900, BSC6910) and
DLINTERFQUALLIMIT (BSC6900, BSC6910) parameters specify the uplink and downlink
interference quality thresholds, respectively.
The SSLENSD (BSC6900, BSC6910), QLENSD (BSC6900, BSC6910), SSLENSI (BSC6900,
BSC6910), and QLENSI (BSC6900, BSC6910) parameters are used for configuring the
number of measurement reports (MRs) used for filtering the signal strength and quality of
TCHs and SDCCHs.
4 Related Features
4.1 GBFD-112013 Abis Congestion Trigger HR Distribution
GBFD-113402 Dynamic Adjustment -

Between FR and HR
GBFD-117301 Flex Abis If the Abis interface uses time division

multiplexing (TDM) transmission, GBFD-
117301 Flex Abis must be enabled
before enabling this feature.
None.
Impacted Features
None.
4.2 GBFD-111005 Enhanced Channel Assignment Algorithm
None.
None.
Impacted Features
None.
Aspect Requirement
BSC None
BTS None
GSM networking The following networking modes apply to this

feature:
 The Abis interface uses IP over EI
transmission.
 The Abis interface uses IP over ETH
transmission.
 The Abis interface uses TDM
transmission, and the GBFD-117301 Flex
Abis feature has been deployed.
MS MSs support HR speech versions.
MSC The MSC supports HR speech versions.

Others None
5.2 Data Preparation
Table 5-2 Data Preparation
LDR First LDRFST BSC6900/BSC69 Set this Network plan

(BSC6900, 10 parameter to
BSC6910) CSPH(CS
Preference
TCHH) if this
feature needs to
be enabled.
Set this
parameter to
CLOSE(Close) if
this feature
needs to be
disabled.
TRM load TRMLOADTHIN BSC6900/BSC69 The value of this Network plan

threshold index DEX (BSC6900, 10 parameter must
BSC6910) be unique.
Transport Type TRANST BSC6900/BSC69 Set this Network plan

(BSC6900, 10 parameter based
BSC6910) on the actual
transmission
type that the Abis
interface uses.
Threshold type THTYPE BSC6900/BSC69 Set this Internal plan

(BSC6900, 10 parameter to
BSC6910) PERCENTAGE(
Percentage) or
BANDWIDTH(B
and Width) to
determine the
threshold
calculation
mode.
5.3 Activation
Using MML Commands

1. Run the SET LDR command with LDR First set to CSPH(CS Preference TCHH).
2. Run the ADD TRMLOADTH command with TRM load threshold index,
Transport Type, and Threshold type set to appropriate values according to threshold
types.
3. Perform this step in Abis over IP mode.
 BSC6900
Run the MOD IPPATH command to configure parameters about an IP path. In this
step, set TRM load threshold index to the value specified in 2.
 BSC6910
Run the MOD ADJNODE command to configure parameters about a transport
adjacent node. In this step, set TRM load threshold index to the value specified in 2.
4. Perform this step in Abis over TDM mode. Run the SET BSCABISPRIMAP
command to set the BSC-side Abis priority mapping. In this step, set TRM load
threshold index to the value specified in 2.
The eGBTS does not support Abis over TDM mode.
 BSC6900
SET LDR: LDRFST=CSPH;
ADD TRMLOADTH: TRMLOADTHINDEX=10, TRANST=IP,
THTYPE=PERCENTAGE;
//In Abis over IP mode
MOD IPPATH: ANI=0, PATHID=0, ITFT=ABIS, TRMLOADTHINDEX=10;
//In Abis over TDM mode
SET BSCABISPRIMAP: IDTYPE=BYID, BTSID=0, TRANSTYPE=TDM,
LOADTHSW=ON, TRMLOADTHINDEX=10;
 BSC6910
SET LDR: LDRFST=CSPH;
ADD TRMLOADTH: TRMLOADTHINDEX=10, TRANST=IP,
THTYPE=PERCENTAGE;
//In Abis over IP mode
MOD ADJNODE: ANI=0, TRMLOADTHINDEX=10;
//In Abis over TDM mode
SET BSCABISPRIMAP: IDTYPE=BYID, BTSID=0, TRANSTYPE=TDM,
LOADTHSW=ON, TRMLOADTHINDEX=10;
Using the CME

This feature can be enabled only when congestion occurs over the Abis interface. Therefore,
this feature cannot be verified when the TRM load threshold is within a normal range.
5.5 Deactivation
Using MML Commands
On the BSC LMT, run the SET LDR command with LDR First set to CLOSE(Close) and
LDR Second, LDR Third, and LDR Fourth set to values other than CSPH(CS Preference
TCHH).
SET LDR: LDRFST=CLOSE;
Using the CME

6 Parameters
 BSC6910 GSM Parameter Reference:contains the parameters related to the BSC6910
reference?
7 Counters
counters.
reference?
8 Glossary
1. TS 29.002: "Digital cellular telecommunications system (Phase 2+); Mobile

Application Part (MAP) specification."
2. ISO/IEC 646 (1991): "Information technology-ISO7-bit coded character set for
information interchange."
3. GSM 04.18: "Digital cellular telecommunications system (Phase 2+); Mobile Radio
Interface Layer 3 specification; Radio Resource Control Protocol."
4. GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio
interface layer 3 specification."
5. GSM 08.06: "Digital cellular telecommunications system (Phase 2+); Signalling
transport mechanism specification for the Base Station System Mobile services
Switching Centre(BSS MSC) interface."
6. GSM 08.08: "Digital cellular telecommunications system (Phase 2+); Mobile services
Switching Centre Base Station System (MSC BSS) interface; Layer 3 specification."
7. GSM 08.51: "Digital cellular telecommunications system (Phase 2+); Base Station
Controller Base Transceiver Station (BSC BTS) interface; General aspects."
Controller Base Transceiver Station (BSC BTS) interface; Interface principles."
Controller Base Transceiver Station (BSC BTS) interface; Layer 2 specification."
Controller Base Transceiver Station (BSC BTS) interface; Layer 3 specification."
GSM BSS
GBSS21.1
Enhanced Measurement
Report (EMR) Feature
Issue 01
Date 2019-06-06

Notice

Address:
Website: https:/
3.6.27 Contents
1.1 Scope
1.3 Change History
2 Overview
2.1 Introduction
3.2 EMR Preprocessing
3.3 2G/3G Interoperability
3.4 DTX
3.5 Handover and Power Control
3.6 Faulty EMR MS Differentiated Processing
3.6.1 EMR MS Capability Database
3.6.2 Automatic Sharing of EMR MS Capability
4 Related Features
5.2 Deploying EMR
5.2.2 Precautions
5.2.3 Activation
5.2.5 Deactivation
6 Parameters
7 Counters
8 Glossary
1.1 Scope
This document describes the GBFD-117501 Enhanced Measurement Report (EMR) feature,
including its technical principles, related features, network impact, and engineering
guidelines.
Purpose

Software Interfaces
1.3 Change History
 Feature change
01 (2019-06-06)
Draft A (2018-12-30)

Feature change Changed the name of None

Huawei mobile element
management system from
U2000 to U2020.
2 Overview
2.1 Introduction
3GPP Release 99 introduced Enhanced Measurement Report (EMR) as a new type of

downlink measurement report (MR). Accordingly, the EMR feature has been introduced to
improve the interoperability between the GSM and UMTS networks and to obtain more
measurement information about neighboring cells.
3GPP TS 44.018 stipulates that the BSC should instruct an MS to report measurement
information about the serving cell and neighboring cells in the Measurement Information
(MI) or 2quater system information (SI) in a common MR or an EMR. Compared with a
common MR, an EMR provides additional measurement information as follows:
 An EMR uses an optimized coding scheme for neighboring cell information, and
therefore provides information on more neighboring cells than a common MR does.
Specifically, a common MR carries information on a maximum of 6 neighboring GSM
cells, while an EMR carries information on up to 15 neighboring GSM/WCDMA/TD-
SCDMA cells. This improves the interoperability between GSM and WCDMA/TD-
SCDMA networks and meets the requirement for service continuity. (WCDMA refers to
Wideband Code Division Multiple Access, and TD-SCDMA refers to Time Division-
Synchronous Code Division Multiple Access.)
 An EMR includes the Bit Error Probability (BEP) for identifying the channel quality.
BEP is a comprehensive criterion for reflecting the carrier-to-interference ratio (CIR),
signal delay extension, and MS data rate on a per burst basis. In addition, BEP is coded in
five bits, while Receive Quality (RXQUAL) is coded only in three bits. Therefore, BEP is
more precise than RXQUAL in speech quality measurement when radio signals are weak.
The RXQUAL value is converted from the bit error rate (BER).
 An EMR contains the number of correctly received speech frames for calculating the
Frame Erase Ratio (FER). FER measures the coding/decoding performance of speech
signals while RXQUAL measures the quality of radio signals. Therefore, FER
outperforms RXQUAL in speech quality measurement.
BEP and FER improve the performance of signal quality-based algorithms. They can replace
RXQUAL, which is commonly used as an indicator of radio signal quality, thereby
improving the performance of power control and handover algorithms.
Figure 2-1 shows the process for transmitting an EMR.
Figure 2-1 Process for transmitting an EMR
Feature BSC6900 BSC6910 BTS eGBTS
EMR √ √ √ √
The MEASURETYPE (BSC6900, BSC6910) parameter specifies the type of the MR reported
by an MS. When MEASURETYPE (BSC6900, BSC6910) is set to EnhMeasReport(Enhance
Measure Report), the MI or 2quater SI sent by the base station subsystem (BSS) carries the
MEASURETYPE and SCALEORDER information elements (IEs). If an MS fails to receive
the SI, the MS continues to report common MRs to the BSS.
The EMR feature requires support from MSs that comply with 3GPP Release 99. If an MS
does not support EMR, the MS continues to report common MRs even if the MI or 2quater SI
indicates that the MS should report an EMR.
In a common MR, information about neighboring GSM cells and neighboring UMTS cells is
reported separately according to the 2G cell BA2 list and UTRAN FDD cell BA2 list.
In an EMR, information about neighboring GSM cells and neighboring UMTS cells is
reported in one neighboring cell table. In the table, neighboring GSM cells use the smaller
indexes and neighboring UMTS cells use the larger indexes.
Assume that a cell has five neighboring GSM cells and four neighboring UMTS cells. If the
MS reports a common MR, the neighboring GSM cells use indexes 0 to 4 of the neighboring
GSM cell table, and the neighboring UMTS cells use indexes 0 to 3 of the neighboring
UMTS cell table. If the MS reports an EMR, the neighboring GSM and UMTS cells all use
the indexes of a hybrid neighboring GSM/UMTS cell table. In the hybrid neighboring
GSM/UMTS cell table, indexes 0 to 4 are assigned to the neighboring GSM cells and indexes
5 to 8 are assigned to the neighboring UMTS cells.
When the MS reports an EMR, the actual signal levels of the serving cell and its neighboring
cells no longer follow the mapping between RXLEV values (0 through 63) and dBm values
(–110 through –47). Instead, the signal levels of the serving cell and its neighboring cells can
be obtained based on the SCALEORDER IE contained in the MI or 2quater SI. The
SCALEORDER IE indicates the mapping offset.
 If SCALEORDER (BSC6900, BSC6910) is set to ADD10dB(+10dB), RXLEV values
0 through 63 map to dBm values –100 through –37.
 If SCALEORDER (BSC6900, BSC6910) is set to ADD0dB(+0dB), RXLEV values 0
through 63 map to dBm values –110 through –47.
To ensure compatibility between EMRs and common MRs, the mapping between RXLEV values 0 through 63
and dBm values –110 through –47 applies when an MS reports an EMR.
3.2 EMR Preprocessing

The EMR feature requires support from the BTS. When sending the Measurement Result
message to the BSC, the BTS determines whether EMR is enabled by checking the setting of
BTSMESRPTPREPROC (BSC6900, BSC6910).
WhenMEASURETYPE (BSC6900, BSC6910) is set to EnhMeasReport(Enhance Measure
Report), the BSC and MS support EMR, but the BTS does not support EMR:
 If BTSMESRPTPREPROC (BSC6900, BSC6910) is set to BSC_Preprocessing(BSC
preprocessing), the BTS forwards an EMR to the BSC without decoding it.
 If BTSMESRPTPREPROC (BSC6900, BSC6910) is set to BTS_Preprocessing(BTS
preprocessing), the BTS cannot decode an EMR.
When MEASURETYPE (BSC6900, BSC6910) is set to EnhMeasReport(Enhance Measure
Report) and BTSMESRPTPREPROC (BSC6900, BSC6910) is set to
BTS_Preprocessing(BTS preprocessing):
 Uplink: The BTS preprocesses an EMR in the same way it preprocesses a common
MR.
 Downlink: The BTS preprocesses an EMR in a way different from the way it
preprocesses a common MR. The differences lie in the interpolating and filtering of
downlink MRs and the number of neighboring GSM and UMTS cells involved in layer 3
MRs.
The preprocessing of downlink MRs involves the following filtering-related parameters:
 MBSIGNLEN (BSC6900, BSC6910)
 MBTRAFFLEN (BSC6900, BSC6910)
 CBSIGNLEN (BSC6900, BSC6910)
 CBTRAFFLEN (BSC6900, BSC6910)
 RQSIGNLEN (BSC6900, BSC6910)
 RQTRAFFLEN (BSC6900, BSC6910)
 NRBSDCCHFFLEN (BSC6900, BSC6910)
 NRBTCHFFLEN (BSC6900, BSC6910)
The preceding filtering-related parameters do not take effect during MR preprocessing if MEASURETYPE
(BSC6900, BSC6910) is set to EnhMeasReport(Enhance Measure Report) and BTSMESRPTPREPROC
(BSC6900, BSC6910) is set to BSC_Preprocessing(BSC preprocessing).
3.3 2G/3G Interoperability
2G/3G interoperability has the following impacts on EMR:

 If the MI or 2quater SI does not carry information about neighboring UMTS cells, the
SI is not controlled by the license for 2G/3G interoperability.
 If the MI or 2quater SI carries information about neighboring UMTS cells, the SI is
controlled by the license for 2G/3G interoperability.
3.4 DTX
An EMR indicates whether DTX is used. In an EMR, the downlink signal quality and receive
signal level use the MEAN_BEP and RXLEV_VAL values, respectively, irrespective of
whether DTX is enabled.
3.5 Handover and Power Control
EMR has significant impact on the power control and handover algorithms.
An EMR uses MEAN_BEP, instead of RXQUAL, to evaluate signal quality. Compared with
RXQUAL, BEP has higher precision, especially when the signal quality is poor.
MEAN_BEP improves the performance of signal quality-based algorithms. Therefore, all the
algorithms that used RXQUAL to evaluate signal quality now need to switch to MEAN_BEP.
The involved parameters are MBSIGNLEN (BSC6900, BSC6910) and MBTRAFFLEN
(BSC6900, BSC6910).
Power control parameters remain unchanged. Power control and handover algorithms also
remain unchanged. Table 3-1 lists the mappings between MEAN_BEP and RXQUAL x 10
values.
Table 3-1 Mappings between MEAN_BEP and RXQUAL x 10 values
MEAN_BEP CIR RXQUAL x 10
0 0 76
1 10 73
2 30 70
3 45 66
4 60 63
5 75 60
6 85 56
7 95 53
8 105 50
9 115 46
10 125 43
11 135 40
12 145 37
13 155 33
14 160 30
15 165 27
16 175 23
MEAN_BEP CIR RXQUAL x 10
17 180 20
18 185 17
19 195 13
20 200 10
21 205 7
22 210 3
23 215 0
24 225 0
25 230 0
26 235 0
27 240 0
28 245 0
29 250 0
30 250 0
31 250 0
3.6 Faulty EMR MS Differentiated Processing
Although mainstream MSs sold on the market report EMRs to the BSS, some MSs may have
defective EMR capability, and handover failures or call drops are likely to occur if the EMR
feature is applied to these MSs. Such an MS is referred to as a faulty EMR MS in this
document.
The faulty EMR MS differentiated processing function is introduced to resolve this issue.
This function consists of two subfunctions: faulty EMR MS identification and faulty EMR
MS processing.
EmrMsCapIdeSwitch (BSC6900, BSC6910) controls whether to enable faulty EMR MS
identification. When this parameter is set to ON(On), the BSS identifies faulty EMR MSs
and stores the information about them in an EMR MS capability database.
EmrMsCapProSwitch (BSC6900, BSC6910) controls whether to enable faulty EMR MS
processing. When this parameter is set to ON(On), the BSS determines whether an EMR MS
is faulty during the attach procedure by checking the MS's international mobile equipment
identity (IMEI) against the EMR MS capability database. If the EMR MS fully supports
EMR, the MS reports an EMR to the BSS. If the EMR MS is faulty, the MS reports a
common MR to the BSS.
Faulty EMR MS differentiated processing prevents handover failures and call drops for faulty
EMR MSs when the EMR feature is enabled. However, enabling this function prolongs the
attach delay, increases the overall call drop rate, and lowers high quality indicators (HQIs).
Therefore, after you have enabled the EMR feature the first time, enable the faulty EMR MS
differentiated processing function for a period of time to collect information about faulty
EMR MSs. Then disable the faulty EMR MS differentiated processing function. After that,
enable and then disable the faulty EMR MS differentiated processing function to update the
EMR MS capability database at fixed intervals.
3.6.1 EMR MS Capability Database
The results of faulty EMR MS identification are not automatically saved to the EMR MS
capability database. In this version, the results can be imported to the EMR MS capability
database through the following method:
After the function of faulty EMR MS differentiated processing runs over a period, execute
the BSC MML command EXP MSTACCAPMML to export the results of faulty EMR MS
identification to an MML script, download the script through File Manager of the WebLMT,
and then execute the script through a batch processing on the BSC to import the results to the
EMR MS capability database. The MML script includes the following information:
 File saving directory: bam version_x ftp ms_tac_cap;
 The script file can be located in the save directory through File Manager of the WebLMT.
 version_x: OMU workspace, which is indicated by Workarea flag in the MML command LST
OMUAREA output.
 File name: Name of the MML script, which is specified using the parameter FN in
the command EXP MSTACCAPMML.
 File content: The following is an example of commands in the MML script. Bit 1 of
DifferFeatureSwitch is the result of faulty EMR MS identification.
Example: ADD GMSTACCAP:TAC="00112233", DIFFERFEATURESWITCH=BIT0-
0&BIT1-1&BIT2-0&BIT3-0&BIT4-0&BIT5-0&BIT6-0&BIT7-0&BIT8-0&BIT9-
0&BIT10-0&BIT11-0&BIT12-0&BIT13-0&BIT14-0&BIT15-0, MINECNOOFFVAL=0,
MINRSCPOFFVAL=0, INTERRATHOEN=YES;
3.6.2 Automatic Sharing of EMR MS Capability
The BSC stores the EMR MS capability only in its EMR MS capability database after
collecting the information. The automatic sharing of EMR MS capability function enables
multiple BSCs to automatically share the EMR MS capability information among one
another. This noticeably improves the efficiency in obtaining EMR MS capability
information and reduces the negative impact of identifying faulty EMR MSs on KPIs.
With the automatic sharing of EMR MS capability function, the user can specify the source
and target BSCs on the U2020 for sharing EMR MS capability information. Figure 3-1 shows
an example. BSCs 1 and 2 are source BSCs, and BSCs 1 through 4 are target BSCs.
Figure 3-1 Automatic sharing of EMR MS capability
This function is supported in U2020 V200R013C00 and later. For details, see U2020 online
help information.
4 Related Features
None.
GBFD-115830 VAMOS -
GBFD-118702 MOCN Shared Cell -
GBFD-191201 Uplink CoMP (Joint RX) -
Impacted Features
None.
Before deploying the EMR feature, collect the following information:

 EMR MS penetration rate
Make sure that the EMR MS penetration rate on your network is higher than 40% before you enable the EMR
feature.
5.2 Deploying EMR
Aspect Requirement
BSC None
BTS None
GSM networking None
MS MSs support EMR.
MSC None

Others The test cell supports the EMR feature and

has been configured with available
neighboring cells.
5.2.2 Precautions
Do not dynamically change the setting of BTSMESRPTPREPROC (BSC6900, BSC6910) or

the neighbor relationship between GSM and UMTS cells when the EMR feature is enabled.
This is because dynamically changing the setting of BTSMESRPTPREPROC (BSC6900,
BSC6910) or the neighbor relationship between GSM and UMTS cells has the following
negative impacts when MEASURETYPE is set to EnhMeasReport(Enhance Measure
Report):
 IfBTSMESRPTPREPROC (BSC6900, BSC6910) is set to BTS_Preprocessing(BTS
preprocessing):
The BTS needs to obtain accurate information about neighboring cells before it can
preprocess an EMR. If neighbor relationship between GSM and UMTS cells is
dynamically added or deleted, the BSC will forcibly hand over MSs to another cell. If a
handover fails, the BSC directly releases the call, therefore increasing the call drop rate.
 If BTSMESRPTPREPROC (BSC6900, BSC6910) is changed to
BSC_Preprocessing(BSC preprocessing):
The BTS continues to preprocess the EMRs received from MSs that have ongoing calls. If
neighbor relationship between GSM and UMTS cells is dynamically added or deleted, the
BSC does not forcibly hand over the MSs to another cell. The BTS, however, may have
trouble in decoding the EMRs.
5.2.3 Activation
Using MML Commands
1. On the BSC LMT, run the SET GCELLCCUTRANSYS command with

Measurement Report Type set to EnhMeasReport(Enhanced Measurement Report)
for the specified cell.
2. (Optional) If you need to detect faulty EMR MSs, run the SET
GCELLCCUTRANSYS command with Faulty EMR MS TAC Collection Switch set
to ON(On).
3. Run the SET GCELLCCUTRANSYS command with MS Differentiated
Processing EMR Switch set to ON(On).
4. Run the SET GCELLSOFT command with Single-User Tracing set to YES(YES).
//Activating EMR
SET GCELLCCUTRANSYS: IDTYPE=BYID, CELLID=1024,
MEASURETYPE=EnhMeasReport;
SET GCELLCCUTRANSYS: IDTYPE=BYID, CELLID=1024, EmrMsCapProSwitch=ON;
SET GCELLCCUTRANSYS: IDTYPE=BYID, CELLID=1024, EmrMsCapIdeSwitch=ON;
SET GCELLSOFT: IDTYPE=BYID, CELLID=1024, TestUserTraceFun=YES;
Using the CME
When configuring the EMR feature on the CME, you must perform a single configuration first, and then
perform batch modifications if required.

Table 5-2 Configuring EMR parameters on the CME

Modification
Center
1 GCELLCCUT BSC6900/BS Measurement MEASURET Yes

RANSYS C6910 Report Type YPE
Faulty EMR EmrMsCapP Yes

MS TAC roSwitch
Collection
Switch
MS EmrMsCapId Yes
Differentiated eSwitch
Processing
EMR Switch
2 GCELLSOFT BSC6900/BS Single-User TestUserTra Yes

C6910 Tracing ceFun
This example assumes that cells 0 and 1 are neighboring GSM cells.
1. Use an MS to initiate a call in cell 0.
2. Check whether the EMR traced over the radio signaling link (RSL) on the Abis
interface contains the EMR IE.
Expected result: The call initiated by a functional EMR MS succeeds and the voice
quality is good. The EMR traced over the Abis interface for cell 0 contains the EMR IE,
which is the "enhanced-measurement-report-struct" IE in the original EMR or the "pre-
proc-emr" IE in the preprocessed EMR.
The BTS will report a common MR if the MS does not support the EMR feature or a faulty EMR MS is
used.
5.2.5 Deactivation
Using MML Commands
1. On the BSC LMT, run the SET GCELLCCUTRANSYS command with

Measurement Report Type set to ComMeasReport(Common Measurement Report)
for the specified cell.
2. (Optional) Run the SET GCELLCCUTRANSYS command with Faulty EMR MS
TAC Collection Switch set to OFF(Off).
3. Run the SET GCELLCCUTRANSYS command with MS Differentiated
Processing EMR Switch set to OFF(Off).
4. Run the SET GCELLSOFT command with Single-User Tracing set to NO(NO).
//Deactivating EMR
SET GCELLCCUTRANSYS: IDTYPE=BYID, CELLID=1024,
MEASURETYPE=ComMeasReport;
SET GCELLCCUTRANSYS: IDTYPE=BYID, CELLID=1024, EmrMsCapProSwitch=OFF;
SET GCELLCCUTRANSYS: IDTYPE=BYID, CELLID=1024, EmrMsCapIdeSwitch=OFF;
SET GCELLSOFT: IDTYPE=BYID, CELLID=1024, TestUserTraceFun=NO;
Using the CME
When configuring the EMR feature on the CME, you must perform a single configuration first, and then
perform batch modifications if required.


Table 5-3 Configuring EMR parameters on the CME
SN MO NE Parameter Parameter ID Configurable
Name in CME Batch
Modification
Center
1 GCELLCCUT BSC6900/BS Measurement MEASURET Yes

RANSYS C6910 Report Type YPE
Faulty EMR EmrMsCapP Yes

MS TAC roSwitch
Collection
Switch
MS EmrMsCapId Yes
Differentiated eSwitch
Processing
EMR Switch
2 GCELLSOFT BSC6900/BS Single-User TestUserTra Yes

C6910 Tracing ceFun
6 Parameters
 BSC6910 GSM Parameter Reference:contains the parameters related to the BSC6910
reference?
7 Counters
counters.
reference?
8 Glossary
1. 3GPP TS 44.018 "Mobile radio interface layer 3 specification; Radio Resource

Control (RRC) protocol"
GSM BSS
GBSS19.1
Assignment and Immediat

Assignment Feature
Issue 01
Date 2017-03-15

Notice

Address:
Website: https:/
3.6.28 Contents
1.1 Scope
1.3 Change History
2 Overview
2.1 Introduction
3 Immediate Assignment
3.1 Immediate Assignment Procedure
3.2 Immediate Assignment Combination
4 Assignment
4.1 Assignment Procedure
4.2 Assignment Classification
5.2 Precautions
5.3 Activation
5.5 Deactivation
6 Parameters
7 Counters
8 Glossary
1.1 Scope
This document describes GBFD-110502 Assignment and Immediate Assignment, including

its technical principles and engineering guidelines.
Purpose

Software Interfaces
1.3 Change History
 Feature change
01 (2017-03-15)
Compared with Issue 02 (2017-01-16) of GBSS18.1, 01 (2017-03-15) of GBSS19.1 includes

the following changes.
Feature change None None
Editorial change Modified 3.1 Immediate Assignment None

Procedure.
2 Overview
2.1 Introduction
When an MS initiates a call or needs to switch from a signaling channel to a TCH, the BSC
needs to assign a channel to the MS.
When the MS initiates a call, the BSC needs to assign an SDCCH or a TCH (the TCH is used
for signaling) according to the specific call establishment cause. This procedure is called
immediate assignment.
After receiving a channel request from the MS, the MSC sends the BSC an Assignment
Request message, instructing the BSC to assign a suitable channel to the MS. The channel to
be allocated must meet the requirements of the MSC and MS, such as the channel type,
speech version, and MS frequency capability. This procedure is called assignment.
The immediate assignment and assignment procedures are very important for call
establishment. Proper immediate assignment and assignment algorithms ensure optimal KPIs,
thereby improving the performance of radio networks.
 Through the immediate assignment procedure, a radio resource (RR) connection is
established between the MS and the network.
 Through the assignment procedure, the MSC assigns a specific TCH to the MS so that
a stable connection is established between the MS and the network.
The processing during the immediate assignment and assignment procedures varies based on
different conditions. For details, see Channel Management Feature Parameter Description.
Assignment and √ √ √ √
Immediate
Assignment
3 Immediate Assignment
3.1 Immediate Assignment Procedure
The immediate assignment procedure is initiated by an MS, with the purpose of establishing
an RR connection between the MS and the network.
The immediate assignment procedure is shown in Figure 3-1.
Figure 3-1 Immediate assignment procedure
1. The MS sends a Channel Request message to the BTS on the RACH.

After initiating the immediate assignment procedure, the MS always listens to the BCCH
and the corresponding CCCH. If the MS does not receive the Immediate Assignment
Command message or Immediate Assignment Extended message, it resends the Channel
Request message at a specified interval. When the number of times that the Channel
Request message is resent exceeds MSMAXRETRAN (BSC6900, BSC6910), the
immediate assignment procedure fails.
2. The BTS sends a Channel Required message to the BSC.
3. After the reception of the Channel Required message, the BSC assigns a signaling
channel and sends the BTS a Channel Activation message, which carries information
elements (IEs) such as Activation Type, Channel Description, Level, and Time Advance
(TA).
4. After the reception of the Channel Activation message, if the IEs carried in the
message are correct, the BTS turns on the power amplifier on the specified channel to
receive uplink messages. At the same time, the BTS sends the BSC a Channel Activation
Acknowledge message carrying the absolute frame number, which is used by the BSC to
determine Starting Time.
5. The BSC sends the MS an Immediate Assignment Command message, instructing the
MS to access the specified channel. The specified channel can be either an SDCCH or a
TCH.
When IMMASSEN (BSC6900, BSC6910) is set to YES(Yes):
 The BSC preferentially allocates TCHs to the MS if both of the following
conditions are met:
For MOCs, IMMTCHMOC (BSC6900, BSC6910) is set to YES(Yes). For MTCs,
IMMTCHMTC (BSC6900, BSC6910) is set to YES(Yes).
The TCH load in the cell is less than the value of ImmTchLoadThres.
HRATESPT (BSC6900, BSC6910) is set to YES(Yes) if TCHH very early assignment
is required.
 The BSC preferentially allocates SDCCHs to the MS in other cases. If no
SDCCHs are available, the BSC allocates TCHs to the MS.
Setting ImmTchLoadThres (BSC6900, BSC6910) to an appropriate value reduces
impacts on the channel congestion rate.
During the calculation of the TCH load in a concentric cell, the TCH load in the underlaid subcell is used
as the TCH load in the concentric cell.
The IMMEDIATE ASSIGNMENT COMMAND message can be resent only when

IMMASSRESENDEN (BSC6900, BSC6910) is set to YES(Yes) and the delay time is
within IMMASSMAXDELAYTIME (BSC6900, BSC6910). When the number of times that
the Immediate Assignment Command message is resent exceeds
IMMASSMAXSENDNUM (BSC6900, BSC6910), the Immediate Assignment Command
message is not resent.
6. The MS sends a Set Asynchronous Balanced Mode (SABM) frame on the main
DCCH to access the network.
7. The BTS answers with an Unnumbered Acknowledge (UA) frame on the main
DCCH.
8. The BTS sends an Establish Indication message to the BSC.
The MS may send several Channel Request messages during one RR connection
establishment attempt. In this case, the BSS activates multiple signaling channels,
whereas the MS uses only one channel. The other channels cannot receive the Establish
Indication message from the BTS for a long time. As a result, the BSC releases the
channels at expiry of timer ESTABINDTIMER (BSC6900, BSC6910).
3.2 Immediate Assignment Combination
Generally, the Immediate Assignment Command message from the BSC to the BTS contains
the response to the channel request from only one MS. On the UM interface, however, the
responses to the Channel Request message are of three types: Immediate Assignment
Command, Immediate Assignment Extended, and Immediate Assignment Reject. One
Immediate Assignment Extended message contains the contents of the Immediate
Assignment Command message (for acknowledgement) sent to two MSs over the Abis
interface. One Immediate Assignment Reject message contains the contents of the Immediate
Assignment Command message (for rejection) sent to four MSs. Therefore, to improve the
message sending efficiency, the BTS encapsulates multiple Immediate Assignment
Command messages received from the BSC into one Immediate Assignment Extended or
Immediate Assignment Reject message before sending them to MSs. This procedure is called
immediate assignment combination.
The Wait Indication IE in the Immediate Assignment Reject message from the BSC to the
MS carries timer T3122.
Upon receiving the Immediate Assignment Reject message, the MS attempts to access the
network at expiry of timer IMMREJWAITINDTIMER (BSC6900, BSC6910).
4 Assignment
4.1 Assignment Procedure
In the assignment procedure, the network assigns a TCH to an MS.

The assignment procedure is shown in Figure 4-1.
Figure 4-1 Assignment procedure
1. The MSC sends an Assignment Request message to the BSS based on the service
request and then starts timer T10. Upon receiving the Assignment Request message from
the MSC, the BSC checks the channel type. If a PS service is requested, the BSC
determines whether the requested service is supported according to the setting of the
DATATRAFFSET (BSC6900, BSC6910) parameter.
2. The BSC sends the BTS a Channel Activation message to activate the corresponding
terrestrial resources. The message carries IEs such as Activation Type, Channel
Description, Level, and TA.
3. Upon receipt of the Channel Activation message, if the IEs carried in the message are
correct, the BTS turns on the power amplifier on the specified channel to receive uplink
messages. At the same time, the BTS sends the BSC a Channel Activation Acknowledge
message carrying the absolute frame number, which is used by the BSC to determine
Starting Time.
4. After receiving the Channel Activation Acknowledge message, the BSC sends the
Assignment Command message on the signaling channel to the MS and starts timer
ASSTIMER (BSC6900, BSC6910). The Assignment Command message carries IEs such
as Channel Description, Power Command, and Channel Mode.
5. After receiving the Assignment Command message, the MS starts to transmit and
receive signaling over the TCH. The MS sends an SABM message to the network over
the FACCH through frame stealing. The SABM frame is the first frame for establishing
the asynchronous balanced mode. Compared with the immediate assignment procedure,
the assignment procedure does not have layer 3 messages.
6. After receiving the SABM message, the BTS sends a UA frame to the MS over the
FACCH. The layer 3 messages are not carried.
7. At the same time, the BTS sends the BSC an ESTABLISH INDICATION message
without the layer 3 messages. Then, the BSC responds with a UA frame for
acknowledgement.
8. After receiving the UA frame, the MS sends an Assignment Complete message to the
network over the FACCH, indicating that the TCH is established successfully. When
receiving the Assignment Complete message, the BSC stops timer ASSTIMER
(BSC6900, BSC6910).
9. In addition, the BSC fills the message with the corresponding information indicated
by the parameter AVer (BSC6900, BSC6910) and sends the message to the MSC. Upon
receiving the Assignment Complete message, the MSC stops timer T10.
4.2 Assignment Classification
In different scenarios, the assignment procedure may play different roles during the call. The
assignment type has certain impacts on allocation and seizure of the network resources.
According to the roles of the assignment procedure in the call, the assignment procedure is
classified into mobile originating call establishment without OACSU (early assignment),
mobile originating call establishment with OACSU (late assignment), mobile originating call
establishment with very early assignment, mobile terminating call establishment without
OACSU (early assignment), mobile terminating call establishment with OACSU (late
assignment), and mobile terminating call establishment with very early assignment.
Mobile Originated Call Establishment Without OACSU (Early Assignment)
Mobile originating call establishment without OACSU (early assignment) refers to the
procedure in which the calling MS is assigned a TCH before the call is established.
After the immediate assignment is complete, the network sends the MS an Assignment
Command message that requests the calling MS to occupy the TCH even if the Altering
message is not received. In this case, the ringing tone is generated by the network. The
mobile originating call establishment without OACSU (early assignment) procedure is shown
in Figure 4-2.
Figure 4-2 Mobile originated call establishment without OACSU (early assignment)
Mobile Originated Call Establishment with OACSU (Late Assignment)
In this mode, the network sends the MS an Assignment Command message that requests the
calling MS to occupy a TCH only after the network receives the Alerting message from the
called party. In this case, the ringing tone is generated by the MS because no TCH is
available before the RR connection is established. The mobile originating call establishment
with OACSU (late assignment) procedure is shown in Figure 4-3.
Figure 4-3 Mobile originated call establishment with OACSU (late assignment)
Mobile Originated Call Establishment with Very Early Assignment
Mobile originating call establishment with very early assignment refers to the procedure in
which a TCH instead of an SDCCH is assigned to the calling MS during the immediate
assignment procedure.
If IMMASSEN (BSC6900, BSC6910) is set to YES(Yes) and no SDCCH is available in the
serving cell of the calling MS, a TCH is allocated during the immediate assignment
procedure.
Mobile originating call establishment with very early assignment can speed up connection
establishment. The network performs authentication, ciphering, other signaling exchanges,
and follow-up call connection procedures on the TCH. In this case, the TCH is used for
signaling. Upon receiving the Assignment Request message from the MSC, the BSC changes
the TCH used for signaling to a real TCH through the Mode Modify command. The mobile
originating call establishment with very early assignment procedure is shown in Figure 4-4.
Figure 4-4 Mobile originated call establishment with very early assignment
Mobile Terminated Call Establishment Without OACSU (Early Assignment)
Mobile terminating call establishment without OACSU (early assignment) refers to the
procedure in which the called MS is assigned a TCH before the call is established.
Mobile terminating call establishment is initiated by the network sending a Paging Request
message. After the immediate assignment procedure is complete, the network sends an
Assignment Command message to the called MS to require the MS to occupy a TCH before
answering the phone. In this case, the ringing tone is generated by the network.
The mobile terminating call establishment without OACSU (early assignment) procedure is
shown in Figure 4-2.
Mobile Terminated Call Establishment with OACSU (Late Assignment)
In this mode, the network sends the MS an Assignment Command message that requests the
called MS to occupy a TCH only after the network receives the Alerting message. In this
case, the ringing tone is generated by the MS because no TCH is available before the RR
connection is established.
The mobile terminating call establishment with OACSU (late assignment) procedure is
shown in Figure 4-3.
Mobile Terminated Establishment with Very Early Assignment
Mobile terminating call establishment with very early assignment refers to the procedure in
which a TCH instead of an SDCCH is assigned to the called MS during the immediate
assignment procedure.
If IMMASSEN (BSC6900, BSC6910) is set to YES(Yes) and no SDCCH is available in the
serving cell of the called MS, a TCH is allocated during the immediate assignment procedure.
Mobile terminating call establishment with very early assignment can speed up connection
establishment. The network performs authentication, ciphering, other signaling exchanges,
and follow-up call connection procedures on the TCH. Upon receiving the Assignment
Request message from the network, the BSC changes the TCH used for signaling to a real
TCH through the Mode Modify command.
The mobile terminating call with very early assignment procedure is shown in Figure 4-4.

Aspect Requirement
BSC None
BTS None
GSM networking None
MS None
MSC None
License None
Others None
5.2 Precautions
If all of the following conditions are met, the BSC allocates TCHs to an ongoing immediate
assignment procedure to ensure successful network access:
 IMMASSEN (BSC6900, BSC6910) is set to YES(Yes).
 No SDCCH resource is available.
 The CN allows MSs to use TCHs, as indicated by the Channel Needed IE.
This operation increases the SMS delay and CSFB delay of some MSs, and may even cause
SMS sending or receiving failures or CSFB failures.
Assignment and immediate assignment are two important procedures during call setup.
Normal immediate and immediate assignment procedures do not require setting of any
parameter. Parameter setting is required only in the immediate assignment of TCHs. The
following section describes how to configure the function of immediate TCH assignment.
5.3 Activation
Using MML Commands
On the BSC LMT, run the SET GCELLBASICPARA command with TCH Immediate
Assignment set to YES(Yes).
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, IMMASSEN=YES;
Using the CME

1. When an MS camps on a cell and no MS is processing services in the cell, block the
SDCCHs and disable the SDCCH Dynamic Adjustment feature.
 On the BSC LMT, run the SET GTRXCHANADMSTAT command to block
an SDCCH. In this step, set Channel No. to the number of the SDCCH and
Administrative State to Lock(Lock).
 Run the SET GCELLBASICPARA command to disable the SDCCH
Dynamic Adjustment feature. In this step, set SDCCH Dynamic Allocation Allowed
to NO(No).
2. Use the MS to initiate a call.
3. View messages traced over the Abis interface.
In the Abis interface message tracing window, the CHANNEL ACTIVATION message
is traced. The Channel Mode and Type field indicates that a TCH, instead of an SDCCH,
is assigned during immediate assignment. During assignment, the Mode Modify Request
and Mode Modify Acknowledge messages are traced.
4. After the verification, unblock the SDCCH and enable the SDCCH Dynamic
Adjustment feature immediately.
 Run the SET GTRXCHANADMSTAT command to unblock an SDCCH. In
this step, set Channel No. to the number of the SDCCH and Administrative State to
Unlock(Unlock).
 Run the SET GCELLBASICPARA command to enable the SDCCH
Dynamic Adjustment feature. In this step, set SDCCH Dynamic Allocation Allowed
to YES(Yes).
5.5 Deactivation
Using MML Commands
On the BSC LMT, run the SET GCELLBASICPARA command with TCH Immediate
Assignment set to NO(No).
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, IMMASSEN=NO;
Using the CME
6 Parameters
 BSC6910 GSM Parameter Reference:
contains the parameters related to the BSC6910
reference?
7 Counters
counters.
reference?
8 Glossary

1. 3GPP TS 48.008 Mobile Switching Centre - Base Station system (MSC-BSS)

interface; Layer 3 specification
2. 3GPP TS 44.018 Mobile radio interface layer 3 specification; Radio Resource Control
(RRC) protocol

GBSS Feature Documentation GBSS21.1 - 08 20210309221351

Uploaded by

Copyright:

Available Formats

You might also like

GBSS Feature Documentation GBSS21.1 - 08 20210309221351

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GBSS Feature Documentation GBSS21.1 - 08 20210309221351

Uploaded by

Copyright:

Available Formats

Handover Re-establishment

Handover Re-establishment Feature

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.

Huawei Technologies Co., Ltd.

This document describes GBFD-510502 Handover Re-establishment, including its technical

Feature Parameter Description documents are intended to acquaint readers with:

This issue does not include any changes.

Compared with Issue 01 (2013-05-06) of GBSS15.0, Draft A (2015-12-31) of GBSS18.1

Change Type Change Description Parameter Change

Feature change Added the Added the

Editorial change None None

Handover Re-establishment does not support directed retry.

2.2 NEs Supporting the Feature

Table 2-1 NEs supporting the feature

3.1 Implementation in the BSS

The implementation of Handover Re-establishment in the base station subsystem (BSS) is as

3.2 Impact on the KPI

4.1 Deployment Requirements

Table 4-1 Deployment requirements

Related features None

BTS BTS3900B/E not support Handover Re-establishment

GSM networking None

Using MML Commands

On the BSC LMT, perform the following steps:

MML Command Examples

SET GCELLSOFT: IDTYPE=BYID, CELLID=0, ACTL2REEST=YES;

Using the CME

For detailed operations, see CME-based Feature Configuration.

Using MML Commands

MML Command Examples

SET GCELLSOFT: IDTYPE=BYID, CELLID=0, ACTL2REEST=NO;

Using the CME

For detailed operations, see CME-based Feature Configuration.

Radio Resource Managem

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.

Huawei Technologies Co., Ltd.

Huawei Industrial Base Bantian, Longgang

2 NEs Supporting the Feature

4 Radio Link Management

5 Radio Common Channel Management

6 Radio Dedicated Channel Management

1 About This Document

Feature Parameter Description documents are intended to acquaint readers with:

This issue does not include any changes.

Compared with Issue 01 (2015-04-20) of GBSS17.1, Draft A (2018-12-30) of GBSS21.1

Change Type Change Description Parameter Change

Feature Added independent configuration of TSC Added the following

Editorial None None

Table 2-1 NEs supporting the feature

Feature BSC6900 BSC6910 GBTS eGBTS

This section describes the GBFD-111001 TRX Management feature.

3.2.1 Radio Resource Indication

3.2.2 SACCH Filling Information Modify

3.2.3 Flow Control

4 Radio Link Management

This chapter describes the GBFD-111002 Radio Link Management feature.

4.2.1 Link Establishment Indication

4.2.2 Link Establishment Request