BreezeCOMPACT Performance Monitoring Reference Guide

Transcription

1 BreezeCOMPACT Performance Monitoring Reference Guide Software Version: 4.0 April 2011 P/N

2 Document History Document History Topic Description Date Issued This is the book first publication Release 4.0, April 2012 ii

3 Legal Rights Legal Rights Trade Names Copyright 2012 Alvarion Ltd. All rights reserved. The material contained herein is proprietary, privileged, and confidential and owned by Alvarion or its third party licensors. No disclosure thereof shall be made to third parties without the express written permission of Alvarion Ltd. Alvarion Ltd. reserves the right to alter the equipment specifications and descriptions in this publication without prior notice. No part of this publication shall be deemed to be part of any contract or warranty unless specifically incorporated by reference into such contract or warranty. Alvarion, BreezeCOM, WALKair, WALKnet, BreezeNET, BreezeACCESS, BreezeLINK, BreezeMAX, BreezeLITE, BreezePHONE, 4Motion and/or other products and/or services referenced here in are either registered trademarks, trademarks or service marks of Alvarion Ltd. All other names are or may be the trademarks of their respective owners. WiMAX Forum is a registered trademark of the WiMAX Forum. WiMAX, the WiMAX Forum logo, WiMAX Forum Certified, and the WiMAX Forum Certified logo are trademarks of the WiMAX Forum. Statement of Conditions The information contained in this manual is subject to change without notice. Alvarion Ltd. shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual or equipment supplied with it. Warranties and Disclaimers Exclusive Warranty All Alvarion Ltd. ( Alvarion ) products purchased from Alvarion or through any of Alvarion's authorized resellers are subject to the following warranty and product liability terms and conditions. (a) Alvarion warrants that the Product hardware it supplies and the tangible media on which any software is installed, under normal use and conditions, will be free from significant defects in materials and workmanship for a period of fourteen (14) months from the date of shipment of a given Product to Purchaser (the Warranty Period ). Alvarion will, at its sole option and as Purchaser's sole remedy, repair or replace any defective Product in accordance with Alvarion' standard R&R procedure. (b) With respect to the Firmware, Alvarion warrants the correct functionality according to the attached documentation, for a period of fourteen (14) month from invoice date (the Warranty Period ). During the Warranty Period, Alvarion may release to its Customers firmware updates, which include additional performance improvements and/or bug fixes, upon availability (the Warranty ). Bug fixes, temporary patches and/or workarounds may be supplied as Firmware updates. Additional hardware, if required, to install or use Firmware updates must be purchased by the Customer. Alvarion will be obligated to support solely the two (2) most recent Software major releases. ALVARION SHALL NOT BE LIABLE UNDER THIS WARRANTY IF ITS TESTING AND EXAMINATION DISCLOSE THAT THE ALLEGED DEFECT IN THE PRODUCT DOES NOT EXIST OR WAS CAUSED BY PURCHASER'S OR ANY THIRD PERSON'S MISUSE, NEGLIGENCE, IMPROPER INSTALLATION OR IMPROPER TESTING, UNAUTHORIZED ATTEMPTS TO REPAIR, OR ANY OTHER CAUSE BEYOND THE RANGE OF THE INTENDED USE, OR BY ACCIDENT, FIRE, LIGHTNING OR OTHER HAZARD. iii

4 Legal Rights Disclaimer Limitation of Liability (a) The Software is sold on an AS IS basis. Alvarion, its affiliates or its licensors MAKE NO WARRANTIES, WHATSOEVER, WHETHER EXPRESS OR IMPLIED, WITH RESPECT TO THE SOFTWARE AND THE ACCOMPANYING DOCUMENTATION. ALVARION SPECIFICALLY DISCLAIMS ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT WITH RESPECT TO THE SOFTWARE. UNITS OF PRODUCT (INCLUDING ALL THE SOFTWARE) DELIVERED TO PURCHASER HEREUNDER ARE NOT FAULT-TOLERANT AND ARE NOT DESIGNED, MANUFACTURED OR INTENDED FOR USE OR RESALE IN APPLICATIONS WHERE THE FAILURE, MALFUNCTION OR INACCURACY OF PRODUCTS CARRIES A RISK OF DEATH OR BODILY INJURY OR SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE ( HIGH RISK ACTIVITIES ). HIGH RISK ACTIVITIES MAY INCLUDE, BUT ARE NOT LIMITED TO, USE AS PART OF ON-LINE CONTROL SYSTEMS IN HAZARDOUS ENVIRONMENTS REQUIRING FAIL-SAFE PERFORMANCE, SUCH AS IN THE OPERATION OF NUCLEAR FACILITIES, AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL, LIFE SUPPORT MACHINES, WEAPONS SYSTEMS OR OTHER APPLICATIONS REPRESENTING A SIMILAR DEGREE OF POTENTIAL HAZARD. ALVARION SPECIFICALLY DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY OF FITNESS FOR HIGH RISK ACTIVITIES. (b) PURCHASER'S SOLE REMEDY FOR BREACH OF THE EXPRESS WARRANTIES ABOVE SHALL BE REPLACEMENT OR REFUND OF THE PURCHASE PRICE AS SPECIFIED ABOVE, AT ALVARION'S OPTION. TO THE FULLEST EXTENT ALLOWED BY LAW, THE WARRANTIES AND REMEDIES SET FORTH IN THIS AGREEMENT ARE EXCLUSIVE AND IN LIEU OF ALL OTHER WARRANTIES OR CONDITIONS, EXPRESS OR IMPLIED, EITHER IN FACT OR BY OPERATION OF LAW, STATUTORY OR OTHERWISE, INCLUDING BUT NOT LIMITED TO WARRANTIES, TERMS OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, SATISFACTORY QUALITY, CORRESPONDENCE WITH DESCRIPTION, NON-INFRINGEMENT, AND ACCURACY OF INFORMATION GENERATED. ALL OF WHICH ARE EXPRESSLY DISCLAIMED. ALVARION' WARRANTIES HEREIN RUN ONLY TO PURCHASER, AND ARE NOT EXTENDED TO ANY THIRD PARTIES. ALVARION NEITHER ASSUMES NOR AUTHORIZES ANY OTHER PERSON TO ASSUME FOR IT ANY OTHER LIABILITY IN CONNECTION WITH THE SALE, INSTALLATION, MAINTENANCE OR USE OF ITS PRODUCTS. (a) ALVARION SHALL NOT BE LIABLE TO THE PURCHASER OR TO ANY THIRD PARTY, FOR ANY LOSS OF PROFITS, LOSS OF USE, INTERRUPTION OF BUSINESS OR FOR ANY INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE OR CONSEQUENTIAL DAMAGES OF ANY KIND, WHETHER ARISING UNDER BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY OR OTHERWISE AND WHETHER BASED ON THIS AGREEMENT OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. (b) TO THE EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL THE LIABILITY FOR DAMAGES HEREUNDER OF ALVARION OR ITS EMPLOYEES OR AGENTS EXCEED THE PURCHASE PRICE PAID FOR THE PRODUCT BY PURCHASER, NOR SHALL THE AGGREGATE LIABILITY FOR DAMAGES TO ALL PARTIES REGARDING ANY PRODUCT EXCEED THE PURCHASE PRICE PAID FOR THAT PRODUCT BY THAT PARTY (EXCEPT IN THE CASE OF A BREACH OF A PARTY'S CONFIDENTIALITY OBLIGATIONS). iv

