2g counters

BSS counter name

1029 TCH_TR_FAIL

1084 TCH_ABIS_FAIL_CALL

1000 SDCCH_SEIZ_ATT

1001 SDCCH_BUSY_ATT

1003 SDDCH_RADIO_FAIL

1004 SDCCH_RF_OLD_HO

1007 SDCCH_ASSIGN

1010 TCH_REQUEST

1011 TCH_REQ_REJ_LACK

Counter number

1013 TCH_RADIO_FAIL

1014 TCH_RF_OLD_HO

1030 TCH_TR_FAIL_OLD

1035 SDCCH_LAPD_FAIL

1036 SDCCH_BTS_FAIL

1037 SDCCH_USER_ACT

1038 SDCCH_BCSU_RESET

1039 SDCCH_NETW_ACT

1044 TCH_FAST_SEIZ

1046 TCH_LAPD_FAIL

1047 TCH_BTS_FAIL

1048 TCH_USER_ACT

1049 TCH_BCSU_RESET

1050 TCH_NETW_ACT

1076 SDCCH_ABIS_FAIL_OLD

1081 TCH_ACT_FAIL_CALL

1085 TCH_ABIS_FAIL_OLD

1192 TCH_REQUESTS_CALL_ATTEMPT

1193 SUCC_TCH_SEIZ_CALL_ATTEMPT

1099 TCH_SEIZ_DUE_SDCCH_CON

1122 TCH_REJ_DUE_REQ_CH_A_IF_CRC

1165 TCH_SUCC_SEIZ_FOR_DIR_ACC

1192 TCH_REQUESTS_CALL_ATTEMPT

1193 SUCC_TCH_SEIZ_CALL_ATTEMPT

1195 MSC_O_HO_CMD

1196 BSC_O_HO_CMD_ASSGN

1197 BTS_HO_ASSGN

1205 TCH_REL_DUE_RAD_FAIL_PH_2_3

2027 AVE_BUSY_TCH

2028 RES_AV_DENOM14

2034 AVE_SDCCH_HOLD_TIM

2034 AVE_SDCCH_HOLD_TIM

2036 AVE_FTCH_HOLD_TIM

2059 AVE_AVAIL_TCH_SUM

2060 AVE_AVAIL_TCH_DEN

2061 AVE_GPRS_CHANNELS_SUM

2062 AVE_GPRS_CHANNELS_DEN

2069 AVE_NON_AVAIL_TCH_TIMESLOT

2070 NON_AVAIL_TCH_DENOM

3001 IMM_ASSGN_SENT

3002 IMM_ASSGN_REJ

3005 DEL_IND_MSG_REC

3012 SUCC_SEIZ_TERM

3013 SUCC_SEIZ_ORI

3020 SDCCH_CALL_RE_EST

3021 SDCCH_EMERG_CALL

3028 SUCC_SDCCH_SMS_EST

3029 UNSUCC_SDCCH_SMS_EST

3044 SUCC_SEIZ_SUPPLEM_SERV

3059 CALL_ASSIGN_AFTER_SMS

4004 MSC_O_SUCC_HO

4014 BSC_O_SUCC_HO

4018 CELL_SUCC_HO

4023 HO CAUSE_UP_QUAL4024 HO CAUSE_UP_LEVEL4025 HO CAUSE_DOWN_QUAL4026 HO CAUSE_DOWN_LEV4027 HO CAUSE_DISTANCE4029 HO CAUSE_INTFER_UP4030 HO CAUSE_INTFER_DWN4031 HO CAUSE_UMBR4032 HO CAUSE_PBDG

4043 MSC_I_TCH_TCH

4044 MSC_I_SDCCH_TCH

4050 MSC_O_SDCCH_TCH

4056 BSC_I_TCH_TCH

4057 BSC_I_SDCCH_TCH

4065 BSC_O_SDCCH_TCH

4074 CELL_SDCCH_TCH

4084 BSC_O_DROP_CALLS

4085 CELL_DROP_CALLS

4107 MSC_O_CALL_DROP_HO

4149 MSC_HO_WCDMA_RAN_SUCC

4154 MSC_GEN_SYS_WCDMA_RAN_HO_COM

4157 MSC_CALL_DROP_HO_WCDMA_RAN

4158 MSC_TO_WCDMA_RAN_SUCC_TCH_HO

57018 SERVED_FACCH_REQ

57020 T3101_EXPIRED

57021 SDCCH_ASSIGN

57028 TCH_CALL_REQ

57033 TCH_NEW_CALL_ASSIGN

