NED GSM Interfaces and Counter

8/10/2019 NED GSM Interfaces and Counter

http://slidepdf.com/reader/full/ned-gsm-interfaces-and-counter 1/212

1 Traffic Measurement

DN9813827Issue 10-0 en

# Nokia Corporation 1 (212)

BSC3119Nokia BSC/TCSM, Rel. S12, ProductDocumentation, v.1



The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is intended for the useof Nokia's customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be reproduced or transmitted in any form or means without the

prior written permission of Nokia. The document has been prepared to be used by professionaland properly trained personnel, and the customer assumes full responsibility when using it.Nokia welcomes customer comments as part of the process of continuous development andimprovement of the documentation.

The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding butshall be defined in the agreement made between Nokia and the customer. However, Nokia hasmade all reasonable efforts to ensure that the instructions contained in the document areadequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the document.

Nokia's liability for any errors in the document is limited to the documentary correction of errors.NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENTOR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARYLOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright according tothe applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

Other product names mentioned in this document may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright © Nokia Corporation 2007. All rights reserved.

2 (212) # Nokia Corporation DN9813827Issue 10-0 en




Contents

Contents 3

List of tables 4

List of figures 5

Summary of changes 9

1 1 Traffic Measurement 11

2 Counters of Traffic Measurement 23

3 Signalling charts of Traffic Measurement 121

4 Signalling charts of Dual Transfer Mode 193



Contents



List of tables

Table 1. Measurement description of Traffic Measurement 11

Table 2. SDCCH attempts counters 11

Table 3. SDCCH success counters 12

Table 4. SDCCH failure counters 12

Table 5. TCH requests and attempts counters 13

Table 6. TCH success counters 14

Table 7. TCH failure counters 16

Table 8. Other counters 18

Table 9. GPRS counters 19

Table 10. Spare counters 20





List of figures

Figure 1. Basic call without counters 122

Figure 2. Basic call with counters 123

Figure 3. Basic call with priority subscriber 124

Figure 4. FACCH call setup due to SDCCH congestion without counters 125

Figure 5. FACCH call setup due to SDCCH congestion with counters 126

Figure 6. FACCH call setup due to SDCCH congestion, no free TCH channel.Optional software directed retry is not activated 127

Figure 7. Normal release 128

Figure 8. Basic call, no free TCH and queuing or directed retry is not allowed 129Figure 9. Successful TCH queuing 130

Figure 10. Basic call, no free TCHs, unsuccessful queuing and directed retry notactivated 131

Figure 11. TCH assignment failure with cause switch_circuit_pool, queuing anddirected retry not allowed 132

Figure 12. Unsuccessful TCH activation 133

Figure 13. Unsuccessful TCH activation, timer expires while waiting for CHANNEL_ACTIVATION_ACK message 134

Figure 14. TCH assignment failure 135

Figure 15. TCH assignment failure, MSC sends CLEAR_COMMAND message 136

Figure 16. CONNECTION_FAILURE message with cause transcoder_failure duringa call 137

Figure 17. TRX or TSL is blocked with different causes during a call 138

Figure 18. SDCCH congestion, FACCH call setup is not activated 139

Figure 19. Unsuccessful SDCCH activation 140

Figure 20. Unsuccessful SDCCH activation, timer expires while waiting for CHANNEL_ACTIVATION_ACK message 141

Figure 21. Connection failure during SDCCH assignment 142

Figure 22. SDCCH assignment failure 143

Figure 23. Unsuccessful SDCCH activation, timer expires while waiting for PHYSICAL_CONTEXT_CONFIRM message 144

Figure 24. TRX/TSL is blocked with different causes during an SDCCH channel



List of figures



activation 145

Figure 25. Successful trunk reservation. Counters updated: 001040, 001041 andbasic call counters, see Figure 2. 146

Figure 26. Unsuccessful trunk reservation 147

Figure 27. Successful internal intra-cell handover. Counters 001090 and 001091 areupdated only with underlay overlay handover. 148

Figure 28. Internal intra-cell HO, successful TCH queuing 149

Figure 29. Unsuccessful internal intra-cell handover, timer expires while waiting for CHANNEL_ACTIVATION_ACK message 151

Figure 30. Unsuccessful internal intra-cell handover, CONNECTION_FAILUREmessage with cause remote_transcoder_failure comes to the targetchannel 152

Figure 31. Unsuccessful internal intra-cell handover, timer expires on the sourcechannel, call cleared 153

Figure 32. Unsuccessful underlay overlay internal intra-cell handover, queuing notallowed 154

Figure 33. Internal intra-cell handover, unsuccessful TCH queuing 155

Figure 34. Internal directed retry 157

Figure 35. Successful internal inter-cell handover 158

Figure 36. Unsuccessful internal inter-cell handover 159

Figure 37. Successful external handover, target 160

Figure 38. Successful external handover, source 161

Figure 39. Unsuccessful external handover, source BSC, timer expires while waitingfor CLEAR_COMMAND message 162

Figure 40. Unsuccessful external handover, MS sends a handover failure 163

Figure 41. Successful traffic reason handover, source 164

Figure 42. Successful SDCCH internal intra-cell handover 165

Figure 43. Unsuccessful SDCCH internal intra-cell handover, timer expires whilewaiting for CHANNEL_ACTIVATION_ACK message 166

Figure 44. Unsuccessful SDCCH internal intra-cell handover, unsuccessful channelactivation 167

Figure 45. Unsuccessful SDCCH internal intra-cell handover,CONNECTION_FAILURE message comes to the target channel duringhandover 168

Figure 46. Successful SDCCH internal inter-cell handover 169





Figure 47. Unsuccessful SDCCH internal inter-cell handover, BTS sendsCONNECTION_FAILURE message 170

Figure 48. Successful SDCCH external handover target 171

Figure 49. Successful SDCCH external handover source. No countersupdating. 171

Figure 50. Unsuccessful SDCCH external handover, timer expires while waiting for CLEAR_COMMAND message 172

Figure 51. Successful forced release 173

Figure 52. Unsuccessful forced release 174

Figure 53. Unsuccessful forced release with external handover 175

Figure 54. Successful forced handover 176

Figure 55. Unsuccessful forced handover 177

Figure 56. Unsuccessful forced handover with external handover 178

Figure 57. Reconfiguration from TCH to SDCCH 179

Figure 58. Normal call 180

Figure 59. Mobile originated HSCSD call setup 181

Figure 60. Successful internal inter-cell handover for HSCSD, target cell allocationsand activations for three channels 182

Figure 61. A CONNECTION_FAILURE message which comes during anHSCSD 183

Figure 62. Internal intra-cell direct access from a regular DCCH to the super-reuseTRX. Optional software direct access to super-reuse TRX in IUOactivated. 184

Figure 63. Unsuccessful internal intra-cell direct access from regular DCCH to thesuper-reuse TRX due to lack of resources. Optional software directaccess to super-reuse TRX in IUO activated. 185

Figure 64. Timer T3107 expires while waiting for ASSIGNMENT_COMPLETEmessage 186

Figure 65. Average counter updating 187

Figure 66. Successful handover due to DADL/B 188

Figure 67. Unsuccessful DADL/B handover due to lack of resources 188

Figure 68. Successful BSC controlled TRHO 189

Figure 69. Unsuccessful BSC controlled TRHO 189

Figure 70. Dropped call between ASSIGNMENT COMPLETE and



List of figures



DISCONNECT 190

Figure 71. Dropped call between ASSIGNMENT COMPLETE and RF CHANNELRELEASE ACK 191

Figure 72. MO DTM call establishment 194

Figure 73. MT DTM call establishment 195

Figure 74. DTM call reallocation; too high CS connection interference 196

Figure 75. DTM call reallocation; inadequate PS connection quality 197

Figure 76. DTM call; internal inter-cell handover; CS connection power budget 198

Figure 77. DTM call; internal inter-cell handover; lack of resources in the PSterritory 199

Figure 78. DTM call; external handover, source BSC 200Figure 79. DTM call; external handover, target BSC 201

Figure 80. DTM call release initiated by the MS 202

Figure 81. DTM call release; packet data transfer end 203

Figure 82. DTM REQUEST rejected when IMSI data not available 204

Figure 83. Unsuccessful MO DTM; activation of a CS TCH in the PS territory fails,timer expires while waiting for CHANNEL ACTIVATION ACK 205

Figure 84. Unsuccessful MT DTM; activation of a CS TCH in the PS territory fails,

timer expires while waiting for CHANNEL ACTIVATION ACK 206Figure 85. Unsuccessful MT DTM; DTM ASSIGNMENT FAILURE received 207

Figure 86. Timer T3107 expires while waiting for ASSIGNMENT COMPLETE 208

Figure 87. DTM call reallocation failure; DTM ASSIGNMENT FAILURE received 209

Figure 88. DTM CS connection drops after ASSIGNMENT COMPLETE;CONNECTION FAILURE received 210

Figure 89. DTM CS connection drops after ASSIGNMENT COMPLETE; RELEASEINDICATION not received 211





Summary of changes

Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Changes made between issues 10 and 9 –1

Related topics revised in Chapter 1.

Call phase information added to updated fields of counters in Chapter 2, whereapplicable.

New counters 001231 – 001234 added. Spare counters 001192, 001193, 001217and 001218 changed to real counters. Counters 001184, 001196, 001198,001199, and 001204 – 001207 modified.

Counters 001150 – 001153 changed to be no longer in use and signalling chart 66removed because Dynamic Hot Spot is no longer supported.

Counters 001209 and 001210 changed to be not in use because Enhanced Qualityof Service is not supported in S12. Enhanced Quality of Service will be availablein S13.

New signalling charts 70 and 71 added, and signalling charts 13, 15, 16, 17, 27,29, 34, 35, 38, 42, 46, and 64 updated in Chapter 3.

Signalling charts of Dual Transfer Mode, which contains some signalling chartsrelated to counters 001233 and 001234, has been added.

Editorial changes made.

Changes made between issues 9 –1 and 9

Spare counter 001216 taken into use.

Signalling charts of Traffic Measurement counters 1086 and 1089 have beenupdated. Counter names of 1086 and 1089 have been updated.



Summary of changes



Changes made between issues 9 and 8 –1

New counters 001204 — 001230 have been added.

Description of the counter number 001003 has been updated.

Counters number 001149 and 001194 have been modified.

Measurement description table has been added.

The name of the document and of Chapter 1 has been changed from BSC Counters: Traffic Measurement to1 Traffic Measurement.

The document has been revised throughout to comply with the latest documentation standards.





1 1 Traffic MeasurementThe BSC traffic measurement registers information related to the stand alonededicated control channel (SDCCH) and traffic channels (TCH). The BSC trafficmeasurement counters are divided into seven different classes. There are countersregarding the number of attempts to seize TCHs and SDCCHs, successful calls,lengths of the queue, and the reasons for failures. This measurement collects oneset of results for each cell. Signalling charts are drawn with the accuracy of message interface.

Measurement description

Table 1. Measurement description of Traffic Measurement

Measurement

Measurement ID

Measurement abbreviation

Traffic Measurement

1

TRAFFICProduct BSC

Product software release S1

Target name BTS

Measurement counters

. SDCCH attempts counters

Table 2. SDCCH attempts counters

Counter Counter number Seizure attempts 001000

SDCCH seizure attempts for MOC 001135

SDCCH seizure attempts for MTC 001136

Dynamic SDCCH reconfiguration at tempt 001154

SDCCH LU attempts 001231






. SDCCH success counters

Table 3. SDCCH success counters

Counter Counter number Success seizure for HO 001006

Success seizure for immediate assignment 001007

. SDCCH failure counters

Table 4. SDCCH failure counters

Counter Counter number Seizure attempts with busy SDCCH 001001

Transactions failed due to BSS failure 001002

Transactions failed due to radio failure 001003

Transact. failed due radio on source channel duringHO

001004

Transact. failed due radio on target channel duringHO

001005

SDCCH activation failure 001027

SDCCH Abis problems 001033

SDCCH A interface problems 001034

SDCCH LAPD failure 001035

SDCCH BTS failure 001036

SDCCH user actions 001037

SDCCH BCSU reset 001038

SDCCH network actions 001039

SDCCH activation failure call 001072

SDCCH activation failure target 001074

SDCCH Abis failure call 001075

SDCCH Abis failure source 001076

SDCCH Abis failure target 001077

SDCCH A interface failure call 001078

SDCCH A interface failure source 001079

SDCCH A interface failure target 001080





Table 4. SDCCH failure counters (cont.)

Counter Counter number Unsuccess immediate assignment SDCCH attempt 001155

SDCCH failures in phase 3 001201

Error indication messages during Location Update 001203

SDCCH LU attempts fail 001232

. TCH requests and attempts counters

Table 5. TCH requests and attempts counters

Counter Counter number TCH request success and unsuccess 001010

Call attempts in the queue 001016

Handover attempts in the queue 001017

TCH call request 001026

Trunk reservation invocations 001040

TCH requests FACCH call setup 001043

Traffic reason HO requests 001052

Traffic reason HO enquiries 001053Forced release assign request at tempts 001054

Forced HO assign request attempts 001055

Queuing allowed assign request attempts 001056

Queuing not allowed assign request attempts 001057

Forced release HO request attempts 001062

Forced HO HO request attempts 001063

Queuing allowed HO request attempts 001064

Queuing not allowed HO request attempts 001065

TCH requests underlay overlay 001090

TCH seizure underlay overlay 001091

Priority subscriber TCH requests 001095

TCH seizure attempt due SDCCH congestion 001098

Full TCH requests success unsuccess 001102

Half TCH requests success unsuccess 001103

TCH requests full preferred 001104






Table 5. TCH requests and attempts counters (cont.)

Counter Counter number TCH requests half preferred 001105

Full TCH requests FACCH call 001123

TCH FACCH call channel rate not defined 001124

TCH seizure attempts for MOC 001137

TCH seizure attempts for MTC 001138

Queued urgent handover attempts 001142

TCH requests for 14.4k data calls 001156

HSCSD transparent TCH request 001158

HSCSD request for call setup 001160HSCSD TCH request for HO 001161

TCH request for a BSC controlled TRHO procedure 001167

DADLB start due to exceeded load 001172

TCH requests for AMR call 001184

TCH requests for 9.6k data calls 001189

TCH requests for call attempt 001192

HO commands in outgoing MSC-controlled handover 001195

HO commands in outgoing BSC –controlled handover 001196

Assignment commands in intra-BTS handover 001197

. TCH success counters

Table 6. TCH success counters

Counter Counter number Success TCH seizure for HO 001008

Success TCH seizure for normal assignment 001009

Success trunk reservation invocations 001041

TCH seizure FACCH call setup 001044

Forced releases 001070

Forced handovers 001071

Priority subscriber success TCH seizure 001096

TCH seizure due SDCCH congestion 001099

Success full TCH seizure 001106







Table 7. TCH failure counters

Counter Counter number TCH request rejected due to lack 001011

Transactions ended due to BSS problem 001012

Transactions ended due to radio failure 001013

Transact. ended due source channel failure duringHO

001014

Transact. ended due target channel failure during HO 001015

Not served queued call attempts 001024

Not served queued HO attempts 001025

TCH activation failure 001028

TCH transcoder failure 001029

TCH transcoder failure source 001030

TCH transcoder failure target 001031

Trunk reservation invocations result refused 001042

TCH Abis problems 001045

TCH LAPD failure 001046

TCH BTS failure 001047

TCH user actions 001048

TCH BCSU reset 001049

TCH network actions 001050

TCH A interface problems 001051

Forced release assign request failed 001058

Forced HO assign request failed 001059

Queuing allowed assign request failed 001060

Queuing not allowed assign request failed 001061

Forced release HO request failed 001066

Forced HO HO request failed 001067

Queuing allowed HO request failed 001068

Queuing not allowed HO request failed 001069

TCH activation failure call 001081

TCH activation failure target 001083

TCH Abis failure call 001084

TCH Abis failure source 001085

TCH Abis failure new 001086





Table 7. TCH failure counters (cont.)

Counter Counter number TCH A interface failure call 001087

TCH A interface failure source 001088

TCH A interface failure new 001089

TCH rejected requests underlay overlay 001092

Non-priority subscriber refused TCH requests 001097

Trunk TCH rejected FR requests 001100

Trunk TCH rejected HR requests 001101

Rejected TCH requests due lack FR 001118

Rejected TCH requests due lack HR 001119Full TCH rejected requests due HR traffic 001120

Half TCH rejected requests due FR traffic 001121

TCH rejected due requested channel A interfacecircuit

001122

Ended due transcoder FR rate 1 001127



Ended due transcoder HR rate 1 001130



Full TCH transaction failures 001133

Half TCH transaction failures 001134

TCH release due to radio failure 001139

TCH release due to BSS failure 001140

TCH seizure failure due to congestion 001141

Queued urgent HO attempts not served 001147

TCH request rejected due to bad quality in adjacents 001151

TCH req rej when qual betw good and bad in adj 001153

HSCSD connection releases due to failure 001164

TCH request for direct access rejected due to lack 001166

Rej TCH seiz for BSC contr TRHO due lack of res 001169

TCH request in DADLB HO rejected 001171

TCH drop due to too low RX level 001194






Table 7. TCH failure counters (cont.)

Counter Counter number TCH releases due to radio failures, updated inphases 9-11

001198

TCH releases due to BSS failures, updated in phases2-3

001199

TCH releases due to BSS failures, updated in phases9-11

001200

Dropped calls after TCH assignment 001202

Number of TCH drops between Assignment Completeand RF Channel Release messages

001204

Number of TCH releases due to radio failures,updated only in phases 2-3

001205

Number of TCH releases due to radio failures,updated only in phases 12-14

001206

Number of TCH releases due to BSS failures,updated only in phases 12-14

001207

Number of TCH requests rejected due to themismatch between the types of the requestedchannel and the A interface circuit, updated only incall setup phase

001208

Number of TCH releases due to BSC-BSC conflict incall setup

001211

Number of TCH releases due to BSC-BSC conflict for target channel

001212

Number of TCH requests rejected due to lack of resources per BCSU

001216

Drops after DTM CS TCH assignment 001233

DTM CS TCH drops between ASSCOMPL and RFCHREL ACK

001234

. Other counters

Table 8. Other counters

Counter Counter number Average queue length for channel seizure request 001018

Queue denominator 1 001019

Average queue time of call attempts 001020






Table 8. Other counters (cont.)

Counter Counter number Average queue time of HO attempts 001022


Not relevant 001032

Not relevant 001073

Not relevant 001082

Successful MOC test call 001093

Unsuccessful MOC test call 001094

Average queuing time of urgent HO attempts 001143

Queue denominator 4 001144 Average queuing time of non-urgent HO attempts 001145


Successful AMR codec set downgrades 001185

Unsuccessful AMR codec set downgrades 001186

Successful AMR codec set upgrades 001187

Unsuccessful AMR codec set upgrades 001188

Internal to external HO 001217

Not changed internal HO 001218

. GPRS counters

Table 9. GPRS counters

Counter Counter number GPRS territory upgrade requests 001174

Incompletely served GPRS territory upgrade requests 001175

GPRS upgrade requests rejected due to CSW traffic 001176

GPRS upgrade requests rejected due to lack of PSW 001177

GPRS upgrade requests rejected due to to lack of PCU

001178

GPRS downgrades due to increase in CSW traffic 001179

GPRS upgrades due to decrease in CSW traffic 001180

GPRS territory downgrade requests 001181






Table 9. GPRS counters (cont.)

Counter Counter number GPRS territory downgrade rejected due to streamingtraffic

001209

GPRS territory downgrade rejected due to need of CS resources.

001210

Number of GPRS territory upgrade requestes fromCSW

001213

Number of GPRS territory upgrade requests fromCSW, partially successful

001214

Number of GPRS territory upgrade requests fromCSW, failed

011215

. Spare counters

Table 10. Spare counters

Counter Counter number Spare001191 001191

Spare001219 001219

Spare001220 001220

Spare001221 001221

Spare001222 001222

Spare001223 001223

Spare001224 001224

Spare001225 001225

Spare001227 001227

Spare001228 001228

Spare001229 001229

Spare001230 001230

Related topics