5 Important Notice Important Notice This user manual is delivered subject to the following conditions and restrictions: This manual contains proprietary information belonging to Alvarion Ltd. Such information is supplied solely for the purpose of assisting properly authorized users of the respective Alvarion products. No part of its contents may be used for any other purpose, disclosed to any person or firm or reproduced by any means, electronic and mechanical, without the express prior written permission of Alvarion Ltd. The text and graphics are for the purpose of illustration and reference only. The specifications on which they are based are subject to change without notice. The software described in this document is furnished under a license. The software may be used or copied only in accordance with the terms of that license. Information in this document is subject to change without notice. Corporate and individual names and data used in examples herein are fictitious unless otherwise noted. Alvarion Ltd. reserves the right to alter the equipment specifications and descriptions in this publication without prior notice. No part of this publication shall be deemed to be part of any contract or warranty unless specifically incorporated by reference into such contract or warranty. The information contained herein is merely descriptive in nature, and does not constitute an offer for the sale of the product described herein. Any changes or modifications of equipment, including opening of the equipment not expressly approved by Alvarion Ltd. will void equipment warranty and any repair thereafter shall be charged for. It could also void the user's authority to operate the equipment. v

6 Contents Contents 1. Performance Parameters Types Performance Management Methods Real-Time Performance Monitoring Performance Parameters Collection Aggregation Period Collected Files Creation and Storage Connectivity Performance Parameters Data One Interface Data Two Interface Data Three Interface Traffic Utilization Integrity TxR1 Total Traffic RxR1 Total Traffic TxR3 Total Traffic BS General All MS Basic Mode Real-Time Traffic (R1 Interface-Traffic Statistics) R1 Interface - Traffic Throughput R1 Interface - Traffic Quality R6 Interface Management NE Report...28 vi

7 Chapter 1 - Performance Parameters TypesReal-Time Performance Monitoring Performance Parameters Types Real-Time Performance Monitoring 1. Performance Parameters Types The system supports three types of performance parameters: Counter: A counter is a cumulative count of the monitored event, incremented by one for each occurrence of the event and wraps around after reaching the maximum value. Gauge: A gauge represents a dynamic variables that may change in either direction. A Gauge can be either an integer or a real value. In the current release all gauges are 32 bits. ugauge32: Used for parameters which are not counters or gauges, such as IP Addresses, Frequency, etc. 2. Performance Management Methods The system supports two methods of performance management: Real-Time Performance Monitoring Performance Parameters Collection 2.1 Real-Time Performance Monitoring The operator of a management system may request a view of on-line selected performance parameters, to be on-line gathered from the device and presented at almost real-time. The operator may select the polling interval for these parameters, as well as their presentation mode. This function is mainly used for maintenance and troubleshooting purposes. Real-time retrieval of performance parameters by a management system is based on standard SNMP GET (and GET NEXT) requests using the relevant OIDs. Each SNMP GET request may refer to one or more performance parameters. Performance parameters are defined by their MIB OIDs. A series of OIDs is used to define the corresponding series of performance parameters. The system responds to SNMP GET and GETBULK requests with the actual snapshot of current values of the requested parameters, captured on all requested parameters as close as possible to the reception of the SNMP GET (or GETBULK) request. Data may not be available for real-time performance monitoring, due to several reasons such as system restart or configuration problem. Such conditions cause SNMP GET response that includes the failure reason (standard SNMP values). 1

8 Chapter 1 - Performance Management MethodsPerformance Parameters Collection Performance Management Methods Performance Parameters Collection 2.2 Performance Parameters Collection This section includes: Aggregation Period Collected Files Creation and Storage Aggregation Period The Performance Parameters Collection capability enables collection of data by the system during a certain aggregation period and storing it in files. The management system can then upload the data files and store them for later analysis. The system manages the aggregation period start and end, according to the system s RTC (Real Time Clock) and the 1PPS signal. The requested performance data is accumulated over fixed periods of 900 seconds (15 minutes). The aggregation periods are aligned to the end of each quarter of an hour period, with accuracy of better than ± 10 seconds (10:00, 10:15, 10:30,...). System restart due to any cause during the aggregation period results in the total elimination of all historical performance data, including the data of the relevant period Collected Files Creation and Storage The system creates a file of the collected performance parameters after the expiration of each aggregation period. The file includes the performance data gathered during the same aggregation period. Performance files use XML format. The XML file structure is compliant with the 3GPP standard TS v The system compresses the combined file using GZip algorithm and name it according to the UTC time stamp of the aggregation period end, having the format of "prf_<site id>_yyyymmddhhmm.xml.gz, where: YYYY: Year MM: Month of year (01 to 12) DD: Day of month (01 to 31) hh: Hour of day (00 to 23) mm: Minute of hour, may have the following values only: 00, 15, 30, 45. Each record shall be assigned with the date and time and source device identification that includes the BTS ID and management IP address. BSs will be identified by their BS ID, frequency and BW. In addition each record of each element includes full/partial accumulation flag as follows: 0 - All the data is full. 2

