SDCCH Usage and Dimension Ing

SDCCH Usage and Dimensioning
Site Vlizy Originator(s) E. SALOMON E. BEAUMONT
Mobile Networks Division PROFESSIONAL CUSTOMER SERVICES SDCCH USAGE AND

DIMENSIONING
METHODS
Domain Division Rubric Type Distrib. Codes
Network Design and Architecture MND/BU BSS/PCS/NMO/NDA Methods
RELEASED
PREDISTRIBUTION: MND/PCS Vlizy: Ch. Blachier MND/PCS/NOD Vlizy: F. Jarreau MND/BR AME OPERATIONS: Vlizy H. Forgeoux ABSTRACT: This document describes the management of the SDCCH channel and a methodology to dimension this resource. MND/SYT Vlizy: A. Freulon MND/ND Vlizy: A. Van Gysel
APPROVALS Name App. Ch. BLACHIER C. BRECHTMANN
Date
ALCATEL
File Sdcch_dimensioning.doc
Reference 3DF 01903 0010 PGZZA
Date 18/01/2002
Edition 01
Page 1/35
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorisation.
This page is left intentionally blank
ALCATEL
Date 18/01/2002
Edition 01
Page 2/35
SDCCH DIMENSIONING
ALCATEL
Date 18/01/2002
Edition 01
Page 3/35
TABLE OF CONTENT
1 2 3 4
HISTORY.......................................................................................................................................................................................6 REFERENCE DOCUMENTS ..................................................................................................................................................7 SCOPE.............................................................................................................................................................................................8 SDCCH PRESENTATION........................................................................................................................................................9 4.1 SIGNALLING CHANNELS DESCRIPTION ................................................................................................................................... 9 4.2 SDCCH USAGE...................................................................................................................................................................... 10 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 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 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 9 10
SDCCH DIMENSIONING EXAMPLE...............................................................................................................................32 CONCLUSION ...........................................................................................................................................................................33 GLOSSARY.................................................................................................................................................................................34
01 Ed
18/01/2002 DATE
CHANGE NOTE
Evolium/R&D APPRAISAL AUTHORITY
MCD/NS_UMTS/PCS/NDA ORIGINATOR
ALCATEL
Date 18/01/2002
Edition 01
Page 4/35
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
ALCATEL
Date 18/01/2002
Edition 01
Page 5/35
1
Ed. 01
HISTORY
Prop. 01 Date 20/12/01 Author NDA team Comments Creation
ALCATEL
Date 18/01/2002
Edition 01
Page 6/35
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] Rseaux GSM, 5me dition revue et augmente, 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
ALCATEL
Date 18/01/2002
Edition 01
Page 7/35
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.
ALCATEL
Date 18/01/2002
Edition 01
Page 8/35
SDCCH PRESENTATION
4.1 Signalling Channels Description

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. The signalling channel type can be defined using a 3 letters abbreviation: BCCH - Broadcast Control Channel CBCH - Cell Broadcast Channel CCCH - Common Control Channel FCCH - Frequency Correction Channel SACCH - Slow Associated Control Channel SCH - Synchronisation Channel SDCCH - Standalone Dedicated Control Channel
Those signalling channels are combined in the TRX TS: BCC: Main BCCH/CCCH of the Cell FCCH+SCH+BCCH+CCCH CBC: Combined BCCH, i.e. main BCCH/CCCH combined with 4 SDCCH channels FCCH+SCH+BCCH+CCCH+SDCCH/4+SACCH CCC: Multiple CCCH (BCCH+CCCH) - not yet used SDC: Specifies that the physical channel concerned carries 8 SDCCH channels together with their SACCHs SDCCH/8+SACCH/8 TCH: Traffic Channel (can be used as a full rate or half rate channel) BLO: Blocked Channel due to radio resources CBH: Main combined BCCH with Cell Broadcast Channel FCCH+SCH+BCCH+CCCH+SDCCH/3+SACCH/3+CBCH SDH: Specifies that the physical channel concerned carries 7 SDCCH channels together with their SACCHs with Cell Broadcast Channel SDCC/7+SACCH/7+CBCH
ALCATEL
Date 18/01/2002
Edition 01
Page 9/35
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. One SDCCH channel offers a throughput of 800 bit/s.
4.2 SDCCH USAGE

