Half Rate in BSC

BSC3153
Nokia GSM/EDGE BSS, Rel. BSS13, BSC and

TCSM, Rel. S13, Product Documentation, v.1
Half Rate in BSC
DN9814086 # Nokia Siemens Networks 1 (80)

Issue 11-0 en
27/02/2008
Half Rate in BSC
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 which
the 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
DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,
DIRECT, INDIRECT, 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 respective owners,
and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2008. All rights reserved.
2 (80) # Nokia Siemens Networks DN9814086

Issue 11-0 en
27/02/2008
Contents
Contents
Contents 3
List of tables 4
List of figures 5
Summary of changes 7
1 Overview of Half Rate 9
2 Technical description of Half Rate 11

2.1 Capacity and channel resources 15
2.2 Requirements for Half Rate 16
3 Channel rate and speech codec control in handovers 19
4 Channel rate selection based on cell load 27
5 Half Rate and radio resource allocation 33

5.1 The A interface in radio resource allocation 45
5.2 The Abis interface in radio resource allocation 51
5.3 The Radio interface in radio resource allocation 52
6 TCH allocation schemes in Half Rate 55
7 User interface of Half Rate 79

Issue 11-0 en
27/02/2008
Half Rate in BSC
List of tables
Table 1. Conversion of RTSL types on the Abis O & M interface 12

Table 2. Software requirements 16
Table 3. Circuit modes supported by TCSM2 47
Table 4. Circuit modes supported by TCSM3i 48
Table 5. A interface circuit pools supported by the BSC 48
Table 6. Uplink DTX control 53

Issue 11-0 en
27/02/2008
List of figures
List of figures
Figure 1. Transmission example 17

Figure 2. Cell load based TCH allocation 28
Figure 3. Assignment, mobile terminated call 56
Figure 4. Assignment, mobile terminated call (continued) 57
Figure 5. Assignment, change of the A interface circuit pool 60
Figure 6. Internal handover, intra-cell 63
Figure 7. Internal handover, intra-cell (continued) 64
Figure 8. Internal handover, inter-cell (asynchronous) 66
Figure 9. Internal handover, inter-cell (asynchronous) (continued) 67
Figure 10. External handover, source BSS 70
Figure 11. External handover, target BSS 72
Figure 12. External handover, change of the A interface circuit pool 74

Issue 11-0 en
27/02/2008
Half Rate in BSC

Issue 11-0 en
27/02/2008
Summary of changes
Summary of changes
Changes between document issues are cumulative. Therefore, the latest

document issue contains all changes made to previous issues.
Changes made between issues 11-0 and 10-0
Section Fault recovery in chapter Technical description of Half Rate has

been updated because now also non-control channels can be
reconfigured in fault recovery situations.
Information on Nokia Flexi EDGE BTS has been added to table Software
requirements in chapter Technical description of Half Rate.
Information on Nokia PrimeSite BTSs and Nokia 2nd generation BTSs has
been removed.
Chapter Overview of Half Rate
The list of related topics has been modified and updated.
Chapter Technical description of Half Rate
Subsection Capacity and channel resources
Information referring to TRCU and SM2M has been deleted and

information referring to TCSM3i has been added.
Subsection Requirements for Half Rate
Figure Transmission example has been updated.
Information referring to TCSM2 and the explanation of the function of

Group Switches has been deleted.

Issue 11-0 en
27/02/2008
Half Rate in BSC
Chapter Channel rate and speech codec control in handovers
A reference to internal handover to external has been added.
Chapter Half Rate and radio resource allocation
More information on the channel allocation for mobile-terminating calls

(MTCs) has been added to TCH type requirements and to Restrictions
caused by FACCH call set-up.
Minor editorial changes throughout the document.
Subsection RXLev Min Access has been added to Chapter TCH allocation
schemes in Half Rate.
Half Rate data qualities have been modified due to HR data support.
Nokia licence control information has been added.

Issue 11-0 en
27/02/2008
Overview of Half Rate
1 Overview of Half Rate

With Half Rate (HR) coding it is possible to maximise the spectrum
efficiency. HR coding almost doubles the amount of radio resources,
compared with the use of full rate traffic channels (TCHs). Whenever HR is
mentioned in Half Rate in BSC, it applies to speech or signalling cases
only. HR coding for data is not supported.
Full rate (FR) speech and data is coded and transferred using 16 kbit/s
channels in the BSS. With the HR coding, 8 kbit/s transmission can be
used on the Abis interface. This is also possible on the Ater interface when
the BSS (BTS, BSC, transcoder) and mobile stations all support HR.
Each radio timeslot of the BTS TRX can be configured to be a FR, HR, or
dual rate (DR) TCH resource on the Abis interface. In the case of dual rate,
the BSC dynamically allocates an idle radio timeslot either for HR or FR
coding on a call basis.
It is possible to introduce HR coding to existing full rate GSM networks

gradually. The A interface supports different types of transcoders capable
of FR coding, HR coding, or both. The BSS is able to co-operate
simultaneously with both old phase 1 FR-only mobile stations and with
phase 2 mobile stations that support both FR and HR. HR can, therefore,
also be installed in the network without replacing the old transcoders with
new ones that support the HR coding.
Half Rate is an application software in the BSC.
Related topics in Half Rate in BSC
. Technical description of Half Rate

. Channel rate and speech codec control in handovers
. Channel rate selection based on cell load
. Half Rate and radio resource allocation

Issue 11-0 en
27/02/2008
Half Rate in BSC
. TCH allocation schemes in Half Rate

. User interface of Half Rate
Other related topics
.
Functional descriptions
. Radio network performance
.
Radio Channel Allocation
. Operability
.
Radio Network Configuration Management
. Radio Network Supervision in BSC
. Feature descriptions
. Radio network performance
. Dynamic Frequency and Channel Allocation
.
Enhanced Speech Codecs: AMR and EFR
. FACCH Call Set-up
.
Intelligent Underlay-Overlay
. Data
.
GPRS/EDGE in BSC
. Value added services
. Radio Resource Pre-emption and Queuing
. Product descriptions
. Product Description of Nokia BSC2i and BSCi High Capacity
Base Station Controller
. Product Description of Nokia BSC3i High Capacity Base
Station Controller
. Test and activate
.
Radio network performance
. Activating and Testing BSS6115: Half Rate
.
Operate and maintain
. BSC Statistics Administration
. Reference
. Alarms
. Base Station Alarms (7000–7999)
.
Parameters
. BSS Radio Network Parameter Dictionary

Issue 11-0 en
27/02/2008
Technical description of Half Rate
2 Technical description of Half Rate

Half Rate and radio resource allocation
Introduction of Half Rate (HR) to a network has significant effects on the

TCH allocation algorithm of the BSC. With the most optimised allocation of
traffic channels, the BSC must be able to ensure the penetration of mobile
stations which do or do not support HR. The BSC must also be able to co-
operate with the other network elements having different kinds of
capabilities in supporting HR.
For more information on radio resource allocation and channel rate, see
.
Overview of Half Rate
. Channel rate and speech codec control in handovers
.
Channel rate selection based on cell load
. Half Rate and radio resource allocation
.
Activating and Testing BSS6115: Half Rate under Test and activate/
Radio network performance in the PDF view
. Channel rate for AMR calls in Enhanced Speech Codecs: AMR and
EFR under Feature descriptions/Radio network performance in the
PDF view
.
Radio Channel Allocation under Functional descriptions/Radio
network performance in the PDF view
.
Radio Resource Pre-emption and Queuing under Feature
descriptions/Value added services in the PDF view
.
Dynamic Frequency and Channel Allocation under Feature
descriptions/Radio network performance in the PDF view

Issue 11-0 en
27/02/2008
Half Rate in BSC
Effects on the Abis O & M interface
A logical radio timeslot (RTSL) type dual rate (DR) TCH is introduced on
the Abis O & M interface. The BSC converts RTSL TCH types of the BSC
database for the Abis O & M interface configuration messages according
to table Conversion of RTSL types on the Abis O & M interface.
Table 1. Conversion of RTSL types on the Abis O & M interface
BSC database Abis O&M BTS

TCHF TCHF TCHF
TCHH TCHD TCHD
TCHD TCHD TCHD
If a TRX has one or more DR TCH RTSLs, all the RTSLs of the TRX are
handled as DR TCH RTSLs in the BTS.
In the TRX reset and restart procedures, the BTS checks that the logical
channel configuration given by the BSC in the TRX configuration message
matches the actual hardware/software configuration of the BTS. If the
logical configuration of a TRX contains HR TCH or DR TCH RTSLs and
the TRX hardware or BTS software does not support HR, the BTS
generates a fatal TRX-wide alarm.
When a TRX test using RTSL(s) configured as a HR TCH or a DR TCH is

run, the BTS configures the RTSL dynamically as a full rate (FR) TCH. The
FR path is tested and after the test the BTS returns the original channel
configuration of the RTSL into use.
Effects on the Q3 interface
Two values (HR TCH and DR TCH) for the channel type parameter of the
radio channel object are introduced on the Q3 interface.
A TRX-specific parameter is needed to indicate whether the TRX supports

HR or not.
Radio network supervision
The radio network supervision reports on the network capacity problems

and certain types of repeated or continuous errors and disturbances in
radio channel transactions on the BTS level. The success of HR and FR
TCH transactions is monitored by both channel and BTS-specific
supervisions. The channel-specific supervisions are:

Issue 11-0 en
27/02/2008
. mean duration of calls on a specific channel
The measurement reveals possible hanging calls and sudden call

drops immediately after call establishment.
.
channel failure rate
The measurement reveals abnormally ended transactions on a
specific channel.
. interference estimation of a TCH RTSL
The measurement is based on the interference-level information
which is received per TCH subchannel from the BTS.
The traffic channel congestion level is measured per BTS. HR and FR

traffic portions in congestion can be observed separately.
For more information, see Radio Network Supervision in BSC under

Functional descriptions/Operability in the PDF view.
Supervision of available traffic channels
The system supervises the ratio of available traffic channels to the

configured traffic channels on the BTS, in case the ratio falls below the
given threshold. The availability of HR TCHs and FR TCHs per sector
must be supervised separately, and an alarm is triggered if the availability
of either HR TCHs or FR TCHs falls below the user-defined limit.
If the number of HR TCHs is below the given threshold, the alarm 7717
WORKING HALF RATE TCH RATIO BELOW THRESHOLD is triggered. If
the number of FR TCHs is below the given threshold, the 7711 WORKING
FULL RATE TCH RATIO BELOW THRESHOLD alarm is triggered. The
system cancels these alarms when the given threshold is exceeded.
You can define the supervision alarm limits with the Base Station
Controller Parameter Handling in BSC MML commands (command group
EE). The alarm limit for full rate TCH availability (ALFRT)
parameter defines the lower limit value for the available FR TCHs. The
alarm limit for half rate TCH availability (ALHRT) parameter
determines the corresponding threshold value for HR TCHs.
For more information on alarms, see Base Station Alarms (7000–7999)

under Reference/Alarms in the PDF view.

Issue 11-0 en
27/02/2008
Half Rate in BSC
Fault recovery
During a recovery situation when HR is used, each RTSL holding control

channels is included in the number of TCHs as two TCH resources. In this
way, it is possible to control the number of real TCHs in a recovery
situation.
The radio network recovery system handles the HR TCH resources (HR
TCH and DR TCH) in the same way as the FR TCH resources. Therefore,
if a TRX becomes faulty, the system must take into account the TRX's
capability to support HR TCHs. The system reads this from the TRX half
rate support (HRS) parameter of the TRX object.
Depending on the BTS configuration in a recovery situation:
. all timeslots of the TRX are reconfigured or
. the user defined traffic timeslots of the TRX are restored.
The RNW recovery reconfigures all timeslots of the TRX in TRX

reconfiguration, if Soft Channel Capacity and AMR are used and all
unlocked TRXs of the BTS have been defined to support HR. The RNW
recovery can restore the operator-defined original traffic channel
configuration of the TRX in TRX reconfiguration, if Soft Channel Capacity
is not in use, or AMR HR is not in use in the BTS or not all unlocked TRXs
of the BTS have been defined to support HR.
The 7727 TRAFFIC CHANNEL NUMBER DECREASED alarm is