. Counters of Traffic Measurement

. Signalling charts of Traffic Measurement

. Signalling charts of Dual Transfer Mode



http://-/?-

http://-/?-



Instructions

. BSC Statistics Administration

For information on using this measurement to test the activation of relatedsoftware, see the testing instructions in:

. Activating and Testing BSS6071: EFR

. Activating and Testing BSS6115: Half Rate

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

. Activating and Testing BSS7036: Dynamic SDCCH

.

Activating and Testing BSS9006: GPRS . Activating and Testing BSS10004: AMR

Reference

. BSC Measurement Counters Displaying Program (FOXMEA)

. Performance Measurements

Descriptions

. Advanced Multilayer Handling

. Direct Access to Desired Layer/Band

. Directed Retry in BSC

. Dual Transfer Mode in BSC

. Dynamic Abis

. Dynamic Frequency and Channel Allocation in BSC

. Dynamic SDCCH in Radio Channel Allocation

. (E)GPRS in BSC

. Enhanced Coverage by Frequency Hopping

. Enhanced Speech Codecs: AMR and EFR

. Extended Cell Range

. FACCH Call Set-up

. Half Rate in BSC




http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-



. Handover Support for Coverage Enhancements

. HSCSD and 14.4 kbit/s Data Services in BSC

.

Intelligent Underlay-Overlay. Multi BCF Control in BSC

. Radio Resource Pre-emption and Queuing in BSC

. Traffic Reason Handover in BSC

. Trunk Reservation



http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-



2 Counters of Traffic Measurement

Number

Name

Release

001000

SEIZURE ATTEMPTS

S1

Trigger points See figures:. Basic call with counters. FACCH call setup due to SDCCH congestion with counters. FACCH call setup due to SDCCH congestion, no free TCH channel . SDCCH congestion, FACCH call setup is not activated . Successful SDCCH internal intra-cell handover . Successful SDCCH internal inter-cell handover . Successful SDCCH external handover target . Reconfiguration from TCH to SDCCH

Description Number of times when an MS attempts to seize an SDCCH.

Updated When the RRM receives requests for SDCCH from an MS as the MSneeds a channel for either a call or a HO.

Number

Name

Release

001001

SEIZURE ATTEMPTS WITH BUSY SDCCH

S1

Trigger points See figures:. FACCH call setup due to SDCCH congestion with counters. FACCH call setup because of SDCCH congestion. SDCCH congestion, FACCH call setup is not activated

Description Number of times when an MS attempts to seize an SDCCH but theattempt is unsuccessful because all SDCCHs are busy. This counter does not necessarily mean that the call attempt is lost, because thecall may be established as an FACCH call setup using TCH insteadof SDCCH. This counter is not triggered when the TCHreconfiguration is attempted because of dynamic SDCCH allocation.If the attempt fails, the SDCCH_busy_attempt is triggered together with 1155 UNSUCC_IMM_ASS_SDCCH_ATTEMPT.

Updated When the RRM has no SDCCHs to allocate for a call or HOattempts.



Counters of Traffic Measurement



Number

Name

Release

001002

TRANSACTIONS FAIL DUE TO BSS FAIL

S1

Trigger points See figures:. Unsuccessful SDCCH activation, timer expires while waiting for

CHANNEL_ACTIVATION_ACK message. SDCCH assignment failure. Unsuccessful SDCCH activation, timer expires while waiting for

PHYSICAL_CONTEXT_CONFIRM message. TRX/TSL is blocked with different causes during an SDCCH

channel activation. Unsuccessful SDCCH internal intra-cell handover, timer expires

while waiting for CHANNEL_ACTIVATION_ACK message. Unsuccessful SDCCH external handover, timer expires while

waiting for CLEAR_COMMAND messageDescription Number of SDCCH transactions ended because of a BSS failure.

Updated When one of the counters 001033, 001034, 001035, or 001036 isupdated. This counter represents their sum.

Impact See field descriptions of the counters 001033, 001034, 001035, and001036.

Number

Name

Release

001003

TRANSACTIONS FAIL DUE TO RADIO FAIL

S1Trigger points See figures:

. TCH assignment failure

. Connection failure during SDCCH assignment

Description Number of SDCCH transactions ended because of a radio failure.

Updated When an SDCCH transaction ends because of a radio failure (radiolink timeout) and the RRM releases the SDCCH.

This counter is updated in call phases 1-8 only.

Impact Call cleared

Reason for the impact External / Abis Interface





Number

Name

Release

001004

TRANSACTIONS FAIL DUE RADIO ON SOURCECHANNEL DURING HO

S1

Trigger points See figure Unsuccessful SDCCH internal inter-cell handover, BTS sends CONNECTION_FAILURE message

Description Number of SDCCH transactions ended because of a radio failure onthe source channel during a handover between SDCCH-SDCCH or SDCCH-TCH.


Updated When an SDCCH transaction ends because of a radio failure (HOfailure) on the source channel during a handover attempt and theRRM releases the SDCCH.

Dependencies with other counters/ PI(s) It is this counter in the source cell that is updated. If the target celllies within the same BSC, also counter 001005 in the target cell isupdated along with this counter.

Impact HO failure and call cleared

Number

Name

Release

001005

TRANSACTIONS FAIL DUE RADIO ON TARGET CHANNELDURING HO

S1

Trigger points See figure Unsuccessful SDCCH internal intra-cell handover,CONNECTION_FAILURE message comes to the target channel during handover

Description Number of SDCCH transactions ended because of a radio failure onthe target channel during an SDCCH HO.

Updated When an SDCCH transaction ends because of a radio failure on thetarget channel during a handover attempt and the RRM releases theSDCCH.


Impact HO failure, the call may possibly be cleared

Reason for the impact Since the MS cannot access the target channel, a radio failureoccurs. The unsuccessful seizure may have been caused by amissing indication of call establishment, missing detection of HO,missing indication of the HO completed, or corrupted messagesrelated to the HO.






Number

Name

Release

001006

SUCCESS SEIZURE FOR HO

S1

Trigger points See figures:. Successful SDCCH internal intra-cell handover . Successful SDCCH internal inter-cell handover . Successful SDCCH external handover target

Description Number of successful SDCCH seizures for a handover.

Updated When the RRM allocates an SDCCH as a response to an SDCCHrequest in a handover attempt.

Number

Name

Release

001007

SUCCESS SEIZURE FOR IMMEDIATE ASSIGNMENT

S1

Trigger points See figures:. Basic call with counters. Reconfiguration from TCH to SDCCH

Description Number of successful seizures of SDCCH for an immediateassignment.

Updated When the RRM allocates an SDCCH for an immediate assignment ina call attempt.

Number

Name

Release

001008

SUCCESS TCH SEIZURE FOR HO

S1

Trigger points See figures:. Successful internal intra-cell handover . Internal intra-cell HO, successful TCH queuing . Successful internal inter-cell handover . Successful external handover, target

Description Number of successful requests for a TCH in a handover.

Updated When the RRM allocates a TCH as a response to a TCH request ina handover attempt. The channel is reserved by the RRM, but thesuccess of the HO is not known in this phase.





Number

Name

Release

001009

SUCCESS TCH SEIZURE FOR NORMAL ASSIGNMENT

S1

Trigger points See figures:. Basic call with counters. Basic call with priority subscriber . Successful TCH queuing . Successful forced release. Successful forced handover

Description Number of successful requests for a TCH in a normal assignment.

Updated When the RRM allocates a TCH as a response to a TCH request ina call attempt.

Number

Name

Release

001010

TCH REQUEST SUCCESS AND UNSUCCESS

S1

Trigger points See figures:. Basic call with counters. Basic call with priority subscriber . FACCH call setup due to SDCCH congestion with counters. FACCH call setup because of SDCCH congestion. Basic call, no free TCH and queuing or directed retry is not allowed . Successful TCH queuing . Basic call, no free TCHs, unsuccessful queuing and directed retry

not activated . TCH assignment failure with cause switch_circuit_pool, queuing

and directed retry not allowed . Unsuccessful trunk reservation. Successful internal intra-cell handover . Internal intra-cell HO, successful TCH queuing . Unsuccessful underlay overlay internal intra-cell handover, queuing

not allowed . Internal intra-cell handover, unsuccessful TCH queuing .

Internal directed retry . Successful internal inter-cell handover . Successful external handover, target . Successful forced release. Unsuccessful forced release. Unsuccessful forced release with external handover . Successful forced handover . Unsuccessful forced handover . Unsuccessful forced handover with external handover






Number

Name

Release

001010

TCH REQUEST SUCCESS AND UNSUCCESS

S1

Description Total number of requests for a TCH (successful and unsuccessful).

Updated When the RRM receives a request for a TCH either in a call or ahandover attempt.

Number

Name

Release

Definition updated

001011

TCH REQUEST REJECTED DUE TO LACK

S1

S11

Trigger points See figures:. Basic call without counters. Basic call, no free TCHs, unsuccessful queuing and directed retry


and directed retry not allowed . Unsuccessful underlay overlay internal intra-cell handover, queuing

not allowed . Internal intra-cell handover, unsuccessful TCH queuing . Unsuccessful forced release. Unsuccessful forced release with external handover . Unsuccessful forced handover

Description Number of requests for TCHs that are rejected because there are noradio resources available. This counter is also updated when arequest for TCH is rejected because of a mismatch between thetypes of the requested channel and the A interface circuit.

Updated When the RRM has no TCHs available for either call or HO attemptrequests, or the RRM changes the A interface circuit pool before theTCH allocation. This counter may be updated immediately after aTCH request or, in case of queuing, when the queuing timer expires.

NOTE! In case of DR this counter is updated as follows:

1) When a call is removed from the queue because of a DR attempt,this counter is NOT updated on the SOURCE side, instead counter

001173 is updated.

2) If queuing is not used or the queuing timer expires before a DRattempt, this counter is updated on the SOURCE side.

3) On the TARGET side, this counter is updated in case of congestion (blocking ).

Dependencies with other counters/ PI(s)

See also counter 004079.





Number

Name

Release

001012

TRANSACTIONS ENDED DUE TO BSS PROBLEM

S1

Trigger points See figures:. Unsuccessful TCH activation, timer expires while waiting for

CHANNEL_ACTIVATION_ACK message. TCH assignment failure, MSC sends CLEAR_COMMAND

message. TRX or TSL is blocked with different causes during a call . Unsuccessful internal intra-cell handover, timer expires while

waiting for CHANNEL_ACTIVATION_ACK message. Unsuccessful external handover, source BSC, timer expires while

waiting for CLEAR_COMMAND message. Unsuccessful external handover, MS sends a handover failure. Dropped call between ASSIGNMENT COMPLETE and

DISCONNECT

Description Number of TCH transactions ended because of BSS problems.

Updated When one of the counters 001045, 001046, 001047, or 001051 isupdated. This counter represents their sum.

Impact See field descriptions of counters 001045, 001046, 001047 and001051.

Number

Name

Release

Definition updated

001013

TRANSACTIONS ENDED DUE RADIO FAIL

S1

S11

Trigger points See figures:. Timer T3107 expires while waiting for ASSIGNMENT_COMPLETE

message. Dropped call between ASSIGNMENT COMPLETE and

DISCONNECT

Description Number of TCH transactions ended because of a radio failure.

Updated When a TCH transaction ends because of a radio failure and theRRM releases the TCH. This counter is typical in connection withcoverage problems.

ERROR INDICATION is sent by the BTS to the BSC in the followingcases:. Sequence error in a received message (the case where

retransmission is not possible).. Timer T200 has expired N200 +1 times (MS doesn't respond any

more).. Unsolicited DM response when link is established.

This counter is updated in call phases 1-8 or 15 only.






Number

Name

Release

Definition updated

001013

TRANSACTIONS ENDED DUE RADIO FAIL

S1

S11

Impact Call cleared

Number

Name

Release

001014

TRANSACTIONS ENDED DUE SOURCE CHANNEL FAILDURING HO

S1

Trigger points See figure Unsuccessful internal intra-cell handover, timer expires onthe source channel, call cleared

Description Number of TCH transactions ended because of a radio failure on thesource channel during a handover attempt.


Updated When a TCH transaction ends because of a radio failure (HO failure)on the source channel during a handover attempt.


Number

Name

Release

001015

TRANSACTIONS ENDED DUE TARGET CHANNEL FAILDURING HO

S1

Description A TCH transaction ends because of a radio failure (HO failure) on thetarget channel during a handover attempt.

Updated When a TCH transaction ends because of a radio failure on thetarget channel during a handover attempt.



Reason for the impact Since the MS cannot access the target channel, a radio failureoccurs. It may be caused by missing indication of call establishment,missing detection of HO, missing indication of the HO completed or corrupted messages related to HO.


Counter 1088 is also updated along with this counter if the MS failsto return to the old channel during an inter-BSC handover.





Number

Name

Release

001016

CALL ATTEMPTS IN THE QUEUE

S1

Trigger points See figures:. Successful TCH queuing . Basic call, no free TCHs, unsuccessful queuing and directed retry

not activated

Description Number of call attempts set in the queue for a TCH.

Updated When the RRM puts a TCH request for call attempt in the queuesince it has no TCHs of the requested kind available.


Counter 001010 is updated along with this counter.

Number

Name

Release

001017

HANDOVER ATTEMPTS IN THE QUEUE

S1

Trigger points See figures:. Internal intra-cell HO, successful TCH queuing . Internal intra-cell handover, unsuccessful TCH queuing . Internal directed retry

Description Number of HO attempts set in the queue for a TCH.

Updated When the RRM sets a TCH request for a handover attempt in thequeue since it has no TCHs of the requested kind available.



Number

Name

Release

001018

AVE QUEUE LENGTH FOR CHANNEL SEIZURE REQUEST

S1

Trigger points See figure Average counter updating

Description Average number of requests for channel seizure in the queue.

Updated Every 20 seconds, as averaging takes place once in themeasurement period. The sample counter is updated when a requestis set in the queue or removed from it. Updated only to normal TRXrecord, not to extended TRX record.

Logical type Average






Number

Name

Release

001019

QUEUE DENOMINATOR 1

S1

Description Denominator of the average number of requests for channel seizure(always > 0).

Number

Name

Release

001020

AVE QUEUE TIME OF CALL ATTEMPTS

S1


not activated

Description The average t ime for which call attempts are kept in the queue (theunit of the value is 10 ms).

Updated The sample counter is updated when a TCH request for a callattempt is removed from the queue (both in a successful andunsuccessful case).


In a successful case counters 001009 and 001021 are updated alongwith this counter. In an unsuccessful case counters 001021, 001024and 001060 are updated along with this counter.


Unit 10 ms

Number

Name

Release

001021

QUEUE DENOMINATOR 2

S1


not activated

Description Denominator of the average t ime for which call attempts are kept inthe queue (always > 0).





Number

Name

Release

001022

AVE QUEUE TIME OF HO ATTEMPTS

S1


Description The average time for which HO attempts are kept in the queue. (theunit of the value is 10 ms)

Updated The sample counter is updated when a TCH request for a handover attempt is removed from the queue (both in a successful andunsuccessful case).

Dependencies with other counters/

PI(s)

In a successful case counters 001008 and 001023 are updated along

with this counter. In an unsuccessful case counters 001023, 001025and 001068 are updated along with this counter.


Unit 10 ms

Number

Name

Release

001023

QUEUE DENOMINATOR 3

S1


Description Denominator of the average time for which HO attempts are kept inthe queue (always > 0).

Number

Name

Release

001024

NOT SERVED QUEUED CALL ATTEMPTS

S1

Trigger points See figure Basic call, no free TCHs, unsuccessful queuing and directed retry not activated

Description Number of call attempts in the queue which were not served.

Updated When a call attempt is removed from the queue because a timer expires, or the call attempt is substituted by another attempt of higher priority.

NOTE! This counter is not updated in DR (neither in a successful or unsuccessful DR).






Number

Name

Release

001024

NOT SERVED QUEUED CALL ATTEMPTS

S1


Counters 001020, 001021 and 001060 are updated along with thiscounter.

Number

Name

Release

001025

NOT SERVED QUEUED HO ATTEMPTS

S1

Trigger points See figure Internal intra-cell handover, unsuccessful TCH queuing

Description Number of HO attempts in the queue which were not served.

Updated When a handover attempt is removed from the queue because atimer expires, or the HO attempt is substituted by another attempt of higher priority.



Number

Name

Release

001026

TCH CALL REQ

S2

Trigger points See figures:. Basic call with counters. Basic call with priority subscriber . Successful TCH queuing . Basic call, no free TCHs, unsuccessful queuing and directed retry


and directed retry not allowed . Unsuccessful trunk reservation. Internal directed retry . Successful forced release. Unsuccessful forced release. Successful forced handover . Unsuccessful forced handover

Description Number of TCH requests for a normal assignment (both successfuland unsuccessful).

Updated When the RRM receives a TCH request in a call attempt.







Number

Name

Release

001027

SDCCH ACT FAIL

S2

Trigger points See figures:. Unsuccessful SDCCH activation. Unsuccessful SDCCH internal intra-cell handover, unsuccessful

channel activation

Description Number of SDCCH transactions that are ended because of a failurein the activation of a channel either during a call or HO attempt.

Updated When either of the counters 001072 and 001074 is updated. Thiscounter represents their sum.

Impact - Call cleared

- HO failure

Reason for the impact External / Abis interface

Number

Name

Release

001028

TCH ACT FAIL

S2

Trigger points See figures:. Unsuccessful TCH activation. Unsuccessful internal inter-cell handover

Description Number of TCH transactions that are ended because of a failure inthe activation of a channel either during a call or HO attempt.

Updated When either of the counters 001081 and 001083 is updated. Thiscounter represents their sum.


- HO failure

Reason for the impact Abis Interface

Number

NameRelease

001029

TCH TR FAILS2

Trigger points See figure CONNECTION_FAILURE message with causetranscoder_failure during a call

Description Number of TCH transactions that are ended because of a transcoder failure.






Number

Name

Release

001029

TCH TR FAIL

S2

Updated When a TCH transaction ends because of a transcoder failure duringa call attempt and the RRM releases the TCH. These failures canalso contain situations when the timer T3109 expires in a BSC in callrelease phase while waiting for the Release Indication. The MSsubscriber does not see these failures caused by the T3109 expiryas real drop calls.


Impact Call cleared

Number

Name

Release

001030

TCH TR FAIL SOURCE

S2

Description Number of TCH transactions that are ended because of a transcoder failure on the source channel during a handover on a TCH.

Updated When a TCH transaction ends because of a transcoder failure on thesource channel during a handover attempt and the RRM releases theTCH. This happens before the RRM receives a message from theMS stating that the HO or assignment is completed.



Number

Name

Release

001031

TCH TR FAIL TARGET

S2

Trigger points See figure Unsuccessful internal intra-cell handover,CONNECTION_FAILURE message with causeremote_transcoder_failure comes to the target channel

Description Number of TCH transactions that are ended because of a transcoder failure on the target channel during a handover on a TCH.

Updated When a TCH transaction ends because of a transcoder failure on thetarget channel during a handover attempt and the RRM releases theTCH. This happens before the RRM receives a message from theMS stating that the HO or assignment is completed.







Number

Name

Release

001032

NOT RELEVANT

S2

Description Not in use

Number

Name

Release

001033

SDCCH ABIS PROBL

S2


CHANNEL_ACTIVATION_ACK message. Unsuccessful SDCCH activation, timer expires while waiting for


channel activation. Unsuccessful SDCCH internal intra-cell handover, timer expires

while waiting for CHANNEL_ACTIVATION_ACK message

Description Number of SDCCH transactions that are ended because of a failurein the Abis interface.

Updated When any of the counters 001075, 001076 and 001077 is updated.This counter represents their sum.


- HO failure


Number

Name

Release

001034

SDCCH A IF PROBL

S2

Trigger points See figures:. SDCCH assignment failure. Unsuccessful SDCCH external handover, timer expires while

waiting for CLEAR_COMMAND message

Description Number of SDCCH transactions that are ended because of a failurein the A interface.

Updated When any of the counters 001078, 001079, and 001080 is updated.This counter represents their sum.


- HO failure

Reason for the impact External / A interface








Number

Name

Release

001038

SDCCH BCSU RESET