57035 TCH_NORM_RELEASE

72000 NBR_OF_UL_TBF

72005 NBR_OF_DL_TBF

72056 UL_TBF_REL_DUE_NO_RESP_MS

72057 DL_TBF_REL_DUE_NO_RESP_MS

72062 RLC_DATA_BLOCKS_DL_CS1

72063 RLC_DATA_BLOCKS_DL_CS2

72064 RLC_DATA_BLOCKS_UL_CS1



72082 PACKET_CH_REQ

72092 UL_TBF_ESTABLISHMENT_FAILED

72093 DL_TBF_ESTABLISHMENT_FAILED

72094

72095 DL_EGPRS_TBF_RELEASE_DUE_NO_RESP

72100 AVER_TBFS_PER_TSL_UL_DEN

72102 AVER_TBFS_PER_TSL_DL_DEN

72121 UL_TBF_ESTABL_STARTED

72171 AVE_UL_TBF_PER_USED_TSL

72172 AVE_DL_TBF_PER_USED_TSL

79000 DL_RLC_BLOCKS_IN_ACK_MODE

79001 DL_RLC_BLOCKS_IN_UNACK_MODE

79002 UL_RLC_BLOCKS_IN_ACK_MODE

UL EGPRS_TBF_RELEASE_DUE_NO_RESPONSE_FROM_MS

79002 UL_RLC_BLOCKS_IN_ACK_MODE

79003 UL_RLC_BLOCKS_IN_UNACK_MODE

105010 DTM_DURATION_SUM_HR

105011 DTM_DURATION_SUM_FR

- SPARE001229

Description

Number of TCH transactions that are ended because of a transcoder failure. Counter is updated when a TCH transaction ends because of a transcoder failure during a call attempt. These failures can also contain situations when the timer T3109 expires in a BSC in call release phase while waiting for the Release Indication. The MS subscriber does not see these failures caused by the T3109 expiry as real dropcalls.Number of TCH transactions ended because of a failure in the Abis interface during a call in progress. The signalling problems might include missing acknowledgement of channel activation, missing indication of call establishment, receipt of an error indication, corrupted messages, missing measurement results from the BTS, excessive timing advance or some internal reasons. These failures can also contain situations when the timer T3109 expires in a BSC in call release phase while waiting for the Release Indication. The MS subscriber does not see these failures caused by the T3109 expiry as real drop callsNumber of times when an MS attempts to seize an SDCCH. Updated when the RRM receives requests for SDCCH from an MS as the MS needs a channel for either a call or a hondoverNumber of times when an MS attempts to seize an SDCCH but the attempt is unsuccessful because all SDCCHs are busy. This counter does not necessarily mean that the call attempt is lost, because the call might be established as an FACCH call setup using TCH instead of SDCCH. This counter is not triggered when the TCH reconfiguration is attempted because of dynamic SDCCH allocation. If the attempt fails, the SDCCH_BUSY_ATTEMPT is triggered together with 1155 UNSUCC_IMM_ASS_SDCCH_ATTEMPT. Counter is updated when the RRM has no SDCCHs to allocate for a call or handover attemptsNumber of SDCCH transactions ended because of a radio failure. When the SDCCH transaction ends because of a radio failure (radio link timeout) the RRM releases the SDCCH. This counter is updated in call phases 1-8 onlyNumber of SDCCH transactions ended because of a radio failure on the source channel during a handover between SDCCH-SDCCH or SDCCH-TCH. This counter is updated in the source cell. If the target cell lies within the same BSC, also counter 001005 in the target cell is updated along with this counter. The counter is updated when an SDCCH transaction ends because of a radio failure (handover failure) on the source channel during a handover attempt and after releasing the SDCCH by RRM. This counter is updated only in call phases 9-11.Number of successful seizures of SDCCH for an immediate assignment. Updated when the RRM allocates an SDCCH for an immediate assignment in a call attempt.Total number of requests for a TCH (successful and unsuccessful). Takes into account incoming HO from 3G. When the RRM receives a request for a TCH either in a call or a handover attempt.Number of requests for TCHs that are rejected because there are no radio resources available for either call or handover attempts. This counter is also updated when a request for TCH is rejected because of a mismatch between the types of the requested channel and the A interface circuit. Updated when the RRM has no TCHs available for either call or HO attempt requests, or the RRM changes the A interface circuit pool before the TCH allocation. This counter might be updated immediately after a TCH request or, in case of queuing, when the queuing timer expires.

timer T200 has expired N200 +1 times (MS does not respond any more),

Number of TCH transactions ended because of a BCSU restart.

