Você está na página 1de 56

GSM/EDGE BSS, Rel.

RG20(BSS), Operating
Documentation, Issue 04

Feature description

BSS7003 and BSS7037: HSCSD and 14.4


kbit/s Data Services in BSC
DN9813893
Issue 9-0
Approval Date 2010-04-26

Confidential

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services 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 2010. All rights reserved

Important Notice on Product Safety


This product may present safety risks due to laser, electricity, heat, and other sources
of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle
this product and only after having carefully read the safety information applicable to this
product.
The safety information is provided in the Safety Information section in the Legal, Safety
and Environmental Information part of this document or documentation set.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit


Von diesem Produkt knnen Gefahren durch Laser, Elektrizitt, Hitzeentwicklung oder
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch
geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheitsanforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter Sicherheitshinweise im Teil Legal,
Safety and Environmental Information dieses Dokuments oder dieses Dokumentationssatzes.

Id:0900d8058072ae6a
Confidential

DN9813893
Issue 9-0

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Table of contents
This document has 56 pages.
Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1

Overview of HSCSD and 14.4 kbit/s Data Services in BSC . . . . . . . . . . 7

Technical description of HSCSD and 14.4 kbit/s Data Services in BSC . 9

Functionality of HSCSD and 14.4 kbit/s Data Services in BSC . . . . . . . 16

4
4.1

HSCSD and 14.4 kbit/s Data Services effects on interface procedures 27


HSCSD and 14.4 kbit/s Data Services effects on A interface procedures.
27
HSCSD and 14.4 kbit/s Data Services effects on the Abis interface procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
HSCSD and 14.4 kbit/s Data Services effects on Radio interface procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4.2
4.3

DN9813893

Schemes in HSCSD and 14.4 kbit/s Data Services. . . . . . . . . . . . . . . . 35

User interface of HSCSD and 14.4 kbit/s Data Services . . . . . . . . . . . . 55

Id:0900d8058072ae6a
Confidential

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

List of figures
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
Figure 10
Figure 11
Figure 12
Figure 13
Figure 14
Figure 15
Figure 16
Figure 17
Figure 18

HSCSD network architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9


Double slot operation in the radio interface . . . . . . . . . . . . . . . . . . . . . . 10
Puncturing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Example of Ater switching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Transmission example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Ater TSL allocation example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Ater TSL allocation example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Ater TSL allocation example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Channel type information element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Coding of data rate/transparency indicator field . . . . . . . . . . . . . . . . . . . 27
Mobile-originated call setup, basic scheme . . . . . . . . . . . . . . . . . . . . . . 36
Mobile-originated call setup, basic scheme . . . . . . . . . . . . . . . . . . . . . . 37
Resource downgrade from 3+1 to 2+2 HSCSD configuration, basic
scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Resource upgrade from 2+2 to 3+1 HSCSD configuration, basic scheme .
40
Resource upgrade from 2+2 to 3+1 HSCSD configuration, basic scheme .
41
BSC internal inter-cell handover, basic scheme . . . . . . . . . . . . . . . . . . . 43
External handover, basic scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
External handover, basic scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Id:0900d8058072ae6a
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

List of tables
Table 1
Table 2

DN9813893

Data rates achieved by HSCSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7


Different failure causes scenarios for in call modification . . . . . . . . . . . 13

Id:0900d8058072ae6a
Confidential

Summary of changes

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Changes between issues 9-0 (2010/04/26, RG20(BSS)) and 8-0(2009/12/02,
RG10(BSS))
Technical description of HSCSD and 14.4 kbit/s Data Services in BSC (2)
Added information on BSS21238:Merged PGSM900 and EGSM900 feature
under Restrictions in the use of HSCSD and 14.4 kbit/s data services.
Added Restriction due to Packet abis and A over IP under In Call Modification
Added sectionBSS21238:Merged PGSM900 and EGSM900, BSS21341: A over IP,
Transcoder in BSS and BSS21454: Packet Abis over IP/Ethernet and BSS21440:
Packet Abis over TDM under Interworking with other functionalities
Changes made between issues 8-0 and 7-0
The term circuit mode is replaced with the term circuit type throughout the document.
Chapter HSCSD and 14.4 kbit/s Data Services effects on interface procedures: new
AMR-WB pools have been added and the definitions to circuit types has been modified.
Changes made between issues 7-0 and 6-0
Editorial changes.

Id:0900d8058072aec5
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Overview of HSCSD and 14.4 kbit/s Data Services in


BSC

1 Overview of HSCSD and 14.4 kbit/s Data


Services in BSC
High Speed Circuit Switched Data (HSCSD) and 14.4 kbit/s data services are system
functionalitites in Nokia Siemens Networks DX 200 Base Station Controller (BSC) and
TCSM.
They have effects on the following network elements: the Mobile Switching Center
(MSC), Base Transceiver Station (BTS), NetAct, the Mobile Station (MS) and NPS/X.
High Speed Circuit Switched Data (HSCSD)
High speed circuit switched data provides accelerated data rates for end-user applications. The current trend is for increased demand for high data rate applications such as
the World Wide Web (WWW), file transfer and facsimile. HSCSD will facilitate the use
of such applications.
The Base Station System (BSS) implementation is to reserve a multiple set of basic (current) resources for one high speed data call. The data rate and number of reserved time
slots varies between one and a user application-defined maximum. The variable rate is
needed, for example, for handovers to a new cell if the requested data rate cannot be
given immediately. The BSS implementation of HSCSD supports simultaneous use of
four time slots per one HSCSD call. The following table presents the corresponding
maximum data rates with different channel codings:
RTSLs

9.6 kbit/s

14.4 kbit/s

9.6 kbit/s

14.4 kbit/s

19.2 kbit/s

28.8 kbit/s

28.8 kbit/s

43.2 kbit/s

38.4 kbit/s

57.6 kbit/s

Table 1

Data rates achieved by HSCSD

Both asynchronous and synchronous bearer services and transparent and non-transparent transfer modes are supported. Transparent HSCSD uses fixed data rates
throughout the call whereas non-transparent HSCSD is flexible and the data rate can be
changed during the call for example due to the traffic situation. The radio interface is
either symmetric or asymmetric depending on MS capability. However, the Abis interface and the A interface are always symmetric. In the A interface, HSCSD connections
can be switched to one of the HSCSD supporting pools.
14.4 kbit/s data services
14.4 kbit/s data services accelerates the standard 9.6 kbit/s user data rate with a single
time slot to 14.4 kbit/s.
The use of 14.4 kbit/s data service reduces cell coverage. For example, if the current
9.6 kbit/s service has 90% coverage, the 14.4 kbit/s service will have about 84-87% coverage. The current threshold for power control represents the predicted border of the
acceptable user data performance for the speech or 9.6 kbit/s data. This is not adequate
for 14.4 kbit/s user data since 14.4 kbit/s channel coding can stand fewer errors. To
maintain 14.4 kbit/s performance adequate, the RX_QUAL value has to be better and

DN9813893

Id:0900d80580735035
Confidential

Overview of HSCSD and 14.4 kbit/s Data Services in


BSC

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

therefore the power increase has to be started at higher quality for 14.4 kbit/s calls than
for other calls.
A threshold parameter pc lower thresholds qual144 Rx level (LQR), Px
(LQP), Nx (LQN) is defined for triggering downlink and uplink power increase for 14.4
kbit/s connections. However, for optimal performance, channel coding is changed
between 14.4 kbit/s and 9.6 kbit/s channel codings by the automatic link adaptation
(ALA) procedure according to Mobile Station (MS) and Base Transceiver Station (BTS)
power levels. The parameter power limit ALA (ALIM) determines the MS and BTS
power levels when ALA is performed. ALA is applicable for non-transparent data connections.
14.4 kbit/s data service can be combined with HSCSD. In the A interface, 14.4 kbit/s
data connection can be switched to one of the pools which support 14.4 kbit/s channel
coding.
Related topics of HSCSD and 14.4 kbit/s Data Services in BSC

Technical description of HSCSD and 14.4 kbit/s Data Services in BSC


Functionality of HSCSD and 14.4 kbit/s Data Services in BSC
HSCSD and 14.4 kbit/s Data Services effects on interface procedures
Schemes in HSCSD and 14.4 kbit/s Data Services
User interface of HSCSD and 14.4 kbit/s Data Services

Other related topics

Instruction
Activating and Testing BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data
Services

Id:0900d80580735035
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Technical description of HSCSD and 14.4 kbit/s Data


Services in BSC

2 Technical description of HSCSD and 14.4


kbit/s Data Services in BSC
In HSCSD, higher data rates can be offered using several full rate TCHs for one connection. Therefore, a functionality is needed in both the MS and the MSC to split data to
be carried in several radio interface FR TCHs and then to be combined at the other end.
For cellular operations, the HSCSD channels in the same connection are controlled as
one radio link. For example, handovers are made simultaneously for all channels in one
HSCSD connection. On the A interface, HSCSD channels are multiplexed to one 64
kbit/s circuit (see Figure HSCSD network architecture).
In the Ater interface, HSCSD calls use circuit pools supporting four and eight bit switchings. Support for cases when the A interface does not support the pool concept is also
required.
MS

BTS

BSC

TCSM

MSC

Air i/f

Abis i/f

Ater i/f

A i/f

1-4
TCH/F

1-4
TCH/F

max 1
circuit

max 1
circuit

T
A
F

Figure 1

HSCSD network architecture

The adaptation of the GSM transmission to other networks (for example, PSTN) is done
by the Interworking Functions (IWF) in MSC. On the MS side, the Terminal Adaptation
Function (TAF) performs the adaptation between the terminal equipment and the GSM
radio transmission part.
Transparent (T) service
In transparent data services, the radio interface transmission scheme provides only
forward error correction. The throughput between IWF and TAF is constant. In HSCSD,
this means that the requested data rate has to be fulfilled from the call setup to the
release of the call, including possible handovers during the call. Radio interface user
rates are requested in T service (for example 4.8, 9.6 or 14.4 kbit/s). In HSCSD, the
transparent service uses only bi-directional channels.
Non-transparent (NT) service and flexible channel allocation
In non-transparent data services the sent frames include redundancy bits to enable the
receiver to detect remaining errors after forward error correction. With Radio Link
Protocol (RLP), the receiver tests the correctness of the frame and if found not correct,
sends a negative acknowledge message to the sender. The available throughput varies
with the quality of the basic transmission but the quality of the sent data is excellent.
NT service makes it possible to use flexible radio interface data rates. For HSCSD, this
means that reserved radio resources can also vary during a call. Depending on the available resources, the HSCSD connection can occupy channels from one to a user-defined
maximum number of channels. New procedures, resource upgrade and resource down-

DN9813893

Id:0900d8058072ae67
Confidential

Technical description of HSCSD and 14.4 kbit/s Data


Services in BSC

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

grade, are introduced in the BSC. Total radio interface data rates are requested in the
NT service (for example 6.0, 12.0 or 14.5 kbit/s).
MS multislot capability
The number of channels for an HSCSD connection depends on how many channels the
MS is able to receive or transmit and how fast it can perform the adaptations between
operation modes. With the MS multislot capability, the BSC can determine the kind of
HSCSD connections it can allocate for a certain MS. See 3GPP TS 45.002: Multiplexing
and multiple access on the radio path.
The Type 1 MSS need time to adapt between different modes, so they can only either
receive, send, or monitor the neighbor cell fields at a time. Transmitting and receiving in
the same time slot is made possible by shifting the transmitting time slots (see the figure
below).
MS RX

MS TX

Monitor

Figure 2

Double slot operation in the radio interface

The allocated channel may be from non-consecutive time slots as long as the MS multislot capability is taken into account. For type 1 MSS, it means that in practice consecutive time slots almost always have to be allocated. Type 2 MSS can receive and
transmit simultaneously, which makes radio channel allocation more flexible.
Radio interface
In a symmetric HSCSD connection, all the channels transfer data in both uplink and
downlink directions. In order to enable greater data rates for type 1 MSS, it is possible
to transmit in downlink direction with more channels than in uplink direction. Channels
that transmit in both directions are called bi-directional channels and channels that
transmit only in the downlink direction are called uni-directional channels.
At least one bi-directional channel is required for each HSCSD connection. In both symmetric and asymmetric HSCSD configurations one bi-directional channel, the main
channel, carries a Fast Associated Control Channel (FACCH) used for all the signalling
not carried on the Slow Associated Control Channels (SACCH).
Individual signal level and quality reporting is used for all bi-directional channels. The
quality measurements reported on the main channel are based on the worst downlink
quality measured among the main and the uni-directional downlink time slots used.
14.4/14.5 kbit/s channel coding
14.4/14.5 kbit/s is the data rate to be used over one full rate traffic channel (FR TCH).
The 14.4/14.5 kbit/s radio interface rate is achieved by changing the puncturing scheme.
By puncturing, a number of channel coding bits in 22.8 kbit/s frame is reduced by a predetermined rule.
For more information, see 3GPP TS 45.003: Channel Coding.