Call set-up is required to establish connection between a Mobile Station (MS) and the Network SubSystem (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 Mobile Management Calls DescriptionThese 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. These calls, e.g. SMS and Supplementary Service (SS) calls, pass small amounts of information. Therefore, only a signalling channel is used. 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.
Service Calls User Traffic Calls
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.
ALCATEL
Date 18/01/2002
Edition 01
Page 10/35
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.
ALCATEL
Date 18/01/2002
Edition 01
Page 11/35
SDCCH PROCEDURE
5.1 SDCCH channel activation

The MS initiates a call (MOC) by sending a channel_request message, with a Random Access Information Value (REF). The REF includes an establishment cause and a random number, used for authentication. It is transmitted on the RACH channel. The RACH channel is associated with the CCCH channel, which the MS is monitoring while in idle mode. In case of Mobile Terminated Call (MTC), the same procedure is followed except that the channel_request message comes in reply to a paging_request command. The establishment cause field of the REF specifies: An emergency call Call re-establishment Response to paging MS originated speech call Location update Service call (SMS, etc)
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.
ALCATEL
Date 18/01/2002
Edition 01
Page 12/35
MS
Mobile Terminated
BTS
mmand Paging co up paging gro CCCH TS+
BSC
Paging +cell list IE
MSC
quest Paging re TMSI/IMS I
Mobile Originated+Terminated
Channel R equest (RA CH) REF
Channel R equired REF+RFN+ TA Channel Activation +power
REF Stored in MS memory
SDCCH Allocation
TA+SDCCH Channel A
ctivation A ck
MS compares message with ent AGCH te Assignm REF in memory Immedia +RFN+REF TA+SDCCH Switch to SDCCH
SABM cm+Servic e Request UA quest Service Re Service Request must match original sent by MS in the SABM
mand Assign com Immediate RFN+REF +power+ TA+SDCCH
Establish In dication cm+Servic e Request
SCCP Conn ectio cm+Servic
n Request
e Request
firm ection Con SCCP Conn
REF: RFN: TA: Cm: Power: SABM: Service Request: UA:
Random Access Information Value Reduced Frame Number Timing Advance Classmark MS power, BTS power Set Asynchronous Balanced Mode Initial layer 3 message including the MS identity and classmark Unnumbered Acknowledgement
Figure 1: Radio link establishment for Mobile Originated/ Terminated Call The MS continues to transmit channel_request messages until it receives a response. If no response is received before the MS has retransmitted a predefined number of retries, the MS: Displays a network error message for all calls except location updates Performs automatic reselection for location update calls. This means that the MS attempts random access on a different cell.
ALCATEL
Date 18/01/2002
Edition 01
Page 13/35
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 BTS sends the immediate_assignment message to the MS on the AGCH. 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.
ALCATEL
Date 18/01/2002
Edition 01
Page 14/35
For an MS originated call, the layer 3 message from the MS contains: An information Element (IE) indicating: CM service request (speech, SMS, emergency call) Location updating request (Location updating procedure) IMSI detach indication (MS power off) CM re-establishment request (after a failure) The MS identity
The MS classmark The network uses this message to decide which call negotiation procedures are required and whether to assign a TCH. The BTS sends an establish_indication message to the BSC to indicate that the MS has connected. The BSC stops the guard timer, extracts the classmark information and initiates an SCCP connection with the MSC. 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
ALCATEL
Date 18/01/2002
Edition 01
Page 15/35
5.2 Service Request
5.2.1 Traffic Channel
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. The MS sends then an assignment_complete message to the BSC. The BSC can then release the SDCCH resource.
ALCATEL
Date 18/01/2002
Edition 01
Page 16/35
MS
BTS
BSC
nt Request Assignme pe+cm Channel ty
MSC
TCH Allocation
Physical co ntext requ est
Physical co ntext confi rm TA+power SACCH update TA+power Channel A ctivation
+power cipher+DTX TCH+TA+ Channel A ctivation A ck Power+TA mand Assign com TCH
Assign com
ma
) nd (SDCCH
Release SDCCH
TCH SABM (FA CCH) ) UA (FACCH
Assignme nt comple te (FACCH ) Assignme nt comple te
Initiate SDCCH Release
DTX: FACCH: SACCH:
Discontinuous Transmission Fast Associated Control Channel Slow Associated Control Channel
Figure 2: Signalling to traffic channel transfer An authentication and ciphering procedure might take place before releasing the SDCCH channel to ensure that the subscriber identification (IMSI, TMSI) and IMEI are valid and to encrypt the rest of the data exchanged. 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.
ALCATEL
Date 18/01/2002
Edition 01
Page 17/35
MS
BTS
SDCCH channel allocation
BSC
MSC
Switch to SDCCH
SABM e Request UA Service Re quest
cm+Servic
Establish In dication cm+Servic e Request
SCCP Conn ection Req uest cm+Servic e Request firm ection Con SCCP Conn
Authentication and Ciphering

SABM SAPI=3 UA SAPI=3 Establish In dication SAPI=3
SMS Control Protocol
- Data - Ack
SMS Control Protocol
- Data SMS Control Protocol SMS Control Protocol
- Ack
Initiate connection Release
SAPI:
Service Access Point Identifier
Figure 3: SMS transmission on SDCCH channel The number of bytes for SMS cannot be estimated because it depends on the message content. Thus, it is necessary to consider an average SMS length.
ALCATEL
Date 18/01/2002
Edition 01
Page 18/35
5.2.3 Location Update 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. Change of location area The MS detects a new Location Area Identity (LAI) in the BCCH when the current call has finished. The MS camps on a cell with a different location area code to the one in the MS memory. The MS initiates then a LU procedure. This saves the system performing several LU if the MS is handed over several times during a call.
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.
ALCATEL
Date 18/01/2002
Edition 01
Page 19/35
5.2.4 IMSI attach/detach 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. Initiation of the IMSI attach/detach procedure is controlled by a parameter in the BSS, Attach_detach_allowed. When this parameter is set, the BSS broadcasts system information on all cell indicating that the network supports the IMSI attach/detach feature. MSs, which have successfully connected and logged themselves onto the network are then obliged to perform IMSI attach/detach procedure.
5.3 SDCCH channel release

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.
ALCATEL
Date 18/01/2002
Edition 01
Page 20/35
MS
BTS
elease Channel R SACCH Deactivate Release In dication l Release RF Channe
BSC
Clear Com mand
MSC
CCH) elease (SD Channel R DISC (SDC CH) H)
UA (SDCC
Clear Com plete
Return to BCCH channel
RF channe l Release A ck
Figure 4: Release of the SDCCH channel
ALCATEL
Date 18/01/2002
Edition 01
Page 21/35
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.
6.1 Call mix

We have seen that the SDCCH are implied in different procedures: Location update: periodic, new updating, IMSI attach/detach SMS (Short Message Service, originating or terminated) Originating and Terminating calls
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:
Mean TCH holding time Mobile Orig. Call Mobile Term. Call Location Update IMSI Attach IMSI Detach Orig. SMS PtP Term. SMS PtP
TRAFFIC MIX @ BH PER CALL 50 seconds 60% percent 40% percent 3 per call 0.5 per call 0.5 per call 0.3 per call 0.7 per call
Table 1: Alcatel Reference call mix Call mix varies related to: Cell: The TCH traffic induced by subscribers and average number of LU/call are cell dependent Hour: By default the dimensioning is always realised for the busy hour Period: Traffic intensity and distribution may be modified according to seasons/ special events,
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.
ALCATEL
Date 18/01/2002
Edition 01
Page 22/35
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)
6.2 SDCCH holding time and SDCCH usage per call

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 SDCCH HT per procedure (ms) Alcatel call mix (LU+SMS) No LU, No SMS No LU, SMS LU, No SMS MTC 3300 0.6 0.6 0.6 0.6 2850 0.4 0.4 0.4 0.4 LU 4400 3 0 0 3 IMSI attach IMSI detach SMS SDCCH average HT (s) SDCCH usage per call (s) 2970 2565 6500 0.5 0.5 1 4.26 25.59 0.5 0.5 0 2.94 5.89 0.5 0.5 1 4.13 12.39 0.5 0.5 0 3.82 19.09
Table 2: SDCCH Holding Time Those values can also be retrieved using RNO or AnaQOS.
ALCATEL
Date 18/01/2002
Edition 01
Page 23/35
6.3 Number of calls

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:
Ncalls =
traffic _ in _ the _ cell traffic _ per _ call
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:
Ncalls =
21.04 = 1503 calls per hour in a 4 TRX cell. 0.014
6.4 SDCCH traffic

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 _ traffic = Ncalls