9 Chapter 1 - Connectivity Performance Parameters Connectivity Performance Parameters 1 - Partial time accumulation. 2 - Provisioning has been changed during accumulation period. 3 - Provisioning has been changed during accumulation period and partial time accumulation. The partial flag shall consider also system reset or power up in the middle of integration time. Any radio head channel disable and port disconnection or failure shall be considered also as partial flag in the middle or in the start of integration time. Problem recovery in the middle of the aggregation period shall not affect partial flag. The system stores up to 24 hours of long-term performance data (96 files) in the path /tftpboot/management/performance. Files are erased from the storage (overwritten) using a FIFO mechanism. Data is not erased as a result of any management-initiated action. All data is erased after system reset. Stored performance files can be uploaded to a management system using TFTP as many times as required. If a TFTP session has started, deletion of that file caused by the FIFO mechanism does not affect the upload. 3. File Collection performance parameters are available only in collected files (not supported in the MIB, not available for real-time monitoring). This section includes: Connectivity Performance Parameters 3.1 Connectivity Performance Parameters All Connectivity performance parameters are of type Counter32. The Connectivity performance parameters include the following groups: Data One Interface Data Two Interface Data Three Interface 3

10 Chapter Data One Interface Group Name (in XML file and MIB): pmcnnctdataoneinterface Table 1: Data One Interface Performance Parameters Parameter cnnctdataoneoutoctet cnnctdataoneinoctet Description The total number of bytes transmitted from this interface The total number of bytes received on this interface Data Two Interface Group Name (in XML file and MIB): pmcnnctdatatwointerface Table 2: Data Two Interface Performance Parameters Parameter cnnctdatatwooutoctet cnnctdatatwoinoctet Description The total number of bytes transmitted from this interface The total number of bytes received on this interface Data Three Interface Group Name (in XML file and MIB): pmcnnctdatathreeinterface Table 3: Data Three Interface Performance Parameters Parameter cnnctdatathreeoutoctet cnnctdatathreeinoctet Description The total number of bytes transmitted from this interface The total number of bytes received on this interface 3.2 The BS groups are collected for each existing BS. The current groups are: Traffic Utilization Integrity TxR1 Total Traffic RxR1 Total Traffic TxR3 Total Traffic 4

11 Chapter 1 - BS General All MS Basic Mode Traffic Group Name (in XML file and MIB): pmbstraffictable Table 4: BS Traffic Performance Parameters - File Collection Parameter Type Counts the Number of... bsulharqtransmissionsqpskoneovertwotimessix Counter32 UL HARQ transmissions using QPSK 1/2 Repetition 6 bsulharqtransmissionsqpskoneovertwotimesfour Counter32 UL HARQ transmissions using QPSK 1/2 Repetition 4 bsulharqtransmissionsqpskoneovertwotimestwo Counter32 UL HARQ transmissions using QPSK 1/2 Repetition 2 bsulharqtransmissionsqpskoneovertwo Counter32 UL HARQ transmissions using QPSK 1/2 bsulharqtransmissionsqpskthreeoverfour Counter32 UL HARQ transmissions using QPSK 3/4 bsulharqtransmissionsqamsixteenoneovertwo Counter32 UL HARQ transmissions using QAM16 1/2 bsulharqtransmissionsqamsixteenthreeoverfour Counter32 UL HARQ transmissions using QAM16 3/4 bsulharqtransmissionsqamsixtyfouroneovertwo Counter32 UL HARQ transmissions using QAM64 1/2 bsulharqtransmissionsqamsixtyfourtwooverthree Counter32 UL HARQ transmissions using QAM64 2/3 bsulharqtransmissionsqamsixtyfourthreeoverfour Counter32 UL HARQ transmissions using QAM64 3/4 bsulharqtransmissionsqamsixtyfourfiveoversix Counter32 UL HARQ transmissions using QAM64 5/6 bsulharqsbdropsqpskoneovertwotimessix Counter32 Ul HARQ sub-bursts transmitted by the MSs using QPSK 1/2 Repetition 6 that were dropped (not retransmitted) although NAK was sent by the BS. bsulharqsbdropsqpskoneovertwotimesfour Counter32 Ul HARQ sub-bursts transmitted by the MSs using QPSK 1/2 Repetition 4 that were dropped (not retransmitted) although NAK was sent by the BS. bsulharqsbdropsqpskoneovertwotimestwo Counter32 Ul HARQ sub-bursts transmitted by the MSs using QPSK 1/2 Repetition 2 that were dropped (not retransmitted) although NAK was sent by the BS. 5

12 Chapter 1 - Table 4: BS Traffic Performance Parameters - File Collection (Continued) Parameter Type Counts the Number of... bsulharqsbdropsqpskoneovertwo Counter32 Ul HARQ sub-bursts transmitted by the MSs using QPSK 1/2 that were dropped (not retransmitted) although NAK was sent by the BS. bsulharqsbdropsqpskthreeoverfour Counter32 Ul HARQ sub-bursts transmitted by the MSs using QPSK 3/4 that were dropped (not retransmitted) although NAK was sent by the BS. bsulharqsbdropsqamsixteenoneovertwo Counter32 Ul HARQ sub-bursts transmitted by the MSs using QAM16 1/2 that were dropped (not retransmitted) although NAK was sent by the BS. bsulharqsbdropsqamsixteenthreeoverfour Counter32 Ul HARQ sub-bursts transmitted by the MSs using QAM16 3/4 that were dropped (not retransmitted) although NAK was sent by the BS. bsulharqsbdropsqamsixtyfouroneovertwo Counter32 Ul HARQ sub-bursts transmitted by the MSs using QAM64 1/2 that were dropped (not retransmitted) although NAK was sent by the BS. bsulharqsbdropsqamsixtyfourtwooverthree Counter32 Ul HARQ sub-bursts transmitted by the MSs using QAM64 2/3 that were dropped (not retransmitted) although NAK was sent by the BS. bsulharqsbdropsqamsixtyfourthreeoverfour Counter32 Ul HARQ sub-bursts transmitted by the MSs using QAM64 3/4 that were dropped (not retransmitted) although NAK was sent by the BS. bsulharqsbdropsqamsixtyfourfiveoversix Counter32 Ul HARQ sub-bursts transmitted by the MSs using QAM64 5/6 that were dropped (not retransmitted) although NAK was sent by the BS. bsmaplengthtwosymbols Counter32 Frames for which map length was two symbols bsmaplengthfoursymbols Counter32 Frames for which map length was four symbols bsmaplengthsixsymbols Counter32 Frames for which map length was six symbols 6