10

Id:0900d8058072ae67
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Technical description of HSCSD and 14.4 kbit/s Data


Services in BSC

12.0 kbit/s
240 bits

22.
Block code
240 + 4

244 bits

1/2 rate
convol.
code

488 bits

puncturing
488-32

588 bits

puncturing
588-132

456 bits

22.

14.5 kbit/s
290 bits

Block code
290 + 4

Figure 3

Puncturing

294 bits

1/2 rate
convol.
code

8 kbit/s

8 kbit/s
456 bits

14.4/14.5 kbit/s channel coding is more vulnerable to bad quality. For example, if the
current 9.6/12.0 kbit/s service has 90% coverage, the 14.4/14.5 kbit/s service will have
about 84-87% coverage. In the NT service, when the error rate for 14.5 kbit/s is unacceptable, the performance can significantly be improved by automatic link adaptation
(ALA) function. In ALA, channel coding is changed between 14.5 kbit/s and 12.0 kbit/s.
Requirements for HSCSD and 14.4 kbit/s data services

BSC: At least S7-level software is required


Only MSS of phase 2+ which have HSCSD or 14.4 kbit/s data service especially
implemented support HSCSD and 14.4 kbit/s data services.

Restrictions in the use of HSCSD and 14.4 kbit/s data services

HSCSD configurations of up to four FR TCHs are supported.


The automatic link adaptation (ALA) procedure is not used in transparent (T)
service.
4.8/6.0 kbit/s channel coding is not supported in HSCSD connections.
The resource upgrade and downgrade procedures are not used in T service.
Change of main channels during the call is not supported.
Non-consecutive channel allocations are not allocated for T requests.
HSCSD is supported in a PGSM 900 - EGSM 900 BTS where the BCCH is on the
PGSM 900 frequency band only with the Merged PGSM900 and EGSM900 feature.
For detail, see BSS21238: Merged PGSM 900 and EGSM 900.

Maximum HSCSD data rates


Up to four channels can be allocated for one HSCSD connection. 14.4/14.5 kbit/s is the
maximum throughput for one channel. When the HSCSD and 14.4/14.5 kbit/s channel
coding are used together, data rates of 57.6 kbit/s for transparent service and 58 kbit/s
for non-transparent service are achieved.
Interworking with other functionalities

DN9813893

Frequency Hopping
The same frequency hopping sequence is used for all the channels in the HSCSD
configuration. When base band frequency hopping is in use, HSCSD channels in the
same configuration must be allocated from the same hopping group.
For more information, see Frequency Hopping.

Id:0900d8058072ae67
Confidential

11

Technical description of HSCSD and 14.4 kbit/s Data


Services in BSC

12

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Intelligent Underlay-Overlay (IUO)


HSCSD radio resource allocation parameters are defined separately for the regular
layer (see User interface of HSCSD and 14.4 kbit Data Services). Resource
upgrades are not done in the regular frequency area.
In a super-reuse layer, all the channels in HSCSD configuration must fulfil the interference band recommendation defined by the BSC.
For more information on IUO, see Intelligent Underlay-Overlay.
Trunk Reservation
When the trunk reservation algorithm is applied
non-transparent connections are started with one channel and the connection is
upgraded if possible. The trunk reservation algorithm is used for every channel
allocation.
for transparent connections, the parameter number of free traffic
channels (n) is modified:
n = n - number of channels needed for T connection + 1
For more information, see Trunk Reservation.
Queuing
Call setup or handover attempts in queue are preferred to upgrade pending HSCSD
connections in channel allocation algorithm.
Transparent HSCSD connections cannot enter a cell through queueing. Non-transparent HSCSD connections can have the first channel through queueing.
For more information on queuing, see Radio Resource Pre-emption and Queuing.
Pre-emption
Transparent HSCSD connections cannot enter a cell by pre-emption. The preemption handover is not applied to transparent HSCSD connections.
If the target of pre-emption is a non-transparent HSCSD connection with more than
one channel, the handover or release is changed to a resource downgrade.
Non-transparent HSCSD connections can enter a cell by pre-emption with only one
channel.
For more information on pre-emption, see Radio Resource Pre-emption and
Queuing.
Extended Cell Range
HSCSD load is controlled separately in extended and normal areas. For more information, see Extended Cell Range.
FACCH Call Setup
FACCH Call Setup is not made for transparent HSCSD connections requiring more
than one channel. Non-transparent connection is started with one channel and the
possibility to resource upgrade is checked after the assignment.
For more information, see FACCH Call Set-up.
RX Quality and RX Level Statistics
Uni-directional channels are taken into account by modifying the main channel increment step. The main channel increment step is the number of unidirectional
channels plus one. The counter to be incremented is defined by the quality or level
of the main channel.
For more information, see 14 RX Quality Statistics Measurement.
In Call Modification
In call modification is not made for transparent connections requiring or using more
than one channel.
The BSC functions in the following way when the MSC allows changes during a nontransparent connection:

Id:0900d8058072ae67
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Technical description of HSCSD and 14.4 kbit/s Data


Services in BSC

speech to HSCSD: the connection is started with one channel and additional
channels are allocated by the resource upgrade procedure if needed.
HSCSD to speech: the connection is downgraded to one channel before change
of modes.
The BSC functions in the following way when the MSC does not allow changes
during a non-transparent connection:
speech to HSCSD: the connection is made with one channel, resource upgrade
is not possible.
HSCSD to speech: the connection is downgraded to one channel before change
of modes.
Restriction in In Call Modification
In call modification from voice to data or vice-versa is not supported when packet
abis is configured between BSC and BTS. It is also not supported in cases when
AoIP is configured between BSC and MSS and transcoder (TC) resides in BSS.
When MSS sends ASSIGNMENT REQUEST to BSC, the failure cause message for
the different interface combinations is send in the ASSIGNMENT FAILURE message
to MSS as given in Table 2.
Abis type configured
between BSC and BTS

A interface configured
between BSC and MSS

Failure cause message

Legacy Abis

AoIP TC in BSS

Requested
transcoding/rate
adaption
unavailable

Packet Abis

AoIP TC in BSS

Requested
transcoding/rate
adaption
unavailable

Packet Abis

AoTDM or Legacy A

Requested
terrestrial
resource
unavailable

Table 2

DN9813893

Different failure causes scenarios for in call modification

traffic reason handover


Traffic reason handovers are made only to single slot connections and HSCSD connections requiring only one channel.
For more information, see Traffic Reason Handover in BSC.
Power optimization in handover
Optimized power is defined by the channel triggering the handover and it is used for
all time slots in HSCSD configuration.
For more information on power optimization in handover, see RF Power Control and
Handover Algorithm and Intelligent Underlay-Overlay.
Interference band recommendation
The interference band recommendation is defined by the channel triggering the
handover and it is used for all time slots in HSCSD time slot allocations.
For more information on interference band recommendation, see
Radio Resource Pre-emption and Queuing

Id:0900d8058072ae67
Confidential

13

Technical description of HSCSD and 14.4 kbit/s Data


Services in BSC

14

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

RF Power Control and Handover Algorithm


Intelligent Underlay-Overlay.
Dual band network operation
System information messages Sys_Info_5, Sys_Info_5bis, Sys_Info_5ter and
Sys_Info_6 are sent only in the main channel.
For more information, see Dual Band Network Operation.
TRX locking with forced HO and save calls by forced HO prior to cell recovery
Handover is started only in the main HSCSD channel. The subchannels are then set
free along with the main channel.
For more information on TRX locking with forced handover (HO) and save calls by
forced HO prior to cell recovery, see RF Power Control and Handover Algorithm.
RXLev Min Access
If RXLev Min Access is activated in the BSC, the C/N based method for an HSCSD
or single slot data call is used to determine whether TCH can be allocated according
to the downlink RX level measured by MS.
Different call types (EFR/FR, HR, AMR FR, AMR HR, and 14.4 data) require separately set C/N threshold values. These values determine the serving rxlevel needed
for a data call.
The EFR/FR C/N threshold value is used for 4.8 kbit/s and 9.6 kbit/s. The 14.4 C/N
threshold value is used for 14.4 kbit/s coding.
In case of Non-Transparent HSCSD or single slot call, the following rules are valid
when selecting appropriate coding for channel allocation.
Requested data rate and MS capabilities determine which codings are appropriate (and in case of HSCSD data call; how many TSLs are needed).
Available appropriate coding fulfilling the C/N threshold value is selected for
coding in channel allocation.
If the appropriate available coding does not fulfil the required C/N threshold in a
Transparent HSCSD or single slot call, the data call request is rejected.
For more information, see RXLev Min Access in Radio Channel Allocation.
BSS21238: Merged PGSM 900 and EGSM 900
HSCSD is supported in a PGSM 900 - EGSM 900 BTS where the BCCH is on the
PGSM 900 frequency band only with the Merged PGSM900 and EGSM900 feature.
For detail, see BSS21238: Merged PGSM 900 and EGSM 900.
BSS21341: A over IP, Transcoder in BSS
HSCSD requires presence of TCSM entity in GERAN, that is, HSCSD is supported
in case of A over IP when the transcoder is located in BSS. It requires the following
circuit pools to be defined to Ater interface for multislot cases of two and four slot
pools:
Pool no 89 for 16kbps and 32 kbps HSCSD calls
Pool no 90 for 64 kbps HSCSD calls.
Pool no 90 is also used for 32kbps call HSCSD class which can be upgraded to a
64kbps call. The BSC find the Ater resource to support HSCSD calls. It also
supports 16, 32 and 64kbit/s circuits in the Ater interface. HSCSD call requires the
Rate Adaptation unit in the TRAU. TRAU is available only in the PCM over IP (PI) or
PCM over TDM (PT) interface, hence for HSCSD calls only PI or PT A-Interface is
used.
BSS21454: Packet Abis over IP/Ethernet and BSS21440: Packet Abis over TDM
When either packet Abis over TDM or packet Abis over Ethernet is used, HSCSD is
supported only with the AoIP (TC in BSS) and AoTDM (G.711), A interfaces options.
Data transfer at user plane between BTS and ETPT/E in BSC happens via UDP-

Id:0900d8058072ae67
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Technical description of HSCSD and 14.4 kbit/s Data


Services in BSC

Radio Channel-ports of TCHs. Each TCH of a HSCSD call has its own port. UDPRadio Channel-port identifies the radio timeslot and TRX of the data in multiplexed
Abis u-plane UDP packet. In HSCSD call setup and channel configuration upgrade
u-plane resources are allocated form ETPT/E and group switch. During HSCSD
connection ETPT/E converts Abis u-plane packets to TRAU frames and sends them
to Ater via group switch. ETPT/E also receives TRAU frames from group switch and
converts them to Abis u-plane packets and sends them to BTS via UDP-Radio
Channel-ports of the HSCSD connection.

DN9813893

Id:0900d8058072ae67
Confidential

15

Functionality of HSCSD and 14.4 kbit/s Data Services


in BSC

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

3 Functionality of HSCSD and 14.4 kbit/s Data


Services in BSC
The following topics are covered below:

HSCSD call setup


Radio resource allocation
Channel configuration change
The A and Ater interfaces
Power control and handover algorithm in HSCSD and 14.4/14.5 kbit/s connections
Handover signalling
Start of ciphering in HSCSD
HSCSD load control

HSCSD call setup


Parameters for an HSCSD call are negotiated by the MS and the MSC in the call setup
phase. The BSC notices the HSCSD call in a Channel Type information element (IE) in
an ASSIGNMENT REQUEST message received from the MSC. The channel type IE
defines the requested data service type (Non-transparent/transparent), a required total
data rate, maximum number of full rate traffic channels (FR TCH) and supported
channel codings. The MS sends its multislot class information to the network using the
early classmark sending procedure. These are the parameters for channel allocation
procedure.
A separate channel activation is applied for all the HSCSD channels. One of the bi-directional channels is a main signalling link which carries an FACCH used for all signalling
not carried on the SACCH(s). The selected channel configuration is forwarded to the MS
in an ASSIGNMENT COMMAND message. The MSC is informed of the chosen HSCSD
configuration in an ASSIGNMENT COMPLETE message.
Radio resource allocation
An HSCSD call uses a multislot configuration consisting of one or several FR TCH(s).
HSCSD parameters for channel allocation are