Number of TCH transactions ended because of a radio failure. The RRM releases the TCH when a TCH transaction ends because of a radio failure. This counter is typical in connection with coverage problems. ERROR INDICATION is sent by the BTS to the BSC in the following cases:

sequence error in a received message (the case where retransmission is not possible),

unsolicited DM response when link is established. This counter is updated in call phases 1-8 or 15 only.

during a handover attempt. When a TCH transaction ends because of a radio failure (handover failure) on the source channel during a handover attempt to counter is Number of TCH transactions ended because of a transcoder failure on the source channel during a handover on a TCH. When a TCH transaction ends because of a transcoder failure on the source channel during a handover attempt and the RRM releases the TCH the counter is updated. This happens before the RRM receives a message from the MS stating the handover or the assignment is completed. This counter is updated only in call phases 9 to 11.Number of SDCCH transactions ended because of the LAPD failure. When an SDCCH transaction ends because of a TRX blocked by an LAPD failure, the RRM releases the SDCCH.Number of SDCCH transactions ended because of the BTS failure. The SDCCH is released when an SDCCH transaction ends because of a TRX being blocked by a BTS failure.Number of SDCCH transactions ended because of user actions. When the user disconnects a busy SDCCH by blocking the TSL/TRX with an MML command the transaction ends and the SDCCH is released.Number of SDCCH transactions ended because of a BCSU restart. The BCSU restarts trigger the SDCCH release. When an SDCCH transaction ends because of a TRX blocked by a BCSU restart the the SDCCH is released by RRMNumber of SDCCH transactions ended because of the radio network reconfiguration. The SDCCH transaction ends because of a TRX blocked by a failure which leads to TRX reconfiguration. The failure might occur both during call and handover attempts.Number of successful seizures of TCHs in FACCH call setup. When the RRM allocates a TCH as a response to an SDCCH request as part of the FACCH call setup because of no SDCCHs being idle the counter is updated.Number of TCH transactions ended because of an LAPD failure. When a TCH transaction ends because of a TRX blocked by an LAPD failure and the RRM releases the TCH the counter is updated.Number of TCH transactions ended because of a BTS failure. Counter update is done after the RRM releases the TCH because of the BTS failure.Number of TCH transactions ended because of user actions. Counter update is done a after the user disconnection form the busy TCH by blocking the TSL/TRX with an MML command. The transaction ends and the TCH is released.

Number of TCH transactions ended because of the radio network reconfiguration. Counter is updated when a TCH transaction ends because of a TRX blocked by a failure which leads to TRX reconfiguration.

Number of handover commands sent by the BSC in an outgoing MSC-controlled handover.

Number of all handover commands sent by the BSC in an outgoing BSC-controlled handover.

Number of assignment commands sent in intra-BTS handovers.

Number of SDCCH transactions ended because of a failure in the Abis interface on the source channel during SDCCH-SDCCH or SDCCH-TCH handover. The SDCCH is released by RRM when SDCCH transaction ends because of a failure in the Abis interface on the source channel during a handover and. This counter is updated only in call phases 9-11.Number of TCH transactions ended because of channel activation failure during a call attempt. After the TCH transaction ends because of the channel activation failure in the BTS the RRM releases the TCH. This counter is updated only in call phases 1 to 8.Number of TCH transactions ended because of a failure in the Abis interface on the source channel during a TCH handover. When a TCH transaction ends because of a failure in the Abis interface on the source channel during a TCH handover the RRM releases the TCH, then counter is updated. This counter is updated only in call phases 9 to 11.Number of TCH channel requests for a call. Updated while a TCH is requested for a call. The counter is updated only once for every call attempt.Number of successful TCH channel seizures for a call. Updated when a TCH is successfully allocated for a call. The counter is updated only once for every call attempt.Number of successful TCH seizures because of congestion on the SDCCH. The RRM allocates a TCH as a response to a request for SDCCH seizure during congestion on the SDCCHs and then the counter is updated.Number of requests for TCHs that are rejected because of a mismatch between the types of the requested channel and the A interface circuit, whether queuing occurred or not. When the RRM changes the A interface circuit pool before TCH allocation.Number of successful seizures for a TCH in direct accesses to a super-reuse TRX during the call setup phase. When the RRM allocates a TCH as a response to a TCH request in a call attempt using direct access to a super-reuse TRX procedure the counter is updated.Number of TCH channel requests for a call. Updated when a TCH is requested for a call. The counter is updated only once for every call attempt. If the seizure of TCH is successful, the counter is updated to the BTS from which the TCH was successfully seizured. In case the seizure is unsuccessful, the counter is updated to the BCCH BTS.Number of succesful TCH channel seizures for a call. The counter is updated only once for every call attempt and it is not updated for TCH-TCH handover attempts.

