BSS Feature Description (Continue) PDF

HUAWEI BSC6000 Base Station Subsystem
BSS Feature Description
20 EGPRS
20
EGPRS
About This Chapter

20.1 Overview
This describes the EGPRS. The Enhanced Data Rate for GSM Evolution (EDGE) can provide
high-rate data services.
20.2 Availability
This lists the NEs, software versions, licenses, and other conditions required for the
implementation of EDGE.
20.3 Impact
This describes the impact of EGPRS on system performance.
20.4 Technical Description
This describes the technical aspects of EDGE. EDGE is an evolution stage of PS services. It can
be called as 2.75 G mobile communication technology. If the equipment on the current network
remains unchanged, EDGE can be implemented through the upgrade of relevant software. EDGE
can enhance the transmission rate of PS data.
20.5 Capabilities
This describes the EDGE capabilities of the built-in PCU and external PCU.
20.6 Implementation
EDGE implementation consists of configuring EDGE with the built-in PCU and configuring
EDGE with the external PCU.
20.7 Maintenance Information
This lists the alarms and counters related to EDGE.
20.8 References
The references indicate the documents about EDGE from the related standard organizations.
Issue 03 (2009-06-08)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
20-1

20 EGPRS
20.1 Overview
This describes the EGPRS. The Enhanced Data Rate for GSM Evolution (EDGE) can provide
high-rate data services.
Definition
EDGE consists of the Enhanced GPRS (EGPRS) and the Enhanced Circuit Switched Data
(ECSD).
l
EGPRS is the enhanced GPRS. EGPRS uses the 8PSK modulation mode so that the rate
of a single channel is improved. The maximum rate of a single channel is 59.2 kbit/s.
ECSD is the enhanced High Speed Circuit Switched Data (HSCSD).

NOTE
The Huawei BSS supports only EGPRS. Unless otherwise specified, EDGE referred to in this document
indicates EGPRS.
Purposes
Using the new modulation and coding schemes, EDGE greatly improves the data service rates.
The data transmission rates on the Um interface in EDGE are almost three times those in GSM.
This meets the requirements of high-rate data services.
Term
None.
Acronyms and Abbreviations
20-2
Acronym and
Abbreviation
Full Spelling
EDGE
Enhanced Data Rate for GSM Evolution
GPRS
General Packet Radio Service
PCIC
Packet Circuit Identity Code
BER
Bit Error Rate
BVC
BSSGP Virtual Connection
BSSGP
Base Station System GPRS Protocol
QoS
Quality of Service
TBF
Temporary Block Flow
CCCH
Common Control Channel
PCCCH
Packet Common Control Channel
PACCH
Packet Associated Control Channel

Issue 03 (2009-06-08)

20 EGPRS
Acronym and
Abbreviation
Full Spelling
RLC
Radio Link Control
20.2 Availability
This lists the NEs, software versions, licenses, and other conditions required for the
implementation of EDGE.
NEs Involved
Table 20-1 lists the network elements (NEs) involved in EDGE.
Table 20-1 NEs Involved in EDGE
MS
BTS
BSC
PCU
SGSN
GGSN
MSC
HLR
NOTE
l -: not involved
l : involved
Software Versions
Table 20-2 lists the versions of GBSS products that support EDGE.
Table 20-2 GBSS products and software versions
Product
Version
BSC
BSC6000
V900R008C01 and later versions
BTS
BTS3X
G3BTS32V302R002C05 and later versions
BTS3012A
All versions
BTS3001C
All versions
BTS3002C
All versions
BTS3002E
BTS3000V100R002C01 and later versions
BTS3006C
BTS3012
Issue 03 (2009-06-08)
DTRU
QTRU

20-3

20 EGPRS
Product
Version
BTS3012
AE
DTRU
QTRU
BTS3900 GSM
BTS3900A GSM
DBS3900 GSM
Miscellaneous
l
The EDGE Support can be configured only when the GPRS Support is configured.
For the concentric cell, the configuration between the overlaid subcell and the underlaid
subcell should be the same; that is, the overlaid subcell and underlaid subcell should be
configured in such as way that they both support EDGE or both do not support EDGE.
20.3 Impact
This describes the impact of EGPRS on system performance.
Impact on System Performance

l
When the EDGE function is enabled, the maximum number of TRXs supported by one E1
cable in different network topologies decreases. Thus, the number of TRXs that each GMPS
or GEPS supports decreases.
NOTE
The number of idle timeslots and TRXs that each E1 cable can be configured with must meet the
following requirement: The number of configured TRXs + the number of configured idle timeslots/
8 the maximum number of configurable TRXs.
l
When the external PCU is used and the EDGE function is enabled, the capacity of each
RPPU in the PCU decreases. The number of PDCHs that can be activated on each RPPU
decreases from 120 to 100.
Impact on Other Features

None.

This describes the technical aspects of EDGE. EDGE is an evolution stage of PS services. It can
be called as 2.75 G mobile communication technology. If the equipment on the current network
remains unchanged, EDGE can be implemented through the upgrade of relevant software. EDGE
can enhance the transmission rate of PS data.
20-4

Issue 03 (2009-06-08)

20 EGPRS
20.4.1 8PSK Modulation Mode

This describes the 8PSK modulation mode. In 8PSK modulation mode, symbols represent the
absolute phases of signals. There are eight possible symbols and each symbol represents three
bits of information.
The GSM system uses the Gaussian Minimum Shift Keying (GMSK) modulation mode. In
GMSK modulation mode, bit 0 or 1 indicates the change in signal phases. Each phase change
is represented by a symbol.
In 8PSK modulation mode, symbols represent the absolute phases of signals. There are eight
possible symbols and each symbol represents three bits of information. Therefore, the data rate
on the Um interface in EDGE can theoretically be three times that in GSM.
Figure 20-1 shows the I/Q relations for the modulation and demodulation in GSM and EDGE.
Figure 20-1 I/Q relations for the modulation and demodulation in GSM and EDGE
GPRS:
GMSK modulation
EGPRS:
8PSK modulation
Q
Q
(0,1,0)
(0,1,1)
(0,0,0)
(0,0,1)
I
I
(1,1,1)
0
(1,1,0)
(1,0,1)
(1,0,0)
NOTE
In terms of performance, the 8PSK modulation mode is better than the GMSK modulation mode. The
demodulation threshold of the 8PSK mode, however, is higher than the demodulation threshold of the
GMSK mode. The modulation mode is radio environment specific. The PCU automatically adjusts the
modulation mode based on the BER report from an MS. Therefore, the modulation and demodulation mode
that EDGE uses can be 8PSK or GMSK.
Table 20-3 lists the modulation bits and corresponding symbols shown in Figure 20-1.
Table 20-3 Modulation bits and corresponding symbols
Issue 03 (2009-06-08)
Modulation Bit
Symbol
(1,1,1)
(0,1,1)
1
20-5

20 EGPRS
Modulation Bit
Symbol
(0,1,0)
(0,0,0)
(0,0,1)
(1,0,1)
(1,0,0)
(1,1,0)
NOTE
Table 20-3 lists all the modulation bits and corresponding symbols.
20.4.2 EGPRS Transmit Power

This describes the transmit power of a BTS that uses 8PSK modulation mode.
From the perspective of network operation, the transceiver of the BTS in EDGE must have the
same spectrum features as those of an ordinary transceiver. When sending the signals modulated
in 8PSK modulation mode, the transceiver of the BTS in EDGE uses the transmit power that is
2 dB5 dB less than the average power in GMSK modulation mode. Thus, the requirements for
spectrum can be met. In the system, the cell parameter 8PSK power attenuation grade and the
trx parameter TRX 8PSK Level can be specified to meet the requirements.
On the BCCH, the transmit power of the signals modulated in 8PSK modulation mode is at most
4 dB less than the average transmit power of the signals modulated in GMSK modulation mode.
On the timeslot located before the timeslot of the BCCH/CCCH, the transmit power of the signals
modulated in 8PSK mode is at most 2 dB less than that of the signals modulated in GMSK
modulation mode.
20.4.3 MCS-1 to MCS-9 Coding Schemes

This describes MCS-1 to MCS-9 modulation and coding schemes used in EDGE.
EDGE uses MCS-1 to MCS-9 modulation and coding schemes, as listed in Table 20-4.
Table 20-4 Modulation and coding schemes in EDGE
20-6
Coding Scheme
Modulation Mode
Number of Bits
in the Payload of
Each Burst
Rate (kbit/s)
MCS-9
8PSK
2 x 592
59.2
MCS-8
2 x 544
54.4
MCS-7
2 x 448
44.8

Issue 03 (2009-06-08)

Coding Scheme
20 EGPRS
Modulation Mode
Number of Bits
in the Payload of
Each Burst
Rate (kbit/s)
592
29.6
544 + 48
27.2
448
22.4
352
17.6
296
14.8
272 + 24
13.6
MCS-2
224
11.2
MCS-1
176
8.8
MCS-6
MCS-5
MCS-4
GMSK
MCS-3
NOTE
For 544 + 48 and 272 + 24 in the previous table, 544 and 272 indicate the significant bits, and 48 and 24
indicate the padding bits.
The initial coding schemes used in EDGE can be specified through the parameters Uplink
Default MCS Type and Downlink Default MCS Type. When the EDGE service is used,
whether the uplink/downlink is adjusted based on the signal transmission quality depends on the
setting of the parameters Uplink Fixed MCS Type and Downlink Fixed MCS Type.
Figure 20-2 shows the rates of GPRS channels and those of EDGE channels.
Figure 20-2 Rates of GPRS channels and those of EDGE channels
kbit/s
59.2
60.0
54.4
GPRS
50.0
44.8
EDGE
40.0
29.6
30.0
20.2
20.0
12.2
10.0
22.4
14.8
14.4
8.8
8.0
17.6
11.2
0.0
CS-1
CS-2
CS-3 CS-4
MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9
GMSK
modulation
Issue 03 (2009-06-08)

8PSK
modulation
20-7

20 EGPRS
20.4.4 Link Quality Control

This describes the link quality control. The link quality control enables the system to adapt to
the radio transmission environment dynamically by changing modulation and coding schemes
during data transmission, thus improving the link quality.
EDGE uses a set of high-efficient link quality control algorithm. EDGE has two link quality
control modes: Link Adaptation (LA) and Incremental Redundancy (IR). The link quality control
mode is set through the parameter Link Quality Control Mode. For the cells where the signal
quality on the Um interface is good, this parameter is set to LA.
Basic Principle of LA
During data transmission, the sender retransmits the original data block or segments the original
data block into two data blocks and then transmits them. The receiver need not restore the
previous erroneous data blocks.
Basic Principle of IR
During data transmission, the sender does not consider the radio transmission environment at
first and uses a high data rate coding scheme for the data transmission. Although the data rate
is high, the capability of data protection is weak. If the data is received incorrectly, the sender
retransmits additional coding information. The receiver combines the new information with the
previous information and then performs decoding. The previous process is repeated until the
decoding succeeds.
l
During uplink data transmission, the system notifies an MS to use the IR mode by setting
RESEGMENT in the uplink resource assignment message to 0 (segmentation forbidden).
In IR mode, the receiver should have sufficient memory to save the history information. If
the network memory is insufficient, the system can notify the MS of the memory
insufficiency by setting RESEGMENT in the UPLINK ACK/NACK message to 1.
During downlink data transmission, if the memory of an MS is insufficient, the MS can

send MS OUT OF MEMORY to the network through a DOWNLINK ACK/NACK
message. Then, the network cannot use the IR mode in downlink data transmission.
20.4.5 Types of Preferred EGPRS Channels

This describes the types of preferred channels in EGPRS.
The preferred channel types are as follows:
l
EGPRS dedicated channel

EGPRS dedicated channels can be used by only EGPRS MSs.
EGPRS preferred channel

EGPRS preferred channels are preferentially used by EGPRS MSs. The EGPRS preferred
channels can be used by GPRS MSs when the channels are in the idle state. When an EGPRS
MS requests an EGPRS preferred channel, the GPRS MS that occupies the EGPRS
preferred channel should be transferred to other channels. The signals of an EGPRS MS
and those of a GPRS MS cannot be multiplexed onto one EGPRS preferred channel.
Normal EGPRS channel

Normal EGPRS channels can be used by GPRS MSs and EGPRS MSs.
20-8
GPRS channel
Issue 03 (2009-06-08)

20 EGPRS
GPRS channels are used by GPRS MSs. If a cell is not configured with EGPRS channels,
EGPRS MSs in the cell preferentially use GPRS channels to process GPRS services.
l
Non-GPRS channel
Non-GPRS channels are not used for packet services.
When configuring Channel Type on the TRX, you can select the channel type through GPRS
Channel Priority Type.
When the system allocates PDCHs, the preferred channel type varies according to packet data
services.
l
For the GPRS service, the GPRS channels are preferentially assigned. Then the normal
EGPRS channels are assigned and finally the EGPRS preferred channels are assigned.
For the EGPRS service, the EGPRS dedicated channels are preferentially assigned. Then
the EGPRS preferred channels are assigned and finally the normal EGPRS channels are
assigned.
On the normal EGPRS channel, the GPRS MS may use the uplink channel, and the EGPRS MS
may use the downlink channel. The parameter Allow E Down G Up Switch can be set to avoid
channel multiplexing. If you want to eliminate the possibility of EDGE/GPRS co-timeslot, do
not configure normal EGPRS channels.
NOTE
Channels should be selected according to the preferred channel type. For example, if the channels on the
TRX that supports EGPRS are configured as GPRS channels, these channels can be used for only GPRS
services. EGPRS dedicated channels can be configured only as static channels. Other three types of
preferred channels can be configured as static or dynamic channels.
20.4.6 CCCH 11Bit EGPRS Access

EDGE supports 11Bit EGPRS access on the CCCH. EDGE reduces the access delay and
improves the access performance of the MS.
The access process of the 11Bit EGPRS on the CCCH is as follows:
1.
The MS sends the 11bit EGPRS PAKCET CHANNEL REQUEST message on the CCCH
for one phase packet access.
2.
The network assigns the EDGE channel for the MS through the IMMEDIATE
ASSIGNMENT message. Therefore, the EGPRS TBF is established.
Whether to enable CCCH 11Bit EGPRS access depends on the setting of the parameter Support
11BIT EGPRS Access.
20.4.7 Assignment of Idle Timeslots

For packet data services, the Abis interface supports the mapping of several timeslots to one
traffic channel. Then, the timeslots are divided and combined on the TX and RX ends.
The data rate of each timeslot on the Abis interface is 16 kbit/s. In EDGE, the data rate can be
59.2 kbit/s. In GPRS, the CS-3/CS-4 coding scheme needs to be added with a subtimeslot. In
EDGE, each PDCH can be added with three subtimeslots. EDGE coding schemes are MCS1 to
MCS9. The number of Abis links required for different coding schemes is different, as described
in Table 20-5.
Issue 03 (2009-06-08)

20-9

20 EGPRS
Table 20-5 Coding schemes and number of required Abis links

Coding Scheme
Number of Required Abis Links
MCS-1MCS-2
MCS-3MCS-6
MCS-7
MCS-8MCS-9
The number of idle timeslots on the Abis interface requested during EDGE coding scheme
adjustment is related to the coding scheme. As described in Table 20-5, when EDGE uses coding
schemes MCS-3-MCS-6, an idle timeslot on the Abis interface is required. The idle timeslots
on the Abis interface in the same BTS can be allocated to any PDCH on any TRX in the same
cabinet group. The idle timeslot on the Abis interface is set through the parameter Idle
Timeslots.
NOTE
When the Abis interface uses IP or HDLC transmission, there is no idle timeslot configuration.
When the Flex Abis feature of the BTS is enabled, if the CS traffic is light, idle timeslots may not be
configured and the EDGE service can still run normally.
When the Flex Abis feature of the BTS is enabled, if the CS traffic is heavy, idle timeslots should be
configured. Otherwise, the EDGE service may fail for a long time.
20.5 Capabilities
This describes the EDGE capabilities of the built-in PCU and external PCU.
Built-in PCU
The EDGE capabilities of the built-in PCU are as follows:
20-10
The system uses the resource pool redundancy configuration mode. The maximum
configuration that the system can support is 8 + 1 = 9 GDPUPs.
The maximum number of cells supported by each GDPUP is 1,024.
The maximum number of activated PDCHs supported by each GDPUP is 1,024. All the
channels support the MCS9 coding scheme.
The maximum number of configurable PDCHs is 15,360.
The maximum number of activated PDCHs in full configuration is 8,192. All the channels
support the MCS9 coding scheme.
The maximum throughput on the Gb interface is 512 Mbit/s.
The maximum number of uplink PDCHs that can be used by a single MS is 4.
The maximum number of downlink PDCHs that can be used by a single MS is 5.
The maximum number of pairs of configured GFGUGs/GEPUGs are 8.

Issue 03 (2009-06-08)

20 EGPRS
External PCU
The EDGE capabilities of the external PCU are as follows:
l
The BSC supports 256 E1 lines on the Pb interface.
Each GMPS/GEPS subrack supports 64 E1 lines on the Pb interface.
Each GEIUP/GOIUP supports 32 E1 lines on the Pb interface.
The GOIUP provides one STM-1 port, which carries 63 E1 links.
20.6 Implementation
EDGE implementation consists of configuring EDGE with the built-in PCU and configuring
EDGE with the external PCU.
20.6.1 Configuring EGPRS (with Built-in PCU)

This describes how to configure EDGE on the BSC6000 Local Maintenance Terminal.
Prerequisite
l
The system is configured to support GPRS. For details about how to configure GPRS with
the built-in PCU, see 19.6.5 Configuring GPRS (with External PCU).
The subrack-OSP mapping is configured. For details, refer to Configuring the SubrackOSP Mapping.
The license is applied and activated. To apply for and activate the license, do as follows:
1.
2.
In the BSC6000V900R008 Exceptional Commercial License Application Template,

fill in the following information.
Fill in the number of PDCHs to be purchased in the Number of resources column

corresponding to the Maximum Number of PDCH Groups Activated in the
Resource control items column.
Fill in the number of TRXs to be purchased in the Number of resources column

corresponding to the Number of the TRX Supporting EDGE in the Resource
control items column.
Activate the license on the Local Maintenance Terminal. For details, refer to
Activating the BSC License.
Procedure
Step 1 Configure site idle timeslot.
1.
Issue 03 (2009-06-08)
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target BTS, and then choose Configure Site Idle Timeslot from the shortcut
menu. A dialog box is displayed, as shown in Figure 20-3.

20-11

20 EGPRS
Figure 20-3 Configure Site Idle Timeslot dialog box
2.
In the Idle Timeslot area, click the box under the Idle Timeslots area, and then enter the
number of idle timeslots to be configured.
3.
Click Finish to end the configuration.

NOTE
Idle Timeslots should be configured only when TransType of the BSC is set to TDM.
When the Flex Abis feature of the BTS is enabled, if the CS traffic is light, idle timeslots may not be
configured and the EDGE service can still run normally.
When the Flex Abis feature of the BTS is enabled, if the CS traffic is heavy, idle timeslots should be
configured. Otherwise, the EDGE service may fail for a long time.
Step 2 Configure the cell to support EDGE.
20-12
1.
On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management

Tree tab page, and then choose Set Cell Attributes from the shortcut menu.
2.
In the displayed dialog box, double-click the target cell in the Cell view list box to add it
to the Selected cells list box. Then, click Next.
3.
In the Cells to be set list box, select the target cell, and then click Set Cell Attributes. A
dialog box is displayed, as shown in Figure 20-4.

Issue 03 (2009-06-08)

20 EGPRS
Figure 20-4 Set Other Parameter dialog box
4.
Select EDGE Support.
5.
Click OK to end the configuration.
Step 3 Configure the channel type.

1.
On the BSC6000 Local Maintenance Terminal, right-click a TRX on the Management

Tree tab page, and then choose Configure TRX Attributes from the shortcut menu.
2.
In the displayed dialog box, select the target TRX in the TRX view list box, and then click
Configure TRX Attributes.
3.
In the displayed dialog box, click the Channel Attributes tab, as shown in Figure 20-5.
Issue 03 (2009-06-08)

20-13

20 EGPRS
Figure 20-5 Channel Attributes tab page
4.
Select Channel No., and then select the channel type that supports packet services such as
PDTCH or TCH Full Rate in the Channel Type drop-down list box. Then, set GPRS
Channel Priority Type.
5.
----End
20.6.2 Configuring EGPRS (with External PCU)

This describes how to configure EDGE on the BSC6000 Local Maintenance Terminal.
Prerequisite
l
The system is configured to support GPRS. For details about how to configure GPRS with
the external PCU, refer to 19.6.5 Configuring GPRS (with External PCU).
The subrack-OSP mapping is configured. For details, refer to Configuring the SubrackOSP Mapping.
1.

fill in the following information.
20-14
Fill in the number of PDCHs to be purchased in the Number of resources column

corresponding to the Maximum Number of PDCH Groups Activated in the
Resource control items column.
Issue 03 (2009-06-08)

2.
20 EGPRS
Fill in the number of TRXs to be purchased in the Number of resources column

corresponding to the Number of the TRX Supporting EDGE in the Resource
control items column.
Procedure
Step 1 Configure Site Idle Timeslot dialog box
1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target BTS, and then choose Configure Site Idle Timeslot from the shortcut
Figure 20-6 Configure Site Idle Timeslot dialog box
2.
In the Idle Timeslot area, click the box under the Idle Timeslots area, and then enter the
number of idle timeslots to be configured.
3.
Click Finish to end the configuration.

NOTE
Idle Timeslots should be configured only when TransType of the BSC is set to TDM.
When the Flex Abis feature of the BTS is enabled, idle timeslots may not be configured and the EDGE
service can still run normally,if the CS traffic is light.
When the Flex Abis feature of the BTS is enabled, idle timeslots should be configured. Otherwise, the
EDGE service may fail for a long time,if the CS traffic is heavy.
Step 2 Configure the cell to support EDGE.

Issue 03 (2009-06-08)

20-15

20 EGPRS
1.

Tree tab page, and then choose Configure Cell Attributes from the shortcut menu.
2.
3.
In the Cells to be set list box, select the target cell, and then click Set Cell Attributes. A
4.
Select EDGE Support.
5.
Step 3 Configure the channel type.

1.
20-16
On the BSC6000 Local Maintenance Terminal, right-click a TRX on the Management

Tree tab page, and then choose Configure TRX Attributes from the shortcut menu.
Issue 03 (2009-06-08)

20 EGPRS
2.
In the displayed dialog box, select the target TRX in the TRX view list box, and then click
Configure TRX Attributes.
3.
In the displayed dialog box, click the Channel Attributes tab, as shown in Figure 20-8.
Figure 20-8 Channel Attributes tab page
4.
Select Channel No., and then select PDTCH or Dynamic PDCH in the Channel Type
drop-down list box. Then, set GPRS Channel Priority Type.
5.
----End

This lists the alarms and counters related to EDGE.
Alarms
The alarms related to EDGE consist of alarms related to the built-in PCU and alarms related to
the external PCU, as listed in Table 20-6 and Table 20-7.
Issue 03 (2009-06-08)

20-17

20 EGPRS
Table 20-6 Alarms related to the built-in PCU

Alarm ID
Alarm Name
291
Cell Transmission Delay Abnormal
293
GB BC Faulty
294
TRX Config Error
331
NSVC Faulty
332
NSVL Faulty
333
NSE Faulty
340
Cell PS Service Faulty
341
DSP Resource Overload
342
PTP BVC Faulty
343
NSVL Dynamic Configuration Process Failure
344
FAULTY DSP OVER LIMIT
Table 20-7 Alarms related to the external PCU

Alarm ID
Alarm Name
104
All PBSLs in the PCU Are Faulty
128
No Circuit Configured in the PCU
Counters
The counters related to EDGE consist of counters related to the built-in PCU and counters related
to the external PCU, as listed in Table 20-8 and Table 20-9.
Table 20-8 Counters related to the built-in PCU
20-18
Counter
Description
A331
Delivered Paging Messages for PS Service
ZTA308H
Immediate Assignment Requests per BSC (PS

Service)
A031
SGSN-Initiated Paging Requests for PS

Service
L3188D
PACKET CCCH LOAD IND Messages Sent

on Abis Interface

Issue 03 (2009-06-08)

Issue 03 (2009-06-08)
20 EGPRS
Counter
Description
A9201
Number of Uplink EGPRS TBF

Establishment Attempts
A9202
Number of Successful Uplink EGPRS TBF

Establishments
A9203
Number of Failed Uplink EGPRS TBF

Establishments due to No Channel
A9204
Number of Failed Uplink EGPRS TBF

Establishments due to MS No Response
A9205
Number of Uplink EGPRS TBF Normal

Releases
A9206
Number of Uplink EGPRS TBF Abnormal

Releases due to N3101 Overflow (MS No
Response)
A9207

Releases due to N3103 Overflow (MS No
Response)
A9208

Releases due to SUSPEND
A9209

Releases due to FLUSH
A9210

Releases due to No Channel
A9211
Total Number of Sampled Concurrent Uplink

EGPRS TBFs
A9212
Sampling Times of Concurrent Uplink

EGPRS TBFs
AA9213
Average Number of Concurrent Uplink

EGPRS TBFs
A9214
Total Duration of Uplink EGPRS TBF (ms)
AA9215
Average Duration of Uplink EGPRS TBF (s)
A9301
Number of Downlink EGPRS TBF

Establishment Attempts
A9302
Number of Successful Downlink EGPRS

TBF Establishments
A9303
Number of Failed Downlink EGPRS TBF

Establishments due to No Channel
A9304
Number of Failed Downlink EGPRS TBF

Establishments due to MS No Response

20-19

20 EGPRS
20-20
Counter
Description
A9305
Number of Downlink EGPRS TBF Normal

Releases
A9306
Number of Downlink EGPRS TBF Abnormal

Releases due to N3105 Overflow
A9307

Releases due to SUSPEND
A9308

Releases due to FLUSH
A9309

Releases due to No Channel
A9310
Total Number of Sampled Concurrent

Downlink EGPRS TBFs
A9311
Sampling Times of Concurrent Downlink

EGPRS TBFs
AA9312
Average Number of Concurrent Downlink

EGPRS TBFs
A9313
Total Duration of Downlink EGPRS TBF

(ms)
AA9314
Average Duration of Downlink EGPRS TBF

(s)
L9201
Total Number of Uplink EGPRS RLC Data

Blocks
L9202
Total Number of Uplink EGPRS MCS1 RLC

Data Blocks
L9203

Data Blocks
L9204

Data Blocks
L9205

Data Blocks
L9206

Data Blocks
L9207

Data Blocks
L9208

Data Blocks
L9209

Data Blocks

Issue 03 (2009-06-08)

Issue 03 (2009-06-08)
20 EGPRS
Counter
Description
L9210

Data Blocks
L9211
Total Number of Valid Uplink EGPRS MCS1

RLC Data Blocks
L9212

RLC Data Blocks
L9213

RLC Data Blocks
L9214

RLC Data Blocks
L9215

RLC Data Blocks
L9216

RLC Data Blocks
L9217

RLC Data Blocks
L9218

RLC Data Blocks
L9219

RLC Data Blocks
RL9220
Retransmission Rate of Uplink EGPRS

MCS1 RLC Data Block (%)
RL9221

RL9222

RL9223

RL9224

RL9225

RL9226

RL9227

RL9228


20-21

20 EGPRS
20-22
Counter
Description
L9229
Number of MCS Upgrades on Uplink EGPRS

TBF
L9230
Number of MCS Degrades on Uplink EGPRS

TBF
L9231
Number of Uplink EGPRS RLC Control

Blocks
TL9232
Average Throughput of Uplink EGPRS RLC

(kbit/s)
TL9233
Average Payload of Single Uplink EGPRS

TBF (KB)
L9234
Total Number of Uplink EGPRS TBFs
L9301
Total Number of Downlink EGPRS RLC

Data Blocks
L9302
Total Number of Downlink EGPRS MCS1

RLC Data Blocks
L9303

RLC Data Blocks
L9304

RLC Data Blocks
L9305

RLC Data Blocks
L9306

RLC Data Blocks
L9307

RLC data blocks
L9308

RLC Data Blocks
L9309

RLC Data Blocks
L9310

RLC Data Blocks
L9311
Total Number of Valid Downlink EGPRS

MCS1 RLC Data Blocks
L9312

L9313


Issue 03 (2009-06-08)

Issue 03 (2009-06-08)
20 EGPRS
Counter
Description
L9314

L9315

L9316

L9317

L9318

L9319

RL9320
Retransmission Rate of Downlink EGPRS

MCS1 RLC Data Blocks (%)
RL9321

RL9322

RL9323

RL9324

RL9325

RL9326

RL9327

RL9328

L9329
Number of MCS Upgrades on Downlink

EGPRS TBF
L9330
Number of MCS Degrades on Downlink

EGPRS TBF
L9331
Number of Downlink EGPRS RLC Control

Blocks
L9332
Number of Downlink EGPRS RLC Dummy

Blocks

20-23

20 EGPRS
20-24
Counter
Description
TL9333
Average Throughput of Downlink EGPRS

RLC (kbit/s)
TL9334
Average Payload of Single Downlink EGPRS

TBF (KB)
L9335
Total Number of Downlink EGPRS TBFs
S9101
Number of Times 8PSK_MEAN_BEP=1
S9102
S9103
S9104
S9105
S9106
S9107
S9108
S9109
S9110
S9111
S9112
S9113
S9114
S9115
S9116
S9117
S9118
S9119
S9120
S9121
S9122
S9123
S9124
S9125
S9126

Issue 03 (2009-06-08)

20 EGPRS
Counter
Description
S9127
S9128
S9129
S9130
S9131
S9132
Table 20-9 Counters related to the external PCU
Issue 03 (2009-06-08)
Counter
Description
AR3015A
Mean Number of Dynamically Configured

Channels (EDGE) (900/850 Cell)
AR3015B

Channels (EDGE) (1800/1900 Cell)
CR3015

Channels (EDGE)
AR3025A
Mean Number of Available Channels

(EDGE) (900/850 Cell)
AR3025B

(EDGE) (1800/1900 Cell)
CR3025

(EDGE)
R3005A
Number of Initially Configured Channels

(Static EDGE) (900/850 Cell)
R3005B

(Static EDGE) (1800/1900 Cell)
R3006A

(Dynamic EDGE) (900/850 Cell)
R3006B

(Dynamic EDGE) (1800/1900 Cell)
CR3005

(Static EDGE)
CR3006

(Dynamic EDGE)
AL8351
Mean Number of Faulty Circuits on the Pb

Interface

20-25

20 EGPRS
20-26
Counter
Description
AL8353
Mean Number of Blocked Circuits on the Pb

Interface
AL8354
Mean Number of Idle Circuits on the Pb

Interface
AL8355
Mean Number of Busy Circuits on the Pb

Interface
AL8352
Mean Number of Circuits in Maintenance

State on the Pb Interface
L0387
Total Number of Messages Received from

PCU
L8387
Messages Received from a PCU
R3140
Requests for TCH from the PCU
R3141
Successful Requests for TCH from the PCU
AR3011A

Channels (PDCH) (900/850 Cell)
AR3011B

Channels (PDCH) (1800/1900 Cell)
CR3011

Channels (PDCH)
AR3021A

(PDCH) (900/850 Cell)
AR3021B

(PDCH) (1800/1900 Cell)
CR3021

(PDCH)
R3001A

(Static PDCH) (900/850 Cell)
R3001B

(Static PDCH) (1800/1900 Cell)
R3002A

(Dynamic PDCH) (900/850 Cell)
R3002B

(Dynamic PDCH) (1800/1900 Cell)
CR3001

(Static PDCH)
CR3002

(Dynamic PDCH)

Issue 03 (2009-06-08)

20 EGPRS
Counter
Description
ZTA331
Paging Requests on the Abis Interface per

BSC (PS Service)
ZTA301H
Immediate Assignment Commands per BSC

(PS Service)
ZTL3188D
PCH Overloads due to PS Service Counted

through the Indications from the Abis
Interface per BSC
20.8 References
The references indicate the documents about EDGE from the related standard organizations.
The references are as follows:
3GPP TS 50.059
"Enhanced Data rates for GSM Evolution (EDGE); Project scheduling and open issues for
EDGE"
Issue 03 (2009-06-08)

20-27

21 Co-BCCH Cell
21
Co-BCCH Cell
About This Chapter

21.1 Overview
This describes the definition and purposes of the Co-BCCH cell. The Co-BCCH cell adopts the
dual-band technique and features expanded cell capacity and minimized handover occurrences.
21.2 Availability
This lists the NEs, software, and hardware configuration of the BTS required for the
implementation of the Co-BCCH cell.
21.3 Impact
This describes the impact of the Co-BCCH cell on system performance.
This describes the implementation of channel assignment and handover.
21.5 Capabilities
None.
21.6 Implementation
This describes the configuration principle, configuration preparation, scenario analysis,
configuration procedure, and deactivation of the Co-BCCH cell.
This lists the performance counters related to the Co-BCCH cell.
21.8 References
Issue 03 (2009-06-08)

21-1

21 Co-BCCH Cell
21.1 Overview
This describes the definition and purposes of the Co-BCCH cell. The Co-BCCH cell adopts the
dual-band technique and features expanded cell capacity and minimized handover occurrences.
Definition
The Co-BCCH cell refers to a cell where the GSM900&DCS1800 TRXs coexist (or
GSM850&DCS1800, GSM850&PCS1900). The TRXs on the two bands use one main BCCH.
In a dual-band network, a dual-band MS can work on either of the bands. A single-band MS can
also work normally on its band.
The GSM900 band consists of the P-GSM, E-GSM, and R-GSM.
Purposes
The Co-BCCH cell improves the continuous coverage and sparse coverage in hot spots.
With the rapid increase of mobile users, the dual-band network solution becomes a growing
trend around the globe. The dual-band network has the following three networking modes:
l
Independent MSC Networking
Co-MSC Independent BSC Networking
Co-BSC Networking
The highlight of the dual-band network with the Co-BCCH cell is that the primary frequency
band and the secondary frequency band are the same and they coexist in one cell. The secondary
frequency band is the extension of the primary frequency band. This feature eliminates the
technical bottleneck on cell reselection and handover in other networking modes. Specifically,
the advantages of the dual-band network with the Co-BCCH cell are listed as follows:
l
The capacity of the cell is expanded and the occurrences of cell reselection for the MS are
reduced.
For example, a site is configured with a GSM900 cell and a DCS1800 cell. Each cell is
configured with two TRXs. You can obtain the data as listed in Table 21-1 when querying
the ERLANG B.
Table 21-1 Data in ERLANG B
21-2
Network
ing
Mode
Quantity
of
BCCHs
Quantity
of
SDCCHs
Quantity
of TCHs
Call Loss
Rate
Traffic Volume
Common
dual-band
network
28
2%
16.40 ERL
Dual-band
network
with CoBCCH
cell
29
2%
21.04 ERL

Issue 03 (2009-06-08)

21 Co-BCCH Cell
The inter-cell handover occurrences are reduced.

When an MS initiates a handover request, the MS is handed over to the channels on the
other frequency band in the serving cell.
The number of the BCCH TRXs is reduced and the interference caused by the BCCH TRXs
is reduced.
Convenient maintenance
The number of cells and neighboring cells of the Co-BCCH cell network is less than that
of the common dual-band network. Thus, the maintenance workload is reduced.
The system assigns channels on different frequency bands to the MS based on the RX level, RX
quality and TA value. The underlaid subcell is used for cell coverage and the overlaid subcell
is used for traffic absorption. Thus, the cell coverage is maximized and the capacity balance
between the overlaid subcell and the underlaid subcell is maintained.
Terms
Terms
Definition
M criteria
Indicates a criteria that selects only the neighbor cells of which the
RX level is higher than the lowest MS RX level threshold and sorts
the qualified cells in the candidate cell list. The serving cell and
neighbor cells are sorted based on the RX level.
ERLANG B
Indicates the relation among the number of common channels, call

loss rate, and traffic volume in busy hours. The ERLANG B is
developed from the ERLANG call loss formula.
Primary frequency
band
Indicates the frequency band containing the main BCCH frequency

in a Co-BCCH cell.
Secondary frequency
band
Indicates the frequency band that does not contain the main BCCH
frequency in a Co-BCCH cell.
Issue 03 (2009-06-08)
Full Spelling
BCCH
Broadcast Control Channel
SDCCH
Stand-alone Dedicated Control Channel
PBGT
Power Budget
BQ
Bad Quality
MR
Measurement Report
TA
Timing Advance

21-3

21 Co-BCCH Cell
21.2 Availability
This lists the NEs, software, and hardware configuration of the BTS required for the
implementation of the Co-BCCH cell.
NEs Involved
Table 21-2 lists the network elements involved in the Co-BCCH cell.
Table 21-2 NEs involved in Co-BCCH cell
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 21-3 lists the NEs and software versions that support Co-BCCH cell.
Product
Version
BSC
BSC6000
BTS
BTS3012
BTS3012
21-4
V900R008C01 and later releases

DTRU
BTS3000V100R001C01 and later releases
QTRU
DTRU
QTRU
BTS3006C
BTS3002E
DBS3900 GSM
BTS3900 GSM
BTS3900A GSM
BTS2X
All releases
BTS3001C
All releases
BTS3002C
All releases

Issue 03 (2009-06-08)

Product
21 Co-BCCH Cell
Version
BTS3X
All releases
Double-transceiver BTSs
All releases
Miscellaneous
The BTS must meet the following requirements if you configure Co-BCCH.
l
Number of TRXs
The number of GSM900 TRXs or DCS1800 TRXs should be less than or equal to four in
a Co-BCCH cell. If the number exceeds four, enough antenna output ports and antenna
models are required. The coverage of the TRXs on the same frequency band should be the
same in the case of antenna installation.
Antenna types and azimuth
If the GSM900 TRX and the DCS1800 TRX use the same antenna, the dual-band
antenna is required.
If the GSM900 TRX and the DCS1800 TRX use the antenna respectively, either the
dual-band antenna or the single-band antenna is allowed. When the sing-band antenna
is used, the azimuth of the antennas used for the GSM900 TRX and the DCS1800 TRX
in the same cell must be the same.
Type of the combiner

As a combiner cannot support the GSM900 and the DCS1800 at the same time, the GSM900
TRX and the DCS1800 TRX must use different combiners.
Combination mode
The combination mode of the TRXs on the same frequency band in a cell must be the same.
Otherwise, the TX power levels of the TRXs on the same frequency band in a cell are not
consistent, and the coverage of these TRXs is not consistent. Thus, the Co-BCCH cell
cannot be enabled because of a 3-layer or more-layer concentric cell.
21.3 Impact
This describes the impact of the Co-BCCH cell on system performance.

The impact of the Co-BCCH cell on system performance is as follows:
l
Co-BCCH cell can be applied to specific scenarios only. If Co-BCCH is applied to

unqualified scenarios, the network KPI is deteriorated.
For details of the application scenarios of the Co-BCCH, refer to 21.6.3 Risk Analysis of
the Configuration Scenarios.
The neighboring cell of the Co-BCCH cell is limited.

The neighboring cell of the Co-BCCH cell cannot be GSM900 cell or DCS1800 cell.
Otherwise, the traffic volume is unbalanced.
Issue 03 (2009-06-08)

21-5

21 Co-BCCH Cell
NOTE
If the GSM900 cell and the DCS1800 cell are at the same layer, they can be neighboring cell of the
Co-BCCH cell.
For details of network layer and network hierarchy, refer to 7.3.2.10 Fast-Moving Micro Cell
Handover.
l
The configuration of network optimization parameters of the Co-BCCH cell is more

difficult than that of the common cell.

The Co-BCCH cell and the double-timeslot cell cannot coexist.

This describes the implementation of channel assignment and handover.
21.4.1 GSM900/DSC1800 Co-BCCH Cell Channel Assignment

This describes the Co-BCCH cell channel assignment. Channel assignment strategy of the CoBCCH cell complies with the channel assignment algorithm of the concentric cell and is
associated with the frequency band supported by the MS.
The GSM900&DCS1800 (or GSM850&DCS1800, GSM850&PCS1900) Co-BCCH cell is
realized based on the principles of the concentric cell, which are described as follows:
l
GSM900 (or GSM850) TRXs are configured in the underlaid subcell for network coverage.
DCS1800 (or PCS1900) TRXs are configured in the overlaid subcell for traffic absorption.
Therefore, the channel assignment of the Co-BCCH cell should comply with the channel
assignment strategy of the concentric cell. Before the channel assignment, however, the network
needs to determine the frequency bands supported by the MS. If the MS supports the bands in
the underlaid and overlaid subcell, the channel assignment strategy of the concentric cell is
applied. Otherwise, the network assigns only the channels in the underlaid subcell to the MS.
Immediate Assignment
In the immediate assignment procedure, the BSC does not receive any information about the
MS. If TA exists, the BSC assigns underlaid or overlaid channels to the MS based on TA. The
BSC preferentially assigns the channels in the underlaid subcell to the MS to ensure that the
conversation can be established.
Assignment
In the assignment procedure, the channel assignment is related to MS classmark 3.
21-6
If the BSC does not obtain MS classmark 3, or if MS classmark 3 indicates that the MS
supports only the underlaid frequency band, then the BSC assigns only the underlaid
channels to the MS.
If MS classmark 3 indicates that the MS supports the underlaid and overlaid frequency
bands, the BSC assigns underlaid or overlaid channels to the MS based on Assign
Optimum Layer and Assign-optimum-level Threshold.
Issue 03 (2009-06-08)

21 Co-BCCH Cell
Incoming Internal Inter-Cell Handover

In the incoming internal inter-cell handover procedure, the channel assignment is related to MS
classmark 3.
l
channels to the MS.
bands, the BSC assigns underlaid or overlaid channels to the MS based on Pref. Subcell
in HO of Intra-BSC.
Because the inter-cell handover is generally triggered on the cell edge, you are advised to set
the Pref. Subcell in HO of Intra-BSC to Underlaid Subcell.
Incoming External Inter-Cell Handover

In the incoming external inter-cell handover procedure, the channel assignment is related to MS
classmark 3.
l
channels to the MS.
bands, the BSC assigns underlaid or overlaid channels to the MS based on Incoming-toBSC HO Optimum Layer.
Because the inter-cell handover is generally triggered on the cell edge, you are advised to set
the Incoming-to-BSC HO Optimum Layer to Underlaid Subcell.
21.4.2 GSM900/DCS1800 Co-BCCH Cell Handover

This describes the GSM900/DCS1800 Co-BCCH cell handover. The Co-BCCH cell handover
is based on the handover algorithm of the concentric cell.
Neighbor Cell Selection

Based on the M criteria, the actual RX level of the serving cell is used for the handover decision
and the RX level of the neighbor cells is used for neighbor cell queuing, no matter the MS is
located in the overlaid subcell or the underlaid subcell. When the MS is in the overlaid subcell,
the underlaid subcell is handled as a special neighbor cell.
Handover Within an Enhanced Concentric Cell

The underlaid subcell can provide better speech quality in a concentric cell. Therefore, the
utilization ratio of the underlaid subcell is maximized.
The underlaid-to-overlaid subcell handover occurs only when the traffic volume in the underlaid
cell is high, the RX level of the MS is high, the RX quality of the MS is good, and the TA value
is low. In other words, all the following conditions must be met:
l
DL RX Level UtoO HO Received Level Threshold

This condition is controlled by RX_LEV for UO HO Allowed.
Issue 03 (2009-06-08)
DL RX Quality < RX_QUAL Threshold

21-7

21 Co-BCCH Cell
This condition is controlled by RX_QUAL for UO HO Allowed.

l
TA < (TA Threshold TA Hysteresis)

This condition is controlled by TA for UO HO Allowed.
Traffic of the underlaid subcell > Tch Traffic Busy Underlay Threshold
This condition is controlled by Underlaid Subcell HO Step Period (s) and Underlaid
Subcell HO Step Level.
If the serving cell has the highest priority in the neighbor cell queue, the overlaid-to-underlaid
subcell handover occurs when the RX level of the MS, the RX quality of the MS, or the TA
deteriorates. In other words, one of the following conditions should be met:
l
DL RX Level < OtoU HO Received Level Threshold

This condition is controlled by RX_LEV for UO HO Allowed.
DL RX Quality RX_QUAL Threshold

This condition is controlled by RX_QUAL for UO HO Allowed.
TA (TA Threshold TA Hysteresis)

This condition is controlled by TA for UO HO Allowed.
If the serving cell does not have the highest priority in the neighbor cell queue, the MS is handed
over to another neighbor cell.
Inter-Subcell Handover
The actual RX level of the cell is used for all the handover decision algorithms except the PBGT
handover decision algorithm.
The PBGT algorithm calculates the path loss of the neighbor cell at the same layer and hierarchy
by using the RX level of the underlaid cell for handover decision. Because of fast fading of the
signal level transmitted by the DCS1800 TRXs in the overlaid subcell, the handover decision
based on the actual RX level in the overlaid subcell is improper when compared with the RX
level in a neighbor cell. To ensure the accuracy of the PBGT handover decision, the handover
decision should be based on the RX level in the underlaid subcell.
For the incoming inter-cell handover and the incoming-to-BSC handover in the Co-BCCH cell,
to avoid a low handover success rate due to inaccurate signal level of the target cell, set Pref.
Subcell in HO of Intra-BSC and Incoming-to-BSC HO Optimum Layer to Underlaid
Subcell.
21.5 Capabilities
None.
21.6 Implementation
This describes the configuration principle, configuration preparation, scenario analysis,
configuration procedure, and deactivation of the Co-BCCH cell.
21.6.1 Configuration Principles

This describes the configuration principles of the Co-BCCH cell.
21-8

Issue 03 (2009-06-08)

21 Co-BCCH Cell
A Co-BCCH cell consists of an overlaid subcell and an underlaid subcell. The specific band
configuration is as follows:
l
If the overlaid subcell is configured with the DCS1800 TRX, the underlaid subcell is
configured with the GSM900 or GSM850 TRX.
If the overlaid subcell is configured with the PCS1900 TRX, the underlaid subcell is
configured with the GSM850 TRX.
NOTE
The path loss of the DCS1800 TRX is fast. At the distance of 0.5 to 1 km, the signal power of the DCS1800
TRX is about 15 dB less than the signal power of the GSM900 TRX.
Configure the Co-BCCH cell based on the following principles:

l
Generally, do not assign the overlaid subcell channel to a call, do not assign the incoming
inter-cell handover request directly to the overlaid subcell, and do not forcibly assign a call
beyond coverage of the DCS1800 TRX to the overlaid subcell.
Properly assign the traffic volume in the underlaid subcell and the overlaid subcell to
maintain the traffic balance between the overlaid subcell and the underlaid subcell.
Configure the BCCH in the GSM900 TRX. The priority of the TRX types from high to low
is: P-GSM, E-GSM, and R-GSM.
Configure the SDCCH, PDCH, and BCCH in the same TRX.
The frequency hopping between the GSM900 frequencies and the DCS1800 frequencies
is not allowed. The frequency hopping between frequencies within the same frequency
band is allowed.
Prevent a multi-layer concentric cell due to inconsistent combination mode of the TRXs
on the same frequency band. A multi-layer concentric cell deteriorates the network KPI,
such as handover success rate and assignment success rate.
21.6.2 Preparations for the Configuration

This describes the preparations for configuring the Co-BCCH cell. You are required to be
familiar with the related information based on which the parameter configuration is performed.
Get familiar with the state of the current cell, which includes the following items:
l
User distribution and traffic volume in the coverage area of the site
Ratio of the coverage of the DCS1800/PCS1900 TRX to the coverage of the entire cell
Ratio of the coverage of the GSM900/GSM850 TRX to the coverage of the entire cell
Whether the GSM900/GSM850 TRXs can carry all the traffic in the cell.
Number of the GSM900/GSM850 TRXs and the DCS1800/PCS1900 TRXs. Whether the
frequency reuse on the GSM900/GSM850 band is tight and whether the interference exists.
Pay attention to the following restrictions on network planning:

l
Issue 03 (2009-06-08)
Number of TRXs
If the traffic is distributed mainly in the overlaid subcell and if the congestion is unlikely
to occur in the underlaid subcell, the number of TRXs configured in the underlaid subcell
can be small.
If the traffic volume in the underlaid subcell is high, the TRXs in the underlaid subcell
should outnumber or be equal to the TRXs in the overlaid subcell to prevent the
congestion in the underlaid subcell.
21-9

21 Co-BCCH Cell
If the TRXs in the underlaid subcell are not enough, the TRXs in a fully-loaded underlaid
subcell are likely to be congested in high traffic hours. This deteriorates the network
KPIs, such as TCH Seizure Success Rate and handover success ratio.
Neighbor cell
This factor is neglectable if the Co-BCCH cell is not adjacent to two or more singleband cells at the same time.
If the Co-BCCH cell is adjacent to two single-band cells using the two bands of the CoBCCH cell at the same time, you should consider the network hierarchy.
This factor is neglectable if the Co-BCCH cell has a low priority.
If the Co-BCCH cell is adjacent to two single-band cells using the two bands of the
Co-BCCH cell at the same time, you should consider the network hierarchy.
You should consider the traffic load of neighbor cells if the Co-BCCH cell has
a high priority. If the traffic load of neighbor cells is high, the traffic distributed
on edge of a common cell is absorbed by the Co-BCCH cell. Thus, the TRXs in
the underlaid subcell are likely to be congested and the network KPIs, such as
TCH Seizure Success Rate and handover success ratio are deteriorated. In this
case, the Co-BCCH cell is not recommended.
If the Co-BCCH cell has to be used, you should analyze the traffic distribution
based on the congestion conditions in the underlaid subcell and then adjust the
handover parameters of related cells. The purpose is to prevent the calls on edge
of a common cell from being handed over to the Co-BCCH cell.
21.6.3 Risk Analysis of the Configuration Scenarios

This describes the risk analysis of the configuration scenarios. The configuration scenarios
consist of common and special scenarios.
In the Co-BCCH cell, two types of TRXs with different coverage capabilities are configured.
Therefore, the traffic volume of the overlaid and underlaid subcells should be properly assigned
without deteriorating the network KPIs. The traffic assignment of the overlaid and underlaid
subcells is influenced by two factors. One is the number of TRXs in the overlaid and underlaid
subcells, and the other is the actual coverage of the overlaid and underlaid subcells (represented
by the inter-site distance).
Risk Analysis in Common Scenarios

Table 21-4 lists the risk analysis in common scenarios.
21-10

Issue 03 (2009-06-08)

21 Co-BCCH Cell
Table 21-4 Risk analysis in common scenarios
Issue 03 (2009-06-08)
N
o.
Scenario
Descriptio
n
Scenario Analysis
Risk
Solution
The intersite distance

is within
800 m.
The coverage capability of

the DCS1800 TRXs is
equivalent to that of the
GSM900 TRXs.
Therefore, the underlaidto-overlaid or overlaid-tounderlaid handover in the
Co-BCCH cell is unlikely
to fail.
There is no risk,
and the CoBCCH cell can
be enabled.
None
The intersite
distance
is from
800 m to
1,600 m.
The risk is
small, and the
Co-BCCH cell
can be enabled.
The
number
of TRXs
in the
underlaid
subcell is
equal to
or more
than the
number
of TRXs
in the
overlaid
subcell.
The overlaid subcell only

covers about half of the
coverage area of a CoBCCH cell. The underlaid
subcell configured with
enough TRXs can cover
the remaining area of a CoBCCH cell. Therefore, the
risk is low.
Assigns enough traffic

volume to the underlaid
subcell with
precondition that no
congestion occurs in
the underlaid subcell.
Thus, the risk of
underlaid-to-overlaid
handover in high traffic
hours is minimized.

Adjust UtoO HO
Received Level
Threshold to arrange
the traffic of the
overlaid and underlaid
subcells.
l
If the value of this

parameter is
reduced, the number
of underlaid subcell
to overlaid subcell
handovers increases.
If the value of this

parameter is
increased, the
number of underlaid
subcell to overlaid
subcell handovers
decreases.
21-11

21 Co-BCCH Cell
21-12
N
o.
Scenario
Descriptio
n
The intersite
distance
is from
800 m to
1,600 m.
The
number
of TRXs
in the
underlaid
subcell is
less than
the
number
of TRXs
in the
overlaid
subcell.
Scenario Analysis
Risk
Solution
The overlaid subcell only

covers about half of the
subcell with few TRXs
may not (or just be able to)
cover the remaining area
of a Co-BCCH cell.
Therefore, most of the
traffic is handed over to
the overlaid subcell in high
traffic hours. Possible
risks are as follows:
The risk is
medium, and
you are advised
not to enable the
Co-BCCH. If
you enable the
Co-BCCH, you
are advised to
enable halfrate
channels in the
underlaid
subcell or to add
underlaid
TRXs.
Enable the half-rate

services or increase the
TRXs in the underlaid
subcell.
Certain calls beyond the

coverage of the overlaid
subcell are likely to be
handed over to the
overlaid subcell and the
handover fails.
With the increase of cell

traffic, the underlaid
subcell becomes badly
congested while the
overlaid subcell
remains idle. In
addition, the
performance indicators,
such as the underlaidto-overlaid handover
success rate and the
DCS1800 channel
seizure success rate are
deteriorated.

Issue 03 (2009-06-08)

N
o.
Scenario
Descriptio
n
Issue 03 (2009-06-08)
The intersite
distance
is more
than
1,600 m.
The
number
of TRXs
in the
underlaid
subcell is
equal to
or more
than the
number
of TRXs
in the
overlaid
subcell.
21 Co-BCCH Cell
Scenario Analysis
Risk
Solution
The overlaid subcell

covers less than half of the
coverage area of a CoBCCH cell and the
underlaid subcell is
configured with enough
TRXs. Based on the
quantity and distribution
of users, either of the
following scenarios may
occur:
The risk is
medium.
None
Scenario 1
Most users are in the
overlaid subcell. The
TRXs of the underlaid
subcell can carry the
traffic in coverage of
the underlaid subcell. In
this situation, the
underlaid subcell
should carry most of the
traffic to reduce the risk
cause by the underlaidto-overlaid handover in
high traffic hours.
Scenario 2
Users are distributed
evenly and the
underlaid subcell TRXs
cannot (or just be able
to) carry the traffic in
the coverage area of the
underlaid subcell. Thus,
the underlaid subcell
becomes badly
congested and the
overlaid subcell
remains idle. In
addition, the
performance indicators,
such as the underlaidto-overlaid handover
DCS1800 channel
deteriorated.
For scenario
1, the CoBCCH can be
enabled.
For scenario
2, you are
advised not to
enable the
Co-BCCH. If
you enable
the CoBCCH, you
are advised to
enable
halfrate
channels in
the underlaid
subcell or to
add underlaid
TRXs.

21-13

21 Co-BCCH Cell
N
o.
Scenario
Descriptio
n
The intersite
distance
is more
than
1,600 m.
The
number
of TRXs
in the
underlaid
subcell is
less than
the
number
of TRXs
in the
overlaid
subcell.
Scenario Analysis
Risk
Solution

covers less than half of the
subcell with few TRXs
cannot (or just be able to)
carry the traffic in the
coverage of the underlaid
subcell. Possible risks are
as follows:
The risk is large,

and the CoBCCH cannot
be enabled.
Enable the half-rate

services or increase the
TRXs in the underlaid
subcell.
The underlaid subcell is

badly congested.

remains idle.
The underlaid-tooverlaid handover

DCS1800 channel
deteriorated.
The methods for determining the risks are as follows:

l
In a common dual-band network, if the congestion does not occur in the overlaid or
underlaid subcell, the related performance indicators have no change after the Co-BCCH
cell is enabled.
In a common dual-band network, if the congestion in the GSM900 subcell occurs at an

earlier time than in the DCS1800 subcell, a forcible traffic transfer from the GSM900
subcell to the DCS1800 subcell is likely to deteriorate the KPIs. In this case, related
performance indicators are deteriorated if the Co-BCCH cell is enabled. For example, the
underlaid-to-overlaid handover success rate and the DCS1800 channel seizure success rate
are reduced.
Risk Analysis in Special Scenarios

Use the following methods to eliminate problems which may occur when the Co-BCCH cell is
enabled in special scenarios:
l
The TRXs number in the overlaid and underlaid subcells is equivalent and most of the
traffic should be assigned in the overlaid subcell.
You can lower the value of UtoO HO Received Level Threshold to increase the traffic
in the overlaid subcell. To avoid ping-pong handovers because of signal level fluctuation,
the value of OtoU HO Received Level Threshold should be less than 25.
21-14
Severe interference exists in the GSM900 subcell.

Issue 03 (2009-06-08)

21 Co-BCCH Cell
You can suppress the interference to some extent by adjusting the parameters related to
concentric cell.
When the inter-site distance is less than 1,000 m, add the traffic in the overlaid subcell.
NOTE
You can determine that the GSM900 channel is seriously interfered if the interference band is high,
the RX quality is bad, and the call drop rate is 1.2 times or more than the call drop rate of the DSC1800
channel.
l
In a common dual-band network, only few cells are configured to be the Co-BCCH cells.
The neighbor cells are single-band or dual-band cells.
In a common dual-band network, the DCS1800 cell is at Level 2 and the GSM900 cell is
at level 3. That is, the DCS1800 cell level is higher than the GSM900 cell level. In this
situation, the following may occur when the Co-BCCH cell is enabled:
If the Co-BCCH cell is set to level 2, the traffic absorption capability of the GSM900
TRX becomes enhanced. The traffic of the neighbor cells is absorbed. Thus, the traffic
volume of the cell increases sharply and related performance indicators are deteriorated.
If the Co-BCCH cell is set to level 3, the traffic in the coverage of the DCS1800 TRX
is absorbed by the neighbor cells. The cell traffic volume is decreased.
To avoid these risks, you must enable the Co-BCCH cell in the neighbor sites.
21.6.4 Configuring the Co-BCCH Cell

This describes how to configure the Co-BCCH cell on the BSC6000 Local Maintenance
Terminal.
Procedure
Step 1 Add a Co-BCCH cell
1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target BTS and then choose Add Cell on the shortcut menu. The Add Cell dialog
box is displayed.
2.
Click Add Cell. A dialog box is displayed, as shown in Figure 21-1.

Figure 21-1 Add New Cell dialog box
Issue 03 (2009-06-08)

21-15

21 Co-BCCH Cell
NOTE
Figure 21-1 takes an example of external PCU. When the PCU is in built-in mode, there is no PCU
Name in Figure 21-1.
3.
In Figure 21-1, set Frequency Band to GSM900&DCS1800 or GSM850&DCS1800,

and then click OK. The Add Cell dialog box is returned.
NOTE
If you select GSM850&PCS1900, you must set High Frequency Band to PCS1900.
4.
Click Next. The Set Site Attributes dialog box is displayed.
5.
Select a site from the Site List, and then click Set Site Device to set related parameters.
NOTE
You must set Add Chain and Manual Abis according to transmission path and customer
requirements.
Step 2 Configure cell attributes

1.
21-16
Click Next. The Set Cell Attributes dialog box is displayed. Select cells from the Cells to
be set list box, and then click Set Cell Attributes. A dialog box is displayed, as shown in
Figure 21-2.

Issue 03 (2009-06-08)

21 Co-BCCH Cell
Figure 21-2 Set Cell Attributes dialog box
2.
Set BCCH IUO Attribute.
Step 3 Assign TRXs for the add cell

1.
Issue 03 (2009-06-08)
In the dialog box shown in Figure 21-2, click Frequency Config. A dialog box is displayed,
as shown in Figure 21-3.

21-17

21 Co-BCCH Cell
Figure 21-3 Set Cell Frequency dialog box
2.
Select the GSM900 frequencies and DCS1800 frequencies, and then click OK to return to
the dialog box shown in Figure 21-2.
Step 4 Set the attributes of the newly assigned TRXs

1.
In the dialog box shown in Figure 21-2, click TRX Config. A dialog box is displayed, as
shown in Figure 21-4.
Figure 21-4 Configure TRX Attributes dialog box (1)
21-18

Issue 03 (2009-06-08)

21 Co-BCCH Cell
2.
On the Frequency Attributes tab page, double-click a target frequency in Available

Frequencies to add the frequency to Assigned Frequencies.
3.
On the Device Attributes tab page, check Value of the HW_Concentric Attribute
parameter, as shown in Figure 21-5.
NOTE
The Value of the HW_Concentric Attribute cannot be set. Instead, it is determined by the value of
the BCCH IUO Attribute in Figure 21-2.
Figure 21-5 Configure TRX Attributes dialog box (2)
Step 5 Set ECSC

1.
Issue 03 (2009-06-08)
In the dialog box shown in Figure 21-2, click Call Control. A dialog box is displayed, as

21-19

21 Co-BCCH Cell
Figure 21-6 Set Call Control Parameter dialog box
2.
Specify ECSC based on the actual situations.

NOTE
If you set ECSC to No, the MS reports classmark 3 only when the MSC queries. Before the MSC
queries MS classmark 3, the MS is preferentially assigned to the channels on the GSM900 TRXs.
Thus, the traffic load in the underlaid subcell may be too high.
Step 6 Set the handover parameters

1.
21-20
Click Handover Data in the dialog box shown in Figure 21-2. A dialog box is displayed,

Issue 03 (2009-06-08)

21 Co-BCCH Cell
Figure 21-7 Set Handover Parameter dialog box (1)
2.
Select Enhanced Concentric Allowed.
3.
Click Advanced. A dialog box is displayed, as shown in Figure 21-8.
Issue 03 (2009-06-08)

21-21

21 Co-BCCH Cell
Figure 21-8 Set Handover Parameter dialog box (2)
4.
Set UtoO Traffic HO Allowed to Yes.

NOTE
UtoO Traffic HO Allowed is available only when Enhanced Concentric Allowed is set to Yes.
When Enhanced Concentric Allowed is set to Yes, the serving cell automatically becomes a
neighbor cell of itself and cannot be deleted. In the handover algorithm of the enhanced concentric
cell, the signal strength of the BCCH TRX is measured in the same way as the signal strength of the
neighbor cell. Therefore, the error caused by estimation of the signal strength of the BCCH TRX in
the handover algorithm of the common concentric cell can be eliminated.
Step 7 Set other parameters

1.
In the dialog box shown in Figure 21-8, set Pref. Subcell in HO of Intra-BSC and
Incoming-to-BSC HO Optimum Layer to Underlaid Subcell.
2.
Set Assign Optimum Layer, Assign-optimum-level Threshold, and TA Threshold of

Assignment Pref..
3.
Set Concentric Circles HO Allowed, UL to OL HO Allowed, and OL to UL HO

Allowed.
4.
Set TA for UO HO Allowed, RX_LEV for UO HO Allowed, and RX_QUAL for UO

HO Allowed.
----End
21.6.5 Deactivating the Co-BCCH Cell

This describes how to deactivate the Co-BCCH cell on the BSC6000 Local Maintenance
Terminal.
Prerequisite
To deactivate a non Co-BCCH cell, you need to delete the cell and then add a cell according to
the actual command.
21-22

Issue 03 (2009-06-08)

21 Co-BCCH Cell
Procedure
Step 1 Delete the existing cell.
1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target cell and then choose Delete Cell from the shortcut menu. The Delete Cell
dialog box is displayed.
2.
In the Delete Cell dialog box, double-click the target cell in the Cell view area to add the
cell to the Cells to be deleted area.
3.
Click Finish. The deletion is complete.
Step 2 Add a new cell and complete the cell configuration.

----End

This lists the performance counters related to the Co-BCCH cell.
Alarms
None
Counters
Table 21-5 lists the performance counters related to the Co-BCCH cell.
Table 21-5 Counters related to the Co-BCCH cell
Issue 03 (2009-06-08)
Counter
Description
AS330A
Mean Uplink Receive Level during

Concentric Cell Handover Initiation (Overlay
to Underlay)
AS332A
Mean Downlink Receive Level during

Concentric Cell Handover Initiation (Overlay
to Underlay)
AS330B
Mean Uplink Receive Level during

Concentric Cell Handover Initiation
(Underlay to Overlay)
AS332B
Mean Downlink Receive Level during

Concentric Cell Handover Initiation
AS334A
Mean Timing Advance during Concentric

Cell Handover Initiation (Overlay to
Underlay)
AS334B
Mean Timing Advance during Concentric

Cell Handover Initiation (Underlay to
Overlay)
21-23

21 Co-BCCH Cell
21-24
Counter
Description
H3001
Internal Intra-Cell Handover Requests

(Overlay to Underlay)
H3002
Internal Intra-Cell Handover Requests

H3012
Internal Intra-Cell Handover Commands

H3011
Internal Intra-Cell Handover Commands

H3022A
Failed Internal Intra-Cell Handovers

(Channel Unavailable) (Underlay to Overlay)
H3021A
Failed Internal Intra-Cell Handovers

(Channel Unavailable) (Overlay to Underlay)
H3022M
Failed Internal Intra-Cell Handovers (Other

Causes) (Underlay to Overlay)
H3021M
Failed Internal Intra-Cell Handovers (Other

Causes) (Overlay to Underlay)
TH3032
Success Rate of Internal Intra-Cell Handover

(Underlaid Subcell to Overlaid Subcell)
TH3031
Success Rate of Internal Intra-Cell Handover

S3012
MRs on Signaling Channels (Underlaid

Subcell)
S3011
MRs on Signaling Channels (Overlaid

Subcell)
S3002
MRs on TCHs (Underlaid Subcell)
S3001
MRs on TCHs (Overlaid Subcell)
CR3557
Traffic Volume of TCHs (Underlaid Subcell)
CR3558
Traffic Volume of TCHs (Overlaid Subcell)
R3200
Channel Assignment Requests (Underlaid

Subcell Only)
R3201
Channel Assignment Requests (Overlaid

Subcell Only)
R3202
Channel Assignment Requests (Underlaid

Subcell Preferred)
R3203
Channel Assignment Requests (Overlaid

Subcell Preferred)

Issue 03 (2009-06-08)

Issue 03 (2009-06-08)
21 Co-BCCH Cell
Counter
Description
R3202B
TCH Assignment Requests (Underlaid

Subcell Preferred)
R3203B
TCH Assignment Requests (Overlaid Subcell

Preferred)
R3202D
Channel Assignment Requests in Incoming

Internal Inter-Cell Handover Procedure
(TCH)(Underlaid Subcell Preferred)
R3203D

(TCH) (Overlaid Subcell Preferred)
R3202E

External Inter-Cell Handover Procedure
(TCH) (Underlaid Subcell Preferred)
R3203E

R3222B
Channel Assignment Overflows (TCH)

(Underlaid Subcell Preferred)
R3223B
Channel Assignment Overflows (TCH)

(Overlaid Subcell Preferred)
R3222D
Channel Assignment Overflows in Incoming

R3223D

R3222E

R3223E

R3225J
Channel Assignment Overflows in Underlaid

Subcell (TCH)
R3224J
Channel Assignment Overflows in Overlaid

Subcell (TCH)
R3225G

Subcell (SDCCH)
R3224G

Subcell (SDCCH)

21-25

21 Co-BCCH Cell
Counter
Description
R3225H

Subcell (TCHF)
R3224H

Subcell (TCHF)
R3225I

Subcell (TCHH)
R3224I

Subcell (TCHH)
R3224K
Failed Handovers from Underlaid Subcell to

Overlaid Subcell due to Busy Channels in
Overlaid Subcell
R3225K
Failed Handovers from Overlaid Subcell to

Underlaid Subcell due to Busy Channels in
Underlaid Subcell
21.8 References
l
GSM 08.08:
"Mobile Switching Centre - Base Station system (MSC-BSS) Interface Layer 3
Specification"
GSM 04.08
"Mobile Radio Interface - Layer 3 Specification"
21-26

Issue 03 (2009-06-08)

22
22 Satellite Transmission
Satellite Transmission
About This Chapter

22.1 Overview
This describes the application of satellite transmission, which is mainly adopted in remote
mountainous areas or sparsely populated plains.
22.2 Availability
This lists the NEs and software required for the implementation of satellite transmission.
22.3 Impact
The describes the impact of satellite transmission on system performance and other features.
This describes the network topologies of satellite transmission and the application of satellite
transmission over the Abis interface. Huawei BSS supports the satellite transmission over the
Ater, A, Abis, Pb interface, and Gb interfaces.
22.5 Implementation
This describes how to configure satellite transmission on the Ater, A, Abis, and Pb interfaces.
None.
22.7 References
None.
Issue 03 (2009-06-08)

22-1

22.1 Overview
This describes the application of satellite transmission, which is mainly adopted in remote
mountainous areas or sparsely populated plains.
Definition
Satellite transmission enables different entities to communicate with each other by using the
satellites orbiting the earth.
Compared with traditional terrestrial transmission, satellite transmission encounters the
problems such as delay, jitter, and bit error.
Huawei BSS eliminates the delay, jitter, and bit error problems over satellite transmission
through the optimization of signaling procedures and the adjustment of relevant timers. Huawei
BSS supports the satellite transmission over the A, Ater, Abis, Pb, and Gb interfaces.
Purposes
The satellite transmission features wide coverage, long transmission distance, and flexible link
scheduling. This enables satellite transmission to be used beyond geographical difference and
transmission distance. Satellite transmission is widely used in remote mountainous areas or
sparsely populated plains.
Terms
None

Acronyms and
Abbreviations
Full Spelling
BC
Bear Channel
DCE
Data Circuit-Terminating Equipment
DTE
Data Terminal Equipment
VSAT
Very Satellite Communications Terminal
22.2 Availability
This lists the NEs and software required for the implementation of satellite transmission.
NEs Involved
Table 22-1 describes the NEs involved in satellite transmission.
22-2

Issue 03 (2009-06-08)

Table 22-1 NEs involved in satellite transmission

MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 22-2 describes the versions of GBSS products that support satellite transmission.
Product
Version
BSC
BSC6000
BTS
BTS3012
BTS3012A
E

DTRU
QTRU
DTRU
QTRU
BTS3006C
BTS3002E
DBS3900 GSM
BTS3900 GSM
BTS3900A GSM
BTS30
All releases
BTS312
All releases
BTS3012A
All releases
BTS3001C
All releases
BTS3002C
All releases
Miscellaneous
None
Issue 03 (2009-06-08)

22-3

22.3 Impact
The describes the impact of satellite transmission on system performance and other features.

The delay involved in satellite transmission may affect the counters such as call drop rate,
handover success rate, and assignment success rate.

Call drops occur when the forward link and reverse link in the Huawei BTS ring topology
are switched over.

This describes the network topologies of satellite transmission and the application of satellite
transmission over the Abis interface. Huawei BSS supports the satellite transmission over the
Ater, A, Abis, Pb interface, and Gb interfaces.
22.4.1 Network Topologies of Satellite Transmission

This topic describes the networking of the satellite transmission over the Abis interface.
Star topology is generally adopted when the satellite transmission is implemented over the Abis
interface. Figure 22-1 shows a typical networking of satellite transmission.
NOTE
The principle of satellite transmission over Abis, Ater, Pb, and Gb interfaces is the same as that over the
Abis interface.
Figure 22-1 Typical networking of satellite transmission
Satellite
ground station
MSC
BSC
BTS
SDH/PDH or
microwave/
optical cables
22-4
E1
Ground
receiving station
E1
Ground
receiving station
BTS
BTS
BTS

Issue 03 (2009-06-08)

The satellite communication is composed of the communication satellites and ground stations.
The communications satellite is usually a geosynchronous satellite, which orbits the equator.
The satellite orbits at a distance of 35786 km from the earth and has an angular orbital velocity
equal to the earth orbital velocity. The satellite is composed of the control system,
communication system (antennas and repeaters), telemeter system, power supply system, and
temperature control system.
The Earth station is composed of the antenna system, transceiver, channel terminal (modem),
communication control system, and power supply system.
l
The earth station generally used for satellite transmission is a large international or
European standard communication station, which features high data rate, large aperture,
and high cost. User data is transferred to the Earth stations for communication, through the
terrestrial network.
Using the VSAT-based system to build up a private network causes lower cost, smaller
aperture, and flexible deployment.
22.4.2 Satellite Transmission on the Abis Interface

This describes the satellite transmission over the Abis interface. Satellite transmission has a
higher transmission delay than the terrestrial transmission. Huawei BSS is developed with
multiple optimization mechanisms to avoid abnormal procedures caused by prolonged delay.
Immediate Assignment Opt.

The immediate assignment procedure involves the following steps:
1.
The BSC sends a Channel Activation message to the BTS.
2.
The BTS responds with a Channel Activation Acknowledgement message.
3.
The BSC sends an Immediate Assignment Command message to the MS.

NOTE
In the terrestrial transmission, the interval between the Channel Activation message and the Channel
Activation Acknowledgement is short. In the satellite transmission, however, the MS takes a longer time
to receive the Immediate Assignment Command message from the BSS. The optimized immediate
assignment procedure is adopted in the satellite transmission to avoid prolonged call proceeding and
immediate assignment failure due to transmission delay.
After sending a Channel Activation message to the BTS, the BSC proceeds to send an Immediate
Assignment Command message to the MS without waiting for the Channel Activation
Acknowledgement message from the BTS.
Impact of System Information

To avoid the transmission delay and improve the access success rate of the MS in satellite
transmission, performs the following settings:
l
Add the times for the MS to send the Channel Request message. The default value of MS
MAX Retrans is 4, and you can set the value of it according to actual commands.
Increase the interval between two transmissions by setting Tx-integer to 50.
Issue 03 (2009-06-08)

22-5

Processing of LAPD Protocols

Prolong the length of timers and increase the value of the sliding window while processing LAPD
protocols to overcome the impact of transmission delay.
Operating Mode of the BTS Clock

The BTS clock is subject to the BSC clock. If the satellite equipment fails to keep clock
synchronization, you can select the internal clock as the clock reference. The internal clock
extracted from the BSS also meets the requirements specified in GSM protocols.
Voice Quality
The voice quality is not affected when the bit error rate is less than 110-6. Generally, the bit
error rate in satellite transmission is less than 110-8.
22.4.3 Satellite Transmission on the Pb Interface

The link layer on the Pb interface adopts LAPD link protocols. The processing on the LAPD
link is the same as that on the Abis interface.
22.4.4 Satellite Transmission on the Gb Interface

This describes the satellite transmission on the Gb interface. Because E1 transmission on the Gb
interface is unavailable in some countries and regions, the BSC supports satellite as a relay for
transmission on the Gb interface.
FR is used on the Gb interface as bearer protocol. The FR link on the Gb interface of the Huawei
BSS can support 600 ms delay carried with satellite transmission.
When you configure satellite transmission on the Gb interface, ensure that the following
parameters involved in the FR link on the Gb interface meet the requirement of delay:
l
DTE Parameter (N391)
DTE Parameter (T391)
The value of T391 must be greater than three times of satellite transmission delay.
The mode of Bear Channel (BC) is determined by networking:
l
If the PCU is directly connected to the SGSN, set the PCU to Data Terminal Equipment
(DTE) and the SGSN to Data Circuit-Terminating Equipment (DCE).
If the PCU is connected to the SGSN through an intermediate network, set the PCU to DTE,
intermediate network to DCE, and SGSN to either DTE or DCE.
When IP transmission mode is used on the Gb interface, the default settings can support the 600
ms delay carried with satellite transmission.
NOTE
The timers are set to default values.
22-6

Issue 03 (2009-06-08)

22.5 Implementation
This describes how to configure satellite transmission on the Ater, A, Abis, and Pb interfaces.
22.5.1 Configuring Satellite Transmission on the Ater Interface

This describes how to configure satellite transmission on the Ater interface on the BSC6000
Local Maintenance Terminal.
Prerequisite
The Ater connection path is configured for the GEIUT/GOIUT in the GMPS.
Context
When the GTCS is remotely configured, the signaling transmission, service transmission, and
GTCS OM are required. Therefore, you are advised not to configure satellite transmission on
the Ater interface when the GTCS is remotely configured.
To enable the normal processing of PS services in the satellite transmission mode, the PS cell
GPRS parameters T3168 must be set to 2000ms, T3192 to 0ms, BS_CV_MAX to 15.
Procedure
Step 1 On the BSC Device Panel tab page of the BSC6000 Local Maintenance Terminal, right-click
a GEIUT/GOIUT, and then choose Configure Ater Connection Path. A dialog box is
displayed.
Step 2 Click Add. A dialog box is displayed, as shown in Figure 22-2.
Figure 22-2 Add Ater Connection Path dialog box
Issue 03 (2009-06-08)

22-7

Step 3 Set the parameters related to the Ater connection path, and click OK. The addition of an Ater
connection path is complete.
a GEIUT/GOIUT, and then choose Add Ater Signaling Link. A dialog box is displayed.
Figure 22-3 Add Ater Signaling Link dialog box
Step 6 Set Transmission Mode to Satellite Transmission.

Step 7 Set corresponding Timeslot No. as shown in Figure 22-4. Only one timeslot No. can be
configured.
22-8

Issue 03 (2009-06-08)

Figure 22-4 Configuring timeslot
Step 8 Click OK. The upper-level dialog box is displayed.

Step 9 Click Finish to complete the configuration of satellite transmission on the Ater interface.
----End
22.5.2 Configuring Satellite Transmission on the A Interface

This describes how to configure satellite transmission on the A interface on the BSC6000 Local
Maintenance Terminal.
Prerequisite
The E1 is configured for the GEIUA/GOIUA in the GTCS.
Context
Procedure
a GEIUA/GOIUA, and then choose Configure A Interface E1/T1. A dialog box is displayed.
Issue 03 (2009-06-08)

22-9

Figure 22-5 Adding A interface E1/T1
Step 3 Set relevant parameters on the A Interface E1/T1 Attributes tab page, and then click OK. The
addition of an E1 to the A interface is complete.
a GEIUA/GOIUA in the GTCS, and then choose Configure SS7 Signaling Link. A dialog box
is displayed.
22-10

Issue 03 (2009-06-08)

Figure 22-6 Adding an SS7 signaling link
Step 6 Select the MTP2 tab, and then set parameters, as shown in Figure 22-7.
CAUTION
The signaling link with the Rate Type of 64 kbit/s can be configured with only one E1 timeslot.
Issue 03 (2009-06-08)

22-11

Figure 22-7 Configuring timeslot
Step 7 Select the MTP3 tab, set SLC, SLC Send, and Satellite Flag, as shown in Figure 22-8.
22-12

Issue 03 (2009-06-08)

Figure 22-8 Configuring MTP3 parameters
NOTE
Meanings of the Satellite Flag values: Yes indicates that satellite transmission is supported, and No
indicates that the terrestrial transmission is supported.
The settings of SLC and SLC send must be the same between the BSC and the MSC.

Step 9 Click Finish to complete the configuration of satellite transmission on the A interface.
----End
22.5.3 Configuring Satellite Transmission on the Abis Interface

This describes how to configure satellite transmission on the Abis interface on the BSC6000
Prerequisite
Apply for a license and activate the license.
1.
Issue 03 (2009-06-08)
To apply for the license for the satellite transmission on Abis interface, in the
BSC6000V900R008 Exceptional Commercial License Application Template, you should
fill in the number of the sites that support satellite transmission in the Number of sites
supporting satellite transmission column in the License control items column.
22-13

2.
Activate the license on the Local Maintenance Terminal. For details, see Activating the
BSC License.
After the licenses are activated, the BSC can support satellite transmission over the Abis interface
based on the number of applied licenses. By default, the satellite transmission over Abis
interface is closed. You can perform certain data configuration on the BSC6000 Local
Maintenance Terminal to open the satellite transmission on Abis interface.
NOTE
The license strategy applies only to the Abis interface. The other interfaces can support satellite
transmission once they are correctly configured.
Context
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click
a BTS that needs to be configured with satellite transmission data, and then choose Site
Operation > Configure Site Attributes on the shortcut menu.
Step 2 Click Set Site Attributes. A dialog box is displayed, as shown in Figure 22-9.
Figure 22-9 Configuring site attributes (1)
22-14

Issue 03 (2009-06-08)

Step 3 Select the Basic Information tab, and then set Transmission Mode to Satellite
Transmission and Clock Type to Internal Clock.
Step 5 Click Finish to complete the basic configuration of satellite transmission on the Abis interface.
NOTE
The transmission modes on the Abis interface are as follows:

l
In terrestrial transmission, the information transferred between the BTS and the BSC is carried by the
land bearing network.
In satellite transmission, the information transferred between the BTS and the BSC is carried by the
satellite communications equipment.
Step 6 Improve cell performance

1.
Set RSL Lapd Link Window Size

a.
On the BSC6000 Local Maintenance Terminal, right-click a BTS on the

Management Tree tab page. Then, choose BTS Operation > Configure BTS
Attributes from the shortcut menu. The Configure Site Attributes dialog box is
displayed.
b.
In the displayed dialog box, select Configure Cell Attributes. A dialog box is
displayed, as shown in Figure 22-10.
Figure 22-10 Site Attributes
Issue 03 (2009-06-08)

22-15

c.
Select the OML Setting tab, and then set RSL Lapd Link Window Size to 48.
NOTE
This parameter is bound to the parameter Transmission Mode. That is, the value of this parameter
automatically matches that of the transmission mode.
2.
Set SDCCH Dynamic Allocation Allowed

a.
On the Management Tree tab page of the BSC6000 Local Maintenance

Terminal, right-click the target cell, and then choose Configure Cell Attributes from
the shortcut menu. A dialog box is displayed. Select cells, and then click Next.
b.
In the displayed dialog box, click Configure Cell Attributes. A dialog box is
22-16

Issue 03 (2009-06-08)

c.
3.
Select SDCCH Dynamic Allocation Allowed.
Set MS MAX Retrans.

a.
4.
The default value of the MS MAX Retrans is 4. You can change the value according
to actual commands.
Set Tx-integer.
a.

b.
c.
In the Advanced Attributes area, click Idle Mode. A dialog box is displayed, as
Figure 22-12 Set Idle Parameter dialog box (1)
d.
5.
Issue 03 (2009-06-08)
Set Tx-integer to 50.
Set the timer.

a.

b.
c.
In the Advanced Attributes area, select Call Control.
d.

22-17

Figure 22-13 Configuring Call Control Parameters
e.
Set T200 SDCCH(5ms) to 200, T200 SACCH SDCCH(10ms) to 100, and T200
SDCCH SAPI3(5ms) to 200.
NOTE
Huawei recommends that the value of T200 SDCCH(5ms) is equal to or greater than 840 ms
(168 ms expressed in 5 ms on the BSC6000 Local Maintenance Terminal) when satellite
transmission is enabled.
The satellite transmission delay is 270 ms on average with different intermediate transmission.
----End
22.5.4 Configuring Satellite Transmission on the Pb Interface

This describes how to configure satellite transmission on the Pb interface on the BSC6000 Local
Maintenance Terminal or PCU LocalWS.
Context
Procedure
l
22-18
Configure satellite transmission on the Pb interface on the BSC6000 Local Maintenance

Terminal.
1.
On the BSC Device Panel tab page of the BSC6000 Local Maintenance
Terminal, right-click GEIUP/GOIUP in the GEPS, and then choose Configure Pb
Interface E1/T1. A dialog box is displayed.
2.
Click Add. A dialog box is displayed, as shown in Figure 22-14.

Issue 03 (2009-06-08)

Figure 22-14 Adding Pb interface E1/T1
3.
Select the Pb Interface E1/T1 Attributes tab, and then set the Transmission
Mode to Satellite Transmission.
NOTE
The Start PCIC must be the multiple of 128. The configuration of the parameters on the CIC
Attributes tab page is not necessary.
4.
Click OK. The upper-level dialog box is displayed.
5.
Click Finish to complete the configuration of satellite transmission over the Pb

interface.
NOTE
Pb signaling links can be carried by terrestrial transmission or satellite transmission scheme.

The satellite transmission scheme can be adopted in deserts or lakes where the terrestrial
transmission is unavailable.
After the Pb E1 ports are configured with satellite transmission scheme, the Pb signaling
links can automatically switch to satellite transmission mode based on the transmission
mode adopted on the E1 ports.
Configure satellite transmission on the Pb interface on the PCU LocalWS.

1.
Run the mt gcell deactive<LCNo> command to deactivate a cell.
2.
Run the pcu add sattrans<LCNo>yes command to configure satellite transmission

for the cell.
3.
Run the mt gcell active <LCNo> command to activate the cell.
----End
22.5.5 Configuring Satellite Transmission on the Gb Interface

This describes how to configure satellite transmission on the Gb interface on the BSC6000 Local
Issue 03 (2009-06-08)

22-19

Context
Parameter DTE Parameter (T391) is involved in satellite transmission on the Gb interface. The
default value of the parameter is 10 S, which can support the delay caused by satellite
transmission. DTE Parameter (N391), DTE Parameter (N392), and DTE Parameter
(N393) are set to default values.
Procedure
GFGUG/GFPUG, and then choose Configure BC.
Step 2 Modify DTE parameters on the displayed dialog box.
----End

None.
Alarms
None.
Counter
None.
22.7 References
None.
22-20

Issue 03 (2009-06-08)

23 TRX Cooperation
23
TRX Cooperation
About This Chapter

23.1 Overview
This describes the BCCH TRX cooperation. When a BCCH TRX of a cell is unavailable, the
BSC specifies another available TRX in the cell to replace the original BCCH TRX. This
describes the TRX cooperation. When faults occur on the TRXs in a cell, the TRX cooperation
ensures that the cell is functional.
23.2 Availability
This lists the NEs and software required for the implementation of TRX cooperation.
23.3 Impact
This describes the impact of TRX cooperation on system performance and on other features.
This describes the principles of the BCCH TRX cooperation, baseband FH TRX cooperation,
and the TRX cooperation algorithm.
23.5 Implementation
This describes how to configure the TRX cooperation.
This lists the alarms and performance counters related to TRX cooperation.
23.7 References
None.
Issue 03 (2009-06-08)

23-1

23 TRX Cooperation
23.1 Overview
BSC specifies another available TRX in the cell to replace the original BCCH TRX. This
describes the TRX cooperation. When faults occur on the TRXs in a cell, the TRX cooperation
ensures that the cell is functional.
Definition
When some TRXs in a cell fail, the cell may be not functional. When faults occur on the TRXs
in a cell, the TRX cooperation ensures that the cell is functional.
The TRX cooperation is categorized into the following modes:
l
BCCH TRX Cooperation

When a BCCH TRX fails, the BSC selects a normal TRX as the new BCCH TRX according
to the TRX cooperation algorithm to ensure that the cell is functional. When the fault of
the original BCCH TRX is rectified, the BSC can switch the BCCH back to the original
TRX.
Description of the Baseband FH TRX Cooperation

When a TRX of the cell in Baseband FH mode is faulty, the BSC changes the mode to be
None FH to avoid decrease in the voice quality.
Purposes
When a BCCH TRX of a cell fails, all the services in this cell are interrupted. To ensure the
normal running of the cell services, the BSC initiates another TRX in the cell to replace the
faulty TRX.
When the TRX of a cell in baseband FH mode fails, some speech frames in the call using the
FH channel are lost. Thus, the voice quality is decreased. To ensure the voice quality in the cell,
the BSC enables the baseband FH TRX cooperation and changes the mode to none FH. Then,
faults of few TRXs do not affect the voice quality in the entire cell. After the faults are rectified,
the BSC can revert the FH mode of the cell to baseband FH.
NOTE
During the period in which the service is interrupted due to TRX failure and then the service is resumed
after TRX cooperation, the system determines whether the TRX cooperation is required, performs cell
service handover, and cell re-initialization.
The TRX cooperation is not triggered within a certain period after the cell is initialized. The period is
determined by the Aiding Delay Protect Time(min). By default, the value is 15 minutes.
Terms
23-2
Terms
Definition
Original main BCCH

TRX
Indicates the main BCCH TRX configured on the BSC6000 Local

Maintenance Terminal by the user in the cell.

Issue 03 (2009-06-08)

23 TRX Cooperation
Terms
Definition
Cooperated TRX
In TRX cooperation, the cooperated TRX is an available TRX

selected through the TRX cooperation algorithm to replace the
original main BCCH TRX. The selected TRX is the new BCCH
TRX of the cell.
Current main BCCH

TRX
Indicates the working BCCH TRX after TRX cooperation.
Task per second
Indicates the task that is performed each second in the system.
Acronym and Abbreviation

Acronym and
Abbreviation
Full Spelling
BCCH
Broadcast Control CHannel
TCH
Traffic Channel
SDCCH
PDCH
Packet Data Channel
CBCH
Cell Broadcast CHannel
23.2 Availability
This lists the NEs and software required for the implementation of TRX cooperation.
NEs Involved
Table 23-1 lists the network elements involved in TRX cooperation.
Table 23-1 NEs involved in TRX cooperation
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l : not involved
l : involved
Software Releases
Table 23-2 describes the versions supported by the GBSS NEs involved in TRX cooperation.
Issue 03 (2009-06-08)

23-3

23 TRX Cooperation

Product
Version
BSC
BSC6000
BTS
BTS3012
BTS3012A
E

DTRU
QTRU
DTRU
QTRU
BTS3006C
BTS3002E
DBS3900 GSM
BTS3900 GSM
BTS3900A GSM
BTS30
All releases
BTS312
All releases
BTS3012A
All releases
BTS3001C
All releases
BTS3002C
All releases
23.3 Impact
This describes the impact of TRX cooperation on system performance and on other features.

The impacts of the BCCH TRX cooperation on system performance are as follows:
l
After the BCCH TRX cooperation, the BSC specifies a normal non-BCCH TRX as the
BCCH TRX; therefore, the number of available TCHs decreases and the cell capacity is
reduced. The greater the number of faulty TRXs , the lower the cell capacity.
If a PDCH TRX is involved in the BCCH TRX cooperation, the PDCH is unavailable and
the packet service capacity is deceased after the BCCH TRX cooperation; if a CBCH TRX
is involved in the BCCH TRX cooperation, the CBCH is unavailable and the cell broadcast
service is terminated after the BCCH TRX cooperation.
If either of the original main BCCH TRX or the cooperated TRX does not support the
EDGE, neither of them supports the EDGE after the BCCH TRX cooperation.
If the cell is a concentric cell and the cooperated TRX is in an overlaid subcell, the coverage
of the cell decreases after the TRX cooperation.
The impacts of the baseband FH TRX cooperation on system performance are as follows:
23-4

Issue 03 (2009-06-08)

23 TRX Cooperation
In the baseband FH TRX cooperation, the BSC changes the FH mode from Baseband
FH to None FH. The cell cannot implement the functions of interference diversity and antiattenuation.
When the baseband FH mode of the cell is Baseband FH Joined By The TRX Carrying
the Primary BCCH and when the BCCH TRX of the cell fails, both the BCCH TRX
cooperation and the baseband FH TRX cooperation are performed. That is, the BSC
changes the FH mode of the cell to None FH. After all faults on the original primary BCCH
TRX and the TRX involved in the FH are rectified, the BSC reverts to FH mode to
Baseband FH.

The impacts of the TRX cooperation on other features are as follows:
l
The TRX cooperation is not performed during the validity period of the configured and
modified data, resource check, and BTS initialization.
If the SDCCH dynamic adjustment, full-rate/half-rate dynamic adjustment, or PDCH

dynamic adjustment occurs in the cell, the types of the dynamically adjusted channels
carried by the TRXs involved in the TRX cooperation are reverted to be the initial types
after the TRX cooperation or TRX cooperation switchback.

This describes the principles of the BCCH TRX cooperation, baseband FH TRX cooperation,
and the TRX cooperation algorithm.
23.4.1 BCCH TRX Cooperation

BSC specifies another available TRX in the cell to replace the original BCCH TRX, thus ensuring
that the cell is functional. When the fault of the original BCCH TRX is rectified, the BSC can
switch the BCCH back to the original TRX.
The BCCH TRX cooperation involves the following:
l
Recovery of the original BCCH TRX

The BCCH TRX cooperation is triggered by the required status change message reported from
the BTS.
The requirements of the BCCH TRX cooperation are as follows:
l
The object in the message must be of the channel level and must be the main BCCH.
NOTE
If the BCCH TRX cooperation occurs, the object in the message must be the main BCCH after the
TRX cooperation.
l
The status of the main BCCH is DISABLED.
The availability status of the main BCCH must be one of those listed in Table 23-3.
Issue 03 (2009-06-08)

23-5

23 TRX Cooperation
Table 23-3 Availability status and meaning

Availability Status
Meaning
POWER_OFF
Indicates that the equipment is powered off.
FAILED
Indicates that the equipment fails.
NOT_INSTALLED_REAL
Indicates that the equipment is not installed.
DEPENDENCY
Indicates that the equipment is unavailable because

of other faulty equipment.
The cell number in the BCCH TRX cooperation message is used to identify the cell where the
BCCH TRX cooperation is performed. The BCCH TRX cooperation of different cells can be
performed concurrently.
The process of the BCCH TRX cooperation is as follows:
1.
When a cell meets the requirements for the BCCH TRX cooperation, the BSC starts a
protection timer with the duration as one minute.
NOTE
The protection timer with the duration of one minute can avoid the TRX cooperation caused by
unstable TRX status.
2.
After the protection timer times out, the BSC checks whether the cell meets the
requirements for the TRX cooperation again.
l
If the cell meets the requirements, the BSC sends requests to all the calls in the cell for
force handover and starts a 10-second timer.
If the cell does not meet the requirements, the BSC terminates the process of TRX
cooperation.
3.
After all the calls in the cell are handed over or the 10-second timer times out, the BSC
selects an available TRX in the cell to replace the original BCCH TRX.
4.
The BSC initializes the cell and delivers the configuration data to the BTS. In addition, the
BSC delivers the configuration data of the original BCCH TRX to the cooperated TRX and
delivers the configuration data of the cooperated TRX to the original BCCH TRX. The
cooperated TRX thus can provide services of the original BCCH TRX.
Recovery of the Original BCCH TRX

After the BCCH TRX cooperation, if the fault on the original BCCH TRX in the cell is rectified,
recovery of the original BCCH TRX is performed. The configuration data of the two TRXs
involved in the TRX cooperation is adjusted, and the initial configuration data of the cell is
restored.
The process of the original BCCH TRX recovery is reverse to that of the BCCH TRX
cooperation. The differences between them are the triggering conditions and processing. The
time to perform the original BCCH TRX recovery is controlled by TRX Aiding Function
Control, which can be set to TRX Aiding Not Allowed, Allowed & Recover Immediately,
or Allowed Recover When Check Res.
The recovery of the original BCCH TRX is triggered by the required status change message
reported from the BTS. In addition, the status of the original BCCH is DISABLED.
23-6

Issue 03 (2009-06-08)

23 TRX Cooperation
The cell number in the BCCH TRX recovery message is used to identify the cell where the
recovery of the original BCCH TRX is performed. The recovery of the original BCCH TRX of
different cells can be performed concurrently.
When a cell meets the requirements for the original BCCH TRX recovery, the process of the
original BCCH TRX recovery is similar to that of the BCCH TRX cooperation. Finally, you
need to restore the initial configuration data before the TRX cooperation according to certain
mapping rules.
23.4.2 Description of the Baseband FH TRX Cooperation

This describes the baseband FH TRX cooperation. In a cell with the FH mode as Baseband
FH, when a TRX involved in the FH fails, the BSC initiates the baseband FH TRX cooperation
and changes the FH mode of the cell to None FH. After the TRX faults are rectified, the BSC
reverts the FH mode to Baseband FH.
The baseband FH TRX cooperation involves the following:
l
Recovery of the original baseband FH TRX

The baseband FH TRX cooperation can be performed in only the baseband FH cell, and is
triggered by the required status change message reported from the BTS.
The requirements for the baseband FH TRX cooperation are as follows:
l
The object in the message must be of the BT level and must be the TRX involved in the
baseband FH.
The TRX is in DISABLED status.
The availability status of the TRX must be one of those listed in Table 23-4.
Table 23-4 Availability status and meaning
Availability Status
Meaning
POWER_OFF
Indicates that the equipment is powered off.
FAILED
Indicates that the equipment fails.
NOT_INSTALLED_REAL
Indicates that the equipment is not installed.
DEPENDENCY
Indicates that the equipment is unavailable because

of other faulty equipment.
The cell number in the baseband FH TRX cooperation message is used to identify the cell where
the baseband FH TRX cooperation is performed. The baseband FH TRX cooperation of different
cells can be performed concurrently.
The process of the baseband FH TRX cooperation is as follows:
1.
Issue 03 (2009-06-08)
When a cell meets the requirements for the baseband FH TRX cooperation, the BSC starts
a protection timer with the duration as one minute.
23-7

23 TRX Cooperation
NOTE
The protection timer with the duration of one minute can avoid the TRX cooperation caused by
unstable TRX status.
2.
After the protection timer times out, the BSC checks whether the cell meets the
requirements for the TRX cooperation again.
l
If the cell meets the requirements, the BSC sends requests to all the calls in the cell for
force handover and starts a 10-second timer.
If the cell does not meet the requirements, the BSC terminates the process of TRX
cooperation.
3.
After all the calls in the cell are handed over or the 10-second timer times out, the BSC
changes the FH mode of the cell from Baseband FH to None FH.
4.
The BSC initializes the cell, delivers new configuration data to the BTS, and changes the
FH mode of the cell from Baseband FH to None FH.
Recovery of the Original Baseband FH TRX

When the faults of the baseband FH TRX in the cell are rectified, the BSC reverts the FH
mode of the cell to Baseband FH. The time to perform the original BCCH TRX recovery is
controlled by TRX Aiding Function Control, which can be set to TRX Aiding Not
Allowed, Allowed & Recover Immediately, or Allowed Recover When Check Res.
The process of the original baseband FH TRX is reverse to that of the baseband FH TRX
cooperation. The differences between them are the triggering conditions and processing.
The recovery of the original baseband FH TRX can be performed in only the baseband FH cell,
and is triggered by the required status change message reported from the BTS. The object in the
message must be of the BT level and must be the TRX involved in the baseband FH. The status
of the original baseband FH TRX must be ENABLED.
The cell number in the baseband FH TRX recovery message is used to identify the cell where
the recovery of the original baseband FH TRX is performed. The recovery of the original
baseband FH TRX can be performed concurrently in different cells.
23.4.3 TRX Cooperation Algorithm

This describes the algorithm adopted by the BSC to select the cooperated TRX in the TRX
cooperation.
TRX cooperation is performed between the following three status:
l
Default status
Preprocessing status
Post-processing status
In the TRX cooperation, the BSC takes the following protection measures to ensure the
communication quality of the radio network.
l
Preprocessing protection
Avoids the frequent TRX cooperation caused by the TRX intermittence.
Post-processing protection
Provides sufficient time for the calls in the cell where the TRX cooperation is performed.
23-8

Issue 03 (2009-06-08)

23 TRX Cooperation
23.4.3.1 Checking the Availability Status of Cells

This describes how to check the availability status of a cell to determine whether the cell meets
the requirements for the TRX cooperation.
The cell status check is triggered by the task per second. The 512 cells are checked cyclically.
In the cell status check, the BSC ignores the cell in the abnormal state and finds the cell meeting
the requirements for the TRX cooperation.
The cells in the abnormal state are as follows:
l
The cell is not installed.

AIDING_EXPT_CELL_NOT_INSTALL
The cell is not in the working state.

AIDING_EXPT_IN_INITIAL_PROCESS
The OML of the cell is disconnected.

AIDING_EXPT_OML_ABNORMAL
The dynamic adjustment is not allowed.

AIDING_EXPT_DATA_ADJUST_DISABLE
The TRX cooperation is not in the default state.

AIDING_EXPT_NOT_AIDING_BUTT
The cell is initialized for less than 15 minutes.

AIDING_EXPT_INITIAL_PROTECT
After the BSC finds the normal cell, the TRX cooperation process is started.
23.4.3.2 Checking the TRX Status

This describes how to check the TRX status to specify the type of TRX cooperation in a cell.
Conditions of the BCCH TRX Cooperation and Recovery of the Original BCCH
TRX
The BCCH TRX cooperation and the recovery of the original BCCH TRX can be performed
only when certain conditions are satisfied. Table 23-5 shows the conditions of the BCCH TRX
cooperation and recovery of the original BCCH TRX.
Table 23-5 Conditions of the BCCH TRX cooperation and recovery of the original BCCH TRX
Issue 03 (2009-06-08)
Conditions of the BCCH TRX

Cooperation
Conditions of the Recovery of the

Original BCCH TRX
The TRX Aiding Function Control Switch

in the cell is enabled.
The TRX Aiding Function Control

Switch in the cell is enabled.
The status of the current BCCH is

DISABLED.
The current BCCH TRX is not the one in the

initial configuration.

23-9

23 TRX Cooperation
Conditions of the BCCH TRX

Cooperation

Original BCCH TRX
The availability status of the BCCH can be

POWER_OFF, FAILED,
NOT_INSTALLED_REAL, or
DEPENDENCY.
The status of the BCCH in the initial

configuration is ENABLED.
Conditions of the Baseband FH TRX Cooperation and Recovery of the Original

Baseband FH TRX
The baseband FH TRX cooperation and the recovery of the original baseband FH TRX can be
performed only when certain conditions are satisfied. Table 23-6 shows the conditions of the
baseband FH TRX cooperation and recovery of the original baseband FH TRX.
Table 23-6 Conditions of the baseband FH TRX cooperation and recovery of the original
baseband FH TRX
Conditions of the Baseband FH TRX
Cooperation

Original Baseband FH TRX
The TRX Aiding Function Control

Switch in the cell is enabled.
The TRX Aiding Function Control Switch

in the cell is enabled.
The FH mode of the cell is Baseband FH.
The BSC changes the FH mode of the cell

from Baseband FH to None FH.
The baseband FH TRX cooperation is not

performed in this cell. That is, all the TRXs
involved in the baseband FH are normal.
The status of the original BCCH is

DISABLED.
The availability status of at least one TRX

involved in the baseband FH is
POWER_OFF, FAILED,
NOT_INSTALLED_REA, or
DEPENDENCY.
The status of all the TRXs involved in the

baseband FH is ENABLED.
NOTE
When the BCCH TRX cooperation is performed in the cell where the baseband FH occurs, the BSC initiates
the baseband FH TRX cooperation forcibly and changes the FH mode of the cell from Baseband FH to
None FH.
After the TRX status check is complete:

l
If the BSC detects that the TRX cooperation is not required, the TRX cooperation is quitted.
If the BSC detects that the conditions of the TRX cooperation are satisfied, the BSC starts
the preprocessing timer. The duration of the timer is one minute.
When the timer for the processing before the TRX cooperation expires, the BSC starts the
processing before the TRX cooperation.
23-10

Issue 03 (2009-06-08)

23 TRX Cooperation
The BSC then checks the TRX status again to avoid frequent TRX cooperation caused by TRX
intermittence. If the BCCH TRX cooperation is required, the BSC starts to search for the
cooperated TRX.
23.4.3.3 Preprocessing the TRX Cooperation

This describes the processing before the TRX cooperation. The processing before the TRX
cooperation involves searching for the cooperated TRX and processing after the TRX
cooperation.
Searching for the Cooperated TRX

Before starting the BCCH TRX cooperation, the BSC must select a normal TRX in the cell as
the candidate cooperated TRX. In the selection, configuration of the TRX should be considered.
The following TRXs cannot be selected as the candidate cooperated TRX:
l
TRX where the current BCCH is located
TRX that is in a different DTMU from the original BCCH TRX (The BCCH TRX
cooperation cannot be performed across cabinet groups.)
TRX in the DISABLED state
TRX that cannot exchange frequencies with the original BCCH TRX (The TRX, the CDU
and PBU to which the TRX belongs do not support the frequencies of the original BCCH.)
TRX involved in the RF FH in the cavity combiner
TRX that is in a different cavity combiner from that of the original BCCH TRX, and whose
frequency spacing is less than 3 after the frequency exchange.
The BSC puts all the available TRXs in the cell into the candidate TRX queue, and then ranks
them according to priorities. The TRX with the highest priority is selected as the candidate
cooperated BCCH TRX.
The principle for accessing the priorities is as follows: Each TRX is assigned with a byte.
Initially, the byte is set to OxFF. Each bit represents whether the related function is supported.
When the certain condition is satisfied, the bit is set to 0. After the assessment of the priorities,
the smaller the value, the higher the priority. Figure 23-1 lists the principles for assessing the
priority of the candidate TRX.
Figure 23-1 Principles for assessing the priority of the candidate TRX
bit7
bit6
bit5
bit4
bit3
bit2
bit1
bit0
No PDCH
No CBCH
Reserved
Issue 03 (2009-06-08)
Underlaid
subcell
TRX
Consistent
transmit and
receive modes
Consistent
mode of
supporting
EDGE

23-11

23 TRX Cooperation
Table 23-7 lists the meanings of parameters in assessing the priority of the candidate TRX.
Table 23-7 Parameters in assessing the priority of the candidate TRX
Bit
Meaning
bit0
bit0=0: The candidate TRX is not configured with the PDCH.
bit1
bit1=0: The candidate TRX is not configured with the CBCH.
bit2
Bit2=0: The transmit and receive mode of the candidate TRX is the same as that
of the original main BCCH TRX.
NOTE
The transmit and receive mode is a concept in the BTS3012. The RF transmit modes
supported by the DTRU of the BTS3012 include transmit independence, Power Boost
Technology (PBT), wideband combination, and transmit diversity; the receive modes
supported by the DTRU of the BTS3012 include independent receive, receive diversity,
and four-way receive diversity. The transmit and receive mode of other types of BTSs is
OxFF.
bit3
bit3=0: If the original main BCCH TRX supports the EDGE, the candidate TRX
also supports the EDGE; if the original main BCCH TRX does not support the
EDGE, the candidate TRX does not support the EDGE.
bit4
bit4=0: The candidate TRX is in the underlaid subcell.

If the cell is a concentric cell, the main BCCH TRX is generally in the underlaid
subcell and has a wide coverage. If the main BCCH TRX fails, the coverage of
the cell decreases.
bit5
Reserved.
bit6
bit7
In the TRX cooperation, the cell needs to be initialized. The calls in the current cell must be
handed over to other cells in order not to affect the voice quality. After the processing before
the TRX cooperation, the BSC starts a time for processing after the TRX cooperation with the
duration of 10 seconds to ensure sufficient time for the handover of all calls in the cell.
Processing After the TRX Cooperation

When the timer for the processing after the TRX cooperation times out, the BSC starts the
processing after the TRX cooperation.
The processing after the TRX cooperation includes the following:
1.
Modifying the dynamic variables

The BSC records the numbers of the cooperated TRX, the original BCCH TRX, and the
current BCCH TRX. The cooperated TRX is mapped to the original BCCH TRX, and the
initial configuration of the current BCCH TRX is restored. When the cell is initialized, the
BSC delivers configuration information to the each TRX according to the mapping rules.
23-12

Issue 03 (2009-06-08)

2.
23 TRX Cooperation
Sending alarms
The alarms include 401 BCCH Mutual Aid in a Cell, 402 Switchback after BCCH Mutual
Aid in a Cell, 409 Cell BCCH Aiding to IUO_INN TRX, 403 Baseband FH Mutual Aid in
a Cell, and 404 Switchback after Baseband FH Mutual Aid in a Cell.
3.
Requesting the initialization of the cell

The cell needs to be initialized in both the BCCH TRX cooperation and the baseband FH
TRX cooperation. In the cell initialization of the BCCH TRX cooperation, the configuration
of the original BCCH TRX and that of the cooperated TRX are exchanged except the
attributes of whether the AMR is supported and the RF receive mode and not exchanged.
23.5 Implementation
This describes how to configure the TRX cooperation.
23.5.1 Configuring TRX Cooperation

This topic describes how to configure TRXs on the BSC6000 Local Maintenance Terminal.
Context
The TRX cooperation switch is at the cell level. That is, each cell can independently choose to
enable or disable the TRX cooperation.
Procedure
the cell to be configured with the TRX cooperation and choose Configure Cell Attributes from
the shortcut menu.
Step 2 In the displayed dialog box, double-click the cell to be configured with the TRX cooperation in
the Cell view list box to add the cell to the Selected cells list box. Then, click Next.
Step 3 In the Cells to be set area, select the cell to be configured with the TRX cooperation, and then
click Set Cell Properties. A dialog box is displayed, as shown in Figure 23-2.
Issue 03 (2009-06-08)

23-13

23 TRX Cooperation
Step 4 In the Advanced Attributes area, click Call Control.

Step 5 In the displayed dialog box, click Advanced. A dialog box is displayed, as shown in Figure
23-3.
23-14

Issue 03 (2009-06-08)

23 TRX Cooperation
Figure 23-3 Setting advanced call control parameters
Step 6 In Figure 23-3, select the Call Control tab, and then set the TRX Aiding Function Control to
TRX Aiding Not Allowed, Allowed & Recover Immediately, or Allowed Recover When
Check Res.
NOTE
The default value of TRX Aiding Function Control is Allowed Recover When Check Res; therefore,
by default, the TRX cooperation of each cell is enabled.
Step 7 Click OK to return to the dialog box shown in Figure 23-2.

Step 8 Click OK to save the settings of the parameters.
----End

This lists the alarms and performance counters related to TRX cooperation.
Alarms
Table 23-8 lists the alarms related to TRX cooperation.
Table 23-8 Alarms related to TRX cooperation
Issue 03 (2009-06-08)
Alarm ID
Alarm Name
401
BCCH Mutual Aid in a Cell
402
Switchback after BCCH Mutual Aid in a Cell
403
Baseband FH Mutual Aid in a Cell

23-15

23 TRX Cooperation
Alarm ID
Alarm Name
404
Switchback after Baseband FH Mutual Aid in a Cell
409
Cell BCCH Aiding to IUO_INN TRX
Counters
Table 23-9 lists the counters related to TRX cooperation.
Table 23-9 Counters related to TRX cooperation
Counter
Description
R3710
Cell BCCH Mutual Aids
R3711
Recoveries after Cell BCCH Mutual Aids
R3720
Cell Baseband Hopping Mutual Aids
R3721
Recoveries after Cell Baseband Hopping Mutual Aids
23.7 References
None.
23-16

Issue 03 (2009-06-08)

24
24 High-Speed Signaling
High-Speed Signaling
About This Chapter

24.1 Overview
This describes the definition and purposes of applying No.7 signaling links. The No.7 signaling
links with different data rates can be applied according to the signaling load.
24.2 Availability
This lists the NEs and software required for the implementation of high-speed signaling links.
24.3 Impact
This describes the impact of high-speed signaling links on system performance.
The implementation of the 2 Mbit/s signaling link in the BSC is achieved by several boards.
Also, the implementation of the 2 Mbit/s signal link and its functions differ with those of the 64
kbit/s signaling link.
24.5 Capabilities
This describes the capabilities of the high-speed signaling links.
24.6 Implementation
This describes how to configure, verify, and disable high-speed signaling links.
This lists the alarms and counters related to high-speed signaling links.
24.8 References
Issue 03 (2009-06-08)

24-1

24.1 Overview
This describes the definition and purposes of applying No.7 signaling links. The No.7 signaling
links with different data rates can be applied according to the signaling load.
Definition
Two types of signaling links are available in the SS7 network: 64 kbit/s signaling link and 2
Mbit/s signaling link.
The 2 Mbit/s signaling link, also called high-speed signaling link, is the No.7 link in the SS7
network with a data rate of N x 64 kbit/s (1 N < 32). N indicates the number of timeslots
occupied by the high-speed signaling link.
The BSC uses the high-speed signaling links when the signaling load of the system is high. The
high-speed signaling link has the following features:
l
A high-speed signaling link occupies multiple 64 kbit/s timeslots with a data rate of N x
64 kbit/s (1 N < 32).
The electrical features of the high-speed signaling link port comply with the ITU-T G.703
protocol and its frame structure complies with the ITU-T G.704 protocol.
NOTE
The naming of the 2 Mbit/s high speed signaling link is specified by the ITU protocols. In actual situations,
the maximum data rate of the high-speed signaling link is 1,984 kbit/s.
Purposes
The BSC uses the high-speed signaling links when the 64 kbit/s signaling links fail to meet the
signaling requirements on the A interface due to high traffic volume.
The high speed signaling links are used in the following scenarios:
l
Some timeslots over a port are used to transmit speech information and the other timeslots
are used to transmit signaling information.
A telecom operator chooses high-speed signaling links with different data rates based on
the load of the signaling links.
Terms
24-2
Terms
Definition
Signaling link
No.7 signaling link, used to connect the signaling

points in the SS7 network and to transmit signaling
information
2 Mbit/s signaling link
High-speed signaling link with a data rate of N x

64 kbit/s (1 N < 32)
64 kbit/s signaling link
Signaling link with a data rate of 64 kbit/s

Issue 03 (2009-06-08)


Acronyms and
Abbreviations
Full Spelling
BSN
Backward Sequence Number
FSN
Forward Sequence Number
LI
Length Indicator
SLC
Signaling Link Code
24.2 Availability
This lists the NEs and software required for the implementation of high-speed signaling links.
NEs Involved
Table 24-1 lists the NEs involved in high-speed signaling links.
Table 24-1 NEs involved in high-speed signaling links
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l : not involved
l : involved
Software Releases
Table 24-2 lists the versions of GBSS products that support high-speed signaling links.
Product
BSC
Version
BSC6000
Miscellaneous
None.
24.3 Impact
This describes the impact of high-speed signaling links on system performance.
Issue 03 (2009-06-08)

24-3


Compared with the 64 kbit/s signaling link, the 2 Mbit/s signaling link is configured with more
timeslots; thus, the signaling transmission capacity of the 2 Mbit/s signaling link is greatly
enhanced.
NOTE
Generally, high-speed signaling links are used for terrestrial transmission instead of for satellite
transmission.
Compatibility tests must be performed when the high-speed signaling equipment from different
manufacturers are used in the same network.

None.

The implementation of the 2 Mbit/s signaling link in the BSC is achieved by several boards.
Also, the implementation of the 2 Mbit/s signal link and its functions differ with those of the 64
kbit/s signaling link.
24.4.1 Implementation
This describes the implementation of the 2 Mbit/s signaling links, which are achieved by the
GXPUM, GSCU, and GEIUA.
Processing of No.7 Signaling in the BSC

The No.7 signaling is processed differently for the BSC subracks configured in different modes.
l
Figure 24-1 shows the processing of the No.7 signaling in BM/TC separated mode.
Figure 24-2 shows the processing of the No.7 signaling in BM/TC combined mode.
Figure 24-1 Sigaling link on the A interface (BM/TC separated)
1.
24-4
In the GMPS/GEPS, the GXPUM processes the signaling based on the MTP3, SCCP, and
BSSAP protocols. Then, the GSCU transmits the processed signaling to the GEIUT/GOIUT
in the same subrack.
Issue 03 (2009-06-08)

2.
The GEIUT in the GMPS/GEPS processes the received signaling based on the MTP2
protocol, and then transmits the signaling to the GEIUT in the GTCS through the Ater
interface.
3.
In the GTCS, the GTNU performs timeslot-based TDM switching of the signaling, and
then transmits the signaling to the GEIUA/GOIUA.
4.
The signaling is transmitted to the MSC over the A interface.
Figure 24-2 Signaling link on the A interface (BM/TC combined)
1.
In the GMPS/GEPS, the GXPUM/GXPUT processes the signaling based on the MTP3,
SCCP, and BSSAP protocols. Then, the GSCU transmits the processed signaling to the
GEIUT/GOIUA in the same subrack.
2.
The GEIUA/GOIUA processes the signaling based on the MTP2 protocol, and then
transmits the signaling to the MSC.
Configuration Principles
The configuration principles are as follows:
l
Do not allocate timeslot 0 to the 2 Mbit/s signaling link.
The timeslots allocated to a 2 Mbit/s signaling link can be discontinuous.
When you allocate N (1 N < 32) 64 kbit/s timeslots to a 2 Mbit/s signaling link, Huawei
recommends that N ranges from 8 to 25.
The high-speed signaling link and 64 kbit/s signaling link cannot be applied in one BSC.
The bandwidth of each 2 Mbit/s signaling link might vary. However, you are advised to
apply the same bandwidth for the 2 Mbit/s signaling links as they share the traffic load
during the operation. Each high-speed signaling link can occupy the randomly combined
timeslots except timeslot 0.
The signaling links in the GSM telecommunications system are very important, and thus
the reliability of the 2 Mbit/s signaling links must be taken into account. In actual situations,
Huawei recommends that at least two signaling links are available in the same signaling
point, and that the two signaling links use different E1 or STM-1.
Determine the signaling mode used between the BSC and MSC before configuring the
signaling links in the BSC.
Configure the 2 Mbit/s signaling links in the BSC if eight or more 64 kbit/s signaling links
are required, considering the signaling transfer capacity between the BSC and MSC.
Issue 03 (2009-06-08)

24-5

l
The TS number of the timeslots allocated for a 2 Mbit/s signaling link must be the same
between the BSC and the MSC. Configure the E1 port number based on the connection of
the E1 cable.
The BSC6000 supports the MSC POOL feature, which means that one BSC can be
connected to multiple MSCs, MSC Servers, or MGWs. In this case, you need to configure
the No.7 signaling links according to the proportion of the A interface circuits (CIC)
between the BSC and the MSCs (MSC Servers or MGWs) to the total A interface circuits
(CIC).
Configuration in BM/TC separated mode:

l
Each 2 Mbit/s signaling link can be configured only in one E1 port of the GEIUT.
Multiple 2 Mbit/s signaling links can be configured in one E1 port of the GEIUT and occupy
different timeslots over the E1 port.
If the 2 Mbit/s signaling links in the GEIUT are removed, you need to reset the GEIUT
before configuring the 64 kbit/s signaling links.
If the 64 kbit/s signaling links in the GEIUT are removed, you need to reset the GEIUT
before configuring the 2 Mbit/s signaling links.
A maximum of eight 2 Mbit/s signaling links can be configured in one GEIUT.
If the 2 Mbit/s signaling links is configured in the BSC, the MTP3 link management entity of
the BSC continuously attempts to establish signaling links. Once the signaling links are
successfully established, the signaling messages can be transmitted.
24.4.2 Comparison Between 2 Mbit/s Signaling Link and 64 kbit/s

Signaling Link
This compares the 2 Mbit/s signaling link with the 64 kbit/s signaling link in terms of
implementation and functions.
Implementation
The implementation differences between the 2 Mbit/s signaling link and the 64 kbit/s signaling
link are classified into the following types:
l
24-6
Format of signaling messages
The BSN and FSN in the 64 kbit/s signaling link are 7 bits in length. The BSN and FSN
in the 2 Mbit/s signaling link are 12 bits in length, ranging from 0 to 4095. Figure
24-3 shows the formats of the signal units in the 2 Mbit/s signaling link.
The LI in the 64 kbit/s signaling link is 6 bits in length. The LI in the 2 Mbit/s signaling
link is 9 bits in length, ranging from 0 to 511. The 9-bit LI can indicate the 272-octet
information field supported by the MTP.

Issue 03 (2009-06-08)

Figure 24-3 Formats of the signal units in the 2 Mbit/s signaling link
F
CK
16
SIF
SIO
Spare
LI
F
I Res
B
FSN
B
I
B
Res
BSN
8n, n 2
12
12
First bit transmitted
(a) Basic format of a Message Signal Unit (MSU)
CK
16
SF
Spare
LI
8 or 16
F
I Res
B
FSN
B
I
B
Res
BSN
12
12
BSN
12
(b) Format of a Link Status Signal Unit (LSSU)
Spare
LI
F
I Res
B
FSN
B
I
B
CK
Res
1 3
12
1
7
9
16
3
(c) Format of a Fill-In Signal Unit (FISU)

T1178370-96
Error correction methods
The 2 Mbit/s signaling link adopts the basic error correction method. This method
detects the error signal units by defining the time segments with flags.
The 64 kbit/s signal links adopts the preventive cyclic retransmission method.
The sequence-related messages such as COO and COA are different in format.
The basic buffer capacity in error correction is as follows:
The retransmission buffer area at the sending end of the 2 Mbit/s signaling link is 4095
in length, greater than that of the 64 kbit/s signaling link.
The buffer area at the receiving end of the 2 Mbit/s signaling link is greater than that of
the 64 kbit/s signaling link.
Functions
l
Delimitation and alignment of signal units

The flag code can be used to delimit a signal unit. The bit pattern for the flag code is
01111110. The zero insertion method is applied to ensure that the pattern cannot be imitated
elsewhere in the unit. Loss of alignment occurs when a bit pattern disallowed by the
delimitation procedure (more than six consecutive 1 s) is received, or when the allowed
length of the signal unit is exceeded.
Acceptance procedure
Upon detection of an error signal unit, the acceptance procedure defines the time segment
with a flag and starts a counter, which is incremented every time a signal unit error is
detected. If the counter exceeds the threshold, the signaling link is defined as invalid.
Error detection
The error detection function is performed by means of 16 check bits provided at the end of
each signal unit.
Error correction
The 2 Mbit/s signaling link adopts the basic error correction method, a noncompelled
method in which the positive/negative acknowledgements and the retransmission
Issue 03 (2009-06-08)

24-7

mechanisms are used to ensure correct transfer of message signal units. Before the positive
acknowledgements are received, the transmitted signal units are stored in the transmitting
sequence. This mechanism enables that the transmitted but not yet positively acknowledged
signal units remain available for retransmission before new signal units are transmitted.
l
Initial alignment
Initial alignment applies to the activation and restoration of a signaling link.
Error monitoring
Error monitoring is performed when a signaling link is either in the error time segments or
in the proving state of the initial alignment procedure.
Flow Control
Upon detection of congestion at the receiving end of the signaling link, the flow control
mechanism is activated at the receiving end. A certain status indication of the signaling
link is sent to the transmitting end, informing the transmitting end to stop transmitting the
signal units already acknowledged.
If the congestion is abated, acknowledgements of input signal units are resumed by the
signaling link.
If the congestion persists, the receiving end periodically sends a link status signal unit
to the transmitting end of the signaling link.
If the congestion period exceeds a predefined threshold, the transmitting end recognizes
a signaling link failure and exits the services.
24.5 Capabilities
This describes the capabilities of the high-speed signaling links.
The capabilities of the high-speed signaling links are as follows:
l
One 2 Mbit/s signaling link can be configured with 1 to 31 timeslots.
One BSC subrack can be configured with up to eight 2 Mbit/s signaling links.
One BSC subrack must be configured with only one type of signaling links such as 2 Mbit/
s signaling link or 64 kbit/s signaling link.
24.6 Implementation
This describes how to configure, verify, and disable high-speed signaling links.
24.6.1 Configuring High-Speed Signaling Links

This describes how to configure a 2 Mbit/s signaling link on the BSC6000 Local Maintenance
Terminal.
Procedure
Step 1 Right-click a GEIUA on the BSC Device Panel of the BSC6000 Local Maintenance
Terminal and choose Configure SS7 Signaling Link from the shortcut menu. A dialog box is
24-8

Issue 03 (2009-06-08)

Figure 24-4 Configuring an SS7 signaling link
Step 2 Click Add. A dialog box is displayed, as shown in Figure 24-5. On the MTP2 tab page, set
Rate Type to 2Mbit/s, and select the timeslots for A Timeslot Mask and Ater Timeslot
Mask.
Issue 03 (2009-06-08)

24-9

Figure 24-5 Adding an SS7 signaling link (MTP2)
NOTE
In BM/TC separated mode when the GTCS is configured remotely, you are advised to configure the SS7
signaling link on the main GTCS. Also, TS1 should not be selected in Ater Timeslot Mask.
Step 3 On the MTP3 tab page as shown in Figure 24-6, set SLC and SLC Send.
24-10

Issue 03 (2009-06-08)

Figure 24-6 Adding an SS7 signaling link (MTP3)

Step 5 Click Finish to complete the configuration of the SS7 signaling link.
----End
24.6.2 Verifying High-Speed Signaling Links

This describes how to verify high-speed signaling links on the BSC6000 Local Maintenance
Terminal and Local Maintenance Terminal.
Procedure
l
Through GUI
1.
On the BSC6000 Local Maintenance Terminal, select the BSC Attributes tab page.
2.
In the Other Data area, click A Signaling Link. A dialog box is displayed, as shown
in Figure 24-7.
You can view and query the status of the high-speed signaling link on the Figure
24-7.
Issue 03 (2009-06-08)

24-11

Figure 24-7 Viewing SS7 signaling links
3.
On the menu of the BSC6000 Local Maintenance Terminal, choose BSC

Maintenance > Maintain Transmission and Signaling > Maintain MTP3 Link.
In the displayed dialog box, click Query to query the status of the No.7 signaling
links.
Through MML
1.
On the Local Maintenance Terminal, enter the command LST N7LNK.

NOTE
The parameters highlighted in red must be set.
2.
Set parameters.
3.
Run the command and the operation is complete.
----End
24.6.3 Disabling High-Speed Signaling links

This describes how to remove the 2 Mbit/s signaling links on the BSC6000 Local Maintenance
Terminal and Local Maintenance Terminal.
24-12

Issue 03 (2009-06-08)

Procedure
l
Through GUI
1.
Right-click a GEIUA on the BSC Device Panel of the BSC6000 Local Maintenance
Terminal and choose Configure SS7 Signaling Link from the shortcut menu. A
Figure 24-8 Removing SS7 signaling links
2.
Select the SS7 signaling link to be removed in Figure 24-8, and click Delete.
3.
Click Finish to complete the removing of the SS7 signaling link.
Through MML
1.
On the Local Maintenance Terminal, enter the command RMV N7LNK.

NOTE
2.
Set parameters.
3.
Run the command and the operation is complete.
----End

This lists the alarms and counters related to high-speed signaling links.
Alarms
Table 24-3 lists the alarms related to high-speed signaling links.
Issue 03 (2009-06-08)

24-13

Table 24-3 Alarms related to high-speed signaling links

Alarm ID
Alarm Name
21503
MTP3 Link Unavailable
21504
MTP3 Layer 2 Congestion
21512
MTP3 Link Test Failure
21511
MTP3 Link Test Success
21514
MTP2 Link Service Disrupted
Counters
None.
24.8 References
ITU_T Q.703, "Specifications of Signalling System No. 7 Message transfer part signaling
link"
24-14

Issue 03 (2009-06-08)

25
25 Local Multiple Signaling Point
Local Multiple Signaling Point
About This Chapter

25.1 Overview
This describes the multiple signaling point feature, which enables one physical BSC to serve as
multiple BSCs so that each logical BSC can exchange signaling with the MSC.
25.2 Availability
This lists the NEs, software, and licenses required for the implementation of local multiple
signaling point.
25.3 Impact
This describes the impact of local multiple signaling point on system performance and on other
features.
This describes the functions and provides background information of local multiple signaling
point.
25.5 Capabilities
This describes the capabilities of local multiple signaling point.
25.6 Implementation
This describes how to configure local multiple signaling point.
This describes the alarms and counters related to local multiple signaling point.
25.8 References
None.
Issue 03 (2009-06-08)

25-1

25.1 Overview
This describes the multiple signaling point feature, which enables one physical BSC to serve as
multiple BSCs so that each logical BSC can exchange signaling with the MSC.
Introduction
The feature of local multiple signaling point enables one physical BSC to serve as multiple
logical BSCs. Each logical BSC has an SS7 signaling point code.
After signaling links are established between a logical BSC and the MSC, the logical BSC serves
as an independent BSC and works with the MSC to process the services.
Purposes
You can configure the location area of each logical BSC by implementing the local multiple
signaling feature to properly distribute the traffic volume to the logical BSCs.
The number of messages sent and received within the BSC is reduced when each logical BSC
serves as an independent BSC to interact with the MSC.
Terms
Terms
Definition
Signaling point
In SS7, each NE is assigned a network identifier, which is a

14-bit signaling point code or a 24-bit signaling code.
Within a PLMN, an NE that is assigned a signaling point can
be uniquely addressed in the SS7 network. It can communicate
with other NEs.
Local multiple signaling

points of the BSC
One physical BSC serves as multiple logical BSCs. Each

logical BSC has an SS7 signaling point code and can exchange
signaling with the MSC.
Local signaling point
The local signaling point of the BSC is assigned to the BSC

and is referred to as local originating signaling point.
25-2
Acronym and
Abbreviation
Full Spelling
STP
Signaling Transfer Point
SPC
Signaling Point Code

Issue 03 (2009-06-08)

25.2 Availability
This lists the NEs, software, and licenses required for the implementation of local multiple
signaling point.
NEs Involved
Table 25-1 lists the NEs involved in local multiple signaling point.
Table 25-1 NEs involved in local multiple signaling point
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 25-2 lists the GBSS products and the software versions that support local multiple
signaling point.
Product
Version
BSC
BSC6000
V900R008C01 and later

releases
Important Point
If IP transmission mode is adopted on the A interface, the local multiple signaling point is not
supported.
25.3 Impact
This describes the impact of local multiple signaling point on system performance and on other
features.

The impact of local multiple signaling point on system performance is as follows:
Issue 03 (2009-06-08)

25-3


l
The original intra-BSC handover or intra-BSC directed retry may be converted into
outgoing BSC handover or outgoing BSC directed retry. Thus, the signaling load on the A
interface and the call establishment time are increased.
The location areas should be configured properly to reduce the load impact on the system
effectively. Improper configuration of local areas my have an adverse effect on the
performance of the system.

To apply for the license for local multiple signaling point, in the BSC6000V900R008 Exceptional
Commercial License Application Template, you should fill in the originating signaling point and
destination signaling point of the GMPS subrack in ESN Information. For details on how to
obtain ESN, refer to Querying BSC ESNs.

This describes the functions and provides background information of local multiple signaling
point.
Background Information
According to GSM SS7 protocols, a maximum of 16 narrowband signaling links (64 kbit/s) or
16 high-speed signaling links can be configured between the MSC and the BSC. These signaling
links are used to transmit service signaling.
If narrowband signaling links are required, up to sixteen 64 kbit/s SS7 signaling links can be
configured on the A interface. If the capacity of a BSC is large, the load of signaling links on
the A interface is heavy. Thus, narrowband signaling links cannot meet the traffic requirements.
Then, one physical BSC serves as multiple logical BSCs. As a local signaling point, each logical
BSC can be considered as an independent BSC and it carries a certain traffic volume.
Multiple pairs of signaling points take over the traffic volume that is previously carried by one
pair of signaling points (the MSC and one physical BSC). The multiple pairs of signaling points
can be the MSC and logical BSC 1, the MSC and logical BSC 2, ..., the MSC and logical BSC
n. A maximum of 16 signaling links can be configured between each pair of signaling points.
Assume that there are N local signaling points. The ratio of the traffic volume on the signaling
links between each pair and the total traffic volume is 1:N. The load of signaling links on the A
interface is minimized.
In addition, when one physical BSC serves as multiple logical BSCs, the stability of the BSC
and MSC increases. When one logical BSC is faulty, the services carried by the other logical
BSCs are not affected.
Functions
In the GSM SS7, signaling messages are transmitted on the signaling links between two signaling
points (the BSC and the MSC).
If E1 transmission is adopted on the A interface, the data transfer rate on each timeslot is 64
kbit/s. Each SS7 narrowband signaling link on the A interface uses only one 64 kbit/s timeslot.
Based on the traffic volume on the A interface, several SS7 signaling links need to be configured
to carry service signaling between the BSC and the MSC. Thus, the traffic load on each signaling
25-4

Issue 03 (2009-06-08)

link meets the specified requirements ensuring the security and reliability of signaling
transmission.
According to the SS7 protocols, each SS7 signaling link between a pair of signaling points has
a unique signaling link code (SLC). The SLC has four bits. This indicates that the number of
signaling links between a pair of signaling points cannot exceed 16.
Figure 25-1 Signaling links between the BSC and the MSC
link0
MSC
BSC
link15
SPC0
For a large capacity BSC, more than 16 narrowband signaling links on the A interface are
required to meet the requirements of traffic volume and the load on the signaling links. Local
multiple signaling points of the BSC can be used to increase the signaling links between the
BSC and the MSC. In case the total traffic volume is not increased, the load of each signaling
link is decreased.
Assume that one physical BSC serves as two logical BSCs (BSC 1 and BSC 2). Figure 25-2
shows the connections of local multiple signaling points.
Figure 25-2 Connections of local multiple signaling points
link0
Logical
BSC1
Logical
BSC2
BSC
SPC1
link15
link0
BSC
SPC2
MSC
SPC0
link15
25.5 Capabilities
This describes the capabilities of local multiple signaling point.
The capabilities of local multiple signaling point are as follows:
Issue 03 (2009-06-08)

25-5


l
The local signaling point is configured in the unit of BM subrack. That is, one local signaling
point is assigned to at least one BM subrack, and each BM subrack must belong to one
local signaling point. Thus, the BSC can be configured with up to four local signaling points.
Each GTCS has only one local signaling point. A common signaling point is provided to
the GTCS and BM subrack to which the GTCS is connected. Thus, when multiple BM
subracks are connected to one GTCS, these BM subracks should be configured with the
same local signaling point.
If a local signaling point is assigned to only one BM subrack, the BM subrack can be
configured with up to sixteen 64 kbit/s signaling links or up to eight high-speed signaling
links on the A interface.
If a local signaling point is assigned to multiple BM subracks, these BM subracks can be

configured with up to sixteen 64 kbit/s SS7 signaling links or up to sixteen high-speed
signaling links on the A interface. In addition, Each BM subrack can be configured with
not more than eight high-speed signaling links.
For a physical BSC, the signaling links (on the Ater interface) of all the local signaling
points must be of the same type. The signaling links (on the A interface) of all the local
signaling points must be of the same type. So, all the signaling links must be configured as
64 kbit/s narrowband signaling links or high-speed (Nx64 kbit/s) signaling links.
All the local signaling points of a physical BSC should have the same encoding scheme:
14-bit signaling point code or 24-bit signaling point code.
25.6 Implementation
This describes how to configure local multiple signaling point.
25.6.1 Configuring Local Multiple Signaling Point

This describes how to configure local multiple signaling point on the BSC6000 Local
Procedure
Step 1 Configure an SS7 signaling point.
1.
25-6
On the Management Tree tab page of theBSC6000 Local Maintenance Terminal, rightclick BSC6000, and then choose Configure SS7 Signaling Point from the shortcut menu.
A dialog box is displayed, as shown in Figure 25-3.

Issue 03 (2009-06-08)

Figure 25-3 Configure SS7 Signaling Point dialog box
2.
Click the OSP tab. Then, click Add OSP. A dialog box is displayed, as shown in Figure
25-4.
Figure 25-4 Add OSP dialog box
3.
Issue 03 (2009-06-08)
Set relevant parameters and then click OK.

25-7

NOTE
A maximum of four OSPs can be configured. After the configuration, click OK to return to the dialog
box shown in Figure 25-3.
4.
In Figure 25-3, click the DSP tab. A dialog box is displayed, as shown in Figure 25-5.
Figure 25-5 Configure SS7 Signaling Point dialog box
5.
25-8
Click Add DSP. A dialog box is displayed, as shown in Figure 25-6.

Issue 03 (2009-06-08)

Figure 25-6 Add a DSP.
NOTE
If there is no direct physical link between the OSP and the DSP, then you have to configure STPs.
In the dialog box, as shown in Figure 25-6, set Using STP to Yes.
6.
Set the parameters of the DSP.
Step 2 Configure the mapping between subracks and signaling points.

1.
Issue 03 (2009-06-08)
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000 and choose Configure Subrack-OSP Mapping from the shortcut menu.

25-9

Figure 25-7 Configure Subrack-OSP Mapping dialog box
2.
Set OSP for the target subrack.
3.
Click Finish to complete the configuration.

NOTE
For each BM subrack, you should configure the mapping between the BM subrack and the local
signaling point. For each signaling point, you should configure SS7 signaling links. The configuration
procedure is similar to configuring general SS7 signaling links.
----End

This describes the alarms and counters related to local multiple signaling point.
Alarms
None.
Counters
None.
25.8 References
None.
25-10

Issue 03 (2009-06-08)

26 Semipermanent Link
26
Semipermanent Link
About This Chapter

26.1 Overview
This describes semipermanent link, which helps to improve the usage of existing transmission
resources and enables telecom operators to minimize the operation cost.
26.2 Availability
This lists the NEs and software required for the implementation of semipermanent link.
This describes the connections and implementation of the semipermanent link.
26.4 Capabilities
None.
26.5 Implementation
This describes how to configure a semipermanent link and a monitoring timeslot.
This lists the alarms and counters related to semipermanent link.
26.7 References
None.
Issue 03 (2009-06-08)

26-1

26.1 Overview
This describes semipermanent link, which helps to improve the usage of existing transmission
resources and enables telecom operators to minimize the operation cost.
Definition
The semipermanent link feature enables some of the idle E1 timeslots in the current network to
be used to provide transmission paths for subscribers. The paths are used to transmit such
information as business hall information, alarm information on the BTS AC power supply, and
other maintenance information.
Purposes
When the telecom operator needs to transmit some data from one terminal to another terminal
and the data does not have a high requirement for the transmission bandwidth, the idle
transmission resources in the GSM network can be specially used to transfer the data.
Terms
Terms
Definition
OML
Operation and maintenance link (OML) is used to operate and maintain a

BTS.
RSL
Radio signaling link (RSL) is a link between the BSC and a TRX. The RSL
is used to transmit radio signaling.
Ater
connection
path
Ater connection path is the transmission path between the GMPS/GEPS

and the GTCS. It is used to transmit traffic data and signaling.

Acronyms and
Abbreviations
Full Spelling
CIC
Circuit Identity Code
HW
High Way
26.2 Availability
This lists the NEs and software required for the implementation of semipermanent link.
NEs Involved
Table 26-1 lists the NEs involved in semipermanent link.
26-2

Issue 03 (2009-06-08)

Table 26-1 NEs involved in semipermanent link

MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 26-2 lists the versions of GBSS products that support semipermanent link.
Product
Version
BSC
BSC6000
BTS
BTS3012
BTS3012A
E

DTRU
QTRU
DTRU
QTRU
BTS3006C
BTS3002E
DBS3900 GSM
BTS3900 GSM
BTS3900A GSM
Miscellaneous
Timeslot cross connection equipment is required at both ends of the semipermanent link. The
equipment extracts the timeslots that are assigned to the semipermanent link to transmit signals.

This describes the connections and implementation of the semipermanent link.
26.3.1 Connections of Semipermanent Link

This describes the connections of a semipermanent link. The boards related to a semipermanent
link are the transparent transmission interface board, GTNU, GEIUB, GEHUB, and BTS
interface board.
Issue 03 (2009-06-08)

26-3

Generally, when an MS makes a call, the BSS connects the CIC link on the A interface and the
link on the Abis interface through the GTNU, interface board, and GDPUC. When the call is
disconnected, the connections are released. The previous procedure for establishing a link is not
applicable to a semipermanent link. After the data related to a semipermanent link is configured,
the BSS system automatically establishes the link. Except that the link is manually deleted, the
link remains available.
In the traditional TDM transport mode, to establish a semipermanent link from the BTS to the
A interface, the BSS system must reserve a timeslot on the E1 link that connects to the transparent
transmission board, GTNU, GEIUB, and BTS interface board. The timeslot is not used to
transmit traffic signals or signaling. Then, the BSS system connects the reserved timeslots one
by one to form a connection path.Figure 26-1 shows a semipermanent link in the BSS system
in the TDM transport mode.
Figure 26-1 Semipermanent link in the BSS system (in TDM transport mode)
Transparent
transmission
interface
board
G
T
N
U
G
E
I
U
B
B
T
S
1
B
T
S
2
In the Abis transport optimization mode, the physical links are established by connecting a
timeslot on a port of the GEHUB to a timeslot on another port, and then by using cables to
connect the ports of the GEHUB and the GEIUB. Other links are connected in the same way as
the TDM transport mode. Figure 26-2 shows a semipermanent link in the BSS system in the
Abis transport optimization mode.
Figure 26-2 Semipermanent link in the BSS system (in Abis transport optimization mode)
Transparent
transmission
interface
board
G
T
N
U
G
E
I
U
B
G
E
H
U
B
B
T
S
1
B
T
S
2
NOTE
The transparent transmission interface board is only responsible for transparent transmission of signals. It
can be configured as an output-only board, an input-only board, or a board for both input and output.
In the BSS system, semipermanent links are of two types:

l
Semipermanent link
The semipermanent connection refers to the connection on both sides of the GTNU. In this
connection, the BSC interface boards are used for input and output, and the GTNU
exchanges signals between the interface boards. The semipermanent connection can be
26-4

Issue 03 (2009-06-08)

configured on the BSC6000 Local Maintenance Terminal or Local Maintenance

Terminal.
l
Monitoring timeslot
The monitoring timeslot refers to the semipermanent link between the BTS and the
transparent transmission interface board in the BSC. You can configure the monitoring
timeslot on the BSC6000 Local Maintenance Terminal or Local Maintenance
Terminal.
NOTE
Based on actual requirements, the input port and output port can be configured on the same interface board.
On the BSC6000 Local Maintenance Terminal or Local Maintenance Terminal, the semipermanent
connection is configured on the basis of the BSC, whereas the monitoring timeslot is configured on the
basis of the BTS.
The main difference between the semipermanent connection and the monitoring timeslot is the
start point and end point of the two connections. As the two ends of the monitoring timeslot are
the BSC and the BTS, a semipermanent link is established when the monitoring timeslot is
configured.
26.3.2 Implementation of Semipermanent Link

This describes the implementation of semipermanent link in different physical entities.
Implementation of a Semipermanent Link in the Interface Board

The connection between the E1 timeslot of the BSC interface board and the highway timeslot
of the GTNU depends on the net table sent by the BSC. The BSC interface board supports
semipermanent links of 8 kbit/s, 16 kbit/s, 32 kbit/s, and 64 kbit/s. The 64 kbit/s semipermanent
link on the Ater interface can be multiplexed with the RSL. No semipermanent link can be
configured between the BM subrack and the TC subrack.
Implementation of a Semipermanent Link in the BTS

The BTS interface board can transparently transmit the timeslot signals on one port to any other
port. Thus, a semipermanent link (monitoring timeslot) of the BTS can be configured. The
monitoring timeslot signals are transmitted from any other port. Alternatively, the monitoring
timeslot signals are transparently transmitted to the incoming E1 timeslot of a lower-level BTS.
Thus, the semipermanent link of cascaded BTSs is realized.
Implementation of a Semipermanent Link in the GTNU

A connection is established between the timeslot of the semipermanent link on the BSC interface
board and the input port on the GTNU. In addition, a connection is established between the
timeslot of the semipermanent link on the BSC interface board and the output port on the GTNU.
The GTNU establishes a connection between these connections based on relevant timeslots.
Thus, a semipermanent link is established between the transparent transmission interface board
and another interface board or a BTS.
After the semipermanent link is configured, timeslot cross connection equipment should be
installed at both ends of the physical link. The equipment extracts required timeslots to transmit
information.
Issue 03 (2009-06-08)

26-5

26.4 Capabilities
None.
26.5 Implementation
This describes how to configure a semipermanent link and a monitoring timeslot.
26.5.1 Configuring a Semipermanent Link

This describes how to configure a semipermanent link on the BSC6000 Local Maintenance
Terminal .
Prerequisite
Before configuring a semipermanent link, you should install timeslot cross connection
equipment at both ends of the semipermanent link. The equipment extracts the timeslots assigned
to the semipermanent link to transmit information.
The license of NC2 is applied and activated. To apply for and activate the license, do as follows:
1.
Fill in the Resource Control Items column of Number of semipermanent connection

under Function control items in BSC6000V900R008 Exceptional Commercial License
Application Template.
2.
Activate the license on the Local Maintenance Terminal. For details, refer to Activating
the BSC License.
Procedure
BSC6000, and then choose Configure Semipermanent Link on the shortcut menu. A dialog
box is displayed.
26-6

Issue 03 (2009-06-08)

Figure 26-3 Configuring a semipermanent link (2)
Step 3 Set Semipermanent Link Rate, In-BSC Subrack No., In-BSC Slot No., In-BSC Port No.,
In-BSC Timeslot No., In-BSC Sub-Timeslot Start No., Out-BSC Subrack No , Out-BSC
Slot No., Out-BSC Port No., Out-BSC Timeslot No., and Out-BSC Sub-Timeslot Start
No.. Then click OK. A dialog box is displayed, as shown in Figure 26-4.
Figure 26-4 Configuring a semipermanent link (3)
Issue 03 (2009-06-08)

26-7

Step 4 Click Finish. A dialog box is displayed.

Step 5 Click Yes. The configuration is complete.
----End
26.5.2 Configuring a Monitoring Timeslot

This describes how to configure a monitoring timeslot on the BSC6000 Local Maintenance
Terminal .
Prerequisite
Before configuring a monitoring timeslot, you should install timeslot cross connection
equipment at both ends of the semipermanent link. The equipment extracts the timeslots assigned
to the semipermanent link to transmit information.
Procedure
the target site, and then choose Configure Site Monitor Timeslot on the shortcut menu.
Step 2 On the displayed dialog box, click Set Monitor Timeslot.
Step 3 On the displayed dialog box, click Add Record. A dialog box is displayed, as shown in Figure
26-5.
Figure 26-5 Configuring site monitor timeslot (3)
26-8

Issue 03 (2009-06-08)

Step 4 Set Timeslot Rate, In-BSC Subrack No., In-BSC Slot No., In-BSC Port No., In-BSC
Timeslot No , In-BSC Sub-Timeslot No. Site Port No., Out-Site Timeslot No. and Out-Site
Sub-Timeslot No..Then click OK. A dialog box is displayed, as shown in Figure 26-6.
Figure 26-6 Configuring site monitor timeslot (4)
Step 5 Click OK.

Step 6 Click Finish. Monitoring timeslots are configured for the BTS.
----End
26.5.3 Verifying a Semipermanent Link

This describes how to verify whether a semipermanent link is successfully established.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, click the BSC Attributes tab.
Step 2 On the displayed dialog box, click Timeslot of E1/T1 Int. A dialog box is displayed, as shown
in Figure 26-7.
Issue 03 (2009-06-08)

26-9

Figure 26-7 View E1/T1 dialog box
Step 3 Click the target interface E1 tab. Take Ater Interface E1/T1 for example. A dialog box is
26-10

Issue 03 (2009-06-08)

Figure 26-8 Ater Interface E1/T1
Step 4 Select Subrack No., Slot No., and Port No.. In the Timeslot list on the right, the Timeslot
Type of the semipermanent link is SemiCon.
----End

This lists the alarms and counters related to semipermanent link.
Alarms
None.
Counters
None.
26.7 References
None.
Issue 03 (2009-06-08)

26-11
26-12


Issue 03 (2009-06-08)

27
27 Discontinuous Transmission and Discontinuous

Reception
Discontinuous Transmission and

Discontinuous Reception
About This Chapter

27.1 Overview
This describes the definitions of DTX and DRX and purposes of applying DTX and DRX. DTX
and DRX mechanism reduces the interference level and improves the system efficiency. Through
this mechanism, the wastage of system resources can be minimized and meanwhile an acceptable
signal quality is maintained.
27.2 Availability
This lists the NEs and software required for the implementation of DTX and DRX.
This describes the technical aspects of DTX and DRX. The DTX and DRX improve the system
efficiency by introducing the comfortable noises and enabling the MS to detect system
information sent from paging groups.
27.4 Capabilities
None.
27.5 Implementation
This describes how to configure DTX and DRX.
None.
27.7 References
Issue 03 (2009-06-08)

27-1

Reception

27.1 Overview
This describes the definitions of DTX and DRX and purposes of applying DTX and DRX. DTX
and DRX mechanism reduces the interference level and improves the system efficiency. Through
this mechanism, the wastage of system resources can be minimized and meanwhile an acceptable
signal quality is maintained.
Definition
l
Discontinuous Transmission
When the MS is engaged but no speech signals are transferred, the MS sends only
comfortable noises to the peer end. These comfortable noises are added deliberately and
periodically. The information contained in the comfortable noises is less than the
information contained in the sampled data of normal speeches.
Discontinuous Reception
The MS in idle mode detects only the paging channels within a specific paging group. When
other paging groups send paging messages to the MS, the MS blocks the receive channel.
Purposes
l
DTX
The MS does not keep transmitting speech signals during a call. Typically, only 40% of
the duration of the call is occupied for speech transmission. During the non-speech
transmission period, the MS reduces the transmitted data to suppress the interference to
other channels and to help reserve system resources. In addition, DTX relieves the workload
of the TX module of the MS. The MS can enjoy a longer call duration and standby time.
DTX affects only the transmission of TCH frames.
DRX
Each MS is mapped to a paging group, and each paging group is mapped to a paging subchannel in the serving cell. When operating in idle mode, the MS detects the paging
messages broadcast by the system only on the mapped paging sub-channel. The MS blocks
other paging sub-channels by powering off some hardware. This also save power.
Terms
None.

None.
27.2 Availability
This lists the NEs and software required for the implementation of DTX and DRX.
NEs Involved
Table 27-1 lists the NEs involved in DTX and DRX.
27-2

Issue 03 (2009-06-08)


Reception
Table 27-1 NEs involved in DTX and DRX

MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 27-2 lists the versions of GBSS products that support DTX and DRX.
Product
Version
BSC
BSC6000
BTS
BTS3012
BTS3012AE

DTRU
QTRU
DTRU
QTRU
BTS3006C
BTS3002E
DBS3900 GSM
BTS3900 GSM
BTS3900A GSM
Miscellaneous
None.

This describes the technical aspects of DTX and DRX. The DTX and DRX improve the system
efficiency by introducing the comfortable noises and enabling the MS to detect system
information sent from paging groups.
Issue 03 (2009-06-08)

27-3

Reception

27.3.1 DTX
This describes DTX. Through this mechanism, the transmit power of an MS is reduced when
the MS does not receive any speech signals. DTX is used to improve the speech services of the
entire radio network.
DTX involves the following technical aspects:
l
Silence Descriptor (SID) frames
Voice Activation Detection (VAD) technique
Global Measurement and Local Measurement
When there is no speech signal transmission during a call, the MS sends SID frames to the BTS.
The VAD technique enables the MS to accurately detect speech signals. The principles of SID
frames and the VAD technique are described as follows:
l
Silence Descriptor (SID) frames

The noise coding procedure is basically the same as the speech coding procedure. After
sampling and quantification, the noise data of every 20 ms is coded into a noise block by
a hybrid coder. The noise blocks, which is 260 bits each in length, are constructed as special
SID frames. After channel coding, interleaving, encryption, and modulation, the SID
frames are sent out through eight continuous bursts.
A complete SACCH message block on the TCH consists of four 26 multi-frames (480 ms).
To enable the peer end to identify speech frames and SID frames, the eight continuous
bursts are always sent at the beginning of the third 26 multi-frame. No message is sent on
other frames (except for the SACCH) of a measurement period.
NOTE
A SID encoded with a 20-ms noise block completes the interleaving process with the last SID and
next SID. The first SID completes the interleaving process with the voice frame before it and the
next SID.
The DTX function is optional. UL DTX and DL DTX are independent from each other. The control
unit of DTX is a cell. UL DTX and DL DTX are independent from each other, the two processes are
respectively activated by related system parameters:
l
The UL DTX is activated by the parameters DtxMeasUsed and UL DTX on the BSC side.
The DL DTX is activated by the "DTX Flag" in the "Service/BSC Table on the MSC side and
by the DtxMeasUsed and DL DTX on the BSC side.
DTX is used only in voice transmission mode and non-transparent data transmission mode. UL DTX
depends on the input to the MS and DL DTX depends on the input to the MSC/TRAU.
l
VAD
When DTX is enabled, the coder must decide whether the current signal is a speech signal
or a noise signal. The VAD technique is designed to help the coder to make the decision.
The VAD technique distinguishes the speech from the noise based on a principle that the
energy of noises is always lower than that of speeches. VAD specifies a threshold for the
power of the voice signal based on the power of the noise signal in actual environment.
Only the signal with power value greater than the threshold is identified as voice.
The VAD technique is closely associated with the speech coding algorithm. VAD compares
the energy of filtered signals with the threshold defined by itself, and then decides whether
every output frame contains the speech or the noise. In addition, VAD provides additional
bits to indicate whether or not to transmit the frame.
27-4

Issue 03 (2009-06-08)


Reception
VAD generates a group of thresholds every 20 ms of voice block for decision on whether
the next 20 ms voice block is voice or noise. In case a strong background noise, the noise
signal is identified as the voice by VAD and is sent after encoding.
Two measurement methods are available in the GSM: global measurement and local
measurement.
l
Global measurement: measures the receive level and receive quality in 100 timeslots in the
whole measurement period (four 26 multiframes except idle frames) and calculates the
average value.
Local measurement: measures the receive level and receive quality in 12 timeslots and
calculates the average value, including eight continuous TCH bursts and four SACCH
bursts carrying measurement reports.
To ensure consistency, the BTS and the MS perform the global and local measurements
regardless of the activated UL/DL DTX. Each SACCH measurement report of the BTS and the
MS specifies whether the DTX function is applied, so the BSC can select the global measurement
or local measurement for decision based on the measurement report.
NOTE
In downlink, the network set SRO to 1 when sending frame B
27.3.2 DRX
This describes DRX. In DRX mode, every MS (IMSI) is mapped to a specific paging group.
The MS calculates the paging groups based on the IMSI and the CCCH configuration of the
serving cell, and then detects the system information sent only from the paging groups.
DRX involves the concept of paging group in related GSM protocols.
l
Paging group
In the GSM network, the CCCH includes the AGCH and the PCH. The CCCH can be
carried on one or more physical channels. In case of high paging traffic in a location area,
one physical timeslot for paging message transmission is not enough. The GSM protocol
allows multiple CCCHs to be configured on the TRX carrying the BCCH. The CCCHs can
be configured only on timeslot 0, 2, 4, or 6.
The number of the CCCH message blocks that a cell owns reflects the resources that can
be used as the AGCH or the PCH in the cell. Table 27-3 lists the mapping relation between
the CCCH Conf and the number of CCCH message blocks in the BCCH multi-frame
structure.
Table 27-3 Relation between CCCH configuration and number of CCCH message blocks
in the BCCH multi-frame structure
Issue 03 (2009-06-08)
CCCH Configuration
Number of CCCH Message

Blocks in BCCH Multi-Frame
One physical channel used for CCCH, not

combined with SDCCHs
One physical channel used for CCCH, combined

with SDCCHs

27-5

Reception

CCCH Configuration
Number of CCCH Message

Blocks in BCCH Multi-Frame
Two physical channels used for CCCH, not

18
Three physical channels used for CCCH, not

27
Four physical channels used for CCCH, not

36
BS_AG_BLKS_RES specifies the number of CCCH message blocks used as the AGCH
in the BCCH multi-frame structure. BS-PA-MFRAMS specifies the scale of BCCH multiframes that are used by the paging group.
The formula for calculating the number of paging groups of the service cells is: Number
of paging groups = (Number of CCCH Message Blocks in BCCH Multi-Frame
BS_AG_BLKS_RES) x BS-PA-MFRAMS
l
Calculating the paging group

The formula for calculating the paging group mapped to the MS is:
Paging group = ((IMSI mod 1000) mod (Number of cell paging groups)) div BS-PAMFRAMS
The MS calculates the mapped paging group based on the IMSI and the configuration of
paging channels in the serving cell, and then calculates the paging sub-channel of the
mapped paging group.
27.4 Capabilities
None.
27.5 Implementation
This describes how to configure DTX and DRX.
27.5.1 Configuring DTX

This describes how to configure DTX on the BSC6000 Local Maintenance Terminal.
27-6

Issue 03 (2009-06-08)


Reception
Prerequisite
NOTE
The setting of uplink DTX is completed only on the BSC side.
The setting of downlink DTX should be performed on both the BSC side and the MSC side; otherwise,
the downlink DTX does not work.
Data configuration on the MSC side: The setting of "DTX Flag" in the "Servie/BSC Table" determines
whether downlink DTX is allowed on the MSC side.
l
If Yes is selected, the downlink DTX is enabled. The MSC attaches the DTX flag in the assignment
message, requesting the BSS to read the DTX flag.
If No is selected, the downlink DTX is disabled. The MSC does not request the BSS to read the
DTX flag.
Procedure
the target cell, and then choose Configure Cell Attributes from the shortcut menu. The
Configuring Cell Attributes dialog box is displayed.
Step 2 Double-click the target cell in the Cell view list box to add it to the Selected cells list box.
Step 3 Click Next. The Configuring Cells Attributes dialog box is displayed.
Step 5 In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog
box is displayed, as shown in Figure 27-1.
Issue 03 (2009-06-08)

27-7

Reception

Step 6 Click Handover Data. The Set Handover Parameter dialog box is displayed.
Step 7 Click Advanced. The dialog box as shown in Figure 27-2 is displayed. Select the Filter/Penalty
Data tab.
27-8

Issue 03 (2009-06-08)


Reception
Step 8 Set DtxMeasUsed to Open, and then click OK to return to Figure 27-1.
Step 9 In Figure 27-1, set UL DTX to Shall use to configure uplink DTX.
Step 10 In Figure 27-1, select DL DTX and click OK. The configuration of downlink DTX is complete.
----End
27.5.2 Configuring DRX

This describes how to configure DRX on the BSC6000 Local Maintenance Terminal and
Procedure
Issue 03 (2009-06-08)

27-9

Reception

Figure 27-3 Setting Cell Attributes dialog box
Step 5 Click Idle Mode. The Browse Idle Parameter dialog box is displayed.
Step 6 Set BS_AG_BLKS_RES and BS-PA-MFRARMS. Click OK to complete the configuration.
----End

None.
Alarms
None.
27-10

Issue 03 (2009-06-08)


Reception
Counters
None.
27.7 References
3GPP TS 05.02
Issue 03 (2009-06-08)

27-11

28 Location Service
28
Location Service
About This Chapter

28.1 Overview
This describes location service. Although the precision of the GSM location service is not high,
it can meet the current requirements of the customers in the mobile communications market.
28.2 Availability
This lists the NEs, software, NSS, BSS, and license required for the implementation of location
service.
This describes the technical aspect of LCS. Location service is realized through the interaction
between the software and hardware entity in an LCS server and that in an LCS client.
28.4 Capabilities
This describes the positioning precision of location service.
28.5 Implementation
This describes how to configure location service and simple location service.
This describes the alarms and counters related to location service.
28.7 References
Issue 03 (2009-06-08)

28-1

28 Location Service
28.1 Overview
This describes location service. Although the precision of the GSM location service is not high,
it can meet the current requirements of the customers in the mobile communications market.
Definition
An MS can be positioned according to the longitude and latitude of the GSM BTS and the timing
advance (TA) value.
Purposes
The location service (LCS) enables the network to provide various services for an MS based on
the location of the MS. These services include weather forecasts, trip scheduling, emergency
assistance, stock information, business planning, and transportation conditions.
For single-user message trace, the simple location service can locate the user based on the related
information.
Terms
None.

Acronyms and
Abbreviations
Full Spelling
PLMN
PLMN Public Land Mobile Network
LCS
LoCation Service
TA
Timing Advance
28.2 Availability
This lists the NEs, software, NSS, BSS, and license required for the implementation of location
service.
NEs Involved
Table 28-1 lists the NEs involved in location service.
Table 28-1 NEs involved in location service
28-2
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR

Issue 03 (2009-06-08)

MS
BTS
28 Location Service
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 28-2 lists the NEs and software versions that support location service.
Product
Version
BSC
BSC6000
Miscellaneous
The location service is available only when both the NSS and BSS support it.
Location service requires a license on the BSS side.

This describes the technical aspect of LCS. Location service is realized through the interaction
between the software and hardware entity in an LCS server and that in an LCS client.
28.3.1 Concepts
This describes the concepts related to location service: LCS server and LCS client.
l
LCS server
The LCS server is the software and hardware entity that provides location service. The LCS
server receives service requests and responds to the requests. It consists of components that
are distributed in one or more PLMNs.
LCS client
The LCS client is the software and hardware entity that obtains location information for
one or more MSs. The LCS client interacts with the LCS server. To obtain location
information, the LCS client subscribes to location service from the LCS server.
The LCS client may and may not interact with the MS.
The LCS client formats data, displays data, and manages GUI.
Each LCS client has a unique international identifier.
28.3.2 Location Service Processing Procedure

This describes the processing procedure of location service.
Issue 03 (2009-06-08)

28-3

28 Location Service
The LCS server is located inside the BSC. Figure 28-1 shows the processing procedure of
location service.
Figure 28-1 Processing procedure of location service
MSC
BSC
Perform Location Request
Perform Location Response (Abort)
1.
On receiving a location request from an MS, the MSC sends a Perform Location Request
message to the BSC.
2.
On receiving the Perform Location Request message, the BSC performs as follows:
If the serving cell of the MS does not support location service, the BSC performs no
processing and sends no response message to the MSC.
If the serving cell of the MS supports location service but does not support the location
algorithms required by the MSC, the BSC sends a Perform Location Response message to
the BSC. The cause value of the message is Position Method Failure.
NOTE
As shown in Figure 28-1, Perform Location Response (Abort) indicates two conditions:
If the BSC successfully processes a request, it sends a Perform Location Response message to the
MSC. If the BSC fails to process the request, it sends a Perform Location Abort message to the MSC.
l
If the serving cell of the MS supports the location service and required location algorithms,
the BSC calculates the required information by referring to the data configuration and TA
value. Then, the BSC sends a Perform Location Response message to the MSC.
28.3.3 Location Estimate

This describes Location Estimate, which indicates the location information on an MS.
Location Estimate indicates the location information on an MS. Represented by a certain shape,
Location Estimate indicates the possible area where an MS is located.
According to related protocols, location information can be represented by seven shapes,
including Ellipsoid Point, Ellipsoid point with uncertainty circle, Polygon, and Ellipsoid Arc.
The Huawei BSC uses the CELL+TA positioning method. Location Estimate is represented by
Ellipsoid Arc, as shown in Figure 28-2.
28-4

Issue 03 (2009-06-08)

28 Location Service
Figure 28-2 Location information represented by Ellipsoid Arc

North
Point(o)
q
b
r1
r2
: offset angle, that is, Antenna Azimuth Angle(Degree)
: Included Angle(Degree)
r1: inner radius
r2: uncertainty radius
Point (o): indicates the coordinate of a location. Point (o) is

identified by the longitude and latitude of the location.
NOTE
If r1 = 0, the arc is a sector. In addition, if = 0 and = 360, the arc is a circle, which represents an
omnidirectional cell.
Generated by the LCS server, the Location Estimate indicates the location area of the positioning
target. Location Estimate is contained in the Perform Location Response message.
Figure 28-3 shows the coding of the Location Estimate represented by Ellipsoid Arc.
Issue 03 (2009-06-08)

28-5

28 Location Service
Figure 28-3 Coding of the Location Estimate represented by Ellipsoid Arc

8
1
7
0
Space
1
Octet 1
Octet 2
Degrees of latitude
Octet 3
Octet 4
Octet 5
Degrees of longitude
Octet 6
Octet 7
Inner radius
Octet 8
Octet 9
0
Space
Uncertainty radius
Octet 10
Offset angle
Octet 11
Included angle
Octet 12
Confidence
Octet 13
0
Space
Table 28-3 Description of coding for the Location Estimate represented by Ellipsoid Arc
Name
Meaning
Bit value 0 = North

Bit value 1 = South
Degrees of latitude
The latitude of Point (o), as shown in Figure 28-2.

N = [X x 223/90], where [ ] is an integral function. The value of N
ranges from 0 to 2231.
Assume that N is the coding of the latitude, and X is the absolute value
of the actual latitude. The value of X ranges from 0 to 90.
N is coded in 24 bits: bit 0 to bit 23. Where, bits 0 through 22 are value
bits and bit 23 is a sign bit.
NOTE
When X = 90, the value of N is 2231.
28-6

Issue 03 (2009-06-08)

28 Location Service
Name
Meaning
Degrees of
longitude
The longitude of Point (o), as shown in Figure 28-2.

N = [X x 224/360], where [ ] is an integral function. The value of N
ranges from 223 to 2231.
Assume that N is the coding of the longitude, and X is the absolute
value of the actual longitude. The value of X ranges from 180 to
+180.
N is coded in 24 bits (bit 0 to bit 23) and is represented by two's
complement.
NOTE
When X = 180, the value of N is 2231.
r1, as shown in Figure 28-2.
Inner radius
N = [R/5], where [ ] is an integral function.

Assume that N is the coding of inner radius, and X is the actual value
of inner radius.
N is coded in sixteen bits (bit 0 to bit 15).
Uncertainty radius
r2, as shown in Figure 28-2.

r = C((1 + x)k 1), where C = 10 and x = 0.1.
Assume that K is the coding of Uncertainty radius, and r is the actual
value of Uncertainty radius.
K is coded in seven bits (bit 0 to bit 6). The value of K ranges from 0
to 127.
, as shown in Figure 28-2.
Offset angle
N = [a/2], where [ ] is an integral function. The value of N ranges from

0 to 180.
Assume that N is the coding of the angle, and a is the actual value of
the angle. N is coded in eight bits (bit 0 to bit 7).
Included angle
, as shown in Figure 28-2.

N = [a/2], where [ ] is an integral function. The value of N ranges from
0 to 180.
Assume that N is the coding of the angle, and a is the actual value of
the angle. N is coded in eight bits (bit 0 to bit 7).
Confidence
Confidence indicates the possibility that an MS is located in the area

represented by Ellipsoid Arc.
K is the coding of confidence and is coded in seven bits (bit 0 to bit 6).
The value of K ranges from 0 to 100.
NOTE
The value of r1+r2 is determined by the tilt and Antenna Altitude(Meter) of the antenna, and the value
of r1 is determined by TA.
Issue 03 (2009-06-08)

28-7

28 Location Service
The Location Estimate can be configured on the BSC6000 Local Maintenance Terminal. For
details, refer to Step 2 in 28.5.1 Configuring Location Service.
28.3.4 Message Format

This describes the IEs of two messages between the BSC and the MSC.
Table 28-4 describes the Perform Location Request message from the MSC to the BSC. Where,
n indicates n bytes.
Table 28-4 Perform Location Request message
28-8
Information
Element
Description
Transmission
Direction
Length (Bytes)
Message type
Message type
Both
Location Type
Contains location
information and
positioning method.
Both
3n
Cell Identifier
Cell ID
Both
5-10
Classmark
Information Type 3
MS classmark 3
Both
3-14
LCS Client Type
Type of the LCS

client
Both
3n
Chosen Channel
the channel that is

assigned to the
current service
Both
LCS Priority
The priority of
location service.
Level 0 is the highest
priority, and level 1
is the normal
priority.
Both
3n
LCS QoS
QoS of location
Both
service. The
parameters related to
LCS QoS include
horizontal precision
and vertical
precision.
3n
GPS Assistance
Data
GPS assistance data
MSCBSS
3n
APDU
Protocol data unit of

the BSS LAPD layer
Both
3n

Issue 03 (2009-06-08)

28 Location Service
Table 28-5 describes the Perform Location Response message that the BSC sends to the MSC.
Where, n indicates n bytes.
Table 28-5 Perform Location Response message
Information
Element
Description
Transmission
Direction
Length (Bytes)
Message type
Message type
Both
Location Estimate
Location
information on an
MS
Both
3-22
Positioning Data
Positioning data,
including the
resolution and
positioning method
Both
3n
Deciphering Keys
deciphering keys,
including encryption
identifier, current
deciphering key, and
deciphering key of
the next data frame
BSSMSC
3n
LCS Cause
Cause value of
location service
Both
3n
28.4 Capabilities
This describes the positioning precision of location service.
The positioning precision depends on the following factors:
l
Angle of antennas in a cell: Directional antennas have higher positioning precision than
omnidirectional antennas.
Movement speed of the LCS client: The faster the LCS client moves, the lower the
positioning precision is.
Precision of the location data configured in a cell.

NOTE
If all the following conditions are met, an MS can be positioned in a sector area that has a radius of 500
meters (the distance of one TA). The conditions are as follows: The location of the MS is unchanged. The
transmission quality of radio signals is good. The data configuration of a cell is correct. The Cell+TA
positioning method is used.
28.5 Implementation
This describes how to configure location service and simple location service.
Issue 03 (2009-06-08)

28-9

28 Location Service
28.5.1 Configuring Location Service

This describes how to configure location service on the BSC6000 Local Maintenance
Terminal.
Prerequisite
1.
When applying for the LCS license, ensure that the Number of resources column
corresponding to Whether to activate the LCS(CELLID+TA) function or not under
Function control items row in BSC6000V900R008 (None) Commercial License
Application Template is set to 1. Value 1 indicates that this function should be enabled.
2.
the BSC License.
Procedure
Step 1 Configure the BSC to support location service.
1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then choose Configure BSC Attributes on the shortcut menu. A
2.
Click the Software Parameters tab. Set LCS Support Control to Yes, as shown in Figure
28-4.
Figure 28-4 Configuring the LCS Support Control parameter
Step 2 Configure the LCS attributes of a cell.

28-10

Issue 03 (2009-06-08)

28 Location Service
1.

Tree tab page, and choose Configure Cell Attributes.
2.
3.
In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A
4.
Issue 03 (2009-06-08)
Click Other Attributes. A dialog box is displayed. Click Advanced. A dialog box is

28-11

28 Location Service
5.
Click the LCS Parameters tab, and then set the parameters as required.
6.
Click OK to return to the upper-level menu until configuring location service is complete.
----End
Postrequisite
In a location service enabled cell, use an MS to make a test call. On the BSC6000 Local
Maintenance Terminal, enable the MS tracing function to trace the call signaling of the MS.
When analyzing the signaling on the A interface, you can find the Perform Location Request
and Perform Location Response messages. If the Perform Location Response message contains
the Location Estimate IE, you can infer that location service is active. If you select Display
Location Information, the location information is displayed.
28.5.2 Configuring Simple Location Service

This describes how to configure simple location service on the BSC6000 Local Maintenance
Terminal.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, click the Trace & Monitor tab. Then, doubleclick Trace User Message on the tab page. A dialog box is displayed, as shown in Figure
28-7.
28-12

Issue 03 (2009-06-08)

28 Location Service
Figure 28-7 Trace User Message dialog box
Step 2 Select Display Location Information in the Set Display area to configure simple location
service.
NOTE
For details on how to configure the parameters in the dialog box shown in Figure 28-7, refer to 9.6.1
Configuring Message Tracing.
Step 3 Click OK to complete the parameter settings for single-user message tracing and to save the
trace message file.
Step 4 On the BSC6000 Local Maintenance Terminal, click the Trace & Monitor tab. Then, doubleclick Review Tracing on the tab page. Select a trace message file and open it. A window is
In the window shown in Figure 28-8, the Location Information column lists the location
information about the user during the period of message trace.
Issue 03 (2009-06-08)

28-13

28 Location Service
Figure 28-8 Trace User Message window
----End

This describes the alarms and counters related to location service.
Alarms
None.
Counters
None.
28.7 References
3G TS 23.032 V3.1.0 (2000-03)
28-14

Issue 03 (2009-06-08)

29 TFO
29
TFO
About This Chapter

29.1 Overview
This describes the application of the TFO in improving voice quality.
29.2 Availability
This lists the NEs, software, and voice coding schemes required for the implementation of TFO.
29.3 Impact
This describes the impact of TFO on other system features.
This describes the application of the TFO. Once a call connection is established, the TRAU
frame is used for channel activation so that the TFO message response mechanism is established.
The rearranged speech frames form the TFO frames so that the codec process is reduced to such
a level that the speech quality is significantly improved.
29.5 Capabilities
This describes the TFO capabilities with different service types.
29.6 Implementation
This describes how to configure and verify TFO.
None.
29.8 References
Issue 03 (2009-06-08)

29-1

29 TFO
29.1 Overview
This describes the application of the TFO in improving voice quality.
Definition
There is a process called the Tandem Operation during a conversation in which the speech is
transcoded two times. Speech signals are degraded due to Tandem Operation, as shown in Figure
29-1.
Figure 29-1 Tandem operation
Speech
frame
Encoding
BTS
Speech
compression
BSC
(TC)
Decoding
PCM
MSC
BSC
(TC)
PCM
A-law/u-law PCM
Encoding
BTS
Speech
frame
Speech
compression
Decoding
Figure 29-2 shows the Tandem Free Operation in which the speech signals are transparently
transferred between two MSs.
Figure 29-2 TFO
Speech
frame
BTS
Disable
Tandem
operation
Endcoding
BSC
(TC)
TFO
PCM
MSC
PCM
Disable Disable
Tandem Tandem
operation operation
BSC
(TC)
TFO
BTS
Speech
frame
Disable
Tandem
operation
Speech compression
Decoding
Purposes
TFO eliminates one encoding/decoding process to improve the speech quality.
29-2

Issue 03 (2009-06-08)

29 TFO
Terms
Terms
Definition
TFO
Tandem Free Operation: It eliminates one encoding/decoding

process during an MS-MS call.
IPE
In Path Equipment: The IPE can be classified into echo canceller,

digital communication multiplexer equipment (DCME), dual tone
multi-frequency (DTMF) generator, A-law/u-law converter, and so
on.
TFO MESSAGE
The TFO MESSAGE is the in-band signaling used for TFO

negotiation between TCs.
TFO FRAME
As shown in Figure 29-2, TRAU frame is the speech data format

used between the MS and the TC. TFO frame is the speech data
format used between the TCs once the TFO is established.

Acronyms and
Abbreviations
Full Spelling
AEC
Acoustic Echo Cancellation
ALC
Adaptive Level Control
EFR
Enhance Full Rate speech codec
FR
Full Rate speech codec
HR
Half Rate speech codec
IPE
In Path Equipment
MOS
Mean Opinion Score
TFO
Tandem Free Operation
TRAU
Transcoding and Rate Adaptation Unit
29.2 Availability
This lists the NEs, software, and voice coding schemes required for the implementation of TFO.
NEs Involved
Table 29-1 lists the NEs involved in TFO.
Issue 03 (2009-06-08)

29-3

29 TFO
Table 29-1 NEs involved in TFO

MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l : not involved
l : involved
Software Releases
Table 29-2 lists the versions of GBSS products that support TFO.
Product
BSC
Version
BSC6000
Miscellaneous
The BSC supports the TFO in the FR, HR, EFR coding schemes. It dos not support the TFO in
the AMR HR and AMR FR coding schemes.
When BSC Subrack Combination Type is set to IP on A Interface, the BSC does not support
TFO.
When BSC Subrack Combination Type is set to BM/TC Together:
l
If the TDM mode is applied on the Abis interface, the BSC supports TFO.
If the HDLC/IP mode is applied on the Abis interface, the BSC does not support TFO.
29.3 Impact
This describes the impact of TFO on other system features.

None

Once TFO is enabled, the system disables the AEC/ALC/ANR associated with the FR/EFR/HR
services.

This describes the application of the TFO. Once a call connection is established, the TRAU
frame is used for channel activation so that the TFO message response mechanism is established.
29-4

Issue 03 (2009-06-08)

29 TFO
The rearranged speech frames form the TFO frames so that the codec process is reduced to such
a level that the speech quality is significantly improved.
29.4.1 TFO Messages

This describes the TFO message types, namely, TFO_REQ, TFO_ACK, and IS_IPE.
Transmission of TFO Messages

TFO messages are transmitted in bit spacing schemes. In other words, the least significant bit
in the first sample of the 16 PCM samples is replaced. This minimizes the impact caused by bit
replacement.
Classification of TFO Messages

l
TFO_REQ messages
This command type requests to activate the TFO feature.
TFO_ACK messages
This command type responds to the TFO_REQ commands.
IS_IPE messages
The IS_IPE messages are classified into FO_TRANS messages and TFO_NORMAL
messages.
The TFO_TRANS messages are used to activate and maintain the ability of the IPE
equipment to support the TFO feature.
The TFO_NORMAL messages are used to revert the IPEs to normal operation.
NOTE
The TFO_FILL does not belong to IS_IPE in terms of classification. Its enables the IPE to synchronize
with the TFO message in short. The TFO_FILL is mainly used to re-synchronize the IPEs in abnormal
cases.
l
Other commands
When the TFO_DUP command is used in intra-cell and inter-cell handovers, the TFO
connection between the newly activated TRAU channels and the original TRAU
channels can be established immediately.
The TFO_SYL command reports that the synchronization information of the TFO frame
is lost. It is mainly used for channel handover.
29.4.2 TFO Frame

This describes the TFO frame, which is actually a bit conversion format of the TRAU (see GSM
Rec.08.60).
The TFO frame occupies the two least significant bits of the 8-bit PCM frame. The remaining
six bits are still used for transmitting the decoded speech signals. In other words, when the TFO
is activated, the decoder of the TRAU is still in work. On receiving the TRAU frame through
the Abis interface, the decoder performs decoding and A-law conversion of the TRAU frame,
and generates a new PCM frame by combining the six most significant bits of the TRAU frame
with the TFO frame.
Issue 03 (2009-06-08)

29-5

29 TFO
29.4.3 TRAU Operating Process in TFO Mode

This describes the TRAU operating process in ideal and abnormal cases.
TRAU Operating Process in Idea Case (Simple Mode)

1.
The TRAU is activated when it receives a speech frame. The encoder and decoder are
activated at the same time.
2.
The TRAU activates the TFO protocol processor, sends the TFO_REQ message on the A
interface, and monitors the TFO messages on the A interface (check whether there is
TFO_REQ or TFO_ACK sent from the remote end).
3.
If the coding format of the TRAUs matches at two ends, the TRAU initiates the uplink TFO
and begins to send TFO frames. The TRAU also embeds TFO_TRANS messages into the
TFO frames to maintain the "direct pass-through" function of the IPE.
4.
On receiving the remote TFO frames through the A interface, the TRAU initiates the
downlink TFO and deactivates the encoder. The TFO protocol processor is then responsible
for the construction and transmission of downlink TRAU frames.
5.
If the synchronization with the BTS fails in 10 successive frames, the current channel is
regarded being released. The TRAU deactivates the decoder and the TFO protocol
processor.
Handling in Abnormal Cases

l
After a channel is activated, the TRAU sends consecutive TFO_REQ commands. If no

response is received when the number of TFO_REQ commands has exceeded the threshold,
the TRAU stops sending TFO messages but keeps monitoring the TFO messages on the A
interface until the channel is released.
If the coding format of the TRAUs does not match at two ends, the TRAU aborts the
establishment of TFO links and returns to normal operation.
Bit errors occur during the transmission of TFO frames and TFO messages.
Bit errors are detected through comparison between synchronization bits and Cyclic
Redundancy Check (CRC).
The TFO messages can do certain error correction of the bit errors. However, the bits to be
corrected differ. For details, refer to the protocols listed in 29.8 References.
If the TFO frames cannot be normally received due to bit errors, only synchronization bit
errors are allowed based on the DTX status. If there are error parameters, the current frame
should be discarded and replaced with the preceding good one.
Synchronization lost of the TFO frames

In normal situations, the synchronization lost of the TFO frames are mainly caused by the
instant channel handover. The TRAU has no knowledge of the channel handover
information. Therefore, if there is synchronization lost of TFO frames, the TRAU does not
quit the TFO activation status but tries to establish a connection with the remote TRAU
through the TFO_SYL message. The remote TRAU responses with the TFO_DUP. If the
connection is established within a predefined period, the current status of the call remains;
if the connection is not established within the predefined period, the local TRAU quits the
TFO status.
29.4.4 Realization of TFO

This describes how the TRAU activates a channel on the Abis interface, transfers TFO messages,
and establishes acknowledgement mechanism.
29-6

Issue 03 (2009-06-08)

29 TFO
1.
During the call setup process, the TRAU searches for valid TRAU frames on the Abis
interface to activate the current channel.
2.
When the channel is activated, the TRAU activates the encoder and decoder, and inserts
TFO messages in the PCM samples on the A interface by using the bit stealing scheme.
If the TFO message acknowledgment mechanism is not established within a predefined

period, the TRAU performs the transcoding in a normal way.
If the TFO message acknowledgment mechanism is established, the TRAU rearranges the
speech frames received on the Abis interface, forms the TFO frames, and then transmits
the TFO frames to the remote TRAU. On receiving the TFO frames, the remote TRAU
processes the bits that constitute the TFO frames, forms the TRAU frames, and then
transmits the TRAU frames over the Abis interface. As the speech signals are encoded and
decoded only in the MS, this prevents repeated transcoding and can thus improve speech
quality.
29.5 Capabilities
This describes the TFO capabilities with different service types.
In the TFO, the Mean Opinion Score (MOS) of the HR services increases by 0.3-0.5, the FR
services by 0.2-0.4, and the EFR services by 0.1-0.3.
29.6 Implementation
This describes how to configure and verify TFO.
29.6.1 Configuring TFO

This describes how to configure TFO on the BSC6000 Local Maintenance Terminal.
Context
Configure TFO according to the setting of BSC Subrack Combination Type:
l
In BM/TC separate mode, the TFO should be configured in the GDPUC/GDPUX of the
GTCS. The TFO need not be configured in the GDPUX of the GMPS/GEPS.
In BM/TC together mode and that the TDM mode is applied on the Abis interface, the TFO
should be configured in the GDPUX of the GMPS/GEPS.
In A over IP mode, the TFO is not supported.
Procedure
Step 1 Configure the attributes of different boards according to the BSC subrack combination modes.
l
BM/TC separate
On the BSC Device Panel of the BSC6000 Local Maintenance Terminal, right-click the
GDPUC/GDPUX of the GTCS and select Configure Board Attributes from the shortcut
Issue 03 (2009-06-08)

29-7

29 TFO
Figure 29-3 Configuring GDPUC/GDPUX attributes
BM/TC together
On the BSC Device Panel of the BSC6000 Local Maintenance Terminal, right-click the
GDPUX of the GMPS/GEPS and select Confiugre Board Attributes from the shortcut
Figure 29-4 Configuring GDPUC attributes
29-8

Issue 03 (2009-06-08)

29 TFO
Step 2 Click Next. A dialog box is displayed, as shown in Figure 29-5.

Figure 29-5 Configuring the TFO feature
Step 3 Select Configure All and set TFO Switch to Open.

Step 4 Click Finish. The configuration is complete.
----End
29.6.2 Verifying TFO

This describes how to verify TFO on the BSC6000 Local Maintenance Terminal.
Context
Verify TFO according to the setting of BSC Subrack Combination Type:
l
In BM/TC separate mode, verify TFO of the GDPUC/GDPUX in the GTCS.
In BM/TC together mode, verify TFO of the GDPUX in the GMPS/GEPS.

NOTE
This takes the example of verifying TFO of the GDPUC in the GTCS in the BM/TC separate mode.
Procedure
Step 1 On the BSC Device Panel of the BSC6000 Local Maintenance Terminal, right-click the
GDPUC of the GTCS and selectQuery DSP Resources from the shortcut menu. A dialog box
is displayed, as shown inFigure 29-6.
Issue 03 (2009-06-08)

29-9

29 TFO
Figure 29-6 Querying DSP resources
Step 2 Click the DSP Channel/Link State. A dialog box is displayed, as shown in Figure 29-7.
29-10

Issue 03 (2009-06-08)

29 TFO
Figure 29-7 Querying DSP channel/link state
Step 3 Select the corresponding Subrack No., Slot No., and DSP No., and then click Query. If there
are TCHs whose TFO status is activated, you can infer that the TFO verification succeeds.
----End

None.
Alarms
None
Issue 03 (2009-06-08)

29-11

29 TFO
Counters
None
29.8 References
29-12
3GPP 02.53: "Digital cellular telecommunication system (Phase 2+); Tandem Free
Operation (TFO) of Speech Codecs; Service Description; Stage 1"
3GPP 03.53: "Digital cellular telecommunication system (Phase 2+); Tandem Free
Operation (TFO) of Speech Codecs; Service Description; Stage 2"
3GPP 08.62: "Inband Tandem Free Operation (TFO) of Speech Codecs; Service
Description; Stage 3"

Issue 03 (2009-06-08)

30 ICC
30
ICC
About This Chapter

30.1 Overview
This describes the definition of ICC and purposes of applying ICC.
30.2 Availability
This lists the NEs and software required for the implementation of ICC.
30.3 Impact
None.
This describes the background of ICC and the ICC algorithm developed by Huawei.
30.5 Capabilities
This describes the ICC gain.
30.6 Implementation
None.
None.
30.8 References
None.
Issue 03 (2009-06-08)

30-1

30 ICC
30.1 Overview
This describes the definition of ICC and purposes of applying ICC.
Definition
Interference Rejection Combining (ICC) is an improved RF algorithm. It helps increase the
resistance to interference and improve the voice quality.
Purposes
The purposes of applying the ICC are as follows:
l
Enhancing the capability to resist multipath attenuation
Enhancing the capability to resist co-channel interference
Enhancing the receiver sensitivity of the BTS
Terms
None.

None.
30.2 Availability
This lists the NEs and software required for the implementation of ICC.
NEs Involved
Table 30-1 lists the NEs involved in ICC.
Table 30-1 NEs involved in ICC
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 30-2 lists the versions of GBSS products that support ICC.
30-2

Issue 03 (2009-06-08)

30 ICC

Product
BTS
Version
BTS3012
BTS3012AE
DTRU
QTRU
DTRU
QTRU
BTS3006C
BTS3002E
DBS3900 GSM
BTS3900 GSM
BTS3900A GSM
BTS312
G3BTS32V302R002C07 and later releases
BTS3006A
BTS30
Miscellaneous
None.
30.3 Impact
None.

This describes the background of ICC and the ICC algorithm developed by Huawei.
Technical Description
The TX signals arrive at the main antenna and the diversity antenna through different radio paths.
This process generates combinative antenna thermal noise and co-channel interference. Noise
and interference may degrade the demodulation performance of the BTS.
From the perspective of the communication principles, there is no correlation between the main
antenna noise and the diversity antenna noise, but the correlation exists for the co-channel
interference.
The ICC technique takes into account the correlation between noises and between interference
sources. Therefore, noise and co-channel interference are suppressed, and the demodulation
performance of the BTS is enhanced.
Issue 03 (2009-06-08)

30-3

30 ICC
Introduction to ICC Algorithm

The ICC algorithm combines the main signal r1(k) and the diversity signal r2(k) to suppress noise
and interference. Figure 30-1 shows the ICC algorithm.
Figure 30-1 ICC algorithm
RX channel 1
RX signal r1 (k )
Noise and
W1
interference
S1 (k )
Noise and
interference W2
RX channel 2
RX signal r2 ( k )
TX signal x(k)
RX channel 3
RX channel 4
RX signal r3 ( k )
RX signal r4 ( k )
S2 (k )
Noise and
interference
W3
Noise and
interference
W4
y(k)
S3 (k )
S4 (k )
The TX signal x(k) arrives at the main antenna and the diversity antenna through the main
channel and the diversity channel respectively. The two RX signals are identified as r1(k) and
r2(k). After the combination of noise and interference, the two RX signals are identified as S1
(k) and S2(k).
Based on the maximum signal-to-noise ratio criterion, the ICC algorithm calculates the two
combination coefficients, W1 and W2, and yields y(k):
y(k) = W1 x S1(k) + W2 x S2(k)
The ICC algorithm developed by Huawei considers the noise and interference from the ambient
environment, and processes speech signals and interference signals based on the maximum
signal-to-noise ratio criterion. Therefore, the ICC algorithm features the high capability to resist
multipath fading and co-channel interference, and the receiver sensitivity of the BTS is also
increased.
30.5 Capabilities
Suppose there are three interference sources in the actual network. The first interference source
is 6 dB higher than the second interference source and 10 dB higher than the third source. In
addition, the first interference source is 9 dB higher than the noise power and the antenna signals
and interference are not correlated.Table 30-3 shows the ICC gain.
30-4

Issue 03 (2009-06-08)

30 ICC
Table 30-3 Estimated ICC gain in the actual network

Scenario
Gain
Two-antenna ICC
[1.5 dB, 2.0 dB]
Four-antenna ICC
[2.5 dB, 3.5 dB]
30.6 Implementation
None.

None.
Alarms
None.
Counters
None.
30.8 References
None.
Issue 03 (2009-06-08)

30-5

31 PBT
31
PBT
About This Chapter

31.1 Overview
This describes the power boost technology (PBT), which can be used to expand the radio
coverage of BTSs.
31.2 Availability
This lists the NEs, software, and licenses required for the implementation of PBT.
31.3 Impact
This describes the impact of PBT on system performance and on other features.
This describes the technical aspects of PBT. In PBT mode, one signal is divided into two signals.
The two signals are amplified and then combined into one. Thus, the transmit power is almost
doubled.
31.5 Capabilities
This describes the combination power of PBT and the capabilities of dynamic PBT.
31.6 Implementation
This describes how to configure PBT and configure dynamic PBT.
This lists the alarms and counters related to PBT.
31.8 References
None.
Issue 03 (2009-06-08)

31-1

31 PBT
31.1 Overview
This describes the power boost technology (PBT), which can be used to expand the radio
coverage of BTSs.
Definition
The PBT is a power boost technology. In PBT mode, the double-transceiver unit serves as a
single transceiver. One signal output through modulation and DA conversion is divided into two
RF signals, which then enter the power amplifier for amplification. Then, the amplified signals
are combined. As the two signals are aligned in phase, the transmit power is amplified and the
downlink signal strength is increased.
In dynamic PBT mode, the corresponding timeslots on the two TRXs of a double-transceiver
unit are set to PBT, and other timeslots are set to non-PBT. After the timeslots in PBT mode are
released, they can be set to non-PBT.
Purposes
PBT is used to expand the radio coverage of BTSs and is applicable to the areas with wide
coverage.
In PBT mode, the downlink signal strength is increased. At the same time, if the UL signals are
optimized during network construction, the overall radio coverage is expanded.
Dynamic PBT makes full use of idle timeslots and expands the coverage in the areas with weak
signals, such as at cell edges, indoors, or in cars. Based on actual network conditions, adjustments
can be made to achieve the balance between capacity and coverage.
Terms
None.

Acronym and
Abbreviation
Full Spelling
PBT
Power Booster Technology
DTRU
Double TRansceivers Unit
31.2 Availability
This lists the NEs, software, and licenses required for the implementation of PBT.
NEs Involved
Table 31-1 describes the NEs involved in PBT.
31-2

Issue 03 (2009-06-08)

31 PBT
Table 31-1 NEs involved in PBT

MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 31-2 lists the versions of the GBSS products that support PBT.
Product
Version
BSC
BSC6000
BTS
BTS3012
DTRU
BTS3000V100R001C01 and later

releases
BTS3012AE
DTRU

releases
BTS3006C
Not supported
BTS3002E
Not supported
DBS3900 GSM

releases
BTS3900 GSM

releases
BTS3900A GSM

releases
Table 31-3 lists the versions of the GBSS products that support dynamic PBT.
Product
Issue 03 (2009-06-08)
Version
BSC
BSC6000
BTS
BTS3012
DTRU

releases
BTS3012AE
DTRU

releases

31-3

31 PBT
Product
Version
BTS3006C
Not supported
BTS3002E
Not supported
DBS3900 GSM
Not supported
BTS3900 GSM
Not supported
BTS3900A GSM
Not supported
Miscellaneous
PBT and dynamic PBT are controlled by the licenses.
31.3 Impact
This describes the impact of PBT on system performance and on other features.

In PBT mode, one double-transceiver unit in the BTS3012/BTS3012AE serves as one TRX.
Thus, a fully configured cabinet provides only six TRXs.
In dynamic PBT mode, the corresponding timeslots of the two TRXs in one double-transceiver
unit form a channel group. After dynamic PBT is adopted, these channel groups are restored to
independent channels. After channel groups are released, the overall capacity is the same as that
in non-PBT mode.

None.

This describes the technical aspects of PBT. In PBT mode, one signal is divided into two signals.
The two signals are amplified and then combined into one. Thus, the transmit power is almost
doubled.
PBT
Physically, after multiple signals that have the same phase and frequency are superposed, signals
can be strengthened. This principle is used in PBT. In PBT mode, one signal is divided into two
signals, and then the two signals are amplified. After that, the two signals are superposed in the
same phase and with the same frequency. The two signals are aligned in phase, so their
combination is functionally equivalent to power amplification.
Figure 31-1 shows the working principle of PBT in the DTRU.
31-4

Issue 03 (2009-06-08)

31 PBT
Figure 31-1 Working principle of PBT in the DTRU

TX1
Control unit
TX
TRX0
TCOM
Combiner
TX2
TX
TRX1
The signal from TRX0 is divided into two signals by a divider. Then, the two signals enter RF
units TX1 and TX2 respectively. After being amplified by the RF units, the two signals are
combined by the combiner. Then, the combined RF signals are transmitted through the TCOM
port.
When PBT is adopted, the uplink coverage may be insufficient if the UL signals are not amplified
or the uplink receiver sensitivity is not improved. The UL coverage and the DL coverage may
be imbalanced. Thus, measures should be taken to improve the receive quality of UL signals.
You can use one of the following ways to improve the receive quality of UL signals:
l
Configure 33 Four-Way Receive Diversity.
Configure a tower mounted amplifier (TMA).
The TMA is a low noise amplifier module that is installed on a tower. After receiving UL signals
from the antenna, the TMA amplifies the signals and then transmits them to the feeder. Thus,
the receiver sensitivity of the BTS is improved and the UL coverage is expanded. In addition,
when the TMA is used, the transmit power of an MS is reduced and the speech quality is
improved.
A triplex TMA is commonly used.
A triplex TMA consists of the following parts:
l
Triplex filter
Low noise amplifier
Feeder
A triplex TMA processes signals as follows:

1.
The triplex filter filters the signals from the antenna to remove the out-band interference.
2.
The low noise amplifier amplifies the weak signals.
Issue 03 (2009-06-08)

31-5

31 PBT
3.
The feeder transmits the amplified signals to the indoor units.
As shown in Figure 31-2, the triplex TMA should be installed close to the antenna.
Figure 31-2 Installing the TMA
1
2
(1) Antenna
(2) Antenna support
(3) Jumper
(4) TMA
(5) Feeder
(6) Cabinet
Dynamic PBT
Dynamic PBT is mainly applicable to concentric cells. If the downlink coverage in the overlaid
subcell is restricted, continuous coverage is unavailable, and the capacity of the underlaid subcell
is small. Thus, the underlaid subcell may be congested and the overlaid subcell may be idle. In
PBT mode, only one TRX in a double-transceiver unit is used and the TRX utilization is low.
Dynamic PBT supports timeslot-based PBT. In other words, two TRXs in a double-transceiver
unit work independently except in some specific timeslots. Dynamic conversion is performed
between channel groups and common channels. This keeps a balance among cost, capacity, and
coverage. The resource utilization is increased and the coverage problem is solved to some
extent.
NOTE
When the DTRU works in dynamic PBT mode, the channels with the same timeslot number on the two
TRXs of the same DTRU form a PBT channel group. The two channels must be TCHs (TCHF or TCHH).
The channel with a smaller TRX number is the primary channel, and the channel with a greater TRX number
is the secondary channel. The primary channel and the secondary channel are the channels with the same
timeslot number on the same DTRU.
The BCCHs, SDCCHs, PDCHs, and CBCHs cannot form a channel group. They can only be used as
independent channels.
During channel assignment, the BSC searches for the optimal channels. After dynamic PBT is
enabled, the BSC determines whether the optimal channels can form a PBT channel group if the
PBT channel group should be assigned. If a PBT channel group can be formed, the BSC blocks
31-6

Issue 03 (2009-06-08)

31 PBT
the secondary channel. Then the BSC assigns the channel group to the call. If the optimal
channels cannot form a channel group, the BSC regards the channels as independent channels
and assigns them to the call. If the optimal channels can form a channel group but one of them
is occupied by an MS, the BSC attempts to hand over the MS to another channel. After the
channel is idle, a channel group is formed and then assigned to the call.
In dynamic PBT mode, the downlink-limited handover decision algorithm is added to determine
whether the downlink signal strength is limited. If the downlink signal strength is limited and
the serving cell supports dynamic PBT, the call is handed over to an available channel group. If
one of the two channels with the same timeslot number on the same DTRU is occupied by the
call, the MS on the other channel should be handed over to other idle channel.
When the downlink signal strength is increased to a certain level, the PBT channel group is not
required. The BSC divides the channel group into two independent channels and maintains the
call on the primary channel. In addition, the BSC releases the secondary channel to increase the
capacity of the cell.
NOTE
After dynamic PBT is enabled, the BSC reserves most possible channel pairs that can form channel groups
during the assignment of normal independent channels.
With dynamic PBT used in the overlaid subcell, the coverage of the overlaid subcell is increased
through the handover of edge calls to the overlaid subcell. This helps to balance the traffic in
the overlaid subcell and that in the underlaid subcell, and also increase the success rate of
handover from the underlaid subcell to the overlaid subcell.
Dynamic PBT is implemented through software. That is, the hardware connections of the BTS
in dynamic PBT are the same as those in PBT, and only software upgrade is required.
31.5 Capabilities
This describes the combination power of PBT and the capabilities of dynamic PBT.
Table 31-4 and Table 31-5 describe the output power in PBT mode.
Table 31-4 Output power of the BTS3012/BTS3012AE in PBT mode
Modulation
Mode
Issue 03 (2009-06-08)
Output Power of a Single TRX in DTRU
Output Power in PBT

Mode
Specification 1
Specification 2
GMSK
40 W (46 dBm)
60 W (47.78 dBm)
100 W (49 dBm)
8PSK
40 W (46 dBm)
40 W (46 dBm)
60 W (47.78 dBm)

31-7

31 PBT
Table 31-5 Output power of the DBS3900 GSM in PBT mode

Output Power of a Single TRX in
RRU (Non-Combination Mode)
Output Power in PBT Mode
900 M
1800 M
900 M
1800 M
GMSK
30 W (44.77 dBm)
20 W (43
dBm)
40 W (46 dBm)
30 W (44.77
dBm)
8PSK
20 W (43 dBm)
15 W (41.76
dBm)
25 W (43.98 dBm)
20 W (43 dBm)
Modulati
on Mode
Capabilities of dynamic PBT: If a channel group works in the same manner as that in PBT mode,
the output power is the same as the combination power in PBT mode. That is, the power is
amplified after signal combination. If a channel works in independent mode, the power is
transmitted in wideband combination mode.
31.6 Implementation
This describes how to configure PBT and configure dynamic PBT.
31.6.1 Configuring PBT

This describes the hardware configuration for PBT. It also describes how to configure PBT on
the BSC6000 Local Maintenance Terminal.
Prerequisite
1.
In the Resource control items column of BSC6000V900R008 Exceptional Commercial

License Application Template, locate the Number of multi-transceivers supporting PBT
transmit row and specify a value in the cell corresponding to the Resource number
column. The value indicates the number of DTRUs that support PBT.
2.
the BSC License.
Context
The DTRUs of the BTS3012 are classified into two types: DTRU (type A) and DTRU (type B).
The two types of DTRUs have different panels. Therefore, the cable connections are also
different.
The TRX attributes and antenna feeder attributes for the DBS3900 GSM are set on the BSC
side. The method of configuring PBT for the DBS3900 GSM is the same as that for the BTS3012/
BTS3012AE.
Procedure
l
31-8
Configure the hardware for PBT.

Issue 03 (2009-06-08)

31 PBT
Figure 31-3 and Figure 31-4 show the connections between the DTRU and the DDPU in
PBT mode.
Issue 03 (2009-06-08)

31-9

31 PBT
Figure 31-3 Connections between the DTRU (type A) and the DDPU in PBT mode
DDPU
RUN
ALM
VSWRA
VSWRB
COM
POWER
RXA1
RXA2 TXA
RXA3
RXA4
RXB1
RXB2
RXB3 TXB
RXB4
DTRU
TX1
IN1
TCOM
IN2
TX2
RUN
ACT
ALM
RF_IND
RS T
RXM1
RXD1
RXM2
RXD2
POWER
31-10

Issue 03 (2009-06-08)

Issue 03 (2009-06-08)

31 PBT
31-11

31 PBT
Figure 31-4 Connections between the DTRU (type B) and the DDPU in PBT mode
DDPU
RUN
ALM
VSWRA
VSWRB
COM
POWER
RXA1
RXA2 TXA
RXA3
RXA4
RXB1
RXB2
RXB3 TXB
RXB4
DTRU
TX1
TCOM
TX2
RUN
ACT
ALM
RF_IND
RS T
RXM1
RXD1
RXM2
RXD2
POWER
31-12

Issue 03 (2009-06-08)

31 PBT
For details on the descriptions of the ports on the DTRU (type A), DTRU (type B), and
DDPU, refer to Table 2 and Table 3 in LEDs and Ports on the DTRU, and Table 2 in LEDs
and Ports on the DDPU.
l
Configure the data.

1.

Terminal, right-click the target TRX and then choose Configure TRX Attributes
from the shortcut menu.
2.
In the displayed dialog box, click Set TRX Attributes.
3.
In the displayed dialog box, click the Device Attributes tab. Set Send Mode to
PBT, as shown in Figure 31-5.
Figure 31-5 Configuring TRX attributes
----End
31.6.2 Configuring Dynamic PBT

This describes how to configure dynamic PBT on the BSC6000 Local Maintenance
Terminal.
Prerequisite
Issue 03 (2009-06-08)

31-13

31 PBT
1.
In the License control items of the BSC6000V900R008 Exceptional Commercial License

Application Template, locate the Number of TRXs that support dynamic PBT row and
specify a value in the cell corresponding to the Resource number column. The value
indicates the number of DTRUs that support dynamic PBT.
2.
the BSC License.
Context
The hardware configuration for dynamic PBT is the same as that for PBT. For details, refer to
31.6.1 Configuring PBT.
Procedure
the target cell. Then, choose Configure Cell Attributes from the shortcut menu.
Step 2 In the displayed dialog box, double-click the target cell. Then, click Next.
Step 3 In the displayed dialog box, click Configure Cell Attributes. A dialog box is displayed, as
31-14

Issue 03 (2009-06-08)

31 PBT
Step 4 In the dialog box shown in Figure 31-6, set Cell Type to Concentric cell. Then, click Channel
Management. A dialog box is displayed, as shown in Figure 31-7.
Issue 03 (2009-06-08)

31-15

31 PBT
Figure 31-7 Set Channel Parameter dialog box
Step 5 Set Dynamic Transmission Diversity (PBT) Supported to DPBT. Then, click OK. The dialog
box shown in Figure 31-6 is displayed.
Step 6 Select the TRXs for the overlaid cell in the Assigned TRXs area. Then, click TRX Config.
Step 7 In the displayed dialog box, click the Device Attributes tab. set Send Mode to DPBT, as shown
in Figure 31-8.
31-16

Issue 03 (2009-06-08)

31 PBT
Figure 31-8 Configuring TRX attributes
Step 8 Click OK until the configuration is complete.

----End

This lists the alarms and counters related to PBT.
Alarms
Table 31-6 lists the alarms related to the PBT.
Table 31-6 Alarms
Issue 03 (2009-06-08)
Alarm ID
Alarm Name
4110
TRX Power Decrease Alarm
4112
Close HPA Alarm
4140
PAU Temperature Alarm
4144
TRX VSWR Alarm

31-17

31 PBT
Counters
None.
31.8 References
None.
31-18

Issue 03 (2009-06-08)

32 Transmit Diversity
32
Transmit Diversity
About This Chapter

32.1 Overview
This describes the definitions and purposes of transmit diversity and dynamic transmit diversity.
Transmit diversity is a method to manually realize the multipath, thus improving downlink signal
quality.
32.2 Availability
This lists the NEs, software, and licenses required for the implementation of transmit diversity
and dynamic transmit diversity.
This describes the technical aspects of transmit diversity and dynamic transmit diversity.
Multipath attenuation is one of the characteristics of radio channels. Through the transmit
diversity and dynamic transmit diversity techniques, the signal attenuation can be minimized.
32.4 Implementation
This describes how to configure transmit diversity and dynamic transmit diversity.
This lists the alarms and counters related to transmit diversity.
32.6 References
None.
Issue 03 (2009-06-08)

32-1

32.1 Overview
This describes the definitions and purposes of transmit diversity and dynamic transmit diversity.
Transmit diversity is a method to manually realize the multipath, thus improving downlink signal
quality.
Definition
In transmit diversity mode, the baseband signal of one MS is transmitted on two RF channels.
As there is no correlation between two antennas, the problems of dramatic change of signal level
and QoS decrease due to multipath propagation are solved, thus improving the downlink
coverage performance.
In dynamic transmit diversity mode, the corresponding timeslots of the two TRXs in one doubletransceiver unit are set to transmit diversity, and other timeslots are set to non-transmit diversity.
After the timeslots in transmit diversity mode are released, they can be set to non-transmit
diversity.
Purposes
The transmit diversity technique can improve the downlink signal quality, thus meeting the
demanding requirements for radio communications in certain cases.
Dynamic transmit diversity makes full use of idle timeslots and expands the coverage in the
areas with weak signals, such as at cell edges, indoors, or in cars. Based on actual network
conditions, adjustments can be made to achieve the balance between capacity and coverage. The
resource utilization is increased and good quality services can be provided if required.
Terms
None.

None.
32.2 Availability
This lists the NEs, software, and licenses required for the implementation of transmit diversity
and dynamic transmit diversity.
NEs Involved
Table 32-1 describes the NEs involved in transmit diversity and dynamic transmit diversity.
Table 32-1 NEs involved in transmit diversity
32-2
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR

Issue 03 (2009-06-08)

MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l : not involved
l : involved
Software Releases
Table 32-2 lists the software versions of the GBSS products that support transmit diversity.
Product
Version
BSC
BSC6000
BTS
BTS3012
DTRU

releases
BTS3012AE
DTRU

releases
BTS3006C

releases
BTS3002E

releases
DBS3900 GSM

releases
BTS3900 GSM

releases
BTS3900A GSM

releases
Table 32-3 lists the software versions of the GBSS products that support dynamic transmit
diversity.
Product
Issue 03 (2009-06-08)
Version
BSC
BSC6000
BTS
BTS3012
DTRU

releases
BTS3012AE
DTRU

releases

32-3

Product
Version
BTS3006C

releases
BTS3002E

releases
DBS3900 GSM
Not supported
BTS3900 GSM
Not supported
BTS3900A GSM
Not supported
Miscellaneous
The number of TRXs that support transmit diversity or dynamic transmit diversity is determined
by the license.

This describes the technical aspects of transmit diversity and dynamic transmit diversity.
Multipath attenuation is one of the characteristics of radio channels. Through the transmit
diversity and dynamic transmit diversity techniques, the signal attenuation can be minimized.
Transmit Diversity
In the radio propagation environment, TX signals may be adversely affected by shadow
attenuation, which is caused by buildings and other obstacles. TX signals arrive at the receive
end in various ways, such as line-of-sight (LOS), reflections, and dispersions. As the MS moves
around, Rayleigh attenuation occurs because the TX signals traveling through various paths are
combined. Rayleigh attenuation causes a rapid fluctuation of the signal amplitude. Therefore,
the signal quality is severely affected.
Shadow attenuation and Rayleigh attenuation severely degrade the quality of RX signals. The
two types of attenuation are major factors in the vulnerable radio link of the mobile
communications.
The transmit diversity technology uses the non-correlation feature between two routes of signals,
that is, the two routes of signals have different deep fading points, to improve the quality of the
received signals, thus conquering multipath fading. In transmit diversity mode, one baseband
signal is transmitted through two RF channels. The signal combination in the multipath
transmission is optimized. Thus, the impact of Rayleigh attenuation on the MS is reduced.
The gain of transmit diversity is high in the scenarios with obvious multipath effects. In the static
channel model (such as grassland and sea), transmit diversity cannot bring about obvious
diversity gain,
Figure 32-1 shows the transmit diversity of a double-transceiver unit. The signal from TRX0 is
divided into two signals by a divider. Then, the two signals enter RF units TX1 and TX2
respectively. The signals are amplified by the RF units and then transmitted to the radio channels
over the antenna.
32-4

Issue 03 (2009-06-08)

Figure 32-1 Transmit diversity
NOTE
In transmit diversity mode, one double-transceiver unit serves as only one TRX.
Dynamic Transmit Diversity

Dynamic transmit diversity is mainly applicable to concentric cells. If the downlink coverage
in the overlaid subcell is restricted, continuous coverage is unavailable, and the capacity of the
underlaid subcell is small. Thus, the underlaid subcell may be congested and the overlaid subcell
may be idle. In transmit diversity mode, only one TRX in a double-transceiver unit is used and
the TRX utilization is low.
Dynamic transmit diversity supports timeslot-based transmit diversity. In other words, two
TRXs in a double-transceiver unit work independently except in some specific timeslots.
Dynamic conversion is performed between channel groups and common channels. This keeps
a balance among cost, capacity, and coverage.
NOTE
When a double-transceiver unit works in dynamic transmit diversity mode, the channels with the same
timeslot number on the two TRXs in one double-transceiver unit form a transmit diversity channel group.
The two channels must be TCHs (TCHF or TCHH). The channel with a smaller TRX number is the primary
channel, and the channel with a greater TRX number is the secondary channel. The primary channel and
the secondary channel are the channels with the same timeslot number on the one double-transceiver unit.
BCCHs, SDCCHs, PDCHs, and CBCHs cannot form a channel group. They can only be used as
independent channels.
During channel assignment, the BSC searches for the optimal channels. After dynamic transmit
diversity is enabled, the BSC determines whether the optimal channels can form a transmit
diversity channel group if the transmit diversity channel group should be assigned. If a transmit
diversity channel group can be formed, the BSC blocks the secondary channel. Then, the BSC
assigns the channel group to the call. If the optimal channels cannot form a channel group, the
BSC regards the channels as independent channels and assigns them to different calls. If the
Issue 03 (2009-06-08)

32-5

optimal channels can form a channel group but one of them is occupied by an MS, the BSC
attempts to hand over the MS to another channel. After the channel is idle, a channel group is
formed and then assigned to the call.
In dynamic transmit diversity mode, the downlink-limited handover decision algorithm is added
to determine whether the downlink signal strength is limited. If the downlink signal strength is
limited and the serving cell supports dynamic transmit diversity, the call is handed over to an
available channel group. If one of the two channels with the same timeslot number on one doubletransceiver unit is occupied by the call, the MS on the other channel should be handed over to
another idle channel.
When the downlink signal strength is increased to a certain level, the transmit diversity channel
is not required. The BSC divides the channel group into two independent channels and maintains
the call on the primary channel. At the same time, the BSC releases the secondary channel to
increase the capacity of the cell.
NOTE
After dynamic transmit diversity is enabled, the BSC reserves most possible channel pairs that can form
channel groups when assigning common independent channels.
With dynamic transmit diversity used in the overlaid subcell, the coverage of the overlaid subcell
is increased. That is, the edge calls can be handed over to the overlaid subcell. This keeps a
traffic balance between the overlaid and underlaid subcell.
Dynamic transmit diversity is implemented through software. That is, the hardware connections
of the BTS in dynamic transmit diversity are the same as those in transmit diversity, and only
software upgrade is required.
32.4 Implementation
This describes how to configure transmit diversity and dynamic transmit diversity.
32.4.1 Cable Connections (Transmit Diversity)

This describes how to connect the cables in transmit diversity mode.
Procedure
l
32-6
The blue lines in Figure 32-2 show the cable connections between the DTRU and the DDPU
in the BTS3012/BTS3012AE in transmit diversity mode.

Issue 03 (2009-06-08)

Figure 32-2 Cable connections between the DTRU and the DDPU in transmit diversity
mode
DDPU
RUN
ALM
VSWRA
VSWRB
COM
POWER
RXA1
RXA2 TXA
RXA3
RXA4
RXB1
RXB2
RXB3 TXB
RXB4
DTRU
TX1
TCOM
TX2
RUN
ACT
ALM
RF_IND
RS T
RXM1
RXD1
RXM2
RXD2
POWER
Issue 03 (2009-06-08)

32-7

For details on how to connect the RF cables in the BTS3012/BTS3012AE, refer to

Installing the RF Signal Cables of the BTS3012/BTS3012AE.
For details on the descriptions of the ports on the DTRU and DDPU, refer to LEDs and
Ports on the DTRU and LEDs and Ports on the DDPU.
Figure 32-3 shows the cable connections between the DDPM and the DDRM in the
BTS3006C in transmit diversity mode.
Figure 32-3 cable connections between the DDPM and the DDRM in the BTS3006C in
transmit diversity mode.
DDRM
DSEM
TX1-
TX2-
DMCM
DSEM
DDPM
TXB TXA
RXB1
RUN
RXA1
ALM
RUN/SLPACTALMRF_IND
RXM1RXD1-
VSWR A
VSWRB
RXB2
RXA2
RXB3
RXA3
RXM2RXD2FAN-
ANTB ANTA
32-8
Figure 32-4 shows the cable connections between the DDPM and the DDRM in the
BTS3002E in transmit diversity mode.

Issue 03 (2009-06-08)

Figure 32-4 cable connections between the DDPM and the DDRM in the BTS3002E in
transmit diversity mode
DDPM
DDRM
DPSM
TX1TXB TXA
RXB1
RUN
ALM
RXA1
TX2-
VSWRA
VSWRB
RXB2
RXA2
RXB3
RXA3
ANTB ANTA
DMCM
DATM
FAN-
Issue 03 (2009-06-08)
DOOR
For details on how to connect the RF cables in the BTS3006C/BTS3002E, refer to

Installing the RF Signal Cables of the BTS3006C/BTS3002E.
For details on the descriptions of the ports on the DDRM and DDPM, refer to LEDs
and Ports on the DDRM and LEDs and Ports on the DDPM.
Figure 32-5 shows the cable connections in the DBS3900 GSM in transmit diversity mode.

32-9

Figure 32-5 Cable connections in the DBS3900 GSM in transmit diversity mode
ANT Antenna
ANT_TX/RXA
ANT_TX/RXB
RX_IN/OUT
RRU0
CPRI_E
CPRI_W
CPRI0
CPRI5
BBU
For details on how to connect the RF cables in the DBS3900 GSM, refer to Installing
the RF Cables of the RRU.
For details on the descriptions of the ports on the RRU and BBU, refer to Ports of the
RRU Module and Ports of the BBU.
----End
32.4.2 Configuring Transmit Diversity

This describes how to configure transmit diversity on the BSC6000 Local Maintenance
Terminal.
Prerequisite
32-10
1.
In the Resource control items column of BSC6000V900R008 Exceptional Commercial

License Application Template, locate the Number of multi-transceivers supporting
diversity transmit row and specify a value in the cell corresponding to the Resource
number column. The value indicates the number of double-transceiver units that support
transmit diversity.
2.
the BSC License.
Issue 03 (2009-06-08)

Procedure
the target TRX and then select Configure TRX Attributes from the shortcut menu.
Step 2 In the displayed dialog box, click Set TRX Attributes. A dialog box is displayed. Select the
Device Attributes tab page, as shown in Figure 32-6.
Figure 32-6 Setting DTRU transmit diversity mode
Step 3 Set Send Mode to Diversity Transmitter.

Step 4 Click OK. The configuration is complete.
NOTE
In the case of transmit diversity, one double-transceiver unit serves as one TRX.
----End
32.4.3 Configuring Dynamic Transmit Diversity

This describes how to configure dynamic transmit diversity on the BSC6000 Local
Prerequisite
Issue 03 (2009-06-08)

32-11

1.
In the License control items column of the BSC6000V900R008 Exceptional Commercial

License Application Template, locate the Number of TRXs that support dynamic PBT
row and specify a value in the cell corresponding to the Resource number column. The
value indicates the number of TRXs that support dynamic PBT.
2.
the BSC License.
Procedure
the target cell. Then, choose Configure Cell Attributes from the shortcut menu.
Step 2 In the displayed dialog box, double-click the target cell. Then, click Next.
Step 3 In the displayed dialog box, click Set Cell Properties. A dialog box is displayed, as shown in
Figure 32-7.
32-12

Issue 03 (2009-06-08)

Step 4 In the dialog box shown in Figure 32-7, set Cell Type to Concentric cell. Then, click Channel
Management. A dialog box is displayed, as shown in Figure 32-8.
Step 5 Set Dynamic Transmission Diversity (PBT) Supported to DDIVERSITY. Then, click OK.
The dialog box shown in Figure 32-7 is displayed.
Step 6 Select the target TRX of the concentric cell in the Assigned TRXs area. Then, click TRX
Config. A dialog box is displayed. Click the Device Attributes tab, and set Send Mode to
DDIVERSITY, as shown in Figure 32-9.
Issue 03 (2009-06-08)

32-13

Figure 32-9 Configure TRX Attributes dialog box

----End

This lists the alarms and counters related to transmit diversity.
Alarms
Table 32-4 lists the alarms related to transmit diversity.
Table 32-4 Alarms related to transmit diversity
32-14
Alarm ID
Alarm Name
4112
Close HPA Alarm
4140
PAU Temperature Alarm
4144
TRX VSWR Alarm
4196
SEND DIV Channel Alarm

Issue 03 (2009-06-08)

Counters
None.
32.6 References
None.
Issue 03 (2009-06-08)

32-15

33
33 Four-Way Receive Diversity
Four-Way Receive Diversity
About This Chapter

33.1 Overview
This describes the definition and purposes of the four-way receive diversity. The four-way
receive diversity combines the four-way RX signals to optimize the uplink signals.
33.2 Availability
This lists the NEs, software, and license required for implementing the four-way receive
diversity.
This describes the technical aspects of the four-way receive diversity. The radio channel is a
type of multipath fading channel. Through the four-way receive diversity technique, multipath
attenuation can be suppressed and the power gain of the uplink signals on the radio channel and
the receiver sensitivity can be improved.
33.4 Capabilities
33.5 Implementation
This describes how to install the hardware equipment and configure the four-way receive
diversity.
This lists the alarms related to four-way receive diversity.
33.7 References
None.
Issue 03 (2009-06-08)

33-1

33.1 Overview
This describes the definition and purposes of the four-way receive diversity. The four-way
receive diversity combines the four-way RX signals to optimize the uplink signals.
Definition
The four-way RX signals are sent to one TRX simultaneously. Through the diversity
combination technique, the uplink receiver sensitivity is improved.
Purposes
The four-way receive diversity technique optimizes uplink signals to meet the demanding
requirements for radio communications in certain cases and to improve the uplink performance
in wide coverage scenarios.
Terms
None.

Full Spelling
ICC
Interference Cancellation Combining
MRC
Maximal Ratio Combining
33.2 Availability
This lists the NEs, software, and license required for implementing the four-way receive
diversity.
NEs Involved
Table 33-1 lists the network elements involved in the four-way receive diversity.
Table 33-1 Network elements involved in the four-way receive diversity
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
33-2

Issue 03 (2009-06-08)

Software Releases
Table 33-2 lists the NEs and software versions that support four-way receive diversity.
Product
Version
BSC
BSC6000
BTS
BTS3012
DTRU

releases
BTS3012AE
DTRU

releases
BTS3006C

releases
BTS3002E

releases
BTS3900 GSM

releases
BTS3900A GSM

releases
Miscellaneous
Four-way receive diversity is controlled by the license.

This describes the technical aspects of the four-way receive diversity. The radio channel is a
type of multipath fading channel. Through the four-way receive diversity technique, multipath
attenuation can be suppressed and the power gain of the uplink signals on the radio channel and
the receiver sensitivity can be improved.
In radio communication environment, the TX signals tend to be affected by the shadow fading,
buildings, and landforms. The TX signals from the MS arrive at the BTS in various ways, such
as line-of-sight (LOS), reflections, and dispersions. As the MS moves around, the Rayleigh
fading is generated because the TX signals traveling through various paths are combined. In the
Rayleigh fading, the signal amplitude changes very quickly. The four-way receive diversity
technique can be used to suppress this type of fading.
Four-way receive diversity means that four RX paths receives the same signal separately. The
received signals are combined into one, and thus the uplink gain is enhanced. To ensure that the
diversity antennas receives signals separately from each other, the distance between diversity
antennas must be greater than 10 times the radio signal wavelength or the polarization diversity
is adopted.
Figure 33-1 shows the principles of four-way receive diversity of the DTRU. The four RX
signals (RXM1, RXD1, RXM2, and RXD2) are sent to one TRX in the DTRU for combination.
Issue 03 (2009-06-08)

33-3


NOTE
With four-way receive diversity, only one TRX in the DTRU can be used.
Figure 33-1 Working principles of the four-way receive diversity
TX1
TX
IN1
TCOM
Combiner
TRX0
IN2
TX2
RXM1
RXD1
Divider
Divider
TX
RXM2
TRX1
RXD2
There are two types of four-way receive diversity techniques: Interference Cancellation
Combining (ICC) and Maximal Ratio Combining (MRC). MRC is the best in the case that there
is no interference and noise is restricted. MRC does not consider the correlation of interference
on combining diversities. In the actual network, the interference on different diversity antennas
comes from the interference signals of the same source. Therefore, the interference has a certain
correlation. ICC uses this correlation to eliminate some interference. ICC is a technique
developed based on MRC.
When the DTRU adopts the four-way receive diversity technique, the TX signals arrive at the
diversity antennas through different radio paths. This process generates combinative antenna
thermal noise and co-channel interference, thus affecting the demodulation performance of the
BTS. The noise of the diversity antennas has no correlation, but the co-channel interference has
a certain correlation. The ICC technique takes into account the correlation between noises and
between interference sources. Therefore, noise and co-channel interference are suppressed, and
the demodulation performance of the BTS is enhanced.
The ICC algorithm combines the diversity signals r1(k), r2(k), r3(k), and r4(k) to suppress noise
and interference. Figure 33-2 shows the principles of the ICC algorithm.
33-4

Issue 03 (2009-06-08)

Figure 33-2 ICC algorithm
RX channel 1
RX signal r1 (k )
Noise and
W1
interference
S1 (k )
Noise and
interference W2
RX channel 2
RX signal r2 ( k )
TX signal x(k)
RX channel 3
RX channel 4
RX signal r3 ( k )
RX signal r4 ( k )
S2 (k )
Noise and
interference
W3
Noise and
interference
W4
y(k)
S3 (k )
S4 (k )
The ICC algorithm procedure shown in Figure 33-2 is described as follows:

1.
The TX signal x(k) arrives at the diversity antennas through four receive paths. Then, the
signals are marked r1(k), r2(k), r3(k), and r4(k). With interference and noise added, the
signals are marked S1(k), S2(k), S3(k), and S4(k).
2.
Based on the maximum signal-to-noise ratio criterion, calculate the adaptive combining
coefficients W1, W2, W3, and W4 and obtain the output signal value through the formula:
y(k) = W1 x S1(k) + W2 x S2(k) + W3 x S3(k) + W4 x S4(k).
NOTE
When W1, W2, W3, and W4 are equal to 1, y(k) is the output signal value calculated through the MRC
algorithm.
The four receive paths shown in Figure 33-2 correspond to two pairs of main/diversity paths.
Huawei four-way receive diversity algorithm supports the MRC algorithm and the ICC algorithm
with blind detection. The ICC algorithm with blind detection prevents negative gain relative to
the MRC algorithm when the ICC algorithm is used in the scenario with no interference and
restricted noise. The ICC algorithm with blind detection is scenario-adaptive and can determine
the scenario of RX signals on each timeslot.
l
For the interference-restricted scenario, the ICC algorithm is used.
For the noise-restricted scenario, the MRC algorithm is used.
The ICC algorithm with blind detection processes useful signals and interference signals based
on the maximum signal-to-noise ratio criterion. Therefore, the ICC algorithm features the high
capability to resist multipath fading and co-channel interference, and the receiver sensitivity is
improved.
33.4 Capabilities
Issue 03 (2009-06-08)

33-5

Assume that there are three interference sources in the actual network. The first interference
source is 6 dB higher than the second one and 10 dB higher than the third one. In addition, the
first interference source is 9 dB higher than the noise power . Table 33-3 lists the ICC gain.
Table 33-3 ICC gain relative to the MRC gain
Scenario
Gain
Two-antenna ICC
[1.5 dB, 2.0 dB]
Four-antenna ICC
[2.5 dB, 3.5 dB]
33.5 Implementation
This describes how to install the hardware equipment and configure the four-way receive
diversity.
33.5.1 Installing Hardware (Four-Way Receive Diversity)

This describes how to install the hardware and connect the cables in four-way receive diversity
mode.
Procedure
Installing the RF Signal Cables of the BTS3012/BTS3012AE shows the procedure for hardware
installation in four-way receive diversity mode. This takes the BTS3012/BTS3012AE as an
example.
The red lines in Figure 33-3 shows the connection between the DTRU and the DDPU in fourway receive diversity mode.
33-6

Issue 03 (2009-06-08)

Figure 33-3 Connection between the DTRU and the DDPU in four-way receive diversity mode
DDPU
DDPU
RUN
ALM
VSWRA
VSWRB
RUN
ALM
VSWRA
VSWRB
COM
COM
POWER
POWER
RXA1
RXA1
RXA4
RXA4
RXB1
RXB1
RXB2
RXB2
RXB3 TXB
RXB3 TXB
RXB4
RXB4
DTRU
DTRU
TX1
TX1
TCOM
TCOM
TX2
TX2
RXA2 TXA
RXA3
RXA2 TXA
RXA3
RUN
ACT
ALM
RF_IND
RUN
ACT
ALM
RF_IND
RS T
RS T
RXM1
RXM1
RXD1
RXD1
RXM2
RXM2
RXD2
RXD2
POWER
POWER
Table 33-4 Description of ports on the DTRU
Issue 03 (2009-06-08)
Port
Type
Description
TX1
N female connector
TX1 output

33-7

Port
Type
Description
TCOM
N female connector
Combines and exports signals from TX1 and TX2

or exports PBT combined signals.
TX2
N female connector
TX2 output
RXM1
SMA female connector
Main receive port of TRX 1 or diversity receive

port 1 of TRX 1
RXD1
Diversity receive port of TRX 1 or diversity

receive port 2 of TRX 1
RXM2
Main receive port of TRX 2 or diversity receive

port 3 of TRX 1
RXD2
Diversity receive port of TRX 2 or diversity

receive port 4 of TRX 1
PWR
3V3 power connector
Power input
Table 33-5 Description of ports on the DDPU
33-8
Port
Type
Description
COM
DB26 female connector
Receives control signal, communication signal,

clock signal, and rack number signal from the
DCTB of the BTS3012.
Receives control signal, communication signal,

and clock signal from the DSCB of the
BTS3012AE.
POWER
3V3 power connector
Power input
TXA
N female connector
Combined TX input from the DTRU to the DCOM
TXB
N female connector
Combined TX input from the DTRU to the DCOM
RXA1
Main output port for route 1
RXA2
RXA3
RXA4
RXB1
Diversity output port for route 1
RXB2
RXB3
RXB4

Issue 03 (2009-06-08)

Port
Type
Description
ANTA
DIN female connector
Connects to the BTS3012 indoor 1/2-inch

jumper or the Bias-Tee.
Connects to the BTS3012AE indoor 1/4-inch

Connects to the BTS3012 indoor 1/2-inch

Connects to the BTS3012AE indoor 1/4-inch

ANTB
DIN female connector
----End
33.5.2 Configuring Four-Way Receive Diversity

This describes how to configure four-way receive diversity on the BSC6000 Local Maintenance
Terminal or on the Local Maintenance Terminal.
Prerequisite
1.
Apply for the license for four-way receive diversity. In the BSC6000V900R008 Exceptional
Commercial License Application Template, specify a value of the Resource number
corresponding to the Number of multi-transceiver unit which Receiver is Four
Diversity Receiver row in the Resource control items column. The value indicates the
number of multi-transceiver units that support four-way receive diversity.
2.
the BSC License.
Procedure
the target TRX and then select Configure TRX Attributes from the shortcut menu.
Step 2 In the displayed dialog box, click Set TRX Attributes. A dialog box is displayed. Select the
Device Attributes tab page, as shown in Figure 33-4.
Set Receive Mode to Four Diversity Receiver.
Issue 03 (2009-06-08)

33-9

Figure 33-4 Setting DTRU four-way receive diversity mode
----End

This lists the alarms related to four-way receive diversity.
Alarms
Table 33-6 lists the alarms related to the four-way receive diversity.
Table 33-6 Alarms related to four-way receive diversity
Alarm ID
Alarm Name
4118
4-way Diversity receiving alarm
Counters
None.
33-10

Issue 03 (2009-06-08)

33.7 References
None.
Issue 03 (2009-06-08)

33-11

34
34 SDCCH Dynamic Adjustment
SDCCH Dynamic Adjustment
About This Chapter

34.1 Overview
This describes SDCCH dynamic adjustment. The SDCCH dynamic adjustment refers to the
process through which the TCHF is converted to the SDCCH and the SDCCH is switched back
to TCHF. The SDCCH dynamic adjustment can reduce the probability of SDCCH congestion
and the impact of SDCCH initial configuration on the system performance.
34.2 Availability
This lists the NEs and software required for the implementation of SDCCH dynamic adjustment.
34.3 Impact
This describes the impact of SDCCH dynamic adjustment on system performance.
This describes the technical aspects of SDCCH dynamic adjustment. SDCCH dynamic
adjustment should be triggered depending on the cause of unsuccessful channel assignment,
current traffic flow, and channel assignment procedure. If SDCCH dynamic adjustment is
required, the BSC searches for an appropriate TCHF and triggers the SDCCH dynamic
adjustment. If the adjustment is successful, the BSC uses the related algorithm to determine
whether to switch back the SDCCH. If the requirements for switchback are met, the BSC
switches back the SDCCH that is converted from the TCHF to the TCHF.
34.5 Implementation
This describes how to configure SDCCH dynamic adjustment.
This lists the counters related to SDCCH dynamic adjustment.
34.7 References
None.
Issue 03 (2009-06-08)

34-1

34.1 Overview
This describes SDCCH dynamic adjustment. The SDCCH dynamic adjustment refers to the
process through which the TCHF is converted to the SDCCH and the SDCCH is switched back
to TCHF. The SDCCH dynamic adjustment can reduce the probability of SDCCH congestion
and the impact of SDCCH initial configuration on the system performance.
Definition
When an MS fails to request an SDCCH or the SDCCH resources are insufficient, the SDCCH
dynamic adjustment may be triggered. SDCCH dynamic adjustment is performed to convert the
TCHF to the SDCCH. This can optimize the configuration of the SDCCH and TCHF. After the
TCHF is converted to the SDCCH, the switchback of the SDCCH to the TCHF may also be
triggered.
Purposes
SDCCH dynamic adjustment can optimize the utilization of traffic channels and signaling
channels. It can also reduce the congestion rate of the SDCCH, the number of SDCCHs to be
configured, the impact on the system performance, and the requirement for the accuracy of the
required SDCCHs.
For example, if the TCHs are idle but the SDCCHs are congested because the traffic volume of
short messages increases or because the traffic peak hour bursts, the MSs may not be able to
apply for SDCCHs and cannot access the network. After SDCCH dynamic adjustment is applied,
the system capacity and call completion rate can be increased.
Terms
Terms
Definition
SDCCH
TCHF
Full-rate speech channel
TCHH
Half-rate speech channel

Full Spelling
MS
Mobile Station
SDCCH
34.2 Availability
This lists the NEs and software required for the implementation of SDCCH dynamic adjustment.
34-2

Issue 03 (2009-06-08)

NEs Involved
Table 34-1 lists the NEs involved in SDCCH dynamic adjustment.
Table 34-1 NEs involved in SDCCH dynamic adjustment
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 34-2 lists the versions of GBSS products that support SDCCH dynamic adjustment.
Product
Version
BSC
BSC6000
BTS
BTS3012
BTS3012AE

DTRU
QTRU
DTRU
QTRU
BTS3006C
BTS3002E
DBS3900 GSM
BTS3900 GSM
BTS3900A GSM
Miscellaneous
None.
34.3 Impact
This describes the impact of SDCCH dynamic adjustment on system performance.
Issue 03 (2009-06-08)

34-3


The impact of SDCCH dynamic adjustment on system performance is as follows:
l
The bearer capacity of TCHs in a cell is reduced because the SDCCH dynamic adjustment
uses the TCHFs.
SDCCH dynamic adjustment requires the intra-cell handover because the seized TCH must
be adjusted. This increases the traffic volume of intra-cell handovers.

None.

This describes the technical aspects of SDCCH dynamic adjustment. SDCCH dynamic
adjustment should be triggered depending on the cause of unsuccessful channel assignment,
current traffic flow, and channel assignment procedure. If SDCCH dynamic adjustment is
required, the BSC searches for an appropriate TCHF and triggers the SDCCH dynamic
adjustment. If the adjustment is successful, the BSC uses the related algorithm to determine
whether to switch back the SDCCH. If the requirements for switchback are met, the BSC
switches back the SDCCH that is converted from the TCHF to the TCHF.
34.4.1 SDCCH Dynamic Adjustment Procedure

This describes the SDCCH dynamic adjustment procedure, which consists of the conversion of
the TCHF to the SDCCH and the switchback of the SDCCH to the TCHF.
Figure 34-1 shows the procedure for SDCCH dynamic adjustment.
34-4

Issue 03 (2009-06-08)

Figure 34-1 SDCCH dynamic adjustment procedure

Start
SDCCH dynamic
adjustment decision
SDCCH dynamic
adjustment implementation
SDCCH switchback
decision
SDCCH switchback
implementation
End
The SDCCH dynamic adjustment procedure is as follows:

1.
Determine whether to perform SDCCH dynamic adjustment.
2.
Perform SDCCH dynamic adjustment to convert idle TCHFs to SDCCHs.
3.
Determine whether to perform SDCCH switchback.
4.
Perform SDCCH switchback to convert SDCCHs to TCHFs.
34.4.2 SDCCH Dynamic Adjustment Decision

This describes the SDCCH dynamic adjustment decision. SDCCH dynamic adjustment decision
is triggered after the SDCCH assignment procedure is complete.
The SDCCH assignment procedure is triggered by procedures such as the immediate assignment
procedure and the SDCCH incoming cell handover procedure. After an SDCCH assignment
procedure is complete, the SDCCH dynamic adjustment decision is triggered if the SDCCH
resources are insufficient or if the SDCCH assignment fails. When an SDCCH assignment fails,
the SDCCH dynamic adjustment is triggered, but the adjusted SDCCH is used only for the next
SDCCH request.
Figure 34-2 shows the procedure for triggering the SDCCH dynamic adjustment decision.
Issue 03 (2009-06-08)

34-5

Figure 34-2 Procedure for triggering the SDCCH dynamic adjustment decision
Start
SDCCH allocation
No
Is SDCCH
allocation
successful?
Yes
Is the allocated
channel the
requested one?
Yes
No
TCHF-to-SDCCH
conversion decision
End
After the SDCCH dynamic adjustment decision is triggered, the BSC decides whether the
adjustment is allowed. SDCCH dynamic adjustment is triggered only when all the conditions
are met. The conditions for triggering SDCCH dynamic adjustment are as follows:
1.
Whether the internal flow control level is greater than 0

If the internal flow control level is greater than 0, the SDCCH dynamic adjustment cannot
be triggered. If the internal flow control level is not greater than 0, the SDCCH dynamic
adjustment can be triggered.
The internal flow control level can be determined by the current CPU usage. When the
CPU usage is less than 65%, the internal flow control level is usually 0 if no emergency
such as a burst of numerous maintenance operations occurs. Level 0 of flow control
indicates that flow control is not triggered.
34-6

Issue 03 (2009-06-08)

NOTE
For details about how to query the current CPU usage, refer to Querying the CPU/DSP Usage.
2.
Whether SDCCH Dynamic Allocation Allowed is selected

If it is selected, the SDCCH dynamic adjustment can be triggered. If it is not selected, the
SDCCH dynamic adjustment cannot be triggered.
3.
Whether there are an ongoing SDCCH dynamic adjustment procedure

If there is an ongoing SDCCH dynamic adjustment procedure, a new DCCH dynamic
adjustment cannot be triggered. If there is no ongoing SDCCH dynamic adjustment
procedure, a new DCCH dynamic adjustment can be triggered.
NOTE
If an SDCCH dynamic adjustment procedure is not complete, a new SDCCH dynamic adjustment
procedure is unavailable. The switchback procedure and the adjustment procedure can be performed
simultaneously.
4.
Whether the number of idle SDCCHs in the current cell is greater than Idle SDCCH
Threshold N1
If the number of idle SDCCHs in the current cell is greater than the value of this parameter,
the SDCCH dynamic adjustment cannot be triggered. If the number of idle SDCCHs in the
current cell is not greater than the value of this parameter, the SDCCH dynamic adjustment
can be triggered.
5.
If the SDCCH dynamic adjustment is successful, whether the number of SDCCHs in the
current cell is greater than Cell SDCCH Channel Maximum after the adjustment
If the number of SDCCHs in the current cell is greater than the value of this parameter after
the adjustment, the SDCCH dynamic adjustment cannot be triggered. If the number of
SDCCHs in the current cell is not greater than the value of this parameter after the
adjustment, the SDCCH dynamic adjustment can be triggered.
NOTE
One TCHF can be converted to eight SDCCHs. Therefore, the criterion is whether the number of all
the SDCCHs plus eight is greater than Cell SDCCH Channel Maximum.
6.
Whether each TRX in the cell is assigned sufficient idle TCHs. The decision procedure is
as follows:
(1) The BSC measures the number of idle TCHFs and the number of idle TCHHs in the
cell.
(2) The BSC determines whether twice the number of TCHFs plus the number of idle
TCHHs is greater than eight. If the total number is greater than eight, the SDCCH
dynamic adjustment can be triggered. If the total number is not greater than eight, the
BSC proceeds with 6.3.
(3) The BSC determines whether twice the number of TCHFs plus the number of idle
TCHHs is greater than twice the number of TRXs in the cell. If the total number is
greater than twice the number of TRXs in the cell, there are sufficient idle TCHs and
the SDCCH dynamic adjustment can be triggered. If the total number is not greater
than twice the number of TRXs in the cell, the SDCCH dynamic adjustment cannot
be triggered.
NOTE
For details about how to determine the number of idle channels in a cell, refer to Monitoring Channel
Status.
7.
Issue 03 (2009-06-08)
Whether there are appropriate TCHFs for adjustment

34-7

If there are no appropriate TCHFs for adjustment, the SDCCH dynamic adjustment cannot
be triggered. If there are appropriate TCHFs for adjustment, the SDCCH dynamic
adjustment can be triggered.
NOTE
For details on the TCHF selection , refer to 34.4.3 SDCCH Dynamic Adjustment Algorithms.
Figure 34-3 shows the procedure for the SDCCH dynamic adjustment decision.
34-8

Issue 03 (2009-06-08)

Figure 34-3 Procedure for the SDCCH dynamic adjustment decision

Start
Does the system

performance support SDCCH
dynamic adjustment?
No
Yes
Is the parameter SDCCH
Dynamic Allocation Allowed
selected in data configuration?
No
Yes
Yes
Is SDCCH dynamic
adjustment being performed
in the current cell?
No
Measure the number of normal SDCCHs and
the number of idle SDCCHs in the current cell
Is the number of idle

SDCCHs not greater than Idle
SDCCH Threshold N1?
No
Yes
If the conversion is
performed, is the number of converted
SDCCHs not greater than Cell SDCCH
Channel Maximum?
No
Yes
Does each TRX in the cell
have sufficient idle TCHs?
No
Yes
Is there any TCH
that can be dynamically
converted to the SDCCH?
No
Yes
Perform the dynamic adjustment
End
Issue 03 (2009-06-08)

34-9

34.4.3 SDCCH Dynamic Adjustment Algorithms

This describes SDCCH dynamic adjustment algorithms. SDCCH dynamic adjustment
algorithms are the TCHF selection and the conversion of the TCHF to the SDCCH.
TCHF Selection
The TCHF used for SDCCH dynamic adjustment must meet the following requirements:
l
The channel must be in the available state.
The frequency band where the current BCCH is located and the frequency band supported
by the TCHF must have a mapping listed in Table 34-3.
The current type of the channel used for SDCCH dynamic adjustment must be TCHF, but
the channel can be set to TCHF or TCHH during data configuration.
The number of SDCCHs on the TRX where the TCHF is located cannot exceed eight. If
the channel type of a timeslot is SDCCH/8, the timeslot contains eight SDCCHs.
The current cell must have more than one TRX.
Table 34-3 Mapping between the frequency band where the BCCH is located and the frequency
band supported by the TCHF
Frequency Band Where the BCCH Is
Located
Frequency Band Supported by the

TCHF
P-GSM900M
P-GSM900M
E-GSM900M
P-GSM900M or E-GSM900M
R-GSM900M
P-GSM900M, E-GSM900M, or RGSM900M
DCS1800M
DCS1800M
PCS1900M
PCS1900M
GSM850M
GSM850M
GSM480M
GSM480M
GSM450M
GSM450M
The following table describes the selection of TCHFs to be adjusted for different types of cells.
34-10
If...
Then...
The cell is a common cell,
Dynamic adjustment can be performed if the

previous requirements are met. Figure 34-4
shows the selection procedure.

Issue 03 (2009-06-08)

If...
Then...
The cell is not a concentric cell (GSM900/

DCS1800 Co-BCCH cell),
The BSC preferentially selects the idle

TCHFs that meet the above requirements in
the underlaid subcell. If such idle TCHFs are
not found, the BSC selects the seized TCHFs.
If the TCHFs that meet the requirements are
not found in the underlaid subcell, the BSC
selects the idle TCHFs that meet the
requirements in the overlaid subcell. If such
idle TCHFs are not found, the BSC selects the
seized TCHFs. Figure 34-4 shows the
selection procedure.
The cell is a concentric cell (GSM900/

DCS1800 Co-BCCH cell),
The BSC preferentially selects the idle

TCHFs that meet the above requirements in
the underlaid subcell. If such idle TCHFs are
not found, the BSC selects the seized TCHFs.
Figure 34-4 shows the selection procedure.
NOTE
The TCHFs in the overlaid subcell cannot be used
for SDCCH dynamic adjustment.
Issue 03 (2009-06-08)

34-11

Figure 34-4 Procedure for selecting a TCHF when the TRX is selected
Start
Is the SDCCH dynamic

adjustment decision implemented
for the TCHF that meets the above
requirements?
Yes
No
Are the TRX number and the
TCHF number marked?
No
Yes
Are the SDCCHs on the current
TRX fewer than the SDCCHs on the
temporarily marked TRX?
Yes
Mark the current TRX and

a TCHF as the selected
TRX and TCHF
No
Does the SDCCHs on the
current TRX equal the SDCCHs on the
temporarily marked TRX?
No
Yes
No
Is the marked TCHF seized?
Yes
Is the TCHF idle?
Yes
No
End and return the
marked TRX number and
TCHF number
Converting the TCHF to the SDCCH

After selecting a TCHF, the BSC performs the dynamic SDCCH conversion procedure. The
dynamic SDCCH conversion procedures vary with the status of the selected TCHF.
l
34-12
The selected TCHF is idle.

1.
The BSC adjusts the channel attribute from TCHF to SDCCH.
2.
The BSC performs different operations based on whether the adjustment of channel
attribute is successful.
If the adjustment is successful, the BSC adds a dynamic conversion ongoing flag
to the cell.
If the adjustment fails, the dynamic conversion is terminated.

Issue 03 (2009-06-08)

3.
The BSC sends a command to the BTS for adjusting the channel attribute and starts
the relevant performance measurement.
4.
After receiving the command, the BTS starts converting the channels. After the
channels are converted, the BTS sends the Status Change Report to the BSC.
5.
After receiving the Status Change Report, the BSC sets the status of the converted
SDCCH/8 to idle and deletes the dynamic conversion ongoing flag. The dynamic
TCHF-to-SDCCH conversion is complete.
The selected TCHF is busy.

1.
To prevent the services carried on the selected TCHF from being disrupted, the BSC
initiates a forced intra-cell handover.
2.
The BSC sets the dynamic conversion ongoing flag for the cell and sets the channel
status to "TCHF converted to SDCCH, waiting for forced handover response" to
prevent the TCHF from being assigned to other services.
3.
The BSC performs different operations based on whether a forced handover response
is received.
If the BSC receives the forced handover response, it determines whether the forced
handover is successful.
If the forced handover fails, the TCHF is not released and the BSC deletes the
dynamic conversion ongoing flag of the cell. The channel conversion is
terminated.
If the forced handover is successful, the BSC sets the channel status to "Waiting
for channel release". When the TCHF becomes idle, the BSC follows the
procedure for converting the idle TCHF to the SDCCH.
If the BSC does not receive any forced handover response, the BSC deletes the
dynamic conversion ongoing flag of the cell. The channel conversion is terminated.
NOTE
The most distant TCH from the PDTCH is preferentially selected for dynamic SDCCH conversion.
34.4.4 SDCCH Reversion Decision

After the TCHF is converted to the SDCCH, the SDCCH is reverted to the TCHF if certain
conditions are met.
The BSC determines to revert the SDCCH to the TCHF if the following conditions are met:
l
The selected SDCCH/8 channels are converted from a TCHF.
One or more of the selected SDCCH/8 channels are idle.
The channel selection varies with the type of the cell:
Issue 03 (2009-06-08)
If the cell is not a concentric cell, the SDCCH reversion can be performed when the
previous conditions are met.
If the cell is a concentric cell, the BSC preferentially selects an SDCCH that meets the
previous conditions on the TRX in the overlaid subcell. If there is no appropriate
SDCCH in the overlaid subcell, the BSC selects an appropriate SDCCH in the underlaid
subcell.
If the QTRU is used, the SDCCH on the timeslot with the maximum number of SDCCHs
is preferentially selected.
34-13

34.4.5 SDCCH Reversion Procedure

If the requirements for SDCCH reversion are met, the BSC performs the SDCCH reversion
procedure.
The SDCCH reversion procedure lasts less than three seconds. A busy SDCCH/8 channel can
also be reverted to the TCHF. Therefore, based on the status of the selected SDCCH/8 channels,
the SDCCH reversion procedure is classified into the following types:
l
If all the selected SDCCH/8 channels are idle, the SDCCH reversion procedure is as
follows:
1.
The BSC adjusts the channel attribute from SDCCH to TCHF.
2.
The BSC sends a command to the BTS for adjusting the channel attribute and starts
the relevant performance measurement.
3.
After receiving the command, the BTS starts converting the channels. After the
channels are converted, the BTS sends the Status Change Report to the BSC.
4.
After receiving the Status Change Report, the BSC sets the status of the converted
TCHF to idle. The SDCCH-to-TCHF reversion is complete.
If one or more of the selected SDCCH/8 channels are busy, the SDCCH reversion procedure
is as follows:
1.
To prevent call disruption on the selected SDCCH/8 channel, the BSC triggers the
timer, waiting for the release of channels.
2.
The BSC sets the channel status to "SDCCH/8 converted to TCHF, waiting for idle
channel" to prevent these channels from being assigned before reversion.
3.
If the sub-channels are still busy when the timer expires, they are released forcibly.
4.
When all the selected SDCCH/8 channels are idle, the BSC follows the related
procedure for reverting the idle SDCCH.
NOTE
Typically, all the SDCCH/8 channels will be idle before the timer expires, because the occupation
of the SDCCH is very short.
34.5 Implementation
This describes how to configure SDCCH dynamic adjustment.
34.5.1 Configuring SDCCH Dynamic Adjustment

This describes how to configure SDCCH dynamic adjustment on the BSC6000 Local
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree
tab page. Then, choose Configure Cell Attributes.
Step 2 In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the
Selected cells list box. Then, click Next.
34-14

Issue 03 (2009-06-08)

Select SDCCH Dynamic Allocation Allowed.
Step 4 Click Channel Management. A dialog box is displayed, as shown in Figure 34-6.
Set the parameters related to SDCCH dynamic adjustment. The parameters are as follows:
l
Idle SDCCH Threshold N1
Cell SDCCH Channel Maximum
TCH Minimum Recovery Time
Issue 03 (2009-06-08)

34-15

----End

This lists the counters related to SDCCH dynamic adjustment.
Alarms
None.
Counters
Table 34-4 lists the performance counters related to SDCCH dynamic adjustment.
34-16

Issue 03 (2009-06-08)

Table 34-4 Counters related to SDCCH dynamic adjustment.

Counte
r
Description
R3516A
Number of Channel Conversions (TCH-SDCCH)
R3516B
Number of Channel Conversions (SDCCH-TCH)
H3024A
Failed Internal Intra-Cell Handovers (Dynamic Conversion, TCH-SDCCH)
H3024B
Failed Internal Intra-Cell Handovers (Dynamic Conversion, SDCCH-TCH)
H3004A
Internal Intra-Cell Handover Requests (Dynamic Conversion, TCH-SDCCH)
H3004B
Internal Intra-Cell Handover Requests (Dynamic Conversion, SDCCH-TCH)
H3014A
Internal Intra-Cell Handover Commands (Dynamic Conversion, TCH-SDCCH)
H3014B
Internal Intra-Cell Handover Commands (Dynamic Conversion, SDCCH-TCH)
TH3034
A
Success Rate of Internal Intra-Cell Handover (Dynamic Conversion, TCHSDCCH)
TH3034
B
Success Rate of Internal Intra-Cell Handover (Dynamic Conversion, SDCCHTCH)
CH3034
A
Successful Internal Intra-Cell Handovers (Dynamic Conversion, TCH-SDCCH)
CH3034
B
Successful Internal Intra-Cell Handovers (Dynamic Conversion, SDCCH-TCH)
34.7 References
None.
Issue 03 (2009-06-08)

34-17

35 NACC
35
NACC
About This Chapter

35.1 Overview
Network Assisted Cell Change (NACC) accelerates MS cell reselection and shortens the service
disruption time during cell reselection.
35.2 Availability
This lists the NEs, software, and licenses required for the implementation of NACC.
This describes the application scenarios and the procedure of NACC.
35.4 Implementation
This describes how to configure NACC.
None.
35.6 References
Issue 03 (2009-06-08)

35-1

35 NACC
35.1 Overview
Network Assisted Cell Change (NACC) accelerates MS cell reselection and shortens the service
disruption time during cell reselection.
Definition
NACC is short for Network Assisted Cell Change. In the NC0 and NC1 network control modes
and the packet transfer mode, the MS requests the system information of the reselected neighbor
cell from the network side when performing cell reselection. The network side notifies the MS
of the requested neighbor cell system information through the Cell Change Notification (CCN)
procedure.
NOTE
The CCN procedure is the NACC procedure.
Purposes
The purpose of NACC is to accelerate the cell reselection of the MS.
Terms
None.

Full Spelling
NACC
Network Assisted Cell Change
NC0
Network Control Mode 0
NC1
NC2
CCN
Cell Change Notification
35.2 Availability
This lists the NEs, software, and licenses required for the implementation of NACC.
NEs Involved
Table 35-1 lists the NEs involved in NACC in external PCU mode.
35-2

Issue 03 (2009-06-08)

35 NACC
Table 35-1 NEs involved in NACC

MS
BTS
BSC
PCU
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Table 35-2 lists the NEs involved in NACC in built-in PCU mode.
Table 35-2 NEs involved in NACC
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 35-3 lists the versions of GBSS products that support NACC in external PCU mode.
Product
Version
BSC
BSC6000
PCU
PCU
G3PCUV300R005C05 and later releases
Table 35-4 lists the versions of the software that supports NACC in built-in PCU mode.
Product
BSC
Version
BSC6000
Miscellaneous
NACC is available only when a license is obtained.
NACC requires the support of the MS.
Issue 03 (2009-06-08)

35-3

35 NACC

This describes the application scenarios and the procedure of NACC.
Application Scenarios
NACC application scenarios are based on cell reselection initiated by the MS. NACC only
accelerates cell reselection initiated by the MS.
The MS and BSC performs NACC when the following conditions are met:
l
The Network Control Mode parameter is set to nc0 or nc1.
In the cell configuration of the BSC, the Support NACC parameter is set to YES.
The MS operates in CCN mode.
The MS detects that the signal strength in the serving cell is poor and finds the neighbor
cell with good signal strength.
NACC Procedure
The NACC procedures consist of starting NACC only, starting NACC and SI Status, and starting
NACC and NC2.
l
Starting NACC only

In the cell configuration, the Support NACC parameter is set to YES. In such a case, only
the NACC procedure is started, as shown in Figure 35-1.
Figure 35-1 Starting NACC
MS
BSC
PACKET CELL CHANGE NOTIFICATION
PACKET NEIGHBOUR CELL DATA
PACKET CELL CHANGE CONTINUE
35-4
1.
When the MS in CCN mode determines to perform cell reselection, it does not perform
a handover but sends the PACKET CELL CHANGE NOTIFICATION message to
the BSC to request the system information of the target cell to be reselected.
2.
Upon receipt of the PACKET CELL CHANGE NOTIFICATION message, the BSC
sends the PACKET NEIGHBOUR CELL DATA message to the MS. This message
can be sent in one or more cases. The PACKET NEIGHBOUR CELL DATA message
Issue 03 (2009-06-08)

35 NACC
carries the SI1, SI3, and SI13 system information of the target cell. Then, the BSC
sends the PACKET CELL CHANGE CONTINUE message to the MS to inform the
MS to continue with cell reselection.
3.
After receiving the PACKET NEIGHBOUR CELL DATA message from the BSC,
the MS saves the system information carried by this message. After receiving the
PACKET CELL CHANGE CONTINUE message, the MS returns to NC0/NC1 mode
from CCN mode and continues with cell reselection.
4.
Based on the system information of the target cell, the MS is handed over to the
reselected target cell. The system information of the target cell can speed up the cell
reselection.
Starting NACC and SI Status

The NACC procedure is performed to transfer the system information of the neighbor cell
to the MS, and the SI Status procedure is performed to transfer the system information of
the serving cell to the MS. The combination of the NACC procedure and the SI Status
procedure can speed up the cell reselection.
In the cell configuration, the Support NACC and Support PACKET SI STATUS
parameters are set to YES. In such a case, the NACC procedure and the SI Status procedure
are started, as shown in Figure 35-2.
Figure 35-2 Starting NACC and SI Status
MS
BSC
PACKET CELL CHANGE NOTIFICATION
PACKET NEIGHBOUR CELL DATA
PACKET CELL CHANGE CONTINUE
PACKET SI STATUS
PACKET SERVING CELL DATA
Issue 03 (2009-06-08)
1.
After the MS is handed over to a new cell, if the MS does not receive the system
information of this cell, it sends the PACKET SI STATUS message to the BSC to
request the system information of the serving cell.
2.
Upon receipt of the PACKET SI STATUS message, the BSC sends the PACKET
SERVING CELL DATA message to the MS. This message can be sent in one or more
cases. It carries the system information of the serving cell.
35-5

35 NACC
3.
After receiving the PACKET SERVING CELL DATA message from the BSC, the
MS saves the system information carried by the message. The MS can speed up the
access to the serving cell according to the system information of the serving cell.
Starting NACC and NC2

When the Support NACC parameter is set to YES and the Network Control Mode
parameter is set to NC2, the procedure is actually the NC2 procedure. Before sending the
PACKET CELL CHANGE ORDER message to the MS, the BSC must send the PACKET
NEIGHBOUR CELL DATA message to MS. The PACKET NEIGHBOUR CELL DATA
message carries the system information of the neighbor cell.
35.4 Implementation
This describes how to configure NACC.
35.4.1 Configuring NACC

This describes how to configure NACC on the BSC6000 Local Maintenance Terminal.
Prerequisite
l
The cell supports the GPRS services.
1.
Apply for the license for the NACC. In the BSC6000V900R008 Exceptional
Commercial License Application Template, specify a value in the corresponding cell
of the Number of Cell supporting NC2 row in the Resource control items column.
The value indicates the number of cells that support the NACC.
2.
Procedure
35-6

Issue 03 (2009-06-08)

35 NACC
Figure 35-3 Set Cell Attributes dialog box (NACC)
Step 5 Click GPRS Attributes. The Set PS Cell GPRS Parameter dialog box is displayed. Then, set
Network Control Mode tonc0 or nc1
Step 7 Select Support NACC.
NOTE
To configure the SI STATUS, select Support PACKET SI STATUS.
Step 8 Click OK to return to the Set Cell Attributes dialog box.

Step 9 Click Finish to complete the configuration of the cell attributes.
----End
Issue 03 (2009-06-08)

35-7

35 NACC

None.
Alarms
None.
Counters
None.
35.6 References
3GPP TS 44.060 V6.12.0
35-8

Issue 03 (2009-06-08)

36 NC2
36
NC2
About This Chapter

36.1 Overview
This describes network controlled cell reselection, which is also referred to as network control
mode 2 (NC2). In NC2 mode, the network requests measurement reports from the MS and
controls the cell reselection.
36.2 Availability
This lists the NEs, software, and license required for the implementation of NC2.
This describes three types of cell reselection modes in NC2: critical cell reselection, cell load
reselection, and general cell reselection.
36.4 Implementation
This describes how to configure NC2 and the PCU.
This lists the alarms and counters related to NC2.
36.6 References
Issue 03 (2009-06-08)

36-1

36 NC2
36.1 Overview
This describes network controlled cell reselection, which is also referred to as network control
mode 2 (NC2). In NC2 mode, the network requests measurement reports from the MS and
controls the cell reselection.
Definition
If an MS is in NC2 and packet transfer mode, the network can send a Packet Cell Change Order
message to notify the MS to initiate a cell reselection.
Purposes
In NC2 mode, the network orders the MS to reselect a new cell that has better transmission
quality. Compared with the autonomous cell reselection of the MS, the network controlled cell
reselection comprehensively considers the load conditions of each cell and automatically adjusts
the loads of the cells.
Terms
None.

Acronyms and
Abbreviations
Full Spelling
NC2
36.2 Availability
This lists the NEs, software, and license required for the implementation of NC2.
NEs Involved
Table 36-1 lists the NEs involved in NC2 in external PCU mode.
Table 36-1 NEs involved in NC2
MS
BTS
BSC
PCU
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
36-2

Issue 03 (2009-06-08)

36 NC2
Table 36-2 lists the NEs involved in NC2 in built-in PCU mode.
Table 36-2 NEs involved in NC2
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 36-3 lists the versions of the software that supports NC2 in external PCU mode.
Product
Version
BSC
BSC6000

releases
PCU
PCU
G3PCUV300R005C05 and
later releases
Table 36-4 lists the versions of the software that supports NC2 in built-in PCU mode.
Product
BSC
Version
BSC6000

releases
Miscellaneous
NC2 is available only when a license is obtained.
NC2 requires the support of an MS.
If an MS supports the NC2 mode, the MS sends a Packet Measurement Report message to trigger
an NC2 procedure.

This describes three types of cell reselection modes in NC2: critical cell reselection, cell load
reselection, and general cell reselection.
Issue 03 (2009-06-08)

36-3

36 NC2
Critical Cell Reselection

Critical cell reselection is based on the transmission quality of cells. Based on the UL and DL
receive quality on the Um interface, the PCU determines whether a critical cell reselection should
be performed. Through bit error rates (BERs), the PCU determines the variation in the
transmission quality. The increase in BERs indicates that signal levels decrease or channel
interference increases. Then, the PCU orders the MS to reselect a neighbor cell that has stronger
signal strength.
Cell Load Reselection

In the network, the loads of some cells are heavy, whereas the loads of other cells are light. To
balance the loads of these cells, cell load reselection is performed. In a cell load reselection
procedure, some MSs in heavy-load cells are reselected to light-load cells. In addition, the MSs
in neighbor cells should not be reselected to heavy-load cells. Figure 36-1 shows the cell load
reselection mode.
Figure 36-1 Cell load reselection mode (1)
A cell with
a heavy load
A cell with
a light load
A cell with
a light load
A cell with
a heavy load
A cell with
a light load
A cell with
a heavy load
A cell with
a light load
To determine the traffic load of a cell, compare the channel multiplexing rate with the predefined
threshold:
l
If the channel multiplexing rate of a cell is higher than the start threshold of load cell
reselection, you can infer that the traffic load of the cell is heavy and load cell reselection
algorithms should be performed.
If the channel multiplexing rate of a cell is lower than the receiving threshold of cell load
reselection, you can infer that the traffic load of the cell is light. Therefore, some of the
loads of heavy-load cells can be reselected to the cell.
In cell load reselection mode, an MS with overhigh signal levels cannot be reselected to a
neighbor cell. Through the setting of the level threshold of cell load reselection, an MS whose
signal level is lower than the level threshold of cell load reselection can be reselected to a
neighbor cell. Figure 36-2 shows the cell load reselection mode.
36-4

Issue 03 (2009-06-08)

36 NC2
Figure 36-2 Cell load reselection mode (2)

Load reselection area
Normal
reselection border
Cell A
Cell B
Load reselection threshold
General Cell Reselection

General cell reselection is based on signal levels. If the transmission quality and traffic load of
the serving cell do not trigger cell reselection, the MS is reselected to a neighbor cell that has
stronger signal strength through the general cell reselection procedure.
36.4 Implementation
This describes how to configure NC2 and the PCU.
36.4.1 Configuring NC2

This describes how to configure NC2 on the BSC6000 Local Maintenance Terminal.
Prerequisite
The cell supports the GPRS services.
1.
Apply for the license for the NC2. In the BSC6000V900R008 Exceptional Commercial
License Application Template, specify a value in the corresponding cell of the Number of
Cell supporting NC2 row in the Resource control items column. The value indicates the
number of cells that support the NC2.
2.
the BSC License.
Context
The configuration schemes for NC2 are as follows:
l
Only NC2 needs to be configured in built-in PCU mode.
NC2 and 36.4.2 Configuring the External PCU need to be configured in external PCU
mode.
Issue 03 (2009-06-08)

36-5

36 NC2
Procedure
the target cell, and then choose Configure Cell Attributes on the shortcut menu. The Select
Cell dialog box is displayed.
Step 2 Double-click the target cell in the Cell view list box to add the cell to the Selected cells list box.
Figure 36-3 Set Cell Attributes dialog box (NC2)
Step 5 Click GPRS Attributes. The Set PS Cell GPRS Parameter dialog box is displayed. Then, set
Network Control Mode to nc2.
36-6

Issue 03 (2009-06-08)

36 NC2

Step 7 Select Support NC2.
Step 8 Click OK to return to the Set Cell Attributes dialog box.
Step 9 Click Finish to complete the configuration of the cell attributes.
----End
36.4.2 Configuring the External PCU

This describes how to configure NC2 on the PCU Maintenance Terminal.
Procedure
l
Configure NC2 on the PCU Maintenance Terminal in static data configuration mode.
1.
Log in to the PCU Maintenance Terminal through Telnet.
2.
On the PCU Maintenance Terminal, run the command pcu add relatedinfo
LCNo NCO BSIC SpgcCCCHSup PriAccThr RAColor to add the parameters related
to System Information of logical cells, as shown in Figure 36-4.
Figure 36-4 Parameters related to System Information of logical cells
Table 36-5 describes the parameters related to System Information of logical cells.
Table 36-5 Description of the parameters related to System Information of logical cells
Issue 03 (2009-06-08)
Parameter
Description
LCNo
The number of a logical cell. Value range: 065534

36-7

36 NC2
Parameter
Description
NCO
Network control mode. Value range: NC0, NC1, and NC2

NC0: An MS performs autonomous cell reselection.
NC1: An MS sends measurement reports to the network and

performs autonomous cell reselection.
NC2: An MS sends measurement reports to the network and

cannot perform autonomous cell reselection.
BSIC
Base station identity code. When configuring BSIC, you should

refer to the configuration information of the BSIC on the BSC
side. Value range: 063
SpgcCCCHSup
Whether the SPLIT_PG_CYCLE parameter is transmitted on

the CCCH of the cell. Value range: yes and no
PriAccThr
Packet access priority level. PriAccThr specifies the priority

level of the MS to access the cell. Value range: 0, 36
RAColor
3.
36-8
0: MSs are not allowed to perform packet services.
3: MSs with priority level 1 can perform packet services.
4: MSs with priority levels 12 can perform packet services.
RAColor defines the routing area color code of a GPRS cell.

Value range: 07
Run the write command to save the setting. Then type Y to end the configuration, as

Issue 03 (2009-06-08)

36 NC2
Figure 36-5 Configuration successful
Configure NC2 on the PCU Maintenance Terminal in dynamic data configuration mode.
1.
Log in to the PCU Maintenance Terminal through Telnet.
2.
On the PCU Maintenance Terminal, run the command pcu cell dynsetLCNo to enter
the cell dynamic configuration window, as shown in Figure 36-6.
Figure 36-6 Cell dynamic configuration window
3.
Issue 03 (2009-06-08)
Set NCO to NC2, as shown in Figure 36-7.

36-9

36 NC2
Figure 36-7 Setting NC2 mode (2)
4.
Type e to activate the configuration. If you need to configure other attributes, type
Y. If you do not need to configure other attributes, type N, as shown in Figure 36-8.
Figure 36-8 Setting NC2 mode (2)
5.
36-10
Run the write command to save the setting. Then type Y to end the configuration, as
Issue 03 (2009-06-08)

36 NC2
Figure 36-9 Setting NC2 mode result window
----End

This lists the alarms and counters related to NC2.
Alarms
None.
Counters
Table 36-6 lists the alarms related to NC2.
Table 36-6 Counters related to NC2
Issue 03 (2009-06-08)
Counter
Description
H9010
Number of Network Controlled Cell Reselection

Attempts
H9011

Attempts due to Downlink Quality
H9012

Attempts due to Traffic Load
H9013

Attempts for Better Cell
36-11

36 NC2
Counter
Description
H9014
Number of Failed Network Controlled Cell

Reselections
36.6 References
3GPP TS 44.060 V6.12.0
36-12

Issue 03 (2009-06-08)

37 Streaming QoS
37
Streaming QoS
About This Chapter

37.1 Overview
This describes the transmission requirements for streaming services, such as the guaranteed bit
rate, maximum bit rate, and transmission delay.
37.2 Availability
This lists the NEs, software, and license required for the implementation of Streaming QoS.
37.3 Impact
This describes the impact of streaming QoS on system performance.
This describes the technical aspects of steaming QoS. The PCU acquires the GBR of an MS
through the PFC procedure, and then calculates the data blocks transmitted on the Um interface
in a unit time based on the active codec scheme.
37.5 Implementation
This describes how to configure and verify Streaming QoS.
None.
37.7 References
Issue 03 (2009-06-08)

37-1

37 Streaming QoS
37.1 Overview
This describes the transmission requirements for streaming services, such as the guaranteed bit
rate, maximum bit rate, and transmission delay.
Definition
Streaming services comprise audio and video services. The streaming QoS defines the
transmission requirements for streaming services.
Purposes
The guaranteed bit rate (GBR) specified in QoS is used to guarantee a sufficient and stable
bandwidth for the streaming services in progress.
An MS that supports GBR can preempt the bandwidth of another MS that does not support GBR.
If both MSs support GBR, the Um resources that are insufficient are allocated to the MS that
accesses the network earlier.
Terms
None.
37-2
Acronyms and
Abbreviations
Full Spelling
QoS
Quality of Service
GBR
Guaranteed Bit Rate
PFC
Packet Flow Context
PSI
Packet System Information
SI
System Information
PFI
Packet Flow Identifier
ABQP
Aggregate BSS QoS Profile Packet
PFT
Packet Flow Timer
BSS
Base Station Subsystem
PFM
Packet Flow Management
SGSN
Service GPRS Support Node
PDP
Packet Data Protocol

Issue 03 (2009-06-08)

37 Streaming QoS
37.2 Availability
This lists the NEs, software, and license required for the implementation of Streaming QoS.
NEs Involved
Table 37-1 lists the NEs involved in Streaming QoS in external PCU mode.
Table 37-1 NEs involved in streaming QoS
MS
BTS
BSC
MSC
PCU
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Table 37-2 lists the NEs involved in Streaming QoS in built-in PCU mode.
Table 37-2 NEs involved in streaming QoS
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 37-3 lists the versions of GBSS products that support Streaming QoS in external PCU
mode.
Product
PCU
Version
PCU6000
All releases
Table 37-4 lists the versions of GBSS products that support Streaming QoS in built-in PCU
mode.
Issue 03 (2009-06-08)

37-3

37 Streaming QoS

Product
Version
BSC
BSC6000

releases
Miscellaneous
The Streaming QoS must be activated with a license.
The availability of streaming QoS also requires the support of the MS and the subscription of
the users.
The PFC Feature Mode field in the GPRS Cell Options IE of system information PSI13/SI13
specifies whether the networks support the PFC. If the uplink data block sent on the Um interface
by an MS contains the PFI that is greater than or equal to 8 bits, the MS supports steaming QoS.
37.3 Impact
This describes the impact of streaming QoS on system performance.

l
An MS that supports the streaming QoS feature has a higher priority over the MS that does
not support the streaming QoS feature. Thus, the MS supports the streaming QoS feature
may preempt a much wider bandwidth than the MS that does not support the streaming
QoS feature.
When the radio resources are insufficient, the MS that accesses the network earlier is
allocated a wider bandwidth than the MS accessing the network later.

None.

This describes the technical aspects of steaming QoS. The PCU acquires the GBR of an MS
through the PFC procedure, and then calculates the data blocks transmitted on the Um interface
in a unit time based on the active codec scheme.
37.4.1 Establishment of PFC

This describes the procedure for establishing the PFC. The establishment procedure specifies a
PFC for an MS and provides the parameters required for the uplink and downlink data
transmission. The PFC establishment can be initiated by the BSS or by the SGSN.
PFC Establishment Procedure Initiated by the BSS

1.
37-4
On receiving the Downlink Unitdata message on the Gb interface and the Uplink RLC data
block message, EGPRS Uplink RLC data block message, Packet Resource Request
Issue 03 (2009-06-08)

37 Streaming QoS
message, and Packet Downlink Ack/Nack message, which includes the information
element Channel Request Description on the Um interface, the BSS checks whether the
PFC that corresponds to the PFI field carried by the MS exists. If the PFC does not exist,
the BSS sends a Download_BSS_PFC PDU message to the SGSN and starts timer T6 to
trigger the retransmission mechanism. If the BSS fails to receive a Create_BSS_PFC PDU
message after the retransmission mechanism terminates, the PFC establishment procedure
is complete.
2.
On receiving the Download_BSS_PFC PDU message from the BSS, the SGSN responds
with a Create_BSS_PFC PDU message. If the Download_BSS_PFC PDU message
contains unknown PFI, the SGSN does not send the Create_BSS_PFC PDU message. The
corresponding ABQP and PFT are provided.
3.
On receiving the Create_BSS_PFC PDU message, the BSS stops T6 and negotiates between
the Packet Flow Management (PFM) and QoS about the ABQP. After the negotiation, the
BSS establishes the PFC corresponding to the PFI. If the establishment succeeds, the BSS
sends a Create_BSS_PFC_ACK message to the SGSN. If the establishment fails, the BSS
sends a Create_BSS_PFC_Nack message to the SGSN.
Figure 37-1 shows the PFC establishment procedure initiated by the BSS.
Figure 37-1 PFC establishment procedure initiated by the BSS
MS
BSS
SGSN
Downlink/Uplink Unitdata
Download_BSS_PFC
Create_BSS_PFC
Create_BSS_PFC_Ack/Nack
PFC Establishment Procedure Initiated by the SGSN

After the MS finishes the Packet Data Protocol (PDP) context activation, the SGSN sends a
Create_BSS_PFC PDU message to the BSS. The following steps are the same as those listed in
the PFC Establishment Procedure Initiated by the BSS.
Figure 37-2 shows the PFC establishment procedure initiated by the SGSN.
Figure 37-2 PFC establishment procedure initiated by the SGSN
BSS
MS
SGSN
Downlink/Uplink Unitdata
Modify_BSS_PFC
Modify_BSS_PFC_Ack
Issue 03 (2009-06-08)

37-5

37 Streaming QoS
37.4.2 Modification of PFC

This describes the procedure for modifying the PFC. This procedure, which can be initiated by
the BSS or by the SGSN, modifies the PFC of an MS in the BSS.
PFC Modification Procedure Initiated by the BSS

1.
Upon receipt of the PFC modification indication from the PCU, the BSS sends a
Modify_BSS_PFC PDU message to the SGSN and starts timer T8 to trigger the
retransmission mechanism. If the BSS fails to receive a Modify_BSS_PFC_Ack message
after the retransmission mechanism is terminated, the PFC modification procedure is
complete.
2.
When the SGSN receives the Modify_BSS_PFC PDU message:
3.
If the new PFC is accepted, the SGSN responds with a Modify_BSS_PFC_Ack

message, which contains the original ABQP. The modification of the PFC succeeds.
If the new PFC is not accepted, the SGSN responds with a Modify_BSS_PFC_Ack
message, which does not contain the original ABQP. The modification of the PFC fails.
Upon receipt of the Modify_BSS_PFC_Ack message, the BSS stops timer T8 and compares
the ABQP from the QoS with the ABQP from the SGSN.
l
If the two ABQPs are the same, the current PFC is modified.
If the two ABQPs are different, the modification of the PFC fails, and the original PFC
is retained.
Figure 37-3 shows the PFC modification procedure initiated by the BSS.
Figure 37-3 PFC modification procedure initiated by the BSS
MS
BSS
SGSN
PDP Context Activation

Create _BSS_PFC
Create_BSS_PFC_Ack/Nack
PFC Modification Procedure Initiated by the SGSN

The SGSN sends the BSS a Create_BSS_PFC PDU message, in which the PFI corresponds to
the PFC in the BSS. For the detailed procedure, refer to 37.4.1 Establishment of PFC.
37.4.3 Deletion of PFC

This describes the procedure for deleting the PFC. This procedure, which can be initiated by the
BSS or by the SGSN, deletes the PFC of the MS in the BSS.
37-6

Issue 03 (2009-06-08)

37 Streaming QoS
PFC Deletion Procedure Initiated by the BSS

The BSS deletes specified or all PFCs without notifying the SGSN.
PFC Deletion Procedure Initiated by the SGSN

Upon receipt of the Delete_BSS_PFC message, the BSS, based on the PFI present in the message,
deletes the corresponding PFC saved in the BSS, and then sends a Delete_BSS_PFC_Ack
message to the SGSN.
Figure 37-4 shows the PFC deletion procedure initiated by the SGSN.
Figure 37-4 PFC deletion procedure initiated by the SGSN
SGSN
BSS
Delete_BSS_PFC
Delete_BSS_PFC_Ack
37.4.4 GBR-Supported Uplink TBF Establishment Procedure

This describes the GBR-supported procedure for establishing the uplink TBF.
When establishing the uplink TBF:
l
If the uplink TBF establishment uses two phase access, the BSS searches for the PFC based
on the PFI specified in the Packet Resource Request message.
If the PFC is not established, the BSS should negotiate with the SGSN to establish the
PFC, and then allocate resources based on Best Effort.
If the PFC is established, the BSS allocates resources based on the GBR specified in
the PFC.
If the uplink TBF establishment uses one phase access, the BSS allocates resources based
on Best Effort. After the PFC is established, BSS reallocates the resources.
NOTE
When the PFC establishment procedure between the PCU and SGSN is complete, the BSS reallocates
resources based on the GBR specified in the PFC.
37.4.5 GBR-Supported Downlink TBF Establishment Procedure

This describes the GBR-supported procedure for establishing the downlink TBF.
When establishing the downlink TBF, the BSS searches for the PFC in the PCU based on the
PFI attached in the LLC PDU.
l
If the PFC is not established, the BSS should negotiate with the SGSN to establish the PFC,
and then allocates resources based on Best Effort.
If the PFC is established, the BSS allocates resources based on the GBR specified in the
PFC.
Issue 03 (2009-06-08)

37-7

37 Streaming QoS
NOTE
When the PFC establishment procedure between the PCU and SGSN is complete, the BSS reallocates
resources based on the GBR specified in the PFC.
37.4.6 Resources Reallocation Due to Changes of Uplink and

Downlink Codec Modes
This describes the principles for reallocating the resources on the Um interface when there is
change in the uplink and downlink codec modes.
The resources reallocation caused by changes of UL/DL codec modes does not change the
allocated channel group. Instead, the block budgeting is performed only on the allocated channel
group.
l
The handling is complete if the remaining block budgeting matches the original GBR.
If the remaining block budgeting does not match the original GBR, all the remaining
resources are allocated to the MS, and the PFC modification procedure is initiated. The
GBR is modified based on the allocated resources, and the SGSN is notified of the GBR
modification.
37.4.7 Resources Reallocation Due to Changes of PFC

The SGSN initiates a PFC modification procedure and modifies the Packet Flow Context (PFC)
of the Temporary Block Flow (TBF) in use. After the modification procedure is complete, the
BSS reallocates resources based on the new PFC and modifies the flow control of the MS.
37.5 Implementation
This describes how to configure and verify Streaming QoS.
37.5.1 Configuring Streaming QoS

This describes how to configure streaming QoS.
Prerequisite
In built-in PCU mode, activate the license through the Local Maintenance Terminal. For the
detailed operations, refer to Activating the BSC License.
In external PCU mode, the license should be written through the PCU maintenance console.
1.
Write the license in a newly deployed and an expanded office.

l
To write a license in a newly deployed office, do as follows:

(1) Enter the public key. For details, refer to the command pcu limit updatekey.
(2) Enter the SSN. For details, refer to the command pcu limit putssn.
(3) Switch the active and standby boards and repeat steps 1.1 and 1.2.
(4) Reset the system.
37-8
To write a license in an expanded office, do as follows:

Issue 03 (2009-06-08)

37 Streaming QoS
(1) Back up the SSN by referring to the following instructions.

NOTE
Retrieve and save the original SSN for problem locating when the expansion procedure
fails.
(2) Enter the SSN by referring to the command pcu limit putssn.
(3) Reset the system.
2.
Write the public key file.

NOTE
Command: pcu limit updatekey <HostIP>< FileName>

In the command, <HostIP> is the IP address of the <TFTP Server>, which is reserved at present. You
can update the public key only by uploading the public key file from the hard disk. By default, the
<HostIP> is set to 0.0.0.0. <FileName is the path containing the file name. Enter /hda0/filename if
you upload the public key from partition 0 of the hard disk.
Upload the public key file to the hard disk of the active POMU board.
(1) Enter the command ftp enable.
(2) Enter the command ftp adduser to add an FTP user.
(3) Upload the public key file to the hard disk of the POMU board through the FTP utility.
(4) Enter the public key by running the command pcu limit updatekey 0.0.0.0 /hda0/
ssn/pcu.pk. Assume /hda0/ssn/pcu.pk is the path in which the public key file is saved.
(5) Delete the public key file in the hard disk of the POMU board after the operation
succeeds.
3.
Write the SSN file.

NOTE
Command: pcu limit putssn <HostIP> <FileName>

Where, <HostIP> is the IP address of the TFTP Server, which is reserved at present. You can update
the public key only by uploading the public key file from the hard disk now. The <HostIP> is set to
0.0.0.0 by default.< FileName is the path containing the file name. Enter /hda0/filename if you upload
the public key from partition 0 of the hard disk.
Enter SSN from the hard disk of the active POMU board.
(3) Upload the SSN file to the hard disk of the POMU board through the FTP utility.
(4) Enter SSN by running the command pcu limit putssn 0.0.0.0 /hda0/ssn/1.ssn.
Assume /hda0/ssn/1.ssn is the path in which the SSN file is saved.
(5) If the operation fails, locate the problem based on the returned message. If the Key
Error message is displayed, enter the public key file by referring to preceding
operations.
(6) If the operation succeeds, reset the system for the changes to take effect.
(7) Delete the SSN file from the hard disk of the POMU board after the operation is
complete.
4.
Issue 03 (2009-06-08)
Obtain the SSN file:

37-9

37 Streaming QoS
NOTE
Command: pcu limit backupssn <HostIP> <FileName>

Where, <HostIP> is the IP address of the TFTP Server, which is reserved at present. You can update
the public key only by uploading the public key file from the hard disk now. The <HostIP> is set to
0.0.0.0 by default.< FileName is the path containing the file name. Enter /hda0/filename if you upload
the public key from partition 0 of the hard disk.
Back up the SSN file in the hard disk of the active POMU board.
(3) Back up the SSN by running the command pcu limit backupssn 0.0.0.0 /hda0/ssn/
filename.ssn. Assume /hda0/ssn/filename.ssn is the path in which the SSN file is
stored.
(4) Download the SSN file to the target computer through the FTP utility.
(5) Delete the SSN file from the hard disk of the corresponding POMU board after the
operation is complete.
Context
CAUTION
l
Write the public key in both the active and the standby POMU boards. A license alarm is
generated if the license is not written in the active and standby boards simultaneously. In
addition, the services may not be restored after the boards are switched.
The writing of the SSN in the standby POMU board is optional as the active POMU board
automatically synchronizes the SSN in the standby POMU board. The prerequisite is that a
public key is correctly written in the standby POMU board and the active POMU board.
After the writing of public key is complete, delete the files uploaded to the hard disk of the
POMU board.
The prerequisite for entering the license commands is that the POMU board is started. Use
the telnet to connect to the POMU board for operation and maintenance.
Perform the preceding operations in Huawei Engineer mode to ensure information security.
Enter the public key if the public key has not been written.
To avoid data collision, use one terminal to perform license-related operations of a POMU
board, such as the commands putssn, backupssn, and updatekey (the commands showesn
and showssn are not affected).
Delete the corresponding files from the hard disk of the POMU board after the operations
are complete.
Procedure
Step 1 Enable the PFC function on the SGSN side.
On the SGSN side, enter the command set softpara. Select BYTE as the parameter type, 13 as
the parameter index, and 32 as the parameter value.
Step 2 Register the MS with the HLR.
37-10

Issue 03 (2009-06-08)

37 Streaming QoS
Run the command mod GPRS to modify the following fields:

l
Set Traffic Class to Streaming.
Set uplink GBR to Expected Value.
Set downlink GBR to an Expected Value.
----End
37.5.2 Verifying Streaming QoS

This describes how to verify streaming QoS.
Procedure
Step 1 Test the streaming services of the MS that supports streaming QoS and check whether there is
a PFC establishment procedure during the PDP activation process.
Step 2 Verify that the access requests of other MSs or the downlink services do not affect the streaming
QoS.
----End

None.
Alarms
None.
Counters
None.
37.7 References
l
3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base
Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC)
protocol".
3GPP TS 23.107: "Quality of Service (QoS) concept and architecture".
Issue 03 (2009-06-08)

37-11

38
38 Packet Performance Improvement
Packet Performance Improvement
About This Chapter

38.1 Overview
This describes three sub-functions of the packet performance improvement, namely, extended
uplink TBF, EGPRS access of 11-bit messages, and takeover of the packet immediate assignment
by the BTS.
38.2 Availability
This lists the NEs and software required for the implementation of the packet performance
improvement, as well as the MS capabilities.
This describes the sub-functions of the packet performance improvement, namely, extended
by the BTS.
38.4 Capabilities
This describes the influences of the three sub-functions of the packet performance improvement
on the system performance.
38.5 Implementation
This describes how to configure and verify packet performance improvement.
This lists the counters related to packet performance improvement.
38.7 References
Issue 03 (2009-06-08)

38-1

38.1 Overview
This describes three sub-functions of the packet performance improvement, namely, extended
by the BTS.
Definition
The definitions for the sub-functions of the packet performance improvement are as follows:
l
Extended Uplink TBF
Normal uplink TBF

The MS determines the release of the TBF. The MS indicates the end of the TBF by
sending the RLC/MAC data block with CV = 0. On receiving all the data blocks, the
network sends the Packet Uplink Ack/Nack message with FAI = 1 to release the TBF.
NOTE
The CV field attached to the message from the MS specifies the remaining data blocks sent
on the uplink TBF. For example, the CV of the second-to-last data block is 1 and the CV of
the last data block is 0.
When the network receives all the uplink data blocks, the FAI bit is set to 1. Otherwise, the
FAI bit is 0.
Extended Uplink TBF

On receiving all the uplink data blocks, the network sends a control block with FAI =
0, sets the uplink TBF to be in inactive period, and starts an inactive period timer. Before
the inactive period timer expires, the network continues allocating uplink resources for
the MS. The uplink resources allow the MS to transfer control blocks.
The network sets the TBF to be in active period again upon the reception of uplink data
blocks during the inactive period of the TBF.
When the inactive period timer expires, the network sends the control block with FAI
= 1 and releases the uplink TBF.
EGPRS Access of 11-Bit Messages on the CCCH

The MS sends the 11-bit EGPRS Packet Channel Request message on the CCCH for one
phase packet access. The network assigns the EDGE channel for the MS through the
Immediate Assignment message. Therefore, the EGPRS TBF is established.
Takeover of the Packet Immediate Assignment by the BTS

The packet immediate assignment is taken over from the PCU to the BTS. The BTS
processes the packet channel request, performs the uplink immediate assignment, and
therefore establishes the uplink TBF. The PCU allocates the uplink TBF resources in
advance and sends an additional immediate assignment message to the BTS. When the MS
initiates a packet channel request, the BTS assigns the pre-allocated resources to the MS
and establishes the uplink TBF.
The packet performance improvement enables the immediate assignment message to be
sent at an earlier time. Thus, the MS can access the network at a faster speed.
Purposes
l
38-2
Extended Uplink TBF

Issue 03 (2009-06-08)

The MS enters the inactive period when there is no data transmission and automatically
switches to the active period upon any data transmission. The procedures for reapplication
and resource assignment are not required and therefore the transmission delay is minimized.
The EGPRS one phase access is enabled and the access delay is minimized. Thus, the EDGE
MS access performance is improved.
The packet immediate assignment is taken over from the PCU to the BTS. Thus, the MS
access performance is improved and the access delay is minimized.
Terms
None.

Acronyms and
Abbreviations
Full Spelling
CV
Countdown Value
FAI
Final Acknowledge Indication
TBF
Temporary Block Flow
38.2 Availability
This lists the NEs and software required for the implementation of the packet performance
improvement, as well as the MS capabilities.
NEs Involved
Table 38-1 lists the NEs involved in the packet performance improvement.
Table 38-1 NEs involved in the packet performance improvement
MS
BTS
BSC
PCU
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 38-2 lists the versions of GBSS products that support the extended uplink TBF.
Issue 03 (2009-06-08)

38-3


Product
Version
PCU
PCU
Table 38-3 lists the versions of GBSS products that support the EGPRS access of 11-bit
messages on the CCCH.
Product
Version
PCU
PCU
BTS
BTS3012
BTS3012AE

DTRU
QTRU
DTRU
QTRU
BTS3006C
BTS3002E
DBS3900 GSM
BTS3900 GSM
BTS3900A GSM
Table 38-4 lists the versions of GBSS products that support the takeover of the packet immediate
assignment by the BTS.
Product
Version
BSC
BSC6000
PCU
PCU
BTS
BTS3012
BTS3012AE
BTS3006C
38-4
DTRU
QTRU
DTRU
QTRU


Issue 03 (2009-06-08)

Product
Version
BTS3002E
DBS3900 GSM
BTS3900 GSM
BTS3900A GSM
Miscellaneous
l
Extended Uplink TBF

The MS must support the GERAN Feature Package 1.

The MS must support the EGPRS.

This describes the sub-functions of the packet performance improvement, namely, extended
by the BTS.
38.3.1 EGPRS Access of 11-Bit Messages on the CCCH

This describes the procedure for the EGPRS access of 11-bit messages on the CCCH.
Figure 38-1 shows the procedure for the EGPRS access of 11-bit messages on the CCCH.
Figure 38-1 Procedure for EGPRS access of 11-bit messages on the CCCH
MS
PCU
Channel Request
The procedure for the EGPRS access of 11-bit messages on the CCCH is the same as that for
the one-phase access of 8-bit messages on the CCCH. The access rate of the EGPRS access of
11-bit messages on the CCCH is equivalent to that of the one-phase access of 8-bit messages on
the CCCH. Compared with the EDGE two-phase access, the EGPRS access of 11-bit messages
on the CCCH is faster by 300 ms.
38.3.2 Extended Uplink TBF

This describes the transmission procedure for the extended uplink TBF.
The transmission procedure for the extended uplink TBF consists of two phases:
Issue 03 (2009-06-08)

38-5


l
Active period
Inactive period
NOTE
Normal uplink TBF has only the active period.
When there is no data transmission on the MS (the data block with CV = 0 is sent), the extended
uplink TBF does not stop immediately. The extended uplink TBF enters the inactive period when
the network sends the Packet Uplink Ack/Nack message with FAI = 0.
During the inactive period, the MS does not transfer any new data blocks. When the inactive
period timer on the network side expires, the network initiates the release procedure. The
duration of the inactive period timer can be regulated.
Figure 38-2 shows the procedure for the extended uplink TBF.
Figure 38-2 Procedure for the extended uplink TBF
PCU
MS
Normal Uplink TBF
Packet Uplink Data Block (CV=1)
Packet Uplink Ack/Nack (FAI=1)
Packet Control Ack
Extended Uplink TBF

Start inactive period timer
Packet Uplink Dummy Block

Stop inactive period timer

Start inactive period timer

Inactive period timer expire
Packet Control Ack
38.3.3 Takeover of the Packet Immediate Assignment by the BTS

This describes the procedure for the takeover of the packet immediate assignment by the BTS.
38-6

Issue 03 (2009-06-08)

l
Pre-allocating resources
The PCU allocates the uplink resources in advance, and sends an additional immediate
assignment message to the BTS.
Processing channel request

The MS sends the Channel Request message to the BTS. The BTS responds with the
Immediate Assignment message and schedules the uplink data blocks through the
preemption mechanism.
Figure 38-3 Procedure for the takeover of the packet immediate assignment by the BTS
MS
BTS
Channel Request
PCU
Pre-allocate Uplink TBF Resource
Channel Request (additional)

Immediate Assignment (additional)
Uplink Data Block

Uplink Data Block
38.4 Capabilities
This describes the influences of the three sub-functions of the packet performance improvement
on the system performance.
l
Extended Uplink TBF

Run the Ping command on the server. The Ping delay is reduced by 300 ms.

The access delay for the EGPRS capable MS is reduced by 300 ms.

The access delay for the MS is reduced by 100 ms.
38.5 Implementation
This describes how to configure and verify packet performance improvement.
38.5.1 Configuring Packet Performance Improvement

This describes how to configure packet performance improvement through the maintenance
terminal on the PCU side.
Issue 03 (2009-06-08)

38-7

Procedure
Step 1 Configuring the extended uplink TBF
l
In external PCU mode, run the command PCU add privateoptpara through the maintenance
terminal on the PCU side to configure the duration of the inactive period timer.
To configure the duration of the inactive period timer to 2000 ms, run the following
command:
pcu add
privateoptpara<LCNo><PSPrecedence><UpTbfRelDelay>2000<DnTbfRelDelay>
To disable the extended uplink TBF when the UpExtTbfInActDelay parameter is set to
0, run the following command:
pcu add
privateoptpara<LCNo><PSPrecedence><UpTbfRelDelay>0<DnTbfRelDelay>
In built-in PCU mode, run the command SET PRIVATEOPTPARA on the Local
Maintenance Terminal to configure the duration of the inactive period timer.
Step 2 Configuring the EGPRS access of 11-bit messages on the CCCH

l
In external PCU mode, run the command PCU set egprspara through the maintenance
terminal on the PCU side to configure the EGPRS access of 11-bit messages on the CCCH
for the cell.
To enable the EGPRS access of 11-bit messages on the CCCH for the cell, run the
following command:
pcu set egprspara
<LCNo><LQCMode><BepPeriod>yes<UpFixMcs><UpDefaultMcs><DnFixMcs>
<DnDefaultMcs>
To disable the EGPRS access of 11-bit messages on the CCCH for the cell, run the
following command:
pcu set egprspara
<LCNo><LQCMode><BepPeriod>no<UpFixMcs><UpDefaultMcs><DnFixMcs>
<DnDefaultMcs>
In built-in PCU mode, run the command SET PSBASE on the Local Maintenance
Terminal to configure the duration of the inactive period timer.
----End
38.5.2 Verifying Packet Performance Improvement

This describes how to test the service performance by using an MS, with the three sub-functions
of packet performance improvement enabled and disabled.
Procedure
Step 1 Extended Uplink TBF
Use an MS supporting the GERAN Feature Package 1 to test the Ping service performance, with
the extended uplink TBF enabled and disabled.
Step 2 EGPRS Access of 11-Bit Messages on the CCCH
38-8

Issue 03 (2009-06-08)

Use an EGPRS capable MS to test the Ping service performance, with the EGPRS access of 11bit messages on the CCCH enabled and disabled.
Step 3 Takeover of the Packet Immediate Assignment by the BTS
Use an MS to test the Ping service performance, with the takeover of the packet immediate
assignment by the BTS enabled and disabled.
----End

This lists the counters related to packet performance improvement.
Alarms
None.
Counters
None.
38.7 References
l
The extended uplink TBF complies with 3GPP TS 44.060 (Release 4).
The EGPRS access of 11-bit messages on the CCCH complies with 3GPP TS 44.018
(Release 4).
Issue 03 (2009-06-08)

38-9

39 Flex Abis
39
Flex Abis
About This Chapter

39.1 Overview
Flex Abis is used for the dynamic allocation of the Abis interface transmission resources on the
Um interface. This feature helps to fully use the transmission resources on the Abis interface.
39.2 Availability
This lists the NEs, software, and license required for the implementation of Flex Abis.
39.3 Impact
This describes the impact of Flex Abis on system performance and on other features.
Flex Abis is used for the dynamic allocation of the Abis interface transmission resources and
greatly improves the utilization of transmission resources on the Abis interface.
39.5 Implementation
This describes how to configure Flex Abis.
This lists the alarms and performance counters related to Flex Abis.
39.7 References
None.
Issue 03 (2009-06-08)

39-1

39 Flex Abis
39.1 Overview
Flex Abis is used for the dynamic allocation of the Abis interface transmission resources on the
Um interface. This feature helps to fully use the transmission resources on the Abis interface.
Definition
In the traditional BSC, the Abis interface transmission resources are allocated in fixed allocation
mode. That is, the transmission resources on the Abis interface and the TCH resources on the
Um interface are fixedly allocated according to the configuration in a one-to-one
correspondence. They cannot be shared with each other.
In practice, the PS services and CS services in different cells and different BTSs are not always
busy.
l
Generally, when the load of a BTS is heavy, the load of other BTSs is light.
When the traffic volume of PS services is heavy, that of CS services is light.
In such a case, if the Abis interface transmission resources can be shared among different BTSs,
cells, and services, the resource utilization can be greatly improved.
Flex Abis is an allocation mode of the Abis interface transmission resources. That is, the Abis
interface transmission resources form a resource pool to share resources among CS services and
PS services (including idle timeslots) and also among different cells and BTSs.
Purposes
With the intense competition in the communication industry, telecom operators become more
and more concerned about how to reduce operating expenditure and increase profitability.
Transmission resources account for one fourth of the whole operating expenditure.
Flex Abis enables the sharing of the Abis interface transmission resources among different BTSs,
cells, and services and thus improves the resource utilization. Especially, the Abis interface
transmission resources can be fully used when Flex Abis applies to the following cases:
l
Multi-cell large-capacity BTSs
Cascaded BTSs
Cells configured with the EGPRS function
Terms
39-2
Term
Definition
ESL
The extend signaling link (ESL) transmits signaling

between the BSC and the BTS. The ESL and the operation
and maintenance link (OML) use the same 64 kbit/s
timeslot. In 16 kbit/s multiplexing mode, the system does
not allocate timeslots for the ESL. Therefore, the ESL
shares the same timeslot with the OML. After Flex Abis is
configured, one BTS can be configured with only one ESL.

Issue 03 (2009-06-08)

39 Flex Abis

Acronym and
Abbreviation
Full Spelling
LMT
Local Maintenance Terminal
ESL
Extend Signaling Link
Flex Abis
Flexible Abis
39.2 Availability
This lists the NEs, software, and license required for the implementation of Flex Abis.
NEs Involved
Table 39-1 lists the NEs involved in Flex Abis.
Table 39-1 NEs involved in Flex Abis
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 39-2 lists the versions of GBSS products that support Flex Abis.
Product
Version
BSC
BSC6000
BTS
BTS3012
BTS3012AE
Issue 03 (2009-06-08)

DTRU
QTRU
DTRU
QTRU
BTS3006C
BTS3002E

39-3

39 Flex Abis
Product
Version
DBS3900 GSM
Not supported
BTS3900 GSM
Not supported
BTS3900A GSM
Not supported
Miscellaneous
Flex Abis requires a proper license. The number of TRXs that support Flex Abis is defined by
the license.
39.3 Impact
This describes the impact of Flex Abis on system performance and on other features.

The impact of Flex Abis on system performance is as follows:
l
Flex Abis uses dynamic allocation of Abis interface transmission resources. When the BSC
allocates related resources, it notifies the BTS through signaling messages. Therefore, the
signaling load on the Abis interface increases.
The reliability of dynamic allocation is low relative to fixed allocation.

The impact of Flex Abis on other features is as follows:
l
Flex Abis serves as the basis of the BTS local switching feature. After the BTS local
switching, the occupied Abis interface transmission resources are released. This can save
the transmission resources on the Abis interface.
The ring topology of BTS I with Flex Abis enabled has the following impact on other
features:
Flex Abis must be enabled in all the BTSs, and only the forward and reverse single E1
link is supported.
The Abis bypass function is not supported.
The 16 kbit/s LAPD link is not supported.
The Flex Abis and Abis bypass functions can be enabled simultaneously.

Flex Abis is used for the dynamic allocation of the Abis interface transmission resources and
greatly improves the utilization of transmission resources on the Abis interface.
39-4

Issue 03 (2009-06-08)

39 Flex Abis
Flex Abis Timeslot Allocation

In traditional mode, there is a one-to-one correspondence between the Um interface resources
and the Abis interface transmission resources. Even if the Um interface resources are idle, the
fixed Abis interface transmission resources are also occupied. After Flex Abis is enabled in the
BSC, the Abis interface transmission resources use the resource pool mode. The associated Abis
interface transmission resources are allocated on demand only when the Um interface resources
are occupied. This substitutes the traditional fixed resource allocation mode and improves the
utilization of the Abis interface transmission resources. Except that the monitoring timeslot
(TS0), RSL, and OML still use the fixed allocation mode of the Abis interface transmission
resources, other Abis interface transmission resources fall into the resource pool, as shown in
Figure 39-1.
Figure 39-1 Principle of Flex Abis
0
clock
10
Dynamic
Fixed
TRX1
10
11
0
clock
11
12
13
13
20
20
21
21
22
22
23
30
12
TRX2
31
23
30
31
32
32
33
40
41
41
42
42
43
43
33
40
5 0
5 0
Occupied
Idle
Flex Abis Networking

As shown in Figure 39-2, Link1, Link2, and Link3 correspond to the Abis interface transmission
links between the BSC and BTS0, between BTS0 and BTS1, and between BTS1 and BTS2
respectively. The physical transmission media can be one or more E1s/T1s or satellite
transmission is used.
The transmission resources on each Abis interface transmission link form a resource pool to
share resources between CS services and PS services.
Issue 03 (2009-06-08)

39-5

39 Flex Abis
l
The transmission resources on Link1 form Pool0.

The resources in Pool0 can be shared by CS services and PS services on BTS0, BTS1, and
BTS2.

The resources in Pool1 can be shared by CS services and PS services on BTS1 and BTS2.

The resources in Pool2 can be shared by CS services and PS services on BTS2.
Figure 39-2 Flex Abis network topology

Link2
Link1
PoolB1
B
S
Pool 0
T
S
Link3
Pool 1
Pool 2
If Flex Abis is enabled in the BSC, the BSC must allocate the Abis interface transmission
resources and establishes the transmission link between the BSC and the BTS, as shown in
Figure 39-2.
When a channel on BTS2 is allocated, the BSC must dynamically allocate the Abis interface
transmission resources on Link1, Link2, and Link3 for the channel and inform BTS0, BTS1,
and BTS2 that the transmission links for the channel are established. To ensure the reliable
transmission of connection messages between the BSC and the BTS, a new ESL is added for
transmitting connection messages. In 64 kbit/s reuse mode, the ESL and OML must use the same
64 kbit/s timeslot on an E1. The maximum number of RSL links reused by the OML must be
adjusted. A maximum of two RSL links can be reused.
During the second dynamic timeslot allocation, if FlexAbis Bypast-connect Status is set to
YES, the BSC uses the timeslot occupied last time and does not sends the same connection
message to the BTS again.
Flex Abis PS Domain Function

After Flex Abis is enabled in the BSC, the PS domain transmission resources are allocated in
the following ways to improve the utilization of transmission resources:
39-6
The BSC allocates a main timeslot based on the transmission resources of the 16 kbit/s subtimeslot.
The BSC allocates additional timeslots dynamically in steps of 16 kbit/s based on the
required coding rate on the Um interface.

Issue 03 (2009-06-08)

39 Flex Abis
39.4.1 Abis Resources Load-Triggered Half-Rate Assignment

Algorithm
This describes the Abis resources load-triggered half-rate assignment algorithm. This algorithm
determines whether the full-rate/half-rate channel assignment should be adjusted on the basis of
the Abis resource load. If this algorithm is used, the full-rate TCHs can be converted to the halfrate TCHs when the Abis resources are insufficient.
After Flex Abis is enabled in the BSC, the Abis interface transmission resources may be
insufficient before the Um interface resources are used up. Therefore, triggering half-rate
assignment through the Um interface resource load in the cell may affect the performance of the
entire network. The Abis resources load-triggered half-rate assignment algorithm solves this
problem.
Figure 39-3 shows the Abis resources load-triggered half-rate assignment procedure.
Figure 39-3 Abis resources load-triggered half-rate assignment procedure
Start
Calculate the Abis resources load
on the transmission link
Make an Abis resource load
decision on the transmission link.
Make a comprehensive decision
End
1.
Calculate the Abis resource load on the transmission link.

After Flex Abis is enabled, the Abis interface transmission resources on the entire link are
shared among all the BTSs. Therefore, the Abis resource load depends on the load of all
the Abis interface connection links on the entire link.
2.
Make an Abis resource load decision on the transmission link.

When the Abis Resource Adjustment TCHH Function Switch is set to Yes, the system
allocates half-rate TCHs preferentially if the fixed Abis channel seizure ratio exceeds the
Fix Abis Prior Choose Abis Load Thred(%) and the Flex Abis channel seizure ratio
exceeds the Flex Abis Prior Choose Abis Load Thred(%).
3.
Make a comprehensive decision.

The system make a comprehensive decision based on the Um interface resource load
decision result and the Abis resource load decision result.
Issue 03 (2009-06-08)

39-7

39 Flex Abis
l
Assignment adjustment must be started if either of the decision results is preferential

assignment of half-rate TCHs.
Assignment adjustment need not be started or loopback from half rate to full rate is
triggered only when the two decision results are preferential assignment of full-rate
TCHs.
NOTE
For details about the decision on preferential assignment of half-rate TCHs, see 12.4.1 Channel Rate
Assignment Strategies.
39.4.2 Abis Resources Preempted by the CS Services from the PS

Services
When all the Abis interface transmission resources are occupied, the new CS services can
preempt the Abis interface transmission resources of the PS services.
The CS services and PS services share the Abis interface transmission resources. The CS services
can preempt the resources of PS services on the secondary link (or even the primary link if
necessary) in the local and lower-level BTSs.
Whether the CS services can preempt the resources of PS services on the secondary link in the
local BTS and in the lower-level BTS are determined by the parameters Sublink resources
preemption switch and Lower-level sublink resources preemption switch respectively.
When the CS services preempt the Abis interface transmission resources of the PS services, if
the PCU supports the preemption and the PCU Support PREEMPT_ABIS_LINK message is
set to Open, the BSC sends this message to the PCU.
39.5 Implementation
This describes how to configure Flex Abis.
39.5.1 Configuration Suggestions

This provides the suggestions for configuring Flex Abis, which can help improve the network
performance.
Scenarios
To improve the resource utilization, enable Flex Abis in the following scenarios:
l
Transmission resources are limited, and the rent is very high, for example, satellite
transmission.
The actual traffic volume is lighter than that in the Um interface resource plan.
The cells that share Abis interface transmission resources have different peak hours.
The proportion of PS service users in the cell is high.

Generally, the PS service and CS service have different peak hours. The resource utilization
can be improved if the PS service and CS service share Abis interface transmission
resources.
39-8

Issue 03 (2009-06-08)

39 Flex Abis
Suggestions on Cascaded BTS Configuration

The suggestions on the configuration of cascaded BTSs with Flex Abis enabled are as follows:
l
If you need to configure a cascaded BTS on a link to support Flex Abis, the Flex Abis
Mode parameter of the upper-level BTS must be set to Flex.
If the Flex Abis Mode parameter of a BTS on the link is set to SemiSolid, the Flex Abis
Mode parameter of all the lower-level BTSs must be set to SemiSolid.
The main cabinet group of the level 1 BTS can be connected to the GEIUB only through
the E1 port on the main cabinet group. The extension cabinet group of the level 1 BTS can
be connected to the GEIUB through the internal connections of the main cabinet group or
through the E1 port on the extension cabinet group.
The BTSs can be cascaded only through the E1 ports on the main cabinet group. The
extension cabinet group can be cascaded with the upper-level BTS only through the main
cabinet group. The extension cabinet groups in the same BTS cannot be cascaded.
Each BTS can be cascaded with only one upper-level BTS. One BTS cannot be connected
to an upper-level BTS and a GEIUB at the same time.
Suggestions on Configuration of BTS Combined Cabinets and Cabinet Groups

The suggestions on the configuration of cabinet combination or cabinet groups between the
double-transceiver BTS and the BTS that does not support Flex Abis are as follows:
l
The Flex Abis Mode parameter of the Abis interface between the double-transceiver BTS
and the BTS that does not support Flex Abis or between the two BTSs that do not support
Flex Abis is set to Fix.
The Flex Abis Mode between the double-transceiver BTS and the BSC or between the
double-transceiver BTSs is set to Flex or SemiSolid.
Figure 39-4 Configuration of BTS combined cabinets and cabinet groups

BSC
BTS
Dynamic
allocation
Main cabinet group

(double-transceiver BTS)
BTS
Fixed
allocation
BTS not
supporting Flex
Abis
Fixed allocation
Extension cabinet group

(BTS not supporting Flex
Abis)
Issue 03 (2009-06-08)

39-9

39 Flex Abis
Suggestions on Parameter Modification

Generally, the Multiplexing Mode of the BTS is set to 4:1. When Flex Abis is enabled, the
Multiplexing Mode can be set to 5:1 or 6:1 to multiplex five RSL links or six RSL links to a
64 kbit/s timeslot and to prevent an additional 64 kbit/s timeslot from being occupied.
During the initial configuration of a BTS, set Flex Abis Mode to Flex Abis or SemiSolid to
enable Flex Abis.
After the BTS is configured, if you need to enable Flex Abis, set Flex Abis Mode to Flex or
SemiSolid.
Other Configuration Suggestions

For a BTS with Flex Abis enabled, certain timeslots except the permanently assigned timeslots
(such as signaling timeslots and monitoring timeslots) on E1 links can be disabled. These
unavailable timeslots can be used for special conditions (such as satellite transmission) or in the
case that only some timeslots on an E1 are available. For details, see 39.5.3 Configuring an
Exclusive Timeslot.
39.5.2 Configuring Flex Abis

This describes how to configure Flex Abis on the BSC6000 Local Maintenance Terminal.
Prerequisite
1.
Apply for the license of Flex Abis. In the BSC6000V900R008 Exceptional Commercial
License Application Template, specify a value in the Number of TRX supporting Flex
Abis row of the Resource control items column. The value indicates the number of TRXs
that support Flex Abis.
2.
Activate the license on the Local Maintenance Terminal. For details, see Activating the
BSC License.
Context
NOTE
Before configuring Flex Abis, see 39.5.1 Configuration Suggestions.
Procedure
Step 1 Configure a Flex Abis BTS.
NOTE
This describes only the Flex Abis configuration during the BTS configuration. For details about the BTS
configuration, see Adding a BTS (TDM Transmission Mode).
1.
On the BSC6000 Local Maintenance Terminal, right-click the GEIUB, and then choose
Add Site from the shortcut menu. A dialog box is displayed.
2.
Click Add Site. A dialog box is displayed, as shown in Figure 39-5.

Set FlexAbis Mode to Flex Abis or SemiSolid and set Multiplexing Mode.
39-10

Issue 03 (2009-06-08)

39 Flex Abis
NOTE
When the transmission resources are limited, if Flex Abis is enabled, set Multiplexing Mode to
5:1 or 6:1. This may cause link congestion to a certain extent.
If the OML and ESL are multiplexed to timeslot 31 on each E1 link, the Multiplexing Mode of
the timeslot cannot be set to 5:1 or 6:1.
If the Support Separate check box is selected, the BTS can be configured with the multitransceiver unit.
Figure 39-5 Add New Site dialog box
Step 2 Configure the cell attributes.

1.

Tree tab page. Then, select Configure Cell Attributes from the shortcut menu.
2.
to the Select cells list box. Then, click Next.
3.
Issue 03 (2009-06-08)

39-11

39 Flex Abis
4.
Click Other Attributes. A dialog box is displayed. Click Advanced. A dialog box is
On the Cell Soft Parameters tab page, set Sublink resources preemption switch and
Lower-level sublink resources preemption switch according to actual requirements.
39-12

Issue 03 (2009-06-08)

39 Flex Abis
Figure 39-7 Setting other parameters
5.
Click OK to return to the dialog box shown in Figure 39-6.
6.
In the dialog box shown in Figure 39-6, click Call Control. A dialog box is displayed, as
Set Abis Resource Adjustment TCHH Function Switch.
Issue 03 (2009-06-08)

39-13

39 Flex Abis
Figure 39-8 Setting call control parameters
7.
Click OK to return to the dialog box shown in Figure 39-6.
8.
In the dialog box shown in Figure 39-6, click Channel Management. Then, click
Advanced. A dialog box is displayed, as shown in Figure 39-9.
On the HW II Channel Assignment and Radio Channel Control tab page, set Flex Abis
Prior Choose Abis Load Thred(%) according to actual requirements.
39-14

Issue 03 (2009-06-08)

39 Flex Abis
Figure 39-9 Setting channel management parameters
Step 3 Configure BSC attributes.

1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000 and choose Configure BSC Attributes from the shortcut menu.
2.
On the Software Parameters tab page, set FlexAbis Bypast-connect Status.
Step 4 Modify the Flex Abis feature of the BTS.

1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the BTS that carries the call and select Site Operation > Modify Site Flex Abis
Mode. A dialog box is displayed, as shown in Figure 39-10.
Set Flex Abis Mode to Flex or SemiSolid.
Issue 03 (2009-06-08)

39-15

39 Flex Abis
Figure 39-10 Configuring the Flex Abis attribute of a BTS
2.
Click Finish. The Flex Abis configuration of the BTS is complete.
----End
39.5.3 Configuring an Exclusive Timeslot

This describes how to configure an exclusive timeslot on the BSC6000 Local Maintenance
Terminal.
Procedure
a BTS with Flex Abis enabled, and then choose Manually Assign Site Abis Timeslot from the
shortcut menu.
Step 2 Click Set Exclusive Timeslot. A dialog box is displayed, as shown in Figure 39-11.
39-16

Issue 03 (2009-06-08)

39 Flex Abis
Figure 39-11 Set Exclusive Timeslot dialog box
Step 3 Select a port on which the exclusive timeslot is located, and then click Set Port Exclusive
Timeslot. A dialog box is displayed, as shown in Figure 39-12.
Set Start Time Slot No, Start Sub-TS No, End Time Slot No, and End Sub-TS No according
to the actual conditions.
Issue 03 (2009-06-08)

39-17

39 Flex Abis
Figure 39-12 Browse Timeslot on the ports on site dialog box
Step 4 Click Set to let the configuration take effect.

NOTE
If you want to reconfigure Flex Abis on the exclusive timeslot, click Restore.
Step 5 Click OK. The configuration is complete.

----End

This lists the alarms and performance counters related to Flex Abis.
Alarms
Table 39-3 lists the alarms related to Flex Abis.
Table 39-3 Alarms related to Flex Abis
39-18
Alarm ID
Alarm Name
410
BTS's capability doesn't account with the config data

Issue 03 (2009-06-08)

39 Flex Abis
Counters
Table 39-4 lists the counters related to Flex Abis.
Table 39-4 Counters related to Flex Abis
Issue 03 (2009-06-08)
Counter
Description
R2720
Dynamic Assign Abis Resource(8K_CS)
R2721
Dynamic Assign Abis Resource(16K_CS)
R2722
Dynamic Assign Abis Resource(PS_MainLink)
R2723
Dynamic Assign Abis Resource(PS_SubLink)
R2730
Failed Dynamic Assign Abis Resource(8K_CS)
R2731
Failed Dynamic Assign Abis Resource(16K_CS)
R2732
Failed Dynamic Assign Abis Resource

(PS_MainLink)
R2733
Failed Dynamic Assign Abis Resource

(PS_SubLink)
R2741
FlexAbis TSs
R2742
Fault FlexAbis TSs
RR2752
Congestion Ratio of Dynamic Assign Abis

Resource(16K)
R276
CS Service Connection Failures Due to Abis Link

Failure
R3162b
Number of Failures to Allocate Abis Resources

(TCHF)
R3163b

(TCHH)
R3164b

(Dynamic PDCH)
R3142
Number of Failures to Request Dynamic PDCH

(No Abis Resources Available)
R3151c
Number of Successful Additions of Sub-Timeslot

(through Dynamic Allocation of Idle Timeslots)
R3152a
Number of Failures to Add Sub-Timeslot (Abis

Resource Request Failure)
R3153a
Number of Pre-emptions of the Dynamic Abis

Sub-Timeslots of the Serving Site
R3153c
Number of Pre-emptions of the Dynamic Abis

Sub-Timeslots of the Lower-Level Site
39-19

39 Flex Abis
Counter
Description
R3154a
Number of Pre-emptions of Dynamic Abis SubTimeslots
R3181
Number of Times CS Services Pre-empt the

Resources for PS Services
39.7 References
None.
39-20

Issue 03 (2009-06-08)

40 MSC Pool
40
MSC Pool
About This Chapter

40.1 Overview
This introduces the MSC pool. The MSCs in the MSC pool implement load balancing and
resource sharing for even distribution of traffic in the MSC pool, thus reducing inter-MSC
handovers and realizing redundancy backup.
40.2 Availability
This lists the NEs, software, and other conditions required for the implementation of the MSC
pool.
This describes the technical aspects of the MSC pool. Through the MSC pool, the NAS node
can be selected according to the load balancing algorithm. For example, new MSs are assigned
to different MSCs in the MSC pool according to this algorithm; thus implementing the load
balancing between MSCs in the MSC pool.
40.4 Capabilities
This describes the capabilities of the MSC pool.
40.5 Implementation
This describes how to configure and verify the MSC pool.
This lists the alarms related to the MSC pool.
40.7 References
Issue 03 (2009-06-08)

40-1

40 MSC Pool
40.1 Overview
This introduces the MSC pool. The MSCs in the MSC pool implement load balancing and
resource sharing for even distribution of traffic in the MSC pool, thus reducing inter-MSC
handovers and realizing redundancy backup.
Definition
Multiple MSCs constitute an MSC pool. The BSC connects to each MSC in the MSC pool.
Purposes
The MSC pool is based on the 3GPP TS 23.236-630 protocol and has the following features:
l
The MSCs in the MSC pool implements load balancing and resource sharing, thus
improving the network capacity and reducing equipment investment.
The resources between MSCs in the MSC pool are evenly distributed, thus realizing
redundancy backup. If you add or delete an MSC, services are not affected. Therefore,
network reliability is improved.
The MSC pool is logically an MSC. Therefore, the handcover between MSCs is reduced
and network performance is improved.
Terms
Terms
Definition
Pooling area
A pooling area refers to the serving area of one or more

RAN nodes. Within a pooling area, an MS can roam freely
without the change of the serving node of the CN. A
pooling area is served by one or more CNs. Multiple
pooling areas can be overlapped.
Node selection mechanism
The node selection mechanism refers to a mechanism

where a CN device is selected to serve MSs.
NRI
An NRI is used to identify a CN device.
NULL_NRI
A NULL_NRI is a special NRI. It is coded following the

same priciples as common NRIs.
Non-broadcast LAI
40-2
For an MSC pool with a single operator, the NULL_NRI

is unique.
When the MOCN is supported, each operator has a

unique NULL_NRI in the MSC pool.
A Non-broadcast LAI is a special LAI. It is coded

following the same principles as common LAIs. Each
MSC in the MSC pool must be assigned a unique nonbroadcast LAI, which is used when the MSC is offloaded.

Issue 03 (2009-06-08)

40 MSC Pool
Terms
Definition
MSC status
The MSC can be in the administration state and the

operation state.
l
Administration state
In the administration state, the configuration data of the
MSC and the private messages on the A interface can
be modified. The administration state can be normal,
offload, or inhibited.
Operation state
The actual state of the CN can be available or
unavailable. For example, when all the No. 7 signaling
links are disconnected, the state of the MSC is
unavailable. After the disconnected No. 7 signaling
links are restored, the state of the MSC becomes
available.

Acronyms and
Abbreviations
Full Spelling
BSC
Base Station Controller
CN
Core Network
DPC
Destination (signaling) Point Code
IMSI
International Mobile Station Identity
IMEI
MGW
Media Gateway
MSC
Mobile Switching Center
MOCN
Multi-Operator Core Network
NAS
Non Access Stratum
NRI
Network Resource Identifier
RAN
Radio Access Network
TMSI
40.2 Availability
This lists the NEs, software, and other conditions required for the implementation of the MSC
pool.
Issue 03 (2009-06-08)

40-3

40 MSC Pool
NEs Involved
Table 40-1 lists the NEs involved in the MSC pool.
Table 40-1 NEs involved in the MSC pool
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 40-2 lists the versions of GBSS products related to the MSC pool.
Product
BSC
Version
BSC6000

releases
Miscellaneous
The precautions for using the MSC pool are as follows:
l
To implement the MSC pool, licenses are required and MSC Pool Function Enabled must
be configured on the BSC side.
In actual networking, the interconnected MSCs must support the MSC pool.
After the MSC pool is enabled on the BSC side, the TMSI re-allocation function must be
enabled on the MSC side.
If the BSC supports the MSC pool, the following data of the BSC must be the same as the
data of the MSC and the MGW:
NRI Length(Bit) and NRI and DPC Route
NULL-NRI and NULL-NRI and DPC Route
MSC Available Capacity, MNC, MSC ID, and MSC Administration State

This describes the technical aspects of the MSC pool. Through the MSC pool, the NAS node
can be selected according to the load balancing algorithm. For example, new MSs are assigned
to different MSCs in the MSC pool according to this algorithm; thus implementing the load
balancing between MSCs in the MSC pool.
40-4

Issue 03 (2009-06-08)

40 MSC Pool
40.3.1 Typical Topology

This describes the typical topology of the MSC pool.
Figure 40-1 shows the typical topology of the MSC pool.
Figure 40-1 Typical topology of the MSC pool
MSC3
MSC6
MSC2
MSC5
MSC1
MSC7
MSC4
CS pool-area 1
CS pool-area 2
RAN node
RAN node
RAN node
RAN node
Area 1
Area 2
Area 3
Area 4
RAN node
RAN node
RAN node
RAN node
Area 7
Area 8
Area 5
Area 6
PS pool-area 1
PS pool-area 2
SGSN1
SGSN2
SGSN3
SGSN6
SGSN4
SGSN5
As shown in Figure 40-1, MSC1, MSC2, and MSC3 constitute an MSC pool, and Area1, Area
2, Area 5, and Area 6 constitute a pool area. Through the MSC pool, one BSC can be connected
to multiple MSCs at the same time. In addition, the services on the BSC are evenly distributed
to the corresponding MSC for handling according to the NRI or load balancing principle.
A pool area refers to the serving area of one or more RAN nodes. Within a pool area, an MS can
roam freely without the change of the serving node of the CN. A pool area is served by one or
more CNs. Multiple pool areas can have common parts.
40.3.2 TMSI Carrying NRI

This describes the TMSI carrying the NRI. After the MSC pool is enabled on the BSC side, the
P-TMSI allocation function must be enabled on the MSC side and the NRI must be included in
the TMSI that is allocated to the MS by the MSC.
Issue 03 (2009-06-08)

40-5

40 MSC Pool
The NRI length ranges from 0 bits to 10 bits and is used to identify each MSC in the MSC pool.
The NRI is positioned in a specified segment and starts from the 23rd bit, as shown in Figure
40-2.
Figure 40-2 Position of the NRI in the TMSI
31
30 29
CS/PS
28 27 26 25
24 23 22
VLR-restart
21 20
19
18
used NRI range
The NRIs in a pooling area must be equal in length. If two pooling areas overlap, the NRIs in
the two areas must be equal in length.
40.3.3 Load Balancing Algorithm

This describes the load balancing algorithm. The BSC implements load balancing between
MSCs. The BSC selects an MSC according to the status and available capacity of the MSC so
that load balancing between MSCs is ensured.
The load balancing algorithm consists of the algorithm defined by protocols and the random
number algorithm.
l
Algorithm defined by the 3GPP 23.236-630 protocol

When the NAS message of an MS includes the IMSI or IMEI, the BSC calculates the value
of V based on the formula (IMSI10)mod 1000 or (IMEI10)mod 1000. Then, the BSC
selects an MSC after querying the (V, MSC) relation table.
The (V, MSC) relation table is generated by the BSC based on the status and available
capacity of each MSC in the MSC pool. According to this algorithm, the traffic load of the
MSC is related to the distribution of the IMSI, which cannot fully implement the load
balancing function.
Random number algorithm

When the NAS message of the MS includes IMSI/IMEI/NULL_NRI, the BSC chooses a
random number from 0 to 999 as the value of V. Then, the BSC queries the (V, MSC)
relation table to determine the MSC for the current service.
The two algorithms differ in the methods for calculating the value of V but the two algorithms
have the same way of selecting an MSC based on the value of V.
40-6

Issue 03 (2009-06-08)

40 MSC Pool
CAUTION
If the random number algorithm is used, the TMSI allocation function must be enabled on the
MSC. This is because the mapping relation between the IMSI and the MSC is uncertain.
l
If the TMSI allocation function is not enabled on the MSC, the MS carrying the IMSI
initiates a call and the BSC routes the call to other MSCs at random. This call fails because
because the data of the MS is not available in the VLR of another MSC.
If the TMSI allocation function is enabled on the MSC, the MS can use the TMSI in
preference to initiate a call. Therefore, the call is successful.
40.3.4 NAS Node Selection (TMSI)

This describes NAS node selection. The BSC selects an MSC in the MSC pool by parsing the
NRI value in the TMSI.
The mapping relation between the NRI and the MSC is defined in data configuration of the BSC.
An NRI corresponds to only one MSC whereas an MSC can correspond to multiple NRIs.
When an MS uses the TMSI to update the location or initiate a call, the BSC can determine the
MSC by parsing the NRI value in the TMSI and querying the mapping relation between the NRI
and the MSC.
l
If the value of the NRI is NULL-NRI, the BSC uses the random number algorithm to select
an MSC from the MSCs whose states are normal and available.
If the BSC cannot find the corresponding MSC, or the MSC is in the unavailable state, or
the MSC Administration State is inhibited
, the BSC uses the random number algorithm to select an MSC from the MSCs whose states
are normal and available.
NOTE
If the MSC pool function is enabled on the BSC, the BSC selects most of MSCs by parsing the TMSI.
40.3.5 NAS Node Selection (IMSI/IMEI)

This describes the NAS node selection. When the MS uses the IMSI/IMEI to access the network,
the BSC assigns the MS to an MSC according to the load balancing algorithm.
If the message Complete Layer 3 Information reported by the MS carries the IMSI, the BSC
assigns the services of the MS to an MSC according to the load balancing algorithm. The MS
can request services such as call initiation, location update, paging response, service re-setup,
RR Initialization Request, and IMSI Detach.
If the message Complete Layer 3 Information reported by the MS carries the IMEI, the BSC
assigns the services on the MS to an MSC according to the load balancing algorithm. The MS
can request services such as the emergence call service.
40.3.6 IMSI Paging Processing

This describes IMSI paging processing. When a paging message delivered by the network carries
the IMSI, the paging response message of the MS also carries the IMSI. If the two IMSIs are
consistent, the BSC sends the paging response message to the MSC that sends the paging.
Issue 03 (2009-06-08)

40-7

40 MSC Pool
To ensure the normal processing of a call, the BSC must send the paging response message to
the MSC that issues the paging message.
l
When a paging message carries only the IMSI, the BSC buffers the mapping relation
between the IMSI and the MSC signaling point. After receiving the paging response
message, the BSC queries the mapping relation between the IMSI and the MSC to find the
MSC signaling point. Then, the BSC sends the paging response message to the
corresponding MSC. If the BSC does not receive the paging response message within a
specified period (configurable), the BSC releases the mapping relation between the IMSI
and the MSC signaling point.
When a paging message carries the TMSI, the BSC need not buffer the mapping relation
between the IMSI and the MSC signaling point. After receiving the paging response
message, the BSC finds the MSC signaling point according to the NRI in the TMSI. Then,
the BSC sends the paging response message to the corresponding MSC.
The MSC sends the CS paging message to the SGSN through the Gs interface. The SGSN
forwards the message to the BSC. Then, the MS reports the paging response message to the
MSC through the A interface.
l
For the CS paing message that contains the IMSI, the BSC must record the information
about the mapping relation between the paging message and the MSC that issues the paging
message so that the BSC can send the paging response message to the MSC in future. For
the CS-domain paging message that contains the TMSI, the BSC can find the corresponding
MSC according to the NRI in the TMSI.
For the PS paging message, the paging response of the MS is forwarded to the SGSN
through the BSC.
40.3.7 Load Reassignment

This describes load reassignment. The system can reassign MSs of an MSC to other MSCs in
the MSC pool.
Assume that MS1 is originally attached to MSC1, and now MSC1 is in the offload state. The
offload process of MS1 is as follows:
l
40-8
MS1 initiates a call.

1.
Before the call is established, MSC1 reassigns a TMSI to MS1. The value of the NRI
is NULL_NRI and the value of the LAI is Non-broadcast LAI/RAI.
2.
After the call is terminated, if MS1 finds that the LAI sent by MSC1 is different from
the LAI of the current cell, MS1 immediately initiates the location update procedure.
3.
In the location update message Complete Layer 3 Information reported by MS1, the
BSC obtains the NRI NULL_NRI by decoding the TMSI. The BSC then connects
MS1 to another MSC according to the load balancing algorithm.
4.
The MSC assigns a new TMSI to MS1.
If MS1 does not initiate a call for a long period, it is assigned to an MSC through through
periodical location update procedures.
1.
In the location update procedure of MS1, MS1 reports the TMSI and the BSC assigns
the TMSI to MSC1.
2.
MSC1 assigns the TMSI to MS1. The NRI value in the TMSI is NULL_NRI and the
LAI value in the message is Non-broadcast LAI/RAI.
Issue 03 (2009-06-08)

40 MSC Pool
3.
If MS1 finds that the LAI in the message is different from the LAI of the current cell,
MS1 initiates the location update procedure again.
4.
When MSC1 is in the offload state and the NRI value in the TMSI is NULL_NRI, the
BSC assigns MS1 to another MSC. In this way, MS1 is reassigned.
If MS1 is powered off for a long period, it initiates a location update procedure immediately
after it is powered on.
If MSC1 is still in the offload state, MS1 is reassigned in accordance with the preceding
location update procedure.
If MSC1 is restored to the normal state, MS1 continues being attached to MSC1 and
is not reassigned.
After the offload is complete, you must set the administration state of MSC1 to normal.
Otherwise, MSC1 cannot receive the information about newly registered MSs.
40.3.8 Message Processing on the A Interface

This describes message processing on the A interface. After the MSC pool is enabled, private
messages can also be processed on the A interface. There are some changes of the standard
message processing on the A interface.
Private Message Processing

In the MSC pool networking, if the MSC and the BSC are Huawei devices, the MSC periodically
broadcasts its capacity usage. The private message carries the information about the total
capacity and available capacity of the MSC. After receiving the private message, the BSC
updates the value of the MSC available capacity parameter, thus making the load balancing
algorithm more effective.
If the available capacity in the private message is directly used by the BSC as a load balancing
parameter, MSC Available Capacity that is set on the BSC side is invalid and unavailable for
future use. To solve the problem, the BSC uses the following formula:
MSC available capacity = MSC Available Capacity configured by the BSC - (total MSC
capacity in the private message - MSC available capacity in the private message)
When MSC Available Capacity configured by the BSC is far less than the total MSC capacity
in the private message, the calculated result may be equal to or smaller than 0. In this case, the
MSC available capacity is regarded as 0.
In addition, the MSC sends the configuration message to notify the BSC of the current MSC
status. In this way, the MSC is offloaded. The MSC can query the current MSC status saved on
the BSC. If the MSC considers that the query result is abnormal, it can send the configuration
message to the BSC to reset the MSC status.
NOTE
By default, the period for broadcasting the private message is one hour. The period can be set on the NSS
side.
Standard Message Processing

The changes of the standard message processing on the A interface are as follows:
l
Issue 03 (2009-06-08)
Initiating the processing of the Overload message

40-9

40 MSC Pool
Originally, the BSC sends the Overload message to only one MSC. After the MSC pool is
enabled, the BSC needs to send the Overload message to all MSCs in the MSC pool.
l
Processing the RESET message

Before the MSC pool is enabled, the BSC releases all the calls after receiving the RESET
message on the A interface. This is because all the calls are processed by one MSC. After
connecting to multiple MSCs, the BSC responds to only the MSC that sends the RESET
message. The responses of the BSC include restart-indication, call clearance, and circuit
initialization.
Sending the RESET message

If the BSC is reset after connecting to multiple MSCs, the BSC sends the RESET message
to all the MSCs and sets the Receive MSC Config. Msg. Timer to wait for the responses
from all the MSCs. If the BSC does not receive any RESET message response from the
MSC, the BSC resends the RESET message to the MSC.
40.4 Capabilities
This describes the capabilities of the MSC pool.
The common capabilities of the MSC pool are as follows:
l
Each MSC pool can be configured with up to 32 MSCs.
Each BSC can be connected to 32 MSCs.
Each NMS can manage 128 BSCs at the same time.
Each NMS can manage 32 MSC pools at the same time.
Each MSC can belong to up to eight MSC pools at the the same time.
Each MSC/VLR can be configured with up to eight NRIs at the same time.
Each BSC can be configured with up to 1024 NRIs.
Each BSC can be configured with up to 5 NULL-NRIs and each NULL-NRI can be
configured with up to 32 MSCs.
40.5 Implementation
This describes how to configure and verify the MSC pool.
40.5.1 Configuring MSC Pool (in A Interface over TDM Mode)

This describes how to configure the MSC pool on the BSC6000 Local Maintenance
Terminal.
Prerequisite
40-10
The BSC and MSC are Huawei devices.
The MSC server interconnects to the MGW and the relevant data is configured correctly.
Issue 03 (2009-06-08)

40 MSC Pool
1.
When applying for the MSC pool license, ensure that Support MSC POOL
Function under Function control items in BSC6000V900R008 Exceptional
Commercial License Application Template is set to 1.
2.
Activate the license on the BSC6000 Local Maintenance Terminal. For details, refer
to Activating the BSC License.
3.
The BSC supports the MSC pool after the license is activated. Set the attributes of
related objects and parameters on the BSC6000 Local Maintenance Terminal.
Context
This describes the application of the MSC pool on the BSC.
Procedure
Step 1 Configure the data of the MSC server and the MGW.
1.
For Huawei core network devices, enable the MSC pool on the MSC side.
2.
Set A-Flex to Yes on the MSC side.
3.
Configure the parameters related to the MSC pool, such as the NRI and NULL_NRI of
each MSC, available capacity of the MSC, MNC, and CN ID.
For details about setting parameters, refer to the user manuals related to the MSC products.
Step 2 Add a DSP.

1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then select Configure SS7 Signaling Point from the shortcut menu.
In Figure 40-3, click the DSP tab.
Figure 40-3 Configuring an SS7 signaling point
Issue 03 (2009-06-08)

40-11

40 MSC Pool
2.
Click Add DSP. A dialog box is displayed, as shown in Figure 40-4.

Configure DSP Group No., MSC Available Capacity, MNC, MSC ID, MSC
Administration State, and BSC Default DSP.
Figure 40-4 Adding the DSP
NOTE
If you plan to add multiple DSPs, you need to modify BSC Default DSP.
3.
Click OK. The configuration is complete.
Step 3 Configure the A interface E1/T1.

1.
40-12
Right-click a GEIUA on the BSC Device Panel of the BSC6000 Local Maintenance
Terminal and select Configure A Interface E1/T1 from the shortcut menu. A dialog box
is displayed, as shown in Figure 40-5.

Issue 03 (2009-06-08)

40 MSC Pool
Figure 40-5 Configuring A interface E1/T1
2.

Figure 40-6 Adding A interface E1/T1
Issue 03 (2009-06-08)

40-13

40 MSC Pool
CAUTION
The DSP Group No. maps the Port No.. Configure the Start CIC of this port.
The start CICs of different ports within a DPC group cannot be duplicate.
3.
Step 4 Configure MSC pool parameters.

1.
On the BSC6000 Local Maintenance Terminal, right-click BSC6000 and then select
Configure BSC Attributes from the shortcut menu. Click the MSC Pool Parameters tag
on the displayed dialog box as shown in Figure 40-7.
Figure 40-7 Configuring MSC pool parameters
2.
Configure the parameters displayed in Figure 40-7 and then click Finish. The configuration
of the MSC pool parameters is complete.
Step 5 Configure the NRI and DPC route.

1.
40-14
Click the NRI and DPC Route tab in Figure 40-7. A tab page is displayed, as shown in
Figure 40-8.

Issue 03 (2009-06-08)

40 MSC Pool
Figure 40-8 Configuring the NRI and DPC route
2.

Configure NRI and DPC.
Figure 40-9 Adding the NRI and DPC route
Issue 03 (2009-06-08)

40-15

40 MSC Pool
3.
Click OK. The configuration of the NRI and DPC route is complete.
Step 6 Configure the Null-NRI and DPC route.

1.
Click the Null-NRI and DPC Route tab in Figure 40-7. A tab page is displayed, as shown
in Figure 40-10.
Figure 40-10 Configuring the Null-NRI and DPC route
2.

Configure NULL-NRI and DPC.
40-16

Issue 03 (2009-06-08)

40 MSC Pool
Figure 40-11 Adding the Null-NRI and DPC route
3.
Click OK. The configuration of the Null-NRI and DPC route is complete.
----End
40.5.2 Configuring MSC Pool (in A Interface over IP Mode)

This describes how to configure the MSC pool on the BSC6000 Local Maintenance
Terminal.
Prerequisite
l
1.
When applying for the MSC pool license, ensure that Support MSC POOL
Function under Function control items in BSC6000V900R008 Exceptional
Commercial License Application Template is set to 1.
2.
Activate the license on the BSC6000 Local Maintenance Terminal. For details, refer
to Activating the BSC License.
3.
The BSC supports the MSC pool after the license is activated. Set the attributes of
related objects and parameters on the BSC6000 Local Maintenance Terminal.
Context
This describes the application of the MSC pool on the BSC.
Issue 03 (2009-06-08)

40-17

40 MSC Pool
Procedure
Step 1 Configure the data of the MSC server and the MGW.
1.
For Huawei core network devices, enable the MSC pool on the MSC side.
2.
Set A-Flex to Yes on the MSC side.
3.
Configure the parameters related to the MSC pool, such as the NRI and NULL_NRI of
each MSC, available capacity of the MSC, MNC, and CN ID.
For details about setting parameters, refer to the user manuals related to the MSC products.
Step 2 Configure the M3UA destination entity.

1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then select Configure M3UA Data > Configure M3UA Entity from
the shortcut menu. A dialog box is displayed, as shown in Figure 40-12.
In Figure 40-12, click the DSP tab.
Figure 40-12 Configuring the M3UA destination entity
2.

Configure DSP Group No., MSC Available Capacity, MNC, MSC ID, MSC
Administration State, and BSC Default DSP.
40-18

Issue 03 (2009-06-08)

40 MSC Pool
Figure 40-13 Adding the M3UA destination entity
3.
Step 3 Configure the M3UA link set.

1.
Issue 03 (2009-06-08)
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then select Configure M3UA Data > Configure M3UA Linkset
from the shortcut menu. A dialog box is displayed, as shown in Figure 40-14.

40-19

40 MSC Pool
Figure 40-14 Configuring the M3UA link set
2.

Figure 40-15 Adding the M3UA link set
3.
40-20
Set each parameter and click OK. The configuration of the M3UA link set is complete.
Issue 03 (2009-06-08)

40 MSC Pool
Step 4 Configure the M3UA route.

1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then select Configure M3UA Data > Configure M3UA Route from
the shortcut menu. A dialog box is displayed, as shown in Figure 40-16.
Figure 40-16 Configuring the M3UA route
2.
Issue 03 (2009-06-08)

40-21

40 MSC Pool
Figure 40-17 Adding the M3UA route
3.
Set each parameter and click OK. The configuration of the M3UA route is complete.
Step 5 Configure the M3UA link.

1.
40-22
On the BSC6000 Local Maintenance Terminal, right-click the GFGUA board of the
GMPS subrack, and then select Configure M3UA Link from the shortcut menu. A dialog

Issue 03 (2009-06-08)

40 MSC Pool
Figure 40-18 Configuring the M3UA link
2.

Figure 40-19 Adding the M3UA link
3.
Issue 03 (2009-06-08)
Set each parameter and click OK. The configuration of the M3UA route is complete.
40-23

40 MSC Pool
Step 6 Configure MSC pool parameters.

1.
On the BSC6000 Local Maintenance Terminal, right-click BSC6000 and then select
Configure BSC Attributes from the shortcut menu. Click the MSC Pool Parameters tab
in the displayed dialog box, as shown in Figure 40-20.
Figure 40-20 Configuring MSC pool parameters
2.
Set each parameter and click Finish. The configuration of the MSC pool parameters is
complete.
Step 7 Configure the NRI and DPC route.

1.
40-24
Click the NRI and DPC Route tab in Figure 40-20. A tab page is displayed, as shown in
Figure 40-21.

Issue 03 (2009-06-08)

40 MSC Pool
Figure 40-21 Configuring the NRI and DPC route
2.

Configure NRI and DPC.
Figure 40-22 Adding the NRI and DPC route
Issue 03 (2009-06-08)

40-25

40 MSC Pool
3.
Click OK. The configuration of the NRI and DPC route is complete.
Step 8 Configure the Null-NRI and DPC route.

1.
Click the Null-NRI and DPC Route tab in Figure 40-20. A tab page is displayed, as shown
in Figure 40-23.
Figure 40-23 Configuring the Null-NRI and DPC route
2.

Configure NULL-NRI and DPC.
40-26

Issue 03 (2009-06-08)

40 MSC Pool
Figure 40-24 Adding the Null-NRI and DPC route
3.
Click OK. The configuration of the Null-NRI and DPC route is complete.
----End
40.5.3 Verifying MSC Pool

This describes how to verify the MSC pool. On the BSC6000 Local Maintenance Terminal,
you can view the distribution of an MS to the MSC through the messages traced on the A
interface.
Prerequisite
l
Context
The MSC pool is verified with the load balancing algorithm.
Procedure
l
Select Random Algorithm in the MSC Pool Load Balancing Algorithm Selection table.
1.
After the MS is powered on, its location is updated.
Use the IMSI for location update.

The MS is assigned to a normal and available MSC in the MSC pool at random.
The MSC with a higher available capacity is more probable to be chosen.
Use the TMSI for location update.

The MS is assigned to the MSC that maps the NRI in the TMSI.
Issue 03 (2009-06-08)

40-27

40 MSC Pool
2.
After the location of the MS is updated, the MSC assigns the TMSI to the MS. This
MSC provides later service for the MS.
3.
When the MS initiates a call or other services again, the MS is assigned to the MSC.
Select Based on MSC ID Algorithm in the MSC Pool Load Balancing Algorithm
Selection table.
Each time the location of the MS is updated through the IMSI or a call is initiated, the BSC
assigns the MS to a specified MSC in the normal and available state.
----End

This lists the alarms related to the MSC pool.
Alarms
If multiple DSPs are supported, the DPC information is added to the alarms related to the MSC
for distinguishing different MSCs. Table 40-3 lists the alarms related to the MSC pool.
Table 40-3 Alarms related to the MSC pool
Alarm ID
Alarm Name
124
No A Interface Circuit Configured in the BSC
126
No Circuit Configured in the MSC
129
MSC Resetting
130
BSC Resetting Failure
131
BSC Unable to Reset a Circuit
132
BSC Unable to Block a Circuit
133
BSC Unable to Unblock a Circuit
Performances
None.
40.7 References
3GPP TS 23.236 V6.3.0
40-28

Issue 03 (2009-06-08)

41 BTS Ring Topology
41
BTS Ring Topology
About This Chapter

41.1 Overview
This describes the definition and purpose of BTS ring topology. In addition to saving
transmission resources, the BTS ring topology improves system reliability, protects operators'
investment, and ensures normal services.
41.2 Availability
This describes the availability of the BTS ring topology, which involves the network elements
(NEs), software, and other conditions.
41.3 Impact
This describes the impact of BTS ring topology on the system performance.
This describes the technical aspects of BTS ring topology, including the automatic switchover
and manual switchover during link disconnection, and the types of BTS ring topology.
41.5 Implementation
This describes how to configure the BTS ring topology, change non-ring topology to ring
topology, verify BTS ring topology, delete a BTS from the ring topology, and manually switch
over the BTS ring topology.
There is no maintenance information about the BTS ring topology.
41.7 References
None.
Issue 03 (2009-06-08)

41-1

41.1 Overview
This describes the definition and purpose of BTS ring topology. In addition to saving
transmission resources, the BTS ring topology improves system reliability, protects operators'
investment, and ensures normal services.
Definition
The BTS ring topology is one of the topologies supported by the BTS. Other topologies include
star, chain, and tree topologies.
Figure 41-1 and Figure 41-2 show the BTS ring topologies.
Figure 41-1 BTS ring topology (1)
B
0
G
E
I
U
B
BTS0
C
0
BTS1
D
0
BTS2
E
1
BTS3
Figure 41-2 BTS ring topology (2)
A
G
E
I
U
B
B
0
BTS0
C
0
BTS1
BTS2
G
E
I
U
B
41-2

BTS3
Issue 03 (2009-06-08)

NOTE
0 and 1 shown in Figure 41-1 refer to port 0 and port 1 of the BTS. In the BTS ring topology, the link set
up at port 0 is a forward link and the link set up at port 1 is a reverse link.
The BTS ring topology can be implemented between interface boards but not between subracks. In other
words, the BTS ring topology must be implemented between the GEIUBs located in the same subrack, as
Normally, the BTS ring topology is a chain of BTS0, BTS1, and BTS2 in sequence, known as
a forward direction. In the forward direction as shown in Figure 41-1, BTS0 is the highest-level
BTS, BTS1 is the second-level BTS, .and other BTSs are connected analogically. When the link
A, B, C, or D is broken, the BTSs in front of the breakpoint remains in the same topology, and
the BTSs behind the breakpoint form a chain in a reverse direction.
The BTS ring topology is categorized into two types, namely, Huawei BTS ring topology
and Huawei BTS ring topology . In BTS ring topology , the BTS with a reverse link will
be initialized again after transmission disruption, and thus the services of the BTS are interrupted.
In BTS ring topology , the services of the BTS with a reverse link are not interrupted after
transmission disruption.
Purposes
The BTS ring topology saves transmission resources and improves network reliability.
Terms
None.

None.
41.2 Availability
This describes the availability of the BTS ring topology, which involves the network elements
(NEs), software, and other conditions.
NEs Involved
Table 41-1 lists the NEs involved in the BTS ring topology.
Table 41-1 NEs involved in BTS ring topology
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Issue 03 (2009-06-08)

41-3

Software Releases
Table 41-2 lists the versions of GBSS products that support BTS ring topology .
Table 41-2 GBSS products and software versions supporting BTS ring topology
Product
Version
BSC
BSC6000
BTS
BTS3012
BTS3012A
E

DTRU
QTRU
DTRU
QTRU
BTS3006C
BTS3002E
DBS3900 GSM
BTS3900 GSM
BTS3900A GSM
Table 41-3 lists the versions of GBSS products that support BTS ring topology .
Table 41-3 GBSS products and software versions supporting BTS ring topology
Product
Version
BSC
BSC6000
BTS
BTS3012
BTS3012AE
41-4

DTRU
QTRU
DTRU
QTRU
BTS3006C
BTS3002E
DBS3900 GSM
BTS3900 GSM
BTS3900A GSM

Issue 03 (2009-06-08)

Miscellaneous
l
The BTS in the ring topology can be connected only with a single E1 link.
The BTS in the same ring topology can be configured as only one type, that is, either BTS
ring topology or BTS ring topology .
Based on physical links, a maximum of five levels of cascaded BTSs can be set up in the
ring topology.
Call drops occur when the forward link and reverse link in BTS ring topology are
switched over.
NOTE
The ring topology uses port 0 and port 1 of the BTS.
41.3 Impact
This describes the impact of BTS ring topology on the system performance.

BTS Ring Topology I
l
If you manually switch over the BTS ring topology, the BTS is reset and thus the services
of the BTS are affected.
After automatic disconnection, the BTS is initiated and thus the services of the BTS are
affected.
The BTS ring topology with 39 Flex Abis enabled does not preempt lower-level sublink
resources.
BTS Ring Topology II

l
The switchover from forward link to reverse link of the BTS ring topology lasts no longer
than eight seconds, which is also the time when a physical link is restored to an RSL link.
The OML link is established eight seconds after the setup of the physical link.

BTS Ring Topology I
l
Other ports of the BTSs cannot be connected to the cascaded BTSs.
51.4.2 Abis over IP and Hub BTS are not supported.
BTS ring topology I with 39 Flex Abis enabled has the following impacts on the other
features:
39 Flex Abis must be enabled in all the BTSs and only the forward and reverse single
E1 link is supported.
The Abis bypass function is not supported.
The 16 kbit/s LAPD link is not supported.
BTS Ring Topology II

l
Other ports of the BTSs cannot be connected to the cascaded BTSs.
51.4.2 Abis over IP and Hub BTS are not supported.
Issue 03 (2009-06-08)

41-5


l
39 Flex Abis, 52 Abis Transmission Optimization, and Abis bypass are not supported.

This describes the technical aspects of BTS ring topology, including the automatic switchover
and manual switchover during link disconnection, and the types of BTS ring topology.
41.4.1 Automatic Switchover During Link Disconnection

This describes the automatic switchover performed during link disconnection. When a link of
the BTS ring topology is broken, the BTSs behind the breakpoint automatically set up a link in
the reverse direction.
The automatic switchover is a basic function of the BTS ring topology. Normally, all the BTSs
in the ring topology form a chain of forward links. If one of the links is broken, all the BTSs
behind the breakpoint automatically set up a link in the reverse direction. When the reverse link
is set up, the BTSs are initialized to form a new chain which can work normally.
If the forward link is restored to a normal state but the reverse link is broken, the BTSs
automatically switch over to the forward link. Before switchover, the BTSs need to wait for a
certain period of time (Ring I Waiting Time Before Rotate(s) or Ring II Waiting Time Before
Rotate(s) to prevent the switchover caused by OML intermittent.
41.4.2 Manual Switchover During Link Disconnection

This describes the manual switchover during link disconnection. When a link is broken and the
transmission is restored with the setup of a reverse link, the automatic switchover is disabled.
The maintenance personnel, however, can forcibly switch over the link to the forward direction.
When the transmission quality in the forward direction is poor, the maintenance personnel can
manually switch over the link to the reverse direction.
The transmission in the forward and reverse directions must work normally during manual
switchover. The BTS must be first connected to the specified port. If the connection fails, the
BTS is connected to another port. The BTSs are connected separately to form a ring topology,
and the OML of the lower-level BTSs can be set up only after the upper-level BTSs transparently
transmit the timeslot exchange. In this case, the link in the ring cannot be set up at a time. When
you switch over multiple BTSs at the same time, some BTSs may be set up in the original
direction.
Therefore, when you switch over the forward link to the reverse link, you must first switch over
the highest-level BTS in the reverse direction. After a BTS is successfully connected in the
reverse direction and is automatically initialized, you can continue with the next BTS. When
you switch over the reverse link to the forward link, you must first switch over the highest-level
BTS in the forward direction.
NOTE
During manual switchover, the corresponding BTS is reset and related alarms are reported.
The port mentioned herein refers to the port on the GEIUB/GOIUB.
41-6
The parameters involved in the switchover of BTS ring topology are Ring I Waiting
Time Before Rotate(s) and Ring I Try Rotating Duration Time(s).
The parameters involved in the switchover of BTS ring topology are Ring II Waiting
Time Before Rotate(s) and Ring II Try Rotating Duration Time(s).
Issue 03 (2009-06-08)

41.4.3 Types of BTS Ring Topology

The BTS ring topology is categorized into two types, namely, BTS ring topology and BTS
ring topology . The difference between the two types is that after transmission disruption,
BTS ring topology re-initializes the reverse-link BTS and thus interrupts the BTS services,
whereas BTS ring topology does not interrupt the BTS services.
BTS Ring Topology

In BTS ring topology , when the BTS is disconnected from the network, the BTS can be
reconnected in the reverse direction through automatic switchover. Thus, the BTS can work
normally. If the transmission is restored to the normal state after the BTS is reconnected in the
reverse direction, the automatic switchover is disabled. You can enable the manual switchover
function to connect the BTS in the forward direction.
When BTS ring topology and Flex Abis are enabled at the same time, the dynamic assignment
of timeslots for transmission can be performed in the forward and reverse directions if the
communication in the two directions is normal, as shown in Figure 41-3. This function prevents
transmission links from congestion and enhances network resource utilization.
Figure 41-3 Transmission in the forward and reverse directions
B
0
G
E
I
U
B
BTS0
Forward link
C
0
BTS1
Reverse link
1 0
BTS2
E
1
BTS3
BTS Ring Topology

BTS ring topology is optimized on the basis of BTS ring topology . The difference between
the two types is that after transmission disruption, BTS ring topology re-initializes the reverselink BTS and thus interrupts the BTS services, whereas BTS ring topology does not interrupt
the BTS services.
The parameters related to BTS ring topology are configured on the BSC6000 Local
Maintenance Terminal. To enable BTS ring topology , set Configure Ring II to Yes. Other
parameters include Ring II Waiting Time Before Rotate(s), Ring II Try Rotating Duration
Time(s), and Ring II Rotating Penalty Time(s).
In addition, set the parameters related to OML links. The system detects the OML link status
according to the parameters T200(10ms), T203(s), and N200(time)
NOTE
The parameters related to BTS ring topology can be queried.
Issue 03 (2009-06-08)

41-7

41.4.4 BTS HDLC Ring Topology

The HDLC ring topology is composed of the BTSs that operate in Abis optimized transmission
mode.
The HDLC ring topology applies only to ring topology II. The HDLC ring topology supports
the formation of the ring through ports 0 and 1 of each BTS. The forward ring and reverse ring
can be connected over one interface board or over two interface boards. However, the two rings
cannot be connected over different subracks.
Compared with the TDM ring topology, the HDLC ring topology has the following restrictions:
l
The HDLC ring topology does not support the HDLC-TDM hybrid networking.
The HDLC ring topology does not support the connection of a secondary link.
In HDLC ring topology, the hybrid grouping with an old cabinet (BTS30 or BTS312) is
not supported.
The HDLC ring topology does not support the connection of a branch BTS.
The HDLC ring topology does not the functions such as Flex Abis, Abis bypass, local
switching, and 16 kbit/s LAPD signaling links.
The HDLC ring topology supports the configuration of exclusive timeslots, but does not
support the configuration of monitor timeslots.
The timeslots associated with the HDLC ring topology do not support the manual allocation.
The HDLC ring topology does not support the conversion of the bearing modes, that is, the
conversion from the HDLC ring topology to the TDM ring topology.
NOTE
Based on physical links, a maximum of five levels of cascaded BTSs can be set up in the ring topology.
In HDLC ring topology, ports 0 and 1 of the BTSs are used. The connection of ports 0 and 1 of the BTSs
should cannot be modified.
41.5 Implementation
This describes how to configure the BTS ring topology, change non-ring topology to ring
topology, verify BTS ring topology, delete a BTS from the ring topology, and manually switch
over the BTS ring topology.
41.5.1 Recommended Configuration of BTS Ring Topology

This provides the recommended configuration of BTS ring topology to meet different network
requirements.
Scenarios
Generally, BTS ring topology is implemented in the following scenarios:
41-8
Communication quality is good and transmission is stable.
Communication quality is poor and transmission is unstable.

Issue 03 (2009-06-08)

Recommended Configurations
Table 41-4 describes the parameter configuration of BTS ring topology in good-quality
transmission.
Table 41-4 Parameter configuration of BTS ring topology in good-quality transmission
Ring
Waiting Time
Before Rotate
(s)
Ring Try
Rotating
Duration
Time(s)
Ring II
Rotating
Penalty
Time(s)
T200
(10ms)
T203 (s)
N200
(time)
60
12
Table 41-5 describes the parameter configuration of BTS ring topology in poor-quality
transmission.
Table 41-5 Parameter configuration of BTS ring topology in poor-quality transmission
Ring
Waiting Time
Before Rotate
(s)
Ring Try
Rotating
Duration
Time(s)
Ring II
Rotating
Penalty
Time(s)
T200
(10ms)
T203 (s)
N200
(time)
30
60
24
41.5.2 Configuring BTS Ring Topology

This describes how to configure the BTS ring topology on the BSC6000 Local Maintenance
Terminal.
Prerequisite
l
The type of BTS ring topology is determined, that is, either BTS ring topology I or BTS
ring topology II.
The service bearing mode is determined, that is, either TDM mode or HDLC mode.
Context
NOTE
This takes adding TDM ring topology on the GEIUB as an example for configuring BTS ring topology I.
This takes adding HDLC ring topology on the GEHUB as an example for configuring HDLC ring topology.
Procedure
l
Configure BTS ring topology I.

1.
Issue 03 (2009-06-08)
On the BSC6000 Local Maintenance Terminal, right-click the GEIUB, and then
select Add Site from the shortcut menu. A dialog box is displayed.
41-9

2.
In the displayed dialog box, click Add Site. Then, in the displayed dialog box, set the
parameters such as SiteType and Site Name, set Configure Ring to Yes, and set
Service Mode to TDM, as shown in Figure 41-4.
Figure 41-4 Add New Site dialog box (TDM)
3.
Click OK and a dialog box is displayed. Specify Reverse Slot No. and Reverse Port
No., as shown in Figure 41-5.
Figure 41-5 Set Rev Info dialog box (1)
41-10

Issue 03 (2009-06-08)

4.
Click OK. A dialog box is displayed, as shown in Figure 41-6.
Figure 41-6 Add Site dialog box (1)
5.
Click Add Site, as shown in Figure 41-6. For details, refer to Adding a BTS (TDM
Transmission Mode).
NOTE
If the BTS in the ring topology supports Flex Abis, you are required to configure Flex Abis.
For details, refer to 39.5.2 Configuring Flex Abis.
Configure BTS ring topology .

1.
On the BSC6000 Local Maintenance Terminal, right-click a BTS and select Site
Operation > Configure Site Attributes from the shortcut menu.
NOTE
BTS ring topology II is configured on the basis of BTS ring topology I.
2.
Issue 03 (2009-06-08)
In the displayed dialog box, click Set Site Attributes. A dialog box is displayed, as

41-11

Figure 41-7 Site Attributes dialog box
3.
41-12
Select the Ring Information tab page, set Configure Ring II to Yes, and set other
parameters, as shown inFigure 41-8.

Issue 03 (2009-06-08)

Figure 41-8 Configuring parameters related to BTS ring topology II
4.
l
Issue 03 (2009-06-08)
Click OK to return to the previous dialog box, and click Finish to end the task.
Configure HDLC ring topology.

1.
On the BSC6000 Local Maintenance Terminal, right-click the GEHUB, and then
select Add Site from the shortcut menu.
2.
In the displayed dialog box, click Add Site. Then, in the displayed dialog box, set the
parameters such as SiteType and Site Name, set Configure Ring to Yes, and set
Service Mode to HDLC, as shown in Figure 41-9.

41-13

Figure 41-9 Add New Site dialog box (HDLC)
3.
41-14
Click OK and a dialog box is displayed. Specify Reverse Slot No. and Reverse Ring
Port No, as shown in Figure 41-10.

Issue 03 (2009-06-08)

Figure 41-10 Set Rev Info dialog box (2)
4.
Click OK. A dialog box is displayed, as shown in Figure 41-11.
5.
Click Add Site, as shown in Figure 41-11. For details, refer to Adding a BTS (HDLC/
HUB Transmission Mode).
----End
41.5.3 Changing Non-Ring Topology to Ring Topology

This describes how to change non-ring topology to ring topology on the BSC6000 Local
Context
Before you change non-ring topology to ring topology, the following prerequisites must be met :
Issue 03 (2009-06-08)

41-15


l
The BTSs must be in the chain topology, and port 1 of the upper-level BTS must be
connected to port 0 of the lower-level BTS.
Only the ring topology parameters of the lowest-level BTS can be modified.
The cables between the lowest-level BTS and the BSC are connected.
CAUTION
During the change from non-ring topology to ring topology, the corresponding BTS is reset and
related alarms are reported.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, right-click a BTS whose ring topology is to
be changed, and then choose Site Operation > Configure Site Attributes . A dialog box is
Figure 41-12 Configure Site Attributes dialog box
Step 2 Select the lowest-level BTS in the ring topology, and then click Set Site Attributes. A dialog
box is displayed.
Step 3 Select the Ring Information tab page, and then set Configure Ring to Yes, as shown in Figure
41-13. Then, Click OK.
41-16

Issue 03 (2009-06-08)

Figure 41-13 Site Attributes dialog box
Step 4 Click OK to return to the upper-level menu.

Step 5 Click Finish to end the task.
NOTE
To change the ring topology to BTS ring topology , refer to the related section in 41.5.2 Configuring
BTS Ring Topology.
----End
41.5.4 Verifying BTS Ring Topology

This describes how to verify the BTS ring topology on the BSC6000 Local Maintenance
Terminal.
Context
BTS ring topology verification happens in the network deployment acceptance phase and the
troubleshooting phase.
Issue 03 (2009-06-08)

41-17

CAUTION
During manual switchover, the corresponding BTS is reset and related alarms are reported.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, choose BTS Maintenance > Maintain Site
> Maintain Ring Network. A dialog box is displayed, as shown in Figure 41-14.
Figure 41-14 Maintain Ring Network dialog box
Step 2 Select a BTS in the ring topology, and then click Query. The Working Port of the BTS is
displayed.
Step 3 Manually switch over the BTS.
Select the BTSs that need to be switched over, and then click Switch.
Step 4 Query the working port of the BTS.
After the BTS is normally started, refer to Step 1 and Step 2 to query the Working Port of the
BTS. If any of the following situations occurs, you can infer that the ring topology is set up
successfully.
41-18

Issue 03 (2009-06-08)

The Working Port queried in Step 2 is 0, and the Working Port queried in this step is 1.
The Working Port queried in Step 2 is 1, and the Working Port queried in this step is 0.
----End
41.5.5 Deleting a BTS from Ring Topology

This describes how to delete a BTS from the ring topology on the BSC6000 Local Maintenance
Terminal.
Prerequisite
CAUTION
Before deleting a BTS, ensure that the E1 cables connected to the target BTS are removed.
Context
If the deleted BTS has lower-level BTSs, the lower-level BTSs are also deleted.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, right-click a BTS in the ring topology, and
then choose Site Operation > Delete Site. A dialog box is displayed, as shown in Figure
41-15.
Figure 41-15 Delete Site dialog box
Issue 03 (2009-06-08)

41-19

Step 2 Select the BTS that needs to be deleted, and then double-click it to add it into the Site List.
Step 3 Click Finish to end the task.
----End
41.5.6 Manually Switching over BTS Ring Topology

This describes how to manually switch over the BTS ring topology on the BSC6000 Local
Prerequisite
The communication between the BSC and the BTS is normal.
Context
When you switch over the forward link to the reverse link, first switch over the highest-level
BTS in the reverse direction and then the other BTSs in sequence. When you switch over the
reverse link to the forward link, first switch over the highest-level BTS in the forward direction
and then the other BTSs in sequence.
CAUTION
The manual switchover of BTS ring topology is critical to operation and maintenance. After
switchover, the BTS cannot work for a period of time, which may affect services. Therefore, be
cautious when performing this operation.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, choose BTS Maintenance > Maintain Site
> Maintain Ring Network. A dialog box is displayed, as shown in Figure 41-16.
41-20

Issue 03 (2009-06-08)

Figure 41-16 Maintain Ring Network dialog box
Step 2 Select BTSs from the Candidate Sites, and click Query. The parameters Working Port, Auto
Switch Enable, Waiting Time Before Switch(s), Try Switching Duration Time(s), RingNet
, and Query Result of the selected BTSs are displayed.
NOTE
The settings of displayed parameters are determined by RingNet . If RingNet is set to No, the value
of RingNet is displayed; if RingNet is set to Yes, the value of RingNet is displayed.
Step 3 Select the BTSs that need to be switched over, and then click Switch. The Maintain Ring
Network dialog box is displayed, as shown in Figure 41-16.
----End

There is no maintenance information about the BTS ring topology.
Alarms
None.
Issue 03 (2009-06-08)

41-21

Counters
None.
41.7 References
None.
41-22

Issue 03 (2009-06-08)

42 BSC Local Switching
42
BSC Local Switching
About This Chapter

42.1 Overview
This provides the definition and describes the purposes of BSC local switching.
42.2 Availability
This lists the NEs, software versions, and other support required for the implementation of BSC
local switching.
42.3 Impact
This describes the impact of BSC local switching on system performance and other features.
This describes the technical aspects of BSC local switching, consisting of start, recovery, and
handover of BSC local switching calls.
42.5 Implementation
This describes how to configure and verify BSC local switching.
This lists the alarms and performance counters related to BSC local switching.
42.7 References
None.
Issue 03 (2009-06-08)

42-1

42.1 Overview
This provides the definition and describes the purposes of BSC local switching.
Definition
BSC local switching refers to a process in which speech signals on the Abis interface loop back
to the MS without passing through the NSS when the calling party and called party are served
by the same BSC, as shown in Figure 42-1. BSC local switching saves transmission resources
of section C.
Figure 42-1 BSC local switching diagram
A
BTS
MSC
MGW
BTS
BSC
TC
MGW
BTS
Speech signal stream of the BSC

local switching between BTSs
controlled by a BSC
Traffic link
Signaling link
NOTE
BSC local switching is performed on the BSC side without involving the NSS. Speech signals do not pass
through the MSC. The transmission resources of section D and section E on the MSC side, however, are
not released.
Purposes
BSC local switching saves transmission resources of the Ater interface.
42-2

Issue 03 (2009-06-08)

Terms
Terms
Definition
BTS local switching
When the calling party and called party are served by the
same BTS or BTS group, speech signals on the Abis
interface loop back to the MS in a BTS or BTS group
without passing through the BSC and MSC.
Loopback restoration
Calls in the local switching state are recovered to the

ordinary conversation state.
Ater
Interface between the GMPS/GEPS and the GTCS
Speech Version
In the GSM communication system, the versions of the

speech coding/decoding algorithm are categorized into
full-rate speech versions 1, 2, and 3 and half-rate speech
versions 1, 2, and 3.
Supplementary services of a
successful call
Indicates the additional services such as call waiting and

call hold, which are provided for users to handle a
successful call.
Supplementary services of
multiparty communication
Supports a simultaneous communication with more than

one party. Supplementary services for multiparty
communication are categorized into two types: multiparty
service and conference call.

Acronyms and
Abbreviations
Full Spelling
ACS
Active Codec Set
TFO
AMR
Adaptive Multi Rate
CIC
Circuit Identity Code
GMPS
GSM Main Processing Subrack
GEPS
GSM Extended Processing Subrack
GTCS
GSM TransCoder Subrack
42.2 Availability
This lists the NEs, software versions, and other support required for the implementation of BSC
local switching.
Issue 03 (2009-06-08)

42-3

NEs Involved
Table 42-1 lists the NEs involved in BSC local switching.
Table 42-1 NEs involved in BSC local switching
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 42-2 lists the versions of GBSS products that support BSC local switching.
Product
Version
BSC
BSC6000
BTS
BTS3012
BTS3012
AE

DTRU
QTRU
DTRU
QTRU
BTS3006C
BTS3002E
BTS3900 GSM
Not supported currently
BTS3900A GSM
DBS3900 GSM
Miscellaneous
The other requirements for BSC local switching are as follows:
42-4
A license is required for BSC local switching.
If IP transmission mode is adopted on the A interface, the BSC local switching is not
supported.
If transmission optimization mode is adopted on the Abis interface, the BSC local switching
is not supported.
Issue 03 (2009-06-08)

If IP transmission mode is adopted on the Abis interface, the BSC local switching is not
supported.
The Hub BTS does not support BSC local switching.
If the BSC Subrack Combination Type is set to BM/TC Together, the BSC local
switching is not supported.
The BSS can perform BSS local switching independently without the MSC cooperation.
If the BSS Loop Switch MSC Cooperate Switch is set to Open, you can infer that the
BSC local switching is controlled by the MSC. If the MSC does not allow BSC local
switching, which is carried in the assignment request message, the BSC local switching is
not supported.
For a group of combined BTSs, if BTS versions support BSC local switching, but carrier
versions of BTSs do not support this feature, BSC local switching cannot be enabled.
The charging of local switching is determined by the NSS.
42.3 Impact
This describes the impact of BSC local switching on system performance and other features.

The impact of BSC local switching on system performance is as follows:
l
After BSC local switching is enabled, the handover success rate may decrease, and the call
drop rate may increase. For details about the causes, refer to 42.4.3 Handover of BSC
Local Switching Call.
When the GTCS is locally configured, BSC local switching should not be enabled because
the transmission line of the Ater interface is relatively short.
After BSC local switching is enabled, the announcement and lawful interception services
of the MSC are not supported. If the MS in the call setup procedure requires to be monitored,
the MSC asks the BSC not to initiate BSC local switching.
If a forced handover is required upon the activation of BTS local switching, the BSC is
unable to request the PCU to convert the PDCH back to TCH and to perform contention
resolution in the channel request process. BSC local switching may fail to be enabled owing
to the unavailability of radio resources.
Enabling BSC local switching may cause discontinuous voice for a short time.

The impact of BSC local switching on other features is as follows:
l
After BSC local switching is enabled, call completion supplementary services and MPTY
supplementary services are not supported.

This describes the technical aspects of BSC local switching, consisting of start, recovery, and
handover of BSC local switching calls.
Issue 03 (2009-06-08)

42-5

42.4.1 Initiation of BSC Local Switching Call

This describes the requirements for the start of BSC local switching call. To initiate a BSC local
switching call, the call must meet the relevant conditions, pass the BSC local switch call check,
comply with the relevant initiation policies, and select the correct speech version for the calling
and called parties.
The process for initiating a BSC local switching call is as follows:
1.
After the called party answers or the incoming BSC handover of speech service is complete,
the BSC checks the conditions for starting BSC local switching. The conditions for starting
BSC local switching are as follows:
l
Whether the license supports BSC local switching.
Whether BSS General Strategy supports BSC local switching.
Whether the call meets the requirement for initiating the BSS General Strategy.
2.
If these conditions are met, the BSC starts local switching call detection to detect whether
the calling and called parties are served by the same BSC.
3.
If the caller and the called party are located under the same BSC, proceed with the following
steps:
l
If Options for BSC Local Switch is set to Prefix Number, and one party meets the
start conditions, BSC local switching is started.
If Avoid Number for BSC is set, and one party meets the closing conditions, BSC local
switching is not started.
When starting BSC local switching, ensure that the voice coding rates of the calling and called
parties are the same. If different voice coding rates are used, the BSC adjusts the different rates
to the same rate through a forcible handover. If the adjustment fails, the BSC local switching is
not initiated. In AMR mode, the same voice coding rate must be used by the caller and the called
party. In addition, the rate is fixed.
When a BSC local switching call selects a speech version, the selected speech version must be
supported by the caller and the called party.
l
If the speech version supported by the caller and the called party intersect, and the speech
version used by the caller and the called party belong to the intersection, select a speech
version according to the policies described in Table 42-3.
Table 42-3 Policies for selecting a speech version for local switching
42-6
AMR
Whether the
ACS Is
Consistent
and Uses the
Same Rate
Full- or HalfRate Channel
Speech
Version
Adjustment
Policy
Both the caller

and the called
party use
AMR.
Consistent
Not involved
Not involved
The conditions
for local
switching are
met. There is
no need for
adjustment.

Issue 03 (2009-06-08)

AMR
Issue 03 (2009-06-08)
Whether the
ACS Is
Consistent
and Uses the
Same Rate
Speech
Version
Adjustment
Policy
Inconsistent
Not involved
Not involved
Both the caller

and the called
party need to be
adjusted.
AMR is used
by either the
caller or the
called party of
a call.
Not involved
Not involved
Not involved
Change an MS
using AMR to a
non-AMR MS.
Ensure that the
specific rate
and speech
version of one
party are
consistent with
those of the
other party.
Neither the
caller nor the
called party
uses AMR.
Not involved
Inconsistent
Not involved
Change a halfrate MS to a
full-rate MS.
Ensure that the
specific rate
and speech
version of one
party are
consistent with
those of the
other party.
Consistent
Same
The conditions
for local
switching are
met. There is
no need for
adjustment.
Different
Change the
speech version
of a high-rate
MS to the
speech
version of a
low-rate MS.
If only one speech version that is being used belongs to the intersection, select the speech
version as the target speech version.

42-7


l
If neither the speech version currently used by the caller nor the speech version currently
used by the called party belongs to the intersection, select the speech version of the highest
version from the intersection. Full rate is preferred when both full rate and half rate are
supported.
NOTE
As the same rate set is used for a call when the call uses Adaptive MultiRate (AMR), AMR is not
selected when neither the speech version used by the caller nor the speech version used by the called
party belongs to the intersection.
When the speech versions used by both parties are consistent, the BSC sets up speech signal
links, and both parties perform TDM switching in the BSC. After the TDM switching is
successful, the call enters the BSC local switching state, and the redundant resources on the Ater
interface are released.
NOTE
The MSC cannot obtain BSC local switching information because speech signals do not pass through the
MSC. To ensure the consistency of circuit resources on the MSC and BSC sides, however, the BSC does
not release the CIC circuit.
42.4.2 Recovery of BSC Local Switching Call

This describes the recovery of BSC local switching call. When a handover occurs during a BSC
local switching call, the target cell may not support local switching or the outgoing BSC handover
fails. In this case, the BSC local switching call must be recovered to an ordinary call.
The BSC resets up the Ater interface transmission channel, and the speech signals are sent to
the MSC through the BSC and then are switched to the MS.
The recovery of the BSC local switching call is determined by the BSC without manual
intervention and configuration parameters.
42.4.3 Handover of BSC Local Switching Call

This describes the handover of BSC local switching call. The intra-BSC handover and outgoing
BSC handover of the BSC local switching call are different from the common handover
mechanism.
Intra-BSC Handover
The difference between the intra-BSC handover of the BSC local switching call and the common
handover is that the speech version cannot be changed during the handover of the BSC local
switching call. That is, the speech version before the handover must be consistent with the
speech version after the handover. The restriction on speech versions may result in the drop of
speech version and the increase of call drop rate.
l
After the intra-BSC handover succeeds, the BSC local switching call may be maintained
or switched to a BTS local switching call and then recovered to an ordinary call depending
on the local switching support capability of the target channel.
If the intra-BSC handover fails, the BSC local switching call is kept in the BSC local
switching state.
Inter-BSC Handover
The process of the inter-BSC handover of a BSC local switching call is as follows:
42-8

Issue 03 (2009-06-08)

1.
Based on the handover decision algorithm, the BSC determines to initiate a BSC handover
by sending a handover request to the MSC.
2.
Upon receipt of the handover request, the MSC issues a handover command to the BSC.
l
Upon receipt of the handover command, the BSC informs the peer end of the local
switching call that the call is restored to a common call. This ensures a normal speech
after the inter-BSC handover succeeds.
If the BSC does not receive the handover command, the BSC local switching call is
maintained.
If the BSC receives the handover failure message reported by an MS, the BSC informs
the caller of the local switching call that the call is restored to a common call.
42.5 Implementation
This describes how to configure and verify BSC local switching.
42.5.1 Configuring BSC Local Switching

This describes how to configure BSC local switching on the BSC6000 Local Maintenance
Terminal.
Prerequisite
l
1.

fill in the actual number of TRXs that support BSC local switching in the Number of
resources column corresponding to the Number of the TRX supporting BSC local
switching in the Resource control items.
2.
Enable the license on the Local Maintenance Terminal. For details, refer to
The SS7 signaling points of the BSC are configured. For how to configure the SS7 signaling
points, refer to Configuring the SS7 Signaling Points.
Procedure
Step 1 Configure BSS local switching (performed by the BSC independently or cooperating with the
MSC) on the BSC.
1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000 and select Configure SS7 Signaling Point from the shortcut menu. A
2.
Click the DSP tab, as shown in Figure 42-2.
Issue 03 (2009-06-08)

42-9

Figure 42-2 Configuring DSP
3.
Select a DSP, and the click Modify DSP. A dialog box is displayed, as shown in Figure
42-3.
Figure 42-3 Modifying DSP
42-10

Issue 03 (2009-06-08)

4.
Set the BSS Loop Switch MSC Cooperate Switch.

l
If the BSC performs BSS local switching independently, set the BSS Loop Switch MSC
Cooperate Switch to Close.
If the MSC cooperates with the BSC for the BSS local switching, set the BSS Loop
Switch MSC Cooperate Switch to Open, and set parameters on the MSC side so that
the BSS local switching is supported.
Step 2 Set parameters involved in BSC local switching on the BSC.

1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000 and select Configure BSS Local Switch from the shortcut menu. A dialog
Figure 42-4 BSS General Strategy
2.
Set BSS General Strategy to BSC Priority or BSC Local Switching.
3.
Set Options for BSC Local Switch.
4.
Issue 03 (2009-06-08)
If Options for BSC Local Switch is set to Start Ater for BSC, set Start Ater
Threshold for BSC. Go to 2.4.
If Options for BSC Local Switch is set to Prefix Number or Unconditional Start,
go to 2.4.
Click Next. A dialog box is displayed, as shown in Figure 42-5.

l
If Options for BSC Local Switch in Figure 42-4 is set to Prefix Number, set Prefix
Number for BSC and Number in the BSC Local Switching Prefix Start tag page.
Go to 2.5.
If Options for BSC Local Switch in Figure 42-4 is set to Unconditional Start, go to
2.5.
42-11

Figure 42-5 BSC Local Switching Prefix Start
5.
42-12
Click the BSC Local Switching Prefix Close tab, as shown in Figure 42-6.
l
If BSC Close Based on Number in Figure 42-4 is set to Yes, set Avoid Number for
BSC and Number. Go to 2.6.
If BSC Close Based on Number in Figure 42-4 is set to No, go to 2.6.

Issue 03 (2009-06-08)

Figure 42-6 BSC Local Switching Prefix Close
6.
Click Finish to complete the configuration of BSC local switching.
----End
42.5.2 Verifying BSC Local Switching

This describes how to verify BSC local switching on the BSC6000 Local Maintenance
Terminal.
Procedure
Step 1 On the BSC6000 LMT window, choose BSC Maintenance > User Resource Maintenance >
Query Call Resources. A dialog box is displayed, as shown in Figure 42-7.
Issue 03 (2009-06-08)

42-13

Figure 42-7 Query result
Step 2 Enter the relevant information in Calling ID. Then, click Query. The result is displayed, as
If BSC local switching is started successfully, the following output is displayed in the Query
Result window:
l
The TC subrack information contains only A interface information instead of Ater

interface information.
The BM subrack information contains Abis interface information.
The activation of BSC local switching is successful.
42-14

Issue 03 (2009-06-08)

Figure 42-8 Query result
----End

This lists the alarms and performance counters related to BSC local switching.
Alarms
None.
Counters
Table 42-4 lists the counters related to BSC local switching.
Issue 03 (2009-06-08)

42-15

Table 42-4 Counters related to BSC local switching
42-16
Counter
Description
R381
Number of Loopback Start Attempts
R3820
Number of Loopback Start Failures (No

Loopback Policy Available)
R3821
Number of Loopback Start Failures (Speech

Version Adjustment Failure)
R3822
Number of Loopback Start Failures (Invalid

State)
R3824
Number of Loopback Start Failure

(Territorial Resource Request Failure)
R3825
Number of Loopback Start Failure (Timer

Expired)
R3826
Number of Loopback Start Failures (Not

Support by the BTS)
R3827
Number of Loopback Start Failures (Other

Causes)
R382b
Number of BSC Loopback Failures after the

Handover during the BTS Loopback
R382c
Number of BTS Loopback Failures after the

Handover during the BSC Loopback
R382d

R3830
Number of Successful BSC Loopback

Attempts
R3830a

Attempts after the Handover during the BTS
Loopback
R3830b

Attempts after the Handover during the BSC
Loopback
R3831b
Number of Successful BTS Loopback

Loopback
CR382
Number of Loopback Start Failures
R3840
Number of Attempts to Return to Normal Call

from BSC Loopback

Issue 03 (2009-06-08)

Issue 03 (2009-06-08)
Counter
Description
R3850a
Number of Failures to Return to Normal Call

from BSC Loopback (Territorial Resource
Request Failure)
R3850b

from BSC Loopback (Others)
CR3850

from BSC Loopback
R3860
Number of Successful Attempts to Return to

Normal Call from BSC Loopback
TR3860
BSC Loopback to Normal Call Success Rate
M3720
Call Drops Due to BSC Loopback Start

Failure (Terrestrial Resource Request
Failure)
M3721
Call Drops Due to BSC Loopback Start

Failure (Others)
M390
Call Drops Due to Loopback Start Failure

(Timer Expired)
CM397
CM398
Call Drops Due to Handover Failure During

the Loopback
M3701
Call Drops Due to Connection Failures in

Stable BSC Loopback State
M3700
Call Drops Due to Error Indications in Stable

BSC Loopback State
M3702
Call Drops Due to Release Indications in

M372
Call Drops Due to No MRs from MS in Stable

BSC Loopback State
M375
Call Drops Due to Forced Handovers in

M373
Call Drops Due to Abis Terrestrial Link

Failure in Stable BSC Loopback State
M374
Call Drops Due to Equipment Failures in

CM370
Call Drops in Stable BSC Loopback State
M3751
Call Drops Due to Failures to Return to

Normal Call from BSC Loopback (Terrestrial

42-17

Counter
Description
M3752

Normal Call from BSC Loopback (Others)
CM385

Normal Call from Loopback
CM390
Call Drops During Loopback
M3852

Normal Call from BTS Loopback (Others)
CM385

CM390
42.7 References
None.
42-18

Issue 03 (2009-06-08)

43 BTS Local Switching
43
BTS Local Switching
About This Chapter

43.1 Overview
BTS local switching is a process in which speech signals are switched to the target MS of a call
through the BTS. It helps save transmission resources.
43.2 Availability
This lists the NEs, software, and other conditions required for the implementation of BTS local
switching.
43.3 Impact
This describes the impact of BTS local switching on system performance and on other features.
This describes the initiation of BTS local switching call, recovery of BTS local switching call,
and handover of BTS local switching call.
43.5 Implementation
This describes how to configure and verify BTS local switching.
The maintenance information about BTS local switch refers to performance counters.
43.7 References
None.
Issue 03 (2009-06-08)

43-1

43.1 Overview
BTS local switching is a process in which speech signals are switched to the target MS of a call
through the BTS. It helps save transmission resources.
Definition
In BTS local switching, the calling and called parties are served by the same BTS or by the same
BTS group. The BTS or BTS group processes the Abis speech signals associated with the call
and transmits the speech signals to the addressed party without routing the speech signals to the
BSC and MSC, as shown in Figure 43-1.
Figure 43-1 BTS local switching diagram
A
(2)
(1)
BTS
MSC
MGW
BTS
BSC
TC
MGW
BTS
Speech signal stream of the BTS local switching

under the same BTS or same BTS group
Traffic link
Signaling link
NOTE
BTS local switching is performed on the BSS side, not involving on the NSS side. The speech signals are
not routed to the MSC. The transmission resources on segments D and E on the MSC side, however, are
not released.
Purposes
With BTS local switching, the transmission resources on the Abis and Ater interfaces are greatly
saved.
43-2

Issue 03 (2009-06-08)

As shown in Figure 43-1, BTS local switching helps save the transmission resources on
segments B and C or on segments A, B, and C.
Terms
Terms
Definition
BSC Local
Switching
In BSC local switching, the two MSs involved in a call are served by the
same BSC. On the Abis interface, the BSC routes the speech signals to the
addressed MS directly without routing the speech signals to NSS. The Ater
transmission resources originally occupied by the call are released and
saved accordingly.
Loopback
restoration
Indicates that a call in the local switching status is restored to a common

call.
Ater
Interface between the GMPS/GEPS and the GTCS
Speech Version
There are different versions of speech codec algorithms available in the

GSM. For example, the full-rate speech versions are numbered 1, 2, and
3, and the half-rate speech versions are also numbered 1, 2, and 3.
Flex Abis
This is a timeslot allocation scheme adopted on the Abis interface. In this

scheme, the channels on the Um interface and the timeslots on the Abis
interface are not long bundled together. Instead, the timeslots on the Abis
interface are allocated dynamically for each call.
Supplementary
services of a
successful call
Indicates the additional services such as call waiting and call hold, which
are provided for users to handle a successful call.
Supplementary
services of
multiparty
communication
Supports a simultaneous communication with more than one party.

Supplementary services for multiparty communication are categorized
into two types: multiparty service and conference call.
BTS ring
topology
Connecting the BTS ring topology to the BSC helps improve the
robustness and reliability of the network. For details about the BTS ring
topology, refer to 41 BTS Ring Topology.
Issue 03 (2009-06-08)
Acronyms and
Abbreviations
Full Spelling
ACS
Active Codec Set
BSC
Base Station Controller
MSC
Mobile Switching Center
CN
Core Network
DPC
Destination (signaling) Point Code

43-3

Acronyms and
Abbreviations
Full Spelling
NRI
Network Resource Identifier
TMSI
IMSI
IMEI
MGW
Media Gateway
NAS
Non Access Stratum
MOCN
Multi-Operator Core Network
43.2 Availability
This lists the NEs, software, and other conditions required for the implementation of BTS local
switching.
NEs Involved
Table 43-1 lists the NEs involved in BTS local switching.
Table 43-1 NEs involved in BTS local switching
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 43-2 lists the versions of GBSS products that support BTS local switching.
Product
43-4
Version
BSC
BSC6000
BTS
BTS3012

DTRU
QTRU

Issue 03 (2009-06-08)

Product
Version
BTS3012
AE
DTRU
QTRU
BTS3006C
BTS3002E
BTS3900 GSM
BTS3900A GSM
DBS3900 GSM
Miscellaneous
BTS local switching has the following limits:
l
A license is required for BTS local switching.
If IP transmission mode is adopted on the A interface, the BTS local switching is not
supported.
If transmission optimization mode is adopted on the Abis interface, the BTS local switching
is not supported.
If IP transmission mode is adopted on the Abis interface, the BTS local switching is not
supported.
The Hub BTS does not support BTS local switching.
BTS local switching is not restricted when BSC Subrack Combination Type is set to
BM/TC together.
The BSS can perform BSS local switching independently without the MSC cooperation.
If BSS Loop Switch MSC Cooperate Switch is set to Open, you can infer that the BSC
local switching is controlled by the MSC. If the BSS local switching is not allowed on the
MSC side, this information is carried in the assignment request message and thus the BTS
local switching is not supported.
BTS local switching and BTS ring topology cannot be enabled for a BTS at the same time.
In the sites with hybrid BTS cabinet groups the BTS local switching cannot be implemented
if the BTS software versions support BTS local switching while the TRX software versions
do not support BTS local switching.
The charging of local switching is controlled by the NSS.
43.3 Impact
This describes the impact of BTS local switching on system performance and on other features.

BTS local switching has the following impact on system performance:
Issue 03 (2009-06-08)

43-5


l
After BTS local switching is enabled, the handover success rate may decrease, and the call
drop rate may increase. For details about the causes, refer to 43.4.3 Handover of BTS
Local Switching Call.
During the process for enabling BTS local switching, temporary audio discontinuity may
occur.
After BTS local switching is enabled, the system does not support the MSC announcement
and lawful interception services. If the MS in the call setup process requires to be
supervised, the MSC instructs the BSC not to initiate BTS local switching.
If a forced handover is required upon the activation of BTS local switching, the BSC is
unable to request the PCU to convert the PDCH back to TCH and to perform contention
resolution in the channel request process. The BTS local switching may fail if no radio
resources are available.
During the process for enabling BTS local switching, temporary audio discontinuity may
occur.

BTS local switching has the following impact on other features:
l
After BTS local switching is enabled, the system does not support the supplementary
services of a successful call or the supplementary services of multiparty communication.
BTS local switching can be enabled only when BTSs support Flex Abis and the timeslot
assignment mode is set to dynamic assignment. For details, refer to 39 Flex Abis.

This describes the initiation of BTS local switching call, recovery of BTS local switching call,
and handover of BTS local switching call.
43.4.1 Initiation of BTS Local Switching Call

This describes the initiation of a BTS local switching call. To initiate a BTS local switch call,
the call must meet the relevant conditions, pass the BTS local switch call check, comply with
the relevant initiation policies, and selects the correct speech version for the calling and called
parties.
The process for initiating the BTS local switching call is as follows:
1.
43-6
After the called party picks up a phone or the speech service is switched to the BSC, the
BSC determines whether the conditions for initiating BTS local switching are met. The
conditions for initiating BTS local switching are as follows:
l
Whether the existing license supports BTS local switching
Whether the BSS General Strategy supports BTS local switching
Whether the call meets the requirement for initiating the BSS General Strategy
2.
If the conditions for initiating BTS local switching are met, the BSC starts checking a local
switching call. That is, through the GTCS, the BSC checks whether the calling and the
called parties are served by the same BSC.
3.
If the calling and called parties are served by the same BSC, proceed with the following
steps:
Issue 03 (2009-06-08)

When Options for BTS Local Switch is set to number prefix for initiation, initiate
BTS local switching if either the calling party or the called party meets the initiation
conditions.
When Avoid Number for BTS is set, do not initiate local switching if either the caller
or the called party meets the closing condition.
When the BTS local switching is started, the speech codec rates of the calling party and called
party must be the same. If different speech codec rates are used, the BSC adjusts the different
rates to the same rate through a forced handover. If the adjustment fails, the BSC local switching
is not initiated. In AMR mode, the same speech codec rate must be used by the calling and called
parties. In addition, the rate is fixed.
When a BTS local switching call selects a speech version, the selected speech version must be
supported by the caller and the called party.
l
If the speech version supported by the caller and the called party intersect, and the speech
version used by the caller and the called party belong to the intersection, select a speech
version according to the policies described in Table 43-3.
Table 43-3 Policies for selecting a speech version for local switching
AMR
Whether the
ACS Is
Consistent
and Uses the
Same Rate
Speech
Version
Adjustment
Policy
Both the caller

and the called
party use
AMR.
Consistent
Not involved
Not involved
The conditions
for local
switching are
met. There is
no need for
adjustment.
Inconsistent
Not involved
Not involved
Both the caller

and the called
party need to be
adjusted.
Not involved
Not involved
Not involved
Change an MS
using AMR to a
non-AMR MS.
Ensure that the
specific rate
and speech
version of one
party are
consistent with
those of the
other party.
AMR is used
by either the
caller or the
called party of
a call.
Issue 03 (2009-06-08)

43-7

AMR
Whether the
ACS Is
Consistent
and Uses the
Same Rate
Speech
Version
Adjustment
Policy
Neither the
caller nor the
called party
uses AMR.
Not involved
Inconsistent
Not involved
Change a halfrate MS to a
full-rate MS.
Ensure that the
specific rate
and speech
version of one
party are
consistent with
those of the
other party.
Consistent
Same
The conditions
for local
switching are
met. There is
no need for
adjustment.
Different
Change the
speech version
of a high-rate
MS to the
speech
version of a
low-rate MS.
If only one speech version that is being used belongs to the intersection, select the speech
version as the target speech version.
If neither the speech version currently used by the caller nor the speech version currently
used by the called party belongs to the intersection, select the speech version of the highest
version from the intersection. Full rate is preferred when both full rate and half rate are
supported.
NOTE
As the same rate set is used for a call when the call uses Adaptive MultiRate (AMR), AMR is not
selected when neither the speech version used by the caller nor the speech version used by the called
party belongs to the intersection.
When the speech version used by the calling and called parties is the same, the BSC issues a
link setup command to the BTS. The call loops back on the Abis interface of the BTS or the
BTS group. After the loopback is successful, the call is switched to the BTS local switching
status. Then, the resources on the Abis and Ater interface are released.
43-8

Issue 03 (2009-06-08)

43.4.2 Recovery of BTS Local Switching Call

When the handover of a BTS local switching call occurs, the TRX of the target channel may not
support local switching or the handover of a particular type may fail. In such a case, a BTS local
switching call must be restored to a common call.
The BSC issues a link setup command to the BTS to re-establish the Abis terrestrial transmission
resource associated with the channel on the Um interface. In the BSC, the transmission channel
on the Ater interface is set up. Speech signals are sent from the BSC to the MSC, which routes
the speech signals to the called party.
The recovery of BTS local switching call is determined by the BSC without human intervention.
There are no configuration parameters available.
43.4.3 Handover of BTS Local Switching Call

The implementation of intra-BSC handover and inter-BSC handover of a BTS local switching
call is different from that of a common handover.
Intra-BSC Handover
The difference between the intra-BSC handover of the BTS local switching call and the common
handover is that the speech version cannot be changed during the handover of the BTS local
switching call. That is, the speech version before the handover must be consistent with that after
the handover. The restriction on speech versions may result in the drop of handover success rate
and the increase of call drop rate.
l
After the intra-BSC handover of a BTS local switching call succeeds, the BTS local
switching call may be retained, be changed to a BSC local switching call, or be restored to
a common call based on the local switching capability of the target channel.
After the BSS receives a handover failure message reported by the MS, the BTS local
switching call is restored to a common call if the BSC receives a handover detection
message. If the BSC does not receive a handover detection message, the BTS local
switching call remains unchanged.
Inter-BSC Handover
The process of the inter-BSC handover of a BSC local switching call is as follows:
1.
Based on the handover decision algorithm, the BSC determines to initiate an inter-BSC
handover by sending a handover request to the MSC.
2.
On receiving the handover request message, the MSC sends a handover command message
to the BSC.
Issue 03 (2009-06-08)
On receiving the handover command message, the BSC informs the peer end of the
local switching call that the call is restored to a common call. This ensures a normal
speech after the inter-BSC handover succeeds.
If the BSC does not receive the handover command message, the BTS local switching
call remains unchanged.
If the BSC receives the handover failure message reported by an MS, the BSC informs
the caller of the local switching call that the call is restored to a common call.

43-9

43.5 Implementation
This describes how to configure and verify BTS local switching.
43.5.1 Configuring BTS Local Switching

This describes how to configure BTS local switching on the BSC6000 Local Maintenance
Terminal.
Prerequisite
l
1.

fill in the actual number of TRXs that support BTS local switching in the Number of
resources column corresponding to the Number of the TRX supporting BTS local
switching in the Resource control items.
2.
Enable the license on the Local Maintenance Terminal. For details, refer to
The SS7 signaling points of the BSC are configured. For how to configure the SS7 signaling
points, refer to Configuring the SS7 Signaling Points.
Procedure
Step 1 Configure BSS local switching (performed by the BSC independently or cooperating with the
MSC) on the BSC.
43-10
1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000 and select Configure SS7 Signaling Point from the shortcut menu. A
2.
Click the DSP tab, as shown in Figure 43-2.

Issue 03 (2009-06-08)

Figure 43-2 Configuring DSP
3.
Select a DSP, and the click Modify DSP. A dialog box is displayed, as shown in Figure
43-3.
Figure 43-3 Modifying DSP
Issue 03 (2009-06-08)

43-11

4.
Set the BSS Loop Switch MSC Cooperate Switch.

l
If the BSC performs BSS local switching independently, set the BSS Loop Switch MSC
Cooperate Switch to Close.
If the MSC cooperates with the BSC for the BSS local switching, set the BSS Loop
Switch MSC Cooperate Switch to Open, and set parameters on the MSC side so that
the BSS local switching is supported.
Step 2 On the BSC, set parameters related to BTS local switching.

1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000 and select Configure BSS Local Switch from the shortcut menu. A dialog
Figure 43-4 General Strategy of the BSS Local Switching
2.
Set BSS General Strategy to BTS Priority or BTS Local Switching.
3.
Configure Options for BTS Local Switch.
4.
43-12
If Options for BTS Local Switch is set to Start Abis for BTS, set Start Abis
Threshold for BSC. Go to 2.4.
If Options for BTS Local Switch is set to Prefix Number or Unconditional Start, go
to 2.4.
Click Next. A dialog box is displayed, as shown in Figure 43-5.

l
If Options for BTS Local Switch in Figure 43-4 is set to Prefix Number, set Prefix
Number for BTS and Number in the BTS Local Switching Prefix Start tag page. Go
to 2.5.
If Options for BTS Local Switch in Figure 43-4 is set to Unconditional Start, go to
2.5.
Issue 03 (2009-06-08)

Figure 43-5 Prefix to start BTS local switch
5.
Issue 03 (2009-06-08)
Click the Segment to Avoid BTS Local Switch tab shown in Figure 43-6.
l
If BTS Close Based on Number in Figure 43-4 is set to Yes, set Avoid Number for
BTS and Number. Go to 2.6.
If BTS Close Based on Number in Figure 43-4 is set to No, go to 2.6.

43-13

Figure 43-6 Segment to avoid BTS local switch
6.
Click Finish to complete the configuration of the BSC.
Step 3 On the BTS, set parameters related to BTS local switching.

1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick a BTS and select Site Operation > Configure Site Attributes from the shortcut
menu.
2.
Select a BTS in the Site View list box and click Set Site Attributes. A dialog box is
Set Support BTS Local Switch to Yes.
43-14

Issue 03 (2009-06-08)

Figure 43-7 Configuring site attributes (2)
3.
Click OK to complete the configuration.
Step 4 Configure the Flex Abis attribute of a BTS.

1.
Issue 03 (2009-06-08)
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the BTS that carries the call and select Site Operation > Modify Site Flex Abis
Mode. A dialog box is displayed, as shown in Figure 43-8.

43-15

Figure 43-8 Configuring the Flex Abis attribute of a BTS
2.
Set Flex Abis Mode to Flex or SemiSolid.
3.
Click Finish to complete the configuration.
----End
43.5.2 Verifying BTS Local Switching

This describes how to verify BTS local switching on the BSC6000 Local Maintenance
Terminal.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal window, choose BSC Maintenance >
Maintain User Resource > Query Single User Resources. A dialog box is displayed, as shown
in Figure 43-9.
43-16

Issue 03 (2009-06-08)

Figure 43-9 Querying single user resources
Step 2 Enter the relevant information in the Calling ID area. Then, click Query. The result is displayed,
If BSC local switching is started successfully, the following information is displayed in the
Query Result pane:
l
TC Subrack Information contains only A Interface Information and does not contain the
Ater interface information.
BM Subrack Information is not available.
Issue 03 (2009-06-08)

43-17

Figure 43-10 Querying single user resources
----End

The maintenance information about BTS local switch refers to performance counters.
Alarms
None.
Counters
Table 43-4 lists the performance counters pertaining to BTS local switch.
43-18

Issue 03 (2009-06-08)

Table 43-4 Performance counters pertaining to BTS local switch
Issue 03 (2009-06-08)
Counter
Description
R380
Number of Call Detect Messages Originated

during Local Switching
R381
Number of Loopback Start Attempts
R3820
Number of Loopback Start Failures (No

Loopback Policy Available)
R3821
Number of Loopback Start Failures (Speech

Version Adjustment Failure)
R3822
Number of Loopback Start Failures (Invalid

State)
R3823
Number of Loopback Start Failures (Failures

on the BTS Side)
R3824
Number of Loopback Start Failure

(Territorial Resource Request Failure)
R3825
Number of Loopback Start Failure (Timer

Expired)
R3826
Number of Loopback Start Failures (Not

Support by the BTS)
R3827
Number of Loopback Start Failures (Other

Causes)
R382b

R382c

R382a

R3831

Attempts
R3830a

Loopback
R3831a

Loopback
R3831b

Loopback
CR382
Number of Loopback Start Failures

43-19
43-20

Counter
Description
R3841
Number of Attempts to Return to Normal Call

from BTS Loopback
R3851a

from BTS Loopback (Territorial Resource
Request Failure)
R3851b

from BTS Loopback (Others)
CR3851

from BTS Loopback
R3861
Number of Successful Attempts to Return to

Normal Call from BTS Loopback
TR3861
BTS Loopback to Normal Call Success Rate
M3820
Call Drops Due to BTS Loopback Start

Failure (Territorial Resource Request
Failure)
M3821

Failure (Failures on the BTS Side)
M3822

Failure (Others)
M390

(Timer Expired)
CM397
CM398
Call Drops Due to Handover Failure During

the Loopback
M3801
Call Drops Due to Connection Failures in

Stable BTS Loopback State
M3800
Call Drops Due to Error Indications in Stable

BTS Loopback State
M3802
Call Drops Due to Release Indications in

M382
Call Drops Due to No MRs from MS in Stable

BTS Loopback State
M385
Call Drops Due to Forced Handovers in

M383
Call Drops Due to Abis Terrestrial Link

Failure in Stable BTS Loopback State
M384
Call Drops Due to Equipment Failures in


Issue 03 (2009-06-08)

Counter
Description
CM380
Call Drops in Stable BTS Loopback State
M3851

Normal Call from BTS Loopback (Territorial
M3852

Normal Call from BTS Loopback (Others)
CM385

CM390
43.7 References
None.
Issue 03 (2009-06-08)

43-21

44 Dynamic MAIO
44
Dynamic MAIO
About This Chapter

44.1 Overview
Dynamic MAIO is used to reduce the co-channel interference and adjacent-channel interference
in the GSM system through the preferential selection of the channels with less interference during
channel assignment.
44.2 Availability
This lists the NEs, software versions, and other support required for the implementation of
dynamic MAIO.
This describes channel assignment, MAIO assignment, and HSN assignment related to dynamic
MAIO.
44.4 Capabilities
This describes the functions that dynamic MAIO supports and the limitations on dynamic MAIO.
44.5 Implementation
This describes how to configure and verify dynamic MAIO.
This lists the alarms and performance counters related to dynamic MAIO.
44.7 References
The references indicate the documents about dynamic MAIO from the related standard
organizations.
Issue 03 (2009-06-08)

44-1

44 Dynamic MAIO
44.1 Overview
Dynamic MAIO is used to reduce the co-channel interference and adjacent-channel interference
in the GSM system through the preferential selection of the channels with less interference during
channel assignment.
Definition
Dynamic MAIO means that channels with less interference are preferentially selected during
channel assignment. If the finally selected channel incurs interference, the minimum MAIO or
HSN is assigned to the channel.
Purposes
Because the frequency resources are limited, much co-channel interference and adjacent-channel
interference occur in the GSM system in the case of aggressive frequency reuse. Dynamic MAIO
can be used to minimize the co-channel interference and adjacent-channel interference for some
channels when frequency hopping is enabled in a cell.
HSN assignment principle: If other channels on the same timeslot with the finally selected
channel in the cell are in the inactive state, and if there are occupied channels on the same timeslot
in all neighbor cells in the BTS, change the HSN of the current channel and select an unused
HSN to reduce the interference between active channels.
Terms
Terms
Definition
Flex MAIO
Dynamic MAIO
HSN
Hopping sequence number
MA
Mobile allocation, that is, a frequency set of the cell frequency hopping
group
MAIO
Mobile allocation index offset
44-2
Acronyms and
Abbreviations
Full Spelling
HSN
Hopping Sequence Number
MA
Mobile Allocation
MAIO
Mobile Allocation Index Offset

Issue 03 (2009-06-08)

44 Dynamic MAIO
44.2 Availability
This lists the NEs, software versions, and other support required for the implementation of
dynamic MAIO.
NEs Involved
Table 44-1 describes the NEs involved in dynamic MAIO.
Table 44-1 NEs involved in dynamic MAIO
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 44-2 lists the software versions of GBSS products that support dynamic MAIO.
Product
Version
BSC
BSC6000
BTS
BTS3X
GBTS32R007C02 and later releases
BTS3002E
BTS3006C
BTS3012
BTS3012A
E
Issue 03 (2009-06-08)
DTRU
QTRU
DTRU
QTRU
BTS3900 GSM
BTS3900A GSM
DBS3900 GSM

44-3

44 Dynamic MAIO
Miscellaneous
The other requirements for dynamic MAIO are as follows:
l
The BTS software must meet the version requirements. For details, refer to Table 44-2. If
the BTS software does not meet the version requirements, call failures may occur.
On the BSC6000 Local Maintenance Terminal, enable the Flex MAIO Switch and
perform channel frequency hopping.

This describes channel assignment, MAIO assignment, and HSN assignment related to dynamic
MAIO.
44.3.1 Dynamic MAIO Channel Assignment

This describes dynamic MAIO channel assignment based on the priority of timeslot interference.
In the case of the same priority, the channel with the least dynamic MAIO timeslot interference
is preferentially selected. During channel frequency hopping, the frequency is related to the MA,
frame number, HSN, and MAIO. According to the 45.002 protocol, the index of the frequency
in the MA table can be calculated as follows:
(S+MAIO)%N
Where, S indicates the frequency index calculated on the basis of the frame number and HSN.
N indicates the number of frequencies in the MA.
According to the formula, when two channels on the same timeslot have the same HSN and MA
and there are some adjacent frequencies in the MA, one of the following cases may occur:
l
The adjacent-channel interference occurs only when two channels on the same timeslot use
the adjacent MAIO.
The co-channel interference occurs only when two channels on the same timeslot use the
same MAIO.
If two channels use different MAs, but the number of frequencies in the MAs and the HSN are
the same, there are adjacent frequencies or the same frequencies between the MAs.
l
If two channels use adjacent frequencies, and the MAIO difference is the same as the
spacing between the two adjacent frequencies in the MA table, the adjacent-channel
interference occurs between the channels.
For example, MA = (1, 2, 5, 7). If the MAIOs used by two channels on the same timeslot
are 0 and 1 respectively, the MAIO difference is 1. If the spacing between adjacent
frequencies 1 and 2 in the MA table is also 1, the adjacent-channel interference occurs
between the two channels.
If two channels use the same frequencies, and if the MAIO difference is the same as the
spacing between the two frequencies in the MA table, the co-channel interference occurs
between the channels.
The weight of co-channel interference in a cell or between cells is the highest. If an MAIO is
assigned, channels on the same timeslot in the BTS cannot be assigned with the same MAIO,
that is, co-channel interference is prohibited in the BTS.
44-4

Issue 03 (2009-06-08)

44 Dynamic MAIO
The TCHF channel interference is eight times the SDCCH/8 interference. The TCHH channel
interference is four times the SDCCH/8 interference. The interference in cells is stronger than
that between cells. The adjacent-channel interference in cells is stronger than the co-channel
interference between cells. When a channel is occupied, it may produce co-channel or adjacentchannel interference to other channels on the same timeslot in the BTS. The timeslot interference
record contains the total interference of all the active channels on the timeslot in the BTS to the
channels in a timeslot in the cell. Based on the current timeslot interference record, channels
with less interference can be selected during channel assignment.
Active channels refer to not only occupied channels but also dynamic or static PDCHs.
According to the characteristics of packet services, if there is a dynamic PDCH or a static PDCH
on the timeslot, the configured HSN or MAIO must be used during the channel activation and
assignment irrespective of circuit services or packet services. Dynamic assignment cannot be
performed. If this channel is configured with an HSN or MAIO, the channel permanently uses
it. The HSN or MAIO of this channel cannot be dynamically assigned to other channels.
Dynamic MAIO does not apply to this channel.
The timeslot interference priority is not the prerequisite for channel assignment. This priority is
higher than the priority of history records, carriers, and interference but lower than the priority
of the TCH rate type and Flex Abis. For details, refer to the description of Huawei II Channel
Assignment Algorithm in 2.3.3 Channel Assignment Algorithms.
44.3.2 Assignment Principle for Dynamic MAIO and HSN

This describes the assignment principle for the dynamic MAIO and HSN.
The assignment principle for the dynamic MAIO and HSN is as follows:
l
If a channel is not for RF frequency hopping, or the configuration type is dynamic PDCH
or static PDCH, the MAIO is not updated. Use the configured data to activate the channel.
If there is an active channel on the same frequency and timeslot, and a subchannel on the
timeslot is assigned, use the HSN and MAIO of the occupied subchannel to activate the
channel.
If the active HSN on the timeslot is different from the configured HSN, use the active
HSN and the configured MAIO to activate the channel.
If there is no active channel on the same timeslot in the cell, but there are active channels
on the same timeslot in all neighbor cells in the BTS and the HSN of active channels in
neighbor cells is the configured HSN, an unused HSN is dynamically assigned. The
HSN for activating the channel is a newly assigned HSN, and the MAIO for activating the
channel is the configured MAIO.
If the timeslot interference record is read based on the timeslot number of the channel, the
configured HSN, and the MAIO of the timeslot and if the channel incurs interference, the
MAIO with the least interference is dynamically assigned and this MAIO is the MAIO
for activating the channel.
44.4 Capabilities
This describes the functions that dynamic MAIO supports and the limitations on dynamic MAIO.
Dynamic MAIO supports the following functions:
l
Issue 03 (2009-06-08)
Assigning the channel with the least interference or the MAIO and HSN to CS calls
44-5

44 Dynamic MAIO
l
Supporting dynamic MAIO assignment in the BTS
The limitations on dynamic MAIO are as follows:

l
Only the function of selecting a channel with the least interference is supported. Dynamic
MAIO assignment is not supported during baseband frequency hopping.
Only circuit services support dynamic MAIO assignment. Packet services do not support
dynamic MAIO assignment.
44.5 Implementation
This describes how to configure and verify dynamic MAIO.
44.5.1 Precautions for Configuring Dynamic MAIO

This provides the precautions for configuring dynamic MAIO.
The limitations for configuring dynamic MAIO are as follows:
l
Each cell can be configured with a maximum of 2 different MAs.
The MAs used by the same timeslot in the same BTS have the same length. The channels
on the same timeslot in the same BTS use the same MA for frequency hopping.
No cells in the BTS are configured with frame offset.
The configuration of Flex MAIO Switch of cells in the same BTS must be consistent.
Because the double-slot extended cell features wide coverage and non-aggressive
frequency reuse, dynamic MAIO does not need to be enabled.
For better performance of the dynamic MAIO algorithm, the frequency hopping data
configuration of the BTS must meet the following requirements:
l
1x1 frequency reuse with BCCH frequencies not joining in frequency hopping
All the frequency hopping channels in the BTS use the same MA and HSN.
1x1 frequency reuse with BCCH frequencies joining in frequency hopping

All the channels on timeslot 0 in the BTS use one set of frequency hopping data {MA0,
HSN0}. All the other channels use another set of frequency hopping data {MA1, HSN1}.
44-6
1x3 frequency reuse with BCCH frequencies not joining in frequency hopping
The frequency hopping data used by the cells in the BTS is different, but the number
of frequencies in all MAs and the HSN are the same.
Adjacent frequencies exist not in MAs but between the MAs.
The frequency hopping data used by all the FH channels in the cell is the same.
1x3 frequency reuse with BCCH frequencies joining in frequency hopping
The frequency hopping data used by the cells in the BTS is different, but the number
of frequencies in all MAs on the same timeslot and the HSN are the same.
Adjacent frequencies exist not in MAs but between the MAs.
The MA used by timeslot 0 in the cell is different from the MA used by other timeslots.
The frequency hopping data used by other timeslots is the same.
Issue 03 (2009-06-08)

44 Dynamic MAIO
44.5.2 Configuring Dynamic MAIO

This describes how to configure dynamic MAIO on the BSC6000 Local Maintenance
Terminal.
Procedure
Step 3 In the displayed dialog box, click Configure Cell Attributes. A dialog box is displayed, as
Issue 03 (2009-06-08)

44-7

44 Dynamic MAIO
Step 4 As shown in Figure 44-1, click Channel Management. Click Advanced, as shown in Figure
44-2.
Figure 44-2 Configuring Flex MAIO channel management parameters in a cell
Step 5 On the HWII Channel Assignment and Radio Channel Control tab page, as shown in Figure
44-2, set Flex MAIO Switch and Flex HSN Switch.
Step 6 Configure the frequency hopping data of the cell to enable the cell to support dynamic MAIO.
For details about the configuration of frequency hopping data, refer to 17 Frequency
Hopping.
----End
44.5.3 Verifying Dynamic MAIO

This describes how to verify dynamic MAIO on the BSC6000 Local Maintenance Terminal.
Prerequisite
The prerequisites for verifying dynamic MAIO are as follows:
l
The BSC6000 Local Maintenance Terminal is started normally.
The communication between the BSC and the BTS is normal.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, click
Trace&Monitor, and then choose Trace > Trace User Message. A dialog box is displayed, as
44-8

Issue 03 (2009-06-08)

44 Dynamic MAIO
Figure 44-3 Tracing User Messages
Step 2 Set parameters in the Interface Type, Tracing Mode, and Color areas. Select and fill in the
IMSI, TMSI, MSISDN, IMEI, or Channel of the user to be traced. Click OK to start tracing.
The result is displayed, as shown in Figure 44-4.
Figure 44-4 Result of tracing user messages
Issue 03 (2009-06-08)

44-9

44 Dynamic MAIO
Step 3 Double-click the CHANNEL ACTIVATION area. A window is displayed, as shown in Figure
44-5.
Figure 44-5 Viewing Messages
If the messages shown in Figure 44-5 contain frequency hopping attributes, you can infer that
dynamic MAIO is enabled. Otherwise, dynamic MAIO is not enabled.
----End

This lists the alarms and performance counters related to dynamic MAIO.
Alarms
None
Counters
None
44-10

Issue 03 (2009-06-08)

44 Dynamic MAIO
44.7 References
The references indicate the documents about dynamic MAIO from the related standard
organizations.
The references are as follows:
l
GSM 05.03 V7.3.1

"Digital cellular telecommunications system (Phase 2+); Channel coding"
GSM 05.09 V7.7.1

"Digital cellular telecommunications system (Phase 2+); Link Adaptation"
GSM 04.08 V7.21.0

"Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3
specification"
GSM 06.90 V7.2.1

"Digital cellular telecommunications system (Phase 2+); Adaptive Multi-Rate (AMR)
speech transcoding"
GSM 06.91 V7.1.1

"Digital cellular telecommunications system (Phase 2+); Substitution and muting of lost
frames for Adaptive Multi Rate (AMR) speech traffic channels"
GSM 06.92 V7.1.1

"Digital cellular telecommunications system (Phase 2+); Comfort noise aspects for
Adaptive Multi-Rate (AMR) speech traffic channels "
GSM 06.93 V7.5.0

"Digital cellular telecommunications system (Phase 2+); Discontinuous transmission
(DTX) for Adaptive Multi Rate (AMR) speech traffic channels"
GSM 06.94 V7.1.1

"Digital cellular telecommunications system (Phase 2+); Voice Activity Detection (VAD)
for Adaptive Multi-Rate speech traffic channels"
GSM 08.08 V7.7.0

"Digital cellular telecommunications system (Phase 2+); Mobile-services Switching Centre
- Base Station System (MSC - BSS) interface; Layer 3 specification"
GSM 08.58 V7.4.1

"Digital cellular telecommunications system (Phase 2+); Base Station Controller - Base
Transceiver Station (BSC - BTS) interface; Layer 3 specification"
GSM 08.60 V7.3.0

"Digital cellular telecommunications system (Phase 2+); In-band control of remote
transcoders and rate adaptors for full rate traffic channels"
GSM 08.61 V7.3.0

"Digital cellular telecommunications system (Phase 2+); In band control of remote
transcoders and rate adaptors for half rate traffic channels"
Issue 03 (2009-06-08)

44-11

45 Antenna Hopping
45
Antenna Hopping
About This Chapter

45.1 Overview
This describes antenna hopping. Antenna hopping enables the random transmission of downlink
data of each carrier on other carriers. This optimizes the data reception of the MS from the main
BCCH carrier and the data transmission of the main BCCH carrier, thus improving the network
performance.
45.2 Availability
This lists the NEs and software required for the implementation of antenna hopping.
This describes the technical aspects of antenna hopping. Through the hopping bus, the data of
a carrier can be randomly transmitted on other carriers. Antenna hopping is implemented on the
basis of the hopping bus and the antenna hopping algorithm.
45.4 Implementation
This describes how to configure antenna hopping.
This lists the alarms related to antenna hopping.
45.6 References
Issue 03 (2009-06-08)

45-1

45 Antenna Hopping
45.1 Overview
This describes antenna hopping. Antenna hopping enables the random transmission of downlink
data of each carrier on other carriers. This optimizes the data reception of the MS from the main
BCCH carrier and the data transmission of the main BCCH carrier, thus improving the network
performance.
Definition
Antenna hopping enables the random transmission of downlink data of each carrier on other
carriers.
During antenna hopping, the data on the main BCCH carrier is randomly transmitted on other
carriers, and the data on other carriers is also randomly transmitted on the main BCCH carrier.
Purposes
In a GSM cell, the frequency, frame number, system information, and paging group are
transmitted on the BCCH of the main BCCH carrier. These broadcast messages are used by the
MS in idle mode to search for a network and by the MS in dedicated mode to measure the
neighbor cell.
If the MS is located in a place where it is difficult to receive the messages from the main BCCH
carrier or if the antenna for the main BCCH carrier is damaged, the MS cannot receive the
broadcast control messages from the BCCH carrier properly.
Similar to baseband frequency hopping, antenna hopping enables the data of all the timeslots on
the main BCCH carrier to be transmitted on the antennas of all the carriers in the cell in sequence.
This increases the space diversity of the main BCCH signals, and optimizes the data reception
of the MS from the main BCCH carrier and the data transmission of the main BCCH carrier.
Therefore, the network performance is improved.
Terms
Terms
Definition
Hopping Bus
Data bus that receives the external carrier data in baseband frequency
hopping or antenna hopping
Timeslot
Interval
Hardware interruption every 577 s specified in GSM Rec. 05.02
45-2
Acronyms and
Abbreviations
Full Spelling
CA
Cell Allocation
FN
Frame Number
Issue 03 (2009-06-08)

45 Antenna Hopping
Acronyms and
Abbreviations
Full Spelling
MAIO
Mobile Allocation Index Offset
HSN
Hopping Sequence Number
MA
Mobile Allocation
FH-BUS
Frequency Hopping Bus
D-BUS
DATA-BUS
RF
Radio Frequency
TRX
Transceiver
45.2 Availability
This lists the NEs and software required for the implementation of antenna hopping.
NEs Involved
Table 45-1 lists the NEs involved in antenna hopping.
Table 45-1 NEs involved in antenna hopping
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l : not involved
l : involved
Software Releases
Table 45-2 lists the versions of GBSS products that support antenna hopping.
Product
Version
BSC
BSC6000
BTS
BTS3012
BTS3012AE
Issue 03 (2009-06-08)

DTRU
QTRU
DTRU

45-3

45 Antenna Hopping
Product
Version
QTRU
BTS3006C
BTS3002E
DBS3900 GSM
BTS3900 GSM
BTS3900A GSM
Miscellaneous
None.

This describes the technical aspects of antenna hopping. Through the hopping bus, the data of
a carrier can be randomly transmitted on other carriers. Antenna hopping is implemented on the
basis of the hopping bus and the antenna hopping algorithm.
45.3.1 Hopping Bus

This describes the hopping bus. The hardware of antenna hopping is implemented based on the
hardware of baseband frequency hopping.
During baseband frequency hopping and antenna hopping, a large number of data exchanges
are performed between different carriers in the same cabinet. The hopping bus is introduced to
facilitate data exchanges. When antenna hopping is realized, each carrier sends the TX
frequency, TX ID, and data of the current frame to the hopping bus during the timeslot interval.
The carrier receives the corresponding frequency and data from the hopping bus and configures
the RF based on the frequency. Then, the RF sends the data to the MS over the Um interface.
Figure 45-1 shows the position of the hopping bus in the BTS.
45-4

Issue 03 (2009-06-08)

45 Antenna Hopping
Figure 45-1 Position of the hopping bus in the BTS
ANT
DBUS
FH_BUS
TRX1
ANT
TRXn
DBUS
45.3.2 Antenna Hopping Algorithm

This describes antenna hopping algorithm. Through the antenna hopping frequency list and the
ID algorithm, antenna hopping algorithm ensures that the frequency and data of each frame on
the hopping bus is unique and has a one-to-one relation with the carrier number.
Build the antenna hopping frequency list based on the frequency information configured on the
BSC side. The BTS searches for the frequency from the antenna hopping frequency list when it
needs to send the antenna hopping frequency. When calculating the antenna ID, enter the carrier
number to calculate an offset based on the frame number and timeslot number of the carrier
number, and then obtain an unique antenna hopping ID based on the offset.
Figure 45-2 shows the procedure for transmitting the data in antenna hopping.
Issue 03 (2009-06-08)

45-5

45 Antenna Hopping
Figure 45-2 Procedure for transmitting the data in antenna hopping

Start
Receives the data
to be transmitted
Antenna
hopping or not?
No
Yes
Frequency
hopping or not?
No
Transmit on the local TRX
Update the antenna

hopping frequency list
with non frequency
Yes
Update the antenna hopping
frequency list with frequency
Search for the
frequency from the antenna
Calculate the
antenna hopping ID
Send the data to the
frequency hopping bus
End
Figure 45-3 shows the procedure for receiving the data in antenna hopping.
45-6

Issue 03 (2009-06-08)

45 Antenna Hopping
Figure 45-3 Procedure for receiving the data in antenna hopping

Start
Check for the data on

frequency hopping bus
The data matches

the ID of the TRX?
No
No handling
Yes
Receive the data
Send the data to the MS

over the Um interface
End
45.4 Implementation
This describes how to configure antenna hopping.
45.4.1 Configuring Antenna Hopping

This describes how to configure antenna hopping on the BSC6000 Local Maintenance
Terminal.
Prerequisite
Antenna hopping is mainly applied in the cells with poor radio propagation conditions and poor
Um interface quality.
Context
When baseband frequency hopping and antenna hopping are applied at the same time, adhere
to the following principles:
l
The number of baseband frequency hopping groups must be the same as that of antenna
hopping groups.
One carrier number must belong to the baseband frequency hopping group and the antenna
hopping group with the same group number.
Issue 03 (2009-06-08)

45-7

45 Antenna Hopping
Procedure
the cell where antenna hopping is to be modified, and then choose Configure Cell Attributes
from the shortcut menu.
Selected cells list box.
Step 3 Click Next. In the displayed dialog box, select the target cell from the Cells to be set list box,
and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 45-4.
Step 4 Click Antenna Hopping. A dialog box is displayed. Set CELL Antenna Hopping to YES, and
set Group Number, Current Group No., HSN, and corresponding TRXs, as shown in Figure
45-5.
45-8

Issue 03 (2009-06-08)

45 Antenna Hopping
NOTE
Antenna hopping is configured in a cell. Each cell can be configured with more than one antenna
hopping group.
When a TRX in an antenna hopping group incurs a fault, the BSC requests that antenna hopping be
disabled in this antenna hopping group. If the faulty TRX recovers, antenna hopping is enabled in the
antenna hopping group.
Figure 45-5 Configure Cell Antenna Hopping dialog box
CAUTION
Do not set HSN to 0 (cyclic hopping), because this leads to low quality of interference source
diversity.
----End
45.4.2 Verifying Antenna Hopping

This describes how to verify antenna hopping. Antenna hopping is invisible to the MS. To verify
antenna hopping, you must use a spectrum analyzer to check whether there are continuous output
signals on the main BCCH frequencies on the main BCCH carrier. If the signals are
discontinuous, the antenna hopping is enabled.
Issue 03 (2009-06-08)

45-9

45 Antenna Hopping

This lists the alarms related to antenna hopping.
Alarms
Table 45-3 lists the alarms related to antenna hopping.
Table 45-3 Alarms related to antenna hopping.
Alarm ID
Alarm Name
4114
Interior I/O Alarm
2126
TRX Interior I/O Alarm
3584
DRU Interior I/O Alarm
Counters
None.
45.6 References
l
GSM 05.02 V7.0.0 (1999-03)

Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access
on the radio path
GSM 05.02 V7.0.0 (1999-03)

Digital cellular telecommunications system (Phase 2+); Channel coding
45-10

Issue 03 (2009-06-08)

46 Voice Quality Index
46
Voice Quality Index
About This Chapter

46.1 Overview
This describes the definition and purposes of applying VQI.
46.2 Availability
This lists the NEs and software required for the implementation of VQI.
This describes the technical aspects of VQI.
46.4 Implementation
This describes how to configure and verify VQI.
This lists the counters related to VQI.
46.6 References
None.
Issue 03 (2009-06-08)

46-1

46.1 Overview
This describes the definition and purposes of applying VQI.
Definition
Voice Quality Index (VQI) defines the mapping between the radio transmission performance
and the voice quality.
Purposes
Through the VQI, the influence of the radio transmission performance on the voice quality can
be measured in a direct way.
Terms
Terms
Definition
MOS analysis
A method for assessing the voice quality with a group of people who answer
phones in a room.
The ITU-T P.800 defines the assessment of the selected voice samples that
adopt the TFO and compression algorithm. The assessment is made by a
group of male and female expert audience on certain conditions. The
assessment result is the MOS, which is classified into five levels. Level 1
indicates the poorest and Level 5 the best.
CHR
CHR is a system for quick fault location. It can record and store the faults
during calls for each user on a CHR server. You can query the call history
records of a specific user on a CHR client to quickly locate the faults if
necessary.
46-2
Acronyms
and
Abbreviatio
ns
Full Spelling
VQI
Voice Quality Index
BER
Bit Error Ratio
FER
Frame Error Rate
LFE
Longest Consecutive Frame Error
DTX
MOS
Mean Opinion Score
CHR
Call History Record

Issue 03 (2009-06-08)

46.2 Availability
This lists the NEs and software required for the implementation of VQI.
NEs Involved
Table 46-1 lists the NEs involved in VQI.
Table 46-1 NEs involved in VQI
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
-: not involved
: involved
Software Releases
Table 46-2 lists the versions of GBSS products that support VQI.
Product
Version
BSC
BSC6000
BTS
BTS3012
BTS3012AE

DTRU
QTRU
DTRU
QTRU
BTS3006C
BTS3002E
DBS3900 GSM
BTS3900 GSM
BTS3900A GSM
Miscellaneous
None.
Issue 03 (2009-06-08)

46-3


This describes the technical aspects of VQI.
46.3.1 Principle of Voice Quality Index

This describes the assessment of voice quality with the establishment of the mapping model
between the radio transmission performance and the voice quality.
VQI model
Figure 46-1 shows the VQI model.
Figure 46-1 VQI model
BSC(traffic statistics)
BSC
BTS
BER
Short-time
VQI
FER
HO
DTX
Nonlinear
calculation
Handover
Nonlinear
calculation
Long-time
VQI
Calculate
the
average
value
VQI
CODE
The VQI model involves the following operations:

1.
Collecting information about the radio transmission performance, including the BER, FER,
and HO.
2.
Recording other information, including the DTX and the Codec modes. The DTX is used
to filter the valid statistics of the FER/BER/HO; the Codec is used to filter the mapping
between the radio transmission performance and the voice quality.
3.
Processing the parameters according to the preceding information.
4.
Performing nonlinear processing, such as normalizing the BER according to the Codec
modes.
5.
Performing linear prediction to obtain an estimated VQI score.
The preceding analysis shows that the voice quality is determined by the bit errors and frame
errors (including packet loss) information; that is, VQI=F(BER,FER).
46-4
The principle of the coder determines that the voice quality depends on the erroneous frames
and lost frames. The VQI score is related to the FER to the power of x; that is, VQI
FERx.
The voice quality is related not only to the measurement of FER but also to the distribution
of the erroneous frames. Thus, the variable LFE is applied to represent their relation, that
is, VQILFE.
Issue 03 (2009-06-08)

l
In the GSM TCH, the frames verified by the 3-bit CRC mechanism might contain residual
erroneous codes. Thus, the formula VQIBER should be applied.
In conclusion, the formula for the relation between the VQI and the radio transmission
performance is VQI = A BER + B FER + C LEF + Const.
NOTE
In the formula, A, B, and C are the model parameters, and Const is a constant.
Rectification of the VQI Model

To ensure higher credibility of the estimated VQI score, a large number of tests must be
performed to yield the data for adjustment and rectification.
Figure 46-2 shows the principle of rectifying the VQI model.
Figure 46-2 Principle of rectifying the VQI model
RX end
Channel
decoding
Source
decoding
Channel
decoding
Multiparameter
modeling
Speech RX
VQI model
Channel
decoding
The VQI model is rectified by comparing the radio performance parameters such as BER, FER,
and LFE at the receiving end and comparing the voice quality of the received calls.
46.3.2 Measurement of Voice Quality

This describes the measurement of the voice quality. The VQI classifies the voice quality into
11 levels. During a call, the VQI score of each level is counted and the average VQI score is
measured. The average VQI score is used as the performance counter for assessing the voice
quality of the TRX carrying this call.
Obtaining the VQI Information

In each call, when the parameter Voice quality report switch is enabled, the TRX receives the
customized extended measurement reports from the BTS every five measurement periods (five
measurement periods last 2.4 seconds). The uplink measurement reports contain the short-time
VQI information.
NOTE
The VQI information reported in five measurement report periods is called the short-time VQI information.
Issue 03 (2009-06-08)

46-5

Classification of VQI Scores

The MOS analysis method is applied in VQI to measure the voice quality. MOS is used to assess
the quality of the middle- and low-rate voice codec modes. The MOS score ranges from 1 to 5.
l
5: Excellent
4: Good
3: Fair
2: Poor
1: Unsatisfactory
Measurement of Voice Quality

The methods for measuring VQI voice quality are as follows:
l
Voice quality levels

Based on the score range of the MOS analysis method, the voice quality is further classified
into 11 levels for measuring performance, as listed in Table 46-3.
Table 46-3 Voice quality levels
Level
Meaning
Initial level
voice quality < 0.5
Level 1
0.5 < voice quality < 1.0
Level 2
Level 3
Level 4
Level 5
Level 6
Level 7
Level 8
Level 9
Level 10
voice quality > 5.0
Measurement of long-time VQI scores

The long-time VQI score is the sum of all short-time VQI scores during a call. In each call,
the number of short-time VQI scores of each level and the total short-time VQI scores are
measured, and then the average VQI score is measured according to the total long-time
VQI scores and the number of VQI scores.
When a call is released, the number of VQI scores of each level and the average VQI score
are output to the CHR and used as the counters of the voice quality of the TRX carrying
this call.
46-6

Issue 03 (2009-06-08)

If the VQI is used to collect statistics of voice quality, the voice quality of the HR TRX
and the voice quality of the FR TRX must be measured respectively. The type of the TRX
does not affect the counters.
NOTE
To avoid floating-point calculation when the VQI performance is measured, the VQI score is multiplied
by 50 and then the result is converted into an integer. The integer is sent to the BSC. After receiving
the VQI score, the BSC forwards the score to the M2000 for processing. The M2000 divides the value
by 50 and then obtains the average short-time VQI score.
After receiving the VQI scores, the BSC divides the scores by 50 and then obtains the scores ranging
from 0 to 5.1. The BSC measures the performance information with the scale as 0.5 scores. That is,
the number of measurement reports with the VQI score range as 00.5 indicates the number of
measurement reports with the VQI score smaller than 0.5. Other levels are deduced by analogy.
46.4 Implementation
This describes how to configure and verify VQI.
46.4.1 Configuring Voice Quality Index

This describes how to configure VQI on the BSC6000 Local Maintenance Terminal.
Procedure
Issue 03 (2009-06-08)

46-7

Step 4 Click Other Attributes. A dialog box is displayed, as shown in Figure 46-4.
Set Voice quality report switch to report.
46-8

Issue 03 (2009-06-08)

----End
46.4.2 Verifying Voice Quality Index

This describes how to verify VQI on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the Management Tree panel of the BSC6000 Local Maintenance Terminal, select the
Trace&Monitor tab. On the tab page, choose Trace > Trace User Message and double-click
it. A dialog box is displayed, as shown in Figure 46-5.
Issue 03 (2009-06-08)

46-9

Figure 46-5 Trace User Message dialog box
Step 2 Set the parameters Interface Type, Tracing Mode, and Color. Select and fill in the IMSI,
TMSI, MSISDN, IMEI, or Channel of the user to be traced. Click OK to start tracing. The
result is displayed, as shown in Figure 46-6.
46-10

Issue 03 (2009-06-08)

Figure 46-6 Result of tracing the user message
Step 3 Select Preprocessed Measurement Result (If the preprocessed measurement result function is
not enabled, select Measurement Result). Double-click it. A dialog box is displayed, as shown
in Figure 46-7.
Issue 03 (2009-06-08)

46-11

Figure 46-7 Message explanation
In Figure 46-7,
l
if the tlv-type-vqir field exists, it indicates that the BTS reports the VQI information.
otherwise, the BTS does not report the VQI information.
----End

This lists the counters related to VQI.
Alarms
None.
Counters
Table 46-4 lists the counters related to VQI.
46-12

Issue 03 (2009-06-08)

Table 46-4 Counters

Counter
Description
S4504
Number of the Measurements of the FR VQI

(Voice Quality Index) in the Customized MR
S4505
Total Number of the Measurements of the FR VQI

S4506
Number of the Measurements of the HR VQI

S4507
Total Number of the Measurements of the VQI

S4513
Number of Customized MRs with Voice Quality

Rank Smaller than 0.5
S4514

Rank Greater than 0.5 and Smaller than 1.0
S4515

S4516

S4517

S4518

S4519

S4520

S4521

S4522

S4523

Rank Greater than 5.0
46.6 References
None.
Issue 03 (2009-06-08)

46-13

47
47 Automatic Noise Restraint
Automatic Noise Restraint
About This Chapter

47.1 Overview
This describes the definition and purposes of applying the automatic noise restraint (ANR). ANR
improves the speech quality in the case that the background noise exists.
47.2 Availability
This lists the NEs and software required for the implementation of ANR.
This describes the technical aspects of ANR. The ANR mechanism periodically analyzes the
speech signals. Through energy estimation, SNR estimation, sound measurement estimation,
and frequency offset estimation of different frequency bands, ANR identifies the background
noise and performs the filtering based on decision updates to obtain the time speech signals after
noise cancellation.
47.4 Implementation
This describes how to configure ANR.
None.
47.6 References
None.
Issue 03 (2009-06-08)

47-1

47.1 Overview
This describes the definition and purposes of applying the automatic noise restraint (ANR). ANR
improves the speech quality in the case that the background noise exists.
Definition
ANR processes the uplink speech signals after decoding and filters the background noise.
Purposes
ANR reduces the background noise in the uplink speech signals and improves the SNR and
speech intelligibility. Thus, the speech signals are clear on the peer end.
Terms
Terms
Definition
Speech intelligibility
Intelligibility of speech information.
Window
General method for speech preprocessing, like Haming

window.

Acronyms
and
Abbreviation
s
Full Spelling
ANR
Automatic Noise Restraint
SNR
Signal Noise Ratio
FFT
Fast Fourier Transform Algorithm
IFFT
Inverse Fast Fourier Transform Algorithm
TFO
47.2 Availability
This lists the NEs and software required for the implementation of ANR.
NEs Involved
Table 47-1 lists the NEs related to ANR.
47-2

Issue 03 (2009-06-08)

Table 47-1 NEs related to ANR

MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 47-2 lists the versions of GBSS products that support ANR.
Product
BSC
Version
BSC6000

releases
Miscellaneous
None.

This describes the technical aspects of ANR. The ANR mechanism periodically analyzes the
speech signals. Through energy estimation, SNR estimation, sound measurement estimation,
and frequency offset estimation of different frequency bands, ANR identifies the background
noise and performs the filtering based on decision updates to obtain the time speech signals after
noise cancellation.
The procedure for the ANR is as follows:
1.
The system performs weighting and window processing on the speech signals.
2.
The system performs FFT to convert time-domain speech signals into frequency-domain
speech signals.
3.
The system divides the generated frequency speech signals into 16 bands for energy
estimation.
4.
The system performs the SNR estimation based on the noise energy of each band.
5.
After the SNR estimation, each SNR is associated with a sound measurement estimation
value. The system accumulates the sound measurement estimation values of 16 bands to
obtain the sum.
6.
The system performs the frequency offset estimation.

(1) The transient energy of each band is expressed in unit dB.
(2) The system compares the transient energy with the mean energy of each band.
Issue 03 (2009-06-08)

47-3

(3) The system obtains the frequency offset of each band. The accumulated frequency
offset of all the bands is the overall frequency offset estimation.
NOTE
The mean energy of each band is calculated through the smooth method. The smooth coefficient is
related to the total energy of current frames and must be calculated for each frame.
7.
The signals with a lower sound measurement or lower frequency offset are identified as
the noise signals.
8.
The system calculates the frequency band gain.

NOTE
The frequency band gain is SNR-related and should not exceed 1.
9.
After the noise identification, the frequency speech signals of each band are weighted by
its band gain to complete the frequency filtering.
10. The system restores the time-domain speech signals using the IFFT.
CAUTION
l
ANR takes effect in real time.
If TFO is activated in a call, ANR automatically becomes unavailable in the call.
When you use a speech quality test device (for example, DSLA), disable ANR to obtain
the accurate test data.
47.4 Implementation
This describes how to configure ANR.
47.4.1 Configuring ANR

This describes how to configure ANR on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the BSC Device Panel of the BSC6000 Local Maintenance Terminal, right-click a
GDPUC or a GDPUX, and then select Configure Board Attributes from the shortcut menu.
Step 2 In the displayed dialog box, set Load Key, and then click Next.
Step 3 In the displayed dialog box, select Configure All and set ANR Switch to Open, as shown in
Figure 47-1.
47-4

Issue 03 (2009-06-08)

Figure 47-1 Configuring the ANR switch
Step 4 Click Finish. The configuration is complete.

----End
Postrequisite
Make a call from an MS to a fixed telephone. Determine whether the background noise received
on the fixed telephone end is reduced and whether the speech quality is improved.

None.
Alarms
None.
Counters
None.
47.6 References
None.
Issue 03 (2009-06-08)

47-5

48
48 Intelligent Power Consumption Decrease
Intelligent Power Consumption

Decrease
About This Chapter

48.1 Overview
Intelligent power consumption decrease is to decrease the power consumption of the BTS in idle
time periods.
48.2 Availability
This lists the NEs and software required for the implementation of intelligent power consumption
decrease.
Intelligent power consumption decrease refers to a technique in which the system can decrease
power consumption by adjusting the working voltage of the configured TRX module, shutting
down the power amplifier configured with the TRX module when the TRX module is idle, or
shutting down the power amplifier not configured with the TRX module.
48.4 Implementation
This describes how to configure intelligent power consumption decrease on BSCs, cells, and
TRX modules.
The relevant maintenance information on intelligent power consumption decrease is not
available.
48.6 References
None.
Issue 03 (2009-06-08)

48-1

48.1 Overview
Intelligent power consumption decrease is to decrease the power consumption of the BTS in idle
time periods.
Definition
Intelligent power consumption decrease applies to the following scenarios:
l
For the BTS main equipment that does not process services, the dormant mode is started
to decrease the power consumption.
When the BTS main equipment operates normally and processes services, intelligent power
consumption decrease is performed to decrease the power consumption of the BTS in the
same coverage.
Huawei BSS products implement intelligent power consumption decrease through the following
methods:
l
Power-off of power amplifier on the timeslot level
Intelligent voltage adjustment
Preferential assignment of the BCCH

For details about the preferential assignment of the BCCH, see 2 Channel Management.
Power control
For details about power control, see 6 Power Control.
DTX
For details about DTX, see 27 Discontinuous Transmission and Discontinuous
Reception.
Use of industry-leading power amplifiers
Purposes
When the traffic is light, the power amplifiers of idle TRX modules are shut down to decrease
the power consumption of the BTS.
In the current network, many cells are in the idle state in most of time of a day. Thus, part of
TRX modules are sufficient for carrying the existing traffic. In such a case, the power amplifiers
of extra TRX modules can be shut down to save more power. As a result, the operator's operation
expenditure is greatly reduced.
Terms
48-2
Term
Definition
GMSK modulation mode
Gaussion Minimum Shift Keying modulation

mode
XMU
General name for BTS3012 DTMU,

BTS3012AE DTMU, BTS3006C DMCM,
and BTS3002E DMCM
Issue 03 (2009-06-08)

Term
Definition
8PSK modulation mode
8 Phase Shift Keying modulation mode
TCHF
Full-rate traffic channel
TCHH
Half-rate traffic channel

Acronym and
Abbreviation
Full Spelling
DTX
48.2 Availability
This lists the NEs and software required for the implementation of intelligent power consumption
decrease.
NEs Involved
Table 48-1 lists the NEs involved in intelligent power consumption decrease.
Table 48-1 NEs involved in intelligent power consumption decrease
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 48-2 lists the versions of GBSS products that support intelligent power consumption
decrease.
Product
Issue 03 (2009-06-08)
Version
BSC
BSC6000
BTS
BTS3012

DTRU

48-3

Product
Version
BTS3012AE
QTRU
DTRU
QTRU
BTS3006C
BTS3002E
DBS3900 GSM
BTS3900 GSM
BTS3900A GSM
Miscellaneous
None.

Intelligent power consumption decrease refers to a technique in which the system can decrease
power consumption by adjusting the working voltage of the configured TRX module, shutting
down the power amplifier configured with the TRX module when the TRX module is idle, or
shutting down the power amplifier not configured with the TRX module.
Dynamic Voltage Adjustment

Dynamic voltage adjustment is a preferred option for the configured TRX module.
The actual working voltage of the TRX module is adjusted according to the following
configurations:
l
Site type
Macro BTS or mini BTS
Power types of the TRX module
Modulation mode of the TRX module

GMSK modulation mode or 8PSK modulation mode
Frequency band types of the TRX module
Static power class configured for the TRX module
Intelligent Shutdown of the Power Amplifier

Based on the traffic volume, the BSC determines whether to issue a command to switch off the
power amplifier of the TRX module to decrease the power consumption of a BTS.
48-4

Issue 03 (2009-06-08)

48.3.1 Intelligent Power Consumption Decrease Configured with

the TRX Module
This describes the conditions and process of dynamic voltage adjustment, intelligent shutdown
of the power amplifier, and power-on of the power amplifier in case one or two carriers are
configured.
Dynamic Voltage Adjustment

Different from the BTS without the TRX module, the BTS with the TRX module needs voltage
adjustment.
The modulation modes used by the TRX module are categorized into the following types:
l
GMSK modulation mode

In GMSK modulation mode, the decrease of working voltage in a permissible range does
not affect the output power of the power amplifier. Adjusting the working voltage of the
power amplifier can improve the efficiency of the power amplifier and decrease power
consumption.
8PSK modulation mode

You can determine that the TRX module operates in 8PSK modulation mode only when
the following conditions are met:
The TRX supports the EDGE service.
More than one PDCH channel is available.
Intelligent Shutdown of the Power Amplifier

After the service of intelligent power consumption decrease is enabled, the system checks the
configuration of the TRX module configured with only one carrier within 10 minutes. In such
a case, the TRX module can close an unconfigured carrier to save power.
The system switches off the power amplifier of the configured TRX module in the following
situations:
l
The XMU issues a command to shut down a power amplifier.
The TRX module is locked.
A critical alarm is generated on the TRX module.
Once the system detects that a power amplifier is in the closed state for one minute, the system
shuts down the power amplifier. This is the mode of delaying the shutdown of a power amplifier.
Power-on of the TRX Power Amplifier

The TRX module immediately switches on the power amplifier of a carrier only when the
following conditions are met and the power amplifier is not switched on repeatedly within one
minute:
l
Critical alarms are not generated or are already cleared on the TRX module.
The XMU does not issue a command to shut down a power amplifier or the XMU issues
a command to switch on a power amplifier.
The TRX module is not locked or the TRX is unlocked.
Issue 03 (2009-06-08)

48-5

48.3.2 Intelligent Power Consumption Decrease Not Configured

with the TRX Module
Intelligent power consumption decrease not configured with the TRX module refers to intelligent
shutdown of the power amplifier.
The shutdown of the power amplifier not configured with the TRX module is also called
immediate shutdown.
NOTE
For details about how to switch on the power amplifier, see 48.3.1 Intelligent Power Consumption
Decrease Configured with the TRX Module.
48.3.3 Intelligent Shutdown of the TRX Power Amplifier

When selecting TRX modules to be shut down, you need to select the ones that have the longest
operation interval and are beyond the power-on protection period to avoid frequent power-on
or shutdown of the TRX power amplifier.
You need to record the time of each operation on a TRX module. The operation interval indicates
the period between the last operation time and the current operation time.
Periodically, the BSC checks whether a cell has sufficient idle channels. If sufficient idle
channels are available for a TRX module in a period, select to shut down the power amplifier
of the TRX module.
The TRX module whose power amplifier should be shut down must meet the following
conditions:
l
The TRX module is in the Normal TRX state.
The maximum operation interval of the TRX module is greater than TRX Power-on
Protection Time(s).
After the TRX module is shut down, an idle SDCCH is available for this cell.
There is no packet traffic channel on the TRX module.
The channel that is experiencing type change does not exist on the TRX module.
As the dynamic power-on of the TRX power amplifier performed on the BTS may be delayed,
the periodic check for Number of Reserved TCHs is added. If the number of idle TCHs in a
cell is smaller than Number of Reserved TCHs, the BTS switches on the power amplifier of a
TRX module. The BTS can shut down the power amplifier of the TRX module only when the
number of idle SDCCHs is greater than Idle SDCCH Threshold N1.
A concentric cell may cause the forcible handover for intelligent shutdown of the TRX power
amplifier or the ping-pong handover of a concentric circle. Therefore, the BSC can issue a
command to the BTS to shut down the power amplifier of the TRX module in a concentric cell
even though calls are available on the TRX module. When the BTS detects that calls are not
available on the TRX module, the BTS shuts down the power amplifier of the TRX module.
48.3.4 Intelligent Shutdown of the TRX Power Amplifier and

Channel Assignment
The BSC attempts to assign busy channels to a small number of TRX modules and assign calls
to the TRX modules that cannot be dynamically shut down. Therefore, call drops and handover
times decrease when TRX power amplifiers are shut down.
48-6

Issue 03 (2009-06-08)

To avoid the conflict between the channel type change and the shutdown of a power amplifier,
prohibit the shutdown of the associated power amplifier during the channel type change.
When some TRX modules are idle, the BSC shuts down the power amplifiers of these TRX
modules. When the traffic is heavy, the BSC needs to switch on the power amplifiers of some
TRX modules in an effort to avoid channel congestion.
If the BSC detects that the power amplifier of a TRX module where the directly assigned channels
or dynamically adjusted channels are located is shut down when the BSC assigns channels, the
BSC issues a command to the BTS, requesting the power-on of the power amplifier.
NOTE
For details about the channel assignment algorithm, see 2 Channel Management.
48.4 Implementation
This describes how to configure intelligent power consumption decrease on BSCs, cells, and
TRX modules.
48.4.1 Configuring Intelligent Power Consumption Decrease

This describes how to configure intelligent power consumption decrease on the BSC6000 Local
Prerequisite
When the BSC enables the intelligent shutdown of the power amplifier, the BTS checks only
the circuit-based services.
Before configuring Allow the Shutdown of the TRX Power Amplifier on the TRX module,
ensure that the TRX module meets the following conditions:
l
The non-primary BCCH is located on the TRX module.
The dynamic or static PDCH does not exist.
Antenna hopping or frequency hopping is not enabled.

NOTE
During a BTS deployment test, set Allow Dynamic Shutdown of TRX Power Amplifier to No on the
BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the BSC, configure the intelligent shutdown of the power amplifier.
NOTE
On some special days, such as holidays, do not shut down the power amplifiers of TRX modules.
For the dates when the intelligent shutdown of power amplifiers is allowed, you need to set a time segment
for each date. You can set 12 dates.
1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then choose Configure BSC Attributes from the shortcut menu.
2.
In the displayed dialog box, click the Triger Saving Power Function tab, as shown in
Figure 48-1.
Issue 03 (2009-06-08)

48-7

Configure Allow Dynamic Shutdown of TRX Power Amplifier, Time When the
Function Is Enabled (HH: MM), Time When the Function Is Disabled (HH: MM),
TRX Power-on Protection Time(s), and Number of Reserved TCHs.
NOTE
In the Prohibit Close TRX Power Amplifier pane shown in Figure 48-1, set the dates on which
the TRX power amplifier cannot be closed.
Figure 48-1 Triger Saving Power Function tab page
3.
Click Finish. A dialog box is displayed.
4.
Click Yes to complete the configuration.
Step 2 Configure intelligent power consumption decrease for cells.

1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick a cell, and then choose Configure Cell Attributes from the shortcut menu.
2.
3.
Select Allow Dynamic Voltage Adjustment and Allow Dynamic Shutdown of TRX
Power Amplifier.
48-8

Issue 03 (2009-06-08)

Step 3 On the TRX module, configure the intelligent shutdown of the power amplifier.
1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target TRX, and then choose Configure TRX Attributes from the shortcut menu.
2.
In the displayed dialog box, select the target TRX, and then click Configure TRX
Attributes.
3.
Click the Device Attributes tab and set Allow Shutdown of TRX Power Amplifier to
Yes, as shown in Figure 48-3.
Issue 03 (2009-06-08)

48-9

Figure 48-3 Configure TRX Attributes dialog box
4.
Click OK to complete the configuration.
----End

The relevant maintenance information on intelligent power consumption decrease is not
available.
Alarms
None.
Counters
None.
48.6 References
None.
48-10

Issue 03 (2009-06-08)

49
49 BCCH Dense Frequency Multiplexing
BCCH Dense Frequency Multiplexing
About This Chapter

49.1 Overview
BCCH dense frequency multiplexing (hereinafter called "Tight BCCH frequency reuse")
enables the BCCHs to use fewer frequencies, thus increasing the number of frequencies at the
FH layer and expanding the system capacity.
49.2 Availability
This lists the NEs and software required for the implementation of tight BCCH frequency reuse.
49.3 Impact
The describes the impact of tight BCCH frequency reuse on system performance and on other
features.
Tight BCCH frequency reuse involves the following functions: tight BCCH common channel
assignment, tight BCCH handover algorithm, and channel assignment for tight BCCH handover.
49.5 Implementation
This describes how to configure tight BCCH frequency reuse and disable tight BCCH frequency
reuse.
This describes the maintenance information related to tight BCCH frequency reuse.
49.7 References
There is no reference information about tight BCCH frequency reuse.
Issue 03 (2009-06-08)

49-1

49.1 Overview
BCCH dense frequency multiplexing (hereinafter called "Tight BCCH frequency reuse")
enables the BCCHs to use fewer frequencies, thus increasing the number of frequencies at the
FH layer and expanding the system capacity.
Definition
In tight BCCH frequency reuse mode, the TCHs on the BCCH frequency is assigned to the MSs
near the BTS. This decreases the requirements for the BCCH frequency reuse intensity and
improves the frequency utilization.
Purposes
The tight BCCH frequency reuse technology is applicable to the network with limited frequency
resources. It helps to increase the reuse intensity of BCCH frequencies and reduce the number
of frequencies used by the BCCHs. Therefore, more frequencies can be used at the FH layer. In
a network where the frequency resources are limited, relatively few frequencies at the FH layer
are a capacity bottleneck. Increasing the number of frequencies at the FH layer can improve the
system capacity.
Terms
Term
Definition
BCCH
frequency
Frequency where the BCCH is located
Tight BCCH
BCCH Dense Frequency Multiplexing

Acronym and
Abbreviation
Full Spelling
EFL
Effective Frequency Load
BCCH
BroadCast Channel
TCH
Traffic Channel
49.2 Availability
This lists the NEs and software required for the implementation of tight BCCH frequency reuse.
NEs Involved
Table 49-1 lists the NEs involved in tight BCCH frequency reuse.
49-2

Issue 03 (2009-06-08)

Table 49-1 NEs involved in tight BCCH frequency reuse

MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 49-2 lists the versions of the GBSS products that support tight BCCH frequency reuse.
Product
Version
BSC
BSC6000

releases
Miscellaneous
None.
49.3 Impact
The describes the impact of tight BCCH frequency reuse on system performance and on other
features.

If the load of a cell increases, an MS served by a channel on the non-BCCH frequency may be
handed over to a channel on the BCCH frequency, thus increasing the number of handovers in
the network.

The impact of this feature on other features is as follows:
l
Concentric cells do not support tight BCCH frequency reuse.
Multiband networks do not support tight BCCH frequency reuse.

Tight BCCH frequency reuse involves the following functions: tight BCCH common channel
assignment, tight BCCH handover algorithm, and channel assignment for tight BCCH handover.
Issue 03 (2009-06-08)

49-3

Technical Description
In general, the purpose of limiting the BCCH frequency reuse intensity is to ensure good
performance of the TCHs on the BCCH frequency. When aggressive frequency reuse is adopted,
the interference in the system is increased, thus greatly decreasing the performance of TCHs.
This problem can be solved if tight BCCH frequency reuse is enabled. Tight BCCH frequency
reuse has the following advantages:
l
Reducing the number of frequencies occupied by the BCCHs, and improving the spectrum
utilization
Increasing the number of frequencies available for TCHs and for FH, expanding the system
capacity without adding new hardware, and saving the costs of adding sites and cells
Assigning the TCHs on BCCH frequencies to only the MSs near the BTS, thus improving
the voice quality because of less uplink interference
Reducing random access failures, and improving the access performance
When tight BCCH frequency reuse is adopted, a cell is classified into different logical layers:
TCH layer on the BCCH frequency and FH layer, as shown in Figure 49-1.
l
The FH layer serves and covers the entire network, including cell edges.
The TCH layer on the BCCH frequency, however, covers only the MSs near the BTS to
guarantee call access and to reduce interference near the BTS.
Figure 49-1 Logical layers of tight BCCH frequency reuse
BCCH Frequency
coverage area
Limit to move to
hopping layer
Limit to move
to BCCH
Call moved to hopping

layer if the quality
degrades too much
Tight BCCH frequency reuse involves the following functions:
49-4
Tight BCCH common channel assignment
Tight BCCH handover algorithm
Channel assignment for tight BCCH handover

Issue 03 (2009-06-08)

Tight BCCH Common Channel Assignment

During an initial access request or a non-tight BCCH handover, if TIGHT BCCH Switch is set
to Yes, a TCH is assigned according to the following principles:
l
If a TCH on non-BCCH frequencies is available, the TCH is preferentially assigned to

ensure access performance.
If all the TCHs on non-BCCH frequencies are occupied, the TCH on the BCCH frequency
is assigned.
Tight BCCH Handover Algorithm

When all the TCHs on non-BCCH frequencies are occupied, the signal quality of an MS on the
cell edge decreases if the TCH on the BCCH frequency is assigned to the MS. Therefore, if the
load of a non-BCCH frequency exceeds Load Threshold for TIGHT BCCH HO, the MS with
good signal quality and far from the cell edge is handed over to the TCH on the BCCH frequency.
Thus, the TCHs on non-BCCH frequencies are reserved for other calls. This ensures the call
performance of other calls.
The principle of tight BCCH handover algorithm is as follows: During the period specified by
TIGHT BCCH HO Watch Time(s), if the period when tight BCCH handover conditions are
met exceeds TIGHT BCCH HO Valid Time(s), a handover is initiated. Otherwise, no handover
is initiated.
Channel Assignment for Tight BCCH Handover

The purpose of tight BCCH handover is to hand over a call near the BTS to the BCCH frequency.
Therefore, if the cause of a handover is tight BCCH handover, a TCH on the BCCH frequency
should be assigned.
49.5 Implementation
This describes how to configure tight BCCH frequency reuse and disable tight BCCH frequency
reuse.
49.5.1 Recommended Configuration of Tight BCCH Frequency

Reuse
This describes the suggestions for configuring tight BCCH frequency reuse.
In general, the 4x3 mode is used in BCCH frequency planning to guarantee high carrier-tointerference ratios (CIRs) between BCCH frequencies. In this mode, the BCCHs occupy 12
frequencies, thus reducing the number of frequencies involved in FH. In a network where the
frequencies are highly reused and the frequency resources are limited, relatively few frequencies
at the FH layer are a capacity bottleneck.
No anti-interference technology such as FH is used on BCCH frequencies. If the 3x3 mode is
used in BCCH frequency planning, the TCHs on BCCH frequencies have low anti-interference
capabilities, thus increasing the interference in the system. When aggressive frequency reuse is
adopted, the performance of TCHs decreases greatly and is unacceptable.
In this case, enabling tight BCCH frequency reuse on the BSC side can solve the problem.
Issue 03 (2009-06-08)

49-5

49.5.2 Configuring Tight BCCH Frequency Reuse

This describes how to configure tight BCCH frequency reuse on the BSC6000 Local
Procedure
Step 1 Configure channel assignment algorithm parameters.
1.
On the BSC6000 Local Maintenance Terminal, right-click the target cell on the
Management Tree tab page, and then choose Configure Cell Attributes from the shortcut
menu.
2.
3.
49-6

Issue 03 (2009-06-08)

4.
Click Channel Management. A dialog box is displayed, as shown in Figure 49-3.

5.
Set TIGHT BCCH Switch to Yes.
6.
Step 2 Configure handover algorithm parameters.

1.
Issue 03 (2009-06-08)
In the dialog box shown in Figure 49-2, click Handover Data. A dialog box is displayed,

49-7

Figure 49-4 Set Handover Parameter dialog box
49-8
2.
Set TIGHT BCCH HO Watch Time(s) and TIGHT BCCH HO Valid Time(s).
3.

Issue 03 (2009-06-08)

Figure 49-5 Cell HO Data tab page
4.
Set RX_QUAL Threshold for TIGHT BCCH HO and Load Threshold for TIGHT
BCCH HO.
----End
49.5.3 Disabling Tight BCCH Frequency Reuse

This describes how to disable tight BCCH frequency reuse on the BSC6000 Local Maintenance
Terminal.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, right-click the target cell on the Management
Tree tab page, and then choose Configure Cell Attributes from the shortcut menu.
Issue 03 (2009-06-08)

49-9

Step 4 Click Channel Management. A dialog box is displayed, as shown in Figure 49-7.
49-10

Issue 03 (2009-06-08)

Step 5 Set TIGHT BCCH Switch to No.

Step 6 Click OK to end the configuration.
----End

This describes the maintenance information related to tight BCCH frequency reuse.
Alarms
None.
Counters
None.
Issue 03 (2009-06-08)

49-11

49.7 References
There is no reference information about tight BCCH frequency reuse.
49-12

Issue 03 (2009-06-08)

50
50 Intra BSC Soft-Synchronized Network
Intra BSC Soft-Synchronized Network
About This Chapter

50.1 Overview
The technology of intra BSC soft-synchronized network (hereinafter called "Um interface
software synchronization") can convert an asynchronous network into a synchronous network.
In cooperation with other related technologies, this technology eliminates the random and
unpredictable interference and thus enhances the system capacity.
50.2 Availability
This lists the NEs, software, and license required for the implementation of Um interface
software synchronization.
50.3 Impact
This describes the impact of Um interface software synchronization on system performance and
on other features.
The Um interface software synchronization technology adjusts the frame numbers and bit offsets
in the frames of the BTSs on the basis of reference BTSs, thus enabling all the BTSs to realize
Um interface synchronization.
50.5 Capabilities
This describes the capabilities of Um interface software synchronization.
50.6 Implementation
This describes how to configure, verify, and disable Um interface software synchronization.
None.
50.8 References
None.
Issue 03 (2009-06-08)

50-1

50.1 Overview
The technology of intra BSC soft-synchronized network (hereinafter called "Um interface
software synchronization") can convert an asynchronous network into a synchronous network.
In cooperation with other related technologies, this technology eliminates the random and
unpredictable interference and thus enhances the system capacity.
Definition
Um interface software synchronization requires the cooperation of MSs and the BSS to
implement the synchronization on the Um interface.
For the hardware synchronization, each BTS is equipped with a GPS and the entire network is
synchronized through a satellite.
In an asynchronous network, the BTSs use different frame numbers and different bit offsets in
the frames.
In a synchronous network, the BTSs use the same frame number and the same bit offset in the
frame.
Purposes
In the existing GSM system, the BTSs are asynchronous with each other. In an asynchronous
network, the co-channel interference and the adjacent-channel interference are uncontrollable
and different timeslots are overlapped randomly. The timeslot overlap, however, may lead to
unnecessary and unpredictable interference. The randomness and unpredictability disable the
implementation of some technologies, such as IBCA. In addition, the performance of some
technologies, such as ICC and SAIC, is greatly degraded.
At present, the Um interface synchronization is realized through hardware synchronization, that
is, each BTS is equipped with a GPS. The hardware synchronization, however, increases the
cost. To reduce the cost, Huawei introduces the concept of software synchronization, which
applies the MSs and the BSS in the network to realize the Um interface synchronization.
Terms
50-2
Terms
Definition
IBCA
Interference based channel allocation. The C/I ratios of idle channels are
estimated. Then, channels are assigned on the basis of the C/I ratio
requirements of calls. At the same time, the newly assigned channels
should not bring unacceptable interference to the established calls.
ICC
The interference elements of the multiple signals received by multiple

antennas are associated with co-channel interface (CCI) and inter-symbol
interference (ISI). Considering the correlation of these two types of
interference, the ICC constructs the two-dimensional combining
coefficient matrix to combine the signals according to the maximum
signal-to-noise ratio criterion.

Issue 03 (2009-06-08)

Terms
Definition
SAIC
SAIC is applicable to the MS with a single antenna. SAIC is used to reduce

the impact of interference on the reception of downlink signals through a
signal processing technology. For details of SAIC, refer to the 3GPP R6
protocol.
BTS loss of
synchronization
The software synchronization status of the BTS is changed from

synchronous with the network to asynchronous with the network.
Clock unlocked
The BTS clock status is changed from locked to other states, such as
Capture or Free-run.

Acronym and
Abbreviation
Full Spelling
AB
Access Burst
IBCA
Interference Based Channel Allocation
ICC
Interference Cancellation Combining
SAIC
Single Antana Interference Cancellation
50.2 Availability
This lists the NEs, software, and license required for the implementation of Um interface
software synchronization.
NEs Involved
Table 50-1 lists the NEs involved in Um interface software synchronization.
Table 50-1 NEs involved in Um interface software synchronization
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 50-2 describes the versions of GBSS products that support Um interface software
synchronization.
Issue 03 (2009-06-08)

50-3


Product
Version
BSC
BSC6000
BTS
BTS3012
BTS3012AE

DTRU
QTRU
DTRU
QTRU
BTS3006C
BTS3002E
Miscellaneous
Um interface software synchronization is available only when a license is obtained.
50.3 Impact
This describes the impact of Um interface software synchronization on system performance and
on other features.

After the Um interface software synchronization is achieved, the IBCA function can be
performed. This greatly improves the performance of the ICC and SAIC technologies and of the
radio-related KPI counters, such as MOS, paging success rate, handover success rate, call drop
rate, and traffic volume.
The conversion from an asynchronous network to a synchronous network can effectively reduce
the interference on the entire network and expand the network capacity.

None.

The Um interface software synchronization technology adjusts the frame numbers and bit offsets
in the frames of the BTSs on the basis of reference BTSs, thus enabling all the BTSs to realize
Um interface synchronization.
50.4.1 Collecting the Offset Information Between BTSs
This describes how to collect the offset information between BTSs.
50.4.2 Synchronizing Two BTSs
This describes how to synchronize two BTSs.
50-4

Issue 03 (2009-06-08)

50.4.3 Synchronizing the Entire Network

This describes how to synchronize the entire network.
50.4.4 Managing the Synchronization Status of BTSs
This describes how to manage the synchronization status of the BTSs.
50.4.1 Collecting the Offset Information Between BTSs

This describes how to collect the offset information between BTSs.
For the collection of the offset information between BTSs, the MS sends an AB to the BTSs.
Then, the BSC obtains the information about the frame numbers, timeslot numbers, and bit
offsets in timeslots. The time synchronization of the two BTSs is performed on the basis of the
obtained information. See Figure 50-1.
Figure 50-1 Collecting the offset information
BTS1
1 2
7
x+1
MS
BTS2
0
1 2
7
y+1
As shown in Figure 50-1, x and y indicate the frame numbers.

The procedure for collecting the offset information between BTSs is as follows:
l
The BSC selects an MS within the overlapping area of BTS1 and BTS2.
The MS sends an AB.
BTS 1 and BTS 2 receive the AB.
After receiving the AB, BTS1 and BTS2 report the time when the AB is received, and
obtain the frame number, timeslot number, and bit offset in the timeslot.
Based on the time information reported by BTS1 and BTS2, the BSC calculates the frame
number offset and bit offset between the two BTSs.
NOTE
The MS in the overlapping area of BTS1 and BTS2 is required to collect the offset information. In addition,
channels on the cells must be reserved for the synchronization measurement. It is recommended that the
information for synchronization be collected when the traffic volume is small.
50.4.2 Synchronizing Two BTSs

This describes how to synchronize two BTSs.
Issue 03 (2009-06-08)

50-5

Take BTS1 as the reference BTS. Keep the frame number and the offset of BTS1 unchanged.
Synchronize BTS2 with BTS1 by adjusting the frame number and the offset. See Figure 50-2.
Figure 50-2 Synchronization of BTSs
BTS1
1 2
x
BTS2
x+1
1 2
7
y+1
1 2
1 2
y
BTS2
x
BTS2
7
x+1
As shown in Figure 50-2, x and y indicate the frame numbers.

The synchronization procedure is as follows:
l
Frame number synchronization: adjust the frame number of BTS2 to the same value as that
of BTS1.
Offset synchronization: adjust the offset of BTS2 to the same value as that of BTS1.
NOTE
During the BTS synchronization, call drops may occur. Therefore, when configuring the synchronization
tasks, ensure that the synchronization is performed during the hours with the smallest traffic volume.
50.4.3 Synchronizing the Entire Network

This describes how to synchronize the entire network.
Synchronize each two BTSs under one BSC so that all the BTSs under the BSC are synchronized,
Figure 50-3 Synchronizing the entire network
20
9
8
19
18
17
7
6
16
50-6
10
3
1
5
15
11
12
13
14

Issue 03 (2009-06-08)

The procedure for synchronizing all the BTSs under one BSC is as follows:
1.
Take BTS1 as a reference and synchronize the first circle of BTSs, for example, BTS2BTS7 shown in Figure 50-3, around BTS1.
2.
Take each BTS in the first circle as a reference and synchronize two neighbor BTSs in the
second circle. If BTS2 is used as a reference, two neighbor BTSs of BTS2, for example,
BTS8 and BTS9 shown in Figure 50-3, should be synchronized.
3.
Use the same way to synchronize all the BTSs under the BSC.
50.4.4 Managing the Synchronization Status of BTSs

This describes how to manage the synchronization status of the BTSs.
Figure 50-4 shows the synchronization procedure and the synchronization status monitoring.
Figure 50-4 Synchronization task management
Information to
be collected
Trigger collection
Collection in
progress
Collection
completed
BTS out of synchronization

BTS reset
Clock unlocked
Information
collected
Trigger
synchronization
Synchronization
completed
Before synchronization, all BTSs are in the Information to be collected state. The BSC initiates
the measurement of the offsets between each two BTSs and the collection of synchronization
information. After the synchronization information is collected, the BTS triggers the adjustment
of frame number and offset. After the adjustment, the BTS is in the Synchronized state. If an
event incurs loss of synchronization, for example, BTS reset, BTS clock unlocked, clock
precision, or other reasons, the BTS state is changed to To Be Collected. In this case, a
synchronization of the corresponding BTSs with the network is initiated again.
50.5 Capabilities
This describes the capabilities of Um interface software synchronization.
The capabilities of Um interface software synchronization are as follows:
For two neighbor BTSs to be synchronized, the offsets between the timeslots should be at most
four bits.
Issue 03 (2009-06-08)

50-7

50.6 Implementation
This describes how to configure, verify, and disable Um interface software synchronization.
50.6.1 Recommended Configuration of Um Interface Software

Synchronization
This provides suggestions for configuring Um interface software synchronization.
The recommended configuration of Um interface software synchronization is as follows:
l
Um interface software synchronization is applicable to the tight frequency reuse scenario.

The distance between BTSs should be shorter than 900 m. A distance of shorter than 800
m is recommended.
The network coverage should be continuous. Under one BSC, the continuous coverage area
can be a set of synchronous BTSs. For an area that is continuously covered by the BTSs
under multiple BSCs, Um interface software synchronization is not applicable.
At present, the network under a single BSC can be synchronized, and the network under
multiple BSCs cannot be synchronized.
If Um interface software synchronization is not in cooperation with other algorithms, the

interference on certain channels may change from random collision to persistent collision,
which leads to the decrease in performance counters on these channels. Therefore, Um
interface software synchronization must be used with other technologies, such as network
planning or IBCA.
50.6.2 Configuring Um Interface Software Synchronization

This describes how to configure the Um interface software synchronization function on the
Prerequisite
1.
In BSC6000V900R008 Exceptional Commercial License Application Template, set

Whether to activate the soft synchronization function or not under License control
items to 1. The value 1 indicates that this function is enabled.
2.
the BSC License.
Procedure
Step 1 On the Local Maintenance Terminal, enter the command SET AISSCFG.
NOTE
Step 2 Set both Collect Offset Information and Offset Time Adjustment Switch to ON, and set other
parameters.
50-8

Issue 03 (2009-06-08)

Step 3 Run the command. The operation is complete.

----End
50.6.3 Verifying Um interface Software Synchronization

This describes how to verify the Um interface software synchronization function on the Local
Procedure
Step 1 On the Local Maintenance Terminal, run the command LST AISSCFG. Check whether the
related information in the returned messages is correct.
Step 2 On the Local Maintenance Terminal, run the command DSP AISSRUNSTATE. Check
whether synchronization tasks are performed properly.
Step 3 On the Local Maintenance Terminal, run the command DSP BTSSYNCINFO. Check the
synchronization status of the BTS.
----End
50.6.4 Disabling Um Interface Software Synchronization

This describes how to disable the Um interface software synchronization function on the Local
Procedure
Step 1 On the Local Maintenance Terminal, enter the command SET AISSCFG.
NOTE
Step 2 Set both Collect Offset Information and Offset Time Adjustment Switch to OFF.
Step 3 Run the command. The operation is complete.
----End

None.
50.8 References
None.
Issue 03 (2009-06-08)

50-9

51 Interface over IP
51
Interface over IP
About This Chapter

51.1 Overview
Interface over IP refers to that IP network is used to transmit signaling and speech signals on
interfaces.
51.2 Availability
This lists the NEs and software required for the implementation of interface over IP.
51.3 Impact
This describes the impact of interface over IP on system performance and on other features.
The interface over IP is classified into A over IP, Abis over IP, and Gb over IP.
51.5 Capabilities
This describes the capabilities of interface over IP.
51.6 Implementation
This describes how to configure A over IP, Abis over IP, and Gb over IP.
This lists the alarms and counters related to interface over IP.
51.8 References
Issue 03 (2009-06-08)

51-1

51.1 Overview
Interface over IP refers to that IP network is used to transmit signaling and speech signals on
interfaces.
Definition
The BSC supports the following types of interface over IP:
l
A over IP
IP network is used to transmit signaling and speech signals on the A interface. The
SIGTRAN (SCCP/M3UA/SCTP/IP) protocol stack is applied to the signaling plane, and
the RTP/UDP/IP protocol stack is applied to the user plane.
When A over IP is enabled, the transcoding from the TRAU of the GTCS to the PCM is
performed by the MGW.
Abis over IP
IP network is used to transmit signaling and speech signals on the Abis interface. The LAPD
Over UPD/IP protocol stack is applied to the signaling plane, and the PTRAU Over UDP/
IP protocol stack is applied to the user plane.
Gb over IP
IP network is used to transmit PS service signals on the Gb interface. The Gb over IP
protocol stack is applied to the Gb interface.
Purposes
The purposes of interface over IP are as follows:
l
The interface over IP supports hybrid transmission modes and low-speed links. Thus, the
topology and transmission mode of IP network are more flexible.
Becasue service transmission network and OM network are based on IP network, the cost
of operation and management can be reduced.
Interface over IP uses the packet switching technique of the IP network. This enables
efficient utilization of transmission resources and enables reduction of cost of transmission
and devices.
IP transmission meets the requirements for future evolution to 3G.
Terms
51-2
Terms
Definition
Association
An association refers to a logical relation (channel) for data

transmission which is set up by two SCTP endpoints through
the four-way startup handshake mechanism of SCTP.

Issue 03 (2009-06-08)

Issue 03 (2009-06-08)
Terms
Definition
BFD
BFD is a simple Hello protocol, similar to the adjacent

detection in the route protocol. Two systems periodically
sends BFD check messages on the channel between the two
systems. If one system does not receive the check messages
from the other system for a long time, you can infer that the
channel is faulty. Under some circumstances, the TX and RX
rates between the two systems need to be adjusted to reduce
traffic load.
DiffServ
The DiffServ defines the DS field in the ToS byte. The

DiffServ also defines a set of packet transfer processing
database. The mark of the DS field in a packet and the
processing of the DS field generates different service levels.
Therefore, DiffServ is actually a strategy of relative priority.
IP protocol
IP protocol refers to a protocol suite consisting of a series of

standards that enables a data packet to be transmitted to its
destination through the Internet. IP protocol provides a
connectionless data packet transmission mechanism, shields
physical network transmission, addresses IP, and selects
routes.
PPP
PPP, a protocol on the data link layer, provides point-to-point

transmission and encapsulates data packets on the network
layer. PPP, located in layer 2 of the IP protocol stack, supports
point-to-point data transmission on full-duplex synchronous
and asynchronous links.
RTP
RTP, a protocol for end-to-end realtime transmission,

provides the RX end with information such as packet serial
number for recovering realtime data, and provides
communications quality test.
SCTP
SCTP, an end-to-end, connection-oriented protocol that

transports data in independent sequenced streams, provides a
reliable transmission of user messages between equivalent
SCTP users.
SIGTRAN
Signaling Transport (SIGTRAN) refers to a protocol stack for

the transport of Switched Circuit Network (SCN) signaling
protocols (SS7/C7) over an IP network. SIGTRAN is applied
to IP network to support the IP interworking between the
traditional narrowband telecommunication network PSTN
and wideband network.
Stream
Stream refer to the directional logical path from one end to

anther end in an SCTP link.
UDP
UDP is a simple data-oriented end-to-end transmission

protocol without reliability. The UDP sends the data from one
end to another through the IP layer regardless of whether the
data can arrive at destinations.

51-3

Terms
Definition
VC Trunk
VC Trunk refers to the logical path formed by some cascaded

VCs.
VRRP
VRRP, an Internet protocol, provides one or more than one

backup route when static routing is used in local area network.
51-4
Full Spelling
ASP
Application Server Process
BFD
Bidirectional Forwarding Detection
BMRC
BM Resource Control
BTSCP
BTS Common Processing
BTSM
Base Transceiver Station Management
BTSTRC
BTS Transmisson Resource Control
CECHM
Cell Channel Management
CEGPRS
Cell GPRS Processing
CM
Configuration Management
CPOS
Channelize Packet Over SDH
CRDLC
Call Radio Link Control
DBAPI
DataBase API
DBMI
DataBase Management Interface
DHCP
Dynamic Host Configuration Protocol
DiffServ
Differentiated Service
EML
Extend Operation Maintenance Link
ESL
Extend Signalling Link
IPSP
IP Server Process
M3UA
MTP3 User Adaptation Layer
MSIP
MS Instance Processing
MSTP
Multiservice Transport Platform
OML
Operation Maintenance Link
PBIP
Pb Interface Processing

Issue 03 (2009-06-08)

Full Spelling
PDCH
Packet Data Channel
POS
Packet Over SDH
RC
Resource Control
RR
Radio Resource
RRM
Radio Resource Management
RSL
Radio Signalling Link
SAPI
Service Access Point Identifier
SCTP
Stream Control Transmission Protocol
SGP
Signalling Gateway Process
SIGTRAN
Signalling Transport
TEI
Terminal Endpoint Identifier
UMG
Universal Media Gateway
VC Trunk
Virtual Container Trunk
VRRP
Virtual Router Redundancy Protocol
51.2 Availability
This lists the NEs and software required for the implementation of interface over IP.
NEs Involved
Table 51-1 lists the NEs involved in interface over IP.
Table 51-1 NEs involved in interface over IP
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Releases
Table 51-2 lists the versions of GBSS products that support interface over IP.
Issue 03 (2009-06-08)

51-5


Product
Version
BSC
BSC6000
BTS
BTS3012
BTS3012AE

DTRU

releases
QTRU

releases
DTRU

releases
QTRU

releases
Miscellaneous
None
51.3 Impact
This describes the impact of interface over IP on system performance and on other features.

The impact of interface over IP on system performance is as follows:
l
The Abis over IP supports the star topology of built-in PCU and BTS, and does not support
the BTS cascade, HubBTS, or TDM/hybrid IP transport.
When A over IP is enabled, the functions of the GTCS are taken over by the MGW and the
BSC is not configured with the GTCS.
The Abis over IP and A over IP support only IPv4.

None

The interface over IP is classified into A over IP, Abis over IP, and Gb over IP.
51.4.1 A over IP
The A over IP is a technique where the IP network is used to transmit signaling and speech
signals on the A interface.
51-6

Issue 03 (2009-06-08)

Network Topologies
The A over IP supports the following three network topologies:
l
Direct connection
Figure 51-1 shows the network topology of direct connection.
Figure 51-1 Network topology for A over IP (direct connection)
MSC server
FE/GE transmission
Signaling on
A interface
BSC
MGW
The network topology of direct connection has the following features:
The reliability is high, the cost is low, and the maintenance is easy.
A high QoS can be easily realized and the call access can be easily controlled.
Layer 2 network through switches

Figure 51-2 shows the network topology of layer 2 network through switches.
Figure 51-2 Network topology for A over IP (layer 2 network through switches)
MSC Server
Switch
FE/GE
BSC
Layer2 Network
Switch
Switch
MGW
Layer 3 network through routers

Figure 51-3 shows the network topology of layer 3 network through routers.
Issue 03 (2009-06-08)

51-7

Figure 51-3 Network topology for A over IP (layer 3 network through routers)
MSC Server
Router
FE/GE
BSC
IP Network
Router
Router
MGW
The previous two network topologies have the following features:

l
Provides a large-capacity bandwidth and a reliable transmission bearer for the A interface
Meets the requirement of GSM evolution for the transport bearer network
Adapts to the impact of burst data on the network
Satisfies the requirement of a large-scale network because of flexibility
Reliability of the Network Topologies

For the previous network topologies, the BSC provides high reliability for load sharing,
involving both inter-board ports and intra-board ports. For the BSC, there are two routes to each
destination IP address at the peer end. If the active route is disrupted, the standby one is
functional, as shown in Figure 51-4.
Figure 51-4 Reliability of the network topologies for A over IP
BSC
A
interface
board
(active)
Switch
Router
Router
MSC server
Router
MGW
IP network
A
interface
board
(standby)
Switch
51-8
Router

Issue 03 (2009-06-08)

Protocol Stack Scheme

When A over IP is enabled, the functions of the GTCS are taken over by the MGW and the BSC
does not perform transcoding. The compressed speech coding mode is still used, and thus the
transmission bandwidth is reduced on the A interface. When an MS calls another MS in the
network, secondary speech coding/decoding can be avoided if the calling and called parties use
the same speech coding scheme. Thus, the speech quality is enhanced and the resources are
saved.
On the A interface, both the signaling plane and the user plane support the IP transmission. The
signaling plane uses the M3UA/SCTP/IP protocol stack and the user plane uses the RTP/UDP/
IP protocol stack to bear speech frames, as shown in Figure 51-5.
Figure 51-5 Protocol stack scheme for A over IP
BSC
Protocol stack for

signaling plane
MSC server
Protocol stack for

user plane
BSSMAP
BSSMAP
BSC
MGW
SCCP
SCCP
Voice
Voice
M3UA
M3UA
RTP
RTP
SCTP
SCTP
UDP
UDP
IP
IP
IP
IP
FE/GE
FE/GE
FE/GE
FE/GE
A interface
A interface
QoS
The GBSS adopts the following mechanisms to ensure high end-to-end QoS.
l
Physical bandwidth shaping

Through the buffer and token bucket, the burst flow in the network is restricted. If the
messages are transmitted at a too fast speed, they are buffered and then transmitted at a
uniform speed under the control of the token bucket.
Priority mapping
A definite rule is used to identify the messages for different services. Then, the messages
are classified and prioritized, and they are associated with the corresponding flow control
and resource assignment. Based on the load on the current network, a specific flow control
action is taken.
Issue 03 (2009-06-08)
Congestion management
51-9

When the speed for the messages to access the network devices is beyond the transmission
capability of the port, congestion occurs and a large amount of network resources are
wasted. Improper resource assignment may lead to system deadlock or corruption.
Increasing the network bandwidth is a direct method of alleviating resource insufficiency.
In addition, congestion avoidance mechanisms are used to avoid congestion. Generally, the
tail drop and WRED are used. When congestion occurs, the Priority Queue (PQ) or
Weighted Round Robin (WRR) of queue scheduling is used to solve the congestion
problem.
Different QoS mechanisms are used for different protocol layers, for example, resource
reservation for the application layer, DiffServ for the IP layer, PQ for the data link layer, and
LR for the physical layer, as listed in Table 51-3.
Table 51-3 Mapping between protocol layer and QoS mechanism
Protocol Layer
QoS Mechanism
Application layer
Resource reservation
IP layer
DiffServ
Data link layer
PQ
Physical layer
LR
51.4.2 Abis over IP

The Abis over IP is a technique where the IP network is used to transmit signaling and speech
signals on the Abis interface.
Network Topologies
The network topologies for Abis over IP support three transmission modes: MSTP, data network,
and satellite link. In these transmission modes, an FE/GE port is provided for the BSC and an
FE port for the BTS.
l
MSTP-based IP network topology

Figure 51-6 shows the MSTP-based IP network topology.
Figure 51-6 MSTP-based IP network topology
FE/GE
BSC
FE
MSTP
Router
Router
BTS
This network topology has the following features:

51-10

Issue 03 (2009-06-08)

It is applicable to the network operators that have established an SDH or MSTP network.
The BTS provides a transmission bandwidth of up to 100 Mbit/s over the FE interface,
thus facilitating BTS upgrade and capacity expansion and enabling the fast deployment
for data services of the BTS.
The VC trunk function provided by the MSTP network enables the establishment of
two VC trunk links between the BTS and the BSC, transmitting real-time service data
and non-real-time service data respectively.
Data network-based IP network topology

Figure 51-7 shows the data network-based IP network topology.
Figure 51-7 Data network-based IP network topology
BSC
Switch
Router
FE/GE
FE/GE
IP/MPLS/VPN
BTS
BSC
BTS
This network topology has the following features:
The data network can provide a large-capacity bandwidth and a reliable transmission
for the Abis interface.
The data network can fulfill the evolution from the GSM network to the IP network.
Satellite link-based IP network topology, including the following two scenarios:
Issue 03 (2009-06-08)
The star network topology of satellite earth stations (station + substation) can be used.
In this network topology, one station can be accessed by multiple BTSs, as shown in
Figure 51-8.

51-11

Figure 51-8 Satellite link-based IP network topology (star network topology)
FE
SDH/PDH or
microwave
transmission
network
BSC
Satellite earth
substation
Satellite earth
station
BTS
FE
Satellite earth
substation
BTS
The mesh network topology of satellite earth stations can be used. This network
topology is flexible and convenient, as shown in Figure 51-9.
Figure 51-9 Satellite link-based IP network topology (mesh network topology)
FE
FE/GE
BSC
Satellite earth
station
Satellite earth
station
BTS
FE
Satellite earth
station
BTS

When Abis over IP is enabled, the LAPD Over UPD/IP protocol stack is applied to the signaling
plane, and the PTRAU Over UDP/IP protocol stack is applied to the user plane, as shown in
Figure 51-10.
51-12

Issue 03 (2009-06-08)

Figure 51-10 Protocol stack scheme for Abis over IP
BTS
Protocol stack for

signaling plane
Protocol stack for

user plane
BSC
OML/RSL/
ESL/EML
OML/RSL/
ESL/EML
BTS
BSC
LAPD
LAPD
PTRU
PTRU
UDP
UDP
UDP
UDP
IP
IP
IP
IP
MAC
MAC
MAC
MAC
Abis interface
Abis interface
QoS
Refer to QoS in 51.4.1 A over IP.
51.4.3 Gb over IP
Gb over IP refers to that when the built-in PCU is used, the PS service signals between the BSC
and the SGSN are transmitted over IP network.
Network Topologies
Figure 51-11 shows the network topologies supported by Gb over IP.
Figure 51-11 Network topology for Gb over IP
FE/GE
BSC
FE/GE
IP Network
Router
Router
SGSN
When Gb over IP is enabled, the signals between the BSC and the SGSN are transmitted over
IP network, and routers are used to provide layer 3 routing services for the BSC and the SGSN.
The bandwidth on the Gb interface is added. Thus, the cost of operation and maintenance is
reduced.
Issue 03 (2009-06-08)

51-13


When Gb over IP is enabled, FE/GE transmission is applied to the physical layer, NS protocol
to layer 2 (Sub NS complies with the IP protocol), and BSSGP to application layer, as shown in
Figure 51-12. For details of the protocol stack for Gb over IP, refer to 19.4.17.1 Description
of the Gb Interface.
Figure 51-12 Protocol stack scheme for Gb over IP
SGSN
BSC
LLC
BSSGP
BSSGP
NS
NS
IP
IP
FE/GE
FE/GE
Gb interface
51.5 Capabilities
This describes the capabilities of interface over IP.
The capabilities of the interface over IP feature are listed as follows:
l
A maximum of 20 pairs of GFGUA/GOGUA can be configured, with a maximum of 5

pairs in each subrack. They can be configured in only the rear subracks. A maximum of
6,144 speech channels can be provided by the GFGUA/GOGUA.
A maximum of 20 pairs of GFGUB/GOGUB can be configured, with a maximum of 5 pairs

in each subrack. They can be configured in only the rear subracks. The GTCS does not
require the configuration of GFGUB/GOGUB. The number of pairs of GFGUB/GOGUB
configured in the main subrack in the case of GOMU is two less than that in the case of
GBAM. A maximum of 384 TRXs can be supported by the GFGUB/GOGUB.
A maximum of 8 pairs of GFGUGs can be configured. For the capabilities of the Gb

interface, refer to 19.5 Capabilities and 20.5 Capabilities.
51.6 Implementation
This describes how to configure A over IP, Abis over IP, and Gb over IP.
51-14

Issue 03 (2009-06-08)

51.6.1 Configuring A over IP

This describes how to configure A over IP on the BSC6000 Local Maintenance Terminal.
Prerequisite
l
The BSC is configured with the GFGUA/GOGUA, which serves as the A over IP interface
board.
1.
When applying for the A over IP license, ensure that the Number of resources column
corresponding to Whether to activate A over IP or not under Function control
items row in BSC6000V900R008 (None) Commercial License Application
Template is set to 1. Value 1 indicates that this function should be enabled.
2.
Procedure
BSC6000 and then select Configure BSC Attributes from the shortcut menu. A dialog box is
On the Basic Data tab page, set BSC Subrack Combination Type to IP on A Interface.
Figure 51-13 Configure BSC Attributes dialog box
Step 2 Add a GFGUA/GOGUA and configure the related parameters.

Issue 03 (2009-06-08)

51-15

1.
Add a GFGUA/GOGUA. For details, refer to step 1 described in Configuring the GFGUA/
GOGUA.
2.
Configure the following parameters: Ethernet port attributes, QoS attributes, and physical
link detect attributes. For details, refer to step 2 described in Configuring the GFGUA/
GOGUA.
3.
Configure the device IP address. For details, refer to step 3 described in Configuring the
GFGUA/GOGUA.
Set Subsystem No., IP Address, and Subnet Mask.
Device IP is the logical IP address used for communication. The device IP address is valid
for all the ports on the device. The active and standby interface boards must be configured
with the same IP address.
4.
Configure the port IP address. For details, refer to step 4 described in Configuring the
GFGUA/GOGUA.
Set Port No., IP Address, and Subnet Mask.
l
5.
The port IP address and the device IP address must be on different network segments.
If the FE transmission is used, one GFGUA can be configured with eight port IP
addresses, and the addresses must distribute on different network segments.
If the GE transmission is used, one GFGUA can be configured with two port IP
If active and standby GFGUAs are configured, their port IP addresses should be different
and should distribute on the same network segment.
Configure the BSC router. For details, refer to step 5 described in Configuring the GFGUA/
GOGUA.
Set Destination IP Address, Route PRI, and Gateway IP Address.
l
Destination IP Address should be set as the destination network segment but not a
single IP address.
Gateway should be on the same network segment as the port IP address of the GFGUA.
In the case of active and standby boards, add a BSC router after their port IP addresses
are configured.
Step 3 Configure the M3UA entities. For details, refer to Configuring the M3UA Entities.
1.
Configure the local entity.

Set Local Entity Name and OPC.
2.
Configure the destination entity.

Set Destination Entity Name and DPC(Hex).
NOTE
If there is no direct physical link between the local entity and the destination entity, you need to
configure the STP entity. In this situation, you need to set Using STP to Yes, and then perform the
following operations.
Step 4 Configure the subrack-OSP mapping. For details, refer to Configuring the Subrack-OSP
Mapping.
According to the OPC set in Step 3, configure OSP.
51-16

Issue 03 (2009-06-08)

Step 5 Configure the M3UA link set. For details, refer to Configuring the M3UA Link Set.
Set Linkset Name and Adjacent Destination Entity.
Step 6 Configure the M3UA route. For details, refer to Configuring the M3UA Route.
According to the M3UA entity configured in Step 3 and the M3UA link set configured in Step
5, set Destination Entity Name and Linkset Name.
Step 7 Configure the M3UA link. For details, refer to Configuring the M3UA Link.
On the M3UA tab page, set Local Port No., Local Address 1, Local Address 2, Peer Address
1, Peer Address 2, Peer Port No., and Priority.
Where, Local Address 1 is the device IP address configured in Step 2. In this situation, the
configuration is not required. In addition, an M3UA link can be configured only when the device
IP address is configured.
----End
51.6.2 Configuring Abis over IP

This describes how to configure Abis over IP on the BSC6000 Local Maintenance
Terminal.
Prerequisite
l
The BSC is configured with the GFGUB/GOGUB, which serves as the Abis over IP
interface board.
1.
In the License control items of the BSC6000V900R008 Exceptional Commercial

License Application Template, locate the Number of TRX supporting Abis Over
IP row and specify a value in the cell corresponding to the Resource number column.
2.
Procedure
Step 1 Add a GFGUB/GOGUB and configured the related parameters.
1.
Add a GFGUB/GOGUB. For details, refer to step 1 described in Configuring the GFGUB/
GOGUB.
2.
Configure the following parameters: Ethernet port attributes, QoS attributes, and physical
link detect attributes. For details, refer to step 2 described in Configuring the GFGUB/
GOGUB.
3.
Configure the device IP address. For details, refer to step 3 described in Configuring the
GFGUB/GOGUB.
Set Subsystem No., IP Address, and Subnet Mask.
Device IP is the logical IP address used for communication. The device IP address is valid
for all the ports on the device. The active and standby interface boards must be configured
with the same IP address.
4.
Configure the port IP address. For details, refer to step 4 described in Configuring the
GFGUB/GOGUB.
Set Port No., IP Address, and Subnet Mask.
Issue 03 (2009-06-08)

51-17


l
5.
The port IP address and the device IP address must be on different network segments.
If the FE transmission is used, one GFGUB can be configured with eight port IP
If the GE transmission is used, one GFGUB can be configured with two port IP
If active and standby GFGUBs are configured, their port IP addresses should be different
and should distribute on the same network segment.
Configure the BSC router. For details, refer to step 5 described in Configuring the GFGUB/
GOGUB.
Set Destination IP Address, Route PRI, and Gateway IP Address.
l
Destination IP Address should be set as the destination network segment but not a
single IP address.
Gateway IP Address should be on the same network segment as the port IP address of
the GFGUB.
In the case of active and standby boards, add a BSC router after their port IP addresses
are configured.
Step 2 Add a BTS and configure the related parameters.

1.
Add a BTS. For details, refer to steps 1 through 5 described in Adding a BTS (IP
Transmission Mode).
Specify Site Name and Site Type. Set Service Mode to IP. Then, set Logic IP.
Adhere to the following principles when configuring the parameters:
2.
Only the BTS3012, BTS3012AE, and BTS3012_II support the IP transmission mode.
Only the BTS3012, BTS3012AE, and BTS3012_II can be set to Support Separate. If
the Support Separate check box is selected, the BTS3012, BTS3012AE, and
BTS3012_ can be configured with the multi-transceiver unit.
Add a cell. For details, refer to steps 6 through 9 described in Adding a BTS (IP
Transmission Mode).
Set Frequency Band.
NOTE
Ensure that the Frequency Band of the cell should be supported by the TRX board.
3.
Configure the antenna feeder attributes for the DDPU. For details, refer to steps 10 through
13 described in Adding a BTS (IP Transmission Mode).
Set Branch No.. .
51-18
At least one TRX should be specified for the downlink tributary. For other tributaries,
use the default values or modify them as required.
The DDPU has two paths: A and B. The two paths are independent of each other. The
data configurations of the DDPU must be consistent with the physical connections, and
the frequency band of the TRX must be the same as the frequency band of the DDPU.
4.
Configure the TRX. For details, refer to steps 14 through 18 described in Adding a BTS
(IP Transmission Mode).
5.
Configure the DDPU attributes. For details, refer to steps 19 through 25 described in Adding
a BTS (IP Transmission Mode).
Issue 03 (2009-06-08)

l
On the PTU parameter of BTS tab page, set Main PTU Bar Code, Back PTU Bar
Code, and PTU Logical IP,
Back PTU Bar Code and Main PTU Bar Code must be different. They must be
unique.
If the standby board is not configured, Back PTU Bar Code must be set to a nonzero value. The zero value indicates that the parameter is null.
On the FE port parameter of BTS tab page, set Physical IP Address.

6.
If the layer 2 networking mode is used, the first physical IP address of the DPTU in
the BTS and the physical IP address of the GFGUB in the BSC must be on the same
network segment.
If the layer 3 networking mode is used, the first physical IP address of the DPTU in
the BTS and the port IP address of the router must be on the same network segment.
Configure the cell attributes. For details, refer to steps 26 through 31 described in Adding
a BTS (IP Transmission Mode).
Set MCC, MNC, LAC, CI, BCC, NCC, Cell Extension Type, and Cell Type.
7.
Add a BTS route. For details, refer to the steps described in Adding a BTS (IP Transmission
Mode).
Set Destination IP Address and Gateway.
Where, Destination IP Address is the logical IP address of the DPTU in the BTS;
Gateway and the port IP address of the DPTU must be on the same network segment.
----End
51.6.3 Configuring Gb over IP

This describes how to configure Gb over IP on the BSC6000 Local Maintenance Terminal.
Prerequisite
For details, refer to 19.6.2 Configuring GPRS (with Built-in PCU).
Procedure
Step 1 Configure the Gb interface and related parameters.
For details, refer to Step 2 in 19.6.2 Configuring GPRS (with Built-in PCU).
Step 2 Configure the SGSN.
For details, refer to Step 3 in 19.6.2 Configuring GPRS (with Built-in PCU).
----End

This lists the alarms and counters related to interface over IP.
Issue 03 (2009-06-08)

51-19

Alarms
Table 51-4 lists the alarms related to interface over IP.
Table 51-4 Alarms related to interface over IP
Alarm ID
Alarm Name
701
M3UA Link Fault
702
M3UA Link Congestion
703
M3UA Route Unvailable
704
M3UA Destination Entity Unvailably
705
PIU Route Status Unavailable
21525
SCCP DSP Unreachable
21526
SCCP Subsystem Prohibited
Counters
Table 51-5 lists the counters related to interface over IP.
Table 51-5 Counters related to interface over IP
51-20
Counter
Description
L0031
Data Blocks Retransmitted over SCTP Link
L0032
Error Packets Received over SCTP Link
L0033
Data Blocks Sent over SCTP Link
L0034
Data Blocks Received over SCTP Link
L0035
Packets Sent over SCTP Link
L0036
Packets Received over SCTP Link
L0021
M3UA Link Failure Times
L0022
M3UA Link Failure Duration
L0023
M3UA Link Congestion Duration
L0011
M3UA Destination Inaccessible Times
L0012
M3UA Destination Inaccessible Duration
L0024
M3UA Link Sent Packets
L0025
M3UA Link Received Packets
L01001
Received Bytes
Issue 03 (2009-06-08)

Counter
Description
L01002
Received Packets
L01003
Sent Bytes
L01004
Sent Packets
L01005
Error Sent Packets
SC010A
CS Packets Sent over FE Port of the PTU
SC000A
CS Packets Received over FE Port of the PTU
SC011A
PS Packets Sent over FE Port of the PTU
SC001A
PS Packets Received over FE Port of the PTU
SC012A
Control-Plane Packets Sent over FE Port of

the PTU
SC002A
Control-Plane Packets Received over FE Port

of the PTU
SC003A
Error CRC Packets Received over FE Port of

the PTU
51.8 References
.
l
3GPP TS 48.016 General Packet Radio Service (GPRS);Base Station System (BSS) Serving GPRS Support Node (SGSN) interface;Network Service
3GPP TS 23.236 Intra-domain connection of Radio Access Network (RAN) nodes to

multiple Core Network (CN) nodes
3GPP TS 48.008 Mobile Switching Centre - Base Station system (MSC-BSS) interface;
Layer 3 specification
3GPP TS 48.060 In-band control of remote transcoders and rate adaptors for full rate traffic
channels
3GPP TS 48.061 In-band control of remote transcoders and rate adaptors for half rate traffic
channels
3GPP TS 46.031 Full rate speech; Discontinuous Transmission (DTX) for full rate speech
traffic channels
3GPP TS 46.041 Half rate speech; Discontinuous Transmission (DTX) for half rate speech
traffic channels
3GPP TR 25.953 TrFO/TFO
ETSI TS 101 318 Using GSM speech codecs within ITU-T Recommendation H.323
RFC 3267 Real-Time Transport Protocol (RTP) Payload Format and File Storage Format
for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB)
Audio Codecs
Issue 03 (2009-06-08)

51-21

51-22
RFC 3551 RTP Profile for Audio and Video Conferences with Minimal Control
RFC 2198 RTP Payload for Redundant Audio Data
RFC 2960 Stream Control Transmission Protocol

Issue 03 (2009-06-08)

52
52 Abis Transmission Optimization
Abis Transmission Optimization
About This Chapter

52.1 Overview
Different from the traditional resource allocation, where a timeslot or sub-timeslot is allocated
to a traffic channel, the Abis transmission optimization allows several links to be multiplexed
on a channel composed of several timeslots. The Abis transmission optimization allows more
efficient use of transmission resources.
52.2 Availability
The Abis transmission optimization can be implemented only with the cooperation of related
NEs, the support of certain software releases, and a license.
52.3 Impact
This describes the impact of the Abis transmission optimization on the system performance and
other features.
This describes the HDLC over E1/T1, HubBTS, HDLC channel, service bearer on the BSC
signaling plane and user plane, setup and configuration of the HDLC channel on the BTS
maintenance plane and service plane, Abis data uplink technology, Abis data downlink
technology, and Abis-interface resource allocation.
52.5 Implementation
This describes the application of Abis transmission optimization engineering, including the
configuration principles of the HDLC channel, configuration of Abis transmission optimization,
and configuration of the HubBTS.
The maintenance information for Abis transmission optimization includes the associated alarms
and performance counters.
52.7 References
None.
Issue 03 (2009-06-08)

52-1

52.1 Overview
Different from the traditional resource allocation, where a timeslot or sub-timeslot is allocated
to a traffic channel, the Abis transmission optimization allows several links to be multiplexed
on a channel composed of several timeslots. The Abis transmission optimization allows more
efficient use of transmission resources.
Definition
The Abis transmission optimization employs the Voice Activity Detection (VAD) to detect and
compress the silent voice frames, and uses the High level Data Link Control (HDLC) protocol
to transmit data. It allows the CS and PS services of multiple TRXs and signaling messages to
be transmitted through an HDLC channel. The HDLC channel is shared by multiple TRXs.
Purpose
According to the attributes of voice, the total bandwidth to be allocated on a shared channel is
far less than the sum of the bandwidth required by TRXs in the same configuration. Therefore,
the share of the HDLC channel enables more efficient use of resources, optimizing the
transmission over the Abis interface.
Terms
Terms
Definition
Interworking
A table that implements protocol termination and conversion through

the transmission interface board.
The Interworking tables consist of the uplink table and downlink table.
Half static
An original configuration is generated in data configuration. This

configuration can be dynamically adjusted by the resource
management module.
52-2
Acronyms and
Abbreviations
Full Spelling
BTSM
Base Transceiver Station Management
EML
Extend Maintenance Link
ESL
Extend Signalling Link
HDLC
High level Data Link Control
HubBTS
Hub Base Transceiver Station
OML
Operation Maintenance Link
PTU
Packet Transfer Unit

Issue 03 (2009-06-08)

Acronyms and
Abbreviations
Full Spelling
RSL
Radio Signalling Link
SAPI
Service Access Point Identifier
TEI
Terminal Endpoint Identifier
VAD
Voice Active Detection
52.2 Availability
The Abis transmission optimization can be implemented only with the cooperation of related
NEs, the support of certain software releases, and a license.
NEs Involved
Table 52-1 lists the NEs required to implement the Abis transmission optimization.
Table 52-1 NEs involved in the Abis transmission optimization
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
NOTE
l -: not involved
l : involved
Software Release
Table 52-2 lists the versions of the GBSS NEs involved in the Abis transmission optimization.
Product
Version
BSC
BSC6000
BTS
BTS3012
BTS3012A
E
Issue 03 (2009-06-08)

DTRU
QTRU
DTRU
QTRU
BTS3006C
BTS3002E

52-3

Product
Version
DBS3900 GSM
Not supported
BTS3900 GSM
Not supported
BTS3900A GSM
Not supported
Miscellaneous
l
A license is required for implementing the Abis transmission optimization. The license
defines the number of TRXs that supports the Abis transmission optimization.
Only the BTS3012 and BTS3012AE support the HubBTS.
To support the HubBTS, the BTS must be configured with a DPTU.
In Abis transmission optimization mode, one E1 supports either 24 TCH/F carriers or 20

TCH/H carriers,one T1 supports either 18 TCH/F carriers or 16 TCH/H carriers.
52.3 Impact
This describes the impact of the Abis transmission optimization on the system performance and
other features.

The Abis transmission optimization does not adversely affect the system performance.

l
To implement the Abis transmission optimization, the BSC must adopt the built-in PCU.
The Abis transmission optimization does not support intra-BSC local switching, intra-BTS
local switching, or Flex Abis.
The Abis transmission optimization supports BTS cascading.

This describes the HDLC over E1/T1, HubBTS, HDLC channel, service bearer on the BSC
signaling plane and user plane, setup and configuration of the HDLC channel on the BTS
maintenance plane and service plane, Abis data uplink technology, Abis data downlink
technology, and Abis-interface resource allocation.
52.4.1 HDLC over E1/T1

The E1/T1 transmission on the Abis interface is implemented through 64 kbit/s sub-timeslots.
The Abis transmission optimization allows one or more (consecutive or non-consecutive) E1/
T1 64 kbit/s sub-timeslots to form a transmission channel that is shared by traffic links.
When TDM transmission is adopted on the Abis interface, each traffic channel, RSL, or OML
occupies a 16 kbit/s or 64 kbit/s sub-timeslot. Even when a traffic channel is idle, the sub-timeslot
is still occupied.
52-4

Issue 03 (2009-06-08)

The FlexAbis technology allows the transmission resources on the Abis interface to be allocated
based on the demand of traffic channels. When a traffic channel is idle, the system does not
allocate any timeslot for it. Thus, the transmission resources on the Abis interface can be reused
based on time. Such kind of reuse is implemented through the idle traffic channels in different
cells or sites.
Generally, the voice activation factor in a conversation is about 0.5. A voice link may have a
large number of silent frames and idle timeslots. The time-based FlexAbis technology, however,
cannot make use of this voice attribute.
The Abis transmission optimization uses HDLC to reuse the transmission resource on the Abis
interface. The HDLC mechanism increases the number of TRXs supported by an E1. The reuse
of resources is implemented through the large number of silent frames and idle timeslots on the
traffic channel. The Abis transmission optimization allows one or more (consecutive or nonconsecutive) E1/T1 64 kbit/s sub-timeslots to form an HDLC channel.
Figure 52-1 shows the networking of the system supporting the HDLC over E1/T1 function.
Figure 52-1 System networking for HDLC over E1/T1
MSC
HubBTS
BTS
BSC
HDLC over E1/T1
TDM transmission
SGSN
BTS
FE/GE/FR
transmission
BTS
BTS
BTS
52.4.2 HDLC Channel

This section describes the classification and model of the HDLC channels.
Classification
The HDLC channels can be classified into the following:
l
Issue 03 (2009-06-08)
HDLC channels on the Abis interface
HDLC channel between the GEHUB of the BSC and the DPTU of the HubBTS
HDLC channels between the GEHUB of the BSC and the DTMU of the BTSs that are
directly connected to the BSC
HDLC channels between the DPTU of the HubBTS and the DTMU of the lower-level
BTSs
52-5


l
HDLC channels in the BTS
HDLC channels between the DPTU of the HubBTS and other cabinets in the cabinet
group
HDLC channels between the main cabinet group and the extension cabinet groups of
the BTSs (supporting the Abis transmission optimization) directly connected to the BSC
or the lower-level BTSs of the HubBTS
NOTE
The main cabinet group implements transparent transmission of the data from the main cabinet group
to the extension cabinet groups over the HDLC channel.
In the BTS cascading, the intermediate HubBTS/BTS implements transparent transmission of

the data over the HDLC channel on the Abis interface.
HDLC Channel Model

Figure 52-2 shows the models of the HDLC channel.
Figure 52-2 HDLC channel model
{TS3,TS4,TS5}
{TS3,TS4,TS5}
E1(0)
HDLC connection point
{TS3,TS4,TS5}
{TS3,TS4,TS5}
Direct connection
{TS7,TS8,TS9}
{TS7,TS8,TS9}
Indirect connection
E1(1)
E1(3)
HDLC
connection point
HDLC transfer point
In the direct connection, the timeslots TS3, TS4, and TS5 of the two connection points of
the HDLC channel exchange information directly.
In the non-direct connection, TS3 of E1 (1) exchanges information with TS7 of E1 (3), TS4
of E1 (1) exchanges information with TS8 of E1 (3), and TS5 of E1 (1) exchanges
information with TS9 of E1 (3).
52.4.3 HubBTS
In the sparsely-populated area, the HubBTS networking can save transmission resources.
After the Abis transmission optimization is implemented, the BTS can be installed with a DPTU
board to implement the HubBTS function. The DPTU board converges and transfers data.
The HubBTS can converge the data from the BTSs of the same level and the lower-level BTSs.
By utilizing the feature that the transmission convergence and resource reuse can bring more
gain, the HubBTS enables the most effective use of the Abis transmission resources between
the HubBTS and the BSC.
The HubBTS also allows proper bandwidth configuration based on the traffic model. Each
HubBTS can converge a maximum of 72 TRXs.
52-6

Issue 03 (2009-06-08)

Figure 52-3 shows the networking of the HubBTS.

Figure 52-3 Networking of the HubBTS
MSC
BTS
HubBTS
BSC
HDLC over E1/T1
TDM transmission
SGSN
BTS
FE/GE/FR
transmission
BTS
BTS
BTS
NOTE
At present, only the HDLC HubBTS is supported.
52.4.4 Service Bearer on the BSC Signaling Plane and User Plane
For BTSs that support Abis transmission optimization, the service bearer on the BSC signaling
plane and user plane is bound to an HDLC channel in the unit of TRX. All signal streams are
transmitted on an HDLC channel.
The HDLC channel on the Abis interface of the HubBTS is semi-static. When configuring the
HDLC channel, first configure the HDLC channel mapping based on the bandwidth of the BTS
and TRX. When services are in progress, the BSC resource management module dynamically
adjusts the Abis resources to be allocated according to the bandwidth of the current channel.
The BSC reads different types of data such as voice service and data facsimile service data in
the CS domain and high-priority and low-priority service data in the PS domain according to
the priority of subscribers and then sends the data to the BTS through cell attributes. The BTS
dispatches and processes the associated types of frames according to the configured priority.
The priority ranges from 0 to 7. 0 indicates the highest priority, and 7 indicates the lowest priority.
You can configure the priority according to the actual requirements. The parameters are as
follows:
l
CS Voice ServicePRI
CS Data ServicePRI
PS HighPRI ServicePRI
PS LowPri ServicePRI
ESL Link
The ESL ensures the reliable transmission of important signaling messages.
Issue 03 (2009-06-08)

52-7

The ESL link in Abis transmission optimization is only used to transmit the Packet Transfer Unit
(PTU) configuration messages in the HubBTS. When the PTU is initiated, the ESL link is used
for configuring PTU messages. When the PTU starts to work, the ESL is used to for adjusting
the cross connection and transfer control table of the service plane dynamically.
On the BSC6000 Local Maintenance Terminal, you can perform message tracing and
performance measurement on the ESL link. For details, see Tracing ESL Messages on the Abis
Interface.
52.4.5 HDLC Setup on the BTS Maintenance Plane and Service

Plane
This describes the setup of the HDLC on the BTS maintenance plane and service plane in Abis
transmission optimization and HubBTS modes.
In Abis transmission optimization mode, the procedure for HDLC setup on the BTS maintenance
plane and service plane is as follows:
1.
The BTS sets up the OML link with the BSC.
2.
The BTS receives the configuration message on the OML link from the BSC, including the
HDLC configuration message and data exchange table.
You can obtain the binding relationship between the E1/T1 timeslots on the Abis interface
and the HDLC channel numbers and the bearer relationship between the BTS links and the
HDLC channels through the configuration message. Timeslot 31 is bound to a channel for
carrying the OML link.
3.
The BTS checks whether the configuration data from the BSC is complete and consistent.
If the configuration data is consistent, the internal exchange table is generated based on the
configuration data and takes effect.
4.
The BTS exchanges data according to the exchange table.

l
On the downlink, the BTS receives the data from the Abis interface and searches the
destination for exchange according to the address information in the datagram header
and the exchange table.
On the uplink, the BTS measures the amount of data to be transmitted on each TRX and
controls the transmission of uplink data on each link according to the measurement
results and the data transmission capability of the HDLC channel.
In Abis transmission optimization mode, the DPTU is added, the procedure for HDLC setup on
the BTS maintenance plane and service plane is the same as that in Abis transmission
optimization mode except that the initialization procedure for the DPTU is added. The
initialization procedure for the DPTU is as follows:
1.
The PTU sets up the ESL link with the BSC.
2.
The BSC sends the DPTU configuration information, HDLC channel binding relationship,
and data exchange table.
52.4.6 Procedure for Transmitting the BTS Uplink Data

This describes the procedure for transmitting the BTS uplink data.
The uplink data transmission technology must enable the TRXs to use the resources on the same
HDLC channel and ensure successful delivery of data to the HDLC channel.
The data transmission procedure in the BTS is as follows:
52-8

Issue 03 (2009-06-08)

1.
The BTS stores the uplink data to the buffer.
2.
The BTS calculates the volume of the data to be sent.
3.
The control TRX of the BTS sends data to the Abis interface at the specified time.
Figure 52-4 shows the procedure for transmitting the BTS uplink data.
Issue 03 (2009-06-08)

52-9

Figure 52-4 Procedure for transmitting the BTS uplink data
Start
Set up the OML link with the BSC

and receive the HDLC
configuration message and data
transfer relationship
Set up the HDLC channel on the

Abis interface
Take statistics on the data to be

transmitted on the HDLC channel
Calculate the amount of data to be

transmitted and the time for
transmitting data
Is the TRX time up?
No
Yes
Transmit the data to the Abis
interface
No
Is the transmission stop

message received?
Yes
End
52-10

Issue 03 (2009-06-08)

NOTE
In HubBTS mode, the DPTU is added to converge the data. The procedure for transmitting the BTS uplink
data is the same as that for Abis transmission optimization mode.
52.4.7 Procedure for Transmitting the BTS Downlink Data

This describes the procedure for transmitting the BTS downlink data.
On the downlink, the BTS constructs the exchange table according to the data exchange
relationship sent by the BSC. The BTS exchanges the data on the Abis interface to the specified
timeslot according to the exchange table.
Figure 52-5 shows the procedure for transmitting the BTS downlink data.
Issue 03 (2009-06-08)

52-11

Figure 52-5 Procedure for transmitting the BTS downlink data

Start
Set up the OML link with the BSC

and receive the HDLC
configuration message and data
transfer relationship
Set up the HDLC channel on the

Abis interface and build the
downlink data transfer relationship
Generate the data exchange table

based on the BSC configuration
data
Receive the data from the HDLC

channel
Is the destination
HDLC searched?
No
Discard the data
Yes
Transmit the data to the
destination link
No
Is the transmission stop

message received?
Yes
End
52-12

Issue 03 (2009-06-08)

NOTE
In HubBTS mode, the DPTU is added to converge the data. The procedure for transmitting the BTS
downlink data is the same as that for Abis transmission optimization mode.
52.4.8 Resource Allocation on the Abis Interface

This describes the resource allocation on the Abis interface.
Figure 52-6 shows the principle of resource allocation on the Abis interface. The following
describes the resource allocation on the Abis interface based on the two BTSs that are connected
through an E1 cable.
Figure 52-6 Resource allocation on the Abis interface
BSC
Abis interface
BTS1
HDLC1
TS1-TS10 timeslots
HDLC2
HDLC2
TS11-TS29 timeslots
BTS2 maintenance signaling
is multiplexed on the HDLC
OML/EML(ESL)
BTS1 maintenance signaling

is multiplexed on the HDLC
OML/EML(ESL)
BTS2
OML/EML(ESL)
The BSC is connected with BTS 1 through an E1 cable, and BTS 1 is cascaded with BTS
2.
The data on the user plane and signaling plane of all the TRXs on BTS 1 is multiplexed on
HDLC 1.
The data on the user plane and signaling plane of all the TRXs on BTS 2 is multiplexed on
HDLC 2.
The resource allocation on the Abis interface in Abis transmission optimization mode has the
same characteristics as the resource allocation in TDM mode. That is, timeslot 0 is used for
synchronization, and timeslot 31 is used for carrying the OML link between the BSC and BTS
1.
The difference between the resource allocation on the Abis interface in Abis transmission
optimization mode and the resource allocation in TDM mode is as follows: Timeslots 1-10 of
BTS 1 are combined to form an HDLC channel. All the TRXs of BTS 1 share this HDLC channel.
Not each TRX is allocated with a timeslot.
52.5 Implementation
This describes the application of Abis transmission optimization engineering, including the
configuration principles of the HDLC channel, configuration of Abis transmission optimization,
and configuration of the HubBTS.
Issue 03 (2009-06-08)

52-13

52.5.1 Configuration Principles of the HDLC Channel

This describes the configuration principles of the HDLC channel.
The configuration principles of the HDLC channel are as follows:
l
The HDLC channel can be bound with multiple 64 kbit/s timeslots. The 64 kbit/s timeslots
can be discontinuous.
The HDLC channel does not support the binding of sub-timeslots. An HDLC channel
cannot be configured on two E1/T1 cables. That is, the HDLC channel cannot be configured
cross the E1/T1 cables.
In E1 mode, the HDLC channel supports the binding of a maximum of 31 timeslots. In T1

mode, the HDLC channel supports the binding of a maximum of 24 timeslots.
When the HDLC channel is bound with multiple timeslots, it transmits and receives data
according to the sequence of timeslots. Because the timeslots in the middle node use
transparent transmission configuration, cross connection must be established according to
the timeslot sequence.
The HDLC channel must be configured according to the channel type and bandwidth. The
continuous HDLC channel is recommended.
52.5.2 Configuring Abis Transmission Optimization or HubBTS

This describes how to configure Abis transmission optimization or HubBTS on the BSC6000
Prerequisite
l
Apply for the license and activate it.

1.
To apply for the license of Abis transmission optimization or HubBTS, enter the
number of TRXs that need to support Abis transmission optimization or HubBTS in
the specification range in Number of TRXs supporting Abis transmission
optimization or Number of HubBTS TRXs supporting HDLC in the Resource
control items column in the BSC6000V900R008 Exceptional Commercial License
Application Template.
2.
Activate the license on the Local Maintenance Terminal. For details, see Activating
the BSC License.
The BTS has the DPTU board, and the BSC has the GEHUB board.
There are idle ports on the GEHUB in the GMPS or GEPS.
The GXPUM/GXPUT is configured for the GMPS or GEPS where the GEHUB is located.
NOTE
The difference between the HubBTS configuration and the Abis transmission optimization configuration
lies in the transmission bearer mode. The transmission bearer mode of the HubBTS is HDLC HubBTS,
and that of Abis transmission optimization is HDLC.
This operation takes adding a HubBTS transmission mode on the GEHUB in the GEPS as an example.
52-14

Issue 03 (2009-06-08)

Table 52-3 Example of the data negotiated and planned for adding a BTS
Parameter
Site
Attributes
Cell
attributes
Issue 03 (2009-06-08)
Example
Source
Site Name
BTS 1
Network
Planning
Site Type
BTS3012
Network
Planning
Upper-Level Port No.
0 GEHUB Port
Network
Planning
Multiplexing Mode
4:1
Network
Planning
FlexAbis Mode
Fix Abis
Network
Planning
Service Mode
HDLC HubBTS
Network
Planning
In Port
Network
Planning
Config Ring
No
Network
Planning
Config AbisByPass
No
Network
Planning
Cell Name
Cell 1
Network
Planning
Frequency Band
GSM900
Network
Planning
MCC
460
Network
Planning
MNC
01
Network
Planning
LAC
8240
Network
Planning
CI
Network
Planning
BCC
Network
Planning
NCC
Network
Planning
Cell Extension Type
Common Cell
Network
Planning

52-15

Parameter
TRX
Attributes
Antenna
feeder
attributes
Example
Source
Cell Type
Common Cell
Network
Planning
Assigned Cell
Cell 1
Network
Planning
Freq Config
988 (main BCCH

frequency), 994
Network
Planning
TRX Config
TRX 0, TRX 1
Network
Planning
FH MODE
None.
Network
Planning
Tributary No.
Downlink Tributary
Network
Planning
Band Type
PGSM900
Network
Planning
TRX Transmit and Receive

Relationship
TRX No.1: 0, A
Network
Planning
TRX No.2: 1, B
Procedure
Step 1 Start the wizard for adding a BTS.
l When adding a BTS for the first time, you can start the wizard for adding a BTS only on the
GEHUB in the GMPS or GEPS. On the BSC6000 Local Maintenance Terminal, right-click
a GEHUB in the GEPS.
l If a BTS already exists, you can add a cascaded BTS under this BTS. On the Management
Tree tab page, right-click a BTS.
Step 2 Choose Add Site from the shortcut menu. A dialog box is displayed, as shown in Figure 52-7.
52-16

Issue 03 (2009-06-08)

Step 3 Click Add Site. A dialog box is displayed, as shown in Figure 52-8.
Figure 52-8 Add New Site dialog box
Step 4 Set the parameters by referring to Table 52-3.

NOTE
The Support Separate option is available only for the BTS3012, BTS3012 II, and BTS3012AE. If Support
Separate is selected, the BTS3012, BTS3012 II, and BTS3012AE can be configured with the multi-TRX
boards.
Step 5 Click OK. A dialog box is displayed, as shown in Figure 52-9.
Issue 03 (2009-06-08)

52-17


Step 7 Select a BTS, and then click Add Cell. A dialog box is displayed, as shown in Figure 52-11.
52-18

Issue 03 (2009-06-08)

Figure 52-11 Adding a cell
Step 8 Set the parameters by referring to Table 52-3.

NOTE
To add more cells at a time, set Number of Cells. The added cell is named in the form of current Cell
Name + sequential number.
Step 9 Click OK. A dialog box is displayed, as shown in Figure 52-12.

Issue 03 (2009-06-08)

52-19

Step 11 Click Site Attributes. A dialog box is displayed, as shown in Figure 52-14.
52-20

Issue 03 (2009-06-08)

Figure 52-14 Site Device Attributes dialog box
Step 12 Double-click DDPU. A dialog box is displayed, as shown in Figure 52-15.
Issue 03 (2009-06-08)

52-21

Figure 52-15 Set antenna feeder property dialog box
NOTE
This takes the configuration of one antenna feeder port on the DDPU as an example. If the antenna
feeder port is not required, you can delete the DDPU.
You have to specify at least one TRX for the downlink tributary of the DDPU. For other tributaries,
use the default settings.
The DDPU has two paths: A and B. The two paths are independent of each other. The data
configurations of the DDPU must be consistent with the physical connections, and the frequency band
of the TRX must be the same as the frequency band of the DDPU.
Step 13 Set the parameters by referring to Table 52-3, as shown in Figure 52-16.
Figure 52-16 Setting antenna feeder attributes
52-22

Issue 03 (2009-06-08)

Step 14 In the dialog box shown in Figure 52-14, right-click an empty slot in the DTRU and choose
Add Board > TRU from the shortcut menu. A TRU is added.
Step 15 Right-click the added TRU and choose Configure Board Attributes from the shortcut menu.
Figure 52-17 Binding Logical TRX dialog box
Step 16 Set Assigned Cell by referring to Table 52-3.

Step 18 Repeat Step 14 through Step 17 to configure more TRX boards.
Issue 03 (2009-06-08)

52-23

Step 21 Click Cell Attributes. A dialog box is displayed, as shown in Figure 52-19.
Step 22 Set the basic attributes of the cell by referring to Table 52-3.
NOTE
The CI of a cell must be unique.
If you select GPRS Support, the BSC must be configured with the built-in PCU. If the BTS does not
support the GPRS function or the GPRS services are unavailable in the cell, do not select GPRS
Support.

Step 24 Click Finish. The BTS is configured.
----End

The maintenance information for Abis transmission optimization includes the associated alarms
and performance counters.
52-24

Issue 03 (2009-06-08)

Alarms
Table 52-4 lists the alarms related to Abis transmission optimization.
Table 52-4 Alarms related to Abis transmission optimization
Alarm ID
Alarm Name
422
BTS doesn't support abis optimize
423
Extension Signaling Link Failure
Counters
Table 52-5 lists the performance counters related to Abis transmission optimization.
Table 52-5 Performance counters related to Abis transmission optimization
Issue 03 (2009-06-08)
Counter
Description
S4010A
Sent CS Packets
S4010B
Sent CS Bytes
S4013A
Sent but Lost CS Packets
S4000A
Received CS Packets
S4000B
Received CS Bytes
S4003A
Received but Lost CS Packets
S4011A
Sent PS Packets
S4011B
Sent PS Bytes
S4014A
Sent but Lost PS Packets
S4001A
Received PS Packets
S4001B
Received PS Bytes
S4004A
Received but Lost PS Packets
S4012A
Sent Signaling-Plane Packets
S4012B
Sent Signaling-Plane Bytes
S4015A
Sent but Lost Signaling-Plane Packets
S4002A
Received Signaling-Plane Packets
S4002B
Received Signaling-Plane Bytes
S4005A
Received but Lost Signaling-Plane Packets
SD010A
CS Packets Sent over HDLC Path

52-25

Counter
Description
SD000A
CS Packets Received Over HDLC Path
SD011
PS Packets Sent Over HDLC Path
SD001
PS Packets Received Over HDLC Path
SD012
Control-Plane Packets Sent over HDLC Path
SD002
Control-Plane Packets Received over HDLC

Path
SD02
Packets Overflowed over HDLC Path
SD003
Error CRC Packets Received over HDLC Path
52.7 References
None.
52-26

Issue 03 (2009-06-08)

BSS Feature Description (Continue) PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSS Feature Description (Continue) PDF

Uploaded by

Copyright:

Available Formats

HUAWEI BSC6000 Base Station Subsystem