Connection Management

Contents
3.6.17 Connection Management

GSM BSS
GBSS22.1

Connection Management Feature

Parameter Description
Issue 01

Date 2020-04-07
 HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2021. 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.17 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 Call Control
3.1 Overview
3.2 Call Classification
3.2.1 MOT
3.2.2 MTC
 3.2.3 Emergency Call
3.3 Call Release
3.3.1 Overview
3.3.2 MS-Initiated Call Release
3.3.3 Network-Initiated Call Release

4 Call Reestablishment
4.1 Overview
4.2 Call Reestablishment Procedure

5 TCH Re-assignment
5.1 Overview
5.2 TCH Re-assignment Procedure

6 MSC Re-Assignment
6.1 Overview
6.2 Procedure

7 Engineering Guidelines
7.1 Deploying Call Control
7.2 Deploying Call Reestablishment
7.2.1 Deployment Requirements
7.2.2 Activation
7.2.3 Activation Observation
7.2.4 Deactivation
7.3 Deploying TCH Re-assignment
7.3.1 Deployment Requirements
7.3.2 Activation
7.3.3 Activation Observation
7.3.4 Deactivation
7.4 Performance Monitoring

8 Parameters

9 Counters

10 Glossary

11 Reference Documents

1 About This Document

1.1 Scope
 This document describes Connection Management, including its technical principles and
engineering guidelines. This document covers the following features:
• GBFD-110501 Call Control
• GBFD-110503 Call Reestablishment
• GBFD-112501 TCH Re-assignment
• MSC Re-assignment
1.2 General Statements

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 (2020-04-07)
 This issue does not include any changes.

Draft A (2020-01-18)

Compared with Issue 01 (2019-06-06) of GBSS21.1, Draft A (2020-01-18) of GBSS22.1

includes the following changes.

Change Type Change Description Parameter Change

Feature change Changed the name of CME to MAE- None

Deployment.

Editorial change None None

2 Overview

2.1 Introduction

GBFD-110501 Call Control is a basic feature that allows an operator to provide circuit switched
(CS) services. With this feature, the base station subsystem (BSS) provides an MS with radio
resources and terrestrial circuits for making a call and assists the mobile switching center (MSC)
during the entire call handling process.
When an MS encounters a radio link failure during a call, GBFD-110503 Call Reestablishment
can be used to reestablish the radio link connection so that the original call can proceed. This
shortens the call intermission and therefore improves user experience.
GBFD-112501 TCH Re-assignment enables the BSC to reassign a traffic channel (TCH) to an
MS after a TCH assignment fails and the MS returns to the standalone dedicated control channel
(SDCCH).
2.2 NEs Supporting the Feature

Table 2-1 NEs supporting the feature

Feature BSC6900 BSC6910 GBTS eGBTS

Call Control √ √ √ √

Call √ √ √ √
Reestablishment

TCH Re- √ √ √ √
assignment
 √ indicates that the NE supports this feature. × indicates that the NE does not support this feature.

3 Call Control

3.1 Overview

The feature involved is GBFD-110501 Call Control.

GBFD-110501 Call Control is a basic feature that allows an operator to provide CS services.
With call control, the BSS provides an MS with radio resources and terrestrial circuits for
making a call and assists the MSC during the entire call handling process.
BSS supports the mobile-originated call (MOC), mobile-terminated call (MTC), and emergency
call. With specific resource management algorithms and control functions, the base station
controller (BSC) provides transport channels for the transmission of call control signaling
between the MS and MSC by setting up radio resource (RR) connections.
During the call control process, the BSS supports priority-based handling. For example, the
emergency call has a higher priority than a common call. Therefore, the emergency call can
obtain the required resources preferentially compared with common calls. Concerning the BSC,
call control involves the allocation of radio channel resources, allocation of A interface resources
in cooperation with the MSC, and release of traffic channels. The basic call processes are as
follows:
• MOC
• MTC
• Emergency call
• MS-initiated call release
• Network-initiated call release
3.2 Call Classification

3.2.1 MOT

In terms of assignment, MOT is classified into the following three types:

• Early assignment
• Late assignment
• Very early assignment
The selection of early assignment and late assignment is determined by the MSC. The very early
assignment is determined by the BSS based on the usage of radio resources.

For details about early assignment, late assignment, and very early assignment, see Assignment and Immediate
Assignment Feature Parameter Description.

3.2.2 MTC

MTC is a process through which the network assigns a traffic channel to a called MS.
Figure 3-1 shows the MTC procedure.
Figure 3-1 MTC procedure
 The Paging message can be transmitted directly from the MSC to the BSC over the A interface or from the SGSN to
