Enhanced Measurement Report

(EMR)
Contents
3.6.27 Enhanced Measurement Report (EMR)

GSM BSS
GBSS22.1
Enhanced Measurement Report (EMR)
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.27 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 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 Engineering Guidelines
5.1 Required Information
5.2 Deploying EMR
5.2.1 Deployment Requirements
5.2.2 Precautions
5.2.3 Activation
5.2.4 Activation Observation
5.2.5 Deactivation

6 Parameters

7 Counters

8 Glossary

9 Reference Documents

1 About This Document

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.
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 versionk
• 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)

GBSS22.1 Draft A (2020-01-18) introduces the following changes to GBSS21.1 01 (2019-06-

06).

Change Type Change Description Parameter Change

Feature change • Changed the name of U2020 to None

MAE-Access.
• Changed the name of CME to MAE-
Deployment.

Editorial change None None

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

2.2 NEs Supporting the Feature

Table 2-1 NEs supporting the feature

Feature BSC6900 BSC6910 BTS eGBTS

EMR √ √ √ √

√ indicates that the NE supports this feature. × indicates that the NE does not support this feature.

3 Technical Description

3.1 Implementation in the BSS

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

17 180 20

18 185 17

19 195 13

20 200 10

21 205 7

22 210 3
 MEAN_BEP CIR RXQUAL x 10

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 MAE-Access 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 MAE-Access V200R013C00 and later. For details, see MAE-
Access online help information.

4 Related Features

Prerequisite Features

None.

Mutually Exclusive Features

Feature ID Feature Name Description

GBFD-115830 VAMOS -

GBFD-118702 MOCN Shared Cell -

GBFD-191201 Uplink CoMP (Joint RX) -

Impacted Features

None.
5 Engineering Guidelines

5.1 Required Information

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

5.2.1 Deployment Requirements

Table 5-1 Deployment requirements

Aspect Requirement

Related features See 4 Related Features.

BSC None

BTS None

GSM networking None

MS MSs support EMR.

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 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).

MML Command Examples

//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 MAE-Deployment

When configuring the EMR feature on the MAE-Deployment, 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 MAE-Deployment. (MAE-Deployment single

configuration)
Set parameters on the MAE-Deployment configuration interface according to the
operation sequence described in Table 5-2.
For detailed operations, see Feature Configuration Using the MAE-Deployment.
2. (Optional) Modify objects in batches on the MAE-Deployment. (MAE-Deployment
batch modification center)

To modify objects, such as BSCs, BTSs, cells, and TRXs, in batches, click the
icon on the MAE-Deployment 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 5-2 Configuring EMR parameters on the MAE-Deployment

SN Managed Object (MO) NE Parameter Parameter ID Configurable

Name in MAE-
Deployment
Batch
Modification
Center

1 GCELLCCUTRANSYS BSC6900/BSC6910 Measurement MEASURETYPE Yes

Report Type

Faulty EMR EmrMsCapProSwitch Yes

MS TAC
Collection
Switch

MS EmrMsCapIdeSwitch Yes
Differentiated
Processing
EMR Switch

2 GCELLSOFT BSC6900/BSC6910 Single-User TestUserTraceFun Yes

Tracing
 5.2.4 Activation Observation

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).

MML Command Examples

//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 MAE-Deployment

When configuring the EMR feature on the MAE-Deployment, 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 MAE-Deployment. (MAE-Deployment single

configuration)
Set parameters on the MAE-Deployment configuration interface according to the
operation sequence described in Table 5-3.
For detailed operations, see Feature Configuration Using the MAE-Deployment.
2. (Optional) Modify objects in batches on the MAE-Deployment. (MAE-Deployment
batch modification center)

To modify objects, such as BSCs, BTSs, cells, and TRXs, in batches, click the
icon on the MAE-Deployment 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 5-3 Configuring EMR parameters on the MAE-Deployment

SN MO NE Parameter Parameter ID Configurable

Name in MAE-
Deployment
Batch
Modification
Center

1 GCELLCCUTRANSYS BSC6900/BSC6910 Measurement MEASURETYPE Yes

Report Type

Faulty EMR EmrMsCapProSwitch Yes

MS TAC
Collection
Switch

MS EmrMsCapIdeSwitch Yes
Differentiated
Processing
EMR Switch

2 GCELLSOFT BSC6900/BSC6910 Single-User TestUserTraceFun Yes

Tracing
6 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.

7 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.

8 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

9 Reference Documents

1. 3GPP TS 44.018 "Mobile radio interface layer 3 specification; Radio Resource

Control (RRC) protocol"