13 Chapter 1 - Table 4: BS Traffic Performance Parameters - File Collection (Continued) Parameter Type Counts the Number of... bsmaplengtheightsymbols Counter32 Frames for which map length was eight symbols bsmaplengthtensymbols Counter32 Frames for which map length was ten symbols bsmaplengthmorethantensymbols Counter32 Frames for which map length was more than ten symbols dlretranshistogramzeroretrans Counter32 Downlink transactions with zero retransmissions dlretranshistogramoneretrans Counter32 Downlink transactions with one retransmission dlretranshistogramtworetrans Counter32 Downlink transactions with two retransmissions dlretranshistogramthreeretrans Counter32 Downlink transactions with three retransmissions dlretranshistogramfourretrans Counter32 Downlink transactions with four retransmissions dlretranshistogramoverfourretrans Counter32 Downlink transactions with over four retransmissions bsdlharqtransmissionsqpskoneovertwotimessix Counter32 DL HARQ transmissions using QPSK 1/2 Repetition 6 bsdlharqtransmissionsqpskoneovertwotimesfour Counter32 DL HARQ transmissions using QPSK 1/2 Repetition 4 bsdlharqtransmissionsqpskoneovertwotimestwo Counter32 DL HARQ transmissions using QPSK 1/2 Repetition 2 bsdlharqtransmissionsqpskoneovertwo Counter32 DL HARQ transmissions using QPSK 1/2 bsdlharqtransmissionsqpskthreeoverfour Counter32 DL HARQ transmissions using QPSK 3/4 bsdlharqtransmissionsqamsixteenoneovertwo Counter32 DL HARQ transmissions using QAM16 1/2 bsdlharqtransmissionsqamsixteenthreeoverfour Counter32 DL HARQ transmissions using QAM16 3/4 bsdlharqtransmissionsqamsixtyfouroneovertwo Counter32 DL HARQ transmissions using QAM64 1/2 bsdlharqtransmissionsqamsixtyfourthreeoverfour Counter32 DL HARQ transmissions using QAM64 3/4 bsdlharqtransmissionsqamsixtyfourtwooverthree Counter32 DL HARQ transmissions using QAM64 2/3 bsdlharqtransmissionsqamsixtyfourfiveoversix Counter32 DL HARQ transmissions using QAM64 5/6 bsdlmimobqpskoneovertwoslots Counter32 DL transmitted slots in MIMO B using QPSK 1/2 7

14 Chapter 1 - Table 4: BS Traffic Performance Parameters - File Collection (Continued) Parameter Type Counts the Number of... bsdlmimobqpskthreeoverfourslots Counter32 DL transmitted slots in MIMO B using QPSK 3/4 bsdlmimobsixteenqamoneovertwoslots Counter32 DL transmitted slots in MIMO B using QAM16 1/2 bsdlmimobsixteenqamthreeoverfourslots Counter32 DL transmitted slots in MIMO B using QAM16 3/4 bsdlmimobsixtyfourqamoneovertwoslots Counter32 DL transmitted slots in MIMO B using QAM64 1/2 bsdlmimobsixtyfourqamtwooverthreeslots Counter32 DL transmitted slots in MIMO B using QAM64 2/3 bsdlmimobsixtyfourqamthreeoverfourslots Counter32 DL transmitted slots in MIMO B using QAM64 3/4 bsdlmimobsixtyfourqamfiveoversixslots Counter32 DL transmitted slots in MIMO B using QAM64 5/6 bssoundingresourceutilization Gauge32 Not applicable for current release Sum of sounding decimations utilized. bssoundingtotalresource Gauge32 Not applicable for current release Sum of total sounding decimation available. Calculated as 900(sec) x 200(frames) x bssoundingnumberofdecimationoffset / 4. bsnumberofregisteredmss Gauge32 The average number of registered MSs during the collection period. bsnumberofidlemss Gauge32 Number of MSs that entered Idle mode. The counter will be increased any time an MS enters to Idle mode it will not be decreased when MS exits from Idle mode. This is required for Idle MSs averaging over the frames. bsnumberofnesuccess Counter32 Number of succeeded initial network entries bsnumberofnefailed Counter32 Number of failed initial networks entries bsmimoabursts Counter32 Number of bursts in MIMO A mode bsmimobbursts Counter32 Number of bursts in MIMO B mode bscddbursts Counter32 Number of bursts in CDD mode 8

15 Chapter 1 - Table 4: BS Traffic Performance Parameters - File Collection (Continued) Parameter Type Counts the Number of... bsbfbursts Counter32 Not applicable for current release Number of bursts in Beam Forming mode bsnumberofcreatedserviceflows Gauge32 Number of created service flows. Counter will be incremented by 1 for each new service flow. Counter will be decremented by 1 for each closed service flow. bsdlharqrepetitions Counter32 Number of DL HARQ repetitions bsdlharqharqacks Counter32 Number of DL HARQ ACKs bsdlharqharqnacks Counter32 Number of DL HARQ NACKs bsdlsuccessfullytransferredbursts Counter32 Number of DL successfully transferred bursts bsdldropbursts Counter32 Number of DL dropped bursts bsulharqrepetitions Counter32 Number of UL HARQ repetitions bsulharqharqacks Counter32 Number of UL HARQ ACKs bsulharqharqnacks Counter32 Number of UL HARQ NACKs bsulsuccessfullytransferredbursts Counter32 Number of UL successfully transferred bursts bsuldropbursts Counter32 Number of UL dropped bursts bssucceedhoattempts Counter32 Number of successful Hand Over attempts bsfailedhoattempts Counter32 Number of failed Hand Over attempts bsdlmimobrthreeqpskoneovertwoslots Counter32 Not applicable for current release. DL transmitted slots in MIMO B using QPSK 1/2 in reuse 3 region bsdlmimobrthreeqpskthreeoverfourslots Counter32 Not applicable for current release. DL transmitted slots in MIMO B using QPSK 3/4 in reuse 3 region bsdlmimobrthreesixteenqamoneovertwoslots Counter32 Not applicable for current release. DL transmitted slots in MIMO B using QAM16 1/2 in reuse 3 region bsdlmimobrthreesixteenqamthreeoverfourslots Counter32 Not applicable for current release. DL transmitted slots in MIMO B using QAM16 3/4 in reuse 3 region 9