generated by the radio network recovery system to indicate that because
of recovery actions some HR TCHs are missing. Alternatively, the TCHs
are changed to NOTUSED channels, because TCH resources have run
out. The channel types changed by the system start from CH7 downwards.
The BSC cancels the alarm automatically when the original TCH count is
returned or the user modifies the channel configuration of the TRX.
In all cases, the recovery system tries to find such a new TRX that the HR
TCHs would not be missed.
The HR TCH disappearance can be avoided by configuring the BTSs in

such a way that there is no combination of TRXs that support HR and
TRXs that do not support HR in the same cell.
For more information on alarms and parameters, see Base Station Alarms
(7000–7999) under Reference/Alarms and BSS Radio Network Parameter
Dictionary under Reference/Parameters in the PDF view.

Issue 11-0 en
27/02/2008
Errors detected by call control in the BSC
If the BSC detects channel type or state mismatches concerning HR TCHs

or DR TCHs, the radio network recovery system runs recovery actions for
the entire RTSL. The same applies to recovery requests if the BTS has
rejected the HR channel allocation request too many times during a
supervision period.
BSS radio network traffic administration
The aim of the traffic administration is to provide relevant information on

the traffic capabilities of the network. Especially in this case you must have
the means to ascertain the functioning of HR. Furthermore, an aid is given
for dimensioning the network, for example, for ascertaining the blocking of
FR BTSs to upgrade them to HR BTSs.
Performance management
Performance management provides information on the success of HR

calls and their share of the traffic. It is possible to compare the amount and
success of HR and FR traffic to find out the capacity of the network as well
as the effects that the implementation of HR has on the penetration of
calls.
For more information, see BSC Statistics Administration under Operate

and maintain in the PDF view.
Allocation of an RTSL for BSS radio network testing
Radio Network tests are run for FR paths only, which means that if the
RTSL is configured as a HR TCH or a DR TCH, the entire RTSL (both HR
TCHs) has to be allocated for the test.
2.1 Capacity and channel resources

Together with HR-related routing and switching and the second generation
transcoder submultiplexer (TCSM2) it is possible to configure 210 HR
channels (seven HR transcoder PCMs connected to one transcoder unit).
TCSM3i and TCSM3i for combined BSC3i/TCSM3i installation allow the
configuration of 120 HR channels (four HR transcoder PCMs connected to
one transcoder unit).
In a FR configuration, the maximum number of FR channels is 116 (four

FR transcoder PCMs connected to one transcoder unit).

Issue 11-0 en
27/02/2008
Half Rate in BSC
It is also possible to create mixed configurations with the accuracy of one

A interface PCM. An example is presented in figure 1 Transmission
example. One FR, one dual rate (DR) and three HR A interface PCMs are
carried over one Ater PCM link, 150 traffic channels in total.
For more information on capacity and channel resources, see the following
documents under Product descriptions in the PDF view:
. Product Description of Nokia BSC2i and BSCi High Capacity Base

Station Controller
. Product Description of Nokia BSC3i High Capacity Base Station
Controller
For more information on signalling capacity, see Radio Network

Configuration Management under Functional descriptions/Operability in
the PDF view.
2.2 Requirements for Half Rate

Software requirements
Table 2. Software requirements
Network element Software requirements

BTS Nokia Talk-family BTS SW release D2.1 or later
Any release of Nokia MetroSite BTS, Nokia InSite
BTS, or Nokia UltraSite EDGE BTS or Nokia Flexi
EDGE BTS
Nokia Flexi EDGE BTS EP1.0
MSC M7 or later
Circuit pool support is required by the MSC.
NetAct OSS4.1 or later
BSC S5 or later
Hardware requirements
HR can be employed only when the BSC is equipped with the bit group
switch (GSWB). In the GSWB, which can handle 8 kbit/s sub-timeslots, all
connections between outgoing and incoming bits can be made with one-bit
accuracy.

Issue 11-0 en
27/02/2008
Transmission management requirements
Figure Transmission example presents an example how the transcoder

PCMs are configured on the A interface.
Abis Ater A
Interface Interface Interface
PCM 1
BTS BSC TCSM HR MSC
ET PCM 2
GSWB HR GSW
PCM 3
HR
PCM 4
BTS ET HR
PCM 5
HR
PCM 6
HR
PCM 7
HR
BTS
PCM 1
TCSM HR
PCM 2
FR
PCM 3
ET DR
PCM 4
HR
PCM 5
HR
PCM 1
TCSM HR
PCM 2
HR
ET PCM 3
HR
PCM 4
HR
ET_PCM transcoder PCM
Figure 1. Transmission example
The transcoder PCMs of the first TCSM unit are all in HR mode. The
second TCSM unit includes all three types of transcoder PCMs: HR, FR,
and DR. The third unit is an HR transcoder.
From the MSC point of view, all PCMs are normal PCMs which consist of
64 kbit/s timeslots.

Issue 11-0 en
27/02/2008
Half Rate in BSC

Issue 11-0 en
27/02/2008
Channel rate and speech codec control in handovers
3 Channel rate and speech codec control

in handovers
The traffic channel rate and the speech codec that are used in a call can
be changed when a new channel is allocated for the call during a
handover. The change can be made if only a preferred channel rate
without any rate change prohibitions is given in the handover request. The
used speech codec can also be changed within a TCH rate, if a handover
is performed between BTSs with different speech encoding capabilities
and several speech codec alternatives have been given for the rate in the
request. In speech call cases this may require that the A interface circuit
type is changed to another one if the circuit used on the old channel does
not support the new channel rate.
There can be a need to deny channel rate and speech codec changes
during the handovers for speech calls to avoid sudden tone changes
during a call. Therefore, if the channel rate selection is not restricted by the
system, you can set extra constraints for the channel rate and speech
codec changes. The changes can be restricted both on the BSS-level (for
inter-cell and intra-cell handovers) and on the BTS-level (for intra-cell
handovers).
When the speech codec is changed during an internal handover, there is a

short break in the downlink speech path because, in this case, a
unidirectional connection cannot be established. However, the BSC can
change these handovers to external handovers to enable a unidirectional
connection and in this way avoid downlink muting. For more information,
see TCH rate in internal handover in Radio Channel Allocation under
Functional descriptions/Radio network performance in the PDF view.
Parameters
In handovers for speech calls, the parameters TCH in handover (HRI)

and TCH rate intra—cell handover (TRIH)control both channel rate
and speech codec selection. In the case of signalling, a half rate (HR) TCH
is allocated primarily unless a full rate (FR) TCH is particularly requested.

Issue 11-0 en
27/02/2008
Half Rate in BSC
. TCH in handover (HRI)
This BSC-specific parameter controls the TCH rate determination

and speech codec selection in TCH allocation during handovers.
The parameter is applied to each handover for which the type of the
source TCH and the source speech version is known, that is, at least
to all BSC-controlled handovers. It can also be applied to the MSC-
controlled, external handovers when the channel type or the speech
version that the call is using in the cell of the source BSS is known in
the target BSS. By default, the call-maintaining type of TCH is
allocated and the actual speech codec used by the call is kept up in
the handover.
The parameter can have the following values:

. 1
In the handover, the best candidate cell in which the same type
of TCH and the same speech version can be used as in the
source cell is selected for a target cell.
If such a cell does not exist, the other speech version is used
or finally the other type of TCH is allocated from the best
possible cell.
This means that in the handover candidate cell list, the cell in
which it is possible to use the same type of TCH, HR or FR that
is used by the call in the source cell of the handover has the
highest priority.
In case one or more cells of that type exist, the best cell in
which the same speech version is used for the call as in the
source cell of the handover is selected. If the same speech
version is not used in any of these cells, the TCH is allocated
from the best of these cells. In the initial radio resource
request, the MSC determines the order of preference,
according to which the speech version representing the type of
the TCH to be allocated is selected.
If all the handover candidate cells are such that it is not
possible even to allocate the TCH of the type which is used for
the call in the source cell, the other type of TCH is allocated
from the best possible candidate cell. In the initial radio
resource request, the MSC determines the order of preference
according to which the speech version representing the type of
the TCH to be allocated is selected.
The actual TCH resource situation, that is, the traffic load of
the cells, also affects the type of the target TCH when the call
is maintained in a FR TCH in the source cell. When the FR
TCH is searched for among the candidate cells, those cells in
which the traffic load requires allocation of the HR TCH, are

Issue 11-0 en
27/02/2008
ignored. The FR TCH is allocated from the best cell in which

the traffic load situation makes it possible. If all the candidate
cells are overloaded, an HR TCH is allocated from the best of
the candidate cells.
When the type of the source TCH is HR and, therefore, an HR
TCH is attempted to be allocated primarily, the actual traffic
load of the candidate cells does not affect the procedure. The
HR TCH is allocated from the best of the candidate cells
regardless of the amount of possible available FR TCH
resources in the cell.
External handover: The current Channel and Speech Version
(used) elements are used, when present, as the primary
decisive factor when allocating a TCH for a speech
connection. For a data call, FR TCH is the only alternative. If
the Current Channel and Speech Version (used) elements are
not present or they are not in line with the received Channel
Type element, the decisive factor is the requirements in the
Channel Type element.
Internal handover: The same applies with the chosen channel
and speech codec.
. 2
During the speech connection the call serving type of the TCH
is allocated primarily and the original speech version is used.
In the case of data connection, the TCH is allocated from the
best cell in the candidate list.
For the speech calls, the procedure is similar to that of value 1.
For data calls, see the description of value 5.
External handover: Current Channel and Speech Version
connection, if the received Channel Type element supports
Current Channel and Speech Version (used). If the Current
Channel and Speech Version (used) elements are not present
or they are not in line with the received Channel Type element,
the decisive factor is the requirements in the Channel Type
element.
Internal handover: The same applies with the chosen channel
and speech codec.
.
3
Channel rate and speech version changes are denied totally.
This means that an attempt is made to find a cell in the
handover candidate list in which it is possible to use the same
type of TCH (HR or FR), which is used by the call in the source
cell of the handover.

Issue 11-0 en
27/02/2008
Half Rate in BSC
The call-serving type of channel is the only alternative in the

TCH allocation. It is not allowed to change the actual speech
version used by the call either.
The traffic load of the candidate cells is not of any importance
in this case. The only requirement is that there is a cell in
which the TCH can be allocated so that the speech version is
not changed. The best of those handover candidates is
selected regardless of its traffic load.
(used) elements are used, when present, as the only decisive
factor when allocating a TCH for a speech connection. For a
data call, FR TCH is the only alternative. If the Current
Channel and Speech Version (used) elements are not present
or they are not in line with the received Channel Type element,
the decisive factor is the requirements in the Channel Type
element.
Internal handover: The same applies with chosen channel and
speech codec.
.
4
The TCH is allocated from the best handover candidate cell in
which the call can use the type of TCH and speech version
that the MSC has set to be the preferred ones in the initial
radio resource request. The speech version can be changed in
order of preference if the allocation of the TCH requires it.
This means that a cell which uses the type of TCH (HR or FR)
that the MSC has originally set to be the preferred one, is
primarily looked for from the handover candidate cell list. The
TCH type and the speech version which the call is using in the
source cell of the handover is ignored.
If such cells exist, the best of them is selected in such a way
that the speech version which best meets the preference order
of the codecs determined by the MSC is used for the call.
If all the handover candidate cells are such that even the TCH
of the type set preferred by the MSC cannot be allocated from
any of them, the other type of TCH is allocated from the best
possible cell. The speech version corresponding to the type of
the TCH is selected in the preference order which the MSC
has determined in the initial radio resource request.
the cells, affects the type of the target TCH when the MSC has
initially preferred the FR TCH. The FR TCH is searched from
the candidate cells. Those cells in which the traffic load
requires allocation of an HR TCH are ignored and the FR TCH
is allocated from the best cell in which the traffic load situation
makes it possible. If all the candidate cells are overloaded, an
HR TCH is allocated from the best of the candidate cells.

