Counter Delta Introduction(GBSS9.0 vs. GBSS8.0)

Why Do We Change GBSS9.0 Counters? Operators Voice: Too Many Counters; Too Few CountersToo many counters: nearly 4,800 counters in GBSS8.0, what for? Too few counters: lacking in some necessary counters that the operator asks for

Pressure on M2000 Mounts with Counters' Continuous Increase in Each R VersionThe number of counters provided by the BSC6000 increases continuously with the upgrade of versions and reaches nearly 4,800 in GBSS8.0. Any counter measurement task that is registered must be imported to the M2000 with the north-bound interface ready. As a result, the performance of the M2000 worsens day by day. In addition, the operator has to add expenditure on hardware to process more counters.

High Cost of Maintenance and UseStudying, maintaining, and using so many counters cost much.

After GU Integration, Counters Related to Devices and Transmission Need to Be Combined to Implement 1 + 1 < 2.Some counters in GBSS8.0 are not inherited in GBSS9.0 on the basis of repeated reviews by personnel from departments of technical service, network optimization, network maintenance, R&D, performance, and documentation. In GBSS9.0, the counters in GBSS8.0 that are frequently used by the operator are inherited and those that are rarely used are not inherited. In this way, the load on the M2000 is lightened and its management is improved. The impact of counter change on the operator is lessened and design freedom is increased. Future evolution of the SRAN is thus better supported.

Yu Jing - :?Yu Jing - :Yu Jing - SRAN:thus

Compared with counters in GBSS8.0, counters in GBSS9.0 undergo great changes. The overall change is as follows: Difference from GBSS8.0 Number of added counters: 1763 Number of modified counters: 1153 (mainly modified in counter names and calculation formulas) Number of deleted counters: 835 Note: Some modification involves KPI. Change ReasonsOverall Difference in Counters Between GBSS9.0 and GBSS8.0

Deleted (835)18Counter deletion follows platform integration between 2G and 3G.136Counters related to transmission and devices are used for internal optimization.131Auxiliary counters in calculation needs no measurement.136Replaceable counters7Counter deletion follows change in devices and functions. 6No need for measurement because of device capacity expansion2Some counters can be monitored by alarms.399Counters with no practical valuesAdded(1763)800Optimization of old features963Addition of new featuresModified(1153)45Change in counter ID and measurement unit8Change in counter formulas1100Counter name standardization

Documentation Difference Between GBSS9.0 and GBSS8.01. Counter names change. For example, BC_TRAN_TX_FR is changed to BC.TRAN.TX.FR. 2. Short names and counter descriptions are presented together.3. Counter ID is added. 4. Features corresponding to counters are added.5. Overall measurement flow charts are added for key measurement units.6. Information about counter change is separately revealed in release notes.

Reasons for Counter Deletion in GBSS9.0 Compared with GBSS8.0Counter Deletion Follows Platform Integration Between 2G and 3GSome 2G and 3G hardware devices are combined into one in GBSS9.0, so the relevant counters are deleted. For example,

Counter Change TypeCounter IDCounter Name Deleted1278969417L01001:Number of Received BytesDeleted1278969418L01002:Number of Received PacketsDeleted1278969419L01003:Number of Sent BytesDeleted1278969420L01004:Number of Sent PacketsDeleted1278969421L01005:Number of Received Error Packets

Reasons for Counter Deletion in GBSS9.0 Compared with GBSS8.0 Counters Related to Transmission and Devices Are Used for Internal OptimizationThe counters related to transmission and devices are private counters of a vendor. They are mainly used for internal maintenance and problem location and the operator seldom cares about them. Therefore the counters are deleted in GBSS9.0. For example,

Counter Change TypeCounter IDCounter Name Deleted1276075417L2100A:Duration of CRC Error on Ports 0Deleted1276075418L2100A:Duration of CRC Error on Ports 1Deleted1276075419L2100A:Duration of CRC Error on Ports 2Deleted1276075420L2100A:Duration of CRC Error on Ports 3Deleted1276075421L2100A:Duration of CRC Error on Ports 4Deleted1276075422L2100A:Duration of CRC Error on Ports 5Deleted1276075423L2100A:Duration of CRC Error on Ports 6Deleted1276075424L2100A:Duration of CRC Error on Ports 7Deleted1276075425L2100A:Duration of CRC Error on Ports 8Deleted1276075426L2100A:Duration of CRC Error on Ports 9Deleted1276075427L2100A:Duration of CRC Error on Ports 10Deleted1276075428L2100A:Duration of CRC Error on Ports 11