16 Chapter 1 - Table 4: BS Traffic Performance Parameters - File Collection (Continued) Parameter Type Counts the Number of... bsdlmimobrthreesixtyfourqamoneovertwoslots Counter32 Not applicable for current release. DL transmitted slots in MIMO B using QAM64 1/2 in reuse 3 region bsdlmimobrthreesixtyfourqamtwooverthreeslots Counter32 Not applicable for current release. DL transmitted slots in MIMO B using QAM64 2/3 in reuse 3 region bsdlmimobrthreesixtyfourqamthreeoverfourslots Counter32 Not applicable for current release. DL transmitted slots in MIMO B using QAM64 3/4 in reuse 3 region bsdlmimobrthreesixtyfourqamfiveoversixslots Counter32 Not applicable for current release. DL transmitted slots in MIMO B using QAM64 5/6 in reuse 3 region bsdlmimoarthreeqpskoneovertwotimessixslots Counter32 Not applicable for current release. DL transmitted slots in MIMO A using QPSK 1/2 Repetition 6 in reuse 3 region bsdlmimoarthreeqpskoneovertwotimesfourslots Counter32 Not applicable for current release. DL transmitted slots in MIMO A using QPSK 1/2 Repetition 4 in reuse 3 region bsdlmimoarthreeqpskoneovertwotimestwoslots Counter32 Not applicable for current release. DL transmitted slots in MIMO A using QPSK 1/2 Repetition 2 in reuse 3 region bsdlmimoarthreeqpskoneovertwoslots Counter32 Not applicable for current release. DL transmitted slots in MIMO A using QPSK 1/2 in reuse 3 region bsdlmimoarthreeqpskthreeoverfourslots Counter32 Not applicable for current release. DL transmitted slots in MIMO A using QPSK 3/4 in reuse 3 region bsdlmimoarthreesixteenqamoneovertwoslots Counter32 Not applicable for current release. DL transmitted slots in MIMO A using QAM16 1/2 in reuse 3 region bsdlmimoarthreesixteenqamthreeoverfourslots Counter32 Not applicable for current release. DL transmitted slots in MIMO A using QAM16 3/4 in reuse 3 region 10

17 Chapter 1 - Table 4: BS Traffic Performance Parameters - File Collection (Continued) Parameter Type Counts the Number of... bsdlmimoarthreesixtyfourqamoneovertwoslots Counter32 Not applicable for current release. DL transmitted slots in MIMO A using QAM64 1/2 in reuse 3 region bsdlmimoarthreesixtyfourqamtwooverthreeslots Counter32 Not applicable for current release. DL transmitted slots in MIMO A using QAM64 2/3 in reuse 3 region bsdlmimoarthreesixtyfourqamthreeoverfourslots Counter32 Not applicable for current release. DL transmitted slots in MIMO A using QAM64 3/4 in reuse 3 region bsdlmimoarthreesixtyfourqamfiveoversixslots Counter32 Not applicable for current release. DL transmitted slots in MIMO A using QAM64 5/6 in reuse 3 region bsdlmimoaqpskoneovertwotimessixslots Counter32 DL transmitted slots in MIMO A using QPSK 1/2 Repetition 6 bsdlmimoaqpskoneovertwotimesfourslots Counter32 DL transmitted slots in MIMO A using QPSK 1/2 Repetition 4 bsdlmimoaqpskoneovertwotimestwoslots Counter32 DL transmitted slots in MIMO A using QPSK 1/2 Repetition 2 bsdlmimoaqpskoneovertwoslots Counter32 DL transmitted slots in MIMO A using QPSK 1/2 bsdlmimoaqpskthreeoverfourslots Counter32 DL transmitted slots in MIMO A using QPSK 3/4 bsdlmimoasixteenqamoneovertwoslots Counter32 DL transmitted slots in MIMO A using QAM16 1/2 bsdlmimoasixteenqamthreeoverfourslots Counter32 DL transmitted slots in MIMO A using QAM16 3/4 bsdlmimoasixtyfourqamoneovertwoslots Counter32 DL transmitted slots in MIMO A using QAM64 1/2 bsdlmimoasixtyfourqamtwooverthreeslots Counter32 DL transmitted slots in MIMO A using QAM64 2/3 bsdlmimoasixtyfourqamthreeoverfourslots Counter32 DL transmitted slots in MIMO A using QAM64 3/4 bsdlmimoasixtyfourqamfiveoversixslots Counter32 DL transmitted slots in MIMO A using QAM64 5/6 11

18 Chapter 1 - Table 4: BS Traffic Performance Parameters - File Collection (Continued) Parameter Type Counts the Number of... NumberOfUsersInR1 Counter32 Number of users in reuse 1 region NumberOfUsersInR3 Counter32 Not applicable for current release. Number of users in reuse 3 region Utilization Group Name (in XML file and MIB): pmbsutilizationtable Integrity Table 5: BS Utilization Performance Parameters - File Collection Parameter Type Description AllocatedSlotsMapZone Counter32 Number of slots allocated to the map zone (first zone) UsedSlotsMapZone Counter32 Average number of used slots in map zone (first zone) AllocatedSlotsDataZoneDl Counter32 Number of slots allocated to the Dl reuse 1 data zone, including slots unused when no demand UsedSlotsDataZoneDl Counter32 Average number of all used slots in Dl reuse 1 data zone AllocatedSlotsDataZoneUl Counter32 Average slots allocated to the Ul data zone, including slots unused when no demand. UsedSlotsDataZoneUl Counter32 Average number of all used slots in Ul data zone bscqichannelutilization Counter32 Number of CQI channels utilized bscqitotalchannel Counter32 For BS BW=10 or 7MHz: 900(sec) x 200(frames) x 168 / 8 Group Name (in XML file and MIB): pmbsintegrity. All Integrity performance parameters are of type Gauge32. For BS BW=5MHz: 900(sec) x 200(frames) x 56 / 8 bscqitotalmax Counter32 Total number of opened CQICH MIMO during the interval UsedSlotsDataZoneDlR3 Counter32 Not applicable for current release. Average number of all used slots in Dl reuse 3 data zone AllocatedSlotsDataZoneDlR3 Gauge32 Not applicable for current release. Number of slots allocated to the Dl reuse 3 data zone, including slots unused when no demand 12