S2

Description Number of SDCCH transactions that are ended because of a BCSUrestart.

Updated When an SDCCH transaction ends because of a TRX blocked by aBCSU restart and the RRM releases the SDCCH.


- HO failure

Reason for the impact BCSU restart

Number

Name

Release

001039

SDCCH NETW ACT

S2

Trigger points See figure TRX/TSL is blocked with different causes during anSDCCH channel activation

Description Number of SDCCH transactions ended because of a reconfigurationof the radio network. (The TRX blocked is in substate blocked by thesystem.)

Updated When an SDCCH transaction ends because of a TRX blocked by afailure which leads to TRX reconfiguration. The failure may occur both during call and HO attempts.


- HO failure

Reason for the impact See Radio Network Management, Service Block Description, for radio network reconfiguration.

Number

Name

Release

001040

TRUNK RES INVOC

S2

Trigger points See figures:. Successful trunk reservation. Unsuccessful trunk reservation

Description Total number of Trunk Reservation function invocations.

Updated When Trunk Reservation is applied during call setup or handover inRadio Resource Management.

Feature Trunk Reservation






Number

Name

Release

001041

SUCC TRUNK RES INVOC

S2

Trigger points See figure Successful trunk reservation

Description Number of successful Trunk Reservation function invocations.

Updated When Trunk Reservation allows resources to be allocated in callsetup or handover in Radio Resource Management.


Number

Name

Release

001042

TRUNK RES INVOC RES REFUSED

S2Trigger points See figure Unsuccessful trunk reservation .

Description Number of Trunk Reservation function invocations that result inresource allocation being refused.

Updated When Trunk Reservation denies access and does not allowresources to be allocated in call setup or handover in RadioResource Management.


Number

Name

Release

Definition updated

001043

TCH REQ FACCH CALL SET

S2

S5

Trigger points See figures:. FACCH call setup due to SDCCH congestion with counters. FACCH call setup because of SDCCH congestion

Description Number of TCH requests for FACCH call setup during SDCCHcongestion (both successful and unsuccessful).

Updated When the RRM receives a request for an SDCCH but there are no

SDCCHs idle and a TCH is tried to be allocated as part of theFACCH call setup. It is indicated in the received SDCCH requestwhether a FACCH setup is allowed or not.


Counters 001010 and 001098 are updated along with this counter.

Feature BSS5290: FACCH Call Setup because of SDCCH Congestion





Number

Name

Release

Definition updated

001044

TCH SEIZ FACCH CALL SET

S2

S5

Trigger points See figure FACCH call setup due to SDCCH congestion withcounters

Description Number of successful seizures of TCHs in FACCH call setup.

Updated When the RRM allocates a TCH as a response to an SDCCHrequest as part of the FACCH call setup because of no SDCCHsbeing idle.




Number

Name

Release

001045

TCH ABIS PROBL

S2


CHANNEL_ACTIVATION_ACK message. TRX or TSL is blocked with different causes during a call . Unsuccessful internal intra-cell handover, timer expires while

waiting for CHANNEL_ACTIVATION_ACK message. Dropped call between ASSIGNMENT COMPLETE and

DISCONNECT

Description Number of TCH transactions that are ended because of a failure inthe Abis interface.

Updated When any of the counters 001084, 001085, and 001086 is updated.This counter represents their sum.

Impact - The call may possibly be cleared

- HO failure


Number

Name

Release

001046

TCH LAPD FAIL

S2

Trigger points See figure TRX or TSL is blocked with different causes during a call

Description Number of TCH transactions that are ended because of an LAPDfailure. (The TRX blocked is in one of these substates: signalling linkfault or PCM fault.)






Number

Name

Release

001046

TCH LAPD FAIL

S2

Updated When a TCH transaction ends because of a TRX blocked by anLAPD failure and the RRM releases the TCH.


- HO failure

Number

Name

Release

001047

TCH BTS FAIL

S2

Trigger points See figure TRX or TSL is blocked with different causes during a call Description Number of TCH transactions that are ended because of a BTS

failure. (The TRX blocked is in one of these substates: FU fault, CUfault, BTS reset, BCF reset, both CU and FU fault, BCF fault.)

Updated When a TCH transaction ends because of a TRX blocked by a BTSfailure and the RRM releases the TCH.

Impact Call cleared

Number

Name

Release

001048

TCH USER ACT

S2


Description Number of TCH transactions that are ended because of user actions.(The TRX/TSL is in substate blocked by the user.)

Updated When the user disconnects a busy TCH by blocking the TSL/TRXwith an MML command. The transaction ends and the TCH isreleased.


- HO failure

Number

Name

Release

001049

TCH BCSU RESET

S2

Description Number of TCH transactions that are ended because of a BCSUrestart.

Updated When a TCH transaction ends because of a TRX blocked by aBCSU restart and the RRM releases the TCH.





Number

Name

Release

001049

TCH BCSU RESET

S2


- HO failure

Reason for the impact BCSU restart

Number

Name

Release

001050

TCH NETW ACT

S2


Description Number of TCH transactions ended because of a reconfiguration of the radio network. (The TRX blocked is in substate blocked by thesystem.)

Updated When a TCH transaction ends because of a TRX blocked by afailure which leads to TRX reconfiguration.

Reason for the impact See Radio Network Management for radio network reconfiguration.

Number

Name

Release

001051

TCH A IF PROBL


. TCH assignment failure, MSC sends CLEAR_COMMANDmessage

. Unsuccessful external handover, source BSC, timer expires whilewaiting for CLEAR_COMMAND message

. Unsuccessful external handover, MS sends a handover failure

Description Number of TCH transactions that are ended because of a failure inthe A interface.

Updated When any of the counters 001087, 001088 and 001089 is updated.This counter represents their sum.

Impact - Call is possibly cleared

- HO failure







Number

Name

Release

001052

TRHO REQ

S2

Trigger points See figure Successful traffic reason handover, source

Description Number of HOs because of traffic reasons.

Updated When a handover, under the control of the MSC and because of atraffic reason procedure, is started as a response to theTRAFFIC_REASON_HO_CANDIDATE_ENQUIRY message from the A interface. The counter tells the number of mobiles, determined bythe MSC to be handed over. Updated only to normal TRX record, notto extended TRX record.

Feature Traffic Reason Handover

Number

Name

Release

001053

TRHO ENQUIRIES

S2

Trigger points See figure Successful traffic reason handover, source

Description Number of enquiries about traffic reason HO.

Updated When the RRM starts a handover by sending a message enquiringabout the traffic reason to the Abis interface.

Feature Traffic Reason Handover

Number

Name

Release

001054

FOR REL ASSIGN REQ ATT

S3

Trigger points See figures:. Basic call with priority subscriber . Successful forced release. Unsuccessful forced release

Description Number of call at tempt requests capable of doing a forced releasefor a call in progress.

Updated When the RRM receives a TCH request for a call attempt which iscapable of doing a forced release for a call in progress.



Feature Queuing and Priority





Number

Name

Release

001055

FOR HO ASSIGN REQ ATT

S3

Trigger points See figures:. Basic call with priority subscriber . Successful forced handover . Unsuccessful forced handover

Description Number of call attempt requests capable of doing a forced HO for acall in progress.

Updated When the RRM receives a TCH request for a call attempt which iscapable of doing a forced HO for a call in progress.




Number

Name

Release

001056

QUE ALL ASSIGN REQ ATT

S3

Trigger points See figures:. Basic call with counters. Successful TCH queuing . Basic call, no free TCHs, unsuccessful queuing and directed retry

not activated . Unsuccessful trunk reservation

Description Number of requests for a call attempt with queuing allowed.

Updated When the RRM receives a TCH request for a call attempt which isallowed to queue for channels.




Number Name

Release

001057QUE NALL ASSIGN REQ ATT

S3

Trigger points See figures:. Basic call with counters. Basic call, no free TCH and queuing or directed retry is not allowed . TCH assignment failure with cause switch_circuit_pool, queuing

and directed retry not allowed . Unsuccessful trunk reservation






Number

Name

Release

001057

QUE NALL ASSIGN REQ ATT

S3

Description Number of requests for a call attempt with queuing not allowed.

Updated When the RRM receives a TCH request for a call attempt which isnot allowed to queue for channels.




Number

Name

Release

001058

FOR REL ASSIGN REQ FAIL

S3

Trigger points See figure Unsuccessful forced release

Description Number of rejected call attempt requests capable of doing a forcedrelease for a call in progress.

Updated When the RRM rejects a TCH request for a call attempt which iscapable of doing a forced release for a call in progress. The highpriority TCH request is rejected because of lack of a suitable call for release or because pre-emption software is not in use in the BSC.




Reason for the impact There is no suitable call for release in the cell or the pre-emptionsoftware is not in use in the BSC.

Number

Name

Release

001059

FOR HO ASSIGN REQ FAIL

S3

Trigger points See figure Unsuccessful forced handover

Description Number of rejected call attempt requests capable of doing a forcedHO for a call in progress.

Updated When the RRM rejects a TCH request for a call attempt which iscapable of doing a forced handover for a call in progress. The highpriority TCH request is rejected because of a lack of suitable calls for a forced handover or because the pre-emption software is not in usein the BSC.








Number

Name

Release

001059

FOR HO ASSIGN REQ FAIL

S3

Reason for the impact There is no suitable call for a forced handover in the cell or the pre-emption software is not in use in the BSC.

Number

Name

Release

001060

QUE ALL ASSIGN REQ FAIL

S3

Trigger points See figures:. Basic call, no free TCHs, unsuccessful queuing and directed retry

not activated . Unsuccessful trunk reservation

Description Number of rejected call at tempt requests with queuing allowed.

Updated When the RRM rejects a TCH request for a call attempt which isallowed to queue.




Reason for the impact This may be because of queuing is not allowed in the BTS, or therequest is removed from the queue because of expiry of a timer, or the request is replaced by a request with higher priority.

Number

Name

Release

001061

QUE NALL ASSIGN REQ FAIL

S3

Trigger points See figures:. Basic call, no free TCH and queuing or directed retry is not allowed . TCH assignment failure with cause switch_circuit_pool, queuing

and directed retry not allowed . Unsuccessful trunk reservation

Description Number of rejected call at tempt requests with queuing not allowed.Updated When the RRM rejects a TCH request for a call attempt which is not

allowed to queue.




Reason for the impact There are no radio resources available.






Number

Name

Release

001062

FOR REL HO REQ ATT

S3

Trigger points See figure Unsuccessful forced release with external handover

Description Number of requests for a handover capable of doing a forced releasefor a call in progress.

Updated When the RRM receives a TCH request for a handover attemptwhich is capable of doing a forced release for a call in progress.




Number

Name

Release

001063

FOR HO HO REQ ATT

S3

Trigger points See figure Unsuccessful forced handover with external handover

Description Number of requests for a handover capable of doing a forced HO for a call in progress.

Updated When the RRM receives a TCH request for a handover attemptwhich is capable of doing a forced HO for a call in progress.




Number

Name

Release

001064

QUE ALL HO REQ ATT

S3

Trigger points See figures:. Successful internal intra-cell handover . Internal intra-cell HO, successful TCH queuing .

Internal intra-cell handover, unsuccessful TCH queuing . Internal directed retry . Successful internal inter-cell handover . Successful external handover, target

Description Number of requests for a handover with queuing allowed.

Updated When the RRM receives a TCH request for a handover attemptwhich is allowed to queue for radio resources.







Number

Name

Release

001064

QUE ALL HO REQ ATT

S3


Number

Name

Release

001065

QUE NALL HO REQ ATT

S3

Trigger points See figures:. Successful internal intra-cell handover . Unsuccessful underlay overlay internal intra-cell handover, queuing

not allowed . Successful internal inter-cell handover . Successful external handover, target

Description Number of requests for HO with queuing not allowed.

Updated When the RRM receives a TCH request for a handover attemptwhich is not allowed to queue for radio resources.




Number

Name

Release

001066

FOR REL HO REQ FAIL

S3

Trigger points See figure Unsuccessful forced release with external handover

Description Number of rejected requests for a handover capable of doing aforced release for a call in progress.

Updated When the RRM rejects a TCH request for a handover attempt whichis capable of doing a forced release for a call in progress. The highpriority TCH request is rejected because of a lack of suitable calls for release or because the pre-emption software is not in use in the

BSC.Dependencies with other counters/ PI(s)



Reason for the impact There is no suitable call for release in the cell or the pre-emptionsoftware is not in use in BSC.






Number

Name

Release

001067

FOR HO HO REQ FAIL

S3

Trigger points See figure Unsuccessful forced handover with external handover

Description Number of rejected requests for a handover capable of doing aforced HO for a call in progress.

Updated When the RRM rejects a TCH request for a handover attempt whichis capable of doing a forced handover for a call in progress. The highpriority TCH request is rejected because of a lack of suitable calls for a forced handover or because the pre-emption software is not in usein the BSC.




Reason for the impact There is no suitable call for a forced handover in the cell or the pre-emption software is not in use in the BSC.

Number

Name

Release

001068

QUE ALL HO REQ FAIL

S3


Description Number of the rejected requests for a handover with queuing

allowed.Updated When the RRM rejects a TCH request for a handover attempt which

is allowed to queue.




Reason for the impact This may be because queuing is not allowed in the BTS, or therequest is removed from the queue because of expiry of a timer, or the request is replaced by another with higher priority.

Number

Name

Release

001069

QUE NALL HO REQ FAIL

S3

Trigger points See figure Unsuccessful underlay overlay internal intra-cell handover,queuing not allowed

Description Number of rejected requests for a handover with queuing notallowed.





Number

Name

Release

001069

QUE NALL HO REQ FAIL

S3

Updated When the RRM rejects a TCH request for a handover attempt whichis not allowed to queue.




Reason for the impact There are no radio resources available.

Number

Name

Release

001070

FORCED RELEASES

S3

Trigger points See figure Successful forced release

Description Number of forced releases.

Updated When the RRM starts to terminate a call in progress forcefully bysending a release request to the Abis interface.


Number

NameRelease

001071

FORCED HANDOVERSS3

Trigger points See figure Successful forced handover

Description Number of forced HOs.

Updated When the RRM receives an acknowledgement from the Handover Attempt Supervisor of the Abis interface to its request for a forcedHO.


Number Name

Release

001072SDCCH ACT FAIL CALL

S3

Trigger points See figure Unsuccessful SDCCH activation

Description Number of SDCCH transactions that are ended because of a failurein the activation of a channel during a call.








Number

Name

Release

001075

SDCCH ABIS FAIL CALL

S3


CHANNEL_ACTIVATION_ACK message. Unsuccessful SDCCH activation, timer expires while waiting for


channel activation

Description Number of SDCCH transactions that are ended because of a failurein the Abis interface during a call in progress. There is noacknowledgement of channel activation, no indication of callestablishment received, i.e., ghosts.

Updated When an SDCCH transaction ends because of signalling problems inthe Abis interface and the RRM releases the SDCCH.


Reasons that trigger the counter:

Phantom RACHs that have a valid establihment cause.

The BTS can hear the MS, but the MS cannot hear the BTS, and sothe MS does not respond to the IMMEDIATE ASSIGNMENTmessage with a SABM.

MS is accessing the network at the limit of sensitivity and messagesare lost.

Poor Radio conditions.MS is accessing network through another BTS (co-channel, co-BSICinterference).

Impact Call cleared


Number

Name

Release

001076

SDCCH ABIS FAIL SOURCE

S3

Description Number of SDCCH transactions that are ended because of a failurein the Abis interface on the source channel during SDCCH-SDCCHor SDCCH-TCH HO.

Updated When an SDCCH transaction ends because of a failure in the Abisinterface on the source channel during a handover and the RRMreleases the SDCCH.


Feature SDCCH Handover, Directed retry







Number

Name

Release

001076

SDCCH ABIS FAIL SOURCE

S3

Reason for the impact External / Abis interface.

Number

Name

Release

001077

SDCCH ABIS FAIL TARGET

S3

Trigger points See figure Unsuccessful SDCCH internal intra-cell handover, timer expires while waiting for CHANNEL_ACTIVATION_ACK message

Description Number of SDCCH transactions that are ended because of a failurein the Abis interface on the target channel during a handover.

Updated When an SDCCH transaction ends because of a failure in the Abisinterface on the target channel during a handover and the RRMreleases the SDCCH.


Feature SDCCH Handover

Impact HO failure and possibly call cleared


Number

Name

Release

001078

SDCCH A IF FAIL CALL

S3

Trigger points See figure SDCCH assignment failure

Description Number of SDCCH transactions ended because of a failure in the Ainterface during a call attempt.

Updated When an SDCCH transaction ends because of signalling problems inthe A interface during a call attempt and the RRM releases theSDCCH.


Impact Call clearedReason for the impact External / A interface.

There may be a failure in the SDCCH signalling connection.





Number

Name

Release

001079

SDCCH A IF FAIL SOURCE

S3

Trigger points See figure Unsuccessful SDCCH external handover, timer expireswhile waiting for CLEAR_COMMAND message

Description Number of SDCCH transactions ended because of a failure in the Ainterface on the source channel during an SDCCH-SDCCH or SDCCH-TCH HO.

Updated When an SDCCH transaction ends because of signalling problems inthe A interface during an SDCCH-SDCCH or SDCCH-TCH HO andthe RRM releases the SDCCH.


Feature SDCCH Handover, Directed retry


Reason for the impact External / A interface.


Number

Name

Release

001080

SDCCH A IF FAIL TARGET

S3

Trigger points See figure Unsuccessful SDCCH external handover, timer expireswhile waiting for CLEAR_COMMAND message

Description Number of SDCCH transactions ended because of a failure in the Ainterface on the target channel during an SDCCH HO.

Updated When an SDCCH transaction ends because of signalling problems inthe A interface during an SDCCH HO and the RRM releases theSDCCH.


Feature SDCCH Handover


Reason for the impact External / A interface.









Number

Name

Release

001084

TCH ABIS FAIL CALL

S3

Description Number of TCH transactions ended because of a failure in the Abisinterface during a call in progress.

Updated When a TCH transaction ends because of signalling problems in the Abis interface and the RRM releases the TCH.


Impact Call cleared


The signalling problems may include missing acknowledgement of channel activation, missing indication of call establishment, receipt of an error indication, corrupted messages, missing measurement

results from the BTS, excessive timing advance or some internalreasons. These failures can also contain situations when the timer T3109 expires in a BSC in call release phase while waiting for theRelease Indication. The MS subscriber does not see these failurescaused by the T3109 expiry as real drop calls.

Number

Name

Release

001085

TCH ABIS FAIL SOURCE

S3

Description Number of TCH transactions ended because of a failure in the Abis

interface on the source channel during a TCH HO.Updated When a TCH transaction ends because of a failure in the Abis

interface on the source channel during a TCH HO and the RRMreleases the TCH.




Number

NameRelease

001086

TCH ABIS FAIL NEW S3

Trigger points See figure Unsuccessful internal intra-cell handover, timer expireswhile waiting for CHANNEL_ACTIVATION_ACK message

Description Number of TCH transactions ended because of a failure in the Abisinterface on the new channel during a TCH handover.






Number

Name

Release

001086

TCH ABIS FAIL NEW

S3

Updated When a TCH transaction ends because of a failure in the Abisinterface on the new channel during a TCH handover and the RRMreleases the TCH.


Impact HO failure and possibly call cleared


Number

Name

Release

001087

TCH A IF FAIL CALL

S3

Trigger points See figure TCH assignment failure, MSC sends CLEAR_COMMANDmessage

Description Number of TCH transactions ended because of a failure in the Ainterface during a call in progress.

Updated When a TCH transaction ends because of signalling problems in the A interface during a call and the RRM releases the TCH.


Impact Call cleared

Reason for the impact External / A interface.The signalling problems may include the CLEAR_COMMANDmessage from the MSC during the call setup phase before the MSCreceives an indication of the completion of the assignment from theMS and the ABNORMAL_CLEAR_ RECEIVED_DUE_TO_A_ INTERFACE message (reset circuit, SCCP cleared by RLSD).

Number

Name

Release

001088

TCH A IF FAIL SOURCE

S3

Trigger points See figure Unsuccessful external handover, source BSC, timer expires while waiting for CLEAR_COMMAND message