required total radio interface data rate (Non-transparent service)


requested radio interface user rate (Transparent service)
maximum number of sub-channels
service (Transparent/Non-transparent)
MS multislot capability
allowed radio interface rates per channel.

The BSC receives the parameters in either the ASSIGNMENT REQUEST or the
HANDOVER REQUEST message. An exception is the MS multislot class, which is not
a part of the ASSIGNMENT REQUEST message. In a call setup, the MS informs its multislot class with the CLASSMARK CHANGE message before the assignment.
The BSC tries to allocate as many channels as needed to fulfil the required total data
rate. The fastest appropriate data rate per channel is used. For example, when the
required data rate for transparent (T) service is 14.4 kbit/s, one 14.4 kbit/s channel is
chosen. If only 9.6 kbit/s channel coding is supported, two 9.6 kbit/s channels are allocated, resulting in 19.2 kbit/s total data rate. In T service, extra data bits are padded with

16

Id:0900d80580590c87
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Functionality of HSCSD and 14.4 kbit/s Data Services


in BSC

fill by TAF or IWF respectively in MS or MSC. If total data rate 9.6 or 19.2 kbit/s for T
service is requested, 9.6 kbit/s channel coding is used.
Channels in an HSCSD connection must be allocated from the same transceiver (TRX).
The MS multislot capability determines how far the allocated time slots can be from each
other. The number of channels for HSCSD connection at the first allocation after request
or during the connection by downgrade procedure can be controlled with parameterisation. For more information, see HSCSD load control. In the downgrade procedure, part
of the channels of the HSCSD connection are released for other use, while the HSCSD
connection is maintained with a reduced total data rate.
HSCSD service at the call setup or during the connection can be improved with directed
retry or upgrade pending procedures. In the upgrade procedure, new channels are activated and added to a current HSCSD connection, thus increasing the total data rate.
For more information on directed retry, see Directed Retry in BSC.
For transparent HSCSD connections, a certain number of FR TCHs must be allocated
to meet the requested total data rate. If there are not enough channels in a cell, directed
retry (DR) procedure can be used in call setup. If the target cell in a handover cannot
provide the requested total data rate, the DR attempt is terminated and the call is
released.
A non-transparent HSCSD call can be started with fewer FR TCHs than required. At
least one channel is allocated for the HSCSD connection if there are free resources
available in a cell. The upgrade pending procedure is started if the required total radio
interface data rate cannot be fulfilled at the initial channel allocation or if the number of
channels is decreased during the connection. Pending is maintained until the required
data rate is reached.
Channel allocation parameters may change during a non-transparent HSCSD call, for
example, the user may change the required total data rate. The MSC indicates the
change by sending an ASSIGNMENT REQUEST message to the BSC. If there is a contradiction between the new parameters and the used radio interface resources, a
resource downgrade is needed.
In pre-emption, a higher priority connection can occupy channel(s) from lower priority
connection(s). The pre-emption capability indicator for the pre-emptive connection and
the pre-emption vulnerability indicator for the call to be handed over or released must
allow the pre-emption. An HSCSD call with a lower priority level can also be the target
of a pre-emption. The resource downgrade procedure can be used for non-transparent
connections using more than one channel.
For more information on pre-emption, see Radio Resource Pre-emption and Queuing.
Channel configuration change
The BSC changes the number of used time slots in a multislot configuration with
resource upgrade and downgrade procedures. The mode modify procedure can be
used to change the channel coding of used channels.
The BSC configures BTS resources. The configuration determines the time slots used
in uplink, the time slots used in downlink and which mode they use. When new channels
are allocated, the BSC sends a CHANNEL ACTIVATION message. The BSC sends a
MODE MODIFY message when the channel coding of the current channel is changed
or if transfer mode is changed between the uni-directional and bi-directional modes.
The CONFIGURATION CHANGE COMMAND message commands the MS to use a
new channel configuration. If the command instructs the MS to use a configuration it

DN9813893

Id:0900d80580590c87
Confidential

17

Functionality of HSCSD and 14.4 kbit/s Data Services


in BSC

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

does not support, it sends a CONFIGURATION CHANGE REJECT message with the
cause 'channel mode unacceptable'.
A CHANNEL MODE MODIFY or CONFIGURATION CHANGE COMMAND message is
used when a new channel mode is used for currently allocated channels.
After acknowledgement from the MS, the BSC sends a HANDOVER PERFORMED
message to the MSC containing the new channel configuration.
The A and Ater interfaces
There are circuit pools (CIP) to support HSCSD connections on the A interface. A circuit
pool is a group of circuits supporting the same channel type. Supported pools can
handle all the existing connection types (half rate (HR), full rate (FR), enhanced full rate
(EFR), FR data, adaptive multi-rate (AMR)) with either HSCSD max. 2 * FR data (HS2)
or HSCSD max. 4 * FR data (HS4) or 14.4/14.5 kbit/s channel coding. HSCSD pools are
supported with or without 14.4/14.5 kbit/s. See also HSCSD and 14.4 kbit/s Data
Services effects on A interface procedures.
In HS4, a whole Ater PCM time slot is reserved for one connection. The reserved FR
TCHs are connected to consecutive Ater subchannels. An exception to this is downgrade which can lead to the non-consecutive switching of the subchannel. In the subsequent upgrade, the lowest possible subchannel is switched (see the figure below). See
also 3GPP TS 48.020: Rate adaption on the Base Station System - Mobile-services
Switching Centre (BSS-MSC) interface.
3 TCH/F HSCSD connection
Radio i/f

Ater i/f

0 1 2 3 4 5 6 7

0 1 2 3 4 5 6 7

- - S M S - - -

3 3 2 2 4 4 - -

Resource downgrade to 2 TCH/F


0 1 2 3 4 5 6 7

0 1 2 3 4 5 6 7

- - - M S - - -

3 3 - - 4 4 - -

Resource upgrade to 3 TCH/F


0 1 2 3 4 5 6 7

0 1 2 3 4 5 6 7

- - - M S S - -

3 3 5 5 4 4 - -

M = HSCSD main
channel
S = HSCSD sub
channel

2-5 = Abis
TSL
numbers

Figure 4

Example of Ater switching

Transcoder PCMs can be defined in Ater PCM in any order. All time slots in the last connected transcoder PCM cannot be allocated on Ater in certain combinations, because
this would lead to ineffective use of hardware.

18

Id:0900d80580590c87
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Abis
interface

Functionality of HSCSD and 14.4 kbit/s Data Services


in BSC

Ater
interface

A
interface
PCM 1

BTS

MSC

TCSM

BSC
ET

PCM 2
GSWB

ET
PCM 3
PCM 4

BTS
PCM 1
TCSM
ET

PCM 2

BTS

PCM 1
ET

TCSM

ET_PCM

Figure 5

DN9813893

transcoder PCM

Transmission example

Id:0900d80580590c87
Confidential

19

Functionality of HSCSD and 14.4 kbit/s Data Services


in BSC

TSL

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

00
01
02

TSL 0
LAP-D
4

1
5

2
6

3
7

03

10

11

04

12

13

14

15

05

16

17

18

19

06

20

21

22

23

07

24

25

26

27

08

28

29

30

31

09

1
5

2
6

3
7

10
11

10

11

12

12

13

14

15

13

16

17

18

19

14

20

21

22

23

15

24

25

26

27

16

28

29

30

31

17
18

1
5

2
6

3
7

19

10

11

20

12

13

14

15

21

16

17

18

19

22

20

21

22

23

23

24

25

26

27

24

28

29

30

31

25

26

27

28

5
7

29

30

10

11

31

12

13

1st transcoder PCM

2nd transcoder PCM

3rd transcoder PCM

4th transcoder PCM


(partial)

In TCSM, TSLs 2...31 can be through connected to transcoder PCM TSLs 1...31.
TCSM allows the last transcoder PCM to be partial.

Figure 6

20

Ater TSL allocation example

Id:0900d80580590c87
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

TSL
00
01

Functionality of HSCSD and 14.4 kbit/s Data Services


in BSC

LAP-D

3
4
TSL 0

02

03

04

05

06

10

11

07

12

13

08

14

15

09

16

17

10

18

19

11

20

21

12

22

23

13

24

25

14

26

27

15

28

29

16

30

31

17

18

19

20

21

22

23

24

25

26

10

27

11

28

12

29

13

30

14

31

15

1st transcoder PCM

2nd transcoder PCM


(partial)

In TCSM, TSLs 2...31 can be through connected to transcoder PCM TSLs 1...31.
TCSM allows the last transcoder PCM to be partial.

Figure 7

DN9813893

Ater TSL allocation example

Id:0900d80580590c87
Confidential

21

Functionality of HSCSD and 14.4 kbit/s Data Services


in BSC

TSL
00
01

LAP-D

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

3
4
TSL 0
-

5
-

02

03

04

05

06

07

08

09

10

10

11

11

12

12

13

13

14

14

15

15

16

16

17

17

18

18

19

19

20

20

21

21

22

22

23

23

24

24

25

25

26

26

27

27

28

28

29

29

30

30

31

31

7
-

1st transcoder PCM

In TCSM, TSLs 2...31 can be through connected to transcoder


PCM TSLs 1...31.TCSM allows the last transcoder PCM to be partial.

Figure 8

Ater TSL allocation example

Power control and handover algorithm in HSCSD and 14.4/14.5 kbit/s connections

22

Measurement reporting
The signal level and quality are reported by every bi-directional channel in an
HSCSD multislot call. The MS copies the neighbouring cell's measurement reports
to every bi-directional channel. Uni-directional channels cannot report their measurements because they do not have an uplink SACCH where the measurement
reports are sent. The quality measurement reported on the main channel is the worst
quality measured among the main and the uni-directional downlink channel(s) used.
See 3GPP TS 45.008: Radio subsystem link control.

Id:0900d80580590c87
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

DN9813893

Functionality of HSCSD and 14.4 kbit/s Data Services


in BSC

Radio link timeout


Only the main SACCH is used for determining the Base Station Subsystem (BSS)
radio link failure.
Power control
Power control is made individually for every bi-directional channel. The MS neglects
power control information on a unidirectional channel. The BTS is commanded to
use the same power in uni-directional channels as in the main channel. Power
control is not made during automatic link adaptation signalling.
Automatic link adaptation (ALA)
New threshold parameters are needed to trigger the ALA. In ALA, channel coding is
changed during the call according to the uplink and downlink signal quality and the
MS and BTS powers. On the edge of a cell, for example, the channel coding can
drop from 14.5 kbit/s to 12.0 kbit/s. Channel coding is changed for all the channels
in a multislot configuration. In NT transfer mode, the dropping of channel coding can
lead to an increase of user data rate when the number of retransmissions of data
bursts decreases. The ALA is also used in increasing channel coding from 12.0
kbit/s to 14.5 kbit/s. The ALA procedure is used only in the NT service.
The channel coding change in the BTS is made using a MODE MODIFY message.
Radio resources may be adjusted to meet the required total radio interface rate, if
possible by the maximum allowed number of channels. If new channels are allocated or old channels are released, respectively either the resource upgrade or the
downgrade procedure is used. In a single slot data connection, a CHANNEL MODE
MODIFY message is used to command the MS to use the new channel coding. In a
multislot connection, a CONFIGURATION CHANGE COMMAND message is used.
Handover
Any bi-directional HSCSD channel can trigger a handover. ALA is prohibited during
handover signalling. All existing handover reasons are supported. See RF Power
Control and Handover Algorithm .
14.4/14.5 kbit/s connection power control and automatic link adaptation
RX_QUAL reported by the MS and the BTS indicates the quality of the sent frame,
not the performance of the user data. The threshold for power control represents the
predicted border of the acceptable user data performance for the speech or 9.6/12.0
kbit/s data. This is not adequate for the 14.4/14.5 kbit/s user data because 14.4/14.5
kbit/s channel coding can tolerate less errors. To maintain the 14.4/14.5 kbit/s performance adequate, the RX_QUAL needs to be kept higher and therefore the power
increase must be started at a higher quality for 14.4/14.5 kbit/s calls than for other
calls.
The threshold parameter pc lower thresholds qual144 Rx level (LQR),
Px (LQP), Nx (LQN) has been defined for triggering downlink and uplink power
increase for 14.4/14.5 kbit/s connection. Its value should be set to higher quality than
the ordinary power increase lower thresholds.
The parameter power limit ALA (ALIM) determines the MS and BTS power
levels where the channel coding is changed between 14.5 kbit/s and 12 kbit/s in the
NT service. The power level is identified as an attenuation from the maximum
allowed power of the MS/BTS. BTS power control is taken into account only if it is
enabled. ALA is possible when
ALA enabled (AENA) parameter enables ALA in the cell
the connection uses either 14.5 kbit/s or 12.0 kbit/s channel coding
14.5 kbit/s and 12.0 kbit/s channel codings are both allowed for the connection

