
2/19

2 DN03499862

Issue 5-1


Id:0900d80580787c84

The information in this document is subject to change without notice and describes only the

product defined in the introduction of this documentation. This documentation is intended for the

use of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted

in any form or means without the prior written permission of Nokia Siemens Networks. The

documentation has been prepared to be used by professional and properly trained personnel,

and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes

customer comments as part of the process of continuous development and improvement of the

documentation.

The information or statements given in this documentation concerning the suitability, capacity,

or performance of the mentioned hardware or software products are given "as is" and all liability

arising in connection with such hardware or software products shall be defined conclusively and

finally in a separate agreement between Nokia Siemens Networks and the customer. However,

Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions

contained in the document are adequate and free of material errors and omissions. Nokia

Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which

may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO

EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-

TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-

RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED

TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY

OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION

IN IT.

This documentation and the product it describes are considered protected by copyrights and

other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark

of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respectiveowners, and they are mentioned for identification purposes only.

Copyright Nokia Siemens Networks 2010. All rights reserved

f Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment.

Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal

injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected

has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Span-

nung. Einige Teile knnen auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverlet-

zungen und Sachschden fhren.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die

Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene

Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.


3/19

DN03499862

Issue 5-1

3


Id:0900d80580787c84

Table of ContentsThis document has 19 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Overview of Soft Channel Capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 Requirements for Soft Channel Capacity. . . . . . . . . . . . . . . . . . . . . . . . . 9

3 Technical description of Soft Channel Capacity . . . . . . . . . . . . . . . . . . 10

3.1 BSC radio network configuration with Soft Channel Capacity. . . . . . . . 10

3.2 Radio channel allocation with Soft Channel Capacity . . . . . . . . . . . . . . 10

3.3 Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4 User interface of Soft Channel Capacity . . . . . . . . . . . . . . . . . . . . . . . . 18


4/19

4 DN03499862

Issue 5-1


Id:0900d80580787c84

List of FiguresFigure 1 Example of active traffic channel limits per BCSU . . . . . . . . . . . . . . . . . 11

Figure 2 Example of cell capacity assurance algorithm . . . . . . . . . . . . . . . . . . . . 12


5/19

DN03499862

Issue 5-1

5


Id:0900d80580787c84

List of TablesTable 1 Maximum number of TCHs per BCSU . . . . . . . . . . . . . . . . . . . . . . . . . 10

Table 2 Maximum number of simultaneously active TCHs per BCSU . . . . . . . . 10

Table 3 Number of active TCHs depending on the activation type . . . . . . . . . . 11

Table 4 Soft Channel Capacity interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . 12


6/19

6 DN03499862

Issue 5-1


Id:0900d80580787c84


7/19

DN03499862

Issue 5-1

7

Soft Channel Capacity in BSC Summary of changes

Id:0900d805807874e4

Summary of changesChanges between document issues are cumulative. Therefore, the latest document

issue contains all changes made to previous issues.

Changes made between issues 5-1 and 5-0

Information on allocation of HR TCH channels for low tariff users has been added to

interworkingin chapterTechnical description of Soft Channel Capacity.


Flexi BSC has been added to tables Maximum number of TCHs per BCSUand

Maximum number of simultaneously active TCHs per BCSUin chapterTechnical

description of Soft Channel Capacity.


Information on radio network recovery has been added to table Soft Channel Capacityinterworkingin chapterTechnical description of Soft Channel Capacity.


Information on Inter-System Direct Access has been removed from Technical descrip-

tion of Soft Channel Capacity in BSC, as it is no longer relevant.


8/19

8 DN03499862

Issue 5-1


Id:0900d8058058fcd2

Overview of Soft Channel Capacity

1 Overview of Soft Channel CapacitySoft Channel Capacity increases the traffic channel (TCH) limit on the BSC2i and

BSC3i platforms. The existing limit of the number of TCHs per BSC is doubled. You can

configure all the radio traffic timeslots of all the half rate (HR) capable TRXs to dual rate

(DR) support. The overall traffic processing capacity of the BSC is not increased. The

traffic processing capacity of the BSC remains on the level defined in the BSC2i and

BSC3i product descriptions.

Soft Channel Capacity is a licence-based application software. Its use is controlled by a