Description Number of TCH transactions ended because of a failure in the Ainterface on the source channel during a handover attempt.

Updated When a TCH transaction ends because of an A interface failure (HOfailure) on the source channel during a TCH HO attempt and theRRM releases the TCH.






Number

Name

Release

001088

TCH A IF FAIL SOURCE

S3


This counter is updated in the source cell. If the target cell lies withinthe same BSC, also counter 001015 in the target cell is updatedalong with this counter.

This counter is also updated if the MS fails to return to the oldchannel during an inter-BSC handover.



Number

NameRelease

001089

TCH A IF FAIL NEW S3

Trigger points See figure Unsuccessful external handover, MS sends a handover failure

Description Number of TCH transactions ended because of a failure in the Ainterface on the new channel during a handover attempt.

Updated When a TCH transaction ends because of a failure in the A interface(HO failure) on the new channel during a handover attempt and theRRM releases the TCH.




Number

Name

Release

001090

TCH REQ UND OVER

S4

Trigger points See figures:. Successful internal intra-cell handover . Internal intra-cell HO, successful TCH queuing . Unsuccessful underlay overlay internal intra-cell handover, queuing

not allowed . Internal directed retry . Successful internal inter-cell handover

Description Number of TCH requests for an underlay overlay HO. Updated onlyto normal TRX record, not to extended TRX record.

Updated When the RRM receives a TCH request for an underlay overlay HO.






Number

Name

Release

001090

TCH REQ UND OVER

S4



Feature BSC4016: Intelligent Underlay Overlay

Number

Name

Release

001091

TCH SEIZ UND OVER

S4

Trigger points See figures:. Successful internal intra-cell handover . Internal intra-cell HO, successful TCH queuing . Successful internal inter-cell handover

Description Number of TCH seizures for an underlay overlay HO.

Updated When the RRM allocates a TCH as a response to a TCH request for an underlay overlay HO. Updated only to normal TRX record, not toextended TRX record.




Number

Name

Release

001092

TCH REJ REQ UND OVE

S4

Trigger points See figure Unsuccessful underlay overlay internal intra-cell handover,queuing not allowed

Description Number of TCH requests for an underlay overlay HO rejectedbecause of a lack of resources.

Updated When the RRM rejects a TCH request for an underlay overlay HObecause of lack of resources. Updated only to normal TRX record,

not to extended TRX record.








Number

Name

Release

001093

SUCC MOC TEST CALL

S4

Description Number of successful MOC test calls during a scheduled test.

Updated When the RRM receives a message from the BTTEST.

Feature BSC4531: BTS Testing:Scheduled MOC

Number

Name

Release

001094

FAIL MOC TEST CALL

S4

Description Number of unsuccessful MOC test calls during a scheduled test.

Updated When the RRM receives a message from the BTTEST.


BSC4531: BTS Testing: Scheduled MOC

Number

Name

Release

001095

PRI SUBSCR TCH REQ

S5

Trigger points See figures:. Basic call with priority subscriber . Unsuccessful forced release. Unsuccessful forced release with external handover . Unsuccessful forced handover . Unsuccessful forced handover with external handover

Description Number of TCH requests of the type priority subscriber

Updated When the RRM receives a TCH request either in a call or HOattempt and the MS priority level in the priority information element(PIE) indicates that the MS is a priority subscriber.



Feature BSS5190: Enhanced Trunk Reservation






Number

Name

Release

001096

PRI SUBSCR SUCC TCH SEIZ

S5

Trigger points See figure Basic call with priority subscriber

Description Number of successful TCH seizures of the type priority subscriber.

Updated When the RRM allocates a TCH as a response to a TCH request ineither a call or HO attempt and the MS priority level in the priorityinformation element (PIE) indicates that the MS is a prioritysubscriber.


Counter 001008 or 001009 is updated along with this counter.


Number

Name

Release

001097

NO PRI SUBSCR REFUSED TCH REQ

S5

Trigger points See figure Unsuccessful trunk reservation

Description Number of TCH requests of the type non-priority subscriber that arerejected because there are no resources available to subscribersother than priority subscribers.

Updated When the RRM rejects a TCH request because of no resourcesavailable to subscribers other than priority subscribers.




Number

Name

Release

001098

TCH SEIZ ATT DUE SDCCH CON

S5

Trigger points See figures:. FACCH call setup due to SDCCH congestion with counters. FACCH call setup because of SDCCH congestion

Description Number of attempts to seize a TCH because of SDCCH congestion.

Updated When the RRM attempts to allocate a TCH as a response to arequest for an SDCCH seizure during SDCCH congestion. The RRMdoes this if the TCH allocation (=FACCH setup) is allowed in themessage carrying the request for the SDCCH seizure.







Number

Name

Release

001098

TCH SEIZ ATT DUE SDCCH CON

S5


Number

Name

Release

001099

TCH SEIZ DUE SDCCH CON

S5


Description Number of successful TCH seizures because of congestion on theSDCCH.

Updated When the RRM allocates a TCH as a response to a request for SDCCH seizure during congestion on the SDCCHs. The RRMallocates a TCH if the TCH allocation (=FACCH setup) is allowed inthe message carrying the request for the SDCCH seizure.


This counter is updated along with counter 001044.


Number

NameRelease

001100

TRUNK TCH REJECTED FR REQS5


Description Number of requests for trunk reservation function that result in therejection of TCH allocation when FR or preferred FR TCH has beenrequested.

Updated When the RRM denies access by applying the trunk reservationfunction and FR or preferred FR TCH has been requested.



Feature BSS5010: Half Rate and BSS5190 Enhanced Trunk Reservation






Number

Name

Release

001101

TRUNK TCH REJECTED HR REQ

S5


Description Number of requests for trunk reservation function that result inrejection of TCH allocation when HR or preferred HR TCH has beenrequested.

Updated When the RRM denies access by applying the trunk reservationfunction and HR or preferred HR TCH has been requested.



Feature BSS5010: Half Rate and BSS5190 Enhanced Trunk Reservation

Number

Name

Release

001102

FULL TCH REQ SUCC UNSUCC

S5

Trigger points See figures:. Basic call with counters. Basic call with priority subscriber . Basic call, no free TCH and queuing or directed retry is not allowed . Successful TCH queuing . Basic call, no free TCHs, unsuccessful queuing and directed retry

not activated . Unsuccessful trunk reservation. Successful internal intra-cell handover . Internal intra-cell HO, successful TCH queuing . Unsuccessful underlay overlay internal intra-cell handover, queuing

not allowed . Internal intra-cell handover, unsuccessful TCH queuing . Internal directed retry . Successful internal inter-cell handover . Successful external handover, target . Successful forced release.

Unsuccessful forced release. Unsuccessful forced release with external handover . Successful forced handover . Unsuccessful forced handover . Unsuccessful forced handover with external handover

Description Number of requests for FR TCH (both successful and unsuccessful).







Number

Name

Release

001103

HALF TCH REQ SUCC UNSUCC

S5

Updated When the RRM receives a TCH request either in a call or HOattempt and HR TCH channel is requested.

NOTE! This counter is updated when the channel rate of therequested TCH is defined to be HR only; the type of the TCH may belimited either by an assignment request or a handover request fromthe A interface, or it may be because of the BSC restricting theselection of channel type in TCH allocation.



Feature BSS5010: Half Rate

Number

Name

Release

001104

TCH REQ FULL PREFERRED

S5

Trigger points See figures:. Basic call with counters. Basic call with priority subscriber . Basic call, no free TCH and queuing or directed retry is not allowed . Successful TCH queuing . Basic call, no free TCHs, unsuccessful queuing and directed retry



not allowed . Internal intra-cell handover, unsuccessful TCH queuing . Internal directed retry . Successful internal inter-cell handover .

Successful external handover, target . Successful forced release. Unsuccessful forced release. Unsuccessful forced release with external handover . Successful forced handover . Unsuccessful forced handover . Unsuccessful forced handover with external handover

Description Number of TCH requests with FR preferred (both successful andunsuccessful).





Number

Name

Release

001104

TCH REQ FULL PREFERRED

S5

Updated When the RRM receives a TCH request either in a call or HOattempt and FR or HR TCH channel is requested alternatively withFR preferred.

NOTE! The preferred channel rate can be defined either by anassignment request or HO request received from the A interface or by software which is activated on the BSC for controlling theselection of the channel type in TCH allocation. In the latter case thepreferred channel type can be quite the opposite to the one initiallyset by the MSC.




Number

Name

Release

001105

TCH REQ HALF PREFERRED

S5

Trigger points See figures:. Basic call with counters. Basic call with priority subscriber . Basic call, no free TCH and queuing or directed retry is not allowed .

Successful TCH queuing . Basic call, no free TCHs, unsuccessful queuing and directed retry



not allowed . Internal intra-cell handover, unsuccessful TCH queuing . Internal directed retry . Successful internal inter-cell handover . Successful external handover, target . Successful forced release. Unsuccessful forced release. Unsuccessful forced release with external handover . Successful forced handover . Unsuccessful forced handover . Unsuccessful forced handover with external handover






Number

Name

Release

001105

TCH REQ HALF PREFERRED

S5

Description Number of TCH requests with HR preferred (both successful andunsuccessful).

Updated When the RRM receives a TCH request either in a call or HOattempt and FR or HR TCH channel is requested alternatively withHR preferred.

NOTE! The preferred channel rate can be defined either byassignment request or HO request received from the A interface or by softwares which are activated on the BSC for controlling theselection of the channel type in TCH allocation. In the latter case thepreferred channel type can be quite the opposite to the one initiallyset by the MSC.




Number

Name

Release

001106

SUCC FULL TCH SEIZ

S5

Trigger points See figures:. Basic call with counters.

Basic call with priority subscriber . Successful TCH queuing . Successful internal intra-cell handover . Internal intra-cell HO, successful TCH queuing . Successful internal inter-cell handover . Successful external handover, target . Successful forced release. Successful forced handover

Description Number of successful FR TCH seizures.

Updated When the RRM allocates an FR TCH as a response to a TCHrequest.


Either counter 001008 or counter 001009 is updated along with thiscounter.






Number

Name

Release

001107

SUCC HALF TCH SEIZ

S5

Trigger points See figures:. Basic call with counters. Basic call with priority subscriber . Successful TCH queuing . Successful internal intra-cell handover . Internal intra-cell HO, successful TCH queuing . Successful internal inter-cell handover . Successful external handover, target . Successful forced release. Successful forced handover

Description Number of successful HR TCH seizures.

Updated When the RRM allocates an HR TCH as a response to a TCHrequest.


Either counter 001008 or counter 001009 is updated along with thiscounter.







Number

Name

Release

001108

FULL TCH SEIZ SPEECH VER 1

S5

Trigger points See figures:. Normal release. Unsuccessful TCH activation. Unsuccessful TCH activation, timer expires while waiting for

CHANNEL_ACTIVATION_ACK message. TCH assignment failure. TCH assignment failure, MSC sends CLEAR_COMMAND

message. CONNECTION_FAILURE message with cause transcoder_failure

during a call . TRX or TSL is blocked with different causes during a call . Unsuccessful internal intra-cell handover, timer expires while

waiting for CHANNEL_ACTIVATION_ACK message. Unsuccessful internal intra-cell handover,

CONNECTION_FAILURE message with causeremote_transcoder_failure comes to the target channel

. Unsuccessful internal intra-cell handover, timer expires on thesource channel, call cleared

. Unsuccessful internal inter-cell handover

. Successful external handover, source



. Successful forced release

. Timer T3107 expires while waiting for ASSIGNMENT_COMPLETE message

. Dropped call between ASSIGNMENT COMPLETE and DISCONNECT

. Dropped call between ASSIGNMENT COMPLETE and RF CHANNEL RELEASE ACK

Description Number of successful FR TCH seizures when speech FR version 1is in use.

Updated When an FR TCH allocated for speech is released and the FR codecversion 1 is in use.






Number

Name

Release

001109


S5
























Number

Name

Release

001110


S5























Number

Name

Release

001111

HALF TCH SEIZ SPEECH VER 1

S5
















Description Number of successful HR TCH seizures when speech FR version 1is in use.

Updated When an HR TCH allocated for speech is released and the HRcodec version 1 is in use.







Number

Name

Release

001112


S5























Number

Name

Release

001113


S5
























Number

Name

Release

001114

FULL TCH SEIZ NORM ASSIGNMENT

S5


Description Number of successful FR TCH seizures for a normal assignment.

Updated When the RRM allocates an FR TCH as a response to a TCHrequest in a call attempt.




Number

Name

Release

001115

HALF TCH SEIZ NORM ASSIGNMENT

S5


Description Number of successful HR TCH seizures for a normal assignment.

Updated When the RRM allocates an HR TCH as a response to a TCHrequest in a call attempt.




Number

Name

Release

001116

FULL TCH SEIZ INT HO CH RATE

S5






Number

Name

Release

001116

FULL TCH SEIZ INT HO CH RATE

S5

Description Number of successful FR TCH seizures for an internal HO when thechannel rate changes.

Updated When the RRM allocates an FR TCH for an internal HO as aresponse to a TCH request and the channel rate is changed from HRto FR.




Number Name

Release

001117HALF TCH SEIZ INT HO CH RATE

S5


Description Number of successful HR TCH seizures for an internal HO when thechannel rate changes.

Updated When the RRM allocates an HR TCH for an internal HO as a

response to a TCH request and the channel rate is changed from FRto HR.











Number

Name

Release

001119

REJ TCH REQ DUE LACK HR

S5

Description Number of TCH requests that are rejected because of a lack of resources, when HR or preferred HR TCH is requested.

Updated When no TCHs are available when requested from the RRM either ina call or HO attempt and either HR or preferred HR TCH wasrequested. The counter may be updated immediately after the TCHrequest or, in case of queuing after the queuing, timer expires.




Number

Name

Release

001120

FULL TCH REJ DUE HR TRAF

S5

Trigger points See figures:. FACCH call setup due to SDCCH congestion, no free TCH channel . Basic call, no free TCH and queuing or directed retry is not allowed . Successful TCH queuing . Basic call, no free TCHs, unsuccessful queuing and directed retry

not activated . Unsuccessful trunk reservation. Internal intra-cell HO, successful TCH queuing . Unsuccessful underlay overlay internal intra-cell handover, queuing

not allowed . Internal intra-cell handover, unsuccessful TCH queuing . Successful forced release. Unsuccessful forced release. Unsuccessful forced release with external handover . Successful forced handover . Unsuccessful forced handover . Unsuccessful forced handover with external handover

Description Number of requests for FR TCHs that are rejected because of HRtraffic, whether queuing occurred or not.

Updated When no FR TCH is available in a situation where HR calls are beingmaintained in DR TSLs and there are free HR TCHs among the DRor permanent HR resources for at least two HR calls.

NOTE! The counter is incremented on receipt of the request for theFR TCH, regardless of whether the request is set in the queue, pre-empted, subjected to directed retry or some other procedure of thekind.









Number

Name

Release

001122

TCH REJ DUE REQ CH A IF CRC

S5

Feature BSS5010 Half Rate

Number

Name

Release

001123

FULL TCH REQ FACCH CALL

S5

Trigger points See figures:. FACCH call setup due to SDCCH congestion with counters. FACCH call setup due to SDCCH congestion, no free TCH channel

Description Number of requests for FR TCH in FACCH call setup during SDCCHcongestion (both successful and unsuccessful).

Updated When the RRM receives a request for SDCCH allocation but no idleSDCCHs exist and TCH allocation (=FACCH call setup) is allowed inthe request which also indicates that the TCH rate should be FR.




Number

Name

Release

001124

TCH FACCH CALL CH RATE NOT DEF

S5

Trigger points See figures:. FACCH call setup due to SDCCH congestion with counters. FACCH call setup due to SDCCH congestion, no free TCH channel

Description Number of requests for TCHs in FACCH call setup during SDCCHcongestion when the TCH rate is not defined to be uniquely FR or HR (both successful and unsuccessful).

Updated When the RRM receives a request for SDCCH allocation but no idleSDCCHs exist and TCH allocation (=FACCH call setup) is allowed in

the request which also indicates that either of the two possiblechannel rates is accepted to be allocated.









Number

Name

Release

001125

SUCC FULL TCH SEIZ FACCH CALL

S5


Description Number of successful FR TCHs seizures for a FACCH call setup.

Updated When the RRM allocates an FR TCH as a response to an SDCCHrequest as part of the FACCH call setup during SDCCH congestion.



Feature BSS5010 Half Rate

Number

Name

Release

001126

SUCC HALF TCH SEIZ FACCH CALL

S5


Description Number of successful HR TCHs seizures for a FACCH call setup.

Updated When the RRM allocates an HR TCH as a response to an SDCCHrequest as part of the FACCH call setup during SDCCH congestion.




Number

Name

Release

001127

ENDED DUE TRANSC FR RATE 1

S5

Trigger points See figures:. CONNECTION_FAILURE message with cause transcoder_failure

during a call . Unsuccessful internal intra-cell handover,


Description Number of radio TCH transactions that are ended because of atranscoder failure when speech FR version 1 is in use.

Updated When one of the transcoder failure counters 001029, 001030 or 001031 is updated and the FR codec version 1 is in use.






Number

Name

Release

001128


S5




Description Number of radio TCH transactions that are ended because of atranscoder failure when speech FR version 2 is in use.



Number

Name

Release

001129


S5



CONNECTION_FAILURE message with cause

remote_transcoder_failure comes to the target channel Description Number of radio TCH transactions that are ended because of a

transcoder failure when speech FR version 3 is in use.



Number

Name

Release

001130

ENDED DUE TRANSC HR RATE 1


. CONNECTION_FAILURE message with cause transcoder_failureduring a call

. Unsuccessful internal intra-cell handover,CONNECTION_FAILURE message with causeremote_transcoder_failure comes to the target channel

Description Number of radio TCH transactions that are ended because of atranscoder failure when speech HR version 1 is in use.






Number

Name

Release

001130


S5

Updated When one of the transcoder failure counters 001029, 001030, or 001031 is updated and the HR codec version 1 is in use.


Number

Name

Release

001131


S5




Description Number of radio TCH transactions that are ended because of atranscoder failure when speech HR version 2 is in use.

Updated When one of the transcoder failure counters 001029, 001030 or 001031 is updated and the HR codec version 2 is in use.


Number

Name

Release

001132


S5Trigger Points See figures:


. Unsuccessful internal intra-cell handover, CONNECTION_FAILURE message with cause remote_transcoder_failure comes to the target channel

Description Number of radio TCH transactions that are ended because of a

transcoder failure when speech HR version 3 is in use.

Updated When one of the transcoder failure counters 001029, 001030 or 001031 is updated and the HR codec version 3 is in use.






Number

Name

Release

001133

FULL TCH TR FAIL

S5

Trigger points See figures:. Unsuccessful TCH activation. Unsuccessful TCH activation, timer expires while waiting for











Description Total number of FR TCH transaction failures.

Updated When an FR TCH transaction ends because of any abnormal reason,that is, some specific failure counter has been updated, and the RRMreleases the FR TCH.







Number

Name

Release

001134

HALF TCH TR FAIL

S5

Trigger points See figures:. Unsuccessful TCH activation. Unsuccessful TCH activation, timer expires while waiting for











Description Total number of HR TCH transaction failures.

Updated When an HR TCH transaction ends because of any abnormalreason, that is, some specific failure counter has been updated, andthe RRM releases the HR TCH.


Number

Name

Release

001135

SDCCH SEIZ ATT FOR MOC

S6

Trigger points See figures:. Basic call with counters. FACCH call setup due to SDCCH congestion with counters. FACCH call setup due to SDCCH congestion, no free TCH channel . SDCCH congestion, FACCH call setup is not activated . Successful SDCCH internal intra-cell handover . Successful SDCCH internal inter-cell handover . Reconfiguration from TCH to SDCCH





Number

Name

Release

001135

SDCCH SEIZ ATT FOR MOC

S6

Description Number of SDCCH seizure attempts for an MOC. In case of anexternal handover and handovers after external handover thiscounter is not incremented. In case of an intra-cell or inter-cell(SDCCH to SDCCH) handover this counter is updated.