Number of the TCH releases because of the radio failures. Counter 001139 is updated together with this counter. When the TCH is released in call phase 2 (MM signalling) or 3 (Basic assignment) because of a radio failure counter is updated.value of this counter by the value of counter 002028 RES AVAIL DENOMINATOR 14. The 002028 counter is updated along with this counter. The number of busy TCH timeslots is sampled every 20 seconds. When HR capable timeslot has both channels occupied the number of busy TCHs is updated for both TCHs individually.Number of samples of busy TCH timeslots. Denominator of counter 002027 AVE BUSY TCH is always bigger than 0. The 002027 counter is updated along with this counter. The counter is incremented every 20 seconds when sample of number of busy TCH timeslots is taken.Average time that SDCCHs are busy. The average value is calculated by dividing the value of this counter by the value of the next counter. The measurement period starts

No free SDCCH.Abis interface process has no internal resources to handle the request.

Number of DELETE_INDICATION messages received from the BTS.

value of this counter by the value of the next counter. The measurement period starts when an SDCCH is allocated and ends when the SDCCH is released and marked free.Length of the reservation summed up into the counter at the release of TCH. Unit of the counter is 10 ms.Average number of available TCHs. The average value is calculated by dividing the value of this counter by the value of the next counter. Counter 002060 is updated along with this counter. The counter is sampled every 20 seconds.Denominator of the average number of available TCHs.The value is always bigger than 0. Counter 002059 is updated along with this counter.Average number of radio time slots delivered for GPRS use. The average value is calculated by dividing the value of this counter by the value of the next counter. The counter value does not indicate how many time slots has actually been used for GPRS traffic. Counter 002062 is updated along with this counter. Counter is updated when the GPRS territory of the BTS is upgraded or downgraded. The counter is sampled every 20 seconds.Denominator of the average number of GPRS channels. The value is always bigger than 0. Counter 002061 is updated along with this counter.Average number of the TCH timeslots not available. Counter is updated when TCH timeslot is not available, it is sampled every 20 seconds.Denominator of the average number of the TCHs timeslots not available. The value is always bigger than 0. The counter is increased by every 20 seconds.

Number of IMMEDIATE_ASSIGN_COMMAND messages sent to the BTS. Counted when the IMMEDIATE_ASSIGN_COMMAND message is sent to the BTS.

Number of IMMEDIATE_ASSIGNMENT_REJECT messages sent to the BTS. This counter is updated when an IMMEDIATE_ASSIGNMENT_REJECT message is packed and sent to the BTS. The message can include one to four immediate assignment rejects. The IMMEDIATE_ASSIGNMENT_REJECT message is sent to MS in the following cases:

BTS sends the DELETE INDICATION message each time when IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT REJECT message is lost, for example due to BTS buffer overflown. Counter is updated when the DELETE_INDICATION message is received from the BTS.Number of successful seizures of SDCCHs for an MTC. When an ESTABLISH_INDICATION message with paging response is received on SDCCH from the BTS.Number of successful seizures for SDCCH for an MOC. When an ESTABLISH_INDICATION message with CM service request is received on SDCCH from the BTS. This counter is updated also in case of an SMS or Supplementary Service Requests.

The handover cause is UPLINK QUALITY.The handover cause is UPLINK LEVEL.The handover cause is DOWNLINK QUALITY.The handover cause is DOWNLINK LEVEL.The handover cause is DISTANCE.The handover cause is HIGH INT ON UPLINK.The cause sighs INT ON DOWNLINK.The handover cause is UMBRELLA.The handover cause is POWER BUDGET.