19 Chapter 1 - Table 6: BS Integrity Performance Parameters - File Collection Parameter DlSinrPerUserHistogramMinus3dB DlSinrPerUserHistogramMinus1dB DlSinrPerUserHistogramPlus1dB DlSinrPerUserHistogramPlus3dB DlSinrPerUserHistogramPlus5dB DlSinrPerUserHistogramPlus7dB DlSinrPerUserHistogramPlus9dB DlSinrPerUserHistogramPlus11dB DlSinrPerUserHistogramPlus13dB DlSinrPerUserHistogramPlus15dB DlSinrPerUserHistogramPlus17dB DlSinrPerUserHistogramPlus19dB Description Counts number of MSs in both reuse 1 and reuse 3 regions for which the latest reported DL SINR is lower than -2dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in both reuse 1 and reuse 3 regions for which the latest reported DL SINR is between -2dB and 0dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in both reuse 1 and reuse 3 regions for which the latest reported DL SINR is between 0dB and2db. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in both reuse 1 and reuse 3 regions for which the latest reported DL SINR is between 2dB and 4dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in both reuse 1 and reuse 3 regions for which the latest reported DL SINR is between 4dB and 6dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in both reuse 1 and reuse 3 regions for which the latest reported DL SINR is between 6dB and 8dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in both reuse 1 and reuse 3 regions for which the latest reported DL SINR is between 8dB and 10dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in both reuse 1 and reuse 3 regions for which the latest reported DL SINR is between 10dB and 12dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in both reuse 1 and reuse 3 regions for which the latest reported DL SINR is between 12dB and 14dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in both reuse 1 and reuse 3 regions for which the latest reported DL SINR is between 14dB and 16dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in both reuse 1 and reuse 3 regions for which the latest reported DL SINR is between 16dB and 18dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in both reuse 1 and reuse 3 regions for which the latest reported DL SINR is between 18dB and 20dB. Counter is updated at the end of collection interval ("snapshot") 13

20 Chapter 1 - Table 6: BS Integrity Performance Parameters - File Collection (Continued) Parameter DlSinrPerUserHistogramPlus21dB DlSinrPerUserHistogramPlus23dB DlSinrPerUserHistogramPlus25dB ReceivedPwrHistogramNiMinus1dB ReceivedPwrHistogramNiPlus1dB ReceivedPwrHistogramNiPlus3dB ReceivedPwrHistogramNiPlus5dB ReceivedPwrHistogramNiPlus7dB ReceivedPwrHistogramNiPlus9dB ReceivedPwrHistogramNiPlus11dB ReceivedPwrHistogramNiPlus13dB ReceivedPwrHistogramNiPlus15dB Description Counts number of MSs in both reuse 1 and reuse 3 regions for which the latest reported DL SINR is between 20dB and 22dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in both reuse 1 and reuse 3 regions for which the latest reported DL SINR is between 22dB and 24dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in both reuse 1 and reuse 3 regions for which the latest reported DL SINR is higher than 24. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs for which the received power at the last received message is lower than NI. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs for which the received power at the last received message is lower than NI+2 and higher than NI. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs for which the received power at the last received message is lower than NI+4 and higher than NI+2. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs for which the received power at the last received message is lower than NI+6 and higher than NI+4. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs for which the received power at the last received message is lower than NI+8 and higher than NI+6. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs for which the received power at the last received message is lower than NI+10 and higher than NI+8. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs for which the received power at the last received message is lower than NI+12 and higher than NI+10. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs for which the received power at the last received message is lower than NI+14 and higher than NI+12. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs for which the received power at the last received message is lower than NI+16 and higher than NI+14. Counter is updated at the end of collection interval ("snapshot") 14

21 Chapter 1 - Table 6: BS Integrity Performance Parameters - File Collection (Continued) Parameter ReceivedPwrHistogramNiPlus17dB ReceivedPwrHistogramNiPlus19dB ReceivedPwrHistogramNiPlus21dB bsulnoisefloormediandbm bsulnoisefloor99percentiledbm DlSinrR3PerUserHistogramMinus3dB DlSinrR3PerUserHistogramMinus1dB DlSinrR3PerUserHistogramPlus1dB DlSinrR3PerUserHistogramPlus3dB DlSinrR3PerUserHistogramPlus5dB DlSinrR3PerUserHistogramPlus7dB DlSinrR3PerUserHistogramPlus9dB DlSinrR3PerUserHistogramPlus11dB Description Counts number of MSs for which the received power at the last received message is lower than NI+18 and higher than NI+16. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs for which the received power at the last received message is lower than NI+20 and higher than NI+18. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs for which the received power at the last received message is higher than NI+20. Counter is updated at the end of collection interval ("snapshot") The median value of the uplink noise floor histogram. Counter is updated and reset at the end of collection interval ("snapshot") The 99% value of the uplink noise floor histogram. Counter is updated and reset at the end of collection interval ("snapshot") Counts number of MSs in reuse 3 region for which the latest reported DL SINR is lower than -2dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in reuse 3 region for which the latest reported DL SINR is between -2dB and 0dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in reuse 3 region for which the latest reported DL SINR is between 0dB and 2dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in reuse 3 region for which the latest reported DL SINR is between 2dB and 4dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in reuse 3 region for which the latest reported DL SINR is between 4dB and 6dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in reuse 3 region for which the latest reported DL SINR is between 6dB and 8dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in reuse 3 region for which the latest reported DL SINR is between 8dB and 10dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in reuse 3 region for which the latest reported DL SINR is between 10dB and 12dB. Counter is updated at the end of collection interval ("snapshot") 15