capacity licence based on the number of TRXs. With one TRX licence, you can have

eight additional AMR HR channels. For more information on licensing, see Licence Man-

agement in BSC.

Benefits

With Soft Channel Capacity, you can fully utilise the AMR HR application software in the

existing networks without deploying more BSCs.

Related topics in Overview of Soft Channel Capacity

Requirements for Soft Channel Capacity

Technical description of Soft Channel Capacity

User interface of Soft Channel Capacity

Other related topics

Descriptions

Radio Channel Allocation

Traffic Reason Handover in BSC

RF Power Control and Handover Algorithm

Radio Network Recovery and State Management

GSM-WCDMA Interworking

Common BCCH Control in BSC

Enhanced Speech Codecs: AMR and EFR

Direct Access to Desired Layer/Band

GPRS/EDGE

HSCSD and 14.4 kbit/s Data Services in BSC

Wireless Priority Service

Trunk reservation

Product Description of BSC2i and BSCi High Capacity Base Station Controller Product Description of BSC3i High Capacity Base Station Controller

Instructions

BSS Transmission Configuration

Licence Management in BSC

Reference

Base Station Alarms (70007999)

1 Traffic Measurement

2 Resource Availability Measurement

109 Soft Channel Capacity Measurement

BSS Radio Network Parameter Dictionary

General Error Messages of System
http://general_glossary.pdf/http://general_glossary.pdf/http://dn9814168.pdf/http://dn9814214.pdf/http://dn9814129.pdf/http://dn9814008.pdf/http://dn01159377.pdf/http://dn0176501.pdf/http://dn9814098.pdf/http://dn98799824.pdf/http://dn03299216.pdf/http://dn9813893.pdf/http://dn0294915.pdf/http://dn9814265.pdf/http://dn99558545.pdf/http://dn01149718.pdf/http://dn9812391.pdf/http://dn04112837.pdf/http://pdn9813099.pdf/http://dn9813827.pdf/http://dn9813757.pdf/http://dn05207461.pdf/http://dn9813866.pdf/http://dn9813866.pdf/http://dn05207461.pdf/http://dn9813757.pdf/http://dn9813827.pdf/http://pdn9813099.pdf/http://dn04112837.pdf/http://dn9812391.pdf/http://dn01149718.pdf/http://dn99558545.pdf/http://dn9814265.pdf/http://dn0294915.pdf/http://dn9813893.pdf/http://dn03299216.pdf/http://dn98799824.pdf/http://dn9814098.pdf/http://dn0176501.pdf/http://dn01159377.pdf/http://dn9814008.pdf/http://dn9814129.pdf/http://dn9814214.pdf/http://dn9814168.pdf/http://general_glossary.pdf/http://general_glossary.pdf/


9/19

DN03499862

Issue 5-1

9

Soft Channel Capacity in BSC Requirements for Soft Channel Capacity

Id:0900d8058058fcd5

2 Requirements for Soft Channel Capacity

Software requirements

Soft Channel Capacity requires that AMR HR is in use.

Hardware requirements

Soft Channel Capacity requires BSC2i or BSC3i.

In BSC2, the existing limit on number of traffic channels per BSC is not changed.

TRXSIG capacity

The restrictions set by the TRXSIG capacity are also valid with Soft Channel Capacity.

You should not create more radio channels per TRX than recommended in BSS Trans-

mission Configuration.
http://general_glossary.pdf/http://general_glossary.pdf/


10/19

10 DN03499862

Issue 5-1


Id:0900d80580787331


3 Technical description of Soft Channel

Capacity

3.1 BSC radio network configuration with Soft Channel

Capacity

With Soft Channel Capacity, the maximum number oftraffic channels (TCH) per BSC

signalling unit (BCSU) is doubled. The new numbers are shown in table Maximum

number of TCHs per BCSU.

With these new limits it is possible to configure all radio traffic timeslots to dual rate (DR)

support. Increasing the limits means that more TCHs can be created in the radio network

than are allowed to be activated simultaneously. This is extra TCH capacity.

3.2 Radio channel allocation with Soft Channel Capacity

Maximum number of simultaneously active traffic channels per BCSU

The limits of the number of simultaneously active traffic channels (TCH) per BCSU are

shown in table Maximum number of simultaneously active TCHs per BCSU.