Updated When the RRM receives a request for a SDCCH from an MSbecause the MS needs a channel for a MOC. Note that this counter contains all requests for an SDCCH in originating direction, for example Mobile Originating calls, Location Updates, SupplementaryService requests and SMS on SDCCH. In case of an SMS thiscounter is triggered even if the SMS would eventually be sent onTCH instead of SDCCH.



Number

Name

Release

001136

SDCCH SEIZ ATT FOR MTC

S6

Trigger points See figures:. Basic call with counters. FACCH call setup due to SDCCH congestion with counters. FACCH call setup due to SDCCH congestion, no free TCH channel . SDCCH congestion, FACCH call setup is not activated . Successful SDCCH internal intra-cell handover . Successful SDCCH internal inter-cell handover . Reconfiguration from TCH to SDCCH

Description Number of SDCCH seizure attempts for an MTC. In case of anexternal handover and handovers after external handover thiscounter is not incremented. In case of an intra-cell or inter-cell(SDCCH to SDCCH) handover this counter is updated.

Updated When the RRM receives a request for a SDCCH from an MS as theMS needs a channel for a MTC. Note that this counter contains allrequests for an SDCCH in terminating direction, for example Mobile

Terminating calls and SMS on SDCCH. In case of an SMS thiscounter is triggered even if the SMS would eventually be sent onTCH instead of SDCCH.








Number

Name

Release

001137

TCH SEIZ ATT FOR MOC

S6

Trigger points See figures:. Basic call with counters. Basic call with priority subscriber . FACCH call setup due to SDCCH congestion with counters. FACCH call setup due to SDCCH congestion, no free TCH channel . Basic call, no free TCH and queuing or directed retry is not allowed . Successful TCH queuing . Basic call, no free TCHs, unsuccessful queuing and directed retry



not allowed . Internal intra-cell handover, unsuccessful TCH queuing . Internal directed retry . Successful internal inter-cell handover . Successful forced release. Unsuccessful forced release. Successful forced handover . Unsuccessful forced handover

Description Number of TCH seizure attempts during an MOC, in call setup phasebefore connection acknowledgement. In case of an externalhandover and handovers after external handover this counter is notincremented. In case of an intra-cell or inter-cell (TCH to TCH or SDCCH to TCH) handover this counter is updated.

Updated When RRM receives requests for a TCH for an MOC. In FACCH callsetup RRM attempts to allocate a TCH as a response to a requestfor an SDCCH seizure during SDCCH congestion.







Number

Name

Release

001138

TCH SEIZ ATT FOR MTC

S6

Trigger points See figures:. Basic call with counters. Basic call with priority subscriber . FACCH call setup due to SDCCH congestion with counters. FACCH call setup due to SDCCH congestion, no free TCH channel . Basic call, no free TCH and queuing or directed retry is not allowed . Successful TCH queuing . Basic call, no free TCHs, unsuccessful queuing and directed retry



not allowed . Internal intra-cell handover, unsuccessful TCH queuing . Internal directed retry . Successful internal inter-cell handover . Successful forced release. Unsuccessful forced release. Successful forced handover . Unsuccessful forced handover

Description Number of TCH seizure attempts during an MTC, in call setup phasebefore connection acknowledgement. In case of an externalhandover and handovers after external handover this counter is notincremented. In case of an intra-cell or inter-cell (TCH to TCH or SDCCH to TCH) handover this counter is updated.

Updated When RRM receives requests for a TCH for an MTC. In FACCH callsetup RRM attempts to allocate a TCH as a response to a requestfor an SDCCH seizure during SDCCH congestion.








Number

Name

Release

001139

TCH REL because of RADIO FAIL

S6

Trigger points See figure Timer T3107 expires while waiting for ASSIGNMENT_COMPLETE message

Description Number of TCH releases because of radio failures, in call setupphase before connection acknowledgement. This counter is alsoupdated in an intra-cell or inter-cell handover, if the TCH is releasedbecause of a radio failure before the conversation phase (handover is started and it fails before a connection acknowledgement messageis received).

Updated When a TCH is released because of a radio failure.

This counter is updated in call phases 2, 3, 5, or 8-14 only.



Number

Name

Release

001140

TCH REL DUE TO BSS FAIL

S6


CHANNEL_ACTIVATION_ACK message. TCH assignment failure, MSC sends CLEAR_COMMAND

messageDescription Number of TCH releases because of BSS failures, in call setup

phase before connection acknowledgement. This counter is alsoupdated in intra-cell or inter-cell handover, if the TCH is releasedbecause of BSS problems before conversation phase (handover isstarted and fails before connection acknowledgement message isreceived).

Updated When a TCH is released because of BSS problems.

This counter is updated in call phases 2, 3, 5, or 8-14 only.







Number

Name

Release

001141

TCH SEIZ FAILS DUE TO CONG

S6

Trigger points See figures:. FACCH call setup due to SDCCH congestion, no free TCH channel . Basic call, no free TCH and queuing or directed retry is not allowed . Basic call, no free TCHs, unsuccessful queuing and directed retry


and directed retry not allowed . Unsuccessful forced release. Unsuccessful forced handover

Description Number of TCH seizure failures because of congestion during callsetup before connection acknowledgement. This counter is alsoupdated in intra-cell or inter-cell handover, if the TCH attempt failsbecause of congestion before conversation phase (handover isstarted and fails before connection acknowledgement message isreceived). In case of an external handover and handovers after external handover this counter is not incremented.

Updated When RRM rejects a TCH request because of congestion.

This counter is updated in call phases 2, 3, 5, or 8 only.



Number Name

Release

001142QUEUED URGENT HANDOVER ATTEMPTS

S6

Trigger points See figures:. Internal intra-cell HO, successful TCH queuing . Internal intra-cell handover, unsuccessful TCH queuing

Description Number of queued urgent handover attempts.

Updated When a TCH request for an urgent handover attempt is put to thequeue because of a lack of available TCH resources requested.

Dependencies with other counters/ PI(s) Counters 001010 and 001064 are updated along with this counter.

Feature BSS6115: Radio Channel Allocation Enhancements






Number

Name

Release

001143

AVE QUE TIME OF URGENT HO ATTEMPTS

S6


Description Numerator of average queuing time of queued urgent handover attempts (unit of the value is 10 ms).

Updated When a TCH request for an urgent handover attempt is removedfrom the queue (both in a successful and an unsuccessful case).


In a successful case counters 001008, 001022 and 001144 areupdated along with this counter. In an unsuccessful case counters001022, 001025, 001068 and 001144 are updated along with thiscounter.



Unit 10 ms

Number

Name

Release

001144

QUE DENOMINATOR 4

S6


Description Denominator of average queuing time of queued urgent handover attempts.

Updated Every 20 seconds. The averaging is made within the measurementperiod.




Number

Name

Release

001145

AVE QUE TIME OF NON URGENT HO ATTEMPTS

S6






Number

Name

Release

001145

AVE QUE TIME OF NON URGENT HO ATTEMPTS

S6

Description Numerator of average queuing time of queued non-urgent handover attempts.

Updated When a TCH request for a non-urgent HO attempt is removed fromthe queue (both in a successful and unsuccessful case).


In a successful case counters 001008, 001022 and 001146 areupdated along with this counter. In an unsuccessful case counters001022, 001025, 001068 and 001146 are updated along with thiscounter.



Number

Name

Release

001146

QUE DENOMINATOR 5

S6


Description Denominator of average queuing time of queued urgent HO attempts(unit of the value is 10 ms).

Updated Every 20 seconds. The averaging is made with the measurementperiod.




Unit 10 ms

Number

Name

Release

001147

QUEUED URG HO ATTS NOT SERVED

S6


Description Number of queued urgent handover attempts not served.

Updated When the urgent HO attempt is removed from the queue because of queuing timer expiry or substitution by a higher priority queuing item.


Counters 001022, 001025, 001068 and 001143 are updated alongwith this counter.

Feature BSS6115 Radio Channel Allocation Enhancements






Number

Name

Release

001148

MS SUCC TCH SEIZURE FOR ASSIGNMENT COMPLETE

S7

Trigger points See figure Normal call

Description Number of times when a MS is successfully on the TCH after an ASSIGNMENT_COMPLETE message.

Updated When anASSIGNMENT_COMPLETE message is received from theMS via BTS to TCH. The TCH is reserved and the MS is moved fromthe SDCCH to the TCH. This counter is updated only when a call isestablished for the first time, not during handovers.

This counter is not updated with softwares FACCH call setupbecause of SDCCH congestion, directed retry procedure in BSC,TCH assignment to super reuse TRX in IUO and direct access tosuper re-use TRX in IUO.

Number

Name

Release

Definition updated

001149

CALLS ENDED BY USER DURING DADL/B SETUP

S7

S11.5

Description Number of CALLS RELEASED BY USER in a call setup phaseduring DADL/B handover.

Updated When the user releases the call in call setup phase and BSC hasstarted to evaluate the potential target cells for DADL/B handover.

Number

Name

Release

Definition updated

001150

SUCC TCH SEIZ WHEN GOOD QUAL IN ADJACENTS

S8

S12

Description This counter is no longer in use.

Updated Not updated





Number

Name

Release

Definition updated

001151

TCH REQ REJ DUE TO BAD QUALITY IN ADJACENT

S8

S12


Updated Not updated

Number

Name

Release

Definition updated

001152

SUCC TCH SEIZ WHEN QUAL BETW GOOD AND BAD INADJACENT

S8

S12Description This counter is no longer in use.

Updated Not updated

Number

Name

Release

Definition updated

001153

TCH REQ REJ WHEN QUAL BETW GOOD AND BAD INADJACENT

S8

S12


Updated Not updated

Number

Name

Release

001154

DYNAMIC SDCCH RECONFIGURATION ATTEMPT

S7

Trigger points See figure Reconfiguration from TCH to SDCCH

Description Number of SDCCH reconfiguration attempts for immediate

assignment.Updated When a SDCCH channel is needed for an immediate assignment

and no free SDCCHs are available and the request is sent for reconfiguring a TCH channel to a SDCCH channel. This counter isnot updated if reconfiguration is done from SDCCH to TCH channel.



Feature BSS7036 Dynamic SDCCH allocation






Number

Name

Release

001155

UNSUCC IMM ASS SDCCH ATTEMPT

S7


Description Number of unsuccessful SDCCH allocation attempts for immediateassignment.

Updated When the SDCCH channel allocation does not succeed because of alack of SDCCH resources at the time of the immediate assignment.When SDCCH is released with the dx-cause rtsl_reconf_fail_c.

Triggered for example when a dynamic SDCCH allocation (1154DYNAMIC_SDCCH_RECONFIGURATION_ATTEMPT) is tried but itfails. Failure can be caused for example by the following situations.. In the BCSU there cannot be more SDCCH allocated.. All TCHs are busy and cannot be reallocated.. RRM has reconfigured a TCH to SDCCH but ABI cannot do the

same. In this case the dynamic SDCCH seized by RRM is releasedwith cause rtsl_reconf_fail and the call attempt fails (blocking).



Feature BSS7036: Dynamic SDCCH allocation

Number

NameRelease

001156

HSCSD TCH REQ WITH 14,4S7

Trigger points See figures:. Mobile originated HSCSD call setup. Successful internal inter-cell handover for HSCSD, target cell

allocations and activations for three channels

Description Number of TCH requests for 14.4 kbit/s data.

NOTE! Despite its name, this counter is not related to High SpeedCirciuit Switched Data (HSCSD), but the single slot 14.4 kbit/s dataservices.

Updated When the RRM receives a TCH request for a single slot 14.4 kbit/sdata connection in a call or a handover attempt.


Counters for a TCH request.

Feature BSS7037: 14.4 kbit/s data services





Number

Name

Release

001157

HSCSD SUCC TCH SEIZ WITH 14,4

S7



Description Number of successful TCH seizures for 14.4 kbit/s data.

NOTE! Despite of its name, this counter is not related to High SpeedCirciuit Switched Data (HSCSD), but the single slot 14.4 kbit/s dataservices.

Updated When the RRM allocates a TCH/F as a response to a single slot14.4 kbit/s request in a call or handover attempt.


Counters for a successful TCH seizures.

Feature BSS7037: 14.4 kbit/s data services

Number

Name

Release

001158

HSCSD TRANSP TCH REQ

S7



Description Number of transparent HSCSD TCH requests.

Updated When TCH/F(s) is / are requested for a transparent HSCSD servicefrom the RRM in a call or a handover attempt.



Feature BSS7003: High speed circuit switched data

Number

Name

Release

001159

HSCSD SUCC TRANSP TCH SEIZ

S7



Description Number of successful transparent HSCSD TCH seizures.






Number

Name

Release

001159

HSCSD SUCC TRANSP TCH SEIZ

S7

Updated When TCH/F has been successfully allocated for transparent HSCSDservice by RRM. Incrementation is made only by the HSCSD mainchannel allocation.




Number

Name

Release

001160

HSCSD REQ FOR CALL SETUP

S7

Trigger points See figure Mobile originated HSCSD call setup

Description Number of HSCSD TCH requests for a call set-up.

Updated When the HSCSD data connection is requested from the RRM in acall attempt.




Number

Name

Release

001161

HSCSD TCH REQ FOR HO

S7

Trigger points See figure Successful internal inter-cell handover for HSCSD, target cell allocations and activations for three channels

Description Number of HSCSD TCH requests for a HO.

Updated When the HSCSD data connection is requested from the RRM in ahandover attempt.








Number

Name

Release

001162

HSCSD SUCC TCH SEIZ FOR CALL SETUP

S7

Trigger points See figure Mobile originated HSCSD call setup

Description Number of successful HSCSD TCH seizures for a call set-up.

Updated When the RRM allocates a main HSCSD TCH/F as a response to anHSCSD call attempt.



Feature BSS7003 High speed circuit switched data

Number

Name

Release

001163

HSCSD SUCC TCH SEIZ FOR HO

S7

Trigger points See figure Successful internal inter-cell handover for HSCSD, target cell allocations and activations for three channels

Description Number of successful HSCSD TCH seizures for a HO.

Updated When the RRM allocates a main HSCSD TCH/F as a response to ahandover attempt.




Number

Name

Release

001164

HSCSD CON REL DUE TO FAIL

S7

Trigger points See figure A CONNECTION_FAILURE message which comes during an HSCSD

Description Number of HSCSD connection releases because of a failure.

Updated When the HSCSD main TCH/F is released with dx_cause indicating

a failure.


Impact HO failure, Call cleared








Number

Name

Release

001168

SUCC TCH SEIZ FOR A BSC CONTROLLED TRHO

S8

Trigger points See figure Successful BSC controlled TRHO

Description Number of successful TCH seizures for a BSC-controlled TRHO

Updated When the RRM allocates a TCH as a response to a TCH request ina BSC-controlled TRHO attempt.

Feature BSS8123 Advanced Multilayer Handling

Number

Name

Release

001169

REJ TCH SEIZ FOR A BSC CONTROLLED TRHO DUELACK OF RESOURCES

S8

Trigger points See figure Unsuccessful BSC controlled TRHO

Description Number of rejected TCH requests for a BSC-controlled TRHOprocedure because of exceeded load in the target cell.

Updated When the RRM rejects traffic channel allocation because of exceeded load in the target cell in a BSC-controlled TRHO.

Feature BSS8123: Advanced Multilayer Handling

Number

Name

Release

001170

SUCCESSFUL TCH SEIZURES FOR DADLB HO

S8

Trigger points See figure Successful handover due to DADL/B

Description The number of successful TCH seizures because of DADL/Bhandover.

Updated The counter is updated when a TCH allocation in the target cellduring DADL/B handover is successful. BSC internal handover case.

Feature BSS8032: Direct Access to Desired Layer/band

Number

Name

Release

001171

TCH REQUEST IN DADLB HO REJECTED

S8

Trigger points See figure Unsuccessful DADL/B handover due to lack of resources

Description Number of TCH requests in DADL/B handover rejected because of alack of TCH.






Number

Name

Release

001171

TCH REQUEST IN DADLB HO REJECTED

S8

Updated The counter is updated when a TCH allocation in the target cellduring DADL/B handover is unsuccessful because of lack of TCH.BSC internal handover case.


Number

Name

Release

001172

DADLB START DUE TO EXCEEDED LOAD

S8

Trigger points See figures:. Successful handover due to DADL/B. Unsuccessful DADL/B handover due to lack of resources

Description Number of DADL/B handover at tempts, started because of exceededload in accessed cell.

Updated This counter is updated when channel request is rejected because of excessive load and Radio Resource management requests a DADL/ B handover. If the target cell is found within MaxTimeLimitDR, theDADL/B handover is started and also the counter 4129 is updated. If this timer triggers the DADL/B handover is not started.


004129 is updated if DADL/B HO is started.


Number

Name

Release

001173

REMOVAL FROM QUE DUE TO DR

S8

Trigger points See figure Internal directed retry

Description Number of requests removed from the queue because of start of DR.

Updated This counter is updated when a request is removed from the queue

by the RRM because of the start of DR.





Number

Name

Release

001174

GPRS TER UPGRD REQ

S9

Description Number of territory upgrade requests received from the PacketController Unit.

Updated When the Radio Resource Management receives from the PacketController Unit a request for new radio time slots to be added into theGPRS territory. The PCU can request an upgrade after BSC hasfulfilled the default territory defined by the operator parameters.

The upgrade of the GPRS territory may be started for variousreasons, for example when GPRS is set enabled in a BTS, GPRS-TRX is created or deblocked, TSL inside the GPRS territory isdeblocked or CS load decreases, but this counter is not triggered inthese cases.

NOTE! This counter is triggered only when GPRS Territory Upgradeis started by Packet Switched Radio Resource Managementrequesting additional GPRS capacity.

Feature BSS9006: GPRS Telecom in BCSU and MCMU

Number

Name

Release

001175

INCOMPL SERV GPRS TER UPGR REQ

S9

Description Number of territory upgrade requests that have been served with lessradio time slots than requested.

Updated When Radio Resource Management upgrades the GPRS territorywith less RTSLs than the Packet Controller Unit requested for.


Number

Name

Release

001176

GPRS TER UG REJ DUE CSW TR

S9

Description Number of territory upgrade requests that have been rejectedbecause of the high load of the circuit switched traffic.

Updated When Radio Resource Management rejects a GPRS territoryupgrade request from the PCU because of high traffic load in BTSand maintaining the margin of idle TCHs for circuit switched trafficdoes not allow the upgrade.







Number

Name

Release

001177

GPRS TER UG REJ DUE LACK PSW RES

S9

Description Number of territory upgrade requests that have been rejectedbecause there are not enough resources capable of GPRS in theBTS.

Updated When Radio Resource Management rejects a GPRS territoryupgrade request of the PCU because all TRXs capable of GPRStraffic are already within the GPRS territory.


Number

NameRelease

001178

GPRS TER UG REJ DUE LACK PCU CAPS9

Description Number of territory upgrade requests that have been rejectedbecause the capacity of the Packet Controller Unit the BTS isconnected to is already totally in use.

Updated When Radio Resource Management rejects a GPRS territoryupgrade request from the PCU because the maximum number of TSLs, which the PCU is capable to handle are already in use.


Number Name

Release

001179GPRS TER DG DUE INC IN CSW TR

S9

Description Number of GPRS territory downgrades made because of theincrease in the circuit switched traffic load.

Updated When the Radio Resource Management starts a GPRS territorydowngrade in order to maintain the margin of idle TCHs for circuitswitched traffic after a circuit switched channel allocation, or whenthe BSC during TCH congestion in the CSW territory directlyallocates a TCH belonging to the GPRS territory.






Number

Name

Release

001180

GPRS TER UG DUE DEC CSW TR

S9

Description Number of GPRS territory upgrades made to fulfill the default GPRSterritory as a consequence of decrease in the circuit switched trafficload.

Updated When the Radio Resource Management starts a GPRS territoryupgrade in order to fulfill the defined default GPRS territory after thetraffic load in the BTS has decreased as a consequence of a circuitswitched channel release.


Number

Name

Release

001181

GPRS TER DOWNGRADE REQ

S9

Description Number of territory downgrade requests received from the PacketController Unit.