Number of successful SDCCH seizures for call re-establishment attempts. When an ESTABLISHMENT_INDICATION message for a call re-establishment is received on SDCCH from the BTS. This counter counts only the number of re-establisment attempts on SDCCH. The counter 057022 gives the number of SDCCH re-establishment assignments.Number of successful seizures of SDCCHs for an emergency call. When an ESTABLISH_INDICATION message for an emergency call is received on SDCCH from the BTS.Number of SMSs successfully established on an SDCCH. The counter is updated when an ESTABLISH_INDICATION message (mobile originating SMS) or an ESTABLISH_CONFIRM message (mobile terminating SMS) is received on SDCCH from the BTS.Number of unsuccessful establishments of SMSs on an SDCCH. After the establishment of an SMS fails on SDCCH the counter is updated.Number of successful seizures of SDCCHs for supplementary service. Counter update goes after an ESTABLISH_INDICATION message with CM service request and service type supplementary service is received on SDCCH from the BTS.Number of calls started directly after an SMS on the already reserved SDCCH. When an ASSIGNMENT REQUEST message is received directly after a successful SMS on SDCCH from the MSC.Number of successful outgoing handovers controlled by the MSC. This counter is updated when one of the counters 004049, 004050 or 004051 is updated. This counter represents their sum. Updated when the handover is completed.Number of successful outgoing handovers controlled by the BSC. This counter is updated when one of the counters 004064, 004065 or 004066 is updated. This counter represents their sum. Updated when the handover is completed.Number of successful intra-cell handovers. This counter is updated when one of the counters 004073, 004074 or 004075 is updated. This counter represents their sum. Updated when the handover is completed.

Number of successful incoming TCH to TCH handovers controlled by the MSC. Updated when the handover is completed.Number of successful incoming SDCCH to TCH handovers controlled by the MSC. Counter 004000 is updated along with this counter. When a directed retry procedure is completed.

Number of successful outgoing SDCCH to TCH handovers controlled by the MSC. The directed retry procedure is completed when the counter is released

Number of successful incoming TCH to TCH handovers controlled by the BSC (pegged only in 2G handovers.) Updated when the HO is completed.Number of successful incoming SDCCH to TCH handovers controlled by the BSC. Counter 004010 is updated along with this counter. When a directed retry procedure is completed or when the direct access to the super-reuse TRX is completed or when the TCH assignment to the super-reuse TRX is completed.

004014 is updated along with this counter. Updated when a directed retry procedure is completed, when the direct access from the SDCCH to TCH on a super-reuse TRX is completed, when the intelligent directed retry is completed or when the TCH assignment to a super-reuse TRX is completed.Number of successful intra-cell (SDCCH to TCH) handovers. Counter 004018 is updated along with this counter. When a channel assignment to a super-reuse TRX in an IUO DR is completed or when the direct access to a super-reuse TRX is completed.Number of calls that are dropped during outgoing handovers controlled by the BSC. Counters 004012, 004016 and 004083 are updated along with this counter, or counters 004013, 004017 and 004083 are updated along with this counterNumber of calls dropped during intra-cell handovers. Counter 004020 is updated along with this counter when the MS is lost or counter 004021 is updated along with this counter when switching from a unidirectional to a bi-directional speech path fails.Number of calls that are dropped during external handovers after HANDOVER_COMMAND is received from the MSC. Counter 004007 is updated along with this counter.Number of successfully completed incoming (UTRAN to GSM) handovers. Updated when the inter-system handover (UTRAN to GSM) is acknowledged and completed.Number of the INTER_SYSTEM_HANDOVER_TO_WCDMA_RAN_COMMAND messages generated by outgoing (GSM to WCDMA RAN) inter-system handovers controlled by the MSC. When HANDOVER COMMAND is sent to the MS the counter is updated.Number of dropped calls during outgoing (GSM to WCDMA RAN) handovers after HANDOVER COMMAND is received from the MSC. When a call is dropped during an external handover after the BSC has received a HANDOVER_COMMAND message. The HANDOVER_COMMAND message is received when either the GSM timer T8 expires or when the MSC sends a CLEAR_COMMAND message to the BSC with other cause than call control or handover successful. The counter is updated for non-transparent data calls, transparent data calls or speech calls.the inter-system handover is completed and BSC has received CLEAR_COMMAND from the MSC. The counter is updated for non-transparent data calls, transparent data calls, speech calls.Number of the served FACCH call requests. When a TCH channel is successfully reserved for an FACCH call set-up. A TCH is reserved, because there is a congestion situation on the SDCCH.

Number of times when the GSM timer T3101 expires. The IMMEDIATE_ASSIGN_COMMAND message is sent but an ESTABLISH_INDICATION message is not received causing the GSM timer T3101 to expire on the SDCCH then the counter is updated.Number of the SDCCH assignments. Counter released when an ESTABLISH_INDICATION message is received on the SDCCH from the BTS. This means that an MS is also moved to the SDCCH channel. This counter is updated with all SDCCH assignments, except handover.Number of the TCH call requests Updated when the TCH channel is requested from the RRM. This counter includes all TCH requests, except TCH to TCH handovers. This counter is not updated in re-establishment case.Number of the TCH new call assignments. In case of a new callan ASSIGNMENT_COMPLETE message is received on TCH from the BTS. This counter is updated when an ESTABLISH_INDICATION message is received on the TCH from the BTS. While normal directed retry (inter-cell directed retry) this counter is updated when a HANDOVER_COMPLETE message is received on the TCH from the BTS. If external SDCCH to SDCCH handover is made after a re-establishment, this counter is also updated.