Reasons for Counter Deletion in GBSS9.0 Compared with GBSS8.0 Auxiliary Counters in Calculation Needs No MeasurementIn GBSS8.0, some counters of the temporary process variable (such as accumulated values or sampling values ) type are kept. The counters, however, do not need to be measured. Therefore, the auxiliary counters are deleted in GBSS9.0. For example,

Counter Change TypeCounter IDCounter Name Deleted1278473459R3590:Number of Attempts to Scan SDCCH StatesDeleted1279269426R9210:Sampling Times of PDCH Queue LengthDeleted1279269427R9210:Sampling Times of PDCH Queue LengthDeleted1279269429R9211:Total Sampled PPCH Queue LengthsDeleted1279269431R9213:Total Sampled PAGCH Queue LengthsDeleted1279769417R9215:Total Sampled PDTCH Queue LengthsDeleted1279769418R9401:Total Sampled DSP CPU UsageDeleted1279770419R9402:Sampling Times of DSP CPU UsageDeleted1279770420R9503:Total Number of Sampled PDCHs Activated on DSPDeleted1279770424R9504:Sampling Times of PDCH Measurement on DSPDeleted1279869418R9508:Total Number of Sampled PDCHs Occupied on DSPDeleted1279869419S9202:Total Number of Sampled PDCHs Assigned per BSC

Reasons for Counter Deletion in GBSS9.0 Compared with GBSS8.0 Replaceable CountersSome replaceable or calculable counters in GBSS8.0 are redundant and therefore deleted in GBSS9.0. Calculable counters are deleted in GBSS9.0. For example, some counters at the BSC level are deleted in GBSS9.0 because they are insignificant and calculable by accumulating counters at the cell level. Some counters in GBSS8.0 are replaced with new ones in GBSS9.0 because some devices are redesigned. For example,

Counter Change TypeCounter IDCounter NameDeleted1278287437S4420E:Ratio (RQI = 0 to 1)Deleted1278287438S4421E:Ratio (RQI = 1 to 2)Deleted1278287439S4422E:Ratio (RQI = 2 to 3)Deleted1278287440S4423E:Ratio (RQI = 3 to 4)Deleted1278287441S4424E:Ratio (RQI = 4 to 5)Deleted1278287442S4425E:Ratio (RQI = 5 to 6)Deleted1278287443S4426E:Ratio (RQI = 6 to 7)Deleted1278287444S4427E:Ratio (RQI = 7 to 8)Deleted1278287445S4428E:Ratio (RQI = 8 to 9)Deleted1278287446S4429E:Ratio (RQI = 9 to 10)Deleted1278287447S4430E:Ratio (RQI = 10 to 11)Deleted1278287448S4431E:Ratio (RQI = 11 to 12)Deleted1278287449S4432E:Ratio (RQI = 12 to 13)Deleted1278287450S4433E:Ratio (RQI = 13 to 14)Deleted1278287451S4434E:Ratio (RQI = 14 to 15)

Reasons for Counter Deletion in GBSS9.0 Compared with GBSS8.0 Counter Deletion Follows Change in Devices and FunctionsPrior change in devices and functions renders some counters in GBSS8.0 meaningless in GBSS9.0. The counters are therefore deleted in GBSS9.0. For example,

Counter Change TypeCounter IDCounter NameDeleted1275080419AR9702:Average CPU UsageDeleted1275080420R9703:Maximum CPU UsageDeleted1277469417L0387:Total Number of Messages Received from PCUDeleted1277669417L8387:Messages Received from a PCUDeleted1278479417R3140:Requests for TCH from the PCUDeleted1278479418R3141:Successful Requests for TCH from the PCUDeleted1278479419R3142:Number of Failures to Request Dynamic PDCH (No Abis Resources Available)

Reasons for Counter Deletion in GBSS9.0 Compared with GBSS8.0 No Need for Measurement Because Of Device Capacity ExpansionThe capacity or processing capability of some hardware boards improves in GBSS9.0. Accordingly, bottlenecks change. Relevant counters are therefore deleted in GBSS9.0. For example,

Counter Change TypeCounter IDCounter NameDeleted1277870435A349:Discarded CS PagingsDeleted1277870436A350:Discarded PS PagingsDeleted1277871417A530:SM Pagings Discarded on LAPD LinkDeleted1277871418A531:CS Pagings Discarded on LAPD LinkDeleted1277871419A532:PS Pagings Discarded on LAPD LinkDeleted1278088417A533:Random Access Requests Discarded on LAPD