Updated When the Radio Resource Management receives from the PacketController Unit a request for a GPRS territory downgrade. The PCUcan request for a downgrade for GPRS RTSLs beyond the defaultterritory defined by the operator parameters. A GPRS territorydowngrade is initiated because of increase of CS load. PCU caninitiate GPRS resource downgrade to additional GPRS resources.For example, when PCU has previously requested GPRS territory

upgrade and additional channels has been given for GPRS use.When there is no more need for additonal GPRS capacity PCUrequests for downgrade, the additional channels are removed fromGPRS territory and this counter is triggered.


Number

Name

Release

001182

FULL TCH SEIZ INTRA AMR HO

S10

Description Number of successful FR TCH seizures for an intra-cell HO when thechannel rate changes and AMR speech codecs are in use.

Updated When the Radio Resource Management allocates a FR TCH for intra-cell HO as a response to a TCH request and the channel rate ischanged from HR to FR and speech codec versions 3 are in use.



Feature BSS10004: Adaptive Multi Rate Codec






Number

Name

Release

001183

HALF TCH SEIZ INTRA AMR HO

S10

Description Number of successful HR TCH seizures for intra-cell HO when thechannel rate changes and AMR speech codecs are in use.

Updated When the Radio Resource Management allocates a HR TCH for intra-cell HO as a response to a TCH request and the channel rate ischanged from FR to HR and speech codec versions 3 are in use.




Number Name

Release

001184TCH CALL REQ FOR AMR

S10

Description Number of TCH requests for an AMR call.

Updated When the Radio Resource Management receives a TCH request in acall setup or HO attempt and speech codec version 3 is the mostpreferred one.


Counter 001026 is updated along with this counter in case of callsetup.


Number

Name

Release

001185

SUCCESSFUL AMR CODEC SET DOWNGRADES

S10

Description Number of successful AMR codec set downgrades during internalHOs for the source side AMR codec set. Downgrade is made to alignthe source side AMR codec set with the one chosen for the targetside in order to utilize the one-way downlink speech path connectionfor the target side during the internal HO. The utilization of one-waydownlink speech path connection decreases the amount of muting

experienced in the speech path connection. Downgrade decisionduring internal HO depends on the parameter AMR codec mode setdowngrades and upgrades enabled.

Updated By the Abis interface services after successful mode modifyprocedures for BTS and MS.






Number

Name

Release

001186

UNSUCCESSFUL AMR CODEC SET DOWNGRADES

S10

Description Number of unsuccessful AMR codec set downgrades during internalHOs for the source side AMR codec set. Alignment between thesource side AMR codec set and the one chosen for the target sidehas failed and usage of one-way speech path downlink connectionfor the target side during the internal HO is not possible.

Updated By the Abis interface services after an unsuccessful mode modifyprocedure for BTS or MS.


Number

Name

Release

001187

SUCCESSFUL AMR CODEC SET UPGRADES

S10

Description Number of successful AMR codec set upgrades after internal HOs for the target side AMR codec set. Upgrade is made to utilize theoriginal AMR codec set of the target BTS which set was not chosenfor the target side because of target side alignment with the sourceside during internal HO. This alignment is made in order to utilize theone-way downlink speech path connection for the target side duringthe internal HO. The utilization of one-way speech path downlinkconnection decreases the amount of muting experienced in thespeech path connection. Upgrade decision after internal HO dependson the parameters AMR codec mode set downgrades and upgradesenabled and AMR multirate configuration in handovers.

Updated By the Abis interface services after successful mode modifyprocedures for BTS and MS.


Number

Name

Release

001188

UNSUCCESSFUL AMR CODEC SET UPGRADES

S10

Description Number of unsuccessful AMR codec set upgrades after internal HOsfor the target side AMR codec set. The target side continues to usethe currently used AMR codec set.

Updated By the Abis interface services after an unsuccessful mode modifyprocedure for BTS or MS.







Number

Name

Release

001189

TCH REQ FOR 96 DAT CALL

S10

Description Number of TCH requests for 9.6 kbit/s data call.

Updated When the Radio Resource Management receives a TCH request for a single slot 9.6kbit/s data connection in a call or a handover attempt.

Number

Name

Release

001190

SUCC TCH SEIZ FOR 96 DAT CALL

S10

Description Number of successful TCH seizures for 9.6 kbit/s data call.

Updated When the Radio Resource Management allocates a TCH/F as aresponse to a single slot 9.6kbit/s request in a call or handover attempt.

Number

Name

Release

Definition updated

001191

SPARE001191

S10.5 ED

S11Description Reserved for future use.

Number

Name

Release

Definition updated

001192

TCH REQUESTS FOR CALL ATTEMPT

S10.5 ED

S11, S12 (Name changed)

Description Number of TCH channel requests for a call.

Updated Updated when a TCH is requested for a call. The counter is updatedonly once for every call attempt, that is, it is not updated for TCH-TCHhandover attempts.

In segment environment, if the seizure of TCH is successful, thecounter is updated to the BTS from which the TCH was successfullyseizured. If the seizure is unsuccessful, the counter is updated to theBCCH BTS.

Trigger type Event

Logical type Cumulative

Unit Integer number







Number

Name

Release

001196

BSC O HO CMD

S11Description Number of all handover commands or assignment commands sent by

the BSC in an outgoing BSC-controlled handover (SDCCH-SDCCH,TCH-TCH or SDCCH-TCH HO).


Number

Name

Release

001197

BTS HO ASSGN


. Successful internal intra-cell handover

. Successful SDCCH internal intra-cell handover

Description Number of assignment commands sent in intra-BTS handovers(SDCCH-SDCCH, TCH-TCH or SDCCH-TCH).


Number

Name

Release

001198

TCH REL DUE TO RADIO FAIL PH 9-11

S11Description Number of TCH releases because of radio failures.

Updated This counter is updated in call phases 9-11 only (Outgoing handoversbefore CONNECT_ACK).


Number

Name

Release

001199

TCH REL DUE TO BSS FAIL PH 2-3

S11


CHANNEL_ACTIVATION_ACK message. TCH assignment failure, MSC sends CLEAR_COMMAND message

Description Number of TCH releases because of BSS failures.

Updated This counter is updated in call phases 2-3 only.






Number

Name

Release

001200

TCH REL DUE TO BSS FAIL PH 9-11

S11Description Number of TCH releases because of BSS failures. Same DX causes

as in counter 001140.

Updated This counter is updated in call phases 9-11 only (Outgoing handoversbefore CONNECT_ACK).


Number

Name

Release

001201

SDCCH FAIL PH 3

S11Description Number of all the failures on SDCCH in call phase 3 that do not

trigger any TCH failure counter in the same phase.


Number

Name

Release

001202

DROP AFTER TCH ASSIGN


.

CONNECTION_FAILURE message with cause transcoder_failureduring a call . Dropped call between ASSIGNMENT COMPLETE and

DISCONNECT

Description Number of dropped calls after the TCH is assigned.

Updated When the drop occurs between ASSIGNMENT_COMPLETE andDISCONNECT.


Number

Name

Release

001203

ERROR IND DURING LU

S11Description Number of Error indication messages received during the Location

Update procedure.







Number

Name

Release

001204

DROP TCH ASSCOMPL TO RFCH REL

S11.5Trigger points See figures:




Description Number of TCH drops between the Assignment Complete and the RFChannel Release Ack messages.

Updated When the TCH transaction ends in a phase between the AssignmentComplete and the RF Channel Release Ack messages.

Dependencies with other counters

Some of the counters 001013, 001014, 001029, 001030, 001046,001047, 001048, 001049, 001050, 001051, 001070, 001081, 001084,001085, 001087, 001088, and 001202 may be updated together withthis counter.

Number

Name

Release

001205

TCH REL DUE RAD FAIL PH 2-3

S11.5Trigger points See figure Timer T3107 expires while waiting for

ASSIGNMENT_COMPLETE messageDescription Number of the TCH releases because of the radio failures.

Updated When the TCH is released in call phase 2 (MM signalling) or 3 (Basicassignment) because of a radio failure.


Counter 001139 is updated together with this counter.

Number

Name

Release

001206

TCH REL DUE RAD FAIL PH 12-14

S11.5Description Number of the TCH releases because of radio failures.

Updated When the TCH is released during the Handover phases (12-14)because of a radio failure.







Number

Name

Release

001207

TCH REL DUE BSS FAIL PH 12-14

S11.5Description Number of the TCH releases because of the BSS failures.

Updated When the TCH is released during the Handover phases (12-14)because of a BSS failure.



Number

Name

Release

001208

A IF CRC MISMATCH CALL SETUP

S11.5Description Number of the TCH requests rejected because of the mismatch

between the types of the requested channel and the A interfacecircuit, updated in call setup phase only.

Updated When the RRM changes the A interface circuit pool before the TCHallocation.


Counter 001122 is updated together with this counter

Number

NameRelease

Definition updated

001209

GPRS TER DG REJ DUE STREAMINGS11.5

S12

Description This counter is not in use.

Updated This counter is not updated.

Number

Name

Release

Definition updated

001210

GPRS TER DG REQ WHEN EQOS ON

S11.5

S12

Description This counter is not in use.

Updated This counter is not updated.






Number

Name

Release

001211

TCH REL BSC BSC CONFLICT CALL

S11.5Description Number of TCH releases because of a BSC-BSC conflict.

Updated When a TCH is released (with cause bc_t_bsc_bsc_conflict_c in callphases 1-8 or 15)

Feature BSS11052: Dynamic Frequency and Channel Allocation

Number

Name

Release

001212

TCH REL BSC BSC CONFLICT TARG

S11.5

Description Number of TCH releases because of a BSC-BSC conflict.Updated When a TCH is released (with cause bc_t_bsc_bsc_conflict_c in call

phases 12-14)

Feature BSS11052: Dynamic Frequency and Channel Allocation

Number

Name

Release

001213

GPRS TER UG REQ FROM CSW

S11.5Description Number of territory upgrade requests to PCU init iated by the CSW.

Updated When the RRM initiates a PSW territory upgrade to the PCU.


001214 and 001215

Feature BSS1109672: Dynamic Abis Enhancement

Number

Name

Release

001214

GPRS TER UG FROM CSW PARTIAL

S11.5

Description Number of territory upgrade requests from the CSW RRM to the PCUthat have been served with less radio time slots than requested, i.e.partially successful PSW territory upgrade in the PCU.

Updated When the PCU upgrades the GPRS territory with less RTSLs than theRRM requested for.


001213






Number

Name

Release

001215

GPRS TER UG FROM CSW FAILED

S11.5Description Number of territory upgrade requests from the CSW RRM to the PCU

where the upgrade of the single new radio time slots to the PCU wasnot successful.

Updated When the PCU rejects the whole PSW territory upgrade, i.e. no singlenew RTSL was upgraded to the PCU.


001213


Number Name

Release

001216TCH REQ REJ DUE TO LACK OF RES PER BCSU

S11.5Description Number TCH requests rejected because of lack of capacity in one of

the BCSU units.

Updated When there is no BCSU capacity available for either call or HOattempt requests. This counter may be updated either immediatelyafter a TCH request or, in case of queuing, when the queuing timer expires.

When the TCH request is rejected in case of directed retry (DR), thiscounter is updated as follows:

1) When a call is removed from the queue due to a DR attempt, thiscounter is NOT updated on the SOURCE side. Instead, counter 001173 is updated.

2) If queuing is not used or the queuing timer expires before a DRattempt, this counter is updated on the SOURCE side.

3) On the TARGET side, this counter is updated in case of congestion(blocking).

Trigger type Event


001173

Feature BSS115173: Soft Channel CapacityLogical type Cumulative

Unit Integer number






Number

Name

Release

Definition updated

001217

INTERNAL TO EXTERNAL HO

S11.5

S12 (Name changed)

Description Number of internal handovers changed to external handovers.

Updated When an internal handover is aborted by changing it to an externalhandover.

Trigger type Event

Feature BSS20117: TCSM3i Support in BSC


Unit Integer number

Number

Name

Release

Definition updated

001218

NOT CHANGED INTERNAL HO

S11.5

S12 (Name changed)

Description Number of internal handovers that should be changed to externalhandovers, but for which the change is not allowed.

Updated When an internal handover should be changed to an externalhandover, but the change is not allowed due to too high A interfaceload.

Trigger type Event

Feature BSS20117: TCSM3i Support in BSC


Unit Integer number

Number

Name

Release

001219

SPARE001219

S11.5

Description Reserved for future use.





Number

Name

Release

001220

SPARE001220

S11.5Description Reserved for future use.

Number

Name

Release

001221

SPARE001221


Number Name

Release

001222SPARE001222


Number

Name

Release

001223

SPARE001223


Number

Name

Release

001224

SPARE001224


Number

NameRelease

001225

SPARE001225S11.5

Description Reserved for future use.






Number

Name

Release

001226

SPARE001226


Number

Name

Release

001227

SPARE001227


Number Name

Release

001228SPARE001228


Number

Name

Release

001229

SPARE001229


Number

Name

Release

001230

SPARE001230


Number

NameRelease

001231

SDCCH LU ATTEMPTSS12

Description Number of SDCCH location update requests.

Updated When a location update is received as SDCCHrequest type.

Trigger type Event

Dependencies with other counters Counter 001000 is updated before this counter.

Feature BSS20003: CS Statistics Enhancements







Number

Name

Release

001234

DTM CS TCH DROPS BETWEEN ASSCOMPLAND RFCH REL ACK

S12

Trigger points See figures:. DTM CS connection drops after ASSIGNMENT

COMPLETE; CONNECTION FAILURE received . DTM CS connection drops after ASSIGNMENT

COMPLETE; RELEASE INDICATION not received

Description Number of DTM CS TCHs dropped between ASSIGNMENT COMPLETE and RF CHANNELRELEASE ACK messages.

Updated When a CS TCH drop in the PS territory occursbetween ASSIGNMENT COMPLETE and RF

CHANNEL RELEASE ACK messages.This counter is updated in call phases 2, 3, 4, 9, 10,11 and 15 only.

Trigger type Event

Feature BSS20088: Dual Transfer Mode


Unit Integer number

Related topics


Signalling charts of Traffic Measurement

Signalling charts of Dual Transfer Mode



http://-/?-

http://-/?-



3 Signalling charts of Traffic MeasurementThe following figures show the signalling charts of Traffic Measurement:






Figure 1. Basic call without counters

Immediate assign command

BSC:MS: BTS: MSC:

PagingPaging commandPaging request

Radio access part on CCCH

Paging part

Channel request Channel requiredChannel activation

Channel activation ackImmediate assign

DDCH establishment partSabm Establish indication Paging response

Ciphering mode complete

SDCCH signalling part

SetupSetupCall proceeding Call proceeding

Assignment requestPhysical context requestPhysical context confirm

Channel activationChannel activation ack

Assignment command

TCH seized, FACCH signalling part

Ua

Sabm Establish indicationUa

Assignment complete Assignment completeRf channel release

Rf channel release ackAlert AlertConnect Connect

Connect ackConnect ack

Conversation phase

Release completeClear command

Clear completeChannel release

Deactivate SACCHDisc Ua Release indicationRf channel release

Rf channel release ack

Release by MSDisconnect Disconnect

ReleaseReleaseRelease complete

Authentification requestAuthentification requestAuthentification response Authentification response

Identification requestIdentification requestIdentification response Identification response

Ciphering mode commandEncryption commandCiphering mode commandCiphering mode complete





Figure 2. Basic call with counters

BTS: MSC:MS: BSC:

TCH succ req in norm assign 001009


Paging part

Channel request Channel required

Channel activation

Physical context confirm

Channel activation

Basic call signalling continuos, see figure 1

Basic call signalling, see figure 1

SDCCH seiz att for MOCor SDCCH seiz att for MTC

001135

001136

FR TCH succ seiz for norm assignor HR TCH succ seiz for norm assign

001114

001115

FR TCH succ seizor HR TCH succ seiz

001106

001107

SDCCH attempts 001000

SDCCH succ seiz for imm assign 001007

TCH requests 001010

TCH req for norm assign 001026

Ass req, que allowor Ass req, que not allow

001056

001057

001137

001138

TCH seiz att for MOCor TCH seiz att for MTC

001102

001103

001104

001105

FR TCH requestsor HR TCH requestsor FR pref TCH requestsor HR pref TCH requests






Figure 3. Basic call with priority subscriber

BTS: MSC:BSC:


TCH requests 001010


Channel activation



001054

001055

Ass req that can cause forced relor Ass req that can cause forced HO

001102001103

001104

001105


TCH req with prior subscriber 001095

001137

001138


001106

001107


001114

001115



Succ TCH req with prior subscriber 001096

MS:





Figure 4. FACCH call setup due to SDCCH congestion without counters

BSC:MS: MSC:BTS:

Mode modify request


Channel activation

Channel activation ack


Immediate assign

SetupSetupCall proceeding Call proceeding

Assignment request

Mode modify ack

Channel mode modification

Channel mode modification ackAssignment complete

Alert AlertConnect Connect


Channel mode modification

Channel mode modification ack

Conversation phase

Release by MS

DDCH establishment part

TCH, FACCH signalling part


Paging part






Figure 5. FACCH call setup due to SDCCH congestion with counters

BTS: MSC:MS: BSC:

Unsucc imm ass SDCCH attempt 001155


TCH request 001010

Succ TCH seiz due SDCCH cong 001099

001044

Att to seize TCH due SDCCH cong 001098

TCH req for FACCH call set-up 001043

Seiz att with busy SDCCH 001001


Paging part


Channel activation

FACCH call set-up signalling, see figure 4

Succ FR TCH seiz in FACCH callset-upor Succ HR TCH seiz in FACCH callset-up

001125

001126

001135

001136

SDCCH seiz att for MOCor

SDCCH seiz att for MTC

001123

001124

001137

001138

Succ TCH seiz in FACCH callset-up


FR TCH req for FACCH call set-upor TCH req for FACCH call set-up, chrt not def





Figure 6. FACCH call setup due to SDCCH congestion, no free TCH channel.Optional software directed retry is not activated

BSC:

Unsucc imm ass SDCCH attempt 001155

TCH request rejected due to cong 001141

Att to seize TCH due SDCCH cong 001098

TCH req for FACCH call set-up 001043

TCH requests 001010

Seiz att with busy SDCCH 001001


MS: MSC:BTS:

Immediate assignment reject

Channel required


Paging part

Channel request

No free TCH

001135

001136


001123

001124

FR TCH req for FACCH call set-upor TCH req for FACCH call, ch rate notdef

001137

001138

TCH seiz att for MOC

or TCH seiz att for MTC

001120

001121

FR TCH req rej due HR trafficor HR TCH req rej due FR traffic






Figure 7. Normal release


Paging part



Conversation phase

Release by MS

Disconnect DisconnectReleaseRelease

Release complete Release complete

Clear command

Channel release

Deactive sacch

DiscUa

Release indication

Rf channel rel

Rf channel rel ack

Clear complete


001108

001109

001110

001111

001112

001113

FR TCH speech FR ver 1or FR TCH speech FR ver 2or FR TCH speech FR ver 3or HR TCH speech HR ver 1or HR TCH speech HR ver 2or HR TCH speech HR ver 3

BSC:MS: MSC:BTS:





Figure 8. Basic call, no free TCH and queuing or directed retry is not allowed

BSC:

Ass req, queuing not allow 001057


TCH requests 001010

Rej ass req, que not allow 001061

TCH req rej due to lack 001011

TCH req rej due to cong 001141

MS: MSC:BTS:

Assignment failure

Rf channel releaseRf channel release ack

Clear command

Channel release

Deactive sacchDisc

UaRelease indication

Clear complete

Physical context confirmBasic call signalling, see figure 1

No free TCH and queueing or DR not allowed


001137

001138

001102

001103

001104

001105


001120

001121


FR TCH req rej due to lackor HR TCH req rej due to lack

001118

001119






Figure 9. Successful TCH queuing

BTS: MSC:MS: BSC:


Ave queue time of call attempt 001020


Ass req, queuing allowed 001056


TCH requests 001010

Call att set in queue for TCH 001016

Queuing indication

Rf channel release



TCH channel is released, request is taken from queue


Channel activation


001102

001103

001104

001105



001137