the BSC over the Gb interface.
For detailed descriptions of the MTC procedure, see 3GPP TS24.008, TS24.080, TS48.008, TS44.018, and
TS48.058.

3.2.3 Emergency Call

Emergency call is performed by users in emergency situations to contact the outside world. It is
critical for users in emergency situations. For example:
• An MS in an emergency situation can call a specific number for the maximum help
free of charge. The emergency call is allowed even if the MS is out of service or the
bill is overdue.
• An MS in an emergency situation can have a higher level of access priority when
dialing an emergency call. The MS can contact the emergency department even in a
congested cell.
The emergency call procedure is similar to the MOC procedure, except that the
EMERGENCY_SETUP message is used instead of the Setup message.
3.3 Call Release

3.3.1 Overview

In terms of the network element (NE) that initiates the procedure, call release is classified into
MS-originated call release and network-initiated call release.
3.3.2 MS-Initiated Call Release

The MS can initiate call release if necessary (when the user hangs up for example) after
accessing the network normally.
Figure 3-2 shows the procedure of MS-initiated call release.
Figure 3-2 Procedure of MS-initiated call release

The procedure of MS-initiated call release is described as follows:

1. After the call is completed and the calling party hangs up, the calling MS sends a
Disconnect message to the MSC and starts timer T305. This message carries the
cause about the release.
 2. Upon receiving the Disconnect message from the MS, the MSC responds with a
Release message and starts timer T308. In addition, the MSC sends a Disconnect
message to the called party.
3. Upon receiving the Release message from the MSC, the MS stops timer T305,
releases the MM connection, then sends a Release Complete message to the MSC.
4. Upon receiving the Release Complete message from the MS, the MSC stops timer
T308, releases the MM connection, and sends a Clear Command message to the BSC
to instruct the BSC to release the occupied resources on the A and Um interfaces.
5. The BSC sends a Channel Release message to the MS, instructing the MS and base
transceiver station (BTS) to release the logical channel over the Um interface, and
starts timer WAITFORRELIND (BSC6900, BSC6910). This message carries the RR
cause.
6. Upon receiving the Channel Release message, the MS disconnects the uplink
signaling link. Then, the MS sends a DISC frame to the BTS to inform the BTS that
the logical channel is released.
7. The BTS makes acknowledgment by sending a UA frame to the MS. On receiving
the UA frame, the MS returns to the CCCH and enters the idle state.
8. The BSC sends a Deactivate SACCH message to the BTS to instruct the BTS to
deactivate the SACCH.
9. Upon receiving the DISC frame, the BTS sends a Release Indication message to the
BSC, indicating that the MS has released the logical channel over the Um interface.
The BSC stops timer WAITFORRELIND (BSC6900, BSC6910) and starts timer
DELAYSENDRFCHREL (BSC6900, BSC6910).
10. After timer DELAYSENDRFCHREL (BSC6900, BSC6910) expires, the BSC sends
an RF Channel Release message to the BTS to release the RF channel over the Um
interface. The timer DELAYSENDRFCHREL (BSC6900, BSC6910) is used to reserve
some time for connection disconnection confirmation.
11. The BTS sends an RF Channel Release Acknowledge message to the BSC, indicating
that the RF channel over the Um interface is released and can be allocated to other
calls.
12. The BSC sends a Clear Complete message to the MSC.
13. The MSC sends an RLSD message to the BSC to release the SCCP link.
14. The BSC sends an RLC message to the MSC, indicating that the SCCP link is
released.
The conclusion from the previous procedure is:
• Steps 1 through 3 are about call connection release.
• Steps 4 through 14 are about radio resource release.
 After the connections at the CC and MM layers are released successfully, the MSC sends a Clear
Command message to the BSC to release the SCCP link. This message carries the cause about
the call release, for example, "Handover Successful" or "Call Control". If the call release is
caused by failure of A interface message transmission, radio link failure, or device failure, the
BSC sends a Clear Request message to the MSC, which then sends a Clear Command message
to the BSC.
3.3.3 Network-Initiated Call Release

After an MS has accessed the network, the network initiates call release when both of the
following conditions are met:
• MAXTADROPCALLSWITCH (BSC6900, BSC6910) is set to ON(On).
• After the timing advance (TA) values in a number of measurement reports (MRs)
specified by MAXTADROPCALLFILTER (BSC6900, BSC6910) are averaged, the
obtained TA value is greater than the value of MAXTADROPCALLTHRESHOLD
(BSC6900, BSC6910).

