all | frequencies |
|
|
|
|
exhibits | applications |
---|---|---|---|---|---|---|---|
manual | photos | label |
app s | submitted / available | |||||||
---|---|---|---|---|---|---|---|---|
1 |
|
users manual | Users Manual | 4.49 MiB | June 27 2023 / October 26 2023 | delayed release | ||
1 |
|
Internal Photos | Internal Photos | 1.52 MiB | June 27 2023 / October 26 2023 | delayed release | ||
1 |
|
External Photos | External Photos | 955.18 KiB | June 27 2023 / June 28 2023 | |||
1 |
|
Label and Label Location | ID Label/Location Info | 190.20 KiB | June 27 2023 / June 28 2023 | |||
1 | Attestation Statements | June 27 2023 / June 28 2023 | ||||||
1 |
|
Attestation statement | Cover Letter(s) | 190.70 KiB | June 27 2023 / June 28 2023 | |||
1 | Block Diagram | Block Diagram | June 27 2023 | confidential | ||||
1 |
|
Cover Letters | Cover Letter(s) | 1.13 MiB | June 27 2023 / June 28 2023 | |||
1 | Operational Description | Operational Description | June 27 2023 | confidential | ||||
1 | Parts List | Parts List/Tune Up Info | June 27 2023 | confidential | ||||
1 |
|
RF exposure info | RF Exposure Info | 338.53 KiB | June 27 2023 / June 28 2023 | |||
1 | Schematics | Schematics | June 27 2023 | confidential | ||||
1 |
|
Test Report | Test Report | 1.98 MiB | June 27 2023 / June 28 2023 | |||
1 |
|
Test Setup Photos | Test Setup Photos | 2.91 MiB | June 27 2023 / June 28 2023 | |||
1 | Tune up info | Parts List/Tune Up Info | June 27 2023 | confidential |
1 | users manual | Users Manual | 4.49 MiB | June 27 2023 / October 26 2023 | delayed release |
SINGLE BAND FW-600 U S E R G U I D E FW6-B48-00-NA / FW6-B42-43-EU / FW6-B41-00-WW / FW6-B53-00-NA April 2023 FW-600 User Guide Revision History DATE RELEASE ISSUE REASON FOR ISSUE Jan 2021 June 2021 Aug 2021 1.0 2.0 2.1 210803 December 2021 3.0 211209 Initial Release Added Bulk IMSI uploads, removed 6 beams antenna and updates for SW 2.1.9 Updates for SW 2.1.12 features 2CC + 1CC configuration and CSG. Also added note for PCI value changes in 2CC mode. Updates for features up to 3.0.4 QCI-QoS mapping, Whitelist, AAA server authentication and Core Connectivity status pages. January 2022 3.0 220112 Updates for CBSD features in 3.0.5 April 2022 July 2022 3.1 4.0 220420 220714 August 2022 4.1 220805 January 2023 4.2 230116 February 2023 4.3 230208 Updates for SW 3.1.2 features (Secure Gateway, Separate S1 Traffic etc.) and removed information prior to SW 3.0.3. Updates for SW 4.0.3 features Mobility configuration/support. Removal of EEPC information. Added Granted Power Alarm Trigger feature, information on CPI Signed Generator, history and alarm export feature as well as a note on MME pool. Modified Tx Power/EIRP tables and configuration flowchart, added new features for CBSD registration, removed MCS modulation feature mention, added TR-
069 features and updated eNB weights. Updates done to provide further details about UEs supported, added 3CC and adjacent neighbor
(mobility) config, and modified TNC and AISG porta support. April 2023 May 2023 4.4 4.5 230406 Addition of new model FW6-B53-00-NA. 230529 Modifications to FW6-B53-00-NA Specifications, removal of Confidential and addition of ISED Statement. Contact Us BLiNQ Networks (CCARI) 140 Renfrew Drive, Suite 200 Markham, ON L3R 6B3 www.blinqnetworks.com Sales sales@blinqnetworks.com Support
+1-800-301-4962 support@blinqnetworks.com Restricted Use and Duplication Issue 230529 | 2 FW-600 User Guide Table of Contents Revision History ................................................................................................................................................... 2 Table of Contents ................................................................................................................................................ 3 Tables ................................................................................................................................................................. 5 1. About This Guide .......................................................................................................................................... 6 1.1. Manual Conventions ............................................................................................................................. 7 2. FW-600 System Overview............................................................................................................................. 8 2.1. Technical Features ............................................................................................................................... 9 2.2. Network Management Features .......................................................................................................... 10 2.2.1. Security Protocols ........................................................................................................................... 11 3. Technical Specifications .............................................................................................................................. 13 3.1. 3.2. 3.3. 3.4. System Parameters ............................................................................................................................ 13 System Enclosure & Brackets ............................................................................................................. 16 FW-600 Brackets ................................................................................................................................ 16 FW-600 Beams .................................................................................................................................. 18 4. Antenna Model and Specifications .............................................................................................................. 19 4.1. 4.2. FW6-MBA3F-E3AB ............................................................................................................................ 20 FW6-MBA3F-H3AA ............................................................................................................................ 21 5. Getting Started with the FW-600 ................................................................................................................. 22 5.1. FW-600 Web User Interface (WebUI) ................................................................................................. 22 5.1.1. Common Tools ............................................................................................................................... 24 5.1.2. System Status Messages................................................................................................................ 25 6. WebUI Configuration ................................................................................................................................... 27 6.1. 6.2. System Configuration Process ............................................................................................................ 27 System ............................................................................................................................................... 28 6.2.1. Configuring a System Name ........................................................................................................... 28 6.2.2. System Synchronization ................................................................................................................. 28 6.2.3. Network Connectivity Parameters ................................................................................................... 30 6.2.4. Advanced Options .......................................................................................................................... 30 6.3. Carriers .............................................................................................................................................. 36 6.3.1. Antennas ........................................................................................................................................ 36 6.3.2. Cell Parameters .............................................................................................................................. 38 6.3.3. Carriers Parameters ....................................................................................................................... 39 6.3.4. Muting Carriers ............................................................................................................................... 42 6.3.5. Advance Options ............................................................................................................................ 43 6.4. LTE Baseline ...................................................................................................................................... 44 Restricted Use and Duplication Issue 230529 | 3 FW-600 User Guide 6.4.1. Configuring LTE Baseline Parameters ............................................................................................ 45 6.4.2. eNB Identifiers ................................................................................................................................ 48 6.4.3. EPC Settings .................................................................................................................................. 49 6.4.4. Advanced Options .......................................................................................................................... 51 6.5. Mobility ............................................................................................................................................... 55 6.5.1. Neighbors ....................................................................................................................................... 55 6.5.2. Cell Reselection .............................................................................................................................. 59 6.5.3. Handover ........................................................................................................................................ 62 6.6. Embedded EPC .................................................................................................................................. 64 6.7. CBSD ................................................................................................................................................. 64 6.7.1. Configure SAS Server Connectivity ................................................................................................. 64 6.7.2. Device Parameters ......................................................................................................................... 67 6.7.3. Advanced Option ............................................................................................................................ 69 6.8. Management ...................................................................................................................................... 74 6.8.1. UI & Reporting ................................................................................................................................ 74 6.8.2. Syslog ............................................................................................................................................ 78 6.8.3. KPI Reporting ................................................................................................................................. 79 6.8.4. SNMP ............................................................................................................................................. 80 6.9. Verify, Save & Activate Current Running Configuration ....................................................................... 83 6.9.1. Verify and Save Running Configuration ........................................................................................... 83 7. Operation and Maintenance ........................................................................................................................ 84 7.1. Administration..................................................................................................................................... 84 7.1.1. Software Manager .......................................................................................................................... 84 7.1.2. SAS Cert Download ........................................................................................................................ 89 7.1.3. IPSec Cert Download...................................................................................................................... 90 7.1.4. Configuration Manager ................................................................................................................... 91 7.2. Events ................................................................................................................................................ 92 7.2.1. Alarms Page ................................................................................................................................... 92 7.2.2. History Page ................................................................................................................................... 93 7.3. Performance ....................................................................................................................................... 95 7.3.1. eNB Statistics Page ........................................................................................................................ 95 7.3.2. UE Stats Page ................................................................................................................................ 95 7.3.3. Core Connectivity ........................................................................................................................... 97 7.3.4. Network Status ............................................................................................................................... 98 7.3.5. Mobility Status .............................................................................................................................. 100 7.3.6. KPI Reports .................................................................................................................................. 101 Restricted Use and Duplication Issue 230529 | 4 FW-600 User Guide 7.4. Troubleshooting ................................................................................................................................ 103 7.4.1. Band Scan .................................................................................................................................... 103 7.4.2. iPerf.............................................................................................................................................. 103 7.4.3. Network Diagnostics ..................................................................................................................... 105 7.4.4. Troubleshooting Guide.................................................................................................................. 106 Appendix A BLiNQ Wireless Devices and RF Safety/Les appareils sans fil BLiNQ et la scurit RF ............. 108 Equipment Compliance ................................................................................................................................ 108 Appendix B PCI Planning Guidelines ........................................................................................................... 111 Appendix C Commonly Used DSCP Values ................................................................................................. 113 Appendix D UEs Supported for Different Carrier Aggregation Modes ............................................................ 114 Appendix E Alarms and Events (Fault Management).................................................................................... 115 Appendix F List of Acronyms ....................................................................................................................... 120 Tables Table A FW6-B41-00-WW System Parameters .................................................................................................. 13 Table B FW6-B42-43-EU & FW6-B48-00-NA System Parameters ...................................................................... 14 Table C FW6-B53-00-NA System Parameters.................................................................................................... 15 Table D FW6-MBA3F-E3AB Antenna Specifications .......................................................................................... 20 Table E FW6-MBA3F-H3AA Antenna Specifications .......................................................................................... 21 Table G Power Level Configurations Authorized for FW6-B48-00-NA ................................................................. 40 Table H Commonly Used DSCP Values ........................................................................................................... 113 Table I Active UEs Supported per Sector/Beam per eNB.................................................................................. 114 Table J List of Alarms ...................................................................................................................................... 116 Table K List of Events ...................................................................................................................................... 118 Restricted Use and Duplication Issue 230529 | 5 FW-600 User Guide 1. About This Guide This manual contains informational and overview chapters, and then continues as a guide to the recommended order that you configure and then monitor your FW-600 system. It covers features from SW Version 3.0.3 onwards. If a certain feature is specific to a software version, it will be indicated in the respective sections. NOTE: 2.0 SW Versions are not compatible with the FW-600 units. For information with regards to software versions prior to 3.0.3, please refer to FW-600 User Guide_210803. The FW-600 models that are covered in this manual are:
FW6-B41-00-WW FW6-B48-00-NA FW6-B42-43-EU FW6-B53-00-NA As such, whenever FW-600 is mentioned in the manual, it covers all the above models unless otherwise stated. NOTE: The Dual Band FW-600 LAA system have a separate user guide. If your FW-600 unit has the model number FW6-B48-46-NA, please refer to the FW-600 LAA User Guide for configuration details instead. There are two methods to configure the FW-600:
FW-600 Web-based User Interface (WebUI) (recommended) or Command Line Interface (CLI) This user manual contains step-by-step instructions for the FW-600 WebUI. For information about CLI configurations, please contact BLiNQ Customer Support. The WebUI menu structure is the basis for the order of the chapters and the processes contained within those chapters:
Initial system setup: See Chapter 5, Getting Started with the FW-600 Configuration: See Chapter 6 for configuring the FW-600 system using WebUI. Operation and Maintenance: See Chapter 7, Operation and Maintenance Software upgrade Performance containing Evolved Node B (eNB) and Customer Premise Equipment (CPE) statistics plus trace log files and measurements Events including alarms and past events (History) Troubleshooting Management: See Chapter 6.8, Management User operations (Local security) Simple Network Management Protocol (SNMP) Syslog server Restricted Use and Duplication Issue 230529 | 6 FW-600 User Guide 1.1. Manual Conventions This document uses the following conventions:
Bold words indicate actual page names, fields or buttons within the software. It may also be words that need to be emphasized. Examples:
In the LTE (Long-Term Evolution) Baseline Parameters section, enter a value between 0-6 for the Subframe Assignment field. As a default, it has the value of 2. Compact All-Outdoor and Zero-Footprint Form Factor: The FW-600 meets IP67 requirements for operation in tough environments with the capability to handle temperature variations from extreme cold to extreme heat. Bold and Underlined items indicate items that need additional attention. References to related documentation are shown in italic text. Commands typed at a console are shown in a blue monospaced font. The following icons are used to indicate the level of attention that are needed:
This icon indicates crucial information. Failure to observe the information may result in installation failure or error. This icon indicates important information that needs to be observed. Restricted Use and Duplication Issue 230529 | 7 FW-600 User Guide 2. FW-600 System Overview The FW-600 is an ultra-high capacity, all integrated multicarrier LTE base station system designed as a response to todays broadband connectivity needs in rural and dense suburban markets. It packs up to three 2x2 Multiple-Input Multiple-Output (MIMO) carrier radios in one compact form factor. The FW-
600 is paired to passive beamforming antenna systems to bring spectral efficiency and capacity to new horizons. FIGURE 2-1 THREE FW-600 UNITS ON A POLE Key features:
Stock Keeping Units (SKUs) supporting Band 41, 42, 43, 48 and 53 Citizens Broadband Radio Service (CBRS) Category B Certified for FW6-B48-00-NA Supports multiple Time Division Duplexing (TDD) profiles, including TDD Configs 1-7 & 2-7 Up to 96 User Equipment (UEs) per beam in 1 Component Carrier (CC) mode 32 UEs per beam for 2 CC mode Restricted Use and Duplication Issue 230529 | 8 FW-600 User Guide 2.1. Technical Features Some of the main technical product characteristics are as follows:
Compact All-Outdoor and Zero-Footprint Form Factor: The FW-600 meets IP67 requirements for operation in tough environments with the capability to handle temperature variations from extreme cold to extreme heat. BLiNQs state-of-the-art and unique mounting design allows an unobtrusive deployment of multiple FW-600 systems on towers, poles, building sidewalls or rooftops with ease (See the FW-600 Installation Guide for more details). For CBRS Band (for FW6-B48-00-NA): The FW-600 implements a native Spectrum Access System client that fully enables easy Citizens Broadband Radio Service (CBRS) deployments. As a Category B Citizens Broadband Radio Service Device (CBSD), the FW-600 can operate on a Priority Access or General Authorized Access basis in the CBRS band consistent with Title 47 Crest Factor Reduction (CFR) Part 96. Industry Standard TDD LTE-A Release 13 Radio Interface: The FW-600 solution utilizes industry standard
(TDD) LTE-A Release 13 radio capabilities. This allows for robust wireless performance, with extremely cost-
effective deployments of CPEs. Configuration: The FW-600 supports all LTE TDD frame configurations but focuses on Configuration 1 and Configuration 2. Carrier Aggregation: The FW-600 supports carrier aggregation (CA) with up to two (2) Component Carriers
(2CC), allowing for increased throughput to support high bandwidth deployments in both dense suburban and rural environments. Multiple Input Multiple Output (MIMO): The FW-600 system features standard 2x2 MIMO configurations in both downlink (DL) and uplink (UL) directions for each active beam. Quality of Service (QoS): The FW-600 system implements advanced features such Traffic Classification, Admission Control, Rate Shaping plus Active Scheduling and Queue Management in order to deliver the most optimal quality of service. The FW-600 can be paired with different antenna types as to match coverage and/or capacity needs from the operator. This flexibility allows the FW-600 to support both large coverage models, as well as capacity driven models. Here is the recommended antenna for the FW6-B41-00-WW (Band 41) units:
FW6-MBA3F-E3AB (3 Beam antenna) | 21.5 decibels relative to isotropic (dBi) | 12.8 Azimuth (Az) Beamwidth (BW) / Beam This single band, six port multibeam array antenna contains three independent LTE optimized beams covering 1695-2690 MHz frequencies. The LTE Optimized Beams improve LTE data throughput by minimizing beam crossover, providing for an efficient use of valuable radio capacity and frequency spectrum. Here is the recommended antenna for the FW6-B48-00-NA (Band 48) and FW6-B42-43-EU (Band 42/43) units:
FW6-MBA3F-H3AA (3 Beam antenna) | 22.3 dBi | 17.6 Az BW / Beam This multi-beam antenna contains three independent LTE Optimized Beams with 2x2 MIMO capability. Pairing the FW-600 with the FW6-MBA3F-H3AA allows the operator to easily manage network growth and high through deliverables without compromising coverage. Restricted Use and Duplication Issue 230529 | 9 FW-600 User Guide 2.2. Network Management Features The FW-600 implements complete web-based user interface (WebUI) and Command Line Interface (CLI) functionality, plus strong Element Management System (EMS) implementation that suits any type of customer needs. FW-600 Web Interface (WebUI) Accessible via HTTP(S), the WebUI provides an interactive visual toolset that allows you to modify the full configuration of the FW-600 system, as well as view state, fault and performance indicators. The WebUI displays performance data using visual charts and provides applications to visualize the performance data. FW-600 Command Line Interface (CLI) Accessible via Secure Shell protocol (SSH), the CLI provides a well-structured command language in an industry standard idiom. The interface allows you (or third-party system) to manipulate the full configuration of the unit and examine state, performance and fault indicators. TR-069 Accessible via Auto Configuration Server (ACS), the TR-069 protocol allows a safe, remote management and configuration of the eNB. Element Management System (EMS) The NetLiNQ EMS system, enables a state-of-the-art Operations, Administration, Maintenance and Provisioning (OAM&P) feature set. The OAM&P possesses a strong set of interfaces to connect to northbound provision systems. Providing comprehensive Fault, Configuration, Accounting, Performance, and Security (FCAPS) functionality, the FW-600 system uses standard networking protocols and tools that facilitate a full range of element and network management operationsfrom local craft Internet Protocol (IP) address configuration to complex integration in Simple Network Management Protocol (SNMP) or script-based Element Management System (EMS) and Operations Support System (OSS) infrastructures. Community-Based Simple Network Management Protocol version 2 (SNMPv2c) The SNMPv2c interface provide complete access to configuration, state, performance and fault information in the FW-600 system. This allows for high levels of integration in existing EMS/OSS infrastructure for monitoring, Service Level Agreement (SLA) assurance and administrative task automation. Syslog The syslog interface allows the FW-600 system to send standard syslog fault management information (that is, syslog alarms, events, and log entries) to external syslog servers. The FW-600 system provides the following IP addresses for management purposes:
Local Craft IP Address A fixed, non-routable IP address: 169.254.1.1 which is always accessible without Virtual Local Area Network (VLAN) encapsulation. This address is always present on eNodeB (eNB). You use this address in situations where the Management IP Address (see below) is not configured or is unavailable, including initial commissioning and field troubleshooting scenarios. Typically, a technician accesses the Local Craft IP Address by plugging directly into the RJ45 Ethernet port of the eNB. WAN IPv4/IPv6 IP Address A user assigned, static or Dynamic Host Configuration Protocol (DHCP) IPv4/IPv6 address. The device uses this address to exchange traffic and control information with the network. The operator will also use this IPv4/IPv6 address to remotely manage the system. A user-configurable Virtual Local Area Network (VLAN) encapsulates all traffic to and from the Wide Area Network (WAN) interface. The FW-600 system provides the following network management functions:
Configuration Management The system configuration covers several functional areas:
Radio Link Commissioning Radio Link Commissioning parameters (for example, radio frequency, synchronization, TDD configuration) needs to be set before system deployment and are particular to the operator Radio Frequency (RF) network. Restricted Use and Duplication Issue 230529 | 10 FW-600 User Guide EPC Configuration The Evolved Packet Core (EPC) Configuration parameters configure the EPC interface (e.g. Public Land Mobility Network Identifier (PLMN-ID), Mobility Management Entity (MME) interface, Serving Gateway
(SGW) interface). Security Configuration Security Configuration parameters allow you to secure access or disable specific management interfaces
(add local user accounts) and perform various unit administrative operations. EMS Interfaces Configuration Element Management Systems (EMS) enables you to configure SNMP, Syslog, plus the automatic upload of Performance Management (PM) files. All parameters in these areas are accessible via all the network management interfaces previously described. Fault Management The FW-600 system provides fault management service via a comprehensive list of alarms and events. Some of the potential faults that the system detects and initiates alarms on include:
radio and Ethernet link failures hardware module failures synchronization faults software module faults SNMP traps or Syslog relays all alarms and events to higher level managers. The system also allows you to access active alarm and event history information using either the CLI or WebUI. Performance Management The FW-600 system maintains a comprehensive set of performance counters and indicators to facilitate:
performance monitoring SLA monitoring troubleshooting The system provides a full set of Ethernet counters at the interface, module and service flow level, as well as radio quality indicators at the module level. The system makes all the counters available as instantaneous values (via SNMP, CLI or WebUI). Administrative Operations - The FW-600 system provides tools that allow you to perform all standard unit administration operations using the provided remote network management interfaces. The system supports remote software upgrade operations using either a pull paradigm (that is, the system modules retrieve the software package files from external file transfer protocol (FTP) servers or a push scheme using the WebUI
(uploading a software package file to the system modules through the WebUI). The FW-600 system also supports remote configuration backups and backup restoration. 2.2.1. Security Protocols The FW-600 system supports local security access regarding system configuration and maintenance. With this model, you can configure the username, password and access level for the user through the WebUI or CLI. The configuration is stored on the unit. Other than local security access, user credentials can also be created and stored on external AAA
(Authentication, Authorization and Accounting) servers. The FW-600 system supports Remote Authentication Dial-In User Service (RADIUS) and Terminal Access Controller Access-Control System Plus (TACACS+) servers. Please refer to the respective server guides for more details. Restricted Use and Duplication Issue 230529 | 11 FW-600 User Guide 2.2.1.1. Local Networking Protocols Local security protocol is the default protocol for the FW-600 modules. This means that you set each username, password and access level on each module. Each module stores the configuration data in its configuration database. To configure the local security with the WebUI, please see Section 6.8.1.1 SSH/Web Users. 2.2.1.2. External Servers The eNB is also able to reach out to external AAA server and authenticate username and password. This provides scalability and flexibility for your organization when it comes to AAA implementation. RADIUS and TACACS+ servers are supported by the FW-600 system. Two external AAA servers can be configured either with WebUI or CLI. Please see Section 6.8.1.1 for WebUI configuration details. Restricted Use and Duplication Issue 230529 | 12 FW-600 User Guide 3. Technical Specifications This chapter covers:
System Parameters System Enclosure and FW-600 Single Band System Beams 3.1. System Parameters Table A lists the FW6-B41-00-WW system parameters, Table B lists the FW6-B42-43-EU and FW6-B48-00-NA system parameters, and Table C lists the FW6-B53-00-NA system parameters. TABLE A FW6-B41-00-WW SYSTEM PARAMETERS Radio & MBA Specifications Frequency Band 2.49-2.69 GHz (LTE Band 41) Transmit Power (Max.) 39 dBm/antenna port (+ 3 dBm MIMO) Channel Bandwidths 10, 15, 20 MHz RF Propagation LTE Compliance Performance & Attributes 3x MIMO (2Tx x 2Rx) 3GPP Release 10 (SW upgrade to Release 13) Connected/Active User Equipment
(UE) Up to 288 Provisioned UEs per Base Unit (3 Beams) 96 Provisioned UEs per Beam:
Carrier Aggregation Throughput DL TDD Config 2-7
(default) 48 Active UEs per 1CC (CA is performed over the air) Up to 3 Carriers per Base Unit Supports Contiguous and Non-Contiguous 2CC, 3CC. 110 Mbps per carrier of 1CC 330 Mbps per base unit - 3 x 1 CC Throughput UL TDD Config 2-7
(default) 11 Mbps per carrier of 1CC 33 Mbps per base unit - 3 x 1 CC Operating Mode TD-LTE Power Consumption 480 W maximum Power Connectivity 48 VDC 1 x Copper 1000BaseT 1 x SFP 1 x PPS TNC Connector*
1 x AISG/RET Control Port*
6 x 2.2-5 RF Ports Synchronization Embedded EPC Integral GPS antenna (GPS, GLONASS, BeiDou) Software Option Operations, Administration and Maintenance (OAM) Configuration WebUI, CLI, TR-069 and EMS Restricted Use and Duplication Issue 230529 | 13 FW-600 User Guide EMS Integration OAM Protocols MECHANICAL RESTCONF RESTCONF, HTTPS, SSH, SNMPv2c and TR-069 Dimensions (L x W x D) 19.4" x 12" x 8.4" (492 x 304 x 160 mm) Survival Wind Speed Up to 124 mph (200 km/hour) Weight 43.2 lbs. (19.6 Kg) Operational Temperature
-40F to 140F (-40C to 60C)
*Currently not supported. TABLE B FW6-B42-43-EU & FW6-B48-00-NA SYSTEM PARAMETERS Radio & MBA Specifications FW6-B42-43-EU FW6-B48-00-NA Frequency Band 3.4 - 3.6 GHz (LTE Band 42/43) 3.55 - 3.7 GHz (LTE Band 48) Transmit Power (Max.) 39 dBm/antenna port
(+ 3 dBm MIMO) 33 dBm/antenna port
(+ 3 dBm MIMO) Channel Bandwidths 10, 20 MHz RF Propagation LTE Compliance Performance & Attributes Connected/Active User Equipment
(UE) Carrier Aggregation Throughput DL TDD Config 2-7
(default) 3x MIMO (2Tx x 2Rx) 3GPP Release 10 (SW upgrade to Release 13) FW6-B42-43-EU FW6-B48-00-NA Up to 288 Provisioned UEs per Base Unit (3 Beams) 96 Provisioned UEs per Beam:
48 Active UEs for 1CC 32 Active UEs for 2CC and 3CC Up to 3 Carriers per Base Unit Supports Contiguous and Non-Contiguous 2CC, 3CC. Covers Full CBRS Band (150 MHz) for FW6-B48-00-NA 110 Mbps per carrier of 1CC 330 Mbps per base unit - 3 x 1 CC Throughput UL TDD Config 2-7
(default) 11 Mbps per carrier - 1CC 33 Mbps per base unit - 3 x 1 CC Operating Mode Power Consumption Power Connectivity TD-LTE 480 W 180 W 48 VDC 1 x Copper 1000BaseT 1 x SFP 1 x PPS TNC Connector*
1 x AISG/RET Control Port*
6 x 2.2-5 RF Ports Synchronization Embedded EPC Integral GPS antenna (GPS, GLONASS, BeiDou) Software Option Restricted Use and Duplication Issue 230529 | 14 FW-600 User Guide Operations, Administration and Maintenance (OAM) Configuration EMS Integration OAM Protocols MECHANICAL WebUI, CLI, TR-069 and EMS RESTCONF RESTCONF, HTTPS, SSH, SNMPv2c and TR-069 Dimensions (L x W x D) 19.4" x 12" x 8.4" (492 x 304 x 160 mm) Survival Wind Speed Up to 124 mph (200 km/hour) Weight 43.2 lbs. (19.6 Kg) Operational Temperature
-40F to 140F (-40C to 60C)
*Currently not supported. TABLE C FW6-B53-00-NA SYSTEM PARAMETERS Radio & MBA Specifications Frequency Band 2483.5-2495 MHz (LTE Band 53) Transmit Power (Max.) 18 dBm/antenna port (+21 dBm MIMO aggregate) Channel Bandwidths 10 MHz RF Propagation LTE Compliance 3x MIMO (2Tx x 2Rx) 3GPP Release 10 (SW upgrade to Release 13) Performance & Attributes Connected/Active User Equipment
(UE) Throughput DL TDD Config 2-7
(default) Up to 288 Provisioned UEs per Base Unit (3 Beams) 96 Provisioned UEs per Beam:
48 Active UEs per 1CC 110 Mbps per carrier of 1CC 330 Mbps per base unit - 3 x 1 CC Throughput UL TDD Config 2-7
(default) 11 Mbps per carrier - 1CC 33 Mbps per base unit - 3 x 1 CC Operating Mode Power Consumption Power Connectivity TD-LTE 100 W 48 VDC 1 x Copper 1000BaseT 1 x SFP 1 x PPS TNC Connector*
1 x AISG/RET Control Port*
6 x 2.2-5 RF Ports Synchronization Embedded EPC Integral GPS antenna (GPS, GLONASS, BeiDou) Software Option Operations, Administration and Maintenance (OAM) Configuration EMS Integration WebUI, CLI, TR-069 and EMS RESTCONF Restricted Use and Duplication Issue 230529 | 15 FW-600 User Guide OAM Protocols MECHANICAL RESTCONF, HTTPS, SSH, SNMPv2c and TR-069 Dimensions (L x W x D) 19.4" x 12" x 8.4" (492 x 304 x 160 mm) Survival Wind Speed Up to 124 mph (200 km/hour) Weight 37.0 lbs. (16.8 Kg) Operational Temperature
-40F to 140F (-40C to 60C)
*Currently not supported. 3.2. System Enclosure & Brackets The mechanical enclosure for the FW-600 has a GPS antenna attached to it. There are eleven ports on the bottom of the FW-600:
1 x Power Port 1 x Ethernet Port for network connectivity 6 x 2.2-5 RF Ports 1 x Small Form-Factor Pluggable (SFP) Port 1 x Antenna Interface Standards Group/Remote Electrical Tilt (AISG/RET) Control Port*
1 x Threaded Neill-Concelman (TNC) Connector Port*
*Currently not supported. 3.3. FW-600 Brackets You have the option of using a single unit mount (FW6-BRK1-K) or the three units mount (FW6-BRK-K) to install your FW-600 eNB(s) based on your deployment. The single unit mount is made with zinc-plated steel for durability and is designed to ensure that installation will be a breeze. Restricted Use and Duplication Issue 230529 | 16 FW-600 User Guide FIGURE 3-1 FW-600 SINGLE UNIT BRACKET MOUNT If you need to deploy more than one FW-600 eNB on the same tower, you can consider using the 3 units bracket mount (FW6-BRK-K). Due to the unique bracket design, up to three FW-600 units can be installed on one single bracket. This bracket system boosts an ease of installation and simplifies the FW-600 replacement procedure. The figures below show a few examples of possible placements of the FW-600 units on the 3 units mounting bracket. 1 x FW-600 mounted in the middle position 2 x FW-600 mounted on the right side 3 x FW-600 on mounting bracket FIGURE 3-2 FW-600 ENBS ON THE 3 UNITS BRACKET MOUNT Restricted Use and Duplication Issue 230529 | 17 FW-600 User Guide 3.4. FW-600 Beams The FW-600 has three beams Beam 0, 1 and 2 (a software configuration). As such, the RF connector ports at the bottom of the FW-600 unit have markings on them to facilitate the correct external antenna connection. Please refer to the list below for the Connections:
BEAM 0 BEAM 1 BEAM 2 A1 A2 A3 A4 A5 A6 A1 A2 A6 A5 A3 A4 Restricted Use and Duplication Issue 230529 | 18 FW-600 User Guide 4. Antenna Model and Specifications The FW-600 is designed to operate with external antennas. There are the 2 in house antennas that BLiNQ is currently recommending for the FW6-B41-00-WW and FW6-B48-00-NA/FW6-B42-43-EU eNBs. For FW6-B53-00-NA eNBs, please speak with BLiNQ Support if you need a 3rd party recommendation. FW6-MBA3F-E3AB - 3 Beam Antenna recommended for FW6-B41-00-WW 21.5 dBi 12 deg. Azimuth BW/Beam FW6-MBA3F-H3AA - 3 Beam Antenna recommended for FW6-B42-43-EU and FW6-B48-00-NA. 22.3 dBi 17.6 deg. Azimuth BW/Beam 3600 MHz 3600 MHz Restricted Use and Duplication Issue 230529 | 19 FW-600 User Guide 4.1. FW6-MBA3F-E3AB Table D shows the specifications for the FW6-MBA3F-E3AB 3 beam antenna. TABLE D FW6-MBA3F-E3AB ANTENNA SPECIFICATIONS Electrical Frequency Range 2.49 2.69 GHz Gain Azimuth Beamwidth (-3 dB) Azimuth Beam Crossover Elevation Beamwidth (-3 dB) Electrical Downtilt Elevation Sidelobes (1st Upper)
(Typ.) 21.5 dBi 12.8 11.0 dB 9.7 6
< -16 dB Front-to-back Ratio @180 (Typ.)
> 35 dB Cross-Polar Discrimination (at Peak)
> 19 dB Cross-Polar Port-to-Port Isolation
> 24 dB Interbeam Co-Pol Isolation Interbeam Co-Pol Isolation (Non-
Adjacent Beams) (Worse Case) Voltage Standing Wave Ratio
(VSWR)
> 15 dB
> 12 dB
< 1.5:1 Passive Intermodulation (2x20W)
-153 dBc Input Power Continuous Wave
(CW) Polarization Input Impedance Lightning Protection Mechanical 200 Watts Dual Pol 45 50 ohms DC Ground Dimensions (L x W x D) 30.5" x 24.9" x 6.6" (776 x 633 x 167 mm) Survival Wind Speed Up to 150 mph (up to 241 km/hr) Weight (not including mount) 41.6 lbs. (18.9 Kg) Front Wind Load Side Wind Load 162 lbs (722 N) @ 100 mph (161 kph) 46 lbs (206 N) @ 100 mph (161 kph) Equivalent Flat Plate Area 6.3 ft2 (0.6 m2) Connector Mounting Pole 6 x 7-16 DIN female long neck or 4.3-10 female 2-5 (5 12 cm) Restricted Use and Duplication Issue 230529 | 20 FW-600 User Guide 4.2. FW6-MBA3F-H3AA Table E shows the specifications for the FW6-MBA3F-H3AA 3 beam antenna. TABLE E FW6-MBA3F-H3AA ANTENNA SPECIFICATIONS Electrical Frequency Range 3.40 - 3.80 GHz Gain Azimuth Beamwidth (-3 dB) Azimuth Beam Crossover Elevation Beamwidth (-3 dB) Electrical Downtilt 22.3 dBi 17.6 11.1 5.4 4 Elevation Sidelobes (1st Upper)
< -22 dB Front-to-back Ratio @180 (Typ.)
> 35 dB Cross-Polar Discrimination
> 18 dB Cross-Polar Port-to-Port Isolation
> 25 dB Interbeam Co-Pol Isolation
(Adjacent Beams) Interbeam Co-Pol Isolation (Non-
Adjacent Beams) (Worse Case) Voltage Standing Wave Ratio
(VSWR) Passive Intermodulation (2x20W) Input Power Continuous Wave
(CW) Polarization Input Impedance Lightning Protection Mechanical
> 25 dB
> 15 dB
< 1.5:1
-140 dBc 200 Watts Dual Pol 45 50 ohms DC Ground Dimensions (L x W x D) 35.6" x 12.9" x 6.3" (904 x 328 x 160 mm) Survival Wind Speed
> 150 mph (241 km/hr) Weight (not including mount) 22.5 lbs. (10.2 Kg) Front Wind Load Side Wind Load 99 lbs (440 N) @ 100 mph (161 kph) 53 lbs (237 N) @ 100 mph (161 kph) Equivalent Flat Plate Area 3.9 ft2 (0.4 m2) Connector Mounting Pole 6 x 4.3-10 female 2-5 (5 12 cm) Restricted Use and Duplication Issue 230529 | 21 FW-600 User Guide 5. Getting Started with the FW-600 To initially log in to the FW-600:
Connect your computer directly to the FW-600 through an Ethernet cable, and then check your connectivity by pinging the FW-600 using 169.254.1.1 (the Craft IP address that is always accessible). NOTE: You need to statically set the IP address on the computer to 169.254.1.x subnet before pinging. After successfully pinging the Craft IP address, open a web browser and navigate to the pinged 169.254.1.1 to bring up the FW-600 WebUI. To complete the initial system setup with the WebUI, follow the procedures under the desired chapter. NOTE: If required, consult the FW-600 Installation Guide for instructions on powering or installing the unit. 5.1. FW-600 Web User Interface (WebUI) LOGIN CREDENTIALS When prompted for login credentials, enter the default username and password: admin / admin. Title Bar: Tool Area Dashboard Navigation Bar Increase Width Button System Information Bar Restricted Use and Duplication Issue 230529 | 22 FW-600 User Guide On initial log in to the FW-600 Web User Interface (WebUI), you see an overview of the FW-600 details; BLiNQ refers to this page as the Dashboard. The figure below identifies the various elements of the FW-600 WebUI. The dashboard gives you the summary of your system. It shows you the System Overview, which includes the System Name, Device Code, Serial Number, Software Version, Operational Status just to name a few. Please note that the serial number shown represents the serial number of your FW-600 Unit. It will come with the prefix of F60X-YYWWNNNN, where YY is the year, WW is the week and NNNN is the unit number produced in that particular year and week. X indicates the model of the FW-600:
F60A FW6-B48-00-NA F60B FW6-B42-43-EU F60C FW6-B41-00-WW F60E FW6-B53-00-NA There are two tabs at the bottom: Alarms and LTE Cells Status Alarms: Errors on your system will appear in this section, giving you the Alarm ID, Alarm Time, Component, Severity, Type, Probable Cause and Description of the error. LTE Cells Status: This is where you can monitor the LTE Cells operational parameters. Restricted Use and Duplication Issue 230529 | 23 FW-600 User Guide 5.1.1. Common Tools Following are some common features of the FW-600 WebUI. 5.1.1.1. Title Bar: Tool Area Most WebUI pages have either a Commit button or a Refresh button or both in the top right-hand corner. Username Identification Sign Out Button Reboot Button Refresh Button Commit Button Collapse Menu Button Commit button: If you change any settings on a page, select Commit before navigating to another page to save your changes. Refresh button: Updates any read-only data on a page or returns any altered settings to their original values. Reboot button (
): Reboot the FW-600, at any time. It is available at the top of every page. Note: Before a reboot, the FW-600 system performs a verification check between the running configuration and the start-up configuration to determine if there are any changes. This is to prevent the loss of any changes. If there is a change, the system prompts you to save your changes. Sign Out button: Ends each session. Collapse Menu button (
): Minimizes the Dashboard Navigation Bar on the left side. You can still access the menu by positioning your cursor over the thin visible portion of the Dashboard Navigation Bar. Select the Collapse Menu button again to make the menu visible again. Restricted Use and Duplication Issue 230529 | 24 FW-600 User Guide 5.1.1.2. Minimized and Maximized Menus When a plus sign (+) is present beside a menu title, this indicates that you can minimize/maximize this area to reduce or see more options. To maximize an area, select the plus sign (+); the area expands so that all options are visible. To minimize, select the minus sign (-); the menu closes. Maximized 5.1.1.3. System Information Bar The FW-600 system displays the model number, serial number, software version, EEPC version and current license (if applicable) status/number along the bottom of each main page. For example:
5.1.2. System Status Messages The FW-600 WebUI outputs the following types of real-time messages to report on the interaction and/or change results between you and the FW-600 system:
Success Message (Green):
A Success message in green advises, for example, of a successful data or configuration change. Success messages automatically disappear after about 4 seconds. You can dismiss them earlier by clicking on the message. Warning Message (Yellow):
A Warning message in yellow usually cautions of a validation error. For example, if there are problems with entered data, then a Warning message in yellow appears to explain the issue. You must click on a Warning message to dismiss it. They do not disappear automatically. Restricted Use and Duplication Issue 230529 | 25 FW-600 User Guide Error Message (Red):
An Error message in red usually advises, for example, when the server is returning an error. Error messages signify syntactical issues (or a required field being left empty) with the settings you are trying to commit. You must click on an Error message to dismiss it. They do not disappear automatically. Restricted Use and Duplication Issue 230529 | 26 FW-600 User Guide 6. WebUI Configuration This chapter describes the tasks associated with preparing a FW-600 system to provide network services to its users using the WebUI. The recommended FW-600 system commissioning process includes the following steps:
Pre-Configuration in the Warehouse Field Installation (See the FW-600 Installation Guide) The FW-600 system allows efficient installation processes by supporting full pre-configuration of equipment in the warehouse and a field installation process that does not require other installation tools other than the ones needed for the physical installation. 6.1. System Configuration Process The FW-600 WebUI menu structure is the basis for the configuration process. This means that the configuration steps are set up so that you logically input all the related parameters on a page before you move to the next page/step in the configuration process. Please perform these steps in the order presented. SYSTEM System Settings Network Connectivity Advanced CARRIERS Antenna Parameters Cells RF Parameters Advanced MOBILITY
(Optional) Neighbors Cell Reselection Handover EMBEDDED EPC
(Optional) APN Config. UE Templates Subscriber Config. LTE BASELINE LTE Baseline Parameters EPC Settings Advanced CBSD (Optional) Common Settings Device Parameters Advanced MANAGEMENT SSH/Web Users Syslog Settings KPI SNMP FINISH Verify Save Reboot FIGURE 6-1 FW-600 CONFIGURATION PROCESS Restricted Use and Duplication Issue 230529 | 27 FW-600 User Guide 6.2. System On the WebUI (under Setup) System page you set a few parameters:
System Name and Description System Time Zone and Clock Source Network Connectivity parameters Advanced (IPv6, Domain Name System (DNS), Network Time Protocol (NTP), VLAN) 6.2.1. Configuring a System Name When pre-configuring the FW-600, it is highly recommended that you set a unique hostname to differentiate it from other devices. Navigate to the Setup > System page of the FW-600 WebUI. Under the System Settings area, assign a descriptive name to the module in the System Name field. If desired, assign more identifying information via the System Description field. Use System Time Zone and System Clock Source to set your time zone and clock source. Select Commit in the top right corner to save the changes or select the Refresh (
to the previous settings.
)button to cancel and return Repeat as needed for each device in your system. Please note that most configuration changes are only applied after system reboot. To ensure that all your pre-
configuration changes are saved to the start-up configuration file and to activate all your current configuration settings, see Section 6.9, Verify, Save & Activate Current Running Configuration. 6.2.2. System Synchronization The FW-600 system is a Time Division Multiplexed (TDM) radio system. Therefore, FW-600 networks require proper synchronization of the air interface to provide optimal service. The FW-600 system provides flexible synchronization options as well as providing a high-performance extension to existing synchronization networks which delivers quality clock services to downstream devices such as small cells. Restricted Use and Duplication Issue 230529 | 28 FW-600 User Guide The eNodeB synchronizes using the Global Positioning System (GPS). When configured to synchronize via GPS, the FW-600 system uses its internal GPS antenna and receiver module to synchronize to the GPS network. This allows all network deployed FW-600 eNodeBs to accurately synchronize their transmit and receive operations on the air interface. The GPS system also allows the FW-600 system to determine accurate time of day and date information. This time information, together with a user configured time zone setting, tells time across the system and is essential in functions such as fault management (for example, event and alarm time stamping) and historical performance (for example, performance indicator processing and performance file creation). If needed, there is also an optional external GPS source available. The FW-600 system includes a high-performance crystal oscillator that allows it to maintain its clock properties
(Holdover) even if the primary clock reference (that is, GPS) is no longer available. The system provides a Holdover period of 5 minutes. During this time the radio is operational, and the system attempts to recover its primary clock source. If the system does not reacquire the clock source after the Holdover period expires, the system is deemed Not synchronized and therefore ceases radio operation in order to not interfere with other deployed FW-600 systems. On the WebUI, to set the system synchronization:
Navigate the Setup>System page on the FW-600 WebUI. In the System Settings area, you set the system synchronization via the System Clock Source option. Select system clock course to GPS. NOTES:
Networks of FW-600 systems depend on proper synchronization through GPS clock references to operate in an optimal manner and may experience significant performance degradation or even outage if not deployed accordingly. The system allows you to use local clock as a clock source. This parameter is meant for lab testing only. A change in clock source requires a reboot!
When you change the system time, you need to commit to save the changes and then perform a FW-600 reboot in order for the change to take effect. Before moving to a new page, select Commit in the top right corner to save your changes or select the Refresh button to cancel and return to the previous settings. Restricted Use and Duplication Issue 230529 | 29 FW-600 User Guide Reboot the system to activate all your saved changes, by selecting the Reboot System button (
right corner.
) in the top 6.2.3. Network Connectivity Parameters Once logged on to the FW-600, you can change the IP address of the WAN interface under Network Connectivity. There are two possible methods of assigning IP address to the system. You can choose either:
Static: statically assign the IP address for the WAN interface. If set to Static: you must configure the IP address, subnet mask and default gateway, or DHCP: use the Dynamic Host Configuration Protocol (DHCP) to configure this IP address. NOTE: To have DHCP properly assign an address to your FW-600 system, the system must have network access to a DHCP server on your local network. This DHCP server must have available addresses in its address pool, which are in the desired subnet you wish to assign to the system. By default, the FW-600 WAN IPv4 address is assigned via DHCP. To set the IPv4 address, please follow these steps:
Navigate to the Setup>System page of the FW-600 WebUI. Under Network Connectivity, you find all the configurable options. Ensure the WAN IPv4 Address option is set to Static. Enter an IPv4 address, Subnet Mask and optionally an address for the Default Gateway (local router) using the applicable fields. Select Commit in the top right corner to save your changes. NOTES:
At any time during configuration changes and before clicking the Commit button, use the Refresh (
) button to return to the previous settings and/or to update the information on the screen. The changes do not take effect until you reboot the system. Reboot the system by selecting the Reboot System button (
) in the top right corner. 6.2.4. Advanced Options When you click on the Show Advanced button, more configurable fields (IPv6, Advanced Network Connectivity and QCI-QoS Mapping) will appear. Restricted Use and Duplication Issue 230529 | 30 FW-600 User Guide 6.2.4.1. Setting up IPv6 Toggle (Yes or No) to enable or disable IPv6 option. Ensure the WAN IPv6 Address option is set to Static. (WAN IPv4 Address needs to be set to Static for this section to be fillable.) Enter an IPv6 address, IPv6 Prefix Length and optionally an address for the Default Gateway (local router) using the applicable fields. Select Commit in the top right corner to save your changes. Restricted Use and Duplication Issue 230529 | 31 FW-600 User Guide NOTES: At any time during configuration changes in advanced mode and before clicking the Commit button, use the Reset Advanced button (at the bottom) to return to the previous/default settings. 6.2.4.2. Advanced Network Connectivity This is where you can configure the DNS1, DNS2, NTP1, NTP2 and VLAN settings. Enter your desired DNS1, DNS2, NTP1, NTP2 and VLAN values into each of the applicable fields. Select Commit in the top right corner to save your changes. Restricted Use and Duplication Issue 230529 | 32 FW-600 User Guide NOTES:
At any time during configuration changes and before clicking the Commit button, use the Reset Advance button to return to the previous settings and/or to update the information on the screen. All of these advanced parameters (DNS, NTP and VLAN) are optional settings and are not critical for the system to be working. 6.2.4.3. IPv4 and IPv6 Static Routes IPv4 and IPv6 static routes can be added, edited or deleted in this section. This is a feature that is available for SW 3.1.2 onwards. Please note that static routes are needed for the eNB to sent management and S1 traffic over different interfaces. For more information about separating S1 and management interfaces, please see Section 6.4.3.1. To add a static route:
Click on the blue + Add Route button. A pop-up window will appear as follows:
Restricted Use and Duplication Issue 230529 | 33 FW-600 User Guide Adding an IPv4 Static Route Adding an IPv6 Static Route Destination: Specify the routes destination address. This is a required parameter. Next Hop: Specify the next hop IP address. Next Hop is a routing term that refers to the next closest router a packet can go through. This is a required parameter. Interface: Select the desired interface (S1 or mgmt) for this route. Metric: The weighted cost assigned to the route. Lower metrics take precedence over higher costs. When the parameters are entered in, click on + Add Route to add the static route. The route should appear on the respective table IPv4 Static Routes Added IPv6 Static Routes Added Click on Commit to save the changes. NOTE: Separate interface for S1 Traffic option needs to be selected and configured in LTE Baseline
> EPC Settings for the S1 option to be available in the drop-down menu on the Interface field. If not, mgmt will be the only option. To delete a static route:
Check the box beside the desired route and click on the red Delete Route button. Restricted Use and Duplication Issue 230529 | 34 FW-600 User Guide 6.2.4.4. QCI-QoS Mapping Data sent from eNB to EPC is transported over backhaul network. The backhaul network may have limited capacity and be used for transport of other types of data. As a result, the data sent by the eNB may be dropped during congestion. This is a problem both for user plane traffic - as the wireless traffic already has higher probability of error than wireline traffic, and for control plane traffic - as losing these may affect all the connected users (e.g. S1 failure or CBSD Heartbeat drop). With the QCI-QoS Mapping feature, DSCP (Differentiated Services Field Codepoints) values can be configured to be used for specific QCIs (QoS Class Identifier). This will help in prioritizing more important traffic. The default mapping for all QCI values is DSCP 0 and the changes will be applied when the Commit button is clicked. An eNB reboot is not required for this change. To Enable QoS Mapping:
Toggle the button to YES and a list of Traffic Type and its corresponding DSCP value will appear. Configure the DSCP values by using the drop-down menu. Click on Commit to apply the changes. NOTE: Please refer to Appendix D for the list of DSCP values. Restricted Use and Duplication Issue 230529 | 35 FW-600 User Guide 6.3. Carriers On the WebUI Carriers page you set the following parameters:
Antenna Settings Carriers Baseline Parameter (such as Channel Bandwidth and Frequency Setting Mode) Cell 0-5 RF Parameters 6.3.1. Antennas By default, navigating to Setup > Carriers will open the Carriers tab first. To set up the antenna for the FW-600, go to Setup > Carriers and click on the Antennas tab when the Carriers page opens up. On the Antennas page, it will show the list of antennas that have been added with their settings defined. 6.3.1.1. Add an Antenna To add a new antenna:
Click on + Add Antenna. A pop-up window will appear. Restricted Use and Duplication Issue 230529 | 36 FW-600 User Guide Click on Antenna Type to reveal the drop-down menu. Select one of three antenna types: BLiNQ 3Beam,
"BLiNQ 6Beam", or 3rd party". For BLiNQ 3 Beam and BLiNQ 6 Beams, the system will automatically fill in the Horizontal Beamwidth, Vertical Beamwidth and the Antenna Gain. These three fields are greyed out and are not fillable. If a 3rd Party Antenna is selected, all the fields will need to be filled in with the appropriate information, including the number of beams. Enter a name for the Antenna. Central Azimuth: Central azimuth corresponds to overall antenna azimuth. Based on this parameter, the system will calculate azimuth for each beam. The assumption made here is that there is no spacing between beams. By default, azimuth is set at 0. Mechanical Downtilt applies to entire antenna. All the beams inherit this value. This value should match the physical antenna brackets downtilt, if any. The default is 0. Beams Settings:
The system will then automatically open three sub-rows if a 3-beam antenna is selected or six sub-rows if a 6-beam antenna is selected. In the case of a 3rd party antenna, select the appropriate number of beams from the drop-down menu and the corresponding number of sub-rows will appear for configuration. Each beam corresponds to two RF Connectors on FW-600. Refer to Section 3.3 to see the FW-600 beams and connectors. Check off the appropriate boxes as per the connections done at installation (see the FW-600 Installation Guide for more information) While some ports can be left unconnected, checking the same Connectors for a different beam would not be allowed When all the parameters are entered, click on + Add Antenna. The new antenna will be added on the Antennas page. Restricted Use and Duplication Issue 230529 | 37 FW-600 User Guide NOTES:
It is the users responsibility to keep the FW-600 operating within the certified limits. See Table F for the maximum Effective Isotropic Radiated Power (EIRP) and Power allowed. The WebUI only allows up to three antennas on the list. When the list has three antennas, a new antenna cannot be added. One of the antennas will have to be deleted before adding a new antenna. Please see Section 6.3.1.2 for information on deletion of antennas. 6.3.1.2. Deleting an Antenna To delete an antenna, navigate to Setup > Carriers > Antennas Click on the box beside the antenna that you wish to delete:
Click on Delete Antenna and the Antenna will be removed from the list. Deletion of all antennas is not allowed. At least ONE antenna needs to remain on the list. 6.3.2. Cell Parameters Navigate to Setup > Carriers to set up parameters that are common for all the cells:
Channel Size: Select the desired bandwidth via the Channel Size (MHz) drop-down menu. 20 Megahertz (MHz) (default) and 10 MHz: The system supports 10MHz and 20MHz bandwidth configuration for all single band, except the FW6-B53-00-NA units which only support 10MHz. 15 MHz: This option is only available for FW6-B41-00-WW units. However, please note that there is a limit of 32 CPEs per sector (for 1CC) for this bandwidth. Frequency Setting Mode (EARFCN or Frequency) Set the frequency mode for your carrier from the Frequency Setting Mode drop-down list. The options are: EARFCN (E-UTRA Absolute Radio Frequency Channel Number) or Frequency. The default is set to Frequency. Restricted Use and Duplication Issue 230529 | 38 FW-600 User Guide NOTE: If you select EARFCN, configure each Cell x Carrier EARFCN (where x is the desired cell number) to the EARFCN licensed for your operation. Click Commit in the top right corner to save the changes on this page or select the Refresh (
) button to cancel and return to the previous settings. 6.3.3. Carriers Parameters This is where you can set the parameters that are unique for each cell:
Make sure that the box under Enable Cell is checked for each of the cell that you are configuring. Assign the Sector Antenna to each cell using the drop-down list. The list will be populated based on the information on the Antennas tab. Carrier Frequency: Enter the desired frequency for each cell The EARFCN or RF Frequency parameter must match between the FW-600 and the CPE(s) to create a link. Mute Carrier: Check the box to mute a single cell. Muting a cell takes effect immediately without having to reboot the eNB. Click Commit in the top right corner to save the changes on this page or select the Refresh (
) button to cancel and return to the previous settings. 6.3.3.1. Tx Power The software recognizes different product codes and will adjust the TX Power (Transmit Power) limit accordingly. Please note that FW6-B53-00-NA (Band 53) units have a max. TX Power of 18 dBm. Do NOT set the transmit power to above 23 dBm with RF connectors open or unterminated. It will cause a critical damage the hardware and would require an RMA/repair of the FW-600 unit. You can transmit power per cell. Table F shows the power level configurations authorized by FCC for the FW6-
B48-00-NA. Please refer to this table when configuring the Cell Parameters. It is the users responsibility to keep the power levels within the authorized range Restricted Use and Duplication Issue 230529 | 39 FW-600 User Guide TABLE F POWER LEVEL CONFIGURATIONS AUTHORIZED FOR FW6-B48-00-NA FCC ID ROR00000008 FW-600 FW6-B48-00-NA (CBRS) external antennas authorized for use Ant. Ref#
Vendor Antenna Model #
Ant. Gain
(dBi) Antenna Azimuth BW
(deg) Operation Mode Int / Ext Loss (dB) Carrier BW (MHz) FW-600 Cell No. Maximum Configured Power / Antenna Port
(dBm) 2CC 3CC 1CC 1 CCI MBA12F-
HJ5A 24.5 10 2 CCI MBA3F-H3A 22.4 18 1.5 3 MTI MT036S18D S 18 45 4 MTI MT-
404083/ND 17 90
*Power per antenna connector for each CCI Restricted Use and Duplication 10 20 10 20 10 20 10 20 0 1 2 0 1 2 0 1 2 0 1 2 0 1 2 0 1 2 0 1 2 0 1 2 24 24 24 27 27 27 26 26 26 29 29 29 30 30 30 30 33 30 30 30 30 30 33 30 NA 24 NA NA 27 NA NA 26 NA NA 29 NA NA 30 NA NA 30 NA NA 30 NA NA 30 NA NA 24 NA NA 27 NA NA 26 NA NA 29 NA NA 29 NA NA 29 NA NA 29 NA NA 29 NA EIRP / Antenna Port*
(dBm/10MHz) EIRP / Antenna Port*
(dBm/Bandwidth) 1CC 2CC 3CC 1CC 2CC 3CC 47 47 47 47 47 47 46.9 46.9 46.9 46.9 46.9 46.9 46.5 46.5 46.5 43.5 46.5 43.5 45.5 45.5 45.5 42.5 45.5 42.5 NA 47 NA NA 47 NA NA NA 47 NA NA 47 NA NA 47 47 47 50 50 50 46.9 NA 47 NA NA 50 NA NA NA 47 NA NA 50 NA NA 46.9 46.9 46.9 46.9 46.9 NA NA NA NA 46.9 49.9 NA NA NA NA 46.9 46.9 49.9 49.9 49.9 NA NA NA NA 49.9 46.5 NA NA NA NA 46.5 45.5 46.5 46.5 45.5 NA NA NA NA 46.5 46.5 NA NA NA NA 43.5 42.5 49.5 46.5 45.5 NA NA NA NA 46.5 45.5 NA NA NA NA 45.5 44.5 45.5 45.5 44.5 NA NA NA NA 45.5 45.5 NA NA NA NA 42.5 41.5 48.5 45.5 44.5 NA NA 45.5 NA NA Issue 230529 | 40 FW-600 User Guide 6.3.3.2. Carrier Aggregation FW-600 supports DL Carrier Aggregation of up to 3CC starting from SW 4.2.1. This means that for example, the FW-600 can use two 20 MHz channels to transmit towards a single CPE that also support carrier aggregation plus one other independent 20 MHz channel for a 2CC + 1CC configuration. NOTE: FW6-B53-00-NA does not support carrier aggregation. FW-600 supports the following DL Carrier Aggregation modes:
1CC 2CC 2CC + 1 CC 3CC NOTES:
Please note that 2CC and 3CC carrier aggregation can support up to 32 active UEs per beam. For more information about the number of active UEs supported, please refer to Appendix E. The FW6-B41-00-WW only supports carrier aggregation over the air. Please keep that in mind during network planning. The drop-down list for Carrier Aggregation gives the options of Disabled, 2 CC or 3 CC. To enable this function:
Select option 2CC or 3 CC from Carrier Aggregation drop-down list. For 2CC option:
With this option selected, the system automatically selects Cell 0 as Primary Carrier and Cell 1 as Secondary Carrier. Cell 2 will become the independent carrier. Configure the respective Sector Antenna and Carrier Frequency, keeping in mind that Cell 0 and Cell 1 must use the same antenna. Cell 2 on the other hand can use any of the remaining 2 antennas. Restricted Use and Duplication Issue 230529 | 41 FW-600 User Guide In addition, Cell 2 can be disabled by unchecking the box in the Enable Cell column if the independent carrier is not needed. For 3CC Option:
Cell 0 will be set as Primary Carrier, Cell 1 and Cell 2 will be the Secondary Carriers. Configure the respective Sector Antenna and Carrier Frequency, keeping in mind that all three cells must use the same antenna. Select Commit in the top right corner to save the changes on this page or select the Refresh (
) button to cancel and return to the previous settings. NOTES:
For FW6-B48-00-NA and FW6-B42-43-EU, only antenna ports A3 and A4 supports 2CC/3CC operations. Therefore, please use the antenna connected to A3 and A4 ports for 2CC and 3CC configurations. FW6-B41-00-WW supports over the air carrier aggregation. Thus, any of the sector antennas can be used for carrier aggregation operations as long as the Primary and Secondary cells are using the same antenna. An error message will appear if the Primary and Secondary cells are configured with different Sector Antennas when in 2CC or 3CC Carrier Aggregation modes. 6.3.4. Muting Carriers Carriers/Cells can be muted individually as well as collectively at the same time. To mute carriers/cells individually:
Check the box for the desired cell(s) to be muted. The cell(s) will be muted immediately, without a reboot of the eNB. Please note that the carriers can still enabled. Restricted Use and Duplication Issue 230529 | 42 FW-600 User Guide To mute all the carriers/cells at the same time:
Click on the red !Mute All Carriers button at the top right corner of the page. All the carriers will be muted immediately, without rebooting the eNB. Please note that the carriers are still enabled. NOTE: A simple analogy to help understand the difference between enabling a cell versus muting a cell is this: When you are listening to music and you mute it, the music is still running in the background, but you would not hear anything. On another hand, when you turn the music off (disable), it stops completely. 6.3.5. Advance Options When you click Show Advanced button at the bottom of the page, you will reveal more configurable parameters Cell Advanced Parameters (where the Multiband feature is revealed) and Band Scan. Restricted Use and Duplication Issue 230529 | 43 FW-600 User Guide 6.3.5.1. Cell Advance Parameters Band 48 overlaps with Band 42 and 43 (3550-3700MHz). The Multiband feature allows CPE that do not support Band 48 to connect to the FW-600 operating on Band 48. (ie. Backwards compatibility) To enable this feature, make sure that the Enable Multiband is turned to YES.
(Not applicable for Band 41, Band 46 or Band 53 products) NOTE: CPEs support for multiband feature (MFBI) is also required. Please consult your CPE manual to verify this. All BLiNQ CPEs support the multiband feature. 6.3.5.2. Band Scan You can set the FW-600 to scan the frequency band automatically when it is booting up. When this feature is on, the FW-600 will scan and register noise levels across the entire span of the band (150 MHz) in 5 MHz steps for all cells. Under Carriers > Show Advanced > Band Scan, click on the button to toggle between YES and NO. Select the option you desire. Enable Noise Alarms will raise alarms when the noise levels surpass the set thresholds. If you have selected YES, please set up the Noise Threshold and Significant Noise Threshold levels for the scan. The eNB will register anything from -130 dBm to 90 dBm. NOTE: The noise thresholds can be set without rebooting the eNB. Simply click on Commit to apply the changes. 6.4. LTE Baseline On the LTE Baseline page, you configure the following parameters for all modes of operation:
The baseline parameters (such as eNB ID and Cell Range) EPC settings Restricted Use and Duplication Issue 230529 | 44 FW-600 User Guide 6.4.1. Configuring LTE Baseline Parameters In this section, you can assign values to Subframe Assignment, Special Subframe, eNB ID, PCI Seed Value, Cell Range and Tracking Area Code. Based on Baseline eNB ID and PCI Seed Value, the system will calculate eNB Identifiers and PCIs for each of the cells and display these values in the eNB Identifiers table. 6.4.1.1. Subframe Assignment and Special Subframe The advantage of using TDD is that it is possible to change the up and downlink balance and characteristics to meet the load conditions. Please refer to ETSI TS 136 211 Chapter 4.2 to properly configure your subframes. Navigate to the Setup > LTE Baseline page of the FW-600 WebUI. In the LTE Baseline Parameters section, enter a value between 0-6 for the Subframe Assignment field. As a default, it has the value of 2. Under the Special Subframe field, set a value between 0-8. It is set at 7 by default. Restricted Use and Duplication Issue 230529 | 45 FW-600 User Guide Select Commit in the top right corner to save the changes on this page or select the Refresh (
) button to cancel and return to the previous settings. 6.4.1.2. Assign a Baseline eNodeB ID You use the eNodeB ID to identify each cell when establishing a connection with the Evolved Packet Core (EPC). The system automatically generates three IDs from the baseline value of this parameter for each cell respectively, using the following logic:
{[eNB Id]*256},
{[eNB Id]*256+1},
{[eNB Id]*256+2}. This setting must match with the configured value in the EPC. To setup the Baseline eNodeB ID:
Navigate to the Setup > LTE Baseline page of the FW-600 WebUI. Under the LTE Baseline Parameters section, assign the eNodeB identification in the Baseline eNB ID field. The default value for this parameter is 100. Before going to another section, select Commit in the top right corner to save your changes or select the Refresh button to cancel and return to the previous settings. 6.4.1.3. Entering PCI Seed Value The Cell ID and PCI Seed Value define each cells Physical Cell ID (PCI) which the system uses to decode data transmission. PCI calculation: 3*[PCI Seed Value] + [Cell Id]
Cell IDs are fixed at 0, 1 and 2 respectively. Restricted Use and Duplication Issue 230529 | 46 FW-600 User Guide BLiNQ recommends to pre-draft a PCI assignment strategy carefully to avoid interference due to PCI reuse; you can use preconfigured default values. Refer to Appendix B for more information on creating a PCI assignment strategy. To enter PCI Seed Value:
Navigate to the Setup > LTE Baseline Parameters page of the FW-600 WebUI. Under the LTE Baseline Parameters area, assign the PCI Seed Value in the PCI Seed Value field (You can enter any value between 0-167). It is set to 10 by default. Before going to another section, select Commit in the top right corner to save your changes or select the Refresh (
) button to cancel and return to the previous settings. NOTE: When using 2CC configuration, the system automatically assigns the primary carrier the PCI value of Cell 1 and the secondary carrier will have the PCI value of Cell 0. If the CPE was previously locked onto the PCI of Cell 0 in 1CC mode, please log into the CPE, release/delete the PCI lock and relock it with the PCI of cell 1. This way, the CPE will be locked onto the primary carrier when it is in 2CC mode. 6.4.1.4. Setting Tracking Area Code The Tracking Area Code identifies the tracking area within a particular network. You need to set the same code that matches the settings on your EPC. Navigate to Setup > LTE Baseline page to set the tracking area code under LTE Baseline Parameters section. Set the Tracking Area code via the Tracking Area Code field. By default, the value is set at 1. Before going to another section on the page, select Commit in the top right corner to save your changes or select the Refresh (
) button to cancel and return to the previous settings Restricted Use and Duplication Issue 230529 | 47 FW-600 User Guide 6.4.1.5. Enable Mobility The eNB does not turn on mobility functionality by default. This has to be done manually. To enable mobility support:
Go to Setup > LTE Baseline > LTE Baseline Parameters Toggle the Enable Mobility button to YES Click on Commit in the top right corner to commit the change. An additional option (Mobility) will appear on the Navigation Bar/Menu 6.4.2. eNB Identifiers The values in this section are read-only and will change based on the values inserted in the LTE Baseline Parameters section. To manipulate the values in this section, change the Baseline eNB ID and PCI Seed Value (see Section 6.4.1.2 and Section 6.4.1.3) in LTE Baseline Parameters. Varies with Baseline eNB ID Varies with PCI Seed Value Restricted Use and Duplication Issue 230529 | 48 FW-600 User Guide 6.4.3. EPC Settings The Evolved Packet Core (EPC) sets up the optional integrated (embedded) Evolved Packet Core on the FW-600 system. In the EPC Settings section, you will configure the system to use External EPC. This is also the section where you configure the PLMN ID. The Public Land Mobile Network Identifier or PLMN ID defines the network. The PLMN ID consists of a 3-digit mobile country code (MCC) and a 2 (or 3)-digit mobile network code (MNC), thus PLMN-ID = MCC + MNC. You must enter the value that matches the one in the EPC. To configure the Evolved Packet Core (EPC) for the FW-600:
Navigate to the Setup > LTE Baseline page of the FW-600 WebUI. Under the PLMN Id area of the EPC Settings section, assign the Public Land Mobile Network identification in the PLMN Id field. The default value is 00101 (test network). Select either External or Embedded under EPC If Embedded is selected, please refer to Embedded EPC Install and Config Guide for more information. If External is selected, enter the MME Name and MME Host (IPv4 or IPv6 address). If more than one MME Name/Host is entered, MME pooling will automatically be enabled. Enter more than one MME Name/Host to enable MME Pooling Select Commit in the top right corner to save your changes or select the Refresh (
) button to cancel and return to the previous settings. NOTES:
Mobile Management Entity (MME) plays an import role in LTE EPC architecture. MME is the main signalling node in the EPC. Multiple MMEs can be grouped together in a pool to meet increasing signalling load in the network. MME 0 and MME 1 cannot have the same Name and Host. Restricted Use and Duplication Issue 230529 | 49 FW-600 User Guide 6.4.3.1. Separate Interface for S1 Traffic To set up a separate interface for S1 traffic (instead of sending both mgmt. and S1 traffic over a single interface):
Check off the box for Separate Interface for S1 Traffic. This will reveal a set of editable configuration parameters. Please fill in the following items:
Enable VLAN: This option is set on YES and is not editable. VLAN ID: VLAN ID has a value range from 0 to 4094. It specifies which VLAN ID tag to add to a packet. IPv4/IPv6 Address: Enter the IP addresses for the S1 traffic interface. Subnet Mask: Enter the subnet mask for this interface. IPv6 Prefix Length: Enter the IPv6 prefix length, a value between 1 to 127. Click on Commit to save the changes. NOTE: This option is not available when the external EPC is connected via secure gateway. 6.4.3.2. Secure Gateway The FW-600 system can connect to an external EPC via secure gateway for added security. Up to 2 separate secure gateways can be set at the same time for redundancy purposes. SecGW 1 is optional. To set up secure gateway:
Select Connect to EPC via Secure Gateway option by checking the box. This will open a section with various configuration parameters. Enter the secure gateway Name and Host address. Restricted Use and Duplication Issue 230529 | 50 FW-600 User Guide IKEv2: Internet Key Exchange Version 2 (IKEv2) is the second-generation standard for a secure key exchange between connected devices. IKEv2 works by using an IPSec-based tunneling protocol to establish a secure connection. Configure the parameters below. Encryption Algorithm: Select 168 bit 3DES-EDE-CBC, 128 bit AES-CBC, 192 bit AES-CBC or 256 bit AES-CBC (default) from the drop-down menu. Auth Algorithm: Select one of the algorithms from the drop-down menu. SHA2_256_128 HMAC is the default selection. Auth Method: Select either a Pre-shared Key or a Public Key. Pre-shared Key is the default selection. Pre-shared Key: This option is only available if a Pre-shared Key is selected under the Auth Method. Enter the key that was given. DH Group: Select one of the DH Group from the drop-down menu. By default, it is set at DH Group 14. DH Groups 1, 2 and 5 is not recommended as they do not provide adequate security against modern threats and should not be used to protect sensitive information. Rekey Time: The default time is set at 4 hours. IPSec: IPSec, or Internet Protocol Security, is a set of protocols used to secure internet protocol (IP) data transmissions and communications, or more simply, internet traffic. To establish a secure connection, IPSec works by authenticating and encrypting each packet of data during the time you are connected. Encryption Algorithm: Select 168 bit 3DES-EDE-CBC, 128 bit AES-CBC, 192 bit AES-CBC or 256 bit AES-CBC (default) from the drop-down menu. Auth Algorithm: Select one of the algorithms from the drop-down menu. SHA2_256_128 HMAC is the default selection. DH Group: Select one of the DH Group from the drop-down menu. By default, it is set at DH Group 14. DH Groups 1, 2 and 5 is not recommended as they do not provide adequate security against modern threats and should not be used to protect sensitive information. Rekey Time: The default time is set at 4 hours. Click on Commit to save the changes. 6.4.4. Advanced Options The Show Advanced Option in the LTE Baseline page opens three more sections where you can set different values for each cell. The sections are LTE Advanced General, PDSCH/PDDCH, Closed Subscriber Group, UE Reporting and Random-access channel / Physical Random-access channel (RACH/PRACH). Restricted Use and Duplication Issue 230529 | 51 FW-600 User Guide 6.4.4.1. LTE Advanced General Settings Set the max. number of UEs (between 0-96) of the respective cells. It is set to 32 by default. Enter the P-max Value. This is the maximum power the CPE can transmit. The maximum value for this parameter is 23dBm. Lastly, configure the Q Rx Lev Min value, which is the minimum signal strength that the CPE needs to see in order to connect. Care must be taken when modifying this parameter. Please note that a value of -65 dBm configured on the FW-600 translates to a min. threshold of -130 dBm (i.e., Multiplied by 2). If the CPE measures the signal strength lower than -130 dBm, then it will not attempt to connect. Increasing the value of this parameter will severely impact the cell range. Select Commit in the top right corner to save your changes or select the Reset Advanced button to cancel and return to the previous advanced settings. Restricted Use and Duplication Issue 230529 | 52 FW-600 User Guide 6.4.4.2. Setting up RACH/PRACH Values Setting up the right values for RACH is critical to achieve up link synchronization between UE and eNB. The default parameters are carefully selected by BLiNQ. Please do not modify unless instructed by BLiNQ Customer Support. Cell Range: Configuring the cell range parameter automatically sets the parameters that the CPE requires to establish the link There is an option to Use RACH/PRACH to configure Cell Range or enter the Cell Range manually. If the former option is chosen, cell range will be calculated automatically. For the latter option, enter the desired Cell Range. The default is set at 20 km. Choose a value from the drop-down list in the RACH Powerramping Step field. This is the amount of power that will be added onto the Initial RTP (which you will be configuring next) after each connection attempt. The next column is RACH Powerramping Preamble Initial RTP. Similarly, select a value from the drop-
down list to set the initial power to use for connection to the CPE. Select the maximum number of connection attempts from the drop-down list under RACH Preamble Trans Max field. The next two columns (PRACH Config Idx and PRACH Zero Corr Zone) are used only if you wish to use RACH/PRACH to configure your cell range instead of setting it. Check off the box at the top left corner of this section. Set your PRACH Config Idx and the PRACH Zero Corr Zone to establish your cell range. Restricted Use and Duplication Issue 230529 | 53 FW-600 User Guide Once you are satisfied with your values, select Commit in the top right corner to save your changes or select the Reset Advanced button to cancel and return to the previous advanced settings 6.4.4.3. Closed Subscriber Group The closed subscriber group (CSG) feature is used when it is needed to further limit UE PLMN selection. This allows the UE to connect to the desired eNB when neighboring radios are using the CBRS shared PLMN. Enable the feature by toggling CSG Indication to Yes. Configure the same CSG Identity for both the eNB as well as the UE. All UEs with matching CSG identity will then be able to attach to the eNB. 6.4.4.4. UE Reporting The FW-600 can obtain DL measurements from CPEs using periodic measurement reports. This way the eNB can add DL measurements to the performance measurements for each UE. To enable this feature, simply click the slider to YES. The default reporting interval is 1024ms. As of SW 3.1.2, this value can only be changed by using CLI. Please contact BLiNQ Customer Support for more information. 6.4.4.5. PDSCH/PDCCH This section sets up the PDCCH (Physical Downlink Control Channel) CFI (Control Format Indicator) value. It defines the number of symbols in each subframe allocated to PDCCH. The default is set at 1. BLiNQ Networks recommends keeping this value at 1. Restricted Use and Duplication Issue 230529 | 54 FW-600 User Guide 6.5. Mobility This is a feature that is only available for SW 4.0 onwards. Please see Section 6.4.1.5 to enable this feature. There are three sections under Mobility:
Neighbors Cell Reselection Handover 6.5.1. Neighbors Under the section of Neighbors, you can configure the following items:
Cells Frequencies X2 Neighbors The following sections will detail the configurations of each item. 6.5.1.1. Cells The cells configured in this section are advertised in SIB4 (to help with intra-frequency cell reselection), SIB5 (to help with inter-frequency cell reselection), or RRC Connection Reconfiguration (to help with handover). It is not mandatory to advertise them, but they do narrow down the candidates to look for. The system currently supports up to 16 neighbor cells (SW 4.0.2 onwards). To add a neighbor cell:
Click on the blue + Add Neighbor Cell button. A pop-up window will appear. Enter the following parameters to add the neighbor cell:
PCell 0 / PCell 1 / PCell 2: These 3 Boolean values determine to which PCell of this eNB the neighbor cell should be applied to. Check off the respective boxes as needed. PLMN ID: The default PLMN ID is set at 00101. This can be changed to your desired value. However, if it is left blank, it will just return to its default value. Restricted Use and Duplication Issue 230529 | 55 FW-600 User Guide Cell ID: Cell ID is a required parameter. Together with the PLNM ID and Tracking Area Code, the Cell ID helps to uniquely identify cell. Initial EARFCN: This is an optional parameter that represents the initial frequency associated with this cell. Once the operator adds this cell to PCells neighbor list or blacklist, this frequency will be advertised in relevant SIBs and RRC Connection Reconfiguration messages. Next, click on the Advanced tab and enter the following parameters. TAC: This is the Tracking Area Code and it plays a part in uniquely identifying the cell. PCI: Similar to EARFCN (see above), this is the initial PCI value to be used. If neighbor advertises different value, the advertised value will be used. Q Offset Cell: This parameter is used if cell is in neighbor cell list. The offset can be positive (decreases the chances of cell to be considered, as it is subtracted from the measured value) or negative (increases the chances of cell to be considered). The range is from -24dB to 24dB. HO Allowed: Check this box to allow Handover. If it is not checked, the cell will be added to blacklist in ALL advertisements. By default, it is set to allow handover. Once the required values are entered, click on the blue + Add Neighbor Cell to add this new cell. 6.5.1.2. Frequencies This section is used for cell reselection to other frequencies (and then information is advertised in SIB5) and for creating measurement reports (and then it is advertised in RRC Connection Reconfiguration message). The system supports entering up to 30 neighboring frequency relations, however up to 8 can be assigned to PCell. There is a separate row for each frequency. Restricted Use and Duplication Issue 230529 | 56 FW-600 User Guide To add a new frequency:
Click on the blue + Add Frequency Relation. A popup window will appear Under the Basic tab, EARFCN: There are 3 different options for this All, Serving and Specific The All frequency is placeholder for the neighboring frequencies the system learns in dynamic fashion. When Serving frequency is selected, the eNB will apply all the parameters defined in this section and use the frequency that eNB cell is using at the moment. PCell 0 / PCell 1 / PCell 2: You can select the cell out of which this frequency will be advertised. By default all PCells are selected. Under the Advanced Tab, Allowed Measurement Bandwidth: This parameter represents the channel bandwidth the UE should assume when scanning for a neighbor frequency. The drop-down menu gives the options for the number of PRBs (Physical Resource Blocks). For example, if the neighboring frequency is 20 MHz wide, the number of PRBs will be 100. Maximum UL Power: This is the TX power. The maximum is 23 dBm. Presence Antenna Port 1: This field is used to indicate whether all the neighbouring cells use Antenna Port 1. Measurements offset Frequency: This value represents the offset that should be added by the UE when comparing measurement of neighbor frequency against relevant threshold (the actual rules depends on the event type). SIB5 Offset Frequency: When this option is checked off, a dropdown menu will appear for selection. This is the value used by the UE when calculating neighbors suitability for cell-reselection. In this case the value is SUBTRACTED from the neighboring frequency measurement. T Reselection E-UTRA Scaling Factor: This parameter is used in cell reselection and tells UE for how long required condition to consider neighboring frequency needs to be satisfied for the UE to move to the target frequency. Restricted Use and Duplication Issue 230529 | 57 FW-600 User Guide When this option is checked, more fields will appear. When all the parameters have been set, click on the + Add Frequency Relation to add the new frequency. 6.5.1.3. X2 Neighbors The purpose of this configuration section is to allow X2 communication with the neighboring cells. X2 neighbor information will be learnt via X2 procedures - X2 setup/X2 response or X2 eNB configuration update. The operation data will be updated based on latest information received. On reboot, configured and learnt data will be used again until it learns new information from peers. For each X2 neighbor, the operator will be able to define the address (ext-enb-host). The address can be IPv4, IPv6, or hostname. It is also possible to specify the SCTP port number (ext-enb-sctp-port) default is 36422. The ENB keeps track about the entity that created the entry (read only variable created-by). Up to 5 X2 neighbors can be configured on the system currently (SW 4.0.2 onwards). NOTE: Please note that only primary cell information will be included in X2 messages as we dont support mobility features on secondary cell. To add an X2 neighbor:
Click on the blue + Add X2 Neighbor button. A pop-up window will appear. Enter the Host details. This can be the IPv4, IPv6 or hostname (domain name) of the X2 neighbor. Enter the SCTP Port number. The default is set at 36422. Restricted Use and Duplication Issue 230529 | 58 FW-600 User Guide Adjacent Neighbour box can be ignored as this does not apply to the FW-600 eNB. Click on the blue +Add X2 Neighbor to add the new X2 neighbor. The newly added neighbor should be listed on the X2 Neighbors page without needing a reboot. To delete an existing neighbor, simply click on the checkbox beside the desired item on the table and hit the red Delete X2 Neighbor button. 6.5.2. Cell Reselection Cell Reselection page handles parameters that instruct UEs how to handle cell reselection while in IDLE mode. Most of these parameters are advertised in SIB3, SIB4, and SIB5. These parameters are configured per enabled PCell. To modify the parameters of a PCell, click on the blue PCell number on the left column. A popup window will appear where configurations in 3 different tabs can be modified. Restricted Use and Duplication Issue 230529 | 59 FW-600 User Guide Under Basic tab:
SIB3 Q Hysteresis: This value defines how much the serving cell signal should be preferred compared to a neighbor cell. SIB3 SNonIntra Search: This parameter represents the minimum acceptable value of the serving cell Srxlev for the UE NOT to start considering inter-frequency cell reselection to cells of lower or equal priority as the serving cell. SIB3 Threshold Serving Low: This parameter represents the minimum acceptable value for serving cell Srxlev (which is roughly difference between serving cell Reference Signal Received Power (RSRP) and minimum acceptable RSRP for the serving cell) for the UE NOT to start considering inter-frequency cell reselection to cells of lower or equal priority as the serving cell. SIB3 Cell Reselection Priority: This is serving cell reselection priority. The UE uses this value to decide if other frequencies defined in SIB5 are of higher priority or not. The default value is set at 7. SIB3 SIntra Search: It specifies the serving cell Srxlev threshold (in dB) for intra-frequency measurements. (Srxlev represents the difference between measured RSRP and minimum acceptable RSRP). By default, this is set at 8. SIB3 T Reselection E-UTRA: This parameter determines for how long the reselection criteria needs to be satisfied for UE to move to another cell on the same frequency. Ths default value is set at 2. Restricted Use and Duplication Issue 230529 | 60 FW-600 User Guide Under the Advanced tab:
SIB3 Speed State Reselection Parameters: This parameter determines if speed state reselection parameters are advertised or not. By default it is set to Yes. SIB3 Mobility T Evaluation: This parameter determines how long the UE needs to satisfy the criteria for moving to Medium or High Mobility state in order to actually move to those states. By default it is set to 240 seconds. You can select any value from the dropdown menu. SIB3 Mobility n-Cell Change Medium: This specifies the maximum number of cell reselections to enter Medium-mobility state. Its default is set to 12, and the range is from 1 to 16. SIB3 Mobility n-Cell Change High: This specifies the maximum number of cell reselections to enter High-mobility state. Its default is set to 16, and the range is from 1 to 16. SIB3 Mobility T Hysteresis Normal: This parameter determines how long the criteria for UE being in Medium or High Mobility need to be NOT satisfied before UE moves to Normal state. Default setting is 240 seconds. Valid values are 60, 120, 180 and 240. SIB3 Speed State Reselection SF Medium: When the UE compares neighbor cell with the serving cell, it adds SIB3 Q Hysteresis to the measurement of the serving cell, effectively ensuring that neighboring cell needs to be at least SIB3 Q Hysteresis or better for the UE to move to it. SIB3 Speed State Reselection SF High: This parameter is added to the measurement of the serving cell when UE is in state of High Mobility. This makes it easier to UE to move to a neighboring cell. In general it makes sense to have this parameter lower than similar parameter for Medium Mobility (for example if it is
-2 for Medium Mobility, it can be -4 for High Mobility) SIB3 Q Rx Lev Min: This value represents the minimum acceptable RSRP for neighboring cells on the same frequency. The default value for this parameter is -60 (the same as for the serving cell) with the range of -70 to -13. SIB3 SIntra Search R9: This parameter define the threshold of the minimum acceptable quality that serving cell has to drop to for the UE to start looking for the alternative cell on the same frequency. This Restricted Use and Duplication Issue 230529 | 61 FW-600 User Guide has the same funtionality as SIB3 SIntra Search (Basic Tab), but it has a higher priority than that. If both values are present/configured, the UE will use SIB3 SIntra Search R9 first. SIB3 SNonIntra Search R9: This parameter represents the threshold if the serving cell signal level
(either RSRP or RSRQ) drops below the threshold, the UE should start looking for other cells. The difference is that this is NonIntra, so UE will start looking at different frequencies. The default values are 8 (RSRP) and 9 (RSRQ). SIB2 Threshold Serving Low Q R9: This parameter determines the condition under which the UE would move to a frequency with a lower priority than the serving cell. It is not turned on by default. If it is selected, the default value will be set to 0. Under Blacklist tab:
You can select the cells listed under Neighbor Cells and place them onto the Blacklisted Cells with the arrow keys. Cells need to be added on as a Neighbor cell before they can be put on the Blacklist. A maximum of 16 cells can be blacklisted. Once all the configurations are modified, click on the + Update button. 6.5.3. Handover Handover is triggered by UE reporting that an event that ENB told UE to look for took place. Hence, this section is primarily about measurement configuration (i.e., what should ENB tell UE to look for and what to do once the event is detected). Restricted Use and Duplication Issue 230529 | 62 FW-600 User Guide To add a Handover Rule:
Click on the blue + Add Handover Rule button. A popup window will appear. Enter the following parameters:
PCell 0 / PCell 1 / PCell 2: This determines to what PCell the handover rule will be applied to. (Only enabled PCells can be selected). Event: Choose A1, A2, A3, A4 or A5 from the dropdown menu. Single PCell supports up to one A1 event type, up to one A2 event type, up to one event for intra-frequency handover, and up to one event for inter-
frequency handover. For A5: A few additional fields will appear as it will need a second Threshold RSRP/RSRQ. EARFCN: Choose either All or Serving from the dropdown menu. If event type A1 or A2 is chosen from before, the only valid option here will be Serving and it will automatically be selected as such. If the event type A3, A4 or A5 is selected, both Serving and All will be available. Trigger Quantity: This parameter tells the UE which RF parameter (RSRP or RSRQ) to evaluate. (This is independent from Report Quantity). If RSRP is chosen, then only Threshold RSRP will need to be filled in and the value entered in Threshold Reference Signal Received Quality (RSRQ) will be ignored (and vice versa). Hysteresis: This parameter is used to reduce bouncing effect when the measured signal is close to the threshold. When the signal needs to go above certain threshold for condition to trigger, the hysteresis is added to the threshold; when the signal needs to go below certain threshold for condition to trigger, the hysteresis is subtracted from the threshold. Default value is set at 2. Threshold RSRP: The default value is set at 80. This will be the threshold value used for measurement depending on the type of event selected. Restricted Use and Duplication Issue 230529 | 63 FW-600 User Guide Threshold RSRQ: The default value is set at 0. This will be the threshold value used for measurement depending on the type of event selected. Time to Trigger: This parameter specifies for how long the event condition has to be satisfied in order for the UE to send measurement report. The default time is set at 640 ms. Report Amount: This parameter specifies how many times the measurement report should be sent. The default is set as infinity as long as the event condition is satisfied, the event will be sent. Report Interval: If the report-amount is greater than 1, this parameter tells the UE how often to send measurement reports (when the event condition is satisfied). Report Quantity: This parameter specifies what measured RF value the UE should provide in measurement report. Max. Report Cells: This parameter specifies how many non-serving cells (that satisfy event condition) to include in measurement report. The default is 4. Once the parameters are set, click on + Add Handover Rule to add the rule. 6.6. Embedded EPC Please refer to the Embedded EPC Install and Config Guide for Embedded EPC configurations on the WebUI. 6.7. CBSD CBSD option is only available for frequency band 48 (B48). When the WebUI loads, it will recognize the eNodeB is operating in B48 and make CBSD option available for configuration. On the WebUI, you use the Citizens Broadband (radio) Service Device (CBSD) page for the Spectrum Access System (SAS) server connectivity. When using the LTE Band 48, eNodeB requires Spectrum Access System
(SAS) server connectivity for operation. The eNodeB will automatically configure the operating frequency and transmit power per beam based on the grants received by the SAS server. Perform these steps in the order presented below. NOTE: Select the Commit button before moving to a new page to save the configuration changes. 6.7.1. Configure SAS Server Connectivity On the WebUI, navigate to Setup > CBSD. Restricted Use and Duplication Issue 230529 | 64 FW-600 User Guide Under the Common Settings area, use the following options to set up SAS server connectivity:
Enable CBSD: Toggle the button to Enable (YES) or Disable (NO) CBSD feature. User ID: Input the CBSD User identification SAS Server URL: Input the Spectrum Access System (SAS) database server Universal Resource Locator (URL), for example: https://developer-sc-02.federatedwireless.com/v1.2 Registration Type: There are 3 ways to register using the WebUI - Single Step (Upload data), Single Step (Input data) or Multi Step. Single Step (Upload data): For this option, a pre-generated the CPI signed CBSD configuration data file needs to be uploaded onto the eNB to enable the registration. o To generate the data file, open the program provided by BLiNQ the CPI Signed Data Generator. Restricted Use and Duplication Issue 230529 | 65 FW-600 User Guide o Click on the top field and select the appropriate unit from the drop-down menu. o Enter the rest of the installation parameters. o Upload the CPI certificate and enter the password required to read CPI certificate. o Click on Generate. This will create the CPI signed data file (MXF-WLTGG12248H_<CPE CBSDID>.txt) in the same folder where the program is located. o On the WebUI, click on Browse to locate the CPI signed data file. Restricted Use and Duplication Issue 230529 | 66 FW-600 User Guide o Select the desired file and click on + Apply. Single Step (Input Data): When this option is selected, a new section will appear, allowing users to input the eNBs data that is needed for CBSD SAS registration. o Fill in or update the fields in this section (Installation Parameters & Certificate). Take note that the Latitude, Longitude, p12 certificate file and the p12 Certificate Passphrase are required. o The p12 certificate will be used for certification purposes and will not be stored in the eNB. Multi Step: For Multi Step registration, installation parameters need to be configured in the SAS portal before configuring on the WebUI. Select Commit in the top right corner to save the changes on this page or select the Refresh (
) button to cancel and return to the previous settings. NOTE: Please ensure that the Registration Type is consistent on both the WebUI here as well as on the SAS Portal. For example, if multi step registration is already done on the SAS portal, select Multi Step on the WebUI instead of Single Step. 6.7.2. Device Parameters This section shows the FCC ID of the eNB as well as its CBSD Device Category. Restricted Use and Duplication Issue 230529 | 67 FW-600 User Guide The CBSD status of each cell can also be seen in this section, showing the CBSDID for each cell along with its configured Antenna (See Section 6.3.3). 6.7.2.1. Standby Grant and Standby Grant Alarm With SW 4.0 onwards, the eNB will notify the operator if the standby grant is better than currently used active grant. This feature will only be activated when Multi-Grant option is turned on under CBSD Advanced Option
(Section 6.7.3.3) Given that promoting standby grant to active grant requires re-registering of the eNB, it needs to be approved by the operator. Therefore, an alarm (Major) will be raised, specifying the cell that is affected. Promote buttons on the Standby Grant column will be enabled when the standby grant is better than the active grant for the specific cell. To promote the standby grant to active grant, simply click on the Promote button. The Promote button will then be greyed out when the standby grant has been promoted. Restricted Use and Duplication Issue 230529 | 68 FW-600 User Guide Clear buttons will be enabled when the Standby Grant Alarm is raised. Click on the Clear button to clear the alarm. If the standby grant is not promoted, the Promote button will remain enabled. When the standby grant is no longer better than the active grant, the alarm will automatically be cleared. 6.7.3. Advanced Option Clicking on the Show Advanced button will reveal the following parameters:
Full Spectrum Request Measurement Capability Persistent Grant and Multi-grant options Heartbeat Intervals, TX Expire Buffer Time and TCP Keepalive Granted Power Alarm Trigger 6.7.3.1. Full Spectrum Request Use the toggle button to turn Full Spectrum Request on (YES) or off (NO). Restricted Use and Duplication Issue 230529 | 69 FW-600 User Guide When full spectrum request is ON (TRUE) the CBSD asks SAS for all the available channels. The eNB considers the channel with maximum allowed power to be the best one; if there are multiple channels available with the maximum allowed power, the eNB will use the channel where it detected the least amount of interference. This feature is set on ON by default. When full spectrum request is OFF (toggle button to NO) the CBSD requests for the carrier frequency that is configured under Carriers section (See Section 6.3.3). CBSD will only start to transmit when it receives an authorized grant. 6.7.3.2. Measurement Capability The SAS may ask the CBSD (the FW-600 in this case) to measure the power it is receiving from other devices in the field, so that SAS can input that in its algorithm when figuring out what frequency to give to CBSDs in that area. The options in this field are:
Power with Grant: The eNB will measure power while transmitting. Power without Grant: The eNB will measure power when it is not authorized to transmit. At the time of the release of this document, SAS vendors do not support this feature on their end. Therefore, please do not configure Measurement Capability 0 and Measurement Capability 1. 6.7.3.3. Persistent Grant and Multi-Grant When Persistent Grant is turned ON (toggle button to YES), the eNB will retain its grant and does not deregister during a reboot. In other words, if the eNB is registered prior to a reboot (be it power failure or a reboot request), it will remain registered after the reboot. If the eNB was authorized before reboot, after reboot the eNB will verify if the authorization is still valid, and if it is, the eNB will continue to transmit. Restricted Use and Duplication Issue 230529 | 70 FW-600 User Guide When the Persistent Grant feature is turned OFF (toggle button to NO), the eNB will require a re-registration after a reboot. The Multi-Grant feature ensures that the eNB will have at least two grants configured before start-up, and request for different frequency ranges that are not overlapped. Therefore, in the event of a grant suspension, the suspension time will be reduced as the eNB will switch to the frequency of the secondary grant for transmission. In the meantime, it will also continue to pursue the primary grant for authorization. 6.7.3.4. Heartbeat Interval The Heartbeat Interval feature allows users to define the preferred interval value which may be adopted by eNB depending on the reference interval value from SAS. After received the first heartbeat response, the eNB compares the interval from SAS response with the configured interval and selects the shorter interval as the final heartbeat interval. The default interval is set at 100s. 6.7.3.5. TX Expire Buffer Time The Tx Expire Buffer Time is the amount of time guaranteed between next heartbeat request sending time and RF Tx expire time. The buffer time is to counter the system time drift. The buffer time interacts with heartbeat interval and takes precedence if it is configured longer. For example, given RF Tx expire time is 220s, the final heartbeat interval is 200s, then the time difference between next heartbeat and Tx timer timeout is 20s. If buffer time is set to 40s, the heartbeat interval will be shortened to 180s. Restricted Use and Duplication Issue 230529 | 71 FW-600 User Guide By default, the buffer time on the software is set to 10s. 6.7.3.6. TCP Keepalive The TCP Keepalive is the message sent from one device to another to prevent the TCP session being broken. In most cases, after TCP session being established, it stays in connected state forever. However, if there is any NAT gateway or firewall in between, due to the limited resources on those intermediate devices, the session may be disconnected after certain amount of time if there is no traffic detected. The TCP keepalive has two timers, idle and interval. The idle timer is to tell TCP state machine after how long time no traffic the session can be deemed as inactive. The interval timer is to tell TCP state machine how often the keepalive message shall be sent out if session is in an idle state. To turn this feature on, simply toggle the TCP Keepalive button to YES and configure the desired TCP Keepalive Idle Time and the TCP Keepalive Interval time. 6.7.3.7. Granted Power Alarm Trigger This feature generates an alarm and SNMP trap whenever a CBSD agent receives a grant with EIRP lower than the maximum EIRP it supports and decides to use it. This is available from SW 4.0.2 onwards. By default, an alarm will be triggered if the granted power is lower than the maximum power supported. Restricted Use and Duplication Issue 230529 | 72 FW-600 User Guide In addition, if the EIRP is needed to be lower than the maximum power, the alarm can be set with a configured threshold. Select Granted power < configured alarm threshold Set the Grant Power Alarm Threshold Restricted Use and Duplication Issue 230529 | 73 FW-600 User Guide 6.8. Management Under Management, configure the following items:
SSH/Web Users IP Connectivity Whitelist Syslog KPI Reporting SNMP 6.8.1. UI & Reporting Configure Usernames and syslog servers in this section of the WebUI. 6.8.1.1. SSH/Web Users Configure the Username, password, and access level for the local security of each unit in this section. The SSH/Web Users feature allows you to add, modify (update password and read/write privileges level) or delete system users from the FW-600 WebUI. Each units configuration database stores the user configuration data locally. In addition, the FW-600 is also able to reach out to external AAA server and authenticate username and password. RADIUS and TACACS+ servers are supported. To add users to (or modify an existing user on) the system using the FW-600 WebUI:
Navigate to the Setup > Management > UI & Reporting page of the FW-600 WebUI. Select the Add User button to add a user in the SSH / Web Users section. An Add User dialog box appears. Restricted Use and Duplication Issue 230529 | 74 FW-600 User Guide From the Add User dialog box, you can enter a username, password and choose the access level of that user (Group) -- either Read Only or Read Write. When all the fields have been entered, click on + Add User to add the new credentials. NOTES:
Usernames must start with a letter and may be composed of alphanumeric characters only. Passwords are case sensitive, may be composed of alphanumeric characters including special characters and must contain at least one (1) letter and one (1) digit. At least one user with read/write privileges needs to exist in the FW-600 system. The system will lock out specific user after 6 unsuccessful login attempts. You can edit existing FW-600 users by selecting the hyperlinked name of the user you want to modify. The Update User dialog box appears. To reset a password, type in the new password and select the Update User button to confirm the new password. Inform the user of the new password. You can also adjust the users access level either Read Only or Read Write. To change a username, you must delete this user and create the user under a new name. Restricted Use and Duplication Issue 230529 | 75 FW-600 User Guide To delete a user: select the check box beside the user that you want to delete. Select the Delete User button. The selected users Username disappears from the list. NOTE: If you cannot login due to a forgotten username or password, contact another user with read/write access privileges to have them reset your login credentials. You can also refer to the eNB Password Recovery Guide for more information. For any of the actions, select Commit for the changes to save your changes or Cancel to abandon this action. Using AAA Server(s):
User credentials have to be created on the RADIUS or TACACS+ server prior to using it on the eNB. Please refer to your RADIUS or TACACS+ server guides for more details. To use an external RADIUS or TACACS+ server on the eNB:
Navigate to the Setup > Management > UI & Reporting page of the FW-600 WebUI. In the SSH / Web Users section, click on the drop-down menu for Authentication Type to select one of the options Local, RADIUS with fallback to Local or TACACS+ with fallback to Local Once the Authentication Type is selected, click on Commit to apply the changes. A new section will appear on the page for further configuration based on the selection made. RADIUS Server Configuration Restricted Use and Duplication Issue 230529 | 76 FW-600 User Guide TACACS+ Server Configuration Enter the Timeout value (in seconds) as well as the number of Retries before the system falls back to the Local server for authentication. You can configure up to 2 external servers. Check the box under Use Server to enable the server. Enter the servers IP Address, Port and the encryption Key. Select Commit to save the changes or Cancel to abandon the change. NOTE: Please note that Server 0 will always be the primary server and Server 1 will be the secondary. This means that the eNB will always try to reach Server 0 first before trying Server 1. 6.8.1.2. IP Connectivity Whitelist This feature would allow the operator to limit the IP addresses that can access the eNB for management purposes. If the IP address is not in the Whitelist, access to HTTPS and SSH will not be allowed. In this section, it will state if the IP Whitelist check is currently enabled or disabled. IP Whitelist check status: Inactive Whitelist is not enabled IP Whitelist check status: Active Whitelist is enabled All the subnets listed will be used in the Whitelist check when it is enabled. To add new subnet:
Click on the Add Subnet button. A new window will pop up. Restricted Use and Duplication Issue 230529 | 77 FW-600 User Guide Enter the IP for the subnet along with the Prefix Length. Click on Add Subnet to add the new IP onto the list. This list only applies to WAN management IP addresses. Reboot is not required for the Whitelist to be enabled. However, once the changes are done, please remember to click on Commit for all the changes to be applied. To delete a subnet from the list:
Click on the check box(es) of the IP(s) to be deleted. Click on the Delete Subnet once the IP(s) have been selected. This will remove the selected IP subnet(s). NOTE: An empty Whitelist is not allowed by system configuration. To enable Whitelist functionality, at least one subnet must be provided. 6.8.2. Syslog The syslog interface allows the FW-600 system to send standard syslog fault management information (that is, syslog alarms, events and log entries) to external syslog servers. On the Setup > Management > UI & Reporting page, you can set or change their operational status. 6.8.2.1. Using/Editing Syslog Server Navigate to the Management > UI & Reporting page. Select the server you wish to use in the Logging section. Restricted Use and Duplication Issue 230529 | 78 FW-600 User Guide Enter either an IPv4 or an IPv6 address in the IP Address field. Select a Severity Filter by using the drop-down list to set the type of information collected. Select the Commit button at the top of the screen to save your changes. 6.8.2.2. Delete a Syslog Server Navigate to the Management > UI & Reporting page. From the Logging section, uncheck the box next to the syslog server that you want to delete. Select the Commit button at the top of the screen to save your changes. The syslog server would then be deleted 6.8.3. KPI Reporting This section allows you to set up custom thresholds for your reporting/analysis/monitoring purposes. Go to Management > UI Reporting > KPI Reporting Restricted Use and Duplication Issue 230529 | 79 FW-600 User Guide Set up the Minimum Threshold (in percentage) for each of the three KPI State Operational, Degraded and Severely Degraded. Check the box at the bottom if you wish to generate an event when the KPI State changes. For example, an event will then be generated if the units performance changed from Degraded to Operational. 6.8.4. SNMP The Simple Network Management Protocol (SNMP) feature allows you to add, delete or edit SNMPv2c users and hosts. Theses interfaces provide complete access to configuration, state, performance and fault information in the FW-600 system. The WebUI SNMP page allows you to set up Simple Network Management Protocol (SNMP) users and host servers, plus add, edit and remove SNMP users and host servers. 6.8.4.1. Add or Remove SNMP User To add or remove an SNMP user:
Access the Management > SNMP page. To add an SNMP user: select the Add User button under the SNMP Users section. An Add User dialog appears. Input the name of the user in the Name field. Use the Access option to designate the user access level by selecting either the Read Only or Read Write option. Restricted Use and Duplication Issue 230529 | 80 FW-600 User Guide Version refers to the security protocol level for that user: v2c (default). Please use only v2c as BLiNQ does not support v3 as of now. Select the Add User button to add your user or the Cancel button to abandon the addition. If you need to edit an existing user, select the hyperlinked name of the desired user, an Update User dialog appears. When you finish your edits, select the Update User button to save your changes or Cancel to abandon these changes. NOTE: You cannot change the name field. If you do need to change the username, delete that user and repeat the above steps with a new name. To remove an SNMP user: select the check box beside the user you want to delete. Select the Delete User button. The user disappears from the list. Select the Commit button at the top of the screen to save your changes. If this is your last change/update, reboot the system to activate all of your saved changes, by selecting the Reboot System button (
) in the top right corner. 6.8.4.2. Add or Remove SNMP Host To add or remove an SNMP host:
Access the Management > SNMP > SNMP Hosts area. To add an SNMP host: select the Add Server button. An Add Server dialog appears. You need to know the Name, IP Address and Port for your SNMP host. Restricted Use and Duplication Issue 230529 | 81 FW-600 User Guide Version refers to the security protocol level for that host. Select either v1 (default) or v2. BLiNQ does not support v3 protocol as of now. Select the Add Server button to add your server or the Cancel button to abandon this addition. If you need to edit an existing SNMP host, select the hyperlinked name of the desired host, an Update Server dialog will appear. When you finish your edits, select the Update Server button to save your changes or Cancel to abandon these changes. NOTE: If you need to change the Host Name, delete that host and repeat the above steps with a new name. To remove an SNMP host: select the check box beside the host you want to delete. Select the Delete Server button. The host disappears from the list. Select the Commit button at the top of the screen to save your changes. If this is your last change/update, reboot the system to activate all of your saved changes, by selecting the Reboot System button (
) in the top right corner. Restricted Use and Duplication Issue 230529 | 82 FW-600 User Guide 6.9. Verify, Save & Activate Current Running Configuration Before exiting from the pre-configuration setup:
Verify that the currently running configuration meets all the configuration system setup requirements. If the configuration matches the expected configuration, you must save the currently running configuration to the start-up configuration. This ensures that any changes are saved after a reboot. To activate and see your configuration changes, reboot the system. 6.9.1. Verify and Save Running Configuration To verify and save the currently running configuration:
Verify the currently running configuration to ensure that it matches the expected configuration. For instance, check that the EARFCN or radio frequencies match on the FW-600 and CPE. Select the Commit button at the top of the screen to save your changes. Reboot the system to activate all your saved changes, by selecting the Reboot System button (
right corner.
) in the top Restricted Use and Duplication Issue 230529 | 83 FW-600 User Guide 7. Operation and Maintenance This section contains the following additional FW-600 operation and maintenance features:
Software Upgrade Performance monitoring statistics for:
eNB CPE Trace Log Files Measurements (per Beam) Fault management via the Events:
Alarms page Events history 7.1. Administration Under Administration, you can manage the following:
Software Version Download SAS Certificate Download IPSec Certificate Generate/Restore from Configuration backup files 7.1.1. Software Manager To perform system software upgrade activities, you must have read-write privileges to access this functionality. The read-only Software Details area informs you of the devices currently running software (active), the available standby software and the current upgrade status. Restricted Use and Duplication Issue 230529 | 84 FW-600 User Guide NOTE: The running software version can also be seen from the Dashboard when you first log into the WebUI. 7.1.1.1. Reset Factory Defaults There is a red !Reset Factory Defaults button at the top of the page. ONLY USE the !Reset Factory Defaults button, when you want to return all of the configuration settings to the factory defaults. You must have read-write privileges to access this button. When you select the !Reset Factory Defaults button, the Login screen appears. All configurations will return to their factory default values. 7.1.1.2. System Software Upgrade Software upgrades occur either from an FTP server, SFTP server or from your hard disk. To upgrade the software, do the following:
Navigate to the Administration > Software Manager in the FW-600 WebUI. Within the Software Download area, from the Software Download Method, select Direct Download, FTP or sFTP Direct Download (for software files located on your hard drive or available network drive) Select the Browse button under Software File. Restricted Use and Duplication Issue 230529 | 85 FW-600 User Guide Browse for the binary file to be used for the upgrade from the File Manager window that appears. Click Open. The file name should appear in the Software File. Click on Download Software to download the software. FTP or sFTP:
Enter the details (Host Address (IPv4 or IPv6), Username, Password and File Path) to locate the file. After choosing your upgrade file, select the Download Software button bottom of the Software Download area. A progress bar will appear. Restricted Use and Duplication Issue 230529 | 86 FW-600 User Guide A green status message at the top of the page will indicate if the software download succeeds. The Standby Software Version field then shows the new software load version. To load the standby software:
Select the Software Switch Over button at the top of the page. A Software Switch Over query window appears. Select the Yes button at the prompt. The system restarts using the new software image. If the banner at the top indicates that this was successful, you have finished this software upgrade procedure. Select the No button if you want to abandon this update. If there is a difference between the currently running configuration and the saved configuration, a different query window appears. Select Yes to save your configuration changes and continue with the switch over or No to continue with the software switch over and lose your configuration changes. You can select Cancel to stop the switch over completely, for instance to verify the configuration changes. If the software upgrade fails (for example, due to a corrupt load), the banner at the top of the page indicates the upgrade was unsuccessful. The system tries three (3) times to restart with the new software version; if the software upgrade attempts fail, the system reverts to the previous software version. In this case, select a different version of the new software and repeat this procedure from the beginning. Restricted Use and Duplication Issue 230529 | 87 FW-600 User Guide NOTES:
You can only upgrade the FW-600 system software from one active browser session. This means you cannot open another browser session and start another upgrade process in parallel with the first. If you try this, you get a warning message, and the system does not let you continue. Furthermore, do not close the browser once you start the upgrade; if you do or if your computer crashes, you must reset the FW-600 system that was being upgraded and start the upgrade process over. To ensure a fresh installation, after switching over to new software, please clear your browser history cache before launching a new WebUI session. 7.1.1.3. Aborting Software Download Software download can be aborted while the system is downloading the file. To abort SW download:
When a SW download has been triggered, a Software Download in Progress bar will appear. Click on the Abort Download button that is on the bar to abort the download process. A red error status message will appear at the top right corner of the page, stating that the download has been aborted. Restricted Use and Duplication Issue 230529 | 88 FW-600 User Guide NOTE: Another way to abort the software download is to open another tab on the browser, login to the eNB and navigate to Administration > Software Manager. Under Software Details, Action Status should display Download in Progress. Click on the blue x Abort Software Download button on the top of the page. Download will then be terminated. 7.1.2. SAS Cert Download To successfully authenticate and establish a TLS connection with the SAS server CBSD SAS certificate must be installed on the unit. CBSD SAS certificates are generated using the MAC address of the CBSD device and the file format would look like CBSD-0CA1380004E2-insta_rsa.certs.tgz NOTE: Certificate package is installed at factory and no operator action is required by default. The operator would need to upload new certificate only in rare scenario (e.g. certificate becomes corrupted). You can download SAS Certificate from either from an FTP server or SFTP server. To download the SAS Certificate, do the following:
Navigate to the Administration > SAS Cert Download. Within the Download SAS Certificate area, select Download Method: FTP or sFTP Enter the details (Host Address (IPv4 or IPv6), Username, Password and File Path) Once you have selected the file that you need, click on the Download button at the top right of the page. Restricted Use and Duplication Issue 230529 | 89 FW-600 User Guide A green status window will appear at the top right corner of the WebUI if download is successful. NOTE: A system reboot is required after the SAS Certificate had been downloaded. 7.1.3. IPSec Cert Download NOTE: IPSec Certificate is needed for communication with Secure Gateway (See Section 6.4.3.2), You can download IPSec Certificate from either from an FTP server or SFTP server. To download the IPSec Certificate, do the following:
Navigate to Administration > SAS Cert Download in the WebUI. Within the Download IPSec Certificate area, select Download Method: FTP or sFTP Enter the details (Host Address (IPv4 or IPv6), Username, Password and File Path) Once you have selected the correct file, click on the Download button at the top right of the page. If download is successful, you will see a green status bar appearing at the top right corner of the WebUI. Restricted Use and Duplication Issue 230529 | 90 FW-600 User Guide 7.1.4. Configuration Manager This is the page you can go to Generate a Configuration Backup File or to Restore from a previous Configuration Backup File. To generate a configuration backup file:
Navigate to Administration > Configuration Manager in the WebUI. Within the Configuration Backup/Restore section, click on the Generate Backup button. A green status bar will appear at the top right corner of the WebUI, informing you that the backup file has been successfully generated. Right click on the blue .xml file link to reveal a popup window. Select Save link as to save the configuration file to your local disk. A File Manager window will appear. Choose the location where you want to save the backup file in and click Save. Restricted Use and Duplication Issue 230529 | 91 FW-600 User Guide To restore from a Configuration Backup file:
Navigate to Administration > Configuration Manager on the WebUI Within the Configuration Backup/Restore section, click on the Browse button in the Restore from Configuration Backup File field. A File Manager window will popup. Please select the configuration backup file that you desire and hit the Restore button. A green status message will appear at the top right corner of the page if the restoration has been successful. 7.2. Events The system events are broken down into two sections:
Alarms and History 7.2.1. Alarms Page This page lists active alarms (set alarms). Once you clear the Alarm, it appears on the History page along with its details. For a list of alarms, see Appendix E. Restricted Use and Duplication Issue 230529 | 92 FW-600 User Guide Refresh Export Use the Refresh button to update the information on the screen. Use the Export button to export the csv file: active_alarms.csv Click on the blue link to download the file. The file can be viewed on Excel or other spreadsheet programs. 7.2.2. History Page The History page lists a chronological history of alarms and events along with their details. The most recent events appear first, to view older events use the page buttons or to quickly access the oldest events, use the Last button. There are three different tabs on the page: System, UE and Noise. Click on the desired tab to view the alarms/events categorized under it. NOTE: For a list of alarms and events see Appendix E. Export Clear Refresh Restricted Use and Duplication Issue 230529 | 93 FW-600 User Guide Use the Refresh button to update the information on the screen. Clear History completely clears the current alarms and events history from the FW-300i event logging infrastructure. Use the Export button to export the 3 .csv files: system_events.csv, ue_events.csv, and noise_events.csv. Once the events have been exported, click the files to download them onto the computer. The file(s) can now be viewed on Excel or other spreadsheet programs. Restricted Use and Duplication Issue 230529 | 94 FW-600 User Guide 7.3. Performance The FW-600 monitors the performance statistics for the eNB and the linked CPE(s). 7.3.1. eNB Statistics Page The eNodeB Statistics or eNB stats page is a read-only page that displays real-time eNB throughput statistics for how the FW-600 and the associated beams have been performing. The system will capture 15 samples in the last 90 seconds and display the information here. 7.3.2. UE Stats Page The Customer Premise Equipment Statistics or UE stats page is a performance read-only page that visualizes the incoming and outgoing traffic for the interface connections between the CPE and the FW-600. This allows you to see traffic and bandwidth usage for the interfaces in real-time and monitor the current download/upload throughput speeds. It also lists the current throughput performance statistics for the interfaces. NOTE: The screen refresh interval is every 5 seconds If needed, the Refresh button allows you to refresh the data immediately. Restricted Use and Duplication Issue 230529 | 95 FW-600 User Guide Reset Attach Count Refresh The UE Statistics covers:
IMSI: IMSI is used as a unique attribute to identify each SIM card within a CPE RNTI: Denotes the Radio Network Temporary Identifier (RNTI) of a connected UE Carrier Frequency: The frequency that the LTE cell is transmitting on CC: Component Carrier UL-SINR: Uplink Signal to Interference and Noise Ratio DL-RSRQ: Downlink Reference Signal Received Quality UL-RSRP: Uplink Reference Signal Received Power DL-RSRP: Downlink Reference Signal Received Power UL MCS: indicates the uplink Modulation and Coding Scheme (MCS) DL MCS: indicates the downlink Modulation and Coding Scheme (MCS) UL-BLER: Uplink Block Error Rate the ratio of the number of erroneous blocks to the total number of blocks transmitted on a digital circuit. DL-BLER: Downlink Block Error Rate DL/UL Throughput: Shows the downlink (DL) and uplink (UL) throughput (Tput) Attach Count: Number of times the CPE connected to the eNB since the eNB started up. From SW 3.0.3 onwards, there is a new Reset Attach Count feature that will reset the attach count of the CPE manually without restarting the eNB. Click on the red Reset Attach Count button and attach count for all the CPEs will start back at 1. 7.3.2.1. Advanced Option The Show Advanced Option in the UE Statistics page show more UE statistics. Restricted Use and Duplication Issue 230529 | 96 FW-600 User Guide This advanced page covers:
IMSI: IMSI is used as a unique attribute to identify each SIM card within a CPE UE Tx Power: The strength of the signal that the CPE is producing during transmission. eNB Rx Gain: Power gain that is received by the eNB. CC: Carrier Component PUSCH-SINR: The Signal to Interference plus Noise Ratio reported through Physical Uplink Shared Channel PUCCH-SINR: The Signal to Interference plus Noise reported through the Physical Uplink Control Channel Timing Advance: Timing advance is a negative offset, at the UE, between the start of a received downlink subframe and a transmitted uplink subframe. This is the value that the eNB will send to the UE to ensure that downlink and uplink subframes are synchronized at the eNB. Erasure: Erasure is a flag raised during SRS processing indicating that sounding signal level was below the noise floor. A number of consecutive SRS reports with erasure flag set is the cause of radio link failure (UE disconnection) Abnormal Release Count: The number of times when the CPE detaches unexpectedly. Failed Attach Count: The number of times when the CPE fail to attach. Connection State: UE state of connection to the eNB. 7.3.3. Core Connectivity The Core Connectivity page shows the status and parameters that the eNB had negotiated with the EPC and other upstream network components. It contains information relating to EPC Connectivity, providing details about the MMEs and SGWs that the eNB is connected to as well as information for CBRS Connectivity (if applicable). Restricted Use and Duplication Issue 230529 | 97 FW-600 User Guide 7.3.4. Network Status The Network Status page displays the IPv4 and IPv6 Routing Information. It also displays the eNB Ethernet Port statistics and thus allowing the operator/user to perform cable diagnostics easily. The page refreshes every 3 seconds. Restricted Use and Duplication Issue 230529 | 98 FW-600 User Guide 7.3.4.1. Routing Information This section displays the IPv4 and IPv6 routes tables. By default, IPv4 routes will be visible. Click on the tabs to switch between IPv4 and IPv6. To view a specific route or to view all routes:
Click on Show Route and a pop-up window will appear. Select the IP Version. Then enter the Subnet Address and the prefix length of the desired route or toggle the All Routes button to YES to display all routes. Click on Get Info to view the route(s). 7.3.4.2. Ethernet Statistics Click on the red ! Clear eth0/eth1 Counter to reset the counters. Restricted Use and Duplication Issue 230529 | 99 FW-600 User Guide Use the yellow Check eth1 Cable Health to check the current state of eth1 To see more counters, click on the blue More Counters button. This will expand the Counters column, revealing more counters:
NOTE: eth0 denotes the SFP Port while eth1 is the RJ45 port. 7.3.5. Mobility Status For the Mobility status page to appear, Mobility mode needs to be enabled and committed (See Section 6.4.1.5). Reboot the eNB and then the status page will appear under Performance on the navigation menu. This is a read only page that allows users to view the mobility status/overview of the eNB:
Restricted Use and Duplication Issue 230529 | 100 FW-600 User Guide 7.3.6. KPI Reports Cell x Measurements page, where x represents the cell number, covers Key Performance Indicators (KPI) subcategories: accessibility, retainability, availability and mobility measurements for that cell. 7.3.6.1. Accessibility RRC Establishments per Cause: details Radio Resource Control (RRC) established connections per cause RRC.ConnEstabAtt.Cause: shows established RRC connections attempts per cause Restricted Use and Duplication Issue 230529 | 101 FW-600 User Guide RRC.ConnEstabSucc.Cause: demonstrates successful RRC connections established per cause RRC Reestablishments per Cause: details Radio Resource Control (RRC) re-established connections per cause RRC.ConnReEstabAtt.Cause: shows re-established RRC connections attempts per cause RRC.ConnReEstabSucc.Cause: demonstrates successful RRC connections re-established per cause S1SIG Establishments: details established S1 signalling S1SIG.ConnEstabAtt: shows S1 signalling established connections attempts per cause S1SIG.ConnEstabSucc: demonstrates successful S1 signalling connections established per cause ERAB Establishments per QCI: details the number of established E-UTRAN Radio Access Bearers (E-RAB) per Quality of Service (QoS) Class Identifier (QCI) ERAB.EstabInitAttNbr.QCI: shows the number of established initial attempts E-RAB per QCI ERAB.EstabInitSuccNbr.QCI: shows the number of successfully established initial attempts E-RAB per QCI ERAB.EstabAddAttNbr.QCI: shows the number of additional established attempts E-RAB per QCI ERAB.EstabAddSuccNbr.QCI: shows the number of additional successfully established attempts E-RAB per QCI 7.3.6.2. Retainability ERAB Releases per QCI: details the number of E-UTRAN Radio Access Bearer (E-RAB) releases per Quality of Service (QoS) Class Identifier (QCI) ERAB.RelActNbr.QCI: shows the actual release number of E-RAB per QCI ERAB.RelEnbNbr.QCI: shows the eNB release number of E-RAB per QCI ERAB Session time: details the E-RAB active session time ERAB.SessionTimeUE: shows the active session time between the UE and the E-RAB 7.3.6.3. Availability RRU Unavailable time per Cause: provides percentage of time that the remote radio unit (RRU) is unavailable per cause (0 and 1) RRU.CellUnavailableTime.Cause 7.3.6.4. Mobility HO Preparations per QCI: provides handover(HO) preparations per standardized Quality of Service (QoS) Class Identifier (QCI) characteristics (release 12) HO.PrepAtt.QCI: specifies the attempted handover preparations per standardized QCI HO.PrepSucc.QCI: states the successful handover preparations per standardized QCI HO Executions:
HO.ExeAtt: identifies the number of handover execution attempts HO.ExeSucc: details the number of handover execution successes Restricted Use and Duplication Issue 230529 | 102 FW-600 User Guide 7.4. Troubleshooting 7.4.1. Band Scan As mentioned in Section 6.3.5.2., the FW-600 can be set to scan the frequency band automatically when it is booting up. When this feature is turned on from the Carriers > Advance > Band Scan page, the FW-600 will scan and register noise levels across the entire span of the band (150 MHz) in 5 MHz steps for all 3 cells. The results of the scan will be shown here, the read-only Troubleshooting > Band Scan page. 7.4.2. iPerf This feature allows users to verify backhaul connectivity. Throughput can be checked between two co-located ENBs, between eNB and EPC (requires iPerf on EPC), and between eNB and BLiNQ AWS iPerf servers. This allows not only the detection of potential issue(s) in the backhaul, but also help identify which hop is the likely source of the problem. Restricted Use and Duplication Issue 230529 | 103 FW-600 User Guide To set up the iPerf testing:
Navigate to Troubleshoot > iPerf Enter the required/desired values in the parameters set out in Configuration Iperf Version: Select between iPerf2 or iPerf3 Device Role: Choose between Client or Server Server: Enter the servers IP address Server Port: Enter the server port for the server to listen on and the client to connect to Local Port: Enter the local port number to be used Test Duration: Enter the duration of the test in seconds Report Interval: Enter the interval time in seconds between periodic reports Protocol: Select between TCP or UDP Number of Streams: Enter the number of streams to be tested Test Direction: Select the test direction from the drop-down menu. Summary Reports: Toggle the button to choose YES for summary reports to be generated or NO for no reports. Include Time Stats: Toggle the button to YES if time stats is to be included or NO for the time stats to be excluded. When the test parameters are entered, click on Start to start the iPerf testing. The test results will appear in the Report section. Restricted Use and Duplication Issue 230529 | 104 FW-600 User Guide NOTE: Parameters available will be changed according to the testing needs. For example, if Server is chosen for Device Role, then the WebUI will display only these parameters: Server Port, Report Interval and Protocol. 7.4.3. Network Diagnostics Under this section, users can run a traceroute test or a ping test for diagnostic purposes. 7.4.3.1. Running a Ping Test To run a ping test:
Navigate to Troubleshoot > Network Diagnostics. Under Configuration > Diagnostic Method, select ping from the drop-down menu. Enter the following parameters:
IP Version: Select either IPv4 or IPv6 Destination: Enter a valid destination IPv4/IPv6 address or domain name. Source Interface: If separate S1 interface has not been set up (See Section 6.4.3.1), the only option here will be WAN and it cannot be changed. If a separate S1 interface has been configured, then select between Mgmt (default) or S1. Ping Count: Enter the number of times to repeat ping. ICMP Payload Size: This is the size of the ping payload. Default is set at 56. Timeout: Timeout in seconds to wait for the reply. Allow Fragmentation: Toggle YES or NO to break up the packet size. When the parameters for the ping test have been entered in, click on Start to start the test. Click on Stop to stop the test. The results of the test will be shown in the Report section. Restricted Use and Duplication Issue 230529 | 105 FW-600 User Guide 7.4.3.2. Running Traceroute A traceroute works by sending Internet Control Message Protocol (ICMP) packets, and every router involved in transferring the data gets these packets. The ICMP packets provide information about whether the routers used in the transmission are able to effectively transfer the data. To run a traceroute test:
Navigate to Troubleshoot > Network Diagnostics. Under Configuration > Diagnostic Method, select traceroute from the drop-down menu. Enter the following parameters:
Destination: Enter a valid destination IPv4/IPv6 address or domain name. Source Interface: If separate S1 interface has not been set up (See Section 6.4.3.1), the only option here will be WAN and it cannot be changed. If a separate S1 interface has been configured, then select between Mgmt (default) or S1. Max Hops: A hop refers to the move data makes as it goes from one router to the next. Enter the maximum number of allowed hops here. Resolve Addresses: Toggle YES or NO for the eNB to resolve addresses. When the parameters for the ping test have been entered in, click on Start to start the test. Click on Stop to stop the test. The results of the test will be shown in the Report section. 7.4.4. Troubleshooting Guide The following is a quick troubleshooting guide:
SYMPTOM POSSIBLE CAUSE SOLUTION State LED stuck continuously on red or amber OS or configuration mismatch preventing the unit from entering functional state Reboot unit. If problem persists over multiple reboots, contact BLiNQ Networks Support. FW-600 cannot be accessed VLAN mismatch Connect computer to the FW-600 Ethernet port, open https://169.254.1.1 and verify configured VLAN (exchange with the craft IP is always untagged) Restricted Use and Duplication Issue 230529 | 106 FW-600 User Guide SYMPTOM POSSIBLE CAUSE SOLUTION Wrong IP is set Connect computer to the FW-600 Ethernet port, open https://169.254.1.1 and verify that configured IP address, subnet mask and default gateway are set properly No dynamic IP address on FW-
600 If the FW-600 is configured for DHCP, verify your network and DHCP Server configuration Browser uses HTTP instead of HTTPS Connect to the FW-600 using https://<FW-600_IP_Address>
Forgotten username/password GPS is not synchronized Refer to the eNB Password Recovery Guide to log in or contact BLiNQ Customer Support. Make sure that the system clock source has been selected to GPS under Setup > Systems > System settings. If the unit is being set up for the first time, please ensure that it has outside visibility and the top of the unit is not heavily obstructed. Please keep in mind that after power disruption that is longer than 10 minutes, GPS synchronization may take up to 45 minutes. Wrong MME IP address set Verify the MME IP address on FW-600 MME unreachable SCTP/GTP filtering eNB related misconfiguration on EPC Verify that there is network connectivity between FW-600 and MME Verify that firewall along the path does not filter SCTP or GTP traffic Verify on EPC that eNB is allowed to connect to it
(typically EPC will either work in unrestricted mode that allows any eNB to connect, or each eNB has to be allowed explicitly) MME inquiry and reply are not going through the same SecGW. Reboot eNB. (This scenario might occur after both SecGW gets disconnected and gets reconnected) Link is down due to loss of GPS sync Reboot the FW-600. FW-600 unable to form S1 link with EPC CPE unable to form link with FW-
600 Wrong RF channel number APN misconfiguration Cell range misconfiguration Link is down CPE unable to pass data traffic Link quality is poor APN misconfiguration Verify the RF channel number configured on CPE to confirm that it matches to FW-600 Verify the APN configured on CPE is the same as in the CPE profile on EPC Verify FW-600 cell range parameter is larger or equal to the distance of the furthest CPE Confirm that the RF channel number is correctly configured on CPE. Restart CPE to trigger network entry again Analyze the link performance metrics (RSRP, CINR, Tx Pwr) on the CPE to determine if its being served by the best available beam. Antenna orientation optimization may be required. If CPE is operating in bridge mode, ensure that on EPC there is an APN defined for user traffic. Restricted Use and Duplication Issue 230529 | 107 FW-600 User Guide Appendix A BLiNQ Wireless Devices and RF Safety/Les appareils sans fil BLiNQ et la scurit RF REMARQUE: La traduction franaise suit le texte anglais. BLiNQ Networks evaluates all of its products to ensure that they conform to the Radio Frequency (RF) energy emission safety limits adopted by the Federal Communications Commission (FCC). BLiNQ Networks conducts these evaluations using the compliance rules and guidelines adopted by both the FCC and Industry Canada. They are based on the results of the Maximum Permissible Exposure (MPE) studies by the FCC for mobile or fixed devices, which dictate MPE limits for human exposure to RF energy. Before selling any wireless networking device to the public, BLiNQ Networks submits its devices to the FCC and Industry Canada for MPE (that is, RF emissions) studies and evaluation. These studies must demonstrate that the device meets the accepted regulatory limits for safe RF emissions, or it is not approved for sale by the FCC and thus cannot be sold to the public. This means that when wireless networking devices, purchased from BLiNQ Networks, are installed and operated as instructed, the RF emissions from the devices is equal to or less than the levels accepted as safe by the FCC and Industry Canada. When used as intended, BLiNQ wireless networking devices do not pose health risks. Like other devices that emit RF energy (such as computers and microwave ovens), the level of RF emissions from BLiNQ devices is too low to cause harm. Further, BLiNQ wireless networking devices emit far lower levels of RF energy than cellular and cordless telephones, and are almost always used further away from the human body. To prevent unnecessary exposure to RF energy:
Always install the FW-600 system so as to provide and maintain a minimum separation distance of at least 1.1 metres (43.3 inches) for Band 48, Band 53 and at least 2 metres (78.5 inches) for Band 41, Band 42/43 from all persons. When the FW-600 system is operational, avoid standing directly in front of the FW-600 antennas. RF energy fields may be present when the transmitter is on. When the FW-600 system is operational, maintain a distance of at least 1.1 metres (43.3 inches) for Band 48, Band 53 and at least 2 metres (78.5 inches) for Band 41, Band 42/43 from the FW-600 antennas. Do not install the FW-600 system in a location where it is possible for people to stand or walk inadvertently in front of an antenna. Antenna Statement:
The antenna used for this transmitter must be installed to provide a separation distance of at least 1.1 metres
(43.3 inches) for Band 48, Band 53 and at least 2 metres (78.5 inches) for Band 41, Band 42/43 from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter. Users and installers must be provided with antenna installation instructions and transmitter operating conditions for satisfying RF exposure compliance.
Restricted Use and Duplication Issue 230529 | 108 FW-600 User Guide BLiNQ Networks value l'ensemble de ses produits afin de s'assurer qu'ils sont conformes la limite d'mission nergtique scuritaire de radiofrquence (RF) adopte par la Federal Communications Commission (FCC). BLiNQ Networks effectue ces valuations en utilisant les rgles et lignes directrices adoptes la fois par le FCC et Industrie Canada. Elles sont bases sur les rsultats de l'exposition maximale admissible, tudes menes par le FCC sur les appareils mobiles ou fixes, qui dictent les limites de l'exposition maximale admissible pour l'exposition humaine aux nergies RF. Avant de vendre tout appareil de rseau sans fil au public, BLiNQ Networks prsente ses appareils au FCC et Industrie Canada pour l'valuation de l'exposition maximale admissible. Ces tudes doivent dmontrer que l'appareil est conforme aux limites rglementaires acceptes pour les missions RF, sinon les appareils ne sont pas approuvs pour la vente par la FCC et ne peuvent donc pas tre vendus au public. Cela signifie que lorsque des quipements sans fil, achets auprs de BLiNQ Networks, sont installs et utiliss conformment aux instructions, les missions RF provenant des dispositifs sont infrieures ou gales aux niveaux accepts comme tant scuritaire par la FCC et Industrie Canada. Lorsqu'utiliss comme prvu, les priphriques sans fil BLiNQ ne posent pas de risques pour la sant. De la mme faon que les autres appareils qui mettent de l'nergie RF (comme les ordinateurs et les fours micro-ondes), le niveau des missions RF des dispositifs BLiNQ est trop faible pour causer des dommages. En outre, les dispositifs de rseau sans fil BLiNQ mettent des niveaux beaucoup plus faibles d'nergie RF que les tlphones cellulaires et sans fil, et sont presque toujours utiliss loin du corps humain. Pour viter toute exposition inutile l'nergie RF :
Installez toujours le systme FW-600 afin de fournir et de maintenir une distance de sparation minimale d'au moins 1.1 mtres (43,3 pouces) pour la bande 48 et la bande 53 et d'au moins 2 mtres (78,5 pouces) pour la bande 41 et la bande 42/43 pour les personnes. Lorsque le systme FW-600 est oprationnel, viter de se tenir directement devant les antennes du FW-600 et leurs antennes internes. Les champs d'nergie RF peuvent tre prsents lorsque l'metteur est en marche. Lorsque le systme FW-600 est oprationnel, maintenir une distance d'au moins 1.1 mtre (43,3 pouces) pour la bande 48 et la bande 53 et d'au moins 2 mtres (78,5 pouces) pour la bande 41, bande 42/43 partir des antennes du FW-600. Ne pas installer le systme FW-600 dans un endroit o il est possible pour les gens de se tenir debout ou de marcher en face d'une antenne. Dclaration dantenne:
L'antenne utilise pour cet metteur doit tre install de faon crer une distance de sparation d'au moins 1.1 mtre (43,3 pouces) pour la bande 48 et la bande 53 et d'au moins 2 mtres (78,5 pouces) pour la bande 41, bande 42/43 de toute personne et ne doit pas tre co-localises ou oprant en conjonction avec une autre antenne ou metteur. Les utilisateurs et les installateurs doivent avoir reus des instructions d'installation de l'antenne et des conditions de fonctionnement de l'metteur pour satisfaire la conformit aux expositions RF. Restricted Use and Duplication Issue 230529 | 109 FW-600 User Guide Equipment Compliance Federal Communications Commission (FCC) Notices This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. 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:
Reorient or relocate the receiving antenna. Increase the separation between the equipment and 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. This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions:
(1) This device may not cause harmful interference, and
(2) This device must accept any interference received, including interference that may cause undesired operation. CAUTION: Any changes or modifications not expressly approved by BLiNQ Networks could void the user's authority to operate this equipment. Restricted Use and Duplication Issue 230529 | 110 FW-600 User Guide Appendix B ISED Non-Interference Disclaimer The FW-600 contains licensed transmitter(s)/receiver(s) that comply with Innovation, Science and Economic Development Canadas licensed RSS(s). Operation is subject to the following two conditions:
(1) The FW-600 may not cause interference.
(2) the device. The FW-600 must accept any interference, including interference that may cause undesired operation of The FW-600 complies with the Canadian ICES-003 Class B specifications. CAN ICES-003(B) / NMB-003 (B). Lmetteur/rcepteur autorise contenu dans le prsent appareil est conforme aux CNR dInnovation, Sciences et Dveloppement conomique Canada applicables aux appareils radio autorise. Lexploitation est autorise aux deux conditions suivantes :
(1) le systme FW-600 ne doit pas produire de brouillage;
(2) susceptible den compromettre le fonctionnement. le systme FW-600 doit accepter tout brouillage radiolectrique subi, mme si le brouillage est Cet appareil numrique de la Canadian ICES-003. Cet appareil numrique de la classe B est conforme la norme NMB-003 du Canada. Restricted Use and Duplication Issue 230529 | 111 FW-600 User Guide Appendix C PCI Planning Guidelines When setting up your system, you must abide by the rules outlined below, to minimize Physical Cell ID (PCI) collision and enforce an effective PCI assignment strategy:
Rule 1: Same PCI Utilization Multiple cells within a FW-600 on the same frequency should not have the same PCI Immediate neighbour cells on the same frequency should not have the same PCI Rule 2: PCI MOD3 Cells on the same frequency within a similar coverage area must not have the same PCI MOD3 (i.e., PCIcellA
!= PCIcellB) Occurs due to the fact that when PCI X is changed by a factor of X+3n (where n is an integer) there is a collision on the reference signals between the two antenna ports, i.e., between the PCI[X]-antenna port0 and PCI[X+3n]-antenna port1 Applicable for MIMO transmission only Rule 3: PCI MOD6 Cells on the same frequency within a similar coverage area must not have the same PCI MOD6 Applicable for SISO transmission only Rule 4: PCI MOD30+
Cells on the same frequency within a similar coverage area must not have the same PCI MOD30 Occurs due to the collision of the uplink (UL) reference signals (RS) which leads to a higher bit error rate
(BER) in the UL Rule 5: PCI MOD50 (20MHz Bandwidth (BW)) or PCI MOD25 (10MHz BW) Cells on the same frequency within a similar coverage area must not have the same PCI MOD50/MOD25 Occurs due to the collision on the Physical Control Format Indicator Channel (PCFICH) which leads to failure in decoding on the Physical Downlink Control Channel (PDCCH) Rule 6: Cell Group ID Correlation Cell Group ID is derived from two length-31 binary m-sequences (m0, m1) Each time m0/m1 repeats, the overall correlation between the two Cell Group ID values is higher No impact to the performance of Key Performance Indicators (KPI) due to this type of interference Only causes network entry delay (by 5-10ms) Restricted Use and Duplication Issue 230529 | 112 FW-600 User Guide Appendix D Commonly Used DSCP Values The table below lists the commonly used DSCP values that can be configured with the QCIs in Section 6.2.4.3. DSCP Name Binary Value Decimal Value TABLE G COMMONLY USED DSCP VALUES CS0 CS1 CS2 CS3 CS4 CS5 CS6 CS7 AF11 AF12 AF13 AF21 AF22 AF23 AF31 AF32 AF33 AF41 AF42 AF43 EF 000000 001000 010000 011000 100000 101000 110000 111000 001010 001100 001110 010010 010100 010110 011010 011100 011110 100010 100100 100110 101110 VOICE-ADMIT 101100 0 8 16 24 32 40 48 56 10 12 14 18 20 22 26 28 30 34 36 38 46 44 Reference RFC 2474 RFC 2474 RFC 2474 RFC 2474 RFC 2474 RFC 2474 RFC 2474 RFC 2474 RFC 2597 RFC 2597 RFC 2597 RFC 2597 RFC 2597 RFC 2597 RFC 2597 RFC 2597 RFC 2597 RFC 2597 RFC 2597 RFC 2597 RFC 3246 RFC 5865 Restricted Use and Duplication Issue 230529 | 113 FW-600 User Guide Appendix E UEs Supported for Different Carrier Aggregation Modes TABLE H ACTIVE UES SUPPORTED PER SECTOR/BEAM PER ENB eNB Model #
Total UEs*
(Per Base Unit) 1 CC 2CC 3CC 2CC + 1CC Active UEs per Sector or Beam Active UEs FW3-B48-00-NA FW3-B48-00-HP-NA FW3-B42-43-HP-EU FW3-B48-46-HP-NA FW6-B48-00-NA FW6-B42-43-EU FW6-B41-00-WW FW6-B48-46-NA FW6-B53-00-NA X3I-35-00-WW-OD X3I-35-00-WW-POE X3I-35-50-WW-POE 288 288 288 96 288 288 288 192**
288 288 288 288 48 48 48 48 48 48 48 48 48 48 48 48
*Up to 3 carriers per base unit unless otherwise stated.
**Up to 6 carriers per base unit. 32 32 32 32 32 32
32
32 32 32 32 32 32 32 32 32
32
32 + 48 32 + 48 32 + 48
32 + 48 32 + 48
32 + 48 32 + 48
Restricted Use and Duplication Issue 230529 | 114 FW-600 User Guide Appendix F
(Fault Management) Alarms and Events This appendix lists the alarms and events for the BLiNQ FW-600 system. NOTE: There is no need to open the FW-600 module casing. If there is an unsolvable problem or a module malfunction, please contact BLiNQ Customer Support for help or a return merchandise authorization (RMA) number/procedure. The FW-600 system issues an alarm notification when a fault condition occurs. You view alarms through the:
FW-600 WebUI Events > Alarms page (See Section 7.2.1) or on the CLI via the show event-history command These alarms require operation and maintenance actions to restore functionality and/or to prevent a more serious situation from developing. Table I List of Alarms shows each alarm (whose name also represents the particular problem), the alarm ID, type and explanation on the likely cause of the alarm and possible solution (as applicable). The FW-600 system issues an event notification when something of importance happens that does not trigger an alarm, but is considered significant enough to take note. You view these events through the:
FW-600 WebUI Events > History page (See Section 7.2.2) or On the CLI via the show event-history command. Table J List of Events shows each event (whose name also represents the particular problem), the event ID, type and explanation on the likely cause of the event. Severity is also defined for each listed alarm and event, to indicate the relative level of urgency for operator action:
CRITICAL the alarm or event requires immediate corrective action, regardless of the time. Major the alarm or event requires immediate corrective action, within working hours. Minor the alarm or event requires corrective action at a suitable time or, at least, continuous close observation. Warning the alarm or event requires corrective action on a scheduled maintenance basis. Information the alarm or event requires no corrective action; it is for informational purposes only. Restricted Use and Duplication Issue 230529 | 115 FW-600 User Guide TABLE I LIST OF ALARMS ID Name Description/Comments Type Severity 1002 PHY Queue Full 3004 Software Boot Failure 4001 Ethernet Port Down 5004 Radio Disabled 5006 Radio Module Down 5008 Radio Temperature Warning 5009 Radio RF Calibration 5014 5015 Radio DCA No Frequency Available Radio Board Information Error 5016 Board Detection Error 5017 Radio Beam Down PHY has stopped processing because the queue is full This may indicate a physical or logical corruption of the system non-volatile storage. Ethernet link is down, can be caused by Eth cable unplugged or connected port defective, administratively disabled, equipment down, etc. System recovers when Ethernet link is re-established. An operator has administratively disabled the radio in the unit. Identified per beam. Configuration issue e.g. radio enabled but not used by any beam. Identified per RF instance. The radio operating temperature has exceeded the normal operating range. Identified per beam. This alarm usually indicates a hardware failure. The unit should be replaced. Identified per RF instance. The system is using all the available frequency channels and pauses the jump sequence to prevent flip-flopping. Comms1. CRITICAL Equip. CRITICAL Comms2. Major Equip.3 Major Equip. Major Equip. Major Equip. CRITICAL Comms. Minor Board information is wrong or invalid. Comms. CRITICAL Board 1611 not detected / Board 1611 detected but not expected / Board 1610 not detected PRACH configuration index does not match beam. Equip. CRITICAL Comms. CRITICAL 5018 RF Mute All carriers are muted by user operation. Equip. Notification 5020 Radio Carrier Down All active RF carriers are down 5021 PAM Warning Power Amplifier Module (PAM) is in abnormal state. Equip. Equip. Major Major 1 Comms = Communications 2 Comms = Communications 3 Equip. = Equipment Restricted Use and Duplication Issue 230529 | 116 FW-600 User Guide ID Name Description/Comments Type Severity 6002 GPS Antenna Failure 6003 Hardware Temperature This indicates a hardware fault with the GPS antenna of the FW-600. The alarm triggers with 2 severity levels:
- Major - this warns that temperature is above normal range (85C) and
- Critical - when the temperature exceeds safety limits and the radio is stopped (90C). Equip. CRITICAL Equip. Major/
CRITICAL 6004 Phy Start Issue Failure to load or start the PHY code. Comms. CRITICAL 6005 RF Power Amp Issue 6006 CA Chain Issue 6007 Core Crash 6008 TX Rx Issue 6009 DSP Startup Error 7001 System GPS Synchronization Lost 7002 System Synchronization Failed 7010 DHCP Server Unavailable 9003 PM Automatic File Upload Failure 1611 could not start, power failure or other issue RF card not Carrier Aggregation (CA) capable. Badly configured CA chain. Equip. CRITICAL Comms. CRITICAL Crash will be identified in the description on dashboard Equip. CRITICAL FPGA stopped generating Tx and Rx signal PHY initialization stuck when DSPs cannot be started. When operating in GPS mode, the GPS receiver has lost synchronization. When operating in 1588 mode, the 1588 client has lost communication with the 1588 master clock. Upon FW-600 reset, this alarm is not raised until 60 s after reset and if synchronization still is not achieved. After holdover time expires (5 minutes), system transitions to unsynchronized state. When operating in GPS mode, the GPS receiver has lost synchronization. When operating in 1588 mode, the 1588 client has lost communication with the 1588 master clock. This alarm is raised when the module fails to achieve system timing synchronization. Probably caused by a loss of signal. The system has not been able to obtain a DHCP address. The unit could not perform the FTP transfer of the performance data. The FTP system is inaccessible. (Module cannot upload PM files to the specified server. Indicates a server connectivity or access error. System recovers when Comms. CRITICAL Equip. CRITICAL Comms. Major Equip. CRITICAL Comms. Major Comms. Minor Restricted Use and Duplication Issue 230529 | 117 FW-600 User Guide ID Name Description/Comments connectivity/access to the PM server is restored.) Type Severity 9005 Invalid UE ID Un-recoverable Dataplane error Comms. Minor 11001 11002 SAS Server Registration Failure (CBSD) Grant Suspended or Terminated (CBSD) 11002 Noise Alarm Registration with SAS server failed. Comms. CRITICAL Grant was suspended or terminated by SAS server. Noise level surpassed threshold levels set in Carriers > Advanced > Band Scan Comms. CRITICAL Comms. Major Equip. Major Comms. CRITICAL 12001 S1 State Enabled 12011 EEPC Lost S1 disabled/enabled EPC Connection Lost TABLE J LIST OF EVENTS ID Name Description/Comments Type Severity 2001 Configuration Changed A configuration change has been committed to the running configuration. System Information 3001 Software Download Downloading software image. System Information 3002 3003 Software Download Successful Software Download Error 3004 Software Boot Failure 5004 Radio Module Disabled Successful download of software image. System Information Software error: A software download is already in progress. This may indicate a physical or logical corruption of the system non-volatile storage. Radio Module is initialized and has received an administrative disable configuration. System Minor Equip. CRITICAL Equip. Information 7003 System Synchronized GPS entered synchronized state. Equip. Information 7004 GPS State Change 8001 Authentication Failed The GPS state machine gained or lost GPS synchronization (specific state indicated by the comment text). Attempts to authenticate on one of the management interfaces of the equipment failed. Equip. Information Security Warning 10001 License successfully applied A license was successfully applied to module. System Major 10002 Invalid license Invalid license: Digital signature does not match license content. System Major Restricted Use and Duplication Issue 230529 | 118 FW-600 User Guide ID Name Description/Comments Type Severity 10003 License not applicable 12001 12002 12003 S1 State Enabled Event
(ENB) UE Attached Event
(ENB) UE Detached Event
(ENB) License not applicable to module: MAC address does not match filter or license capabilities do not match the hardware. System Major S1 State Enabled System Information User Equipment (UE) Attached System Information UE Detached System Information 12005 PCI Changed Cell (x) PCI changed by eSON System Information 12006 NRT Conflict Beam (X) has a PCI conflict System Information 12007 NRT Confusion Beam (X) has a PCI confusion System Information 12008 UE Connection Event UE disconnected. IMSI number as identified. System Information 12009 NRT Added Cell (X) added neighbor PCI System Information 12010 NRT Remove Cell (X) removed neighbor PCI System Information Restricted Use and Duplication Issue 230529 | 119 FW-600 User Guide Appendix G List of Acronyms Acronyms Meaning 3GPP Third Generation Partnership Project AAA AES AF AISG AMBR AMF APN Az BER BLER BW CBRS CBSD CA CC CFI CFR CINR CLI CPE CPI CQI Authentication, Authorization and Accounting (centralized networking protocol) Advanced Encryption Standard Assured Forwarding behavior, DSCP Antenna Interface Standards Group Aggregate Maximum Bit Rate Access and Mobility Management Function Access Point Name Azimuth Bit Error Rate Block Error Rate Beamwidth Citizens Broadband Radio Service Citizens Broadband Radio Service Device Carrier Aggregation Component Carrier Control Format Indicator Crest Factor Reduction Carrier to Interference plus Noise Ratio Command Line Interface Customer Premise Equipment Certified Professional Installer Channel Quality Indicator Craft IP IP address typically used by technical personnel to test the equipment CS CSG CW dB dBi dBm Class Selector, DSCP Closed Subscriber Group Continuous Wave (carrier) Decibels Decibel isotropic Decibels per Milliwatt Restricted Use and Duplication Issue 230529 | 120 FW-600 User Guide Acronyms Meaning DC DCA DHCP DL DSCP DNS Direct Current Dynamic Channel Assignment Dynamic Host Configuration Protocol Downlink Differentiated Services Code Point Domain Name System EARFCN Evolved Absolute Radio Frequency Channel Number (LTE) EF EIRP EMS eNB eNodeB EPC ERAB Expedited Forwarding behavior, DSCP Equivalent/Effective Isotropic Radiated Power Element Management System See eNodeB E-UTRAN Node B, also identified as Evolved Node B (abbreviated as eNodeB or eNB) is an element of an LTE Radio Access Network (RAN) Evolved Packet Core E-UTRAN Radio Access Bearer EUTRAN Evolved Universal Terrestrial Radio Access Network FCAPS Fault, Configuration, Accounting, Performance, and Security FCC FTP GHz GPS GTP Federal Communications Commission File Transfer Protocol Gigahertz Global Positioning System GPRS Tunneling Protocol HARQ Hybrid Automatic Repeat Request HO HP HTTP HTTPS IMSI IP IPSec ISDN Kbps KM KPI Handover High Power Hyper Text Transfer Protocol Hyper Text Transfer Protocol Secure International Mobile Subscriber Identity Internet Protocol Internet Protocol Security Integrated Services Digital Network Kilobits per second Kilometres Key Performance Indicators Restricted Use and Duplication Issue 230529 | 121 FW-600 User Guide Acronyms Meaning LOS LTE MAC Mbps MCC MCS MFBI MHz Line-of-Sight Long Term Evolution refers to a mobile device, high-speed, wireless communications standard. Media Access Control Megabits per second Mobile Country Code Modulation and Coding Scheme Multi-Frequency Band Indicator Megahertz MIMO Multiple Input Multiple Output MIMO-SM Multiple Output-Spatial Multiplexing MME MNC MPE Mobility Management Entity; the key control-node for the LTE access-network Mobile Network Code Maximum Permissible Exposure MS or Msec Millisecond MSR NA NAT NTP OAM OPc PAM PBCH PCCH Multi-Standard Radio North America Network Address Translation Network Time Protocol Operations, Administration and Maintenance Operator Code Power Amplifier Module Physical Broadcast Channel Paging Control Channel (PCCH) PCFICH Physical Control Format Indicator Channel PCI Physical Cell ID PDCCH Physical Downlink Control Channel PDN PDSCH PHICH PHR PHY Packet Data Network Physical Downlink Shared Channel Physical Hybrid-Automatic Repeat Request (ARQ) (HARQ) Indicator Channel Power Headroom Report Physical Layer PLMN-ID Public Land Mobile Network Identifier (PLMN-ID = MCC + MNC) PM Performance Measurement Restricted Use and Duplication Issue 230529 | 122 FW-600 User Guide Acronyms Meaning PPS Pulse Per Second PRACH Physical Random Access Channel PSS PUCCH PUSCH QAM QCI QoS QPSK Primary Synchronization Signal Physical Uplink Control Channel Physical Uplink Shared Channel Quadrature Amplitude Modulation QoS Class Identifier Quality of Service Quadrature Phase Shift Keying RADIUS Remote Authentication Dial-In User Service RACH Random Access Channel RAN RET RF RI RNTI RRC RRU RS RSSI RSCP RSRQ RSRP RTP RX s S1 SAS SCH SCTP SecGW SFP SFTP Radio Access Network Remote Electrical Tilt Radio Frequency Rank Indication Radio Network Temporary Identifier Radio Resource Control Remote Radio Unit Reference Signal Received Signal Strength Indicator Received Signal Code Power Reference Signal Received Quality Reference Signal Received Power Received Target Power Received Second Interface between an eNB and the Core Network (CN) Spectrum Access System Shared Channel Stream Control Transmission Protocol Security Gateway Small form-factor pluggable Secure File Transfer Protocol Restricted Use and Duplication Issue 230529 | 123 FW-600 User Guide Acronyms Meaning SGW SIM SINR SISO SKU SLA Serving Gateway; routes and forwards user data packets, also acts as mobility anchor Subscriber Identity Module Signal to Interference plus Noise Ratio Single Input Single Output Stock Keeping Unit Service Level Agreement SNMP Simple Network Management Protocol SR SRS SSH SW Scheduling Request Sounding Reference Signal Secure Shell protocol Software TACACS Terminal Access Controller Access Control System TACACS+
Terminal Access Controller Access Control System Plus TCP TCP/IP TDD TDM TX Transmission Control Protocol Transmission Control Protocol/Internet Protocol Time Division Duplexing Time Division Multiplexed Transmit UDP/IP User Datagram/Internet Protocol UE UI UL UMTS U-NII URL User Equipment User Interface Uplink Universal Mobile Telecommunications System Unlicensed National Information Infrastructure Universal Resource Locator UTRAN UMTS Terrestrial Radio Access Network VDC VLAN VSWR WAN XML Volts Direct Current Virtual Local Area Network Voltage Standing Wave Ratio Wide Area Network Extensible Markup Language Restricted Use and Duplication Issue 230529 | 124 FW-600 User Guide Restricted Use and Duplication Issue 230529 | 125 Copyright 2014-2023 BLiNQ Networks Inc. CONFIDENTIAL INFORMATION RESTRICTED USE AND DUPLICATION All rights reserved. The information contained in this document is proprietary to BLiNQ Networks Inc. This document may not i n whole or in part be copied, reproduced, or reduced to any medium without prior consent, in writing, from BLiNQ Networks Inc. Disclaimer The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable but are presented without express or implied warranty. Additionally, BLiNQ Networks makes no representations or warranties, either expressed or implied, regarding the contents of this product. BLiNQ Networks shall not be liable for any misuse regard ing this product. The information in this document is subject to change without notice.
1 | Label and Label Location | ID Label/Location Info | 190.20 KiB | June 27 2023 / June 28 2023 |
BLIN G))) N E TW QO RK S MN: FW6-B53-00-NA 48V 2.1A--
FCC ID:ROR0013 IC: 10794A-FW600B53 NETWORKS MN: PWE-BSS.00.NW ABV 10A==
POWER ABOVE 23d8m_ WITH RF PORTS OPEN BLIN G))) N E TW QO RK S MN: FW6-B53-00-NA 48V 2.1A--
FCC ID:ROR0013 IC: 10794A-FW600B53
1 | Attestation statement | Cover Letter(s) | 190.70 KiB | June 27 2023 / June 28 2023 |
U.S. Agent Designation for Service of Process -
Certification Attestation Letter June 15, 2023 Nemko North America, Inc. 303 River Road Ottawa K1V 1H2 Canada ATTN.: Reviewing Engineer FCC ID: ROR0013 Per section 2.911(d)(7) of the FCC rules, BLiNQ Networks Inc. (the applicant) certifies that the equipment for which authorization is sought is designated to the following U.S. Designated agent* for service of process:
Company Name:
Physical U.S. Company Address:
Agent name:
Agent Email Address:
FRN:
Communication Components Inc. 89 Leuning Street, South Hackensack NJ 07606 Dennis Nathan dnathan@cciproducts.com 0006034995 The above contact person accepts the obligation for service of process. The applicant accepts to maintain an agent for no less than one year after the grantee has terminated all marketing and importation or the conclusion of any Commission-related proceeding involving the equipment. Applicant Signed:
Designated
(Required, if different to Applicant):
Agent Signed:
Signed:
Printed name: Jim Dickerman VP Operations Title:
BLiNQ Networks Inc. Company Name:
Date:
June 13, 2023 Signed:
Printed name: Dennis Nathan Title:
Company Name:
Date:
President Communication Components Inc. June 14, 2023 Communication Component Systems, Inc. Confidential 89 Leuning Street, South Hackensack, NJ 07606 201-342-3338 Fax 201-342-3339 www.cciproducts.com
1 | Cover Letters | Cover Letter(s) | 1.13 MiB | June 27 2023 / June 28 2023 |
COMMUNICATION COMPONENTS INC. N EE TW OO R K S&S May 24, 2023 Nemko North America, Inc. 303 River Road, Ottawa, Ontario, Canada K1V 1H2 Attn: Director of Certification Request for Confidentiality FCC FCC ID: RORO013 Pursuant to FCC 47 CFR 0.457(d)(1)(ii) and 0.459 and FCC guidance published in KDB 726920, we hereby request confidential treatment of information accompanying this application as outlined below. We request the exhibits selected below as long term confidential (LTC) be withheld from public view permanently:
Selection of exhibits for LTC - general Exhibit name Operation Description / Theory of Operation
& Permanent (Long Term) Schematics oO Permanent (Long Term) SDR Software / Security Info Selection of exhibits for LTC (with NDA) Exhibit name
! |__ 5 O Permanent (Long Term) Internal Photos We also request the exhibits selected below as short term confidential (STC) be withheld from public view for a period of 120 days from the date of the Grant of Equipment Authorization and prior to marketing. This is to avoid premature release of sensitive information prior to marketing or release of the product to the public:
Selection O Short Term We O Short Term Schematics
& Short Term Internal Photos Oo Short Term Test Setup Photos
'_ Tune up procedure is applicable only for licensed equipment. SDR Software is only applicable for licensed SDRs. 2. These items require further information to be provided to TCB before permanent confidentiality will be extended to these exhibits. Please refer to FCC KDB 726920 and review section II, 3) regarding specific information (NDA) that must accompany these requests. 3 _ Number of days can be listed up to 180 but should not go past the date of beginning of product marketing/sale. 4. Any exhibits that may have already been requested to have Permanent confidentiality need not be repeated under Short-Term confidentiality request. COMMUNICATION COMPONENTS INC. E Short Term Tune-Up Procedure (for Licensed equipment only) Our company has spent a substantial effort in developing this product and it is one of the first of its kind in the industry. Having the subject information easily available to "competition" would negate the advantage they have achieved by developing this product. Not protecting the details of the design will result in financial hardship. When the device is marketed before the requested number of days listed above, the grantee will inform the TCB to release the Short-Term Confidentiality information withheld on the FCC equipment authorization website. COMMUNICATION COMPONENTS INC. N E TW O R K S&S The above information contains trade secrets and proprietary information not customarily released to the public. The public disclosure of this information might be harmful to the applicant and provide unjustified benefits to its competitors. The Applicant understands that pursuant to Rule 0.457(d)(1)(ii), disclosure of this Application and all accompanying materials will not be made before the date of the Grant for this Application. Sincerely, Jim Dickerman Print name Signed by:
VP Operations Title
frequency | equipment class | purpose | ||
---|---|---|---|---|
1 | 2023-06-28 | 2489 ~ 2489 | TNB - Licensed Non-Broadcast Station Transmitter | Original Equipment |
app s | Applicant Information | |||||
---|---|---|---|---|---|---|
1 | Effective |
2023-06-28
|
||||
1 | Applicant's complete, legal business name |
Blinq Networks Inc.
|
||||
1 | FCC Registration Number (FRN) |
0022440390
|
||||
1 | Physical Address |
140 Renfrew Drive
|
||||
1 |
Markham, N/A L3R 6B3
|
|||||
1 |
Canada
|
|||||
app s | TCB Information | |||||
1 | TCB Application Email Address |
j******@nemko.com
|
||||
1 | TCB Scope |
B4: Microwave, Millimeter Wave Band and Citizens Broadband Radio Services equipment in 47 CFR Parts 25, 30, 74, 90, 95, 96, 97, 101 (all above 3 GHz)
|
||||
app s | FCC ID | |||||
1 | Grantee Code |
ROR
|
||||
1 | Equipment Product Code |
0013
|
||||
app s | Person at the applicant's address to receive grant or for contact | |||||
1 | Name |
J******** D********
|
||||
1 | Title |
Vice President Engineering
|
||||
1 | Telephone Number |
416-2******** Extension:
|
||||
1 | Fax Number |
613-5********
|
||||
1 |
j******@blinqnetworks.com
|
|||||
app s | Technical Contact | |||||
n/a | ||||||
app s | Non Technical Contact | |||||
n/a | ||||||
app s | Confidentiality (long or short term) | |||||
1 | Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | Yes | ||||
1 | Long-Term Confidentiality Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | Yes | ||||
1 | If so, specify the short-term confidentiality release date (MM/DD/YYYY format) | 10/26/2023 | ||||
if no date is supplied, the release date will be set to 45 calendar days past the date of grant. | ||||||
app s | Cognitive Radio & Software Defined Radio, Class, etc | |||||
1 | Is this application for software defined/cognitive radio authorization? | No | ||||
1 | Equipment Class | TNB - Licensed Non-Broadcast Station Transmitter | ||||
1 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | LTE Base Station | ||||
1 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
1 | Modular Equipment Type | Does not apply | ||||
1 | Purpose / Application is for | Original Equipment | ||||
1 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | No | ||||
1 | Related Equipment: Is the equipment in this application part of a system that operates with, or is marketed with, another device that requires an equipment authorization? | No | ||||
1 | Grant Comments | Output power listed is EIRP per port based on the antenna described in this filing. End-users and installers must be provided with antenna installation instructions and transmitter operating conditions for satisfying RF exposure compliance. This device supports bandwidth of 10 MHz for LTE Band 53. | ||||
1 | Is there an equipment authorization waiver associated with this application? | No | ||||
1 | If there is an equipment authorization waiver associated with this application, has the associated waiver been approved and all information uploaded? | No | ||||
app s | Test Firm Name and Contact Information | |||||
1 | Firm Name |
Nemko Canada Inc. (Cambridge)
|
||||
1 | Name |
C******** N****
|
||||
1 | Telephone Number |
613-7******** Extension:
|
||||
1 |
c******@nemko.com
|
|||||
Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
1 | 1 | 25 | EP M4 | 2489.00000000 | 2489.00000000 | 3.7150000 | 1.2000000000 ppm | 10M0W7D |
some individual PII (Personally Identifiable Information) available on the public forms may be redacted, original source may include additional details
This product uses the FCC Data API but is not endorsed or certified by the FCC