Id:0900d80580590c87
Confidential

23

Functionality of HSCSD and 14.4 kbit/s Data Services


in BSC

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

the A interface circuit pool used supports 14.5 kbit/s channel coding.
For the MS, the power limit for ALA is defined as
MS_ALA_PWR_LIMIT = MsTxPwrMax - ALIM
The BTS power control range is defined by the following parameters, BS TX pwr
max (PMAX1) and BS TX pwr min (PMIN). The BTS power limit for ALA is
defined as
BTS_ALA_PWR_LIMIT = PMAX - ALIM
When pc lower thresholds qual144 Rx level (LQR), Px (LQP), Nx
(LQN) triggers,
if either the BTS or the MS power value is higher than the power limit, channel
coding is changed to 12.0 kbit/s. After that, RX_QUAL is not monitored to pc
lower thresholds qual144 Rx level (LQR), Px (LQP), Nx (LQN).
if BTS and MS power values are below their ALA limit powers, the power of the
triggered link is increased.
When pc upper thresholds qual dl Rx qual (UDR), Px (UDP), Nx
(UDN) or pc upper thresholds qual ul Rx qual (UUR), Px (UUP), Nx
(UUN) triggers,
the triggered link power is decreased
if channel coding is 12.0 kbit/s and both BTS and MS power values are both
below their ALA power limits, channel coding is changed to 14.5 kbit/s.
The parameter min int between ALA (AMIN) defines an interval that must be
between two consecutive ALA procedures. The interval is, however, neglected if the
power has been increased to its maximum value. If ALA from 14.5 kbit/s to 12.0
kbit/s is not made due to timer parameter, the triggered link power is increased.
The parameter ALA enabled (AENA) is used to switch automatic link adaption
function on and off cell by cell.
14.4/14.5 kbit/s connection power control and automatic link adaptation parameters
can be handled by the Power Control Parameter Handling MML commands.
Handover signalling
The handover is simultaneous for all radio interface time slots. All handover types:
internal intra-cell, internal inter-cell and external handover are supported.
A separate channel activation for all the HSCSD channels is carried out before the
selected channel configuration is forwarded to the mobile station in either the ASSIGNMENT COMMAND (intra-cell handover) or the HANDOVER COMMAND. At handover
completion, the BSC signals the new HSCSD configuration to the MSC.
Channel coding and the number of channels may change during handover unless
changes after the first allocation are denied in the request. 14.4/14.5 kbit/s is used when
it is supported by the BSS. In transparent service, the total data rate may not change
during the call. In the non-transparent service, the number of channels and channel
coding may change during handover depending on the traffic situation in the target
BTSs.
For more information, see Handover Signalling in BSC.
Start of ciphering in HSCSD
The main signalling link controls the encryption procedure in order to start the ciphering.
The encryption information for an additional HSCSD channel is forwarded to the corresponding FR TCH during initial channel activation or later in the MODE MODIFY

24

Id:0900d80580590c87
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Functionality of HSCSD and 14.4 kbit/s Data Services


in BSC

message. The change of the ciphering modes for separate channels within the HSCSD
connection may not be perfectly synchronised.
HSCSD load control
BTS object parameters are used for HSCSD load control.
With the parameter HSCSD TCH capacity minimum (HTM), a certain proportion of
the cell capacity is offered for HSCSD use. In a low traffic load situation, the HSCSD
calls can have more traffic channels (TCHs) than indicated by the parameter. Also,
minimum HSCSD capacity may not be reached due to single slot traffic congestion.
In a highly loaded cell, it is possible to restrict the allocation of multislot configurations
by the parameter HSCSD cell load upper limit (HCU). When the traffic load
increases over the parameter value, each new HSCSD call is started with only one
channel. Exceptions to this rule are:

minimum HSCSD capacity of the cell is not completely in use


service request type is transparent.

Resource upgrades are not made under multislot limitation time. As long as the cell load
is greater than HSCSD cell load upper limit (HCU) value and the minimum
HSCSD capacity is in use, the HSCSD capacity is reduced by downgrading one of the
HSCSD connections for every incoming call.
Channels for transparent HSCSD request are not reserved if it leads to a multislot limitation situation.
In a state in which multislot allocation and HSCSD resource upgrades are allowed, the
following takes place, depending on the situation:

if either the HSCSD load is more than HSCSD TCH capacity minimum (HTM)
or the total cell load is more than UpperLimitCellLoadHSCSD, it causes no
change in state
if the HSCSD load is more than HSCSD TCH capacity minimum (HTM) and the
total cell load is more than HSCSD cell load upper limit (HCU) HSCSD
resource upgrades and multislot allocations are denied and one resource downgrade is made for one of the HSCSD connections for every new channel allocation

In a state in which multislot allocation and resource upgrades are denied and downgrade
for every new channel allocation is done, the following happens depending on the situation:

if the HSCSD load is less than HSCSD TCH capacity minimum (HTM) or the
total cell load is less than HSCSD cell load upper limit (HCU), multislot
allocation and resource upgrade are still denied but HSCSD resource downgrade for
every new allocation is stopped.
if the total cell load is less than HSCSD cell load lower limit (HCL) multislot
allocation and resource upgrades are allowed.

Resource upgrades are denied in the Intelligent Underlay-Overlay (IUO) regular frequency area. The parameter HSCSD regular cell load upper limit (HRCU)
determines the number of occupied TCHs in the IUO cell regular frequency area where
single slot allocation is started. When the regular area load is under the threshold, multislot allocations are possible. When the threshold is exceeded, multislot allocations are
denied and one resource downgrade is made for one of the HSCSD connections for
every new channel allocation.

DN9813893

Id:0900d80580590c87
Confidential

25

Functionality of HSCSD and 14.4 kbit/s Data Services


in BSC

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

In super-reuse frequencies, the HSCSD load is controlled with the parameters HSCSD
TCH capacity minimum (HTM), HSCSD cell load upper limit (HCU) and
HSCSD cell load lower limit (HCL) as in normal cells. The number of TCHs
defined by the parameters is counted from the whole cell resources.
The parameter HSCSD upgrade guard time (HUT) determines a guard time
between two consecutive resource upgrades. However, if the data rate can be
increased significantly, the resource upgrade procedure can be made before the end of
the guard time. The parameter HSCSD upgrade gain (HUG) determines the needed
gain of the increased number of used channels before upgrade during guard time can
be made. For example, an upgrade from two to three channels gives a 50% gain in data
rate and upgrade from one to two gives a 100% gain.
The number of time slots to be released in the downgrade is defined by the parameter
HSCSD minimum exhaust (HME).
The parameter HSCSD downgrade guard time (HDT) determines a guard time
between two consecutive resource downgrades. When the downgrade guard timer
expires and the cell is totally congested, the downgrade is carried out if there is a call in
any of the queues.
The HSCSD load control parameters can be handled by the Base Transceiver Station
Handling MML commands.

26

Id:0900d80580590c87
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

HSCSD and 14.4 kbit/s Data Services effects on interface procedures

4 HSCSD and 14.4 kbit/s Data Services effects


on interface procedures
4.1

HSCSD and 14.4 kbit/s Data Services effects on A interface


procedures
Early classmark sending procedure
The MS multislot class indication bit and MS multislot class (5 bits) indicate the DX MSC
(MSC) the MS multislot capability with the MS Classmark 3 information element in the
Classmark Update message. The Early Classmark Sending procedure must be used to
allow HSCSD connections.
Assignment and external handover procedures
The messages ASSIGNMENT REQUEST and HANDOVER REQUEST contain the
mandatory information element Channel Type which defines the requested resources.
8

Element Identifier

octet 1

Length

octet 2

Spare

Speech / Data ind

octet 3

Channel Rate and Type

octet 4

Speech coding algorithm /


Data Rate + Transparency ind

octet 5

Figure 9

Channel type information element

With the Field Speech/data indicator, the MSC defines whether a speech or a data call
is requested. In the case of a data call, Channel Rate and Type defines whether a single
slot data or multislot data call is requested. When multislot data is requested, the
maximum number of traffic channels and the possibility to change either the number of
traffic channels or the used radio interface rate per channel after the first channel allocation are indicated. With the field Data Rate/Transparency Indicator the MSC defines
whether a transparent or non-transparent service and which data rate is requested and
what radio interface rates per channel are allowed to be used.
8

ext

T/NT

ext

Figure 10

1
octet 5

Rate
spare

allowed
r i/f rate

octet 5a

Coding of data rate/transparency indicator field

The field Rate in Data Rate/Transparency indicator shows

the radio interface data rate in a single slot non-transparent request


the data rate in a single slot transparent request
the required total radio interface data rate in a non-transparent multislot request
the requested radio interface user rate in a transparent multislot request.

The extension field Allowed Radio Interface Rate is optional and it indicates

DN9813893

other possible data rates allowed in a single slot non-transparent request

Id:0900d80580735031
Confidential

27

HSCSD and 14.4 kbit/s Data Services effects on interface procedures

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

the allowed radio interface data rate per channel in a multislot request.

The allowed radio interface rate extension field is not used in single slot transparent
requests. If the extension is not included in the multislot request, the radio interface rate
of 12.0/9.6 kbit/s is used.
In the external handover, the MSC informs the BSC of the MS multislot capability in the
MS multislot class indication bit and the MS multislot class (5 bits) in the MS Classmark
3 information element in the HANDOVER REQUEST message.
The BSC informs the MSC of the selected radio interface rate per channel and the
number of allocated traffic channels in a Chosen Channel information element which is
included in the messages ASSIGNMENT COMPLETE and HANDOVER REQUEST
ACKNOWLEDGE. The information element must always be used with multislot calls
and with single slot calls when the BSC has chosen the used radio interface rate.
Messages HANDOVER REQUIRED and HANDOVER REQUEST can include the
optional information element Current Channel. It indicates the used radio interface rate
per channel and the number of allocated channels.
Both resource request messages include the Circuit Identity Code (CIC) of the A interface circuit, which the BSC can use to find out the transcoding properties. When there
are several circuit pools defined on the A interface, the resource request acknowledge
messages include an information element Circuit Pool, which indicates the circuit pool
number that has been allocated for the connection.
When the BSC rejects the resource request because the pool implied by the CIC does
not support any of the data functionalities indicated in the Channel Type, the cause
value Circuit Pool Mismatch is returned to the MSC in the messages ASSIGNMENT
FAILURE or HANDOVER FAILURE.
In both of these two cases, the Circuit Pool List information element will be included in
the failure message. The Circuit Pool List presents the pools in the order of preference
that the BSC wishes the A interface circuit to be allocated. The circuit pools are switched
as seldom as possible and only existing A interface pools are represented in the list.
If Reversed Hunting is active in the BSC, the A interface circuit is allocated by the BSC.
The changing of the circuit in the case that the initially selected circuit is not suitable is
also handled by the BSC and thus the MSC is not involved.
ETSI specifications (see 3GPP TS 48.008: MSC-BSS Interface, Layer 3 Specification)
define 50 circuit pools supporting different sets of speech and data codings.
The transcoder and submultiplexer TCSM2 supports six circuit types:
A

FR speech version 1
FR speech version 2
FR data (14.5, 12, 6 kbit/s)

HR speech version 1

HR speech version 1
FR speech version 1
FR speech version 2
FR data (14.5, 12, 6 kbit/s)

28

Id:0900d80580735031
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

HSCSD and 14.4 kbit/s Data Services effects on interface procedures

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)

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).

HR speech version 3 (AMR)


FR speech version 3 (AMR)

The transcoder and submultiplexer TCSM3i/Combi supports three circuit types:


G

FR speech version 1
FR speech version 2 (EFR)
FR speech version 3 (AMR)
FR speech version 5 (AMR-WB)
HR speech version 1
HR speech version 3 (AMR)
FR data (14.5, 12, 6, 3.5 kbit/s)

FR speech version 1
FR speech version 2 (EFR)
FR speech version 3 (AMR)
FR speech version 5 (AMR-WB)
HR speech version 1
HR speech version 3 (AMR)
FR data (14.5, 12, 6, 3.5 kbit/s)
HSCSD max 2 x FR data (14.5, 12, 6 kbit/s)

FR speech version 1
FR speech version 2 (EFR)
FR speech version 3 (AMR)
FR speech version 5 (AMR-WB)
HR speech version 1
HR speech version 3 (AMR)