Following the example presented above, we obtain:
SDCCH _ usage 3600
SDCCH _ traffic = 1503
12.39 = 5.17 Erlang at busy hour 3600
for a profile with no LU but with SMS (fifth row of Table 2: SDCCH Holding Time).
ALCATEL
Date 18/01/2002
Edition 01
Page 24/35
6.5 Number of SDCCH TS

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:
Lost Calls Cleared (LCC) Lost Calls Held (LCH) Lost Calls Delayed (LCD) Figure 5: Handling of traffic 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.
ALCATEL
Date 18/01/2002
Edition 01
Page 25/35
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 )

For our previous example, with a pbk equal to 0.5%, it gives:
Nchannels = ErlangB (5.17,0.005) = 15 channels Now that we have processed the number of channels, we can derive the number of TS needed. If the TS are of the SDC type (please see 4.1 above), 8 channels are available per TS. Thus, to cope with 15 channels, it will be necessary to implement 2 TS.
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 Mean TCH holding time Nb voice TRX in cell TCH required blocking probability SDCCH Required blocking probability Mobile Orig. Call Mobile Term. Call Location Update IMSI Attach IMSI Detach Orig. SMS PtP Term. SMS PtP 21.04 50 4 2.00% 0.50% 60% 40% 0 0.5 0.5 0.3 0.7
Erlang seconds TRX percent percent percent percent per call per call per call per call per call
BCCH Combined Not combined
inputs
SDH
None 1 SDH 2 SDH
Table 3: Inputs of the SDCCH dimensioning tool By default, the traffic in the cell (in blue) is the maximum allowed by the blocking probability and its configuration. Note that since GPRS traffic has no impact on SDCCH dimensioning, the traffic to be taken into account is the one provided only by the circuit resources. If any GPRS dedicated TRXs exist, they should not be taken into account for SDCCH dimensioning.
ALCATEL
Date 18/01/2002
Edition 01
Page 26/35
After entering your input in the table, you have to choose: Whether the BCCH is in combined or not combined mode (Option buttons in BCCH group box) Whether the cell broadcast is introduced and with one or two channels (Option buttons in SDH group box)
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 Nb SDH TS Nb SDC TS Total SDCCH TS Processed SDCCH blocking probability Maximum cell traffic 29 0 2 2 0.0550%
TS TS TS TS percent 21.04 Erlang
outputs
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.
TRX 1 1 2 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 BCCH combined Yes No Yes No No No No No No No No No No No No No No No Normal 12 8 12 8 8 16 24 24 24 32 32 32 40 40 40 48 48 48 LU Profiles High Very high 12 12 8 8 12 20 16 16 16 24 24 32 32 32 40 40 48 48 56 64 64 72 72 80 -
Table 5: Recommended SDCCH values
ALCATEL
Date 18/01/2002
number of SDCCH channels