Reasons for Counter Deletion in GBSS9.0 Compared with GBSS8.0 Some Counters Can Be Monitored by AlarmsThe counters that can be monitored by means of alarms are deleted in GBSS9.0. For example,

Counter Change TypeCounter IDCounter NameDeleted1276069417R2701:Successful BTS InitializationsDeleted1276069418R2702:Failed BTS Initializations

Reasons for Counter Deletion in GBSS9.0 Compared with GBSS8.0 Counters with No Practical ValuesThe counters with few practical values for measurement are deleted in GBSS9.0. For example, the counters at the cell level, R3317C:Channel Activation Timeouts in Assignment Procedure (TCHF) and R3327C:Channel Activation Timeouts in Mode Modify Procedure (TCHF) are deleted for a lack of practical values. Although the two counters are intended to indicate respective number of channel allocation timeouts during assignment and mode modification, channel activation timeout is, however, irrelevant to traffic procedures. Once TRXs are faulty, channel activation timeout occurs in the same probability no matter the procedure is that for normal allocation, mode modification, or incoming handovers. Thus only the total number of channel activation timeouts and channel allocation requests are needed and specific procedures need no measurement.

Counter Change TypeCounter IDCounter NameDeleted1278073426R3317A:Channel Activation Attempts in Assignment Procedure (TCHF)Deleted1278073427R3318A:Channel Activation Attempts in Assignment Procedure (TCHH)Deleted1278073432R3327A:Channel Activation Attempts in Mode Modify Procedure (TCHF)Deleted1278073433R3328A:Channel Activation Attempts in Mode Modify Procedure (TCHH)Deleted1278073436R3327C:Channel Activation Timeouts in Mode Modify Procedure (TCHF)Deleted1278073437R3328C:Channel Activation Timeouts in Mode Modify Procedure (TCHH)Deleted1278073438R3330A:Channel Activation Attempts in Internal Intra-Cell Handover Procedure (SDCCH)Deleted1278073439R3337A:Channel Activation Attempts in Internal Intra-Cell Handover Procedure (TCHF)Deleted1278073440R3338A:Channel Activation Attempts in Internal Intra-Cell Handover Procedure (TCHH)Deleted1278073444R3330C:Channel Activation Timeouts in Internal Intra-Cell Handover Procedure (SDCCH)Deleted1278073445R3337C:Channel Activation Timeouts in Internal Intra-Cell Handover Procedure (TCHF)Deleted1278073446R3338C:Channel Activation Timeouts in Internal Intra-Cell Handover Procedure (TCHH)

Reasons for Counter Addition in GBSS9.0 Compared with GBSS8.0 Optimization of Old FeaturesTo increase means of measurement for features in V 8.0, some counters are added. For example, Multi-Carrier Power Allocation (MCPA)For more examples, see the following table.

Counter Change TypeCounter IDCounter NameAdded1276073420R476:The total BURST count cut 0.5dB powerAdded1276073421R477:The total BURST count cut 1.0dB powerAdded1276073422R478:The total BURST count cut 1.5dB powerAdded1276073423R479:The total BURST count cut 2.0dB powerAdded1282411785R483:The total BURST count cut 2.5dB powerAdded1282411786R484:The total BURST count cut 3.0dB and above power

Reasons for Counter Addition in GBSS9.0 Compared with GBSS8.0 Addition of New FeaturesTo increase means of measurement for new features in GBSS9.0, some counters are added. For example, counters are added for new features such as MSC Pool and WB-AMR. For more examples, see the following table.

Counter Change TypeCounter IDCounter NameAdded1282411682L0057F:Number of Users Assigned to the MSC According to NRI Load Sharing in TMSIAdded1282411683L0057G:Number of Users Assigned to the MSC According to NRI Load Sharing Not in Pool in TMSIAdded1282411471S4550W:Number of Uplink Frames with WBAMR of 6.60 kbit/s in the Customized MRAdded1282411472S4551W:Number of Downlink Frames with WBAMR of 6.60 kbit/s in the Customized MRAdded1282411473S4552W:Number of Uplink Frames with WBAMR of 8.85 kbit/s in the Customized MRAdded1282411475S4553W:Number of Downlink Frames with WBAMR of 8.85 kbit/s in the Customized MRAdded1282411476S4554W:Number of Uplink Frames with WBAMR of 12.65 kbit/s in the Customized MRAdded1282411477S4555W:Number of Downlink Frames with WBAMR of 12.65 kbit/s in the Customized MRAdded1282411482S4513B:Number of Customized MRs with WBAMR Voice Quality Rank Smaller than 0.5