DN9813893

Id:0900d80580735031
Confidential

29

HSCSD and 14.4 kbit/s Data Services effects on interface procedures

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

FR data (14.5, 12, 6, 3.5 kbit/s)


HSCSD max 4 x FR data (14.5, 12, 6 kbit/s)
The BSC supports the following A interface circuit pools (for more information on circuit
pools, see 3GPP TS 48.008: MSC-BSS Interface, Layer 3 Specification):
1

FR speech version 1
FR data (12, 6, 3.6 kbit/s)

HR speech version 1
(only supported by TCSM2)

FR speech version 1
FR data (12, 6, 3.6 kbit/s)
HR speech version 1

FR speech version 1
FR speech version 2 (EFR)
FR data (12, 6, 3.6 kbit/s)

FR speech version 1
FR speech version 2 (EFR)
FR data (12, 6, 3.6 kbit/s)
HR speech version 1.

10

FR speech version 1
FR speech version 2 (EFR)
FR data (12, 6, 3.6 kbit/s)
HR speech version 1
HSCSD max 2 * FR data (12, 6 kbit/s)

13

FR speech version 1
FR speech version 2 (EFR)
FR data (12, 6, 3.6 kbit/s)
HR speech version 1
HSCSD max 4 * FR data (12, 6 kbit/s)

20

FR speech version 1
FR speech version 2 (EFR)
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1

30

Id:0900d80580735031
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

21

HSCSD and 14.4 kbit/s Data Services effects on interface procedures

FR speech version 1
FR speech version 2 (EFR)
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
HSCSD max 2 * FR data (14.5, 12, 6 kbit/s)

22

FR speech version 1
FR speech version 2 (EFR)
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
HSCSD max 4 * FR data (14.5, 12, 6 kbit/s)

23

FR speech version 3 (AMR)


HR speech version 3 (AMR)

28

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)
(only supported by TCSM3i/Combi)

32

FR speech version 1
FR speech version 2 (EFR)
FR speech version 3 (AMR)
HR speech version 1
HR speech version 3 (AMR)
HSCSD max 4 x FR data (14.5, 12, 6 kbit/s)
(only supported by TCSM3i/Combi)

37

FR speech version 3
FR speech version 4
FR speech version 5 (AMR-WB)
HR speech version 3
HR speech version 4
HR speech version 6
(only supported by TCSM3i/Combi)

DN9813893

Id:0900d80580735031
Confidential

31

HSCSD and 14.4 kbit/s Data Services effects on interface procedures

38

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

FR speech version 1
FR speech version 2
FR speech version 3
FR speech version 4
FR speech version 5 (AMR-WB)
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 3
HR speech version 4
HR speech version 6
(only supported by TCSM3i/Combi)

40

FR speech version 1
FR speech version 2
FR speech version 3
FR speech version 4
FR speech version 5 (AMR-WB)
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
HR speech version 3
HR speech version 4
HR speech version 6
HR data (6, 3.6 kbit/s)
HSCSD max 4 x FR data (14.5, 12, 6 kbit/s)
EDGE max 2 x FR data (29.0 kbit/s)
EDGE FR data (43.5 kbit/s)
(only supported by TCSM3i/Combi)

BSC internal handover and configuration change procedures


After the BSC internal handover or configuration change procedure, the BSC informs
the MSC of the new radio interface rate per channel and the number of allocated traffic
channels. This is included in the Chosen Channel information element in a HANDOVER
PERFORMED message.

4.2

HSCSD and 14.4 kbit/s Data Services effects on the Abis


interface procedures
Channel activation procedure
The Channel Activation Procedure can be used for channel activations in the call setup
or handover phases and for the Resource Upgrade Procedure during an HSCSD connection to add new full rate traffic channels to an HSCSD configuration. A separate
channel activation is performed for each subchannel in the HSCSD configuration.

32

Id:0900d80580735031
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

HSCSD and 14.4 kbit/s Data Services effects on interface procedures

For the main HSCSD channel, activation types for intra-cell and inter-cell channel
change are used (activation for assignment, activation for synchronous handover or
activation for asynchronous handover) depending on the reason why the main channel
is activated. Additional HSCSD channels are activated as related to multislot configuration.
A Channel Mode defines the characteristics of the activated channel. A full rate TCH
channel Bm is used in the field Channel Rate and Type for single slot full rate data call.
The Channel Rate and Type for an HSCSD channel is either

full rate TCH channel bi-directional Bm


multislot configuration or
full rate TCH channel uni-directional downlink Bm, Multislot configuration.

In Data Rate + Transparency indicator, there is a radio interface data rate 14.5 kbit/s for
non-transparent full rate data channels and a data rate 14.4 kbit/s for transparent full
rate data channels.
Mode modify procedure
The Mode Modify Procedure can be used during a data call to

change the radio interface data rate


change the uni/bi-directionality of an HSCSD channel
start ciphering in an additional HSCSD channel or
change the channel to speech mode.

Full rate speech channels can be changed into data mode with the Mode Modify Procedure.
The Channel mode determines the new characteristics of the channel. Encryption information is a new optional information element in the MODE MODIFY message and it is
included in the message if the ciphering key is to be applied.

4.3

HSCSD and 14.4 kbit/s Data Services effects on Radio


interface procedures
Early classmark sending procedure
The MS multislot class indication bit and the MS multislot class (5 bits) are used by the
MS to indicate to the MS multislot capability to the network. The fields are part of the
Mobile Station Classmark 3 information element in the CLASSMARK CHANGE
message. The Early Classmark Sending procedure must be used for allowing HSCSD
connections.
Assignment and handover procedures
The ASSIGNMENT COMMAND and HANDOVER COMMAND messages indicate the
MS the initial call type and channel configuration. In the radio interface, there is a data
channel mode for 14.5 kbit/s radio interface rate.
The HSCSD multislot configuration can be indicated to the MS either in the Channel
Description 2 or Multislot allocation information element. The former is used instead of
the Channel Description information element and it has exactly the same format. The
use of the Channel description 2 IE is possible when

DN9813893

Id:0900d80580735031
Confidential

33

HSCSD and 14.4 kbit/s Data Services effects on interface procedures

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

the symmetry of all the additional HSCSD channels is equal, that is, all the additional
HSCSD channels are uni-directional or all the additional HSCSD channels are bidirectional.
channels are allocated from the consecutive time slots
the position of the HSCSD main channel is correct. If there is one additional HSCSD
channel, the main channel is in the greater time slot position. If there are two or more
additional channels, the main channel is in the second greatest time slot number.

The Multislot allocation IE is used when it is impossible to use the Channel Description
2. The use of the multislot Allocation IE is indicated in the Channel Description IE field
Channel Type and TDMA Offset. The Multislot Allocation IE defines a bit map of additional channels of multislot configuration in uplink and downlink directions. If the uplink
bit map is not included in the element, the time slots indicated by the downlink bit map
are allocated in both downlink and uplink directions.
Configuration change procedures
Three messages are related to HSCSD in the Configuration Change Procedure:

The CONFIGURATION CHANGE COMMAND is sent on the main Dedicated


Control Channel (DCCH) from the network to the MS to change the channel configuration of a multislot configuration
The CONFIGURATION CHANGE ACKNOWLEDGE message is sent on the main
DCCH from the MS to the network to indicate that the MS has changed to the
ordered channel configuration successfully
The CONFIGURATION CHANGE REJECT message is sent on the main DCCH
from the MS to the network to indicate that the MS has not managed to switch to the
channel configuration ordered by the CONFIGURATION CHANGE COMMAND and
is still using the previous configuration

Configuration Change Procedure can be used to

add new channels to the HSCSD configuration


remove channels from the HSCSD configuration or
change the radio interface rates for all the channels in the HSCSD configuration.

Channel mode modify procedure


A Channel Mode Modify Procedure is used when changing the channel mode between
speech and data or when changing the radio interface data rate of the data channel. In
the Nokia Siemens Networks BSC implementation, Channel Mode Modify is used only
when changing the mode for a channel in a single slot connection or for an HSCSD main
channel as the only channel in the HSCSD configuration. The change between speech
and data is not made for channels in a multislot configuration. The changing of the radio
interface data rate for channels in a multislot configuration is made with the Configuration change procedure.

34

Id:0900d80580735031
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Schemes in HSCSD and 14.4 kbit/s Data Services

5 Schemes in HSCSD and 14.4 kbit/s Data


Services
The following schemes are described below:

DN9813893

Assignment in HSCSD and 14.4 kbit/s Data Services


HSCSD FACCH call setup
Subsequent assignment in HSCSD and 14.4 kbit/s Data Services
Configuration changes, basic schemes
BSC internal handover
External handover
HSCSD and 14.4 kbit/s Data Service request checks
Interoperability of HSCSD procedures
Channel allocation
Resource upgrade
Resource downgrade
Switching of HSCSD connection
Power control

Id:0900d80580590c8d
Confidential

35

Schemes in HSCSD and 14.4 kbit/s Data Services

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Assignment in HSCSD and 14.4 kbit/s Data Services


MS

BTS

MSC

BSC

**** NORMAL SIGNALLING

****

Classmark_ChangeClassmark_Update
2

**** NORMAL SIGNALLING

****

Setup
3
Call_Proceeding
4
Assignment_Request
5
Physical_Context_Request
6
Physical_Context_Confirm
7
Channel_Activation

Channel_Activation
9
Channel_Activation_ack
10
Channel_Activation_ack
11
Assignment_Command
12
SABM
13
Establish_Indication
14
UA
15
Assignment_Complete
16
Assignment_Complete
17
**** CONVERSATION PHASE ****

****

RELEASE OF A CALL ****


Clear_Command
18
Channel_Release
19
Clear_Complete
20

Figure 11

36

Mobile-originated call setup, basic scheme

Id:0900d80580590c8d
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

MS

BTS

Schemes in HSCSD and 14.4 kbit/s Data Services

BSC

Deactivate_SACCH

MSC

21

DISC
22
UA

23

Release_Indication
24
RF_Channel_Release
25
RF_Channel_Release
26
RF_Channel_Release_Ack
27
RF_Channel_Release_Ack
28

Figure 12

DN9813893

Mobile-originated call setup, basic scheme

Mobile-originated call setup, basic scheme:


1.
The MS sends its multislot capability information to the network
using the early classmark sending procedure. The CLASSMARK
CHANGE message includes the Mobile Station Classmark 3 IE
defining the MS multislot capabilities.
3.
The MS and the MSC negotiate the characteristics of the HSCSD
call.
5.
The MSC requests data connection. The Channel Type IE specifies
the characteristics for the connection (see HSCSD and 14.4 kbit/s
Data Services effects on A interface procedures).
The BSC checks the correctness of the request, the applicability of
the A interface circuit pool and the BSS capability to serve the
request as defined in HSCSD and 14.4 kbit/s data service request
checks.
The BSC allocates the channels (see Channel allocation) and
determines the HSCSD main channel and the uni/bi-directionality of
each allocated channel (HSCSD configuration), taking into account
the MS multislot capability.
9.
A separate channel activation is applied for each HSCSD channel.
The CHANNEL ACTIVATION message includes IEs Channel mode
and Activation Type, which determine the characteristics of the activated channel (see HSCSD and 14.4 kbit/s Data Services effects on
the Abis interface procedures).
12.
The BSC sends the ASSIGNMENT COMMAND on the main
HSCSD channel to the MS establishing the data call. Channel
Description 2 IE and the Channel Mode IE determine a single slot
14.4/14.5 kbit/s data call. HSCSD multislot configuration is determined by either the Channel Description 2 IE or Multislot Allocation
IE as defined in HSCSD and 14.4 kbit/s Data Services effects on
Radio interface procedures and the selected channel coding is indicated in Channel Mode IE.
14.
The BSC switches separate Abis PCM TSLs to consecutive A interface PCM TSLs as defined in Switching of HSCSD connection.

Id:0900d80580590c8d
Confidential

37

Schemes in HSCSD and 14.4 kbit/s Data Services

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

17.

