FCC ID: XN3-QUANTUM6636 6x6 MIMO WiMAX Base Station

PureWave Quantum 6600 High performance, all outdoor Mobile WiMAX base stations PureWave Quantum 6600 User Guide v2.1

(ING -00006-001 Rev E) PureWave Quantum 6600 User Guide v2.1 PureWave Networks 2010. All rights reserved. PureWave Networks has prepared this manual for use by PureWave Networks personnel, licensees, customers, and customers of customers. The information contained herein is the property of PureWave Networks and shall neither be reproduced in whole nor in art without prior written approval from PureWave Networks. PureWave Networks reserves the right to make changes without notice to the specifications and materials contained herein, and shall not be responsible for any damages caused by reliance on the material presented, including, but not limited to, typographical, arithmetic and listing errors. Page 2 PureWave Quantum 6600 User Guide v2.1 Contents Contents ........................................................................................................................................................ 3 Figures ........................................................................................................................................................... 5 Tables ............................................................................................................................................................ 9 Regulatory Notice ....................................................................................................................................... 10 Safety Precautions ...................................................................................................................................... 11 1 Preface ................................................................................................................................................ 12 1.1 1.2 1.3 1.4 About This Document ................................................................................................................. 12 Symbols used in this Document .................................................................................................. 12 Locating the Product Serial Number ........................................................................................... 12 Obtaining Documentation and Support ...................................................................................... 13 2 PureWave Quantum Base Station Overview ...................................................................................... 14 2.1 2.2 2.3 Introduction - What is a Compact Base Station? ........................................................................ 14 PureWave Quantum at a Glance ................................................................................................ 15 A Closer Look ............................................................................................................................... 17 2.3.1 Ports and Indicators ............................................................................................................ 17 2.3.2 Radio and Physical Layer Specifications .............................................................................. 20 2.3.3 Capacity and Performance Characteristics ......................................................................... 24 2.3.4 Electro-Mechanical and Environmental Specifications....................................................... 25 3 Quick Start Guide ................................................................................................................................ 27 3.1 3.2 3.3 Preparing and Powering Up the Base Station ............................................................................. 27 Default Parameters ..................................................................................................................... 28 Logging in to the CLI .................................................................................................................... 28 3.3.1 Accessing the CLI via the Base Station Console Port........................................................... 29 3.3.2 Accessing the CLI via an Ethernet Port ................................................................................ 31 3.4 Logging in to the Web GUI Interface .......................................................................................... 32 3.4.1 Web Interface Configuration Key Concepts ........................................................................ 36 3.4.2 Web GUI CLI Access Level ................................................................................................... 45 3.5 Base Station Initial Configuration ............................................................................................... 52 Page 3 PureWave Quantum 6600 User Guide v2.1 3.5.1 System Architecture and Terminology................................................................................ 52 3.5.2 Base Station Management Interface and Access Parameters ............................................ 52 3.5.3 Base Station Configuration Parameters .............................................................................. 55 3.5.4 Connecting a Subscriber Station ......................................................................................... 98 3.5.5 Subscriber CPE Client Profiles ........................................................................................... 103 3.6 Base Station Software Upgrade ................................................................................................ 121 3.6.1 Single-Step Software Upgrade .......................................................................................... 123 3.6.2 Multi-Step Software Upgrade ........................................................................................... 125 3.6.3 Base Station Performance Monitoring ............................................................................. 129 Appendix A Capacity Tables ................................................................................................................. 163 Appendix B Limited Warranty Statements ........................................................................................... 166 Hardware .............................................................................................................................................. 166 Software ................................................................................................................................................ 166 Additional Conditions............................................................................................................................ 167 No Fault Found ...................................................................................................................................... 167 Warranty Limitations ............................................................................................................................ 167 Warranty Disclaimer ............................................................................................................................. 167 Obtaining Warranty Service .................................................................................................................. 168 Assistance.............................................................................................................................................. 169 Page 4 PureWave Quantum 6600 User Guide v2.1 Figures Figure 1: PureWave Quantum 6600 Base Station Mounted on Tower ................................................ 16 Figure 2: PureWave Quantum 6600 Base Station .............................................................................. 17 Figure 3: Quantum 6600 with Available Solar Shield ......................................................................... 26 Figure 4: PuTTY Serial Port Configuration Window ............................................................................ 29 Figure 5: Console Login..................................................................................................................... 30 Figure 6: Console Login Default Status .............................................................................................. 30 Figure 7: PuTTY SSH Client Configuration .......................................................................................... 31 Figure 8: Web GUI Interface Login Page ............................................................................................ 32 Figure 9: Main Web GUI Interface Screen .......................................................................................... 33 Figure 10: Main Web GUI Interface Window Refresh ......................................................................... 34 Figure 11: Web GUI Interface Web Main Menu Option ...................................................................... 34 Figure 12: Web GUI Interface HTTP Support ...................................................................................... 35 Figure 13: Web GUI Interface HTTP Support Edit Enabled .................................................................. 35 Figure 14: The Main Web GUI Interface Screen in View Mode ........................................................... 36 Figure 15: The Web GUI Interface Screen in Edit Private Mode .......................................................... 37 Figure 16: Configuration Changes Popup Window ............................................................................. 38 Figure 17: Revert Option .................................................................................................................. 38 Figure 18: Revert All Configuration Changes...................................................................................... 39 Figure 19: Rollback Option ............................................................................................................... 40 Figure 20: Validate Option ................................................................................................................ 40 Figure 21: Commit Option ................................................................................................................ 41 Figure 22: Commit Option Successful ................................................................................................ 42 Figure 23: Writing Running Configuration to Startup ......................................................................... 43 Figure 24: Writing Running Configuration to Startup Successful ......................................................... 43 Figure 25: Reboot Base Station ......................................................................................................... 44 Figure 26: Reboot Base Station Successful ........................................................................................ 44 Figure 27: The Tools Tab Menu Options ............................................................................................ 45 Figure 28: The Tools Tab Logs Menu ................................................................................................. 46 Figure 29: The Tools Tab System Log ................................................................................................. 47 Figure 30: The Tools Tab Alert Log .................................................................................................... 47 Figure 31: The Tools Tab Audit Log ................................................................................................... 48 Figure 32: The Tools Tab Accessories Menu ...................................................................................... 48 Figure 33: The Accessories Ping Command ........................................................................................ 49 Figure 34: The Accessories Ping Results ............................................................................................ 49 Figure 35: The Accessories CPU Load Results ..................................................................................... 50 Figure 36: The Tools Tab CLI ............................................................................................................. 50 Figure 37: The Tools Tab Users Connected to Base Station ................................................................ 51 Figure 38: The Tools Tab Users Instant Messaging ............................................................................. 51 Figure 39: Initial Connection to CLI ................................................................................................... 53 Page 5 PureWave Quantum 6600 User Guide v2.1 Figure 40: Base Station CLI Time ....................................................................................................... 54 Figure 41: Base Station CLI Initial Configuration ................................................................................ 54 Figure 42: Base Station CLI Hostname Change ................................................................................... 55 Figure 43: Base Station CLI Username Password Change ................................................................... 55 Figure 44: Sector Settings ................................................................................................................. 57 Figure 45: Sector General Options .................................................................................................... 58 Figure 46: Sector General Configuration Parameters ......................................................................... 59 Figure 47: Sector General Provisioning Parameters ........................................................................... 60 Figure 48: Sector External IP Address ................................................................................................ 61 Figure 49: Sector External IP Address Configuration .......................................................................... 61 Figure 50: Sector External IP Address Changed .................................................................................. 62 Figure 51: Sector External ASN Gateway Settings .............................................................................. 63 Figure 52: Sector External Radius Server Settings .............................................................................. 63 Figure 53: Sector External Radius Server Settings .............................................................................. 64 Figure 54: Sector Advanced Settings ................................................................................................. 65 Figure 55: Sector Configured WIMAX Settings ................................................................................... 65 Figure 56: Sector State WIMAX Settings ............................................................................................ 66 Figure 57: Sector WIMAX Settings Configuration ............................................................................... 66 Figure 58: Sector Radio Configured Settings ...................................................................................... 69 Figure 59: Sector Radio State Settings ............................................................................................... 69 Figure 60: Sector Radio Settings Configuration .................................................................................. 70 Figure 61 Contention Based Mode .................................................................................................... 71 Figure 62 OmniWave Settings ........................................................................................................... 71 Figure 63: Sector Security Settings .................................................................................................... 72 Figure 64: Sector Security Settings Configuration .............................................................................. 72 Figure 65: System Settings ................................................................................................................ 73 Figure 66: System External ASN Gateway Settings ............................................................................. 75 Figure 67 System Handover Trigger Setting ....................................................................................... 77 Figure 68 Neighbor configuration ..................................................................................................... 78 Figure 69: System Reset to Default Option ........................................................................................ 78 Figure 70: System Management Static IP Address ............................................................................. 79 Figure 71: System Base Station Inventory ......................................................................................... 79 Figure 72: GPS Settings and Status .................................................................................................... 80 Figure 73: Time Settings ................................................................................................................... 82 Figure 74: Time NTP Server Settings.................................................................................................. 83 Figure 75: Time NTP Server Configuration ......................................................................................... 83 Figure 76: Time NTP Server System Set ............................................................................................. 84 Figure 77: Time NTP Server Synchronization Update ......................................................................... 85 Figure 78: Telnet Server Enabled ...................................................................................................... 85 Figure 79: Web Server HTTP Support ................................................................................................ 86 Figure 80: Configuration Settings ...................................................................................................... 88 Figure 81: Configuration Copy Settings ............................................................................................. 89 Page 6 PureWave Quantum 6600 User Guide v2.1 Figure 82: Configuration Copy Successful .......................................................................................... 89 Figure 83: Configuration Move Settings ............................................................................................ 90 Figure 84: Configuration Delete Settings ........................................................................................... 91 Figure 85: Configuration Export Settings ........................................................................................... 92 Figure 86: Configuration Import Settings .......................................................................................... 93 Figure 87: Configuration Write Settings ............................................................................................ 94 Figure 88: Configuration Backup Settings .......................................................................................... 95 Figure 89: Configuration Restore Settings ......................................................................................... 95 Figure 90: Configuration Download Settings ..................................................................................... 96 Figure 91: Configuration Upload Settings .......................................................................................... 97 Figure 92: CPE Main Menu Option .................................................................................................... 98 Figure 93: Add Subscriber CPE Option ............................................................................................... 99 Figure 94: Add Subscriber CPE MAC Address ..................................................................................... 99 Figure 95: Add Subscriber CPE Settings ........................................................................................... 101 Figure 96: Add Subscriber CPE Validation ........................................................................................ 101 Figure 97: Add Subscriber CPE Commit ........................................................................................... 102 Figure 98: Subscriber CPE Configured Settings ................................................................................. 102 Figure 99: Subscriber CPE Delete .................................................................................................... 103 Figure 100: Subscriber CPE Provisioning Flow Concepts ................................................................... 103 Figure 101: Typical Best Effort Client Profile .................................................................................... 105 Figure 102: Typical Voice and Data Client Profile ............................................................................. 105 Figure 103: Service Profile Menu Option ......................................................................................... 106 Figure 104: Service Profile Classifier Profile ..................................................................................... 108 Figure 105: Service Profile Classifier Profile Edit Capability .............................................................. 110 Figure 106: Service Profile HARQ Profile ......................................................................................... 111 Figure 107: Service Profile HARQ Profile Edit Capability .................................................................. 112 Figure 108: Service Profile ARQ Profile ............................................................................................ 112 Figure 109: Service Profile ARQ Profile Edit Capability ..................................................................... 114 Figure 110: Default Quality of Service Profiles ................................................................................. 115 Figure 111: Quality of Service Profiles ............................................................................................. 116 Figure 112: Quality of Service Edit Capability .................................................................................. 117 Figure 113: Client Profile ................................................................................................................ 118 Figure 114: Client Profile Edit Capability ......................................................................................... 119 Figure 115: Client Profile Edit Full Capability ................................................................................... 120 Figure 116: Software Components .................................................................................................. 121 Figure 117: FTP Server Configuration .............................................................................................. 122 Figure 118: Software Image Management Dialog ............................................................................ 123 Figure 119: Single-Step Software Upgrade Dialog ............................................................................ 124 Figure 120: Software Download and Installation Dialog .................................................................. 126 Figure 121: Software Partition Selection and Display ....................................................................... 127 Figure 122: Software Image Partition Selection ............................................................................... 128 Figure 123: Performance Monitoring Interface ................................................................................ 129 Page 7 PureWave Quantum 6600 User Guide v2.1 Figure 124: Interface Status Key Settings and Status ....................................................................... 130 Figure 125: Sector Settings ............................................................................................................. 131 Figure 126: Sector Statistics Interface Key Settings .......................................................................... 132 Figure 127: Sector Statistics Interface Key Settings .......................................................................... 133 Figure 128: Sector Statistics Packet Error Rate Metrics .................................................................... 134 Figure 129: Sector Statistics Startup Counters ................................................................................. 135 Figure 130: Sector Statistics Throughput Counters .......................................................................... 135 Figure 131: Sector MSS-Statistics Metrics ........................................................................................ 136 Figure 132: Sector Statistics MSS Throughput Counters ................................................................... 137 Figure 133: Sector Statistics Service Flow Throughput Counters ....................................................... 138 Figure 134: Sector Statistics Downlink RSSI CINR Metrics ................................................................ 139 Figure 135 Sector Statistics Upstream RSSI CINR Metrics ................................................................. 140 Figure 136: Sector Statistics HARQ Counters ................................................................................... 141 Figure 137: Sector Statistics Modulation Code Counters .................................................................. 142 Figure 138: Sector Statistics Active Service Flows ............................................................................ 143 Figure 139: Sector Statistics Registered SS ...................................................................................... 144 Figure 140: Main Menu Logging Options ......................................................................................... 144 Figure 141: Logging Remote Host Information ................................................................................ 146 Figure 142: Logging Local Information............................................................................................. 147 Figure 143: Logging Local Override ................................................................................................. 147 Figure 144: Logging File Information ............................................................................................... 148 Figure 145: Logging File Rotation .................................................................................................... 149 Figure 146: Logging File Delete ....................................................................................................... 150 Figure 147: Logging File Upload ...................................................................................................... 151 Figure 148: Logging Files Filenames ................................................................................................ 151 Figure 149: Logging Files System Information .................................................................................. 152 Figure 150 snmp-server configuration ............................................................................................. 153 Figure 151 Community sub-menu ................................................................................................... 154 Figure 152 snmpCommunityEntry Table.......................................................................................... 155 Figure 153 SNMP user configuration ............................................................................................... 156 Figure 154 SNMP user configuration continued ............................................................................... 156 Figure 155 SNMP Notify Configuration ............................................................................................ 157 Figure 156 SNMP Trap Destination ................................................................................................. 158 Figure 157 Trap Destination Configuration Parameters ................................................................... 159 Figure 158 Trap Destination Configuration Parameters continued ................................................... 159 Figure 159 Alarm Management ...................................................................................................... 161 Figure 160 Alarm Action ................................................................................................................. 162 Page 8 PureWave Quantum 6600 User Guide v2.1 Tables Table 1: Base Station Connector Descriptions ................................................................................... 18 Table 2: Base Station LED Description ............................................................................................... 19 Table 3: Radio and PHY Specifications ............................................................................................... 20 Table 4: Typical Rx Sensitivity ........................................................................................................... 21 Table 5: EIRP Calculations ................................................................................................................. 22 Table 6: Performance Characteristics ................................................................................................ 24 Table 7: Environmental and Mechanical Specifications ...................................................................... 25 Table 8: Base Station Management Interface and Access Default Parameters .................................... 28 Table 9: Console Port Settings .......................................................................................................... 29 Table 10: Base Station Management Interface and Access Parameters .............................................. 52 Table 11: Base Station Sector Configuration Data .............................................................................. 56 Table 12 SNMP Notification Table .................................................................................................. 157 Table 13 SNMP Target Address Table .............................................................................................. 160 Table 14: Max Throughput - 35:12 - 74%:26%.................................................................................. 163 Table 15: Max Throughput - 32:15 68%:32% ................................................................................. 163 Table 16: Max Throughput 29:18 - 62%:38% ................................................................................. 164 Table 17: Max Throughput 26:21 - 55%:45% ................................................................................. 164 Table 18: Max Throughput 21:12 - 64%:36% ................................................................................. 164 Table 19: Max Throughput 23:9 - 72%:28% ................................................................................... 164 Table 20: Max Throughput 17:15 - 53%:47% ................................................................................. 165 Table 21: Summary of PureWave RMA Conditions and Charges ....................................................... 169 Page 9 PureWave Quantum 6600 User Guide v2.1 Regulatory Notice This device complies with the FCC limits a class B digital device, pursuant to Part 15 of the FCC Rules. A complete list of regulatory certifications can be provided by PureWave upon request. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

Re-orient or relocate the receiving antenna/s. Increase the separation between the equipment and other receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. Shielded cables and I/O cords must be used for this equipment to comply with the relevant FCC regulations. Changes or modifications not expressly approved in writing by PureWave Networks may void the user's authority to operate this equipment. The 2.3, 3.3 and 3.5 GHz products have the CE (European Conformity) Mark. Note: This device must be professionally installed, and the operator and/or the licensed spectrum holder have the responsibility to comply with FCC regulations. Note: The contention protocol MUST be turned on and used for the specified band (3.65GHz

- 3.7 GHz) in the specified country or wherever FCC rules and regulations are enforced. Failure to comply makes the operation of this device illegal. Page 10 PureWave Quantum 6600 User Guide v2.1 Safety Precautions When operating or installing this equipment, please observe the following precautions to minimize the risk of danger or personnel injury:

NEVER install equipment if there is a chance of lightning or other adverse weather conditions. NEVER install equipment in a wet location unless the equipment is specifically design for wet locations. NEVER touch un-insulated wires or terminals unless the wire has been disconnected from any equipment. ALWAYS use caution when installing or modifying cables. ALWAYS disconnect all lines and power connections before servicing or disassembling this equipment. ALWAYS assume that all components and assemblies are static sensitive and always follow local ESD-prevention guidelines to prevent equipment damage. For any external power supply that provides the power source for the PureWave equipment, replace any power supply fuse with the same rating or equivalent; otherwise PureWave Networks cannot not be responsible for any subsequent damage to the equipment. For performance and safety reasons, only power supplies listed for use with telephone equipment by a Nationally Recognized Testing Laboratory (NRTL) should be used with equipment. ALL wiring external to the product(s) should follow the provisions of the current edition of the National Electrical Code. These units contain no user serviceable components. Only authorized service personnel should service or repair these units. Use only isolated Class 2 Power Source, Rated 48V dc 5.0A Minimum. Page 11 PureWave Quantum 6600 User Guide v2.1 1 Preface 1.1 About This Document The purpose of this User Guide is to quickly familiarize the user with the PureWave Quantum 6000 family of Base stations, their initial setup, and provisioning. It is not intended to be a comprehensive reference for the product and all its capabilities, nor does it cover in depth provisioning, operation, or administration using the PureView Network Management System or the PureWave Quantum Command-Line Interface. Please refer to their respective user guides for more in-depth coverage of those tools. Please also note that this guide does not cover the physical installation of the product, but rather assumes that the Base station has been fully installed and is ready to be powered on. Please refer to the PureWave Quantum 6600 Installation Guide for detailed professional installation guidelines. Always refer to the current set of Release Notes for the most up to date information and a description of the current features as they relate to the PureWave system. These may be different from and supersede the information contained within this Installation Guide. 1.2 Symbols used in this Document Notes, cautions and timesavers use these conventions and symbols:

Tip Note Means the following will help you solve a problem. The tips information might not be troubleshooting or even an action, but could be useful information. Means reader take note. Notes contain helpful suggestions or references to materials not contained in this manual. Caution Means reader be careful. In this situation, you might do something that could result equipment damage or loss of data. Warning This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. 1.3 Locating the Product Serial Number The product identification information, serial number, and certification information are located on a label on the side panel of the Base station. Please take note of and keep this information for your records, as it is very important for warranty and support services. Page 12 PureWave Quantum 6600 User Guide v2.1 1.4 Obtaining Documentation and Support All requests for documentation and/or support should be addressed to Technical Support Department PureWave Networks, Inc. 2660-C Marine Way Mountain View, CA 94043 E-mail: support@pwnets.com Tel: 650-528-5200 Fax: 650-528-5222 Page 13 PureWave Quantum 6600 User Guide v2.1 2 PureWave Quantum Base Station Overview 2.1 Introduction - What is a Compact Base Station?

At PureWave, we believe that true broadband data networks must roll out in a completely different manner than the traditional, low-throughput cellular networks of yesterday. The traditional cellular network paradigm of colossal macro Base stations and large cell radii developed from the need for high-coverage networks to carry low-bandwidth voice and messaging traffic. However, as the demand for data-based applications has grown, networks have quickly become congested, necessitating new wireless standards designed specifically for high-speed broadband data. Furthermore, as spectrum is always a scarce and expensive resource, the need for improved frequency re-use techniques has become more important than ever. The clear solution to this is higher-efficiency wireless standards, such as IEEE 802.16e Mobile WiMAX, and more flexible cell sizes. Where medium and high population density exists, cell sizes should be small to enable increased spectral re-use, thereby ensuring that each subscriber enjoys a sufficient amount of throughput. In such cases it may be necessary to deploy Base stations on utility poles, flag poles, rooftops, small buildings and walls. This necessitates small, pleasant form-factor Base stations that can accept a variety of antenna types, both omni-directional and directional. Such Base stations are often referred to as Pico. Because wired backhaul may not always be available in some such locations, it also suggests the need for wireless backhaul options. On the other hand, in rural areas with lower population densities, it makes more economic sense to deploy fewer Base stations on higher towers or buildings and usually with higher transmit power. This is closer to the traditional cellular approach and typically involves large, expensive and power-hungry macro or micro Base stations, often with split designs requiring both indoor and tower-top electronics. Wherever indoor components are required an operator must obtain an air-conditioned shelter, which adds significantly to the continual operating expenditures of such a deployment and limits the deployment location. PureWave has taken a revolutionary approach in the development of exclusively Compact Base stations. A compact Base station shares the similar form-factor and cost of a Pico Base station, but with the performance of a Macro Base station. It is a zero-footprint device that can be fully co-located with its antennas. It is the best of all worlds and can be flexibly deployed in Pico, Macro, and Micro type deployments. Welcome to the Revolution!

Page 14 PureWave Quantum 6600 User Guide v2.1 2.2 PureWave Quantum at a Glance The PureWave Quantum Family of Compact Mobile WiMAX Base Stations is PureWaves 3rd generation Base station platform and we believe it presents what is simply the most advanced and high-performing, yet cost-effective Base station solution available. The PureWave Quantum Family of Base stations currently consists of the 2x4 (2 Transmit, 4 Receive) Quantum 1000, the 3 x 2 x 2 Quantum 2200 and the PureWave Quantum 6600 (6x6) products. This Users Guide covers the PureWave Quantum 6600 products, with models differentiated by only the frequency variant which is represented by the two right digits. For example, the PureWave Quantum 6625 is the 2.5GHz variant, supported 2.5-2.7GHz. Otherwise they are functionally identical. In this guide we will, without loss of generality, refer primarily to the PureWave Quantum 6600 product, which is synonymous to writing PureWave Quantum 66xx. Please note that not all Quantum models are available in all markets. Please contact your sales representative for additional information and ordering options. The PureWave Quantum Family of Base station products is fully 802.16e (Mobile WiMAX) compliant and designed to interoperate seamlessly with standard, off-the-shelf, WiMAX-certified subscriber devices. All PureWave Quantum products feature a software-defined radio (SDR) architecture that allows them to continuously evolve and take on new features as they become available. Some of the key highlights of the PureWave Quantum Family of products include the following:

Superior Range An antenna array of up to 6 antennas operated in concert creates tightly focused radio beams that extend the range of each Base station by up to 40% or boost capacity where required. Spectral Re-use Sophisticated interference mitigation techniques coupled with advanced beamforming technology, both made possible by PureWaves multiple antenna architecture, allow for simple network deployments and for improved spectral re-use. Software Defined Radio Protects your investment through support for overtheair, field upgrades of existing networks as standards evolve and new features and capabilities are released. Completely Weatherproof PureWave Quantum Base stations do not require shelter and can be installed completely outdoors. This eliminates the capital cost of building a shelter and the recurring cost of leasing or running an air-conditioned site. Flexibly Mount Virtually Anywhere PureWave Quantum Base stations can be deployed on towers, utility poles, walls, rooftops, etc, without the need for remote RF heads. ASN-GW Optional PureWave Quantum Base stations can operate with or without an ASN-GW, making even small deployments affordable. PureWave Quantum Base stations can utilize virtually any off the shelf antennas, both omni-directional and sectored. However, PureWave recommends our own line of affordable, compact, multi-antenna panels designed specifically to complement the performance of our Base stations. Page 15 PureWave Quantum 6600 User Guide v2.1 PureWave Quantum Base Stations can be installed indoors or outdoors, however the antennas must always be installed outdoors. Figure 1 shows a PureWave Quantum 6600 Base station co-located on a tower with a PureWave 6-Port Antenna Panel. Figure 1: PureWave Quantum 6600 Base Station Mounted on Tower PureWaves carrier-grade solution includes the full-featured and highly scalable PureView NMS

(Network Management System), which can efficiently and powerfully provision and manage all Base station and Subscriber Stations in the access network. PureView features include automatic discovery, fault management, inventory tables, configuration, and performance management. PureView utilizes full open standard SNMP on the access network side, and employs a full-featured northbound interface for connection to virtually any existing NMS. In addition to the PureView NMS, all PureWave Quantum Base Stations support a full-featured Command Line Interface (CLI) and an integrated Web Interface. Please refer to the PureView NMS User Guide and the CLI User Guide for in depth coverage of those applications. Page 16 PureWave Quantum 6600 User Guide v2.1 2.3 A Closer Look The PureWave Quantum 6600 Base Station is a single, weather-resistant enclosure with overall dimensions 17.5 x 16.7 x 5.3 (44cm x 42cm x 13cm). The Base station is a single self-contained unit. Note that the PureWave Quantum 6600 Base Station has no user-serviceable components. PureWave Quantum products employ a sophisticated and flexible hardware architecture that combines general purpose processors, and application-specific hardware. Together these components deliver the processing power required to realize the high-performance required by todays demanding applications, while yielding the flexibility to support future functionality as needs arise. 2.3.1 Ports and Indicators The PureWave Quantum 6600 connector panel is shown in figure 2. The products flexible architecture allows for a number of product variants to suite almost limitless deployment needs. The model shown includes six antenna ports, two CAT-5 Gigabit Ethernet backhaul ports, and a DC power connector. Single or Multi-Mode Fiber backhaul and AC power options are also available. As the configuration of individual Base station models varies, so will the appearance of the connector panel. All PureWave Quantum Base stations include a serial (RS-232) console port, a GPS antenna connector, a ground terminal, and three high-intensity LEDs. Figure 2: PureWave Quantum 6600 Base Station Page 17 PureWave Quantum 6600 User Guide v2.1 Note that Installation and weatherproofing must be completed by a professional installer. Please refer to the PureWave Quantum 6000 Base Station Installation Guide for detailed instructions. The function of each Base station connector/port is described in Table 1. Note that every connector present must be terminated to ensure proper Base station operation. Please refer to the PureWave Quantum 6600 Installation Guide for comprehensive installation procedures. Connector PWR GND GPS ETH-1 ETH-2 CONSOLE ANT 1-6 Function

-48VDC power source inputs for the unit. DC power connector: LTW BB-04PMMS-LC7001 (chassis), LTW BB-04BFFA-LL7001

(mate) This M5 screw provides a ground connection point to the Base Station. It is the installers responsibility to ensure that the unit is professionally grounded and complies with all relevant local codes. N-type connector for mandatory external GPS antenna. 3.3V power on center pin. This Gigabit Ethernet port serves as the data traffic backhaul Interface and also provides for in-band management of the Base Station. Note that this port may be physically routed directly to the operators network equipment, or it may be daisy-chained through additional PureWave Quantum sectors by routing it to another units ETH-2 port. Cat-5 (RJ-45), Single-Mode Fiber (HartingPull/Han 3 A), and Multi-Mode (LC duplex) Fiber options are available for the ETH-1 port. This Gigabit Ethernet port serves as an incoming daisy-chain port from a neighboring sector, and may be used for out-of-band management of the Base Station. It may also be used to connect to an external device, such as a web camera. Daisy-chained traffic is aggregated and passed through the ETH-1 port. Cat-5 (RJ-45), Single-Mode Fiber (HartingPull/Han 3 A), and Multi-Mode (LC duplex) Fiber options are available for the ETH-2 port. RJ-45 based RS-232 port for CLI control via a console. Defaults settings are 38400, 8 data bits, 1 stop bit, no parity bits, no flow control. N-type Tx / Rx Antenna Ports. Table 1: Base Station Connector Descriptions Page 18 PureWave Quantum 6600 User Guide v2.1 The Base Stations three high-intensity LEDs are intended to be viewable from the ground for quick confirmation of the units operational state. Table 2 describes the function of each indicator. Note that the LEDs can be turned off by the operator using the PureView NMS, the Web Interface, or the Base Stations command-line interface. LED STATUS LINK POWER Function Green - BS is up and running normally. No faults detected. Blinking Red System booting up, or system is temporarily down. Solid Red - Fault detected. Off LEDs disabled or Power is off. Fault detected if POWER LED is Green, but STATUS LED is Off.

(Status LED for ETH-1 Gigabit Ethernet Port) Solid Green Connected to an Ethernet switch. Blinking Green Ethernet packet activity. Off LEDs disabled or no Ethernet activity detected. Green Power is being supplied to the BS. Off LEDs disabled or no power is being supplied to the BS. Table 2: Base Station LED Description Page 19 PureWave Quantum 6600 User Guide v2.1 2.3.2 Radio and Physical Layer Specifications The PureWave Quantum Family of Base Stations is available in several models to support a variety of frequency bands and the regulatory requirements of a number of countries. Because several deployment-specific variables (e.g., antenna type, cable type and length, settings, etc) can affect the effective power output and other characteristics of the system, it is the customers responsibility to assure that each deployment of this product meets applicable regulations. The PureView NMS, the Web UI, and the CLI all provide guidelines and feedback to ensure an appropriate installation. Table 3 lists key radio-related specifications of PureWave Quantum Base Stations. Note that additional features, not listed, may be released in future software revisions. Parameter Specification Frequency Bands Channel Sizes Duplex Method DL:UL Ratios Number of Tx/Rx Antennas Tx Power per Antenna Permutation Modulation XX23: 2.3-2.4GHz XX25: 2.496-2.69GHz XX33: 3.3-3.4GHz XX35: 3.4-3.6GHz XX36: 3.6-3.8GHz, including 3.65GHz US 5, 7,10 MHz TDD 35:12, 29:18, 32:15, 26:21 (5MHz and 10MHz) 23:9, 21:12, 17:15 (7MHz) Up to 6 Tx, 6 Rx for Quantum 6600 series 33dBm (RMS data power at maximum MCS level, measured at each external antenna connector of the Base Station) PUSC QPSK-1/2, QPSK-3/4 16QAM-1/2, 16QAM-3/4 64QAM-1/2, 64QAM-2/3, 64QAM-3/4, 64QAM-5/6 Data Repetition Coding QPSK-1/2 Repetition 2, 4, 6 MAP Repetition Smart Antenna Capabilities Air Link Optimization 1, 2 Beamforming, MIMO Matrix A, MIMO Matrix B, Cyclic Delay Diversity, MRC HARQ, CTC Table 3: Radio and PHY Specifications Page 20 PureWave Quantum 6600 User Guide v2.1 2.3.2.1 Receiver Sensitivity Table 4 presents typical receiver sensitivity specs of the Quantum 6600 Base Station. Note that sensitivity will be correspondingly less on models with fewer than 6 antennas. Note that the values presented are measured over the entire channel bandwidth, as opposed to WiMAX Radio Conformance Test (RCT) type measurements, which are measured over only a fraction of the channel bandwidth. Typical 6-Ant Rx Sensitivity AWGN, 10-6 BER, Full Band, in dBm UL MCS (CTC) QPSK-1/2 QPSK-3/4 16QAM-1/2 16QAM-3/4 64QAM-1/2 64QAM-2/3 64QAM-3/4 64QAM-5/6 5MHz

-105.0

-102.0

-99.8

-96.1

-95.1

-90.9

-90.2

-87.0 10MHz

-102.0

-99.0

-96.8

-93.1

-92.1

-87.9

-87.2

-84.0 Table 4: Typical Rx Sensitivity 2.3.2.2 Computing EIRP Power Effective Isotropic Radiated Power (EIRP) refers to the transmit power radiating out of the antenna. The accurate computation of EIRP is essential to proper network planning and to ensuring that the system meets local and regional maximum power regulations. As indicated in Table 3, the average Tx power output at each Base Station antenna connector is 33dBm. The average EIRP per antenna is computed as follows:

Ave EIRP per Ant (in dBm) = Ave Tx Pwr per Ant + Ant Gain Cable and Connector Loss For example, if deployed with a 14dBi antenna connected to the Base Station with only a few feet of cable, the average EIRP per Antenna might be 33dBm + 14dBi 1dB = 46dBm. The total average EIRP of the Base Station with all antennas combined can then be computed as follows:

Total Ave EIRP (in dBm) = Ave EIRP per Ant + 10log (Number of Antennas) For a 6 antenna Base Station, the example above yields Total Ave EIRP = 46dBm + 7.78dB = 53.78dBm. Page 21 PureWave Quantum 6600 User Guide v2.1 Note that some regulations refer to peak power, which in a WiMAX system is normally as much as 10dB higher than average power. In the case of the PureWave Quantum products the peak power can be assumed to be 9dB higher than average. Therefore, Peak EIRP should be computed as follows:

Peak EIRP per Ant (in dBm) = Ave EIRP per Ant + 9dB. Total Peak EIRP (in dBm) = Total Ave EIRP + 9dB. For the above example, Peak EIRP per Ant = 46dBm + 9dB = 54dBm and Total Peak EIRP = 53.78dBm +

9dB = 62.78dBm. These equations are summarized in Table 5. EIRP Metric Formula Ave EIRP per Ant (in dBm)

= Ave Tx Pwr per Ant + Ant Gain Cable and Connector Loss Total Ave EIRP (in dBm)

= Ave EIRP per Ant + 10log(Number of Antennas) Peak EIRP per ant (in dBm) = Ave EIRP per Ant + 9dB Total Peak EIRP (in dBm)

= Total Ave EIRP + 9dB Table 5: EIRP Calculations Note that some regulations are specified for particular channel bandwidths and/or antenna beamwidth and in such cases the allowable power should be scaled accordingly. As with the previous calculations, each case is often unique. Although the PureView NMS provides guidance and limits where known regional regulations apply, it is ultimately the responsibility of the spectrum holder to assure that appropriate limits are set. Page 22 PureWave Quantum 6600 User Guide v2.1 2.3.2.3 Smart Antenna Capabilities Beamforming is a technique that combines and focuses signals to and from multiple antennas to improve both downlink and uplink performance. On the uplink, the Base Station combines signals received on its multiple antennas, resulting in substantial link budget gains that improve range and throughput. Maximum Ratio Combining (MRC) and Minimum Mean-Square Error (MMSE) are basic techniques from which more sophisticated uplink processing techniques (such as interference mitigation) are built. On the downlink (Base Station to Subscriber Station), sophisticated digital signal processing algorithms exploit information gathered during the uplink beamforming process to concentrate the transmitted RF energy from the antenna array to the exact subscriber stations locations, improving gain, efficiency and signal to noise ratio (SNR), resulting in greater range and throughput. MIMO Matrix A utilizes a technique called space-time coding (STC), which exploits the spatial diversity of the channel to improve downlink performance. By improving data reception, it can increase range and maximize the utilization of available sector capacity. MIMO Matrix B utilizes a technique called spatial multiplexing (SM), in which multiple streams of data are simultaneously transmitted through multiple antennas and effectively separated by the receiving device. This technique can actually increase the spectral efficiency and, hence, the capacity of a system. The effectiveness of MIMO relies upon the spatial diversity inherent within the channel as well as other factors, and therefore a given technique may be more appropriate for certain users or deployments. Fortunately, PureWave Quantum Base Stations make these decisions automatically, maximizing the efficiency of your valuable spectrum. Cyclic Delay Diversity (CDD) is a technique employed by PureWave Quantum Base stations to allow the power of multiple antennas to be combined in transmitting a single stream of data even when MIMO or beamforming cannot be supported (e.g., when transmitting the MAP). Page 23 PureWave Quantum 6600 User Guide v2.1 2.3.3 Capacity and Performance Characteristics Table 6 summarizes key upper layer and overall performance characteristics of PureWave Quantum Base Stations. Note that some features may not be currently available, but are planned for future software releases. In addition, detailed throughput tables for each DL:UL ratios are presented in Appendix B. Parameter Active Users Service Flows Per User Peak Throughput QoS Convergence Sublayer Security Management Core Network Interface Specification 200 16 Aggregate: Up to 50Mbps DL: Up to 43Mbps UL: Up to 20Mbps BE, UGS, ErtPS, nrtPS, rtPS IP-CS, Eth-CS, IPv4, IPv6 Pass-Through AES-128, EAP-TLS, EAP-TTLS, PKMv2 PureView NMS / EMS, Remote CLI, Web Interface, SNMP v2c, SNMPv3 R6 (NWG 1.2.2, NWG 1.3.1), Radius Table 6: Performance Characteristics Page 24 PureWave Quantum 6600 User Guide v2.1 2.3.4 Electro-Mechanical and Environmental Specifications All PureWave Quantum Family Base Stations consist of a single, all-in-one, fully weatherproof unit that may be installed entirely outdoors or indoors, as dictated by each deployment. Please refer to the PureWave Quantum Base Station Installation Guide for detailed installation instructions and guidelines. Table 7 lists the mechanical, electrical, and environmental properties of the PureWave Quantum 6600 Base Station. Physical & Environmental Specifications Dimensions Weight Power Temperature Humidity Altitude 17.5 x 16.7 x 5.3

(44cm x 42cm x 13cm) 32lbs (14.5kg) (does not include mounting hardware)

-48 VDC (150 Watts Max)

-40C to +55C (ETSI EN 300 019-1.4 Class 4.1E) Note: An available solar shield is required for ambient temperatures exceeding +45C with full sun exposure. 5-100% non-condensing To 10,000 ft above sea level Surge Protection UL497B Lightning Protection Min 10kA IEC 6100-4-5 (optional via external kit) Weatherproofing IEC IP67 Wind Loading 160Km/hr operation, 200Km/hr survival Lightning Protection Min 10kA IEC 6100-4-5 (optional via external kit) Safety and IEC IP EN 300 019-2-2, GR487, IEC 60529 Vibration and Dust ETSI EN 300 019-1-4 Class 4.1E Table 7: Environmental and Mechanical Specifications For temperatures above +45 degrees C in direct sunlight it is necessary to deploy the Base Station with the available solar shield, shown in Figure 3. Again, details can be found in the PureWave Quantum 6600 Base Station Installation Guide. Page 25 PureWave Quantum 6600 User Guide v2.1 Figure 3: Quantum 6600 with Available Solar Shield Page 26 PureWave Quantum 6600 User Guide v2.1 3 Quick Start Guide This section describes how an Operator may power-up the PureWave Base Station and verify proper system initialization and configuration. There are two methods by which a PureWave Quantum Base Station may be configured and/or managed. This can be achieved via either a graphical user interface

(GUI) Web Interface or a command line interface (CLI). Each interface has the capability of configuring all parameters available in the Base Station. It is generally recommended to configure using the CLI for the first initial configuration of the Base Station or in the event that the Base Station management interface parameters are not known. PureWave thereafter recommends using the Web Interface for all configuration parameters. Note that the Web Interface and the CLI utilize the same terminology, parameter names, etc. 3.1 Preparing and Powering Up the Base Station Before powering on the Base Station it is critical that all of its connector panel ports be properly connected or terminated per the detailed instructions in the PureWave Quantum 6600 Installation Guide. Failure to do so may result in damage to the Base station. The procedures in this section assume the following connections have been to the Base Station:

Antenna's have be connected to each Base Station ANT (ANT 1 through ANT 6) ports. A GPS antenna is properly installed and attached to the Base Station GPS port. The ETH-1 port is connected to an accessible network via a router or other mechanism. An appropriate cable has been connected to the Console port. To connect to the Console port, the User will need the following hardware that is provided with the Base Station installation kit. These are as follows:

RJ45 cable. DB9 male connector (Network Adapter). DB9 female to DB9 female adapter. The adaptor should be connected to a straight-through serial cable. Do not use a Cisco rollover cable or a null modem serial cable as these are not supported. Please see the PureWave Quantum 6600 Installation Guide for more details. Optional: Serial to USB connector. Most laptop nowadays comes with USB connection instead of serial connection. If the PC/laptop has a DB9 serial connection then there is no requirement for a USB adapter. If not, then you will need to get serial to USB adapter to access the Base Station CLI. Plug one end of a straight Cat 5 Ethernet cable into the Base Station Console port and the Page 27 PureWave Quantum 6600 User Guide v2.1 other end into the RJ45 to Modem adapter. Connect the other end of this Modem adapter to a DB9 serial cable and connect this DB9 serial cable to a USB adapter that connect to your laptop. With the Base Station and all cables properly installed, power may now be applied to the Base Station. The Base Station has no power switch so it will begin to power up immediately when a power source is attached. The POWER LED should be solid green. 3.2 Default Parameters Table 8 lists the factory default values that are set prior to shipment. These default parameters provide the means for a User to gain access to the system. Parameter Mgmt IP Address Factory Default 192.168.1.10 Mgmt IP Netmask 255.255.255.0 Mgmt Default Gateway 192.168.1.254 Hostname quantum-bs Admin User name admin admin User Password admin123 Table 8: Base Station Management Interface and Access Default Parameters 3.3 Logging in to the CLI The PureWave Quantum Base Stations Command Line Interface (CLI) has a standard Cisco IOS

(Internetwork Operating System) look and feel to its operation. It is accessible via the Base Station Console interface using an appropriate terminal emulator, or via a Base Station ETH-1 port using either SSH or Telnet. Both methods of access will be described. Telnet is disabled by default so may not be used for initial configuration. It is assumed that the default parameters (IP address, baud rate, etc) are still in use. If defaults have been changed then please use the current values. Accessing the CLI via the Ethernet port requires that its IP address and related parameters be known. If the default settings have been changed and the new settings have been lost then access via the Base Station Console port will be required to reset those parameters. Page 28 PureWave Quantum 6600 User Guide v2.1 3.3.1 Accessing the CLI via the Base Station Console Port

(1)

(2) Connect a computer to the Base Station Console port as detailed in section 3.1 above. Open a terminal emulation program on the computer. Suitable programs are PuTTY or HyperTerminal (Figure 4). Figure 4: PuTTY Serial Port Configuration Window Create a new connection with the serial port settings as outlined in Table 9. Serial Console Port Settings Serial Line COM1 Speed (Baud Rate) 38400 Data bits Stop Bits Parity Flow Control 8 1 None None Table 9: Console Port Settings

(3) A login prompt will be displayed as in fFigure 5: Console Login. The default Login and Password are:

Default login:

admin Default password:

admin123 Page 29 PureWave Quantum 6600 User Guide v2.1 Figure 5: Console Login After this login, the User will be presented at the hostname prompt (figure 6). If the Base Station is still in its default status then the hostname prompt will be quantum-bs. Figure 6: Console Login Default Status Page 30

(4) PureWave Quantum 6600 User Guide v2.1 3.3.2 Accessing the CLI via an Ethernet Port

(1) Connect a computer using an Ethernet connection to the Base Station ETH-1 port (either directly or via a router or network). Open an SSH client program such as PuTTY (Figure 7: ). The default port number is 22. Figure 7: PuTTY SSH Client Configuration

(2) Create a new SSH profile using the default management IP values. If the defaults have been changed then please use their current values. If the management IP settings are "unknown" then the Base Station can only be accessed via its Console port (refer to section 3.3.1). Once the Base Station has been accessed, its management IP settings can be reset using the procedure detailed in section 3.4.

(3) The default Login and Password are:

Default login:

admin Default password:

admin123 Page 31 PureWave Quantum 6600 User Guide v2.1 3.4 Logging in to the Web GUI Interface The PureWave Quantum Base Stations Web Interface is accessible through most major web browsers that support SSL connections. The Web Interface has been specifically tested on Internet Explorer

(Version 7 and up) and Mozilla FireFox. Access via HTTP and HTTPS are both supported, however HTTPS is the default and HTTP is disabled by default. If the current ETH-1 port IP settings have been lost then they must be reset using access via the Base Station Console CLI (see section 3.3.1). The ETH-1 management IP settings must be known if the Base Station is to be accessed via the Web GUI Interface. Connect a computer using an Ethernet connection to the Base Station ETH-1 port (either directly or via a router or network). Open an SSH client program on the computer. Open up a web browser and type in https://192.168.1.10 or http://192.168.1.10 (if HTTP has been enabled which is disabled by default) in the address field. If the default ETH-1 management IP settings have been changed then please enter the current Management IP Address of the Base Station. If the User is presented with a certificate error in the browser, then just click ignore or continue to web site and proceed. The login page is displayed in Figure 8: . The default Username and Password are:

Default Username:

admin Default Password:

admin123 Figure 8: Web GUI Interface Login Page Page 32

(1)

(2)

(3) PureWave Quantum 6600 User Guide v2.1

(4) After login, the User will be presented at the Main Web GUI Interface Screen (figure 9). This will be the starting position for all subsequent configurations. Figure 9: Main Web GUI Interface Screen

(5) The structure of the Main Web GUI Interface Screen is as follow:

Configuration and a Tools tab across the top of the screen. o Underneath these Tabs there are the View or Edit modes of operation (Edit Private and Edit Exclusive). Configuration tree on the left-hand side of the screen which consists of the Main Menu Options. The plus sign "+" indicates that there are Main Menu Sub-Elements to each Main Menu Option. The right hand side of the screen to the right of the Main Menu Options will be blank.

(6) Once a Main Menu Option has been selected and navigated to, even if the User reverts back to the Main Web GUI Interface Screen, the previous menu option will be displayed on the right hand side of the screen (refer to figure 10). Once the screen is "refreshed", this will be cleared away. Page 33 PureWave Quantum 6600 User Guide v2.1 Figure 10: Main Web GUI Interface Window Refresh To enable Base Station access via HTTP then:

(1) From the Main Web GUI Interface Screen select the Configuration Tab and then the web Main Menu Option from the down the left hand side menu (figure 11). Figure 11: Web GUI Interface Web Main Menu Option Page 34 PureWave Quantum 6600 User Guide v2.1

(2) A window will be displayed that provides an indication or not as to Web Server HTTP Support

(figure 12). Figure 12: Web GUI Interface HTTP Support

(3) To enable first select Edit Private or Edit Exclusive. This will drop the User into the Edit mode

(figure 13). The User can enable the Web Server HTTP Support by selecting the Enabled option Figure 13: Web GUI Interface HTTP Support Edit Enabled The User must Commit the changes (apply the configuration in run-time). To Commit, select the Commit option. A prompt screen will appear directing the User to confirm the pending configuration changes. To proceed the User must select Cancel or OK. Page 35

(4) PureWave Quantum 6600 User Guide v2.1 3.4.1 Web Interface Configuration Key Concepts The Web GUI Interface, when the Configuration Tab has been selected, has two major modes of operation:

Read-only access of all parameters. This is the default mode upon initial log in (refer to figure 14). View Mode:

Edit Mode: Write access configuration of all available parameters. Within this mode there are two sub-options:

Edit Private. Edit Private will allow the user to configure all parameters but will not lock the configuration database, allowing for other users to make configuration changes at the same time (see Figure 15). Edit Exclusive. Edit Exclusive will lock the configuration database and prevent any other user from making configuration changes. Note: System configuration changes are first made to the running configuration database in memory. This allows the opportunity for the user to test the changes first before committing. In order to make the change persistent and survive a restart, the Configuration-Write command must be used. Figure 14: The Main Web GUI Interface Screen in View Mode Page 36 PureWave Quantum 6600 User Guide v2.1 Figure 15: The Web GUI Interface Screen in Edit Private Mode At the Main Web GUI Interface Screen, select the Configuration Tab, select the configuration Main Menu option and then Edit Private or Edit Exclusive. The User will now be in the Edit mode. There are a number of key concepts that will be repeatedly used when the User is in the Edit mode and thus making configuration changes. These key concepts form the six Command Menu Options when the User is in the Edit mode. These are:

Changes. This prompts the User to accept the configuration changes that have been made. Validate. This validates that the changes are valid and have been configured correctly. Revert All. This will cancel (or revert) any changes that may have been made. Commit. This will commit the changes to the running database. Rollback. This will rollback any changes to a previously saved state. Exit Transaction. This will exit the Edit mode. When the User selects the Changes Command Menu Option then they are presented with the following options:

If no configuration changes have been made, then a popup window appears stating "No configuration changes have been made". The User simply selects the OK prompt to navigate back to the Edit Mode. Page 37 PureWave Quantum 6600 User Guide v2.1 Figure 16: Configuration Changes Popup Window If relevant changes have been made, then a window appears. This indicates the relevant configuration file for this pending change. It indicates the relevant parameter that is in the process of being changed and the old and the new value. There is also an option within this window to Revert the change (refer to figure 17). If the User selects this revert option then the intended changes will be reversed and the "No configuration changes" will appear (refer to figure 16 above). Figure 17: Revert Option If the User has made some configuration changes and then they decide to reverse the changes then the User can select the Revert All window option. Selecting this option presents:

If no configuration changes have been made, then a window appears stating "There is nothing to revert". The User simply selects the OK prompt to navigate back to the Edit Mode. Page 38 PureWave Quantum 6600 User Guide v2.1 If changes have been made, then a window appears stating "All your non-committed configuration changes will be reverted" (refer to figure 18). The User simply selects the OK prompt to proceed and navigate back to the Edit Mode. Figure 18: Revert All Configuration Changes If the User has made some configuration changes and these have been committed and saved the User can make use of the Rollback All window option. A rolling audit log of all configuration changes in stored within the Base Station (refer to figure 19). This log is a record of:

Rollback File. This is the name of the configuration file. Creator. This is the creator of the change. This will be the login name that was used at the time of the configuration change. Date. This was the date of the change. Via. This was the method of access to the Base Station that was used to effect the change. On the right side of the window, is a text pad that provide details of the parameters and how they were changed. To effect the Rollback procedure then the User simply has to highlight the relevant rollback file and then select the Load Command Menu Option (refer to figure 19). Page 39 PureWave Quantum 6600 User Guide v2.1 Figure 19: Rollback Option If the User has made some configuration changes and they wish to Validate the changes then the User can select the Validate Command Menu Option. If the User, after making the relevant changes, selects the Validate option then if the intended changes are valid, then a window appears stating "The configuration is ready to be committed" appears (refer to figure 20). The User simply selects the OK prompt to proceed and navigate back to the Edit Mode. Figure 20: Validate Option Page 40 PureWave Quantum 6600 User Guide v2.1 The Commit Command Menu Option performs a crucial procedure in that it commits all configuration changes to the running database. When in Edit mode, the method of configuring and saving changes remains the same. A user may change any number of parameters but none of those changes will take effect until they are committed. Clicking the Commit Menu will result in one of the following actions If no configuration changes have been made, then a window appears stating "There is nothing to commit". The User simply selects the OK prompt to navigate back to the Edit Mode. If changes have been made, then a window appears stating "Do you want to commit your pending configuration changes?" (refer to figure 21). The User simply selects the OK prompt to proceed. Figure 21: Commit Option When OK has been selected then a window appears stating "The configuration has been committed" (figure 22). The User simply selects the OK prompt to proceed and navigate back to the Edit mode. Note: System configuration changes are first made to the running configuration database in memory. In order to make the change persistent and survive a restart, the Configuration-

Write command must be used. Page 41 PureWave Quantum 6600 User Guide v2.1 Figure 22: Commit Option Successful Unsaved configuration changes persist for only the current boot. If the Base station is rebooted then those changes will be lost if the configuration has not been committed. Several menus have two sets of parameters, these are defined as:

Configured Parameters. These are the most recently saved settings and are stored in the systems configuration database State Parameters. These are the readings of the actual state from the Base Station. State Parameters may be identical to Configured Parameters, or they may be committed but unsaved parameters that differ from the Configured Parameters. After a reboot, both sets of parameters will be identical. The "Save Procedure" is to ensure that the running configuration is saved is:

(1) At the Main Web GUI Interface Screen, select the Configuration Tab, select the configuration Main Menu Option then the write Main Menu Sub-Element. The User will have to click on the Perform Command Menu Option to copy the running configuration to the startup (see figure 23). Page 42 PureWave Quantum 6600 User Guide v2.1 Figure 23: Writing Running Configuration to Startup

(2) A pop up window indicating that the write was successful will be displayed (refer to figure 24). Figure 24: Writing Running Configuration to Startup Successful Page 43 PureWave Quantum 6600 User Guide v2.1 Note: Several configuration changes require that the Base station be rebooted. The procedure to reboot a Base Station is as follows:

(1) At the Main Web GUI Interface Screen, select the Configuration Tab, select the administration Main Menu option and then reboot Main Menu Sub-Element. The User will have to click on the Perform Command Menu Option to reboot the entire Base Station (refer to figure 25). Figure 25: Reboot Base Station

(2) Upon clicking perform, the user must confirm the reboot operation by clicking Ok. After the reboot option has been performed then an appropriate window indicating a successful reboot execution will be displayed (figure 26). The subsequent time for the Base Station to become operational is approximately 5 minutes. Figure 26: Reboot Base Station Successful Page 44 PureWave Quantum 6600 User Guide v2.1

(3) The system will use the stored startup configuration after rebooting. Unwritten changes in the running configuration will be lost.

(4) There are two reboot options under the administration Main Menu options including reboot. This option will reboot the Base Station reboot-sectors. This option will reboot the internal elements of the Base Station that are pertinent to the sector RF elements only. After the reboot-sectors option has been performed then an appropriate window indicating a successful reboot execution will be displayed. The subsequent time for the Base Station to become operational is approximately 2 minutes. 3.4.2 Web GUI CLI Access Level The PureWave Quantum Base Station has a Command Line Interface (CLI) that can be accessed from within the Web GUI. To access the Web GUI CLI then at the Main Web GUI Interface Screen, select the Tools Tab. The User will be presented with a number of User tools (figure 27). Figure 27: The Tools Tab Menu Options The User is presented with four Tools Command Menu Options. These are:

Logs. This allows the User to display and hence view:

o System log o Alert log o Audit log. Accessories. The following protocols are made available to the User:

Page 45 PureWave Quantum 6600 User Guide v2.1 o Ping o Traceroute o CPU Load CLI. The User has access to the CLI and can execute all the CLI commands directly if required. Users. This indicates all the Users that are currently connected to the Base Station. It also provides a means to physically "kick" them off their connection. In addition, a message board is provided thus enabling instant messages to be sent to the Users that are currently connected to the Base Station. 3.4.2.1 Tools Logs At the Main Web GUI Interface Screen, select the Tools Tab and then Logs (refer to figure 28). Figure 28: The Tools Tab Logs Menu To view the relevant Log, the User simply has to select one of the 3 logs that are available to view. These logs are system, alert and audit logs. The three Tools logs are displayed in figures 29 through 31 below. Page 46 PureWave Quantum 6600 User Guide v2.1 Figure 29: The Tools Tab System Log Figure 30: The Tools Tab Alert Log Page 47 PureWave Quantum 6600 User Guide v2.1 Figure 31: The Tools Tab Audit Log 3.4.2.2 Tools Accessories At the Main Web GUI Interface Screen, select the Tools Tab and then Accessories (refer to figure 32). Figure 32: The Tools Tab Accessories Menu To perform the relevant protocol, the User simply has to select the relevant option. To enable Ping or Traceroute, the User must:

Select the New button A popup window will appear, this will enable the User to specify the host (figure 33). Page 48

(1)

(2) PureWave Quantum 6600 User Guide v2.1 Figure 33: The Accessories Ping Command The User must now select the OK command button. The results of the action will then be displayed (refer to figure 34). Figure 34: The Accessories Ping Results

(3)

(4) To examine the CPU Load, the User simply has to select the CPU Load option. The User is presented with a display of the current CPU load. This will automatically be updated every 5 seconds and it will calculate the load averages over 1, 5 and 15 respectively (refer to figure 35). Page 49 PureWave Quantum 6600 User Guide v2.1 Figure 35: The Accessories CPU Load Results 3.4.2.3 Tools CLI At the Main Web GUI Interface Screen, select the Tools Tab and then CLI. The User is presented with a CLI screen (refer to figure 36). The User is free to enter all the available CLI options Figure 36: The Tools Tab CLI Page 50

PureWave Quantum 6600 User Guide v2.1 3.4.2.4 Tools Users At the Main Web GUI Interface Screen, select the Tools Tab and then Users. The User is presented with a screen that indicates the Users that are currently logged in to the Base Station and an instant messaging section to communicate with these Users (figure 37). Figure 37: The Tools Tab Users Connected to Base Station The User can also physically disconnect or "kick" off the User. The User simply has to select the Kick command option. A message board is provided to enable instant messages to be sent to the Users that are currently connected to the Base Station. The User simply has to enter the relevant message in the text box and then press Send. There is also the option to Clear history if required (refer to figure 38). Figure 38: The Tools Tab Users Instant Messaging Page 51 PureWave Quantum 6600 User Guide v2.1 3.5 Base Station Initial Configuration 3.5.1 System Architecture and Terminology In this section we will configure the minimal set of parameters that must be appropriately set prior to deployment. It is important to first clarify some terminology related to the system architectural model. In typical terminology, a Base Station is comprised of one or more co-located sectors. Each PureWave Quantum 6000 Base Station can be deployed either by itself, as a single-sector Base station, or as one sector in a multi-sectored Base station. In either case, each PureWave Quantum 6000 must be fully configured and provisioned in its entirety, as if it was a standalone Base Station. The various Web Interface configuration parameters are organized into a hierarchical tree, and that some parameters are labeled as Base Station level and some sector level. Since the Quantum 6000 Base Station is really both a sector and a Base station, the differentiation is for organizational purposes, as well as compatibility with future multi-sector functionality or products. Additionally, a Base Station must be connected to subscriber devices on the air-interface side and to a Core Network on the backhaul side. As discussed previously, PureWave Quantum 6000 Base Stations can flexibly support a variety of core network configurations, ranging from a simple router (Standalone Mode) to a full ASN-GW. It also has a built-in Radius client for connection to an external AAA server when in Standalone Mode. 3.5.2 Base Station Management Interface and Access Parameters Table 10 lists the minimum set of management interface parameters that must be set prior to deployment. These parameters govern how an operator, administrator, or management system interfaces with and gains access to the Base Station. Before proceeding, please gather the information listed in the table. Factory default values are provided here as they are required for initial access. Parameter Mgmt IP Address Mgmt IP Netmask Description IP address used for all external mgmt interfaces (CLI / Web / SNMP). Mgmt interface IP netmask Mgmt Default Gateway Mgmt interface default gateway Factory Default 192.168.1.10 255.255.255.0 192.168.1.254 Hostname String name assigned to the Base Station. quantum-bs admin User Password Unique password for default admin admin123 Table 10: Base Station Management Interface and Access Parameters Page 52 PureWave Quantum 6600 User Guide v2.1 To perform the initial configuration of the Base Station, it is recommended to configure the Management Interface Parameters via accessing through the Base Station Console Port. To complete this section you will need the data in Table 10. If the management IP settings are "unknown" then the Base Station can only be accessed via its Console port (refer to section 3.3.1). Once the Base Station has been accessed, its management IP settings can be reset using the procedure detailed in section 3.4. Even though the CLI may be accessed through the Ethernet ports, it is not the recommended method of changing the management interface parameters, as connectivity with the port will be lost immediately upon changing them. Log into the CLI (Section 3.3) and execute the commands as indicated to configure the Base Station access parameters. Text in brackets <> should be replaced with your configuration data to replace the default values from the table above.

(1) At the quantum-bs> prompt, type enable. This will drop the User into the enable mode and the prompt will change from > to # (refer to figure 39). Figure 39: Initial Connection to CLI At the quantum-bs# prompt type configure terminal. The prompt will now indicate that the User is now in config mode and it will display the current Base Station time (figure 40). Page 53

(2) PureWave Quantum 6600 User Guide v2.1 Figure 40: Base Station CLI Time To set the Management IP address, at the Quantum:quantum-bs(config) prompt type system interface ip address <Mgmt IP Address> netmask <Mgmt IP Netmask> e.g. system interface ip address 192.168.200.104 netmask 255.255.255.0 To set the default Gateway at the Quantum:quantum-bs(config) prompt type system interface ip default-gateway <Mgmt Default Gateway> e.g. system interface ip default-gateway 192.168.200.1 To exit, at the Quantum:quantum-bs(config) prompt type exit The changes must be written to memory. At the quantum-bs# prompt type write memory (refer to figure 41). Figure 41: Base Station CLI Initial Configuration

(3)

(4)

(5)

(6)

(7) The IP address change to the Base station is immediate and does not require a reboot. Page 54 PureWave Quantum 6600 User Guide v2.1

(8) Another useful command is the ability to change the default Quantum prompt. When the User is in the config mode, type system hostname <Hostname> (refer to Figure 42). The change must be written to memory and the Base Station has to be rebooted. Figure 42: Base Station CLI Hostname Change

(9) To change the username admin password, when the User is in the config mode, type username admin password Password <new admin User Password>

The change must be written to memory (Figure 43). Figure 43: Base Station CLI Username Password Change 3.5.3 Base Station Configuration Parameters There are a number of key parameters that must be configured, as a minimum, prior to deployment and operation of the Base Station. Table 11 is a list of these parameters. In addition to these key parameters, there are a number of other parameters that can be configured on the Base Station. Such parameters can be left in their default configuration for "nominal" Base Station operation but there is the option to Page 55 PureWave Quantum 6600 User Guide v2.1 change based upon specific operating conditions. All parameters will be described in the following sections. One point to make, is that in the context of the PureWave Quantum 6600, as this is a single sector Base Station, the terms Sector and Base Station are effectively synonymous. This fact is represented within the Web GUI Interface by the use of the number 1 at the appropriate menu option. The number 1 stands for Sector 1. The key Base Station parameters that must be configured are:

Configuration Item Description Base Station Mode Standalone Local Mode(default) or ASN Gateway Mode ASN Gateway IP Address IP Address of the ASN-GW (ASN-GW Mode only) Base Station Radius IP Address IP Address of the Radius Server (Standalone Mode only) Base Station Radius Port Radius Server Port (Standalone Mode only) Base Station Radius Secret Radius string secret (Standalone Mode only) Sector IP address IP Address of the sectors datapath interface Sector IP Netmask Netmask of the sectors datapath interface Sector Default Gateway Default gateway of the sectors datapath interface Sector BS-ID Sector CS Type Base Station ID of the sector Convergence sub-layer type of the sector: Ethernet CS

(default) or IPv4 CS Sector Radio Center Frequency Center frequency in kHz Sector Channel Bandwidth 5 MHz, 7MHz, or 10 MHz (default) Sector Radio Power Output Sector Radio Antenna Gain Preamble power output value per antenna (includes 3 dB preamble). Default : 36 dBm. Antenna gain (dBi) Sector Radio Cable Loss Estimated external cable loss (dB) Sector Antenna TX Mode MIMO-A (default) or MIMO-AB Sector DL:UL Frame Ratio Sector Antenna TX Mode 26:21, 29:18, 32:15, 35:12 (default) in 5MHz and 10MHz 23:9, 21:12, 17:15 in 7MHz MIMO-A (default) or MIMO-AB Table 11: Base Station Sector Configuration Data The Web GUI Interface will be used to configure the parameters that are required in Table 11. The starting point for all configurations is the Main Web GUI Interface Screen. The relevant parameters are distributed across a number of different menu options and hence screens and windows. Each of these options will be discussed in detail. Page 56 PureWave Quantum 6600 User Guide v2.1 After making the various configuration changes, the User will need to "Commit" and "Save"

the changes. 3.5.3.1 Sector, General Settings At the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option and then general Main Menu Sub-Element. This will display the Sector Settings window (Figure 44). Figure 44: Sector Settings There are two basic groups to this Sector option. These are:

Sector Advanced Settings (configured) Sector Provisioning (configured) The User now has to navigate to the next level, therefore at the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, general Main Menu Sub-Element and then 1, this will display the key settings window. There are three distinct groups to this window (refer to Figure 45). Key Settings. This indicates the relevant sector, which as has been described in number 1. This is not a configurable parameter. Sector General Administration (configured). This is an indication whether the sector has been enabled to effect general administration. This can be configured. Sector General Status. This indicates the current status of the following parameters. These parameters are non-configurable:

Page 57 PureWave Quantum 6600 User Guide v2.1 Figure 45: Sector General Options The Key Settings are defined by the following parameters (refer to Figure 46):

Operational State. This indicates if the Base Station is operational GPS State. This indicates the status of the Base Station GPS. Restart Count. This is a cumulative count of the number of sector restarts since the Base Station was power cycled. Number of MSS Subscribers. This is a count of the current Subscribers that are connected to the sector. Number of Service Flows. This is a count of the total number of Subscriber service flows that are currently configured. Image Bank A Software Version. The software that has been loaded into Bank A. Image Bank B Software Version. The software that has been loaded into Bank B. Running Software Version. This is the current operating version of software. Last Reset Reason. This provides a reason for the last sector reset. Page 58 PureWave Quantum 6600 User Guide v2.1 Figure 46: Sector General Configuration Parameters At the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, general Main Menu Sub-Element, 1 and then system. This will display the currently configured Sector General Provisioning window. There are a further two sub-elements to this window but only one is displayed. These sub-elements are:

system. This option enables the User to configure the parameters. state. This is a duplication of the windows and parameters that are contained within the system options. These are "read-only" screens and provide an indication as the current state or status of the system parameters. The status of the following parameters are displayed and the User is free to configure as required (refer to Figure 47). To edit and configure then the User must enter the Edit Mode (select Edit Private/Exclusive):

Base Station ID. This is the unique identifier that specifically indentifies the Base Station to the Subscribers. It is not recommended that this is changed. Cell ID. This is a numeric identifier that the User will define to a cell (acceptable range is 0 to 31). Convergence Sublayer Type. This is the convergence sublayer type that is globally set for the sector. The available options are ETHERNET_CS and IPv4_CS. The default is ETHERNET_CS. Downlink Broadcast Rate. This is a User defined parameter that specifies the maximum reserved Downlink (DL) rate for the purposes of IP broadcast traffic. This rate can be set up to 1Mbps and once set it is reserved and as such it is not available for Data Traffic. The default is 64000. Page 59 PureWave Quantum 6600 User Guide v2.1 Mode. This is the Base Station Mode and the available options are standalone-local (this is selected when the Base Station is used in a standalone mode and it is not connected to an ASN Gateway) the and asn-gateway (selected when the Base Station is connected to an ASN Gateway). Figure 47: Sector General Provisioning Parameters At the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, general Main Menu Sub-Element, 1, system and then ip and this will display the current configuration of the Sector External IP Address (refer to Figure 48). This is the Management IP Address through which the User is able to communicate to the Base Station. The Management IP parameters that the User can configure are:

Address. This is the IP address Netmask. This is the netmask associated with the IP address Gateway. This is the defined gateway. Page 60 PureWave Quantum 6600 User Guide v2.1 Figure 48: Sector External IP Address To edit the parameter, the User must enter the Edit Mode (select Edit Private or Edit Exclusive). Once in the Edit Mode the User simply has to select the notepad icon and this will provide an option to edit the IP address (refer to Figure 49 and Figure 50). Figure 49: Sector External IP Address Configuration Page 61 PureWave Quantum 6600 User Guide v2.1 Figure 50: Sector External IP Address Changed At the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, general Main Menu Sub-Element, 1, state and then system. This provides another view that will display the current configuration of the Sector. Even if the User enters the Edit Mode (select Edit Private or Edit Exclusive), no parameters are made available for editing. The options to configure these parameters are contained under the system and then base station options. There are three distinct groups to this window (refer to Figure 51 and Figure 52). Sector External ASN-Gateway. This contains the parameters:

IP Address. This is the IP Address of the external ASN Gateway. o o Port Number. This is the IP port number that is used to communicate with the ASN Gateway. o Nwg-version. This is the current firmware version of the ASN Gateway. Sector General Provisioning o Base Station ID. This is the unique identifier that specifically indentifies the Base Station to the Subscribers. o Cell ID. This is a numeric identifier that the User will define to a cell. o Convergence Sublayer Type. This is the convergence sublayer type that is globally set for the sector. o Downlink Broadcast Rate. This is the maximum reserved Downlink (DL) rate for the purposes of IP broadcast traffic. o Maximum Supported CPEs. This specifies the maximum number of Subscriber CPEs

(200) that can be connected to the Base Station. o Mode. This specifies whether the Base Station Mode is connected to an ASN Gateway. Sector External Radius Server Settings o IP Address. This is the IP Address of the external radius server. Page 62 PureWave Quantum 6600 User Guide v2.1 o Port Number. This is the IP port number that is used to communicate with the external radius server for authentication purposes. o Secret. This is the radius shared secret between the radius server and the Base Station. Figure 51: Sector External ASN Gateway Settings Figure 52: Sector External Radius Server Settings At the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, general Main Menu Sub-Element, 1, state, system and then ip. This provides another view that will display the current Management IP configuration of the Sector. Even if the User enters the Edit Mode

(select Edit Private or Edit Exclusive), no parameters are made available for editing. Page 63 PureWave Quantum 6600 User Guide v2.1 There following information is displayed in Figure 53. Sector External IP Address. Netmask. Gateway. Figure 53: Sector External Radius Server Settings 3.5.3.2 Sector, Advanced Settings At Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, advanced Main Menu Sub-Element and then 1, this will display the key settings window. There are two further sub-elements to this window but the information is only displayed when the actual element is selected. These further sub-elements are (refer to Figure 54):

wimax. These are the parameters that can be configured as defined by the WiMAX 802.16e specification. radio. These are the parameters that can be configured as part of the specific Base Station radio transmission configuration. security Page 64 PureWave Quantum 6600 User Guide v2.1 Figure 54: Sector Advanced Settings To view the Sector WIMAX Settings, at the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, advanced Main Menu Sub-Element, 1, and then wimax. The display is split into two main sections. These sections do not fit onto one screen and therefore the User has to scroll down to view etc (refer to Figure 55 and Figure 56). Sector WIMAX Settings (configured). These are the parameters that the User can Edit. Sector WIMAX Settings (state). These are the current configurations values of the parameters. Figure 55: Sector Configured WIMAX Settings Page 65 PureWave Quantum 6600 User Guide v2.1 Figure 56: Sector State WIMAX Settings If the User wants to configure any of the WiMAX parameters then they must enter the Edit Mode (select Edit Private or Edit Exclusive) and edit as necessary. The methods to Edit the parameters will be offered via a drop down menu of choices, enabling of a check box or editing of a notepad icon. After making the various configuration changes, the User will need to "Commit" and "Save" the changes. Figure 57: Sector WIMAX Settings Configuration Page 66 PureWave Quantum 6600 User Guide v2.1 The Sector WIMAX Settings parameters that the User can configure are defined below:

Maximum Uplink Rate. This parameter provides the means to globally fix the maximum modulation rate in the Uplink direction (defined as Subscriber to Base Station). If the User wants to dynamically adapt the rate to the maximum then the default value of QAM64_5/6 can be left unchanged. Refer to Appendix A for an explanation of how the maximum modulation rate, defined as MCS Rate, effectively caps the system data throughput. If the User wants to physically cap the rate and hence cap the throughput, they are free to select from the following MCS rates:

o QAM64_5/6 o QAM64_3/4 o QAM64_2/3 o QAM64_1/2 o QAM16_3/4 o QAM16_1/2 o QPSK_3/4 o QPSK_1/2 Maximum Downlink Rate. This parameter provides the means to globally fix the maximum modulation rate in the Downlink direction (defined as Base Station to Subscriber). The default is QAM64_5/6 and the same options as maximum uplink rate parameter are available. Antenna TX Mode. This the option to define the Smart Antenna Capabilities that were described in section 2.3.2.3. The default setting is MIMO-A and the available options are:

o MIMO-AB o MIMO-A Auto Power Control. The transmit power of a Subscriber is controlled via automatic algorithms in the Base Station. This control of the transmit power ensures optimum performance. The default is open-loop and the available options are:

o open-loop. In the case of an open loop algorithm, the Base Station sends a signal to the Subscriber of the required settings and the Subscriber controls its transmit power dynamically. o closed-loop. In the case of closed loop, the Base Station controls the Subscriber transmit power settings with a full measurements loop. Auto Transmit After Reset Mode. When this is enabled the Base Station will automatically start transmitting upon a power cycle. If this is disabled, then the User will have to manually start the transmission. Channel Bandwidth. This is the current channel bandwidth of the radio transmission. The default is 10MHz and the options are:

o 10MHz o 7 MHz o 5MHz DCD Interval. This is the WiMAX 802.16e DCD Interval value and it is to be defined in milliseconds. The default is 1000 (1 second) and the available range is 15 up to 10000. Default Provisioning Enabled. The User has the choice to enable or disable this feature. If this is enabled, then the Quality of Service (QoS) profile for the CPE will be the Default QoS that has been provisioned. This is defined as QoS profile 1. If this is disabled then the QoS profile will be that as defined for the particular CPE. Page 67 PureWave Quantum 6600 User Guide v2.1 Downlink/Uplink Frame Ratio. This is the ratio of downlink to uplink MAP symbols, refer to Appendix A and how this affects data throughput. The default option is 35:12 and the available options are:

o 26:21 o 29:18 o 32:15 o 35:12 Maximum Distance. This is the maximum distance, defined in km, that a Base Station can transmit to a CPE. The default is set to 11 and the User can select in the range 1 to 24. Noise and Interference Settings. The default is 35. NI is defined as per the IEEE 802.16-e as the noise per tone in 0.5 db steps above the -150 dBm, where 0 is -150dbm and 35 is -132.5dbm per tone. UCD Interval. This is WiMAX 802.16e UCD Interval value and it is to be defined in milliseconds. Interval defined in milliseconds. The default is 1000 (1 second) and the available range is 15 up to 10000. DL ECINR Report Support Specifies the mode of CINR reporting to be provided from the CPEs. Disabling ECINR reporting should be done only in case of older CPE revisions that do not support ECINR reporting. 5MHz Large Map Support Available and applicable only in case of 5MHz channel bandwidth setting. Auto Noise Level Adjustment Support Enables the automatic dynamic adjustment of NI and internal settings with respect to the measured noise level on the channel. The Noise measurement values can be seen in the radio tab. To view the Radio Settings, at the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, advanced Main Menu Sub-Element, 1, and then radio. The display is split into three main grouping sections. These sections do not fit onto one screen and therefore the User has to scroll down to view etc (refer to Figure 58 and Figure 59). Radio Settings (configured). These are the parameters that the User can Edit. Radio Settings (state). These are the current configurations values of the parameters. Noise and Interference Measurements (status). These are the current configurations values of the parameters. The Noise level is represented in 3 different measurement units. Page 68 PureWave Quantum 6600 User Guide v2.1 Figure 58: Sector Radio Configured Settings Figure 59: Sector Radio State Settings If the User wants to configure any of the Radio parameters then they must enter the Edit Mode (select Edit Private or Edit Exclusive) and edit as necessary. The methods to Edit the parameters will be offered via editing of a notepad icon (refer to Figure 60). Page 69 PureWave Quantum 6600 User Guide v2.1 Figure 60: Sector Radio Settings Configuration After making the various configuration changes, the User will need to "Commit" and "Save" the changes. The Radio Settings parameters that the User can configure are defined below:

Antenna Gain. This is the gain (in dB) for the Antenna that the Base Station is connected to. The default setting is 0 but the User is free to enter any value. Cable Loss. This is a loss of the cable (in dBs) from the Base Station to the Antenna. The default setting is 0 but the User is free to enter any value. Center Frequency. This is the center frequency of the Base Station and it must match with what is configured on the Subscribers. The default setting is relative to the frequency range of operation of the Base Station. To re-configure, the center frequency has to be input in KHz. Power Output. This is the radio output power in dBm. The default setting is relative to the frequency range of operation of the Base Station. The User must ensure that the maximum output power is defined as described in section 2.3.2.2 "Computing EIRP Power". Contention Based Mode may be enabled on the Radios to support the upper 25 MHz of the 3.65 GHz US ISM band. To utilize Wimax Contention Based Mode, at the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, advanced Main Menu Sub-Element, 1, and then radio and contention-based mode. The display is split into two grouping sections. These sections do not fit onto one screen and therefore the User has to scroll down to view etc (refer to Figure 61). Mode (enable/disable). Allows the feature to be enabled or disabled Carrier Sense Threshold. Set to -85.0 dBm Page 70 PureWave Quantum 6600 User Guide v2.1 Carrier BackOff Frame. Number of frames to wait when a carrier is detected Carrier Sense Resume Frame. Set to 752 Figure 61 Contention Based Mode Omniwave may be enabled on the radio level to support a 3x2x2 configuration. To utilize Omniwave, at the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, advanced Main Menu Sub-Element, 1, and then radio and omniwave. Mode (enable/disable). Allows the feature to be enabled or disabled Status. Current configuration (enabled or disabled) Figure 62 OmniWave Settings Page 71 PureWave Quantum 6600 User Guide v2.1 To view the Security Settings, at the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, advanced Main Menu Sub-Element, 1, and then security. The display is split into two main grouping sections (refer to Figure 63). Security Settings (configured). These are the parameters that the User can Edit. Security Settings (state). These are the current configurations values of the parameters. Figure 63: Sector Security Settings If the User wants to configure any of the Security parameters then they must enter the Edit Mode

(select Edit Private or Edit Exclusive) and edit as necessary. The methods to Edit the parameters will be offered via an enabling of a check box or editing of a notepad icon (refer to Figure 64). Figure 64: Sector Security Settings Configuration Page 72 PureWave Quantum 6600 User Guide v2.1 After making the various configuration changes, the User will need to "Commit" and "Save" the changes. The Security Settings parameters that the User can configure are defined below:

AK Lifetime. This stands for Authorization Key lifetime. It is used when authentication and encryption is enabled. It is periodically re-generated by the Base Station after a request is received from a Subscriber following expiration of this timeout. The default setting is 6048000 but the User is free to enter any value. Enabled. This indicates whether the Security Feature has been enabled or not. TEK Lifetime. This stands for Traffic Encryption Key lifetime. It is used when authentication and encryption is enabled. It is periodically re-generated by the Base Station after a request is received from a Subscriber following expiration of this timeout. The default setting is 43200 but the User is free to enter any value. 3.5.3.3 System Settings At the Main Web GUI Interface Screen select the Configuration Tab and then select system Main Menu Option. This will display the System Settings window. The system menu option has three further sub-

elements , these being (refer to Figure 65):

base-station. This details various Base Station parameters. reset. This is a means for the User to default the Base Station back to its "out of the box" initial configuration values. Figure 65: System Settings Page 73 PureWave Quantum 6600 User Guide v2.1 The System display is split into seven main grouping sections. These sections do not fit onto one screen and therefore the User has to scroll down to view etc. An indication as to whether there are any User configurable parameters included in the grouping is provided. If the User wants to configure any of the parameters then they must enter the Edit Mode (select Edit Private or Edit Exclusive) and edit as necessary. The methods to Edit the parameters will be offered via a drop down menu of choices, an enabling of a check box or editing of a notepad icon.

/system/state. This option does not contain any User configurable parameters. System Console Settings. System Miscellaneous Settings. System General Settings. System Identification Setting. This option does not contain any User configurable parameters. System Utilization Statistics. This option does not contain any User configurable parameters. The parameters that the User can configure and the relevant grouping section that they belong are outlined below. After making the various configuration changes, the User will need to "Commit" and

"Save" the changes. System Console Settings. o Baudrate. This is the baud rate that is configured for serial connection via the Base Station Console Port. The default is 38400 and the available options are 115200, 57600, 38400, 19200 and 9600. System Miscellaneous Settings. o Hostname. This is a free format text field for the User to specify a hostname. o Led-enabled. The User can enable or disable the LED indicators for the Base Station. System General settings. o Name. This is a free format text field for the User to specify a name to the Base Station. o Location. This is a free format text field for the User to specify a location to the Base Station. o Contact. This is a free format text field for the User to specify a contact for the Base Station. At the Main Web GUI Interface Screen select the Configuration Tab, select system Main Menu Option and then the base-station Main Menu Sub-Element. This will display the External ASN-Gateway Settings window (refer to Figure 66). Page 74 PureWave Quantum 6600 User Guide v2.1 Figure 66: System External ASN Gateway Settings The System display is split into four main grouping sections. These sections do not fit onto one screen and therefore the User has to scroll down to view etc. An indication as to whether there are any User configurable parameters included in the grouping is provided. If the User wants to configure any of the parameters then they must enter the Edit Mode (select Edit Private or Edit Exclusive) and edit as necessary. The methods to Edit the parameters will be offered via a drop down menu of choices or editing of a notepad icon. External ASN-Gateway Settings. These are the settings for any external ASN Gateway that is connected to the Base Station. Base-Station Settings. These are the settings for the Base Station. External Radius Server Settings. These are the settings for the external Radius Server, if configured.

/system/base-station/neighbor. These are settings which are broadcasted by the base station so that the CPE understands which neighboring Base Stations to scan The parameters that the User can configure and the relevant grouping section that they belong are outlined below. After making the various configuration changes, the User will need to "Commit" and

"Save" the changes. External ASN-Gateway Settings. o ASN-Gateway IP Address. This is the IP address of the ASN Gateway that the Base Station is connected to. An IP address has to be provided if the Base Station has been configured to operate in ASN Gateway mode. o ASN-Gateway Port Number. This is the Port Number that the Base Station use to communicate with the ASN Gateway. Page 75 PureWave Quantum 6600 User Guide v2.1 o ASN-Gateway Vendor ID. This User has the option to select and store the vendor of the ASN Gateway. The current options are Wichorus and Cisco. o ASN-Gateway NWG Version. This User has the option to select and store the current firmware version of the ASN Gateway. The current options are v1.2 and v1.3. Base-Station Settings o Group-id. This is a free format text field. o Group-descr. This is a free format text field. o Mode. This defines the mode of operation for the Base Station. The default option is standalone-local and the available options are asn-gateway and standalone-local. External Radius Server Settings o Radius Server IP Address. If the Base Station has been configured to use an external Radius Server, then its IP address would be provided here. o Radius Server Port Number. This is the Port Number that the Base Station use to communicate with the Radius Server. o Secret. This is the radius "secret" that is shared between the Base Station and the Radius Server. The system, base-station menu option has two further sub-elements, handover and neighbor. handover. This is where triggers are set for handover operation (see Figure 67). By default, there are no triggers. For handover operation at least two triggers must be set, one for scanning and one for handover. This information is incorporated into DCD message sent by the base station. This may be left unconfigured if no handover is desired. For each trigger following needs to be configured:

o Trigger Index: A user defined unique number between 1-8. o Average Duration: Trigger averaging duration is the time measured in number of frames over which the metric measurements are averaged. o Trigger Type: This defines trigger metric, CINR or RSSI o Trigger Function: This parameter specifies the function for the trigger type chosen earlier. Select one from the dropdown menu. o Trigger Action: This parameter specifies the action, scanning or handover, to take when trigger criteria is met. Select from the dropdown menu. o Trigger Value: This parameter specifies the value for corresponding to the trigger type and function selected above. Page 76 PureWave Quantum 6600 User Guide v2.1 Figure 67 System Handover Trigger Setting neighbor. This is the place to configure information about neighbor base stations (Figure 68). This is required for handover operation. This can be left unconfigured if no handover is required. For each neighbor, following needs to be configured:

a. BS id: This is the BSID of neighbor bs. Use upper case letters only. BSID of the neighboring base stations should have same operator id as the serving base station., i.e. the upper 6 bytes should be same. IP Address: This is the IP address of the neighbor base station. o o Preamble Index: This is the preamble-index of the neighbor base station. o BS Index: This is a user defined number in the range of 1-254. The index of 255 has a special meaning. When this index is set to 255 then the neighbor will be considered as a non-Purewave base station, and Purewave base station will unconditionally accept the handover request. No backbone communication will take place. o BS Frequency: This is the frequency of the neighbor base station in KHz. Page 77 PureWave Quantum 6600 User Guide v2.1 Figure 68 Neighbor configuration At the Main Web GUI Interface Screen select the Configuration Tab, select system Main Menu Option, reset Main Menu Sub-Element and then factory/Default. This provides the User with a reset system to factory defaults option (refer to Figure 69). The User has to select Perform Command Menu Option to erase the startup configuration and reboot the system. Afterwards the system will come up with the factory default configuration. Figure 69: System Reset to Default Option Page 78 PureWave Quantum 6600 User Guide v2.1 At the Main Web GUI Interface Screen select the Configuration Tab, select system Main Menu Option, reset Main Menu Sub-Element and then interface. This provides the User with the options to configure the System Management Static IP Address (refer to Figure 70). If the User wants to configure any of the parameters then they must enter the Edit Mode (select Edit Private or Edit Exclusive) and edit as necessary. The methods to Edit the parameters will be offered via editing of a notepad icon. The parameters to configure for the Base Station Static Management IP Address are:

Address Netmask Default Gateway Figure 70: System Management Static IP Address At the Main Web GUI Interface Screen select the Configuration Tab, select system Main Menu Option and then inventory Main Menu Sub-Element. This will provide the User with an inventory checklist of the internal hardware modules of the Base Station (refer to Figure 71). Figure 71: System Base Station Inventory Page 79 PureWave Quantum 6600 User Guide v2.1 3.5.3.4 GPS Settings The use of a GPS for air frame synchronization is mandatory if more than one Base Station is installed in a geographical area where potential radio transmissions could interfere with one another. GPS is enabled or disabled via the GPS option. At the Main Web GUI Interface Screen select the Configuration Tab and then select the gps Main Menu Option. This will display the GPS Settings and Status window (Figure 72). The gps Main Menu Option has no further sub-elements . Figure 72: GPS Settings and Status The GPS Settings display is split into one main group sections. An indication as to whether there are any User configurable parameters included in the group is provided. If the User wants to configure any of the parameters then they must enter the Edit Mode (select Edit Private or Edit Exclusive) and edit as necessary. The methods to Edit the parameters will be offered via an enabling of a check box or editing of a notepad icon. A GPS antenna MUST be connected to the base Station before setting GPS Admin Status to Enabled. The GPS Settings and Status window contains (refer to figure 69):

GPS Admin Status. This is an indication of the GPS Admin Status. The options are enabled and disabled with disabled as the default. Sync Recovery Timeout Interval. The Base Station has a Sync Recovery feature, whereby the Base Station is automatically reset if GPS sync is lost for more than a specified timeout period. The timeout period (in seconds) is specified via the Sync Recovery Timeout Interval parameter. The default value is 1800 seconds. Page 80 PureWave Quantum 6600 User Guide v2.1 Latitude (degrees). This is the latitude location of the GPS receiver. This is not a User configurable parameter. Longitude (degrees). This is the longitude location of the GPS receiver. This is not a User configurable parameter. Altitude (meters). This is the altitude in meters, above sea level of the GPS receiver. This is not a User configurable parameter. State. This is an indication of the state of the GPS receiver. This is not a User configurable parameter. Sync Loss Occurrences since Last Reboot. This is a cumulative count of the number of GPS sync losses since the Base Station was last reset. This is not a User configurable parameter. Sync Loss Recoveries since Last Reboot. This is a cumulative count of the number of GPS sync recoveries since the Base Station was last reset. This is not a User configurable parameter. The GPS will be in one of the states below from startup and until it is operational and providing synchronization to the base station. Offline. The 1 PPS from the satellite signal is not detected, so basic synch lock has not occurred. This can be also seen as there should not be any coordinates if the GPS is offline INIT: GPS state which dictates whether or not the BASE STATION will start transmission if the GPS is enabled. o o o o INIT-Initializing INIT-Tracking-1-OSO INIT-Tracking-2-STO-Init INIT-Tracking-3-STO-Start UP: GPS is operational (up). o UP-Tracking-Done. Base Station will begin transmission o UP-Tracking-Hist. Last GPS state indicating a steady state. o UP-Holdoff o UP-ReAcquire o UP-Retrack DOWN: GPS is not operational (down). o DOWN-Unreliable o DOWN-Recovery 3.5.3.5 Time Settings It is important that the Base Station maintain an accurate date and time so that system logs are aligned and may be correlated with other network activity and trouble reports. Although the date and time must be initially set by the user, the Base Station supports the Network Time Protocol (NTP) to maintain its accuracy. The use of NTP is optional Page 81 PureWave Quantum 6600 User Guide v2.1 At the Main Web GUI Interface Screen select the Configuration Tab and then select the time Main Menu Option. This will display the System Date and Time Settings and the display is split into one main group section (refer to Figure 73). In addition, the time menu option has a single further sub-element. The further sub element is:

ntp. These are the NTP time settings. Figure 73: Time Settings An indication as to whether there are any User configurable parameters included in the group is provided. If the User wants to configure any of the parameters then they must enter the Edit Mode

(select Edit Private or Edit Exclusive) and edit as necessary. The methods to Edit the parameters will be offered via drop down menu. The System Date and Time Settings window contains:

System Time and Date. This is an indication of current date and time. This is not a User configurable parameter. Timezone. This is an indication of the timezone. The Use is free to select their respective timezone and multiple options are available via the dropdown menu. To view the Network Time Protocol Settings then at the Main Web GUI Interface Screen select the Configuration Tab, select time Main Menu Option and then ntp Main Menu Sub-Element. The display is split into two main grouping sections (figure 71). Network Time Protocol Settings. This is an indication as to whether NTP has been enabled. The options are enabled and disabled with disabled as the default. NTP Server Settings. This is an indication of the IP address, the NTP protocol version and whether the server is enabled of the NTP server. If the User wants to configure the NTP settings Page 82 PureWave Quantum 6600 User Guide v2.1 then they can edit, delete or add another NTP server. If the User enters the Edit mode for this parameter, then a further sub element with two more windows appear and the User can edit as required (refer to figure 72). The User can configure:

Ip-address. This is the IP Address of the NTP Server. o o Version. This is the protocol version of the NTP Server. o Enabled. This indicates whether the NTP Server is enabled. Figure 74: Time NTP Server Settings Figure 75: Time NTP Server Configuration Page 83 PureWave Quantum 6600 User Guide v2.1 To view the current System Time and Date Settings then at the Main Web GUI Interface Screen select the Configuration Tab, select time Main Menu Option and then the set Main Menu Sub-Element. The display is split into two main grouping sections (refer to Figure 76). Set System Time and Date. This is a text box that contains the Perform Command Menu Option. Set System Time and Date. The User is free to configure the Time and Date. The dialog time is specified in 24-hour format and includes milliseconds (Ms), which may simply be set to 0. TzH is the timezone hours offset from Coordinated Universal Time (UTC) and is between -23 and

+23. TzM is the timezone minutes offset from Coordinated Universal Time (UTC) and is between 0 and 59. Once these parameters have been configured, the User must select the Perform Command Menu Option for the changes to be effected. Figure 76: Time NTP Server System Set To view the NTP Time/Date Synchronization then at the Main Web GUI Interface Screen select the Configuration Tab, select time Main Menu Option, then ntp Main Menu Sub-Element and then ntpdate. The display is split into two main grouping sections (refer to Figure 77). NTP Time/Date Synchronization. This command will perform a one-time synchronization to the selected NTP server. To apply the User simply needs to select the Perform command button. NTP Time/Date Synchronization. The User can configure the NTP Server IP address to perform the one time synchronization with. Page 84 PureWave Quantum 6600 User Guide v2.1 Figure 77: Time NTP Server Synchronization Update 3.5.3.6 Telnet Settings At the Main Web GUI Interface Screen select the Configuration Tab and select the telnet Main Menu Option. This will display the /telnet/server Settings and the display is split into one main group section

(refer to Figure 78). There are no further sub-element associated with this option. The /telnet/server settings are:

Enabled. This indicates whether the telnet option has been enabled or not. This is a User configurable value that is edited via a check box. Figure 78: Telnet Server Enabled Page 85 PureWave Quantum 6600 User Guide v2.1 3.5.3.7 Telnet Settings At the Main Web GUI Interface Screen select the Configuration Tab and select the web Main Menu Option. This will display the web Settings and the display is split into two main grouping sections (refer to Figure 79). There are no further sub-element associated with this option. The main grouping sections are:

Web Server HTTP Support. This indicates the Base Station HTTP options. The configuration options are:

o Enabled. This indicates whether the HTTP Support option has been enabled or not. This is a User configurable value that is edited via a check box. The default configuration is disabled. o Port Number. This is the port number for HTTP Support. This is a User configurable value that is edited via a notepad icon. Web Server HTTPS Support. This indicates the Base Station HTTP options. The configuration options are:

o Enabled. This indicates whether the HTTPS Support option has been enabled or not. This is a User configurable value that is edited via a check box. The default option is enabled. o Port Number. This is the port number for HTTPS Support. This is a User configurable value that is edited via a notepad icon. Figure 79: Web Server HTTP Support 3.5.3.8 Configuration Settings All the Base Station configuration parameters are contained and stored local on the Base Station in flash memory, via a number of configuration files. The User has the complete control to perform a variety of functions such as copy, move, delete and restore etc on these files. This presents a User with an option, Page 86 PureWave Quantum 6600 User Guide v2.1 in the event that they would like to re-configure a Base Station or the Subscriber CPE profiles they can copy and export a configuration file which can then easily be edited and downloaded back onto the Base Station. This is an alternative approach to the screen by screen configuration method that is detailed in this User Guide. At the Main Web GUI Interface Screen select the Configuration Tab and select the configuration Main Menu Option. This will display the configuration Settings and the display is split into two main grouping sections (refer to figure 77). There are ten Main Menu Sub-Elements associated with the configuration Main Menu Option. The main grouping sections are:

Configuration File Operation Status. This indicates the Configuration File operation status when the User is downloading or uploading a configuration file. The parameters that are displayed are as follows. o State. This indicates execution state of the configuration command. It is not a configurable parameter and simply states the current status, for example Idle. o Download Progress. This provides an indication of the completion percentage of the configuration file that is being downloaded. This is not a configurable parameter. o Upload Progress. This provides an indication of the completion percentage of the configuration file that is being uploaded. This is not a configurable parameter. Configuration Files. This is a list of the configuration files on the Base Station. There is no configurable parameters for these files and the information that is presented for each file is:

o Name. o Size. The size of the file is in bytes. o Modified. This is the date and time that the file was last modified. The ten Main Menu Sub-Elements are essentially the actions that can be performed on a configuration file. The User is not required to be in Edit Mode to perform any of these actions, the action is presented to them directly at each Main Menu Sub-Element option. These are:

copy move delete export import write backup restore download upload files Page 87 PureWave Quantum 6600 User Guide v2.1 The Main Menu Sub-Elements will be examined in detail. The same display elements are presented when the User navigates to each of these 10 Main Menu Sub-Elements. The display is split into two main grouping sections (refer to Figure 80). The top grouping section provides a description and instructions of the action. The bottom grouping section provides the mechanism to perform the action. Another common theme throughout the Main Menu Sub-Element is the ability to select a configuration file for an action. The relevant files are presented to the User via a drop down menu or the files are listed under the files Main Menu Sub-Element option. To view the files then at the Main Web GUI Interface Screen select the Configuration Tab and select the files Main Menu Option. This will display all the relevant files. The explanation for each file is:

.cnf (configuration) files are created by the export command and can only be read by the import command. The data in the file is saved as a series of CLI commands. This file is in ASCII format and can be edited within a text editor. o profile.cnf file is the Base Station configuration file. o cpe.cnf is the Subscriber CPE configuration file. The backup.bak.tgz is the non-editable database backup configuration stored in a compressed format. This file is created with the backup command and can only be read by the restore command. Figure 80: Configuration Settings At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the copy Main Menu Sub-Element. This will display window to copy a configuration file. Page 88 PureWave Quantum 6600 User Guide v2.1 Figure 81: Configuration Copy Settings The procedure to copy a file is (refer to Figure 81):

Select the file to be copied from the drop down menu of the Existing File Name field. Enter the copied file name in the Copied File Name field. Enable the Force field if the User wants to overwrite an existing file on the Base Station. The User must then press the Perform Command Menu Option. The relevant file will now be copied and the results of this action will be displayed (Figure 82). Figure 82: Configuration Copy Successful Page 89

(1)

(2)

(3)

(4)

(5) PureWave Quantum 6600 User Guide v2.1 At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the move Main Menu Sub-Element. This will display window to move or rename a configuration file (Figure 83). Figure 83: Configuration Move Settings The procedure to rename a file is:

(1)

(2)

(3)

(4) Select the file to be renamed from the drop down menu of the Existing File Name field. Enter the new file name in the New File Name field. The User must then press the Perform Command Menu Option. The relevant file will now be renamed and the results of this action will be displayed. At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the delete Main Menu Sub-Element. This will display window to delete a configuration file (refer to Figure 84). Page 90 PureWave Quantum 6600 User Guide v2.1 Figure 84: Configuration Delete Settings The procedure to delete a file is:

(1)

(2) Select the file to be renamed from the drop down menu of the Filename field. The User must then press the Perform Command Menu Option. A prompt box will now appear and the User is requested to confirm "Do you really want to delete the file?".

(3) The relevant file will now be renamed and the results of this action will be displayed. Page 91 PureWave Quantum 6600 User Guide v2.1 At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the export Main Menu Sub-Element. This will display window to export a configuration file (refer to Figure 85). The export option creates an ASCII file that can be physically edited by the User. The file will be stored in flash on the Base Station and the User will have to upload it off the Base Station. Figure 85: Configuration Export Settings The procedure to export a file is:

Select the CLI export filter from the drop down menu of the CLI Export Filter. The options are:

All. This will export the entire configuration database except for Subscriber CPE provisioning. CPE. This will export the Subscriber CPE provisioning database only. Service-Profile. This will export the Service Profile database only. Enter the destination filename to export the database in the Filename field. The User must then press the Perform Command Menu Option. The relevant file will now be renamed and the results of this action will be displayed.

(1)

(2)

(3)

(4) At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the import Main Menu Sub-Element. This will display window to import a configuration file (refer to Figure 86). The import option will import a configuration into the running configuration. Page 92 PureWave Quantum 6600 User Guide v2.1 Overwriting the configuration file can have serious consequences. The User must proceed with care. Figure 86: Configuration Import Settings The procedure to import a file to the Base Station:

(1)

(2)

(3) Select the filename to import into the running configuration from the drop down menu of the Import Filename. If the User enables the Overwrite field, then this will replace the existing CPE configuration data with the imported data. This will only work with files created with the export CPE option. Trying to load other files with the overwrite option set will result in an error message. If the User does not enable the Overwrite field, then the imported data will be merged with the existing configuration.

(4) The User must then press the Perform Command Menu Option. The Import command can take several minutes to complete. Please wait until this process is completed before going on to make any other configuration changes. At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the write Main Menu Sub-Element. This will display window to write a configuration Page 93 PureWave Quantum 6600 User Guide v2.1 file (refer to Figure 87). The write procedure will copy the running configuration to startup. The new startup configuration will be effective at the next reboot of the Base Station. Please note that changes will not be persistent and survive a restart unless the write command is issued after the changes are made. Figure 87: Configuration Write Settings The procedure to write the configuration is:

(1) The User must then press the Perform Command Menu Option. A prompt box will now appear and the User is requested to confirm "Do you really want to write the file?".

(2) The relevant configuration will now be written and the results of this action will be displayed. At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the backup Main Menu Sub-Element. This will display window to backup a configuration file (refer to Figure 88). The backup procedure will create a binary backup of the entire database which is compressed into a tar.gz file. This is effectively the essence of the Base Station but it cannot be edited by the User. Page 94 PureWave Quantum 6600 User Guide v2.1 Figure 88: Configuration Backup Settings The procedure to backup a database is:

(1)

(2) Select the filename to create a binary backup of the database in the Filename field. The User must then press the Perform Command Menu Option. A prompt box will now appear and the User is requested to confirm "Do you really want to delete the file?".

(3) The relevant file will now be renamed and the results of this action will be displayed. At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the restore Main Menu Sub-Element. This will display window to restore a configuration file (refer to Figure 89). The procedure will restore a binary backup of the entire database. This procedure will affect a reboot of the Base Station. Figure 89: Configuration Restore Settings Page 95 PureWave Quantum 6600 User Guide v2.1 The procedure to restore a database is:

(1)

(2) Select the filename to restore a binary backup of the database in the Filename field. The User must then press the Perform Command Menu Option. A prompt box will now appear and the User is requested to confirm "Do you really want to delete the file?".

(3) The relevant file will now be renamed and the results of this action will be displayed. At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the download Main Menu Sub-element. This will display window to download a configuration file to a remote server (refer to Figure 90). Prior to downloading the file, the User must ensure that an FTP Server has been configured and is running. There are a number of free commercially available FTP Servers that can be used. A key step in the process is to ensure that the URL for the file is set to be the FTP Home directory. For the purposes of upload and download, think of the Base Station as client in relation to the FTP as the server. The download process will therefore download from the Server to the Base Station. Figure 90: Configuration Download Settings The procedure to download a file from a remote server is:

(1) Enter the remote server source configuration URL in the FTP/HTTP/HTTPS URL field. Acceptable examples are:

ftp://192.168.10.1/filename http://my.host-name.com/dir/filename ftp://username:password@noc.big_co.com:2323/dir/filename Page 96 PureWave Quantum 6600 User Guide v2.1

(2)

(3) Enter the destination configuration used filename used for the Base Station is the Destination Filename field. The User must then press the Perform Command Menu Option. A prompt box will now appear and the User is requested to confirm "Do you want to download the file?".

(4) The relevant file will now be downloaded and the results of this action will be displayed. At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the upload Main Menu Sub-Element. This will display window to upload a configuration file to a remote server (refer to Figure 91). Prior to uploading the file, the User must ensure that a FTP Server has been configured and is running. Figure 91: Configuration Upload Settings The procedure to upload a file to a remote server is:

(1)

(2) Enter the configuration source filename in the Source Filename field. Enter the remote server destination file URL in the FTP/HTTP/HTTPS URL field. Acceptable examples are:

ftp://192.168.10.1/filename http://my.host-name.com/dir/filename ftp://username:password@noc.big_co.com:2323/dir/filename

(3) The User must then press the Perform Command Menu Option. A prompt box will now appear and the User is requested to confirm "Do you want to upload the file?".

(4) The relevant file will now be uploaded and the results of this action will be displayed. Page 97 PureWave Quantum 6600 User Guide v2.1 To ensure that the User has a stored backup of the running configuration file, then the User would export and then upload the relevant files. To restore a previously stored file from its remote location, then the User would download and then import. 3.5.4 Connecting a Subscriber Station The procedures for provisioning each make and model of Subscriber CPE device vary and hence are beyond the scope of this document. However, PureWave have prepared general documentation that details recommend procedures to configure specific Subscriber units. Please refer to this documentation for further details. When a Subscriber CPE is powered on and configured for an appropriate Base Station, if that Base Station is configured for auto-provisioning, the Subscriber CPE will automatically connect to the Base Station and it will be assigned the default Client Profile (Client Profile 1). The User however has the complete flexibility to pre-configure the Subscriber CPE and has the capability to assign it to a specific Client Profile. The procedure to configure a Subscriber CPE is:

For the particular Subscriber CPE that you wish to provision please record the Subscriber MAC address. This is written on the CPE label. At the Main Web GUI Interface Screen select the Configuration Tab and then the cpe Main Menu Option. This will display a list of all Subscriber CPEs that have been specifically configured on the Base Station (refer to Figure 92). If there are none listed then none have been configured. Figure 92: CPE Main Menu Option Page 98

(1)

(2) PureWave Quantum 6600 User Guide v2.1

(3) The User now has to enter the Edit Mode (select Edit Private or Edit Exclusive). The <Add cpe>

option will appear (refer to Figure 93). Figure 93: Add Subscriber CPE Option

(4) The User must select the <Add cpe> option. A Key Settings window will appear. The User is prompted to enter the Subscriber CPE MAC Address. The MAC Address must be entered in Upper Case letters only and using a colon (:) to separate the digits, e.g. 00:17:C4:8F:9B:34. If the User selects the ? Command Menu Option within the window then a reminder prompt will be displayed. Once the MAC Address has been entered the User must select the Add command button (refer to Figure 94). Figure 94: Add Subscriber CPE MAC Address Page 99 PureWave Quantum 6600 User Guide v2.1 The User will now be presented with the Subscriber configuration options. The options to select are (refer to Figure 95):

Convergence Sublayer Type. The User can select from a drop down menu. The default option is Ethernet_CS and the available options are:

IPV4_CS o o ETHERNET_CS . This is the default setting, the Base Station operates in Standalone mode. Client Profile. This profile can be selected from a drop down menu. The User can select

<unset> or from one of the user configured profiles (1 through 8). IP Address. Applicable/Visible only when the CPE is configured for IPV4_CS Convergence Sublayer mode and the base station operated in Stand Alone mode. 0.0.0.0 value (default) means that the CPE will obtain its IP address through DHCP Server. When changed from the defaults value a static IP address is used for the Provisioning. The CPE device must be configured with the same IP address. IP Netmask. Applicable/Visible only when the CPE is configured for IPV4_CS Convergence Sublayer mode and the base station operated in Stand Alone mode. Defines the Subnet Mask. Currently only a single IP Address is possible, thus the default value of 255.255.255.25.255 should not be changed!

Customer ID. This is a free format text field that enables the User to uniquely define a Subscriber. This is edited by selecting the notepad icon. Maximum Uplink Rate. The User can select the maximum uplink modulation rate. This will effectively provide a cap on the maximum data traffic rate. This direction is defined as the Subscriber to Base Station. This is selected via the drop down menu and the options are:

o QAM64 5/6 o QAM64 3/4 o QAM64 2/3 o QAM64 1/2 o QAM16 3/4 o QAM16 1/2 o QPSK 3/4 o QPSK 1/2 Maximum Downlink Rate. The User can select the maximum downlink modulation rate. This will effectively provide a cap on the maximum data traffic rate. This direction is defined as the Base Station to Subscriber. This is selected via the drop down menu and the options are:

o QAM64 5/6 o QAM64 3/4 o QAM64 2/3 o QAM64 1/2 o QAM16 3/4 o QAM16 1/2 o QPSK 3/4 o QPSK 1/2 Page 100

(5) PureWave Quantum 6600 User Guide v2.1 Figure 95: Add Subscriber CPE Settings

(6) Once the Subscriber options have been selected, the User can then Validate the changes. The User simply selects the Validate command button. A window indicating whether the Validation is successful or not will appear (refer to Figure 96). If successful then the User has to select the OK command button. Figure 96: Add Subscriber CPE Validation

(7) After performing the Validation, the final step is to execute the Commit procedure. The User simply has to select the Commit command button. A window prompting the User to commit the changes will appear. To effect the commit the User has to select the OK command button (refer to Figure 97). A further window indicating that the commit changes succeeded will appear. Page 101 PureWave Quantum 6600 User Guide v2.1 Figure 97: Add Subscriber CPE Commit

(8) The Subscriber configuration details will now be displayed. Figure 98: Subscriber CPE Configured Settings If the User wants to delete a previously configured Subscriber, then the option to delete is available. When the User is in the Edit Mode, there is a red cross box positioned next to the end of the Subscriber MAC Address listing. If the User positions the cursor over the box then the message Remove cpe:cpe appears (refer to Figure 99). The User simply selects this box. The User must then commit the changes. Page 102

(9) PureWave Quantum 6600 User Guide v2.1 Figure 99: Subscriber CPE Delete 3.5.5 Subscriber CPE Client Profiles The process to create a QoS (Quality of Service) Client Profile on the Subscriber CPE is relatively straightforward. The basic concept flow diagram is detailed in Figure 100. Figure 100: Subscriber CPE Provisioning Flow Concepts The Service Profile system through the use of Client Profiles, create multiple data connections that suit the need of the Operator or Service Level Agreements. The Client Profile is the top level in a complex hierarchy that provides a large degree of flexibility in service offerings. Page 103 PureWave Quantum 6600 User Guide v2.1 Client Profiles are assigned to individual Subscriber CPEs and within each client profile there is the ability to throttle throughput, and organize types of traffic into specific connection types. The use of ARQ/HARQ is also contained within this system. The Subscriber CPE Client Profile contains a Service Flow for both the uplink and the downlink directions. The Service Flow is created from the following components:

The direction of flow of traffic The specific Quality of Service (QoS) type, e.g. Best Effort (BE) or Unsolicited Grant Service

(UGS) etc that is to be applied. ARQ and/or HARQ definitions. These are the error recovery mechanisms. Packet Classifiers. This will classify on a packet by packet basis depending on the defined classification criteria. For example, the conditions under which the packet is to be transported and/or which Service flow it is to be assigned. A Client Profile is a set a Service Flows that correspond to a specific Service Level Agreement assigned to a customer. Each Client Profile supports up to 16 service flows and each service flow is uni-

directional. A set of service flows includes an Uplink and a Downlink direction. Tip When designing Client Profiles, it is important to understand how the throughout rating mechanism works. In the event of contradicting parameters being set, the system will allocate to a Subscriber CPE the lower of the parameters. For example, assume a conflict between the Client Profile setting the maximum uplink rate of 2Mbps and the QoS Profile setting the maximum sustained rate to 1Mbps. In this example, the system will limit the uplink rate to 1Mbps. Figure 101 demonstrates a typical "Best Effort" type of Client Profile. Consider a packet that is flowing in the downlink direction (i.e. Base Station to Subscriber CPE). The same concept applies in the uplink direction. A packet flow from the network and into the Base Station. It is destined for the Subscriber CPE. The packet is then processed by the Classifiers rules that have been defined. In this example these are the Downlink Packet Classifier. If the packet is subject to the Classifier rule then it is processed and classified as defined by that rule. Packets that are not subject to the rule are then identified as a Non Classified Packet. The Non Classified Packets are then passed out of the Base Station and are now subject to the relevant Service Flow definitions. In this example this would be Best Effort. Page 104 PureWave Quantum 6600 User Guide v2.1 Figure 101: Typical Best Effort Client Profile Figure 99 demonstrates a more complex but still typical "Voice and Data" type of application. In this example these is a VoIP Packet Classifier defined. This has been associated to an eRTPS Service Flow. Non Classifier packets have been set to a Best Effort Service Flow. Any packet that enters from the Network will be tested against the Classifier rules. A VoIP packet will therefore be transmitted downlink via eRTPS and everything else via Best Effort. Figure 102: Typical Voice and Data Client Profile Page 105 PureWave Quantum 6600 User Guide v2.1 By default the Base Station is pre-configured with a number of profiles for Classifier, HARQ, ARQ, QoS and Client. The User has the complete freedom and flexibility to use these pre-defined profiles or they can edit accordingly. At Main Web GUI Interface Screen select the Configuration Tab and then the service-profile Main Menu Option. This window details the information for the service profile Main Menu Option. There are five Main Menu Sub-Elements and window is split into five main grouping sections (refer to Figure 103). The five main grouping sections provide a summary of the information that can be obtained by selecting and navigating down into the Main Menu Sub-Element level. Figure 103: Service Profile Menu Option The Main Menu Sub-Elements are:

cls-profile. These are the Classifier profiles. harq-profile. These are the Hybrid ARQ (automatic recovery) profiles. arq-profile. These are the ARQ profiles. qos-profile. These are the Quality of Service profiles. client-profile. These are the Client profiles. This just provides an indication of the information that is displayed. A description of the variables will be provided when the Main Menu Sub-Elements are described. The five main grouping sections are:

Classifier Profiler. The User can define up to 64 Classifier profiles. A list of profiles (up to 16 at a time) and the following information is displayed for each Classifier:

o Profile #

o Name o Description o Cls-priority o Cls-priority-used Page 106 PureWave Quantum 6600 User Guide v2.1 o Eth-type o Eth-type-used o Ip-tos-dscp Hybrid ARQ Profile. The User can define up to 8 profiles and the following information is displayed for each profile:

o Profile #

o Name o Description o Enable o Channel-mapping o Num-retries o Pdu-sn-support ARQ Profile. The User can define up to 3 profiles and the following information is displayed for each profile:

o Profile #

o Name o Description o Enable o Deliver-in-order o Window-size o Timeout-tx-delay o Timeout-rx-delay QoS Profile. The User can define up to 16 profiles and the following information is displayed for each QoS profile:

o Profile #

o Name o Max-sustained-traffic-rate o Max-latency o Data-delivery-service o Traffic-priority o Max-traffic-burst Client Profile. The User can define up to 8 profiles and the following information is displayed for each Client profile:

o Profile #

o Description o Max-dl-rate o Max-pps o Max-ul-rate o Min-dl-reserved-rate o Min-ul-reserved-rate Page 107 PureWave Quantum 6600 User Guide v2.1 At Main Web GUI Interface Screen select the Configuration Tab and then the service-profile Main Menu Option. If the User now enters the Edit Mode, then they can either Edit or Delete any of all the profiles that have been configured as a default. If the User decides to Edit any of these profiles then they are immediately navigated to the relevant Main Menu Sub-Element level. The information that is presented at the service-profile Main Menu Option level is simply a summary of what is actually available for each of the profiles. The User can navigate to the respective Main Menu Sub-Element level for full viewing and configuration capabilities. If the User wants to configure any of the parameters then they must enter the Edit Mode

(select Edit Private or Edit Exclusive) and edit as necessary. The methods to Edit the parameters will be offered via a drop down menu of choices, an enabling of a check box or editing of a notepad icon. These Profiles will now be described in detail. 3.5.5.1 Classifier Profile This profile will classify on a packet by packet basis depending on the defined classification criteria. For example, the conditions under which the packet is to be transported and/or which Service flow it is to be assigned. At Main Web GUI Interface Screen select the Configuration Tab, then the service-profile Main menu Option and then the cls-profile Main Menu Sub-Element. This User is presented with all the 64 pre-

configured default profiles. These are displayed 16 at a time. To physically view all the profile configuration parameters then the User must actually select a profile and two main grouping sections are presented (refer to Figure 104). Figure 104: Service Profile Classifier Profile Page 108 PureWave Quantum 6600 User Guide v2.1 The main grouping sections are:

Key settings. This simply displays:

o Profile #

Classifier Profile. This displays all that the available configuration parameters. These are:

o Name. This is the profile name and it is a text field o Description. This is the profile description and it is a text field. o Cls-priority. This User can assign a priority to the classifier. The priority is assigned as a number in the range 0 to 255. The default priority is 0 (no priority). o Cls-priority-used. This is a check box to enable/disable the priority rule. o Eth-type. This is the Ethernet Type. This is assigned as a number in the range 1501 to 65535. This represents the value in decimal format. o o o Eth-type-used. This is a check box to enable/disable the Ethernet Type rule. o Ip-tos-dscp. This is the IP TOS Descriptor. This is assigned as a number in the range 0

(default) to 63. Ip-tos-dscp-used. This is a check box to enable/disable the IP TOS Descriptor rule. Ip-protocol. This is the IP Protocol. This is assigned as a number in the range 0 (default) to 255. Ip-protocol-used. This is a check box to enable/disable the IP Protocol rule. o o Dest-ip-addr-prfx. This is the IP Destination Address and Prefix (mask length). Configuration examples are 192.0.0.0/2, 192.168.0.0/3, 192.1468.254.0/23 and 192.168.1.1/32. o Dest-ip-addr-used. This is a check box to enable/disable the IP Destination Address rule. o Src-ip-addr-prfx. This is the IP Source Address and Prefix (mask length). Configuration examples are 192.0.0.0/2, 192.168.0.0/3, 192.1468.254.0/23 and 192.168.1.1/32. o src-ip-addr-used. This is a check box to enable/disable the IP Source Address rule. o Dest-port-start. This is the Destination Port Low Limit. This is assigned as a number in the range 0 (default) to 65535. o Dest-port-end. This is the Destination Port High Limit. This is assigned as a number in the range 0 (default) to 65535. o Dest-ip-port-used. This is a check box to enable/disable the Destination Port rule. o Src-port-start. This is the Source Port Low Limit. This is assigned as a number in the range 0 (default) to 65535. o Src-port-end. This is the Source Port High Limit. This is assigned as a number in the range 0 (default) to 65535. o Src-ip-port-used. This is a check box to enable/disable the Source Port rule. o Vlan-id. This is the VLAN ID Tag. This is assigned as a number in the range 0 (default) to 4095. o Vlan-id-used. This is a check box to enable/disable the VLAN ID rule. o Vlan-user-priority-low. This is the VLAN User Priority Low Byte. This is assigned as a number in the range 0 (default) to 7. Page 109 PureWave Quantum 6600 User Guide v2.1 o Vlan-user-priority-high. This is the VLAN User Priority High Byte. This is assigned as a number in the range 0 (default) to 7. o Vlan-user-priority-used. This is a check box to enable/disable the VLAN User Priority rule. The System is pre-configured with 64 default profiles. If the User wants to add any of their own configurations, they must delete a profile before they can add and configure a new one. When in Edit mode, the User is presented with (refer to Figure 105):

<Add cls-profile>. If the User selects this option and there is available profile to be added then they can simply add and then they will be dropped directly into the configuration window. A List of all the profiles with a red box beside each profile. If the User navigates to the red icon then this will present the User with the ability to delete the profile. Figure 105: Service Profile Classifier Profile Edit Capability 3.5.5.2 HARQ Profile At Main Web GUI Interface Screen select the Configuration Tab, then the service-profile Main Menu option and then the harq-profile Main Menu Sub-Element. This User is presented with all the 6 pre-

configured default profiles. To physically view all the profile configuration parameters then the User must actually select a profile and two main grouping sections are presented (refer to Figure 106). Page 110

PureWave Quantum 6600 User Guide v2.1 Figure 106: Service Profile HARQ Profile The main grouping sections are:

Key settings. This simply displays:

o Profile #

Hybrid ARQ Profile. This displays all that the available configuration parameters . These are:

o Name. This is the profile name and it is a text field o Description. This is the profile description and it is a text field. o Enable. This is a check box to enable/disable the HARQ profile. o Channel-mapping. This is the HARQ Map Length. This is assigned as a number in the range 0 to 16 with a default of 4. o Num-retires. This is the HARQ Number of Retries. This is assigned as a number in the range 0 to 16 with a default of 1. o Pdu-sn-support. This is the HARQ PDU SN Support. The options are none, short (default) and long. The System is pre-configured with 6 default profiles. If the User wants to add any of their own configurations, they must delete a profile before they can add and configure a new one. When in Edit mode, the User is presented with (refer to Figure 107):

<Add harq-profile>. If the User selects this option and there is available profile to be added then they can simply add and then they will be dropped directly into the configuration window. A List of all the profiles with a red box beside each profile. If the User navigates to the red icon then this will present the User with the ability to delete the profile. Page 111 PureWave Quantum 6600 User Guide v2.1 Figure 107: Service Profile HARQ Profile Edit Capability 3.5.5.3 ARQ Profile At Main Web GUI Interface Screen select the Configuration Tab, then the service-profile Main Menu option and then the arq-profile Main Menu Sub-Element. This User is presented with all the 3 pre-

configured default profiles. To physically view all the profile configuration parameters then the User must actually select a profile and two main grouping sections are presented (refer to Figure 108). Figure 108: Service Profile ARQ Profile Page 112 PureWave Quantum 6600 User Guide v2.1 The main grouping sections are:

Key settings. This simply displays:

o Profile #

ARQ Profile. This displays all that the available configuration parameters. These are:

o Name. This is the profile name and it is a text field o Description. This is the profile description and it is a text field. o Enable. This is a check box to enable/disable the ARQ profile. o Deliver-in-order. This is a check box to enable/disable the ARQ deliver in order option. o Window-size. This is the ARQ Window Size. This is assigned as a number in the range 1 to 1024 (default). o Timeout-tx-delay. This is the ARQ Transmit Retry Timeout Delay. This is assigned in units of 5msec in the range 0 to 1310 with a default of 5 (25msec). o Timeout-rx-delay. This is the ARQ Receive Retry Timeout Delay. This is assigned in units of 5msec in the range 0 to 1310 with a default of 5 (25msec). o Block-lifetime. This is the ARQ Transmit Retry Timeout Delay. This is assigned in units of 5msec in the range 0 to 1310 with a default of 5 (25msec). o Sync-loss. This is the ARQ Sync Loss Timeout. This is assigned in units of 5msec in the range 0 to 1310 with a default of 120 (600msec). o Purge-timeout. This is the ARQ Purge Timeout. This is assigned in units of 5msec in the range 0 to 1310 with a default of 32 (160msec). o Block-size. This is the ARQ Block Size. The options are 16, 32, 64, 128 (default), 256, 512 and 1024. o Ack-processing-time. This is the ARQ Acknowledge Processing Time. This is assigned as a number in msec in the range 0 (default) to 255. The System is pre-configured with 6 default profiles. If the User wants to add any of their own configurations, they must delete a profile before they can add and configure a new one. When in Edit mode, the User is presented with:

<Add arq-profile>. If the User selects this option and there is available profile to be added then they can simply add and then they will be dropped directly into the configuration window. A List of all the profiles with a red box beside each profile. If the User navigates to the red icon then this will present the User with the ability to delete the profile (refer to Figure 109). Page 113 PureWave Quantum 6600 User Guide v2.1 Figure 109: Service Profile ARQ Profile Edit Capability 3.5.5.4 Quality of Service, QoS Profile A QoS Profile contains all information in regards to QoS type, latency, throughput and etc. These Profiles are independent of direction and can be applied to multiple service flows. The types of QoS that are offered are:

Best Effort or BE. Alternatively this is described as MIR or Maximum Information Rate. Unsolicited Grant Service or UGS. An alternative for this is CIR or Committed Information Rate. Extended Real-Time Polling Service or eRTPS. This is also known as Dynamic CIR. Best Effort is by far the most commonly used QoS type that is configured in the majority of deployments. It is bursty in nature and provides for up to a maximum rate. As an example, it could provide for internet speeds of up to 3 Mbps. The disadvantage of a Best Effort Service is that it does not provide any guarantee that the configured throughput will be achieved. A Base Station will offer throughput to BE configured Subscribers as long as there is bandwidth available and there are no other CIR configured Subscriber demanding throughput Unsolicited Grant Service connections provide for a dedicated and guaranteed Service Level Agreement. It is typically used for applications that require constant bit rate services such as VoIP. Any traffic assigned to a UGS service flow will be allocated for the sole use by that Subscriber. The allocated traffic for this UGS will be removed from the available pool of throughput for the Base Station to which the Subscriber has been configured. UGS connections typically provide low latency which is ideal for VoIP applications. Extended Real-Time Polling Service is a QoS type that is very similar to UGS. Traffic is allocated for the sole use by a Subscriber CPE but only when the Subscriber CPE requests traffic. However, when traffic is Page 114 PureWave Quantum 6600 User Guide v2.1 not being requested by the Subscriber, the allocated eRTPS bandwidth can be used by any other Subscriber. The eRTPS is the preferred QoS type for VoIP applications due to the dynamic resource control. There are 16 QoS profiles that have been pre-configured and stored in the Base Station. These can be viewed at the summary level (refer to Figure 110). At Main Web GUI Interface Screen select the Configuration Tab and then select the service-profile Main Menu Sub-Element. For full examination and configuration of the QoS profiles then the User needs to navigate into the Main Menu Sub-Element level. Figure 110: Default Quality of Service Profiles At Main Web GUI Interface Screen select the Configuration Tab, then the service-profile Main Menu Option and then the qos-profile Main Menu Sub-Element. This User is presented with all the 16 pre-

configured default profiles (refer to Figure 111). To physically view all the profile configuration parameters then the User must actually select a profile and two main grouping sections are presented. Page 115 PureWave Quantum 6600 User Guide v2.1 Figure 111: Quality of Service Profiles The main grouping sections are:

Key settings. This simply displays:

o Profile #

QoS Profile. This displays all that the available configuration parameters. These are:

o Name. This is the profile name and it is a text field. o Description. This is the profile description and it is a text field. o Max-sustained-traffic-rate. This is a Maximum Sustained Traffic Rate. This is assigned in bits per second in the range 0 to 4294967295. o Max-latency. This is a Maximum Latency. This is assigned in milliseconds in the range 0 to 65535. o Data-delivery-service. This is the Data Delivery Service. The options that are available via a dropdown menu are UGS_Service, RTP_Service, nRTP_Service, BE_Service and eRTP_Service. o Traffic-priority. This is the Traffic Priority Level. This is assigned as a number in the range 0 (default) to 7. o Max-traffic-burst. This is a Maximum Traffic Burst Size. This is assigned in bits per second in the range 0 to 4294967295. o Min-reserved-traffic-rate. This is a Maximum Reserved Traffic Rate. This is assigned in bits per second in the range 0 to 4294967295. o Tolerated-jitter. This is a Tolerated Jitter. This is assigned in milliseconds in the range 0 to 65535. o Unsolicited-grant-interval. This is a Unsolicited Grant Interval. This is assigned as a number in the range 0 to 65535. Page 116 PureWave Quantum 6600 User Guide v2.1 o Unsolicited-poll-interval. This is a Unsolicited Poll Interval. This is assigned as a number in the range 0 to 65535. The System is pre-configured with 16 default profiles. If the User wants to add any of their configurations, they must delete a profile before they can add and configure a new one. When in Edit mode, the User is presented with (refer to Figure 112):

<Add qos-profile>. If the User selects this option and there is available profile to be added then they can simply add and then they will be dropped directly into the configuration window. A List of all the profiles with a red box beside each profile. If the User navigates to the red icon then this will present the User with the ability to delete the profile. Figure 112: Quality of Service Edit Capability 3.5.5.5 Client Profile A Client Profile is a set a Service Flows that correspond to a specific Service Level Agreement assigned to a customer. The system is pre-configured with 8 Client Profiles and each Profile must be configured with an Uplink and a Downlink Service Flow. Therefore, each Client Profile supports up to 16 service flows and each service flow is uni-directional. At Main Web GUI Interface Screen select the Configuration Tab, then the service-profile main menu option and then the client-profile main Menu Sub-Element. This User is presented with all the 8 pre-

configured default profiles. To physically view all the profile configuration parameters then the User must actually select a profile and three main grouping sections are presented (refer to Figure 113). Page 117 PureWave Quantum 6600 User Guide v2.1 Figure 113: Client Profile The main grouping sections are:

Key settings. This simply displays:

o Profile #

ARQ Profile. This displays all that the available configuration parameters. These are:

o Description. This is the profile description and it is a text field. o Max-dl-rate. This is a Maximum Downlink Rate that is reserved for this client. This is assigned in bits per second in the range 0 to 4294967295. o Max-pps. This is a Maximum Packets per second. This is assigned as a number in the range 0 to 65535. o Max-traffic-burst. This is a Maximum Client Traffic Burst. This is as a number in the range 0 to 4294967295. o Max-ul-rate. This is a Maximum Uplink Rate for this client. This is assigned in bits per second in the range 0 to 4294967295. o Min-dl-reserved-rate. This is a Minimum Downlink Rate that is reserved for this client. This is assigned in bits per second in the range 0 to 4294967295 o Min-ul-reserved-rate. This is a Minimum Uplink Rate for this client. This is assigned in bits per second in the range 0 to 4294967295 o Name. This is the profile name and it is a text field. o Num-sflow. This is the Number of Service Flows for the Client Profile. This is as a number in the range 1 to 16. o Priority. This is the Traffic Priority for this Client. This is assigned as a number in the range 1 to 8. Service Flow Profile. This lists all the Service Flow Profiles. The configurable parameters for each Service Flow Profile are:

o Profile #. This is the number of the Client profile. o Name. This is the name of the Client profile. Page 118 PureWave Quantum 6600 User Guide v2.1 o Description. This is the text description of the Client profile. o Direction. This is the direction of the traffic flow. o Arq-profile-num. This is the number of the arq profile that has been assigned for this Client Profile. o Cls-profile-num. This is the number of the classifier profile that has been assigned for this Client Profile. o Harq-profile-num. This is the number of the harq profile that has been assigned for this Client Profile. o Qos-profile-num. This is the number of the QoS profile that has been assigned for this Client Profile. To define a Client profile then the User must be in the Edit Mode. There are two ways to edit and configure a Client Profile.

(1) At the Main Web GUI Interface Screen select the Configuration Tab, then the service-profile Main Menu Option and then the client-profile Main menu Sub-Element. This User must then select the Client Profile that they wish to configure and scroll down to the bottom of the Window. They will be presented with the Service Flow Profile (refer to Figure 114). If the User enters the Edit Mode then at the end of each profile the Edit and Delete Command Menu Options will appear. The User can select the Edit Command Menu option and they will be navigated into the Edit Mode. Figure 114: Client Profile Edit Capability The User can navigate direct to the Service Flow Profile options. At the Main Web GUI Interface Screen select the Configuration Tab, then the service-profile Main Menu Option, then the client-profile Main Menu Sub-Element, then the relevant profile #, then sflow-profile and finally the relevant profile #. The User is presented with two main grouping sections. The User must be in Edit Mode to configure any of the parameters (refer to Figure 115). When in Edit Mode if the Page 119

(2) PureWave Quantum 6600 User Guide v2.1 User navigates to the red icon then this will present the User with the ability to delete the profile. Figure 115: Client Profile Edit Full Capability The main grouping sections are:

Key settings. This simply displays:

o Profile #

Service Flow Profile. This displays all that the available configuration parameters. These are:

o Name. This is the Service Flow name and it is a text field. o Description. This is the Service Flow description and it is a text field. o Direction. This is the direction of traffic flow for the Service Flow. The options are downlink or uplink. o Arq-profile-num. This is the ARQ Profile Number that is used by this Service Flow. The options are any of the 3 ARQ profiles that have been configured in the ARQ Profile configuration (refer to section 3.5.5.3). o Cls-profile-num. This is the CLS Profile Number that is used by this Service Flow. The options are any of the 64 CLS profiles that have been configured in the CLS Profile configuration (refer to section 3.5.5.1). o Harq-profile-num. This is the HARQ Profile Number that is used by this Service Flow. The options are any of the 6 HARQ profiles that have been configured in the HARQ Profile configuration (refer to section 3.5.5.2). o Qos-profile-num. This is the QoS Profile Number that is used by this Service Flow. The options are any of the 16 QoS profiles that have been configured in the QoS Profile configuration (refer to section 3.5.5.4). Page 120 PureWave Quantum 6600 User Guide v2.1 3.6 Base Station Software Upgrade One of the Base Stations key features is that it has been designed to support a Software Defined Radio (SDR) architecture. The distinct advantage is that a Base Station can be remotely upgraded with additional features and capabilities as these are developed. The Base Station maintains two software versions/images that may be selectively enabled, thus providing a fail-safe software upgrade procedure. The software upgrade process may be performed from the CLI, the Web Interface, as well as from the PureView EMS. In this section, the software upgrade procedures using the Web Interface is detailed. The first step in the process is to copy the software to a directory on the PC which is running the FTP server. Please ensure the PureWave directory structure is kept intact. Copy the software image, as provided by PureWave, to the assigned home directory of the FTP server (Figure 116). Figure 116: Software Components The next step is to confirm and setup the FTP Server. There are a number of free commercially available FTP Servers that can be used (refer to Figure 117, which is a 3CDaemon). Ensure that the FTP Server is running. Page 121 PureWave Quantum 6600 User Guide v2.1 Figure 117: FTP Server Configuration At the Main Web GUI Interface Screen select the Configuration Tab and then the software Main Menu Option. This will display the software Settings and the display is split into two main grouping sections. There are three further sub-element associated with this option. There are no User configurable options for the software Main Menu Option. The Base Station flash contains two partitions which are both loaded with software. There is a partition A and a partition B. The GUI will provide an indication as to current status of the software. The two main grouping sections for this Menu Main Sub-Element are (refer to Figure 118):

Software Image Management. This displays the details for each software image. The options are:

o Current Boot. This indicates which partition provided the current active software load. o Next Boot. This indicates after the next reboot of the Base Station, which partition the software will be loaded from. o Boot Partition A. This indicates the software revision that is currently loaded into partition A. o Boot Partition B. This indicates the software revision that is currently loaded into partition B. o Sw Version Candidate. This is not relevant for the current method of software upgrade. It will simply indicate "No Software candidate available". Software Image Status. This provides an indication of the download status. The options are:

o State Detail. This will provide an indication of the current state of software upgrade detail. o Download Progress. This is a percentage indicator of the state of download progress. Page 122 PureWave Quantum 6600 User Guide v2.1 Figure 118: Software Image Management Dialog 3.6.1 Single-Step Software Upgrade The Base Station software upgrade process can be performed using a single operation. This performs the following procedure while providing continual upgrade status to the User.

(1)

(2)

(3)

(4)

(5) Downloads the software image file from a user defined location using FTP, HTTP, or HTTPS. Unpacks the downloaded software image, verifies the image integrity (CRC and MD5 checksum), and prepares for installation. Performs a complex set of operations to upgrade the various components of the Base Station. Selects the new software image installed in the secondary partition as the partition to be used after the next Base Station reboot. Reboots the Base Station. To execute the Single-Step Software Upgrade Procedure, at the Main Web GUI Interface Screen the Configuration Tab, then the software Main Menu Option and then the upgrade Main Menu Sub-

Element. The User will be presented with two main grouping sections (refer to Figure 119). In the Download, Install, Select Software Image and Reboot section, enter the URL of the new software image in the SW Image URL box. There are a variety of formats of the URL of remote source file is. These can be displayed if the User selects the "help" key. These URL formats are defined as:

ftp://[user[:password]@]hostname[:port]/filepath http://hostname[:port]/filepath https://hostname[:port]/filepath Where [ ] indicates optional items. Thus, Page 123 PureWave Quantum 6600 User Guide v2.1 user:password@ is optional, and the :password part can be omitted

[:port] is also optional Examples using ftp (you can substitute http or https):

ftp://myhost.com/filename ftp://myhost.com/directory/filename ftp://myhost.com:2323/directory/filename ftp://myname@myhost.com:2323/directoryname/filename ftp://myname:password@myhost.com:2323/directoryname/filename URL of remote source file; format is as follows:

protocol://[user[:password]]@host[:port]/path protocol can be ftp, http, or https Figure 119: Single-Step Software Upgrade Dialog Once the URL has been entered, the User must select the Perform Command Menu Option in the Download Software Images, install, select and reboot on Base Station section to initiate the upgrade process. This action will upgrade the Base Station in one simple step. It will:

Transfer the software to the relevant partition on the Base Station. The software will always be loaded into the non Current Boot partition. For example, if the Current Boot is A, then the software will be loaded into B. Write the software into the relevant partition flash. This step will automatically change the next boot option to the other partition from which it currently is. This is of course the partition to which the software has just been downloaded. Page 124

(1)

(2) PureWave Quantum 6600 User Guide v2.1

(3) Automatically reboot the Base Station. The reboot will then automatically be loaded from the next boot partition which was changed in step (2) above. This means that the Base Station will now be operational on the software that was just downloaded. 3.6.2 Multi-Step Software Upgrade The Base Station software upgrade process can also be performed in multiple steps as an alternative to the single step process. This will present the User with better control over the various stages of the software upgrade process. 3.6.2.1 Software Download and Installation In this procedure the following steps are performed:

(1)

(2)

(3) Downloads the software image file from a user defined location using FTP, HTTP, or HTTPS. Unpacks the downloaded software image, verifies the image integrity (CRC and MD5 checksum), and prepares for installation. Performs a complex set of operations to upgrade the various components of the Base Station. The first step is the software download and installation procedure. At the Main Web GUI Interface Screen select the Configuration Tab, then the software Main Menu Option and then the install Main Menu Sub-Element. The User will be presented with two main grouping sections (refer to Figure 120). In the Download and Install Software Images section, then enter the URL of the new software image in the SW Image URL box. There are a variety of formats of the URL of remote source file is. These can be displayed if the User selects the "help" key. These URL formats are defined as:

ftp://[user[:password]@]hostname[:port]/filepath http://hostname[:port]/filepath https://hostname[:port]/filepath Where [ ] indicates optional items. Thus, user:password@ is optional, and the :password part can be omitted

[:port] is also optional Examples using ftp (you can substitute http or https):

ftp://myhost.com/filename ftp://myhost.com/directory/filename ftp://myhost.com:2323/directory/filename ftp://myname@myhost.com:2323/directoryname/filename ftp://myname:password@myhost.com:2323/directoryname/filename URL of remote source file; format is as follows:

Page 125 PureWave Quantum 6600 User Guide v2.1 protocol://[user[:password]]@host[:port]/path protocol can be ftp, http, or https Figure 120: Software Download and Installation Dialog Once the URL has been entered, the User must select the Perform Command Menu Option in the Download Software Images, install, select and reboot on Base Station section to initiate the upgrade process. This action will upgrade the Base Station in one simple step. It will:

(1) Transfer the software to the relevant partition on the Base Station. The software will always be loaded into the non Current Boot partition. For example, if the Current Boot is A, then the software will be loaded into B. 3.6.2.2 Software Partition Selection and Display The final step in the Multiple Step Software Upgrade process is the software partition selection and display procedure. At the Main Web GUI Interface Screen select the Configuration Tab, then the software Main Menu Option and then the boot Main Menu Sub-Element. The User will be presented with two main grouping sections (refer to Figure 121):

Select Next SW Image to Boot from Select Software Image Page 126 PureWave Quantum 6600 User Guide v2.1 Figure 121: Software Partition Selection and Display The purpose of the Select Next SW Image to Boot from is that this command will allow the selected image to run after the next reboot. It will not affect the currently "Running" image. Subsequent reboots will run the "Select" software image. The available choices are:

A: The image loaded in software bank A. B: The image loaded in software bank B. Next: The alternative to the currently "Running " image. If the current image is A, the next boot will use B and vice versa. The User needs to scroll down to the Select Software Image grouping and thus select what actions they wish to take (refer to Figure 122). The User does not need to be in Edit Mode within this menu option. Select. The options to select here are:

o Next o B o A Now. This is a check box that has to be enabled. Page 127 PureWave Quantum 6600 User Guide v2.1 Figure 122: Software Image Partition Selection To execute the procedure then the User needs to select the Perform Command Menu Option in the Select Next SW Image to Boot from grouping section. If the "Now" box is checked (i.e. enabled) the system will reboot shortly after the Perform Command Menu Option has been selected. It may take up to a minute for the Base Station to reboot. If the User attempts to navigate in the Web Interface window, the browser may report an "Unexpected Operation Error". The Web Interface may require re-

loading once the Base Station has restarted. Page 128 PureWave Quantum 6600 User Guide v2.1 3.6.3 Base Station Performance Monitoring There are a number of monitoring parameters that can be checked to determine the overall performance of the Base Station and for any Subscribers that are connected to the Base Station. These parameters are contained within a variety of menu options. The Users starting point is Web GUI Main Web GUI Interface Screen. 3.6.3.1 Interface At Main Web GUI Interface Screen select the Configuration Tab and then the interface Main Menu Option this will display the key settings window. This window details enabled the configuration of the backhaul interfaces There are two Main Menu Sub-Elements to this window and the window is split into two main grouping sections (refer to Figure 123). Figure 123: Performance Monitoring Interface The Main Menu Sub-Elements are:

statistics. These are not applicable and returns no values. status. This describes the configured settings and the current status of these interfaces. configure. This configures the backhaul interfaces speed and mode of operation Page 129 PureWave Quantum 6600 User Guide v2.1 Interface Settings and Status. The configured settings and their current status that are displayed for the five interfaces are:

o Admin State. This is the admin state. o Oper State. This is the operational state. o Link Speed. This is the interface link speed. o Duplex Type. This is duplex setting. o Maximum MTU Length. This is the maximum configured MTU Length. o MAC Address. This is the MAC address of the interface. At the Main Web GUI Interface Screen select the Configuration Tab and then the interface Main Menu Option, then the status main Menu Sub-Element. The resulting window will be split into two main sections (refer to Figure 124). These are:

Key Settings. o Name. This will indicate which interface is being displayed Interface Statistics and Status. The following settings and status are displayed. These are not editable parameters. o Admin State. This is the admin state. o Oper State. This is the operational state. o Link Speed. This is the interface link speed. o Duplex Type. This is duplex setting. o Maximum MTU Length. This is the maximum configured MTU Length. o MAC Address. This is the MAC address of the interface. Figure 124: Interface Status Key Settings and Status The same format is repeated for all interfaces and therefore only one will be outlined. To view the Interface Statistics of another interface then simply at the Main Web GUI Interface Screen select the Page 130 PureWave Quantum 6600 User Guide v2.1 Configuration Tab, then the interface Main Menu Option, then the status Main Menu Sub-Element and then relevant interface. At the Main Web GUI Interface Screen select the Configuration Tab and then the interface Main Menu Option, then the configure main Menu Sub-Element. The resulting window will be split into two main sections (refer to Figure 124). 3.6.3.2 Sector Statistics At the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu Option. This will display the Sector Settings window (refer to Figure 125). There are no parameters to edit within the sector Main Menu Option. Figure 125: Sector Settings There are two basic groups to this Sector option. These are:

Sector Advanced Settings (configured) Sector Provisioning (configured) Important sector statistics are contained within two options within the Sector Main Menu Option. The User now has to navigate to the next level, therefore at the Main Web GUI Interface Screen select the sector main Menu option and then the statistics Main Menu Sub-Element. There are four further sub-

elements to this option and the window is split into four main grouping sections (refer to Figure 126). The main grouping sections provide a summary of the information that can be obtained by selecting and navigating down into the Menu Sub-Element level. Page 131 PureWave Quantum 6600 User Guide v2.1 Figure 126: Sector Statistics Interface Key Settings The further sub-elements are:

service-flow-metrics. Several key service flow metrics are provided at a sector level (i.e. a Base Station level). packer-error-rate-metrics. This will display several key packet error rate counters. startup-counters. These are startup counters for a sector level. throughput-counters. Sector throughput counters are displayed. The four main grouping sections are the summary for the sub-elements on a per sector basis:

Sector Service-Flow Metrics. Sector Pkt Error-Rate Metrics. Sector Startup Counters. Sector Throughput Counters. To fully display all the available statistics the User now has to navigate to the next level, therefore at the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu Option then the statistics Main Menu Sub-Element, then service-flow-metrics and then 1. This will display the Metrics window. There are two distinct groups to this window (refer to Figure 127). Key Settings. This indicates the relevant sector, which as has been described in number 1. This is not a configurable parameter. Sector Service-Flow Metrics. The following Metrics are displayed. These are displayed as a raw number but they can also be displayed in graphical form by selecting the "Graph" command button. o DSA Requests o DSA Req Successes Page 132 PureWave Quantum 6600 User Guide v2.1 o DSC Requests o DSC Req Successes o DSD Requests o DSD Req Successes o Max Active Svc Flows o Max Active DL Svc Flows o Max Active UL Svc Flows Figure 127: Sector Statistics Interface Key Settings A similar format is repeated for the other three sector, statistics sub elements. The Key Settings window indicates the relevant sector. The information that is presented for each sub element, packet-error-rate-

metrics, startup-counters and throughput-counters is:

For the packet-error-rate metrics menu option the following Sector Pkt Error-Rate Metrics are displayed (refer to Figure 128):

o DL Packets Sent o DL Packet Errors o DL Pkt Error Rate o UL Packets Sent o UL Packet Errors o UL Pkt Error Rate For the startup-counters menu option, the following Sector Startup Counters are displayed

(refer to Figure 129):

o Authentication Attempts o Authentication Successes Page 133 PureWave Quantum 6600 User Guide v2.1 o Ranging Attempts o Ranging Successes o Ranging Periodic o Bandwidth Requests o Handover Ranging For the throughput-counters menu option, the following Sector Throughput Counters are displayed (refer to Figure 130):

o DL User Bytes o UL User Bytes o DL MAC Bytes o UL MAC Bytes o DL User Packets o UL User Packets o DL MAC Packets o UL MAC Packets o DL User Pkt Errors o UL User Pkt Errors o DL MAC Pkt Errors o UL MAC Pkt Errors Figure 128: Sector Statistics Packet Error Rate Metrics Page 134 PureWave Quantum 6600 User Guide v2.1 Figure 129: Sector Statistics Startup Counters Figure 130: Sector Statistics Throughput Counters Important Subscriber statistics are contained within the statistics-mss Main Menu Sub-Element within the Sector Main Menu Option. The User now has to navigate to the next level, therefore at the Main Web GUI Interface Screen select the sector Main Menu Option and then the statistics-mss Main Menu Sub-Element. There are seven further sub-elements to this option and the windows is split into the seven main grouping sections (refer to Figure 131). The main grouping sections provide a summary of the information that can be obtained by selecting and drilling down into the sub-element level. Page 135 PureWave Quantum 6600 User Guide v2.1 Figure 131: Sector MSS-Statistics Metrics The further sub-elements are:

mss-throughput-counters. This is the throughput counters for the Subscribers that are communicating with the Base Station. sflow-throughput-counters. These are the throughput counters per service flow. rssi-cinr-counters. These are the RSSI and CINR metrics per Subscriber and per upstream/

downstream direction. harq-counters. These are the HARQ counters per Subscriber. modulation-code-rate. These are the Modulation and Coding Scheme (MCS) per Subscriber. active-service-flows. These are the active Service flows per Subscriber. registered-ss. These are the registered Subscriber Station details. The seven main grouping sections are the summary for the sub-elements on a per sector basis:

Throughput Counters per MSS Throughput Counters Per Service-Flow RSSI and CINR Metrics Per MSS HARQ Counters Per MSS Modulation and Coding Scheme (MCS) Active Service Flows Registered Subscriber Station To fully display all the available statistics the User now has to navigate to the next level, therefore at the Main Web GUI Interface Screen select the Configuration Tab, then the sector Main Menu Option, then the statistics-mss Main Menu Sub-Element and then one of the seven further sub-elements. Under each tree Sub-element a list of all the connected Subscribers will be displayed. The Use has to select the relevant Subscriber and the information will be displayed for the particular Subscriber. Page 136 PureWave Quantum 6600 User Guide v2.1 At the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu Option, then the statistics-mss Main Menu Sub-Element and then mss-throughput-counters. There are two distinct groups to this window (refer to Figure 132). Key Settings. This indicates the relevant Subscriber. This is not a configurable parameter. The following information is presented:

o Sector o MAC Address Throughput Counters Per MSS. The following Metrics are displayed. These are displayed as a raw number but they can also be displayed in graphical form by selecting the "Graph" command button. o DL Bytes o Ul Bytes o DL Pkts o UL Pkts o DL Pkt Err o UL Pkt Err o Hcs-cnt o Crc-cnt Figure 132: Sector Statistics MSS Throughput Counters At the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu option, then the statistics-mss Main Menu Sub-Element and then sflow-throughput-counters. The Service Flows that have been defined for each Subscriber will be displayed. For each Subscriber there will be at least two defined Service Flows, one for Upstream and another for Downstream. There are two distinct groups to this window (refer to Figure 133). Page 137 PureWave Quantum 6600 User Guide v2.1 Key Settings. This indicates the relevant Subscriber. This is not a configurable parameter. The following information is presented:

o Sector o MAC Address o SFID. This is the Service Flow identifier. Throughput Counters Per Service-Flow. The following Metrics are displayed. These are displayed as a raw number but they can also be displayed in graphical form by selecting the "Graph"

command button. o DL Bytes o UL Bytes o DL Pkts o UL Pkts o DL Pkt Err o UL Pkt Err Figure 133: Sector Statistics Service Flow Throughput Counters At the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu Option, then the statistics-mss Main Menu Sub-Element and then rssi-cinr-metrics. The downstream and upstream direction for each Subscriber will be displayed. There are two distinct groups to this window. Figure 134 has the downstream RSSI parameters and Figure 135 has the upstream metrics. Key Settings. This indicates the relevant Subscriber. This is not a configurable parameter. The following information is presented:

o Sector o MAC Address o Channel Dir. This indicates the respective direction that the Metrics are displayed. Page 138 PureWave Quantum 6600 User Guide v2.1 Downstream RSSI/CINR Metrics. The following Metrics are displayed. These are displayed as a raw number but they can also be displayed in graphical form by selecting the "Graph" command button. If the CLI is used to view metrics, the RSSI per antenna will be shown but will have the same value across all antennas. o CINR Mean o CINR Std Dev o RSSI Mean o RSSI Std Dev Upstream RSSI/CINR Metrics. The following Metrics are displayed. These are displayed as a raw number but they can also be displayed in graphical form by selecting the "Graph" command button. o Mean CINR o Std Dev CINR o Maximum RSSI o Std Dev RSSI o Antenna 1 RSSI o Antenna 2 RSSI o Antenna 3 RSSI o Antenna 4 RSSI o Antenna 5 RSSI o Antenna 6 RSSI Figure 134: Sector Statistics Downlink RSSI CINR Metrics Page 139 PureWave Quantum 6600 User Guide v2.1 Figure 135 Sector Statistics Upstream RSSI CINR Metrics At the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu Option, then the statistics-mss Main Menu Sub-Element and then harq-counters. There will be three HARQ Service Flow identifiers displayed for each Subscriber. There are two distinct groups to this window (refer to Figure 136). Key Settings. This indicates the relevant Subscriber. This is not a configurable parameter. The following information is presented:

o Sector o MAC Address o Svc Flow ID HARQ Counters Per MSS. The following Metrics are displayed. These are displayed as a raw number but they can also be displayed in graphical form by selecting the "Graph" command button. It is not possible to view all the metrics in one window and therefore the User has to scroll down to view them all. o HARQ Enabled. This indicates whether HARQ has been enabled. This is not however a configurable parameter. o HARQ DL Pkt Ack o HARQ DL Pkt Neg Ack o HARQ DL Pkt Trans o HARQ DL Pkt Retrans o HARQ DL Pky Discards o HARQ DL Pkt 1st Neg Ack o HARQ UL Pkt Ack o HARQ UL Pkt Neg Ack o HARQ UL Pkt Trans Page 140 PureWave Quantum 6600 User Guide v2.1 o HARQ UL Pkt Retrans o HARQ UL Pky Discards o HARQ UL Pkt 1st Neg Ack Figure 136: Sector Statistics HARQ Counters At the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu option, then the statistics-mss Main Menu Sub-Element and then modulation-code-rate. The information for each Subscriber is displayed. There are two distinct groups to this window (refer to Figure 137). Key Settings. This indicates the relevant Subscriber. This is not a configurable parameter. The following information is presented:

o Sector o MAC Address Modulation and Coding Scheme (MCS). The following information is displayed. o DL MCS. This indicates the maximum downlink MCS rate. The available options are:

QPSK 1/2 QPSK 3/4 QAM16 1/2 QAM16 3/4 QAM64 1/2 QAM64 2/3 QAM64 3/4 QAM64 5/6 o UL MCS. This indicates the maximum uplink MCS rate. The available options are the same as the downlink. Page 141 PureWave Quantum 6600 User Guide v2.1 Figure 137: Sector Statistics Modulation Code Counters At the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu Option, then the statistics-mss Main Menu Sub-Element and then active-service-flows. The Service Flows that are active for each Subscriber will be displayed. For each Subscriber there will be at least two active Service Flows, one for Upstream and another for Downstream. There are two distinct groups to this window (refer to Figure 138). Key Settings. This indicates the relevant Subscriber. This is not a configurable parameter. The following information is presented:

o Sector o MAC Address o Svc Flow ID. This is the Service Flow identifier. Active Service Flows. The following Metrics are displayed. These are displayed as a raw number but they can also be displayed in graphical form by selecting the "Graph" command button. o Svc Flow Dir. This provides an indication of the respective direction. The options are uplink or downlink. o UL Bytes. This provides an indication of the Service Flow QoS (Quality of Service). o Svc Flow CID o Svc Flow SAID Page 142 PureWave Quantum 6600 User Guide v2.1 Figure 138: Sector Statistics Active Service Flows At the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu Option, then the statistics-mss Main Menu Sub-Element and then registered-ss. The number of registered Subscribers will be displayed. There are two distinct groups to this window (refer to Figure 139). Key Settings. This indicates the relevant Subscriber. This is not a configurable parameter. The following information is presented:

o Sector o MAC Address Registered Subscriber Station. The following information is displayed. These are not configurable parameters at this menu option. o Client Profile ID. o Network Entry State. This provides an indication as to the connected "state" of the Subscriber. o Uptime. This is the Subscriber connected time. o Network Entry Type. This indicated the way the CPE connected to the Base station. Initial Means through means of initial ranging or Handover through handover ranging. o Authentication status o SNR Reporting Method o Basic CID o Primary CID o Vendor ID o MAC Version Page 143 PureWave Quantum 6600 User Guide v2.1 Figure 139: Sector Statistics Registered SS 3.6.3.3 Logging The Base Station contains a number of internal system management logs. The Web Gui provides the User with complete flexibility on performing a number of key actions on these logs. At the Main Web GUI Interface Screen select the Configuration Tab and then select the logging Main Menu Option. This will display all the system logs files (Figure 140). Figure 140: Main Menu Logging Options Page 144 PureWave Quantum 6600 User Guide v2.1 The logging Main Menu option contains four Main Menu Sub-Elements. These are:

remote. The User has the capability to define a remote server to forward a pre-defined log level. local. The User has the capability to define the minimum severity level to log. file. These are file actions that the User can perform. files. This describes the system log files. At the Main Web GUI Interface Screen select the Configuration Tab and then select the logging Main Menu Option and then the remote Main Menu Sub-Element. The User is now presented with a window that displays the remote Log Server Settings. There are two distinct groups to this window (refer to Figure 141). The User is presented with a host Menu Sub-Element from the remote Main Menu Sub-

Element level. If the User navigates to this level then it will display a list of all the log servers that have been configured. The User can select to view the relevant details. Default Remote Log Server Settings. The User can view and hence configure the default minimum severity log level to forward to the remote server. This will apply to all remote servers which have a level of default. The User must be in Edit Mode to configure. In addition to the default level there are nine available options. These are:

info o none o debug o o notice o warning o error o critical o alert o emergency Remote Log Server Settings. For log servers that have configured the following information is displayed. To configure the User must be in Edit Mode. Once in Edit Mode, the User can <Add host>, delete or change the Severity Level of an existing host. o Hostname. If the User wants to add a remote server then they must enter the syslog remote server IP address or domain name. The User cannot edit the hostname for a syslog server that has been configured, this syslog must be deleted and then it can be re-added. When in the Edit Mode, there is a red box beside each hostname. If the User navigates to the red icon then this will present the User with the ability to delete the hostname. o Severity Level. The User can configure or re-configure the syslog server to that of the default level or any of the nine available options. Page 145 PureWave Quantum 6600 User Guide v2.1 Figure 141: Logging Remote Host Information At the Main Web GUI Interface Screen select the Configuration Tab and then select the logging Main Menu Option and then the local Main Menu Sub-Element. The User is now presented with a window that displays the local Log Server Settings. This only one distinct group to this window (refer to Figure 142). The User can select to view the relevant details. Default Local Log Server Settings. The User can view and hence configure the default minimum severity log level for the local internal log server. This will apply to all local servers except those which have been configured in the logging local override configuration. The User must be in Edit Mode to configure. To define the default level there are one of nine available options to select. These are:

info o none o debug o o notice o warning o error o critical o alert o emergency Page 146 PureWave Quantum 6600 User Guide v2.1 Figure 142: Logging Local Information At the Main Web GUI Interface Screen select the Configuration Tab, then select the logging Main Menu option, then the local Main Menu Sub-Element and then override. The User can now is now presented with an option to increase or decrease the internal sys log per daemon/application which are internal to the Base Station (refer to Figure 143). The User must be in Edit mode to configure. Figure 143: Logging Local Override Page 147 PureWave Quantum 6600 User Guide v2.1 When in Edit mode only one distinct group to this window is displayed. The User must <Add Source>

and define the relevant App Name. The configurable options are:

Key Settings App Name o confd o wmdlpcClientd r6mgrd o o sectord o statsd o genactiond o snmpactiond o gpsmgrsyncd o swumgrd o sysmgrd Once the App Name has been selected then the User is presented with an Application Log Settings menu where the Severity Level can be configured. At the Main Web GUI Interface Screen select the Configuration Tab and then the logging Main Menu option and then the file Main Menu Sub-Element. The User is now presented with further Menu Sub-

Elements (refer to Figure 144). The User now has top select one of the Menu Sub-Elements to be presented with an action. Figure 144: Logging File Information At the Main Web GUI Interface Screen select the Configuration Tab, select the logging Main Menu Option, then the file Main Menu Sub-Element, then rotation and finally force. Page 148 PureWave Quantum 6600 User Guide v2.1 This will force a reboot of the Base Station and the log file to effectively rotate and begin logging again. The rotate feature forces the logging to the relevant file to stop, it then compresses the file, effectively renames it (generally by appending a .1 to the end of the filename) and then starts the logging to a new file. E.g. the current sys log file is messages but at the last rotate action this file was rotated into messages.1.gz and the then logging started again to messages. An automatic rotation will occur when the file size reaches 5MBytes. There are no parameters to edit and the User simply has to select the Perform Command Menu Option to initiate the log file rotation (refer to Figure 145). Figure 145: Logging File Rotation At the Main Web GUI Interface Screen select the Configuration Tab, then the logging Main Menu Option, then the file Main Menu Sub-Element and then delete. This option provides a means for the User to delete a log file (refer to Figure 146). Two distinct window groups are presented to the User. These are:

Delete Log File. This simply provides a description of the actions. Delete Log File. The User simply selects the log file that they would like to delete. The list of available files are presented via a drop down menu. The User does not have to be in Edit mode to select the log file. Page 149 PureWave Quantum 6600 User Guide v2.1 Figure 146: Logging File Delete At the Main Web GUI Interface Screen select the Configuration Tab, then select the logging Main Menu Option, then the file Main Menu Sub-Element and then upload. This option provides a means for the User to upload a log file to a server URL. Two distinct window groups are presented to the User. These are (refer to Figure 147):

Upload Log File to Remote Server. This simply provides a description of the actions. Upload Log File. The User does not have to be in Edit mode to perform these actions. Prior to uploading the file, the User must ensure that an FTP Server has been configured and is running. The User has to select the following information:

o File to Upload. The User selects the log file that they would like to upload. The list of available files are presented via a drop down menu. o Destination URL. There are a variety of formats for the destination URL. These can be displayed if the User selects the "help" key. These URL formats are defined as:

ftp://[user[:password]@]hostname[:port]/filepath http://hostname[:port]/filepath https://hostname[:port]/filepath Where [ ] indicates optional items. Thus, user:password@ is optional, and the :password part can be omitted

[:port] is also optional Examples using ftp (you can substitute http or https):

ftp://myhost.com/filename ftp://myhost.com/directory/filename ftp://myhost.com:2323/directory/filename Page 150 PureWave Quantum 6600 User Guide v2.1 ftp://myname@myhost.com:2323/directoryname/filename ftp://myname:password@myhost.com:2323/directoryname/filename URL of remote source file; format is as follows:

protocol://[user[:password]]@host[:port]/path protocol can be ftp, http, or https Figure 147: Logging File Upload At the Main Web GUI Interface Screen select the Configuration Tab, then select the logging Main Menu option, and then the files main Menu Sub-Element. This option provides a list of all the sys log files on the Base Station (refer to Figure 148). Figure 148: Logging Files Filenames Page 151 PureWave Quantum 6600 User Guide v2.1 If the User selects a relevant file, then the characteristics of the file are displayed. The following information will be displayed for each file (refer to Figure 149):

Key Settings o Filename System Log Files o Size. This is the file size in bytes. o Modified. This was the date that the file was last modified. Figure 149: Logging Files System Information Page 152 PureWave Quantum 6600 User Guide v2.1 3.6.3.4 SNMP Server Simple Network Management Protocol (SNMP) is an "Internet-standard protocol for managing devices on IP networks. The SNMP server exposes management data in the form of variables on the managed systems, which describe the system configuration (MIBs). These variables can then be queried and set by managing applications called Network Management Systems (NMS). To configure the SNMP Server, select the Configuration Tab and then select the snmp-server from Main Menu Option (Figure 150). Figure 150 snmp-server configuration When in Edit mode, the configurable options are:

SNMP v1 (enable/disable) SNMP v2c (enable/disable) SNMP v3 (enable/disable) Port (default 161) The community sub-menu (Figure 151) allows the configuration of the community string (basic password) used for security for with SNMP. If the User wants to add or edit any of the existing community strings then they must then select snmpCommunityTable and enter the Edit Mode (Edit Private or Edit Exclusive). The following options will be available

<Add snmpCommunityEntry>. This allows addition of a new community string private. SNMP access which allows read-write permissions. public. SNMP access which allows read-only permissions. standard trap. Read-only permissions for sending SNMP traps. Page 153 PureWave Quantum 6600 User Guide v2.1 Figure 151 Community sub-menu If the User wants to add or edit any of the existing community strings then they must then select enter the Edit Mode (Edit Private or Edit Exclusive). The following options will be available for each entry

(Figure 152) Key Settings o SNMP Community Index snmpCommunityEntry o SNMP Community Name. Name of the community string o SNMP Community Security Name. Level of access including read-write and read-only o SNMP Community Context Engine ID. o SNMP Community Context Name. o SNMP Community Transport Tag. o SNMP Community Storage Type. Default value is permanent Page 154 PureWave Quantum 6600 User Guide v2.1 Figure 152 snmpCommunityEntry Table The user sub-menu (Figure 153 and Figure 154) allows the protection of SNMPv3 packets from the above threats by utilizing a concept of multiple users where each user provides secret keys for authentication and privacy. If the User wants to add or edit any of the existing user record then they must then select user and enter the Edit Mode (Edit Private or Edit Exclusive). The following options will be available Key Settings o Usm User Engine ID o Usm User Name usmUserEntry o Usm User Security Name o Usm User Clone From. o Usm User Auth Protocol. o Usm User Auth Key Change. o Usm User Own Auth Key Change. o Usm User Priv Protocol. o Usm User Priv Key Change. o Usm User Own Priv Key Change. o Usm User Public. o Usm User Storage Type. Default is nonVolatile o Usm User Auth Key. o Usm User Priv Key. Page 155 PureWave Quantum 6600 User Guide v2.1 Figure 153 SNMP user configuration Figure 154 SNMP user configuration continued The notify sub-menu (Figure 155) configures the SNMP notification generation mechanism. If the User wants to add or edit any of the existing community strings then they must then select snmpNotifyTable and enter the Edit Mode (Edit Private or Edit Exclusive). The following options will be available Key Settings o SNMP Notify Name snmpNotifyEntry (Field entries are explain in Table 12 SNMP Notification TableTable 12) o Snmp Notify Tag. o Snmp Notify Type. o Snmp Notify Storage Type. Page 156 PureWave Quantum 6600 User Guide v2.1 Figure 155 SNMP Notify Configuration Name Description Field Example Snmp Notify Name A unique identifier used to index this table 1-32 chars Snmp Notify Tag Snmp Notify Type A tag value used to reference one or more entries in snmpTargetAddrTable. Selects the type of notification to be generated for the entries in the snmpTargetAddrTable referenced by snmpNotifyTag:

Example: std_trap Example: trap Snmp Notify Storage Type trap(1) - Generates an SNMPv2c Trap PDU inform(2) - Generates an InformRequest PDU Specifies how the row should be stored. Table 12 SNMP Notification Table The default value is nonVolatile. Page 157 PureWave Quantum 6600 User Guide v2.1 Figure 156 SNMP Trap Destination The trap destination sub-menu (Figure 156) specifies the network and transport layer attributes of notification destinations. Each row in this table is used to send traps to a different NMS. If the User wants to add or edit any of the existing trap destinations, then they must then select NMS-

Address and enter the Edit Mode (Edit Private or Edit Exclusive). The following options will be available below (Figure 157 and Figure 158) Key Settings o NMS-Address snmpNotifyEntry (Field entries are explain in Table 13Table 12 SNMP Notification Table) o Snmp Target Addr TDomain. o Snmp Target Addr TAddress. o Snmp Target Addr Timeout. o Snmp Target Addr TAddress. o Snmp Target Addr Retry Count. o Snmp Target Addr Tag List. o Snmp Target Addr Params. o Snmp Target Addr Storage Type. o Snmp Target Addr Engine ID. o Snmp Target Addr TMask. o Enabled. Page 158 PureWave Quantum 6600 User Guide v2.1 Figure 157 Trap Destination Configuration Parameters Figure 158 Trap Destination Configuration Parameters continued Page 159 PureWave Quantum 6600 User Guide v2.1 Name Description Field Example snmpTargetAddrName Name of the target snmpTargetAddrTable 1-32 chars snmpTargetAddrTDomain snmpTargetAddrTAddress snmpTargetAddrTimeout snmpTargetAddrRetryCount snmpTargetAddrTagList snmpTargetAddrParams This object indicates the transport type of the address contained in the snmpTargetAddrTAddress object Specifies the target address, which consists of an IP address followed by a UDP port number Sets a timeout value (in ticks) for the transmission of InformRequest PDU or TCP connection. The agent will wait this amount of time for a response to an InformRequest PDU or TCP connection before attempting again. Sets the number of times that the agent will resend an InformRequest PDU or attempt to establish a TCP connection before abandoning further attempts and logging an error in the agent log file. A list that provides the correlation between snmpTargetAddrTable and snmpNotifyTable. When generating a notification, the agent searches this list for the value contained in snmpNotifyTag. If the list contains this value, then the agent uses the information in this row to create a destination for the notification. Indexes the row in snmpTargetParamsTable that describes the security parameters to be used when sending the notification. If the row specified does not exist, the notification will not be sent. snmpTargetAddrStorageType Specifies how the row should be stored. snmpTargetAddrEngineID Internal use only, leave blank snmpTargetAddrTMask Internal use only, leave blank snmpTargetAddrStorageType enabled Internal use only ( Maximum message size) default 2048 This field allows trap sending to a given NMS to be paused Table 13 SNMP Target Address Table 1.3.6.1.6.1.1 is the domain for UDP Example:

127.0.0.1.0.162. Example: 1500 is 1.5 seconds Example: 3 For example:

std_trap For example:

target_v2 The default value is nonVolatile. 2048 true/false Page 160 PureWave Quantum 6600 User Guide v2.1 3.6.3.5 Alarm Management The Quantum Base Station has advanced alarm and fault management capabilities. When a fault or event occurs, an alarm condition will be raised. An alarm is a persistent indication of a fault that clears only when the triggering condition has been resolved. To configure Alarm Management, select the Configuration Tab and then select the alarm Main Menu Option (Figure 159). Figure 159 Alarm Management When in View or Edit mode, the options are:

action. Allows acknowledgement, clearing and un-acknowledgment of alarms active. View a list of the active alarms To acknowledge, clear or un-acknowledge an alarm, select the action sub-Element (Figure 160). The User is now presented with a window that displays an operation to be performed on the following alarm-names. Voltage. Allows acknowledgement, clearing and un-acknowledgment of alarms Sector-Comm-Loss. Indicates if Sector is Up or Down. Temperature. Low, Hi or Normal Operating Temperature Sector-Down. View the active alarms GPS-Synch-Holdoff. Indicates if GPS is reliable or unreliable. GPS-Synch-Loss. Indicates if GPS is reliable or unreliable. Select the alarm type and click Perform to apply the action Page 161 PureWave Quantum 6600 User Guide v2.1 Figure 160 Alarm Action Page 162 PureWave Quantum 6600 User Guide v2.1 Appendix A Capacity Tables We present here a set of tables specifying the raw (MAC-layer) throughput of a PureWave Quantum Family base Station for 5, 7 and 10MHz, under ideal conditions, corresponding to the maximum achievable performance that can be achieved using IEEE 802.16e per channel bandwidth and TDD configuration ratio. All results assume PUSC, a MAP size of 4 symbols, and 1 preamble symbol. The numbers represent the maximum MAC layer performance using all sub-channels and exclude Ethernet Layer 2 or higher layer overheads. Values are in units of Mbps. Note that these results are specific to the stated configuration under ideal conditions and should be considered indicative of expected results. Actual results will vary depending upon the actual configuration, error rate, environment, and numerous other factors. MCS Rate 64QAM-5/6 64QAM-3/4 64QAM-2/3 64QAM-1/2 16QAM-3/4 16QAM-1/2 QPSK-3/4 QPSK-1/2 MCS Rate 64QAM-5/6 64QAM-3/4 64QAM-2/3 64QAM-1/2 16QAM-3/4 16QAM-1/2 QPSK-3/4 QPSK-1/2 10MHz Downlink Uplink 21.60 19.44 17.28 12.96 12.96 8.64 6.48 4.32 5.04 4.54 4.03 3.02 3.02 2.02 1.51 1.01 Bi-Dir 25.44 22.90 20.35 15.26 15.26 10.18 7.63 5.09 5MHz Downlink Uplink 10.8 9.72 8.64 6.48 6.48 4.32 3.24 2.16 2.45 2.2 1.96 1.47 1.47 0.98 0.73 0.49 Table 14: Max Throughput - 35:12 - 74%:26%

10MHz Downlink Uplink 18.72 16.85 14.98 11.23 11.23 7.49 5.62 3.74 6.72 6.05 5.38 4.03 4.03 2.69 2.02 1.34 Bi-Dir 25.44 22.90 20.35 15.26 15.26 10.18 7.63 5.09 5MHz Downlink Uplink 9.36 8.42 7.49 5.62 5.62 3.74 2.81 1.87 3.26 2.94 2.61 1.96 1.96 1.31 0.98 0.65 Table 15: Max Throughput - 32:15 68%:32%

Bi-Dir 13.25 11.92 10.6 7.95 7.95 5.3 3.97 2.65 Bi-Dir 12.62 11.36 10.10 7.57 7.57 5.05 3.79 2.52 Page 163 PureWave Quantum 6600 User Guide v2.1 10MHz Downlink Uplink 17.28 15.55 13.82 10.37 10.37 6.91 5.18 3.46 8.40 7.56 6.72 5.04 5.04 3.36 2.52 1.68 Bi-Dir 25.68 23.11 20.54 15.41 15.41 10.27 7.70 5.14 5MHz Downlink Uplink 8.64 7.78 6.91 5.18 5.18 3.46 2.59 1.73 4.08 3.67 3.26 2.45 2.45 1.63 1.22 0.82 Table 16: Max Throughput 29:18 - 62%:38%

10MHz Downlink Uplink 10.08 14.40 12.96 11.52 8.64 8.64 5.76 4.32 2.88 9.07 8.06 6.05 6.05 4.03 3.02 2.02 Bi-Dir 24.48 22.03 19.58 14.69 14.69 9.79 7.34 4.90 5MHz Downlink Uplink 7.20 6.48 5.76 4.32 4.32 2.88 2.16 1.44 4.90 4.41 3.92 2.94 2.94 1.96 1.47 0.98 Table 17: Max Throughput 26:21 - 55%:45%

MCS Rate 64QAM-5/6 64QAM-3/4 64QAM-2/3 64QAM-1/2 16QAM-3/4 16QAM-1/2 QPSK-3/4 QPSK-1/2 MCS Rate 64QAM-5/6 64QAM-3/4 64QAM-2/3 64QAM-1/2 16QAM-3/4 16QAM-1/2 QPSK-3/4 QPSK-1/2 Bi-Dir 12.72 11.45 10.18 7.63 7.63 5.09 3.82 2.54 Bi-Dir 12.10 10.89 9.68 7.26 7.26 4.84 3.63 2.42 MCS Rate 64QAM-5/6 64QAM-3/4 64QAM-2/3 64QAM-1/2 16QAM-3/4 16QAM-1/2 QPSK-3/4 QPSK-1/2 7MHz Downlink Uplink 11.5 10.4 9.2 6.9 4.6 3.5 2.3 11.5 5.0 4.5 4.0 3.0 2.0 1.5 1.0 5.0 Bi-Dir 16.6 14.9 13.2 9.9 6.6 5.0 3.3 16.6 MCS Rate 64QAM-5/6 64QAM-3/4 64QAM-2/3 64QAM-1/2 16QAM-3/4 16QAM-1/2 QPSK-3/4 QPSK-1/2 7MHz Downlink Uplink 13.0 11.7 10.4 7.8 5.2 3.9 2.6 13.0 3.4 3.0 2.7 2.0 1.3 1.0 0.7 3.4 Bi-Dir 16.3 14.7 13.1 9.8 6.5 4.9 3.3 16.3 Table 18: Max Throughput 21:12 - 64%:36%

Table 19: Max Throughput 23:9 - 72%:28%

Page 164 PureWave Quantum 6600 User Guide v2.1 MCS Rate 64QAM-5/6 64QAM-3/4 64QAM-2/3 64QAM-1/2 16QAM-3/4 16QAM-1/2 QPSK-3/4 QPSK-1/2 7MHz Downlink Uplink 8.6 7.8 6.9 5.2 3.5 2.6 1.7 8.6 6.7 6.0 5.4 4.0 2.7 2.0 1.3 6.7 Bi-Dir 15.4 13.8 12.3 9.2 6.1 4.6 3.1 15.4 Table 20: Max Throughput 17:15 - 53%:47%

Page 165 PureWave Quantum 6600 User Guide v2.1 Appendix B Limited Warranty Statements Hardware PureWave, Inc (PureWave or the Company) warrants to the original end-user (Customer) that this hardware product will conform in all material respects to the specifications provided with the hardware and will be free from defects in workmanship and materials, under normal use and service, for a period of 365 days from the date of original shipment by PureWave. PureWave's sole obligation under this limited warranty shall be, at PureWave's option, to repair the defective product or part, deliver to Customer an equivalent product or part to replace the defective item, or if neither of the two foregoing options is reasonably possible, refund to Customer the purchase price paid for the defective product. All products that are replaced will become the property of PureWave. Replacement products may be new or reconditioned. PureWave's obligations hereunder are conditioned upon the returned of affected articles in accordance with PureWave's Return Material Authorization (RMA) procedures. The above warranty will also apply to any replaced or repaired product for 90 days from the date of shipment from PureWave of the replaced or repaired product, or the remainder of the initial warranty period, whichever is longer. Software PureWave warrants to the Customer that for a period of ninety (90) days from your receipt of the Product as demonstrated by written records (the Warranty Period) the Software will perform substantially in accordance with the Documentation. If the Software fails to comply with the warranty set forth above, your exclusive remedy will be, at the option of PureWave (i) a reasonable effort by PureWave to make the Software perform substantially in accordance with the Documentation, or (ii) return of the purchase price. This limited warranty applies only if you return all copies of the Product, together with proof of purchase, to PureWave during the Warranty Period. This limited warranty is VOID if failure of the Software is due to modification of the Software not made by PureWave, or the abuse or misapplication of the Software. PUREWAVE DOES NOT WARRANT THAT THE SOFTWARE IS ERROR FREE, THAT THE CUSTOMER WILL BE ABLE TO OPERATE THE SOFTWARE WITHOUT PROBLEMS OR INTERRUPTIONS OR THAT THE SOFTWARE OR ANY EQUIPMENT, SYSTEM OR NETWORK ON WHICH THE SOFTWARE IS USED WILL BE FREE OF VULNERABILITY TO INTRUSION OR ATTACK. Page 166 PureWave Quantum 6600 User Guide v2.1 Additional Conditions Notwithstanding anything else herein or otherwise, PureWave reserves the right to establish amendments to its RMA Policy from time to time. Further, PureWave Technical Support may prefer to troubleshoot the wireless link with an onsite Customer technician while the Products are in their original non-conforming state. This process might assist Customer in understanding and troubleshooting the issue. If PureWave was not afforded the opportunity to troubleshoot an allegedly non-conforming Product in original non-conforming state, PureWave may approve or reject an RMA request in its sole discretion. No Fault Found Notwithstanding sections above, if PureWave cannot duplicate any alleged non-conformity, the Product will be returned to the Customer as "No Fault Found." PureWave reserves the right to charge a testing fee in connection with a returned product that PureWave determines as No Fault Found, and any such payment must be received by PureWave prior to return shipment of the applicable Product to Customer. Warranty Limitations PureWaves warranties do not apply to any product (hardware or software) which has (a) been subjected to abuse, misuse, neglect, accident, or mishandling, (b) been opened, repaired, modified, or altered by anyone other than PureWave, (c) been used for or subjected to applications, environments, or physical or electrical stress or conditions other than as intended and recommended by PureWave, (d) been improperly stored, transported, installed, or used, or (e) had its serial number or other identification markings altered or removed. Warranty Disclaimer PURWAVES SPECIFIC WARRANTIES SUMMARIZED ABOVE ARE THE ONLY WARRANTIES GIVEN BY PUREWAVE WITH RESPECT TO ITS PRODUCTS (HARDWARE AND SOFTWARE) AND ARE GIVEN IN LIEU OF ANY AND ALL OTHER WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY, OR ARISING BY CUSTOM, TRADE USAGE, OR COURSE OF DEALING, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND PUREWAVE DISCLAIMS ANY AND ALL OTHER WARRANTIES TO THE MAXIMUM EXTENT PERMITTED BY LAW. Without limiting the generality of the foregoing sentence, PureWave makes no warranty or representation, either expressed or implied, as to, and disclaims all liability and responsibility for, (a) the operation, compliance, labeling, or packaging of any of its products under the laws of any jurisdiction outside of the United States of America and (b) the regulatory compliance of any products in any jurisdiction in which it has not specifically identified compliance or the use of any product in any jurisdiction in any manner other than as contemplated in the regulatory certifications and approvals for that product in that jurisdiction. To the extent an implied warranty cannot be excluded, such warranty is limited in duration to the warranty period. The disclaimer and exclusion applies even if the express warranty fails of its essential purpose. Page 167 PureWave Quantum 6600 User Guide v2.1 Obtaining Warranty Service Customer must contact the Company, by sending an e-mail to support@pwnets.com to obtain warranty service authorization. When contacting PureWave for support, please be prepared to provide the product description and serial number and a description of the problem. The Customer will be expected to complete a Return Material Authorization (RMA) form to initiate the request. Full instructions as to how to complete and where to send the form are provided on the form. Date of proof of purchase from PureWave will be required. Products returned to PureWave Inc must be pre-authorized by PureWave with a Return Material Authorization (RMA) number and sent prepaid and packaged appropriately for safe shipment. The Customer requesting the RMA will be the exporter. The exporter is responsible to ship RMA equipment to PureWaves address and has to bear the cost and risk involved in bringing the goods to PureWaves location. Risk of loss in return shipment will be borne by Customer, and it is recommended that returned goods be insured and/or sent by a method that provides for tracking of the package. Responsibility for loss or damage does not transfer to PureWave until the returned item is received by PureWave. Provided that PureWave determines that the item is actually defective, the repaired or replaced item will be shipped to Customer, at PureWave's expense, (1) not later than thirty (30) days after PureWave receives the defective product or (2) to the terms of a separate written agreement with PureWave. If the allegedly non-conforming Product is not received by PureWave within thirty (30) days of Customer initiating the RMA request, the RMA process for that Product will be deemed cancelled. You may also obtain the status of their RMA request(s) by sending an e-mail to support@pwnets.com referencing their assigned RMA Number(s). No product will be accepted for repair or replacement by PureWave without a RMA number. The product must be returned to PureWave, properly packaged to prevent damage, shipping and handling charges prepaid, with the RMA number prominently displayed on the outside of the container. If PureWave determines that a returned product is not defective or is not covered by the terms of the warranty, the Customer will be charged a service charge and return shipping charges. Table 21 summarizes the conditions and charges that PureWave reserves the right to levy. Page 168 PureWave Quantum 6600 User Guide v2.1 RMA Related Issue Under Warranty Repair and return No charge, PureWave pays Shipment of unit to PureWave Customer pays Regular Shipment to Customer No charge, PureWave pays Expedited shipment to Customer Customer pays the additional cost of the expedited shipping No Fault Found PureWave reserves the right to levy a charge Warranty for repaired and or replaced product Remainder of the original warranty or 90 days Table 21: Summary of PureWave RMA Conditions and Charges Assistance For assistance, contact your nearest PureWave Networks Sales and Service office. Additional information is available on the PureWave Networks website at http://www.pwnets.com. For Customer Service call: 650-528-5200, or Email: support@pwnets.com. Page 169

Quantum 2200 High performance, all outdoor Mobile WiMAX base stations PureWave Quantum 2200 Installation Guide v2.1 ING-00702-001 Rev C Quantum 2200 Installation Guide v2.1 PureWave Networks 2011. All rights reserved. PureWave Networks has prepared this manual for use by PureWave Networks personnel, licensees, customers, and customers of customers. The information contained herein is the property of PureWave Networks and shall neither be reproduced in whole nor in art without prior written approval from PureWave Networks. PureWave Networks reserves the right to make changes without notice to the specifications and materials contained herein, and shall not be responsible for any damages caused by reliance on the material presented, including, but not limited to, typographical, arithmetic and listing errors. Page 2 Quantum 2200 Installation Guide v2.1 Contents Contents ........................................................................................................................................................ 3 Figures ........................................................................................................................................................... 5 Tables ............................................................................................................................................................ 6 Regulatory Notice ......................................................................................................................................... 7 Safety Precautions ........................................................................................................................................ 8 1 Preface .................................................................................................................................................. 9 1.1 1.2 1.3 1.4 1.5 About This Document ................................................................................................................... 9 Symbols used in this Document .................................................................................................... 9 Packaging and Components .......................................................................................................... 9 Locating the Product Serial Number ........................................................................................... 10 Obtaining Documentation and Support ...................................................................................... 10 2 Base Station Basics .............................................................................................................................. 11 2.1 2.2 2.3 Physical and Environmental Specifications ................................................................................. 11 Physical and Environmental Specifications ................................................................................. 12 Connectors and Indicators .......................................................................................................... 13 3 Mounting the Base Station ................................................................................................................. 15 3.1 3.2 Fundamentals ............................................................................................................................. 15 The Pole-Mount Kit ..................................................................................................................... 16 3.2.1 Pole Mount Installation Procedure ..................................................................................... 17 4 Mounting the Antennas ...................................................................................................................... 21 5 Connecting the Antennas to the Base Station .................................................................................... 22 5.1 5.2 Installation of Lightning Surge Protectors .................................................................................. 22 Connecting the Antennas to the Base Station ............................................................................ 24 6 Installing the GPS Antenna.................................................................................................................. 25 6.1 6.2 Selecting and Mounting a GPS Antenna ..................................................................................... 25 Connecting the GPS Antenna to the Base Station ...................................................................... 26 7 Connecting Ethernet and Serial Console Cables ................................................................................. 27 7.1 The PureWave Basic DC Installation Kit ...................................................................................... 27 Page 3 Quantum 2200 Installation Guide v2.1 7.2 Preparing the Ethernet and Console Cables ............................................................................... 28 7.3 Weatherproofing the Ethernet and Console Connections ......................................................... 29 8 Connecting DC Power and Ground ..................................................................................................... 31 8.1 8.2 Base Station Single-Point Grounding .......................................................................................... 31 Preparing the DC Power Connector ............................................................................................ 31 Appendix A Connector Weatherproofing ............................................................................................... 38 Required Materials ................................................................................................................................. 38 General Guidelines for Working with Weatherproofing Tape ................................................................ 38 Weatherproofing Procedures ................................................................................................................. 39 Appendix B Warranty Statements .......................................................................................................... 42 Hardware ................................................................................................................................................ 42 Software .................................................................................................................................................. 42 Additional Conditions.............................................................................................................................. 43 No Fault Found ........................................................................................................................................ 43 Warranty Limitations .............................................................................................................................. 43 Warranty Disclaimer ............................................................................................................................... 43 Obtaining Warranty Service .................................................................................................................... 44 Out of Box Failure (OBF) / Dead on Arrival (DOA) .................................................................................. 45 Advanced Replacement .......................................................................................................................... 45 Assistance................................................................................................................................................ 46 Page 4 Quantum 2200 Installation Guide v2.1 Figures Figure 1: PureWave Quantum 2200 Base Station .............................................................................. 11 Figure 2 Mounted PureWave Quantum 2200 .................................................................................... 11 Figure 3: Base Station Connectors ..................................................................................................... 13 Figure 4: Base Station Mounting Holes ............................................................................................. 15 Figure 5: Example of Mounting Point with Spacing Hardware ............................................................ 15 Figure 6: Example Deployment Consisting of Pole Attached to a Metal Frame ................................... 16 Figure 7: Base Station Pole Mount Assembly Diagram ....................................................................... 18 Figure 8: Base Station Mounting Bracket .......................................................................................... 18 Figure 9: Pole Mounting Plates ......................................................................................................... 19 Figure 10: Base Station Mounting Bracket Alignment ........................................................................ 19 Figure 11: Pole Mount Subassembly ................................................................................................. 20 Figure 12: Pole-Mounted PureWave Antenna ................................................................................... 21 Figure 13 Antenna Connection ......................................................................................................... 24 Figure 14: Optional GPS Antenna and Mounting Kit .......................................................................... 25 Figure 15: T-567B RJ-45 Connector .................................................................................................... 29 Figure 16: RJ-45 IP67 Weatherproof Housing Assembly ..................................................................... 29 Figure 17: Assembled RJ-45 IP67 Weatherproof Housing ................................................................... 30 Figure 18: IP67 DC Power Connector and Pin Assignments ................................................................ 32 Figure 19: Crimp and Insertion Tools for the DC Power Connector ..................................................... 32 Figure 20: Slide connector onto cable before crimping. .................................................................... 33 Figure 21: Wire properly inserted into circular socket crimp contact .................................................. 33 Figure 22: Side and top views of correct crimping technique ............................................................. 34 Figure 23: Properly completed first crimp ......................................................................................... 34 Figure 24: Start the second crimp with tool section A. ................................................................... 35 Figure 25: Complete the second crimp with tool section B. ........................................................... 35 Figure 26: Fully completed pin .......................................................................................................... 35 Figure 27: Pins inserted into DC power connector ............................................................................. 36 Figure 28: Use needle-nose pliers to push the pins further into the plug. .......................................... 36 Figure 29: Use insertion tool to secure the pins in the plug. .............................................................. 37 Figure 30: Front view of plug with crimp pins properly inserted......................................................... 37 Figure 31: Completed Power Connector Assembly ............................................................................ 37 Figure 32: Proper Weatherproof Tape Overlap .................................................................................. 38 Figure 33: Torque Wrench for N-Type Connector .............................................................................. 39 Figure 34: First Plastic Tape Layer ..................................................................................................... 39 Figure 35: First Rubber Tape Layer .................................................................................................... 40 Figure 36: Wrapping Plastic Tape on Top of the Rubber Tape ............................................................ 40 Figure 37: Wrapping Plastic Tape 1 Below Previous Wrap ............................................................ 41 Page 5 Quantum 2200 Installation Guide v2.1 Tables Table 1: Quantum Environmental and Mechanical Specifications ...................................................... 12 Table 2: Base Station LED Description ............................................................................................... 13 Table 3: Base Station Connector Descriptions ................................................................................... 14 Table 4: PureWave Quantum Base Station Pole Mount Kit Contents .................................................. 17 Table 5: PureWave Quantum Surge Protection Kit Contents .............................................................. 22 Table 6: PureWave Quantum Surge Protection Kit Specifications....................................................... 23 Table 7: PureWave Quantum Basic DC Installation Kit Contents ........................................................ 27 Table 8: Cat 5e+ Connector Pinout .................................................................................................... 28 Table 9: Summary of PureWave RMA Conditions and Charges ........................................................... 45 Page 6 Quantum 2200 Installation Guide v2.1 Regulatory Notice This device complies with the FCC limits a class B digital device, pursuant to Part 15 of the FCC Rules. A complete list of regulatory certifications can be provided by PureWave upon request. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

Re-orient or relocate the receiving antenna/s. Increase the separation between the equipment and other receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. Shielded cables and I/O cords must be used for this equipment to comply with the relevant FCC regulations. Changes or modifications not expressly approved in writing by PureWave Networks may void the user's authority to operate this equipment. Note: This device must be professionally installed, and the operator and/or the licensed spectrum holder has the responsibility to comply with FCC regulations. Note: The contention protocol MUST be turned on and used for the specified band (3.65GHz

- 3.7 GHz) in the specified country or wherever FCC rules and regulations are enforced. Failure to comply makes the operation of this device illegal. Page 7 Quantum 2200 Installation Guide v2.1 Safety Precautions When installing this equipment, please observe the following precautions to minimize the risk of danger or personnel injury:

NEVER install equipment if there is a chance of lightning or other adverse weather conditions. NEVER install equipment in a wet location unless the equipment is specifically design for wet locations. NEVER touch un-insultated wires or terminals unless the wire has been disconnected from any equipment. ALWAYS use caution when installing or modifying cables. ALWAYS disconnect all lines and power connections before servicing or disassembling this equipment. ALWAYS assume that all components and assemblies are static sensitive and always follow local ESD-prevention guidelines to prevent equipment damage. For any external power supply that provides the power source for the PureWave equipment, replace any power supply fuse with the same rating or equivalent; otherwise PureWave Networks cannot not be responsible for any subsequent damage to the equipment. For performance and safety reasons, only power supplies listed for use with telephone equipment by a Nationally Recognized Testing Laboratory (NRTL) should be used with equipment. ALL wiring external to the product(s) should follow the provisions of the current edition of the National Electrical Code. These units contain no user serviceable components. Only authorized service personnel should service or repair these units. Use only isolated Class 2 Power Source, Rated 48V dc 5.0A Minimum. Page 8 Quantum 2200 Installation Guide v2.1 1 Preface 1.1 About This Document This guide is intended for use by a professional installer who performs the physical installation of any PureWave Quantum 2200 Base Station. It does not cover base station functional setup or operation. For detailed information about setup and operation of the PureWave Quantum 2200 Base Station, please refer to the Quantum 2200 Users Guide. Always refer to the current set of Release Notes for the most up to date information and a description of the current features as they relate to the PureWave system. These may be different from the information contained within this Installation Guide. 1.2 Symbols used in this Document Notes, cautions, and timesavers use these conventions and symbols:

Tip Note Caution Warning Means the following will help you solve a problem. The tips information might not be troubleshooting or even an action, but could be useful information. Means reader take note. Notes contain helpful suggestions or references to materials not contained in this manual. Means reader be careful. In this situation, you might do something that could result equipment damage or loss of data. This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. 1.3 Packaging and Components Your PureWave Quantum Base Station and accompanying installation kits and hardware have been packaged into a single box. Some such kits are optional and, if not present, are replaced with empty boxes to ensure safe and secure shipping. All are listed below:

PureWave Quantum Base Station PureWave Quantum Basic DC Installation Kit PureWave Quantum Pole Mounting Kit PureWave Quantum Surge Protection Kit GPS Antenna Kit Page 9 Quantum 2200 Installation Guide v2.1 If you have purchased a 6-Port Antenna Panel or other antenna(s) from PureWave then it is packaged in a separate box along with its mounting kit and instructions. Please refer to the instructions provided with your antenna(s) for proper mounting procedures. Connection of the antennas to the base station is covered within this guide. 1.4 Locating the Product Serial Number The product identification information, serial number, and certification information are located on a label on the side panel of the base station. Please take note of and keep this information for your records, as it is very important for warranty and support services. 1.5 Obtaining Documentation and Support All requests for documentation and/or support should be addressed to Technical Support Department PureWave Networks, Inc. 2660-C Marine Way Mountain View, CA 94043 E-mail: support@pwnets.com Tel: 650-528-5200 Fax: 650-528-5222 Page 10 Quantum 2200 Installation Guide v2.1 2 Base Station Basics 2.1 Physical and Environmental Specifications The PureWave Quantum 2200 Base Station (Figure 1) is made up of a single, weather-resistant enclosure with overall dimensions 17.5 x 16.7 x 5.3 (44cm x 42cm x 13cm). The base station is a single self-

contained unit and has no user-serviceable components. Figure 1: PureWave Quantum 2200 Base Station The PureWave Quantum Base Station can be installed indoors or outdoors (Figure 2), however the antennas must always be installed outdoors. Figure 2 Mounted PureWave Quantum 2200 Page 11 Quantum 2200 Installation Guide v2.1 2.2 Physical and Environmental Specifications Table 1 lists the mechanical, electrical, and environmental properties of the PureWave Quantum Base Station. Physical & Environmental Specifications Dimensions Weight Power Temperature Humidity Altitude 17.5 x 16.7 x 5.3

(44cm x 42cm x 13cm) 32lbs (14.5kg) (does not include mounting hardware)

-48 VDC 90 Watts Max

-40C to +55C (ETSI EN 300 019-1.4 Class 4.1E) Note: An available solar shield is required for ambient temperatures exceeding +45C with full sun exposure. 5-100% non-condensing To 10,000 ft above sea level Surge Protection UL497B Lightning Protection Min 10kA IEC 6100-4-5 (optional via external kit) Weatherproofing IEC IP67 Wind Loading 160Km/hr operation, 200Km/hr survival Safety and IEC IP EN 300 019-2-2, GR487, IEC 60529 Vibration and Dust ETSI EN 300 019-1-4 Class 4.1E Table 1: Quantum Environmental and Mechanical Specifications Page 12 Quantum 2200 Installation Guide v2.1 2.3 Connectors and Indicators Figure 3 shows the bottom panel of the base station, where all the connectors and indicators are located. Figure 3: Base Station Connectors The base station connector panel contains 3 high-intensity LEDs that are intended to be viewable from the ground for quick confirmation of the operational state of the base station. Table 2 describes the function of each LED. LED STATUS LINK Function Green - BS is up and running normally. No faults detected. Blinking Red System booting up, or system is temporarily down. Solid Red - Fault detected. Off LEDs disabled or Power is off. Fault detected if POWER LED is Green, but STATUS LED is Off. Solid Green Connected to an Ethernet switch. Blinking Green Ethernet packet activity. Off LEDs disabled or no Ethernet activity detected. POWER Green Power is being supplied to the BS. Off LEDs disabled or no power is being supplied to the BS. Table 2: Base Station LED Description The function of each base station connector/port is described in Table 3. Note that every present connector must be terminated according to the instructions in this guide to ensure proper base station operation. Page 13 Quantum 2200 Installation Guide v2.1 Connector POWER GND GPS ETH-1 ETH-2 CONSOLE ANT 1-2 Function

-48VDC power source inputs for the unit. DC power connector: Fits Tyco P/N 796095-2 connector. This M5 screw provides a ground connection point to the base station. It is the installers responsibility to ensure that the unit is professionally grounded and complies with all relevant local codes. N-type connector for mandatory external GPS antenna. 3.3V power on center pin. This Gigabit Ethernet port serves as the data traffic backhaul Interface and also provides for in-

band management of the base station. Note that this port may be physically routed directly to the operators network equipment, or it may be daisy-chained through additional PureWave Quantum sectors by routing it to another units ETH-2 port. Cat-5 (RJ-45), Single-Mode Fiber (HartingPull/Han 3 A), and Multi-Mode (LC duplex) Fiber options are available for the ETH-1 port. This Gigabit Ethernet port serves as an incoming daisy-chain port from a neighboring sector, and may be used for out-of-band management of the base station. It may also be used to connect to an external device, such as a web camera. Daisy-chained traffic is aggregated and passed through the ETH-1 port. Cat-5 (RJ-45), Single-Mode Fiber (HartingPull/Han 3 A), and Multi-Mode (LC duplex) Fiber options are available for the ETH-2 port. RJ-45 based RS-232 port for CLI control via a console. Defaults settings are 38400, 8, None, 1, Xon/Xoff.Xoff N-type Tx / Rx Antenna Ports. Table 3: Base Station Connector Descriptions Page 14 Quantum 2200 Installation Guide v2.1 3 Mounting the Base Station 3.1 Fundamentals The back side of the base station includes 6 metric M8-1.25 threaded mounting holes, as shown in Figure 4. Figure 4: Base Station Mounting Holes Because the mounting holes are recessed, provisions must be made to provide for spacing between the mounting points and the mounting bracket or surface, as exemplified in Figure 5. Figure 5: Example of Mounting Point with Spacing Hardware It is imperative that proper airflow be maintained on all sides of the base station and that all heat sinks remain unobstructed. In the case of wall or surface mounting a minimum of 2 of space should be maintained between the base station and mounting surface. Page 15 Quantum 2200 Installation Guide v2.1 3.2 The Pole-Mount Kit The optional PureWave Quantum Base Station Pole Mounting Kit provides all hardware required for installing the base station on a pole ranging from 2.5-5 inches in diameter. It is important to note that the use of a pole mount in no way dictates that the base must actually be deployed on top of a long pole, although in many cases it will in fact be. Alternatively the base station may be conveniently attached to a short pole, which may then be easily mounted to a metal frame or struts that conform to the specific deployment using commonly available hardware. An example of this is shown in Figure 6. Figure 6: Example Deployment Consisting of Pole Attached to a Metal Frame The PureWave Quantum Base Station Pole Mount Kit has been specifically designed to handle the weight of the base station. However, it is critical that the full weight of the base station plus mounting hardware be considered in designing the overall base station mounting solution. Fully assembled, the PureWave Quantum Base Station Pole Mount Kit weighs 16lbs (7.3kg). Page 16 Quantum 2200 Installation Guide v2.1 If you have ordered the pole mounting kit then it was shipped in the same box as the base station. Please locate the kit and compare its contents to Table 4. Item Quantity Purpose a) Front Pole Mount Plate b) Back Pole Mount Plate c) Base Station Mounting Bracket 1 1 1 d) Carriage Bolt SAE 3/8-16 Up to 12 e) Nylon Pushnut, 3/8 f) Nylon Tie Wrap g) Hex Nut, SAE 3/8-16 h) Split Lock Washer, SAE 38 i) Hex Bolt, Metric M8 -1.25 X 16 j) Hex Bolt, Metric M8 -1.25 X 25 4 2 4 4 6 4 Grips pole along with back pole mount plate (b). The base station mounting bracket also connects to this piece. Grips pole along with front pole mount plate (a). Attaches to base station mounting holes, as well as to front pole mount plate (a). A built-in handle facilitates carrying the base station when attached. Selection of carriage bolts ranging from 6 to 10, fully or partially threaded. Select a set of 4 that are appropriate to the installation, and use with push nut (e), hex nut (g), and washer

(h) to fasten front (a) and back (b) mounting plates to pole. Slide onto carriage bolt (d) to prevent it from slipping out of front mounting plate (a) while fastening hex nut (g) and washer

(h). Use to temporarily affix mounting hardware to pole during the installation process. Use with carriage bolts (d) and split lock washers (h) as described. Use with carriage bolts (d) and hex nuts(g) as described. Use with M8 split lock washers (k) to fasten base station mounting bracket (c) to base station. Use with M8 split lock washers (k) to fasten base station mounting bracket (c) to front pole mount plate (a). k) Split Lock Washer, Metric M8 10 Use with M8 bolts (i, j) as described. Table 4: PureWave Quantum Base Station Pole Mount Kit Contents 3.2.1 Pole Mount Installation Procedure Figure 7 illustrates how the entire pole-mounting mechanism connects together and to the base station. The pole mount mechanism consists of a base station bracket (Figure 8) that attaches to the mounting points on the back of the base station, and a pair of pole-mount plates (Figure 9) that grip the pole and to which the base station bracket attaches. Table 4 indicates where each included piece of hardware is to be used and should be strictly followed to ensure a secure and proper installation. Page 17 Quantum 2200 Installation Guide v2.1 Figure 7: Base Station Pole Mount Assembly Diagram Figure 8: Base Station Mounting Bracket Page 18 Quantum 2200 Installation Guide v2.1 Figure 9: Pole Mounting Plates First mount the Base Station Mounting Bracket (Figure 8: Base Station Mounting Bracket) to the base station using the provided hardware, as indicated in Table 4. When installing the base station mounting bracket onto the base station, be sure to align it as shown in Figure 10. Note that the bracket is designed for upright mounting of the base station; that is, mounting with the connectors facing down. Tighten the bolts to a torque of 30 in-lbs. Figure 10: Base Station Mounting Bracket Alignment The base station bracket may be mounted to the base station ahead of time as it has a built-

in handle that facilitates its transportation and carrying the base station up a tower. To improve the effectiveness of connector waterproofing and to optimize the base stations thermal performance, it is recommended that the base station be mounted in an upright position, with the connectors at the bottom. Note that the base station bracket is designed specifically to attach to the 6 recessed mounting holes on the base station, and hence can be useful in a variety of mounting scenarios. However, use of this bracket without the pole mounting plates designed specifically to accompany it is at the sole discretion and responsibility of the customer. Page 19 FrontMountingPlateRearMountingPlate Quantum 2200 Installation Guide v2.1 The next step is to mount the front and back pole mount plates (Figure 9) to the pole, using the provided hardware as indicated in Table 4. Nylon tie wraps have been provided for convenience to temporarily affix the front mounting plate to the pole during the installation process. A selection of carriage bolts has been provided to accommodate a variety of pole diameters. Select a set of 4 bolts that enable a secure fit to your pole. Insert each carriage bolt through the front mounting plate and slide a pushnut onto it to temporarily hold it in place. Slide the back mounting plate onto the carriage bolts, sandwiching the pole in-between, then add lock washers and hex nuts tightened to a torque of 30 in-lbs. Insert the four provided M8-1.25x25 hex bolts along with M8 split lock washers into the side holes of the front pole mounting plate and leave them loose for now. These bolts provide the attachment point for the base station mounting bracket to the pole mount subassembly. The completed subassembly is shown in Figure 11. Figure 11: Pole Mount Subassembly Finally, using the handle on the base station mounting bracket, lift the base station subassembly onto the pole mount subassembly and hang it on the four side mounting bolts. Torque the bolts to 30 in-lbs. For this and other installations in this manual, a suitable anti-corrosion lubricant should be applied to all exposed metal surfaces. For your convenience a tube of Bostik NEVER-SEEZ has been provided in the PureWave Quantum Base Station Basic Installation Kit. Note that these types of lubricants tend to be messy and sticky to apply due to the nature of their intended application. Always read the labels or instructions provided and take necessary pre-cautions during application. Page 20 Quantum 2200 Installation Guide v2.1 4 Mounting the Antennas PureWave Quantum Base Stations can be deployed with virtually any type of antennas that operate in the relevant frequency band and that meet regional regulatory standards. Antenna mounting procedures will vary by model and manufacturer, so we refer the installer to the instructions that came with the antenna(s) and/or antenna mount(s) for their secure and proper installation (Figure 12) As a general rule the antennas should be installed as close as practical to the base station. This minimizes signal loss which is directly proportional to cable length. In addition, a high-quality, low-loss coaxial cable capable of propagating the relevant frequencies (such as Hyperlink Technologies P/N CA3N100 or Times Microwave LMR 400) should be utilized between the antenna and base station. In the event that the base station cannot be co-located with the antennas the choice of cable is even more important, as signal losses can be significant. For example, LMR 400 cable has an attenuation loss of 6.8dB per 100ft at a frequency of 2.5GHz. It is important that cable loss be computed and understood to ensure that adequate range will still be achieved for your deployment needs. Figure 12: Pole-Mounted PureWave Antenna Page 21 Quantum 2200 Installation Guide v2.1 5 Connecting the Antennas to the Base Station 5.1 Installation of Lightning Surge Protectors In most environments it is essential for the base station to be installed with external protection against surges caused by lightning on the antenna cables. PureWave therefore recommends that suitable surge protectors be installed on each base station antenna connector. For an indoor installation of the Base Station, surge protection devices should be installed at the entrance to the building that houses the Base Station. For an outdoor installation they are installed on the relevant connectors. The optional PureWave Quantum Surge Protection Kit has been developed for your convenience and provides hardware designed to protect the base station from surges on its antenna connectors. PureWave strongly recommends the use of this kit. It is important to note, however, that every environment and installation is different. Therefore, it is the responsibility of the customer and the installer to ensure that sufficient protection is employed, whether or not this kit is utilized. If you have ordered the PureWave Quantum Surge Protection Kit then it was shipped in the same box as the base station. Please locate the kit and compare its contents to Table 5. Item Quantity Purpose

(a) Connector Weather Proofing Kit

(b) Connector, Insulated Crimp Ring Terminal, Lug, AGW 10-12, #10

(c) Surge Arrestor, RF, N-Type M/F

(d) Lubricant, NEVERSEEZ Regular Grade 1OZ

(e) External Tooth Lock Washer, Metric, M5

(f) Hex Nut, Metric, M5-.8

(g) DC Surge Protection 1 2 2 1 2 2 1 Contains tape and butyl rubber for weatherproofing the antenna connectors and surge arrestors (c). Used to create ground connections between Quantum BS Surge Arrestor (c) and ground terminal on BS. Attaches to a base station antenna connector on one side, and an antenna cable on the other side. Anti-corrosion / anti-seize lubricant for use on exposed metal surfaces. Hex nut (f) to fasten crimp rings (b) to Surge Arrestor (c). Use with washer (e) to fasten crimp rings (b) to Surge Arrestor (c). Quantum Base Station DC Power Supply Surge Protection. Table 5: PureWave Quantum Surge Protection Kit Contents Page 22 Quantum 2200 Installation Guide v2.1 Specifications for the PureWave Quantum Surge Protection Kit are summarized in Table 6. Surge Protector Feature Specifications Surge Capabilities IEC 1000-4-5, 8/20s @ 10kA Frequency Range Return Loss Insertion Loss RF Power Limit 2-6GHz

> 20dB 0.2dB 10 Watts Max Temperature

-40oC to +85oC Relative Humidity 0-100% condensing Surge Throughput Energy 0.5J (6kV/3kA 8/20s) Peak Let-Through Voltage 3V (6kV/3kA 8/20s) Table 6: PureWave Quantum Surge Protection Kit Specifications The following surge protector installation procedure is specific to the PureWave Quantum Surge Protection Kit. If you have chosen to use alternative surge protection hardware then please follow the instructions received with that hardware to ensure proper installation. However, we still recommend that you review the procedure below, as much of it will still be relevant. Step 1:

Screw one surge arrestor onto each base station antenna connector ANT-1 and ANT-2 and tighten to a torque of 12-15 in-lbs. Step 2: Weatherproof each surge arrestor connection to the base station before proceeding with the Step 3:

next step. Please refer to Appendix A for a general discussion and guidelines on weatherproofing connections. Place the grounding bar over the row of surge arrestors such that the two ground terminal screws are facing the bottom of the base station, and secure in place with the lock washers and nuts that came packaged with each surge protector. Tighten each nut to a torque of 30 in-lbs. Step 4: Wire ground connections from the ground bar terminals to the base station connector panel grounding terminal using the provided crimp rings and hardware. Base station grounding procedures are covered in Appendix A. Page 23 Quantum 2200 Installation Guide v2.1 5.2 Connecting the Antennas to the Base Station The base station has two N-type antenna connectors that must be attached to each installed antenna using high-quality coaxial cable, as discussed in Section 4. The number of connectors/adapters used should also be minimized as they are especially lossy. Most industrial-grade antennas, including all PureWave antennas, utilize N-type connectors. Regardless of the antenna-side connector type, it is important to obtain or construct cables with the correct respective terminal types and of the correct length to avoid the need for additional connectors or adaptors. Figure 13 Antenna Connection Prepare and run 2 low loss coax cables from the base station to the antenna. Connect each base station

(or surge arrestor) connector to the corresponding port number on the installed antennas. All antenna ports must be connected (Figure 13). Finally, weatherproof every connector. Please refer to Appendix A for a general discussion and guidelines on weatherproofing connections. Thorough weatherproofing of all connections is extremely important to ensure long-term base station operation as well as validation of the warranty. Page 24 Quantum 2200 Installation Guide v2.1 6 Installing the GPS Antenna WiMAX base stations utilize GPS (the Global Positioning System) to maintain tight synchronization and coordination among themselves in a network. This assures that all base stations in the network transmit and receive in harmony, as they must all utilize the same Downlink / Uplink Ratio. 6.1 Selecting and Mounting a GPS Antenna PureWave Quantum Base Stations incorporate an integrated GPS receiver which must be connected to an external GPS antenna view of a number of GPS satellites. Installation location flexibility and the amount of tolerable obstruction are heavily dependent upon the quality and capabilities of the chosen antenna. The choice of GPS antenna is an important one, as there are many models available in the market for many purposes, and hence some are very inexpensive but also low gain and/or low quality. A poor GPS antenna can easily become the point of failure of your system. PureWave strongly recommends the use of a high-quality GPS antenna and therefore offers an optional GPS Antenna Kit, featuring a GPS antenna with integrated 40dB low-noise amplifier and mount kit

(Figure 14). Figure 14: Optional GPS Antenna and Mounting Kit If you have ordered the GPS Antenna Kit it was shipped in the same box as the base station. The optional GPS Antenna Kit it includes all required mounting hardware and instructions and we refer the installer to that documentation for secure and proper installation. Similarly, if an alternative GPS antenna has been chosen, please refer to the instructions provided by the manufacturer for proper mounting procedures. Page 25 Quantum 2200 Installation Guide v2.1 6.2 Connecting the GPS Antenna to the Base Station The base station utilizes an N-type GPS antenna connector. The GPS antenna that comes as part of the optional GPS Antenna Kit also has an N-type connector. Prepare a high-quality coaxial cable of the appropriate length and with the appropriate connector types for use in connecting the GPS antenna to the base station. Connect the coaxial cable from the external GPS antenna to the N-type female connector marked GPS on the base station, and weatherproof the connectors. Please refer to Appendix A for a general discussion and guidelines on weatherproofing connections. Page 26 Quantum 2200 Installation Guide v2.1 7 Connecting Ethernet and Serial Console Cables 7.1 The PureWave Basic DC Installation Kit Each PureWave Quantum Base Station is shipped with the PureWave Quantum Basic DC Installation Kit, which contains hardware and components required for connecting and waterproofing the Ethernet ports, console port, the power port, and the grounding terminal. This kit has been shipped in the same box as the base station. Please locate it and compare its contents to Table 7. Item Quantity Purpose a) 6 Cat 5e Cable b) DB9 Female to DB9 Female Serial Cable c) Network DB9 Female to RJ45 Adaptor d) DC Connector 4 Pin Female Plug e) 14-18 AWG Circular Socket Crimp Contact f) Cable Clamp Connector g) RJ45 IP67 Weatherproof Housing h) Insulated Crimp Ring Terminal i) NEVER-SEEZ Lubricant, 1oz tube j) Weatherproofing Kit k) RJ45 Plug Shielded Connector l) Washer, Metric M5 Flat m) Washer/Metric, M5 External Tooth Lock n) Hex Nut Metric, M5-.8 o) Extra Hardware Kit 1 1 1 1 4 1 3 1 1 1 6 1 1 1 1 Connects base-station serial/console port connector to DB9 to RJ45 adaptor (c) Connects serial consol/terminal to DB9 to RJ45 adaptor (c) Couples cables for serial console connection (a, b) Part of DC power connector subassembly (d, e, f) Part of DC power connector subassembly (d, e, f) Part of DC power connector subassembly (d, e, f) Weatherproof housing subassemblies for ETH-1, ETH-2, and Console Connectors Attaches to base station ground terminal using provided hardware (l, m, n) Anti-corrosive lubricant For all connectors. Recommended weatherproofing procedures are provided in this document. Provided for use in creating custom-length CAT-5 cables for ETH1, ETH2, and Console connections. Part of crimp ring subassembly (h, l, m, n) Part of crimp ring subassembly (h, l, m, n) Part of crimp ring subassembly (h, l, m, n) A variety of extra parts for convenience Table 7: PureWave Quantum Basic DC Installation Kit Contents Page 27 Quantum 2200 Installation Guide v2.1 7.2 Preparing the Ethernet and Console Cables ETH-1 and ETH-2 connectors should both be run from the base station to the operators network equipment. The CONSOLE connection may be connected for initial provisioning and thereafter on an as-

needed basis or it may be permanently connected as with the Ethernet connections. Please take into consideration that the RS-232 console connection is less tolerant to noise and interference in long cable runs than the Ethernet interfaces. The maximum length of the Cat-5e cables connecting the Ethernet or console ports on the base station to the Service Providers network equipment is limited to 100m (328ft). When the Base Station is mounted outdoors it is important to use outdoor rated Category-

5e+ Gigabit Ethernet Cable, such as Commscope Ultra IITM, and shielded outdoor rated metal RJ-45 connectors. Six high-quality shielded connectors have been included in the PureWave Quantum Basic Installation Kit. Prepare and connect two Cat 5e+ cables from the ETH-1 and ETH-2 ports to the operators network equipment, and one more for the CONSOLE port if desired. In preparing the Cat 5e+ cables, terminate each at the base station in accordance with the T-568B wiring standard, as described in Table 8 and illustrated in Figure 15. Pair Number Wire Color Pin Number 1 2 3 4 white / blue Blue white / orange Orange white / green green white brown brown 5 4 1 2 3 6 7 8 Table 8: Cat 5e+ Connector Pinout Page 28 Quantum 2200 Installation Guide v2.1 Figure 15: T-567B RJ-45 Connector 7.3 Weatherproofing the Ethernet and Console Connections If the CONSOLE port is not to be permanently connected then it should remain tightly capped for the time-being. A serial cable, a 6 Cat-5 cable, and a DB9 to RJ-45 adapter has been supplied with the PureWave Quantum Basic DC Installation Kit for bring-up and provisioning purposes utilizing the CONSOLE port. Please refer to the PureWave Quantum User Manual for additional information. A set of three RJ-45 IP67 weatherproof housing assemblies have been supplied as part of the PureWave Quantum Basic DC Installation Kit for the purpose of weatherproofing the Ethernet and console connectors. The procedure for installation of the housing onto each cable and connector is provided below. Note that at least one end of the cable should be crimped with a RJ-45 connector only at the end of the procedure. Please refer to Figure 16 during the following procedure, as it shows the interconnection and orientation of each part in the assembly. Figure 16: RJ-45 IP67 Weatherproof Housing Assembly Page 29 Quantum 2200 Installation Guide v2.1 Slip the Sealing Nut onto the RJ-45 cable. Place the screw nut onto the housing with the threads facing forward Insert the seal into the housing Insert the cable through the seal and housing exiting the front of the housing Strip cable sheath Crimp the RJ 45 plug onto the cable Pull the cable back so the plug fits into the housing. Secure the sealing nut in place Stick the gasket onto the front end of the housing Step 1:

Step 2:

Step 3:

Step 4:

Step 5:

Step 6:

Step 7:

Step 8:

Step 9:

The fully assembled connector is shown in Figure 17 and can now be attached to each base station RJ-45 connector thus creating a weather protected connection. Additional weatherproof wrapping, as described in Appendix A is still, however, recommended. Figure 17: Assembled RJ-45 IP67 Weatherproof Housing Page 30 Quantum 2200 Installation Guide v2.1 8 Connecting DC Power and Ground 8.1 Base Station Single-Point Grounding Extensive analysis and investigation of installations has led to the belief that the root cause at the heart of the majority of power-related failures is likely to be the presence of multi-point grounding of equipment. Single point grounding eliminates ground voltage differentials and thus dramatically increases equipment survivability during surges. Single point grounding requires that the grounding leads from antennas, base station, and surge protection devices for a particular sector are bonded together at the same point on the tower or in the shelter, in the case of an indoor installation. It is not necessary to bond all sectors together. An insulated crimp ring has been supplied as part of the PureWave Quantum Basic DC Installation Kit

(Table 7), along with the hardware required to mount it to the base station GND terminal connection. Furthermore, if the optional PureWave Quantum Surge Protection Kit (Table 5) has been installed then it includes a set of crimp rings for mounting on the ground terminals of the supplied grounding bar. Conductors from each installed crimp ring should be connected together, and then tied to a single-point common grounding point. The following grounding guidelines apply, whether or not the PureWave Quantum Surge Protection Kit has been installed:

Surge protection devices generally connect to ground by using a ground wire. Cut any extra ground wire length when finished connecting it to the single point earth ground. Never loop or coil up the ground wire, and avoid sharp bends. Always connect it straight to ground. A good earth ground impedance is less than 1.0 ohm. Measure ground impedance at the point where the protector ground wire is connected and not at the ground rod. Connect the protector ground wire and equipment ground (both power ground and telecomm. ground) to a single common ground. Make sure all connections are fastened securely. 8.2 Preparing the DC Power Connector The DC power source to a PureWave Quantum Base Station must be capable of delivering up to 10 Amps of current at -48 VDC. The base station requires ~6 Amps max at -48VDC (range -40VDC to -

57VDC, -38VDC min). The power connector used on the base station will accommodate 14 to 18 gauge wire. Remember to take account of the voltage drop when running long power cable runs. For example, for 18 AWG and a cable length of 100 feet, a nominal 48VDC supply delivering into a 6A load will have a voltage drop of 9.3 volts. Page 31 Quantum 2200 Installation Guide v2.1 This DC power connector assembly has been provided as part of the Basic DC Installation Kit (Table 7) and consists of a 4-pin female power connector plug, a set of crimp contacts, and a cable clamp. The connector with pin assignments is shown in (Figure 18). Figure 18: IP67 DC Power Connector and Pin Assignments To successfully complete the power cable assembly you will need the following tools (not provided). Wire-strippers Needle-nose pliers Phillips Screwdriver Crimping tool The Tyco 91519-1 Crimp Tool was specifically designed for the pins of the Quantum power connector. However, due to its high cost we have focused on a procedure for creating the connector with the much more affordable Waldom W-HT1921 Crimp Tool and plus the Tyco / AMP 200893-2 Insertion Tool. All are shown in Figure 19. If you choose to use the optional Tyco crimp tool then please follow the instructions included with the tool for the proper crimping procedure. Figure 19: Crimp and Insertion Tools for the DC Power Connector Page 32 Quantum 2200 Installation Guide v2.1 Step 1: Use wire strippers to remove about 1/4 inch of insulation from each wire and approximately 1 of outer cable insulation. It is important that each wire be the same length, with equal lengths of stripped wire. Step 2:

Slide the circular socket connector over the power cable as shown in Figure 20. Figure 20: Slide connector onto cable before crimping. Step 3:

Place stripped wire into circular socket crimp contact such that insulated wire is present at the first crimp location and bare wire is present at the second crimp location (Figure 21). Figure 21: Wire properly inserted into circular socket crimp contact Using the Waldom crimping tool in crimp head location B, squeeze carefully, assuring that the first crimp location is forming properly before wielding full pressure. Give it a slight tug to ensure that it is secure and that the wire is tightly crimped into place. The pin connector crimp locations are U-shaped and must be placed in the crimper such that the open end of the U-shape points toward the A/B locations. When forming the U-shaped crimp it is important to ensure the crimp folds back on itself, creating a heart-shape. Please refer to Figure 22 and Figure 23. Page 33 Step 4:

Quantum 2200 Installation Guide v2.1 Figure 22: Side and top views of correct crimping technique Figure 23: Properly completed first crimp Step 5:

Crimp the cable again at the second crimp location by starting with the A side of the crimping tool (Figure 24). Release crimping pressure when the second crimp location begins to curl. Next place the second crimp location in section B of the tool (Figure 25) and securely complete the crimp. Page 34 Quantum 2200 Installation Guide v2.1 Figure 24: Start the second crimp with tool section A. Figure 25: Complete the second crimp with tool section B. The fully completed pin is shown in Figure 26. Now repeat Steps 3-5 for each of the three additional pins. Figure 26: Fully completed pin Page 35 Step 6:

Step 7:

Step 8:

Quantum 2200 Installation Guide v2.1 Using your fingers, insert the crimped pins into the corresponding holes of the DC power connector plug (Figure 27). Be sure to match the pin-out as specified earlier. Figure 27: Pins inserted into DC power connector Next use needle nose pliers to insert the pins further by grabbing the first crimp location and pushing all the way into the connector body. It helps if you place the connector face down on a table to provide extra leverage. It is critical that the pins are pushed as far into the connector body as possible. See Figure 28 Figure 28: Use needle-nose pliers to push the pins further into the plug. Now use the insertion tool to secure the pins inside the connector plug (Figure 29). An audible click should be heard when the pin is fully inserted into the connector body. Properly inserted pins will be visible from the front of the connected as shown in Figure 30). Note: It is possible to over-insert the pin when using the pin insertion tool, so take care to gently insert the ping into the connector body. Page 36 Quantum 2200 Installation Guide v2.1 Figure 29: Use insertion tool to secure the pins in the plug. Figure 30: Front view of plug with crimp pins properly inserted Step 9:

Complete the assembly by screwing the plug into the circular socket connector and secure with the cable clamp by tightening the two strain-relief screws using a Phillips screwdriver. The completed assembly is shown in Figure 31. Figure 31: Completed Power Connector Assembly Note that the base station does not have a power switch and will immediately power up if the DC power connector is in place and power is applied. Please do not apply power to the base station until all connections are made in accordance with the instructions in this guide. Then, please refer to the PureWave Quantum Base Station User Guide for additional instructions. Page 37 Quantum 2200 Installation Guide v2.1 Appendix A Connector Weatherproofing Required Materials PureWave recommends that appropriate weather protection sealing be applied to all outdoor installed elements of the system. Weatherproofing tape kits can very effectively seal the junction between mating connectors. Proper and diligent weatherproofing not only protects the connection from water damage, but also prevents vibrations from loosening the interface. A wide range of weather protection materials and kits are commercially available. The PureWave Quantum Basic DC Installation Kit and the Optional PureWave Quantum Surge Protection Kit each include a weatherproofing kit that contains a variety of tapes along with general weatherproofing guidelines. General Guidelines for Working with Weatherproofing Tape When applied, the tape must be above 32F (0C) to ensure adhesion. Do not stretch the tape. Apply only enough tension to provide a smooth wrap. Smooth each wrapped layer with your hands to ensure full adhesion. Do not pull the tape to tear it - always cut it. Pulled tape eventually unravels, decreasing protection. Add extra final layers of tape in warmer climates where there will be long exposure to damaging ultra violet (UV) rays. Two or three extra layers of tape will provide additional UV protection. On vertical runs, the last wrap of 3/4 tape should be wrapped from the bottom to the top. This provides a shingle effect. When wrapping tape, overlap the tape to half-width as shown in Figure 32. Figure 32: Proper Weatherproof Tape Overlap Page 38 Quantum 2200 Installation Guide v2.1 Weatherproofing Procedures The following procedure is illustrated for an N-type antenna connector (without surge connector) but applies to all connector types. Step 1:

Tighten the connection with a torque wrench to the proper torque value (12-15lbs for an N-

type connector) to ensure that correct internal seals and surface contacts are made. One recommended torque wrench for an N-Type connector is the Andre 244379 and is shown in Figure 33. Figure 33: Torque Wrench for N-Type Connector Step 2: Wrap the connection with a layer of 3/4 (19-mm) plastic tape, starting at 1 (25 mm) from the connector. Overlap the tape to half-width as illustrated in Figure 32 and extend the wrapping over the entire connector. Avoid making creases or wrinkles. Smooth the tape edges. See Figure 34. Figure 34: First Plastic Tape Layer Cut a 5 (125-mm) length of rubber tape. Expand the width of the tape by stretching it such that it will wrap completely around the connector and cable. Press the tape edges together so that there are no gaps. Press the tape against the connector and cable. The tape should extend 1 (25 mm) beyond the plastic tape on the cable (Figure 35). Page 39 Step 3:

Quantum 2200 Installation Guide v2.1 Figure 35: First Rubber Tape Layer Step 4:

Start wrapping a layer of 2 (50-mm) plastic tape 1 (25 mm) below the rubber tape, overlapping at half width (Figure 36). Finish the wrap at the flange of the antenna connector and cut the tape. Figure 36: Wrapping Plastic Tape on Top of the Rubber Tape Start wrapping three layers of 3/4 (19-mm) plastic tape, 1 (25 mm) below the previous 2

(50-mm) wrap, overlapping at half width (Figure 37) until the entire connector is wrapped. The tape should be applied in one strip if possible. A strip can be coiled onto an applicator such as a pencil. Apply only enough tension to get good adhesion and keep the tape smooth. Page 40 Step 5:

Quantum 2200 Installation Guide v2.1 Figure 37: Wrapping Plastic Tape 1 Below Previous Wrap Step 6:

Inspect your weatherproofing job for quality. Any exposed areas will quickly become problematic. Repeat for all remaining connectors. Page 41 Quantum 2200 Installation Guide v2.1 Appendix B Warranty Statements Hardware PureWave, Inc (PureWave or the Company) warrants to the end-user (Customer) that this hardware product will conform in all material respects to the specifications provided with the hardware and will be free from defects in workmanship and materials, under normal use and service, for a period of 365 days from the date of original shipment by PureWave. PureWave's sole obligation under this limited warranty shall be, at PureWave's option, to repair the defective product or part, deliver to Customer an equivalent product or part to replace the defective item, or if neither of the two foregoing options is reasonably possible, refund to Customer the purchase price paid for the defective product. All products that are replaced will become the property of PureWave. Replacement products may be new or reconditioned. PureWave's obligations hereunder are conditioned upon the returned of affected articles in accordance with PureWave's Return Material Authorization (RMA) procedures. Subject to the limitations and conditions herein and in the Supply Agreement, after Customer has completed the steps outlined below, PureWave will evaluate each returned Product and will use reasonable commercial efforts to either, in its discretion, repair or replace products confirmed by PureWave as non-conforming that are covered under the warranty provided in the Supply Agreement. PureWave shall be responsible for shipping the repaired or replaced Product to Customer. PureWave will use reasonable commercial efforts to ship repaired or replacement Product within thirty (30) business days of its receipt, however, the allegedly non-conforming Product must be received by PureWave before any replacement unit will be shipped. The above warranty will also apply to any replaced or repaired product for 90 days from the date of shipment from PureWave of the replaced or repaired product, or the remainder of the initial warranty period, whichever is longer. Software PureWave warrants to the Customer that for a period of ninety (90) days from your receipt of the Product (the Warranty Period) the Software will perform substantially in accordance with the Documentation. If the Software fails to comply with the warranty set forth above, your exclusive remedy will be, at the option of PureWave (i) a reasonable effort by PureWave to make the Software perform substantially in accordance with the Documentation, or (ii) return of the purchase price. This limited warranty applies only if you return all copies of the Product, together with proof of purchase, to PureWave during the Warranty Period. Page 42 Quantum 2200 Installation Guide v2.1 This limited warranty is VOID if failure of the Software is due to modification of the Software not made by PureWave, or the abuse or misapplication of the Software. PureWave does not warrant that the Software is error free, that the Customer will be able to operate the Software without problems or interruptions or that the Software or any equipment, system or network on which the Software is used will be free of vulnerability to intrusion or attack. Additional Conditions Notwithstanding anything else herein or otherwise, PureWave reserves the right to establish amendments to this RMA Policy from time to time. Further, PureWave Technical Support may prefer to troubleshoot the wireless link with an onsite Customer technician while the Products are in their original non-conforming state. This process might assist Customer in understanding and troubleshooting the issue. If PureWave was not afforded the opportunity to troubleshoot an allegedly non-conforming Product in original non-conforming state, PureWave may approve or reject the RMA request in its sole discretion, and such Products are not eligible for advance replacement. No Fault Found Notwithstanding sections above, if PureWave cannot duplicate any alleged non-conformity, the Product will be returned to the Customer as "No Fault Found." PureWave reserves the right to charge a testing fee in connection with a returned product that PureWave determines as No Fault Found, and any such payment must be received by PureWave prior to return shipment of the applicable Product to Customer. Warranty Limitations PureWaves warranties do not apply to any product (hardware or software) which has (a) been subjected to abuse, misuse, neglect, accident, or mishandling, (b) been opened, repaired, modified, or altered by anyone other than PureWave, (c) been used for or subjected to applications, environments, or physical or electrical stress or conditions other than as intended and recommended by PureWave, (d) been improperly stored, transported, installed, or used, or (e) had its serial number or other identification markings altered or removed. Warranty Disclaimer PURWAVES SPECIFIC WARRANTIES SUMMARIZED ABOVE ARE THE ONLY WARRANTIES GIVEN BY PUREWAVE WITH RESPECT TO ITS PRODUCTS (HARDWARE AND SOFTWARE) AND ARE GIVEN IN LIEU OF ANY AND ALL OTHER WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY, OR ARISING BY CUSTOM, TRADE USAGE, OR COURSE OF DEALING, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND PUREWAVE DISCLAIMS ANY AND ALL OTHER WARRANTIES TO THE MAXIMUM EXTENT PERMITTED BY LAW. Without limiting the Page 43 Quantum 2200 Installation Guide v2.1 generality of the foregoing sentence, PureWave makes no warranty or representation, either expressed or implied, as to, and disclaims all liability and responsibility for, (a) the operation, compliance, labeling, or packaging of any of its products under the laws of any jurisdiction outside of the United States of America and (b) the regulatory compliance of any products in any jurisdiction in which it has not specifically identified compliance or the use of any product in any jurisdiction in any manner other than as contemplated in the regulatory certifications and approvals for that product in that jurisdiction. To the extent an implied warranty cannot be excluded, such warranty is limited in duration to the warranty period. The disclaimer and exclusion applies even if the express warranty fails of its essential purpose. Obtaining Warranty Service Customer must contact the Company, by sending an e-mail to support@pwnets.com to obtain warranty service authorization. When contacting PureWave for support, please be prepared to provide the product description and serial number and a description of the problem. The Customer will be expected to complete a Return Material Authorization (RMA) form to initiate the request. Full instructions as to how to complete and where to send the form are provided on the form. Date of proof of purchase from PureWave will be required. Products returned to PureWave Inc must be pre-authorized by PureWave with a Return Material Authorization (RMA) number and sent prepaid and packaged appropriately for safe shipment. The Customer requesting the RMA will be the exporter. The exporter is responsible to ship RMA equipment to PureWaves address and has to bear the cost and risk involved in bringing the goods to PureWaves location. Risk of loss in return shipment will be borne by Customer, and it is recommended that returned goods be insured and/or sent by a method that provides for tracking of the package. Responsibility for loss or damage does not transfer to PureWave until the returned item is received by PureWave. Provided that PureWave determines that the item is actually defective, the repaired or replaced item will be shipped to Customer, at PureWave's expense, (1) not later than thirty (30) days after PureWave receives the defective product or (2) to the terms of a separate written agreement with PureWave. If the allegedly non-conforming Product is not received by PureWave within thirty (30) days of Customer initiating the RMA request, the RMA process for that Product will be deemed cancelled. Customer may also obtain the status of their RMA request(s) by sending an e-mail to support@pwnets.com referencing their assigned RMA Number(s). No product will be accepted for repair or replacement by PureWave without a RMA number. The product must be returned to PureWave, properly packaged to prevent damage, shipping and handling charges prepaid, with the RMA number prominently displayed on the outside of the container. If PureWave determines that a returned product is not defective or is not covered by the terms of the warranty, the Customer will be charged a service charge and return shipping charges. Page 44 Quantum 2200 Installation Guide v2.1 Table 9 summarizes the conditions and charges that PureWave reserves the right to levy. RMA Related Issue Under Warranty Repair and return No charge, PureWave pays Shipment of unit to PureWave Customer pays Regular Shipment to Customer No charge, PureWave pays Expedited shipment to Customer No Fault Found Customer pays the additional cost of the expedited shipping PureWave reserves the right to levy a charge Warranty for repaired and or replaced product Remainder of the original warranty or 90 days Table 9: Summary of PureWave RMA Conditions and Charges Out of Box Failure (OBF) / Dead on Arrival (DOA) In the event a product becomes entirely inoperable within the first forty-eight (48) hours of the initial installation of the product, and such installation takes place within ninety (90) days after the date of shipment from PureWave, the Customer may request that the unit be considered as an Out Box Failure

(OBF) or Dead on Arrival (DOA). PureWave will consider an OBF or DOA as being eligible to be considered for an advance replacement request. The conditions for such a request are as outlined below. Advanced Replacement In some unique situations, PureWave may consider, at its sole discretion on a case-by-case basis, an advance replacement request for a non-conforming Product that is still covered under its warranty period. The following conditions apply to advance replacements:

PureWave has a suitable equivalent replacement unit available. Customers network is experiencing a severe degradation or a complete outage. Customer has complied with the RMA procedures provided herein PureWave reserves the right to levy a charge for the processing and handling of the advance replacement request. To waive this charge will be the sole discretion of the Senior VP of Sales. If expedited shipping is required then Customer pays for all expedited shipping and handling charges that are in excess of the regular shipment charges. To waive this charge will be the sole discretion of the Senior VP of Sales. Page 45

(i)

(ii)

(iii)

(iv)

(v) Quantum 2200 Installation Guide v2.1

(vi) When an advance replacement is provided and Customer fails to return the original product to

(vii) PureWave within fifteen (15) days after shipment of the replacement, PureWave will charge the Customer for the replacement product, at list price. The shipment of advance replacement products is subject to local legal requirements and may not be available in all locations. PureWave will use reasonable commercial efforts to ship advance replacement Products within five (5) business days after PureWaves confirmation that advance replacement is appropriate. PureWave shall not be responsible for shipping delays if any of conditions herein are not met. For products that are out of warranty, the repair of such products will be subject to a repair fee. In addition, any request for the Advance Replacement of product that is out of warranty will be subject to not only the repair fee but additional fees as well. Please contact PureWave for further details. PureWave does offer extended warranties and enhanced service options for its Customers who desire those enhanced features. Please contact PureWave for further information about these options Assistance For assistance, contact your nearest PureWave Networks Sales and Service office. Additional information is available on the PureWave Networks website at http://www.pwnets.com. For Customer Service call: 650-528-5200, or Email: support@pwnets.com. Page 46

Quantum 6600 High performance, all outdoor Mobile WiMAX base stations PureWave Quantum 6600 Installation Guide v2.1 ING-00701-001 Rev D PureWave Quantum 6600 Installation Guide v2.1 PureWave Networks 2010. All rights reserved. PureWave Networks has prepared this manual for use by PureWave Networks personnel, licensees, customers, and customers of customers. The information contained herein is the property of PureWave Networks and shall neither be reproduced in whole nor in art without prior written approval from PureWave Networks. PureWave Networks reserves the right to make changes without notice to the specifications and materials contained herein, and shall not be responsible for any damages caused by reliance on the material presented, including, but not limited to, typographical, arithmetic and listing errors. Page 2 PureWave Quantum 6600 Installation Guide v2.1 Contents Contents ........................................................................................................................................................ 3 Figures ........................................................................................................................................................... 5 Tables ............................................................................................................................................................ 6 Regulatory Notice ......................................................................................................................................... 7 Safety Precautions ........................................................................................................................................ 8 1 Preface .................................................................................................................................................. 9 1.1 1.2 1.3 1.4 1.5 About This Document ................................................................................................................... 9 Symbols used in this Document .................................................................................................... 9 Packaging and Components .......................................................................................................... 9 Locating the Product Serial Number ........................................................................................... 10 Obtaining Documentation and Support ...................................................................................... 10 2 Base Station Basics .............................................................................................................................. 11 2.1 2.2 2.3 Physical and Environmental Specifications ................................................................................. 11 Physical and Environmental Specifications ................................................................................. 12 Connectors and Indicators .......................................................................................................... 13 3 Mounting the Base Station ................................................................................................................. 15 3.1 3.2 Fundamentals ............................................................................................................................. 15 The Pole-Mount Kit ..................................................................................................................... 16 3.2.1 Pole Mount Installation Procedure ..................................................................................... 17 4 Mounting the Antennas ...................................................................................................................... 21 5 Connecting the Antennas to the Base Station .................................................................................... 22 5.1 5.2 Installation of Lightning Surge Protectors .................................................................................. 22 Connecting the Antennas to the Base Station ............................................................................ 24 5.2.1 3x2x2 OmniWave Configuration ......................................................................................... 25 6 Installing the GPS Antenna.................................................................................................................. 26 6.1 6.2 Selecting and Mounting a GPS Antenna ..................................................................................... 26 Connecting the GPS Antenna to the Base Station ...................................................................... 27 7 Connecting Ethernet and Serial Console Cables ................................................................................. 28 Page 3 PureWave Quantum 6600 Installation Guide v2.1 7.1 7.2 The PureWave Basic DC Installation Kit ...................................................................................... 28 Preparing the Ethernet and Console Cables ............................................................................... 29 7.3 Weatherproofing the Ethernet and Console Connections ......................................................... 30 8 Connecting DC Power and Ground ..................................................................................................... 32 8.1 8.2 Base Station Single-Point Grounding .......................................................................................... 32 Preparing the DC Power Connector ............................................................................................ 32 Appendix A Connector Weatherproofing ............................................................................................... 39 Required Materials ................................................................................................................................. 39 General Guidelines for Working with Weatherproofing Tape ................................................................ 39 Weatherproofing Procedures ................................................................................................................. 40 Appendix B Warranty Statements .......................................................................................................... 43 Hardware ................................................................................................................................................ 43 Software .................................................................................................................................................. 43 Additional Conditions.............................................................................................................................. 44 No Fault Found ........................................................................................................................................ 44 Warranty Limitations .............................................................................................................................. 44 Warranty Disclaimer ............................................................................................................................... 44 Obtaining Warranty Service .................................................................................................................... 45 Out of Box Failure (OBF) / Dead on Arrival (DOA) .................................................................................. 46 Advanced Replacement .......................................................................................................................... 46 Assistance................................................................................................................................................ 47 Page 4 PureWave Quantum 6600 Installation Guide v2.1 Figures Figure 1: PureWave Quantum 6600 Base Station .............................................................................. 11 Figure 2: PureWave Quantum 6600 Base Station Mounted on a Tower.............................................. 11 Figure 3: Base Station Connectors ..................................................................................................... 13 Figure 4: Base Station Mounting Holes ............................................................................................. 15 Figure 5: Example of Mounting Point with Spacing Hardware ............................................................ 15 Figure 6: Example Deployment Consisting of Pole Attached to a Metal Frame ................................... 16 Figure 7: Base Station Pole Mount Assembly Diagram ....................................................................... 18 Figure 8: Base Station Mounting Bracket .......................................................................................... 18 Figure 9: Pole Mounting Plates ......................................................................................................... 19 Figure 10: Base Station Mounting Bracket Alignment ........................................................................ 19 Figure 11: Pole Mount Subassembly ................................................................................................. 20 Figure 12: Pole-Mounted PureWave 6-Port Antenna Panel ................................................................ 21 Figure 13: PureWave 6-Port Antenna Panel Connectors .................................................................... 24 Figure 14: PureWave 3x2x2 Configuration ........................................................................................ 25 Figure 15: Optional GPS Antenna and Mounting Kit .......................................................................... 26 Figure 16: T-567B RJ-45 Connector .................................................................................................... 30 Figure 17: RJ-45 IP67 Weatherproof Housing Assembly ..................................................................... 30 Figure 18: Assembled RJ-45 IP67 Weatherproof Housing ................................................................... 31 Figure 19: IP67 DC Power Connector and Pin Assignments ................................................................ 33 Figure 20: Crimp and Insertion Tools for the DC Power Connector ..................................................... 33 Figure 21: Slide connector onto cable before crimping. .................................................................... 34 Figure 22: Wire properly inserted into circular socket crimp contact .................................................. 34 Figure 23: Side and top views of correct crimping technique ............................................................. 35 Figure 24: Properly completed first crimp ......................................................................................... 35 Figure 25: Start the second crimp with tool section A. ................................................................... 36 Figure 26: Complete the second crimp with tool section B. ........................................................... 36 Figure 27: Fully completed pin .......................................................................................................... 36 Figure 28: Pins inserted into DC power connector ............................................................................. 37 Figure 29: Use needle-nose pliers to push the pins further into the plug. .......................................... 37 Figure 30: Use insertion tool to secure the pins in the plug. .............................................................. 38 Figure 31: Front view of plug with crimp pins properly inserted......................................................... 38 Figure 32: Completed Power Connector Assembly ............................................................................ 38 Figure 33: Proper Weatherproof Tape Overlap .................................................................................. 39 Figure 34: Torque Wrench for N-Type Connector .............................................................................. 40 Figure 35: First Plastic Tape Layer ..................................................................................................... 40 Figure 36: First Rubber Tape Layer .................................................................................................... 41 Figure 37: Wrapping Plastic Tape on Top of the Rubber Tape ............................................................ 41 Figure 38: Wrapping Plastic Tape 1 Below Previous Wrap ............................................................ 42 Page 5 PureWave Quantum 6600 Installation Guide v2.1 Tables Table 1: Quantum Environmental and Mechanical Specifications ...................................................... 12 Table 2: Base Station LED Description ............................................................................................... 13 Table 3: Base Station Connector Descriptions ................................................................................... 14 Table 4: PureWave Quantum Base Station Pole Mount Kit Contents .................................................. 17 Table 5: PureWave Quantum Surge Protection Kit Contents .............................................................. 22 Table 6: PureWave Quantum Surge Protection Kit Specifications....................................................... 23 Table 7: PureWave Quantum Basic DC Installation Kit Contents ........................................................ 28 Table 8: Cat 5e+ Connector Pinout .................................................................................................... 29 Table 9: Summary of PureWave RMA Conditions and Charges ........................................................... 46 Page 6 PureWave Quantum 6600 Installation Guide v2.1 Regulatory Notice This device complies with the FCC limits a class B digital device, pursuant to Part 15 of the FCC Rules. A complete list of regulatory certifications can be provided by PureWave upon request. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

Re-orient or relocate the receiving antenna/s. Increase the separation between the equipment and other receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. Shielded cables and I/O cords must be used for this equipment to comply with the relevant FCC regulations. Changes or modifications not expressly approved in writing by PureWave Networks may void the user's authority to operate this equipment. Note: This device must be professionally installed, and the operator and/or the licensed spectrum holder has the responsibility to comply with FCC regulations. Note: The contention protocol MUST be turned on and used for the specified band (3.65GHz

- 3.7 GHz) in the specified country or wherever FCC rules and regulations are enforced. Failure to comply makes the operation of this device illegal. Page 7 PureWave Quantum 6600 Installation Guide v2.1 Safety Precautions When installing this equipment, please observe the following precautions to minimize the risk of danger or personnel injury:

NEVER install equipment if there is a chance of lightning or other adverse weather conditions. NEVER install equipment in a wet location unless the equipment is specifically design for wet locations. NEVER touch un-insultated wires or terminals unless the wire has been disconnected from any equipment. ALWAYS use caution when installing or modifying cables. ALWAYS disconnect all lines and power connections before servicing or disassembling this equipment. ALWAYS assume that all components and assemblies are static sensitive and always follow local ESD-prevention guidelines to prevent equipment damage. For any external power supply that provides the power source for the PureWave equipment, replace any power supply fuse with the same rating or equivalent; otherwise PureWave Networks cannot not be responsible for any subsequent damage to the equipment. For performance and safety reasons, only power supplies listed for use with telephone equipment by a Nationally Recognized Testing Laboratory (NRTL) should be used with equipment. ALL wiring external to the product(s) should follow the provisions of the current edition of the National Electrical Code. These units contain no user serviceable components. Only authorized service personnel should service or repair these units. Use only isolated Class 2 Power Source, Rated 48V dc 5.0A Minimum. Page 8 PureWave Quantum 6600 Installation Guide v2.1 1 Preface 1.1 About This Document This guide is intended for use by a professional installer who performs the physical installation of any PureWave Quantum 6600 Base Station. It does not cover base station functional setup or operation. For detailed information about setup and operation of the PureWave Quantum 6600 Base Station, please refer to the Quantum 6600 Users Guide. Always refer to the current set of Release Notes for the most up to date information and a description of the current features as they relate to the PureWave system. These may be different from the information contained within this Installation Guide. 1.2 Symbols used in this Document Notes, cautions, and timesavers use these conventions and symbols:

Tip Note Caution Warning Means the following will help you solve a problem. The tips information might not be troubleshooting or even an action, but could be useful information. Means reader take note. Notes contain helpful suggestions or references to materials not contained in this manual. Means reader be careful. In this situation, you might do something that could result equipment damage or loss of data. This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. 1.3 Packaging and Components Your PureWave Quantum Base Station and accompanying installation kits and hardware have been packaged into a single box. Some such kits are optional and, if not present, are replaced with empty boxes to ensure safe and secure shipping. All are listed below:

PureWave Quantum Base Station PureWave Quantum Basic DC Installation Kit PureWave Quantum Pole Mounting Kit PureWave Quantum Surge Protection Kit GPS Antenna Kit Page 9 PureWave Quantum 6600 Installation Guide v2.1 If you have purchased a 6-Port Antenna Panel or other antenna(s) from PureWave then it is packaged in a separate box along with its mounting kit and instructions. Please refer to the instructions provided with your antenna(s) for proper mounting procedures. Connection of the antennas to the base station is covered within this guide. 1.4 Locating the Product Serial Number The product identification information, serial number, and certification information are located on a label on the side panel of the base station. Please take note of and keep this information for your records, as it is very important for warranty and support services. 1.5 Obtaining Documentation and Support All requests for documentation and/or support should be addressed to Technical Support Department PureWave Networks, Inc. 2660-C Marine Way Mountain View, CA 94043 E-mail: support@pwnets.com Tel: 650-528-5200 Fax: 650-528-5222 Page 10 PureWave Quantum 6600 Installation Guide v2.1 2 Base Station Basics 2.1 Physical and Environmental Specifications The PureWave Quantum 6600 Base Station (Figure 1) is made up of a single, weather-resistant enclosure with overall dimensions 17.5 x 16.7 x 5.3 (44cm x 42cm x 13cm). The base station is a single self-

contained unit and has no user-serviceable components. Figure 1: PureWave Quantum 6600 Base Station The PureWave Quantum Base Station can be installed indoors or outdoors, however the antennas must always be installed outdoors. Figure 2 shows a PureWave Quantum 6600 base station co-located on a tower with a PureWave 6-Port Antenna Panel. Figure 2: PureWave Quantum 6600 Base Station Mounted on a Tower Page 11 PureWave Quantum 6600 Installation Guide v2.1 2.2 Physical and Environmental Specifications Table 1 lists the mechanical, electrical, and environmental properties of the PureWave Quantum Base Station. Physical & Environmental Specifications Dimensions Weight Power Temperature Humidity Altitude 17.5 x 16.7 x 5.3

(44cm x 42cm x 13cm) 32lbs (14.5kg) (does not include mounting hardware)

-48 VDC 150 Watts Max

-40C to +55C (ETSI EN 300 019-1.4 Class 4.1E) Note: An available solar shield is required for ambient temperatures exceeding +45C with full sun exposure. 5-100% non-condensing To 10,000 ft above sea level Surge Protection UL497B Lightning Protection Min 10kA IEC 6100-4-5 (optional via external kit) Weatherproofing IEC IP67 Wind Loading 160Km/hr operation, 200Km/hr survival Safety and IEC IP EN 300 019-2-2, GR487, IEC 60529 Vibration and Dust ETSI EN 300 019-1-4 Class 4.1E Table 1: Quantum Environmental and Mechanical Specifications Page 12 PureWave Quantum 6600 Installation Guide v2.1 2.3 Connectors and Indicators Figure 3 shows the bottom panel of the base station, where all the connectors and indicators are located. Figure 3: Base Station Connectors The base station connector panel contains 3 high-intensity LEDs that are intended to be viewable from the ground for quick confirmation of the operational state of the base station. Table 2 describes the function of each LED. LED STATUS LINK Function Green - BS is up and running normally. No faults detected. Blinking Red System booting up, or system is temporarily down. Solid Red - Fault detected. Off LEDs disabled or Power is off. Fault detected if POWER LED is Green, but STATUS LED is Off. Solid Green Connected to an Ethernet switch. Blinking Green Ethernet packet activity. Off LEDs disabled or no Ethernet activity detected. POWER Green Power is being supplied to the BS. Off LEDs disabled or no power is being supplied to the BS. Table 2: Base Station LED Description Page 13 PureWave Quantum 6600 Installation Guide v2.1 The function of each base station connector/port is described in Table 3. Note that every present connector must be terminated according to the instructions in this guide to ensure proper base station operation. Connector POWER GND GPS ETH-1 ETH-2 CONSOLE ANT 1-6 Function

-48VDC power source inputs for the unit. DC power connector: Fits Tyco P/N 796095-2 connector. This M5 screw provides a ground connection point to the base station. It is the installers responsibility to ensure that the unit is professionally grounded and complies with all relevant local codes. N-type connector for mandatory external GPS antenna. 3.3V power on center pin. This Gigabit Ethernet port serves as the data traffic backhaul Interface and also provides for in-

band management of the base station. Note that this port may be physically routed directly to the operators network equipment, or it may be daisy-chained through additional PureWave Quantum sectors by routing it to another units ETH-2 port. Cat-5 (RJ-45), Single-Mode Fiber (HartingPull/Han 3 A), and Multi-Mode (LC duplex) Fiber options are available for the ETH-1 port. This Gigabit Ethernet port serves as an incoming daisy-chain port from a neighboring sector, and may be used for out-of-band management of the base station. It may also be used to connect to an external device, such as a web camera. Daisy-chained traffic is aggregated and passed through the ETH-1 port. Cat-5 (RJ-45), Single-Mode Fiber (HartingPull/Han 3 A), and Multi-Mode (LC duplex) Fiber options are available for the ETH-2 port. RJ-45 based RS-232 port for CLI control via a console. Defaults settings are 38400, 8, None, 1, Xon/Xoff.Xoff N-type Tx / Rx Antenna Ports. Table 3: Base Station Connector Descriptions Page 14 PureWave Quantum 6600 Installation Guide v2.1 3 Mounting the Base Station 3.1 Fundamentals The back side of the base station includes 6 metric M8-1.25 threaded mounting holes, as shown in Figure 4. Figure 4: Base Station Mounting Holes Because the mounting holes are recessed, provisions must be made to provide for spacing between the mounting points and the mounting bracket or surface, as exemplified in Figure 5. Figure 5: Example of Mounting Point with Spacing Hardware It is imperative that proper airflow be maintained on all sides of the base station and that all heat sinks remain unobstructed. In the case of wall or surface mounting a minimum of 2 of space should be maintained between the base station and mounting surface. Page 15 PureWave Quantum 6600 Installation Guide v2.1 3.2 The Pole-Mount Kit The optional PureWave Quantum Base Station Pole Mounting Kit provides all hardware required for installing the base station on a pole ranging from 2.5-5 inches in diameter. It is important to note that the use of a pole mount in no way dictates that the base must actually be deployed on top of a long pole, although in many cases it will in fact be. Alternatively the base station may be conveniently attached to a short pole, which may then be easily mounted to a metal frame or struts that conform to the specific deployment using commonly available hardware. An example of this is shown in Figure 6. Figure 6: Example Deployment Consisting of Pole Attached to a Metal Frame The PureWave Quantum Base Station Pole Mount Kit has been specifically designed to handle the weight of the base station. However, it is critical that the full weight of the base station plus mounting hardware be considered in designing the overall base station mounting solution. Fully assembled, the PureWave Quantum Base Station Pole Mount Kit weighs 16lbs (7.3kg). Page 16 PureWave Quantum 6600 Installation Guide v2.1 If you have ordered the pole mounting kit then it was shipped in the same box as the base station. Please locate the kit and compare its contents to Table 4. Item Quantity Purpose a) Front Pole Mount Plate b) Back Pole Mount Plate c) Base Station Mounting Bracket 1 1 1 d) Carriage Bolt SAE 3/8-16 Up to 12 e) Nylon Pushnut, 3/8 f) Nylon Tie Wrap g) Hex Nut, SAE 3/8-16 h) Split Lock Washer, SAE 38 i) Hex Bolt, Metric M8 -1.25 X 16 j) Hex Bolt, Metric M8 -1.25 X 25 4 2 4 4 6 4 Grips pole along with back pole mount plate (b). The base station mounting bracket also connects to this piece. Grips pole along with front pole mount plate (a). Attaches to base station mounting holes, as well as to front pole mount plate (a). A built-in handle facilitates carrying the base station when attached. Selection of carriage bolts ranging from 6 to 10, fully or partially threaded. Select a set of 4 that are appropriate to the installation, and use with push nut (e), hex nut (g), and washer

(h) to fasten front (a) and back (b) mounting plates to pole. Slide onto carriage bolt (d) to prevent it from slipping out of front mounting plate (a) while fastening hex nut (g) and washer

(h). Use to temporarily affix mounting hardware to pole during the installation process. Use with carriage bolts (d) and split lock washers (h) as described. Use with carriage bolts (d) and hex nuts(g) as described. Use with M8 split lock washers (k) to fasten base station mounting bracket (c) to base station. Use with M8 split lock washers (k) to fasten base station mounting bracket (c) to front pole mount plate (a). k) Split Lock Washer, Metric M8 10 Use with M8 bolts (i, j) as described. Table 4: PureWave Quantum Base Station Pole Mount Kit Contents 3.2.1 Pole Mount Installation Procedure Figure 7 illustrates how the entire pole-mounting mechanism connects together and to the base station. The pole mount mechanism consists of a base station bracket (Figure 8) that attaches to the mounting points on the back of the base station, and a pair of pole-mount plates (Figure 9) that grip the pole and to which the base station bracket attaches. Table 4 indicates where each included piece of hardware is to be used and should be strictly followed to ensure a secure and proper installation. Page 17 PureWave Quantum 6600 Installation Guide v2.1 Figure 7: Base Station Pole Mount Assembly Diagram Figure 8: Base Station Mounting Bracket Page 18 PureWave Quantum 6600 Installation Guide v2.1 Figure 9: Pole Mounting Plates First mount the Base Station Mounting Bracket (Figure 8: Base Station Mounting Bracket) to the base station using the provided hardware, as indicated in Table 4. When installing the base station mounting bracket onto the base station, be sure to align it as shown in Figure 10. Note that the bracket is designed for upright mounting of the base station; that is, mounting with the connectors facing down. Tighten the bolts to a torque of 30 in-lbs. Figure 10: Base Station Mounting Bracket Alignment The base station bracket may be mounted to the base station ahead of time as it has a built-

in handle that facilitates its transportation and carrying the base station up a tower. To improve the effectiveness of connector waterproofing and to optimize the base stations thermal performance, it is recommended that the base station be mounted in an upright position, with the connectors at the bottom. Note that the base station bracket is designed specifically to attach to the 6 recessed mounting holes on the base station, and hence can be useful in a variety of mounting scenarios. However, use of this bracket without the pole mounting plates designed specifically to accompany it is at the sole discretion and responsibility of the customer. Page 19 FrontMountingPlateRearMountingPlate PureWave Quantum 6600 Installation Guide v2.1 The next step is to mount the front and back pole mount plates (Figure 9) to the pole, using the provided hardware as indicated in Table 4. Nylon tie wraps have been provided for convenience to temporarily affix the front mounting plate to the pole during the installation process. A selection of carriage bolts has been provided to accommodate a variety of pole diameters. Select a set of 4 bolts that enable a secure fit to your pole. Insert each carriage bolt through the front mounting plate and slide a pushnut onto it to temporarily hold it in place. Slide the back mounting plate onto the carriage bolts, sandwiching the pole in-between, then add lock washers and hex nuts tightened to a torque of 30 in-lbs. Insert the four provided M8-1.25x25 hex bolts along with M8 split lock washers into the side holes of the front pole mounting plate and leave them loose for now. These bolts provide the attachment point for the base station mounting bracket to the pole mount subassembly. The completed subassembly is shown in Figure 11. Figure 11: Pole Mount Subassembly Finally, using the handle on the base station mounting bracket, lift the base station subassembly onto the pole mount subassembly and hang it on the four side mounting bolts. Torque the bolts to 30 in-lbs. For this and other installations in this manual, a suitable anti-corrosion lubricant should be applied to all exposed metal surfaces. For your convenience a tube of Bostik NEVER-SEEZ has been provided in the PureWave Quantum Base Station Basic Installation Kit. Note that these types of lubricants tend to be messy and sticky to apply due to the nature of their intended application. Always read the labels or instructions provided and take necessary pre-cautions during application. Page 20 PureWave Quantum 6600 Installation Guide v2.1 4 Mounting the Antennas PureWave Quantum Base Stations can be deployed with virtually any type of antennas that operate in the relevant frequency band and that meet regional regulatory standards. Because the PureWave Quantum 6600 base station supports six antennas, the easiest and most cost-effective solution is to use a PureWave 6-Port Antenna Panel in the appropriate frequency band. By combining six cross-polarized antennas in a single compact radome it reduces deployment real-estate and greatly simplifies installation effort since only a single mount is required. Antenna mounting procedures will vary by model and manufacturer, so we refer the installer to the instructions that came with the antenna(s) and/or antenna mount(s) for their secure and proper installation. The PureWave 6-Port Antenna Panel is shipped with a pole-mount kit and installation instructions. Note that if you purchased a PureWave 6-Port Antenna Panel then the Antenna and Mounting kit were shipped in a separate box from the base station. A pole-mounted PureWave 6-Port Antenna Panel is illustrated in Figure 12. Figure 12: Pole-Mounted PureWave 6-Port Antenna Panel As a general rule the antennas should be installed as close as practical to the base station. This minimizes signal loss which is directly proportional to cable length. In addition, a high-quality, low-loss coaxial cable capable of propagating the relevant frequencies (such as Hyperlink Technologies P/N CA3N100 or Times Microwave LMR 400) should be utilized between the antenna and base station. In the event that the base station cannot be co-located with the antennas the choice of cable is even more important, as signal losses can be significant. For example, LMR 400 cable has an attenuation loss of 6.8dB per 100ft at a frequency of 2.5GHz. It is important that cable loss be computed and understood to ensure that adequate range will still be achieved for your deployment needs. Page 21 PureWave Quantum 6600 Installation Guide v2.1 5 Connecting the Antennas to the Base Station 5.1 Installation of Lightning Surge Protectors In most environments it is essential for the base station to be installed with external protection against surges caused by lightning on the antenna cables. PureWave therefore recommends that suitable surge protectors be installed on each base station antenna connector. For an indoor installation of the Base Station, surge protection devices should be installed at the entrance to the building that houses the Base Station. For an outdoor installation they are installed on the relevant connectors. The optional PureWave Quantum Surge Protection Kit has been developed for your convenience and provides hardware designed to protect the base station from surges on its antenna connectors. PureWave strongly recommends the use of this kit. It is important to note, however, that every environment and installation is different. Therefore, it is the responsibility of the customer and the installer to ensure that sufficient protection is employed, whether or not this kit is utilized. If you have ordered the PureWave Quantum Surge Protection Kit then it was shipped in the same box as the base station. Please locate the kit and compare its contents to Table 5. Item Quantity Purpose

(a) Connector Weather Proofing Kit

(b) Connector, Insulated Crimp Ring Terminal, Lug, AGW 10-12, #10

(c) Surge Arrestor, RF, N-Type M/F

(d) Lubricant, NEVERSEEZ Regular Grade 1OZ

(e) Flat Washer, Metric, M5

(f) External Tooth Lock Washer, Metric, M5

(g) Hex Nut, Metric, M5-.8

(h) Quantum BS Grounding Bar

(h) DC Surge Protection 1 2 6 1 2 2 2 1 1 Contains tape and butyl rubber for weatherproofing the antenna connectors and surge arrestors (c). Used to create ground connections between Quantum BS Grounding Bar (h) and ground terminal on BS. Attaches to a base station antenna connector on one side, and an antenna cable on the other side. Each subassembly also includes mounting hardware for grounding bar (h). Anti-corrosion / anti-seize lubricant for use on exposed metal surfaces. Use with tooth lock washer (g) and hex nut(g) to fasten crimp rings (b) to ground bar (h). Use with flat washer (e) and hex nut(g) to fasten crimp rings

(b) to ground bar (h). Use with washers (e, f) to fasten crimp rings (b) to ground bar (h). Connects to surge protectors (c) and crimp rings (b). Quantum Base Station DC Power Supply Surge Protection. Table 5: PureWave Quantum Surge Protection Kit Contents Page 22 PureWave Quantum 6600 Installation Guide v2.1 Specifications for the PureWave Quantum Surge Protection Kit are summarized in Table 6. Surge Protector Feature Specifications Surge Capabilities IEC 1000-4-5, 8/20s @ 10kA Frequency Range Return Loss Insertion Loss RF Power Limit 2-6GHz

> 20dB 0.2dB 10 Watts Max Temperature

-40oC to +85oC Relative Humidity 0-100% condensing Surge Throughput Energy 0.5J (6kV/3kA 8/20s) Peak Let-Through Voltage 3V (6kV/3kA 8/20s) Table 6: PureWave Quantum Surge Protection Kit Specifications The following surge protector installation procedure is specific to the PureWave Quantum Surge Protection Kit. If you have chosen to use alternative surge protection hardware then please follow the instructions received with that hardware to ensure proper installation. However, we still recommend that you review the procedure below, as much of it will still be relevant. Step 1:

Screw one surge arrestor onto each base station antenna connector ANT-1 through ANT-6 and tighten to a torque of 12-15 in-lbs. Step 2: Weatherproof each surge arrestor connection to the base station before proceeding with the Step 3:

next step. Please refer to Appendix A for a general discussion and guidelines on weatherproofing connections. Place the grounding bar over the row of surge arrestors such that the two ground terminal screws are facing the bottom of the base station, and secure in place with the lock washers and nuts that came packaged with each surge protector. Tighten each nut to a torque of 30 in-lbs. Step 4: Wire ground connections from the ground bar terminals to the base station connector panel grounding terminal using the provided crimp rings and hardware. Base station grounding procedures are covered in Appendix A. Page 23 PureWave Quantum 6600 Installation Guide v2.1 5.2 Connecting the Antennas to the Base Station The base station has six N-type antenna connectors that must be attached to each installed antenna using high-quality coaxial cable, as discussed in Section 4. The number of connectors/adapters used should also be minimized as they are especially lossy. Most industrial-grade antennas, including all PureWave antennas, utilize N-type connectors. Regardless of the antenna-side connector type, it is important to obtain or construct cables with the correct respective terminal types and of the correct length to avoid the need for additional connectors or adaptors. Figure 13 shows the N-type connectors on the back of the PureWave 6-Port Antenna Panel. The arrows represent the relative polarization of each antenna. Note that each adjacent connector corresponds to alternating +45 or -45 degree polarized antennas. If alternative cross-polarized antennas are utilized then it is recommended that they be arranged and labeled in an analogous manner. If vertically polarized antennas are used then it is still recommended that they be linearly labeled consecutively (i.e., ANT-1 next to ANT-2 next to ANT-3, etc). Figure 13: PureWave 6-Port Antenna Panel Connectors Prepare and run 6 low loss coax cables from the base station to the antenna. Starting at base station ANT-1 and continuing to ANT-6, connect each base station (or surge arrestor) connector to the corresponding port number on the installed antennas. All antenna ports must be connected. Finally, weatherproof every connector. Please refer to Appendix A for a general discussion and guidelines on weatherproofing connections. Thorough weatherproofing of all connections is extremely important to ensure long-term base station operation as well as validation of the warranty. Page 24 PureWave Quantum 6600 Installation Guide v2.1 5.2.1 3x2x2 OmniWave Configuration The base station allows for a configuration supporting a 3 sectors deployment and therefore allows for a flexible coverage area. Figure 14 shows the configuration steps described below:

Determine the optimal antenna placement configuration to support coverage and capacity requirements for your deployment Connect Cables from Ant-1 and Ant-2 to Antenna Panel A (Ports 1 and 2) Connect Cables from Ant-3 and Ant-4 to Antenna Panel B (Ports 1 and 2) Connect Cables from Ant-5 and Ant-6 to Antenna Panel C (Ports 1 and 2) Step 1:

Step 2:

Step 3:

Step 4:

Figure 14: PureWave 3x2x2 Configuration Page 25 PureWave Quantum 6600 Installation Guide v2.1 6 Installing the GPS Antenna WiMAX base stations utilize GPS (the Global Positioning System) to maintain tight synchronization and coordination among themselves in a network. This assures that all base stations in the network transmit and receive in harmony, as they must all utilize the same Downlink / Uplink Ratio. 6.1 Selecting and Mounting a GPS Antenna PureWave Quantum Base Stations incorporate an integrated GPS receiver which must be connected to an external GPS antenna view of a number of GPS satellites. Installation location flexibility and the amount of tolerable obstruction are heavily dependent upon the quality and capabilities of the chosen antenna. The choice of GPS antenna is an important one, as there are many models available in the market for many purposes, and hence some are very inexpensive but also low gain and/or low quality. A poor GPS antenna can easily become the point of failure of your system. PureWave strongly recommends the use of a high-quality GPS antenna and therefore offers an optional GPS Antenna Kit, featuring a GPS antenna with integrated 40dB low-noise amplifier and mount kit

(Figure 15). Figure 15: Optional GPS Antenna and Mounting Kit If you have ordered the GPS Antenna Kit it was shipped in the same box as the base station. The optional GPS Antenna Kit it includes all required mounting hardware and instructions and we refer the installer to that documentation for secure and proper installation. Similarly, if an alternative GPS antenna has been chosen, please refer to the instructions provided by the manufacturer for proper mounting procedures. Page 26 PureWave Quantum 6600 Installation Guide v2.1 6.2 Connecting the GPS Antenna to the Base Station The base station utilizes an N-type GPS antenna connector. The GPS antenna that comes as part of the optional GPS Antenna Kit also has an N-type connector. Prepare a high-quality coaxial cable of the appropriate length and with the appropriate connector types for use in connecting the GPS antenna to the base station. Connect the coaxial cable from the external GPS antenna to the N-type female connector marked GPS on the base station, and weatherproof the connectors. Please refer to Appendix A for a general discussion and guidelines on weatherproofing connections. Page 27 PureWave Quantum 6600 Installation Guide v2.1 7 Connecting Ethernet and Serial Console Cables 7.1 The PureWave Basic DC Installation Kit Each PureWave Quantum Base Station is shipped with the PureWave Quantum Basic DC Installation Kit, which contains hardware and components required for connecting and waterproofing the ethernet ports, console port, the power port, and the grounding terminal. This kit has been shipped in the same box as the base station. Please locate it and compare its contents to Table 7. Item Quantity Purpose a) 6 Cat 5e Cable b) DB9 Female to DB9 Female Serial Cable c) Network DB9 Female to RJ45 Adaptor d) DC Connector 4 Pin Female Plug e) 14-18 AWG Circular Socket Crimp Contact f) Cable Clamp Connector g) RJ45 IP67 Weatherproof Housing h) Insulated Crimp Ring Terminal i) NEVER-SEEZ Lubricant, 1oz tube j) Weatherproofing Kit k) RJ45 Plug Shielded Connector l) Washer, Metric M5 Flat m) Washer/Metric, M5 External Tooth Lock n) Hex Nut Metric, M5-.8 o) Extra Hardware Kit 1 1 1 1 4 1 3 1 1 1 6 1 1 1 1 Connects base-station serial/console port connector to DB9 to RJ45 adaptor (c) Connects serial consol/terminal to DB9 to RJ45 adaptor (c) Couples cables for serial console connection (a, b) Part of DC power connector subassembly (d, e, f) Part of DC power connector subassembly (d, e, f) Part of DC power connector subassembly (d, e, f) Weatherproof housing subassemblies for ETH-1, ETH-2, and Console Connectors Attaches to base station ground terminal using provided hardware (l, m, n) Anti-corrosive lubricant For all connectors. Recommended weatherproofing procedures are provided in this document. Provided for use in creating custom-length CAT-5 cables for ETH1, ETH2, and Console connections. Part of crimp ring subassembly (h, l, m, n) Part of crimp ring subassembly (h, l, m, n) Part of crimp ring subassembly (h, l, m, n) A variety of extra parts for convenience Table 7: PureWave Quantum Basic DC Installation Kit Contents Page 28 PureWave Quantum 6600 Installation Guide v2.1 7.2 Preparing the Ethernet and Console Cables ETH-1 and ETH-2 connectors should both be run from the base station to the operators network equipment. The CONSOLE connection may be connected for initial provisioning and thereafter on an as-

needed basis or it may be permanently connected as with the Ethernet connections. Please take into consideration that the RS-232 console connection is less tolerant to noise and interference in long cable runs than the Ethernet interfaces. The maximum length of the Cat-5e cables connecting the ethernet or console ports on the base station to the Service Providers network equipment is limited to 100m (328ft). When the Base Station is mounted outdoors it is important to use outdoor rated Category-

5e+ Gigabit Ethernet Cable, such as Commscope Ultra IITM, and shielded outdoor rated metal RJ-45 connectors. Six high-quality shielded connectors have been included in the PureWave Quantum Basic Installation Kit. Prepare and connect two Cat 5e+ cables from the ETH-1 and ETH-2 ports to the operators network equipment, and one more for the CONSOLE port if desired. In preparing the Cat 5e+ cables, terminate each at the base station in accordance with the T-568B wiring standard, as described in Table 8 and illustrated in Figure 16. Pair Number Wire Color Pin Number 1 2 3 4 white / blue Blue white / orange Orange white / green green white brown brown 5 4 1 2 3 6 7 8 Table 8: Cat 5e+ Connector Pinout Page 29 PureWave Quantum 6600 Installation Guide v2.1 Figure 16: T-567B RJ-45 Connector 7.3 Weatherproofing the Ethernet and Console Connections If the CONSOLE port is not to be permanently connected then it should remain tightly capped for the time-being. A serial cable, a 6 Cat-5 cable, and a DB9 to RJ-45 adapter has been supplied with the PureWave Quantum Basic DC Installation Kit for bring-up and provisioning purposes utilizing the CONSOLE port. Please refer to the PureWave Quantum User Manual for additional information. A set of three RJ-45 IP67 weatherproof housing assemblies have been supplied as part of the PureWave Quantum Basic DC Installation Kit for the purpose of weatherproofing the ethernet and console connectors. The procedure for installation of the housing onto each cable and connector is provided below. Note that at least one end of the cable should be crimped with a RJ-45 connector only at the end of the procedure. Please refer to Figure 17 during the following procedure, as it shows the interconnection and orientation of each part in the assembly. Figure 17: RJ-45 IP67 Weatherproof Housing Assembly Page 30 PureWave Quantum 6600 Installation Guide v2.1 Slip the Sealing Nut onto the RJ-45 cable. Place the screw nut onto the housing with the threads facing forward Insert the seal into the housing Insert the cable through the seal and housing exiting the front of the housing Strip cable sheath Crimp the RJ 45 plug onto the cable Pull the cable back so the plug fits into the housing. Secure the sealing nut in place Stick the gasket onto the front end of the housing Step 1:

Step 2:

Step 3:

Step 4:

Step 5:

Step 6:

Step 7:

Step 8:

Step 9:

The fully assembled connector is shown in Figure 18 and can now be attached to each base station RJ-45 connector thus creating a weather protected connection. Additional weatherproof wrapping, as described in Appendix A is still, however, recommended. Figure 18: Assembled RJ-45 IP67 Weatherproof Housing Page 31 PureWave Quantum 6600 Installation Guide v2.1 8 Connecting DC Power and Ground 8.1 Base Station Single-Point Grounding Extensive analysis and investigation of installations has led to the belief that the root cause at the heart of the majority of power-related failures is likely to be the presence of multi-point grounding of equipment. Single point grounding eliminates ground voltage differentials and thus dramatically increases equipment survivability during surges. Single point grounding requires that the grounding leads from antennas, base station, and surge protection devices for a particular sector are bonded together at the same point on the tower or in the shelter, in the case of an indoor installation. It is not necessary to bond all sectors together. An insulated crimp ring has been supplied as part of the PureWave Quantum Basic DC Installation Kit

(Table 7), along with the hardware required to mount it to the base station GND terminal connection. Furthermore, if the optional PureWave Quantum Surge Protection Kit (Table 5) has been installed then it includes a set of crimp rings for mounting on the ground terminals of the supplied grounding bar. Conductors from each installed crimp ring should be connected together, and then tied to a single-point common grounding point. The following grounding guidelines apply, whether or not the PureWave Quantum Surge Protection Kit has been installed:

Surge protection devices generally connect to ground by using a ground wire. Cut any extra ground wire length when finished connecting it to the single point earth ground. Never loop or coil up the ground wire, and avoid sharp bends. Always connect it straight to ground. A good earth ground impedance is less than 1.0 ohm. Measure ground impedance at the point where the protector ground wire is connected and not at the ground rod. Connect the protector ground wire and equipment ground (both power ground and telecomm. ground) to a single common ground. Make sure all connections are fastened securely. 8.2 Preparing the DC Power Connector The DC power source to a PureWave Quantum Base Station must be capable of delivering up to 10 Amps of current at -48 VDC. The base station requires ~6 Amps max at -48VDC (range -40VDC to -

57VDC, -38VDC min). The power connector used on the base station will accommodate 14 to 18 gauge wire. Remember to take account of the voltage drop when running long power cable runs. For example, for 18 AWG and a cable length of 100 feet, a nominal 48VDC supply delivering into a 6A load will have a voltage drop of 9.3 volts. Page 32 PureWave Quantum 6600 Installation Guide v2.1 This DC power connector assembly has been provided as part of the Basic DC Installation Kit (Table 7) and consists of a 4-pin female power connector plug, a set of crimp contacts, and a cable clamp. The connector with pin assignments is shown in (Figure 19). Figure 19: IP67 DC Power Connector and Pin Assignments To successfully complete the power cable assembly you will need the following tools (not provided). Wire-strippers Needle-nose pliers Phillips Screwdriver Crimping tool The Tyco 91519-1 Crimp Tool was specifically designed for the pins of the Quantum power connector. However, due to its high cost we have focused on a procedure for creating the connector with the much more affordable Waldom W-HT1921 Crimp Tool and plus the Tyco / AMP 200893-2 Insertion Tool. All are shown in Figure 20. If you choose to use the optional Tyco crimp tool then please follow the instructions included with the tool for the proper crimping procedure. Figure 20: Crimp and Insertion Tools for the DC Power Connector Page 33 PureWave Quantum 6600 Installation Guide v2.1 Step 1: Use wire strippers to remove about 1/4 inch of insulation from each wire and approximately 1 of outer cable insulation. It is important that each wire be the same length, with equal lengths of stripped wire. Step 2:

Slide the circular socket connector over the power cable as shown in Figure 21. Figure 21: Slide connector onto cable before crimping. Step 3:

Place stripped wire into circular socket crimp contact such that insulated wire is present at the first crimp location and bare wire is present at the second crimp location (Figure 22). Figure 22: Wire properly inserted into circular socket crimp contact Using the Walcom crimping tool in crimp head location B, squeeze carefully, assuring that the first crimp location is forming properly before wielding full pressure. Give it a slight tug to ensure that it is secure and that the wire is tightly crimped into place. The pin connector crimp locations are U-shaped and must be placed in the crimper such that the open end of the U-shape points toward the A/B locations. When forming the U-shaped crimp it is important to ensure the crimp folds back on itself, creating a heart-shape. Please refer to Figure 23 and Figure 24. Page 34 Step 4:

PureWave Quantum 6600 Installation Guide v2.1 Figure 23: Side and top views of correct crimping technique Figure 24: Properly completed first crimp Step 5:

Crimp the cable again at the second crimp location by starting with the A side of the crimping tool (Figure 25). Release crimping pressure when the second crimp location begins to curl. Next place the second crimp location in section B of the tool (Figure 26) and securely complete the crimp. Page 35 PureWave Quantum 6600 Installation Guide v2.1 Figure 25: Start the second crimp with tool section A. Figure 26: Complete the second crimp with tool section B. The fully completed pin is shown in Figure 27. Now repeat Steps 3-5 for each of the three additional pins. Figure 27: Fully completed pin Page 36 Step 6:

Step 7:

Step 8:

PureWave Quantum 6600 Installation Guide v2.1 Using your fingers, insert the crimped pins into the corresponding holes of the DC power connector plug (Figure 28). Be sure to match the pin-out as specified earlier. Figure 28: Pins inserted into DC power connector Next use needle nose pliers to insert the pins further by grabbing the first crimp location and pushing all the way into the connector body. It helps if you place the connector face down on a table to provide extra leverage. It is critical that the pins are pushed as far into the connector body as possible. See Figure 29. Figure 29: Use needle-nose pliers to push the pins further into the plug. Now use the insertion tool to secure the pins inside the connector plug (Figure 30). An audible click should be heard when the pin is fully inserted into the connector body. Properly inserted pins will be visible from the front of the connected as shown in (Figure 31). Note: It is possible to over-insert the pin when using the pin insertion tool, so take care to gently insert the ping into the connector body. Page 37 PureWave Quantum 6600 Installation Guide v2.1 Figure 30: Use insertion tool to secure the pins in the plug. Figure 31: Front view of plug with crimp pins properly inserted Step 9:

Complete the assembly by screwing the plug into the circular socket connector and secure with the cable clamp by tightening the two strain-relief screws using a Phillips screwdriver. The completed assembly is shown in Figure 32. Figure 32: Completed Power Connector Assembly Note that the base station does not have a power switch and will immediately power up if the DC power connector is in place and power is applied. Please do not apply power to the base station until all connections are made in accordance with the instructions in this guide. Then, please refer to the PureWave Quantum Base Station User Guide for additional instructions. Page 38 PureWave Quantum 6600 Installation Guide v2.1 Appendix A Connector Weatherproofing Required Materials PureWave recommends that appropriate weather protection sealing be applied to all outdoor installed elements of the system. Weatherproofing tape kits can very effectively seal the junction between mating connectors. Proper and diligent weatherproofing not only protects the connection from water damage, but also prevents vibrations from loosening the interface. A wide range of weather protection materials and kits are commercially available. The PureWave Quantum Basic DC Installation Kit and the Optional PureWave Quantum Surge Protection Kit each include a weatherproofing kit that contains a variety of tapes along with general weatherproofing guidelines. General Guidelines for Working with Weatherproofing Tape When applied, the tape must be above 32F (0C) to ensure adhesion. Do not stretch the tape. Apply only enough tension to provide a smooth wrap. Smooth each wrapped layer with your hands to ensure full adhesion. Do not pull the tape to tear it - always cut it. Pulled tape eventually unravels, decreasing protection. Add extra final layers of tape in warmer climates where there will be long exposure to damaging ultra violet (UV) rays. Two or three extra layers of tape will provide additional UV protection. On vertical runs, the last wrap of 3/4 tape should be wrapped from the bottom to the top. This provides a shingle effect. When wrapping tape, overlap the tape to half-width as shown in Figure 33. Figure 33: Proper Weatherproof Tape Overlap Page 39 PureWave Quantum 6600 Installation Guide v2.1 Weatherproofing Procedures The following procedure is illustrated for an N-type antenna connector (without surge connector) but applies to all connector types. Step 1:

Tighten the connection with a torque wrench to the proper torque value (12-15lbs for an N-

type connector) to ensure that correct internal seals and surface contacts are made. One recommended torque wrench for an N-Type connector is the Andre 244379 and is shown in Figure 34. Figure 34: Torque Wrench for N-Type Connector Step 2: Wrap the connection with a layer of 3/4 (19-mm) plastic tape, starting at 1 (25 mm) from the connector. Overlap the tape to half-width as illustrated in Figure 33 and extend the wrapping over the entire connector. Avoid making creases or wrinkles. Smooth the tape edges. See Figure 35. Figure 35: First Plastic Tape Layer Cut a 5 (125-mm) length of rubber tape. Expand the width of the tape by stretching it such that it will wrap completely around the connector and cable. Press the tape edges together so that there are no gaps. Press the tape against the connector and cable. The tape should extend 1 (25 mm) beyond the plastic tape on the cable (Figure 36). Page 40 Step 3:

PureWave Quantum 6600 Installation Guide v2.1 Figure 36: First Rubber Tape Layer Step 4:

Start wrapping a layer of 2 (50-mm) plastic tape 1 (25 mm) below the rubber tape, overlapping at half width (Figure 37). Finish the wrap at the flange of the antenna connector and cut the tape. Figure 37: Wrapping Plastic Tape on Top of the Rubber Tape Start wrapping three layers of 3/4 (19-mm) plastic tape, 1 (25 mm) below the previous 2

(50-mm) wrap, overlapping at half width (Figure 38) until the entire connector is wrapped. The tape should be applied in one strip if possible. A strip can be coiled onto an applicator such as a pencil. Apply only enough tension to get good adhesion and keep the tape smooth. Page 41 Step 5:

PureWave Quantum 6600 Installation Guide v2.1 Figure 38: Wrapping Plastic Tape 1 Below Previous Wrap Step 6:

Inspect your weatherproofing job for quality. Any exposed areas will quickly become problematic. Repeat for all remaining connectors. Page 42 PureWave Quantum 6600 Installation Guide v2.1 Appendix B Warranty Statements Hardware PureWave, Inc (PureWave or the Company) warrants to the end-user (Customer) that this hardware product will conform in all material respects to the specifications provided with the hardware and will be free from defects in workmanship and materials, under normal use and service, for a period of 365 days from the date of original shipment by PureWave. PureWave's sole obligation under this limited warranty shall be, at PureWave's option, to repair the defective product or part, deliver to Customer an equivalent product or part to replace the defective item, or if neither of the two foregoing options is reasonably possible, refund to Customer the purchase price paid for the defective product. All products that are replaced will become the property of PureWave. Replacement products may be new or reconditioned. PureWave's obligations hereunder are conditioned upon the returned of affected articles in accordance with PureWave's Return Material Authorization (RMA) procedures. Subject to the limitations and conditions herein and in the Supply Agreement, after Customer has completed the steps outlined below, PureWave will evaluate each returned Product and will use reasonable commercial efforts to either, in its discretion, repair or replace products confirmed by PureWave as non-conforming that are covered under the warranty provided in the Supply Agreement. PureWave shall be responsible for shipping the repaired or replaced Product to Customer. PureWave will use reasonable commercial efforts to ship repaired or replacement Product within thirty (30) business days of its receipt, however, the allegedly non-conforming Product must be received by PureWave before any replacement unit will be shipped. The above warranty will also apply to any replaced or repaired product for 90 days from the date of shipment from PureWave of the replaced or repaired product, or the remainder of the initial warranty period, whichever is longer. Software PureWave warrants to the Customer that for a period of ninety (90) days from your receipt of the Product (the Warranty Period) the Software will perform substantially in accordance with the Documentation. If the Software fails to comply with the warranty set forth above, your exclusive remedy will be, at the option of PureWave (i) a reasonable effort by PureWave to make the Software perform substantially in accordance with the Documentation, or (ii) return of the purchase price. This limited warranty applies only if you return all copies of the Product, together with proof of purchase, to PureWave during the Warranty Period. Page 43 PureWave Quantum 6600 Installation Guide v2.1 This limited warranty is VOID if failure of the Software is due to modification of the Software not made by PureWave, or the abuse or misapplication of the Software. PureWave does not warrant that the Software is error free, that the Customer will be able to operate the Software without problems or interruptions or that the Software or any equipment, system or network on which the Software is used will be free of vulnerability to intrusion or attack. Additional Conditions Notwithstanding anything else herein or otherwise, PureWave reserves the right to establish amendments to this RMA Policy from time to time. Further, PureWave Technical Support may prefer to troubleshoot the wireless link with an onsite Customer technician while the Products are in their original non-conforming state. This process might assist Customer in understanding and troubleshooting the issue. If PureWave was not afforded the opportunity to troubleshoot an allegedly non-conforming Product in original non-conforming state, PureWave may approve or reject the RMA request in its sole discretion, and such Products are not eligible for advance replacement. No Fault Found Notwithstanding sections above, if PureWave cannot duplicate any alleged non-conformity, the Product will be returned to the Customer as "No Fault Found." PureWave reserves the right to charge a testing fee in connection with a returned product that PureWave determines as No Fault Found, and any such payment must be received by PureWave prior to return shipment of the applicable Product to Customer. Warranty Limitations PureWaves warranties do not apply to any product (hardware or software) which has (a) been subjected to abuse, misuse, neglect, accident, or mishandling, (b) been opened, repaired, modified, or altered by anyone other than PureWave, (c) been used for or subjected to applications, environments, or physical or electrical stress or conditions other than as intended and recommended by PureWave, (d) been improperly stored, transported, installed, or used, or (e) had its serial number or other identification markings altered or removed. Warranty Disclaimer PURWAVES SPECIFIC WARRANTIES SUMMARIZED ABOVE ARE THE ONLY WARRANTIES GIVEN BY PUREWAVE WITH RESPECT TO ITS PRODUCTS (HARDWARE AND SOFTWARE) AND ARE GIVEN IN LIEU OF ANY AND ALL OTHER WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY, OR ARISING BY CUSTOM, TRADE USAGE, OR COURSE OF DEALING, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND PUREWAVE DISCLAIMS ANY AND ALL OTHER WARRANTIES TO THE MAXIMUM EXTENT PERMITTED BY LAW. Without limiting the Page 44 PureWave Quantum 6600 Installation Guide v2.1 generality of the foregoing sentence, PureWave makes no warranty or representation, either expressed or implied, as to, and disclaims all liability and responsibility for, (a) the operation, compliance, labeling, or packaging of any of its products under the laws of any jurisdiction outside of the United States of America and (b) the regulatory compliance of any products in any jurisdiction in which it has not specifically identified compliance or the use of any product in any jurisdiction in any manner other than as contemplated in the regulatory certifications and approvals for that product in that jurisdiction. To the extent an implied warranty cannot be excluded, such warranty is limited in duration to the warranty period. The disclaimer and exclusion applies even if the express warranty fails of its essential purpose. Obtaining Warranty Service Customer must contact the Company, by sending an e-mail to support@pwnets.com to obtain warranty service authorization. When contacting PureWave for support, please be prepared to provide the product description and serial number and a description of the problem. The Customer will be expected to complete a Return Material Authorization (RMA) form to initiate the request. Full instructions as to how to complete and where to send the form are provided on the form. Date of proof of purchase from PureWave will be required. Products returned to PureWave Inc must be pre-authorized by PureWave with a Return Material Authorization (RMA) number and sent prepaid and packaged appropriately for safe shipment. The Customer requesting the RMA will be the exporter. The exporter is responsible to ship RMA equipment to PureWaves address and has to bear the cost and risk involved in bringing the goods to PureWaves location. Risk of loss in return shipment will be borne by Customer, and it is recommended that returned goods be insured and/or sent by a method that provides for tracking of the package. Responsibility for loss or damage does not transfer to PureWave until the returned item is received by PureWave. Provided that PureWave determines that the item is actually defective, the repaired or replaced item will be shipped to Customer, at PureWave's expense, (1) not later than thirty (30) days after PureWave receives the defective product or (2) to the terms of a separate written agreement with PureWave. If the allegedly non-conforming Product is not received by PureWave within thirty (30) days of Customer initiating the RMA request, the RMA process for that Product will be deemed cancelled. Customer may also obtain the status of their RMA request(s) by sending an e-mail to support@pwnets.com referencing their assigned RMA Number(s). No product will be accepted for repair or replacement by PureWave without a RMA number. The product must be returned to PureWave, properly packaged to prevent damage, shipping and handling charges prepaid, with the RMA number prominently displayed on the outside of the container. If PureWave determines that a returned product is not defective or is not covered by the terms of the warranty, the Customer will be charged a service charge and return shipping charges. Page 45 PureWave Quantum 6600 Installation Guide v2.1 Table 9 summarizes the conditions and charges that PureWave reserves the right to levy. RMA Related Issue Under Warranty Repair and return No charge, PureWave pays Shipment of unit to PureWave Customer pays Regular Shipment to Customer No charge, PureWave pays Expedited shipment to Customer No Fault Found Customer pays the additional cost of the expedited shipping PureWave reserves the right to levy a charge Warranty for repaired and or replaced product Remainder of the original warranty or 90 days Table 9: Summary of PureWave RMA Conditions and Charges Out of Box Failure (OBF) / Dead on Arrival (DOA) In the event a product becomes entirely inoperable within the first forty-eight (48) hours of the initial installation of the product, and such installation takes place within ninety (90) days after the date of shipment from PureWave, the Customer may request that the unit be considered as an Out Box Failure

(OBF) or Dead on Arrival (DOA). PureWave will consider an OBF or DOA as being eligible to be considered for an advance replacement request. The conditions for such a request are as outlined below. Advanced Replacement In some unique situations, PureWave may consider, at its sole discretion on a case-by-case basis, an advance replacement request for a non-conforming Product that is still covered under its warranty period. The following conditions apply to advance replacements:

PureWave has a suitable equivalent replacement unit available. Customers network is experiencing a severe degradation or a complete outage. Customer has complied with the RMA procedures provided herein PureWave reserves the right to levy a charge for the processing and handling of the advance replacement request. To waive this charge will be the sole discretion of the Senior VP of Sales. If expedited shipping is required then Customer pays for all expedited shipping and handling charges that are in excess of the regular shipment charges. To waive this charge will be the sole discretion of the Senior VP of Sales. Page 46

(i)

(ii)

(iii)

(iv)

(v) PureWave Quantum 6600 Installation Guide v2.1

(vi) When an advance replacement is provided and Customer fails to return the original product to

(vii) PureWave within fifteen (15) days after shipment of the replacement, PureWave will charge the Customer for the replacement product, at list price. The shipment of advance replacement products is subject to local legal requirements and may not be available in all locations. PureWave will use reasonable commercial efforts to ship advance replacement Products within five (5) business days after PureWaves confirmation that advance replacement is appropriate. PureWave shall not be responsible for shipping delays if any of conditions herein are not met. For products that are out of warranty, the repair of such products will be subject to a repair fee. In addition, any request for the Advance Replacement of product that is out of warranty will be subject to not only the repair fee but additional fees as well. Please contact PureWave for further details. PureWave does offer extended warranties and enhanced service options for its Customers who desire those enhanced features. Please contact PureWave for further information about these options Assistance For assistance, contact your nearest PureWave Networks Sales and Service office. Additional information is available on the PureWave Networks website at http://www.pwnets.com. For Customer Service call: 650-528-5200, or Email: support@pwnets.com. Page 47

Designed for Operators, by Operators Table of Contents Symbols used in this document .................................................................................................................... 4 Regulatory Notice ......................................................................................................................................... 4 Safety Precautions ........................................................................................................................................ 5 1. Preface ...................................................................................................................................................... 6 1.1 About This Document ......................................................................................................................... 6 1.2 Locating the Product Serial Number ................................................................................................... 6 1.3 Obtaining Documentation and Support .............................................................................................. 6 2. Mercury Quantum Base Station Overview ............................................................................................... 7 2.1 Introduction What is a Compact Base Station ................................................................................. 7 2.2 Mercury Quantum 6600 at a Glance................................................................................................... 7 2.3 A Closer Look ....................................................................................................................................... 9 2.3.1 Ports and Indicators ..................................................................................................................... 9 2.3.2 Radio and Physical Layer Specifications ..................................................................................... 11 2.3.3 Capacity and Performance Characteristics ................................................................................ 14 2.3.4 Electro-Mechanical and Environmental Specifications.............................................................. 15 3. Quick Start Guide .................................................................................................................................... 17 3.1 Preparing and Powering Up the Base Station ................................................................................... 17 3.2 Default Parameters ........................................................................................................................... 18 3.3 Logging in to the CLI .......................................................................................................................... 18 3.3.1 Accessing the CLI via the Base Station Console Port ................................................................. 18 3.3.2 Accessing the CLI via an Ethernet Port....................................................................................... 21 3.4 Logging into the Web GUI Interface ................................................................................................. 21 3.4.1 Web Interface Configuration Key Concepts ............................................................................... 24 3.4.2 Web GUI CLI Access Level .......................................................................................................... 32 3.5 Base Station Initial Configuration ..................................................................................................... 38 3.5.1 System Architecture and Terminology....................................................................................... 38 3.5.2 Base Station Management Interface Access Parameters .......................................................... 38 3.5.3 Base Station Configuration Parameters ..................................................................................... 42 3.5.4 Connecting a Subscriber Station ................................................................................................ 93 3.5.5 Subscriber CPE Client Profiles .................................................................................................... 99 3.6 Base Station Software Upgrade ...................................................................................................... 125 2 | P a g e Designed for Operators, by Operators 3.6.1 Automatic Upgrade .................................................................................................................. 127 3.6.2 Manual Software Upgrade ....................................................................................................... 128 3.6.3 Base Station Performance Monitoring .................................................................................... 131 4 Citizens Broadband Radio Service Operations (47 C.F.R. Part 96) ......................................................... 165 4.1 Citizens Broadband Radio Service (CBRS) Overview ....................................................................... 165 4.1.2 CBRS Operations ...................................................................................................................... 165 4.1.3 Requirements for the Quantum 6636 to Operate in CBRS ...................................................... 166 4.2 Base Station Configuration for use with CBRS and the Mercury Networks Domain Proxy ............ 167 4.3 External Antennas ........................................................................................................................... 168 4.3.1 Mercury Networks 3.3-3.8GHz 2-Port Antenna (098-00459-035) ........................................... 169 4.3.2 Mercury Networks 3.3-3.8GHz 6-Port Antenna (098-00459-035) ........................................... 171 4.4 The Mercury Networks Domain Proxy ............................................................................................ 172 4.3.1 Accessing the Mercury Networks Domain Proxy ..................................................................... 173 4.3.2 Domain Proxy Devices ........................................................................................................... 174 4.3.3 CPIs (Certified Professional Installers) ..................................................................................... 179 4.3.4 Logs .......................................................................................................................................... 180 Appendix A Capacity Tables ...................................................................................................................... 182 Appendix B Changes Requiring a Reboot .................................................................................................. 186 Appendix C Limited Warranty Statements ............................................................................................... 187 Hardware .............................................................................................................................................. 187 Software ................................................................................................................................................ 187 Additional Conditions............................................................................................................................ 187 No Fault Found ...................................................................................................................................... 188 Warranty Limitations ............................................................................................................................ 188 Warranty Disclaimer ............................................................................................................................. 188 Obtaining Warranty Service .................................................................................................................. 188 Assistance.............................................................................................................................................. 189 3 | P a g e Designed for Operators, by Operators Symbols used in this document Notes, cautions, and timesavers use these conventions and symbols:

Tip A tip will help you to solve a problem. A tip might not be troubleshooting or even an action, but could be useful information. Note Notes contain helpful suggestions or references to materials not contained in this manual. Caution Be careful. In Caution situations, you might do something that could result equipment damage or loss of data. Warning A warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Regulatory Notice This device complies with the FCC limits a class B digital device, pursuant to Part 15 of the FCC Rules. A complete list of regulatory certifications can be provided by Mercury Networks upon request. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

Re-orient or relocate the receiving antenna(s). Connect the equipment into an outlet on a circuit different from that to which the receiver is Increase the separation between the equipment and other receiver. connected. Consult the dealer or an experienced radio frequency technician/engineer for help. Shielded cables and I/O cords must be used for this equipment to comply with the relevant FCC regulations. 4 | P a g e Designed for Operators, by Operators Changes or modifications not expressly approved by Mercury Networks, LLC. may void the users authority to operate this equipment. The 2.3, 3.3, and 3.5 GHz products have the CE (European Conformity) Mark. Note: This device must be professionally installed, and the operator and/or the licensed spectrum holder have the responsibility to comply with FCC regulations. Note: This device must be professionally installed, and the operator and/or the licensed spectrum holder have the responsibility to comply with FCC regulations. Note: The contention protocol MUST be turned on and used for the specified band

(3.65GHz - 3.7 GHz) in the specified country or wherever FCC rules and regulations are enforced. Failure to comply makes the operation of this device illegal. Safety Precautions When operating or installing this equipment, please observe the following precautions to minimize the risk of danger or personnel injury:

NEVER install equipment if there is a chance of lightning or other adverse weather conditions. NEVER install equipment in a wet location unless the equipment is specifically design for wet locations. NEVER touch un-insulated wires or terminals unless the wire has been disconnected from any equipment. ALWAYS use caution when installing or modifying cables. ALWAYS disconnect all lines and power connections before servicing or disassembling this equipment. ALWAYS assume that all components and assemblies are static sensitive and always follow local ESD-prevention guidelines to prevent equipment damage. For any external power supply that provides the power source for the Mercury Networks equipment, replace any power supply fuse with the same rating or equivalent; otherwise Mercury Networks cannot not be responsible for any subsequent damage to the equipment. 5 | P a g e Designed for Operators, by Operators For performance and safety reasons, only power supplies listed for use with telephone equipment by a Nationally Recognized Testing Laboratory (NRTL) should be used with equipment. ALL wiring external to the product(s) should follow the provisions of the current edition of the National Electrical Code. These units contain no user serviceable components. Only authorized service personnel should service or repair these units. Use only isolated Class 2 Power Source, Rated 48VDC, 5.0A Minimum. 1. Preface 1.1 About This Document The purpose of this User Guide is to quickly familiarize the user with the Mercury Networks Quantum 6000 family of Base stations, their initial setup, and provisioning. It is not intended to be a comprehensive reference for the product and all its capabilities, nor does it cover in depth provisioning, operation, or administration using the PureView Network Management System or the Mercury Networks Quantum command line interface. Please refer to their respective user guides for more in-depth coverage of those tools. Please also note that this guide does not cover the physical installation of the product, but rather assumes that the Base Station has been fully installed and is ready to be powered on. Please refer to the Mercury Networks Quantum 6600 Installation Guide for detailed professional installation guidelines. Always refer to the current set of Release Notes for the most up to date information and a description of the current features as they relate to the Mercury Networks system. These may be different from and supersede the information contained within this Installation Guide. 1.2 Locating the Product Serial Number The product identification information, serial number, and certification information are located on a label on the side panel of the Base station. Please take note of and keep this information for your records, as it is very important for warranty and support services. 1.3 Obtaining Documentation and Support All requests for documentation and/or support should be addressed to:

Mercury Networks, LLC. 1100 Walnut St, Suite 2050 Kansas City, Missouri 64105 E-mail: support@mercurynets.com Tel: (888) 909-6717 Fax: (408) 827-9124 6 | P a g e Designed for Operators, by Operators 2. Mercury Quantum Base Station Overview 2.1 Introduction What is a Compact Base Station At Mercury, we believe that true broadband data networks must roll out in a completely different manner than the traditional, low-throughput cellular networks of yesterday. The traditional cellular network paradigm of colossal macro Base stations and large cell radii developed from the need for high-coverage networks to carry low-bandwidth voice and messaging traffic. However, as the demand for data-based applications has grown, networks have quickly become congested, necessitating new wireless standards designed specifically for high-speed broadband data. Furthermore, as spectrum is always a scarce and expensive resource, the need for improved frequency re-use techniques has become more important than ever. The clear solution to this is higher-efficiency wireless standards, such as IEEE 802.16e Mobile WiMAX, and more flexible cell sizes. Where medium and high population density exists, cell sizes should be small to enable increased spectral re-use, thereby ensuring that each subscriber enjoys a sufficient amount of throughput. In such cases it may be necessary to deploy Base stations on utility poles, flag poles, rooftops, small buildings and walls. This necessitates small, pleasant form-factor Base stations that can accept a variety of antenna types, both omni-directional and directional. Such Base stations are often referred to as Pico. Because wired backhaul may not always be available in some such locations, it also suggests the need for wireless backhaul options. On the other hand, in rural areas with lower population densities, it makes more economic sense to deploy fewer Base stations on higher towers or buildings and usually with higher transmit power. This is closer to the traditional cellular approach and typically involves large, expensive and power-hungry macro or micro Base stations, often with split designs requiring both indoor and tower-top electronics. Wherever indoor components are required an operator must obtain an air-conditioned shelter, which adds significantly to the continual operating expenditures of such a deployment and limits the deployment location. Mercury has taken a revolutionary approach in the development of exclusively Compact Base stations. A compact Base station shares the similar form-factor and cost of a Pico Base station, but with the performance of a Macro Base station. It is a zero-footprint device that can be fully co-located with its antennas. It is the best of all worlds and can be flexibly deployed in Pico, Macro, and Micro type deployments. Welcome to the Revolution!

2.2 Mercury Quantum 6600 at a Glance The Quantum 6600 is Mercurys 3rd generation Base station and is part of the Mercury X4G ecosystem. Built on a 6x6 design, the Quantum 6600 was made for non-line-of-sight and can handle the toughest of environments. The 6600 is quite simply the highest performing, most advanced carrier-grade Base station in the market. This Users Guide covers the Mercury Quantum 6600 products, with models differentiated by only the frequency variant which is represented by the two right digits. For example, the Mercury Quantum 6625 is the 2.5GHz variant, supported 2.5-2.7GHz. Otherwise they are functionally identical. In this guide we will, without loss of generality, refer primarily to the Mercury Quantum 6600 product, which is 7 | P a g e Designed for Operators, by Operators synonymous to writing Mercury Quantum 66xx. Please note that not all Quantum models are available in all markets. Please contact your sales representative for additional information and ordering options. The Mercury Quantum Family of Base station products is fully 802.16e (Mobile WiMAX) compliant and designed to interoperate seamlessly with standard, off-the-shelf, WiMAX certified subscriber devices. All Mercury Quantum products feature a software-defined radio (SDR) architecture that allows them to continuously evolve and take on new features as they become available. Some of the key highlights of the Mercury Quantum 6600 include the following:

Superior Range An antenna array of 6 antennas operated in concert creates tightly focused radio beams that extend the range of each Base station by up to 40% or boost capacity where required. Spectral Re-use Sophisticated interference mitigation techniques coupled with advanced beamforming technology, both made possible by Mercurys multiple antenna architecture, allow for simple network deployments and for improved spectral re-use. Software Defined Radio Protects your investment through support for over-the-air, field upgrades of existing networks as standards evolve and new features and capabilities are released. Completely Weatherproof Mercury Quantum Base stations do not require shelter and can be installed completely outdoors. This eliminates the capital cost of building a shelter and the recurring cost of leasing or running an airconditioned site. Flexibly Mount Virtually Anywhere Mercury Quantum Base stations can be deployed on towers, utility poles, walls, rooftops, etc, without the need for remote RF heads. ASN-GW Optional Mercury Quantum Base stations can operate with or without an ASN-GW, making even small deployments affordable. Mercury Quantum Base stations can utilize virtually any off the shelf antennas, both omnidirectional and sectored. However, Mercury recommends our own line of affordable, compact, multi-antenna panels designed specifically to complement the performance of our Base stations. Mercury Quantum Base Stations can be installed indoors or outdoors, however the antennas must always be installed outdoors. Figure 1 shows a Mercury Quantum 6600 Base station co-located on a tower with a Mercury 6-Port Antenna Panel. Mercurys carrier-grade solution includes the full-featured and highly scalable PureView NMS (Network Management System), which can efficiently and powerfully provision and manage all Base station and Subscriber Stations in the access network. PureView features include automatic discovery, tables, configuration, and performance management. PureView utilizes full open standard SNMP on the access network side, and employs a full-

featured northbound interface for connection to virtually any existing NMS. fault management, inventory Figure 1 Mercury Quantum 6600 Base Station Mounted on Tower 8 | P a g e Designed for Operators, by Operators In addition to the PureView NMS, all Mercury Quantum Base Stations support a fullfeatured Command Line Interface (CLI) and an integrated Web Interface. Please refer to the PureView NMS User Guide and the CLI User Guide for in depth coverage of those applications. 2.3 A Closer Look The Mercury Quantum 6600 Base Station is a single, weather-resistant enclosure with overall dimensions 17.5 x 16.7 x 5.3 (44cm x 42cm x 13cm). The Base station is a single self-contained unit. Note that the Mercury Quantum 6600 Base Station has no user serviceable components. Mercury Quantum products employ a sophisticated and flexible hardware architecture that combines general-purpose processors, and application-specific hardware. Together these components deliver the processing power required to realize the high-performance required by todays demanding applications, while yielding the flexibility to support future functionality as needs arise. 2.3.1 Ports and Indicators The Mercury Quantum 6600 connector panel is shown in Figure 2. The products flexible architecture allows for a number of product variants to suite almost limitless deployment needs. The model shown includes six antenna ports, two CAT-5 Gigabit Ethernet backhaul ports, and a DC power connector. Single or Multi-Mode Fiber backhaul are also available. As the configuration of individual Base station models varies, so will the appearance of the connector panel. All Mercury Quantum Base stations include a serial

(RS-232) console port, a GPS antenna connector, a ground terminal, and three high-intensity LEDs. Figure 2 Mercury Quantum 6600 Base Station Note that a professional installer must complete the installation and weatherproofing. Please refer to the Mercury Quantum 6600 Base Station Installation Guide for detailed instructions. 9 | P a g e Designed for Operators, by Operators The function of each Base station connector/port is described in Table 1. Note that every connector present must be terminated to ensure proper Base station operation. Please refer to the Mercury Quantum 6600 Installation Guide for comprehensive installation procedures. Connector Function Power GPS ETH-1 ETH-2

-48VDC power source inputs for the unit. DC power connector: LTW BB-04PMMS-LC7001 (chassis), LTW BB-04BFFA-LL7001 (mate) N-type female connector for mandatory external GPS antenna. 3.3V power on center pin. This Gigabit Ethernet port serves as the data traffic backhaul Interface and also provides for in-band management of the Base Station. Available port options are Cat-5 (RJ-45), Single-Mode Fiber (HartingPull/Han 3 A), and Multi-Mode (LC duplex) Fiber. This Gigabit Ethernet port may be used for out-of-band management of the Base Station. It may also be used to connect to an external device, such as a web camera. Available port options are Cat-5 (RJ45), Single-Mode Fiber

(HartingPull/Han 3 A), and Multi-Mode (LC duplex) Fiber. Console RJ-45 based RS-232 port for CLI control via a console. Defaults settings are 38400, 8 data bits, 1 stop bit, no parity bits, no flow control. ANT 1-6 N-type Tx / Rx Antenna Ports. Table 1 Base Station Connector Description LED Function Green - BS is up and running normally. No faults detected. Blinking Red System booting up, or system is temporarily down. Solid Red -

Fault detected. Off LEDs disabled or Power is off. Fault detected if POWER LED is Green, but STATUS LED is Off.

(Status LED for ETH-1 Gigabit Ethernet Port) Solid Green Connected to an Ethernet switch. Blinking Green Ethernet packet activity. Off LEDs disabled or no Ethernet activity detected. Green Power is being supplied to the BS. Off LEDs disabled or no power is being supplied to the BS. Table 2 Base Station LED Description The Base Stations three high-intensity LEDs are intended to be viewable from the ground for quick confirmation of the units operational state. Table 2 describes the function of each indicator. Note 10 | P a g e Status Link Power Designed for Operators, by Operators that the LEDs can be turned off by the operator using the PureView NMS, the Web Interface, or the Base Stations command-line interface. 2.3.2 Radio and Physical Layer Specifications The Mercury Quantum Family of Base Stations is available in several models to support a variety of frequency bands and the regulatory requirements of a number of countries. Because several deployment-specific variables (e.g., antenna type, cable type and length, settings, etc) can affect the effective power output and other characteristics of the system, it is the customers responsibility to assure that each deployment of this product meets applicable regulations. The PureView NMS, the Web UI, and the CLI all provide guidelines and feedback to ensure an appropriate installation. Table 3 lists key radio-related specifications of Mercury Quantum Base Stations. Note that additional features, not listed, may be released in future software revisions. Parameter Specification 6623: 2.30-2.40 GHz 6625: 2.50-2.70 GHz 6633: 3.30-3.40 GHz 6635: 3.40-3.60 GHz 6635-IC: 3.45-3.65 GHz 6636: 3.65-3.70 GHz 3.5 MHz 5 MHz 7 MHz 10 MHz TDD Frequency Bands Channel Sizes Duplex Method DL:UL Ratios 35:12, 29:18, 32:15, 26:21 (5 MHz and 10 MHz) 23:9, 21:12, 17:15 (3.5 MHz and 7 MHz) Number of Tx/Rx Antennas 6 Tx, 6 Rx Tx Power per Antenna 33dBm (RMS data power at maximum MCS level, measured at each external antenna connector of the Base Station) Permutation PUSC Modulation Rates QPSK-1/2, QPSK-3/4 16QAM-1/2, 16QAM-3/4 64QAM-1/2, 64QAM-2/3, 64QAM-3/4, 64QAM-5/6 Data Repetition Coding QPSK-1/2 Repetition 2, 4, 6 MAP Repetition 1, 2 11 | P a g e Designed for Operators, by Operators Smart Antenna Capabilities Beamforming, MIMO Matrix A, MIMO Matrix B, Cyclic Delay Diversity, MRC Air Link Optimization HARQ, CTC Table 3 Radio and PHY Specifications 2.3.2.1 Receiver Sensitivity Table 4 presents typical receiver sensitivity specs of the Quantum 6600 Base Station. Note that sensitivity will be correspondingly less on models with fewer than 6 antennas. Note that the values presented are measured over the entire channel bandwidth, as opposed to WiMAX Radio Conformance Test (RCT) type measurements, which are measured over only a fraction of the channel bandwidth. Typical 6-Ant RX Sensitivity (AWGN, 106 BER, Full Band, in dBm) UL MCS (CTS) 3.5 MHz 5 MHz 7 MHz 10 MHz QPSK-1/2

-107

-105

-104

-102 QPSK-3/4

-104

-102

-101 QAM16-1/2

-102

-100

-99

-97

-93

-92

-88

-87

-84

-99

-95

-94

-90

-89

-86 QAM16-3/4 QAM64-1/2 QAM64-2/3 QAM64-3/4 QAM64-5/6

-98

-97

-93

-92

-89

-96

-95

-91

-90

-87 Table 4 Typical Uplink RX Sensitivity 2.3.2.2 Computing EIRP Power Effective Isotropic Radiated Power (EIRP) refers to the transmit power radiating out of the antenna. The accurate computation of EIRP is essential to proper network planning and to ensuring that the system meets local and regional maximum power regulations. 12 | P a g e Designed for Operators, by Operators As indicated in Table 3, the average Tx power output at each Base Station antenna connector is 33dBm. The average EIRP per antenna is computed as follows:

Ave EIRP per Ant (in dBm) = Ave Tx Pwr per Ant + Ant Gain Cable and Connector Loss For example, if deployed with a 15dBi antenna connected to the Base Station with only a few feet of cable, the average EIRP per Antenna might be 33dBm + 15dBi 1dB = 47dBm. The total average EIRP of the Base Station with all antennas combined can then be computed as follows:

Total Ave EIRP (in dBm) = Ave EIRP per Ant + 10log (Number of Antennas) For a 6 antenna Base Station, the example above yields Total Ave EIRP = 47dBm + 7.78dB = 54.78dBm. Note that some regulations refer to peak power, which in a WiMAX system is normally as much as 10dB higher than average power. In the case of the Mercury Quantum products the peak power can be assumed to be 9dB higher than average. Therefore, Peak EIRP should be computed as follows:

Peak EIRP per Ant (in dBm) = Ave EIRP per Ant + 9dB Total Peak EIRP (in dBm) = Total Ave EIRP + 9dB For the above example, Peak EIRP per Ant = 46dBm + 9dB = 54dBm and Total Peak EIRP = 53.78dBm

+ 9dB = 62.78dBm. These equations are summarized in Table 5. EIRP Metric Formula Ave EIRP per Ant (in dBm)

= Ave Tx Pwr per Ant + Ant Gain Cable and Connector Loss Total Ave EIRP (in dBm

= Ave EIRP per Ant + 10log(Number of Antennas) Peak EIRP (in dBm)

= Ave EIRP per Ant + 9dB Total Peak EIRP (in dBm)

= Total Ave EIRP + 9dB Table 5 EIRP Calculations Note that some regulations are specified for particular channel bandwidths and/or antenna beamwidth and in such cases the allowable power should be scaled accordingly. As with the previous calculations, each case is often unique. Although the PureView NMS provides guidance and limits where known regional regulations apply, it is ultimately the responsibility of the spectrum holder to assure that appropriate limits are set. 13 | P a g e Designed for Operators, by Operators 2.3.2.3 Smart Antenna Capabilities Beamforming is a technique that combines and focuses signals to and from multiple antennas to improve both downlink and uplink performance. On the uplink, the Base Station combines signals received on its multiple antennas, resulting in substantial link budget gains that improve range and throughput. Maximum Ratio Combining (MRC) and Minimum Mean-Square Error (MMSE) are basic techniques from which more sophisticated uplink processing techniques (such as interference mitigation) are built. On the downlink (Base Station to Subscriber Station), sophisticated digital signal processing algorithms exploit information gathered during the uplink beamforming process to concentrate the transmitted RF energy from the antenna array to the exact subscriber stations locations, improving gain, efficiency and signal to noise ratio (SNR), resulting in greater range and throughput. MIMO Matrix A utilizes a technique called space-time coding (STC), which exploits the spatial diversity of the channel to improve downlink performance. By improving data reception, it can increase range and maximize the utilization of available sector capacity. MIMO Matrix B utilizes a technique called spatial multiplexing (SM), in which multiple streams of data are simultaneously transmitted through multiple antennas and effectively separated by the receiving device. This technique can actually increase the spectral efficiency and, hence, the capacity of a system. The effectiveness of MIMO relies upon the spatial diversity inherent within the channel as well as other factors, and therefore a given technique may be more appropriate for certain users or deployments. Fortunately, Mercury Quantum Base Stations make these decisions automatically, maximizing the efficiency of your valuable spectrum. Cyclic Delay Diversity (CDD) is a technique employed by Mercury Quantum Base stations to allow the power of multiple antennas to be combined in transmitting a single stream of data even when MIMO or beamforming cannot be supported (e.g., when transmitting the MAP). 2.3.3 Capacity and Performance Characteristics Table 6 summarizes key upper layer and overall performance characteristics of Mercury Quantum Base Stations. Note that some features may not be currently available but are planned for future software releases. In addition, detailed throughput tables for each DL:UL ratios are presented in Appendix B. Parameter Specification Maximum Number of Connected Users Maximum Number of Service Flows per User 200 16 14 | P a g e Designed for Operators, by Operators Peak Throughput Aggregate: Up to 58Mbps (35:12 Ratio) DL: Up to 43Mbps (35:12 Ratio) UL: Up to 8Mbps (26:21 Ratio) QoS BE, UGS, eRTPs, nRTPs, RTPs Convergence Sub-Layer IP-CS, Eth-CS, IPv4, IPv6 Pass-Through Security Security AES-128, EAP-TLS, EAP-TTLS, PKMv2 Management PureView NMS / EMS, Remote CLI, Web Interface, SNMP v2c, SNMPv3 Core Network Interface R6 (NWG 1.2.2, NWG 1.3.1), Radius Table 6 Performance Characteristics 2.3.4 Electro-Mechanical and Environmental Specifications All Mercury Quantum Family Base Stations consist of a single, all-in-one, fully weatherproof unit that may be installed entirely outdoors or indoors, as dictated by each deployment. Please refer to the Mercury Quantum Base Station Installation Guide for detailed installation instructions and guidelines. Table 7 lists the mechanical, electrical, and environmental properties of the Mercury Quantum 6600 Base Station. Physical & Environmental Specification Dimensions 17.5 x 16.7 x 5.3 (44cm x 42cm x 13cm) 32lbs (14.5kg) (does not include mounting hardware) Weight Power

-48 VDC (150 Watts Max) Temperature

-40C to +55C (ETSI EN 300 019-1.4 Class 4.1E) Humidity 5-100% non-condensing Altitude To 10,000 ft above sea level 15 | P a g e Designed for Operators, by Operators Surge Protection UL497B Lightning Protection Min 10kA IEC 6100-4-5 (optional via external kit) Weatherproofing IEC IP67 Wind Loading 160Km/hr operation, 200Km/hr survival Safety and IEC IP EN 300 019-2-2, GR487, IEC 60529 Vibration and Dust ETSI EN 300 019-1-4 Class 4.1E Table 7 Environmental and Mechanical Specifications For temperatures above +45 degrees C in direct sunlight it is necessary to deploy the Base Station with the available solar shield, shown in Figure 3. Again, details can be found in the Mercury Quantum 6600 Base Station Installation Guide. Figure 3 Quantum 6600 with Available Solar Shield 16 | P a g e Designed for Operators, by Operators 3. Quick Start Guide This section describes how an Operator may power-up the Mercury Base Station and verify proper system initialization and configuration. There are two methods by which a Mercury Quantum Base Station may be configured and/or managed. This can be achieved via either a graphical user interface

(GUI) Web Interface or a command line interface (CLI). Each interface has the capability of configuring all parameters available in the Base Station. It is generally recommended to configure using the CLI for the first initial configuration of the Base Station or if the Base Station management interface parameters are not known. Mercury thereafter recommends using the Web Interface for all configuration parameters. Note that the Web Interface and the CLI utilize the same terminology, parameter names, etc. 3.1 Preparing and Powering Up the Base Station Before powering on the Base Station, it is critical that all its connector panel ports be properly connected or terminated per the detailed instructions in the Mercury Quantum 6600 Installation Guide. Failure to do so may result in damage to the Base station. The procedures in this section assume the following connections have been to the Base Station:

Antennas have been connected to each Base Station ANT (ANT 1 through ANT 6) ports. A GPS antenna is properly installed and attached to the Base Station GPS port. The ETH-1 port is connected to an accessible network via a router or other mechanism. An appropriate cable has been connected to the Console port. To connect to the Console port, the User will need the following hardware that is provided with the Base Station installation kit. These are as follows:

o RJ45 cable o DB9 male connector (Network Adapter) o DB9 female to DB9 female adapter The adaptor should be connected to a straight-through serial cable. Do not use a Cisco rollover cable or a null modem serial cable as these are not supported. Please see the Mercury Quantum 6600 Installation Guide for more details. Optional: Serial to USB connector. Most laptop nowadays comes with USB connection instead of serial connection. If the PC/laptop has a DB9 serial connection, then there is no requirement for a USB adapter. If not, then you will need to get serial to USB adapter to access the Base Station CLI. Plug one end of a straight Cat 5 Ethernet cable into the Base Station Console port and the other end into the RJ45 to Modem adapter. Connect the other end of this Modem adapter to a DB9 serial cable and connect this DB9 serial cable to a USB adapter that connect to your laptop. 17 | P a g e Designed for Operators, by Operators With the Base Station and all cables properly installed, power may now be applied to the Base Station. The Base Station has no power switch so it will begin to power up immediately when a power source is attached. The POWER LED should be solid green 3.2 Default Parameters Table 8 lists the factory default values that are set prior to shipment. These default parameters provide the means for a User to gain access to the system. Parameter Factory Default Mgmt IP Address 192.168.1.10 Mgmt IP Network 255.255.255.0 Mgmt Default Gateway 192.168.1.254 Hostname quantum-bs Admin Username admin Admin User Password admin123 Table 8 Base Station Management Interface and Access Default Parameters 3.3 Logging in to the CLI The Mercury Quantum Base Stations Command Line Interface (CLI) has a standard Cisco IOS

(Internetwork Operating System) look and feel to its operation. It is accessible via the Base Station Console interface using an appropriate terminal emulator, or via a Base Station ETH-1 port using either SSH or Telnet. Both methods of access will be described. Telnet is disabled by default so may not be used for initial configuration. It is assumed that the default parameters (IP address, baud rate, etc) are still in use. If defaults have been changed then please use the current values. 3.3.1 Accessing the CLI via the Base Station Console Port 1. Connect a computer to the Base Station Console port as detailed in section 3.1. 18 | P a g e Designed for Operators, by Operators HyperTerminal (Figure 4). 2. Open a terminal emulation program on the computer. Suitable programs are PuTTY or Figure 4 PuTTY Serial Port Configuration Window Create a new connection with the serial port settings as outlined in Table 9. Serial Console Port Settings Serial Line COM1 Speed (Baud Rates) 38400 8 1 None None Table 9 Console Port Settings Data bits Stop Bits Parity Flow Control 19 | P a g e Designed for Operators, by Operators A login prompt will be displayed as in Figure 5: Console Login. The default Login and Password are:

Default Login:

Default Password:

admin admin123 Figure 5 Console Login 3. After this login, the User will be presented at the hostname prompt (Figure 6). If the Base Station is still in its default status, then the hostname prompt will be quantum-bs. Figure 6 Console Login Default Status 20 | P a g e Designed for Operators, by Operators 3.3.2 Accessing the CLI via an Ethernet Port 1. Connect a computer using an Ethernet connection to the Base Station ETH-1 port (either directly or via a router or network). Open an SSH client program such as PuTTY (Figure 7). The default port number is 22. Figure 7 PuTTY SSH Client Configuration 2. Create a new SSH profile using the default management IP values. If the defaults have been changed, please use their current values. If the management IP settings are "unknown" then the Base Station can only be accessed via its Console port (refer to section 3.3.1). Once the Base Station has been accessed, its management IP settings can be reset using the procedure detailed in Section 3.5.2. 3. The default Login and Password are:

Default Login:

Default Password:

admin admin123 3.4 Logging into the Web GUI Interface The Mercury Quantum Base Stations Web Interface is accessible through most major web browsers that support SSL connections. The Web Interface has been specifically tested on Internet Explorer

(Version 7 and up) and Mozilla FireFox. Access via HTTP and HTTPS are both supported; however, HTTPS is the default and HTTP is disabled by default. If the current ETH-1 port IP settings have been lost, then they must be reset using access via the Base Station Console CLI (see section 3.3.1). The ETH-1 management IP settings must be known if the Base Station is to be accessed via the Web GUI Interface. 1. Connect a computer using an Ethernet connection to the Base Station ETH-1 port (either directly or via a router/network). Open an SSH client program on the computer. 2. Open a web browser and type https://192.168.1.10 or http://192.168.1.10 (if HTTP has been enabled, which is disabled by default) in the address field. If the default ETH-1 management IP settings have been changed, please use the current management IP. 21 | P a g e Designed for Operators, by Operators If the User is presented with a certificate error in the browser, then just click ignore or continue to web site and proceed. 3. The login page is displayed in Figure 8. The default Username and Password are:

Default Login:

Default Password:

admin admin123 Figure 8 Web GUI Interface Login Page 4. After login, the User will be presented at the Main Web GUI Interface Screen (Figure 9). This will be the starting position for all subsequent configurations. Figure 9 Main Web GUI Interface Screen 5. The structure of the Main Web GUI Interface Screen is as follows:

Configuration and a Tools tab across the top of the screen i. Underneath these Tabs there are the View or Edit modes of operation (Edit Private and Edit Exclusive). 22 | P a g e Designed for Operators, by Operators Configuration tree on the left-hand side of the screen which consists of the Main Menu Options. The plus sign + indicates that there are Main Menu Sub-Elements to each Main Menu Option. The right-hand side of the screen to the right of the Main Menu Options will be blank. 6. Once a Main Menu Option has been selected and navigated to, even if the User reverts to the Main Web GUI Interface Screen, the previous menu option will be displayed on the right-hand side of the screen. Once the screen is "refreshed", this will be cleared away. To enable Base Station access via HTTP:

1. From the Main Web GUI Interface Screen select the Configuration Tab and then the web Main Menu Option form the left-hand side menu (Figure 10) Figure 10 Web GUI Interface Configuration Menu 2. A window will be displayed that provides an indication or not as to the Web Server HTTP Support

(Figure 11). 23 | P a g e Designed for Operators, by Operators Figure 11 Web GUI Interface HTTP Support 3. To enable first select Edit Private or Edit Exclusive. This will drop the User into the Edit mode

(Figure 12). The User can enable the Web Server HTTP Support by selecting the Enabled option. 4. The User must Commit the changes (apply the configuration in run-time). To commit, select the Commit option. A prompt screen will appear directing the User to confirm the pending configuration changes. To proceed the User must select Cancel or OK. 3.4.1 Web Interface Configuration Key Concepts The Web GUI Interface, when the Configuration Tab has been selected, has two major modes of operation:

View Mode: Read-only access of all parameters. This is the default mode upon initial log in Edit Mode: Write access configuration of all available parameters. Within this mode there are

(refer to Figure 9). two sub-options:

o Edit Private. Edit Private will allow the user to configure all parameters but will not lock the configuration database, allowing for other users to make configuration changes at the same time (s). o Edit Exclusive. Edit Exclusive will lock the configuration database and prevent any other user from making configuration changes. Note: System configuration changes are first made to the running configuration database in memory. This allows the opportunity for the user to test the changes first before saving. In order to make the change persistent and survive a restart, the Configuration-

Write command must be used. 24 | P a g e Designed for Operators, by Operators Figure 12 The Web GUI Interface Screen in Edit Private Mode At the Main Web GUI Interface Screen, select the Configuration Tab, select the configuration Main Menu option and then Edit Private or Edit Exclusive. The User will now be in the Edit mode. There are a number of key concepts that will be repeatedly used when the User is in the Edit mode and thus making configuration changes. These key concepts form the six Command Menu Options when the User is in the Edit mode. These are:

Changes. This prompts the User to see the configuration changes that have been made. Validate. This validates that the changes are valid and have been configured correctly. Revert All. This will cancel (or revert) any changes that may have been made. Commit. This will commit the changes to the running database. Rollback. This will rollback any changes to a previously saved state. Exit Transaction. This will exit the Edit mode. When the User selects the Changes Command Menu Option then they are presented with the following options:

If no configuration changes have been made, then a popup window appears stating "No configuration changes have been made". The User simply selects the OK prompt to navigate back to the Edit Mode. 25 | P a g e Designed for Operators, by Operators Figure 13 Configuration Changes Popup Window If relevant changes have been made, then a window appears. This indicates the relevant parameter that is in the process of being changed and the old and the new value. There is also an option within this window to Revert the change (Figure 14). If the User selects this revert option, then the intended changes will be reversed and the "No configuration changes" will appear (Figure 13). Figure 14 Revert Option 26 | P a g e Designed for Operators, by Operators If the User has made some configuration changes and then they decide to reverse the changes then the User can select the Revert All window option. Selecting this option presents:

If no configuration changes have been made, then a window appears stating "There is nothing to revert". The User simply selects the OK prompt to navigate back to the Edit Mode. If changes have been made, then a window appears stating "All your noncommitted configuration changes will be reverted" (Figure 15). The User simply selects the OK prompt to proceed and navigate back to the Edit Mode. Figure 15 Revert All Configuration Changes If the User has made some configuration changes and these have been committed and saved the User can make use of the Rollback All window option. A rolling audit log of all configuration changes in stored within the Base Station. This log is a record of:

Rollback File. This is the name of the rollback file. Creator. This is the creator of the change. This will be the login name that was used at the time of the configuration change. Date. This was the date of the change. Via. This was the method of access to the Base Station that was used to effect the change. On the right side of the window, is a text pad that provide details of the parameters and how they were changed. To perform the Rollback procedure then the User simply must highlight the relevant rollback file and then select the Load Command Menu Option below. 27 | P a g e Designed for Operators, by Operators Figure 16 Rollback Option If the User has made some configuration changes and they wish to Validate the changes then the User can select the Validate Command Menu Option. If the User, after making the relevant changes, selects the Validate option then if the intended changes are valid, then a window appears stating

"The configuration is ready to be committed" appears below. The User simply selects the OK prompt to proceed and navigate back to the Edit Mode. Figure 17 Validate Option The Commit Command Menu Option performs a crucial procedure in that it commits all configuration changes to the running database. When in Edit mode, the method of configuring and saving changes remains the same. A user may change any number of parameters but none of those changes will take effect until they are committed. 28 | P a g e Designed for Operators, by Operators Clicking the Commit Menu will result in one of the following actions If no configuration changes have been made, then a window appears stating "There is nothing to commit". The User simply selects the OK prompt to navigate back to the Edit Mode. If changes have been made, then a window appears stating "Do you want to commit your pending configuration changes?". The User simply selects the OK prompt to proceed. Figure 18 Commit Option Note: System configuration changes are first made to the running configuration database in memory. In order to make the change persistent and survive a restart, the Configuration-Write command must be used. When OK has been selected then a window appears stating "The configuration has been committed". The User simply selects the OK prompt to proceed and navigate back to the Edit mode. Unsaved configuration changes persist for only the current boot. If the Base station is rebooted then those changes will be lost if the configuration has not been saved. Several menus have two sets of parameters, these are defined as:

Configured Parameters. These are the most recently saved settings and are stored in the systems configuration database State Parameters. These are the readings of the actual state from the Base Station. State Parameters may be identical to Configured Parameters, or they may be committed but not propagated to the Base Station. After a reboot, both sets of parameters will be identical. 29 | P a g e Designed for Operators, by Operators The "Save Procedure" is to ensure that the running configuration is saved is:

1. At the Main Web GUI Interface Screen, select the Configuration Tab, select the configuration Main Menu Option then the write Main Menu Sub-Element. The User will have to click on the Perform Command Menu Option to copy the running configuration to the startup as below. Figure 19 Writing Running Configuration to Startup 2. A pop-up window indicating that the write was successful will be displayed. Note: Several configuration changes require that the Sector be rebooted. The only parameter requiring a complete Base Station reboot is enabling or disabling the ASN Gateway settings. The procedure to reboot a Base Station is as follows:

1. At the Main Web GUI Interface Screen, select the Configuration Tab, select the administration Main Menu option and then reboot Main Menu Sub-Element. The User will have to click on the Perform Command Menu Option to reboot the entire Base Station (Figure 20). 30 | P a g e Designed for Operators, by Operators Figure 20 Reboot Base Station 2. Upon clicking perform, the user must confirm the reboot operation by clicking Ok. After the reboot option has been performed then an appropriate window indicating a successful reboot execution will be displayed. The subsequent time for the Base Station to become operational is approximately 5 minutes. 3. The system will use the stored startup configuration after rebooting. Unwritten changes in the running configuration will be lost. 4. There are two reboot options under the administration Main Menu options including:

reboot. This option will reboot the Base Station reboot-sectors. This option will reboot the internal elements of the Base Station that are pertinent to the sector RF elements only. After the reboot sectors option has been performed then an appropriate window indicating a successful reboot execution will be displayed. The subsequent time for the Base Station to become operational is approximately 2 minutes. 31 | P a g e Designed for Operators, by Operators 3.4.2 Web GUI CLI Access Level The Mercury Quantum Base Station has a Command Line Interface (CLI) that can be accessed from within the Web GUI. To access the Web GUI CLI then at the Main Web GUI Interface Screen, select the Tools Tab. The User will be presented with a number of User tools as below. Figure 21 The Tools Tab Menu Options The User is presented with four Tools Command Menu Options. These are:

o Logs. This allows the User to display and hence view:

Accessories. The following protocols are made available to the User:

System log Alert log Audit log Ping Traceroute CPU Load required. o CLI. The User has access to the CLI and can execute all the CLI commands directly if o Users. This indicates all the Users that are currently connected to the Base Station. It also provides a means to physically "kick" them off their connection. In addition, a message board is provided thus enabling instant messages to be sent to the Users that are currently connected to the Base Station. 3.4.2.1 Tools Logs At the Main Web GUI Interface Screen, select the Tools Tab and then Logs. Figure 22 The Tools Tab Logs Menu 32 | P a g e Designed for Operators, by Operators To view the relevant Log, the User simply must select one of the 3 logs that are available to view. These logs are system, alert and audit logs. The three Tools logs are displayed below. Figure 23 The Tools Tab System Log Figure 24 The Tools Tab Alert Log 33 | P a g e Designed for Operators, by Operators Figure 25 The Tools Tab Audit Log 3.4.2.2 Tools Accessories At the Main Web GUI Interface Screen, select the Tools Tab and then Accessories as below. Figure 26 The Tools Tab Accessories Menu To perform the relevant protocol, the User must select the relevant option. To enable Ping or Traceroute, the User must:

1. Select the New button 2. A pop-up window will appear, this will enable the User to specify the host (Figure 27) 3. The User must now select the OK command button 4. The results will be displayed as below 34 | P a g e Designed for Operators, by Operators Figure 27 The Accessories Ping Command Figure 28 The Accessories Ping Results To examine the CPU Load, the User must select the CPU Load option. The User is presented with a display of the current CPU load. This will automatically be updated every 5 seconds and it will calculate the load averages over 1, 5 and 15 respectively (Figure 29). 35 | P a g e Designed for Operators, by Operators Figure 29 The Accessories CPU Load Results 3.4.2.3 Tools CLI At the Main Web GUI Interface Screen, select the Tools Tab and then CLI. The User is presented with a CLI screen (Figure 30). The User is free to enter all the available CLI options. Figure 30 The Tools Tab CLI 3.4.2.4 Tools Users At the Main Web GUI Interface Screen, select the Tools Tab and then Users. The User is presented with a screen that indicates the Users that are currently logged in to the Base Station and an instant messaging section to communicate with these Users (figure 37). 36 | P a g e Designed for Operators, by Operators Figure 31 The Tools Tab Users Connected to Base Station The User can also physically disconnect or "kick" off the User. The User must select the Kick command option. A message board is provided to enable instant messages to be sent to the Users that are currently connected to the Base Station. The User must enter the relevant message in the text box and then press Send. There is also the option to Clear history if required (refer to figure 38). Figure 32 The Tools Tab User Instant Messaging 37 | P a g e Designed for Operators, by Operators 3.5 Base Station Initial Configuration 3.5.1 System Architecture and Terminology In this section we will configure the minimal set of parameters that must be appropriately set prior to deployment. It is important to first clarify some terminology related to the system architectural model. In typical terminology, a Base Station is comprised of one or more co-located sectors. Each Mercury Quantum 6000 Base Station can be deployed either by itself, as a single sector Base station, or as one sector in a multi-sectored Base station. In either case, each Mercury Quantum 6000 must be fully configured and provisioned in its entirety, as if it was a standalone Base Station. The various Web Interface configuration parameters are organized into a hierarchical tree, and that some parameters are labeled as Base Station level and some sector level. Since the Quantum 6000 Base Station is really both a sector and a Base station, the differentiation is for organizational purposes, as well as compatibility with future multisector functionality or products. Additionally, a Base Station must be connected to subscriber devices on the air-interface side and to a Core Network on the backhaul side. As discussed previously, Mercury Quantum 6000 Base Stations can flexibly support a variety of core network configurations, ranging from a simple router

(Standalone Mode) to a full ASN-GW. It also has a built-in Radius client for connection to an external AAA server when in Standalone Mode. 3.5.2 Base Station Management Interface Access Parameters Table 10 lists the minimum set of management interface parameters that must be set prior to deployment. These parameters govern how an operator, administrator, or management system interfaces with and gains access to the Base Station. Before proceeding, please gather the information listed in the table. Factory default values are provided here as they are required for initial access. Parameter Description Factory Default Mgmt IP Address IP address used for all external Mgmt interfaces

(CLI / Web / SNMP). 192.168.1.10 Mgmt IP Netmask Mgmt interface IP netmask 255.255.255.0 Mgmt Default Gateway Mgmt interface default gateway 192.168.1.254 Hostname String name assigned to the Base Station. quantum-bs Admin User Password Unique password for default admin admin123 Table 10 Base Station Management Interface and Access Parameters 38 | P a g e Designed for Operators, by Operators To perform the initial configuration of the Base Station, it is recommended to configure the Management Interface Parameters via accessing through the Base Station Console Port. To complete this section, you will need the data in Table 10. If the management IP settings are "unknown" then the Base Station can only be accessed via its Console port (refer to section 3.3.1). Once the Base Station has been accessed, its management IP settings can be reset using the procedure detailed in section 3.4. Even though the CLI may be accessed through the Ethernet ports, it is not the recommended method of changing the management interface parameters, as connectivity with the port will be lost immediately upon changing them. Log into the CLI (Section 3.3) and execute the commands as indicated to configure the Base Station access parameters. Text in brackets <> should be replaced with your configuration data to replace the default values from the table above. 1. At the quantum-bs> prompt, type enable. This will drop the User into the enable mode and the prompt will change from > to # (Figure 33). Figure 33 Initial Connection to CLI 2. At the quantum-bs# prompt type configure terminal. The prompt will now indicate that the User is now in config mode and it will display the current Base Station time (Figure 34). 39 | P a g e Designed for Operators, by Operators Figure 34 Base Station CLI Time 3. To set the Management IP address, at the Quantum:quantum-bs(config) prompt type system interface ip address <Mgmt IP Address> netmask <Mgmt IP Netmask> e.g. system interface ip address 192.168.200.104 netmask 255.255.255.0 4. To set the default Gateway at the Quantum:quantum-bs(config) prompt type system interface ip default-gateway <Mgmt Default Gateway> e.g. system interface ip default-gateway 192.168.200.1 5. To exit, at the Quantum:quantum-bs(config) prompt type exit 6. The changes must be written to memory. At the quantum-bs# prompt type write memory

(Figure 35) Figure 35 Base Station CLI Initial Configuration 40 | P a g e Designed for Operators, by Operators 7. The IP address change to the Base station is immediate and does not require a reboot 8. Another useful command is the ability to change the default Quantum prompt. When the User is in the config mode, type system hostname <Hostname> (refer to Figure 36). The change must be written to memory and the Base Station must be rebooted 9. To change the username admin password, when the User is in the config mode, type Figure 36 Base Station CLI Hostname Change username admin password Password <new admin User Password>

The change must be written to memory (Figure 37). Figure 37 Base Station CLI Username Password Change 41 | P a g e Designed for Operators, by Operators 3.5.3 Base Station Configuration Parameters There are several key parameters that must be configured, as a minimum, prior to deployment and operation of the Base Station. Table 11 is a list of these parameters. In addition to these key parameters, there are several other parameters that can be configured on the Base Station. Such parameters can be left in their default configuration for "nominal" Base Station operation but there is the option to change based upon specific operating conditions. All parameters will be described in the following sections. One point to make, is that in the context of the Mercury Quantum 6600, as this is a single sector Base Station, the terms Sector and Base Station are effectively synonymous. This fact is represented within the Web GUI Interface using the number 1 at the appropriate menu option. The number 1 stands for Sector 1. The key Base Station parameters that must be configured are:

Configuration Item Description Base Station Mode Standalone Local Mode(default) or ASN Gateway Mode ASN Gateway IP Address IP Address of the ASN-GW (ASN-GW Mode only) Configuration Item Description Base Station Radius IP Address IP Address of the Radius Server (Standalone Mode only) Base Station Radius Port Radius Server Port (Standalone Mode only) Base Station Radius Secret Radius string secret (Standalone Mode only) Sector IP Address IP Address of the sectors datapath interface Sector IP Netmask Netmask of the sectors datapath interface Sector Default Gateway Default gateway of the sectors datapath interface Sector BS-ID Sector CS Type Base Station ID of the sector. In 6 Byte format like MAC Address format Convergence sub-layer type of the sector: Ethernet CS (default) or IPv4 CS 42 | P a g e Designed for Operators, by Operators Sector Radio Center Frequency Center frequency in kHz Sector Channel Bandwidth 3.5MHz, 5MHz, 7MHz, or 10 MHz (default) Sector Radio Power Output Preamble power output value per antenna (includes 3 dB preamble). Default: 23 dBm. Operations under FCC Part 96:

Power setting shall not exceed:

3.5 MHz: 31 dBm 5 MHz: 32 dBm 7 MHz: 32 dBm 10 MHz: 33 dBm Sector Radio Antenna Gain Antenna gain (dBi) Sector Radio Cable Loss Estimated external cable loss (dB) Sector Antenna TX Mode MIMO-A (default) or MIMO-AB Sector DL:UL Frame Ratio 26:21, 29:18, 32:15, 35:12 (default) in 5MHz and 10MHz 23:9, 21:12, 17:15 in 3.5 and 7MHz Table 11 Base Station Sector Configuration Data The Web GUI Interface will be used to configure the parameters that are required in Table 11. The starting point for all configurations is the Main Web GUI Interface Screen. The relevant parameters are distributed across several different menu options and hence screens and windows. Each of these options will be discussed in detail. After making the various configuration changes, the User will need to commit and save the changes. 3.5.3.1 Sector, General Settings At the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option and then general Main Menu Sub-Element. This will display the Sector Settings window. There are two basic groups to this Sector option. These are:

Sector Advanced Settings (configured) Sector Provisioning (configured) The User now has to navigate to the next level, therefore at the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, general Main Menu Sub-Element and then 1, this will display the key settings window. There are three distinct groups to this window

(Figure 38). 43 | P a g e Designed for Operators, by Operators Key Settings. This indicates the relevant sector, which as has been described in number 1. This is not a configurable parameter. A new key may be added in Edit Mode (Figure 39) Sector General Administration (configured). This is an indication whether the sector has been enabled for general administration. This parameter is not used. Use the Auto Transmit after Reset Mode parameter to disable the Sector from transmitting after the next reset. See Section Sector General Status. This indicates the current status of the following parameters. These parameters are non-configurable:

Figure 38 Sector General Options The Key Settings are defined by the following parameters (Figure 39):

Operational State. This indicates if the Sector is operational GPS State. This indicates the GPS status of the Sector. Restart Count. This is a cumulative count of the number of sector restarts since the Base Station Current Frame Number. Represents the count of WIMAX frames being allocated for was power cycled. transmission. 44 | P a g e Designed for Operators, by Operators the sector. currently in use. Number of MSS Subscribers. This is a count of the current Subscribers that are connected to Number of Service Flows. This is a count of the total number of Subscriber service flows that are Sector Software Version Status. Indicates the sector software version if there is a mismatch or if the sector is running from a recovery image. Running Software Version. This is the current running sector software version. Last Reset Reason. This provides a reason for the last sector reset. Figure 39 Sector Key Settings At the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, general Main Menu Sub-Element, 1 and then system. This will display the currently configured Sector General Provisioning window. There are a further two sub-elements to this window but only one is displayed. These sub-elements are:

system. This option enables the User to configure the parameters. state. This is a duplication of the windows and parameters that are contained within the system options. These are "read-only" screens and provide an indication as the current state or status of the system parameters. The status of the following parameters is displayed, and the User is free to configure as required (refer to (Figure 40). To edit and configure then the User must enter the Edit Mode (select Edit Private/Exclusive):

Base Station ID. This is the unique identifier that specifically identifies the Base Station to the Subscribers. It is recommended that this is changed to have a unique value in deployment. For inter-provider handover, please see the IEEE 802.16e guidelines. Cell ID. This is a numeric identifier that will define the cell (acceptable range is 0 to 31). 45 | P a g e Designed for Operators, by Operators Convergence Sublayer Type. This is the convergence sublayer type that is globally set for the sector. The available options are ETHERNET_CS and IPv4_CS. The default is ETHERNET_CS. Downlink Broadcast Rate. This is a User defined parameter that specifies the maximum \

Downlink (DL) rate in bits/second for the purposes of Ethernet Multicast, Ethernet Broadcast and IP broadcast traffic. This rate can be set up to 1Mbps and it uses QPSK modulation rate over the air. This parameter is only valid when operating in stand-alone mode. The default is 64000. Block DHCP Downlink Broadcasts. Selecting this option prevents rouge DHCP servers behind Subscriber Units from assigning IP addresses back to the network. This is primarily applicable for the Ethernet CS (Convergence Sublayer) mode of operation. By default this option is disabled. CPE to CPE Relaying (ETH CS). If this option is enabled, it would allow all traffic to flow between the two CPEs without the need for the frames to be sent back to the backhaul side. This is applicable only in Ethernet CS stand-alone mode of operation. Only unicast and ARP broadcast frames will be relayed. This is useful for allowing two remote offices or locations to communicate. Please note that latency will be double on communications and the maximum capacity will be determined by the lowest of the uplink modulation rates between Subscriber Units. CPE to CPE All Broadcasts (ETH CS). If this option is enabled, it would allow all broadcast traffic to be relayed between the two CPEs. This is useful if the application requires Ethernet Broadcast frames other than ARP to be relayed. Examples include video broadcasting using IPTV. This is applicable only in Ethernet CS stand-alone mode of operation when CPE to CPE relaying is enabled. Downlink ARP Override. Downlink ARP Unicast packets are retransmitted as ARP broadcast packets. Mode. This is the Base Station Mode of network operation and the available options are:

o standalone-local. Base Station operates in standalone mode where the users are local to the Base Station; CPE provisioning database is location and it is not connected to an ASN Gateway) o standalone-local-AAA. Base Station operates in standalone mode, uses AAA for provisioning of the CPEs and is not connected to an ASN Gateway. The AAA specifies the AC address of the CPE and the Client Profile ID that should be used by the CPE. The Client Profiles are configured in the Base Station and is must be maintained the same across all base station in a deployment served by the same AAA server o asn-gateway. ASN Gateway is used for all provisioning of the CPEs, there will be a GRE tunnel created between the Sector and the ASN Gateway and all data traffic will be sent out from the ASN Gateway (aggregator) and AAA provisioning 46 | P a g e Designed for Operators, by Operators Figure 40 Sector General Provisioning Parameters At the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, general Main Menu Sub-Element, 1, system and then ip and this will display the current configuration of the Sector External IP Address (Figure 41). This is a different IP address from the one configured on the Base Station and is recommended to be configured within the same IP subnet as the Base station IP pointing to the same default gateway. This IP address is used for:

o Generation of AAA Authentication requests (if sector security is enabled) when o As the Source for all data traffic (towards the network) when operating in IP CS Stand operating in Stand Alone mode. Alone mode. o As the GRE tunnel source for all data traffic when operating in ASN Gateway mode. Address. This is the IP address Netmask. This is the netmask associated with the IP address Gateway. This is the default gateway. 47 | P a g e Designed for Operators, by Operators Figure 41 Sector External IP Address To edit the parameter, the User must enter the Edit Mode (select Edit Private or Edit Exclusive). Once in the Edit Mode the User must select the notepad icon and this will provide an option to edit the IP address (Figure 42). Figure 42 Sector External IP Address Configuration 48 | P a g e Designed for Operators, by Operators At the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, general Main Menu Sub-Element, 1, state and then system. This provides another view that will display the current configuration of the Sector. Even if the User enters the Edit Mode (select Edit Private or Edit Exclusive), no parameters are made available for editing. The options to configure these parameters are contained under the system and then base station options. This shows the currently used parameters by the Sector. Configuration is performed at the system level (Figure 43 and Figure 44). Sector External ASN-Gateway (state). Management Vlan Sector General Provisioning Sector External Radius Server Settings Figure 43 Management Vlan Settings (state) 49 | P a g e Designed for Operators, by Operators Figure 44 Sector General Provisioning and External Radius Server State At the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, general Main Menu Sub-Element, 1, state, system and then ip. This provides another view that will display the current External IP Address of the Sector. Even if the User enters the Edit Mode (select Edit Private or Edit Exclusive), no parameters are made available for editing. There following information is displayed in Figure 45. Sector External IP Address Netmask Gateway 50 | P a g e Designed for Operators, by Operators Figure 45 Sector External IP Address Settings (state) 3.5.3.2 Sector, Advanced Settings At Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, advanced Main Menu Sub-Element and then 1, this will display the key settings window. There are two further sub-elements to this window but the information is only displayed when the actual element is selected. These further sub-elements are (refer to Figure 46):

wimax. These are the parameters that can be configured as defined by the WiMAX 802.16e specification radio. These are the parameters that can be configured as part of the specific Base Station radio transmission configuration security. Parameters for the authorization key settings Figure 46 Sector Advanced Settings 51 | P a g e Designed for Operators, by Operators To view the Sector WIMAX Settings, at the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, advanced Main Menu Sub-Element, 1, and then wimax. The display is split into two main sections. These sections do not fit onto one screen and therefore the User has to scroll down to view etc (refer to Figure 47 and Figure 48). Sector WIMAX Settings (configured). These are the parameters that the User can Edit Sector WIMAX Settings (state). These are the currently used configuration values of the parameters Figure 47 Sector WiMAX Settings (state) 52 | P a g e Designed for Operators, by Operators Figure 48 Sector State WiMAX Settings If the User wants to configure any of the WiMAX parameters, then they must enter the Edit Mode (select Edit Private or Edit Exclusive) and edit as necessary. The methods to Edit the parameters will be offered via a drop-down menu of choices, enabling of a check box or editing of a notepad icon. After making the various configuration changes, the User will need to "Commit" and "Save" the changes. 53 | P a g e Designed for Operators, by Operators Figure 49 Sector WiMAX Settings Configuration The Sector WIMAX Settings parameters that the User can configure are defined below:

Maximum Uplink Rate. This parameter provides the means to globally fix the maximum modulation rate in the Uplink direction (defined as Subscriber to Base Station). If the User wants to dynamically adapt the rate to the maximum, then the default value of QAM64_5/6 can be left unchanged. Refer to Appendix A for an explanation of how the maximum modulation rate, defined as MCS Rate, effectively caps the system data throughput. If the User wants to physically cap the rate and hence cap the throughput, they are free to select from the following MCS rates:

o QAM64_5/6 o QAM64_3/4 o QAM64_2/3 o QAM64_1/2 o QAM16_3/4 o QAM16_1/2 o QPSK_3/4 o QPSK_1/2 54 | P a g e Designed for Operators, by Operators Maximum Downlink Rate. This parameter provides the means to globally fix the maximum modulation rate in the Downlink direction (defined as Base Station to Subscriber). The default is QAM64_5/6 and the same options as maximum uplink rate parameter are available. Antenna TX Mode. This the option to define the Smart Antenna Capabilities that were described in section 2.3.2.3. The default setting is MIMO-A and the available options are:

o MIMO-AB o MIMO-A. In MIMO-AB mode, if the Subscriber Unit indicates that the channel conditions allow the operation of MIMO-B (usually in high multipath conditions with very strong downlink signal and CINR) the Base station will dynamically assign the CPE to operate in MIMO-B mode doubling the capacity on the downlink direction. Auto Power Control. The transmit power of a Subscriber is controlled via automatic algorithms in the Base Station. This control of the transmit power ensures optimum performance. The default is open-loop and the available options are:

o open-loop. In the case of an open loop algorithm, the Base Station sends a signal to the Subscriber of the required settings and the Subscriber adjusts its transmit power dynamically. o closed-loop. In the case of closed loop, the Base Station controls the Subscriber transmit power settings with a full measurements loop. Auto Transmit After Reset Mode. When this is enabled the Base Station will automatically start transmitting upon a power cycle. If this is disabled, then the User will have to manually start the transmission. By default, this is disabled. The user needs to enable this after connecting the antenna, setting the frequency and TX power level. Channel Bandwidth. This is the current channel bandwidth of the radio transmission. The default is 10MHz and the options are:

o 10MHz o 7MHz o 5MHz o 3.5MHz DCD Interval. This is the internal with which WiMAX 802.16e DCD messages are transmitted and is defined in milliseconds. The default is 1000 (1 second) and the available range is 15 up to 10000. Default Provisioning Enabled. The user has the choice to enable or disable this feature. If this is enabled, then any non-explicitly provisioned CPE will be assigned the Default Client Profile. If this is disabled and the CPE is not explicitly provisioned, the CPE will remain wirelessly connected but will not be assigned any data service flows which will cause no data traffic to pass through. Downlink/Uplink Frame Ratio. This is the ratio of downlink to uplink frame symbols, refer to Appendix A and how this affects data throughput. The default option is 35:12. Maximum Distance. This is the maximum distance, defined in km, that a CPE can communicate with a Base Station. The default is set to 11Km and the user can select in the range 1 to 58Km. Increasing the value above 11km will lower the maximum achievable downlink performance. Configuring a distance greater than 28Km will cause a donut effect, where the area of coverage will be between the outer and inner radius. The outer radius will be the maximum distance configured and the inner radius will be the maximum distance 55 | P a g e Designed for Operators, by Operators configured minus 28. Example 1: If the Maximum distance is set to 13Km, the area of coverage will be between the Base Station up to 13Km. Example 2: If the Maximum distance is set to 44Km, the area of coverage will be between 16Km and 44Km. We recommend configuring this value appropriately such that the desired area is covered. When applying the change, a popup will appear and you will be required to commit (Figure 50). Noise and Interference Settings. The default is 35. NI is defined as per the IEEE 802.16-e as the noise per tone in 0.5 db steps above the -150 dBm, where 0 is -150dbm and 35 is -

132.5dbm per tone. This value represents the noise level per tone at the receiver of the Base station which gets advertised and is used by the CPEs to determine their uplink TX power when operating in open loop power control. Auto Noise Level Adjustment Support. Enables the automatic dynamic adjustment of NI and internal settings with respect to the measured noise level on the channel. The Noise measurement values can be seen in the radio tab. DL ECINR Report Support. Specifies the mode of CINR reporting to be provided from the CPEs. Default is enabled (ECINR). Disabling CINR reporting should be done only in case of older CPE revisions that do not support ECINR reporting. UCD Interval. This is WiMAX 802.16e UCD Interval value and it is to be defined in milliseconds. Interval defined in milliseconds. The default is 1000 (1 second) and the available range is 15 up to 10000. 5MHz Large Map Support Available and applicable only in case of 5MHz channel bandwidth setting. Extends the MAP size and supports larger number of bursts per frame. Recommended to be enabled in case of large number of CPEs and when using combined data + voice. To view the Radio Settings, at the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, advanced Main Menu Sub-Element, 1, and then radio. The display is split into three main grouping sections. These sections do not fit onto one screen and therefore the User must scroll down to view etc (refer to Figure 51 and Figure 52). Radio Settings (configured). These are the parameters that the User can Edit Radio Settings (state). These are the current configurations values of the parameters Noise and Interference Measurements (status). These are the current configurations values of the parameters. The Noise level is represented in 3 different measurement units Figure 50 Distance Setting Warning Pop-up 56 | P a g e Designed for Operators, by Operators Figure 51 Sector Radio Configured Settings Figure 52 Sector Radio State Settings 57 | P a g e Designed for Operators, by Operators If the User wants to configure any of the Radio parameters, then they must enter the Edit Mode (select Edit Private or Edit Exclusive) and edit as necessary. The methods to edit the parameters will be offered via editing of a notepad icon (Figure 53). Figure 53 Sector Radio Settings Configuration After making the various configuration changes, the User will need to "Commit" and "Save" the changes. The Radio Settings parameters that the User can configure are defined below:

Antenna Gain. This is the gain (in dB) for the Antenna that the Base Station is connected to. The default setting is 0, however this should be set exactly as the antenna that is used. Setting an incorrect value may cause the degraded performance. Cable Loss. This is a loss of the cable (in dBs) from the Base Station to the Antenna. The default setting is 0 but needs to be set according to the loss of the cable used. Setting an incorrect value may cause the degraded performance. Center Frequency. This is the center frequency of the Base Station and it must match with what is configured on the Subscribers. The default setting is relative to the frequency range of operation of the Base Station. To re-configure, the center frequency has to be input in KHz. Power Output. This is the radio output power in dBm. The default setting is relative to the frequency range of operation of the Base Station. The User must ensure that the maximum output power is defined as described in section 2.3.2.2. Contention Based Mode must be enabled on the Radios to support the upper 25 MHz of the 3.65 GHz US band. The diagram below provides an example of utilizing part of the upper 25 MHz for a 7 MHz channel width. In this case Contention-Based Mode must be enabled. To utilize WiMAX Contention Based Mode, at the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, advanced Main Menu Sub-Element, 1, and then radio and contention-based mode. The display is split into two grouping sections. These sections do not fit onto one screen and therefore the User must scroll down to view etc. (Figure 54). 58 | P a g e Designed for Operators, by Operators Mode (enable/disable). Allows the feature to be enabled or disabled Carrier Sense Threshold. Set to -85.0 dBm by default. Any signals detected beyond this threshold Carrier BackOff Frame. Number of frames to wait for transmission when an interfering carrier is Carrier Sense Resume Frame. Number of frames to resume listening when an interfering carrier will be ignored detected is detected. Default is 752. Figure 54 Contention Based Mode Omniwave may be enabled on the radio level to support a 3x2x2 configuration. To utilize Omniwave, at the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, advanced Main Menu Sub-Element, 1, and then radio and omniwave. Mode (enable/disable). Allows the feature to be enabled or disabled Status. Current configuration (enabled or disabled) 59 | P a g e Designed for Operators, by Operators Figure 55 OmniWave Settings To view the Security Settings, at the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option, advanced Main Menu Sub-Element, 1, and then security. The display is split into two main grouping sections (Figure 56). Security Settings (configured). These are the parameters that the User can Edit. Security Settings (state). These are the current configurations values of the parameters. Figure 56 Sector Security Settings 60 | P a g e Designed for Operators, by Operators If the User wants to configure any of the Security parameters, then they must enter the Edit Mode

(select Edit Private or Edit Exclusive) and edit as necessary. The methods to Edit the parameters will be offered via an enabling of a check box or editing of a notepad icon (Figure 57). Figure 57 Sector Security Settings Configuration After making the various configuration changes, the User will need to "Commit" and "Save" the changes. The Security Settings parameters that the User can configure are defined below:

AK Lifetime. This stands for Authorization Key lifetime. It is used when authentication and encryption is enabled. The key is periodically re-generated by the Base Station after a request is received from a Subscriber following expiration of this timeout. The default setting is 6048000 and it is not recommended to change this value. Enabled. This indicates whether the Security Feature has been enabled or not. TEK Lifetime. This stands for Traffic Encryption Key lifetime. The key is used when authentication and encryption is enabled. It is periodically re-generated by the Base Station after a request is received from a Subscriber following expiration of this timeout. It is not recommended to change the default value. To view the Action Options, at the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option and the action Main Menu Sub Element and Key Index 1. 61 | P a g e Designed for Operators, by Operators The action options are as follows:

Figure 58 Sector Action Menu Subscriber Station. Allows user to perform abort ranging, deregister or reset on a CPE Reboot. Will perform a reboot of the entire sector Start Noise Measurement. Will put the sector in a special mode to measure noise and interference Start Radio Transmit. Will revert the sector back in the radio transmit mode Figure 59 Abort Ranging Request To perform the Subscriber-Station (or CPE) Action Options, at the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option and the action Main Menu Sub-Element and Key Index 1 followed by subscriber-station and one of the options below:

62 | P a g e Designed for Operators, by Operators abort. Specify a CPE via its MAC Address. Hit Perform and the current ranging operation will cease, and the CPE will attempt to re-enter the network. Refer to Figure 60. deregister. Specify a CPE via its MAC Address. Hit Perform and the current CPE will be deregistered from the sector. Refer to Figure 61. reset. Will put the sector in a special mode to measure noise and interference (Figure 61) Figure 60 De-register CPE Figure 61 Reset CPE Action 63 | P a g e Designed for Operators, by Operators To perform the Sector Action Options, at the Main Web GUI Interface Screen select the Configuration Tab, select sector Main Menu Option and the action Main Menu Sub Element and Key Index 1 followed by subscriber-station and one of the options below:

Figure 62 Reboot Sector Action Reboot. Hit Perform and the current sector will be rebooted (Figure 62) Start-Noise Measurement. Hit Perform and the action will put the sector in a special mode to measure noise and interference (Figure 63), results will be available after a short time Start-radio-transmit. Will put the sector in a special mode to measure noise and interference

(Figure 64) Figure 63 Start Noise Measurement 64 | P a g e Designed for Operators, by Operators Figure 64 Radio Transmit Sector Action 3.5.3.3 System Settings At the Main Web GUI Interface Screen select the Configuration Tab and then select system Main Menu Option. This will display the System Settings window. The system menu option has three further sub elements, these being (Figure 65):

Base-Station. This details various Base Station parameters Reset. This is a means for the User to default the Base Station back to its "out of the box"

initial configuration values or default configurations Interface. 65 | P a g e Designed for Operators, by Operators Figure 65 System Settings The System display is split into seven main grouping sections. These sections do not fit onto one screen and therefore the User must scroll down to view etc. An indication as to whether there are any User configurable parameters included in the grouping is provided. If the User wants to configure any of the parameters, then they must enter the Edit Mode (select Edit Private or Edit Exclusive) and edit as necessary. The methods to Edit the parameters will be offered via a drop-down menu of choices, an enabling of a check box or editing of a notepad icon. The parameters that the User can configure and the relevant grouping section that they belong to are outlined below. After making the various configuration changes, the User will need to "Commit" and

"Save" the changes. System Console Settings (Figure 66) o Baudrate. This is the baud rate that is configured for serial connection via the Base Station Console Port. The default is 38400 and the available options are 115200, 57600, 38400, 19200 and 9600. System Miscellaneous Settings o Hostname. This is a free format text field for the User to specify a hostname. o Led-enabled. The User can enable or disable the LED indicators for the Base Station. 66 | P a g e Designed for Operators, by Operators System General Settings o Name. This is a free format text field for the User to specify a name to the Base o Location. This is a free format text field for the User to specify a location to the Base o Contact. This is a free format text field for the User to specify a contact for the Base Station. Station. Station. o Uptime. Figure 66 System Console Settings At the Main Web GUI Interface Screen select the Configuration Tab, select system Main Menu Option and then the base-station Main Menu Sub-Element. This will display the External ASN-Gateway Settings window (Figure 67). 67 | P a g e Designed for Operators, by Operators Figure 67 System External ASN Gateway Settings The System display is split into several grouping sections. These sections do not fit onto one screen and therefore the User must scroll down to view etc. An indication as to whether there are any User configurable parameters included in the grouping is provided. If the User wants to configure any of the parameters, then they must enter the Edit Mode (select Edit Private or Edit Exclusive) and edit as necessary. The methods to Edit the parameters will be offered via a drop-down menu of choices or editing of a notepad icon. External ASN-Gateway Settings. These are the settings for any external ASN Gateway that is connected to the Base Station. Base-Station Settings. These are the settings for the Base Station. External Radius Server Settings. These are the settings for the external Radius Server, if configured. The parameters that the User can configure and the relevant grouping section that they belong are outlined below. After making the various configuration changes, the User will need to "Commit" and

"Save" the changes. External ASN-Gateway Settings. o ASN-Gateway IP Address. This is the IP address of the ASN Gateway that the Base Station is connected to. An IP address has to be provided if the Base Station has been configured to operate in ASN Gateway mode. 68 | P a g e Designed for Operators, by Operators o ASN-Gateway Port Number. This is the Port Number that the Base Station use to communicate with the ASN Gateway. o ASN-Gateway Vendor ID. This User has the option to select and store the vendor of the ASN Gateway. The current options are Wichorus and Cisco. o ASN-Gateway NWG Version. This User has the option to select and store the protocol used to communicate with the ASN Gateway. The current options are v1.2 and v1.3. Base-Station Settings o Group-id. This is a free format text field. o Group-descr. This is a free format text field. o Mode. This defines the mode of operation for the Base Station. The default option is standalone-local, and the available options are asngateway and standalone-AAA-

prov. External Radius Server Settings (Figure 69) o Radius Server IP Address. This is the IP Address of the AAA server used for authentication/encryption purposes and provisioning when set to local-AAA provisioning. Applicable only in case of Stand-Alone Mode. o Radius Server Port Number. This is the Port Number that the Base Station use to communicate with the Radius Server. Applicable only in standalone mode. o Secret. This is the radius "secret" that is shared between the Base Station and the Radius Server. o AAA Provision Realm. This is an optional parameter that can be used in case the base station operates in standalone-AAA-prov mode, where the base station will append the specified realm on every provisioning request to the server. This can simplify the configuration on the AAA side in cases where the MAC Address of the CPE is already used for authentication purposes. Default is empty, which means that the AAA provisioning request will contain only the MAC Address of the CPE. Figure 68 External Radius Server Settings 69 | P a g e Designed for Operators, by Operators The system, base-station menu option has two further sub-elements, handover, neighbor and wimax learning. handover. This is where triggers are set for handover operation. By default, there are no triggers. For handover operation at least two triggers must be set, one for scanning and one for handover. This information is incorporated into DCD message sent by the base station. This may be left unconfigured if no handover is desired. For each trigger following needs to be configured (Figure 70):

o Trigger Index: A user defined unique number between 1-8. o Average Duration: Trigger averaging duration is the time measured in number of frames over which the metric measurements are averaged. o Trigger Type: This defines trigger metric, CINR or RSSI o Trigger Function: This parameter specifies the function for the trigger type chosen earlier. Select one from the dropdown menu. o Trigger Action: This parameter specifies the action, scanning (MOB_SCAN_REQ) or handover (RSP_MOB_MSHO_REQ), to take when trigger criteria is met. Select from the dropdown menu. o Trigger Value: This parameter specifies the value for corresponding to the trigger type and function selected above. Figure 69 Base Station Handover 70 | P a g e Designed for Operators, by Operators Figure 70 System Handover Trigger Setting Neighbor. This is the place to configure information about neighbor Base Stations (Figure 71). This is required for handover operation. The neighbor list is specified in Figure 72. This can be left unconfigured if no handover is required. For each neighbor, the following needs to be configured:

o BS id: This is the BSID of neighbor bs. Use upper case letters only. BSID of the neighboring base stations should have same operator id as the serving base station, i.e. the upper 6 bytes should be same. IP Address: This is the IP address of the neighbor base station. o o Preamble Index: This is the preamble-index (or Cell-ID parameter) of the neighbor base station. o BS Index: This is a user defined number in the range of 1-254. The index of 255 has a special meaning. When this index is set to 255 then the neighbor will be considered as a non-Mercury base station, and Mercury base station will unconditionally accept the handover request. No backbone communication will take place. o BS Frequency: This is the frequency of the neighbor base station in KHz. 71 | P a g e Designed for Operators, by Operators Figure 71 Base Station Neighbor Settings Figure 72 Base Station Neighbor List Wimax learning. This learning table indicates the devices on the wireless side and their association with a CPE. 72 | P a g e Designed for Operators, by Operators Figure 73 WiMAX Learning Table The parameters in the learning table are as follows:

o Sector. Represents the Sector ID on which the device was learned. For Quantum 6600 this is always 1. o MAC. Mac Address of the device learned in the bridge learning table o DEV MAC. The MAC Address of the device(s) behind the CPE. This will be the MAC address of the mobile station (MS) if it operates in NAT Mode or is USB type. There can be up to 10 MAC addresses behind a CPE if the Base Station operates in Bridge Mode Stand Alone. In case the Base Station operates in IP CS Stand Alone mode the MAC address will always be the one of the MS. Each IP should be displayed as a separate entry. IP Address. The IP Addresses of the devices behind the CPE. This is relevant only in case the base station operates in IP CS Stand Alone mode. In other cases, this will not return any value. In case the CPE operates in NAT/Router mode or is of USB type this will be usually a single entry with the IP Address. o o Static. If the entry is manually provisioned or if the IP Address was obtained through DHCP Server. This is relevant only for IP CS Stand Alone mode. o Ageing. Represent the time in seconds of the device since the last frame was received originating with the matching source MAC Address. Aging is not applicable to IP CS Stand along mode, where there is IP Address learned No Ageing. 73 | P a g e Designed for Operators, by Operators 3.5.3.4 Resetting System to Factory Defaults There are two options to reset the system back to default configuration defaultConfiguration: clears the configuration but retains the IP addresses and Management VLAN configuration. factoryDefault: restores the system back to factory defaults including IP addresses. At the Main Web GUI Interface Screen select the Configuration Tab, select system Main Menu Option, reset Main Menu Sub-Element and then defaultConfiguration OR factoryDefault. This provides the User with a reset system to factory defaults option (Figure 74). The User must select Perform Command Menu Option to erase the startup configuration and reboot the system. Afterwards the system will come up with the factory default configuration. Figure 74 System Reset to Default Option 3.5.3.5 Resetting Interface to Factory Defaults At the Main Web GUI Interface Screen select the Configuration Tab, select system Main Menu Option, reset Main Menu Sub-Element and then interface. This provides the User with the options to configure the System Management Static IP Address and Management VLAN (Figure 75). If the User wants to configure any of the parameters, then they must enter the Edit Mode (select Edit Private or Edit Exclusive) and edit as necessary. The methods to Edit the parameters will be offered via editing of a notepad icon. 74 | P a g e Designed for Operators, by Operators The parameters to configure for the Base Station Static Management IP Address are:

Address Netmask Default Gateway VLAN Enabled VLAN ID VLAN Priority Figure 75 System Management Static IP Address and VLAN 3.5.3.6 GPS Settings The use of a GPS for air frame synchronization is mandatory if more than one Base Station is installed in a geographical area where potential radio transmissions could interfere with one another. GPS is enabled or disabled via the GPS option. At the Main Web GUI Interface Screen select the Configuration Tab and then select the gps Main Menu Option. This will display the GPS Settings and Status window (Figure 76). The gps Main Menu Option has no further sub-elements. 75 | P a g e Designed for Operators, by Operators Figure 76 GPS Settings and Configuration The GPS Settings display is split into one main group sections. An indication as to whether there are any User configurable parameters included in the group is provided. If the User wants to configure any of the parameters, then they must enter the Edit Mode (select Edit Private or Edit Exclusive) and edit as necessary. The methods to Edit the parameters will be offered via an enabling of a check box or editing of a notepad icon. A GPS antenna MUST be connected to the Base Station before setting GPS Admin Status to Enabled The GPS Settings and Status window contains:

GPS Admin Status. This is an indication of the GPS Admin Status. The options are enabled and disabled with disabled as the default. Sync Recovery Timeout Interval. The Base Station has a Sync Recovery feature, whereby the Base Station Radio is automatically reset if GPS sync is lost for more than a specified timeout period. The timeout period (in seconds) is specified via the Sync Recovery Timeout Interval parameter. The default value is 1800 seconds. Latitude (degrees). This is the latitude location of the GPS receiver. This is not a User configurable parameter. Longitude (degrees). This is the longitude location of the GPS receiver. This is not a User configurable parameter. State. This is an indication of the state of the GPS receiver. This is not a User configurable parameter. 76 | P a g e Designed for Operators, by Operators Sync Loss Occurrences since Last Reboot. This is a cumulative count of the number of GPS sync losses since the Base Station was last reset. This is not a User configurable parameter. Sync Loss Recoveries since Last Reboot. This is a cumulative count of the number of GPS sync recoveries since the Base Station was last reset. This is not a User configurable parameter. The GPS will be in one of the states below from startup and until it is operational and providing synchronization to the base station. Offline. The 1 PPS from the satellite signal is not detected, so basic synch lock has not occurred. This can be also seen as there should not be any coordinates if the GPS is offline INIT: GPS state which dictates whether the BASE STATION will start transmission if the GPS is enabled. o o o o INIT-Initializing INIT-Tracking-1-OSO INIT-Tracking-2-STO-Init INIT-Tracking-3-STO-Start UP: GPS is operational (up). o UP-Tracking-Done. Base Station will begin transmission o UP-Tracking-Hist. Last GPS state indicating a steady state. o UP-Holdoff o UP-ReAcquire o UP-Retrack DOWN: GPS is not operational (down). o DOWN-Unreliable o DOWN-Recovery 3.5.3.7 Time Settings It is important that the Base Station maintain an accurate date and time so that system logs are aligned and may be correlated with other network activity and trouble reports. Although the date and time must be initially set by the user, the Base Station supports the Network Time Protocol (NTP) to maintain its accuracy. The use of NTP is optional At the Main Web GUI Interface Screen select the Configuration Tab and then select the time Main Menu Option. This will display the System Date and Time Settings and the display is split into one main group section (Figure 77). In addition, the time menu option has a single further sub-element. The further sub element is:

ntp. These are the NTP time settings. 77 | P a g e Designed for Operators, by Operators Figure 77 Time Settings An indication as to whether there are any User configurable parameters included in the group is provided. If the User wants to configure any of the parameters, then they must enter the Edit Mode

(select Edit Private or Edit Exclusive) and edit as necessary. The methods to Edit the parameters will be offered via drop down menu. The System Date and Time Settings window contains:

System Time and Date. This is an indication of current date and time. This is not a User configurable parameter. Timezone. This is an indication of the timezone. The Use is free to select their respective timezone and multiple options are available via the dropdown menu. To view the Network Time Protocol Settings then at the Main Web GUI Interface Screen, select the Configuration Tab, select time Main Menu Option and then ntp Main Menu Sub-Element. The display is split into two main grouping sections. Network Time Protocol Settings. This is an indication as to whether NTP has been enabled. The options are enabled and disabled with disabled as the default. NTP Server Settings. This is an indication of the IP address, the NTP protocol version and whether the server is enabled of the NTP server. If the User wants to configure the NTP settings then they can edit, delete or add another NTP server. If the User enters the Edit mode for this parameter, then a further sub element with two more windows appear and the User can edit as required. The User can configure:

Ip-address. This is the IP Address of the NTP Server. o o Version. This is the protocol version of the NTP Server. o Enabled. This indicates whether the NTP Server is enabled. 78 | P a g e Designed for Operators, by Operators Figure 78 Time NTP Server Settings Figure 79 Time NTP Server Configuration 79 | P a g e Designed for Operators, by Operators To view the current System Time and Date Settings then at the Main Web GUI Interface Screen select the Configuration Tab, select time Main Menu Option and then the set Main Menu Sub-Element. The display is split into two main grouping sections. (Figure 80). Set System Time and Date. This is a text box that contains the Perform Command Menu Option. Time and Date. The User is free to configure the Time and Date. The dialog time is specified in 24-hour format and includes milliseconds (Ms), which may simply be set to 0. TzH is the time zone hours offset from Coordinated Universal Time (UTC) and is between -23 and +23. TzM is the time zone minutes offset from Coordinated Universal Time (UTC) and is between 0 and 59. Once these parameters have been configured, the User must select the Perform Command Menu Option for the changes to be affected. Figure 80 Time NTP Server System Set To view the NTP Time/Date Synchronization then at the Main Web GUI Interface Screen select the Configuration Tab, select time Main Menu Option, then ntp Main Menu SubElement and then ntpdate. The display is split into two main grouping sections (refer to Figure 81). NTP Time/Date Synchronization. This command will perform a one-time synchronization to the selected NTP server. To apply the User simply needs to select the Perform command button. NTP Time/Date Synchronization. The User can configure the NTP Server IP address to perform the one-time synchronization with. 80 | P a g e Designed for Operators, by Operators Figure 81 Time NTP Server Synchronization Update 3.5.3.8 Telnet Settings At the Main Web GUI Interface Screen select the Configuration Tab and select the telnet Main Menu Option. This will display the /telnet/server Settings and the display is split into one main group section

(Figure 82). There is no further sub-element associated with this option. The /telnet/server settings are:

Enabled. This indicates whether the telnet option has been enabled or not. This is a User configurable value that is edited via a check box. 81 | P a g e Designed for Operators, by Operators Figure 82 Telnet Server Enabled 3.5.3.9 Web Server Settings At the Main Web GUI Interface Screen select the Configuration Tab and select the web Main Menu Option. This will display the web Settings and the display is split into two main grouping sections

(Figure 83). The main grouping sections are:

Web Server HTTP Support. This indicates the Base Station HTTP options. The configuration options are:

o Enabled. This indicates whether the HTTP Support option has been enabled or not. This is a User configurable value that is edited via a check box. The default configuration is disabled. o Port Number. This is the port number that the HTTP Server inside the Base Station will listen on and accept connections. Web Server HTTPS Support. This indicates the Base Station HTTP options. The configuration options are:

o Enabled. This indicates whether the HTTPS Support option has been enabled or not. This is a User configurable value that is edited via a check box. The default option is enabled. o Port Number. This is the port number that the HTTPS Server inside the Base Station will listen on and accept connections. 82 | P a g e Designed for Operators, by Operators Figure 83 Web Server HTTP Support 3.5.3.10 Configuration Settings All the Base Station configuration parameters are contained and stored local on the Base Station in flash memory, via a number of configuration files. The User has the complete control to perform a variety of functions such as copy, move, delete and restore etc. on these files. This presents a User with an option, in the event that they would like to reconfigure a Base Station or the Subscriber CPE profiles they can copy and export a configuration file which can then easily be edited and downloaded back onto the Base Station. This is an alternative approach to the screen by screen configuration method that is detailed in this User Guide. At the Main Web GUI Interface Screen select the Configuration Tab and select the configuration Main Menu Option. This will display the configuration Settings and the display is split into two main grouping sections (Figure 76). There are ten Main Menu Sub-Elements associated with the configuration Main Menu Option. The main grouping sections are:

Configuration File Operation Status. This indicates the Configuration File operation status when the User is downloading or uploading a configuration file. The parameters that are displayed are as follows. o State. This indicates execution state of the configuration command. It is not a configurable parameter and simply states the current status, for example Idle. 83 | P a g e Designed for Operators, by Operators o Download Progress. This provides an indication of the completion percentage of the configuration file that is being downloaded. This is not a configurable parameter. o Upload Progress. This provides an indication of the completion percentage of the configuration file that is being uploaded. This is not a configurable parameter. Configuration Files. This is a list of the configuration files on the Base Station. There is no configurable parameters for these files and the information that is presented for each file is:

o Name. o Size. The size of the file is in bytes. o Modified. This is the date and time that the file was last modified. The ten Main Menu Sub-Elements are essentially the actions that can be performed on a configuration file. The User is not required to be in Edit Mode to perform any of these actions, the action is presented to them directly at each Main Menu Sub-Element option. These are:

Copy Move Delete Export Import Write Restore Download Upload Files The Main Menu Sub-Elements will be examined in detail. The same display elements are presented when the User navigates to each of these 10 Main Menu Sub-Elements. The display is split into two main grouping sections (Figure 84). The top grouping section provides a description and instructions of the action. The bottom grouping section provides the mechanism to perform the action. Another common theme throughout the Main Menu Sub-Element is the ability to select a configuration file for an action. The relevant files are presented to the User via a drop-down menu or the files are listed under the files Main Menu Sub-Element option. To view the files then at the Main Web GUI Interface Screen, select the Configuration Tab and select the files Main Menu Option. This will display all the relevant files. The explanation for each file is:

.cnf (configuration) files are created by the export command and can only be read by the import command. The data in the file is saved as a series of CLI commands. This file is in ASCII format and can be edited within a text editor. o profile.cnf file is the Base Station configuration file o cpe.cnf file is the Subscriber CPE configuration file 84 | P a g e Designed for Operators, by Operators Figure 84 Configuration Settings At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the copy Main Menu Sub-Element. This will display window to copy a configuration file. The procedure to copy a file is:

Figure 85 Configuration Copy Settings 1. Select the file to be copied from the drop-down menu of the Existing File Name field (Figure 2. Enter the copied file name in the Copied File Name field. 85 | P a g e 85). Designed for Operators, by Operators 3. Enable the Force field if the User wants to overwrite an existing file on the Base Station. 4. The User must then press the Perform Command Menu Option. 5. The relevant file will now be copied, and the results of this action will be displayed as below. Figure 86 Configuration Copy Successful At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the move Main Menu Sub-Element. This will display window to move or rename a configuration file (Figure 87). Figure 87 Configuration Move Settings The procedure to rename a file is:

1. Select the file to be renamed from the drop-down menu of the Existing File Name field. 2. Enter the new file name in the New File Name field. 3. The User must then press the Perform Command Menu Option. 4. The relevant file will now be renamed, and the results of this action will be displayed. 86 | P a g e Designed for Operators, by Operators At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the delete Main Menu Sub-Element. This will display window to delete a configuration file (Figure 88). The procedure to delete a file is:

Figure 88 Configuration Delete Settings 1. Select the file to be renamed from the drop-down menu of the Filename field. 2. The User must then press the Perform Command Menu Option. A prompt box will now appear, and the User is requested to confirm "Do you really want to delete the file?". 3. The relevant file will now be renamed, and the results of this action will be displayed. At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the export Main Menu Sub-Element. This will display window to export a configuration file (Figure 89). The export option creates an ASCII file that can be physically edited by the User. The file will be stored in flash on the Base Station and the User will have to upload it off the Base Station. The procedure to export a file is:

87 | P a g e Designed for Operators, by Operators Figure 89 Configuration Export Settings 1. Select the CLI export filter from the drop-down menu of the CLI Export Filter. The options are:

a. All. This will export the entire configuration database. b. BS-Configuration. Base Station configuration database only. This excludes CPE and Service-profiles. c. CPE. This will export the Subscriber CPE provisioning database only. d. Service-Profile. This will export the Service Profile database only. 2. Enter the destination filename to export the database in the Filename field. 3. The User must then press the Perform Command Menu Option. 4. The relevant file will now be created, and the results of this action will be displayed. At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the import Main Menu Sub-Element. This will display window to import a configuration file (Figure 90). The import option will import a configuration into the running configuration. Overwriting the configuration file can have serious consequences. The User must proceed with care. 88 | P a g e Designed for Operators, by Operators Figure 90 Configuration Import Settings The procedure to import a file to the Base Station:

1. Select the filename to import into the running configuration from the drop-down menu of the 2. 3. Import Filename. If the User enables the Overwrite field, then this will replace the existing CPE configuration data with the imported data. This will only work with files created with the export CPE option. Trying to load other files with the overwrite option set will result in an error message. If the User does not enable the Overwrite field, then the imported data will be merged with the existing configuration. 4. The User must then press the Perform Command Menu Option. The Import command can take several minutes to complete. Please wait until this process is completed before going on to make any other configuration changes. At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the write Main Menu Sub-Element. This will display window to write a configuration file

(Figure 91). The write procedure will copy the running configuration to startup. The new startup configuration will be effective at the next reboot of the Base Station. Please note that changes will not be persistent and survive a restart unless the write command is issued after the changes are made. 89 | P a g e Designed for Operators, by Operators The procedure to write the configuration is:

Figure 91 Configuration Write Settings 1. The User must then press the Perform Command Menu Option. A prompt box will now appear, and the User is requested to confirm "Do you really want to write the file?". 2. The relevant configuration will now be written, and the results of this action will be displayed. At the Main Web GUI Interface Screen select the Configuration Tab, then Configuration Main Menu Option and then the restore Main Menu Sub-Element. This will display window to restore a configuration file (Figure 92). The procedure will restore a binary backup of the entire database. This procedure will require a reboot of the Base Station. The procedure to restore a database is:

Figure 92 Configuration Restore Settings 1. Select the filename to restore a binary backup of the database in the Filename field. 90 | P a g e Designed for Operators, by Operators 2. The User must then press the Perform Command Menu Option. A prompt box will now appear, and the User is requested to confirm "Do you really want to delete the file?". 3. The relevant file will now be renamed, and the results of this action will be displayed. At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the download Main Menu Sub-element. This will display window to download a configuration file to a remote server (Figure 93). Prior to downloading the file, the User must ensure that an FTP Server has been configured and is running. There are several free commercially available FTP Servers that can be used. A key step in the process is to ensure that the URL for the file is set to be the FTP Home directory. For the purposes of upload and download, think of the Base Station as client in relation to the FTP as the server. The download process will therefore download from the Server to the Base Station. Figure 93 Configuration Download Settings The procedure to download a file from a remote server is:

1. Enter the remote server source configuration URL in the FTP/HTTP/HTTPS URL field. Acceptable examples are:

ftp://192.168.10.1/filename a. b. http://my.host-name.com/dir/filename c. ftp://username:password@noc.big_co.com:2323/dir/filename 2. Enter the destination configuration used filename used for the Base Station is the Destination Filename field. 3. The User must then press the Perform Command Menu Option. A prompt box will now appear, and the User is requested to confirm "Do you want to download the file?". 4. The relevant file will now be downloaded, and the results of this action will be displayed. 91 | P a g e Designed for Operators, by Operators At the Main Web GUI Interface Screen select the Configuration Tab, then configuration Main Menu Option and then the upload Main Menu Sub-Element. This will display window to upload a configuration file to a remote server (Figure 94). Prior to uploading the file, the User must ensure that an FTP Server has been configured and is running. Figure 94 Configuration Upload Settings The procedure to upload a file to a remote server is:

1. Enter the configuration source filename in the Source Filename field. ftp://192.168.10.1/filename a. b. http://my.host-name.com/dir/filename c. ftp://username:password@noc.big_co.com:2323/dir/filename 2. Enter the remote server destination file URL in the FTP/HTTP/HTTPS URL field. Acceptable examples are:

3. The User must then press the Perform Command Menu Option. A prompt box will now appear, and the User is requested to confirm "Do you want to upload the file?". 4. The relevant file will now be uploaded, and the results of this action will be displayed. To ensure that the User has a stored backup of the running configuration file, then the User would export and then upload the relevant files. To restore a previously stored filed from its remote location, then the User would download and then import. The procedure to upload a file to a remote server is:

1. Enter the configuration source filename in the Source Filename field. 2. Enter the remote server destination file URL in the FTP/HTTP/HTTPS URL field. Acceptable examples are:

ftp://192.168.10.1/filename a. b. http://my.host-name.com/dir/filename c. ftp://username:password@noc.big_co.com:2323/dir/filename 92 | P a g e Designed for Operators, by Operators 3. The User must then press the Perform Command Menu Option. A prompt box will now appear, and the User is requested to confirm "Do you want to upload the file?". 4. The relevant file will now be uploaded, and the results of this action will be displayed. To ensure that the User has a stored backup of the running configuration file, then the User would export and then upload the relevant files. To restore a previously stored file from its remote location, then the User would download and then import. 3.5.4 Connecting a Subscriber Station The procedures for provisioning each make and model of Subscriber CPE device vary and hence are beyond the scope of this document. However, Mercury have prepared general documentation that details recommend procedures to configure specific Subscriber units. Please refer to this documentation for further details. When a Subscriber CPE is powered on and configured for an appropriate Base Station, if that Base Station is configured for autoprovisioning, the Subscriber CPE will automatically connect to the Base Station and it will be assigned the default Client Profile (Client Profile 1). The User however has the complete flexibility to pre-configure the Subscriber CPE and has the capability to assign it to a specific Client Profile. The procedure to configure a Subscriber CPE is:

1. For the Subscriber CPE that you wish to provision please record the Subscriber MAC address. This is written on the CPE label. 2. At the Main Web GUI Interface Screen select the Configuration Tab and then the cpe Main Menu Option. This will display a list of all Subscriber CPEs that have been specifically configured on the Base Station (Figure 95). If there are none listed, then none have been configured. Figure 95 CPE Main Menu Option 93 | P a g e Designed for Operators, by Operators 3. The User now must enter the Edit Mode (select Edit Private or Edit Exclusive). The <Add cpe>

option will appear (refer to Figure 96). Figure 96 Add Subscriber CPE Option 4. The User must select the <Add cpe> option. A Key Settings window will appear. The User is prompted to enter the Subscriber CPE MAC Address. The MAC Address must be entered in Upper Case letters only and using a colon (:) to separate the digits, e.g. 00:17:C4:8F:9B:34. If the User selects the ? Command Menu Option within the window then a reminder prompt will be displayed. Once the MAC Address has been entered the User must select the Add command button (Figure 97). Figure 97 Add Subscriber CPE MAC Address 5. The User will now be presented with the Subscriber configuration options. The options to select are (Figure 98):

Convergence Sublayer Type. The User can select from a drop-down menu. The default option is Ethernet CS and the available options are:

IPV4_CS. o o ETHERNET_CS . This is the default setting; the Base Station operates in Standalone mode. Client Profile. This profile can be selected from a drop-down menu. The User can select <unset>

or from one of the user configured profiles (1 through 64). IP Address. Applicable/Visible only when the CPE is configured for IPV4_CS Convergence Sublayer mode and the base station operated in Stand Alone mode. 0.0.0.0 value (default) means that the 94 | P a g e Designed for Operators, by Operators CPE will obtain its IP address through DHCP Server. When changed from the defaults value a static IP address is used for the Provisioning. The CPE devices WAN interface must be configured with the same IP address. IP Netmask. Applicable/Visible only when the CPE is configured for IPV4_CS Convergence Sublayer mode and the base station operated in Stand Alone mode. Defines the Subnet Mask. Currently only a single IP Address is possible, thus the default value of 255.255.255.25.255 should not be changed!

Customer ID. This is a free format text field that enables the User to uniquely define a Subscriber. This is edited by selecting the notepad icon. Maximum Uplink Rate. The User can select the maximum uplink modulation rate. This will effectively provide a cap on the maximum data traffic rate. This direction is defined as the Subscriber to Base Station. This is selected via the drop-down menu and the options are:

o QAM64 5/6 o QAM64 3/4 o QAM64 2/3 o QAM64 1/2 o QAM16 3/4 o QAM16 1/2 o QPSK 3/4 o QPSK 1/2 o QAM64 5/6 o QAM64 3/4 o QAM64 2/3 o QAM64 1/2 o QAM16 3/4 o QAM16 1/2 o QPSK 3/4 o QPSK 1/2 Maximum Downlink Rate. The User can select the maximum downlink modulation rate. This will effectively provide a cap on the maximum data traffic rate. This direction is defined as the Base Station to Subscriber. This is selected via the drop-down menu and the options are:

Vlan-profile. Select and apply a default Vlan-profile to the CPE. 95 | P a g e Designed for Operators, by Operators Figure 98 Add Subscriber CPE Settings 6. Once the Subscriber options have been selected, the User can then Validate the changes. The User simply selects the Validate command button. A window indicating whether the Validation is successful or not will appear (Figure 99). If successful, then the User has to select the OK command button. Figure 99 Add Subscriber CPE Validation 96 | P a g e Designed for Operators, by Operators 7. After performing the Validation, the final step is to execute the Commit procedure. The User must select the Commit command button. A window prompting the User to commit the changes will appear. To affect the commit the User must select the OK command button (Figure 100). A further window indicating that the commit changes succeeded will appear. 8. The Subscriber configuration details will now be displayed. Figure 100 Add Subscriber CPE Commit 97 | P a g e Designed for Operators, by Operators Figure 101 Subscriber CPE Configured Settings 9. If the User wants to delete a previously configured Subscriber, then the option to delete is available. When the User is in the Edit Mode, there is a red cross box positioned next to the end of the Subscriber MAC Address listing. If the User positions the cursor over the box, then the message Remove cpe appears (Figure 102). The User simply selects this box. The User must then commit the changes. Figure 102 Subscriber CPE Delete 98 | P a g e Designed for Operators, by Operators 3.5.5 Subscriber CPE Client Profiles The process to create a QoS (Quality of Service) Client Profile on the Subscriber CPE is relatively straightforward. The basic concept flow diagram is detailed in Figure 103. Figure 103 Subscriber CPE Provisioning Flow Concepts The Service Profile system using Client Profiles, creates multiple data connections that suit the need of the Operator or Service Level Agreements. The Client Profile is the top level in a complex hierarchy that provides a large degree of flexibility in service offerings. Client Profiles are assigned to individual Subscriber CPEs and within each client profile there is the ability to throttle throughput and organize types of traffic into specific connection types. The use of ARQ/HARQ is also contained within this system. The Subscriber CPE Client Profile contains a Service Flow for both the uplink and the downlink directions. The Service Flow is created from the following components:

The direction of flow of traffic The specific Quality of Service (QoS) type, e.g. Best Effort (BE) or Unsolicited Grant Service (UGS) and the bandwidth rates applied to a service flow ARQ and/or HARQ definitions. These are the error recovery mechanisms. Packet Classifiers. This will classify on a packet by packet basis depending on the defined classification criteria. For example, the conditions under which the packet is to be transported and/or which Service flow it is to be assigned. A Client Profile is a set a Service Flows that correspond to a specific Service Level Agreement assigned to a customer. Each Client Profile supports up to 16 service flows and each service flow is unidirectional. A set of service flows includes an Uplink and a Downlink direction. Tip: When designing Client Profiles, it is important to understand how the throughput rating mechanism works. In the event of contradicting parameters being set, the system will allocate to a Subscriber CPE the lower of the parameters. For example, assume a conflict between the Client Profile setting the maximum uplink rate of 2Mbps and the QoS Profile setting the maximum sustained rate to 1Mbps. In this example, the system will limit the uplink rate to 1Mbps. 99 | P a g e Designed for Operators, by Operators Figure 104 demonstrates a typical "Best Effort" type of Client Profile. Consider a packet that is flowing in the downlink direction (i.e. Base Station to Subscriber CPE). The same concept applies in the uplink direction. A packet flow from the network and into the Base Station. It is destined for the Subscriber CPE. The packet is then processed by the Classifiers rules that have been defined. In this example these are the Downlink Packet Classifier. If the packet is subject to the Classifier rule, then it is processed and classified as defined by that rule. Packets that are not subject to the rule are then identified as a Non-Classified Packet. The Non-Classified Packets are then passed out of the Base Station and are now subject to the relevant Service Flow definitions. In this example this would be Best Effort. Figure 104 Typical Best Effort Client Profile Figure 98 demonstrates a more complex but still typical "Voice and Data" type of application. In this example these is a VoIP Packet Classifier defined. This has been associated to an eRTPS Service Flow. Non-Classified packets have been set to a Best Effort Service Flow. Any packet that enters from the Network will be tested against the Classifier rules. A VoIP packet will therefore be transmitted downlink via eRTPS and everything else via Best Effort. 100 | P a g e Designed for Operators, by Operators Figure 105 Typical Voice and Data Client Profile By default, the Base Station is pre-configured with several profiles for Classifier, HARQ, ARQ, QoS and Client. The User has the complete freedom and flexibility to use these pre-

defined profiles or they can edit accordingly. At the Main Web GUI Interface Screen select the Configuration Tab and then the serviceprofile Main Menu Option. This window details the information for the service profile Main Menu Option. There are five Main Menu Sub-Elements and window is split into five main grouping sections (Figure 106). The five main grouping sections provide a summary of the information that can be obtained by selecting and navigating down into the Main Menu Sub-Element level. Figure 106 Service Profile Menu Option The Main Menu Sub-Elements are:

cls-profile. These are the Classifier profiles. harq-profile. These are the Hybrid ARQ (automatic recovery) profiles. arq-profile. These are the ARQ profiles. qos-profile. These are the Quality of Service profiles. client-profile. These are the Client profiles. vlan-profile. VLAN configuration profiles. 101 | P a g e Designed for Operators, by Operators This just provides an indication of the information that is displayed. A description of the variables will be provided when the Main Menu Sub-Elements are described. The five main grouping sections are:

Classifier Profiler. The User can define up to 64 Classifier profiles. A list of profiles (up to 16 at a time) and the following information is displayed for each Classifier:

Hybrid ARQ Profile. The User can define up to 6 profiles and the following information is displayed ARQ Profile. The User can define up to 3 profiles and the following information is displayed for each profile. It is recommended to keep default values. o Profile #

o Name o Description o Cls-priority o Cls-priority-used o Eth-type o Eth-type-used o Ip-tos-dscp for each profile:

o Profile #

o Name o Description o Enable o Channel-mapping o Num-retries o Pdu-sn-support o Profile #

o Name o Description o Enable o Deliver-in-order o Window-size o Timeout-tx-delay o Timeout-rx-delay o Block-lifetime o Sync-loss o Purge-timeout o Block-size o Ack-processing-time each QoS profile:

o Profile #

o Name o Max-sustained-traffic-rate o Max-latency o Data-delivery-service o Traffic-priority o Max-traffic-burst QoS Profile. The User can define up to 32 profiles and the following information is displayed for 102 | P a g e Client Profile. The User can define up to 64 profiles and the following information is Designed for Operators, by Operators o Min-reserved-traffic-rate o Tolerated-jitter o Unsolicited-grant-interval o Unsolicited-poll-interval displayed for each Client profile:

o Profile #

o Description o Max-dl-rate o Max-pps o Max-ul-rate o Min-dl-reserved-rate o Min-ul-reserved-rate At Main Web GUI Interface Screen select the Configuration Tab and then the serviceprofile Main Menu Option. If the User now enters the Edit Mode, then they can either Edit or Delete any of all the profiles that have been configured as a default. If the User decides to Edit any of these profiles, then they are immediately navigated to the relevant Main Menu Sub-Element level. The information that is presented at the service-profile Main Menu Option level is simply a summary of what is available for each of the profiles. The User can navigate to the respective Main Menu Sub-Element level for full viewing and configuration capabilities. If the User wants to configure any of the parameters, then they must enter the Edit Mode

(select Edit Private or Edit Exclusive) and edit as necessary. The methods to Edit the parameters will be offered via a drop-down menu of choices, an enabling of a check box or editing of a notepad icon. These Profiles will now be described in detail. These Profiles will now be described in detail. 3.5.5.1 Classifier Profile This profile will classify on a packet by packet basis depending on the defined classification criteria. For example, the conditions under which the packet is to be transported and/or which Service flow it is to be assigned. At Main Web GUI Interface Screen select the Configuration Tab, then the service-profile Main menu Option and then the cls-profile Main Menu Sub-Element. This User is presented with all the 64 preconfigured default profiles. These are displayed 16 at a time. To physically view all the profile configuration parameters then the User must select a profile and two main grouping sections are presented (Figure 107). 103 | P a g e Designed for Operators, by Operators Figure 107 Service Profile Client Profile The main grouping sections are:

Key settings. This simply displays:

o Profile #

Classifier Profile. This displays all that the available configuration parameters. These are:

o Name. This is the profile name and it is a text field o Description. This is the profile description and it is a text field. o Cls-priority. This User can assign a priority to the classifier. The priority is assigned as a number in the range 0 to 255. The default priority is 0 (no priority). o Cls-priority-used. This is a check box to enable/disable the priority rule. o Eth-type. This is the Ethernet Type. This is assigned as a number in the range 1501 to 65535. This represents the value in decimal format. o o o Eth-type-used. This is a check box to enable/disable the Ethernet Type rule. o Ip-tos-dscp. This is the IP TOS Descriptor. This is assigned as a number in the range 0

(default) to 63. Ip-tos-dscp-used. This is a check box to enable/disable the IP TOS Descriptor rule. Ip-protocol. This is the IP Protocol. This is assigned as a number in the range 0 (default) to 255. Ip-protocol-used. This is a check box to enable/disable the IP Protocol rule. o o Dest-ip-addr-prfx. This is the IP Destination Address and Prefix (mask length). Configuration examples are 192.0.0.0/2, 192.168.0.0/3, 192.1468.254.0/23 and 192.168.1.1/32. o Dest-ip-addr-used. This is a check box to enable/disable the IP Destination Address rule. o Src-ip-addr-prfx. This is the IP Source Address and Prefix (mask length). Configuration examples are 192.0.0.0/2, 192.168.0.0/3, 192.1468.254.0/23 and 192.168.1.1/32. o Src-ip-addr-used. This is a check box to enable/disable the IP Source Address rule. o Dest-port-start. This is the Destination Port Low Limit. This is assigned as a number in the o Dest-port-end. This is the Destination Port High Limit. This is assigned as a number in the range 0 (default) to 65535. range 0 (default) to 65535. o Dest-ip-port-used. This is a check box to enable/disable the Destination Port rule. 104 | P a g e Designed for Operators, by Operators o Src-port-start. This is the Source Port Low Limit. This is assigned as a number in the range o Src-port-end. This is the Source Port High Limit. This is assigned as a number in the range o Src-ip-port-used. This is a check box to enable/disable the Source Port rule. o Vlan-id. This is the VLAN ID Tag. This is assigned as a number in the range 0 (default) to 0 (default) to 65535. 0 (default) to 65535. 4095. o Vlan-id-used. This is a check box to enable/disable the VLAN ID rule. o Vlan-user-priority-low. This is the VLAN User Priority Low Byte. This is assigned as a o Vlan-user-priority-high. This is the VLAN User Priority High Byte. This is assigned as a number in the range 0 (default) to 7. number in the range 0 (default) to 7. o Vlan-user-priority-used. This is a check box to enable/disable the VLAN User Priority rule. o Mac-addr-option. This is a drop-down list to specify if a MAC address will be used for classification. The default value is auto. Other options include CPE_MAC or OUI

(Organizationally Unique Identifier). The OUI is a unique 24-bit string assigned to hardware manufacturers. o Mac-addr-oui. If OUI is specied in the Mac-addr-option, then this field will be visible. It will allow a 24-bit string to be specified to identify the hardware manufacturer. o Allow-arp. This is a check box to enable/disable the ARP broadcasts. Figure 108 Classifier Profile 105 | P a g e Designed for Operators, by Operators Figure 109 Classifier Profile Continued The System is pre-configured with 64 default profiles. If the User wants to add any of their own configurations, they must delete a profile before they can add and configure a new one. When in Edit mode, the User is presented with (Figure 110):

<Add cls-profile>. If the User selects this option and there is available profile to be added, then they can simply add and then they will be dropped directly into the configuration window. A List of all the profiles with a red box beside each profile. If the User navigates to the red icon, then this will present the User with the ability to delete the profile. 106 | P a g e Designed for Operators, by Operators Figure 110 Service Profile Classifier Profile Edit Capability 3.5.5.2 HARQ Profile At the Main Web GUI Interface Screen select the Configuration Tab, then the serviceprofile Main Menu option and then the harq-profile Main Menu Sub-Element. This User is presented with all the 6 preconfigured default profiles. To physically view all the profile configuration parameters then the User must select a profile and two main grouping sections are presented (Figure 111). Figure 111 Service Profile HARQ Profile 107 | P a g e Designed for Operators, by Operators The main grouping sections are:

Key settings. This simply displays:

o Profile #

Hybrid ARQ Profile. This displays all that the available configuration parameters. These are:

o Name. This is the profile name and it is a text field o Description. This is the profile description and it is a text field o Enable. This is a check box to enable/disable the HARQ function o Channel-mapping. This is the HARQ Map Length. This is assigned as a number in the range o Num-retires. This is the HARQ Number of Retries. This is assigned as a number in the 0 to 16 with a default of 4 range 0 to 16 with a default of 1 o Pdu-sn-support. This is the HARQ PDU Sequence Number Support. The options are none, short (default) and long for reordering control. PDN sequence number is used to re-order HARQ bursts on the receiver. Short uses 3-byte sequence number and the long uses 4 byte. In general long is better in DL and short is enough in the UL. It is recommended to keep the default settings. The System is pre-configured with 6 default profiles. If the User wants to add any of their own configurations, they must delete a profile before they can add and configure a new one. When in Edit mode, the User is presented with (Figure 112):

<Add harq-profile>. If the User selects this option and there is available profile to be added, then they can simply add and then they will be dropped directly into the configuration window. A List of all the profiles with a red box beside each profile. If the User navigates to the red icon, then this will present the User with the ability to delete the profile. Figure 112 Service Profile HARQ Profile Edit Capability 108 | P a g e Designed for Operators, by Operators 3.5.5.3 ARQ Profile At the Main Web GUI Interface Screen select the Configuration Tab, then the serviceprofile Main Menu option and then the arq-profile Main Menu Sub-Element. This User is presented with all the 3 preconfigured default profiles. To physically view all the profile configuration parameters then the User must select a profile and two main grouping sections are presented (Figure 113). Figure 113 Service Profile ARQ Profile The main grouping sections are:

Key settings. This simply displays:

o Profile #

ARQ Profile. This displays all that the available configuration parameters. These are:

o Name. This is the profile name and it is a text field o Description. This is the profile description and it is a text field. o Enable. This is a check box to enable/disable the ARQ profile. o Deliver-in-order. This is a check box to enable/disable the ARQ deliver in order option. o Window-size. This is the ARQ Window Size. This is assigned as a number in the range 1 to 1024 (default). o Timeout-tx-delay. This is the ARQ Transmit Retry Timeout Delay. This is assigned in units of 5msec in the range 0 to 1310 with a default of 5 (25msec). 109 | P a g e Designed for Operators, by Operators o Timeout-rx-delay. This is the ARQ Receive Retry Timeout Delay. This is assigned in units of 5msec in the range 0 to 1310 with a default of 5 (25msec). o Block-lifetime. This is the ARQ Transmit Retry Timeout Delay. This is assigned in units of 5msec in the range 0 to 1310 with a default of 5 (25msec). o Sync-loss. This is the ARQ Sync Loss Timeout. This is assigned in units of 5msec in the range 0 to 1310 with a default of 120 (600msec). o Purge-timeout. This is the ARQ Purge Timeout. This is assigned in units of 5msec in the range 0 to 1310 with a default of 32 (160msec). o Block-size. This is the ARQ Block Size. The options are 16, 32, 64, 128 (default), 256, 512 and 1024. o Ack-processing-time. This is the ARQ Acknowledge Processing Time. This is assigned as a number in msec in the range 0 (default) to 255. The System is pre-configured with 6 default profiles. If the User wants to add any of their own configurations, they must delete a profile before they can add and configure a new one. When in Edit mode, the User is presented with:

<Add arq-profile>. If the User selects this option and there is available profile to be added, then they can simply add and then they will be dropped directly into the configuration window. A List of all the profiles with a red box beside each profile. If the User navigates to the red icon then this will present the User with the ability to delete the profile (Figure 114). Figure 114 Service Profile ARQ Profile Edit Capability 110 | P a g e Designed for Operators, by Operators 3.5.5.4 Quality of Service, QoS Profile A QoS Profile contains all information in regards to QoS type, latency, throughput and etc. These Profiles are independent of direction and can be applied to multiple service flows. The types of QoS that are offered are:

Best Effort or BE. Alternatively this is described as MIR or Maximum Information Rate. Unsolicited Grant Service or UGS. An alternative for this is CIR or Committed Information Rate. Extended Real-Time Polling Service or eRTPS. This is also known as Dynamic CIR. Best Effort is by far the most used QoS type that is configured in most deployments. This Qos type is bursty in nature and provides for up to a maximum rate. As an example, it could provide for internet speeds of up to 3 Mbps. The disadvantage of a Best Effort Service is that it does not provide any guarantee that the configured throughput will be achieved. A Base Station will offer throughput to BE configured Subscribers if there is bandwidth available and there are no other CIR configured Subscribers demanding throughput Unsolicited Grant Service connections provide for a dedicated and guaranteed Service Level Agreement. It is typically used for applications that require constant bit rate services such as VoIP. Any traffic assigned to a UGS service flow will be allocated for the sole use by that Subscriber. The allocated traffic for this UGS will be removed from the available pool of throughput for the Base Station to which the Subscriber has been configured. UGS connections typically provide low latency which is ideal for VoIP applications. Extended Real-Time Polling Service is a QoS type that is very similar to UGS. Traffic is allocated for the sole use by a Subscriber CPE but only when the Subscriber CPE requests traffic. However, when traffic is not being requested by the Subscriber, the allocated eRTPS bandwidth can be used by any other Subscriber. The eRTPS is the preferred QoS type for VoIP applications due to the dynamic resource control. There are 32 QoS profiles that have been pre-configured and stored in the Base Station. These can be viewed at the summary level (Figure 115). At Main Web GUI Interface Screen select the Configuration Tab and then select the service-profile Main Menu Sub-Element. For full examination and configuration of the QoS profiles then the User needs to navigate into the Main Menu Sub-Element level. 111 | P a g e Designed for Operators, by Operators Figure 115 Default Quality of Service Profiles At the Main Web GUI Interface Screen select the Configuration Tab, then the serviceprofile Main Menu Option and then the qos-profile Main Menu Sub-Element. This User is presented with all the 32 preconfigured default profiles (Figure 116). To physically view all the profile configuration parameters then the User must select profile and two main grouping sections are presented. Figure 116 Quality of Service Profiles 112 | P a g e Designed for Operators, by Operators The main grouping sections are:

Key settings. This simply displays:

o Profile #

QoS Profile. This displays all that the available configuration parameters. These are:

o Name. This is the profile name and it is a text field. o Description. This is the profile description and it is a text field. o Max-sustained-traffic-rate. This is a Maximum Sustained Traffic Rate. This is assigned in bits per second in the range 0 to 4294967295. o Max-latency. This is a Maximum Latency. This is assigned in milliseconds in the range 0 to 65535. o Data-delivery-service. This is the Data Delivery Service. The options that are available via a dropdown menu are UGS_Service, RTP_Service, nRTP_Service, BE_Service and eRTP_Service. o Traffic-priority. This is the Traffic Priority Level. This is assigned as a number in the range 0 (default) to 7. o Max-traffic-burst. This is a Maximum Traffic Burst Size. This is assigned in bits per second in the range 0 to 4294967295. o Min-reserved-traffic-rate. This is a Minimum Reserved Traffic Rate. This is assigned in bits per second in the range 0 to 4294967295. o Tolerated-jitter. This is a Tolerated Jitter. This is assigned in milliseconds in the range 0 to 65535. o Unsolicited-grant-interval. This is a Unsolicited Grant Interval and is only relevant for UGS. This is assigned as a number in the range 0 to 65535. o Unsolicited-poll-interval. This is a Unsolicited Poll Interval and is only relevant for nonUGS service classes. This is assigned as a number in the range 0 to 65535. The System is pre-configured with 32 default profiles. If the User wants to add any of their configurations, they must delete a profile before they can add and configure a new one. When in Edit mode, the User is presented with (Figure 117):

<Add qos-profile>. If the User selects this option and there is available profile to be added then they can simply add and then they will be dropped directly into the configuration window. A List of all the profiles with a red box beside each profile. If the User navigates to the red icon then this will present the User with the ability to delete the profile. 113 | P a g e Designed for Operators, by Operators Figure 117 Quality of Service Edit Capability 3.5.5.5 Client Profile A Client Profile is a set of Service Flows that correspond to a specific Service Level Agreement assigned to a customer. The system allows up to 64 Client Profiles and each Profile must be configured with an Uplink and a Downlink Service Flow. At Main Web GUI Interface Screen select the Configuration Tab, then the service-profile main menu option for a summary page (Figure 118). Figure 118 Client Profile Summary For details navigate further to the client-profile main Menu Sub-Element. This User is presented with up to 64 profiles. To physically view all the profile configuration parameters then the User must actually select a profile and three main grouping sections are presented (Figure 119). 114 | P a g e Designed for Operators, by Operators Figure 119 Client Profile The main grouping sections are:

Key settings. This simply displays:

o Profile #

Client Profile. This displays all that the available configuration parameters. These are:

o Description. This is the profile description and it is a text field. o Max-dl-rate. This is a Maximum Downlink Rate that is reserved for this client. This is assigned in bits per second in the range 0 to 4294967295. o Max-pps. This is a Maximum Packets per second. This is assigned as a number in the range 0 to 65535. 0 to 4294967295. o Max-traffic-burst. This is a Maximum Client Traffic Burst. This is as a number in the range o Max-ul-rate. This is a Maximum Uplink Rate for this client. This is assigned in bits per second in the range 0 to 4294967295. o Min-dl-reserved-rate. This is a Minimum Downlink Rate that is reserved for this client. This is assigned in bits per second in the range 0 to 4294967295. o Min-ul-reserved-rate. This is a Minimum Uplink Rate for this client. This is assigned in bits per second in the range 0 to 4294967295. o Name. This is the profile name and it is a text field. o Num-sflow. This is the Number of Service Flows for the Client Profile. This is as a number in the range 1 to 16. 115 | P a g e Designed for Operators, by Operators 1 to 8. o Priority. This is the Traffic Priority for this Client. This is assigned as a number in the range o Service Flow Profile. This lists all the Service Flow Profiles. The configurable parameters for each Service Flow Profile are:

o Profile #. This is the number of the Service Flow profile. o Name. This is the name of the Client profile. o Description. This is the text description of the Client profile. o Direction. This is the direction of the traffic flow. o Arq-profile-num. This is the number of the arq profile that has been assigned for this o Cls-profile-num. This is the number of the classifier profile that has been assigned for this o Harq-profile-num. This is the number of the harq profile that has been assigned for this o Qos-profile-num. This is the number of the QoS profile that has been assigned for this Service Flow Profile. Client Profile. Client Profile. Client Profile. To define a Client profile then the User must be in the Edit Mode. There are two ways to edit and configure a Client Profile. 1. At the Main Web GUI Interface Screen select the Configuration Tab, then the service-profile Main Menu Option and then the client-profile Main menu Sub Element. This User must then select the Client Profile that they wish to configure and scroll down to the bottom of the Window. They will be presented with the Service Flow Profile (Figure 120). If the User enters the Edit Mode, then at the end of each profile the Edit and Delete Command Menu Options will appear. The User can select the Edit Command Menu option and they will be navigated into the Edit Mode. Figure 120 Client Profile Edit Capability 2. The User can navigate direct to the Service Flow Profile options. At the Main Web GUI Interface Screen select the Configuration Tab, then the service-profile Main Menu Option, then the client-

profile Main Menu Sub-Element, then the relevant profile #, then sflow-profile and finally the relevant profile #. The User is presented with two main grouping sections. The User must be in 116 | P a g e Designed for Operators, by Operators Edit Mode to configure any of the parameters (Figure 121). When in Edit Mode if the User navigates to the red icon then this will present the User with the ability to delete the profile. Figure 121 Client Profile Edit Full Capability The main grouping sections are:

Key settings. This simply displays:

o Profile #

Service Flow Profile. This displays all that the available service flow parameters. These are:

o Name. This is the Service Flow name and it is a text field. o Description. This is the Service Flow description and it is a text field. o Direction. This is the direction of traffic flow for the Service Flow. The options are downlink or uplink. o Arq-profile-num. This is the ARQ Profile Number that is used by this Service Flow. The options are any of the 3 ARQ profiles that have been configured in the ARQ Profile configuration (refer to section 3.5.5.3). o Cls-profile-num. This is the CLS Profile Number that is used by this Service Flow. The options are any of the 64 CLS profiles that have been configured in the CLS Profile configuration (refer to section 3.5.5.1). 117 | P a g e Designed for Operators, by Operators o Harq-profile-num. This is the HARQ Profile Number that is used by this Service Flow. The options are any of the 6 HARQ profiles that have been configured in the HARQ Profile configuration (refer to section 3.5.5.2). o Qos-profile-num. This is the QoS Profile Number that is used by this Service Flow. The options are any of the 32 QoS profiles that have been configured in the QoS Profile configuration (refer to section 3.5.5.4). 3.5.5.6 CPE Provisioning Using a AAA Server Alternatively, the AAA (authentication, authorization and accounting) Server may be used perform CPE provisioning. This will allow configuration of most of the CPE configuration parameters including CPE Configuration including MAC, CS Sublayer, Client Profile, Maximum Uplink and Downlink Rate IP Settings including IP Address, Subnet mask, Customer ID is not supported To enable AAA provisioning, enable the option in the Web GUI. At the Main Web GUI Interface Screen select the Configuration Tab, then the system main menu option and then the base-station main Menu Sub-Element. This User is presented with the Base Station settings. To enable AAA provisioning, change the Mode from standalone-local to standalone-aaa-prov (Figure 122). Additionally, the following parameters are required to be configured (Figure 123). AAA (Radius) server ip address, AAA (Radius) server port number AAA (Radius) server secret, Provisioning realm: This parameter distinguishes between AAA provisioning vs AAA authentication while editing users file on AAA server. Mercury provides a customer specific AAA dictionary file which needs to be included with the AAA server and enable the service to properly format and send the provisioning information to the Base Station. Please contact Customer Support for further documentation on how to set-up and configure the AAA server. 118 | P a g e Designed for Operators, by Operators Figure 122 AAA Server Configuration on Base Station Figure 123 AAA Server Configuration on Base Station continued 119 | P a g e Designed for Operators, by Operators 3.5.5.7 Advanced VLAN Capabilities The Quantum Base Station has advanced Virtual LAN (or VLAN) capabilities as defined by IEEE 802.1q and 802.1p. The VLAN tags are a numerical header applied to an Ethernet frame in order to segregate a physical Ethernet segment into logical networks. The advantages of using a VLAN are the following:

Quality of Service (Qos) capabilities at Layer 2 allows different types of traffic to be placed on different VLANs for segmentation. E.g. Voice, video and data traffic can be assigned different VLANs Security to isolate user traffic from each other and keep management traffic separate Network Optimization to reduce broadcast storms and end user devices affecting the entire network. 3.5.5.8 VLAN for Management Traffic VLAN Management may be configured on the Base Station. Care must be taken to ensure this is configured correctly. All management traffic will accept management VLAN only including the Web GUI, FTP, SNMP, Telnet, Radius, SSH, R6 Control path and NTP. See section 3.5.3.5 for further information on configuring the management VLAN. 3.5.5.9 VLAN for Data Traffic In order to configure VLAN operations, the Base Station must be configured in Ethernet CS Stand Alone Mode. There are three modes of operation available that are configured from the VLAN profile. Transparent mode where the CPE (or devices behind the CPE) are performing tagging and untagging Per CPE Basis (per-mss) where a specific VLAN ID is assigned to a specific CPE from the Base Station side. On the CPE side there is no device with VLAN support, and this is transparent to the user. Service Flow (per-sf) basis where individual service flows are assigned a specific VLAN ID. This is useful for enforcing QoS policies and requires advanced configuration, classification and planning for implementation. Figure 124 VLAN Modes of Operation 120 | P a g e Designed for Operators, by Operators Figure 125 VLAN Profile List To configure VLANs for data traffic, select the Configuration Tab and then select the service profile Main Menu Option and then vlan-profile (Figure 125). 1. To enable first select Edit Private or Edit Exclusive. This will place the User into the Edit mode The User can add a profile or modify an existing one (Figure 126). 2. Enter a profile number (as below) or select an existing profile to edit Figure 126 VLAN Profile Edit Mode 121 | P a g e Designed for Operators, by Operators Figure 127 VLAN Profile Number 3. The User is now presented with a window that displays the following parameters. With the configuration below, it is assumed that the CPEs and Base Station have their VLAN tagging/untagging performed by other devices either behind the CPE or Base Station. VLAN Profile Number. This parameter is a number between 1-94. It is recommended to leave Profile 1 unchanged. Name/Description. Description for the VLAN Profile VLAN Mode. Depending on your configuration, set this mode to Transparent, per-sf or per-

mss the BST). VLAN Priority. The priority bit (0-7) inside the VLAN Packet that will be sent out with (from VLAN ID. The VLAN ID (0-4094) that the Packet will be sent out with (from the BST) and/or be expected to be received (from the Backhaul). Ether Type. The Ethernet Type of the Packet that will be sent out with (from the BST) and/or 0x8100(802.1q), Range with). Valid is:

to expected 0x9100/0x9200/0x9300/0x88a8 (QinQ). received be 122 | P a g e Designed for Operators, by Operators Figure 128 VLAN Profile Configuration 4. The User must Commit the changes (apply the configuration in run-time). To Commit, select the Commit option. A prompt screen will appear directing the User to confirm the pending configuration changes. To proceed the User must select Cancel or OK. The transparent mode configuration may also be used in combination with management VLAN where the system management interface VLAN is configured with a separate VLAN id. This will allow the management traffic to be isolated from data traffic. In the Per CPE Basis (or per-mss) mode, the CPE will automatically have its traffic tagged with the configured VLAN ID for traffic leaving the base station. This configuration may also be used in combination with management VLAN where the system management interface VLAN is configured with a separate VLAN id. This will allow the management traffic to be isolated from data traffic. Additionally, a per Service Flow VLAN may be used in combination with this configuration providing that the VLAN classification rules are set correctly. In the Per Service Flow Basis, the CPE will automatically have its traffic tagged with the configured VLAN ID for traffic leaving the base station. This configuration may also be used in combination with management VLAN and the per-CPE based configuration. 123 | P a g e Designed for Operators, by Operators 3.5.5.10 VLAN Classification To configure the tagging options for per-CPE and per-SF basis, classification rules must be configured. The options for VLAN classification includes:

CLS-priority (classifier priority) CLS-priority-used MAC-addr-option MAC-address-OUI For further information on configuring a classifier for VLAN, please see section 3.5.5.1. To apply a default VLAN profile to a CPE, please see section 3.5.4. 3.5.5.11 VLAN QinQ Configuration QinQ (or double-tagging) allows multiple VLAN headers to be inserted into a single frame. This configuration allows the service provider to manage data traffic with their own ID and shield the VLAN ID of the user, so as to save the public network VLAN ID resource of the service provider. This configuration mode is used on the per CPE or per Service Flow basis. To set QinQ configuration:

VLAN Profile Number. This parameter is a number between 1-94. Name/Description. Description for the VLAN Profile VLAN Mode. Set this mode to per-sf or per-mss mode VLAN Priority. The priority bit (0-7) inside the VLAN Packet that will be sent out with (from the BST). VLAN ID. The VLAN ID (0-4094) that the Packet will be sent out with (from the BST) and/or be expected to be received (from the Backhaul). Ether Type. To configure QinQ set the Ether Type to 0x9100/0x9200/0x9300/0x88a8. 124 | P a g e Designed for Operators, by Operators 3.6 Base Station Software Upgrade One of the Base Stations key features is that it has been designed to support a Software Defined Radio

(SDR) architecture. The distinct advantage is that a Base Station can be remotely upgraded with additional features and capabilities as these are developed. The Base Station maintains two software versions/images that may be selectively enabled, thus providing a fail-safe software upgrade procedure. The software upgrade process may be performed from the CLI, the Web Interface, as well as from the PureView EMS. In this section, the software upgrade procedures using the Web Interface is detailed. The first step in the process is to copy the software to a directory on the PC which is running the FTP server. Please ensure the Mercury directory structure is kept intact. Copy the software image, as provided by Mercury, to the assigned home directory of the FTP server (Figure 129). Figure 129 Software Components The next step is to confirm and setup the FTP Server. There are several free commercially available FTP Servers that can be used (Figure 130) such as 3CDaemon. Ensure that the FTP Server is running. Figure 130 FTP Server Configuration 125 | P a g e Designed for Operators, by Operators At the Main Web GUI Interface Screen select the Configuration Tab and then the software Main Menu Option. This will display the software Settings and the display is split into two main grouping sections. There are three further sub-element associated with this option. There are no User configurable options for the software Main Menu Option. The Base Station flash contains two partitions which are both loaded with software. There is a Bank A and a Bank B. The GUI will provide an indication as to current status of the software. The two main grouping sections for this Menu Main Sub-Element are (Figure 131):

Software Image Management. This displays the details for each software image. The options are:

load. o Current Boot Bank. This indicates which bank provided the current running software o Next Boot Bank. This indicates after the next reboot of the Base Station, which bank the software will be loaded from. o Boot Bank A. This indicates the software revision that is currently loaded into bank A. o Boot Bank B. This indicates the software revision that is currently loaded into bank B. o Sw Version Candidate. This is not relevant for the current method of software upgrade. It will simply indicate "No Software candidate available". Software Image Status. This provides an indication of the download status. The options are:

o State Detail. This will provide an indication of the current state of software upgrade detail. o Download Progress. This is a percentage indicator of the state of download progress. Figure 131 Software Image Management Dialog 126 | P a g e Designed for Operators, by Operators 3.6.1 Automatic Upgrade The Base Station software upgrade process can be performed using a single automatic operation. This performs the following procedure while providing continual upgrade status to the User. 1. Loads the software image file from a user defined location using FTP, HTTP, or HTTPS. 2. Unpacks the downloaded software image, verifies the image integrity (CRC and MD5 checksum), 3. Performs operations to distribute the software image to the various components of the Base 4. Selects the new software image installed as the partition to be used after the next Base Station and prepares for installation. Station. reboot. 5. Reboots the Base Station. To execute the Single-Step Software Upgrade Procedure, at the Main Web GUI Interface Screen the Configuration Tab, then the software Main Menu Option and then the automaticUpgrade Main Menu Sub-Element. The User will be presented with two main grouping sections (Figure 132). In the Load selected image from server, set nextBoot bank and Reboot section, enter the URL of the new software image in the SW Image URL box. There are a variety of formats of the URL of remote source file is. These can be displayed if the User selects the "help" key. These URL formats are defined as:

ftp://[user[:password]@]hostname[:port]/filepath http://hostname[:port]/filepath https://hostname[:port]/filepath Where [ ] indicates optional items. Thus, user:password@ is optional, and the :password part can be omitted

[:port] is also optional Examples using ftp (you can substitute http or https):

ftp://myhost.com/filename ftp://myhost.com/directory/filename ftp://myhost.com:2323/directory/filename ftp://myname@myhost.com:2323/directoryname/filename ftp://myname:password@myhost.com:2323/directoryname/filename URL of remote source file; format is as follows:

protocol://[user[:password]]@host[:port]/path protocol can be ftp, http, or https 127 | P a g e Designed for Operators, by Operators Figure 132 Single-Step Software Upgrade Dialog Once the URL has been entered, the User must select the Perform Command Menu Option in the Load selected image from server, set nextBoot bank, and Reboot section to initiate the upgrade process. This action will upgrade the Base Station in one simple step. 3.6.2 Manual Software Upgrade The Base Station software upgrade process can also be performed in two steps as an alternative to the automatic process. This will present the User with control over the various stages of the software upgrade process. 3.6.2.1 Loading Software In this procedure the following steps are performed:

1. Loads the software image file from a user defined location using FTP, HTTP, or HTTPS. 2. Unpacks the downloaded software image, verifies the image integrity (CRC and MD5 checksum), and prepares for installation. 3. Performs operations to update the flash partition. The first step is the software download and installation procedure. At the Main Web GUI Interface Screen select the Configuration Tab, then the software Main Menu Option and then the load Main Menu Sub-

Element. The User will be presented with two main grouping sections (Figure 133). In the Download and Install Software Images section, then enter the URL of the new software image in the SW Image URL box. Please see section 3.6.1 for syntax and examples of URLs that may be used. 128 | P a g e Designed for Operators, by Operators Figure 133 Software Load Menu Option Once the URL has been entered, the User must select the Perform Command Menu Option in the Download Software Images from server on Base Station section to initiate the software load process. 3.6.2.2 NextBoot Image Bank Selection The final step in the Multiple Step Software Upgrade process is the next boot partition selection and display procedure. At the Main Web GUI Interface Screen select the Configuration Tab, then the software Main Menu Option and then the boot Main Menu Sub-Element. The User will be presented with the option to select the next image bank to boot from (Figure 134):

129 | P a g e Designed for Operators, by Operators Figure 134 Software Image Bank Selection Display The purpose of the Select Next image bank to boot from is to specify the selected image to run after the next reboot. It will not affect the currently "Running" image. Subsequent reboots will run the "Selected"

software image (Figure 135). The available choices are:

A: The image loaded in image bank A. B: The image loaded in image bank B. Next: The alternative to the currently "Running" image. If the current image is A, the next boot will use B and vice versa. Now. This is a check box that must be enabled to perform automatic reset. Figure 135 Software Image Partition Selection 130 | P a g e Designed for Operators, by Operators 3.6.3 Base Station Performance Monitoring There are several monitoring parameters that can be checked to determine the overall performance of the Base Station and for any Subscribers that are connected to the Base Station. These parameters are contained within a variety of menu options. The Users starting point is Web GUI Main Web GUI Interface Screen. 3.6.3.1 Interface At Main Web GUI Interface Screen select the Configuration Tab and then the interface Main Menu Option this will display the key settings window. This window details enabled the configuration of the backhaul interfaces There are two Main Menu Sub-Elements to this window and the window is split into two main grouping sections (Figure 136). Figure 136 Performance Monitoring Interface The Main Menu Sub-Elements are:

configure. This configures the backhaul interfaces speed and mode of operation status. This describes the configured settings and the current status of these interfaces. Backhaul learning. Ethernet devices learned from backhaul Interface Settings and Status. The configured settings and their current status that are displayed for the five interfaces are:

o Admin State. This is the admin state o Oper State. This is the operational state o Link Speed. This is the interface link speed o Duplex Type. This is duplex status 131 | P a g e Designed for Operators, by Operators o Autoneg. This is autonegotiate setting o Maximum MTU Length. This is the maximum configured MTU Length o MAC Address. This is the MAC address of the interface At the Main Web GUI Interface Screen select the Configuration Tab and then the interface Main Menu Option, then the status main Menu Sub-Element. The resulting window will be split into two main sections

(Figure 137). These are:

Key Settings. o Name. This will indicate which interface is being displayed Interface Statistics and Status. The following settings and status are displayed. These are not editable parameters. o Admin State. This is the admin state o Oper State. This is the operational state o Link Speed. This is the interface link speed o Duplex Type. This is duplex setting o Maximum MTU Length. This is the maximum configured MTU Length o MAC Address. This is the MAC address of the interface Figure 137 Interface Status Key Settings and Status The same format is repeated for all interfaces and therefore only one will be outlined. To view the Interface Statistics of another interface then simply at the Main Web GUI Interface Screen select the Configuration Tab, then the interface Main Menu Option, then the status Main Menu Sub-Element and then relevant interface. To view Backhaul Learning table, at the Main Web GUI Interface Screen select the Configuration Tab and then the interface Main Menu Option, then the backhaullearning main Menu Sub Element. The resulting window will be split into two main sections (Figure 138). These are:

MAC. The MAC Address of the device learned. Port. The backhaul port where the device was learned from. IP Address. The IP address of the device. Applicable only in case of IP CS Stand Alone mode. Ageing. The time in seconds since the last packet was received from the device. There is 300 sec ageing. 132 | P a g e Designed for Operators, by Operators Figure 138 Backhaul Learning To view an individual Backhaul Learning entry from the table, at the Main Web GUI Interface Screen select the Configuration Tab and then the interface Main Menu Option, then the backhaul-learning main Menu Sub-Element followed by the MAC address of the device (Figure 139). Figure 139 Backhaul Learning Table Entry 133 | P a g e Designed for Operators, by Operators 3.6.3.2 Sector Statistics At the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu Option. This will display the Sector Settings window (Figure 140). There are no parameters to edit within the sector Main Menu Option. Figure 140 Sector Statistics When you select, Statistics, the further sub-elements are:

throughput-counters. Sector throughput counters are displayed. startup-counters. These are startup counters for a sector level. packer-error-rate-metrics. This will display several key packet error rate counters. Sector Advanced Settings (configured) Sector Provisioning (configured) Important sector statistics are contained within two options within the Sector Main Menu Option. The User now must navigate to the next level, therefore at the Main Web GUI Interface Screen select the sector main Menu option and then the statistics Main Menu Sub-Element. There are four further sub elements to this option and the window is split into four main grouping sections (Figure 141). The main grouping sections provide a summary of the information that can be obtained by selecting and navigating down into the Menu Sub-Element level. Figure 141 Sector Statistics Interface Key Settings The further sub-elements are:

service-flow-metrics. Several key service flow metrics are provided at a sector level (i.e. a Base Station level). 134 | P a g e Designed for Operators, by Operators To fully display all the available statistics the User now has to navigate to the next level, therefore at the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu Option then the statistics Main Menu Sub-Element, then service-flowmetrics and then 1. This will display the Metrics window. There are two distinct groups to this window (Figure 142). Key Settings. This indicates the relevant sector, which as has been described in number 1. This is not a configurable parameter. Sector Service-Flow Metrics. The following Metrics are displayed. These are displayed as a raw number but they can also be displayed in graphical form by selecting the "Graph" command button. o DSA Requests o DSA Req Successes o DSC Requests o DSC Req Successes o DSD Requests o DSD Req Successes o Max Active Svc Flows o Max Active DL Svc Flows o Max Active UL Svc Flows Figure 142 Sector Statistics Interface Key Settings 135 | P a g e Designed for Operators, by Operators A similar format is repeated for the other sector, statistics sub elements. The Key Settings window indicates the relevant sector. The information that is presented for each sub element, packet-error-

ratemetrics, startup-counters and throughput-counters is:

For the packet-error-rate metrics menu option the following Sector Pkt Error-Rate Metrics are For the startup-counters menu option, the following Sector Startup Counters are displayed For the throughput-counters menu option, the following Sector Throughput Counters are displayed (Figure 143):

o DL Packets Sent o DL Packet Errors o DL Pkt Error Rate o UL Packets Sent o UL Packet Errors o UL Pkt Error Rate

(Figure 144):

o Authentication Attempts o Authentication Successes o Ranging Attempts o Ranging Successes o Ranging Periodic o Bandwidth Requests o Handover Ranging displayed (Figure 145):

o DL User Bytes o UL User Bytes o DL MAC Bytes o UL MAC Bytes o DL User Packets o UL User Packets o DL MAC Packets o UL MAC Packets o DL User Pkt Errors o UL User Pkt Errors o DL MAC Pkt Errors o UL MAC Pkt Errors 136 | P a g e Designed for Operators, by Operators Figure 143 Sector Statistics Packet Error Rate Metrics Figure 144 Sector Statistics Startup Counters 137 | P a g e Designed for Operators, by Operators Figure 145 Sector Statistics Throughput Counters Important Subscriber statistics are contained within the statistics-mss Main Menu Sub Element within the Sector Main Menu Option. The User now has to navigate to the next level, therefore at the Main Web GUI Interface Screen select the sector Main Menu Option and then the statistics-mss Main Menu Sub-

Element. There are seven further sub elements to this option and the windows is split into the seven main grouping sections (Figure 146). The main grouping sections provide a summary of the information that can be obtained by selecting and drilling down into the sub-element level. 138 | P a g e Designed for Operators, by Operators Figure 146 Sector MSS-Statistics Metrics The further sub-elements are:

mss-throughput-counters. This is the throughput counters for the Subscribers that are communicating with the Base Station. sflow-throughput-counters. These are the throughput counters per service flow. rssi-cinr-counters. These are the RSSI and CINR metrics per Subscriber and per upstream/downstream direction. harq-counters. These are the HARQ counters per Subscriber. modulation-code-rate. These are the Modulation and Coding Scheme (MCS) per Subscriber. active-service-flows. These are the active Service flows per Subscriber. registered-ss. These are the registered Subscriber Station details. The seven main grouping sections are the summary for the sub-elements on a per sector basis:

Throughput Counters per MSS Throughput Counters Per Service-Flow RSSI and CINR Metrics Per MSS HARQ Counters Per MSS Modulation and Coding Scheme (MCS) Active Service Flows Registered Subscriber Station 139 | P a g e Designed for Operators, by Operators To fully display all the available statistics the User now has to navigate to the next level, therefore at the Main Web GUI Interface Screen select the Configuration Tab, then the sector Main Menu Option, then the statistics-mss Main Menu Sub-Element and then one of the seven further sub-elements. Under each tree Sub-element a list of all the connected Subscribers will be displayed. The Use has to select the relevant Subscriber and the information will be displayed for the particular Subscriber. At the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu Option, then the statistics-mss Main Menu Sub-Element and then mssthroughput-counters. There are two distinct groups to this window (Figure 147). Key Settings. This indicates the relevant Subscriber. This is not a configurable parameter. The following information is presented:

o Sector o MAC Address Throughput Counters Per MSS. The following Metrics are displayed. These are displayed as a raw number but they can also be displayed in graphical form by selecting the "Graph" command button. o DL Bytes o Ul Bytes o DL Pkts o UL Pkts o DL Pkt Err o UL Pkt Err o Hcs-cnt o Crc-cnt 140 | P a g e Designed for Operators, by Operators Figure 147 Registered Subscriber Station Throughput Counters At the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu option, then the statistics-mss Main Menu Sub-Element and then sflowthroughput-counters. The Service Flows that have been defined for each Subscriber will be displayed. For each Subscriber there will be at least two defined Service Flows, one for Upstream and another for Downstream. There are two distinct groups to this window (Figure 148). Key Settings. This indicates the relevant Subscriber. This is not a configurable parameter. The following information is presented:

o Sector o MAC Address SFID. This is the Service Flow identifier. Throughput Counters Per Service-Flow. The following Metrics are displayed. These are displayed as a raw number, but they can also be displayed in graphical form by selecting the

"Graph" command button. o DL Bytes o UL Bytes o DL Pkts o UL Pkts 141 | P a g e Designed for Operators, by Operators Figure 148 Sector Statistics Service Flow Throughput Counters At the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu Option, then the statistics-mss Main Menu Sub-Element and then rssi-cinrmetrics. The downstream and upstream direction for each Subscriber will be displayed. There are two distinct groups to this window. Figure 149 has the downstream RSSI parameters and Figure 150 has the upstream metrics. Key Settings. This indicates the relevant Subscriber. This is not a configurable parameter. The following information is presented:

o Sector. o MAC Address. o Channel Dir. This indicates the respective direction that the Metrics are displayed. Downstream RSSI/CINR Metrics. The following Metrics are displayed. These are displayed as a raw number but they can also be displayed in graphical form by selecting the "Graph" command button. If the CLI is used to view metrics, the RSSI per antenna will be shown but will have the same value across all antennas. Upstream RSSI/CINR Metrics. The following Metrics are displayed. These are displayed as a raw number but they can also be displayed in graphical form by selecting the "Graph" command button. o CINR Mean o CINR Std Dev o RSSI Mean o RSSI Std Dev o Mean CINR o Std Dev CINR o Maximum RSSI 142 | P a g e Designed for Operators, by Operators o Std Dev RSSI o Antenna 1 RSSI o Antenna 2 RSSI o Antenna 3 RSSI o Antenna 4 RSSI o Antenna 5 RSSI Figure 149 Sector Statistics Downlink RSSI CINR Metrics 143 | P a g e Designed for Operators, by Operators Figure 150 Sector Statistics Upstream RSSI CINR Metrics At the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu Option, then the statistics-mss Main Menu Sub-Element and then harqcounters. There will be three HARQ Service Flow identifiers displayed for each Subscriber. There are two distinct groups to this window (Figure 151). Key Settings. This indicates the relevant Subscriber. This is not a configurable parameter. The HARQ Counters Per MSS. The following Metrics are displayed. These are displayed as a raw number, but they can also be displayed in graphical form by selecting the "Graph" command button. It is not possible to view all the metrics in one window and therefore the User must scroll down to view them all. o HARQ Enabled. This indicates whether HARQ has been enabled. This is not however a following information is presented:

o Sector. o MAC Address. o Svc Flow ID. configurable parameter. o HARQ DL Pkt Ack o HARQ DL Pkt Neg Ack o HARQ DL Pkt Trans o HARQ DL Pkt Retrans 144 | P a g e Designed for Operators, by Operators o HARQ DL Pky Discards o HARQ DL Pkt 1st Neg Ack o HARQ UL Pkt Ack o HARQ UL Pkt Neg Ack o HARQ UL Pkt Trans o HARQ UL Pkt Retrans o HARQ UL Pky Discards o HARQ UL Pkt 1st Neg Ack Figure 151 Sector Statistics HARQ Counters At the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu option, then the statistics-mss Main Menu Sub-Element and then modulation-code-rate. The information for each Subscriber is displayed. There are two distinct groups to this window (Figure 152). Key Settings. This indicates the relevant Subscriber. This is not a configurable parameter. The following information is presented:

o Sector o MAC Address Modulation and Coding Scheme (MCS). The following information is displayed. o DL MCS. This indicates the current downlink MCS rate. The available options are:

QPSK 1/2 QPSK 3/4 QAM16 1/2 QAM16 3/4 QAM64 1/2 QAM64 2/3 QAM64 3/4 145 | P a g e Designed for Operators, by Operators QAM64 5/6 as the downlink. o UL MCS. This indicates the current uplink MCS rate. The available options are the same o DL HARQ STATE. Indication if any of the downlink services flows have HARQ Enabled. o DL MCS HARQ. The current MCS Rate used for the downlink services flows that have o UL HARQ STATE. Indication if any of the uplink services flows have HARQ Enabled. o UL MCS HARQ. The current MCS Rate used for the uplink services flows that have HARQ. HARQ. Figure 152 Sector Statistics Modulation Code Counters At the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu Option, then the statistics-mss Main Menu Sub-Element and then activeservice-flows. The Service Flows that are active for each Subscriber will be displayed. For each Subscriber there will be at least two active Service Flows, one for Upstream and another for Downstream. There are two distinct groups to this window (Figure 153). Key Settings. This indicates the relevant Subscriber. This is not a configurable parameter. The following information is presented:

o Sector o MAC Address o Svc Flow ID. This is the Service Flow identifier. Active Service Flows. The following Metrics are displayed. These are displayed as a raw number, but they can also be displayed in graphical form by selecting the "Graph" command button. o Svc Flow Dir. This provides an indication of the respective direction. The options are uplink or downlink. 146 | P a g e Designed for Operators, by Operators o UL Bytes. This provides an indication of the Service Flow QoS (Quality of Service). o Svc Flow CID o Svc Flow SAID Figure 153 Sector Statistics Active Service Flows At the Main Web GUI Interface Screen select the Configuration Tab and then the sector Main Menu Option, then the statistics-mss Main Menu Sub-Element and then registered-ss. The number of registered Subscribers will be displayed. There are two distinct groups to this window (Figure 154). Key Settings. This indicates the relevant Subscriber. This is not a configurable parameter. The following information is presented:

o Sector o MAC Address. Subscriber Unit WIMAX MAC addresses. Registered Subscriber Station. The following information is displayed. These are not configurable parameters at this menu option. o Client Profile ID. o Provisioning Status. One of the states below INIT. Initializing During Network Entry ACTIVE Service Flows are Provisioned and active DENY Provisioning Denied. Usually by the AAA server. TIMEOUT AAA Server timeout out. LOCAL TIMEOUT Local provisioning Timeout. o Provisioning Method. One of the methods below UKNOWN Usually during network entry. STANDALONE Uses local Base Station provisioning Database. STANDALONE DEF Uses Local Default Provisioning. AAA PROV Provisioned using AAA Server. ASN-GW PROV Provisioned using ASN Gateway. 147 | P a g e Designed for Operators, by Operators o Network Entry State. This provides an indication as to the connected "state" of the o Uptime. This is the Subscriber connected time. o Network Entry Type. This indicated the way the CPE connected to the Base station. o Authentication status. The authentication mode of the CPE o SNR Reporting Method. The reporting method used by the CPE to report downlink o Basic CID. Basic Connection ID o Primary CID. Primary Connection ID o Vendor ID. The part of the MAC Address used to determine the CPE vendor (OUI) o MAC Version. The WIMAX MAC version number Subscriber. channel status Figure 154 Sector Statistics Registered SS 148 | P a g e Designed for Operators, by Operators 3.6.3.3. Logging The Base Station contains several internal system management logs. The Web GUI provides the User with complete flexibility on performing several key actions on these logs. At the Main Web GUI Interface Screen select the Configuration Tab and then select the logging Main Menu Option. This will display all the system logs files (Figure 155). Figure 155 Main Menu Logging Options The logging Main Menu option contains four Main Menu Sub-Elements. These are:

remote. The User has the capability to define a remote server to forward a predefined log level. local. The User has the capability to define the minimum severity level to log. file. These are file actions that the User can perform. files. This describes the system log files. At the Main Web GUI Interface Screen select the Configuration Tab and then select the logging Main Menu Option and then the remote Main Menu Sub-Element. The User is now presented with a window that displays the remote Log Server Settings. There are two distinct groups to this window (Figure 156). The User is presented with a host Menu Sub-Element from the remote Main Menu Sub-Element level. If 149 | P a g e Designed for Operators, by Operators the User navigates to this level, then it will display a list of all the log servers that have been configured. The User can select to view the relevant details. Default Remote Log Server Settings. The User can view and hence configure the default minimum severity log level to forward to the remote server. This will apply to all remote servers which have a level of default. The User must be in Edit Mode to configure. In addition to the default level there are nine available options. These are:

info o none o debug o o notice o warning o error o critical o alert o emergency Remote Log Server Settings. For log servers that have configured the following information is displayed. To configure the User must be in Edit Mode. Once in Edit Mode, the User can <Add host>, delete or change the Severity Level of an existing host. o Hostname. If the User wants to add a remote server then they must enter the syslog remote server IP address or domain name. The User cannot edit the hostname for a syslog server that has been configured, this syslog must be deleted and then it can be re-added. When in the Edit Mode, there is a red box beside each hostname. If the User navigates to the red icon, then this will present the User with the ability to delete the hostname. o Security Level. The User can configure or re-configure the syslog server to that of the default level or any of the nine available options. Figure 156 Logging Remote Host Information 150 | P a g e Designed for Operators, by Operators At the Main Web GUI Interface Screen select the Configuration Tab and then select the logging Main Menu Option and then the local Main Menu Sub-Element. The User is now presented with a window that displays the local Log Server Settings. This only one distinct group to this window (Figure 157). The User can select to view the relevant details. Default Local Log Server Settings. The User can view and hence configure the default minimum severity log level for the local internal log server. This will apply to all local servers except those which have been configured in the logging local override configuration. The User must be in Edit Mode to configure. To define the default level there are one of nine available options to select. These are:

info o none o debug o o notice o warning o error o critical o alert o emergency Figure 157 Logging Local Information At the Main Web GUI Interface Screen select the Configuration Tab, then select the logging Main Menu option, then the local Main Menu Sub-Element and then override. The User can now is now presented with an option to increase or decrease the internal sys log per daemon/application which are internal to the Base Station (Figure 158). The User must be in Edit mode to configure. 151 | P a g e Figure 158 Logging Local Override When in Edit mode only one distinct group to this window is displayed. The User must <Add Source> and define the relevant App Name. The configurable options are:

Designed for Operators, by Operators Key Settings App Name o confd o wmdlpcClientd o r6mgrd o sectord o statsd o genactiond o snmpactiond o gpsmgrsyncd o swumgrd o sysmgrd Once the App Name has been selected then the User is presented with an Application Log Settings menu where the Severity Level can be configured. At the Main Web GUI Interface Screen select the Configuration Tab and then the logging Main Menu option and then the file Main Menu Sub-Element. The User is now presented with further Menu Sub-

Elements (Figure 159). The User now has top select one of the Menu Sub-Elements to be presented with an action. Figure 159 Logging File Information 152 | P a g e Designed for Operators, by Operators At the Main Web GUI Interface Screen select the Configuration Tab, select the logging Main Menu Option, then the file Main Menu Sub-Element, then rotation and finally force. This will force a reboot of the Base Station and the log file to effectively rotate and begin logging again. The rotate feature forces the logging to the relevant file to stop, it then compresses the file, effectively renames it (generally by appending a .1 to the end of the filename) and then starts the logging to a new file. E.g. the current sys log file is messages but at the last rotate action this file was rotated into messages.1.gz and the then logging started again to messages. An automatic rotation will occur when the file size reaches 5MBytes. There are no parameters to edit and the User simply has to select the Perform Command Menu Option to initiate the log file rotation (Figure 160). Figure 160 Logging File Rotation At the Main Web GUI Interface Screen select the Configuration Tab, then the logging Main Menu Option, then the file Main Menu Sub-Element and then delete. This option provides a means for the User to delete a log file (Figure 161). Two distinct window groups are presented to the User. These are:

Delete Log File. This simply provides a description of the actions. Delete Log File. The User simply selects the log file that they would like to delete. The list of available files is presented via a drop-down menu. The User does not have to be in Edit mode to select the log file. 153 | P a g e Designed for Operators, by Operators Figure 161 Logging File Delete At the Main Web GUI Interface Screen select the Configuration Tab, then select the logging Main Menu Option, then the file Main Menu Sub-Element and then upload. This option provides a means for the User to upload a log file to a server URL. Two distinct window groups are presented to the User. These are (Figure 162):

Upload Log File to Remote Server. This simply provides a description of the actions. Upload Log File. The User does not have to be in Edit mode to perform these actions. Prior to uploading the file, the User must ensure that an FTP Server has been configured and is running. The User has to select the following information:

o File to Upload. The User selects the log file that they would like to upload. The list of available files is presented via a drop down menu. o Destination URL. There are a variety of formats for the destination URL. These can be displayed if the User selects the "help" key. These URL formats are defined as:

ftp://[user[:password]@]hostname[:port]/filepath o o http://hostname[:port]/filepath o https://hostname[:port]/filepath Where [ ] indicates optional items. Thus, user:password@ is optional, and the :password part can be omitted o o o o o

[:port] is also optional Examples using ftp (you can substitute http or https):

ftp://myhost.com/filename ftp://myhost.com/directory/filename ftp://myhost.com:2323/directory/filename ftp://myname@myhost.com:2323/directoryname/filename ftp://myname:password@myhost.com:2323/directoryname/filename URL of remote source file; format is as follows:

o protocol://[user[:password]]@host[:port]/path o protocol can be ftp, http, or https 154 | P a g e Designed for Operators, by Operators Figure 162 Logging File Upload At the Main Web GUI Interface Screen select the Configuration Tab, then select the logging Main Menu option, and then the files main Menu Sub-Element. This option provides a list of all the sys log files on the Base Station (Figure 163). Figure 163 Logging File Filenames 155 | P a g e Designed for Operators, by Operators If the User selects a relevant file, then the characteristics of the file are displayed. The following information will be displayed for each file:

Key Settings o Filename o System Log Files o Size. This is the file size in bytes. o Modified. This was the date that the file was last modified. 3.6.3.4 SNMP Server Simple Network Management Protocol (SNMP) is an "Internet-standard protocol for managing devices on IP networks. The SNMP server exposes management data in the form of variables on the managed systems, which describe the system configuration (MIBs). These variables can then be queried and set by managing applications called Network Management Systems (NMS). To configure the SNMP Server, select the Configuration Tab, Edit Private and then select the snmp-server from Main Menu Option (Figure 164). Figure 164 SNMP-Server Configuration When in Edit mode, the configurable options are:

SNMP Agent (enable/disable). Enables SNMP agent software on Base Station for connection to an NMS (Network management System). SNMP v1 (enable/disable). Enables SNMP version 1 (SNMPv1) is the initial implementation of the SNMP protocol and the de-facto network management protocol. 156 | P a g e Designed for Operators, by Operators SNMP v2c (enable/disable). Enables SNMP version 2 (SNMPv2) which is the implementation of the SNMP protocol and includes performance, security and confidentiality updates. SNMP v3 (enable/disable). Enables SNMP version 3 (SNMPv3) which includes encoded community strings for improved security. Port (default 161). The SNMP agent receives requests by default on UDP port 161. The community sub-menu (Figure 165) allows the configuration of the community string (basic password) used for security for with SNMP. If the User wants to add or edit any of the existing community strings, then they must then select snmpCommunityTable and enter the Edit Mode (Edit Private or Edit Exclusive). The following options will be available:

<Add snmpCommunityEntry>. This allows addition of a new community string private. SNMP access which allows read-write permissions. public. SNMP access which allows read-only permissions. standard trap. Read-only permissions for sending SNMP traps. Figure 165 Community Sub-Menu If the User wants to add or edit any of the existing community strings, then they must then select enter the Edit Mode (Edit Private or Edit Exclusive). The following options will be available for each entry (Figure 166):

Key Settings o SNMP Community Index snmpCommunityEntry o SNMP Community Name. Name of the community string o SNMP Community Security Name. Level of access including read-write and read-only o SNMP Community Context Engine ID. o SNMP Community Context Name. o SNMP Community Transport Tag. o SNMP Community Storage Type. Default value is permanent 157 | P a g e Designed for Operators, by Operators Figure 166 snmpCommunityEntry Table The user sub-menu (Figure 167) allows the protection of SNMPv3 packets from the above threats by utilizing a concept of multiple users where each user provides secret keys for authentication and privacy. If the User wants to add or edit any of the existing user record, then they must then select user and enter the Edit Mode (Edit Private or Edit Exclusive). The following options will be available:

Key Settings o Usm User Engine ID o Usm User Name usmUserEntry o Usm User Security Name o Usm User Clone From. o Usm User Auth Protocol. o Usm User Auth Key Change. o Usm User Own Auth Key Change. o Usm User Priv Protocol. o Usm User Priv Key Change. o Usm User Own Priv Key Change. o Usm User Public. o Usm User Storage Type. Default is nonVolatile o Usm User Auth Key. 158 | P a g e Designed for Operators, by Operators Figure 167 SNMP User Configuration The notify sub-menu (Figure 168) configures the SNMP notification generation mechanism. If the User wants to add or edit any of the existing community strings, then they must then select snmpNotifyTable and enter the Edit Mode (Edit Private or Edit Exclusive). The following options will be available:

Key Settings o SNMP Notify Name o SNMP Notify Tag. o SNMP Notify Type. o SNMP Notify Storage Type. snmpNotifyEntry (Field entries are explained in Table 12 SNMP Notification Table) 159 | P a g e Designed for Operators, by Operators Figure 168 SNMP Notify Configuration Name Description Field Example SNMP Notify Name SNMP Notify Tag SNMP Notify Type A unique identifier used to index this table. 1-32 chars A tag value used to reference one or more entries in snmpTargetAddrTable. Example: std_trap Selects the type of notification to be generated for the entries in the snmpTargetAddrTable referenced by snmpNotifyTag:

trap(1) - Generates an SNMPv2c Trap PDU inform(2) - Generates an InformRequest PDU Example: trap SNMP Notify Storage Type String name assigned to the Base Station. Table 12 SNMP Notification Table The default value is nonVolatile. 160 | P a g e Designed for Operators, by Operators Figure 169 SNMP Trap Destination The trap destination sub-menu (Figure 169) specifies the network and transport layer attributes of notification destinations. Each row in this table is used to send traps to a different NMS. If the User wants to add or edit any of the existing trap destinations, then they must then select NMSAddress and enter the Edit Mode (Edit Private or Edit Exclusive). The following options will be available below:

Key Settings o NMS-Address snmpNotifyEntry (Field entries are explained in Table 13 Table 12 SNMP Notification Table) o Snmp Target Addr TDomain. o Snmp Target Addr TAddress. o Snmp Target Addr Timeout. o Snmp Target Addr TAddress. o Snmp Target Addr Retry Count. o Snmp Target Addr Tag List. o Snmp Target Addr Params. o Snmp Target Addr Storage Type. o Snmp Target Addr Engine ID. o Snmp Target Addr TMask. o Enabled. 161 | P a g e Designed for Operators, by Operators Name Description Name Description Name of the target snmpTargetAddrTable. This object indicates the transport type of the address contained in the snmpTargetAddrTAddress object. Specifies the target address, which consists of an IP address followed by a UDP port number. Sets a timeout value (in ticks) for the transmission of InformRequest PDU or TCP connection. The agent will wait this amount of time for a response to an InformRequest PDU or TCP connection before attempting again. Example: 1500 is 1.5 seconds Field Example 1-32 chars 1.3.6.1.6.1.1 is the domain for UDP Example:

127.0.0.1.0.162 Field Example Example: 3 Sets the number of times that the agent will resend an InformRequest PDU or attempt to establish a TCP connection before abandoning further attempts and logging an error in the agent log file. A list that provides the correlation between snmpTargetAddrTable and snmpNotifyTable. When generating a notification, the agent searches this list for the value contained in snmpNotifyTag. If the list contains this value, then the agent uses the information in this row to create a destination for the notification. For example:

std_trap Indexes the row in snmpTargetParamsTable that describes the security parameters to be used when sending the notification. If the row specified does not exist, the notification will not be sent. For example:

target_v2 Specifies how the row should be stored. Internal use only, leave blank. The default value is nonVolatile. 162 | P a g e SNMPTargetAddName SNMPTargetAddrTDomain SNMPTargetAddrTAddress SNMPTargetAddrTTimeout SNMPTargetAddrRetryCou nt SNMPTargetAddrTagList SNMPTargetAddrParams SNMPTargetAddrStorageT ype SNMPTargetAddrEngineID Designed for Operators, by Operators SNMPTargetAddrTMask Internal use only, leave blank. SNMPTargetAddrStorageT ype Enabled Internal use only ( Maximum message size) default 2048. This field allows trap sending to a given NMS to be paused. Table 13 SNMP Target Address Table 2048 true/false 3.6.3.5 Alarm Management The Quantum Base Station has advanced alarm and fault management capabilities. When a fault or event occurs, an alarm condition will be raised. An alarm is a persistent indication of a fault that clears only when the triggering condition has been resolved. To configure Alarm Management, select the Configuration Tab and then select the alarm Main Menu Option (Figure 170). When in View or Edit mode, the options are:

action. Allows acknowledgement, clearing and un-acknowledgment of alarms active. View a list of the active alarms Figure 170 Alarm Management To acknowledge, clear or un-acknowledge an alarm, select the action sub-Element (Figure 171). The User is now presented with a window that displays an operation to be performed on the following alarm-names. Voltage. Allows acknowledgement, clearing and un-acknowledgment of alarms Sector-Comm-Loss. Indicates if Sector is Up or Down. Temperature. Low, Hi or Normal Operating Temperature Sector-Down. View the active alarms GPS-Synch-Holdoff. Indicates if GPS is reliable or unreliable. GPS-Synch-Loss. Indicates if GPS is reliable or unreliable. Select the alarm type and click Perform to apply the action 163 | P a g e Designed for Operators, by Operators Figure 171 Alarm Action 164 | P a g e Designed for Operators, by Operators 4 Citizens Broadband Radio Service Operations (47 C.F.R. Part 96) All information provided herein including, but not limited to, feature content, releases, functionality, estimated dates, and timelines, has been prepared by Mercury Networks, LLC. for general information and documentation purposes only and is subject to change at any time. Including, without limitation, because of specific field conditions. Mercury Networks, LLC. is under no obligation and is making no commitments with regards to any of the information contained in the following section (4. Citizens Broadband Radio Service Operations). Mercury Networks, LLC. has made all reasonable effort to ensure that the information contained in the following section is adequate and free of material errors. Subject to applicable law, in no event will Mercury Networks, LLC. be liable for errors in this documentation, or for any damages including but not limited to direct, in-direct, incidental, or consequential, or any losses that may arise from use of this documentation or the information in it. For operations under FCC Part 96, Citizens Broadband Radio Service, the Quantum 6636 can me modified for use with the additional spectrum available in the CBRS band (3550-3700) through the combination of a firmware upgrade and use of a proprietary Domain Proxy application. For access to the necessary firmware and domain proxy applications, operators must contact Mercury Networks for assistance. The following sections outline Quantum 6636 operations under Part 96, the necessary configuration, and use of the domain proxy application. 4.1 Citizens Broadband Radio Service (CBRS) Overview Citizens Broadband Radio Service (CBRS) is a 150 MHz wide broadcast band of the 3.5 GHz band (3550 MHz to 3700 MHz) in the United States. In 2017, the US Federal Communications Commission (FCC) completed a process which began in 2012 to establish rules for commercial use of this band, while reserving parts of the band interference with US Navy radar systems and aircraft communications (otherwise known as 47 CFR Part 96). for the US Federal Government to limit On January 27, 2020, the FCC authorized full use of the CBRS band for wireless service provider commercialization without the restrictions to prevent interference with military use of the spectrum. Under the new rules, wireless carriers using CBRS might be able to deploy 5G mobile networks without having to acquire spectrum licenses. Existing 3.65 GHz licenses possessed by various operators will begin their transition from Part 90 to Part 96 in October of 2020. Unless the license being used is covered by a Part 90(z) Grandfathered Protection Zone registration, which may extend the use of the license temporarily beyond the anticipated October 2020 transition date, will be required to transition to CBRS for continued use of the Quantum 6636 product inside the US (see 47 CFR Subpart Z Wireless Broadband Services in the 3650-3700 MHz band for up-to-date information regarding the latest federal regulations). 4.1.2 CBRS Operations The Citizens Broadband Radio Service is governed by a three-tiered spectrum authorization framework to accommodate a variety of commercial uses on a shared basis with incumbent federal and non-federal users of the band in the US. Access and operations will be managed by a dynamic spectrum access system, conceptually similar to the databases used to manage Television White Spaces devices. The three tiers are: Incumbent Access, Priority Access, and General Authorized Access. 165 | P a g e Designed for Operators, by Operators Incumbent Access users include authorized federal and grandfathered fixed satellite service users currently operating in the 3.5 GHz Band. Under the rules promulgated by the FCC, these users, particularly including US Navy radar operators, will be protected from harmful interference from Priority Access and General Authorized Access users. Existing 36503700 MHz band operations

"are grandfathered for up to 5 years", with the FCC's Wireless Telecommunications Bureau and Office of Engineering and Technology charged with soliciting public comment on "the appropriate methodology for defining the grandfathered wireless protection zone contours". The Priority Access tier consists of Priority Access Licenses (PALs) that will be assigned using competitive bidding within the 3550-3650 MHz portion of the band. Each PAL is defined as a non-

renewable authorization to use a 10-megahertz channel in a single census tract for three-years. Up to seven total PALs may be assigned in any given census tract with up to four PALs going to any single applicant. Applicants may acquire up to two-consecutive PAL terms in any given license area during the first auction. The General Authorized Access tier is licensed-by-rule to permit open, flexible access to the band for the widest possible group of potential users. General Authorized Access users are permitted to use any portion of the 3550-3700 MHz band not assigned to a higher tier user and may also operate opportunistically on unused Priority Access channels. A Spectrum Access System (SAS) is used as an automated frequency coordinator that can manage spectrum sharing on a dynamic, as-needed bases across the three tiers of access. The Quantum 6636 can engage communications with and accept commands from a SAS utilizing the Mercury Networks Domain Proxy. A Domain Proxy (DP) is an entity engaging in communications with the SAS on behalf of multiple individual CBSDs or networks of CBSDs. The Domain Proxy can also provide a translational capability to interface legacy radio equipment in the 3650-3700 MHz band with a SAS to ensure compliance with Part 96 rules. regarding information More here:

https://cbrs.wirelessinnovation.org/. We highly encourage any operator who wishes to utilize the Quantum 6636 for deployment in a CBRS environment carefully review the standards available on the WinnForum site as they may change periodically. and Winnforum standards found FCC can be 4.1.3 Requirements for the Quantum 6636 to Operate in CBRS Whether you plan to operate with an Incumbent Access license, a Priority Access license, or a General Authorized Access license, the Quantum6636 can utilize the full 150 MHz available in CBRS (3550-3700 MHz), provided a few preparations have been made first:

1. The Quantum 6636 Base Station will need the latest CBRS compatible software build. You can learn more about upgrading the Base Station software in section 3.6 of this guide. a. The software will be issued by an authorized Mercury Networks support technician. To learn more about this process contact support@mercurynets.com. 2. Basic Base Station parameters will need to be configured prior to connecting the Quantum 6636 with the Mercury Networks Domain Proxy. This is covered in detail in section 4.2. 3. The Quantum 6636 Base Station will require the Mercury Networks Domain Proxy for use with an authorized SAS provider. To learn more about the Mercury Networks Domain Proxy, see section 4.3 of this guide. 166 | P a g e Designed for Operators, by Operators 4. All Quantum 6636 installations will need to be signed by a Certified Professional Installer (CPI) with a valid certificate loaded into the Mercury Networks Domain Proxy. To learn more about the Mercury Networks Domain Proxy, see section 4.3 of this guide. 4.2 Base Station Configuration for use with CBRS and the Mercury Networks Domain Proxy The following section will outline the basic configuration parameters that need to be established with the Quantum 6636 product prior to use with the Mercury Networks Domain Proxy. There are two methods for managing/configuring a Base Station:

1. Command Line Interface (CLI) 2. Graphical User Interface (GUI) Web Interface All configuration parameters are available through CLI. The CLI is recommended for configuring a Base Station for use in the CBRS band and with the Mercury Networks Domain Proxy. The CLI is accessible via the Base Station Console Interface using an appropriate terminal emulator, or via a Base Station ETH-1 port using either SSH or Telnet (Telnet is disabled by default). Refer to section 3 Quick Start Guide for additional information regarding initial configuration, and a full list of configurable parameters. The following commands assume you have read through section 3 and are prepared to use the CLI for issuing configuration commands to the Base Station. Items you will need to know prior to configuration are:

System IP address Sector IP address Management VLAN Antenna gain Antenna beadwidth Antenna downtilt Cable loss Host Name BSID Time Zone NTP Server Enter configuration mode and issue the following commands via CLI to configure the Quantum 6636:

1. configure 2. Connect to the Base Station via ETH-1. a. Default Base Station Management IP address (Host Name): 192.168.1.10 b. Default credentials are:

admin admin123 3. Gather the needed files for the software upgrade (contact support@mercurynets.com) 4. Perform the necessary software upgrade to both banks A and B 5. Run commands 167 | P a g e Designed for Operators, by Operators a. system interface ip address <new device ip> netmask <new device subnet mask>

default-gateway <new device gateway>

b. system interface mgmt-vlan vlan-enabled true vlan-id <new vlan>

This will change the IP address and VLAN immediately. It is recommended to make this change via the Console connection, so you dont lose access to the device. c. write memory 6. Once changes have been committed you will have to change your Ethernet adapter information and SSH to the new Management IP address and VLAN (if applicable) you just entered. 7. Enter configuration mode configure 8. Type sector advanced 1 to begin sector configuration then type the below commands a. wimax max-uplink-rate QAM64_5/6 b. wimax max-downlink-rate QAM64_5/6 c. wimax antenna-tx-mode MIMO-AB d. wimax auto-power-control open-loop e. wimax channel-bw 10MHz f. wimax dl-ul-frame-ratio 26:21 i. Options: 26:21, 29:18, 32:15, 35:12 g. Radio antenna-gain <applicable antenna gain>

h. Radio cable loss <applicable cable loss>

9. sector general 1 system ip address <IP address> netmask <netmask> gateway <gateway>

10. ctrl c 11. write memory The Quantum 6636 should now be configured for management access on your network. This will be required for the device to communicate with the Domain Proxy. Refer to section 3.6 of this guide for additional configuration options. 4.3 External Antennas For operations under Part 96, the Quantum 6636 can only be used in conjunction with the Mercury Networks 3.5GHz 2-Port Antenna (098-00459-0035) in a sectorized and cross-polarized configuration, or the Mercury Networks 3.5GHz 6-port Panel Antenna (099-00455-003). The following sections provide additional guidance for permissible antenna types and configurations for operations under Part 96. Be advised the conducted transmit power of the Quantum 6636 may need to be reduced to ensure the regulatory limit on transmitter EIRP is not exceeded. The installer must understand how to compute the effective antenna gain from the actual antenna gain and the feeder cable losses. The range of permissible values for maximum antenna gain and feeder cable losses are taken into consideration with the domain proxy, and calculations are performed to ensure that it is not possible for the installation to exceed the EIRP limit, when the appropriate values for antenna gain and cable feeder loss are entered into the domain proxy GUI. The Quantum 6600 platform adheres to all applicable EIRP limits for transmit power when operating in MIMO mode. 168 | P a g e Designed for Operators, by Operators 4.3.1 Mercury Networks 3.3-3.8GHz 2-Port Antenna (098-00459-035) The Mercury Networks 3.5GHz 2-Port Antenna (098-00459-0035) allows for a sectorized, cross polarized deployment. For operations under Part 96 that involve a single Quantum 6636 deployment, or OmniWave deployment, the following antenna array and configuration should be used to prevent overlap and interference. Antenna specifications can be found on the following table:

2-port antenna installation should be sectorized, cross polarized, and arranged so that the 3dB band does not overlap each other. 169 | P a g e Designed for Operators, by Operators The recommended azimuth for a standard OmniWave deployment arranges the antennas in a manner that separation between the antennas will prevent overlap and interference. Antennas must be arranged in the following deployment. Sector 1 Azimuth: 0 (true north) Sector 2 Azimuth: 120 Sector 3 Azimuth: 240 3dB Beamwidth The azimuthal beamwidth between 3dB down angles shall be 90 degrees nominal. The elevation beamwidth between 3dB down angles is 8 degrees minimum Polarization Each array is +/-45 degree dual slant 170 | P a g e Designed for Operators, by Operators 4.3.2 Mercury Networks 3.3-3.8GHz 6-Port Antenna (098-00455-003) The Mercury Networks 3.5GHz 6-Port Antenna (099-00455-003) allows for a directional deployment of a Quantum 6636. Antenna specifications are found in the following table:

171 | P a g e Designed for Operators, by Operators The recommended azimuth for a standard three Quantum 6636 deployment arranges the antennas in a manner that separation between the antennas will prevent overlap and interference. Antennas must be arranged in the following deployment. Sector 1 Azimuth: 0 (true north) Sector 2 Azimuth: 120 Sector 3 Azimuth: 240 3dB Beamwidth The azimuthal beamwidth between 3dB down angles shall be 90 degrees nominal. The elevation beamwidth between 3dB down angles is 8 degrees minimum Polarization Each array is +/-45 degree dual slant, cross-polarized with no phase-shifting Alternative arrangements are possible, so long as each antenna has 120 degrees of separation from each azimuth measurement. 4.4 The Mercury Networks Domain Proxy The information contained in this section will instruct you on how to connect your Quantum 6636 to the Mercury Networks Domain Proxy as a CBSD for use in the Citizens Broadband Radio Service (47 C.F.R. Part 96) band. This section is assuming the steps in section 4.2 have been completed, as well as a review of section 3.6. You MUST have a GPS antenna connected and functional, and the Quantum 6636 MUST be obtaining GPS synchronization for the SAS to issue commands to the Base Station. 172 | P a g e Designed for Operators, by Operators A Certified Professional Installer (CPI) is required for activation of any CBSD for use with a SAS. The Quantum 6636, as with any CBSD, will not transmit until all necessary configuration parameters have been input into the Domain Proxy, and a CPI has signed off on the physical installation of the CBSD. The Mercury Networks Domain Proxy is designed to act as a management platform for the Quantum 6636 product line, as well as a bridge for multiple Base Stations to communicate with a SAS. It possesses an intuitive, web-based GUI that will assist with commands issued by the SAS. 4.3.1 Accessing the Mercury Networks Domain Proxy The Mercury Networks Domain Proxy can be accessed through a web browser by pointing your browser at the URL established for the Domain Proxy by the Mercury Networks support team. Once the page loads the User is presented with a login screen. Enter your E-mail Address and Password to get started (Figure 172). Figure 172 Domain Proxy Login Once login credentials are successfully entered, the User is presented with a welcome screen, and tabs across the top of the screen for navigation (Figure 173). The navigation tabs include:

Devices Displays a list of all CBSDs entered into the Domain Proxy CPIs Displays a list of all Certified Professional Installers capable of signing-off on a CBSD installation. (Note: certificates for CPIs can be managed in the Domain Proxy, this will be covered later in this section). 173 | P a g e Designed for Operators, by Operators Logs Displays operational logs for the Domain Proxy to provide information on CBSD and Domain Proxy communication with the SAS. Logout Logs the User out of the Domain Proxy. Figure 173 Welcome Screen 4.3.2 Domain Proxy Devices CBSDs can be managed through the domain proxy. When the Devices tab is selected the User will be presented with a list of all unregistered and registered CBSDs that have been added to the Domain Proxy for management. There are 3 navigation options in the Devices menu:

Map Represented by a green globe. Displays a map with locations for all registered CBSDs based on GPS coordinates. Add Device Represented by a blue +. Add a new CBSD to the Domain Proxy Device ID Provides additional information for existing registered devices including configuration parameters, SAS Status, CBSD SAS ID, SAS Vendor, and the date of last update. Figure 174 Devices Sub-menu 174 | P a g e Designed for Operators, by Operators 4.3.2.1 Map View The Map View shows Users the geographic location for all CBSDs. A pin drop, which represents the CBSDs location, can be clicked on for additional information including the Device ID, Device Status, and SAS ID. 4.3.2.2 Device ID View The Device ID View shows specific information for each CBSD managed by the Domain Proxy. This information includes a summary of the devices status with the SAS, FCC & CBSD information, installation parameters, antenna information, measurement capabilities, air interface information, CBSD hardware & software information, and a map view specific to the CBSD selected (Figures 176 and 177). Figure 175 Device ID View 175 | P a g e Designed for Operators, by Operators Figure 176 Device ID View Continued 4.3.2.3 Adding a Device Clicking the blue + button on the devices sub-menu opens the New Device screen (Figure 178). The Quantum 6636 will need to have a management IP configured before you can add the device to the Domain Proxy. Once the management IP address is known, add it under the IP field, followed by the SNMP Community (by default this is private for most Quantum 6636 Base Stations). Once the IP and the SNMP community have been entered, select Query. Figure 177 New Device The User will be presented with a summary screen displaying all parameters automatically imported to the Domain Proxy (Figure 179 and 180). The following remaining parameters will need to be provided before the Quantum 6636 can be successfully added and registered to the Domain Proxy:

Height (meters) Height Above Average Terrain The FCC currently provides a HAAT calculator to assist users with obtaining and entering this data (https://www.fcc.gov/media/radio/haat-

calculator). 176 | P a g e Designed for Operators, by Operators Antenna Azimuth The directional heading for the Quantum 6636 antenna. 0-360 degrees where 0 degrees would be used for an omniwave deployment. Antenna Downtilt the mechanical downtilt of the Quantum 6636 antenna. Antenna Beamwidth the degrees for the antennas horizontal plane coverage. Figure 178 New Device Parameters Figure 179 New Device Parameters Continued 177 | P a g e Designed for Operators, by Operators Once all remaining parameters have been keyed, select an Endpoint (SAS) for registration and then select Save. The User will then be presented with a summary screen where they can edit existing parameters, remove the device if it was keyed in error, or Sign & Register the device to the Domain Proxy (Figure 181). Note: If the User signed into the Domain Proxy is not a CPI, they will only have the ability to register the device. A CPI will still need to sign the device for communication with the SAS. Figure 180 Device Summary Once the Quantum 6636 has been signed and registered, it is ready to query the SAS for a grant to transmit. This can be done by selecting Grants next to the Device button in the summary screen. 4.3.2.4 Obtaining a Grant from the SAS In the Grants tab, select New to begin the spectrum inquiry process (Figure 182). Using the drop-

down menu select the frequency to perform the spectrum inquiry and then select save. 178 | P a g e Designed for Operators, by Operators Figure 181 Spectrum Inquiry Screen Once a grant has been received an updated SAS status will be displayed (Figure 183). The Quantum 6636 should now receive instructions from the Domain Proxy for transmit. If the requested frequency is not available an error will be displayed. Figure 182 SAS Status Update 4.3.3 CPIs (Certified Professional Installers) The CBRS band provides for a sophisticated multi-tier shared spectrum with protected incumbents. Pursuant to the FCC, the majority of CBRS radio transceivers or Citizens Broadband Service Devices

(CBSDs) must be installed by a CPI in order to lawfully operate within the designated spectrum of CBRS. In order to meet the FCC Part 96 rules, CPIs must be trained and currently certified. The WInnForums the CPI Accreditation Standard provides a working outline of how training programs for CPI will be achieved as well as what CBSDs need certification, CPI responsibilities, and more. CPIs using the Mercury Networks Domain Proxy can be managed through the CPIs menu. 4.3.3.1 Adding a New CPI In the CPIs menu, a new CPI can be added by selecting Create in the upper right-hand corner (Figure 184). 179 | P a g e Designed for Operators, by Operators Figure 183 CPI List A new CPI will need the unique CPI name, CPI ID, CPI password, and P12 certificate issued by the accrediting body. Certificates only need to be uploaded once and can be centrally managed by the Domain Proxy until they expire. Once the appropriate credentials have been added, select Save to add the CPI (Figure 185). Figure 184 New CPI 4.3.4 Logs Logs can be used to trouble-shoot and validate communication with the SAS. Output for all SAS communication is displayed under the Logs menu in the Domain Proxy (Figure 186). 180 | P a g e Designed for Operators, by Operators Figure 185 Operational Logs 181 | P a g e Designed for Operators, by Operators Appendix A Capacity Tables We present here a set of tables specifying the raw (MAC-layer) throughput of a Mercury Quantum Family base Station for 5, 7 and 10MHz, under ideal conditions, corresponding to the maximum achievable performance that can be achieved using IEEE 802.16e per channel bandwidth and TDD configuration ratio. All results assume PUSC, a MAP size of 4 symbols, and 1 preamble symbol. The numbers represent the maximum MAC layer performance using all sub-channels and exclude Ethernet Layer 2 or higher layer overheads. Values are in units of Mbps. Note that these results are specific to the stated configuration under ideal conditions and should be considered indicative of expected results. Actual results will vary depending upon the actual configuration, error rate, environment, and numerous other factors. 10MHz 5MHz Downlink Uplink Bi-Dir Downlink Uplink MCS Rate 64QAM-5/6 21.60 64QAM-3/4 19.44 64QAM-2/3 17.28 64QAM-1/2 12.96 16QAM-3/4 12.96 16QAM-1/2 8.64 QPSK-3/4 6.48 QPSK-1/2 4.32 5.04 4.54 4.03 3.02 3.02 2.02 1.51 1.01 25.44 22.90 20.35 15.26 15.26 10.18 7.63 5.09 10.8 9.72 8.64 6.48 6.48 4.32 3.24 2.16 2.45 2.2 1.96 1.47 1.47 0.98 0.73 0.49 Bi-Dir 13.25 11.92 10.6 7.95 7.95 5.3 3.97 2.65 Table 14 Max Throughput 35:12 - 74%:26%

182 | P a g e Designed for Operators, by Operators 10MHz 5MHz Downlink Uplink Bi-Dir Downlink Uplink Table 15 Max Throughput - 32:15 - 68%:32%

10MHz 5MHz MCS Rate Downlink Uplink Bi-Dir Downlink Uplink 64QAM-5/6 17.28 8.40 25.68 8.64 MCS Rate 64QAM-5/6 18.72 64QAM-3/4 16.85 64QAM-2/3 14.98 64QAM-1/2 11.23 16QAM-3/4 11.23 16QAM-1/2 7.49 QPSK-3/4 5.62 QPSK-1/2 3.74 64QAM-3/4 15.55 64QAM-2/3 13.82 64QAM-1/2 10.37 16QAM-3/4 10.37 16QAM-1/2 6.91 QPSK-3/4 5.18 QPSK-1/2 3.46 6.72 6.05 5.38 4.03 4.03 2.69 2.02 1.34 7.56 6.72 5.04 5.04 3.36 2.52 1.68 25.44 22.90 20.35 15.26 15.26 10.18 7.63 5.09 23.11 20.54 15.41 15.41 10.27 7.70 5.14 9.36 8.42 7.49 5.62 5.62 3.74 2.81 1.87 7.78 6.91 5.18 5.18 3.46 2.59 1.73 3.26 2.94 2.61 1.96 1.96 1.31 0.98 0.65 4.08 3.67 3.26 2.45 2.45 1.63 1.22 0.82 Bi-Dir 12.62 11.36 10.10 7.57 7.57 5.05 3.79 2.52 Bi-Dir 12.72 11.45 10.18 7.63 7.63 5.09 3.82 2.54 Table 16 Max Throughput - 29:18 - 62%:38%

183 | P a g e Designed for Operators, by Operators 10MHz 5MHz MCS Rate Downlink Uplink Bi-Dir Downlink Uplink 64QAM-5/6 14.40 10.08 24.48 64QAM-3/4 12.96 64QAM-2/3 11.52 64QAM-1/2 8.64 16QAM-3/4 8.64 16QAM-1/2 5.76 QPSK-3/4 4.32 QPSK-1/2 2.88 9.07 8.06 6.05 6.05 4.03 3.02 2.02 22.03 19.58 14.69 14.69 9.79 7.34 4.90 7.20 6.48 5.76 4.32 4.32 2.88 2.16 1.44 4.90 4.41 3.92 2.94 2.94 1.96 1.47 0.98 Bi-Dir 12.10 10.89 9.68 7.26 7.26 4.84 3.63 2.42 Table 17 Max Throughput - 26:21 - 55%:45%

7MHz Downlink Uplink Bi-Dir MCS Rate 64QAM-5/6 11.5 64QAM-3/4 10.4 64QAM-2/3 9.2 16QAM-3/4 6.9 16QAM-1/2 4.6 QPSK-3/4 QPSK-1/2 3.5 2.3 5.0 4.5 4.0 3.0 2.0 1.5 1.0 16.6 14.9 13.2 9.9 6.6 5.0 3.3 Table 18 Max Throughput - 21:12 - 64%:36%

184 | P a g e Designed for Operators, by Operators 7MHz Downlink Uplink Bi-Dir MCS Rate 64QAM-5/6 13.0 64QAM-3/4 11.7 64QAM-2/3 10.4 16QAM-3/4 7.8 16QAM-1/2 5.2 QPSK-3/4 QPSK-1/2 3.9 2.6 MCS Rate 64QAM-5/6 8.6 64QAM-3/4 7.8 64QAM-2/3 6.9 16QAM-3/4 5.2 16QAM-1/2 3.5 QPSK-3/4 QPSK-1/2 2.6 1.7 3.4 3.0 2.7 2.0 1.3 1.0 0.7 6.7 6.0 5.4 4.0 2.7 2.0 1.3 16.3 14.7 13.1 9.8 6.5 4.9 3.3 15.4 13.8 12.3 9.2 6.1 4.6 3.1 Table 19 Max Throughput - 23:9 - 72%:28%

7MHz Downlink Uplink Bi-Dir Table 20 Max Throughput - 17:15 - 53%:47%

185 | P a g e Designed for Operators, by Operators Appendix B Changes Requiring a Reboot gps enabled sector general 1 o system bs-id o system cell-id o system cs-type o system ip address o system ip netmask o system ip gateway o system mode o system downlink-broadcast-rate o system block-dhcp-downlink-broadcasts o system cpe-to-cpe-relay-enabled o system cpe-to-cpe-brodcast-relay-enabled sector advanced 1 o wimax auto-power-control o wimax dl-ul-frame-ratio o wimax max-distance o wimax large-map-enabled o security ak-lifetime o security enabled o security tek-lifetime system interface mgmt-vlan vlan-enabled system interface mgmt-vlan vlan-id system interface mgmt-vlan vlan-priority system base-station asn-gateway ip-address system base-station asn-gateway port-number system base-station radius ip-address system base-station radius port-number system base-station radius secret system base-station mode 186 | P a g e Designed for Operators, by Operators Appendix C Limited Warranty Statements Hardware Mercury, Inc. (Mercury or the Company) warrants to the original end-user (Customer) that this hardware product will conform in all material respects to the specifications provided with the hardware and will be free from defects in workmanship and materials, under normal use and service, for a period of 365 days from the date of original shipment by Mercury. Mercury's sole obligation under this limited warranty shall be, at Mercury's option, to repair the defective product or part, deliver to Customer an equivalent product or part to replace the defective item, or if neither of the two foregoing options is reasonably possible, refund to Customer the purchase price paid for the defective product. All products that are replaced will become the property of Mercury. Replacement products may be new or reconditioned. Mercury's obligations hereunder are conditioned upon the returned of affected articles in accordance with Mercury's Return Material Authorization (RMA) procedures. The above warranty will also apply to any replaced or repaired product for 90 days from the date of shipment from Mercury of the replaced or repaired product, or the remainder of the initial warranty period, whichever is longer. Software Mercury warrants to the Customer that for a period of ninety (90) days from your receipt of the Product as demonstrated by written records (the Warranty Period) the Software will perform substantially in accordance with the Documentation. If the Software fails to comply with the warranty set forth above, your exclusive remedy will be, at the option of Mercury (i) a reasonable effort by Mercury to make the Software perform substantially in accordance with the Documentation, or (ii) return of the purchase price. This limited warranty applies only if you return all copies of the Product, together with proof of purchase, to Mercury during the Warranty Period. This limited warranty is VOID if failure of the Software is due to modification of the Software not made by Mercury, or the abuse or misapplication of the Software. MERCURY DOES NOT WARRANT THAT THE SOFTWARE IS ERROR FREE, THAT THE CUSTOMER WILL BE ABLE TO OPERATE THE SOFTWARE WITHOUT PROBLEMS OR INTERRUPTIONS OR THAT THE SOFTWARE OR ANY EQUIPMENT, SYSTEM OR NETWORK ON WHICH THE SOFTWARE IS USED WILL BE FREE OF VULNERABILITY TO INTRUSION OR ATTACK. Additional Conditions Notwithstanding anything else herein or otherwise, Mercury reserves the right to establish amendments to its RMA Policy from time to time. Further, Mercury Technical Support may prefer to troubleshoot the wireless link with an onsite Customer technician while the Products are in their original non-conforming state. This process might assist Customer in understanding and troubleshooting the issue. If Mercury was not afforded the opportunity to troubleshoot an allegedly non-conforming Product in original non-

conforming state, Mercury may approve or reject an RMA request in its sole discretion. 187 | P a g e Designed for Operators, by Operators No Fault Found Notwithstanding sections above, if Mercury cannot duplicate any alleged non-conformity, the Product will be returned to the Customer as "No Fault Found." Mercury reserves the right to charge a testing fee in connection with a returned product that Mercury determines as No Fault Found, and any such payment must be received by Mercury prior to return shipment of the applicable Product to Customer. Warranty Limitations Mercurys warranties do not apply to any product (hardware or software) which has (a) been subjected to abuse, misuse, neglect, accident, or mishandling, (b) been opened, repaired, modified, or altered by anyone other than Mercury, (c) been used for or subjected to applications, environments, or physical or electrical stress or conditions other than as intended and recommended by Mercury, (d) been improperly stored, transported, installed, or used, or (e) had its serial number or other identification markings altered or removed. Warranty Disclaimer PURWAVES SPECIFIC WARRANTIES SUMMARIZED ABOVE ARE THE ONLY WARRANTIES GIVEN BY MERCURY WITH RESPECT TO ITS PRODUCTS (HARDWARE AND SOFTWARE) AND ARE GIVEN IN LIEU OF ANY AND ALL OTHER WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY, OR ARISING BY CUSTOM, TRADE USAGE, OR COURSE OF DEALING, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND MERCURY DISCLAIMS ANY AND ALL OTHER WARRANTIES TO THE MAXIMUM EXTENT PERMITTED BY LAW. Without limiting the generality of the foregoing sentence, Mercury makes no warranty or representation, either expressed or implied, as to, and disclaims all liability and responsibility for, (a) the operation, compliance, labeling, or packaging of any of its products under the laws of any jurisdiction outside of the United States of America and (b) the regulatory compliance of any products in any jurisdiction in which it has not specifically identified compliance or the use of any product in any jurisdiction in any manner other than as contemplated in the regulatory certifications and approvals for that product in that jurisdiction. To the extent an implied warranty cannot be excluded, such warranty is limited in duration to the warranty period. The disclaimer and exclusion apply even if the express warranty fails of its essential purpose. Obtaining Warranty Service Customer must contact the Company, by sending an e-mail to support@mercurynets.com to obtain warranty service authorization. When contacting Mercury for support, please be prepared to provide the product description and serial number and a description of the problem. The Customer will be expected to complete a Return Material Authorization (RMA) form to initiate the request. Full instructions as to how to complete and where to send the form are provided on the form. Date of proof of purchase from Mercury will be required. Products returned to Mercury Inc. must be pre-authorized by Mercury with a Return Material Authorization (RMA) number and sent prepaid and packaged appropriately for safe shipment. The Customer requesting the RMA will be the exporter. The exporter is responsible to ship RMA equipment 188 | P a g e Designed for Operators, by Operators to Mercurys address and has to bear the cost and risk involved in bringing the goods to Mercurys location. Risk of loss in return shipment will be borne by Customer, and it is recommended that returned goods be insured and/or sent by a method that provides for tracking of the package. Responsibility for loss or damage does not transfer to Mercury until the returned item is received by Mercury. Provided that Mercury determines that the item is actually defective, the repaired or replaced item will be shipped to Customer, at Mercury's expense, (1) not later than thirty (30) days after Mercury receives the defective product or (2) to the terms of a separate written agreement with Mercury. If the allegedly non-conforming Product is not received by Mercury within thirty (30) days of Customer initiating the RMA request, the RMA process for that Product will be deemed cancelled. You may also obtain support@mercurynets.com referencing their assigned RMA Number(s). the status of their RMA request(s) by sending an e-mail to No product will be accepted for repair or replacement by Mercury without a RMA number. The product must be returned to Mercury, properly packaged to prevent damage, shipping and handling charges prepaid, with the RMA number prominently displayed on the outside of the container. If Mercury determines that a returned product is not defective or is not covered by the terms of the warranty, the Customer will be charged a service charge and return shipping charges. RMA Related Issue Under Warranty Repair and return No charge, Mercury Networks pays Shipment of unit to Mercury Networks Customer pays Regular shipment to customer Expedited shipment to customer No fault found No charge, Mercury Networks pays Customer pays the additional cost of the expedited shipping Mercury Networks reserves the right to levy a charge Warranty for repaired and/or replaced product Remainder of the original warranty or 90 days Table 21 Summary of Mercury RMA Conditions and Changes Assistance For assistance, contact your nearest Mercury Networks Sales and Service office. Additional information is available on the Mercury Networks website at http://www.mercurynets.com. For Customer Service call: +1-888-909-6717, or Email: support@mercurynets.com. 189 | P a g e Designed for Operators, by Operators 190 | P a g e

Model QUANTUM 6636 Base Station, 3.65 GHz PWN #099-00701-036 Serial # 102125 Revision A MAC 00-1D-3F-00-0F-5C FCC ID: XN3-QUANTUM 6636 IC: 8974A-QUANTUM 6636 PureWave Networks ah 2660 Marine Way Oo;

Mountain View, CA 94043 PureWave support@PWNETS.com vetworks Model QUANTUM 6625 Rase Station, 2.5 GH2 PWN #099-00490-025 Serial # 100386 Revision H D-8F-00-0!

Mercury Networks, LLC. 1100 Walnut St, Suite 2050 Kansas City, Missouri 64106 Authorization on Behalf of Mercury Networks, LLC. For the US Federal Communications Commission Office of Engineering and Technology and Other FCC Programs Offices 1. I, Garrett R. Wiseman, am the CEO of Mercury Networks, LLC and Applicant/Grantee Contact of Record for Mercury Networks, LLC. I am duly authorized by Mercury Networks, LLC. to make this Authorization on Mercury Networks, LLC.s behalf. 2. This Authorization will designate the person named below to act on my behalf and on behalf of Mercury Networks, LLC. as authorized agent and representative, until further notice, with the additional power to designate one or more third-party agents for Mercury Networks, LLC. with regard to particular matters and applications. All acts carried out and requests made by this named representative relating to any matter before the FCC, including requests for confidentiality, shall have the same effect as mine. Name:

Title:

Address:

Telephone:

E-mail:

Matthew Sams Chief of Staff Mercury Networks, LLC. 1100 Walnut St, Suite 2050 Kansas City, MO 64106

(888) 909-6717 matthew.sams@mercurywireless.com 3. Questions about the scope and effect of this Authorization should be addressed as follows:

Garrett R. Wiseman Mercury Networks, LLC. 1100 Walnut St, Suite 2050 Kansas City, MO 64106

(888) 909-6717 garrett.wiseman@mercurywireless.com I declare under penalty of perjury that the foregoing is true and correct, and that this Authorization was executed in Kansas City, Missouri on the date indicated below my signature. 4. ________________________________ Signature Garrett R. Wiseman, CEO Mercury Networks, LLC. Date: 9 September, 2020

Mercury Networks, LLC. 1100 Walnut St, Suite 2050 Kansas City, Missouri 64106 Date: September 17, 2020 Federal Communications Commission Equipment Authorization Branch 7435 Oakland Mills Road Columbia, MD 21046 FCC ID: XN3-QUANTUM6636 Subject: Statement of Compliance with KBD 940060 To whom it may concern, We, Mercury Networks, LLC., hereby attest that the firmware upgrade made available to the Quantum 6636 product will allow the device to operate within the parameters outlined in FCC CFR 47 Part 96, as well as OET KDB 940660, Certification and Test Procedures for Citizens Broadband Radio Service Devices Authorized under Part 96. Specific test parameters and system capabilities are outlined below:

Application for authorization as Category B CBSD per Section 96.49 Capability of two-way transmission and operation in the entire 3550-3700 MHz band Test mode and radio management o Compel the device-under-test to operate on a channel selectable by test personnel o Vary the output power from minimum to maximum EIRP and set it to a desired level o As needed, continuously transmit a modulated signal (i.e with no time bursting or signal gating applied) Enter all required SAS registration Information via a Domain Proxy server View all information provided to the radio by the SAS Force the DUT to stop operations on a specific channel and/or move to another channel Geo-location to an accuracy of +/-50 m horizontal and +/-3 m of elevation. Signal level reporting Frequency reporting CBSD Management Software (Domain Proxy) data collection capabilities Antenna height AGL (m) CBSD class (Category B) Requested authorization status (PAL or GAA) FCC ID Call sign (PALs only) Geographic location User contact info Air interference technology Serial #

Antenna gain Antenna beamwidth Antenna azimuth Antenna downtilt CBSD General Requirements Phone: (888) 909-6717 Fax: (785) 748-4624 matthew.sams@mercurywireless.com Mercury Networks, LLC. 1100 Walnut St, Suite 2050 Kansas City, Missouri 64106 CBSD will only transmit after it receives authorization from SAS CBSD will change operating power and/or channel in response to command from SAS CBSD will transmit at a power level less than or equal to the maximum power level approved by SAs CBSD will transmit with a bandwidth less than or equal to SAS specified bandwidth CBSD will transmit on SAS specified frequency CBSD will stop transmission in response to a command from SAS, within a period as required by Part 96 CBSD will send measurement in response to command from SAS CBSD will notify SAS via Domain Proxy of a new location when it is beyond the required distance parameter (+/-50 m) within the required time frame CBSD will be capable of reporting signal level (measurement data) and frequency to SAS via Domain Proxy When communication to SAS/Domain Proxy is lost, the CBSD will:

o Immediately stop transmission after expiration of heartbeat timeout o Re-establish its connection to the SAS via Domain Proxy Sincerely, Matthew Sams Chief of Staff Mercury Networks, LLC. Phone: (888) 909-6717 Fax: (785) 748-4624 matthew.sams@mercurywireless.com

Mercury Networks, LLC. 1100 Walnut St, Suite 2050 Kansas City, Missouri 64106 Date: September 30, 2020 Federal Communications Commission Equipment Authorization Branch 7435 Oakland Mills Road Columbia, MD 21046 FCC ID: XN3-QUANTUM 6636 Subject: Request for Confidentiality To whom it may concern:

Long Term Confidentiality Pursuant to Sections 0.457 and 0.459 of the Commissions Rules, we hereby respectfully request confidential treatment of information accompanying this application as outlined below:

Block Diagrams Schematics Operational Description Part List Tune-up Info Internal Pictures Short Term Confidentiality Pursuant to Sections 0.457 and 0.459 of the Commissions Rules, we hereby respectfully request short-

term confidential treatment of information accompanying this application as outlined below until 180 days after the Grant Date of the Equipment Authorization in order to ensure sensitive business information remains confidential until the actual marketing of the device. User Manuals Justification for requesting confidentiality for internal photographs:

The product is a non-consumer WiMAX base station transmitter that is installed on top of poles, in fenced in areas of rooftops and in other locations not accessible to anyone but authorized installation and repair personnel. Access is made difficult both for security purposes and for RF safety considerations. The internal photographs for a microwave transmitter yield a lot of design information to a prospective competitor that would otherwise not be accessible. The schematics and block diagrams are routinely kept confidential, but the internal photographs show IC numbers and part numbers which tell a great deal about the reference designs that are used, making it easier to reverse engineer the design. The photographs also reveal critical information regarding interconnection of subsystems (by following PCB traces shown in the photos). Finally, the photos show how the circuits are packaged and fit into the housing, which can be a challenge for the correct operation of microwave circuits. These documents contain detailed system and equipment description and related information about the product that Mercury Networks considers to be proprietary, confidential, and a custom design and, otherwise, would not release to the public. Since this design is a basis from which future technological products may evolve, Mercury Networks considers that this information would be of benefit to its competitors, and that disclosure of the information in these documents would give Internal photograph. Phone: (888) 909-6717 Fax: (785) 748-4624 matthew.sams@mercurywireless.com Mercury Networks, LLC. 1100 Walnut St, Suite 2050 Kansas City, Missouri 64106 If you have questions or need further information, please contact the undersigned. Sincerely, Applicants company name Applicants company address Signature Email Phone

: Matthew Sams / Chief of Staff

: matthew.sams@mercurywireless.com

: (888) 909-6717

: Mercury Networks, LLC.

: 1100 Main St. Suite 2050, Kansas City, MO 64106, USA Phone: (888) 909-6717 Fax: (785) 748-4624 matthew.sams@mercurywireless.com

Mercury Networks, LLC. 1100 Walnut St, Suite 2050 Kansas City, Missouri 64106 Date: September 17, 2020 Subject: Permissive change application for FCC 47 CFR Part 96 3550-3700 MHz radio Federal Communications Commission Equipment Authorization Branch 7435 Oakland Mills Road Columbia, MD 21046 Applicant:

Equipment:

Model:

FCC ID:

Mercury Networks, LLC Part 90 3.65 GHz Base Station QUANTUM 6636 XN3-QUANTUM 6636 To whom it may concern, Mercury Networks LLC. is requesting authorization to upgrade their certified radio operating in the 3650-3700 MHz band to operate in 3550-3700 MHz band under FCC 47 CFR Part 96 (Citizens Broadband Radio Service) rules. Mercury Networks has a new firmware build that can be loaded onto its existing Quantum 6636 radios. The change is software only, no hardware changes are needed to enable the additional 100Mhz of spectrum allocated as part of FCC 47 CFR Part 96 Citizens Broadband Radio Service. This updated firmware, in combination with a Domain Proxy developed for use with the Quantum 6636 product, will allow operators to continue use of the product once Part 90(z) rules sunset. If you have any questions or need further information, please contact the undersigned. Sincerely, Matthew Sams Chief of Staff Mercury Networks, LLC. Phone: (888) 909-6717 Fax: (785) 748-4624 matthew.sams@mercurywireless.com

Mercury Networks, LLC. 1100 Walnut St, Suite 2050 Kansas City, Missouri 64106 9/17/2020 Federal Communications Commission 7435 Oakland Mills Road Columbia, MD 21046 To whom it may concern:

Mercury Networks, LLC., hereby requests a Permissive Change Class II of the radio equipment certification for the product name certification number, FCC ID: XN3-QUANTUM6636. This product differs from the originally approved product in the following manner:

(a) Associated digital circuitry. There are no changes.

(b) Functional capabilities. The following functional capabilities are changed through a software upgrade made to the Quantum 6636 equipment:

a. Capability of two-way transmission and operation in the 3550-3700 MHz Citizens Broadband Radio Service (CBRS) band. b. Allow the device to operate within the parameters outlined in FCC CFR 47 Part 96, as well as OET KDB 940660.

(c) Antenna Characteristics. There are no changes.

(d) Cosmetic differences There are no changes. I do attest that the Field strength and/or RF Output readings remained the same or are lower than the originally approved product and that they did not increase therefore qualifying this product for this application type. Sincerely, Matthew Sams Chief of Staff Mercury Networks, LLC. 1100 Walnut St, Suite 2050 Kansas City, Missouri 64106 1

Mercury Networks, LLC. 1100 Walnut St, Suite 2050 Kansas City, Missouri 64106 Date: September 17, 2020 Federal Communications Commission Equipment Authorization Branch 7435 Oakland Mills Road Columbia, MD 21046 Subject: Professional Installation Declaration To whom it may concern, Please be advised that due to the unique market and function targeted by this product, this product will require special trained professionals for configuration and installation, otherwise known as a Certified Professional Installer (CPI), through an WInnForum Approved CPI Training Program. We further declare that the product will be distributed through a controlled distribution channel which has special trained professionals to advise on installation of this product and will not be sold directly to the general public through a retail store. Sincerely, Applicants company name Applicants company address Signature Email Phone

: Matthew Sams / Chief of Staff

: matthew.sams@mercurywireless.com

: (888) 909-6717

: Mercury Networks, LLC.

: 1100 Walnut St, Suite 2050, Kansas City, MO 64106, USA Phone: (888) 909-6717 Fax: (785) 748-4624 matthew.sams@mercurywireless.com