Issue 11-0 en
27/02/2008
When the MSC has preferred the HR TCH and, therefore, the
HR TCH is attempted to be allocated primarily, the actual traffic
load of the candidate cells does not affect the procedure. The
HR TCH is allocated from the best of the candidate cells
regardless of the amount of possible available FR TCH
resources in the cell.
External and internal handovers: The requirements in the
Channel Type element are the primary decisive factor when
allocating a TCH for a speech connection. Current Channel
and Speech Version (used) elements are not used. For a data
connection, FR TCH is the only alternative.
. 5
The TCH must be allocated from the best BTS of the handover
candidate list, regardless of the speech codec version actually
used.
This means that the TCH is allocated from the best handover
candidate cell that has the available TCH resources.
An attempt is made in the cell to allocate the same type of TCH
(HR or FR) which is used for the call in the source cell of the
handover. If this is possible, it is also checked whether the
same speech version can be used for the call as in the source
cell of the handover. If the speech version cannot be used, the
speech version which represents the type of the TCH to be
allocated is selected in the preference order which the MSC
has determined in the initial radio resource request.
When the TCH of the type which is used for the call in the
source cell of the handover cannot be allocated, the other type
of TCH is allocated. The speech version corresponding to the
type of the TCH is selected in the preference order which the
MSC has determined in the initial radio resource request.
the best cell, also affects the type of the target TCH when the
call is maintained in FR TCH in the source cell. The FR TCH is
allocated when the cell is not overloaded. If the cell is
overloaded, an HR TCH is allocated.
When the type of the source TCH is HR and, therefore, the HR
TCH is attempted to be allocated primarily from the best cell,
the actual traffic load of the cell does not have an effect at all.
The HR TCH is allocated if one is available.
connection. For a data call, FR TCH is the only alternative. If
Current Channel and Speech Version (used) elements are not

Issue 11-0 en
27/02/2008
Half Rate in BSC
present or they are not in line with the received Channel Type
element or they prevent the TCH allocation from the best
candidate, the decisive factor is the requirements in the
Channel Type element.
Internal handover: The same applies with chosen channel and
speech codec.
The parameter can be handled with the EEM and EEO commands.
.
TCH rate intra—cell handover (TRIH)
Though the BSS-level channel rate control is valid for all the TCH
handovers, it can be readjusted with this BTS-specific parameter for
the internal intra-cell handovers in each BTS. The possible
parameterisation alternatives correspond to values 1-4 of the
parameter TCH in handover (HRI).
An additional value 0 corresponds to the case where no extra
constraints for the intra-cell handovers are given and the TCH in
handover (HRI) parameter is also applied for the intra-cell
handovers in the particular BTS.
If the BSS-level parameter has the value of 5, a TCH with the same
characteristics as the call-serving TCH is preferred primarily from
another TRX than the one maintaining the call in the BTS. If
possible, the call-serving type of TCH and the used speech version
are preferred.
The parameter can be handled with the EQM and EQO commands.
Note that if the MSC has denied any channel rate changes during
handovers in the initial resource request, this cannot be overwritten with
either of the two parameters.
These parameters control the channel rate and speech codec in internal
and external handovers if the TCH is allocated for speech. For a data
connection, FR TCH is the only alternative. If signalling is indicated in the
resource request, the preferred channel rate type of channel is allocated
primarily for internal handovers. Note that the type of the allocated TCH
fulfils all the conditions determined primarily by the Channel Type
information element (IE) of the initial A interface message and the type of
the A interface circuit. The BSC parameters give the extra constraints for
the channel selection. Especially if the channel rate changes are denied
after the first TCH assignment, it is not possible to evade the prohibition by
giving a suitable value to the parameters. However, in emergency calls the
channel rate is always determined merely on the basis of the Channel
Type and A interface circuit type.

Issue 11-0 en
27/02/2008
The BSC is able to send in the A interface HANDOVER REQUIRED

message and receive two optional information elements, Current Channel
and Speech Version in the HANDOVER REQUEST message. Whenever
this information is available in the target BSC of the handover, that is,
when the MSC is able to transfer it, the TCH type and speech version
control, described above, is also applied for the external handovers.

Issue 11-0 en
27/02/2008
Half Rate in BSC

Issue 11-0 en
27/02/2008
4 Channel rate selection based on cell load

Channel rate selection based on cell load offers the possibility to
determine the distribution between full rate (FR) TCH and half rate (HR)
TCHs according to the cell load in TCH allocation for requests that can
accept a TCH of any channel rate.
TCH allocation control according to cell load is possible when
. the MSC does not determine the channel rate uniquely but gives
only the preferred rate, that is, HR or FR
. the BTS traffic channel configuration, the resource situation in the
cell, and the parameters the operator has possibly set do not restrict
the TCH allocation
To apply cell load in TCH rate selection, the A interface circuit must
support both TCH rates. If there is no support for both TCH rates, the A
interface circuit must be changed to one from another circuit pool before a
TCH of the selected rate can be allocated.
If traffic channel allocation based on cell load is applied, FR TCHs are

allocated until the number of free FR resources is reduced below a specific
lower limit. After this the HR resources are allocated. When the number of
FR TCH resources increases above a specific upper limit, FR TCHs are
allocated again. This is illustrated with Figure Cell load based TCH
allocation.

Issue 11-0 en
27/02/2008
Half Rate in BSC
Free FR TCHs
Upper limit for

free FR TCHs
Lower limit for

free FR TCHs
Allocation of Allocation of Allocation of Time

FR TCHs HR TCHs FR TCHs
Figure 2. Cell load based TCH allocation
HR controls the TCH allocation for dual rate (DR) requests, that is, when
both channel rates are acceptable. For requests that determine a single
TCH rate a channel of the respective type is allocated regardless of the
traffic channel load in the BTS.
HR is applicable for speech calls and signalling with some exceptions. For
data calls, FR TCH is the only alternative.
. In a speech call, if HR is set to be the preferred rate, the

corresponding free permanent TCH resource is allocated primarily,
regardless of whether the cell-load-based TCH allocation has been
activated or not.
.
With signalling, a HR TCH is always allocated if it is set to be the
primary requirement although the cell load does not currently require
it.

Issue 11-0 en
27/02/2008
If HR is activated and the lower limit is set to be greater than zero, at least
the last free DR RTSL is split into two HR TCHs in TCH allocation. This
makes it possible to determine a positive margin for the HR TCH allocation
in cells equipped with only one TRX without making the lower limit
unnecessarily high.
If the value of the lower limit equals zero, HR TCH resource can be
allocated for a speech call only if the MSC strictly requires it, regardless of
whether the target cell has permanent HR resources or not.
Parameters
HR is controlled by two parameters that determine the values of the upper

and the lower limit for FR TCH load in a cell. The limit parameters are given
as relative amounts of free FR TCH resources in proportion to working FR
TCH resources. The parameters can be defined on both the BSC level and
the SEG level.
.
lower limit for FR TCH resources
. BSC level: lower limit for FR TCH resources (HRL)
.
SEG level: lower limit for FR TCH resources (FRL)
The parameter gives the lower limit percentage value of the relative
amount of free FR TCH resources. The limit includes permanent and
DR types together. If a FR TCH was chosen the previous time the
rate determination dependent on cell load was applied, the relative
amount of free FR TCH resources must be above this limit for a FR
TCH to be allocated. If the relative amount of free FR TCH resources
is below the lower limit, a HR TCH has to be allocated.
. upper limit for FR TCH resources
.
BSC level: upper limit for FR TCH resources (HRU)
. SEG level: upper limit for FR TCH resources (FRU)
The parameter gives the upper limit percentage value of the relative
amount of free FR TCH resources. If a HR TCH was chosen the
previous time the rate determination dependent on cell load was
applied, the relative amount of free FR TCH resources must be
below this limit for a HR TCH to be allocated. If the relative amount of
free FR TCH resources is above the upper limit, a FR TCH has to be
allocated.
HR is enabled in specific cells when either of the two parameter pairs is

effective. However, when the SEG-level parameters are effective, the
BSC-level parameters are not significant in TCH allocation.
If the upper limit is set smaller than the lower limit the effect of the
parameters is deactivated.

Issue 11-0 en
27/02/2008
Half Rate in BSC
The SEG-level parameters, if active, are followed in a particular cell. If no

individual channel rate control rules have been specified in the cell, the
common BSC-level parameters are applied. The default values of the
parameters have been set so that the cell load is not initially used.
HR is disabled in specific cells when it is disabled both on the BSS level

and cell level.
These parameters are handled with the EEM, EEO, EQM, and EQO
commands.
Channel rate control in handovers
In addition to the call set-up and external handovers, the two TCH
allocation thresholds can also be applied in internal handovers, but only if
the handover request does not contain any limitations concerning the
channel rate changes, or if they are not defined on the BSS level.
The parameters that control the channel rate, TCH in handover (HRI)
and TCH rate intra-cell handover (TRIH), cause the following
restrictions for applying the cell load threshold parameters:
.
If HR is the preferred channel rate of the resource request, the
corresponding available permanent HR TCH resource is allocated
primarily, regardless of whether the cell-load-based TCH allocation
has been activated or not.
. An HR TCH is always allocated if the cell load requires it, regardless
of possible existing available permanent FR resources or the
preferred FR TCH requirement of the TCH resource request.
.
When the TCH is allocated for internal handover and the channel
rate changes are denied totally (either by the MSC or by the BSC),
neither of them are allowed because of the cell-load-dependent
resource conditions.
.
When the TCH is allocated for internal handovers and the call-
maintaining type of TCH is determined to be the preferred
alternative, a HR channel is allocated for a HR call from the best
possible cell, regardless of cell load.
. When the TCH is allocated for internal handover: if the rate preferred
by the MSC is defined as the primary rate to be used, and if the MSC
has a preferred HR TCH, a HR channel is allocated from the best
possible cell, regardless of the traffic load in the cell.
The other values of the parameters controlling channel rate make it

possible to take into account the cell load thresholds in TCH allocation for
internal handovers because of the flexible limitations they determine.

Issue 11-0 en
27/02/2008
GPRS/EDGE
If GPRS/EDGE is in use in a BTS in which a TCH is being allocated, the

TCH resources of the BTS are divided between two territories for the
circuit-switched (CS) traffic and the packet-switched (PS) GPRS/EDGE
traffic. In this case, the actual TCH load thresholds used in TCH rate
selection are calculated by applying the threshold parameters to the
resource amounts of the CS territory. With the CS TCH allocation
calculation (CTC) parameter, you can define how the RTSLs used for
PS are seen when calculating resources for CS allocation.
For more information, see GPRS/EDGE in BSC under Feature

descriptions/Data in the PDF view.

Issue 11-0 en
27/02/2008
Half Rate in BSC

Issue 11-0 en
27/02/2008
5 Half Rate and radio resource allocation

TCH type requirements
Initially the mobile station (MS) informs the network of its transcoding
capabilities. It sends this information in two phases of the call set-up.
When the MS requires a channel for starting the connection establishment

to the network, it sends a specific establishment cause in the message
which indicates the reason for the call attempt to the network. Phase 2
MSs also inform of the required type of TCH, that is, whether the half rate
(HR) TCH is sufficient or whether the full rate (FR) TCH is the only
alternative. This is possible only in mobile-originating calls (MOC) when
the new establishment causes are supported by the network (NECI is set
ON in the BTS). In mobile-terminating calls (MTC) the type of the channel
needed is indicated to the MS in the paging request. The BSC uses the
establishment cause information when it decides on the first dedicated
control channel (DCCH) to be allocated for the call. A FR TCH is always
allocated for an MTC because the HR capabilities of the MS cannot be
solved for the call in this phase of the fast associated control channel
(FACCH) call set-up. The BSC describes the allocated DCCH to the MSC
in the message containing the initial layer 3 information.
When the connection to the network has been established, the MS sends
information of its HR capabilities on the main DCCH. The information is
transferred in the Bearer Capability (BC) information element (IE) of the
set-up or call confirmation messages to the MSC, depending on whether
the call is a MOC or a MTC. Two alternatives are possible:
. the MS supports only FR transcoding (phase 1 MS)

. the MS is capable of both FR and HR transcoding
In this case, the MS also states which TCH rate is preferred, either
FR or HR.

Issue 11-0 en
27/02/2008
Half Rate in BSC
The BC IE sometimes also contains information on the speech codec

versions the MS supports. The MS gives all speech codec versions in the
order of preference, which further determines the requirement of the
channel rate preference.
The BSC receives from the MSC the TCH channel type and rate
requirement in the Channel Type IE of the ASSIGNMENT REQUEST
message. In the external handover case the Channel Type IE is also
received in the HANDOVER REQUEST message. The MSC requests a
strictly FR or HR traffic channel. The former choice is the only possibility
when the MS supports FR transcoding only. If the MS supports HR, the
MSC lets the BSC make the final decision on the TCH type. The MSC then
gives only the preference for the channel rate, either FR or HR.
In a speech call, the Channel Type IE also contains the Permitted Speech
Version Indication. One or more speech versions can be represented. In
the latter case codecs are given in the order of preference, which may also
determine the requirement of the channel rate preference. The decision of
the channel rate in TCH allocation made by the BSC depends on which
speech codec versions of a specific channel rate the BTS supports.
The HANDOVER REQUEST message optionally includes information on