Reasons for Counter Modification in GBSS9.0 Compared with GBSS8.0 Change in Counter ID and Measurement UnitDue to platform change in GBSS9.0, measurement units are rearranged for some counters and counter ID is changed. For example,

Counter Change TypeCounter IDCounter NameChange ReasonValues in GBSS8.0Modified1282423588AL1251:Mean number of faulty circuits on the Ater interfaceWe change the measurement unit, measurement object, counter ID and counter name by transferring the resource management of the Ater interface from the MPS/EPS to the TCS.Measurement Unit: 1275070218: Ater Interface Circuit Measurement per TC SubrackMeasurement Object: 1275069427: TCCounter ID: 1276870419Modified1282423589AL1253:Mean number of blocked circuits on the Ater interfaceWe change the measurement unit, measurement object, counter ID and counter name by transferring the resource management of the Ater interface from the MPS/EPS to the TCS.Measurement Unit: 1275070218: Ater Interface Circuit Measurement per TC SubrackMeasurement Object: 1275069427: TCCounter ID: 1276870422Modified1282423590AL1252:Mean number of circuits in maintenance state on the Ater interfaceWe change the measurement unit, measurement object, counter ID and counter name by transferring the resource management of the Ater interface from the MPS/EPS to the TCS.Measurement Unit: 1275070218: Ater Interface Circuit Measurement per TC SubrackMeasurement Object: 1275069427: TCCounter ID: 1276870425Modified1282423591AL1254:Mean number of idle circuits on the Ater interfaceWe change the measurement unit, measurement object, counter ID and counter name by transferring the resource management of the Ater interface from the MPS/EPS to the TCS.Measurement Unit: 1275070218: Ater Interface Circuit Measurement per TC SubrackMeasurement Object: 1275069427: TCCounter ID: 1276870428

Reasons for Counter Modification in GBSS9.0 Compared with GBSS8.0 Change in Counter FormulasDetected bugs including errors in the definition of some counter formulas are rectified in GBSS9.0. For example, in the counter, RA333: RA333:Success Rate of Call Establishment, the calculated value can exceed 100% when the allocation of the SDCCH is enabled. For more examples, see the following table.

Counter IDCounter NameValues in GBSS8.01278076513RA333:Success Rate of Call EstablishmentOld formula:Success Rate of Call Establishment = ([Success Rate of Call Setup (Immediate Assignment)]/{100})*([Success Rate of TCH Assignment]/{100})*(1-([Call Drop Rate on SDCCH]/{100}))*{100}

New formula:Success Rate of Call Establishment = ([Successful Assignments]-([Assignment Requests (Signaling Channel) SDCCH]+[Assignment Requests (Signaling Channel) TCH]-[Failed Assignments (Signaling Channel)]+[Assignment Requests (TCH Assigned Repeatedly over A Interface)]-[Failed Assignments (TCH Assigned Repeatedly over A Interface)]))*{100}/([SDCCH Seizures for Speech Service]+[TCHF Seizures for Speech Service]+[TCHH Seizures for Speech Service])

Reasons for Counter Modification in GBSS9.0 Compared with GBSS8.0 Counter Name StandardizationCounter names are standardized in GBSS9.0. Counter definitions remain unchanged. For example,

Counter Change TypeCounter IDCounter NameModified1279469417L9701:Number of transmitted NS PDUs on NSVCModified1279469418L9702:Number of received NS PDUs on NSVCModified1279469419L9703:Number of discarded NS PDUs on NSVCModified1279469420L9704:Total Number of bytes of transmitted NS PDUs on NSVCModified1279469421L9705:Total Number of bytes of received NS PDUs on NSVCModified1279469422L9706:Number of transmitted RESET Messages on NSVCModified1279469423L9707:Number of received RESET ACK Messages on NSVCModified1279469424L9708:Number of received RESET Messages on NSVCModified1279469425L9709:Number of transmitted RESET ACK Messages on NSVCModified1279469426L9710:Number of transmitted BLOCK Messages on NSVCModified1279469427L9711:Number of received BLOCK ACK Messages on NSVCModified1279469428L9712:Number of received BLOCK Messages on NSVCModified1279469429L9713:Number of transmitted BLOCK ACK Messages on NSVC