Professional Documents
Culture Documents
GBSS22.1
Issue 02
Date 2021-04-30
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.
Website: https://www.huawei.com
Email: support@huawei.com
Contents
2 Overview....................................................................................................................................4
2.1 Introduction............................................................................................................................................................................... 4
2.2 NEs Supporting the Feature................................................................................................................................................ 6
3 Classification of PDCHs.......................................................................................................... 8
4 Allocation of PDCHs............................................................................................................. 10
4.1 Overview.................................................................................................................................................................................. 10
4.2 Allocation Preprocessing.................................................................................................................................................... 11
4.3 Prioritizing Channel Groups.............................................................................................................................................. 15
7 PDCH Repacking.................................................................................................................... 45
7.1 Overview.................................................................................................................................................................................. 45
7.2 Conditions for Handing over a CS User........................................................................................................................ 46
7.3 CS Users Do Not Support Forced Intra-Cell Handover............................................................................................ 46
7.4 Precautions for PDCH Repacking.................................................................................................................................... 47
9.4 Features Related to GBFD-119505 PDCH Dynamic Adjustment with Two Thresholds................................52
9.5 Features Related to GBFD-119302 Packet Channel Dispatching......................................................................... 52
10 Network Impact.................................................................................................................. 54
10.1 PDCH Dynamic Adjustment............................................................................................................................................ 54
10.1.1 System Capacity.............................................................................................................................................................. 54
10.1.2 Network Performance................................................................................................................................................... 54
10.2 Load Sharing........................................................................................................................................................................ 55
10.2.1 System Capacity.............................................................................................................................................................. 55
10.2.2 Network Performance................................................................................................................................................... 55
10.3 Adaptive Adjustment of Uplink and Downlink Channels..................................................................................... 55
10.3.1 System Capacity.............................................................................................................................................................. 55
10.3.2 Network Performance................................................................................................................................................... 56
10.4 PDCH Dynamic Adjustment with Two Thresholds.................................................................................................. 56
10.4.1 System Capacity.............................................................................................................................................................. 56
10.4.2 Network Performance................................................................................................................................................... 56
10.5 Packet Channel Dispatching........................................................................................................................................... 56
10.5.1 System Capacity.............................................................................................................................................................. 56
10.5.2 Network Performance................................................................................................................................................... 56
11 Engineering Guidelines...................................................................................................... 57
11.1 When to Use GPRS/EGPRS Channel Management................................................................................................. 57
11.1.1 PDCH Dynamic Adjustment........................................................................................................................................ 57
11.1.2 Load Sharing..................................................................................................................................................................... 57
11.1.3 Adaptive Adjustment of Uplink and Downlink Channels..................................................................................57
11.1.4 PDCH Dynamic Adjustment with Two Thresholds.............................................................................................. 57
11.1.5 Packet Channel Dispatching........................................................................................................................................57
11.2 Required Information........................................................................................................................................................ 58
11.2.1 PDCH Dynamic Adjustment........................................................................................................................................ 58
11.2.2 Load Sharing..................................................................................................................................................................... 58
11.2.3 Adaptive Adjustment of Uplink and Downlink Channels..................................................................................58
11.2.4 PDCH Dynamic Adjustment with Two Thresholds.............................................................................................. 58
11.2.5 Packet Channel Dispatching........................................................................................................................................58
11.3 Deploying PDCH Dynamic Adjustment.......................................................................................................................58
11.3.1 Deployment Requirement............................................................................................................................................ 59
11.3.2 Activation........................................................................................................................................................................... 59
11.3.3 Activation Observation.................................................................................................................................................. 64
11.3.4 Deactivation...................................................................................................................................................................... 65
11.4 Deploying Load Sharing................................................................................................................................................... 67
11.5 Deploying Adaptive Adjustment of Uplink and Downlink Channels................................................................67
11.6 Deploying PDCH Dynamic Adjustment with Two Thresholds.............................................................................67
11.6.1 Deployment Requirement............................................................................................................................................ 67
11.6.2 Data Preparation............................................................................................................................................................. 68
11.6.3 Activation........................................................................................................................................................................... 71
12 Parameters............................................................................................................................90
13 Counters................................................................................................................................ 91
14 Glossary................................................................................................................................. 92
15 Reference Documents........................................................................................................ 93
1.1 Scope
This document describes GPRS/EGPRS Channel Management, including its
technical principles, related features, network impact, and engineering guidelines.
This document describes the basic transmission time interval (BTTI) packet data
channel (PDCH) allocation algorithm, dynamic PDCH conversion algorithm, and
dynamic PDCH release algorithm. The Dual Carriers in Downlink (DCDL), Mobile
Station Receiver Diversity (MSRD), and Reduced Transmission Time Interval (RTTI)
PDCH allocation algorithms are not involved. For details about the DCDL and
MSRD PDCH allocation algorithms, see Dual Carriers in Downlink Feature
Parameter Description. For details about the RTTI PDCH allocation algorithm, see
Latency Reduction Feature Parameter Description.
This document covers the following features:
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.
02 (2021-04-30)
This issue includes the following changes.
01 (2020-04-07)
This issue does not include any changes.
Draft B (2020-03-09)
This issue includes the following changes.
Draft A (2020-01-18)
GBSS22.1 Draft A (2020-01-18) introduces the following changes to GBSS21.1 01
(2019-06-06).
2 Overview
2.1 Introduction
This section describes the following channel management features:
● GBFD-113101 PDCH Dynamic Adjustment
● GBFD-119302 Packet Channel Dispatching
● GBFD-119505 PDCH Dynamic Adjustment with Two Thresholds
● GBFD-119303 Load Sharing
● GBFD-119501 Adaptive Adjustment of Uplink and Downlink Channels
After a general packet radio system (GPRS) network is deployed, circuit switched
(CS) services and packet switched (PS) services in the network share channel
resources on the Um interface. With operators focusing more attention on PS
services, more and more channel resources on the Um interface are required for
PS services. In addition, to ensure the quality of CS services and PS services, the
system needs to efficiently manage all the PDCHs.
The GPRS/EGPRS Channel Management feature involves PDCH allocation, dynamic
PDCH conversion, dynamic PDCH release, and PDCH repacking. PDCH allocation
depends on various factors. During dynamic PDCH conversion and dynamic PDCH
release, the BSC adjusts PDCHs properly based on the service requirements and
actual network conditions. The GPRS/EGPRS Channel Management feature
ensures not only the quality of service for a single user, but also the performance
of the entire network.
During the PDCH allocation process, the principles and requirements for the BSC
to select the final channel group vary according to actual conditions. Therefore,
the PDCH allocation algorithm defines a priority for each channel group. When an
MS requests a PDCH, the BSC allocates a qualified channel group with the highest
priority to the MS.
The BSC determines whether to trigger dynamic PDCH conversion based on the
following factors:
● PDCH allocation result
● Number of the idle CS channels
Load Sharing √ √ √ √
NOTE
√ indicates that the NE supports this feature. × indicates that the NE does not support this
feature.
3 Classification of PDCHs
PBCCH_PDTCH(PBCCH+PDTCH), or PCCCH_PDTCH(PCCCH+PDTCH). To
ensure that initial network accesses for PS services are successful when no
dynamic PDCH is available and CS services are busy, you are advised to
configure at least one static PDCH in a PS-capable cell.
● Dynamic PDCH
The dynamic PDCH carries CS services or PS services depending on the service
requirement. It supports only one type of service at a time. A PDCH is a
dynamic PDCH when the CHTYPE (BSC6900, BSC6910) parameter is set to
TCHFR(TCH Full Rate), which is the default value of the parameter.
NOTE
If CHTYPE (BSC6900, BSC6910) is set to DPDCH(Dynamic PDCH) for the BSC configured
with an external packet control unit (PCU), the PDCH is a dynamic PDCH. The BSC6910
does not support an external PCU.
Static PDCHs are used for PS service access. Dynamic PDCHs are adjusted based
on the cell load. When you configure static PDCHs or adjust dynamic PDCHs,
consider timeslot continuity to ensure a satisfactory PS rate.
4 Allocation of PDCHs
4.1 Overview
When the uplink and downlink TBFs are not established but a data transfer
request comes in, the MS sends a PDCH request to instruct the BSC to establish
the uplink TBF. A PDCH request sent from the MS can be either of the following
types:
● One-phase access on the common control channel (CCCH) and packet
common control channel (PCCCH)
To respond to the PDCH request for one-phase access, the BSC allocates one
PDCH to the MS.
● Two-phase access on the CCCH and PCCCH
To respond to the PDCH request for two-phase access, the BSC allocates only
one radio block on the PDCH to the MS for the first time. The MS sends the
packet resource request in the allocated radio block. For the second time, the
BSC allocates one or more PDCHs to the MS based on the multislot capability
of the MS.
When the BSC receives downlink logical link control (LLC) packet data units
(PDUs) from the serving GPRS support node (SGSN) but detects no available
uplink or downlink TBF, the BSC sends an Immediate Assignment message on the
CCCH or a Packet Downlink Assignment message on the PCCCH to establish a
downlink TBF. Then, the BSC allocates one PDCH to the MS.
When the MS is in packet transfer mode, the BSC establishes for the MS an uplink
or downlink TBF on the packet associated control channel (PACCH) based on the
service requirement. When establishing an uplink or downlink TBF on the PACCH,
the BSC allocates one or more PDCHs to the MS based on the multislot capability
of the MS.
When the MS is in packet transfer mode, the BSC can reallocate resources to MSs.
The reallocation can implement the Load Sharing and Adaptive Adjustment of
Uplink and Downlink Channels features. Upon receiving an uplink or downlink LLC
PDU, the BSC performs resource reallocation under the following conditions:
● The BSC does not perform resource reallocation when either of the following
conditions is met:
● PDCHs to be released are not allocated to MSs. If TBFs on the dynamic PDCHs
are to be released due to insufficient resources, the dynamic PDCHs are
marked as PDCHs to be released and are not allocated.
● If the number of MSs multiplexed onto a PDCH in the uplink multiplied by 10
produces a number greater than or equal to the value of PDCHUPLEV
(BSC6900, BSC6910), the PDCH cannot be allocated for the uplink PS service.
● If the number of MSs multiplexed onto a PDCH in the downlink multiplied by
10 produces a number greater than or equal to the value of PDCHDWNLEV
(BSC6900, BSC6910), the PDCH cannot be allocated for the downlink PS
service.
● The GPRS channel cannot be allocated for the EGPRS service.
● The EGPRS dedicated channel cannot be allocated for the GPRS service.
● If the EGPRS preferred channel has been allocated for the EGPRS service, or
EnEdgePriGprs (BSC6900, BSC6910) parameter is set to NO(No), it cannot
be allocated for the GPRS service.
● When the downlink EGPRS and uplink GPRS services share an EGPRS common
channel, the downlink data blocks on this channel must be modulated with
Gaussian minimum shift-frequency keying (GMSK) if the GPRS uplink data
blocks require scheduling. This may decrease the EGPRS downlink
transmission rate. Therefore, the downlink EGPRS and uplink GPRS can share
an EGPRS common channel only if the FORBIDEDGU (BSC6900, BSC6910)
parameter is set to OPEN(Open).
Service types for an MS are classified into GMM/SM signaling service, uplink
preferred service, downlink preferred service, and neutral preferred service. When
the ALLOCSINGLEPDCHFORSIGNALLING (BSC6900, BSC6910) parameter is set
to ON(ON), the BSC checks whether the MS is performing signaling services.
● If the BSC allocates resources to the MS for the first time, the service type for
the MS is determined by the AccStaServiceType (BSC6900, BSC6910)
parameter.
● If the BSC allocates downlink resources to the MS that has performed cell
reselection for the first time and the CellReselTrafficContinue (BSC6900,
BSC6910) parameter is set to ON(ON), the service type for the MS is the
same as that for the MS before the cell reselection.
● During a fast reallocation, the BSC checks the service traffic processed by the
MS between the previous and current reallocations. For the first reallocation,
the BSC checks the service traffic processed by the MS between the
reallocation and service establishment.
The BSC considers the uplink preferred service as the service type for the MS
to perform resource reallocation if the following condition is met:
Uplink service traffic/Downlink service traffic ≥ ULCOEFFICIENTTSRAPIDADJ
(BSC6900, BSC6910)
The BSC considers the downlink preferred service as the service type for the
MS to perform resource reallocation if the following condition is met:
Downlink service traffic/Uplink service traffic ≥ DLCOEFFICIENTTSRAPIDADJ
(BSC6900, BSC6910)
The BSC considers the neutral preferred service as the service type for the MS
to perform resource reallocation in other conditions.
● During a normal reallocation, the BSC checks the service traffic processed by
the MS between the previous and current reallocations. For the first
reallocation, the BSC checks the service traffic processed by the MS between
the reallocation and service setup.
The BSC considers the uplink preferred service as the service type for the MS
to perform resource reallocation if the following condition is met:
Uplink service traffic/Downlink service traffic ≥ TrafficClassUlCoefficient
(BSC6900, BSC6910)
The BSC considers the downlink preferred service as the service type for the
MS to perform resource reallocation if the following condition is met:
Downlink service traffic/Uplink service traffic ≥ TrafficClassDlCoefficient
(BSC6900, BSC6910)
The BSC considers the neutral preferred service as the service type for the MS
to perform resource reallocation in other conditions.
With the GBFD-119501 Adaptive Adjustment of Uplink and Downlink Channels
feature, the BSC determines the maximum number of uplink and downlink
channels that can be allocated to an MS according to the following principles:
● For the signaling service, the BSC allocates one uplink channel and one
downlink channel to an MS if the ALLOCSINGLEPDCHFORSIGNALLING
(BSC6900, BSC6910) parameter is set to ON(ON).
● For the uplink preferred service, the BSC allocates as many uplink channels as
possible.
– If SUPPORTEDA (BSC6900, BSC6910) is set to SUPPORT(Support), the
BSC allocates three or more uplink channels to the MS based on the radio
access capability of the MS.
– If SUPPORTEDA (BSC6900, BSC6910) is set to NOTSUPPORT(Not
Support), the BSC allocates a maximum of two uplink channels to the
MS based on the radio access capability of the MS.
● For the downlink preferred service, the BSC allocates as many downlink
channels as possible.
If SUPPORTDL5TS (BSC6900, BSC6910) is set to SUPPORT(Support), the
BSC allocates a maximum of five downlink channels to the MS based on the
radio access capability of the MS. If SUPPORTDL5TS (BSC6900, BSC6910) is
set to NOTSUPPORT(Not Support), the BSC allocates a maximum of four
downlink channels.
● For the neutral service, the BSC allocates the uplink and downlink channels in
a balanced manner.
For example, the BSC allocates three downlink channels and two uplink
channels to an MS whose multislot class is 10.
When the Abis interface uses satellite transmission and data transmission is
complete, it takes a long time for the MS to respond to the BSC with the
acknowledgement message. This delays resource release. To minimize resource
waste, the BSC restricts the number of channels allocated to an MS. If the BSC
detects that the Abis transmission delay is longer than NormalCellTransDelay
(BSC6900, BSC6910), the BSC allocates a maximum of one uplink channel and a
maximum of three downlink channels to an MS in the cell.
When the channel multiplexing rate (average number of MSs multiplexed onto a
PDCH in a cell) is greater than the value of PSServiceBusyThreshold (BSC6900,
BSC6910), the PS traffic in a cell is heavy and the BSC no longer allocates
channels to new MSs according to their timeslot capabilities. Instead, one uplink
and one downlink channels are allocated to a new MS to ensure its access to the
network. In addition, the release delay of all downlink TBFs in the cell is reduced
to half the value of DNTBFRELDELAY (BSC6900, BSC6910). Reducing the delay
helps prevent new MSs from being denied access due to heavy traffic. Channel
allocation to MSs that request channels again and to guaranteed bit rate (GBR)
MSs, however, is not affected. When the channel multiplexing rate is less than or
equal to the value of PSServiceBusyThreshold (BSC6900, BSC6910), the PS
traffic in a cell is light. For new MSs that were allocated one uplink and one
downlink channels, the BSC triggers the channel reallocation procedure to
reallocate channels to them if necessary.
When the channel usage rate in a cell is greater than or equal to IMOptThrsh
(BSC6900, BSC6910) divided by 100, if SPTDPI (BSC6900, BSC6910) is set to
SUPPORT(GGSN Support), the maximum number of channels allocated to TBFs
depends on the parameter settings for interactive, background, best effort (BE),
and instant messaging (IM) services.
● Parameters related to IM services are: IMArp1PriMaxPDCHNum (BSC6900,
BSC6910), IMArp2PriMaxPDCHNum (BSC6900, BSC6910),
IMArp3PriMaxPDCHNum (BSC6900, BSC6910).
● Parameters related to interactive services are: Thp1Arp1PriMaxPDCHNum
(BSC6900, BSC6910), Thp1Arp2PriMaxPDCHNum (BSC6900, BSC6910),
Thp1Arp3PriMaxPDCHNum (BSC6900, BSC6910),
Thp2Arp1PriMaxPDCHNum (BSC6900, BSC6910),
Thp2Arp2PriMaxPDCHNum (BSC6900, BSC6910),
Thp2Arp3PriMaxPDCHNum (BSC6900, BSC6910),
Thp3Arp1PriMaxPDCHNum (BSC6900, BSC6910),
Thp3Arp2PriMaxPDCHNum (BSC6900, BSC6910), and
Thp3Arp3PriMaxPDCHNum (BSC6900, BSC6910).
● Parameters related to background services are: BkgArp1PriMaxPDCHNum
(BSC6900, BSC6910), BkgArp2PriMaxPDCHNum (BSC6900, BSC6910), and
BkgArp3PriMaxPDCHNum (BSC6900, BSC6910).
● Parameters related to BE services are: BeArp1PriMaxPDCHNum (BSC6900,
BSC6910), BeArp2PriMaxPDCHNum (BSC6900, BSC6910), and
BeArp3PriMaxPDCHNum (BSC6900, BSC6910).
When the channel usage rate in a cell is greater than or equal to IMOptThrsh
(BSC6900, BSC6910) divided by 100, if SPTDPI (BSC6900, BSC6910) is set to
BSCSUPPORT(BSC Support), the maximum number of channels allocated to TBFs
depends on the parameter settings for IM, web browsing, email, streaming media,
and P2P resource balancing services. For details, see Differentiated PS Services
Feature Parameter Description.
The PDCH management optimization enables the BSC to consider the PDCH
continuity during channel allocation; that is, if EnPDAdminOpt (BSC6900,
BSC6910) is set to ON(On), the BSC considers the number of consecutive PDCHs
on a TRX when selecting a channel group. This ensures that the PDCHs used by PS
services are consecutive and distributed to several TRXs.
Consecutive PDCHs that meet the MSs' multislot capability are grouped and
assigned different priorities based on Table 4-1. The PDCH group whose PDCHs
cannot meet the MSs' multislot capability can also be allocated to MSs based on
its priority. Based on the priority for each PDCH group, the PDCH allocation
algorithm enables the BSC to determine whether a group is allocable. The BSC
preferentially allocates the group with a higher priority.
Table 4-1 describes the factors that affect PDCH allocation (The following factors
are ranked by priority from high to low.). Dynamic PDCH conversion is triggered if
no channel group is available.
When EnPDAdminOpt (BSC6900, BSC6910) is set to ON(On), Table 4-2 lists the
PDCH group allocation priorities for EGPRS users in scenarios where
E64KPriSwitch (BSC6900, BSC6910) is set to ON(On) and the Abis interface uses
TDM transmission.
5.1 Overview
The BSC triggers a dynamic PDCH pre-conversion every minute for cells
configured with all dynamic PDCHs, including the triggering condition judgment
and the dynamic PDCH pre-conversion. If the cell has been configured with any
static PDCHs, the dynamic PDCH pre-conversion does not start.
The BSC triggers a dynamic PDCH conversion based on the multislot capability of
an MS when any of the following conditions is met:
● If the BSC fails to allocate PDCHs to an MS and does not obtain the radio
access capability of the MS, which includes the multislot capability, the BSC
converts only one dynamic PDCH. If the BSC obtains the radio access
capability that includes the multislot capability from the MS, the BSC converts
the number of dynamic PDCHs required by the MS.
● If the PDCHs to be allocated to an MS are insufficient, the BSC triggers
dynamic PDCH conversion. The number of converted dynamic PDCHs is equal
to the number of PDCHs required by the MS minus the number of PDCHs
already allocated to the MS.
● If the BSC has allocated GPRS channels to an EGPRS-capable MS and dynamic
PDCHs that can be converted to EGPRS channels are available in a cell,
dynamic PDCH conversion is triggered to convert the required number of
dynamic PDCHs to EGPRS channels.
● After the dynamic PDCH conversion, the total number of PDCHs cannot
exceed value N, which can be calculated using the following formula:
N = (Number of available TCHFs + Number of available static PDCHs) x
MAXPDCHRATE (BSC6900, BSC6910)
Assume that A is the number of PDCHs to be converted, B is the value of N
minus the number of existing PDCHs in the cell (including static PDCHs), the
number of PDCHs that are actually converted is the smaller of A and B.
The BSC does not trigger a dynamic PDCH conversion due to limited multislot
capability (excluding channel allocation failures) when the following conditions
are met:
NOTE
During dynamic PDCH pre-conversion, the BSC reserves PDCHs for EGPRS and
GPRS services based on the number of pre-converted PDCHs. The pre-converted
common EGPRS PDCHs can be reserved for both EGPRS and GPRS services. The
number of PDCHs to be pre-converted is calculated as follows:
● If the PDCHs are reserved for EGPRS services, use the following formula:
Number of PDCHs to be pre-converted = Number of PDCHs that need to be
reserved – Number of activated EGPRS PDCHs in the cell
● If the PDCHs are reserved for GPRS services, use the following formula:
Number of PDCHs to be pre-converted = Number of PDCHs that need to be
reserved – Number of activated GPRS PDCHs (including the number of
common EGPRS PDCHs converted for EGPRS services) in the cell
Table 5-1 describes the weighting factors and their priority levels for selecting the
target TRX for PDCH conversion.
Table 5-1 Weighting factors and their priority levels for selecting the target TRX
for PDCH conversion
To select a TRX based on the criteria listed in Table 5-1, perform the following
steps:
Step 1 Filter all TRXs in the cell based on the criteria with the highest priority.
● If only one TRX meets the criteria, the TRX is selected as the candidate TRX.
Go to Step 3.
● If multiple TRXs meet the criteria, these TRXs are involved in the next round
of filtering, as described in Step 2.
● If no TRX meets the criteria, all TRXs are involved in the next round of
filtering, as described in Step 2.
Step 2 Filter all TRXs based on the criteria with a lower priority.
● If only one TRX meets the criteria, the TRX is selected as the candidate TRX.
Go to Step 3.
● If multiple TRXs or no TRX meets the criteria, repeat Step 2 until the
corresponding TRX is selected. Go to Step 3.
Step 3 The BSC selects the dynamic PDCHs for conversion in the following sequence: 6, 5,
7, 4, 3, 2, 1, and 0.
NOTE
If the conversion requires channel groups, the BSC selects multiple timeslots for conversion in
the following sequence based on the timeslot number: 6, 5, 7, 4, 3, 2, 1, and 0.
----End
The optimized PDCH channel allocation function categorizes PDCH dynamic
conversion into load- and multislot-triggered PDCH conversion. The two types of
conversions are differentiated from the weighting factors and priority levels. They
are triggered by different causes and processed in a different way. Table 5-2 and
Table 5-3 describe the weighting factors and priority levels for PDCH conversion.
● Load-triggered PDCH conversion: The BSC preferentially selects the target TRX
from the TRXs that carry PDCHs. If there are no convertible TCHs on this type
of TRX, the BSC selects the target TRX from the TRXs that do not carry
PDCHs. After selecting the target TRX, the BSC should convert the required
attribute of the TRX" listed in Table 5-2 and Table 5-3 is lower than the priority
level of "Interference level of the TRX."
The frequency band range for TRXs on which PDCH conversion is performed is
controlled by the RAMBCAP (BSC6900, BSC6910) parameter:
● BCCHANDSUBFREQS(BCCH Band and Compatible Bands): If the frequency
bands supported by MSs are unknown, the BSC performs multislot- and load-
triggered PDCH conversion on the frequency bands compatible with the
frequency band used by BCCH TRX. If the frequency bands supported by MSs
are known, the BSC performs multislot- and load-triggered PDCH conversion
on the frequency bands supported by MSs.
● ALLFREQS(All Bands): The BSC performs multislot- and load-triggered PDCH
conversion on all frequency bands.
Table 5-2 Weighting factors and priority levels for PDCH conversion (PDCHs
available)
Priority Factor Description
15 PDCH location in the A TRX whose PDCHs are in the right part
consecutive activated in the consecutive activated PDCH group
PDCH group on the TRX on the TRX are preferred.
Table 5-3 Weighting factors and priority levels for PDCH conversion (PDCHs
unavailable)
Priority Factor Description
6.1 Overview
When a dynamic PDCH remains idle for a period of time, the BSC releases it. The
period of idle time is specified by a timer, which is determined by the
DYNCHFREETM (BSC6900, BSC6910) parameter. If PS services occupy the
dynamic PDCH before the timer expires, the timer stops. After all the TBFs on the
dynamic PDCH are released, the timer restarts.
The CS service preempts the dynamic PDCH when no TCHs are available for
allocation. If the Abis interface uses the High-Level Data Link Control (HDLC)
transmission or IP transmission, the CS service also preempts the dynamic PDCH
when no Abis transmission resources are available.
NOTE
To improve the PS service performance, the BSC enables the GBFD-119505 PDCH
Dynamic Adjustment with Two Thresholds feature when both the following
conditions are met:
● CHIDLHIGHTHR (BSC6900, BSC6910) is set to a value other than 100.
● The Um interface resources and digital signal processing (DSP) resources are
insufficient.
● The proportion of idle CS channels in the cell is less than the value of
CHIDLLOWTHR (BSC6900, BSC6910).
– The MS multiplexing rates on the uplink and downlink PDCHs are less
than the values of UPDYNCHNTRANLEV (BSC6900, BSC6910) and
DWNDYNCHNTRANLEV (BSC6900, BSC6910) respectively.
● PSDUALTHROPTSW (BSC6900, BSC6910) is set to OFF(Off) and the number
of available idle CS channels in the cell is less than the value of
DYNCHTRANRESLEV (BSC6900, BSC6910).
● Both of the following conditions are met if PSDUALTHROPTSW (BSC6900,
BSC6910) is set to ON(On):
– The proportion of idle channels in the cell is less than the value of
CHIDLLOWTHR (BSC6900, BSC6910).
– The MS multiplexing rates on the uplink and downlink PDCHs are less
than the values of UPDYNCHNRETRANLEV (BSC6900, BSC6910) and
DWNDYNCHNRETRANLEV (BSC6900, BSC6910) respectively.
NOTE
TBF load is the total number of MSs carried on the channels of a cell.
● The cell where dynamic PDCH conversion fails meets any of the following
conditions:
– Less than four PDCHs are allocated to MSs in the cell.
– The uplink TBF load in the cell is greater than the value of
UPDYNCHNTRANLEV (BSC6900, BSC6910) or the downlink TBF load in
the cell is greater than the value of DWNDYNCHNTRANLEV (BSC6900,
BSC6910).
● The cell with the same DSP distribution as the cell where dynamic PDCH
conversion fails meets all the following conditions:
– The PSRESPREEMPTED (BSC6900, BSC6910) parameter is set to
YES(Yes).
– More than four PDCHs are allocated to MSs in the cell.
– The uplink TBF load in the cell is less than the value of
UPDYNCHNTRANLEV (BSC6900, BSC6910) and the downlink TBF load
in the cell is less than the value of DWNDYNCHNTRANLEV (BSC6900,
BSC6910).
If the BSC releases PDCHs in the cells with the same DSP distribution meeting the
previous conditions, the cell whose dynamic PDCH conversion fails preempts the
released PDCHs. If the dynamic PDCH release is triggered because of insufficient
DSP resources, only one PDCH is released at a time.
Table 6-1 Indexes of factors for a dynamic PDCH release due to preemption
by CS services and insufficient resources when EnPDAdminOpt (BSC6900,
BSC6910) and PDCHReclaimPolicy (BSC6900, BSC6910) are set to different
values
NOTE
Table 6-2 Factors for a dynamic PDCH release (with PDCH allocation optimization
disabled)
Table 6-3 Factors for a dynamic PDCH release (with PDCH allocation optimization
enabled)
Priority Factor Description
Table 6-4 Factors for a dynamic PDCH release (with PDCH allocation optimization
enabled and preferential consideration of PS continuity)
Priority Factor Description
Step 1 Filter all dynamic PDCHs in the cell based on the criteria with the highest priority:
● If only one dynamic PDCH meets the criteria, the dynamic PDCH is selected as
the candidate PDCH.
● If multiple dynamic PDCHs meet the criteria, these dynamic PDCHs are
involved in the next round of filtering, as described in Step 2.
● If no dynamic PDCH meets the criteria, all the dynamic PDCHs are involved in
the next round of filtering, as described in Step 2.
Step 2 Filter all the dynamic PDCHs based on the criteria with a lower priority:
● If only one dynamic PDCH meets the criteria, the dynamic PDCH is selected as
the candidate PDCH.
● If multiple dynamic PDCHs meet the criteria, repeat Step 2 until the
corresponding dynamic PDCH is selected.
----End
7 PDCH Repacking
7.1 Overview
In scenarios where PS services are preferentially processed, PDCH repacking
ensures the PDCH continuity and that PDCHs are distributed to several TRXs in a
cell.
If the PDCHREFORMING (BSC6900, BSC6910) parameter is set to YES(YES), the
BSC regards that the TCHs occupied by CS services can be converted to PDCHs
when selecting the optimal channel group. If the selected optimal PDCH group
contains TCHs occupied by CS services, the BSC performs an intra-cell handover
for the MSs processing CS services. Then, the BSC determines whether to convert
the TCHs to PDCHs based on the handover result.
● When the handover succeeds, the BSC automatically converts idle TCHs to
PDCHs.
● When the handover fails:
– If DYNCHNPREEMPTLEV (BSC6900, BSC6910) is set to LEVEL2(No
preempt of service TCHF), the BSC releases CS services and
automatically converts idle TCHs to PDCHs.
– If DYNCHNPREEMPTLEV (BSC6900, BSC6910) is set to a value other
than LEVEL2(No preempt of service TCHF), CS services return to the
original channel and no channel conversion is required.
If PDCHREFORMING (BSC6900, BSC6910) is set to YES(YES) and
EnPDAdminOpt (BSC6900, BSC6910) is set to ON(On), the PDCH repacking uses
the following optimized algorithm:
● During the PDCH conversion, the BSC regards that TCHs occupied by CS
services cannot be converted to PDCHs when selecting the optimal channel
group.
● The PDCH repacking is triggered when the number of converted PDCHs does
not reach the expected number or the PDCH conversion is performed on a
TRX that does not have any PDCH.
● The PDCH repacking is allowed only when the cell load is less than the value
of AMRFULLTOHALFHOTHRESH (BSC6900, BSC6910) and the minimum
value of NOAMRFULLTOHALFTHRESH (BSC6900, BSC6910).
● During the PDCH repacking, the BSC traverses all TRXs configured with
PDCHs in the cell to find a CS user that has the most significant impact on
the PDCH to trigger a forced intra-cell handover.
● After triggering the forced intra-cell handover for the TCH occupied by the CS
user, the BSC starts a timer. Another PDCH repacking can be performed only
after the timer expires.
● The occupied TCH becomes idle after the handover and a conversion from the
TCH to a PDCH is triggered by a new PS user.
Table 7-1 Factors that are considered during intra-cell handover for MSs
processing CS services
Table 8-1 Factors for preferred TRXs selected for PDCH automatic planning
● For a concentric cell, enable the PDCH automatic planning function for the overlaid and
underlaid subcells independently.
● You can run the DSP CHNSTAT command to query the planning result.
----End
9 Related Features
GBFD-114101 GPRS -
GBFD-114201 EGPRS -
Impacted Features
Feature ID Feature Name Description
GBFD-114101 GPRS -
GBFD-114201 EGPRS -
Impacted Features
None
GBFD-114101 GPRS -
GBFD-114201 EGPRS -
Impacted Features
None
Impacted Features
Feature ID Feature Name Description
GBFD-114201 EGPRS -
Impacted Features
None
10 Network Impact
NOTICE
11 Engineering Guidelines
MS None
MSC None
License None
11.3.2 Activation
Using MML Commands
Step 1 On the BSC LMT, run the SET GTRXCHAN command to configure a dynamic
PDCH. In this step, set Channel Type of the target channel to TCHFR(TCH Full
Rate).
Step 2 (Optional) Run the SET GCELLPSCHM command to activate the PDCH
management algorithm optimization. In this step, set PDCH Management
Optimization to ON(On).
Step 3 (Optional) Run the SET GCELLPSCHM command to activate the GPRS load
calculation optimization. In this step, set GPRS Load Calculation Optimize
Switch to ON(On).
Step 4 (Optional) Run the SET GCELLPSCHM command to enable the BSC to
automatically plan preferred GPRS PDCH types. In this step, set GPRS Channel
Priority Type Auto-Planning to ON(On).
● If the cell is not a concentric cell, set Number of EGPRS Normal Channels,
Number of EGPRS Priority Channels, or Number of EGPRS Special
Channels based on the channel type configured for the cell before the
When configuring the PDCH Dynamic Adjustment 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.
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
----End
Number of EgprsSpeC
EGPRS hnum
Special
Channels
Number of EgprsSpeC
EGPRS hnumInn
Special
Channels
(OL
Subcell)
Number of EgprsPriCh
EGPRS numInn
Priority
Channels
(OL
Subcell)
Number of EgprsNorC
EGPRS hnumInn
Normal
Channels
(OL
Subcell)
Expected result: The measurement results show that the value of the AR9303:
Average Number of Available PDCHs counter measured in Step 3.3 is greater than
that measured in Step 3.1.
Step 4 (Optional) Check whether the function of automatically planning preferred GPRS
PDCH types is activated.
On the BSC LMT, run the DSP CHNSTAT command to query the status of channels
for a cell. The results for PDCH Channel Priority Type show the preferred PDCH
types after auto planning.
Step 5 (Optional) Check whether the BSC preferentially considers PS continuity during a
dynamic PDCH release.
Monitor the channel status in a cell on the LMT. The monitoring results show that
the BSC preferentially selects a PDCH with poor PS continuity during a dynamic
PDCH release.
Step 6 (Optional) Check whether the BSC preferentially allocates a 64 kbit/s EGPRS PDCH
to an EGPRS user.
1. Configure a cell with two EGPRS TRXs with four available PDCHs on each TRX.
2. Run the SET GCELLGPRS command to enable the EGPRS function. In this step,
set GPRS to SupportAsInnPcu(Support as built-in PCU) and EDGE to
YES(Yes).
3. Run the SET BTSIDLETS command with Idle Timeslots set to 18 for the test
BTS.
4. Run the SET GCELLPSCHM command with its parameters set as follows:
Set Downlink Multiplex Threshold of Dynamic Channel Conversion to 40.
Set PDCH Downlink Multiplex Threshold to 160.
5. Use MS 1 to access the test cell and perform FTP downloading services.
6. Run the DSP PDCH command to check whether Channel Bandwidth of the
channel occupied by MS 1 is 64K.
7. Use MS 2 to access the test cell and perform FTP downloading services.
8. Run the DSP PDCH command to check whether Channel Bandwidth of the
channel occupied by MS 2 is 64K.
----End
11.3.4 Deactivation
On the BSC LMT, run the SET GCELLPSCHM command with PDCH Management
Optimization set to OFF(Off).
Run the SET GCELLPSCHM command with GPRS Load Calculation Optimize
Switch set to OFF(Off).
Step 4 (Optional) Disable the BSC to automatically plan preferred GPRS PDCH types.
Run the SET GCELLPSCHM command with GPRS Channel Priority Type Auto-
Planning set to OFF(Off).
Run the SET GCELLPSCHM command with Dynamic PDCH Release Policy set to
LOADFIRST(PDCH Load First for Active PDCH Release and Preemption).
Step 6 (Optional) Disable the BSC to preferentially allocate a 64 kbit/s EGPRS PDCH to
an EGPRS user.
Run the SET GCELLPSCHM command with 64K EGPRS PDCH First Switch set to
OFF(Off).
----End
BTS None
GSM None
networking
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
11.6.3 Activation
● Upper Threshold for CS Idle Channel Rate (The value of this parameter
must be less than 100)
● Lower Threshold for CS Idle Channel Rate (The value of this parameter
must be less than 100)
● Inter_Cell PS Resource Preempt Allowed
● PS Two Thresholds Optimized Switch
● Dynamic PDCH Release UL Multiplex Threshold
● Dynamic PDCH Release DL Multiplex Threshold
● Inter_Cell PS Resource Preempted Allowed
Step 2 Run the SET BTSOTHPARA command with PS Service Guaranteed Rate set to
64K(64K).
----End
Step 2 Run the DSP PDCH command to query the number of PDCHs occupied by the MS
and the number of TBFs on the PDCHs. In this step, set Cell Index to the index of
the serving cell.
Step 4 Run the DSP PDCH command to query the number of PDCHs occupied by the MS
and the number of TBFs on the PDCHs. In this step, set Cell Index to the index of
the serving cell.
----End
11.6.5 Deactivation
Aspect Requirement
BTS None
Aspect Requirement
GSM None
networking
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
11.7.2 Activation
Using MML Commands
Step 1 Configure an EGPRS TRX for the cell.
Step 2 On the BSC LMT, run the SET GCELLGPRS command to enable the EGPRS
function. In this step, set GPRS to SupportAsInnPcu(Support as built-in PCU)
and EDGE to YES(Yes).F
Step 3 On the BSC LMT, run the SET GTRXCHAN command with TRX ID, Channel No.,
Channel Type, and PDCH Channel Priority Type set to appropriate values.
Expected result: The values of Channel Type of six channels are PDTCH(PDTCH),
and the values of PDCH Channel Priority Type are EGPRSSPECH(EGPRS Special
Channel).
----End
When configuring the Packet Channel Dispatching 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.
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
----End
A GPRS MS (class10) that supports only GPRS service and an EGPRS MS (class10) that
supports only EGPRS service are available.
Step 1 Start the PS Um interface trace task for the test MS to monitor the channel status.
For the detailed operations, see BSC6900 GSM LMT User Guide or BSC6910 GSM
LMT User Guide.
Step 2 Use the GPRS MS to initiate the PDP context activation.
Step 3 Attach the EGPRS MS to the EGPRS network and initiate the PDP context
activation.
Expected result:
● The GPRS MS cannot initiate an EGPRS attach and PDP activation.
● The EGPRS MS can be attached to the EGPRS network and successfully
activate the PDP context.
----End
11.7.4 Deactivation
Using MML Commands
On the BSC LMT, run the SET GTRXCHAN command with Channel Type set to
PDTCH(PDTCH) and PDCH Channel Priority Type to a value other than
EGPRSSPECH(EGPRS Special Channel).
When configuring the Packet Channel Dispatching 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.
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
----End
Aspect Requirement
BTS None
Aspect Requirement
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
11.8.2 Activation
Using MML Commands
Step 1 Configure two EGPRS TRXs for the cell.
Step 2 On the BSC LMT, run the SET GCELLGPRS command to enable the EGPRS
function. In this step, set GPRS to SupportAsInnPcu(Support as built-in PCU)
and EDGE to YES(Yes).
Step 3 Run the SET GTRXCHANADMSTAT command with TRX ID set to the index of the
BCCH TRX, and Channel No. and Administrative State set to appropriate values.
Expected result: The values of Administrative State for all the service channels on
the BCCH TRX are Lock(Lock).
Step 4 Run the SET GTRXCHAN command with TRX ID set to the index of the EGPRS-
capable TRX, and Channel Type and PDCH Channel Priority Type set to
appropriate values.
The values of Channel Type are PDTCH(PDTCH). The values of PDCH Channel
Priority Type of four channels are EGPRSPRICH(EGPRS Priority Channel) and
PDCH Channel Priority Type of the other four channels is GPRS(GPRS Channel).
----End
The GPRS MS 1 (class10), GPRS MS 2 (class10), and EGPRS MS1 (class10) have been
attached to a test cell.
Step 2 EGPRS MS 1 activates a PDP context and starts to download data using FTP.
Step 3 GPRS MS 1 activates a PDP context and starts to download data using FTP.
Step 4 GPRS MS 2 activates a PDP context and starts to download data using FTP.
Step 5 EGPRS MS 1 stops downloading data using FTP and releases the PDCHs.
Step 6 After a period of time, EGPRS MS 1 starts to download data using FTP again.
Step 7 Use a drive test tool to record the number of PDCHs occupied by each MS in the
preceding steps.
Expected result:
● After EGPRS MS 1 activates a PDP context for the first time, it downloads data
using FTP on the EGPRS Preferred channel.
● The GPRS MS 2 shares PDCHs with GPRS MS 1 to download data using FTP.
The BSC will not allocate an EGPRS Preferred channel to GPRS MS 2.
● After EGPRS MS1 stops downloading data using FTP and releases the EGPRS
priority PDCH, the BSC allocates the PDCH to either GPRS MS 1 or GPRS MS 2
so that they no longer share the same PDCH.
● After EGPRS MS 1 starts to download data using FTP again, GPRS MS2 or
GPRS MS1 is switched out of the EGPRS Preferred channel so that GPRS MS 1
and GPRS MS 2 still share the same PDCHs.
● EGPRS MS 1 still downloads data using FTP on the EGPRS Preferred channel.
----End
11.8.4 Deactivation
BTS None
GSM None
networking
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
11.9.2 Activation
Using MML Commands
Step 1 Configure an EGPRS TRX for the cell.
Step 2 On the BSC LMT, run the SET GTRXCHAN command with its parameters set as
follows:
● Set TRX ID to the index of the EGPRS-capable TRX.
● Set Channel Type to PDTCH(PDTCH).
● Set PDCH Channel Priority Type to EGPRSNORCH(EGPRS Normal
Channel).
Step 3 Run the SET BSCPSSOFTPARA command with Allow E Down G Up Switch set to
CLOSE(Close).
----End
When configuring the Packet Channel Dispatching 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.
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 through the MAE-
----End
Two GPRS MSs (class 8) and one EGPRS MS (class10) are available.
Step 1 Attach GPRS MS 1 to the GPRS network and initiate the PDP context activation.
GPRS MS 1 starts to upload data using FTP on an uplink channel. The downlink
channels are not used.
Step 2 Attach EGPRS MS 1 to the EGPRS network and initiate the PDP context activation.
EGPRS MS 1 starts to download data using FTP on a different PDCH from the
PDCH used by GPRS MS 1.
Step 3 Attach GPRS MS 2 to the GPRS network and initiate the PDP context activation.
GPRS MS 1 starts to upload data using FTP on the same PDCH used by GPRS MS
1.
Step 4 Record the PDCHs used by each MS.
Expected result:
● After EGPRS MS 1 accesses the cell and starts to download data using FTP, the
BSC does not multiplex the uplink channel of GPRS MS 1 and the downlink
channel of EGPRS MS1 onto the same PDCH.
● After GPRS MS 2 accesses the cell and starts to upload data using FTP, the
BSC does not multiplex the uplink channel of GPRS MS 2 and the downlink
channel of EGPRS MS1 onto the same PDCH.
----End
11.9.4 Deactivation
Using MML Commands
On the BSC LMT, run the SET BSCPSSOFTPARA command with Allow E Down G
Up Switch set to OPEN(Open).
When configuring the Packet Channel Dispatching 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.
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
----End
These counters reflect the gain in the efficiency in which PDCHs carry TBFs.
NOTICE
NOTICE
The following configurations are not mandatory for dynamic PDCH allocation
optimization. But if the following configurations do not apply, the optimization on
PDCH allocation algorithms has no significant gains.
NOTICE
11.12 Troubleshooting
Fault Description (6900)
Run the DSP PDCHNUM command to check whether the number of activated
PDCHs reaches the specification of all DSPs. If it does, PDCHs released by a cell
will be immediately occupied by other cells once this cell resets. When this occurs,
this cell cannot activate any PDCH after reset completion, because the number of
activated PDCHs has reached the DSP specification. This cell can restore PS
services only when an idle PDCH is available.
Troubleshooting Procedure (6900)
You are advised to add DPUg boards for capacity expansion.
If this problem persists after capacity expansion, contact Huawei technical
engineers.
Fault Description (6910)
Run the DSP PDCHNUM command to check whether the number of activated
PDCHs reaches the specification of all GUPPSs. If it does, PDCHs released by a cell
will be immediately occupied by other cells once this cell resets. When this occurs,
this cell cannot activate any PDCH after reset completion, because the number of
activated PDCHs has reached the GUPPS specification. This cell can restore PS
services only when an idle PDCH is available.
Troubleshooting Procedure (6910)
You are advised to add GCUP boards for capacity expansion.
If this problem persists after capacity expansion, contact Huawei technical
engineers.
12 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.
NOTE
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.
13 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.
NOTE
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.
14 Glossary
15 Reference Documents
1. 3GPP TS 44.060 "Mobile Station (MS) - Base Station System (BSS) interface;
Radio Link Control/Medium Access Control (RLC/MAC) protocol"
2. 3GPP TS 44.018 "Mobile Radio Interface Layer 3 Specification – Radio
Resource Control (RRC) Protocol"
3. 3GPP TS 45.002 "Radio Access Network; Multiplexing and multiple access on
the radio path"
4. 3GPP TS 24.008, 3GPP TS 48.018, and 3GPP TS 48.016 peer layer protocols
between the BSS and the SGSN