the source channel (Current Channel IE). The mode of the channel
(speech or data call information) and the channel rate and type (stand-
alone dedicated control channel (SDCCH), FR TCH or HR TCH) are
represented in the IE.
In a speech call, the HANDOVER REQUEST message also optionally

contains the speech version information the MS is using on the source
TCH. The codec information also implies the source channel rate and type.
Both the BC IE and the Channel Type IE can be used when the BSC
makes a decision on the rate and on the type of the target channel in
allocation of the TCH for the call to be handed over.
As an extra requirement, the MSC also determines whether the channel

rate changes are allowed or not after the first channel allocation. If the
MSC has not uniquely determined the TCH type, the TCH rate changes
take place during the BSS-internal handovers. The type of the call-
maintaining TCH brings a new factor for TCH allocation at the time of
internal handovers: whether the BSC must always allocate a call-
maintaining type of TCH for speech quality reasons or allow the channel
rate to change, for example, because of to the TCH resource situation of
the adjacent cells. The decision procedure is simpler if the MSC denies
channel rate changes.

Issue 11-0 en
27/02/2008
In the subsequent assignment case as well as in initial assignment of the

FACCH call set-up, the situation is perhaps more complicated because the
call is already maintained in a certain type of TCH, HR or FR. No problems
occur if the MS supports only FR. However, if the MS supports both
channel rates, problems may occur in those exceptional cases when the
MSC strictly requires either an HR TCH or an FR TCH.
The BTS does not allow reconfiguration of an active channel from HR to

FR or vice versa by using the Mode Modify procedure. If the channel rate
requirement of the ASSIGNMENT REQUEST is totally contradictory with
the type of the call-maintaining TCH, the call modification procedure is
unsuccessful. Especially alternating speech connection cases where the
channel rate changes are required cause the BSC to be unable to handle
the connection portion. However, this does not deviate from the GSM
recommendations which state that FR is used from the start of the call if
one of the connection portions requires FR.
The BSC changes the initial preference of the TCH rate stated in the
Channel Type IE because of resource reasons of a specific cell, that is, the
actual TCH configuration, the traffic load of a cell or constraints determined
for the TCH channel rate at the time of internal handovers.
Circuit configuration on the A interface
The transcoders are located at the MSC site. Therefore, when the MSC
allocates the A interface circuit, it simultaneously determines the
transcoder to be used. If there are transcoders of different transcoding
capabilities, the A interface circuit allocation becomes dependent on the
channel rate of the required traffic channel resource.
If Reversed Hunting is active, the A interface circuit is allocated by the

BSC instead of the MSC.
A circuit pool concept has been introduced in GSM recommendations for

handling transcoders of different types (for more information, see 3GPP
TS 48.008: MSC-BSS Interface, Layer 3 Specification). Each circuit pool
consists of a group of A interface circuits which all have the same
transcoding capabilities.
There are 50 predefined speech-codec-specific circuit pools. The DX 200

BSC supports the following 13:
.
FR pool of circuits supporting FR speech version 1 and FR data (12,
6, 3.6 kbit/s)
.
HR pool of circuits supporting HR speech version 1 (supported only
by TCSM2)

Issue 11-0 en
27/02/2008
Half Rate in BSC
. dual rate (DR) pool of circuits supporting FR speech version 1 and

HR version 1 and FR data (12, 6, 3.6 kbit/s)
. FR pool of circuits supporting FR speech versions 1 and 2 and FR
data (12, 6, 3.6 kbit/s)
. DR pool of circuits supporting FR speech versions 1 and 2 and HR
version 1 and FR data (12, 6, 3.6 kbit/s)
version 1 and FR data (14.5, 12, 6, 3.6 kbit/s)
version 1 and FR data (12, 6, 3.6 kbit/s) and multislot data (max 2 x
12 or 6 kbit/s)
version 1 and FR data (12, 6, 3.6 kbit/s) and multislot data (max 4 x
12 or 6 kbit/s)
.
DR pool of circuits supporting FR speech versions 1 and 2 and HR
version 1 and FR data (14.5, 12, 6, 3.6 kbit/s) and multislot data
(max 2 x 14.5 or 12 or 6 kbit/s)
version 1 and FR data (14.5, 12, 6, 3.6 kbit/s) and multislot data
(max 4 x 14.5 or 12 or 6 kbit/s)
. DR pool of circuits supporting FR speech version 3 and HR version 3
. DR pool of circuits supporting FR speech versions 1, 2 and 3 and
HR versions 1 and 3 and FR data (14.5, 12, 6, 3.6 kbit/s) (supported
by TCSM3i and TCSM3i for combined BSC3i/TCSM3i installation)
. DR pool of circuits supporting FR speech versions 1, 2 and 3 and
HR versions 1 and 3 and FR data (14.5, 12, 6, 3.6 kbit/s) and
multislot data (max 4 x 14.6 or 12 or 6 kbit/s) (supported by TCSM3i
and TCSM3i for combined BSC3i/TCSM3i installation)
Speech FR version 2 corresponds to the enhanced full rate (EFR) speech

codec. Speech FR version 3 and HR version 3 correspond to adaptive
multirate codec (AMR) FR and AMR HR codecs. EFR-supporting pools
are available only when the EFR option is used in the BSC. AMR-
supporting pools are available only when the AMR option is used in the
BSC.
For more information on AMR and EFR, see Enhanced Speech Codecs:
AMR and EFR under Feature descriptions/Radio network performance in
the PDF view.

Issue 11-0 en
27/02/2008
The A interface circuit must enable the BSC to allocate a radio resource of
the requested type. If the A interface circuit pool type and the TCH
resource request are totally contradictory, the BSC interrupts the on-going
transaction, assignment or external handover attempt, by sending the
proper failure message to the MSC.
Rather than the pool of the A interface circuit allocated by the MSC (or by
the BSC if Reversed Hunting is active), the actual A interface circuit pool
configuration determines primarily how the BSC selects the channel rate of
the TCH to be allocated. There must be a circuit pool that supports the
type of TCH that is going to be allocated according to the requirements,
including those related to the speech codec versions, received from the
MSC.
There is a specific fallback procedure for cases in which the circuit that the
MSC has allocated belongs to another type of pool than what is suitable for
the BSC. The fallback procedure makes it possible for the MSC to
reallocate the circuit from the correct pool. If Reversed Hunting is active
the circuit reallocation is done internally by the BSC and, therefore, the
MSC is not involved. For more information, see Radio Channel Allocation
under Functional descriptions/ Radio network performance in the PDF
view.
This example is valid only if Reversed Hunting is not active: the MSC
defines that a HR channel is preferred, but allocates the A interface circuit
from the FR pool. If an HR TCH is available in the BTS and a HR or a DR
circuit pool exists on the A interface, the BSC sends the MSC the
appropriate transaction failure message. The message contains the
specific cause and information on the pool from where the MSC has
allocated the circuit. The message also contains a recommendation of the
pool that is the most suitable for the BSC and from which the A interface
circuit should be allocated. The MSC then sends a new ASSIGNMENT
REQUEST or HANDOVER REQUEST message with new A interface
circuit information. This method enables the BSC to allocate the TCH radio
resources more efficiently because the initial allocation of the A interface
circuit does not necessarily set also the TCH resource type.
Channel type and A interface circuit pools
The BSC makes primary checks of the ASSIGNMENT REQUEST and the
HANDOVER REQUEST messages. The remaining checks are made
during the TCH allocation. The following assumptions and principles are
observed:

Issue 11-0 en
27/02/2008
Half Rate in BSC
. The speech version indications of the Channel Type IE must be

reasonable. This means that it must be possible to attach a specific
codec version to a specific channel rate, either FR or HR. Each
codec version that does not meet this requirement is removed from
the speech version indication list of the resource request.
.
The A interface circuit pools must support the speech version
indication of the resource request. Any codec version that does not
have transcoding support is removed from the resource request.
. FR channel rate must be allowed in channel rate requirements if a
data call is concerned.
. The A interface circuit must support FR coding for data if a data call
is concerned.
The total mismatches between the requested channel type (that is, the
permitted speech version indication) and the A interface circuit pools are
observed immediately when the ASSIGNMENT REQUEST or
HANDOVER REQUEST has been received. This observation is possible
only if the circuit identification code (CIC) is included in the request, that is,
the circuit has been allocated in the traditional way by the MSC (Reversed
Hunting is not active). The treatment of the partial contradictions depends
not only on the A interface circuit pool configuration, but also on the TCH
resource situation of the target cell.
In general, when the A interface circuit does not support the preferred TCH
channel rate requirement and the cell has the preferred type of TCHs
available, the BSC immediately tries to change the A interface circuit pool
to another pool if a suitable one exists. When the A interface circuit
supports only the preferred channel rate and the cell has configured the
same type of TCHs, the BSC first tries to allocate a TCH. If the attempt
fails, the BSC tries to change the A interface circuit to a pool which better
supports the TCH rate requirement.
The primary checking that the BSC makes for the ASSIGNMENT
REQUEST depend on the call phase in which the message has been
received from the A interface. In the initial ASSIGNMENT REQUEST, as
well as when the HANDOVER REQUEST is received from the A interface,
when speech or data is indicated in the Channel Type IE, the procedure
progresses in the following way:

Issue 11-0 en
27/02/2008
1. In a speech call, the BSC must first confirm that the speech
encoding algorithm versions are valid and correspond to the channel
rate requirements. If they are not, that is, there are no A interface
circuit pools supporting any of the speech versions expected in the
resource request, the transaction procedure (assignment or external
handover) is interrupted (that is, an ASSIGNMENT or HANDOVER
FAILURE message is going to be sent to the MSC) with the A
interface cause Requested Speech Version Unavailable.
When both of the two possible channel rates given are alternative
choices but only one of them has reasonable codec version
represented in the CHANNEL TYPE, the resource request message
is accepted but the channel rate requirement of the Channel Type IE
is revised.
2. For a data call, FR channel rate has to be allowed, otherwise the
channel cannot be allocated. If the channel rate and the radio
interface data rate are fully contradictory, the transaction is
interrupted with the A interface error cause Invalid Message
Contents. This can happen, for example, if a transparent service of
9.6 kbit/s data rate is required but the channel rate of the TCH
requested to be allocated is HR. If the channel rate and the radio
interface data rate are in line but the only allowed channel rate is HR,
the transaction is interrupted with A interface error cause Requested
Transcoding/Rate Adaption Unavailable.
3. This statement is valid only if Reversed Hunting is not active. When
the pool of the A interface circuit implied by the CIC represents an
existing pool, but it is totally contradictory with the permitted speech
version indication of the resource request, the transaction is
interrupted with the A interface cause value Circuit Pool Mismatch.
This is the case when, for example, an HR TCH is requested but the
pool type is FR.
4. When a resource is requested for a data call but there is no suitable
A interface circuit pool which supports the data rate requirements,
the transaction is interrupted with cause Requested Transcoding/
Rate Adaption Unavailable.
a resource is requested for a data call and the data rate requirement
does not match with the A interface pool implied by the CIC, but
there is a suitable A interface circuit pool which supports the data
rate requirements, the transaction is interrupted with the A interface
cause Switch Circuit Pool.

Issue 11-0 en
27/02/2008
Half Rate in BSC

more than one alternative is given in the permitted speech version
indication of the Channel Type IE of the resource request, but the
pool of the A interface circuit implied by the CIC does not support all
of them, the BSC checks whether there are other pools of available
circuits which match the codec versions that the A interface circuit
pool does not support.
7. When the speech version requirements and the circuit pool (CIP)
type match fully, the transaction is accepted. The message contains
the Channel Type IE, pool information of the A interface circuit, and
the statement that the pool switching is not allowed.
If the ASSIGNMENT REQUEST is received at the time of the FACCH call

set-up, the checking procedure is modified in the following way:
1. The channel rate and type requirement of the Channel Type IE must
be compatible with the channel rate of the TCH allocated by the
BSC. If it is not, the assignment procedure is interrupted with the
cause Invalid Message Contents.
2. Checks of the speech encoding algorithm versions are made with
regard to the allocated TCH. This is also valid for the data rate
requirements.
3. This statement is valid only if Reversed Hunting is not active. The
pool of the A interface circuit implied by the CIC is compared with the
allocated TCH. If the pool is compatible with the permitted speech
version indication of the Channel Type IE, but it does not support the
TCH that the BSC has allocated for the call or if the speech codec
requirement requires the A interface circuit pool switching, the failure
message is sent to the MSC with the cause Switch Circuit Pool.
If the ASSIGNMENT REQUEST is received during the In Call Modification