The BSC informs the MSC about the number of allocated channels
and the chosen channel coding with the Chosen Channel IE (see
HSCSD and 14.4 kbit/s Data Services effects on A interface procedures).
The circuit pool of the A interface circuit implied by the CIC of the
ASSIGNMENT REQUEST is sent to the MSC in the Circuit Pool IE
if there exists more than one pool on the A interface.
19.
CHANNEL RELEASE is sent only on the main HSCSD channel.
21.
DEACTIVATE SACCH is sent only on the main HSCSD channel.
24.
RELEASE INDICATION is sent only on the main HSCSD channel.
26.
Separate RF CHANNEL RELEASE messages are sent for each
HSCSD channel.
Mobile-terminated call setup:
From the BSC viewpoint, the mobile-terminated HSCSD call setup case does not
differ from the mobile-originated case. At the call setup the MS and the MSC negotiate the characteristics of the HSCSD call with messages SETUP and CALL CONFIRMED. From the ASSIGMENT REQUEST onwards, the signalling is as in the
mobile-originated case.
Abnormal cases in call setup
If the BSC finds the ASSIGNMENT REQUEST incorrect or the BSS is unable to
serve the request as defined in HSCSD and 14.4 kbit/s data service request checks,
the BSC sends an ASSIGNMENT FAILURE message to the MSC.
If any of the CHANNEL ACTIVATION messages to the BTS fails, the whole HSCSD
call setup is terminated. All successfully activated channels are released and the
ASSIGNMENT FAILURE message is sent to the MSC.
If the MS rejects the ASSIGNMENT COMMAND, all the channels are released from
the BTS and the ASSIGNMENT FAILURE message is sent to the MSC.

HSCSD FACCH call setup


An HSCSD FACCH call setup is possible for non-transparent connections and transparent connections needing only one channel. Otherwise the BSC rejects the ASSIGNMENT REQUEST for the HSCSD FACCH call setup with the cause 'Invalid Message
Contents'. Checkings in FACCH setup for HSCSD and 14.4 kbit/s connections are
described in Checking the HSCSD and 14.4 kbit/s data service requests.
The HSCSD non-transparent connection established with the FACCH call setup is
started with one channel. The BSC counts the number of channels needed and resource
upgrade is possible after the assignment has been completed.
Subsequent assignment in HSCSD and 14.4 kbit/s Data Services
Subsequent assignment for HSCSD data connections can be carried out when the userdefined maximum number of channels or required data rate is changed. However, subsequent assignment from high speed to multi-slot data is not supported. The BSC
rejects such requests by sending an ASSIGNMENT FAILURE message to the MSC.
Checkings in the subsequent assignment are for HSCSD and 14.4/14.5 kbit/s connections are described in HSCSD and 14.4 kbit/s data service request checks.

38

User-initiated service level upgrade or downgrade


The MSC sends an ASSIGNMENT REQUEST in which HSCSD parameters have
been changed by the maximum number of channels or the air interface user rate.
The BSC recounts the number of needed channels using the current channel
coding. If there are more channels currently allocated than indicated by the new

Id:0900d80580590c8d
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Schemes in HSCSD and 14.4 kbit/s Data Services

maximum number of channels, the resource downgrade procedure is used to


release the extra channels before sending the ASSIGNMENT COMPLETE
message. If the new parameters allow the use of more channels than currently allocated, the ASSIGNMENT COMPLETE is sent first and the resource upgrade can be
done later as a separate procedure.
Abnormal cases
If mode modification towards the BTS fails, the current mode is kept. The BSC sends
an ASSIGNMENT FAILURE message to the MSC with a cause 'requested transcoding/rate adaption unavailable'.
If mode modification towards the MS fails, the BSC sends an ASSIGNMENT
FAILURE message to the MSC with the cause 'requested transcoding/rate adaption
unavailable'.
If resource downgrade fails in a user-initiated service level downgrade, the current
configuration is maintained. The BSC sends an ASSIGNMENT FAILURE message
to the MSC with a cause 'requested transcoding/rate adaption unavailable'.

Configuration changes, basic schemes

Resource downgrade
The BSC initiates the downgrade procedure (see Functionality of HSCSD and 14.4
kbit/s Data Services in BSC, HSCSD load control and Resource downgrade) and
defines the new configuration for the HSCSD connection. Multiple channels may be
released from the configuration during the same procedure. In this example, the
HSCSD configuration is downgraded from 3+1 to 2+2 configuration. A mode modify
procedure is needed when the uni/bi-directionality of a remaining channel is
changed. The network has to use bi-directional channels whenever it is allowed by
the MS multislot capability.
MS

BTS

MSC

BSC

**** HSCSD 3+1 connection ongoing ***

**** Resource downgrade decision ***


Mode_Modify
1
Mode_Modify_Ack
2
Configuration_Change_Command
3
Configuration_Change_Ack
4
Handover_Performed
5
RF_Channel_Release
6
RF_Channel_Release_Ack
7

Figure 13

DN9813893

Resource downgrade from 3+1 to 2+2 HSCSD configuration, basic


scheme

Resource downgrade from 3+1 to 2+2 HSCSD configuration, basic scheme


1.
A remaining uni-directional subchannel is changed to bi-directional.

Id:0900d80580590c8d
Confidential

39

Schemes in HSCSD and 14.4 kbit/s Data Services

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

3.

The BSC informs the MS of the new HSCSD configuration in the


Multislot Allocation IE.
The BSC switches the new configuration to the A interface as
described in Switching of HSCSD connection.
5.
The MSC is informed of the new number of channels and the used
channel coding in the Chosen Channel IE.
6.
The downgraded channel is released.
Resource upgrade
The BSC initiates the upgrade (see Functionality of HSCSD and 14.4 kbit/s Data
Services in BSC, HSCSD load control and Resource Upgrade) and defines the new
configuration for the HSCSD connection. Multiple channels may be added to the
configuration during the same procedure. In this example HSCSD configuration is
upgraded from 2+2 to 3+1 configuration. The mode modify procedure is needed
when the uni/bi-directionality of a remaining channel is changed. Uni-directional
channels are used to achieve higher total data rates with type 1 HSCSD MSS.
MS

BTS

MSC

BSC

**** HSCSD 2+2 connection ongoing ***

**** Resource upgrade decision

***

Channel_Activation

1
Channel_Activation_Ack

2
Mode_Modify
3
Mode_Modify_Ack
4
Configuration_Change_Command

5
Configuration_Change_Ack

6
Handover_Performed
7

Figure 14

40

Resource upgrade from 2+2 to 3+1 HSCSD configuration, basic


scheme

Resource upgrade from 2+2 to 3+1 HSCSD configuration, basic scheme


1.
The new upgraded uni-directional channel is activated.
3.
The previously allocated bi-directional channel is changed to a unidirectional one.
5.
The Multislot Allocation IE indicates the new HSCSD configuration
to the MS.
The BSC switches the new configuration to the A interface as
described in Switching of HSCSD connection.
7.
The new number of channels and the used channel coding are indicated to the MSC in the Chosen Channel IE.
Automatic Link Adaptation (ALA)
The BSC initiates the ALA procedure by the signal quality, BTS power and MS
power as defined in 14.4/14.5 kbit/s connection power control and automatic link
adaptation. The new channel coding is forwarded to the BSC, which may add a

Id:0900d80580590c8d
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Schemes in HSCSD and 14.4 kbit/s Data Services

resource upgrade or downgrade procedure to be carried out during the same signalling. The BSC defines the new configuration for the HSCSD connection. Channel
coding is changed to all channels belonging to the HSCSD connection. In this
example, the required air interface user rate is 29.0/36.0 kbit/s. The HSCSD connection is started with 14.5 kbit/s channel coding using 2+2 configuration. Channel
coding is changed to 12.0 kbit/s in ALA and the BSC changes the HSCSD configuration to 3+1.
When the channel coding is changed for a single slot non-transparent (NT) connection, a CHANNEL MODE MODIFY message is used instead of a CONFIGURATION
CHANGE COMMAND message to command the MS.
MS

BTS

BSC

MSC

**** HSCSD 2+2 connection using ***


**** 14.5 channel coding ongoing ***

**** ALA decision to 12.0 kbit/s ***


**** RNDSEB decides to upgrade ***
Channel_Activation
1
Channel_Actication_Ack
2
Mode_Modify
3
Mode_Modify_Ack
4
Mode_Modify
5
Mode_Modify_Ack
6
Configuration_Change_Command
7
Configuration_Change_Ack
8
Handover_Performed
9

Figure 15

DN9813893

Resource upgrade from 2+2 to 3+1 HSCSD configuration, basic


scheme

Resource upgrade from 2+2 to 3+1 HSCSD configuration, basic scheme


1.
The new upgraded uni-directional channel is activated. 12.0 kbit/s
rate in channel mode is used.
3.
The previously allocated bi-directional channel is changed to unidirectional using the rate of 12.0 kbit/s in channel mode.
5.
The rate of 12.0 kbit/s in channel mode is changed for the HSCSD
main channel too.
7.
The Multislot Allocation IE indicates the new HSCSD configuration
to the MS. The 12.0 kbit/s channel mode is used.
The BSC switches the new configuration to the A interface as
described in Switching of HSCSD connection.
9.
The new number of channels and the used channel coding are indicated to the MSC in the Chosen Channel IE.

Id:0900d80580590c8d
Confidential

41

Schemes in HSCSD and 14.4 kbit/s Data Services

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Abnormal Cases
If channel activation or mode modification for any of the commanded subchannels
or configuration change command to the MS is rejected, the old configuration is
returned. New channels are released and mode modification is redone for the
channels that were modified. In the case of timer expiry, the HSCSD call is cleared.
If the MS sends a CONFIGURATION CHANGE REJECT message with a cause
'channel mode unacceptable', the BSC prevents further configuration changes for
the connection and if the automatic link adaptation (ALA) was a part of the configuration change procedure, it prevents further ALA procedures for the connection.
If the switching of the new configuration fails, the BSC sends a CLEAR REQUEST
message to the MSC.

BSC internal handover


There are no HSCSD-specific differences in BSC internal, intra-cell or inter-cell handovers. The following signalling example describes a BSC internal, inter-cell handover.
The source cell non-transparent HSCSD configuration is 2+2 using 14.5 kbit/s channel
coding. In the target cell 3+1 non-transparent HSCSD configuration is allocated using
the 12.0 kbit/s channel coding.

42

Id:0900d80580590c8d
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

MS

BTS1

Schemes in HSCSD and 14.4 kbit/s Data Services

BTS2

BSC

MSC

Handover measurements and decision


Measurement_Report
1
Measurement_Result
2
Measurement_Report
3
Measurement_Result
4
Channel_Activation
5
Channel_Activation
6
Channel_Activation
7
Channel_Activation_ack
8
Channel_Activation_ack
9
Channel_Activation_ack
10
Handover_Command
11
Handover_Access
12
Handover_Detection
13
Physical_Info
14
SABM
15
Establish_Indication
16
UA
17
Handover_Complete
18
Handover_Performed
19
RF_Channel_Release
20
RF_Channel_Release
21
RF_Channel_Release_Ack
22
RF_Channel_Release_Ack
23

Figure 16

BSC internal inter-cell handover, basic scheme

BSC internal inter-cell handover, basic scheme


4.

The BSC receives measurement results via all the bi-directional channels. Any of the bi-directional channels can trigger the handover. All
handover causes are supported.
The BSC allocates the channels (Channel Allocation) and determines
the HSCSD main channel and the uni/bi-directionality of each allocated
channel (HSCSD configuration) taking into account the MS multislot
capability.

DN9813893

Id:0900d80580590c8d
Confidential

43

Schemes in HSCSD and 14.4 kbit/s Data Services

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

7.

A separate channel activation is applied for each HSCSD channel. The


CHANNEL ACTIVATION message includes IEs Channel mode and
Activation Type, which determine the characteristics of the activated
channel (see HSCSD and 14.4 kbit/s Data Services effects on the Abis
interface procedures).

11.

The BSC sends the HANDOVER COMMAND on the main HSCSD


channel to the MS establishing the data call. The HSCSD multislot configuration is determined by either the Channel Description 2 IE or Multislot Allocation IE as defined in HSCSD and 14.4 kbit/s Data Services
effects on Radio interface procedures and the selected channel coding
is indicated in Channel Mode IE. (Single slot 14.4/14.5 kbit/s data call is
determined by the Channel Description 2 IE and the Channel Mode IE.)

13.

A HANDOVER DETECTION message is received on the main HSCSD


channel.

16.

An ESTABLISH INDICATION message is received on the main HSCSD


channel.
The BSC switches separate Abis PCM TSLs to consecutive A interface
PCM TSLs as defined in Switching of HSCSD connection.

18.

A HANDOVER COMPLETE message is received on the main HSCSD


channel.

19.

The BSC informs the MSC about the number of allocated channels and
the chosen channel coding with the Chosen Channel IE (see HSCSD
and 14.4 kbit/s Data Services effects on A interface procedures).

21.

Separate RF CHANNEL RELEASE messages are sent for each


HSCSD channel.