The number of active TCHs per BCSU is maintained in the BSC. The radio resource

management part of the BSC controls the usage of TCHs. If the number of active TCHs

in the BCSU reaches the limit value, it is not possible to activate a new TCH in the TRXs

controlled by that BCSU until an active TCH has been released. Figure Example of

active traffic channel limits per BCSUgives an example of activeTCH limits per BCSU

in BSC2i.

BSC type Number of TCHs in the BCSU

BSC2i 1024

BSC3i 660 1760

BSC3i 1000/2000 3200

Flexi BSC 8000

Table 1 Maximum number of TCHs per BCSU

BSC type Number of simultaneously active

TCHs in the BCSU

BSC2i 512

BSC3i 660 880

BSC3i 1000/2000 1600

Flexi BSC 4000

Table 2 Maximum number of simultaneously active TCHs per BCSU
http://general_glossary.pdf/http://general_glossary.pdf/http://general_glossary.pdf/http://general_glossary.pdf/http://general_glossary.pdf/http://general_glossary.pdf/


11/19

DN03499862

Issue 5-1

11

Soft Channel Capacity in BSC Technical description of Soft Channel Capacity

Id:0900d80580787331

Figure 1 Example of active traffic channel limits per BCSU

In the example, it is not possible to allocate a TCH in TRX 1 or in TRX 2. In BCSU 1 the

maximum number of TCHs is already activated. In BCSU 2 all the TCHs are already acti-

vated. It is possible to allocate a TCH only in TRX 3. If TRX 3 happens to be in usealready, it is not possible to allocate a TCH in the cell even if there were free channels

in TRX 1.

The principles of calculating the number of active TCHs are described in table Number

of active TCHs depending on the activation type.

Cell capacity assurance

The cell capacity assurance algorithm ensures that a sufficient number of TCHs can be

activated in each cell of the network at any time even if extra TCH capacity has beencreated in the radio network. This algorithm assures that the minimum number of the

calls that can be set up in each cell of the network at any time is equal to the number of

the created TCH timeslots in the cells, that is, the cell capacity assurance level is 100%.

Figure Example of cell capacity assurance algorithm describes the cell capacity assur-

ance algorithm.

Activation type Number of active TCHs

Full rate single slot CS call 1

Half rate single slot CS call 1

2-timeslot multislot CS data call 2



GPRS/EDGE territory timeslot 1

Dynamic SDCCH timeslot 1

CS connection of a DTM call 1

Table 3 Number of active TCHs depending on the activation type

BSC2i

BCSU 1: 600 TCHs created

512 TCHs active

BCSU 2: 500 TCHs created500 TCHs active

TRX 1

BTS 1

TRX 2

TRX 3

BCSU 1

BCSU 3

BCSU 2



12/19

12 DN03499862

Issue 5-1


Id:0900d80580787331


Figure 2 Example of cell capacity assurance algorithm

The assured TCH capacity of BTS 1, 2, and 3 together is 18 TCHs. Only 6 TCHs are

currently active in those BTSs. The maximum number of simultaneously active TCHs in

BCSU 1 is 512. Of those, 500 are already active. Therefore, it is not possible to activate

a TCH in TRX 4 of BTS 4. The free resources of BCSU 1 must be saved for BTSs 1, 2,

and 3 to assure sufficient number of calls in each of the BTSs. In BTS 4, it is possible to

allocate a TCH only in TRX 5 at the moment.

3.3 Interworking

The extra TCH capacity created in the radio network has effects on various operating

and application software in the BSC. The effects are described in table Soft Channel

Capacity interworking.

BTS 1: assured capacity6 TCHs2 active TCHs


BSC2i




BCSU 2: 500 TCHs created

490 TCHs active

TRX 1

BTS 1

TRX 3

BTS 3BCSU 1

TRX 2

BTS 2

TRX 5

TRX 4

BTS 4BCSU 2

BTS 4: TRX 4 assured TCHcapacity activated

Basic/application software Interworking

Congestion time The BSC starts the congestion time if the number

of idle channels in the BTS drops to zero. If extra

TCH capacity has been created in the BTSs, it is

possible to have the radio channel allocation

attempts rejected because of a lack of traffic

handling capacity in the BCSU even if the conges-

