Page 1
System
Manual
BreezeCOMPACT LTE
SSystem Manual
RR6.9
System
Manual
Release Version: 7.2
June 2019
Rev 0.9
Page 2
BreezeCOMPACT System Manual
Chapter 1: System
Description
2
Legal Rights
Trade Names
Statement of Conditions
Warranties and Disclaimers
Exclusive Warranty
© Copyright 2018 Telrad Networks Ltd. All rights reserved.
The material contained herein is proprietary, privileged, and confidential and owned by Telrad
Networks or its third party licensors. No disclosure thereof shall be made to third parties
without the express written permission of Telrad Networks Ltd.
Telrad Networks Ltd. reserves the right to alter the equipment specifications and descriptions
in this publication without prior notice. No part of this publication shall be deemed to be part
of any contract or warranty unless specifically incorporated by reference into such contract or
warranty.
BreezeCOM®, BreezeMAX®, 4Motion® and/or other products and Telrad Networks/or services
referenced herein are either registered trademarks, trademarks or service marks of Telrad
Networks Ltd.
All other names are or may be the trademarks of their respective owners.
The information contained in this manual is subject to change without notice. Telrad Networks
Ltd. shall not be liable for errors contained herein or for incidental or consequential damages
in connection with the furnishing, performance, or use of this manual or equipment supplied
with it.
All Telrad Networks Ltd. (“Telrad Networks“) products purchased from Telrad Networks or
through any of Telrad Networks' authorized resellers are subject to the following warranty and
product liability terms and conditions.
(a) Telrad Networks warrants that the Product hardware it supplies and the tangible media on
which any software is installed, under normal use and conditions, will be free from significant
defects in materials and workmanship for a period of fourteen (14) months from the date of
shipment of a given Product to Purchaser (the "Warranty Period"). Telrad Networks will, at its
sole option and as Purchaser's sole remedy, repair or replace any defective Product in
accordance with Telrad Networks' standard R&R procedure.
(b) With respect to the Firmware, Telrad Networks warrants the correct functionality
according to the attached documentation, for a period of fourteen (14) month from invoice date
(the "Warranty Period")". During the Warranty Period, Telrad Networks may release to its
Customers firmware updates, which include additional performance improvements and/or bug
fixes, upon availability (the "Warranty"). Bug fixes, temporary patches and/or workarounds
may be supplied as Firmware updates.
Additional hardware, if required, to install or use Firmware updates must be purchased by the
Customer. Telrad will be obligated to support solely the two (2) most recent Software major
releases.
TELRAD NETWORKS SHALL NOT BE LIABLE UNDER THIS WARRANTY IF ITS
TESTING AND EXAMINATION DISCLOSE THAT THE ALLEGED DEFECT IN THE
PRODUCT DOES NOT EXIST OR WAS CAUSED BY PURCHASER'S OR ANY THIRD
PERSON'S MISUSE, NEGLIGENCE, IMPROPER INSTALLATION OR IMPROPER
TESTING, UNAUTHORIZED ATTEMPTS TO REPAIR, OR ANY OTHER CAUSE BEYOND
THE RANGE OF THE INTENDED USE, OR BY ACCIDENT, FIRE, LIGHTNING OR OTHER
HAZARD.
Page 3
BreezeCOMPACT System Manual
Chapter 1: System
Description
3
Disclaimer
Limitation of Liability
(a) The Software is sold on an "AS IS" basis. Telrad Networks, its affiliates or its licensors
MAKE NO WARRANTIES, WHATSOEVER, WHETHER EXPRESS OR IMPLIED, WITH
RESPECT TO THE SOFTWARE AND THE ACCOMPANYING DOCUMENTATION.
TELRAD NETWORKS SPECIFICALLY DISCLAIMS ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT WITH RESPECT TO THE SOFTWARE. UNITS OF PRODUCT
(INCLUDING ALL THE SOFTWARE) DELIVERED TO PURCHASER HEREUNDER ARE
NOT FAULT-TOLERANT AND ARE NOT DESIGNED, MANUFACTURED OR INTENDED
FOR USE OR RESALE IN APPLICATIONS WHERE THE FAILURE, MALFUNCTION OR
INACCURACY OF PRODUCTS CARRIES A RISK OF DEATH OR BODILY INJURY OR
SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE ("HIGH-RISK ACTIVITIES"). HIGHRISK ACTIVITIES MAY INCLUDE, BUT ARE NOT LIMITED TO, USE AS PART OF ONLINE CONTROL SYSTEMS IN HAZARDOUS ENVIRONMENTS REQUIRING FAIL-SAFE
PERFORMANCE, SUCH AS IN THE OPERATION OF NUCLEAR FACILITIES, AIRCRAFT
NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL, LIFE
SUPPORT MACHINES, WEAPONS SYSTEMS OR OTHER APPLICATIONS
REPRESENTING A SIMILAR DEGREE OF POTENTIAL HAZARD. TELRAD NETWORKS
SPECIFICALLY DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY OF FITNESS FOR
HIGH-RISK ACTIVITIES.
(b) PURCHASER'S SOLE REMEDY FOR BREACH OF THE EXPRESS WARRANTIES
ABOVE SHALL BE REPLACEMENT OR REFUND OF THE PURCHASE PRICE AS
SPECIFIED ABOVE, AT TELRAD NETWORKS'S OPTION. TO THE FULLEST EXTENT
ALLOWED BY LAW, THE WARRANTIES AND REMEDIES SET FORTH IN THIS
AGREEMENT ARE EXCLUSIVE AND IN LIEU OF ALL OTHER WARRANTIES OR
CONDITIONS, EXPRESS OR IMPLIED, EITHER IN FACT OR BY OPERATION OF LAW,
STATUTORY OR OTHERWISE, INCLUDING BUT NOT LIMITED TO WARRANTIES,
TERMS OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, SATISFACTORY QUALITY, CORRESPONDENCE WITH DESCRIPTION, NONINFRINGEMENT, AND ACCURACY OF INFORMATION GENERATED, ALL OF WHICH
ARE EXPRESSLY DISCLAIMED. TELRAD NETWORKS' WARRANTIES HEREIN RUN
ONLY TO PURCHASER, AND ARE NOT EXTENDED TO ANY THIRD PARTIES. TELRAD
NETWORKS NEITHER ASSUMES NOR AUTHORIZES ANY OTHER PERSON TO ASSUME
FOR IT ANY OTHER LIABILITY IN CONNECTION WITH THE SALE, INSTALLATION,
MAINTENANCE OR USE OF ITS PRODUCTS.
(a) TELRAD NETWORKS SHALL NOT BE LIABLE TO THE PURCHASER OR TO ANY
THIRD PARTY, FOR ANY LOSS OF PROFITS, LOSS OF USE, INTERRUPTION OF
BUSINESS OR FOR ANY INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE OR
CONSEQUENTIAL DAMAGES OF ANY KIND, WHETHER ARISING UNDER BREACH OF
CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY OR OTHERWISE
AND WHETHER BASED ON THIS AGREEMENT OR OTHERWISE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGES.
(b) TO THE EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL THE
LIABILITY FOR DAMAGES HEREUNDER OF TELRAD NETWORKS OR ITS EMPLOYEES
OR AGENTS EXCEED THE PURCHASE PRICE PAID FOR THE PRODUCT BY
PURCHASER, NOR SHALL THE AGGREGATE LIABILITY FOR DAMAGES TO ALL
PARTIES REGARDING ANY PRODUCT EXCEED THE PURCHASE PRICE PAID FOR
THAT PRODUCT BY THAT PARTY (EXCEPT IN THE CASE OF A BREACH OF A PARTY'S
CONFIDENTIALITY OBLIGATIONS).
Page 4
BreezeCOMPACT System Manual
Chapter 1: System
Description
4
Radio Frequency Interference Statement
5.X GHz Statement (FCC/IC)
Continuity of transmission
The Base Transceiver Station (BTS) equipment has been tested and found to comply with the
limits for a class A digital device, pursuant to ETSI EN 301 489-1 rules and Part 15 of the FCC
Rules. These limits are designed to provide reasonable protection against harmful interference
when the equipment is operated in commercial, business and industrial environments. This
equipment generates, uses and can radiate radio frequency energy and, if not installed and
used in accordance with the instruction manual, may cause harmful interference to radio
communications. Operation of this equipment in a residential area is likely to cause harmful
interference in which case the user will be required to correct the interference at the user's own
expense.
This device has been designed to operate with the antennas listed in Antennas Appendix A and
having a maximum gain of 17 dBi for 5.1 & 5.8GHz bands. Antennas not included in this list or
having a gain greater than 17 dBi are strictly prohibited.
To reduce potential radio interference to other users, the antenna type and its gain should be
so chosen that the Equivalent Isotropically Radiated Power (EIRP) is not more than that
permitted for successful communication.
Not withstand the above, operation in 5.XGHz Bands is subject to local and regional
regulations which may include but may not be limited to:
x Sub-band to operate
x Allowed Tx Power
x Actual channel bandwidth
x Allowed EIRP
This device has several alarms that should avoid operational failure.
The Algorithm is interrupt by alarms and react as needed:
x Over Temperature (Basic card, Digital card, Adaptor card) will shutdown the RF
channels for 30 min and then will start RF Channels again.
x 2 x BB PLL-Lock one for each RFic, will shutdown the RF channels and try to lock The
PLL, after fails it will reboot the unit.
x 2 x RF TX/Rx PLL-Lock one for each RFic, will shutdown the RF channels and try to
lock The PLL, after fails it will reboot the unit.
In case of absence of information to transmit the unit will transmit only the necessary control
or signaling that digital transmission allowed.
Page 5
BreezeCOMPACT System Manual
Chapter 1: System
Description
5
Radio Frequency Interference Statement
FCC and Industry Canada Radiation Hazard Warning
Industry Canada Statement
This device complies with FCC Rules Part 15 and with Industry Canada licence-exempt RSS
standard(s). Operation is subject to two conditions: (1) This device may not cause harmful
interference, and (2) this device must accept any interference that may be received or that may
cause undesired operation.
Canada: Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux
appareils radio exempts de licence. L'exploitation est autorisée aux deux conditions suivantes :
(1) l'appareil ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit accepter
tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en compromettre le
fonctionnement.
NOTE: 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 Class B digital apparatus complies with Canadian ICES-003.
Cet appareil numerique de la classe B est conforme a la norme NMB-003 du Canada.
Frequency Stability
BreezeU100 & Comact1000 are based on OCXO oscillator with Max frequency stability of
200PPb, The OCXO is a 40 MHz device which feeds the RF component
The 40MHz OCXO is a standalone discrete part, while the other VCO’s are incorporated in the
RF component. The Oscillator and VCO’s are used in conjunction with a phase lock circuit on
the RF component in order to generate stable clocks and RF signals.
To comply with Industry Canada exposure requirements, and FCC RF exposure requirements
in Section 1.1307 and 2.1091 of the FCC Rules, the antenna used for this transmitter must be
fixed-mounted on outdoor permanent structures with a separation distance of at least 425 cm
from all persons.
Pour se conformer aux exigences d’exposition d'Industrie Canada, et aux exigences FCC dans
les sections 1,1307 et 2,1091 de la réglementation FCC, l'antenne utilisée pour cet émetteur
doit être montée d’une manière fixe sur des structures permanentes de plein air avec une
distance de séparation d'au moins 425 cm de toutes personnes.
Users can obtain Canadian information on RF exposure and compliance from the Canadian
Representative:
Nick Dewar
Page 6
BreezeCOMPACT System Manual
Chapter 1: System
Description
6
Canadian Radio Standards Specifications (RSS) Compliance Statement
R&TTE Compliance Statement
Safety Considerations – General
Grounding
Nick.Dewar@Telrad.com
This device has been designed to operate with the antennas listed in “Antennas” on page 28,
and having a maximum gain of 18 dBi. Antennas not included in this list or having a gain
greater than 18 dBi are strictly prohibited for High-density areas of use with this device. Lowdensity areas can use a higher-gain Antenna.
To reduce potential radio interference to other users, the antenna type and its gain should be
so chosen that the Equivalent Isotropically Radiated Power (EIRP) is not more than that
permitted for successful communication.
This equipment complies with the appropriate essential requirements of Article 3 of the
R&TTE Directive 1999/5/EC.
For the following safety considerations, “Instrument” means the BreezeCOMPACT units'
components and their cables.
The BTS chassis is required to be bonded to protective grounding using the bonding stud or
screw provided with each unit.
Page 7
BreezeCOMPACT System Manual
Chapter 1: System
Description
7
Safety Considerations – DC-powered Equipment
CAUTION ATTENTION
Risk of electric shock and energy hazard.
Risque de décharge électrique et
d'electrocution.
Restricted Access Area: The DC-powered
equipment should only be installed in a
Restricted Access Area.
Zone d’Accès Limité: L’alimentation en
dans une zone a accès limité
Installation Codes: The equipment must
Electrical Code.
Normes d’installation: les équipements
d’après les normes
électriques nationales US et les normes
Overcurrent Protection: A readily
overcurrent protective device, rated 10A,
wiring.
Protection de ssurintensité: Une
CAUTION: This equipment is designed
instructions.
ATTENTION: Cet équipement est
terre entre le courant continu et le reste
The equipment must be
electrode conductor.
L’appareil doit être connecté a
Caution
Line Voltage
courant continue doit être installée
be installed according to the latest
edition of the country’s national
electrical codes. For North America,
equipment must be installed in
accordance with the US National
Electrical Code and the Canadian
accessible Listed branch circuit
must be incorporated in the building
to permit connection between the
earthed conductor of the DC supply
circuit and the grounding conductor at
the equipment. See installation
connected directly to the DC
Supply System grounding
electrode conductor.
All equipment in the immediate
vicinity must be grounded in
the same way, and not be
grounded elsewhere.
The DC supply system is to be
local, meaning within the same
premises as the equipment.
There shall be no disconnect
device between the grounded
circuit conductor of the DC
source (return) and the point of
connection of the grounding
doivent être installes d’après les
dernières normes en vigueur. Pour
l’Amérique du nord les équipements
doivent être installés
électriques Canadiennes.
protection de surintensité de 10A doit
être installée sur le circuit
d’alimentation.
prévu pour permettre une mise a la
de l’installation. Voir les instructions
d’installation.
la terre de l’allimentation en
courant continu.
Tout appareil dans la proximité
immédiate doit être connecté a
la terre de la même manière et
pas autrement.
L’alimentation du système en
courant continu doit être local
et remplir les mêmes
conditions que le matériel.
Le circuit de terre doit être
ininterrompu entre la source et
les différents appareils.
To avoid electrical shock, do not perform any servicing unless you are qualified to do so.
Pour éviter tout choque électrique ne pas intervenir sur les circuits électriques si vous n’êtes
pas qualifié pour.
Before connecting this instrument to the power line, make sure that the voltage of the power
source matches the requirements of the instrument.
Page 8
BreezeCOMPACT System Manual
Chapter 1: System
Description
8
Laser
CLASS 1 LASER PRODUCT
The system can be equipped with
Class 1 laser products, which comply
with IEC 60825-1, IEC 60825-
2 and a
UL recognized laser or CDRH CFR
Title 21, part 1040.
The system does not emit hazardous
light, and the beam is totally enclosed
during normal operation, as long as
the equipment is operated in
accordance with the applicable s
afety
instructions.
APPAREIL A` LASER DE CLASSE 1
Classe du Laser
Le système peut être équipe d’un laser
de classe 1 selon la norme IEC 60825-
1,
IEC 60825-2 et reconnu comme UL laser
ou CDRH CFR titre 21, partie 1040.
Le système n’émet pas de lumière
apparente et le rayon est entièrement
protégé pendant l’utilisation normal du
système par l’utilisateur tant que les
appareils sont utilisés en suivant les
instructions de sécurité.
Laser Safety Statutory Warning
Précautions de sécurité réglementaire pour laser
Radio
Outdoor Units and Antennas Installation and Grounding
All personnel involved in equipment installation, operation and maintenance must be aware
that laser radiation is invisible. Therefore, although protective devices generally prevent direct
exposure to the beam, personnel must strictly observe the applicable safety precautions, and in
particular, must avoid staring into optical connectors, either directly or using optical
instruments.
Remember that observing safety precautions is not a matter of personal choice; ignoring safety
puts all people within the line-of-sight in danger.
Tout personnel impliqué dans l’installation, le fonctionnement et la maintenance de
l’installation doivent savoir que les radiations laser sont invisibles. Donc, bien que
généralement les protections évitent tout contact direct avec les rayons émis, le personnel doit
observer strictement les précautions de sécurité et en particulier, les connecteurs optiques,
aussi bien directement ou avec des instruments d’optique.
Souvenez vous que remplir les précautions de sécurité n’est en aucun cas un choix personnel;
ignorer les règles de sécurité mets toutes les personnes en présence en danger.
The instrument transmits radio energy during normal operation. To avoid possible harmful
exposure to this energy, do not stand or work for extended periods of time in front of its
antenna. The long-term characteristics or the possible physiological effects of radio frequency
electromagnetic fields have not yet been fully investigated.
The BreezeCOMPACT 1000 and BreezeU100 require installation by a CPI (Certified
Professional Installer)
Page 9
BreezeCOMPACT System Manual
Chapter 1: System
Description
9
General Notes – 5GHz Devices Operation
USA CBRS Band Category B device
All CBSDs
Category B Devices
x Geographic location
x Sensing capability (if supported)
x Limited to Outdoor operation
Ensure that outdoor units, antennas and supporting structures are properly installed to
eliminate any physical hazard to either people or property. Make sure that the installation of
the outdoor unit, antenna and cables is performed in accordance with all relevant national and
local building and safety codes. Even where grounding is not mandatory according to
applicable regulation and national codes, it is highly recommended to ensure that the outdoor
unit and the antenna mast are grounded and suitable lightning protection devices are used so
as to provide protection against voltage surges and static charges. In any event, Telrad
Networks is not liable for any injury, damage or regulation violations associated with or caused
by installation, grounding or lightning protection.
(1) The equipment is targeted to be installed by professional installers and to be
purchased from authorized dealers only.
(2) The device is to be used for industrial/commercial use and not private use.
(3) The device has its own Management Tool and Licensing Software that is unique and
cannot be operated by an average consumer as such it must be configured by a
professional installer
(4) Requirements for professional installers:
- Installation must be controlled.
- Installed by licensed professionals
- Installation requires special training by Telrad
The BreezeCOMPACT 1000 requires installation by a CPI (Certified Professional Installer) as
defined in Section 96.39 and 96.45 of FCC part 96 requirements. The Compact is Classified as
a Category B CBSD which requires the following info be recorded and uploaded as part of the
CPI process per section 96.45
x Antenna height AGL (m)
x CBSD class (Category A or B)
x Requested authorization status (PAL or GAA)
x FCC ID
x Call sign (PALs only)
x User contact info
x Air interference technology
x Serial #
The BreezeCompact 1000 (Category B CBSD) must report to a SAS to register and obtain
spectrum grants per FCC part 96. Local administration should be executed through the
domain proxy and all freq, bandwidth and power adjustments must be handled in coordination
with the SAS and grant process. Once band 48 CBRS license has been added to the system the
CBSD will require a grant from the SAS to automatically modify TX on/off, Frequency,
bandwidth and power. Location info will be reported to the SAS by means of GPS
synchronization.
x Antenna gain
9
x Antenna Beam-width
x Antenna Azimuth
x Antenna Down tile angle
Page 10
BreezeCOMPACT System Manual
Chapter 1: System
Description
10
Page 11
BreezeCOMPACT System Manual
Chapter 1: System
Description
11
Transmitter Antenna
Disposal of Electronic and Electrical Waste
Disposal of Electronic and Electrical Waste
Under Industry Canada regulations, this radio transmitter may only operate using an antenna
of a type and maximum (or lesser) gain approved for the transmitter by Industry Canada. To
reduce potential radio interference to other users, the antenna type and its gain should be so
chosen that the equivalent isotropically radiated power (EIRP) is not more than that necessary
for successful communication.
Conformément à la réglementation d'Industrie Canada, le présent émetteur radio peut
fonctionner avec une antenne d'un type et d'un gain maximal (ou inférieur) approuvé pour
l'émetteur par Industrie Canada. Dans le but de réduire les risques de brouillage
radioélectrique à l'intention des autres utilisateurs, il faut choisir le type d'antenne et son gain
de sorte que la puissance isotrope rayonnée équivalente (p.i.r.e.) ne dépasse pas l'intensité
nécessaire à l'établissement d'une communication satisfaisante.
This radio transmitter IC:899A-COMPACT3X has been approved by Industry Canada to
operate with the antenna types listed in Section 1.4.7 below with the maximum permissible
gain and required antenna impedance for each antenna type indicated. Antenna types not
included in this list, having a gain greater than the maximum gain indicated for that type, are
strictly prohibited for use with this device.
Le présent émetteur radio IC:899A-COMPACT3X a été approuvé par Industrie Canada pour
fonctionner avec les types d'antenne énumérés dans la Section 1.4.7 ci-dessous et ayant un gain
admissible maximal et l'impédance requise pour chaque type d'antenne. Les types d'antenne
non inclus dans cette liste, ou dont le gain est supérieur au gain maximal indiqué, sont
strictement interdits pour l'exploitation de l'émetteur.
Pursuant to the WEEE EU Directive, electronic and electrical waste must not be
disposed of with unsorted waste. Please contact your local recycling authority for
disposal of this product.
Page 12
BreezeCOMPACT System Manual
Chapter 1: System
Description
12
Important Notice
This manual is delivered subject to the following conditions and restrictions:
This manual contains proprietary information belonging to Telrad Networks Ltd.
No part of its contents may be used for any other purpose, disclosed to any
The text and graphics are for the purpose of illustration and reference only. The
The software described in this document is furnished under a license. The
Information in this document is subject to change without notice. Corporate and
Telrad Networks reserves the right to alter the equipment specifications and
The information contained herein is merely descriptive in nature, and does not
Any changes or modifications of equipment, including opening of the equipment
Some of the equipment provided by Telrad Networks and specified in this
Such information is supplied solely for the purpose of assisting properly
authorized users of the respective Telrad Networks products.
person or firm or reproduced by any means, electronic and mechanical, without
the express prior written permission of Telrad Networks Ltd.
specifications on which they are based are subject to change without notice.
software may be used or copied only in accordance with the terms of that license.
individual names and data used in examples herein are fictitious unless
otherwise noted.
descriptions in this publication without prior notice. No part of this publication
shall be deemed to be part of any contract or warranty unless specifically
incorporated by reference into such contract or warranty.
constitute an offer for the sale of the product described herein.
not expressly approved by Telrad Networks Ltd., will void equipment warranty
and any repair thereafter shall be charged for. It may also void the user's
authority to operate the equipment.
manual is manufactured and warranted by third parties. All such equipment
must be installed and handled in full compliance with the instructions provided
by such manufacturers as attached to this manual or provided thereafter by
Telrad Networks or the manufacturers. Non-compliance with such instructions
may result in serious damage and/or bodily harm and/or void the user's authority
to operate the equipment and/or revoke the warranty provided by such
manufacturer.
Page 13
BreezeCOMPACT System Manual
13
Chapter 1: System
Description
About This Manual
Chapter 1: System Description,
Chapter 2: Commissioning Steps,
Chapter 3: Operation and Administration Procedures,
Chapter 4: Events and Alarms,
Chapter 5: Licensing Mechanism,
This manual describes the BreezeCOMPACT solution, and details how to install, operate and
manage the BTS equipment.
This manual is intended for technicians responsible for installing, setting and operating the
BreezeCOMPACT BTS equipment, and for system administrators responsible for managing
the system.
In Release 6.8, BreezeCOMPACT1000 introduce new hardware including BreezeWAY1010
EPC (embedded EPC), for the additional EPC configuration please refer to BreezeWAY EPC
user manual.
This manual contains the following chapters:
BreezeCOMPACT for provisioning.
configure the BreezeCOMPACT and perform various types of software upgrades.
alarms in the system.
alarms in the system.
page 23, describes the BreezeCOMPACT system.
page 48, describes how to commission the
page 54, describes how to
page 132, describes how to handle events and
page 140, describes how to handle events and
Page 14
BreezeCOMPACT System Manual
Chapter 1: System
ption
14
C
Contents
.................................................. 23
1.1 LTE .......................................................................................................................... 24
1.2 Telrad LTE End-to-End Solution ............................................................................. 25
1.3 BreezeCOMPACT Family ........................................................................................ 26
1.4 BreezeCOMPACT Product Types per Frequency ..................................................... 30
1.5 BreezeCOMPACT Features ..................................................................................... 31
1.6 BreezeCOMPACT R7.2 Software Capabilities ......................................................... 40
1.7 BreezeCOMPACT Accessories and Specifications .................................................... 43
............................................... 48
2.1 BreezeCOMPACT Commissioning ........................................................................... 48
................. 54
3.1 Configuration commit procedure .............................................................................. 54
3.2 CLI User – Radius Authentication ........................................................................... 55
Descri
Chapter 1: System Description
1.1.1 Introduction to LTE ......................................................................................... 24
1.1.2 E-UTRAN Architecture ................................................................................... 24
1.3.1 BreezeCOMPACT 1000 – Small Cell, High Performance, Superior No-Line-
of-Sight ............................................................................................................. 27
1.3.2 BreezeCOMPACT 2000 – Coverage and Capacity ......................................... 27
1.3.3 BreezeCOMPACT 3000 – Unmatched Performance ...................................... 28
1.3.4 BreezeU100 (5.XGHz only) .............................................................................. 29
1.5.1 BreezeCOMPACT Topologies .......................................................................... 31
1.5.2 BreezeCOMPACT TDD Configuration ........................................................... 34
1.5.3 BreezeCOMPACT QoS .................................................................................... 35
1.5.4 BreezeCOMPACT Equal Time/Equal Rate Scheduler ................................... 36
1.5.5 Equal Rate Scheduling .................................................................................... 37
1.5.6 Multiple PLMN IDs ......................................................................................... 38
1.5.7 EPC Redundancy and Load Balancing (Cluster) ........................................... 38
1.5.8 Spectrum analyzer ........................................................................................... 39
1.5.9 GPS ................................................................................................................... 39
1.7.1 Antennas .......................................................................................................... 43
1.7.2 SFP (Fiber) ....................................................................................................... 43
1.7.3 Modem and Radio ............................................................................................ 43
1.7.4 Data Communication (Ethernet Interfaces) ................................................... 44
1.7.5 GPS Receiver Specifications ............................................................................ 44
1.7.6 Configuration and Management ..................................................................... 44
1.7.7 Standards Compliance, General ..................................................................... 45
1.7.8 Environmental ................................................................................................. 45
1.7.9 Mechanical and Electrical ............................................................................... 45
Chapter 2: Commissioning Steps
2.1.1 Preface .............................................................................................................. 48
2.1.2 Purpose ............................................................................................................. 50
2.1.3 BreezeCOMPACT Commissioning Procedure ................................................ 50
Chapter 3: Operation and Administration Procedures
Page 15
BreezeCOMPACT System Manual
Chapter 1: System
Description
15
3.3 BreezeCOMPACT Full Configuration via CLI ......................................................... 56
3.4 Software Upgrade Via SSH ...................................................................................... 93
3.5 Software Upgrade Via BreezeVIEW ........................................................................ 96
3.6 Resetting BreezeCOMPACT to Its Factory Defaults ............................................... 103
3.7 Provisioning BreezeCOMPACT Using a Template ................................................. 105
3.8 Locking and Unlocking a Device ............................................................................. 109
3.9 Rebooting BreezeCOMPACT from BreezeVIEW ..................................................... 110
3.10 Spectrum Analyzer ................................................................................................. 112
3.11 Performance Monitoring ......................................................................................... 120
................................................. 132
4.1 Alarm Introduction ................................................................................................. 132
4.2 Alarm Severities ..................................................................................................... 132
4.3 Handling Alarms and Events Using the CLI .......................................................... 133
4.4 Handling Alarms and Events Using BreezeVIEW .................................................. 134
4.5 BreezeCOMPACT – System Events ........................................................................ 135
4.6 BreezeCOMPACT – Alarms .................................................................................... 136
............................................. 140
5.1 Licensing introduction ............................................................................................ 140
5.2 Licensing Prerequisites ........................................................................................... 140
5.3 BreezeVIEW License related Functionality ............................................................ 141
3
3.3.1 Purpose ............................................................................................................. 56
3.3.2 Full Configuration via CLI Procedure ............................................................ 56
3.3.3 Stop/Start all RH ports transmitting from BreezeVIEW CLI ....................... 86
3.3.4 Enhanced log collection ................................................................................... 87
3.3.5 Configuration of backup & restore to external TFTP .................................... 87
3.3.6 Configuring Via BreezeVIEW ......................................................................... 88
3.4.1 Purpose ............................................................................................................. 93
3.4.2 Procedure ......................................................................................................... 93
3.5.1 Purpose ............................................................................................................. 96
3.5.2 Procedure ......................................................................................................... 96
3.6.1 Purpose ........................................................................................................... 103
3.6.2 Procedure ....................................................................................................... 103
3.7.1 Purpose ........................................................................................................... 105
3.7.2 Procedure ....................................................................................................... 105
3.8.1 Purpose ........................................................................................................... 109
3.8.2 Procedure ....................................................................................................... 109
3.9.1 Purpose ........................................................................................................... 110
3.9.2 Procedure ....................................................................................................... 111
3.10.1 Spectrum Analyzer Collection ....................................................................... 112
3.10.2 Spectrum Analyzer Range Frequency Scanning .......................................... 115
3.11.1 Purpose ........................................................................................................... 120
3.11.2 Procedure ....................................................................................................... 120
3.11.3 Performance KPIs Description ...................................................................... 127
Chapter 4: Events and Alarms
Chapter 5: Licensing Mechanism
5.3.1 License Distribution to HW ........................................................................... 141
Page 16
BreezeCOMPACT System Manual
Chapter 1: System
Description
16
5.4 CLI License Operations .......................................................................................... 146
................................................... 149
A.1 5.x GHz Antennas ................................................................................................... 149
5.3.2 License Status View per Single HW ............................................................. 142
5.3.3 License inventory Display per network ........................................................ 144
5.3.4 License Related Alarms ................................................................................. 146
5
5.4.1 TFTP server verification/configuration......................................................... 146
5.4.2 Showing license status of an LTE device ...................................................... 146
5.4.3 Loading LTE license via CLI ......................................................................... 147
Appendix A: 5GHz Antennas
Page 17
BreezeCOMPACT System Manual
Chapter 1: System
Description
17
List of Figures
L
Figure 1: E-UTRAN Architecture ....................................................................................................................... 24
Figure 2: Telrad LTE End-to-End Solution Using BreezeWAY 2020 ............................................................... 25
Figure 3: LTE End-to-End Solution Using Embedded EPC in BreezeCOMPACT1000 ................................... 25
Figure 4: BreezeCOMPACT 1000 – Small Cell, High Performance .................................................................. 27
Figure 5: BreezeCOMPACT 2000 – Coverage and Capacity ............................................................................. 27
Figure 6: BreezeCOMPACT 3000 – Unmatched Performance .......................................................................... 28
Figure 6: BreezeU100 – LTE-U .......................................................................................................................... 29
Figure 7: Single Sector Topology......................................................................................................................... 31
Figure 7: MU-MIMO Operation .......................................................................................................................... 32
Figure 8: Split Mode 2x2 Topology ..................................................................................................................... 32
Figure 9: Dual Sector 2x2 Topology .................................................................................................................... 33
Figure 10: Dual Carrier 2x2 Topology towards the same geographical sector ................................................. 33
Figure 11: Dual Carrier Aggregation 2x2 Topology towards the same geographical sector ............................ 34
Figure 12: TDD Configurations .......................................................................................................................... 34
Figure 13: Subframe Types ................................................................................................................................. 35
Figure 14: QCI Types .......................................................................................................................................... 36
Figure 15: Equal Rate Scheduling ...................................................................................................................... 37
Figure 16: Equal Time Scheduling ..................................................................................................................... 37
Figure 17: EPC Redundancy and Load Balancing ............................................................................................. 38
Figure 18: GPS Chaining .................................................................................................................................... 39
Figure 19: SAS Server Setting Screen ................................................................................................................ 48
Figure 20: CBSD Screens .................................................................................................................................... 49
Figure 21: CLI User – Radius Authentication ................................................................................................... 55
Figure 22: Deployment Tab in BreezeVIEW ...................................................................................................... 57
Figure 23: BREEZEVIEW -ENB deployment tab when setting deployment topology as Default topology .... 58
Figure 24: BREEZEVIEW -ENB Advanced RAN tab when setting deployment topology as Default ............. 58
Figure 25: BREEZEVIEW -ENB Antenna's status in single carrier 4Rx/2Tx .................................................. 60
Figure 26: BREEZEVIEW -ENB deployment tab in single carrier 4Rx/2Tx .................................................... 60
Figure 27: BREEZEVIEW -ENB Antenna's status in single carrier 4Rx/4Tx .................................................. 61
Figure 28: BREEZEVIEW -ENB deployment tab in single carrier 4Rx/4Tx .................................................... 61
Figure 27: BREEZEVIEW -ENB Antenna's status in single carrier 4Rx/4Tx DL MU-MIMO ........................ 62
Figure 28: BREEZEVIEW -ENB deployment tab in single carrier 4Rx/4Tx DL MU-MIMO .......................... 63
Figure 29: BREEZEVIEW -ENB Antenna's status in SplitMode2x2................................................................ 64
Figure 30: BREEZEVIEW -ENB deployment tab when in SplitMode2x2 ........................................................ 64
Figure 31: BREEZEVIEW -ENB Antenna's status in SplitModef1f2 ............................................................... 66
Figure 32: BREEZEVIEW -ENB deployment tab when in SplitModef1f2 ....................................................... 66
Figure 33: BREEZEVIEW -ENB CELL0 deployment tab when in SplitModef1f2........................................... 66
Figure 34: BREEZEVIEW -ENB Antenna's status in DualCarrier .................................................................. 67
Figure 35: BREEZEVIEW -ENB deployment tab when in DualCarrier .......................................................... 68
Figure 36: BREEZEVIEW -ENB CELL0 deployment tab when in DualCarrier.............................................. 68
Figure 37: BREEZEVIEW -ENB CELL1 deployment tab when in DualCarrier.............................................. 68
Figure 38: BREEZEVIEW -ENB Antenna's status in DualCarrierAggregation .............................................. 70
Figure 39: BREEZEVIEW -ENB deployment tab when in DualCarrierAggregation ...................................... 70
Figure 40: BREEZEVIEW -ENB CELL0 deployment tab when in DualCarrierAggregation ......................... 70
Figure 41: BREEZEVIEW -ENB CELL1 deployment tab when in DualCarrierAggregation ......................... 70
Figure 42: Physical ports configuration in BREEZEVIEW ............................................................................... 75
Figure 43: Handover A5 Events .......................................................................................................................... 83
Figure 44: Handover A3 Events .......................................................................................................................... 84
Figure 45: Device Information ............................................................................................................................ 88
Figure 46: Device Capability ............................................................................................................................... 89
Figure 47: Device Capability ............................................................................................................................... 89
Page 18
BreezeCOMPACT System Manual
Chapter 1: System
Description
18
Figure 48: Device Networking Information ........................................................................................................ 89
Figure 49: External Management Interface − 1 ................................................................................................. 89
Figure 50: External Management Interface − 2 ................................................................................................. 90
Figure 51: Cell Configuration ............................................................................................................................. 90
Figure 52: Handover Configuration –A5 ............................................................................................................ 90
Figure 53: Handover Configuration –A3 ............................................................................................................ 91
Figure 54: Neighbor Cells List Configuration .................................................................................................... 91
Figure 55: QoS Configuration − 1 ....................................................................................................................... 92
Figure 56: Timing Configuration ........................................................................................................................ 92
Figure57: Confirm Save ...................................................................................................................................... 92
Figure 58: Actions Menu − Reset to Factory Defaults ....................................................................................... 93
Figure 59: Reset Device ....................................................................................................................................... 93
Figure 60: TFTP Server IP Address ................................................................................................................... 97
Figure 61: Actions Menu – Load SW File To Backup ........................................................................................ 97
Figure 62: Load SW File to Backup Main Window ............................................................................................ 98
Figure 63: Warning − Load to Backup ................................................................................................................ 98
Figure 64: Ongoing Task − Load to Backup SW Version ................................................................................... 98
Figure 65: Ongoing Task − Successful ................................................................................................................ 99
Figure 66: Device Details Window – Backup SW Version ................................................................................. 99
Figure 67: SW Upgrade Menu – Run SW From Backup ................................................................................... 99
Figure 68: Run SW from Backup Window .......................................................................................................... 99
Figure 69: Warning − Run SW from Backup .................................................................................................... 100
Figure 70: Ongoing Task − Run SW from Backup − In Process ...................................................................... 100
Figure 71: Ongoing Task − Run SW from Backup − Success .......................................................................... 100
Figure 72: Device Details Window − Backup Software Version is Active ....................................................... 101
Figure 73: SW Upgrade Menu – Make Backup File As Main ......................................................................... 101
Figure 74: Make Backup Software As Main Window ...................................................................................... 101
Figure 75: Warning – Make Backup SW as Main ............................................................................................ 102
Figure 76: Warning − Make Backup SW as Main − Success ........................................................................... 102
Figure 77: Main SW Version Activated ............................................................................................................ 102
Figure 78: System Events Window ................................................................................................................... 103
Figure 79: Set Factory Defaults ........................................................................................................................ 104
Figure 80: Warning – Set Factory Defaults ..................................................................................................... 104
Figure 81: Management Status – Unreachable ............................................................................................... 105
Figure 82: Selecting a Template ....................................................................................................................... 106
Figure 83: New Template .................................................................................................................................. 106
Figure 84: Template Details Window − 1 ......................................................................................................... 106
Figure 85: Templates Window .......................................................................................................................... 106
Figure 86: Template Details Window − 2 ......................................................................................................... 107
Figure 87: Apply From Template – Device Details Window............................................................................ 107
Figure 88: Apply From Template – New Devices Area of Home Page ............................................................ 108
Figure 89: Apply a Template Window .............................................................................................................. 108
Figure 90: Locking a Device .............................................................................................................................. 109
Figure 91: Locked Device .................................................................................................................................. 109
Figure 92: Unlock & Sync From Device ............................................................................................................ 110
Figure 93: Reboot ............................................................................................................................................... 111
Figure 94: Warning − Reset .............................................................................................................................. 111
Figure 95: Device Details − Unreachable Management Status ...................................................................... 112
Figure 96: Device Details − Managed Management Status ............................................................................ 112
Figure 97: System Events Window − Reset ...................................................................................................... 112
Figure 98: BREEZEVIEW -ENB Spectrum Analyzer Collection All Antennas ............................................. 114
Figure 99: BREEZEVIEW -ENB Spectrum Analyzer Collection 1 Antenna .................................................. 115
Figure 100: BREEZEVIEW -ENB Spectrum Analyzer Range Frequency Scanning page ............................. 119
Page 19
BreezeCOMPACT System Manual
Chapter 1: System
Description
19
List of Tables
Figure 101: BREEZEVIEW – Spectrum Analyzer Disable .............................................................................. 119
Figure 102: Accessing the KPI – Device Details Window ................................................................................ 120
Figure 103: Accessing the KPI – Devices Window ........................................................................................... 121
Figure 104: eNodeB Device Performance View ................................................................................................ 121
Figure 105: Basic KPIs ...................................................................................................................................... 121
Figure 106: Device Performance View Toolbar ................................................................................................ 122
Figure 107: Legend ............................................................................................................................................ 122
Figure 108: Air Link Utilization Graph............................................................................................................ 123
Figure 109: Registered and Active UEs Graph ................................................................................................ 123
Figure 110: Layer 3 Throughput Graph ........................................................................................................... 124
Figure 111: Changing the Time Zoom – Before Releasing the Mouse Button ................................................ 125
Figure 112: Graph View Zoom – After Releasing the Mouse Button .............................................................. 125
Figure113: Export Window ............................................................................................................................... 126
Figure 114: Time Span Selection ...................................................................................................................... 126
Figure 115: From/To Dates ............................................................................................................................... 127
Figure 116: Chart Button .................................................................................................................................. 127
Figure 117: Chart Context Menu ...................................................................................................................... 127
Figure 118: BreezeVIEW – Alarms ................................................................................................................... 134
Figure 119: BreezeVIEW – System Events ...................................................................................................... 135
Figure 120: Devices view with highlighted devices to be licensed .................................................................. 141
Figure 121: Load License File form .................................................................................................................. 141
Figure 122: License loading warning frame ..................................................................................................... 142
Figure 123: Ongoing task view (in this example - with failed license loading operations) ............................ 142
Figure 124: closed left pane without license info ............................................................................................. 143
Figure 125: expanded left pane with license info ............................................................................................. 144
Figure 126: Device licensing controls ............................................................................................................... 145
Figure 127: Device Licensing view.................................................................................................................... 145
Figure 128: Alarms view with 'license' as search criterion .............................................................................. 146
L
Table 0-1: Glossary .............................................................................................................................................. 20
Table 2-2: Telrad Solution per Product Type ..................................................................................................... 26
Table 2-3: BreezeCOMPACT Models .................................................................................................................. 30
Table 2-4: Cell Radius and Special Subframes .................................................................................................. 35
Table 2-5: General Modem and Radio Specifications ......................................................................................... 43
Table 2-6: Data Communication (Ethernet Interfaces) ..................................................................................... 44
Table 2-7: BMAX-4M-GPS and BreezeGPS Receiver, Mechanical and Electrical Specifications .................... 44
Table 2-8: Configuration and Management ........................................................................................................ 44
Table 2-9: Standards Compliance, General ........................................................................................................ 45
Table 2-10: Environmental Specifications .......................................................................................................... 45
Table 2-11: Mechanical and Electrical Specifications, BreezeCOMPACT 1000 Units ..................................... 45
Table 2-12: Mechanical and Electrical Specifications, BreezeCOMPACT 2000 Units ..................................... 47
Table 2-13: Mechanical and Electrical Specifications, BreezeCOMPACT 3000 Units ..................................... 47
Table 2-11: Mechanical and Electrical Specifications, BreezeU100 Unit ......................................................... 47
Table 3-1: SSF Settings ....................................................................................................................................... 78
Table 3-2: SA results table ................................................................................................................................ 118
Table 3-3: Performance KPIs ............................................................................................................................ 127
Table 4-1: BreezeCOMPACT System Events ................................................................................................... 135
Table 4-2: BreezeCOMPACT Alarms ................................................................................................................ 136
Page 20
BreezeCOMPACT System Manual
Chapter 1: System
Description
20
TTable 0--11:: GGlossary
AAcronym
DDescription
3GPP
3rd Generation Partnership Project
AAA
Authentication, Authorization and Accounting
BB
Baseband
BS
Base Station
BTS
Base Transceiver Station
CA
Carrier Aggregation
CAPEX
Capital Expenditure
CLI
Command Line Interface
CPE
Customer Premises Equipment
CQI
Channel Quality Indication
DSCP
Differentiated Services Code Point
DL
Downlink
EARFCN
EUTRA Absolute Radio Frequency Channel Number
ECGI
E-UTRAN Cell Global Identifier
EDT
Electrical Down-Tilt
EIRP
Equivalent Isotopically Radiated Power
eNB
eNodeB
EPC
Evolved Packet Core
EPROM
Erasable Programmable Read-Only Memory
E-UTRAN
Evolved UMTS Terrestrial Radio Access Network
FDD
Frequency Division Duplexing
GBR
Guaranteed Bit Rate
GHz
Gigahertz
GPS
Global Positioning System
HARQ
Hybrid Automatic Repeat Request
HPA
High Power Amplifier
HSS
Home Subscriber Server
IDU
Indoor unit
IEEE
Institute of Electrical and Electronics Engineers
IF
Interface
IP
Internet Protocol
iPCRF
Internal Policy and Charging Rules Function
IPv4
Internet Protocol Version 4
iHSS
Internal Home Subscriber Server
km
Kilometers
LC
Lucent Connector fiber optics
LSB
Least Significant Bit
LTE
Long Term Evolution
LTE-U
LTE in Un-Licensed Bands
MBR
Maximum Bit Rate
MCC
Mobile Country Code
MCS
Modulation and coding scheme
Page 21
BreezeCOMPACT System Manual
Chapter 1: System
Description
21
TTable 0--11:: GGlossary
AAcronym
DDescription
MDT
Mechanical Down-Tilt
MHz
Megahertz
MIMO
Multiple Input and Multiple Output
MME
Mobility Management Entity
MNC
Mobile Network Code
MO
Managed Object
MSB
Most Significant Bit
MTU
Maximum Transmission Unit
MU-MIMO
Multi User MIMO
NMS
Network Management System
Non-GBR
Non-Guaranteed Bit Rate
ODU
Outdoor Unit
OFDM
Orthogonal Frequency Division Multiplexing
OPEX
Operating Expenditure
PA
Power Amplifier
PCI
Physical Cell ID
PER
Packet Error Rate
PGW
Packet Gateway
PHY
Physical Layer
PLL
Phase-Locked Loop
PLMN ID
Public Land Mobile Network Identifier
PN
Part Number
QAM
Quadrature Amplitude Modulation
QCI
QoS Class Identifier
QoS
Quality of Service
QPSK
Quadrature Phase Shift Keying
RACH
Random Access Channel
RB
Resource Block
RH
Radio Head
RNC
Radio Network Controller
RNP
Radio Network Planning
RRC
Radio Resource Control
RRM
Radio Resource Management
Rx
Receiver
SFP
Small Form-Factor Pluggable
SFR
Soft Frequency Reuse
SGW
Serving GateWay
SINR
Signal to Interference plus Noise Ratio
SSF
Special SubFrame
SSH
Secure Shell
SW
Software
TA
Tracking Area
Page 22
BreezeCOMPACT System Manual
Chapter 1: System
Description
22
TTable 0--11:: GGlossary
AAcronym
DDescription
TAC
Tracking Area Code
TAI
Tracking Area Identity
TDD
Time-Division Duplex
TFTP
Trivial File Transfer Protocol
Tx
Transmitter
UE
User Equipment
UE-AMBR
UE Aggregate Maximum Bit Rate
UL
Uplink
VLAN
Virtual Local Area Network
VSWR
Voltage Standing Wave Ratio
WiMAX
Worldwide Interoperability for Microwave Access
Page 23
BreezeCOMPACT System Manual
23
LTE,
Telrad LTE End-to-End Solution,
BreezeCOMPACT Family,
BreezeCOMPACT Product Types per Frequency,
BreezeCOMPACT Features,
BreezeCOMPACT R7.2 Software Capabilities,
BreezeCOMPACT Accessories and Specifications,
Chapter 1: System Description
In This Chapter:
L
on page 24
on page, 25
on page 26
on page 31
on page 30
on page 40
on page 43
Page 24
BreezeCOMPACT System Manual
Chapter 1: System Description
LTE
24
1.1 LTE
1.1.1 Introduction to LTE
1.1.2 E-UTRAN Architecture
Figure 1: E-UTRAN Architecture
Long-Term Evolution (LTE), commonly marketed as 4G LTE, is a wireless communication
standard for high-speed data for mobile phones and data terminals. The standard, which was
developed by the 3rd Generation Partnership Project (3GPP), is specified in its Release 8
document series, with enhancements described in later releases.
The key benefits of LTE include:
Responds to user demand for higher data rates (peak rates) and quality of service
(QoS) that supports up to 20MHz channels in release 8 with Carrier Aggregation
(CA) capabilities supported beginning with release 10
Addresses continued demand for cost reduction (CAPEX and OPEX).
Supports both Frequency Division Duplexing (FDD) and Time-Devision Duplex
(TDD).
IP-based network architecture provides a simpler all-IP architecture that lowers
operating costs.
The LTE radio access network E-UTRAN architecture has been improved from a legacy cellular
radio access (such as 3G) UTRAN network. eNodeB functions in E-UTRAN include not only
legacy base station (NodeB) functions, but also the radio interface and Radio Network
Controllers (RNCs), which include Radio Resource Management (RRM) functions.
Because both WiMAX and E-UTRAN architecture implement a similar approach, it is easier to
migrate WiMAX networks to LTE. For example, Telrad’s BreezeCOMPACT and Dual Mode CPE
solution enables software upgrades from WiMAX to LTE. For more details about WiMAX
migration options, contact Telrad.
Page 25
BreezeCOMPACT System Manual
Chapter 1: System Description
End Solution
25
1.2 Telrad LTE End-to-End Solution
Figure 2: Telrad LTE End-to-End Solution Using BreezeWAY 2020
Figure 3: LTE End-to-End Solution Using Embedded EPC in BreezeCOMPACT1000
Telrad delivers a comprehensive LTE solution that includes BreezeCOMPACT eNB, BreezeWAY
EPC, BreezeRADIUS AAA, CPE Indoor and Outdoor (User Equipment [UE]) and the
BreezeVIEW management system.
Telrad LTE End-to-
Page 26
BreezeCOMPACT System Manual
Chapter 1: System Description
BreezeCOMPACT Family
26
Table 2-2: Telrad Solution per Product Type
Product Type
Product
BS
BreezeCOMPACT 1000, 2000 and 3000
CPE
CPE7000 Outdoor/Indoor, CPE8102 Indoor,
or Third Party
EPC
BreezeWAY2020 EPC, BreezeWAY1010 Embedded EPC in
BreezeCOMPACT1000/BU100 or Third Party (IOT required)
User Provisioning
Internal HSS (BreezeWAY2020) or BreezeRADIUS AAA
(Aradial)
Network Management
BreezeVIEW (BS and EPC) UEs-VIEW (UE)
CPEView TR-069(UE/CPE)
Performance Monitoring
BreezeVIEW
1.3 BreezeCOMPACT Family
BreezeCOMPACT 1000,
BreezeCOMPACT 2000,
BreezeCOMPACT 3000,
BreezeU100,
CPE8000/8100/8101, CPE9000, CPE12000 Outdoor
Telrad’s BreezeCOMPACT family of products includes the following BreezeCOMPACT base
station models:
page 28
page 27
page 27
page 28
The highlights of these products are described in the sections that follow. For more
information, please visit the BreezeCOMPACT section of the Telrad website at
http://www.telrad.com/products/.
Page 27
BreezeCOMPACT System Manual
BreezeCOMPACT Family
27
1.3.1 BreezeCOMPACT 1000 – Small Cell, High
Performance, Superior No-Line-of-Sight
Figure 4: BreezeCOMPACT 1000 – Small Cell, High Performance
1.3.2 BreezeCOMPACT 2000 – Coverage and Capacity
Figure 5: BreezeCOMPACT 2000 – Coverage and Capacity
Chapter 1: System Description
The BreezeCOMPACT 1000 is Telrad’s flagship solution that delivers high performance,
enabling superior connectivity in a small package:
Bands 42, 43 & 48; 3.3–3.5 GHz, 3.4–3.7 GHz, 3.6–3.8 GHz; 30 dBm per port
5.XGHz Band up to 20 dBm per port (subject to local
regulation)BreezeWAY1010 embedded EPC
WiMAX/TD-LTE-Advanced, software-upgradable
Double capacity with dual-sector/carrier
4Tx x 4Rx and modem in a single, all-outdoor form factor
Ultimate alternative to small cells in dense urban areas
Highest capacity using Outdoor CPEs and 4x4 diversity
The BreezeCOMPACT 2000 offers pervasive coverage, enabling triple-play connectivity in areas
with no line of sight, in an all-outdoor single form factor:
(Note: Compact2000 is not supported on R7.0 onwards)
Band 42; 3.5 GHz; 37 dBm per port
WiMAX/TD-LTE-Advanced, software-upgradable
Ideal for urban environments with a mix of CPEs
High power for areas with Non-Line-of-Sight
All-in-one, outdoor Radio 4Rx x 2Tx and Modem
High coverage and capacity for indoor CPEs
Page 28
BreezeCOMPACT System Manual
BreezeCOMPACT Family
28
1.3.3 BreezeCOMPACT 3000 – Unmatched Performance
Figure 6: BreezeCOMPACT 3000 – Unmatched Performance
Chapter 1: System Description
The BreezeCOMPACT 3000 provides high-performance indoor coverage for multiple devices,
such as USB dongles, hotspot units and a wide selection of mobile devices:
4 x 4, 40 dBm (10 Watts) per port
3.3–3.4GHz Band 42; 3.4–3.6GHz, 3.475–3.7 GHz
2.3–2.4
4Tx x 4Rx and modem in a single, all-outdoor form factor
GHz Band 40
; 2.5.–2.7GHz Band 41
WiMAX/TD-LTE-Advanced, software-upgradable
For Fixed, High-mobility and Dense environments
Double capacity with dual-sector/carrier
High power for areas with Non-Line-of-Sight
Highest coverage and capacity using indoor and outdoor CPEs with 4x4 diversity
Page 29
BreezeCOMPACT System Manual
Chapter 1: System Description
BreezeCOMPACT Family
29
1.3.4 BreezeU100 (5.XGHz only)
Figure 7: BreezeU100 – LTE-U
The BreezeU100 provides high-performance outdoor coverage in licensed and un-licensed
5.XGHz Bands for multiple devices.
4 x 4, up to 20 dBm (100 mWatts) per port
5.X GHz Band up to 20dBm per port (subject to local regulations)
4Tx x 4Rx and modem in a single, all-outdoor form factor
TD-LTE-Advanced
For Fixed, Mobility and Dense environments
Embedded Antenna
Embedded EPC1010
Double capacity with dual-sector/carrier
High power for areas with Non-Line-of-Sight
Highest coverage and capacity using outdoor CPEs with 4x4 diversity
(subject to local regulations)
Page 30
BreezeCOMPACT System Manual
BreezeCOMPACT Product Types per Frequency
30
1.4 BreezeCOMPACT Product Types per Frequency
Table 2-3: BreezeCOMPACT Models
Platform
Part NNo.
Telrad Part Number (PN)
Supporte
d SW
Release
Frequencies
Tx
Power
per
Port
(dBm)
Rx/
Tx
Config..
Compact1000e (
BreezeWAY1010)
3.400–3.700 MHz:
Band 48: 3.550-3700*
Compact1000e (
BreezeWAY1010)
Compact1000e (
BreezeWAY1010)
Compact1000
Band 48: 3.550-3700*
Compact1000
Compact1000
Compact2000
Compact3000
Compact3000
Compact3000
Compact3000
Compact3000
Compact1000e (with
BreezeWAY1010)
-L
Compact1000e (with
BreezeWAY1010)
-L
BreezeU100
-L
Chapter 1: System Description
Table 2-3 specifies the BreezeCOMPACT models and their supported frequencies.
Band 42: 3.400–3.600
with
with
with
735470
735472
735473
CMP.XT-BS-3.4-3.7 R7.2
CMP.XT-BS-3.3-3.5 R7.2
CMP.XT-BS-3.6-3.8 R7.2 3.600–3.800 MHz 30 4x4
Band 43: 3.600–3.700
Band 43: 3.700–3.800 is
3.300
3.400–3.700 MHz:
Band 42: 3.400–3.600
735270 CMP.XT-BS-3.4-3.7 R7.2
Band 43: 3.600–3.700
Band 43: 3.700–3.800 is
not supported.
–3.500 MHz
not supported.
30 4x4
30 4x4
30 4x4
735272 CMP.XT-BS-3.3-3.5 R7.2 3.300–3.500 MHz 30 4x4
735273 CMP.XT-BS-3.6-3.8 R7.2 3.600–3.800 MHz 30 4x4
735271 CMP.HP-BS-3.5 R6.9 3.400–3.600 MHz 37 4x2
725270 CMP3000-B41-2496-2690MHz
723270 CMP3000-B40-2300-2400MHz
735370 CMP3000-B42-3400-3600MHz
735373 CMP3000-3300-3400MHz R7.2 3.300-3.400 MHz 40 4x4
735376 CMP3000-3475-3700MHz R7.2 3.475-3.700 MHz 40 4x4
750470
750471
755270
CMP.TX-BS-5.X
CMP.TX-BS-5.X
BreezeU100-5.x-Int.Ant R7.2 5.150-5.900 MHz** 20 4x4
R7.2 2.496–2.690 MHz 40 4x4
R7.2 2.300–2.400 MHz 40 4x4
R7.2 3.400-3.600 MHz 40 4x4
R7.2
R7.2
5.150-5.900 MHz** 20 4x4
4.900-5.350 MHz** 20 4x4
* Requires CBRS License key. Once enabled all freq, bandwidth, TX power require a spectrum grant through
BreezeView Domain proxy which will coordinate with a SAS. Only 10 and 20MHz channels are supported on
CBRS version. Note only 2x2, Dual carrier, Dual Sector and 4RX 2TX are supported under part 96 using Rel
7.0. 4TX modes are planned for rel 7.2
** Exact RF Band, Tx power and channel bandwidth is Subject to local/regional regulation
Page 31
BreezeCOMPACT System Manual
Chapter 1: System Description
BreezeCOMPACT Features
31
1.5 BreezeCOMPACT Features
1.5.1 BreezeCOMPACT Topologies
Single Sector with Single Carrier,
Single Carrier 2Tx2Rx
Single Carrier 2Tx4Rx
Single Carrier 4Tx4Rx
Single Carrier 4Tx4Rx with DL MU-MIMO
Two Geographical Sectors:
Split Mode,
Split Mode 2TX/2Rx F1F1
Split Mode 2TX/2Rx F1F2
Dual Carrier (Sector)
Single Geographical Sector - Dual Carrier:
Dual Carrier,
Dual Carrier Aggregation,
1.5.1.1 Single Sector
Figure 8: Single Sector Topology
The BreezeCOMPACT platform supports 4Tx/4Rx Radio. The following topologies are supported
as can be also configured via the BreezeView “Deployment” Menu:
o
o
o
o
o
o
o
o
page 31
Activation of those various topologies, requires appliance of relevant
software licenses
page 32
, page 33
page 33
page 33
1.5.1.1.1.1 Single Sector 2x2 and 4x4
The Single Sector topology covers one geographic area. It can achieve up to 50% improved
coverage/capacity on both the downlink (DL) and the uplink (UL) (vs 2x2) due to better diversity
and power to the UE. Single Sector supports 2Tx/2Rx, 4Tx/2Rx and 4Tx/4RX.
Page 32
BreezeCOMPACT System Manual
Chapter 1: System Description
BreezeCOMPACT Features
32
Figure 9: MU-MIMO Operation
1.5.1.2 Two Geographical Sectors:
1.5.1.2.1 Split Mode 2x2
Figure 10: Split Mode 2x2 Topology
Handover is not supported in Split mode.
1.5.1.1.1.2 Single Sector 4x4 with MU-MIMO
Downlink Multi-User MIMO (MU-MIMO) topology is supported for higher sector throughput
with enhanced spectral efficiency optimized for fixed wireless. This mode of operation is
supported in single sector with Compact’s configuration to be used is 4Tx/4Rx.
This topology covers two geographic sectors / areas, where the split mode is ideal for small areas
with a low number of subscribers, each geographical sector can be configured in the same
frequency F1F1 or different frequency F1F2.
The Single Carrier Using Split Mode topology enables deployment on a single BreezeCOMPACT
unit to cover two geographic areas. In this mode, single carrier bandwidth (for example,
20/10MHz) is used. The capacity of the single carrier is shared over both the geographic areas.
There are two options for Split mode:
Split Mode default mode - using the same frequency for the two 2x2 sectors where
the two antennas are back to back
Split Mode f1f2 - Using different frequency for each 2x2 sector
The capacity of single carrier (5, 10, 14, 15, 20 MHz) is shared between the two sectors in both
cases.
Page 33
BreezeCOMPACT System Manual
Chapter 1: System Description
BreezeCOMPACT Features
33
1.5.1.2.2 Dual Carrier (Sector) 2x2
This feature is available for 5+5, 10+10, 14+14, 15+15, 20+20 MHz .
Figure 11: Dual Sector 2x2 Topology
1.5.1.3 Single Geographical Sector using Dual Carrier 2x2
1.5.1.3.1 Dual Carrier 2x2
This feature is available for 5+5, 10+10, 14+14, 15+15, 20+20 MHz.
Figure 12: Dual Carrier 2x2 Topology towards the same geographical sector
1.5.1.3.2 Dual Carrier Aggregation (Downlink)
The Dual Sector topology enables a double-capacity BreezeCOMPACT. In this mode, the
BreezeCOMPACT behaves like two 2x2 eNodeB’s (double capacity vs split mode). UEs on
different geographical sectors see different eNodeB’s on different carriers. Each carrier can use
any center frequency within the product’s frequency range. For example, the
BreezeCOMPACT 1000 supports 3.4–3.7 GHz. The operator can configure one carrier for
3.405 GHz and another for 3.695 GHz. This capability enables two 5MHz carriers or two 10 Hz
carriers.
The Dual Carrier topology enables a double-capacity BreezeCOMPACT. In this mode, the
BreezeCOMPACT behaves like two 2x2 eNodeB’s towards the same geographical sectors at two
different frequencies (double capacity vs single carrier).
UEs on different carriers see different eNodeB’s on different carriers. Each carrier can use any
center frequency within the product’s frequency range (but not the same frequency). For
example, the BreezeCOMPACT 1000 supports 3.4–3.7 GHz. The operator can configure one
carrier for 3.405 GHz and another for 3.695 GHz. This capability enables two 5MHz carriers or
two 10 Hz carriers.
In a case of a Compact with a Dual Carrier configuration (two carries with two different
frequencies within the same geographical sector). The Carrier Aggregation capability is
supported with selective CPE’s. The Carrier Aggregation enables optimizing Sector performance
with increased throughput per user by aggregating two radio channels in the Downlink for the
same CPE.
Page 34
BreezeCOMPACT System Manual
BreezeCOMPACT Features
34
Figure 13: Dual Carrier Aggregation 2x2 Topology towards the same geographical sector
1.5.1.3.3 Load Balancing
1.5.2 BreezeCOMPACT TDD Configuration
1.5.2.1 LTE TDD Configuration
Figure 14: TDD Configurations
Note: In Release R7.0, configurations 0, 1 and 2 are supported (Configuration 0
is demo mode)
Chapter 1: System Description
In a case of a Compact with a Dual Carrier configuration or with Dual Carrier Aggregation
configuration (two carries towards the same geographical sector) the Load Balancing capability
enables balance users per each carrier to eliminate un balanced user count per a specific carrier.
This feature is enabled by the BreezeView towards the CPE.
LTE supports various TDD configurations, which define the ratio between the DL and the UL.
The LTE frame comprises 10 subframes, each of which is one millisecond long. The special
subframes (marked in yellow in Figure 14) function as transition frames between the DL and
the UL.
Page 35
BreezeCOMPACT System Manual
Chapter 1: System Description
eezeCOMPACT Features
35
1.5.2.2 LTE TDD Special Subframe Configuration
Figure 15: Subframe Types
Table 2-4: Cell Radius and Special Subframes
Cell Radius (Km)
SpecialSubframeCfg
Maximum SSupported RRange
R <= 10
0 to 3, 7
10 km
R <= 20
0 to 2
20 km
R <= 30
0 to 1
30 km
R <= 39 0 39 km
R <= 60 0 60 km
1.5.3 BreezeCOMPACT QoS
QCI 1–4:
QCI 5–9:
The Special subframe contains the DL (DwPTS), Gap and UL (UpPTS) parts. A longer Gap
supports a longer range. Figure 15 describes the special subframe types.
Br
The Special subframe configuration defines the cell radius limitation, in addition to the
throughput allocation for the DL and the UL. UE’s located further than the cell radius are not
registered to the eNodeB.
Cell radius limitations may reduce inter-cell configuration issues and enable the UE to register
the correct eNodeB.
The table below describes the Special subframe configuration for each range.
3GPP defines the following levels of quality of service (QoS):
Guaranteed Bit Rate (GBR) service
Non-Guaranteed Bit Rate (Non-GBR)
Page 36
BreezeCOMPACT System Manual
BreezeCOMPACT Features
36
Figure 16: QCI Types
GBR:
MBR:
UE-AMBR:
1.5.4 BreezeCOMPACT Equal Time/Equal Rate Scheduler
Chapter 1: System Description
Figure 16 describes each QCI type and provides an application example for each type.
GBR provides a guaranteed bit rate and is associated with parameters such as GBR and MBR,
as follows:
The Non-GBR bearer does not provide a guaranteed bit rate and has the parameter
UE-AMBR, as follows:
QoS provisioning per UE can be either iHSS (in EPC and BreezeVIEW) or AAA.
The minimum guaranteed bit rate. Specified independently for the UL and
DL.
The maximum guaranteed bit rate. Specified independently for the UL and
DL.
non-GBR throughput among all APNs to a specific UE.
The UE aggregate maximum bit rate is the maximum allowed total
The system enables two scheduling schemes to support fairness between different UEs. It takes into account
scenarios in which the system is overloaded and has limited air resources. The BreezeCOMPACT scheduler
supports the following scheduling schemes: Equal Time and Equal Rate.
In order to ensure GBR committed rates in QCI 1-4, Equal rate scheduling is assigned always to
the GBR portion.
For the un-committed (MBR / AMBR), operator can configure the eNB for Equal time or Equal
rate.
Page 37
BreezeCOMPACT System Manual
Chapter 1: System Description
BreezeCOMPACT Features
37
1.5.5 Equal Rate Scheduling
Figure 17: Equal Rate Scheduling
1.5.5.1 Equal Time Scheduling
Figure 18: Equal Time Scheduling
1.5.5.2 Scheduling Schemes and QCI Mapping
GBR (Committed):
MBR Minus GBR (Uncommitted Portion):
UE-AMBR:
The Equal Rate scheduler attempts to deliver the same bit rate to all UEs provisioned that have
the same GBR/MBR/AMBR. When UEs have different radio link conditions, the low modulation
CPEs consume more air resource than the good modulation CPEs, in order to reach bit-rate
fairness, as shown below:
The Equal Rate scheme delivers rates that are proportional to the provisioning of
GBR/MBR/AMBR.
In Release 6.8, a new protection mechanism for Equal Rate was introduced to limit the
consumption of air resources by CPEs in poor radio conditions.
The Equal Time scheduler attempts to deliver the same air resources to all UEs provisioned that
have the same MBR. When UEs have different radio link conditions, lower-modulation CPEs get
a lower bit rate than good-modulation CPEs, as shown below:
The Equal Time scheme delivers rates that are proportional to the provisioning of MBR/AMBR.
The BreezeCOMPACT scheduler behavior for GBR/Non-GBR QCIs works as follows:
Guaranteed bit rate service (QCI 1–4):
Time/Equal Rate (based on user provisioning)
Schedule D with Equal Rate
Scheduled either using Equal
Non-guaranteed bit rate (QCI 5–9):
provisioning)
Scheduled either with Equal Time/Equal Rate (based on user
Page 38
BreezeCOMPACT System Manual
BreezeCOMPACT Features
38
1.5.6 Multiple PLMN IDs
1.5.7 EPC Redundancy and Load Balancing (Cluster)
Figure 19: EPC Redundancy and Load Balancing
Chapter 1: System Description
The PLMN ID is built by concatenating the Mobile Country Code (MCC) and the Mobile Network
Code (MNC). It provides the unique network identity. The same PLMN ID value must be
configured in both the EPC and the eNB. The BreezeCOMPACT can support multiple PLMN
IDs working with different MMEs/EPCs for multi-service networks and RAN sharing scenarios.
The eNodeB (BreezeCOMPACT) is configured with the list of MME IP addresses. When the UE
is initially attached, the eNodeB selects the relevant MME/EPC based on the PLMN ID.
For more details about this capability, contact Telrad.
The BreezeCOMPACT supports redundancy and load balancing between different
BreezeWAY2020 entities in an EPC cluster. The cluster organizes the EPC entities in order to
scale up the capacity and redundancy.
BreezeCOMPACT configuration enables multiple IP addresses to be configured for MMEs/EPCs
(as described for multiple PLMN IDs in Sections 1.5.5, Multiple PLMN IDs
When EPCs/MMEs are configured with the same PLMN ID, BreezeCOMPACT can select the
best EPC for load-balancing purposes.
Telrad BreezeCOMPACT eNB supports proportional-fair load-balancing mechanism for UE
sessions distribution between EPC (MME) entities it is associated with (S1 Flex topology). The
Load-balancing mechanism is applied during a new UE Attach procedure. eNB may be
provisioned with multiple EPCs (MMEs) in a load-balancing/ failover mode. BreezeCOMPACT
supports two pools of MMEs (EPCs) for load balancing
– Primary and Secondary.
EPC “balancing” is used within the pool – either Primary or Secondary. If no resources or no
available MME entities event occurs in the Primary pool, eNB will switch to the Secondary pool.
When resources of the Primary pool recover, eNB will switch back to use it (for a new-coming
UEs)
Note: In R6.9 BreezeCOMPACT with eEPC (BreezeWAY1010), can be configured to enable local
embedded EPC entity which can be set as one of EPC entities (either primary or secondary)
Page 39
BreezeCOMPACT System Manual
Chapter 1: System Description
BreezeCOMPACT Features
39
1.5.8 Spectrum analyzer
1.5.9 GPS
GPS Chaining
Figure 20: GPS Chaining
In case of GPS chaining, the chained units depend on proper operation of the
feeding units (Master or Slaves). Therefore for better redundancy general
recommendation would be to use single GPS per BreezeCOMPACT
The spectrum analyzer functionality was developed to help field engineers to define the best (less
interfere) channel for BreezeCOMPACT during the installation and commissioning. This
function is critical in unlicensed bands, such as in 3.65 GHz – 3.7 GHz in the US and Canada,
where other transmitting devices may interfere with the BreezeCOMPACT. In addition, it allows
operator in licensed band to identify existence of interference from other sources which may not
be allowed to use the spectrum.
GPS is used to synchronize the air link frames of Intra-site-located and Inter-site-located BTSs,
in order to ensure that the air frame starts at the same time in all base stations (BSs), and that
all BSs switch from transmit (DL) to receive (UL) at the same time. This synchronization is
necessary for preventing Intra-site and Inter-site interference and BS saturation (assuming that
all BSs operate with the same frame size and with the same DL/UL ratio).
The all-outdoor GPS receiver is a pole-mountable GPS receiver and antenna in a single
environmentally protected enclosure that is powered from the unit.
several collocated units (up to 4 BreezeCOMPACT units). The figure below describes the GPS
chaining connectivity.
is supported where the chaining enables the use of a single GPS receiver for
Page 40
BreezeCOMPACT System Manual
BreezeCOMPACT R7.2 Software Capabilities
40
1.6 BreezeCOMPACT R7.2 Software Capabilities
LTE 3GPP Capabilities:
3GPP Release:
Distance:
Transmit Modes (TM):
BreezeCOMPACT hardware Capabilities:
Number of Tx/Rx:
BreezeCOMPACT Topology:
new in R7.2)
BreezeCOMPACT SDR Capabilities:
GPS:
GPS:
GPS:
Data Port redudnacy :
BreezeCOMPACT embedded EPC –
Radio Capabilities:
Chapter 1: System Description
The following describes the BreezeCOMPACT R7.2 capabilities (the list includes existing and
new features): (For the most updated feature set please refer to the Release Notes)
configuration)
Single Sector
Split Mode 2x2 (Dual Sector with Single Carrier) – Single frequency or two different
frequencies for each sector
Dual Sector Mode (5+5MHz,10+10MHz,14+14MHz, 15+15MHz and 20+20MHz)
2x2 - Single frequency or two different frequencies for each sector
Dual Carrier Mode (5+5MHz,10+10MHz,14+14MHz, 15+15MHz and 20+20MHz)
2x2 - Two different frequencies for each Carrier on the same geogrpahical sector
Downlink Dual Carrier Aggregation with selected CPE’s
(5+5MHz,10+10MHz,14+14MHz, 15+15MHz and 20+20MHz) 2x2 - Two different
frequencies for each Carrier on the same geogrpahical sector towards the CPE (with
CPE9000, CPE12000)
Load Balancing of CPE’s between two Carriers within the same Geographical
Sector (via BreezeView)
Downlink Multi-User MIMO (MU-MIMO) (n
Higher sector throughput with enhanced spectral efficiency optimized for fixed
wireless. (Compact’s configuration to be used is 4Tx/4Rx)
Release 9 with Release 12 capabilities for selected UE’s
Up to 60 kilometers (km)
TM1, TM2, TM3 & TM4, TM8 (relevant for 4x4 single sector
4x4, 2x2, 2x4
Single BreezeCOMPACT or multiple on-site (chained)
Supporting Holdover time up to 2 hours
Enabling/Disabling Tx Power shutdown (Operator Parameter), when holdover
time is expired
(requires cell site switch support) –
Supporting Local (eEPC) and Remote EPC
Two IP addresses for BreezeCOMPACT – LTE interface and eEPC
UL and DL rate adaptation
UE power control
X2 Handover Support – A3 triggers (supported) and A5 Triggers
Equal Time/Equal Rate scheduling
WiMAX, LTE and LTE-Advanced
capability to switch from DAT1 to DAT2 in case of link down
BW1010 (on supported hardware models)
Page 41
BreezeCOMPACT System Manual
Chapter 1: System Description
BreezeCOMPACT R7.2 Software Capabilities
41
CAT12 Downlink 256QAM (with Selected CAT12 CPE’12000’s) (new in R7.2)
Soft Frequency Reuse (SFR) (new in R7.2)
(new in R7.2)
(new in R7.2)
CBRS Band 48 Support:
(
Services/ QOS:
Networking:
Management
Equal rate scheduling protection for low modulation CPEs (Weak UEs protection)
UL QAM64 supported (On supported CPE models)
Higher Downlink throughput (per sector and per CPE)
In case of Reuse 1 deployments where nearby cells operate in the same frequency.
Spectrum analyzer – full band scan
Spectrum analyzer (NI - Noise indication) – MAX NI during the last 5 min
measurements interval
UE KPIs using CPE VIEW
TDD configuration 0 - for enhanced Uplink as a demo mode
SSF#7 (for up to 10Km radius)
Frequency Selective Scheduling
Uplink Interference Protection for 5GHz bands (
Compact1000
CPE9000, CPE8100
EUD Support (please contact CS for latest SW versions):
Maximum Tx power limit
Channel Change
Downlink RSSI measurement via TR-069
Default bearers (GBR or Non-GBR QCIs)
Dedicated bearers (GBR or Non-GBR QCIs)
Supporting PBR – QoS between multiple GBR bearers
All QoS parameters support: QCI 1–9; GBR/MBR, AMBR with full rate policy
Multiple PLMN-IDs support
S1 interface is 802.1q tagged - VLANs for LTE infrastructure and Management.
DSCP and 802.1p policy-based marking at the infrastructure level for Control Plane
(LTE infrastructure VLAN), Management (Management VLAN) and User traffic (as per
LTE bearer QCI)
eNodeB Ethernet statistics
Rollback management
CLI User Authentication
NTP – BreezeVIEW address is added
Software Licensing
Load Balancing of CPE’s between two carriers within the same geographical sectors
Federated CBRS SAS Support Rel. 1.5 (please contact CS for latest SW versions)
Page 42
BreezeCOMPACT System Manual
Chapter 1: System Description
BreezeCOMPACT R7.2 Software Capabilities
42
Floating UE Licensing (for EPC and CPEView)
BreezeView feature Licensing per Comapct
Page 43
BreezeCOMPACT System Manual
zeCOMPACT Accessories and Specifications
43
1.7 BreezeCOMPACT Accessories and Specifications
1.7.1 Antennas
1.7.2 SFP (Fiber)
1.7.3 Modem and Radio
Table 2-5: General Modem and Radio Specifications
Item
Description
BreezeCOMPACT Family:
List of products supported
by frequency band,
maximum
port
BreezeCOMPACT 1000:
4
4
BreezeCOMPACT 2000: (N/A in Release 7.0 Onwards)
BreezeCOM
PACT 3000:
Breeze
U100:
5,150–5,900 MHz, 20 dBm per port, 4 Rx by 4 Tx
Central Frequency
Resolution
WiMAX: 0.125 MHz
LTE: 0.1 MHz
Operation Mode
TDD
Channel Bandwidth*
5, 10, 14, 15, 20 MHz – Single Carrier
20+20MHz – Dual Sector/Carrier
Tx Power Control Range
10 dB, in 1dB steps
Tx Power Accuracy
+/- 1 dB
Modulation
QPSK, QAM16, QAM64 (MCS0-MCS28), QAM256 (MCS_MCS__)
Chapter 1: System Description
Bree
In the system architecture, the antenna is represented as an independent element. This provides
the operator with the flexibility to select between different antenna types with various
capabilities, such as supported frequencies, gain, beam width and sizing.
BreezeCOMPACT supports 1GB fiber on the DAT1 port.
Telrad supplies the following accessories (must be ordered separately):
Pluggable multi-mode SFP (PN 300728) or single mode SFP (PN 300758)
LC connector
Adhesive tube shrink
Sealing gland
Tx power and
configuration
3,300–3,500 MHz, 30 dBm per port, 4 Rx by 4 Tx
3,400–3,700 MHz, 30 dBm per port, 4 Rx by 4 Tx
3,600–3,800 MHz, 30 dBm per port, 4 Rx by 4 Tx
5,150–5,900 MHz, 20 dBm per port, 4 Rx by 4 Tx
,900–5,350 MHz, 20 dBm per port, 4 Rx by
TxB
3,400–3,600 MHz, 37 dBm per port, 4 Rx by 2 Tx
(Tx RF ports 1, 2)
2,496–2,696 MHz, 40 dBm per port, 4 Rx by 4 Tx
2,300–2,400 MHz, 40 dBm per port, 4 Rx by 4 Tx
3,300–3,400 MHz, 40 dBm per port, 4 Rx by 4 Tx
3,400–3,600 MHz, 40 dBm per port, 4 Rx by 4 Tx
3,475–3,700 MHz, 40 dBm per port, 4 Rx by 4 Tx
5+5MHz, 10+10MHz, 14+14MHz, 15+15MHz,
Page 44
BreezeCOMPACT System Manual
BreezeCOMPACT Accessories and Specifications
44
Item
Description
Access Method
OFDMA Downlink
SC-FDMA Uplink
1.7.4 Data Communication (Ethernet Interfaces)
Table 2-6: Data Communication (Ethernet Interfaces)
Item
Description
Standards Compliance
IEEE 802.3 CSMA/CD
DAT 1 (optional, if an SFP is
installed)
1000Mbps Base-X optical fiber interface, Half/Full Duplex
with Auto-Negotiation
DAT 2
100/1000 Mbps Base-T twisted-pair electrical interface,
Half/Full Duplex with Auto-Negotiation
DAT 3
BreezeCOMPACT1000/3000 10/100 Mbps Base-T twistedpair electrical interface, Half/Full Duplex with Auto
Negotiation
BreezeCOMPACT with embedded EPC 10/100
Base
with Auto-Negotiation
1.7.5 GPS Receiver Specifications
Table 2-7: BMAX-4M-GPS and BreezeGPS Receiver, Mechanical and Electrical Specifications
Item
Description
Dimensions
8.8 x 10.4 x 16 cm
Weight
0.38 kilograms (Kg)
Power Source
12 VDC from the BTS
Power Consumption
2W maximum
Connector
RJ-45
1.7.6 Configuration and Management
Table 2-8: Configuration and Management
Item
Description
Management (Out-of-Band,
In
BreezeVIEW
CLI
Device Management protocol
NETCONF
Software Upgrade
TFTP/BreezeVIEW
Chapter 1: System Description
* Note only 10 and 20MHz channels supported when Compact is licensed for CBRS. All
spectrum allocation and grant to transmit will be issued by an approved SAS to BreezeView
Domain Proxy
** Note only 10, 15 and 20MHz channels supported when Compact 5GHz Mode subject to
local regulations
-T twisted-pair electrical interface, Half/Full Duplex
-
/1000 Mbps
-Band)
Page 45
BreezeCOMPACT System Manual
Chapter 1: System Description
BreezeCOMPACT Accessories and Specifications
45
1.7.7 Standards Compliance, General
Table 2-9: Standards Compliance, General
Type
Standard
EMC
ETSI EN 301 489-1/4
FCC Part 15
Safety
EN60950-1/22 (CE)
UL 62368-1
Environmental
ETS 300 019:
Part 2-4 T 4.1E for outdoor
Radio
ETSI EN 302 326
(Compact1000, BU100: 5.150-5.250MHz & 5.725-5.825MHz)
1.7.8 Environmental
Table 2-10: Environmental Specifications
Type
Details
Operating Temperature
-40°C to 55°C
Operating Humidity
5%–95%, weather protected
1.7.9 Mechanical and Electrical
1.7.9.1 BreezeCOMPACT 1000
Table 2-11: Mechanical and Electrical Specifications, BreezeCOMPACT 1000 Units
Item
Description
Dimensions
242.7 x 343 x 166.9 mm
Weight
8.2 Kg
Power Input
-40 to -60 VDC
Power Consumption
100W Average (at 70% Tx/Rx duty cycle)
142W peak (Power supply requirement)
Tx Ports/Rx Ports
Ports 1–4 (Tx), Ports 1–4 (Rx)
IEC/EN 62368-1 UL 60950-1/22 (US/C)
Part 2-1 T 1.2 and part 2-2 T 2.3 for indoor and outdoor
Part 2-3 T 3.2 for indoor
FCC Part 90
IC RSS-192
IC RSS-197
IC RSS-247
(Compact1000, BU100: 5.150-5.250MHz & 5.725-5.825MHz)
FCC Part 27
FCC Part 96 (CBSD Compact1000 3,550-3,700MHz)
FCC 47CFR, Part 15, Subpart E:
Colored certifications are under process for 5.XGHz Products (Compact1000 & BU100).
Certification is subject to relevant frequency band and Product Type
Page 46
BreezeCOMPACT System Manual
Chapter 1: System Description
BreezeCOMPACT Accessories and Specifications
46
Page 47
BreezeCOMPACT System Manual
BreezeCOMPACT Accessories and Specifications
47
1.7.9.2 BreezeCOMPACT 2000 (Not supported on R7.0 onwards)
Table 2-12: Mechanical and Electrical Specifications, BreezeCOMPACT 2000 Units
Item
Description
Dimensions
280 x 510 x 220 mm
Weight
19.5 Kg
Power Input
-40 to -60 VDC
Power Consumption
186W Average (at 70% Tx/Rx duty cycle)
225W peak (Power supply requirement)
Tx Ports/Rx Ports
Ports 1, 2 (Tx), Ports 1–4 (Rx)
1.7.9.3 BreezeCOMPACT 3000
Table 2-13: Mechanical and Electrical Specifications, BreezeCOMPACT 3000 Units
Item
Description
Dimensions
260 x 400 x 330 mm
Weight
19 Kg
Power Input
-40 to -60 VDC
Power Consumption
230W Average (at 70% Tx/Rx duty cycle)
300W peak (Power supply requirement)
Tx Ports/Rx Ports
Ports 1–4 (Tx), Ports 1–4 (Rx)
1.7.9.4 BreezeU100
Table 2-14: Mechanical and Electrical Specifications, BreezeU100 Unit
Item
Description
Dimensions
423 x 159 x 357 mm
Weight
12 Kg
Power Input
-40 to -60 VDC
Power Consumption
100W Average (at 70% Tx/Rx duty cycle)
142W peak (Power supply requirement)
Chapter 1: System Description
Page 48
BreezeCOMPACT System Manual
48
BreezeCOMPACT Commissioning,
2.1 BreezeCOMPACT Commissioning
2.1.1 Preface
2.1.1.1 For Un-License Markets:
Before commissioning BreezeCOMPACT or BreezeU100 at 5.XGHz Bands please refer
to 5GHz band warning on page 7. All RF configurations are subject to local/regional
regulations by Operator
2.1.1.2 For CBRS Markets:
Before commissioning BreezeCOMPACT please refer to CBRS band warning on page 7.
Figure 21: SAS Server Setting Screen
Chapter 2: Commissioning Steps
In This Chapter:
B
on page 48
All RF configuration is handled by CBSD configuration within BreezeView Domain
proxy
SAS Communication is required as are necessary parameters detailed on page 7. All
parameters below must be populated for the Category B CBSD. Telrad standard 65 degree
antenna is 17.5dBi. This 17.5 dBi will be computed as part of MAX EIRP. MAX EIRP will be
granted by the SAS based. Assuming no coexistence requirements or incumbent protection this
EIRP would be 47dBm/10MHz. Based on 2x2 MiMO the Compact could use up to 30dBm per
port i.e. 30dBm (MiMO per port cross polarized) + antenna gain 17.5dBi - .5dB cable loss =
47dBm EIRP. When using 4x4 (TM4) The max TX power would be 27dBm to account for MiMO
Array Gain.
Page 49
BreezeCOMPACT System Manual
49
BreezeCOMPACT Commissioning
Figure 22: CBSD Screens
Chapter 2: Commissioning Steps
SAS Communication is required as are necessary parameters detailed on page 7. All
parameters below must be populated for the Category B CBSD. Telrad standard 65 degree
antenna is 17.5dBi. This 17.5 dBi will be computed as part of MAX EIRP. MAX EIRP will be
granted by the SAS based. Assuming no coexistence requirements or incumbent protection this
EIRP would be 47dBm/10MHz. Based on 2x2 MiMO the Compact could use up to 30dBm per
port i.e. 30dBm (MiMO per port cross polarized) + antenna gain 17.5dBi - .5dB cable loss =
47dBm EIRP. When using 4x4 (TM4) The max TX power would be 27dBm to account for MiMO
Array Gain.
Page 50
BreezeCOMPACT System Manual
50
BreezeCOMPACT Commissioning
2.1.2 Purpose
2.1.3 BreezeCOMPACT Commissioning Procedure
2.1.3.1 Initial Out-of-the-Box Connection
1
2
192.168.1.100
3
4
192.168.1.1
5
admin
.
BreezeCompact>
configure
BreezeCompact%
Chapter 2: Commissioning Steps
This procedure describes the steps required to initially commission the BreezeCOMPACT 1000,
2000 and 3000 and BreezeU100, in order to enable its connection for provisioning.
BreezeWAY1010 embedded EPC configuration is covered in BreezeWAY user manual
The following procedure assumes that the BreezeCOMPACT LTE software is already loaded
(already upgraded from WiMAX or shipped with the LTE software) and has been set to the
factory defaults.
¾ To connect the Br eezeCOMPACT :
Connect the cable from the PC to the DATA3 Local Management port.
On the PC, define the IP address as 1
Connect the BreezeCOMPACT unit to the power supply and wait until the unit boots up.
Use any Telnet client software on the PC, such as putty.exe, to access the eNodeB using the
IP address 1
After a prompt is displayed, perform the following:
Log in using a
.
Use the password LteAdmin!.
At the B
displays.
It is recommended that you change the password. To change the password, see the
BreezeVIEW User Manual
for more details.
.
prompt, type c
.
. The B
prompt
Page 51
BreezeCOMPACT System Manual
51
mmissioning
2.1.3.2 eNodeB initial general and external management parameters
1
2
3
BreezeCompact%
set device general enable-embedded-EPC
BreezeCompact%
set networking external-management ip-address
set networking external-management subnet-mask
set networking external-management next-hop-gateway
set networking external-management vlan-id
set networking external-management use-bearer-ip-address
Chapter 2: Commissioning Steps
BreezeCOMPACT Co
This section describes how to define the management parameters for the CLI and the
BreezeVIEW connectivity. To define CLI with BreezeVIEW - general and external
Management connection parameters:
Perform the procedure described in Section 2.1.3.1, Initial Out-of-the-Box Connection.
Perform eNodeB Timing and GPS configuration as described in Section 4.2.2.11
Perform basic device commissioning procedure
Set Device ID
At the B
commands: set device general device-id < unsignedInt, 1 .. 999999 >
prompt, set parameters by entering the following
For embedded eNB (BreezeCompact 1000e) use the following command to
enable/disable EPC
<Disable or Enable>.
External management IP parameters
At the B
commands:
address >
subnet mask >
management default gateway>
management >
This value can be a vlan number or NoVLAN in case that this external
management port is not tagged with VLAN.
prompt, set parameters by entering the following
<The external management IP
<The external management
<The external
<VLAN of the external
The default value is false. Set the value to true in case that the s1 bearer address
and the external management will have the same IP address
<true or false >
Page 52
BreezeCOMPACT System Manual
52
Chapter 2: Commissioning Steps
BreezeCOMPACT Commissioning
BreezeCompact%
set networking physical-ports-list
duplex-mode
set networking physical-ports-list
negotiation
set networking physical-ports-list
speed
set device management nms-ip
set device management tftp-ip-address
4
5
6
BreezeCompact> request reboot reboot
L1 & L2 Port configuration (default Auto negotiate)
At the B
commands:
or HalfDuplex>
This command sets a port Duplex (half or full)
manual>
This command sets a port negotiation to manual or Automatic mode.
command sets the port speed to 100 or 1000 .
Important remark : For port 1: speed may be 1 Gb only For port 2: speed may be
100Mb or 1Gb only For port 3: speed may be 100Mb only in
BreezeCOMPACT1000 & 3000, in case of embbeded EPC 1000Mb can be set.
Configure NMS BreezeVIEW IP address to permit auto discovery of the device.
prompt, set parameters by entering the following
<Port number 1-3> d
<Port number 1-3> n
<Port number 1-3> s
<fullDuplex
<Auto or
<100 ,1000> This
<The NMS IP address>
Configure the TFTP server IP address (used for software version upgrade) –
TFTP server IP address (optional)
Perform license loading according to the procedure described in the Chapter 6, Licensing
Mechanism.
Perform commit procedure as explained in3.1
Reboot is required for changes to take effect
The reboot will disrupt all services provided by device. Are You sure? [no,yes] yes
<TFTP Server IP address>
Page 53
BreezeCOMPACT System Manual
53
BreezeCOMPACT Commissioning
1
2
3
7
8
Chapter 2: Commissioning Steps
¾ To install the Br eezeCOMPACT har dware on a pol e:
Follow the hardware installation instructions provided in the quick installation guides for
the various BreezeCOMPACT devices.
Connect DATA1 or/and DATA2 to the network.
Install the GPS and connect the GPS cable.
After the eNodeB is up, it is discovered automatically by BreezeVIEW.
You can configure the eNodeB using:
BreezeVIEW configuration methods (such as Manual and Template). For more details, see
Section 3.3.6, Configuring Via BreezeVIEW.
A direct SSH connection to an external management IP address in order to use the
management CLI. For more details, see Chapter 3, Operation and Administration
Procedures.
5. Please verify if the equipment installed properly. The PWR (Power) and GPS LEDs status
should be GREEN.
Page 54
BreezeCOMPACT System Manual
54
Chapter 3: Operation and Administration
Procedures
Configuration commit procedure
BreezeCOMPACT Full Configuration via
Software Upgrade Via
Software Upgrade Via BreezeVIEW,
Resetting BreezeCOMPACT to Its Factory Default,
Provisioning BreezeCOMPACT Using a Template,
Locking and Unlocking a Device,
Spectrum Analyzer Collection,
Performance Monitoring,
3.1 Configuration commit procedure
1
Commit
2
3
4
Chapter 3: Operation and
Administration Procedures
In This Chapter:
The following section will cover the relevant CLI commands in two ways:
CLI, on page 93
on page 109
on page 112
on page 120
CLI, on page 56
on page 96
The following procedure explains how to implement updates in CLI configuration.
After performing such updates follow the following steps at the BreezeCompact% prompt
C
A message "commit update" should show up in case that the validation check for the last
changes past successfully.
quit (it is not mandatory to exit from configuration mode to continue)
on page 103
on page 105
Once configuration changes are complete and committed. It is required to perform a reset to
activate the changes, at the BreezeCompact> prompt, type the following:
request reboot reboot
When the following message displays, type yes to confirm:
The reboot will disrupt all services provided by device. Are You sure? [no,yes]
The eNB as a result will reset then the eNB should come up with the updates implemented
configuration.
Page 55
BreezeCOMPACT System Manual
55
Chapter 3: Operation and Administration
Procedures
Radius Authentication
3.2 CLI User – Radius Authentication
Figure 23: CLI User – Radius Authentication
CLI User –
To implement this feature please contact a Telrad Support
Release 6.9 enables a new feature – authentication and authorization of the management user
session using RADIUS. If configured, when a new SSH management session is being established
to BreezeCOMPACT entity, BreezeCOMPACT management client will trigger RADIUS session
authentication and authorization with the provisioned AAA server.
As per authorization parameters, 2 types of access rights are supported: read-write access or readonly access. BreezeCOMPACT entity generates an audit log for any change performed by the
management user, capturing modification Date and Time, User name and the committed change.
Page 56
BreezeCOMPACT System Manual
56
Chapter 3: Operation and Administration
Procedures
on via CLI
3.3 BreezeCOMPACT Full Configuration via CLI
3.3.1 Purpose
3.3.2 Full Configuration via CLI Procedure
3.3.2.1 Configuring Device Settings
BreezeCompact%
3.3.2.2 Configuring LTE TDD Configuration
set deployment frame-structure subframe-Cfg <Sub frame configuration number >
set deployment frame-structure special-subframe-Cfg <special sub frame
configuration number >
set deployment wimax-coexisting <true or false>
show deployment
BreezeCOMPACT Full Configurati
This procedure describes how to configure the BreezeCOMPACT for full functionality.
The following procedures must only be performed after the commissioning procedure described in
Chapter 3, Commissioning has been completed. The following procedures must be performed in
the same order as described below.
Device general settings
At the B
commands:
set device general device-id <The unique device ID>
prompt, set parameters by entering the following
set device general address <Address location of the device>
set device general area <Operator Area location of the device>
set device general contact <The name of the contact person>
set device general name <The name of the device and device site>
Device management settings (DNS IP Address)
set device management primary-dns-ip-address <Primary DNS IP address>
set device management secondary-dns-ip-address <Secondary DNS IP address>
In order to configure LTE TDD and special subframe configuration the following cli commands
should be performed from BreezeCompact% prompt:
set cell ran-common cell-radius <cell radius number in km>
The value for the cell radius should be between 1-60 km
The value for the sub frame configuration should be between 0-2 (These are the supported
values). Please see further explanation regarding the possible sub frames in 1.5.2.1
The value for the special sub frame configuration should be within 0-3 (These are the supported
values). Please see further explanation regarding the possible special sub frame configurations
in 1.5.2.2
It is recommended to set this value as true .This value is important to be set to true in order to
be avoided from mutual interference when WiMAX is running and additional LTE deployments.
In order to show the Implanted configuration, run the following command from BreezeCompact%
prompt:
As a result, you will see the following output as an example:
Page 57
BreezeCOMPACT System Manual
57
Chapter 3: Operation and Administration
Procedures
OMPACT Full Configuration via CLI
Figure 24: Deployment Tab in BreezeVIEW
3.3.2.3 Configuring deployment for an Antenna Topology
3.3.2.3.1 Default topology - single carrier 2Rx/2Tx
set deployment topology DefaultTopology
show deployment topology
topology DefaultTopology;
show ran rh-ports-admin-state
show status ran port
topology SplitMode2X2; wimax-coexisting true; enable-dcs false;
frame-structure { subframe-Cfg 2;
special-subframe-Cfg 0;
}
BreezeC
In this release, the supported modes are Single Sector and Dual Carrier/Split Mode 2x2. For more
details, see Section 1.5.1, BreezeCOMPACT Topologies.
At the BreezeCompact% prompt, set the cell deployment topology of the antenna:
This is the default deployment topology. In case that it's required to set the deployment topology
to default topology the following steps should be considered:
The following command should be running from CLI from BreezeCompact% prompt:
Perform commit procedure as in 3.1
When running:
Result is:
When running:
result is:
port1-admin-state Operative; port2-admin-state Operative; port3-admin-state ShutDown;
port4-admin-state ShutDown;
When running From BreezeCompact> prompt :
result is: PortsList 1 {
operational-status InService; admin-state InService;
}
PortsList 2 {
Page 58
BreezeCOMPACT System Manual
58
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
Figure 25: BREEZEVIEW -ENB deployment tab when setting deployment topology as Default
topology
Figure 26: BREEZEVIEW -ENB Advanced RAN tab when setting deployment topology as Default
3.3.2.3.2 Single Carrier 2T x /4Rx
set deployment topology SingleCarrier2X4
commit
show deployment topology
operational-status InService; admin-state InService;
}
PortsList 3 {
operational-status OutOfService; admin-state InShutdown;
}
PortsList 4 {
operational-status OutOfService; admin-state InShutdown;
}
The above means that 2 antennas (1,2) are operative and antennas 3,4 are not. Default topology
control in BreezeView :
When looking on the BreezeVIEW ENB Advanced RAN tab:
In this mode 2 antennas in transmit mode and 4 antennas in receive.
In order to change the deployment mode to single carrier 2Tx/4Rx perform the following CLI
command from ENB from BreezeCompact% prompt:
when running:
result is :
topology SingleCarrier2X4;
When running:
Page 59
BreezeCOMPACT System Manual
59
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
show ran rh-ports-admin-state
result is:
port1-admin-state Operative; port2-admin-state Operative; port3-admin-state RxOnly; port4admin-state RxOnly;
Page 60
BreezeCOMPACT System Manual
show status ran port
Figure 27: BREEZEVIEW -ENB Antenna's status in single carrier 4Rx/2Tx
Figure 28: BREEZEVIEW -ENB deployment tab in single carrier 4Rx/2Tx
3.3.2.3.3 Single Carrier 4X4
When running from BreezeCompact> prompt :
s
result is: PortsList 1 {
operational-status InService; admin-state InService;
}
PortsList 2 {
operational-status InService; admin-state InService;
}
PortsList 3 {
operational-status InService; admin-state RxOnly;
}
PortsList 4 {
operational-status InService; admin-state RxOnly;
}
On BreezeVIEW :
When clicking on the BreezeVIEW home->devices->ENB ->device details :
When looking on Breeze view on the ENB deployment tab:
In order to change the topology to Single carrier 4x4 , On BreezeCOMPACT CLI from
BreezeCompact% prompt perform the following commands :
When running from % prompt: "show deployment topology" topology SingleCarrier4X4TM4;
When running from % prompt : " show ran rh-ports-admin-state" port1-admin-state Operative;
port2-admin-state Operative; port3-admin-state Operative; port4-admin-state Operative;
set deployment topology SingleCarrier4X4TM4
Perform commit procedure as per 3.1
Page 61
BreezeCOMPACT System Manual
61
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
Figure 29: BREEZEVIEW -ENB Antenna's status in single carrier 4Rx/4Tx
Figure 30: BREEZEVIEW -ENB deployment tab in single carrier 4Rx/4Tx
3.3.2.3.4 Single Carrier 4X4 with DL MU-MIMO
When running from > prompt : "show status ran port" you should see the following :
PortsList 1 {
operational-status InService; admin-state InService;
}
PortsList 2 {
operational-status InService; admin-state InService;
}
PortsList 3 {
operational-status InService; admin-state InService;
}
PortsList 4 {
operational-status InService; admin-state InService;
}
On BreezeVIEW :
When clicking on the BREEZEVIEW home->devices->ENB ->device details:
When looking on Breeze view on the ENB deployment tab:
In order to change the topology to Single carrier 4x4 with DL MU-MIMO, On
BreezeCOMPACT CLI from BreezeCompact% prompt perform the following commands :
Page 62
BreezeCOMPACT System Manual
62
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
Figure 31: BREEZEVIEW -ENB Antenna's status in single carrier 4Rx/4Tx DL MU-MIMO
set deployment topology MuMimo
Perform commit procedure as per 3.1
On BreezeCOMPACT1000>show ran
ran general min-freq 3400
ran general max-freq 3700
ran general max-tx 30
ran general port-config 4x4
PORT OPERATIONAL ADMIN
NUM STATUS STATE
1 InService InService
2 InService InService
3 InService InService
4 InService InService
BreezeCOMPACT1000%show ran
rh-ports-admin-state {
port1-admin-state Operative;
port2-admin-state Operative;
port3-admin-state Operative;
port4-admin-state Operative;
}
[ok]
On BreezeVIEW :
When clicking on the BREEZEVIEW home->devices->ENB ->device details:
When looking on Breeze view on the ENB deployment tab:
Page 63
BreezeCOMPACT System Manual
63
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
Figure 32: BREEZEVIEW -ENB deployment tab in single carrier 4Rx/4Tx DL MU-MIMO
3.3.2.3.5 SplitMode2X2:
show deployment topology
show ran rh-ports-admin-state
The Split Mode 2x2 normal mode will use the same frequency for both sectors.
In order to change the deployment mode to SplitMode2x2 perform the following CLI command
from ENB from BreezeCompact% prompt:
set deployment topology SplitMode2X2
Perform commit procedure on 3.1
when running:
result is:
topology SplitMode2X2;
When running:
result is:
port1-admin-state Operative; port2-admin-state Operative; port3-admin-state Operative;
port4-admin-state Operative;
When running from BreezeCompact> prompt :
Page 64
BreezeCOMPACT System Manual
64
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
show status ran port
Figure 33: BREEZEVIEW -ENB Antenna's status in SplitMode2x2
Figure 34: BREEZEVIEW -ENB deployment tab when in SplitMode2x2
3.3.2.3.6 SplitModef1f2:
result is:
PortsList 1 {
operational-status InService; admin-state InService;
}
PortsList 2 {
operational-status InService; admin-state InService;
}
PortsList 3 {
operational-status InService; admin-state InService;
}
PortsList 4 {
operational-status InService; admin-state InService;
}
On BreezeVIEW :
When clicking on the BREEZEVIEW home->devices->ENB ->device details :
When looking on Breeze view on the ENB deployment tab:
On SplitMode2x2 all 4 antennas are fully operational. All Antenna's will work with the same
frequency.
Split mode f1f2 enabling each 2x2 sector (port 1,2 and port 3,4) to define different center
frequencies.
On BreezeCOMPACT CLI from BreezeCompact% prompt perform the following in order to set:
Page 65
BreezeCOMPACT System Manual
65
Chapter 3: Operation and Administration
Procedures
onfiguration via CLI
set deployment topology SplitModef1f2
set cell1
central-frequency <Frequency 1 in MHZ>
set cell1
central-frequency-f2 < Frequency 2 in MHZ>
show status ran port
general
general
Perform commit procedure as per 3.1
When running: show deployment topology
Result is: topology SplitModef1f2;
When running: show ran rh-ports-admin-state
Result is: port1-admin-state Operative; port2-admin-state Operative; port3-admin-state
Operative; port4-admin-state Operative;
When running: show cell ran-rf
result is:
bandwidth 5MHz;
tx-power 30;
BreezeCOMPACT Full C
When running: show cell0 general
result is:
central-frequency 3510.0;
central-frequency-f2 3540.0;
phy-cell-id 0;
result is :
PortsList 1 {
operational-status InService; admin-state InService;
}
PortsList 2 {
operational-status InService; admin-state InService;
}
PortsList 3 {
operational-status InService; admin-state InService;
}
PortsList 4 {
operational-status InService; admin-state InService;
}
On BREEZEVIEW when looking in Home->devices->ENB ->Device details:
Page 66
BreezeCOMPACT System Manual
66
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
Figure 35: BREEZEVIEW -ENB Antenna's status in SplitModef1f2
Figure 36: BREEZEVIEW -ENB deployment tab when in SplitModef1f2
Figure 37: BREEZEVIEW -ENB CELL0 deployment tab when in SplitModef1f2
3.3.2.3.7 Dual Sector/Carrier:
When looking on BREEZEVIEW->Home->devices-> ENB deployment tab :
On BREEZEVIEW->devices->ENB ->cell0 tab:
As can be seen in Figure 27: BREEZEVIEW -ENB CELL0 deployment tab when in
SplitModef1f2 it is important to set F2 frequency when working on splitModef1f2
The Dual Carrier topology enables a double-capacity BreezeCOMPACT. In this mode, the
BreezeCOMPACT behaves like two 2x2 eNodeBs (double capacity vs split mode).
On BreezeCOMPACT CLI from BreezeCompact% prompt perform the following in order to set:
set deployment topology DualCarrier
set cell1 general central-frequency <Frequency 1 in MHZ>
set cell1 general central-frequency-f2 < Frequency 2 in MHZ>
Perform commit procedure as per 3.1
When running: show deployment topology
Result is: topology DualCarrier;
When running: show ran rh-ports-admin-state
Result is: port1-admin-state Operative; port2-admin-state Operative; port3-admin-state
Operative; port4-admin-state Operative;
Page 67
BreezeCOMPACT System Manual
67
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
Figure 38: BREEZEVIEW -ENB Antenna's status in DualCarrier
When running: show cell ran-rf
result is:
bandwidth 5MHz;
tx-power 30;
When running show cell0 general
result is:
cell-identity 0;
central-frequency 3510.0;
phy-cell-id 0;
When running show cell1 general
result is:
cell-identity 0;
central-frequency 3510.0;
phy-cell-id 0;
show status ran port
result is :
PortsList 1 {
operational-status InService; admin-state InService;
}
PortsList 2 {
operational-status InService; admin-state InService;
}
PortsList 3 {
operational-status InService; admin-state InService;
}
PortsList 4 {
operational-status InService; admin-state InService;
}
On BREEZEVIEW when looking in Home->devices->ENB ->Device details:
When looking on BREEZEVIEW->Home->devices-> ENB deployment tab :
Page 68
BreezeCOMPACT System Manual
68
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
Figure 39: BREEZEVIEW -ENB deployment tab when in DualCarrier
Figure 40: BREEZEVIEW -ENB CELL0 deployment tab when in DualCarrier
Figure 41: BREEZEVIEW -ENB CELL1 deployment tab when in DualCarrier
3.3.2.3.8 Dual Carrier Aggregation:
On BREEZEVIEW->devices->ENB ->cell0 tab:
On BREEZEVIEW->devices->ENB ->cell1 tab:
The Dual Carrier Aggregation topology enables in addition to a double-capacity
BreezeCOMPACT, an up to double downlink capacity on selected CPE. In this mode, the
BreezeCOMPACT behaves like two 2x2 eNodeBs (up to double downlink capacity vs split
mode) and enables selected CPE’s to aggregate downlink traffic from both carriers.
On BreezeCOMPACT CLI from BreezeCompact% prompt perform the following in order to set:
set deployment topology DualCarrierAggregation
set cell0 general central-frequency <Frequency 0 in MHZ>
set cell1 general central-frequency <Frequency 1 in MHZ>
set cell0 general phy-cell-id [physical cell ID 0]
set cell1 general phy-cell-id [physical cell ID 1]
Perform commit procedure as per 3.1
When running: show deployment topology
Result is: topology DualCarrierAggregation
When running: show ran rh-ports-admin-state
Page 69
BreezeCOMPACT System Manual
69
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
Result is: port1-admin-state Operative; port2-admin-state Operative; port3-admin-state
Operative; port4-admin-state Operative;
When running: show cell ran-rf
result is:
bandwidth 5MHz;
tx-power 30;
When running show cell0 general
result is:
cell-identity 0;
central-frequency 3510.0;
phy-cell-id 1;
When running show cell1 general
result is:
cell-identity 1;
central-frequency 3510.0;
phy-cell-id 1;
show status ran port
result is :
PortsList 1 {
operational-status InService; admin-state InService;
}
PortsList 2 {
operational-status InService; admin-state InService;
}
PortsList 3 {
operational-status InService; admin-state InService;
}
PortsList 4 {
operational-status InService; admin-state InService;
}
On BREEZEVIEW when looking in Home->devices->ENB ->Device details:
Page 70
BreezeCOMPACT System Manual
70
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
Figure 42: BREEZEVIEW -ENB Antenna's status in DualCarrierAggregation
Figure 43: BREEZEVIEW -ENB deployment tab when in DualCarrierAggregation
Figure 44: BREEZEVIEW -ENB CELL0 deployment tab when in DualCarrierAggregation
Figure 45: BREEZEVIEW -ENB CELL1 deployment tab when in DualCarrierAggregation
3.3.2.4 Configuring the Bearer Network
When looking on BREEZEVIEW->Home->devices-> ENB deployment tab :
On BREEZEVIEW->devices->ENB ->cell0 tab:
On BREEZEVIEW->devices->ENB ->cell1 tab:
The Bearer network is used to enable an LTE S1 connection between the eNodeB and the
MME. It supports the S1-C, S1-U and X2 protocols over an SCTP connection.
The Bearer connection is defined on the same port as the management port, with a different
VLAN separation.
Page 71
BreezeCOMPACT System Manual
71
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
BreezeCompact%
9
10
11
12
13
3.3.2.5 Configuring S1 Signaling
BreezeCompact%
14
15
16
¾ To configure th e bear er net work:
At the B
set networking lte-infrastructure enb-ip-address < eNB infrastructure IP address>
set networking lte-infrastructure subnet-mask <Subnet mask>
set networking lte-infrastructure next-hop-gateway <DGW IP>
set networking lte-infrastructure vlan-id <VLAD ID or NoVLAN>
For eEPC with EPC mode Enable,
set networking lte-infrastructure eepc-ip-address < IP address of the embedded EPC>
the following commands:
¾ To show the current configuration run the following command:
show networking lte-infrastructure:
enb-ip-address 192.168.11.14;
subnet-mask 255.255.255.0;
next-hop-gateway 192.168.11.254;
vlan-id 11;
The S1 signaling IP list is used to connect to up to six EPC (MME) IP addresses, in order to
enable a redundant, load-balancing configuration. Using this configuration for multiple MME
IP addresses enables either load balancing or multiple PLMID capabilities. For more details,
see Section 1.5.6, Multiple PLMN IDs
prompt, set the bearer network parameters by entering
and Section 1.5.7, EPC Redundancy and Load Balancing (Cluster).
¾ To configure an S1 signaling connection to the EPC BreezeWay2020:
At the B
set networking s1-signaling link-server-list <MME IP address>
prompt, enter the following command:
¾ In order to delete an existing configured s1 signaling connection to the EPC
BreezeWay2020:
At the BreezeCompact% prompt, enter the following command:
delete networking s1-signaling link-server-list <Default MME IP address>
¾ To show the current configuration:
At the Breezecompact% prompt , enter the following command:
show networking s1-signaling-servers-list As a result you will see the following output:
s1-signaling-servers-list 172.16.81.144;
Page 72
BreezeCOMPACT System Manual
72
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
3.3.2.5.1 PLMN-ID setting
plmn-identity-list 011111 is-primary true
3.3.2.5.2 Load Balancing & Redundancy setting
¾ In order to configure TAC per ENB run the command below:
At the BreezeCompact% prompt, enter the following command:
set cell tracking-area tac <Track area code number >
¾ In order to show the TAC configured in the ENB run the command below
from the BreezeCompact% pro mpt
show cell tracking-area
As a result you should get the output as per the example below : tac 1;
The BreezeCOMPACT support multiple PLMN-IDs to enable multi-service modes, each
PLMN-ID can be supported by the EPCs in the network. Once PLMN-IDs are set the eNodeB
publish over the air to all UEs the available PLMN-IDs, according to the UE logic it decides
which PLMN ID will be selected. In case UE does not select the PLMN-ID, the default PLMNID is used by the eNodeB.
In order to Set PLMN IDs:
set cell tracking-area p
is-primary settings :
true – The PLM-ID is the default PLMN-ID false – non default PLMN-ID
¾ In order to show the PLMN ID configured in the ENB run the command
below from the BreezeCompact% prompt
Show cell tracking-area plmn-identity-list
As a result you should get the output as per the example below : plmn-identity-list 00101;
The Load-balancing mechanism is applied during a new UE Attach procedure. eNB may be
provisioned with multiple EPCs (MMEs) in a load-balancing/ failover mode.
BreezeCOMPACT supports two pools of MMEs (EPCs) for load balancing – Primary and
Secondary.
EPC load balancing is used within the pool – either Primary or Secondary. If no resources or no
available MME entities event occurs in the Primary pool, eNB will switch to the Secondary
pool. When resources of the Primary pool recover, eNB will switch back to use it (for a newcoming UEs)
Note, that BreezeCOMPACT supports multiple PLMNIDs concept for EUTRAN sharing and
multi-service networks convergence. In this case, BreezeCOMPACT will sort out all the MMEs
(EPCs) per PLMNID – effectively, this will result in Primary/ Secondary EPC pools per each of
the configured PLMNIDs (MME provides its PLMNID to eNB during S1 Setup).
eNB balancing the UE sessions between MMEs during UE Attach. The eNB balancing
algorithm takes into account EPC relative capacity and actual eNB load for the particular
EPC. “EPC relative capacity” is the number configured in EPC and provided to eNB during S1
setup. It is proportional to EPC licensed capacity. “Actual capacity”- is the local eNB counter
that represents the number of active UE sessions on the particular EPC.
Page 73
BreezeCOMPACT System Manual
73
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
For load balancing - configure MMEs within the same group (Primary or
secondary group)
3.3.2.6 Use Bearer Interface as External Management Mode
Bearer
Interface as External Management
Mode
BreezeCompact%
BreezeCompact%
In the case of a restart on one of the EPC entities, after that EPC recovers, eNBs will force all
the sessions to it until the load between all the entities is proportionally aligned.
In the case eNB switched to work with the Secondary MME pool, the UE sessions forwarded to
"secondary" MME entities will stay there until UE disconnection. After the recovery of the
primary, in a new UE Attach, eNB will perform the new balancing decision, forwarding the
new coming UEs to one of the Primary MME entities. There is a manual operational command
on eNB that enables an operator to force disconnection of UE sessions on Secondary MME
entities to move to the primary.
Following the settings. This should be running from BreezeCompact% prompt:
set networking s1-signaling-servers-list 172.16.81.144 mme-load-balancing-
priority Primary
set networking s1-signaling-servers-list 172.26.20.70 mme-load-balancing-
priority Secondary
Secondary)
For Fail over – configure at least two MMEs (one in primary group and one in
Show MME settings:
BreezeCompact% show networking s1-signaling-servers-list
s1-signaling-servers-list 172.16.81.144 {mme-load-balancing-priority Primary;
}
s1-signaling-servers-list 172.26.20.70 { mme-load-balancing-priority Secondary;
}
Note, in case the primary fail consequently all the UEs which associate with the primary MME
automatically will registers with the secondary MME. When the primary MME will come up
the UEs that are connected to the secondary MME will not move back to the primary MME
unless the operator will initiate the following command:
BreezeCompact% prompt:
request eNB-actions switch-over-to-primary-mme-pool
If a single interface is used for both bearer traffic and management, you must select the B
M
and external management parameters are ignored.
option. In this mode, only the bearer VLAN is used
Do not use this mode when using the BreezeWay2020, as the Management and
Bearer must be defined on different VLANs.
To enable this mode, enter the following command at the B
set networking external-management use-bearer-ip-address true
To disable this mode (the default mode), enter the following command at the B
prompt:
prompt:
Page 74
BreezeCOMPACT System Manual
74
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
17
3.3.2.7 Data Port redundancy
3.3.2.8 Modifying Physical Data Port Parameters
set networking external-management use-bearer-ip-address false
To show the current configuration:
At the Breezecompact% prompt , enter the following command:
show networking external-management use-bearer-ip-address As a result you will see the
following output:
use-bearer-ip-address false;
To make BreezeCOMPACT1000/3000 DAT1 and DAT2 redundancy the DAT1 (fiber) and DAT2
(copper) links must be active in the same time.
Only one port will be active a time (preferred is DAT1) and in time connection (link) failed, the
eNB will be switch its connectivity to DAT2.
Note: In R6.9, BreezeCOMPACT with embedded EPC hardware (1000e) does not support
dynamic data port redundancy. For further information, please contact Telrad CS.
Modifying physical data port parameters is optional.
A 1GB interface can use either the DAT1 (Fiber) or DAT2 (Copper) interface.
Page 75
BreezeCOMPACT System Manual
75
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
Figure 46: Physical ports configuration in BREEZEVIEW
¾ To modify physical data port parameters:
Use following command level in BreezeCompact% prompt:
set networking physical-ports-list <Port number 1-3> duplex-mode <fullDuplex
or HalfDuplex>
This command sets a port Duplex (half or full)
set networking physical-ports-list <Port number 1-3> negotiation <Auto or
manual> This command sets a port negotiation to manual or Automatic mode.
set networking physical-ports-list <Port number 1-3> speed <100 ,1000> This
command sets the port speed to 100 or 1000 .
Important remark : For port 1: speed may be 1 Gb only For port 2: speed may be 100Mb or
1Gb only For port 3: speed may be 100Mb only in BreezeCOMPACT1000 & 3000, in case of
embbeded EPC 1000Mb can be set.
¾ To show the current port configuration:
Use following command level in BreezeCompact% prompt:
show networking physical-ports-list The result should look like that :
physical-ports-list 1 { negotiation Auto;
duplex-mode FullDuplex; speed 1000;
}
physical-ports-list 2 { negotiation Auto;
duplex-mode FullDuplex; speed 1000;
}
physical-ports-list 3 { negotiation Auto;
duplex-mode FullDuplex; speed 100;
}
¾ To show the current configuration from BREEZEVIEW open from
BREEZEVIEW->home->devices->ENB->networking tab and see the Physical
data ports table as in the bottom part of this tab :
Page 76
BreezeCOMPACT System Manual
76
Chapter 3: Operation and Administration
Procedures
onfiguration via CLI
3.3.2.9 Modifying Local Management Connectivity Parameters
18
19
20
3.3.2.10 Configuring the Cell (RAN)
BreezeCompact%
21 set cell tracking-area ttac <Tracking Area ID>
22 set cell tracking-area pplmn-identity-list <Customer PLMN ID>
BreezeCOMPACT Full C
Local management refers to IP connectivity from a PC that connects directly to the eNodeB
local network port (DAT3) using a
on-the-bench
Modifying local management connectivity parameters is optional.
provisioning as part of the commissioning process or during other debugging.
¾ To modify local management connectivity parameters:
Use following command level from BreezeCompact% prompt
set networking local-management ip-address <IP address of the local Management
interface>
set networking local-management subnet-mask <Local management subnet mask of the IP
interface>
¾ To show the current configuration:
Use following command level from BreezeCompact% prompt
same subnet IP
without a VLAN. This connection enables
show networking local-management As a result the following will show up :
ip-address 192.168.0.10;
subnet-mask 255.255.255.0;
¾ To configure a cell:
At the B
The Tracking Area (TA) is a logical concept that involves an area in which the user
can move around without having to update the MME. The network allocates a list to
the user that contains one or more TAs. In certain operation modes, the UE can move
around freely in all of the TAs on the list, without updating the MME.
Each eNodeB broadcasts a special tracking area code (TAC) to indicate to which TA
the eNodeB belongs. This TAC is unique within a PLMN. Because the PLMN is a
unique number allocated to each system operator and because the TAC is unique
within a PLMN, if you combine these two numbers, you have a globally unique
number. This number (PLMN + TAC) is called the Tracking Area Identity (TAI).
This parameter must match the TAC on the EPC. When using BreezeWay2020, use
TAC=1 as the default.
following commands:
prompt, configure cell parameters by entering the
The same PLMN ID value must be configured in both the EPC and the eNB. The eNB
BreezeCOMPACT can support multiple PLMN IDs working with different EPCs (in
multi-service networks, RAN sharing scenarios and so on).
Page 77
BreezeCOMPACT System Manual
77
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
Macro eNB ID
local cell ID
23 set cell ran-common enb-identity <eNB Identity>
24 set cell1 general cell-identity <<Cell ID>
25 set cell ran-common cell-radius <Cell Radius in KM>
cell-radius
26 set cell ran-common eNB-name<ENB name>
27 show cell ran-common
It is possible to use different PLMN IDs for a SIM card (Home PLMN ID) and for
the network (PLMN ID configured in an eNB/EPC and broadcast over the air). In
this case, the UE is in
ECGI Setting:
The following parameters enable the operator to define a unique ECGI:
An eNB is a base station, which can have multiple cells (sector/carriers), each
with its own cell ID.
The BreezeCOMPACT BS type is a Macro BS (Macro eNB). A Macro eNB can
include multiple cells.
The global identity of the cell (ECGI) is 28 bits, where 20 MSBs refer to the Macro
eNB identity and the last eight bits (LSBs) refer to the
eNB.
In order for the MME to distinguish between two eNBs, the 20 MSBs for the two eNBs
should be different. If an eNB has multiple cells/sectors, the 20 MSBs must be the same
for these cells/sectors, and the eight LSBs should be different. To ensure that this is the
case, each BreezeCOMPACT has two configurable parameters: the eNB identifier (20
bits) and the local cell identifier (eight bits). Together, they define a unique ECGI.
The ECGI ID contains 28 bits, and consists of the M
ECGI ID displays on the UE. The ECGI ID is determined, as follows:
eNB-identity * 256 + cell-identity.
If the operator does not have multi-sector/multi-carrier functionality, the operator can
leave the local cell ID’s default value (for example, 1),
a unique value.
This parameter must be unique on the network. It specifies the Global eNB ID for the
Macro eNB ID (20 bits).
Roaming
mode for the network.
and configure only the eNB ID as
local
cell ID inside the
and l
. The
This is the Local Cell ID for the Macro eNodeB ID. The default can be 1.
This parameter defines the maximum cell radius, in kilometers. The eNodeB determines
the cell radius according to the received RACH code. RACH codes exceeding the c
parameter are rejected and the UE cannot attach. This value must not exceed the
maximum allowed distance for the Special Subframe (SSF) configuration.
In this parameter there is a possibility to define a name to this ENB that will be
populated in the S1-MME interface.
Note: the name should not contain space.
In order to show the configuration done run the following command from
BreezeCompact% prompt in ENB :
As a result you should see an output similar to as follows:
enb-identity 1;
enb-name "eNB";
cell-radius 39;
In general, the special sub frame (SSF) configuration determines the gap required
between the DL path and the UL path. It is primarily used to supported different cell
Page 78
BreezeCOMPACT System Manual
78
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
SpecialSubframeCfg
Table 3-1: SSF Settings
Cell Radius (Km)
SpecialSubframeCfg
1 =< R <= 10
0 to 3, 7
11 =< R <= 20
0 to 2
21 =< R <= 30
0 to 1
31 =< R <= 39
0
39 =< R <= 60
0
28 set cell ran-rf bandwidth << Bandwidth allocated for the cell in MHZ >
29 set cell1 general central-frequency
30 set cell1 general phy-cell-id <<Physical Cell ID>
31 set cell ran-rf tx-power <TX Power; Maximum allowed TX power to
MAX-10Dbm>
32 set cell1 general central-frequency-f2 <<f2 frequency in MHZ>
radiuses, UL sounding and special RACH capabilities. Table 3-1 describes the
relationship between the SSF setting, as set in QoS >scheduler>special-subframe-Cfg.
When the S
value matches the Cell Radius value, as described in Table 3-1.
parameter is configured, verify that the configured
Here the value of the bandwith of the cell should be set in MHz units. Possible
values are 5,10,15,20 .
The supported resolution is XXXX
This parameter sets the central frequency of the LTE bandwidth. You must set the
central frequency within the limits specified by the Device Frequency and Bandwidth
that are currently set. For example: set cell ran-rf central-frequency
.123
3510
The Physical Cell ID sets the physical (PHY) layer Cell ID. This PHY-layer Cell ID
determines the Cell ID Group and Cell ID Sector. There are 168 possible Cell ID
groups and three possible Cell ID sectors. Therefore, there are 3 * 168 = 504 possible
PHY-layer cell IDs.
The PHY Cell ID can be calculated using the following formula:
PHY-layer Cell ID = 3 * (Cell ID Group) + Cell ID Sector
The selected PHY Cell ID should be part of the radio network planning (RNP) and
should be planned carefully.
<Central frequency, in MHz>
.XXX MHz.
This parameter sets the power that the eNodeB can transmit. The maximum power is
determined during eNodeB power up and is recognized by the type of radio head inside
the BreezeCOMPACT. The permitted power range is between 1dBm and the
maximum power allowed for the radio head type.
This is required to be configured in case that the deployment topology is set to
SplitModef1f2
Rotem – Please confirm the above change is correct (Confirm)
In order to show the configuration related to this ran-rf run the following command from
BreezeCompact% prompt in ENB :
Page 79
BreezeCOMPACT System Manual
79
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
33 show cell ran-rf
34
35 Set cell SFR configuration:
3.3.2.11 Configuring eNodeB Timing and GPS
BreezeCompact%
36 set timing chain-mode
If the GPS is connected directly to the eNodeB, define the chain mode as
MASTER. If it is chained to another eNodeB, define the chain mode as
SLAVE.
37 set timing gps-type
38 set timing ntp-ip-address
ntp-ip-address
39 set timing time-zone-params TZP area <Customer area> city <Customer City>
40 set timing gps-enable-disable
41 show timing
As a result the out should look like below :
bandwidth 5MHz;
tx-power 20;
show cell1 general
As a result the out should look like below :
cell-identity 1;
central-frequency 3510.0;
phy-cell-id 1;
This is the prameter for using Soft Frequncy Reuse (SFR) in case of Reuse 1 deployments
where nearby cells operate in the same freuqcy.
¾ To configure eNodeB Timing and GPS:
More information about GPS capabilities are described in section 1.5.7 GPS
At the B
The permitted types are Origin or Trimble. The value depends on the GPS hardware.
Trimble GPS PNs : 700250/700258 BMAX-4M-GPS
Origin GPS PN : 700275 BreezeGPS
is not functioning>
When the eNodeB starts, it looks for GPS in order to obtain the PPS and time. When it
fails to retrieve or work with the GPS, it gets the time from the NTP server. The NTP
server list is an internal list and includes all known public NTP servers. The operator
can define a specific NTP IP address to be used by using the n
The NTP time is used for logs and event time marking for maintenance and debugging
purposes.
The time-zone offset modifies the time received by the GPS or NTP, in order to be aligned
with the local time.
It is possible to disable the need of GPS before enabling the RF chain.
In order to show the current GPS related configuration run the following command
from the BreezeCompact% prompt :
commands:
<Master or Slave>
<GPS Type>
<Dedicated NTP Server IP address for time setting in case GPS
prompt, configure the GPS by entering the following
<Enable/Disable>
parameter.
Page 80
BreezeCOMPACT System Manual
80
Chapter 3: Operation and Administration
Procedures
Configuration via CLI
42 set timing hold-over-passed-operation <true or false>
3.3.2.12 Configuring Quality of Service Parameters
As a result the output should look like that :
time-zone-params TZP {
area Custom;
city GMT+0300;
Defines whether to stop transmitting after Hold Over Timeout.
}
BreezeCOMPACT Full
In this section, you define the QoS for the external management VLAN, including the control
plane (DATA Bearer infrastructure) VLAN and the User DATA QoS parameters per QCI.
These commands should be running from BreezeCompact% prompt:
set qos general s1-mme-dscp-value< s1 Bearer DSCP marking > Value should be
between 0-63
set qos general mng-dscp-value<management QoS DSCP markup> Value should
be between 0-63 .
set qos general mng-802.1p <Management QoS 802.1p Priority on management>
Values should be between 0-7 .7 is the highest priority and 0 is the lowest .
set qos general s1-mme-802.1p < S1 - MME 802.1p Priority > Values should be
between 0-7.
In order to show the current general QOS related configuration run the following command
from the BreezeCompact% prompt:
show qos general
As a result the output should look like that :
mng-dscp-value 8;
mng-802.1p 1;
s1-mme-dscp-value 48;
s1-mme-802.1p 6;
Below are CLI commands from ENB BreezeCompact% regarding the classified 9 possible level
:
set qos s1-u-qos-list <QCI 1-9> 8021p-marking <802.1 marking value for this
QCI> . Marking of possible vlan tag between 0-7 for s1-u packets on 802.1 layer
belongs to a specific QCI level.
set qos s1-u-qos-list <QCI 1-9> dscp-marking <dscp marking value for this QCI> .
Marking of possible levels between 0-64 for s1-u packets on dscp layer belongs to a specific
QCI level.
set qos s1-u-qos-list <QCI 1-9> priority <Priority given> .
Marking of possible levels between 1-9. By this command it is possible to change the priority
associated with this QCI for s1 traffic .
Page 81
BreezeCOMPACT System Manual
81
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
Telrad recommends to keep the QCI priority default settings, as changing them
may affect system QoS behavior. Contact Telrad Support for assistance if you need
to update the QCI table.
The following describes how to adapt QCI settings:
In order to show the current QOS s1-u-qis-list in the ENB perform the following command
from CLI BreezeCompact% prompt:
show qos s1-u-qos-list
As a result the output should look like that :
s1-u-qos-list 1 {
priority 2;
dscp-marking 0;
}
s1-u-qos-list 2 {
priority 4;
dscp-marking 0;
}
s1-u-qos-list 3 {
priority 3;
dscp-marking 0;
}
s1-u-qos-list 4 {
priority 5;
dscp-marking 0;
}
s1-u-qos-list 5 {
priority 1;
dscp-marking 0;
}
s1-u-qos-list 6 {
priority 6;
dscp-marking 0;
}
Page 82
BreezeCOMPACT System Manual
82
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
Downlink MCS
Uplink MCS
No protection
n/a
n/a
Level 1 protection
3
6
Level 2 protection
9
10
s1-u-qos-list 7 {
priority 7;
dscp-marking 0;
}
s1-u-qos-list 8 {
priority 8;
dscp-marking 0;
}
s1-u-qos-list 9 {
priority 9;
dscp-marking 0;
}
Configuring uncommitted scheduler type:
set qos scheduler dl-uncommit-scheduler <EqualRate or EqualTime>
By this command it is possible to set what will be the fairness mechanism for user data
traffic to the UE's for data coming on the downlink direction.
set qos scheduler ul-uncommit-scheduler <EqualRate or EqualTime>
By this command it is possible to set what will be the fairness mechanism for user data
traffic to the UE's for data coming on the uplink direction.
Note that Equal Rate is applied automaticaly for the commited portion (GBR), where the
uncommit type configured in this command is related to MBR/AMBR which is the
uncommited service.
Configuring weak UE scheduling protection level:
In general, when working with Equal Rate or Equal Time (with mutliple QCIs),
weak UEs (low MCS) may consumes most of the sector air resources. As a result,
the sector throughput degrades dramatically. In order to limit the canalization of
resources by these weak UEs, three configurable levels for DL and UL defines if
the UE is considered weak or not – NoProtection, Level1Protection and
Level2Protection.
set qos scheduler weak-ue-protection < Level1Protection or Level2Protection or
NoProtection >
UE is considered as weak UE when it equal or below the defined MCS
(Modulation) :
This option defines the level of protection of the system utilization resources . The threshold
of each level are configurable on the vendor level.
Page 83
BreezeCOMPACT System Manual
83
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
3.3.2.13 Configuring Handovers
Figure 47: Handover A5 Events
In order to show the current QOS scheduler related parameters in the ENB perform the
following command from CLI BreezeCompact% prompt:
show qos scheduler
As a result the output should look like that :
ul-uncommit-scheduler EqualTime;
dl-uncommit-scheduler EqualTime;
weak-ue-protection Level1Protection;
Configuration:
set qos scheduler weak-ue-protection
Possible completions: Level1Protection, Level2Protection, NoProtection
set qos scheduler weak-ue-protection Level1Protection dl-uncommit-scheduler
(EqualRate/EqualTime)
set qos scheduler weak-ue-protection Level1Protection ul- uncommit-scheduler
(EqualRate/EqualTime)
The BreezeCOMPACT supports handovers (HOs) with an A5 and A3 trigger that supports the
LTE X2 protocol.
An A5 HO event triggers when UE RF conditions to the serving BS RF become worse than the
provisioned value (Threshold 1) and the Neighbor BS becomes better than the provisioned
value (Threshold 2).
Figure describes A5 HO events. The service BS’s Serving (S-cell) is shown in blue and the
Neighbor cell (n-cell) is shown in red.
TheA5 trigger is triggered on the RSRP levels.
Each neighbor cell is identified by its frequency (EARFCN), eNB ID, physical cell ID and X2 IP
address (the Bearer IP address of the eNB in the BreezeCOMPACT).
Page 84
BreezeCOMPACT System Manual
84
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
Figure 48: Handover A3 Events
To set the HO triggers, you define the measurement type and thresholds for the A5 triggers
using the following commands:
set cell handover-triggers measurement-type <RSRP or RSRQ>
Sets the way how the measurement will be prformed (based on RSRP or RSRQ)
set cell handover-triggers a5-threshold1-rsrp <Defines the RSRP level for
threshold 1>
Specifies the Threshold 1 value used in an E-UTRA measurement-report triggering
condition for the A5 (dBm) RSRP event.
set cell handover-triggers a5-threshold1-rsrq<Defines the RSRQ level for
threshold 1>
Specifies the Threshold 1 value used in an E-UTRA measurement-report triggering
condition for the A5 (dB) RSRQ event.
set cell handover-triggers a5-threshold2-rsrp <Defines the RSRP level for
threshold 2>
Specifies the Threshold 2 value used in an E-UTRA measurement-report triggering
condition for the A5 (dBm) RSRP event.
In order to show the current handover trigers related parameters in the ENB perform the
following command from CLI BreezeCompact% prompt:
show cell handover-triggers
As a result the output should look like that :
measurement-type RSRP; a5-threshold1-rsrp -140;
a5-threshold2-rsrp -140;
a5-threshold1-rsrq -20;
a5-threshold2-rsrq -20;
An A3 HO event basic form the UE sends an A3 measurement report when a non-serving
cell RSRP becomes better than the serving cell RSRP by a margin defined by an A3 offset
parameter. (A3-OFFSET parameter units is 0.5db)
In other words, when ∆RSRP > A3 offset,
where ∆RSRP = RSRPneigh − RSRPserv.
Figure below shows an example of the A3 reporting event.
Page 85
BreezeCOMPACT System Manual
85
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
To change the handover event to A3 use the following command:
set cell handover-triggers trigger-type A3
To set the HO triggers, define A3 offset value using the following commands:set
cell handover-triggers a3-offset <offset value>
In order to show the current handover trigers related parameters in the ENB perform the
following command from CLI BreezeCompact%: prompt:
show cell handover-triggers
As a result the output should look like that :
trigger-type A3;
a2-threshold-rsrp -140;
a3-offset 6;
To set the neighbors that participate in the X2 HO process, you must define the neighbor list.
The operator should define parallel definitions in the neighbor cell:
set cell1 neighbor-list-cell <Cell ID> <eNodeB ID> black-listed <true or false>
Indicates whether or not this neighbor cell is allowed as a handover target for UEs (true
– enabled false-not enabled).
set cell1 neighbor-list-cell <Cell ID> <eNodeB ID> cio < offset>
Specifies the individual cell offset that applies to a specific neighboring cell. This value is in
dB with an offset of 15, which means that the configuration of the parameter with a value of
15 is equal to 0dB.
set cell1 neighbor-list-cell <Cell ID> <eNodeB ID> eutra-carrier-arfcn <ARFCN>
Specifies the ARFCN of the neighbor carrier frequency.
set cell1 neighbor-list-cell <Cell ID> <eNodeB ID> neighbor-ip-address <X2 of
Neighbor IP Address>
Sets the neighbor X2 IP for signaling.
set cell1 neighbor-list-cell <Cell ID> <eNodeB ID> phy-cell-id <physical-cell-id>
Specifies the neighbor physical cell ID.
set cell1 neighbor-list-cell <Cell ID> <eNodeB ID> qoffset <qoffset>
Specifies the cell-specific offset that applies to a specific neighboring cell. This value is in dB
with an offset of 15, which means that the configuration of the parameter with a value of 15
is equal to 0dB.
set cell1 neighbor-list-cell <Cell ID> <eNodeB ID> rx-tx-power <RS Tx power in
DB>
Specifies the downlink reference-signal transmit power.
Page 86
BreezeCOMPACT System Manual
86
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
3.3.2.14 Applying Parameter Changes
3.3.3 Stop/Start all RH ports transmitting from BreezeVIEW
CLI
request devices device <device ID> live-status cell-actions-transmission stop-transmission cellidentity <Cell ID>
request devices device <device ID> live-status cell-actions-transmission start-transmission celliden
tity <Cell ID>
Apply and activate the configuration by performing commit procedure in 3.1
¾ 4 In order to show the current cell neighbor list related
parameters in the ENB perform the following command from CLI
BreezeCompact% prompt :
show cell neighbor-list-cell
As a result the output should look like that :
neighbor-list-cell 1 1 {
eutra-carrier-arfcn 42590;
phy-cell-id 1;
qoffset 1;
cio 1;
rx-tx-power 15; black-listed false;
neighbor-ip-address 172.16.1.23;
}
neighbor-list-cell 1 2 {
eutra-carrier-arfcn 42591;
phy-cell-id 2;
qoffset 14;
cio 0;
rx-tx-power 22; black-listed false;
neighbor-ip-address 172.16.2.5;
}
Open BreezeVIEW CLI and perform the following command to stop transmission
for the cell :
To start transmission of all 4 ports perform the following command
Command help:
start-transmission - Start Transmission of a selected Cell
stop-transmission - Stop Transmission of a selected Cell
Cell ID – perform operation on the specific cell ID (carrier)
Page 87
BreezeCOMPACT System Manual
87
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
3.3.4 Enhanced log collection
request usage upload-logs-files destination-ip-address <IP address> destination-path
<destination pat
h>
3.3.5 Configuration of backup & restore to external TFTP
3.3.5.1 Create and Save (backup) the configuration file on TFTP
server.
request config-file create-config-file
yes
show notification stream alarm
request config-file upload-config-file destination-ip-address <IP address> destination-path
<destinat
ion path>
show notification stream alarm
3.3.5.2 Download and Restore (restore) the configuration file from
TFTP server.
request config-file upload-config-file destination-ip-address <IP Address> destination-path
<destination path>
yes
Enhanced log Collection located at tmp and in case of reset /mnt/flashes/ backup (only in case
of eNB reset)
To upload log files to TFTP server use the following command:
To create configuration file:
This action will create a configuration file,
which later can be uploaded to an external TFTP server.
Are You sure? [no,yes]
Status Success
Check in system events that create-config-file-completed by command:
Upload configuration file to external TFTP server by command:
Check in system events that upload-config-file-completed by command:
To upload configuration file:
This action will upload device configuration file to an external tFTP server.
Are You sure? [no,yes] y
Page 88
BreezeCOMPACT System Manual
88
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
show notification stream alarm
request config-file restore-config-file
yes
show notification stream alarm
request reboot reboot
3.3.6 Configuring Via BreezeVIEW
1
admin
2
3
Figure 49: Device Information
4
Check in system events that upload-config-file-completed by command:
Restore configuration file
This action will load (restore)the configuration file from the disk and replace the database.
Are You sure? [no,yes] y
Check in system events that restore-config-file-completed by command:
Reboot eNB to apply changes
The following describes how to perform a full configuration via BreezeVIEW.
¾ To configure via Breez eVIEW :
Access BreezeVIEW as a
In the device list, select the number of the device to be edited.
Define the device’s general information, as shown below.
.
Define the device’s management information, as shown in above.
Page 89
BreezeCOMPACT System Manual
89
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
5
Figure 50: Device Capability
Figure 51: Device Capability
6
Figure 52: Device Networking Information
7
Use Bearer Interface as External
Management
Figure 53: External Management Interface − 1
Use Bearer Interface as External
Management
Define the device’s antenna topology information, as shown below.
Also you can define here the Frame structure sub frame assignment as well as the special
sub frame pattern.
Define the device’s networking information, as shown in Figure .
If the system is operating in Unified mode, check the U
checkbox.
If the system is operating in Inband mode, uncheck the U
checkbox:
Page 90
BreezeCOMPACT System Manual
90
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
Figure 54: External Management Interface − 2
8
TAC
Figure 55: Cell Configuration
Part of the parameters such as: Cell ID, Central Frequency and Physical
Cell ID are now
under Cell1 (please refer to the picture below)
9
Trigger Quantity
RSRP
Figure 56: Handover Configuration –A5
Define the cell configuration by:
43 Adding the PLMNID to the PLMN Identity List.
44 Setting the RAN Common parameters,
45 Setting the RAN RF parameters.
46 Setting the cell’s T
value.
Define HOs using the BreezeVIEW GUI by:
47 Defining the handover A5 triggers in the cell.
48 Defining the T
49 Defining the A5 thresholds for Trigger 1 and Trigger 2.
as R
.
Page 91
BreezeCOMPACT System Manual
91
Chapter 3: Operation and Administration
Procedures
Configuration via CLI
Figure 57: Handover Configuration –A3
10
Figure 58: Neighbor Cells List Configuration
11
50 Choose A3 triggers in the cell.
51 Defining A2 threshould and A3 offset
Define the Neighbor Cells List by:
BreezeCOMPACT Full
52 Defining the neighbor list sectors.
53 Defining the neighbor eNB ID.
54 Defining the neighbor EARFCN (central frequency).
55 Defining the neighbor physical cell ID (PCI).
56 Defining neighbor offsets.
57 Defining the neighbor reference signal maximum power.
58 Defining the neighbor X2 IP (is the same as the Neighbor Bearer IP address for
BreezeCOMPACT).
Define QoS parameters by:
59 Configuring Scheduler parameters.
60 Defining Networking QoS.
61 Defining the QCI index’s QoS parameter.
Page 92
BreezeCOMPACT System Manual
92
Chapter 3: Operation and Administration
Procedures
BreezeCOMPACT Full Configuration via CLI
Figure 59: QoS Configuration − 1
12
Figure 60: Timing Configuration
13
Figure61: Confirm Save
14
OK
15
Actions
Reset
Define timing parameters by:
62 Setting the GPS configuration. If the BreezeCOMPACT is a GPS Slave, set the GPS
Master/Slave field to Slave
63 Setting of the GPS Type :
a. Trimble GPS PNs : 700250/700258 BMAX-4M-GPS
b. Origin GPS PN : 700275 BreezeGPS
64 . Setting the NTP IP Address. It is possible to set more than 1 IP address as
NTPThesystem will use the NTP as a backup only to the GPS.
Click the button.
The following window displays:
Click O
In the A
to confirm.
menu, reset the device by selecting R
to Factory Defaults.
Page 93
BreezeCOMPACT System Manual
93
Chapter 3: Operation and Administration
Procedures
Software Upgrade Via SSH
Figure 62: Actions Menu − Reset to Factory Defaults
Figure 63: Reset Device
16
3.4 Software Upgrade Via SSH
3.4.1 Purpose
3.4.2
Procedure
The following window displays:
It provides the opportunity to make a reset "Now" or "Schedule" it on some day and hour.
17. Click Ok to reset the device and complete the configuration.
This procedure describes how to upgrade LTE software using CLI commands.
Upgrading LTE software via SSH involves performing the following steps using the CLI:
Page 94
BreezeCOMPACT System Manual
94
Chapter 3: Operation and Administration
Procedures
SSH
Preparing the TFTP Server,
Configuring the TFTP Server,
Copying the BreezeCOMPACT Software to the TFTP
Loading a New Software Version to the Backup
Resetting the BreezeCOMPACT from the Backup Bank,
Setting the BreezeCOMPACT Version in the Backup Bank as the Main
,
3.4.2.1 Preparing the TFTP Server
3.4.2.2 Configuring the TFTP Server
1
BreezeCompact%
2
3.4.2.3 Copying the BreezeCOMPACT Software to the TFTP Server
1
TFTP
2
/opt/lte/Data/FirmwareSW/ENB
3.4.2.4 Loading a New Software Version to the Backup Bank
1
BreezeCompact>
request software-upgrade load-to-backup file-name
“compact version
This action will download the software image from the TFTP server. Are You sure?
[no,yes]
2
yes
Software Upgrade Via
Version
page 95
page 94
¾ To prepare the T FTP server:
Set the TFTP server on BreezeVIEW. Refer to the
Configuration
section in the
¾ To set the TFTP server in the CLI:
page 94
Server, page 94
Bank, page 94
page 95
TFTP Server Installation and
BreezeVIEW Installation Manual
Software
for details.
At the B
65 set device management tftp-ip-address <TFTP IP Address- Breeze View IP>
Perform the commit procedure as per 3.1.
prompt, enter the following command:
¾ To copy the BreezeCOMPACT sof tware t o the TFTP server:
Copy the new BreezeCOMPACT software version to the T
When using BreezeVIEW as the TFTP server, copy the new BreezeCOMPACT version
using an SFTP program (such as FileZilla) to the eNodeB software version directory
(/
).
directory.
¾ To load a new software version to the backup bank (shadow):
At the B
For example, COMPACT0608B.05643
The following displays:
prompt, type r
(including extension)””.
Type y
.
Page 95
BreezeCOMPACT System Manual
95
Chapter 3: Operation and Administration
Procedures
Software Upgrade Via SSH
3
3.4.2.5 Resetting the BreezeCOMPACT from the Backup Bank
1
BreezeCompact>
request software-upgrade reset-from-backup
The reset will disrupt all services provided by the device. The device will come up with the
backup v
ersion. Are You sure? [no,yes]
2
yes
3
show status device
BreezeCompact>
Wait until the new version appears in the back-up-sw version, as shown below:
BreezeCOMPACT1000>show device
device general product-type COMPACT
device general product-subtype ENB
device general compact-model-type BreezeCompact1000
device inventory hw-ver 002-001-00
device inventory serial-number 95009785
device inventory main-sw-ver 0609.07358
device inventory backup-sw-ver 0609.07395
device inventory running-sw MainSW
device inventory boot-ver 0608.03.00045
device inventory up-time 2018-02-19T14:19:54+00:00
device inventory temperature 40
The following procedure describes how to reset the eNodeB from the backup bank in order to
load the eNodeB software version from a backup.
¾ To reset the eNodeB from the backup bank:
At the B
following message displays:
Type y
After the eNodeB is up, type s
.
The line highlighted in yellow below shows the current software version.
BreezeCOMPACT1000>show device
device general product-type COMPACT
device general product-subtype ENB
device general compact-model-type BreezeCompact1000
device inventory hw-ver 002-001-00
device inventory serial-number 95009785
device inventory main-sw-ver 0609.07395
device inventory backup-sw-ver 0609.07358
device inventory running-sw ShadowSW
device inventory boot-ver 0608.03.00045
device inventory up-time 2018-02-19T14:19:54+00:00
device inventory temperature 40
prompt, type r
at the B
prompt:
. The
Page 96
BreezeCOMPACT System Manual
96
Chapter 3: Operation and Administration
Procedures
Software Upgrade Via BreezeVIEW
3.4.2.6 Setting the BreezeCOMPACT Version in the Backup Bank as
the Main Software Version
1
BreezeCompact>
BreezeCompact> request software-upgrade set-backup-as-main
This action will set the backup software image as Main. Are You sure? [no,yes]
2
yes
3
3.5 Software Upgrade Via BreezeVIEW
3.5.1 Purpose
3.5.2 Procedure
Configuring TFTP as the BreezeVIEW IP
Copying the BreezeCOMPACT Software to the TFTP
Uploading the Software to a
Running the Software from a Backup
Setting the Backup as the Main
The following procedure describes how to set the BreezeCOMPACT backup software version as
the Main software version.
¾ To set the backup version as the main software version:
At the B
Type y
Check the status by typing the following:
The following message displays:
.
BreezeCOMPACT1000>show device
device general product-type COMPACT
device general product-subtype ENB
device general compact-model-type BreezeCompact1000
device inventory hw-ver 002-001-00
device inventory serial-number 95009785
device inventory main-sw-ver 0609.07395
device inventory backup-sw-ver 0609.07358
device inventory running-sw MainSW
device inventory boot-ver 0608.03.00045
device inventory up-time 2018-02-19T14:19:54+00:00
prompt, type the following:
device inventory temperature 40
This procedure describes how to upgrade LTE BreezeCOMPACT software using BreezeVIEW.
Upgrading LTE software via BreezeVIEW involves performing the following steps:
Backup, page 97
Version, page 101
Address, page 97
Server, page 97
Version, page 99
Page 97
BreezeCOMPACT System Manual
97
Chapter 3: Operation and Administration
Procedures
Software Upgrade Via BreezeVIEW
3.5.2.1 Configuring TFTP as the BreezeVIEW IP Address
Figure 64: TFTP Server IP Address
3.5.2.2 Copying the BreezeCOMPACT Software to the TFTP Server
1
TFTP
2
/opt/lte/Data/FirmwareSW/ENB
3.5.2.3 Uploading the Software to a Backup
1
SW Upgrade
Load SW File To Backup
Figure 65: Actions Menu – Load SW File To Backup
The TFTP configuration should be installed on BreezeVIEW in order to enable it to act as the
TFTP server. For details describing how to configure BreezeVIEW as the TFTP server, refer to
TFTP Server Installation and Configuration
the
Manual.
Configure the TFTP IP address in BREEZEVIEW->home->devices->ENB->General tab with
the TFTP IP address.
section in the
BreezeVIEW Installation
¾ To copy the BreezeCOMPACT softw are version t o the TFT P server:
Copy the new BreezeCOMPACT software version to the T
In case that using BreezeVIEW as the TFTP server, copy the new BreezeCOMPACT
version using an SFTP program (such as FileZilla) to the eNodeB software version
directory (/
).
¾ To upload software to a backup:
In the S
select
The
Load SW File to Backup
dropdown menu of the
.
window opens.
Device
directory.
window or the
Device Details
window,
Confirm that the device is selected in the device list.
Page 98
BreezeCOMPACT System Manual
98
Chapter 3: Operation and Administration
Procedures
Software Upgrade Via BreezeVIEW
2
Select Backup SW File
3
Figure 66: Load SW File to Backup Main Window
4
Figure 67: Warning − Load to Backup
5
Yes
In Process
Status
Figure 68: Ongoing Task − Load to Backup SW Version
6
Success
Status
Select the correct software version file in the S
Click OOK. The following displays:
The following window displays:
list.
Click Y
column, as shown below:
Wait until the ongoing task displays S
. The
Ongoing
window displays. The last action shows I
in the
column, as shown below:
in the S
Page 99
BreezeCOMPACT System Manual
99
Chapter 3: Operation and Administration
Procedures
Software Upgrade Via BreezeVIEW
Figure 69: Ongoing Task
Successful
Figure 70: Device Details Window – Backup SW Version
3.5.2.4 Running the Software from a Backup Version
1
SW Upgrade
Run SW From Backup
Figure 71: SW Upgrade Menu – Run SW From Backup
2
Figure 72: Run SW from Backup Window
−
The new version displays in the
Device Details
window, as shown below:
¾ To run LTE software from a backup:
In the S
menu, select R
.
Select the device in the Select Devices area in the
Run SW From Backup
window.
Page 100
BreezeCOMPACT System Manual
100
Chapter 3: Operation and Administration
Procedures
Software Upgrade Via BreezeVIEW
3
Figure 73: Warning − Run SW from Backup
4
Yes
In Process
Status
Figure 74: Ongoing Task − Run SW from Backup − In Process
5
In Process
Success
Status
Figure 75: Ongoing Task
Run SW from Backup − Success
Click OOK. The following window displays:
Click Y
The eNodeB resets. The
task with the
.
Ongoing
window redisplays showing the Run SW from Backup
status in the S
column, as shown below:
After the connection resumes, check the status and verify that the running version is from
the backup bank. Wait until the I
status changes to S
in the S
column, as shown below:
−
Loading...