procedure, the following actions take place:
1. The channel rate and type requirement of the Channel Type IE must
match the channel rate of the allocated TCH. If it does not, the
assignment procedure is interrupted with the cause Invalid Message
Contents.
2. Checks of the speech encoding algorithm version are made with
regard to the allocated TCH. This is also valid for the data rate
requirements.
3. Because the A interface circuit is already allocated, no other
compatibility checks need to be made.

Issue 11-0 en
27/02/2008
The BSC sends the TCH resource request to the Radio Resource
Management. The message contains the information on the Channel Type
IE, pool information of the A interface circuit, and if the A interface pool
does not fully support the TCH type requirement, information on whether
immediate pool switching is possible or not.
1. If the A interface circuit supports only AMR and the MS supports

both AMR and other codecs, but the target cell has no available
resources and it does not support AMR, a possible AMR call request
is rejected with the cause No Radio Resource Available. However, if
the target cell has other than AMR resources supported by the
configured MS, but no free resources, and queuing or pre-emption is
allowed, the AMR request is rejected with the cause Switch Circuit
Pool.
2. If the A interface circuit only supports the channel rate stated as
preferred in the resource request (here either the MSC or the BSC
itself sets the preference), the BSC attempts to allocate a TCH.
If there are preferred types of TCHs available in the BTS, but the A
interface circuit does not support the speech version set preferred
although the BTS does, the following takes place, depending on the
pool switching advice set by the BSC:
. If the A interface circuit does not support the preferred codec
or codecs and it is possible to switch to the appropriate pool
immediately, the TCH allocation attempt fails with the cause
Switch Circuit Pool. This is the case when the circuit is
allocated by the MSC. If Reversed Hunting is active, pool
switching is handled by the BSC and the MSC is not involved.
Both the queuing of TCH resource and the directed retry are
denied.
. If the A interface circuit does not support the preferred codec
or codecs and it is indicated that the immediate switching to
the appropriate pool is not possible, the TCH is allocated and
the most preferred codec that the A interface circuit pool and
the cell are supporting is used.
If there are no preferred types of TCHs available in the cell, the
following takes place, depending on the TCH configuration of the
BTS and the pool switching advice set by the BSC:

Issue 11-0 en
27/02/2008
Half Rate in BSC
. If the available TCH resources in the cell are other than the
preferred channel rate type, the TCH allocation attempt fails
with the cause Switch Circuit Pool. This is the case when the
circuit is allocated by the MSC. If Reversed Hunting is active,
pool switching is handled by the BSC and the MSC is not
involved. If immediate pool switching is possible, both TCH
resource queuing and directed retry are prohibited, otherwise
they can be attempted.
. If the A interface circuit supports AMR and the MS supports
both AMR and other codecs, but the target cell supports only
either of AMR codec sets but same kind of resources are not
available, a possible AMR call request is rejected with the
cause No Radio Resource Available. However, if the target cell
has other than AMR resources supported by the configured
MS, but no free resources, and queuing and pre-emption is
allowed, the AMR request is rejected with the cause Switch
Circuit Pool.
3. If the A interface circuit does not support the channel rate stated as
preferred in the resource request, the decision of the TCH allocation
attempt again depends on the BTS configuration:
. If the BTS has the preferred type of TCHs available and
immediate pool switching is possible, the TCH allocation
attempt is interrupted immediately with the cause Switch
Circuit Pool. This is the case when the circuit is allocated by
the MSC. If Reversed Hunting is active, pool switching is
handled by the BSC and the MSC is not involved.
Neither TCH resource queuing nor directed retry are allowed
in this case.
. If the BTS has no preferred type of TCHs available, allocation
of a TCH is attempted.
If there are non-preferred types of TCHs available in the BTS
but the A interface circuit does not support the speech version
set as preferred in the channel rate although the BTS does, the
following takes place, depending on the pool switching advice
set by the BSC:

Issue 11-0 en
27/02/2008
a. When the A interface circuit does not support the

preferred codec or codecs of the channel rate and it is
possible to switch to the appropriate pool immediately,
the TCH allocation attempt fails with the cause Switch
Circuit Pool. This is the case when the circuit is allocated
by the MSC. If Reversed Hunting is active, pool
switching is handled by the BSC and the MSC is not
involved. Both the queuing of TCH resource and the
directed retry are denied.
b. When the A interface circuit does not support the
preferred codec or codecs of the TCH rate and it is
indicated that immediate switching to the appropriate
pool is not possible, a TCH is allocated and the most
preferred codec that the A interface circuit pool and the
BTS are supporting is used.
If there are no non-preferred TCHs available in the BTS, the
following takes place, depending on the TCH configuration of
the BTS:
a. If the BTS has preferred channel rate type of TCHs
available, the TCH allocation attempt fails with the cause
Switch Circuit Pool. This is the case when the circuit is
allocated by the MSC. If Reversed Hunting is active,
pool switching is handled by the BSC and, therefore, the
MSC is not involved.
Both the queuing of TCH resource and directed retry are
denied.
b. If the BTS has no preferred channel rate type of TCHs
available, the TCH allocation fails with the cause No
Radio Resource Available.
The queuing of TCH resource and directed retry are both
possible in this case.
The BSC controls that only one attempt is made to switch the A interface
circuit pool during the same assignment or external handover. It is
sufficient that the circuit pool supports the TCH that the BSC is going to
allocate. No pool switching attempt is made for merely changing the A
interface circuit from one pool to another, for example, because of a circuit
reservation situation in a specific pool.
When the initial cause value of the HANDOVER REQUEST is Switch

Circuit Pool, no attempt is made to change the A interface circuit pool. This
kind of handover is interpreted to be an attempt to switch the circuit pool.
In a total pool and Channel Type mismatch cases, the A interface failure
message is always sent with the cause Circuit Pool Mismatch. This is done
regardless of the reason for the last failure message.

Issue 11-0 en
27/02/2008
Half Rate in BSC
Restrictions to the Mode Modify procedure
The Mode Modify procedure cannot be used for changing the TCH rate
from FR to HR and vice versa, because the BTS allows the reconfiguration
of an RTSL only using the Channel Activation command which cannot be
used for an active TCH.
Neither can the Subsequent Assignment procedure be used to change the

TCH type. Subsequent Assignment attempts fail when the uniquely
determined TCH type requirement (that is, either FR or HR TCH) is
contradictory with the channel rate of a call-maintaining TCH.
In both cases, the BSC sends an ASSIGNMENT FAILURE message with

a proper cause value to the A interface.
Switching, for example, from HR transcoded speech to data transmission

in a FR TCH by using Channel Mode Modify is not supported. This is
possible only during handovers.
Restrictions caused by FACCH call set-up
The HR TCH allocation is applied in FACCH call set-up of MOCs only

when the network supports the new establishment causes and the channel
is requested for establishing an HR speech call. The NECI for new
establishment causes is set ON or OFF for an individual cell. When it is set
ON, the phase 2 MSs include more accurate information about the
establishment cause and TCH rate needed for the requested service. The
decision of the initial TCH type in FACCH call set-up is made according to
this information.
The FR TCH is always allocated for emergency calls and mobile-

terminating calls (MTCs) because the HR capabilities of the MS cannot be
solved for the calls in this phase of the call set-up.
When the NECI is set OFF, the FACCH call set-up of MOCs only takes
place on a FR TCH.
There is a possibility of contradictions between the TCH type allocated by

the BSC for an MS supporting HR and the TCH type request of the MSC
when the latter is uniquely determined to be either HR or FR. This can
happen if the MSC does not accept the optional Chosen Channel IE of the
initial message containing layer 3 information sent by the BSS (for
complete Layer 3 information, see 3GPP TS 24.008: Mobile Radio
Interface, Layer 3 Specification). In these cases the BSC sends an
ASSIGNMENT FAILURE message with a proper cause value to the MSC.

Issue 11-0 en
27/02/2008
For more information, see FACCH Call Set-up under Feature descriptions/
Radio network performance in the PDF view.
Restrictions to the Additional Assignment procedure
Additional Assignment is not supported in changing the channel

configuration from HR TCH + ACCH to HR TCH + HR TCH + ACCH.
5.1 The A interface in radio resource allocation

Resource Indication
Both full rate (FR) and half rate (HR) TCH resources available in a specific
cell are represented in the Resource Available IE. Presentation is in terms
of the number of channels available in five interference bands.
The optional Total Accessible Resources IE gives the number of the FR

and HR TCH resources which are accessible or in use.
Complete Layer 3 Information
The message includes the optional Chosen Channel IE which the BSS
can use for giving the MSC a description of the channel (channel rate and
type) on which the first layer 3 message was received. The IE is significant
especially when the MS is assigned from the common control channel
(CCCH) directly to the TCH by the Immediate Assignment procedure.
Assignment and External Handover
The ASSIGNMENT REQUEST and HANDOVER REQUEST messages

contain the mandatory Channel Type IE which represents the channel rate
and type requirement. In speech call cases, the indication of permitted
speech versions is included in the request messages. Space for three
codec versions has been reserved for both FR and HR codecs. Currently
the following speech versions are available:
Full rate:
. GSM 1
.
GSM 2 (EFR)
. GSM 3 (AMR)
Half rate:

Issue 11-0 en
27/02/2008
Half Rate in BSC
. GSM 1
. GSM 3 (AMR)
Codec versions are presented in the order of preference in the indication

list.
The data adaption information is included when a resource is requested for

data.
The HANDOVER REQUIRED and HANDOVER REQUEST messages

include the following optional information elements (IEs):
. Current Channel
Current Channel indicates both the type and the mode of the
channel allocated to the MS. When the channel is a TCH, the
channel rate is specified. The mode indicates whether it is a speech
or a data call. In the case of a data call, the interface rate is also
given.
.
Speech Version
Speech Version indicates the speech version used by the call.
In speech and data call cases, both resource request messages include
the circuit identity code (CIC) of the A interface circuit which the BSC uses
in finding out the transcoding properties. The CIC is not included if
Reversed Hunting is active.
The ASSIGNMENT COMPLETE and HANDOVER REQUEST

ACKNOWLEDGE messages contain the optional Chosen Channel IE. It
describes the radio resource which the BSS has allocated and in TCH
cases also whether it is FR or HR. These messages also include the
Speech Version IE when the BSC chooses the speech version.
Both of the resource request acknowledge messages and the failure

messages ASSIGNMENT FAILURE and HANDOVER FAILURE contain
the optional Circuit Pool IE when several circuit pools are defined on the A
interface for indicating the type of the pool from which the circuit has
initially been allocated.
3GPP specifications (3GPP TS 48.008: MSC-BSS Interface, Layer 3

Specification) define 50 circuit pools supporting different sets of speeds
and data codings.

Issue 11-0 en
27/02/2008
The transcoder and submultiplexer TCSM2 supports six circuit modes

(3GPP TS 48.008: MSC-BSS Interface, Layer 3 Specification). For details,
see table Circuit modes supported by TCSM2.
Table 3. Circuit modes supported by TCSM2
Mode Speech/data
A FR speech version 1
FR speech version 2
FR data (14.5, 12, 6 kbit/s)
B HR speech version 1
C HR speech version 1
FR speech version 1
FR speech version 2
FR data (14.5, 12, 6 kbit/s)
D HR speech version 1
FR speech version 1
FR speech version 2
FR data (14.5, 12, 6 kbit/s)
HSCSD max 2 * FR data (14.5, 12, 6 kbit/s)
E HR speech version 1
FR speech version 1
FR speech version 2
FR data (14.5, 12, 6 kbit/s)
HSCSD max 4 * FR data (14.5, 12, 6 kbit/s)
F HR speech version 3
FR speech version 3
The transcoder and submultiplexer TCSM3i and TCSM3i for combined

BSC3i/TCSM3i installation support three circuit modes (3GPP TS 48.008:
MSC-BSS Interface, Layer 3 Specification). For details, see table Circuit
modes supported by TCSM3i.