tion time is not shown in the statistics.

Table 4 Soft Channel Capacity interworking
http://general_glossary.pdf/http://general_glossary.pdf/http://general_glossary.pdf/http://general_glossary.pdf/


13/19

DN03499862

Issue 5-1

13


Id:0900d80580787331

Intra-BTS handovers because of

GPRS/EDGE or high-speed circuit-

switched data (HSCSD)

Intra-BTS handovers are started for the single-slot

circuit-switched (CS) calls in the BSC to enable

the GPRS/EDGE territory upgrade or the HSCSDupgrade. The BSC starts these handovers based

on the number of idle channels in the BTSs. If

extra TCH capacity has been created in the BTSs,

it is possible to have handover attempts started

and rejected because of a lack of traffic handling

capacity in the BCSU although there are idle

channels in the BTSs.

For more information on GPRS/EDGE and

HSCSD, see EDGE System Feature Description

and HSCSD and 14.4 kbit/s Data Services in

BSC.

GPRS/EDGE margins The GPRS/EDGE territory upgrade and down-

grade decisions are based on the number of idletimeslots in the BTS. If extra TCH capacity has

been created in the BTS, the downgrade margin

does not work optimally. The GPRS/EDGE terri-

tory downgrade caused by the increasing CS

traffic is not started as early as without extra TCH

capacity. The effects can be reduced by setting

the BSC parameters free TSL for CS

upgrade (CSU) and free TSL for CS

downgrade (CSD) to maximum values.

Wireless Priority Service (WPS) WPS is application software in the BSC. The radio

channel allocation for the public (RCAP) algorithm

is based on the traffic load situation in the cell. The

BSC checks the cell resource usage based on theBSC parameters WPS priority capacity

(WPIC) and WPS preference capacity

(WPEC). If extra TCH capacity has been created

in the cell, it is possible that the round robin allo-

cation is invoked too late and no resources are

available for an incoming public user in the cell.

This situation can be avoided by reducing the

values of the WPIC and WPEC parameters and

increasing the value of the BSC parameter

public served count (PSC). The values of

the WPIC and WPEC parameters should be

reduced in relation to the amount of extra TCH

capacity in the network. If the number of TCHshas been doubled in the network, the values of the

parameters should be halved.

For more information, see Wireless Priority

Service under Feature descriptions/Value added

services and BSS Radio Network Parameter Dic-

tionary.


Table 4 Soft Channel Capacity interworking (Cont.)


14/19

14 DN03499862

Issue 5-1


Id:0900d80580787331


Directed Retry for a queued WPS

user

The BSC checks the cell resource usage of the

target cells based on the BSC parameters WPS

priority capacity (WPIC) and WPSpreference capacity (WPEC). If extra TCH

capacity has been created in the cell, it is possible

that a Directed Retry handover for a queued WPS

user is started to a cell which actually is congested

and the WPS call setup is interrupted. This situa-

tion can be avoided by reducing the values of the

WPIC and WPEC parameters. The values of these

parameters should be reduced in relation to the

amount of extra TCH capacity in the network. If

the number of TCHs has been doubled in the

network, the values of the parameters should be

halved.

For more information, see Wireless Priority

Service under Feature descriptions/Value added

services and BSS Radio Network Parameter Dic-

tionary.

BSC-initiated Traffic Reason

Handover (BSC-initiated TRHO)

BSC-initiated TRHO is a part of Advanced Multi-

layer Handling application software in the BSC.

The BSC checks the traffic load situation in the

serving cell based on the parameterAMH upper

load threshold (AUT). If the traffic load of the

serving cell exceeds the AUT parameter, the BSC

tries to hand over calls to other, less loaded cells.

If extra TCH capacity has been created in the

serving cell, the handovers are started later than

without extra capacity. It is possible that the cell isalready congested but the handovers are not

started because of the extra TCH capacity. The

effects can be minimised by reducing the value of

the AUT parameter.

The load of the target cell in the BSC TRHO

attempt is checked based on the value of the

parameterAMH max load of target cell

(AML). If the traffic load in the target cell is below

the value of the AML parameter, the call is handed

over to the target cell. The aim is to avoid making

handovers from one congested cell to another. If

extra TCH capacity has been created in the target

cell, the handover can be made to a cell which

