Huawei Bsc6000 Kpi Ref

8/21/2019 Huawei Bsc6000 Kpi Ref

http://slidepdf.com/reader/full/huawei-bsc6000-kpi-ref 1/609

HUAWEI BSC6000 Base Station Controller

Performance Counter Reference Contents

Issue 03 (2007-05-09) Huawei Technologies Proprietary i

Contents

1 BSC Measurement......................................................................................................................1-1

1.1 Overview of BSC Measurement....................................................................................................................1-2

1.2 Access Measurement per BSC ......................................................................... .............................................1-2

1.2.1 Overview..............................................................................................................................................1-2

1.2.2 Immediate Assignment Requests per BSC................................................................................ ...........1-4

1.2.3 Immediate Assignment Commands per BSC.......................................................................................1-5

1.2.4 SDCCH Seizure Requests per BSC .................................................................. ...................................1-5

1.2.5 Failed SDCCH Seizures due to Busy SDCCH per BSC ...................................................................... 1-6

1.2.6 Successful SDCCH Seizures per BSC ................................................................... ..............................1-6

1.2.7 Call Drops on SDCCH per BSC ...................................................................... ....................................1-7

1.2.8 Traffic Volume on SDCCH per BSC........................................................ ............................................1-7

1.2.9 Available SDCCHs per BSC......................................................................... .......................................1-8

1.2.10 Configured SDCCHs per BSC...........................................................................................................1-8

1.2.11 TCH Seizure Requests per BSC (Signaling Channel)........................................................................1-9

1.2.12 Failed TCH Seizures due to Busy TCH per BSC (Signaling Channel)..............................................1-9

1.2.13 Successful TCH Seizures per BSC (Signaling Channel) ................................................................. 1-10

1.2.14 Call Drops on TCH per BSC (Signaling Channel).............................................................. .............1-10

1.2.15 Traffic Volume on TCH per BSC (Signaling Channel) .............................................................. ......1-11

1.2.16 TCH Seizure Requests per BSC (Traffic Channel)............................................................. ............. 1-11

1.2.17 Failed TCH Seizures due to Busy TCH per BSC (Traffic Channel) ................................................1-12

1.2.18 Successful TCH Seizures per BSC (Traffic Channel)............................. .........................................1-12

1.2.19 Call Drops on TCH in Stable State per BSC (Traffic Channel) ....................................................... 1-13

1.2.20 TCH Seizure Requests in TCH Handovers per BSC (Traffic Channel).......................... .................1-13

1.2.21 Failed TCH Seizures in TCH Handovers due to Busy TCH per BSC (Traffic Channel) .................1-14

1.2.22 Successful TCH Seizures in TCH handovers per BSC (Traffic Channel)........................................1-14

1.2.23 Call Drops in TCH Handovers per BSC (Traffic Channel)................................. .............................1-15

1.2.24 Traffic Volume on TCH per BSC (Traffic Channel) ....................................................................... .1-15

1.2.25 Available TCHs per BSC ......................................................................... ........................................1-16

1.2.26 Configured TCHs per BSC .............................................................. ................................................1-16

1.2.27 Call Setup Indications per BSC (CS Service) ...................................................................... ............1-17

1.2.28 Random Access Success Ratio per BSC ................................................................ ..........................1-17

1.2.29 TCH Assignment Success Ratio per BSC....................................................................... .................1-18



Contents


Performance Counter Reference

ii Huawei Technologies Proprietary Issue 03 (2007-05-09)

1.2.30 Congestion Ratio on SDCCH per BSC............................................................................................1-18

1.2.31 Call Drop Ratio on SDCCH per BSC....................................................................... .......................1-18

1.2.32 SDCCH Availability per BSC ......................................................... ................................................. 1-19

1.2.33 Congestion Ratio on TCH per BSC............................................................ .....................................1-19

1.2.34 Call Drop Ratio on TCH per BSC....................................................................................................1-20

1.2.35 Traffic Call Drop Ratio on TCH per BSC........................................................................................1-20

1.2.36 TCH Availability per BSC ..................................................................... ..........................................1-21

1.2.37 Call Setup Success Ratio per BSC (Immediate Assignment)..................................... ......................1-21

1.3 TRX Measurement per BSC........................................................................................................................1-21

1.3.1 Overview............................................................................................................................................1-21

1.3.2 Number of Configured TRXs per BSC..............................................................................................1-22

1.3.3 Number of Available TRXs per BSC ............................................................. ....................................1-22

1.3.4 TRX Availability per BSC ................................................................ ................................................. 1-22

1.4 Call Measurement per BSC.........................................................................................................................1-23

1.4.1 Overview............................................................................................................................................1-23

1.4.2 MSC Rejects in Response to the CM Service Requests from the MS per BSC (Congestion) ...........1-24

1.4.3 MSC Rejects in Response to the CM Service Requests from the MS per BSC (Network Failure) ...1-24

1.4.4 MSC Rejects in Response to the CM Service Requests from the MS per BSC (Illegal MS) ............1-25

1.4.5 MSC Rejects in Response to the CM Service Requests from the MS per BSC (Other Causes)........ 1-25

1.4.6 Mean Interval between Random Access Attempts per BSC (MOC).................................................. 1-26

1.4.7 Mean Interval between Random Access Attempts per BSC (PS Call)............................................... 1-26

1.4.8 Paging Requests on the Abis Interface per BSC (CS Service)...........................................................1-26

1.4.9 Successful Pagings on the Abis Interface per BSC (CS Service).......................................................1-27 1.4.10 PCH Overloads due to CS Service Counted Through the Indications from the Abis Interface per BSC

....................................................................................................................................................................1-27

1.4.11 RACH Overloads due to CS Service Counted Through the Indications from the Abis Interface per

BSC.............................................................................................................................................................1-28

1.4.12 Paging Requests on the Abis Interface per BSC (PS Service) ......................................................... 1-28

1.4.13 PCH Overloads due to PS Service Counted through the Indications from the Abis Interface per BSC

....................................................................................................................................................................1-29

1.4.14 Immediate Assignment Requests per BSC (PS Service)............................................... ...................1-29

1.4.15 Immediate Assignment Commands per BSC (PS Service).............................................................. 1-30

1.5 Assignment Measurement per BSC.............................................................................................................1-30 1.5.1 Overview............................................................................................................................................1-30

1.5.2 Failed Assignments per BSC (Invalid State)......................................................................................1-31

1.5.3 Failed Assignments per BSC (Invalid Message)................................................................................1-31

1.5.4 Failed Assignments per BSC (Channel Unavailable)..................................................................... ....1-32

1.5.5 Failed Assignments per BSC (Terrestrial Resource Unavailable)..................................... .................1-32

1.5.6 Failed Assignments per BSC (Terrestrial Circuit Already Allocated)......................... .......................1-33

1.5.7 Failed Assignments per BSC (Equipment Failure) ........................................................................ ....1-33

1.5.8 Failed Assignments per BSC (Reconnection to Old Channels) ......................................................... 1-34

1.5.9 Failed Assignments per BSC (Timer Expired)...................................................................................1-34





Issue 03 (2007-05-09) Huawei Technologies Proprietary iii

1.5.10 Failed Assignments per BSC (Other Causes)...................................................................................1-35

1.5.11 CHAN ACT NACK Messages Sent by BTS in Immediate Assignment Procedure per BSC ..........1-36

1.5.12 Channel Activation Timeouts in Immediate Assignment Procedure per BSC .................................1-36

1.6 Call Drop Measurement per BSC................................................................................................................1-37

1.6.1 Overview............................................................................................................................................1-37

1.6.2 Successful Connections per BSC (TCHF) (Traffic Channel).............................................................1-38

1.6.3 Call Drops after Answers per BSC (TCHF) (Traffic Channel) .......................................................... 1-38

1.6.4 Call Drops on TCH per BSC (Error Indication).................................................................................1-38

1.6.5 Call Drops on TCH per BSC (Connection Failure) ........................................................ ...................1-40

1.6.6 Call Drops on TCH per BSC (Release Indication).............................................................................1-41

1.6.7 Call Drops on TCH per BSC (Abis Terrestrial Link Failure)............................................................. 1-42

1.6.8 Call Drops on TCH per BSC (Forced Handover) .......................................................... ....................1-42

1.6.9 Call Drops on TCH per BSC (Other Causes).....................................................................................1-43

1.7 Handover Failure Measurement per BSC....................................................................................................1-44

1.7.1 Overview............................................................................................................................................1-44

1.7.2 Failed Reconnections to Old Channels upon Intra-Cell Handover Failure per BSC .........................1-45

1.7.3 Successful Reconnections to Old Channels upon Intra-Cell Handover Failure per BSC ..................1-46

1.7.4 Failed Reconnections to Old Channels upon Internal Outgoing Cell Handover Failure per BSC.....1-48

1.7.5 Successful Reconnections to Old Channels upon Internal Outgoing Cell Handover Failure per BSC..1-

49

1.7.6 Failed Reconnections to Old Channels upon External Outgoing Cell Handover Failure per BSC....1-51

1.7.7 Successful Reconnections to Old Channels upon External Outgoing Cell Handover Failure per BSC.1-

53

1.7.8 Failed Reconnections to Old Channels upon Inter-RAT Outgoing Cell Handover Failure per BSC .1-55

1.7.9 Successful Reconnections to Old Channels upon Inter-RAT Outgoing Cell Handover Failure per BSC

....................................................................................................................................................................1-56

1.7.10 Failed External Incoming Cell Handovers per BSC (Illegal Message)............................................ 1-58

1.7.11 Failed External Incoming Cell Handovers per BSC (Channel Unavailable)....................................1-59

1.7.12 Failed External Incoming Cell Handovers per BSC (Requested Terrestrial Resource Unavailable)1-59

1.7.13 Failed External Incoming Cell Handovers per BSC (Terrestrial Resource Already Allocated) .......1-60

1.7.14 Failed External Incoming Cell Handovers per BSC (Equipment Failure) .......................................1-61

1.7.15 Failed External Incoming Cell Handovers per BSC (Timer Expired)..............................................1-62

1.7.16 Failed External Incoming Cell Handovers per BSC (Other Causes)................................................1-63 1.7.17 CHAN ACT NACK Messages Sent by BTS in External Incoming Cell Handover Procedure per BSC

....................................................................................................................................................................1-64

1.7.18 Channel Activation Timeouts in External Incoming Cell Handover Procedure per BSC ................1-65

1.8 Handover Attempt Measurement per BSC..................................................................................................1-65

1.8.1 Overview............................................................................................................................................1-65

1.8.2 Attempted Handovers per BSC (Uplink Signal Quality) ................................................................... 1-66

1.8.3 Attempted Handovers per BSC (Downlink Signal Quality)...............................................................1-67

1.8.4 Attempted Handovers per BSC (Uplink Signal Strength)..................................................................1-67

1.8.5 Attempted Handovers per BSC (Downlink Signal Strength) ............................................................. 1-68

1.8.6 Attempted Handovers per BSC (Timing Advance) ........................................................................... .1-69



Contents



iv Huawei Technologies Proprietary Issue 03 (2007-05-09)

1.8.7 Attempted Handovers per BSC (Better Cell)....................................................................... ..............1-69

1.8.8 Attempted Handovers per BSC (Load) ...................................................................... ........................1-70

1.8.9 Attempted Handovers per BSC (Rapid Level Drop)..........................................................................1-71

1.8.10 Attempted Handovers per BSC (MSC Intervention).................................................. ......................1-71

1.8.11 Attempted Handovers per BSC (OM Intervention)............................................................. .............1-72

1.8.12 Attempted Handovers per BSC (Other Causes) ............................................................................ ...1-72

1.8.13 Attempted Handovers per BSC (Underlaid Subcell to Overlaid Subcell).......... ..............................1-73

1.8.14 Attempted Handovers per BSC (Overlaid Subcell to Underlaid Subcell).......... ..............................1-74

1.8.15 Attempted Handovers per BSC (Intra-Cell TCHF-to-TCHH Handover).........................................1-74

1.8.16 Attempted Handovers per BSC (Directed Retry).............................................................................1-75

1.9 Handover Success Measurement per BSC................................................................. .................................1-76

1.9.1 Overview............................................................................................................................................1-76

1.9.2 Successful Handovers per BSC (Uplink Signal Quality)...................................................................1-77

1.9.3 Successful Handovers per BSC (Downlink Signal Quality) .............................................................. 1-77

1.9.4 Successful Handovers per BSC (Uplink Signal Strength) ................................................................. 1-78

1.9.5 Successful Handovers per BSC (Downlink Signal Strength).............................................................1-78

1.9.6 Successful Handovers per BSC (Timing Advance)............................................................................1-79

1.9.7 Successful Handovers per BSC (Better Cell).....................................................................................1-79

1.9.8 Successful Handovers per BSC (Load)..............................................................................................1-80

1.9.9 Successful Handovers per BSC (Rapid Level Drop) ........................................................................ .1-80

1.9.10 Successful Handovers per BSC (MSC Intervention) ............................................................ ...........1-81

1.9.11 Successful Handovers per BSC (OM Intervention) ............................................................ .............1-82

1.9.12 Successful Handovers per BSC (Other Causes)............................................................................ ...1-82 1.9.13 Successful Handovers per BSC (Underlaid Subcell to Overlaid Subcell) .......................................1-83

1.9.14 Successful Handovers per BSC (Overlaid Subcell to Underlaid Subcell) .......................................1-83

1.9.15 Successful Handovers per BSC (Intra-Cell TCHF-to-TCHH Handover) ........................................1-84

1.9.16 Successful Handovers per BSC (Directed Retry).............................................................................1-84

1.10 Inter-Frequency-Band Measurement per BSC.................................................................. ........................1-86

1.10.1 Overview..........................................................................................................................................1-86

1.10.2 Attempted Internal Inter-Cell Handovers per BSC (900/850 to 1800/1900).................................... 1-87

1.10.3 Attempted Internal Inter-Cell Handovers per BSC (1800/1900 to 900/850).................................... 1-87

1.10.4 Successful Internal Inter-Cell Handovers per BSC (900/850 to 1800/1900) ...................................1-88

1.10.5 Successful Internal Inter-Cell Handovers per BSC (1800/1900 to 900/850) ...................................1-89

1.10.6 Attempted Incoming BSC Handovers per BSC (900/850 to 1800/1900).........................................1-90

1.10.7 Attempted Incoming BSC Handovers per BSC (1800/1900 to 900/850).........................................1-90

1.10.8 Successful Incoming BSC Handovers per BSC (900/850 to 1800/1900) ........................................1-91

1.10.9 Successful Incoming BSC Handovers per BSC (1800/1900 to 900/850) ........................................1-92

1.10.10 Attempted Outgoing BSC Handovers per BSC (900/850 to 1800/1900).......................................1-93

1.10.11 Attempted Outgoing BSC Handovers per BSC (1800/1900 to 900/850) .......................................1-93

1.10.12 Successful Outgoing BSC Handovers per BSC (900/850 to 1800/1900).......................................1-94

1.10.13 Successful Outgoing BSC Handovers per BSC (1800/1900 to 900/850).......................................1-95

1.11 Handover KPI Measurement per BSC....................................................................................................... 1-96





Issue 03 (2007-05-09) Huawei Technologies Proprietary v

1.11.1 Overview..........................................................................................................................................1-96

1.11.2 Internal Intra-Cell Handover Requests per BSC................................................................ ..............1-98

1.11.3 Internal Intra-Cell Handover Commands per BSC ........................................................... ...............1-98

1.11.4 Successful Internal Intra-Cell Handovers per BSC..........................................................................1-99

1.11.5 Internal Outgoing Cell Handover Requests per BSC..................................................................... ..1-99

1.11.6 Internal Outgoing Cell Handover Commands per BSC............................................................. ....1-100

1.11.7 Successful Internal Outgoing Cell Handovers per BSC.................................................................1-101

1.11.8 Internal Incoming Cell Handover Requests per BSC.....................................................................1-101

1.11.9 Internal Incoming Cell Handover Commands per BSC................................................................. 1-102

1.11.10 Successful Internal Incoming Cell Handovers per BSC...............................................................1-103

1.11.11 External Outgoing Cell Handover Requests per BSC ................................................................ ..1-103

1.11.12 External Outgoing Cell Handover Commands per BSC .............................................................. 1-104

1.11.13 Successful External Outgoing Cell Handovers per BSC..............................................................1-105

1.11.14 External Incoming Cell Handover Requests per BSC..................................................................1-105

1.11.15 External Incoming Cell Handover Commands per BSC..............................................................1-106

1.11.16 Successful External Incoming Cell Handovers per BSC........................................... ...................1-107

1.11.17 Dual-Band Handover Requests per BSC...................................................................................... 1-107

1.11.18 Successful Dual-Band Handovers per BSC .................................................................... .............1-108

1.11.19 External Outgoing Cell Handover Requests per BSC (Inter-Signaling-Point Handover)............1-108

1.11.20 Failed External Outgoing Cell Handovers per BSC (Inter-Signaling-Point Handover)............... 1-109

1.11.21 External Outgoing Cell Handover Commands per BSC (Inter-Signaling-Point Handover) ........1-109

1.11.22 Internal Handover Success Ratio per BSC...................................................................................1-109

1.11.23 Intra-BSC Radio Handover Success Ratio per BSC ............................................................ ........1-110 1.11.24 External Outgoing Cell Handover Success Ratio per BSC .......................................................... 1-110

1.11.25 External Outgoing Cell Radio Handover Success Ratio per BSC................................................ 1-111

1.11.26 External Incoming Cell Handover Success Ratio per BSC............................. ............................. 1-111

1.11.27 External Incoming Cell Radio Handover Success Ratio per BSC ............................................... 1-112

1.11.28 Handover Success Ratio per BSC.................................................................... ............................ 1-112

1.11.29 Radio Handover Success Ratio per BSC......................................................................................1-113

1.11.30 Dual-Band Handover Success Ratio per BSC..............................................................................1-113

2 SCCP Measurement...................................................................................................................2-1

2.1 Overview of SCCP Measurement ........................................................... ...................................................... 2-2 2.2 SCCP OSP Measurement ........................................................ ................................................................ ......2-2

2.2.1 Overview of SCCP OSP Measurement ................................................................... .............................2-2

2.2.2 Number of Sent UDT Messages ............................................................. .............................................2-3

2.2.3 Number of Received UDT Messages...................................................................................................2-3

2.2.4 Number of Sent XUDT Messages........................................................................................................2-4

2.2.5 Number of Received XUDT Messages................................................................................................2-4

2.2.6 Number of Sent CR Messages ................................................................. ............................................2-4

2.2.7 Number of Received CR Messages......................................................................................................2-5

2.2.8 Number of Sent CREF Messages.........................................................................................................2-5



Contents



vi Huawei Technologies Proprietary Issue 03 (2007-05-09)

2.2.9 Number of Received CREF Messages.................................................................................................2-6

2.2.10 Ratio of CREF by Peer SCCP............................................................................................................2-6

2.2.11 Ratio of CREF by Local SCCP..........................................................................................................2-6

2.2.12 Received CC Messages......................................................................................................................2-7

2.2.13 Sent CC Messages..............................................................................................................................2-7

2.2.14 Sent DT1 Messages............................................................................................................................2-8

2.2.15 Received DT1 Messages....................................................................................................................2-8

2.2.16 Sent RLSD Messages.........................................................................................................................2-8

2.2.17 Received RLSD Messages.................................................................................................................2-9

2.2.18 Sent RLC Messages ................................................................ ........................................................... 2-9

2.2.19 Received RLC Messages ................................................................... .............................................. 2-10

3 MTP3 Measurement ..................................................................................................................3-1

3.1 Overview of MTP3 Measurement.................................................................................................................3-2

3.2 MTP3 Link Measurement ................................................................ ............................................................. 3-2

3.2.1 Overview..............................................................................................................................................3-2

3.2.2 In-Service Duration of MTP3 Link......................................................................................................3-3

3.2.3 Out-of-Service Duration of MTP3 Link...............................................................................................3-4

3.2.4 Duration of MTP3 Link Fault ..................................................................... .........................................3-4

3.2.5 Duration of MTP3 Link Local Inhibition.............................................................................................3-4

3.2.6 Duration of MTP3 Link Remote Inhibition ........................................................................ .................3-5

3.2.7 Duration of MTP3 Link Remote Processor Fault ............................................................. ...................3-5

3.2.8 Duration of MTP3 Link Congestion ...................................................................... ..............................3-6

3.2.9 Failures of MTP3 Link for All Reasons...............................................................................................3-6

3.2.10 MTP3 Link Local Inhibitions .................................................................. ..........................................3-6

3.2.11 MTP3 Link Remote Inhibitions .................................................................... .....................................3-7

3.2.12 MTP3 Link Remote Processor Failures ........................................................... ..................................3-7

3.2.13 MTP3 Link Local Switchovers ............................................................ ..............................................3-8

3.2.14 MSUs Sent on MTP3 Link.................................................................................................................3-8

3.2.15 MSUs Received on MTP3 Link.........................................................................................................3-9

3.2.16 MTP3 Link Congestions .............................................................. ...................................................... 3-9

3.2.17 Discarded MSUs During Link Congestion .................................................................... ....................3-9

3.2.18 Transfer Inhibition Messages Received on MTP3 Link...................................................................3-10 3.2.19 Octets in SIFs or SIOs Sent on MTP3 Link.....................................................................................3-10

3.2.20 Octets in SIFs and SIOs Received by MTP3 Link...........................................................................3-11

3.2.21 64 kbit/s Timeslots Occupied by a Signaling Link...........................................................................3-11

3.2.22 Ratio of Transmit Bandwidth to Total Bandwidth ................................................................... ........3-11

3.2.23 Ratio of Receive Bandwidth to Total Bandwidth........................ ..................................................... 3-12

3.2.24 Bytes of MTP2 Message Head in MSU Messages on MTP3 Link..................................................3-12

4 LAPD Measurement ..................................................................................................................4-1

4.1 Overview of LAPD Measurement.................................................................................................................4-2

4.2 LAPD Link Measurement ............................................................... .............................................................. 4-2





Issue 03 (2007-05-09) Huawei Technologies Proprietary vii

4.2.1 Overview..............................................................................................................................................4-2

4.2.2 SABME Frames Sent on LAPD Link ..................................................................... .............................4-3

4.2.3 SABME Frames Received on LAPD Link ........................................................... ...............................4-3

4.2.4 REJ Frames Sent on LAPD Link.......................................................................... ...............................4-4

4.2.5 REJ Frames Received on LAPD Link .................................................................... .............................4-4

4.2.6 RNR Frames Sent on LAPD Link........................................................................................................4-5

4.2.7 RNR Frames Received on LAPD Link................................................................................................4-5

4.2.8 I Frames Resent on LAPD Link...........................................................................................................4-5

4.2.9 Incorrect I Frames Received on LAPD Link ...................................................................... .................4-6

4.2.10 I Frames Received on LAPD Link from Application Layer .............................................................. 4-6

4.2.11 I Frames Sent on LAPD Link.............................................................................................................4-7

4.2.12 I Frames Received by LAPD Link.....................................................................................................4-7

4.2.13 I Frames Discarded by LAPD Link ............................................................... ....................................4-7

4.2.14 UA Frames Sent on LAPD Link .......................................................................... ..............................4-8

4.2.15 UA Frames Received by LAPD Link.................................................................................................4-8

4.2.16 UI Frames Received by LAPD Link..................................................................................................4-9

5 System Load Measurement ......................................................................................................5-1

5.1 Overview of System Load Measurement .......................................................................... ............................5-2

5.2 CPU Usage Measurement ....................................................... ................................................................ ......5-2

5.2.1 Overview..............................................................................................................................................5-2

5.2.2 Mean CPU Usage.................................................................................................................................5-2

5.2.3 Maximum CPU Usage .............................................................. ........................................................... 5-3

6 BTSM Management...................................................................................................................6-1

6.1 Overview of BTSM Measurement ..................................................................... ...........................................6-2

6.2 BTS State Measurement per BTS..................................................................................................................6-2

6.2.1 Overview..............................................................................................................................................6-2

6.2.2 Successful BTS Initializations ...................................................................... .......................................6-3

6.2.3 Failed BTS Initializations ................................................................ .................................................... 6-3

6.2.4 BTS OML Disruption Duration ..................................................................... ......................................6-4

6.2.5 BTS Out-of-Service Duration ..................................................................... .........................................6-4

6.2.6 BTS Availability...................................................................................................................................6-4

6.2.7 BTS In-Service Duration ........................................................................... ..........................................6-5

6.3 BTS Configuration Measurement per BM Subrack ........................................................................... ...........6-5

6.3.1 Overview..............................................................................................................................................6-5

6.3.2 Activated BTSs ............................................................. ....................................................................... 6-6

6.3.3 Available BTSs.....................................................................................................................................6-6

6.4 Cell State Measurement per Cell...................................................................................................................6-6

6.4.1 Overview..............................................................................................................................................6-6

6.4.2 Successful Cell Initializations..............................................................................................................6-7

6.4.3 Failed Cell Initializations.....................................................................................................................6-7

6.4.4 Cell BCCH Mutual Aid........................................................................................................................6-8



Contents



viii Huawei Technologies Proprietary Issue 03 (2007-05-09)

6.4.5 Recoveries after Cell BCCH Mutual Aid.............................................................................................6-8

6.4.6 Cell Baseband Hopping Mutual Aid .................................................................. ..................................6-9

6.4.7 Recoveries After Cell Baseband Hopping Mutual Aid ............................................................. ...........6-9

6.4.8 Cell Out-of-Service Duration...............................................................................................................6-9

6.4.9 Cell Availability ............................................................. .................................................................... 6-10

6.4.10 Cell In-Service Duration ..................................................................... ............................................. 6-10

6.5 Cell Configuration Measurement per BM Subrack.....................................................................................6-11

6.5.1 Overview............................................................................................................................................6-11

6.5.2 Activated Cells...................................................................................................................................6-11

6.5.3 Available Cells .............................................................. ................................................................ .....6-11

6.6 TRX State Measurement per TRX................................................................... ........................................... 6-12

6.6.1 Overview............................................................................................................................................6-12

6.6.2 TRX Out-of-Service Duration............................................................................................................6-12

6.7 TRX Configuration Measurement per BM Subrack....................................................................................6-13

6.7.1 Overview............................................................................................................................................6-13

6.7.2 Activated TRXs..................................................................................................................................6-13

6.7.3 Available TRXs................................................................... ............................................................... 6-13

6.7.4 TRX Availability ............................................................ .................................................................... 6-14

6.8 CRC Error Measurement per BTS .................................................................. ............................................ 6-14

6.8.1 Overview............................................................................................................................................6-14

6.8.2 Duration of CRC Error on Ports 0 Through 23..................................................................................6-14

6.9 CRC Serious Error Measurement per BTS .............................................................. ...................................6-16

6.9.1 Overview............................................................................................................................................6-16 6.9.2 Duration of Serious CRC Error on Ports 0 Through 23 ................................................................... ..6-16

6.10 LAPD Link Measurement at the BTS .................................................................. .....................................6-18

6.10.1 Overview..........................................................................................................................................6-18

6.10.2 SABME Frames Sent by the BTS on LAPD Link.................................................................. .........6-18

6.10.3 SABME Frames Received by the BTS on LAPD Link ................................................................... 6-19

6.10.4 BTS-Sent Rejects to the LAPD Setup Requests ......................................................................... .....6-20

6.10.5 BTS-Received Rejects to the LAPD Setup Requests............................................. ..........................6-20

6.10.6 RNR Frames Sent by the BTS on LAPD Link.................................................................................6-21

6.10.7 RNR Frames Received by the BTS on LAPD Link.........................................................................6-21

6.10.8 I Frames Resent by the BTS on LAPD Link....................................................................................6-22

6.10.9 NRERR Frames Received by the BTS on LAPD Link....................................................................6-22

6.10.10 L3 Data Requests Received by BTS on LAPD Link ..................................................................... 6-23

6.10.11 I Frames Sent by the BTS on LAPD Link......................................................................................6-23

6.10.12 I Frames Received by the BTS on LAPD Link..............................................................................6-24

6.10.13 Queue Overflows of Messages Sent by BTS on LAPD Link ........................................................ 6-24

6.10.14 Erroneous Long Frames Received by BTS Physical Layer on LAPD Link...................................6-25

6.10.15 Erroneous Octet Received by BTS Physical Layer on LAPD Link...............................................6-25

6.10.16 Discarded Series Received by BTS Physical Layer on LAPD Link..............................................6-26

6.10.17 Number of Times the BTS Receives CRC Errors on LAPD Link .................................................6-26





Issue 03 (2007-05-09) Huawei Technologies Proprietary ix

6.10.18 L1 and L2 Overflows on LAPD Link of the BTS..........................................................................6-27

6.10.19 Total Frames Received by the BTS Physical Layer on LAPD Link ..............................................6-27

7 Resources Measurement...........................................................................................................7-1

7.1 Overview of Resources Measurement...........................................................................................................7-2 7.2 A Interface Circuit Measurement per DPC................................................................................... .................7-2

7.2.1 Overview..............................................................................................................................................7-2

7.2.2 Mean Number of Uninstalled Circuits on the A Interface................. ................................................... 7-3

7.2.3 Mean Number of Faulty Circuits on the A Interface........................................................................ ....7-3

7.2.4 Mean Number of Circuits in Maintenance State on the A Interface........................ .............................7-4

7.2.5 Mean Number of Blocked Circuits on the A Interface.........................................................................7-4

7.2.6 Mean Number of Idle Circuits on the A Interface................................................................................7-5

7.2.7 Mean Number of Busy Circuits on the A Interface..............................................................................7-5

7.2.8 Mean Number of Circuits with Uninstalled Peer Circuits on the A Interface ......................................7-6

7.3 TC Measurement per DPC .................................................................. .......................................................... 7-6

7.3.1 Overview..............................................................................................................................................7-6

7.3.2 Mean Number of Faulty TC Resources................................................................................................7-7

7.3.3 Mean Number of Idle TC Resources....................................................................................................7-7

7.3.4 Mean Number of Busy TC Resources..................................................................................................7-8

7.4 Pb Interface Circuit Measurement per PCU..................................................................................................7-8

7.4.1 Overview..............................................................................................................................................7-8

7.4.2 Mean Number of Faulty Circuits on the Pb Interface .................................................................. ........7-9

7.4.3 Mean Number of Blocked Circuits on the Pb Interface .................................................................... ...7-9

7.4.4 Mean Number of Idle Circuits on the Pb Interface ............................................................ ................7-10

7.4.5 Mean Number of Busy Circuits on the Pb Interface .............................................................. ............7-10

7.4.6 Mean Number of Circuits in Maintenance State on the Pb Interface................................................. 7-11

7.5 Ater Interface Circuit Measurement per BM Subrack.................................................................................7-11

7.5.1 Overview............................................................................................................................................7-11

7.5.2 Mean Number of Faulty Circuits on the Ater Interface......................................................................7-12

7.5.3 Mean Number of Idle Circuits on the Ater Interface..........................................................................7-12

7.5.4 Mean Number of Busy Circuits on the Ater Interface........................................................................7-13

8 MSC Measurement....................................................................................................................8-1

8.1 Overview of MSC Measurement...................................................................................................................8-2

8.2 MSC Measurement per DPC.........................................................................................................................8-2

8.2.1 Overview..............................................................................................................................................8-2

8.2.2 Number of MSC Resets ................................................................. ...................................................... 8-2

8.2.3 Number of Messages Received from MSC..........................................................................................8-3

9 CBC Measurement .....................................................................................................................9-1

9.1 Overview of CBC Measurement ...................................................................... ............................................. 9-2

9.2 CBC Measurement per BSC ................................................................. ........................................................ 9-2

9.2.1 Overview..............................................................................................................................................9-2

9.2.2 WRITE-REPLACE Requests Received by BSC ................................................................... ..............9-3



Contents



x Huawei Technologies Proprietary Issue 03 (2007-05-09)

9.2.3 KILL Requests Received by BSC........................................................................................................9-4

9.2.4 STATUS-CBCH-QUERY Requests Received by BSC...................... ..................................................9-4

9.2.5 STATUS-MESSAGE-QUERY Requests Received by BSC ................................................................ 9-4

9.2.6 SET-DRX Requests Received by BSC ............................................................................ ....................9-5

9.2.7 RESET Requests Received by BSC.....................................................................................................9-5

9.2.8 REPORT Responses to WRITE-REPLACE Requests.................................................................. .......9-5

9.2.9 REJECT Responses to WRITE-REPLACE Requests.......................................................................... 9-6

9.2.10 REPORT Responses to KILL Requests .................................................................. ...........................9-6

9.2.11 REJECT Responses to KILL Requests ................................................................... ...........................9-7

9.2.12 REPORT Responses to STATUS-CBCH-QUERY Requests ............................................................. 9-7

9.2.13 REJECT Responses to STATUS-CBCH-QUERY Requests .............................................................. 9-8

9.2.14 REPORT Responses to STATUS-MESSAGE-QUERY Requests......................................................9-8

9.2.15 REJECT Responses to STATUS-MESSAGE-QUERY Requests ......................................................9-9

9.2.16 REPORT Responses to SET-DRX Requests....................... ............................................................... 9-9

9.2.17 REJECT Responses to SET-DRX Requests............................................... ......................................9-10

9.2.18 RESTART-INDICATION Requests Sent from BSC................ ........................................................ 9-10

9.2.19 REJECT Responses to RESTART-INDICATION Requests ............................................................ 9-11

9.2.20 FAILURE-INDICATION Requests Sent from BSC....................................................................... .9-11

9.2.21 CBCH Loading Indications Received by BSC (Overflow)..............................................................9-12

9.2.22 CBCH Loading Indications Received by BSC (Underflow)............................................................9-12

9.2.23 WRITE-REPLACE Requests (WRITE Requests) Received by BSC..............................................9-12

9.2.24 REPORT Responses to WRITE-REPLACE Requests (WRITE Requests) .....................................9-13

9.2.25 REJECT Responses to WRITE-REPLACE Requests (WRITE Requests) ......................................9-13 9.2.26 WRITE-REPLACE Requests (REPLACE Requests) Received by BSC..................... ....................9-14

9.2.27 REPORT Responses to WRITE-REPLACE Requests (REPLACE Requests) ................................9-14

9.2.28 REJECT Responses to WRITE-REPLACE Requests (REPLACE Requests) .................................9-14

9.2.29 Mean Capacity of BSC Message Library.........................................................................................9-15

9.2.30 Disruptions of the BSC-CBC Connection........................................................................................9-15

10 PCU Measurement.................................................................................................................10-1

10.1 Overview of PCU Measurement ....................................................................... ........................................10-2

10.2 PCU Measurement per BSC......................................................................................................................10-2

10.2.1 Overview..........................................................................................................................................10-2 10.2.2 Total Messages Received from PCU................................................................................................ 10-2

10.3 PCU Measurement per PCU ................................................................... .................................................. 10-3

10.3.1 Overview..........................................................................................................................................10-3

10.3.2 Messages Received from a PCU......................................................................................................10-3

11 Paging Measurement.............................................................................................................11-1

11.1 Overview of Paging Measurement ........................................................................ .................................... 11-2

11.2 A Interface Paging Measurement............................................................................ ................................... 11-2

11.2.1 Overview of A Interface Paging Measurement ...................................................................... .......... 11-2

11.2.2 MSC-Initiated Paging Requests for CS Service...............................................................................11-3





Issue 03 (2007-05-09) Huawei Technologies Proprietary xi

11.2.3 SGSN-Initiated Paging Requests for CS Service ........................................................................... ..11-3

11.2.4 SGSN-Initiated Paging Requests for PS Service........................................................................... ...11-4

11.2.5 Delivered to BTS for CS Service .......................................................................... ........................... 11-5

11.3 Abis Interface Paging Measurement..........................................................................................................11-6

11.3.1 Overview of Abis Interface Paging Measurement............................................................................ 11-6

11.3.2 Delivered Paging Messages for CS Service....................................................................... .............. 11-6

11.3.3 Delivered Paging Messages for PS Service ........................................................................ ............. 11-7

11.4 Measurement of Discarded Paging Messages due to Overload per LAPD ............................................... 11-8

11.4.1 Overview of Measurement of Discarded Paging Messages due to Overload per LAPD .................11-8

11.4.2 SM Pagings Discarded on LAPD Link ..................................................................... ....................... 11-9

11.4.3 CS Pagings Discarded on LAPD Link ....................................................................... ...................... 11-9

11.4.4 PS Pagings Discarded on LAPD Link..................................................................................... ......... 11-9

12 Call Measurement..................................................................................................................12-1

12.1 Overview of Call Measurement ..................................................................... ........................................... 12-3

12.2 Call Duration Measurement per BSC........................................................................................................12-4

12.2.1 Overview..........................................................................................................................................12-4

12.2.2 Mean Duration of Call Access ........................................................................... ..............................12-4

12.2.3 Mean Duration of Call Establishment..............................................................................................12-4

12.3 Flow Control Measurement per Cell .................................................................... .....................................12-5

12.3.1 Overview..........................................................................................................................................12-5

12.3.2 MSG DEL IND Messages Sent on Abis Interface ..................................................................... ......12-6

12.3.3 MSG CCCH LOAD IND (RACH) Messages Sent on Abis Interface .............................................12-6

12.3.4 MSG CCCH LOAD IND (PCH) Messages Sent on Abis Interface.................................................12-7

12.3.5 PACKET CCCH LOAD IND Messages Sent on Abis Interface................................. .....................12-7

12.3.6 MSG ABIS OVERLOAD (CCCH OVERLOAD) Messages Sent on Abis Interface......................12-8

12.3.7 MSG ABIS OVERLOAD (PROCESSOR OVERLOAD) Messages Sent on Abis Interface ..........12-8

12.3.8 LOAD IND Messages Sent on the A-Interface................................................................................12-9

12.3.9 Increases of Flow Control Levels ................................................................. ...................................12-9

12.3.10 Decreases of Flow Control Levels .......................................................................... .....................12-10

12.3.11 Ignored Trigger Events.................................................................................................................12-11

12.3.12 Highest Level Delays.................................................................... ............................................... 12-11

12.3.13 Paging Messages Discarded from the PCH Queue ................................................................... ...12-12 12.3.14 Maximum Seizure Ratio of PCH Paging Queue..........................................................................12-12

12.4 Short Message Measurement per Cell.....................................................................................................12-13

12.4.1 Overview........................................................................................................................................12-13

12.4.2 Uplink Point-to-Point Short Messages on SDCCH........................................................................ 12-13

12.4.3 Downlink Point-to-Point Short Messages on SDCCH........................................................ ...........12-14

12.4.4 Uplink Point-to-Point Short Messages on TCH.............................................................................12-14

12.4.5 Downlink Point-to-Point Short Messages on TCH ............................................................. ...........12-14

12.4.6 Total Uplink Point-to-Point Short Messages..................................................................................12-15

12.4.7 Total Downlink Point-to-Point Short Messages.............................................................................12-15



Contents



xii Huawei Technologies Proprietary Issue 03 (2007-05-09)

12.4.8 Point-to-Point Short Messages on SDCCH....................................................................................12-15

12.4.9 Point-to-Point Short Messages on TCH.........................................................................................12-16

12.5 Call Drop Measurement per Cell.............................................................................................................12-16

12.5.1 Overview........................................................................................................................................12-16

12.5.2 Call Drop Sampled Measurement per Cell ...................................................................... ..............12-17

12.5.3 Call Drop Analyzed Measurement per Cell ........................................................................... ........12-22

12.6 Channel Activation Measurement per Cell............................................................................................. .12-30

12.6.1 Overview........................................................................................................................................12-30

12.6.2 SDCCH Connection Measurement per Cell...................................................................................12-30

12.6.3 TCH Connection Measurement per Cell........................................................................................12-33

12.6.4 Channel Activation Analyzed Measurement per Cell .................................................................... 12-37

12.7 Channel Seizure Measurement per TRX.................................................................................................12-42

12.8 Immediate Assignment Measurement per Cell........................................................................................12-45

12.8.1 Overview........................................................................................................................................12-45

12.8.2 Channel Requests per Cell ...................................................................... .......................................12-46

12.8.3 Immediate Assignment Commands per Cell..................................................................................12-47

12.8.4 Call Setup Indications per Cell ....................................................................... ...............................12-49

12.8.5 Rejects to Service Requests per Cell..............................................................................................12-51

12.8.6 Immediate Assignment Analyzed Measurement per Cell .............................................................. 12-52

12.9 Assignment Measurement per Cell..........................................................................................................12-55

12.9.1 Overview........................................................................................................................................12-55

12.9.2 Assignment Requests per Cell........................................................................................................12-55

12.9.3 Assignment Commands per Cell....................................................................................................12-58 12.9.4 Completed Assignments per Cell...................................................................................................12-59

12.9.5 Failed Assignments per Cell ........................................................... ............................................... 12-61

12.9.6 Mode Modify Commands per Cell .......................................................................... ......................12-63

12.9.7 Failed Mode Modify Attempts per Cell ............................................................................ .............12-65

12.9.8 Assignment Procedure Analyzed Measurement per Cell ............................................................... 12-67

12.10 Intra-Cell Handover Measurement per Cell ..................................................................... .....................12-70

12.10.1 Overview......................................................................................................................................12-70

12.10.2 Intra-Cell Handover Requests per Cell ................................................................ ........................12-71

12.10.3 Intra-Cell Handover Commands per Cell.....................................................................................12-73

12.10.4 Failed Intra-Cell Handovers per Cell ....................................................................... ....................12-74

12.10.5 Intra-Cell AMR Handover per Cell..............................................................................................12-80

12.10.6 Intra-Cell Handover Detection Messages Received by BSC per Cell..........................................12-82

12.10.7 Intra-Cell Handover Measurement per Cell ........................................................................ .........12-82

12.11 Incoming Internal Inter-Cell Handover Measurement per Cell.............................................................12-88

12.11.1 Overview......................................................................................................................................12-88

12.11.2 Incoming Internal Inter-Cell Handover Requests per Cell ........................................................... 12-89

12.11.3 Incoming Internal Inter-Cell Handover Responses per Cell......................................................... 12-91

12.11.4 Failed Incoming Internal Inter-Cell Handovers per Cell..............................................................12-92

12.11.5 Incoming Internal Inter-Cell Handover Detection Messages Received by BSC per Cell ............12-96





Issue 03 (2007-05-09) Huawei Technologies Proprietary xiii

12.11.6 Incoming Internal Inter-Cell Handover Analyzed Measurement per Cell................ ....................12-97

12.12 Outgoing Internal Inter-Cell Handover Measurement per Cell ............................................................. 12-99

12.12.1 Overview......................................................................................................................................12-99

12.12.2 Outgoing Internal Inter-Cell Handover Requests per Cell......................................................... 12-103

12.12.3 Outgoing Internal Inter-Cell Handover Commands per Cell ..................................................... 12-106

12.12.4 Failed Outgoing Internal Inter-Cell Handovers per Cell............................................................12-109

12.12.5 Outgoing Internal Inter-Cell Handover Measurement per Cell..................................................12-119

12.13 Incoming External Inter-Cell Handover Measurement per Cell..................................... .....................12-124

12.13.1 Overview....................................................................................................................................12-124

12.13.2 Incoming External Inter-Cell Handover Requests per Cell........................................................ 12-126

12.13.3 Incoming External Inter-Cell Handover Responses per Cell ..................................................... 12-128

12.13.4 Failed Incoming External Inter-Cell Handovers per Cell...........................................................12-129

12.13.5 Incoming External Inter-Cell Handover Detection Messages Received by BSC per Cell .........12-134

12.13.6 Incoming External Inter-Cell Handover Analyzed Measurement per Cell ................................12-135

12.14 Outgoing External Inter-Cell Handover Measurement per Cell .......................................................... 12-138

12.14.1 Overview....................................................................................................................................12-138

12.14.2 Outgoing External Inter-Cell Handover Requests per Cell........................................................12-142

12.14.3 Outgoing External Inter-Cell Handover Commands per Cell .................................................... 12-145

12.14.4 Failed Outgoing External Inter-Cell Handovers per Cell...........................................................12-149

12.14.5 Outgoing External Inter-Cell Handover Analyzed Measurement per Cell.................................12-162

12.15 Incoming Inter-RAT Inter-Cell Handover Measurement per Cell ....................................................... 12-168

12.15.1 Overview....................................................................................................................................12-168

12.15.2 Incoming Inter-RAT Inter-Cell Handover Requests per Cell ..................................................... 12-170 12.15.3 Incoming Inter-RAT Inter-Cell Handover Responses per Cell................................................... 12-171

12.15.4 Failed Incoming Inter-RAT Inter-Cell Handovers per Cell ........................................................ 12-172

12.15.5 Incoming Inter-RAT Inter-Cell Handover Analyzed Measurement per Cell.......... ....................12-174

12.16 Outgoing Inter-RAT Inter-Cell Handover Measurement per Cell ....................................................... 12-176

12.16.1 Overview....................................................................................................................................12-176

12.16.2 Outgoing Inter-RAT Inter-Cell Handover Requests per Cell ..................................................... 12-179

12.16.3 Outgoing Inter-RAT Inter-Cell Handover Commands per Cell .................................................12-180

12.16.4 Failed Outgoing Inter-RAT Inter-Cell Handovers per Cell ........................................................ 12-181

12.16.5 Outgoing Inter-RAT Inter-Cell Handover Analyzed Measurement per Cell ..............................12-187

12.17 GSM Cell to GSM Cell Incoming Handover Measurement................................................................ 12-191

12.17.1 Overview....................................................................................................................................12-191

12.17.2 Cell Incoming Handover Requests (Cell to Cell).......................................................................12-192

12.17.3 Failed Cell Incoming Handovers (Cell to Cell)..........................................................................12-192

12.17.4 Cell Incoming Handover Analyzed Measurement (Cell to Cell) ............................................... 12-193

12.17.5 Incoming Cell Handover Requests (Timing Advance) (Cell to Cell)......................................... 12-194

12.18 GSM Cell to GSM Cell Outgoing Handover Measurement................................................................12-194

12.18.1 Overview....................................................................................................................................12-194

12.18.2 Cell Outgoing Handover Commands (Cell to Cell) ................................................................... 12-195

12.18.3 Failed Cell Outgoing Handovers (Cell to Cell)..........................................................................12-197



Contents



xiv Huawei Technologies Proprietary Issue 03 (2007-05-09)

12.18.4 Cell Outgoing Handover Analyzed Measurement (Cell to Cell)................................... .............12-198

12.19 Measurement of MRs upon Handover Initiation per Cell ..................................................... ..............12-199

12.19.1 Overview....................................................................................................................................12-199

12.19.2 Measurement of MRs upon Handover Initiation (Receiving Quality) per Cell .........................12-200

12.19.3 Mean Uplink Receiving Level during Handover Initiation per Cell..........................................12-201

12.19.4 Mean Uplink Receiving Quality during Handover Initiation per Cell .......................................12-202

12.19.5 Concentric Cell Handover Initiation MR Analyzed Measurement (Receiving Level) per Cell .12-203

12.19.6 Concentric Cell Handover Initiation MR Analyzed Measurement (Timing Advance) per Cell.12-204

12.20 KPI Measurement per Cell..................................................................................................................12-205

12.20.1 Overview....................................................................................................................................12-205

12.20.2 Immediate Assignment Requests .................................................................... ...........................12-206

12.20.3 Immediate Assignment Commands............................................................................................12-207

12.20.4 SDCCH Seizure Requests..........................................................................................................12-207

12.20.5 Failed SDCCH Seizures due to Busy SDCCH...........................................................................12-208

12.20.6 Successful SDCCH Seizures......................................................................................................12-208

12.20.7 Traffic Volume on SDCCH................................................................... .....................................12-209

12.20.8 Traffic Volume on SDCCH................................................................... .....................................12-210

12.20.9 Available SDCCHs.....................................................................................................................12-210

12.20.10 Configured SDCCHs................................................................................................................12-210

12.20.11 TCH Seizure Requests (Signaling Channel) .................................................................. .......... 12-211

12.20.12 Failed TCH Seizures due to Busy TCH (Signaling Channel) .................................................. 12-211

12.20.13 Successful TCH Seizures (Signaling Channel) ..................................................................... ...12-212

12.20.14 Call Drops on TCH (Signaling Channel) ...................................................................... ...........12-212 12.20.15 Traffic Volume on TCH (Signaling Channel)........................................................................... 12-213

12.20.16 TCH Seizure Requests (Traffic Channel).............................................................................. ...12-213

12.20.17 Failed TCH Seizures due to Busy TCH (Traffic Channel)........................................ ...............12-214

12.20.18 Successful TCH Seizures (Traffic Channel) ........................................................................... .12-214

12.20.19 Call Drops on TCH in Stable State (Traffic Channel)..............................................................12-214

12.20.20 TCH Seizure Requests in TCH Handovers (Traffic Channel)..................................................12-215

12.20.21 Failed TCH Seizures in TCH Handovers due to Busy TCH (Traffic Channel)........................12-216

12.20.22 Successful TCH Seizures in TCH Handovers (Traffic Channel) .............................................12-216

12.20.23 Call Drops in TCH Handovers (Traffic Channel) .................................................................... 12-217

12.20.24 Traffic Volume on TCH (Traffic Channel)...... ..................................................................... ....12-217

12.20.25 Available TCHs..................................................................... ................................................... 12-218

12.20.26 Configured TCHs.....................................................................................................................12-218

12.20.27 Dual-Band Handover Requests ...................................................................... ..........................12-218

12.20.28 Successful Dual-Band Handovers............................................................................................12-219

12.21 Calls Discarded due to Overload per LAPD ................................................................ .......................12-221

12.21.1 Overview....................................................................................................................................12-221

12.21.2 Random Access Requests Discarded on LAPD ................................................................... ......12-221

13 MR Measurement...................................................................................................................13-1





Issue 03 (2007-05-09) Huawei Technologies Proprietary xv

13.1 Overview of MR Measurement.................................................................................................................13-3

13.2 Number of MRs per Cell...........................................................................................................................13-3

13.2.1 Overview of Number of MRs per Cell.............................................................................................13-3

13.2.2 Sampled MRs per Cell .................................................................. ................................................... 13-4

13.2.3 Analyzed MRs per Cell....................................................................................................................13-5

13.3 Interference Band Measurement per TRX.................................................................................................13-6

13.3.1 Overview of Interference Band Measurement per TRX .................................................................. 13-6

13.3.2 Sampled Measurement of Interference Band per TRX.................................................................... 13-7

13.3.3 Analyzed Measurement of Interference Band per TRX................................................................... 13-8

13.4 Power Control Messages per Cell ........................................................................ ...................................13-10

13.4.1 Overview of Power Control Messages per Cell ................................................................ .............13-10

13.4.2 Number of Power Control Messages per Cell................................................................................13-11

13.4.3 Sampled Power Rank During Power Control per Cell.............................. .....................................13-12

13.4.4 Analyzed Power Rank During Power Control per Cell............................. .....................................13-12

13.4.5 Sampled Level of Power Control Signals per Cell........................................................... ..............13-13

13.4.6 Analyzed Level of Power Control Signals per Cell ....................................................................... 13-14

13.4.7 Sampling Quality of Power Control Signals per Cell ................................................................. ...13-14

13.4.8 Analyzed Quality of Power Control Signals per Cell.....................................................................13-15

13.4.9 Sampled Duration of Maximum Power per Cell............................................................................13-15

13.4.10 Analyzed Duration of Maximum Power per Cell.........................................................................13-16

13.4.11 Distance Between MS and BTS per Cell ................................................................ .....................13-17

13.4.12 Maximum Distance Between MS and BTS per Cell....................................................................13-17

13.4.13 Number of Power Control Messages per Cell..............................................................................13-18 13.4.14 Mean Distance Between MS and BTS.........................................................................................13-18

13.5 Neighbor Cell Level Measurement per Cell............................................................................................13-18

13.5.1 Overview of Neighbor Cell Level Measurement per Cell..............................................................13-18

13.5.2 Strength of Signals in Neighbor Cells............................................................................................13-19

13.5.3 Number of MRs of Neighbor Cells................................................................................................13-19

13.5.4 Mean Strength of Signals in Neighbor Cells..................................................................................13-20

13.6 TCHF Receive Level Measurement per TRX................................................................. ........................13-20

13.7 TCHH Receive Level Measurement per TRX.........................................................................................13-28

13.8 Receive Quality Measurement per TRX .............................................................. ...................................13-36

13.9 Uplink-and-Downlink Balance Measurement per TRX.............................................................. ............13-39

13.10 Number of MRs Based on TA per TRX ........................................................... .....................................13-41

13.11 Radio Link Failure Measurement per TRX......... ..................................................................... .............13-43

13.11.1 Overview of Radio Link Failure Measurement per TRX................... .......................................... 13-43

13.11.2 Uplink and Downlink Level During Radio Link Failure per TRX...............................................13-43

13.11.3 Mean Uplink and Downlink Level During Radio Link Failure per TRX ....................................13-44

13.11.4 Uplink and Downlink Quality During Radio Link Failure per TRX............................................ 13-45

13.11.5 Mean Uplink and Downlink Quality During Radio Link Failure per TRX..................................13-46

13.11.6 TA During Radio Link Failure per TRX .................................................................... ..................13-47

13.11.7 Mean TA During Radio Link Failure per TRX ..................................................................... .......13-47



Contents



xvi Huawei Technologies Proprietary Issue 03 (2007-05-09)

13.11.8 Sampled Radio Link Failures per TRX........................................................................................13-48

13.12 Radio Link Failure Measurement based on TA per TRX ................................................................... ...13-49

13.13 RQI Measurement based on TA per TRX..............................................................................................13-51

13.13.1 Overview of RQI Measurement based on TA per TRX ............................................................... 13-51

13.13.2 Sampled RQI based on TA per TRX......................................................... ...................................13-51

13.13.3 Analyzed RQI based on TA per TRX........................................................ ...................................13-54

14 Channel Measurement ..........................................................................................................14-1

14.1 Overview of Channel Measurement..........................................................................................................14-3

14.2 Channel Configuration Measurement per Cell..........................................................................................14-3

14.2.1 Overview..........................................................................................................................................14-3

14.2.2 Sampled Measurement of Initially Configured Channels ................................................................ 14-4

14.2.3 Analyzed Measurement of Dynamically Configured Channels ....................................................... 14-6

14.2.4 Analyzed Measurement of Available Channels............................................................................ ..14-12

14.2.5 SDCCH Availability.......................................................................................................................14-18

14.2.6 TCH Availability .......................................................... .................................................................. 14-19

14.2.7 Analyzed Measurement of Initially Configured Channels ............................................................. 14-19

14.3 Channel Conversion Measurement per Cell............................................................................................14-22

14.3.1 Overview........................................................................................................................................14-22

14.3.2 Channel Conversion Requests (TCHF-TCHH)..............................................................................14-23

14.3.3 Successful Channel Conversions (TCHF-TCHH) ................................................................ .........14-23

14.3.4 Channel Conversion Requests (TCHH-TCHF)..............................................................................14-24

14.3.5 Successful Channel Conversions (TCHH-TCHF) ......................................................................... 14-25

14.3.6 Number of Channel Conversions (TCH-SDCCH).........................................................................14-26

14.3.7 Number of Channel Conversions (SDCCH-TCH).........................................................................14-26

14.4 Channel Busy Duration Measurement per Cell.......................................................................................14-27

14.4.1 Overview........................................................................................................................................14-27

14.4.2 Busy State Duration of All Channels (SDCCH/TCHF/TCHH) ..................................................... 14-27

14.4.3 Mean Duration of Busy State for All Channels (SDCCH/TCHF/TCHH)......................................14-28

14.5 Measurement of Maximum Busy Channels per Cell...............................................................................14-29

14.6 Channel State Measurement per Cell ................................................................. .....................................14-30

14.6.1 Overview........................................................................................................................................14-30

14.6.2 Mean Number of Busy Signaling Channels (SDCCH/TCHF/TCHH)........... ................................14-31 14.6.3 Mean Number of Busy TCHs (TCHF/TCHH).............................. ................................................. 14-32

14.6.4 Mean Number of Blocked Channels.............. ..................................................................... ...........14-33

14.6.5 Mean Number of Idle Channels .......................................................................... ...........................14-34

14.6.6 Mean Number of Busy TCHs (Overlaid Subcell)........... ............................................................... 14-35

14.6.7 Mean Number of Busy TCHs (Underlaid Subcell)............ ............................................................ 14-35

14.6.8 Mean Number of Busy Signaling Channels (SDCCH/TCHF/TCHH)........... ................................14-36

14.6.9 Mean Number of Busy TCHs (TCHF/TCHH).............................. ................................................. 14-37

14.7 Channel Assignment Request Measurement per Cell........................................... ...................................14-38

14.7.1 Overview........................................................................................................................................14-38





Issue 03 (2007-05-09) Huawei Technologies Proprietary xvii

14.7.2 Channel Assignment Requests in Immediate Assignment Procedure (SDCCH/TCHF/TCHH/TCH)14-

38

14.7.3 Channel Assignment Requests in Assignment Procedure (TCHF/TCHH/TCH) ...........................14-40

14.7.4 Channel Assignment Requests in Internal Intra-Cell Handover Procedure

(SDCCH/TCHF/TCHH/TCH) .................................................................... .............................................. 14-41 14.7.5 Channel Assignment Requests in Incoming Internal Inter-Cell Handover Procedure

(SDCCH/TCHF/TCHH/TCH) .................................................................... .............................................. 14-42

14.7.6 Channel Assignment Requests in Incoming External Inter-Cell Handover Procedure

(SDCCH/TCHF/TCHH/TCH) .................................................................... .............................................. 14-44

14.7.7 Channel Assignment Requests (SDCCH) ......................................................................... .............14-45

14.7.8 Channel Assignment Requests (TCHF) .................................................................. .......................14-46

14.7.9 Channel Assignment Requests (TCHH).........................................................................................14-46

14.7.10 Channel Assignment Requests (TCH) ................................................................. ........................14-47

14.8 Channel Assignment Success Measurement per TRX.............................................................................14-47

14.8.1 Overview........................................................................................................................................14-47

14.8.2 Successful Channel Assignments in Immediate Assignment Procedure (SDCCH/ TCHF/TCHH)14-48

14.8.3 Successful Channel Assignments in Assignment Procedure (TCHF/TCHH) ................................14-50

14.8.4 Successful Channel Assignments in Internal Intra-Cell Handover Procedure (SDCCH/TCHF/TCHH)

..................................................................................................................................................................14-51

14.8.5 Successful Channel Assignments in Incoming Internal Inter-Cell Handover Procedure

(SDCCH/TCHF/TCHH)................................................................... ........................................................ 14-52

14.8.6 Successful Channel Assignments in Incoming External Inter-Cell Handover Procedure (SDCCH/

TCHF/TCHH)...........................................................................................................................................14-53

14.8.7 Successful Channel Assignments (SDCCH)..................................................................................14-54

14.8.8 Successful Channel Assignments (TCHF)................................................................ .....................14-54

14.8.9 Successful Channel Assignments (TCHH) ....................................................................... .............14-55

14.8.10 Successful Channel Assignments (TCH) .......................................................................... ...........14-55

14.9 Channel Assignment Failure Measurement per Cell ...................................................................... .........14-56

14.9.1 Overview........................................................................................................................................14-56

14.9.2 Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Immediate

Assignment Procedure (SDCCH) ................................................................... ..........................................14-57


Assignment Procedure (TCHF) ............................................................................ ....................................14-58


Assignment Procedure (TCHH)................................................................................................................14-59

14.9.5 Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Assignment

Procedure (TCHF/TCHH) ............................................................... ......................................................... 14-59

14.9.6 Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Internal Intra-Cell

Handover Procedure (SDCCH).................................................................................................................14-60

14.9.7 Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Internal Intra-Cell

Handover Procedure (TCHF/TCHH)........................................................................................................14-61

14.9.8 Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Incoming Internal

Inter-Cell Handover Procedure (SDCCH) .............................................................. ..................................14-62

14.9.9 Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Incoming Internal

Inter-Cell Handover Procedure (TCHF/ TCHH)............................................................... ........................14-62



Contents



xviii Huawei Technologies Proprietary Issue 03 (2007-05-09)

14.9.10 Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Incoming External

Inter-Cell Handover Procedure (SDCCH) .............................................................. ..................................14-63

14.9.11 Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Incoming External

Inter-Cell Handover Procedure (TCHF/ TCHH)............................................................... ........................14-64

14.9.12 Channel Assignment Failures (All Channels Busy or Channels Unconfigured) (SDCCH)......... 14-65 14.9.13 Channel Assignment Failures (All Channels Busy or Channels Unconfigured) (TCHF) ............14-65

14.9.14 Channel Assignment Failures (All Channels Busy or Channels Unconfigured) (TCHH) ...........14-66

14.9.15 Channel Assignment Failures (All Channels Busy or Channels Unconfigured) (TCH) ..............14-67

14.10 Channel Assignment Concentric Cell Measurement per Cell ............................................................... 14-68

14.10.1 Overview......................................................................................................................................14-68

14.10.2 Channel Assignment Requests of Concentric Cell...................................................... .................14-69

14.10.3 TCH Assignment Requests of Concentric Cell .................................................................. ..........14-69

14.10.4 Assignment Requests of Concentric Cell in Incoming Internal Inter-Cell Handover Procedure (TCH)

..................................................................................................................................................................14-70

14.10.5 Channel Assignment Requests in Incoming External Inter-Cell Handover Procedure (TCH).....14-71

14.10.6 Channel Assignment Overflows (TCH) (Underlaid Subcell Preferred or Overlaid Subcell Preferred)

..................................................................................................................................................................14-72

14.10.7 Channel Assignment Overflows in Concentric Cell in Incoming Internal Inter-Cell Handover

Procedure (TCH).......................................................................................................................................14-73

14.10.8 Channel Assignment Overflows in Concentric Cell in Incoming External Inter-Cell Handover

Procedure (TCH).......................................................................................................................................14-73

14.10.9 Channel Assignment Overflows in Concentric Cell (TCH)......................................................... 14-74

14.10.10 Channel Assignment Overflows in Concentric Cell (SDCCH)..................................................14-75

14.10.11 Channel Assignment Overflows in Concentric Cell (TCHF) ..................................................... 14-75

14.10.12 Channel Assignment Overflows in Concentric Cell (TCHH).................................................... 14-76

14.10.13 Failed Handovers from Underlaid Subcell to Overlaid Subcell due to Busy Channels in Overlaid

Subcell .......................................................... ...................................................................... ......................14-77

14.10.14 Failed Handovers from Overlaid Subcell to Underlaid Subcell due to Busy Channels in Underlaid

Subcell .......................................................... ...................................................................... ......................14-77

14.11 Channel Assignment Queue Measurement per Cell ..................................................................... .........14-78

14.11.1 Overview......................................................................................................................................14-78

14.11.2 Maximum Queue Length ................................................................ ............................................. 14-78

14.11.3 Total Queue Length......................................................................................................................14-79

14.11.4 Sampled Queuings .............................................................. ......................................................... 14-79

14.11.5 Total Queuing Duration................................................................................................................14-79

14.11.6 Channel Assignment Queue Measurement................................................................................... 14-80

14.11.7 Mean Queue Length.....................................................................................................................14-81

14.11.8 Mean Queuing Duration...............................................................................................................14-82

14.11.9 Failed Queuings ....................................................... .................................................................... 14-82

14.12 Channel Assignment GPRS Measurement per Cell ..................................................................... .........14-83

14.12.1 Overview......................................................................................................................................14-83

14.12.2 Requests for TCH from the PCU ......................................................................... ........................14-83

14.12.3 Successful TCH Requests from the PCU.....................................................................................14-84




Performance Counter Reference Figures

Issue 03 (2007-05-09) Huawei Technologies Proprietary xix

Figures

Figure 2-1 SCCP Measurement..........................................................................................................................2-3

Figure 3-1 MTP3 Measurement .............................................................. ........................................................... 3-3

Figure 4-1 LAPD link measurement ............................................................. ..................................................... 4-3

Figure 11-1 MSC-initiated paging procedure for CS service ........................................................................... 11-3 Figure 11-2 SGSN-initiated paging procedure for CS service ................................................................ .........11-4

Figure 11-3 SGSN-initiated paging procedure for PS service..........................................................................11-5

Figure 11-4 BSC-delivered CS paging procedure .................................................................... ........................ 11-6

Figure 11-5 CS paging procedure.....................................................................................................................11-7

Figure 11-6 PS paging procedure ................................................................... .................................................. 11-8

Figure 12-1 Immediate assignment procedure ....................................................................... ........................12-46

Figure 12-2 trigger points of the counters of Immediate Assignment Commands per Cell............................12-48

Figure 12-3 Trigger points of the counters of Call Setup Indications.............................................................12-51

Figure 12-4 Trigger points of the counters of Rejects to Service Requests per Cell ......................................12-52

Figure 12-5 Trigger point of the counters of Assignment Requests per Cell..................................................12-57

Figure 12-6 Trigger Point of the counters of Assignment Commands per Cell.............................. ................12-59

Figure 12-7 Trigger points of the counters of Completed Assignments per Cell ...........................................12-60

Figure 12-8 Trigger points of the counters of Mode Modify Commands per Cell............... ..........................12-65

Figure 12-9 Trigger points of the counters of Failed Mode Modify Attempts per Cell........................... .......12-67

Figure 12-10 Intra-cell handover procedure...................................................................................................12-71

Figure 12-11 Trigger points of the counters of Failed Intra-Cell Handovers per Cell ....................................12-78

Figure 12-12 Incoming internal inter-cell handover.......................................................................................12-89

Figure 12-13 Trigger points of the counters of Failed Incoming Internal Inter-Cell Handovers per Cell ......12-95

Figure 12-14 Outgoing internal inter-cell handover (excluding directed retry) ........................................... 12-101

Figure 12-15 Outgoing internal inter-cell handover (directed retry) ............................................................ 12-102

Figure 12-16 Trigger points of the counters of Failed Outgoing Internal Inter-Cell Handovers per Cell

(Excluding Directed Retry) .......................................................... ................................................................. 12-115



Figures



xx Huawei Technologies Proprietary Issue 03 (2007-05-09)

Figure 12-17 Trigger points of the counters of Failed Outgoing Internal Inter-Cell Handovers per Cell (Directed

Retry) .................................................................. ......................................................................... ................. 12-116

Figure 12-18 Incoming external inter-cell handover ................................................................... .................12-125

Figure 12-19 Trigger points of the counters of Failed Incoming External Inter-Cell Handovers per Cell BSC.12-132

Figure 12-20 Outgoing external inter-cell handover (excluding directed retry)...........................................12-139

Figure 12-21 Outgoing external inter-cell handover (Directed Retry) ......................................................... 12-141

Figure 12-22 Trigger points of Failed Outgoing External Inter-Cell Handovers (Excluding Directed Retry) ...12-

157

Figure 12-23 Failed Outgoing External Inter-Cell Handovers (Directed Retry) ..........................................12-158

Figure 12-24 Incoming inter-RAT inter-cell handover procedure................................................................ 12-169

Figure 12-25 Incoming inter-RAT inter-cell handover procedure................................................................ 12-173

Figure 12-26 Outgoing inter-RAT inter-cell handover procedure (excluding directed retry).......................12-177

Figure 12-27 Outgoing inter-RAT inter-cell handover procedure (including directed retry) .......................12-178

Figure 12-28 Outgoing inter-RAT inter-cell handover procedure (excluding directed retry).......................12-184

Figure 12-29 Outgoing inter-RAT inter-cell handover procedure (including directed retry) .......................12-185

Figure 14-1 Channel assignment in the immediate assignment procedure.....................................................14-40

Figure 14-2 Channel assignment in the assignment procedure ................................................................... ...14-41

Figure 14-3 Channel assignment in the internal intra-cell handover procedure .............................................14-42

Figure 14-4 Channel assignment in the incoming internal inter-cell handover procedure .............................14-43

Figure 14-5 Channel assignment in the incoming external inter-cell handover procedure.............................14-45

Figure 14-6 Channel assignment in the immediate assignment procedure.....................................................14-49




Performance Counter Reference Tables

Issue 03 (2007-05-09) Huawei Technologies Proprietary xxi

Tables

Table 1-1 Measurement units of BSC Measurement ............................................................... ...........................1-2

Table 1-2 Counters of Access Measurement per BSC............................................................................ ............1-3

Table 1-3 Counters of TRX Measurement per BSC ............................................................................ .............1-22

Table 1-4 Counters of Call Measurement per BSC...........................................................................................1-23 Table 1-5 Counters of Assignment Measurement per BSC .................................................................. ............1-30

Table 1-6 Counters of Call Drop Measurement per BSC ...................................................................... ...........1-37

Table 1-7 Counters of Handover Failure Measurement per BSC ..................................................................... 1-44

Table 1-8 Counters of Handover Attempt Measurement per BSC.......................... ..........................................1-66

Table 1-9 Counters of Handover Success Measurement per BSC....................................................................1-76

Table 1-10 Counters of Inter-Frequency-Band Measurement per BSC............................................................1-86

Table 1-11 Counters of Handover KPI Measurement per BSC ..................................................................... ...1-96

Table 2-1 Measurement unit of SCCP Measurement..........................................................................................2-2

Table 2-2 Counters of SCCP OSP Measurement............................................................... .................................2-2

Table 3-1 MTP3 Measurement Units..................................................................................................................3-2

Table 3-2 Counters of MTP3 Link Measurement ......................................................................... ......................3-2

Table 4-1 Measurement unit of LAPD Measurement.........................................................................................4-2

Table 4-2 Counters of LAPD Link Measurement...............................................................................................4-2

Table 5-1 Measurement unit of System Load Measurement .......................................................... ....................5-2

Table 5-2 Counters of CPU Usage Measurement .............................................................. .................................5-2

Table 6-1 Measurement units of BTSM Measurement.......................................................................................6-2

Table 6-2 Counters of BTS State Measurement per BTS ................................................................. ..................6-2

Table 6-3 Counters of BTS Configuration Measurement per BM Subrack........................................................6-5

Table 6-4 Counters of Cell State Measurement per Cell.............................................. .......................................6-7

Table 6-5 Counters of Cell Configuration Measurement per BM Subrack....................................................... 6-11

Table 6-6 Counters of TRX State Measurement per TRX.................................................................. ..............6-12

Table 6-7 Counters of TRX Configuration Measurement per BM Subrack ..................................................... 6-13



Tables



xxii Huawei Technologies Proprietary Issue 03 (2007-05-09)

Table 6-8 Counters of CRC Error Measurement per BTS............................................................................ ....6-14

Table 6-9 Counters of Duration of CRC Error on Ports 0 Through 23............................................................. 6-15

Table 6-10 Counter of CRC Serious Error Measurement per BTS...................................................................6-16

Table 6-11 Counters of Duration of Serious CRC Error on Ports 0 Through 23 .............................................. 6-16

Table 6-12 Counters of LAPD Link Measurement at the BTS.........................................................................6-18

Table 7-1 Measurement Units of Resources Measurement.................................................................................7-2

Table 7-2 Counters of A Interface Circuit Measurement per DPC .................................................................. ...7-2

Table 7-3 Counters of TC Measurement per DPC..............................................................................................7-6

Table 7-4 Counters of Pb Interface Circuit Measurement per PCU....................................................................7-8

Table 7-5 Counters of Ater Interface Circuit Measurement per BM Subrack................................................... 7-11

Table 8-1 Measurement Unit of MSC Measurement..........................................................................................8-2

Table 8-2 Counters of MSC Measurement per DPC............................................................................. ..............8-2

Table 9-1 Measurement unit of CBC measurement............................................................................................9-2

Table 9-2 Counters of CBC Measurement..........................................................................................................9-2

Table 10-1 Measurement units of PCU Measurement......................................................................................10-2

Table 10-2 Counters of PCU Measurement per BSC .................................................................. .....................10-2

Table 10-3 Counter of PCU Measurement per PCU.........................................................................................10-3

Table 11-1 Measurement units of Paging Measurement...................................................................................11-2

Table 11-2 Counters of Measurement of the Paging on the A Interface per BSC............................................. 11-2

Table 11-3 Counters of Measurement of the Paging on the Abis Interface per Cell.........................................11-6

Table 11-4 Counters of Measurement of Discarded Paging Messages due to Overload per LAPD.................11-8

Table 12-1 Measurement units of call measurement ...................................................................... ..................12-3

Table 12-2 Counters of Call Duration Measurement per BSC ........................................................... ..............12-4

Table 12-3 Counters of Flow Control Measurement per Cell...........................................................................12-5

Table 12-4 Counters of Short Message Measurement per Cell.......................................................................12-13

Table 12-5 Counter classification of Call Drop Measurement per Cell..........................................................12-16

Table 12-6 Counters of Call Drop Sampled Measurement per Cell ............................................................... 12-17

Table 12-7 Counters of Call Drop Analyzed Measurement per Cell .............................................................. 12-22

Table 12-8 Counter classification of Channel Activation Measurement per Cell ...........................................12-30

Table 12-9 Counters of SDCCH Connection Measurement per Cell..............................................................12-30

Table 12-10 TCH Connection Measurement per Cell.....................................................................................12-33

Table 12-11 Counters of Channel Activation Analyzed Measurement per Cell..............................................12-37

Table 12-12 Counters of Channel Seizure Measurement per TRX.................................................................12-42





Issue 03 (2007-05-09) Huawei Technologies Proprietary xxiii

Table 12-13 Counter classification of Immediate Assignment Measurement per Cell ...................................12-46

Table 12-14 Counters of Channel Requests per Cell .................................................................. ....................12-47

Table 12-15 Counters of Immediate Assignment Commands per Cell ........................................................... 12-47

Table 12-16 Counters of Call Setup Indications........... ............................................................................ ......12-49

Table 12-17 Counter of Rejects to Service Requests per Cell .............................................................. ..........12-51

Table 12-18 Counters of Immediate Assignment Analyzed Measurement per Cell .......................................12-52

Table 12-19 Counter classification of Assignment Measurement per Cell.....................................................12-55

Table 12-20 Counters of Assignment Requests per Cell.................................................................................12-55

Table 12-21 Counters of Assignment Commands per Cell.............................................................................12-58

Table 12-22 Counters of Completed Assignments per Cell............................................................................12-59

Table 12-23 Counters of Failed Assignments per Cell ......................................................................... ..........12-61

Table 12-24 Counters of Mode Modify Commands per Cell ....................................................................... ..12-64

Table 12-25 Counters of Failed Mode Modify Attempts per Cell .................................................................. 12-65

Table 12-26 Counters of Assignment Procedure Analyzed Measurement per Cell ........................................12-67

Table 12-27 Counter classification of Intra-Cell Handover Requests per Cell...............................................12-71

Table 12-28 Counters of Internal Intra-Cell Handover Requests per Cell......................................................12-72

Table 12-29 Counters of Intra-Cell Handover Commands per Cell................................................................12-73

Table 12-30 Counters of Failed Intra-Cell Handovers per Cell ............................................................ ..........12-74

Table 12-31 Counters of Intra-Cell AMR Handover per Cell.................................................................. .......12-80

Table 12-32 Counters of Intra-Cell Handover Detection Messages Received by BSC per Cell.....................12-82

Table 12-33 Counters of Intra-Cell Handover Measurement per Cell............................................................12-82

Table 12-34 Counter classification of Incoming Internal Inter-Cell Handover Measurement per Cell ..........12-89

Table 12-35 Counters of Incoming Internal Inter-Cell Handover Requests per Cell......................................12-90

Table 12-36 Counters of Incoming Internal Inter-Cell Handover Responses per Cell ...................................12-91

Table 12-37 Counters of Failed Incoming Internal Inter-Cell Handovers per Cell......................................... 12-92

Table 12-38 Counters of Incoming Internal Inter-Cell Handover Detection Messages Received by BSC per Cell.........................................................................................................................................................................12-96

Table 12-39 Counters of Incoming Internal Inter-Cell Handover Analyzed Measurement per Cell...............12-97

Table 12-40 Counter classification of Outgoing Internal Inter-Cell Handover Measurement per Cell ........12-103

Table 12-41 Counters of Outgoing Internal Inter-Cell Handover Requests per Cell (Excluding Directed Retry)

.......................................................................................................................................................................12-103

Table 12-42 Counters of Outgoing Internal Inter-Cell Handover Requests per Cell (Directed Retry)......... 12-104

Table 12-43 Counters of Outgoing Internal Inter-Cell Handover Commands per Cell (Excluding Directed Retry)

.......................................................................................................................................................................12-106

Table 12-44 Counters of Outgoing Internal Inter-Cell Handover Commands per Cell (Directed Retry) .....12-107



Tables



xxiv Huawei Technologies Proprietary Issue 03 (2007-05-09)

Table 12-45 Counters of Failed Outgoing Internal Inter-Cell Handovers per Cell (Excluding Directed Retry).12-

110

Table 12-46 Counters of Failed Outgoing Internal Inter-Cell Handovers per Cell (Directed Retry)............ 12-111

Table 12-47 Counters of Failed Outgoing Internal Inter-Cell Handovers per Cell (Including Directed Retry)..12-112

Table 12-48 Counters of Outgoing Internal Inter-Cell Handover Measurement per Cell ............................. 12-119

Table 12-49 Counter classification of Incoming External Inter-Cell Handover Measurement per Cell .......12-125

Table 12-50 Counters of Incoming External Inter-Cell Handover Requests per Cell...................................12-126

Table 12-51 Counters of Incoming External Inter-Cell Handover Responses per Cell ................................12-128

Table 12-52 Counters of Failed Incoming External Inter-Cell Handovers per Cell......................................12-129

Table 12-53 Counters of Incoming External Inter-Cell Handover Detection Messages Received by BSC per Cell

.......................................................................................................................................................................12-134

Table 12-54 Counters of Incoming External Inter-Cell Handover Analyzed Measurement per Cell ...........12-135

Table 12-55 Counter classification of outgoing External Inter-Cell Handover Measurement per Cell ........12-142

Table 12-56 Counters of Outgoing External Inter-Cell Handover Requests per Cell (Excluding Directed Retry)

.......................................................................................................................................................................12-142

Table 12-57 Counters of Outgoing External Inter-Cell Handover Requests per Cell (Directed Retry)........12-143

Table 12-58 Counters of Outgoing External Inter-Cell Handover Requests per Cell (Including Directed Retry)

.......................................................................................................................................................................12-144

Table 12-59 Counters of Outgoing External Inter-Cell Handover Commands per Cell (Excluding Directed Retry)

.......................................................................................................................................................................12-145

Table 12-60 Counters of Outgoing External Inter-Cell Handover Commands per Cell (Directed Retry) ....12-146

Table 12-61 Counters of Outgoing External Inter-Cell Handover Commands per Cell (Including Directed Retry)

.......................................................................................................................................................................12-147

Table 12-62 Counters of Failed Outgoing External Inter-Cell Handovers per Cell (Excluding Directed Retry)12-

149

Table 12-63 Counters of Failed Outgoing External Inter-Cell Handovers per Cell (Directed Retry)...........12-151

Table 12-64 Counters of Failed Outgoing External Inter-Cell Handovers per Cell (Including Directed Retry).12-

152

Table 12-65 Counters of Outgoing External Inter-Cell Handover Analyzed Measurement per Cell............ 12-162

Table 12-66 Counter types of Incoming Inter-RAT Inter-Cell Handover Measurement per Cell .................12-169

Table 12-67 Counters of Incoming Inter-RAT Inter-Cell Handover Requests per Cell ................................12-170

Table 12-68 Counters of Incoming Inter-RAT Inter-Cell Handover Responses per Cell..............................12-171

Table 12-69 Counters of Failed Incoming Inter-RAT Inter-Cell Handovers per Cell...................................12-172

Table 12-70 Counters of Incoming Inter-RAT Inter-Cell Handover Analyzed Measurement per Cell......... 12-174

Table 12-71 Counter types of Outgoing Inter-RAT Inter-Cell Handover Measurement per Cell .................12-178

Table 12-72 Counters of Outgoing Inter-RAT Inter-Cell Handover Requests per Cell ................................12-179





Issue 03 (2007-05-09) Huawei Technologies Proprietary xxv

Table 12-73 Counters of Outgoing Inter-RAT Inter-Cell Handover Commands per Cell ............................12-180

Table 12-74 Counters of Failed Outgoing Inter-RAT Inter-Cell Handovers per Cell ...................................12-181

Table 12-75 Counters of Outgoing Inter-RAT Inter-Cell Handover Analyzed Measurement per Cell .........12-187

Table 12-76 Counter types of CGSM Cell to GSM Cell Incoming Handover Measurement....................... 12-191

Table 12-77 Counter of Failed Cell Incoming Handovers (Cell to Cell)...................................................... 12-192

Table 12-78 Counters of Cell Incoming Handover Analyzed Measurement (Cell to Cell) ..........................12-193

Table 12-79 Counter types of GSM Cell to GSM Cell Outgoing Handover ................................................ 12-195

Table 12-80 Counters of Cell Outgoing Handover Commands (Cell to Cell).............................................. 12-195

Table 12-81 Counters of Failed Cell Outgoing Handovers (Cell to Cell).....................................................12-197

Table 12-82 Counters of Cell Outgoing Handover Analyzed Measurement................................................. 12-198

Table 12-83 Counter types of Measurement of MRs upon Handover Initiation per Cell .............................12-200

Table 12-84 Counters of Measurement of MRs upon Handover Initiation (Receiving Quality) per Cell ....12-200

Table 12-85 Counters of Concentric Cell Handover Initiation MR Analyzed Measurement (Receiving Level)

per Cell........ ..................................................................... .......................................................................... ...12-203

Table 12-86 Counters of Concentric Cell Handover Initiation MR Analyzed Measurement (Timing Advance)

per Cell........ ..................................................................... .......................................................................... ...12-204

Table 12-87 Counters of KPI Measurement per Cell....................................................................................12-205

Table 12-88 Counter of Calls Discarded due to Overload per LAPD........................................................... 12-221

Table 13-1 Measurement units of MR Measurement........................................................................................13-3

Table 13-2 Counters of Number of MRs per Cell.............................................................................................13-3

Table 13-3 Counters of Sampled MRs per Cell .................................................................. ..............................13-4

Table 13-4 Counters of Analyzed MRs per Cell...............................................................................................13-5

Table 13-5 Power level range of the interference band.....................................................................................13-7

Table 13-6 Counters of Interference Band Measurement per TRX.................................................................. 13-7

Table 13-7 Counters of Sampled Measurement of Interference Band..............................................................13-7

Table 13-8 Counters of Analyzed Measurement of Interference Band per TRX..............................................13-8

Table 13-9 Counters of Power Control Messages per Cell.............................................................................13-10

Table 13-10 Counters of Number of Power Control Messages per Cell.........................................................13-11

Table 13-11 Counters of Sampled Power Rank During Power Control per Cell............................................13-12

Table 13-12 Counters of Analyzed Power Rank During Power Control per Cell...........................................13-12

Table 13-13 Counters of Sampled Level of Power Control Signals per Cell..................................................13-13

Table 13-14 Counters of Analyzed Level of Power Control Signals per Cell ................................................13-14

Table 13-15 Counters of Quality of Power Control Signals per Cell..............................................................13-14

Table 13-16 Counters of Analyzed Quality of Power Control Signals per Cell..............................................13-15



Tables



xxvi Huawei Technologies Proprietary Issue 03 (2007-05-09)

Table 13-17 Counters of Sampled Duration of Maximum Power per Cell.....................................................13-15

Table 13-18 Counters of Analyzed Duration of Maximum Power per Cell............................ ........................13-16

Table 13-19 Counters of Neighbor Cell Level Measurement per Cell ........................................................... 13-19

Table 13-20 Rank of the receive level ............................................................. ............................................... 13-20

Table 13-21 Rank of the receive quality based on the bit error rate ............................................................... 13-21

Table 13-22 Counters of TCHF Receive Level Measurement per TRX......................................................... 13-21

Table 13-23 Counters of TCHH Receive Level Measurement per TRX ........................................................ 13-29

Table 13-24 Counters of Receive Quality Measurement per TRX................................................................. 13-36

Table 13-25 Mapping between the uplink/downlink balance rank and the receive level ...............................13-39

Table 13-26 Counters of Uplink-and-Downlink Balance Measurement per TRX................. .........................13-40

Table 13-27 Counters of Number of MRs based on TA per TRX.................................................... ...............13-41

Table 13-28 Counters of Radio Link Failure Measurement per TRX............................................................. 13-43

Table 13-29 Counters of Uplink and Downlink Level During Radio Link Failure per TRX .........................13-43

Table 13-30 Counters of Mean Uplink and Downlink Level During Radio Link Failure per TRX ...............13-44

Table 13-31 Counters of Uplink and Downlink Quality During Radio Link Failure per TRX ......................13-45

Table 13-32 Counters of Mean Quality of Uplink and Downlink During Radio Link Failure per TRX........13-46

Table 13-33 Counters of TA During Radio Link Failure per TRX ................................................................. 13-47

Table 13-34 Counters of Mean TA During Radio Link Failure per TRX....................................................... 13-47

Table 13-35 Counters of Sampled Radio Link Failures per TRX...................................................................13-48

Table 13-36 Counters of Radio Link Failure Measurement based on TA per TRX........................................13-49

Table 13-37 Counters of RQI Measurement based on TA per TRX ............................................................... 13-51

Table 13-38 Counters of Sampled RQI based on TA per TRX................................................................... ....13-51

Table 13-39 Counters of Analyzed RQI based on TA per TRX................................................................. .....13-54

Table 14-1 Measurement units of Channel Measurement.................................................................................14-3

Table 14-2 Classification of the counters in the Channel Configuration Measurement per Cell measurement unit

...........................................................................................................................................................................14-4

Table 14-3 Counters in the Sampled Measurement of Initially Configured Channels measurement unit ........14-4

Table 14-4 Counters in the Analyzed Measurement of Dynamically Configured Channels measurement unit14-7

Table 14-5 Counters in the Analyzed Measurement of Available Channels measurement unit ......................14-12

Table 14-6 Counters in the Analyzed Measurement of Initially Configured Channels measurement unit .....14-20

Table 14-7 Counters in the Channel Conversion Measurement per Cell measurement unit........................... 14-22

Table 14-8 Classification of the counters in the Channel Busy Duration Measurement per Cell measurement

unit ................................................................ ................................................................. .................................14-27

Table 14-9 Counters in the Busy State Duration of All Channels (SDCCH/TCHF/TCHH) measurement unit .14-

27





Issue 03 (2007-05-09) Huawei Technologies Proprietary xxvii

Table 14-10 Counters in the Mean Duration of Busy State for All Channels (SDCCH/TCHF/TCHH)

measurement unit .................................................................. ............................................................... ...........14-28

Table 14-11 Counters in the Measurement of Maximum Busy Channels per Cell measurement unit............ 14-29

Table 14-12 Classification of the counters in the Channel State Measurement per Cell measurement unit ...14-31 Table 14-13 Counters in the Mean Number of Busy Signaling Channels (SDCCH/TCHF/TCHH) measurement

unit ................................................................ ................................................................. .................................14-31

Table 14-14 Counters in the Mean Number of Busy TCHs (TCHF/TCHH) measurement unit.....................14-33

Table 14-15 Counters in the Mean Number of Blocked Channels measurement unit ....................................14-34

Table 14-16 Counters in the Mean Number of Idle Channels measurement unit ...........................................14-34

Table 14-17 Counters in the Mean Number of Busy Signaling Channels (SDCCH/TCHF/TCHH) measurement

unit ................................................................ ................................................................. .................................14-36

Table 14-18 Counters in the Mean Number of Busy TCHs (TCHF/TCHH) measurement unit.....................14-37

Table 14-19 Classification of the counters in the Channel Assignment Request Measurement per Cell


Table 14-20 Counters in the Channel Assignment Requests in Immediate Assignment Procedure

(SDCCH/TCHF/TCHH/TCH) measurement unit ................................................................ ...........................14-39

Table 14-21 Counters in the Channel Assignment Requests in Assignment Procedure (TCHF/TCHH/TCH)


Table 14-22 Counters in the Channel Assignment Requests in Internal Intra-Cell Handover Procedure


Table 14-23 Counters in the Channel Assignment Requests in Incoming Internal Inter-Cell Handover Procedure


Table 14-24 Counters in the Channel Assignment Requests in Incoming External Inter-Cell Handover

Procedure measurement unit .................................................................... ....................................................... 14-44

Table 14-25 Classification of the counters in the Channel Assignment Success Measurement per TRX


Table 14-26 Counters in the Channel Assignment Success Measurement per TRX measurement unit .........14-48

Table 14-27 Counters in the Successful Channel Assignments in Assignment Procedure (TCHF/TCHH)


Table 14-28 Counters in the Successful Channel Assignments in Internal Intra-Cell Handover Procedure

(SDCCH/TCHF/TCHH) .............................................................. ................................................................... 14-51

Table 14-29 Counters in the Successful Channel Assignments in Incoming Internal Inter-Cell Handover

Procedure (SDCCH/TCHF/TCHH) measurement unit ........................................................... ........................14-52

Table 14-30 Counters in the Successful Channel Assignments in Incoming External Inter-Cell Handover

Procedure (SDCCH/ TCHF/TCHH) measurement unit ......................................................................... .........14-53

Table 14-31 Classification of the counters in the Channel Assignment Failure Measurement per Cell


Table 14-32 Counters in the Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in

Assignment Procedure (TCHF/TCHH) measurement unit .................................................................. ...........14-59



Tables



xxviii Huawei Technologies Proprietary Issue 03 (2007-05-09)


Internal Intra-Cell Handover Procedure (TCHF/TCHH) measurement unit ................................................... 14-61


Incoming Internal Inter-Cell Handover Procedure (TCHF/ TCHH) measurement unit ..................................14-62


Incoming External Inter-Cell Handover Procedure (TCHF/ TCHH) measurement unit .................................14-64

Table 14-36 Counter classification of Channel Assignment Concentric Cell Measurement per Cell............. 14-68

Table 14-37 Channel Assignment Requests of Concentric Cell ..................................................................... 14-69

Table 14-38 Counters of TCH Assignment Requests of Concentric Cell ....................................................... 14-70

Table 14-39 Counters of Channel Assignment Requests of Concentric Cell in Incoming Internal Inter-Cell

Handover Procedure (TCH ) ................................................................. .......................................................... 14-70

Table 14-40 Counters of Channel Assignment Requests in Incoming External Inter-Cell Handover Procedure

(TCH)..............................................................................................................................................................14-71

Table 14-41 Counters of Channel Assignment Overflows (TCH) (Underlaid Subcell Preferred or Overlaid

Subcell Preferred)............................................................................................................................................14-72

Table 14-42 Counters of Channel Assignment Overflows in Concentric Cell in Incoming Internal Inter-Cell

Handover Procedure (TCH) .................................................................. .......................................................... 14-73

Table 14-43 Counters of Channel Assignment Overflows in Concentric Cell in Incoming External Inter-Cell

Handover Procedure (TCH) .................................................................. .......................................................... 14-74

Table 14-44 Counters of Channel Assignment Overflows in Concentric Cell (TCH)....................................14-74

Table 14-45 Counters of Channel Assignment Overflows in Concentric Cell (SDCCH)...............................14-75

Table 14-46 Counters of Channel Assignment Overflows in Concentric Cell (TCHF).................................. 14-76

Table 14-47 Counters of Channel Assignment Overflows in Concentric Cell (TCHH).................................14-76

Table 14-48 Measurement units of Channel Assignment Queue Measurement per Cell................................14-78

Table 14-49 Counters of Channel Assignment Queue Measurement ............................................................. 14-80

Table 14-50 Counters of Channel Assignment GPRS Measurement per Cell ................................................14-83




Performance Counter Reference 1 BSC Measurement

Issue 03 (2007-05-09) Huawei Technologies Proprietary 1-1

1 BSC Measurement

About This Chapter

The following table lists the sections of this chapter.

Section Description

1.1 Overview of BSC

Measurement

Introduces the BSC Measurement and its measurement

units.

1.2 Access Measurement perBSC

Describes the Access Measurement per BSC and itscounters.

1.3 TRX Measurement perBSC

Describes the TRX Measurement per BSC and itscounters.

1.4 Call Measurement perBSC Describes the Call Measurement per BSC and itscounters.

1.5 Assignment Measurement

per BSC

Describes the Assignment Measurement per BSC and its

counters.

1.6 Call Drop Measurement per BSC

Describes the Call Drop Measurement per BSC and itscounters.

1.7 Handover Failure

Measurement per BSC

Describes the Handover Failure Measurement per BSC

and its counters.

1.8 Handover Attempt

Measurement per BSC

Describes the Handover Attempt Measurement per BSC

and its counters

1.9 Handover Success

Measurement per BSC

Describes the Handover Success Measurement per BSC

and its counters.

1.10 Inter-Frequency-BandMeasurement per BSC

Describes the Inter-Frequency-Band Measurement perBSC and its counters.

1.11 Handover KPI

Measurement per BSC

Describes the Handover KPI Measurement per BSC and

its counters.



1 BSC Measurement



1-2 Huawei Technologies Proprietary Issue 03 (2007-05-09)

1.1 Overview of BSC Measurement

BSC Measurement refers to the measurement of traffic in all the cells controlled by a BSC.Table 1-1 lists the measurement units of BSC Measurement.

Table 1-1 Measurement units of BSC Measurement

Measurement Unit Section

Access Measurement per BSC 1.2

TRX Measurement per BSC 1.3

Call Measurement per BSC 1.4

Assignment Measurement per BSC 1.5

Call Drop Measurement per BSC 1.6

Handover Failure Measurement per BSC 1.7

Handover Attempt Measurement per BSC 1.8

Handover Success Measurement per BSC 1.9

Inter-Frequency-Band Measurement per BSC 1.10

Handover KPI Measurement per BSC 1.11

1.2 Access Measurement per BSC

1.2.1 Overview

When an MS requires network services for reasons such as the Mobile Originated Call(MOC), Mobile Terminated Call (MTC), emergency call, call re-establishment, location

updating, packet call, and Location Measurement Unit (LMU)+Reserved, it sends the BTS aCHAN REQ message on the RACH. After receiving this message, the BTS reports a CHAN

RQD message to the BSC for a signaling channel.

After receiving the CHAN RQD message, the BSC assigns and activates a signaling channelto the MS. If the BSC receives a CHAN ACTIV ACK message from the BTS, the signaling

channel is ready for the assignment. The BSC sends an IMM ASS CMD message, requestingthe MS to access the specified signaling channel. This signaling channel can be an SDCCH or

a TCH.

After receiving a FIRST SABM frame from the MS, the BTS sends an EST IND message tothe BSC.

After receiving the EST IND message that carries an MM message (CM SERV REQ message,

LOC UPD REQ message, IMSI DTCH message, PAG RSP message, CM RE-EST REQ






message, SS ACTIVATION message, LCS message), the BSC requests the MSC to establishthe A interface connection and transparently transmits the MM message to the MSC.

Table 1-2 lists the counters of Access Measurement per BSC.

Table 1-2 Counters of Access Measurement per BSC

Counter Section

ZCA300J: Immediate Assignment Requests per BSC 1.2.2

ZK3101: Immediate Assignment Commands per BSC 1.2.3

ZK3000: SDCCH Seizure Requests per BSC 1.2.4

ZK3001: Failed SDCCH Seizures due to Busy SDCCH per BSC 1.2.5

ZK3003: Successful SDCCH Seizures per BSC 1.2.6

ZCM30: Call Drops on SDCCH per BSC 1.2.7

ZK3004: Traffic Volume on SDCCH per BSC 1.2.8

ZK3005: Available SDCCHs per BSC 1.2.9

ZK3006: Configured SDCCHs per BSC 1.2.10

ZK3020: TCH Seizure Requests per BSC (Signaling Channel) 1.2.11

ZK3021: Failed TCH Seizures due to Busy TCH per BSC (Signaling Channel) 1.2.12

ZK3023: Successful TCH Seizures per BSC (Signaling Channel) 1.2.13

ZK3022: Call Drops on TCH per BSC (Signaling Channel) 1.2.14

ZK3024: Traffic Volume on TCH per BSC (Signaling Channel) 1.2.15

ZK3010A: TCH Seizure Requests per BSC (Traffic Channel) 1.2.16

ZK3011A: Failed TCH Seizures due to Busy TCH per BSC (Traffic Channel) 1.2.17

ZK3013A: Successful TCH Seizures per BSC (Traffic Channel) 1.2.18

ZCM36D: Call Drops on TCH in Stable State per BSC (Traffic Channel) 1.2.19

ZK3010B: TCH Seizure Requests in TCH Handovers per BSC (TrafficChannel)

1.2.20

ZK3011B: Failed TCH Seizures in TCH Handovers due to Busy TCH per BSC(Traffic Channel)

1.2.21

ZK3013B: Successful TCH Seizures in TCH handovers per BSC (Traffic

Channel)

1.2.22

ZCM339B: Call Drops in TCH Handovers per BSC (Traffic Channel) 1.2.23

ZK3014: Traffic Volume on TCH per BSC (Traffic Channel) 1.2.24

ZK3015: Available TCHs per BSC 1.2.25

ZK3016: Configured TCHs per BSC 1.2.26



1 BSC Measurement




Counter Section

ZCA303J: Call Setup Indications per BSC (CS Service) 1.2.27

ZTR101A: Random Access Success Ratio per BSC 1.2.28

ZTR102A: TCH Assignment Success Ratio per BSC 1.2.29

ZTR103A: Congestion Ratio on SDCCH per BSC 1.2.30

ZTR104A: Call Drop Ratio on SDCCH per BSC 1.2.31

ZTR105A: SDCCH Availability per BSC 1.2.32

ZTR106A: Congestion Ratio on TCH per BSC 1.2.33

ZTR107A: Call Drop Ratio on TCH per BSC 1.2.34

ZTR108A: Traffic Call Drop Ratio on TCH per BSC 1.2.35

ZTR109A: TCH Availability per BSC 1.2.36

ZTR110A: Call Setup Success Ratio per BSC (Immediate Assignment) 1.2.37

1.2.2 Immediate Assignment Requests per BSC

Counter

ZCA300J: Immediate Assignment Requests per BSC

Meaning

To obtain the service from the network, an MS sends a CHAN REQ message on the RACH.

After receiving this message, the BTS sends a CHAN RQD message to the BSC for adedicated channel. This counter applies to the channel access due to all causes but PS services

in all the cells controlled by a BSC.

Trigger Point

None.

Formula

Immediate Assignment Requests per BSC = ∑<

=

N i

i 0

Immediate Assignment Requests

This counter is the sum of the predefined counter Immediate Assignment Requests in all the

cells controlled by a BSC.






1.2.3 Immediate Assignment Commands per BSC

Counter

ZK3101: Immediate Assignment Commands per BSC

Meaning

In an immediate assignment procedure, an MS reports a CHAN REQ message to the BTS.

The BTS receives this message and sends a CHAN RQD message to the BSC. After receivingthe CHAN RQD message, the BSC assigns a signaling channel to the MS and activates thechannel. If the BSC receives a CHAN ACTIV ACK message from the BTS, the BTS already

prepares the channel. The BSC sends an IMM ASSIGN CMD message to the MS, requestingthe MS to access the specified signaling channel. This channel may be an SDCCH or a TCH.

This counter applies to the channel access due to all causes but PS services in all the cellscontrolled by a BSC.

Trigger Point

None.

Formula

None.

1.2.4 SDCCH Seizure Requests per BSC

CounterZK3000: SDCCH Seizure Requests per BSC

Meaning

In an immediate assignment procedure, an MS requests a channel from the BSS. In an inter-

BSC incoming handover procedure, the MSC requests the BSS to assign a channel for the MS.In an internal handover procedure, the BSC requests a channel from the BSS. In the channel

request procedures described previously, the BSC receives a related request and thenmeasures this counter if the requested channel is an SDCCH.

Trigger Point None.

Formula

SDCCH Seizure Requests per BSC =∑<

=

N i

i 0

SDCCH Seizure Requests

This counter is the sum of the predefined counter SDCCH Seizure Requests in all the cellscontrolled by a BSC.



1 BSC Measurement




1.2.5 Failed SDCCH Seizures due to Busy SDCCH per BSC

Counter

ZK3001: Failed SDCCH Seizures due to Busy SDCCH per BSC

Meaning

In an immediate assignment procedure or a handover procedure, the BSC triggers the counter

when the MS or the MSC requests an SDCCH from the BSS but no SDCCH is available.

Trigger Point

None.

Formula

Failed SDCCH Seizures due to Busy SDCCH per BSC =∑<

=

N i

i 0

Failed SDCCH Seizures due to

Busy SDCCH

This counter is the sum of the predefined counter Failed SDCCH Seizures due to Busy

SDCCH in all the cells controlled by a BSC.

1.2.6 Successful SDCCH Seizures per BSC

Counter

ZK3003: Successful SDCCH Seizures per BSC

Meaning

In an SDCCH immediate assignment procedure, the BTS sends a channel activation success

message to the BSC. After receiving this message, the BSC regards the SDCCH as beingsuccessfully seized. In an SDCCH handover procedure, the BTS sends a handover detectionmessage to the target cell. After receiving this message, the BSC regards the SDCCH as being

successfully seized.

This counter applies to the previous two cases.

Trigger Point

None.

Formula

Successful SDCCH Seizures per BSC=∑<

=

N i

i 0

Successful SDCCH Seizures

This counter is the sum of the predefined counter Successful SDCCH Seizures in all the cells

controlled by a BSC.






1.2.7 Call Drops on SDCCH per BSC

Counter

ZCM30: Call Drops on SDCCH per BSC

Meaning

This counter measures the number of call drops on the SDCCH in all the cells controlled by a

BSC. The call drops may be caused by the Um interface failure, no MRs from the MS for along time, Abis interface failure, equipment failure, and forced handover.

Trigger Point

None.

Formula

Call Drops on SDCCH per BSC=∑<

=

N i

i 0

Call Drops on SDCCH

This counter is the sum of the predefined counter Call Drops on SDCCH in all the cells


1.2.8 Traffic Volume on SDCCH per BSC

Counter

ZK3004: Traffic Volume on SDCCH per BSC

Meaning

This counter measures the ratio of the duration for which the MS occupies the SDCCH to the

granularity period. The duration for which the MS occupies the SDCCH is equal to thenumber of measurement reports from the MS on the SDCCH multiplied by the reporting period 0.47 second.

Trigger Point

None.

Formula

Traffic Volume on SDCCH per BSC =∑<

=

N i

i 0

Traffic Volume on SDCCH

This counter is the sum of the predefined counter Traffic Volume on SDCCH in all the cellscontrolled by a BSC.



1 BSC Measurement




1.2.9 Available SDCCHs per BSC

Counter

ZK3005: Available SDCCHs per BSC

Meaning

This counter measures the number of SDCCHs in idle or busy state in all the cells controlled

by a BSC. Here, the SDCCHs include those obtained dynamically from TCHs. This counter isequal to the total number of available SDCCHs per BSC divided by the number of sample points.

Trigger Point

None.

Formula

Available SDCCHs per BSC =∑<

=

N i

i 0

Available SDCCHs

This counter is the sum of the predefined counter Available SDCCHs in all the cells controlled by a BSC.

1.2.10 Configured SDCCHs per BSC

Counter

ZK3006: Configured SDCCHs per BSC

Meaning

This counter measures the number of SDCCHs configured for all the cells controlled by a

BSC. Here, the SDCCHs include those obtained dynamically from TCHs. This countermeasures the mean number of configured SDCCHs per BSC.

Trigger Point

None.

Formula

Configured SDCCHs per BSC = ∑<

=

N i

i 0

Configured SDCCHs

This counter is the sum of the predefined counter Configured SDCCHs in all the cellscontrolled by a BSC.






1.2.11 TCH Seizure Requests per BSC (Signaling Channel)

Counter

ZK3020: TCH Seizure Requests per BSC (Signaling Channel)

Meaning

This counter measures the number of the CHAN RQD messages sent from the BTS to the

BSC in a very early TCH assignment procedure.

Trigger Point

None.

Formula

TCH Seizure Requests per BSC (Signaling Channel)= ∑<

=

N i

i 0

TCH Seizure Requests (Signaling

Channel)

This counter is the sum of the predefined counter TCH Seizure Requests (Signaling Channel)


1.2.12 Failed TCH Seizures due to Busy TCH per BSC (SignalingChannel)

Counter

ZK3021: Failed TCH Seizures due to Busy TCH per BSC (Signaling Channel)

Meaning

This counter measures the number of times the BSC has no TCH (signaling channel) to assignin a very early TCH assignment procedure.

Trigger Point

None.

Formula

Failed TCH Seizures due to Busy TCH per BSC (Signaling Channel)=∑<

=

N i

i 0

Failed TCH

Seizures due to Busy TCH (Signaling Channel)

This counter is the sum of the predefined counter Failed TCH Seizures due to Busy TCH

(Signaling Channel) in all the cells controlled by a BSC.



1 BSC Measurement




1.2.13 Successful TCH Seizures per BSC (Signaling Channel)

Counter

ZK3023: Successful TCH Seizures per BSC (Signaling Channel)

Meaning

This counter measures the number of successful activations of TCHs (signaling channels)

assigned by the BSC in a very early TCH assignment procedure.

Trigger Point

None.

Formula

Successful TCH Seizures per BSC (Signaling Channel)=∑<

=

N i

i 0

Successful TCH Seizures

(Signaling Channel)

This counter is the sum of the predefined counter Successful TCH Seizures (Signaling

Channel) in all the cells controlled by a BSC.

1.2.14 Call Drops on TCH per BSC (Signaling Channel)

Counter

ZK3022: Call Drops on TCH per BSC (Signaling Channel)

Meaning

This counter measures the number of call drops occurred although the MS sets up on the TCH

a normal connection with the service type of signaling.

Trigger Point

None.

Formula

Call Drops on TCH per BSC (Signaling Channel)=∑<

=

N i

i 0

Call Drops on TCH (Signaling

Channel)

This counter is the sum of the predefined counter Call Drops on TCH (Signaling Channel) in

all the cells controlled by a BSC.






1.2.15 Traffic Volume on TCH per BSC (Signaling Channel)

Counter

ZK3024: Traffic Volume on TCH per BSC (Signaling Channel)

Meaning

This counter measures the ratio of the duration for which the MS occupies the TCH (signaling

channel) to the granularity period. The duration for which the MS occupies the TCH is equalto the number of measurement reports from the MS on the TCH multiplied by the reporting period 0.48 second.

Trigger Point

None.

Formula

Traffic Volume on TCH per BSC (Signaling Channel)=∑<

=

N i

i 0

Traffic Volume on TCH

(Signaling Channel)

This counter is the sum of the predefined counter Traffic Volume on TCH (Signaling Channel)


1.2.16 TCH Seizure Requests per BSC (Traffic Channel)

Counter

ZK3010A: TCH Seizure Requests per BSC (Traffic Channel)

Meaning

This counter measures the number of TCH (traffic channel) seizure requests received by the

BSC from the MSC.

Trigger Point

None.

Formula

TCH Seizure Requests per BSC (Traffic Channel)=∑<

=

N i

i 0

TCH Seizure Requests (Traffic

Channel)

This counter is the sum of the predefined counter TCH Seizure Requests (Traffic Channel) in




1 BSC Measurement




1.2.17 Failed TCH Seizures due to Busy TCH per BSC (TrafficChannel)

CounterZK3011A: Failed TCH Seizures due to Busy TCH per BSC (Traffic Channel)

Meaning

This counter measures the number of failed TCH (traffic channel) seizures due to no TCH

available.

Trigger Point

None.

Formula

Failed TCH Seizures due to Busy TCH per BSC (Traffic Channel) = [∑<

=

N i

i 0

Failed Assignments

(First Assignment, No Channel Available in Assignment Procedure)]+ [∑<

=

N i

i 0

Failed

Assignments (First Assignment, No Channel Available in Directed Retry Procedure)]+

[∑<

=

N i

i 0

Failed Assignments (Reconnection to Old Channels, No Channel Available in

Assignment)]+ [∑<

=

N i

i 0

Failed Assignments (Reconnection to Old Channels, No Channel

Available in Directed Retry)]

1.2.18 Successful TCH Seizures per BSC (Traffic Channel)

Counter

ZK3013A: Successful TCH Seizures per BSC (Traffic Channel)

MeaningThis counter measures the number of successful TCH (traffic channel) seizures by the MS in

assignment procedures.

Trigger Point

None.






Formula

Successful TCH Seizures per BSC (Traffic Channel)=∑<

=

N i

i 0

Successful TCH Seizures (Traffic

Channel)

This counter is the sum of the predefined counter Successful TCH Seizures (Traffic Channel)


1.2.19 Call Drops on TCH in Stable State per BSC (TrafficChannel)

Counter

ZCM36D: Call Drops on TCH in Stable State per BSC (Traffic Channel)

Meaning

This counter measures the number of call drops occurred after the MS is in the stable

communication state on the TCH (traffic channel).

Trigger Point

None.

Formula

Call Drops on TCH in Stable State per BSC (Traffic Channel)=∑<

=

N i

i 0

Call Drops on TCH

This counter is the sum of the predefined counter Call Drops on TCH in all the cells


1.2.20 TCH Seizure Requests in TCH Handovers per BSC (TrafficChannel)

Counter

ZK3010B: TCH Seizure Requests in TCH Handovers per BSC (Traffic Channel)

Meaning

In an internal handover procedure, the MS requests the BSS to reassign a TCH (traffic

channel). In an inter-BSC incoming handover procedure, the MSC requests the BSS to assigna TCH (traffic channel).

This counter measures the total number of TCH seizure requests in the procedures mentioned previously.



1 BSC Measurement




Trigger Point

None.

Formula

TCH Seizure Requests in TCH Handovers per BSC (Traffic Channel)=∑<

=

N i

i 0

Internal Incoming

Cell Handover Requests per BSC(TCH)

This counter is the sum of the predefined counter Internal Incoming Cell Handover Requests per BSC(TCH) in all the cells controlled by a BSC.

1.2.21 Failed TCH Seizures in TCH Handovers due to Busy TCHper BSC (Traffic Channel)

Counter

ZK3011B: Failed TCH Seizures in TCH Handovers due to Busy TCH per BSC (Traffic

Channel)

Meaning


available in TCH handovers.

Trigger Point

None.

Formula

Failed TCH Seizures in TCH Handovers due to Busy TCH per BSC (Traffic Channel)=∑<

=

N i

i 0

Failed TCH Seizures in TCH Handovers due to Busy TCH (Traffic Channel)

This counter is the sum of the predefined counter Failed TCH Seizures in TCH Handoversdue to Busy TCH (Traffic Channel) in all the cells controlled by a BSC.

1.2.22 Successful TCH Seizures in TCH handovers per BSC(Traffic Channel)

Counter

ZK3013B: Successful TCH Seizures in TCH handovers per BSC (Traffic Channel)

Meaning

This counter measures the number of successful TCH (traffic channel) seizures by the MSduring TCH handovers.






Trigger Point

None.

Formula

Successful TCH Seizures in TCH handovers per BSC (Traffic Channel)=∑<

=

N i

i 0

Successful

TCH Seizures in TCH handovers (Traffic Channel)

This counter is the sum of the predefined counter Successful TCH Seizures in TCH handovers(Traffic Channel) in all the cells controlled by a BSC.

1.2.23 Call Drops in TCH Handovers per BSC (Traffic Channel)

CounterZCM339B: Call Drops in TCH Handovers per BSC (Traffic Channel)

Meaning

This counter measures the number of call drops due to the Um interface failure during TCH

(traffic channel) handovers.

Trigger Point

None.

Formula

Call Drops in TCH Handovers per BSC (Traffic Channel)=∑<

=

N i

i 0

Clear Requests Sent on the A

Interface in Handover State (TCHF) (TCH)+∑<

=

N i

i 0

Clear Requests Sent on the A Interface in

Handover State (TCHH) (TCH)

1.2.24 Traffic Volume on TCH per BSC (Traffic Channel)

Counter

ZK3014: Traffic Volume on TCH per BSC (Traffic Channel)

Meaning

This counter measures the ratio of the duration for which the MS occupies the TCH (traffic

channel) to the granularity period. The duration for which the MS occupies the TCH is equalto the number of measurement reports from the MS on the TCH multiplied by the reporting

period 0.48 second.



1 BSC Measurement




Trigger Point

None.

Formula

Traffic Volume on TCH per BSC (Traffic Channel)=∑<

=

N i

i 0

Traffic Volume of TCHs

This counter is the sum of the predefined counter Traffic Volume of TCHs in all the cellscontrolled by a BSC.

1.2.25 Available TCHs per BSC

Counter

ZK3015: Available TCHs per BSC

Meaning

This counter measures the number of TCHs in idle or busy state in all the cells controlled by a

BSC. Here, the TCHs exclude the TCHs changed to SDCCHs through dynamic adjustment but include the TCHs obtained from PDCHs through dynamic adjustment. This counter isequal to the total number of available TCHs divided by the number of sample points.

Trigger Point

None.

Formula

Available TCHs per BSC =∑<

=

N i

i 0

Mean Number of Available Channels (TCH)

This counter is the sum of the predefined counter Mean Number of Available Channels (TCH)in all the cells controlled by a BSC.

1.2.26 Configured TCHs per BSC

Counter

ZK3016: Configured TCHs per BSC

Meaning

This counter measures the number of TCHs configured for all the cells controlled by a BSC.

Here, the TCHs exclude the TCHs changed to SDCCHs through dynamic adjustment butinclude the TCHs obtained from PDCHs through dynamic adjustment. This counter is equal to

the total number of configured TCHs divided by the number of sample points.






Trigger Point

None.

Formula

Configured TCHs per BSC=∑<

=

N i

i 0

Mean Number of Dynamically Configured Channels (TCH)

This counter is the sum of the predefined counter Mean Number of Dynamically ConfiguredChannels (TCH) in all the cells controlled by a BSC.

1.2.27 Call Setup Indications per BSC (CS Service)

Counter

ZCA303J: Call Setup Indications per BSC (CS Service)

Meaning

This counter measures the number of call setup indications received by all the cells in a BSC

during CS services in immediate assignment procedures.

Trigger Point

None.

Formula

Call Setup Indications per BSC (CS Service)=∑<

=

N i

i 0

Call Setup Indications (Circuit Service)

This counter is the sum of the predefined counter Call Setup Indications (Circuit Service) in


1.2.28 Random Access Success Ratio per BSC

Counter

ZTR101A: Random Access Success Ratio per BSC

Meaning

This counter measures the success rate of random access in a BSC, that is, the success rate of

immediate assignment procedures in a BSC.

Trigger Point

None.



1 BSC Measurement




Formula

Random Access Success Ratio per BSC = ([Immediate Assignment Commands per

BSC]/[Immediate Assignment Requests per BSC])*{100}

1.2.29 TCH Assignment Success Ratio per BSC

Counter

ZTR102A: TCH Assignment Success Ratio per BSC

Meaning

This counter measures the success rate of TCH assignment procedures in a BSC.

Trigger Point

None.

Formula

TCH Assignment Success Ratio per BSC = ([∑<

=

N i

i 0

Successful Assignments]/[∑<

=

N i

i 0

Assignment

Requests])*{100}

1.2.30 Congestion Ratio on SDCCH per BSC

Counter

ZTR103A: Congestion Ratio on SDCCH per BSC

Meaning

This counter measures the ratio of the number of times no SDCCH is available for assignment

to the total number of SDCCH requests in a BSC.

Trigger Point

None.

Formula

Congestion Ratio on SDCCH per BSC = ([Failed SDCCH Seizures due to Busy SDCCH per

BSC]/[ SDCCH Seizure Requests per BSC])*{100}

1.2.31 Call Drop Ratio on SDCCH per BSC

Counter

ZTR104A: Call Drop Ratio on SDCCH per BSC






Meaning

This counter measures the ratio of the number of call drops on the SDCCH to the number of

successful SDCCH requests in a BSC.

Trigger Point

None.

Formula

Call Drop Ratio on SDCCH per BSC = ([Call Drops on SDCCH per BSC]/[ Successful

SDCCH Seizures per BSC])*{100}

1.2.32 SDCCH Availability per BSC

Counter

ZTR105A: SDCCH Availability per BSC

Meaning

This counter measures the ratio of the number of the available SDCCHs to the number of the

configured SDCCHs in a BSC.

Trigger Point

None.

Formula

SDCCH Availability per BSC = ([Available SDCCHs per BSC]/[ Configured SDCCHs per

BSC])*{100}

1.2.33 Congestion Ratio on TCH per BSC

Counter

ZTR106A: Congestion Ratio on TCH per BSC

Meaning

This counter measures the ratio of the number of times no TCH is available for assignment in

situations such as call setup, handovers, and very early assignment procedures to the total

number of TCH requests in a BSC.

Trigger Point

None.



1 BSC Measurement




Formula

Congestion Ratio on TCH per BSC = (([Failed TCH Seizures due to Busy TCH per BSC

(Signaling Channel)]+[ Failed TCH Seizures due to Busy TCH per BSC (Traffic

Channel)]+[ Failed TCH Seizures in TCH Handovers due to Busy TCH per BSC (Traffic

Channel)])/([TCH Seizure Requests per BSC (Signaling Channel)]+[ TCH Seizure Requests per BSC (Traffic Channel)]+[ TCH Seizure Requests in TCH Handovers per BSC (TrafficChannel)]))*{100}

1.2.34 Call Drop Ratio on TCH per BSC

Counter

ZTR107A: Call Drop Ratio on TCH per BSC

Meaning

This counter measures the ratio of the number of call drops on the TCH in situations such ascall setup and handovers to the number of successful TCH requests in a BSC.

Trigger Point

None.

Formula

Call Drop Ratio on TCH per BSC =[ Call Drops on TCH]/( [Successful TCH Seizures (Traffic

Channel)]+[Successful TCH Seizures in TCH handovers per BSC (Traffic Channel)])*{100}

1.2.35 Traffic Call Drop Ratio on TCH per BSC

Counter

ZTR108A: Traffic Call Drop Ratio on TCH per BSC

Meaning

This counter measures the ratio of the number of traffic call drops on the TCH in situations

such as call setup and handovers to the number of successful TCH requests in a BSC.

Trigger Point

None.

Formula

Traffic Call Drop Ratio on TCH per BSC = {60}*[Traffic Volume on TCH per BSC (Traffic

Channel)]/([Call Drops on TCH in Stable State per BSC (Traffic Channel)]+[ Call Drops inTCH Handovers per BSC (Traffic Channel)])






1.2.36 TCH Availability per BSC

Counter

ZTR109A: TCH Availability per BSC

Meaning

This counter measures the ratio of the number of the available TCHs to the number of the

configured TCHs in a BSC.

Trigger Point

None.

FormulaTCH Availability per BSC = ([Available TCHs per BSC]/[ Configured TCHs per BSC])*{100}

1.2.37 Call Setup Success Ratio per BSC (Immediate Assignment)

Counter

ZTR110A: Call Setup Success Ratio per BSC (Immediate Assignment)

Meaning

This counter measures the ratio of the number of call setup indications (CS service) to thenumber of immediate assignment requests in a BSC.

Trigger Point

None.

Formula

Call Setup Success Ratio per BSC (Immediate Assignment) = ([Call Setup Indications perBSC (CS Service)]/[ Immediate Assignment Requests per BSC])*{100}

1.3 TRX Measurement per BSC

1.3.1 Overview

TRX Measurement per BSC refers to the measurement of the number of configured TRXs,the number of available TRXs, the TRX availability in a BSC.

Table 1-3 lists the counters of TRX Measurement per BSC.



1 BSC Measurement




Table 1-3 Counters of TRX Measurement per BSC

Counter Section

ZR460: Number of Configured TRXs per BSC 1.3.2

ZR461: Number of Available TRXs per BSC 1.3.3

ZR462: TRX Availability per BSC 1.3.4

1.3.2 Number of Configured TRXs per BSC

Counter

ZR460: Number of Configured TRXs per BSC

Meaning

This counter measures the number of configured TRXs in all the cells controlled by a BSC.

Trigger Point

None.

Formula

None.

1.3.3 Number of Available TRXs per BSC

Counter

ZR461: Number of Available TRXs per BSC

Meaning

This counter measures the number of available TRXs in all the cells controlled by a BSC.

Trigger Point None.

Formula

None.

1.3.4 TRX Availability per BSC

Counter

ZR462: TRX Availability per BSC






Meaning

This counter measures the ratio of the number of the available TRXs to the number of the

configured TRXs in a BSC.

Trigger Point

None.

Formula

TRX Availability per BSC = ([Number of Available TRXs per BSC]/[ Number of Configured

TRXs per BSC])*{100}

1.4 Call Measurement per BSC1.4.1 Overview

Call Measurement per BSC refers to the measurement of call services in a BSC.

Table 1-4 lists the counters of Call Measurement per BSC.

Table 1-4 Counters of Call Measurement per BSC

Counter Section

ZA3050: MSC Rejects in Response to the CM Service Requests from the MS

per BSC (Congestion)

1.4.2

ZA3051: MSC Rejects in Response to the CM Service Requests from the MS per BSC (Network Failure)

1.4.3


per BSC (Illegal MS)

1.4.4


per BSC (Other Causes)

1.4.5

ZTA300A: Mean Interval between Random Access Attempts per BSC (MOC) 1.4.6

ZTA300H: Mean Interval between Random Access Attempts per BSC (PS Call) 1.4.7

ZTA330: Paging Requests on the Abis Interface per BSC (CS Service) 1.4.8

ZTA3030C: Successful Pagings on the Abis Interface per BSC (CS Service) 1.4.9

ZTL3188C: PCH Overloads due to CS Service Counted Through the Indicationsfrom the Abis Interface per BSC

1.4.10

ZTL3188B: RACH Overloads due to CS Service Counted Through theIndications from the Abis Interface per BSC

1.4.11

ZTA331: Paging Requests on the Abis Interface per BSC (PS Service) 1.4.12

ZTL3188D: Immediate Assignment Requests per BSC (PS Service) 1.4.13



1 BSC Measurement




Counter Section

ZTA308H: Mean Interval between Random Access Attempts per BSC (PSService)

1.4.14

ZTA301H: Immediate Assignment Commands per BSC (PS Service) 1.4.15

1.4.2 MSC Rejects in Response to the CM Service Requests fromthe MS per BSC (Congestion)

Counter

ZA3050: MSC Rejects in Response to the CM Service Requests from the MS per BSC(Congestion)

Meaning

In the immediate assignment procedure where an MS requests for connection setup, the MSestablishes an RR connection with the BSS first, and then sends a CM SERV REQ message

on the MM layer. The BSS transparently transmits this message to the NSS. If the NSS doesnot support or cannot respond to the service request because of congestion, the MSC sends a

CM SERV REJ message to the MS and the BSC transparently transmits this message.

Trigger Point

None.

Formula

None.

1.4.3 MSC Rejects in Response to the CM Service Requests fromthe MS per BSC (Network Failure)

Counter

ZA3051: MSC Rejects in Response to the CM Service Requests from the MS per BSC

(Network Failure)

Meaning

After receiving a CM SERVICE REQUEST message sent on the MM layer from an MS, the

MSC sends a CM SERVICE REJECT message to the MS if the MSC cannot respond to theCM service request because of a network failure. The CM SERVICE REJECT message

carries the reject cause of Network Failure.

Trigger Point

None.






Formula

None.

1.4.4 MSC Rejects in Response to the CM Service Requests fromthe MS per BSC (Illegal MS)

Counter

ZA3052: MSC Rejects in Response to the CM Service Requests from the MS per BSC

(Illegal MS)

Meaning


MSC sends a CM SERVICE REJECT message to the MS if the MSC does not respond to theCM service request because the MSC cannot identify the MS. The CM SERVICE REJECT

message carries the reject cause of Illegal MS.

Trigger Point

None.

Formula

None.

1.4.5 MSC Rejects in Response to the CM Service Requests fromthe MS per BSC (Other Causes)

Counter

ZA3053: MSC Rejects in Response to the CM Service Requests from the MS per BSC (Other

Causes)

Meaning


MSC sends a CM SERVICE REJECT message to the MS if the MSC does not respond to theCM service request for causes except for those mentioned previously.

Trigger Point

None.

Formula

None.



1 BSC Measurement




1.4.6 Mean Interval between Random Access Attempts per BSC(MOC)

CounterZTA300A: Mean Interval between Random Access Attempts per BSC (MOC)

Meaning

This counter measures the mean time interval (seconds) between two consecutive channel

requests (MOC) in a granularity period in a BSC.

Trigger Point

None.

Formula

Mean Interval between Random Access Attempts per BSC (MOC) = {[GP]*60}/∑<

=

N i

i 0

Channel

Requests (MOC)

1.4.7 Mean Interval between Random Access Attempts per BSC(PS Call)

CounterZTA300H: Mean Interval between Random Access Attempts per BSC (PS Call)

Meaning

This counter measures the mean time interval (seconds) between two consecutive channel

requests (PS call) in a granularity period in a BSC.

Trigger Point

None.

Formula

Mean Interval between Random Access Attempts per BSC (PS Call) = {[GP]*60}/ ∑<

=

N i

i 0

Channel Requests (Packet Call)

1.4.8 Paging Requests on the Abis Interface per BSC (CS Service)

Counter

ZTA330: Paging Requests on the Abis Interface per BSC (CS Service)






Meaning

This counter measures the number of paging request (CS service) on the Abis interface in all

the cells controlled by a BSC.

Trigger Point

None.

Formula

Delivered Paging Messages on the Abis Interface per BSC (CS Service) = ∑<

=

N i

i 0

Delivered

Paging Messages for CS Service

1.4.9 Successful Pagings on the Abis Interface per BSC (CSService)

Counter

ZTA3030C: Successful Pagings on the Abis Interface per BSC (CS Service)

Meaning

This counter measures the number of successful pagings (CS service) on the Abis interface in


Trigger Point

None.

Formula

Successful Pagings on the Abis Interface per BSC (CS Service)= ∑<

=

N i

i 0

Call Setup Indications

(MTC) (SDCCH) +∑<

=

N i

i 0

Call Setup Indications (MTC) (TCHF)+∑<

=

N i

i 0

Call Setup Indications

(MTC) (TCHH)

1.4.10 PCH Overloads due to CS Service Counted Through theIndications from the Abis Interface per BSC

Counter

ZTL3188C: PCH Overloads due to CS Service Counted Through the Indications from theAbis Interface per BSC



1 BSC Measurement




Meaning

This counter measures the number of PCH overloads (CS service) on the Abis interface in all


Trigger Point

None.

Formula

PCH Overloads due to CS Service Counted Through the Indications from the Abis Interface

per BSC =∑<

=

N i

i 0

MSG CCCH LOAD IND (PCH) Messages Sent on Abis Interface

1.4.11 RACH Overloads due to CS Service Counted Through theIndications from the Abis Interface per BSC

Counter

ZTL3188B: RACH Overloads due to CS Service Counted Through the Indications from the

Abis Interface per BSC

Meaning

This counter measures the number of RACH overloads (CS service) on the Abis interface in


Trigger Point

None.

Formula

RACH Overloads due to CS Service Counted Through the Indications from the Abis Interface

per BSC =∑<

=

N i

i 0

MSG CCCH LOAD IND (RACH) Messages Sent on Abis Interface

1.4.12 Paging Requests on the Abis Interface per BSC (PS Service)

Counter

ZTA331: Paging Requests on the Abis Interface per BSC (PS Service)

Meaning

This counter measures the number of paging request (PS service) on the Abis interface in all







Trigger Point

None.

Formula

Delivered Paging Messages on the Abis Interface per BSC (PS Service )= ∑<

=

N i

i 0

Delivered

Paging Messages for PS Service

1.4.13 PCH Overloads due to PS Service Counted through theIndications from the Abis Interface per BSC

Counter

ZTL3188D: PCH Overloads due to PS Service Counted through the Indications from the AbisInterface per BSC

Meaning

This counter measures the number of PCH overloads (PS service) on the Abis interface in all


Trigger Point

None.

Formula

Immediate Assignment Requests per BSC (PS Service)=∑<

=

N i

i 0

PACKET CCCH LOAD IND

Messages Sent on Abis Interface

1.4.14 Immediate Assignment Requests per BSC (PS Service)

Counter

ZTA308H: Immediate Assignment Requests per BSC (PS Service)

Meaning

This counter measures the number of immediate assignment requests (PS service) in all the


Trigger Point

None.



1 BSC Measurement




Formula

Mean Interval between Random Access Attempts per BSC (PS Call)=∑<

=

N i

i 0

Channel Requests

(Packet Call)

1.4.15 Immediate Assignment Commands per BSC (PS Service)

Counter

ZTA301H: Immediate Assignment Commands per BSC (PS Service)

Meaning

This counter measures the number of immediate assignment commands (PS service) in all the


Trigger Point

None.

Formula

Immediate Assignment Commands per BSC (PS Service)=∑<

=

N i

i 0

Immediate Assignment

Commands (Packet Service)

1.5 Assignment Measurement per BSC

1.5.1 Overview

Assignment Measurement per BSC refers to the measurement of successful and failed

assignment procedures in a BSC.

Table 1-5 lists the counters of Assignment Measurement per BSC.

Table 1-5 Counters of Assignment Measurement per BSC

Counter Section

ZA3129I: Failed Assignments per BSC (Invalid State) 1.5.2

ZA3129J: Failed Assignments per BSC (Invalid Message) 1.5.3

ZTA3129J: Failed Assignments per BSC (Channel Unavailable) 1.5.4

ZTA312A: Failed Assignments per BSC (Requested Terrestrial ResourceUnavailable)

1.5.5

ZTA312K: Failed Assignments per BSC (Terrestrial Resource Already

Allocated)

1.5.6






Counter Section

ZTA312L: Failed Assignments per BSC (Equipment Failure) 1.5.7

ZTA312M: Failed Assignments per BSC (Reconnection to Old Channels) 1.5.8

ZTCA312: Failed Assignments per BSC (Timer Expired) 1.5.9

ZTK3011A: Failed Assignments per BSC (Other Causes) 1.5.10

ZTA3129E: CHAN ACT NACK Messages Sent by BTS in ImmediateAssignment Procedure per BSC

1.5.11

ZTA3159E: Channel Activation Timeouts in Immediate Assignment Procedure per BSC

1.5.12

1.5.2 Failed Assignments per BSC (Invalid State)

Counter

ZA3129I: Failed Assignments per BSC (Invalid State)

Meaning

In an assignment procedure, the MSC sends an ASS REQ message to the BSS, and then theBSS selects a traffic channel or a signaling channel. The assignment procedure may fail

because of different factors.

This counter measures the number of failed assignments in a BSC because of invalid states.

Trigger Point

None.

Formula

None.

1.5.3 Failed Assignments per BSC (Invalid Message)

Counter

ZA3129J: Failed Assignments per BSC (Invalid Message)

Meaning

In an assignment procedure, the MSC sends an ASS REQ message to the BSS, and then theBSS selects a traffic channel or a signaling channel. The assignment procedure may fail


This counter measures the number of failed assignments in a BSC because of invalidmessages.



1 BSC Measurement




Trigger Point

None.

Formula None.

1.5.4 Failed Assignments per BSC (Channel Unavailable)

Counter

ZTA3129J: Failed Assignments per BSC (Channel Unavailable)

Meaning

In an assignment procedure, the MSC sends an ASS REQ message to the BSS, and then theBSS selects a traffic channel or a signaling channel. The assignment procedure may fail because of different factors.

This counter measures the number of failed assignments in a BSC because channels are

unavailable.

Trigger Point

None.

Formula

Failed Assignments per BSC (Channel Unavailable) =∑<

=

N i

i 0

Failed TCH Seizures due to Busy

TCH (Traffic Channel)

1.5.5 Failed Assignments per BSC (Terrestrial ResourceUnavailable)

Counter

ZTA312A: Failed Assignments per BSC (Terrestrial Resource Unavailable)

Meaning

In an assignment procedure, the MSC sends an ASS REQ message to the BSS, and then the

BSS selects a traffic channel or a signaling channel. The assignment procedure may fail


This counter measures the number of failed assignments in a BSC because the terrestrialresources are unavailable.

Trigger Point

None.






Formula

Failed Assignments per BSC (Terrestrial Resource Unavailable) = ∑<

=

N i

i 0

Failed Assignments

(CIC Unavailable)+∑<

=

N i

i 0

Failed Mode Modify Attempts (CIC Unavailable)

1.5.6 Failed Assignments per BSC (Terrestrial Circuit AlreadyAllocated)

Counter

ZTA312K: Failed Assignments per BSC (Terrestrial Circuit Already Allocated)

Meaning


BSS selects a traffic channel or a signaling channel. The assignment procedure may fail because of different factors.

This counter measures the number of failed assignments in a BSC because the terrestrial

circuit is already allocated.

Trigger Point

None.

Formula

Failed Assignments per BSC (Terrestrial Circuit Already Allocated) = ∑<

=

N i

i 0

Failed

Assignments (CIC Allocated)+∑<

=

N i

i 0

Failed Mode Modify Attempts (CIC Allocated)

1.5.7 Failed Assignments per BSC (Equipment Failure)

CounterZTA312L: Failed Assignments per BSC (Equipment Failure)

Meaning




This counter measures the number of failed assignments in a BSC because of equipmentfailures.



1 BSC Measurement




Trigger Point

None.

Formula

Failed Assignments per BSC (Equipment Failure) = [∑<

=

N i

i 0

Failed Assignments (A Interface

Failure)]+ [∑<

=

N i

i 0

Failed Mode Modify Attempts (A Interface Failure)]+ [∑<

=

N i

i 0

Failed

Assignments (First Assignment, Terrestrial Resource Request Failed)]+ [∑<

=

N i

i 0

Failed

Assignments (Reconnection to Old Channels, Terrestrial Resource Request Failed)]+

[∑<

=

N i

i 0

Failed Mode Modify Attempts (Terrestrial Resource Request Failed)]

1.5.8 Failed Assignments per BSC (Reconnection to Old Channels)

Counter

ZTA312M: Failed Assignments per BSC (Reconnection to Old Channels)

Meaning



This counter measures the number of failed assignments in a BSC because of reconnections to

old channels.

Trigger Point

None.

Formula

Failed Assignments per BSC (Reconnection to Old Channels) = ∑<

=

N i

i 0

Failed Assignments

(Reconnection to Old Channels, Reconnection to Old Channel in Assignment)]+ [∑<

=

N i

i 0

Failed

Assignments (Reconnection to Old Channels, Reconnection to Old Channel in DirectedRetry)]

1.5.9 Failed Assignments per BSC (Timer Expired)

Counter

ZTCA312: Failed Assignments per BSC (Timer Expired)






Meaning




This counter measures the number of failed assignments in a BSC because the timer expired.

Trigger Point

None.

Formula

Failed Assignments per BSC (Timer Expired) = [∑<

=

N i

i 0

Failed Assignments (First Assignment,

Assignment Timed Out)]+ [∑<

=

N i

i 0

Failed Assignments (First Assignment, Directed Retry Timed

Out)]+ [∑<

=

N i

i 0

Failed Assignments (Reconnection to Old Channels, Timer Expired in

Assignment)]+ [∑<

=

N i

i 0

Failed Assignments (Reconnection to Old Channels, Timer Expired in

Directed Retry)]+ [∑<

=

N i

i 0

Failed Mode Modify Attempts (Timer Expired)]

1.5.10 Failed Assignments per BSC (Other Causes)

Counter

ZTK3011A: Failed Assignments per BSC (Other Causes)

Meaning



This counter measures the number of failed assignments in a BSC because of other factors.

Trigger Point

None.

Formula

Failed Assignments per BSC (Other Causes) = [∑<

=

N i

i 0

Failed Assignments (Clear Commands

Sent By MSC)]+ [∑

<

=

N i

i 0 Failed Mode Modify Attempts (Clear Commands Sent By MSC)]



1 BSC Measurement




1.5.11 CHAN ACT NACK Messages Sent by BTS in ImmediateAssignment Procedure per BSC

CounterZTA3129E: CHAN ACT NACK Messages Sent by BTS in Immediate Assignment Procedure

per BSC

Meaning

In a TCH immediate assignment procedure, the BSC sends a CHAN ACTIV message to the

BTS. If the BTS returns a CHAN ACTIV NACK message, the TCH activation fails. The BSCmeasures the counter CHAN ACTIV NACK Messages Sent by BTS in Immediate

Assignment Procedure (TCHF) or the counter CHAN ACTIV NACK Messages Sent by BTS

in Immediate Assignment Procedure (TCHH) in the cell where the TCH is located.

This counter contains the counters described previously in all the cells controlled by a BSC.

Trigger Point

None.

Formula

CHAN ACT NACK Messages Sent by BTS in Immediate Assignment Procedure per BSC=

[∑<

=

N i

i 0

CHAN ACTIV NACK Messages Sent by BTS in Assignment Procedure (TCHF)]+

[∑<

=

N i

i 0

CHAN ACTIV NACK Messages Sent by BTS in Assignment Procedure (TCHH)]+

[∑<

=

N i

i 0

CHAN ACTIV NACK Messages Sent by BTS in Mode Modify Procedure (TCHF)]+

[∑<

=

N i

i 0

CHAN ACTIV NACK Messages Sent by BTS in Mode Modify Procedure (TCHH)]

1.5.12 Channel Activation Timeouts in Immediate AssignmentProcedure per BSC

Counter

ZTA3159E: Channel Activation Timeouts in Immediate Assignment Procedure per BSC

Meaning

In the TCH immediate assignment procedure, the BSC sends a CHAN ACTIV message to theBTS and triggers an internal timer. If no CHAN ACTIV ACK message is received within

scheduled time (five seconds by default), the BSC measures the counter Channel Activation

Timeouts in Immediate Assignment Procedure (TCHF) or the counter Channel ActivationTimeouts in Immediate Assignment Procedure (TCHH) in the cell where the TCH is located.






This counter contains the counters described previously in all the cells controlled by a BSC.

Trigger Point

None.

Formula

Channel Activation Timeouts in Immediate Assignment Procedure per BSC= [∑<

=

N i

i 0

Channel

Activation Timeouts in Assignment Procedure (TCHF)]+ [∑<

=

N i

i 0

Channel Activation Timeouts

in Assignment Procedure (TCHH)]+ [∑<

=

N i

i 0

Channel Activation Timeouts in Mode Modify

Procedure (TCHF)]+ [∑<

=

N i

i 0

Channel Activation Timeouts in Mode Modify Procedure (TCHH)]

1.6 Call Drop Measurement per BSC

1.6.1 Overview

Call Drop Measurement per BSC refers to the measurement of call drops in a BSC.

Table 1-6 lists the counters of Call Drop Measurement per BSC.

Table 1-6 Counters of Call Drop Measurement per BSC

Counter Section

ZM318: Successful Connections per BSC (TCHF) (Traffic Channel) 1.6.2

ZM317: Call Drops after Answers per BSC (TCHF) (Traffic Channel) 1.6.3

ZTM328: Call Drops on TCH per BSC (Error Indication) 1.6.4

ZTM329: Call Drops on TCH per BSC (Connection Failure) 1.6.5

ZTM330: Call Drops on TCH per BSC (Release Indication) 1.6.6

ZTM331: Call Drops on TCH per BSC (Abis Terrestrial Link Failure) 1.6.7

ZTM332: Call Drops on TCH per BSC (Forced Handover) 1.6.8

ZTM333: Call Drops on TCH per BSC (Other Causes) 1.6.9



1 BSC Measurement




1.6.2 Successful Connections per BSC (TCHF) (Traffic Channel)

Counter

ZM318: Successful Connections per BSC (TCHF) (Traffic Channel)

Meaning

After a call is set up, the BSC receives the CONN message from the called MS and the

CONN ACK message from the calling MS if the called party answers. The BSC measures thenumber of successful connections.

This counter measures the number of successful connections on the TCHF in all the cells


Trigger Point

None.

Formula

None.

1.6.3 Call Drops after Answers per BSC (TCHF) (Traffic Channel)

Counter

ZM317: Call Drops after Answers per BSC (TCHF) (Traffic Channel)

Meaning

This counter measures the number of call drops after answers in a BSC. The counter measures

only the call drops after the assignment procedure is complete and the MS successfully seizesa TCHF.

Trigger Point

None.

Formula None.

1.6.4 Call Drops on TCH per BSC (Error Indication)

Counter

ZTM328: Call Drops on TCH per BSC (Error Indication)






Meaning

After a call is set up on the TCH, the BTS sends an ERR IND message to the BSC if the radio

link layer incurs errors. Call drops occur on the Um interface.

This counter measures the number of call drops on the TCH in a BSC because the BSCreceives error indications.

Trigger Point

None.

Formula

Call Drops on TCH per BSC (Error Indication) = [∑<

=

N i

i 0

Call Drops due to ERR IND Received

on TCHF (Signaling Channel) in Stable State (T200 Expired)]+ [∑<

=

N i

i 0

Call Drops due to ERR

IND Received on SDCCH (Signaling Channel) in Stable State (Unsolicited DM Response)]+

[∑<

=

N i

i 0

Call Drops due to ERR IND Received on SDCCH (Signaling Channel) in Stable State

(Sequence Error)]+ [∑<

=

N i

i 0

Call Drops due to ERR IND Received on TCHH (Signaling

Channel) in Stable State (T200 Expired)]+ [∑<

=

N i

i 0

Call Drops due to ERR IND Received on

TCHH (Signaling Channel) in Stable State (Unsolicited DM Response)]+ [∑<

=

N i

i 0

Call Drops

due to ERR IND Received on TCHH (Signaling Channel) in Stable State (Sequence Error)]+

[∑<

=

N i

i 0

Call Drops due to ERR IND Received on TCHF (TCH) in Stable State (T200

Expired)]+ [∑<

=

N i

i 0

Call Drops due to ERR IND Received on TCHF (TCH) in Stable State

(Unsolicited DM Response)]+ [∑<

=

N i

i 0

Call Drops due to ERR IND Received on TCHF (TCH)

in Stable State (Sequence Error)]+ [∑<

=

N i

i 0

Call Drops due to ERR IND Received on TCHH

(TCH) in Stable State (T200 Expired)]+ [∑<

=

N i

i 0

Call Drops due to ERR IND Received on

TCHH (TCH) in Stable State (Unsolicited DM Response)]+ [∑<

=

N i

i 0

Call Drops due to ERR

IND Received on TCHH (TCH) in Stable State (Sequence Error)]



1 BSC Measurement




1.6.5 Call Drops on TCH per BSC (Connection Failure)

Counter

ZTM329: Call Drops on TCH per BSC (Connection Failure)

Meaning

After a call is set up on the TCH, the BTS sends a CONN FAIL IND message to the BSC if

the radio link layer incurs errors or if hardware fails. Call drops occur on the Um interface.

This counter measures the number of call drops on the TCH in a BSC because the connectionfails.

Trigger Point

None.

Formula

Call Drops on TCH per BSC (Connection Failure) = [∑<

=

N i

i 0

Call Drops due to CONN FAIL

Received on TCHF (Signaling Channel) in Stable State (Radio Link Failure)]+ [∑<

=

N i

i 0

Call

Drops due to CONN FAIL Received on TCHF (Signaling Channel) in Stable State (HO

Access Failure)]+ [∑<

=

N i

i 0

Call Drops due to CONN FAIL Received on TCHF (Signaling

Channel) in Stable State (OM Intervention)]+ [∑<

=

N i

i 0

Call Drops due to CONN FAIL Received

on TCHF (Signaling Channel) in Stable State (Radio Resource Unavailable)]+ [∑<

=

N i

i 0

Call

Drops due to CONN FAIL Received on TCHF (Signaling Channel) in Stable State (Other

Causes)]+ [∑<

=

N i

i 0

Call Drops due to CONN FAIL Received on TCHH (Signaling Channel) in

Stable State (Radio Link Failure)]+ [∑<

=

N i

i 0

Call Drops due to CONN FAIL Received on TCHH

(Signaling Channel) in Stable State (HO Access Failure)]+ [∑<

=

N i

i 0

Call Drops due to CONN

FAIL Received on TCHH (Signaling Channel) in Stable State (OM Intervention)]+ [∑<

=

N i

i 0

Call

Drops due to CONN FAIL Received on TCHH (Signaling Channel) in Stable State (Radio

Resource Unavailable)]+ [∑<

=

N i

i 0

Call Drops due to CONN FAIL Received on TCHH (Signaling

Channel) in Stable State (Other Causes)]+ [∑<

=

N i

i 0

Call Drops due to CONN FAIL Received on






TCHF (TCH) in Stable State (Radio Link Failure)]+ [∑<

=

N i

i 0


Received on TCHF (TCH) in Stable State (HO Access Failure)]+ [∑<

=

N i

i 0

Call Drops due to

CONN FAIL Received on TCHF (TCH) in Stable State (OM Intervention)]+ [∑<

=

N i

i 0

Call Drops

due to CONN FAIL Received on TCHF (TCH) in Stable State (Radio Resource

Unavailable)]+ [∑<

=

N i

i 0

Call Drops due to CONN FAIL Received on TCHF (TCH) in Stable

State (Other Causes)]+ [∑<

=

N i

i 0

Call Drops due to CONN FAIL Received on TCHH (TCH) in

Stable State (Radio Link Failure)]+ [∑<

=

N i

i0

Call Drops due to CONN FAIL Received on TCHH

(TCH) in Stable State (HO Access Failure)]+ [∑<

=

N i

i 0

Call Drops due to CONN FAIL Received

on TCHH (TCH) in Stable State (OM Intervention)]+ [∑<

=

N i

i 0


Received on TCHH (TCH) in Stable State (Radio Resource Unavailable)]+ [∑<

=

N i

i 0

Call Drops

due to CONN FAIL Received on TCHH (TCH) in Stable State (Other Causes)]

1.6.6 Call Drops on TCH per BSC (Release Indication)

Counter

ZTM330: Call Drops on TCH per BSC (Release Indication)

Meaning

In multiframe link setup state, the BTS sends a REL IND message to the BSC after receiving

a DISC frame from an MS. Call drops occur on the Um interface.

This counter measures the number of call drops on the TCH in a BSC because the BSCreceives release indications.

Trigger Point

None.

Formula

Call Drops on TCH per BSC (Release Indication) = [∑<

=

N i

i 0

Call Drops due to REL IND

Received on TCHF (Signaling Channel)]+ [∑<

=

N i

i0

Call Drops due to REL IND Received on



1 BSC Measurement




TCHF (TCH)]+ [∑<

=

N i

i 0

Call Drops due to REL IND Received on TCHH (Signaling Channel)]+

[∑<

=

N i

i 0

Call Drops due to REL IND Received on TCHH (TCH)]

1.6.7 Call Drops on TCH per BSC (Abis Terrestrial Link Failure)

Counter

ZTM331: Call Drops on TCH per BSC (Abis Terrestrial Link Failure)

Meaning

After a call is set up on the TCH, a call drop occurs on the Um interface if the Abis terrestrial

link incurs an error.

This counter measures the number of call drops because the Abis terrestrial link incurs errors.

Trigger Point

None.

Formula

Call Drops on TCH per BSC (Abis Terrestrial Link Failure) = [∑<

=

N i

i 0

Call Drops due to Abis

Terrestrial Link Failure (TCHF) (Signaling Channel)]+ [∑<

=

N i

i 0

Call Drops due to Abis

Terrestrial Link Failure (TCHF) (TCH)]+ [∑<

=

N i

i 0

Call Drops due to Abis Terrestrial Link

Failure (TCHH) (Signaling Channel)]+ [∑<

=

N i

i 0

Call Drops due to Abis Terrestrial Link Failure

(TCHH) (TCH)]

1.6.8 Call Drops on TCH per BSC (Forced Handover)

Counter

ZTM332: Call Drops on TCH per BSC (Forced Handover)

Meaning

This counter measures the number of call drops on the TCH in a BSC because of forcedhandovers.

Trigger Point

None.






Formula

Call Drops on TCH per BSC (Forced Handover) = [∑<

=

N i

i 0

Call Drops due to Forced Handover

(TCHF) (Signaling Channel)]+ [∑<

=

N i

i 0

Call Drops due to Forced Handover (TCHF) (TCH)]+

[∑<

=

N i

i 0

Call Drops due to Forced Handover (TCHH) (Signaling Channel)]+ [∑<

=

N i

i 0

Call Drops

due to Forced Handover (TCHH) (TCH)]

1.6.9 Call Drops on TCH per BSC (Other Causes)

Counter

ZTM333: Call Drops on TCH per BSC (Other Causes)

Meaning

This counter measures the number of call drops on the TCH in a BSC because of other factors,including no MRs from the MS, equipment failures, and resource check.

Trigger Point

None.

Formula

Call Drops on TCH per BSC (Other Causes) = [∑<

=

N i

i 0

Call Drops due to No MRs from MS for

a Long Time (TCHF) (Signaling Channel)]+ [∑<

=

N i

i 0

Call Drops due to No MRs from MS for a

Long Time (TCHF) (Traffic Channel)]+ [∑<

=

N i

i 0

Call Drops due to No MRs from MS for a Long

Time (TCHH) (Signaling Channel)]+ [∑<

=

N i

i 0

Call Drops due to No MRs from MS for a Long

Time (TCHH) (Traffic Channel)]+ [∑<

=

N i

i 0

Call Drops due to Equipment Failure (TCHF)

(Signaling Channel)]+ [∑<

=

N i

i 0

Call Drops due to Equipment Failure (TCHF) (Traffic

Channel)]+ [∑<

=

N i

i 0

Call Drops due to Equipment Failure (TCHH) (Signaling Channel)]+

[∑<

=

N i

i 0

Call Drops due to Equipment Failure (TCHH) (Traffic Channel)]+ [∑<

=

N i

i 0

Call Drops due



1 BSC Measurement




to Resource Check (TCHF) (Signaling Channel)]+ [∑<

=

N i

i 0

Call Drops due to Resource Check

(TCHH) (Signaling Channel)]+ [∑<

=

N i

i 0

Call Drops due to Resource Check (TCHF) (Traffic

Channel)]+ [∑<

=

N i

i 0

Call Drops due to Resource Check (TCHH) (Traffic Channel)]

1.7 Handover Failure Measurement per BSC

1.7.1 Overview

Handover Failure Measurement per BSC refers to the measurement of handover failures

caused by different factors in a BSC. The handover may occur in a cell, in a BSC, betweenBSCs, or between the 2G system and the 3G system.

Table 1-7 lists the counters of Handover Failure Measurement per BSC.

Table 1-7 Counters of Handover Failure Measurement per BSC

Counter Section

ZCH902C: Failed Reconnections to Old Channels upon Intra-Cell Handover

Failure per BSC

1.7.2

ZCH902D: Successful Reconnections to Old Channels upon Intra-CellHandover Failure per BSC 1.7.3

ZCH912C: Failed Reconnections to Old Channels upon Internal Outgoing Cell

Handover Failure per BSC

1.7.4

ZCH912D: Successful Reconnections to Old Channels upon Internal Outgoing

Cell Handover Failure per BSC

1.7.5

ZCH932C: Failed Reconnections to Old Channels upon External Outgoing CellHandover Failure per BSC

1.7.6

ZCH932D: Successful Reconnections to Old Channels upon External OutgoingCell Handover Failure per BSC

1.7.7

ZH952C: Successful Reconnections to Old Channels upon Inter-RAT Outgoing

Cell Handover Failure per BSC

1.7.8

ZCH952D: Successful Reconnections to Old Channels upon Inter-RAT

Outgoing Cell Handover Failure per BSC

1.7.9

ZH942I: Failed External Incoming Cell Handovers per BSC (Illegal Message) 1.7.10

ZCH942A: Failed External Incoming Cell Handovers per BSC (ChannelUnavailable)

1.7.11

ZH942E: Failed External Incoming Cell Handovers per BSC (Requested

Territorial Resource Unavailable)

1.7.12






Counter Section

ZH942F: Failed External Incoming Cell Handovers per BSC (Territorial

Resource Already Allocated)

1.7.13

ZH942B: Failed External Incoming Cell Handovers per BSC (EquipmentFailure)

1.7.14

ZCH9420C: Failed External Incoming Cell Handovers per BSC (TimerExpired)

1.7.15

ZH942H: Failed External Incoming Cell Handovers per BSC (Other Causes) 1.7.16

ZCR9350B: CHAN ACT NACK Messages Sent by BTS in External IncomingCell Handover Procedure per BSC

1.7.17

ZCR9350C: Channel Activation Timeouts in External Incoming Cell Handover

Procedure per BSC

1.7.18

1.7.2 Failed Reconnections to Old Channels upon Intra-CellHandover Failure per BSC

Counter

ZCH902C: Failed Reconnections to Old Channels upon Intra-Cell Handover Failure per BSC

Meaning

This counter measures the number of failed intra-cell handovers because the timer expires inall the cells controlled by a BSC.

The channel involved in the measurement is of the following types:

SDCCH

TCHF

TCHH

In an intra-cell handover procedure, the BSC sends an HO CMD message to the MS and starts

a timer to wait for an HO CMP message. The measurement is triggered when the timer

expires. The measurement is based on the channel type.

The intra-cell handover is of the following types:

Intra-cell handover requests in normal conditions

Intra-cell handover requests caused by dynamic channel conversion

Intra-cell handover requests in concentric cells

The causes for handover failures are as follows:

Channel unavailable

Terrestrial resource request failed

A-interface failure



1 BSC Measurement




Clear commands sent by MSC

Timer expired

Reconnection to old channels

The dynamic channel conversion is of the following types: TCHF to TCHH

TCHH to TCHF

TCH to SDCCH

SDCCH to TCH

The concentric cell handover is of the following types:

Underlaid subcell to overlaid subcell

Overlaid subcell to underlaid subcell

Along with Internal Intra-Cell Handover Requests per BSC and Internal Intra-Cell Handover

Commands per BSC, the counter shows the performance of intra-cell handovers in a BSC.

Trigger Point

None.

Formula

Failed Reconnections to Old Channels upon Intra-Cell Handover Failure per BSC=∑<

=

N i

i 0

Failed

Internal Intra-Cell Handovers (Timer Expired) (SDCCH)+∑

<

=

N i

i 0Failed Internal Intra-Cell

Handovers (Timer Expired) (TCHF) (Signaling Channel)+∑<

=

N i

i 0

Failed Internal Intra-Cell

Handovers (Timer Expired) (TCHH) (Signaling Channel)+∑<

=

N i

i 0


Handovers (Timer Expired) (TCHF) (Traffic Channel)+∑<

=

N i

i 0


Handovers (Timer Expired) (TCHH) (Traffic Channel)

1.7.3 Successful Reconnections to Old Channels upon Intra-CellHandover Failure per BSC

Counter

ZCH902D: Successful Reconnections to Old Channels upon Intra-Cell Handover Failure perBSC

Meaning

This counter measures the number of successful reconnections to old channels after the intra-

cell handover fails.







SDCCH

TCHF

TCHHIn an intra-cell handover procedure, the BSC sends an HO CMD message to the MS and starts

a timer to wait for an HO CMP message. If the MS reconnects to the old channel and reports ahandover failure message on the old channel before the timer expires, the BSC measures thenumber of successful reconnections to old channels based on the cause carried in the message.

The cause carried in the HO FAIL message may be one of the following:

Abnormal release, unspecified

Abnormal release, channel unacceptable

Abnormal release, timer expired

Abnormal release, no activity on the radio path

Preemptive release

Handover impossible, timing advance out of range

Channel mode unavailable

Frequency not implemented

Call already cleared

Semantically incorrect message

Invalid mandatory information

Message type non-existent or not implemented

Message type not compatible with protocol state

Conditional IE error)

No cell allocation available

Protocol error unspecified

Other

Trigger Point

None.

Formula

Successful Reconnections to Old Channels upon Intra-Cell Handover Failure per BSC =∑<

=

N i

i 0

Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Abnormal Release,

Unspecified)+∑<

=

N i

i 0

Failed Internal Intra-Cell Handovers (Reconnection to Old Channels)

(Abnormal Release, Channel Unacceptable)+∑<

=

N i

i 0

Failed Internal Intra-Cell Handovers

(Reconnection to Old Channels) (Abnormal Release, Timer Expired)+∑<

=

N i

i 0

Failed Internal

Intra-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, No Activity on the



1 BSC Measurement




Radio Path)+∑<

=

N i

i 0


(Preemptive Release)+∑<

=

N i

i 0

Failed Internal Intra-Cell Handovers (Reconnection to Old

Channels) (Handover Failed, Timing Advance out of Range)+∑<

=

N i

i 0


Handovers (Reconnection to Old Channels) (Channel Mode Unavailable)+∑<

=

N i

i 0

Failed Internal

Intra-Cell Handovers (Reconnection to Old Channels) (Frequency Unavailable)+∑<

=

N i

i 0

Failed

Internal Intra-Cell Handovers (Reconnection to Old Channels) (Call Already Cleared)+∑<

=

N i

i 0

Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Semantically Incorrect

Message)+∑<

=

N i

i 0

Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Invalid

Mandatory Information)+∑<

=

N i

i 0


Channels) (Message Type Non-existent or Not Implemented)+∑<

=

N i

i 0


Handovers (Reconnection to Old Channels) (Message Type Not Compatible with Protocol

State)+∑<

=

N i

i 0


(Conditional IE Error)+∑<

=

N i

i 0


Channels) (No Cell Allocation Available)+∑<

=

N i

i 0


(Reconnection to Old Channels) (Protocol Error Unspecified)+∑<

=

N i

i 0


Handovers (Reconnection to Old Channels) (Other Causes)

1.7.4 Failed Reconnections to Old Channels upon Internal

Outgoing Cell Handover Failure per BSC

Counter

ZCH912C: Failed Reconnections to Old Channels upon Internal Outgoing Cell Handover

Failure per BSC

Meaning

This counter measures the number of failed internal outgoing cell handovers because the timer

expires in all the cells controlled by a BSC.







SDCCH

TCHF

TCHH

In an internal outgoing cell handover procedure (including directed retry), the BSC measuresthis counter if the no HO CMP message is received within scheduled time. The measurement

is based on the channel type and the crossing of frequency bands in the source cell.

The crossing of frequency bands is of the following types:

900/850 to 900/850

1800/1900 to 1800/1900

900/850 to 1800/1900

1800/1900 to 900/850

Trigger Point

None.

Formula

Failed Reconnections to Old Channels upon Internal Outgoing Cell Handover Failure per

BSC=∑<

=

N i

i 0

Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (SDCCH)

(Excluding Directed Retry)+∑<

=

N i

i 0

Failed Outgoing Internal Inter-Cell Handovers (Timer

Expired) (TCHF) (Signaling Channel)+∑

<

=

N i

i 0

Failed Outgoing Internal Inter-Cell Handovers

(Timer Expired) (TCHH) (Signaling Channel)+∑<

=

N i

i 0

Failed Outgoing Internal Inter-Cell


=

N i

i 0

Failed Outgoing Internal Inter-

Cell Handovers (Timer Expired) (TCHH) (Traffic Channel)+∑<

=

N i

i 0

Failed Outgoing Internal

Inter-Cell Handovers (Timer Expired) (Directed Retry)

1.7.5 Successful Reconnections to Old Channels upon InternalOutgoing Cell Handover Failure per BSC

Counter

ZCH912D: Successful Reconnections to Old Channels upon Internal Outgoing Cell Handover

Failure per BSC

Meaning

This counter measures the number of successful reconnections to old channels after the

internal outgoing cell handover fails in all the cells controlled by a BSC.



1 BSC Measurement




In an internal outgoing cell handover procedure, the BSC sends an HO CMD message in thesource cell to the MS and starts a timer to wait for an HO CMP message. If the MS reconnectsto the old channel and reports a HO FAIL message on the old channel before the timer expires,

the BSC measures the number of successful reconnections to old channels based on the causecarried in the message.


900/850 to 900/850

1800/1900 to 1800/1900

900/850 to 1800/1900

1800/1900 to 900/850

The cause carried in the HO FAIL message may be one of the following:





Preemptive release







Message type non-existent or not implemented Message type not compatible with protocol state

Conditional IE error



Other

Trigger Point

None.

Formula

Successful Reconnections to Old Channels upon Internal Outgoing Cell Handover Failure per

BSC=∑<

=

N i

i 0

Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels)

(Abnormal Release, Unspecified)+∑<

=

N i

i 0


(Reconnection to Old Channels) (Abnormal Release, Channel Unacceptable)+∑<

=

N i

i 0

Failed

Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal Release,






Timer Expired)+∑<

=

N i

i 0

Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old

Channels) (Abnormal Release, No Activity on the Radio Path)+∑<

=

N i

i 0


Inter-Cell Handovers (Reconnection to Old Channels) (Preemptive Release)+∑<

=

N i

i 0

Failed

Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Handover Failed,

Timing Advance out of Range)+∑<

=

N i

i 0


(Reconnection to Old Channels) (Channel Mode Unavailable)+∑<

=

N i

i 0


Inter-Cell Handovers (Reconnection to Old Channels) (Frequency Unavailable)+∑<

=

N i

i0

Failed

Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Call Already

Cleared)+∑<

=

N i

i 0

Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels)

(Semantically Incorrect Message)+∑<

=

N i

i 0


(Reconnection to Old Channels) (Invalid Mandatory Information)+∑<

=

N i

i 0

Failed Outgoing

Internal Inter-Cell Handovers (Reconnection to Old Channels) (Message Type Non-existent or

Not Implemented)+∑

<

=

N i

i 0Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old

Channels) (Message Type Not Compatible with Protocol State)+∑<

=

N i

i 0


Inter-Cell Handovers (Reconnection to Old Channels) (Conditional IE Error)+∑<

=

N i

i 0

Failed

Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (No Cell Allocation

Available)+∑<

=

N i

i 0

Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old

Channels) (Protocol Error Unspecified)+

∑

<

=

N i

i 0


(Reconnection to Old Channels) (Other Causes)

1.7.6 Failed Reconnections to Old Channels upon ExternalOutgoing Cell Handover Failure per BSC

Counter

ZCH912C: Failed Reconnections to Old Channels upon External Outgoing Cell Handover

Failure per BSC



1 BSC Measurement




Meaning

This counter measures the number of failed reconnections to old channels after the external

outgoing cell handover fails because the timer T8 expires.


SDCCH

TCHF

TCHH

In an external outgoing cell handover procedure, the source BSC sends a HO CMD message

in the source cell to the MS and then triggers the timer T8 to wait for the CLR CMD messagefrom the MSC.

Along with External Outgoing Cell Handover Requests per BSC and External Outgoing Cell

Handover Commands per BSC, this counter shows the performance of external outgoing cellhandovers in a BSC. Along with the counters related to external incoming cell handovers, this

counter shows the performance of cell handovers between BSCs.


900/850 to 900/850

1800/1900 to 1800/1900

900/850 to 1800/1900

1800/1900 to 900/850

The external outgoing cell handover also occurs during the handover between different

signaling points in a BSC.

Trigger Point

None.

Formula

Failed Reconnections to Old Channels upon Internal Outgoing Cell Handover Failure per

BSC=∑<

=

N i

i 0

Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (SDCCH)

(Excluding Directed Retry)+∑<

=

N i

i 0

Failed Outgoing Internal Inter-Cell Handovers (Timer

Expired) (TCHF) (Signaling Channel)+∑<

=

N i

i 0


(Timer Expired) (TCHH) (Signaling Channel)+∑<

=

N i

i 0

Failed Outgoing Internal Inter-Cell


=

N i

i 0

Failed Outgoing Internal Inter-

Cell Handovers (Timer Expired) (TCHH) (Traffic Channel)+∑<

=

N i

i 0


Inter-Cell Handovers (Timer Expired) (Directed Retry)






1.7.7 Successful Reconnections to Old Channels upon ExternalOutgoing Cell Handover Failure per BSC

CounterZCH932D: Successful Reconnections to Old Channels upon External Outgoing Cell


Meaning

This counter measures the number of successful reconnections to old channels after the

external outgoing cell handover fails.


SDCCH

TCHF

TCHH

In an external outgoing cell handover procedure, the BSC sends an HO CMD message in thesource cell to the MS and starts a timer to wait for an HO CMP message. If the MS reconnects

to the old channel and reports an HO FAIL message on the old channel before the timerexpires, the BSC measures the number of successful reconnections to old channels in the

target cell. The measurement is based on the cause carried in the message.


900/850 to 900/850

1800/1900 to 1800/1900 900/850 to 1800/1900

1800/1900 to 900/850



The cause carried in the message may be one of the following:




Abnormal release, no activity on the radio path Preemptive release











1 BSC Measurement







Other

Trigger Point

None.

Formula

Successful Reconnections to Old Channels upon External Outgoing Cell Handover Failure per

BSC=∑<

=

N i

i 0

Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels)

(Abnormal Release, Unspecified)+∑

<

=

N i

i 0Failed Outgoing External Inter-Cell Handovers

(Reconnection to Old Channels) (Abnormal Release, Channel Unacceptable)+∑<

=

N i

i 0

Failed

Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal Release,

Timer Expired)+∑<

=

N i

i 0

Failed Outgoing External Inter-Cell Handovers (Reconnection to Old

Channels) (Abnormal Release, No Activity on the Radio Path)+∑<

=

N i

i 0

Failed Outgoing External

Inter-Cell Handovers (Reconnection to Old Channels) (Preemptive Release)+∑

<

=

N i

i 0Failed

Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Handover Failed,

Timing Advance out of Range)+∑<

=

N i

i 0

Failed Outgoing External Inter-Cell Handovers


=

N i

i 0


Inter-Cell Handovers (Reconnection to Old Channels) (Frequency Unavailable)+∑<

=

N i

i 0

Failed

Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Call Already

Cleared)+∑<

=

N i

i 0


(Semantically Incorrect Message)+∑<

=

N i

i 0


(Reconnection to Old Channels) (Invalid Mandatory Information)+∑<

=

N i

i 0

Failed Outgoing

External Inter-Cell Handovers (Reconnection to Old Channels) (Message Type Non-existent

or Not Implemented)+∑<

=

N i

i 0

Failed Outgoing External Inter-Cell Handovers (Reconnection to






Old Channels) (Message Type Not Compatible with Protocol State)+∑<

=

N i

i 0

Failed Outgoing

External Inter-Cell Handovers (Reconnection to Old Channels) (Conditional IE Error)+∑<

=

N i

i 0

Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (No Cell

Allocation Available)+∑<

=

N i

i 0

Failed Outgoing External Inter-Cell Handovers (Reconnection to

Old Channels) (Protocol Error Unspecified)+∑<

=

N i

i 0

Failed Outgoing External Inter-Cell

Handovers (Reconnection to Old Channels) (Other Causes)

1.7.8 Failed Reconnections to Old Channels upon Inter-RATOutgoing Cell Handover Failure per BSC

Counter

ZH952C: Failed Reconnections to Old Channels upon Inter-RAT Outgoing Cell Handover

Failure per BSC

Meaning

This counter measures the number of failed reconnections to old channels after the inter-RAT

outgoing cell handover fails because the timer T8 expires.


SDCCH

TCHF

TCHH

In an inter-RAT outgoing cell handover procedure (including directed retry), the BSC

measures this counter if the handover fails because the BSC receives no CLR CMD messagefrom the MSC within scheduled time (T8 expires).


900/850 to 900/850

1800/1900 to 1800/1900

900/850 to 1800/1900

1800/1900 to 900/850



Trigger Point

None.



1 BSC Measurement




Formula

Failed Reconnections to Old Channels upon Inter-RAT Outgoing Cell Handover Failure per

BSC＝∑<

=

N i

i 0

Failed Outgoing Inter-RAT Inter-Cell Handovers (T8 Expired)

This counter is the sum of the predefined counter Failed Outgoing Inter-RAT Inter-Cell

Handovers (T8 Expired) in all the cells controlled by a BSC.

1.7.9 Successful Reconnections to Old Channels upon Inter-RATOutgoing Cell Handover Failure per BSC

Counter

ZCH952D: Successful Reconnections to Old Channels upon Inter-RAT Outgoing Cell


Meaning

This counter measures the number of successful reconnections to old channels after the inter-

RAT outgoing cell handover fails.


SDCCH

TCHF

TCHH

In an inter-RAT outgoing cell handover procedure (excluding directed retry), the MS sends anHO FAIL message in the source cell to the source BSC if the MS fails to access the target celland successfully reconnects to the old channel in the source cell. The BSC measures thenumber of successful reconnections to old channels based on the RR cause carried in the HO

FAIL message.

The RR cause carried in the message may be one of the following:





Preemptive release

















Other

Trigger Point

None.

Formula

Successful Reconnections to Old Channels upon Inter-RAT Handover Failure per BSC=∑<

=

N i

i 0

Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal

Release, Unspecified)+∑<

=

N i

i 0

Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection

to Old Channels) (Abnormal Release, Channel Unacceptable)+∑<

=

N i

i 0

Failed Outgoing Inter-

RAT Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, Timer

Expired)+∑<

=

N i

i 0

Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old

Channels) (Abnormal Release, No Activity on the Radio Path))+∑<

=

N i

i 0


RAT Inter-Cell Handovers (Reconnection to Old Channels) (Preemptive Release) +∑<

=

N i

i 0

Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Handover

Failed, Timing Advance out of Range) +∑<

=

N i

i 0

Failed Outgoing Inter-RAT Inter-Cell Handovers


=

N i

i 0


RAT Inter-Cell Handovers (Reconnection to Old Channels) (Frequency

Unavailable)+∑<

=

N i

i 0


Channels) (Call Already Cleared)+

∑

<

=

N i

i 0


(Reconnection to Old Channels) (Semantically Incorrect Message)+∑<

=

N i

i 0

Failed Outgoing

Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Invalid Mandatory

Information)+∑<

=

N i

i 0


Channels) (Message Type Non-existent or Not Implemented)+∑<

=

N i

i 0


RAT Inter-Cell Handovers (Reconnection to Old Channels) (Message Type Not Compatible



1 BSC Measurement




with Protocol State)+∑<

=

N i

i 0

Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to

Old Channels) (Conditional IE Error)+∑<

=

N i

i 0


(Reconnection to Old Channels) (No Cell Allocation Available)+∑<

=

N i

i 0


RAT Inter-Cell Handovers (Reconnection to Old Channels) (Protocol Error

Unspecified)+∑<

=

N i

i 0


Channels) (Other Causes)

1.7.10 Failed External Incoming Cell Handovers per BSC (IllegalMessage)

Counter

ZH942I: Failed External Incoming Cell Handovers per BSC (Illegal Message)

Meaning

This counter measures the number of failed external incoming cell handovers caused by

illegal messages in all the cells controlled by a BSC. In an external incoming cell handover procedure, the target BSC receives an HO REQ message from the MSC and decodes themessage. When finding out that the message is not compliant with the protocol requirements

during the decoding, the BSC measures the number of failed external incoming cell handovers

based on the channel type, the crossing of frequency bands, and the failure cause.

The channel involved in the measurement may be an SDCCH or a TCH. The TCH may be a

traffic channel or a signaling channel.


900/850 to 900/850

1800/1900 to 1800/1900

900/850 to 1800/1900

1800/1900 to 900/850

Along with External Incoming Cell Handover Requests per BSC and External Incoming CellHandover Commands per BSC, the counter shows the performance of external incoming cell

handovers. Along with the counters related to external outgoing cell handovers, the countershows the performance of the cell handovers between BSCs.

Trigger Point

None.

Formula

None.






1.7.11 Failed External Incoming Cell Handovers per BSC (ChannelUnavailable)

CounterZCH942A: Failed External Incoming Cell Handovers per BSC (Channel Unavailable)

Meaning

This counter measures the number of failed external incoming cell handovers because no

channel is available in all the cells controlled by a BSC. In an external incoming cell handover procedure, the target BSC receives an HO REQ message from the MSC and decodes themessage. After successfully decoding the message, the BSC requests a channel from the target

cell. If the target cell returns a channel request failure message with the cause of channel

unavailable in it, the BSC measures the number of failed external incoming cell handovers

based on the channel type. The channel involved in the measurement may be an SDCCH or aTCH.


900/850 to 900/850

1800/1900 to 1800/1900

900/850 to 1800/1900

1800/1900 to 900/850

Along with External Incoming Cell Handover Requests per BSC and External Incoming Cell

Handover Commands per BSC, the counter shows the performance of external incoming cellhandovers. Along with the counters related to the external outgoing cell handovers, the

counter shows the performance of cell handovers between BSCs.

Trigger Point

None.

Formula

Failed External Incoming Cell Handovers per BSC (Channel Unavailable)=∑<

=

N i

i 0

Failed

Incoming External Inter-Cell Handovers (No Channel Available) (SDCCH)]+ ∑

<

=

N i

i 0Failed

Incoming External Inter-Cell Handovers (No Channel Available) (TCH)

1.7.12 Failed External Incoming Cell Handovers per BSC(Requested Terrestrial Resource Unavailable)

Counter

ZH942E: Failed External Incoming Cell Handovers per BSC (Requested Terrestrial Resource

Unavailable)



1 BSC Measurement




Meaning

This counter measures the number of failed external incoming cell handovers because the

requested terrestrial resources is unavailable in all the cells controlled by a BSC. The

measurement is performed in the target cell based on channel type and the crossing of

frequency bands.

The target BSC receives an HO REQ message from the MSC and decodes it. The target BSC

then requests a channel from the target cell. If the request is successful, the target BSC sends aCHAN ACTIV message to the target cell. After receiving a CHAN ACTIV ACK message, the

target BSC requests the terrestrial resources and terrestrial link resources about speechservices.

The CIC resources on the A interface is a key factor of the terrestrial resource request. The

MSC sends the target BSC an HO REQ message that carries the CIC. If the target BSCdetects that the CIC is unavailable, the BSC measures the counter Failed External Incoming

Cell Handovers per BSC (Requested Terrestrial Resource Unavailable).

The channel involved in the measurement may be an SDCCH or a TCH. The TCH may be atraffic channel or a signaling channel.


900/850 to 900/850

1800/1900 to 1800/1900

900/850 to 1800/1900

1800/1900 to 900/850

The external incoming cell handover also occurs during the handover between differentsignaling points in a BSC.

Trigger Point

None.

Formula

Failed External Incoming Cell Handovers per BSC (Requested Terrestrial Resource

Unavailable)＝∑<

=

N i

i 0

Failed Incoming External Inter-Cell Handovers (CIC Unavailable)

This counter is the sum of the predefined counter Failed Incoming External Inter-Cell

Handovers (CIC Unavailable) in all the cells controlled by a BSC.

1.7.13 Failed External Incoming Cell Handovers per BSC(Terrestrial Resource Already Allocated)

Counter

ZH942F: Failed External Incoming Cell Handovers per BSC (Terrestrial Resource Already

Allocated)






Meaning


terrestrial resources is already allocated in all the cells controlled by a BSC. The measurement

is performed in the target cell based on channel type and the crossing of frequency bands.

The target BSC receives an HO REQ message from the MSC and decodes it. The target BSCthen requests a channel from the target cell. If the request is successful, the target BSC sends a

CHAN ACTIV message to the target cell. After receiving a CHAN ACTIV ACK message, thetarget BSC requests the terrestrial resources and terrestrial link resources about speech

services.

The CIC resources on the A interface is a key factor of the terrestrial resource request. TheMSC sends the target BSC an HO REQ message that carries the CIC. If the target BSC

detects that the CIC is already allocated, the BSC measures the counter Failed ExternalIncoming Cell Handovers per BSC (Terrestrial Resource Already Allocated).




900/850 to 900/850

1800/1900 to 1800/1900

900/850 to 1800/1900

1800/1900 to 900/850

The external incoming cell handover also occurs during the handover between different


Trigger Point None.

Formula

Failed External Incoming Cell Handovers per BSC (Terrestrial Resource Already Allocated)

＝∑<

=

N i

i 0

Failed Incoming External Inter-Cell Handovers (CIC Allocated)

This counter is the sum of the predefined counter Failed Incoming External Inter-Cell

Handovers (CIC Allocated) in all the cells controlled by a BSC.

1.7.14 Failed External Incoming Cell Handovers per BSC(Equipment Failure)

Counter

ZH942B: Failed External Incoming Cell Handovers per BSC (Equipment Failure)



1 BSC Measurement




Meaning

This counter measures the number of failed external incoming cell handovers caused by the

equipment failure in all the cells controlled by a BSC. The measurement is performed in the

target cell based on channel type and the crossing of frequency bands.

The target BSC receives an HO REQ message from the MSC and decodes it. The target BSCthen requests a channel from the target cell. If the request is successful, the target BSC sends a

CHAN ACTIV message to the target cell. After receiving a CHAN ACTIV ACK message, thetarget BSC requests the terrestrial resources and terrestrial link resources about speech

services. If the request fails, the BSC measures the counter Failed External Incoming CellHandovers per BSC (Equipment Failure).




900/850 to 900/850 1800/1900 to 1800/1900

900/850 to 1800/1900

1800/1900 to 900/850

The external incoming cell handover also occurs during the handover between different


Trigger Point

None.

Formula

Failed External Incoming Cell Handovers per BSC (Equipment Failure)＝∑<

=

N i

i 0

Failed

Incoming External Inter-Cell Handovers (Terrestrial Resource Request Failed)

This counter is the sum of the predefined counter Failed Incoming External Inter-CellHandovers (Terrestrial Resource Request Failed) in all the cells controlled by a BSC.

1.7.15 Failed External Incoming Cell Handovers per BSC (TimerExpired)

Counter

ZCH9420C: Failed External Incoming Cell Handovers per BSC (Timer Expired)

Meaning


timer expires in all the cells controlled by a BSC.

In an external incoming cell handover procedure, the target BSC measures this counter in the

target cell based on the channel type and the TCH service type if the target BSC receives no

HO CMP message within scheduled time.








900/850 to 900/850 1800/1900 to 1800/1900

900/850 to 1800/1900

1800/1900 to 900/850

Along with External Incoming Cell Handover Requests per BSC and External Incoming Cell

Handover Commands per BSC, the counter shows the performance of external incoming cell

handovers. Along with the counters related to the external outgoing cell handovers, thecounter shows the performance of cell handovers between BSCs.

Trigger Point

None.

Formula

Failed External Incoming Cell Handovers per BSC (Timer Expired)=∑<

=

N i

i 0

Failed Incoming

External Inter-Cell Handovers (Timer Expired) (SDCCH)+∑<

=

N i

i 0

Failed Incoming External

Inter-Cell Handovers (Timer Expired) (TCH) (Signaling Channel)+∑<

=

N i

i 0

Failed Incoming

External Inter-Cell Handovers (Timer Expired) (TCH) (Traffic Channel)

1.7.16 Failed External Incoming Cell Handovers per BSC (OtherCauses)

Counter

ZH942H: Failed External Incoming Cell Handovers per BSC (Other Causes)

Meaning

This counter measures the number of failed external incoming cell handovers caused by the

CLR CMD message received from the MSC in all the cells controlled by a BSC.

In an external incoming cell handover procedure, this counter is measured when the handover

fails because the target BSC receives a CLR CMD message from the MSC.

Along with External Incoming Cell Handover Requests per BSC and External Incoming CellHandover Commands per BSC, the counter shows the performance of external incoming cell

handovers. Along with the counters related to the external outgoing cell handovers, thecounter shows the performance of cell handovers between BSCs.



1 BSC Measurement




Trigger Point

None.

Formula

Failed External Incoming Cell Handovers per BSC (Other Causes)＝∑<

=

N i

i 0

Failed Incoming

External Inter-Cell Handovers (Clear Commands Sent By MSC)

This counter is the sum of the predefined counter Failed Incoming External Inter-CellHandovers (Clear Commands Sent By MSC) in all the cells controlled by a BSC.

1.7.17 CHAN ACT NACK Messages Sent by BTS in ExternalIncoming Cell Handover Procedure per BSC

Counter

ZCR9350B: CHAN ACT NACK Messages Sent by BTS in External Incoming Cell Handover

Procedure per BSC

Meaning

This counter measures the number of CHAN ACT NACK messages sent by the BTS in the

external incoming cell handover procedure in all the cells controlled by a BSC.

In an external incoming cell handover procedure, the target BSC sends a CHAN ACTIVmessage to a BTS. If the BTS returns a CHAN ACTIV NACK message, the handover fails.

The BSC measures this counter in the target cell. The measurement is based on the channeltype. The channel involved in the measurement may be an SDCCH or a TCH. The TCH may be a traffic channel or a signaling channel.

Trigger Point

None.

Formula

CHAN ACT NACK Messages Sent by BTS in External Incoming Cell Handover Procedure

per BSC =∑<

=

N i

i 0

CHAN ACT NACK Messages Sent by BTS in External Incoming Cell

Handover Procedure per BSC(SDCCH) +∑<

=

N i

i 0

CHAN ACT NACK Messages Sent by BTS in

External Incoming Cell Handover Procedure per BSC(TCHF) +∑<

=

N i

i 0

CHAN ACT NACK

Messages Sent by BTS in External Incoming Cell Handover Procedure per BSC (TCHH)






1.7.18 Channel Activation Timeouts in External Incoming CellHandover Procedure per BSC

CounterZCR9350C: Channel Activation Timeouts in External Incoming Cell Handover Procedure per

BSC

Meaning

This counter measures the number of channel activation timeouts in the external incoming cell

handover procedure in all the cells controlled by a BSC.

In an external incoming cell SDCCH handover procedure, the BSC sends a CHAN ACTIV

message to a BTS. If the BTS returns a CHAN ACTIV NACK message, the handover fails.The BSC measures this counter in the target cell. The measurement is based on the channel

type.


Trigger Point

None.

Formula

CHAN ACT NACK Messages Sent by BTS in External Incoming Cell Handover Procedure

per BSC=∑<

=

N i

i 0

Channel Activation Timeouts in Incoming External Inter-Cell Handover

Procedure (SDCCH)+∑<

=

N i

i 0

Channel Activation Timeouts in Incoming External Inter-Cell

Handover Procedure (TCHF)+∑<

=

N i

i 0

Channel Activation Timeouts in Incoming External Inter-

Cell Handover Procedure (TCHH)

1.8 Handover Attempt Measurement per BSC1.8.1 Overview

Handover Attempt Measurement per BSC measures the number of handover attempts due to

all reasons per BSC.

Table 1-8 lists the counters of Handover Attempt Measurement per BSC.



1 BSC Measurement




Table 1-8 Counters of Handover Attempt Measurement per BSC

Counter Section

ZCH970A: Attempted Handovers per BSC (Uplink Signal Quality) 1.8.2

ZCH970B: Attempted Handovers per BSC (Downlink Signal Quality) 1.8.3

ZCH970C: Attempted Handovers per BSC (Uplink Signal Strength) 1.8.4

ZCH970D: Attempted Handovers per BSC (Downlink Signal Strength) 1.8.5

ZCH970E: Attempted Handovers per BSC (Timing Advance) 1.8.6

ZCH970F: Attempted Handovers per BSC (Better Cell) 1.8.7

ZCH970G: Attempted Handovers per BSC (Load) 1.8.8

ZCH970H: Attempted Handovers per BSC (Rapid Level Drop) 1.8.9

ZCH970I: Attempted Handovers per BSC (MSC Intervention) 1.8.10

ZCH970J: Attempted Handovers per BSC (OM Intervention) 1.8.11

ZCH970L: Attempted Handovers per BSC (Other Causes) 1.8.12

ZCH971J: Attempted Handovers per BSC (Underlaid Subcell to Overlaid

Subcell)

1.8.13

ZCH971L: Attempted Handovers per BSC (Overlaid Subcell to UnderlaidSubcell)

1.8.14

ZCH9005: Attempted Handovers per BSC (Intra-Cell TCHF-to-TCHH

Handover)

1.8.15

ZCH9701: Attempted Handovers per BSC (Directed Retry) 1.8.16

1.8.2 Attempted Handovers per BSC (Uplink Signal Quality)

Counter

ZCH970A: Attempted Handovers per BSC (Uplink Signal Quality)

Meaning

This counter measures the number of attempted outgoing cell handovers per BSC (uplinksignal quality).

The BSC decides whether to initiate a handover based on the MR and the handover algorithm.

If the source cell and the object cell are controlled by one BSC, the BSC will initiate aninternal inter-cell handover.

If the source cell and the object cell are controlled by different BSCs, the BSC will initiate an

external inter-cell handover.

This counter is measured when the handover cause is uplink signal quality.






Trigger Point

None.

Formula

Attempted Handovers per BSC (Uplink Signal Quality)=∑<

=

N i

i 0

Outgoing Internal Inter-Cell

Handover Requests (Uplink Quality)]+ ∑<

=

N i

i 0

Outgoing External Inter-Cell Handover Requests

(Uplink Quality)

1.8.3 Attempted Handovers per BSC (Downlink Signal Quality)

CounterZCH970B: Attempted Handovers per BSC (Downlink Signal Quality)

Meaning

This counter measures the number of attempted outgoing cell handovers per BSC (downlink

signal quality).


If the source cell and the object cell are controlled by one BSC, the BSC will initiate an

internal inter-cell handover.

If the source cell and the object cell are controlled by different BSCs, the BSC will initiate anexternal inter-cell handover.

This counter is measured when the handover cause is downlink signal quality.

Trigger Point

None.

Formula

Attempted Handovers per BSC (Downlink Signal Quality)=∑

<

=

N i

i 0Outgoing Internal Inter-Cell

Handover Requests (Downlink Quality)]+∑<

=

N i

i 0

Outgoing External Inter-Cell Handover

Requests (Downlink Quality)

1.8.4 Attempted Handovers per BSC (Uplink Signal Strength)

Counter

ZCH970C: Attempted Handovers per BSC (Uplink Signal Strength)



1 BSC Measurement




Meaning

This counter measures the number of attempted outgoing cell handovers per BSC (uplink

signal strength).





This counter is measured when the handover cause is uplink signal quality.

Trigger Point

None.

Formula

Attempted Handovers per BSC (Uplink Signal Strength) =∑<

=

N i

i 0


Handover Requests (Uplink Strength)]+∑<

=

N i

i 0


(Uplink Strength)

1.8.5 Attempted Handovers per BSC (Downlink Signal Strength)

Counter

ZCH970D: Attempted Handovers per BSC (Downlink Signal Strength)

Meaning

This counter measures the number of attempted outgoing cell handovers per BSC (downlink

signal strength).

The BSC decides whether to initiate a handover based on the measurement report and the

handover algorithm.

If the source cell and the object cell are controlled by one BSC, the internal incoming cellhandover is initiated.


This counter is measured when the handover cause is downlink signal strength.

Trigger Point

None.






Formula

Attempted Handovers per BSC (Downlink Signal Strength) =∑<

=

N i

i 0

Outgoing Internal Inter-

Cell Handover Requests (Downlink Strength)]+∑<

=

N i

i 0


Requests (Downlink Strength)

1.8.6 Attempted Handovers per BSC (Timing Advance)

Counter

ZCH970E: Attempted Handovers per BSC (Timing Advance)

MeaningThis counter measures the number of attempted outgoing cell handovers per BSC (timing

advance).






This counter is measured when the handover cause is timing advance.

Trigger Point

None.

Formula

Attempted Handovers per BSC (Timing Advance)=∑<

=

N i

i 0


Handover Requests (Timing Advance)]+∑<

=

N i

i 0


(Timing Advance)

1.8.7 Attempted Handovers per BSC (Better Cell)

Counter

ZCH970F: Attempted Handovers per BSC (Better Cell)

Meaning

This counter measures the number of attempted outgoing cell handovers per BSC (better cell).




1 BSC Measurement







This counter is measured when the handover cause is better cell.

Trigger Point

None.

Formula

Attempted Handovers per BSC (Better Cell)=∑<

=

N i

i 0

Outgoing Internal Inter-Cell Handover

Requests (Better Cell)]+∑<

=

N i

i 0

Outgoing External Inter-Cell Handover Requests (Better Cell)

1.8.8 Attempted Handovers per BSC (Load)

Counter

ZCH970G: Attempted Handovers per BSC (Load)

Meaning

This counter measures the number of attempted outgoing cell handovers per BSC (load).





This counter is measured when the handover cause is load.

Trigger Point

None.

Formula

Attempted Handovers per BSC (Load)=∑<

=

N i

i 0

Outgoing Internal Inter-Cell Handover Requests

(Load)+ ∑<

=

N i

i 0

Outgoing External Inter-Cell Handover Requests (Load)






1.8.9 Attempted Handovers per BSC (Rapid Level Drop)

Counter

ZCH970H: Attempted Handovers per BSC (Rapid Level Drop)

Meaning

This counter measures the number of attempted outgoing cell handovers per BSC (rapid level

drop).





This counter is measured when the handover cause is rapid level drop.

Trigger Point

None.

Formula

Attempted Handovers per BSC (Rapid Level Drop)=∑<

=

N i

i 0


Handover Requests (Rapid Level Drop)]+∑<

=

N i

i 0


Requests (Rapid Level Drop)

1.8.10 Attempted Handovers per BSC (MSC Intervention)

Counter

ZCH970I: Attempted Handovers per BSC (MSC Intervention)

MeaningThis counter measures the number of attempted outgoing cell handovers per BSC (MSC

intervention).




This counter is measured when the handover cause is MSC intervention.



1 BSC Measurement




Trigger Point

None.

Formula

Attempted Handovers per BSC (MSC Intervention)=∑<

=

N i

i 0


Handover Requests (MSC Intervention)]+∑<

=

N i

i 0


Requests (MSC Intervention)

1.8.11 Attempted Handovers per BSC (OM Intervention)

CounterZCH970J: Attempted Handovers per BSC (OM Intervention)

Meaning

This counter measures the number of attempted outgoing cell handovers per BSC (OM

intervention).





This counter is measured when the handover cause is OM intervention.

Trigger Point

None.

Formula

Attempted Handovers per BSC (OM Intervention)=∑

<

=

N i

i 0Outgoing Internal Inter-Cell

Handover Requests (OM Intervention)]+∑<

=

N i

i 0


Requests (OM Intervention)

1.8.12 Attempted Handovers per BSC (Other Causes)

Counter

ZCH970L: Attempted Handovers per BSC (Other Causes)






Meaning

This counter measures the number of attempted outgoing cell handovers per BSC (other

causes).





This counter is measured when the handover causes are other causes.

Trigger Point

None.

Formula

Attempted Handovers per BSC (Other Causes)=∑<

=

N i

i 0


Requests (Other Causes)]+∑<

=

N i

i 0

Outgoing External Inter-Cell Handover Requests (Other

Causes)

1.8.13 Attempted Handovers per BSC (Underlaid Subcell to

Overlaid Subcell)

Counter

ZCH971J: Attempted Handovers per BSC (Underlaid Subcell to Overlaid Subcell)

Meaning

This counter measures the number of attempted handovers per BSC (underlaid subcell to

overlaid subcell).

This counter indicates the frequency of attempted handovers per BSC (underlaid subcell to

overlaid subcell). You can know the handover performance by referring to Internal Intra-CellHandover Commands per BSC and Successful Internal Intra-Cell Handovers per BSC.

The BSC selects preferentially the idle neighbor cells as the object cells. For a neighbor cell that is indifferent a GSM Main Processing Subrack (GMPS) from but the same BSC with the source cell, if its

channel status is not known, this neighbor cell is considered as idle. If all the neighbor cells of the sourcecell are congested, a default neighbor cell (the first cell in the candidate cell list) is selected even if it iscongested. This counter is measured when the selected neighbor cell is the source cell. It is not measured

when the object overlaid or underlaid subcell is congested.

Trigger Point

None.



1 BSC Measurement




Formula

Attempted Handovers per BSC (Underlaid Subcell to Overlaid Subcell)＝∑<

=

N i

i 0

Internal Intra-

Cell Handover Requests (Underlay to Overlay)

This counter is the sum of the predefined counter Internal Intra-Cell Handover Requests

(Underlay to Overlay) in all the cells controlled by a BSC.

1.8.14 Attempted Handovers per BSC (Overlaid Subcell toUnderlaid Subcell)

Counter

ZCH971L: Attempted Handovers per BSC (Overlaid Subcell to Underlaid Subcell)

Meaning

This counter measures the number of attempted handovers per BSC (overlaid subcell to

underlaid subcell).

The BSC selects preferentially the idle neighbor cells as the object cells. For a neighbor cell that is indifferent a GSM Main Processing Subrack (GMPS) from but the same BSC with the source cell, if itschannel status is not known, this neighbor cell is considered as idle. If all the neighbor cells of the source

cell are congested, a default neighbor cell (the first cell in the candidate cell list) is selected even if it iscongested. This counter is measured when the selected neighbor cell is the source cell. It is not measured

when the object overlaid or underlaid subcell is congested.

Trigger Point

None.

Formula

Attempted Handovers per BSC (Overlaid Subcell to Underlaid Subcell)＝∑<

=

N i

i 0

Internal Intra-

Cell Handover Requests (Overlay to Underlay)

This counter is the sum of the predefined counter Internal Intra-Cell Handover Requests

(Overlay to Underlay) in all the cells controlled by a BSC.

1.8.15 Attempted Handovers per BSC (Intra-Cell TCHF-to-TCHHHandover)

Counter

ZCH9005: Attempted Handovers per BSC (Intra-Cell TCHF-to-TCHH Handover)






Meaning

This counter measures the number of attempted handovers per BSC (intra-cell TCHF-to-

TCHH handover).

This counter indicates the frequency of attempted handovers per BSC (intra-cell TCHF-to-TCHH handover). You can know the handover performance by referring to Internal Intra-CellHandover Commands per BSC and Successful Internal Intra-Cell Handovers per BSC.

Trigger Point

None.

Formula

Attempted Handovers per BSC (Intra-Cell TCHF-to-TCHH Handover)=∑<

=

N i

i 0

Internal Intra-

Cell Handover Requests (AMR) (TCHF-TCHH)+ ∑<

=

N i

i 0

Internal Intra-Cell Handover Requests

(AMR) (TCHH-TCHF)

1.8.16 Attempted Handovers per BSC (Directed Retry)

Counter

ZCH9701: Attempted Handovers per BSC (Directed Retry)

Meaning

This counter measures the number of attempted outgoing cell handovers per BSC (directed

retry).

The handover can be between M900/850 and M900/850, M1800/1900 and M1800/1900,M900/850 and M1800/1900, M1800/1900 and M900/850.

Trigger Point

None.

Formula

Attempted Handovers per BSC (Directed Retry)=∑<

=

N i

i 0


Requests (Directed Retry) (900/850-900/850)+∑<

=

N i

i 0


Requests (Directed Retry) (1800/1900-1800/1900)+∑<

=

N i

i 0


Handover Requests (Directed Retry) (900/850-1800/1900)+∑<

=

N i

i 0




1 BSC Measurement





=

N i

i 0

Outgoing External Inter-Cell


=

N i

i 0



=

N i

i 0

Outgoing External Inter-

Cell Handover Requests (Directed Retry) (900/850-1800/1900)+∑<

=

N i

i 0


Cell Handover Requests (Directed Retry) (1800/1900-900/850)

1.9 Handover Success Measurement per BSC

1.9.1 Overview

Handover Success Measurement per BSC refers to the measurement of the number of

handovers due to all reasons per BSC.

Table 1-9 lists the counters of Handover Success Measurement per BSC.

Table 1-9 Counters of Handover Success Measurement per BSC

Counter Section

ZCH973A: Successful Handovers per BSC (Uplink Signal Quality) 1.9.2

ZCH973B: Successful Handovers per BSC (Downlink Signal Quality) 1.9.3

ZCH973C: Successful Handovers per BSC (Uplink Signal Strength) 1.9.4

ZCH973D: Successful Handovers per BSC (Downlink Signal Strength) 1.9.5

ZCH973E: Successful Handovers per BSC (Timing Advance) 1.9.6

ZCH973F: Successful Handovers per BSC (Better Cell) 1.9.7

ZCH973G: Successful Handovers per BSC (Load) 1.9.8

ZCH973H: Successful Handovers per BSC (Rapid Level Drop) 1.9.9

ZCH973I: Successful Handovers per BSC (MSC Intervention) 1.9.10

ZCH973J: Successful Handovers per BSC (OM Intervention) 1.9.11

ZCH973L: Successful Handovers per BSC (Other Causes) 1.9.12

ZH9032: Successful Handovers per BSC (Underlaid Subcell to OverlaidSubcell)

1.9.13

ZH9031: Successful Handovers per BSC (Overlaid Subcell to UnderlaidSubcell)

1.9.14

ZH9035: Successful Handovers per BSC (Intra-Cell TCHF-to-TCHH

Handover)

1.9.15






Counter Section

ZH9731: Successful Handovers per BSC (Directed Retry) 1.9.16

1.9.2 Successful Handovers per BSC (Uplink Signal Quality)

Counter

ZCH973A: Successful Handovers per BSC (Uplink Signal Quality)

Meaning

This counter measures the number of successful handovers per BSC (uplink signal quality).

Trigger Point

None.

Formula

Successful Handovers per BSC (Uplink Signal Quality)=(∑<

=

N i

i 0


Handover Requests (Uplink Quality)+∑<

=

N i

i 0


(Uplink Quality))-(∑<

=

N i

i 0

Failed Outgoing Internal Inter-Cell Handovers (Uplink Quality)+∑<

=

N i

i 0

Failed Outgoing External Inter-Cell Handovers (Uplink Quality))

1.9.3 Successful Handovers per BSC (Downlink Signal Quality)

Counter

ZCH973B: Successful Handovers per BSC (Downlink Signal Quality)

Meaning

This counter measures the number of successful handovers per BSC (downlink signal quality).

Trigger Point

None.



1 BSC Measurement




Formula

Successful Handovers per BSC (Downlink Signal Quality)=(∑<

=

N i

i 0


Handover Requests (Downlink Quality)+∑<

=

N i

i 0


Requests (Downlink Quality))-(∑<

=

N i

i 0


(Downlink Quality)+∑<

=

N i

i 0

Failed Outgoing External Inter-Cell Handovers (Downlink Quality))

1.9.4 Successful Handovers per BSC (Uplink Signal Strength)

CounterZCH973C: Successful Handovers per BSC (Uplink Signal Strength)

Meaning

This counter measures the number of successful outgoing cell handovers per BSC (uplink

signal strength).

Trigger Point

None.

Formula

Successful Handovers per BSC (Uplink Signal Strength)=(∑<

=

N i

i 0


Handover Requests (Uplink Strength)+∑<

=

N i

i 0


(Uplink Strength))-(∑<

=

N i

i 0

Failed Outgoing Internal Inter-Cell Handovers (Uplink Strength)

+∑

<

=

N i

i 0Failed Outgoing External Inter-Cell Handovers (Uplink Strength))

1.9.5 Successful Handovers per BSC (Downlink Signal Strength)

Counter

ZCH973D: Successful Handovers per BSC (Downlink Signal Strength)

Meaning

This counter measures the number of successful outgoing cell handovers per BSC (downlink

signal strength).






Trigger Point

None.

Formula

Successful Handovers per BSC (Downlink Signal Strength)=(∑<

=

N i

i 0


Cell Handover Requests (Downlink Strength)+∑<

=

N i

i 0


Requests (Downlink Strength)-(∑<

=

N i

i 0


(Downlink Strength)+∑<

=

N i

i 0

Failed Outgoing External Inter-Cell Handovers (Downlink

Strength))

1.9.6 Successful Handovers per BSC (Timing Advance)

Counter

ZCH973E: Successful Handovers per BSC (Timing Advance)

Meaning

This counter measures the number of successful outgoing cell handovers per BSC (timing

advance).

Trigger Point

None.

Formula

Successful Handovers per BSC (Timing Advance)=(∑<

=

N i

i 0


Handover Requests (Timing Advance)+∑

<

=

N i

i 0 Outgoing External Inter-Cell Handover Requests

(Timing Advance)-(∑<

=

N i

i 0

Failed Outgoing Internal Inter-Cell Handovers (Timing

Advance)+∑<

=

N i

i 0

Failed Outgoing External Inter-Cell Handovers (Timing Advance))

1.9.7 Successful Handovers per BSC (Better Cell)

Counter

ZCH973F: Successful Handovers per BSC (Better Cell)



1 BSC Measurement




Meaning

This counter measures the number of successful outgoing cell handovers per BSC (better cell).

Better cell refers to a cell with less path loss and higher priority.

Trigger Point

None.

Formula

Successful Handovers per BSC (Better Cell)=(∑<

=

N i

i 0


Requests (Better Cell)+∑<

=

N i

i 0

Outgoing External Inter-Cell Handover Requests (Better Cell))-

(∑<

=

N i

i 0

Failed Outgoing Internal Inter-Cell Handovers (Better Cell)+∑<

=

N i

i 0

Failed Outgoing

External Inter-Cell Handovers (Better Cell))

1.9.8 Successful Handovers per BSC (Load)

Counter

ZCH973G: Successful Handovers per BSC (Load)

MeaningThis counter measures the number of successful handovers per BSC (load).

Trigger Point

None.

Formula

Successful Handovers per BSC (Load)=(∑<

=

N i

i 0

Outgoing Internal Inter-Cell Handover Requests

(Load)+∑<

=

N i

i 0

Outgoing External Inter-Cell Handover Requests (Load)-(∑<

=

N i

i 0

Failed Outgoing

Internal Inter-Cell Handovers (Load)+∑<

=

N i

i 0


(Load))

1.9.9 Successful Handovers per BSC (Rapid Level Drop)

Counter

ZCH973H: Successful Handovers per BSC (Rapid Level Drop)






Meaning

This counter measures the number of successful handovers per BSC (rapid level drop).

Trigger Point None.

Formula

Successful Handovers per BSC (Rapid Level Drop)=(∑<

=

N i

i 0


Handover Requests (Rapid Level Drop)+∑<

=

N i

i 0


Requests (Rapid Level Drop)-(∑

<

=

N i

i 0Failed Outgoing Internal Inter-Cell Handovers (Rapid

Level Drop)+∑<

=

N i

i 0

Failed Outgoing External Inter-Cell Handovers (Rapid Level Drop))

1.9.10 Successful Handovers per BSC (MSC Intervention)

Counter

ZCH973I: Successful Handovers per BSC (MSC Intervention)

Meaning

This counter measures the number of successful outgoing cell handovers per BSC (MSC

intervention). The MSC sends the HANDOVER CANDIDATE ENQUIRY message to theBSC, and then handovers of multiple MSs in one cell are initiated.

Trigger Point

None.

Formula

Successful Handovers per BSC (MSC Intervention)=(∑<

=

N i

i 0


Handover Requests (MSC Intervention)+∑<

=

N i

i 0


Requests (MSC Intervention)-(∑<

=

N i

i 0

Failed Outgoing Internal Inter-Cell Handovers (MSC

Intervention)+∑<

=

N i

i 0

Failed Outgoing External Inter-Cell Handovers (MSC Intervention))



1 BSC Measurement




1.9.11 Successful Handovers per BSC (OM Intervention)

Counter

ZCH973J: Successful Handovers per BSC (OM Intervention)

Meaning

This counter measures the number of successful handovers per BSC (OM intervention).

Trigger Point

None.

Formula

Successful Handovers per BSC (OM Intervention)=(∑<

=

N i

i 0


Handover Requests (OM Intervention)+∑<

=

N i

i 0


(OM Intervention))-(∑<

=

N i

i 0

Failed Outgoing Internal Inter-Cell Handovers (OM

Intervention)+∑<

=

N i

i 0

Failed Outgoing External Inter-Cell Handovers (OM Intervention))

1.9.12 Successful Handovers per BSC (Other Causes)

Counter

ZCH973L: Successful Handovers per BSC (Other Causes)

Meaning

This counter measures the number of successful handovers per BSC (other causes).

Trigger Point

None.

Formula

Successful Handovers per BSC (Other Causes)=(∑<

=

N i

i 0


Requests (Other Causes)+∑<

=

N i

i 0

Outgoing External Inter-Cell Handover Requests (Other






Causes)-(∑<

=

N i

i 0

Failed Outgoing Internal Inter-Cell Handovers (Other Causes)+∑<

=

N i

i 0

Failed

Outgoing External Inter-Cell Handovers (Other Causes)）

1.9.13 Successful Handovers per BSC (Underlaid Subcell toOverlaid Subcell)

Counter

ZH9032: Successful Handovers per BSC (Underlaid Subcell to Overlaid Subcell)

Meaning

This counter measures the number of successful handovers per BSC (underlaid subcell to

overlaid subcell).

Trigger Point

None.

Formula

Successful Handovers per BSC (Underlaid Subcell to Overlaid Subcell)=∑<

=

N i

i 0

Internal Intra-

Cell Handover Requests (Underlay to Overlay)- (∑<

=

N i

i 0


(Channel Unavailable) (Underlay to Overlay)+∑<

=

N i

i 0


(Channel Unavailable) (Underlay to Overlay)

1.9.14 Successful Handovers per BSC (Overlaid Subcell toUnderlaid Subcell)

Counter

ZH9031: Successful Handovers per BSC (Overlaid Subcell to Underlaid Subcell)

Meaning

This counter measures the number of successful handovers per BSC (overlaid subcell to

underlaid subcell).

Trigger Point

None.



1 BSC Measurement




Formula

Successful Handovers per BSC (Overlaid Subcell to Underlaid Subcell)=∑<

=

N i

i 0

Internal Intra-

Cell Handover Requests (Overlay to Underlay)+ (∑<

=

N i

i 0


(Channel Unavailable) (Overlay to Underlay)+∑<

=

N i

i 0


(Channel Unavailable) (Overlay to Underlay)

1.9.15 Successful Handovers per BSC (Intra-Cell TCHF-to-TCHHHandover)

CounterZH9035: Successful Handovers per BSC (Intra-Cell TCHF-to-TCHH Handover)

Meaning

This counter measures the number of successful handovers per BSC (intra-cell TCHF to

TCHH handover).

Trigger Point

None.

Formula

Successful Handovers per BSC (Intra-Cell TCHF-to-TCHH Handover)= (∑<

=

N i

i 0

Internal Intra-

Cell Handover Requests (AMR) (TCHF-TCHH)+∑<

=

N i

i 0


(AMR) (TCHH-TCHF) - (∑<

=

N i

i 0

Failed Internal Intra-Cell Handovers (AMR) (TCHF-

TCHH)+∑

<

=

N i

i 0Failed Internal Intra-Cell Handovers (AMR) (TCHH-TCHF)

1.9.16 Successful Handovers per BSC (Directed Retry)

Counter

ZH9731: Successful Handovers per BSC (Directed Retry)

Meaning

This counter measures the number of successful outgoing cell handovers per BSC (direct

retry).






The channels can be SDCCHs, TCHFs, and TCHHs.

The handover can be between M900/850 and M900/850, M1800/1900 and M1800/1900,

M900/850 and M1800/1900, M1800/1900 and M900/850.

Trigger Point

None.

Formula

Successful Handovers per BSC (Directed Retry)= (∑<

=

N i

i 0



=

N i

i 0



=

N i

i 0



=

N i

i 0



=

N i

i 0



=

N i

i 0



=

N i

i 0

Outgoing External

Inter-Cell Handover Requests (Directed Retry) (900/850-1800/1900)+∑<

=

N i

i 0

Outgoing External

Inter-Cell Handover Requests (Directed Retry) (1800/1900-900/850)) - (∑<

=

N i

i 0

Failed Outgoing

Internal Inter-Cell Handovers (Directed Retry) (900/850-900/850)+∑<

=

N i

i 0

Failed Outgoing


=

N i

i 0

Failed Outgoing


=

N i

i 0

Failed Outgoing


=

N i

i 0

Failed Outgoing

External Inter-Cell Handovers (Directed Retry) (900/850-900/850)+∑<

=

N i

i 0

Failed Outgoing


=

N i

i 0

Failed Outgoing



1 BSC Measurement





=

N i

i 0

Failed Outgoing

External Inter-Cell Handovers (Directed Retry) (1800/1900-900/850))

1.10 Inter-Frequency-Band Measurement per BSC

1.10.1 Overview

Inter-Frequency-Band Measurement per BSC refers to the measurement of the number ofinternal and external BSC handover attempts and successes.

Table 1-10 lists the counters of Inter-Frequency-Band Measurement per BSC.

Table 1-10 Counters of Inter-Frequency-Band Measurement per BSC

Counter Section

ZCH900Y: Attempted Internal Inter-Cell Handovers per BSC (900/850 to1800/1900)

1.10.2

ZCH900Z: Attempted Internal Inter-Cell Handovers per BSC (1800/1900 to900/850)

1.10.3

ZCH903Y: Successful Internal Inter-Cell Handovers per BSC (900/850 to1800/1900)

1.10.4

ZCH903Z: Successful Internal Inter-Cell Handovers per BSC (1800/1900 to

900/850)

1.10.5

ZCH940Y: Attempted Incoming BSC Handovers per BSC (900/850 to1800/1900)

1.10.6

ZCH940Z: Attempted Incoming BSC Handovers per BSC (1800/1900 to900/850)

1.10.7

ZCH943Y: Successful Incoming BSC Handovers per BSC (900/850 to1800/1900)

1.10.8

ZCH943Z: Successful Incoming BSC Handovers per BSC (1800/1900 to

900/850)

1.10.9

ZCH930Y: Attempted Outgoing BSC Handovers per BSC (900/850 to1800/1900)

1.10.10

ZCH930Z: Attempted Outgoing BSC Handovers per BSC (1800/1900 to900/850)

1.10.11

ZCH933Y: Successful Outgoing BSC Handovers per BSC (900/850 to

1800/1900)

1.10.12

ZCH933Z: Successful Outgoing BSC Handovers per BSC (1800/1900 to

900/850)

1.10.13






1.10.2 Attempted Internal Inter-Cell Handovers per BSC (900/850to 1800/1900)

CounterZCH900Y: Attempted Internal Inter-Cell Handovers per BSC (900/850 to 1800/1900)

Meaning

This counter measures the number of attempted internal inter-cell handovers per BSC

(900/850 to 1800/1900).The BSC decides whether to initiate a handover based on themeasurement report and the handover algorithm. If the source cell and the object cell arecontrolled by one BSC, the internal inter-cell handover is initiated.

The channels can be SDCCHs and TCHs.

This counter indicates the frequency of attempted internal inter-cell handovers per BSC. Youcan know the handover performance by referring to Successful Internal Inter-Cell Handovers

per BSC (900/850 to 1800/1900).

The handover is between only M900/850 and M1800/1900.

Trigger Point

None.

Formula

Attempted Internal Inter-Cell Handovers per BSC (900/850 to 1800/1900)=∑<

=

N i

i 0

Incoming

Internal Inter-Cell Handover Requests (SDCCH) (900/850-1800/1900)+∑<

=

N i

i 0

Incoming

Internal Inter-Cell Handover Requests (TCH) (900/850-1800/1900)

1.10.3 Attempted Internal Inter-Cell Handovers per BSC(1800/1900 to 900/850)

Counter

ZCH900Z: Attempted Internal Inter-Cell Handovers per BSC (1800/1900 to 900/850)

Meaning

This counter measures the number of attempted internal inter-cell handovers per BSC

(1800/1900 to 900/850).The BSC decides whether to initiate a handover based on themeasurement report and the handover algorithm. If the source cell and the object cell are

controlled by one BSC, the internal inter-cell handover is initiated.




1 BSC Measurement




This counter indicates the frequency of attempted internal inter-cell handovers per BSC. Youcan know the handover performance by referring to Successful Internal Inter-Cell Handovers per BSC (1800/1900 to 900/850).


Trigger Point

None.

Formula

Attempted Internal Inter-Cell Handovers per BSC (1800/1900 to 900/850) =∑<

=

N i

i 0

Incoming

Internal Inter-Cell Handover Requests (SDCCH) (1800/1900-900/850)+∑

<

=

N i

i 0Incoming

Internal Inter-Cell Handover Requests (TCH) (1800/1900-900/850)

1.10.4 Successful Internal Inter-Cell Handovers per BSC (900/850to 1800/1900)

Counter

ZCH903Y: Successful Internal Inter-Cell Handovers per BSC (900/850 to 1800/1900)

Meaning

This counter measures the number of successful internal inter-cell handovers per BSC

(900850 to 1800/1900).


You can know the handover performance by referring to Attempted Internal Inter-Cell

Handovers per BSC (900/850 to 1800/1900).


Trigger Point

None.

Formula

Successful Internal Inter-Cell Handovers per BSC (900/850 to 1800/1900)= (∑<

=

N i

i 0

Incoming


=

N i

i 0

Incoming






Internal Inter-Cell Handover Requests (TCH) (900/850-1800/1900)) - (∑<

=

N i

i 0

Failed Incoming

Internal Inter-Cell Handovers (SDCCH) (900/850-1800/1900)+∑<

=

N i

i 0

Failed Incoming Internal

Inter-Cell Handovers (TCH) (900/850-1800/1900))

1.10.5 Successful Internal Inter-Cell Handovers per BSC(1800/1900 to 900/850)

Counter

ZCH903Z: Successful Internal Inter-Cell Handovers per BSC (1800/1900 to 900/850)

Meaning

This counter measures the number of successful internal inter-cell handovers per BSC(1800/1900 to 900/850). This counter is measured based on the channel type. The handover

initiation causes are direct retry and indirect retry.


You can know the handover performance by referring to Attempted Internal Inter-Cell

Handovers per BSC (1800/1900 to 900/850).


Trigger Point

None.

Formula

Successful Internal Inter-Cell Handovers per BSC (1800/1900 to 900/850) = (∑<

=

N i

i 0

Incoming


=

N i

i 0

Incoming

Internal Inter-Cell Handover Requests (TCH) (1800/1900-900/850)) - (∑<

=

N i

i 0

Failed Incoming

Internal Inter-Cell Handovers (SDCCH) (1800/1900-900/850)+∑<

=

N i

i 0

Failed Incoming Internal

Inter-Cell Handovers (TCH) (1800/1900-900/850))



1 BSC Measurement




1.10.6 Attempted Incoming BSC Handovers per BSC (900/850 to1800/1900)

CounterZCH940Y: Attempted Incoming BSC Handovers per BSC (900/850 to 1800/1900)

Meaning

This counter measures the number of attempted incoming BSC handovers per BSC (900/850

to 1800/1900).

If the source cell and the object cell are controlled by different BSCs, the external BSChandover is initiated. This counter is measured based on the channel type and seized TCH

channel type.


This counter indicates the frequency of attempted incoming BSC handovers per BSC. You canknow the handover performance by referring to Successful Incoming BSC Handovers per

BSC (900/850 to 1800/1900).


Trigger Point

None.

Formula

Attempted Incoming BSC Handovers per BSC (900/850 to 1800/1900)=∑<

=

N i

i 0

Incoming

External Inter-Cell Handover Requests (SDCCH) (900/850-1800/1900)+∑<

=

N i

i 0

Incoming

External Inter-Cell Handover Requests (TCH) (900/850-1800/1900)

1.10.7 Attempted Incoming BSC Handovers per BSC (1800/1900 to

900/850)

Counter

ZCH940Z: Attempted Incoming BSC Handovers per BSC (1800/1900 to 900/850)

Meaning

This counter measures the number of attempted incoming BSC handovers per BSC

(1800/1900 to 900/850).






If the source cell and the object cell are controlled by different BSCs, the external BSChandover is initiated. This counter is measured based on the channel type and seized TCHchannel type.


This counter indicates the frequency of attempted incoming BSC handovers per BSC. You can

know the handover performance by referring to Successful Incoming BSC Handovers per

BSC (1800/1900 to 900/850).


Trigger Point

None.

Formula

Attempted Incoming BSC Handovers per BSC (900/850 to 1800/1900)=∑<

=

N i

i 0

Incoming


=

N i

i 0

Incoming

External Inter-Cell Handover Requests (TCH) (900/850-1800/1900)

1.10.8 Successful Incoming BSC Handovers per BSC (900/850 to1800/1900)

Counter

ZCH943Y: Successful Incoming BSC Handovers per BSC (900/850 to 1800/1900)

Meaning

This counter measures the number of successful incoming BSC handovers per BSC (900/850to 1800/1900).


You can know the handover performance by referring to Attempted Incoming BSC Handovers per BSC (900/850 to 1800/1900).


Trigger Point

None.



1 BSC Measurement




Formula

Successful Incoming BSC Handovers per BSC (900/850 to 1800/1900)= (∑<

=

N i

i 0

Incoming


=

N i

i 0

Incoming

External Inter-Cell Handover Requests (TCH) (900/850-1800/1900))- (∑<

=

N i

i 0

Failed Incoming

External Inter-Cell Handovers (SDCCH) (900/850-1800/1900)+∑<

=

N i

i 0

Failed Incoming

External Inter-Cell Handovers (TCH) (900/850-1800/1900))

1.10.9 Successful Incoming BSC Handovers per BSC (1800/1900 to

900/850)

Counter

ZCH943Z: Successful Incoming BSC Handovers per BSC (1800/1900 to 900/850)

Meaning

This counter measures the number of successful incoming BSC handovers per BSC(1800/1900 to 900/850).


You can know the handover performance by referring to Attempted Incoming BSC Handovers per BSC (1800/1900 to 900/850).


Trigger Point

None.

Formula

Successful Incoming BSC Handovers per BSC (1800/1900 to 900/850)= (∑<

=

N i

i 0

Incoming


=

N i

i 0

Incoming

External Inter-Cell Handover Requests (TCH) (1800/1900-900/850)) - (∑<

=

N i

i 0

Failed Incoming

External Inter-Cell Handovers (SDCCH) (1800/1900-900/850)+∑<

=

N i

i 0

Failed Incoming

External Inter-Cell Handovers (TCH) (1800/1900-900/850))






1.10.10 Attempted Outgoing BSC Handovers per BSC (900/850 to1800/1900)

CounterZCH930Y: Attempted Outgoing BSC Handovers per BSC (900/850 to 1800/1900)

Meaning

This counter measures the number of attempted outgoing BSC handovers per BSC (900/850

to 1800/1900).This counter is measured based on the channel type, signaling points, andhandover initiation causes.


The handover between different signaling points in a BSC is also called outgoing external

inter-cell handover.

This counter indicates the frequency of attempted outgoing BSC handovers per BSC. You canknow the handover performance by referring to Successful Outgoing BSC Handovers per

BSC (900/850 to 1800/1900).


Trigger Point

None.

Formula

Attempted Outgoing BSC Handovers per BSC (900/850 to 1800/1900)＝∑<

=

N i

i 0

Outgoing

External Inter-Cell Handover Requests (SDCCH) (Excluding Directed Retry) (900/850-

1800/1900)+∑<

=

N i

i 0

Outgoing External Inter-Cell Handover Requests (TCHF) (Excluding

Directed Retry) (900/850-1800/1900)+∑<

=

N i

i 0


(TCHH) (Excluding Directed Retry) (900/850-1800/1900)+∑<

=

N i

i 0


Handover Requests (Directed Retry) (900/850-1800/1900)

1.10.11 Attempted Outgoing BSC Handovers per BSC (1800/1900to 900/850)

Counter

ZCH930Z: Attempted Outgoing BSC Handovers per BSC (1800/1900 to 900/850)



1 BSC Measurement




Meaning

This counter measures the number of attempted outgoing BSC handovers per BSC

(1800/1900 to 900/850).This counter is measured based on the channel type, signaling points,

and handover initiation causes.


The handover between different signaling points in a BSC is also called outgoing externalinter-cell handover.

This counter indicates the frequency of attempted outgoing BSC handovers per BSC. You can

know the handover performance by referring to Successful Outgoing BSC Handovers perBSC (1800/1900 to 900/850).


Trigger Point

None.

Formula

Attempted Outgoing BSC Handovers per BSC (1800/1900 to 900/850)＝∑<

=

N i

i 0

Outgoing


900/850)+∑<

=

N i

i

0

Outgoing External Inter-Cell Handover Requests (TCHF) (Excluding Directed

Retry) (1800/1900-900/850)+∑<

=

N i

i 0

Outgoing External Inter-Cell Handover Requests (TCHH)

(Excluding Directed Retry) (1800/1900-900/850)+∑<

=

N i

i 0


Handover Requests (Directed Retry) (1800/1900-900/850)

1.10.12 Successful Outgoing BSC Handovers per BSC (900/850 to1800/1900)

Counter

ZCH933Y: Successful Outgoing BSC Handovers per BSC (900/850 to 1800/1900)

Meaning

This counter measures the number of successful outgoing BSC handovers per BSC (900/850

to 1800/1900). This counter is measured based on the channel type and signaling points. Thehandover initiation causes are direct retry and indirect retry.








Trigger Point

None.

Formula

Successful Outgoing BSC Handovers per BSC (900/850 to 1800/1900)= (∑<

=

N i

i 0

Outgoing


900/850)+∑<

=

N i

i 0

Outgoing External Inter-Cell Handover Requests (TCHF) (Excluding Directed

Retry) (1800/1900-900/850)+∑

<

=

N i

i 0

Outgoing External Inter-Cell Handover Requests (TCHH)

(Excluding Directed Retry) (1800/1900-900/850)+∑<

=

N i

i 0


Handover Requests (Directed Retry) (1800/1900-900/850))- (∑<

=

N i

i 0


Inter-Cell Handovers (SDCCH) (1800/1900-900/850)+∑<

=

N i

i 0

Failed Outgoing External Inter-

Cell Handovers (TCHF) (1800/1900-900/850)+∑<

=

N i

i 0


Handovers (TCHH) (1800/1900-900/850)+∑<

=

N i

i 0


Handovers (Directed Retry) (1800/1900-900/850)

1.10.13 Successful Outgoing BSC Handovers per BSC (1800/1900to 900/850)

Counter

ZCH933Z: Successful Outgoing BSC Handovers per BSC (1800/1900 to 900/850)

Meaning

This counter measures the number of successful outgoing BSC handovers per BSC

(1800/1900 to 900/850). This counter is measured based on the channel type and signaling points. The handover initiation causes are direct retry and indirect retry.





1 BSC Measurement




Trigger Point

None.

Formula

Successful Outgoing BSC Handovers per BSC (1800/1900 to 900/850)＝ ([∑<

=

N i

i 0

Outgoing


900/850)]+ [∑<

=

N i

i 0

External Outgoing Cell Handover Requests per BSC(TCHF) (Excluding

Directed Retry) (1800/1900-900/850)]+ [∑<

=

N i

i 0


Requests (TCHH) (Excluding Directed Retry) (1800/1900-900/850)]+ [∑<

=

N i

i 0

Outgoing

External Inter-Cell Handover Requests (Directed Retry) (1800/1900-900/850)]) -

([∑<

=

N i

i 0

Failed Outgoing External Inter-Cell Handovers (SDCCH) (1800/1900-900/850)]+

[∑<

=

N i

i 0

Failed Outgoing External Inter-Cell Handovers (TCHF) (1800/1900-900/850)]+

[∑<

=

N i

i 0

Failed Outgoing External Inter-Cell Handovers (TCHH) (1800/1900-900/850)]+

[∑<

=

N i

i 0

Failed Outgoing External Inter-Cell Handovers (Directed Retry) (1800/1900-900/850)])

1.11 Handover KPI Measurement per BSC

1.11.1 Overview

Handover KPI Measurement per BSC refers to the measurement of the number of internal andexternal BSC handovers, handover requests, commands, and success ratio.

Table 1-11 lists the counters of Handover KPI Measurement per BSC.

Table 1-11 Counters of Handover KPI Measurement per BSC

Counter Section

ZCH300: Internal Intra-Cell Handover Requests per BSC 1.11.2

ZCH301: Internal Intra-Cell Handover Commands per BSC 1.11.3

ZCH303: Successful Internal Intra-Cell Handovers per BSC 1.11.4

ZCH310: Internal Outgoing Cell Handover Requests per BSC 1.11.5

ZCH311: Internal Outgoing Cell Handover Commands per BSC 1.11.6






Counter Section

ZCH313: Successful Internal Outgoing Cell Handovers per BSC 1.11.7

ZCH320: Internal Incoming Cell Handover Requests per BSC 1.11.8

ZK3190: Internal Incoming Cell Handover Commands per BSC 1.11.9

ZCH323: Successful Internal Incoming Cell Handovers per BSC 1.11.10

ZCH330: External Outgoing Cell Handover Requests per BSC 1.11.11

ZCH331: External Outgoing Cell Handover Commands per BSC 1.11.12

ZCH333: Successful External Outgoing Cell Handovers per BSC 1.11.13

ZCH340: External Incoming Cell Handover Requests per BSC 1.11.14

ZK3191: External Incoming Cell Handover Commands per BSC 1.11.15

ZCH343: Successful External Incoming Cell Handovers per BSC 1.11.16

ZCH343: Dual-Band Handover Requests per BSC 1.11.17

ZK3173: Successful Dual-Band Handovers per BSC 1.11.18

ZK3189: External Outgoing Cell Handover Requests per BSC (Inter-

Signaling-Point Handover)

1.11.19

ZK3190: Failed External Outgoing Cell Handovers per BSC (Inter-


1.11.20

ZK3191: External Outgoing Cell Handover Commands per BSC (Inter-


1.11.21

ZK3174: Internal Handover Success Ratio per BSC 1.11.22

ZK3175: Intra-BSC Radio Handover Success Ratio per BSC 1.11.23

ZK3176: External Outgoing Cell Handover Success Ratio per BSC 1.11.24

ZK3177: External Outgoing Cell Radio Handover Success Ratio per

BSC

1.11.25

ZK3178: External Incoming Cell Handover Success Ratio per BSC 1.11.26

ZK3179: External Incoming Cell Radio Handover Success Ratio per

BSC

1.11.27

ZK3180: Handover Success Ratio per BSC 1.11.28

ZK3181: Radio Handover Success Ratio per BSC 1.11.29

ZK3182: Dual-Band Handover Success Ratio per BSC 1.11.30



1 BSC Measurement




1.11.2 Internal Intra-Cell Handover Requests per BSC

Counter

ZCH300: Internal Intra-Cell Handover Requests per BSC

Meaning

This counter measures the number of internal intra-cell handover requests per BSC. The

channels can be SDCCHs, TCHFs, and TCHHs.

The handover initiation is related to the quality and strength of uplink and downlink signals,TA, better cell, cell load, fast level drop, MSC and OM intervention, and EDGE coverage.

This counter indicates the frequency of internal intra-cell handovers per BSC. You can know

the handover performance by referring to Internal Intra-Cell Handover Commands per BSC and Successful Internal Intra-Cell Handovers per BSC.

Trigger Point

None.

Formula

Internal Intra-Cell Handover Requests per BSC=∑<

=

N i

i 0


This counter is the sum of the predefined counter Internal Intra-Cell Handover Requests in all


1.11.3 Internal Intra-Cell Handover Commands per BSC

Counter

ZCH301: Internal Intra-Cell Handover Commands per BSC

Meaning

This counter measures the number of internal intra-cell handover commands per BSC. The


The handover requests include intra-cell handover requests, channel type change requests, and

intra-cell concentric cell handover requests.

Trigger Point

None.

Formula

Internal Intra-Cell Handover Commands per BSC=∑<

=

N i

i 0

Internal Intra-Cell Handover

Commands






This counter is the sum of the predefined counter Internal Intra-Cell Handover Commands inall the cells controlled by a BSC.

1.11.4 Successful Internal Intra-Cell Handovers per BSC

Counter

ZCH303: Successful Internal Intra-Cell Handovers per BSC

Meaning

This counter measures the number of successful internal intra-cell handovers per BSC. Thechannels can be SDCCHs, TCHFs, and TCHHs.

The handover requests include intra-cell handover requests, channel type change requests, and

intra-cell concentric cell handover requests.

You can know the handover performance by referring to Internal Intra-Cell HandoverRequests per BSC.

Trigger Point

None.

Formula

Successful Internal Intra-Cell Handovers per BSC=∑<

=

N i

i 0

Successful Internal Intra-Cell

Handovers

This counter is the sum of the predefined counter Successful Internal Intra-Cell Handovers in


1.11.5 Internal Outgoing Cell Handover Requests per BSC

Counter

ZCH310: Internal Outgoing Cell Handover Requests per BSC

Meaning

This counter measures the number of internal outgoing cell handover requests per BSC. The



handover algorithm. If the source cell and the object cell are controlled by one BSC, theinternal inter-cell handover is initiated.

The handover initiation is related to the quality and strength of uplink and downlink signals,

TA, better cell, cell load, fast level drop, MSC and OM intervention, and EDGE coverage.


M900/850 and M1800/1900, M1800/1900 and M900/850.



1 BSC Measurement




You can know the performance of internal outgoing cell handovers per BSC by referring tothis counter, Internal Outgoing Cell Handover Commands per BSC, and Successful InternalOutgoing Cell Handovers per BSC. You can also know the performance of internal inter-cell

handovers per BSC by referring to this counter and counters of internal BSC incoming cellhandover.

Trigger Point

None.

Formula

Internal Outgoing Cell Handover Requests per BSC=∑<

=

N i

i 0


Handover Requests

This counter is the sum of the predefined counter Outgoing Internal Inter-Cell HandoverRequests in all the cells controlled by a BSC.

1.11.6 Internal Outgoing Cell Handover Commands per BSC

Counter

ZCH311: Internal Outgoing Cell Handover Commands per BSC

Meaning

This counter measures the number of external outgoing cell handover commands per BSC.The channels can be SDCCHs, TCHFs, and TCHHs.

During the process of internal outgoing cell handover, the BSC sends the HO CMD message

to the MS through the source cell. This counter is measured according to the channel type,handover initiation cause, and handover bands type.




You can know the handover performance by referring to Internal Outgoing Cell Handover

Requests per BSC.

Trigger Point

None.

Formula

Internal Outgoing Cell Handover Commands per BSC=∑<

=

N i

i 0


Handover Commands






This counter is the sum of the predefined counter Outgoing Internal Inter-Cell HandoverCommands in all the cells controlled by a BSC.

1.11.7 Successful Internal Outgoing Cell Handovers per BSC

Counter

ZCH313: Successful Internal Outgoing Cell Handovers per BSC

Meaning

This counter measures the number of successful internal outgoing cell handovers per BSC.The channels can be SDCCHs, TCHFs, and TCHHs.



You can know the handover performance by referring to Internal Outgoing Cell HandoverRequests per BSC.

Trigger Point

None.

Formula

Successful Internal Outgoing Cell Handovers per BSC=∑<

=

N i

i 0

Successful Outgoing Internal

Inter-Cell Handover

This counter is the sum of the predefined counter Successful Outgoing Internal Inter-Cell

Handover in all the cells controlled by a BSC.

1.11.8 Internal Incoming Cell Handover Requests per BSC

Counter

ZCH320: Internal Incoming Cell Handover Requests per BSC

Meaning

This counter measures the number of internal incoming cell handover requests per BSC. The



handover algorithm. If the source cell and the object cell are controlled by one BSC, theinternal inter-cell handover is initiated.


M900/850 and M1800/1900, M1800/1900 and M900/850.

You can know the handover performance by referring to Internal Incoming Cell Handover

Commands per BSC.



1 BSC Measurement




Trigger Point

None.

Formula

Internal Incoming Cell Handover Requests per BSC=∑<

=

N i

i 0

Incoming Internal Inter-Cell

Handover Requests

This counter is the sum of the predefined counter Incoming Internal Inter-Cell HandoverRequests in all the cells controlled by a BSC.

1.11.9 Internal Incoming Cell Handover Commands per BSC

CounterZK3190: Internal Incoming Cell Handover Commands per BSC

Meaning

This counter measures the number of internal incoming cell handover commands per BSC.


During the process of internal incoming cell handover, the BSC sends the HO CMD message

to the MS through the source cell. This counter is measured according to the channel type,handover initiation cause, and handover bands type.


M900/850 and M1800/1900, M1800/1900 and M900/850.

You can know the performance of internal incoming cell handovers per BSC by referring tothis counter and Successful Internal Incoming Cell Handovers per BSC. You can also know

the performance of internal inter-cell handovers per BSC by referring to this counter andcounters of internal inter-cell handovers per BSC.

Trigger Point

None.

Formula

Internal Incoming Cell Handover Commands per BSC =∑<

=

N i

i 0

Incoming Internal Inter-Cell

Handover Responses

This counter is the sum of the predefined counter Incoming Internal Inter-Cell HandoverResponses in all the cells controlled by a BSC.






1.11.10 Successful Internal Incoming Cell Handovers per BSC

Counter

ZCH323: Successful Internal Incoming Cell Handovers per BSC

Meaning

This counter measures the number of successful internal incoming cell handovers per BSC.



You can know the handover performance by referring to Internal Incoming Cell Handover

Requests per BSC and Internal Incoming Cell Handover Commands per BSC.

Trigger Point

None.

Formula

Successful Internal Incoming Cell Handovers per BSC=∑<

=

N i

i 0

Successful Internal Incoming

Cell Handovers

This counter is the sum of the predefined counter Successful Internal Incoming Cell

Handovers in all the cells controlled by a BSC.

1.11.11 External Outgoing Cell Handover Requests per BSC

Counter

ZCH330: External Outgoing Cell Handover Requests per BSC

Meaning

This counter measures the number of external outgoing cell handover requests per BSC. Thechannels can be SDCCHs, TCHFs, and TCHHs.

This counter is measured based on the channel type, signaling points, and handover initiationcauses.




You can know the performance of external outgoing cell handovers per BSC by referring to

this counter, External Outgoing Cell Handover Commands per BSC and Successful External

Outgoing Cell Handovers per BSC. You can also know the performance of external cell



1 BSC Measurement




handovers per BSC by referring to this counter and counters of external incoming cellhandovers per BSC.

Trigger Point

None.

Formula

External Outgoing Cell Handover Requests per BSC=∑<

=

N i

i 0

External Outgoing Cell Handover

Requests

This counter is the sum of the predefined counter External Outgoing Cell Handover Requestsin all the cells controlled by a BSC.

1.11.12 External Outgoing Cell Handover Commands per BSC

Counter

ZCH331: External Outgoing Cell Handover Commands per BSC

Meaning

This counter measures the number of external outgoing cell handover commands per BSC.


This counter is measured based on the channel type, signaling points, and handover initiation

causes.




You can know the performance of external outgoing cell handovers per BSC by referring tothis counter, External Outgoing Cell Handover Requests per BSC, and Successful ExternalOutgoing Cell Handovers per BSC. You can also know the performance of external cell

handovers per BSC by referring to this counter and counters of external incoming cell

handovers per BSC.

Trigger Point

None.

Formula

External Outgoing Cell Handover Commands per BSC=∑<

=

N i

i 0

External Outgoing Cell

Handover Commands

This counter is the sum of the predefined counter External Outgoing Cell Handover

Commands in all the cells controlled by a BSC.






1.11.13 Successful External Outgoing Cell Handovers per BSC

Counter

ZCH333: Successful External Outgoing Cell Handovers per BSC

Meaning

This counter measures the number of successful external outgoing cell handovers per BSC.



You can know the handover performance by referring to External Outgoing Cell Handover

Requests per BSC and External Outgoing Cell Handover Commands per BSC.

Trigger Point

None.

Formula

Successful External Outgoing Cell Handovers per BSC=∑<

=

N i

i 0

Successful External Outgoing

Cell Handovers

This counter is the sum of the predefined counter Successful External Outgoing Cell

Handovers in all the cells controlled by a BSC.

1.11.14 External Incoming Cell Handover Requests per BSC

Counter

ZCH340: External Incoming Cell Handover Requests per BSC

Meaning

This counter measures the number of external incoming cell handover requests per BSC. Thechannels can be SDCCHs, TCHFs, and TCHHs.

If the source cell and the object cell are controlled by different BSCs, the external BSChandover is initiated. This counter is measured based on the channel type, the type of bandsthat the handover crosses, and the seized TCH channel type.


You can know the performance of external incoming cell handovers per BSC by referring to

this counter, External Incoming Cell Handover Commands per BSC, and Successful ExternalIncoming Cell Handovers per BSC. You can also know the performance of external cell

handovers per BSC by referring to this counter and counters of external BSC outgoing cellhandovers.



1 BSC Measurement




Trigger Point

None.

Formula

External Incoming Cell Handover Requests per BSC=∑<

=

N i

i 0

External Incoming Cell Handover

Requests

This counter is the sum of the predefined counter External Incoming Cell Handover Requestsin all the cells controlled by a BSC.

1.11.15 External Incoming Cell Handover Commands per BSC

CounterZK3191: External Incoming Cell Handover Commands per BSC

Meaning

This counter measures the number of external incoming cell handover commands per BSC.


After BSC2 receives an HO REQ message, it requests for a channel from the target cell and

activates it. BSC2 requests for speech service resources. If the request succeeds, the BSC2returns an HO REQ ACK message to the MSC.

This counter is measured based on the channel type and the type of bands that the handover

crosses.


You can know the performance of external incoming cell handovers per BSC by referring to

this counter, External Incoming Cell Handover Requests per BSC, and Successful ExternalIncoming Cell Handovers per BSC. You can also know the performance of external cell

handovers per BSC by referring to this counter and counters of external cell handovers perBSC.

Trigger Point

None.

Formula

External Incoming Cell Handover Commands per BSC =∑<

=

N i

i 0

Incoming External Inter-Cell

Handover Responses

This counter is the sum of the predefined counter Incoming External Inter-Cell Handover

Responses in all the cells controlled by a BSC.






1.11.16 Successful External Incoming Cell Handovers per BSC

Counter

ZCH343: Successful External Incoming Cell Handovers per BSC

Meaning

During an external BSC handover, the object BSC starts preparing a new channel after it

receives a HANDOVER REQUEST message from the MSC. After the new channel is prepared and the MS successfully accesses the object cell, the BSC sends a HANDOVERCOMPLETE message to the MSC. This handover succeeds.

This counter measures the number of successful external incoming cell handovers per BSC.The channels can be SDCCHs, TCHFs, and TCHHs.



You can know the handover performance by referring to External Incoming Cell HandoverRequests per BSC and External Incoming Cell Handover Commands per BSC.

Trigger Point

None.

Formula

Successful External Incoming Cell Handovers per BSC=∑

<

=

N i

i 0Successful Incoming External

Inter-Cell Handovers

This counter is the sum of the predefined counter Successful Incoming External Inter-CellHandovers in all the cells controlled by a BSC.

1.11.17 Dual-Band Handover Requests per BSC

Counter

ZK3170: Dual-Band Handover Requests per BSC

Meaning

This counter measures the number of dual-band handover requests per BSC.

Trigger Point

None.



1 BSC Measurement




Formula

Dual-Band Handover Requests per BSC=∑<

=

N i

i 0

Dual-Band Handover Requests

This counter is the sum of the predefined counter Dual-Band Handover Requests in all thecells controlled by a BSC.

1.11.18 Successful Dual-Band Handovers per BSC

Counter

ZK3173: Successful Dual-Band Handovers per BSC

Meaning

This counter measures the number of successful dual-band handovers per BSC.

Trigger Point

None.

Formula

Successful Dual-Band Handovers per BSC =∑<

=

N i

i 0 Successful Dual-Band Handovers

This counter is the sum of the predefined counter Successful Dual-Band Handovers in all thecells controlled by a BSC.

1.11.19 External Outgoing Cell Handover Requests per BSC(Inter-Signaling-Point Handover)

Counter

ZK3192: External Outgoing Cell Handover Requests per BSC (Inter-Signaling-Point

Handover)

Meaning

This counter measures the number of external outgoing cell handover requests per BSC (inter-

signaling-point handover).

Trigger Point

None.

Formula

None.






1.11.20 Failed External Outgoing Cell Handovers per BSC (Inter-Signaling-Point Handover)

CounterZK3193: Failed External Outgoing Cell Handovers per BSC (Inter-Signaling-Point Handover)

Meaning

This counter measures the number of failed external outgoing cell handovers per BSC (inter-

signaling-point handover).

Trigger Point

None.

Formula

None.

1.11.21 External Outgoing Cell Handover Commands per BSC(Inter-Signaling-Point Handover)

Counter

ZK3194: External Outgoing Cell Handover Commands per BSC (Inter-Signaling-Point

Handover)

Meaning

This counter measures the number of external outgoing cell handover commands per BSC

(inter-signaling-point handover).

Trigger Point

None.

Formula

None.

1.11.22 Internal Handover Success Ratio per BSC

Counter

ZK3174: Internal Handover Success Ratio per BSC



1 BSC Measurement




Meaning

This counter measures the success ratio of internal handovers per BSC. Handover failures are

due to all reasons, including bad quality, internal BSC channel congestion, and MSC

intervention.

Trigger Point

None.

Formula

Internal Handover Success Ratio per BSC＝ (([Successful Internal Intra-Cell Handovers per

BSC]+[Successful Internal Incoming Cell Handovers per BSC]))/([Internal Intra-CellHandover Requests per BSC]+[Internal Incoming Cell Handover Requests per BSC]))*{100}

1.11.23 Intra-BSC Radio Handover Success Ratio per BSCCounter

ZK3175: Intra-BSC Radio Handover Success Ratio per BSC

Meaning

This counter measures the success ratio of internal radio handovers per BSC. Handover

failure causes are only related to the Um interface.

Trigger Point

None.

Formula

Intra-BSC Radio Handover Success Ratio per BSC＝(([Successful Internal Intra-Cell

Handovers per BSC]+[Successful Internal Incoming Cell Handovers per BSC]))/([InternalIntra-Cell Handover Commands per BSC]+[Incoming Internal Inter-Cell Handover Responses

per BSC]))*{100}

1.11.24 External Outgoing Cell Handover Success Ratio per BSC

Counter

ZK3176: External Outgoing Cell Handover Success Ratio per BSC

Meaning

This counter measures the success ratio of external outgoing cell handovers per BSC.

Handover failure causes include bad quality, internal BSC channel congestion, and MSC

intervention.






Trigger Point

None.

FormulaExternal Outgoing Cell Handover Success Ratio per BSC＝ ([Successful External Outgoing

Cell Handovers per BSC]/[External Outgoing Cell Handover Requests per BSC])*{100}

1.11.25 External Outgoing Cell Radio Handover Success Ratio perBSC

Counter

ZK3177: External Outgoing Cell Radio Handover Success Ratio per BSC

Meaning

This counter measures the success ratio of external outgoing cell radio handovers per BSC.

Handover failure causes are only related to the air interface.

Trigger Point

None.

Formula

External Outgoing Cell Radio Handover Success Ratio per BSC＝ ([Successful External

Outgoing Cell Handovers per BSC]/[External Outgoing Cell Handover Commands perBSC])*{100}

1.11.26 External Incoming Cell Handover Success Ratio per BSC

Counter

ZK3178: External Incoming Cell Handover Success Ratio per BSC

Meaning

This counter measures the success ratio of external incoming cell handovers per BSC.

Trigger Point

None.

Formula

External Incoming Cell Handover Success Ratio per BSC＝([Successful External Incoming

Cell Handovers per BSC]/[External Incoming Cell Handover Requests per BSC])*{100}



1 BSC Measurement




1.11.27 External Incoming Cell Radio Handover Success Ratio perBSC

CounterZK3179: External Incoming Cell Radio Handover Success Ratio per BSC

Meaning

This counter measures the success ratio of external incoming cell radio handovers per BSC.

Trigger Point

None.

Formula

External Incoming Cell Radio Handover Success Ratio per BSC＝([Successful External

Incoming Cell Handovers per BSC]/[ Incoming External Inter-Cell Handover Requests per

BSC])*{100}

1.11.28 Handover Success Ratio per BSC

Counter

ZK3180: Handover Success Ratio per BSC

Meaning

This counter measures the success ratio of handovers per BSC including internal BSChandover, external BSC outgoing cell handover, and external BSC incoming cell handover.

Handover failures are due to all reasons, including bad quality, internal BSC channelcongestion, and MSC intervention.

Trigger Point

None.

FormulaHandover Success Ratio per BSC＝ (([Successful Internal Intra-Cell Handovers per

BSC]+[Successful Internal Incoming Cell Handovers per BSC]+[Successful External

Outgoing Cell Handovers per BSC]+[Successful External Incoming Cell Handovers perBSC])/([Internal Intra-Cell Handover Requests per BSC]+[Internal Incoming Cell Handover

Requests per BSC]+[External Outgoing Cell Handover Requests per BSC]+[ExternalIncoming Cell Handover Requests per BSC]))*{100}






1.11.29 Radio Handover Success Ratio per BSC

Counter

ZK3181: Radio Handover Success Ratio per BSC

Meaning

This counter measures the success ratio of radio handovers per BSC.

Trigger Point

None.

Formula

Radio Handover Success Ratio per BSC＝ (([Successful Internal Intra-Cell Handovers per

BSC]+[Successful Internal Incoming Cell Handovers per BSC]+[Successful External

Outgoing Cell Handovers per BSC]+[Successful External Incoming Cell Handovers perBSC])/([Internal Intra-Cell Handover Commands per BSC]+[ Incoming Internal Inter-CellHandover Responses per BSC]+[External Outgoing Cell Handover Commands per

BSC]+[ Incoming External Inter-Cell Handover Responses per BSC]))*{100}

1.11.30 Dual-Band Handover Success Ratio per BSC

Counter

ZK3182: Dual-Band Handover Success Ratio per BSC

Meaning

This counter measures the success ratio of dual-band handovers per BSC. Handover failures

are due to all reasons, including bad quality, internal BSC channel congestion, and MSCintervention.

Trigger Point

None.

Formula

Dual-Band Handover Success Ratio per BSC＝([Successful Dual-Band Handovers per

BSC]/[Dual-Band Handover Requests per BSC])*{100}




Performance Counter Reference 2 SCCP Measurement


2 SCCP Measurement

About This Chapter


Section Describes

2.1 Overview of SCCPMeasurement

The functions and measurement unit of the SCCPMeasurement.

2.2 SCCP OSP Measurement The functions and counters of SCCP OSP Measurement.



2 SCCP Measurement




2.1 Overview of SCCP Measurement

SCCP Measurement refers to the measurement of SCCP original signaling points (OSPs).Table 2-1 lists the measurement unit of SCCP Measurement.

Table 2-1 Measurement unit of SCCP Measurement


SCCP OSP Measurement 2.2

2.2 SCCP OSP Measurement

2.2.1 Overview of SCCP OSP Measurement

SCCP OSP Measurement refers to the measurement of the number of various messages theSCCP sends or receives.

Table 2-2 lists the counters of SCCP OSP Measurement.

Table 2-2 Counters of SCCP OSP Measurement

Counter SectionL7001: Number of Sent UDT Messages 2.2.2

L7002: Number of Received UDT Messages 2.2.3

L7003: Number of Sent XUDT Messages 2.2.4

L7004: Number of Received XUDT Messages 2.2.5

L7005: Number of Sent CR Messages 2.2.6

L7006: Number of Received CR Messages 2.2.7

L7007: Number of Sent CREFR Messages 2.2.8

L7008: Number of Received CREFR Messages 2.2.9

RL7009: Ratio of CREF by Peer SCCP 2.2.10

RL7010: Ratio of CREF by Local SCCP 2.2.11






2.2.2 Number of Sent UDT Messages

Counter

L7001: Number of Sent UDT Messages.

Meaning

This counter measures the number of Unitdata (UDT) meassages sent by the SCCP.

Trigger Point

The trigger point is on the BSC side, as shown in Figure 2-1.

Figure 2-1 SCCP Measurement

BSC MSC

A interface

This counter is measured when the SCCP sends a UDT message.

Formula

None.

2.2.3 Number of Received UDT Messages

Counter

L7002: Number of Received UDT Messages.

Meaning

This counter measures the number of UDT meassage received by the SCCP.

Trigger Point


This counter is measured when the SCCP receives a UDT message.

Formula

None.



2 SCCP Measurement




2.2.4 Number of Sent XUDT Messages

Counter

L7003: Number of Sent XUDT Messages.

Meaning

This counter measures the number of Extended Unit Data (XUDT) messages sent by the

SCCP.

Trigger Point


This counter is measured when the SCCP sends an XUDT message.

Formula

None.

2.2.5 Number of Received XUDT Messages

Counter

L7004: Number of Received XUDT Messages.

MeaningThis counter measures the number of XUDT messages received by the SCCP.

Trigger Point


This counter is measured when the SCCP receives an XUDT message.

Formula

None.

2.2.6 Number of Sent CR Messages

Counter

L7005: Number of Sent CR Messages.

Meaning

This counter measures the number of Connection Request (CR) messages sent by the SCCP.






Trigger Point


This counter is measured when the SCCP sends a CR message.

Formula

None.

2.2.7 Number of Received CR Messages

Counter

L7006: Number of Received CR Messages.

MeaningThis counter measures the number of CR messages received by the SCCP.

Trigger Point


This counter is measured when the SCCP receives a CR message.

Formula

None.

2.2.8 Number of Sent CREF Messages

Counter

L7007: Number of Sent CREF Messages.

Meaning

This counter measures the number of Connection Refused (CREF) messages sent by the

SCCP.

Trigger Point


This counter is measured when the SCCP sends a CREF message.

Formula

None.



2 SCCP Measurement




2.2.9 Number of Received CREF Messages

Counter

L7008: Number of Received CREF Messages.

Meaning

This counter measures the number of CREF messages received by the SCCP.

Trigger Point


This counter is measured when the SCCP receives a CREF message.

Formula

None.

2.2.10 Ratio of CREF by Peer SCCP

Counter

RL7009: Ratio of CREF by Peer SCCP.

Meaning

This counter is predefined. It measures the ratio of the Number of Received CREF Messagesto Number of Sent CR Messages.

Trigger Point


This counter is measured when the measurement results are reported in a GP.

Formula

Ratio of CREF by Peer SCCP (%) = Number of Received CREF Messages *100/ Number of

Sent CR Messages.

2.2.11 Ratio of CREF by Local SCCP

Counter

RL7010: Ratio of CREF by Local SCCP.

Meaning

This counter is predefined. It measures the ratio of the Number of Sent CREF Messages to

Number of Received CR Messages.






Trigger Point


This counter is measured when the measurement results are reported in a GP.

Formula

Ratio of CREF by Local SCCP (%) =

Number of Sent CREF Messages *100/ Number of Received CR Messages

2.2.12 Received CC Messages

Counter

L7011: Received CC Messages.

Meaning

This counter measures the number of times the SCCP module receives a Connection Confirm

(CC) message.

Trigger Point


The measurement is triggered when the SCCP module receives a CC message.

Formula

None.

2.2.13 Sent CC Messages

Counter

L7012: Sent CC Messages.

Meaning

This counter measures the number of times the SCCP module sends a CC message.

Trigger Point


The measurement is triggered when the SCCP module sends a CC message.

Formula

None.



2 SCCP Measurement




2.2.14 Sent DT1 Messages

Counter

L7013: Sent DT1 Messages.

Meaning

This counter measures the number of times the SCCP module sends a data form 1 (DT1)

message.

Trigger Point


The measurement is triggered when the SCCP module sends a DT1 message.

Formula

None.

2.2.15 Received DT1 Messages

Counter

L7014: Received DT1 Messages.

MeaningThis counter meausres the number of times the SCCP module receives a DT1 message.

Trigger Point


The measurement is triggered when the SCCP module receives a DT1 message.

Formula

None.

2.2.16 Sent RLSD Messages

Counter

L7015: Sent RLSD Messages.

Meaning

This counter measures the number of times the SCCP module sends a released (RLSD)

message.






Trigger Point


The measurement is triggered when the SCCP module sends a RLSD message.

Formula

None.

2.2.17 Received RLSD Messages

Counter

L7016: Received RLSD Messages.

MeaningThis counter measures the number of times the SCCP module receives an RLSD message.

Trigger Point


The measurement is triggered when the SCCP module receives a RLSD message.

Formula

None.

2.2.18 Sent RLC Messages

Counter

L7017: Sent RLC Messages.

Meaning

This counter measures the number of times the SCCP module sends a release complete (RLC)

message.

Trigger Point


The measurement is triggered when the SCCP module sends an RLC message.

Formula

None.



2 SCCP Measurement




2.2.19 Received RLC Messages

Counter

L7018: Received RLC Messages.

Meaning

This counter measures the number of times the SCCP module receives an RLC message.

Trigger Point


The measurement is triggered when the SCCP module receives a RLC message.

Formula

None.




Performance Counter Reference 3 MTP3 Measurement


3 MTP3 Measurement

About This Chapter


Section Describes

3.1 Overview of MTP3Measurement

The functions and measurement units of MTP3Measurement.

3.2 MTP3 Link Measurement The functions and counters of MTP3 Link Measurement.



3 MTP3 Measurement




3.1 Overview of MTP3 Measurement

Message Transfer Part Level 3 (MTP3) Measurement is used to measure the MTP3 link, linkset, and Destination Signaling Points (DSPs).

Table 3-1 lists the measurement units of MTP3 Measurement.

Table 3-1 MTP3 Measurement Units


MTP3 Link Measurement 3.2

3.2 MTP3 Link Measurement

3.2.1 Overview

MTP3 Link Measurement is used to measure the MTP3 link in normal, faulty, congestion, and

changing status. The measurement includes the number of messages sent and received on thelink, the duration of various states, and the number of status changes.

Table 3-2 lists the counters of MTP3 Link Measurement.

Table 3-2 Counters of MTP3 Link Measurement

Counter Section

TL6001: In-Service Duration of MTP3 Link 3.2.2

L6002: Out-of-Service Duration of MTP3 Link 3.2.3

L6003: Duration of MTP3 Link Fault 3.2.4

L6004: Duration of MTP3 Link Local Inhibition 3.2.5

L6005: Duration of MTP3 Link Remote Inhibition 3.2.6

L6006: Duration of MTP3 Link Remote Processor Fault 3.2.7

L6007: Duration of MTP3 Link Congestion 3.2.8

L6008: Failures of MTP3 Link for All Reasons 3.2.9

L6009: MTP3 Link Local Inhibitions 3.2.10

L6010: MTP3 Link Remote Inhibitions 3.2.11

L6011: MTP3 Link Remote Processor Failures 3.2.12

L6012: MTP3 Link Local Switchovers 3.2.13

L6013: MSUs Sent on MTP3 Link 3.2.14






Counter Section

L6014: MSUs Received on MTP3 Link 3.2.15

L6015: MTP3 Link Congestions 3.2.16

L6016: Discarded MSUs during Link Congestion 3.2.17

L6017: Transfer Inhibition Messages Received on MTP3 Link 3.2.18

L6018: Octets in SIFs or SIOs Sent on MTP3 Link 3.2.19

L6019: Octets in SIFs and SIOs Received on MTP3 Link 3.2.20

L6020: 64 kbit/s Timeslots Seized by Signaling Link 3.2.21

RL6021: Ratio of Transmit Bandwidth to Total Bandwidth 3.2.22

RL6022: Ratio of Receive Bandwidth to Total Bandwidth 3.2.23

L6023: Bytes of MTP2 Message Head in MSU Messages on MTP3 Link 3.2.24

3.2.2 In-Service Duration of MTP3 Link

Counter

L6001: In-Service Duration of MTP3 Link.

MeaningThis counter measures the duration of the MTP3 link in service.

Trigger Point


Figure 3-1 MTP3 Measurement

BSC MSC

A interface

This counter increases by 1 every second when the MTP3 link is in service.

Formula

In-Service Duration of MTP3 Link=

{GP}*{60}) – [Out-of-Service Duration of MTP3 Link]



3 MTP3 Measurement




3.2.3 Out-of-Service Duration of MTP3 Link

Counter

L6002: Out-of-Service Duration of MTP3 Link.

Meaning

This counter measures the Out-of-Service Duration of MTP3 Link.

Trigger Point


This counter increases by 1 every second when the MTP3 link is out of service.

Formula

None.

3.2.4 Duration of MTP3 Link Fault

Counter

L6003: Duration of MTP3 Link Fault.

Meaning

This counter measures the duration of MTP3 link fault.

Trigger Point


This counter increases by 1 every second when the MTP3 link is faulty.

Formula

None.

3.2.5 Duration of MTP3 Link Local Inhibition

Counter

L6004: Duration of MTP3 Link Local Inhibit.

Meaning

This counter measures the duration of the MTP3 link local inhibition.






Trigger Point


This counter increases by 1 every second when the MTP3 link is at the local end inhibition.

Formula

None.

3.2.6 Duration of MTP3 Link Remote Inhibition

Counter

L6005: Duration of MTP3 Link Remote Inhibit.

MeaningThis counter measures the duration of MTP3 link remote inhibition.

Trigger Point


This counter increases by 1 every second when the MTP3 link is in remote inhibition.

Formula

None.

3.2.7 Duration of MTP3 Link Remote Processor Fault

Counter

L6006: Duration of MTP3 Link Remote Processor Fault.

Meaning

This counter measures the duration of MTP3 link remote processor fault.

Trigger Point


This counter increases by 1 every second when the MTP3 link remote processor is faulty.

Formula

None.



3 MTP3 Measurement




3.2.8 Duration of MTP3 Link Congestion

Counter

L6007: Duration of MTP3 Link Congestion.

Meaning

This counter measures the duration of MTP3 link congestion.

Trigger Point


This counter increases by 1 every second when the MTP3 link is congested.

Formula

None.

3.2.9 Failures of MTP3 Link for All Reasons

Counter

L6008: Failures of MTP3 Link for All Reasons.

Meaning

This counter measures the number of MTP3 link failures.

The MTP2 reports link disruption, and then the MTP3 detects the number of link failures

caused by signaling link disruption or link deactivation by the user.

Trigger Point


This counter is measured when:

The MTP2 reports link disruption.

The signaling link is disrupted. Link deactivation by the user succeeds.

Formula

None.

3.2.10 MTP3 Link Local Inhibitions

Counter

L6009: MTP3 Link Local Inhibitions.






Meaning

This counter measures the number of MTP3 link local inhibitions.

The BSC inhibits a link on the LMT. If the inhibition does not lead to service interruption

between the BSC and the MSC, the local inhibition is considered to succeed.

Trigger Point


This counter increases by 1 when the MTP3 link is inhibited at the local end.

Formula

None.

3.2.11 MTP3 Link Remote Inhibitions

Counter

L6010: MTP3 Link Remote Inhibitions.

Meaning

This counter measures the number of MTP3 link remote inhibitions.

The BSC receives a request from the MSC for inhibiting a link. If the inhibition does not lead

to service interruption between the BSC and the MSC, the remote inhibition is considered to

succeed.

Trigger Point


This counter increases by 1 when the MTP3 link is inhibited at the remote end.

Formula

None.

3.2.12 MTP3 Link Remote Processor Failures

Counter

L6011: MTP3 Link Remote Processor Failures.

Meaning

This counter measures the number of failures of the MTP3 link remote processor.

The MTP3 link does not bear services after it receives a message indicating MSC processorfailure or detects an MSC processor failure. The MTP3 link recovers after it receives the

recover indication from the MTP2.



3 MTP3 Measurement




Trigger Point


This counter increases by 1 when the MTP3 link remote processor is faulty.

Formula

None.

3.2.13 MTP3 Link Local Switchovers

Counter

L6012: MTP3 Link Local Switchovers.

MeaningThis counter measures the number of MTP3 link local switchovers.

If a signaling link becomes unavailable, the traffic on this link is transferred to other links.

This procedure is called a changeover.

Trigger Point


This counter increases by 1 when the MTP3 link changeover occurs at the local end.

Formula

None.

3.2.14 MSUs Sent on MTP3 Link

Counter

L6013: MSUs Sent on MTP3 Link.

Meaning

This counter measures the number of Message Signal Units (MSUs) sent on the MTP3 link.

Trigger Point


This counter increases by 1 when the MTP3 link sends an MSU.

Formula

None.






3.2.15 MSUs Received on MTP3 Link

Counter

L6014: MSUs Received on MTP3 Link.

Meaning

This counter measures the number of MSUs received by the MTP3 link.

Trigger Point


This counter increases by 1 when the MTP3 link receives an MSU.

Formula

None.

3.2.16 MTP3 Link Congestions

Counter

L6015: MTP3 Link Congestions.

Meaning

This counter measures the number of MTP3 link congestions.

Trigger Point


This counter increases by 1 every time the MTP3 link is congested.

Formula

None.

3.2.17 Discarded MSUs During Link Congestion

Counter

L6016: Discarded MSUs During Link Congestion

Meaning

This counter measures the number of MSUs that the MTP3 discards during signaling linkcongestion.



3 MTP3 Measurement




Trigger Point


This counter increases by 1 when the MTP3 discards an MSU during signaling link

congestion.

Formula

None.

3.2.18 Transfer Inhibition Messages Received on MTP3 Link

Counter

L6017: Transfer Inhibition Messages Received on MTP3 Link.

Meaning

This counter measures the number of transfer inhibition messages that the MTP3 receives.

If the MSC cannot reach a DSP, it sends the transfer inhibition message to the MTP3.

Trigger Point


This counter increases by 1 when the MTP3 receives a transfer inhibition message from the

remote end.

Formula

None.

3.2.19 Octets in SIFs or SIOs Sent on MTP3 Link

Counter

L6018: Octets in SIFs or SIOs Sent on MTP3 Link.

MeaningThis counter measures the number of octets in the Signaling Information Fields (SIFs) and

Service Information Octets (SIOs) sent on the MTP3 link.

Trigger Point


This counter is measured when the MTP3 link sends SIFs and SIOs that contain octets.

Formula

None.






3.2.20 Octets in SIFs and SIOs Received by MTP3 Link

Counter

L6019: Octets in SIF and SIO Received by MTP3 Link.

Meaning

This counter measures the number of octets in SIFs and SIOs received by the MTP3 link.

Trigger Point


This counter is measured when the MTP3 link receives SIFs and SIOs that contain octets.

Formula

None.

3.2.21 64 kbit/s Timeslots Occupied by a Signaling Link

Counter

L6020: 64 kbit/s Timeslots Occupied by a Signaling Link.

Meaning

This counter measures the number of 64 kbit/s timeslots occupied by a signaling link.

Trigger Point


This counter is measured when a signaling link is set up.

You can skip this counter.

Formula None.

3.2.22 Ratio of Transmit Bandwidth to Total Bandwidth

Counter

RL6021: Ratio of Transmit Bandwidth to Total Bandwidth.



3 MTP3 Measurement




Meaning

This counter measures the ratio of the transmit bandwidth to the total bandwidth of the

signaling link in a GP.

Trigger Point


This counter is measured when the measurement result is reported in a GP.

Formula

Ratio of Transmit Bandwidth to Total Bandwidth=

(MSUs Sent on MTP3 Link * 6 + Octets in SIFs and SIOs Sent by MTP3) * 100/(8192 % 64

kbit/s Timeslots Seized by Signaling Link * GP * 60)

3.2.23 Ratio of Receive Bandwidth to Total Bandwidth

Counter

RL6022: Ratio of Receive Bandwidth to Total Bandwidth.

Meaning

This counter measures the ratio of the receive bandwidth to the total bandwidth of the

signaling link in a GP.

Trigger Point


This counter is measured when the measurement result is reported in a GP.

Formula

Ratio of Receive Bandwidth to Total Bandwidth=

(MSUs Received by MTP3 Link * 6 + Octets in SIFs and SIOs Received by MTP3) *

100/(8192 * 64 kbit/s Timeslots Seized by Signaling Link * GP * 60)

3.2.24 Bytes of MTP2 Message Head in MSU Messages on MTP3Link

Counter

L6023: Bytes of MTP2 Message Head in MSU Messages on MTP3 Link

Meaning

This counter measures the bytes of the MTP2 message head in the MSU messages on the

MTP3 link.






Trigger Point


This counter is measured when an MTP3 link object is created.

Formula

None.




Performance Counter Reference 4 LAPD Measurement


4 LAPD Measurement

About This Chapter


Section Describes

4.1 Overview of LAPDMeasurement

The function and measurement unit of LAPD LinkMeasurement.

4.2 LAPD Link Measurement The function and counters of LAPD Link Measurement.



4 LAPD Measurement




4.1 Overview of LAPD Measurement

LAPD Measurement is used to measure the basic signaling process and the traffic volume onthe Abis and Pb interfaces.

Table 4-1 lists the measurement unit of LAPD Measurement.

Table 4-1 Measurement unit of LAPD Measurement


LAPD Link Measurement 4.2

4.2 LAPD Link Measurement

4.2.1 Overview

The LAPD link is the signaling transfer channel between the BSC and the BTS, and between

the BSC and the PCU.

LAPD Link Measurement is used to measure the number of Q921 protocol frames related tothe LAPD link on the BSC side.

Table 4-2 lists the counters of LAPD Link Measurement.

Table 4-2 Counters of LAPD Link Measurement

Counter Section

L5001: SABME Frames Sent on LAPD Link 4.2.2

L5002: SABME Frames Received on LAPD Link 4.2.3

L5003: REJ Frames Sent on LAPD Link 4.2.4

L5004: REJ Frames Received on LAPD Link 4.2.5

L5005: RNR Frames Sent on LAPD Link 4.2.6L5006: RNR Frames Received on LAPD Link 4.2.7

L5007: I Frames Resent on LAPD Link 4.2.8

L5008: Incorrect I Frames Received on LAPD Link 4.2.9

L5009: I Frames Received on LAPD Link from Application Layer 4.2.10

L5010: I Frames Sent on LAPD Link 4.2.11

L5011: I Frames Received on LAPD Link 4.2.12

L5012: I Frames Discarded on LAPD Link 4.2.13






Counter Section

L5013: UA Frames Sent on LAPD Link 4.2.14

L5014: UA Frames Received on LAPD Link 4.2.15

L5015: UI Frames Received on LAPD Link 4.2.16

4.2.2 SABME Frames Sent on LAPD Link

Counter

L5001: SABME Frames Sent on LAPD Link.

MeaningThis counter measures the number of SABME frames sent on LAPD links.

Trigger Point

The trigger point is on the BSC side, as shown in Figure 4-1

Figure 4-1 LAPD link measurement

BTS BSC

PCU

Abis interface

Pb interface

This counter is measured when the BSC sends SABME frames to the BTS or the PCU duringinitial link setup or link disruption.

Formula

None.

4.2.3 SABME Frames Received on LAPD Link

Counter

L5002: SABME Frames Received on LAPD Link.



4 LAPD Measurement




Meaning

This counter measures the number of SABME frames received on LAPD links.

Trigger PointThe trigger point is on the BSC side, as shown in Figure 4-1.

This counter is measured when the BSC receives SABME frames from the BTS or the PCU

after LAPD link setup.

Formula

None.

4.2.4 REJ Frames Sent on LAPD Link

Counter

L5003: REJ Frames Sent on LAPD Link.

Meaning

This counter measures the number of REJ frames sent on LAPD links.

Trigger Point


This counter is measured when the BSC sends REJ frames to the BTS or the PCU after theLAPD link receives incorrect frames.

Formula

None.

4.2.5 REJ Frames Received on LAPD Link

Counter

L5004: REJ Frames Received on LAPD Link

Meaning

This counter measures the number of REJ frames received on LAPD links.

Trigger Point


This counter is measured when the BSC receives REJ frames from the BTS or the PCU.






Formula

None.

4.2.6 RNR Frames Sent on LAPD LinkCounter

L5005: RNR Frames Sent on LAPD Link.

Meaning

This counter measures the number of RNR frames sent on LAPD links.

Trigger Point


This counter is measured when the BSC sends RNR frames to the BTS or the PCU after it

receives RR frames when it is busy.

Formula

None.

4.2.7 RNR Frames Received on LAPD Link

Counter

L5006: RNR Frames Received on LAPD Link.

Meaning

This counter measures the number of RNR frames received on LAPD links.

Trigger Point


This counter is measured when the BSC receives RNR frames from the BTS or the PCU.

Formula

None.

4.2.8 I Frames Resent on LAPD Link

Counter

L5007: I Frames Resent on LAPD Link.



4 LAPD Measurement




Meaning

This counter measures the number of I frames resent on LAPD links.

Trigger PointThe trigger point is on the BSC side, as shown in Figure 4-1.

This counter is measured when the BSC resends I frames to the BTS or the PCU.

Formula

None.

4.2.9 Incorrect I Frames Received on LAPD Link

CounterL5008: Incorrect I Frames Received on LAPD Link.

Meaning

This counter measures the number of incorrect frames received on LAPD links.

Trigger Point


This counter is measured when the BSC receives incorrect I frames from the BTS or the PCU.

Formula

None.

4.2.10 I Frames Received on LAPD Link from Application Layer

Counter

L5009: I Frames Received by LAPD Link from Application Layer

Meaning

This counter measures the number of I frames that the LAPD link receives from the

application layer.

Trigger Point


This counter is measured when the LAPD link receives I frames from the application layer.






Formula

None.

4.2.11 I Frames Sent on LAPD LinkCounter

L5010: I Frames Sent on LAPD Link.

Meaning

This counter measures the number of I frames sent on the LAPD link.

Trigger Point


This counter is measured when the LAPD link sends I frames to the BTS or the PCU.

Formula

None.

4.2.12 I Frames Received by LAPD Link

Counter

L5011: I Frames Received by LAPD Link.

Meaning

This counter measures the number of I frames received by the LAPD link.

Trigger Point


This counter is measured when the LAPD link receives I frames from the BTS or the PCU.

Formula

None.

4.2.13 I Frames Discarded by LAPD Link

Counter

L5012: I Frames Discarded by LAPD Link.

Meaning

This counter measures the number of I frames discarded by the LAPD link.



4 LAPD Measurement




Trigger Point


This counter is measured when the LAPD link discards the I frames sent from the application

layer if the I frame queue overflows.

Formula

None.

4.2.14 UA Frames Sent on LAPD Link

Counter

L5013: UA Frames Sent on LAPD Link.

Meaning

This counter measures the number of UA frames sent on the LAPD link.

Trigger Point


This counter is measured when the LAPD link sends UA frames to the BTS or the PCU after

it receives SABME frames.

Formula None.

4.2.15 UA Frames Received by LAPD Link

Counter

L5014: UA Frames Received by LAPD Link.

Meaning

This counter measures the number of UA frames received by the LAPD link.

Trigger Point


This counter is measured when the LAPD link receives UA frames from the BTS or the PCU.

Formula

None.






4.2.16 UI Frames Received by LAPD Link

Counter

L5015: UI Frames Received by LAPD Link.

Meaning

This counter measures the number of UI frames received by the LAPD link.

Trigger Point


This counter is measured when the LAPD link receives UI frames sent from the BTS or thePCU.

Formula

None.




Performance Counter Reference 5 System Load Measurement


5 System Load Measurement

About This Chapter


Section Describes

5.1 Overview of System LoadMeasurement

Describes System Load Measurement and itsmeasurement unit.

5.2 CPU Usage Measurement Describes CPU Usage Measurement and its counters.



5 System Load Measurement




5.1 Overview of System Load Measurement

System Load Measurement refers to the measurement of the system load of the BSC. Thesystem load refers to the CPU usage of the BSC boards and the GBAM.

The CPU usage shows the load situation of the system, but a 100% CPU usage does not meanthat the CPU has reached its limitation and cannot process extra services. The BSC has acertain buffer capability, which can save extra service requests. As long as there is still a

buffer area in the host, the BSC continues to process new services. Therefore, high CPU usage

does not necessarily mean that the BSC is faulty, even if the CPU usage reaches 80%occasionally.

The buffer area of the BSC is limited. If the CPU usage is high for a long time, a transient

exhaustion of the buffer area may occur because there are sharp bursts of service requests.The BSC will abandon new service requests.

Table 5-1 lists the measurement unit of System Load Measurement.

Table 5-1 Measurement unit of System Load Measurement


CPU Usage Measurement 5.2

5.2 CPU Usage Measurement5.2.1 Overview

CPU Usage Measurement is used to measure the CPU usage of BSC boards and the GBAM.

Table 5-2 lists the counters of CPU Usage Measurement.

Table 5-2 Counters of CPU Usage Measurement

Counter Section

AR9702: Mean CPU Usage 5.2.2

R9703: Maximum CPU Usage 5.2.3

5.2.2 Mean CPU Usage

Counter

AR9702: Mean CPU Usage




Performance Counter Reference 5 System Load Measurement


Meaning

This counter measures the mean ratio of the busy time of the CPU in a Granularity Period

(GP). The counter shows the load situation of the BSC.

Trigger Point

None.

Formula

Mean CPU Usage = [Accumulated CPU Usage] / [Number of CPU Usage Measurements]

After a board or the GBAM runs for 30 seconds, the BSC measures the CPU usage every second and

obtains Accumulated CPU Usage in a GP. Number of CPU Usage Measurements refers to the number oftimes the BSC measure the CPU usage.

5.2.3 Maximum CPU Usage

Counter

R9703: Maximum CPU Usage

Meaning

This counter measures the maximum CPU usage in a GP.

Trigger PointThe BSC measures the CPU usage every second in a GP and compares it with the current

value. The measurement is triggered when the BSC detects the maximum CPU usage in a GP.

Formula

None.




Performance Counter Reference 6 BTSM Management


6 BTSM Management

About This Chapter


Section Describes

6.1 Overview of BTSMMeasurement

The measurement units of BTSM Measurement.

6.2 BTS State Measurement per BTS

The function and counters of BTS State Measurement perBTS.

6.3 BTS ConfigurationMeasurement per BM Subrack The function and counters of BTS ConfigurationMeasurement per BM Subrack.

6.4 Cell State Measurement per Cell

The function and counters of Cell State Measurement perCell.

6.5 Cell ConfigurationMeasurement per BM Subrack

The function and counters of Cell ConfigurationMeasurement per BM Subrack.

6.6 TRX State Measurement

per TRX

The function and counters of TRX State Measurement per

TRX.

6.7 TRX Configuration

Measurement per BM Subrack

The function and counters of TRX Configuration

Measurement per BM Subrack.

6.8 CRC Error Measurement per BTS

The function and counters of CRC Error Measurement per BTS.

6.9 CRC Serious Error

Measurement per BTS

The function and counters of CRC Serious Error

Measurement per BTS.

6.10 LAPD Link Measurement

at the BTS

The function and counters of LAPD Link Measurement at

the BTS.



6 BTSM Management




6.1 Overview of BTSM Measurement

Base Transceiver Station Management (BTSM) measurement is used to measure the state ofthe BTS, cell, and TRX, and link communication state between the BSC and the BTS.

Table 6-1 lists the measurement units of BTSM management.

Table 6-1 Measurement units of BTSM Measurement


BTS State Measurement per BTS 6.2

BTS Configuration Measurement per BM Subrack 6.3

Cell State Measurement per Cell 6.4

Cell Configuration Measurement per BM Subrack 6.5

TRX State Measurement per TRX 6.6

TRX Configuration Measurement per BM Subrack 6.7

CRC Error Measurement per BTS 6.8

CRC Serious Error Measurement per BTS 6.9

LAPD Link Measurement at the BTS 6.10

BM: Basic Module

BM subrack = GSM Main Processing Subrack (GMPS)/GSM Extended Processing Subrack (GEPS)

6.2 BTS State Measurement per BTS

6.2.1 Overview

BTS State Measurement per BTS is used to measure the BTS reset state, services state, andOML communication state.

Table 6-2 lists the counters of BTS State Measurement per BTS.

Table 6-2 Counters of BTS State Measurement per BTS

Counter Section

R2701: Successful BTS Initializations 6.2.2

R2702: Failed BTS Initializations 6.2.3

L2130: BTS OML Disruption Duration 6.2.4

R273: BTS Out-of-Service Duration 6.2.5






Counter Section

TR273: BTS Availability 6.2.6

CR273: BTS In-Service Duration 6.2.7

6.2.2 Successful BTS Initializations

Counter

R2701: Successful BTS Initializations.

Meaning

This counter measures the number of successful BTS initializations.

Trigger Point

This counter is measured when BTS initialization succeeds.

Formula

None.

6.2.3 Failed BTS Initializations

Counter

R2702: Failed BTS Initializations.

Meaning

This counter measures the number of failed BTS initializations.

Trigger Point


BTS initialization fails.

BTS initialization fails for the second time.

Flow control is generated during BTS initialization.

Formula

None.



6 BTSM Management




6.2.4 BTS OML Disruption Duration

Counter

L2130: BTS OML Disruption Duration.

Meaning

When the OML between the BTS and the BSC is faulty, the OML of this BTS is considered

disrupted, and the duration of the disruption is measured.

Trigger Point

This counter is measured when the BTS OML is disrupted.

Formula None.

6.2.5 BTS Out-of-Service Duration

Counter

R273: Duration of Site Out of Service.

Meaning

When the main Broadcast Control Channels (BCCHs) of all the cells under the BTS are faulty,the BTS is considered to be out of service and the duration is measured.

Trigger Point

This counter is measured when the BSC detects faults in the main BCCHs of all the cells

under one BTS.

In some occasions, this counter may have an error of five seconds (the sampling period).

Formula

None.

6.2.6 BTS Availability

Counter

TR273: BTS Availability.

Meaning

This counter measures the BTS availability in a Granularity Period (GP).






Trigger Point

None.

Formula[BTS Availability] = [BTS In-Service Duration]*{100}/({GP}*{60})

GP unit: minute

6.2.7 BTS In-Service Duration

Counter

CR273: BTS In-Service Duration.

Meaning

This counter measures the duration of the BTS in service in a GP.

Trigger Point

None.

Formula

[BTS In-Service Duration] = {GP}*{60} – [BTS Out-of-Service Duration]

GP unit: minute

6.3 BTS Configuration Measurement per BM Subrack

6.3.1 OverviewBTS Configuration Measurement per BM Subrack is used to measure the activated andavailable BTSs.

Table 6-3 lists the counters of BTS Configuration Measurement per BM Subrack.

Table 6-3 Counters of BTS Configuration Measurement per BM Subrack

Counter Section

R260: Activated BTSs 6.3.2

R261: Available BTSs 6.3.3



6 BTSM Management




6.3.2 Activated BTSs

Counter

R260: Activated BTSs.

Meaning

This counter measures the number of activated BTSs in data configuration.

Trigger Point

None.

Formula

None.

6.3.3 Available BTSs

Counter

R261: Available BTSs.

Meaning

This counter measures the number of BTSs that are in the ENABLE state.

Trigger Point

The BSC queries the operation state of the BTS regularly and measures the number ofactivated BTSs.

Formula

None.

6.4 Cell State Measurement per Cell

6.4.1 Overview

Cell State Measurement per Cell is used to measure the cell reset state, cell service state, andmutual aid state.

Table 6-4 lists the counters of Cell State Measurement per Cell.






Table 6-4 Counters of Cell State Measurement per Cell

Counter Section

R3701: Successful Cell Initializations 6.4.2

R3702: Failed Cell Initializations 6.4.3

R3710: Cell BCCH Mutual Aid 6.4.4

R3711: Recoveries after Cell BCCH Mutual Aid 6.4.5

R3720: Cell Baseband Hopping Mutual Aid 6.4.6

R3721: Recoveries after Cell Baseband Hopping Mutual Aid 6.4.7

R373: Cell Out-of-Service Duration 6.4.8

TR373: Cell Availability Duration 6.4.9

CR373: Cell In-Service Duration 6.4.10

6.4.2 Successful Cell Initializations

Counter

R3701: Successful Cell Initializations.

Meaning

This counter measures the number of successful cell initializations.

Trigger Point

This counter is measured when cell initialization succeeds.

Formula

None.

6.4.3 Failed Cell Initializations

Counter

R3702: Failed Cell Initializations.

Meaning

This counter measures the number of failed cell initializations.

Trigger Point




6 BTSM Management




Cell initialization fails.

Cell initialization fails for the second time.

Flow control is generated during cell initialization.

Formula

None.

6.4.4 Cell BCCH Mutual Aid

Counter

R3710: Cell BCCH Mutual Aid.

Meaning

If the main BCCH of a cell is faulty, to ensure the continuity of services, the BSC allocates a

TCH of another TRX as a new BCCH. This is called BCCH mutual aid. This countermeasures the number of BCCH mutual aid.

Trigger Point

If the main BCCH of a cell is faulty, the BSC allocates a TCH of another TRX as a new

BCCH and accumulates the BCCH mutual aid.

Formula

None.

6.4.5 Recoveries after Cell BCCH Mutual Aid

Counter

R3711: Recoveries after Cell BCCH Mutual Aid.

Meaning

When the BSC detects that the original faulty TRX recovers after the mutual aid, the BSC

adjusts the BCCH back to the original TRX.

Trigger Point

When the BSC detects that the original faulty TRX recovers after the mutual aid, the BSC

adjusts the BCCH back to the original TRX and accumulates the recoveries.

Formula

None.






6.4.6 Cell Baseband Hopping Mutual Aid

Counter

R3720: Cell Baseband Hopping Mutual Aid.

Meaning

If the TRXs that are involved in baseband hopping are faulty, the baseband hopping function

of this cell is disabled.

Trigger Point

If the TRXs that are involved in baseband hopping are faulty, the BSC disables the baseband

hopping function of this cell and accumulates the baseband hopping mutual aid.

Formula

None.

6.4.7 Recoveries After Cell Baseband Hopping Mutual Aid

Counter

R3721: Recoveries After Cell Baseband Hopping Mutual Aid.

Meaning

If the BSC detects that all the faulty TRXs that are involved in baseband hopping are

recovered, the baseband hopping function is resumed.

Trigger Point

After cell baseband hopping mutual aid, the BSC detects the original faulty TRXs at regular

intervals. If these faulty TRXs are recovered, the baseband hopping function is resumed, and

the recoveries after cell baseband hopping mutual aid are accumulated.

Formula

None.

6.4.8 Cell Out-of-Service Duration

Counter

R373: Cell Out-of-Service Duration.

Meaning

If the main BCCH of a cell is faulty, this cell is considered to be out of service. This counter

measures the Cell Out-of-Service Duration.



6 BTSM Management




Trigger Point

This counter is measured when the BSC detects that the main BCCH of a cell is faulty.


Formula

None.

6.4.9 Cell Availability

Counter

TR373: Cell Availability

Meaning

This counter is used to measure the cell availability in a GP.

Trigger Point

None.

Formula

[Cell Availability] = [Cell In-Service Duration]*{100}/({GP}*{60})

GP unit: minute

6.4.10 Cell In-Service Duration

Counter

CR373: Cell In-Service Duration.

Meaning

This counter measures the duration of a cell in service in a GP.

Trigger Point

None.

Formula

[Cell In-Service Duration] = {GP}*{60} – [Cell Out-of-Service Duration]

GP unit: minute






6.5 Cell Configuration Measurement per BM Subrack

6.5.1 Overview

Configuration Measurement <BM Subrack> is used to measure the number of activated cellsand available cells.

Table 6-5 lists the counters of Cell Configuration Measurement per BM Subrack.

Table 6-5 Counters of Cell Configuration Measurement per BM Subrack

Counter Section

R360: Activated cells 6.5.2

R361: Available cells 6.5.3

6.5.2 Activated Cells

Counter

R360: Activated Cells.

Meaning

This counter measures the number of activated cells in data configuration.

Trigger Point

None.

Formula

None.

6.5.3 Available Cells

CounterR361: Available Cells.

Meaning

This counter measures the number of cells whose operation state is ENABLE.

Trigger Point

The BSC queries the operation state of cells at regular intervals and measures the number of

activated cells.



6 BTSM Management




Formula

None.

6.6 TRX State Measurement per TRX

6.6.1 Overview

TRX State Measurement per TRX is used to measure the TRX Out-of-Service Duration.

Table 6-6 lists the counter of TRX State Measurement per TRX.

Table 6-6 Counters of TRX State Measurement per TRX

Counter Section

R473: TRX Out-of-Service Duration 6.6.2

6.6.2 TRX Out-of-Service Duration

Counter

R473: TRX Out-of-Service Duration.

MeaningThis counter measures the out-of-service duration of the TRX.

The TRX is considered out of service when all the channels on the TRX cannot provide

services.

Trigger Point

This counter is measured when the BSC detects that none of the TCHs are available.


Formula

None.






6.7 TRX Configuration Measurement per BM Subrack

6.7.1 Overview

TRX Configuration Measurement per BM Subrack is used to measure the number of activatedand available TRXs, and the TRX availability.

Table 6-7 lists the counters of TRX Configuration Measurement per BM Subrack.

Table 6-7 Counters of TRX Configuration Measurement per BM Subrack

Counter Section

R460: Activated TRXs 6.7.2

R461: Available TRXs 6.7.3

RR461: TRX Availability 6.7.4

6.7.2 Activated TRXs

Counter

R460: Activated TRXs.

Meaning

This counter measures the number of activated TRXs in data configuration.

Trigger Point

None.

Formula

None.

6.7.3 Available TRXs

Counter

R461: Available TRXs.

Meaning

This counter measures the number of TRXs whose operation state is ENABLE.

Trigger Point

This counter is measured when the BSC queries the operation state of TRXs at regular

intervals and measures the number of available TRXs.



6 BTSM Management




Formula

None.

6.7.4 TRX AvailabilityCounter

RR461: TRX Availability

Meaning

This counter measures the ratio of the number of available TRXs to the number of the

configured TRXs.

Trigger Point

None.

Formula

[TRX Availability] = [Available TRXs]*{100}/[Configured TRXs]

6.8 CRC Error Measurement per BTS

6.8.1 OverviewCRC Error Measurement per BTS is used to measure the duration of CRC error on E1 portson the Abis interface. This measurement unit reflects the communication status of E1 cables

between the BSC and the BTS.

Table 6-8 lists the counter of CRC Error Measurement per BTS.

Table 6-8 Counters of CRC Error Measurement per BTS

Counter Section

Duration of CRC Error on Ports 0 Through 23 6.8.2

6.8.2 Duration of CRC Error on Ports 0 Through 23

Counter

Table 6-9 lists the counters of Duration of CRC Error on Ports 0 Through 23.






Table 6-9 Counters of Duration of CRC Error on Ports 0 Through 23

Number Counter

1 L2100A: Duration of CRC Error on Port 0
























Meaning

The BSC and the BTS communicate through E1 cables.

The BTS detects whether there are CRC errors on E1 ports every second. If an error occurs,the number on the counter increases by one, and the total is reported to the BSC every five

minutes. Then the BSC accumulates the reported numbers to get the value in a GP.



6 BTSM Management




This counter measures the duration of CRC errors on E1 ports. The greater the value is, theworse the transmission quality will be.

Trigger Point

The BTS reports the message containing CRC authentication results to the BSC every five

minutes. Then the BSC measures this counter according to the port number in the message.

Formula

None.

6.9 CRC Serious Error Measurement per BTS

6.9.1 OverviewCRC Serious Error Measurement per BTS is used to measure the duration of CRC seriouserror on E1 ports on the Abis interface. This measurement unit reflects the communication

status of E1 cables between the BSC and the BTS.

Table 6-10 lists the counter of CRC Serious Error Measurement per BTS.

Table 6-10 Counter of CRC Serious Error Measurement per BTS

Counter Section

Duration of Serious CRC Error on Ports 0 Through 23 6.9.2

6.9.2 Duration of Serious CRC Error on Ports 0 Through 23

Counter

Table 6-11 lists the counters of Duration of Serious CRC Error on Ports 0 Through 23.

Table 6-11 Counters of Duration of Serious CRC Error on Ports 0 Through 23

Number Counter

1 L2100B: Duration of Serious CRC Error on Port 0












Number Counter


















Meaning

The BSC and the BTS communicate through E1 cables.

The BTS detects whether there are CRC serious errors on E1 ports every second. If a seriouserror occurs, the number on the counter increases by one, and the total is reported to the BSC

every five minutes. Then the BSC accumulates the reported numbers to get the value in a GP.

This counter measures the duration of CRC serious errors on E1 ports. The greater the value is,the worse the transmission quality will be.

Trigger Point

The BTS reports the message containing CRC authentication results to the BSC every fiveminutes. Then the BSC measures this counter according to the port number in the message.

Formula

None.



6 BTSM Management




6.10 LAPD Link Measurement at the BTS

6.10.1 Overview

LAPD Link Measurement at the BTS is used to measure the number of various frames sent between the BSC and the BTS.

Table 6-12 lists the counters of LAPD Link Measurement at the BTS.

Table 6-12 Counters of LAPD Link Measurement at the BTS

Counter Section

L5101: SABME Frames Sent by the BTS on LAPD Link 6.10.2

L5102: SABME Frames Received by the BTS on LAPD Link 6.10.3

L5103: BTS-Sent Rejects to the LAPD Setup Requests 6.10.4

L5104: BTS-Received Rejects to the LAPD Setup Requests 6.10.5

L5105: RNR Frames Sent by the BTS on LAPD Link 6.10.6

L5106: RNR Frames Received by the BTS on LAPD Link 6.10.7

L5107: I Frames Resent by the BTS on LAPD Link 6.10.8

L5108: NRERR Frames Received by the BTS on LAPD Link 6.10.9

L5109: L3 Data Requests Received by BTS on LAPD Link 6.10.10

L5110: I Frames Sent by the BTS on LAPD Link 6.10.11L5111: I Frames Received by the BTS on LAPD Link 6.10.12

L5112: Queue Overflows of Messages Sent by BTS on LAPD Link 6.10.13

L5113: Erroneous Long Frames Received by BTS Physical Layer on LAPDLink

6.10.14

L5114: Erroneous Octet Received by BTS Physical Layer on LAPD Link 6.10.15

L5115: Discarded Series Received by BTS Physical Layer on LAPD Link 6.10.16

L5116: Number of Times the BTS Receives CRC Errors on LAPD Link 6.10.17

L5117: L1 and L2 Overflows on LAPD Link of the BTS 6.10.18

L5118: Total Frames Received by the BTS Physical Layer on LAPD Link 6.10.19

6.10.2 SABME Frames Sent by the BTS on LAPD Link

Counter

L5101: SABME Frames Sent by the BTS on LAPD Link.






Meaning

This counter measures the number of SABME frames that the BTS L2 sends on LAPD Link.

The SABME frame is sent to request for link setup.

During the startup and normal operation of the BSC, the BTS does not initiate a link setuprequest or send SABME frames to the BSC. If the LAPD status is converted to multi-frame

(Multi_I) setup, the BTS may send SABME frames to the BSC.

If the physical uplink is disrupted, the measurement result cannot be sent to the BSC and thiscounter does not increase.

Trigger Point

This counter is measured when the BTS L2 sends an SAMBE frame on LAPD Link.

Formula None.

6.10.3 SABME Frames Received by the BTS on LAPD Link

Counter

L5102: SABME Frames Received by the BTS on LAPD Link.

Meaning

This counter measures the number of SABME frames that the BTS L2 receives on LAPDLink.

The SABME frame is sent to request for link setup.

After the BSC starts up, the link status is converted to multi-frame (Multi_I) setup through theframe interaction between the L2 entities of the BSC and the BTS. During this procedure, the

Abis interface board sends the SABME frame to the BTS L2. If the link is abnormal or the

link between the BSC and the BTS is disrupted, the BSC sends the SABME frame to requestfor link setup.

If the physical uplink is disrupted, the BTS does not receive frames from the BSC and this

counter does not increase.

If the physical downlink is disrupted, the measurement result cannot be sent to the BSC andthis counter does not increase.

Trigger Point

This counter is measured when the BTS L2 receives an SAMBE frame on LAPD Link.

Formula

None.



6 BTSM Management




6.10.4 BTS-Sent Rejects to the LAPD Setup Requests

Counter

L5103: BTS-Sent Rejects to the LAPD Setup Requests.

Meaning

This counter measures the number of REJ frames that the BTS L2 sends on LAPD Link.

The REJ frame is a monitoring frame, which means that the received I frame (information

frame) is rejected. The REJ frame contains the serial number of the expected I Frame.

I frames are numbered in sequence. The BTS L2 has records for received and sent I frames.

Normally, the value of this counter should be 0. If the BTS receives an I frame with anunexpected number, it sends a REJ frame to the BSC, and this counter increases by 1.

If the physical uplink is disrupted, the measurement result cannot be sent to the BSC and this


Trigger Point

This counter is measured when the BTS L2 sends a REJ frame on LAPD Link.

Formula

None.

6.10.5 BTS-Received Rejects to the LAPD Setup Requests

Counter

L5104: BTS-Received Rejects to the LAPD Setup Requests.

Meaning

This counter measures the number of REJ frames that the BTS L2 receives on LAPD Link.

The REJ frame is a monitoring frame, which means that the received I frame (informationframe) is rejected. The REJ frame contains the serial number of the expected I frame.

I frames are numbered in sequence. The BTS L2 has records for received and sent I frames.

Normally, the value of this counter should be 0. If the BSC receives an I frame with an

unexpected number, it sends a REJ frame to the BTS, and this counter increases by 1.


Trigger Point

This counter is measured when the BTS L2 sends a REJ frame on LAPD Link.






Formula

None.

6.10.6 RNR Frames Sent by the BTS on LAPD LinkCounter

L5105: RNR Frames Sent by the BTS on LAPD Link.

Meaning

This counter measures the number of RNR frames that the BTS L2 sends on LAPD Link.

The RNR frame is a monitoring frame, which means that the local receiver is busy and is notready to receive the next I frame. The RNR frame contains the serial number of the expected I

frame. The peer end stops sending I frames on receiving the RNR frame.

If the BTS receiver is busy, the BTS sends an RNR frame to the BSC. The BSC stops sendingI frames on receiving the RNR frame.

If the physical uplink is disrupted, the measurement result cannot be sent to the BSC and this


Trigger Point

This counter is measured when the BTS L2 sends an RNR frame on LAPD Link.

Formula

None.

6.10.7 RNR Frames Received by the BTS on LAPD Link

Counter

L5106: RNR Frames Received by the BTS on LAPD Link.

Meaning

This counter measures the number of RNR frames that the BTS L2 receives on LAPD Link.

The RNR frame is a monitoring frame, which means that the local receiver is busy and is notready to receive the next I frame. The RNR frame contains the serial number of the expected I

frame. The peer end stops sending I frames on receiving RNR frames.

If the BSC receiver is busy, the BSC sends an RNR frame to the BTS. The BTS stops sendingI frames on receiving the RNR frame.


Trigger Point

This counter is measured when the BTS L2 sends an RNR frame on LAPD Link.



6 BTSM Management




Formula

None.

6.10.8 I Frames Resent by the BTS on LAPD LinkCounter

L5107: I Frames Resent by the BTS on LAPD Link.

Meaning

This counter measures the number of I frames that the BTS L2 resends on LAPD Link.

If the BTS receives a REJ frame from the BSC, it means that an error occurs when the BSCreceives I frames. Then the BTS resends this I frame and all the I frames with numbers bigger

than this number.

If the BTS receives an RNR frame from the BSC, it means that the L2 receiver of the BSC is busy and cannot receive I frames. Then the BTS resends this I frame and all the I frames with

numbers bigger than this number after the L2 receiver of the BSC is free.

This counter increases by 1 when the BTS resends an I frame.


Trigger Point

This counter is measured when the BTS L2 resends an I frame on LAPD Link.

Formula

None.

6.10.9 NRERR Frames Received by the BTS on LAPD Link

Counter

L5108: NRERR Frames Received by the BTS on LAPD Link.

Meaning

This counter measures the number of frames that the BTS LAPD Link receives whose

numbers are different from those of the to-be-sent frames.

The RR frames, RNR frames, REJ frames, and I frames sent from the BSC to the BTS containthe numbers of the to-be-sent I frames. The BTS records the number range of the to-be-sent I

frames. If the received I frame number is not within the range, this number is consideredincorrect, and this counter increases by 1.

If the physical uplink is disrupted, the measurement result cannot be sent to the BSC, and this







Trigger Point

This counter is measured when the BTS L2 receives LAPD Link frames whose numbers are

different from those of the to-be-sent frames.

Formula

None.

6.10.10 L3 Data Requests Received by BTS on LAPD Link

Counter

L5109: L3 Data Requests Received by BTS on LAPD Link.

Meaning

This counter measures the number of requests that are sent from LAPD Link L3 to L2 and

contain the to-be-confirmed messages.

The requests sent from L3 consist of the messages that need or need not be confirmed. The

former are transferred in L2 I frames and the latter are transferred in L2 UI frames.

All the L3 messages sent by the BTS except for the MR need be confirmed. If the BTS L2receives one request containing the to-be-confirmed message from L3, this counter increases

by 1.



Trigger Point

This counter is measured when the BTS L2 LAPD Link receives the request containing the to- be-confirmed message from L3.

Formula

None.

6.10.11 I Frames Sent by the BTS on LAPD Link

Counter

L5110: I Frames Sent by the BTS on LAPD Link.

Meaning

This counter measures the number of I frames sent by the BTS L2 on LAPD Link.

The requests sent from L3 consist of the messages that need or need not be confirmed. Theformer are transferred in L2 I frames and the latter transferred in L2 UI frames.

All the L3 messages sent by the BTS except for the MR need be confirmed. When the BTS

L2 sends an I frame on LAPD Link, this counter increases by 1.



6 BTSM Management




If the physical uplink is disrupted, the measurement result cannot be sent to the BSC, and thiscounter does not increase.

Trigger Point

This counter is measured when the BTS L2 sends an I frame on LAPD Link.

Formula

None.

6.10.12 I Frames Received by the BTS on LAPD Link

Counter

L5111: I Frames Received by the BTS on LAPD Link.

Meaning

This counter measures the number of I frames the BTS L2 receives on LAPD Link.

The requests sent from L3 consist of the messages that need or need not be confirmed. Theformer are transferred in L2 I frames and the latter are transferred in L2 UI frames.

All the L3 messages sent by the BSC need be confirmed. If the BTS L2 receives one I frame,

this counter increases by 1.


Trigger Point

This counter is measured when the BTS L2 receives an I frame on LAPD Link.

Formula

None.

6.10.13 Queue Overflows of Messages Sent by BTS on LAPD Link

CounterL5112: Queue Overflows of Messages Sent by BTS on LAPD Link.

Meaning

The requests sent from L3 consist of the messages that need or need not be confirmed. The

former are transferred in L2 I frames and the latter are transferred in L2 UI frames.

When the BTS L2 sends the to-be-confirmed messages through I frames, it puts the I frames

in a message queue and sends them in sequence.

If too many messages are to be sent within a short period of time by L3, the message queue

overflows, messages are lost, and this counter increases by 1.







Trigger Point

This counter is measured when the message queue of I frames sent by the BTS L2 on LAPD

Link overflows.

Formula

None.

6.10.14 Erroneous Long Frames Received by BTS Physical Layeron LAPD Link

CounterL5113: Erroneous Long Frames Received by BTS Physical Layer on LAPD Link.

Meaning

The L3 messages are sent through L2 to L1. Then L1 sends the messages in the form of

physical frames. If an error occurs when L1 receives a long frame, this frame is discarded, andthis counter increases by 1.


Trigger Point

This counter is measured when the BTS L1 erroneously receives an LAPD Link long frame.

Formula

None.

6.10.15 Erroneous Octet Received by BTS Physical Layer on LAPDLink

Counter

L5114: Erroneous Octet Received by BTS Physical Layer on LAPD Link

Meaning


physical frames. If the received frame contains incorrect bytes, this frame is discarded, andthis counter increases by 1.





6 BTSM Management




Trigger Point

This counter is measured when the BTS L1 receives frames containing byte errors.

Formula None.

6.10.16 Discarded Series Received by BTS Physical Layer onLAPD Link

Counter

L5115: Discarded Series Received by BTS Physical Layer on LAPD Link.

MeaningThe L3 messages are sent through L2 to L1. Then L1 sends the messages in the form of

physical frames. If the received frame contains the discarded series, the frame is discarded,and this counter increases by 1.



Trigger Point

This counter is measured when the BTS L1 receives frames containing discarded series.

Formula

None.

6.10.17 Number of Times the BTS Receives CRC Errors on LAPDLink

Counter

L5116: Number of Times the BTS Receives CRC Errors on LAPD Link.

Meaning


physical frames. If L1 receives a frame containing CRC errors, the frame is discarded, and the

counter increases by 1.


Trigger Point

This counter is measured when the BTS L1 receives a frame containing CRC errors.






Formula

None.

6.10.18 L1 and L2 Overflows on LAPD Link of the BTSCounter

L5117: L1 and L2 Overflows on LAPD Link of the BTS.

Meaning

The BTS receives physical frames through L1, and then puts them in the queue from L1 to L2.

If large amount of information is received within a short period of time, the message queueoverflows, messages are lost, and this item increases by 1.


Trigger Point

This counter is measured when the message queue from BTS OML L1 to L2 overflows.

Formula

None.

6.10.19 Total Frames Received by the BTS Physical Layer on

LAPD Link

Counter

L5118: Total Frames Received by the BTS Physical Layer on LAPD Link.

Meaning

The BTS receives the physical frames through layer 1 (L1) and then puts the physical frames

in the queue from L1 to L2.

This counter increases by 1 when L1 receives an LAPD Link frame.

If the physical uplink is disrupted, the measurement cannot be sent to the BSC and thiscounter does not increase.

Trigger Point

This counter is measured when BTS L1 receives an LAPD Link frame.

Formula

None.




Performance Counter Reference 7 Resources Measurement


7 Resources Measurement

About This Chapter


Section Describes

7.1 Overview of ResourcesMeasurement

The functions and measurement units of ResourcesMeasurement.

7.2 A Interface CircuitMeasurement per DPC

The functions and counters of A Interface CircuitMeasurement per DPC.

7.3 TC Measurement per DPC The functions and counters of TC Measurement per DPC.

7.4 Pb Interface Circuit

Measurement per PCU

The functions and counters of Pb Interface Circuit

Measurement per PCU.

7.5 Ater Interface Circuit

Measurement per BM Subrack

The functions and counters of Ater Interface Circuit

Measurement per BM Subrack.







7.1 Overview of Resources Measurement

Resources Measurement is used to measure the state of circuits on the A interface, Pbinterface, and Ater interface, and the TC resources.

Table 7-1 lists the measurement units of Resources Measurement.

Table 7-1 Measurement Units of Resources Measurement


A Interface Circuit Measurement per DPC 7.2

TC Measurement per DPC 7.3

Pb Interface Circuit Measurement per PCU 7.4

Ater Interface Circuit Measurement per BM Subrack 7.5

DPC: Destination Signaling Point Code

BM: Base Module

BM subrack = GSM Main Processing Subrack (GMPS)/GSM Extended Processing Subrack (GEPS)

7.2 A Interface Circuit Measurement per DPC

7.2.1 Overview

A Interface Circuit Measurement per DPC is used to measure the circuits in a faulty, busy, idle,

uninstalled, and maintenance state.

Table 7-2 lists counters of A Interface Circuit Measurement per DPC.

Table 7-2 Counters of A Interface Circuit Measurement per DPC

Counter Section

AL0050: Mean Number of Uninstalled Circuits on the A Interface 0

AL0051: Mean Number of Faulty Circuits on the A Interface 7.2.3

AL0052: Mean Number of Circuits in Maintenance State on the A Interface 7.2.4

AL0053: Mean Number of Blocked Circuits on the A Interface 7.2.5

AL0054: Mean Number of Idle Circuits on the A Interface 7.2.6

AL0055: Mean Number of Busy Circuits on the A Interface 7.2.7

AL0089: Mean Number of Circuits with Uninstalled Peer Circuits on the A

Interface

7.2.8






7.2.2 Mean Number of Uninstalled Circuits on the A Interface

Counter

AL0050: Mean Number of Uninstalled Circuits on the A Interface.

Meaning

This counter measures the mean number of uninstalled circuits on the A interface.

Trigger Point

The BSC measures the number of uninstalled circuits on the A interface every 10 s.

This counter is calculated by the later-mentioned formula.

Formula

Mean Number of Uninstalled Circuits on the A Interface = [Sampling Number of Uninstalled

Circuits on the A Interface]/({GP}*{6})

GP: Granularity Period. (Unit: minute)

7.2.3 Mean Number of Faulty Circuits on the A Interface

Counter

AL0051: Mean Number of Faulty Circuits on the A Interface.

Meaning

This counter measures the mean number of faulty circuits on the A interface.

Trigger Point

The BSC measures the number of faulty circuits on the A interface every 10 s.


Formula

Mean Number of Faulty Circuits on the A Interface = [Sampling Number of Faulty Circuits

on the A Interface]/({GP}*{6})








7.2.4 Mean Number of Circuits in Maintenance State on the AInterface

CounterAL0052: Mean Number of Circuits in Maintenance State on the A Interface.

Meaning

This counter measures the mean number of circuits in maintenance state on the A interface.

Trigger Point

The BSC measures the number of circuits in the maintenance state on the A interface every 10

s.


Formula

Mean Number of Circuits in Maintenance State on the A Interface = [Sampling Number of

Circuits in Maintenance State on the A Interface]/({GP}*{6})


7.2.5 Mean Number of Blocked Circuits on the A Interface

Counter

AL0053: Mean Number of Blocked Circuits on the A Interface.

Meaning

This counter measures the mean number of Blocked Circuits on the A Interface.

Trigger Point

The BSC measures the number of blocked circuits on the A interface every 10 s.


Formula

Mean Number of Blocked Circuits on the A Interface = [Sampling Number of BlockedCircuits on the A Interface]/({GP}*{6})







7.2.6 Mean Number of Idle Circuits on the A Interface

Counter

AL0054: Mean Number of Idle Circuits on the A Interface.

Meaning

This counter measures the mean number of idle circuits on the A interface.

Trigger Point

The BSC measures the number of idle circuits on the A interface every 10 s.


Formula

Mean Number of Idle Circuits on the A Interface = [Sampling Number of Idle Circuits on the

A Interface]/({GP}*{6})


7.2.7 Mean Number of Busy Circuits on the A Interface

Counter

AL0055: Mean Number of Busy Circuits on the A Interface.

Meaning

This counter measures the mean number of busy circuits on the A interface.

Trigger Point

The BSC measures the number of busy circuits on the A interface every 10 s.


Formula

Mean Number of Busy Circuits on the A Interface = [Sampling Number of Busy Circuits on

the A Interface]/({GP}*{6})








7.2.8 Mean Number of Circuits with Uninstalled Peer Circuits onthe A Interface

CounterAL0056: Mean Number of Circuits with Uninstalled Peer Circuits on the A Interface.

Meaning

This counter measures the mean number of circuits with uninstalled peer circuits on the A

interface.

Trigger Point

The BSC measures the number of circuits whose peer circuits are uninstalled on the A

interface every 10 s.


Formula

Mean Number of Circuits with Uninstalled Peer Circuits on the A Interface = [Sampling

Number of A Circuits with Uninstalled Peer Circuits on the A Interface]/({GP}*{6})


7.3 TC Measurement per DPC

7.3.1 Overview

TC Measurement per DPC is used to measure the faulty, idle, and busy TC Resources.

Table 7-3 lists the counters of TC Measurement per DPC.

Table 7-3 Counters of TC Measurement per DPC

Counter Section

AR0751: Mean Number of Faulty TC Resources 7.3.2

AR0754: Mean Number of Idle TC Resources 7.3.3

AR0755: Mean Number of Busy TC Resources 7.3.4






7.3.2 Mean Number of Faulty TC Resources

Counter

AR0751: Mean Number of Faulty Transcoders (TC Resources).

Meaning

This counter measures the mean number of faulty TC Resources.

Trigger Point

The BSC measures the number of faulty TC Resources every 10 s.


Formula

Mean Number of Faulty TC Resources = [Sampling Number of Faulty TC

Resources]/({GP}*{6})


7.3.3 Mean Number of Idle TC Resources

Counter

AR0754: Mean Number of Idle TC Resources.

Meaning

This counter measures the mean number of idle TC Resources.

Trigger Point

The BSC measures the number of idle TC Resources every 10 s.


Formula

Mean Number of Idle TC Resources = [Sampling Number of Idle TC Resources]/({GP}*{6})








7.3.4 Mean Number of Busy TC Resources

Counter

AR0755: Mean Number of Busy TC Resources.

Meaning

This counter measures the mean number of busy TC Resources.

Trigger Point

The BSC measures the number of busy TC Resources every 10 s.


Formula

Mean Number of Busy TC Resources = [Sampling Number of Busy TC

Resources]/({GP}*{6})


7.4 Pb Interface Circuit Measurement per PCU

7.4.1 Overview

Pb Interface Circuit Measurement per PCU is used to measure the faulty, and busy circuits,and the circuits in the maintenance state.

Table 7-4 lists counters of Pb Interface Circuit Measurement per PCU.

Table 7-4 Counters of Pb Interface Circuit Measurement per PCU

Counter Section

AL8351: Mean Number of Faulty Circuits on the Pb Interface 7.4.2

AL8353: Mean Number of Blocked Circuits on the Pb Interface 7.4.3

AL8354: Mean Number of Idle Circuits on the Pb Interface 7.4.4

AL8355: Mean Number of Busy Circuits on the Pb Interface 7.4.5

AL8352: Mean Number of Circuits in Maintenance State on the Pb Interface 7.4.6






7.4.2 Mean Number of Faulty Circuits on the Pb Interface

Counter

AL8351: Mean Number of Faulty Circuits on the Pb Interface.

Meaning

This counter measures the mean number of faulty circuits on the Pb interface.

Trigger Point

The BSC measures the number of faulty circuits on the Pb interface every 10 s.


Formula

Mean Number of Faulty Circuits on the Pb Interface = [Sampling Number of Faulty Circuits

on the Pb Interface]/({GP}*{6})


7.4.3 Mean Number of Blocked Circuits on the Pb Interface

Counter

AL8353: Mean Number of Blocked Circuits on the Pb Interface.

Meaning

This counter measures the mean number of blocked circuits on the Pb interface.

Trigger Point

The BSC measures the number of blocked circuits on the Pb interface every 10 s.


Formula

Mean Number of Blocked Circuits on the Pb Interface = [Sampling Number of Blocked

Circuits on the Pb Interface]/({GP}*{6})








7.4.4 Mean Number of Idle Circuits on the Pb Interface

Counter

AL8354: Mean Number of Idle Circuits on the Pb Interface.

Meaning

This counter measures the mean number of idle circuits on the Pb interface.

Trigger Point

The BSC measures the number of idle circuits on the Pb interface every 10 s.


Formula

Mean Number of Idle Circuits on the Pb Interface = [Sampling Number of Idle Circuits on the

Pb Interface]/({GP}*{6})


7.4.5 Mean Number of Busy Circuits on the Pb Interface

Counter

AL8355: Mean Number of Busy Circuits on the Pb Interface.

Meaning

This counter measures the mean number of busy circuits on the Pb interface.

Trigger Point

The BSC measures the number of busy circuits on the Pb interface every 10 s.


Formula

Mean Number of Busy Circuits on the Pb Interface = [Sampling Number of Busy Circuits on

the Pb Interface]/({GP}*{6})







7.4.6 Mean Number of Circuits in Maintenance State on the PbInterface

CounterAL8352: Mean Number of Circuits in Maintenance State on the Pb Interface.

Meaning

This counter measures the mean number of circuits in the maintenance state on the Pb

interface.

Trigger Point

The BSC measures the number of circuits in the maintenance state on the Pb interface every

10 s.


Formula

Mean Number of Circuits in Maintenance State on the Pb Interface = [Sampling Number of

Circuits in Maintenance State on the Pb Interface]/({GP}*{6})


7.5 Ater Interface Circuit Measurement per BM Subrack

7.5.1 Overview

Ater Interface Circuit Measurement per BM Subrack is used to measure the faulty, idle, and

busy circuits on the Ater interface.

Table 7-5 lists the counters of Ater Interface Circuit Measurement per BM Subrack.

Table 7-5 Counters of Ater Interface Circuit Measurement per BM Subrack

Counter Section

AL1251: Mean Number of Faulty Circuits on the Ater Interface 7.5.2

AL1254: Mean Number of Idle Circuits on the Ater Interface 7.5.3

AL1255: Mean Number of Busy Circuits on the Ater Interface 7.5.4







7.5.2 Mean Number of Faulty Circuits on the Ater Interface

Counter

AL1251: Mean Number of Faulty Circuits on the Ater Interface.

Meaning

This counter measures the mean number of faulty circuits on the Ater interface.

Trigger Point

The BSC measures the number of faulty circuits on the Ater interface every 10 s.


Formula

Mean Number of Faulty Circuits on the Ater Interface = [Sampling Number of Faulty Circuits

on the Ater Interface]/({GP}*{6})


7.5.3 Mean Number of Idle Circuits on the Ater Interface

Counter

AL1254: Mean Number of Idle Circuits on the Ater Interface.

Meaning

This counter measures the mean number of idle circuits on the Ater interface.

Trigger Point

The BSC measures the number of idle circuits on the Ater interface every 10 s.


Formula

Mean Number of Idle Circuits on the Ater Interface = [Sampling Number of Idle Circuits on

the Ater Interface]/({GP}*{6})







7.5.4 Mean Number of Busy Circuits on the Ater Interface

Counter

AL1255: Mean Number of Busy Circuits on the Ater Interface.

Meaning

This counter measures the mean number of busy circuits on the Ater interface.

Trigger Point

The BSC measures the number of busy circuits on the Ater interface every 10 s.


Formula

Mean Number of Busy Circuits on the Ater Interface = [Sampling Number of Busy Circuits

on the Ater Interface]/({GP}*{6})





Performance Counter Reference 8 MSC Measurement


8 MSC Measurement

About This Chapter


Section Describes

8.1 Overview of MSC

Measurement

The functions and measurement unit of MSC

Measurement.

8.2 MSC Measurement per

DPC

The functions and counters of MSC Measurement per

DPC.



8 MSC Measurement




8.1 Overview of MSC Measurement

MSC Measurement is used to measure the number of Number of MSC Resets and the numberof messages that the BSC receives from the MSC.

Table 8-1 lists the measurement unit of MSC Measurement.

Table 8-1 Measurement Unit of MSC Measurement


MSC Measurement per DPC 8.2

8.2 MSC Measurement per DPC

8.2.1 Overview

MSC Measurement per DPC is used to measure the number of Number of MSC Resets and

the number of messages that the BSC receives from the MSC.

Table 8-2 lists the counters of MSC Measurement per DPC.

Table 8-2 Counters of MSC Measurement per DPC

Counter Section

L0056A: Number of MSC Resets 8.2.2

L0056B: Number of Messages Received from MSC 8.2.3

8.2.2 Number of MSC Resets

Counter

L0056A: Number of MSC Resets.

Meaning

This counter measures the number of Number of MSC Resets.

Trigger Point

This counter increases by 1 when the BSC receives a reset message from the MSC.




Performance Counter Reference 8 MSC Measurement


Formula

None.

8.2.3 Number of Messages Received from MSCCounter

L0056B: Number of Messages Received from MSC.

Meaning

This counter measures the number of messages that the BSC receives from the MSC.

Trigger Point

This counter increases by 1 when the BSC receives messages from the MSC.

Formula

None.




Performance Counter Reference 9 CBC Measurement


9 CBC Measurement

About This Chapter


Section Describes

9.1 Overview of CBC Measurement The CBC measurement and its measurement units.

9.2 CBC Measurement per BSC The CBC measurement per BSC and its counters.



9 CBC Measurement




9.1 Overview of CBC Measurement

Cell Broadcast Center (CBC) measurement refers to the measurement of the reception of cell broadcast data and the response of the BSC to the data.

Table 9-1 lists the measurement unit of CBC measurement.

Table 9-1 Measurement unit of CBC measurement


CBC Measurement per BSC 9.2

9.2 CBC Measurement per BSC

9.2.1 Overview

CBC Measurement is used to measure the reception of cell broadcast data and the response of

the BSC to the data.

Table 9-2 lists the counters of CBC Measurement.

Table 9-2 Counters of CBC Measurement

Counter Section

L0457: WRITE-REPLACE Requests Received by BSC 9.2.2

L0458: KILL Requests Received by BSC 9.2.3

L0459: STATUS-CBCH-QUERY Requests Received by BSC 9.2.4

L0460: STATUS-MESSAGE-QUERY Requests Received by BSC 9.2.5

L0461: SET-DRX Requests Received by BSC 9.2.6

L0462: RESET Requests Received by BSC 9.2.7

L0463: REPORT Responses to WRITE-REPLACE Requests 9.2.8

L0464: REJECT Responses to WRITE-REPLACE Requests 9.2.9

L0465: REPORT Responses to KILL Requests 9.2.10

L0466: REJECT Responses to KILL Requests 9.2.11

L0467: REPORT Responses to STATUS-CBCH-QUERY Requests 9.2.12

L0468: REJECT Responses to STATUS-CBCH-QUERY Requests 9.2.13

L0469: REPORT Responses to STATUS-MESSAGE-QUERY Requests 9.2.14

L0470: REJECT Responses to STATUS-MESSAGE-QUERY Requests 9.2.15






Counter Section

L0471: REPORT Responses to SET-DRX Requests 9.2.16

L0472: REJECT Responses to SET-DRX Requests 9.2.17

L0473: RESTART-INDICATION Requests Sent from BSC 9.2.18

L0474: REJECT Responses to RESTART-INDICATION Requests 9.2.19

L0475: FAILURE-INDICATION Requests Sent from BSC 9.2.20

L0476: CBCH Loading Indications Received by BSC (Overflow) 9.2.21

L0477: CBCH Loading Indications Received by BSC (Underflow) 9.2.22

L0478: WRITE-REPLACE Requests (WRITE Requests) Received by BSC 9.2.23

L0479: REPORT Responses to WRITE-REPLACE Requests (WRITE

Requests)

9.2.24

L0480: REJECT Responses to WRITE-REPLACE Requests (WRITE Requests) 9.2.25

L0481: WRITE-REPLACE Requests (REPLACE Requests) Received by BSC 9.2.26

L0482: REPORT Responses to WRITE-REPLACE Requests (REPLACE

Requests)

9.2.27

L0483: REJECT Responses to WRITE-REPLACE Requests (REPLACERequests)

9.2.28

AL0484: Mean Capacity of BSC Message Library 9.2.29

L0486: Disruptions of the BSC-CBC Connection 9.2.30

9.2.2 WRITE-REPLACE Requests Received by BSC

Counter

L0457: WRITE-REPLACE Requests Received by BSC

Meaning

This counter measures the number of times the BSC receives a WRITE-REPLACE request on

the BSC-CBC interface.

Trigger Point

This counter increases by one when the BSC receives a WRITE-REPLACE request from the

CBC.

Formula

None.



9 CBC Measurement




9.2.3 KILL Requests Received by BSC

Counter

L0458: KILL Requests Received by BSC

Meaning

This counter is used to measure the number of times the BSC receives a KILL request on the

BSC-CBC interface.

Trigger Point

This counter increases by one when the BSC receives a KILL request from the CBC.

Formula None.

9.2.4 STATUS-CBCH-QUERY Requests Received by BSC

Counter

L0459: STATUS-CBCH-QUERY Requests Received by BSC

Meaning

This counter is used to measure the number of times the BSC receives a STATUS-CBCH-QUERY request on the BSC-CBC interface.

Trigger Point

This counter increases by one when the BSC receives a STATUS-CBCH-QUERY request

from the CBC.

Formula

None.

9.2.5 STATUS-MESSAGE-QUERY Requests Received by BSC

Counter

L0460: STATUS-MESSAGE-QUERY Requests Received by BSC

Meaning

This counter is used to measure the number of times the BSC receives a STATUS-

MESSAGE-QUERY request on the BSC-CBC interface.






Trigger Point

This counter increases by one when the BSC receives a STATUS-MESSAGE-QUERY request

from the CBC.

Formula

None.

9.2.6 SET-DRX Requests Received by BSC

Counter

L0461: SET-DRX Requests Received by BSC

Meaning

This counter is used to measure the number of times the BSC receives a SET-DRX request on

the BSC-CBC interface.

Trigger Point

This counter increases by one when the BSC receives a SET-DRX request from the CBC.

Formula

None.

9.2.7 RESET Requests Received by BSC

Counter

L0462: RESET Requests Received by BSC

Meaning

This counter is used to measure the number of times the BSC receives a RESET request onthe BSC-CBC interface.

Trigger PointThis counter increases by one when the BSC receives a RESET request from the CBC.

Formula

None.

9.2.8 REPORT Responses to WRITE-REPLACE Requests

Counter

L0463: REPORT Responses to WRITE-REPLACE Requests



9 CBC Measurement




Meaning

This counter is used to measure the number of REPORT responses to WRITE-REPLACE

requests from the BSC to the CBC.

After receiving a WRITE-REPLACE request on the BSC-CBC interface, the BSC sends a REPORTresponse message or a REJECT response message to the CBC.

Trigger Point

This counter increases by one when the BSC sends the CBC a REPORT response to theWRITE-REPLACE request.

Formula

None.

9.2.9 REJECT Responses to WRITE-REPLACE Requests

Counter

L0464: REJECT Responses to WRITE-REPLACE Requests

Meaning

This counter is used to measure the number of REJECT responses to WRITE-REPLACE

requests from the BSC to the CBC.

After receiving a WRITE-REPLACE request on the BSC-CBC interface, the BSC sends a REPORTresponse message or a REJECT response message to the CBC.

Trigger Point

This counter increases by one when the BSC sends a REJECT response message to the CBC.

Formula

None.

9.2.10 REPORT Responses to KILL Requests

Counter

L0465: REPORT Responses to KILL Requests

Meaning

This counter is used to measure the number of REPORT responses to KILL requests from the

BSC to the CBC.






After receiving a KILL request on the BSC-CBC interface, the BSC sends a REPORT response messageor a REJECT response message to the CBC.

Trigger PointThis counter increases by one when the BSC sends the CBC a REPORT response to the KILL

request.

Formula

None.

9.2.11 REJECT Responses to KILL Requests

CounterL0466: REJECT Responses to KILL Requests

Meaning

This counter is used to measure the number of REJECT responses to KILL requests from BSC

to the CBC.

After receiving a KILL request on the BSC-CBC interface, the BSC sends a REPORT response messageor a REJECT response message to the CBC.

Trigger Point

This counter increases by one when the BSC sends the CBC a REJECT response to the KILL

request.

Formula

None.

9.2.12 REPORT Responses to STATUS-CBCH-QUERY Requests

CounterL0467: REPORT Responses to STATUS-CBCH-QUERY Requests

Meaning

This counter is used to measure the number of REPORT responses to STATUS-CBCH-

QUERY requests from the BSC to the CBC.

After receiving a STATUS-CBCH-QUERY request on the BSC-CBC interface, the BSC sends a

REPORT response message or a REJECT response message to the CBC.



9 CBC Measurement




Trigger Point

This counter increases by one when the BSC sends the CBC a REPORT response to the

STATUS-CBCH-QUERY request.

Formula

None.

9.2.13 REJECT Responses to STATUS-CBCH-QUERY Requests

Counter

L0468: REJECT Responses to STATUS-CBCH-QUERY Requests

Meaning

This counter is used to measure the number of REJECT responses to STATUS-CBCH-

QUERY requests from the BSC to the CBC.

After receiving a STATUS-CBCH-QUERY request on the BSC-CBC interface, the BSC sends aREPORT response message or a REJECT response message to the CBC.

Trigger Point

This counter increases by one when the BSC sends the CBC a REJECT response to the

STATUS-CBCH-QUERY request.

Formula

None.

9.2.14 REPORT Responses to STATUS-MESSAGE-QUERYRequests

Counter

L0469: REPORT Responses to STATUS-MESSAGE-QUERY Requests

Meaning

This counter is used to measure the number of REPORT responses to STATUS-MESSAGE-QUERY requests from the BSC to the CBC.

After receiving a STATUS-MESSAGE-QUERY query on the BSC-CBC interface, the BSC sends a







Trigger Point

This counter increases by one when the BSC sends the CBC a REPORT response to the

STATUS-MESSAGE-QUERY request.

Formula

None.

9.2.15 REJECT Responses to STATUS-MESSAGE-QUERYRequests

Counter

L0470: REJECT Responses to STATUS-MESSAGE-QUERY Requests

Meaning

This counter is used to measure the number of REJECT responses to STATUS-MESSAGE-QUERY requests from the BSC to the CBC.

After receiving a STATUS-MESSAGE-QUERY query on the BSC-CBC interface, the BSC sends a


Trigger Point

This counter increases by one when the BSC sends a REJECT response to the STATUS-MESSAGE-QUERY request.

Formula

None.

9.2.16 REPORT Responses to SET-DRX Requests

Counter

L0471: REPORT Responses to SET-DRX Requests

Meaning

This counter is used to measure the number of REPORT responses to SET-DRX requests fromthe BSC to the CBC.

After receiving a SET-DRX request on the BSC-CBC interface, the BSC sends a REPORT response

message or a REJECT response message to the CBC.



9 CBC Measurement




Trigger Point

This counter increases by one when the BSC sends the CBC a REPORT response to the SET-

DRX request.

Formula

None.

9.2.17 REJECT Responses to SET-DRX Requests

Counter

L0472: REJECT Responses to SET-DRX Requests

Meaning

This counter is used to measure the number of REJECT responses to SET-DRX requests from

the BSC to the CBC.

After receiving a SET-DRX request on the BSC-CBC interface, the BSC sends a REPORT responsemessage or a REJECT response message to the CBC.

Trigger Point

This counter increases by one when the BSC sends the CBC a REJECT response to SET-DRX

request.

Formula

None.

9.2.18 RESTART-INDICATION Requests Sent from BSC

Counter

L0473: RESTART-INDICATION Requests Sent from BSC

MeaningThis counter is used to measure the number of RESTART-INDICATION requests sent from

BSC to the CBC.

After receiving a RESET message on the BSC-CBC interface, the BSC sends a RESTART-INDICATION requests or a REJECT response message to the CBC.

Trigger Point

This counter increases by one when the BSC sends a RESTART-INDICATION request to the

CBC.






Formula

None.

9.2.19 REJECT Responses to RESTART-INDICATION RequestsCounter

L0474: REJECT Responses to RESTART-INDICATION Requests

Meaning

This counter is used to measure the number of REJECT responses to RESTART-

INDICATION requests from the BSC to the CBC.

After receiving a RESET message on the BSC-CBC interface, the BSC sends a RESTART-INDICATION requests or a REJECT response message to the CBC.

Trigger Point

This counter increases by one when the BSC sends the CBC a REJECT response message to

the RESTART-INDICATION request.

Formula

None.

9.2.20 FAILURE-INDICATION Requests Sent from BSC

Counter

L0475: FAILURE-INDICATION Requests Sent from BSC

Meaning

This counter is used to measure the number of FAILURE-INDICATION requests sent from

the BSC to the CBC.

Trigger PointThis counter increases by one when the BSC sends a FAILURE-INDICATION request to the

CBC.

Formula

None.



9 CBC Measurement




9.2.21 CBCH Loading Indications Received by BSC (Overflow)

Counter

L0476: CBCH Loading Indications Received by BSC (Overflow)

Meaning

This counter is used to measure the number of CBCH Loading Indication (overflow)

messages received by the BSC from the BTS.

Trigger Point

This counter increases by one when the BSC receives a CBCH Loading Indication (overflow)

message from the BTS.

Formula

None.

9.2.22 CBCH Loading Indications Received by BSC (Underflow)

Counter

L0477: CBCH Loading Indications Received by BSC (Underflow)

Meaning

This counter is used to measure the number of CBCH Loading Indication (underflow)

messages received by the BSC from the BTS.

Trigger Point

This counter increases by one when the BSC receives a CBCH Loading Indication (underflow)


Formula

None.

9.2.23 WRITE-REPLACE Requests (WRITE Requests) Received byBSC

Counter

L0478: WRITE-REPLACE Requests (WRITE Requests) Received by BSC

Meaning

This counter is used to measure the number of WRITE-REPLACE requests (WRITE requests)

received by the BSC.






Trigger Point

This counter increases by one when the BSC receives a WRITE-REPLACE request (WRITE

request).

Formula

None.

9.2.24 REPORT Responses to WRITE-REPLACE Requests(WRITE Requests)

Counter

L0479: REPORT Responses to WRITE-REPLACE Requests (WRITE Requests)

Meaning

This counter is used to measure the number of REPORT responses to WRITE-REPLACErequests (WRITE requests) from the BSC.

Trigger Point

This counter increases by one when the BSC sends a REPORT response message to theWRITE-REPLACE request (WRITE request).

Formula

None.

9.2.25 REJECT Responses to WRITE-REPLACE Requests (WRITERequests)

Counter

L0480: REJECT Responses to WRITE-REPLACE Requests (WRITE Requests)

Meaning

This counter is used to measure the number of REJECT responses to WRITE-REPLACErequests (WRITE requests) from the BSC.

Trigger Point

This counter increases by one when the BSC sends a REJECT response to the WRITE-REPLACE request (WRITE request).

Formula

None.



9 CBC Measurement




9.2.26 WRITE-REPLACE Requests (REPLACE Requests) Receivedby BSC

CounterL0481: WRITE-REPLACE Requests (REPLACE Requests) Received by BSC

Meaning

This counter is used to measure the number of WRITE-REPLACE requests (REPLACE

requests) received by the BSC.

Trigger Point

This counter increases by one when the BSC receives a WRITE-REPLACE request

(REPLACE request).

Formula

None.

9.2.27 REPORT Responses to WRITE-REPLACE Requests(REPLACE Requests)

Counter

L0482: REPORT Responses to WRITE-REPLACE Requests (REPLACE Requests)

Meaning

This counter is used to measure the number of REPORT responses to WRITE-REPLACE

requests (REPLACE requests) from the BSC.

Trigger Point

This counter increases by one when the BSC sends a REPORT response message to the

WRITE-REPLACE request (REPLACE request).

Formula

None.

9.2.28 REJECT Responses to WRITE-REPLACE Requests(REPLACE Requests)

Counter

L0483: REJECT Responses to WRITE-REPLACE Requests (REPLACE Requests)






Meaning

This counter is used to measure the number of REJECT responses to WRITE-REPLACE

requests (REPLACE requests) from the BSC.

Trigger Point

This counter increases by one when the BSC sends a REJECT response message to the

WRITE-REPLACE request (REPLACE request).

Formula

None.

9.2.29 Mean Capacity of BSC Message Library

Counter

AL0484: Mean Capacity of BSC Message Library

Meaning

This counter is used to measure the mean number of messages in the BSC message library.

Trigger Point

None.

Formula

Mean number of messages in the BSC message library =

Accumulated number of messages in the BSC message library/Number of samplings ofmessages in the BSC message library

9.2.30 Disruptions of the BSC-CBC Connection

Counter

L0486: Disruptions of the BSC-CBC Connection

Meaning

This counter is used to measure the number of times the connection between the BSC and the

CBC disrupts.

Trigger Point

This counter increases by one when the connection between the BSC and the CBC disrupts.

Formula

None.




Performance Counter Reference 10 PCU Measurement


10 PCU Measurement

About This Chapter


Section Describes

10.1 Overview of PCUMeasurement

Introduces the functions and measurement units ofPCU Measurement.

10.2 PCU Measurement per BSC Describes the functions and counters of PCUMeasurement per BSC.

10.3 PCU Measurement per PCU Describes the functions and counters of PCUMeasurement per PCU.



10 PCU Measurement




10.1 Overview of PCU Measurement

PCU Measurement is used to measure the number of messages that the BSC receives from thePCU.

Table 10-1 lists the measurement units of PCU Measurement.

Table 10-1 Measurement units of PCU Measurement


PCU Measurement per BSC 10.2

PCU Measurement per PCU 10.3

10.2 PCU Measurement per BSC

10.2.1 Overview

PCU Measurement per BSC is used to measure the number of messages that the BSC receivesfrom the PCU.

Table 10-2 lists the counters of PCU Measurement per BSC.

Table 10-2 Counters of PCU Measurement per BSC

Counter Section

L0387: Total Messages Received from PCU 10.2.2

10.2.2 Total Messages Received from PCU

Counter

L0387: L0387: Total Messages Received from PCU.

Meaning

This counter measures the number of messages that the BSC receives from all the PCUs.

Trigger Point

This counter increases by 1 when the BSC receives a message from the PCU.




Performance Counter Reference 10 PCU Measurement


Formula

None.

10.3 PCU Measurement per PCU

10.3.1 Overview

PCU Measurement per PCU is used to measure the number of messages that the BSC receives

from one PCU.

Table 10-3 lists the counter of PCU Measurement per PCU.

Table 10-3 Counter of PCU Measurement per PCU

Counter Section

L8387: Messages Received from a PCU 10.3.2

10.3.2 Messages Received from a PCU

Counter

L8387: Messages Received from one PCU.

Meaning

This counter measures the number of messages that the BSC receives from one PCU.

Trigger Point

This counter increases by 1 when the BSC receives a message from a PCU.

Formula

None.




Performance Counter Reference 11 Paging Measurement


11 Paging Measurement

About This Chapter


Section Describes

11.1 Overview of PagingMeasurement

Introduces the measurement units of PagingMeasurement.

11.2 A Interface PagingMeasurement

Describes the functions and counters of Measurement ofthe Paging on the A Interface per BSC.

11.3 Abis Interface PagingMeasurement Describes the functions and counters of Measurement ofthe Paging on the Abis Interface per Cell.

11.4 Measurement ofDiscarded Paging Messagesdue to Overload per LAPD

Describes the functions and counters of Measurement ofDiscarded Paging Messages due to Overload per LAPD.







11.1 Overview of Paging Measurement

Paging Measurement refers to the measurement of the number of paging messages on the Ainterface and Abis interface.

Table 11-1 lists the measurement units of Paging Measurement.

Table 11-1 Measurement units of Paging Measurement


A Interface Paging Measurement 11.2

Abis Interface Paging Measurement 11.3

Measurement of Discarded Paging Messages due to Overload per LAPD 11.4

11.2 A Interface Paging Measurement

11.2.1 Overview of A Interface Paging Measurement

Measurement of the Paging on the A Interface per BSC refers to the measurement of thenumber of paging messages from the core network.

The paging messages from the core network have two types, the circuit service (CS) pagings,and the packet service (PS) pagings. The CS pagings are sent from the MSC to the BSC onthe A interface, and the PS pagings are sent from the SGSN to the BSC through the SGSN on

the Gb interface (The pagings can be sent directly to the BSC when the BSC has a built-inPCU). The CS pagings can be sent to the BSC through the SGSN and the PCU when the Gs

interface (interface between the MSC and the SGSN) is available.

Table 11-2 lists the counters of Measurement of the Paging on the A Interface per BSC

Table 11-2 Counters of Measurement of the Paging on the A Interface per BSC

Number Counter

1 A0300: MSC-Initiated Paging Requests for CS Service

2 A0301: SGSN-Initiated Paging Requests for CS Service

3 A031: SGSN-Initiated Paging Requests for PS Service

4 A032: Delivered to BTS for CS Service






11.2.2 MSC-Initiated Paging Requests for CS Service

Counter

A0300: MSC-Initiated Paging Requests for CS Service

Meaning

This counter measures the number of CS paging requests sent from the MSC to the BSC. The

CS paging requests are sent directly from the MSC to the BSC, and the BSC measures thiscounter after receiving such a paging request.

Trigger Point

This counter is measured when the BSC receives an MSC-initiated paging request, as shown

in Figure 11-1.

Figure 11-1 MSC-initiated paging procedure for CS service

BTS BSCMS MSC

A

PAGING REQ

CHAN REQ

PAGING CMD

CHAN RED

PAGING

Formula

None.

11.2.3 SGSN-Initiated Paging Requests for CS Service

Counter

A0301: SGSN-Initiated Paging Requests for CS Service.

Meaning

This counter measures the number of CS paging requests sent from the SGSN to the BSC.

The CS paging requests are sent from the SGSN to the BSC through the PCU. The BSCmeasures this counter after receiving such a paging request.







Trigger Point

This counter is measured when the BSC receives the PAGING (CS) message from the PCU or

the SGSN, as shown in Figure 11-2.

Figure 11-2 SGSN-initiated paging procedure for CS service

BTS BSCMS PCU/SGSN

A

PAGING REQ

CHAN REQ

PAGING CMD

CHAN RQD

PAGING(CS)

CHAN REQ

Formula

None.

This counter takes effect only when the Gs interface (interface between the MSC and the SGSN) isavailable.

11.2.4 SGSN-Initiated Paging Requests for PS Service

Counter

A031: SGSN-Initiated Paging Requests for PS Service

Meaning

This counter measures the number of PS paging requests sent from the SGSN to the BSC. The

PS paging requests are sent from the SGSN to the BSC through the PCU. The BSC measures

this counter after receiving such a paging request.






Trigger Point

This counter is measured when the BSC receives the PAGING (PS) message from the PCU or

the SGSN, as shown in Figure 11-3.

Figure 11-3 SGSN-initiated paging procedure for PS service

BTS BSCMS SGSN

A

PAGING REQ

CHAN REQ

PAGING CMD

CHAN RQD

PAGING（PS）

CHAN REQ

PCU

PAGING REQ

PAGING REQ

Formula

None.

11.2.5 Delivered to BTS for CS Service

Counter

A032: Delivered to BTS for CS Service

Meaning

This counter measures the number of paging requests delivered from the BSC to the BTS. You

can judge whether the paging messages are lost with the reference of A0300: MSC-InitiatedPaging Requests for CS Service.

Trigger Point

This counter is measured when the BSC delivers a paging request to the BTS, as shown inFigure 11-4.







Figure 11-4 BSC-delivered CS paging procedure

MS BTS BSC MSC

APAGING REQ

CHAN REQ

PAGING CMD

CHAN RQD

PAGING

Formula None.

11.3 Abis Interface Paging Measurement

11.3.1 Overview of Abis Interface Paging Measurement

Measurement of the Paging on the Abis Interface per Cell refers to the measurement of thenumber of PS and CS pagings that the BSC sends to the BTS on the Abis interface.

Table 11-3 lists the counters of Measurement of the Paging on the Abis Interface per Cell.

Table 11-3 Counters of Measurement of the Paging on the Abis Interface per Cell

Number Counter

1 A330: Delivered Paging Messages for CS Service

2 A331: Delivered Paging Messages for PS Service

11.3.2 Delivered Paging Messages for CS Service

Counter

A330: Delivered Paging Messages for CS Service

Meaning

The BSC delivers the PAGING CMD message based on the cell identity after it receives thePAGING message from the MSC or the PCU, and this counter is measured.






Trigger Point

This counter is measured when the BSC delivers a PAGING CMD to the BTS, as shown in

Figure 11-5.

Figure 11-5 CS paging procedure

BTS BSCMS PCU

APAGING REQ

PAGING CMD

PAGING REQ

SGSN MSC

PAGING

PAGING

PAGING REQ

Formula

None.

11.3.3 Delivered Paging Messages for PS Service

Counter

A331: Delivered Paging Messages for PS Service.

Meaning

The SGSN delivers the PAGING REQ message to the PCU. The PCU processes the message

and then sends the PACKET PAGING message to the BSC. The BSC delivers the PSPAGING CMD to related cells based on the cell identity in the PACKET PAGING message

and this counter is measured.







Trigger Point

This counter is measured when the BSC delivers a PS PAGING CMD message to the BTS, as

shown in Figure 11-6.

Figure 11-6 PS paging procedure

PAGING REQ

BTS BSCMS PCU

APAGING REQ

PS PAGING CMD

PAGING

SGSN

Formula

None.

11.4 Measurement of Discarded Paging Messages due toOverload per LAPD

11.4.1 Overview of Measurement of Discarded Paging Messagesdue to Overload per LAPD

Measurement of Discarded Paging Messages due to Overload per LAPD refers to the

measurement of the discarded number of CS and PS pagings on the LAPD link due tooverload of the system.

Table 11-4 lists the counters of Measurement of Discarded Paging Messages due to Overload

per LAPD.

Table 11-4 Counters of Measurement of Discarded Paging Messages due to Overload per LAPD

Number Counter

1 A530: SM Pagings Discarded on LAPD Link

2 A531: CS Pagings Discarded on LAPD Link

3 A532: PS Pagings Discarded on LAPD Link






11.4.2 SM Pagings Discarded on LAPD Link

Counter

A530: SM Pagings Discarded on LAPD Link

Meaning

This counter measures the number of discarded short message (SM) pagings on the LAPD.

Trigger Point

This counter is measured when an SM paging is discarded on the LAPD link due to overload

of the GEIUB/GOIUB overload or the LAPD link.

Formula None.

11.4.3 CS Pagings Discarded on LAPD Link

Counter

A531: CS Pagings Discarded on LAPD Link

Meaning

This counter measures the number of discarded CS pagings on the LAPD link.

Trigger Point

This counter is measured when a CS paging is discarded on the LAPD link due to overload of

the GEIUB/GOIUB or the LAPD link.

Formula

None.

11.4.4 PS Pagings Discarded on LAPD Link

Counter

A532: PS Pagings Discarded on LAPD Link

Meaning

This counter measures the number of discarded PS pagings on the LAPD link.







Trigger Point

This counter is measured when a PS paging is discarded on the LAPD link due to overload of

the GEIUB/GOIUB or the LAPD link.

Formula

None.




Performance Counter Reference 12 Call Measurement


12 Call Measurement

About This Chapter


Section Describes

12.1 Overview of Call Measurement Introduces the call measurement and itsmeasurement units.

12.2 Call Duration Measurement perBSC

Describes Call Duration Measurement per BSC andits counters.

12.3 Flow Control Measurement perCell Describes Flow Control Measurement per Cell andits counters.

12.4 Short Message Measurement per Cell

Describes Short Message Measurement per Celland its counters.

12.5 Call Drop Measurement perCell

Describes Call Drop Measurement per Cell and itscounters.

12.6 Channel Activation

Measurement per Cell

Describes Channel Activation Measurement per

Cell and its counters.

12.7 Channel Seizure Measurement

per TRX

Describes Channel Seizure Measurement per TRX

and its counters.

12.8 Immediate AssignmentMeasurement per Cell

Describes Immediate Assignment Measurement perCell and its counters.

12.9 Assignment Measurement per

Cell

Describes Assignment Measurement per Cell and

its counters.

12.10 Intra-Cell Handover


Describes Intra-Cell Handover Measurement per

Cell and its counters.

12.11 Incoming Internal Inter-Cell

Handover Measurement per Cell

Describes Incoming Internal Inter-Cell Handover

Measurement per Cell and its counters.



12 Call Measurement




Section Describes

12.12 Outgoing Internal Inter-Cell

Handover Measurement per Cell

Describes Outgoing Internal Inter-Cell Handover


12.13 Incoming External Inter-CellHandover Measurement per Cell

Describes Incoming External Inter-Cell HandoverMeasurement per Cell and its counters.

12.14 Outgoing External Inter-CellHandover Measurement per Cell

Describes Outgoing External Inter-Cell HandoverMeasurement per Cell and its counters.

12.15 Incoming Inter-RAT Inter-

Cell Handover Measurement perCell

Describes Incoming Inter-RAT Inter-Cell Handover


12.16 Outgoing Inter-RAT Inter-

Cell Handover Measurement perCell

Describes Outgoing Inter-RAT Inter-Cell HandoverMeasurement per Cell and its counters.

12.17 GSM Cell to GSM CellIncoming Handover Measurement

Describes GSM Cell to GSM Cell IncomingHandover Measurement and its counters.

12.18 GSM Cell to GSM CellOutgoing Handover Measurement

Describes GSM Cell to GSM Cell OutgoingHandover Measurement and its counters.

12.19 Measurement of MRs upon

Handover Initiation per Cell

Describes Measurement of MRs upon Handover

Initiation per Cell and its counters.

12.20 KPI Measurement per Cell Describes KPI Measurement per Cell and its

counters.

12.21 Calls Discarded due toOverload per LAPD Describes Calls Discarded due to Overload perLAPD and its counters.






12.1 Overview of Call Measurement

Call measurement refers to the measurement of the call services in the BSC.Table 12-1 lists the measurement units of call measurement.

Table 12-1 Measurement units of call measurement


Call Duration Measurement per BSC 12.2

Flow Control Measurement per Cell 12.3

Short Message Measurement per Cell 12.4

Call Drop Measurement per Cell 12.5

Channel Activation Measurement per Cell 12.6

Channel Seizure Measurement per TRX 12.7

Immediate Assignment Measurement per Cell 12.8

Assignment Measurement per Cell 12.9

Intra-Cell Handover Measurement per Cell 12.10

Incoming Internal Inter-Cell Handover Measurement per Cell 12.11

Outgoing Internal Inter-Cell Handover Measurement per Cell 12.12

Incoming External Inter-Cell Handover Measurement per Cell 12.13

Outgoing External Inter-Cell Handover Measurement per Cell 12.14

Incoming Inter-RAT Inter-Cell Handover Measurement per Cell 12.15

Outgoing Inter-RAT Inter-Cell Handover Measurement per Cell 12.16

GSM Cell to GSM Cell Incoming Handover Measurement 12.17

GSM Cell to GSM Cell Outgoing Handover Measurement 12.18

Measurement of MRs upon Handover Initiation per Cell 12.19

KPI Measurement per Cell 12.20

Calls Discarded due to Overload per LAPD 12.21



12 Call Measurement




12.2 Call Duration Measurement per BSC

12.2.1 Overview

Call Duration Measurement per BSC is used to measure the access duration and establishmentduration of all the calls in the BSC.

Table 12-2 lists the counters of Call Duration Measurement per BSC.

Table 12-2 Counters of Call Duration Measurement per BSC

Number Counter

1 AA032: Mean Duration of Call Access

2 AA033: Mean Duration of Call Establishment

12.2.2 Mean Duration of Call Access

Counter

AA032: Mean Duration of Call Access

Meaning

This counter measures the mean duration of call access in a Granularity Period (GP).

Trigger Point

None.

Formula

Mean Duration of Call Access = [Total Duration of Call Access]/[Sampled Duration of Call

Access]

GP unit: 100 milliseconds

12.2.3 Mean Duration of Call Establishment

Counter

AA033: Mean Duration of Call Establishment

Meaning

This counter measures the mean duration of call establishment in a GP.






Trigger Point

None.

FormulaMean Duration of Call Establishment = [Total Duration of Call Establishment]/[Sampled

Duration of Call Establishment]

GP unit: 100 milliseconds

12.3 Flow Control Measurement per Cell

12.3.1 OverviewFlow Control Measurement per Cell is used to measure the resource utilization of a cell or a

BTS.

Table 12-3 lists the counters of Flow Control Measurement per Cell.

Table 12-3 Counters of Flow Control Measurement per Cell

Number Counter

1 L3188A: MSG DEL IND Messages Sent on Abis Interface

2 L3188B: MSG CCCH LOAD IND (RACH) Messages Sent on Abis Interface

3 L3188C: MSG CCCH LOAD IND (PCH) Messages Sent on Abis Interface

4 L3188D: PACKET CCCH LOAD IND Messages Sent on Abis Interface

5 L3188E: MSG ABIS OVERLOAD (CCCH OVERLOAD) Messages Sent onAbis Interface

6 L3188F: MSG ABIS OVERLOAD (PROCESSOR OVERLOAD) MessagesSent on Abis Interface

7 L3188G: LOAD IND Messages Sent on the A-Interface

8 L3188H: Increases of Flow Control Levels

9 L3188I: Decreases of Flow Control Levels

10 L3188J: Ignored Trigger Events

11 L3188K: Highest Level Delays

12 L3188L: Paging Messages Discarded from the PCH Queue

13 L3188M: Maximum Seizure Ratio of PCH Paging Queue



12 Call Measurement




12.3.2 MSG DEL IND Messages Sent on Abis Interface

Counter

L3188A: MSG DEL IND Messages Sent on Abis Interface

Meaning

When an IMM ASS CMD message is deleted because of downlink CCCH overload in a cell,

the BTS sends an MSG DEL IND message. This counter measures the number of times theBTS sends the MSG DEL IND messages about a cell in a GP.

Trigger Point

The measurement is triggered when the BSC receives an MSG DEL IND message from the

BTS.

Formula

None.

12.3.3 MSG CCCH LOAD IND (RACH) Messages Sent on AbisInterface

Counter

L3188B: MSG CCCH LOAD IND (RACH) Messages Sent on Abis Interface

Meaning

When the uplink CCCH (RACH) in a cell is overloaded, the BTS sends an MSG CCCH

LOAD IND (RACH) message to the BSC.

Huawei BSS does not support the RACH overload of packet services. The RACH overload caused by

the calls of packet services is also regarded as the RACH overload of circuit services.

Trigger Point

The measurement is triggered when the BSC receives an MSG CCCH LOAD IND (RACH)message from the BTS. The cause carried in this message is uplink CCCH (RACH) overload.

Formula

None.






12.3.4 MSG CCCH LOAD IND (PCH) Messages Sent on AbisInterface

CounterL3188C: MSG CCCH LOAD IND (PCH) Messages Sent on Abis Interface

Meaning

The BTS saves the downlink CCCH (PCH) messages received from the BSC and the PCU

into different receive buffer queues. When the length of the queue exceeds the specifiedthreshold, the downlink CCCH is overloaded. The BTS can report overload to the BSC andidentify whether the overload is caused by excessive downlink packet services or by excessive

downlink circuit services. If the overload is caused by excessive downlink circuit services, the

BTS sends a CCCH LOAD IND message to the BSC and the BSC forwards it to the PCU.

Trigger Point

The measurement is triggered when the BSC receives from the BTS an MSG CCCH LOAD

IND (PCH) message. The cause carried in this message is downlink CCCH (PCH) overload ofcircuit services.

Formula

None.

12.3.5 PACKET CCCH LOAD IND Messages Sent on Abis

Interface

Counter

L3188D: PACKET CCCH LOAD IND Messages Sent on Abis Interface

Meaning

This counter measures the number of times the BSC receives a PACKET CCCH LOAD IND

message from a cell in a GP, that is, the number of times the BTS receives from the BSC and

PCU a downlink CCCH (PCH) message. When the CCCH of packet services is overloaded,

the BTS sends a PACKET CCCH LOAD IND message to the BSC and the BSC forwards it tothe PCU.

Trigger Point

The measurement is triggered when the BSC receives a PACKET CCCH LOAD IND


Formula

None.



12 Call Measurement




12.3.6 MSG ABIS OVERLOAD (CCCH OVERLOAD) MessagesSent on Abis Interface

CounterL3188E: MSG ABIS OVERLOAD (CCCH OVERLOAD) Messages Sent on Abis Interface

Meaning

This counter measures the number of times the BSC receives an MSG ABIS OVERLOAD

(CCCH OVERLOAD) message from a cell in a GP. When the BTS sends an MSG ABISOVERLOAD (CCCH OVERLOAD) message to the BSC, it also sends the BSC a CCCHLOAD INDICATION message.

TRX overload reports (CCCH overload) = CCCH load reports (RACH overload) + CCCH load reports

(PCH overload) (circuit service and packet service).

In actual situations, this equation may not exist due to bit errors.

Trigger Point

The measurement is triggered when the BSC receives an MSG ABIS OVERLOAD (CCCH

OVERLOAD) message from the BTS.

Formula

None.

12.3.7 MSG ABIS OVERLOAD (PROCESSOR OVERLOAD)Messages Sent on Abis Interface

Counter

L3188F: MSG ABIS OVERLOAD (PROCESSOR OVERLOAD) Messages Sent on AbisInterface

Meaning

This counter measures the number of times the BSC receives an MSG ABIS OVERLOAD(PROCESSOR OVERLOAD) message from a cell in a GP. Processor overload means that the

CPU load of the TRX processor in a cell exceeds the threshold. This counter is not directlyrelated to CCCH overload.

Trigger Point

The measurement is triggered when the BSC receives an MSG ABIS OVERLOAD

(PROCESSOR OVERLOAD) message from the BTS.

Formula

None.






12.3.8 LOAD IND Messages Sent on the A-Interface

Counter

L3188G: LOAD IND Messages Sent on the A-Interface

Meaning

If a cell has no TCHs available but the cell has external neighbor cells, the BSC sends the

MSC a LOAD IND message to avoid the handover of the call from the external neighbor cellto this cell. The MSC then forwards this message to the BSS where the external neighbor cellis located. Therefore, the BSS will not select congested cells as candidate cells for handovers.

The BSC checks the number of idle TCHs every five seconds.

Trigger Point

The measurement is triggered when the BSC sends a LOAD IND message to the MSC.

Formula

None.

12.3.9 Increases of Flow Control Levels

Counter

L3188H: Increases of Flow Control Levels

Meaning

Cell flow control is performed through double timers. When a trigger event occurs, the eventis ignored if T1 is running. If T1 is not running, the flow control level increases by one unless

the flow control has already reached the highest level. T1 and T2 (T2 > T1) are triggered. IfT2 expires, the flow control level decreases by one. If the flow control level is not zero after

the decrease, T2 is triggered again.

This counter measures the number of times the trigger event occurs when T1 stops and theflow control has not reached the highest level.



12 Call Measurement




The description of the double timers is as follows:

When the event that can trigger AGCH flow control occurs, the cell flow control timer is triggered if

neither T1 nor T2 is running. The timer length is T1. The status of the timer is changed to T1 running.

If the flow control does not reach the highest level (level 5), the AGCH flow control level increases by one and the number of times the flow control level increases is measured.

If the flow control level has reached the highest level, the Highest Level Delays counter is measured.

If the flow control timer is in T1 running status, the event is ignored and the times the trigger event isignored is measured.

If the flow control timer in T1 running status expires, the timer is triggered again and the timer length is

T2-T1. The status of the flow control timer is changed to T1 stopped and T2 running status.

In T1 stopped and T2 running status, if the event that can trigger AGCH flow control occurs, the cell

flow control timer is triggered again. The timer length is T1. The status of the flow control timer ischanged to T1 running. If the timer expires, the flow control level decreases by one and the number oftimes the flow control level decreases is measured.

If the flow control level is not zero after the decrease, the cell flow control timer is triggered again.

The timer length is T2. The status of the flow control timer remains the same.

If the flow control level becomes zero after the decrease, the status of the flow control timer is

changed to T1 and T2 stopped.

Trigger Point

The BSC detects that all the SDCCHs are busy when sending an IMM ASS REJ message. The

measurement is triggered if T1 stops and the flow control has not reached the highest level.

Formula

None.

12.3.10 Decreases of Flow Control Levels

Counter

L3188I: Decreases of Flow Control Levels

Meaning

Cell flow control is performed through double timers. When a trigger event occurs, the event

is ignored if T1 is running. If T1 is not running, the flow control level increases by one unlessthe flow control has already reached the highest level. T1 and T2 (T2 > T1) are triggered. If

T2 expires, the flow control level decreases by one. If the flow control level is not zero afterthe decrease, T2 is triggered again. The number of the times the flow control level decreasesis the number of the times T2 expires.

This counter measures the number of times the flow control level decreases.

Trigger Point

The measurement is triggered when T2 expires.

Formula

None.






12.3.11 Ignored Trigger Events

Counter

L3188J: Ignored Trigger Events

Meaning


is ignored if T1 is running. If T1 is not running, the flow control level increases by one unlessthe flow control has already reached the highest level. T1 and T2 (T2 > T1) are triggered. IfT2 expires, the flow control level decreases by one. If the flow control level is not zero after

the decrease, T2 is triggered again.

This counter measures the number of times trigger events occur when T1 is running.

Trigger PointThe measurement is triggered when T1 is running.

Formula

None.

12.3.12 Highest Level Delays

Counter

L3188K: Highest Level Delays

Meaning


is ignored if T1 is running. If T1 is not running, the flow control level increases by one unless

the flow control has already reached the highest level. T1 and T2 (T2 > T1) are triggered. If

T2 expires, the flow control level decreases by one. If the flow control level is not zero afterthe decrease, T2 is triggered again.

This counter measures the number of times the trigger event occurs when T2 is running and

the flow control has reached the highest level.

Trigger Point

The BSC detects that all the SDCCHs are busy when sending an IMM ASS REJ message. The

measurement is triggered if the flow control has reached the highest level.

Formula

None.



12 Call Measurement




12.3.13 Paging Messages Discarded from the PCH Queue

Counter

L3188L: Paging Messages Discarded from the PCH Queue

Meaning

When the downlink CCCH (PCH) is overloaded, the BTS rerports the BTS STATIS REPORT

message to the BSC and measures the number of CS and PS paging messages discarded bythe PCH in a GP.

The discard causes include queue overflow, queue overflow caused by preferential insertion,

and queuing timer expiration.

When the PCCCH is provided, this counter measures only the number of discarded CS panging

messages.

Trigger Point

This counter is measured when the BSC receives the BTS STATIS REPORT message from

the BTS.

Formula

None.

12.3.14 Maximum Seizure Ratio of PCH Paging QueueCounter

L3188M: Maximum Seizure Ratio of PCH Paging Queue

Meaning

When the downlink CCCH (PCH) is overloaded, the BTS rerports the BTS STATIS REPORT

message to the BSC.

This counter measures the maximum seizure ratio of the PCH paging queue.

Trigger Point

This counter is measured when the BSC receives the BTS STATIS REPORT message from

the BTS.

Formula

None.






12.4 Short Message Measurement per Cell

12.4.1 Overview

Short Message Measurement per Cell is used to measure the transmission and reception ofshort messages in a cell.

Table 12-4 lists the counters of Short Message Measurement per Cell.

Table 12-4 Counters of Short Message Measurement per Cell

Number Counter

1 A3340A: Uplink Point-to-Point Short Messages on SDCCH

2 A3340B: Downlink Point-to-Point Short Messages on SDCCH

3 A3349A: Uplink Point-to-Point Short Messages on TCH

4 A3349B: Downlink Point-to-Point Short Messages on TCH

5 CA334A: Total Uplink Point-to-Point Short Messages

6 CA334B: Total Downlink Point-to-Point Short Messages

7 CA3340: Point-to-Point Short Messages on SDCCH

8 CA3349: Point-to-Point Short Messages on TCH

12.4.2 Uplink Point-to-Point Short Messages on SDCCH

Counter

A3340A: Uplink Point-to-Point Short Messages on SDCCH

Meaning

This counter measures the number of uplink point-to-point short messages on the SDCCH.

Uplink short messages are sent from the MS to the BSC.

Trigger Point

The measurement is triggered when the BSC receives an uplink point-to-point short message

on the SDCCH.

Formula

None.



12 Call Measurement




12.4.3 Downlink Point-to-Point Short Messages on SDCCH

Counter

A3340B: Downlink Point-to-Point Short Messages on SDCCH

Meaning

This counter measures the number of downlink point-to-point short messages on the SDCCH.

Downlink short messages are sent from the BSC to the MS.

Trigger Point

The measurement is triggered when the BSC sends a downlink point-to-point short message

on the SDCCH.

Formula

None.

12.4.4 Uplink Point-to-Point Short Messages on TCH

Counter

A3349A: Uplink Point-to-Point Short Messages on TCH

Meaning

This counter measures the number of uplink point-to-point short messages on the TCH.

Trigger Point

The measurement is triggered when the BSC receives an uplink point-to-point short messageon the TCH.

Formula

None.

12.4.5 Downlink Point-to-Point Short Messages on TCH

Counter

A3349B: Downlink Point-to-Point Short Messages on TCH

Meaning

This counter measures the number of downlink point-to-point short messages on the TCH.






Trigger Point

The measurement is triggered when the BSC sends a downlink point-to-point short message

on the TCH.

Formula

None.

12.4.6 Total Uplink Point-to-Point Short Messages

Counter

CA334A: Total Uplink Point-to-Point Short Messages

Meaning

This counter measures the total number of uplink point-to-point short messages.

Trigger Point

None.

Formula

Total Uplink Point-to-Point Short Messages = [Uplink Point-to-Point Short Messages on

SDCCH] + [Uplink Point-to-Point Short Messages on TCH]

12.4.7 Total Downlink Point-to-Point Short Messages

Counter

CA334B: Total Downlink Point-to-Point Short Messages

Meaning

This counter measures the total number of downlink point-to-point short messages.

Trigger Point

None.

Formula

Downlink Point-to-Point Short Messages = [Downlink Point-to-Point Short Messages on

SDCCH] + [Downlink Point-to-Point Short Messages on TCH]

12.4.8 Point-to-Point Short Messages on SDCCH

Counter

CA3340: Point-to-Point Short Messages on SDCCH



12 Call Measurement




Meaning

This counter measures the number of point-to-point short messages on the SDCCH.

Trigger Point None.

Formula

Point-to-Point Short Messages on SDCCH = [Uplink Point-to-Point Short Messages on

SDCCH] + [Downlink Point-to-Point Short Messages on SDCCH]

12.4.9 Point-to-Point Short Messages on TCH

Counter

CA3349: Point-to-Point Short Messages on TCH

Meaning

This counter measures the number of point-to-point short messages on the TCH.

Trigger Point

None.

FormulaPoint-to-Point Short Messages on TCH = [Uplink Point-to-Point Short Messages on TCH] +[Downlink Point-to-Point Short Messages on TCH]

12.5 Call Drop Measurement per Cell

12.5.1 Overview

Call Drop Measurement per Cell is used to measure the call drops based on the causes,

channel types, service types, and call status of the call drops.

Table 12-5 lists the counter classification of Call Drop Measurement per Cell.

Table 12-5 Counter classification of Call Drop Measurement per Cell

Counter Classification Section

Call Drop Sampled Measurement per Cell 12.5.2

Call Drop Analyzed Measurement per Cell 12.5.3






12.5.2 Call Drop Sampled Measurement per Cell

Counter

Table 12-6 lists the counters of Call Drop Sampled Measurement per Cell.

Table 12-6 Counters of Call Drop Sampled Measurement per Cell

Number Counter

1 M3000A: Call Drops due to ERR IND Received on SDCCH in Stable State(T200 Expired)

2 M3000B: Call Drops due to ERR IND Received on SDCCH in Stable State

(Unsolicited DM Response)

3 M3000C: Call Drops due to ERR IND Received on SDCCH in Stable State

(Sequence Error)

4 M3400A: Call Drops due to ERR IND Received on TCHF (Signaling Channel)in Stable State (T200 Expired)

5 M3400B: Call Drops due to ERR IND Received on TCHF (Signaling Channel)in Stable State (Unsolicited DM Response)

6 M3400C: Call Drops due to ERR IND Received on TCHF (Signaling Channel)in Stable State (Sequence Error)

7 M3500A: Call Drops due to ERR IND Received on TCHH (Signaling Channel)in Stable State (T200 Expired)

8 M3500B: Call Drops due to ERR IND Received on TCHH (Signaling Channel)in Stable State (Unsolicited DM Response)

9 M3500C: Call Drops due to ERR IND Received on TCHH (Signaling Channel)in Stable State (Sequence Error)

10 M3100A: Call Drops due to ERR IND Received on TCHF (Traffic Channel) inStable State (T200 Expired)

11 M3100B: Call Drops due to ERR IND Received on TCHF (Traffic Channel) inStable State (Unsolicited DM Response)

12 M3100C: Call Drops due to ERR IND Received on TCHF (Traffic Channel) in

Stable State (Sequence Error)

13 M3200A: Call Drops due to ERR IND Received on TCHH (Traffic Channel) in

Stable State (T200 Expired)

14 M3200B: Call Drops due to ERR IND Received on TCHH (Traffic Channel) inStable State (Unsolicited DM Response)

15 M3200C: Call Drops due to ERR IND Received on TCHH (Traffic Channel) inStable State (Sequence Error)

16 M3001A: Call Drops due to CONN FAIL Received on SDCCH in Stable State

(Radio Link Failure)



12 Call Measurement




Number Counter

17 M3001B: Call Drops due to CONN FAIL Received on SDCCH in Stable State

(HO Access Failure)

18 M3001C: Call Drops due to CONN FAIL Received on SDCCH in Stable State(OM Intervention)

19 M3001D: Call Drops due to CONN FAIL Received on SDCCH in Stable State(Radio Resource Unavailable)

20 M3001E: Call Drops due to CONN FAIL Received on SDCCH in Stable State

(Other Causes)

21 M3401A: Call Drops due to CONN FAIL Received on TCHF (SignalingChannel) in Stable State (Radio Link Failure)

22 M3401B: Call Drops due to CONN FAIL Received on TCHF (Signaling

Channel) in Stable State (HO Access Failure)

23 M3401C: Call Drops due to CONN FAIL Received on TCHF (SignalingChannel) in Stable State (OM Intervention)

24 M3401D: Call Drops due to CONN FAIL Received on TCHF (Signaling

Channel) in Stable State (Radio Resource Unavailable)

25 M3401E: Call Drops due to CONN FAIL Received on TCHF (SignalingChannel) in Stable State (Other Causes)

26 M3501A: Call Drops due to CONN FAIL Received on TCHH (SignalingChannel) in Stable State (Radio Link Failure)

27 M3501B: Call Drops due to CONN FAIL Received on TCHH (SignalingChannel) in Stable State (HO Access Failure)

28 M3501C: Call Drops due to CONN FAIL Received on TCHH (SignalingChannel) in Stable State (OM Intervention)

29 M3501D: Call Drops due to CONN FAIL Received on TCHH (SignalingChannel) in Stable State (Radio Resource Unavailable)

30 M3501E: Call Drops due to CONN FAIL Received on TCHH (SignalingChannel) in Stable State (Other Causes)

31 M3101A: Call Drops due to CONN FAIL Received on TCHF (Traffic

Channel) in Stable State (Radio Link Failure)

32 M3101B: Call Drops due to CONN FAIL Received on TCHF (TrafficChannel) in Stable State (HO Access Failure)

33 M3101C: Call Drops due to CONN FAIL Received on TCHF (TrafficChannel) in Stable State (OM Intervention)

34 M3101D: Call Drops due to CONN FAIL Received on TCHF (TrafficChannel) in Stable State (Radio Resource Unavailable)

35 M3101E: Call Drops due to CONN FAIL Received on TCHF (TCH) in Stable

State (Other Causes)






Number Counter

36 M3201A: Call Drops due to CONN FAIL Received on TCHH (TCH) in Stable

State (Radio Link Failure)

37 M3201B: Call Drops due to CONN FAIL Received on TCHH (TCH) in StableState (HO Access Failure)

38 M3201C: Call Drops due to CONN FAIL Received on TCHH (TCH) in StableState (OM Intervention)

39 M3201D: Call Drops due to CONN FAIL Received on TCHH (TCH) in Stable

State (Radio Resource Unavailable)

40 M3201E: Call Drops due to CONN FAIL Received on TCHH (TCH) in StableState (Other Causes)

41 M3002: Call Drops due to REL IND Received on SDCCH

42 M3402: Call Drops due to REL IND Received on TCHF (Signaling Channel)

43 M3102: Call Drops due to REL IND Received on TCHF (TCH)

44 M3502: Call Drops due to REL IND Received on TCHH (Signaling Channel)

45 M3202: Call Drops due to REL IND Received on TCHH (TCH)

46 M302: Call Drops due to No MRs from MS for a Long Time (SDCCH)

47 M342: Call Drops due to No MRs from MS for a Long Time (TCHF)

(Signaling Channel)

48 M312: Call Drops due to No MRs from MS for a Long Time (TCHF) (TCH)

49 M352: Call Drops due to No MRs from MS for a Long Time (TCHH)(Signaling Channel)

50 M322: Call Drops due to No MRs from MS for a Long Time (TCHH) (TCH)

51 M303: Call Drops due to Abis Terrestrial Link Failure (SDCCH)

52 M343: Call Drops due to Abis Terrestrial Link Failure (TCHF) (Signaling

Channel)

53 M313: Call Drops due to Abis Terrestrial Link Failure (TCHF) (TCH)

54 M353: Call Drops due to Abis Terrestrial Link Failure (TCHH) (SignalingChannel)

55 M323: Call Drops due to Abis Terrestrial Link Failure (TCHH) (TCH)

56 M304: Call Drops due to Equipment Failure (SDCCH)

57 M344: Call Drops due to Equipment Failure (TCHF) (Signaling Channel)

58 M314: Call Drops due to Equipment Failure (TCHF) (TCH)

59 M354: Call Drops due to Equipment Failure (TCHH) (Signaling Channel)

60 M324: Call Drops due to Equipment Failure (TCHH) (TCH)



12 Call Measurement




Number Counter

61 M305: Call Drops due to Forced Handover (SDCCH)

62 M345: Call Drops due to Forced Handover (TCHF) (Signaling Channel)

63 M315: Call Drops due to Forced Handover (TCHF) (TCH)

64 M355: Call Drops due to Forced Handover (TCHH) (Signaling Channel)

65 M325: Call Drops due to Forced Handover (TCHH) (TCH)

66 M306: Call Drops due to Resource Check (SDCCH)

67 M346: Call Drops due to Resource Check (TCHF) (Signaling Channel)

68 M356: Call Drops due to Resource Check (TCHH) (Signaling Channel)

69 M316: Call Drops due to Resource Check (TCHF) (Traffic Channel)

70 M326: Call Drops due to Resource Check (TCHH) (Traffic Channel)

71 M317: Call Drops after Answer (TCHF) (Traffic Channel)

72 M327: Call Drops after Answer (TCHH) (Traffic Channel)

73 M318: Successful Connections (TCHF) (Traffic Channel)

74 M328: Successful Connections (TCHH) (Traffic Channel)

75 M309: Clear Requests Sent on the A-Interface (SDCCH)

76 M349: Clear Requests Sent on the A-Interface (TCHF) (Signaling Channel)

77 M359: Clear Requests Sent on the A-Interface (TCHH) (Signaling Channel)

78 M319A: Clear Requests Sent on the A-Interface in Stable State (TCHF)(Traffic Channel)

79 M319B: Clear Requests Sent on the A-Interface in Handover State (TCHF)

(Traffic Channel)

80 M329A: Clear Requests Sent on the A-Interface in Stable State (TCHH)

(Traffic Channel)

81 M329B: Clear Requests Sent on the A-Interface in Handover State (TCHH)

(Traffic Channel)

Meaning

After an MS occupies a channel, the BTS sends an ERR IND message to the BSC because ofradio link errors. Call drops occur on the Um interface. When receiving the ERR IND

message with a cause value of timer T200 expired (N200+1) times (0x01), unsolicited DMresponse, multiple frame established state (0x05), or sequence error (0x07) in it, the BSC

measures the call drop counters related to ERR IND. The measurement is based on thechannel type (SDCCH, TCHF, or TCHH), service type (signaling or traffic), and cause value.

After an MS occupies a channel, the BTS sends a CONN FAIL IND message to the BSC because of radio link errors or hardware failure. Call drops occur on the Um interface. When






receiving the CONN FAIL IND message with a cause value of radio link failure (0x01),handover access failure (0x02), OM intervention (0x07), or radio resource not available (0x21)in it, the BSC measures the call drop counters related to CONN FAIL IND on the basis of the

channel type (SDCCH, TCHF, or TCHH), service type (signaling or traffic), and cause value.

In multiframe link setup status, the BTS sends a REL IND message to the BSC after receivingthe DISC frame from an MS. Call drops occur on the Um interface. The BSC measures the

call drop counters related to REL IND on the basis of the channel type (SDCCH, TCHF, orTCHH), service type (signaling or traffic), and cause value.

After an MS occupies an SDCCH, it sends a measurement report to the network every 470 ms.

After an MS occupies a TCH, it sends a measurement report to the network every 480 ms. Ifthe BSC does not receive any measurement report within scheduled time (five minutes by

default), call drops occur on the Um interface. The BSC measures the call drop countersrelated to no measurement reports based on the channel type (SDCCH, TCHF, or TCHH) and

the service type (signaling or traffic).

After an MS occupies a channel, the BTS sends a CONN FAIL IND message to the BSC

because of radio link connection failure. Call drops occur on the Um interface. Whenreceiving the CONN FAIL IND message with a cause equipment failure (0x20) or terrestrialchannel failure (0x22), the BSC measures the call drop counters related to hardware failure on

the basis of the channel type (SDCCH, TCHF, or TCHH), service type (signaling or traffic),and cause value.

After an MS occupies a channel, the BSC measures the call drop counters related to

equipment failure on the basis of the channel type (SDCCH, TCHF, or TCHH) and the servicetype (signaling or traffic) if a release procedure is initiated because of BSC internal errors.

After an MS occupies a channel, a forced handover is initiated but failed. If the release procedure is required, the BSC measures the call drop counters related to the forced handover

based on the channel type (SDCCH, TCHF, or TCHH) and the service type (signaling or

traffic).

After an MS occupies a channel, a release procedure is initiated if the resource check fails.

The BSC measures the call drop counters related to the resource check based on the channeltype (SDCCH, TCHF, or TCHH) and the service type (signaling or traffic).

After a call is established, a conversation begins if the called party answers. If a call drop

occurs for a certain reason, the BSC measures the related call drop counters after aconversation begins based on the channel type (TCHF or TCHH).

After a call is established, the BSC receives the CONN message from the called MS and the

CONN ACK message from the calling MS if the called party answers. The BSC measures thecounters related to successful connections based on the channel type (TCHF or TCHH).

After an MS occupies a channel, the BSC measures the counters related to clear requests senton the A interface on the basis of the channel type (SDCCH, TCHF, or TCHH), service type(signaling or traffic), or status (stable or HO) when the BSC sends a CLR REQ message to the

MSC.

Trigger Point

The measurement of call drops is triggered when a call drop occurs. The measurement of

successful connections is triggered when the called party answers.

Formula

None.



12 Call Measurement




12.5.3 Call Drop Analyzed Measurement per Cell

Counter

Table 12-7 lists the counters of Call Drop Analyzed Measurement per Cell.

Table 12-7 Counters of Call Drop Analyzed Measurement per Cell

Number Counter

1 CM33: Call Drops on TCH

2 CM360: Call Drops on Radio Interface in Stable State (Signaling Channel)

3 CM361: Call Drops on Radio Interface in Handover State (Signaling Channel)

4 CM36: Call Drops on Signaling Channel

5 CM330: Call Drops on Radio Interface in Stable State (TCH)

6 CM331: Call Drops on Radio Interface in Handover State (TCH)

7 CM3600: Call Drops on Signaling Channel in Stable State (Error Indication)

8 CM3601: Call Drops on Signaling Channel in Stable State (ConnectionFailure)

9 CM3602: Call Drops on Signaling Channel in Stable State (Release Indication)

10 CM36C: Call Drops on Radio Interface (Signaling Channel)

11 CM362: Call Drops due to No MRs from MS for a Long Time (Signaling

Channel)

12 CM363: Call Drops due to Abis Terrestrial Link Failure (Signaling Channel)

13 CM364: Call Drops due to Equipment Failure (Signaling Channel)

14 CM365: Call Drops due to Forced Handover (Signaling Channel)

15 CM33C: Call Drops on Radio Interface (TCH)

16 CM3301: Call Drops on TCH in Stable State (Connection Failure)

17 CM3300: Call Drops on TCH in Stable State (Error Indication)

18 CM3302: Call Drops on TCH in Stable State (Release Indication)

19 CM332: Call Drops due to No MRs from MS for a Long Time (TCH)

20 CM333: Call Drops due to Abis Terrestrial Link Failure (TCH)

21 CM334: Call Drops due to Equipment Failure (TCH)

22 CM335: Call Drops due to Forced Handover (TCH)

23 CM30: Call Drops on SDCCH

24 CM30A: Call Drops on Radio Interface (SDCCH)

25 CM396: Call Drops due to Resource Check






Number Counter

26 CM337: Call Drops after Answer

27 CM338: Successful Connections

28 CM369: Clear Requests Sent on the A Interface (TCH) (Signaling Channel)

29 CM339A: Clear Requests Sent on the A Interface in Stable State (TCH)(Traffic Channel)

30 CM339B: Clear Requests Sent on the A Interface in Handover State (TCH)

(Traffic Channel)

31 CM339: Clear Requests Sent on the A Interface (TCH) (Traffic Channel)

Meaning

None.

Trigger Point

None.

Formula

Call Drops on TCH =

[Call Drops on Radio Interface in Stable State (TCH)] +

[Call Drops on Radio Interface in Handover State (TCH)] +

[Call Drops due to No MRs from MS for a Long Time (TCH)] +

[Call Drops due to Abis Terrestrial Link Failure (TCH)] +

[Call Drops due to Equipment Failure (TCH)] +

[Call Drops due to Forced Handover (TCH)]

Call Drops on Radio Interface in Stable State (Signaling Channel) =

[Call Drops on Signaling Channel in Stable State (Error Indication)] +

[Call Drops on Signaling Channel in Stable State (Connection Failure)] +

[Call Drops on Signaling Channel in Stable State (Release Indication)]

Call Drops on Radio Interface in Handover State (Signaling Channel) =

[Failed Internal Intra-Cell Handovers (Timer Expired) (SDCCH)] +

[Failed Internal Intra-Cell Handovers (Timer Expired) (TCHF) (Signaling Channel)] +

[Failed Internal Intra-Cell Handovers (Timer Expired) (TCHH) (Signaling Channel)] +



12 Call Measurement




[Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (SDCCH) (ExcludingDirected Retry)] +

[Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (Directed Retry)] +

[Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (TCHF) (Signaling Channel)]+

[Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (TCHH) (Signaling Channel)]+

[Failed Outgoing External Inter-Cell Handovers (T8 Expired) (SDCCH) (Excluding Directed

Retry)] +

[Failed Outgoing External Inter-Cell Handovers (T8 Expired) (Directed Retry)] +

[Failed Outgoing External Inter-Cell Handovers (T8 Expired) (TCHF) (Signaling Channel)] +

[Failed Outgoing External Inter-Cell Handovers (T8 Expired) (TCHH) (Signaling Channel)] +

[Failed Incoming External Inter-Cell Handovers (Timer Expired) (SDCCH)] +

[Failed Incoming External Inter-Cell Handovers (Timer Expired) (TCH) (Signaling Channel)]

Call Drops on Signaling Channel =

[Call Drops on Radio Interface in Stable State (Signaling Channel)] +

[Call Drops on Radio Interface in Handover State (Signaling Channel)] +

[Call Drops due to No MRs from MS for a Long Time (Signaling Channel)] +

[Call Drops due to Abis Terrestrial Link Failure (Signaling Channel)] +[Call Drops due to Equipment Failure (Signaling Channel)] +

[Call Drops due to Forced Handover (Signaling Channel)]

Call Drops on Radio Interface in Stable State (TCH) =

[Call Drops on TCH in Stable State (Error Indication)] +

[Call Drops on TCH in Stable State (Connection Failure)] +

[Call Drops on TCH in Stable State (Release Indication)]

Call Drops on Radio Interface in Handover State (TCH) =

[Failed Internal Intra-Cell Handovers (Timer Expired) (TCHF) (Traffic Channel)] +

[Failed Internal Intra-Cell Handovers (Timer Expired) (TCHH) (Traffic Channel)] +

[Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (TCHF) (Traffic Channel)] +

[Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (TCHH) (Traffic Channel)] +

[Failed Outgoing External Inter-Cell Handovers (T8 Expired) (TCHF) (Traffic Channel)] +

[Failed Outgoing External Inter-Cell Handovers (T8 Expired) (TCHH) (Traffic Channel)] +






[Failed Incoming External Inter-Cell Handovers (Timer Expired) (TCH) (Traffic Channel)]

Call Drops on Signaling Channel in Stable State (Error Indication) =

[Call Drops due to ERR IND Received on SDCCH in Stable State (T200 Expired)] +

[Call Drops due to ERR IND Received on SDCCH in Stable State (Unsolicited DMResponse)] +

[Call Drops due to ERR IND Received on SDCCH in Stable State (Sequence Error)] +

[Call Drops due to ERR IND Received on TCHF in Stable State (T200 Expired) (Signaling

Channel)] +

[Call Drops due to ERR IND Received on TCHF (Signaling Channel) in Stable State(Unsolicited DM Response)] +

[Call Drops due to ERR IND Received on TCHF (Signaling Channel) in Stable State

(Sequence Error)] +

[Call Drops due to ERR IND Received on TCHH (Signaling Channel) in Stable State (T200

Expired)] +

[Call Drops due to ERR IND Received on TCHH (Signaling Channel) in Stable State(Unsolicited DM Response)] +

[Call Drops due to ERR IND Received on TCHH (Signaling Channel) in Stable State

(Sequence Error)]

Call Drops on Signaling Channel in Stable State (Connection Failure) =

[Call Drops due to CONN FAIL Received on SDCCH in Stable State (Radio Link Failure)] +

[Call Drops due to CONN FAIL Received on SDCCH in Stable State (HO Access Failure)] +

[Call Drops due to CONN FAIL Received on SDCCH in Stable State (OM Intervention)] +

[Call Drops due to CONN FAIL Received on SDCCH in Stable State (Radio ResourceUnavailable)] +

[Call Drops due to CONN FAIL Received on SDCCH in Stable State (Other Causes)] +

[Call Drops due to CONN FAIL Received on TCHF (Signaling Channel) in Stable State(Radio Link Failure)] +

[Call Drops due to CONN FAIL Received on TCHF (Signaling Channel) in Stable State (HOAccess Failure)] +

[Call Drops due to CONN FAIL Received on TCHF (Signaling Channel) in Stable State (OM

Intervention)] +

[Call Drops due to CONN FAIL Received on TCHF (Signaling Channel) in Stable State

(Radio Resource Unavailable) in Stable State (OM Intervention)] +

[Call Drops due to CONN FAIL Received on TCHF (Signaling Channel) in Stable State

(Other Causes)] +

[Call Drops due to CONN FAIL Received on TCHH (Signaling Channel) in Stable State

(Radio Link Failure)] +



12 Call Measurement




[Call Drops due to CONN FAIL Received on TCHH (Signaling Channel) in Stable State (HOAccess Failure)] +

[Call Drops due to CONN FAIL Received on TCHH (Signaling Channel) in Stable State (OM

Intervention)] +

[Call Drops due to CONN FAIL Received on TCHH (Signaling Channel) in Stable State

(Radio Resource Unavailable)] +

[Call Drops due to CONN FAIL Received on TCHH (Signaling Channel) in Stable State(Other Causes)]

Call Drops on Signaling Channel in Stable State (Release Indication) =

[Call Drops due to REL IND Received on SDCCH] +

[Call Drops due to REL IND Received on TCHF (Signaling Channel)] +

[Call Drops due to REL IND Received on TCHH (Signaling Channel)]

Call Drops on Radio Interface (Signaling Channel) =

[Call Drops on Radio Interface in Stable State (Signaling Channel)] +

[Call Drops on Radio Interface in Handover State (Signaling Channel)]

Call Drops due to No MRs from MS for a Long Time (Signaling Channel) =

[Call Drops due to No MRs from MS for a Long Time (SDCCH)] +[Call Drops due to No MRs from MS for a Long Time (TCHF) (Signaling Channel)] +

[Call Drops due to No MRs from MS for a Long Time (TCHH) (Signaling Channel)]

Call Drops due to Abis Terrestrial Link Failure (Signaling Channel) =

[Call Drops due to Abis Terrestrial Link Failure (SDCCH)] +

[Call Drops due to Abis Terrestrial Link Failure (TCHF) (Signaling Channel)] +

[Call Drops due to Abis Terrestrial Link Failure (TCHH) (Signaling Channel)]

Call Drops due to Equipment Failure (Signaling Channel) =

[Call Drops due to Equipment Failure (SDCCH)] +

[Call Drops due to Equipment Failure (TCHF) (Signaling Channel)] +

[Call Drops due to Equipment Failure (TCHH) (Signaling Channel)]

Call Drops due to Forced Handover (Signaling Channel) =

[Call Drops due to Forced Handover (SDCCH)] +

[Call Drops due to Forced Handover (TCHF) (Signaling Channel)] +






[Call Drops due to Forced Handover (TCHH) (Signaling Channel)]

Call Drops on Radio Interface (TCH) =


[Call Drops on Radio Interface in Handover State (TCH)] +

Call Drops on TCH in Stable State (Connection Failure) =

[Call Drops due to CONN FAIL Received on TCHF (TCH) in Stable State (Radio Link

Failure)] +

[Call Drops due to CONN FAIL Received on TCHF (TCH) in Stable State (HO Access

Failure)] +

[Call Drops due to CONN FAIL Received on TCHF (TCH) in Stable State (OM Intervention)]+

[Call Drops due to CONN FAIL Received on TCHF (TCH) in Stable State (Radio ResourceUnavailable)] +

[Call Drops due to CONN FAIL Received on TCHF (TCH) in Stable State (Other Causes)] +

[Call Drops due to CONN FAIL Received on TCHH (TCH) in Stable State (Radio Link

Failure)] +

[Call Drops due to CONN FAIL Received on TCHH (TCH) in Stable State (HO AccessFailure)] +

[Call Drops due to CONN FAIL Received on TCHH (TCH) in Stable State (OM Intervention)]+

[Call Drops due to CONN FAIL Received on TCHH (TCH) in Stable State (Radio Resource

Unavailable)] +

[Call Drops due to CONN FAIL Received on TCHH (TCH) in Stable State (Other Causes)]

Call Drops on TCH in Stable State (Error Indication) =

[Call Drops due to ERR IND Received on TCHF (TCH) in Stable State (T200 Expired)] +

[Call Drops due to ERR IND Received on TCHF (TCH) in Stable State (Unsolicited DMResponse)] +

[Call Drops due to ERR IND Received on TCHF (TCH) in Stable State (Sequence Error)] +

[Call Drops due to ERR IND Received on TCHH (TCH) in Stable State (T200 Expired)] +

[Call Drops due to ERR IND Received on TCHH (TCH) in Stable State (Unsolicited DM

Response)] +

[Call Drops due to ERR IND Received on TCHH (TCH) in Stable State (Sequence Error)]

Call Drops on TCH in Stable State (Release Indication) =



12 Call Measurement




[Call Drops due to REL IND Received on TCHF (TCH)] +

[Call Drops due to REL IND Received on TCHH (TCH)]

Call Drops due to No MRs from MS for a Long Time (TCH) =

[Call Drops due to No MRs from MS for a Long Time (TCHF) (TCH)] +

[Call Drops due to No MRs from MS for a Long Time (TCHH) (TCH)]

Call Drops due to Abis Terrestrial Link Failure (TCH) =

[Call Drops due to Abis Terrestrial Link Failure (TCHF) (TCH)] +

[Call Drops due to Abis Terrestrial Link Failure (TCHH) (TCH)]

Call Drops due to Equipment Failure (TCH) =

[Call Drops due to Equipment Failure (TCHF) (TCH)] +

[Call Drops due to Equipment Failure (TCHH) (TCH)]

Call Drops due to Forced Handover (TCH) =

[Call Drops due to Forced Handover (TCHF) (TCH)] +

[Call Drops due to Forced Handover (TCHH) (TCH)]

Call Drops on SDCCH =

[Call Drops on Radio Interface (SDCCH)] +

[Call Drops due to No MRs from MS for a Long Time (SDCCH)] +

[Call Drops due to Abis Terrestrial Link Failure (SDCCH)] +

[Call Drops due to Equipment Failure (SDCCH)] +

[Call Drops due to Forced Handover (SDCCH)]

Call Drops on Radio Interface (SDCCH) =

[Call Drops due to ERR IND Received on SDCCH in Stable State (T200 Expired)] +

[Call Drops due to ERR IND Received on SDCCH in Stable State (Unsolicited DM

Response)] +

[Call Drops due to ERR IND Received on SDCCH in Stable State (Sequence Error)] +

[Call Drops due to CONN FAIL Received on SDCCH in Stable State (Radio Link Failure)] +

[Call Drops due to CONN FAIL Received on SDCCH in Stable State (HO Access Failure)] +

[Call Drops due to CONN FAIL Received on SDCCH in Stable State (OM Intervention)] +






[Call Drops due to CONN FAIL Received on SDCCH in Stable State (Radio ResourceUnavailable)] +

[Call Drops due to CONN FAIL Received on SDCCH in Stable State (Other Causes)] +

[Call Drops due to REL IND Received on SDCCH] +[Failed Internal Intra-Cell Handovers (Timer Expired) (SDCCH)] +

[Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (SDCCH) (Excluding

Directed Retry)] +

[Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (Directed Retry)] +

[Failed Outgoing External Inter-Cell Handovers (T8 Expired) (SDCCH) (Excluding Directed

Retry)] +

[Failed Outgoing External Inter-Cell Handovers (T8 Expired) (Directed Retry)] +

[Failed Incoming External Inter-Cell Handovers (Timer Expired) (SDCCH)]

Call Drops due to Resource Check =

[Call Drops due to Resource Check (SDCCH)] +

[Call Drops due to Resource Check (TCHF) (Signaling Channel)] +

[Call Drops due to Resource Check (TCHH) (Signaling Channel)] +

[Call Drops due to Resource Check (TCHF) (TCH)] +

[Call Drops due to Resource Check (TCHH) (TCH)]

Call Drops after Answer =

[Call Drops after Answer (TCHF) (TCH)] +

[Call Drops after Answer (TCHH) (TCH)]

Successful Connections =

[Successful Connections (TCHF) (TCH)] +

[Successful Connections (TCHH) (TCH)]

Clear Requests Sent on the A Interface (TCH) (Signaling Channel) =

[Clear Requests Sent on the A-Interface (TCHF) (Signaling Channel)] +

[Clear Requests Sent on the A-Interface (TCHH) (Signaling Channel)]

Clear Requests Sent on the A Interface in Stable State (TCH) (Traffic Channel) =

[Clear Requests Sent on the A-Interface in Stable State (TCHF) (TCH)] +

[Clear Requests Sent on the A-Interface in Stable State (TCHH) (TCH)]



12 Call Measurement




Clear Requests Sent on the A Interface in Handover State (TCH) (Traffic Channel) =

[Clear Requests Sent on the A-Interface in Handover State (TCHF) (TCH)] +

[Clear Requests Sent on the A-Interface in Handover State (TCHH) (TCH)]

Clear Requests Sent on the A Interface (TCH) (Traffic Channel) =

[Clear Requests Sent on the A-Interface in Stable State (TCH) (Traffic Channel)] +

[Clear Requests Sent on the A Interface in Handover State (TCH) (Traffic Channel)]

12.6 Channel Activation Measurement per Cell

12.6.1 OverviewChannel Activation Measurement per Cell is used to measure the activation of all types ofchannels in a cell.

Table 12-8 lists the counter classification of Channel Activation Measurement per Cell.

Table 12-8 Counter classification of Channel Activation Measurement per Cell


SDCCH Connection Measurement per Cell 12.6.2

TCH Connection Measurement per Cell 12.6.3

Channel Activation Analyzed Measurement per Cell 12.6.4

12.6.2 SDCCH Connection Measurement per Cell

Counter

Table 12-9 lists the counters of SDCCH Connection Measurement per Cell.

Table 12-9 Counters of SDCCH Connection Measurement per Cell

Number Counter

1 R3300A: Channel Activation Attempts in Immediate Assignment Procedure(SDCCH)

2 R3300B: CHAN ACTIV NACK Messages Sent by BTS in ImmediateAssignment Procedure (SDCCH)

3 R3300C: Channel Activation Timeouts in Immediate Assignment Procedure

(SDCCH)

4 R3330A: Channel Activation Attempts in Internal Intra-Cell Handover

Procedure (SDCCH)






Number Counter

5 R3330B: CHAN ACTIV NACK Messages Sent by BTS in Internal Intra-Cell

Handover Procedure (SDCCH)

6 R3330C: Channel Activation Timeouts in Internal Intra-Cell HandoverProcedure (SDCCH)

7 R3340A: Channel Activation Attempts in Incoming Internal Inter-CellHandover Procedure (SDCCH)

8 R3340B: CHAN ACTIV NACK Messages Sent by BTS in Incoming Internal

Inter-Cell Handover Procedure (SDCCH)

9 R3340C: Channel Activation Timeouts in Incoming Internal Inter-CellHandover Procedure (SDCCH)

10 R3350A: Channel Activation Attempts in Incoming External Inter-Cell


11 R3350B: CHAN ACTIV NACK Messages Sent by BTS in Incoming ExternalInter-Cell Handover Procedure (SDCCH)

12 R3350C: Channel Activation Timeouts in Incoming External Inter-Cell


Meaning

After receiving a CHAN RQD message from the BTS, the BSC measures R3300A: Channel

Activation Attempts in Immediate Assignment Procedure (SDCCH) in the cell where theSDCCH is located if the BSC assigns an SDCCH and sends a CHAN ACTIV message to theBTS.

In the SDCCH immediate assignment procedure, the BSC sends a CHAN ACTIV message to

the BTS. If the BTS returns a CHAN ACTIV NACK message, the SDCCH activation fails.The BSC measures R3300B: CHAN ACTIV NACK Messages Sent by BTS in ImmediateAssignment Procedure (SDCCH) in the cell where the SDCCH is located.

In the SDCCH immediate assignment procedure, the BSC sends a CHAN ACTIV message tothe BTS and triggers an internal timer. If no CHAN ACTIV ACK message is received withinscheduled time (five seconds by default), the BSC measures R3300C: Channel Activation

Timeouts in Immediate Assignment Procedure (SDCCH) in the cell where the SDCCH is

located.

When the MS is in stable state on the SDCCH, the BSC sends a CHAN ACTIV message to

the BTS where the target cell is located if the BSC decides to initiate a handover based on

measurement reports and if the target cell is the current cell. The BSC measures R3330A:Channel Activation Attempts in Internal Intra-Cell Handover Procedure (SDCCH) in the cellwhere the target SDCCH is located.

In the intra-cell SDCCH handover procedure, the BSC sends a CHAN ACTIV message to theBTS. If the BTS returns a CHAN ACTIV NACK message, the SDCCH handover fails. The

BSC measures R3330B: CHAN ACTIV NACK Messages Sent by BTS in Internal Intra-CellHandover Procedure (SDCCH) in the cell where the target SDCCH is located.



12 Call Measurement




In the intra-cell SDCCH handover procedure, the BSC sends a CHAN ACTIV message to theBTS and triggers an internal timer. If no CHAN ACTIV ACK message is received withinscheduled time (five seconds by default), the BSC measures R3330C: Channel Activation

Timeouts in Internal Intra-Cell Handover Procedure (SDCCH) in the cell where the targetSDCCH is located.

When the MS is in stable state on the SDCCH, the BSC sends a CHAN ACTIV message to

the BTS where the target cell is located if the BSC decides to initiate a handover based onmeasurement reports and if the target cell and the current cell are two cells in one BSC. The

BSC measures R3340A: Channel Activation Attempts in Incoming Internal Inter-CellHandover Procedure (SDCCH) in the cell where the target SDCCH is located.

In the incoming internal inter-cell SDCCH handover procedure, the BSC sends a CHAN

ACTIV message to the BTS. If the BTS returns a CHAN ACTIV NACK message, theSDCCH handover fails. The BSC measures R3340B: CHAN ACTIV NACK Messages Sent

by BTS in Incoming Internal Inter-Cell Handover Procedure (SDCCH) in the cell where thetarget SDCCH is located.

In the incoming internal inter-cell SDCCH handover procedure, the BSC sends a CHANACTIV message to the BTS and triggers an internal timer. If no CHAN ACTIV ACK messageis received within scheduled time (five seconds by default), the BSC measures R3340C:

Channel Activation Timeouts in Incoming Internal Inter-Cell Handover Procedure (SDCCH)in the cell where the target SDCCH is located.

After receiving an HO REQ message from the MSC, the BSC measures R3350A: Channel

Activation Attempts in Incoming External Inter-Cell Handover Procedure (SDCCH) in thecell where the target SDCCH is located if the BSC assigns an SDCCH and sends a CHAN

ACTIV message to the BTS.

In the incoming external inter-cell SDCCH handover procedure, the BSC sends a CHAN

ACTIV message to the BTS. If the BTS returns a CHAN ACTIV NACK message, the

SDCCH handover fails. The BSC measures R3350B: CHAN ACTIV NACK Messages Sent by BTS in Incoming External Inter-Cell Handover Procedure (SDCCH) in the cell where the

target SDCCH is located.

In the incoming external inter-cell SDCCH handover procedure, the BSC sends a CHANACTIV message to the BTS and triggers an internal timer. If no CHAN ACTIV ACK message

is received within scheduled time (five seconds by default), the BSC measures R3350C:

Channel Activation Timeouts in Incoming External Inter-Cell Handover Procedure (SDCCH)in the cell where the target SDCCH is located.

Trigger Point

For the trigger points of the counters, see the flow charts in the following measurement units:

Immediate Assignment Measurement per Cell

Assignment Measurement per Cell

Intra-Cell Handover Measurement per Cell

Incoming Internal Inter-Cell Handover Measurement per Cell

Outgoing Internal Inter-Cell Handover Measurement per Cell

Incoming External Inter-Cell Handover Measurement per Cell

Outgoing External Inter-Cell Handover Measurement per Cell

Incoming Inter-RAT Inter-Cell Handover Measurement per Cell







Formula

None.

12.6.3 TCH Connection Measurement per CellCounter

Table 12-10 lists the counters of TCH Connection Measurement per Cell.

Table 12-10 TCH Connection Measurement per Cell

Number Counter

1 R3307A: Channel Activation Attempts in Immediate Assignment Procedure(TCHF)

2 R3308A: Channel Activation Attempts in Immediate Assignment Procedure(TCHH)

3 R3307B: CHAN ACTIV NACK Messages Sent by BTS in Immediate

Assignment Procedure (TCHF)

4 R3308B: CHAN ACTIV NACK Messages Sent by BTS in Immediate

Assignment Procedure (TCHH)

5 R3307C: Channel Activation Timeouts in Immediate Assignment Procedure(TCHF)

6 R3308C: Channel Activation Timeouts in Immediate Assignment Procedure

(TCHH)

7 R3317A: Channel Activation Attempts in Assignment Procedure (TCHF)

8 R3318A: Channel Activation Attempts in Assignment Procedure (TCHH)

9 R3317B: CHAN ACTIV NACK Messages Sent by BTS in AssignmentProcedure (TCHF)

10 R3318B: CHAN ACTIV NACK Messages Sent by BTS in Assignment

Procedure (TCHH)

11 R3317C: Channel Activation Timeouts in Assignment Procedure (TCHF)

12 R3318C: Channel Activation Timeouts in Assignment Procedure (TCHH)

13 R3327A: Channel Activation Attempts in Mode Modify Procedure (TCHF)

14 R3328A: Channel Activation Attempts in Mode Modify Procedure (TCHH)

15 R3327B: CHAN ACTIV NACK Messages Sent by BTS in Mode Modify

Procedure (TCHF)

16 R3328B: CHAN ACTIV NACK Messages Sent by BTS in Mode ModifyProcedure (TCHH)

17 R3327C: Channel Activation Timeouts in Mode Modify Procedure (TCHF)

18 R3328C: Channel Activation Timeouts in Mode Modify Procedure (TCHH)



12 Call Measurement




Number Counter

19 R3337A: Channel Activation Attempts in Internal Intra-Cell Handover

Procedure (TCHF)

20 R3338A: Channel Activation Attempts in Internal Intra-Cell HandoverProcedure (TCHH)

21 R3337B: CHAN ACTIV NACK Messages Sent by BTS in Internal Intra-CellHandover Procedure (TCHF)

22 R3338B: CHAN ACTIV NACK Messages Sent by BTS in Internal Intra-Cell

Handover Procedure (TCHH)

23 R3337C: Channel Activation Timeouts in Internal Intra-Cell HandoverProcedure (TCHF)

24 R3338C: Channel Activation Timeouts in Internal Intra-Cell Handover

Procedure (TCHH)

25 R3347A: Channel Activation Attempts in Incoming Internal Inter-CellHandover Procedure (TCHF)

26 R3348A: Channel Activation Attempts in Incoming Internal Inter-Cell


27 R3347B: CHAN ACTIV NACK Messages Sent by BTS in Incoming InternalInter-Cell Handover Procedure (TCHF)

28 R3348B: CHAN ACTIV NACK Messages Sent by BTS in Incoming InternalInter-Cell Handover Procedure (TCHH)

29 R3347C: Channel Activation Timeouts in Incoming Internal Inter-CellHandover Procedure (TCHF)

30 R3348C: Channel Activation Timeouts in Incoming Internal Inter-CellHandover Procedure (TCHH)

31 R3357A: Channel Activation Attempts in Incoming External Inter-CellHandover Procedure (TCHF)

32 R3358A: Channel Activation Attempts in Incoming External Inter-CellHandover Procedure (TCHH)

33 R3357B: CHAN ACTIV NACK Messages Sent by BTS in Incoming External

Inter-Cell Handover Procedure (TCHF)

34 R3358B: CHAN ACTIV NACK Messages Sent by BTS in Incoming ExternalInter-Cell Handover Procedure (TCHH)

35 R3357C: Channel Activation Timeouts in Incoming External Inter-CellHandover Procedure (TCHF)

36 R3358C: Channel Activation Timeouts in Incoming External Inter-CellHandover Procedure (TCHH)






Meaning

In the immediate assignment procedure, the BSC receives a CHAN RQD message from the

BTS. If the BSC assigns a TCH (TCHF or TCHH) and sends a CHAN ACTIV message to the

BTS, the BSC measures R3307A: Channel Activation Attempts in Immediate Assignment

Procedure (TCHF) or R3308A: Channel Activation Attempts in Immediate AssignmentProcedure (TCHH) in the cell where the TCH is located.

In the TCH immediate assignment procedure, the BSC sends a CHAN ACTIV message to theBTS. If the BTS returns a CHAN ACTIV NACK message, the TCH activation fails. The BSC

measures R3307B: CHAN ACTIV NACK Messages Sent by BTS in Immediate AssignmentProcedure (TCHF) or R3308B: CHAN ACTIV NACK Messages Sent by BTS in ImmediateAssignment Procedure (TCHH) in the cell where the TCH is located.

In the TCH immediate assignment procedure, the BSC sends a CHAN ACTIV message to theBTS and triggers an internal timer. If no CHAN ACTIV ACK message is received within

scheduled time (five seconds by default), the BSC measures R3307C: Channel ActivationTimeouts in Immediate Assignment Procedure (TCHF) or R3308C: Channel Activation

Timeouts in Immediate Assignment Procedure (TCHH) in the cell where the TCH is located.

When the signaling or traffic is stable, the BSC receives an ASS REQ message from the MSC.If the requested service is of the speech or the data type and if the assignment procedure

proceeds, the BSC assigns a TCH and sends a CHAN ACTIV message to the BTS.Meanwhile, the BSC measures R3317A: Channel Activation Attempts in Assignment

Procedure (TCHF) and R3318A: Channel Activation Attempts in Assignment Procedure(TCHH) in the cell where the TCH is located.

In the assignment procedure, the BSC assigns a TCH and sends a CHAN ACTIV message to

the BTS. If the BTS returns a CHAN ACTIV NACK message, the channel activation fails.The BSC measures R3317B: CHAN ACTIV NACK Messages Sent by BTS in Assignment

Procedure (TCHF) or R3318B: CHAN ACTIV NACK Messages Sent by BTS in Assignment

Procedure (TCHH) in the cell where the TCH is located.

In the assignment procedure, the BSC assigns a TCH and sends a CHAN ACTIV message tothe BTS. The BSC also triggers an internal timer concurrently. If no CHAN ACTIV ACKmessage is received within scheduled time (five seconds by default), the BSC measures

R3317C: Channel Activation Timeouts in Assignment Procedure (TCHF) or R3318C:Channel Activation Timeouts in Assignment Procedure (TCHH) in the cell where the TCH is

located.

When the signaling or traffic is stable, the BSC receives an ASS REQ message from the MSC.

If the requested service is of the speech or the data type and the BSC decides to initiate theMode Modify procedure, the BSC sends a MODE MODIFY message to the BTS andmeasures R3327A: Channel Activation Attempts in Mode Modify Procedure (TCHF) or

R3328A: Channel Activation Attempts in Mode Modify Procedure (TCHH) in the cell wherethe TCH is located.

In the Mode Modify procedure, the BSC sends a MODE MODIFY message to the BTS. If the

BTS returns a MODE MODIFY NACK message, the Mode Modify procedure fails. The BSC

measures R3327B: CHAN ACTIV NACK Messages Sent by BTS in Mode Modify Procedure(TCHF) or R3328B: CHAN ACTIV NACK Messages Sent by BTS in Mode ModifyProcedure (TCHH) in the cell where the TCH is located.

In the Mode Modify procedure, the BSC sends a MODE MODIFY message to the BTS andtriggers an internal timer. If no MODE MODIFY ACK message is received within scheduledtime (five seconds by default), the BSC measures R3327C: Channel Activation Timeouts in

Mode Modify Procedure (TCHF) or R3328C: Channel Activation Timeouts in Mode Modify

Procedure (TCHH) in the cell where the TCH is located.



12 Call Measurement




When an MS is in stable state on a TCH, the BSC sends a CHAN ACTIV message to the BTSwhere the target cell is located if the BSC decides to initiate a handover based onmeasurement reports and if the target cell is the current cell. The BSC measures R3337A:

Channel Activation Attempts in Internal Intra-Cell Handover Procedure (TCHF) or R3338A:Channel Activation Attempts in Internal Intra-Cell Handover Procedure (TCHH) in the cell

where the target TCH is located.

In the intra-cell TCH handover procedure, the BSC sends a CHAN ACTIV message to theBTS. If the BTS returns a CHAN ACTIV NACK message, the channel activation fails. The

BSC measures R3337B: CHAN ACTIV NACK Messages Sent by BTS in Internal Intra-CellHandover Procedure (TCHF) or R3338B: CHAN ACTIV NACK Messages Sent by BTS in

Internal Intra-Cell Handover Procedure (TCHH) in the cell where the target TCH is located.

In the intra-cell TCH handover procedure, the BSC sends a CHAN ACTIV message to theBTS and triggers an internal timer. If no CHAN ACTIV ACK is received within scheduled

time (five seconds by default), the BSC measures R3337C: Channel Activation Timeouts inInternal Intra-Cell Handover Procedure (TCHF) or R3338C: Channel Activation Timeouts in

Internal Intra-Cell Handover Procedure (TCHH) in the cell where the target TCH is located.

When an MS is in stable state on a TCH, the BSC sends a CHAN ACTIV message to the BTSwhere the target cell is located if the BSC decides to initiate a handover based on

measurement reports and if the target cell and the current cell are two cells in one BSC.Meanwhile, the BSC measures R3347A: Channel Activation Attempts in Incoming Internal

Inter-Cell Handover Procedure (TCHF) or R3348A: Channel Activation Attempts inIncoming Internal Inter-Cell Handover Procedure (TCHH) in the cell where the target TCH is

located.

In the incoming internal inter-cell TCH handover procedure, the BSC sends a CHAN ACTIVmessage to the BTS. If the BTS return s a CHAN ACTIV NACK message, the channel

activation fails. The BSC measures R3347B: CHAN ACTIV NACK Messages Sent by BTSin Incoming Internal Inter-Cell Handover Procedure (TCHF) and R3348B: CHAN ACTIV

NACK Messages Sent by BTS in Incoming Internal Inter-Cell Handover Procedure (TCHH)in the cell where the target TCH is located.

In the incoming internal inter-cell TCH handover procedure, the BSC sends a CHAN ACTIVmessage to the BTS and triggers an internal timer. If no CHAN ACTIV ACK message isreceived within scheduled time (five seconds by default), the BSC measures R3347C:

Channel Activation Timeouts in Incoming Internal Inter-Cell Handover Procedure (TCHF) or

R3348C: Channel Activation Timeouts in Incoming Internal Inter-Cell Handover Procedure(TCHH) in the cell where the target TCH is located.

The BSC receives a HO REQ message from the MSC. If the BSC assigns a TCH and sends a

CHAN ACTIV to the BTS, the BSC measures R3357A: Channel Activation Attempts inIncoming External Inter-Cell Handover Procedure (TCHF) or R3358A: Channel Activation

Attempts in Incoming External Inter-Cell Handover Procedure (TCHH) in the cell where thetarget TCH is located.

In the incoming external inter-cell TCH handover procedure, the BSC sends a CHAN ACTIVmessage to the BTS. If the BTS returns a CHAN ACTIV NACK message, the channel

activation fails. The BSC measures R3357B: CHAN ACTIV NACK Messages Sent by BTS

in Incoming External Inter-Cell Handover Procedure (TCHF) or R3358B: CHAN ACTIV NACK Messages Sent by BTS in Incoming External Inter-Cell Handover Procedure (TCHH)in the cell where the target TCH is located.

In the incoming external inter-cell TCH handover procedure, the BSC sends a CHAN ACTIVmessage to the BTS and triggers an internal timer. If no CHAN ACTIV ACK message isreceived within scheduled time (five seconds by default), the BSC measures R3357C:

Channel Activation Timeouts in Incoming External Inter-Cell Handover Procedure (TCHF) or






R3358C: Channel Activation Timeouts in Incoming External Inter-Cell Handover Procedure(TCHH) in the cell where the target TCH is located.

Trigger Point

For the trigger points of the counters, see the flow charts in the following measurement units:

Immediate Assignment Measurement per Cell

Assignment Measurement per Cell

Intra-Cell Handover Measurement per Cell

Incoming Internal Inter-Cell Handover Measurement per Cell

Outgoing Internal Inter-Cell Handover Measurement per Cell

Incoming External Inter-Cell Handover Measurement per Cell


Incoming Inter-RAT Inter-Cell Handover Measurement per Cell


Formula

None.

12.6.4 Channel Activation Analyzed Measurement per Cell

Counter

Table 12-11 lists the counters of Channel Activation Analyzed Measurement per Cell.

Table 12-11 Counters of Channel Activation Analyzed Measurement per Cell

Number Counter

1 CR33A: Channel Activation Attempts

2 CR330A: Channel Activation Attempts in Immediate Assignment Procedure

3 CR331A: Channel Activation Attempts in Assignment Procedure

4 CR332A: Channel Activation Attempts in Mode Modify Procedure

5 CR333A: Channel Activation Attempts in Internal Intra-Cell HandoverProcedure

6 CR334A: Channel Activation Attempts in Incoming Internal Inter-CellHandover Procedure

7 CR335A: Channel Activation Attempts in Incoming External Inter-CellHandover Procedure

8 CR33B: CHAN ACTIV NACK Messages Sent by BTS

9 CR330B: CHAN ACTIV NACK Messages Sent by BTS in Immediate

Assignment Procedure



12 Call Measurement




Number Counter

10 CR331B: CHAN ACTIV NACK Messages Sent by BTS in Assignment

Procedure

11 CR332B: CHAN ACTIV NACK Messages Sent by BTS in Mode ModifyProcedure

12 CR333B: CHAN ACTIV NACK Messages Sent by BTS in Internal Intra-CellHandover Procedure

13 CR334B: CHAN ACTIV NACK Messages Sent by BTS in Incoming Internal

Inter-Cell Handover Procedure

14 CR335B: CHAN ACTIV NACK Messages Sent by BTS in Incoming ExternalInter-Cell Handover Procedure

15 CR33C: Channel Activation Timeouts

16 CR330C: Channel Activation Timeouts in Immediate Assignment Procedure

17 CR331C: Channel Activation Timeouts in Assignment Procedure

18 CR332C: Channel Activation Timeouts in Mode Modify Procedure

19 CR333C: Channel Activation Timeouts in Internal Intra-Cell HandoverProcedure

20 CR334C: Channel Activation Timeouts in Incoming Internal Inter-CellHandover Procedure

21 CR335C: Channel Activation Timeouts in Incoming External Inter-Cell

Handover Procedure

Meaning

None.

Trigger Point

None.

Formula

Channel Activation Attempts =

[Channel Activation Attempts in Immediate Assignment Procedure] +

[Channel Activation Attempts in Assignment Procedure] +

[Channel Activation Attempts in Mode Modify Procedure] +

[Channel Activation Attempts in Internal Intra-Cell Handover Procedure] +

[Channel Activation Attempts in Incoming Internal Inter-Cell Handover Procedure] +

[Channel Activation Attempts in Incoming External Inter-Cell Handover Procedure]






Channel Activation Attempts in Immediate Assignment Procedure =

[Channel Activation Attempts in Immediate Assignment Procedure (SDCCH)] +

[Channel Activation Attempts in Immediate Assignment Procedure (TCHF)] +

[Channel Activation Attempts in Immediate Assignment Procedure (TCHH)]

Channel Activation Attempts in Assignment Procedure =

[Channel Activation Attempts in Assignment Procedure (TCHF)] +

[Channel Activation Attempts in Assignment Procedure (TCHH)]

Channel Activation Attempts in Mode Modify Procedure =

[Channel Activation Attempts in Mode Modify Procedure (TCHF)] +[Channel Activation Attempts in Mode Modify Procedure (TCHH)]

Channel Activation Attempts in Internal Intra-Cell Handover Procedure =

[Channel Activation Attempts in Internal Intra-Cell Handover Procedure (SDCCH)] +

[Channel Activation Attempts in Internal Intra-Cell Handover Procedure (TCHF)] +

[Channel Activation Attempts in Internal Intra-Cell Handover Procedure (TCHH)]

Channel Activation Attempts in Incoming Internal Inter-Cell Handover Procedure =

[Channel Activation Attempts in Incoming Internal Inter-Cell Handover Procedure (SDCCH)]

+

[Channel Activation Attempts in Incoming Internal Inter-Cell Handover Procedure (TCHF)] +

[Channel Activation Attempts in Incoming Internal Inter-Cell Handover Procedure (TCHH)]

Channel Activation Attempts in Incoming External Inter-Cell Handover Procedure =

[Channel Activation Attempts in Incoming External Inter-Cell Handover Procedure (SDCCH)]

+

[Channel Activation Attempts in Incoming External Inter-Cell Handover Procedure (TCHF)]+

[Channel Activation Attempts in Incoming External Inter-Cell Handover Procedure (TCHH)]

CHAN ACTIV NACK Messages Sent by BTS =

[CHAN ACTIV NACK Messages Sent by BTS in Immediate Assignment Procedure] +

[CHAN ACTIV NACK Messages Sent by BTS in Assignment Procedure] +

[CHAN ACTIV NACK Messages Sent by BTS in Mode Modify Procedure] +



12 Call Measurement




[CHAN ACTIV NACK Messages Sent by BTS in Internal Intra-Cell Handover Procedure] +

[CHAN ACTIV NACK Messages Sent by BTS in Incoming Internal Inter-Cell Handover

Procedure] +

[CHAN ACTIV NACK Messages Sent by BTS in Incoming External Inter-Cell HandoverProcedure]

CHAN ACTIV NACK Messages Sent by BTS in Immediate Assignment Procedure =

[CHAN ACTIV NACK Messages Sent by BTS in Immediate Assignment Procedure(SDCCH)] +

[CHAN ACTIV NACK Messages Sent by BTS in Immediate Assignment Procedure (TCHF)]+

[CHAN ACTIV NACK Messages Sent by BTS in Immediate Assignment Procedure (TCHH)]

CHAN ACTIV NACK Messages Sent by BTS in Assignment Procedure =

[CHAN ACTIV NACK Messages Sent by BTS in Assignment Procedure (TCHF)] +

[CHAN ACTIV NACK Messages Sent by BTS in Assignment Procedure (TCHH)]

CHAN ACTIV NACK Messages Sent by BTS in Mode Modify Procedure =

[CHAN ACTIV NACK Messages Sent by BTS in Mode Modify Procedure (TCHF)] +

[CHAN ACTIV NACK Messages Sent by BTS in Mode Modify Procedure (TCHH)]

CHAN ACTIV NACK Messages Sent by BTS in Internal Intra-Cell Handover Procedure =

[CHAN ACTIV NACK Messages Sent by BTS in Internal Intra-Cell Handover Procedure

(SDCCH)] +


(TCHF)] +


(TCHH)]

CHAN ACTIV NACK Messages Sent by BTS in Incoming Internal Inter-Cell Handover

Procedure =

[CHAN ACTIV NACK Messages Sent by BTS in Incoming Internal Inter-Cell Handover

Procedure (SDCCH)] +

[CHAN ACTIV NACK Messages Sent by BTS in Incoming Internal Inter-Cell HandoverProcedure (TCHF)] +

[CHAN ACTIV NACK Messages Sent by BTS in Incoming Internal Inter-Cell HandoverProcedure (TCHH)]






CHAN ACTIV NACK Messages Sent by BTS in Incoming External Inter-Cell HandoverProcedure =

[CHAN ACTIV NACK Messages Sent by BTS in Incoming External Inter-Cell Handover

Procedure (SDCCH)] +

[CHAN ACTIV NACK Messages Sent by BTS in Incoming External Inter-Cell Handover

Procedure (TCHF)] +

[CHAN ACTIV NACK Messages Sent by BTS in Incoming External Inter-Cell HandoverProcedure (TCHH)]

Channel Activation Timeouts =

[Channel Activation Timeouts in Immediate Assignment Procedure] +

[Channel Activation Timeouts in Assignment Procedure] +

[Channel Activation Timeouts in Mode Modify Procedure] +

[Channel Activation Timeouts in Internal Intra-Cell Handover Procedure] +

[Channel Activation Timeouts in Incoming Internal Inter-Cell Handover Procedure] +

[Channel Activation Timeouts in Incoming External Inter-Cell Handover Procedure]

Channel Activation Timeouts in Immediate Assignment Procedure =

[Channel Activation Timeouts in Immediate Assignment Procedure (SDCCH)] +

[Channel Activation Timeouts in Immediate Assignment Procedure (TCHF)] +[Channel Activation Timeouts in Immediate Assignment Procedure (TCHH)]

Channel Activation Timeouts in Assignment Procedure =

[Channel Activation Timeouts in Assignment Procedure (TCHF)] +

[Channel Activation Timeouts in Assignment Procedure (TCHH)]

Channel Activation Timeouts in Mode Modify Procedure =

[Channel Activation Timeouts in Mode Modify Procedure (TCHF)] +

[Channel Activation Timeouts in Mode Modify Procedure (TCHH)]

Channel Activation Timeouts in Internal Intra-Cell Handover Procedure =

[Channel Activation Timeouts in Internal Intra-Cell Handover Procedure (SDCCH)] +

[Channel Activation Timeouts in Internal Intra-Cell Handover Procedure (TCHF)] +

[Channel Activation Timeouts in Internal Intra-Cell Handover Procedure (TCHH)]



12 Call Measurement




Channel Activation Timeouts in Incoming Internal Inter-Cell Handover Procedure =

[Channel Activation Timeouts in Incoming Internal Inter-Cell Handover Procedure (SDCCH)]

+

[Channel Activation Timeouts in Incoming Internal Inter-Cell Handover Procedure (TCHF)] +[Channel Activation Timeouts in Incoming Internal Inter-Cell Handover Procedure (TCHH)]

Channel Activation Timeouts in Incoming External Inter-Cell Handover Procedure =

[Channel Activation Timeouts in Incoming External Inter-Cell Handover Procedure (SDCCH)]

+

[Channel Activation Timeouts in Incoming External Inter-Cell Handover Procedure (TCHF)]+

[Channel Activation Timeouts in Incoming External Inter-Cell Handover Procedure (TCHH)]

12.7 Channel Seizure Measurement per TRX

Counter

Channel Seizure Measurement per TRX is used to measure the channel seizures in all types ofservice procedures.

Table 12-12 lists the counters of Channel Seizure Measurement per TRX.

Table 12-12 Counters of Channel Seizure Measurement per TRX

Number Counter

1 R4400A: Attempted Immediate Assignments (SDCCH)

2 R4409A: Attempted Immediate Assignments (TCH)

3 R4400B: Successful Immediate Assignments (SDCCH)

4 R4409B: Attempted Immediate Assignment Procedures (TCH)

5 R4419A: Attempted Assignments (TCH)

6 R4419B: Completed Assignments (TCH)

7 R4429A: Attempted Mode Modify Procedures (TCH)

8 R4429B: Completed Mode Modify Procedures (TCH)

9 R4430A: Attempted Handovers (SDCCH)

10 R4439A: Attempted Handovers (TCH)

11 R4430B: Completed Handovers (SDCCH)

12 R4439B: Completed Handovers (TCH)

13 CR440A: Attempted Immediate Assignments






Number Counter

14 CR440B: Successful Immediate Assignments

15 CR443A: Attempted Handovers

16 CR443B: Completed Handovers

Meaning

In the SDCCH immediate assignment procedure, the BSC receives from the BTS a CHAN

ACTIV ACK message, indicating that the SDCCH is successfully activated. The BSC sends

an IMM ASS CMD message, requesting the MS to access the specified SDCCH. Meanwhile,the BSC measures R4400A: Attempted Immediate Assignments (SDCCH) in the TRX where

the SDCCH is located.

In the TCH immediate assignment procedure, the BSC receives from the BTS a CHANACTIV ACK message, indicating that the TCH is successfully activated. The BSC sends an

IMM ASS CMD message, requesting the MS to access the specified TCH. Meanwhile, theBSC measures R4409A: Attempted Immediate Assignments (TCH) in the TRX where the

TCH is located.

In the SDCCH immediate assignment procedure, an MS reports a FIRST SABM frame to theBTS on the SDCCH after seizing the assigned SDCCH. Through this frame, the MS notifies

the BTS that the radio link layer has entered multiframe link setup state. The BTS returns aUA frame to the MS and sends the BSC an EST IND message to notify the BSC that the link

is established on the Um interface. After receiving the EST IND message, the BSC measuresR4400B: Successful Immediate Assignments (SDCCH) in the TRX where the SDCCH is

located.

In the TCH immediate assignment procedure, an MS reports a FIRST SABM frame to theBTS on the TCH after seizing the assigned TCH. Through this frame, the MS notifies the BTS

that the radio link layer has entered multiframe link setup state. The BTS returns a UA frameto the MS and sends the BSC an EST IND message to notify the BSC that the link is

established on the Um interface. After receiving the EST IND message, the BSC measuresR4409B: Attempted Immediate Assignment Procedures (TCH) in the TRX where the TCH islocated.

In the assignment procedure, the BSC assigns a TCH and receives a CHAN ACTIV ACKmessage. The BSC then sends an ASS CMD message to the MS and measures R4419A

Attempted Assignments (TCH) in the TRX where the TCH is located.

In the assignment procedure, the BSC assigns a TCH and sends an ASS CMD message to theMS. After receiving the ASS CMD message, the MS sends the BTS a FIRST SABM frame,

indicating that the Um interface is in multiframe link setup state. The BTS returns a UA frameto the MS and sends the BSC an EST IND message, indicating that the link is established on

the Um interface. After receiving the UA frame, the MS sends an ASS CMP message to theBSC. The BSC receives this message and measures R4419B: Completed Assignments (TCH)

in the TRX where the TCH is located.

In the Mode Modify procedure, the BSC sends a CHAN MODE MODIFY message to the MSafter receiving a MODE MODIFY ACK message. Meanwhile, the BSC measures R4429A:

Attempted Mode Modify Procedures (TCH) in the TRX where the TCH is located.

In the Mode Modify procedure, the MS sends a FIRST SABM frame to the BTS afterreceiving a CHAN MODE MODIFY message. This frame indicates that the Um interface is in



12 Call Measurement




multiframe link setup state. The BTS returns a UA frame to the MS and sends the BSC anEST IND message, indicating that the link is established on the Um interface. After receivingthe UA frame, the MS sends a CHAN MODE MODIFY ACK message to the BSC. The BSC

receives this message and measures R4429B: Completed Mode Modify Procedures (TCH) inthe TRX where the TCH is located.

In the SDCCH handover procedure, the BSC sends an HO CMD message from the source cell

to the MS after receiving a CHAN ACTIV ACK message from the target cell. Meanwhile, theBSC measures R4430A: Attempted Handovers (SDCCH) in the TRX where the target

SDCCH is located.

In the TCH handover procedure, the BSC sends an HO CMD message from the source cell tothe MS after receiving a CHAN ACTIV ACK message from the target cell. Meanwhile, the

BSC measures R4439A: Attempted Handovers (TCH) in the TRX where the target TCH islocated.

In the SDCCH handover procedure, the MS sends an HO ACC message to the BTS where thetarget cell is located after receiving an HO CMD message. The BTS notifies the BSC of this

message through an HO DETECT message. If the source cell and the target cell belong todifferent BTSs, the BTS where the target cell is located sends a PHY INFO message to theMS. The MS returns a FIRST SABM frame and sends an EST IND message from the target

cell to the BSC. The MS also sends an HO CMP message to the BSC. After receiving thismessage, the BSC measures R4430B: Completed Handovers (SDCCH) in the TRX where the

target SDCCH is located.

In the TCH handover procedure, the MS sends an HO ACC message to the BTS where thetarget cell is located after receiving an HO CMD message. The BTS notifies the BSC of this

message through an HO DETECT message. If the source cell and the target cell belong todifferent BTSs, the BTS where the target cell is located sends a PHY INFO message to the

MS. The MS returns a FIRST SABM frame and sends an EST IND message from the targetcell to the BSC. The MS also sends an HO CMP message to the BSC. After receiving this

message, the BSC measures R4439B: Completed Handovers (TCH) in the TRX where thetarget TCH is located.

In the immediate assignment procedure, the BSC receives from the BTS a CHAN ACTIVACK message, indicating that the channel is successfully activated. The BSC sends an IMMASS CMD message, requesting the MS to access the specified channel. This channel can be

an SDCCH or a TCH. CR440A: Attempted Immediate Assignments is used to measure the

IMM ASS CMD messages received on all the channels of a TRX.

In the immediate assignment procedure, an MS reports a FIRST SABM frame to the BTS on

the TCH after seizing the assigned channel. Through this frame, the MS notifies the BTS that

the radio link layer has entered multiframe link setup state. The BTS returns a UA frame tothe MS and sends the BSC an EST IND message to notify the BSC that the link is established

on the Um interface. The channel can be an SDCCH or a TCH. CR440B: SuccessfulImmediate Assignment Procedures is used to measure the EST IND messages received on all

the channels of a TRX.

In a handover procedure, the BSC sends an HO CMD message from the source cell to the MS

after receiving a CHAN ACTIV ACK message from the target cell. The handover can be an

SDCCH handover or a TCH handover. CR443A: Attempted Handovers is used to measure theHandover CMD messages received on all the channels of a TRX.

In a handover procedure, the MS sends an HO ACC message to the BTS where the target cell

is located after receiving an HO CMD message. The BTS notifies the BSC of this messagethrough an HO DETECT message. If the source cell and the target cell belong to differentBTSs, the BTS where the target cell is located sends a PHY INFO message to the MS. The

MS returns a FIRST SABM frame and sends an EST IND message from the target cell to the






BSC. The MS also sends an HO CMP message to the BSC. CR443B: Completed Handoversis used to measure the Handover CMP received on all the channels of a TRX.

Trigger Point

For the trigger points of the counters, see the flow charts in Immediate Assignment

Measurement per Cell, Assignment Measurement per Cell, Intra-Cell Handover Measurement per Cell, Incoming Internal Inter-Cell Handover Measurement per Cell, Outgoing Internal

Inter-Cell Handover Measurement per Cell, Incoming External Inter-Cell HandoverMeasurement per Cell, Outgoing External Inter-Cell Handover Measurement per Cell,

Incoming Inter-RAT Inter-Cell Handover Measurement per Cell, and Outgoing Inter-RATInter-Cell Handover Measurement per Cell.

Formula

Attempted Immediate Assignments =

[Attempted Immediate Assignments (SDCCH)] +

[Attempted Immediate Assignments (TCH)]

Successful Immediate Assignment Procedures =

[Successful Immediate Assignments (SDCCH)] +

[Attempted Immediate Assignment Procedures (TCH)]

Attempted Handovers =

[Attempted Handovers (SDCCH)] +

[Attempted Handovers (TCH)]

Completed Handovers =

[Completed Handovers (SDCCH)] +

[Completed Handovers (TCH)]

12.8 Immediate Assignment Measurement per Cell12.8.1 Overview

When an MS requires network services for reasons such as Mobile Originated Call (MOC),Mobile Terminated Call (MTC), emergency call, call re-establishment, location updating,

packet call, and Location Measurement Unit (LMU)+Reserved, it sends the BTS a CHANREQ message on the RACH. After receiving this message, the BTS reports a CHAN RQD

message to the BSC.

After receiving the CHAN RQD message, the BSC assigns and activates a signaling channelto the MS. If the BSC receives a CHAN ACTIV ACK message from the BTS, the signaling

channel is ready for the assignment. The BSC sends an IMM ASS CMD message, requesting



12 Call Measurement




the MS to access the specified signaling channel. This signaling channel can be an SDCCH ora TCH.

After receiving a FIRST SABM frame from the MS, the BTS sends an EST IND message to

the BSC.

After receiving the EST IND message that carries an MM message (CM SERV REQ message,

LOC UPD REQ message, IMSI DTCH message, PAG RSP message, CM RE-EST REQ

message), the BSC requests the MSC to establish the A interface connection and transparentlytransmits the MM message to the MSC.

Figure 12-1 shows the immediate assignment procedure.

Figure 12-1 Immediate assignment procedure

BTS BSCMS

C

IMM ASS CMD

B

A

CHAN REQ

CHAN RQD

CHAN ACTIV

CHAN ACTIV ACK

EST IND

Table 12-13 lists the counter classification of Immediate Assignment Measurement per Cell.

Table 12-13 Counter classification of Immediate Assignment Measurement per Cell


Channel Requests per Cell 12.8.2

Immediate Assignment Commands per Cell 12.8.3

Call Setup Indications per Cell 12.8.4

Rejects to Service Requests per Cell 12.8.5

Immediate Assignment Analyzed Measurement per Cell 12.8.6

12.8.2 Channel Requests per Cell

Counter

Table 12-14 lists the counters of Channel Requests per Cell.






Table 12-14 Counters of Channel Requests per Cell

Number Counter

1 A300A: Channel Requests (MOC)

2 A300C: Channel Requests (MTC)

3 A300D: Channel Requests (Emergency Call)

4 A300E: Channel Requests (Call Re-establishment)

5 A300F: Channel Requests (Location Updating)

6 A300H: Channel Requests (Packet Call)

7 A300I: Channel Requests (LMU+Reserved)

Meaning

When an MS requires network services, it sends the BTS a CHAN REQ message on the

RACH. After receiving this message, the BTS reports a CHAN RQD message to the BSC for

a dedicated channel. The counters measure channel access due to different causes.

Trigger Point

As shown in Figure 12-1 (A), the measurement is triggered when the BSC receives a CHAN

RQD message from the BTS where the target cell is located. The measurement is based on theaccess cause.

Formula

None.

12.8.3 Immediate Assignment Commands per Cell

Counter

Table 12-15 lists the counters of Immediate Assignment Commands per Cell.

Table 12-15 Counters of Immediate Assignment Commands per Cell

Number Counter

1 A3010: Immediate Assignment Commands (SDCCH)

2 A3017: Immediate Assignment Commands (TCHF)

3 A3018: Immediate Assignment Commands (TCHH)

4 A301H: Immediate Assignment Commands (Packet Service)

5 A302J: Rejects to Immediate Assignments (Circuit Service)

6 A302H: Rejects to Immediate Assignments (Packet Service)



12 Call Measurement




Meaning

In the immediate assignment procedure, the BSC sends the MS an IMM ASS CMD message

after receiving a CHAN ACTIV ACK message from the BTS. Through this message, the BSC

notifies the MS to access the specified signaling channel. The signaling channel can be an

SDCCH, TCHF, or TCHH. The access cause is circuit services or packet services.

After receiving a CHAN RQD message from the BTS, the BSC sends the MS an IMM ASS

REJ message if there is no channel available, the channel activation fails, or the channelactivation timed out. The immediate assignment fails.

Trigger Point

Figure 12-2 shows the trigger points of the counters of Immediate Assignment Commands per

Cell.

Figure 12-2 trigger points of the counters of Immediate Assignment Commands per Cell

BTS BSCMS

C

IMM ASS REJ

B

A

CHAN REQ

CHAN RQD

CHAN ACTIV

CHAN ACTIV NACK

TIME OUT

IMM ASS REJ

IMM ASS REJ

As shown in Figure 12-1 (B), the measurement related to immediate assignment commands is

triggered when the BSC sends an IMM ASS CMD message to an MS in the target cell. Themeasurement is based on the channel type and the access cause.

As shown in Figure 12-2 (A), (B), and (C), the BSC sends an IMM ASS REJ message to anMS in the target cell. If the access cause is packet services, the BSC measures Rejects toImmediate Assignments (Packet Service). If the access cause is not packet services, the BSCmeasures Rejects to Immediate Assignments (Circuit Service).

The descriptions of trigger points A, B, and C are as follows:

Trigger point A means that the immediate assignment is rejected because there are noavailable channels.

Trigger point B means that the immediate assignment is rejected because the channelactivation fails.

Trigger point C means that the immediate assignment is rejected because the channel

activation timed out.






Formula

None.

12.8.4 Call Setup Indications per CellCounter

Table 12-16 lists the counters of Call Setup Indications.

Table 12-16 Counters of Call Setup Indications

Number Counter

1 A3030A: Call Setup Indications (MOC Non SMS) (SDCCH)

2 A3030B: Call Setup Indications (MOC SMS) (SDCCH)

3 A3030C: Call Setup Indications (MTC) (SDCCH)

4 A3030D: Call Setup Indications (Emergency Call) (SDCCH)

5 A3030E: Call Setup Indications (Call Re-establishment) (SDCCH)

6 A3030F: Call Setup Indications (Location Updating) (SDCCH)

7 A3030G: Call Setup Indications (IMSI Detach) (SDCCH)

8 A3030H: Call Setup Indications (Packet Service) (SDCCH)

9 A3030I: Call Setup Indications (SS) (SDCCH)

10 A3030J: Call Setup Indications (LCS) (SDCCH)

11 A3030K: Call Setup Indications (Others) (SDCCH)

12 A3037A: Call Setup Indications (MOC Non SMS) (TCHF)

13 A3037B: Call Setup Indications (MOC SMS) (TCHF)

14 A3037C: Call Setup Indications (MTC) (TCHF)

15 A3037D: Call Setup Indications (Emergency Call) (TCHF)

16 A3037E: Call Setup Indications (Call Re-establishment) (TCHF)

17 A3037G: Call Setup Indications (IMSI Detach) (TCHF)

18 A3037H: Call Setup Indications (Packet Service) (TCHF)

19 A3037I: Call Setup Indications (SS) (TCHF)

20 A3037J: Call Setup Indications (LCS) (TCHF)

21 A3037K: Call Setup Indications (Others) (TCHF)

22 A3038A: Call Setup Indications (MOC Non SMS) (TCHH)

23 A3038C: Call Setup Indications (MTC) (TCHH)

24 A3038E: Call Setup Indications (Call Re-establishment) (TCHH)



12 Call Measurement




Number Counter

25 A3038H: Call Setup Indications (Packet Service) (TCHH)

26 A3038I: Call Setup Indications (SS) (TCHH)

27 A3038J: Call Setup Indications (LCS) (TCHH)

28 A3038K: Call Setup Indications (Others) (TCHH)

29 A3040: Call Setup Indications Timed Out (SDCCH)

30 A3047: Call Setup Indications Timed Out (TCHF)

31 A3048: Call Setup Indications Timed Out (TCHH)

32 A3039J: SDCCH Seizures for Speech Service

Meaning

In the immediate assignment procedure, an MS reports a FIRST SABM frame to the BTS on

the seized signaling channel (SDCCH, TCHF, or TCHH). Through this frame, the MS notifies

the BTS that the radio link layer has entered the multiframe link setup state. The BTS returnsa UA frame to the MS and sends the BSC an EST IND message to notify the BSC that thelink is established on the Um interface.

After link setup on the air interface, counter A3039J: SDCCH Seizures for Speech Service ismeasured for speed service.

In the immediate assignment procedure, the BSC sends an IMM ASS CMD message to an MS

and triggers a timer. If no EST IND message is received within scheduled time (10 seconds bydefault), the BSC measures the counters related to the timeout of call setup indications.

Trigger Point

As shown in Figure 12-1 (C), the measurement related to call setup indications is triggered

when the BSC receives an EST IND message from the BTS where the target cell is located.This measurement is based on the channel type, the value of the service request message, and

the number of seized SDCCHs for speech service.

As shown in Figure 12-3 (A), the BSC sends an IMM ASS CMD message in the target cell.

The measurement related to the timeout of call setup indications is triggered if no EST IND

message is received within scheduled time. This measurement is based on the channel type.






Figure 12-3 Trigger points of the counters of Call Setup Indications

BTS BSCMS

A

IMM ASS CMD

CHAN REQ

CHAN RQD

CHAN ACTIV

CHAN ACTIV ACK

TIME OUT

Formula

None.

12.8.5 Rejects to Service Requests per Cell

Counter

Table 12-17 lists the counters of Rejects to Service Requests per Cell.

Table 12-17 Counter of Rejects to Service Requests per Cell

Number Counter

1 A3050: Rejects to Service Requests (Congestion)

2 A3051: Rejects to Service Requests (Network Failure)

3 A3052: Rejects to Service Requests (Illegal MS)

4 A3053: Rejects to Service Requests (Other Causes)

Meaning

In the immediate assignment procedure where an MS requests for connection setup, the MS

establishes an RR connection with the BSS first, and then sends a CM SERV REQ message

on the MM layer. The BSS transparently transmits this message to the NSS. If the NSS doesnot support or cannot respond to the service request due to congestion, network failure, illegal

MS or other causes, the MSC sends a CM SERV REJ message to the MS and the BSCtransparently transmits this message.



12 Call Measurement




Trigger Point

As shown in Figure 12-4 (A), the measurement is triggered when the BSC receives a CM

SERV REJ message that is sent from the MSC to an MS in the target cell. The measurement is

based on the reject cause.

Figure 12-4 Trigger points of the counters of Rejects to Service Requests per Cell

BTS BSCMS

A

IMM ASS CMD

CHAN REQ

CHAN RQD

CHAN ACTIV

CHAN ACTIV ACK

EST IND

CR

CC

CM SERV REJ

MSC

Formula

None.

12.8.6 Immediate Assignment Analyzed Measurement per Cell

Counter

Table 12-18 lists the counters of Immediate Assignment Analyzed Measurement per Cell.

Table 12-18 Counters of Immediate Assignment Analyzed Measurement per Cell

Number Counter

1 CA300J: Channel Requests (Circuit Service)

2 CA303J: Call Setup Indications (Circuit Service)

3 CA3030J: Call Setup Indications (SDCCH) (Circuit Service)

4 CA3039J: Call Setup Indications (TCH) (Circuit Service)

5 RA301G: Success Rate of Immediate Assignment

6 CA301J: Immediate Assignment Commands (Circuit Service)






Number Counter

7 CA303H: Call Setup Indications (Packet Service)

8 CA304: Call Setup Indications Timed Out

9 CA305: Rejects to Service Requests

10 RA303G: Success Rate of Call Setup (Immediate Assignment)

Meaning

None.

Trigger Point

None.

Formula

Channel Requests (Circuit Service) =

[Channel Requests (MOC)] +

[Channel Requests (MTC)] +

[Channel Requests (Emergency Call)] +

[Channel Requests (Call Re-establishment)] +

[Channel Requests (Location Updating)]

Call Setup Indications (Circuit Service) =

[Call Setup Indications (SDCCH) (Circuit Service)] +

[Call Setup Indications (TCH) (Circuit Service)]

Call Setup Indications (SDCCH) (Circuit Service) =

[Call Setup Indications (MOC Non SMS) (SDCCH)] +

[Call Setup Indications (MOC SMS) (SDCCH)] +

[Call Setup Indications (MTC) (SDCCH)] +

[Call Setup Indications (Emergency Call) (SDCCH)] +

[Call Setup Indications (Call Re-establishment) (SDCCH)] +

[Call Setup Indications (Location Updating) (SDCCH)] +

[Call Setup Indications (IMSI Detach) (SDCCH)]



12 Call Measurement




Call Setup Indications (TCH) (Circuit Service) =

[Call Setup Indications (MOC Non SMS) (TCHF)] +

[Call Setup Indications (MOC SMS) (TCHF)] +

[Call Setup Indications (MTC) (TCHF)] +

[Call Setup Indications (Emergency Call) (TCHF)] +

[Call Setup Indications (Call Re-establishment) (TCHF)] +

[Call Setup Indications (IMSI Detach) (TCHF)] +

[Call Setup Indications (MOC Non SMS) (TCHH)] +

[Call Setup Indications (MTC) (TCHH)] +

[Call Setup Indications (Call Re-establishment) (TCHH)]

Success Rate of Immediate Assignment =

[Immediate Assignment Commands (Circuit Service)]*{100}/[Channel Requests (Circuit

Service)]

Immediate Assignment Commands (Circuit Service) =

[Immediate Assignment Commands (SDCCH)] +

[Immediate Assignment Commands (TCHF)] +

[Immediate Assignment Commands (TCHH)]

Call Setup Indications (Packet Service) =

[Call Setup Indications (Packet Service) (SDCCH)] +

[Call Setup Indications (Packet Service) (TCHF)] +

[Call Setup Indications (Packet Service) (TCHH)]

Call Setup Indications Timed Out =

[Call Setup Indications Timed Out (SDCCH)] +

[Call Setup Indications Timed Out (TCHF)] +

[Call Setup Indications Timed Out (TCHH)]

Rejects to Service Requests =

[Rejects to Service Requests (Congestion)] +

[Rejects to Service Requests (Network Failure)] +

[Rejects to Service Requests (Illegal MS)] +






[Rejects to Service Requests (Other Causes)]

Success Rate of Call Setup (Immediate Assignment) =

[Call Setup Indications (Circuit Service)]*{100}/[Channel Requests (Circuit Service)]

12.9 Assignment Measurement per Cell

12.9.1 Overview

Table 12-19 lists the counter classification of Assignment Measurement per Cell.

Table 12-19 Counter classification of Assignment Measurement per Cell


Assignment Requests per Cell 12.9.2

Assignment Commands per Cell 12.9.3

Completed Assignments per Cell 12.9.4

Failed Assignments per Cell 12.9.5

Mode Modify Commands per Cell 12.9.6

Failed Mode Modify Attempts per Cell 12.9.7

Assignment Procedure Analyzed Measurement per Cell 12.9.8

12.9.2 Assignment Requests per Cell

Counter

Table 12-20 lists the counters of Assignment Requests per Cell.

Table 12-20 Counters of Assignment Requests per Cell

Number Counter

1 A3100A: Assignment Requests (Signaling Channel)

2 A3100B: Assignment Requests (TCHF Only)

3 A3100C: Assignment Requests (TCHH Only)

4 A3100D: Assignment Requests (TCHF Preferred, Channel Type

Unchangeable)

5 A3100E: Assignment Requests (TCHH Preferred, Channel TypeUnchangeable)



12 Call Measurement




Number Counter

6 A3100F: Assignment Requests (TCHF or TCHH, Channel Type

Unchangeable)

7 A3100G: Assignment Requests (TCHF Preferred, Channel Type Changeable)

8 A3100H: Assignment Requests (TCHH Preferred, Channel Type Changeable)

9 A3100I: Assignment Requests (TCHF or TCHH, Channel Type Changeable)

10 A3101A: Assignment Requests (MOC)

11 A3101C: Assignment Requests (MTC)

12 A3101D: Assignment Requests (Emergency Call)

13 A3101E: Assignment Requests (Call Re-establishment)

Meaning

The counters measure the ASS REQ messages received by the BSC from the MSC in the

assignment procedure. The message specifies the signaling type or service type. If the servicetype (speech or data) is different, the channel assigned by the MSC is also different.

When the channel assigned by the MSC is used for speech services, the assigned channel is of the

following types:

Full rate TCH channel Bm

Half rate TCH channel Lm

Full or Half rate TCH channel, Full rate preferred, changes between full rate and half rate allowedalso after first channel allocation as a result of the request

Full or half rate TCH channel, half rate preferred, changes between full rate and half rate allowedalso after first channel allocation as a result of the request

Full or half rate TCH channel, full rate preferred, changes between full rate and half rate not allowed

after first channel allocation as a result of the request

Full or half rate TCH channel, half rate preferred, changes between full rate and half rate not allowed


Full or half rate TCH channel, changes between full and half rate allowed also after first channel

allocation as a result of the request

Full or half rate TCH channel, changes between full and half rate not allowed after first channel

allocation as a result of the request

Huawei BSC supports all of the eight channel types.

When the channel assigned by the MSC is used for data services, the assigned channel is of the

following types:

Full rate TCH channel Bm

Half rate TCH channel Lm

Full or half rate TCH channel, full rate preferred, changes between full rate and half rate allowed

also after first channel allocation as a result of the request

Full or half rate TCH channel, half rate preferred, changes between full rate and half rate allowedalso after first channel allocation as a result of the request

Full or half rate TCH channel, full rate preferred, changes between full rate and half rate not allowed


Full or Half rate TCH channel. Half rate preferred, changes between full rate and half rate not






allowed after first channel allocation as a result of the request

Full rate TCH channels in a multislot configuration, changes by the BSS of the number of TCHs andif applicable the used radio interface rate per channel allowed after first channel allocation as a result

of the request

Full rate TCH channels in a multislot configuration, changes by the BSS of the number of TCHs or

the used radio interface rate per channel not allowed after first channel allocation as a result of therequest

Huawei BSC supports the first six channel types.

Trigger Point

In the immediate assignment procedure, the BSS assigns a signaling channel to an MS. After

the RR connection between the MS and the BSS is established, the MS establishes the MMand the CC connections with the MSC through the signaling channel. Based on the CC

connection request from the MS, the MSC assigns terrestrial resources to the MS and

specifies available channel types in an ASS REQ message.

The measurement is triggered when the BSC receives an ASS REQ message from the MSC,as shown in Figure 12-5 (A). The measurement is based on the channel type and the access

cause carried in the message.

Figure 12-5 Trigger point of the counters of Assignment Requests per Cell

BTS BSCMS

A

IMM ASS CMD

CHAN REQ

CHAN RQD

CHAN ACTIV

CHAN ACTIV ACK

EST IND

CR(CMP L3 INFO)

CC

CM SERV ACP

MSC

SETUP

CALL PROCEEDING

ASS REQ

SABM

UA

Formula

None.



12 Call Measurement




12.9.3 Assignment Commands per Cell

Counter

Table 12-21 lists the counters of Assignment Commands per Cell.

Table 12-21 Counters of Assignment Commands per Cell

Number Counter

1 A3117A: Assignment Commands (MOC) (TCHF) (Excluding Directed Retry)

2 A3117C: Assignment Commands (MTC) (TCHF) (Excluding Directed Retry)

3 A3117D: Assignment Commands (Emergency Call) (TCHF) (ExcludingDirected Retry)

4 A3117E: Assignment Commands (Call Re-establishment) (TCHF) (ExcludingDirected Retry)

5 A3118A: Assignment Commands (MOC) (TCHH) (Excluding Directed Retry)

6 A3118C: Assignment Commands (MTC) (TCHH) (Excluding Directed Retry)

7 A3118D: Assignment Commands (Emergency Call) (TCHH) (ExcludingDirected Retry)

8 A3118E: Assignment Commands (Call Re-establishment) (TCHH) (ExcludingDirected Retry)

Meaning

This counter measures the number of times the BSC sends an ASS CMD message to an MS.

Trigger Point

In the assignment procedure, the BSC assigns a TCH to an MS (In the signaling traffic

assignment, the BSC returns an assignment complete message to the MSC and assigns nosignaling channel). After the channel is activated, the BSC sends an ASS CMD message to the

MSC.

As shown in Figure 12-6 (B), the measurement is triggered when the BSC sends an ASSCMD message to the MSC. The measurement is based on channel types and call accesscauses.






Figure 12-6 Trigger Point of the counters of Assignment Commands per Cell

BTS BSCMS MSC

B

CHAN ACTIV

CHAN ACTIV ACK

ASS REQ

ASS CMD

Formula

None.

12.9.4 Completed Assignments per Cell

Counter

Table 12-22 lists the counters of Completed Assignments per Cell.

Table 12-22 Counters of Completed Assignments per Cell

Number Counter

1 A3167A: Speech Version 1 Completed Assignments (Excluding DirectedRetry) (TCHF)

2 A3167B: Speech Version 2 Completed Assignments (Excluding DirectedRetry) (TCHF)

3 A3167C: Speech Version 3 Completed Assignments (Excluding Directed

Retry) (TCHF)

4 A3168A: Speech Version 1 Completed Assignments (Excluding Directed

Retry) (TCHH)

5 A3168B: Speech Version 2 Completed Assignments (Excluding DirectedRetry) (TCHH)

6 A3168C: Speech Version 3 Completed Assignments (Excluding DirectedRetry) (TCHH)

Meaning

The counters measure the following:



12 Call Measurement




Number of times the MS sends an ASS CMP message to the BSC in the assignment procedure

Number of times the calls use a certain speech version when the MS sends an ASS CMPmessage to the BSC in the assignment procedure

Number of times the MS sends an HO CMP message to the BSC in the directed retry procedure

Trigger Point

The assignment procedure is initiated after the BSC receives an ASS REQ message from the

MSC. The BSC sends an ASS CMD message to the MS. If a full rate TCH or half rate TCH is

successfully assigned to the MS during the first assignment, the MS reports an ASS CMPmessage to the BSC. The BSC receives this message and forwards it to the MSC.

As shown in Figure 12-7 (C), the measurement of completed assignments (first assignment of

a TCHF or a TCHH) is triggered when the BSC receives an ASS CMP message.

Figure 12-7 Trigger points of the counters of Completed Assignments per Cell

BTS BSCMS

ASS CMD

ASS REQ

CHAN ACTIV

CHAN ACTIV ACK

EST IND

MSC

ASS CMP

SABM

UA

ASS CMP

When the BSC receives an ASS REQ message from the MSC, it initiates an assignment

procedure. If the first assignment fails, the MS sends an ASS FAIL message to the BSC andthe BSC initiates the re-assignment procedure. If a full rate TCH or half rate TCH is

successfully assigned to the MS, the MS sends an ASS CMP message to the BSC. Themeasurement of completed assignments (re-assignment of a TCHF or a TCHH) is triggered

when the BSC receives the ASS CMP message. The BSC sends the ASS CMP message to theMSC at the same time.

Formula

None.






12.9.5 Failed Assignments per Cell

Counter

Table 12-23 lists the counters of Failed Assignments per Cell.

Table 12-23 Counters of Failed Assignments per Cell

Number Counter

1 A3127A: Failed Assignments (MOC) (TCHF) (Excluding Directed Retry)

2 A3127C: Failed Assignments (MTC) (TCHF) (Excluding Directed Retry)

3 A3127D: Failed Assignments (Emergency Call) (TCHF) (ExcludingDirected Retry)

4 A3127E: Failed Assignments (Call Re-establishment) (TCHF) (ExcludingDirected Retry)

5 A3128A: Failed Assignments (MOC) (TCHH) (Excluding Directed Retry)

6 A3128C: Failed Assignments (MTC) (TCHH) (Excluding Directed Retry)

7 A3128D: Failed Assignments (Emergency Call) (TCHH) (ExcludingDirected Retry)

8 A3128E: Failed Assignments (Call Re-establishment) (TCHH) (ExcludingDirected Retry)

9 A312Aa: Failed Assignments (MOC) (Including Directed Retry)

10 A312Ca: Failed Assignments (MTC) (Including Directed Retry)

11 A312Da: Failed Assignments (Emergency Call) (Including Directed Retry)

12 A312Ea: Failed Assignments (Call Re-establishment) (Including DirectedRetry)

13 A312A: Failed Assignments (Signaling Channel)

14 A3129I: Failed Assignments (Invalid State)

15 A3129J: Failed Assignments (Invalid Message)

16 A3129E: Failed Assignments (CIC Unavailable)

17 A3129F: Failed Assignments (CIC Allocated)

18 A3129G: Failed Assignments (A-Interface Failure)

19 A3129H: Failed Assignments (Clear Commands Sent by MSC)

20 A312A: Failed Assignments (First Assignment, Channel Unavailable inAssignment Procedure)

21 A3129C: Failed Assignments (First Assignment, Assignment Timed Out)

22 A312K: Failed Assignments (First Assignment, Channel Unavailable in

Directed Retry Procedure)



12 Call Measurement




Number Counter

23 A3129O: Failed Assignments (First Assignment, Directed Retry Timed Out)

24 A3129B: Failed Assignments (First Assignment, Terrestrial Resource

Request Failed)

25 A312L: Failed Assignments (Reconnection to Old Channels, ChannelUnavailable in Assignment)

26 A3129D: Failed Assignments (Reconnection to Old Channels, Reconnectionto Old Channel in Assignment)

27 A3129P: Failed Assignments (Reconnection to Old Channels, Timer Expiredin Assignment)

28 A312M: Failed Assignments (Reconnection to Old Channels, ChannelUnavailable in Directed Retry)

29 A3129R: Failed Assignments (Reconnection to Old Channels, Reconnectionto Old Channel in Directed Retry)

30 A3129Q: Failed Assignments (Reconnection to Old Channels, Timer Expiredin Directed Retry)

31 A3129N: Failed Assignments (Reconnection to Old Channels, TerrestrialResource Request Failed)

Meaning

The counters measure the number of failed assignments due to different causes.

In the assignment procedure, the MSC sends an ASS REQ message to the BSS. The BSS

selects a traffic channel or signaling channel. The assignment may fail due to various causes.

An assignment may fail due to any of the following causes:

The BSS detects that there are no traffic channels or signaling channels available and sends an ASSFAIL message to the MSC.

The MS sends an ASS FAIL message to the BSS directly.

No ASS CMP message is received within scheduled time after the BSS receives an ASS REQ

message from the MSC.

The BSS determines that the message is in invalid state.

The BSS receives an invalid message.

The request for terrestrial resources fails.

The CIC is unavailable or is already allocated.

A failure occurs on the A interface.

The MSC sends a clear command.

Trigger Point

If the MSC receives no ASS CMP message after sending an ASS REQ message to the BSS,

the measurement of Failed Assignments per Cell is triggered. The BSS sends an ASS FAIL






message to the MSC. The measurement is based on the failure cause, procedure, and assignedchannel type.

In the assignment procedure (including or excluding directed retry), the related

measurement is triggered when the assignment procedure fails. The measurement is

based on the access cause and the assigned channel type. In the assignment procedure, the measurement of Failed Assignments (Invalid State) is

triggered when the BSC detects that the status of the received message does not matchthe current procedure.

In the assignment procedure, the related measurement is triggered when the BSC detects

that errors occur in the decoding of the received ASS REQ message. The errors may beof the channel type, CIC, and layer 3 header information.

After the BSC receives an ASS REQ message from the MSC, the measurement of Failed

Assignments (First Assignment, Terrestrial Resource Request Failed) is triggered whenthe BSC fails to request the terrestrial resources specified in the message.

In the assignment procedure, the related measurement is triggered when the BSC detects

that the CIC carried in the received ASS REQ message is unavailable or is alreadyallocated.

In the assignment procedure after the A interface link is established, the MSC sends anASS REQ message to the BSC. The measurement of Failed Assignments (A-Interface

Failure) is triggered when the MSC sends a CLEAR CMD message or a DISCONNECTmessage to the BSC because errors occur on the A interface.

In the assignment procedure, the MSC sends an ASS REQ message to the BSC. Themeasurement of Failed Assignments (Clear Commands Sent by MSC) is triggered when

the MSC sends a CLEAR CMD message before the BSC responds to the ASS REQmessage.

In the first assignment, directed retry, re-assignment, or re-assignment directed retry

procedure, the related measurement is triggered when the BSC detects that there are noavailable channel resources.

In the first assignment or the directed retry procedure, the BSC sends an ASS CMDmessage, and then triggers an assignment timer. The related measurement is triggeredwhen the timer expires.

In the assignment procedure, the BSC receives an ASS REQ message from the MSC. Ifthe first assignment fails, the MS reconnects to the old channel and sends an ASS FAIL

message to the BSC. The BSC then initiates the two procedures described previously andthe measurement is triggered when the assignment fails.

Formula

None.

12.9.6 Mode Modify Commands per Cell

Counter

Table 12-24 lists the counters of Mode Modify Commands per Cell.



12 Call Measurement




Table 12-24 Counters of Mode Modify Commands per Cell

Number Counter

1 A3147A: Mode Modify Commands (MOC) (TCHF)

2 A3147C: Mode Modify Commands (MTC) (TCHF)

3 A3147D: Mode Modify Commands (Emergency Call) (TCHF)

4 A3147E: Mode Modify Commands (Call Re-establishment) (TCHF)

5 A3148A: Mode Modify Commands (MOC) (TCHH)

6 A3148C: Mode Modify Commands (MTC) (TCHH)

7 A3148E: Mode Modify Commands (Call Re-establishment) (TCHH)

Meaning

In the immediate assignment procedure, if there are no idle SDCCHs but idle TCHs to be

assigned and if the immediate assignment of TCHs is allowed, the assigned full rate or half

rate TCH is used as a signaling channel. There is no need to assign a TCH during theassignment. The assigned full rate or half rate TCH is converted to a speech channel through aMode Modify procedure.

The counters measure the number of times the BSC sends a CHAN MODE MODIFYmessage to the MS after receiving the MODE MODIFY ACK message from the BTS.

Together with Completed Mode Modify Procedures (TCH), the counters can be used to

calculate the success rate of Mode Modify procedures.

Trigger Point

As shown in Figure 12-8 (E1), after receiving the ASS REQ message from the MSC, the BSC

checks the CHANNEL TYPE carried in the message and initiates the Mode Modify procedureif the CHANNEL TYPE and the type of the channel assigned in the assignment procedure

meet either of the following conditions:

Same type of channel rate, different speech data indications

Same type of channel rate and speech data indication, different speech coding algorithmsor data transparent transmission indications

If the Mode Modify procedure is performed in the assignment procedure, the BSC sends a

MODE MODIFY message to the BTS. After receiving a MODE MODIFY ACK messagefrom the BTS, the BSC sends a CHAN MODE MODIFY message to the MS.

The measurement is triggered when the BSC sends a CHAN MODE MODIFY message to the

MS.






Figure 12-8 Trigger points of the counters of Mode Modify Commands per Cell

BTS BSCMS

E2

ASS REQ

MODE MODIFY

MSC

ASS CMP

E1

MODE MODIFY ACK

CHANMODE MODIFY

CHANMODE MODIFY ACK

Formula

None.

12.9.7 Failed Mode Modify Attempts per Cell

Counter

Table 12-25 lists the counters of Failed Mode Modify Attempts per Cell.

Table 12-25 Counters of Failed Mode Modify Attempts per Cell

Number Counter

1 A3157A: Failed Mode Modify Attempts (MOC) (TCHF)

2 A3157C: Failed Mode Modify Attempts (MTC) (TCHF)

3 A3157D: Failed Mode Modify Attempts (Emergency Call) (TCHF)

4 A3157E: Failed Mode Modify Attempts (Call Re-establishment) (TCHF)

5 A3158A: Failed Mode Modify Attempts (MOC) (TCHH)

6 A3158C: Failed Mode Modify Attempts (MTC) (TCHH)

7 A3158E: Failed Mode Modify Attempts (Call Re-establishment) (TCHH)

8 A3159E: Failed Mode Modify Attempts (CIC Unavailable)

9 A3159F: Failed Mode Modify Attempts (CIC Allocated)

10 A3159B: Failed Mode Modify Attempts (Terrestrial Resource Request Failed)



12 Call Measurement




Number Counter

11 A3159G: Failed Mode Modify Attempts (A-Interface Failure)

12 A3159H: Failed Mode Modify Attempts (Clear Commands Sent by MSC)

13 A3159C: Failed Mode Modify Attempts (Timer Expired)

Meaning

The counters measure the number of times the assignment fails after the BSC sends a MODE

MODIFY message to the MS.

Trigger Point

If the Mode Modify procedure is performed in the assignment procedure but the TCHassignment fails due to various causes, the measurement of Failed Mode Modify Attempts per

Cell is triggered.

As shown in Figure 12-9 (F), after the BSC receives an ASS REQ message from theMSC, the measurement of Failed Mode Modify Attempts (Terrestrial Resource RequestFailed) is triggered when the request for terrestrial resources fails.

As shown in Figure 12-9 (G), after the BSC receives an ASS REQ message from theMSC in the Mode Modify procedure, the related measurement is triggered when the BSCdetects that the CIC is unavailable or is already allocated.

After the A interface link is established, the MSC sends an ASS REQ message to the

BSC. In the Mode Modify procedure, the measurement of Failed Mode Modify Attempts

(A-Interface Failure) is triggered when the MSC sends a CLEAR CMD message or aDISCONNECT message to the BSC because errors occur on the A interface.

In the Mode Modify procedure, the MSC sends an ASS REQ message to the BSC. The

measurement of Failed Mode Modify Attempts (Clear Commands Sent by MSC) istriggered when the MSC sends a CLEAR CMD message before the BSC responds to theASS REQ message.

As shown in Figure 12-9 (H), the BSC sends a CHAN MODE MODIFY message in theMode Modify procedure, and then triggers an assignment timer. The related

measurement is triggered when the BSC receives a CHAN MODE MODIFY NACKmessage or when the timer expires.






Figure 12-9 Trigger points of the counters of Failed Mode Modify Attempts per Cell

BTS BSCMS

H

ASS REQ

MODE MODIFY

MSC

ASS FAIL

G

MODE MODIFY ACK

CHAN MODE MODIFY

CHAN MODE MODIFY NACK

F

(MODE MODIFY NACK)

Formula

None.

12.9.8 Assignment Procedure Analyzed Measurement per Cell

CounterTable 12-26 lists the counters of Assignment Procedure Analyzed Measurement per Cell.

Table 12-26 Counters of Assignment Procedure Analyzed Measurement per Cell

Number Counter

1 CA310: Assignment Requests

2 CA313: Successful Assignments

3 RCA313: Success Rate of TCH Assignment

4 CA311: Assignment Commands

5 CA314: Mode Modify Commands

6 CA316: Completed Assignments (Um Interface)

7 CA312: Failed Assignments (Channel Unavailable)

Meaning

None.



12 Call Measurement




Trigger Point

None.

FormulaAssignment Requests =

[Assignment Requests (Signaling Channel)] +

[Assignment Requests (TCHF Only)] +

[Assignment Requests (TCHH Only)] +

[Assignment Requests (TCHF Preferred, Channel Type Unchangeable)] +

[Assignment Requests (TCHH Preferred, Channel Type Unchangeable)] +

[Assignment Requests (TCHF or TCHH, Channel Type Unchangeable)] +

[Assignment Requests (TCHF Preferred, Channel Type Changeable)] +

[Assignment Requests (TCHH Preferred, Channel Type Changeable)] +

[Assignment Requests (TCHF or TCHH, Channel Type Changeable)]

Successful Assignments =

[Assignment Requests]-

([Failed Assignments (Signaling Channel)] +

[Failed Assignments (MOC) (Including Directed Retry)] +

[Failed Assignments (MTC) (Including Directed Retry)] +

[Failed Assignments (Emergency Call) (Including Directed Retry)] +

[Failed Assignments (Call Re-establishment) (Including Directed Retry)] +

[Failed Mode Modify Attempts (MOC) (TCHF)] +

[Failed Mode Modify Attempts (MTC) (TCHF)] +

[Failed Mode Modify Attempts (Emergency Call) (TCHF)] +

[Failed Mode Modify Attempts (Call Re-establishment) (TCHF)] +

[Failed Mode Modify Attempts (MOC) (TCHH)] +

[Failed Mode Modify Attempts (MTC) (TCHH)] +

[Failed Mode Modify Attempts (Call Re-establishment) (TCHH)])

Success Rate of TCH Assignment =

[Successful Assignments]*{100}/[Assignment Requests]

Assignment Commands =






[Assignment Commands (MOC) (TCHF) (Excluding Directed Retry)] +

[Assignment Commands (MTC) (TCHF) (Excluding Directed Retry)] +

[Assignment Commands (Emergency Call) (TCHF) (Excluding Directed Retry)] +

[Assignment Commands (Call Re-establishment) (TCHF) (Excluding Directed Retry)] +

[Assignment Commands (MOC) (TCHH) (Excluding Directed Retry)] +

[Assignment Commands (MTC) (TCHH) (Excluding Directed Retry)] +

[Assignment Commands (Emergency Call) (TCHH) (Excluding Directed Retry)] +

[Assignment Commands (Call Re-establishment) (TCHH) (Excluding Directed Retry)]

Mode Modify Commands =

[Mode Modify Commands (MOC) (TCHF)] +[Mode Modify Commands (MTC) (TCHF)] +

[Mode Modify Commands (Emergency Call) (TCHF)] +

[Mode Modify Commands (Call Re-establishment) (TCHF)] +

[Mode Modify Commands (MOC) (TCHH)] +

[Mode Modify Commands (MTC) (TCHH)] +

[Mode Modify Commands (Emergency Call) (TCHH)] +

[Mode Modify Commands (Call Re-establishment) (TCHH)]

Completed Assignments (Um Interface) =

[Speech Version 1 Completed Assignments (Excluding Directed Retry) (TCHF)] +



[Speech Version 1 Completed Assignments (Excluding Directed Retry) (TCHH)] +

[Speech Version 2 Completed Assignments (Excluding Directed Retry) (TCHH)] +

[Speech Version 3 Completed Assignments (Excluding Directed Retry) (TCHH)]

Failed Assignments (Channel Unavailable) =

[Failed Assignments (First Assignment, Channel Unavailable in Assignment Procedure)] +

[Failed Assignments (First Assignment, Channel Unavailable in Directed Retry Procedure)] +

[Failed Assignments (Reconnection to Old Channels, Channel Unavailable in Assignment)] +

[Failed Assignments (Reconnection to Old Channels, Channel Unavailable in Directed Retry)]



12 Call Measurement




12.10 Intra-Cell Handover Measurement per Cell

12.10.1 Overview

After seizing a dedicated channel, an MS sends the BSC measurement reports periodically.After receiving the measurement reports, the BSC uses the handover algorithm to decidewhether a handover is required or not based on the measurement reports. If a handover is

required and the source cell (current cell) is also the target cell, an intra-cell handover isinitiated.

The Intra-cell handover procedure is as follows:

Step 1 The BSC sends a CHAN ACTIV message to the BTS where the target cell is located. Thismessage is used to activate the specified channel in the target cell.

Step 2 After receiving a CHAN ACTIV ACK message, the BSC requests for channel resources. If

the request succeeds, the BSC sends the MS an HO CMD message, requesting the MS to

initiate a handover from the source cell to the target cell.

Step 3 The MS sends the target BTS a HO ACC message to attempt to access a new cell.

Step 4 The target BTS forwards this message through an HO DETECT message to the BSC and

sends a PHY INFO message to the MS.

Step 5 The MS sends a FIRST SABM frame to the target BTS and the target BTS sends an EST INDmessage to the BSC, indicating that the MS has successfully accessed the target cell. The MSalso sends an HO CMP message to the BSC.

Step 6 The BSC sends an HO PERFORMED message to the MSC.

----End






Figure 12-10 Intra-cell handover procedure

BTS1(CELLO) BSCMS

PHY INFO

HO DETECT

MS MSCBTS1(CELLO)

A

B

CHAN ACTIV

HO ACC

FIRST SABM

EST IND

CHAN ACTIV

ACKHO CMD

MR FROM MS

HO CMP

HO PERFORMED

A: Intra-cell handover request

B: Intra-cell handover command

Table 12-27 lists the counter classification of Intra-Cell Handover Requests per Cell.

Table 12-27 Counter classification of Intra-Cell Handover Requests per Cell


Intra-Cell Handover Requests per Cell 12.10.2

Intra-Cell Handover Commands per Cell 12.10.3

Failed Intra-Cell Handovers per Cell 12.10.4

Intra-Cell AMR Handover per Cell 12.10.5

Intra-Cell Handover Detection Messages Received by BSC per Cell 12.10.6

Intra-Cell Handover Measurement per Cell 12.10.7

12.10.2 Intra-Cell Handover Requests per Cell

Counter

Table 12-28 lists the counters of Internal Intra-Cell Handover Requests per Cell.



12 Call Measurement




Table 12-28 Counters of Internal Intra-Cell Handover Requests per Cell

Number Counter

1 H3000: Internal Intra-Cell Handover Requests (SDCCH)

2 H3009: Internal Intra-Cell Handover Requests (TCH)

3 H3003A: Internal Intra-Cell Handover Requests (Dynamic Conversion, TCHF-TCHH)

4 H3003B: Internal Intra-Cell Handover Requests (Dynamic Conversion, TCHH-

TCHF)

5 H3004A: Internal Intra-Cell Handover Requests (Dynamic Conversion, TCH-

SDCCH)

6 H3004B: Internal Intra-Cell Handover Requests (Dynamic Conversion,

SDCCH-TCH)

7 H3002: Internal Intra-Cell Handover Requests (Underlay to Overlay)

8 H3001: Internal Intra-Cell Handover Requests (Overlay to Underlay)

9 CH3036A: Internal Intra-Cell Handover Requests due to Uplink Interference

10 CH3036B: Internal Intra-Cell Handover Requests due to Downlink Interference

Meaning

The counters measure the number of intra-cell handover requests based on handover types andchannel types.

The counters show the frequency of intra-cell handovers in the current cell. Along with Intra-

Cell Handover Commands per Cell and Failed Intra-Cell Handovers per Cell, the counters

show the performance of intra-cell handovers.


Intra-cell handover in normal conditions

Intra-cell handover caused by dynamic channel conversion

Intra-cell handover in concentric cells


SDCCH

TCH

The dynamic channel conversion is of the following types:

TCHF to TCHH (TCHF-TCHH)

TCHH to TCHF (TCHH-TCHF)

TCH to SDCCH (TCH-SDCCH)

SDCCH to TCH (SDCCH-TCH)







Underlaid subcell to overlaid subcell (Underlay to Overlay)

Overlaid subcell to underlaid subcell (Overlay to Underlay)

For intra-cell handovers caused by uplink and downlink intereference, counters CH3036A:

Internal Intra-Cell Handover Requests due to Uplink Interference and CH3036B: Internal

Intra-Cell Handover Requests due to Downlink Interferenc are measured respectively.

In the internal handover procedure, the BSC selects the idle neighbor cell (the neighbor cell in the same

BSC but different BM is assumed to be idle) as the preferred target cell. If all the neighbor cells of thesource cell are busy, the first cell on the list of candidate neighbor cells is selected. The handover is

performed even if this cell is busy. If the selected neighbor cell is also the source cell, the related counteris measured.

In the concentric cell handover (also a kind of intra-cell handover), no handover is performed if thetarget underlaid subcell or overlaid subcell is congested. No counters will be measured.

Trigger Point

As shown in Figure 12-10 (A), the measurement is triggered when the BSC decides that anintra-cell handover is required based on measurement reports. The measurement is based on

the handover type and the channel type.

Formula

None.

12.10.3 Intra-Cell Handover Commands per Cell

Counter

Table 12-29 lists the counters of Intra-Cell Handover Commands per Cell.

Table 12-29 Counters of Intra-Cell Handover Commands per Cell

Number Counter

1 H3010: Internal Intra-Cell Handover Commands (SDCCH)

2 H3017: Internal Intra-Cell Handover Commands (TCHF)

3 H3018: Internal Intra-Cell Handover Commands (TCHH)

4 H3013A: Internal Intra-Cell Handover Commands (Dynamic Conversion,

TCHF-TCHH)

5 H3013B: Internal Intra-Cell Handover Commands (Dynamic Conversion,

TCHH-TCHF)

6 H3014A: Internal Intra-Cell Handover Commands (Dynamic Conversion,TCH-SDCCH)

7 H3014B: Internal Intra-Cell Handover Commands (Dynamic Conversion,

SDCCH-TCH)

8 H3012: Internal Intra-Cell Handover Commands (Underlay to Overlay)

9 H3011: Internal Intra-Cell Handover Commands (Overlay to Underlay)



12 Call Measurement




Meaning

The counters measure the number of intra-cell handover commands based on handover types

and channel types.

Along with Intra-Cell Handover Requests per Cell and Failed Intra-Cell Handovers per Cell,the counters show the performance of intra-cell handovers.






SDCCH

TCHF

TCHH









Trigger Point

As shown in Figure 12-10 (B), the measurement is triggered when the BSC sends an HO

CMD message through the source cell to the MS. The measurement is based on the handovertype and the channel type.

Formula

None.

12.10.4 Failed Intra-Cell Handovers per Cell

Counter

Table 12-30 lists the counters of Failed Intra-Cell Handovers per Cell.

Table 12-30 Counters of Failed Intra-Cell Handovers per Cell

Number Counter

1 H3020: Failed Internal Intra-Cell Handovers (SDCCH)

2 H3029: Failed Internal Intra-Cell Handovers (TCH)






Number Counter

3 H3020A: Failed Internal Intra-Cell Handovers (Channel Unavailable)

(SDCCH)

4 H3029A: Failed Internal Intra-Cell Handovers (Channel Unavailable) (TCH)

5 H302B: Failed Internal Intra-Cell Handovers (Terrestrial Resource RequestFailed)

6 H302G: Failed Internal Intra-Cell Handovers (A-Interface Failure)

7 H3020C: Failed Internal Intra-Cell Handovers (Timer Expired) (SDCCH)

8 H3027Cb: Failed Internal Intra-Cell Handovers (Timer Expired) (TCHF)

(Signaling Channel)

9 H3028Cb: Failed Internal Intra-Cell Handovers (Timer Expired) (TCHH)

(Signaling Channel)

10 H3027Ca: Failed Internal Intra-Cell Handovers (Timer Expired) (TCHF)(Traffic Channel)

11 H3028Ca: Failed Internal Intra-Cell Handovers (Timer Expired) (TCHH)(Traffic Channel)

12 H302Da: Failed Internal Intra-Cell Handovers (Reconnection to Old Channels)

(Abnormal Release, Unspecified)

13 H302Db: Failed Internal Intra-Cell Handovers (Reconnection to Old Channels)(Abnormal Release, Channel Unacceptable)

14 H302Dc: Failed Internal Intra-Cell Handovers (Reconnection to Old Channels)(Abnormal Release, Timer Expired)

15 H302Dd: Failed Internal Intra-Cell Handovers (Reconnection to Old Channels)(Abnormal Release, No Activity on the Radio Path)

16 H302De: Failed Internal Intra-Cell Handovers (Reconnection to Old Channels)

(Preemptive Release)

17 H302Df: Failed Internal Intra-Cell Handovers (Reconnection to Old Channels)(Handover Failed, Timing Advance out of Range)

18 H302Dg: Failed Internal Intra-Cell Handovers (Reconnection to Old Channels)(Channel Mode Unavailable)

19 H302Dh: Failed Internal Intra-Cell Handovers (Reconnection to Old Channels)(Frequency Unavailable)

20 H302Di: Failed Internal Intra-Cell Handovers (Reconnection to Old Channels)(Call Already Cleared)

21 H302Dj: Failed Internal Intra-Cell Handovers (Reconnection to Old Channels)(Semantically Incorrect Message)

22 H302Dk: Failed Internal Intra-Cell Handovers (Reconnection to Old Channels)(Invalid Mandatory Information)



12 Call Measurement




Number Counter

23 H302Dl: Failed Internal Intra-Cell Handovers (Reconnection to Old Channels)

(Message Type Non-existent or Not Implemented)

24 H302Dm: Failed Internal Intra-Cell Handovers (Reconnection to OldChannels) (Message Type Not Compatible with Protocol State)

25 H302Dn: Failed Internal Intra-Cell Handovers (Reconnection to Old Channels)(Conditional IE Error)

26 H302Do: Failed Internal Intra-Cell Handovers (Reconnection to Old Channels)

(No Cell Allocation Available)

27 H302Dp: Failed Internal Intra-Cell Handovers (Reconnection to Old Channels)(Protocol Error Unspecified)

28 H302Dq: Failed Internal Intra-Cell Handovers (Reconnection to Old Channels)

(Other Causes)

29 H3022A: Failed Internal Intra-Cell Handovers (Channel Unavailable)(Underlay to Overlay)

30 H3021A: Failed Internal Intra-Cell Handovers (Channel Unavailable) (Overlay

to Underlay)

31 H3022M: Failed Internal Intra-Cell Handovers (Other Causes) (Underlay toOverlay)

32 H3021M: Failed Internal Intra-Cell Handovers (Other Causes) (Overlay toUnderlay)

33 H3023A: Failed Internal Intra-Cell Handovers (Dynamic Conversion, TCHF-TCHH)

34 H3023B: Failed Internal Intra-Cell Handovers (Dynamic Conversion, TCHH-TCHF)

35 H3024A: Failed Internal Intra-Cell Handovers (Dynamic Conversion, TCH-SDCCH)

36 H3024B: Failed Internal Intra-Cell Handovers (Dynamic Conversion, SDCCH-TCH)

Meaning

The counters measure the number of failed intra-cell handovers based on handover types,channel types, and failure causes.

Along with Intra-Cell Handover Requests per Cell and Intra-Cell Handover Commands perCell, the counters show the performance of intra-cell handovers.











SDCCH

TCHF

TCHHThe failure causes of intra-cell handovers include the following:

Channel unavailable


A-interface failure


Timer expired










Trigger Point

Figure 12-11 shows the trigger points of the counters of Failed Intra-Cell Handovers per Cell.



12 Call Measurement




Figure 12-11 Trigger points of the counters of Failed Intra-Cell Handovers per Cell

BTS1(CELLO) BSCMS MS MSCBTS1(CELLO)

F

PHY INFO

HO DETECT

A

B

G

CHAN ACTIV

HO ACC

FIRST SABM

EST IND

CHAN

ACTIV ACK

HO CMD

MR FROM MS

TIME OUT

HO FAIL

HO CMP

HO PERFORMED

In the

intra-cell

handover

procedure

C

D

H

E

A: Failed Intra-Cell Handovers (Channel Unavailable)

B: Failed Intra-Cell Handovers (Terrestrial Resource Request Failed)

C: Failed Intra-Cell Handovers (A-Interface Failure)D: Failed Intra-Cell Handovers (Clear Commands Sent by MSC)

E: Failed Intra-Cell Handovers

F: Failed Intra-Cell Handovers (Timer Expired)

G: Failed Intra-Cell Handovers (Reconnection to Old Channels)

H: Failed Intra-Cell Handovers (Other Causes)

The trigger points of the counters are as follows:

Failed Intra-Cell Handovers

As shown in Figure 12-11, the measurement is triggered when the intra-cell handover

fails before the handover completion timer expires. The measurement is based on thechannel type.


− SDCCH

− TCH


− TCHF to TCHH (TCHF-TCHH)

− TCHH to TCHF (TCHH-TCHF)

− TCH to SDCCH (TCH-SDCCH)

− SDCCH to TCH (SDCCH-TCH)

Failed Intra-Cell Handovers (Channel Unavailable)






As shown in Figure 12-11, the measurement is triggered when a channel request fails because the target cell has no channel available. The measurement is based on thehandover type and the channel type.


− Intra-cell handover requests in normal conditions− Intra-cell handover requests in concentric cells.


− SDCCH

− TCHF

− TCHH


− Underlaid subcell to overlaid subcell (Underlay to Overlay)

− Overlaid subcell to underlaid subcell (Overlay to Underlay)

Failed Intra-Cell Handovers (Terrestrial Resource Request Failed)As shown in Figure 12-11, the measurement is triggered when the BSC net-drive fails.

Failed Intra-Cell Handovers (A-Interface Failure)

As shown in Figure 12-11, the measurement is triggered when the BSC receives an A-interface failure message before the MS sends an HO CMP message to the BSC.

Failed Intra-Cell Handovers (Clear Commands Sent by MSC)

As shown in Figure 12-11, the measurement is triggered when the BSC receives a CLRCMD message before the MS sends an HO CMP message to the BSC.

Failed Intra-Cell Handovers (Timer Expired)

As shown in Figure 12-11, the BSC sends an HO CMD message to the MS and starts a

timer to wait for an HO CMP message. The measurement is triggered when the timerexpires. The measurement is based on the channel type.


− SDCCH

− TCHF

− TCHH

Failed Intra-Cell Handovers (Reconnection to Old Channels)

As shown in Figure 12-11, BSC sends an HO CMD message to the MS and starts a timer

to wait for an HO CMP message. Before the timer expires, the MS reconnects to the oldchannel and sends the BSC an HO FAIL message on the old channel. The measurement

is triggered when the BSC receives the HO FAIL message. The measurement is based on

the failure cause carried in the message.

The message carries any of the following failure causes:





Preemptive release

Handover failed, timing advance out of range


Frequency unavailable



12 Call Measurement












Other causes

Failed Intra-Cell Handovers (Concentric Cell)

As shown in Figure 12-11, after the BSC sends an HO CMD message to the MS, the

measurement is triggered when the BSC receives an HO FAIL message before receivingan HO CMP message from the MS. The HO FAIL message carries any cause except for

those described previously. The measurement is based on the handover direction

(underlaid subcell to overlaid subcell, overlaid subcell to underlaid subcell).

Formula

None.

12.10.5 Intra-Cell AMR Handover per Cell

Counter

Table 12-31 lists the counters of Intra-Cell AMR Handover per Cell.

Table 12-31 Counters of Intra-Cell AMR Handover per Cell

Number Counter

1 H3055A: Internal Intra-Cell Handovers Not Initiated (AMR) (TCHF-TCHH)

2 H3055B: Internal Intra-Cell Handovers Not Initiated (AMR) (TCHH-TCHF)

3 H3005A: Internal Intra-Cell Handover Requests (AMR) (TCHF-TCHH)

4 H3005B: Internal Intra-Cell Handover Requests (AMR) (TCHH-TCHF)

5 H3015A: Internal Intra-Cell Handover Commands (AMR) (TCHF-TCHH)

6 H3015B: Internal Intra-Cell Handover Commands (AMR) (TCHH-TCHF)

7 H3025A: Failed Internal Intra-Cell Handovers (AMR) (TCHF-TCHH)

8 H3025B: Failed Internal Intra-Cell Handovers (AMR) (TCHH-TCHF)

Meaning

For an Adaptive Multi-Rate (AMR) call, when the BSC decides that an intra-cell handover(TCHF to TCHH) is required based on the handover algorithm, the BSC ignores the handover






indication and measures Internal Intra-Cell Handovers Not Initiated (AMR) (TCHF-TCHH) ifthe MSC does not allow the conversion of channel types.

For an AMR call, when the BSC decides that an intra-cell handover (TCHH to TCHF) is

required based on the handover algorithm, the BSC ignores the handover indication and

measures Internal Intra-Cell Handovers Not Initiated (AMR) (TCHH-TCHF) if the MSC doesnot allow the conversion of channel types.

For an AMR call, when the BSC decides that an intra-cell handover (TCHF to TCHH) isrequired based on the handover algorithm, the BSC measures Internal Intra-Cell HandoverRequests (AMR) (TCHF-TCHH) if the handover is allowed.

For an AMR call, when the BSC decides that an intra-cell handover (TCHH to TCHF) isrequired based on the handover algorithm, the BSC measures Internal Intra-Cell HandoverRequests (AMR) (TCHH-TCHF) if the handover is allowed.

For an AMR call, if the BSC decides that an intra-cell handover (TCHF to TCHH) is required based on the handover algorithm, the BSC measures Internal Intra-Cell Handover Commands

(AMR) (TCHF-TCHH) when the handover is initiated and a handover command is sent.For an AMR call, if the BSC decides that an intra-cell handover (TCHH to TCHF) is required based on the handover algorithm, the BSC measures Internal Intra-Cell Handover Commands

(AMR) (TCHH-TCHF) when the handover is initiated and a handover command is sent.

For an AMR call, if the BSC decides that an intra-cell handover (TCHF to TCHH) is required based on the handover algorithm, the BSC measures Failed Internal Intra-Cell Handovers

(AMR) (TCHF-TCHH) when the handover is initiated but the handover fails due to a certaincause.

For an AMR call, if the BSC decides that an intra-cell handover (TCHH to TCHF) is required

based on the handover algorithm, the BSC measures Failed Internal Intra-Cell Handovers(AMR) (TCHH-TCHF) when the handover is initiated but the handover fails due to a certain

cause.

The AMR is a kind of speech codec algorithm. It can improve the speech quality by adjusting theencoding rate based on the radio environment.

To control the call performance in a flexible way and to maximize the network capacity, the BSC needs

a handover algorithm as follows:

If an AMR call seizes a full rate channel and its RQI is always higher than the defined threshold ofthe handover from the TCHF to the TCHH in a period of time, the handover from the TCHF to the

TCHH is triggered.

If an AMR call seizes a half rate channel and its RQI is always lower than the defined threshold ofthe handover from the TCHH to the TCHF in a period of time, the handover from the TCHH to the

TCHF is triggered.

The algorithm is controlled by the switches of both the intra-cell handover permit and the intra-cell

full rate–half rate handover permit. Because the BTS reports the RQI for only AMR calls, the AMRhandover is used for only AMR calls.

Trigger Point

For the description of the trigger points of the counters, refer to the trigger points of the

common handovers.

Formula

None.



12 Call Measurement




12.10.6 Intra-Cell Handover Detection Messages Received by BSCper Cell

CounterTable 12-32 lists the counters of Intra-Cell Handover Detection Messages Received by BSC

per Cell.

Table 12-32 Counters of Intra-Cell Handover Detection Messages Received by BSC per Cell

Number Counter

1 H3040: Internal Intra-Cell Handover Detection Messages Received by BSC(SDCCH)

2 H3047: Internal Intra-Cell Handover Detection Messages Received by BSC

(TCHF)

3 H3048: Internal Intra-Cell Handover Detection Messages Received by BSC(TCHH)

Meaning

The counters measure the number of times the BSC receives from the BTS an HO DETECT

message in the target cell (current cell). The measurement is based on the channel type.

The channel type consists of SDCCH, TCHF, and TCHH.

Trigger Point

As shown in Figure 12-11, the measurement is triggered when the BSC receives an HO

DETECT message in the target cell (current cell). The measurement is based on the channeltype.

Formula

None.

12.10.7 Intra-Cell Handover Measurement per CellCounter

Table 12-33 lists the counters of Intra-Cell Handover Measurement per Cell.

Table 12-33 Counters of Intra-Cell Handover Measurement per Cell

Number Counter

1 CH300: Internal Intra-Cell Handover Requests

2 CH303: Successful Internal Intra-Cell Handovers






Number Counter

3 TH303: Success Rate of Internal Intra-Cell Handover

4 TH3032: Success Rate of Internal Intra-Cell Handover (Underlay to Overlay)

5 TH3031: Success Rate of Internal Intra-Cell Handover (Overlay to Underlay)

6 CH301: Internal Intra-Cell Handover Commands

7 CH304: Internal Intra-Cell Handover Detection Messages Received by BSC

8 CH302: Failed Internal Intra-Cell Handovers

9 CH302A: Failed Internal Intra-Cell Handovers (Channel Unavailable)

10 CH302C: Failed Internal Intra-Cell Handovers (Timer Expiry)

11 CH302D: Failed Internal Intra-Cell Handovers (Reconnection to Old

Channels)

12 CH3022: Failed Internal Intra-Cell Handovers (Underlay to Overlay)

13 CH3021: Failed Internal Intra-Cell Handovers (Overlay to Underlay)

14 TH3033A: Success Rate of Internal Intra-Cell Handover (Dynamic

Conversion, TCHF-TCHH)

15 TH3033B: Success Rate of Internal Intra-Cell Handover (DynamicConversion, TCHH-TCHF)

16 TH3034A: Success Rate of Internal Intra-Cell Handover (Dynamic

Conversion, TCH-SDCCH)

17 TH3034B: Success Rate of Internal Intra-Cell Handover (Dynamic

Conversion, SDCCH-TCH)

18 TH3035A: Success Rate of Internal Intra-Cell Handover (AMR) (TCHF-

TCHH)

19 TH3035B: Success Rate of Internal Intra-Cell Handover (AMR) (TCHH-TCHF)

20 CH3032: Successful Internal Intra-Cell Handovers (Underlay to Overlay)

21 CH3031: Successful Internal Intra-Cell Handovers (Overlay to Underlay)

22 CH3033A: Successful Internal Intra-Cell Handovers (Dynamic Conversion,TCHF-TCHH)

23 CH3033B: Successful Internal Intra-Cell Handovers (Dynamic Conversion,TCHH-TCHF)

24 CH3034A: Successful Internal Intra-Cell Handovers (Dynamic Conversion,

TCH-SDCCH)

25 CH3034B: Successful Internal Intra-Cell Handovers (Dynamic Conversion,

SDCCH-TCH)

26 CH3035A: Successful Internal Intra-Cell Handovers (AMR) (TCHF-TCHH)



12 Call Measurement




Number Counter

27 CH3035B: Successful Internal Intra-Cell Handovers (AMR) (TCHH-TCHF)

Meaning

None.

Trigger Point

None.

Formula

Internal Intra-Cell Handover Requests =

[Internal Intra-Cell Handover Requests (SDCCH)] + [Internal Intra-Cell Handover Requests

(TCH)]

Successful Internal Intra-Cell Handovers =

[Internal Intra-Cell Handover Requests (SDCCH)] + [Internal Intra-Cell Handover Requests(TCH)]-[Failed Internal Intra-Cell Handovers (SDCCH)]-[Failed Internal Intra-Cell

Handovers (TCH)]

SUCCESS RATE OF INTERNAL INTRA-CELL HANDOVER =

[Successful Internal Intra-Cell Handovers]*{100}/[Internal Intra-Cell Handover Requests]

SUCCESS RATE OF INTERNAL INTRA-CELL HANDOVER (Underlay to Overlay) =

[Successful Internal Intra-Cell Handovers (Underlay to Overlay)]*{100}/[Internal Intra-Cell

Handover Requests (Underlay to Overlay)]

SUCCESS RATE OF INTERNAL INTRA-CELL HANDOVER (Overlay to Underlay) =

[Successful Internal Intra-Cell Handovers (Overlay to Underlay)]*{100}/[Internal Intra-Cell

Handover Requests (Overlay to Underlay)]

Internal Intra-Cell Handover Commands =

[Internal Intra-Cell Handover Commands (SDCCH)] +

[Internal Intra-Cell Handover Commands (TCHF)] +

[Internal Intra-Cell Handover Commands (TCHH)]

Internal Intra-Cell Handover Detection Messages Received by BSC =

[Internal Intra-Cell Handover Detection Messages Received by BSC (SDCCH)] +






[Internal Intra-Cell Handover Detection Messages Received by BSC (TCHF)] +

[Internal Intra-Cell Handover Detection Messages Received by BSC (TCHH)]

Failed Internal Intra-Cell Handovers =

[Failed Internal Intra-Cell Handovers (SDCCH)] +

[Failed Internal Intra-Cell Handovers (TCH)]

Failed Internal Intra-Cell Handovers (Channel Unavailable) =

[Failed Internal Intra-Cell Handovers (Channel Unavailable) (SDCCH)] +

[Failed Internal Intra-Cell Handovers (Channel Unavailable) (TCH)]

Failed Internal Intra-Cell Handovers (Timer Expired) =

[Failed Internal Intra-Cell Handovers (Timer Expired) (SDCCH)] +

[Failed Internal Intra-Cell Handovers (Timer Expired) (TCHF) (Signaling Channel)] +

[Failed Internal Intra-Cell Handovers (Timer Expired) (TCHH) (Signaling Channel)] +

[Failed Internal Intra-Cell Handovers (Timer Expired) (TCHF) (Traffic Channel)] +

[Failed Internal Intra-Cell Handovers (Timer Expired) (TCHH) (Traffic Channel)]

Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) =

[Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Abnormal Release,

Unspecified)] +

[Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Abnormal Release,Channel Unacceptable)] +

[Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Abnormal Release,

Timer Expired)] +

[Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, No

Activity on the Radio Path)] +

[Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Preemptive Release)]

+

[Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Handover Failed,Timing Advance out of Range)] +

[Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Channel ModeUnavailable)] +

[Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Frequency

Unavailable)] +

[Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Call Already Cleared)]

+



12 Call Measurement




[Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Semantically IncorrectMessage)] +

[Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Invalid Mandatory

Information)] +

[Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Message Type Non-

existent or Not Implemented)] +

[Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Message Type NotCompatible with Protocol State)] +

[Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Conditional IE Error)]+

[Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (No Cell Allocation

Available)] +

[Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Protocol Error

Unspecified)] +

[Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Other Causes)]

Failed Internal Intra-Cell Handovers (Underlay to Overlay) =

[Failed Internal Intra-Cell Handovers (Channel Unavailable) (Underlay to Overlay)] +

[Failed Internal Intra-Cell Handovers (Other Causes) (Underlay to Overlay)]

Failed Internal Intra-Cell Handovers (Overlay to Underlay) =

[Failed Internal Intra-Cell Handovers (Channel Unavailable) (Overlay to Underlay)] +

[Failed Internal Intra-Cell Handovers (Other Causes) (Overlay to Underlay)]

Success Rate of Internal Intra-Cell Handover (Dynamic Conversion, TCHF-TCHH) =

[Successful Internal Intra-Cell Handovers (Dynamic Conversion, TCHF-

TCHH)]*{100}/[Internal Intra-Cell Handover Requests (Dynamic Conversion, TCHF-TCHH)]

Success Rate of Internal Intra-Cell Handover (Dynamic Conversion, TCHH-TCHF) =[Successful Internal Intra-Cell Handovers (Dynamic Conversion, TCHH-

TCHF)]*{100}/[Internal Intra-Cell Handover Requests (Dynamic Conversion, TCHH-TCHF)]

Success Rate of Internal Intra-Cell Handover (Dynamic Conversion, TCH-SDCCH) =

Successful Internal Intra-Cell Handovers (Dynamic Conversion, TCH-SDCCH)]*{100}/[Internal Intra-Cell Handover Requests (Dynamic Conversion, TCH-

SDCCH)]

Success Rate of Internal Intra-Cell Handover (Dynamic Conversion, SDCCH-TCH) =






[Successful Internal Intra-Cell Handovers (Dynamic Conversion, SDCCH-TCH) ]*{100}/[ Internal Intra-Cell Handover Requests (Dynamic Conversion, SDCCH-TCH) ]

Success Rate of Internal Intra-Cell Handover (AMR) (TCHF-TCHH) =

[Successful Internal Intra-Cell Handovers (AMR) (TCHF-TCHH)]*{100}/[Internal Intra-CellHandover Requests (AMR) (TCHF-TCHH)]

Success Rate of Internal Intra-Cell Handover (AMR) (TCHH-TCHF) =

[Successful Internal Intra-Cell Handovers (AMR) (TCHH-TCHF)]*{100}/[Internal Intra-CellHandover Requests (AMR) (TCHH-TCHF)]

Successful Internal Intra-Cell Handovers (Underlay to Overlay) =

[Internal Intra-Cell Handover Requests (Underlay to Overlay)]-[Failed Internal Intra-CellHandovers (Channel Unavailable) (Underlay to Overlay)]-[Failed Internal Intra-Cell

Handovers (Other Causes) (Underlay to Overlay)]

Successful Internal Intra-Cell Handovers (Overlay to Underlay) =

[Internal Intra-Cell Handover Requests (Overlay to Underlay)]-[Failed Internal Intra-Cell

Handovers (Channel Unavailable) (Overlay to Underlay)]-[Failed Internal Intra-Cell

Handovers (Other Causes) (Overlay to Underlay)]

Successful Internal Intra-Cell Handovers (Dynamic Conversion, TCHF-TCHH) =

[Internal Intra-Cell Handover Requests (Dynamic Conversion, TCHF-TCHH)]- [Failed

Internal Intra-Cell Handovers (Dynamic Conversion, TCHF-TCHH) ]

Successful Internal Intra-Cell Handovers (Dynamic Conversion, TCHH-TCHF) =

[Internal Intra-Cell Handover Requests (Dynamic Conversion, TCHH-TCHF)]- [Failed

Internal Intra-Cell Handovers (TCHH-TCHF)]

Successful Internal Intra-Cell Handovers (Dynamic Conversion, TCH-SDCCH) =

[Internal Intra-Cell Handover Requests (Dynamic Conversion, TCH-SDCCH) ]-[ Failed

Internal Intra-Cell Handovers (Dynamic Conversion, TCH-SDCCH) ]

Successful Internal Intra-Cell Handovers (Dynamic Conversion, SDCCH-TCH) =

[Internal Intra-Cell Handover Requests (Dynamic Conversion, SDCCH-TCH)]- [FailedInternal Intra-Cell Handovers (Dynamic Conversion, SDCCH-TCH) ]

Successful Internal Intra-Cell Handovers (AMR) (TCHF-TCHH) =



12 Call Measurement




[Internal Intra-Cell Handover Requests (AMR) (TCHF-TCHH)]- [Failed Internal Intra-CellHandovers (AMR) (TCHF-TCHH)]

Successful Internal Intra-Cell Handovers (AMR) (TCHH-TCHF) =[Internal Intra-Cell Handover Requests (AMR) (TCHH-TCHF)]- [Failed Internal Intra-Cell

Handovers (AMR) (TCHH-TCHF)]

12.11 Incoming Internal Inter-Cell HandoverMeasurement per Cell

12.11.1 Overview

After an MS seizes a dedicated channel, it sends measurement reports to the BSC periodically.After receiving the measurement reports, the BSC uses the handover algorithm to decide

whether a handover is required or not on the basis of the factors such as the cell load,concentric cell, signal interference, and measurement reports. If a handover is required and

the source cell (current cell) and the target cell are two cells in a BSC, an internal inter-cellhandover is initiated.

The internal inter-cell handover procedure is as follows:

Step 1 The BSC sends a CHAN ACTIV message to the BTS where the target cell is located. Thismessage is used to activate the specified channel in the target cell.

Step 2 After receiving a CHAN ACTIV ACK message, the BSC requests for channel resources. If

the request succeeds, the BSC sends the MS an HO CMD message, requesting the MSthrough the source cell to initiate a handover from the source cell to the target cell.


Step 4 The target BTS forwards this message through an HO DETECT message to the BSC and

sends a PHY INFO message to the MS.

Step 5 The MS sends a FIRST SABM frame to the target BTS and the target BTS sends the BSC an

EST IND message, indicating that the MS has successfully accessed the target cell. The MS

also sends an HO CMP message to the BSC.


----End

The incoming internal inter-cell handover is part of the internal inter-cell handover. It refers to

the internal inter-cell handover procedure performed in the target cell (the cell where the MSis located after the handover). The source cell (the cell where the MS is located before the

handover) and the target cell can be two cells in a BTS or two cells in two BTSs controlled byone BSC.

Figure 12-12 shows the incoming internal inter-cell handover procedure.






Figure 12-12 Incoming internal inter-cell handover

BTS1(CELL1) BSCMS

PHY INFO

HO DETECT

MS MSCBTS1(CELLO)

A

B

CHAN ACTIV

HO ACC

FIRST SABM

EST IND

CHAN ACTIV

ACKHO CMD

MR FROM MS

HO CMP

HO PERFORMED

A: Incoming Internal Inter-Cell Handover Requests

B: Incoming Internal Inter-Cell Handover Responses

Table 12-34 lists the counter classification of Incoming Internal Inter-Cell HandoverMeasurement per Cell.

Table 12-34 Counter classification of Incoming Internal Inter-Cell Handover Measurement per

Cell


Incoming Internal Inter-Cell Handover Requests per Cell 0

Incoming Internal Inter-Cell Handover Responses per Cell 12.11.3

Failed Incoming Internal Inter-Cell Handovers per Cell 12.11.4

Incoming Internal Inter-Cell Handover Detection Messages Received byBSC per Cell

12.11.5

Incoming Internal Inter-Cell Handover Analyzed Measurement per Cell 12.11.6

12.11.2 Incoming Internal Inter-Cell Handover Requests per Cell

Counter

Table 12-35 lists the counters of Incoming Internal Inter-Cell Handover Requests per Cell.



12 Call Measurement




Table 12-35 Counters of Incoming Internal Inter-Cell Handover Requests per Cell

Number Counter

1 H3200W: Incoming Internal Inter-Cell Handover Requests (SDCCH)

(900/850-900/850)

2 H3200X: Incoming Internal Inter-Cell Handover Requests (SDCCH)(1800/1900-1800/1900)

3 H3200Y: Incoming Internal Inter-Cell Handover Requests (SDCCH) (900/850-1800/1900)

4 H3200Z: Incoming Internal Inter-Cell Handover Requests (SDCCH)(1800/1900-900/850)

5 H3209W: Incoming Internal Inter-Cell Handover Requests (TCH) (900/850-900/850)

6 H3209X: Incoming Internal Inter-Cell Handover Requests (TCH) (1800/1900-1800/1900)

7 H3209Y: Incoming Internal Inter-Cell Handover Requests (TCH) (900/850-1800/1900)

8 H3209Z: Incoming Internal Inter-Cell Handover Requests (TCH) (1800/1900-900/850)

Meaning

The BSC uses the handover algorithm to decide whether a handover is required or not based

on the measurement reports. If a handover is required and the source cell (current cell) and thetarget cell are two different cells controlled by a BSC, the BSC initiates an internal inter-cell

handover.

The counters measure the number of internal inter-cell handovers in the target cell. Themeasurement is based on the channel type and the crossing of frequency bands.

Along with Incoming Internal Inter-Cell Handover Responses per Cell and Failed Incoming

Internal Inter-Cell Handover , the counters show the performance of incoming internal inter-

cell handovers. Along with Outgoing Internal Inter-Cell Handover Measurement per Cell, thecounters show the performance of internal inter-cell handovers.


SDCCH

TCH


900/850 to 900/850

1800/1900 to 1800/1900

900/850 to 1800/1900

1800/1900 to 900/850






Trigger Point

As shown in Figure 12-12 (A), the measurement is triggered when the BSC decides to initiate

an incoming internal inter-cell handover. The measurement is based on the channel type and

the crossing of frequency bands.

Formula

None.

12.11.3 Incoming Internal Inter-Cell Handover Responses per Cell

Counter

Table 12-36 lists the counters of Incoming Internal Inter-Cell Handover Responses per Cell.

Table 12-36 Counters of Incoming Internal Inter-Cell Handover Responses per Cell

Number Counter

1 H3210W: Incoming Internal Inter-Cell Handover Responses (SDCCH)

(900/850-900/850)

2 H3210X: Incoming Internal Inter-Cell Handover Responses (SDCCH)

(1800/1900-1800/1900)

3 H3210Y: Incoming Internal Inter-Cell Handover Responses (SDCCH)(900/850-1800/1900)

4 H3210Z: Incoming Internal Inter-Cell Handover Responses (SDCCH)

(1800/1900-900/850)

5 H3217W: Incoming Internal Inter-Cell Handover Responses (TCHF)

(900/850-900/850)

6 H3217X: Incoming Internal Inter-Cell Handover Responses (TCHF)

(1800/1900-1800/1900)

7 H3217Y: Incoming Internal Inter-Cell Handover Responses (TCHF)(900/850-1800/1900)

8 H3217Z: Incoming Internal Inter-Cell Handover Responses (TCHF)

(1800/1900-900/850)

9 H3218W: Incoming Internal Inter-Cell Handover Responses (TCHH)

(900/850-900/850)

10 H3218X: Incoming Internal Inter-Cell Handover Responses (TCHH)(1800/1900-1800/1900)

11 H3218Y: Incoming Internal Inter-Cell Handover Responses (TCHH)(900/850-1800/1900)

12 H3218Z: Incoming Internal Inter-Cell Handover Responses (TCHH)(1800/1900-900/850)



12 Call Measurement




Meaning

The counters measure the number of incoming internal inter-cell handover responses of the

target cell. The BSC sends the MS an HO CMD message in the source cell. This message is

regarded as a handover response of the target cell to the MS. The measurement is based on the

channel type and the crossing of frequency bands.

Along with Incoming Internal Inter-Cell Handover Requests per Cell, Intra-Cell Handover

Requests per Cell, and Failed Incoming Internal Inter-Cell Handovers per Cell, the countersshow the performance of incoming internal inter-cell handovers. Along with Outgoing

Internal Inter-Cell Handover Measurement per Cell, the counters show the performance ofinternal inter-cell handovers.


SDCCH

TCHF

TCHHThe crossing of frequency bands is of the following types:

900/850 to 900/850

1800/1900 to 1800/1900

900/850 to 1800/1900

1800/1900 to 900/850

Trigger Point

As shown in Figure 12-12 (B), the measurement is triggered when the BSC sends the MS an

HO CMD message in the source cell. The measurement is based on the channel type and thecrossing of frequency bands.

Formula

None.

12.11.4 Failed Incoming Internal Inter-Cell Handovers per Cell

Counter

Table 12-37 lists the counters of Failed Incoming Internal Inter-Cell Handovers per Cell.

Table 12-37 Counters of Failed Incoming Internal Inter-Cell Handovers per Cell

Number Counter

1 H3220W: Failed Incoming Internal Inter-Cell Handovers (SDCCH) (900/850-900/850)

2 H3220X: Failed Incoming Internal Inter-Cell Handovers (SDCCH)(1800/1900-1800/1900)

3 H3220Y: Failed Incoming Internal Inter-Cell Handovers (SDCCH) (900/850-1800/1900)






Number Counter

4 H3220Z: Failed Incoming Internal Inter-Cell Handovers (SDCCH) (1800/1900-

900/850)

5 H3229W: Failed Incoming Internal Inter-Cell Handovers (TCH) (900/850-900/850)

6 H3229X: Failed Incoming Internal Inter-Cell Handovers (TCH) (1800/1900-1800/1900)

7 H3229Y: Failed Incoming Internal Inter-Cell Handovers (TCH) (900/850-

1800/1900)

8 H3229Z: Failed Incoming Internal Inter-Cell Handovers (TCH) (1800/1900-900/850)

9 H3220A: Failed Incoming Internal Inter-Cell Handovers (Channel Unavailable)

(SDCCH)

10 H3229A: Failed Incoming Internal Inter-Cell Handovers (Channel Unavailable)(TCH)

11 H322B: Failed Incoming Internal Inter-Cell Handovers (Terrestrial Resource

Request Failed)

12 H322D: Failed Incoming Internal Inter-Cell Handovers (Reconnection to OldChannels)

13 H322G: Failed Incoming Internal Inter-Cell Handovers (A-Interface Failure)

14 H3220C: Failed Incoming Internal Inter-Cell Handovers (Timer Expired)

(SDCCH)

15 H3227Cb: Failed Incoming Internal Inter-Cell Handovers (Timer Expired)(TCHF) (Signaling Channel)

16 H3228Cb: Failed Incoming Internal Inter-Cell Handovers (Timer Expired)

(TCHH) (Signaling Channel)

17 H3227Ca: Failed Incoming Internal Inter-Cell Handovers (Timer Expired)

(TCHF) (Traffic Channel)

18 H3228Ca: Failed Incoming Internal Inter-Cell Handovers (Timer Expired)(TCHH) (Traffic Channel)

Meaning

The counters measure the number of failed incoming internal inter-cell handovers in the targetcell due to different causes. The measurement is based on the channel type, the failure cause,

and the crossing of frequency bands.

Along with Incoming Internal Inter-Cell Handover Requests per Cell and Incoming InternalInter-Cell Handover Responses per Cell, the counters show the performance of incoming

internal inter-cell handovers. Along with Outgoing Internal Inter-Cell Handover Measurement per Cell, the counters show the performance of internal inter-cell handovers.



12 Call Measurement





SDCCH

TCH


900/850 to 900/850

1800/1900 to 1800/1900

900/850 to 1800/1900

1800/1900 to 900/850

The failure causes include:

Channel unavailable

Terrestrial resource request failure

A-interface failure

Timer expired


Trigger Point


Failed Incoming Internal Inter-Cell Handovers

As shown in Figure 12-13, the measurement is triggered when the intra-cell handoverfails before the handover completion timer expires. The measurement is based on thechannel type and the crossing of frequency bands.


− SDCCH

− TCH


− 900/850 to 900/850

− 1800/1900 to 1800/1900

− 900/850 to 1800/1900

− 1800/1900 to 900/850

Failed Incoming Internal Inter-Cell Handovers (Channel Unavailable)

As shown in Figure 12-13, the measurement is triggered when a channel request fails because the target cell has no channel available. The measurement is based on thechannel type.


− SDCCH

− TCHF

− TCHH

Failed Incoming Internal Inter-Cell Handovers (Terrestrial Resource Request Failed)

As shown in Figure 12-13, the measurement is triggered when the BSC net-drive fails.

Failed Incoming Internal Inter-Cell Handovers (A-Interface Failure)






As shown in Figure 12-13, the measurement is triggered when the BSC receives an A-interface failure message before the MS sends an HO CMP message to the BSC.

Failed Incoming Internal Inter-Cell Handovers (Timer Expired)

As shown in Figure 12-13, the BSC sends an HO CMD message to the MS and starts a

timer to wait for an HO CMP message. The measurement is triggered when the timerexpires. The measurement is based on the channel type.


− SDCCH

− TCHF

− TCHH

Failed Incoming Internal Inter-Cell Handovers (Reconnection to Old Channels)

As shown in Figure 12-13, BSC sends an HO CMD message to the MS and starts a timer

to wait for an HO CMP message. Before the timer expires, the MS reconnects to the oldchannel and sends the BSC an HO FAIL message on the old channel. The measurement

is triggered when the BSC receives the HO FAIL message.

Figure 12-13 Trigger points of the counters of Failed Incoming Internal Inter-Cell Handovers perCell

BTS1(CELL1) BSCMS MS MSCBTS1(CELLO)

E

PHY INFO

HO DETECT

A

B

F

CHAN ACTIV

HO ACC

FIRST SABM

EST IND

CHAN

ACTIV ACK

HO CMD

MR FROM MS

TIME OUT

HO FAIL

HO CMP

HO PERFORMED

C

D

In the

incoming

internal

inter-cellhandover

procedure

A: Failed Incoming Internal Inter-Cell Handovers (Channel Unavailable)

B: Failed Incoming Internal Inter-Cell Handovers (Terrestrial Resource Request Failed)

C: Failed Incoming Internal Inter-Cell Handovers (A-Interface Failure)

D: Failed Incoming Internal Inter-Cell Handovers

E: Failed Incoming Internal Inter-Cell Handovers (Timer Expired)

F: Failed Incoming Internal Inter-Cell Handovers (Reconnection to Old Channels)



12 Call Measurement




Formula

None.

12.11.5 Incoming Internal Inter-Cell Handover DetectionMessages Received by BSC per Cell

Counter

Table 12-38 lists the counters of Incoming Internal Inter-Cell Handover Detection Messages

Received by BSC per Cell.

Table 12-38 Counters of Incoming Internal Inter-Cell Handover Detection Messages Received by

BSC per Cell

Number Counter

1 H3240: Incoming Internal Inter-Cell Handover Detection Messages Received by BSC (SDCCH)

2 H3247: Incoming Internal Inter-Cell Handover Detection Messages Received

by BSC (TCHF)

3 H3248: Incoming Internal Inter-Cell Handover Detection Messages Received

by BSC (TCHH)

MeaningThe counters measure the number of times the BSC receives an HO DETECT message from

the BTS in the target cell. The measurement is based on the channel type.


SDCCH

TCHF

TCHH

Trigger Point

As shown in Figure 12-13, the measurement is triggered when the BSC receives an HODETECT message from the BTS in the target cell. The measurement is based on the channeltype.

Formula

None.






12.11.6 Incoming Internal Inter-Cell Handover AnalyzedMeasurement per Cell

CounterTable 12-39 lists the counters of Incoming Internal Inter-Cell Handover AnalyzedMeasurement per Cell.

Table 12-39 Counters of Incoming Internal Inter-Cell Handover Analyzed Measurement per Cell

Number Counter

1 CH320: Incoming Internal Inter-Cell Handover Requests

2 CH323: Successful Incoming Internal Inter-Cell Handovers

3 TH323: Success Rate of Incoming Internal Inter-Cell Handover

4 CH322: Failed Incoming Internal Inter-Cell Handovers

5 CH324: Incoming Internal Inter-Cell Handover Detection Messages Received byBSC

6 CH321: Incoming Internal Inter-Cell Handover Responses

7 CH322C: Failed Incoming Internal Inter-Cell Handovers (Timer Expired)

Meaning None.

Trigger Point

None.

Formula

Incoming Internal Inter-Cell Handover Requests =

[Incoming Internal Inter-Cell Handover Requests (SDCCH) (900/850-900/850)] +




[Incoming Internal Inter-Cell Handover Requests (TCH) (900/850-900/850)] +



[Incoming Internal Inter-Cell Handover Requests (TCH) (1800/1900-900/850)]



12 Call Measurement




Successful Incoming Internal Inter-Cell Handovers =








[Incoming Internal Inter-Cell Handover Requests (TCH) (1800/1900-900/850)]-

[Failed Incoming Internal Inter-Cell Handovers (SDCCH) (900/850-900/850)]-

[Failed Incoming Internal Inter-Cell Handovers (SDCCH) (1800/1900-1800/1900)]-[Failed Incoming Internal Inter-Cell Handovers (SDCCH) (900/850-1800/1900)]-

[Failed Incoming Internal Inter-Cell Handovers (SDCCH) (1800/1900-900/850)]-

[Failed Incoming Internal Inter-Cell Handovers (TCH) (900/850-900/850)]-



[Failed Incoming Internal Inter-Cell Handovers (TCH) (1800/1900-900/850)]

Success Rate of Incoming Internal Inter-Cell Handover =

[Successful Incoming Internal Inter-Cell Handovers]*{100}/[Incoming Internal Inter-Cell

Handover Requests]

Failed Incoming Internal Inter-Cell Handovers =

[Failed Incoming Internal Inter-Cell Handovers (SDCCH) (900/850-900/850)] +




[Failed Incoming Internal Inter-Cell Handovers (TCH) (900/850-900/850)] +



[Failed Incoming Internal Inter-Cell Handovers (TCH) (1800/1900-900/850)]

Incoming Internal Inter-Cell Handover Detection Messages Received by BSC =

[Incoming Internal Inter-Cell Handover Detection Messages Received by BSC (SDCCH)] +






[Incoming Internal Inter-Cell Handover Detection Messages Received by BSC (TCHF)] +

[Incoming Internal Inter-Cell Handover Detection Messages Received by BSC (TCHH)]

Incoming Internal Inter-Cell Handover Responses =

[Incoming Internal Inter-Cell Handover Responses (SDCCH) (900/850-900/850)] +




[Incoming Internal Inter-Cell Handover Responses (TCHF) (900/850-900/850)] +

[Incoming Internal Inter-Cell Handover Responses (TCHF) (1800/1900-1800/1900)] +

[Incoming Internal Inter-Cell Handover Responses (TCHF) (900/850-1800/1900)] +[Incoming Internal Inter-Cell Handover Responses (TCHF) (1800/1900-900/850)] +

[Incoming Internal Inter-Cell Handover Responses (TCHH) (900/850-900/850)] +



[Incoming Internal Inter-Cell Handover Responses (TCHH) (1800/1900-900/850)]

Failed Incoming Internal Inter-Cell Handovers (Timer Expired) =

[Failed Incoming Internal Inter-Cell Handovers (Timer Expired) (SDCCH)] +

[Failed Incoming Internal Inter-Cell Handovers (Timer Expired) (TCHF) (Signaling Channel)]

+

[Failed Incoming Internal Inter-Cell Handovers (Timer Expired) (TCHH) (Signaling Channel)]+

[Failed Incoming Internal Inter-Cell Handovers (Timer Expired) (TCHF) (Traffic Channel)] +

[Failed Incoming Internal Inter-Cell Handovers (Timer Expired) (TCHH) (Traffic Channel)]

12.12 Outgoing Internal Inter-Cell HandoverMeasurement per Cell

12.12.1 Overview

Outgoing Internal Inter-Cell Handover Measurement per cell is used to measure the handover

of the cells controlled by one BSC. The measurement is performed in the source cell.

The outgoing internal inter-cell handover is initiated by measurement reports or by

assignment requests sent from the MSC. The descriptions of these two types of handovers areas follows:



12 Call Measurement




Outgoing internal inter-cell handover initiated by measurement reports (excluding

directed retry)

After an MS seizes a dedicated channel, it sends measurement reports to the BSC periodically.

After receiving the measurement reports, the BSC uses the handover algorithm to decide

whether a handover is required or not on the basis of the factors such as the cell load,concentric cell, signal interference, and measurement reports. If a handover is required and

the source cell (current cell) and the target cell are two cells in a BSC, an internal inter-cellhandover is initiated.

The procedure is as follows:

Step 1 The BSC sends a CHAN ACTIV message to the BTS where the target cell is located. This

message is used to activate the specified channel in the target cell.

Step 2 After receiving a CHAN ACTIV ACK message, the BSC requests for speech service

resources. If the request succeeds, the BSC sends the MS an HO CMD message, requestingthe MS to initiate a handover from the source cell to the target cell.


Step 4 The target BTS forwards this message through an HO DETECT message to the BSC andsends a PHY INFO message to the MS.

Step 5 The MS sends a FIRST SABM frame to the target BTS and the target BTS sends an EST INDmessage to the BSC, indicating that the MS has successfully accessed the target cell. The MSalso sends an HO CMP message to the BSC.


----End

The outgoing internal inter-cell handover is part of the internal inter-cell handover. It refers tothe internal inter-cell handover procedure performed in the source cell (the cell where the MSis located before the handover). The source cell and the target cell (the cell where the MS is

located after the handover) can be two cells in a BTS or two cells in two BTSs controlled byone BSC.

Figure 12-14 shows the procedure of outgoing internal inter-cell handover (excluding directedretry).






Figure 12-14 Outgoing internal inter-cell handover (excluding directed retry)

BTS1(CELL1) BSCMS

PHY INFO

HO DETECT

MS MSCBTS1(CELLO)

A

B

CHAN ACTIV

HO ACC

FIRST SABM

EST IND

CHAN

ACTIV ACKHO CMD

MR FROM MS

HO CMP

HO PERFORMED

A: Outgoing Internal Inter-Cell Handover Requests (Excluding Directed Retry)

B: Outgoing Internal Inter-Cell Handover Commands (Excluding Directed Retry)

Outgoing internal inter-cell handover initiated by the assignment request sent from theMSC (directed retry)


Step 1 When an MS needs to initiate a call, it sends a CHAN RQD message to the BSC through theBTS.

Step 2 The BSC requests for an SDCCH or TCH signaling channel, and sends a CHAN ACTIVmessage to the BTS. After receiving a CHAN ACTIV ACK message from the BTS, the BSC

sends the MS an IMM ASS CMD message on the signaling channel, requesting the MS toaccess the network on this signaling channel.

Step 3 After receiving an EST IND message from the MS, the BSC encapsulates the CM SERV

REQ message carried in the EST IND message into the CR message and forwards it to theMSC. After the MSC returns a CC message, the communication between the MS and theMSC is established on the MM layer.

Step 4 After the messages CM SERV ACCEPT, SETUP, and CALL PROCEEDING are sent, theMSC sends an ASS REQ message to the BSC and the BSC analyzes the information such as

cell load to select an assignment mode (normal assignment, mode modification, directed

retry). If current cell load is too high, the BSC decides to initiate a directed retry procedure.

Step 5 The BSC sends a CHAN ACTIV message to the target cell. After receiving a CHAN ACTIV

ACK message, the BSC requests for speech service resources.

Step 6 If the request succeeds, the BSC sends an HO CMD message to the MS, and the MS sends an

HO ACC message to attempt to access a new cell.



12 Call Measurement




Step 7 The BTS sends an HO DETECT message to the BSC and sends a PHY INFO message to theMS.

Step 8 The MS sends a FIRST SABM to access the network. The BTS sends an EST IND messageto the BSC and a UA frame to the MS. The MS sends an HO CMP message to the BSC.

Step 9 The BSC sends an ASS CMP message to the MSC and completes other signaling processing.

----End

The outgoing internal inter-cell handover is part of the internal inter-cell handover procedure.

It refers to the handover procedure performed in the source cell (the cell where the MS islocated before the handover). The source cell and the target cell (the cell where the MS is

located after the handover) can be two cells in a BTS or two cells in two BTSs controlled byone BSC.

Figure 12-15 Outgoing internal inter-cell handover (directed retry)

BTS1(CELL1) BSCMS

UA EST IND（CM

SERV REQ）

MSBTS2(CELLO)

A

B

CHAN ACTIV

FIRST SABM

FIRST SABM

CHAN

ACTIV ACK

HO CMD

CHAN RED

CHAN REQ

IMM ASS CMD

CC

CR(CM

SERV REQ)

CM SERV

ACCEPT

SETUP

CALL

PROCEEDING

ASSIGN REQ

CHAN ACTIV

CHAN ACTIV ACK

UA

HO ACC

PHY INFOHO DETECT

EST IND

HO CMP

ASSIGN CMP

MSC

A: Outgoing Internal Inter-Cell Handover Requests (Directed Retry)

B: Outgoing Internal Inter-Cell Handover Commands (Directed Retry)






Table 12-40 lists the counter classification of Outgoing Internal Inter-Cell Handover

Measurement per Cell.

Table 12-40 Counter classification of Outgoing Internal Inter-Cell Handover Measurement per

CellCounter Classification Section

Outgoing Internal Inter-Cell Handover Requests per Cell 0

Outgoing Internal Inter-Cell Handover Commands per Cell 12.12.3

Failed Outgoing Internal Inter-Cell Handovers per Cell 12.12.3

Outgoing Internal Inter-Cell Handover Measurement per Cell 12.12.5

12.12.2 Outgoing Internal Inter-Cell Handover Requests per Cell

Counter

Table 12-41 lists the counters of Outgoing Internal Inter-Cell Handover Requests per Cell(Excluding Directed Retry).

Table 12-41 Counters of Outgoing Internal Inter-Cell Handover Requests per Cell (ExcludingDirected Retry)

Number Counter

1 H3100W: Outgoing Internal Inter-Cell Handover Requests (SDCCH)(Excluding Directed Retry) (900/850-900/850)

2 H3100X: Outgoing Internal Inter-Cell Handover Requests (SDCCH)(Excluding Directed Retry) (1800/1900-1800/1900)

3 H3100Y: Outgoing Internal Inter-Cell Handover Requests (SDCCH)(Excluding Directed Retry) (900/850-1800/1900)

4 H3100Z: Outgoing Internal Inter-Cell Handover Requests (SDCCH)(Excluding Directed Retry) (1800/1900-900/850)

5 H3107W: Outgoing Internal Inter-Cell Handover Requests (TCHF) (Excluding

Directed Retry) (900/850-900/850)

6 H3107X: Outgoing Internal Inter-Cell Handover Requests (TCHF) (ExcludingDirected Retry) (1800/1900-1800/1900)

7 H3107Y: Outgoing Internal Inter-Cell Handover Requests (TCHF) (ExcludingDirected Retry) (900/850-1800/1900)

8 H3107Z: Outgoing Internal Inter-Cell Handover Requests (TCHF) (Excluding

Directed Retry) (1800/1900-900/850)

9 H3108W: Outgoing Internal Inter-Cell Handover Requests (TCHH) (ExcludingDirected Retry) (900/850-900/850)



12 Call Measurement




Number Counter

10 H3108X: Outgoing Internal Inter-Cell Handover Requests (TCHH) (Excluding

Directed Retry) (1800/1900-1800/1900)

11 H3108Y: Outgoing Internal Inter-Cell Handover Requests (TCHH) (ExcludingDirected Retry) (900/850-1800/1900)

12 H3108Z: Outgoing Internal Inter-Cell Handover Requests (TCHH) (ExcludingDirected Retry) (1800/1900-900/850)

13 H310A: Outgoing Internal Inter-Cell Handover Requests (Uplink Quality)

14 H310B: Outgoing Internal Inter-Cell Handover Requests (Downlink Quality)

15 H310C: Outgoing Internal Inter-Cell Handover Requests (Uplink Strength)

16 H310D: Outgoing Internal Inter-Cell Handover Requests (Downlink Strength)

17 H310E: Outgoing Internal Inter-Cell Handover Requests (Timing Advance)

18 H310F: Outgoing Internal Inter-Cell Handover Requests (Better Cell)

19 H310G: Outgoing Internal Inter-Cell Handover Requests (Load)

20 H310H: Outgoing Internal Inter-Cell Handover Requests (Rapid Level Drop)

21 H310I: Outgoing Internal Inter-Cell Handover Requests (MSC Intervention)

22 H310J: Outgoing Internal Inter-Cell Handover Requests (OM Intervention)

23 H310L: Outgoing Internal Inter-Cell Handover Requests (Other Causes)

Table 12-42 lists the counters of Outgoing Internal Inter-Cell Handover Requests per Cell

(Directed Retry).

Table 12-42 Counters of Outgoing Internal Inter-Cell Handover Requests per Cell (Directed Retry)

Number Counter

1 H3101W: Outgoing Internal Inter-Cell Handover Requests (Directed Retry)

(900/850-900/850)

2 H3101X: Outgoing Internal Inter-Cell Handover Requests (Directed Retry)

(1800/1900-1800/1900)

3 H3101Y: Outgoing Internal Inter-Cell Handover Requests (Directed Retry)(900/850-1800/1900)

4 H3101Z: Outgoing Internal Inter-Cell Handover Requests (Directed Retry)

(1800/1900-900/850)

Meaning

The descriptions of the counters are as follows






Outgoing Internal Inter-Cell Handover Requests (Excluding Directed Retry)

The BSC uses the handover algorithm to decide whether a handover is required or not

based on the measurement reports. If a handover is required and the source cell (currentcell) and the target cell are two cells controlled by one BSC, the BSC initiates an internal

inter-cell handover.The counter measures the number of outgoing internal inter-cell handover requests

initiated by the BSC. The measurement is based on the channel type, the handover cause,and the crossing of frequency bands.

Along with Outgoing Internal Inter-Cell Handover Commands per Cell and Failed

Outgoing Internal Inter-Cell Handovers per Cell, the counter shows the performance ofoutgoing internal inter-cell handovers. Along with Incoming Internal Inter-Cell

Handover Measurement per Cell, the counter shows the performance of internal inter-cell handovers.


− SDCCH

− TCHF− TCHH

The handover causes consist of the following:

− Uplink quality

− Downlink quality

− Uplink strength

− Downlink strength

− Timing advance

− Better cell

−

Load− Rapid level drop

− MSC intervention

− OM intervention

− Other causes


− 900/850 to 900/850

− 1800/1900 to 1800/1900

− 900/850 to 1800/1900

− 1800/1900 to 900/850

Outgoing Internal Inter-Cell Handover Requests (Directed Retry)

When directed retry occurs in the assignment procedure and the source cell and the target

cell are two cells controlled by one BSC, the BSC sends an outgoing internal inter-cellhandover request to the MS. This counter measures the number of outgoing internal

inter-cell handover requests. The measurement is based on the crossing of frequency bands.

Along with Outgoing Internal Inter-Cell Handover Commands per Cell and FailedOutgoing Internal Inter-Cell Handovers per Cell, the counter shows the performance of

outgoing internal inter-cell handovers. Along with Incoming Internal Inter-Cell





12 Call Measurement




− 900/850 to 900/850

− 1800/1900 to 1800/1900

− 900/850 to 1800/1900

− 1800/1900 to 900/850

Trigger Point


Outgoing Internal Inter-Cell Handover Requests (Excluding Directed Retry)

As shown in Figure 12-14 (A), the measurement is triggered when the BSC decides to

initiate an outgoing internal inter-cell handover based on measurement reports. Themeasurement is based on the channel type, the handover cause, and the crossing offrequency bands.

Outgoing Internal Inter-Cell Handover Requests (Directed Retry)

As shown in Figure 12-15 (A), the measurement is triggered when the BSC initiates adirected retry procedure. The measurement is based on the crossing of frequency bands.

Formula

None.

12.12.3 Outgoing Internal Inter-Cell Handover Commands perCell

Counter

Table 12-43 lists the counters of Outgoing Internal Inter-Cell Handover Commands per Cell(Excluding Directed Retry).

Table 12-43 Counters of Outgoing Internal Inter-Cell Handover Commands per Cell (ExcludingDirected Retry)

Number Counter

1 H3110W: Outgoing Internal Inter-Cell Handover Command (SDCCH)(Excluding Directed Retry) (900/850-900/850)

2 H3110X: Outgoing Internal Inter-Cell Handover Commands (SDCCH)

(Excluding Directed Retry) (1800/1900-1800/1900)

3 H3110Y: Outgoing Internal Inter-Cell Handover Commands (SDCCH)(Excluding Directed Retry) (900/850-1800/1900)

4 H3110Z: Outgoing Internal Inter-Cell Handover Commands (SDCCH)(Excluding Directed Retry) (1800/1900-900/850)

5 H3117W: Outgoing Internal Inter-Cell Handover Commands (TCHF)(Excluding Directed Retry) (900/850-900/850)

6 H3117X: Outgoing Internal Inter-Cell Handover Commands (TCHF)(Excluding Directed Retry) (1800/1900-1800/1900)






Number Counter

7 H3117Y: Outgoing Internal Inter-Cell Handover Commands (TCHF)


8 H3117Z: Outgoing Internal Inter-Cell Handover Commands (TCHF)(Excluding Directed Retry) (1800/1900-900/850)

9 H3118W: Outgoing Internal Inter-Cell Handover Commands (TCHH)(Excluding Directed Retry) (900/850-900/850)

10 H3118X: Outgoing Internal Inter-Cell Handover Commands (TCHH)


11 H3118Y: Outgoing Internal Inter-Cell Handover Commands (TCHH)(Excluding Directed Retry) (900/850-1800/1900)

12 H3118Z: Outgoing Internal Inter-Cell Handover Commands (TCHH)


13 H311A: Outgoing Internal Inter-Cell Handover Commands (Uplink Quality)

14 H311B: Outgoing Internal Inter-Cell Handover Commands (DownlinkQuality)

15 H311C: Outgoing Internal Inter-Cell Handover Commands (Uplink Strength)

16 H311D: Outgoing Internal Inter-Cell Handover Commands (DownlinkStrength)

17 H311E: Outgoing Internal Inter-Cell Handover Commands (Timing Advance)

18 H311F: Outgoing Internal Inter-Cell Handover Commands (Better Cell)

19 H311G: Outgoing Internal Inter-Cell Handover Commands (Load)

20 H311H: Outgoing Internal Inter-Cell Handover Commands (Rapid Level

Drop)

21 H311I: Outgoing Internal Inter-Cell Handover Commands (MSC Intervention)

22 H311J: Outgoing Internal Inter-Cell Handover Commands (OM Intervention)

23 H311L: Outgoing Internal Inter-Cell Handover Commands (Other Causes)

Table 12-44 lists the counters of Outgoing Internal Inter-Cell Handover Commands per Cell(Directed Retry).

Table 12-44 Counters of Outgoing Internal Inter-Cell Handover Commands per Cell (DirectedRetry)

Number Counter

1 H3111W: Outgoing Internal Inter-Cell Handover Commands (Directed Retry)

(900/850-900/850)

2 H3111X: Outgoing Internal Inter-Cell Handover Commands (Directed Retry)

(1800/1900-1800/1900)



12 Call Measurement




Number Counter

3 H3111Y: Outgoing Internal Inter-Cell Handover Commands (Directed Retry)

(900/850-1800/1900)

4 H3111Z: Outgoing Internal Inter-Cell Handover Commands (Directed Retry)(1800/1900-900/850)

Meaning

The descriptions of the counters are as follows:

Outgoing Internal Inter-Cell Handover Commands (Excluding Directed Retry)

In the outgoing internal inter-cell handover (excluding directed retry) procedure, theBSC sends an HO CMD message to the MS. The measurement is performed in the

source cell. The measurement is based on channel type, the handover cause, and thecrossing of frequency bands.

Along with Outgoing Internal Inter-Cell Handover Requests per Cell and Failed

Outgoing Internal Inter-Cell Handovers per Cell, the counter shows the performance ofoutgoing internal inter-cell handovers. Along with Incoming Internal Inter-CellHandover Measurement per Cell, the counter shows the performance of internal inter-

cell handovers.


− SDCCH

− TCHF

− TCHH


− Uplink quality


− Uplink strength


− Timing advance

− Better cell

− Load

− Rapid level drop


− OM intervention

− EDGE coverage

− Other causes


− 900/850 to 900/850

− 1800/1900 to 1800/1900

− 900/850 to 1800/1900

− 1800/1900 to 900/850

Outgoing Internal Inter-Cell Handover Commands (Directed Retry)






In the outgoing internal inter-cell handover (directed retry) procedure, the BSC sends anHO CMD message to the MS through the source cell. The measurement is performed inthe source cell. The measurement is based on the crossing of frequency bands.

Along with Outgoing Internal Inter-Cell Handover Requests per Cell and Failed

Outgoing Internal Inter-Cell Handovers per Cell, the counter shows the performance ofoutgoing internal inter-cell handovers. Along with Incoming Internal Inter-Cell



− 900/850 to 900/850

− 1800/1900 to 1800/1900

− 900/850 to 1800/1900

− 1800/1900 to 900/850

Trigger Point


Outgoing Internal Inter-Cell Handover Commands (Excluding Directed Retry)

As shown in Figure 12-14 (B), the measurement is triggered when the BSC sends an HOCMD message to the MS through the source cell in the outgoing internal inter-cellhandover (excluding directed retry) procedure. The measurement is based on channeltype, the handover cause, and the crossing of frequency bands.

Outgoing Internal Inter-Cell Handover Commands (Directed Retry)

As shown in Figure 12-15 (B), the measurement is triggered when the BSC sends an HO

CMD message to the MS through the source cell in the outgoing internal inter-cellhandover (directed retry) procedure.

Formula

None.

12.12.4 Failed Outgoing Internal Inter-Cell Handovers per Cell

Counter

Based on the procedure where the trigger points are located, the counters of Failed Outgoing

Internal Inter-Cell Handovers per Cell can be classified into the following groups:

Failed Outgoing Internal Inter-Cell Handovers per Cell (Excluding Directed Retry)

Failed Outgoing Internal Inter-Cell Handovers per Cell (Directed Retry)

Failed Outgoing Internal Inter-Cell Handovers per Cell (Including Directed Retry)

Table 12-45 lists the counters of Failed Outgoing Internal Inter-Cell Handovers per Cell

(Excluding Directed Retry).



12 Call Measurement




Table 12-45 Counters of Failed Outgoing Internal Inter-Cell Handovers per Cell (ExcludingDirected Retry)

Number Counter

1 H3120W: Failed Outgoing Internal Inter-Cell Handovers (SDCCH)(Excluding Directed Retry) (900/850-900/850)

2 H3120X: Failed Outgoing Internal Inter-Cell Handovers (SDCCH)(Excluding Directed Retry) (1800/1900-1800/1900)

3 H3120Y: Failed Outgoing Internal Inter-Cell Handovers (SDCCH)


4 H3120Z: Failed Outgoing Internal Inter-Cell Handovers (SDCCH)


5 H3127W: Failed Outgoing Internal Inter-Cell Handovers (TCHF) (ExcludingDirected Retry) (900/850-900/850)

6 H3127X: Failed Outgoing Internal Inter-Cell Handovers (TCHF) (ExcludingDirected Retry) (1800/1900-1800/1900)

7 H3127Y: Failed Outgoing Internal Inter-Cell Handovers (TCHF) (Excluding

Directed Retry) (900/850-1800/1900)

8 H3127Z: Failed Outgoing Internal Inter-Cell Handovers (TCHF) (ExcludingDirected Retry) (1800/1900-900/850)

9 H3128W: Failed Outgoing Internal Inter-Cell Handovers (TCHH)(Excluding Directed Retry) (900/850-900/850)

10 H3128X: Failed Outgoing Internal Inter-Cell Handovers (TCHH) (ExcludingDirected Retry) (1800/1900-1800/1900)

11 H3128Y: Failed Outgoing Internal Inter-Cell Handovers (TCHH) (Excluding

Directed Retry) (900/850-1800/1900)

12 H3128Z: Failed Outgoing Internal Inter-Cell Handovers (TCHH) (ExcludingDirected Retry) (1800/1900-900/850)

13 H3120C: Failed Outgoing Internal Inter-Cell Handovers (Timer Expired)(SDCCH) (Excluding Directed Retry)

14 H312Da: Failed Outgoing Internal Inter-Cell Handovers (Reconnection toOld Channels) (Abnormal Release, Unspecified)

15 H312Db: Failed Outgoing Internal Inter-Cell Handovers (Reconnection toOld Channels) (Abnormal Release, Channel Unacceptable)

16 H312Dc: Failed Outgoing Internal Inter-Cell Handovers (Reconnection toOld Channels) (Abnormal Release, Timer Expired)

17 H312Dd: Failed Outgoing Internal Inter-Cell Handovers (Reconnection toOld Channels) (Abnormal Release, No Activity on the Radio Path)

18 H312De: Failed Outgoing Internal Inter-Cell Handovers (Reconnection toOld Channels) (Preemptive Release)






Number Counter

19 H312Df: Failed Outgoing Internal Inter-Cell Handovers (Reconnection to

Old Channels) (Handover Failed, Timing Advance out of Range)

20 H312Dg: Failed Outgoing Internal Inter-Cell Handovers (Reconnection toOld Channels) (Channel Mode Unavailable)

21 H312Dh: Failed Outgoing Internal Inter-Cell Handovers (Reconnection toOld Channels) (Frequency Unavailable)

22 H312Di: Failed Outgoing Internal Inter-Cell Handovers (Reconnection to

Old Channels) (Call Already Cleared)

23 H312Dj: Failed Outgoing Internal Inter-Cell Handovers (Reconnection toOld Channels) (Semantically Incorrect Message)

24 H312Dk: Failed Outgoing Internal Inter-Cell Handovers (Reconnection to

Old Channels) (Invalid Mandatory Information)

25 H312Dl: Failed Outgoing Internal Inter-Cell Handovers (Reconnection toOld Channels) (Message Type Non-existent or Not Implemented)

26 H312Dm: Failed Outgoing Internal Inter-Cell Handovers (Reconnection to

Old Channels) (Message Type Not Compatible with Protocol State)

27 H312Dn: Failed Outgoing Internal Inter-Cell Handovers (Reconnection toOld Channels) (Conditional IE Error)

28 H312Do: Failed Outgoing Internal Inter-Cell Handovers (Reconnection toOld Channels) (No Cell Allocation Available)

29 H312Dp: Failed Outgoing Internal Inter-Cell Handovers (Reconnection toOld Channels) (Protocol Error Unspecified)

30 H312Dq: Failed Outgoing Internal Inter-Cell Handovers (Reconnection toOld Channels) (Other Causes)

Table 12-46 lists the counters of Failed Outgoing Internal Inter-Cell Handovers per Cell

(Directed Retry).

Table 12-46 Counters of Failed Outgoing Internal Inter-Cell Handovers per Cell (Directed Retry)

Number Counter

1 H3121W: Failed Outgoing Internal Inter-Cell Handovers (Directed Retry)

(900/850-900/850)

2 H3121X: Failed Outgoing Internal Inter-Cell Handovers (Directed Retry)

(1800/1900-1800/1900)

3 H3121Y: Failed Outgoing Internal Inter-Cell Handovers (Directed Retry)(900/850-1800/1900)

4 H3121Z: Failed Outgoing Internal Inter-Cell Handovers (Directed Retry)(1800/1900-900/850)



12 Call Measurement




Number Counter

5 H3121C: Failed Outgoing Internal Inter-Cell Handovers (Timer Expired)

(Directed Retry)

Failed Outgoing Internal Inter-Cell Handovers per Cell (Including Directed Retry) refers the

failed outgoing internal inter-cell handovers initiated by measurement reports or directed retry.

Table 12-47 lists the counters of Failed Outgoing Internal Inter-Cell Handovers per Cell(Including Directed Retry)

Table 12-47 Counters of Failed Outgoing Internal Inter-Cell Handovers per Cell (IncludingDirected Retry)

Number Counter

1 H312A: Failed Outgoing Internal Inter-Cell Handovers (Channel Unavailable)

2 H312B: Failed Outgoing Internal Inter-Cell Handovers (Terrestrial Resource

Request Failed)

3 H312G: Failed Outgoing Internal Inter-Cell Handovers (A-Interface Failure)

4 H3127Cb: Failed Outgoing Internal Inter-Cell Handovers (Timer Expired)(TCHF) (Signaling Channel)

5 H3128Cb: Failed Outgoing Internal Inter-Cell Handovers (Timer Expired)(TCHH) (Signaling Channel)

6 H3127Ca: Failed Outgoing Internal Inter-Cell Handovers (Timer Expired)(TCHF) (Traffic Channel)

7 H3128Ca: Failed Outgoing Internal Inter-Cell Handovers (Timer Expired)(TCHH) (Traffic Channel)

8 H3122A: Failed Outgoing Internal Inter-Cell Handovers (Uplink Quality)

9 H3122B: Failed Outgoing Internal Inter-Cell Handovers (Downlink Quality)

10 H3122C: Failed Outgoing Internal Inter-Cell Handovers (Uplink Strength)

11 H3122D: Failed Outgoing Internal Inter-Cell Handovers (Downlink Strength)

12 H3122E: Failed Outgoing Internal Inter-Cell Handovers (Timing Advance)

13 H3122F: Failed Outgoing Internal Inter-Cell Handovers (Better Cell)

14 H3122G: Failed Outgoing Internal Inter-Cell Handovers (Load)

15 H3122H: Failed Outgoing Internal Inter-Cell Handovers (Rapid Level Drop)

16 H3122I: Failed Outgoing Internal Inter-Cell Handovers (MSC Intervention)

17 H3122J: Failed Outgoing Internal Inter-Cell Handovers (OM Intervention)

18 H3122L: Failed Outgoing Internal Inter-Cell Handovers (Other Causes)






Meaning


Failed Outgoing Internal Inter-Cell Handovers per Cell (Excluding Directed Retry)

In the outgoing internal inter-cell handover (excluding directed retry) procedure, whenthe outgoing internal inter-cell handover fails because errors occur before the BSC

receives an HO CMP message or before the timer that is set to wait for the HO CMPmessage expires, the BSC measures the counters. The measurement is based on thechannel type, the failure cause, the handover cause, and the crossing of frequency bands.

Along with Outgoing Internal Inter-Cell Handover Requests per Cell and Outgoing

Internal Inter-Cell Handover Commands per Cell, the counters show the performance ofoutgoing internal inter-cell handovers. Along with Incoming Internal Inter-Cell

Handover Measurement per Cell, the counters show the performance of internal inter-cell handovers.


− SDCCH− TCHF

− TCHH

The failure causes include the following:

− Channel unavailable

− Terrestrial resource request failure

− A-Interface Failure

− MSC Intervention

− Timer Expired

− Reconnection to Old Channels

− Congestion


− Uplink quality


− Uplink strength


− Timing advance

− Better cell

− Load



− OM intervention

− EDGE coverage

− Other causes


− 900/850 to 900/850

− 1800/1900 to 1800/1900

− 900/850 to 1800/1900

− 1800/1900 to 900/850



12 Call Measurement




Failed Outgoing Internal Inter-Cell Handovers per Cell (Directed Retry)

In the outgoing internal inter-cell handover (directed retry) procedure, when the outgoing

internal inter-cell handover fails because errors occur before the BSC receives an HOCMP message or before the timer that is set to wait for the HO CMP message expires,

the BSC measures the counters. The measurement is based on the channel type, thefailure cause, the handover cause, and the crossing of frequency bands.

Along with Outgoing Internal Inter-Cell Handover Requests per Cell and OutgoingInternal Inter-Cell Handover Commands per Cell, the counters show the performance of

outgoing internal inter-cell handovers. Along with Incoming Internal Inter-CellHandover Measurement per Cell, the counters show the performance of internal inter-cell handovers.


− TCHF

− TCHH

The failure causes include the following:

− Channel unavailable

− Terrestrial resource request failure

− A-Interface Failure

− MSC Intervention

− Timer Expired


− Uplink quality


− Uplink strength

− Downlink strength− Timing advance

− Better cell

− Load



− OM intervention

− EDGE coverage

− Other causes

The crossing of frequency bands is of the following types:− 900/850 to 900/850

− 1800/1900 to 1800/1900

− 900/850 to 1800/1900

− 1800/1900 to 900/850

Trigger Point

Figure 12-16 and Figure 12-17 show the trigger points of the counters of Failed OutgoingInternal Inter-Cell Handovers per Cell (Excluding Directed Retry) and Failed Outgoing

Internal Inter-Cell Handovers per Cell (Directed Retry).






Figure 12-16 Trigger points of the counters of Failed Outgoing Internal Inter-Cell Handovers perCell (Excluding Directed Retry)

BTS1(CELL1) BSCMS

PHY INFO

HO DETECT

MS MSCBTS1(CELLO)

A

C

CHAN ACTIV

HO ACC

FIRST SABM

EST IND

CHAN ACTIV

ACK

HO CMD

MR FROM MS

HO CMP

HO PERFORMED

H

F

B

G

D

E

In the

outgoing

internalinter-cell

handover

procedure

I



12 Call Measurement




Figure 12-17 Trigger points of the counters of Failed Outgoing Internal Inter-Cell Handovers per Cell (Directed Retry)

BTS1(CELL1) BSCMS

UA EST IND（CM

SERV REQ）

MSBTS2(CELLO)

A

B

CHAN ACTIV

FIRSTSABM

FIRSTSABM

CHAN

ACTIV ACK

HO CMD

CHAN RED

CHAN REQ

IMM ASSCMD

CC

CR(CM

SERV REQ)

CMSERV

ACCEPT

SETUP

CALL

PROCEEDING

ASSIGNREQ

CHAN ACTIV

CHAN ACTIV ACK

UA

HO ACCPHY INFO

HO DETECT

EST IND

HO CMP

ASSIGNCMP

MSC

C

F

TIMEOUT

In the outgoing

internal i nter-cell

handover

procedure

D

E

J

G

A: Failed Outgoing Internal Inter-Cell Handovers (Channel Unavailable)

B: Failed Outgoing Internal Inter-Cell Handovers (Congestion)

C: Failed Outgoing Internal Inter-Cell Handovers (Terrestrial Resource Request Failed)

D: Failed Outgoing Internal Inter-Cell Handovers (A-Interface Failure)

E: Failed Outgoing Internal Inter-Cell Handovers (Clear Commands Sent by MSC)

F: Failed Outgoing Internal Inter-Cell Handovers (Timer Expired)

G: Failed Outgoing Internal Inter-Cell Handovers (Handover Causes)

H: Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels)

I: Failed Outgoing Internal Inter-Cell Handovers (Excluding Directed Retry)

J: Failed Outgoing Internal Inter-Cell Handovers (Directed Retry)

Failed Outgoing Internal Inter-Cell Handovers (Excluding Directed Retry)






As shown in Figure 12-16, in the outgoing internal inter-cell handover (excludingdirected retry) procedure, the measurement is triggered when the handover fails beforethe MS successfully accesses the target cell and before the handover completed timer

expires. The measurement is based on the channel type and the crossing of frequency bands.


− SDCCH

− TCHF

− TCHH


− 900/850 to 900/850

− 1800/1900 to 1800/1900

− 900/850 to 1800/1900

− 1800/1900 to 900/850

Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels,Excluding Directed Retry)

As shown in Figure 12-16, in the outgoing internal inter-cell handover procedure, theBSC sends an HO CMD message to the MS through the source cell and initiates a timerto wait for an HO CMP message. The measurement is triggered when the MS reconnects

to the old channel and sends an HO FAIL message on the old channel. The measurementis based on the failure cause.

The failure causes consist of the following:

− Abnormal release, unspecified

− Abnormal release, channel unacceptable

−

Abnormal release, timer expired− Abnormal release, no activity on the radio path

− Preemptive release

− Handover failed, timing advance out of range

− Channel mode unavailable

− Frequency unavailable

− Call already cleared

− Semantically incorrect message

− Invalid mandatory information

− Message type non-existent or not implemented

− Message type not compatible with protocol state

− Conditional IE error

− No cell allocation available

− Protocol error unspecified

− Other causes

Failed Outgoing Internal Inter-Cell Handovers (Directed Retry)

As shown in Figure 12-17, in the outgoing internal inter-cell handover (directed retry)

procedure, the measurement is triggered when the handover fails before the MSsuccessfully accesses the target cell and before the handover completed timer expires.The measurement is based on the crossing of frequency bands.




12 Call Measurement




− 900/850 to 900/850

− 1800/1900 to 1800/1900

− 900/850 to 1800/1900

− 1800/1900 to 900/850

Failed Outgoing Internal Inter-Cell Handovers (Channel Unavailable)

As shown in Figure 12-16 and Figure 12-17, in the outgoing internal inter-cell handover

(including directed retry) procedure, the measurement is triggered when the channelrequest fails and the failure cause is no channel available.

Failed Outgoing Internal Inter-Cell Handovers (Terrestrial Resource Request Failed)

As shown in Figure 12-16 and Figure 12-17, in the outgoing internal inter-cell handover(including directed retry) procedure, the measurement is triggered when the net-drivefails.

Failed Outgoing Internal Inter-Cell Handovers (A-Interface Failure)


(including directed retry) procedure, the measurement is triggered when an A interfacefailure message is received from the MSC.

Failed Outgoing Internal Inter-Cell Handovers (Clear Commands Sent by MSC)

As shown in Figure 12-16 and Figure 12-17, in the outgoing internal inter-cell handover(including directed retry) procedure, the measurement is triggered when a clearcommand is received from the MSC.

Failed Outgoing Internal Inter-Cell Handovers (Timer Expired)


(including directed retry) procedure, the measurement is triggered when the handovercompleted timer expires.

Failed Outgoing Internal Inter-Cell Handovers (Handover Causes)


(including directed retry) procedure, the measurement is triggered when the handoverfails due to abnormal factors. The measurement is based on handover causes.


− Uplink quality


− Uplink strength


− Timing advance

−

Better cell− Load



− OM intervention

− EDGE coverage

− Other causes

Failed Outgoing Internal Inter-Cell Handovers (Congestion)


(Including Directed Retry) procedure, the measurement is triggered when the channel






request fails because of the target cell congestion. The measurement is based on thecauses of congestion.

The causes of congestion consist of the following:

− Uplink quality


− Uplink strength


− Timing advance

− Better cell

− Load



− OM intervention

− Directed retry− Minimum timing advance

− Other causes

Formula

None.

12.12.5 Outgoing Internal Inter-Cell Handover Measurement perCell

Counter

Table 12-48 lists the counters of Outgoing Internal Inter-Cell Handover Measurement per Cell.

Table 12-48 Counters of Outgoing Internal Inter-Cell Handover Measurement per Cell

Number Counter

1 CH310: Outgoing Internal Inter-Cell Handover Requests

2 CH313: Successful Outgoing Internal Inter-Cell Handover

3 CH312: Failed Outgoing Internal Inter-Cell Handovers

4 TH313: Success Rate of Outgoing Internal Inter-Cell Handover

5 CH311: Outgoing Internal Inter-Cell Handover Commands

6 CH312C: Failed Outgoing Internal Inter-Cell Handovers (Timer Expired)

7 CH312D: Failed Outgoing Internal Inter-Cell Handovers (Reconnection toOld Channels)



12 Call Measurement




Meaning

None.

Trigger Point None.

Formula

Outgoing Internal Inter-Cell Handover Requests =

[Outgoing Internal Inter-Cell Handover Requests (SDCCH) (Excluding Directed Retry)(900/850-900/850)] +

[Outgoing Internal Inter-Cell Handover Requests (SDCCH) (Excluding Directed Retry)

(1800/1900-1800/1900)] +



[Outgoing Internal Inter-Cell Handover Requests (TCHF) (Excluding Directed Retry)

(900/850-900/850)] +

[Outgoing Internal Inter-Cell Handover Requests (TCHF) (Excluding Directed Retry)(1800/1900-1800/1900)] +

[Outgoing Internal Inter-Cell Handover Requests (TCHF) (Excluding Directed Retry)

(900/850-1800/1900)] +[Outgoing Internal Inter-Cell Handover Requests (TCHF) (Excluding Directed Retry)(1800/1900-900/850)] +

[Outgoing Internal Inter-Cell Handover Requests (TCHH) (Excluding Directed Retry)(900/850-900/850)] +

[Outgoing Internal Inter-Cell Handover Requests (TCHH) (Excluding Directed Retry)

(1800/1900-1800/1900)] +



[Outgoing Internal Inter-Cell Handover Requests (Directed Retry) (900/850-900/850)] +



[Outgoing Internal Inter-Cell Handover Requests (Directed Retry) (1800/1900-900/850)]

Successful Outgoing Internal Inter-Cell Handover =






[Outgoing Internal Inter-Cell Handover Requests] -[Failed Outgoing Internal Inter-CellHandovers]

Failed Outgoing Internal Inter-Cell Handovers =[Failed Outgoing Internal Inter-Cell Handovers (SDCCH) (Excluding Directed Retry)

(900/850-900/850)] +

[Failed Outgoing Internal Inter-Cell Handovers (SDCCH) (Excluding Directed Retry)(1800/1900-1800/1900)] +

[Failed Outgoing Internal Inter-Cell Handovers (SDCCH) (Excluding Directed Retry)

(900/850-1800/1900)] +

[Failed Outgoing Internal Inter-Cell Handovers (SDCCH) (Excluding Directed Retry)(1800/1900-900/850)] +

[Failed Outgoing Internal Inter-Cell Handovers (TCHF) (Excluding Directed Retry) (900/850-900/850)] +

[Failed Outgoing Internal Inter-Cell Handovers (TCHF) (Excluding Directed Retry)

(1800/1900-1800/1900)] +

[Failed Outgoing Internal Inter-Cell Handovers (TCHF) (Excluding Directed Retry) (900/850-1800/1900)] +

[Failed Outgoing Internal Inter-Cell Handovers (TCHF) (Excluding Directed Retry)

(1800/1900-900/850)] +

[Failed Outgoing Internal Inter-Cell Handovers (TCHH) (Excluding Directed Retry)(900/850-900/850)] +

[Failed Outgoing Internal Inter-Cell Handovers (TCHH) (Excluding Directed Retry)(1800/1900-1800/1900)] +

[Failed Outgoing Internal Inter-Cell Handovers (TCHH) (Excluding Directed Retry)

(900/850-1800/1900)] +

[Failed Outgoing Internal Inter-Cell Handovers (TCHH) (Excluding Directed Retry)

(1800/1900-900/850)] +

[Failed Outgoing Internal Inter-Cell Handovers (Directed Retry) (900/850-900/850)] +

[Failed Outgoing Internal Inter-Cell Handovers (Directed Retry) (1800/1900-1800/1900)] +

[Failed Outgoing Internal Inter-Cell Handovers (Directed Retry) (900/850-1800/1900)] +[Failed Outgoing Internal Inter-Cell Handovers (Directed Retry) (1800/1900-900/850)]

Success Rate of Outgoing Internal Inter-Cell Handover =

[Successful Outgoing Internal Inter-Cell Handover]*{100}/[Outgoing Internal Inter-CellHandover Requests]

Outgoing Internal Inter-Cell Handover Commands =



12 Call Measurement




[Outgoing Internal Inter-Cell Handover Commands (SDCCH) (Excluding Directed Retry)(900/850-900/850)] +

[Outgoing Internal Inter-Cell Handover Commands (SDCCH) (Excluding Directed Retry)

(1800/1900-1800/1900)] +

[Outgoing Internal Inter-Cell Handover Commands (SDCCH) (Excluding Directed Retry)

(900/850-1800/1900)] +

[Outgoing Internal Inter-Cell Handover Commands (SDCCH) (Excluding Directed Retry)(1800/1900-900/850)] +

[Outgoing Internal Inter-Cell Handover Commands (TCHF) (Excluding Directed Retry)(900/850-900/850)] +

[Outgoing Internal Inter-Cell Handover Commands (TCHF) (Excluding Directed Retry)

(1800/1900-1800/1900)] +


(900/850-1800/1900)] +


(1800/1900-900/850)] +

[Outgoing Internal Inter-Cell Handover Commands (TCHH) (Excluding Directed Retry)(900/850-900/850)] +


[Outgoing Internal Inter-Cell Handover Commands (TCHH) (Excluding Directed Retry)

(900/850-1800/1900)] +


[Outgoing Internal Inter-Cell Handover Commands (Directed Retry) (900/850-900/850)] +

[Outgoing Internal Inter-Cell Handover Commands (Directed Retry) (1800/1900-1800/1900)]+

[Outgoing Internal Inter-Cell Handover Commands (Directed Retry) (900/850-1800/1900)] +

[Outgoing Internal Inter-Cell Handover Commands (Directed Retry) (1800/1900-900/850)]

Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) =[Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (SDCCH) (ExcludingDirected Retry)] +

[Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (TCHF) (Signaling Channel)]

+

[Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (TCHH) (Signaling Channel)]+

[Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (TCHF) (Traffic Channel)] +

[Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (TCHH) (Traffic Channel)] +

[Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (Directed Retry)]






Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) =

[Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal

Release, Unspecified)] +

[Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (AbnormalRelease, Channel Unacceptable)] +

[Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (AbnormalRelease, Timer Expired)] +

[Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal

Release, No Activity on the Radio Path)] +

[Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (PreemptiveRelease)] +

[Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Handover

Failed, Timing Advance out of Range)] +

[Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (ChannelMode Unavailable)] +

[Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (FrequencyUnavailable)] +

[Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Call Already

Cleared)] +

[Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels)(Semantically Incorrect Message)] +

[Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Invalid

Mandatory Information)] +

[Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (MessageType Non-existent or Not Implemented)] +

[Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (MessageType Not Compatible with Protocol State)] +

[Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Conditional

IE Error)] +

[Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (No CellAllocation Available)] +

[Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (ProtocolError Unspecified)] +

[Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (OtherCauses)]



12 Call Measurement




12.13 Incoming External Inter-Cell HandoverMeasurement per Cell

12.13.1 OverviewAfter the BSC receives measurement reports from the MS, it uses the handover algorithm todecide whether a handover is required or not on the basis of the factors such as the cell load,

signal quality, signal interference, and measurement reports. If a handover is required and thesource cell (current cell) and the target cell are controlled by two BSCs, an external inter-cell

handover is initiated.

The incoming external inter-cell handover is part of the external inter-cell handover. It refersto the external inter-cell handover performed in the target cell.

In the following topics, the BSC where the source cell is located is called BSC1 and the BSC where the

target cell is located is called BSC2. The BTS where the source cell is located is called BTS1 and theBTS where the target cell is located is called BTS2

The external inter-cell handover procedure is as follows:

Step 1 The handover algorithm in BSC1 notifies BSC1 to initiate an external inter-cell handover

based on the factors such as the measurement reports received from the MS, current cell load,

and the cell load of the neighbor cell.

Step 2 BSC1 sends the MSC an HO RQD message, requesting the MSC of the target cell.

Step 3 Based on the target cell, the MSC finds BSC2 and sends an HO REQ message to BSC2.

Step 4 BSC2 requests for a traffic channel from the target cell. After the request succeeds, BSC2

sends a CHAN ACTIV message to the target cell. After receiving a CHAN ACTIV ACKmessage from the target cell, BSC2 requests for speech service resources.

Step 5 After the request succeeds, BSC2 sends the MSC an HO REQ ACK message to notify the

MSC that the target cell is ready for the MS access.

Step 6 The MSC sends an HO CMD message to BSC1 and BSC1 forwards this message to the MS.

This message is used to request the MS to access the target cell.

Step 7 The MS sends the target cell an HO ACC message to attempt to access the new cell. BTS2

sends an HO DETECT message to BSC2 and a PHY INFO message to the MS.

Step 8 The MS sends a FIRST SABM frame to BTS2. After receiving this frame, BTS2 sends an

EST IND message to BSC2 and returns a UA frame to the MS.

Step 9 After the MS accesses the target cell, it sends an HO CMP message to BSC2 and BSC2forwards this message to the MSC.

Step 10 The MSC sends a CLR CMD message to BSC1 and the BSC1 releases the terrestrial

resources in the source cell.

Step 11 BSC1 sends a CLR CMP message to the MSC.

----End

The measurement of the incoming external inter-cell handover is performed in the target cell.

Figure 12-18 shows the incoming external inter-cell handover.






Figure 12-18 Incoming external inter-cell handover

BTS1 BSC1MS

HO CMD

MSMSC BTS2

A

B

HO REQ ACK

MR FROM MS

HO RQD

HO REQ

CHAN ACTIV

CHAN

ACTIV ACK

HO DETECT

HO CMD

HO DETECT

EST IND

HO ACC

PHY INFO

FIRST SABM

UA

HO CMP

HO CMP

CLR CMD

CLR CMP

BSC2

A: Incoming external inter-cell handover requests

B: Incoming external inter-cell handover responses

Table 12-49 lists the counter classification of Incoming External Inter-Cell HandoverMeasurement per Cell.

Table 12-49 Counter classification of Incoming External Inter-Cell Handover Measurement perCell


Incoming External Inter-Cell Handover Requests per Cell 12.13.2

Incoming External Inter-Cell Handover Responses per Cell 12.13.3

Failed Incoming External Inter-Cell Handovers per Cell 12.13.4

Incoming External Inter-Cell Handover Detection Messages Received by BSC per Cell

12.13.5

Incoming External Inter-Cell Handover Analyzed Measurement per Cell 12.13.6



12 Call Measurement




12.13.2 Incoming External Inter-Cell Handover Requests per Cell

Counter

Table 12-50 lists the counters of Incoming External Inter-Cell Handover Requests per Cell.

Table 12-50 Counters of Incoming External Inter-Cell Handover Requests per Cell

Number Counter

1 H3400W: Incoming External Inter-Cell Handover Requests (SDCCH)(900/850-900/850)

2 H3400X: Incoming External Inter-Cell Handover Requests (SDCCH)

(1800/1900-1800/1900)

3 H3400Y: Incoming External Inter-Cell Handover Requests (SDCCH)

(900/850-1800/1900)

4 H3400Z: Incoming External Inter-Cell Handover Requests (SDCCH)(1800/1900-900/850)

5 H3409W: Incoming External Inter-Cell Handover Requests (TCH) (900/850-900/850)

6 H3409X: Incoming External Inter-Cell Handover Requests (TCH)(1800/1900-1800/1900)

7 H3409Y: Incoming External Inter-Cell Handover Requests (TCH) (900/850-1800/1900)

8 H3409Z: Incoming External Inter-Cell Handover Requests (TCH)(1800/1900-900/850)

9 H3401B: Incoming External Inter-Cell Handover TCH Requests (TCHFOnly)

10 H3401C: Incoming External Inter-Cell Handover TCH Requests (TCHHOnly)

11 H3401D: Incoming External Inter-Cell Handover TCH Requests (TCHFPreferred, Channel Type Unchangeable)

12 H3401E: Incoming External Inter-Cell Handover TCH Requests (TCHH

Preferred, Channel Type Unchangeable)

13 H3401G: Incoming External Inter-Cell Handover TCH Requests (TCHF

Preferred, Channel Type Changeable)

14 H3401H: Incoming External Inter-Cell Handover TCH Requests (TCHHPreferred, Channel Type Changeable)

15 H3401F: Incoming External Inter-Cell Handover TCH Requests (TCHF orTCHH, Channel Type Unchangeable)

16 H3401I: Incoming External Inter-Cell Handover TCH Requests (TCHF or

TCHH, Channel Type Changeable)






Meaning

The handover algorithm in BSC1 notifies BSC1 to initiate an inter-cell handover. If the source

cell and the target cell are controlled by two BSCs, an external inter-cell handover is initiated.

The measurement is performed in the target cell. The measurement is based on the channel

type, the crossing of frequency bands, and the TCH seizure type.

Along with Incoming External Inter-Cell Handover Responses per Cell and Failed Incoming

External Inter-Cell Handovers per Cell, the counters show the performance of incomingexternal inter-cell handovers. Along with Outgoing External Inter-Cell Handover

Measurement per Cell, the counters show the performance of external inter-cell handovers.


SDCCH

TCH


900/850 to 900/850

1800/1900 to 1800/1900

900/850 to 1800/1900

1800/1900 to 900/850

The TCH seizure is of the following types:

TCHF only

TCHH only

TCHF preferred, channel type unchangeable

TCHH preferred, channel type unchangeable

TCHF preferred, channel type changeable

TCHH Preferred, Channel Type Changeable

TCHF or TCHH, Channel Type Unchangeable

TCHF or TCHH, Channel Type Changeable

Trigger Point

As shown in Figure 12-18 (A), the measurement is triggered when BSC2 receives an HO

REQ message from the MSC. The measurement is based on the channel type, the crossing offrequency bands, and the TCH seizure type.

Formula

None.



12 Call Measurement




12.13.3 Incoming External Inter-Cell Handover Responses perCell

CounterTable 12-51 lists the counters of Incoming External Inter-Cell Handover Responses per Cell.

Table 12-51 Counters of Incoming External Inter-Cell Handover Responses per Cell

Number Counter

1 H3410W: Incoming External Inter-Cell Handover Responses (SDCCH)

(900/850-900/850)

2 H3410X: Incoming External Inter-Cell Handover Responses (SDCCH)(1800/1900-1800/1900)

3 H3410Y: Incoming External Inter-Cell Handover Responses (SDCCH)(900/850-1800/1900)

4 H3410Z: Incoming External Inter-Cell Handover Responses (SDCCH)(1800/1900-900/850)

5 H3417W: Incoming External Inter-Cell Handover Responses (TCHF)

(900/850-900/850)

6 H3417X: Incoming External Inter-Cell Handover Responses (TCHF)(1800/1900-1800/1900)

7 H3417Y: Incoming External Inter-Cell Handover Responses (TCHF) (900/850-

1800/1900)

8 H3417Z: Incoming External Inter-Cell Handover Responses (TCHF)

(1800/1900-900/850)

9 H3418W: Incoming External Inter-Cell Handover Responses (TCHH)

(900/850-900/850)

10 H3418X: Incoming External Inter-Cell Handover Responses (TCHH)(1800/1900-1800/1900)

11 H3418Y: Incoming External Inter-Cell Handover Responses (TCHH)

(900/850-1800/1900)

12 H3418Z: Incoming External Inter-Cell Handover Responses (TCHH)

(1800/1900-900/850)

Meaning

After BSC2 receives an HO REQ message, it requests for a channel from the target cell and

activates it. BSC2 requests for speech service resources. If the request succeeds, the BSC2returns an HO REQ ACK message to the MSC. The measurement is performed in the target

cell. The measurement is based on the channel type and the crossing of frequency bands.






Along with Incoming External Inter-Cell Handover Requests per Cell and Failed IncomingInternal Inter-Cell Handovers per Cell, the counters show the performance of incomingexternal inter-cell handovers. Along with Outgoing External Inter-Cell Handover

Measurement per Cell, the counters show the performance of external inter-cell handovers.


SDCCH

TCHF

TCHH


900/850 to 900/850

1800/1900 to 1800/1900

900/850 to 1800/1900

1800/1900 to 900/850

Trigger Point

As shown in Figure 12-18 (B), the measurement is triggered when BSC2 sends an HO REQ

ACK to the MSC. The measurement is based on the channel type and the crossing of

frequency bands.

Formula

None.

12.13.4 Failed Incoming External Inter-Cell Handovers per CellCounter

Table 12-52 lists the counters of Failed Incoming External Inter-Cell Handovers per Cell.

Table 12-52 Counters of Failed Incoming External Inter-Cell Handovers per Cell

Number Counter

1 H3420W: Failed Incoming External Inter-Cell Handovers (SDCCH)(900/850-900/850)

2 H3420X: Failed Incoming External Inter-Cell Handovers (SDCCH)(1800/1900-1800/1900)

3 H3420Y: Failed Incoming External Inter-Cell Handovers (SDCCH)(900/850-1800/1900)

4 H3420Z: Failed Incoming External Inter-Cell Handovers (SDCCH)(1800/1900-900/850)

5 H3429W: Failed Incoming External Inter-Cell Handovers (TCH) (900/850-

900/850)

6 H3429X: Failed Incoming External Inter-Cell Handovers (TCH) (1800/1900-

1800/1900)



12 Call Measurement




Number Counter

7 H3429Y: Failed Incoming External Inter-Cell Handovers (TCH) (900/850-

1800/1900)

8 H3429Z: Failed Incoming External Inter-Cell Handovers (TCH) (1800/1900-900/850)

9 H342I: Failed Incoming External Inter-Cell Handovers (Invalid Message)

10 H3420A: Failed Incoming External Inter-Cell Handovers (ChannelUnavailable) (SDCCH)

11 H3429A: Failed Incoming External Inter-Cell Handovers (ChannelUnavailable) (TCH)

12 H342E: Failed Incoming External Inter-Cell Handovers (CIC Unavailable)

13 H342F: Failed Incoming External Inter-Cell Handovers (CIC Allocated)

14 H342B: Failed Incoming External Inter-Cell Handovers (Terrestrial ResourceRequest Failed)

15 H342H: Failed Incoming External Inter-Cell Handovers (Clear CommandsSent by MSC)

16 CH342D: External Incoming Cell Handover Failures (Failed to Seize a New

Channel)

17 H3420C: Failed Incoming External Inter-Cell Handovers (Timer Expired)(SDCCH)

18 H3429Cb: Failed Incoming External Inter-Cell Handovers (Timer Expired)(TCH) (Signaling Channel)

19 H3429Ca: Failed Incoming External Inter-Cell Handovers (Timer Expired)(TCH) (Traffic Channel)

Meaning

In the incoming external inter-cell handover procedure, BSC2 measures the related counter

when receiving a message that causes a handover failure. The measurement is performed in

the target cell. The measurement is based on the channel type, the crossing of frequency bands,and the failure cause.

Along with Incoming External Inter-Cell Handover Requests per Cell and Incoming External

Inter-Cell Handover Responses per Cell, the counters show the performance of incomingexternal inter-cell handovers. Along with Outgoing External Inter-Cell HandoverMeasurement per Cell, the counters show the performance of external inter-cell handovers.


SDCCH

TCH (traffic channel or signaling channel)







900/850 to 900/850

1800/1900 to 1800/1900

900/850 to 1800/1900

1800/1900 to 900/850

The failure causes consist of the following:

Invalid message

Channel unavailable

CIC unavailable

CIC allocated



Seizure of a new channel failed

Timer expired

Trigger Point

Figure 12-19 shows the trigger points of the counters of Failed Incoming External Inter-Cell

Handovers per Cell.



12 Call Measurement




Figure 12-19 Trigger points of the counters of Failed Incoming External Inter-Cell Handovers perCell BSC

BTS1 BSC1MS

HO CMD

MSMSC BTS2

B

HO

REQ ACK

MR FROM MS

HO RQD

HO REQ

CHAN ACTIV

CHAN

ACTIV ACK

HO DETECTHO CMD

HO DETECT

EST IND

HO ACC

PHY INFO

FIRST SABM

UA

HO CMP

HO CMP

CLR CMD

CLR CMP

BSC2

In the

incoming

external

inter-cell

handover

procedure

A

E

C

D

TIME OUT

F

A: Failed Incoming External Inter-Cell Handovers

B: Failed Incoming External Inter-Cell Handovers (Invalid Message)

C: Failed Incoming External Inter-Cell Handovers (Channel Unavailable)

D: Failed Incoming External Inter-Cell Handovers (Terrestrial Resource Request Failed, CIC

Unavailable, CIC Allocated)

E: Failed Incoming External Inter-Cell Handovers (Clear Commands Sent by MSC), External

Incoming Cell Handover Failures (Failed to Seize a New Channel)

F: Failed Incoming External Inter-Cell Handovers (Timer Expired)


Failed Incoming External Inter-Cell Handovers (Invalid Message)

BSC2 receives an HO REQ message from the MSC and decodes it. The measurement istriggered when BSC2 detects that the message is invalid.

Failed Incoming External Inter-Cell Handovers (Channel Unavailable)

BSC2 receives an HO REQ message from the MSC and decodes it. BSC2 then requestsfor a channel from the target cell. The measurement is triggered when the target cell

returns a request failure message with the cause of channel unavailable. The

measurement is based on the channel type.







− SDCCH

− TCH

Failed Incoming External Inter-Cell Handovers (Terrestrial Resource Request Failed,

CIC Unavailable, CIC Allocated)

BSC2 receives an HO REQ message from the MSC and decodes it. BSC2 then requests

for a channel from the target cell. If the request succeeds, BSC2 sends a CHAN ACTIVmessage to the target cell. After receiving a CHAN ACTIV ACK message, BSC2requests for the terrestrial resources and terrestrial link resources about speech services.

− If the request for terrestrial resources fails, the measurement of Failed IncomingExternal Inter-Cell Handovers (Terrestrial Resource Request Failed) is triggered.

− The CIC resources on the A interface is a key factor of the terrestrial resource request.

The MSC sends BSC2 an HO REQ message that carries the CIC. If BSC2 detects

that the CIC is unavailable, the measurement of Failed Incoming External Inter-CellHandovers (Terrestrial Resource Request Failed, CIC Unavailable is triggered.

− If BSC2 detects that the CIC is already allocated, the measurement of Failed

Incoming External Inter-Cell Handovers (Terrestrial Resource Request Failed, CICAllocated) is triggered.

Failed Incoming External Inter-Cell Handovers (Timer Expired)

In the incoming external inter-cell handover procedure, the measurement is triggered

when BSC2 receives a TIME OUT message. The measurement is based on the channeltype and the TCH service type.


− SDCCH

− TCH

The TCH is of the following service types:− TCH service channel

− TCH signaling channel

Failed Incoming External Inter-Cell Handovers (Clear Commands Sent by MSC)

In the incoming external inter-cell handover procedure, the measurement is triggeredwhen BSC2 receives a CLR CMD message from the MSC.

External Incoming Cell Handover Failures (Failed to Seize a New Channel)

As shown in point E in Figure 12-19, during an external incoming cell handover procedure, this handover fails when BSC2 receives the CLR CMD from the MSC. If the

cause for the clearance is radio interface failure, the measurement of this counter is

triggered. Failed Incoming External Inter-Cell Handovers

In the incoming external inter-cell handover procedure, the measurement is triggeredwhen the handover fails.

Formula

None.



12 Call Measurement




12.13.5 Incoming External Inter-Cell Handover DetectionMessages Received by BSC per Cell

CounterTable 12-53 lists the counters of Incoming External Inter-Cell Handover Detection Messages

Received by BSC per Cell.

Table 12-53 Counters of Incoming External Inter-Cell Handover Detection Messages Received byBSC per Cell

Number Counter

1 H3440: Incoming External Inter-Cell Handover Detection Messages Received

by BSC (SDCCH)

2 H3447: Incoming External Inter-Cell Handover Detection Messages Received by BSC (TCHF)

3 H3448: Incoming External Inter-Cell Handover Detection Messages Received by BSC (TCHH)

Meaning

The counters measure the number of times BSC2 receives an HO DETECT message. Themeasurement is performed in the target cell.


SDCCH

TCHF

TCHH

Trigger Point

As shown in Figure 12-19, the measurement is triggered when BSC2 receives an HO

DETECT message. The measurement is based on the channel type.

Formula None.






12.13.6 Incoming External Inter-Cell Handover AnalyzedMeasurement per Cell

CounterTable 12-54 lists the counters of Incoming External Inter-Cell Handover AnalyzedMeasurement per Cell.

Table 12-54 Counters of Incoming External Inter-Cell Handover Analyzed Measurement per Cell

Number Counter

1 CH340: Incoming External Inter-Cell Handover Requests

2 CH343: Successful Incoming External Inter-Cell Handovers

3 CH341: Incoming External Inter-Cell Handover Responses

4 TH343: Success Rate of Incoming External Inter-Cell Handover

5 CH3401: Incoming External Inter-Cell Handover TCH Requests

6 CH344: Incoming External Inter-Cell Handover Detection Messages Received by BSC

7 CH342: Failed Incoming External Inter-Cell Handovers

8 CH342C: Failed Incoming External Inter-Cell Handovers (Timer Expired)

9 CH346: Incoming External Inter-Cell Handover Requests(Better Cell)

Meaning

None.

Trigger Point

None.

Formula

Incoming External Inter-Cell Handover Requests =

[Incoming External Inter-Cell Handover Requests (SDCCH) (900/850-900/850)] +




[Incoming External Inter-Cell Handover Requests (TCH) (900/850-900/850)] +





12 Call Measurement




[Incoming External Inter-Cell Handover Requests (TCH) (1800/1900-900/850)]

Successful Incoming External Inter-Cell Handovers =

([Incoming External Inter-Cell Handover Requests (SDCCH) (900/850-900/850)] +







[Incoming External Inter-Cell Handover Requests (TCH) (1800/1900-900/850)])

-([Failed Incoming External Inter-Cell Handovers (SDCCH) (900/850-900/850)] +

[Failed Incoming External Inter-Cell Handovers (SDCCH) (1800/1900-1800/1900)] +



[Failed Incoming External Inter-Cell Handovers (TCH) (900/850-900/850)] +



[Failed Incoming External Inter-Cell Handovers (TCH) (1800/1900-900/850)])

Incoming External Inter-Cell Handover Responses =

[Incoming External Inter-Cell Handover Responses (SDCCH) (900/850-900/850)] +




[Incoming External Inter-Cell Handover Responses (TCHF) (900/850-900/850)] +




[Incoming External Inter-Cell Handover Responses (TCHH) (900/850-900/850)] +



[Incoming External Inter-Cell Handover Responses (TCHH) (1800/1900-900/850)]






Success Rate of Incoming External Inter-Cell Handover =

[Successful Incoming External Inter-Cell Handovers]*{100}/[Incoming External Inter-Cell

Handover Requests]

Incoming External Inter-Cell Handover TCH Requests =

[Incoming External Inter-Cell Handover TCH Requests (TCHF Only)] +

[Incoming External Inter-Cell Handover TCH Requests (TCHH Only)] +

[Incoming External Inter-Cell Handover TCH Requests (TCHF Preferred, Channel TypeUnchangeable)] +

[Incoming External Inter-Cell Handover TCH Requests (TCHH Preferred, Channel Type

Unchangeable)] +

[Incoming External Inter-Cell Handover TCH Requests (TCHF Preferred, Channel TypeChangeable)] +

[Incoming External Inter-Cell Handover TCH Requests (TCHH Preferred, Channel Type

Changeable)] +

[Incoming External Inter-Cell Handover TCH Requests (TCHF or TCHH, Channel TypeUnchangeable)] +

[Incoming External Inter-Cell Handover TCH Requests (TCHF or TCHH, Channel TypeChangeable)]

Incoming External Inter-Cell Handover Detection Messages Received by BSC =

[Incoming External Inter-Cell Handover Detection Messages Received by BSC (SDCCH)] +

[Incoming External Inter-Cell Handover Detection Messages Received by BSC (TCHF)] +

[Incoming External Inter-Cell Handover Detection Messages Received by BSC (TCHH)]

Failed Incoming External Inter-Cell Handovers =








[Failed Incoming External Inter-Cell Handovers (TCH) (1800/1900-900/850)]



12 Call Measurement




Failed Incoming External Inter-Cell Handovers (Timer Expired) =

[Failed Incoming External Inter-Cell Handovers (Timer Expired) (SDCCH)] +

[Failed Incoming External Inter-Cell Handovers (Timer Expired) (TCH) (Signaling Channel)]

+[Failed Incoming External Inter-Cell Handovers (Timer Expired) (TCH) (Traffic Channel)]

12.14 Outgoing External Inter-Cell HandoverMeasurement per Cell

12.14.1 Overview

Outgoing External Inter-Cell Handover Measurement per Cell can be classified into Outgoing

External Inter-Cell Handover (Excluding Directed Retry) and Outgoing External Inter-CellHandover (Directed Retry).

Outgoing external inter-cell handover (excluding directed retry)

As shown in Figure 12-20, after the BSC receives measurement reports from the MS, it uses

the handover algorithm to decide whether a handover is required or not. If a handover is

required and the source cell (the current cell where the MS is located) and the target cell (thecell where the MS is located after the handover) are controlled by two BSCs, an externalinter-cell handover is initiated.

The measurement of outgoing external inter-cell handover (excluding directed retry) is performed in the source cell.

The procedure of the outgoing external inter-cell handover (excluding directed retry) is as

follows:

Step 1 BSC1 initiates an external inter-cell handover based on the handover algorithm.

Step 2 BSC1 sends an HO RQD message to the MSC.

Step 3 Based on the HO RQD message and the relation between the cell and the BSC, the MSC findsBSC2 and sends an HO REQ message to BSC2.

Step 4 BSC2 requests for a traffic channel from the target cell. After the request succeeds, BSC2sends a CHAN ACTIV message to the target cell. After receiving a CHAN ACTIV ACKmessage from the target cell, BSC2 requests for speech service resources. After the request

succeeds, BSC2 sends the MSC an HO REQ ACK message to notify the MSC that the targetcell is ready for the MS access.



Step 6 The MS sends the target cell an HO ACC message to attempt to access the target cell. BTS2


Step 7 The MS sends a FIRST SABM frame to BTS2. After receiving this frame, BTS2 sends an

EST IND message to BSC2 and returns a UA frame to the MS.

Step 8 After the MS accesses the target cell, it sends an HO CMP message to BSC2 and BSC2

forwards this message to the MSC.






Step 9 The MSC sends a CLR CMD message to BSC1 and the BSC1 releases the terrestrialresources in the source cell.


----End

Figure 12-20 Outgoing external inter-cell handover (excluding directed retry)

BTS1 BSC1MS

HO CMD

MSMSC BTS2

A

HO REQ ACK

MR FROM MS

HO RQD

HO REQ

CHAN ACTIV

CHAN

ACTIV ACK

HO DETECT

HO CMD

HO DETECT

EST IND

HO ACC

PHY INFO

FIRST SABM

UA

HO CMP

HO CMP

CLR CMD

CLR CMP

BSC2

B

A: Outgoing external inter-cell handover request (excluding directed retry)

B: Outgoing external inter-cell handover response (excluding directed retry)

Outgoing external inter-cell handover (directed retry)


Step 1 As shown in Figure 12-21, the MS sends a CHAN RQD message to BTS1 and BTS1

forwards it to BSC1.

Step 2 BSC1 requests for a signaling channel from the source cell. If the request succeeds, BSC1sends a CHAN ACTIV message to the source cell. After receiving a CHAN ACTIV ACKmessage from the source cell, BSC1 sends an IMM ASS CMD to the MS through the source

cell.

Step 3 The MS sends a FIRST ASBM frame to BTS1 and BTS1 returns a UA frame. After receiving

the FIRST ASBM frame, BTS1 sends an EST IND message to BSC1.

Step 4 BSC1 extracts the CM SERV REQ message carried in the EST IND message, encapsulates itinto a connection request (CR) message, and sends the CR message to the MSC.



12 Call Measurement




Step 5 The MSC returns a Connection Confirm (CC) message. The MM connection between the MSand the MSC is established.

Step 6 After the transmission of the CM SERV ACCEPT, SETUP, and CALL PROCEEDINGmessages, the MSC sends an ASSIGN REQ message to BSC1.

Step 7 BSC1 selects a kind of assignment procedure (normal assignment procedure, mode modify

procedure, directed retry procedure) based on the load of the source cell.

Step 8 If the subsequent services are unavailable or the subsequent services affect the existing

services because the cell load is too high, BSC1 selects the directed retry procedure. If thesource cell and the target cell are controlled by two BSCs, the directed retry is performed

through an external inter-cell handover procedure. If the measurement is performed in thesource cell, the outgoing external inter-cell handover procedure is initiated.

Step 9 BSC1 sends an HO RQD message to the MSC to initiate an external inter-cell handover.

Step 10 Based on the HO RQD message and the relation between the cell and the BSC, the MSC finds

BSC2 and sends an HO REQ message to BSC2.

Step 11 BSC2 requests for a channel from the target cell. After the request succeeds, BSC2 sends aCHAN ACTIV message to the target cell. After receiving a CHAN ACTIV ACK message

from the target cell, BSC2 requests for speech service resources. After the request succeeds,BSC2 sends the MSC an HO REQ ACK message to notify the MSC that the target cell is

ready for the MS access.



Step 13 The MS sends the target cell an HO ACC message to attempt to access the target cell. BTS2


Step 14 BSC2 sends an HO DETECT message to the MSC. The MS sends a FIRST SABM frame toBTS2. After receiving this frame, BTS2 returns a UA frame to the MS and sends an EST INDmessage to BSC2.

Step 15 The MS sends an HO CMP message to BSC2 and BSC2 forwards this message to the MSC.

Step 16 The MSC sends a CLR CMD message to BSC1 and the BSC1 releases the terrestrialresources in the source cell.


----End






Figure 12-21 Outgoing external inter-cell handover (Directed Retry)

BTS1(CELL1) BSC1MS

UA EST IND（CM

SERV REQ）

MSBTS2(CELLO)

A

B

CHAN ACTIV

FIRST SABM

FIRST SABM

CHAN

ACTIV ACK

HO CMD

CHAN RED

CHAN REQ

IMM

ASS CMD

CC

CR(CM

SERV REQ)

CM SERV

ACCEPT

SETUP

CALL

PROCEEDING

ASSIGN REQ

CHAN ACTIV

CHAN

ACTIV ACK

UA

HO ACC

PHY INFO

HO DETECT

EST IND

HO CMP

MSC BSC2

HO RQD

HO REQ

HO REQ ACK

HO CMD

HO DETECT

HO CMP

CLR CMD

CLR CMP

A: Outgoing external inter-cell handover requests (Directed Retry)

B: Outgoing external inter-cell handover responses (Directed Retry)

Table 12-55 lists the counter classification of Outgoing External Inter-Cell Handover




12 Call Measurement




Table 12-55 Counter classification of outgoing External Inter-Cell Handover Measurement perCell


Outgoing External Inter-Cell Handover Requests per Cell 12.14.2

Outgoing External Inter-Cell Handover Commands per Cell 12.14.3

Failed Outgoing External Inter-Cell Handovers per Cell 12.14.4

Outgoing External Inter-Cell Handover Analyzed Measurement per Cell 12.14.5

12.14.2 Outgoing External Inter-Cell Handover Requests per Cell

CounterTable 12-56 lists the counters of Outgoing External Inter-Cell Handover Requests per Cell


Table 12-56 Counters of Outgoing External Inter-Cell Handover Requests per Cell (ExcludingDirected Retry)

Number Counter

1 H3300W: Outgoing External Inter-Cell Handover Requests (SDCCH)(Excluding Directed Retry) (900/850-900/850)

2 H3300X: Outgoing External Inter-Cell Handover Requests (SDCCH)(Excluding Directed Retry) (1800/1900-1800/1900)

3 H3300Y: Outgoing External Inter-Cell Handover Requests (SDCCH)(Excluding Directed Retry) (900/850-1800/1900)

4 H3300Z: Outgoing External Inter-Cell Handover Requests (SDCCH)(Excluding Directed Retry) (1800/1900-900/850)

5 H3307W: Outgoing External Inter-Cell Handover Requests (TCHF) (Excluding

Directed Retry) (900/850-900/850)

6 H3307X: Outgoing External Inter-Cell Handover Requests (TCHF) (ExcludingDirected Retry) (1800/1900-1800/1900)

7 H3307Y: Outgoing External Inter-Cell Handover Requests (TCHF) (ExcludingDirected Retry) (900/850-1800/1900)

8 H3307Z: Outgoing External Inter-Cell Handover Requests (TCHF) (Excluding

Directed Retry) (1800/1900-900/850)

9 H3308W: Outgoing External Inter-Cell Handover Requests (TCHH)


10 H3308X: Outgoing External Inter-Cell Handover Requests (TCHH) (ExcludingDirected Retry) (1800/1900-1800/1900)






Number Counter

11 H3308Y: Outgoing External Inter-Cell Handover Requests (TCHH) (Excluding

Directed Retry) (900/850-1800/1900)

12 H3308Z: Outgoing External Inter-Cell Handover Requests (TCHH) (ExcludingDirected Retry) (1800/1900-900/850)

13 H330A: Outgoing External Inter-Cell Handover Requests (Uplink Quality)

14 H330B: Outgoing External Inter-Cell Handover Requests (Downlink Quality)

15 H330C: Outgoing External Inter-Cell Handover Requests (Uplink Strength)

16 H330D: Outgoing External Inter-Cell Handover Requests (Downlink Strength)

17 H330E: Outgoing External Inter-Cell Handover Requests (Timing Advance)

18 H330F: Outgoing External Inter-Cell Handover Requests (Better Cell)

19 H330G: Outgoing External Inter-Cell Handover Requests (Load)

20 H330H: Outgoing External Inter-Cell Handover Requests (Rapid Level Drop)

21 H330I: Outgoing External Inter-Cell Handover Requests (MSC Intervention)

22 H330J: Outgoing External Inter-Cell Handover Requests (OM Intervention)

23 H330L: Outgoing External Inter-Cell Handover Requests (Other Causes)

Table 12-57 lists the counters of Outgoing External Inter-Cell Handover Requests per Cell

(Directed Retry).

Table 12-57 Counters of Outgoing External Inter-Cell Handover Requests per Cell (DirectedRetry)

Number Counter

1 H3301W: Outgoing External Inter-Cell Handover Requests (Directed Retry)(900/850-900/850)

2 H3301X: Outgoing External Inter-Cell Handover Requests (Directed Retry)(1800/1900-1800/1900)

3 H3301Y: Outgoing External Inter-Cell Handover Requests (Directed Retry)(900/850-1800/1900)

4 H3301Z: Outgoing External Inter-Cell Handover Requests (Directed Retry)

(1800/1900-900/850)

Table 12-58 lists the counters of Outgoing External Inter-Cell Handover Requests per Cell

(Including Directed Retry).



12 Call Measurement




Table 12-58 Counters of Outgoing External Inter-Cell Handover Requests per Cell (IncludingDirected Retry)

Number Counter

1 H3303: Outgoing External Inter-Cell Handover Requests (DifferentSignaling Points)

Meaning


Outgoing External Inter-Cell Handover Requests (Excluding Directed Retry)

The counters measure the number of outgoing external inter-cell handover requestsinitiated by the handover algorithm. The measurement is performed in the source cell.

The measurement is based on the channel type, different signaling points, and thehandover cause.

Along with Outgoing External Inter-Cell Handover Commands per Cell and Failed

Outgoing External Inter-Cell Handovers per Cell, the counters show the performance ofoutgoing external inter-cell handover. Along with Incoming External Inter-CellHandover Measurement per Cell, the counters show the performance of external inter-cell handovers.


− SDCCH

− TCHF

− TCHH

The handover between different signaling points in a BSC is also called outgoingexternal inter-cell handover.


− Uplink quality


− Uplink strength


− Timing advance

− Better cell

−

Load− Rapid level drop


− OM intervention

− EDGE coverage

− Other causes

Outgoing External Inter-Cell Handover Requests (Directed Retry)

The counters measure the number of outgoing external inter-cell handover requests in thedirected retry procedure.

Along with Outgoing External Inter-Cell Handover Commands per Cell and Failed

Outgoing External Inter-Cell Handovers per Cell, the counters show the performance of






outgoing external inter-cell handovers. Along with Incoming External Inter-CellHandover Measurement per Cell, the counters show the performance of external inter-cell handovers.

Trigger PointThe trigger points of the counters are as follows:

Outgoing External Inter-Cell Handover Requests (Excluding Directed Retry)

As shown in Figure 12-20 (A), the measurement is triggered when the BSC decides toinitiate an outgoing external inter-cell handover based on the measurement reports. The

measurement is based on the channel type, different signaling points, and the handovercause.

Outgoing External Inter-Cell Handover Requests (Directed Retry)

As shown in Figure 12-21 (A), the measurement is triggered when the BSC initiates adirected retry procedure.

Formula

None.

12.14.3 Outgoing External Inter-Cell Handover Commands perCell

Counter

Table 12-59 lists the counters of Outgoing External Inter-Cell Handover Commands per Cell


Table 12-59 Counters of Outgoing External Inter-Cell Handover Commands per Cell (ExcludingDirected Retry)

Number Counter

1 H3310W: Outgoing External Inter-Cell Handover Commands (SDCCH)(Excluding Directed Retry) (900/850-900/850)

2 H3310X: Outgoing External Inter-Cell Handover Commands (SDCCH)(Excluding Directed Retry) (1800/1900-1800/1900)

3 H3310Y: Outgoing External Inter-Cell Handover Commands (SDCCH)(Excluding Directed Retry) (900/850-1800/1900)

4 H3310Z: Outgoing External Inter-Cell Handover Commands (SDCCH)(Excluding Directed Retry) (1800/1900-900/850)

5 H3317W: Outgoing External Inter-Cell Handover Commands (TCHF)(Excluding Directed Retry) (900/850-900/850)

6 H3317X: Outgoing External Inter-Cell Handover Commands (TCHF)(Excluding Directed Retry) (1800/1900-1800/1900)



12 Call Measurement




Number Counter

7 H3317Y: Outgoing External Inter-Cell Handover Commands (TCHF)


8 H3317Z: Outgoing External Inter-Cell Handover Commands (TCHF)(Excluding Directed Retry) (1800/1900-900/850)

9 H3318W: Outgoing External Inter-Cell Handover Commands (TCHH)(Excluding Directed Retry) (900/850-900/850)

10 H3318X: Outgoing External Inter-Cell Handover Commands (TCHH)


11 H3318Y: Outgoing External Inter-Cell Handover Commands (TCHH)(Excluding Directed Retry) (900/850-1800/1900)

12 H3318Z: Outgoing External Inter-Cell Handover Commands (TCHH)


13 H331A: Outgoing External Inter-Cell Handover Commands (Uplink Quality)

14 H331B: Outgoing External Inter-Cell Handover Commands (DownlinkQuality)

15 H331C: Outgoing External Inter-Cell Handover Commands (Uplink Strength)

16 H331D: Outgoing External Inter-Cell Handover Commands (DownlinkStrength)

17 H331E: Outgoing External Inter-Cell Handover Commands (Timing Advance)

18 H331F: Outgoing External Inter-Cell Handover Commands (Better Cell)

19 H331G: Outgoing External Inter-Cell Handover Commands (Load)

20 H331H: Outgoing External Inter-Cell Handover Commands (Rapid Level

Drop)

21 H331I: Outgoing External Inter-Cell Handover Commands (MSC Intervention)

22 H331J: Outgoing External Inter-Cell Handover Commands (OM Intervention)

23 H331L: Outgoing External Inter-Cell Handover Commands (Other Causes)

Table 12-60 lists the counters of Outgoing External Inter-Cell Handover Commands per Cell(Directed Retry).

Table 12-60 Counters of Outgoing External Inter-Cell Handover Commands per Cell (DirectedRetry)

Number Counter

1 H3311W: Outgoing External Inter-Cell Handover Commands (Directed Retry)

(900/850-900/850)

2 H3311X: Outgoing External Inter-Cell Handover Commands (Directed Retry)

(1800/1900-1800/1900)






Number Counter

3 H3311Y: Outgoing External Inter-Cell Handover Commands (Directed Retry)

(900/850-1800/1900)

4 H3311Z: Outgoing External Inter-Cell Handover Commands (Directed Retry)(1800/1900-900/850)

Table 12-61 lists the counters of Outgoing External Inter-Cell Handover Commands per Cell

(Including Directed Retry).

Table 12-61 Counters of Outgoing External Inter-Cell Handover Commands per Cell (Including

Directed Retry)

Number Counter

1 H3313: Outgoing External Inter-Cell Handover Commands (DifferentSignaling Points)

Meaning


Outgoing External Inter-Cell Handover Commands (Excluding Directed Retry)

The counters measure the number of times BSC1 sends an HO CMD message to the MS.

The measurement is based on the crossing of frequency bands, the channel type, differentsignaling points, and the handover cause.

Along with Outgoing External Inter-Cell Handover Requests per Cell and FailedOutgoing External Inter-Cell Handovers per Cell, the counters show the performance of



− 900/850 to 900/850

− 1800/1900 to 1800/1900

− 900/850 to 1800/1900

− 1800/1900 to 900/850


− SDCCH

− TCHF

− TCHH



− Uplink quality




12 Call Measurement




− Uplink strength


− Timing advance

− Better cell

− Load



− OM intervention

− EDGE coverage

− Other causes

Outgoing External Inter-Cell Handover Commands (Directed Retry)

In the directed retry procedure, the counters measure the number of times the BSC sends

an HO CMD message to the MS. The measurement is based on the crossing of frequency

bands and different signaling points.Along with Outgoing External Inter-Cell Handover Requests per Cell and FailedOutgoing External Inter-Cell Handovers per Cell, the counters show the performance of



− 900/850 to 900/850

− 1800/1900 to 1800/1900

− 900/850 to 1800/1900

− 1800/1900 to 900/850


Trigger Point


Outgoing External Inter-Cell Handover Commands (Excluding Directed Retry)

As shown in Figure 12-20 (B), in the outgoing external inter-cell (excluding directedretry) procedure, the measurement is triggered when the BSC sends an HO CMDmessage to the MS. The measurement is performed in the source cell. The measurement

is based on the crossing of frequency bands, the channel type, different signaling points,and the handover cause.

Outgoing External Inter-Cell Handover Commands (Directed Retry)

As shown in Figure 12-21 (B), in the outgoing external inter-cell handover (directed

retry) procedure, the measurement is triggered when the BSC sends an HO CMDmessage to the MS. The measurement is performed in the source cell. The measurementis based on the crossing of frequency bands and different signaling points.

Formula

None.






12.14.4 Failed Outgoing External Inter-Cell Handovers per Cell

Counter

Table 12-62 lists the counters of Failed Outgoing External Inter-Cell Handovers per Cell(Excluding Directed Retry).

Table 12-62 Counters of Failed Outgoing External Inter-Cell Handovers per Cell (Excluding

Directed Retry)

Number Counter

1 H3320W: Failed Outgoing External Inter-Cell Handovers (SDCCH) (900/850-900/850)

2 H3320X: Failed Outgoing External Inter-Cell Handovers (SDCCH)

(1800/1900-1800/1900)

3 H3320Y: Failed Outgoing External Inter-Cell Handovers (SDCCH) (900/850-1800/1900)

4 H3320Z: Failed Outgoing External Inter-Cell Handovers (SDCCH)(1800/1900-900/850)

5 H3327W: Failed Outgoing External Inter-Cell Handovers (TCHF) (900/850-

900/850)

6 H3327X: Failed Outgoing External Inter-Cell Handovers (TCHF) (1800/1900-

1800/1900)

7 H3327Y: Failed Outgoing External Inter-Cell Handovers (TCHF) (900/850-1800/1900)

8 H3327Z: Failed Outgoing External Inter-Cell Handovers (TCHF) (1800/1900-900/850)

9 H3328W: Failed Outgoing External Inter-Cell Handovers (TCHH) (900/850-

900/850)

10 H3328X: Failed Outgoing External Inter-Cell Handovers (TCHH) (1800/1900-

1800/1900)

11 H3328Y: Failed Outgoing External Inter-Cell Handovers (TCHH) (900/850-1800/1900)

12 H3328Z: Failed Outgoing External Inter-Cell Handovers (TCHH) (1800/1900-900/850)

13 H3322A: Failed Outgoing External Inter-Cell Handovers (Uplink Quality)

14 H3322B: Failed Outgoing External Inter-Cell Handovers (Downlink Quality)

15 H3322C: Failed Outgoing External Inter-Cell Handovers (Uplink Strength)

16 H3322D: Failed Outgoing External Inter-Cell Handovers (Downlink Strength)

17 H3322E: Failed Outgoing External Inter-Cell Handovers (Timing Advance)

18 H3322F: Failed Outgoing External Inter-Cell Handovers (Better Cell)



12 Call Measurement




Number Counter

19 H3322G: Failed Outgoing External Inter-Cell Handovers (Load)

20 H3322H: Failed Outgoing External Inter-Cell Handovers (Rapid Level Drop)

21 H3322I: Failed Outgoing External Inter-Cell Handovers (MSC Intervention)

22 H3322J: Failed Outgoing External Inter-Cell Handovers (OM Intervention)

23 H3322L: Failed Outgoing External Inter-Cell Handovers (Other Causes)

24 H332Da: Failed Outgoing External Inter-Cell Handovers (Reconnection to OldChannels) (Abnormal Release, Unspecified)

25 H332Db: Failed Outgoing External Inter-Cell Handovers (Reconnection to OldChannels) (Abnormal Release, Channel Unacceptable)

26 H332Dc: Failed Outgoing External Inter-Cell Handovers (Reconnection to Old

Channels) (Abnormal Release, Timer Expired)

27 H332Dd: Failed Outgoing External Inter-Cell Handovers (Reconnection to OldChannels) (Abnormal Release, No Activity on the Radio Path)

28 H332De: Failed Outgoing External Inter-Cell Handovers (Reconnection to Old

Channels) (Preemptive Release)

29 H332Df: Failed Outgoing External Inter-Cell Handovers (Reconnection to OldChannels) (Handover Failed, Timing Advance out of Range)

30 H332Dg: Failed Outgoing External Inter-Cell Handovers (Reconnection to OldChannels) (Channel Mode Unavailable)

31 H332Dh: Failed Outgoing External Inter-Cell Handovers (Reconnection to Old

Channels) (Frequency Unavailable)

32 H332Di: Failed Outgoing External Inter-Cell Handovers (Reconnection to Old

Channels) (Call Already Cleared)

33 H332Dj: Failed Outgoing External Inter-Cell Handovers (Reconnection to OldChannels) (Semantically Incorrect Message)

34 H332Dk: Failed Outgoing External Inter-Cell Handovers (Reconnection to Old

Channels) (Invalid Mandatory Information)

35 H332Dl: Failed Outgoing External Inter-Cell Handovers (Reconnection to Old

Channels) (Message Type Non-existent or Not Implemented)

36 H332Dm: Failed Outgoing External Inter-Cell Handovers (Reconnection to

Old Channels) (Message Type Not Compatible with Protocol State)

37 H332Dn: Failed Outgoing External Inter-Cell Handovers (Reconnection to OldChannels) (Conditional IE Error)

38 H332Do: Failed Outgoing External Inter-Cell Handovers (Reconnection to Old

Channels) (No Cell Allocation Available)

39 H332Dp: Failed Outgoing External Inter-Cell Handovers (Reconnection to Old

Channels) (Protocol Error Unspecified)






Number Counter

40 H332Dq: Failed Outgoing External Inter-Cell Handovers (Reconnection to Old

Channels) (Other Causes)

41 H3320L: Failed Outgoing External Inter-Cell Handovers (T7 Expiry)(SDCCH)

42 H3327Lb: Failed Outgoing External Inter-Cell Handovers (T7 Expiry) (TCHF)(Signaling Channel)

43 H3328Lb: Failed Outgoing External Inter-Cell Handovers (T7 Expiry) (TCHH)

(Signaling Channel)

44 H3320C: Failed Outgoing External Inter-Cell Handovers (T8 Expiry)(SDCCH) (Excluding Directed Retry)

45 H3327Cb: Failed Outgoing External Inter-Cell Handovers (T8 Expiry) (TCHF)

(Signaling Channel)

46 H3328Cb: Failed Outgoing External Inter-Cell Handovers (T8 Expiry) (TCHH)(Signaling Channel)

Table 12-63 lists the counters of Failed Outgoing External Inter-Cell Handovers per Cell(Directed Retry).

Table 12-63 Counters of Failed Outgoing External Inter-Cell Handovers per Cell (Directed Retry)

Number Counter

1 H3321W: Failed Outgoing External Inter-Cell Handovers (Directed Retry)(900/850-900/850)

2 H3321X: Failed Outgoing External Inter-Cell Handovers (Directed Retry)

(1800/1900-1800/1900)

3 H3321Y: Failed Outgoing External Inter-Cell Handovers (Directed Retry)

(900/850-1800/1900)

4 H3321Z: Failed Outgoing External Inter-Cell Handovers (Directed Retry)(1800/1900-900/850)

5 H3321L: Failed Outgoing External Inter-Cell Handovers (T7 Expired)

(Directed Retry)

6 H3321C: Failed Outgoing External Inter-Cell Handovers (T8 Expired)

(Directed Retry)

Table 12-64 lists the counters of Failed Outgoing External Inter-Cell Handovers per Cell(Including Directed Retry).



12 Call Measurement




Table 12-64 Counters of Failed Outgoing External Inter-Cell Handovers per Cell (IncludingDirected Retry)

Number Counter

1 H332Ka: Failed Outgoing External Inter-Cell Handovers (Handover RequestRejected) (OM Intervention)

2 H332Kb: Failed Outgoing External Inter-Cell Handovers (Handover RequestRejected) (Equipment Failure)

3 H332Kc: Failed Outgoing External Inter-Cell Handovers (Handover Request

Rejected) (No Radio Resource Available)

4 H332Kd: Failed Outgoing External Inter-Cell Handovers (Handover Request

Rejected) (Requested Terrestrial Resource Unavailable)

5 H332Ke: Failed Outgoing External Inter-Cell Handovers (Handover RequestRejected) (BSS not Equipped)

6 H332Kf: Failed Outgoing External Inter-Cell Handovers (Handover RequestRejected) (Invalid Cell)

7 H332Kg: Failed Outgoing External Inter-Cell Handovers (Handover Request

Rejected) (Requested Transcoding/Rate Adaption Unavailable)

8 H332Kh: Failed Outgoing External Inter-Cell Handovers (Handover RequestRejected) (Circuit Pool Mismatch)

9 H332Ki: Failed Outgoing External Inter-Cell Handovers (Handover RequestRejected) (Requested Speech Version Unavailable)

10 H332Kj: Failed Outgoing External Inter-Cell Handovers (Handover RequestRejected) (Ciphering Algorithm not Supported)

11 H332Kk: Failed Outgoing External Inter-Cell Handovers (Handover Request

Rejected) (Terrestrial circuit already allocated)

12 H332Kl: Failed Outgoing External Inter-Cell Handovers (Handover RequestRejected) (Invalid Message)

13 H332Km: Failed Outgoing External Inter-Cell Handovers (Handover RequestRejected) (Protocol Error between BSS and MSC)

14 H332Kn: Failed Outgoing External Inter-Cell Handovers (Handover RequestRejected) (Other Causes)

15 H332Ha: Failed Outgoing External Inter-Cell Handovers (Clear CommandsSent by MSC) (Radio Interface Message Failure)

16 H332Hb: Failed Outgoing External Inter-Cell Handovers (Clear CommandsSent by MSC) (Radio Interface Failure)

17 H332Hc: Failed Outgoing External Inter-Cell Handovers (Clear CommandsSent by MSC) (OM Intervention)

18 H332Hd: Failed Outgoing External Inter-Cell Handovers (Clear CommandsSent by MSC) (Equipment Failure)






Number Counter

19 H332He: Failed Outgoing External Inter-Cell Handovers (Clear Commands

Sent by MSC) (Preemption)

20 H332Hf: Failed Outgoing External Inter-Cell Handovers (Clear CommandsSent by MSC) (Invalid Message)

21 H332Hg: Failed Outgoing External Inter-Cell Handovers (Clear CommandsSent by MSC) (Protocol Error between BSS and MSC)

22 H332Hh: Failed Outgoing External Inter-Cell Handovers (Clear Commands

Sent by MSC) (Other Causes)

23 H332G: Failed Outgoing External Inter-Cell Handovers (A-Interface Failure)

24 H3327La: Failed Outgoing External Inter-Cell Handovers (T7 Expired)(TCHF) (Traffic Channel)

25 H3328La: Failed Outgoing External Inter-Cell Handovers (T7 Expired)(TCHH) (Traffic Channel)

26 H3327Ca: Failed Outgoing External Inter-Cell Handovers (T8 Expired)(TCHF) (Traffic Channel)

27 H3328Ca: Failed Outgoing External Inter-Cell Handovers (T8 Expired)(TCHH) (Traffic Channel)

28 H332Ka: Failed Outgoing External Inter-Cell Handovers (Handover Request

Rejected) (OM Intervention)

29 H3323: Failed Outgoing External Inter-Cell Handovers (Different Signaling

Points)

Meaning Failed Outgoing External Inter-Cell Handovers (Excluding Directed Retry)

In the outgoing external inter-cell handover (excluding directed retry) procedure, the

BSC measures the related counter when the handover fails. The measurement is based onthe crossing of frequency bands, channel type, different signaling points, reject cause,

RR cause, clear command sent by MSC and A-interface failure, timer expired, andhandover cause.

Along with Outgoing External Inter-Cell Handover Requests per Cell and OutgoingExternal Inter-Cell Handover Commands per Cell, the counters show the performance of

outgoing external inter-cell handovers. Along with Incoming External Inter-Cell

Handover Measurement per Cell, the counters show the performance of external inter-cell handovers.


− 900/850 to 900/850

− 1800/1900 to 1800/1900

− 900/850 to 1800/1900

− 1800/1900 to 900/850




12 Call Measurement




− SDCCH

− TCHF

− TCHH

The handover between different signaling points in a BSC is also called outgoing


The reject causes consist of the following:

− OM intervention

− Equipment failure

− No radio resource available

− Requested terrestrial resource unavailable

− BSS not equipped

− Invalid Cell

− Requested transcoding/rate adaption unavailable

− Circuit pool mismatch− Requested Speech version unavailable

− Ciphering algorithm not supported

− Terrestrial circuit already allocated

− Invalid message

− Protocol Error between BSS and MSC

− Other causes

The RR causes of reconnection to old channels consist of the following:


−

Abnormal release, channel unacceptable− Abnormal release, timer expired

− Abnormal release, no activity on the radio path













− Other causes

The clear commands sent by MSC and A-interface failure consist of the following:

− Radio interface message failure

− Radio interface failure

− OM intervention







− Preemption

− Invalid message


− Other causes

The A interface failure occurs when the message such as MSC reset and SCCP linksdisruption is sent on the A interface.

The timers involved in the measurement consist of T7 and T8. T7 is triggered to wait for

an HO CMD message from the MSC after BSC1 sends an HO RQD message to the MSC.

T8 is triggered to wait for a CLR CMD message from the MSC after BSC1 sends an HOCMD message to the MS through the source cell.


− Uplink quality


− Uplink strength


− Timing advance

− Better cell

− Load



− OM intervention

− EDGE coverage

− Other causes

Failed Outgoing External Inter-Cell Handovers (Directed Retry)

In the outgoing external inter-cell handover (directed retry) procedure, the BSC measures

the related counter when the handover fails. The measurement is based on the crossing offrequency bands, different signaling points, reject cause, clear command sent by MSCand A-interface failure, and timer expired.

Along with Outgoing External Inter-Cell Handover Requests per Cell and Outgoing

External Inter-Cell Handover Commands per Cell, the counters show the performance ofoutgoing external inter-cell handovers. Along with Incoming External Inter-Cell

Handover Measurement per Cell, the counters show the performance of external inter-cell handovers.

The crossing of frequency bands is of the following types:− 900/850 to 900/850

− 1800/1900 to 1800/1900

− 900/850 to 1800/1900

− 1800/1900 to 900/850



− OM intervention





12 Call Measurement






− Invalid Cell


− Circuit pool mismatch

− Requested speech version unavailable



− Invalid message

− Protocol error between BSS and MSC

− Other causes

The clear commands sent by MSC and A-interface failure consist of the following:



− OM intervention


− Preemption

− Invalid message


− Other causes

The A interface failure occurs when the message such as MSC reset and SCCP linksdisruption is sent on the A interface.

The timers involved in the measurement consist of T7 and T8. T7 is triggered to wait foran HO CMD message from the MSC after BSC1 sends an HO RQD message to the MSC.T8 is triggered to wait for a CLR CMD message from the MSC after BSC1 sends an HOCMD message to the MS through the source cell.

Trigger Point

Figure 12-22 and Figure 12-23 show the trigger points of Failed Outgoing External Inter-Cell

Handovers (Excluding Directed Retry) and Failed Outgoing External Inter-Cell Handovers

(Directed Retry) respectively.






Figure 12-22 Trigger points of Failed Outgoing External Inter-Cell Handovers (ExcludingDirected Retry)

BTS1 BSC1MS

HO CMD

MSMSC BTS2

C HO

REQ ACK

MR FROM MS

HO RQD

HO REQ

CHAN ACTIV

CHAN

ACTIV ACK

HO DETECT

HO CMD HO DETECT

EST IND

HO ACC

PHY INFOFIRST SABM

UA

HO CMP

HO CMP

CLR CMD

CLR CMP

BSC2

A

E

G

HO FAILHO

RQD REJ

T7 expired

Reconnection

to old channel

D

H

T7 expired

F

Resource

request failed

In the

outgoing

external

inter-cell

handover

procedure



12 Call Measurement




Figure 12-23 Failed Outgoing External Inter-Cell Handovers (Directed Retry)

In the

outgoing

external

inter-cell

handover

(directed

retry)

procedure

BTS1(CELL1) BSC1MS

ASSIGN

REQ

MSMSC BTS2(CELL0)

CHAN

ACTIV ACK

HO DETECTHO

DETECT

EST IND

FIRST

SABM

HO ACC

HO CMD

CLR CMD

CLR CMP

BSC2

B

E

HO

REQ ACK

IMM ASS CMD

C

G

T7 expired

F

CHAN REQ

CHAN RQD

CHAN ACTIV

CHAN

ACTIV ACK

UA EST IND(CM

SERV REQ)CR(CM

SERV REQ)

CC

CM SERV ACCEPT

SETUP

CALL PROCEEDING

HO RQD

HO REQ

HO FAILHO

RQD REJ

HO CMD

Resource

request failed

CHAN ACTIV

PHY INFO

FIRST SABM

UA

HO CMP

HO CMP

H

T8 expired

A: Failed Outgoing External Inter-Cell Handovers (Excluding Directed Retry)

B: Failed Outgoing External Inter-Cell Handovers (Directed Retry)

C: Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected)

D: Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels)

E: Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent by MSC)

F: Failed Outgoing Internal Inter-Cell Handovers (A-Interface Failure)

G: Failed Outgoing Internal Inter-Cell Handovers (T7 Expired)

H: Failed Outgoing Internal Inter-Cell Handovers (T8 Expired)







Failed Outgoing External Inter-Cell Handovers (Excluding Directed Retry)

As shown in Figure 12-22, in the outgoing external inter-cell handover (excluding

directed retry) procedure, the related measurement is triggered when the handover fails.The measurement is based on the crossing of frequency bands, channel type, different

signaling points, and handover cause.The crossing of frequency bands is of the following types:

− 900/850 to 900/850

− 1800/1900 to 1800/1900

− 900/850 to 1800/1900

− 1800/1900 to 900/850


− SDCCH

− TCHF

− TCHH



− Uplink quality


− Uplink strength


− Timing advance

− Better cell

− Load− Rapid level drop


− OM intervention

− EDGE coverage

− Other causes

Failed Outgoing External Inter-Cell Handovers (Directed Retry)

As shown in Figure 12-22, in the outgoing external inter-cell handover (directed retry) procedure, the related measurement is triggered when the handover fails. The

measurement is based on the crossing of frequency bands and the different signaling

points.The crossing of frequency bands is of the following types:

− 900/850 to 900/850

− 1800/1900 to 1800/1900

− 900/850 to 1800/1900

− 1800/1900 to 900/850


Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected)

As shown in Figure 12-22 and Figure 12-23, when the BSC receives an HO FAIL

message from BSC2, it analyzes the failure cause and sends an HO RQD REJ message to



12 Call Measurement




BSC1. The related measurement is triggered when the MSC sends an HO RQD REJmessage to BSC1. The measurement is based on the reject cause carried in the HO RQDREJ message.


− OM intervention− Equipment failure




− Invalid cell



− Requested Speech version unavailable

−

Ciphering algorithm not supported− Terrestrial circuit already allocated

− Invalid message


− Other cause


As shown in Figure 12-22, in the outgoing external inter-cell handover (excludingdirected retry) procedure, the measurement is triggered when the MS reconnects to the

old channel and sends an HO FAIL message on the old channel. The measurement is based on the RR cause.

The RR causes consist of the following:− Abnormal release, unspecified


− Abnormal release, timer expired














− Other causes

Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent by MSC)






As shown in Figure 12-22 and Figure 12-23, in the outgoing external inter-cell handover(including directed retry) procedure, the measurement is triggered when BSC1 receives aCLR CMD message from the MSC. The measurement is based on the cause carried inthe CLR CMD message.

The causes consist of the following:− Radio interface message failure


− OM intervention


− Preemption

− Invalid message


− Other causes

Failed Outgoing External Inter-Cell Handovers (A-Interface Failure)

As shown in Figure 12-22 and Figure 12-23, in the outgoing external inter-cell handover

(including directed retry) procedure, the measurement is triggered when BSC1 receivesan A interface failure message. The measurement is performed in the source cell.

Failed Outgoing External Inter-Cell Handovers (T7 Expired)


(including directed retry) procedure, the measurement is triggered when T7 expires. T7is triggered to wait for an HO CMD message from the MSC after BSC1 sends an HORQD message to the MSC. The measurement is based on the channel type.


− SDCCH

− TCHF− TCHH

If directed retry is performed in the outgoing external inter-cell handover procedure, thechannel involved in the measurement is a traffic channel. If no directed retry is performed in the outgoing external inter-cell handover procedure, the channel involvedin the measurement can be a traffic channel or a signaling channel.

Failed Outgoing External Inter-Cell Handovers (T8 Expired)


(including directed retry) procedure, the measurement is triggered when T8 expires. T8

is triggered to wait for a CLR CMD message from the MSC after BSC1 sends an HOCMD message to the MS through the source cell. If T8 expires, the MS does not access

the target cell or reconnect to the old channel within the scheduled time. Themeasurement is based on the channel type.

If directed retry is performed in the outgoing external inter-cell handover procedure, thechannel involved in the measurement is a traffic channel. If no directed retry is

performed in the outgoing external inter-cell handover procedure, the channel involvedin the measurement can be a traffic channel or a signaling channel.

Formula

None.



12 Call Measurement




12.14.5 Outgoing External Inter-Cell Handover AnalyzedMeasurement per Cell

CounterTable 12-65 lists the counters of Outgoing External Inter-Cell Handover Analyzed


Table 12-65 Counters of Outgoing External Inter-Cell Handover Analyzed Measurement per Cell

Number Counter

1 CH330: Outgoing External Inter-Cell Handover Requests

2 CH333: Successful Outgoing External Inter-Cell Handovers

3 CH331: Outgoing External Inter-Cell Handover Commands

4 CH332: Failed Outgoing External Inter-Cell Handovers

5 TH333: Success Rate of Outgoing External Inter-Cell Handover

6 CH332K: Failed Outgoing External Inter-Cell Handovers (Handover RequestRejected)

7 CH332D: Failed Outgoing External Inter-Cell Handovers (Reconnection toOld Channels)

8 CH332H: Failed Outgoing External Inter-Cell Handovers (Clear Commands

Sent by MSC)

9 CH332L: Failed Outgoing External Inter-Cell Handovers (T7 Expired)

10 CH332C: Failed Outgoing External Inter-Cell Handovers (T8 Expired)

Meaning

None.

Trigger Point

None.

Formula

Outgoing External Inter-Cell Handover Requests =

[Outgoing External Inter-Cell Handover Requests (SDCCH) (Excluding Directed Retry)(900/850-900/850)] +


[Outgoing External Inter-Cell Handover Requests (SDCCH) (Excluding Directed Retry)

(900/850-1800/1900)] +







[Outgoing External Inter-Cell Handover Requests (TCHF) (Excluding Directed Retry)

(900/850-900/850)] +


(1800/1900-1800/1900)] +

[Outgoing External Inter-Cell Handover Requests (TCHF) (Excluding Directed Retry)(900/850-1800/1900)] +


[Outgoing External Inter-Cell Handover Requests (TCHH) (Excluding Directed Retry)

(900/850-900/850)] +


(1800/1900-1800/1900)] +


(900/850-1800/1900)] +

[Outgoing External Inter-Cell Handover Requests (TCHH) (Excluding Directed Retry)(1800/1900-900/850)] +

[Outgoing External Inter-Cell Handover Requests (Directed Retry) (900/850-900/850)] +



[Outgoing External Inter-Cell Handover Requests (Directed Retry) (1800/1900-900/850)]

Successful Outgoing External Inter-Cell Handovers =

[Outgoing External Inter-Cell Handover Requests]-

[Failed Outgoing External Inter-Cell Handovers]

Outgoing External Inter-Cell Handover Commands =

[Outgoing External Inter-Cell Handover Commands (SDCCH) (Excluding Directed Retry)

(900/850-900/850)] +

[Outgoing External Inter-Cell Handover Commands (SDCCH) (Excluding Directed Retry)

(1800/1900-1800/1900)] +

[Outgoing External Inter-Cell Handover Commands (SDCCH) (Excluding Directed Retry)(900/850-1800/1900)] +

[Outgoing External Inter-Cell Handover Commands (SDCCH) (Excluding Directed Retry)(1800/1900-900/850)] +

[Outgoing External Inter-Cell Handover Commands (TCHF) (Excluding Directed Retry)

(900/850-900/850)] +



12 Call Measurement




[Outgoing External Inter-Cell Handover Commands (TCHF) (Excluding Directed Retry)(1800/1900-1800/1900)] +


(900/850-1800/1900)] +


(1800/1900-900/850)] +

[Outgoing External Inter-Cell Handover Commands (TCHH) (Excluding Directed Retry)(900/850-900/850)] +

[Outgoing External Inter-Cell Handover Commands (TCHH) (Excluding Directed Retry)(1800/1900-1800/1900)] +

[Outgoing External Inter-Cell Handover Commands (TCHH) (Excluding Directed Retry)

(900/850-1800/1900)] +

[Outgoing External Inter-Cell Handover Commands (TCHH) (Excluding Directed Retry)

(1800/1900-900/850)] +

[Outgoing External Inter-Cell Handover Commands (Directed Retry) (900/850-900/850)] +

[Outgoing External Inter-Cell Handover Commands (Directed Retry) (1800/1900-1800/1900)]+

[Outgoing External Inter-Cell Handover Commands (Directed Retry) (900/850-1800/1900)] +

[Outgoing External Inter-Cell Handover Commands (Directed Retry) (1800/1900-900/850)]

Failed Outgoing External Inter-Cell Handovers =

[Failed Outgoing External Inter-Cell Handovers (SDCCH) (Excluding Directed Retry)(900/850-900/850)] +

[Failed Outgoing External Inter-Cell Handovers (SDCCH) (Excluding Directed Retry)

(1800/1900-1800/1900)] +



(1800/1900-900/850)] +

[Failed Outgoing External Inter-Cell Handovers (TCHF) (Excluding Directed Retry)

(900/850-900/850)] +[Failed Outgoing External Inter-Cell Handovers (TCHF) (Excluding Directed Retry)(1800/1900-1800/1900)] +


(900/850-1800/1900)] +

[Failed Outgoing External Inter-Cell Handovers (TCHF) (Excluding Directed Retry)(1800/1900-900/850)] +

[Failed Outgoing External Inter-Cell Handovers (TCHH) (Excluding Directed Retry)

(900/850-900/850)] +

[Failed Outgoing External Inter-Cell Handovers (TCHH) (Excluding Directed Retry)(1800/1900-1800/1900)] +






[Failed Outgoing External Inter-Cell Handovers (TCHH) (Excluding Directed Retry)(900/850-1800/1900)] +


(1800/1900-900/850)] +

[Failed Outgoing External Inter-Cell Handovers (Directed Retry) (900/850-900/850)] +



[Failed Outgoing External Inter-Cell Handovers (Directed Retry) (1800/1900-900/850)]

Success Rate of Outgoing External Inter-Cell Handover =

[Successful Outgoing External Inter-Cell Handovers] *{100}/[Outgoing External Inter-Cell

Handover Requests]

Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) =

[Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (OM

Intervention)] +

[Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Equipment

Failure)] +

[Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (No RadioResource Available)] +

[Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (RequestedTerrestrial Resource Unavailable)] +

[Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (BSS not

Equipped)] +

[Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Invalid Cell)]+

[Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Requested

Transcoding/Rate Adaption Unavailable)] +

[Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Circuit PoolMismatch)] +

[Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (RequestedSpeech Version Unavailable)] +

[Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Ciphering

Algorithm not Supported)] +

[Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Terrestrialcircuit already allocated)] +

[Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Invalid

Message)] +

[Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Protocol Error

between BSS and MSC)] +



12 Call Measurement




[Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Other Causes)]

Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) =

[Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (AbnormalRelease, Unspecified)] +

[Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal

Release, Channel Unacceptable)] +

[Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (AbnormalRelease, Timer Expired)] +

[Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (AbnormalRelease, No Activity on the Radio Path)] +

[Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Preemptive

Release)] +[Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Handover


[Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Channel

Mode Unavailable)] +

[Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (FrequencyUnavailable)] +

[Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (CallAlready Cleared)] +

[Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels)(Semantically Incorrect Message)] +

[Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Invalid


[Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (MessageType Non-existent or Not Implemented)] +

[Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (MessageType Not Compatible with Protocol State)] +

[Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Conditional

IE Error)] +

[Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (No Cell

Allocation Available)] +

[Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Protocol

Error Unspecified)] +

[Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (OtherCauses)]

Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent by MSC) =

[Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent by MSC) (RadioInterface Message Failure)] +






[Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent by MSC) (RadioInterface Failure)] +

[Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent by MSC) (OM

Intervention)] +

[Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent by MSC) (Equipment

Failure)] +

[Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent by MSC)(Preemption)] +

[Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent by MSC) (InvalidMessage)] +

[Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent by MSC) (Protocol

Error between BSS and MSC)] +

[Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent by MSC) (Other

Causes)]

Failed Outgoing External Inter-Cell Handovers (T7 Expired) =

[Failed Outgoing External Inter-Cell Handovers (T7 Expired) (SDCCH) (Excluding DirectedRetry)] +





[Failed Outgoing External Inter-Cell Handovers (T7 Expired) (Directed Retry)]

Failed Outgoing External Inter-Cell Handovers (T8 Expired) =

[Failed Outgoing External Inter-Cell Handovers (T8 Expired) (SDCCH) (Excluding DirectedRetry)] +





[Failed Outgoing External Inter-Cell Handovers (T8 Expired) (Directed Retry)]



12 Call Measurement




12.15 Incoming Inter-RAT Inter-Cell HandoverMeasurement per Cell

12.15.1 Overview

The conventions used in this section are as follows:

The MSC of the local system is referred to as MSC 1, and that of another system is referred to as

MSC 2.

The BSC of the local system is referred to as BSC 1.

The BTS of the local system is referred to as BTS 1.

The procedure for incoming inter-RAT inter-cell handover is as follows:

MSC 2 sends a PERFORM HO message to MSC 1. Based on the information of the target

cell in this message and the mapping between cells and BSCs in the MSC 1 data configuration,MSC 1 finds out the corresponding BSC, that is, BSC 1, and sends an HO ERQ message toBSC 1. Based on the information of the target cell, BSC 1 requests channel resources from the

target cell. After the request succeeds, BSC 1 sends a CHAN ACTIV message to the target

cell. BTS 1 sends a CHAN ACTIV ACK message from the target cell to BSC 1. BSC 1requests the resources for voice service. After the request succeeds, BSC 1 sends an HO REQACK message to MSC 1.

After receiving an HO CMD message from another system, the MS sends an HO ACCmessage to BTS 1, attempting to access the new system from the target cell. BTS 1 reports anHO DETECT message to MSC 1 through BSC 1. At the same time, BTS 1 sends a PHY

INFO message to the MS. The MS sends a FIRST SABM message to access the network.

BTS 1 sends an EST IND message to BSC 1. At the same time, BTS 1 responds the MS with

a UA message. After accessing the network, the MS sends an HO CMP message to MSC 1through the target cell.

Here, the incoming inter-RAT inter-cell handover is complete.






Figure 12-24 Incoming inter-RAT inter-cell handover procedure

MSC1 BSC1MSC2 BTS1

A

MS

PERFORM HO

HO REQ

CHAN ACTIV

CHAN ACTIV ACK

HO REQ ACK

RADIO CHAN ACK

IAM

ACM

BHO ACC

HO DETECT

HO DETECT

PHY INFO

FIRST SABM

UAEST IND

HO CMP

HO CMP

SEND END SIG

A: Request for incoming inter-RAT inter-cell handover

B: Respond to the request for incoming inter-RAT inter-cell handover

Table 12-66 lists the counter types of Incoming Inter-RAT Inter-Cell Handover Measurement per Cell.

Table 12-66 Counter types of Incoming Inter-RAT Inter-Cell Handover Measurement per Cell

Counter Type Section

Incoming Inter-RAT Inter-Cell Handover Requests per Cell 12.15.2

Incoming Inter-RAT Inter-Cell Handover Responses per Cell 12.15.3

Failed Incoming Inter-RAT Inter-Cell Handovers per Cell 12.15.4

Incoming Inter-RAT Inter-Cell Handover Analyzed Measurement per Cell 12.15.5



12 Call Measurement




12.15.2 Incoming Inter-RAT Inter-Cell Handover Requests perCell

CounterTable 12-67 lists the counters of Incoming Inter-RAT Inter-Cell Handover Requests per Cell.

Table 12-67 Counters of Incoming Inter-RAT Inter-Cell Handover Requests per Cell

Number Counter

1 H3600: Incoming Inter-RAT Inter-Cell Handover Requests (SDCCH)

2 H3609: Incoming Inter-RAT Inter-Cell Handover Requests (TCH)

Meaning

When receiving an HO ERQ message from MSC 1, BSC 1 performs the measurement basedon the channel type if deciding to perform an inter-RAT handover.

Along with Incoming Inter-RAT Inter-Cell Handover Responses per Cell and Failed Incoming

Inter-RAT Inter-Cell Handovers per Cell, this type of counters can help you to betterunderstand the situation of incoming inter-RAT inter-cell handover.

Along with Outgoing Inter-RAT Inter-Cell Handover Measurement per Cell, this type ofcounters can help you to better understand the performance of incoming inter-RAT inter-cell

handover.

The channel type may be SDCCH or TCH.

Trigger Point

The measurement is triggered at point A as shown in Figure 12-24, that is, when BSC 1

receives an HO REQ message from MSC 1. For an inter-RAT handover, the measurement is based on the channel type.

Formula

None.






12.15.3 Incoming Inter-RAT Inter-Cell Handover Responses perCell

CounterTable 12-68 list the counters of Incoming Inter-RAT Inter-Cell Handover Responses per Cell.

Table 12-68 Counters of Incoming Inter-RAT Inter-Cell Handover Responses per Cell

Number Counter

1 H3610: Incoming Inter-RAT Inter-Cell Handover Responses (SDCCH)

2 H3617: Incoming Inter-RAT Inter-Cell Handover Responses (TCHF)

3 H3618: Incoming Inter-RAT Inter-Cell Handover Responses (TCHH)

Meaning

When responding MSC 1 with an HO REQ ACK message, BSC 1 performs the measurement

based on the channel type.

Along with Incoming Inter-RAT Inter-Cell Handover Responses per Cell and Failed Incoming

Inter-RAT Inter-Cell Handovers per Cell, this type of counters can help you to betterunderstand the situation of incoming inter-RAT inter-cell handovers.

Along with Outgoing Inter-RAT Inter-Cell Handover Measurement per Cell, this type of

counters can help you to better understand the performance of incoming inter-RAT inter-cellhandovers.

The channel type may be SDCCH, TCHH, or TCHF.

Trigger Point

The measurement is triggered at point B as shown in Figure 12-24, that is, when BSC 1

responds MSC 1 with an HO REQ ACK message. The measurement is based on the channeltype.

Formula

None.



12 Call Measurement




12.15.4 Failed Incoming Inter-RAT Inter-Cell Handovers per Cell

Counter

Table 12-69 list the counters of Failed Incoming Inter-RAT Inter-Cell Handovers per Cell.

Table 12-69 Counters of Failed Incoming Inter-RAT Inter-Cell Handovers per Cell

Number Counter

1 H3620: Failed Incoming Inter-RAT Inter-Cell Handovers (SDCCH)

2 H3627: Failed Incoming Inter-RAT Inter-Cell Handovers (TCHF)

3 H3628: Failed Incoming Inter-RAT Inter-Cell Handovers (TCHH)

4 H362J: Failed Incoming Inter-RAT Inter-Cell Handovers (Invalid Message)

5 H3620A: Failed Incoming Inter-RAT Inter-Cell Handovers (ChannelUnavailable) (SDCCH)

6 H3629A: Failed Incoming Inter-RAT Inter-Cell Handovers (ChannelUnavailable) (TCH)

7 H362E: Failed Incoming Inter-RAT Inter-Cell Handovers (CIC Unavailable)

8 H362F: Failed Incoming Inter-RAT Inter-Cell Handovers (CIC Allocated)

9 H362B: Failed Incoming Inter-RAT Inter-Cell Handovers (Terrestrial Resource

Request Failed)

10 H362H: Failed Incoming Inter-RAT Inter-Cell Handovers (Clear CommandsSent by MSC)

11 H3620C: Failed Incoming Inter-RAT Inter-Cell Handovers (Timer Expired)(SDCCH)

12 H3629Cb: Failed Incoming Inter-RAT Inter-Cell Handovers (Timer Expired)

(TCH) (Signaling Channel)

13 H3629Ca: Failed Incoming Inter-RAT Inter-Cell Handovers (Timer Expired)(TCH) (Traffic Channel)

Meaning

When an incoming inter-RAT inter-cell handover fails, BSC 1 performs the measurement

based on the channel type, triggering condition, and failure cause.

Along with Incoming Inter-RAT Inter-Cell Handover Requests per Cell and Incoming Inter-

RAT Inter-Cell Handover Responses per Cell, this type of counters can help you to betterunderstand the situation of incoming inter-RAT inter-cell handovers.

Along with Outgoing Inter-RAT Inter-Cell Handover Measurement per Cell, this type of

counters can help you to better understand the performance of incoming inter-RAT inter-cellhandovers.






The channel type may be SDCCH, TCHF, or TCHH.

The triggering condition of a failure in incoming inter-RAT inter-cell handover may be Invalid

Message, Channel Unavailable, CIC abnormal, Terrestrial Resource Request Failed, Clear

Commands Sent by MSC, or Timer Expired.

The failure cause may be CIC Unavailable or CICI Allocated.

Trigger Point

The measurement is triggered at any of points A to G as shown in Figure 12-25.

Figure 12-25 Incoming inter-RAT inter-cell handover procedure

MSC1 BSC1MSC2 BTS1 MS

HO REQ

C

B

A

PERFORM HO

HO REQ ACK

D

E

F

CHAN ACTIV

CHAN ACTIV ACK

RADIOCHAN ACK

IAM

ACM

HO DETECT

HO DETECT

HO ACC

PHY INFO

FIRST SABM

UAHandover

timer timeout

G

HO CMP

HO CMP

SEND END SIG

EST IND

A: Failed Incoming Inter-RAT Inter-Cell Handovers

B: Failed Incoming Inter-RAT Inter-Cell Handovers (Invalid Message)

C: Failed Incoming Inter-RAT Inter-Cell Handover Requests (Channel Unavailable)

D: Failed Incoming Inter-RAT Inter-Cell Handovers (CIC abnormal)

E: Failed Incoming Inter-RAT Inter-Cell Handovers (Terrestrial Resource Request Failed)

F: Failed Incoming Inter-RAT Inter-Cell Handovers (Clear Commands Sent by MSC)

G: Failed Incoming Inter-RAT Inter-Cell Handovers (Timer Expired)



12 Call Measurement




Failed Incoming Inter-RAT Inter-Cell Handovers

When an incoming inter-RAT inter-cell handover fails, BSC 1 performs the measurement based on the channel type.

The channel type may be SDCCH, TCHF, or TCHH.

Failed Incoming Inter-RAT Inter-Cell Handovers (Invalid Message)

When receiving an HO REQ message from MSC 1, BSC 1 decodes the message. When

finding out that the message is not compliant with the protocol requirements during thedecoding, BSC 1 performs the measurement.

Failed Incoming Inter-RAT Inter-Cell Handovers (Channel Unavailable)

When the target cell responds BSC 1 that the request for channel resources fails becauseof channel unavailable, BSC 1 performs the measurement based on the channel type.

The channel type may be SDCCH or TCH.

Failed Incoming Inter-RAT Inter-Cell Handovers (CIC Unavailable)

When failing to request terrestrial resources because of CIC abnormal, BSC 1 performs

the measurement based on the failure cause. Where, the CIC is carried in the HO REQmessage.

The failure cause may be CIC Unavailable or CIC Allocated.

Failed Incoming Inter-RAT Inter-Cell Handovers (Terrestrial Resource Request Failed)

When failing to request terrestrial resources not because of CIC abnormal, BSC 1 performs the measurement. Where, the CIC is carried in the HO REQ message.

Failed Incoming Inter-RAT Inter-Cell Handovers (Clear Commands Sent by MSC)

When receiving a CLR CMD message from MSC 1, BSC 1 performs the measurement.

Failed Incoming Inter-RAT Inter-Cell Handovers (Timer Expired)

When failing to receive an HO CMP message from the MS through the target cell before

the timer is expired, BSC 1 performs the measurement based on the channel type.The channel type may be SDCCH or TCH. Here, the TCH may be a traffic channel or asignaling channel.

Formula

None.

12.15.5 Incoming Inter-RAT Inter-Cell Handover AnalyzedMeasurement per Cell

Counter

Table 12-70 lists the counters of Incoming Inter-RAT Inter-Cell Handover Analyzed


Table 12-70 Counters of Incoming Inter-RAT Inter-Cell Handover Analyzed Measurement perCell

Number Counter

1 CH360: Incoming Inter-RAT Inter-Cell Handover Requests

2 CH363: Successful Incoming Inter-RAT Inter-Cell Handovers






Number Counter

3 TH363: Success Rate of Incoming Inter-RAT Inter-Cell Handover

4 CH361: Incoming Inter-RAT Inter-Cell Handover Responses

5 H362: Failed Incoming Inter-RAT Inter-Cell Handovers

6 H362C: Failed Incoming Inter-RAT Inter-Cell Handovers (Timer Expired)

Meaning

None.

Trigger Point

None.

Formula

Incoming Inter-RAT Inter-Cell Handover Requests =

[Incoming Inter-RAT Inter-Cell Handover Requests (SDCCH)] +

[Incoming Inter-RAT Inter-Cell Handover Requests (TCH)]

Successful Incoming Inter-RAT Inter-Cell Handovers =

[Incoming Inter-RAT Inter-Cell Handover Requests (SDCCH)] +

[Incoming Inter-RAT Inter-Cell Handover Requests (TCH)]-

[Failed Incoming Inter-RAT Inter-Cell Handovers (SDCCH)]-

[Failed Incoming Inter-RAT Inter-Cell Handovers (TCHF)]-

[Failed Incoming Inter-RAT Inter-Cell Handovers (TCHH)]

Success Rate of Incoming Inter-RAT Inter-Cell Handover =

[Successful Incoming Inter-RAT Inter-Cell Handovers]*{100}/[Incoming Inter-RAT Inter-Cell Handover Requests]

Incoming Inter-RAT Inter-Cell Handover Responses =

[Incoming Inter-RAT Inter-Cell Handover Responses (SDCCH)] +

[Incoming Inter-RAT Inter-Cell Handover Responses (TCHF)] +

[Incoming Inter-RAT Inter-Cell Handover Responses (TCHH)]

Failed Incoming Inter-RAT Inter-Cell Handovers =



12 Call Measurement




[Failed Incoming Inter-RAT Inter-Cell Handovers (SDCCH)] +

[Failed Incoming Inter-RAT Inter-Cell Handovers (TCHF)] +

[Failed Incoming Inter-RAT Inter-Cell Handovers (TCHH)]

Failed Incoming Inter-RAT Inter-Cell Handovers (Timer Expired)=

[Failed Incoming Inter-RAT Inter-Cell Handovers (Timer Expired) (SDCCH)] +

[Failed Incoming Inter-RAT Inter-Cell Handovers (Timer Expired) (TCH) (SignalingChannel)] +

[Failed Incoming Inter-RAT Inter-Cell Handovers (Timer Expired) (TCH) (Traffic Channel)]

12.16 Outgoing Inter-RAT Inter-Cell HandoverMeasurement per Cell

12.16.1 Overview

The conventions used in this section are as follows:

The BSC of the source cell is referred to as BSC 2. The BSC of the target cell is referred to as BSC 1.

The BTS corresponds to BSC 2 is referred to as BTS 2.

The MSC corresponds to BSC 2 is referred to as MSC 2.

Outgoing Inter-RAT Inter-Cell Handover Measurement per Cell has the following two types:

Outgoing Inter-RAT Inter-Cell Handover Measurement per Cell (Excluding DirectedRetry)

The MS sends a measurement report to BSC 2. Based on the current load and signalinterference of the cell as well as the signal quality and RX/TX level in the measurement

report, BSC 2 decides whether to perform a handover. If deciding to perform a handover,BSC 2 sends a handover triggering indication to the corresponding processing module. If

the target cell is in another system, BSC 2 initiates an inter-RAT handover outgoing fromthe source cell.

BSC 2 sends an HO RQD message to MSC 2, requesting MSC 2 to notify the other

system. Based on its data configuration, MSC 2 finds out the corresponding MSC, that is,

MSC 1, and a handover request to MSC 1. After preparing for the handover, the othersystem notifies MSC 2. MSC 2 sends an HO CMD message to BSC 2, requesting BSC 2

to notify the MS. BSC 2 sends an HO CMD message to the MS through the source cell,requesting the MS to access the network in the target cell.

After the access succeeds, MSC 1 notifies MSC 2 that the incoming inter-RAT inter-cell

handover is complete. MSC 2 sends a CLR CMD message to BSC 2. After instructingthe source cell to release related resources, BSC 2 responds MSC 2 with a CLR CMP

message.

Here, the outgoing inter-RAT inter-cell handover is complete.






Figure 12-26 Outgoing inter-RAT inter-cell handover procedure (excluding directed retry)

MSC2 BSC2MSC1 BTS2

A

MS

MR FROM MS

HO RQD

RADIO CHAN ACK

IAM

ACM

B

HO CMD

HO CMD

CLR CMP

SEND END SIG

PERFORM HO

CLR CMD

A: Request for an outgoing inter-RAT inter-cell handover

B: Command for an incoming inter-RAT inter-cell handover

Outgoing Inter-RAT Inter-Cell Handover Measurement per Cell (Directed Retry)

After receiving an ASSIGN REQ message from MSC 2, BSC 2 decides the assignment

mode based on the load of the cell. There are three assignment procedures: normal

assignment procedure, directed retry procedure, and assignment modification procedure.If the load of the cell is so high that the cell cannot admit a new service or that a newservice will affect current services, BSC 2 decides to perform a directed retry. If the

target cell selected during the directed retry belongs to another system, BSC 2 initiatesan inter-RAT inter-cell handover procedure outgoing from the source cell.

BSC 2 sends an HO RQD message to MSC 2, requesting MSC 2 to notify the other

system. Based on its data configuration, MSC 2 finds out the corresponding MSC, that is,MSC 1, and a handover request to MSC 1. After preparing for the handover, the other

system notifies MSC 2. MSC 2 sends an HO CMD message to BSC 2, requesting BSC 2to notify the MS. BSC 2 sends an HO CMD message to the MS through the source cell,

requesting the MS to access the network in the target cell. After the access succeeds,MSC 1 notifies MSC 2 that the incoming inter-RAT inter-cell handover is complete.

MSC 2 sends a CLR CMD message to BSC 2. After instructing the source cell to releaserelated resources, BSC 2 responds MSC 2 with a CLR CMP message.

Here, the outgoing inter-RAT inter-cell handover during directed retry is complete.



12 Call Measurement




Figure 12-27 Outgoing inter-RAT inter-cell handover procedure (including directed retry)

MSC2 BSC2MSC1 BTS2

A

MS

ASSIGN REQ

HO RQD

RADIO CHAN ACK

IAM

ACM

B

HO CMD

HO CMD

CLR CMP

SEND END SIG

PERFORM HO

CLR CMD

A: Request for an outgoing inter-RAT inter-cell handover

B: Command for an incoming inter-RAT inter-cell handover

Table 12-71 lists the counter types of Outgoing Inter-RAT Inter-Cell Handover Measurement per Cell.

Table 12-71 Counter types of Outgoing Inter-RAT Inter-Cell Handover Measurement per Cell


Outgoing Inter-RAT Inter-Cell Handover Requests per Cell 12.16.2

Outgoing Inter-RAT Inter-Cell Handover Commands per Cell 12.16.3

Failed Outgoing Inter-RAT Inter-Cell Handovers per Cell 12.16.4

Outgoing Inter-RAT Inter-Cell Handover Analyzed Measurement per Cell 12.16.5






12.16.2 Outgoing Inter-RAT Inter-Cell Handover Requests perCell

CounterTable 12-72 lists the counters of Outgoing Inter-RAT Inter-Cell Handover Requests per Cell.

Table 12-72 Counters of Outgoing Inter-RAT Inter-Cell Handover Requests per Cell

Number Counter

1 H3500: Outgoing Inter-RAT Inter-Cell Handover Requests (SDCCH)

(Excluding Directed Retry)

2 H3507: Outgoing Inter-RAT Inter-Cell Handover Requests (TCHF)

3 H3508: Outgoing Inter-RAT Inter-Cell Handover Requests (TCHH)

Meaning Outgoing Inter-RAT Inter-Cell Handover Requests (Excluding Directed Retry)

This type of counters measures the number of outgoing inter-RAT inter-cell handoverrequests that are initiated according to handover decision.

Along with Outgoing Inter-RAT Inter-Cell Handover Commands per Cell and Failed

Outgoing External Inter-Cell Handovers per Cell, this type of counters can help you to better understand the situation of outgoing inter-RAT inter-cell handovers.

Along with Incoming Inter-RAT Inter-Cell Handover Measurement per Cell, this type ofcounters can help you to better understand the situation of all outgoing inter-RAT inter-cell handovers.

The channel type may be SDCCH.

Outgoing Inter-RAT Inter-Cell Handover Requests (Directed Retry)

This type of counters measures the number of outgoing inter-RAT inter-cell handoverrequests that are initiated by the BSC during directed retry in an assignment procedure.

Along with Outgoing Inter-RAT Inter-Cell Handover Commands per Cell and Failed

Outgoing External Inter-Cell Handovers per Cell, this type of counters can help you to better understand the situation of outgoing inter-RAT inter-cell handovers.

Along with Incoming Inter-RAT Inter-Cell Handover Measurement per Cell, this type ofcounters can help you to better understand the situation of all outgoing inter-RAT inter-cell handovers.

The channel type may be TCHH or TCHF.

Trigger Point Outgoing Inter-RAT Inter-Cell Handover Requests (Excluding Directed Retry)

The measurement is triggered at point A as shown in Figure 12-27, that is, when BSC 2decides to perform an outgoing inter-RAT inter-cell handover according to measurementreports. The measurement is based on the channel type.

Outgoing Inter-RAT Inter-Cell Handover Requests (Directed Retry)



12 Call Measurement




The measurement is triggered at point A as shown in Figure 12-27, that is, when BSC 2decides to perform an inter-RAT directed retry. The measurement is based on the channeltype.

Formula None.

12.16.3 Outgoing Inter-RAT Inter-Cell Handover Commands perCell

Counter

Table 12-73 lists the counters of Outgoing Inter-RAT Inter-Cell Handover Commands per Cell.

Table 12-73 Counters of Outgoing Inter-RAT Inter-Cell Handover Commands per Cell

Number Counter

1 H3510: Outgoing Inter-RAT Inter-Cell Handover Commands (SDCCH)(Excluding Directed Retry)

2 H3517: Outgoing Inter-RAT Inter-Cell Handover Commands (TCHF)

3 H3518: Outgoing Inter-RAT Inter-Cell Handover Commands (TCHH)

MeaningThis type of counters measures the number of outgoing inter-RAT inter-cell handover

commands that are sent by BSC 2 to the MS through the source cell. Along with Outgoing

Inter-RAT Inter-Cell Handover Requests per Cell and Failed Outgoing External Inter-CellHandovers per Cell, this type of counters can help you to better understand the situation of

outgoing inter-RAT inter-cell handovers.

Along with Incoming Inter-RAT Inter-Cell Handover Measurement per Cell, this type ofcounters can help you to better understand the situation of all outgoing inter-RAT inter-cell

handovers.

The channel type may be SDCCH, TCHH, or TCHF. The directed retry procedure applies to

only traffic channels.

Trigger Point

The measurement is triggered at point B as shown in Figure 12-26 and Figure 12-27, that is,

when BSC 2 sends an HO CMD message to the MS through the source cell. Here, thehandover includes directed retry. The measurement is based on the channel type.

Formula

None.






12.16.4 Failed Outgoing Inter-RAT Inter-Cell Handovers per Cell

Counter

Table 12-74 lists the counters of Failed Outgoing Inter-RAT Inter-Cell Handovers per Cell.

Table 12-74 Counters of Failed Outgoing Inter-RAT Inter-Cell Handovers per Cell

Number Counter

1 H3520: Failed Outgoing Inter-RAT Inter-Cell Handovers (SDCCH) (ExcludingDirected Retry)

2 H3527: Failed Outgoing Inter-RAT Inter-Cell Handovers (TCHF)

3 H3528: Failed Outgoing Inter-RAT Inter-Cell Handovers (TCHH)

4 H352Da: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection toOld Channels) (Abnormal Release, Unspecified)

5 H352Db: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to

Old Channels) (Abnormal Release, Channel Unacceptable)

6 H352Dc: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to

Old Channels) (Abnormal Release, Timer Expired)

7 H352Dd: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection toOld Channels) (Abnormal Release, No Activity on the Radio Path)

8 H352De: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to

Old Channels) (Preemptive Release)

9 H352Df: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to

Old Channels) (Handover Failed, Timing Advance out of Range)

10 H352Dg: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to

Old Channels) (Channel Mode Unavailable)

11 H352Dh: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection toOld Channels) (Frequency Unavailable)

12 H352Di: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection toOld Channels) (Call Already Cleared)

13 H352Dj: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection toOld Channels) (Semantically Incorrect Message)

14 H352Dk: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection toOld Channels) (Invalid Mandatory Information)

15 H352Dl: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection toOld Channels) (Message Type Non-existent or Not Implemented)

16 H352Dm: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection toOld Channels) (Message Type Not Compatible with Protocol State)

17 H352Dn: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to

Old Channels) (Conditional IE Error)



12 Call Measurement




Number Counter

18 H352Do: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to

Old Channels) (No Cell Allocation Available)

19 H352Dp: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection toOld Channels) (Protocol Error Unspecified)

20 H352Dq: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection toOld Channels) (Other Causes)

21 H352Ka: Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request

Rejected) (OM Intervention)

22 H352Kb: Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover RequestRejected) (Equipment Failure)

23 H352Kc: Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request

Rejected) (No Radio Resource Available)

24 H352Kd: Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover RequestRejected) (Requested Terrestrial Resource Unavailable)

25 H352Ke: Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request

Rejected) (BSS not Equipped)

26 H352Kf: Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover RequestRejected) (Invalid Cell)

27 H352Kg: Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover RequestRejected) (Requested Transcoding/Rate Adaption Unavailable)

28 H352Kh: Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover RequestRejected) (Circuit Pool Mismatch)

29 H352Ki: Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover RequestRejected) (Requested Speech Version Unavailable)

30 H352Kj: Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover RequestRejected) (Ciphering Algorithm not Supported)

31 H352Kk: Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover RequestRejected) (Terrestrial circuit already allocated)

32 H352Kl: Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request

Rejected) (Invalid Message)

33 H352Km: Failed Outgoing Inter-RAT Inter-Cell Handovers (HandoverRequest Rejected) (Protocol Error between BSS and MSC)

34 H352Kn: Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover RequestRejected) (Other Causes)

35 H352Ha: Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear CommandsSent by MSC) (Radio Interface Message Failure)

36 H352Hb: Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands

Sent by MSC) (Radio Interface Failure)






Number Counter

37 H352Hc: Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands

Sent by MSC) (OM Intervention)

38 H352Hd: Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear CommandsSent by MSC) (Equipment Failure)

39 H352He: Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear CommandsSent by MSC) (Preemption)

40 H352Hf: Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands

Sent by MSC) (Invalid Message)

41 H352Hg: Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear CommandsSent by MSC) (Protocol Error between BSS and MSC)

42 H352Hh: Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands

Sent by MSC) (Other Causes)

43 H352G: Failed Outgoing Inter-RAT Inter-Cell Handovers (A-Interface Failure)

44 H352L: Failed Outgoing Inter-RAT Inter-Cell Handovers (T7 Expired)

45 H352C: Failed Outgoing Inter-RAT Inter-Cell Handovers (T8 Expired)

Meaning

This type of counters measures the number of failed outgoing inter-RAT inter-cell handovers

based on the channel type and failure cause. Here, the handover excludes directed retry.

Along with Outgoing Inter-RAT Inter-Cell Handover Requests per Cell and Outgoing Inter-RAT Inter-Cell Handover Commands per Cell, this type of counters can help you to better

understand the situation of outgoing inter-RAT inter-cell handovers.

Along with Incoming Inter-RAT Inter-Cell Handover Measurement per Cell, this type ofcounters can help you to better understand the situation of all outgoing inter-RAT inter-cell

handovers.

The channel type may be SDCCH, TCHH, or TCHF. The directed retry procedure applies to

only traffic channels.

The failure cause may be one of the following:

Handover request rejected

Reconnected to the old channel, excluding directed retry

Command from the MSC cleared

The A interface failed

T7 or T8 timer expired



12 Call Measurement




Trigger Point

The measurement is triggered at any of points A to H as shown in Figure 12-28 and Figure 12-

29.

Figure 12-28 Outgoing inter-RAT inter-cell handover procedure (excluding directed retry)


MR FROM MS

HO RQD

HO CMD

CLR CMD

SEND END SIG

C

G

T7 expired

A

E

In the

outgoing

inter-RAT

inter-cell

handover

procedure

PERFORM HO

Handover failed

HO RQD REJ

HO CMD

HO FAIL

D

H

T8 expired

CLR CMP

F






Figure 12-29 Outgoing inter-RAT inter-cell handover procedure (including directed retry)


HO CMD

CLR CMD

SEND END SIG

C

G

T7 expired

B

E

In the

outgoing

inter-RAT

inter-cell

handover

procedure

PERFORM HO

Handover failed

HO RQD

HO CMD

H

T8 expired

CLR CMP

F

ASSIGN REQ

HO RQD REJ

A: Failed Outgoing Inter-RAT Inter-Cell Handovers (Excluding Directed Retry)

B: Failed Outgoing Inter-RAT Inter-Cell Handovers (Directed Retry)

C: Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected)

E: Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent by MSC)

F: Failed Outgoing Inter-RAT Inter-Cell Handovers (A-Interface Failure)

G: Failed Outgoing Inter-RAT Inter-Cell Handovers (T7 Expired)H: Failed Outgoing Inter-RAT Inter-Cell Handovers (T8 Expired)

Failed Outgoing Inter-RAT Inter-Cell Handovers (Excluding Directed Retry)

As shown in Figure 12-28, the measurement is triggered when an outgoing inter-RAT

inter-cell handover (excluding directed retry) fails. The measurement is based on thechannel type.

The channel type may be SDCCH, TCHH, or TCHF.

Failed Outgoing Inter-RAT Inter-Cell Handovers (Directed Retry)

As shown in Figure 12-29, the measurement is triggered when an outgoing inter-RATinter-cell handover (including directed retry) fails. The measurement is based on thechannel type.

The channel type may be TCHH or TCHF.

Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected)

As shown in Figure 12-28 and Figure 12-29, the measurement is triggered when MSC 2sends an HO RQD REJ message to BSC 2 during an outgoing inter-RAT inter-cellhandover (including directed retry). The measurement is based on the rejection cause.

The rejection causes are as follows:

− OM intervention





12 Call Measurement






− Invalid Cell



− Requested Speech version unavailable



− Invalid message


− Other causes

Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels)

As shown in Figure 12-28, the measurement is triggered when the MS sends an HO

FAIL message to BSC 2 through the source cell after failing to access the new system inthe target cell and returning to the old channel during an outgoing inter-RAT inter-cellhandover (excluding directed retry). The measurement is based on the RR cause.

The RR causes for handover failure are as follows:



− Abnormal release, timer expired













− Protocol error unspecified− Other causes

Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent by MSC)

As shown in Figure 12-28 and Figure 12-29, the measurement is triggered when BSC 2

receives a CLR CMD message from MSC 2 during an outgoing inter-RAT inter-cellhandover (including directed retry). The measurement is based on the clearance cause.

The clearance causes are as follows:



− OM intervention







− Preemption

− Invalid message


− Other causes

Failed Outgoing Inter-RAT Inter-Cell Handovers (A-Interface Failure)


receives a message indicating that the A interface fails during an outgoing inter-RATinter-cell handover (including directed retry).


As shown in Figure 12-28 and Figure 12-29, the measurement is triggered when BSC 2does not receive an HO CMD message from MSC 2 before T7 expires during anoutgoing inter-RAT inter-cell handover (including directed retry).



does not receive a CLR CMD message from MSC 2 before T8 expires during anoutgoing inter-RAT inter-cell handover (including directed retry).

Formula

None.

12.16.5 Outgoing Inter-RAT Inter-Cell Handover AnalyzedMeasurement per Cell

Counter

Table 12-75 lists the counters of Outgoing Inter-RAT Inter-Cell Handover Analyzed


Table 12-75 Counters of Outgoing Inter-RAT Inter-Cell Handover Analyzed Measurement per

Cell

Number Counter

1 CH350: Outgoing Inter-RAT Inter-Cell Handover Requests

2 CH353: Successful Outgoing Inter-RAT Inter-Cell Handovers

3 TH353: Success Rate of Outgoing Inter-RAT Inter-Cell Handover

4 CH351: Outgoing Inter-RAT Inter-Cell Handover Commands

5 CH352: Failed Outgoing Inter-RAT Inter-Cell Handovers

6 CH352D: Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection toOld Channels)

7 CH352K: Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover

Request Rejected)

8 CH352H: Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands

Sent by MSC)



12 Call Measurement




Meaning

None.

Trigger Point None.

Formula

Outgoing Inter-RAT Inter-Cell Handover Requests =

[Outgoing Inter-RAT Inter-Cell Handover Requests (SDCCH) (Excluding Directed Retry)] +

[Outgoing Inter-RAT Inter-Cell Handover Requests (TCHF)] +

[Outgoing Inter-RAT Inter-Cell Handover Requests (TCHH)]

Successful Outgoing Inter-RAT Inter-Cell Handovers =

[Outgoing Inter-RAT Inter-Cell Handover Requests (SDCCH) (Excluding Directed Retry)] +

[Outgoing Inter-RAT Inter-Cell Handover Requests (TCHF)] +

[Outgoing Inter-RAT Inter-Cell Handover Requests (TCHH)]-

[Failed Outgoing Inter-RAT Inter-Cell Handovers (SDCCH) (Excluding Directed Retry)]-

[Failed Outgoing Inter-RAT Inter-Cell Handovers (TCHF)]-

[Failed Outgoing Inter-RAT Inter-Cell Handovers (TCHH)]

Success Rate of Outgoing Inter-RAT Inter-Cell Handover =

[Successful Outgoing Inter-RAT Inter-Cell Handovers]*{100}/[Outgoing Inter-RAT Inter-Cell

Handover Requests]

Outgoing Inter-RAT Inter-Cell Handover Commands =

[Outgoing Inter-RAT Inter-Cell Handover Commands (SDCCH) (Excluding Directed Retry)]

+

[Outgoing Inter-RAT Inter-Cell Handover Commands (TCHF)] +

[Outgoing Inter-RAT Inter-Cell Handover Commands (TCHH)]

Failed Outgoing Inter-RAT Inter-Cell Handovers =

[Failed Outgoing Inter-RAT Inter-Cell Handovers (SDCCH) (Excluding Directed Retry)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (TCHF)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (TCHH)]






Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels)=

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal

Release, Unspecified)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (AbnormalRelease, Channel Unacceptable)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (AbnormalRelease, Timer Expired)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal

Release, No Activity on the Radio Path)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels)(Preemptive Release)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Handover


[Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (ChannelMode Unavailable)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels)(Frequency Unavailable)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Call

Already Cleared)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels)(Semantically Incorrect Message)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Invalid


[Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (MessageType Non-existent or Not Implemented)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (MessageType Not Compatible with Protocol State)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels)

(Conditional IE Error)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (No CellAllocation Available)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (ProtocolError Unspecified)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (OtherCauses)]

Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected)=

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (OM

Intervention)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (EquipmentFailure)] +



12 Call Measurement




[Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (No RadioResource Available)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (Requested

Terrestrial Resource Unavailable)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (BSS not

Equipped)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (Invalid Cell)]+

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (RequestedTranscoding/Rate Adaption Unavailable)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (Circuit Pool

Mismatch)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (Requested

Speech Version Unavailable)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (Ciphering

Algorithm not Supported)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (Terrestrialcircuit already allocated)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (InvalidMessage)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (Protocol

Error between BSS and MSC)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (OtherCauses)]

Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent by MSC)=

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent by MSC) (Radio

Interface Message Failure)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent by MSC) (Radio

Interface Failure)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent by MSC) (OM

Intervention)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent by MSC)(Equipment Failure)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent by MSC)

(Preemption)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent by MSC) (Invalid

Message)] +

[Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent by MSC) (ProtocolError between BSS and MSC)] +






[Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent by MSC) (OtherCauses)]

12.17 GSM Cell to GSM Cell Incoming HandoverMeasurement

12.17.1 Overview

GSM Cell to GSM Cell Incoming Handover refers to a handover in which the MS is handedover to the target cell from the source cell.

GSM Cell to GSM Cell Incoming Handover Measurement aims to measure the following twotypes of handover:

After receiving a measurement report from the MS, the BSC decides to perform a

handover based on the interference of the current channel, the load of the cell, and themeasurement report, which indicates the signal quality, strength, and TX/RX level.

After receiving an ASSIGN REQ message from the MSC, the BSC decides theassignment mode based on the load of the cell. There are three assignment procedures:

normal assignment procedure, directed retry procedure, and assignment modification procedure. If the load of the cell is so high that the cell cannot admit a new service or

that a new service will affect current services, the BSC decides to perform a handoverthrough directed retry.

The incoming handover procedure is as follows:

Step 1 The main processing module of the BSC receives an intra-BSC handover triggering indication

from the handover algorithm, an inter-BSC HO REQ message from the MSC, or a request forhandover during directed retry.

Step 2 The BSC sends an inter-BSC HO REQ message to the target cell through the MSC or directly

requests channel resources from the target cell controlled by the same BSC for channel

resources.

Step 3 The BSC sends an HO CMD message to the MS through the source cell after the request

succeeds.

Step 4 The MS accesses the network through the target cell by receiving/sending messages such asHO ACC, PHY INFO, FIRST SABM, and UA.

Step 5 The MS sends an HO CMP message to the BSC through the target cell and releases the

resources of the source cell.

----End

Table 12-76 lists the counter types of GSM Cell to GSM Cell Incoming Handover

Measurement.

Table 12-76 Counter types of CGSM Cell to GSM Cell Incoming Handover Measurement


Cell Incoming Handover Requests (Cell to Cell) 12.17.2



12 Call Measurement





Failed Cell Incoming Handovers (Cell to Cell) 12.17.3

Cell Incoming Handover Analyzed Measurement (Cell to Cell) 12.17.4

Incoming Cell Handover Requests (Timing Advance) (Cell to Cell) 12.17.5

12.17.2 Cell Incoming Handover Requests (Cell to Cell)

Counter

H380: Cell Incoming Handover Requests

MeaningThis counter measures the number of Cell Incoming Handover Requests.

Along with Failed Cell Incoming Handovers (Cell to Cell), this counter can help you to better

understand the situation of inter-cell incoming handovers.

Along with GSM Cell to GSM Cell Outgoing Handover Measurement, this counter can helpyou to better understand the situation of inter-cell handovers.

Trigger Point

The measurement is triggered when an incoming handover occurs between different cells.

Formula

None.

12.17.3 Failed Cell Incoming Handovers (Cell to Cell)

Counter

Table 12-77 lists the counter of Failed Cell Incoming Handovers (Cell to Cell).

Table 12-77 Counter of Failed Cell Incoming Handovers (Cell to Cell)

Number Counter

1 H382A: Failed Cell Incoming Handovers (Congestion)

2 H382M: Failed Cell Incoming Handovers (Other Causes)

Meaning

This type of counters measures the number of inter-cell incoming handover failures based on

the failure cause.






Along with Cell Incoming Handover Requests (Cell to Cell), this counter can help you to better under stand the situation of inter-cell incoming handovers.

Along with GSM Cell to GSM Cell Outgoing Handover Measurement, this counter can help

you to better understand the situation of inter-cell handovers.

The failure cause may be congestion or others.

The counter H382M: Failed Cell Incoming Handovers (Other Causes) also includes directed retry(handover cause).

Trigger Point

The measurement is triggered when an inter-cell incoming handover fails. The measurement

is based on the failure cause.

Formula None.

12.17.4 Cell Incoming Handover Analyzed Measurement (Cell toCell)

Counter

Table 12-78 lists the counters of Cell Incoming Handover Analyzed Measurement (Cell to

Cell).

Table 12-78 Counters of Cell Incoming Handover Analyzed Measurement (Cell to Cell)

Number Counter

1 RH383: Success Rate of Cell Incoming Handovers

2 H382: Failed Cell Incoming Handovers

3 H383: Successful Cell Incoming Handovers

Meaning None.

Trigger Point

None.

Formula

Success Rate of Cell Incoming Handovers =

[Successful Cell Incoming Handovers]*{100}/[Cell Incoming Handover Requests]



12 Call Measurement




Failed Cell Incoming Handovers =

[Failed Cell Incoming Handovers (Congestion)] +

[Failed Cell Incoming Handovers (Other Causes)]

Successful Cell Incoming Handovers =

[Cell Incoming Handover Requests]-[Failed Cell Incoming Handovers]

12.17.5 Incoming Cell Handover Requests (Timing Advance) (Cellto Cell)

Counter

CH347: Incoming Cell Handover Requests (Timing Advance)

Meaning

This counter measures the number of incoming cell handover requests. The handover cause istiming advance.

Trigger Point

As long as the source cell and the object cell are different, this counter is measured based onthe handover cause.

Formula None.

12.18 GSM Cell to GSM Cell Outgoing HandoverMeasurement

12.18.1 Overview

GSM Cell to GSM Cell Outgoing Handover refers to a handover in which the MS is handedover from the source cell to the target cell.

GSM Cell to GSM Cell Outgoing Handover Measurement aims to measure the following two

types of handover:

After receiving a measurement report from the MS, the BSC decides to perform a

handover based on the interference of the current channel, the load of the cell, and themeasurement report, which indicates the signal quality, strength, and TX/RX level.

After receiving an ASSIGN REQ message from the MSC, the BSC decides the

assignment mode based on the load of the cell. There are three assignment procedures:normal assignment procedure, directed retry procedure, and assignment modification procedure. If the load of the cell is so high that the cell cannot admit a new service or






that a new service will affect current services, the BSC decides to perform a handoverthrough directed retry.

The outgoing handover procedure is as follows:

Step 1 The main processing module of the BSC receives an intra-BSC handover triggering indicationfrom the handover algorithm, an inter-BSC HO REQ message from the MSC, or a request for

handover during directed retry.

Step 2 The BSC sends an inter-BSC HO REQ message to the target cell through the MSC or directly

requests channel resources from the target cell controlled by the same BSC for channelresources.

Step 3 The target cell responds to the HO REQ message after the request and preparation succeed.

Step 4 The BSC sends an HO CMD message to the MS through the source cell.

Step 5 The MS accesses the network through the target cell by receiving/sending messages such asHO ACC, PHY INFO, FIRST SABM, and UA.

Step 6 The MS sends an HO CMP message to the BSC through the target cell and releases the

resources of the source cell.

----End

Table 12-79 lists the counter types of GSM Cell to GSM Cell Outgoing Handover.

Table 12-79 Counter types of GSM Cell to GSM Cell Outgoing Handover


Cell Outgoing Handover Commands (Cell to Cell) 12.18.2

Failed Cell Outgoing Handovers (Cell to Cell) 12.18.3

Cell Outgoing Handover Analyzed Measurement (Cell to Cell) 12.18.4

12.18.2 Cell Outgoing Handover Commands (Cell to Cell)

Counter

Table 12-80 lists the counters of Cell Outgoing Handover Commands (Cell to Cell).

Table 12-80 Counters of Cell Outgoing Handover Commands (Cell to Cell)

Number Counter

1 H371A: Cell Outgoing Handover Commands (Uplink Quality)

2 H371B: Cell Outgoing Handover Commands (Downlink Quality)

3 H371C: Cell Outgoing Handover Commands (Uplink Strength)

4 H371D: Cell Outgoing Handover Commands (Downlink Strength)

5 H371E: Cell Outgoing Handover Commands (Timing Advance)



12 Call Measurement




Number Counter

6 H371F: Cell Outgoing Handover Commands (Better Cell)

7 H371G: Cell Outgoing Handover Commands (Load)

8 H371H: Cell Outgoing Handover Commands (Rapid Level Drop)

9 H371I: Cell Outgoing Handover Commands (MSC Intervention)

10 H371J: Cell Outgoing Handover Commands (OM Intervention)

11 H371L: Cell Outgoing Handover Commands (Other Causes)

Meaning

This counter measures the number of Cell Outgoing Handover Commands.

Along with Failed Cell Outgoing Handovers (Cell to Cell), this counter can help you to better

understand the situation of outgoing handovers between different cells.

Along with GSM Cell to GSM Cell Incoming Handover Measurement, this counter can helpyou to better understand the situation of inter-cell handovers.

The triggering conditions of inter-cell outgoing handover are as follows:

Uplink Quality

Downlink Quality

Uplink Strength

Downlink Strength

Timing Advance

Better Cell

Cell Load

Rapid Level Drop

MSC Intervention

OM Intervention

EDGE coverage

Other Causes

The counter H371L: Cell Outgoing Handover Commands (Other Causes) also includes directed retry(handover cause).

Trigger Point

The measurement is triggered when an outgoing handover occurs between different cells.

Formula

None.






12.18.3 Failed Cell Outgoing Handovers (Cell to Cell)

Counter

Table 12-81 lists the counters of Failed Cell Outgoing Handovers (Cell to Cell).

Table 12-81 Counters of Failed Cell Outgoing Handovers (Cell to Cell)

Number Counter

1 H372A: Failed Cell Outgoing Handovers (Uplink Quality)

2 H372B: Failed Cell Outgoing Handovers (Downlink Quality)

3 H372C: Failed Cell Outgoing Handovers (Uplink Strength)

4 H372D: Failed Cell Outgoing Handovers (Downlink Strength)

5 H372E: Failed Cell Outgoing Handovers (Timing Advance)

6 H372F: Failed Cell Outgoing Handovers (Better Cell)

7 H372G: Failed Cell Outgoing Handovers (Load)

8 H372H: Failed Cell Outgoing Handovers (Rapid Level Drop)

9 H372I: Failed Cell Outgoing Handovers (MSC Intervention)

10 H372J: Failed Cell Outgoing Handovers (OM Intervention)

11 H372L: Failed Cell Outgoing Handovers (Other Causes)

Meaning

This type of counters measures the number of inter-cell outgoing handover failures based on

the triggering cause.

Along with Cell Outgoing Handover Commands (Cell to Cell), this counter can help you to better understand the situation of outgoing handovers between different cells.

Along with GSM Cell to GSM Cell Incoming Handover Measurement, this counter can helpyou to better understand the situation of inter-cell handovers.

The triggering conditions of inter-cell outgoing handover are as follows:

Uplink Quality

Downlink Quality

Uplink Strength

Downlink Strength

Timing Advance

Better Cell

Cell Load

Rapid Level Drop

MSC Intervention



12 Call Measurement




OM Intervention

EDGE coverage

Other Causes

The counter H372L: Failed Cell Outgoing Handovers (Other Causes) also includes directed retry(handover cause).

Trigger Point

The measurement is triggered when an outgoing handover occurs between different cells.

Formula

None.

12.18.4 Cell Outgoing Handover Analyzed Measurement (Cell toCell)

Counter

Table 12-82 lists the counters of Cell Outgoing Handover Analyzed Measurement (Cell to

Cell).

Table 12-82 Counters of Cell Outgoing Handover Analyzed Measurement

Number Counter

1 RH373: Success Rate of Cell Outgoing Handovers

2 H371: Cell Outgoing Handover Commands

3 H372: Failed Cell Outgoing Handovers

4 H373: Successful Cell Outgoing Handovers

Meaning

None.

Trigger Point

None.

Formula

Success Rate of Cell Outgoing Handovers =

[Successful Cell Outgoing Handovers]*{100}/[Cell Outgoing Handover Commands]

Cell Outgoing Handover Commands =






[Cell Outgoing Handover Commands (Uplink Quality)] +

[Cell Outgoing Handover Commands (Downlink Quality)] +

[Cell Outgoing Handover Commands (Uplink Strength)] +

[Cell Outgoing Handover Commands (Downlink Strength)] +

[Cell Outgoing Handover Commands (Timing Advance)] +

[Cell Outgoing Handover Commands (Better Cell)] +

[Cell Outgoing Handover Commands (Load)] +

[Cell Outgoing Handover Commands (Rapid Level Drop)] +

[Cell Outgoing Handover Commands (MSC Intervention)] +

[Cell Outgoing Handover Commands (OM Intervention)] +

[Cell Outgoing Handover Commands (Other Causes)]

Failed Cell Outgoing Handovers =

[Failed Cell Outgoing Handovers (Uplink Quality)] +

[Failed Cell Outgoing Handovers (Downlink Quality)] +

[Failed Cell Outgoing Handovers (Uplink Strength)] +

[Failed Cell Outgoing Handovers (Downlink Strength)] +

[Failed Cell Outgoing Handovers (Timing Advance)] +

[Failed Cell Outgoing Handovers (Better Cell)] +

[Failed Cell Outgoing Handovers (Load)] +

[Failed Cell Outgoing Handovers (Rapid Level Drop)] +

[Failed Cell Outgoing Handovers (MSC Intervention)] +

[Failed Cell Outgoing Handovers (OM Intervention)] +

[Failed Cell Outgoing Handovers (Other Causes)]

Successful Cell Outgoing Handovers =

[Cell Outgoing Handover Commands]-[Failed Cell Outgoing Handovers]

12.19 Measurement of MRs upon Handover Initiation perCell

12.19.1 Overview

Measurement of MRs upon Handover Initiation per Cell is used to measure the receiving level,

receiving quality, and timing advance (TA) status reported in handover.



12 Call Measurement




Table 12-83 lists the counter types of Measurement of MRs upon Handover Initiation per Cell.

Table 12-83 Counter types of Measurement of MRs upon Handover Initiation per Cell


Measurement of MRs upon Handover Initiation (Receiving Quality) per Cell 12.19.2

Mean Uplink Receiving Level during Handover Initiation per Cell 12.19.3

Mean Uplink Receiving Quality during Handover Initiation per Cell 12.19.4

Concentric Cell Handover Initiation MR Analyzed Measurement (Receiving

Level) per Cell 12.19.5

Concentric Cell Handover Initiation MR Analyzed Measurement (TimingAdvance) per Cell

12.19.6

12.19.2 Measurement of MRs upon Handover Initiation(Receiving Quality) per Cell

Counter

Table 12-84 lists the counters of Measurement of MRs upon Handover Initiation (Receiving

Quality) per Cell.

Table 12-84 Counters of Measurement of MRs upon Handover Initiation (Receiving Quality) per

Cell

Number Counter

1 S3300C: Number of MRs during Handover Initiation (Uplink Receiving Level

Rank = 0)

2 S3301C: Number of MRs during Handover Initiation (Uplink Receiving LevelRank = 1)



Rank = 3)


Rank = 4)




Rank = 7)






Number Counter

9 S3310C: Number of MRs during Handover Initiation (Uplink Receiving

Quality Rank = 0)

10 S3311C: Number of MRs during Handover Initiation (Uplink ReceivingQuality Rank = 1)



Quality Rank = 3)



Quality Rank = 5)



Quality Rank = 7)

Meaning

After receiving a valid measurement report from an MS or a valid preprocessing measurement

report from a BTS, the BSC decides whether to initiate a handover after a decision. Ifdeciding to initiate a handover, the BSC triggers the counters based on the receiving level (1– 7) and the receiving quality (1–7).

Trigger Point

The measurement is triggered when the BSC decides to initiate a handover based on a valid

measurement report from an MS or a valid preprocessing measurement report from a BTS.

Formula

None.

12.19.3 Mean Uplink Receiving Level during Handover Initiationper Cell

Counter

AS330C: Mean Uplink Receiving Level during Handover Initiation

Meaning


report from a BTS, the BSC sums up the uplink receiving level based on the measurement



12 Call Measurement




report if deciding to initiate a handover. At the end of the measurement period, the BSCdivides the sum by the number of handover initiations to obtain the Mean Uplink ReceivingLevel during Handover Initiation.

Trigger Point None.

Formula

Mean Uplink Receiving Level during Handover Initiation =

Uplink Receiving Level during Handover Initiation/

(Outgoing External Inter-Cell Handover Requests+

Outgoing Internal Inter-Cell Handover Requests+

Internal Intra-Cell Handover Requests (SDCCH) +

Internal Intra-Cell Handover Requests (TCH))

12.19.4 Mean Uplink Receiving Quality during HandoverInitiation per Cell

Counter

AS331C: Mean Uplink Receiving Quality during Handover Initiation

MeaningAfter receiving a valid measurement report from an MS or a valid preprocessing measurementreport from a BTS, the BSC sums up the uplink receiving quality based on the measurement

report if deciding to initiate a handover. At the end of the measurement period, the BSCdivides the sum by the number of handover initiations to obtain the Mean Uplink Receiving

Quality during Handover Initiation.

Trigger Point

None.

Formula

Mean Uplink Receiving Quality during Handover Initiation =

Uplink Receiving Quality during Handover Initiation/

(Outgoing External Inter-Cell Handover Requests+

Inter-BSC Cell Outgoing Handover Requests +

Internal Intra-Cell Handover Requests (SDCCH) +

Internal Intra-Cell Handover Requests (TCH))






12.19.5 Concentric Cell Handover Initiation MR AnalyzedMeasurement (Receiving Level) per Cell

CounterTable 12-85 lists the counters of Concentric Cell Handover Initiation MR AnalyzedMeasurement (Receiving Level) per Cell.

Table 12-85 Counters of Concentric Cell Handover Initiation MR Analyzed Measurement(Receiving Level) per Cell

Number Counter

1 AS330A: Mean Uplink Receiving Level during Concentric Cell Handover

Initiation (Overlay to Underlay)

2 AS332A: Mean Downlink Receiving Level during Concentric Cell HandoverInitiation (Overlay to Underlay)

3 AS330B: Mean Uplink Receiving Level during Concentric Cell HandoverInitiation (Underlay to Overlay)

4 AS332B: Mean Downlink Receiving Level during Concentric Cell HandoverInitiation (Underlay to Overlay)

Meaning


report from a BTS, the BSC adds the reported uplink receiving level to the counter UplinkReceiving Level during Concentric Cell Handover Initiation (Overlay to Underlay) if deciding

to initiate an overlay-to-underlay handover. In this case, the BSC also adds the downlinkreceiving level to the counter Downlink Receiving Level during Concentric Cell Handover

Initiation (Overlay to Underlay).

At the end of the measurement report, the BSC respectively divides the two sums by thenumber of Internal Intra-Cell Handover Requests (Overlay to Underlay) to obtain the Mean

Uplink Receiving Level during Concentric Cell Handover Initiation (Overlay to Underlay)

and the Mean Downlink Receiving Level during Concentric Cell Handover Initiation(Overlay to Underlay).


report from a BTS, the BSC adds the reported uplink receiving level to the counter UplinkReceiving Level during Concentric Cell Handover Initiation (Underlay to Overlay) if decidingto initiate an underlay-to-overlay handover. In this case, the BSC also adds the downlink

receiving level to the counter Downlink Receiving Level during Concentric Cell Handover

Initiation (Underlay to Overlay).

At the end of the measurement report, the BSC respectively divides the two sums by the

number of Internal Intra-Cell Handover Requests (Underlay to Overlay) to obtain the Mean

Uplink Receiving Level during Concentric Cell Handover Initiation (Underlay to Overlay)and the Mean Downlink Receiving Level during Concentric Cell Handover Initiation(Underlay to Overlay).



12 Call Measurement




Trigger Point

None.

FormulaMean Uplink Receiving Level during Concentric Cell Handover Initiation (Overlay to

Underlay)=

Uplink Receiving Level during Concentric Cell Handover Initiation (Overlay toUnderlay)/Internal Intra-Cell Handover Requests (Overlay to Underlay)

Mean Downlink Receiving Level during Concentric Cell Handover Initiation (Overlay to

Underlay)=

Downlink Receiving Level during Concentric Cell Handover Initiation (Overlay toUnderlay)/Internal Intra-Cell Handover Requests (Overlay to Underlay)

Mean Uplink Receiving Level during Concentric Cell Handover Initiation (Underlay toOverlay)=

Uplink Receiving Level during Concentric Cell Handover Initiation (Underlay to

Overlay)/Internal Intra-Cell Handover Requests (Underlay to Overlay)

Mean Downlink Receiving Level during Concentric Cell Handover Initiation (Underlay toOverlay)=

Downlink Receiving Level during Concentric Cell Handover Initiation (Underlay to

Overlay)/Internal Intra-Cell Handover Requests (Underlay to Overlay)

12.19.6 Concentric Cell Handover Initiation MR Analyzed

Measurement (Timing Advance) per Cell

Counter

Table 12-86 lists the counter of Concentric Cell Handover Initiation MR Analyzed

Measurement (Timing Advance) per Cell.

Table 12-86 Counters of Concentric Cell Handover Initiation MR Analyzed Measurement(Timing Advance) per Cell

Number Counter

1 AS334A: Mean Timing Advance during Concentric Cell Handover Initiation(Overlay to Underlay)

2 AS334B: Mean Timing Advance during Concentric Cell Handover Initiation(Underlay to Overlay)

Meaning


report from a BTS, the BSC adds the reported TA to the counter Timing Advance Level






during Concentric Cell Handover Initiation (Overlay to Underlay) if deciding to initiate anoverlay-to-underlay handover.

At the end of the measurement period, the BSC divides the sum by the number of Internal

Intra-Cell Handover Requests (Overlay to Underlay) to obtain the Mean Timing Advance

during Concentric Cell Handover Initiation (Overlay to Underlay).


report from a BTS, the BSC adds the reported TA to the counter Timing Advance Levelduring Concentric Cell Handover Initiation (Underlay to Overlay) if deciding to initiate anunderlay-to-overlay handover.

At the end of the measurement period, the BSC divides the sum by the number of InternalIntra-Cell Handover Requests (Underlay to Overlay) to obtain the Mean Timing Advanceduring Concentric Cell Handover Initiation (Underlay to Overlay).

Trigger Point

None.

Formula

Mean Timing Advance during Concentric Cell Handover Initiation (Overlay to Underlay)

= Timing Advance during Concentric Cell Handover Initiation (Overlay to Underlay)/InternalIntra-Cell Handover Requests (Overlay to Underlay)

Mean Timing Advance during Concentric Cell Handover Initiation (Underlay to Overlay)

= Timing Advance during Concentric Cell Handover Initiation (Underlay to Overlay)/Internal

Intra-Cell Handover Requests (Underlay to Overlay)

12.20 KPI Measurement per Cell

12.20.1 Overview

Table 12-87 lists the counters of KPI Measurement per Cell.

Table 12-87 Counters of KPI Measurement per Cell

Number Counter

1 K3100: Immediate Assignment Requests

2 K3101: Immediate Assignment Commands

3 K3000: SDCCH Seizure Requests

4 K3001: Failed SDCCH Seizures due to Busy SDCCH

5 K3003: Successful SDCCH Seizures

6 K3004: Traffic Volume on SDCCH

7 K3005: Available SDCCHs



12 Call Measurement




Number Counter

8 K3006: Configured SDCCHs

9 K3020: TCH Seizure Requests (Signaling Channel)

10 K3021: Failed TCH Seizures due to Busy TCH (Signaling Channel)

11 K3023: Successful TCH Seizures (Signaling Channel)

12 K3022: Call Drops on TCH (Signaling Channel)

13 K3024: Traffic Volume on TCH (Signaling Channel)

14 K3010A: TCH Seizure Requests (Traffic Channel)

15 K3011A: Failed TCH Seizures due to Busy TCH (Traffic Channel)

16 K3013A: Successful TCH Seizures (Traffic Channel)

17 K3012A: Call Drops on TCH in Stable State (Traffic Channel)

18 K3010B: TCH Seizure Requests in TCH Handovers (Traffic Channel)

19 K3011B: Failed TCH Seizures in TCH Handovers due to Busy TCH (TrafficChannel)

20 K3013B: Successful TCH Seizures in TCH handovers (Traffic Channel)

21 K3012B: Call Drops in TCH Handovers (Traffic Channel)

22 K3014: Traffic Volume on TCH (Traffic Channel)

23 K3015: Available TCHs

24 K3016: Configured TCHs

25 K3170: Dual-Band Handover Requests

26 K3173: Successful Dual-Band Handovers

12.20.2 Immediate Assignment Requests

CounterK3100: Immediate Assignment Requests

Meaning

To obtain the service from the network, an MS sends a CHAN REQ message. After receiving

this message, the BTS sends a CHAN RQD message to the BSC for a dedicated channel. Thiscounter applies to the channel accesses due to all causes but packet services.

Trigger Point

None.






Formula

Immediate Assignment Requests =

[Channel Requests (Circuit Service)]

12.20.3 Immediate Assignment Commands

Counter

K3101: Immediate Assignment Commands

Meaning

In an immediate assignment procedure, the MS reports a CHAN REQ message to the BTS.The BTS sends a CHAN RQD message to the BSC. The BSC allocates a signaling channel

for the MS and activates the channel. If the BSC receives a CHAN ACTIV ACK messagefrom the BTS, it is an indication that the BTS already prepares the channel. The BSC sends an

IMM ASSIGN CMD message to the MS, instructing the MS to access the specified signalingchannel. This channel may be an SDCCH or TCH. This counter applies to the channel

accesses due to all causes but packet services.

Trigger Point

None.

Formula

Immediate Assignment Commands =

[Immediate Assignment Commands (Circuit Service)]

12.20.4 SDCCH Seizure Requests

Counter

K3000: SDCCH Seizure Requests

Meaning

In an immediate assignment procedure, the MS requests a channel from the BSS. In an inter-BSC incoming handover procedure, the MSC requests the BSS to allocate a channel for the

MS. In an intra-BSC incoming handover procedure, the BSC requests a channel from the BSS.

In the procedures mentioned previously, the BSC triggers the counter after receiving a requestfor SDCCH.

Trigger Point

None.

Formula

SDCCH Seizure Requests =



12 Call Measurement




[Channel Assignment Requests in Immediate Assignment Procedure (SDCCH)] +

[Internal Intra-Cell Handover Requests (SDCCH)] +








[Incoming External Inter-Cell Handover Requests (SDCCH) (1800/1900-900/850)]

12.20.5 Failed SDCCH Seizures due to Busy SDCCH

Counter

K3001: Failed SDCCH Seizures due to Busy SDCCH

Meaning

In an immediate assignment procedure or a handover procedure, the BSC triggers the counter

when the MS or MSC requests an SDCCH from the BSS but no SDCCH is available.

Trigger Point None.

Formula

Failed SDCCH Seizures due to Busy SDCCH =

[Failed Channel Assignments due to Busy or Not Configured Channels in ImmediateAssignment Procedure (SDCCH)] +

[Failed Internal Intra-Cell Handovers (Channel Unavailable) (SDCCH)] +

[Failed Incoming Internal Inter-Cell Handovers (Channel Unavailable) (SDCCH)] +

[Failed Incoming External Inter-Cell Handovers (Channel Unavailable) (SDCCH)]

12.20.6 Successful SDCCH Seizures

Counter

K3003: Successful SDCCH Seizures






Meaning

In an SDCCH immediate assignment procedure, the BTS sends a channel activation success

message to the BSC. After receiving this message, the BSC regards that the assignment of

SDCCH succeeds. In an SDCCH handover procedure, the BTS sends a handover detection

message to the target cell. After receiving this message, the BSC regards that the assignmentof SDCCH succeeds.

This counter applies to the previous two cases.

Trigger Point

None.

Formula

Successful SDCCH Seizures=

[Channel Activation Attempts in Immediate Assignment Procedure (SDCCH)]-

[CHAN ACTIV NACK Messages Sent by BTS in Immediate Assignment Procedure(SDCCH)]-

[Channel Activation Timeouts in Immediate Assignment Procedure (SDCCH)] +

[Internal Intra-Cell Handover Detection Messages Received by BSC (SDCCH)] +

[Incoming Internal Inter-Cell Handover Detection Messages Received by BSC (SDCCH)] +

[Incoming External Inter-Cell Handover Detection Messages Received by BSC (SDCCH)]

12.20.7 Traffic Volume on SDCCH

Counter

K3004: Traffic Volume on SDCCH

Meaning

This counter measures the ratio of the duration for which the MS occupies the SDCCH to themeasurement period. The duration for which the MS occupies the SDCCH is equal to the

number of reports from the MS on the SDCCH multiplied by the reporting period 0.47s.

Trigger Point

None.

Formula

Traffic Volume on SDCCH =

[Traffic Volume on Signaling Channel (SDCCH)]



12 Call Measurement




12.20.8 Traffic Volume on SDCCH

Counter

K3004: Traffic Volume on SDCCH

Meaning

The unit of this counter is Erlang.

Trigger Point

None.

Formula

Traffic Volume on SDCCH =

[Traffic Volume on Signaling Channel (SDCCH)]

12.20.9 Available SDCCHs

Counter

K3005: Available SDCCHs

Meaning

This counter measures the number of SDCCHs in idle or busy state in a cell of the BSC. Here,the SDCCHs include those obtained dynamically from TCHs. This counter is equal to the

total number of available SDCCHs divided by the number of sample points.

Trigger Point

None.

Formula

Available SDCCHs =

[Mean Number of Available Channels (SDCCH)]

12.20.10 Configured SDCCHs

Counter

K3006: Configured SDCCHs






Meaning

This counter measures the number of SDCCH configured for a cell of the BSC. Here, the

SDCCHs include those obtained dynamically from TCHs. This counter measures the mean

number of configured SDCCHs.

Trigger Point

None.

Formula

Configured SDCCHs =

[Mean Number of Configured Channels (SDCCH)]

12.20.11 TCH Seizure Requests (Signaling Channel)

Counter

K3021: TCH Seizure Requests (Signaling Channel)

Meaning

This counter measures the number of the CHAN RQD messages sent from the BTS to theBSC in an immediate TCH assignment procedure.

Trigger Point

None.

Formula

TCH Seizure Requests (Signaling Channel) =

[Channel Assignment Requests in Immediate Assignment Procedure (TCH)]

12.20.12 Failed TCH Seizures due to Busy TCH (SignalingChannel)

Counter

K3021: Failed TCH Seizures due to Busy TCH (Signaling Channel)

Meaning

This counter measures the times the BSC has no TCH (signaling channel) to allocate in an

immediate TCH assignment procedure.

Trigger Point

None.



12 Call Measurement




Formula

Failed TCH Seizures due to Busy TCH (Signaling Channel) =

[Channel Assignment Requests in Immediate Assignment Procedure (TCH)]-

[Immediate Assignment Commands (TCHF)]-

[Immediate Assignment Commands (TCHH)]

12.20.13 Successful TCH Seizures (Signaling Channel)

Counter

K3023: Successful TCH Seizures (Signaling Channel)

Meaning

This counter measures the number of successful activations of the TCHs (signaling channels)

allocated by the BSC in an immediate TCH assignment procedure.

Trigger Point

None.

Formula

Successful TCH Seizures (Signaling Channel) =

([Channel Activation Attempts in Immediate Assignment Procedure (TCHF)] +

[Channel Activation Attempts in Immediate Assignment Procedure (TCHH)])-

([CHAN ACTIV NACK Messages Sent by BTS in Immediate Assignment Procedure (TCHF)]+

[CHAN ACTIV NACK Messages Sent by BTS in Immediate Assignment Procedure (TCHH)]

+

[Channel Activation Timeouts in Immediate Assignment Procedure (TCHF)] +

[Channel Activation Timeouts in Immediate Assignment Procedure (TCHH)])

12.20.14 Call Drops on TCH (Signaling Channel)

Counter

K3022: Call Drops on TCH (Signaling Channel)

Meaning

This counter measures the number of call drops occurred although the MS sets up on the TCHa normal connection with the service type of signaling.






Trigger Point

None.

FormulaCall Drops on TCH (Signaling Channel) =

[Call Drops on Signaling Channel]-

[Call Drops on SDCCH]

12.20.15 Traffic Volume on TCH (Signaling Channel)

Counter

K3024: Traffic Volume on TCH (Signaling Channel)

Meaning

This counter measures the ratio of the duration for which the MS occupies the TCH (signaling

channel) to the measurement period. The duration for which the MS occupies the TCH isequal to the number of reports from the MS on the TCH multiplied by the reporting period

0.48s.

Trigger Point

None.

Formula

Traffic Volume on TCH (Signaling Channel) =

[Traffic Volume on Signaling Channel (TCH)]

12.20.16 TCH Seizure Requests (Traffic Channel)

Counter

K3010A: TCH Seizure Requests (Traffic Channel)

Meaning

This counter measures the number of TCH (traffic channel) seizure requests received by the

BSC from the MSC.

Trigger Point

None.

Formula

TCH Seizure Requests (Traffic Channel) =



12 Call Measurement




[Assignment Requests]

12.20.17 Failed TCH Seizures due to Busy TCH (Traffic Channel)

Counter

K3011A: Failed TCH Seizures due to Busy TCH (Traffic Channel)

Meaning


available.

Trigger Point

None.

Formula

Failed TCH Seizures due to Busy TCH (Traffic Channel) =

[Failed Assignments (Channel Unavailable)]

12.20.18 Successful TCH Seizures (Traffic Channel)

Counter

K3013A: Successful TCH Seizures (Traffic Channel)

Meaning

This counter measures the number of successful TCH (traffic channel) seizures by the MS.

Trigger Point

None.

Formula

Successful TCH Seizures (Traffic Channel) =

[Successful Assignments]

12.20.19 Call Drops on TCH in Stable State (Traffic Channel)

Counter

K3012A: Call Drops on TCH in Stable State (Traffic Channel)

Meaning

This counter measures the number of call drops occurred after the MS is in the stablecommunication state on the TCH (traffic channel).






Trigger Point

None.

FormulaCall Drops on TCH in Stable State (Traffic Channel) =


[Call Drops due to No MRs from MS for a Long Time (TCH)] +

[Call Drops due to Abis Terrestrial Link Failure (TCH)] +

[Call Drops due to Equipment Failure (TCH)] +

[Call Drops due to Forced Handover (TCH)]

12.20.20 TCH Seizure Requests in TCH Handovers (TrafficChannel)

Counter

K3010B: TCH Seizure Requests in TCH Handovers (Traffic Channel)

Meaning

In an intra-BSC incoming handover procedure, the MS requests the BSS to reallocate a TCH

(traffic channel). In an inter-BSC incoming handover procedure, the MSC requests the BSS to

reallocate a TCH (traffic channel).This counter measures the total number of TCH seizure requests in the procedures mentioned previously.

Trigger Point

None.

Formula

TCH Seizure Requests in TCH Handovers (Traffic Channel) =

[Internal Intra-Cell Handover Requests (TCH)] +










12 Call Measurement




[Incoming External Inter-Cell Handover Requests (TCH) (1800/1900-900/850)]

12.20.21 Failed TCH Seizures in TCH Handovers due to BusyTCH (Traffic Channel)

Counter

K3011B: Failed TCH Seizures in TCH Handovers due to Busy TCH (Traffic Channel)

Meaning


available in TCH handovers.

Trigger Point

None.

Formula

Failed TCH Seizures in TCH Handovers due to Busy TCH (Traffic Channel) =

[Failed Internal Intra-Cell Handovers (Channel Unavailable) (TCH)] +

[Failed Incoming Internal Inter-Cell Handovers (Channel Unavailable) (TCH)] +

[Failed Incoming External Inter-Cell Handovers (Channel Unavailable) (TCH)]

12.20.22 Successful TCH Seizures in TCH Handovers (TrafficChannel)

Counter

K3013B: Successful TCH Seizures in TCH Handovers (Traffic Channel)

Meaning

This counter measures the number of successful TCH (traffic channel) seizures by the MS

during TCH handovers.

Trigger Point

None.

Formula

Successful TCH Seizures in TCH Handovers (Traffic Channel) =

[Internal Intra-Cell Handover Detection Messages Received by BSC (TCHF)] +

[Internal Intra-Cell Handover Detection Messages Received by BSC (TCHH)] +

[Incoming Internal Inter-Cell Handover Detection Messages Received by BSC (TCHF)] +






[Incoming Internal Inter-Cell Handover Detection Messages Received by BSC (TCHH)] +

[Incoming External Inter-Cell Handover Detection Messages Received by BSC (TCHF)] +

[Incoming External Inter-Cell Handover Detection Messages Received by BSC (TCHH)]

12.20.23 Call Drops in TCH Handovers (Traffic Channel)

Counter

K3012B: Call Drops in TCH Handovers (Traffic Channel)

Meaning

This counter measures the number of call drops due to the radio interface during TCH (traffic

channel) handovers.

Trigger Point

None.

Formula

Call Drops in TCH Handovers (Traffic Channel) =

[Call Drops on Radio Interface in Handover State (TCH)]

12.20.24 Traffic Volume on TCH (Traffic Channel)

Counter

K3014: Traffic Volume on TCH (Traffic Channel)

Meaning

This counter measures the ratio of the duration for which the MS occupies the TCH (traffic

channel) to the measurement period. The duration for which the MS occupies the TCH isequal to the number of reports from the MS on the TCH multiplied by the reporting period0.48s.

Trigger Point None.

Formula

Traffic Volume on TCH (Traffic Channel) =

[Traffic Volume on TCH]



12 Call Measurement




12.20.25 Available TCHs

Counter

K3015: Available TCHs

Meaning

This counter measures the number of TCHs in idle or busy state in a cell of the BSC. Here,

the TCHs exclude the TCHs changed to SDCCHs through dynamic adjustment but include theTCHs obtained from PDCHs through dynamic adjustment. This counter is equal to the totalnumber of available TCHs divided by the number of sample points.

Trigger Point

None.

Formula

Available TCHs =

[Mean Number of Available Channels (TCH)]

12.20.26 Configured TCHs

Counter

K3016: Configured TCHs

Meaning

This counter s the number of TCHs configured for a cell of the BSC. Here, the TCHs exclude

the TCHs changed to SDCCHs through dynamic adjustment but include the TCHs obtainedfrom PDCHs through dynamic adjustment. This counter is equal to the total number of

configured TCHs divided by the number of sample points.

Trigger Point

None.

Formula

Configured TCHs =

[Mean Number of Configured Channels (TCH)]

12.20.27 Dual-Band Handover Requests

Counter

K3170: Dual-Band Handover Requests






Meaning

This counter measures the total number of intra-BSC and inter-BSC dual-band handover

requests.

Trigger Point

None.

Formula

Dual-Band Handover Requests =







(900/850-1800/1900)] +










[Outgoing External Inter-Cell Handover Requests (Directed Retry) (1800/1900-900/850)]

12.20.28 Successful Dual-Band Handovers

Counter

K3173: Successful Dual-Band Handovers



12 Call Measurement




Meaning

This counter measures the total number of successful intra-BSC and inter-BSC dual-band

handovers.

Trigger Point

None.

Formula

Successful Dual-Band Handovers=

([Incoming Internal Inter-Cell Handover Requests (SDCCH) (900/850-1800/1900)] +






(900/850-1800/1900)] +










[Outgoing External Inter-Cell Handover Requests (Directed Retry) (1800/1900-900/850)])-

([Failed Incoming Internal Inter-Cell Handovers (SDCCH) (900/850-1800/1900)] +





(900/850-1800/1900)] +






[Failed Outgoing External Inter-Cell Handovers (TCHF) (Excluding Directed Retry)(900/850-1800/1900)] +


(900/850-1800/1900)] +








(1800/1900-900/850)] +


(1800/1900-900/850)] +

[Failed Outgoing External Inter-Cell Handovers (Directed Retry) (1800/1900-900/850)])

12.21 Calls Discarded due to Overload per LAPD

12.21.1 Overview

The measurement unit Calls Discarded due to Overload per LAPD is used to measure thenumber of random access requests discarded on LAPD.

Table 12-88 lists the counter of Calls Discarded due to Overload per LAPD.

Table 12-88 Counter of Calls Discarded due to Overload per LAPD

Number Counter

1 A533: Random Access Requests Discarded on LAPD

12.21.2 Random Access Requests Discarded on LAPD

Counter

A533: Random Access Requests Discarded on LAPD

Meaning

If the number of random access messages exceeds those that can be processed in unit time,

usually 100ms, the BSC discards the new requests and triggers the counter.



12 Call Measurement




Trigger Point

The measurement is triggered when the BSC discards a new random access request because

of the upper limit of flow control exceeded.

Formula

None.




Performance Counter Reference 13 MR Measurement


13 MR Measurement

About This Chapter


Section Describes

13.1 Overview of MRMeasurement

Introduces the measurement units of MR Measurement.

13.2 Number of MRs per Cell Describes the functions and counters of Number of MRs per Cell.

13.3 Interference BandMeasurement per TRX Describes the functions and counters of Interference BandMeasurement.

13.4 Power Control Messages per Cell

Describes the functions and counters of Power ControlMessages per Cell.

13.5 Neighbor Cell LevelMeasurement per Cell

Describes the functions and counters of Neighbor CellLevel Measurement per Cell.

13.6 TCHF Receive Level

Measurement per TRX

Describes the functions and counters of TCHF Receive

level Measurement per TRX.

13.7 TCHH Receive Level

Measurement per TRX

Describes the functions and counters of TCHH Receive

level Measurement per TRX.

13.8 Receive QualityMeasurement per TRX

Describes the functions and counters of Receive QualityMeasurement per TRX.

13.9 Uplink-and-Downlink

Balance Measurement perTRX

Describes the functions and counters of Uplink-and-

Downlink Balance Measurement per TRX.

13.10 Number of MRs Basedon TA per TRX

Describes the functions and counters of TA TrafficDistribution Measurement per TRX.

13.11 Radio Link FailureMeasurement per TRX

Describes the functions and counters of Radio LinkFailure Measurement per TRX.



13 MR Measurement




Section Describes

13.12 Radio Link Failure

Measurement based on TA perTRX

Describes the functions and counters of Radio Link

Failure Measurement by TA Traffic Distribution perTRX.

13.13 RQI Measurement based

on TA per TRX

Describes the functions and counters of RQI

Measurement by TA Traffic Distribution per TRX.






13.1 Overview of MR Measurement

After seizing a specific channel, the MS periodically reports measurement reports (MRs) tothe BSC. The BSC performs power control and handover decision based on the MRs.

MR Measurement refers to the measurement of counters related to MRs and helps withnetwork optimization.

Table 13-1 lists the measurement units of MR Measurement.

Table 13-1 Measurement units of MR Measurement

Number Measurement Unit

1 Number of MRs per Cell

2 Interference Band Measurement per TRX

3 Power Control Messages per Cell

4 Neighbor Cell Level Measurement per Cell

5 TCHF Receive Level Measurement per TRX

6 TCHH Receive Level Measurement per TRX

7 Receive Quality Measurement per TRX

8 Uplink-and-Downlink Balance Measurement per TRX

9 Number of MRs Based on TA per TRX

10 Radio Link Failure Measurement per TRX

11 Radio Link Failure Measurement based on TA per TRX

12 RQI Measurement based on TA per TRX

13.2 Number of MRs per Cell

13.2.1 Overview of Number of MRs per Cell

Number of MRs per Cell refers to the measurement of the number of MRs received by

channels in a cell.

Table 13-2 lists the counters of Number of MRs per Cell.

Table 13-2 Counters of Number of MRs per Cell

Counter Section

Sampled MRs per Cell 13.2.2



13 MR Measurement




Counter Section

Analyzed MRs per Cell 13.2.3

13.2.2 Sampled MRs per Cell

Counter

Table 13-3 lists the counters of Sampled MRs per Cell.

Table 13-3 Counters of Sampled MRs per Cell

Number Counter

1 S3010A: MRs on Signaling Channels (SDCCH) (M900/850 Cell)

2 S3010B: MRs on Signaling Channels (SDCCH) (M1800/1900 Cell)

3 S3017A: MRs on Signaling Channels (TCHF) (M900/850 Cell)

4 S3017B: MRs on Signaling Channels (TCHF) (M1800/1900 Cell)

5 S3018A: MRs on Signaling Channels (TCHH) (M900/850 Cell)

6 S3018B: MRs on Signaling Channels (TCHH) (M1800/1900 Cell)

7 S3007A: MRs on TCHs (TCHF) (M900/850 Cell)

8 S3007B: MRs on TCHs (TCHF) (M1800/1900 Cell)

9 S3008A: MRs on TCHs (TCHH) (M900/850 Cell)

10 S3008B: MRs on TCHs (TCHH) (M1800/1900 Cell)

11 S3012: MRs on Signaling Channels (Underlaid Subcell)

12 S3011: MRs on Signaling Channels (Overlaid Subcell)

13 S3002: MRs on TCHs (Underlaid Subcell)

14 S3001: MRs on TCHs (Overlaid Subcell)

Meaning

After receiving a valid MR, or a preprocessing MR, the BSC measures the number of received

MRs based on the following factors:

Frequency band the cell is in (M900/850, M1800/1900)

Channel type (SDCCH, TCHF, and TCHH)

Cell type (normal, concentric)

Concentric cell attribute (overlaid subcell, underlaid subcell)






Valid MRs refer to complete MRs that contain both valid uplink and downlink MRs.

Trigger Point

The BSC measures the number of received MRs based on the frequency band, channel type,

cell type, and concentric cell attributes, after it receives valid MRs from the MS.

Formula

None.

13.2.3 Analyzed MRs per Cell

Counter

Table 13-4 lists the counters of Analyzed MRs per Cell.

Table 13-4 Counters of Analyzed MRs per Cell

Number Counter

1 CR3557: Traffic Volume of TCHs (Underlaid Subcell)

2 CR3558: Traffic Volume of TCHs (Overlaid Subcell)

3 TS3010: Traffic Volume of Signaling Channels (SDCCH)

4 TS3019: Traffic Volume of Signaling Channels (TCH)

5 CR355A: Traffic Volume of TCHs

6 CS300: MRs on TCHs

7 CS3007: MRs on TCHs (TCHF)

8 CS3008: MRs on TCHs (TCHH)

9 CS301: MRs on Signaling Channels

10 CS3010: MRs on Signaling Channels (SDCCH)

11 CS3017: MRs on Signaling Channels (TCHF)

12 CS3018: MRs on Signaling Channels (TCHH)

13 CS3023: Traffic Volume of Speech Service on SDCCH

14 CS3024: Traffic Volume of Short Message Service on SDCCH

15 CS3025: Traffic Volume of USSD Service on SDCCH

Meaning

None.



13 MR Measurement




The unit of the traffic volume in Table 13-4 is Erlang.

Trigger Point

None.

Formula

Traffic Volume of TCHs (Underlaid Subcell) = Mean Number of Busy TCHs (Underlaid

Subcell)

Traffic Volume of TCHs (Overlaid Subcell) = Mean Number of Busy TCHs (Overlaid Subcell)

Traffic Volume of Signaling Channels (SDCCH) = ([MRs on Signaling Channels (SDCCH)(M900/850 Cell)] + [MRs on Signaling Channels (SDCCH) (M1800/1900

Cell)])*{47}/({100}*{GP}*{60})

Traffic Volume of Signaling Channels (TCH) = ([MRs on Signaling Channels (TCHF)(M900/850 Cell)] + [MRs on Signaling Channels (TCHF) (M1800/1900 Cell)] + [MRs on

Signaling Channels (TCHH) (M900/850 Cell)] + [MRs on Signaling Channels (TCHH)(M1800/1900 Cell)])*{48}/({100}*{GP}*{60})

Traffic Volume of TCHs = [Mean Number of Busy TCHs (TCHF) (900/850 Cell)] + [Mean

Number of Busy TCHs (TCHF) (1800/1900 Cell)] + [Mean Number of Busy TCHs (TCHH)(900/850 Cell)] + [Mean Number of Busy TCHs (TCHH) (1800/1900 Cell)]

MRs on TCHs = [MRs on TCHs (TCHF) (M900/850 Cell)] + [MRs on TCHs (TCHH)

(M900/850 Cell)]

MRs on TCHs (TCHF) = [MRs on TCHs (TCHF) (M900/850 Cell)] + [MRs on TCHs (TCHF)(M1800/1900 Cell)]

MRs on TCHs (TCHH) (M900/850 Cell) = [MRs on TCHs (TCHH) (M900/850 Cell)] +[MRs on TCHs (TCHH) (M1800/1900 Cell)]

MRs on Signaling Channels = [MRs on Signaling Channels (SDCCH)] + [MRs on Signaling

Channels (TCHF)] + [MRs on Signaling Channels (TCHH)]

MRs on Signaling Channels (SDCCH) = [MRs on Signaling Channels (SDCCH) (M900/850Cell)] + [MRs on Signaling Channels (SDCCH) (M1800/1900 Cell)]

MRs on Signaling Channels (TCHF)= [MRs on Signaling Channels (TCHF) (M900/850 Cell)]

+ [MRs on Signaling Channels (TCHF) (M1800/1900 Cell)]

MRs on Signaling Channels (TCHH) = [MRs on Signaling Channels (TCHH) (M900/850Cell)] + [MRs on Signaling Channels (TCHH) (M1800/1900 Cell)]

13.3 Interference Band Measurement per TRX

13.3.1 Overview of Interference Band Measurement per TRX

Interference band is the interference level contained in the RF RES IND message that the BTS

reports to the BSC when the channel is idle. There are five levels. The level range of each band is set through the Local Maintenance Terminal (LMT).






Table 13-5 lists the typical settings of the power level range.

Table 13-5 Power level range of the interference band

Interference Band Power Level Range

Interference band 1 –105 dBm to –98 dBm





The higher rank suggests higher interference level. An idle channel at interference band 4 or 5

suggests the existence of interference.

Interference Band Measurement per TRX refers to the measurement of idle channels that arein the interference bands.

Table 13-6 lists the counters of Interference Band Measurement per TRX.

Table 13-6 Counters of Interference Band Measurement per TRX

Counter Section

Sampled Measurement of Interference Band per TRX 13.3.2

Analyzed Measurement of Interference Band per TRX 13.3.3

13.3.2 Sampled Measurement of Interference Band per TRX

Counter

Table 13-7 lists the counters of Sampled Measurement of Interference Band.

Table 13-7 Counters of Sampled Measurement of Interference Band

Number Counter

1 S4210A: Uplink Interference Indication Messages (SDCCH)

2 S4210B: Downlink Interference Indication Messages (SDCCH)

3 S4219A: Uplink Interference Indication Messages (TCH)

4 S4219B: Downlink Interference Indication Messages (TCH)



13 MR Measurement




Meaning

In HUAWEI Channel Allocation Algorithm II, the BTS compares the level and quality in the

MR with the thresholds set in data configuration. If both the level and the quality exceed the

preset thresholds, the counters are measured based on the channel type (TCH or SDCCH) and

interference direction (uplink or downlink).

Trigger Point

The counters are measured based on the channel type (TCH or SDCCH) and interference

direction (uplink or downlink) if the level and the quality exceed the preset thresholds.

Formula

None.

13.3.3 Analyzed Measurement of Interference Band per TRXCounter

Table 13-8 lists the counters of Analyzed Measurement of Interference Band per TRX.

Table 13-8 Counters of Analyzed Measurement of Interference Band per TRX

Number Counter

1 AS4200A: Mean Number of SDCCHs in Interference Band 1

2 AS4200B: Mean Number of SDCCHs in Interference Band 2

3 AS4200C: Mean Number of SDCCHs in Interference Band 3

4 AS4200D: Mean Number of SDCCHs in Interference Band 4

5 AS4200E: Mean Number of SDCCHs in Interference Band 5

6 AS4207A: Mean Number of TCHFs in Interference Band 1

7 AS4207B: Mean Number of TCHFs in Interference Band 2

8 AS4207C: Mean Number of TCHFs in Interference Band 3

9 AS4207D: Mean Number of TCHFs in Interference Band 4

10 AS4207E: Mean Number of TCHFs in Interference Band 5

11 AS4208A: Mean Number of TCHHs in Interference Band 1

12 AS4208B: Mean Number of TCHHs in Interference Band 2

13 AS4208C: Mean Number of TCHHs in Interference Band 3

14 AS4208D: Mean Number of TCHHs in Interference Band 4

15 AS4208E: Mean Number of TCHHs in Interference Band 5






Meaning

The BSC receives from the BTS the RF RES IND message that contains the interference band

levels of all the idle channels in a TRX. Then the BSC measures the counters according to the

channel type (TCHF, TCHH, or SDCCH) and the interference band level.

Mean Number of SDCCHs in Interference Band = Number of SDCCHs in Interference Band/[Sampled Number of Interference Bands]

Trigger Point

None.

Formula

Mean Number of SDCCHs in Interference Band 1 = [Number of SDCCHs in Interference

Band 1]/[ Sampled Number of Interference Bands]

Mean Number of SDCCHs in Interference Band 2 = [Number of SDCCHs in InterferenceBand 2]/[ Sampled Number of Interference Bands]

Mean Number of SDCCHs in Interference Band 3 = [Number of SDCCHs in Interference

Band 3]/[ Sampled Number of Interference Bands]



Mean Number of TCHFs in Interference Band 1 = [Number of TCHFs in Interference Band

1]/[ Sampled Number of Interference Bands]

Mean Number of TCHFs in Interference Band 2 = [Number of TCHFs in Interference Band2]/[ Sampled Number of Interference Bands]







Mean Number of TCHHs in Interference Band 1 = [Number of TCHHs in Interference Band


Mean Number of TCHHs in Interference Band 2 = [Number of TCHHs in Interference Band2]/[ Sampled Number of Interference Bands]

Mean Number of TCHHs in Interference Band 3 = [Number of TCHHs in Interference Band





13 MR Measurement





13.4 Power Control Messages per Cell

13.4.1 Overview of Power Control Messages per Cell

Power control refers to changing the transmission power of the MS or the BTS. The purpose

of power control is to reduce the interference, raise the spectrum usage, and prolong the

lifespan of the MS battery.

The factors that influence power control are the receive level and quality of received signalsin the MRs. If the quality of both the receive level and the received signals are good, you can

reduce the interference by lowering the transmission power at the peer end.

Power Control Messages per Cell refers to the measurement of the transmission power andthe receive level between the BTS and the MS.

Table 13-9 lists the counters of Power Control Messages per Cell.

Table 13-9 Counters of Power Control Messages per Cell

Counter Section

Number of Power Control Messages per Cell 13.4.2

Sampled Power Rank During Power Control per Cell 13.4.3

Analyzed Power Rank During Power Control per Cell 13.4.4

Sampled Level of Power Control Signals per Cell 13.4.5

Analyzed Level of Power Control Signals per Cell 13.4.6

Sampling Quality of Power Control Signals per Cell 13.4.7

Analyzed Quality of Power Control Signals per Cell 13.4.8

Sampled Duration of Maximum Power per Cell 13.4.9

Analyzed Duration of Maximum Power per Cell 13.4.10

Distance Between MS and BTS per Cell 13.4.11

Maximum Distance Between MS and BTS per Cell 13.4.12

Number of Power Control Messages per Cell 13.4.13

Mean Distance Between MS and BTS per Cell 13.4.14






13.4.2 Number of Power Control Messages per Cell

Counter

Table 13-10 lists the counters of Number of Power Control Messages per Cell.

Table 13-10 Counters of Number of Power Control Messages per Cell

Number Counter

1 S3230A: Number of Power Control Increase Messages Sent to MS

2 S3230B: Number of Power Control Decrease Messages Sent to MS

3 S3231A: Number of Power Control Increase Messages Sent to BTS

4 S3231B: Number of Power Control Decrease Messages Sent to BTS

Meaning

After receiving the MR, the BSC compares the uplink receive level and the uplink receive

quality with the preset thresholds and makes the following decisions:

If the transmission power of the MS need be increased, the BSC sends the powerincrease request to the MS, and the S3230A: Number of Power Control IncreaseMessages Sent to MS is measured.

If the transmission power of the MS need be decreased, the BSC sends the power

decrease request to the MS, and the S3230B: Number of Power Control DecreaseMessages Sent to MS is measured.

If the transmission power of the BTS need be increased, the BSC sends the powerincrease request to the BTS, and the S3231A: Number of Power Control IncreaseMessages Sent to BTS is measured.

If the transmission power of the BTS need be decreased, the BSC sends the power

decrease request to the BTS, and the S3231B: Number of Power Control DecreaseMessages Sent to BTS is measured.

Trigger Point

The BSC measures the counters based on the power control objectives (MS or BTS) and type(to increase or decrease the transmit power) after receiving the valid MRs from the MS.

Formula

None.



13 MR Measurement




13.4.3 Sampled Power Rank During Power Control per Cell

Counter

Table 13-11 lists the counters of Sampled Power Rank During Power Control per Cell.

Table 13-11 Counters of Sampled Power Rank During Power Control per Cell

Number Counter

1 S3240: MS Power Rank

2 S3241: BTS Power Rank

3 S327A: Number of Times (Maximum Uplink Transmit Power)

4 S327B: Number of Times (Maximum Downlink Transmit Power)

Meaning

In S3240: MS Power Rank, higher rank of the transmit power indicates smaller transmit

power of the MS.

In S3241: BTS Power Rank, higher rank of the transmit power indicates smaller transmit power of the BTS.

The counter S327A: Number of Times (Maximum Uplink Transmit Power) increases by 1

when the rank of the uplink transmit power in the MR is lower than or equal to the rank of the

Maximum MS Transmit Power in the system message.

The counter S327B: Number of Times (Maximum Downlink Transmit Power) increases by 1when the rank of the downlink transmit power is 0.

Trigger Point

The BSC measures the MS Power Rank and the BTS Power Rank based on the transmit

power ranks of the MS and the BTS after receiving the valid MRs from the MS.

Formula

None.

13.4.4 Analyzed Power Rank During Power Control per Cell

Counter

Table 13-12 lists the counters of Analyzed Power Rank During Power Control per Cell.

Table 13-12 Counters of Analyzed Power Rank During Power Control per Cell

Number Counter

1 AS3240: Mean Power Rank of MS






Number Counter

2 AS3241: Mean Power Rank of BTS

Meaning

The counters measure the mean transmit power of the MS and the BTS.

Trigger Point

None.

Formula

Mean Power Rank of MS = [MS Power Rank]/[Number of Power Control Messages]

Mean Power Rank of BTS = [BTS Power Rank]/[ Number of Power Control Messages]

13.4.5 Sampled Level of Power Control Signals per Cell

Counter

Table 13-13 lists the counters of Sampled Level of Power Control Signals per Cell.

Table 13-13 Counters of Sampled Level of Power Control Signals per Cell

Number Counter

1 S325B: Strength of Downlink Signals

2 S325A: Strength of Uplink Signals

Meaning

The counters measure the uplink and downlink receive level.

Trigger PointThe BSC measures the counters based on the uplink and downlink receive level after

receiving the valid MRs from the MS.

Formula

None.



13 MR Measurement




13.4.6 Analyzed Level of Power Control Signals per Cell

Counter

Table 13-14 lists the counters of Analyzed Level of Power Control Signals per Cell.

Table 13-14 Counters of Analyzed Level of Power Control Signals per Cell

Number Counter

1 AS325B: Mean Strength of Downlink Signals

2 AS325A: Mean Strength of Uplink Signals

MeaningThe counters measure the mean uplink and downlink receive level.

Trigger Point

None.

Formula

Mean Strength of Downlink Signals = [Strength of Downlink Signals]/[ Number of Power

Control Messages]

Mean Strength of Uplink Signals = [Strength of Uplink Signals]/[ Number of Power ControlMessages]

13.4.7 Sampling Quality of Power Control Signals per Cell

Counter

Table 13-15 lists the counters of Quality of Power Control Signals per Cell.

Table 13-15 Counters of Quality of Power Control Signals per Cell

Number Counter

1 S326B: Quality of Downlink Signals

2 S326A: Quality of Uplink Signals

Meaning

The counters measure the quality of the uplink and downlink received signals. The receive

quality has eight ranks, and lower rank suggests better quality.






Trigger Point

The BSC measures the counters based on the quality ranks of the uplink and downlink

received signals after receiving valid MRs from the MS.

Formula

None.

13.4.8 Analyzed Quality of Power Control Signals per Cell

Counter

Table 13-16 lists the counters of Analyzed Quality of Power Control Signals per Cell.

Table 13-16 Counters of Analyzed Quality of Power Control Signals per Cell

Number Counter

1 AS326B: Mean Quality of Downlink Signals

2 AS326A: Mean Quality of Uplink Signals

Meaning

The counters measure the mean receive quality of the uplink and downlink signals. The

receive quality has eight ranks, and lower rank suggests better quality.

Trigger Point

None.

Formula

Mean Quality of Downlink Signals = [Quality of Downlink Signals]/[Number of Power

Control Messages]

Mean Quality of Uplink Signals = [Quality of Uplink Signals]/[Number of Power Control

Messages]

13.4.9 Sampled Duration of Maximum Power per Cell

Counter

Table 13-17 lists the counters of Sampled Duration of Maximum Power per Cell.

Table 13-17 Counters of Sampled Duration of Maximum Power per Cell

Number Counter

1 TS327B: Duration of Maximum Downlink Power



13 MR Measurement




Number Counter

2 TS327A: Duration of Maximum Uplink Power

Meaning

This counter measures the duration of the maximum uplink and downlink power.

Trigger Point

If the downlink transmit power rank is 0, the counter TS427B: Duration of Maximum

Downlink Power increases by 0.48 s.

If the uplink transmit power rank is lower than or equal to the Maximum Transmit Power

Control Level in the system information, the counter TS427A: Duration of Maximum Uplink

Power increases by 0.48 s.

Formula

None.

13.4.10 Analyzed Duration of Maximum Power per Cell

Counter

Table 13-18 lists the counters of Analyzed Duration of Maximum Power per Cell.

Table 13-18 Counters of Analyzed Duration of Maximum Power per Cell

Number Counter

1 RS327B: Ratio of Maximum Downlink Power Duration (%)

2 RS327A: Ratio of Maximum Uplink Power Duration (%)

Meaning

RS327B: Ratio of Maximum Downlink Power Duration (%) measures the ratio of theDuration of Maximum Downlink Power to the Number of Power Control Messages. Greatvalue of this counter suggests bad coverage or improper settings of power control parameters.

RS327A: Ratio of Maximum Uplink Power Duration (%) measures the ratio of the Duration

of Maximum Uplink Power to the Number of Power Control Messages. Great value of thiscounter suggests low rank of the uplink receive level or improper settings of power control

parameters.

Trigger Point

None.






Formula

Ratio of Maximum Downlink Power Duration (%) = {100}*[ Duration of Maximum

Downlink Power]/([Number of Power Control Messages]*{48}/{100})

Ratio of Maximum Uplink Power Duration (%)= {100}*[ Duration of Maximum UplinkPower]/([Number of Power Control Messages]*{48}/{100})

13.4.11 Distance Between MS and BTS per Cell

Counter

S3280: Distance Between MS and BTS

Meaning

The distance between the MS and the BTS is measured in TA (one TA equals to 550 m.) The

value of TA increases with the distance.

This counter measures the distance between the MS and the BTS.

Trigger Point

The counter increases by 1 when the BSC receives a valid MR that contains the TA.

Formula

None.

13.4.12 Maximum Distance Between MS and BTS per Cell

Counter

S3281: Maximum Distance Between MS and BTS

Meaning

The distance between the MS and the BTS is measured in TA (one TA equals to 550 m.) The

value of TA increases with the distance.

This counter measures the maximum distance between the MS and the BTS.

Trigger Point

This counter is measured when the BSC records the maximum distance (in TA) in a valid MR

that the MS reports in a GP.

Formula

None.



13 MR Measurement




13.4.13 Number of Power Control Messages per Cell

Counter

S329: Number of Power Control Messages

Meaning

This counter measures the total number of cell power control messages.

Trigger Point

This counter is measured when the BSC receives a valid MR that contains a power control

message.

Formula None.

13.4.14 Mean Distance Between MS and BTS

Counter

AS3280: Mean Distance Between MS and BTS.

Meaning

This counter measures the mean distance between the MS and the BTS.

Trigger Point

None.

Formula

Mean Distance Between MS and BTS = [Distance Between MS and BTS]/[Number of Power

Control Messages]

13.5 Neighbor Cell Level Measurement per Cell

13.5.1 Overview of Neighbor Cell Level Measurement per Cell

Neighbor Cell Level Measurement per Cell refers to the measurement of mean receive levelof neighbor cells. This measurement unit helps to determine whether to configure neighborcells.

Table 13-19 lists the counters of Neighbor Cell Level Measurement per Cell.






Table 13-19 Counters of Neighbor Cell Level Measurement per Cell

Number Counter

1 S360: Strength of Signals in Neighbor Cells

2 S361: Number of MRs of Neighbor Cells

3 AS360: Mean Strength of Signals in Neighbor Cells

13.5.2 Strength of Signals in Neighbor Cells

Counter

S360: Strength of Signals in Neighbor Cells.

Meaning

This counter measures the strength of signals in neighbor cells.

Trigger Point

This counter is measured when the BSC receives a valid MR and accumulates the receive

level of all the neighbor cells.

This counter's measurement object can be configured. If the measurement object is not configured, this

counter is not measured.

Formula

None.

13.5.3 Number of MRs of Neighbor Cells

Counter

S361: Number of MRs of Neighbor Cells.

Meaning

This counter measures the number of MRs in neighbor cells.

Trigger Point

This counter is measured based on the neighboring cells when the BSC receives a valid MR

from the MS.

This counter's measurement object can be configured. If the measurement object is not configured, this

counter is not measured.



13 MR Measurement




Formula

None.

13.5.4 Mean Strength of Signals in Neighbor CellsCounter

AS360: Mean Strength of Signals in Neighbor Cells.

Meaning

This counter measures the mean strength of signals in neighbor cells in a GP.

Trigger Point

None.

Formula

Mean Strength of Signals in Neighbor Cells= [Strength of Signals in Neighbor Cells]/[ MRs

of Neighbor Cells]

13.6 TCHF Receive Level Measurement per TRX

CounterThe valid MRs that the BSC receives contain the ranks of the uplink and downlink receive

level and the ranks of the uplink and downlink receive quality.

The receive level has eight ranks, and higher rank suggests greater receive level, as shown inTable 13-20.

Table 13-20 Rank of the receive level

Rank of Receive Level Receive Level(dBm)

0 <–100

1 (-100,85]

2 (-85,-80]

3 (-80,-75]

4 (-75,-70]

5 (-70,-65]

6 (-65,-60]

7 >-60






The receive quality has eight ranks, and higher rank suggests worse receive quality, as shownin Table 13-21.

Table 13-21 Rank of the receive quality based on the bit error rate

Rank of Receive Quality Bit Error Rate

0 < 0.2%

1 0.2%–0.4%

2 0.4%–0.8%

3 0.8%–1.6%

4 1.6%–3.2%

5 3.2%–6.4%

6 6.4%–12.8%

7 > 12.8%

TCHF Receive Level Measurement per TRX refers to the measurement of the sampled

receive level ranks and receive quality ranks in the MRs on the TCHF.

Table 13-22 lists the counters of TCHF Receive Level Measurement per TRX.

Table 13-22 Counters of TCHF Receive Level Measurement per TRX

Number Counter

1 S4100A: Number of MRs on Uplink TCHF (Receive Level Rank 0 andReceive Quality Rank 0)







8 S4107A: Number of MRs on Uplink TCHF (Receive Level Rank 0 and

Receive Quality Rank 7)





13 MR Measurement




Number Counter
