001138

001120

001121



001106

001107


001114

001115





Figure 10. Basic call, no free TCHs, unsuccessful queuing and directed retrynot activated

BSC:

001020

Call att in queue not served 001024


MS: MSC:BTS:

Assignment failure


Clear command

Channel releaseDeactive sacch

Disc

Ua Release indication

Clear complete

Physical context confirmBasic call signalling, see figure 1

No TCH released in time

001118

001119


Rej ass req, que allowed 001060



Queuing indication

001120

001121


No free TCH, call is set in queue

Ass req, queuing allowed 001056

TCH seiz att for MOC

or TCH seiz att for MTC

001137

001138

001102

001103

001104

001105


TCH requests 001010



Ave queue time of call attempt






Figure 11. TCH assignment failure with cause switch_circuit_pool , queuing anddirected retry not allowed

BTS: MSC:MS: BSC:

Ass req, que not allowed 001057

TCH requests 001010

Assignment failure

Clear command

Channel release

Deactive SACCH

Disc


Rf channel release



Clear complete



001104

001105

FR pref TCH requestsor HR pref TCH requests

001137001138



Rej ass req, que not allow 001061

001118

001119


TCH req rej due change crct pool 001122






Figure 12. Unsuccessful TCH activation

BTS: MSC:MS: BSC:

Assignment failure

Clear command

Channel release

Deactive SACCHDisc

Ua

Release indication

Clear complete


TCH activation fail 001028

SDCCH Rf channel rel

SDCCH Rf channel rel ack

Rf channel rel ack

Physical context request

Assignment request


Channel activation

Channel activation nack

Rf channel rel

Failure

TCH transact end due ch act fail 001081

001133001134

FR TCH transactions failor HR TCH transactions fail


001108

001109

001110

001111

001112

001113






Figure 13. Unsuccessful TCH activation, timer expires while waiting for CHANNEL_ACTIVATION_ACK message

MSC:BSC:BTS:MS:

TCH rel due BSS fail 001140

TCH transact end due BSS probl 001012

Start timer T9103

SDCCH Rf channel relSDCCH Rf channel rel ack

Rf channel rel ack

Assignment failureClear command

Channel release

Deactive SACCHDisc

Ua Release indication

Clear complete

Physical context requestAssignment request


Channel activation

Rf channel rel


TCH transact end due Abis fail 001045

TCH transact end due Abis fail 001084

001133001134


001108

001109

001110

001111

001112

001113


Timer T9103 expires

TCH rel due to BSS fail PH 2-3 001199







Figure 15. TCH assignment failure, MSC sends CLEAR_COMMAND message

MSC:BSC:BTS:MS:

SDCCH Rf channel rel

SDCCH Rf channel rel ack

TCH Rf channel rel ack

Radio access part on CCCHPaging part


Sabm

Disc


Ua

Channel release

Release indication

TCH Rf channel release

Establish indication Clear command

Clear complete

Deactive SACCH



TCH transact end due A int fail 001051


001108

001109

001110

001111

001112

001113

FR TCH speech FR ver 1or FR TCH speech FR ver 2or FR TCH speech FR ver 3or HR TCH speech HR ver 1or HR TCH speech HR ver 2or

HR TCH speech HR ver 3001133

00113


TCH rel due BSS fail 001140

TCH rel due to BSS fail PH 2-3 001199





Figure 16. CONNECTION_FAILURE message with cause transcoder_failure during a call

MSC:BSC:BTS:MS:

Failure

TCH transact end due transc fail 001029

Rf channel rel ack

Conversation phase

Clear request

Disc

Ua

Channel release

Release indication

Rf channel release

Connection failure

Clear command

Clear complete

Deactive SACCH

001108

001109

001110

001111

001112

001113


001127

001128

001129

001130

001131

001132

TCH transc fail FR speech ver 1or TCH transc fail FR speech ver 2or TCH transc fail FR speech ver 3or TCH transc fail HR speech ver 1or TCH transc fail HR speech ver 2or TCH transc fail HR speech ver 3

001133

001134


Drop after TCH assign 001202

Drop TCH asscompl to RFCH rel 001204






Figure 17. TRX or TSL is blocked with different causes during a call

MSC:BSC:BTS:MS:

TCH transact end due LAPD fail 001046

TCH Abis probl 001045


TRX / TSL is blocked

Clear complete

Rf channel rel ack

Conversation phase

Clear request

DiscUa

Channel release

Rf channel release

Clear command

Deactive SACCH

TCH transact end due BTS fail 001047

TCH transact end due USER act 001048

TCH transact end due NETW act 001050

TCH transact end due Abis int fail 001084

001133

001134

FR TCH transactions fail

or HR TCH transactions fail

001108

001109

001110

001111

001112

001113






Figure TRX or TSL is blocked with different causes during a call : Countersupdated with cause LAPD_failure: 001012 and 001046. Counters updated withcause BTS_failure: 001012 and 001047. Counter 001048 is updated with causeUSER_actions. Counter 001050 is updated with cause NETW_actions. Countersupdated with cause ABIS_failure: 001012, 001045 and 001084. Counter 001108,001109, 001110, 001111, 001112 or 001113 and counter 001133 or 001134 arealways updated with these causes.

Figure 18. SDCCH congestion, FACCH call setup is not activated

BSC:

Unsucc imm ass SDCCH att001155

SDCCH seiz att for MOC001135 or

SDCCH seiz att for MTC001136

SDCCH attempts001000

Seiz att with busy SDCCH001001

MS: MSC:BTS:


Channel required

Channel request

Paging part







Figure 19. Unsuccessful SDCCH activation

BSC:

SDCCH transact end due ch act fail001072

SDCCH activation failure001027

MS: MSC:BTS:

Failure

Channel request

Channel required

Channel activation


Rf channel release




Paging part





Figure 20. Unsuccessful SDCCH activation, timer expires while waiting for CHANNEL_ACTIVATION_ACK message

MSC:BSC:BTS:MS:

SDCCH transact end dueBSS fail

Start timer T9103

Channel request

Channel required

Channel activation

Paging part

Rf channel release




Timer T9103 expires

SDCCH transact end duefail in Abis int

SDCCH transact end due fail in Abis intduring a call

001002

001033

001075






Figure 21. Connection failure during SDCCH assignment

BTS:

Failure

MSC:MS: BSC:

SDCCH transact ended due radio fail001003


Channel activation



Immediate assign

Connection failure

Channel release

Deactive SACCHDisc


Rf channel release



Paging part








Figure 23. Unsuccessful SDCCH activation, timer expires while waiting for PHYSICAL_CONTEXT_CONFIRM message

MSC:BSC:BTS:MS:



SDCCH transact end due fail in Abis intduring a call

001002

001033

001075

Timer T9108 expires

Start timer T9108

Assignment request


Assignment failure


Clear command

Rf channel release


Channel release

Deactive SACCHDisc


Clear complete





Figure 24. TRX/TSL is blocked with different causes during an SDCCH channelactivation

Figure TRX/TSL is blocked with different causes during an SDCCH channel activation : Counters updated with cause LAPD_failure : 001002 and 001035.Counters updated with cause BTS_failure : 001002 and 001036. Counter 001037is updated with cause USER_actions . Counter 001039 is updated with causeNETW_actions . Counters updated with cause ABIS_failure : 001002, 001033 and001075.

MSC:BSC:BTS:MS:



001002

001033

TRX / TSL is blocked

Channel requestChannel required

Channel activation

Paging part

Rf channel release



SDCCH transaction end dueLAPD fail 001035

SDCCH transact ended dueBTS fail 001036

SDCCH transact end dueuser actions 001037

SDCCH transact end duenetw act fail 001039

SDCCH transact end due fail in Abis intduring a call 001075







Figure 25. Successful trunk reservation. Counters updated: 001040, 001041and basic call counters, see Figure 2.

BSC:

Succ trunk reservations001041

Trunk reservations001040

MS: MSC:BTS:


Assignment request


Channel activation


Assignment command







Figure 26. Unsuccessful trunk reservation

MSC:BSC:BTS:MS:


TCH requests 001010

Trunk reservations 001040

Assignment failure



Clear command

Channel releaseDeactive sacchDisc


Clear complete


001056

001057

Ass req, que allowor Ass req, que not allow

001102

001103

001104

001105

FR TCH requestsor HR TCH requests

or FR pref TCH requestsor HR pref TCH requests

001137

001138


Unsuccessful trunk reservation

Refus TCH req of non-prior subsc 001097

Refused trunk reservations 001042

001100

001101

FR TCH req for trunk reserv rejor HR TCH req for trunk reserv rej

001060

001061

Rej ass req, queueing allowedor Rej ass req, queueing not allowed

001120

001121







Figure 27. Successful internal intra-cell handover. Counters 001090 and001091 are updated only with underlay overlay handover.

MSC:BSC:BTS:MS:

TCH requests 001010

Meas report Meas resultPhysical context request


HO measurement, Old TCH channel


Assignment command

Assignment command


Rr HO performed


Assignment complete Assignment complete

001137

001138


001064

001065

Att to req HO, que allowedor Att to req HO, que not allowed

001102 or 001103 or 001104 or 001105

FR TCH requestsHR TCH requestsFR pref TCH requestsHR pref TCH requests

TCH req for underlay/overlay HO 001090

Succ TCH req for HO 001008

TCH seiz for underlay/overlay HO 001091

001106 or 001107

FR TCH succ seizHR TCH succ seiz

Succ seiz of FR TCH in int HOwith ch rate changesor Succ seiz of HR TCH in int HO

with ch rate changes

001116

001117

Old TCH channel release

Signalling on new TCH channel

Signalling on old TCH channel

New TCH channel reservation and activation

BTS HO assgn 001197





Figure 28. Internal intra-cell HO, successful TCH queuing

MSC:BSC:BTS:MS:

TCH requests 001010



Channel activation


001102 or 001103 or

001104 or 001105

FR TCH requestsHR TCH requests

FR pref TCH requestsHR pref TCH requests


001106 or 001107




Att to req HO, que allowed 001064

No free TCH, request is set in queue

001120

001121


TCH channel is released, request is taken from queue

HO signalling, see figure 27

001137 or 001138

TCH seiz att for MOCTCH seiz att for MTC

HO att set in queue for TCH 001017

Queued urgent HO attempt 001142

001023

001022

Queue denominator 3

Ave queue time of ho attempt

001143

001145

Ave queue time of urgent ho attor Ave queue time of non urgent ho att

Queue denominator 4Queue denominator 4

001144 or 001146


TCH seiz for underlay/overlay HO 001091

Succ FR TCH int HO with ch rt chor

Succ HR TCH int HO with ch rt ch

001116

001117








Figure 29. Unsuccessful internal intra-cell handover, timer expires while waitingfor CHANNEL_ACTIVATION_ACK message

MSC:BSC:BTS:MS:


Start timer T9103

Timer T9103 expires

Meas report Meas result

Physical context requestPhysical context confirm

Channel activation

Call going on the TCH channel

Rf channel release


HO measurement, HO decision


Normal HO counters updated, see figure 27

TCH Abis probl 001045

TCH transact end due Abis int failon new channel

001108

001109

001110

001111

001112

001113



001133

001134

Call continuous on the old TCH channel

001086






Figure 30. Unsuccessful internal intra-cell handover, CONNECTION_FAILUREmessage with cause remote_transcoder_failure comes to the targetchannel

MSC:BSC:BTS:MS:



Channel activation

Call going on the TCH channelHO measurement, HO decision


TCH transact end due transcfail on target

FR TCH transactions failor

HR TCH transactions fail

001133

001134

001031


Call continuous on the old TCH channel

Signalling on FACCH TCH (old channel)Assignment command

Connection failure

Assignment command


HO failure HO failure

Signalling on FACCH TCH (new channel), channel release

001108

001109

001110

001111

001112

001113


001127

001128

001129

001130

001131

001132

TCH transc fail FR speech ver 1or TCH transc fail FR speech ver 2or TCH transc fail FR speech ver 3or TCH transc fail HR speech ver 1or TCH transc fail HR speech ver 2or TCH transc fail HR speech ver 3





Figure 31. Unsuccessful internal intra-cell handover, timer expires on thesource channel, call cleared

MSC:BSC:BTS:MS:



FR TCH transactions failHR TCH transactions fail

001133 or 001134

Start timer T3107



Assignment commandAssignment command



Clear requestClear command


Clear complete




Signalling on new TCH channel


Timer T3107 expires

New channel release

001108 or 001109 or 001110 or 001111 or 001112 or 001113

FR TCH speech FR ver 1FR TCH speech FR ver 2FR TCH speech FR ver 3HR TCH speech HR ver 1HR TCH speech HR ver 2HR TCH speech HR ver 3

001133 or 001134

FR TCH transactions failHR TCH transactions fail

Old TCH channel release

TCH transact end due fail on source 001014001108 or 001109 or 001110 or 001111 or 001112 or 001113







Figure 32. Unsuccessful underlay overlay internal intra-cell handover, queuingnot allowed

BSC: MSC:BTS:MS:




Call continuous on old channel


No free TCH, queueing not allowed

TCH requests 001010

001137

001138


001102

001103

001104

001105


Att to req HO, que not allowed 001065



001118

001119


001120

001121


HO req fail, queueing not allowed 001069

TCH req for underlay/overlay HOrej due lack 001092





Figure 33. Internal intra-cell handover, unsuccessful TCH queuing

MSC:BSC:BTS:MS:

TCH requests 001010



001102 or

001103 or 001104 or 001105

FR TCH requests

HR TCH requestsFR pref TCH requestsHR pref TCH requests



No free TCH, request is set in queue

001120

001121


001137 or 001138


HO att set in queue for TCH 001017

Queued urgent HO attempt 001142

Queue denominator 3 001023Ave queue time of ho attempt 001022

Att to req HO, queueing allowed 001064

Call continous on old TCH channel

No suitable TCH released in time


HO att in queue not served 001025

HO req rej , queueing allowed 001068

001144 or 001146

Queue denominator 4Queue denominator 5

Queued urgent HO att not served 001147

001143

001145

Ave queue time of urgent ho attor

Ave queue time of non urgent ho att

001118 or 001119

FR TCH req rej due to lackHR TCH req rej due to lack






Figure Internal intra-cell handover, unsuccessful TCH queuing : Counters 001142,001143, 001144 and 001147 are updated only if the handover is started by causeurgent_handover . Counters 001145 and 001146 are updated only if the handover is started by cause non_urgent_handover .





Figure 34. Internal directed retry

MSC:BSC:BTS:MS:

TCH requests 001010


001102 or 001103 or 001104 or 001105


Ass req, queueing allowed 001065


Assignment request

Sabm Establish indication


Channel activation


HO command

HO command

HO access HO detectionPhysical info

Ua

Rr Assignment complete


HO complete HO complete

Cell is congested, no TCH

Queueing indication

TCH reservation and activation in new BTS

Basic call signalling continuous, see figure 1

Queueing possible and started

TCH request for norm assign 001026


001137 or 001138



SDCCH release in old BTS

Signalling on FACCH - TCH in new BTS

Signalling on SDCCH in old BTS

DR HO beginsRemoval from queue due to DR 001173

Ave queue time of call attempt 001020


BTS O HO cmd 001196








Figure Successful internal inter-cell handover : Counters 001090 and 001091 areupdated only with underlay overlay handover.

Figure 36. Unsuccessful internal inter-cell handover

MSC:BSC:BTS:MS:


TCH activation fail 001028


Channel activation


New TCH channel reservation and activation in new BTS

Call continuous on the old channel



New channel release

TCH transact end due TCH actfail in target

001108

001109

001110

001111

001112

001113


001133

001134


001083






Figure 37. Successful external handover, target

MSC:BSC:BTS:MS:

TCH requests 001010

HO request

Channel activation


HO request ack

HO access HO detection HO detection

Physical info


UaHO complete

Rr

HO complete HO completed

001064

001065

Att to req HO, que allowedor Att to req HO, que not allowed

001102

001103

001104

001105



001106

001107






Figure 38. Successful external handover, source

BTS: MSC:MS: BSC:

FR TCH speech FR ver 1001108 or



HR TCH speech HR ver 1001111 or

HR TCH speech HR ver 2001112 or

HR TCH speech HR ver 3001113

HO command

Rf channel release


HO requiredMeas report Meas result

Clear complete

HO command

HO command

Clear command

MSC O HO cmd 001195








Figure 40. Unsuccessful external handover, MS sends a handover failure

MSC:BSC:BTS:MS:

Meas report Meas result HO requiredHO request


Channel activation




HO request ack

Clear command

Rf channel release


HO failure HO failure HO failure

Clear complete

HO commandHO commandHO command

New TCH channel reservation and activation in new BSC


Signalling on old BSC, MS sends HO failure

Signalling on new BSC, channel is released



TCH transact end due A int fail on

new001108

001109

001110

001111

001112

001113


001133

001134


001089






Figure 41. Successful traffic reason handover, source

MSC:BSC:BTS:MS:

HO s due to traffic reasons 001052

Rf resource indicationResource request

Resource indication

HO candidate enquiry

HO required

HO candidate responseHO commandHO commandHO command

Enquiries of traffic reason HO 001053







Figure 43. Unsuccessful SDCCH internal intra-cell handover, timer expireswhile waiting for CHANNEL_ACTIVATION_ACK message

MSC:BSC:BTS:MS:

Timer T9103 expires

Start timer T9103




Channel activation

HO measurement, old SDCCH channel

Rf channel release


New SDCCH channel reservation and activation

SDCCH transact end due BSSprobl

Signalling continuous on old SDCCH channel

SDCCH transact end due Abisint fail

SDCCH transact end due Abis int failon target

001002

001033

001077





Figure 44. Unsuccessful SDCCH internal intra-cell handover, unsuccessfulchannel activation

BSC:

SDCCH transact end duech act fail on target

001074

SDCCH transact end duech act fail

001027

MS: MSC:BTS:




Channel activation

Rf channel release



HO measurement, old SDCCH channel


Signalling continuous on old SDCCH channel






Figure 45. Unsuccessful SDCCH internal intra-cell handover,CONNECTION_FAILURE message comes to the target channelduring handover

MSC:BSC:BTS:MS:




HO measurement, Old SDCCH channel

Channel activation


Assignment commandAssignment command


UaConnection failure

Signalling continuous on old channel

Rf channel release



Signalling on old SDCCH channel

Signalling on new SDCCH channel

SDCCH transact end dueradio fail on target 001005





Figure 46. Successful SDCCH internal inter-cell handover

MSC:BSC:BTS:MS:


Succ SDCCH seiz for HO 001006



HO measurement, Old SDCCH channel in old BTS

Channel activation


New SDCCH channel reserv. and activ. in new BTS

Signalling on the old SDCCH channel in the old BTS

HO command

HO command

Signalling on new SDCCH channel in new BTS

HO access HO detection

Physical info

Ua

Rr HO performed

Old SDCCH channel release in the old BTS

Rf channel release



001135

001136


BTS O HO cmd 001196










Figure 50. Unsuccessful SDCCH external handover, timer expires while waitingfor CLEAR_COMMAND message

MSC:BSC:BTS:MS:

SDCCH transact end due A int fail 001034

SDCCH transact end due BSS fail 001002

Timer T8 expires

Start timer T8

HO command

Rf channel release


HO requiredMeas report Meas result

Clear complete

HO commandHO command

Clear command

Clear request

Signalling on SDCCH source channel

Rf channel release ackRf channel release

Clear command

Clear complete

SDCCH transact end due A int failon source

Signalling on SDCCH target channel

SDCCH transact end due BSS fail 001002

SDCCH transact end due A int fail 001034

SDCCH transact end due A int failon target

001079

001080





Figure 51. Successful forced release

MSC:BSC:BTS:MS:

TCH requests 001010

Call going on TCH channel

Clear requestClear command

Channel releaseDeactive SACCHDisc

Ua Release indicationRf channel release


Clear complete

Channel activation


Queueing indication

New call coming with priority subscriber


TCH req for norm assign 001026Ass req that can cause forced rel 001054

001102 or 001103 or 001104 or 001105

FR TCH requestsHR TCH requestsFR pref TCH requestsHR pref TCH requestsTCH seiz att for MOCTCH seiz att for MTC