already is almost congested. The effects can be

minimised by reducing the value of the AML

parameter. The values of the AUT and AML param-

eters should be reduced in relation to the amount

of extra TCH capacity in the network. If the

number of TCHs has been doubled in the network,

the values of the parameters should be halved.

For more information, see RF Power Control and

Handover Algorithm.




15/19

DN03499862

Issue 5-1

15


Id:0900d80580787331

MSC-initiated TRHO The BSC reports the number of idle TCHs in the

cells to the MSC. If extra TCH capacity has been

created in the cell, it is not necessarily possible toallocate all the reported idle channels of a cell

simultaneously. As a consequence, the MSC may

start handovers from one congested cell to

another.

For more information, see Traffic Reason

Handover in BSC.

Direct Access to Desired

Layer/Band (DADL/B)

DADL/B is application software in the BSC. When

DADL/B is activated, the BSC checks the traffic

load situation in the accessed cell based on the

BTS parameterBTS load threshold (BLT).

If the traffic load of the accessed cell exceeds the

value of the BLT parameter, the BSC tries to direct

the call to another layer or band of the network. Ifextra TCH capacity has been created in the

accessed cell, the calls are not directed to another

layer or band as early as without extra TCH

capacity. The effects can be minimised by

reducing the value of the BLT parameter. The

value of the BLT parameter should be reduced in

relation to the amount of extra TCH capacity in the

network. If the number of TCHs has been doubled

in the cell, the value of the parameter should be

halved.

For more information, see Direct Access to

Desired Layer/Band.




16/19

16 DN03499862

Issue 5-1


Id:0900d80580787331


Load distribution between the

BTSs of the segment

The load distribution between different BTSs in a

segment is controlled with the BTS parameter

BTS load in SEG (LSEG). For each call, theBSC checks the resource usage of each BTS of

the target segment based on the LSEG parameter.

The BSC then decides to which BTS the call is

directed. The aim is to keep the load of each BTS

within the limit that the LSEG parameter defines. If

extra TCH capacity has been created in the

segment, the calls are not directed, for example,

to a non-BCCH layer of the segment as early as

without extra TCH capacity. The effects can be

minimised by adjusting the value of the LSEG

parameter. The value of the LSEG parameter

should be reduced in relation to the amount of

extra TCH capacity in the network. If the number

of TCHs has been doubled in the BTS, the valueof the parameter should be halved. However, if

the value of the LSEG parameter has already been

set to a low value (about 10% or lower), there is

not necessarily any need to change the value. In

this case the load distribution between layers in

the segment works well also with the extra TCH

capacity.

For more information on the load distribution

between the BTSs of the segment, see Common

BCCH Control in BSC.

Dynamic SDCCH reconfiguration The last idle TCH timeslot of a cell is not supposed

to be reconfigured to the stand-alone dedicatedcontrol channel (SDCCH). In case of the last idle

TCH timeslot the FACCH call setup is applied.

However, if extra TCH capacity has been created

in the cell, it is possible that the dynamic SDCCH

reconfiguration causes temporary TCH conges-

tion in the cell.

For more information on Dynamic SDCCH, see

chapterDynamic SDCCHin Radio Channel Allo-

cation.




17/19

DN03499862

Issue 5-1

17


Id:0900d80580787331

Related topics

Overview of Soft Channel Capacity

GSM-WCDMA Inter-System

Handover (ISHO)

ISHO from a GSM to a WCDMA RAN cell for

speech calls is started on the basis of the traffic

load in the serving GSM cell. The load in theserving cell is checked with the handover param-

etermin traffic load for speech call

(LTSC). The handover is not started until the load

in the serving cell exceeds the threshold. If extra

TCH capacity has been created in the serving cell,

the handovers to the WCDMA RAN cell are not

started as early as without extra TCH capacity.

The effect can be minimised by reducing the value

of the LTSC parameter. The value of the LTSC

parameter should be reduced in relation to the

amount of extra TCH capacity in the network. I f

the number of TCHs has been doubled in the cell,

the value of the parameter should be halved.

For more information on ISHO, see GSM-

WCDMA Interworking.

Trunk Reservation Trunk Reservation does not work optimally if extra

TCH capacity has been created in the BSC. The

trunk reservation algorithm takes into account all