External handover
The following signalling example describes external handover. Source cell non-transparent HSCSD configuration is 3+1 using 14.5 kbit/s channel coding. In the target cell,
only 2+2 configuration with 14.5 kbit/s channel coding can be allocated.

44

Id:0900d80580590c8d
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

MS

Schemes in HSCSD and 14.4 kbit/s Data Services

BTS2

BTS1

BSC1

BSC2

MSC

Handover measurements and decision


Measurement_Report

2
3

Measurement_Result

Measurement_Report
4

Measurement_Result
Handover_Required
5
Handover_Request
6
Channel_Activation
Channel_Activation
9
10

Channel_Activation_ack
Channel_Activation_ack

Handover_Command
14

Handover_Request_Ack
11
Handover_Command
12
13

Handover_Access
15

Handover_Detection
Handover_Detect
16

Physical_Info
17
18

SABM

UA
21

19

Establish_Indication

20

Handover_Complete

24
RF_Channel_Release
RF_Channel_Release
RF_Channel_Release

Figure 17
MS

Handover_Complete
22
Clear_Command
23
Clear_Complete

25
26
27

External handover, basic scheme


BTS1

BTS2

BSC1

BSC2

MSC

RF_Channel_Release_Ack
28
RF_Channel_Release_Ack
29
RF_Channel_Release_Ack
30

Figure 18

DN9813893

External handover, basic scheme

Id:0900d80580590c8d
Confidential

45

Schemes in HSCSD and 14.4 kbit/s Data Services

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

External handover, basic scheme


4.

The BSC receives measurement results by all the bi-directional channels. Any of the bi-directional channels can trigger the handover. All the
handover causes are supported.

5.

The source BSC starts the external handover. Currently used channel
coding is included in the message in single slot 14.4/14.5 kbit/s
handover if the BSC has made the choice. (The currently used number
of channels and channel coding are always included in the message
when an HSCSD call is handed over.)
External handover can also be requested due to circuit pool switching
(see HSCSD and 14.4 kbit/s data service request checks).

6.

The MSC requests data connection. The Channel Type IE specifies the
characteristics for the connection (see HSCSD and 14.4 kbit/s Data
Services effects on A interface procedures).
The BSC checks the correctness of the request, the applicability of the
A interface circuit pool and the BSS capability to serve the request as
defined in HSCSD and 14.4 kbit/s data service request checks.
The BSC allocates the channels (see Channel allocation) and determines the HSCSD main channel and the uni/bi-directionality of each
allocated channel (HSCSD configuration) taking into account the MS
multislot capability.

8.

A separate channel activation is applied for each HSCSD channel. The


CHANNEL ACTIVATION message includes IEs Channel mode and
Activation Type, which determine the characteristics of the activated
channel. For more information, see Assignment.

11.

The BSC switches separate Abis PCM TSLs to consecutive A interface


PCM TSLs as defined in Switching of HSCSD connection.
The BSC informs the MSC about the number of allocated channels and
the chosen channel coding with the Chosen Channel IE (see HSCSD
and 14.4 kbit/s Data Services effects on A interface procedures).
The circuit pool of the A interface circuit implied by the CIC of the
HANDOVER REQUEST is sent to the MSC in the Circuit Pool IE when
more than one pool exists on the A interface.
A radio interface message HANDOVER COMMAND is included in the
message. HSCSD multislot configuration is determined by either the
Channel Description 2 IE or Multislot Allocation IE as defined in HSCSD
and 14.4 kbit/s Data Services effects on Radio interface procedures and
the selected channel coding is indicated in Channel Mode IE. (Single
slot 14.4/14.5 kbit/s data call is determined by the Channel Description
2 IE and the Channel Mode IE.)

46

13.

A HANDOVER COMMAND message is forwarded to the MS on the


HSCSD main channel.

15.

A HANDOVER DETECTION is received on the HSCSD main channel.

19.

An ESTABLISH INDICATION is received on the HSCSD main channel.

21.

A HANDOVER COMPLETE is received on the HSCSD main channel.

Id:0900d80580590c8d
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

27.

Schemes in HSCSD and 14.4 kbit/s Data Services

Separate RF CHANNEL RELEASE messages are sent for each


HSCSD channel.

HSCSD and 14.4 kbit/s data service request checks


The BSC checks HSCSD and 14.4 kbit/s connection requests for the following:

DN9813893

that the MSC connection request is appropriate


that the BSS is capable of serving the request
that the MS is capable of serving the request
that the circuit pool (CIP) suggestion is appropriate for the requested connection.

Initial connection request checkings


Combination of the separate fields must form an unambiguous request. Otherwise the request is rejected with the cause 'Invalid message contents'.
If HSCSD is not activated, the multislot service request is rejected with error
cause 'Requested transcoding/rate adaption unavailable'.
14.4 kbit/s must be activated to allow 14.4/14.5 kbit/s data connections. Otherwise 14.4/14.5 kbit/s channel coding is removed from the list of allowed channel
codings in the data channel request. If the 14.4/14.5 kbit/s is the only choice in
the list, the assignment request is rejected with the cause value 'Requested
transcoding/rate adaption unavailable'.
The 4.8/6.0 kbit/s channel coding is removed from the list of allowed channel
codings in HSCSD requests. If the 4.8/6.0 kbit/s is the only choice in the list, the
ASSIGNMENT REQUEST is rejected with the cause value 'Requested
transcoding/rate adaption unavailable'.
It must be possible to allocate the required data rate with the maximum number
of channels and the fastest allowed channel coding in transparent (T) services.
Otherwise the request is rejected with error cause 'Invalid message contents'.
If there is no pool that can support the requested data rate, the circuit reservation
is interrupted with the A interface error cause 'Requested transcoding/rate
adaption unavailable'.
The HSCSD connection requests can be switched to circuit pool numbers 10,
13, 21, 22 and 32. If the MSC suggests another CIP, the BSC changes the
channel rate and type field in Channel Type IE to Full rate TCH channel Bm.
If none of the A interface circuit pools supports 14.4/14.5 kbit/s channel coding,
14.4/14.5 kbit/s channel coding is removed from the list of allowed channel
codings in a data channel request. If in a single slot data call request the
14.4/14.5 kbit/s channel coding is in the field Rate, it is replaced by the fastest
channel coding in the list of allowed codings. If the 14.4/14.5 kbit/s is the only
choice on the list, the assignment request is rejected with the cause 'Requested
transcoding/rate adaption unavailable'.
The MS must be capable of using the user-defined maximum number of channels. Otherwise the request is rejected with the cause 'MS not equipped'.
If the automatic link adaptation (ALA) is allowed by the radio network parameter
EnableALA and 14.5 kbit/s and 12.0 kbit/s channel codings are both allowed for
the connection, the selected circuit pool must support the maximum number of
channels allowed by the user. Otherwise the request is rejected with the cause
'Switch circuit pool'. CIP number 22 is set as the first candidate in the circuit pool
list.

Id:0900d80580590c8d
Confidential

47

Schemes in HSCSD and 14.4 kbit/s Data Services

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

FACCH call setup


An FACCH can be used as a signalling channel in the call setup when there are no
SDCCH channels available. If more than one channel is requested for HSCSD
transparent (T) service in the FACCH call setup, the BSC rejects the ASSIGNMENT
REQUEST message with the cause 'Invalid message contents'.
Subsequent Assignment
The meaning of Subsequent Assignment for the BSC is that an ASSIGNMENT
REQUEST message is received from the MSC during an ongoing connection on a
traffic channel in speech or date mode. Subsequent assignment can be used to
change the mode from FR speech to data
change the mode from data to FR speech
change the HSCSD parameters.
The BSC checks the following:
The circuit pool is not changed due to the subsequent assignment. If the original
channel mode is speech and the subsequent assignment is to the 14.4 kbit/s
data or HSCSD, the used CIP must support the requested service. If none of the
allowed channel codings is supported by the circuit pool in use, the assignment
is acceptable. Otherwise the request is rejected with error cause 'Invalid
message contents'.
If the original type of the call is transparent (T) HSCSD using more than one
channel or the subsequent assignment is to transparent HSCSD requiring more
than one channel, the request is rejected with error cause 'Invalid message contents'.
Subsequent assignments from half rate (HR) to full rate (FR) or from FR to HR
are not supported. Such requests are rejected with the cause 'Invalid message
contents'.
The BSC does not start the circuit pool switching procedure during the subsequent
assignment procedure.
BSC internal handover
The BSC allocates resources for internal handover with the cause 'Switch circuit
pool' when
the used circuit pool does not support the number of channels needed to fulfil
the requested total data rate.
the used circuit pool does not support 14.4 kbit/s, although it is in the list of
allowed channel codings and its use is practical.
the used circuit pool does not support the maximum number of channels, automatic link adaptation (ALA) is allowed by the radio network parameter
EnableALA and the 14.5 kbit/s and 12.0 kbit/s channel codings are both
allowed for the connection.
The order of the pool numbers in the Circuit pool list depends on the case.
The BSC then switches the handover type to BSC external handover with the cause
'Switch circuit pool'. However, the handover attempt is terminated if
an MSC-controlled external handover has already been attempted unsuccessfully and an internal handover is attempted due to that or
there is no appropriate candidate for the external handover.

Interoperability of HSCSD procedures


One of the following procedures can be processed at a time for an HSCSD connection:

48

handover

Id:0900d80580590c8d
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Schemes in HSCSD and 14.4 kbit/s Data Services

ALA (a resource upgrade or downgrade can be a part of ALA)


resource upgrade
resource downgrade
subsequent assignment
release of the connection.

Interoperability of handover, assignment and release procedures are similar to single


slot connections.
The BSC does not start any of the configuration change procedures during the release
procedure and the subsequent assignment procedure.
A interface messages are buffered during resource upgrade, resource downgrade, ALA
and handover procedures.
During a handover, the BSC does the following:

controls that only one handover at a time is processed for multislot connection
controls that ALA is not started
rejects the start of configuration change procedures

During the ALA, the BSC does the following:

controls that only one ALA at a time is processed for multislot connection.
controls that a handover is not started
does not start any of the configuration change procedures

During resource upgrade or downgrade, the BSC does the following:

sets both upgrade and downgrade timers when starting a resource upgrade or
downgrade procedure. Upgrade or downgrade may be started after timer expiry
For a more detailed description, see Channel Allocation.
controls the resource upgrade and downgrade procedures and does not start
handover or ALA during them

Channel allocation

DN9813893

14.4 kbit/s channel allocation


The TRX and time slot selection for a 14.4 kbit/s data call is similar to the one in full
rate speech call and full rate data call with a lower data rate (see Radio Channel
Allocation ).
Single slot FR channel allocation
In single slot channel allocation, the BSC attempts to keep consecutive full rate
traffic channels free for HSCSD multislot connections. The interference band to be
used by the MSC, Interference band recommendation by the BSC, BCCH/nonBCCH preference and TRX change in intra-cell handover principles are still maintained and favoured as before introducing HSCSD. Here only a list of the single slot
channel allocation rules in preference order is given.
A more detailed description of the single slot channel allocation algorithm can be
found in Radio Channel Allocation.
The following rules are valid regardless of HSCSD presence in the BSS. Note that
TSL selection is made as a result of using an appropriate set of the following list
items.
Preference of rules for single slot channel allocation which is always used:
1
in intra-cell handover, an attempt to change the TRX is made
2
allocation is made according to interference band requirements
determined for the call

Id:0900d80580590c8d
Confidential

49

Schemes in HSCSD and 14.4 kbit/s Data Services

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

50

the TRX selection is made according to possible BCCH/non-BCCH


TRX priorisation
4
permanent type FR TCH resources are preferred to dual rate
resources.
When the cell load is low, the TRX selection and TSL selection in TRX are both
rotated according to an additional rule. Additional rules for the single slot channel
allocation when the cell load is high are presented below:
5
the TSL is selected from a place that has the least consecutive
TSLs free, that is, the BSC attempts to keep bigger TSL gaps free
for HSCSD connections
6
the biggest free TSL gaps in TRXs are compared and the TRX containing the smallest of them is selected
7
the TSL is selected from the TRX containing the least free
resources
8
TSLs in either end of the TRX are preferred
9
the TRX selection is rotated
10
a TSL in HSCSD territory is selected
HSCSD channel allocation
The following issues are taken into account in HSCSD channel allocation:
data service (transparent/non-transparent)
the required total radio interface data rate (non-transparent service)
the requested radio interface user rate (transparent service)
the maximum number of channels (user-defined)
the MS multislot class
the allowed channel codings
the interference band to be used by the MSC
the interference band recommendation by the BSC
the average interference level if no interference band defined by the MSC or by
the BSC
the possibility to change the configuration after the first allocation
the preference between BCCH and non-BCCH TRXs
the preference between permanent FR TCHs and dual FR TCHs
the TRX selection in intra-cell handover
When a transparent HSCSD call is requested, the BSC counts the number of
channels needed by dividing the requested radio interface user rate with the fastest
allowed channel coding. Upward rounding is applied to enable full service of the
requested data rate. Exceptions to this rule are radio interface user rates 9.6 and
19.2 kbit/s in which it is more practical to use the 9.6 kbit/s channel coding since the
same number of channels would be needed if the 14.4 kbit/s channel coding with
poorer error correction was used.
The number of channels with a certain channel coding is indicated in the required
total radio interface data rate request when a non-transparent HSCSD call is
requested. The fastest allowed channel coding is selected.
The BSC may not allocate more channels than allowed by the user-defined
maximum number of channels.
When the MSC has given the interference bands to be used, only those interference
bands can be used for any HSCSD channel allocation. When allocating channels in