Edition 01
Page 27/35
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
ALCATEL
Date 18/01/2002
Edition 01
Page 28/35
IMPACT ON ABIS RESOURCE
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
7.1 Optimisation of the Abis resource

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: MCB type MCB 64/4 MCB 64/2 MCB 64/1 TS used on Abis interface 9 5 3 Description One signalling channel at 64 kbit/s and 4 TRX One signalling channel at 64 kbit/s and 2 TRX One signalling channel at 64 kbit/s and 1 TRX
Table 6: Multiplexed Channel Block presentation 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.
ALCATEL
Date 18/01/2002
Edition 01
Page 29/35
7.2 SDCCH Allocation and Response time

The static 16K has several restrictions: Each TRX is carrying a maximum of one SDCCH TS. Not compatible with the Half-Rate mode. Maximum throughput of the RSL channels is 16 kbit/s.
The statistical 64K allows overcoming those restrictions.
7.2.1 Maximum number of SDCCH 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. MCB type MCB 64/2 MCB 64/4 MCB 64/2 Configuration 2 TRX FR, BCCH 4 TRX FR, BCCH 2 TRX DR, BCCH SDCCH # 32 32 32
Table 7: Maximum SDCCH number per MCB type 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.
ALCATEL
Date 18/01/2002
Edition 01
Page 30/35
7.2.2 Compatibility with Half-Rate Mode As stated below, MCB64/2 and MCB64/1 are fully compatible with half-rate feature. MCB type MCB 64/4 MCB 64/2 MCB 64/1 Compatibility Full Rate only Dual Rate or Full Rate Dual Rate or Full Rate
Table 8: MCB scheme compliance with Dual Rate
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. Hence, MCB64/2 is strongly advised for the following configuration: The operator wants to concentrate the SDCCH on a few TRXs Multi-band cell (possibility to have SDCCH of the outer zone on the same MCB) Cell with very high signalling load (LA border, high SMS) or cell with more than 6 TRX FR (high CCCH load) Cell with GPRS, without Master PDCH, and with very good performances required (congested RSL will slow down the TBF establishment) High paging rate (LA > 100 000 users or more than 28 paging/s/cell)
7.3 Abis Interface recommendation

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.
ALCATEL
Date 18/01/2002
Edition 01
Page 31/35
SDCCH DIMENSIONING EXAMPLE
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 Mean TCH holding time Nb voice TRX in cell TCH required blocking probability SDCCH Required blocking probability Mobile Orig. Call Mobile Term. Call Location Update IMSI Attach IMSI Detach Orig. SMS PtP Term. SMS PtP 25.53 50 5 2.00% 0.50% 60% 40% 7 0.5 0.5 1 1.5
Erlang seconds TRX percent percent percent percent per call per call per call per call per call
The number of SMS per call is 2.5 times above the reference B7 Alcatel call-mix. We consider a noncombined 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 Nb SDH TS Nb SDC TS Total SDCCH TS Processed SDCCH blocking probability Maximum cell traffic 34 0 5 5 0.4849%
inputs
TS TS TS TS percent 25.53 Erlang
In this case, one SDCCH channel per TRX should be implemented. The MCB64/2 is recommended to carry the high load of signalling, especially on the first TRX (CCCH+SDCCH).
ALCATEL
outputs
Date 18/01/2002
Edition 01
Page 32/35
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.
ALCATEL
Date 18/01/2002
Edition 01
Page 33/35
10 GLOSSARY
A Abis AC BCCH BIE BSC BSS BTS CCCH CIC CM CPRA DCN DR DRFU DTC DTX EFR FACCH FR G703 Gb GCH GPRS GPU GSL HLR IMEI IMSI LAPD MD MFS MS A interface is between BSC and MSC Abis interface is between BTS and BSC Alternative Current Broadcast Control Channel Base station Interface Equipment Base Station Controller Base Station Subsystem Base Transceiver Station Common Control Channel Channel Identity Code ClassMark Common Processor A Digital Cross-connect Network Dual Rate Dual Rate Frame Unit Digital Trunk Controller Discontinuous Transmission Enhanced Full Rate Fast Associated Control Channel Full Rate Physical/electrical characteristics of hierarchical digital interfaces Telecommunication interface between MFS and SGSN GPRS Channel (Ater interface) General Packet Radio Service GPRS Processing Unit GPRS Signalling Link Lome Location Register International Mobile Equipment Identity International Mobile Subscriber Identity Link Access Protocol on D channel Multi Drop Multi-BSS Fast packet Server Mobile Station
ALCATEL
Date 18/01/2002
Edition 01
Page 34/35
MSC NE NSS O&M PSTN PDCH QoS REK RSL RTC SABM SACCH SDCCH SGSN SM SS7 SUM SUMP TA TC TCH TCUA TCUC TMA TMSI TRAU TRCU TRX TS TSU UA VLR WBC
Mobile Switching Centre Network Element Network Sub-System Operation and Maintenance Public Switched Telephone Network Packet Data Channel (Air and Abis Interface) Quality of Service Range Extension Kit Radio Signalling Link Remote Tuneable Combiner Set Asynchronous Balanced Mode Slow Associated Control Channel Stand Alone Dedicated Control Channel Serving GPRS Support Node Sub Multiplexer Signaling System number 7 Station Unit Module Station Unit Module PCM Timing Advance TransCoder Traffic Channel Terminal Control Unit A Terminal Control Unit C Tower Mounted Amplifier Temporary Mobile Subscriber Identity Transcoder/Rate Adaptation Unit Transcoder Rate adaptation Control Unit Transmitter / Receiver (logical view) Time slot Terminal Sub Unit Unnumbered Acknowledgement Visitor Location Register Wide Band Combiner
END OF DOCUMENT
ALCATEL
Date 18/01/2002
Edition 01
Page 35/35

SDCCH Usage and Dimension Ing

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SDCCH Usage and Dimension Ing

Hochgeladen von

Copyright:

Verfügbare Formate

SDCCH Usage and Dimensioning

Site Vlizy Originator(s) E. SALOMON E. BEAUMONT

Mobile Networks Division PROFESSIONAL CUSTOMER SERVICES SDCCH USAGE AND

Domain Division Rubric Type Distrib. Codes

Network Design and Architecture MND/BU BSS/PCS/NMO/NDA Methods

APPROVALS Name App. Ch. BLACHIER C. BRECHTMANN

Reference 3DF 01903 0010 PGZZA