22 Chapter 1 - Table 6: BS Integrity Performance Parameters - File Collection (Continued) Parameter DlSinrR3PerUserHistogramPlus13dB DlSinrR3PerUserHistogramPlus15dB DlSinrR3PerUserHistogramPlus17dB DlSinrR3PerUserHistogramPlus19dB DlSinrR3PerUserHistogramPlus21dB DlSinrR3PerUserHistogramPlus23dB DlSinrR3PerUserHistogramPlus25dB Description Counts number of MSs in reuse 3 region for which the latest reported DL SINR is between 12dB and 14dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in reuse 3 region for which the latest reported DL SINR is between 14dB and 16dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in reuse 3 region for which the latest reported DL SINR is between 16dB and 18dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in reuse 3 region for which the latest reported DL SINR is between 18dB and 20dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in reuse 3 region for which the latest reported DL SINR is between 20dB and 22dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in reuse 3 region for which the latest reported DL SINR is between 22dB and 24dB. Counter is updated at the end of collection interval ("snapshot") Counts number of MSs in reuse 3 region for which the latest reported DL SINR is higher than 24dB. Counter is updated at the end of collection interval ("snapshot") TxR1 Total Traffic Group Name (in XML file and MIB): pmbstxr1totaltraffictable. All TxR1 Total traffic parameters are of type Counter32. The TxR1 Total Traffic parameters count size (in bytes) of BS uplink allocations in reuse 1 region for transport connections in specific MCS, including MAC overhead (header, CRC, ARQ/HARQ retransmissions). They do not consider FCH, preamble, broadcast and management messages. Table 7: TxR1 Total Traffic Parameters - File Collection Parameter bstotalbytestxr1qpskoneovertwotimessix Description Counts size (in bytes) of BS uplink allocations in reuse 1 region for transport connections in QPSK 1/2 Repetition 6, including MAC overhead (header, CRC, ARQ/HARQ retransmissions). They do not consider FCH, preamble, broadcast and management messages. 16

23 Chapter 1 - Table 7: TxR1 Total Traffic Parameters - File Collection Parameter bstotalbytestxr1qpskoneovertwotimesfour bstotalbytestxr1qpskoneovertwotimestwo bstotalbytestxr1qpskoneovertwo bstotalbytestxr1qpskthreeoverfour bstotalbytestxr1qamsixteenoneovertwo bstotalbytestxr1qamsixteenthreeoverfour bstotalbytestxr1qamsixtyfouroneovertwo bstotalbytestxr1qamsixtyfourtwooverthree bstotalbytestxr1qamsixtyfourthreeoverfour Description Counts size (in bytes) of BS uplink allocations in reuse 1 region for transport connections in QPSK 1/2 Repetition 4, including MAC overhead (header, CRC, ARQ/HARQ retransmissions). They do not consider FCH, preamble, broadcast and management messages. Counts size (in bytes) of BS uplink allocations in reuse 1 region for transport connections in QPSK 1/2 Repetition 4, including MAC overhead (header, CRC, ARQ/HARQ retransmissions). They do not consider FCH, preamble, broadcast and management messages. Counts size (in bytes) of BS uplink allocations in reuse 1 region for transport connections in QPSK 1/2, including MAC overhead (header, CRC, ARQ/HARQ retransmissions). They do not consider FCH, preamble, broadcast and management messages. Counts size (in bytes) of BS uplink allocations in reuse 1 region for transport connections in QPSK 3/4, including MAC overhead (header, CRC, ARQ/HARQ retransmissions). They do not consider FCH, preamble, broadcast and management messages. Counts size (in bytes) of BS uplink allocations in reuse 1 region for transport connections in QAM16 1/2, including MAC overhead FCH, preamble, broadcast and management messages. Counts size (in bytes) of BS uplink allocations in reuse 1 region for transport connections in QAM16 3/4, including MAC overhead FCH, preamble, broadcast and management messages. Counts size (in bytes) of BS uplink allocations in reuse 1 region for transport connections in QAM64 1/2, including MAC overhead FCH, preamble, broadcast and management messages. Counts size (in bytes) of BS uplink allocations in reuse 1 region for transport connections in QAM64 2/3, including MAC overhead FCH, preamble, broadcast and management messages. Counts size (in bytes) of BS uplink allocations in reuse 1 region for transport connections in QAM64 3/4, including MAC overhead FCH, preamble, broadcast and management messages. 17

24 Chapter 1 - Table 7: TxR1 Total Traffic Parameters - File Collection Parameter bstotalbytestxr1qamsixtyfourfiveoversix Description Counts size (in bytes) of BS uplink allocations in reuse 1 region for transport connections in QAM64 5/6, including MAC overhead FCH, preamble, broadcast and management messages RxR1 Total Traffic Group Name (in XML file and MIB): pmbsrxr1totaltraffictable. All TxR1 Total traffic parameters are of type Counter32. The RxR1 Total Traffic parameters count size (in bytes) of BS downlink allocations in reuse 1 region for transport connections in specific MCS, including MAC overhead (header, CRC, ARQ/HARQ retransmissions). They do not consider feedback on and management messages. Table 8: RxR1 Total Traffic Parameters - File Collection Parameter bstotalbytesrxr1qpskoneovertwotimessix bstotalbytesrxr1qpskoneovertwotimesfour bstotalbytesrxr1qpskoneovertwotimestwo bstotalbytesrxr1qpskoneovertwo bstotalbytesrxr1qpskthreeoverfour Description Counts size (in bytes) of BS downlink allocations in reuse 1 region for transport connections in QPSK 1/2 Repetition 6, including MAC overhead (header, CRC, ARQ/HARQ retransmissions). They do not consider feedback on and management messages Counts size (in bytes) of BS downlink allocations in reuse 1 region for transport connections in QPSK 1/2 Repetition 4, including MAC overhead (header, CRC, ARQ/HARQ retransmissions). They do not consider feedback on and management messages Counts size (in bytes) of BS downlink allocations in reuse 1 region for transport connections in QPSK 1/2 Repetition 2, including MAC overhead (header, CRC, ARQ/HARQ retransmissions). They do not consider feedback on and management messages Counts size (in bytes) of BS downlink allocations in reuse 1 region for transport connections in QPSK 1/2, including MAC overhead feedback on and management messages Counts size (in bytes) of BS downlink allocations in reuse 1 region for transport connections in QPSK 3/4 Repetition 6, including MAC overhead (header, CRC, ARQ/HARQ retransmissions). They do not consider feedback on and management messages 18