Issue 11-0 en
27/02/2008
Half Rate in BSC
Table 4. Circuit modes supported by TCSM3i
Mode Speech/data
G FR speech version 1
FR speech version 2 (EFR)
FR speech version 3 (AMR)
HR speech version 1
HR speech version 3 (AMR)
FR data (14.5, 12, 6, 3.5 kbit/s)
H FR speech version 1
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
HSCSD max 2 x FR data (14.5, 12, 6 kbit/s)
I FR speech version 1
HR speech version 1
The BSC supports the A interface circuit pools listed in table A interface
circuit pools supported by the BSC (for more information, see 3GPP TS
48.008: MSC-BSS Interface, Layer 3 Specification).
Table 5. A interface circuit pools supported by the BSC
A interface circuit Speech/data

pool
1 FR speech version 1
FR data (12, 6, 3.6 kbit/s)
2 HR speech version 1
(only supported by TCSM2)
HR speech version 1

Issue 11-0 en
27/02/2008
Table 5. A interface circuit pools supported by the BSC (cont.)

pool
HR speech version 1
HR speech version 1
HSCSD max 2 x FR data (12, 6 kbit/s)
HR speech version 1
HSCSD max 4 x FR data (12, 6 kbit/s)
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
23 FR speech version 3 (AMR)

Issue 11-0 en
27/02/2008
Half Rate in BSC
Table 5. A interface circuit pools supported by the BSC (cont.)

pool
HR speech version 1
FR data (14.5, 12, 6, 3.5 kbit/s)
(only supported by TCSM3i and TCSM3i for combined
BSC3i/TCSM3i installation)
HR speech version 1
(only supported by TCSM3i and TCSM3i for combined
BSC3i/TCSM3i installation)
The following applies to cases in which Reversed Hunting is not active.
When the resource request is rejected by the BSC because the pool
implied by the CIC does not support any of the speech versions or data
coding indicated in the Channel Type, the cause Circuit Pool Mismatch is
returned to the MSC in the ASSIGNMENT FAILURE and HANDOVER
FAILURE messages.
While the type of circuit pool is compatible with the speech version or data
coding requirements stated in the resource request and the BSC still
wishes to switch the terrestrial circuit to another pool, an ASSIGNMENT
FAILURE or HANDOVER FAILURE message with the cause Switch
Circuit Pool is sent to the MSC.
In both of these two cases the Circuit Pool List IE is included in the failure
messages. The Circuit Pool List presents the pools in the order of
preference, indicated by the BSC, according to which the A interface circuit
should be allocated.

Issue 11-0 en
27/02/2008
The creation method of the Circuit Pool List depends on the actual cause
value, the circuit pool configuration of the A interface and TCH
configuration of the BTS. Not all the pool list variants are presented here in
detail. There are three simple principles which are followed while forming
the circuit pool list:
.
Only those pools which actually exist on the A interface are
represented in the pool list.
.
Circuit pools are switched as seldom as possible. The DR or multiple
codec pools are favoured when the order of preference of the pools
is determined.
. The circuit pool list is formed as simply as possible. Here also
possible future pools, which will increase the complexity of forming
the circuit pool list, must be taken into account.
The BSC sends the HANDOVER REQUIRED message with the cause
Switch Circuit Pool to the MSC when it wants the A interface circuit pool to
be changed during an internal handover. The message is sent if the
successful allocation of a proper TCH in intra-BSS handover requires it.
The message also contains the list of preferred circuit pools.
The MSC gives a HANDOVER REQUEST with the cause Switch Circuit
Pool (or alternatively HANDOVER REQUIRED REJECT) as a response to
the message.
5.2 The Abis interface in radio resource allocation

Channel Activation and Mode Modify
Channel rate and type of the Channel Mode IE specifies the channel
characteristics and the possible data adaption.
Channel Activation Negative Acknowledgement
The following cause values are significant in HR:

Issue 11-0 en
27/02/2008
Half Rate in BSC
1. Radio channel already activated/allocated

. If an attempt is made to activate for an full rate (FR) call a dual
rate (DR) RTSL, which has already been activated for an HR
or FR call.
. If an attempt is made to activate for an HR call a DR RTSL,
which has already been activated for an FR call.
. If an attempt is made to activate for an HR call the subchannel
of a DR RTSL, which has already been activated for an HR
call.
2. Service or Option Not Implemented, Unspecified
Nokia Talk-family BTS with SW releases D1.1 and earlier when an
attempt is made to activate an RTSL for an FR call but the channel
mode in the message is HR.
3. General Information Element Error
.
Nokia Talk-family BTS with SW releases D1.1 and earlier
when an attempt is made to activate an RTSL for an HR call.
.
Nokia Talk-family BTS with SW releases D2.0 and later when
an attempt is made to activate an HR TCH but the TRX
configuration does not support HR.
4. Mandatory Information Element Error
Nokia Talk-Family BTS with SW releases D2.0 and later when the
channel type is accepted but the channel mode is contradictory in
the activation command; replaces the cause Service or Option Not
Implemented, Unspecified.
RF Resource Indication
The channel interference band information of an RTSL is coded per

subchannel. Particularly, both the FR and the HR subchannels of the DR
RTSLs are reported.
5.3 The Radio interface in radio resource allocation

System Information Type 6
In 3GPP specifications, the uplink DTX indicator included in the Cell

Options IE of the SYSTEM INFORMATION TYPE 6 message has different
interpretations when the message is sent on a FR TCH-SACCH or an HR
TCH-SACCH (for more information, see 3GPP TS 44.018: Mobile Radio
Interface, Layer 3 Specification).

Issue 11-0 en
27/02/2008
At the same time the representation of the DTX indicator has an extra bit to
make it possible to define more different combinations (maximum of eight)
of the DTX control orders.
The TRX-specific sending of the SYSTEM INFORMATION TYPE 6 to the

BTS takes place in a similar way as before (as well as the sending of the
BTS-specific SYSTEM INFORMATION 3 message which contains the
DTX indicator sent on the BCCH). The SYSTEM INFORMATION TYPE 6,
sent per TRX, fully determines the DTX control on the FR TCH-SACCH. It
also determines the control on the HR TCH-SACCH, and that is why to get
the right interpretation of the DTX mode, the HR-call-specific SYSTEM
INFORMATION TYPE 6 must always be sent to the BTS when the BTS-
specific DTX indicator has a different meaning on the HR TCH-SACCH
than on the FR TCH-SACCH. Sending of the call-specific SYSTEM
INFORMATION TYPE 6 takes place in the channel activation phase by
loading the message data to the SACCH Information IE of the CHANNEL
ACTIVATION message.
Table Uplink DTX control illustrates the value of the DTX indicator
depending on the uplink DTX mode and the SACCH type. The cases in
which the HR-call-specific SYSTEM INFORMATION TYPE 6 is sent to the
BTS, are also presented:
Table 6. Uplink DTX control
DTX DTX
indicator on indicator on Sys info 6 in
Uplink DTX FR-SACCH HR-SACCH activation of
DTX mode mode of MS bit 8 6 5 bit 8 6 5 HR TCH
0 may use 000 100 Yes
1 uses 001 101 Yes
2 does not use 010 010 No
The columns of the table are:
.
DTX mode
This is the BTS object class parameter, which defines the use of the
uplink DTX. The parameter can have the three different values
presented in the table.
. DTX indicator on FR-SACCH

Issue 11-0 en
27/02/2008
Half Rate in BSC
This presents the way the DTX indicator is coded on the FR TCH-
SACCH. Although bit 8 (of the Cell Options IE) has been included in
the presentation, the coding is the same as earlier because it has
been a spare bit which has always had the value 0. Because the
spare bit 8 is not actually used here, the phase 1 MSs can also
manage with the DTX indicator.
. DTX indicator on HR-SACCH
This presents the way the DTX indicator is coded on the HR TCH-
SACCH.
.
Sys info 6 in activation of HR TCH
This presents the cases in which SYSTEM INFORMATION TYPE 6
is loaded to the CHANNEL ACTIVATION message in activation of
HR TCH.
The discontinuous uplink transmission can be switched off for the HR calls
in the BSS area with the aid of an UTPFIL parameter of the BSC.
Changes in the Assignment and Handover Commands and Channel

Mode Modify because of HR
. channel type of the Channel description IE and the mode in

command messages to the MS
. RR cause Channel Mode Unacceptable in failure messages from the
MS

Issue 11-0 en
27/02/2008
TCH allocation schemes in Half Rate
6 TCH allocation schemes in Half Rate

The following sections cover aspects of TCH allocation at a general level.
The main aspect is how specific types of TCH are allocated depending on
the TCH rate requirement and the A interface circuit pool configuration.
Some special cases on speech codec level are also handled in Enhanced
Speech Codecs: AMR and EFR under Feature descriptions/Radio network
performance in the PDF view. The following signalling cases are described
here:
. assignment
.
external handover
. internal handover

Issue 11-0 en
27/02/2008
Half Rate in BSC
Assignment, basic procedure
MS BTS BSC MSC
Paging part
Paging_Request Paging_Command Paging

3 2 1
Radio access part on CCCH
Channel_Request Channel_Required
4 5
Channel_Activation
6
Channel_Activation_Ack
7
Immediate_Assign_Command
8
Immediate_Assignment
9
DCCH establishment part
Sabm Establish_Indication
10 11
UA
12
Complete_Layer_3_Information
13
SDCCH signalling part:

Ciphering and encryption...
Figure 3. Assignment, mobile terminated call

Issue 11-0 en
27/02/2008
MS BTS BSC MSC
SDCCH signalling part: Call set-up
Set-up
14
Call_Confirmed
15
Assignment_Request
16
Physical_Context_Request
17
Physical_Context_Confirm
18
Channel_Activation
19
20
Assignment_Command
21
FACCH signalling part
22 23
UA
24
Assignment_Complete Assignment_Complete
25 26
Assignment complete
Figure 4. Assignment, mobile terminated call (continued)
1. The message contains the optional Channel Needed

information element (IE) as an indication to the MS
which channel is needed for the transaction related to
the paging. If the TCH is indicated, the alternatives for
channel rates are also given.
2. When the Channel Needed IE is not received from
the MSC, the BSC always includes the IE with the
indicator of 'any channel' in the paging message.

Issue 11-0 en
27/02/2008
Half Rate in BSC
4. The message contains the Establishment Cause.

5. When fast associated control channel (FACCH) call
set-up is applied, the BSC allocates directly a TCH,
half rate (HR) or full rate (FR), if the channel rate is
specified in the Establishment Cause. However,
because the basic call set-up procedure is described
here, we assume that the stand-alone dedicated
control channel SDCCH, is allocated as the channel
first dedicated.
For more information, see FACCH Call Set-up under
Feature descriptions/Radio network performance in
the PDF view.
10. Paging Response; the MS starts to establish the
associated control channel (DCCH).
13. The BSC establishes the signalling connection
control part (SCCP) connection for the dedicated
signalling to the MSC. The message contains the
Paging Response and the optional Chosen Channel
IE for indicating the type of channel from which the
layer 3 message was received. The channel type can
be SDCCH, FR TCH, or HR TCH.
14. Initiates call establishment. No channel type
requirement is set to the MS.
15. The Bearer Capability IE of the message includes
the MS service request. The Radio Channel
Requirement field indicates whether the MS supports
Half Rate or not. The Bearer Capability also contains
the Permitted Speech Version Indication which
represents the speech codecs the MS is supporting in
the order of preference.
16. Request to allocate a TCH radio resource. The
Channel Type IE specifies the channel rate and type.
In a speech call, the indication of permitted speech
versions is included in the IE. In a data call, the data
adaption is represented.
When a resource is requested for speech or data, the
message contains the circuit identification code (CIC)
of the A interface circuit allocated by the MSC. With
this CIC information, the BSC determines the
corresponding circuit pool. The CIC is not included if
Reversed Hunting is active; the A interface circuit is
then allocated by the BSC.
19. The Channel Number and Channel Mode of the
message together specify the channel type and mode
of transcoding (speech version) or rate adaption.

Issue 11-0 en
27/02/2008
System Information Type 6 is included in the SACCH

Information IE when a special uplink DTX control
command must be sent in a HR call.
21. Request for TCH establishment. The Channel Type
of the Channel Description IE indicates the channel
rate and type. The Channel Mode IE gives the mode
of transcoding (speech version) or rate adaption.
25. Successful assignment is performed as follows:
When the ASSIGNMENT COMMAND message
instructs the MS to use a Channel Description or
Mode that it does not support, it returns an
ASSIGNMENT FAILURE message with the cause
Channel Mode Unacceptable and remains on the
current channel and uses the old mode. An
ASSIGNMENT FAILURE message with the cause
Radio Interface Failure, Reversion to Old Channel is
then sent to the MSC.
26. The message contains the optional Chosen Channel
IE if the BSC has been allowed to select the channel.
It gives the channel rate and the type of the radio
channel assigned to the MS.
The optional Speech Version (chosen) IE indicates
the selected speech version. The BSC includes this
IE in the message if it has selected the speech
version.
The optional Circuit Pool IE, which indicates the A
interface circuit pool implied by the CIC of the chosen
circuit, is included when more than one circuit pool
exists on the A interface.