If MaxTaDropCallOptSw (BSC6900, BSC6910) is set to ON(On), the BSC optimizes the values of
MAXTADROPCALLFILTER (BSC6900, BSC6910) and MAXTADROPCALLTHRESHOLD
(BSC6900, BSC6910).

The procedure of network-initiated call release is similar to Figure 3-2, except that the messages in
steps 1 through 3 are transparently transmitted in reverse.

4 Call Reestablishment

4.1 Overview

The feature involved is GBFD-110503 Call Reestablishment.

When an MS encounters a radio link failure during a call, Call Reestablishment can be used to
reestablish the radio link connection so that the original call can proceed. This shortens the call
intermission and therefore improves user experience.
4.2 Call Reestablishment Procedure

The CALLRESTABDIS (BSC6900, BSC6910) parameter specifies whether to enable call

reestablishment.
When the MS encounters a radio link failure during a call, call reestablishment procedure can be
used to reestablish the radio link connection so that the original call can proceed. Call
reestablishment may occur in a new cell or a new location area. If a cell supports call
reestablishment, the start of a call reestablishment attempt depends on call state of the MS.
After call reestablishment is started, the MSC starts the encryption and assignment procedures.
Then, the MSC checks whether the call state or auxiliary state of the MS is correct. If the call
state or auxiliary state of the MS is correct, the call is reestablished.
During call reestablishment, the MS cannot return to the idle state. Therefore, the MS cannot
perform location update when its source cell and target cell for call reestablishment are in
different location areas. After the ongoing call is complete, the MS can perform location update.
Call reestablishment procedure is controlled by the MSC. The BSC sets up channels and
forwards layer 3 messages.
Figure 4-1 shows call reestablishment procedure.
Figure 4-1 Call reestablishment procedure

1. Step 1 shows that the BTS reports a radio link failure to the BSC. The BSC starts the
call reestablishment timer for delayed release of A interface resources and waiting
for call reestablishment.
2. Steps 2 through 6 show the procedure of immediate assignment and seizure of
signaling channels.
 3. Steps 7 and 8 show the encryption procedure.
4. Steps 9 and 10 show the assignment procedure.
5. Step 13 and 14 show the procedure of A interface resource release. The MSC sends a
Clear Command message to instruct the BSC to release A interface resources used
before call reestablishment. Upon receiving this message, the BSC stops the
TREESTABLISH timer and releases A interface resources used before call
reestablishment.
The TREESTABLISH timer is specified by the MSIPFAILINDDELAY (BSC6910,
BSC6900) parameter. If this timer expires before the MSC sends the Clear Command
message, the BSC releases A interface resources used before call reestablishment. In
this situation, call reestablishment may fail.

5 TCH Re-assignment

5.1 Overview

The feature involved is GBFD-112501 TCH Re-assignment.

GBFD-112501 TCH Re-assignment enables the BSC to reassign a TCH to an MS after a TCH
assignment fails and the MS returns to the SDCCH.
The TCH Re-assignment feature provides the following benefits:
• Reduces the impact on call maintenance due to a TRX channel failure in the cell and
avoids the first dialing failure.
• Reduces the assignment failures due to interference on certain frequencies in the cell
and avoids the impact on call maintenance.
• Improves the service quality for users.
5.2 TCH Re-assignment Procedure

The triggering of TCH re-assignment is determined by the REASSEN (BSC6900, BSC6910)

parameter.
Upon receiving an Assignment Request message from the MSC during call setup, the BSC
assigns a TCH for a call, and then sends an Assignment Command message to the MS. If the MS
fails to access the TCH for certain reasons, such as co-channel interference, and returns to the
SDCCH, the BSC does not immediately send an Assignment Failure message to the MSC.
Instead, the BSC allocates another TCH for the call. The number of reassignments cannot exceed
the value of ASSRETRYMAX (BSC6900, BSC6910). If the reassignment succeeds, the BSC sends
an Assignment Complete message to the MSC. Otherwise, the BSC sends an Assignment Failure
message to the MSC.
Figure 5-1 shows the TCH re-assignment procedure.
Figure 5-1 TCH re-assignment procedure

The TCH re-assignment procedure is described as follows:

1. Upon receiving the Assignment Failure message from the MS, the BSC stops timer
T3107. After internal processing, the BSC sends a Channel Activation message to the
BTS, and waits for the Channel Activation Acknowledge message from the BTS. To
avoid degraded quality of service (QoS) due to interference, TRX channel failure, or
engineering mishandling, a TCH on either the same frequency band or a different
frequency band can be assigned during TCH re-assignment. The frequency band is
determined by the REASSFREQBAND (BSC6900, BSC6910) parameter.
2. Upon receiving the Channel Activation Acknowledge message from the BTS, the
BSC proceeds with internal handling.
 3. The BSC uses the SDCCH, which has not been released, to send an Assignment