Number of the TCH normal releases. When the TCH channel is released (after a CHANNEL_RELEASE message) without any problems and the channel is reserved for a normal call the counter is updated. If an external handover is made after a re-establishment this counter is also updated. In case the BSC receives a Release Indication message from the BTS withandoverut having started the call release, the BSC does not consider this as a dropped call and therefore it triggers this counter.The counter is triggered exactly after IMMEDIATE_ASSIGNMENT, PACKET_UPLINK_ASSIGNMENT or PACKET_TIMESLOT_RECONFIGURE messages. Consecutive TBFs from the same MS to the same direction might use only one TSL allocation. This counter is not updated in reallocations, whereas counters 072034 to 072038 and 072044 to 072048 are updated both unacknowledged mode downlink TBF establishments. Updated when a downlink TBF is established. The counter is triggered after IMMEDIATE_ASSIGNMENT, PACKET_DOWNLINK_ASSIGNMENT messages. This counter is not updated in reallocations. This Number of uplink TBF releases due to no response from MS. The BSC increases N3101 for each USF when no data is received from the MS. When N3101 reaches the maximum value timer T3169 is started. When the timer expires and neither a SUSPEND nor FLUSH-LL message is received before expiration this counter is updated. If either of them is received before T3169 expiration, a corresponding counter 072058 UL TBF_REL_DU_ TO_FLUSH or 072060 UL_TBF_REL DUE_TO_SUSPEND is updated instead. This counter is updated separately for normal, extended and super-extended areas.Number of downlink TBF releases due to no response from MS. If the BSC does not receive a PACKET_DOWNLINK_ACK/NACK message after it has polled the MS, it increases N3105. When the timer expires, and neither a SUSPEND nor FLUSH-LL message is received before expiration, this counter is updated. If either of them is received before T3195 expiration a corresponding counter 072059 DL TBF REL DUE TO FLUSH or 072061 DL TBF REL DUE TO SUSPEND is updated instead. This counter is updated separately for normal, extended and super-extended areas.Number of new RLC data blocks in downlink with CS1. This counter does not count the retransmitted data blocks. When a valid, new RLC data block is sent in downlink with CS1 coding scheme the counter is updated. This counter does not include retransmissions, but is triggered both in acknowledged and unacknowledged modes.In downlink data transfer the PCU selects the CS to be used, and the code word for the selected CS is included in each sent RLC data block. If the CS is changed during one TBF reservation, the new CS code word is included in the blocks. In retransmissions the same CS has to be used as in the initial block transmission. The unacknowledged RLC blocks always use CS1 and trigger this counter. This counter is updated separately for normal, extended and super-extended areas.CS2. This counter does not include retransmissions. In downlink packet transfer the PCU selects the CS to be used, and the code word for the selected CS is included in each sent RLC data block. If the CS is changed during one TBF reservation, the new CS code word is included in the blocks. In retransmission the same CS has to be used as in the initial block transmission. This counter is updated separately for normal, extended and not include retransmissions, but it is triggered both in acknowledged and unacknowledged modes. The MS is told with either the IMMEDIATE_ASSIGNMENT or the PACKET_UPLINK_ASSIGNMENT message which CS to use initially in the uplink data transfer. The PCU can command the MS to change the CS by sending a PACKET_UPLINK_ACK/NACK message that includes a Channel Coding Command field. In retransmissions the same CS has to be retransmissions. CS2 is always acknowledged. The MS is told with either the IMMEDIATE_ASSIGNMENT or PACKET_UPLINK_ASSIGNMENT message which CS to use initially in the uplink data transfer. The PCU can command the MS to change the CS by sending a

the uplink data transfer. The PCU can command the MS to change the CS by sending a PACKET_UPLINK_ACK/NACK message, which includes the Channel Coding Command field. In retransmission the same CS has to be used as in the initial block transmission. This Number of packet channel requests on CCCH. Updated when a packet channel request is received on common control channel (CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST).

Number of uplink GPRS TBF establishments that have failed due to no response from MS. Updated when the TBF establishment is aborted.

Number of downlink GPRS TBF establishments that have failed due to no response from MS. Updated when the GPRS TBF establishment is aborted due to no response from MS.

