Allahabad BSC-2 TASR degradation.

Allahabad BSC-2
TASR Degradation

Document Type: Analysis.

Document Number: Huawei-GSM-24092011-01)

Prepared By Reviewed By Authorized By

Manish Singh Deep Dhiman Hiren Joshi

Release On :- 24-Sept 2010

Page 1 of 5 ALUMS TEC-RAN

 Allahabad BSC-2 TASR degradation.

Allahabad BSC-2 TASR Degradation Analysis

Problem Description
In Allahabad GSM BSC-2, a large number of assignment failures occurring
between 19 hrs to 23 hrs.

Problem Analysis
• Cause

In Allahabad BSC-2, 517 TRXs are configured in subrack 0 and 755 TRXs are
configured in subrack-1 of a BSC. All GDPUP boards are configured in
subrack 0. As a result, when PS services are busy, a lot of intra-subrack
LVDS resources are occupied by PS services but no resources are allocated
to CS services. Therefore, assignment failures occur and the cause is
equipment failure: terrestrial resource request failed.
When GDPUP boards are configured only in subrack 0, LVDS resources need
to be allocated to both PS services and CS services through the GTNU
boards for inter-subrack processing. When PS services are busy, a lot of
inter-subrack LVDS resources are occupied by PS services. The total number
of LVDS resources, however, is 4096. In this case, no inter-subrack LVDS
resources can be allocated to CS services and therefore assignment failures
occur. When GDPUP boards are configured in subrack 1, PS services are
processed by GDPUP boards in subrack 1. After that, messages are sent to
subrack 0 through GSCU boards. In this case, PS services will not occupy
inter-subrack LVDS resources for inter-subrack processing and therefore CS
services will not be affected.
The BSC collects the number of assignment requests after receiving the ASS
REQ message sent by the MSC. In this case, when the TASR is low, the
number of assignment requests increases due to subscriber behaviors.

• Impact

When PS services are busy, CS services are affected. As a result, a lot of

assignment failures occur, which affects accessing of MSs.

• Trigger Scenario

The data configuration is improper. A large number of TRXs are configured

but no GDPUP boards are configured in subrack 1.

Page 2 of 5 ALUMS TEC-RAN

 Allahabad BSC-2 TASR degradation.

Detailed Analysis
• Analysis of Configuration Data

According to data configuration of the Allahabad BSC-2, it is found the

following conditions are available on BSC:

(1) A large number of TRXs are configured in subrack 1.

(2) Two GDPUP boards are configured in subrack 0.

Allahabad BSC-2:

• Analysis of Traffic Measurement Counters

According to traffic measurement counters, assignment failures were pegged

in A3129B:Failed Assignments (First Assignment, Terrestrial Resource
Request Failed) counter (call drops due to equipment failure) occur because
the terrestrial resource request failed.
In addition, Out of 200 affected cells 196 are in subrack-1 of BSC .So
assignment failures occur mainly in cells under subrack 1 of BSC.
Allahabad BSC-2

Page 3 of 5 ALUMS TEC-RAN

 Allahabad BSC-2 TASR degradation.

SUM:Failed Assignments (First Assignment, Terrestrial Resource Request

Failed)
Subrack Total A3129B:Failed Assignments (First Assignment,
No. Terrestrial Resource Request Failed)(times)
0 13
1 61166
2 11
Grand Total 61190

In Allahabad BSC-2, the number of channels configured in each subrack is as

follows:

Channel Type Subrack 0 Subrack 1 Subrack 2

Row Labels 0 1 2
Main BCCH 144 216 149
PDTCH 312 437 332
SDCCH+CBCH 144 216 148
SDCCH8 85 152 72
TCH Full Rate 3451 5019 3091
PDCH+TCH/F 3763 5456 3423
(=(PDCH+TCH/F)*Maximum
Ratio Threshold of PDCHs
in a Cell) 1317.05 1909.6 1198.05

On the BSC, the number of average LVDS resources occupied by each PS

service is as follows:

Page 4 of 5 ALUMS TEC-RAN

 Allahabad BSC-2 TASR degradation.

In theory, the total number of LVDS resources occupied by PS services during

the busiest hours is 4815 (1909.6 x (Average LVD=2.52) = 4815). The total
number of actually configured inter-subrack LVDS resources, however, is
4096. In this case, no LVDS resources can be allocated to CS services when
PS services are busy.

Improvement:
After Shifting the GDPUp board from subrack-0 slot-9 to Subrack-1 slot-9 the failure reduced to
almost less than 50.

Suggestion:
It is recommended that data should be reconfigured at the site, that is, TRXs
should be evenly allocated in each subrack and GDPUP boards should be
evenly allocated in each subrack. Two GDPUP boards are configured only in
subrack 0 on the BSC at the site. It is recommended that GDPUP boards
should be configured in each subrack.
In addition, as the rapid development of data services on each BSC on the
live network, congestion is likely to occur in the future.The total number of
PDCHs and TCH/Fs configured on the entire BSC is 12642. When Maximum
Ratio Threshold of PDCH is set to 30%, the maximum number of PDCHs is
3793. On the live network, each BSC is configured with a maximum of 1024
PDCHs. As the increasing of data subscribers, the number of required PDCHs
may exceed 1024 during busy hours. It is recommended that the capacity of
GDPUPs should be expanded as soon as possible to solve the problem that
congestion may occur as the rapid increasing of data subscribers.

Page 5 of 5 ALUMS TEC-RAN