Professional Documents
Culture Documents
INTRODUCTION TO STATISTICS STATISTICAL OPERATIONS BSS STATISTICS CELL STATISTICS NEIGHBOUR STATISTICS
CHAPTER 6 CHAPTER 7 CHAPTER 8 CHAPTER 9 CHAPTER 10
CARRIER AND TIMESLOT GPROC AND DPROC LMTL STATISTICS BSS STATS FOR LOCATION MTL STATISTICS
STATISTICS STATISTICS SERVICES SUPPORT
CHAPTER 11 CHAPTER 12 CHAPTER 13 CHAPTER 14 CHAPTER 15
CBL, GSL, OML, RSL AND PCU STATISTICS BSS–SMLC STATISTICS WEB MMI STATISTICS HR AND AMR STATISTICS
XBL STATISTICS
CHAPTER 16 CHAPTER 17 CHAPTER 18 CHAPTER 19 CHAPTER 20
CALL MODEL STATISTICS KEY STATISTICS NETWORK HEALTH LADDER DIAGRAMS IMPACTS ON STATISTICS
REPORTS
INDEX
MAINTENANCE INFORMATION
GSM STATISTICS APPLICATION
GSM SOFTWARE RELEASE 7 HALF RATE
GSR7
Half Rate
CONTROLLED INTRODUCTION
68P02901W56-Q
Half Rate
INTRODUCTION
CONTROLLED
68P02901W56-Q
MAINTENANCE INFORMATION
GSR7
GSM STATISTICS APPLICATION
GSM SOFTWARE RELEASE 7 HALF RATE
Maintenance Information: GSM
Statistics Application
Contents
68P02901W56-Q i
24 May 2004 CONTROLLED INTRODUCTION
Contents
ROUTING_UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
RSL_LCF_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
SCCP_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
SCCP_MSGS_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
SCCP_MSGS_TX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
SIF_SIO_RX_OPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
SIF_SIO_TX_DPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
SIF_SIO_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
ii 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Contents
INTERBAND_ACTIVITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61
INTRA_CELL_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62
INV_EST_CAUSE_ON_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
MA_CMD_TO_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-65
MA_COMPLETE_FROM_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66
MA_COMPLETE_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-67
MA_FAIL_FROM_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69
MA_REQ_FROM_MSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70
MA_CMD_TO_MS_BLKD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
MS_ACCESS_BY_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73
MS_TCH_USAGE_BY_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
MS_TCH_USAGE_BY_TYPE_PCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-75
MT_LCS_ON_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-77
NUM_EMERG_ACCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
NUM_EMERG_REJECTED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-79
NUM_EMERG_TCH_KILL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80
NUM_EMERG_TERM_SDCCH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81
OK_ACC_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
OK_ACC_PROC_SUC_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
OUT_HO_CAUSE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-85
OUT_INTER_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87
OUT_INTRA_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89
PAGE_REQ_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-91
PAGING_REQUESTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92
PCH_AGCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-93
PCH_Q_PAGE_DISCARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94
PPCH_Q_PAGE_DISCARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-95
RF_LOSSES_SD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96
RF_LOSSES_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-97
SDCCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-99
SECOND_ASSIGN_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-100
SECOND_ASSIGN_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-101
SMS_INIT_ON_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-102
SMS_INIT_ON_SDCCH_HO_IN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-103
SMS_INIT_ON_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104
SMS_NO_BCAST_MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-105
TCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-106
TCH_CONG_INNER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-107
TCH_DELAY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-108
TCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-109
TCH_Q_REMOVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-110
TCH_USAGE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-111
TCH_USAGE_EXT_RANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-113
TCH_USAGE_INNER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114
TOTAL_CALLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-115
ZONE_CHANGE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-116
ZONE_CHANGE_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-117
68P02901W56-Q iii
24 May 2004 CONTROLLED INTRODUCTION
Contents
iv 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Contents
LMTP_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35
LMTP_SIB_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36
68P02901W56-Q v
24 May 2004 CONTROLLED INTRODUCTION
Contents
MTP_START_RPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-32
MTP_STOP_RPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33
MTP_SU_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
MTP_UNAVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35
SIB_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-36
SIB_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-37
SL_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-38
SL_STOP_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-39
vi 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Contents
DL_TBF_TIME_4_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-54
EGPRS_64K_CHANNELS_SWITCHED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-55
EGPRS_64K_NOT_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-56
EGPRS_AVAIL_PDTCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-57
EGPRS_DL_ASGN_PCCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-58
G_RACH_UNSVCD_BTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-59
GBL_DL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-60
GBL_DL_DATA_THRPUT_HIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-61
GBL_FLOW_CTRL_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-63
GBL_LINK_INS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-64
GBL_PAGING_REQS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-65
GBL_UL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-66
GBL_UL_DATA_THRPUT_HIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-67
GBL_UNAVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-69
GPRS_32K_CHANNELS_SWITCHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-70
GPRS_32K_DL_NOT_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-71
GPRS_32K_UL_NOT_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-72
GPRS_ACCESS_PER_AGCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-73
GPRS_ACCESS_PER_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-74
GPRS_AVAIL_PDTCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-75
GPRS_CELL_RESELECT_ATTMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-77
GPRS_CELL_RESELECT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-78
GPRS_CHANNELS_SWITCHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-79
GPRS_DL_ASGN_PCCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-80
GPRS_DYNET_FAILURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-81
GPRS_DYNET_RES_REQS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-83
GPRS_DYNET_SWI_REQS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-84
GPRS_MS_NEIGHBOR_STRONG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-85
GPRS_PCH_AGCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-86
GPRS_PPCH_PAGCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-87
GPRS_PRR_BLK_USG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-88
GPRS_RACH_ARRIVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-90
IDLE_PDTCH_INTF_BAND0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-92
IDLE_PDTCH_INTF_BAND1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-93
IDLE_PDTCH_INTF_BAND2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-94
IDLE_PDTCH_INTF_BAND3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-95
IDLE_PDTCH_INTF_BAND4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-96
IMM_ASSGN_CAUSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-97
MS_CLASS_1_10_REQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-99
MS_CLASS_11_20_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-101
MS_CLASS_21_29_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-103
NO_PDTCH_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-105
NO_PDTCH_AVAIL_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-106
PRP_LOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-107
UL_BUSY_PDTCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-109
UL_PDTCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-111
UL_PDTCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-112
UL_PDTCH_SEIZURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-113
UL_RADIO_BLKS_8PSK_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-114
UL_RADIO_BLKS_8PSK_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-116
UL_RADIO_BLKS_GMSK_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-118
UL_RADIO_BLKS_GMSK_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-120
UL_RLC_ACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-122
UL_RLC_RETX_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-124
UL_RLC_UNACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-126
68P02901W56-Q vii
24 May 2004 CONTROLLED INTRODUCTION
Contents
UL_TBF_TIME_8PSK_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-128
UL_TBF_TIME_8PSK_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-129
UL_TBF_TIME_GMSK_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-130
UL_TBF_TIME_GMSK_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-131
viii 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Contents
68P02901W56-Q ix
24 May 2004 CONTROLLED INTRODUCTION
Contents
CALL_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-20
CELL_UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-21
CS1_USAGE_DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-22
CS1_USAGE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-23
CS2_USAGE_DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-24
CS2_USAGE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-25
CS3_USAGE_DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-26
CS3_USAGE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-27
CS4_USAGE_DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-28
CS4_USAGE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-29
DL_AIR_INTERFACE_BW_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-30
DL_AIR_INTERFACE_BW_CS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-31
DL_AIR_INTERFACE_BW_CS3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-32
DL_AIR_INTERFACE_BW_CS4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-33
DOWNLINK_TRAFFIC_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-34
DROP_CALL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-36
GBL_AVAILABILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-38
GPRS_BW_USAGE_DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-39
GPRS_BW_USAGE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-40
GPRS_DL_ACT_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-41
GPRS_UL_ACT_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-42
HO_CAUSE_ADJ_CH_INTERF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-43
HO_CAUSE_BAND_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-44
HO_CAUSE_BAND_REASSGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-45
HO_CAUSE_CONGEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-46
HO_CAUSE_DISTANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-47
HO_CAUSE_DLINTERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-48
HO_CAUSE_DLLEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-49
HO_CAUSE_DLQUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-50
HO_CAUSE_PWRBGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-51
HO_CAUSE_UPINTERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-52
HO_CAUSE_UPLEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-53
HO_CAUSE_UPQUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-54
HO_PER_CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-55
IN_INTER_BSS_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-56
IN_INTER_CELL_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-57
IN_INTRA_BSS_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-58
INCOMING_HO_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-59
INTERNAL_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-60
INTERNAL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-61
INTERNAL_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-62
INTRA_CELL_HO_FAIL_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-63
INTRA_CELL_HO_FAIL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-64
INTRA_CELL_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-65
MAX_TCH_BUSY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-66
MSC_PAGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-67
MEAN_TIME_BETWEEN_DROPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-68
MEAN_TIME_BETWEEN_HOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-69
OUT_INTER_BSS_HO_FAIL_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-70
OUT_INTER_BSS_HO_FAIL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-71
OUT_INTER_BSS_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-72
OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-73
OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED_MS. . . . . . . . . . . . . . . . . . . . . . . 18-74
OUT_INTER_CELL_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-75
OUT_INTER_CELL_HO_SUCCESS_RATE_RECOVERED_MS . . . . . . . . . . . . . . . . . . . . 18-76
x 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Contents
OUT_INTRA_BSS_HO_FAIL_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-77
OUT_INTRA_BSS_HO_FAIL_RECOVERED_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-78
OUT_INTRA_BSS_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-79
OUTGOING_HO_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-80
PAGING_COMPRESSION_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-81
PAGING_OVERFLOW_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-82
PAGING_RESPONSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-83
PAGING_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-84
PERCENTAGE_INTER_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-85
PERCENTAGE_INTRA_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-86
PERCENTAGE_INTRA_CELL_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-87
PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK. . . . . . . . . . . . . . . . . . . . . . . . . 18-88
RANKING_FORMULA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-89
RF_ASSIGN_FAIL_RATE_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-90
RF_ASSIGN_FAIL_RATE_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-91
RF_ASSIGNMENT_SUCCESS_RATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-92
SDCCH_ACCESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-93
SDCCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-94
SDCCH_CONGESTION_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-95
SDCCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-96
SDCCH_USAGE_ACCESS_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-98
SDCCH_USAGE_CALL_REESTABLISH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-99
SDCCH_USAGE_EMERGENCY_CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-100
SDCCH_USAGE_IMSI_DETACH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-101
SDCCH_USAGE_LOCATION_UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-102
SDCCH_USAGE_MS_ORIGINATED_CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-103
SDCCH_USAGE_MS_ORIGINATED_SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-104
SDCCH_USAGE_SMS_ORIGINATED_SS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-105
SDCCH_USAGE_PAGING_RESPONSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-106
SDCCH_USAGE_SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-107
SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGESTION_RELIEF . . . . . . . . . . . . . . . . . . 18-108
SPILL_OVER_FACTOR_DIRECTED_RETRY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-109
SPILL_OVER_FACTOR_MULTIBAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-110
TCH_ACCESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-111
TCH_CONGESTION_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-113
TCH_CONGESTION_TIME_INNER_ZONE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-114
TCH_CONGESTION_TIME_OUTER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-115
TCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-116
TCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-118
UL_AIR_INTERFACE_BW_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-120
UL_AIR_INTERFACE_BW_CS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-121
UL_AIR_INTERFACE_BW_CS3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-122
UL_AIR_INTERFACE_BW_CS4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-123
UPLINK_PDTCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-124
UPLINK_TRAFFIC_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-125
68P02901W56-Q xi
24 May 2004 CONTROLLED INTRODUCTION
Contents
xii 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
List
of
Figures
List of Figures
68P02901W56-Q xiii
24 May 2004 CONTROLLED INTRODUCTION
List of Figures
Figure 19-40: Inter-BSS handover unsuccessful with fail-recovered source cell . . . . . . . . . . . . . . 19-48
Figure 19-41: Inter-BSS handover unsuccessful due to invalid frequency supported . . . . . . . . . . . . 19-49
Figure 19-42: Invalid frequency at assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-50
Figure 19-43: Intra-BSS handover successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-51
Figure 19-44: Unsuccessful band reassign. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-52
Figure 19-45: RSL link scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-54
Figure 19-46: MTL link scenario (Part I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-56
Figure 19-47: MTL link transition scenarios (Part II) . . . . . . . . . . . . . . . . . . . . . . . . . . 19-57
Figure 19-48: MTL link transition scenarios (Part III) . . . . . . . . . . . . . . . . . . . . . . . . . . 19-58
Figure 19-49: MTL link transition scenarios (Part IV) . . . . . . . . . . . . . . . . . . . . . . . . . . 19-59
Figure 19-50: GBL_DL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-60
Figure 19-51: GBL_FLOW_CTRL_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-61
Figure 19-52: CELL_FLUSH_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-61
Figure 19-53: GBL_PAGING_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-62
Figure 19-54: GBL_UL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-63
Figure 19-55: Accessibility CHANNEL_REQ_REJ . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-64
Figure 19-56: GPRS_ACCESS_PER_RACH and GPRS_ACCESS_PER_AGCH . . . . . . . . . . . . . 19-65
Figure 19-57: Accessibility and GBL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-66
Figure 19-58: MS CLASS statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-67
Figure 19-59: GPRS_CHANNELS_SWITCHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-68
Figure 19-60: Uplink data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-70
Figure 19-61: Downlink data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-71
Figure 20-1: Approximate equality procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-5
Figure 20-2: Phantom RACHs illustration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6
xiv 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
List
of
Tables
List of Tables
68P02901W56-Q xv
24 May 2004 CONTROLLED INTRODUCTION
List of Tables
xvi 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
About
This
Manual
Detailed information on previous GSR statistical information, for example, GSR 5.1 and GSR6,
can be obtained from the appropriate GSM Statistics Application manual.
The target audience for this manual is GSM network operators and administrators.
68P02901W56-Q 1
24 May 2004 CONTROLLED INTRODUCTION
Issue status of this manual
The following shows the issue status of this manual since it was first released.
Version information
The following table lists the versions of this manual in order of issue:
Manual
Date of issue Remarks
issue
O 03 Oct 1994 Original issue - Software release 1.2.2.x
A 30 Dec 1994 Issue A - Software release 1.2.3.x
B 01 Sep 1995 Issue B - Software release 1.3.0.x
C 31 May 1996 Issue C - Software release 1.4.0.x
D 28 Mar 1997 Issue D - Software release 1.4.1.x
E 29 Aug 1997 Issue E - GSM Software Release 2
F 27 Apr 1998 Issue F - GSM Software Release 3
G 12 Mar 1999 Issue G - GSM Software Release 4
H 14 Jul 2000 Issue H - GSM Software Release 1.6.1.3
J 31 Jul 2001 Issue J - GSM Software Release 5
K 31 May 2002 Issue K - GSM Software Release 5.1
L 30 Nov 2002 Issue L - GSM Software Release 6
M 02 May 2003 Issue M - GSM Software Release 6 (Horizon II)
P 13 Nov 2003 Issue P - GSM Software Release 7
Q 24 May 2004 Issue Q- GSM Software Release 7 Half Rate
(Controlled Introduction)
2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Issue status of this manual
Service GMR
Remarks
Request Number
N/A N/A
68P02901W56-Q 3
24 May 2004 CONTROLLED INTRODUCTION
General information
General information
• Motorola disclaims all liability whatsoever, implied or express, for any risk of damage,
loss or reduction in system performance arising directly or indirectly out of the failure
of the customer, or any one acting on the customers behalf, to abide by the instructions,
system parameters or recommendations made in this manual
• If this manual was obtained when attending a Motorola training course, it will not be updated
or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was supplied
under normal operational circumstances, to support a major software release, then corrections
will be supplied automatically by Motorola in the form of General Manual Revisions (GMRs).
Purpose
Motorola cellular communications manuals are intended to instruct and assist personnel in the operation,
installation and maintenance of the Motorola cellular infrastructure equipment and ancillary devices. It is
recommended that all personnel engaged in such activities be properly trained by Motorola.
These manuals are not intended to replace the system and equipment training offered by Motorola, although
they can be used to supplement and enhance the knowledge gained through such training.
Feature references
Most of the manuals in the set, of which this manual is part, are revised to accommodate features
released at Motorola General System Releases (GSRn) or GPRS Support Node (GSNn) releases. In
these manuals, new and amended features are tagged to help users to assess the impact on installed
networks. The tags are the appropriate Motorola Roadmap DataBase (RDB) numbers or Research and
Development Prioritization (RDP) numbers. The tags include index references which are listed in the
manual Index. The Index includes the entry feature which is followed by a list of the RDB or RDP
numbers for the released features, with page references and hot links in electronic copy.
4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
General information
For a list of Roadmap numbers and the RDB or RDP numbers of the features included in this
software release, refer to the manualSystem Information: GSM Overview (68P02901W01), or to
the manual System Information: GPRS Overview (68P02903W01).
Cross references
Throughout this manual, references are made to external publications, chapter numbers and
section names. The references to external publications are shown in italics, chapter and
section name cross references are emphasised blue in text.
This manual is divided into uniquely identified and numbered chapters that, in turn, are
divided into sections. Sections are not numbered, but are individually named at the top of
each page, and are listed in the table of contents.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the GSM and
GPRS network is encrypted. In order to comply with the export and import requirements of particular
countries, this encryption occurs at different levels as individually standardised, or may not be present
at all in some parts of the network in which it is normally implemented. The manual set, of which
this manual is a part, covers encryption as if fully implemented. Because the rules differ in individual
countries, limitations on the encryption included in the particular software being delivered, are covered
in the Release Notes that accompany the individual software release.
68P02901W56-Q 5
24 May 2004 CONTROLLED INTRODUCTION
General information
Text conventions
The following conventions are used in the Motorola cellular infrastructure manuals to represent
keyboard input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this.
6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Reporting safety issues
Whenever a safety issue arises, carry out the following procedure in all instances. Ensure
that all site personnel are familiar with this procedure.
Procedure
68P02901W56-Q 7
24 May 2004 CONTROLLED INTRODUCTION
Warnings and cautions
The following describes how warnings and cautions are used in this manual and in
all manuals of this Motorola manual set.
Warnings
Definition of Warning
A warning is used to alert the reader to possible hazards that could cause loss of life, physical
injury, or ill health. This includes hazards introduced during maintenance, for example, the use of
adhesives and solvents, as well as those inherent in the equipment.
Do not look directly into fibre optic cables or data in/out connectors. Laser
radiation can come from either the data in/out connectors or unterminated
fibre optic cables connected to data in/out connectors.
Observe all warnings during all phases of operation, installation and maintenance of the equipment
described in the Motorola manuals. Failure to comply with these warnings, or with specific
warnings elsewhere in the Motorola manuals, or on the equipment itself, violates safety
standards of design, manufacture and intended use of the equipment. Motorola assumes no
liability for the customer’s failure to comply with these requirements.
Cautions
8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Warnings and cautions
Definition of Caution
A caution means that there is a possibility of damage to systems, software or individual items of
equipment within a system. However, this presents no danger to personnel.
Do not use test equipment that is beyond its due calibration date;
arrange for calibration to be carried out.
68P02901W56-Q 9
24 May 2004 CONTROLLED INTRODUCTION
General warnings
General warnings
Observe the following specific warnings during all phases of operation, installation and
maintenance of the equipment described in the Motorola manuals:
• Electric shock.
• RF radiation.
• Laser radiation.
• Heavy equipment.
• Parts substitution.
• Battery supplies.
• Lithium batteries.
Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola manuals,
violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes
no liability for the customer’s failure to comply with these requirements.
Warning labels
Warnings particularly applicable to the equipment are positioned on the equipment. Personnel working
with or operating Motorola equipment must comply with any warning labels fitted to the equipment.
Warning labels must not be removed, painted over or obscured in any way.
Specific warnings
Specific warnings used throughout the GSM manual set are shown below, and will be
incorporated into procedures as applicable.
These must be observed by all personnel at all times when working with the equipment, as must
any other warnings given in text, in the illustrations and on the equipment.
10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
General warnings
This equipment operates from a potentially hazardous voltage of 230 V a.c. single
phase or 415 V a.c. three phase supply. To achieve isolation of the equipment
from the a.c. supply, the a.c. input isolator must be set to off and locked.
When working with electrical equipment, reference must be made to the Electricity at Work Regulations 1989
(UK), or to the relevant electricity at work legislation for the country in which the equipment is used.
Electric shock
Do not touch the victim with your bare hands until the electric circuit is broken.
Switch off. If this is not possible, protect yourself with dry insulating material
and pull or push the victim clear of the conductor.
ALWAYS send for trained first aid or medical assistance IMMEDIATELY.
In cases of low voltage electric shock (including public supply voltages), serious injuries and even
death, may result. Direct electrical contact can stun a casualty causing breathing, and even the heart,
to stop. It can also cause skin burns at the points of entry and exit of the current.
In the event of an electric shock it may be necessary to carry out artificial respiration. ALWAYS
send for trained first aid or medical assistance IMMEDIATELY.
If the casualty is also suffering from burns, flood the affected area with cold water to cool,
until trained first aid or medical assistance arrives.
RF radiation
68P02901W56-Q 11
24 May 2004 CONTROLLED INTRODUCTION
General warnings
Relevant standards (USA and EC), to which regard should be paid when working with RF equipment are:
• ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure
to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors.
Laser radiation can come from either the data in/out connectors or unterminated
fibre optic cables connected to data in/out connectors.
Lifting equipment
When dismantling heavy assemblies, or removing or replacing equipment, the competent responsible
person must ensure that adequate lifting facilities are available. Where provided, lifting frames
must be used for these operations. When equipment has to be manhandled, reference must be
made to the Manual Handling of Loads Regulations 1992 (UK) or to the relevant manual handling
of loads legislation for the country in which the equipment is used.
Parts substitution
12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
General warnings
Battery supplies
Lithium batteries
Contact your local Motorola office for how to return defective lithium batteries.
68P02901W56-Q 13
24 May 2004 CONTROLLED INTRODUCTION
General cautions
General cautions
Observe the following cautions during operation, installation and maintenance of the equipment
described in the Motorola manuals. Failure to comply with these cautions or with specific cautions
elsewhere in the Motorola manuals may result in damage to the equipment. Motorola assumes no
liability for the customer’s failure to comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution labels fitted to
the equipment. Caution labels must not be removed, painted over or obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this manual.
These must be observed by all personnel at all times when working with the equipment, as must
any other cautions given in text, on the illustrations and on the equipment.
Fibre optics
Fibre optic cables must not be bent in a radius of less than 30 mm.
Static discharge
14 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Devices sensitive to static
Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of
insulation that is susceptible to damage from electrostatic charge. Such a charge applied to
the leads of the device could cause irreparable damage.
These charges can be built up on nylon overalls, by friction, by pushing the hands into high
insulation packing material or by use of unearthed soldering irons.
MOS devices are normally despatched from the manufacturers with the leads short circuited together,
for example, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic
foam. Provided the leads are short circuited it is safe to handle the device.
In the event of one of these devices having to be replaced, observe the following
precautions when handling the replacement:
• Leave the short circuit on the leads until the last moment. It may be necessary to replace
the conductive foam by a piece of wire to enable the device to be fitted.
• Do not wear outer clothing made of nylon or similar man made material.
A cotton overall is preferable.
• If possible work on an earthed metal surface or anti-static mat. Wipe insulated plastic
work surfaces with an anti-static cloth before starting the operation.
• All metal tools should be used and when not in use they should be placed on an earthed surface.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to
electrostatic damage. However PCBs should be handled with care, preferably by their edges and
not by their tracks and pins, they should be transferred directly from their packing to the equipment
(or the other way around) and never left exposed on the workbench.
68P02901W56-Q 15
24 May 2004 CONTROLLED INTRODUCTION
Motorola manual set
The Motorola manual sets provide the information needed to operate, install and maintain the Motorola
equipment. Manuals for the GSM, GPRS and UMTS products are available on the following media:
• Printed hard copy.
Each CD-ROM includes all manuals related to a specified main GSM, GPRS or UMTS software
release, together with current versions of appropriate hardware manuals, and has additional
navigation facilities. A snapshot copy of on-line documentation is also included, though it
will not be updated in line with subsequent point releases.
The CD-ROM does not include Release Notes or documentation supporting specialist
products such as MARS or COP.
Use the Motorola 68Pxxxxxxxx order (catalogue) number to order hard copy manuals or CD-ROMs.
All orders must be placed with your Motorola Local Office or Representative.
16 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
GMR amendment
GMR amendment
Changes to a manual that occur after the printing date are incorporated into the manual using
General Manual Revisions (GMRs). GMRs are issued to correct Motorola manuals as and when
required. A GMR has the same identity as the target manual. Each GMR is identified by a
number in a sequence that starts at 01 for each manual at each issue.
GMR availability
• Printed hard copy - Complete replacement content or loose leaf pages with amendment list.
Remove and replace pages in this manual, as detailed on the GMR instruction sheet.
GMR instructions
When a GMR is inserted in this manual, the amendment record below is completed to
record the GMR. Retain the instruction sheet that accompanies each GMR and insert it in
a suitable place in this manual for future reference.
68P02901W56-Q 17
24 May 2004 CONTROLLED INTRODUCTION
GMR amendment
18 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
1
Introduction to statistics
Statistics are pieces of numerical data which have been collected and systematically categorized. In
GSM terms, the data collected is generated from network and system events, categorized as a raw
statistic type and used to determine system quality of service. This allows network operators and
administrators to gauge service accessibility, integrity and retainability.
The following topics are described:
• "Introduction to GSM Statistics Manual" on page 1-2
68P02901W56-Q 1-1
24 May 2004 CONTROLLED INTRODUCTION
Introduction to GSM Statistics Manual Chapter 1: Introduction to statistics
Statistics
This manual describes the statistical measurements generated by the BSS in response to monitored
network and system events. The statistics include statistical measurements defined in the GSM
Technical Specification 12.04, plus additional Motorola-defined statistics.
Network operators may use raw and processed statistics for the following network
management and planning functions:
• Quality of service monitoring.
Service accessibility.
Service integrity.
Service retainability.
• Fault finding.
• Optimization.
• Network planning.
Raw statistics
The BSS generates raw statistics for reporting individual network performance. The OMC-R
processes raw statistics to create key, network health and custom statistics. These statistics include
call processing, interface, and processor utilization measurements.
1-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Introduction to GSM Statistics Manual
Call statistics
Call processing functions and features generate statistics that show how the system is performing.
Interface statistics
Terrestrial interface activities generate interface statistics that show the activity on and condition of the interface
links. The interface links are the physical connections between the MS, BSS, and MSC network elements.
Key statistics
Key statistics are generated at the OMC-R by processing raw statistics generated by the BSS,
using predefined algorithms. These statistics are designed to give an overall indication of the
condition of the system and allow comparisons of similar time periods over a span of time, to
help detect congestion trends and possible performance degradation.
Key statistics are also provided to facilitate the monitoring of the most important network parameters.
For example, various handover failure statistics may be combined and averaged over the total
number of calls, to produce a handover failure rate key statistic.
The following are the key statistics groupings:
• Call Summary.
• Channel Usage.
• Connection Establishment.
• RF Loss Summary.
• MTL Utilization.
Network health statistics are calculated at the OMC-R using a combination of raw and key statistics.
These statistics are used to create BSS network performance reports. These reports provide an
indication of the networks health from the subscribers perspective.
The following are the network health report groupings:
• Health check.
• GPRS performance.
• Handover performance.
• TCH congestion.
68P02901W56-Q 1-3
24 May 2004 CONTROLLED INTRODUCTION
Introduction to GSM Statistics Manual Chapter 1: Introduction to statistics
• SDCCH congestion.
• Paging performance.
• Radio performance.
Custom statistics
The OMC-R permits the creation of custom statistics using the algebraic combination of existing
raw and key statistics. Refer to the Installation and Configuration: GSM System Configuration
(68P02901W17) manual for procedures on creating custom statistics.
Statistic terms
This manual contains the following statistical terms throughout this manual:
Application process - The process responsible for creating and pegging a statistic.
Bin - A collection area used for the storage of cumulative values for distribution and counter array statistics.
Distribution statistics:
The use of a bin is for measuring the frequency of an event. The measurement can be done
by time (weighted distributions) or by occurrences (normal distributions). There are 10 bins
(numbered 0 - 9). Each bin has a low to high range.
Counter array statistics:
The use of a bin is for counting the number of occurrences on a per scenario or cause basis. The
number of bins varies based on the number of causes being tracked.
Cumulative value - The total value for the entire interval.
Default time interval - The key statistics default time interval is 0.5 hours when computing all key statistics.
The interval used for two key statistics, TCH_MEAN_HOLDING_TIME and SD-
CCH_MEAN_HOLDING_TIME, is specified in seconds. To convert the default value of
0.5 hours to seconds, multiply the 0.5 hours by 3600.
Interval - A recording period of time in which a statistic is pegged. The default time is 30
minute intervals and there are 12 intervals of data stored at the BSS.
Interval expiry - The end of an interval.
Maximum value - The highest reported value for the interval.
Mean value - The average value for the interval.
Minimum value - The lowest reported value for the interval.
Number of periods - The value used in calculating the mean for durations. This value is
incremented by one every time the duration timer is stopped.
1-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Introduction to GSM Statistics Manual
Number of samples - The value used in calculating the mean for distributions. For a normal distribution,
this value is incremented by one each time a value is reported. For a weighted distribution, this
value is incremented by the time difference since the last reported value.
Peg - A peg is a single incremental action modifying the value of a statistic.
Pegging - Pegging refers to recording a statistical value.
Reported value - The value reported by the application process pegging the statistic.
SUM - In the key and network health statistic formulae, SUM is the arithmetic total of a mathematical
formula for one or more cells selected in the OMC-R GUI Performance Management window. The
mathematical formula may include a single raw statistic or a set of arithmetic functions.
Temporary value - This value is used in weighted distributions. The application process
supplies both the reported value (which is used to update a bin) and the temporary value
(which is stored for updating a bin at interval expiry).
Threshold value - The threshold value can be set in the configuration management database using the
MMI. When the reported value for a statistic equals the threshold value, an alarm is sent from the BSS to
the OMC-R. Thresholds may also be specified for individual bins in counter array statistics.
68P02901W56-Q 1-5
24 May 2004 CONTROLLED INTRODUCTION
Types of raw statistics Chapter 1: Introduction to statistics
Introduction
• Counter array.
• Gauge.
• Duration.
• Normal distribution.
• Weighted distribution.
Counter statistics
A counter statistic is the cumulative value of an event reported by an application process. The
application process increments or pegs the counter statistic by the reported value during an interval.
The ALLOC_SDCCH statistic is an example of a counter statistic.
Maximum value
The maximum value of a counter statistic is 4294967294 (hex= 0xfffffffe). If a counter statistic reaches
the maximum value, it will remain at that value until the interval expiry.
Interval expiry
Interval expiry is the end of a statistic interval. At the interval expiry, the BSS saves
the counter statistic value then resets it to zero.
1-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Types of raw statistics
Counter array statistics are the total number of times an event occurs and a breakdown of the causes
or reasons why the event occurred during an interval. When an event occurs, the BSS increments
the individual cause or reason by the value reported by the application at the interval expiry. The
OK_ACC_PROC statistic is an example of a counter array statistic.
Display convention
The convention used in this manual for presenting a specific bin of a counter array statistic is COUNTER
ARRAY STATISTIC NAME[bin name]. For example, OK_ACC_PROC[CM_REESTABLISH]
is the CM_REESTABLISH bin of the OK_ACC_PROC counter array statistic.
Maximum value
The maximum value for the total and individual cumulative values is 65534 (hex=0xfffe). If a bin count
reaches this value during a period, the bin contents will remain at the maximum value until the interval expiry.
Interval expiry
Interval expiry is the end of a statistic interval. At the interval expiry, the BSS saves the counter array
total values and the values of the individual bins then resets them to zero.
Gauge statistics
Gauge statistics report the maximum and mean values of a statistic for an interval. The
IDLE_TCH_INTF_BAND0 statistic is an example of a gauge statistic.
While a gauge statistic may result in the report of a reported negative value, the cumulative value
may not be a negative value. The BSS checks the cumulative before calculating the mean value,
and if the result is a negative number, it will set the mean zero.
Interval expiry
Interval expiry is the end of a statistic interval. At the interval expiry, the BSS saves the mean
and maximum gauge statistic values then resets them to zero.
68P02901W56-Q 1-7
24 May 2004 CONTROLLED INTRODUCTION
Types of raw statistics Chapter 1: Introduction to statistics
Duration statistics
A duration statistic is a group of values associated with timing of events controlled by an application
process. The duration statistics include the total duration, mean, maximum, and minimum values. The
FLOW_CONTROL_BARRED statistic is an example of a duration statistic.
Total duration
The OMC only reports the total duration.
The total duration is the length of time an event occurs during an interval. It is a cumulative
value reported in milliseconds. When the event starts, the BSS saves the start time of day (in
milliseconds). When the event ends, the BSS saves the stop time of day (in milliseconds). The
BSS calculates the total duration using the following formula:
stop time - start time
Mean value
The BSS calculates the mean duration by dividing the total duration by the period counter. The BSS
increments the period counter each time a measured event occurs during an interval.
mean = total time / period counter
Maximum value
The maximum value of a duration statistic is 86400000 (the number of milliseconds in 24 hours).
Interval expiry
Interval expiry is the end of a statistic interval. The following processes occur at the interval expiry:
• If no events occur during the interval, the BSS sets the duration minimum value is to
zero. The BSS saves this minimum value then resets it to 0xffffffff.
• The BSS saves the duration mean and maximum values then resets them to zero.
• The BSS resets the period counter and cumulative values to zero.
1-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Types of raw statistics
Normal distribution statistics are the number of times the reported value of an event falls within a
specified range. A distribution statistic is a single row array of 10 bins, numbered 0-9. The BSS also
saves the minimum reported value, the maximum reported value, and a calculated mean of the reported
values. The OMC only reports the distribution mean, maximum, and minimum values.
Bins
Each bin represents a range of values reported by an application. Each time an application reports
a value, the BSS increments the bin corresponding to the reported value by one. The BSS also
increments the sample count by one and calculates the total of all reported values during the
interval. The disp_stats command displays the individual bin values.
The operator may specify the range of values represented by each bin or use the system defaults. The
range of values to be represented by each bin is dependent on the focus of the statistical analysis.
Narrow bin ranges permit closer examination of periods of greatest activity.
Mean value
The BSS calculates the mean value by dividing the cumulative total of the reported values by the sample count.
If there are gaps in the bin ranges, some occurrences of reported events are not included
in the bin counts. For example, if the assigned range of values of two adjacent bins
are 10-15 and 17-20, a reported event with a value of 16 is not recorded. The mean
value does not account for the unrecorded event.
Histogram
A normal distribution statistic may be illustrated as a histogram. Figure 1-1 shows the range of
values assigned to bin 0 is 0-10, bin 1 is 11-20, and bin 7 is 71-80. The histogram shows bins
0 and 1 each contain two occurrences and bin 7 one occurrence.
COUNT 2
0
0 1 2 3 4 5 6 7 8 9
BINS
68P02901W56-Q 1-9
24 May 2004 CONTROLLED INTRODUCTION
Types of raw statistics Chapter 1: Introduction to statistics
Interval expiry
Interval expiry is the end of a statistic interval. The following events occur at the interval expiry:
1. The mean value is calculated. If the number of reported events is not equal to
0, the mean value is calculated by dividing the cumulative value of all of the
reported events by the number of reported events.
2. The distribution minimum value is saved and reset to 0xffffffff. If no value was
received during the interval, the duration minimum value is to 0.
3. The distribution mean value and maximum value are saved and reset to 0.
4. The number of reported events and the cumulative value are reset to 0.
Weighted distribution statistics are the length of time that the reported value of an event falls
within a specified range. These statistics are placed in a single row array of 10 bins, numbered
0-9, and a mean duration of the reported events. The minimum and maximum durations of the
reported values are also saved and reported at the end of the interval.
Bins
Each bin is defined to represent a range of values. Each time an application process reports a
value, the bin corresponding to the reported value is incremented by the length of time the reported
value stays within the bin’s specified range. This allows the number of times a reported value
falls within a specific range to be used to calculate the mean.
The range of values that may be assigned to each of the 10 bins in the array is variable. The range of
values may be sized based on the focus of the analysis to be performed. For example, when measuring a
statistic, the range of values assigned to the bins may be assigned to reflect the periods of greatest activity.
By narrowing the bin ranges, the periods of greatest activity may be more closely examined.
If there are gaps in the bin ranges, some occurrences of reported events are not included
in the bin counts. For example, if the assigned range of values of two adjacent bins
are 10-15 and 17-20, a reported event with a value of 16 is not recorded. The mean
value does not account for the unrecorded event.
1-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Types of raw statistics
Mean value
The mean value is the statistical average of all of the reported values divided by the number of reported events.
The mean for a weighted distribution statistic is not a duration value and is
not calculated using the bin values.
Histogram
A weighted distribution statistic may be illustrated as a histogram. Figure 1-2 shows the range
of values assigned to bin 0 is 0-10 and bin 7 is 71-80. The following histogram shows that
the duration of the event reporting values from 0-10 was 40 milliseconds and the duration of
the events reporting values from 71-80 was 20 milliseconds.
40
30
COUNT 20
10
0
0 1 2 3 4 5 6 7 8 9
BINS
68P02901W56-Q 1-11
24 May 2004 CONTROLLED INTRODUCTION
Types of raw statistics Chapter 1: Introduction to statistics
Interval expiry
Interval expiry is the end of a statistic interval. The following events occur at the interval expiry:
1. Stop any running timers.
2. The mean value is calculated. If the number of reported events is not equal to
0, the mean value is calculated by dividing the cumulative value of all of the
reported events by the number of reported events.
3. The distribution minimum value is saved and reset to 0xffffffff. If no value was received
during the expired interval, the duration minimum value is to 0.
4. The distribution mean value and maximum value are saved and reset to 0.
5. The number of reported events and the cumulative value are reset to 0.
1-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Statistic usages
Statistic usages
Quality of service is determined by statistics related to service accessibility, integrity, and retainability.
Service accessibility
Statistics associated with the following processes are used to determine service accessibility:
• Mobile registration.
• Mobile paging.
• Network accessibility.
Service integrity
Statistics associated with the following processes are used to determine service integrity:
• Call clarity.
• Interference.
Service retainability
Statistics associated with premature releases are used to determine service retainability.
Service accessibility
Service accessibility is associated with the following call setup and clearing processes:
• Mobile registration and paging.
• Network accessibility.
68P02901W56-Q 1-13
24 May 2004 CONTROLLED INTRODUCTION
Statistic usages Chapter 1: Introduction to statistics
Network accessibility
A registered MS should be able to access the network. Access denial is divided into three main categories:
• Call blocking.
No signalling channel (SDCCH) is available.
The raw statistics TCH_DELAY and CALLS_QUEUED are associated with call
set-up time and answer signal delay.
1-14 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Statistic usages
Service integrity
• Lack of interference.
Call clarity
Call clarity is measured by the uplink-downlink path loss difference on the air interface. The raw
statistic PATH_BALANCE is the only measurement associated with call clarity.
Lack of interference
The lack of interference is measured by the bit error rate and the interference level on monitored idle channels.
The raw statistics BER and INTF_ON_IDLE are the only measurements associated with lack of interference.
Service retainability
• The call releases due to equipment failure (MSC, base site, or MS).
68P02901W56-Q 1-15
24 May 2004 CONTROLLED INTRODUCTION
Statistic usages Chapter 1: Introduction to statistics
Fault finding
GSM statistics can be used to find certain classes of faults in the cellular system. A set of statistics
which may be used to perform this function is identified in this section.
Monitoring Faults
Hard failures are normally identified via alarm surveillance. However, it is possible for a system
component to deteriorate over time, while still continuing to function. The deterioration may manifest
itself in a number of ways such as an increase in dropped call rate, or a lower call completion rate.
Monitoring of these system parameters over time can provide the operator with an early indication
of performance degradation due to deterioration in hardware components.
Types of faults
Example of the types of faults that may be identified using statistics include:
• Damaged antennas.
• Frequency drift.
• Electromechanical problems.
Problems with remote combiners.
Noisy channels.
Optimization
Optimization of system parameters is necessary to ensure that the installed cellular infrastructure
is utilized as efficiently as possible. Statistics can be used to monitor and verify the effects of
optimization activities. For example, if handover thresholds are adjusted, statistics may be used to
verify that the new threshold results in an improved handover success rate.
Optimization of a GSM network is a process whereby several BSS database parameters are fine-tuned from
their default values and antenna installations are adjusted to improve call success rate and quality.
By optimizing a network, the performance of the cellular equipment is verified and a benchmark
obtained for the system that may be used for subsequent expansion. The results may also be used
to modify the original data used in the frequency planning tool.
Network planning
It is possible to determine whether or not the network is correctly dimensioned for the offered traffic
load. Statistics that monitor resource utilization and congestion can be used to determine when the
network needs to be expanded, (or contracted, if resources are being under utilized).
1-16 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Statistic usages
Installation and commissioning of cellular equipment is a complex procedure that must be verified after
completion. Part of the verification procedure uses statistics to ensure that the system is operational.
Drive testing is currently one of the means used to verify installation of the network.
Statistics can be used to verify the data collected during drive testing, in order to ensure
that all components of the system are operational.
68P02901W56-Q 1-17
24 May 2004 CONTROLLED INTRODUCTION
Ladder diagrams Chapter 1: Introduction to statistics
Ladder diagrams
The relationship between statistics and call processing elements and functions are graphically
represented as ladder diagrams in Chapter 19, "Ladder diagrams".
Ladder diagrams show the relationships between the MS, BSS, and MSC elements, represented as vertical lines.
The message flows between the network elements are presented as horizontal lines representing
a sequential flow of events. Arrows are used to indicate the direction of the message flow.
Message names are placed above the directional line.
Intermediate network element functions are placed on the vertical lines as a sequential reference. Parallel
functions may also be included as separate vertical lines for additional reference.
Statistics associated with individual messages are located immediately below the directional line. All of the
statistics that may be generated as the result of the process flow will be listed on the diagram.
Example
TIMEOUT
CHAN_REQ_MS_FAIL
1-18 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
2
Statistical operations
Statistical data can be employed in various ways to describe the operation of the system. The view an
operator gets of how the system is performing can be shown through the way statistics are displayed. The
topics described here show how statistical property displays can be enabled and configured.
The following topics are described:
• "Enabling/disabling a statistic" on page 2-2
68P02901W56-Q 2-1
24 May 2004 CONTROLLED INTRODUCTION
Enabling/disabling a statistic Chapter 2: Statistical operations
Enabling/disabling a statistic
Description
Statistics must be enabled to obtain statistical data. The stat_mode command enables and
disables a statistic. Refer to the Technical Description: BSS Command Reference (68P02901W23)
for a detailed description of the stat_mode command.
• ALLOC_SDCCH.
• ALLOC_SDCCH_FAIL.
• ALLOC_TCH.
• ALLOC_TCH_FAIL.
• BUSY_SDCCH.
• BUSY_TCH.
• IN_INTER_BSS_HO.
• IN_INTRA_BSS_HO.
• INTRA_CELL_HO.
• MA_CMD_TO_MS_BLKD.
• MA_REQ_FROM_MSC.
• OK_ACC_PROC.
• OUT_INTER_BSS_HO.
• OUT_INTRA_BSS_HO.
• RF_LOSSES_SD.
• TOTAL_CALLS.
2-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Enabling/disabling a statistic
Enabling a statistic
A statistic is enabled by entering the stat_mode command using the following syntax:
stat_mode <meas_type> on [<location>] [<cell_desc>]
Where: is:
meas_type the statistic being enabled
on enable mode
location the location of the statistic being
enabled, if required
cell_desc the cell name or number, if
required
Example
stat_mode rf_losses_tch on cell_name=mid34a
Where: is:
rf_losses_tch meas_type
on enable mode
cell_name=mid34a cell_desc
System response:
COMMAND ACCEPTED
Disabling a statistic
A statistic is disabled by entering the stat_mode command using the following syntax:
stat_mode <meas_type> off [<location>] [<cell_desc>]
Where: is:
meas_type the statistic being disabled
off disable mode
location the location of the statistic being
disabled, if required
cell_desc the cell name or number, if
required
68P02901W56-Q 2-3
24 May 2004 CONTROLLED INTRODUCTION
Enabling/disabling a statistic Chapter 2: Statistical operations
Example
stat_mode mtp_link_ins off
Where: is:
mtp_link_ins meas_type
off disable mode
System response:
COMMAND ACCEPTED
2-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Displaying enabled statistics
Description
A listing of the currently enabled statistics may be displayed using the disp_enable_stat
command. Refer to the Technical Description: BSS Command Reference (68P02901W23) for
a detailed description of the disp_enable_stat command.
Specific listings may be generated based on the arguments entered with the disp_en-
able_stat command, including:
• No argument - A listing of all currently enabled statistics will be presented.
• BSS - A listing of all of the currently enabled BSS-wide statistics will be presented.
• location - A listing of all of the currently enabled statistics for the specified site will be presented.
• meas_type - A listing of all of the currently enabled statistics for the specified
measurement type will be presented.
A listing of all of the enabled statistics may be displayed by entering the disp_enable_stat
command using the following syntax:
disp_enable_stat
System response:
Enabled Non-Cell Statistics
ma_req_from_msc_fail
page_req_from_msc_fail
ho_req_msc_proto
mtp_sl_fail
mtp_sl_fibr
mtp_sl_ack
mtp_sl_error_rate
mtp_sl_congestion
mtp_sl_alignment
mtp_su_error
mtp_neg_acks
mtp_changeover
mtp_changeback
mtp_restoration
mtp_start_rpo
mtp_stop_rpo
68P02901W56-Q 2-5
24 May 2004 CONTROLLED INTRODUCTION
Displaying enabled statistics Chapter 2: Statistical operations
mtp_mgt_inhibit
mtp_mgt_uninhibit
mtp_re_tx
mtp_sif_sio_rx
mtp_msu_tx
mtp_msu_rx
sl_congestion
sl_stop_congestion
msu_discarded
congestion_lost_msu
sif_sio_rx_opc
sif_sio_tx_dpc
sif_sio_type
routing_syntax
routing_unknown
sccp_msgs
sccp_msgs_tx
sccp_msgs_rx
invalid_frames_rx
i_frames_rx
i_frames_tx
sabm_tx frmr
n2_expiry
mtp_link_ins
mtp_unavailable
mtp_local_mgt
mtp_remote_mgt
mtp_linkfail
mtp_remote_proc
mtp_local_busy
mtp_congestion
cpu_usage
.
.
.
Enabled Statistics for Cell 001 01 03e7h 0028h
{23658} egprs_avail_pdtch
rf_losses_tch
rf_losses_sd
intra_cell_ho
in_inter_ho
out_inter_ho
intra_bss_ho
access_per_rach
.
.
.
tch_delay
intf_on_idle
busy_tch
busy_sdcch
ber
.
.
The remaining cell statistics follow until all of the enabled statistics have been displayed.
2-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Displaying statistic values
Description
The current value of individual statistics for a specific interval can be displayed using the disp_stats
command. Displayed information may represent incremental (peg count) or duration values,
depending on the specified statistic. Refer to the Technical Description: BSS Command Reference
(68P02901W23) for a detailed description of the disp_stats command.
The value of a statistic for the current interval cannot be displayed. The disp_interval
command may be used to display completed intervals.
When counter array statistics are displayed, the values for the individual bins are displayed.
A total value of all of the bins may also be displayed for some counter array statistics. Refer
to the descriptions of individual counter array statistics.
The disp_stats command is entered using the one of the following syntax:
Where: is:
interval a completed statistical interval
meas_type the name of the statistic to be
displayed
cell_desc the cell name or number, if
required
board_desc the board_id, if required
When using the disp_stats command to display a per link statistic, the generated output
will report all links for a specified board.
68P02901W56-Q 2-7
24 May 2004 CONTROLLED INTRODUCTION
Displaying statistic values Chapter 2: Statistical operations
Example
This example shows the interaction required to display the value of a counter array
statistic which includes a total value.
disp_stats 5 out_ho_cause_atmpt cell_number=5 4 3 2 1 61986 34944
Where: is:
5 interval
out_ho_cause_atmpt statistic
5 4 3 2 1 61986 34944 cell_number
System response:
SITE: 0 CELL #: LAC = f222h CI = 8880h
MEAS_TYPE : OUT_HO_CAUSE_ATMPT
Total: 110
Uplink Quality : 10
Uplink Level : 20
Downlink Quality : 10
Downlink Level : 10
Distance : 10
Uplink Interference : 10
Downlink Interference : 10
Power Budget : 10
Congestion : 10
Adjacent Channel Interference : 10
2-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Setting the statistic interval
Description
The stat_interval is a nonstatistical parameter that is used to specify the interval. Refer
to the Technical Description: BSS Command Reference (68P02901W23) for a detailed
description of the stat_interval parameter.
In normal operations, key statistics and health indicators are calculated by the OMC-R
based on the default interval of 30 minutes. If the interval is changed to 60 minutes, it
must be reset to 30 minutes for normal operations.
Where: is:
stat_interval parameter name
30 or 60 valid values for the parameter, in
minutes
location This is a BSS-wide parameter and
0 is the only valid value for this
argument.
Example
This example shows the interaction required to change the statistical interval to 60 minutes.
chg_element stat_interval 60 0
Where: is:
stat_interval parameter name
60 60 minutes
0 location
System response:
COMMAND ACCEPTED
68P02901W56-Q 2-9
24 May 2004 CONTROLLED INTRODUCTION
Displaying the statistic interval Chapter 2: Statistical operations
Description
The stat_interval is a non-statistical parameter that is used to specify the interval. The current interval
may be displayed using the disp_element command using the following syntax:
disp_element stat_interval <location>
Where: is:
stat_interval parameter name
location This is a BSS-wide parameter and
0 is the only valid value for this
argument.
Example
This example shows the interaction required to display the statistical interval.
chg_element stat_interval 0
Where: is:
stat_interval parameter name
0 location
System response:
stat_interval = 30
2-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Displaying the statistic interval start times
Description
The starting times of the statistic intervals may be displayed by entering the disp_interval command.
Refer to the Technical Description: BSS Command Reference (68P02901W23) for a detailed description
of the disp_interval command. No arguments are required with the command.
On startup, the first start time (interval 0) corresponds to current time of the system clock. The
second start time (interval 1) automatically becomes synchronized to the next hour (:00) or
half hour (:30), depending upon the current statistic interval.
Example
This example shows the interaction required to display the starting times of the statistical intervals where
the statistic interval is 30 and the disp_interval command was entered at 1230.
disp_interval
System response:
Interval Start Time (HH:MM:SS)
-------- --------------------
0 09:08:48
1 09:30:00
2 10:00:00
3 10:30:00
4 11:00:00
5 11:30:00
6 12:00:00
7 12:30:00
8 None
9 None
10 None
11 None
The displayed starting times depend on the time of day that the disp_interval command is entered. When
the command is entered, the current set of 12 start times is presented. If the command is entered after
interval 11 would be completed, the listing displays the next set of 12 interval start times.
Example
If the disp_interval command is entered at 1501, the following output displays:
disp_interval
68P02901W56-Q 2-11
24 May 2004 CONTROLLED INTRODUCTION
Displaying the statistic interval start times Chapter 2: Statistical operations
System response:
Interval Start Time (HH:MM:SS)
-------- --------------------
0 15:00:00
1 09:30:00
2 10:00:00
3 10:30:00
4 11:00:00
5 11:30:00
6 12:00:00
7 12:30:00
8 13:00:00
9 13:30:00
10 14:00:00
11 14:30:00
2-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Setting statistic properties
Description
The properties for statistics (except for the statistic interval) may be changed using the chg_stat_prop
command. Refer to the Technical Description: BSS Command Reference (68P02901W23) for
a detailed description of the chg_stat_prop command.
The specific properties that may be changed are dependent on the statistic type.
• The alarm threshold may be changed for counter, counter array and gauge statistics
if an alarm is associated with the statistic.
Setting a threshold
Some counter and gauge statistics may be associated with alarms. Threshold values may
be specified for these statistics. An alarm is sent to the Operations and Maintenance Centre
- Radio (OMC-R) when the threshold is reached.
A threshold is specified by entering the chg_stat_prop command using the following syntax:
chg_stat_prop <meas_type> [<location>] [<cell_desc>]
Where: is:
meas_type a counter or gauge statistic
location the location of the statistic whose
threshold is being set, if required
cell_desc the cell name or number, if
required
Example
This example shows the interaction required to change the alarm threshold for the
rf_losses_tch statistic for cell_name=mn14b at site 1.
chg_stat_prop rf_losses_tch cell_name=mn14b
Where: is:
rf_losses_tch meas_type
cell_name=mn14b cell_desc
68P02901W56-Q 2-13
24 May 2004 CONTROLLED INTRODUCTION
Setting statistic properties Chapter 2: Statistical operations
System response:
Enter the alarm threshold: 500
COMMAND ACCEPTED
Counter statistics
Counter statistics that may be assigned a threshold are presented in Table 2-1.
2-14 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Setting statistic properties
The maximum value that may be assigned to a threshold (2147483647) is set as the default
value upon initialization of the CM database.
The default for the maximum value in the Valid Values column is 2147483647.
Distribution statistics include 10 bins, numbered 0 to 9. Each bin represents a range of values. When events
are reported, the bin corresponding to the reported value is incremented. The range of values for the individual
bins in a distribution statistic may be specified with the chg_stat_prop command using the following syntax:
chg_stat_prop <meas_type> [<location>] [<cell_desc>]
Where: is:
meas_type a normal or weighted distribution
statistic
location the location of the statistic whose
bin range is being set, if required
cell_desc the cell name or number, if
required
The bin ranges for the BER statistic may not be modified.
68P02901W56-Q 2-15
24 May 2004 CONTROLLED INTRODUCTION
Setting statistic properties Chapter 2: Statistical operations
Bin ranges
Distribution statistics include 10 bins, numbered 0 to 9. The range of values to be measured by the
statistic must be considered when assigning values for the individual bins in the distribution. For
example, if the possible range of values to be measured is from 0 to 100, then the minimum value
for bin 0 should be 0, and the maximum value for bin 9 should be 100.
Gaps in the range of values covered should be avoided when assigning the minimum and maximum values for
the individual bins. For example, if bin 0 covers values from 0 to 10 and bin 1 covers values from 12 to 15, a
gap would exist for the value 11. This would cause any report of a value equal to 11 to be ignored.
Bin minimums and maximums may be set to the same value for the same bin. This allows a specific
value to be reported within the overall distribution. For example, if the minimum and maximum values
for a bin are both specified to be 10, the bin is pegged each time a value of 10 is reported.
Default ranges
Distribution statistics have default ranges for bins.
Example
This example shows the interaction required to change the minimum and maximum values for
two bins of the BUSY_TCH statistic for all cells at site 1.
chg_stat_prop busy_tch 1 all
Where: is:
busy_tch meas_type
1 location
all all cells at the specified site
System response:
Enter the bin number(s): 0,1
Enter the min value for bin 0: 0
Enter the max value for bin 0: 5
Enter the min value for bin 1: <return>
7 Enter the max value for bin 1: 7
COMMAND ACCEPTED
2-16 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Displaying statistic properties
Description
The properties of individual statistics may be displayed using the disp_stat_prop command. The
information and presentation format are dependent upon the statistic type, including:
• Alarm severity and threshold values are displayed for counter and gauge statistics.
• The mode and type only are displayed for the duration statistics.
68P02901W56-Q 2-17
24 May 2004 CONTROLLED INTRODUCTION
Displaying statistic properties Chapter 2: Statistical operations
Counter statistic properties are displayed by entering the disp_stat_prop command using the following syntax:
disp_stat_prop <meas_type> [<location>] [<cell_desc>]
Where: is:
meas_type a counter statistic
location the location of the statistic whose
properties are being displayed, if
required
cell_desc the cell name or number, if
required
Example
This example shows the interaction required to display the properties for the TO-
TAL_CALLS statistic for all cells at site 1.
disp_stat_prop total_calls 1 all
Where: is:
total_calls meas_type
1 location
all all cells at the specified location
System response:
STATISTIC: TOTAL_CALLS SITE: 1
TYPE: PER CELL OBJECT:
COUNTER
2-18 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Displaying statistic properties
Gauge statistic properties are displayed by entering the disp_stat_prop command using the following syntax:
disp_stat_prop <meas_type> [<location>] [<cell_desc>]
Where: is:
meas_type a gauge statistic
location the location of the statistic whose
properties are being displayed, if
required
cell_desc the cell name or number, if
required
Example
This example shows the interaction required to display the properties for the AVAILABLE_TCH
statistic for cell_number=5 4 3 2 1 61698 34776 at site 1.
disp_stat_prop available_tch 1 cell_number=5 4 3 2 1 61698 34776
Where: is:
available_tch meas_type
1 location
cell_number=5 4 3 2 1 61698 34776 cell_desc
System response:
STATISTIC: AVAILABLE_TCH SITE: 1
TYPE: PER CELL OBJECT: GAUGE
68P02901W56-Q 2-19
24 May 2004 CONTROLLED INTRODUCTION
Displaying statistic properties Chapter 2: Statistical operations
Where: is:
meas_type a distribution statistic
location the location of the statistic whose
properties are being displayed, if
required
cell_desc the cell name or number, if
required
Example
This example shows the interaction required to display the properties for the BUSY_TCH
statistic for cell_number=5 4 3 2 1 61698 34776 at site 1.
disp_stat_prop busy_tch 1 cell_number=5 4 3 2 1 61698 34776
Where: is:
busy_tch meas_type
1 location
5 4 3 2 1 61698 34776 cell_desc
System response:
STATISTIC: BUSY_TCH SITE: 1
TYPE: PER CELL OBJECT:
DISTRIB
2-20 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Displaying statistic properties
8 16 2147174832
9 214174833 2141749879
68P02901W56-Q 2-21
24 May 2004 CONTROLLED INTRODUCTION
Displaying statistic properties Chapter 2: Statistical operations
Counter array statistic properties are displayed by entering the disp_stat_prop com-
mand using the following syntax:
disp_stat_prop <meas_type> [<location>] [<cell_desc>]
Where: is:
meas_type a counter array statistic
location the location of the statistic whose
properties are being displayed, if
required
cell_desc the cell name or number, if
required
Example
This example shows the interaction required to display the properties for the
OUT_HO_CAUSE_ATMPT statistic.
disp_stat_prop out_ho_cause_atmpt cell_number=5 4 3 2 1 62259 8736
Where: is:
out_ho_cause_atmpt meas_type
5 4 3 2 1 62259 8736 cell_desc
System response:
STATISTIC: OUT_HO_CAUSE_ATMPT SITE: 2
TYPE: PER CELL OBJECT: COUNTER
ARRAY
BIN # CAUSE
--------- ---------
0 ENABLED NO ALARM
1 ENABLED NO ALARM
2 ENABLED NO ALARM
3 ENABLED NO ALARM
4 ENABLED NO ALARM
5
6
7
8
9
CELL # MODE
2-22 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Displaying statistic properties
------------------------- -------
543 21 62259 (f333h) 8736 (2220h) DISABLED
68P02901W56-Q 2-23
24 May 2004 CONTROLLED INTRODUCTION
Displaying statistic properties Chapter 2: Statistical operations
Duration statistic properties are displayed by entering the disp_stat_prop command using the following syntax:
disp_stat_prop <meas_type> [<location>] [<cell_desc>]
Where: is:
meas_type a duration statistic
location the location of the statistic whose
properties are being displayed, if
required
cell_desc the cell name or number, if
required
Example
This example shows the interaction required to display the properties for the
FLOW_CONTROL_BARRED statistic.
disp_stat_prop flow_control_barred 2 5 4 3 2 1 62259 8736
Where: is:
flow_control_barred meas_type
2 location
5 4 3 2 1 62259 8736 cell_desc
System response:
STATISTIC: FLOW_CONTROL_BARRED SITE: 2
TYPE: PER CELL OBJECT: TOTAL TIME
CELL # MODE
------------------ ---------
543 21 62259 (f333h) 8736 (2220h) DISABLED
2-24 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
3
BSS statistics
BSS statistics are captured from events occurring at the BSS. They are categorized into subgroups,
each of which are described in "BSS statistics subgroups" on page 3-2.
68P02901W56-Q 3-1
24 May 2004 CONTROLLED INTRODUCTION
BSS statistics subgroups Chapter 3: BSS statistics
BSS C7 utilization
BSS C7 utilization statistics track the number of messages received and transmitted on
the signalling links. This information indicates the activity level on the Signalling Links
(SLs). The following are BSS C7 utilization statistics:
• "SIF_SIO_RX_OPC" on page 3-19.
Intra-BSS handover
A single counter array statistic tracks the number of successful intra-BSS handovers:
"INTRA_BSS_HO_CAUSE_SUC" on page 3-6.
SCCP performance and utilization statistics track the performance of the Signalling Connection
Control Part (SCCP) protocol layer of the ITU-TSS C7.
The SCCP manages the establishment and release of call related connections. A connection is
established for each transaction. For example, location update and service request, both BSS and
MSC maintain contexts related to the transaction; these contexts may be identified using the SCCP
reference number. This information indicates the performance level and quality of the SCCP.
The following are the SCCP performance and utilization statistics:
• "HO_REQ_MSC_PROTO" on page 3-5.
3-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application BSS statistics subgroups
{24661}
RSL Congestion Control statistics are PM statistics that track the amount of time a processor was in
a congested state and the count of BSS Overload messages during RSL congestion.
The following are the RSL Congestion Control statistics:
• "BSS_OVLD_MSGS_TX" on page 3-4
68P02901W56-Q 3-3
24 May 2004 CONTROLLED INTRODUCTION
BSS_OVLD_MSGS_TX Chapter 3: BSS statistics
BSS_OVLD_MSGS_TX
{24661}
Description
This statistic tracks the number of BSS Overload messages that have been sent from the BSS
to the MSC. The BSS sends Overload messages to the MSC when the first RSL-LCF board is
congested. The BSS sends this statistic to the OMC-R periodically.
Pegging
This statistic is pegged each time an Overload message is sent from the from the BSS to the MSC..
Analysis
This statistic is used for trend analysis of RSL congestion status on a BSS basis.
3-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application HO_REQ_MSC_PROTO
HO_REQ_MSC_PROTO
Description
This statistic tracks the number of Handover Request messages received from the MSC that fail message
validation. Validation failure may occur due to protocol errors which may occur if the message is
badly formatted or incompatible database elements exist in the BSS and MSC.
Pegging
This statistic is pegged each time a Handover Request message from the MSC fails message
validation at the BSS. Currently, this statistic is not pegged.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of message
validation failures that are acceptable in normal system operations.
If the specified threshold is exceeded, the 17. BSS: HO Request from the MSC protocol
error - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
68P02901W56-Q 3-5
24 May 2004 CONTROLLED INTRODUCTION
INTRA_BSS_HO_CAUSE_SUC Chapter 3: BSS statistics
INTRA_BSS_HO_CAUSE_SUC
Description
This statistic tracks the number of successful intra BSS handovers on a per cause basis. A
total count of all successful results is also maintained.
Pegging
The bin corresponding to the cause of the successful handover is pegged each time a Handover
Performed message is sent from the BSS to the MSC.
{4322} Full-rate to half-rate congestion based Intra-cell handovers cause the CONGESTION bin to be pegged.
{4322} Half-rate quality based Intra-cell handovers cause the DOWNLINK_INTERFERENCE
or UPLINK_INTERFERENCE bins to be pegged.
3-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application INTRA_BSS_HO_CAUSE_SUC
Analysis
This statistic can be used for trend analysis permitting early identification of problems before they affect service.
Reference GSM 12.04, 4.21, B.1.1.11.
GSM 12.04, 8.08, 3.2.1.9, and 3.2.1.25.
Usage Radio resource allocation.
Quality of service monitoring.
Network planning.
Optimization.
Basis BSS.
Type Counter array.
68P02901W56-Q 3-7
24 May 2004 CONTROLLED INTRODUCTION
MA_REQ_FROM_MSC_FAIL Chapter 3: BSS statistics
MA_REQ_FROM_MSC_FAIL
Description
This statistic tracks the number of Assignment Request messages received from the MSC that fail
message validation. Validation failure may occur due to protocol errors which may occur if the message
is badly formatted or incompatible database elements exist in the BSS and MSC.
Pegging
This statistic pegs each time an Assignment Request message from the MSC fails message validation at the BSS.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of
failures that are acceptable in normal system operations.
If the specified threshold is exceeded, the 7. BSS: Mobile assignment request from MSC
protocol error - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling
at the OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 8.08, 3.9.2, 3.2.2.5 and 3.2.1.3.
Usage Radio resource allocation.
Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.
3-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MSC_OVLD_MSGS_RX
MSC_OVLD_MSGS_RX
Description
This statistic tracks the number of MSC Overload messages that have been received by the BSS from the
MSC. This statistic pegs independently of the MSC Overload Control feature being enabled or disabled.
Pegging
This statistic pegs each time an Overload message is received by the BSS from the MSC.
Analysis
In systems without the MSC Overload Control feature, this statistic can be used to determine
if the MSC feature should be acquired, if not currently installed.
Reference GSM-BSS-MOC-EFP-001, v1.1, 2238-7
Usage Quality of service.
Network planning.
Basis BSS.
Type Counter.
68P02901W56-Q 3-9
24 May 2004 CONTROLLED INTRODUCTION
MSGS_DISCARD_ON_GPROC Chapter 3: BSS statistics
MSGS_DISCARD_ON_GPROC
{24661}
Description
This statistic counts the number of downlink messages discarded on each GPROC
by the RSL Congestion Control operation.
Pegging
This statistic is pegged each time a downlink message (including MTL-LCF to RSL-LCF, MCU to
DRI) is discarded on a GPROC by the RSL Congestion Control operation.
Analysis
This statistic is used for trend analysis of RSL congestion status.
3-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MSGS_DISCARD_ON_RSL
MSGS_DISCARD_ON_RSL
{24661}
Description
This statistic counts the number of downlink messages discarded on each RSL by the
RSL Congestion Control operation.
Pegging
This statistic is pegged each time downlink messages are discarded by the RSL
Congestion Control operation on each RSL.
Analysis
This statistic is used for trend analysis of RSL congestion status.
68P02901W56-Q 3-11
24 May 2004 CONTROLLED INTRODUCTION
PAGE_REQ_FROM_MSC_FAIL Chapter 3: BSS statistics
PAGE_REQ_FROM_MSC_FAIL
Description
This statistic tracks the number of Page Request messages received from the MSC that fail message
validation. Validation failure may occur due to protocol errors which may occur if the message is
badly formatted. A protocol error does not indicate paging success or failure.
Pegging
This statistic pegs each time a Page Request message from the MSC fails message validation at the BSS.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number
of failures that are acceptable in normal system operations. The Cell Identifier List is not
verified until the page is about to be sent to the cells.
If the specified threshold is exceeded, the 0. BSS: Paging request from MSC protocol
error - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
3-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application ROUTING_SYNTAX
ROUTING_SYNTAX
Description
This statistic tracks the number of SCCP messages with syntax errors.
Pegging
This statistic pegs when a syntax error is detected in an SCCP message.
Analysis
SCCP is an SS7 protocol used in transferring signalling messages between the BSC and MSC.
Excessive syntax errors can result in degraded SCCP performance. A threshold value should be
assigned to this statistic which reflects the maximum number of SCCP messages with syntax
errors that are acceptable in normal system operations.
If the specified threshold is exceeded, the 1. BSS: Routing failure - syntax error detected
- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
68P02901W56-Q 3-13
24 May 2004 CONTROLLED INTRODUCTION
ROUTING_UNKNOWN Chapter 3: BSS statistics
ROUTING_UNKNOWN
Description
This statistic tracks the number of invalid signalling point codes (SPCs) that a BSC has received from the MSC.
Pegging
This statistic pegs whenever an invalid SPC is received from the MSC.
Analysis
An SPC is the destination address for a message routed by the networking functions of the MTP3
protocol. If the BSC receives an incorrect SPC, it will not be able to correctly route the message.
A threshold value should be assigned to this statistic which reflects the maximum number of
invalid SPCs that are acceptable in normal system operations.
If the specified threshold is exceeded, the 2. BSS: Routing failure - reason unknown
- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
3-14 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application RSL_LCF_CONGESTION
RSL_LCF_CONGESTION
{24661}
Description
This statistic indicates the amount of time that a RSL-LCF board is in a congested state. The
BSS sends this duration statistic to the OMC-R periodically.
Pegging
The timer for this statistic is started when more than a certain percentage of RSLs on a LCF board is
congested, and the timer is stopped when less than a certain percentage of RSLs on a LCF board is congested.
Analysis
This statistic is used for trend analysis of RSL congestion status on a LCF basis.
A threshold value should be assigned to this statistic reflecting the maximum percentage of
congested RSLs on a LCF board at which the timer is started, and the minimum percentage of
congested RSLs on a LCF board at which the timer is stopped.
Whenever this statistic timer is started, the 19:GPROC: RSL links congestion alarm is generated
until the timer stops indicating that normal state has resumed. Refer to the Maintenance Information:
Alarm Handling at the OMC-R (68P02901W26) for troubleshooting information.
68P02901W56-Q 3-15
24 May 2004 CONTROLLED INTRODUCTION
SCCP_MSGS Chapter 3: BSS statistics
SCCP_MSGS
Description
This statistic tracks the total number of SCCP messages either transmitted or received over an SL.
Pegging
This statistic pegs when SCCP messages are transmitted or received on the signalling link.
Analysis
SCCP is an SS7 protocol used in transferring signalling messages between the BSC and MSC. This
statistic can be used for trend analysis of SCCP performance and utilization.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage SCCP performance and utilization.
Basis BSS.
Type Counter.
3-16 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SCCP_MSGS_RX
SCCP_MSGS_RX
Description
This statistic tracks the total number of SCCP messages received on an SL for class 0 or class 2.
Pegging
This statistic pegs when SCCP messages are received on the signalling link.
Analysis
SCCP is an SS7 protocol used in transferring signalling messages between the BSC and MSC.
This statistic can be used for trend analysis of the activity on an SL.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage SCCP performance and utilization.
Basis BSS.
Type Counter.
68P02901W56-Q 3-17
24 May 2004 CONTROLLED INTRODUCTION
SCCP_MSGS_TX Chapter 3: BSS statistics
SCCP_MSGS_TX
Description
This statistic tracks the total number of SCCP messages transmitted on an SL for class 0 or class 2.
Pegging
This statistic pegs when SCCP messages are transmitted on the signalling link.
Analysis
SCCP is an SS7 protocol used in transferring signalling messages between the BSC and MSC.
This statistic can be used for trend analysis of the activity on an SL.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage SCCP performance and utilization.
Basis BSS.
Type Counter.
3-18 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SIF_SIO_RX_OPC
SIF_SIO_RX_OPC
Description
This statistic tracks the total number of SIF and SIO octets received on all SLs for a particular BSS.
Pegging
This statistic pegs each time Signal Information Fields (SIF) or Service Information Octets
(SIO) are received across all signalling links to a BSS.
Analysis
SCCP is an SS7 protocol used in transferring signalling messages between the BSC and MSC. This
statistic can be used for trend analysis of the activity on all SLs for a particular BSS.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 utilization.
Basis BSS.
Type Counter.
68P02901W56-Q 3-19
24 May 2004 CONTROLLED INTRODUCTION
SIF_SIO_TX_DPC Chapter 3: BSS statistics
SIF_SIO_TX_DPC
Description
This statistic tracks the total number of Signal Information Fields (SIF) and Service Information Octets
(SIO) octets transmitted on all SLs of a particular BSS by the Destination Point Code (DPC).
Pegging
This statistic pegs each time SIF or SIO are transmitted across all signalling links to a BSS.
Analysis
A DPC is part of the label in a signalling message that uniquely identifies, in a signalling
network, the destination point of the message. This statistic can be used for trend analysis
of the activity of the signalling links on a BSS.
3-20 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SIF_SIO_TYPE
SIF_SIO_TYPE
Description
This statistic tracks the number of SIF MTP, TEST, and SCCP SIO octets transmitted
or received on an SL on an SIO basis.
Pegging
This statistic pegs each time SIF or SIO octets are transmitted or received on each signalling link.
Analysis
This statistic can be used for trend analysis of the activity of the signalling links on a BSS.
68P02901W56-Q 3-21
24 May 2004 CONTROLLED INTRODUCTION
SIF_SIO_TYPE Chapter 3: BSS statistics
3-22 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
4
Cell statistics
Cell statistics are captured from events occurring in a cell. They are categorized into subgroups,
each of which are described in "Cell statistics subgroups" on page 4-2.
68P02901W56-Q 4-1
24 May 2004 CONTROLLED INTRODUCTION
Cell statistics subgroups Chapter 4: Cell statistics
Assignment redirection
Assignment redirection statistics track the number of times a call assignment is redirected to another cell. The
statistic "ASSIGNMENT_REDIRECTION" on page 4-19 is the only assignment redirection statistic.
Call clearing
Call clearing statistics track the number calls lost due to RF failures, cipher mode failures, or
procedure timeouts. The following are call clearing statistics:
• "CIPHER_MODE_FAIL" on page 4-34.
4-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Cell statistics subgroups
Concentric cell
Concentric cell statistics track concentric cell feature processes. The following are concentric cell statistics:
• "TCH_CONG_INNER_ZONE" on page 4-107.
Connection establishment
Connection establishment statistics track access, allocation, channel request, and MSC page request
functions. The following are connection establishment statistics:
• "ACCESS_PER_AGCH" on page 4-8.
68P02901W56-Q 4-3
24 May 2004 CONTROLLED INTRODUCTION
Cell statistics subgroups Chapter 4: Cell statistics
Directed retry
Directed retry statistics track congestion processes associated with the directed retry
feature. The following are directed retry statistics:
• "CONGEST_EXIST_HO_ATMPT" on page 4-39.
Emergency call access statistics track emergency call processes. The following are
emergency call access statistics:
• "NUM_EMERG_ACCESS" on page 4-78.
Extended range statistics track extended range feature processes. The following
are extended range cell statistics:
• "ER_INTRA_CELL_HO_ATMPT" on page 4-46.
General handover
General handover statistics track processes common to all types of handovers. The
following are handover statistics:
• "BAD_HO_REFNUM_MS" on page 4-22.
4-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Cell statistics subgroups
Inter-BSS handover
Intra-BSS handover
Intra-cell handover
Multiband
Multiband statistics track multiband feature processes. The following are multiband statistics:
• "ASSIGNMENT_REDIRECTION" on page 4-19.
68P02901W56-Q 4-5
24 May 2004 CONTROLLED INTRODUCTION
Cell statistics subgroups Chapter 4: Cell statistics
TCH assignment
TCH assignment statistics track successful, unsuccessful, and total traffic channel assignment
processes. The following are TCH assignment statistics:
• "MA_CMD_TO_MS" on page 4-65.
Usage congestion
Usage congestion statistics track congestion processes not related to the directed retry
feature. The following are usage congestion statistics:
• "AVAILABLE_SDCCH" on page 4-20.
4-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Cell statistics subgroups
DYNET failures
Usage DYNET failures statistics track failures of the DYNET. The following are DYNET failures statistics:
• "DYNET_ASSIGN_FAIL" on page 4-44.
Interference bands
Interference band statistics track the number of idle TCHs per interference band:
• "IDLE_TCH_INTF_BAND0" on page 4-54.
68P02901W56-Q 4-7
24 May 2004 CONTROLLED INTRODUCTION
ACCESS_PER_AGCH Chapter 4: Cell statistics
ACCESS_PER_AGCH
Description
Pegging
This statistic pegs when an Access Grant message is sent on the AGCH to signal the
availability of an allocated channel.
Analysis
This statistic can be used for trend analysis of Intermediate Assignment messages sent on the AGCH of a cell.
4-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application ACCESS_PER_PCH
ACCESS_PER_PCH
Description
The ACCESS_PER_PCH statistic tracks the number of Paging Request messages sent on the air interface.
A paging message could contain up to four pages for paging by TMSI and up to two pages for paging by IMSI.
This statistic is modified to count both Circuit Switched (CS) and Packet Switch
(PS) paging on Page Channel (PCH).
This statistic is obtained by measuring the number of PAGING REQUEST messages sent
on the PCH. This statistic counts the number of attempts.
The bins are:
Pegging
This statistic pegs received requests that:
• Succeeded (resulting in channel assignment).
{23658} This statistic is pegged for both GPRS and EGPRS events.
68P02901W56-Q 4-9
24 May 2004 CONTROLLED INTRODUCTION
ACCESS_PER_PCH Chapter 4: Cell statistics
Analysis
This statistic can be used for trend analysis of Paging Request messages sent on the PCH of a cell.
Reference GSM 4.03, 3.0.3, 4.3.2.1.
GSM 4.08, 3.8.0, 3.3.2.1, 7.1.1 and 9.1.21-23.
GSM 12.04, 3.1.0, B.1.1.10.
Usage Radio resource allocation.
Network planning.
Basis Cell.
Type Counter array.
The ACCESS_PER_PCH statistic pegs a second time if the MS does not answer the
first page. This is because there is no way for the BSS to distinguish between a retry
of a page to one MS and an attempt to page a different mobile.
4-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application ACCESS_PER_PPCH
ACCESS_PER_PPCH
{3723}
Description
The ACCESS_PER_PPCH statistic tracks the number of attempted transmissions of Packet Paging
Request messages sent on the Packet Paging Channel (PPCH).
The bins are:
Bin Description
0 Both CS and PS pages within the PACKET PAGING REQUEST message.
1 Only CS pages within the PACKET PAGING REQUEST message.
2 Only PS pages within the PACKET PAGING REQUEST message.
Pegging
This statistic is obtained by measuring the number of Packet Paging Requests sent on
the PPCH. The number of attempts are counted.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Analysis
This statistic can be used for trend analysis of Packet Paging Request messages sent on the PPCH of a cell.
Reference GSM 4.03, 3.0.3, 4.3.2.1.
GSM 4.08, 3.8.0, 3.3.2.1, 7.1.1 and 9.1.21-23.
GSM 12.04, 3.1.0, B.1.1.10.
Usage Radio resource allocation.
Network planning.
Basis Cell.
Type Counter array statistic.
68P02901W56-Q 4-11
24 May 2004 CONTROLLED INTRODUCTION
ACCESS_PER_PPCH Chapter 4: Cell statistics
The ACCESS_PER_PPCH statistic pegs a second time if the MS does not answer the
first page. This is because there is no way for the BSS to distinguish between a retry
of a page to one MS and an attempt to page a different mobile.
4-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application ACCESS_PER_RACH
ACCESS_PER_RACH
Description
The ACCESS_PER_RACH statistic tracks Channel Request messages received by the BSS on the Random
Access CHannel (RACH) of a cell for Circuit Switched (CS) and Packet Switched (PS) related messages.
A Channel Request message is used by the MS to request allocation of a dedicated channel (to be
used as an SDCCH) by the network, in response to a paging message (incoming call) from the
network or as a result of an outgoing call/supplementary short message service dialled from the
MS. It is also used as part of the call re-establishment procedure.
Pegging
This statistic pegs received requests that:
• Succeeded (resulting in channel assignment).
Analysis
This statistic can be used for trend analysis of Channel Request messages sent on the RACH of a cell.
Reference GSM 4.08, 3.8.0, 3.3.1.1, 3.3.2.2, 4.5.1.6, 5.5.4, 7.1.2, 9.1.8 and
9.2.4.
GSM 4.03, 3.03 and 4.3.2.1.
GSM 12.04, 3.2.0, B.1.1.10.
Usage RF loss.
Congestion.
Quality of service monitoring.
Network planning.
Basis Cell.
Type Counter.
68P02901W56-Q 4-13
24 May 2004 CONTROLLED INTRODUCTION
ALLOC_SDCCH Chapter 4: Cell statistics
ALLOC_SDCCH
Description
The ALLOC_SDCCH statistic is the sum of the number of times a SDCCH is successfully seized. If
a TCH is reconfigured as an SDCCH, only the SDCCH statistics will be configured.
A Channel Request message is used by the MS to request allocation of a dedicated channel (to be
used as an SDCCH) by the network, in response to a paging message (incoming call) from the
network or as a result of an outgoing call/supplementary short message service dialled from the
MS. It is also used as part of the call re-establishment procedure.
SDCCH seizure is caused by immediate assignment, handover, and channel assignment procedures.
Congestion is signalled by the Immediate Assignment Reject or the Assignment/Handover Failure message.
Pegging
This statistic pegs each time an Immediate Assignment message is sent by the BSS. An
Immediate Assignment message will be sent upon:
• Successful handover on an SDCCH channel.
This statistic peg for reasons other than calls requiring a traffic channel, such as location updates.
Analysis
This statistic can be used for trend analysis of SDCCH seizures.
4-14 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application ALLOC_SDCCH
68P02901W56-Q 4-15
24 May 2004 CONTROLLED INTRODUCTION
ALLOC_SDCCH_FAIL Chapter 4: Cell statistics
ALLOC_SDCCH_FAIL
Description
The ALLOC_SDCCH_FAIL statistic tracks the number of times that an attempt at SDCCH
seizure was rejected because of SDCCH congestion.
If a TCH is reconfigured as an SDCCH, only the SDCCH statistics is incremented. Congestion is signalled
by the Immediate Assignment Reject or the Assignment/Handover Failure message.
Pegging
This statistic pegs when an Immediate Assignment Reject message is sent to the MS in response to
a channel request because no SDCCH channels were available to be allocated. It is also pegged in
the target cell when rejecting a handover due to a lack of resources.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of SDCCH
failures due to congestion that are acceptable in normal system operations.
If the specified threshold is exceeded, the 1. CELL: Attempt at allocating an SDCCH
failed - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at
the OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 12.04, 3.1.0, B.1.3.4.
GSM 4.08, 3.8.0, 3.3.1.2.2, 3.4.3.3, 3.4.4.4, 9.1.4, 9.1.16 and 9.1.19.
Usage RF loss.
Congestion.
Quality of service monitoring: Call set-up.
Network planning.
Fault finding.
Optimization.
Ladder: Immediate assignment blocked, Connection establishment.
Key statistic : SDCCH_CONGESTION.
Basis Cell.
Type Counter.
Alarm Major.
4-16 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application ALLOC_TCH
ALLOC_TCH
Description
The ALLOC_TCH statistic tracks the number of successful full rate and half rate TCH
allocations within a cell for both call originations and hand ins.
Pegging
This statistic pegs for successful TCH allocations within a cell as a result of a call
establishment or hand in attempt:
• Successful allocation due to call establishment including successful
allocations due to directed retries.
This statistic pegs before the transmission of the assignment/handover command to the MS and, therefore,
does not take into account the success or failure of the assignment/hand in from an RF perspective.
Analysis
68P02901W56-Q 4-17
24 May 2004 CONTROLLED INTRODUCTION
ALLOC_TCH_FAIL Chapter 4: Cell statistics
ALLOC_TCH_FAIL
Description
The ALLOC_TCH_FAIL statistic tracks the number of unsuccessful full rate and half rate
allocations of a TCH within a cell for both call origination and hand in. Cases involving
Immediate Assignment Reject are also included in the peg count.
Pegging
This statistic pegs when an attempt to allocate a TCH in a cell fails due to a lack of resources:
• Unsuccessful allocation due to call establishment including unsuccessful
allocations due to directed retries.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of TCH
failures due to congestion that are acceptable in normal system operations.
If the specified threshold is exceeded, the 25. CELL: Attempt at allocating an TCH failed
- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
Usage Quality of service: Call set-up.
Fault finding.
Optimization.
Network planning Ladder: Inter-BSS handover, Intra-BSS
handover, Assignment to TCH.
Key statistics: TCH_MEAN_ARRIVAL_RATE.
Basis Cell.
Type Counter.
Alarm Major.
4-18 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application ASSIGNMENT_REDIRECTION
ASSIGNMENT_REDIRECTION
Description
Pegging
This statistic pegs whenever a call assignment is redirected to another cell (SD -> TCH).
Analysis
This statistic can be used for trend analysis of the number of successful internal and external
handovers performed as the result of standard directed retry mechanisms.
68P02901W56-Q 4-19
24 May 2004 CONTROLLED INTRODUCTION
AVAILABLE_SDCCH Chapter 4: Cell statistics
AVAILABLE_SDCCH
Description
Pegging
The statistic pegs whenever there is a change in the channel configuration for any channel in the cell (if
the number of TCHs has not changed, it will be pegged with the same value as before).
This statistic pegs when a change in SDCCH availability is detected.
Analysis
This statistic can be used for trend analysis of SDCCH availability.
By comparing the number of available SDCCHs to the total number of SDCCHs in a system, a
percentage of utilization can be calculated. An analysis of the utilization information can be used to
determine the requirement for additional resources before problems occur.
4-20 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application AVAILABLE_TCH
AVAILABLE_TCH
Description
The AVAILABLE_TCH statistic tracks the mean and max number of available TCHs
that are in use or available for use.
The TCH is available when its administrative state is unlocked or shutting down and its operational state is
enabled. The TCH is unavailable when its administrative state is locked and its operational state is disabled.
This statistic is modified to exclude all PDTCHs, both switchable and reserved unless
the switchable PDTCH is configured as TCH.
This statistic is obtained by maintaining the current and total number of available TCH and the amount of
time each TCH is available over the statistical period. The corresponding mean and maximum number of
TCH available are then computed. The TCH is available when its administrative state is unlocked or
shutting down and the operational state is enabled and is unavailable when the its administrative state
changes to locked or the operational state changes to disabled. The available number of TCH is then
incremented or decremented when there is a change in TCH states as described above.
This statistic only counts those traffic channels, which are configured as TCH at the time of measurement.
Switchable PDTCHs will be included only if they are configured as TCHs.
Pegging
The statistic pegs whenever there is a change in the channel configuration for any channel in the cell (if
the number of TCHs has not changed, it will be pegged with the same value as before).
This statistic pegs when a change in TCH availability is detected.
Analysis
This statistic can be used for trend analysis of TCH availability.
By comparing the number of available TCHs to the total number of TCHs in a system, a percentage
of utilization can be calculated. An analysis of the utilization information can be used to determine
the requirement for additional resources before problems occur.
Reference GSM 12.04, 4.2.1, B.2.1.10
Usage Congestion.
Network planning.
Basis Cell.
Type Gauge.
68P02901W56-Q 4-21
24 May 2004 CONTROLLED INTRODUCTION
BAD_HO_REFNUM_MS Chapter 4: Cell statistics
BAD_HO_REFNUM_MS
Description
The BAD_HO_REFNUM_MS statistic tracks the number of times a MS has accessed a channel
with a Handover Reference Number that the BSS was not expecting.
Pegging
This statistic is pegged once for each time a MS has accessed a channel with a Handover Reference
Number that the BSS was not expecting. This field is an unformatted random number. The BSS
only compares what it received with what it expected, for example, potentially up to four times
for each logical handover detect for the SDCCH processed at the BSS.
The MS will continue to attempt access until a good Handover Reference Number is received,
therefore, the handover can be successful and the statistic will still peg. This statistics pegs if
the handover fails and recovers, or fails and loses the mobile.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of
MS accesses of channels with Handover Reference Numbers that the BSS was not expecting
that are acceptable in normal system operations.
High values reported for this statistic may not be because a handover access meant for one cell can be
detected by another, but the channel at the target cell is susceptible during the time between channel
activation and when the MS actually arrives. This is similar to “Phantom RACHs."
If the specified threshold is exceeded, the 19. CELL: Bad HO reference numbers from the
MS - PM alarm will be generated. Refer to the Maintenance Information: Alarm Handling
at the OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 4.08, 3.8.0, 3.4.4.2.1, 3.4.4.2.2 and 9.1.13.
Usage Handover.
Fault finding.
Basis Cell.
Type Counter.
Alarm Warning.
4-22 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application BUSY_SDCCH
BUSY_SDCCH
Description
The BUSY_SDCCH statistic tracks the number of SDCCHs allocated during an interval.
This is a weighted distribution statistic and will produce a mean value indicating the average
number of SDCCHs in use during the interval.
The bin ranges may be changed using the chg_stat_prop command. The default bin ranges
for the BUSY_SDCCH statistic are shown in Table 4-1.
This statistic is affected by phantom RACHs.
Bin Range
0 0 - 0
1 1 - 2
2 3 - 4
3 5 - 6
4 7 - 8
5 9 - 10
6 11 - 12
7 13 - 14
8 15 - 16
9 17 - 400
Pegging
The individual bin values are incremented by the length of time that the number of allocated SDCCHs fall
within the bin range of values. Bin values are pegged each time a SDCCH is allocated or de-allocated.
If a TCH is reconfigured as an SDCCH, only the SDCCH statistics will be pegged.
68P02901W56-Q 4-23
24 May 2004 CONTROLLED INTRODUCTION
BUSY_SDCCH Chapter 4: Cell statistics
Analysis
This statistic can be used for trend analysis of the amount of RF signalling traffic in the
cell SDCCHs. An analysis of the allocation information can be used to determine the
requirement for additional resources before problems occur.
Reference GSM 12.04, 3.1.0, B.1.3.2.
Usage RF loss.
Congestion.
Quality of service monitoring.
Network planning.
Optimization.
Key statistic: SDCCH_MEAN_HOLDING_TIME, SDCCH
_TRAFFIC_CARRIED.
Basis Cell.
Type Weighted distribution.
4-24 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application BUSY_TCH
BUSY_TCH
Description
The BUSY_TCH statistic tracks the number of full rate and half rate TCHs allocated during an interval.
This is a weighted distribution statistic and produces a mean value indicating the average number of
TCHs in use during the interval. It is an indication of the average capacity for additional traffic in
the cell. This statistic includes TCHs used as a Dedicated Control CHannel (DCCH) in immediate
assignment mode. The BUSY_TCH time includes the guard time (the time allowed between ending
a call and being allowed to start another). Since the channel is not available to be used again
until the guard timer expires, it is not considered to be free until then.
The bin ranges may be changed using the chg_stat_prop command. The default bin ranges
for the BUSY_TCH statistic are shown in Table 4-2.
Bin Range
0 0 - 0
1 1 - 2
2 3 - 4
3 5 - 6
4 7 - 8
5 9 - 10
6 11 - 12
7 13 - 14
8 15 - 16
9 17 - 400
Pegging
The individual bin values are incremented by the length of time that the number of allocated full rate and half
rate TCHs fall within the bin range of values. Bin values peg each time a TCH is allocated or de-allocated.
If a TCH is reconfigured as an SDCCH, only the SDCCH statistics are pegged.
68P02901W56-Q 4-25
24 May 2004 CONTROLLED INTRODUCTION
BUSY_TCH Chapter 4: Cell statistics
Analysis
The value of this statistic is not dependent on the number of transceivers. Rather it is dependent on the
number (however large) of simultaneously busy channels. The only dependence on the number of transceivers
is that the value reported may be larger if more traffic channels are used simultaneously.
This statistic can be used for trend analysis of the amount of RF signalling traffic in the cell
TCHs. An analysis of the allocation information can be used to determine the requirement
for additional resources before problems occur.
Reference GSM 12.04, 3.1.0, B1.1.1. GSM 4.08, 3.8.0, 3.3.1.2.1.
Usage RF loss.
Congestion.
Quality of service monitoring.
Network planning.
Optimization.
Key statistic: TCH_MEAN_HOLDING_TIME,
TCH_TRAFFIC_CARRIED.
Basis Cell.
Type Weighted distribution.
4-26 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application BUSY_TCH_CARR
BUSY_TCH_CARR
Description
The BUSY_TCH_CARR statistic tracks the number of full rate and half rate TCHs allocated during an interval.
This is a gauge statistic and produces a mean value indicating the average number of TCHs in use during the
interval. It is an indication of the average capacity for additional traffic in the cell. This statistic includes TCHs
used as a Dedicated Control CHannel (DCCH) in immediate assignment mode. The BUSY_TCH_CARR time
includes the guard time (the time allowed between ending a call and being allowed to start another). Since the
channel is not available to be used again until the guard timer expires, it is not considered to be free until then.
Pegging
This statistic pegs when a change in the number of full rate and half rate TCHs in use are detected.
Analysis
This statistic can be used for trend analysis of the amount of RF signalling traffic in the cell
TCHs. An analysis of the allocation information can be used to determine the requirement
for additional resources before problems occur.
68P02901W56-Q 4-27
24 May 2004 CONTROLLED INTRODUCTION
CALL_SP_VERS_DOWNGRADE_MONITOR Chapter 4: Cell statistics
CALL_SP_VERS_DOWNGRADE_MONITOR
Description
This statistic tracks the number of call rejects and call downgrades due to not sup-
porting requested speech versions.
{4322} The statistic keeps a count of the number of times that the codec mode was downgraded
for EFR, HR AMR FR AMR and GSM HR calls on a per BSS basis.
{22064} With the Half Rate feature unrestricted, the statistic also keeps a count of the number of times that
the codec mode was downgraded for GSM HR calls on a per BSS basis. The additional bin is as follows:
Pegging
The bin corresponding to the cause of the call downgrade or reject is as indicated in description above.
4-28 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CALL_SP_VERS_DOWNGRADE_MONITOR
Analysis
This statistic can be used for analysis of non-support of requested speech versions.
No alarms are raised by this statistic.
68P02901W56-Q 4-29
24 May 2004 CONTROLLED INTRODUCTION
CALLS_QUEUED Chapter 4: Cell statistics
CALLS_QUEUED
Description
The CALLS_QUEUED statistic tracks the Assignment Requests that are queued during an
interval. If queuing has been allowed and no resources exist, the CRM queues an assignment
request and informs the RRSM with a force queue message.
This statistic does not track handovers.
Pegging
This statistic pegs when queueing is enabled in an assignment request and available queue
blocks are used to queue the call successfully.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of calls
queued for each cell on the BSS that are acceptable in normal system operations.
If the specified threshold is exceeded, the 20. CELL: Number of calls queued - PM alarm
will be generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R
(68P02901W26) for troubleshooting information.
4-30 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CHAN_REQ_CAUSE_ATMPT
CHAN_REQ_CAUSE_ATMPT
Description
The CHAN_REQ_CAUSE_ATMPT statistic tracks the number of Channel Request messages received by
the network from a MS (or LMU) by cause. A total count of all successful results is also tracked.
Pegging
This statistic pegs the cause of each Channel Request message received by the network from a MS.
Analysis
This statistic can be used for trend analysis of the type of Channel Request messages that
are received from MSs. This information can be used to used to determine the requirement
for additional resources before problems occur.
Reference GSM 12.04, 4.21, B.2.1.6.
GSM 4.08, v4.15.0, 9.1.8.
Usage Radio resource allocation.
Quality of service monitoring.
Network planning.
Basis Cell.
Type Counter array.
68P02901W56-Q 4-31
24 May 2004 CONTROLLED INTRODUCTION
CHAN_REQ_MS_BLK Chapter 4: Cell statistics
CHAN_REQ_MS_BLK
Description
The CHAN_REQ_MS_BLK statistic tracks the number of times a MS has been refused access to a channel.
An Immediate Assignment Reject message was sent to the MS on CCCH. This event indicates
that the MS has requested allocation of a dedicated channel, and the network has responded by
refusing immediate access to a channel. Pegging of this counter indicates that there are no channels
available for assignment in the cell. The counter pegs once for each Channel Request Reference in
the message announcing the blocking. The cell is therefore fully used, and it will not be possible
to hand over existing calls into the cell or set up new calls in the cell.
If adjacent cells that are candidates for handover are unable to provide the MS with a radio
resource, it will be impossible for the MS to initiate a call. Handover of calls may be
prevented. This will result in call blocking and loss.
Pegging
This statistic pegs when an Immediate Assignment Reject message is sent to the MS on CCCH thus
indicating that there are no channels available for assignment in the cell.
Analysis
This statistic can be used for trend analysis of the number of times channel access has been denied. This
information can be used to used to determine the requirement for additional resources.
Reference GSM 4.08, 3.8.0, 4.5.1.1,8 and 9.1.27a
Usage Radio resource and allocation.
Fault finding.
Network planning.
Quality of service monitoring : Call setup.
Ladder : Immediate assignment blocked
Basis Cell.
Type Counter.
4-32 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CHAN_REQ_MS_FAIL
CHAN_REQ_MS_FAIL
Description
This statistic is the number of times that the BSS times out waiting for the MS to establish on the SDCCH that
was assigned to it during the immediate assignment procedure (see "CHAN_REQ_MS_FAIL" on page 6-9).
68P02901W56-Q 4-33
24 May 2004 CONTROLLED INTRODUCTION
CIPHER_MODE_FAIL Chapter 4: Cell statistics
CIPHER_MODE_FAIL
Description
The CIPHER_MODE_FAIL statistic pegs when an internal Motorola-defined timer in the BSS expires
to indicate that the MS did not respond to the Cipher Mode Command message with the Cipher Mode
Complete message within the allowable time period or responded improperly. It indicates that the MS
probably did not switch correctly into encrypted communication mode when commanded to do so.
Pegging
This statistic pegs when the MS fails to respond to a Cipher Mode Command from the BSS.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of times that MS
failures to respond to BSS Cipher Mode Command messages are acceptable in normal system operations.
If the specified threshold is exceeded, the 6. CELL: Cipher mode command from MSC
failed - PM alarm will be generated. Refer to the Maintenance Information: Alarm Handling
at the OMC-R (68P02901W26) for troubleshooting information.
4-34 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CLASSMK_UPDATE_FAIL
CLASSMK_UPDATE_FAIL
Description
The CLASSMK_UPDATE_FAIL statistic tracks the number of classmark updates containing errors. The
classmark update procedure allows the MS to inform the network of a change to its classmark.
Pegging
This statistic pegs when the validation of the Classmark Update message from the MS fails.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of classmark
updates containing errors that are acceptable in normal system operations.
If the specified threshold is exceeded, the 4. CELL: Class-mark update from MS protocol
error - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 4.08, 3.8.0,8 and 10.5.1.5-6.
GSM 8.08, 3.9.2, 3.1.13 and 3.2.1.29.
Usage Classmark update and cipher mode.
Quality of service monitoring.
Fault finding.
Basis Cell.
Type Counter.
Alarm Minor.
68P02901W56-Q 4-35
24 May 2004 CONTROLLED INTRODUCTION
CLR_CMD_FROM_MSC Chapter 4: Cell statistics
CLR_CMD_FROM_MSC
Description
The CLR_CMD_FROM_MSC statistic separately tracks the number of Clear commands received from
the MSC for SDCCH and TCH resources thereby allowing the analysis of dropped calls.
Pegging
This statistic pegs when a Clear command is received from the MSC.
Analysis
This statistic can be used for trend analysis of the number of Clear commands received from the MSC.
This information can be used to identify and correct problems before they become serious.
Reference GSM 4.08, 3.8.0, 5.4.3. GSM 8.08, 3.9.2, 3.2.1.20. and 3.1.9.2.
Usage Radio resource allocation.
Quality of service monitoring.
Fault finding.
Network planning.
Basis Cell.
Type Counter array.
4-36 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CLR_REQ_TO_MSC
CLR_REQ_TO_MSC
Description
The CLR_REQ_TO_MSC statistic separately tracks the number of Clear Request messages
sent to the MSC for SDCCH and TCH resources.
Generating
The Clear Request message may be generated due to one of the following:
• No radio resources available to allocate from the BSS, call queuing is enabled,
and the maximum call delay has been exceeded.
• Protocol error.
Sending
All Clear Requests are sent per GSM 8.08 specifications. The Clear Request messages are sent to the
MSC because of radio channel failure or a timeout during a procedure. In this case a timeout means
a required message was not received during a procedure. The procedures are:
• Immediate Assignment.
• Assignment.
• Ciphering.
Pegging
This statistic pegs when the BSS sends a Clear Request message to the MSC. CLR_REQ_TO_MSC
is pegged for numerous reasons related to timer expiry. It is a mix of both GSM and internal Motorola
timers. Normal release of a call either from a MS or Land site never cause it to be pegged. A call
must have at least been assigned to an SDCCH or TCH in order for this to be pegged. It is not
pegged when on an AGCH overload. RF loss is the major cause of pegging.
68P02901W56-Q 4-37
24 May 2004 CONTROLLED INTRODUCTION
CLR_REQ_TO_MSC Chapter 4: Cell statistics
Analysis
This statistic can be used for trend analysis of the number of Clear Request messages sent to the MSC.
This information can be used to identify and correct problems before they become serious.
Reference GSM 4.08, 3.8.0, 5.4.3. GSM 8.08, 3.9.2, 3.2.1.20. and 3.1.9.2.
Usage Radio resource allocation.
Quality of service monitoring.
Fault finding.
Network planning.
Ladder : BSS initiated call clearing, handover (Intra-cell) fail/lost,
handover (Intra-BSS) fail/lost.
4-38 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CONGEST_EXIST_HO_ATMPT
CONGEST_EXIST_HO_ATMPT
Description
The CONGEST_EXIST_HO_ATMPT statistic tracks the number of attempted inter-cell handovers (internal
or external to the BSS) of calls on a TCH due to TCH congestion from the source cell.
Pegging
This statistic pegs each time a congestion relief handover is attempted. This statistic is
pegged for both internal inter-cell and external handovers.
Analysis
This statistic can be used for trend analysis of the number of internal and external handovers
attempts due to TCH congestion from source cells.
Reference GSM 8.08, 4.90.
GSM 3.09, 4.50.
GSM 4.08, 4.11.0.
Usage Optimization.
Network planning.
Basis Cell.
Type Counter.
68P02901W56-Q 4-39
24 May 2004 CONTROLLED INTRODUCTION
CONGEST_STAND_HO_ATMPT Chapter 4: Cell statistics
CONGEST_STAND_HO_ATMPT
Description
Pegging
This statistic pegs each time a Directed Retry handover procedure is attempted for
both inter-cell and external handovers.
Analysis
This statistic can be used for trend analysis of the number of attempted internal or external handovers
due to standard Directed Retry mechanisms caused by TCH congestion.
Reference GSM 8.08, 4.90.
GSM 3.09, 4.50.
GSM 4.08, 4.11.0.
Usage Optimization.
Network planning.
Basis Cell.
Type Counter.
4-40 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CONN_REFUSED
CONN_REFUSED
Description
Pegging
This statistic pegs when the MSC sends the BSS an SCCP Connection Refused (CREF) message.
The MSC may send an SCCP Connection Refused message in response to a BSS generated
SCCP Connection Request (CR) message, as a result of
• MS access for a location update.
• SMS activity.
• IMSI detach.
• Call re-establishment.
For example, if an association already exists for the identity of the MS requesting a connection,
the connection request is refused, and this statistic pegs.
Analyse MSC statistics to determine why the CONN_REFUSED statistic is pegged.
Some MSCs may generate a Connection Refused Message during a successful IMSI Detach
rather than a Connection Confirm, so a high value for the CONN_REFUSED statistic may
not indicate a system problem. The MSC performance during IMSI Detach procedures
should be investigated before interpreting the CONN_REFUSED statistic.
68P02901W56-Q 4-41
24 May 2004 CONTROLLED INTRODUCTION
CONN_REFUSED Chapter 4: Cell statistics
Analysis
This statistic can be used for trend analysis of the reasons for connections refused
from the MSC. This is an MSC procedure.
4-42 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CONN_REQ_TO_MSC
CONN_REQ_TO_MSC
Description
The CONN_REQ_TO_MSC statistic tracks the number of connection requests that the BSS sends to the MSC.
Pegging
The statistic pegs only for connection establishments initiated by the BSS. This message is sent by
the MS when it is requesting set-up of the connections for several types of transactions, including
location updates, connection establishments (including re-establishment on failure, short message
transfer, and supplementary service requests), and paging responses.
Analysis
This statistic can be used for trend analysis of the number of connection requests sent from the BSS to the MSC.
68P02901W56-Q 4-43
24 May 2004 CONTROLLED INTRODUCTION
DYNET_ASSIGN_FAIL Chapter 4: Cell statistics
DYNET_ASSIGN_FAIL
Description
The DYNET_ASSIGN_FAIL statistic tracks the number of times assignments have failed due to
insufficient terrestrial backhaul resources on a BTS Dynamic Allocation Network.
Pegging
This statistic pegs each time an assignment procedure fails due to the lack of terrestrial backing resources.
Usage Quality of service monitoring.
Radio resource allocation.
Network planning.
Basis BSS.
Type Counter.
Alarm None.
4-44 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DYNET_CALL_REJECTS
DYNET_CALL_REJECTS
Description
The DYNET_CALL_REJECTS statistic tracks the number of times calls have been blocked or preempted
due to insufficient terrestrial backhaul resources on a BTS Dynamic Allocation Network.
Pegging
The appropriate bin is incremented when specific calls are rejected or preempted.
Usage Quality of service monitoring.
Networking planning.
Radio resource allocation.
Basis DYNET.
Type Counter array.
Alarm None.
68P02901W56-Q 4-45
24 May 2004 CONTROLLED INTRODUCTION
ER_INTRA_CELL_HO_ATMPT Chapter 4: Cell statistics
ER_INTRA_CELL_HO_ATMPT
Description
Pegging
This statistic pegs each time a handover is attempted between a normal channel and an
extended channel in an extended range cell.
Analysis
This statistic can be used for trend analysis of the attempted intra-cell handovers between normal and extended
range channels in an extended range cell. The number of attempted extended range intra-cell handovers can
be used to determine the number of extended range timeslots to configure in an extended range cell.
Reference None.
Usage Quality of service.
Network planning.
Radio resource allocation.
Basis Cell.
Type Counter array.
4-46 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application ER_INTRA_CELL_HO_SUC
ER_INTRA_CELL_HO_SUC
Description
Pegging
This statistic pegs each time a handover is successful between a normal channel and an extended
channel in an extended range cell. No other intra_cell handover statistic is pegged when one of
the bins of the ER_INTRA_CELL_HO_SUC statistic is pegged.
Analysis
This statistic can be used for trend analysis of the successful intra-cell handovers between normal and extended
range channels in an extended range cell. The number of successful extended range intra-cell handovers can
be used to determine the number of extended range timeslots to configure in an extended range cell.
Reference None.
Usage Quality of service.
Network planning.
Radio resource allocation.
Basis Cell.
Type Counter array.
68P02901W56-Q 4-47
24 May 2004 CONTROLLED INTRODUCTION
FLOW_CONTROL_BARRED Chapter 4: Cell statistics
FLOW_CONTROL_BARRED
Description
The FLOW_CONTROL_BARRED statistic tracks the duration for which access classes are barred as a result
of flow control. This statistic gives an indication when flow control actions have been taken to prevent overload.
Pegging
The statistic duration is started when any of the access classes are barred due to flow control and stopped
when the last access class which was barred due to flow control is unbarred.
Analysis
This statistic can be used for trend analysis of the access classes barred as a result of flow control.
Usage Quality of Service.
Network Planning.
Optimization.
Basis Cell.
Type Duration (total time in milliseconds).
4-48 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application HO_FAIL_NO_RESOURCES
HO_FAIL_NO_RESOURCES
Description
The HO_FAIL_NO_RESOURCES tracks the number of handover failures due to a lack of available resources.
Pegging
These individual bins are incremented on a per scenario basis.
68P02901W56-Q 4-49
24 May 2004 CONTROLLED INTRODUCTION
HO_FAIL_NO_RESOURCES Chapter 4: Cell statistics
Analysis
This statistic can be used for trend analysis of the handover failures due to a lack of resources, such as:
• The target cell is barred for some reason, such as hardware failure.
• The speech algorithm at the target BSS is not supported by the MS.
• An SCCP connection is not allocated, that is CRM runs out of SCCP numbers.
Reference Metrica.
Usage Radio resource allocation.
Quality of service monitoring.
Network planning.
Basis Cell.
Type Counter array.
4-50 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application HO_REQ_MSC_FAIL
HO_REQ_MSC_FAIL
Description
The HO_REQ_MSC_FAIL statistic tracks the number of handover request failure messages sent to the
MSC, except for no channel resources available. This message is sent to notify the MSC that the BSS
could not reserve the radio resource that the MSC requested in the Handover Request message.
Pegging
This statistic pegs in the source or target cell depending on where the failure occurs.
This statistic pegs in the source cell if the handover failure originates from the MS. This
indicates that the MS has reverted back to its original channel.
This statistic pegs in the target cell if the handover failure message originates from the target cell.
This could indicate one of the following problems: terrestrial circuit unavailable, terrestrial circuit
in use, ciphering algorithm not supported, or radio resources unavailable.
This statistic is not pegged if resources are not available in the target cell.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of handover failures
for any reason other than lack of channel resources that are acceptable in normal system operations.
If the specified threshold is exceeded, the 18. CELL: HO failure to the MSC due to all possible
errors except no channels - PM alarm is generated. Refer to the Maintenance Information: Alarm
Handling at the OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 8.08, 3.9.2, 3.1.5.3.2, 3.2.1.8 and 3.2.1.16.
Usage Handover.
Fault finding.
Ladder: Handover (Inter-BSS) blocked.
Basis Cell.
Type Counter.
Alarm Warning.
68P02901W56-Q 4-51
24 May 2004 CONTROLLED INTRODUCTION
HO_REQ_ACK_TO_MSC Chapter 4: Cell statistics
HO_REQ_ACK_TO_MSC
Description
The HO_REQ_ACK_TO_MSC statistic tracks the number of handover request acknowledge messages sent
to the MSC for each channel type and speech version by the destination cell in an inter-BSS (external) handover.
{22064} When the Half Rate feature is unrestricted, the HO_REQ_ACK_TO_MSC bin
table introduces bin procedure PM_GSM_HR as shown:
4-52 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application HO_REQ_ACK_TO_MSC
Pegging
This statistic pegs for each channel type and speech version when the BSS sends a Handover Request
Acknowledge message to the MSC. This message is sent to notify the MSC that the BSS has reserved
the radio resource that the MSC asked for in the Handover Request message.
Analysis
This statistic can be used for trend analysis of successful radio resource reservations per channel type
and speech version by the BSS in response to MSC Handover Request messages.
68P02901W56-Q 4-53
24 May 2004 CONTROLLED INTRODUCTION
IDLE_TCH_INTF_BAND0 Chapter 4: Cell statistics
IDLE_TCH_INTF_BAND0
Description
The IDLE_TCH_INTF_BAND0 statistic tracks the maximum and mean number of idle traffic
channels (TCHs) for interference band 0. An idle TCH falls into band 0 if its average interference
band is less than the value of the element interfer_bands, 0.
Idle TCHs are allocated to five interference bands. Each band has an associated
statistic for tracking idle TCHs.
Pegging
This statistic is reported periodically using the rf_res_ind_period element.
Analysis
This statistic can be used for trend analysis of idle traffic channels.
Reference GSM 12.04, 4.2.1, B.2.1.13.
Usage Service integrity.
Fault finding.
Basis Cell.
Type Gauge.
4-54 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application IDLE_TCH_INTF_BAND1
IDLE_TCH_INTF_BAND1
Description
The IDLE_TCH_INTF_BAND1 statistic tracks the maximum and mean number of idle traffic
channels (TCHs) for interference band 1. An idle TCH falls into band 1 if its average interference
band is less than the value of the element interfer_bands, 1.
Idle TCHs are allocated to five interference bands. Each band has an associated
statistic for tracking idle TCHs.
Pegging
This statistic is reported periodically using the rf_res_ind_period element.
Analysis
This statistic can be used for trend analysis of idle traffic channels.
Reference GSM 12.04, 4.2.1, B.2.1.13.
Usage Service integrity.
Fault finding.
Basis Cell.
Type Gauge.
68P02901W56-Q 4-55
24 May 2004 CONTROLLED INTRODUCTION
IDLE_TCH_INTF_BAND2 Chapter 4: Cell statistics
IDLE_TCH_INTF_BAND2
Description
The IDLE_TCH_INTF_BAND2 statistic tracks the maximum and mean number of idle traffic
channels (TCHs) for interference band 2. An idle TCH falls into band 2 if its average interference
band is less than the value of the element interfer_bands, 2.
Idle TCHs are allocated to five interference bands. Each band has an associated
statistic for tracking idle TCHs.
Pegging
This statistic is reported periodically using the rf_res_ind_period element.
Analysis
This statistic can be used for trend analysis of idle traffic channels.
Reference GSM 12.04, 4.2.1, B.2.1.13.
Usage Service integrity.
Fault finding.
Basis Cell.
Type Gauge.
4-56 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application IDLE_TCH_INTF_BAND3
IDLE_TCH_INTF_BAND3
Description
The IDLE_TCH_INTF_BAND3 statistic tracks the maximum and mean number of idle traffic
channels (TCHs) for interference band 3. An idle TCH falls into band 3 if its average interference
band is less than the value of the element interfer_bands, 3.
Idle TCHs are allocated to five interference bands. Each band has an associated
statistic for tracking idle TCHs.
Pegging
This statistic is reported periodically using the rf_res_ind_period element.
Analysis
This statistic can be used for trend analysis of idle traffic channels.
Reference GSM 12.04, 4.2.1, B.2.1.13.
Usage Service integrity.
Fault finding.
Basis Cell.
Type Gauge.
68P02901W56-Q 4-57
24 May 2004 CONTROLLED INTRODUCTION
IDLE_TCH_INTF_BAND4 Chapter 4: Cell statistics
IDLE_TCH_INTF_BAND4
Description
The IDLE_TCH_INTF_BAND4 statistic tracks the maximum and mean number of idle traffic
channels (TCHs) for interference band 4. An idle TCH falls into band 4 if its average interference
band is less than the value of the element interfer_bands, 4.
Idle TCHs are allocated to five interference bands. Each band has an associated
statistic for tracking idle TCHs.
Pegging
This statistic is reported periodically using the rf_res_ind_period element.
Analysis
This statistic can be used for trend analysis of idle traffic channels.
Reference GSM 12.04, 4.2.1, B.2.1.13.
Usage Service integrity.
Fault finding.
Basis Cell.
Type Gauge.
4-58 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application IN_INTER_BSS_HO
IN_INTER_BSS_HO
Description
The IN_INTER_BSS_HO statistic tracks incoming inter-BSS handover procedures on a per scenario
basis. A total value for this statistic is not meaningful and is not displayed.
Pegging
These individual bins are incremented on a per cause basis.
Analysis
This statistic can be used for trend analysis of incoming inter-BSS handover procedures on a per scenario basis.
Reference Metrica, GSM 12.04, 3.1.0, B.1.1.7.
Usage Radio resource allocation.
Quality of service monitoring.
Network planning.
Fault finding.
Handover.
Basis Cell.
Type Counter array.
68P02901W56-Q 4-59
24 May 2004 CONTROLLED INTRODUCTION
IN_INTRA_BSS_HO Chapter 4: Cell statistics
IN_INTRA_BSS_HO
Description
The IN_INTRA_BSS_HO statistic tracks incoming intra-BSS handover procedures on a per scenario
basis. A total value for this statistic is not meaningful and is not displayed.
Pegging
These individual bins are incremented on a per scenario basis.
Analysis
This statistic can be used for trend analysis of incoming intra-BSS handover procedures on a per scenario basis.
Reference Metrica.
GSM 8.08, 3.9.2, 3.1.7, 3.1.5.2.1, 3.2.1.12.
Usage Radio resource allocation.
Quality of service monitoring.
Network planning.
Service retainability.
Fault finding.
Handover.
Basis Cell.
Type Counter array.
4-60 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application INTERBAND_ACTIVITY
INTERBAND_ACTIVITY
Description
The INTERBAND_ACTIVITY statistic tracks inter-band handover attempts in the BSS. Assignment
and handover failures due to incorrect or unsupported frequency information are also tracked. The
Multiband option must be enabled for this statistic to be enabled, disabled, or displayed.
Pegging
This individual bins are incremented on a per cause basis. For inter-band handovers, the
bin of the destination frequency is pegged.
Analysis
This statistic can be used for trend analysis of inter-band handover attempts in the BSS on a per cause basis.
Reference None.
Usage Handover.
Quality of service monitoring.
Network planning.
Service retainability.
Basis Cell.
Type Counter array.
68P02901W56-Q 4-61
24 May 2004 CONTROLLED INTRODUCTION
INTRA_CELL_HO Chapter 4: Cell statistics
INTRA_CELL_HO
Description
A total value for this statistic is not meaningful and is not displayed.
4-62 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application INTRA_CELL_HO
Pegging
INTRA_CELL_HO_REQ is pegged just before sending the intra-cell handover message.
INTRA_CELL_HO_ATMPT_XX_XX replaces INTRA_CELL_HO_ATMPT below.
{4322} INTRA_CELL_HO_ATMPT_XX_XX is pegged after the channel activation message is
received and just before the assignment command is sent to the MS.
INTRA_CELL_HO_SUC is pegged each time a handover performed message is sent to the MS.
INTRA_CELL_HO_LOSTMS is pegged when a radio channel released message is received.
INTRA_CELL_HO_RETURN is pegged when a revert to old channel message is received.
INTRA_CELL_EQUIP_FAIL is pegged when an assignment failure message contains an
equipment failure cause or KSW/highway fault.
INTRA_CELL_HO_CLEARED is pegged every time a call is cleared down during an intra-cell handover.
Analysis
This statistic can be used for trend analysis of intra-cell handovers on a per scenario basis.
Reference Metrica.
GSM 12.04, 3.1.0, B.1.1.6.
GSM 8.08, 3.9.2, 3.1.6, 3.2.1.25.
GSM 4.08, 3.8.0, 9.1.3.
Usage Radio resource allocation.
Quality of service monitoring.
Network planning.
Fault finding.
Service retainability.
Basis Cell.
Type Counter array.
68P02901W56-Q 4-63
24 May 2004 CONTROLLED INTRODUCTION
INV_EST_CAUSE_ON_RACH Chapter 4: Cell statistics
INV_EST_CAUSE_ON_RACH
Description
The INV_EST_CAUSE statistic tracks the number of RACHs with invalid establishment cause.
This helps to account more fully for occurrences of Phantom RACHs.
Pegging
This statistic pegs when the establishment cause is not validated.
It is possible for invalid Channel Requests not to be pegged by this statistic because the Channel Requests
are precisely formatted to prevent being caught by all the validation routines (channel coder, RSS Layer 1,
RSS Abis). These invalid Channel Requests that are not pegged are due to phantom RACHs.
Analysis
This statistic can be used for trend analysis of RACHs with invalid establishment causes.
Reference GSM 4.08, 3.8.0, 3.3.1.1, 3.3.2.2, 4.5.1.6, 5.5.4, 7.1.2, 9.1.8, and
9.2.4.
GSM 4.03, 3.03, and 4.3.2.1.
Usage Handover.
Quality of service monitoring.
Fault finding.
Ladder: Immediate Assignment Failure.
Basis Cell.
Type Counter.
4-64 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MA_CMD_TO_MS
MA_CMD_TO_MS
Description
The MA_CMD_TO_MS statistic tracks the number of Assignment Commands sent to the MS.
Pegging
This statistic pegs when the BSS initiates the channel assignment procedure by sending an Assignment
Command to the MS on the main SDCCH. Assignment Command is sent to the MS at call setup
(traffic channel assignment) and at intra-cell handovers. This causes the MS to:
• Release its link layer connections.
Analysis
This statistic can be used for trend analysis of BSS initiated channel assignment procedures to the MS.
Reference GSM 4.08, 3.8.0, 3.4.3.1 and 9.1.2.
Usage Radio resource allocation.
Call setup.
Ladder: TCH assignment successful, TCH assignment
fail-recovered to SDCCH, handover (Intra-cell) successful,
handover (Intra-cell) fail-recovered, handover (Intra-cell) fail-lost.
Basis Cell.
Type Counter.
68P02901W56-Q 4-65
24 May 2004 CONTROLLED INTRODUCTION
MA_COMPLETE_FROM_MS Chapter 4: Cell statistics
MA_COMPLETE_FROM_MS
Description
Pegging
This statistic pegs when the BSS receives an Assignment Complete message from the MS.
Analysis
This statistic can be used for trend analysis.
4-66 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MA_COMPLETE_TO_MSC
MA_COMPLETE_TO_MSC
Description
{22064} When the Half Rate feature is unrestricted, the MA_COMPLETE_TO_MSC bin
table introduces bin procedure PM_GSM_HR as shown:
Pegging
This statistic pegs when the Assignment Complete message from the MS is forwarded on to the MSC.
68P02901W56-Q 4-67
24 May 2004 CONTROLLED INTRODUCTION
MA_COMPLETE_TO_MSC Chapter 4: Cell statistics
Analysis
{4322} This statistic can be used for trend analysis of successful assignment completions
per channel type and speech version.
4-68 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MA_FAIL_FROM_MS
MA_FAIL_FROM_MS
Description
Pegging
This statistic pegs when the BSS receives an Assignment Failure message from the MS. If the MS detects a
lower layer failure on the new channels before the Assignment Complete message has been sent:
• It deactivates the new channels.
• It then sends the Assignment Failure message on the main DCCH. This statistic
pegs for channel assignment failures at intra-cell handovers for new calls and
channel assignment failures at handover.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of
assignment failures for MSs that are acceptable in normal system operations.
If the specified threshold is exceeded, the 23. CELL: Mobile assignment failure from MS
- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
68P02901W56-Q 4-69
24 May 2004 CONTROLLED INTRODUCTION
MA_REQ_FROM_MSC Chapter 4: Cell statistics
MA_REQ_FROM_MSC
Description
The MA_REQ_FROM_MSC statistic tracks the number of times the MSC asked the BSS to
allocate radio resources. The MSC sends the BSS an Assignment request message containing
details of the type of resource required. The type of resource is based on the MSC analysis
of the call control information received from the MS.
{4322} The bins are:
When the Half Rate feature is unrestricted, the MA_REQ_FROM_MSC bin table
introduces bin procedure PM_GSM_HR as shown:
Pegging
This statistic pegs the radio resource request for each preferred speech version made to a BSS by the MSC.
4-70 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MA_REQ_FROM_MSC
Analysis
This statistic can be used for trend analysis of MSC request to the BSS to allocate radio resources.
Reference GSM 8.08, 3.9.2, 3.1.1.1 and 3.2.1.1.
Usage Radio resource allocation.
Quality of service monitoring: Call setup.
Network planning.
Ladder: TCH assignment successful, TCH assignment
fail-recovered to SDCCH, TCH assignment blocked.
Basis Cell.
Type Counter array statistic.
68P02901W56-Q 4-71
24 May 2004 CONTROLLED INTRODUCTION
MA_CMD_TO_MS_BLKD Chapter 4: Cell statistics
MA_CMD_TO_MS_BLKD
Description
The MA_CMD_TO_MS_BLKD statistic tracks the number of times an assignment request from the
MSC could not be processed (assignment command could not be generated and sent to the mobile
station) as there were no traffic channels available at the cell due to congestion.
Pegging
This statistic is pegged by the BSS when the MSC requests the BSS to allocate radio resource
to an MS, and the BSS finds it has no channels available to allocate. The pegging of this
statistic indicates no channels were available in the currently allocated cell. It is indicated by an
Assignment Failure message with cause: No radio resource available.
If queueing is enabled the statistic is pegged when the BSS queueing related timer bss_t11 expires. If the BSS
assignment_successful timer is set shorter than the BSS bssmap_t11 timer then this statistic will not be pegged.
It is recommended that the assignment_successful timer be always set greater than the bssmap_t11 timer.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of times traffic
channels that may be congested due to a lack of radio resources that are acceptable in normal system operations.
If the specified threshold is exceeded, the 2. CELL: Mobile assign command to MS blocked
(no channel available) - PM alarm is generated. Refer to the Maintenance Information: Alarm
Handling at the OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 8.08, 3.9.2, 3.2.1.3 and 3.2.2.5.
Usage Radio resource allocation.
Quality of service monitoring: Call setup and handover.
Fault finding.
Network planning.
Optimization.
Ladder: TCH assignment blocked.
Basis Cell.
Type Counter.
Alarm Minor.
4-72 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MS_ACCESS_BY_TYPE
MS_ACCESS_BY_TYPE
Description
The MS_ACCESS_BY_TYPE statistic tracks the number of system accesses by the various types
of MSs. The type of MS is included in the MS Classmark 3 information.
This statistic may be enabled only if the Multiband feature is unrestricted and enabled for the cell.
Pegging
The MS_ACCESS_BY_TYPE statistic is pegged by RRSM after the sending of the initial layer
3 information by the MS, on receipt of the classmark of the MS. It can also be pegged if the MS
sends a CLASSMARK CHANGE message whilst in dedicated mode.
Analysis
This statistic can be used for trend analysis of system accesses by MS type.
Usage Quality of Service monitoring.
Network planning.
Basis Cell.
Type Counter array.
68P02901W56-Q 4-73
24 May 2004 CONTROLLED INTRODUCTION
MS_TCH_USAGE_BY_TYPE Chapter 4: Cell statistics
MS_TCH_USAGE_BY_TYPE
Description
The MS_TCH_USAGE_BY_TYPE statistic tracks the length of time spent on TCHs by the
various types of MSs. Duration is measured in deciminutes. (One deciminute equals six seconds.
For example, if MS_TCH_USAGE_BY_TYPE = 31, the call duration was 3.1 minutes or 186
seconds). The type of MS is included in the MS Classmark 3 information.
This statistic may only be enabled if the Multiband feature is unrestricted and enabled for the cell.
Pegging
Each bin is updated by the cell resource manager when the duration for an active channel is recorded. A total
duration is calculated which is the sum for all channels usage time by MSs in a given cell.
Analysis
This statistic can be used for trend analysis of active channel usage. This information can be
used to identify problems before they can affect service.
Usage Service accessibility.
Network planning.
Basis Cell.
Type Counter array.
4-74 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MS_TCH_USAGE_BY_TYPE_PCS
MS_TCH_USAGE_BY_TYPE_PCS
Description
The MS_TCH_USAGE_BY_TYPE_PCS statistic tracks the length of time spent on TCHs by the
various types of MSs. Duration is measured in deciminutes. (One deciminute equals six seconds.
For example, if MS_TCH_USAGE_BY_TYPE_PCS = 31, the call duration was 3.1 minutes or 186
seconds). The type of MS is included in the MS Classmark 3 information.
This statistic may only be enabled if either the PCS1900 or GSM850 frequency band is allowed
on the BSS and the Multiband feature is unrestricted and enabled for the cell.
Bin Description
0 GSM850 only capable mobiles.
1 DCS1800-PCS1900 capable mobiles.
2 PGSM-DCS1800-PCS1900 capable mobiles.
3 PGSM-EGSM-DCS1800-PCS1900 capable mobiles.
4 PGSM-GSM850 capable mobiles.
5 PGSM-EGSM-GSM850 capable mobiles.
6 GSM850-DCS1800 capable mobiles.
7 PGSM-GSM850-DCS1800 capable mobiles.
8 PGSM-EGSM-GSM850-DCS1800 capable mobiles.
9 GSM850-PCS1900 capable mobiles.
10 PGSM-GSM850-PCS1900 capable mobiles.
11 PGSM-EGSM-GSM850-PCS1900 capable mobiles.
12 GSM850-PCS1900-DCS1800 capable mobiles.
13 PGSM-GSM850-PCS1900-DCS1800 capable mobiles.
14 PGSM-EGSM-GSM850-PCS1900-DCS1800 capable mobiles.
Pegging
Each bin is updated by the cell resource manager when the duration for an active channel is recorded. A total
duration is calculated which is the sum for all channels usage time by MSs in a given cell.
68P02901W56-Q 4-75
24 May 2004 CONTROLLED INTRODUCTION
MS_TCH_USAGE_BY_TYPE_PCS Chapter 4: Cell statistics
Analysis
This statistic can be used for trend analysis of active channel usage. This information can be
used to identify problems before they can affect service.
Usage Service accessibility.
Network planning.
Basis Cell.
Type Counter array.
4-76 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MT_LCS_ON_SDCCH
MT_LCS_ON_SDCCH
Description
This statistic counts the number of mobile-terminated SDCCH sessions for Location Services.
The statistic has been introduced to allow the Call Setup Success Rate key statistic (see Chapter
17) to work following the introduction of the Location Services feature.
Pegging
This statistic is pegged each time there is an MT LMU on an SDCCH.
It is also pegged for a MT call when any LCS transaction occurs while the MS is on an SDCCH.
Any of the following messages received over the A-interface are considered LCS transaction
initiations: BSSLAP TA Request, BSSLAP MS Position Command, BSSMAP Perform Location
Request (only applies in the case of a BSS based SMLC).
68P02901W56-Q 4-77
24 May 2004 CONTROLLED INTRODUCTION
NUM_EMERG_ACCESS Chapter 4: Cell statistics
NUM_EMERG_ACCESS
Description
The NUM_EMERG_ACCESS statistic tracks the number of emergency calls that access the system.
Pegging
This statistic pegs after the receipt of an emergency RACH.
Analysis
This statistic can be used for trend analysis of emergency call accesses.
Usage Quality of Service monitoring.
Network planning.
Basis Cell.
Type Counter.
4-78 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application NUM_EMERG_REJECTED
NUM_EMERG_REJECTED
Description
Pegging
This statistic pegs the number of emergency calls that are rejected because all channels were
occupied by other emergency or high priority calls.
Analysis
This statistic can be used for trend analysis of emergency call accesses that failed because all
channels were occupied by other emergency or high priority calls.
Usage Quality of Service.
Network planning.
Basis Cell.
Type Counter.
68P02901W56-Q 4-79
24 May 2004 CONTROLLED INTRODUCTION
NUM_EMERG_TCH_KILL Chapter 4: Cell statistics
NUM_EMERG_TCH_KILL
Description
The NUM_EMERG_TCH_KILL statistic tracks the number of times a call is lost due to emergency
call pre-emption and not to other factors, such as RF losses.
The active channel with the lowest priority is the one that releases a TCH. Additionally,
emergency calls are not pre-empted by other emergency calls.
Pegging
This statistic pegs the number of active calls that are terminated in order to make a TCH available for
an emergency call. This situation arises if all TCHs are occupied and an emergency access requires a
channel. This statistic pegs only if the emergency pre-emption feature is enabled.
Analysis
This statistic can be used for trend analysis of the number of times that calls are lost
due to emergency call pre-emption only.
Usage Quality of Service.
Network planning.
Basis Cell
Type Counter.
4-80 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application NUM_EMERG_TERM_SDCCH
NUM_EMERG_TERM_SDCCH
Description
Pegging
This statistic pegs each time an emergency call is assigned to an SDCCH but must be terminated
because no TCHs are available to complete the call. This statistic is pegged regardless of
the status of the emergency preemption feature.
Analysis
This statistic can be used for trend analysis of the number of times that emergency
accesses are terminated after SDCCH congestion.
Usage Quality of Service.
Network planning.
Basis Cell.
Type Counter.
68P02901W56-Q 4-81
24 May 2004 CONTROLLED INTRODUCTION
OK_ACC_PROC Chapter 4: Cell statistics
OK_ACC_PROC
Description
Pegging
This statistic pegs the total number of successful results per procedure including location services.
4-82 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application OK_ACC_PROC
Analysis
This statistic can be used for trend analysis of the number of successful accesses by procedure.
Reference GSM 12.04, 4.21, B.3.1.2.
GSM 4.08, 4.12, 3.15, 3.3.2.2, 4.4.1, 4.4.4.1, 4.5.1.1, 4.5.1.1,
4.5.1.6, 5.5.4, 7.3.1, 9.2.9, 9.2.12, 9.2.15, and 9.45.
Usage Radio resource allocation.
Quality of service monitoring: Call setup.
Network planning.
Ladder: Immediate assignment successful.
Key Statistics: RF_LOSS_RATE, SDCCH_MEAN_HOLD-
ING_TIME, SDCCH_MEAN_ARRIVAL_RATE,
SDCCH_RF_LOSS_RATE.
Basis Cell.
Type Counter array.
68P02901W56-Q 4-83
24 May 2004 CONTROLLED INTRODUCTION
OK_ACC_PROC_SUC_RACH Chapter 4: Cell statistics
OK_ACC_PROC_SUC_RACH
Description
Pegging
This statistic pegs what it determines to be a valid Channel Request (RACH). This does not
necessarily result in a seizure attempt of an SDCCH.
Analysis
This statistic can be used for trend analysis of the number of successful channel requests on the RACH of a cell.
Reference GSM 4.08, 3.8.0, 3.3.1. 3.3.2.2, 4.5.1.6, 5.5.4, 9.1.8 and 9.2.4.
GSM 12.04, 3.1.0, B.1.2.1.
Usage Radio resource allocation. Ladder: Immediate assignment
successful, Immediate assignment blocked, Immediate assignment
failure.
Basis Cell.
Type Counter.
4-84 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application OUT_HO_CAUSE_ATMPT
OUT_HO_CAUSE_ATMPT
Description
The OUT_HO_CAUSE_ATMPT statistic tracks the number of handover attempts per cell per cause.
The handover attempts include cases involving outgoing inter-cell handovers.
68P02901W56-Q 4-85
24 May 2004 CONTROLLED INTRODUCTION
OUT_HO_CAUSE_ATMPT Chapter 4: Cell statistics
When a specific bin is included in descriptions or formulae in this manual, the convention used for
the presentation of the statistic and the bin identification will be OUT_HO_CAUSE_ATMPT[bin
name]. An example of this convention is OUT_HO_CAUSE_ATMPT[UPQUAL].
Pegging
This statistic pegs the total number of handover attempts out of a specific cell and the cause
for each attempt. This statistic is pegged at the source cell.
Analysis
This statistic can be used for trend analysis of the number of handover attempts per cell per cause.
4-86 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application OUT_INTER_BSS_HO
OUT_INTER_BSS_HO
Description
The OUT_INTER_BSS_HO statistic tracks a range of handover actions associated with outgoing
inter-BSS handovers. A total value for this statistic is not meaningful and is not displayed.
Pegging
OUT_INTER_BSS_REQ_TO_MSC is pegged each time a handover required message is sent to the MSC.
OUT_INTER_BSS_HO_ATMPT is pegged when the handover command is forwarded to the MS.
OUT_INTER_BSS_HO_SUC is pegged when a clear command message is received.
OUT_INTER_BSS_HO_LOSTMS is pegged if a clear command is not received from the
MSC and no handover failure message is received either.
OUT_INTER_BSS_HO_RETURN is pegged each time an unsuccessful handover message is received.
OUT_INTER_BSS_EQUIP_FAIL is pegged if the MS returns a cause of equipment
failure in the handover failure message.
OUT_INTER_BSS_HO_CLEARED is pegged when a call is cleared down during an inter-BSS handover.
68P02901W56-Q 4-87
24 May 2004 CONTROLLED INTRODUCTION
OUT_INTER_BSS_HO Chapter 4: Cell statistics
Analysis
This statistic can be used for trend analysis of inter-BSS handovers on a per handover scenario basis.
Reference GSM 8.08, 3.9.2, 3.1.5.3.1 and 3.2.1.11. GSM 4.08, 3.8.0, 9.1.16
and 3.4.4.4.
GSM 3.1.5.1.1 and 3.2.1.9.
GSM 12.04, 3.2.0, B.1.1.8.
GSM 3.1.9.3 and 3.2.1.21.
Metrica.
Usage Radio resource allocation.
Quality of service monitoring.
Network planning.
Fault finding.
Service retainability.
Basis Cell.
Type Counter array.
4-88 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application OUT_INTRA_BSS_HO
OUT_INTRA_BSS_HO
Description
The OUT_INTRA_BSS_HO statistic tracks a range of handover actions associated with outgoing
intra-BSS handovers. A total value for this statistic is not meaningful and is not displayed.
Pegging
OUT_INTRA_BSS_HO_REQ is pegged each time an intra-BSS handover message is received.
OUT_INTRA_BSS_HO_PRI_BLK is pegged when resources not available message is received.
OUT_INTRA_BSS_HO_ATMPT is pegged when the initiate handover message is sent.
OUT_INTRA_BSS_HO_SUC is pegged when a handover performed message is sent.
OUT_INTRA_BSS_HO_LOSTMS is pegged if the MS fails to return to the original
channel during a handover attempt.
OUT_INTRA_BSS_HO_RETURN is pegged when an unsuccessful handover message is received.
OUT_INTRA_BSS_EQUIP_FAIL is pegged when an assignment failure message contains
an equipment failure cause or KSW/highway fault.
68P02901W56-Q 4-89
24 May 2004 CONTROLLED INTRODUCTION
OUT_INTRA_BSS_HO Chapter 4: Cell statistics
Analysis
This statistic can be used for trend analysis of intra-BSS handovers on a per (handover) scenario basis.
Reference GSM 4.08, 3.8.0, 3.4.4.4.
GSM 8.08, 3.9.2, 3.2.1.16 and 3.2.1.20.
GSM 4.08, 3.8.0, 3.4.4.4 & 7.3.6 and 9.1.16.
GSM 8.08, 3.9.2, 3.1.5.3.2 and 3.2.1.16.
GSM 8.08, 3.9.2, 3.1.7 and 3.1.5.1.1.
GSM 4.08, 3.8.0, 3.4.4.
GSM 8.08, 3.9.2, 3.1.7 and 3.1.5.3.1.
GSM12.04, 3.2.0, B.1.1.9.
GSM 8.08, 3.9.2, 3.1.7 and 3.1.5.2.1 and 3.2.1.12 & 3.2.1.25.
Metrica.
Usage Radio resource allocation.
Quality of service monitoring.
Network planning.
Fault finding.
Service retainability.
Basis Cell.
Type Counter array.
4-90 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application PAGE_REQ_FROM_MSC
PAGE_REQ_FROM_MSC
Description
The PAGE_REQ_FROM_MSC statistic tracks the number of paging requests received from the MSC.
This message is sent by the network when attempting to locate the MS. Each Page message
refers to only one MS. The BSS in turn transmits a paging message which may include
identities for more than one MS (see ACCESS_PER_PCH).
Pegging
This statistic pegs the number of Paging messages received from the MSC by the BSS. This statistic is
pegged when a Paging message is received pertaining to the cell in which the MS is paged.
Analysis
This statistic can be used for trend analysis of the number of paging requests received from the MSC.
68P02901W56-Q 4-91
24 May 2004 CONTROLLED INTRODUCTION
PAGING_REQUESTS Chapter 4: Cell statistics
PAGING_REQUESTS
Description
This statistic accounts for any message making use of a PCH block. This statistic is similar to
PCH_Q_PAGE_DISCARD except the messages are sent, not discarded. This statistic is obtained by
measuring the number of paging requests received from the network for transmission on the PCH.
The bins are:
Pegging
This statistic pegs every multiframe for each message going over a paging block (PCH).
Analysis
This statistic can be used for trend analysis of the number of paging requests received.
4-92 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application PCH_AGCH_Q_LENGTH
PCH_AGCH_Q_LENGTH
Description
Pegging
This statistic pegs once per paging multiframe, by summing the total number of messages in the paging
queue. At the end of the interval, the mean number of messages are calculated and reported.
Analysis
The 12.04 statistic B.2.1.1 is the mean of the number of messages in the PCH-AGCH queue.
68P02901W56-Q 4-93
24 May 2004 CONTROLLED INTRODUCTION
PCH_Q_PAGE_DISCARD Chapter 4: Cell statistics
PCH_Q_PAGE_DISCARD
Description
• PS pages discarded.
This statistic is obtained by measuring the number of Paging requests, which are discarded
from the PCH queue before they could be transmitted. Pages can be discarded from the queues
(assuming queuing is in operation) for a number of reasons, including queue overflow, priority
insertion in the queue causing an overflow and in-queue timer expiry.
Pegging
This statistic pegs each time a page from the MSC is overwritten while in the queue.
The statistic also pegs for CS and PS pages as well as the assignments which the
BSS was going to send over the PCH.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of paging messages
that may be discarded from the PCH queue that are acceptable in normal system operations.
Reference GSM 12.04, 4.2.1, B.2.1.8
Usage Quality of service: Paging analysis.
Optimization.
Network planning.
Basis Cell.
Type Counter.
Alarm Major.
4-94 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application PPCH_Q_PAGE_DISCARD
PPCH_Q_PAGE_DISCARD
{3723}
Description
The PPCH_Q_PAGE_DISCARD statistic tracks the number of Packet Paging Request messages
discarded from the PPCH queue before they could be transmitted.
A page may be discarded from the queue for the following reasons: queue overflow, priority
insertion causing an overflow, and an in_queue timer expiry. The only cause for discarding
pages in the Motorola BSS is queue overflow.
The bins are:
Bin Description
0 CS pages discarded.
1 PS pages discarded.
Pegging
This statistic pegs each time a Packet Paging Request is discarded from the PPCH queue.
68P02901W56-Q 4-95
24 May 2004 CONTROLLED INTRODUCTION
RF_LOSSES_SD Chapter 4: Cell statistics
RF_LOSSES_SD
Description
The RF_LOSSES_SD statistic tracks the number of calls lost while using a SDCCH. If a TCH
is reconfigured as a SDCCH, only the SDCCH statistics are configured.
Pegging
This statistic pegs the number of calls that were terminated because of RF problems. This
statistic will only peg for lost calls after the call has been established. This statistic will not be
pegged when the CHAN_REQ_MS_FAIL statistic is pegged.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of lost
calls while using a SDCCH that are acceptable in normal system operations.
If the specified threshold is exceeded, the 0. CELL: Radio frequency losses while using an
SDCCH - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at
the OMC-R (68P02901W26) for troubleshooting information.
4-96 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application RF_LOSSES_TCH
RF_LOSSES_TCH
Description
The RF_LOSSES_TCH statistic tracks the number of calls lost while using a full rate or half rate TCH.
RF_LOSSES_TCH is the BSS MMI name of the statistic kept by the BSS on a per
timeslot level. The OMC-R rolls the information up to the cell level and refers to
this information as RF_LOSSES_TCH_ROLL.NOTE
Pegging
This statistic pegs the number of full rate and half rate calls that were terminated because of
RF problems. It is composed of calls lost while using a TCH. If a TCH is reconfigured as
an SDCCH, only the SDCCH statistics are configured.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of lost
calls while using a TCH that are acceptable in normal system operations.
68P02901W56-Q 4-97
24 May 2004 CONTROLLED INTRODUCTION
RF_LOSSES_TCH Chapter 4: Cell statistics
RF_LOSSES_TCH is not pegged with any handover failure statistic. In a frequency hopping
environment, this statistic may not be useful at channel level; therefore, roll to cell level.
4-98 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SDCCH_CONGESTION
SDCCH_CONGESTION
Description
Pegging
This statistic records the sum of the duration of periods when all the SDCCH channels in a cell were
busy. The statistic also collects the mean, maximum, and minimum time of SDCCH congestion. If
a TCH is reconfigured as an SDCCH, only the SDCCH statistics are recorded.
Although the mean, maximum and minimum values are collected for this statistic, they can
only be viewed through the MMI using the disp_stats command.
Analysis
This statistic can be used for trend analysis of the length of time during which
SDCCH channels were not available.
Reference GSM 12.04, 3.1.0, B.1.3.5.
Usage RF loss.
Congestion.
Quality of service monitoring.
Network planning.
Optimization.
Basis Cell.
Type Duration (total time in milliseconds).
68P02901W56-Q 4-99
24 May 2004 CONTROLLED INTRODUCTION
SECOND_ASSIGN_ATMPT Chapter 4: Cell statistics
SECOND_ASSIGN_ATMPT
Description
The SECOND_ASSIGN_ATMPT statistic tracks the number of times the network initiated a second
assignment procedure on receipt of an Assignment Failure message from the MS.
Pegging
The BSS only attempts (initiates) a second assignment procedure on receipt of an Assignment
Failure message if the per BSS element second_asgnmnt is set.
Reference None.
Usage Congestion.
Basis Cell.
Type Counter.
4-100 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SECOND_ASSIGN_SUC
SECOND_ASSIGN_SUC
Description
The SECOND_ASSIGN_SUC statistic tracks the number of times that a second assignment procedure initiated
by the network is successfully completed, upon receipt of an Assignment Complete message from the MS.
Pegging
The BSS only attempts (initiates) a second assignment procedure on receipt of an Assignment
Failure message if the per BSS element second_asgnmnt is set.
Reference None.
Usage Congestion.
Basis Cell.
Type Counter.
68P02901W56-Q 4-101
24 May 2004 CONTROLLED INTRODUCTION
SMS_INIT_ON_SDCCH Chapter 4: Cell statistics
SMS_INIT_ON_SDCCH
Description
Pegging
This statistic is incremented on one successful Service Access Point (SAPI3) connection related to a SDCCH.
Analysis
This statistic can be used for trend analysis of how many SMS transactions occurred on a cell.
Usage Originated call and service/connection request.
Basis Cell.
Type Counter.
4-102 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SMS_INIT_ON_SDCCH_HO_IN
SMS_INIT_ON_SDCCH_HO_IN
Description
The SMS_INIT_ON_SDCCH_HO_IN statistic tracks how many Service Access Point (SAP13) connections
are established over an SDCCH for Short Message Service (SMS) transactions during incoming handovers .
Pegging
This statistic is incremented on one successful Service Access Point (SAPI3) connection related to a SDCCH.
Analysis
This statistic can be used for trend analysis of how many SAP13 connections occurred on a cell.
Usage Originated call and service/connection request.
Basis Cell.
Type Counter.
68P02901W56-Q 4-103
24 May 2004 CONTROLLED INTRODUCTION
SMS_INIT_ON_TCH Chapter 4: Cell statistics
SMS_INIT_ON_TCH
Description
The SMS_INIT_ON_TCH statistic tracks how many Short Message Service (SMS)
transactions occurred on a cell related to a TCH.
This statistic can be used to keep track of the number of times a Service Access Point (SAPI3) connection is
created, a SMS requires a logical SAPI3 connection. Additionally, the statistic can be used to determine
how TCHs are being utilized (for example, for SMS as opposed to normal voice traffic).
Pegging
This statistic is incremented upon successful SAPI3 connection related to a TCH.
Analysis
This statistic can be used for trend analysis of how many SMS transactions occurred on a cell related to a TCH.
Usage Originated call and service/connection request.
Basis Cell.
Type Counter.
4-104 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SMS_NO_BCAST_MSG
SMS_NO_BCAST_MSG
Description
The SMS_NO_BCAST_MSG statistic tracks the number of times that a message has
been broadcast on a per cell basis.
Pegging
This statistic pegs each time a message is broadcast on the CBCH.
Analysis
This statistic can be used for trend analysis of how many times a message has been broadcast on a per cell basis.
Usage Fault finding.
Basis Cell.
Type Counter.
68P02901W56-Q 4-105
24 May 2004 CONTROLLED INTRODUCTION
TCH_CONGESTION Chapter 4: Cell statistics
TCH_CONGESTION
Description
The TCH_CONGESTION statistic indicates the amount of time that no {22064} full
rate TCH channels were available in that cell.
The TCH_CONGESTION statistic will only be used for outer zone resources when {22064}
full rate TCH congestion is being measured for Concentric Cells.
A congestion (or blocking) state occurs when all {22064} full rate channels available to traffic
within a cell (the number may vary over time due to failure or maintenance actions) are busy,
where busy means unavailable for allocation to a new call attempt.
Pegging
This statistic pegs the sum of the duration of periods when all {22064} full rate TCHs were busy.
The statistic also reports the mean, maximum and minimum time of {22064} full rate TCH congestion. If a
{22064} full rate TCH is configured as an SDCCH only the SDCCH statistics will be configured.
4-106 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application TCH_CONG_INNER_ZONE
TCH_CONG_INNER_ZONE
Description
The TCH_CONG_INNER_ZONE statistic tracks the total length of time in which all of the
{22064} full rate TCHs in the inner zone of a concentric cell are busy. The Concentric Cell option
must be enabled for this statistic to be enabled, disabled, or displayed.
Pegging
The timer for this statistic is started when all TCHs belonging to {22064} full rate TCHs in the inner
zone are busy. The timer is stopped when an inner zone {22064} full rate TCH is freed.
Analysis
This statistic can be used for trend analysis of the length of time in which all of the {22064}
full rate TCHs in the inner zone of a concentric cell are busy.
Reference None.
Usage Network planning.
Basis Cell.
Type Duration.
68P02901W56-Q 4-107
24 May 2004 CONTROLLED INTRODUCTION
TCH_DELAY Chapter 4: Cell statistics
TCH_DELAY
Description
The TCH_DELAY statistic tracks the mean delay and the statistical distribution of the delay between an
assignment request or handover request and a TCH being allocated for each cell on the BSS.
As more calls (in proportion to the total number of calls) are queued, the mean delay will be longer. Queueing
is only done if the assignment or Handover Request indicates that queueing is allowed for that request. This
statistic will measure the queueing delay effectively. It is possible to have assignments and handovers for which
there is no delay in resource allocation. These no-delay assignments are included in the mean delay statistic.
Pegging
A timer is started when the request is queued and stopped when the request is allocated.
Analysis
This statistic can be used for trend analysis of the queueing delay for a traffic channel being allocated to a cell.
4-108 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application TCH_Q_LENGTH
TCH_Q_LENGTH
Description
The TCH_Q_LENGTH statistic tracks the arithmetic mean of the number of queued TCH
assignment procedures. Queueing is done due to the Call Queueing feature, Emergency
Call Pre-emption, EGSM, and Directed Retry.
Pegging
This measurement is obtained by sampling the TCH queue length and reporting the current length. The mean
TCH queue length includes the number of queued assignment and external handover requests.
Analysis
This statistic can be used for trend analysis of the number of queued TCH assignment procedures.
68P02901W56-Q 4-109
24 May 2004 CONTROLLED INTRODUCTION
TCH_Q_REMOVED Chapter 4: Cell statistics
TCH_Q_REMOVED
Description
The TCH_Q_REMOVED statistic tracks when a queued call is assigned to a Traffic Channel (TCH).
Pegging
These bins are pegged upon removal of either an assignment request or handover request from the TCH queue.
Analysis
This statistic can be used for trend analysis of the number of queued TCH assignment procedures.
Reference None.
Usage Quality of service: Network accessibility.
Network planning.
Optimization.
Basis Cell.
Type Counter array.
4-110 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application TCH_USAGE
TCH_USAGE
Description
The TCH_USAGE statistic gives an indication of the total amount of traffic carried by the cell. Active means
connected (capable of transmitting circuit mode user data) and activated, for example, used as a DCCH.
The TCH_USAGE statistic is used only for outer zone resources when TCH usage
is being measured for Concentric Cells.
The TCH_USAGE statistic measures only the usage of normal range channels in Extended Range Cells.
Both TCH_USAGE and BUSY_TCH include the guard timer value. This is a counter value.
The sum equals the amount of time in milliseconds the TCH was busy, kept by internal timers.
Therefore, when the interval expires, TCH usage may not be reported until the next interval. Exercise
caution if using this value over short interval periods. For example:
• Interval 0 starts.
• Interval 0 expires.
The value reported for the interval will only include the call for TCH0.
• Interval 1 starts.
Pegging
This statistic is the sum of the time that each TCH was active with a call for all TCHs on the cell. If
a TCH is reconfigured as an SDCCH, only the SDCCH statistics will be configured.
68P02901W56-Q 4-111
24 May 2004 CONTROLLED INTRODUCTION
TCH_USAGE Chapter 4: Cell statistics
Analysis
This statistic can be used for trend analysis of the total amount of traffic carried by the cell.
Reference GSM 4.08, 3.8.0, 3.1.4.
Usage RF loss.
Congestion.
Quality of service monitoring.
Network planning.
Optimization.
Basis Cell.
Type Counter.
4-112 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application TCH_USAGE_EXT_RANGE
TCH_USAGE_EXT_RANGE
Description
The TCH_USAGE_EXT_RANGE statistic tracks the number of extended range traffic channels in use.
This statistic may only be enabled if the Extended Range Cell feature is unrestricted and enabled for the cell.
Pegging
This statistic pegs each time an extended range traffic channel is used.
Analysis
This statistic can be used for trend analysis of the number of extended range traffic channels in use.
Reference None.
Usage Quality of service.
Network planning.
Radio resource allocation.
Basis Cell.
Type Counter.
68P02901W56-Q 4-113
24 May 2004 CONTROLLED INTRODUCTION
TCH_USAGE_INNER_ZONE Chapter 4: Cell statistics
TCH_USAGE_INNER_ZONE
Description
Pegging
This statistic pegs when a TCH belonging to a carrier in the inner zone is used.
Analysis
This statistic can be used for trend analysis of the usage of TCHs belonging to carriers
in the inner zone of a concentric cell.
Reference None.
Usage Network planning.
Basis Cell.
Type Counter.
4-114 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application TOTAL_CALLS
TOTAL_CALLS
Description
The TOTAL_CALLS statistic tracks the total number of calls originated for each cell on the BSS.
Pegging
This statistic indicates the number of circuit oriented calls that are originated in the cell. It is
pegged only once per connection at the time of the first successful TCH assignment procedure.
Subsequent channel changes, for example voice to data, are not counted.
This statistic does not necessarily peg all successful calls. It only pegs calls that have been
assigned to the TCH. For example, if the call fails to send a Direct Transfer Application Part
(DTAP) Connect Acknowledge, it still looks successful to the base.
Analysis
This statistic can be used for trend analysis of the total number of calls originated for each cell on the BSS.
68P02901W56-Q 4-115
24 May 2004 CONTROLLED INTRODUCTION
ZONE_CHANGE_ATMPT Chapter 4: Cell statistics
ZONE_CHANGE_ATMPT
Description
The ZONE_CHANGE_ATMPT statistic tracks attempts of each type of concentric cell specific handover.
The Concentric Cell option must be enabled for this statistic to be enabled, disabled, or displayed.
Pegging
Each bin is pegged when a corresponding concentric cell handover is attempted.
Analysis
This statistic can be used for trend analysis of the attempts of each type of concentric cell specific handover.
Reference None.
Usage Network planning.
Basis Cell.
Type Counter array.
4-116 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application ZONE_CHANGE_SUC
ZONE_CHANGE_SUC
Description
The ZONE_CHANGE_SUC statistic tracks each type of successful Concentric Cell specific handover. The
Concentric Cell option must be enabled for this statistic to be enabled, disabled, or displayed.
Pegging
Each bin is pegged when a corresponding concentric cell handover is successful.
Analysis
This statistic can be used for trend analysis of each type of successful concentric cell specific handover.
Reference None.
Usage Network planning.
Basis Cell.
Type Counter array.
68P02901W56-Q 4-117
24 May 2004 CONTROLLED INTRODUCTION
ZONE_CHANGE_SUC Chapter 4: Cell statistics
4-118 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
5
Neighbour statistics
When the BSS is configured to control inter-cell handovers, four of the handover statistics may
be used to track handovers. These neighbour statistics provide the destination cell of an outgoing
handover or the origination cell of an incoming handover.
Each of the neighbour statistics keep track of handover information for a pair of source and neighbour cells.
Neighbour statistics are described in "Introduction to neighbour statistics" on page 5-2.
68P02901W56-Q 5-1
24 May 2004 CONTROLLED INTRODUCTION
Introduction to neighbour statistics Chapter 5: Neighbour statistics
• Target cell - the neighbour cell into which the MS may be handed over. There is no limit
on the number of source cells that may handover calls to a target cell.
• Each neighbour statistic can be enabled for a maximum of 16 cells in a BSS. The cells
for which each of the statistics are enabled do not have to be the same.
When the copy_cell command is used to copy a cell for which one or more of the
neighbour statistics is enabled, all of the statistics for the cell created by the copy_cell
command will be disabled. The individual statistics for the new cell will have to be
enabled individually including the neighbour statistics.
• If the BSS is configured to have the MSC control intra-BSS handovers, the incoming
per cell statistics are affected, and may not be used to track handovers.
Outgoing neighbour statistics track the number of attempted and successful handovers from a
source cell into a neighbour cell. The outgoing neighbour statistics are:
• "OUT_HO_NC_CAUSE_ATMPT" on page 5-10.
5-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Introduction to neighbour statistics
• .
• .
• .
• .
• .
• .
68P02901W56-Q 5-3
24 May 2004 CONTROLLED INTRODUCTION
Introduction to neighbour statistics Chapter 5: Neighbour statistics
Incoming neighbour statistics track the number of attempted and successful handovers into a neighbour
cell from a source cell. Handovers are tracked for only 32 cells for each neighbour cell, even if a
neighbour cell has more than 32 source cells. The incoming neighbour statistics are:
• "IN_INTRA_BSS_NC_ATMPT" on page 5-8.
2. Each cell is sequentially checked, starting at 0 (local cell ID), until a source
which has not already been selected is found.
2. If the cell is not tracking 32 source cells, a check is done to see if new ones can be tracked.
3. If new source cells can be added, reciprocal neighbours are added first, followed by
non-reciprocal neighbours, which are chosen by sequentially looking through the database.
• .
• .
5-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Introduction to neighbour statistics
The following are examples of typical handover situations to show how neighbour cell statistics are pegged.
Notation
An example of the notation used in the examples is:
68P02901W56-Q 5-5
24 May 2004 CONTROLLED INTRODUCTION
Introduction to neighbour statistics Chapter 5: Neighbour statistics
IN_INTRA_BSS_NC_ATMPT: 0 (B-A)
Initial situation
Table 5-1 shows an example of three cells: cell_A, cell_B, and cell_C. All four neighbour cell statistics
are enabled at cell_A. For this example, all cells are internal to the same BSS.
cell_A cell_B
cell_C
Peg source
Neighbour status Initial peg count
target
cell_B is a neighbour of cell_A and IN_INTRA_BSS_NC_ATMPT 0 (B-A)
cell_A is a neighbour of cell_B IN_INTRA_BSS_NC_SUC 0 (B-A)
cell_C is a neighbour of cell_A and IN_INTRA_BSS_NC_ATMPT 0 (C-A)
cell_A is a neighbour of cell_C IN_INTRA_BSS_NC_SUC 0 (C-A)
OUT_HO_NC_CAUSE_ATMPT 0 (A-B)
OUT_HO_NC_SUC 0 (A-B)
OUT_HO_NC_CAUSE_ATMPT 0 (A-C)
OUT_HO_NC_SUC 0 (A-C)
5-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Introduction to neighbour statistics
68P02901W56-Q 5-7
24 May 2004 CONTROLLED INTRODUCTION
IN_INTRA_BSS_NC_ATMPT Chapter 5: Neighbour statistics
IN_INTRA_BSS_NC_ATMPT
Description
Pegging
This statistic is pegged in the target cell against a specific source cell. This is done each time
the SSM decides to perform an intra-BSS handover where the target is an internal neighbour
which is placed first in the Handover Recognized message.
Analysis
This statistic can be used for trend analysis of the number of handover attempts into a cell
and the location of the cells originating the handover attempts.
Reference GSM 12.04, 4.0.0, B.2.2.1GSM 4.08, 8.08, 8.58
Usage Handover.
Quality of Service.
Network Planning.
Optimization.
Fault Finding.
Basis NCell (Neighbour cell).
Type Counter.
5-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application IN_INTRA_BSS_NC_SUC
IN_INTRA_BSS_NC_SUC
Description
Pegging
This statistic is pegged in the target cell upon notification of a successful intra-BSS handover from a specific cell.
Analysis
This statistic can be used for trend analysis of incoming internal inter-cell handovers per originating cell.
68P02901W56-Q 5-9
24 May 2004 CONTROLLED INTRODUCTION
OUT_HO_NC_CAUSE_ATMPT Chapter 5: Neighbour statistics
OUT_HO_NC_CAUSE_ATMPT
Description
Pegging
This statistic pegs the total number of handover attempts out of a specific cell, the location of the target
cell, and the cause for each attempt. This statistic is pegged at the source cell.
5-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application OUT_HO_NC_CAUSE_ATMPT
Analysis
This statistic can be used for trend analysis of handover attempts per neighbour on a per cause basis.
Reference GSM 12.04, 4.0.0, B.2.2.3GSM 4.08, 8.08, 8.58GSM 12.04, 4.2.1
Usage Handover.
Quality of Service.
Network Planning.
Optimization.
Fault Finding.
Ladder: Intra-BSS handover.
Basis NCell (Neighbour cell).
Type Counter array.
68P02901W56-Q 5-11
24 May 2004 CONTROLLED INTRODUCTION
OUT_HO_NC_SUC Chapter 5: Neighbour statistics
OUT_HO_NC_SUC
Description
The OUT_HO_NC_SUC statistic tracks the number of successful outgoing inter-cell handovers
per target cell. This statistic can be enabled for a maximum of 16 cells. For each cell where the
statistic is enabled, a maximum of 32 target cells can be tracked.
Pegging
This statistic pegs the total number of successful handovers out of a specific cell and the
location of the target cell for each successful handover.
Analysis
This statistic can be used for trend analysis of handover performance of specific cells
for each of its neighbouring target cells.
Reference GSM 12.04, 4.0.0, B.2.2.4
GSM 4.08, 8.08, 8.58
Usage Handover.
Quality of Service.
Network Planning.
Optimization.
Fault Finding.
Basis NCell (Neighbour cell).
Type Counter.
5-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
6
Carrier and timeslot statistics
Carrier and timeslot statistics are captured from events occurring in a carrier. They are categorized into
subgroups, each of which are described in "Carrier and timeslot statistics subgroups" on page 6-2.
68P02901W56-Q 6-1
24 May 2004 CONTROLLED INTRODUCTION
Carrier and timeslot statistics subgroups Chapter 6: Carrier and timeslot statistics
Carrier and timeslot statistics are organized into the following major subgroups:
• "Downlink RXQUAL (BER)" on page 6-2.
Downlink receive quality statistics are used to track the Bit Error Rate (BER) of active channels.
The statistic "BER" on page 6-6 is the only downlink RXQUAL statistic.
Uplink receive quality statistics are used to track the Bit Error Rate (BER) of active channels. The
statistic "U_BER" on page 6-23 is the only uplink RXQUAL statistic.
Link balance verification statistics are used to track the link balance between air interface of the
uplink and downlink path loss. The following are the link balance statistics:
• "CHAN_DL_TX_PWR_LVL" on page 6-8.
6-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Carrier and timeslot statistics subgroups
BTS dynamic allocation statistics are used to track utilization of dynet channels. The
following are the BTS dynamic allocation statistics:
• "ALLOC_SDCCH_CARR" on page 6-4.
Timing advance
The timing advance statistic "ROC" on page 6-22 is used to monitor the timing advance measurements.
Miscellaneous
Miscellaneous statistics are used to track several unrelated carrier and timeslot statistics.
The following are the miscellaneous carrier statistics:
• "CHAN_REQ_MS_FAIL" on page 6-9.
68P02901W56-Q 6-3
24 May 2004 CONTROLLED INTRODUCTION
ALLOC_SDCCH_CARR Chapter 6: Carrier and timeslot statistics
ALLOC_SDCCH_CARR
Description
The ALLOC_SDCCH_CARR statistic is the sum of the number of SDCCH allocations per carrier within a cell.
Pegging
This statistic pegs each time an Immediate Assignment message is sent by the BSS. An
Immediate Assignment message will be sent upon:
• Successful handover on an SDCCH channel.
This statistic pegs for reasons other than calls requiring a traffic channel, such as location updates.
Analysis
This statistic can be used for trend analysis of SDCCH allocations and allows the calculation
of the mean hold time of a SDCCH per carrier.
Reference GSM 12.04, 3.1.0, B.1.3.3.
GSM 4.08, 3.8.0, 3.3.12, 3.4.3.1, 3.4.4.1, 9.1.2 to 9.1.4, 9.1.14 to
9.1.19.
Usage RF loss.
Congestion.
Quality of service monitoring: Call set-up.
Network planning.
Ladder: Immediate assignment successful, Intra-cell handover,
Inter-BSS handover, Connection establishment, Intra-BSS
handover.
Basis Carrier.
Type Counter.
6-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application ALLOC_TCH_CARR
ALLOC_TCH_CARR
Description
The ALLOC_TCH_CARR statistic provides the number of successful TCH allocations per
carrier within a cell for both call originations and hand ins.
Pegging
This statistic pegs for successful TCH allocations per carrier within a cell as a result
of a call establishment or hand in attempt:
• Successful allocation due to call establishment including successful
allocations due to directed retries.
This statistic is pegged before the transmission of the assignment/handover command to the MS and,
therefore, does not take into account the success or failure of the assignment/hand in from an RF perspective.
Analysis
This statistic can be used for trend analysis of TCH allocations and allows the calculation
of the mean hold time of a TCH per carrier.
Usage Quality of service monitoring: Call setup.
Network planning.
Ladder: Intra-BSS handover, Inter-BSS handover, Intra-cell
handover, Assignment to TCH.
Key statistics: TCH_MEAN_ARRIVAL_RATE,
TCH_MEAN_HOLDING_TIME, CELL_TCH_ALLOCA-
TIONS, TCH_RF_LOSS_RATE.
Basis Carrier.
Type Counter.
68P02901W56-Q 6-5
24 May 2004 CONTROLLED INTRODUCTION
BER Chapter 6: Carrier and timeslot statistics
BER
Description
The BER statistic tracks the minimum, maximum, and mean Bit Error Rate (BER) for active
channels. The bit error rate value corresponds to the RXQUAL downlink measurement reports.
BER statistic measurements are reported only when the channel is active.
BER on SDCCH channels are affected by phantom RACHs. BER on TCHs are not affected. For a
cell with a non-combined BCCH configuration, there are no values presented on timeslot 0.
Pegging
The statistic pegs every 480 ms (corresponding to each SACCH multiframe).
Units
This statistic is reported using values 0 to 7 that are derived from the RXQUAL values:
6-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application BER
Analysis
This statistic can be used for trend analysis of the BER for active channels.
Reference GSM 4.08, 3.8.0, 3.4.1.2 and 9.1.20 and 10.5.2.11.
GSM 5.08, 3.6.0,8.2 and Appendix A.3.i.
Usage RF loss.
Congestion.
Quality of service monitoring.
Fault finding.
Basis Timeslot.
Type Normal distribution.
68P02901W56-Q 6-7
24 May 2004 CONTROLLED INTRODUCTION
CHAN_DL_TX_PWR_LVL Chapter 6: Carrier and timeslot statistics
CHAN_DL_TX_PWR_LVL
Description
The CHAN_DL_TX_PWR_LVL statistic tracks the maximum, mean, and minimum BSS
(downlink) transmit power level. The reported value is in dBm units.
Pegging
This statistic pegs every SACCH multiframe.
Analysis
This statistic can be used for trend analysis of mean BSS transmit power levels.
6-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CHAN_REQ_MS_FAIL
CHAN_REQ_MS_FAIL
Description
The CHAN_REQ_MS_FAIL statistic tracks the number of times that the BSS times out while waiting for the
MS to establish on the SDCCH that was assigned to it during the immediate assignment procedure.
An Immediate Assign message is sent to the MS on the Access Grant CHannel (AGCH)
and a SDCCH allocated. When the MS does not reply with a SABM on that SDCCH, the
allocated channel is relinquished, and the request forgotten.
This may be a normal occurrence on few occasions such as when the MS is moving out of range, the
MS is failing, or the MS is switched off. However, frequent occurrences of this event within a short
period of time and/or geographically clustered may indicate a hardware failure.
CHAN_REQ_MS_FAIL is the BSS MMI name of the statistic kept by the BSS on
a per timeslot level. The OMC-R rolls the information up to the cell level and refers
to this information as CHAN_REQ_MS_FAIL_ROLL.
Pegging
This statistic pegs when the MS does not reply with Set Asynchronous Balanced Mode (SABM) on the SDCCH.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of BSS
timeouts while waiting for an MS to establish on the SDCCH assigned during the immediate
assignment procedure that are acceptable in normal system operations.
If the specified threshold is exceeded, the 1. CELL: Attempt at allocating an SDCCH
failed - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at
the OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 4.08, 3.8.0, 3.3.1.4 and 9.1.17.
Usage Radio resource and allocation.
Fault finding.
Quality of service monitoring: Call setup.
Ladder: Immediate assignment blocked.
Basis Timeslot.
Type Counter.
Alarm Minor.
68P02901W56-Q 6-9
24 May 2004 CONTROLLED INTRODUCTION
CHAN_REQ_MS_FAIL Chapter 6: Carrier and timeslot statistics
6-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CHAN_UL_TX_PWR_LVL
CHAN_UL_TX_PWR_LVL
Description
The CHAN_UL_TX_PWR_LVL statistic tracks the maximum, mean, and minimum MS (uplink)
transmit power levels. The value is reported in dBm units.
Pegging
This statistic pegs every SACCH multiframe.
Analysis
This statistic can be used for trend analysis of mean MS transmit power levels.
68P02901W56-Q 6-11
24 May 2004 CONTROLLED INTRODUCTION
FER_GSM_FR_EFR Chapter 6: Carrier and timeslot statistics
FER_GSM_FR_EFR
{22064}
Description
Pegging
This statistic pegs the uplink frame erasure rate for non_AMR calls for each carrier in a cell.
Units
The FER_GSM_FR_EFR is reported using values 0 to 9 as follows.
FER_GSM_FR_EFR Quality
FER ratio (min:1 to max:1)
number
0 0.0000 to 0.0416
1 0.0417 to 0.0832
2 0.0833 to 0.1249
3 0.1250 to 0.1666
4 0.1667 to 0.2082
5 0.2083 to 0.2499
6 0.2500 to 0.2916
7 0.2917 to 0.3332
6-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application FER_GSM_FR_EFR
Analysis
This statistic can be used for trend analysis for target optimization effects on cell/radios with regards to quality.
Reference None.
Usage Quality of service,
Fault finding,
RF loss,
Congestion.
Basis Carrier.
Type Normal distribution.
68P02901W56-Q 6-13
24 May 2004 CONTROLLED INTRODUCTION
INTF_ON_IDLE Chapter 6: Carrier and timeslot statistics
INTF_ON_IDLE
Description
The INTF_ON_IDLE statistic indicates the maximum, minimum, and mean interference levels
experienced on idle channels as determined by the BSS.
The bin ranges may be changed using the chg_stat_prop command. The default bin ranges
for the INTF_ON_IDLE statistic are shown in Table 6-2.
Bin Range
0 0 - 5
1 6 - 10
2 11 - 15
3 16 - 20
4 21 - 25
5 26 - 30
6 31 - 35
7 36 - 40
8 41 - 45
9 46 - 65
Table 6-3 provides an indication of the interference on a channel by recording measurements of received
signal strength taken when the channel is idle. This measurement parallels the activity of the channel selection
algorithm of the Cell Resource Manager which uses the same data to rank idle channels, giving preference
to the channels with a lower interference level. The measured signal level is mapped to an RXLEV value
between 0 and 63. Each RXLEV value corresponds to a dBm value, as shown in Table 6-3.
6-14 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application INTF_ON_IDLE
Pegging
This statistic pegs every 480 ms.
Analysis
This statistic can be used for trend analysis of interference levels experienced on idle channels.
Reference GSM 12.04, 3.2.0, B.1.1.13.
GSM 5.08, 3.6.0, 8.1-8.5 and Appendix A.3.ii.
Usage RF loss and congestion.
Quality of service monitoring.
Network planning.
Fault finding.
Basis Timeslot.
Type Normal distribution.
68P02901W56-Q 6-15
24 May 2004 CONTROLLED INTRODUCTION
PATH_BALANCE Chapter 6: Carrier and timeslot statistics
PATH_BALANCE
Description
The PATH_BALANCE statistic tracks the maximum, minimum, and mean link balance on
the air interface between the uplink and downlink path loss.
The actual value for path_balance depends on the type of RF combining used.
Pegging
This statistic is pegged by the value calculated by the following equation:
path_balance = path loss + 110
where:
path loss = uplink path loss - downlink path loss
where:
uplink path loss = actual MS txpower - rxlev_ul
downlink path loss = actual BTS txpower - rxlev_dl
The rxlev_ul and rxlev_dl values reflect the latest reported value and are not averaged values.
PATH_BALANCE is not pegged when either rxlev_ul or rxlev_dl is equal to 63 (-47 dBm).
The range of values for this statistic is 0 to 220 with a long term average of 110 with normal use. A
deviation of ±10 is acceptable, but this is to be understood as a practical guide and not as product
tolerance. If the deviation is greater than ±10, the RF path should be checked.
6-16 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application PATH_BALANCE
Typically, the path loss should be similar in both the uplink and downlink directions. When diversity gain
is enabled, the path balance will be just below 110, indicating a lower uplink path loss.
If... Then...
the Horizon cabinet is equipped with Horizonmacro the SITE alarm 28 “data configuration and Horizon
database, the path_balance statistic will be hardware mismatch" will be generatedoperators
incorrect. should change either the hardware or the database
accordingly.
Consult the manual, Maintenance Information:
Alarm Handling At The OMC-R (68P02901W26).
the Horizonmacro cabinet is equipped with Horizon the SITE alarm 28 “data configuration and Horizon
database, the path_balance statistic will be hardware mismatch" will be generated.operators
incorrect. should change either the hardware or the database
accordingly.
Consult the manual, Maintenance Information:
Alarm Handling At The OMC-R (68P02901W26).
If the Horizonmacro booster unit is faulty or not present, the path_balance statistic is
incorrect. Operators should disregard this statistic until the booster is replaced. Network
planners should check with the OMC operator to determine if any Horizonmacro
alarms (SITE alarms 25, 26 or 27) have been generated.
Analysis
This statistic can be used for trend analysis of the link balance on the air interface
between the uplink and downlink path loss.
Reference None.
Usage Quality of service: Service integrity.
Optimization.
Fault finding.
Basis Carrier.
Type Normal distribution.
Unit dB.
68P02901W56-Q 6-17
24 May 2004 CONTROLLED INTRODUCTION
RBER Chapter 6: Carrier and timeslot statistics
RBER
Description
The RBER (Residual Bit Error Rate) Quality statistic is derived from a ratio of number of bits in
error to total number of bits received, within error detected speech frames defined as good. The
measurement period over which the calculation is made is 480 ms.
During this period, 24 speech frames are decoded and a ratio calculated. By referring to a lookup
table, the ratio is converted to an RBER Quality number between 0 and 7.
Pegging
Every 480 ms, during the SACCH multi-frame by the RSS/HO process.
Units
The RBER statistic is reported using values 0 to 7.
The bin ranges for this statistic are fixed and may not be altered by the operator.
6-18 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application RBER
Analysis
This statistic can be used for trend analysis for target optimization effects on cell/radios with regards to quality.
Reference None.
Usage Quality of service.
Fault finding.
RF loss.
Congestion.
Basis Timeslot.
Type Normal distribution.
68P02901W56-Q 6-19
24 May 2004 CONTROLLED INTRODUCTION
RF_LOSSES_TCH Chapter 6: Carrier and timeslot statistics
RF_LOSSES_TCH
Description
The RF_LOSSES_TCH statistic tracks the number of calls lost while using a full rate or half rate TCH.
RF_LOSSES_TCH is the BSS MMI name of the statistic kept by the BSS on a per
timeslot level. The OMC-R rolls the information up to the cell level and refers to
this information as RF_LOSSES_TCH_ROLL.NOTE
Pegging
This statistic pegs the number of full rate and half rate calls that were terminated because of
RF problems. It is composed of calls lost while using a TCH. If a TCH is reconfigured as
an SDCCH, only the SDCCH statistics are configured.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of lost
calls while using a TCH that are acceptable in normal system operations.
6-20 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application RF_LOSSES_TCH
RF_LOSSES_TCH is not pegged with any handover failure statistic. In a frequency hopping
environment, this statistic may not be useful at channel level; therefore, roll to cell level.
68P02901W56-Q 6-21
24 May 2004 CONTROLLED INTRODUCTION
ROC Chapter 6: Carrier and timeslot statistics
ROC
Description
The ROC statistic tracks the maximum, minimum and mean Range Of Carrier between BSS and MS
on a per carrier basis. The range of carrier value corresponds to the timing advance (TA) measurement
reports. ROC statistic measurements are only reported for active channels.
The bin ranges for the ROC statistic correspond to a number of user definable TA ranges up to
a maximum of 10 bins. The default bin ranges are shown in Table 6-5.
Bin TA Range
0 0 to 6
1 7 to 13
2 14 to 20
3 21 to 27
4 28 to 34
5 35 to 41
6 42 to 48
7 49 to 54
8 55 to 63
9 64 to 219
These bins are not displayed at the OMC but can be displayed at the MMI. To set and display
the bin ranges refer to the chg_stat_prop and disp_stat_prop commands in Chapter 2.
Pegging
The statistic pegs every 480 ms (corresponding to each SACCH multiframe).
Basis Carrier.
Type Normal distribution.
6-22 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application U_BER
U_BER
Description
The U_BER statistic tracks the minimum, maximum, and mean Bit Error Rate (BER) for active
channels. The bit error rate value corresponds to the RXQUAL uplink measurement reports. U_BER
statistic measurements are reported only when the channel is active.
BER on SDCCH channels are affected by phantom RACHs. BER on TCHs are not affected. For a
cell with a non-combined BCCH configuration, there are no values presented on timeslot 0.
Pegging
The statistic pegs every 480 ms (corresponding to each SACCH multiframe).
Units
This statistic is reported using values 0 to 7 that are derived from the RXQUAL values:
68P02901W56-Q 6-23
24 May 2004 CONTROLLED INTRODUCTION
U_BER Chapter 6: Carrier and timeslot statistics
Analysis
This statistic can be used to provide monitoring of uplink RXQUAL performance.
Reference GSM 4.08, 3.8.0, 3.4.1.2 and 9.1.20 and 10.5.2.11.
GSM 5.08, 3.6.0,8.2 and Appendix A.3.i.
Usage RF loss.
Congestion.
Quality of service monitoring.
Fault finding.
Basis Timeslot.
Type Normal distribution.
6-24 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application UPLINK_PATH_LOSS
UPLINK_PATH_LOSS
Description
The UPLINK_PATH_LOSS statistic tracks the minimum, mean, and maximum uplink
losses on a per carrier basis. Reported values can be used to create a profile of the radio link
propagation losses experienced by MSs served in the cell.
Pegging
This statistic is pegged every SACCH multiframe for each active call.
Analysis
This statistic can be used for trend analysis of the uplink losses on a per carrier basis.
Reference None.
Usage RF Loss.
Quality of Service.
Basis Carrier.
Type Normal distribution.
68P02901W56-Q 6-25
24 May 2004 CONTROLLED INTRODUCTION
UPLINK_PATH_LOSS Chapter 6: Carrier and timeslot statistics
6-26 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
7
GPROC and DPROC statistics
GPROC and DPROC statistics track the utilization of the processing units found in various
hardware components in the BSS, for example GPROC and DPROC devices. In the GSM
statistics application, there is only one processor utilization statistic, CPU_USAGE. A full
description of this statistic is given in "CPU_USAGE" on page 7-2.
68P02901W56-Q 7-1
24 May 2004 CONTROLLED INTRODUCTION
CPU_USAGE Chapter 7: GPROC and DPROC statistics
CPU_USAGE
Description
The CPU_USAGE statistic tracks CPU usage. Monitoring of CPU usage allows the operator to determine
if the GPROC and DPROC devices at a particular site are being over, under, or properly utilized.
This statistic is updated from reports generated by the internal executive system, which
keeps track of when CPU usage changes.
Pegging
This statistic records the maximum, minimum, and mean values of the short-term processor utilization
measurement (from which the 30-minute mean, statistic Mean Utilization, is calculated). This statistic
is recorded for each GPROC and DPROC under the control of a BSS.
Analysis
This statistic can be used for trend analysis of GPROC and DPROC utilization.
7-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
8
LMTL statistics
Location Services Message Transfer Link (LMTL) statistics are used to track events for the Location Services
Message Transfer Part (LMTP) of the ITU-TSS No. 7 protocol on the BSC to MSC interface. They are
categorized into subgroups, each of which are described in "LMTL statistics subgroups" on page 8-2.
68P02901W56-Q 8-1
24 May 2004 CONTROLLED INTRODUCTION
LMTL statistics subgroups Chapter 8: LMTL statistics
LMTP C7 availablility
LMTP C7 availability statistics are used to track the duration of signalling link outages and
inhibitions (local and remote) for the LMTP of the ITU-TSS No.7 protocol on the BSC to MSC
interface. The following are the MTP C7 availability statistics:
• "LMTP_LINKFAIL" on page 8-10.
LMTP C7 performance
LMTP C7 performance statistics are used to track the different types of failure and recovery
situations for the LMTP of the ITU-TSS No.7 protocol on the BSC to MSC interface. The
following are the LMTP C7 performance statistics:
• "LMTP_CHANGEBACK" on page 8-6.
8-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LMTL statistics subgroups
LMTP C7 utilization
LMTP C7 utilization statistics are used to track the number of messages received, transmitted and
retransmitted on signalling links and supply information on signalling link congestion for the LMTP of the
ITU-TSS No.7 protocol on the BSC to MSC interface. The following are the LMTP C7 utilization statistics:
• "LMTP_CONGESTION_LOST_MSU" on page 8-4.
68P02901W56-Q 8-3
24 May 2004 CONTROLLED INTRODUCTION
LMTP_CONGESTION_LOST_MSU Chapter 8: LMTL statistics
LMTP_CONGESTION_LOST_MSU
Description
Pegging
This statistic pegs for each congestion event on the Lb-interface which results in MSUs being lost.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of lost
MSUs due to SL congestion that are acceptable in normal system operations.
If the specified threshold is exceeded, the 11. LMTL: SL congestion events resulting in loss
of MSUs - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling
at the OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 utilization.
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Warning.
8-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LMTP_MSU_DISCARDED
LMTP_MSU_DISCARDED
Description
Pegging
This statistic pegs each time an MSU is discarded due to Lb-interface SL congestion.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of MSUs are
being discarded due to SL congestion that are acceptable in normal system operations.
If the specified threshold is exceeded, the 10. LMTL: MSUs discarded due to SL congestion
- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 utilization.
Network planning.
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Warning.
68P02901W56-Q 8-5
24 May 2004 CONTROLLED INTRODUCTION
LMTP_CHANGEBACK Chapter 8: LMTL statistics
LMTP_CHANGEBACK
Description
Pegging
This statistic pegs when MTP traffic that has been changed over to an alternate Signalling
Link (SL) is diverted back to the original SL.
Analysis
This statistic can be used for trend analysis of automatic changebacks that have been successfully completed.
8-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LMTP_CHANGEOVER
LMTP_CHANGEOVER
Description
The LMTP_CHANGEOVER statistic tracks the number of local automatic changeovers that have
been successfully completed. This indicates MTP traffic is being transferred from an Lb interface
Signalling Link (SL) that is going out of service to an alternate SL.
Pegging
This statistic pegs when MTP traffic is changed over to an alternate Lb interface SL.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of out of sequence
messages between a BSS and an SMLC that are acceptable in normal system operations.
If the specified threshold is exceeded, the 7. LMTL: SL number of negative acks received
- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 performance.
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
68P02901W56-Q 8-7
24 May 2004 CONTROLLED INTRODUCTION
LMTP_LOCAL_SL_CONGESTION Chapter 8: LMTL statistics
LMTP_LOCAL_SL_CONGESTION
Description
Pegging
The statistic pegs each time the Lb-interface SL goes into the congestion state at the local site.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of
congestion onsets that are acceptable in normal system operations.
If the specified threshold is exceeded, the 12. LMTL :SL Congestion Indications - PM alarm is generated.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 utilization.
Network planning.
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Major.
8-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LMTP_LINK_INS
LMTP_LINK_INS
Description
The LMTP_LINK_INS statistic tracks the length of time that an Lb-interface Signalling
Link (SL) is in the in-service state.
Pegging
The timer for this statistic is started when an SL is brought into service. The timer is stopped
when the Lb-interface SL is removed from service.
Analysis
This statistic can be used for trend analysis of the utilization of in-service SLs.
68P02901W56-Q 8-9
24 May 2004 CONTROLLED INTRODUCTION
LMTP_LINKFAIL Chapter 8: LMTL statistics
LMTP_LINKFAIL
Description
The LMTP_LINKFAIL statistic tracks the duration of the Lb-interface Signalling Link (SL) unavailability
due to SL failure. It records the total time a particular SL is out of service while trying to align to the SMLC.
Pegging
This statistic timer is started when the SL fails. It is stopped when the SL comes back into service.
Analysis
This statistic can be used for analysis of SL unavailability due to SL failure.
8-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LMTP_LOCAL_BUSY
LMTP_LOCAL_BUSY
Description
The LMTP_LOCAL_BUSY statistic tracks the total time congestion is present on the
local end of the Lb-interface Signalling Link (SL).
Pegging
This statistic is started when congestion is detected on an Lb-interface SL. The statistic
is stopped when normal operation is resumed.
Analysis
This statistic can be used for trend analysis on congestion durations on the local end of the SL.
68P02901W56-Q 8-11
24 May 2004 CONTROLLED INTRODUCTION
LMTP_LOCAL_MGT Chapter 8: LMTL statistics
LMTP_LOCAL_MGT
Description
The LMTP_LOCAL_MGT statistic tracks the total time that a local Lb-interface Signalling
Link (SL) is inhibited due to local management actions.
Pegging
This statistic is started each time the SL is inhibited due to local management actions,
and stopped when the link is enabled.
Analysis
This statistic can be used for trend analysis on inhibited local SLs due to local management action.
8-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LMTP_MGT_INHIBIT
LMTP_MGT_INHIBIT
Description
Pegging
This statistic is started each time the Lb-interface SL is inhibited by the operator.
Analysis
This statistic can be used for trend analysis on inhibited SLs using the shutdown
command on the associated MTP link.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 availability.
Basis Lb SS7_LINK.
Type Counter.
68P02901W56-Q 8-13
24 May 2004 CONTROLLED INTRODUCTION
LMTP_MGT_UNINHIBIT Chapter 8: LMTL statistics
LMTP_MGT_UNINHIBIT
Description
Pegging
This statistic is pegged each time the SL is uninhibited by the operator.
Analysis
This statistic can be used for trend analysis on uninhibited SLs using the unlock
command on the associated MTP link.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 availability.
Basis Lb SS7_LINK.
Type Counter.
8-14 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LMTP_MSU_RX
LMTP_MSU_RX
Description
The LMTP_MSU_RX statistic tracks the number of Message Signal Units (MSUs)
received on a Lb-interface signalling link.
Pegging
This statistic pegs each time MSUs are received over the Lb-interface signalling link.
68P02901W56-Q 8-15
24 May 2004 CONTROLLED INTRODUCTION
LMTP_MSU_TX Chapter 8: LMTL statistics
LMTP_MSU_TX
Description
The LMTP_MSU_TX statistic tracks the number of Message Signal Units (MSUs)
transmitted on an Lb-interface signalling link.
Pegging
This statistic pegs each time MSUs are transmitted over the Lb-interface signalling link.
8-16 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LMTP_NEG_ACKS
LMTP_NEG_ACKS
Description
The LMTP_NEG_ACKS statistic tracks the number of out-of-sequence messages between a BSS
and the BSS-based SMLC across the Lb-interface signalling link.
Pegging
This statistic pegs when the BSS detects out of order messages to the SMLC and requests retransmission.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of out of sequence
messages between a BSS and an SMLC that are acceptable in normal system operations.
If the specified threshold is exceeded, the 7. LMTL: SL number of negative acks received
- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 performance.
Basis Lb SS7_LINK.
Type Counter.
Alarm Warning.
68P02901W56-Q 8-17
24 May 2004 CONTROLLED INTRODUCTION
LMTP_RE_TX Chapter 8: LMTL statistics
LMTP_RE_TX
Description
The LMTP_RE_TX statistic tracks the number of octets that the BSS has retransmitted to the SMLC
because the SMLC has requested retransmission. This indicates how much the BSS and an SMLC
are off in message sequencing by the number of octets retransmitted.
Pegging
This statistic peg the number of octets retransmitted by the BSS to the SMLC.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of octet
retransmissions that are acceptable in normal system operations.
If the specified threshold is exceeded, the 9.LMTL: Number of octets retransmitted - PM
alarm is generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R
(68P02901W26) for troubleshooting information.
8-18 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LMTP_REMOTE_MGT
LMTP_REMOTE_MGT
Description
Pegging
This statistic pegs the duration of the Lb-interface SL inhibition due to remote management action.
Analysis
This statistic can be used for trend analysis of remote management SL inhibition actions.
68P02901W56-Q 8-19
24 May 2004 CONTROLLED INTRODUCTION
LMTP_REMOTE_PROC Chapter 8: LMTL statistics
LMTP_REMOTE_PROC
Description
The LMTP_REMOTE_PROC statistic tracks the time that a remote processor is out of service.
Pegging
This statistic pegs when a remote processor outage is identified, and stopped when
the processor outage condition ceases.
Analysis
This statistic can be used for trend analysis of remote processor outage occurrences in the BSS-based SMLC.
8-20 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LMTP_RESTORATION
LMTP_RESTORATION
Description
The LMTP_RESTORATION statistic tracks the number of times user traffic is allowed on an Lb-interface
Signalling Link (SL) that is in service and not inhibited. This statistic does not track recovery from link fail.
Pegging
This statistic pegs when the Lb-interface SL starts carrying user traffic. This happens when the Lb-interface
SL comes into service, is uninhibited, or recovers from a remote processor outage.
Analysis
This statistic can be used for trend analysis of used traffic being allowed on an SL.
68P02901W56-Q 8-21
24 May 2004 CONTROLLED INTRODUCTION
LMTP_SIF_SIO_RX Chapter 8: LMTL statistics
LMTP_SIF_SIO_RX
Description
The LMTP_SIF_SIO_RX statistic tracks the number of Signal Information Fields (SIF) or Service
Information Octets (SIO) that are received over an Lb-interface signalling link.
Pegging
This statistic pegs each time an SIF or SIO is received over an Lb-interface signalling link.
8-22 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LMTP_SIF_SIO_TX
LMTP_SIF_SIO_TX
Description
The LMTP_SIF_SIO_TX statistic tracks the number of Signal Information Fields (SIF) or Service
Information Octets (SIO) that are transmitted over a signalling link by the BSC to the SMLC.
Pegging
This statistic pegs each time an SIF or SIO are transmitted over a signalling link by the BSC to the SMLC.
68P02901W56-Q 8-23
24 May 2004 CONTROLLED INTRODUCTION
LMTP_SL_ACK Chapter 8: LMTL statistics
LMTP_SL_ACK
Description
The LMTP_SL_ACK statistic tracks the number of times that the link was lost due to
an Lb-interface MTP layer 2 T7 timer expiry.
Pegging
This statistic pegs each time the link is lost due to a timer that expires when an acknowledgement
from the BSS-based SMLC is not received.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of
acknowledgements of MSUs not being received by the BSC that are acceptable in normal system operations.
If the specified threshold is exceeded, the 2. LMTL: SL failure - excessive delay of ACK
- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 performance.
Basis Lb SS7_LINK.
Type Counter.
Alarm Major.
8-24 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LMTP_SL_ALIGNMENT
LMTP_SL_ALIGNMENT
Description
Pegging
This statistic pegs each time an out of service Signalling Link (SL) unsuccessfully
tries to align with the Lb-interface.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of unsuccessful
attempts to align an out-of-service SL to the Lb-interface that are acceptable in normal system operations.
If the specified threshold is exceeded, the 5. LMTL: SL alignment failure - PM alarm
is generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R
(68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 performance.
Basis Lb SS7_LINK.
Type Counter.
Alarm Minor.
68P02901W56-Q 8-25
24 May 2004 CONTROLLED INTRODUCTION
LMTP_REMOTE_SL_CONGESTION Chapter 8: LMTL statistics
LMTP_REMOTE_SL_CONGESTION
Description
Pegging
This statistic pegs each time the remote congestion timer expires.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number
of occurrences of excessive congestion duration at the remote Signalling Link (SL) that
are acceptable in normal system operations.
If the specified threshold is exceeded, the 4. LMTL: SL failure - excessive duration of
congestion - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling
at the OMC-R (68P02901W26) for troubleshooting information.
8-26 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LMTP_SL_ERROR_RATE
LMTP_SL_ERROR_RATE
Description
The LMTP_SL_ERROR_RATE statistic tracks the number of times that an Lb-interface Signalling Link
(SL) is lost due to the expiration of the Signal Unit Error Rate Monitor (SUERM) timer.
Pegging
This statistic pegs each time the Lb-interface SL is lost due to the SUERM timer expiration.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of times an SL may
be lost due to SUERM timer expirations that are acceptable in normal system operations.
If the specified threshold is exceeded, the 3. LMTL: SL failure - excessive error rate
- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
TU-TSS Q.703 - (102).
Usage MTP C7 performance.
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Major.
68P02901W56-Q 8-27
24 May 2004 CONTROLLED INTRODUCTION
LMTP_SL_FAIL Chapter 8: LMTL statistics
LMTP_SL_FAIL
Description
The LMTP_SL_FAIL statistic tracks the Lb-interface Signalling Link (SL) failure for all
causes except operator interaction through the MMI.
Pegging
This statistic is pegged when an Lb-interface SL fails for any reason except operator
interaction through the MMI.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of SL failures, excluding
those caused by operator interaction with the MMI, that are acceptable in normal system operations.
If the specified threshold is exceeded, the 0. LMTL: SL failure - all reasons - PM alarm
is generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R
(68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 performance.
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Major.
8-28 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LMTP_SL_FIBR
LMTP_SL_FIBR
Description
The LMTP_SL_FIBR statistic tracks the number of out-of-sequence messages between a BSC and the
BSS-based SMLC that result in an Lb-interface Signalling Link (SL) going out of service. This statistic
is similar to the LMTP_NEG_ACKS statistic, but signals a more severe condition.
Pegging
This statistic pegs when the SL is lost due to the detection of an abnormal Forward Indicator Bit (FIB) caused
by the de-synchronization of the Backward Sequence Number (BSN) and Forward Sequence Number (FSN).
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of times an SL may be
lost due to the detection of an abnormal FIB that are acceptable in normal system operations.
If the specified threshold is exceeded, the 1. LMTL: SL failure - abnormal FIBR/BSNR
- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
68P02901W56-Q 8-29
24 May 2004 CONTROLLED INTRODUCTION
LMTP_START_RPO Chapter 8: LMTL statistics
LMTP_START_RPO
Description
Pegging
This statistic is pegged each time the BSS is notified that the BSS-based SMLC has
experienced a processor outage.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of remote
processor outages that are acceptable in normal system operations.
If the specified threshold is exceeded, the 8. LMTL: Start of remote processor outage
- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 performance.
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Warning.
8-30 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LMTP_STOP_RPO
LMTP_STOP_RPO
Description
Pegging
This statistic pegs each time the remote processor outage stops.
Analysis
This statistic can be used for trend analysis of remote processor outage condition is no longer present.
68P02901W56-Q 8-31
24 May 2004 CONTROLLED INTRODUCTION
LMTP_SU_ERROR Chapter 8: LMTL statistics
LMTP_SU_ERROR
Description
The LMTP_SU_ERROR statistic tracks the number of times erroneous signal units are
received on the Lb-interface Signalling Link (SL).
Pegging
This statistic pegs each time an erroneous signal unit is received on the Lb-interface SS7 SL.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of times erroneous
signal units may be received on the SL that are acceptable in normal system operations.
If the specified threshold is exceeded, the 6. LMTL: Number of signal units in error
- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 performance.
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Warning.
8-32 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LMTP_UNAVAILABLE
LMTP_UNAVAILABLE
Description
The LMTP_UNAVAILABLE statistic tracks the total time an Lb-interface Signalling Link (SL)
is out of service for all reasons including operator intervention.
Pegging
This statistic records the duration of Lb-interface SL unavailability for all reasons,
including operator intervention through the MMI.
Analysis
This statistic can be used for trend analysis of the duration of SL outages, including
those caused by operator interaction.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 availability.
Fault finding.
Basis Lb SS7_LINK.
Type Duration (total time in milliseconds).
68P02901W56-Q 8-33
24 May 2004 CONTROLLED INTRODUCTION
LMTP_SIB_RX Chapter 8: LMTL statistics
LMTP_SIB_RX
Description
The LMTP_SIB_RX statistic tracks the number of Status Indication Busy LSSU messages
received over an Lb-interface Signalling Link (SL).
Pegging
This statistic is pegged each time the BSS receives a Status Indication Busy (SIB) LSSU
message across the Lb-interface signalling link.
Analysis
This statistic can be used for trend analysis.
8-34 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LMTP_CONGESTION
LMTP_CONGESTION
Description
The LMTP_CONGESTION statistic tracks the time the Lb-interface Signalling Link (SL) is congested.
Pegging
The timer for this statistic is started when congestion is detected on an Lb interface signalling
link. The timer is stopped when normal operation is resumed.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 utilization.
Network planning.
Fault finding.
Basis Lb SS7_Link.
Type Duration.
68P02901W56-Q 8-35
24 May 2004 CONTROLLED INTRODUCTION
LMTP_SIB_TX Chapter 8: LMTL statistics
LMTP_SIB_TX
Description
The LMTP_SIB_TX statistic tracks the number of Status Indication Busy LSSU messages
transmitted over an Lb-interface Signalling Link (SL).
Pegging
This statistic is pegged each time the BSS transmits a Status Indication Busy (SIB) LSSU
message across the Lb-interface signalling link.
Analysis
This statistic can be used for trend analysis.
8-36 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
9
BSS statistics for Location Services
support
BSS statistics for Location Services (LS) support are collected and used for the supported BSS LS. Existing
cell connection establishment statistics as described in Chapter 4, "Cell statistics," are pegged for location
services and specific LS events are captured using BSS LS statistics described in this chapter. These
subgroups are described in "BSS statistics for Location Services support subgroups" on page 9-2.
68P02901W56-Q 9-1
24 May 2004 CONTROLLED INTRODUCTION
BSS statistics for Location Services support subgroups Chapter 9: BSS statistics for Location Services support
BSS statistics for Location Services (LS) support are organized into the following subgroups:
• "Connection establishment" on page 9-2.
Connection establishment
Connection establishment statistics track access and channel request functions. The following statistics
are connection establishment statistics and are pegged for location services:
• "CHAN_REQ_CAUSE_ATMPT" on page 4-31.
Location service
9-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application BSS statistics for Location Services support subgroups
68P02901W56-Q 9-3
24 May 2004 CONTROLLED INTRODUCTION
BSSLAP_ABORT_RCV Chapter 9: BSS statistics for Location Services support
BSSLAP_ABORT_RCV
Description
The BSSLAP_ABORT_RCV statistic tracks the number of BSSLAP abort messages received.
Pegging
This statistic pegs each time a BSSLAP abort message is received.
9-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application BSSLAP_ABORT_SENT
BSSLAP_ABORT_SENT
Description
The BSSLAP_ABORT_SENT statistic tracks the number of BSSLAP abort messages sent.
Pegging
This statistic pegs each time a BSSLAP abort message is sent.
68P02901W56-Q 9-5
24 May 2004 CONTROLLED INTRODUCTION
BSSLAP_MS_POS_CMD Chapter 9: BSS statistics for Location Services support
BSSLAP_MS_POS_CMD
Description
Pegging
This statistic pegs each time a BSSLAP MS position command message is received.
9-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application BSSLAP_MS_POS_RESP
BSSLAP_MS_POS_RESP
Description
The BSSLAP_MS_POS_RESP statistic tracks the number of BSSLAP MS position response messages sent.
Pegging
This statistic pegs each time a BSSLAP MS position response message is sent.
68P02901W56-Q 9-7
24 May 2004 CONTROLLED INTRODUCTION
BSSLAP_REJ Chapter 9: BSS statistics for Location Services support
BSSLAP_REJ
Description
The BSSLAP_REJ statistic tracks the number of BSSLAP reject messages sent.
Pegging
This statistic pegs each time a BSSLAP reject message is sent.
9-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application BSSLAP_RESET
BSSLAP_RESET
Description
The BSSLAP_RESET statistic tracks the number of BSSLAP reset messages sent.
Pegging
This statistic pegs each time a BSSLAP reset message is sent.
68P02901W56-Q 9-9
24 May 2004 CONTROLLED INTRODUCTION
BSSLAP_TA_REQ Chapter 9: BSS statistics for Location Services support
BSSLAP_TA_REQ
Description
The BSSLAP_TA_REQ statistic tracks the number of BSSLAP TA request messages received.
Pegging
This statistic pegs each time a BSSLAP TA request message is received.
9-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application BSSLAP_TA_RESP
BSSLAP_TA_RESP
Description
The BSSLAP_TA_RESP statistic tracks the number of BSSLAP TA response messages sent.
Pegging
This statistic pegs each time a BSSLAP TA response message is sent.
68P02901W56-Q 9-11
24 May 2004 CONTROLLED INTRODUCTION
BSSLAP_TOA_REQ Chapter 9: BSS statistics for Location Services support
BSSLAP_TOA_REQ
Description
The BSSLAP_TOA_REQ statistic tracks the number of BSSLAP TOA request messages received.
Pegging
This statistic pegs each time a BSSLAP TOA request message is received.
9-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application BSSMAP_CONLESS_INFO_RCV
BSSMAP_CONLESS_INFO_RCV
Description
Pegging
This statistic pegs each time a BSSMAP connectionless information message is received.
68P02901W56-Q 9-13
24 May 2004 CONTROLLED INTRODUCTION
BSSMAP_CONLESS_INFO_SENT Chapter 9: BSS statistics for Location Services support
BSSMAP_CONLESS_INFO_SENT
Description
Pegging
This statistic pegs each time a BSSMAP connectionless information message is sent.
9-14 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application BSSMAP_PERF_LOC_ABORT_MSGS
BSSMAP_PERF_LOC_ABORT_MSGS
Description
Pegging
This statistic pegs each time a BSSMAP perform location abort message is received on the A-interface.
68P02901W56-Q 9-15
24 May 2004 CONTROLLED INTRODUCTION
BSSMAP_PERF_LOC_REQ_MSGS Chapter 9: BSS statistics for Location Services support
BSSMAP_PERF_LOC_REQ_MSGS
Description
Pegging
This statistic pegs each time a BSSMAP perform location request message is received on A-interface.
9-16 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application BSSMAP_PERF_LOC_RESP_MSGS
BSSMAP_PERF_LOC_RESP_MSGS
Description
Pegging
This statistic pegs each time a BSSMAP perform location response message is sent on A-interface.
68P02901W56-Q 9-17
24 May 2004 CONTROLLED INTRODUCTION
BSSMAPLE_CONLESS_INFO_RCV Chapter 9: BSS statistics for Location Services support
BSSMAPLE_CONLESS_INFO_RCV
Description
Pegging
This statistic pegs each time a BSSMAP-LE connectionless information message is received.
9-18 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application BSSMAPLE_CONLESS_INFO_SENT
BSSMAPLE_CONLESS_INFO_SENT
Description
Pegging
This statistic pegs each time a BSSMAP-LE connectionless information message is sent.
68P02901W56-Q 9-19
24 May 2004 CONTROLLED INTRODUCTION
BSSMAPLE_PERF_LOC_ABORT_MSGS Chapter 9: BSS statistics for Location Services support
BSSMAPLE_PERF_LOC_ABORT_MSGS
Description
Pegging
This statistic pegs each time a BSSMAP-LE perform location abort message is sent on Lb-interface.
Reference GSM 03.71 v7.4.0, sect 7.11GSM 09.31 v7.1.0, sect 9.3.
Usage MTP C7 utilization.
Fault finding.
Basis BSS.
Type Counter.
9-20 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application BSSMAPLE_PERF_LOC_REQ_MSGS
BSSMAPLE_PERF_LOC_REQ_MSGS
Description
Pegging
This statistic pegs each time a BSSMAP-LE perform location request message is sent on Lb-interface.
Reference GSM 03.71 v7.4.0, sect 7.5, 7.6, 7.7, 7.11, 8.1GSM 09.31 v7.1.0,
sect 9.1.
Usage MTP C7 utilization.
Fault finding.
Basis BSS.
Type Counter.
68P02901W56-Q 9-21
24 May 2004 CONTROLLED INTRODUCTION
BSSMAPLE_PERF_LOC_RESP_MSGS Chapter 9: BSS statistics for Location Services support
BSSMAPLE_PERF_LOC_RESP_MSGS
Description
Pegging
This statistic pegs each time a BSSMAP-LE perform location response message
is received on the Lb-interface.
Reference GSM 03.71 v7.4.0, sect. 7.6, 7.7, 7.11.
GSM 09.31 v7.1.0, sect. 9.2
Usage MTP C7 utilization.
Fault finding.
Basis BSS.
Type Counter.
9-22 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
10
MTL statistics
Message Transfer Link (MTL) statistics are used to track events for the Message Transfer Part (MTP)
of the ITU-TSS No. 7 protocol on the BSC to MSC interface. They are categorized into subgroups,
each of which are described in "MTL statistics subgroups" on page 10-2.
68P02901W56-Q 10-1
24 May 2004 CONTROLLED INTRODUCTION
MTL statistics subgroups Chapter 10: MTL statistics
MTP C7 availability
MTP C7 availability statistics are used to track the duration of signalling link outages and
inhibitions (local and remote) for the MTP of the ITU-TSS No.7 protocol on the BSC to MSC
interface. The following are the MTP C7 availability statistics:
• "MTP_LINKFAIL" on page 10-12.
MTP C7 performance
MTP C7 performance statistics are used track the different types of failure and recovery
situations for the MTP of the ITU-TSS No.7 protocol on the BSC to MSC interface. The
following are the MTP C7 performance statistics:
• "MTP_CHANGEBACK" on page 10-8.
10-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTL statistics subgroups
MTP C7 utilization
MTP C7 utilization statistics are used to track the number of messages received, transmitted and retransmitted
on signalling links and supply information on signalling link congestion for the MTP of the ITU-TSS No.7
protocol on the BSC to MSC interface. The following are the MTP C7 utilization statistics:
• "BUSY_CICS" on page 10-4.
68P02901W56-Q 10-3
24 May 2004 CONTROLLED INTRODUCTION
BUSY_CICS Chapter 10: MTL statistics
BUSY_CICS
Description
The BUSY_CICS statistic tracks the number of BUSY CICS during an interval. This weighted distribution
statistics produces a mean value indicating the average number of CICs in use during the interval.
The bin ranges may be changed using the chg_stat_prop command.
The default bin ranges for the BUSY_CICS statistic are:
Bin Range
0 0 to 9
1 10 to 49
2 50 to 99
3 100 to 199
4 200 to 399
5 400 to 799
6 800 to 1199
7 1200 to 1599
8 1600 to 2199
9 2200 to 3200
Pegging
This statistic is pegged each time an allocation or deallocation of a CIC is detected. It is an
indication of the amount of active calls under the MSC.
The individual bins values are incremented by the length of time that the number of
allocated CICs fall within the bin ranges.
10-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application BUSY_CICS
Analysis
Since each call is routed via the MSC (even intra-BSS and intra-cell), the number of CICs represent
the number of calls in progress under that MSC for this BSS.
Reference None.
Usage Quality of service monitoring.
Network planning.
Optimization.
Basis BSS.
Type Weighted distribution.
68P02901W56-Q 10-5
24 May 2004 CONTROLLED INTRODUCTION
CONGESTION_LOST_MSU Chapter 10: MTL statistics
CONGESTION_LOST_MSU
Description
The CONGESTION_LOST_MSU statistic tracks the number of times Message Signalling Units
(MSU) are being lost due to Signalling Link (SL) congestion.
Pegging
This statistic pegs for each congestion event which results in MSUs being lost.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of lost
MSUs due to SL congestion that are acceptable in normal system operations.
If the specified threshold is exceeded, the 11. MTL: SL congestion events resulting in loss
of MSUs - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling
at the OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 utilization.
Fault finding.
Basis SS7_LINK.
Type Counter.
Alarm Warning.
10-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MSU_DISCARDED
MSU_DISCARDED
Description
The MSU_DISCARDED statistic tracks the number of MSUs discarded while there
is congestion on the Signalling Link (SL).
Pegging
This statistic pegs each time a MSU is discarded while there is congestion on the SL.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of MSUs are
being discarded due to SL congestion that are acceptable in normal system operations.
If the specified threshold is exceeded, the 10. MTL: MSUs discarded due to SL congestion
- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 utilization.
Network planning.
Fault finding.
Basis SS7_LINK.
Type Counter.
Alarm Warning.
68P02901W56-Q 10-7
24 May 2004 CONTROLLED INTRODUCTION
MTP_CHANGEBACK Chapter 10: MTL statistics
MTP_CHANGEBACK
Description
Pegging
This statistic pegs when MTP traffic that has been changed over to an alternate Signalling
Link (SL) is diverted back to the original SL.
Analysis
This statistic can be used for trend analysis of automatic changebacks that have been successfully completed.
10-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTP_CHANGEOVER
MTP_CHANGEOVER
Description
The MTP_CHANGEOVER statistic tracks the number of local automatic changeovers that have
been successfully completed. This indicates MTP traffic is being transferred from a Signalling
Link (SL) that is going out of service to an alternate SL.
Pegging
This statistic pegs when MTP traffic is changed over to an alternate SL.
Analysis
This statistic can be used for trend analysis of local automatic changeovers that
have been successfully completed.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 performance.
Fault finding.
Basis SS7_LINK.
Type Counter.
68P02901W56-Q 10-9
24 May 2004 CONTROLLED INTRODUCTION
MTP_CONGESTION Chapter 10: MTL statistics
MTP_CONGESTION
Description
The MTP_CONGESTION statistic tracks the length of time that a signalling link is congested.
This can be used to indicate signalling link congestion.
Pegging
The timer for this statistic is started when congestion is detected on a signalling link. The
timer is stopped when normal operation is resumed.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 utilization.
Network planning.
Fault finding.
Basis SS7_LINK.
Type Duration (total time in milliseconds).
10-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTP_LINK_INS
MTP_LINK_INS
Description
The MTP_LINK_INS statistic tracks the length of time that a signalling link (SL) is in the in-service state.
Pegging
The timer for this statistic is started when an SL is brought into service. The timer is
stopped when the SL is removed from service.
Analysis
This statistic can be used for trend analysis of the utilization of in-service SLs.
68P02901W56-Q 10-11
24 May 2004 CONTROLLED INTRODUCTION
MTP_LINKFAIL Chapter 10: MTL statistics
MTP_LINKFAIL
Description
The MTP_LINKFAIL statistic tracks the duration of Signalling Link (SL) unavailability due to SL
failure. It records the total time a particular SL is out of service while trying to align.
Pegging
This statistic pegs each time the SL tries to align with the A interface while it is out of service. The
statistic timer is started when the SL fails. It is stopped when the SL comes back into service.
Analysis
This statistic can be used for analysis of SL unavailability due to SL failure.
10-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTP_LOCAL_BUSY
MTP_LOCAL_BUSY
Description
Pegging
This statistic is started when congestion is detected on an SL. The statistic is stopped
when normal operation is resumed.
Analysis
This statistic can be used for trend analysis on congestion durations on the local end of the SL.
68P02901W56-Q 10-13
24 May 2004 CONTROLLED INTRODUCTION
MTP_LOCAL_MGT Chapter 10: MTL statistics
MTP_LOCAL_MGT
Description
The MTP_LOCAL_MGT statistic tracks the total time that a local Signalling Link (SL)
is inhibited due to local management actions.
Pegging
This statistic is started each time the SL is inhibited due to local management actions
and stopped when the link is enabled.
Analysis
This statistic can be used for trend analysis on inhibited local SLs due to local management action.
10-14 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTP_MGT_INHIBIT
MTP_MGT_INHIBIT
Description
The MTP_MGT_INHIBIT statistic tracks the number of times the Signalling Link (SL) is
inhibited using the shutdown command on the MTP link.
Pegging
This statistic is started each time the SL is inhibited by the user entering the shutdown
command on the associated MTP link.
Analysis
This statistic can be used for trend analysis on inhibited SLs using the shutdown
command on the associated MTP link.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 availability.
Basis SS7_LINK.
Type Counter.
68P02901W56-Q 10-15
24 May 2004 CONTROLLED INTRODUCTION
MTP_MGT_UNINHIBIT Chapter 10: MTL statistics
MTP_MGT_UNINHIBIT
Description
The MTP_MGT_UNINHIBIT statistic tracks the number of times the Signalling Link (SL)
is uninhibited using the unlock command on the MTP link.
Pegging
This statistic is started each time the SL is uninhibited using the unlock command on
an SL that was previously inhibited.
Analysis
This statistic can be used for trend analysis on uninhibited SLs using the unlock
command on the associated MTP link.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 availability.
Basis SS7_LINK.
Type Counter.
10-16 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTP_MSU_RX
MTP_MSU_RX
Description
The MTP_MSU_RX statistic tracks the number of Message Signal Units (MSUs)
received on a particular signalling link.
Pegging
This statistic pegs each time MSUs are received over the signalling link.
68P02901W56-Q 10-17
24 May 2004 CONTROLLED INTRODUCTION
MTP_MSU_TX Chapter 10: MTL statistics
MTP_MSU_TX
Description
The MTP_MSU_TX statistic tracks the number of Message Signal Units (MSUs)
transmitted on a particular signalling link.
Pegging
This statistic pegs each time MSUs are transmitted over the signalling link.
10-18 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTP_NEG_ACKS
MTP_NEG_ACKS
Description
The MTP_NEG_ACKS statistic tracks when the messages between a BSS and an MSC get out of sequence.
Pegging
This statistic pegs when the BSS detects out of order messages to the MSC and request retransmission.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of out of sequence
messages between a BSS and a MSC that are acceptable in normal system operations.
If the specified threshold is exceeded, the 7. MTL: SL number of negative acks received
- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
68P02901W56-Q 10-19
24 May 2004 CONTROLLED INTRODUCTION
MTP_RE_TX Chapter 10: MTL statistics
MTP_RE_TX
Description
The MTP_RE_TX statistic tracks the number of octets that the BSS has retransmitted to the MSC
because the MSC has requested retransmission. This indicates how much the BSS and an MSC
are off in message sequencing by the number of octets retransmitted.
Pegging
This statistic pegs the number of octets retransmitted by the BSS to the MSC.
10-20 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTP_REMOTE_MGT
MTP_REMOTE_MGT
Description
The MTP_REMOTE_MGT statistic tracks the total time a Signalling Link (SL) was remotely inhibited.
Pegging
This statistic pegs the duration of the SL inhibition due to remote management action until uninhibited.
Analysis
This statistic can be used for trend analysis of remote management SL inhibition actions.
68P02901W56-Q 10-21
24 May 2004 CONTROLLED INTRODUCTION
MTP_REMOTE_PROC Chapter 10: MTL statistics
MTP_REMOTE_PROC
Description
The MTP_REMOTE_PROC statistic tracks the time that a remote processor is out of service.
Pegging
This statistic pegs when a remote processor outage is identified and stopped when the
processor outage condition ceases.
Analysis
This statistic can be used for trend analysis of remote processor outages.
10-22 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTP_RESTORATION
MTP_RESTORATION
Description
The MTP_RESTORATION statistic tracks the number of times user traffic is allowed on a Signalling Link
(SL) that is in service and not inhibited. This statistic does not track recovery from link fail.
Pegging
This statistic pegs when the SL starts carrying user traffic. This happens when the SL comes into
service, is uninhibited, or recovers from a remote processor outage.
Analysis
This statistic can be used for trend analysis of used traffic being allowed on an SL.
68P02901W56-Q 10-23
24 May 2004 CONTROLLED INTRODUCTION
MTP_SIF_SIO_RX Chapter 10: MTL statistics
MTP_SIF_SIO_RX
Description
The MTP_SIF_SIO_RX statistic tracks the number of Signal Information Fields (SIF) or Service
Information Octets (SIO) that are received over a signalling link.
Pegging
This statistic pegs each time an SIF or SIO is received over the signalling link.
10-24 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTP_SIF_SIO_TX
MTP_SIF_SIO_TX
Description
The MTP_SIF_SIO_TX statistic tracks the number of Signal Information Fields (SIF) or Service
Information Octets (SIO) that are transmitted over a signalling link.
Pegging
This statistic pegs each time an SIF or SIO are transmitted over the signalling link.
68P02901W56-Q 10-25
24 May 2004 CONTROLLED INTRODUCTION
MTP_SL_ACK Chapter 10: MTL statistics
MTP_SL_ACK
Description
The MTP_SL_ACK statistic tracks the number of times that the link was lost because a timer expired
due to an acknowledgement that a Message Signal Unit (MSU) was not sent.
Pegging
This statistic pegs each time the link is lost due to a timer that expires when an
acknowledgement of an MSU is not sent.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of
acknowledgements of MSUs not being sent that are acceptable in normal system operations.
If the specified threshold is exceeded, the 2. MTL: SL failure - excessive delay of ACK -
PM alarm will be generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 performance.
Basis SS7_LINK.
Type Counter.
Alarm Major.
10-26 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTP_SL_ALIGNMENT
MTP_SL_ALIGNMENT
Description
Pegging
This statistic pegs each time an out of service SL unsuccessfully tries to align with the A interface.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of unsuccessful
attempts to align an out of service SL to the A interface that are acceptable in normal system operations.
If the specified threshold is exceeded, the 5. MTL: SL alignment failure - PM alarm is generated. Refer to the
Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) for troubleshooting information.
68P02901W56-Q 10-27
24 May 2004 CONTROLLED INTRODUCTION
MTP_SL_CONGESTION Chapter 10: MTL statistics
MTP_SL_CONGESTION
Description
The MTP_SL_CONGESTION statistic tracks the number of times the remote site is congested.
Pegging
This statistic pegs each time the remote congestion timer expires.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of occurrences of
excessive congestion duration at the remote that are acceptable in normal system operations.
If the specified threshold is exceeded, the 4. MTL: SL failure - excessive duration of
congestion - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling
at the OMC-R (68P02901W26) for troubleshooting information.
10-28 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTP_SL_ERROR_RATE
MTP_SL_ERROR_RATE
Description
The MTP_SL_ERROR_RATE statistic tracks the number of times that a Signalling Link (SL) is lost
due to the expiration of the Signal Unit Error Rate Monitor (SUERM) timer.
Pegging
This statistic pegs each time the SL is lost due to the SUERM timer expiration. (Refer
to ITU-TSS specification Q. 703, Section 102.)
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of times an SL may
be lost due to SUERM timer expirations that are acceptable in normal system operations.
If the specified threshold is exceeded, the 3. MTL: SL failure - excessive error rate - PM
alarm is generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R
(68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 performance.
Fault finding.
Basis SS7_LINK.
Type Counter.
Alarm Major.
68P02901W56-Q 10-29
24 May 2004 CONTROLLED INTRODUCTION
MTP_SL_FAIL Chapter 10: MTL statistics
MTP_SL_FAIL
Description
The MTP_SL_FAIL statistic tracks Signalling Link (SL) failure for all causes except
operator interaction through the MMI.
Pegging
This statistic pegs when an SL fails for any reason except operator interaction through the MMI.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of SL failures, excluding
those caused by operator interaction with the MMI, that are acceptable in normal system operations.
If the specified threshold is exceeded, the 0. MTL: SL failure - all reasons - PM alarm
is generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R
(68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 performance.
Fault finding.
Basis SS7_LINK.
Type Counter.
Alarm Major.
10-30 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTP_SL_FIBR
MTP_SL_FIBR
Description
The MTP_SL_FIBR statistic tracks the messages between a BSS and a remote site are out of
sequence, causing the Signalling Link (SL) to go out of service. This statistic is similar to the
MTP_NEG_ACKS statistic but signals a more severe condition.
Pegging
This statistic pegs when the SL is lost due to the detection of an abnormal Forward Indicator Bit (FIB) caused
by the de-synchronization of the Backward Sequence Number (BSN) and Forward Sequence Number (FSN).
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of times an SL may be
lost due to the detection of an abnormal FIB that are acceptable in normal system operations.
If the specified threshold is exceeded, the 1. MTL: SL failure - abnormal FIBR/BSNR
- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
68P02901W56-Q 10-31
24 May 2004 CONTROLLED INTRODUCTION
MTP_START_RPO Chapter 10: MTL statistics
MTP_START_RPO
Description
The MTP_START_PRO statistic tracks the number of times a remote processor outage occurs.
Pegging
This statistic pegs each time a remote processor outage condition is identified.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of remote
processor outages that are acceptable in normal system operations.
If the specified threshold is exceeded, the 8. MTL: Start of remote processor outage
- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
10-32 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTP_STOP_RPO
MTP_STOP_RPO
Description
The MTP_STOP_RPO statistic tracks the number of times a remote processor outage condition stops.
Pegging
This statistic pegs each time the remote processor outage stops.
Analysis
This statistic can be used for trend analysis of remote processor outages and restoration.
68P02901W56-Q 10-33
24 May 2004 CONTROLLED INTRODUCTION
MTP_SU_ERROR Chapter 10: MTL statistics
MTP_SU_ERROR
Description
The MTP_SU_ERROR statistic tracks the number of times erroneous signal units
are received on the Signalling Link (SL).
Pegging
This statistic pegs each time an erroneous signal unit is received on the SL.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of times erroneous
signal units may be received on the SL that are acceptable in normal system operations.
If the specified threshold is exceeded, the 6. MTL: Number of signal units in error - PM
alarm is generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R
(68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 performance.
Fault finding.
Basis SS7_LINK.
Type Counter.
Alarm Warning.
10-34 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTP_UNAVAILABLE
MTP_UNAVAILABLE
Description
The MTP_UNAVAILABLE statistic tracks the total time a Signalling Link (SL) is out of
service for all reasons including operator intervention.
Pegging
This statistic records the duration of SL unavailability for all reasons, including
operator intervention through the MMI.
Analysis
This statistic can be used for trend analysis of the duration of SL outages, including
those caused by operator interaction.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 availability.
Fault finding.
Basis SS7_LINK.
Type Duration (total time in milliseconds).
68P02901W56-Q 10-35
24 May 2004 CONTROLLED INTRODUCTION
SIB_RX Chapter 10: MTL statistics
SIB_RX
Description
The SIB_RX statistic provides a means of calculating MTL utilization by counting the number
of Status Indication Busy LSSU messages received.
Pegging
This statistic pegs each receipt of a Status Indication Busy (SIB) LSSU message on a per signalling link basis.
Analysis
This statistic can be used for trend analysis.
10-36 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SIB_TX
SIB_TX
Description
The SIB_TX statistic provides a means of calculating MTL utilization by counting the number
of Status Indication Busy LSSU messages transmitted.
Pegging
This statistic pegs each transmission of a Status Indication Busy (SIB) LSSU message
on a per signalling link basis.
Analysis
This statistic can be used for trend analysis.
68P02901W56-Q 10-37
24 May 2004 CONTROLLED INTRODUCTION
SL_CONGESTION Chapter 10: MTL statistics
SL_CONGESTION
Description
The SL_CONGESTION statistic tracks the number of times the remote congestion timer expires
due to excessive duration on a Signalling Link (SL) failure.
Pegging
This statistic pegs each time the remote congestion timer expires due to excessive
duration of congestion on an SL failure.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of remote
congestion timer expirations that are acceptable in normal system operations.
If the specified threshold is exceeded, the 4. MTL: SL failure - excessive duration of
congestion - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling
at the OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 utilization.
Network planning.
Fault finding.
Basis SS7_Link.
Type Counter.
Alarm Warning.
10-38 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SL_STOP_CONGESTION
SL_STOP_CONGESTION
Description
Pegging
This statistic is pegged each time the signalling link congestion indication stops.
68P02901W56-Q 10-39
24 May 2004 CONTROLLED INTRODUCTION
SL_STOP_CONGESTION Chapter 10: MTL statistics
10-40 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
11
CBL, GSL, OML, RSL and XBL statistics
X.25/LAPD statistics included here, are used to track BSS data transmission information.
These statistics relate to events on the following links:
• Cell Broadcast Link (CBL).
68P02901W56-Q 11-1
24 May 2004 CONTROLLED INTRODUCTION
X.25/LAPD Level: X.25 and LAPD statistics Chapter 11: CBL, GSL, OML, RSL and XBL statistics
X.25 and LAPD statistics are used to track BSS data transmission information. The
following are the X.25 and LAPD statistics:
• "ATER_CHANNEL_STATUS" on page 11-3.
11-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application ATER_CHANNEL_STATUS
ATER_CHANNEL_STATUS
Description
The ATER_CHANNEL_STATUS statistic tracks the Ater channel status on a per XBL linkset basis.
Pegging
This statistic pegs the number of events relating to ATER allocation and assignment
scenarios on a per XBL linkset basis.
Reference None.
Usage Network planning.
Fault finding.
Quality of service monitoring.
68P02901W56-Q 11-3
24 May 2004 CONTROLLED INTRODUCTION
ATER_CHANNEL_STATUS Chapter 11: CBL, GSL, OML, RSL and XBL statistics
Basis AXCDR.
Type Large counter array.
11-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application ATER_EMERG_PREEMPT_STATUS
ATER_EMERG_PREEMPT_STATUS
Description
Pegging
Counts the number of events relating to ATER pre-emption for emergency call sce-
narios on a per XBL linkset basis.
Reference None.
Usage Network planning, Optimization.
Quality of service monitoring.
Basis AXCDR
Type Small counter array.
68P02901W56-Q 11-5
24 May 2004 CONTROLLED INTRODUCTION
FRMR Chapter 11: CBL, GSL, OML, RSL and XBL statistics
FRMR
Description
The FRMR statistic tracks the number of frames that were rejected because the frames were not recoverable.
Pegging
This statistic pegs each time a frame is received that is not recoverable.
11-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application I_FRAMES_RX
I_FRAMES_RX
Description
The I_FRAMES_RX statistic tracks the number of Information Frames (I-Frames) received.
Pegging
This statistic pegs when an I-Frame is received.
68P02901W56-Q 11-7
24 May 2004 CONTROLLED INTRODUCTION
I_FRAMES_TX Chapter 11: CBL, GSL, OML, RSL and XBL statistics
I_FRAMES_TX
Description
The I_FRAMES_TX statistic tracks the number of Information Frames (I-Frames) transmitted.
Pegging
This statistic peg when an I-Frame is transmitted.
11-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application INVALID_FRAMES_RX
INVALID_FRAMES_RX
Description
Pegging
This statistic is pegged whenever an invalid frame is received.
• X.25
On the OML (BSS-OMC-R).
• LAPD
On the RSL (BSS-BTS link).
68P02901W56-Q 11-9
24 May 2004 CONTROLLED INTRODUCTION
LAPD_CONGESTION Chapter 11: CBL, GSL, OML, RSL and XBL statistics
LAPD_CONGESTION
Description
The LAPD_CONGESTION statistic tracks the time that the LAPD or X.25 link is congested. This
indicates the time period in milliseconds when the sending speed of the BSC/BTS processes is more than
the link transmit capability and provides a way of monitoring when more links need to be added.
The exec-dlsp process has a bigger buffer to hold outgoing messages therefore the
messages will not get dropped even during the congestion period.
Pegging
This statistic pegs when the transmit buffer gets full and stops when the buffer is available again.
11-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application N2_EXPIRY
N2_EXPIRY
Description
The N2_EXPIRY statistic tracks the number of link alignment retries attempted without success.
Pegging
This statistic pegs when the retry count threshold has been exceeded.
68P02901W56-Q 11-11
24 May 2004 CONTROLLED INTRODUCTION
SABM_TX Chapter 11: CBL, GSL, OML, RSL and XBL statistics
SABM_TX
Description
The SABM_TX statistic tracks the links that come into service.
Pegging
This statistic is pegged for all Set Asynchronous Balanced Mode (SABM) frames.
11-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
12
PCU statistics
PCU statistics are captured from events occurring at the Packet Control Unit (PCU). They are categorized
into subgroups, each of which are described in "PCU statistics subgroups" on page 12-2.
68P02901W56-Q 12-1
24 May 2004 CONTROLLED INTRODUCTION
PCU statistics subgroups Chapter 12: PCU statistics
GBL statistics
The GBL device refers to the configured number of timeslots on an E1 link between the PCU and the Serving
GPRS Support Node (SGSN). This interface is referred to as the Gb interface. The Gb interface allows many
users to be multiplexed over a common physical resource. GPRS signalling and user data are sent on the same
physical resource, that is, no dedicated physical resources are required to be allocated for signalling purposes.
The GBL measurement types are listed as follows:
• "CELL_FLUSH_REQS" on page 12-15
Accessibility statistics
Accessibility statistics measure how effectively GPRS resources are being accessed. These measurements
assist the operator in planning the necessary resources needed for the MS to efficiently access the network.
The accessibility statistics include the following:
• {4441}"CH_REQ_UNSVCD_PCU" on page 12-16
12-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application PCU statistics subgroups
68P02901W56-Q 12-3
24 May 2004 CONTROLLED INTRODUCTION
PCU statistics subgroups Chapter 12: PCU statistics
Throughput statistics
12-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application PCU statistics subgroups
68P02901W56-Q 12-5
24 May 2004 CONTROLLED INTRODUCTION
PCU statistics subgroups Chapter 12: PCU statistics
12-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application AIR_DL_CONTROL_BLKS
AIR_DL_CONTROL_BLKS
Description
The AIR_DL_CONTROL_BLKS statistic tracks the number of downlink control Radio Link Control
(RLC) blocks sent by the Packet Control Unit (PCU). Examples for downlink control blocks are:
• Packet Uplink ACK/NACK.
Pegging
This statistic is pegged for each control block sent down.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Analysis
This statistic can be used for the trend analysis of the number of Radio Link Control blocks sent by the PCU.
Reference None.
Usage Performance management.
Basis Cell.
Type Counter.
68P02901W56-Q 12-7
24 May 2004 CONTROLLED INTRODUCTION
AIR_DL_DATA_BLKS Chapter 12: PCU statistics
AIR_DL_DATA_BLKS
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
The AIR_DL_DATA_BLKS statistic tracks the number of blocks sent by the PCU to the MS for
each quality of service (QoS) level and coding scheme combination.
QoS identifies how delay sensitive the traffic is. Currently only QoS3 is implemented which
is the most delay insensitive traffic class - it is defined as Best Effort.
The bins are defined in Table 12-1.
12-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application AIR_DL_DATA_BLKS
Pegging
The appropriate bin is incremented by the amount of data blocks sent by the PCU to the MS for the
quality of service and coding scheme. Each count is rounded to the nearest 100 blocks.
Reference None.
Usage Network planning.
Basis Cell.
Type Counter array.
68P02901W56-Q 12-9
24 May 2004 CONTROLLED INTRODUCTION
AIR_DL_TBF_FAILURES Chapter 12: PCU statistics
AIR_DL_TBF_FAILURES
{4445}
Description
The AIR_DL_TBF_FAILURES statistic tracks the total number of downlink Temporary Block Flow (TBF)
that are abnormally released in the different phases (identified in the bins) due to radio failures in a cell.
Bin Description
0 Establishment.
1 Data transfer.
2 Delayed TBF release mode.
3 Termination.
Pegging
This statistic pegs each time a downlink TBF is established and later abnormally released due to
radio failures in a cell during a statistical measurement interval. The statistic pegs the appropriate
bin depending on the phase where the TBF was abnormally released.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Reference None
Usage Performance management
Basis Cell.
Type Counter array statistic.
12-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application AIR_UL_CONTROL_BLKS
AIR_UL_CONTROL_BLKS
Description
The AIR_UL_CONTROL_BLKS statistic tracks the number of uplink control Radio Link Control
(RLC) blocks received by the PCU. Examples for Uplink control blocks are:
• Packet Downlink ACK/NACK.
Pegging
This statistic is pegged for each control block the network receives from the MS.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Analysis
This statistic can be used for the trend analysis of Radio Link Control blocks sent by the MS.
Reference None.
Usage Performance management.
Basis Cell.
Type Counter.
68P02901W56-Q 12-11
24 May 2004 CONTROLLED INTRODUCTION
AIR_UL_DATA_BLKS Chapter 12: PCU statistics
AIR_UL_DATA_BLKS
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
The AIR_UL_DATA_BLKS statistic tracks the number of data blocks received by the PCU for
each quality of service level and coding scheme combination.
QoS identifies how delay sensitive the traffic is. Currently only QoS3 is implemented which
is the most delay insensitive traffic class - it is defined as Best Effort.
The bins are defined in Table 12-2.
12-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application AIR_UL_DATA_BLKS
Pegging
The appropriate bin is incremented by the amount of data blocks received for the quality of service
and coding scheme. The count is rounded to the nearest 100 blocks.
Reference None.
Usage Network planning.
Basis Cell.
Type Counter array.
68P02901W56-Q 12-13
24 May 2004 CONTROLLED INTRODUCTION
AIR_UL_TBF_FAILURES Chapter 12: PCU statistics
AIR_UL_TBF_FAILURES
{4445}
Description
The AIR_UL_TBF_FAILURES statistic tracks the total number of uplink Temporary Block Flow (TBF) that
are abnormally released in the different phases (identified in the bins) due to radio failures in a cell.
Bin Description
0 Establishment.
1 Data transfer.
2 Termination.
Pegging
This statistic pegs each time that an uplink TBF is established and later abnormally released due to
radio failures in a cell during a statistical measurement interval. The statistic pegs the appropriate
bin depending on the phase where the TBF was abnormally released.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Reference None
Usage Performance management
Basis Cell.
Type Counter array statistic.
12-14 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CELL_FLUSH_REQS
CELL_FLUSH_REQS
Description
The CELL_FLUSH_REQS statistic tracks the number of flush requests received on the GBL(s) per cell basis.
Pegging
This statistic is pegged each time a flush request is received on the GBL to flush the Logical
Link Control (LLC) Protocol Data Unit (PDU) for a particular MS.
Analysis
This statistic can be used for the trend analysis of the number of flush messages received by the BSS.
Reference None.
Usage Network planning.
Congestion.
Basis Cell
Type Counter.
68P02901W56-Q 12-15
24 May 2004 CONTROLLED INTRODUCTION
CH_REQ_UNSVCD_PCU Chapter 12: PCU statistics
CH_REQ_UNSVCD_PCU
{4441}
Description
This statistic represents the major reasons for not servicing GPRS channel requests at the PCU. Minor
condition scenarios, such as the channel request being received in a wrong MS/TBF state due to system race
conditions, and various system delays are minimal and are not covered in any of the bins above.
Pegging
This statistic is pegged for each channel request unserviced by the PCU.
{23658} This statistic is pegged for both GPRS and EGPRS events.
12-16 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CH_REQ_UNSVCD_PCU
Analysis
This statistic can be used for the trend analysis of the PCU.
Reference None.
Usage Performance management.
Basis Cell.
Type Counter array.
68P02901W56-Q 12-17
24 May 2004 CONTROLLED INTRODUCTION
CHANNEL_REQS_REC Chapter 12: PCU statistics
CHANNEL_REQS_REC
Description
Bin Description
0 A GPRS One-Phase access channel request is received.
1 {3723} A GPRS One-Phase access packet channel request on PCCCH is received.
2 A GPRS single block allocation on CCCH is received.
3 {3723}A GPRS single block allocation on PCCCH is received.
4 A GPRS Packet Resource Request (PRR) message is received (second phase of two
phase access).
5 A GPRS Channel Request in Packet Downlink ACK/NACK (PDAK) message is received.
6 An Enhanced One-Phase (EOP) access indication is received.
7 {23658} EGPRS One-Phase access on CCCH is received.
8 {23658} An EGPRS One-Phase access on PCCCH is received.
9 {23658} An EGPRS Single Block Allocation on CCCH is received
10 {23658} {3723} An EGPRS Single Block Allocation on PCCCH is received.
11 {23658} An EGPRS Packet Resource Request is received.
12 {23658} An EGPRS Channel Request in Packet Downlink ACK/NACK (PDAK) message
is received.
Pegging
This statistic pegs for each channel request message received. The bin that is incremented
is determined by the channel request message type.
Reference None.
Usage Network planning.
Basis Cell.
Type Extra large counter array.
12-18 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CHANNEL_REQS_REJECT
CHANNEL_REQS_REJECT
Description
The CHANNEL_REQS_REJECT statistic tracks the number of rejections by the PCU for packet channel
or resource requests. The PCU rejects such requests because the resources are unavailable.
Pegging
This statistic pegs when a Packet Access Reject message is sent to the MS in response to a
UL Request in PDAK or to a Packet Resource Request (two-phase access) when there are no
resources left to allocate. No retransmissions are pegged.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Reference None.
Usage Network planning.
Congestion.
Basis Cell.
Type Counter.
68P02901W56-Q 12-19
24 May 2004 CONTROLLED INTRODUCTION
CHANNEL_REQS_SUCCESS Chapter 12: PCU statistics
CHANNEL_REQS_SUCCESS
Description
This statistic counts the number of channel or resource requests that are actually
allocated a TBF resource successfully.
This statistic specifically counts the number of ASSIGNMENT messages sent to the
MS. Re-transmissions are excluded.
Bin Description
0 A GPRS One-Phase Access Packet Immediate Assignment (PIA) is sent on CCCH.
1 {3723} A GPRS One-Phase Access Packet Uplink Assignment (PUA) is sent on PCCCH.
2 A GPRS Single Block Allocation PIA is sent on CCCH.
3 {3723} A GPRS Single Block Allocation PUA is sent on CCCH.
4 A GPRS PUA (in response to Packet Resource Request) is sent to establish a TBF (only
the first PUA is counted).
5 A GPRS Packet Timeslot Reconfiguration (PTR) is sent to establish a new TBF or to
re-assign the downlink TBF (only the first PTR is counted).
6 An Enhanced One-Phase (EOP) Access indication is received on CCCH.
7 {3723} A GPRS PUA in response to a “channel request” received in a Packet Downlink
ACK.
8 {23658} An EOP Access PIA is sent on CCCH.
9 {23658} An EOP access PUA is sent on PCCCH.
10 {23658} {3723} An EGPRS Single Block Allocation PIA is sent on CCCH.
11 {23658} An EGPRS Single Block Allocation PUA is sent on PCCCH.
12 {23658} An EGPRS PUA (in response to Packet Resource Request (PRR)) is sent to
establish a TBF (only the first PUA is counted).
13 {23658} An EGPRS PTR is sent to establish a new TBF or to re-assign the downlink TBF
(only the first PTR is counted)..
14 {23658} An EGPRS PUA in response to a “channel request” in a PDAK.
Pegging
This statistic pegs for each channel request message granted on the downlink. The bin that is incremented
is determined by the channel request message type. Retransmissions are not pegged.
12-20 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CHANNEL_REQS_SUCCESS
Analysis
The statistic can be used for the trend analysis of the number of successful uplink
GPRS calls made by a particular CELL.
68P02901W56-Q 12-21
24 May 2004 CONTROLLED INTRODUCTION
CODING_SCHEME_CHANGE Chapter 12: PCU statistics
CODING_SCHEME_CHANGE
Description
Controls blocks (always sent at CS-1) will result in this statistic not being pegged.
Downlink coding scheme transitions for dummy blocks (when entering and
exiting super-coattail) will not be counted.
The bins are defined in Table 12-3:
12-22 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CODING_SCHEME_CHANGE
Pegging
The appropriate bin is incremented each time a change in coding scheme occurs.
Analysis
This statistic can be used for the trend analysis of the number of Coding Scheme upgrades and downgrades
on the uplink and downlink which may signify that the cell is congested.
Reference Digital cellular telecommunications systems (phase 2+) Version
7.0.0 Jan 2000 ETSI.
Usage Congestion, network planning.
Basis Cell.
Type Small counter array.
68P02901W56-Q 12-23
24 May 2004 CONTROLLED INTRODUCTION
CONG_REL_DL_SCTS Chapter 12: PCU statistics
CONG_REL_DL_SCTS
{4445}
Description
The CONG_REL_DL_SCTS statistic tracks the total number of downlink TBF terminations under the
delayed TBF release mode (super-coattail) in a cell as cell availability goes below the following thresholds:
• 25 block periods (500ms) old super-coattail will be terminated if the:
cell availability reached is 25%, in a cell with 3 TS.
This statistic is accessible only if the Increased PRP Capacity feature introduced by
Enhanced Scheduling feature RDB 4441 is unrestricted.
Pegging
This statistic pegs each time that an uplink TBF is successfully established and later released under delayed
TBF release mode to relieve the congestion in a cell during a statistical measurement interval.
{23658} This statistic is pegged for both GPRS and EGPRS events.
12-24 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CONG_REL_DL_SCTS
Reference None
Usage Performance management
Basis Cell.
Type Counter.
68P02901W56-Q 12-25
24 May 2004 CONTROLLED INTRODUCTION
CS12_ON_32K_CHAN Chapter 12: PCU statistics
CS12_ON_32K_CHAN
Description
The CS12_ON_32K_CHAN statistic tracks the percentage of time in a statistics reporting period that
CS-3, CS-4 capable (32kTRAU) GPRS timeslots are used with CS-1 and CS-2 rates.
Pegging
This statistic measures the percentage of blocks for which CS-1 and CS-2 data was transmitted
on a timeslot capable of CS-3 or CS-4 rates.
Reference None.
Usage Radio resource allocation statistics.
Network planning.
Basis Cell.
Type Percentage.
12-26 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DL_BUSY_PDTCH
DL_BUSY_PDTCH
Description
This statistic measures the mean, max and min number of occupied Packet Data CHannels
(PDCH) carrying downlink packet traffic.
This statistic is obtained by sampling the PDTCH, which are carrying packet traffic, at
every packet-scheduling period (20 millisecond).
Table 12-4 shows the ranges for each bin (measured in milliseconds).
Bin Range
0 No PDTCH is busy
1 1-2 PDTCH are busy
2 3-4 PDTCH are busy
3 5-6 PDTCH are busy
4 7-8 PDTCH are busy
5 9-10 PDTCH are busy
6 11-12 PDTCH are busy
7 13-14 PDTCH are busy
8 15-16 PDTCH are busy
9 17-400 PDTCH are busy
Pegging
This statistic pegs every packet-scheduling period (20 millisecond) by sampling the number
of PDTCHs that are carrying downlink packet traffic.
{23658} This statistic is pegged for both GPRS and EGPRS events.
68P02901W56-Q 12-27
24 May 2004 CONTROLLED INTRODUCTION
DL_BUSY_PDTCH Chapter 12: PCU statistics
Analysis
This statistic can be used for trend analysis of the number of PDTCHs that are used for downlink packet traffic.
Reference Digital cellular telecommunications systems (phase 2+) Version
7.0.0 Jan 2000 ETSI.
Usage Network planning, congestion.
Basis Cell
Type Weighted distribution.
12-28 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DL_PDTCH_CONGESTION
DL_PDTCH_CONGESTION
Description
The DL_PDTCH_CONGESTION statistic calculates the number of times a cell is congested due
to MS load on the available air resources on the downlink. Whenever the downlink resources are
determined to be congested, the statistic is updated. When the value of the statistic is large, it indicates
that the cell is congested and more radio resources may need to be provisioned.
Pegging
The PDTCH congestion is computed every 8s (8000ms) in 20ms block periods when the congestion threshold
is reached. The congestion threshold is configurable with values ranging from 1-4. Level 1 means averagely
one TBF per TS on a cell is considered congested. Level 4 means four TBFs per TS are considered congested.
This is synonymous with the concept that one PDTCH can be shared by, at most, 4 MSs.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Analysis
This statistic is totalled in terms of 20 millisecond block periods.
68P02901W56-Q 12-29
24 May 2004 CONTROLLED INTRODUCTION
DL_PDTCH_Q_LENGTH Chapter 12: PCU statistics
DL_PDTCH_Q_LENGTH
Description
This statistic is obtained by sampling the Downlink Request Queue. A Downlink Request
is triggered on arrival of LLC-PDUs at the PCU.
Pegging
This statistic pegs every 20ms. It is incremented when a request is added to the queue and is
decremented when a request is processed, that is, leaves the queue.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Analysis
This statistic can be used for the trend analysis of the average number of downlink messages
waiting for a PDTCH to become available.
Reference Digital cellular telecommunications systems (phase 2+) Version
7.0.0 Jan 2000 ETSI.
Usage Network planning, congestion.
Basis Cell.
Type Gauge.
12-30 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DL_PDTCH_SEIZURE
DL_PDTCH_SEIZURE
Description
This statistic measures successful Packet Data Traffic CHannel (PDTCH) seizure on the downlink. The
purpose of this statistic is to count the number of TBF(s) on the downlink. The statistic is obtained by
measuring the receipt of the first RLC block (PDU) on the PDTCH from the network (downlink).
Pegging
This statistic pegs when the receipt of the first downlink RLC block (PDU) on the
PDTCH from the network is obtained.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Analysis
This statistic can be used for the trend analysis of the total number of TBFs on the downlink for a CELL.
68P02901W56-Q 12-31
24 May 2004 CONTROLLED INTRODUCTION
DL_RADIO_BLKS_1_TS Chapter 12: PCU statistics
DL_RADIO_BLKS_1_TS
{23658}
Description
The DL_RADIO_BLKS_1_TS statistic counts the total number of RLC radio blocks sent to
mobiles that support a maximum of 1 TS in the downlink direction.
100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation of
actual radio blocks counted to units is performed at the end of the interval.
The RLC radio blocks are split into the four GPRS channel coding schemes and the nine
EGPRS coding schemes, as shown in Table 12-5.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
12-32 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DL_RADIO_BLKS_1_TS
In coding schemes MCS-7 through MSC-9, there are two RLC blocks in a radio block. The data shown
in the following table is used to determine which statistic must be pegged for possible combinations of
NEW, NACK, ACK_PEND and STALL when transmitting MCS-7, MCS-8 or MCS-9.
Pegging
This statistic counts the RLC radio blocks for mobiles that support a maximum of 1
TS in the downlink direction as follows:
• Always pegged for mobiles with multislot class 1.
Analysis
Reference None
Usage
Basis Cell
Type Extra large counter array
68P02901W56-Q 12-33
24 May 2004 CONTROLLED INTRODUCTION
DL_RADIO_BLKS_2_TS Chapter 12: PCU statistics
DL_RADIO_BLKS_2_TS
{23658}
Description
The DL_RADIO_BLKS_2_TS statistic counts the total number of RLC radio blocks sent to
mobiles that support a maximum of 2 TS in the downlink direction.
100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation
of actual radio blocks counted to units is done at the end of the interval.
The RLC radio blocks are split into the four GPRS channel coding schemes, and the nine
EGPRS coding schemes, as shown in Table 12-6.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
12-34 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DL_RADIO_BLKS_2_TS
In coding schemes MCS-7 through MSC-9, there are two RLC blocks in a radio block. The data shown
in the following table is used to determine which statistic must be pegged for possible combinations of
NEW, NACK, ACK_PEND and STALL when transmitting MCS-7, MCS-8 or MCS-9.
Pegging
This statistic counts the RLC radio blocks for mobiles that support a maximum of 2
TS in the downlink direction as follows:
• Always pegged for mobiles with multislot class 2, 3 or 5.
• CS-1 through CS-4 are pegged if the GPRS TBF is assigned to the mobile
and its GPRS multislot is class 2,3 or 5.
• MCS-1 through MCS-9 are pegged if an EGPRS mode TBF is assigned to the
mobile and the EGPRS multislot is class 2, 3 or 5.
Analysis
Reference None
Usage
Basis Cell
Type Extra large counter array
68P02901W56-Q 12-35
24 May 2004 CONTROLLED INTRODUCTION
DL_RADIO_BLKS_3_TS Chapter 12: PCU statistics
DL_RADIO_BLKS_3_TS
{23658}
Description
The DL_RADIO_BLKS_3_TS statistic counts the total number of RLC radio blocks sent to
mobiles that support a maximum of 3 TS in the downlink direction.
100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation
of actual radio blocks counted to units is done at the end of the interval.
The RLC radio blocks are split into the four GPRS channel coding schemes and the nine
EGPRS coding schemes, as shown in Table 12-7.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
12-36 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DL_RADIO_BLKS_3_TS
In coding schemes MCS-7 through MSC-9, there are two RLC blocks in a radio block. The data shown
in the following table is used to determine which statistic must be pegged for possible combinations of
NEW, NACK, ACK_PEND and STALL when transmitting MCS-7, MCS-8 or MCS-9.
Pegging
This statistic counts the RLC radio blocks for mobiles that support a maximum of 3
TS in the downlink direction as follows:
• Always pegged for mobiles with multislot class 4, 6, 7, 9, or 13.
• CS-1 through CS-4 are pegged if the GPRS TBF is assigned to the mobile and
its GPRS multislot is class 4, 6, 7, 9, or 13.
• MCS-1 through MCS-9 are pegged if an EGPRS mode TBF is assigned to the mobile
and the EGPRS multislot is class 4, 6, 7, 9, or 13.
Analysis
Reference None
Usage
Basis Cell
Type Extra large counter array
68P02901W56-Q 12-37
24 May 2004 CONTROLLED INTRODUCTION
DL_RADIO_BLKS_4_TS Chapter 12: PCU statistics
DL_RADIO_BLKS_4_TS
{23658}
Description
The DL_RADIO_BLKS_4_TS statistic counts the total number of RLC radio blocks sent to
mobiles that support a maximum of 4 TS in the downlink direction.
100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation
of actual radio blocks counted to units is done at the end of the interval.
The RLC radio blocks are split into the four GPRS channel coding schemes and the nine
EGPRS coding schemes, as shown in Table 12-8.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
12-38 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DL_RADIO_BLKS_4_TS
In coding schemes MCS-7 through MSC-9, there are two RLC blocks in a radio block. The data shown
in the following table is used to determine which statistic must be pegged for possible combinations of
NEW, NACK, ACK_PEND and STALL when transmitting MCS-7, MCS-8 or MCS-9.
Pegging
This statistic counts the RLC radio blocks for mobiles that support a maximum of 4
TS in the downlink direction as follows:
• Always pegged for mobiles with multislot class 8, 10, 11, 12 or 14 through 29.
• CS-1 through CS-4 are pegged if the GPRS TBF is assigned to the mobile and its
GPRS multislot is one of class 8, 10, 11, 12 or 14 through 29.
• MCS-1 through MCS-9 are pegged if an EGPRS mode TBF is assigned to the mobile
and the EGPRS multislot is one of class 8, 10, 11, 12 or 14 through 29.
Analysis
Reference None
Usage
Basis Cell
Type Extra large counter array
68P02901W56-Q 12-39
24 May 2004 CONTROLLED INTRODUCTION
DL_RLC_ACK_NEW_BLKS Chapter 12: PCU statistics
DL_RLC_ACK_NEW_BLKS
{23658}
Description
The DL_RLC_ACK_NEW_BLKS statistic measures the total number of new RLC acknowledge
mode blocks sent for the first time by the PCU over the cell.
100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation
of actual radio blocks counted to units is done at the end of the interval.
The RLC radio blocks are split into the four GPRS channel coding schemes and the nine
EGPRS coding schemes, as shown in Table 12-9.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
12-40 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DL_RLC_ACK_NEW_BLKS
In coding schemes MCS-7 through MSC-9, there are two RLC blocks in a radio block. The data shown
in the following table is used to determine which statistic must be pegged for possible combinations of
NEW, NACK, ACK_PEND and STALL when transmitting MCS-7, MCS-8 or MCS-9.
Pegging
This statistic counts the new RLC acknowledged radio blocks that are sent on a cell. The RLC radio
blocks are counted per coding scheme, therefore pegging the appropriate bin.
Analysis
Reference None
Usage
Basis Cell
Type Extra large counter array
68P02901W56-Q 12-41
24 May 2004 CONTROLLED INTRODUCTION
DL_RLC_DDTR_BLKS Chapter 12: PCU statistics
DL_RLC_DDTR_BLKS
{23658}
Description
The DL_RLC_DDTR_BLKS statistic measures the total number of RLC blocks with dummy LLCs
sent in CS1 or MCS1 during the delayed downlink TBF release period over the cell.
100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation
of actual radio blocks counted to units is done at the end of the interval.
The RLC radio blocks are split into two coding schemes, as shown in Table 12-10.
Bin Range
0 CS-1
1 MCS-1
Pegging
This statistic counts the RLC radio blocks with dummy LLCs (delayed downlink TBF) blocks that are sent
on a cell. The RLC radio blocks are counted per coding scheme, therefore pegging the appropriate bin.
Note that the radio blocks with LLC dummies are always sent using either CS1 or MCS1.
Analysis
Reference None
Usage
Basis Cell
Type Small counter array
12-42 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DL_RLC_NACK_BLKS
DL_RLC_NACK_BLKS
{23658}
Description
The DL_RLC_NACK_BLKS statistic measures the total number of RLC blocks sent
due to an explicit NACK from the mobile.
100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation
of actual radio blocks counted to units is done at the end of the interval.
The RLC radio blocks are split into the four GPRS channel coding schemes and the nine
EGPRS coding schemes, as shown in Table 12-11.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
68P02901W56-Q 12-43
24 May 2004 CONTROLLED INTRODUCTION
DL_RLC_NACK_BLKS Chapter 12: PCU statistics
In coding schemes MCS-7 through MSC-9, there are two RLC blocks in a radio block. The data shown
in the following table is used to determine which statistic must be pegged for possible combinations of
NEW, NACK, ACK_PEND and STALL when transmitting MCS-7, MCS-8 or MCS-9.
Pegging
This statistic counts the RLC blocks that are sent due to an explicit NACK from the mobile. The RLC
radio blocks are counted per coding scheme, therefore pegging the appropriate bin.
Analysis
Reference None
Usage
Basis Cell
Type Extra large counter array
12-44 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DL_RLC_RETX_BLKS
DL_RLC_RETX_BLKS
{23658}
Description
The DL_RLC_RETX_BLKS statistic measures the total number of pre-emptive retransmissions (or ack
pending blocks and acknowledged retransmissions) sent by the PCU over the cell.
100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation
of actual radio blocks counted to units is done at the end of the interval.
The RLC radio blocks are split into the four GPRS channel coding schemes and the nine
EGPRS coding schemes, as shown in Table 12-12.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
68P02901W56-Q 12-45
24 May 2004 CONTROLLED INTRODUCTION
DL_RLC_RETX_BLKS Chapter 12: PCU statistics
In coding schemes MCS-7 through MSC-9, there are two RLC blocks in a radio block. The data shown
in the following table is used to determine which statistic must be pegged for possible combinations of
NEW, NACK, ACK_PEND and STALL when transmitting MCS-7, MCS-8 or MCS-9.
Pegging
This statistic counts the RLC ack pending (or pre-emptive transmissions) radio blocks that are sent on a cell.
The RLC radio blocks are counted per coding scheme, therefore pegging the appropriate bin.
Analysis
Reference None
Usage
Basis Cell
Type Extra large counter array
12-46 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DL_RLC_STALLED_BLKS
DL_RLC_STALLED_BLKS
{23658}
Description
The DL_RLC_STALLED_BLKS statistic measures the total number of RLC blocks retransmitted due to an
RLC window stall. That is, if the window is stalled, all DL radio blocks sent during this period are pegged as
stalled. Stalled blocks supersede other types of transmissions of NEW, NACK and RETX blocks. For example,
a NACK data block sent during a stalled window condition is treated as a stalled block and gets pegged as such.
100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation
of actual radio blocks counted to units is done at the end of the interval.
The RLC radio blocks are split into the four GPRS channel coding schemes and the nine
EGPRS coding schemes, as shown in Table 12-13.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
68P02901W56-Q 12-47
24 May 2004 CONTROLLED INTRODUCTION
DL_RLC_STALLED_BLKS Chapter 12: PCU statistics
In coding schemes MCS-7 through MSC-9, there are two RLC blocks in a radio block. The data shown
in the following table is used to determine which statistic must be pegged for possible combinations of
NEW, NACK, ACK_PEND and STALL when transmitting MCS-7, MCS-8 or MCS-9.
Pegging
This statistic counts the RLC blocks sent due to any RLC window stall in the cell. The RLC radio
blocks are counted per coding scheme therefore pegging the appropriate bin.
Analysis
Reference None
Usage
Basis Cell
Type Extra large counter array
12-48 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DL_RLC_UNACK_NEW_BLKS
DL_RLC_UNACK_NEW_BLKS
{23658}
Description
The DL_RLC_UNACK_NEW_BLKS statistic measures the total number of new RLC unacknowledge
mode blocks sent for the first time by the PCU over the cell.
100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation
of actual radio blocks counted to units is done at the end of the interval.
The RLC radio blocks are split into the four GPRS channel coding schemes and the nine
EGPRS coding schemes, as shown in Table 12-14.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
68P02901W56-Q 12-49
24 May 2004 CONTROLLED INTRODUCTION
DL_RLC_UNACK_NEW_BLKS Chapter 12: PCU statistics
In coding schemes MCS-7 through MSC-9, there are two RLC blocks in a radio block. The data shown
in the following table is used to determine which statistic must be pegged for possible combinations of
NEW, NACK, ACK_PEND and STALL when transmitting MCS-7, MCS-8 or MCS-9.
Pegging
This statistic counts the new RLC unacknowledged radio blocks that are sent on a cell. The RLC radio
blocks are counted per coding scheme, therefore pegging the appropriate bin.
Analysis
Reference None
Usage
Basis Cell
Type Extra large counter array
12-50 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DL_TBF_TIME_1_TS
DL_TBF_TIME_1_TS
{23658}
Description
The DL_TBF_TIME_1_TS statistic counts the cumulative length in number of 20ms radio block periods of
all downlink TBFs for mobiles that support a maximum of 1 TS in the downlink direction.
Pegging
This statistic measures the time of all the TBFs in the downlink for mobiles that support a
maximum of 1 TS in the downlink direction as follows:
• Always pegged for mobiles with multislot class 1.
• If a GPRS TBF is assigned to the mobile and its GPRS multislot is class 1.
• If an EGPRS mode TBF is assigned to the mobile and the EGPRS multislot is class 1.
At the end of the statistical interval this statistic provides a cumulative value of all the DL TBF times
for mobiles supporting a maximum of 1 TS. The TBF time is measured from the TBF set-up time to
the time the mobile acknowledges the full TBF. The TBF time includes all the delayed downlink TBF
release phases except the very last one so as to accurately reflect the perceived throughput.
Analysis
Reference None
Usage
Basis Cell
Type Counter
68P02901W56-Q 12-51
24 May 2004 CONTROLLED INTRODUCTION
DL_TBF_TIME_2_TS Chapter 12: PCU statistics
DL_TBF_TIME_2_TS
{23658}
Description
The DL_TBF_TIME_2_TS statistic counts the cumulative length in number of 20ms radio block periods of
all downlink TBFs for mobiles that support a maximum of 2 TS in the downlink direction.
Pegging
This statistic measures the time of all the TBFs in the downlink for mobiles that support a
maximum of 2 TS in the downlink direction as follows:
• Always pegged for mobiles with multislot class 2, 3 or 5.
• If a GPRS TBF is assigned to the mobile and its GPRS multislot is class 2,3 or 5.
• If an EGPRS mode TBF is assigned to the mobile and the EGPRS multislot is class 2, 3 or 5.
At the end of the statistical interval this statistic provides a cumulative value of all the DL TBF times
for mobiles supporting a maximum of 2 TS. The TBF time is measured from the TBF set-up time to
the time the mobile acknowledges the full TBF. The TBF time includes all the delayed downlink TBF
release phases except the very last one so as to accurately reflect the perceived throughput.
Analysis
Reference None
Usage
Basis Cell
Type Counter
12-52 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DL_TBF_TIME_3_TS
DL_TBF_TIME_3_TS
{23658}
Description
The DL_TBF_TIME_3_TS statistic counts the cumulative length in number of 20ms radio block periods of
all downlink TBFs for mobiles that support a maximum of 3 TS in the downlink direction.
Pegging
This statistic measures the time of all the TBFs in the downlink for mobiles that support a
maximum of 3 TS in the downlink direction as follows:
• Always pegged for mobiles with multislot class 4, 6, 7, 9, or 13.
• If a GPRS TBF is assigned to the mobile and its GPRS multislot is class 4, 6, 7, 9, or 13.
• If an EGPRS mode TBF is assigned to the mobile and the EGPRS multislot
is class 4, 6, 7, 9, or 13.
At the end of the statistical interval this statistic provides a cumulative value of all the DL TBF times
for mobiles supporting a maximum of 3 TS. The TBF time is measured from the TBF set-up time to
the time the mobile acknowledges the full TBF. The TBF time includes all the delayed downlink TBF
release phases except the very last one so as to accurately reflect the perceived throughput.
Analysis
Reference None
Usage
Basis Cell
Type Counter
68P02901W56-Q 12-53
24 May 2004 CONTROLLED INTRODUCTION
DL_TBF_TIME_4_TS Chapter 12: PCU statistics
DL_TBF_TIME_4_TS
{23658}
Description
The DL_TBF_TIME_4_TS statistic counts the cumulative length in number of 20ms radio block periods of
all downlink TBFs for mobiles that support a maximum of 4 TS in the downlink direction.
Pegging
This statistic measures the time of all the TBFs in the downlink for mobiles that support a
maximum of 4 TS in the downlink direction as follows:
• Always pegged for mobiles with multislot class 8, 10, 11, 12 or 14 through 29.
• If a GPRS TBF is assigned to the mobile and its GPRS multislot is one of
class 8, 10, 11, 12 or 14 through 29.
• If an EGPRS mode TBF is assigned to the mobile and the EGPRS multislot is
one of class 8, 10, 11, 12 or 14 through 29.
At the end of the statistical interval this statistic provides a cumulative value of all the DL TBF times
for mobiles supporting a maximum of 4 TS. The TBF time is measured from the TBF set-up time to
the time the mobile acknowledges the full TBF. The TBF time includes all the delayed downlink TBF
release phases except the very last one so as to accurately reflect the perceived throughput.
Analysis
Reference None
Usage
Basis Cell
Type Counter
12-54 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application EGPRS_64K_CHANNELS_SWITCHED
EGPRS_64K_CHANNELS_SWITCHED
{23658}
Description
The EGPRS_64K_CHANNELS_SWITCHED statistic counts the number of times that 64kbps EGPRS
timeslots are used for circuit-switched calls in a statistics reporting period on a per-cell basis.
Pegging
This statistic pegs when a 64kbps EGPRS timeslot is successfully switched to a circuit switched call.
Analysis
Reference None
Usage
Basis Cell
Type Counter
68P02901W56-Q 12-55
24 May 2004 CONTROLLED INTRODUCTION
EGPRS_64K_NOT_AVAIL Chapter 12: PCU statistics
EGPRS_64K_NOT_AVAIL
{23658}
Description
The EGPRS_64K_NOT_AVAIL statistic tracks the number of times that a TBF would have
been able to use EGPRS coding schemes due to good radio conditions in the cell but could not
because the mobile’s timeslot assignment was not 64k TRAU.
Pegging
This statistic pegs when an EGPRS capable mobile is allocated GPRS resources. This statistic
is pegged when 64k TRAU is disabled or when the mobile is allocated GPRS timeslots and the
radio conditions would allow usage of EGPRS coding schemes.
Analysis
Reference None
Usage If CS-3,4 is disabled, it counts how often CS-3,4 would have been
used resulting in increased end user throughput.
Basis Cell
Type Counter
12-56 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application EGPRS_AVAIL_PDTCH
EGPRS_AVAIL_PDTCH
{23658}
Description
The EGPRS_AVAIL_PDTCH statistic measures the mean and max number of available
EGPRS Packet Data Traffic Channels (PDTCH).
This statistic is obtained by maintaining the current and total number of available EGPRS PDTCHs and the
amount of time each is available over the statistical period. The PDTCH is available when its administrative
state is unlocked or shutting down and the operational state is enabled. It is unavailable when its administrative
state changes to locked or the operational state changes to disabled. The available EGPRS PDTCH counts
both reserved PDTCHs and switchable PDTCHs that are actually configured for use as an EGPRS PDTCHs.
Pegging
This statistic pegs whenever there is a change in the channel configuration for any channel
in the cell (if the number of EGPRS PDTCHs has not changed within the current pegging
interval, it is pegged with the same value as before).
This statistic counts the number of timeslots available for GPRS. It treats PBCCH/PCCCH TS
the same as regular PDTCH TS, which means that each TS is counted as 1, even though 4 MS
can share a regular TS, while a PBCCH/PCCCH TS can only be shared by 2 MS.
Analysis
Reference 4.60, 5.08
Usage
Basis Cell
Type Gauge
68P02901W56-Q 12-57
24 May 2004 CONTROLLED INTRODUCTION
EGPRS_DL_ASGN_PCCCH Chapter 12: PCU statistics
EGPRS_DL_ASGN_PCCCH
{23658}
Description
Pegging
This statistic pegs whenever an EGPRS packet downlink assignment is sent on PCCCH.
Analysis
Reference None
Usage
Basis Cell
Type Counter
12-58 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application G_RACH_UNSVCD_BTS
G_RACH_UNSVCD_BTS
{4441}
Description
• No PRR block.
• AGCH discard.
Pegging
This statistic is pegged whenever a GPRS RACH request is unserviced by the BTS.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Analysis
This statistic can be used for the trend analysis of the BTS.
Reference None.
Usage Performance management.
Basis Cell.
Type Small counter array.
68P02901W56-Q 12-59
24 May 2004 CONTROLLED INTRODUCTION
GBL_DL_DATA_THRPUT Chapter 12: PCU statistics
GBL_DL_DATA_THRPUT
Description
The GBL_DL_DATA_THRPUT statistic reports the quantity of data transmitted on the downlink
of the Gb link (GBL) during a given time interval. The PCU calculates the instantaneous
throughput in kilobytes per second by dividing the quantity of data transmitted by the time
interval given by the parameter gbl_thrput_period.
Pegging
This statistic is pegged by computing a moving average in kilobytes per second of the
instantaneous throughput samples. The number of samples used for the computation is
given by the parameter num_gbl_dl_thrput_samples.
Analysis
This statistic can be used for the trend analysis of the average downlink throughput of the GBL.
This statistic is stored in the following columns in the gbl_statistics table:
• dl_datathrput_mean.
• dl_datathrput_max.
Reference None.
Usage Network planning.
Congestion.
Basis GBL.
Type Gauge.
12-60 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GBL_DL_DATA_THRPUT_HIST
GBL_DL_DATA_THRPUT_HIST
Description
Bin Range
0 0 - 30
1 31 - 70
2 71 - 110
3 111 - 140
4 141 - 170
5 171 - 230
6 231 - 300
7 301 - 400
8 401 - 500
9 501 - 600
Pegging
The GBL_DL_DATA_THRPUT_HIST statistic pegs the instantaneous throughput samples
in 10 bins. See Table 12-15 for the ranges.
68P02901W56-Q 12-61
24 May 2004 CONTROLLED INTRODUCTION
GBL_DL_DATA_THRPUT_HIST Chapter 12: PCU statistics
Analysis
This statistic can be used for the trend analysis of GBL downlink throughput.
This statistic is stored in the following columns in the gbl_statistics table:
• dl_thrput_min.
• dl_thrput_mean.
• dl_thrput_max.
Reference None.
Usage Network planning.
Congestion.
Quality of service monitoring: Network accessibility.
Basis GBL.
Type Normal Distribution.
12-62 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GBL_FLOW_CTRL_SENT
GBL_FLOW_CTRL_SENT
Description
The GBL_FLOW_CTRL_SENT tracks the number of flow control messages sent by the
BSS to the Serving GPRS Support Node (SGSN).
Each cell has a buffer that holds downlink data. When a cell buffer reaches a predetermined
threshold, a flow control message is sent to the SGSN.
Flow control is performed to match the flow of downlink data with air throughput.
Pegging
This statistic pegs the number of flow control messages sent by the BSS and is pegged
every time a flow control message is sent.
Analysis
This statistic can be used for trend analysis of the number of flow control messages sent by the BSS.
Reference None.
Usage Network planning.
Congestion.
Quality of service monitoring: Network accessibility.
Basis Cell.
Type Counter.
68P02901W56-Q 12-63
24 May 2004 CONTROLLED INTRODUCTION
GBL_LINK_INS Chapter 12: PCU statistics
GBL_LINK_INS
Description
The GBL_LINK_INS statistic tracks the amount of time in milliseconds that a specified GBL is in service.
Pegging
The timer for this statistic starts when the GBL transitions to the B-U state (that is, returns to service). The
timer for this statistic stops when the GBL is no longer in the B-U state (that is, goes out of service).
Analysis
This statistic can be used for trend analysis of GBL usage.
Reference None.
Usage Network accessibility.
Fault finding.
Protocol utilization.
Basis GBL.
Type Duration.
12-64 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GBL_PAGING_REQS
GBL_PAGING_REQS
Description
The GBL_PAGING_REQS statistic tracks the number of paging requests received at the GBL.
Pegging
This statistic pegs each time an MS page request is received at the GBL.
Analysis
This statistic can be used for the trend analysis of the number of circuit switched and packet
switched pages received by the BSS from the SGSN.
Reference None.
Usage Network planning.
Congestion.
Basis PCU.
Type Counter.
68P02901W56-Q 12-65
24 May 2004 CONTROLLED INTRODUCTION
GBL_UL_DATA_THRPUT Chapter 12: PCU statistics
GBL_UL_DATA_THRPUT
Description
The GBL_UL_DATA_THRPUT statistic reports the quantity of data transmitted on the uplink of the Gb link
(GBL) during a given time interval. The PCU calculates the instantaneous throughput in kilobytes per second
by dividing the quantity of data transmitted by the time interval given by the parameter gbl_thrput_period.
Pegging
This statistic is pegged by computing a moving average in kilobytes per second of the
instantaneous throughput samples. The number of samples used for the computation is
given by the parameter num_gbl_ul_thrput_samples.
Analysis
This statistic can be used for the trend analysis of the average uplink throughput of the GBL.
This statistic is stored in the following columns in the gbl_statistics table:
• ul_datathrput_mean.
• ul_datathrput_max.
Reference None.
Usage Network planning.
Congestion.
Basis GBL.
Type Gauge.
12-66 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GBL_UL_DATA_THRPUT_HIST
GBL_UL_DATA_THRPUT_HIST
Description
Pegging
The GBL_UL_DATA_THRPUT_HIST statistic pegs the instantaneous throughput samples
in 10 bins. The ranges are shown in Table 12-16.
Bin Range
0 0 - 30
1 31 - 70
2 71 - 110
3 111 - 140
4 141 - 170
5 171 - 230
6 231 - 300
7 301 - 400
8 401 - 500
9 501 - 600
68P02901W56-Q 12-67
24 May 2004 CONTROLLED INTRODUCTION
GBL_UL_DATA_THRPUT_HIST Chapter 12: PCU statistics
Analysis
This statistic can be used for the trend analysis of GBL uplink throughput.
This statistic is stored in the following columns in the gbl_statistics table:
• ul_thrput_min.
• ul_thrput_mean.
• ul_thrput_max.
Reference None.
Usage Network planning.
Congestion.
Quality of service monitoring: Network accessibility.
Basis GBL.
Type Normal Distribution.
12-68 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GBL_UNAVAILABLE
GBL_UNAVAILABLE
Description
The GBL_UNAVAILABLE statistic tracks the amount of time in milliseconds that the GBL is out of service.
Pegging
The timer for this statistic is started when the GBL transitions to a state which is not B-U,
that is, when he GBL goes out of service. The timer is stopped when the GBL is in the
B-U state, that is, when the GBL returns to service.
Analysis
This statistic can be used for trend analysis of the duration of GBL outages, including
those caused by operator interaction.
Reference None.
Usage Network accessibility.
Fault finding.
Basis GBL.
Type Duration.
68P02901W56-Q 12-69
24 May 2004 CONTROLLED INTRODUCTION
GPRS_32K_CHANNELS_SWITCHED Chapter 12: PCU statistics
GPRS_32K_CHANNELS_SWITCHED
Description
This statistic keeps a count of the number of times that CS-3,4 capable GPRS timeslots (32k TRAU)
are used for circuit-switched calls in a statistics reporting period on a per-cell basis.
Pegging
This statistic pegs when a 32kilobits per second GPRS timeslot is successfully switched to a circuit switched call.
Reference None.
Usage Radio resource allocation statistics.
Network planning.
Basis Cell.
Type Counter.
12-70 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GPRS_32K_DL_NOT_AVAIL
GPRS_32K_DL_NOT_AVAIL
Description
The GPRS_32K_DL_NOT_AVAIL statistic tracks the number of times that 16k TRAU GPRS
timeslots would have been switched to CS-3,4 due to good radio conditions in the cell, but could
not because the mobile’s timeslot assignment was not 32k TRAU.
Pegging
This statistic pegs when 32k TRAU is disabled or when the mobile is allocated 16k TRAU
timeslots and the radio conditions would allow usage of CS-3,4.
Reference None.
Usage If CS-3,4 is disabled, it is counted how often CS-3,4 would have
been used resulting in increased end user throughput.
Basis Cell.
Type Counter.
68P02901W56-Q 12-71
24 May 2004 CONTROLLED INTRODUCTION
GPRS_32K_UL_NOT_AVAIL Chapter 12: PCU statistics
GPRS_32K_UL_NOT_AVAIL
Description
The GPRS_32K_UL_NOT_AVAIL statistic tracks the number of times that 16k TRAU GPRS
timeslots would have been switched to CS-3,4 due to good radio conditions in the cell, but could
not because the mobile’s timeslot assignment was not 32k TRAU.
Pegging
This statistic pegs when 32k TRAU is disabled or when the mobile is allocated 16k TRAU
timeslots and the radio conditions would allow usage of CS-3,4.
Reference None.
Usage If CS-3,4 is disabled, it is counted how often CS-3,4 would have
been used resulting in increased end user throughput.
Basis Cell.
Type Counter.
12-72 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GPRS_ACCESS_PER_AGCH
GPRS_ACCESS_PER_AGCH
Description
Pegging
This statistic is pegged when an access grant message is sent on the AGCH on a cell for packet data service.
Analysis
This statistic can be used for trend analysis of Immediate Assignment messages sent on the AGCH of a cell.
Reference None.
Usage Radio resource allocation statistics.
Network planning.
Basis Cell.
Type Counter.
68P02901W56-Q 12-73
24 May 2004 CONTROLLED INTRODUCTION
GPRS_ACCESS_PER_RACH Chapter 12: PCU statistics
GPRS_ACCESS_PER_RACH
Description
The GPRS_ACCESS_PER_RACH statistic tracks the number of packet switched Channel Request
messages successfully received on the Random Access CHannel (RACH) for GPRS purposes.
Pegging
This statistic pegs when a packet switched Channel Request message is sent on the
Random Access CHannel (RACH) of a cell.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Analysis
This statistic can be used for trend analysis of Immediate Assignment messages sent on the RACH of a cell.
Reference None.
Usage Radio resource allocation statistics.
Network planning.
Basis Cell.
Type Counter.
12-74 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GPRS_AVAIL_PDTCH
GPRS_AVAIL_PDTCH
Description
This statistic measures the mean and max number of available Packet Data Traffic CHannels (PDTCH).
{3723} This statistic considers a PBCCH/PCCCH timeslot as a PDTCH therefore these will be
recorded by the statistic in its total number of available channels.
This statistic is obtained by maintaining the current and total number of available PDTCH and the amount of
time each PDTCH is available over the statistical period. The corresponding mean and maximum number of
PDTCH are then computed. The PDTCH is available when its administrative state is unlocked or shutting
down and the operational state is enabled. It is unavailable when its administrative state changes to locked
or the operational state changes to disabled. The available number of PDTCH is then incremented or
decremented when there is a change in PDTCH states as described above. The available PDTCH counts both
reserved PDTCHs and switchable PDTCHs that are actually configured as PDTCHs and not as TCHs.
The number of PDTCH = Number of switchable PDTCHs (configured as PDTCHs)
+ Number of reserved PDTCHs
Pegging
The statistic pegs whenever there is a change in the channel configuration for any channel
in the cell (if the number of PDTCHs has not changed within the current pegging interval,
it will be pegged with the same value as before).
This statistic counts the number of timeslots available for GPRS. It treats PBCCH/PCCCH TS
the same as regular PDTCH TS, which means that each TS is counted as 1, even though 4 MS
can share a regular TS, while a PBCCH/PCCCH TS can only be shared by 2 MS.
68P02901W56-Q 12-75
24 May 2004 CONTROLLED INTRODUCTION
GPRS_AVAIL_PDTCH Chapter 12: PCU statistics
Analysis
This statistic can be used for trend analysis of PDTCH availability.
By comparing the number of available PDTCHs to the total number of PDTCHs in a cell, a percentage
of GPRS availability in a cell can be calculated. An analysis of the utilization information can be
used to determine the requirement for additional resources before problems occur.
Reference Digital cellular telecommunications systems (phase 2+) Version
7.0.0 Jan 2000 ETSI.
Usage Congestion.
Network planning.
Basis Cell.
Type Gauge.
12-76 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GPRS_CELL_RESELECT_ATTMPT
GPRS_CELL_RESELECT_ATTMPT
Description
Pegging
This statistic pegs whenever the network sends a packet cell change order message to
the mobile station (in idle or transfer mode).
{23658} This statistic is pegged for both GPRS and EGPRS events.
Analysis
This statistic can be used for analysis of Network Controlled cell reselect attempts from an originating cell.
Reference None.
Usage Radio resource allocation statistics.
Network planning.
Basis Cell.
Type Counter.
68P02901W56-Q 12-77
24 May 2004 CONTROLLED INTRODUCTION
GPRS_CELL_RESELECT_FAIL Chapter 12: PCU statistics
GPRS_CELL_RESELECT_FAIL
Description
Pegging
This statistic pegs when a Packet Cell Change Failure message is sent by an MS.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Analysis
This statistic can be used for analysis of Network Controlled cell reselect failures from an originating cell.
Reference None.
Usage Radio resource allocation statistics.
Network planning.
Basis Cell.
Type Counter.
12-78 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GPRS_CHANNELS_SWITCHED
GPRS_CHANNELS_SWITCHED
Description
This statistic reports the number of times a 16 kilobits per second Packet Data Traffic Channel
(PDTCH) has been switched to a circuit switched Traffic Channel (TCH).
Pegging
This statistic pegs when a 16 kilobits per second PDTCH is switched to a circuit switched TCH.
Reference None.
Usage Radio resource allocation statistics.
Network planning.
Basis Cell.
Type Counter.
68P02901W56-Q 12-79
24 May 2004 CONTROLLED INTRODUCTION
GPRS_DL_ASGN_PCCCH Chapter 12: PCU statistics
GPRS_DL_ASGN_PCCCH
{3723}
Description
This statistic tracks the total number of packet downlink assignment messages received on
the Packet Common Control Channel (PCCCH).
Pegging
This statistic pegs once per packet downlink assignment on the PCCCH.
12-80 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GPRS_DYNET_FAILURES
GPRS_DYNET_FAILURES
Description
The GPRS_DYNET_FAILURES statistic tracks the totals for four different sources
of terrestrial backing failure.
The sources of terrestrial backing failure are listed below.
• Terrestrial resource for a reserved GPRS timeslot is not provided when requested.
There are 4 bins for this array. The ranges are shown in Table 12-17.
Pegging
This statistic is pegged only when both dynamic allocation and GPRS are unrestricted. This
statistic is not pegged if either feature is restricted.
68P02901W56-Q 12-81
24 May 2004 CONTROLLED INTRODUCTION
GPRS_DYNET_FAILURES Chapter 12: PCU statistics
Analysis
This statistic can be used to analyse how effectively terrestrial backing resources are allocated
for a particular site. Bin counts can be observed to determine the effects of blocking,
preemption, and unavailable terrestrial resources with GPRS.
Reference None.
Usage Network planning.
Network accessibility.
Basis Dynet.
Type Counter array.
12-82 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GPRS_DYNET_RES_REQS
GPRS_DYNET_RES_REQS
Description
The GPRS_DYNET_RES_REQS statistic tracks the time that the number of requests for backing of
reserved timeslots were in the queue. Each bin corresponds to a range of queue lengths.
There are 10 bins for this array. The ranges are shown in Table 12-18.
Bin Range
0 0 - 5
1 6 - 10
2 11 - 15
3 16 - 20
4 21 - 25
5 26 - 30
6 31 - 35
7 36 - 40
8 41 - 45
9 46 - 50
Pegging
When this statistic is pegged, the bin corresponding to the length of the queue is incremented by one.
The maximum and minimum queue length and the average queue length is reported.
Reference None.
Usage Network planning.
Basis Dynet.
Type Weighted distribution.
68P02901W56-Q 12-83
24 May 2004 CONTROLLED INTRODUCTION
GPRS_DYNET_SWI_REQS Chapter 12: PCU statistics
GPRS_DYNET_SWI_REQS
Description
The GPRS_DYNET_SWI_REQS statistic tracks the time that the number of requests for
terrestrial backing of switchable GPRS timeslots were in the Dynamic Allocation queue.
Each bin corresponds to a range of queue lengths.
There are 10 bins for this array. The ranges are shown in Table 12-19.
Bin Range
0 0 - 5
1 6 - 10
2 11 - 15
3 16 - 20
4 21 - 25
5 26 - 30
6 31 - 35
7 36 - 40
8 41 - 45
9 46 - 50
Pegging
When this statistic is pegged, the bin corresponding to the length of the queue is incremented by one.
The maximum and minimum queue length and the average queue length are reported.
Reference None.
Usage Network planning.
Basis Dynet.
Type Weighted distribution.
12-84 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GPRS_MS_NEIGHBOR_STRONG
GPRS_MS_NEIGHBOR_STRONG
Description
The GPRS_MS_NEIGHBOR_STRONG statistic tracks the number of GPRS MS(s) for which the rxlev
of any neighbour cell is stronger by a certain threshold than the rxlev of the serving cell.
Pegging
This statistic pegs in NC2, whenever a Packet Measurement Report is received from an MS.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Analysis
This statistic is obtained by measuring the number of GPRS MS/s for which the receive level (rxlev)
of any neighbour cell is stronger than the rxlev of the serving cell by a defined threshold in the Packet
Measurement Report message. The counter is incremented only once for an MS if the multiple
Packet Measurement Report shows a better rxlev than the serving cell.
Reference None.
Usage Radio resource allocation statistics.
Network planning.
Basis Cell.
Type Counter.
68P02901W56-Q 12-85
24 May 2004 CONTROLLED INTRODUCTION
GPRS_PCH_AGCH_Q_LENGTH Chapter 12: PCU statistics
GPRS_PCH_AGCH_Q_LENGTH
Description
This statistic measures the mean Paging CHannel-Access Grant CHannel (PCH-AGCH) queue length.
This statistic is obtained by measuring the arithmetic mean of the number of all messages waiting for
transmission on the PCH-AGCH, for GPRS purpose. This measurement is obtained once in every paging
multi frame, taking the PCH-AGCH queue length and then taking the arithmetic mean.
Pegging
This statistic pegs once per paging multiframe, by summing the total number of messages in the paging
queue. At the end of the interval, the mean number of messages are calculated and reported.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Analysis
The 12.04 statistic B.2.1.1 is the mean of the number of messages in the PCH-AGCH queue.
12-86 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GPRS_PPCH_PAGCH_Q_LENGTH
GPRS_PPCH_PAGCH_Q_LENGTH
{3723}
Description
This statistic measures the mean and max of the number of all messages waiting in the Packet
Paging Channel-Packet Access Grant Channel (PPCH-PAGCH) queue. This statistic is obtained
by measuring the arithmetic mean of the number of all messages waiting for transmission on
the PPCH-PAGCH. This measurement is obtained once in every paging multi frame, taking the
PPCH-PAGCH queue length and then taking the arithmetic mean.
Pegging
This statistic pegs once per paging multiframe, by summing the total number of messages in the paging
queue. At the end of the interval, the mean number of messages are calculated and reported.
Analysis
The 12.04 statistic B.2.1.1 is the mean of the number of messages in the PPCH-PAGCH queue.
68P02901W56-Q 12-87
24 May 2004 CONTROLLED INTRODUCTION
GPRS_PRR_BLK_USG Chapter 12: PCU statistics
GPRS_PRR_BLK_USG
{4441}
Description
The GPRS_PRR_BLK_USG statistic tracks the mean, minimum, and maximum number of PRR block usage.
The bin ranges may be changed using the chg_stat_prop command. The default bin ranges for
the GPRS_PRR_BLK_USG statistic are shown in Table 12-20.
Bin Range
0 0 to 2
1 3 to 5
2 6 to 10
3 11 to 20
4 21 to 40
5 41 to 60
6 61 to 80
7 81 to 100
8 101 to 125
9 126 to 160
Pegging
This statistic is measured by obtaining the PRR block usage at a predefined interval: approximately
one second (four multiframes) and updating the appropriate bin. At the end of the report of the statistical
interval, the mean, minimum, and maximum PRR block usage is reported.
{23658} This statistic is pegged for both GPRS and EGPRS events.
12-88 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GPRS_PRR_BLK_USG
Analysis
Reference None.
Usage Performance management.
Basis Cell.
Type Normal distribution.
68P02901W56-Q 12-89
24 May 2004 CONTROLLED INTRODUCTION
GPRS_RACH_ARRIVAL Chapter 12: PCU statistics
GPRS_RACH_ARRIVAL
{4441}
Description
The GPRS_RACH_ARRIVAL statistic tracks the mean, minimum, and maximum number
of GPRS RACH request arrivals over CCCH.
The bin ranges may be changed using the chg_stat_prop command. The default bin ranges
for the GPRS_RACH_ARRIVAL statistic are shown in
Bin Range
0 0 to 2
1 3 to 5
2 6 to 10
3 11 to 20
4 21 to 40
5 41 to 60
6 61 to 80
7 81 to 100
8 101 to 125
9 126 to 160
Pegging
This statistic is measured by sampling the GPRS RACH over CCCH at a predefined interval:
approximately one second (four multiframes). The total GPRS RACH requests over CCCH during
the time is obtained and the appropriate bin is updated. At the end of the report of the statistical
interval, the mean, minimum, and maximum PRR block usage is reported.
{23658} This statistic is pegged for both GPRS and EGPRS events.
12-90 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GPRS_RACH_ARRIVAL
Analysis
Reference None.
Usage Performance management.
Basis Cell.
Type Normal distribution.
68P02901W56-Q 12-91
24 May 2004 CONTROLLED INTRODUCTION
IDLE_PDTCH_INTF_BAND0 Chapter 12: PCU statistics
IDLE_PDTCH_INTF_BAND0
Description
The IDLE_PDTCH_INTF_BAND0 statistic tracks the maximum and mean number of idle uplink
Packet Data Traffic CHannels (PDTCHs) for interference band 0. An idle PDTCH falls into band 0 if
its average interference band is less than the value of the element interfer_bands, 0.
Idle PDTCHs are allocated to five interference bands. Each band has an associated
statistic for tracking idle PDTCHs.
Pegging
This statistic is updated at every idle frame receipt. The PDTCH is said to be idle if it can be allocated
for a request. An idle PDTCH will fall into band 0 if its idle interference level is less than the value
of the elements interfer_bands 0. The mean and max are calculated from the samples.
Analysis
This statistic can be used for trend analysis of idle packet data traffic channels.
12-92 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application IDLE_PDTCH_INTF_BAND1
IDLE_PDTCH_INTF_BAND1
Description
The IDLE_PDTCH_INTF_BAND1 statistic tracks the maximum and mean number of idle uplink
Packet Data Traffic CHannels (PDTCHs) for interference band 1. An idle PDTCH falls into band 1 if
its average interference band is less than the value of the element interfer_bands, 1.
Idle PDTCHs are allocated to five interference bands. Each band has an associated
statistic for tracking idle PDTCHs.
Pegging
This statistic is updated at every idle frame receipt. The PDTCH is said to be idle if it can be allocated
for a request. An idle PDTCH will fall into band 1 if its idle interference level is less than the value
of the elements interfer_bands 1. The mean and max are calculated from the samples.
Analysis
This statistic can be used for trend analysis of idle packet data traffic channels.
68P02901W56-Q 12-93
24 May 2004 CONTROLLED INTRODUCTION
IDLE_PDTCH_INTF_BAND2 Chapter 12: PCU statistics
IDLE_PDTCH_INTF_BAND2
Description
The IDLE_PDTCH_INTF_BAND2 statistic tracks the maximum and mean number of idle uplink
Packet Data Traffic CHannels (PDTCHs) for interference band 2. An idle PDTCH falls into band 2 if
its average interference band is less than the value of the element interfer_bands, 2.
Idle PDTCHs are allocated to five interference bands. Each band has an associated
statistic for tracking idle PDTCHs.
Pegging
This statistic is updated at every idle frame receipt. The PDTCH is said to be idle if it can be allocated
for a request. An idle PDTCH will fall into band 2 if its idle interference level is less than the value
of the elements interfer_bands 2. The mean and max are calculated from the samples.
Analysis
This statistic can be used for trend analysis of idle packet data traffic channels.
12-94 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application IDLE_PDTCH_INTF_BAND3
IDLE_PDTCH_INTF_BAND3
Description
The IDLE_PDTCH_INTF_BAND3 statistic tracks the maximum and mean number of idle uplink
Packet Data Traffic CHannels (PDTCHs) for interference band 3. An idle PDTCH falls into band 3 if
its average interference band is less than the value of the element interfer_bands, 3.
Idle PDTCHs are allocated to five interference bands. Each band has an associated
statistic for tracking idle PDTCHs.
Pegging
This statistic is updated at every idle frame receipt. The PDTCH is said to be idle if it can be allocated
for a request. An idle PDTCH will fall into band 3 if its idle interference level is less than the value
of the elements interfer_bands 3. The mean and max are calculated from the samples.
Analysis
This statistic can be used for trend analysis of idle packet data traffic channels.
68P02901W56-Q 12-95
24 May 2004 CONTROLLED INTRODUCTION
IDLE_PDTCH_INTF_BAND4 Chapter 12: PCU statistics
IDLE_PDTCH_INTF_BAND4
Description
The IDLE_PDTCH_INTF_BAND4 statistic tracks the maximum and mean number of idle uplink
Packet Data Traffic CHannels (PDTCHs) for interference band 4. An idle PDTCH falls into band 4 if
its average interference band is less than the value of the element interfer_bands, 4.
Idle PDTCHs are allocated to five interference bands. Each band has an associated
statistic for tracking idle PDTCHs.
Pegging
This statistic is updated at every idle frame receipt. The PDTCH is said to be idle if it can be allocated
for a request. An idle PDTCH will fall into band 4 if its idle interference level is less than the value
of the elements interfer_bands 4. The mean and max are calculated from the samples.
Analysis
This statistic can be used for trend analysis of idle packet data traffic channels.
12-96 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application IMM_ASSGN_CAUSE
IMM_ASSGN_CAUSE
Description
This statistic measures the successful immediate assignment procedures, per cause. This statistic is obtained
by measuring the number of IMMEDIATE ASSIGN COMMAND messages transmitted, per cause. This
message contains either an IMMEDIATE ASSIGNMENT message or IMMEDIATE ASSIGNMENT
EXTENDED message. If an IMMEDIATE ASSIGNMENT EXTENDED message is transmitted, the
counter is incremented by two, because it contains assignment information for two MSs otherwise the counter
is incremented by one. The associated bins, identifiers and establishment causes are defined in Table 12-22.
Pegging
This statistic is pegged once for every time the BSS sends an Immediate Assignment (IA) for any of
the specified purposes over the air. IAs for other purposes are not pegged.
This statistic pegs the cause of each IMMEDIATE ASSIGN COMMAND message. If this message
contains an IMMEDIATE ASSIGNMENT message, the cause is pegged once. If this message contains
an IMMEDIATE ASSIGNMENT EXTENDED message, the cause is pegged twice.
68P02901W56-Q 12-97
24 May 2004 CONTROLLED INTRODUCTION
IMM_ASSGN_CAUSE Chapter 12: PCU statistics
Analysis
It represents the total number of IAs pegged during the statistics interval, on a per-cause basis.
Reference Digital cellular telecommunications systems (phase 2+) Version
7.0.0 Jan 2000 ETSI.
Usage The statistic is used for monitoring areas where lots of calls
originate: the operator may wish to charge more for calls made in
these high-traffic zones.
It is also used for monitoring the number of calls undergoing
re-establishment. High numbers of calls undergoing
re-establishment means the RF coverage in an area may have a hole.
Comparing the uplink against downlink GPRS usage tells the
operator how to set the Beta value for a cell (Interleaving TBFs
feature). This allows for better throughput based upon the mobile
subscriber preferences in any particular area.
Basis Cell.
Type Counter array.
12-98 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MS_CLASS_1_10_REQ
MS_CLASS_1_10_REQ
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
The MS_CLASS_1_10_REQ statistic tracks the number of requests received for the MS classes 1 through 10.
Each bin corresponds to a particular MS class as shown in Table 12-23.
Pegging
This is one of three statistics that is pegged every time there is an uplink request from an MS. The
other two are MS_CLASS_11_20_REQ and MS_CLASS_21_29_REQ.
68P02901W56-Q 12-99
24 May 2004 CONTROLLED INTRODUCTION
MS_CLASS_1_10_REQ Chapter 12: PCU statistics
Pegging is performed only for uplink requests received on the CCCH, not for
uplink requests included in the PDAK message.
12-100 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MS_CLASS_11_20_REQ
MS_CLASS_11_20_REQ
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
The MS_CLASS_11_20_REQ statistic tracks the number of requests received for the MS classes 11 through 20.
Each bin corresponds to a particular MS class as shown in Table 12-24.
Pegging
This is one of three stats that is pegged every time there is an uplink request from an MS. The
other two are MS_CLASS_1_10_REQ and MS_CLASS_21_29_REQ.
68P02901W56-Q 12-101
24 May 2004 CONTROLLED INTRODUCTION
MS_CLASS_11_20_REQ Chapter 12: PCU statistics
Pegging is performed only for uplink requests received on the CCCH, not for
uplink requests included in the PDAK message.
12-102 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MS_CLASS_21_29_REQ
MS_CLASS_21_29_REQ
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
Pegging
This is one of three stats that is pegged every time there is an uplink request from an MS. The
other two are MS_CLASS_1_10_REQ and MS_CLASS_11_20_REQ.
68P02901W56-Q 12-103
24 May 2004 CONTROLLED INTRODUCTION
MS_CLASS_21_29_REQ Chapter 12: PCU statistics
Pegging is performed only for uplink requests received on the CCCH, not for
uplink requests included in the PDAK message.
12-104 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application NO_PDTCH_AVAIL
NO_PDTCH_AVAIL
Description
Pegging
When the last PDTCH available is taken for a voice call, the count is incremented.
Reference None.
Usage Network planning.
Network accessibility.
Basis Cell.
Type Counter.
68P02901W56-Q 12-105
24 May 2004 CONTROLLED INTRODUCTION
NO_PDTCH_AVAIL_TIME Chapter 12: PCU statistics
NO_PDTCH_AVAIL_TIME
Description
Pegging
When the last PDTCH available is taken for a voice call, the timer is started and stopped
when at least one PDTCH becomes available.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum acceptable time that no
PDTCHs are available for any of the start/stop time periods. If the specified threshold is exceeded, the
Total time all PDTCHs are unavailable - PM alarm is generated. Refer to the Maintenance Information:
Alarm Handling at the OMC-R (68P02901W26) for troubleshooting information.
Reference None.
Usage Network planning.
Network accessibility.
Basis Cell.
Type Duration.
12-106 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application PRP_LOAD
PRP_LOAD
Description
This statistic measures the load of the Packet Resource Processor (PRP) board. The BSS transfers
data for 30 DL and 30 UL TBFs, and processes control messages for 90 UL and 90 DL TBFs in one
20 millisecond block period. The load of the PRP board is determined by measuring the number of
timeslots pending service for data transfers within a 20 millisecond block period.
Table 12-26 shows the mapping between the number of timeslots pending service and the PRP load.
The statistic is kept on a per DPROC basis.
Table 12-26 Mapping between timeslots pending service and PRP load
Table 12-27 shows the PRP load ranges for each bin of this statistic.
68P02901W56-Q 12-107
24 May 2004 CONTROLLED INTRODUCTION
PRP_LOAD Chapter 12: PCU statistics
Pegging
This statistic pegs the appropriate bin every 20 millisecond based on the number of timeslots
pending service and the bin range values that the customer configured.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Analysis
This statistic can be used for trend analysis of the network load on a PRP board. Each bin can be analysed
to determine the number of occurrences the PRP had a certain percentage of load on it.
Reference None.
Usage Network planning, congestion.
Basis This statistic is based on each DPROC.
Type Normal Distribution.
12-108 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application UL_BUSY_PDTCH
UL_BUSY_PDTCH
Description
This statistic measures the mean, max and min number of occupied Packet Data
CHannel (PDCH) carrying uplink packet traffic.
This statistic is obtained by sampling the PDTCH, which are carrying packet traffic, at
every packet-scheduling period (20 millisecond).
Table 12-28 shows the ranges for each bin (measured in milliseconds).
Bin Range
0 No PDTCH is busy
1 1-2 PDTCH are busy
2 3-4 PDTCH are busy
3 5-6 PDTCH are busy
4 7-8 PDTCH are busy
5 9-10 PDTCH are busy
6 11-12 PDTCH are busy
7 13-14 PDTCH are busy
8 15-16 PDTCH are busy
9 17-400 PDTCH are busy
Pegging
This statistic pegs every packet-scheduling period (20 millisecond) by sampling the number
of PDTCHs that are carrying uplink packet traffic.
{23658} This statistic is pegged for both GPRS and EGPRS events.
68P02901W56-Q 12-109
24 May 2004 CONTROLLED INTRODUCTION
UL_BUSY_PDTCH Chapter 12: PCU statistics
Analysis
This statistic can be used for trend analysis of the number of PDTCHs that are used for uplink packet traffic.
Reference Digital cellular telecommunications systems (phase 2+) Version
7.0.0 Jan 2000 ETSI.
Usage Network planning, congestion.
Basis Cell.
Type Weighted distribution.
12-110 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application UL_PDTCH_CONGESTION
UL_PDTCH_CONGESTION
Description
The UL_PDTCH_CONGESTION statistic calculates the number of times a cell is congested due to
MS load on the available air resources on the uplink. Whenever the uplink resources are determined
to be congested, the statistic is updated. When the value of the statistic is large, it indicates that
the cell is congested and more radio resources may need to be provisioned.
Pegging
The PDTCH congestion is computed every 8s (8000ms) in 20ms block periods when the congestion threshold
is reached. The congestion threshold is configurable with values ranging from 1-4. Level 1 means averagely
one TBF per TS on a cell is considered congested. Level 4 means four TBFs per TS are considered congested.
This is synonymous with the concept that one PDTCH can be shared by, at most, 4 MSs.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Analysis
This statistic is totalled in terms of 20 millisecond block periods.
68P02901W56-Q 12-111
24 May 2004 CONTROLLED INTRODUCTION
UL_PDTCH_Q_LENGTH Chapter 12: PCU statistics
UL_PDTCH_Q_LENGTH
Description
This statistic is obtained by sampling the Uplink Request Queue. Queued messages
are RACH, PRACH and PRR.
Pegging
This statistic pegs every 20ms. It is incremented when a request is added to the queue and is
decremented when a request is processed, that is, leaves the queue.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Analysis
This statistic can be used for the trend analysis of the average number of uplink messages
waiting for a PDTCH to become available.
This statistic can be used for trend analysis of the number of queued uplink PDTCH requests.
12-112 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application UL_PDTCH_SEIZURE
UL_PDTCH_SEIZURE
Description
This statistic measures successful Packet Data Traffic CHannel (PDTCH) seizure on the uplink. The purpose
of this statistic is to count the number of temporary block flows (TBF) on the uplink. The statistic is obtained
by measuring the receipt of the first RLC block (PDU) on the PDTCH from the MS (uplink).
Pegging
This statistic pegs when the receipt of the first uplink RLC block (PDU) on the PDTCH from the MS is obtained.
This statistic pegs when:
• The first uplink data block is received during a two-phase uplink TBF establishment.
• A first uplink data block containing a valid Temporary Logical Link Identity (TLLI)
is received during a one-phase uplink TBF establishment.
{23658} This statistic is pegged for both GPRS and EGPRS events.
Analysis
This statistic can be used for the trend analysis of the total number of TBFs on the downlink for a CELL.
68P02901W56-Q 12-113
24 May 2004 CONTROLLED INTRODUCTION
UL_RADIO_BLKS_8PSK_1_TS Chapter 12: PCU statistics
UL_RADIO_BLKS_8PSK_1_TS
{23658}
Description
The UL_RADIO_BLKS_8PSK_1_TS statistic counts the total number of RLC radio blocks
received from EGPRS mobiles capable of 8PSK on the uplink that support a maximum of 1 TS
in the uplink direction (mobile multislot classes 1, 2, 4, and 8).
100 RLC radio blocks = 1 unit. The maximum recommended interval is 60 minutes. The translation
of actual radio blocks counted to units is performed at the end of the interval.
The RLC radio blocks are split into the four GPRS coding schemes (CS-1 through CS-4) and nine
EGPRS coding schemes (MCS-1 through MCS-9), as shown in Table 12-29.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
12-114 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application UL_RADIO_BLKS_8PSK_1_TS
In coding schemes MCS-7 through MSC-9, there are two RLC blocks in a radio block. The data shown
in the following table is used to determine which statistic must be pegged for possible combinations of
NEW, NACK, ACK_PEND and STALL when transmitting MCS-7, MCS-8 or MCS-9.
Pegging
This statistic counts the RLC radio blocks for EGPRS mobiles capable of 8PSK on the uplink
that support a maximum 1 TS in the uplink direction. Only RLC radio blocks are counted. No
retransmissions due to any cause shall be pegged in this statistic. The RLC radio blocks are
counted per coding scheme, therefore pegging the appropriate bin.
This statistic also pegs for 8PSK mobiles whose multislot class is not known before the end of the UL
TBF. The accuracy of this statistic may be reduced due to these unknown multi-slot cases.
Analysis
Reference None
Usage
Basis Cell
Type Extra large counter array
68P02901W56-Q 12-115
24 May 2004 CONTROLLED INTRODUCTION
UL_RADIO_BLKS_8PSK_2_TS Chapter 12: PCU statistics
UL_RADIO_BLKS_8PSK_2_TS
{23658}
Description
The UL_RADIO_BLKS_8PSK_2_TS statistic counts the total number of RLC radio blocks
received from EGPRS mobiles capable of 8PSK on the uplink that support a maximum of 2 TS
in the uplink direction (mobile multislot classes 3, 5, 6, 9, and 10).
100 RLC radio blocks = 1 unit. The maximum recommended interval is 60 minutes. The translation
of actual radio blocks counted to units is performed at the end of the interval.
The RLC radio blocks are split into the four GPRS coding schemes (CS-1 through CS-4) and nine
EGPRS coding schemes (MCS-1 through MCS-9), as shown in Table 12-30.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
12-116 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application UL_RADIO_BLKS_8PSK_2_TS
In coding schemes MCS-7 through MSC-9, there are two RLC blocks in a radio block. The data shown
in the following table is used to determine which statistic must be pegged for possible combinations of
NEW, NACK, ACK_PEND and STALL when transmitting MCS-7, MCS-8 or MCS-9.
Multislot class 7, 11 and 12 that support more than 2 timeslots on the uplink will be treated as 2-uplink capable.
Multislot class 13 will be treated as multislot class 9.
Multislot classes 14–29 will be treated as multislot class 10.
Pegging
This statistic counts the RLC radio blocks for EGPRS mobiles capable of 8PSK on the uplink
that support a maximum 2 TS in the uplink direction. Only RLC radio blocks are counted. No
retransmissions due to any cause are pegged in this statistic. The RLC radio blocks are counted
per coding scheme, therefore pegging the appropriate bin.
Analysis
Reference None
Usage
Basis Cell
Type Extra large counter array
68P02901W56-Q 12-117
24 May 2004 CONTROLLED INTRODUCTION
UL_RADIO_BLKS_GMSK_1_TS Chapter 12: PCU statistics
UL_RADIO_BLKS_GMSK_1_TS
{23658}
Description
The UL_RADIO_BLKS_GMSK_1_TS statistic counts the total number of RLC radio blocks received from
GPRS and EGPRS mobiles that support a maximum of 1 TS in the uplink direction (mobile multislots
classes 1, 2, 4 and 8). The EGPRS mobile is not capable of supporting 8PSK in the uplink.
This statistic also pegs mobiles whose multislot class is not known before the end of the UL TBF. The
accuracy of this statistic may be reduced due to these unknown multi-slot cases.
100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation of
actual radio blocks counted to units is performed at the end of the interval.
The RLC radio blocks are split into the four GPRS channel coding schemes, and the four
GMSK EGPRS coding schemes, as shown in Table 12-31.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
Pegging
This statistic counts the RLC radio blocks for mobiles that support a maximum of 1 TS in the uplink direction.
Only RLC radio block is counted. No retransmissions due to any cause are pegged in this statistic. The
RLC radio blocks are counted per coding scheme therefore pegging the appropriate bin.
12-118 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application UL_RADIO_BLKS_GMSK_1_TS
Analysis
Reference None
Usage
Basis Cell
Type Medium counter array
68P02901W56-Q 12-119
24 May 2004 CONTROLLED INTRODUCTION
UL_RADIO_BLKS_GMSK_2_TS Chapter 12: PCU statistics
UL_RADIO_BLKS_GMSK_2_TS
{23658}
Description
The UL_RADIO_BLKS_GMSK_2_TS statistic counts the total number of RLC radio blocks received
from GPRS mobiles and EGPRS mobiles not capable of supporting 8PSK in the uplink that support
a maximum of 2 TS in the uplink direction (mobile multislot classes 3, 5, 6, 9 and 10).
This statistic also pegs mobiles whose multislot class is not known before the end of the UL TBF. The
accuracy of this statistic may be reduced due to these unknown multi-slot cases.
100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation of
actual radio blocks counted to units is performed at the end of the interval.
The RLC radio blocks are split into the four GPRS channel coding schemes and the four
GMSK EGPRS coding schemes, as shown in Table 12-32.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
Multislot class 7, 11 and 12 that support more than 2 timeslots on the uplink will be treated as 2-uplink capable.
Multislot class 13 will be treated as multislot class 9.
Multislot classes 14–29 will be treated as multislot class 10.
Pegging
This statistic counts the RLC radio blocks for mobiles that support a maximum of 2 TS in the uplink direction.
Only RLC radio blocks are counted. No retransmissions due to any cause are pegged in this statistic. The
RLC radio blocks are counted per coding scheme therefore pegging the appropriate bin.
12-120 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application UL_RADIO_BLKS_GMSK_2_TS
Analysis
Reference None
Usage
Basis Cell
Type Medium counter array
68P02901W56-Q 12-121
24 May 2004 CONTROLLED INTRODUCTION
UL_RLC_ACK_NEW_BLKS Chapter 12: PCU statistics
UL_RLC_ACK_NEW_BLKS
{23658}
Description
The UL_RLC_ACK_NEW_BLKS statistic measures the total number of new RLC acknowledge
mode blocks received by the PCU over the cell.
100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation of
actual radio blocks counted to units is performed at the end of the interval.
The RLC radio blocks are split into the four GPRS channel coding schemes and the nine
EGPRS coding schemes, as shown in Table 12-33.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
12-122 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application UL_RLC_ACK_NEW_BLKS
In coding schemes MCS-7 through MSC-9, there are two RLC blocks in a radio block. The data shown
in the following table is used to determine which statistic must be pegged for possible combinations of
NEW, NACK, ACK_PEND and STALL when transmitting MCS-7, MCS-8 or MCS-9.
Pegging
This statistic counts the new RLC acknowledged radio blocks that are received on a cell. The RLC
radio blocks are counted per coding scheme, therefore pegging the appropriate bin.
Analysis
Reference None
Usage
Basis Cell
Type Extra large counter array
68P02901W56-Q 12-123
24 May 2004 CONTROLLED INTRODUCTION
UL_RLC_RETX_BLKS Chapter 12: PCU statistics
UL_RLC_RETX_BLKS
{23658}
Description
The UL_RLC_RETX_BLKS statistic measures the total number of pre-emptive retransmissions (or ack
pending blocks and acknowledged retransmissions) received by the PCU over the cell.
100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation of
actual radio blocks counted to units is performed at the end of the interval.
The RLC radio blocks are split into the four GPRS channel coding schemes and the nine
EGPRS coding schemes, as shown in Table 12-34.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
12-124 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application UL_RLC_RETX_BLKS
In coding schemes MCS-7 through MSC-9, there are two RLC blocks in a radio block. The data shown
in the following table is used to determine which statistic must be pegged for possible combinations of
NEW, NACK, ACK_PEND and STALL when transmitting MCS-7, MCS-8 or MCS-9.
Pegging
This statistic counts the RLC ack pending (or pre-emptive transmissions) radio blocks that are received on a
cell. The RLC radio blocks are counted per coding scheme, therefore pegging the appropriate bin.
Analysis
Reference None
Usage
Basis Cell
Type Extra large counter array
68P02901W56-Q 12-125
24 May 2004 CONTROLLED INTRODUCTION
UL_RLC_UNACK_NEW_BLKS Chapter 12: PCU statistics
UL_RLC_UNACK_NEW_BLKS
{23658}
Description
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
12-126 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application UL_RLC_UNACK_NEW_BLKS
In coding schemes MCS-7 through MSC-9, there are two RLC blocks in a radio block. The data shown
in the following table is used to determine which statistic must be pegged for possible combinations of
NEW, NACK, ACK_PEND and STALL when transmitting MCS-7, MCS-8 or MCS-9.
Pegging
This statistic counts the new RLC unacknowledged radio blocks that are received on a cell. The RLC
radio blocks are counted per coding scheme, therefore pegging the appropriate bin.
Analysis
Reference None
Usage
Basis Cell
Type Extra large counter array
68P02901W56-Q 12-127
24 May 2004 CONTROLLED INTRODUCTION
UL_TBF_TIME_8PSK_1_TS Chapter 12: PCU statistics
UL_TBF_TIME_8PSK_1_TS
{23658}
Description
The UL_TBF_TIME_8PSK_1_TS statistic measures the duration in time (the cumulative length
in number of 20ms radio block periods) of the uplink TBFs for EGPRS mobiles that support a
maximum of 1 TS and capable of 8PSK in the uplink direction.
Pegging
This statistic pegs the time of all the TBFs in the uplink for mobiles that support a maximum of 1 TS
and capable of 8PSK in the uplink direction. At the end of the statistical interval this statistic provides a
cumulative value of all the UL TBF times for mobiles supporting a maximum of 1 TS. The TBF time starts
with the set-up of the TBF and finishes when all the uplink RLC radio blocks have been received without error.
This statistic also pegs for 8PSK mobiles whose multislot class is not known before the end of the UL
TBF. The accuracy of this statistic may be reduced due to these unknown multi-slot cases.
Analysis
Reference None
Usage
Basis Cell
Type Counter
12-128 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application UL_TBF_TIME_8PSK_2_TS
UL_TBF_TIME_8PSK_2_TS
{23658}
Description
The UL_TBF_TIME_8PSK_2_TS statistic measures the duration in time (the cumulative length
in number of 20ms radio block periods) of the uplink TBFs for EGPRS mobiles that support a
maximum of 2 TS and capable of 8PSK in the uplink direction.
Pegging
This statistic pegs the time of all the TBFs in the uplink for mobiles that support a maximum of 2 TS
and capable of 8PSK in the uplink direction. At the end of the statistical interval this statistic provides a
cumulative value of all the UL TBF times for mobiles supporting a maximum of 2 TS. The TBF time starts
with the set-up of the TBF and finishes when all the uplink RLC radio blocks have been received without error.
Analysis
Reference None
Usage
Basis Cell
Type Counter
68P02901W56-Q 12-129
24 May 2004 CONTROLLED INTRODUCTION
UL_TBF_TIME_GMSK_1_TS Chapter 12: PCU statistics
UL_TBF_TIME_GMSK_1_TS
{23658}
Description
Pegging
This statistic measures the time of all the TBFs in the uplink for mobiles that support a maximum of 1 TS
in the uplink direction. At the end of the statistical interval this statistic provides a cumulative value of all
the UL TBF times for mobiles supporting a maximum of 1 TS. The TBF time starts with the set-up of
the TBF and finishes when all the uplink RLC radio blocks have been received without error.
Analysis
Reference None
Usage
Basis Cell
Type Counter
12-130 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application UL_TBF_TIME_GMSK_2_TS
UL_TBF_TIME_GMSK_2_TS
{23658}
Description
The UL_TBF_TIME_GMSK_2_TS statistic counts the cumulative length in number of 20ms radio
block periods of all uplink TBFs for GPRS and EGPRS mobiles that support a maximum of 2 TS in the
uplink direction. The EGPRS mobile is not capable of supporting 8PSK in the uplink.
Pegging
This statistic measures the time of all the TBFs in the uplink for mobiles that support a maximum of 2 TS
in the uplink direction. At the end of the statistical interval this statistic provides a cumulative value of all
the UL TBF times for mobiles supporting a maximum of 2 TS. The TBF time starts with the set-up of
the TBF and finishes when all the uplink RLC radio blocks have been received without error.
Analysis
Reference None
Usage
Basis Cell
Type Counter
68P02901W56-Q 12-131
24 May 2004 CONTROLLED INTRODUCTION
UL_TBF_TIME_GMSK_2_TS Chapter 12: PCU statistics
12-132 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
13
BSS-SMLC statistics
BSS-based Serving Mobile Location Centre (SMLC) statistics track events on the signalling
link. They are categorized into subgroups, each of which are described in "BSS-based
SMLC statistics subgroups" on page 13-2.
68P02901W56-Q 13-1
24 May 2004 CONTROLLED INTRODUCTION
BSS-based SMLC statistics subgroups Chapter 13: BSS-SMLC statistics
BSS-based Serving Mobile Location Centre (SMLC) statistics are organized into two major subgroups:
• "BSS C7 utilization" on page 13-2.
BSS C7 utilization
BSS-based SMLC C7 utilization statistics track the number of messages received and transmitted
on the signalling links. This information indicates the activity level on the Signalling Links
(SLs). The following are BSS C7 utilization statistics:
• "L_SIF_SIO_RX_OPC" on page 13-8.
SCCP performance and utilization statistics track the performance of the Signalling Connection
Control Part (SCCP) protocol layer of the ITU-TSS C7.
The SCCP manages the establishment and release of call related connections. A connection is
established for each transaction. For example, location update and service request, both BSS and
BSS-based SMLC maintain contexts related to the transaction; these contexts may be identified using
the SCCP reference number. This information indicates the performance level and quality of the
SCCP. The following are the SCCP performance and utilization statistics:
• "L_ROUTING_SYNTAX" on page 13-3.
13-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application L_ROUTING_SYNTAX
L_ROUTING_SYNTAX
Description
This statistic tracks the number of SCCP messages with syntax errors.
Pegging
This statistic pegs when a syntax error is detected in an SCCP message on the Lb-interface.
Analysis
SCCP is an SS7 protocol used in transferring signalling messages between the BSC and BSS-based
SMLC. Excessive syntax errors can result in degraded SCCP performance.
A threshold value should be assigned to this statistic which reflects the maximum number of SCCP
messages with syntax errors that are acceptable in normal system operations.
If the specified threshold is exceeded, the 18. BSS: Routing failure - syntax error detected
(SMLC) - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling
at the OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage SCCP performance and utilization.
Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.
68P02901W56-Q 13-3
24 May 2004 CONTROLLED INTRODUCTION
L_ROUTING_UNKNOWN Chapter 13: BSS-SMLC statistics
L_ROUTING_UNKNOWN
Description
This statistic tracks the number of invalid signalling point codes (SPCs) that a BSC
has received from the BSS-based SMLC.
Pegging
This statistic pegs whenever an invalid SPC is received from the BSS-based SMLC.
Analysis
An SPC is the destination address for a message routed by the networking functions of the MTP3 protocol.
If the BSC receives an incorrect SPC, it will not be able to correctly route the message.
A threshold value should be assigned to this statistic which reflects the maximum number of
invalid SPCs that are acceptable in normal system operations.
If the specified threshold is exceeded, the 19. BSS: Routing failure - reason unknown
(SMLC) - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling
at the OMC-R (68P02901W26) for troubleshooting information.
13-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application L_SCCP_MSGS
L_SCCP_MSGS
Description
This statistic tracks the total number of SCCP messages either transmitted or received between
the BSC and BSS-based SMLC over an Lb-interface.
Pegging
This statistic pegs when SCCP messages are transmitted or received on the signalling
link between the BSC and BSS-based SMLC.
Analysis
SCCP is an SS7 protocol used in transferring signalling messages between the BSC and BSS-based SMLC.
This statistic can be used for trend analysis of SCCP performance and utilization.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage SCCP performance and utilization.
Basis BSS.
Type Counter.
68P02901W56-Q 13-5
24 May 2004 CONTROLLED INTRODUCTION
L_SCCP_MSGS_RX Chapter 13: BSS-SMLC statistics
L_SCCP_MSGS_RX
Description
This statistic tracks the total number of SCCP messages received by the BSC from BSS-based
SMLC over an Lb-interface for class 0 or class 2.
This statistic will switch on the appropriate device value so that the OMC can store
it in the relevant column of the database:
• the number of SCCP messages received for class 0 will be stored in l_sccp_msgs_rx_0.
• the number of SCCP messages received for class 2 will be stored in l_sccp_msgs_rx_2.
Pegging
This statistic pegs when SCCP messages are received on the signalling link between
the BSC and BSS-based SMLC.
Analysis
SCCP is an SS7 protocol used in transferring signalling messages between the BSC and BSS-based
SMLC. This statistic can be used for trend analysis of the activity on an SL.
13-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application L_SCCP_MSGS_TX
L_SCCP_MSGS_TX
Description
This statistic tracks the total number of SCCP messages transmitted by the BSC to BSS-based
SMLC over the Lb-interface for class 0 or class 2.
This statistic will switch on the appropriate device value so that the OMC can store
it in the relevant column of the database:
• the number of SCCP messages transmitted for class 0 will be stored in l_sccp_msgs_tx_0.
• the number of SCCP messages transmitted for class 2 will be stored in l_sccp_msgs_tx_2.
Pegging
This statistic pegs when SCCP messages are transmitted on the signalling link.
Analysis
SCCP is an SS7 protocol used in transferring signalling messages between the BSC and BSS-based
SMLC. This statistic can be used for trend analysis of the activity over the Lb-interface.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage SCCP performance and utilization.
Basis BSS.
Type Counter.
68P02901W56-Q 13-7
24 May 2004 CONTROLLED INTRODUCTION
L_SIF_SIO_RX_OPC Chapter 13: BSS-SMLC statistics
L_SIF_SIO_RX_OPC
Description
This statistic tracks the total number of SIF and SIOs received on all SLs for the BSS from BSS-based SMLC.
Pegging
This statistic pegs each time Signal Information Fields (SIF) or Service Information Octets (SIO) are
received across all signalling links between the BSS and BSS-based SMLC.
Analysis
SCCP is an SS7 protocol used in transferring signalling messages between the BSC and BSS-based SMLC.
This statistic can be used for trend analysis of the activity on all Lb-interface SLs for a particular BSS.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 utilization.
Basis BSS.
Type Counter.
13-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application L_SIF_SIO_TX_DPC
L_SIF_SIO_TX_DPC
Description
This statistic tracks the total number of Signal Information Fields (SIF) and Service Information Octets
(SIO) transmitted on all SLs of the BSS to the Lb-interface Destination Point Code (DPC).
Pegging
This statistic pegs each time SIF or SIO are transmitted across all signalling links from the BSS
to the BSS-based SMLC (as indicated by the Lb-interface (DPC)).
Analysis
A DPC is part of the label in a signalling message that uniquely identifies, in a signalling
network, the destination point of the message. This statistic can be used for trend analysis
of the activity of the signalling links on a BSS.
Reference GSM 12.07, 3.0.2, 2.8.6.a.
ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 utilization.
Basis BSS.
Type Counter.
68P02901W56-Q 13-9
24 May 2004 CONTROLLED INTRODUCTION
L_SIF_SIO_TYPE Chapter 13: BSS-SMLC statistics
L_SIF_SIO_TYPE
Description
This statistic tracks the number of SIF MTP, TEST, and SCCP SIOs transmitted or
received on all Lb-interface SLs.
This statistic will switch on the appropriate device value so that the OMC can store
it in the relevant column of the database:
• the number of SIF SCCP SIOs will be stored in l_sif_sio_type.
Pegging
This statistic pegs each time SIF or SIOs are transmitted or received on all signalling
links between BSS and BSS-based SMLC.
Analysis
This statistic can be used for trend analysis of the activity of the signalling links on a BSS over the Lb-interface.
13-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application PAGE_REQ_FROM_SMLC_FAIL
PAGE_REQ_FROM_SMLC_FAIL
Description
This statistic tracks the number of page request messages received from the BSS-based
SMLC that fail message validation at the BSS.
Pegging
This statistic pegs each time a page request message from the BSS-based SMLC
fails message validation at the BSS.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of
failures that are acceptable in normal system operations.
If the specified threshold is exceeded, the 20. BSS: Paging request from SMLC protocol
error - PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 8.08, 3.9.2, 3.1.10 and 3.2.1.19.
Usage Quality of service monitoring: Paging analysis.
Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.
68P02901W56-Q 13-11
24 May 2004 CONTROLLED INTRODUCTION
PAGE_REQ_FROM_SMLC_FAIL Chapter 13: BSS-SMLC statistics
13-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
14
Web MMI statistics
The MMI statistics are categorized as PCU real-time statistics and MMI BSC/BTS real-time
statistics. The descriptions for these are given elsewhere in the manual and are referenced
in "MMI statistics subgroups" on page 14-2.
68P02901W56-Q 14-1
24 May 2004 CONTROLLED INTRODUCTION
MMI statistics subgroups Chapter 14: Web MMI statistics
The following MMI PCU real-time statistics are documented elsewhere in this manual.
Table 14-1 indicates the location of these descriptions.
The following MMI BSC/BTS real-time statistics are documented elsewhere in this manual.
Table 14-2 indicates the location of these descriptions.
14-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
15
HR and AMR statistics
Half Rate (HR) and Adaptive Multi-Rate (AMR) statistics are used to gauge performance of
systems employing Half Rate and AMR full-rate link adaptation.
The HR statistics group is shown in "HR statistics group" on page 15-2.
The AMR statistics group is shown in "AMR statistics group" on page 15-3.
68P02901W56-Q 15-1
24 May 2004 CONTROLLED INTRODUCTION
HR statistics group Chapter 15: HR and AMR statistics
HR statistics group
{22064}
The group of Half Rate statistics are listed below:
The following statistics have been modified or created as a result of the GSM Half Rate feature.
•
15-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application AMR statistics group
The following statistics have been modified as a result of the AMR feature:
• "AMR_DECREASE_THRESH_ADJUST" on page 15-7
68P02901W56-Q 15-3
24 May 2004 CONTROLLED INTRODUCTION
ALLOC_TCH_FAIL_HR Chapter 15: HR and AMR statistics
ALLOC_TCH_FAIL_HR
Description
The statistic tracks the number of unsuccessful allocations of a half rate AMR and/or
GSM TCH within a cell for both call origination and hand in. Cases involving Immediate
Assignment Reject are also included in the peg count.
Pegging
This statistic pegs when an attempt to allocate a half rate AMR and/or GSM TCH
in a cell fails due to a lack of resources:
• Unsuccessful allocation due to call establishment including unsuccessful
allocations due to directed retries.
15-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application ALLOC_TCH_FAIL_HR
Upon failure to allocate a channel, the channel allocation failure statistic is pegged for all
the allowed channel rates. Here are some channel allocation failure scenarios:
• If a speech call for which the channel type is full rate and half rate, a failure in allocating a
channel results in both ALLOC_TCH_FAIL and ALLOC_TCH_FAIL_HR being pegged.
• ALLOC_TCH_FAIL_HR is pegged for a speech call for which the channel
type specifies both full rate and half rate (with half rate preferred) but resulting
in a full rate channel being allocated.
• When there is a failure to allocate a half rate channel, both ALLOC_TCH_FAIL
and ALLOC_TCH _FAIL_HR are pegged.
• If the channel type is half rate preferred/full rate non-preferred OR full rate preferred/half
rate non-preferred and neither channel type is allocated (a complete TCH allocation failure
scenario), the ALLOC_TCH_FAIL shall be pegged twice and ALLOC_TCH_FAIL_HR
stat shall be pegged once. That is, once for failed FR and once for failed HR.
• When the non-preferred channel type is successfully assigned a channel, a
failure shall be pegged for the preferred type.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of half rate AMR
and/or GSM TCH failures due to congestion that are acceptable in normal system operations.
68P02901W56-Q 15-5
24 May 2004 CONTROLLED INTRODUCTION
ALLOC_TCH_HR Chapter 15: HR and AMR statistics
ALLOC_TCH_HR
Description
The statistic tracks the number of successful half rate AMR and/or GSM TCH allocations
within a cell for both call originations and hand ins.
Pegging
This statistic pegs for successful half rate AMR and/or GSM TCH allocations within a cell
as a result of a call establishment or hand in attempt:
• Successful allocation due to call establishment including successful allocations
due to incoming directed retries.
This statistic pegs before the transmission of the assignment/handover command to the MS and, therefore,
does not take into account the success or failure of the assignment/hand in from an RF perspective.
Analysis
This statistic can be used for trend analysis of half rate AMR and/or GSM TCH allocations.
Reference None.
Usage Quality of service monitoring: Call setup.
Network planning.
Ladder: Intra-BSS handover, Inter-BSS handover, Intra-cell
handover, Assignment to TCH.
Basis Cell.
Type Counter.
15-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application AMR_DECREASE_THRESH_ADJUST
AMR_DECREASE_THRESH_ADJUST
{4322}
Description
The AMR_INCREASE_THRESH_ADJUST statistic keeps a count of the number of times that the BSS
MS monitor decreases the C/I codec mode adaptation thresholds for AMR calls on a per-cell basis.
Pegging
This statistic pegs each time that the BSS MS monitor decreases the downlink codec mode
adaptation thresholds due to inaccurate C/I estimation by the MS.
Reference None.
Usage Radio resource allocation.
Network planning.
Basis Cell.
Type Counter.
68P02901W56-Q 15-7
24 May 2004 CONTROLLED INTRODUCTION
AMR_FR_DL_CODEC_MODE_USAGE Chapter 15: HR and AMR statistics
AMR_FR_DL_CODEC_MODE_USAGE
{4322}
Description
Bin Description
0 AMR full-rate DL codec mode usage of AFS 12.2kbps
1 AMR full-rate DL codec mode usage of AFS 10.2kbps
2 AMR full-rate DL codec mode usage of AFS 7.4kbps
3 AMR full-rate DL codec mode usage of AFS 6.7kbps
4 AMR full-rate DL codec mode usage of AFS 5.15kbps
Pegging
This statistic pegs each time that a specific codec mode is used on the downlink of full-rate AMR calls.
Reference None.
Usage Radio resource allocation.
Network planning.
Basis Cell.
Type Counter array statistic.
15-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application AMR_FR_DL_ADAPTATION
AMR_FR_DL_ADAPTATION
{4322}
Description
The AMR_FR_DL_ADAPTATION statistic keeps a count of the number of times the codec mode
is adapted on the downlink of full-rate AMR calls on a per-cell basis.
There are up to four codecs in the Active Codec Set (ACS) and the format of this statistic
allows for this. The codecs are referenced sequentially from the lowest speech coding rate to
the highest. The lowest speech coding rate is called the 1st codec. If there are less than four
codecs in the ACS, the higher bit rates are not valid and contain the value zero.
The bins are:
Bin Description
0 AMR full-rate DL codec mode usage adaptation from 1st to 2nd codec mode.
1 AMR full-rate DL codec mode usage adaptation from 2nd to 3rd codec mode.
2 AMR full-rate DL codec mode usage adaptation from 3rd to 4th codec mode.
3 AMR full-rate DL codec mode usage adaptation from 2nd to 1st codec mode.
4 AMR full-rate DL codec mode usage adaptation from 3rd to 2nd codec mode.
5 AMR full-rate DL codec mode usage adaptation from 4th to 3rd codec mode.
Pegging
This statistic pegs each time that a specific codec mode is adapted on the downlink of full-rate AMR calls.
Reference None.
Usage Radio resource allocation.
Network planning.
Basis Cell.
Type Counter array statistic.
68P02901W56-Q 15-9
24 May 2004 CONTROLLED INTRODUCTION
AMR_FR_UL_ADAPTATION Chapter 15: HR and AMR statistics
AMR_FR_UL_ADAPTATION
{4322}
Description
The AMR_FR_UL_ADAPTATION statistic keeps a count of the number of times that the codec
mode is adapted on the uplink of full-rate AMR calls on a per-cell basis.
There are up to four codecs in the Active Codec Set (ACS) and the format of this statistic
allows for this. The codecs are referenced sequentially from the lowest speech coding rate to
the highest. The lowest speech coding rate is called the 1st codec. If there are less than four
codecs in the ACS, the higher bit rates are not valid and contain the value zero.
The bins are:
Bin Description
0 AMR full-rate UL codec mode usage adaptation from 1st to 2nd codec mode.
1 AMR full-rate UL codec mode usage adaptation from 2nd to 3rd codec mode.
2 AMR full-rate UL codec mode usage adaptation from 3rd to 4th codec mode.
3 AMR full-rate UL codec mode usage adaptation from 2nd to 1st codec mode.
4 AMR full-rate UL codec mode usage adaptation from 3rd to 2nd codec mode.
5 AMR full-rate UL codec mode usage adaptation from 4th to 3rd codec mode.
Pegging
This statistic pegs each time that a specific codec mode is adapted on the uplink of full-rate AMR calls.
Reference None.
Usage Radio resource allocation.
Network planning.
Basis Cell.
Type Counter array statistic.
15-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application AMR_FR_UL_CODEC_MODE_USAGE
AMR_FR_UL_CODEC_MODE_USAGE
{4322}
Description
Bin Description
0 AMR full-rate UL codec mode usage of AFS 12.2kbps
1 AMR full-rate UL codec mode usage of AFS 10.2kbps
2 AMR full-rate UL codec mode usage of AFS 7.4kbps
3 AMR full-rate UL codec mode usage of AFS 6.7kbps
4 AMR full-rate UL codec mode usage of AFS 5.15kbps
Pegging
This statistic pegs each time that a specific codec mode is used on the uplink of full-rate AMR calls.
Reference None.
Usage Radio resource allocation.
Network planning.
Basis Cell.
Type Counter array statistic.
68P02901W56-Q 15-11
24 May 2004 CONTROLLED INTRODUCTION
AMR_HR_DL_ADAPTATION Chapter 15: HR and AMR statistics
AMR_HR_DL_ADAPTATION
{4322}
Description
The AMR_HR_DL_ADAPTATION statistic keeps a count of the number of times that the codec
mode is adapted on the downlink of half-rate AMR calls on a per-cell basis.
There are up to four codecs in the Active Codec Set (ACS) and the format of this statistic
allows for this. The codecs are referenced sequentially from the lowest speech coding rate to
the highest. The lowest speech coding rate is called the 1st codec. If there are less than four
codecs in the ACS, the higher bit rates are not valid and contain the value zero.
The bins are:
Bin Description
0 AMR half-rate DL codec mode usage adaptation from 1st to 2nd codec mode.
1 AMR half-rate DL codec mode usage adaptation from 2nd to 3rd codec mode.
2 AMR half-rate DL codec mode usage adaptation from 3rd to 4th codec mode.
3 AMR half-rate DL codec mode usage adaptation from 2nd to 1st codec mode.
4 AMR half-rate DL codec mode usage adaptation from 3rd to 2nd codec mode.
5 AMR half-rate DL codec mode usage adaptation from 4th to 3rd codec mode.
Pegging
This statistic pegs each time that a specific codec mode is adapted on the downlink of half-rate AMR calls.
Reference None.
Usage Radio resource allocation.
Network planning.
Basis Cell.
Type Counter array statistic.
15-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application AMR_HR_DL_CODEC_MODE_USAGE
AMR_HR_DL_CODEC_MODE_USAGE
{4322}
Description
Bin Description
0 AMR half-rate DL codec mode usage of AFS 7.95kbps
1 AMR half-rate DL codec mode usage of AFS 7.4kbps
2 AMR half-rate DL codec mode usage of AFS 6.7kbps
3 AMR half-rate DL codec mode usage of AFS 5.9kbps
4 AMR half-rate DL codec mode usage of AFS 5.15kbps
Pegging
This statistic pegs each time that a specific codec mode is used on the downlink of half-rate AMR calls.
Reference None.
Usage Radio resource allocation.
Network planning.
Basis Cell.
Type Counter array statistic.
68P02901W56-Q 15-13
24 May 2004 CONTROLLED INTRODUCTION
AMR_HR_UL_ADAPTATION Chapter 15: HR and AMR statistics
AMR_HR_UL_ADAPTATION
{4322}
Description
The AMR_HR_UL_ADAPTATION statistic keeps a count of the number of times that the codec
mode is adapted on the uplink of half-rate AMR calls on a per-cell basis.
There are up to four codecs in the Active Codec Set (ACS) and the format of this statistic
allows for this. The codecs are referenced sequentially from the lowest speech coding rate to
the highest. The lowest speech coding rate is called the 1st codec. If there are less than four
codecs in the ACS, the higher bit rates are not valid and contain the value zero.
The bins are:
Bin Description
0 AMR half-rate UL codec mode usage adaptation from 1st to 2nd codec mode.
1 AMR half-rate UL codec mode usage adaptation from 2nd to 3rd codec mode.
2 AMR half-rate UL codec mode usage adaptation from 3rd to 4th codec mode.
3 AMR half-rate UL codec mode usage adaptation from 2nd to 1st codec mode.
4 AMR half-rate UL codec mode usage adaptation from 3rd to 2nd codec mode.
5 AMR half-rate UL codec mode usage adaptation from 4th to 3rd codec mode.
Pegging
This statistic pegs each time that a specific codec mode is adapted on the uplink of half-rate AMR calls.
Reference None.
Usage Radio resource allocation.
Network planning.
Basis Cell.
Type Counter array statistic.
15-14 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application AMR_HR_UL_CODEC_MODE_USAGE
AMR_HR_UL_CODEC_MODE_USAGE
{4322}
Description
Bin Description
0 AMR half-rate UL codec mode usage of AFS 7.95kbps
1 AMR half-rate UL codec mode usage of AFS 7.4kbps
2 AMR half-rate UL codec mode usage of AFS 6.7kbps
3 AMR half-rate UL codec mode usage of AFS 5.9kbps
4 AMR half-rate UL codec mode usage of AFS 5.15kbps
Pegging
This statistic pegs each time that a specific codec mode is used on the uplink of half-rate AMR calls.
Reference None.
Usage Radio resource allocation.
Network planning.
Basis Cell.
Type Counter array statistic.
68P02901W56-Q 15-15
24 May 2004 CONTROLLED INTRODUCTION
AMR_INCREASE_THRESH_ADJUST Chapter 15: HR and AMR statistics
AMR_INCREASE_THRESH_ADJUST
{4322}
Description
The AMR_INCREASE_THRESH_ADJUST statistic keeps a count of the number of times that the BSS
MS monitor increases the C/I codec mode adaptation thresholds for AMR calls on a per-cell basis.
Pegging
This statistic pegs each time that the BSS MS monitor increases the downlink codec mode
adaptation thresholds due to inaccurate C/I estimation by the MS.
Reference None.
Usage Radio resource allocation.
Network planning.
Basis Cell.
Type Counter.
15-16 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application AVAILABLE_TCH_HR
AVAILABLE_TCH_HR
Description
The statistic reports a maximum and average value for the amount of half rate AMR and/or
GSM TCHs that are in use or available to be used within the cell.
Pegging
The statistic pegs whenever there is a change in the half rate AMR and/or GSM channel configuration in
the cell (if the number of TCHs has not changed, it will be pegged with the same value as before).This
statistic pegs when a change in half rate TCH availability is detected.
An idle generic timeslot is counted as one available full rate channel and
two available half rate channels.
Reference None.
Usage Radio resource allocation.
Quality of service monitoring.
Network planning.
Service retainability.
Basis Cell.
Type Gauge statistic.
68P02901W56-Q 15-17
24 May 2004 CONTROLLED INTRODUCTION
BUSY_TCH_CARR_HR Chapter 15: HR and AMR statistics
BUSY_TCH_CARR_HR
Description
The statistic reports a maximum and average value for the amount of half rate AMR
and/or GSM TCHs in use on a per carrier basis.
Pegging
This statistic is updated each time an allocation or deallocation of a half rate AMR and/or GSM TCH occurs.
Reference None.
Usage Radio resource allocation.
Quality of service monitoring.
Network planning.
Service retainability.
Basis Carrier.
Type Gauge statistic.
15-18 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application BUSY_TCH_HR
BUSY_TCH_HR
Description
The statistic reports a maximum and average value for the amount of half rate AMR and/or GSM TCHs in use.
Pegging
This statistic is updated each time an allocation or deallocation of a half rate AMR and/or GSM TCH occurs.
Reference None.
Usage Radio resource allocation.
Quality of service monitoring.
Network planning.
Service retainability.
Basis Cell.
Type Weighted distribution.
68P02901W56-Q 15-19
24 May 2004 CONTROLLED INTRODUCTION
FER_AMR_FR Chapter 15: HR and AMR statistics
FER_AMR_FR
{4322}
Description
The uplink FER_AMR_FR Quality statistic is derived from a ratio of successfully decoded
good speech frames against unsuccessfully decoded bad frames for AMR full- rate calls. The
measurement period over which the calculation is made is 480 ms.
During this period, 24 speech frames are decoded and a ratio calculated. By referring to a lookup
table, the ratio is then converted to a FER_AMR_FR Quality number between 0 and 9.
For example: two bad frames out of 24 results in a ratio of 0.083:1. From the lookup table,
Table 15-1, this relates to an FER_AMR_FR Quality number of 2.
Pegging
This statistic pegs the uplink frame erasure rate for AMR full-rate calls for each carrier in a cell.
Units
The FER_AMR_FR is reported using values 0 to 9 as follows.
FER_AMR_FR Quality
FER_AMR_FR Quality number
number
0 0.0000 to 0.0416
1 0.0417 to 0.0832
2 0.0833 to 0.1249
3 0.1250 to 0.1666
4 0.1667 to 0.2082
5 0.2083 to 0.2499
6 0.2500 to 0.2916
7 0.2917 to 0.3332
8 0.3333 to 0.3749
9 0.3750 to 1.0000
FER_AMR_FR Quality is measured on a timeslot basis for active channels after decoding
de-interleaving and error correction. Data for this statistic is reported by firmware to the
RSS/HO software process where it is pegged.
The values of the bins are fixed and are not adjustable by the operator.
15-20 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application FER_AMR_FR
Analysis
This statistic can be used for trend analysis for target optimization effects on cell/radios with regards to quality.
Reference None.
Usage Quality of service, Fault finding, RF loss, Congestion.
Basis Carrier.
Type Normal distribution.
68P02901W56-Q 15-21
24 May 2004 CONTROLLED INTRODUCTION
FER_AMR_HR Chapter 15: HR and AMR statistics
FER_AMR_HR
{4322}
Description
The uplink FER_AMR_HR Quality statistic is derived from a ratio of successfully decoded
good speech frames against unsuccessfully decoded bad frames for AMR half rate calls. The
measurement period over which the calculation is made is 480 ms.
During this period, 24 speech frames are decoded and a ratio calculated. By referring to a lookup table,
the ratio is then converted to a FER_AMR_HR Quality number between 0 and 9.
For example: two bad frames out of 24 results in a ratio of 0.083:1. From the lookup table,
Table 15-2, this relates to an FER_AMR_HR Quality number of 2.
Pegging
This statistic pegs the uplink frame erasure rate for AMR half rate calls for each carrier in a cell.
Units
The FER_AMR_HR is reported using values 0 to 9 as follows.
FER_AMR_HR Quality
FER ratio (min:1 to max:1)
number
0 0.0000 to 0.0416
1 0.0417 to 0.0832
2 0.0833 to 0.1249
3 0.1250 to 0.1666
4 0.1667 to 0.2082
5 0.2083 to 0.2499
6 0.2500 to 0.2916
7 0.2917 to 0.3332
8 0.3333 to 0.3749
9 0.3750 to 1.0000
FER_AMR_HR Quality is measured on a timeslot basis for active channels after decoding
de-interleaving and error correction. Data for this statistic is reported by firmware to the
RSS/HO software process where it is pegged.
The values of the bins are fixed and are not adjustable by the operator.
15-22 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application FER_AMR_HR
Analysis
This statistic can be used for trend analysis for target optimization effects on cell/radios with regards to quality.
Reference None.
Usage Quality of service, Fault finding, RF loss, Congestion.
Basis Carrier.
Type Normal distribution.
68P02901W56-Q 15-23
24 May 2004 CONTROLLED INTRODUCTION
FER_GSM_HR Chapter 15: HR and AMR statistics
FER_GSM_HR
{22064}
Description
The uplink FER_GSM_HR Quality statistic is derived from a ratio of successfully decoded
good speech frames against unsuccessfully decoded bad frames for GSM half rate calls. The
measurement period over which the calculation is made is 480 ms.
During this period, 24 speech frames are decoded and a ratio calculated. By referring to a lookup
table, the ratio is then converted to a FER_GSM_HR Quality number between 0 and 9.
For example: two bad frames out of 24 results in a ratio of 0.083:1. From the lookup table,
Table 15-3, this relates to an FER_GSM_HR Quality number of 2.
Pegging
This statistic pegs the uplink frame erasure rate for GSM half rate calls for each carrier in a cell.
Units
FER_GSM_HR Quality
FER ratio (min:1 to max:1)
number
0 0.0000 to 0.0416
1 0.0417 to 0.0832
2 0.0833 to 0.1249
3 0.1250 to 0.1666
4 0.1667 to 0.2082
5 0.2083 to 0.2499
6 0.2500 to 0.2916
7 0.2917 to 0.3332
8 0.3333 to 0.3749
9 0.3750 to 1.0000
15-24 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application FER_GSM_HR
FER_GSM_HR Quality is measured on a timeslot basis for active channels after decoding
de-interleaving and error correction. Data for this statistic is reported by firmware to the
RSS/HO software process where it is pegged.
The values of the bins are fixed and are not adjustable by the operator.
68P02901W56-Q 15-25
24 May 2004 CONTROLLED INTRODUCTION
HO_REQ_FROM_MSC Chapter 15: HR and AMR statistics
HO_REQ_FROM_MSC
Description
Bin Procedures
0 PM_FR
1 PM_EFR
2 PM_AMR_FR
3 PM_AMR_HR
4 PM_SDCCH_CHAN
5 PM_Other
{22064} When the Half Rate feature is unrestricted, the HO_REQ_FROM_MSC bin table
introduces bin procedure PM_GSM_HR as shown:
Bin Procedure
6 PM_GSM_HR
Pegging
This statistic pegs the handover request for each channel type and speech version
speech version in the appropriate bin.
15-26 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application RF_LOSSES_TCH_HR
RF_LOSSES_TCH_HR
{22064}
Description
The statistic tracks the number of calls lost while using a half rate AMR and/or GSM TCH.
Pegging
This statistic pegs the number of calls that were terminated because of RF problems. It is composed
of calls lost while using a half rate AMR and/or GSM TCH.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of lost calls while
using a half rate AMR and/or GSM TCH that are acceptable in normal system operations.
Reference None
Usage RF loss.
Congestion.
Quality of service monitoring.
Fault finding.
Installation and commissioning.
Basis Timeslot.
Type Counter.
68P02901W56-Q 15-27
24 May 2004 CONTROLLED INTRODUCTION
TCH_CONG_INNER_ZONE_HR Chapter 15: HR and AMR statistics
TCH_CONG_INNER_ZONE_HR
{22064}
Description
The statistic tracks the duration of time when there are no half rate AMR and/or GSM TCHs
available in the inner zone of a concentric cell or dual band cell.
Pegging
When the last inner zone half rate AMR and/or GSM TCH available is allocated a timer is started.
This timer is stopped when at least one inner zone half rate TCH becomes idle.
Reference None.
Usage Radio resource allocation.
Quality of service monitoring.
Network planning.
Service retainability.
Basis Cell.
Type Duration.
15-28 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application TCH_CONGESTION_HR
TCH_CONGESTION_HR
{22064}
Description
The statistic tracks the duration of time when there are no half rate AMR and/or GSM
TCHs available. For concentric cell or dual band cells, this measurement indicates half rate
AMR and/or GSM TCH congestion for the outer zone.
Pegging
When the last half rate AMR and/or GSM TCH available is allocated a timer is started. This
timer is stopped when at least one half rate TCH becomes idle.
Reference None.
Usage Radio resource allocation.
Quality of service monitoring.
Network planning.
Service retainability.
Basis Cell.
Type Duration.
68P02901W56-Q 15-29
24 May 2004 CONTROLLED INTRODUCTION
TCH_CONGESTION_HR Chapter 15: HR and AMR statistics
15-30 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
16
Call model statistics
Call model parameter values can be derived from the GSM network statistics collected at the OMC-R.
All the statistics used for determining the call model parameters must be collected during busy
hours and averaged over a reasonable period of time (3 months or more).
The call model parameters should be averaged over the entire network or at the BSC level for equipment
dimensioning purposes. This gives more scope of averaging out the load from the network entities.
The following are call model statistics:
• "CALL_DURATION (T)" on page 16-2.
Refer to the System Information: BSS Equipment Planning (68P02900W21) for further
information on the call model parameters.
68P02901W56-Q 16-1
24 May 2004 CONTROLLED INTRODUCTION
CALL_DURATION (T) Chapter 16: Call model statistics
CALL_DURATION (T)
Description
Formula
_ _ _ _ _ _ _ _ _
_ _
Where: is:
N the number of cells.
stat_interval_in_sec the interval over which
BUSY_TCH_MEAN values
are measured. It is 3600 if hourly
values are used and 86400 if daily
values are used.
16-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CALL_SETUP_TCH_BLOCKING_RATE
CALL_SETUP_TCH_BLOCKING_RATE
Description
This statistic provides the percentage of attempts to allocate a TCH call setup that were blocked.
Formula
_ _ _ _ _ _
_ _ _ _
68P02901W56-Q 16-3
24 May 2004 CONTROLLED INTRODUCTION
HANDOVERS_PER_CALL (H) Chapter 16: Call model statistics
HANDOVERS_PER_CALL (H)
Description
This statistic provides the number of Handovers per call where the handovers may
be inter-BSS, intra-BSS or intra-cell.
Formula
_ _ _ _ _ _ _ _ _
_ _ _
_ _
Where: is:
N the number of cells.
The TOTAL_CALLS parameter is the count of the total circuit-switched calls in a cell. It
should be summed for all the cells in the BSC, when used in the previous formula.
Usage Network planning.
Optimization.
Basis Cell.
Raw Statistics OUT_INTER_BSS_REQ_TO_MSC.
OUT_INTRA_BSS_HO_ATMPT.
INTRA_CELL_HO_ATMPT.
TOTAL_CALLS.
ASSIGNMENT_REDIRECTION.
16-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application IMSI_DETACHES_TO_CALL (Id)
IMSI_DETACHES_TO_CALL (I ) d
Description
Formula
_ _ _
_ _
Where: is:
N the number of cells.
68P02901W56-Q 16-5
24 May 2004 CONTROLLED INTRODUCTION
INTRA_BSS_HO_TO_ALL_HO (i) Chapter 16: Call model statistics
INTRA_BSS_HO_TO_ALL_HO (i)
Description
Formula
_ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _
_ _ _
Where: is:
N the number of cells.
16-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application LOCATION_UPDATE_FACTOR (L)
LOCATION_UPDATE_FACTOR (L)
Description
This statistic is calculated using the ratio of location updates per call (l) and the ratio of
IMSI detaches per call (Id). For networks with IMSI detach disabled, the location update
factor equals the ratio of location updates per call (l).
IMSI detach types determine the way the MSC clears the connection with the BSS after receiving the
IMSI detach. When using IMSI detach type 1, the MSC clears the SCCP connection, a clearing procedure
that involves only one uplink (average size of 42 bytes) and one downlink message (average size of 30
bytes). When using IMSI detach type 2, the MSC sends the CLEAR COMMAND and the BSS sends
CLEAR COMPLETE, etc., which involves three uplink (average size of 26 bytes) and three downlink
messages (average size of 30 bytes). A location update procedure itself takes five downlink messages
(average size of 30 bytes) and six uplink messages (average size of 26 bytes).
Hence, an IMSI detach (type1) takes a total of 2/11 (approximately 0.2) of the number of messages as a
location update and a IMSI detach (type 2) takes 6/11 (approximately 0.5) of the messages of a location update.
Formula
If IMSI detach is enabled, then depending on whether short message sequence (type 1) or
long message sequence (type 2) is used, L is calculated as:
• L = LOCATION_UPDATES_TO_CALLS (IMSI detach disabled i.e. Id=0 )
68P02901W56-Q 16-7
24 May 2004 CONTROLLED INTRODUCTION
LOCATION_UPDATES_TO_CALLS (I) Chapter 16: Call model statistics
LOCATION_UPDATES_TO_CALLS (I)
Description
Formula
_ _
_ _
Where: is:
N the number of cells.
16-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application PAGES_PER_CALL (PPC)
PAGES_PER_CALL (P ) PC
Description
Formula
_ _ _
_ _
Where: is:
N the number of cells under the BSC.
68P02901W56-Q 16-9
24 May 2004 CONTROLLED INTRODUCTION
PAGES_PER_SECOND Chapter 16: Call model statistics
PAGES_PER_SECOND
Description
Formula
_ _ _
_ _
_
16-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application PAGING_RATE (P)
PAGING_RATE (P)
Description
The paging rate is the summation of the paging messages sent to each location area
averaged over the interval period.
Formula
_ _ _
_ _ _
Where: is:
N the number of location areas.
PAGE_REQ_FROM_MSC should be the maximum per cell value for each location area.
Usage Network planning.
Optimization.
Basis Cell.
Raw Statistics PAGE_REQ_FROM_MSC.
68P02901W56-Q 16-11
24 May 2004 CONTROLLED INTRODUCTION
SMS_TO_CALL_RATIO (S) Chapter 16: Call model statistics
SMS_TO_CALL_RATIO (S)
Description
Formula
_ _ _ _ _ _
_ _ _ _ _ _ _ _ _
_ _ _ _
16-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
17
Key statistics
Key statistics are a set of calculated values providing an operator with a summary of system performance
during a specific statistics collection interval. They are designed to give an overall indication of the condition
of the system and allow comparison of similar time periods to detect performance changes and trends.
Key statistics are also provided to facilitate the monitoring of the most important network parameters. Key
statistics are calculated at the OMC-R using various BSS raw statistics. Different statistics are combined at the
OMC-R using a predefined formula to produce a new statistic. For example, various handover failure statistics
may be combined and averaged over the total number of calls to produce a handover failure rate key statistic.
Key statistics may be displayed in the Performance Management window of the OMC-R.
They key statistics are categorized into subgroups, each of which are described in
"Key statistics subgroups" on page 17-2.
68P02901W56-Q 17-1
24 May 2004 CONTROLLED INTRODUCTION
Key statistics subgroups Chapter 17: Key statistics
Call summary
Call summary statistics are used to determine assignment and handover performance of one
or more cells. The following are call summary statistics:
• "CALL_SETUP_SUCCESS_RATE" on page 17-6.
Channel usage
Channel usage statistics are used to determine SDCCH and TCH performance levels.
The following are channel usage statistics:
• "MEAN_TCH_BUSY_TIME" on page 17-14.
17-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Key statistics subgroups
Connection establishment
Connection statistics are used to determine the number and interval of attempted and successful
assignment requests. The following are connection establishment statistics:
• "ATTEMPT_IMMED_ASSIGN_PROC" on page 17-5.
RF loss summary
RF loss summary statistics are used to determine TCH assignments within a cell and the rate
of RF lost calls. The following are RF loss summary statistics:
• "CELL_TCH_ALLOCATIONS" on page 17-7.
68P02901W56-Q 17-3
24 May 2004 CONTROLLED INTRODUCTION
Key statistics subgroups Chapter 17: Key statistics
MTL utilisation
MTL utilisation statistics are used to provide a measure of MTL utilisation from the MSC to BSS
and from the BSS to MSC. The following are MTL utilisation statistics:
• "MTL_UTILISATION_RX" on page 17-15.
The template headings are used as required and are not present for all statistics.
17-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application ATTEMPT_IMMED_ASSIGN_PROC
ATTEMPT_IMMED_ASSIGN_PROC
Description
Formula
_ _ _
_ _ _
_ _ _ _
68P02901W56-Q 17-5
24 May 2004 CONTROLLED INTRODUCTION
CALL_SETUP_SUCCESS_RATE Chapter 17: Key statistics
CALL_SETUP_SUCCESS_RATE
Description
The CALL_SETUP_SUCCESS_RATE statistic tracks the percentage of call attempts that result
in a successful TCH access. Network accesses which do not require a TCH are excluded; for
example, location updates, SMS, and Supplementary Service attempts.
Formula
_
_ _
_ _
_ _ _ _
_ _ _ _ _ _
_ _ _
_ _ _
__ _ _
_ __ _ _
_ _ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _
_ _ _ _ _ _
17-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CELL_TCH_ALLOCATIONS
CELL_TCH_ALLOCATIONS
Description
Formula
_ _ _
68P02901W56-Q 17-7
24 May 2004 CONTROLLED INTRODUCTION
CELL_TCH_ASSIGNMENTS Chapter 17: Key statistics
CELL_TCH_ASSIGNMENTS
Description
The CELL_TCH_ASSIGNMENTS statistic is the sum of the total number of calls, the total number of
successful incoming inter-BSS call handovers, and the total number of incoming intra-BSS call handovers.
Formula
_
_ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _
17-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application HANDOVER_FAILURE_RATE
HANDOVER_FAILURE_RATE
Description
The HANDOVER_FAILURE_RATE statistic tracks the percentage of handovers that were attempted
from the source cell (the cell for which the statistic is presented) that failed to successfully reach the
target cell and failed to successfully recover to the source cell, that is, the handover failed and the call
dropped. A handover attempt is counted when a handover command is sent to the MS.
Congestion on the target cell does not result in the BSS sending a handover command to the mobile
therefore this measurement is not impacted by target cell congestion.
Formula
_ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _ _
_
_ _ _ _ _ _ _
_ _ _ _ _
_ _ _ _ _ _ _
68P02901W56-Q 17-9
24 May 2004 CONTROLLED INTRODUCTION
HANDOVER_SUCCESS_RATE Chapter 17: Key statistics
HANDOVER_SUCCESS_RATE
Description
Formula
_ _ _ _ _ _ _
_ _ _ _ _
_ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
17-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application HANDOVER_SUCCESS_RATE
68P02901W56-Q 17-11
24 May 2004 CONTROLLED INTRODUCTION
MEAN_ARRIVAL_TIME_BETWEEN_CALLS Chapter 17: Key statistics
MEAN_ARRIVAL_TIME_BETWEEN_CALLS
Description
Formula
_ _ _
_ _ _ _ _
_ _ _ _
17-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MEAN_INTER_ARRIVAL_TIME
MEAN_INTER_ARRIVAL_TIME
Description
The MEAN_INTER_ARRIVAL_TIME statistic is the arithmetic mean of the sum of the time intervals
between consecutive normal, SMS, supplementary and emergency requests for service.
Formula
BSS Level
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
68P02901W56-Q 17-13
24 May 2004 CONTROLLED INTRODUCTION
MEAN_TCH_BUSY_TIME Chapter 17: Key statistics
MEAN_TCH_BUSY_TIME
Description
Formula
_ _
_ _ _
_ _
Usage Optimization.
Network planning.
Basis Cell.
Type Duration (in seconds).
Raw Statistics AVAILABLE_TCH.
BUSY_TCH.
17-14 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTL_UTILISATION_RX
MTL_UTILISATION_RX
Description
The MTL_UTILISATION_RX statistic provides a measure of MTL utilisation for the MSC to BSS direction.
Formula
_ _ _ _ _ _
_ _
_ _
NOTE: As an explanation as to how the formula was derived, refer to the following
which shows no number simplification:
_ _ _ _ _
_
_ _
_ _
Usage Optimization.
Network planning.
Basis MTL.
Type Percentage.
Raw Statistics MTP_MSU_RX.
MTP_SIF_SIO_RX.
SIB_RX.
MTP_LINK_INS.
68P02901W56-Q 17-15
24 May 2004 CONTROLLED INTRODUCTION
MTL_UTILISATION_TX Chapter 17: Key statistics
MTL_UTILISATION_TX
Description
The MTL_UTILISATION_TX statistic provides a measure of MTL utilisation for the BSS to MSC direction.
Formula
_ _ _ _ _ _
_ _
_ _
NOTE: As an explanation as to how the formula was derived, refer to the following
which shows no number simplification:
_ _ _ _ _
_
_ _
_ _
Usage Optimization.
Network planning.
Basis MTL.
Type Percentage.
Raw Statistics MTP_MSU_TX.
MTP_SIF_SIO_TX.
SIB_TX.
MTP_LINK_INS.
17-16 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application RF_LOSS_RATE
RF_LOSS_RATE
Description
The RF_LOSS_RATE statistic compares the total number of RF losses (while using both
SDCCH and TCH) with the number of calls set-up in the cell plus the number of calls handed
in to the cell. It indicates the cell/system ability to preserve calls.
Formula
_ _
_ _ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _
_ _ _
_ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _
Handovers may relate to SDCCHs (as opposed to TCHs). In this case, the accuracy of the statistic is
affected. For the most part this effect is expected to be negligible. nTCH = Number of TCHs in cell.
Usage Quality of service.
Fault finding and optimization.
Installation and commissioning.
Basis Cell.
Type Percentage.
Raw Statistics IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].
IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].
OK_ACC_PROC: (The value used in this formula is the sum of
bins 0 to 7 of this counter array statistic.) RF_LOSSES_TCH.
RF_LOSSES_SD.
68P02901W56-Q 17-17
24 May 2004 CONTROLLED INTRODUCTION
SDCCH_ACCESS_SUCCESS_RATE Chapter 17: Key statistics
SDCCH_ACCESS_SUCCESS_RATE
Description
Formula
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _
_ _ _
17-18 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SDCCH_BLOCKING_RATE
SDCCH_BLOCKING_RATE
Description
The SDCCH_BLOCKING_RATE statistic tracks the percentage of attempts to allocate an SDCCH that were
blocked due to no available SDCCH resources. This statistic includes incoming SDCCH handover attempts.
Formula
_ _
_ _
_ _ _
68P02901W56-Q 17-19
24 May 2004 CONTROLLED INTRODUCTION
SDCCH_SETUP_BLOCKING_RATE Chapter 17: Key statistics
SDCCH_SETUP_BLOCKING_RATE
Description
Formula
_ _ _
_ _ _
_ _ _ _
_ _ _ _
17-20 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SDCCH_MEAN_ARRIVAL_RATE
SDCCH_MEAN_ARRIVAL_RATE
Description
The SDCCH_MEAN_ARRIVAL_RATE statistic tracks the call arrival (set-up) rate for
the SDCCHs in the cell measured in calls per interval.
Formula
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _
68P02901W56-Q 17-21
24 May 2004 CONTROLLED INTRODUCTION
SDCCH_MEAN_HOLDING_TIME Chapter 17: Key statistics
SDCCH_MEAN_HOLDING_TIME
Description
Formula
_ _ _
_ _ _
_
17-22 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SDCCH_RF_LOSS_RATE
SDCCH_RF_LOSS_RATE
Description
The SDCCH_RF_LOSS_RATE statistic compares the total number of RF losses (while using an
SDCCH), as a percentage of the total number of call attempts for SDCCH channels. T his statistic
is intended to give an indication of how good the cell/system is at preserving calls.
Formula
_ _
_ _ _
_ _ _ _
68P02901W56-Q 17-23
24 May 2004 CONTROLLED INTRODUCTION
SDCCH_TRAFFIC_CARRIED Chapter 17: Key statistics
SDCCH_TRAFFIC_CARRIED
Description
Formula
_ _ _ _
_ _
_ _
_ _ _ _
_ _
_ _
17-24 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SDCCH_TRAFFIC_CARRIED
68P02901W56-Q 17-25
24 May 2004 CONTROLLED INTRODUCTION
SUCCESS_IMMED_ASSIGN_PROC Chapter 17: Key statistics
SUCCESS_IMMED_ASSIGN_PROC
Description
Formula
_ _ _ _ _ _ _
_ _ _
_ _ _
17-26 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SUCCESS_INTERNAL_HO
SUCCESS_INTERNAL_HO
Description
Formula
_ _ _ _ _
_ _
_ _ _ _ _ _ _
68P02901W56-Q 17-27
24 May 2004 CONTROLLED INTRODUCTION
TCH_BLOCKING_RATE Chapter 17: Key statistics
TCH_BLOCKING_RATE
Description
The TCH_BLOCKING_RATE statistic provides the percentage of all requests for TCH resources
(originations and hand ins) which fail due to no available TCH resources.
Formula
_ _
_ _
_
_ _
_
_ _
_ _
_
17-28 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application TCH_BLOCKING_RATE_INNER_Z
TCH_BLOCKING_RATE_INNER_Z
Description
The TCH_BLOCKING_RATE_INNER_Z statistic provides the percentage of all requests for inner
zone TCH resources (originations and hand ins) which fail due to no available TCH resources.
Formula
_ _ _ _
_ _
_ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _
_ _ _ _
_ _
_ _ _ _
_ _ _ _ _
68P02901W56-Q 17-29
24 May 2004 CONTROLLED INTRODUCTION
TCH_BLOCKING_RATE_OUTER_Z Chapter 17: Key statistics
TCH_BLOCKING_RATE_OUTER_Z
Description
The TCH_BLOCKING_RATE_OUTER_Z statistic provides the percentage of all requests for outer
zone TCH resources (originations and hand ins) which fail due to no available TCH resources.
Formula
_ _
_ _ _ _
_ _
_ _
_ _
_ _ _ _
_ _ _
_ _ _ _ _ _ _
_ _ _
_ _ _
_ _
_ _ _ _
_ _
_ _
_ _
_ _ _ _
_ _ _
_ _ _ _ _
17-30 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application TCH_MEAN_ARRIVAL_RATE
TCH_MEAN_ARRIVAL_RATE
Description
Formula
_ _ _ _ _
_ _ _
The arrival rate of calls includes both calls set up on traffic channels within
a cell and handovers into the cell.
Usage Network planning.
Basis Cell.
Type Counter (calls/interval).
Raw Statistics ALLOC_TCH.
ALLOC_TCH_FAIL.
TCH_Q_REMOVED.
68P02901W56-Q 17-31
24 May 2004 CONTROLLED INTRODUCTION
TCH_MEAN_HOLDING_TIME Chapter 17: Key statistics
TCH_MEAN_HOLDING_TIME
Description
Formula
Cell Level
{22064}
_ _
_ _ _
_ _ _
_ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _
BSS Level
{22064}
_ _
_ _ _
_ _ _
_ _
_ _
_ _
_ _
_ _ _
_ _ _ _
Network Level
17-32 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application TCH_MEAN_HOLDING_TIME
{22064}
_ _
_ _ _
_ _ _
_ _
_ _
_ _
_ _
The numerator and denominator may peg on different intervals (where a call extends across
multiple collection boundaries). This affects the accuracy of the statistic for the period. Therefore,
this statistic should be used as a trend rather than focusing on specific values.
Analysis
68P02901W56-Q 17-33
24 May 2004 CONTROLLED INTRODUCTION
TCH_RF_LOSS_RATE Chapter 17: Key statistics
TCH_RF_LOSS_RATE
Description
The TCH_RF_LOSS_RATE statistic tracks the percentage of TCH resources that are
abnormally released due to a failure on the radio interface.
Formula
Cell Level
{22064}
_ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _ _
BSS Level
{22064}
_ _ _ _ _
_ _ _
_
_ _
_ _
_ _
_ _ _ _ _ _
Network Level
{22064}
_ _ _ _ _
_ _ _
_
_ _
_ _
_ _
Analysis
17-34 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application TCH_RF_LOSS_RATE
Type Percentage.
Raw Statistics ASSIGNMENT_REDIRECTION (The value used in this formula
is the sum of bins 0 to 2 of this counter array statistic).
IN_INTER_BSS[IN_INTER_HO_SUC].
IN_INTRA_BSS[IN_INTRA_BSS_HO_SUC].
RF_LOSSES_TCH.
{22064}RF_LOSSES_TCH_HR.
TOTAL_CALLS.
68P02901W56-Q 17-35
24 May 2004 CONTROLLED INTRODUCTION
TCH_TRAFFIC_CARRIED Chapter 17: Key statistics
TCH_TRAFFIC_CARRIED
Description
The TCH_TRAFFIC_CARRIED statistic tracks the mean number of busy TCHs measured in Erlangs.
Formula
_ _ _ _ _
_ _
_ _ _ _ _ _ _
_ _ _ _ _
_ _
17-36 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application TCH_TRAFFIC_CARRIED
Analysis
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Units = Erlangs.
Raw Statistics BUSY_TCH (BUSY_TCH_MEAN).
{22064}BUSY_TCH_HR (BUSY_TCH_HR_MEAN).
68P02901W56-Q 17-37
24 May 2004 CONTROLLED INTRODUCTION
TOTAL_CALLS_KEY Chapter 17: Key statistics
TOTAL_CALLS_KEY
Description
The TOTAL_CALLS_KEY statistic tracks the number of calls for one or more cells during the interval.
Formula
_ _ _
17-38 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application UNSUCCESS_INTERNAL_HO_NOREEST
UNSUCCESS_INTERNAL_HO_NOREEST
Description
Formula
_ _ _ _ _ _ _
_ _ _ _ _ _ _ _
68P02901W56-Q 17-39
24 May 2004 CONTROLLED INTRODUCTION
UNSUCCESS_INTERNAL_HO_REEST Chapter 17: Key statistics
UNSUCCESS_INTERNAL_HO_REEST
Description
Formula
_ _ _ _ _
_ _ _
_ _ _ _ _ _ _
17-40 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
18
Network health reports
Network health statistics quantify BSS performance from a subscriber perspective. A combination of raw
and other network health statistics are used by the OMC-R to calculate these statistics.
Network health statistics are available for display with the Cell device statistics in the
OMC-R Performance Management window.
They network health statistics are categorized into subgroups, each of which are described
in "Network health statistics subgroups" on page 18-2.
68P02901W56-Q 18-1
24 May 2004 CONTROLLED INTRODUCTION
Network health statistics subgroups Chapter 18: Network health reports
Network health statistics are organized into the following major subgroups:
• "GPRS performance" on page 18-2.
GPRS performance
The following statistics provide key performance metrics for the GPRS system:
• "AIR_INTERFACE_BW_CS1" on page 18-8.
18-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Network health statistics subgroups
Handover performance
68P02901W56-Q 18-3
24 May 2004 CONTROLLED INTRODUCTION
Network health statistics subgroups Chapter 18: Network health reports
18-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Network health statistics subgroups
Health check
Paging performance
Radio performance
68P02901W56-Q 18-5
24 May 2004 CONTROLLED INTRODUCTION
Network health statistics subgroups Chapter 18: Network health reports
SDCCH congestion
TCH congestion
18-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Network health statistics subgroups
68P02901W56-Q 18-7
24 May 2004 CONTROLLED INTRODUCTION
AIR_INTERFACE_BW_CS1 Chapter 18: Network health reports
AIR_INTERFACE_BW_CS1
Description
Formula
_ _ _ _
18-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application AIR_INTERFACE_BW_CS2
AIR_INTERFACE_BW_CS2
Description
Formula
_ _ _ _
68P02901W56-Q 18-9
24 May 2004 CONTROLLED INTRODUCTION
AIR_INTERFACE_BW_CS3 Chapter 18: Network health reports
AIR_INTERFACE_BW_CS3
Description
Formula
_ _ _ _
18-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application AIR_INTERFACE_BW_CS4
AIR_INTERFACE_BW_CS4
Description
Formula
_ _ _ _
68P02901W56-Q 18-11
24 May 2004 CONTROLLED INTRODUCTION
AIR_INTERFACE_PAGING Chapter 18: Network health reports
AIR_INTERFACE_PAGING
Description
Formula
_ _ _ _ _ _
_ _
_ _ _ _ _
_ _ _ _ _
18-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application ASSIGNMENT_SUCCESS_RATE
ASSIGNMENT_SUCCESS_RATE
Description
The ASSIGNMENT_SUCCESS_RATE statistic measures the success rate of the A-interface assignment
procedure which will also automatically include the impact of the air interface assignment procedure.
Formula
_ _ _
_ _
_ _ _
68P02901W56-Q 18-13
24 May 2004 CONTROLLED INTRODUCTION
CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS Chapter 18: Network health reports
CALL_SETUP_RF_ASSIGNMENT_
FAIL_RATE_LOST_MS
Description
Formula
_ _ _
_ _ _
_ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _ _
_ _ _ _ _ _
_ _ _
_ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
18-14 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS
68P02901W56-Q 18-15
24 May 2004 CONTROLLED INTRODUCTION
CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_RECOVERED_MS Chapter 18: Network health reports
CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_
RECOVERED_MS
Description
Formula
_ _ _
_ _ _
_ _ _ _ _
_ _ _
_ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
18-16 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE
CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE
Description
Formula
_ _ _
_ _ _ _ _ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
68P02901W56-Q 18-17
24 May 2004 CONTROLLED INTRODUCTION
CALL_SETUP_SUCCESS_RATE Chapter 18: Network health reports
CALL_SETUP_SUCCESS_RATE
Description
The CALL_SETUP_SUCCESS_RATE statistic tracks the percentage of call attempts that result
in a successful TCH access. Network accesses which do not require a TCH are excluded; for
example, location updates, SMS, and Supplementary Service attempts.
Formula
_
_ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _ _
_ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _ _
18-18 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CALL_SUCCESS_RATE
CALL_SUCCESS_RATE
Description
This statistic represents the portion of MS call transactions with normal completions at the radio subsystem,
providing an overall indication of network performance from a subscriber perspective.
A combination of the CALL_SETUP_SUCCESS_RATE and DROP_CALL_RATE network
health statistics is used to calculate this statistic. The raw statistics used to calculate these
health statistics are included in the raw statistics listing.
Formula
_ _
_ _ _ _ _
68P02901W56-Q 18-19
24 May 2004 CONTROLLED INTRODUCTION
CALL_VOLUME Chapter 18: Network health reports
CALL_VOLUME
Description
The CALL_VOLUME statistic tracks the number of call setups which result in a successful TCH access.
Formula
_
_ _
_
_ _
_ _
18-20 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CELL_UPDATE
CELL_UPDATE
Description
The CELL_UPDATE statistic measures the number of cell reselections relating to a particular cell.
Formula
_ _ _
68P02901W56-Q 18-21
24 May 2004 CONTROLLED INTRODUCTION
CS1_USAGE_DL Chapter 18: Network health reports
CS1_USAGE_DL
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
The CS1_USAGE_DL statistic provides the percentage of Radio Link Control blocks transmitted
by the PCU (downlink) using GPRS coding scheme 1.
Formula
_ _ _ _ _ _ _ _
_ _ _ _
_ _
_ _ _
QoS identifies how delay sensitive the traffic is. Currently only QoS3 is implemented which
is the most delay insensitive traffic class - it is defined as Best Effort.
Usage Network planning.
Radio resource allocation.
Basis Cell.
Type Percentage.
Raw Statistics AIR_DL_DATA_BLKS[QOS1_CS1].
AIR_DL_DATA_BLKS[QOS2_CS1].
AIR_DL_DATA_BLKS[QOS3_CS1].
AIR_DL_DATA_BLKS all bins.
18-22 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CS1_USAGE_UL
CS1_USAGE_UL
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
The CS1_USAGE_UL statistic provides the percentage of Radio Link Control blocks received
by the PCU (uplink) using GPRS coding scheme 1.
Formula
_ _ _ _ _ _ _ _
_ _ _ _
_ _
_ _ _
QoS identifies how delay sensitive the traffic is. Currently only QoS3 is implemented which
is the most delay insensitive traffic class - it is defined as Best Effort.
Usage Network planning.
Radio resource allocation.
Basis Cell.
Type Percentage.
Raw Statistics AIR_UL_DATA_BLKS[QOS1_CS1].
AIR_UL_DATA_BLKS[QOS2_CS1].
AIR_UL_DATA_BLKS[QOS3_CS1].
AIR_UL_DATA_BLKS all bins.
68P02901W56-Q 18-23
24 May 2004 CONTROLLED INTRODUCTION
CS2_USAGE_DL Chapter 18: Network health reports
CS2_USAGE_DL
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
The CS2_USAGE_DL statistic provides the percentage of Radio Link Control blocks transmitted
by the PCU (downlink) using GPRS coding scheme 2.
Formula
_ _ _ _ _ _ _ _
_ _ _ _
_ _
_ _ _
QoS identifies how delay sensitive the traffic is. Currently only QoS3 is implemented which
is the most delay insensitive traffic class - it is defined as Best Effort.
Usage Network planning.
Radio resource allocation.
Basis Cell.
Type Percentage.
Raw Statistics AIR_DL_DATA_BLKS[QOS1_CS2].
AIR_DL_DATA_BLKS[QOS2_CS2].
AIR_DL_DATA_BLKS[QOS3_CS2].
AIR_DL_DATA_BLKS all bins.
18-24 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CS2_USAGE_UL
CS2_USAGE_UL
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
The CS2_USAGE_UL statistic provides the percentage of Radio Link Control blocks received
by the PCU (uplink) using GPRS coding scheme 2.
Formula
_ _ _ _ _ _ _ _
_ _ _ _
_ _
_ _ _
QoS identifies how delay sensitive the traffic is. Currently only QoS3 is implemented which
is the most delay insensitive traffic class - it is defined as Best Effort.
Usage Network planning.
Radio resource allocation.
Basis Cell.
Type Percentage.
Raw Statistics AIR_UL_DATA_BLKS[QOS1_CS2].
AIR_UL_DATA_BLKS[QOS2_CS2].
AIR_UL_DATA_BLKS[QOS3_CS2].
AIR_UL_DATA_BLKS all bins.
68P02901W56-Q 18-25
24 May 2004 CONTROLLED INTRODUCTION
CS3_USAGE_DL Chapter 18: Network health reports
CS3_USAGE_DL
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
The CS3_USAGE_DL statistic provides the percentage of Radio Link Control blocks transmitted
by the PCU (downlink) using GPRS coding scheme 3.
Formula
_ _ _ _ _ _ _ _
_ _ _ _
_ _
_ _ _
QoS identifies how delay sensitive the traffic is. Currently only QoS3 is implemented which
is the most delay insensitive traffic class - it is defined as Best Effort.
Usage Network planning.
Radio resource allocation.
Basis Cell.
Type Percentage.
Raw Statistics AIR_DL_DATA_BLKS[QOS1_CS3].
AIR_DL_DATA_BLKS[QOS2_CS3].
AIR_DL_DATA_BLKS[QOS3_CS3].
AIR_DL_DATA_BLKS all bins.
18-26 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CS3_USAGE_UL
CS3_USAGE_UL
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
The CS3_USAGE_UL statistic provides the percentage of Radio Link Control blocks received
by the PCU (uplink) using GPRS coding scheme 3.
Formula
_ _ _ _ _ _ _ _
_ _ _ _
_ _
_ _ _
QoS identifies how delay sensitive the traffic is. Currently only QoS3 is implemented which
is the most delay insensitive traffic class - it is defined as Best Effort.
Usage Network planning.
Radio resource allocation.
Basis Cell.
Type Percentage.
Raw Statistics AIR_UL_DATA_BLKS[QOS1_CS3].
AIR_UL_DATA_BLKS[QOS2_CS3].
AIR_UL_DATA_BLKS[QOS3_CS3].
AIR_UL_DATA_BLKS all bins.
68P02901W56-Q 18-27
24 May 2004 CONTROLLED INTRODUCTION
CS4_USAGE_DL Chapter 18: Network health reports
CS4_USAGE_DL
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
The CS4_USAGE_DL statistic provides the percentage of Radio Link Control blocks transmitted
by the PCU (downlink) using GPRS coding scheme 4.
Formula
_ _ _ _ _ _ _ _
_ _ _ _
_ _
_ _ _
QoS identifies how delay sensitive the traffic is. Currently only QoS3 is implemented which
is the most delay insensitive traffic class - it is defined as Best Effort.
Usage Network planning.
Radio resource allocation.
Basis Cell.
Type Percentage.
Raw Statistics AIR_DL_DATA_BLKS[QOS1_CS4].
AIR_DL_DATA_BLKS[QOS2_CS4].
AIR_DL_DATA_BLKS[QOS3_CS4].
AIR_DL_DATA_BLKS all bins.
18-28 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application CS4_USAGE_UL
CS4_USAGE_UL
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
The CS4_USAGE_UL statistic provides the percentage of Radio Link Control blocks received
by the PCU (uplink) using GPRS coding scheme 4.
Formula
_ _ _ _ _ _ _ _
_ _ _ _
_ _
_ _ _
QoS identifies how delay sensitive the traffic is. Currently only QoS3 is implemented which
is the most delay insensitive traffic class - it is defined as Best Effort.
Usage Network planning.
Radio resource allocation.
Basis Cell.
Type Percentage.
Raw Statistics AIR_UL_DATA_BLKS[QOS1_CS4].
AIR_UL_DATA_BLKS[QOS2_CS4].
AIR_UL_DATA_BLKS[QOS3_CS4].
AIR_UL_DATA_BLKS all bins.
68P02901W56-Q 18-29
24 May 2004 CONTROLLED INTRODUCTION
DL_AIR_INTERFACE_BW_CS1 Chapter 18: Network health reports
DL_AIR_INTERFACE_BW_CS1
Description
The DL_AIR_INTERFACE_BW_CS1 statistic provides a reference value in kilobits per second for the
configured downlink bandwidth in a cell in terms of coding scheme 1 for a statistics collection period.
Formula
For GSR6 (Horizon II) the formula is:
_
_ _ _ _
18-30 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DL_AIR_INTERFACE_BW_CS2
DL_AIR_INTERFACE_BW_CS2
Description
The DL_AIR_INTERFACE_BW_CS2 statistic provides a reference value in kilobits per second for the
configured downlink bandwidth in a cell in terms of coding scheme 2 for a statistics collection period.
Formula
For GSR6 (Horizon II) the formula is:
_
_ _ _ _
68P02901W56-Q 18-31
24 May 2004 CONTROLLED INTRODUCTION
DL_AIR_INTERFACE_BW_CS3 Chapter 18: Network health reports
DL_AIR_INTERFACE_BW_CS3
Description
The DL_AIR_INTERFACE_BW_CS3 statistic provides a reference value in kilobits per second for the
configured downlink bandwidth in a cell in terms of coding scheme 3 for a statistics collection period.
Formula
For GSR6 (Horizon II) the formula is:
_
_ _ _ _
18-32 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DL_AIR_INTERFACE_BW_CS4
DL_AIR_INTERFACE_BW_CS4
Description
The DL_AIR_INTERFACE_BW_CS4 statistic provides a reference value in kilobits per second for the
configured downlink bandwidth in a cell in terms of coding scheme 4 for a statistics collection period.
Formula
For GSR6 (Horizon II) the formula is:
_
_ _ _ _
68P02901W56-Q 18-33
24 May 2004 CONTROLLED INTRODUCTION
DOWNLINK_TRAFFIC_VOLUME Chapter 18: Network health reports
DOWNLINK_TRAFFIC_VOLUME
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
Formula
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _
QoS identifies how delay sensitive the traffic is. Currently only QoS3 is implemented which
is the most delay insensitive traffic class - it is defined as Best Effort.
18-34 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DOWNLINK_TRAFFIC_VOLUME
68P02901W56-Q 18-35
24 May 2004 CONTROLLED INTRODUCTION
DROP_CALL_RATE Chapter 18: Network health reports
DROP_CALL_RATE
Description
The DROP_CALL_RATE statistic tracks the percentage of MSs which, having successfully
accessed a TCH, subsequently experience an abnormal release caused by either radio or equipment
problems. This includes RF losses and losses during handovers.
Formulas
Cell Level
{22064}
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _
_
_ _ _ _ _ _ _
_ _ _ _ _ _ _
BSS Level
{22064}
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _
_
_ _
_ _
_ _
_ _ _ _ _ _ _
Network Level
{22064}
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _
_
_ _
_ _
_ _
18-36 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application DROP_CALL_RATE
Analysis
68P02901W56-Q 18-37
24 May 2004 CONTROLLED INTRODUCTION
GBL_AVAILABILITY Chapter 18: Network health reports
GBL_AVAILABILITY
Description
The GBL_AVAILABILITY statistic measures the availability for a particular Gb link (GBL).
Formula
_ _
_
18-38 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GPRS_BW_USAGE_DL
GPRS_BW_USAGE_DL
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
The GPRS_BW_USAGE_DL statistic measures the bandwidth usage in the downlink direction and
provides an indication of the adequacy of the deployed cell capacity.
Formula
_ _ _
_ _ _
_ _
68P02901W56-Q 18-39
24 May 2004 CONTROLLED INTRODUCTION
GPRS_BW_USAGE_UL Chapter 18: Network health reports
GPRS_BW_USAGE_UL
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
The GPRS_BW_USAGE_UL statistic measures the bandwidth usage in the uplink direction and
provides an indication of the adequacy of the deployed cell capacity.
Formula
_ _ _
_ _ _
_ _
18-40 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GPRS_DL_ACT_TS
GPRS_DL_ACT_TS
Description
The GPRS_DL_ACT_TS statistic measures the utilization of busy downlink PDTCHs in a cell.
Formula
_ _ _ _ _ _
68P02901W56-Q 18-41
24 May 2004 CONTROLLED INTRODUCTION
GPRS_UL_ACT_TS Chapter 18: Network health reports
GPRS_UL_ACT_TS
Description
The GPRS_UL_ACT_TS statistic measures the utilization of busy uplink PDTCHs in a cell.
Formula
_ _ _ _ _ _
18-42 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application HO_CAUSE_ADJ_CH_INTERF
HO_CAUSE_ADJ_CH_INTERF
Description
Formula
_ _ _ _ _ _ _
_ _ _ _ _
68P02901W56-Q 18-43
24 May 2004 CONTROLLED INTRODUCTION
HO_CAUSE_BAND_HO Chapter 18: Network health reports
HO_CAUSE_BAND_HO
Description
The HO_CAUSE_BAND_HO statistic provides the percentage of all handovers due to band handover.
Formula
_ _ _ _ _ _
_ _ _ _
18-44 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application HO_CAUSE_BAND_REASSGN
HO_CAUSE_BAND_REASSGN
Description
Formula
_ _ _ _ _ _ _
_ _ _ _
68P02901W56-Q 18-45
24 May 2004 CONTROLLED INTRODUCTION
HO_CAUSE_CONGEST Chapter 18: Network health reports
HO_CAUSE_CONGEST
Description
Formula
_ _ _ _ _
_ _ _
18-46 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application HO_CAUSE_DISTANCE
HO_CAUSE_DISTANCE
Description
Formula
_ _ _ _ _
_ _ _
68P02901W56-Q 18-47
24 May 2004 CONTROLLED INTRODUCTION
HO_CAUSE_DLINTERF Chapter 18: Network health reports
HO_CAUSE_DLINTERF
Description
The HO_CAUSE_DLINTERF statistic provides the percentage of all handovers due to downlink interference.
Formula
_ _ _ _ _
_ _ _
18-48 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application HO_CAUSE_DLLEVEL
HO_CAUSE_DLLEVEL
Description
The HO_CAUSE_DLLEVEL statistic provides the percentage of all handovers due to downlink level.
Formula
_ _ _ _ _
_ _ _
68P02901W56-Q 18-49
24 May 2004 CONTROLLED INTRODUCTION
HO_CAUSE_DLQUAL Chapter 18: Network health reports
HO_CAUSE_DLQUAL
Description
The HO_CAUSE_DLQUAL statistic provides the percentage of all handovers due to downlink quality.
Formula
_ _ _ _ _
_ _ _
18-50 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application HO_CAUSE_PWRBGT
HO_CAUSE_PWRBGT
Description
The HO_CAUSE_PWRBGT statistic provides the percentage of all handovers due to power budget.
Formula
_ _ _ _ _
_ _ _
68P02901W56-Q 18-51
24 May 2004 CONTROLLED INTRODUCTION
HO_CAUSE_UPINTERF Chapter 18: Network health reports
HO_CAUSE_UPINTERF
Description
The HO_CAUSE_UPINTERF statistic provides the percentage of all handovers due to uplink interference.
Formula
_ _ _ _ _
_ _ _
18-52 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application HO_CAUSE_UPLEVEL
HO_CAUSE_UPLEVEL
Description
The HO_CAUSE_UPLEVEL statistic provides the percentage of all handovers due to uplink level.
Formula
_ _ _ _ _
_ _ _
68P02901W56-Q 18-53
24 May 2004 CONTROLLED INTRODUCTION
HO_CAUSE_UPQUAL Chapter 18: Network health reports
HO_CAUSE_UPQUAL
Description
The HO_CAUSE_UPQUAL statistic provides the percentage of all handovers due to uplink quality.
Formula
_ _ _ _ _
_ _ _
18-54 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application HO_PER_CALL
HO_PER_CALL
Description
The HO_PER_CALL statistic tracks the average number of successful handovers per call.
Formula
Cell Level
_ _ _ _
_ _ _ _ _ _ _
_ _
_
BSS Level
_ _ _ _
_ _ _ _ _ _ _
_ _
_
_ _
_ _
_ _
Network Level
_ _ _ _
_ _ _ _ _ _ _
_ _
_
_ _
_ _
_ _
68P02901W56-Q 18-55
24 May 2004 CONTROLLED INTRODUCTION
IN_INTER_BSS_HO_SUC Chapter 18: Network health reports
IN_INTER_BSS_HO_SUC
Description
The IN_INTER_BSS_HO_SUC statistic tracks the percentage of incoming inter-BSS handover commands
that are sent over the air interface which result in the MS successfully accessing the target channel.
Formula
_ _ _ _ _ _ _
_ _ _ _ _
18-56 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application IN_INTER_CELL_HO_SUC
IN_INTER_CELL_HO_SUC
Description
The IN_INTER_CELL_HO_SUC statistic tracks the percentage of incoming inter-cell handover commands
that are sent over the air interface which result in the MS successfully accessing the target channel.
Formula
_ _ _ _ _ _ _ _ _ _ _
_ _ _ _
_ _ _ _
_ _ _
_ _
_ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _
_ _ _ _
68P02901W56-Q 18-57
24 May 2004 CONTROLLED INTRODUCTION
IN_INTRA_BSS_HO_SUC Chapter 18: Network health reports
IN_INTRA_BSS_HO_SUC
Description
The IN_INTRA_BSS_HO_SUC statistic tracks the percentage of incoming intra-BSS handover commands
that are sent over the air interface which result in the MS successfully accessing the target channel.
Formula
_ _ _ _ _ _ _
_ _ _ _
_ _ _ _
_ _ _
_ _
_ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _
18-58 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application INCOMING_HO_VOLUME
INCOMING_HO_VOLUME
Description
Formulas
Cell Level
_ _ _ _ _ _ _
_ _
_ _ _ _ _ _ _
BSS Level
_ _ _ _ _ _ _ _ _
68P02901W56-Q 18-59
24 May 2004 CONTROLLED INTRODUCTION
INTERNAL_LOST Chapter 18: Network health reports
INTERNAL_LOST
Description
The INTERNAL_LOST statistic tracks the percentage of BSS internal handover commands that are sent
over the air interface which result in the MS failing to access the target and failing to recover to the original
channel; that is, the call drops. This statistic includes intra-BSS and intra-cell handovers.
Formula
_ _ _ _ _ _ _
_ _ _ _ _
_
_ _ _ _ _ _ _
_ _ _ _ _
18-60 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application INTERNAL_RECOVERED
INTERNAL_RECOVERED
Description
The INTERNAL_RECOVERED statistic tracks the percentage of BSS internal handover commands that
are sent over the air interface which result in the MS failing to access the target channel and successfully
recovering to the original channel. This statistic includes intra-BSS and intra-cell handovers.
Formula
_ _ _ _ _ _ _
_ _ _ _ _
_
_ _ _ _ _ _ _
_ _ _ _ _
68P02901W56-Q 18-61
24 May 2004 CONTROLLED INTRODUCTION
INTERNAL_SUCCESS Chapter 18: Network health reports
INTERNAL_SUCCESS
Description
The INTERNAL_SUCCESS statistic tracks the percentage of BSS internal handover commands
that are sent over the air interface which result in the MS successfully accessing the target
channel. This statistic includes intra-BSS and intra-cell handovers.
Formula
_ _ _ _ _ _ _
_ _ _ _ _
_
_ _ _ _ _ _ _
_ _ _ _ _
18-62 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application INTRA_CELL_HO_FAIL_LOST_MS
INTRA_CELL_HO_FAIL_LOST_MS
Description
Formula
_ _ _ _ _ _ _ _
_ _ _ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
68P02901W56-Q 18-63
24 May 2004 CONTROLLED INTRODUCTION
INTRA_CELL_HO_FAIL_RECOVERED Chapter 18: Network health reports
INTRA_CELL_HO_FAIL_RECOVERED
Description
Formula
_ _ _ _ _ _ _ _
_ _ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
18-64 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application INTRA_CELL_HO_SUCCESS_RATE
INTRA_CELL_HO_SUCCESS_RATE
Description
Formula
_ _ _ _ _ _ _ _
_ _ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
68P02901W56-Q 18-65
24 May 2004 CONTROLLED INTRODUCTION
MAX_TCH_BUSY Chapter 18: Network health reports
MAX_TCH_BUSY
Description
The MAX_TCH_BUSY statistic tracks the maximum number of simultaneously busy TCHs.
Formula
_ _ _
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Counter.
Raw Statistics BUSY_TCH[MAX].
18-66 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MSC_PAGING
MSC_PAGING
Description
The MSC_PAGING statistic tracks the total number of BSSMAP paging messages
received over the A-interface from the MSC.
Formula
_ _ _ _
68P02901W56-Q 18-67
24 May 2004 CONTROLLED INTRODUCTION
MEAN_TIME_BETWEEN_DROPS Chapter 18: Network health reports
MEAN_TIME_BETWEEN_DROPS
Description
Formula
{22064}
_ _
_
_ _ _ _ _
_ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
Analysis
18-68 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MEAN_TIME_BETWEEN_HOs
MEAN_TIME_BETWEEN_HOs
Description
The MEAN_TIME_BETWEEN_HOs statistic tracks the mean time interval between inter cell handovers.
Formula
{22064}
_ _
_
_ _ _ _ _
_ _ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _
Analysis
68P02901W56-Q 18-69
24 May 2004 CONTROLLED INTRODUCTION
OUT_INTER_BSS_HO_FAIL_LOST_MS Chapter 18: Network health reports
OUT_INTER_BSS_HO_FAIL_LOST_MS
Description
Formula
_ _ _ _ _ _ _ _ _
_ _ _ _ _
18-70 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application OUT_INTER_BSS_HO_FAIL_RECOVERED
OUT_INTER_BSS_HO_FAIL_RECOVERED
Description
Formula
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _
68P02901W56-Q 18-71
24 May 2004 CONTROLLED INTRODUCTION
OUT_INTER_BSS_HO_SUCCESS_RATE Chapter 18: Network health reports
OUT_INTER_BSS_HO_SUCCESS_RATE
Description
Formula
_ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _
18-72 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS
OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS
Description
Formula
_ _ _ _
_ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _
68P02901W56-Q 18-73
24 May 2004 CONTROLLED INTRODUCTION
OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED_MS Chapter 18: Network health reports
OUT_INTER_CELL_HO_FAIL_RATE_
RECOVERED_MS
Description
Formula
_ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _
_ _ _ _ _ _ _ _
_ _ _ _ _ _ _
18-74 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application OUT_INTER_CELL_HO_SUCCESS_RATE
OUT_INTER_CELL_HO_SUCCESS_RATE
Description
Formula
_ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _
_ _ _ _
68P02901W56-Q 18-75
24 May 2004 CONTROLLED INTRODUCTION
OUT_INTER_CELL_HO_SUCCESS_RATE_RECOVERED_MS Chapter 18: Network health reports
OUT_INTER_CELL_HO_SUCCESS_RATE_
RECOVERED_MS
Description
Formula
_ _ _ _
_ _ _ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _ _
18-76 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application OUT_INTRA_BSS_HO_FAIL_LOST_MS
OUT_INTRA_BSS_HO_FAIL_LOST_MS
Description
Formula
_ _ _ _ _ _ _ _ _
_ _ _ _ _
68P02901W56-Q 18-77
24 May 2004 CONTROLLED INTRODUCTION
OUT_INTRA_BSS_HO_FAIL_RECOVERED_MS Chapter 18: Network health reports
OUT_INTRA_BSS_HO_FAIL_RECOVERED_MS
Description
Formula
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _
18-78 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application OUT_INTRA_BSS_HO_SUC
OUT_INTRA_BSS_HO_SUC
Description
The OUT_INTRA_BSS_HO_SUC statistic tracks the percentage of intra-BSS handover commands that are
sent over the air interface which result in the MS successfully accessing the target channel.
Formula
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _
68P02901W56-Q 18-79
24 May 2004 CONTROLLED INTRODUCTION
OUTGOING_HO_VOLUME Chapter 18: Network health reports
OUTGOING_HO_VOLUME
Description
Formula
_ _ _ _ _ _ _
_ _
_ _ _ _ _ _ _
18-80 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application PAGING_COMPRESSION_RATE
PAGING_COMPRESSION_RATE
Description
The PAGING_COMPRESSION_RATE statistic provides a measure of page packing on the air interface.
Formula
_ _ _ _ _ _
_ _ _ _ _
_ _ _ _ _ _
_
_ _ _
_ _ _
68P02901W56-Q 18-81
24 May 2004 CONTROLLED INTRODUCTION
PAGING_OVERFLOW_RATE Chapter 18: Network health reports
PAGING_OVERFLOW_RATE
Description
The PAGING_OVERFLOW_RATE statistic tracks the percentage of pages which are dropped
from the BSS paging queue due to paging queue overflow. There are two formulas based on
the paging purpose (circuit switched or packet switched).
Formulas
Circuit switched
_ _ _ _ _
_ _ _ _
Packet switched
_ _ _ _ _
_ _ _ _
18-82 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application PAGING_RESPONSE
PAGING_RESPONSE
Description
Formula
_ _ _ _
68P02901W56-Q 18-83
24 May 2004 CONTROLLED INTRODUCTION
PAGING_SUCCESS_RATE Chapter 18: Network health reports
PAGING_SUCCESS_RATE
Description
The PAGING_SUCCESS_RATE statistic tracks the percentage of pages which receive a successful
response from an MS. This statistic is measured on a location area basis.
Formula
_ _ _
_ _
_
18-84 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application PERCENTAGE_INTER_BSS_HO
PERCENTAGE_INTER_BSS_HO
Description
The PERCENTAGE_INTER_BSS_HO statistic calculates the percentage of all inter-BSS handover attempts.
Formula
_ _ _ _ _
_ _ _ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _
68P02901W56-Q 18-85
24 May 2004 CONTROLLED INTRODUCTION
PERCENTAGE_INTRA_BSS_HO Chapter 18: Network health reports
PERCENTAGE_INTRA_BSS_HO
Description
The PERCENTAGE_INTRA_BSS_HO statistic calculates the percentage of all intra-BSS handover attempts.
Formula
_ _ _ _ _
_ _ _ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _
18-86 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application PERCENTAGE_INTRA_CELL_HO
PERCENTAGE_INTRA_CELL_HO
Description
Formula
_ _ _ _
_ _ _ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _
68P02901W56-Q 18-87
24 May 2004 CONTROLLED INTRODUCTION
PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK Chapter 18: Network health reports
PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
Formula
_ _ _ _ _ _ _
_ _ _ _ _ _ _
18-88 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application RANKING_FORMULA
RANKING_FORMULA
Description
Formula
_ _ _
_
_ _ _
Usage Optimization.
Service retainability.
Basis Cell.
Type Counter.
Raw Statistics ASSIGNMENT_REDIRECTION.
INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS].
MT_LCS_ON_SDCCH.
IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].
IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].
OK_ACC_PROC[CM_REESTABLISH].
OK_ACC_PROC[CM_SERV_REQ_CALL].
OK_ACC_PROC[CM_SERV_REQ_EMERG].
OK_ACC_PROC[CM_SERV_REQ_SMS].
OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL].
OK_ACC_PROC[LOC_FLW_ON_REQ_SMS].
OK_ACC_PROC[PAGE_RESPONSE].
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS].
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_CLEARED].
RF_LOSSES_TCH.
SMS_INIT_ON_SDCCH.
TOTAL_CALLS.
68P02901W56-Q 18-89
24 May 2004 CONTROLLED INTRODUCTION
RF_ASSIGN_FAIL_RATE_LOST_MS Chapter 18: Network health reports
RF_ASSIGN_FAIL_RATE_LOST_MS
Description
Formula
_ _ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _
18-90 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application RF_ASSIGN_FAIL_RATE_RECOVERED
RF_ASSIGN_FAIL_RATE_RECOVERED
Description
Formula
_ _ _
_ _ _ _
_ _ _
68P02901W56-Q 18-91
24 May 2004 CONTROLLED INTRODUCTION
RF_ASSIGNMENT_SUCCESS_RATE Chapter 18: Network health reports
RF_ASSIGNMENT_SUCCESS_RATE
Description
Formula
_ _ _
_ _ _
_ _ _
18-92 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SDCCH_ACCESSES
SDCCH_ACCESSES
Description
Formula
_ _ _ _ _
Usage RF loss.
Congestion.
Quality of service.
Network planning.
Basis Cell.
Type Counter.
Raw Statistics ALLOC_SDCCH.
CHAN_REQ_MS_FAIL.
68P02901W56-Q 18-93
24 May 2004 CONTROLLED INTRODUCTION
SDCCH_BLOCKING_RATE Chapter 18: Network health reports
SDCCH_BLOCKING_RATE
Description
The SDCCH_BLOCKING_RATE statistic tracks the percentage of attempts to allocate an SDCCH that were
blocked due to no available SDCCH resources. This statistic includes incoming SDCCH handover attempts.
Formula
_ _
_ _
_ _ _
18-94 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SDCCH_CONGESTION_TIME
SDCCH_CONGESTION_TIME
Description
The SDCCH_CONGESTION_TIME statistic tracks the amount of time in seconds that all SDCCHs are busy.
Formula
_
_ _
Usage RF loss.
Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Duration (seconds).
Raw Statistics SDCCH_CONGESTION.
68P02901W56-Q 18-95
24 May 2004 CONTROLLED INTRODUCTION
SDCCH_TRAFFIC_CARRIED Chapter 18: Network health reports
SDCCH_TRAFFIC_CARRIED
Description
Formula
_ _ _ _
_ _
_ _
_ _ _ _
_ _
_ _
18-96 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SDCCH_TRAFFIC_CARRIED
68P02901W56-Q 18-97
24 May 2004 CONTROLLED INTRODUCTION
SDCCH_USAGE_ACCESS_FAILURE Chapter 18: Network health reports
SDCCH_USAGE_ACCESS_FAILURE
Description
Formula
_ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _
18-98 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SDCCH_USAGE_CALL_REESTABLISH
SDCCH_USAGE_CALL_REESTABLISH
Description
Formula
_ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _
68P02901W56-Q 18-99
24 May 2004 CONTROLLED INTRODUCTION
SDCCH_USAGE_EMERGENCY_CALL Chapter 18: Network health reports
SDCCH_USAGE_EMERGENCY_CALL
Description
Formula
_ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _
18-100 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SDCCH_USAGE_IMSI_DETACH
SDCCH_USAGE_IMSI_DETACH
Description
Formula
_ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _
68P02901W56-Q 18-101
24 May 2004 CONTROLLED INTRODUCTION
SDCCH_USAGE_LOCATION_UPDATE Chapter 18: Network health reports
SDCCH_USAGE_LOCATION_UPDATE
Description
Formula
_ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _
18-102 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SDCCH_USAGE_MS_ORIGINATED_CALL
SDCCH_USAGE_MS_ORIGINATED_CALL
Description
Formula
_ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _
68P02901W56-Q 18-103
24 May 2004 CONTROLLED INTRODUCTION
SDCCH_USAGE_MS_ORIGINATED_SMS Chapter 18: Network health reports
SDCCH_USAGE_MS_ORIGINATED_SMS
Description
Formula
_ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _
18-104 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SDCCH_USAGE_SMS_ORIGINATED_SS
SDCCH_USAGE_SMS_ORIGINATED_SS
Description
Formula
_ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _
68P02901W56-Q 18-105
24 May 2004 CONTROLLED INTRODUCTION
SDCCH_USAGE_PAGING_RESPONSE Chapter 18: Network health reports
SDCCH_USAGE_PAGING_RESPONSE
Description
Formula
_ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _
18-106 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SDCCH_USAGE_SMS
SDCCH_USAGE_SMS
Description
The SDCCH_USAGE_SMS statistic tracks the percentage of immediate assignment SDCCH activations
that are due to mobile originated or mobile terminated SMS attempts.
Formula
_ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _
68P02901W56-Q 18-107
24 May 2004 CONTROLLED INTRODUCTION
SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGESTION_RELIEF Chapter 18: Network health reports
SPILL_OVER_FACTOR_ATTEMPTS_AT_
CONGESTION_RELIEF
Description
Formula
_ _ _ _ _ _
_ _
_ _
_ _
_ _
_ _
18-108 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application SPILL_OVER_FACTOR_DIRECTED_RETRY
SPILL_OVER_FACTOR_DIRECTED_RETRY
Description
Formula
_ _
_ _ _ _ _
_ _
_ _
_ _
_ _
68P02901W56-Q 18-109
24 May 2004 CONTROLLED INTRODUCTION
SPILL_OVER_FACTOR_MULTIBAND Chapter 18: Network health reports
SPILL_OVER_FACTOR_MULTIBAND
Description
Formula
_ _ _ _ _
_
_ _
_ _
_ _
18-110 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application TCH_ACCESSES
TCH_ACCESSES
Description
The TCH_ACCESSES statistic tracks the number of TCH activations which result
in a successful seizure by the MS.
Formula
Cell Level
_
_ _ _ _ _
_ _ _ _
BSS Level
_
_ _ _ _
_ _ _
_ _
_ _
Network Level
_
_ _ _
_ _
_ _
68P02901W56-Q 18-111
24 May 2004 CONTROLLED INTRODUCTION
TCH_ACCESSES Chapter 18: Network health reports
Usage Handover.
Quality of service.
Network planning.
Basis Cell, BSS, or network.
Type Counter.
Raw Statistics ASSIGNMENT_REDIRECTION.
IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].
IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].
TOTAL_CALLS.
18-112 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application TCH_CONGESTION_TIME
TCH_CONGESTION_TIME
Description
The TCH_CONGESTION_TIME statistic tracks the amount of time in seconds that all TCHs are busy.
Formula
_
_ _
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Duration.
Raw Statistics TCH_CONGESTION.
68P02901W56-Q 18-113
24 May 2004 CONTROLLED INTRODUCTION
TCH_CONGESTION_TIME_INNER_ZONE Chapter 18: Network health reports
TCH_CONGESTION_TIME_INNER_ZONE
Description
Formula
_ _ _ _ _ _
_
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Duration.
Raw Statistics TCH_CONGESTION_INNER_Z.
18-114 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application TCH_CONGESTION_TIME_OUTER_ZONE
TCH_CONGESTION_TIME_OUTER_ZONE
Description
Formula
_ _ _ _
_
{22064} When the Half Rate feature is unrestricted, the following formula tracks the amount
of time in seconds that all outer zone half rate TCHs are busy:
_ _ _ _ _
_ _
Analysis
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Duration.
Raw Statistics TCH_CONGESTION.
{22064} Additional Raw Statistic TCH_CONGESTION_HR.
for Half Rate
68P02901W56-Q 18-115
24 May 2004 CONTROLLED INTRODUCTION
TCH_RF_LOSS_RATE Chapter 18: Network health reports
TCH_RF_LOSS_RATE
Description
The TCH_RF_LOSS_RATE statistic tracks the percentage of TCH resources that are
abnormally released due to a failure on the radio interface.
Formula
Cell Level
{22064}
_ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _ _
BSS Level
{22064}
_ _ _ _ _
_ _ _
_
_ _
_ _
_ _
_ _ _ _ _ _
Network Level
{22064}
_ _ _ _ _
_ _ _
_
_ _
_ _
_ _
Analysis
18-116 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application TCH_RF_LOSS_RATE
Type Percentage.
Raw Statistics ASSIGNMENT_REDIRECTION (The value used in this formula
is the sum of bins 0 to 2 of this counter array statistic).
IN_INTER_BSS[IN_INTER_HO_SUC].
IN_INTRA_BSS[IN_INTRA_BSS_HO_SUC].
RF_LOSSES_TCH.
{22064}RF_LOSSES_TCH_HR.
TOTAL_CALLS.
68P02901W56-Q 18-117
24 May 2004 CONTROLLED INTRODUCTION
TCH_TRAFFIC_CARRIED Chapter 18: Network health reports
TCH_TRAFFIC_CARRIED
Description
The TCH_TRAFFIC_CARRIED statistic tracks the mean number of busy TCHs measured in Erlangs.
Formula
_ _ _ _ _
_ _
_ _ _ _ _ _ _
_ _ _ _ _
_ _
18-118 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application TCH_TRAFFIC_CARRIED
Analysis
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Units = Erlangs.
Raw Statistics BUSY_TCH (BUSY_TCH_MEAN).
{22064}BUSY_TCH_HR (BUSY_TCH_HR_MEAN).
68P02901W56-Q 18-119
24 May 2004 CONTROLLED INTRODUCTION
UL_AIR_INTERFACE_BW_CS1 Chapter 18: Network health reports
UL_AIR_INTERFACE_BW_CS1
Description
The UL_AIR_INTERFACE_BW_CS1 statistic provides a reference value for the configured uplink
bandwidth in a cell in terms of coding scheme 1 for a statistics collection period.
Formula
For GSR6 (Horizon II) the formula is:
_
_ _ _ _
18-120 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application UL_AIR_INTERFACE_BW_CS2
UL_AIR_INTERFACE_BW_CS2
Description
The UL_AIR_INTERFACE_BW_CS2 statistic provides a reference value for the configured uplink
bandwidth in a cell in terms of coding scheme 2 for a statistics collection period.
Formula
For GSR6 (Horizon II) the formula is:
_
_ _ _ _
68P02901W56-Q 18-121
24 May 2004 CONTROLLED INTRODUCTION
UL_AIR_INTERFACE_BW_CS3 Chapter 18: Network health reports
UL_AIR_INTERFACE_BW_CS3
Description
The UL_AIR_INTERFACE_BW_CS3 statistic provides a reference value for the configured uplink
bandwidth in a cell in terms of coding scheme 3 for a statistics collection period.
Formula
For GSR6 (Horizon II) the formula is:
_
_ _ _ _
18-122 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application UL_AIR_INTERFACE_BW_CS4
UL_AIR_INTERFACE_BW_CS4
Description
The UL_AIR_INTERFACE_BW_CS4 statistic provides a reference value for the configured uplink
bandwidth in a cell in terms of coding scheme 4 for a statistics collection period.
Formula
For GSR6 (Horizon II) the formula is:
_
_ _ _ _
68P02901W56-Q 18-123
24 May 2004 CONTROLLED INTRODUCTION
UPLINK_PDTCH_BLOCKING_RATE Chapter 18: Network health reports
UPLINK_PDTCH_BLOCKING_RATE
Description
The UPLINK_PDTCH_BLOCKING_RATE statistic provides the success rate of channel requests in GPRS.
Formula
18-124 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application UPLINK_TRAFFIC_VOLUME
UPLINK_TRAFFIC_VOLUME
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Description
Formula
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _
QoS identifies how delay sensitive the traffic is. Currently only QoS3 is implemented which
is the most delay insensitive traffic class - it is defined as Best Effort.
68P02901W56-Q 18-125
24 May 2004 CONTROLLED INTRODUCTION
UPLINK_TRAFFIC_VOLUME Chapter 18: Network health reports
18-126 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
19
Ladder diagrams
Ladder diagrams show the relationships between MS, BSS, and MSC when a message flows between
these network elements. The following topics are described in this chapter:
• "Ladder diagram constructs" on page 19-2
68P02901W56-Q 19-1
24 May 2004 CONTROLLED INTRODUCTION
Ladder diagram constructs Chapter 19: Ladder diagrams
• Provide a visual aid in tracing the statistical processes involved when an event occurs.
The message flows between the network elements are presented as horizontal lines representing
a sequential flow of events. Arrows indicate the direction of the message flow. Message
names are placed above the directional line.
Intermediate network element functions are placed on the vertical lines as a sequential reference. Parallel
functions may also be included as separate vertical lines for additional reference.
Statistics associated with individual messages are located immediately below the directional line. All of
the statistics that may be generated as the result of the process flow is listed on the diagram.
As an example, Figure 19-1 shows the relationships associated with an immediate assignment failure.
TIMEOUT
CHAN_REQ_MS_FAIL
19-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Phone call model
• BSC functions
• MSC functions
• Handover procedure
BSS functions
The GSM BSS is a combination of digital and RF equipment, the purpose of which is to provide
the radio Air interface linking subscribers into the network and providing them with service. The
BSS function is to communicate with the Mobile Switching Centre (MSC), the Operations and
Maintenance Centre - Radio (OMC-R), and the Mobile Subscribers (MSs).
BSC functions
The main functions of the BSC include managing the radio channels and transferring control messages
to and from the MS. Control channels and bearer channels are always under the control of the
BSC. However, many types of call handling messages do not directly affect the BSC and for these
the BSC serves simply as a relay point between the MSC and the MS.
The BSC also incorporates a digital switching matrix. No fixed correspondence exists between the radio
channels at the BSS and the terrestrial circuits, which connect the BSS to the MSC. While the BSC selects
the radio channel, the terrestrial circuit is selected by the MSC, and it is the BSCs switching matrix that
is used to connect the two together. The switching matrix also allows the BSC to perform handovers
between the BTSs under its control without involving the MSC (intra-BSS and intra-cell).
MSC functions
The MSC handles the call set up procedures and controls the location registration and handover
procedures for all except intra-BSS and intra-cell handovers. MSC controlled intra-BSS handovers
can be set as an option at the switch. Location registration (and location update) allows MSs to report
changes in their locations enabling automatic completion of MS-terminated calls.
68P02901W56-Q 19-3
24 May 2004 CONTROLLED INTRODUCTION
Phone call model Chapter 19: Ladder diagrams
Handover procedure
The handover procedure preserves call connections as MSs move from one radio coverage area to
another during an established call. Handovers within cells controlled by a single BSC are handled
by that BSC (intra-BSS and intra-cell). When handovers are between cells controlled by different
BSCs, the primary control is at the MSC (inter-BSS). Handovers can also be performed between BSSs
connected to two different MSCs (inter-MSC handover). In this case, GSM specifications define
standard procedures allowing the two MSCs to coordinate the handover.
OMC-R
MSC BSC
INTER-BSS
BSC BSS
BTS
INTRA-BSS
TDMA FRAMES
BTS
0 1 2 3 4 5 6 7
NOTE: Intra-cell handovers are performed primarily due to poor quality and not to poor level.
0 1 2 3 4 5 6 7
INTRA-CELL
19-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Call procedure milestones
A general description of the milestones in a call procedureis explained in the following paragraphs.
Call procedure
Bids
The first call procedure milestone is a request for service or resource (channel assignment request). At this
point the MS will check the possibility of making a call, before attempting to make a call.
Bids - attempts
A bid is made and accepted to use a resource (channel assignment request). Now an attempt is made to assign
the user to that resource, for example with a traffic channel assignment there is an assignment request from the
MSC, but at this time the assignment to the TCH is not complete. Hence, the connection is not complete.
68P02901W56-Q 19-5
24 May 2004 CONTROLLED INTRODUCTION
Call setup and handover Chapter 19: Ladder diagrams
Statistics matrix
The call setup and handover statistics are shown as a matrix against call processing scenarios
in Table 19-1. Each call processing scenario is broken out into six call procedure milestones
shown in the vertical columns of the matrix.
Milestones
Procedure Failed
Bids Blocked Attempts Success Failed lost
recovered
Immediate OK_ACC_ CHAN_REQ_ see note 3 OK_ACC_ CHAN_REQ_ N/A
Assignment PROC_RACH MS_BLK PROC MS_FAIL or
and AL- and AL- INV_EST_
LOC_SD- LOC_SD- CAUSE_IN_RACH
CCH see CCH_ see note 5
note 1 FAIL see
note 2
Connection - - CONN_REQ_ - CONN_RE- N/A
Establish- TO_MSC FUSED
ment
Assignment MA_REQ_ MA_CMD_ MA_CMD_ TO- For further MA_FAIL_
to TCH at FROM_MSC TO_MS_ TO_MSC TAL_CALLS study FROM_MS
call set-up BLKDALLOC_ and
TCH_FAIL MA_COM-
PLETE_
TO_MSCALLOC_
TCH
Handover IN- AL- IN- IN- IN- IN-
Intra-cell TRA_CELL_ LOC_SD- TRA_CELL_ TRA_CELL_ TRA_CELL_ TRA_CELL_
HO_REQ CCH_ HO_ATMPT HO HO_LOSTMS HO_FAIL
FAIL or and and
HO_FAIL_ MA_CMD_ MA_FAIL_
NO_ RE- TO_MS FROM_MS
SOURCES
(IN-
TER_BSS)
or AL-
LOC_TCH_
FAIL
19-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Call setup and handover
68P02901W56-Q 19-7
24 May 2004 CONTROLLED INTRODUCTION
Call setup and handover Chapter 19: Ladder diagrams
Notes
The following notes refer to the call setup and handover matrix:
1. OK_ACC_PROC_SUC_RACH may be, but is not necessarily equal to ALLOC_SDCCH
because they are pegged by different processes and filtering takes place between the
two pegs. ALLOC_SDCCH is pegged at the target cell for SDCCH Handovers.
If OK_ACC_PROC_SUC_RACH is less than ALLOC_SDCCH, some of the
ALLOC_SDCCH pegs are due to SDCCH Handovers into the cell. And if
ALLOC_SDCCH is less than OK_ACC_PROC_SUC_RACH, some of the
RACHs have been filtered between the two pegs.
19-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Connection establishment
Connection establishment
Figure 19-3 to Figure 19-7 show the ladder diagrams for the connection establishment procedures.
Figure 19-3 shows that connection establishment is successful after immediate assignment is successful,
while Figure 19-7 shows successful mobile-terminated connection establishment.
68P02901W56-Q 19-9
24 May 2004 CONTROLLED INTRODUCTION
Connection establishment Chapter 19: Ladder diagrams
{ - or -
OK_ACC_PROC[CM REESTABLISHMENT]
- or -
OK_ACC_PROC[PAGE RESPONSE]
- or -
OK_ACC_PROC[LOCATION UPDATE]
- or -
OK_ACC_PROC[IMSI DETACH]
IMMEDIATE ASSIGNMENT
CONNECTION REQUEST
CONN_REQ_TO_MSC
CONNECTION CONFIRM
CONNECTION ESTABLISHMENT
MOBILE ORIGINATED
NOTE: RSS Abis does additional filtering of RACH.
19-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Connection establishment
Failure
MS BSS MSC
CHANNEL REQUEST (RACH)
OK_ACC_PROC_SUC_RACH (SEE NOTE)
ACCESS_PER_RACH
CHAN_REQ_CAUSE_ATMPT
(for one of the causes)
MS_ACCESS_BY_TYPE
ALLOC_SDCCH
{
OK_ACC_PROC[CM SERV. REQ. - CALL]
- or -
OK_ACC_PROC[CM REESTABLISHMENT]
- or -
OK_ACC_PROC[PAGE RESPONSE]
- or -
OK_ACC_PROC[LOCATION UPDATE]
- or -
OK_ACC_PROC[IMSI DETACH]
IMMEDIATE ASSIGNMENT
CONNECTION REQUEST
CONN_REQ_TO_MSC
< CREF>
CONN_REFUSED
68P02901W56-Q 19-11
24 May 2004 CONTROLLED INTRODUCTION
Connection establishment Chapter 19: Ladder diagrams
ACCESS_PER_AGCH
TIMEOUT
CHAN_REQ_MS_FAIL
19-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Connection establishment
MS BSS MSC
PAGING
PAGE_REQ_FROM_MSC
PAGING REQUEST
ACCESS_PER_PCH
CHANNEL REQUEST (RACH)
ACCESS_PER_RACH
CHAN_REQ_CAUSE_ATMPT
(PAGING RESPONSE)
MS_ACCESS_BY_TYPE
ALLOC_SDCCH
ACCESS_PER_AGCH
SABMT INITIAL LAYER 3 MESSAGE (SDCCH)
OK_ACC_PROC (PAGING_RESPONSE)
IMMEDIATE ASSIGNMENT
CONNECTION REQUEST
CONN_REQ_TO_MSC
CONNECTION CONFIRM
< CC>
CONNECTION ESTABLISHMENT
(MOBILE TERMINATED)
NOTE: RSS Abis does additional filtering of RACH.
68P02901W56-Q 19-13
24 May 2004 CONTROLLED INTRODUCTION
Assignment to TCH Chapter 19: Ladder diagrams
Assignment to TCH
Figure 19-8 to Figure 19-11 show the ladder diagrams for the assignment to TCH procedures.
Assignment successful
MA_REQ_FROM_MSC
ALLOC_TCH
ASSIGNMENT COMMAND (SDCCH)
MA_CMD_TO_MS
MA_COMPLETE_FROM_MS
ASSIGNMENT COMPLETE
TOTAL_CALLS
(SEE NOTE 1)
MA_COMPLETE_TO_MSC
MS_TCH_USAGE_BY_TYPE
(SEE NOTE 2)
NOTES:
1. Pegged for the first successful TCH assignment.
2. Pegged to start the length of time spent on TCH by various typesof MS. Will not
be pegged after the TCH is deallocated.
19-14 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Assignment to TCH
OK_ACC_PROC_SUC_RACH
(SEE NOTE 1)
CHAN_REQ_CAUSE_ATMPT
(for one of the causes)
INV_EST_CAUSE_ON_RACH
(SEE NOTE 2)
NOTES:
1. RSS Abis does additional filtering of RACH.
2. RSS Abis filtering detects and invalid channel request on RACH.
MA_REQ_FROM_MSC
ALLOC_TCH_FAIL
MA_CMD_TO_MS_BLKD
ASSIGNMENT FAILURE
68P02901W56-Q 19-15
24 May 2004 CONTROLLED INTRODUCTION
Assignment to TCH Chapter 19: Ladder diagrams
Fail recovered
MA_REQ_FROM_MSC
MA_CMD_TO_MS
MA_FAIL_FROM_MS
ASSIGNMENT FAILURE
19-16 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Intra-cell handover
Intra-cell handover
Figure 19-12 to Figure 19-15 show the ladder diagrams for the intra-cell handover procedure. Intra-cell
handovers deal with channels within the same cell; that is, the Target Cell = Source Cell.
Handover successful
INTRA_CELL_HO (INTRA_CELL_HO_REQ)
(SEE NOTE)
INTRA_CELL_HO (INTRA_CELL_HO_ATMPT)
MA_CMD_TO_MS
MSC
ASSIGNMENT COMPLETE
INTRA_BSS_HO_CAUSE_SUC
INTRA_CELL_HO (INTRA_CELL_HO_SUC)
HANDOVER
PERFORMED
NOTE: Need for handover is recognized within the BSS.
68P02901W56-Q 19-17
24 May 2004 CONTROLLED INTRODUCTION
Intra-cell handover Chapter 19: Ladder diagrams
Handover blocked
INTER_CELL_HO (INTRA_CELL_HO_REQ)
(SEE NOTE)
HO_FAIL_NO_RESOURCES
(INTRA_CELL_HO)
ALLOC_TCH_FAIL
Fail recovered
INTRA_CELL_HO (INTRA_CELL_HO_REQ)
(SEE NOTE 1)
ALLOC_TCH
ASSIGNMENT COMMAND
INTRA_CELL_HO (INTRA_CELL_HO_ATMPT)
MA_CMD_TO_MS
ASSIGNMENT FAILURE
(SEE NOTE 2)
INTRA_FAIL_FROM_MS
INTRA_CELL_HO (INTRA_CELL_HO_FAIL)
NOTES:
1. Need for handover is recognized within the BSS.
2. Failure to access target channel.
19-18 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Intra-cell handover
Fail lost
INTRA_CELL_HO (INTRA_CELL_HO_REQ)
(SEE NOTE 1)
ALLOC_TCH
ASSIGNMENT COMMAND
INTRA_CELL_HO (INTRA_CELL_HO_ATMPT)
MA_CMD_TO_MS
TIMEOUT
MSC
INTRA_CELL_HO (INTRA_CELL_HO_LOSTMS)
CLEAR (SEE NOTE 2)
REQUEST
CLR_REQ_TO_MSC
NOTES:
1. Need for handover is recognized within the BSS.
2. Failure to access target channel and no message receive on source channel prior to timer expiry.
68P02901W56-Q 19-19
24 May 2004 CONTROLLED INTRODUCTION
Inter-BSS handover Chapter 19: Ladder diagrams
Inter-BSS handover
Figure 19-16 to Figure 19-19 show the ladder diagrams for the inter-BSS handover procedure.
Handover successful
HANDOVER IN_INTER_BSS_HO
CLEAR COMPLETE (IN_INTER_BSS_
COMMAND HO_SUC)
OUT_INTER_BSS_HO
(OUT_INTER_BSS
HO_SUC)
OUT_HO_NC_SUC
NOTES:
1. Need for handover is recognized within the BSS.
2. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is
detected that contains a bad handover reference number.
Handover blocked
19-20 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Inter-BSS handover
HANDOVER
REQUIRED HANDOVER
(SEE NOTE 1) REQUEST
ALLOC_TCH_FAIL
OUT_INTER_BSS_HO
(OUT_INTER_BSS_
HO_FAIL_NO_RESOURCES
REQ_TO_MSC) (INTER_BSS_HO)
HANDOVER FAILURE
(SEE NOTE 4)
HO_REQ_MSC_FAIL
HANDOVER (SEE NOTE 3)
REQUIRED
(SEE NOTE 2)
OUT_INTER_BSS_HO
(OUT_INTER_BSS_
REQ_TO_MSC)
NOTES:
1. Need for handover is recognized within the BSS.
2. If a need for handover continues to exist after timer expiry.
3. This pegs due to causes other than resource unavailable.
4. Reference GSM 8.08 Section 3.2.2.5 for valid "handover failure" causes.
68P02901W56-Q 19-21
24 May 2004 CONTROLLED INTRODUCTION
Inter-BSS handover Chapter 19: Ladder diagrams
Fail recovered
HANDOVER REQUIRED
(SEE NOTE 1) HANDOVER
REQUEST
OUT_INTER_BSS_HO ALLOC_TCH
(OUT_INTER_BSS_REQ_ HANDOVER REQUEST or ALLOC_SDCCH
TO_MSC) ACKNOWLEDGE
HANDOVER
COMMAND {4322})
HANDOVER
COMMAND HO_REQ_ACK_TO_MSC
OUT_INTER_BSS_HO (SEE NOTE 2)
(OUT_INTER_BSS_HO_
ATMPT)
OUT_HO_CAUSE_ATMPT
OUT_HO_NC_CAUSE_ATMPT
HANDOVER
FAILURE
OUT_INTER_BSS_HO
(OUT_INTER_BSS_HO_
RETURN)
HANDOVER
FAILURE
HO_REQ_MSC_FAIL
NOTES:
1. Need for handover is recognized within the BSS.
2. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is
detected which contains a bad handover reference number.
19-22 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Inter-BSS handover
Fail lost
HANDOVER
RECOGNIZED
HANDOVER
REQUIRED
HANDOVER
REQUEST
HANDOVER
REQUEST
HANDOVER ACKNOWLEDGE
COMMAND
HANDOVER
COMMAND
(SEE NOTE)
OUT_INTER_BSS_HO
(OUT_INTER_BSS_HO_
LOSTMS)
NOTE:
After the handover command is sent to the MS, any of the following messages may be received
at the source BSS: SCCP_RELEASED, RELEASED_DONE, MTG_EXP, RADIO_CHAN_RLSD.
68P02901W56-Q 19-23
24 May 2004 CONTROLLED INTRODUCTION
Inter-BSS handover Chapter 19: Ladder diagrams
HANDOVER REQUIRED
(SEE NOTE 1) HANDOVER
OUT_INTER_BSS_HO REQUEST
(OUT_INTER_BSS_REQ ALLOC_TCH or
_TO_MSC ALLOC_SDCCH
HANDOVER {4322}
HANDOVER REQUEST HO_REQ_ACK_TO_MSC
COMMAND ACKNOWLEDGE (SEE NOTE 2)
HANDOVER
COMMAND
OUT_INTER_BSS_HO
(OUT_INTER_BSS_HO_
ATMPT)
OUT_HO_CAUSE_ATMPT
OUT_HO_NC_CAUSE_
ATMPT
TIMEOUT
(SEE
NOTE 3)
OUT_HO_INTER_BSS_HO
(OUT_INTER_BSS_LOST
MS)
CLEAR REQUEST
CLR_REQ_TO_MSC
CLEAR
COMMAND
IN_INTER_BSS_HO
CLEAR (IN_INTER_BSS_MS_
COMPLETE NO_SEIZE)
NOTES:
1. Need for handover is recognized within the BSS.
2. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is detected that contains
a bad handover reference number.
3. TIMEOUT can occur at source BSS, target BSS, or switch first depending on system timer settings.
19-24 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Inter-BSS handover
MS MS (TARGET
(SOURCE CHANNEL BSS BSS CHANNEL
SOURCE CELL) (SOURCE) MSC (TARGET) TARGET CELL)
ASSIGNMENT
REQUEST
MA_REQ_FROM_MSC
CALLS_QUEUED
TCH_Q_LENGTH
QUEUEING INDICATION
(SEE NOTE 1)
ASSIGNMENT FAILURE
CAUSE DIRECTED RETRY
(SEE NOTE 2)
HANDOVER
HANDOVER REQUIRED
(SEE NOTE 3)
REQUEST ALLOC_TCH
or ALLOC_SDCCH
HANDOVER REQUEST
ACKNOWLEDGE
{4322}
HANDOVER HO_REQ_ACK_TO_
COMMAND MSC
HANDOVER (SEE NOTE 2)
COMMAND CONGEST_STAND_
HO_ATMPT HANDOVER
OUT_INTER_BSS_HO COMPLETE
(OUT_INTER_BSS_HO_
ATMPT)
IN_INTER_BSS_HO
OUT_HO_CAUSE_ATMPT (SUCCESSFUL)
HANDOVER
(CONGESTION)
COMPLETE
OUT_HO_NC_CAUSE_
ATMPT (CONGESTION)
CLEAR COMMAND
ASSIGNMENT_REDI
RECTION
OUT_INTER_BSS_HO
(OUT_INTER_BSS_
HO_SUC)
OUT_HO_NC_SUC
NOTES:
1. Only if queueing is enabled for the cell
2. The necessity in sending this message must align with MSC expectation and is controlled through the
database. Message may be sent after handover required message as controlled by the database.
3. The cause field in this message (either directed retry or handover cause) must align with MSC
expectation and is controlled through the database.
68P02901W56-Q 19-25
24 May 2004 CONTROLLED INTRODUCTION
Intra-BSS handover Chapter 19: Ladder diagrams
Intra-BSS handover
Figure 19-22 to Figure 19-25 show the ladder diagrams for the intra-BSS handover procedure.
Handover successful
MS MS (TARGET
(SOURCE CHANNEL CHANNEL
BSS
SOURCE CELL) TARGET CELL)
OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_REQ)
(SOURCE CELL) (SEE NOTE 1)
ALLOC_TCH or ALLOC_SDCCH
OUT_INTRA_BSS_HO
HANDOVER (OUT_INTRA_BSS_HO_ATMPT) (SOURCE CELL)
COMMAND
IN_INTRA_BSS_NC_ATMPT (TARGET CELL)
OUT_HO_CAUSE_ATMPT (SOURCE CELL)
HANDOVER COMPLETE
INTRA_BSS_HO_CAUSE_SUC
OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_SUC)
(SOURCE CELL)
OUT_HO_NC_SUC (SOURCE CELL)
IN_INTRA_BSS_HO (TARGET CELL) (SEE NOTE 3)
NOTES:
1. Need for handover is recognized within the BSS.
2. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is
detected that contains a bad handover reference number.
3. Handover performed message sent to MSC by source cell.
Handover- blocked
19-26 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Intra-BSS handover
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_REQ)
(SEE NOTE 1)
ALLOC_TCH_FAIL or ALLOC_SDCCH_FAIL
HO_FAIL_NO_RESOURCES (INTRA_BSS_HO)
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_PRI_BLK)
(SEE NOTE 2)
NOTES:
1. Need for handover is recognized within the BSS, but no radio channel is available in primary target cell.
2. Handover target cell list should contain at least two cells in order to peg this statistic. if there
is only 1 cell, the statistic will not be pegged.
68P02901W56-Q 19-27
24 May 2004 CONTROLLED INTRODUCTION
Intra-BSS handover Chapter 19: Ladder diagrams
Fail-recovered
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_REQ)
(SEE NOTE 1)
ALLOC_TCH or ALLOC_SDCCH
(SEE NOTE 2)
HANDOVER COMMAND
OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_ATMPT)
OUT_HO_CAUSE_ATMPT
OUT_HO_NC_CAUSE_ATMPT
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_RETURN)
(SEE NOTE 3)
NOTES:
1. Need for handover is recognized within the BSS.
2. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom)
is detected that contains a bad handover reference number.
3. Failure to access channel in target cell.
19-28 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Intra-BSS handover
Fail-lost
MSC TIMEOUT
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_LOSTMS)
CLEAR (SEE NOTE 3)
REQUEST
CLR_REQ_TO_MSC
NOTES:
1. Need for handover is recognized within the BSS.
2. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is detected
that contains a bad handover reference number.
3. Failure to access channel in target cell and no message received on channel in source cell
prior to timer expiry.
68P02901W56-Q 19-29
24 May 2004 CONTROLLED INTRODUCTION
Intra-BSS handover Chapter 19: Ladder diagrams
Figure 19-26 displays the ladder diagram for intra-BSS handover standard directed retry.
CALLS_QUEUED
TCH_Q_LENGTH
QUEUEING INDICATION (SEE NOTE 1)
CONGEST_STAND_HO_ATMPT
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_ATMPT)
OUT_HO_CAUSE_ATMPT (CONGESTION)
OUT_HO_NC_CAUSE_ATMPT
(CONGESTION)
ASSIGNMENT FAILURE CAUSE DIRECTED RETRY
(SEE NOTE 2)
INTRA_BSS_HO_CAUSE_SUC
(CONGESTION)
ASSIGNMENT_REDIRECTION
IN_INTRA_BSS_HO
(IN_INTRA_BSS_HO_SUC)
NOTES:
1. Only if queuing is enabled for the cell.
2. The necessity in sending this message must align with MSC expectation and is controlled through the
database. Message may be sent after handover required message as controlled by the database.
3. The cause field in this message (either directed retry or handover cause) must align with MSC
expectation and is controlled through the database.
19-30 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Call clearing
Call clearing
Figure 19-27 to Figure 19-30 show the ladder diagrams for the call clearing procedures.
Figure 19-27 shows BSS initiated call clearing - cipher mode fail.
TIMEOUT
CIPHER_MODE_FAIL
CLEAR REQUEST
CLR_REQ_TO_MSC
68P02901W56-Q 19-31
24 May 2004 CONTROLLED INTRODUCTION
Call clearing Chapter 19: Ladder diagrams
RF loss on an SDCCH
Figure 19-28 shows BSS initiated call clearing (RF loss on an SDCCH).
MS BSS MSC
TIMEOUT RF_LOSSES_SD
CLEAR REQUEST
CLR_REQ_TO_MSC
NOTES:
1. MS has established on SDCCH, for example, after immediate assignment successful.
2. Message sent on SACCH every 480 milliseconds.
19-32 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Call clearing
RF loss on a TCH
MS BSS MSC
MEASUREMENT REPORT (SACCH)
TIMEOUT RF_LOSSES_TCH
CLEAR REQUEST
CLR_REQ_TO_MSC
NOTES:
1. MS has established on TCH, for example, after assignment successful.
2. Message sent on SACCH every 480 milliseconds.
Queueing timeout
68P02901W56-Q 19-33
24 May 2004 CONTROLLED INTRODUCTION
Call clearing Chapter 19: Ladder diagrams
CALLS QUEUED
TIMEOUT
CLEAR REQUEST
CLR_REQ_TO_MSC
19-34 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Short message service
Figure 19-31 and Figure 19-32 show the ladder diagrams for the short message service procedures.
Mobile originated
ACKNOWLEDGEMENT
SMS_INIT_ON_SDCCH
or
SMS_INIT_ON_TCH
NOTES:
1. A SAPI 0 mode must exist before the SAPI 3 can be established.
2. SMS_INIT_ON_SDCCH is pegged if the MS is on an SDCCH
and SMS_INIT_ON_TCH is pegged if the MS is on a TCH.
68P02901W56-Q 19-35
24 May 2004 CONTROLLED INTRODUCTION
Short message service Chapter 19: Ladder diagrams
Mobile terminated
SMS MESSAGE
SAPI 3 REQUEST
ACKNOWLEDGEMENT
SMS_INIT_ON_SDCCH
or
SMS_INIT_ON_TCH
SMS MESSAGE
NOTES:
1. A SAPI 0 mode must exist before the SAPI 3 can be established.
2. SMS_INIT_ON_SDCCH is pegged if the MS is on an SDCCH
and SMS_INIT_ON_TCH is pegged if the MS is on a TCH.
19-36 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Congestion relief
Congestion relief
Figure 19-33 shows the an example of the relationships associated with an intra-BSS congestion
relief handover procedure. In this example, an MS attempts to access a TCH in the cell which is
congested and one (or possibly multiple) MS is handed out to free a TCH.
68P02901W56-Q 19-37
24 May 2004 CONTROLLED INTRODUCTION
Congestion relief Chapter 19: Ladder diagrams
ALLOC_TCH_FAIL
CALLS_QUEUED
ALLOC_TCH
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_ATMPT)
OUT_HO_CAUSE_ATMPT
(CONGESTION)
OUT_HO_NC_CAUSE_ATMPT
(CONGESTION)
CONGEST_EXIST_HO_ATMPT
(SEE NOTE)
HANDOVER COMMAND
HANDOVER COMPLETE
INTRA_BSS_HO_CAUSE_SUC
IN_INTRA_BSS_HO
(IN_INTRA_BSS_HO_SUC)
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_SUC)
ALLOC_TCH
TCH_Q_REMOVED
(assignment_resource_req)
MA_CMD_TO_MS
ASSIGNMENT COMMAND
ASSIGNMENT COMPLETE
MA_COMPLETE_FROM_MS
ASSIGNMENT COMPLETE
MA_COMPLETE_TO_MSC
TOTAL_CALLS
NOTE: Only if queueing is enabled for the cell.
19-38 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Directed retry
Directed retry
Figure 19-34 shows an example of the relationships associated with an intra-BSS directed retry procedure.
68P02901W56-Q 19-39
24 May 2004 CONTROLLED INTRODUCTION
Directed retry Chapter 19: Ladder diagrams
MSC BSS MS
ASSIGNMENT REQUEST
MA_REQ_FROM_MSC
ALLOC_TCH_FAIL
CALLS_QUEUED
ALLOC_TCH
TCH_Q_REMOVED
(assignment_resource_req)
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_ATMPT)
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_ATMPT)
OUT_HO_CAUSE_ATMPT
CONGEST_STAND_HO_ATMPT (SEE NOTE1)
HANDOVER COMMAND
HANDOVER COMPLETE
INTRA_BSS_HO_CAUSE_SUC
IN_INTRA_BSS_HO
(IN_INTRA_BSS_HO_SUC)
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_SUC)
ASSIGNMENT COMPLETE (SEE NOTE 2)
MA_COMPLETE_TO-MSC
ASSIGNMENT_REDIRECTION
(DIRECTED RETRY)
NOTES:
1. Only if queuing is enabled for the cell
2. The database element msc_preference indicates that directed retry procedures
are limited to within the BSS. The BSS sends a Handover Performed message, which
indicates the new cell ID.
19-40 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Flow control
Flow control
FLOW_CONTROL_BARRED measures the duration for which access classes are barred as a result of
flow control. The statistic duration will be started when any of the access classes are barred due to flow
control and stopped when the last access class which was barred due to flow control is unbarred.
Example
Figure 19-35 shows an example of the relationships associated with an access procedure.
DURATION
68P02901W56-Q 19-41
24 May 2004 CONTROLLED INTRODUCTION
Intra-BSS interband activity Chapter 19: Ladder diagrams
Figure 19-36 to Figure 19-38 show intra-BSS interband activity handover ladder diagrams. These diagrams
specifically show the outgoing handover statistics. By only showing outgoing handover statistics, a better
focus is placed on the pegging aspects of INTERBAND_ACTIVITY. For a complete handover statistic
pegging description (outgoing and incoming) refer to the general handover ladder diagrams in this chapter.
Handover successful
Figure 19-36 shows an established call on TCH with a subsequent successful in-
tra-BSS handover to a PGSM cell.
19-42 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Intra-BSS interband activity
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_REQ)
HANDOVER
COMMAND
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_ATMPT)
OUT_HO_CAUSE_ATMPT
OUT_HO_NC_CAUSE_ATMPT
(BAND_HANDOVER) (SEE NOTE 2)
INTERBAND_ACTIVITY
(PGSM_HO_ATMPT) (SEE NOTE 3)
HANDOVER
COMPLETE
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_SUC)
OUT_HO_NC_SUC
NOTES:
1. MS_ACCESS_BY_TYPE will peg the bin that matches the MS capability
2. Handover cause band handover for statistics OUT_HO_CAUSE_ATMPT an OUT_HO_NC_CAUSE_ATMPT
is just one possible valid cause for the intra-BSS handover. Other causes are possible and valid as well (like,
powerbudget, uplink quality, downlink level, etc). Band handover triggered handovers are done to move the
mobile from its current frequency band to a preferred frequency band.
3. For other target cell frequency bands, the appropriate bins for INTERBAND_ACTIVITY will peg. For
example, the above ladder diagram applies for other frequency bands, EXCEPT that
INTERBAND_ACTIVITY will peg different bins:
for GSM850 target cells, bin gsm_850_ho_atmpt pegs
for DCS1800 target cells, bin, dcs_1800_ho_atmpt pegs
for PCS1900 target cells, bin, pcs_1900_ho_atmpt pegs
for EGSM target cells, bin egsm_ho_atmpt pegs
68P02901W56-Q 19-43
24 May 2004 CONTROLLED INTRODUCTION
Intra-BSS interband activity Chapter 19: Ladder diagrams
Figure 19-37 shows an established call on TCH with a subsequent handover attempt to a PGSM cell.
The handover is unsuccessful with MS fail recovered to source cell (original channel).
MS MS (TARGET
(SOURCE CHANNEL CHANNEL
BSS
SOURCE CELL) TARGET CELL)
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_REQ)
HANDOVER
COMMAND
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_ATMPT)
OUT_HO_CAUSE_ATMPT
OUT_HO_NC_CAUSE_ATMPT
(BAND_HANDOVER) (SEE NOTE 2)
INTERBAND_ACTIVITY
(PGSM_HO_ATMPT) (SEE NOTE 3)
HANDOVER
FAILURE
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_RETURN)
INTERBAND_ACTIVITY
(PGSM_HO_FAIL)
NOTES:
1. MS_ACCESS_BY_TYPE will peg the bin that matches the MS capability
2. Handover cause band handover statistics OUT_HO_CAUSE_ATMPT and OUT_HO_NC_CAUSE_ATMPT
is just one possible valid cause for the intra-BSS handover. Other causes are possible and valid as well
(like, powerbudget, uplink quality, downlink level, etc). Band handover triggered handovers are done to
move the mobile from its current frequency band to a preferred frequency band.
3. For other target cell frequency bands, the appropriate bins for INTERBAND_ACTIVITY will peg. For
example, the above ladder diagram applies for other frequency bands, except that INTERBAND_ACTIVITY
will peg different bins:
for GSM850 target cells, bin gsm_850_ho_atmpt & gsm_850_ho_fail peg
for DCS1800 target cells, bins dcs_1800_ho_atmpt & dcs_1800_ho_fail peg
for PCS1900 target cells, bins pcs_1900_ho_atmpt & pcs_1900_ho_fail peg
for EGSM target cells, bins egsm_ho_atmpt & egsm_ho_fail peg
19-44 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Intra-BSS interband activity
Figure 19-38 shows an established call on TCH with subsequent intra-BSS handover attempt
to PGSM cell. The handover is unsuccessful due to invalid frequency supported with MS
fail recovered to source cell (original channel).
MS MS (TARGET
(SOURCE CHANNEL BSS CHANNEL
SOURCE CELL) TARGET CELL)
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_REQ) (SOURCE CELL)
HANDOVER
COMMAND
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_ATMPT)
OUT_HO_CAUSE_ATMPT
OUT_HO_NC_CAUSE_ATMPT
(BAND_HANDOVER) (SEE NOTE 2)
INTERBAND_ACTIVITY
(PGSM_HO_ATMPT)
HANDOVER FAILURE
REASON- FREQUENCY OUT_INTRA_BSS_HO
NOT IMPLEMENTED (OUT_INTRA_BSS_HO_RETURN)
INTERBAND_ACTIVITY
(PGSM_HO_FAIL) (SEE NOTE 3)
INTERBAND_ACTIVITY
(INVALID_FREQ_HO)
NOTES:
1. MS_ACCESS_BY_TYPE will peg the bin that matches the MS capability
2. Handover cause band handover statistics OUT_HO_CAUSE_ATMPT and OUT_HO_NC_CAUSE_ATMPT
is just one possible valid cause for the intra-BSS handover. Other causes are possible and valid as well
(like powerbudget, uplink quality, downlink level, etc). Band handover triggered handovers are done to
move the mobile from its current frequency band to a preferred frequency band.
3. For other target cell frequency bands, the appropriate bins for INTERBAND_ACTIVITY will peg. For
example, the above ladder diagram applies for other frequency bands, except that INTERBAND_ACTIVITY
will peg different bins:
for GSM850 target cells, bin gsm_850_ho_atmpt & gsm_850_ho_fail peg
for DCS1800 target cells, bins dcs_1800_ho_atmpt & dcs_1800_ho_fail peg
for PCS1900 target cells, bins pcs_1900_ho_atmpt & pcs_1900_ho_fail peg
for EGSM target cells, bins egsm_ho_atmpt & egsm_ho_fail peg
68P02901W56-Q 19-45
24 May 2004 CONTROLLED INTRODUCTION
Inter-BSS interband activity Chapter 19: Ladder diagrams
Figure 19-39 to Figure 19-41 show inter-BSS interband activity handover ladder diagrams. These diagrams
specifically show the outgoing handover statistics. By only showing outgoing handover statistics, a better
focus is placed on the pegging aspects of INTERBAND_ACTIVITY. For a complete handover statistic
pegging description (outgoing and incoming) refer to the general handover ladder diagrams in this chapter.
Handover successful
Figure 19-39 shows an established call on TCH with a subsequent successful in-
ter-BSS handover to a PGSM cell.
19-46 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Inter-BSS interband activity
NOTES:
1. Need for handover is recognized within the BSS.
2. MS_ACCESS_BY_TYPE will peg the bin that matches the MS capability; MSC must have
Classmark Update message from the mobile so that the target BSS can peg the MS access
type.
3. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is detected
which contains a band handover reference number.
4. Handover cause band handover for statistics OUT_HO_CAUSE_ATMPT and
OUT_HO_NC_CAUSE_ATMPT is just one possible valid cause for the inter-BSS handover.
Other causes are possible and valid as well (like powerbudget, uplink quality, downlink level,
etc). Band handover triggered handovers are done to move the mobile from its current
frequency band to a preferred frequency band.
5. For other target cell frequency bands, the appropriate bins for INTERBAND_ACTIVITY will
peg. For example, the above ladder diagram applies for other frequency bands, except that
INTERBAND_ACTIVITY will peg different bins:
for GSM850 target cells, bin GSM_850_HO_ATMPT pegs
for DCS1800 target cells, bin DCS_1800_HO_ATMPT pegs
for PCS1900 target cells, bin PCS1900_HO_ATMPT pegs
for EGSM target cells, bin EGSM_HO_ATMPT pegs
68P02901W56-Q 19-47
24 May 2004 CONTROLLED INTRODUCTION
Inter-BSS interband activity Chapter 19: Ladder diagrams
Figure 19-40 shows an established call on TCH with a subsequent inter-BSS handover attempt to a PGSM
cell. The handover is unsuccessful with MS fail recovered to source cell (original channel).
HANDOVER
FAILURE
HO_REQ_MSC_FAIL
NOTES:
1. Need for handover is recognized within the BSS.
2. MS_ACCESS_BY_TYPE will peg the bin that matches the MS capability; MSC must have
Classmark Update message from the mobile so that the target BSS can peg the MS access
type.
3. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is detected
which contains a band handover reference number.
4. Handover cause band handover for statistics OUT_HO_CAUSE_ATMPT and
OUT_HO_NC_CAUSE_ATMPT is just one possible valid cause for the inter-BSS handover.
Other causes are possible and valid as well (like powerbudget, uplink quality, downlink level,
etc). Band handover triggered handovers are done to move the mobile from its current
frequency band to a preferred frequency band.
5. For other target cell frequency bands, the appropriate bins for INTERBAND_ACTIVITY will peg.
For example, the above ladder diagram applies for other frequency bands, except that
INTERBAND_ACTIVITY will peg different bins:
for GSM850 target cells, bin GSM_850_HO_ATMPT and GSM_850_HO_FAIL peg
for DCS1800 target cells, bins DCS_1800_HO_ATMPT and DCS_1800_HO_FAIL peg
for PCS1900 target cells, bins PCS1900_HO_ATMPT and PCS_1900_HO_FAIL peg
for EGSM target cells, bins EGSM_HO_ATMPT and EGSM_HO_FAIL peg
19-48 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Inter-BSS interband activity
Figure 19-41 shows an established call on a TCH with subsequent inter-BSS handover
attempt to a PGSM cell. The handover is unsuccessful due to invalid frequency supported
with MS fail recovered to source cell (original channel).
HANDOVER
FAILURE
REASON-
FREQUENCY
NOT
IMPLEMENTED
NOTES: HO_REQ_MSC_FAIL
1. Need for handover is recognized within the BSS.
2. MS_ACCESS_BY_TYPE will peg the bin that matches the MS capability; MSC must have
Classmark Update message from the mobile so that the target BSS can peg the MS access type.
3. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is detected
which contains a band handover reference number.
4. Handover cause band handover for statistics OUT_HO_CAUSE_ATMPT and
OUT_HO_NC_CAUSE_ATMPT is just one possible valid cause for the inter-BSS handover. Other
causes are possible and valid as well (like powerbudget, uplink quality, downlink level, etc). Band
handover triggered handovers are done to move the mobile from its current frequency band to a
preferred frequency band.
5. For other target cell frequency bands, the appropriate bins for INTERBAND_ACTIVITY will peg.
For example, the above ladder diagram applies for other frequency bands, except that
INTERBAND_ACTIVITY will peg different bins. Examples
for GSM850 target cells, bin GSM_850_HO_ATMPT and GSM_850_HO_FAIL peg
for DCS1800 target cells, bins DCS_1800_HO_ATMPT and DCS_1800_HO_FAIL peg
68P02901W56-Q 19-49
24 May 2004 CONTROLLED INTRODUCTION
Interband assignment Chapter 19: Ladder diagrams
Interband assignment
ASSIGNMENT
REQUEST
MA_REQ_FROM_MSC
ALLOC_TCH
MS_ACCESS_BY_TYPE (SEE NOTE)
ASSIGNMENT
COMMAND
MA_CMD_TO_MS
ASSIGNMENT
FAILURE
REASON-
FREQUENCY NOT
IMPLEMENTED
INTERBAND_ACTIVITY (INVALID_FREQ_ASGN)
MA_FAIL_FROM_MS
ASSIGNMENT FAILURE
REASON-FREQUENCY NOT IMPLEMENTED
19-50 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Band Reassignment
Band Reassignment
Introduction
Figure 19-43 and Figure 19-44 show band reassign ladder diagrams. These diagrams specifically
show the outgoing handover statistics. By only showing outgoing handover statistics, a better
focus is placed on the pegging aspects of the band reassign cause.
Handover successful
Figure 19-43 shows an intra-BSS handover attempt of a MS from an SDCCH in the source
cell (frequency band PGSM) to a TCH in a target cell (frequency band DCS1800). The
MS is a dual mode PGSM/DCS1800 capable mobile.
MS BSS MSC
ASSIGNMENT
REQUEST
MA_REQ_FROM_MSC
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_REQ)
OUT_HO_CAUSE_ATMPT
OUT_HO_NC_CAUSE_ATMPT (BAND_REASSIGN)
INTERBAND_ACTIVITY
HANDOVER
COMPLETE (DCS1800_HO_ATMPT)
(RECEIVED FROM OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_SUC)
TARGET CELL)
OUT_HO_NC_SUC
68P02901W56-Q 19-51
24 May 2004 CONTROLLED INTRODUCTION
Band Reassignment Chapter 19: Ladder diagrams
MS BSS MSC
ASSIGNMENT
REQUEST
MA_REQ_FROM_MSC
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_REQ)
OUT_HO_CAUSE_ATMPT
OUT_HO_NC_CAUSE_ATMPT (BAND_REASSIGN)
INTERBAND_ACTIVITY
HANDOVER
FAILURE (DCS1800_HO_ATMPT)
OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_RETURN)
INTERBAND_ACTIVITY
(DCS1800_HO_FAIL)
19-52 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application RSL link scenarios
Introduction
Figure 19-45 shows a ladder diagram scenario for the Radio Signalling Link (RSL) link.
68P02901W56-Q 19-53
24 May 2004 CONTROLLED INTRODUCTION
RSL link scenarios Chapter 19: Ladder diagrams
STEP 1:
lock of RSL
lock of associated MSI
lock of associated MMS
front panel reset
MSI board physically removed
transmit and or receive path terminated
RSL LINK
SABM_TX (note 1)
unlock of RSL
unlock of associated MSI
unlock of associated MMS
front panel reset
MSI physically returned
transmit and or receive path fully restored
RSL LINK
(RSL restoral)
NOTES :
1. SABM_TX will periodically repeat in attempt to restore the RSL connection.
2. N2_EXPIRY may peg depending on the outage. The period this statistic is
updated is dependent on the RSL attributes lapd_n200 and lapd_t200
timer, which get set during the equip of the RSL.
3. If the last RSL to a site goes OOS, then all call processing at the site will
cease as all cells at the site will be barred.
19-54 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTL link scenarios
Figure 19-46 to Figure 19-49 show four ladder diagrams as scenarios for the Message Transfer Link (MTL) link.
68P02901W56-Q 19-55
24 May 2004 CONTROLLED INTRODUCTION
MTL link scenarios Chapter 19: Ladder diagrams
lock of MTL
lock of associated MSI/XCDR
lock of associated MMS
front panel reset MTL LINK
MSI/XCDR board physically removed
MTP_UNAVAILABLE timer
started
MTP_LINK_INS timer
stopped
STEP 2:
unlock of MTL
unlock of associated MSI/XCDR
unlock of associated MMS
front panel restore
MTL LINK
MSI/XCDR board physically returned
MTP_RESTORATION
incremented
MTP_UNAVAILABLE
timer stopped
MTP_LINK_INS timer
started
NOTES:
1. Lock of MTL or associated device transitions operator and admin states from
B-U to D-L
2. Unlock of MTL or associated device transitions operator and admin states from
D-L to B-U.
Lock of MTL or associated device transitions operator and admin states from B-U to D-L
Unlock of MTL or associated device transitions operator and admin states from D-L to B-U.NOTE
19-56 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTL link scenarios
Figure 19-47 shows an MTL transition from B-U to E-U and E-U to B-U with reason Wait.
MTL LINK
MTP_SL_FAIL incremented
MTP_UNAVAILABLE
timer started
MTP_LINK_INS timer
stopped
MTP_LINKFAIL timer
started
MTP_LINK_INS timer
stopped
MTP_SL_ALIGNMENT
incremented
STEP 2:
(MTL transitions from E-U with
reason Wait to B-U
MTL LINK
MTP_RESTORATION
incremented
MTP_LINKFAIL
timer stopped
MTP_UNAVAILABLE
timer stopped
MTP_LINK_INS timer
started
68P02901W56-Q 19-57
24 May 2004 CONTROLLED INTRODUCTION
MTL link scenarios Chapter 19: Ladder diagrams
Figure 19-48 shows an MTL transition from B-U to D-U and D-U to B-U with reason Wait MMS not in service.
MTL LINK
MTP_SL_FAIL incremented
MTP_UNAVAILABLE
timer started
MTP_LINKFAIL timer
started
MTP_LNK_INS timer
started
STEP 2:
(MTL transitions from D-U with reason Wait MMS not in service
MTL LINK
MTP_RESTORATION
incremented
MTP_LINKFAIL
timer stopped
MTP_UNAVAILABLE
timer stopped
MTP_LINK_INS timer
started
19-58 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application MTL link scenarios
Figure 19-49 shows an MTL transition from B-U to E-U and E-U to B-U with reason Wait
improper timeslot mapping between BSC and MSC.
MTL LINK
MTP_SL_FAIL incremented
MTP_UNAVAILABLE
timer started
MTP_LINKFAIL timer
started
MTP_LNK_INS timer
started
MTP_LINK_INS timer
stopped
MTP_SL_ERROR_RATE
incremented
MTP_SL_ALIGNMENT incremented
(periodically repeats)
STEP 2:
(MTL transitions from E-U with reason Wait to B-U with improper
timeslot mapping between BSC and MSC
MTL LINK
MTP_RESTORATION
incremented
MTP_LINKFAIL
timer stopped
MTP_UNAVAILABLE
timer stopped
MTP_LINK_INS timer
started
68P02901W56-Q 19-59
24 May 2004 CONTROLLED INTRODUCTION
GBL statistics Chapter 19: Ladder diagrams
GBL statistics
Figure 19-50 to Figure 19-54 show how the GBL statistics function within the BSS/PCU.
GBL_DL_DATA_THRPUT
Figure 19-50 shows GBL_DL_DATA_THRPUT.
DLCI = 45 DLCI = 45
DLCI = 55
Bearer chan 1
DLCI = 55
19-60 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GBL statistics
GBL_FLOW_CTRL_SENT
Figure 19-51 is a ladder diagram detailing the statistic GBL_FLOW_CTRL_SENT when it is pegged.
It also shows the request and the response messages sent from the BSS/PCU to the SGSN.
BSS/PCU SGSN
GBL_FLOW_CTRL_SENT
CELL_FLUSH_REQS
Figure 19-52 illustrates the statistic CELL_FLUSH_REQS when it is pegged. It also shows
the request and the response sent from the SGSN to the PS.
SGSN GB FU PS
CELL_FLUSH_REQS
68P02901W56-Q 19-61
24 May 2004 CONTROLLED INTRODUCTION
GBL statistics Chapter 19: Ladder diagrams
GBL_PAGING_REQS
Figure 19-53 is a ladder diagram detailing the statistic GBL_PAGING_REQS when it is pegged. It also
shows the request and the response messages sent from the SGSN to the BSS/PCU and the MS.
SGSN BSS/PCU
MS
BSSGP PS PDU
GBL_PAGING_REQS
19-62 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application GBL statistics
GBL_UL_DATA_THRPUT
Figure 19-54 illustrates the statistic GBL_UL_DATA_THRPUT.
DLCI = 45 DLCI = 45
Bearer chan 1
DLCI = 55 DLCI = 55
68P02901W56-Q 19-63
24 May 2004 CONTROLLED INTRODUCTION
Accessibility statistics Chapter 19: Ladder diagrams
Accessibility statistics
CHANNEL_REQ_REJ
Figure 19-55 is a ladder diagram detailing the statistic CHANNEL_REQ_REJ when it is pegged. It also
shows the request and the response messages sent from the BSS/PCU to the mobile station.
BSS/PCU MS
CHANNEL_REQ_REJ
19-64 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Accessibility statistics
BSS/PCU MS
GPRS_ACCESS_PER_RACH
GPRS_ACCESS_PER_AGCH
68P02901W56-Q 19-65
24 May 2004 CONTROLLED INTRODUCTION
Accessibility statistics Chapter 19: Ladder diagrams
SGSN BSS/PCU MS
BSSGP PS PDU
GBL_PAGING_REQS
GPRS_ACCESS_PER_RACH
GPRS_ACCESS_PER_AGCH
19-66 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Accessibility statistics
MS class types are valid for GSR7 release only. They are not valid for EGPRS.
Figure 19-58 is a ladder diagram detailing three MS class type statistics and when pegging occurs. It also
shows the request and response messages sent from the BSS/PCU to the mobile station.
BSS/PCU MS
MS_CLASS_1_10_REQ
MS_CLASS_11_20_REQ
MS_CLASS_21_29_REQ
CHANNEL_REQ_REC
68P02901W56-Q 19-67
24 May 2004 CONTROLLED INTRODUCTION
Accessibility statistics Chapter 19: Ladder diagrams
GPRS_CHANNELS_SWITCHED
Figure 19-59 details the GPRS_CHANNELS_SWITCHED statistic.
19-68 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Throughput statistics
Throughput statistics
68P02901W56-Q 19-69
24 May 2004 CONTROLLED INTRODUCTION
Throughput statistics Chapter 19: Ladder diagrams
AIR_UL_DATA_BLKS
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Figure 19-60 is a ladder diagram detailing the statistic AIR_UL_DATA_BLKS and when pegging occurs.
It also shows the request and response messages sent from the BSS/PCU to the MS.
BSS/PCU MS
DATA BLOCK
AIR_UL_DATA_BLKS
19-70 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Throughput statistics
AIR_DL_DATA_BLKS
This statistic applies to GSR7 release only. It is not valid for EGPRS.
Figure 19-61 is a ladder diagram detailing the statistic AIR_DL_DATA_BLKS and when pegging occurs.
It also shows the request and response messages sent from the BSS/PCU to the MS.
BSS/PCU MS
DATA BLOCK
AIR_DL_DATA_BLKS
68P02901W56-Q 19-71
24 May 2004 CONTROLLED INTRODUCTION
Throughput statistics Chapter 19: Ladder diagrams
19-72 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Chapter
20
Impacts on statistics
The collection, interpretation and accuracy of GSM statistics may be affected by a number of factors,
for example, new software and hardware features. Although not all of the factors are directly
related to statistics, they all have a definite impact on them. The factors described here are listed
below. Also provided is a list of frequently asked questions with answers.
• "Extended GSM (EGSM)" on page 20-2.
68P02901W56-Q 20-1
24 May 2004 CONTROLLED INTRODUCTION
Extended GSM (EGSM) Chapter 20: Impacts on statistics
Overview of EGSM
EGSM900 (Extended GSM) provides the BSS with a further range of frequencies for MS and BSS transmit.
EGSM MSs can use the extended frequency band as well as the primary band, while non-EGSM MSs cannot
use the extended frequency band. A GSM900 cell can contain both GSM900 and EGSM900 carrier hardware.
Requirements
Although EGSM provides additional frequencies for use, several functions must remain in the original
GSM900 band. Functions that must be performed in the GSM900 band are:
• BCCH carrier frequency.
• SDCCH configuration.
Channel allocation
Channel allocation for an EGSM MS proceeds in a way such that the search is between extended then
primary band frequencies, starting from best to worst interference bands until a channel is found.
Forced handovers
To avoid blocking of non-EGSM MSs, an extended band MS using a primary resource can be forced to handover
to an idle extended band resource with an interference band residing above or meeting a specified threshold.
The database parameter egsm_handover_threshold indicates the range of interference bands allowed
for handing over an extended MS using a primary resource that is needed by a non-EGSM MS. Allowed
interference bands are those above or meeting a specified threshold, which are considered quality resources.
The operator also has the option to disallow forced handovers by disabling the egsm_handover_threshold flag.
The following examples illustrate the impact of the EGSM feature on statistics:
20-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Extended GSM (EGSM)
It is more difficult for non-EGSM MSs to access a TCH since EGSM MSs are occupying the primary resources.
The statistics impacted are shown in Table 20-1.
Statistic Value
MA_CMD_TO_MS_BLKD will be higher
MA_COMPLETE_TO_MSC will be lower
BUSY_TCH max/mean value will be lower
TOTAL_CALLS will be lower
TCH_CONGESTION will be lower (See note)
TCH_USAGE will be lower
TCH_DELAY will be higher
TCH_CONGESTION is lower because it is pegged when all TCHs are busy, not just the primary
band TCHs, even though congestion exists for the primary MSs in this example.
More intra-cell handovers are attempted to move the EGSM MSs off of primary resources
to open up primary resources for non-EGSM MSs.
The statistics impacted are shown in Table 20-2.
68P02901W56-Q 20-3
24 May 2004 CONTROLLED INTRODUCTION
Extended GSM (EGSM) Chapter 20: Impacts on statistics
Statistic Value
INTRA_CELL_HO will be higher
INTRA_CELL_HO_REQ will be higher
INTRA_CELL_HO_LOSTMS will be higher
INTRA_CELL_HO_ATMPT will be higher
INTRA_CELL_HO_FAIL will be higher
MA_CMD_TO_MS will be higher
MA_FAIL_TO_MS will be higher
BAD_HO_REFNUM_MS will be higher
CLR_REQ_TO_MSC will be higher
ALLOC_SDCCH_FAIL will be higher
The cell experiences congestion when other non-EGSM MSs try to access the cell, despite
the fact that not all of the resources have been allocated.
The statistics impacted are shown Table 20-3.
Statistic Value
MA_CMD_TO_MS_BLKD will be higher
MA_COMPLETE_TO_MSC will be lower
BUSY_TCH max/mean value will be lower
TOTAL_CALLS will be lower
TCH_CONGESTION will be lower (See note)
TCH_USAGE will be lower
TCH_DELAY will be higher
TCH_CONGESTION is lower because it is pegged when all TCHs are busy, not just the primary
band TCHs, even though congestion exists for the primary MSs in this example.
20-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Approximate equality
Approximate equality
Statistics are kept by processes at the BTS and BSC. When comparing statistics, minor discrepancies
between different statistics may occur because when the statistic interval expires, a procedure may
be in progress and not all statistics related to that procedure have been pegged. These statistics
are pegged in the following interval upon completion of the procedure.
Example
Figure 20-1 is an example of approximate equality.
MA_REQ_FROM_MSC
MA_CMD_TO_MS
MA_COMPLETE_TO_MSC
TOTAL_CALLS
Although the procedure TCH assignment was successful, the statistics file for the 9:00 to
9:30 interval shows the statistic MA_REQ_FROM_MSC incremented with no corresponding
MA_CMD_TO_MS and TOTAL_CALLS values. Also, the 9:30 to 10:00 interval shows the
statistics MA_CMD_TO_MS, TOTAL_CALLS, and MA_COMPLETE_TO_MSC incremented
with no corresponding MA_REQ_FROM_MSC value.
68P02901W56-Q 20-5
24 May 2004 CONTROLLED INTRODUCTION
Phantom RACHs Chapter 20: Impacts on statistics
Phantom RACHs
Phantom RACHs occur primarily as the result of sporadic noise and interference. Channel requests from
distant MSs can be affected by such noise when MS power output is low. If an MS output is high, any
transmitted signals can cause interference to other co-channel and adjacent channel cells. It is unlikely
in a Motorola implementation that cells using similar frequencies will be finely synchronized. This
could happen by chance as each BTS does not have frame synchronization. It is possible though for
partial synchronization to occur and contribute to the phantom RACH problem.
CHANNEL REQUEST
(INV_EST_CAUSE_ON_RACH
CHANNEL REQUEST
ALLOC_SDCCH
(CHAN_REQ_MS_FAIL)
20-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Phantom RACHs
The following process describes the chain of events that take place when a phantom RACH occurs:
1. The channel coder decodes the message on the Random Access Channel from the radio.
If the channel coder cannot decode the message because a field is unrecognizable, the
channel coder pegs an internal counter for the unrecognized message.
If the channel coder decodes the message, the channel coder forwards the channel request to
RSS Layer 1 and included in the message is the peg count of unrecognized messages.
2. RSS layer 1 pegs the OK_ACC_PROC_SUC_RACH statistic once for the channel request
and pegs the ACCESS_PER_RACH statistic once for the channel request plus the peg
count sent by the Channel Coder. RSS layer 1 does no filtering of the RACH.
3. RSS Abis receives the channel request and verifies the one-byte message from the MS.
It verifies that the three most significant bits represent a valid establishment cause (see
GSM4.08, 3.11.0, section 9.1.8 for the valid causes for Phase 1). If the three bits are
verified, the RSS Abis sends a channel request to Call Processing. If the three bits are not
valid, the RSS Abis pegs the INV_EST_CAUSE_ON_RACH statistic.
The other five bits of the eight-bit message are an unformatted five-bit
field, which cannot be verified.
At RSS Abis.
68P02901W56-Q 20-7
24 May 2004 CONTROLLED INTRODUCTION
Phantom RACHs Chapter 20: Impacts on statistics
• ACCESS_PER_AGCH.
• ALLOC_SDCCH.
• ALLOC_SDCCH_FAIL.
• OK_ACC_PROC_SUC_RACH.
• CHAN_REQ_MS_BLK.
• CHAN_REQ_MS_FAIL.
• SDCCH_CONGESTION.
• BUSY_SDCCH.
ACCESS_PER_RACH is pegged for each phantom RACH. The remainder of the above statistics are
affected depending on whether or not the apparent channel request from the MS is known to Call Processing
(Layer 3). RSS (Layer 2) filters out RACHs that are invalid. Specifically, Channel Request messages
received via the RACH that have invalid (reserved) values in the establishment cause field (reference
GSM 04.08) are filtered by the RSS. Therefore, a lot of phantom RACHs never make it up to the Call
Processing processes because of the gating (filtering) function performed by the RSS.
20-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Questions and answers
Assignment failure
• ALLOC_SDCCH_FAIL.
• BUSY_SDCCH.
• BUSY_TCH.
• RF_LOSSES_SD.
• RF_LOSSES_TCH.
• SDCCH_CONGESTION.
• TCH_CONGESTION.
• TCH_USAGE.
A: For example, SDCCH congestion timer gets started when there are no free SDCCHs available at
the cell. If a TCH gets reconfigured to eight SDCCHs, the congestion timer stops because the cell is
no longer congested as far as SDCCHs are concerned. The statistics reflect the current status of the
system. The reconfiguration issue should not affect the accuracy of the statistics.
68P02901W56-Q 20-9
24 May 2004 CONTROLLED INTRODUCTION
Questions and answers Chapter 20: Impacts on statistics
Q: If configuration of SDCCHs, for example, can occur manually or more importantly occur
dynamically during a busy period, would the previous peg information for that half hour
period be lost, and would this affect key statistic results?
A: No, CHAN_REQ_MS_FAIL (the statistic which is pegged per channel) is not deleted when the channel is
configured or reconfigured. The process pegging creates the statistic for all possible SDs. This statistic is never
deleted, so that the statistic for each half hour shows the amount of pegs for the channel for the entire half hour.
Q: Is failed handover and RF_LOSSES_TCH the only possible reason for losing an established call?
A: A call could also be lost because of other procedure failures, like ciphering and Mode Modify.
Phantom RACHs
Q: How can it be determined how many phantom RACHs have been assigned to an SDCCH?
A: CHAN_REQ_MS_FAIL pegs due to timeout, if the MS is out of range or switched off.
After the SDCCH is allocated, an attempt is made to communicate with the MS, and it will
not respond (because it never existed to begin with).
Q: Does updated BTS hardware have any effect on Phantom RACHs?
A: ACCESS_PER_RACH counts reduce considerably between BTS5s and BTS4Ds
(3000 > 300), which have full diversity.
Q: What happens after a SDCCH has been seized by a phantom RACH? Will CLR_REQ_TO_MSC,
CHAN_REQ_MS_FAIL and RF_LOSSES_SD be pegged?
A: Only CHAN_REQ_MS_FAIL is pegged. CLR_REQ_TO_MSC and RF_LOSSES_SD
is not pegged for phantom RACHs.
20-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Index
Index
68P02901W56-Q IX-1
24 May 2004 CONTROLLED INTRODUCTION
Index
IX-2 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Index
68P02901W56-Q IX-3
24 May 2004 CONTROLLED INTRODUCTION
Index
IX-4 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Index
68P02901W56-Q IX-5
24 May 2004 CONTROLLED INTRODUCTION
Index
IX-6 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Index
68P02901W56-Q IX-7
24 May 2004 CONTROLLED INTRODUCTION
Index
IX-8 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Index
68P02901W56-Q IX-9
24 May 2004 CONTROLLED INTRODUCTION
Index
IX-10 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Index
68P02901W56-Q IX-11
24 May 2004 CONTROLLED INTRODUCTION
Index
IX-12 68P02901W56-Q
CONTROLLED INTRODUCTION 24 May 2004
Maintenance Information: GSM Statistics Application Index
68P02901W56-Q IX-13
24 May 2004 CONTROLLED INTRODUCTION