Number of uplink EGPRS TBF establishments that have failed due to no response from MS. Updated when the EGPRS TBF establishment is aborted due to no response from MS.

Number of downlink EGPRS TBF establishments that have failed due to no response from MS. Updated when the EGPRS TBF establishment is aborted due to no response from MS.Denominator for the sum of uplink TBFs average values per timeslot. Incremented once per second. This counter is updated separately for normal, extended and super-extended areas.Denominator for the sum of downlink TBFs average values per timeslot. Incremented once per second. This counter is updated separately for normal, extended and super-extended areas.Number of started UL TBF establishments. Updated before radio resources are allocated after the PCU has received a Channel Request for a new TBF, or channel request in a Packet DL Ack/Nack if there is an ongoing DL TBF. Updated only once per TBF. This counter is updated separately for normal, extended and super-extended areas.Sum of uplink TBFs average values per timeslot. An average value is counted once per second from the used timeslots of a GPRS/EDGE territory. The obtained decimal value is then multiplied by 100 and summed up to this counter. This counter is updated separately for normal, extended and super-extended areas.Sum of downlink TBFs average values per timeslot. An average value is counted once per second from the used timeslots of a GPRS/EDGE territory. The obtained decimal value is then multiplied by 100 and summed up to this counter. This counter is updated separately for normal, extended and super-extended areas.

Number of DL RLC data blocks sent to an EGPRS MS in acknowledged mode for the first time. Retransmitted blocks are not included. The counter is updated after DL RLC data block is sent. This counter is updated separately for normal, extended and super-extended areas.

Number of DL RLC data blocks in unacknowledged mode sent to an EGPRS MS. In unacknowledged mode there are no retransmissions on RLC level. The PCU does not know how many of these blocks get correctly through to the MS. When a DL RLC data block is sent the counter is updated. This counter is updated separately for normal, extended and super-extended areas.

Number of valid UL RLC data blocks with a new BSN received in acknowledged mode from an EGPRS MS within a radio block having a valid header. The counter is updated after valid UL RLC data block is received. This counter is updated separately for normal, extended and super-extended areas.

Not in use.

Number of valid UL RLC data blocks with a new BSN received in acknowledged mode from an EGPRS MS within a radio block having a valid header. The counter is updated after valid UL RLC data block is received. This counter is updated separately for normal, extended and super-extended areas.

Number of valid UL RLC data blocks with a new BSN received in unacknowledged mode from an EGPRS MS within a radio block having a valid header. When a valid UL RLC data block is received the counter is updated. This counter is updated separately for normal, extended and super-extended areas.

Sum of DTM allocation durations having a full rate speech connection. The BSC measures for handover long each DTM CS connection is kept in the PS territory with a full rate speech connection. The measured durations are summed up to this counter.Number of TCH assignment failures where the MS has returned to SDCCH. Updated when the BSC receives ASSIGNMENT FAILURE message from the MS via the BTS indicating that the MS has returned to SDCCH.

Presence in KPI formulas

BSS: dcr_54b Call Drop Rate


BSS: blck_5, SDCCH blocking, before FCS

BSS: blck_5, SDCCH blocking, before FCS

BSS: csf_43b SDCCH usage success rate,BSS: sdr_18a SDCCH RF Loss Rate

BSS: csf_43b SDCCH usage success rate

BSS: sdr_18a SDCCH RF Loss Rate ,

BSS: blck_1a, TCH call blocking


BSS: trf_486a Immediate assignment success rate%

BSS: dcr_29 TCH drop

BSS: dcr_29 TCH drop,BSS: dcr_54b Call Drop Rate







BSS: cssr_8a Call setup success rate









BSS: blck_8i, Call Set-Up Blocking Rate

BSS: blck_8i, Call Set-Up Blocking Rate




BSS: hsr_34a Inter BSS HO Success Rate

BSS: hsr_33a Intra BSS HO Success Rate

BSS: dcr_29 TCH drop,BSS: dcr_54 Call Drop Rate

BSS: trf_1d Average CS traffic per BTS

BSS: trf_1d Average CS traffic per BTSBSS: trf_489 TCH traffic carried

BSS: csf_44b TCH allocation success rate

BSS: csf_44b TCH allocation success rateBSS: hsr_28 Total handover success ratio,BSS: hsr_28 Total handover success ratio,BSS: hsr_28 Total handover success ratio,BSS: hsr_32a Intra cell HO Success Rate

BSS: dcr_26a TCH drop / Erlang (before re-establishment),


BSS: trf_490 SDCCH Traffic CarriedBSS: trf_489 TCH traffic carried,BSS: dcr_55a Mean Time Between Drops