Id:0900d80580590c8d
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Schemes in HSCSD and 14.4 kbit/s Data Services

super-reuse frequencies, a channel of recommended interference band or better


interference band can be allocated.
The number of channels needed must be allocated for the transparent HSCSD connection. Transparent (T) connections are always symmetrical, that is, only bi-directional channels may be allocated. A non-transparent HSCSD connection can be
started with one to a user-defined maximum number of channels. Increasing and
decreasing the number of channels and channel coding change during the connection are also possible for the non-transparent HSCSD connection, except when distinctly denied by the MSC request. When the changes after the first allocation in
assignment or external handover are denied, the BSC must maintain the used
number of channels and the used channel coding in intra-BSC handovers.
Channel allocation for an HSCSD connection is made as soon as a proper gap fulfilling the following conditions is found:
the MSC-defined interference band to be used or
the BSC-recommended or better interference band or
a gap without interference when no interference recommended and
the number of channels needed from a set of permanent FR TCH resources
The search for TRXs is carried out following the possible BCCH/non-BCCH TRX
preference. When channels are searched due to intra-cell handover the source TRX
is examined last. In intra-cell handover for non-transparent HSCSD connection,
fewer channels are allocated rather than selecting the source TRX.
When the free TSL gap contains more channels than are needed by the HSCSD
connection, the allocation is made to the end of the gap. Exceptions to this rule are:
1. The TSL gap fulfilling the interference definitions set by the MSC or the BSC. In
that case the proper TSL gap can also be allocated from inside a greater free
TSL gap.
2. When the allocation of only one channel for the HSCSD connection is made. In
that case the last TSL (TSL 7) is not allocated for the HSCSD connection
because that would restrict the possibilities for upgrading the connection later
due to MS multislot capabilities or a user-initiated service level upgrade procedure.
If there are multiple gaps in the same TRX fulfilling the HSCSD request, the gap
nearest to the start of the TRX is selected.
If the non-transparent HSCSD request cannot be allocated the number of channels
needed, the incomplete TSL gaps are compared by the following prioritised rules:
1
The greatest TSL gap is selected. In HSCSD allocation in regular
frequencies, a larger gap outside the BSC interference band recommendation is selected rather than a smaller gap with which the interference band recommendation could be followed.
2
The BSC interference band recommendation is favoured. If there
are equal-sized gaps not totally fulfilling the number of needed
channels, the gap fulfilling the BSC interference band recommendation is selected. If only a part of the TSL in a gap fulfils the BSC interference band recommendation, the gap is considered as not
fulfilling the recommendation. If no interference band recommendation is defined, the TSL gap with the lowest average interference is
selected.
3
The TSL gap with more permanent FR TCH channels is selected to
avoid inefficient use of half rate capacity.

DN9813893

Id:0900d80580590c8d
Confidential

51

Schemes in HSCSD and 14.4 kbit/s Data Services

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

BCCH/non-BCCH TRX selection preference is followed if there are


equal-sized gaps not totally fulfilling the number of channels needed
and equal by the interference bands.
5
The TSL gap selection is made as close to the middle of the TRX as
possible. An incompletely served HSCSD connection has better
upgrade possibilities when the allocation is not made to either end
of the TRX.
6
TRXs are examined in the same particular order. If there are two
TRXs with equal HSCSD allocation properties, the former TRX of
the examination order is selected.
When channels are searched due to an intra-cell handover, the source TRX is
examined the last. In an intra-cell handover for non-transparent HSCSD connection,
fewer channels are allocated rather than selecting the source TRX.
After the gap for the HSCSD connection is selected, the BSC selects the main
channel according to Channel description 2 (see 3GPP TS 24.008: Mobile radio
interface layer 3 specification). If the consecutive TSLs do not fulfil the requested
data rate in NT service, the HSCSD territory is checked for additional free TSLs from
non-consecutive TSLs. The HSCSD connection territory determines the TSLs
around the HSCSD main channel that can be allocated as additional HSCSD subchannels. The territory is defined by the MS multislot class fields (see 3GPP TS
45.002: Multiplexing and multiple access on the radio path). When all the TSLs for
the HSCSD connection are selected, the BSC determines the uni/bi-directionality of
each channel.
Resource upgrade
HSCSD load control defining the parameterisation leading to the need for upgrade procedure is described in Functionality of HSCSD and 14.4 kbit/s Data Services in BSC,
section HSCSD load control. The radio resource upgrade procedure can be used for
non-transparent HSCSD calls to add more channels to the configuration in order to
better achieve the requested radio interface user rate. The resource upgrade can be
made for an HSCSD call when the minimum HSCSD capacity for the cell is not achieved
and when the traffic load of the cell does not exceed a particular level. The interference
band to be used, defined by the MSC, and the interference band recommendation,
defined by the BSC, are followed as in the initial channel allocation phase. Resource
upgrade can be made until the user-defined maximum number of channels is achieved
or the required air interface user rate is achieved.
The resource upgrade is not made if

the HSCSD connection is allocated in the IUO regular frequency area


changes after first allocation are denied for the connection
the parameter UpgradeGuardTimeHSCSD is set to value '0' for the cell
some other procedure is ongoing for the connection (see Interoperability of HSCSD
procedures) or
the MS has rejected earlier upgrade or downgrade command with the cause
'channel mode unacceptable'.

The resource upgrade procedure is initiated when

52

an FR TCH is released from another connection


the resource upgrade timer expires for the HSCSD connection or
the number of channels needed increases in ALA from 14.5 to 12.0 kbit/s.

Id:0900d80580590c8d
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Schemes in HSCSD and 14.4 kbit/s Data Services

The resource upgrade is not initialised when the upgrades become allowed after the cell
load goes under the LowerLimitCellLoadHSCSD parameter value. Upgrade timers
are restarted if they expire under the upgrade denial time. This is done to avoid rapid
signalling bursts.
When a FR TCH is released, queues are checked first for a new allocation. If there are
no calls in queue and there are HSCSD calls in the TRX, the released TSL location is
checked if it is in the territory of an incompletely served HSCSD non-transparent call.

If the location is within the right area but the upgrade is currently denied by the cell
load or the previous configuration allocation has not been acknowledged, the TSL is
marked as to be in the HSCSD call territory. This means that the TSL is not allocated
for single slot calls when there are other free TSLs.
If the location is within the right area but the upgrade guard time is running, the
number of free resources is counted from the HSCSD connection territory. The
resource upgrade is made if the number of free channels permits the upgrade due
to gain in data rate.

When the upgrade guard time expires, the HSCSD connection territory is checked for
any free resources and as many channels are allocated as are needed and available.
HSCSD upgrade with intra-cell handovers:
If all conditions for HSCSD upgrade are met but there is a call lying beside the HSCSD
call, an intra-cell handover is started. The aim of the handover is to move the call to
another free time slot and clear the time slot for HSCSD use. The BSC continues the
upgrade when the source channel of the handover is released. If the HSCSD connection
needs more than one channel to be upgraded, the UpgradeGuardTimeHSCSD is
waited between the intra-cell handovers.
Resource downgrade
The resource downgrade procedure is initiated

when the total cell traffic load exceeds a certain load and the minimum HSCSD
capacity of the cell is offered. In this situation, HSCSD calls are downgraded for
every incoming call
when the target of pre-emption is a non-transparent HSCSD connection with more
than one channel
when the number of channels needed changes in the ALA from 12.0 kbit/s to 14.5
kbit/s
when the number of channels needed or user-defined maximum number of
channels changes in user-initiated resource level change

The target selection for the HSCSD connection to be downgraded is based on the following principles:

the connection for which downgrade is allowed by the connection type and resource
downgrade guard time can be selected
the connection of the smallest priority is selected
the connection with the highest number of channels used is selected

The resource downgrade is not made if

DN9813893

changes after the first allocation are denied for the connection
the parameter DowngradeGuardTimeHSCSD is set to value '0' for the cell
some other procedure is ongoing for the connection (see Interoperability of HSCSD
procedures) or

Id:0900d80580590c8d
Confidential

53

Schemes in HSCSD and 14.4 kbit/s Data Services

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

the MS has rejected an earlier upgrade or downgrade command with the cause
'channel mode unacceptable'.

Switching of HSCSD connection


The main HSCSD channel is always switched to the first subchannel in an Ater TSL.
This is made to help TCSM synchronisation and to avoid unnecessary changes in
switching when the mode of the connection is changed from HSCSD to speech by subsequent assignment. HSCSD subchannels are switched in ascending order to Ater TSL
subchannels according to their TSL numbers.
At downgrade, any Ater subchannel can be released and subchannels are not moved.
At upgrade, the lowest possible subchannel is switched. See 3GPP TS 48.020: Rate
adaption on the Base Station System - Mobile-services Switching Centre (BSS-MSC)
interface.
Power control
Each bi-directional channel is controlled individually. For uni-directional channels only
downlink power is controlled. Since only the worst channel among the main channel and
uni-directional subchannels is reported, the same downlink power is copied to the unidirectional channels as is used for the main channel.

54

Id:0900d80580590c8d
Confidential

DN9813893

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

User interface of HSCSD and 14.4 kbit/s Data Services

6 User interface of HSCSD and 14.4 kbit/s Data


Services
MML commands

The commands of the following MML command groups are used for creating circuits
and circuit pools supporting HSCSD and 14.4 kbit/s data services:
Transcoder Configuration (WG command group)
Unit Connections Handling (WU command group)
Circuit Group Handling (RC command group)
Circuit State Handling (CE command group)
Parameter Handling (WO command group): software-specific control parameters
Base Transceiver Station Handling (EQ command group): parameters related to
HSCSD load control.
Power Control Parameter Handling (EU command group): parameters related to
14.4/14.5 kbit/s connection power control and automatic link adaptation
GSM Measurement Handling (TP command group): BSC measurements

Parameters
Software-specific control parameters:

HSCSD_USAGE defines if the HSCSD is supported by the BSC or not


The software-specific control parameter DATA_144_USAGE defines whether the
14.4 kbit/s data service is supported by the BSC or not

Parameters related to 14.4/14.5 kbit/s connection power control and automatic link
adaptation:

pc lower thresholds qual144 Rx level (LQR), Px (LQP), Nx (LQN)


power limit ALA (ALIM)
ALA enabled (AENA)
BS TX pwr max (PMAX1)
BS TX pwr min (PMIN)
pc upper thresholds qual dl Rx qual (UDR), Px (UDP), Nx (UDN)
pc upper thresholds qual ul Rx qual (UUR), Px (UUP), Nx (UUN)
min int between ALA (AMIN)

Parameters related to HSCSD load control:

HSCSD
HSCSD
HSCSD
HSCSD
HSCSD
HSCSD
HSCSD
HSCSD

TCH capacity minimum (HTM)


cell load upper limit (HCU)
cell load lower limit (HCL)
regular cell load upper limit (HRCU)
upgrade guard time (HUT)
upgrade gain (HUG)
minimum exhaust (HME)
downgrade guard time (HDT)

For more information on the parameters, see:

DN9813893

Functionality of HSCSD and 14.4 kbit/s Data Services in BSC


BSS Radio Network Parameter Dictionary

Id:0900d80580590c90
Confidential

55

User interface of HSCSD and 14.4 kbit/s Data Services

BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data


Services in BSC

Statistics
A new measurement type High Speed Data Measurement is introduced with new
counters (see 67 High Speed Data Measurement). New counters are also introduced to
the following measurement and observation types:

1 Traffic Measurement
2 Resource Availability Measurement
4 Handover Measurement
5 Power Control Measurement
18 Handover Observation

BSC measurements can be handled by GSM Measurement Handling MML commands.

56

Id:0900d80580590c90
Confidential

DN9813893