25 Chapter 1 - Table 8: RxR1 Total Traffic Parameters - File Collection (Continued) Parameter bstotalbytesrxr1qamsixteenoneovertwo bstotalbytesrxr1qamsixteenthreeoverfour bstotalbytesrxr1qamsixtyfouroneovertwo bstotalbytesrxr1qamsixtyfourtwooverthree bstotalbytesrxr1qamsixtyfourthreeoverfour bstotalbytesrxr1qamsixtyfourfiveoversix Description Counts size (in bytes) of BS downlink allocations in reuse 1 region for transport connections in QAM16 1/2, including MAC overhead feedback on and management messages Counts size (in bytes) of BS downlink allocations in reuse 1 region for transport connections in QAM16 3/4, including MAC overhead feedback on and management messages Counts size (in bytes) of BS downlink allocations in reuse 1 region for transport connections in QAM64 1/2, including MAC overhead feedback on and management messages Counts size (in bytes) of BS downlink allocations in reuse 1 region for transport connections in QAM64 2/3, including MAC overhead feedback on and management messages Counts size (in bytes) of BS downlink allocations in reuse 1 region for transport connections in QAM64 3/4, including MAC overhead feedback on and management messages Counts size (in bytes) of BS downlink allocations in reuse 1 region for transport connections in QAM64 5/6, including MAC overhead feedback on and management messages TxR3 Total Traffic TxR3 Total Traffic parameters are not applicable for the current release. Group Name (in XML file and MIB): pmbstxr3totaltraffictable. All TxR3 Total traffic parameters are of type Counter32. The TxR3 Total Traffic parameters count for each MCS the size (in bytes) of BS uplink allocations for transport connections in reuse 3 region using the specific MCS, including MAC overhead (header, CRC, ARQ/HARQ retransmissions). They do not consider FCH, preamble, broadcast and management messages. 19

26 Chapter 1 - Table 9: TxR3 Total Traffic Parameters - File Collection Parameter bstotalbytestxr3qpskoneovertwotimessix bstotalbytestxr3qpskoneovertwotimesfour bstotalbytestxr3qpskoneovertwotimestwo bstotalbytestxr3qpskoneovertwo bstotalbytestxr3qpskthreeoverfour bstotalbytestxr3qamsixteenoneovertwo bstotalbytestxr3qamsixteenthreeoverfour bstotalbytestxr3qamsixtyfouroneovertwo bstotalbytestxr3qamsixtyfourtwooverthree Description Counts size (in bytes) of BS uplink allocations in reuse 3 region for transport connections in QPSK 1/2 Repetition 6, including MAC overhead (header, CRC, ARQ/HARQ retransmissions). They do not consider FCH, preamble, broadcast and management messages. Counts size (in bytes) of BS uplink allocations in reuse 3 region for transport connections in QPSK 1/2 Repetition 4, including MAC overhead (header, CRC, ARQ/HARQ retransmissions). They do not consider FCH, preamble, broadcast and management messages. Counts size (in bytes) of BS uplink allocations in reuse 3 region for transport connections in QPSK 1/2 Repetition 4, including MAC overhead (header, CRC, ARQ/HARQ retransmissions). They do not consider FCH, preamble, broadcast and management messages. Counts size (in bytes) of BS uplink allocations in reuse 3 region for transport connections in QPSK 1/2, including MAC overhead FCH, preamble, broadcast and management messages. Counts size (in bytes) of BS uplink allocations in reuse 3 region for transport connections in QPSK 3/4, including MAC overhead FCH, preamble, broadcast and management messages. Counts size (in bytes) of BS uplink allocations in reuse 3 region for transport connections in QAM16 1/2, including MAC overhead FCH, preamble, broadcast and management messages. Counts size (in bytes) of BS uplink allocations in reuse 3 region for transport connections in QAM16 3/4, including MAC overhead FCH, preamble, broadcast and management messages. Counts size (in bytes) of BS uplink allocations in reuse 3 region for transport connections in QAM64 1/2, including MAC overhead FCH, preamble, broadcast and management messages. Counts size (in bytes) of BS uplink allocations in reuse 3 region for transport connections in QAM64 2/3, including MAC overhead FCH, preamble, broadcast and management messages. 20

27 Chapter 1 - Table 9: TxR3 Total Traffic Parameters - File Collection (Continued) Parameter bstotalbytestxr3qamsixtyfourthreeoverfour bstotalbytestxr3qamsixtyfourfiveoversix Description Counts size (in bytes) of BS uplink allocations in reuse 3 region for transport connections in QAM64 3/4, including MAC overhead FCH, preamble, broadcast and management messages. Counts size (in bytes) of BS uplink allocations in reuse 3 region for transport connections in QAM64 5/6, including MAC overhead FCH, preamble, broadcast and management messages BS General Group Name (in XML file and MIB): pmbsgeneral. Table 10: BS General Parameters - File Collection Parameter Type Description bsbearerip ugauge32 BS bearer IP address bsofdmadownlinkcenterfreq ugauge32 BS center frequency, in KHz bsbw ugauge32 BS bandwidth, in KHz bssumallslots Counter32 Sum of all slots in all frames: DL & UL MAPs + DL data + UL feedback + UL data. Does not include: Preamble, Cell radius, TTG/RTG, DL Spare bssumdlslots Counter32 Sum of all slots in all DL sub frames: Usable DL slots for DL & UL MAPs + DL data. Does not include: Preamble, Cell radius, TTG/RTG, DL Spare. bssumpreambleslots Counter32 Sum of all slots used for DL preambles. Used symbols for preambles in 15min. bsdlbasicrate Gauge32 Downlink basic rate configured, in bits/slot bssumulslots Gauge32 Sum of all slots in all UL sub frames. Usable DL Slots in UL Data zone. Does not include Feedback zone. bsulbasicrate Gauge32 Uplink basic rate configured, in bits/slot. bssumrsvdslots Gauge32 Downlink slots reserved due to extended cell radius. Cell radius + DL Spare - in symbols bstotalmcastbytestxr1 Counter32 Total bytes broadcasted. All data on broadcast connections (DCD,UCD,NBR-ADV), in bytes. 21