BSS: ava_1g TCH availability ratio








BSS: trf_486a Immediate assignment success rate% ,BSS: trf_467a Immediate assignment access rate,BSS: trf_487 Circuit switched system access

BSS: trf_467a Immediate assignment access rate,

BSS: trf_487 Circuit switched system access

BSS: trf_467a Immediate assignment success rate,

BSS: trf_467a Immediate assignment access rate








BSS: hsr_33a Intra BSS HO Success Rate

BSS: HO DistributionBSS: HO DistributionBSS: HO DistributionBSS: HO DistributionBSS: HO DistributionBSS: HO DistributionBSS: HO DistributionBSS: HO DistributionBSS: HO Distribution


BSS: trf_488 Call Volume BSS: cssr_8a Call setup success rate




BSS: hsr_28 Total handover success ratio,BSS: hsr_28 Total handover success ratio,BSS: hsr_28 Total handover success ratio,BSS: hsr_32a Intra cell HO Success Rate

BSS: csf_44b TCH allocation success rate,




BSS: hfr_68c handover drop ratio







BSS: sdr_18a SDCCH RF Loss Rate

BSS: csf_43b SDCCH usage success rate,

BSS: trf_485a Assignment success rate

BSS: trf_485a Assignment success rate,BSS: dcr_54b Call Drop Rate ,BSS: trf_488 Call Volume BSS: cssr_8a Call setup success rate


BSS: csf_44b TCH allocation success rate

BSS: hsr_28 Total handover success ratio,BSS: hsr_34a Inter BSS HO Success Rate ,

BSS: hsr_28 Total handover success ratio,BSS: csf_44b TCH allocation success rate,BSS: trf_486a Immediate assignment success rate% ,

BSS: trf_486a Immediate assignment success rate%



BSS: tbf_142 UL TBF Failure Rate

BSS: tbf_143 DL TBF Failure Rate



BSS: tbf_74a, TBF establishment success rate UL,

BSS: tbf_145 (E)GPRS DL TBF establishment failure ratio,

BSS: trf_213c, trf_212c GPRS DL/UL Payload Data,

BSS: trf_494 GPRS UL Payload data, trf_495 GPRS DL Payload data

BSS: trf_213c, trf_212c GPRS DL/UL Payload Data,BSS: trf_494 GPRS UL Payload data, trf_495 GPRS DL Payload data BSS: trf_213c, trf_212c GPRS DL/UL Payload Data,BSS: trf_494 GPRS UL Payload data, trf_495 GPRS DL Payload data BSS: trf_213c, trf_212c GPRS DL/UL Payload Data,

BSS: 072082 PACKET_CH_REQ



BSS: trf_494 GPRS UL Payload data, trf_495 GPRS DL Payload data

BSS: tbf_74a, TBF establishment success rate ULBSS: tbf_145 (E)GPRS DL TBF establishment failure ratio,

BSS: tbf_74a, TBF establishment success rate UL,

BSS: tbf_145 (E)GPRS DL TBF establishment failure ratioBSS: tbf_38d, tbf_37d Average DL/UL TBF per timeslotBSS: tbf_38d, tbf_37d Average DL/UL TBF per timeslot

BSS: tbf_74a, TBF establishment success rate UL

BSS: tbf_38d, tbf_37d Average DL/UL TBF per timeslot

BSS: tbf_38d, tbf_37d Average DL/UL TBF per timeslot

BSS: trf_213c, trf_212c GPRS DL/UL Payload Data,BSS: trf_215a, trf_214a EGPRS DL/UL Payload DataBSS: trf_494 GPRS UL Payload data, trf_495 GPRS DL Payload data BSS: trf_213c, trf_212c GPRS DL/UL Payload Data,BSS: trf_215a, trf_214a EGPRS DL/UL Payload Data,BSS: trf_494 GPRS UL Payload data, trf_495 GPRS DL Payload data BSS: trf_213c, trf_212c GPRS DL/UL Payload Data,



BSS: sdr_18a SDCCH RF Loss Rate

BSS: trf_215a, trf_214a EGPRS DL/UL Payload DataBSS: trf_494 GPRS UL Payload data, trf_495 GPRS DL Payload data BSS: trf_213c, trf_212c GPRS DL/UL Payload Data,BSS: trf_215a, trf_214a EGPRS DL/UL Payload Data,BSS: trf_494 GPRS UL Payload data, trf_495 GPRS DL Payload data BSS: dcr_26a TCH drop / Erlang (before re-establishment),


2g counters

Documents