the created radio interface TCHs. If extra TCH

capacity has been created in the BSC, the trunk

reservation algorithm cannot ensure that there is

always capacity available for the priority user in a

cell.

For more information, see Trunk Reservation.

Radio network recovery In a recovery situation, either al l timeslots of the

TRX are reconfigurated or the user defined traffic

timeslots of the TRX are returned, depending on

the BTS configuration. This means that the

number of TCHs per BCSU can change.

For more information, see Radio Network

Recovery and State Management.

Priority based voice quality without

MMI

Soft Channel capacity does not prevent the use of

TCH/H for a low tariff user.




18/19

18 DN03499862

Issue 5-1


Id:0900d8058058fcdb

User interface of Soft Channel Capacity

4 User interface of Soft Channel Capacity

MML commands

Transceiver Handling(command group ER)With the ERM command, you can modify the full rate (FR) radio timeslots to dual rate

(DR) support.

Base Station Controller Parameter Handling(command group EE)

With the EEI command, you can check the number of real TCHs under BCSUs.

Licence and Feature Handling(command group W7)

With the W7I command, you can check the status of the licence.

With the W7M command, you can modify the status of the licence.

For more information on the command groups and MML commands, see MML com-

mands.

Error codes

SOFT CHANNEL CAPACITY LICENCE EXCEEDED

With this error code, the BSC informs you that the maximum amount of soft channels

in the BSC is exceeded.

AMOUNT OF SOFT CHANNELS IN BSC EXCEEDS AMR HR LICENCE CAPACITY

With this error code, the BSC informs you that there are more soft channels config-

ured in the BSC than the AMR HR licence allows.

SOFT CHANNEL CAPACITY FEATURE IS NOT IN USE IN BSC

With this error code, the BSC informs you that Soft Channel Capacity is not in use

in the BSC.

For more information, see Licence Management in BSCand General Error Messages

of System.

Alarms

7746 CH CONGESTION IN CELL ABOVE DEFINED THRESHOLD

Soft Channel Capacity introduces a field to this alarm.

For a more detailed description of the alarm, see Base Station Alarms (70007999).

Counters

The following counters to Soft Channel Capacity Measurement are introduced:

109000 PEAK BUSY TCH PER BCSU

109001 AVE BUSY TCH PER BCSU

109002 AVE BUSY TCH PER BCSU DENOMINATOR

109003 TOTAL TCH BUSY TIME PER BCSU

Also the following counter is added to Traffic Measurement:

001216 TCH REQ REJ DUE TO LACK OF RES PER BCSU

When Soft Channel Capacity is active and extra TCHs have been created in a cell, it is

possible that a radio channel allocation attempt is rejected because of the lack of BCSU

capacity even if there are free radio TCHs in the cell. In this case, the existing Traffic

Measurement and Resource Availability Measurement counters are updated as if the

radio channel allocation attempt was rejected because of a lack of radio resources. The

following counters are an exception:
http://dn9813254.pdf/http://dn9813254.pdf/http://dn9813184.pdf/http://dn9813184.pdf/http://general_glossary.pdf/http://dn0491791.pdf/http://dn0491791.pdf/http://dn0491791.pdf/http://x%3Dd%3Do%3Dc/s-000005.pdfhttp://x%3Dd%3Do%3Dc/s-000005.pdfhttp://dn0491791.pdf/http://dn0491791.pdf/http://dn0491791.pdf/http://general_glossary.pdf/http://dn9813184.pdf/http://dn9813184.pdf/http://dn9813254.pdf/http://dn9813254.pdf/


19/19

DN03499862 19

Soft Channel Capacity in BSC User interface of Soft Channel Capacity

Id:0900d8058058fcdb

002026 TOTAL CHANNEL BUSY TIME

002044 FULL RATE radio CONGESTION TIME

002045 HALF RATE radio CONGESTION TIME

These counters do not show congestion time unless all the radio TCHs of the cell havebeen occupied.

For more information, see the following measurements:

1 Traffic Measurement

2 Resource Availability Measurement

109 Soft Channel Capacity Measurement
http://dn9813827.pdf/http://dn9813757.pdf/http://dn05207461.pdf/http://dn05207461.pdf/http://dn9813757.pdf/http://dn9813827.pdf/

soft channel

Documents