Issue 11-0 en
27/02/2008
Half Rate in BSC
Assignment, change of the circuit pool
MS BTS BSC MSC
SDCCH signalling part: Assignment Request
Assignment_Request
1
Assignment_Failure
2
Assignment_Request
3
4
5
Channel_Activation
6
7
Assignment_Command
8
FACCH signalling part
9 10
UA
11
Assignment_Complete Assignment_Complete
12 13
Assignment complete
Figure 5. Assignment, change of the A interface circuit pool

Issue 11-0 en
27/02/2008
1. Request to allocate a TCH radio resource. The

Channel Type IE specifies the channel rate and type.
In a speech call, the indication of permitted speech
versions is included in the IE. In a data call, the data
adaption is represented.
message contains the CIC of the A interface circuit
allocated by the MSC. With this CIC information, the
BSC evaluates the corresponding circuit pool. If
Reversed Hunting is activated, CIC is not included in
the message; the A interface circuit is allocated by
the BSC.
2. This step is valid only if the MSC has allocated the A
interface circuit. If Reversed Hunting is active, the
pool switching procedure is carried out internally by
the BSC and the MSC is not involved.
When the circuit pool implied by the CIC of the
Assignment Request does not support any speech
codec specified in the Permitted Speech Version
Indication of the Channel Type IE and there is a pool
on the A interface which supports the radio resource
requested, an ASSIGNMENT FAILURE with the
cause Circuit Pool Mismatch is sent to the MSC.
When the circuit pool is compatible with the TCH
resource requirement of the Channel Type IE but the
BSC still wishes to change the circuit pool, the BSC
sends the ASSIGNMENT FAILURE message to the
MSC with the cause Switch Circuit Pool. The reason
for changing the pool in most cases is the actual
traffic channel resource situation of the cell and the
attempt to allocate the TCH radio resources in the
most efficient way. The use of the correct speech
version may also require changing of the A interface
circuit pool.
In both failure cases the Circuit Pool List IE of
preferred pools and the circuit pool implied by the CIC
of the ASSIGNMENT REQUEST (Circuit Pool IE) are
included in the failure message.
interface circuit. If Reversed hunting is active, the
A NEW ASSIGNMENT REQUEST or alternatively a
CLEAR COMMAND is expected from the MSC.

Issue 11-0 en
27/02/2008
Half Rate in BSC
If the circuit pool implied by the CIC of the new

Assignment Request is totally contradictory with the
channel rate or codec requirement specified in the
Channel Type IE, an ASSIGNMENT FAILURE
message with the cause Circuit Pool Mismatch is
sent to the MSC.
If the circuit pool is compatible with the TCH resource
requirement of the Channel Type IE, the BSC
allocates the most suitable TCH which the circuit pool
supports. This is also the case when the pool is the
same as at the time of the first ASSIGNMENT
REQUEST.
An ASSIGNMENT FAILURE message with the cause
No Radio Resource Available is sent to the MSC if
the allocation of the TCH is not successful. The circuit
pool implied by the CIC (Circuit Pool IE) is included in
the failure message as always when more than one
circuit pool is available on the A interface.
IE if the BSC has been allowed to select the channel.
It gives the channel rate and the type of the radio
channel assigned to the MS.
The optional Speech Version (chosen) IE indicates
the selected speech version. The BSC includes this
IE in the message if it has selected the speech
version.
The optional Circuit Pool IE, which indicates the A
circuit, is included when more than one circuit pool

Issue 11-0 en
27/02/2008
Internal handover, intra-cell
MS BTS BSC MSC
Handover measurements and decision
Measurement_Report
1
Measurement_Result
2
Physical context information
3
4
TCH allocation and activation
Channel_Activation
5
6
Signalling on FACCH of source TCH
Assignment_Command
7
Signalling on FACCH of target TCH
Figure 6. Internal handover, intra-cell

Issue 11-0 en
27/02/2008
Half Rate in BSC
MS BTS BSC MSC
8 9
UA
10
Assignment_Complete Handover_Performed
11 12
Source TCH release in BTS
RF_Channel_Release
13
RF_Channel_Release_Ack
14
Figure 7. Internal handover, intra-cell (continued)
5. The Channel Type IE initially received from the MSC

and the type of the source TCH primarily determines
the channel rate of the TCH that the BSC tries to
allocate.
The channel rate and speech version changes are
controlled with the BSS- and BTS-specific
parameters of the BSC. The MSC can also set its
own restrictions.
When the successful allocation of a TCH requires
channel rate change and it is allowed, but the A
interface circuit pool does not support the other type
of TCH, the BSC can try to change the pool if there is
a suitable one on the A interface.
During the handover, the speech version can be
changed even though the channel rate remains
unchanged. This also requires the changing of the A
interface circuit into a pool which supports the new
codec version.
The pool switching procedure is initiated by sending
the HANDOVER REQUIRED message to the A
interface with the cause Switch Circuit Pool. The
message also contains the list of preferred pools
(Circuit Pool List IE) and the identifier of the cell
candidate. The list of preferred pools is not included
in the message if Reversed Hunting is active. The

Issue 11-0 en
27/02/2008
optional IEs Current Channel and Speech Version

(used), which characterise the source channel type
and mode and used speech version, can be included
in the message.
The Channel Number and Channel Mode of the
CHANNEL ACTIVATION message together specify
the channel type and mode of transcoding or rate
adaption.
7. The Channel Type of the Channel Description IE
indicates the channel rate and type of the target
channel. The Channel Mode IE gives the mode of
transcoding (speech version) or rate adaption.
11. A successful handover is performed as follows:
When the ASSIGNMENT COMMAND message
instructs the mobile station to use a Channel
Description or Mode that it does not support, it returns
an ASSIGNMENT FAILURE message with the cause
current channel using the old mode.
IE if the TCH rate has been changed during the
handover. It gives the channel rate and the type of the
radio channel allocated to the MS.
The optional Speech Version (used) IE is also
included when the speech codec has been changed
during the handover.

Issue 11-0 en
27/02/2008
Half Rate in BSC
Internal handover, inter-cell
MS BTS1 BTS2 BSC MSC
Handover measurements and decision
Measurement_Report
1
Measurement_Result
2
TCH allocation and activation in target BTS2
Channel_Activation
3
4
Signalling on FACCH of source BTS1 TCH
Handover_Command
5
Signalling on FACCH of target BTS2 TCH
Handover_Access Handover_Detection
6 7
Physical_Information
8
9 10
UA
11
Handover_Complete Handover_Performed
12 13
Figure 8. Internal handover, inter-cell (asynchronous)

Issue 11-0 en
27/02/2008
MS BTS1 BTS2 BSC MSC
TCH release in source BTS1
RF_Channel_Release
14
15
Figure 9. Internal handover, inter-cell (asynchronous) (continued)
3. The Channel Type IE initially received from the MSC

and the type of the source TCH primarily determines
the channel rate of the TCH that the BSC tries to
allocate. The channel rate and speech version
changes are controlled with the BSS-specific
parameter of the BSC. The MSC can also set its own
restrictions.
When the successful allocation of a TCH requires
channel rate change and it is allowed but the A
interface circuit pool does not support the other type
of TCH, the BSC can try to change the pool if there is
a suitable one on the A interface.
During the handover, the speech version can be
changed even though the channel rate remains
unchanged. This also requires changing the A
interface circuit to a pool which supports the new
codec version.
The pool switching procedure is initiated by sending
the HANDOVER REQUIRED message to the A
interface with the cause Switch Circuit Pool. The
message also contains the list of preferred pools
(Circuit Pool List IE) and the identifier of the cell
candidate. The list of preferred pools is not included
in the message if Reversed Hunting is active. The
and mode and used speech version, can be included
in the message.

Issue 11-0 en
27/02/2008
Half Rate in BSC
The Channel Number and Channel Mode of the

CHANNEL ACTIVATION message together specify
the channel type and mode of transcoding or rate
adaption.
5. The Channel Type of the Channel Description IE
indicates the channel rate and type. The Channel
Mode IE gives the mode of transcoding or rate
adaption.
12. A successful handover is performed as follows:
When the HANDOVER COMMAND message
Mode that it does not support, it returns a
HANDOVER FAILURE message with the cause
current channel and uses the old mode.
IE if the TCH rate has been changed during the
handover. It includes the channel rate and the type of
the radio channel allocated to the MS.
The optional Speech Version (used) IE is also
included when the speech codec has been changed
during the handover.
Changing of the A interface circuit pool
Sometimes during an internal handover the TCH rate change only enables
successful traffic channel allocation. This naturally requires that rate
changes are allowed in general. If the A interface circuit does not support
the new channel type of the target cell, the A interface circuit pool must be
changed.
The BSC initiates the procedure by sending the HANDOVER REQUIRED

message with the cause Switch Circuit Pool to the A interface. The
message also contains the preferred list of pool candidates except when
Reversed Hunting is active. The cell identifier list includes only the target
cell in which the suitable TCH resource can possibly be allocated after the
pool change. The procedure can be initiated both during inter-cell and
intra-cell handovers.

Issue 11-0 en
27/02/2008
The TCH rate changes are not the only reason for codec change at the
time of the internal handover. The BTS may not support the transcoding
used in the source cell, therefore, the speech version should be changed
to a more suitable one. This may sometimes also require switching the A
interface circuit pool.
The circuit pool change procedure is not started for an internal handover
when, during the same handover, an unsuccessful external handover
attempt has already been made, followed by an internal handover attempt.
Handovers to the TCHs of the super-reuse frequency area are exceptional

because they can be merely BSC-controlled. During these handovers the
circuit pool cannot be changed with the aid of the handover type
reselection. For more information, see Intelligent Underlay-Overlay under
Feature descriptions/Radio network performance in the PDF view.
A circuit pool change cannot be initiated during a traffic reason handover

nor during a forced handover caused by pre-emption. The BSS-internal
handovers related to directed retry also have restrictions because they
take place during the assignment procedure.

Issue 11-0 en
27/02/2008
Half Rate in BSC
External handover, basic procedure
MS BTS BSC MSC
Handover measurements
Handover decision and inquiry
Measurement_Report
1
Measurement_Result
2
Handover_Required
3
TCH allocation and activation in target BSS

Handover Command from MSC, FACCH signalling
Handover_Command Handover_Command
5 4
Signalling on FACCH-TCH in target BSS,

disconnection, TCH release in source BSS
Clear_Command
6
RF_Channel_Release
7
8
Clear_Complete
9
Figure 10. External handover, source BSS
3. The source BSC starts an external handover by

sending the HANDOVER REQUIRED message to
the MSC. The message contains a candidate cell list
and a handover cause.
The optional IEs Current Channel and Speech
Version (used), which characterise the source
channel type and mode and the used speech version,
can be included in the message.

Issue 11-0 en
27/02/2008
A handover controlled internally by BSS can be

turned into an MSC-controlled one when the TCH
allocation requires an A interface pool change. The
initial handover can be an inter-cell or an intra-cell
one. In this case, the handover cause is: Switch
Circuit Pool, and the HANDOVER REQUIRED
message contains the Circuit Pool List IE of preferred
pools, except when Reversed Hunting is active. Only
one cell is included in the cell identifier list.
The source BSS in this case is also the target BSS. A
HANDOVER REQUEST with the cause Switch
Circuit Pool or a HANDOVER REQUIRED REJECT
is expected from the MSC.
4. The MSC requires the MS to be handed over. The
message contains the Layer 3 HANDOVER
COMMAND to be sent to the MS.
5. The radio interface HANDOVER COMMAND
message is sent to the MS. The Channel Type of the
Channel Description IE indicates the channel rate
and type. The Channel Mode IE gives the mode of
transcoding or rate adaption.
When the HANDOVER COMMAND message
Mode that it does not support, it returns a
current channel and uses the old mode. A
Radio Interface Failure, Reversion to Old Channel is
then sent to the MSC.

Issue 11-0 en
27/02/2008
Half Rate in BSC
MS BTS BSC MSC
Decision of external handover in source BSS

