Professional Documents
Culture Documents
With Half Rate (HR) coding it is possible to maximise the spectrum efficiency. The Half
Rate 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. Half rate 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 Half Rate 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 Half Rate.
Each radio time slot 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 time slot either for half rate or full rate coding on a call basis.
It is possible to introduce Half Rate coding to existing full rate GSM networks gradually.
The A interface supports different types of transcoders capable of full rate coding, half
rate coding, or both. The BSS is able to co-operate simultaneously with both old phase 1
full-rate-only mobile stations and with phase 2 mobile stations that support both full and
half rate. Half Rate can thus also be installed in the network without replacing the old
transcoders with new ones that support the Half Rate coding.
TCHF
TCHF
TCHH
TCHD
TCHD
TCHD
TCHD
TCHD
The measurement reveals possible hanging calls as well as sudden call drops
immediately after call establishment.
Fault recovery
TRX half rate support (HRS)
In general, the BSC performs the BCCH reconfiguration so that the RTSLs carrying
control channels (BCCH and SDCCH) are reconfigured from the faulty TRX to another
TRX of the BTS. The parameters of the TRX, that is, the frequency and frequency-related
parameters, are swapped between the faulty BCCH TRX and the new BCCH TRX. The
hopping-related parameters of the RTSL are also swapped between all RTSLs.
Depending on the TRX configuration, a situation might arise in the Nokia 2nd generation
BTS where the HR TCH is configured as a FR TCH after the BCCH reconfiguration.
This can happen if there are TRXs which support Half Rate and TRXs which do not
support Half Rate in the same cell. If this happens, the TRX carrying the BCCH becomes
faulty and it does not support Half Rate. The RTSL no. 0 of the working TRX is
configured to be a HR TCH. Channel types of the faulty TRX RTSLs cannot be swapped
directly between the corresponding RTSLs on the working TRX but the control channel
RTSLs on the faulty TRX must be configured as FR TCHs. The HR TCHs on the
working TRX are configured as control channels.
In this case the number of available HR TCHs is reduced because of a TRX failure. The
HR TCHs configured by the operator are not automatically returned into use when the
recovery system notices that the faulty TRX is again working normally. You must restore
the original configuration manually by using the Radio Network Configuration
Management MMLs.
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 TCH(s) is/are changed to (a) NOTUSED channel(s),
because TCH resources have run out. The channel types changed by the system start from
CH7 downwards.
Parameters
In handovers for speech calls, the parameters TCH in handover (HRI) and TCH rate
intracell 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.
TCH in handover (HRI): This
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.
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 fulfils 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 actual TCH resource situation, that is, the traffic load of 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 a 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, a HR
TCH is allocated from the best of the candidate cells.
When the MSC has preferred the HR TCH and thus 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.
HRI =5: The TCH must be allocated from the best BTS of the handover candidate list,
regardless of the speech codec version actually used.( 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 traffic load of 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, a HR TCH is allocated.
When the type of the source TCH is HR and thus 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.
TCH rate intracell 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 the cases 1-4 described
above.
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 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.
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. The figure below visualises the effect
of Half Rate on TCH allocation.
Half Rate is applicable for speech calls, and signalling with some exceptions. For data
calls, FR TCH is the only alternative.
If Half Rate is activated and the lower limit is set to be greater than zero, at least the last
free dual rate (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
lower limit for FR TCH resources:
Half Rate is enabled in specific cells when either of the two parameter pairs is effective.
However, when the SEG-specific parameters: lower limit for FR TCH resources
(FRL) and upper limit for FR TCH resources (FRU) are effective, the BSC-level
parameters: lower limit for FR TCH resources (HRL) and upper limit for FR
TCH resources (HRU) are not significant in TCH allocation.
If the upper limit is set smaller than the lower limit the effect of the parameters is
deactivated.
Half Rate is disabled in specific cells when it is disabled both on the BSS-level and celllevel.
These parameters are handled with the EEM, EEO, EQM, and EQO commands.
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.
(E)GPRS
If the (Enhanced) General Packet Radio Service ((E)GPRS) 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) (E)GPRS
traffic. In this case the actual TCH load thresholds used in TCH rate selection are
calculated applying the threshold parameters to the resource amounts of the CS territory.
With the CS TCH allocation calculation (CTC) parameter the operator is able to
define how the PSW used RTSLs are seen when calculating resources for CS allocation.
MS cannot be solved for the call in this phase of the 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 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 only FR transcoding. If the MS supports Half Rate, 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 are supported by
the BTS.
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.
In the subsequent assignment case as well as in initial assignment of the fast associated
control channel (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.
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.