Académique Documents
Professionnel Documents
Culture Documents
Site
Vélizy Mobile Networks Division
RELEASED
PREDISTRIBUTION:
ABSTRACT:
This document describes the management of the SDCCH channel and a methodology to dimension this
resource.
APPROVALS
App.
Date
SDCCH DIMENSIONING
TABLE OF CONTENT
1 HISTORY.......................................................................................................................................................................................6
3 SCOPE.............................................................................................................................................................................................8
4 SDCCH PRESENTATION........................................................................................................................................................9
4.1 SIGNALLING CHANNELS DESCRIPTION ................................................................................................................................... 9
4.2 SDCCH USAGE...................................................................................................................................................................... 10
5 SDCCH PROCEDURE.............................................................................................................................................................12
5.1 SDCCH CHANNEL ACTIVATION ............................................................................................................................................ 12
5.2 SERVICE REQUEST ................................................................................................................................................................... 16
5.2.1 Traffic Channel..............................................................................................................................................................16
5.2.2 SMS ..................................................................................................................................................................................17
5.2.3 Location Update............................................................................................................................................................19
5.2.4 IMSI attach/detach........................................................................................................................................................20
5.3 SDCCH CHANNEL RELEASE .................................................................................................................................................. 20
6 SDCCH DIMENSIONING......................................................................................................................................................22
6.1 CALL MIX .................................................................................................................................................................................. 22
6.2 SDCCH HOLDING TIME AND SDCCH USAGE PER CALL ................................................................................................... 23
6.3 NUMBER OF CALLS................................................................................................................................................................... 24
6.4 SDCCH TRAFFIC..................................................................................................................................................................... 24
6.5 NUMBER OF SDCCH TS......................................................................................................................................................... 25
6.6 TOOL.......................................................................................................................................................................................... 26
6.7 RECOMMENDATIONS ............................................................................................................................................................... 27
7 IMPACT ON ABIS RESOURCE...........................................................................................................................................29
7.1 OPTIMISATION OF THE A BIS RESOURCE ............................................................................................................................... 29
7.2 SDCCH A LLOCATION AND RESPONSE TIME....................................................................................................................... 30
7.2.1 Maximum number of SDCCH......................................................................................................................................30
7.2.2 Compatibility with Half-Rate Mode...........................................................................................................................31
7.2.3 Throughput.....................................................................................................................................................................31
7.3 A BIS INTERFACE RECOMMENDATION ................................................................................................................................... 31
8 SDCCH DIMENSIONING EXAMPLE...............................................................................................................................32
9 CONCLUSION ...........................................................................................................................................................................33
10 GLOSSARY.................................................................................................................................................................................34
TABLE OF TABLES
Table 1: Alcatel Reference call mix......................................................................................................22
Table 2: SDCCH Holding Time...........................................................................................................23
Table 3: Inputs of the SDCCH dimensioning tool...............................................................................26
Table 4: Outputs of the SDCCH dimensioning tool ............................................................................27
Table 5: Recommended SDCCH values..............................................................................................27
Table 6: Multiplexed Channel Block presentation...............................................................................29
Table 7: Maximum SDCCH number per MCB type ............................................................................30
Table 8: MCB scheme compliance with Dual Rate .............................................................................31
TABLE OF FIGURES
Figure 1: Radio link establishment for Mobile Originated/ Terminated Call ......................................13
Figure 2: Signalling to traffic channel transfer....................................................................................17
Figure 3: SMS transmission on SDCCH channel.................................................................................18
Figure 4: Release of the SDCCH channel ...........................................................................................21
Figure 5: Handling of traffic ................................................................................................................25
1 HISTORY
2 REFERENCE DOCUMENTS
[1] 3BK 02974 AAAA TQZA ALCATEL 900/1800 BSS System description
[2] 3BK 10204 0511 DTZZA Dynamic SDCCH allocation
[3] 8BL 00601 0007 TQZZA BSS – Definition of service indicators
[4] 3DF 00993 7000 PGZZA Optimum Location Area Planning
[5] 3BK 11203 0057 DSZZA Transmission Functional Specification Release B7
[6] 3BK 11203 0059 DSZZA Abis Signalling Load B7
[7] 3BK 11203 0040 DSZZA BSS Telecom Traffic model
[8] “Réseaux GSM”, 5ème édition revue et augmentée, X. Lagrange, Ph. Godlewski, Sami
Tabbane, Hermes science publication
[9] http://www.gsm-support.org/
[10] 3DC 21126 0001 TQZZA Functional Feature Description – Immediate Assignment
Extended in Release B5
3 SCOPE
With the growing interest for Short Message Service (SMS), a precise dimensioning of the signalling
resources on GSM air interface is a necessity.
Since the first SMS, sent in December 1992 on the Vodaphone Network, from a personal computer
to a mobile phone, the SMS market has first grown smoothly to reach nowadays a tremendous
development speed. By May 2001, 15 billion SMS messages were being sent each month, including
150 millions in France alone, representing already an important source of income (almost 10%) for
operators. New ranges of application, like taxed SMS, are to be launched in a near future providing
more services to the customer and more revenues to the operators.
In China, one of the largest markets of mobile telephony in the world in terms of subscribers, the
traffic generated by the SMS doubles every month. The Chinese users of portable send on average
three SMS per month. Globe Telecom, one of the Filipinos mobile operators, treats more than 300
messages per month per subscriber, thus underlining the strong potential of the Chinese market.
Mobile messaging is even evolving beyond text by taking a development path from SMS to EMS
(Enhanced Message Service) to MMS (Multimedia Messaging Service) where text, sound, animation,
and pictures will be supported.
Defining too many SDCCH will lead to a lack of TCH or PDCH resources, and incomes are
generated from circuit switch or packet switch user data. On the contrary, a lack of SDCCH channels
will result in a high blocking rate for SDCCH channels, with deteriorated TCH allocation
consequences. Once again, it implies a decrease of revenue for the operator.
The optimal number of SDCCH channels depends mainly on the duration of the calls, the number of
Location updates and the SMS use.
The first part of the document analyses how the Stand-alone Dedicated Control Channel (SDCCH) is
implied in those events. Then, an analysis of the SDCCH dimensioning process is performed. Finally,
a user-friendly tool developed to support SDCCH dimensioning is presented with a set of
recommended SDCCH configurations based on Alcatel typical call-mix.
4 SDCCH PRESENTATION
In the BTS, every Transceiver (TRX) serves eight basic physical radio channels using a Time Division
Multiple. Every physical radio channel is defined by the TRX serving this channel and by the TS
number (TS 0 ...TS 7). If frequency hopping is not used, a one-to-one relationship exists between
physical channels and Radio Frequency (RF) carrier frequencies.
There are two types of applications for the GSM Cell Broadcast feature:
• The applications where the information broadcast relates more or less to the MS operation in the
Network. This type of application is driven directly by the network/operator. These applications
such as Home zone indication, charging rate indication or Network condition indication, are
value-added features for the operator.
• The application where the operator offers the cell Broadcast facility for use by the entities external
to the GSM network. These application such as road traffic information, public safety,
advertisement etc, can be a source of additional revenue for the operator.
The two types of applications described can coexist.
The GSM Cell Broadcast reduces the number of available SDCCH channels per TS from 8 to 7. This
feature can impact from one to two SDCCH TS. Hence, low impact is foreseen for cells with large
SDCCH configuration.
Call set-up is required to establish connection between a Mobile Station (MS) and the Network Sub-
System (NSS). The NSS is responsible for managing the connection with the correspondent. Different
types of call are defined in the GSM specifications and imply different usage of the radio channels.
The three basics types of call are presented in the following table.
Type of Calls Description-
Mobile Management Calls These calls, e.g. location update, are used by the system to gather MS
information. The exchanges are protocol messages only; therefore,
only a signalling channel is used.
Service Calls These calls, e.g. SMS and Supplementary Service (SS) calls, pass small
amounts of information. Therefore, only a signalling channel is used.
User Traffic Calls These calls to a correspondent, e.g. speech or data calls (in
connected mode), can pass large amounts of information. Therefore
they require more than a signalling channel and used a traffic
channel.
These channels are associated with FACCH/SACCH. An SDCCH is always assigned for call set-up,
even if a TCH is later required for the call. Therefore, SDCCH is implied in the three types of call
described above.
The directed retry feature, which can be seen as a special kind of intercell handover that would be
applied during the call set-up process if a radio cell is congested by traffic load, is not considered in
the following dimensioning process.
GPRS introduction has no impact on the SDCCH load. Packet data channels set-ups and Routing
Area updates are realised via AGCH or PAGCH (if Master PDCH is introduced) and then via
dedicated GPRS channels.
However, AGCH load and consequently Location Area and Routing Area designs will need to be
monitored carefully, especially when GPRS traffic will take off without Master PDCH implemented yet.
5 SDCCH PROCEDURE
The MS notes the random number and frame number associated with each channel_request
message. These are used by the MS to recognise the response sent from the BSS. This response is
sent on the AGCH, which can be monitored by several MSs. The MS decodes all messages sent on
this AGCH and only accepts a message with a random number and frame number matching one of
the last three requests sent.
Paging
Mobile
mmand
Paging co +cell list IE
quest up
Paging re paging gro
CCCH TS+
I
TMSI/IMS
Channel R
equest (RA
CH)
Originated+Terminated
Channel R
REF equired
memory
Channel Activation
+power
TA+SDCCH
Channel A
ctivation A
ck
mand
Assign com
MS compares Immediate
message with ent AGCH
te Assignm +power+
RFN+REF
REF in memory Immedia TA+SDCCH
+RFN+REF
TA+SDCCH
Switch to SABM
SDCCH Establish In
cm+Servic dication
e Request SCCP Conn
cm+Servic ectio n Request
e Request
UA cm+Servic
e Request
quest
Service Re
firm
Service Request must ection Con
SCCP Conn
match original sent
by MS in the SABM
On receipt of the channel_request message from the MS, the BTS sends a channel_required message
to the BSC. This message contains the random number sent by the MS, and the timing advance
measured by the BTS.
The BSC checks the channel_required message to ensure it can accept the request. It allocates an
SDCCH channel if one is available.
The BSCs then sends a channel_activation message to the BTS. It also set a timer to wait for an
acknowledgement from the BTS, indicating that it is ready to activate the channel. The channel
activation message contains:
• A description of the SDCCH to be used
• The Timing Advance (TA)
• MS and BTS power commands. The MS and BTS power are set to the maximum allowed
in the cell.
The BTS initiates the physical layer resources for the channel and sets the LAPDm contention
resolution ready for the first MS message on the SDCCH. It then sends a
channel_activation_ackowledgement message to the BSC. The BSC stops then its guard timer.
The BSC builds and sends an immediate_assign_command message reiterating the information
given in the channel_activation command. This message also includes the random number and
frame number of the original MS request to which the BSC is replying. It also instructs the BTS to
inform the MS of the SDCCH channel assignment. The BSC starts a guard timer for the MS to
respond.
The MS checks the random number and frame number in the immediate_assignment message. If it
matches those from its last three channel_request sent, the MS switches to the indicated SDCCH and
sets its timing advance to the value indicated in the immediate_assignment message.
The first layer 2 frame sent on the SDCCH is a standard LAPDm type frame, known as the Set
Asynchronous Balanced Mode (SABM). On the air interface, it establishes the LAPDm connection with
the BTS. This frame can also contain layer 3 messages.
The MS starts its LAPDm connection and sends a layer 3 message in its first frame. The BTS uses this
message for contention resolution. The BTS sends an acknowledgement to the MS containing the
same layer 3 message. Therefore, only the MS that sent the message can accept the response of the
BTS and consider itself connected.
The BSC sends an SCCP_connection_request message to the MSC. The MSC replies with an
SSCP_connection_confirm message. This message can contain a classmark request or a cipher mode
command.
The signalling link is then established between the MS and the MSC.
SDCCH set-up is then involved in the three types of services enlighten above:
• Service request (call set-up, SMS, …)
• Location update
• IMSI attach/detach
The call set-up procedure has been established via SDCCH, as presented above. However, in case of
call traffic or data traffic in connected mode, the establishment of the communication requires the
allocation of a dedicated traffic channel (TCH).
The TCH allocation is realised simultaneously to the BSC/MSC and BTS/MSC resource allocation.
Thus, the MSC reserves a BSC/MSC resource on the A interface and sends a TCH
assignment_request message to the BSC.
The BSC checks the availability of TCH resources and if available sends a channel_activation to the
BTS, containing the references of the TCH to be used. The BTS replies with a
channel_activation_ackowledgement message to the BSC.
The BSC can now send a commutation order to the MS via an assignment_command message. This
message contains a complete description of the TCH to be used.
The MS commutes then on the new channel and re-establishes a layer 2 connection with the BTS by
sending a SABM message. The signalling SABM message is sent on the FACCH (TCH resource
stolen). This message is acknowledged via an UA message.
est
ntext requ
Physical co
Physical co
ntext confi
rm
TA+power
ctivation
Channel A
SACCH +power
cipher+DTX
TCH+TA+
update
TA+power Channel A
ctivation A
ck
Power+TA
mand
Assign com
)
ma nd (SDCCH
Assign com TCH
TCH
Release SDCCH
SABM (FA
CCH)
)
UA (FACCH
Assignme
nt comple
te (FACCH
)
Assignme
nt comple
te
Initiate SDCCH
Release
5.2.2 SMS
SMS transmission on the Air interface is realised via SDCCH when the mobile is in idle mode. The
existing SACCH is used if the mobile is already transmitting.
Switch to
SDCCH
SABM
Establish In
cm+Servic dication
e Request SCCP Conn
cm+Servic ection Req
e Request uest
UA cm+Servic
e Request
quest
Service Re
firm
ection Con
SCCP Conn
Authentication and Ciphering
SABM
Establish In
dication
SAPI=3
SAPI=3
UA
SAPI=3
- Ack
SMS Control Protocol
- Data
SMS Control Protocol
Initiate connection
Release
A powered-on mobile is informed of an incoming call by a paging message sent over the PCH
channel. One extreme would be to page every cell in the network for each call, which would be
obviously a waste of radio bandwidth. The other extreme would be for the mobile to notify the
system, via location updating messages, of its current location at the individual cell level, but it would
be very wasteful due to the large number of location updating messages issued. A compromise
solution used in GSM is to group cells into Location Areas (LA), and mobile stations are paged in the
cells of their current LA.
The Location Update (LU) procedure is always initiated by the MS. Location Update is performed after
the call has finished. Reasons for location update include:
• Periodic update
The MS performs periodic LU after a lack of signalling activity for a specific time. If the
timer expires, the MS initiates a LU, even if it has not changed of LA. This periodic location
update procedure has been introduced for reliability reasons. If an HLR or MSC/VLR fails,
to have each mobile register simultaneously to bring the database up to date would cause
overloading. Therefore, the database is updated as location-updating events occur. The
enabling of periodic updating, and the time period between periodic updates, is
controlled by the operator, and is a trade-off between signalling traffic and speed of
recovery. The duration of the MS timer is defined by the network and sent to the MS as
system information messages on the BCCH. This time can range from 6 minutes up to 25
hours. If a mobile does not register after the updating time period, it is deregistered.
In both cases, the MS initiates the LU procedure by sending a channel_request message indicating
that the call is for a location update (please see Figure 1, page 13).
The BSS assigns a dedicated SDCCH channel and establishes a signalling link between the MS and
the MSC.
When a signalling path is established, the MS sends the LAI of the old cell on which it was camped to
the MSC. The new VLR interrogates the old VLR for authentication and subscriber information. The
BSS adds the cell identity of the MS current location to the message sent to the MSC. The NSS stores
this information in either its HLR or its VLR.
A procedure related to location updating is the IMSI attach and detach. A detach lets the network
know that the mobile station is unreachable (mobile off), and avoids having to needlessly allocate
channels and send paging messages. An attach (mobile on) is similar to a location update, and
informs the system that the mobile is reachable again.
IMSI attach/detach is a mobility feature, which primarily concerns the MSC and the MS. Used
together with the periodic location update procedure, IMSI attach/detach allows the network to
provide more efficient control and use of the resources.
For example, if a mobile-terminated call arrives for an MS, which is detached, the MSC knows that
the MS is inactive and does not need to initiate a paging request. For the BSS, this can reduce load
on the PCH.
MSs, which have successfully connected and logged themselves onto the network are then obliged to
perform IMSI attach/detach procedure.
The release of the SDCCH channel is initiated by the MSC sending a clear_command message to the
BSC. The BSC acknowledges the command and initiates the release of the dedicated channel. It
sends a layer 3 channel_release message to the MS to release the connection and a deactivate_sacch
message to stop the BTS sending messages on the SACCH channel.
The MS releases then the layer 2 connection by sending a DISC message. The BTS acknowledges this
message by sending a UA and transmit to the BSC a release_indication message.
The BSC sends then a RF_channel_release message to the BTS. The BTS can now completely release
the dedicated channel and acknowledges the command by transmitting a
RF_channel_release_acknowledge to the BSC.
DISC (SDC
CH)
Release In
dication
H)
UA (SDCC Clear Com
plete
l Release
RF Channe
Return to
BCCH channel RF channe
l Release A
ck
6 SDCCH DIMENSIONING
We have seen in the previous chapter that the SDCCHs are used for signalling during call setups,
short message services and location updates (directed retry not presented here). This chapter focuses
on the SDCCH dimensioning. It defines what are the parameters of interest to perform such a
dimensioning based on the SDCCH procedure presented in chapter 5 above.
Directed retry procedure should be considered, but it is similar to TCH queuing procedure (SDCCH
holding time is increased) and it is not taken into account in the SDCCH dimensioning methodology
and tool presented below.
To realise a dimensioning of the SDCCH resources, it is necessary to quantify the different types of
transaction. It will lead to define a call mix. The typical B7 Alcatel call mix, given at busy hour, is the
following:
TRAFFIC MIX @ BH PER CALL
Mean TCH holding time 50 seconds
Mobile Orig. Call 60% percent
Mobile Term. Call 40% percent
Location Update 3 per call
IMSI Attach 0.5 per call
IMSI Detach 0.5 per call
Orig. SMS PtP 0.3 per call
Term. SMS PtP 0.7 per call
Table 1: Alcatel Reference call mix
Any SDCCH dimensioning study is based on the call mix values, which might be provided either by
marketing department (new network), measured (on existing network) or derived from assumptions.
The measurement might be realised either via A or Abis interface monitoring or using tools such as
AnaQOS or RNO.
On one hand, trace measurements provides more detailed data, such as Mobile terminated SMS or
Imsi attach values. Those data must be deduced from Imsi detach and Mobile originated SMS values,
when working with RNO or AnaQOS.
On the other hand, RNO or AnaQOS measurements can be realised on several days or even weeks
whereas trace measurements are restricted to a short period of time.
Whatever the measurement method used, the SDCCH congestion rate indicator allows detecting
non-accurate signalling channel dimensioning.
By default, we introduce three cell profiles based on the position of the cell compared to the Location
Area Border:
• Normal signalling
• High signalling
• Very high signalling
All the call mix parameters presented above are the same for the three types of profiles, except the
ratio LU_RATE = (LU + Imsi attach + Imsi detach) / TCH call, which is different for each profile:
• Normal signalling: LU_RATE = 1 (cell which is not at a Location area border)
• High signalling: LU_RATE = 4 (cell which includes a Location area border but with no specific
peak of LU)
• Very high signalling: LU_RATE = 8 (cell which includes a Location area subject to peaks of LU)
To dimension the number of SDCCH channels needed, the first step is to compute the SDCCH traffic
in Erlang. To do so, we need to process the SDCCH holding time. The SDCCH Holding Times (HT)
have been measured for the different network events presented in the SDCCH PROCEDURE chapter.
Those measurements have been realised with Alcatel test-bed. The average SDCCH holding time
and SDCCH usage per call are then deduced depending on the traffic mix parameter.
Procedure MOC MTC LU IMSI attach IMSI detach SMS SDCCH average HT (s) SDCCH usage per call (s)
SDCCH HT per procedure (ms) 3300 2850 4400 2970 2565 6500 - -
Alcatel call mix (LU+SMS) 0.6 0.4 3 0.5 0.5 1 4.26 25.59
No LU, No SMS 0.6 0.4 0 0.5 0.5 0 2.94 5.89
No LU, SMS 0.6 0.4 0 0.5 0.5 1 4.13 12.39
LU, No SMS 0.6 0.4 3 0.5 0.5 0 3.82 19.09
Knowing the SDCCH traffic per call, it is now necessary to obtain the number of calls per hour. This
value is based on the average call duration and on the traffic of the cell. The following formula is
used:
The traffic per call and traffic in the cell can be measured. For dimensioning purposes, it could be
better to dimension directly the number of SDCCH for the maximum traffic that the cell can handle.
In this case, the Erlang B formula, based on the number of available traffic TS and the blocking
probability, gives the traffic in the cell.
For instance, with 4 TRX, 29 TS reserved for voice traffic and a 2% blocking probability we obtain a
maximum traffic of 21.04 Erlang. The typical Alcatel call duration is 50 s (14 mErlang). It gives the
following number of calls at busy hour, Ncalls:
21.04
Ncalls = = 1503 calls per hour in a 4 TRX cell.
0.014
We can now derive the SDCCH traffic in the cell by multiplying the SDCCH usage per call by the
number of calls. The following formula gives the total SDCCH traffic in the cell:
SDCCH _ usage
SDCCH _ traffic = Ncalls ×
3600
Following the example presented above, we obtain:
12.39
SDCCH _ traffic = 1503 × = 5.17 Erlang at busy hour
3600
for a profile with no LU but with SMS (fifth row of Table 2: SDCCH Holding Time).
We want to determine the number of resources necessary to carry this traffic according a blocking
probability pbk. The Erlang B formula is used to derive the number of channels necessary given the
traffic to handle and the blocking probability.
Erlang B traffic model is based on the following assumptions:
• An infinite number of calling sources
• Random traffic arrival pattern (Poisson distribution)
• Blocked calls are cleared
• Hold times exponentially distributed
The third assumption, how to handle lost calls, is not exact when dealing with SDCCH traffic. The
figure below depicts the three options available when the station you are calling does not answer:
The LCC option assumes that once a call is placed and the server (network) is busy or not available,
the call disappears from the system. In essence, you give up and do something different. This is the
assumption made by the Erlang B law.
The LCH option assumes that a call will be in the system for the duration of the hold time, regardless
of whether or not the call was placed. In essence, you continue to redial for as long as the hold time
before giving up. Recalling, or redialing, is an important traffic consideration. Suppose 200 calls are
attempted. Forty receive busy signals and attempt to redial. That results in 240 call attempts, a 20%
increase. The trunk group is now providing an even poorer GoS than initially thought.
The LCD option means that once a call is placed, it remains in a queue until a server is ready to
handle it. Then it uses the server for the full holding time. This assumption is the one used by the
Erlang C law.
Assuming that the lost calls will clear the system (Erlang B) tends to understate the number of trunks
required; on the other hand, LCH overstates the number.
Using the Erlang B formula for dimensioning SDCCH channel is not exact since a Location Update,
for instance, would not be tried only once. It is therefore a kind of queuing system and not a total loss
system even if the immediate assignment reject failure, implemented in our BSS, prevents the MS to
repeat its SDCCH request in case of SDCCH congestion. Anyway, one must keep in mind that the use
of the Erlang B formula understates the number of SDCCH channels required.
We obtain finally:
Nchannels = ErlangB( SDCCH _ traffic, pbk )
6.6 Tool
An Excel tool, entitled “SDCCH_dim”, has been developed to allow a rapid computation of the
SDCCH configuration needed based on a precise call-mix. The inputs, enlighten in green, are the
following:
TRAFFIC MIX @ BH
Measured cell traffic 21.04 Erlang
Mean TCH holding time 50 seconds
Nb voice TRX in cell 4 TRX BCCH
Combined
TCH required blocking probability 2.00% percent
Not combined
SDCCH Required blocking probability 0.50% percent
inputs
Then, you have to press the Process button at the right hand side of the Excel sheet.
Process
The outputs of the tool, enlighten in light yellow, are the following:
Nb TCH TS 29 TS
Nb SDH TS 0 TS
outputs
Nb SDC TS 2 TS
Total SDCCH TS 2 TS
Processed SDCCH blocking probability 0.0550% percent
Maximum cell traffic 21.04 Erlang
Table 4: Outputs of the SDCCH dimensioning tool
6.7 Recommendations
In this chapter, the recommended number of SDCCH channels based on the typical Alcatel call mix
and the three types of profiles defined in paragraph 6.1 are presented. The table below gives those
values.
LU Profiles
TRX BCCH combined Normal High Very high
1 Yes 12 12 12
1 No 8 8 8
2 Yes 12 12 20
2 No 8 16 16
number of SDCCH channels
3 No 8 16 24
4 No 16 24 32
5 No 24 32 -
6 No 24 32 -
7 No 24 40 -
8 No 32 40 -
9 No 32 48 -
10 No 32 48 -
11 No 40 56 -
12 No 40 64 -
13 No 40 64 -
14 No 48 72 -
15 No 48 72 -
16 No 48 80 -
Table 5: Recommended SDCCH values
Remarks:
• SDCCH HTs have been set to 4s for all transactions except SMS where the holding time has
been set to 7s. This corresponds to values less optimistic than those measured under optimal
conditions in Alcatel premises (presented paragraph 6.3 above).
• Very High Signalling profile should not be implemented on cells with more than 4 TRX to avoid
TCU overload.
• Immediate assignment extended should reduce the CCCH load and might allow preventing
CCCH congestion even for high traffic cells. See Immediate assignment Extended in Release B5
functional feature description [10] for condition of application. SMS usage as well, which implies
long SDCCH holding time, should less impact CCCH load than classical voice traffic.
• DR TRE: the number of needed SDCCH is to be increased as DR TREs handle up to two times
the number of calls handled by FR TREs. The number of SDCCH is obtained by multiplying by 2
the number of SDCCH for FR TRE.
• The maximum number of SDCCH per TRX is:
- For a FUMO: 12 SDCCH
- Other TRE: 24 SDCCH
• Those maximum values are also function of the Abis multiplexing scheme as
presented on paragraph7 below
The Abis interface is impacted by the SDCCH allocation realised at Air interface level. The RSL
channels at Abis level carry the SDCCH load. To do so, the RSL throughput has to be compliant with
the number of SDCCH implemented on the TRXs.
The statistical 64K multiplexing is a new feature of the B6.2 release. The goal of this new feature is
twofold:
• To optimise the physical resource employment (the Abis Time slot and PCM) in order to
reduce the cost of Abis transmission
• To allow more SDCCH resources allocation and better response time than the static RSL 16K
The first point, optimisation of the physical resource, is obtained by multiplexing from 1 to 4 RSL and
the OML of a BTS on 1 Abis TS at 64kbit/s.
When the signalling statistical multiplexing is used, the Abis channels may be seen as a group of
Multiplexed Channel Block (MCB). A MCB connects 1, 2 or 4 TRX of a single BTS equipment
to a single TCU. A TCU may handle up to 4 MCB according to the limitation of 32 TCH per TCU.
Each MCB is made of 1 signalling channel (64 kbit/s) and 2 to 8 traffic TS.
The number of TRX multiplexed within the MCB is defined according to the signalling traffic
supported by the signalling channel.
The possible MCBs used over Abis are:
Hence, the MCB 64/4 and MCB64/2 allow both to carry 12 TRX (maximum number of TRX in one
BTS cabinet) on 1 Abis link with respectively, 27 TS and 30 TS occupied.
With the statistical 64K-multiplexing scheme, the number of SDCCH channels implemented per TRX
is limited to the maximum value allowed per TRX, that is to say:
• For a FUMO: 12 SDCCH
• Other TRE: 24 SDCCH
One should only pay attention that the sum of the SDCCH channels corresponding to the multiplexed
RSL is below or equal to 32 (limit of the TCUC), as presented in the following table.
Hence, the MCB64/2 allows implementing up to 2 SDDCH TS per TRX. Moreover, it is not
recommended for 16K static multiplexing to set BCCH and SDCCH on the same TRX. No such
limitation exits with statistical multiplexing, especially if MCB64/2 is applied. However, TCU load still
needs to be checked at BSC side.
As stated below, MCB64/2 and MCB64/1 are fully compatible with half-rate feature.
7.2.3 Throughput
For 16K static multiplexing the throughput is fixed and equal to 16 kbit/s. In the statistical
multiplexing mode, one, two or 4 RSL share a 64 kbit/s channel, which implies an instantaneous
throughput 4 times higher than the static multiplexing scheme.
Hence, statistical multiplexing 64K shall be better than the static multiplexing at 16 kbit/s. For
instance, power control response time shall be better when statistical scheme is implemented.
Statistical 64K should always be preferred to static multiplexing. It offers better RSL throughput whilst
limiting the number of Abis TS used compared to the 'no multiplexing' scheme.
If star configuration is implemented MCB64/2 ('high load') should be preferred to MCB64/4. It
represents the best trade-off between Abis TS occupancy and response time.
In this chapter, we present an example of SDCCH dimensioning for an Asian-Pacific operator. The
reference call mix is the following:
TRAFFIC MIX @ BH
Measured cell traffic 25.53 Erlang
Mean TCH holding time 50 seconds
Nb voice TRX in cell 5 TRX
TCH required blocking probability 2.00% percent
SDCCH Required blocking probability 0.50% percent
inputs
The number of SMS per call is 2.5 times above the reference B7 Alcatel call-mix. We consider a non-
combined cell with a very high profile (Imsi Attach+Imsi Detach+LU=8) and 5 voice TRX installed.
Cell Broadcast is not implemented. We obtain the following figures:
Nb TCH TS 34 TS
Nb SDH TS 0 TS
outputs
Nb SDC TS 5 TS
Total SDCCH TS 5 TS
Processed SDCCH blocking probability 0.4849% percent
Maximum cell traffic 25.53 Erlang
The MCB64/2 is recommended to carry the high load of signalling, especially on the first TRX
(CCCH+SDCCH).
9 CONCLUSION
With the rapid take off of SMS usage, a precise monitoring of the SDCCH resources is mandatory.
New ranges of application, like taxed SMS, will be launched in a near future and will require an SMS
quality of service follow-up to justify their cost to the user. The basement of such a QoS monitoring is
the right dimensioning of the SDCCH channels, which carry the SMS flows.
Anticipating SDCCH resources understatement can be realised if a close follow-up of the SDCCH
congestion indicator is realised with e.g. RNO warning reports. At this stage, the tool presented in
this document allows performing a precise re-dimensioning of the precious circuit resources.
The best trade-off between voice circuit and signalling channels will be provided.
Finally, a particular attention must be focused on the Abis multiplexing scheme and TCU load to
avoid jeopardising a good Air interface dimensioning either with an unsuitable Abis throughput or
with a high TCU load.
10 GLOSSARY
END OF DOCUMENT