001137 or 001138

001120 or 001121

FR TCH req rej due HR trafficHR TCH req rej due FR traffic

No free TCH channel, call with lower priority is released

Released TCH channel is allocated for the priority call

Forced release 001070


001106 or 001107


Signalling continuous like basic call, see figure 1

001114

001115


001108 or 001109 or 001110 or 001111 or 001112 or 001113







Figure 52. Unsuccessful forced release

MSC:BSC:BTS:MS:

TCH requests 001010

Clear command

Channel release

Deactive SACCHDisc



Clear complete


Queueing indication




Ass req that can cause forced rel 001054

001102 or 001103 or 001104 or

001105



001137 or 001138

001120 or 001121

FR TCH req rej due HR trafficHR TCH req rej due FR traffic

No free TCH channel

Assignment failure

No suitable TCH for release, forced release timer expires


FR TCH req rej due to lackHR TCH req rej due to lack

001118 or 001119

Forced rel req rej 001058

TCH req rej due to lack 001011TCH req rej due to cong 001141





Figure 53. Unsuccessful forced release with external handover

MSC:BSC:BTS:MS:

TCH requests 001010

Meas report Meas result HO requiredHO request

Queuing indication

Priority call going on the TCH channel

Clear command

Rf channel release


HO failure

Clear complete


New TCH channel reservation and activation in new BSC

Att to req HO with forced rel 001062


001102

001103

001104

001105


001120

001121


No suitable TCH for forced release, forced release timer exp ires

001119FR TCH req rej due to lackor HR TCH req rej due to lack


HO req rej with forced release 001066


001118






Figure 54. Successful forced handover

MSC:BSC:BTS:MS:


TCH requests 001010

Ass req that can cause forced HO 001055



Channel activation


No free TCH channel, call with lower priority is forced HO

Queueing indication

001102

001103

001104

001105

FR TCH requestsor HR TCH requestsor


001137

001138


001120

001121


Normal internal inter cell HO, see figure 35

Released TCH channel is allocated for the priority call


Forced HO 001071

001106

001107

FR TCH succ seizor

HR TCH succ seiz

001114

001115


Signalling continuous like basic call, see figure 1





Figure 55. Unsuccessful forced handover

MSC:BSC:BTS:MS:


TCH requests 001010

New call coming with

Calls going on the TCH channel

Clear complete

Forced handover timer expires


No free TCH channel,


Channel releaseDeactive SACCHDisc

Ua Release indicationRf channel release


Queueing indication


Ass req that can cause forced HO 001055


001102

001103

001104001105

FR TCH requestsor HR TCH requestsor


001137

001138


001120

001121


001118

001119



Forced HO req rejected 001059

no suitable calls for forced HO

priority subscriber






Figure 56. Unsuccessful forced handover with external handover

MSC:BSC:BTS:MS:



TCH requests 001010

Att to req HO with forced HO 001063

HO req rej with forced HO 001067

Meas report Meas result HO required

HO request


Queuing indication

New TCH channel reservation

No suitable TCH for forced handover,

Priority call going on the TCH channel


Clear command

Rf channel release


HO failure

Clear complete

001102

001103

001104

001105


001120

001121


001118

001119


forced handover timer expires

and activation in new BSC





Figure 57. Reconfiguration from TCH to SDCCH

MSC:BSC:BTS:MS:

SDCCH attempt 001000

Channel requestChannel required

Channel activation

Paging part


001135

001136


Reconfiguration from idle TCH to active SDCCH

Dynamic SDCCH reconf attempt 001154

SDCCH succ seiz for imm assign 001007







Figure 58. Normal call

MSC:BSC:BTS:MS:

Succ TCH seiz for ass complete 001148




Assignment complete

Assignment complete

Sabm

Ua

Establish indication







Figure 60. Successful internal inter-cell handover for HSCSD, target cellallocations and activations for three channels

MSC:BSC:BTS:MS:

HSCSD TCH request for HO 001161

HSCSD transp TCH request 001158

HSCSD TCH request with 14,4 001156



HO measurement, Old TCH channel in the old BTS

Channel activation


Signalling on the old TCH channel in the old BTS

HO commandHO command

HO access HO detection

Physical info

Ua

Rr HO performed

Rf channel release



Channel activation


Channel activation


New TCH channel reservation and activation in the new BTS

Normal handover counters are updated, see figure 35

HSCSD succ TCH seiz with 14,4 001157

HSCSD succ transp TCH seiz 001159

HSCSD succ TCH seiz for HO 001163

Signalling on the new TCH channel in the new BTS

Old TCH channel release in the old BTS





Figure 61. A CONNECTION_FAILURE message which comes during an

HSCSD

MSC:BSC:BTS:MS:

Failure

HSCSD conn rel due to fail 001164

Rf channel rel ack

Conversation phase

Clear request

Disc

Ua

Channel release

Release indicationRf channel release

Connection failure

Clear commandClear complete

Deactive SACCH






Figure 62. Internal intra-cell direct access from a regular DCCH to the super-reuse TRX. Optional software direct access to super-reuse TRX inIUO activated.

MSC:BSC:BTS:MS:

Succ TCH seiz for dir acc 1165

Assignment request




Channel activation



Assignment command

Assignment command

Ua

Rr

Assignment complete

Rf channel release


Assignment complete Assignment complete

Alert Alert


Connect Connect

Physical context information

Direct access to super-reuse TRX

TCH reservation and activation

Signalling on SDCCH

Signalling on FACCH - TCH

SDCCH release

Connection

Conversation phase





Figure 63. Unsuccessful internal intra-cell direct access from regular DCCH tothe super-reuse TRX due to lack of resources. Optional softwaredirect access to super-reuse TRX in IUO activated.

MSC:BSC:BTS:MS:

TCH req for dir acc rej due lack 1166

Assignment request




Physical context information

Unsuccessful direct access attempt to super-reuse TRX

Signalling continuous on old channel






Figure 64. Timer T3107 expires while waiting for ASSIGNMENT_COMPLETEmessage

MSC:BSC:BTS:MS:

TCH transact end due radio fail 001013

Timer T3107 expires

Start timer T3107

SDCCH Rf channel relSDCCH Rf channel rel ack

Rf channel rel ack


Channel release

Deactive SACCHDisc


Clear complete

Physical context request Assignment request


Channel activation

Rf channel rel


Channel activation ackAssignment command

Assignment commandSabm

Establish indicationUa

001108

001109

001110

001111

001112

001113


001133001134


TCH rel due radio fail 001139

TCH rel due rad fail PH 2-3 001205





Figure 65. Average counter updating

MSC:BSC:BTS:MS:

Timer is started

After 20 seconds

Timer expires

Timer is started again

After 20 seconds

Timer expiresAverage queue length for channelseizure request

Average queue length for channelseizure request

1018

1018






Figure 66. Successful handover due to DADL/B

Figure 67. Unsuccessful DADL/B handover due to lack of resources

BTS: MSC:MS: BSC:

Succ TCH seiz for DADL/B HO001170

DADL/B start due to exceeded load001172


Assignment request



Signalling

Signalling continues

BTS: MSC:MS: BSC:

TCH request in DADL/B HO rejected001171

DADL/B start due to exceeded load001172

Assignment request



Signalling

DR and queuing possible







Figure 70. Dropped call between ASSIGNMENT COMPLETE andDISCONNECT

MSC:BSC:BTS:MS:

Paging/initial MS on CCCH

Clear request

Channel release

Clear command

Clear complete

Deactive SACCH

MM signalling

Basic assignment

AlertAlert

ConnectConnect

Connect ack Connect ack

Conversation

Radio Link Failure

Connection failure

DISC

UA

Release indication

RF channel release

001108FR TCH speech FR ver 1or FR TCH speech FR ver 2or FR TCH speech FR ver 3or HR TCH speech HR ver 1or HR TCH speech HR ver 2or HR TCH speech HR ver 3

001109

001110

001111

001112

001113

TCH transact end due radio fail

001012

TCH Abis problDrop after TCH assign

Drop TCH asscompl to RFCH rel

001013

TCH transact end due BSS probl

001045001202

001204

RF channel release ack







Related topics







4 Signalling charts of Dual Transfer ModeThe following figures show the signalling charts of Dual Transfer Mode:






Figure 72. MO DTM call establishment

MS BTS BSC MSC

MEASUREMENT REPORT

CHANNEL ACTIVATION

CHANNEL ACTIVATION ACK

SABMESTABLISH INDICATIONUA

ASSIGNMENT COMPLETE

RR

HANDOVER PERFORMED

RF CHANNEL RELEASE

RF CHANNEL RELEASE ACK

106000 MO_DTM_CALL_REQUESTS_INI

DTM REQUEST

MEASUREMENT RESULT

PHYSICAL CONTEXT REQUEST

PHYSICAL CONTEXT CONFIRM

DTM ASSIGNMENT COMMAND

105016 DTM_REQ_1_UL_PS_TSL or 105017 DTM_REQ_2_UL_PS_TSL

105009 DTM_ALLOCATIONS_INITIAL

105015 PEAK_DTM_CS_SIMULTAN

105021 DTM_ALLOC_1_UL_PS_TSL or 105022 DTM_ALLOC_2_UL_PS_TSL

Start T3107

051189 INTRA_DTM_MO_CS_TO_PS

106018 DTM_ASSIGN_COMMANDS

071038 REPORTING_TIME_BY_DTM_MS

071037 TCH_RESERV_BY_DTM_MS

MS in dedicated mode

PS data transfer in dual transfer mode

Stop T3107





Figure 73. MT DTM call establishment

MS BTS BSC MSC

SABM

UA

RR

105000 MT_DTM_CALL_REQUESTS_INI

SGSN

LLC PDU

MEASUREMENTREPORT MEASUREMENT RESULT



ASSIGNMENT COMPLETE

HANDOVER PERFORMED



CHANNEL ACTIVATION

RF CHANNEL RELEASE


ESTABLISH INDICATION


105023 DTM_ALLOC_1_DL_PS_TSL or 105024 DTM_ALLOC_2_DL_PS_TSL


051190 INTRA_DTM_MT_CS_TO_PS



105018 DTM_REQ_1_DL_PS_TSL or 105019 DTM_REQ_2_DL_PS_TSL


PS data transfer in dual transfer mode






Figure 74. DTM call reallocation; too high CS connection interference

MS BTS BSC MSC

MEASUREMENT REPORT

CHANNEL ACTIVATION



SABM


UA

ASSIGNMENT COMPLETE

RRHANDOVER PERFORMED

RF CHANNEL RELEASE



MEASUREMENT RESULT

CS connection controldetects too high CSconnection interference





106006 DTM_REALLO_CS_REQUESTS

MS has a DTM allocation with one UL PS TSL allocation

DTM call continues on the new resources

105010 DTM_REALLOCATIONS

105016 DTM_REQ_1_UL_PS_TSL or 105017 DTM_REQ_2_UL_PS_TSL

105021 DTM_ALLOC_1_UL_PS_TSL or 105022 DTM_ALLOC_2_UL_PS_TSL





Figure 75. DTM call reallocation; inadequate PS connection quality

MS BTS BSC MSC

CHANNEL ACTIVATION


SABMESTABLISH INDICATION

UA

ASSIGNMENT COMPLETE

RR

HANDOVER PERFORMED

RF CHANNEL RELEASE


MEASUREMENT REPORT


PS quality control detectsinadequate quality

MEASUREMENT RESULT





051191 INTRA_DTM_MT_PS_TO_PS


105010 DTM_REALLOCATIONS

105005 DTM_REALLO_REQ_PS_QUAL

MS has a DTM allocation with one UL PS TSL allocation

DTM call continues on the new resources

105018 DTM_REQ_1_DL_PS_TSL or 105019 DTM_REQ_2_DL_PS_TSL







Figure 76. DTM call; internal inter-cell handover; CS connection power budget

BTS1 BTS2 BSC MSC

CHANNEL ACTIVATION

HANDOVER ACCESS

MS

PHYSICAL INFO

SABM

UA

RR

DTM INFORMATION

MS has a DTM allocation



MEASUREMENT REPORTMEASUREMENT RESULT

CS connection control startsa power budget handover

HANDOVER COMMAND

HANDOVER DETECTION


HANDOVER COMPLETEHANDOVER PERFORMED

RF CHANNEL RELEASE

CS connection continues in the CS territory of the target ce ll.The DTM call is then re-established in the target cell.

105011 DTM_DURATION_SUM_FR

004199 DTM_CALL_HO_SUCC_TO_DTM_CELL

072202 DL_TBF_RELEASES_DUE_DTM

072201 UL_TBF_RELEASES_DUE_DTM

004198 DTM_CALL_HO_ATT_TO_DTM_CELL

106013 DTM_RELEASES_DUE_CS_HO



HANDOVER COMPLETE

004194 DTM_CALL_HO_FROM_DTM_CELL





Figure 77. DTM call; internal inter-cell handover; lack of resources in the PSterritory

BTS1 BTS2 BSC MSC

HANDOVER ACCESS

MS

PHYSICAL INFO

SABM

UA

RR

DTM INFORMATION



HANDOVER PERFORMED

CHANNEL ACTIVATION

HANDOVER COMMAND

HANDOVER DETECTION


HANDOVER COMPLETE

HANDOVER COMPLETE

RF CHANNEL RELEASE

004194 DTM_CALL_HO_FROM_DTM_CELL



004195DTM_HO_DUE_LACK_OF_RESOURCES







No free resources in the PS territory







Figure 78. DTM call; external handover, source BSC

MS BTS BSC MSC

RF CHANNEL RELEASE


MEASUREMENT RESULT

MEASUREMENT REPORT

HANDOVER REQUIRED

HANDOVER COMMAND

CLEAR COMMAND

CLEAR COMPLETE









MS has a DTM allocation

Channel reservation and activation in the target BSC

HO signalling in the target BSC






Figure 79. DTM call; external handover, target BSC

MS BTS BSC MSC

CHANNEL ACTIVATION


HANDOVER ACCESS

HANDOVER DETECTION

PHYSICAL INFO

SABM


UA

HANDOVER COMPLETE

RR

DTM INFORMATION

HANDOVER REQUEST

HANDOVER REQUESTACKNOWLEDGE

External handover decision in the source BSC

HO signalling in the source BSC, the MSC sends a HO command

Old resources released in the source BSC

The DTM call is then re-established in the target cell.CS connection continues in the CS territory of the target ce ll.








Figure 81. DTM call release; packet data transfer end

MS BTS BSC MSC

SABM

UA

106011 DTM_RELEASES_DUE_PS_RELEASE

SGSN

Last LLC PDU

RR

DL Data Frame (final block), polling

UNACK MODE: Packet Control Ack

ASSIGNMENT COMMAND


ASSIGNMENT COMPLETE

HANDOVER PERFORMED


ACK MODE: (EGPRS) Packet DL Ack /Nack (final ack)



CHANNEL ACTIVATION


RF CHANNEL RELEASE

051192 INTRA_DTM_PS_TO_CS




CS connection continues in the CS territory

MS has a DTM allocation with ongoing UL and/or DL TBFs

RR






Figure 82. DTM REQUEST rejected when IMSI data not available

MS BTS BSC MSCCHANNEL REQUEST

CHANNEL ACTIVATIONCHANNEL ACTIVATION ACK

IMMEDIATE ASSIGNMENT


UA

CLASSMARK CHANGE

CHANNEL ACTIVATION


ASSIGNMENT COMMAND


UA

ASSIGNMENT COMPLETE

DTM REQUEST

RF CHANNEL RELEASE


CONNECT ACKCONNECT

DTM REJECT

106002 MO_DTM_CALL_REJECTS_INI

GPRS INFORMATION

SETUP

CALL PROCEEDING

ALERT

RR

SGSN

LLC PDU

CM SERVICE REQUESTCLASSMARK UPDATE

COMMON ID (not received)

106000 MO_DTM_CALL_REQUESTS_INI

106017 DTM_IMSI_NOT_ AVAILABLE



Authentication, identity request and ciphering

MS continues in dedicated mode.

ASSIGNMENT REQUEST







Figure 84. Unsuccessful MT DTM; activation of a CS TCH in the PS territoryfails, timer expires while waiting for CHANNEL ACTIVATION ACK

SGSNMS BTS BSC

MEASUREMENT REPORT

CHANNEL ACTIVATION

Start T9103

T9103 expires

RF CHANNEL RELEASE


105000 MT_DTM_CALL_REQUESTS_INI

DL LLC PDU

MEASUREMENT RESULT


CHANNEL ACTIVATION ACK (not received)

105015 PEAK_DTM_CS_SIMULTAN


105019 DTM_REQ_2_DL_PS_TSL105018 DTM_REQ_1_DL_PS_TSL or


105002 MT_DTM_CALL_REJECTS_INI




CS call continues on the old TCH channel





Figure 85. Unsuccessful MT DTM; DTM ASSIGNMENT FAILURE received

MS BTS BSC

SABM


UA

DTM ASSIGNMENT FAILURE

RF CHANNEL RELEASE


RR



106008 DTM_ASSIGN_FAILURES_INI


CS call continues on the old TCH channel

MT DTM call establishment started; see MT DTM scenario until DTM ASSIGNMENT COMMANDin figure MT DTM call establishment







Figure 86. Timer T3107 expires while waiting for ASSIGNMENT COMPLETE

MS BTS BSC MSC


RF CHANNEL RELEASE


RF CHANNEL RELEASE


106010 MS_LOST_DURING_ASSIGNMENT

CLEAR REQUEST

CLEAR COMMAND

CLEAR COMPLETE


UAASSIGNMENT COMPLETE (not received)

T3107 expires




Release of the new TCH channel

Release of the old TCH channel

see MT DTM scenario until DTM ASSIGNMENTCOMMAND in figure MT DTM call establishment

Start T3107

CHANNEL RELEASE

DEACTIVATE SACCH

RELEASE INDICATION


072201 UL_TBF_RELEASES_DUE_DTM or 072202 DL_TBF_RELEASES_DUE_DTM

MO or MT DTM call establishment started;







Figure 88. DTM CS connection drops after ASSIGNMENT COMPLETE;CONNECTION FAILURE received

MS BTS BSC MSC

HANDOVER PERFORMED

DISC

CLEAR COMMAND

CHANNEL RELEASE

DEACTIVATE SACCH

UA


RF CHANNEL RELEASE

RELEASE INDICATION

CLEAR COMPLETE

CONNECTION FAILURECLEAR REQUEST

001234 DROP_DTM_TCH_ASCMPL_RFCH_REL

Radio Link Failure detected

ASSIGNMENT COMPLETE

MS has a DTM allocation with ongoing UL and/or DL TBFs; for example, see figureMO DTM call establishment

001233 DROP_AFTER_DTM_TCH_ASSIGN



105011 DTM_DURATION_SUM_HR

072202 DL_TBF_RELEASES_DUE_DTM072201 UL_TBF_RELEASES_DUE_DTM or


RF CHANNEL RELEASE

106014 DTM_RELEASES_DUE_OTHER

051189 INTRA_DTM_MO_CS_TO_PS







Figure 89. DTM CS connection drops after ASSIGNMENT COMPLETE;RELEASE INDICATION not received

Related topics

. 1 Traffic Measurement

. Counters of Traffic Measurement

MS BTS BSC MSC

RELEASE

RELEASE COMPLETE

CLEAR COMMAND

CHANNEL RELEASE

DEACTIVATE SACCH SCCP RELEASE COMPLETE

SCCP RELEASE

DISCONNECT


RF CHANNEL RELEASE

001234 DROP_DTM_TCH_ASCMPL_RFCH_REL

DISC (not received)

RELEASE INDICATION (not received)

T3109 expires

Start T3109

MS has a DTM allocation with ongoing UL and/or DL TBFs; for example, see figureMO DTM call establishment




CLEAR COMPLETE

106012 DTM_RELEASES_DUE_CS_RELEASE








. 4 Handover Measurement

. Counters of Handover Measurement

. 51 BSC Level Clear Code (PM) Measurement

. Counters of 51 BSC Level Clear Code (PM) Measurement

. 71 MS Capability Indication Measurement

. Counters of MS Capability Indication Measurement


http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

Documents

NED GSM Interfaces and Counter