Command message to the MS, and waits for the Establish Indication message from
the MS.
4. The MS sends SABM frames to the BTS to access the network through the FACCH
as indicated in the Assignment Command message.
5. The BTS responds by sending UA frames to the MS through the FACCH.
6. The BTS sends an Establish Indication message to the BSC.
7. After accessing the network through the TCH, the MS sends an Assignment
Complete message to the MSC through the FACCH.
8. After both the radio traffic channel and terrestrial circuit are successfully established,
the BSC sends an Assignment Complete message to the MSC through the occupied
TCH. At this stage, the call is regarded as in conversation state.

6 MSC Re-Assignment

6.1 Overview

MSC Re-assignment enables the MSC to reinitiate an assignment request if the MSC receives an
Assignment Failure message from the BSC or the MSC needs to change the service type during a
call. For details about how to enable MSC Re-assignment, see the MSC documents for
customers.
6.2 Procedure

MSC Re-assignment is enabled in either of the following scenarios:

• During a call, if the BSC sends an Assignment Failure message to the MSC, the MSC
reinitiates an assignment request to increase the assignment success rate. The BSC
processes the request in the same manner as a common assignment request. For
details, see Assignment and Immediate Assignment Feature Parameter Description.
• During a call, if the MSC needs to change the service type, for example, from speech
to Signaling or data, the MSC reinitiates an assignment request.
If the value for the speech/data indicator in an Assignment Request message is
Signaling, the BSC processes the request based on the setting of the
SDCCHASSREQACKFLAG (BSC6900, BSC6910) parameter after receiving the
Assignment Request message from the MSC.
▪ If the parameter is set to OFF(Reply with Assignment Complete), the
BSC responds with an Assignment Complete message and does not assign
another signaling channel to the MS.
 ▪ If the parameter is set to ON(Reply with Assignment Failure), the BSC
responds with an Assignment Failure message.
▪ If the parameter is set to ASSNEWCHN(Assign a New Signaling
Channel), the BSC assigns another signaling channel to the MS and
processes the request in the same manner as a common assignment request.
For details, see Assignment and Immediate Assignment Feature Parameter Description .
When receiving an Assignment Complete message, the BSC releases the
terrestrial circuit resources specified in the preceding assignment and
responds with an Assignment Complete message.

7 Engineering Guidelines

7.1 Deploying Call Control

None
7.2 Deploying Call Reestablishment

7.2.1 Deployment Requirements

Table 7-1 Deployment requirements

Aspect Requirement

Related features None

BSC None

BTS None

GSM networking None

MS None

MSC The MSC supports this feature.

License None

Others None

7.2.2 Activation

Using MML Commands

On the BSC LMT, perform the following steps:

 1. Run the SET GCELLBASICPARA command with Call Reestablishment
Forbidden set to NO(No).
2. Run the SET GCELLTMR command with TREESTABLISH set to an appropriate
value. If this parameter is set to a large value, the radio resources assigned previously
are reserved for a long time, which results in network congestion.
3. Run the SET OTHSOFTPARA command with Call Re-setup Timeout Call Drop
Stat. Optimize set to YES(Yes).

MML Command Examples

SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, CALLRESTABDIS=NO;

SET GCELLTMR: IDTYPE=BYID, CELLID=0, MSIPFAILINDDELAY=10000;
SET OTHSOFTPARA: CALLRSTDROPSTATOPT=YES;

Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.

7.2.3 Activation Observation

1. Select a test cell. The test cell must have two TRXs, where TRX 1 is the BCCH TRX
and TRX 2 is the non-BCCH TRX. TRX 2 requires an independent variable
attenuator or a device that can dynamically adjust the uplink and downlink signals of
TRX 2.
2. Use an MS to make a call in the test cell. On the BSC LMT, run SET
GTRXCHANADMSTAT command to the block all TCHs on TRX 1 so that the MS
uses a TCH on TRX 2. Then, run SET GTRXCHANADMSTAT command to
unblock all TCHs on TRX 1. For details about how to block and unblock TCHs, see
Help Information about the SET GTRXCHANADMSTAT command on the LMT.
3. Sharply attenuate the signals of TRX 2 by using the variable attenuator or other
devices for adjusting signals. Meanwhile, check the signaling traced over the A and
Abis interfaces and monitor the channel status of the test cell.
Expected result:
• As displayed in the channel status monitoring window, the MS
reestablishes a call on TRX 1 of the test cell.
• The signaling messages Cm Re-Establishment Request are traced.
7.2.4 Deactivation