The MSC sends the Handover Request
Handover_Request
1
TCH allocation and activation in target BTS
Channel_Activation
2
3
Handover_Request_Ack
4
Signalling on FACCH-TCH
5 6
Handover_Detect
7
8
9 10
UA
11
Handover_Complete Handover_Complete
12 13
Figure 11. External handover, target BSS

Issue 11-0 en
27/02/2008
1. A request to allocate a TCH radio resource for a

handover. The Channel Type IE specifies the channel
rate and type. In a speech call, the indication of
permitted speech versions is included in the IE. In a
data call, the data adaption is represented.
The message that the MSC sends includes the
and mode and the used speech version. With this
information the channel rate and speech version
changes are controlled with the BSS-specific
parameter of the BSC.
allocated by the MSC. With this CIC information the
BSC can evaluate the corresponding circuit pool. The
CIC is not included in the message if Reversed
Hunting is active.
The message contains both target and source cell
identifiers and the handover cause.
2. The Channel Number and Channel Mode of the
message together specify the channel type and mode
of transcoding or rate adaption.
A System Information Type 6 is included in the
SACCH Information IE when a special uplink DTX
control command must be sent in a HR call.
4. The HANDOVER REQUEST ACKNOWLEDGE
message contains the Layer 3 Handover Command
directed to the source BSS in order to be sent to the
MS. The Channel Type of the Channel Description IE
indicates the channel rate and type. The Channel
Mode IE gives the mode of transcoding or rate
adaption.
The optional Circuit Pool IE which indicates the A
circuit is included when more than one circuit pool
External handover, change of the circuit pool
The following procedure takes place in the target BSS.

Issue 11-0 en
27/02/2008
Half Rate in BSC
MS BTS BSC MSC
Decision of external handover in source BSS

MSC sends the Handover Request to target BSS
Handover_Request
1
Handover_Failure
2
Handover_Request
3
TCH allocation and activation in target BTS
Channel_Activation
4
5
Handover_Request_Ack
6
Signalling on FACCH-TCH
7 8
Handover_Detect
9
10
11 12
UA
13
Handover_Complete Handover_Complete
14 15
Figure 12. External handover, change of the A interface circuit pool

Issue 11-0 en
27/02/2008
1. A request to allocate a TCH radio resource for a

handover. The Channel Type IE specifies the channel
rate and type. In a speech call, the indication of
permitted speech versions is included in the IE. In a
data call, the data adaption is represented.
The optional IEs Current Channel and Speech
Version (used), which characterise the source
channel type and mode and the used speech version,
can be included in the message sent by the MSC.
With this information the channel rate and speech
version changes are controlled with the BSS-specific
parameter of the BSC.
which the MSC has allocated. With the CIC
information the BSC can evaluate the corresponding
circuit pool. The CIC is not included in the message if
Reversed Hunting is active.
The message contains both target and source cell
identifiers and the handover cause.
When the circuit pool implied by the CIC of the
HANDOVER REQUEST does not support any
speech codec specified in the Permitted Speech
Version Indication of the Channel Type IE and there is
a pool on the A interface which supports the radio
resource requested, a HANDOVER FAILURE with
the cause Circuit Pool Mismatch is sent to the MSC.
resource requirement of the Channel Type IE but the
BSC still wishes to change circuit pools, the BSC
sends the HANDOVER FAILURE message to the
MSC with the cause Switch Circuit Pool. The reason
for changing pools in most cases is the actual traffic
channel resource situation of the cell and the attempt
to allocate the TCH radio resources in the most
efficient way. The use of the correct speech version
may also require the A interface circuit pool to be
changed.

Issue 11-0 en
27/02/2008
Half Rate in BSC
Note that the failure message can be delayed in the

pool switching case because of queuing of the TCH
resource request, that is, the MSC receives it after the
Queuing Indication.
In both failure cases the Circuit Pool List IE of
preferred pools and the circuit pool implied by the CIC
of the HANDOVER REQUEST (Circuit Pool IE) are
included in the failure message.
When the cause of the initial HANDOVER REQUEST
is the Switch Circuit Pool, the BSC does not attempt
the pool change because the handover has already
been initiated because of the change of the A
interface circuit pool. The BSC tries to allocate a TCH
supported by the A interface circuit pool. In an
unsuccessful case, a HANDOVER FAILURE
message with the cause No Radio Resource
Available is sent to the MSC. However, in total pool
mismatch cases, the failure message is always sent.
A NEW HANDOVER REQUEST or alternatively a
CLEAR COMMAND is expected from the MSC.
When the circuit pool implied by the CIC of the new
HANDOVER REQUEST is totally contradictory with
the channel rate and codec version requirements
specified in the Channel Type IE, a HANDOVER
FAILURE message with the cause Circuit Pool
Mismatch is sent to the MSC.
resource requirement of the Channel Type IE, the
BSC allocates the most suitable TCH which the
circuit pool supports, also in the case in which the
pool is the same as it was at the time of the first
HANDOVER REQUEST.
A HANDOVER FAILURE message with the cause No
Radio Resource Available is sent to the MSC if the
allocation of a TCH is not successful. The circuit pool
implied by the CIC (Circuit Pool IE) is included in the
failure message as always when more than one
circuit pool is available on the A interface.

Issue 11-0 en
27/02/2008
Directed retry
Directed retry is initiated by the assignment procedure when there is a

temporary traffic channel congestion in the serving cell. The MS is going to
be assigned to a traffic channel of an adjacent cell which is selected on the
basis of the radio measurement reports received from the MS.
The TCH allocation in an internal directed retry handover becomes more

complicated than in an allocation during a normal assignment because in
the former case there can be more than one cell candidate. The
complexity increases when only the preferred channel rate is represented
in the radio resource request. The A interface circuit pool switching can be
started only when target cell for directed retry handover does not support
AMR, but the allocated circuit supports only AMR.
A directed retry handover is initiated in the SDCCH signalling phase.

Therefore, possible channel rate change prohibitions that either the BSC
or the MSC have set have no effect here. The following principles are
observed in TCH allocation for internal directed retry handover:
1. When there is a BTS in the candidate list from which the required
(preferred) type of TCH can be allocated, the TCH is allocated from
the best possible cell.
2. When the preferred type of TCH is not available in a specific cell of
the candidate list but it has the secondary type of TCHs available
and the circuit pool supports the secondary type of TCH, the
secondary type of TCH is allocated. This takes place regardless of
the possibility of there being a worse cell in the candidate list which
has the preferred type of TCHs available.
RXLev Min Access
If RXLev Min Access is activated in the BSC, the carrier-to-noise ratio (C/
N) based method for a speech and a data call is used to determine
whether TCH can be allocated according to the downlink RX level
measured by the MS.
For more information, see RXLev Min Access in Radio Channel Allocation
under Functional Descriptions/Radio network performance in the PDF
view.

Issue 11-0 en
27/02/2008
Half Rate in BSC

Issue 11-0 en
27/02/2008
User interface of Half Rate
7 User interface of Half Rate

MML commands
.
Transceiver Handling (command group ER)
. Base Station Controller Parameter Handling in BSC (command
group EE)
. Base Transceiver Station Handling in BSC (command group EQ)
Parameters
Half Rate (HR) related parameters of the BSDATA (BSS Radio Network
Configuration Database) are located in the BSC, BTS, TRX and radio
timeslot (RTSL) objects. HR-related parameters are visible only if HR is
activated and the BSC is equipped with a bit group switch (GSWB).
.
TRX half rate support (HRS) (ERC, ERM, and ERO commands)
. RTSL type 0–7 (CH0–CH7) (ERC, ERM, ERO, and EEI commands)
. lower limit for FR TCH resources (FRL/HRL) (EEM, EEO,
EQM, and EQO commands)
. upper limit for FR TCH resources (FRU/HRU) (EEM, EEO,
EQM, and EQO commands)
. TCH in handover (HRI) (EEM and EEO commands)
.
TCH rate intra-cell handover (TRIH) (EQM and EQO
commands)
.
initial AMR channel rate (IAC) (EEM and EEO commands)
. alarm limit for full rate TCH availability (ALFRT) (EEQ
and EEO commands)

Issue 11-0 en
27/02/2008
Half Rate in BSC
. alarm limit for half rate TCH availability (ALHRT) (EEQ

and EEO commands)
. CS TCH allocation calculation (CTC) (EEM and EEO
commands)
For more information on parameters, see
.
. Channel rate selection based on cell load
.
Channel rate for AMR calls in Enhanced Speech Codecs: AMR and
EFR under Feature descriptions/Radio network performance in the
PDF view
. BSS Radio Network Parameter Dictionary under Reference/
Parameters in the PDF view.
Alarms
. 7717 WORKING HALF RATE TCH RATIO BELOW THRESHOLD

.
7711 WORKING FULL RATE TCH RATIO BELOW THRESHOLD
. 7727 TRAFFIC CHANNEL NUMBER DECREASED
.
7741 MEAN HOLDING TIME ABOVE DEFINED THRESHOLD
The SUB_CH_ID field indicates if the HR channel generates the
alarm.
. 7743 MEAN HOLDING TIME BELOW DEFINED THRESHOLD
alarm.
. 7745 CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD
alarm.
.
7746 CH CONGESTION IN CELL ABOVE DEFINED THRESHOLD
The REFUSED_HR_CALLS_PERCENTAGE field indicates the
number of HR channel requests rejected because of congestion
compared with all channel requests which are rejected because of
congestion.

Issue 11-0 en
27/02/2008

Half Rate in BSC

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Half Rate in BSC

Transféré par

Droits d'auteur :

Formats disponibles

BSC3153

Nokia GSM/EDGE BSS, Rel. BSS13, BSC and

Half Rate in BSC

DN9814086 # Nokia Siemens Networks 1 (80)

2 (80) # Nokia Siemens Networks DN9814086

1 Overview of Half Rate 9

2 Technical description of Half Rate 11

3 Channel rate and speech codec control in handovers 19

4 Channel rate selection based on cell load 27

5 Half Rate and radio resource allocation 33

6 TCH allocation schemes in Half Rate 55

7 User interface of Half Rate 79

DN9814086 # Nokia Siemens Networks 3 (80)

Table 1. Conversion of RTSL types on the Abis O & M interface 12

4 (80) # Nokia Siemens Networks DN9814086

Figure 1. Transmission example 17

DN9814086 # Nokia Siemens Networks 5 (80)

6 (80) # Nokia Siemens Networks DN9814086

Changes between document issues are cumulative. Therefore, the latest

Changes made between issues 11-0 and 10-0

Section Fault recovery in chapter Technical description of Half Rate has

Changes made between issues 10-0 and 9-1

Chapter Overview of Half Rate

The list of related topics has been modified and updated.

Chapter Technical description of Half Rate

Subsection Capacity and channel resources

Information referring to TRCU and SM2M has been deleted and

Subsection Requirements for Half Rate

Figure Transmission example has been updated.

Information referring to TCSM2 and the explanation of the function of

DN9814086 # Nokia Siemens Networks 7 (80)

Chapter Channel rate and speech codec control in handovers

A reference to internal handover to external has been added.

Chapter Half Rate and radio resource allocation

More information on the channel allocation for mobile-terminating calls

Minor editorial changes throughout the document.

Changes made between issues 9-1 and 9-0

Nokia licence control information has been added.

8 (80) # Nokia Siemens Networks DN9814086

1 Overview of Half Rate

It is possible to introduce HR coding to existing full rate GSM networks

Half Rate is an application software in the BSC.

Related topics in Half Rate in BSC

. Technical description of Half Rate

DN9814086 # Nokia Siemens Networks 9 (80)

. TCH allocation schemes in Half Rate

Other related topics

10 (80) # Nokia Siemens Networks DN9814086

2 Technical description of Half Rate

Introduction of Half Rate (HR) to a network has significant effects on the

DN9814086 # Nokia Siemens Networks 11 (80)

Effects on the Abis O & M interface

Table 1. Conversion of RTSL types on the Abis O & M interface

BSC database Abis O&M BTS

When a TRX test using RTSL(s) configured as a HR TCH or a DR TCH is

Effects on the Q3 interface

A TRX-specific parameter is needed to indicate whether the TRX supports

Radio network supervision

The radio network supervision reports on the network capacity problems

12 (80) # Nokia Siemens Networks DN9814086

. mean duration of calls on a specific channel

The measurement reveals possible hanging calls and sudden call

The traffic channel congestion level is measured per BTS. HR and FR