Using MML Commands

On the BSC LMT, run the SET GCELLBASICPARA command with Call Reestablishment
Forbidden set to YES(Yes).

MML Command Examples

 SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, CALLRESTABDIS=YES;

Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.

7.3 Deploying TCH Re-assignment

7.3.1 Deployment Requirements

Table 7-2 Deployment requirements

Aspect Requirement

Related features None

BSC None

BTS None

GSM networking None

MS None

MSC None

License None

Others None

7.3.2 Activation

Using MML Commands

1. On the BSC LMT, run the SET GCELLCCBASIC command with Allow Reassign
set to YES(Yes).

MML Command Examples

SET GCELLCCBASIC: IDTYPE=BYID, CELLID=0, REASSEN=YES;

Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.

7.3.3 Activation Observation

1. On the BSC LMT, run the SET GCELLCCAD command with Frequency Band of
Reassign set to Same_Band(Same Band).
 This parameter specifies whether channels are preferentially reassigned on a different frequency band
or the same frequency band during TCH reassignment. If this parameter is set to Same_Band(Same
Band), the BSC preferentially reassigns a channel on the same frequency band as the originally
assigned TCH.

2. Reserve an idle TCH on the BCCH TRX and block the other TCHs on the BCCH
TRX.
Run the SET GTRXCHANADMSTAT command with Channel No. set to the
number of TCHs to be blocked and Administrative State set to Lock(Lock).
3. Reserve an idle TCH on the non-BCCH TRX and block the other TCHs on the non-
BCCH TRX. In addition, degrade the uplink signal transmitted on the TRX, for
example, remove the uplink antenna for the non-BCCH TRX.
Expected result: After a call is initiated in the cell, a TCH on the non-BCCH TRX is
assigned to the call in the first assignment. Then, the call is reassigned onto a TCH of
the BCCH TRX because the assignment over the Um interface fails for the non-
BCCH TRX.
7.3.4 Deactivation

Using MML Commands

On the BSC LMT, run the SET GCELLCCBASIC command with Allow Reassign set to
NO(No).

MML Command Examples

SET GCELLCCBASIC: IDTYPE=BYID, CELLID=0, REASSEN=NO;

Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.

7.4 Performance Monitoring

Observe counters listed in the following table to monitor the LTE terminal penetration.

Counter ID Counter Name Counter Description

1282438369 CELL.SPT.LTE.TDD.CALL.NUM A03645:Number of Calls Made by

(BSC6900, BSC6910) LTE TDD Capable MSs

1282438367 CELL.SPT.LTE.FDD.CALL.NUM A03644:Number of Calls Made by

(BSC6900, BSC6910) LTE FDD Capable MSs

Observe counters listed in the following table to monitor the Traffic Volume on TCH occupied
by MSs handed over from the UMTS or LTE network to the GSM network.
Counter ID Counter Name Counter Description

1282454475 CELL.TCH.TRAF.ERL.U2G.HO R3552E:Traffic Volume on TCHs

(BSC6900, BSC6910) Occupied by MSs Handed over
from UMTS to GSM

1282454476 CELL.TCH.TRAF.ERL.L2G.HO R3553E:Traffic Volume on TCHs

(BSC6900, BSC6910) Occupied by MSs Handed over
from LTE to GSM

8 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.
• BSC6910 GSM Parameter Reference: contains the parameters related to the BSC6910
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.
9 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 BSC6910
equipment, transport, and radio access functions.
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
functions, including air interface management, access control, mobility control, and
radio resource management.

You can find the EXCEL files of performance counter reference for the software version used on the live network
from the product documentation delivered with that version.

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.

10 Glossary

For the acronyms, abbreviations, terms, and definitions, see the Glossary.
11 Reference Documents

1. 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network

protocols; Stage 3"
2. 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource
Control (RRC) protocol"
3. 3GPP TS 48.008: "Mobile Switching Center - Base Station system (MSC-BSS)
interface; Layer 3 specification"
4. 3GPP TS 48.058: "Base Station Controller - Base Transceiver Station (BSC-BTS)
Interface; Layer 3 specification"
5. BSC6900 Feature List
6. BSC6900 Basic Feature Description
7. BSC6900 GSM Parameter Reference
8. BSC6900 GSM MML Command Reference