01 FT43131EN01GLN0 Flexihopper Overview

Cellular transmission solutions
for coverage and capacity
Nokia FlexiHopper (Plus)

Product Overview
Nokia Siemens Networks
Objectives
After completing this learning element, the participant will be
able to:
Describe the main features and functions of FlexiHopper (Plus)
radios
List the different types of indoor units commonly used with the
FlexiHopper (Plus) outdoor unit, and describe their main
characteristics
Describe the different site configurations available with
FlexiHopper (Plus)
Describe the various protection methods available with
FlexiHopper (Plus)
Describe the management options available for FlexiHopper (Plus)
FlexiHopper (Plus) features

FlexiHopper (Plus) Product Overview
Nokia FlexiHopper radios

What is Nokia FlexiHopper?
One of the most advanced point-to-point PDH Microwave Radios
available
Complete and compatible family of products for 738 GHz range
All traffic capacities 2x2 16x2 Mbit/s without HW changes
Dual modulation modes: 4-state or 16-state modulation
All market standard features plus many unique ones (integration into
Nokia 2G/3G BTS, software selectable transmission capacity, software
selectable modulation mode, automatic Fading Margin measurement)
FlexiHopper radio
with 30-cm antenna
FlexiHopper radio family

FlexiHopper radios come in 3 different models,
which are available in all frequency bands
FlexiHopper 4E1 provides 2E1 or 4E1 transmission capacity in 4-state modulation mode
FlexiHopper provides 2E1 to 16E1 capacity
with 4-state modulation
FlexiHopper Plus offers 2E1 to 16E1 capacity
with selectable modulation (4-state or 16-state)
Collectively, the 3 models are refered to as FlexiHopper (Plus)
One model can be upgraded to a higher model by software licensing
For example, FlexiHopper 4E1 can be upgraded to FlexiHopper Plus

remotely, without any hardware changes simply by downloading extra
capacity licenses and a modulation license
FlexiHopper features (1)

One platform all frequencies
7, 8, 13, 15, 18, 23, 26, 28, 32 and 38 GHz
All as 1+0 or as 1+1 with HSB, space diversity
or frequency diversity protection
One unit all capacities
2x2 16x2 Mbit/s radio transmission
Programmable capacity selectable with the
element manager
Integrated 2M-level cross-connections
Dual modulation modes
4-state or 16-state modulation selectable
with the element manager
16-state modulation doubles the spectrum
efficiency channel bandwidth is only half
as large as with 4-state modulation
Dual modulation modes

FlexiHopper radios support both 4-state and 16-state modulation
4-state modulation is /4-DQPSK (differential quadrature phase shift keying)
16-state modulation is 32-TCM (Trellis coded modulation)
16-state modulation is an optional feature it enables doubling the
transmission capacity in the same bandwidth as 4-state modulation
16-state modulation provides a capacity upgrade while maintaining the
same bandwidth to save frequency spectrum
Modulation
Channel
bandwidth
(MHz)
4-state
3.5
2 x 2M
4 x 2M
8 x 2M
14
8 x 2M
16 x 2M
28
16 x 2M
16-state
Note that 16-state

modulation
operates only at
8x2M and 16x2M
capacities

Flexbus single cable interconnections
Indoor unit outdoor unit
Indoor unit indoor unit
One indoor unit supports multiple outdoor units
Many different indoor unit types, both stand-alone
and integrated into Nokia 2G/3G BTS
Flexbus also supplies DC power to outdoor unit
Antennas integrated or separate
Integrated 20/30/60 cm low-profile antennas
Integrated 90/120/180 cm antennas with snap-on
adapter
Separate 240/300 cm antennas with waveguide
Both vertical and horizontal polarization possible
Flexbus single-cable interconnections

Flexbus provides a common
interface between all indoor
units and outdoor units
TNC 50 connections
RG-223 cable max 140 m
RG-214 cable max 300 m
New CNT-400 cable
up to 380 m

Useful/innovative software features
Tx power adjustable with software dynamic range up to
28 dB
Built-in Rx level measurement
Built-in automatic Fading Margin measurement
Automatic Transmit Power Control (ATPC)
Adaptive Level Control with Quality measure (ALCQ)
more sophisticated Nokia-patented version of ATPC
Automated configuration backup between IU and OUs
Updating OU and IU software using either local or remote
software download
Upgrading radio capacity or modulation mode with local or
remote download of SW license keys
Optional auxiliary data channels
Optional Ethernet data channels
SNMP management option for IP-based DCN
OSPF routing option with IP-based management
10
Integrated radio and 2M cross-connect
11

Error protection
Forward error correction (FEC):
redundancy bit error correction
Selectable interleaving (off, 2-depth, 4-depth):
interleaving burst errors to bit errors
Scrambling polynomial for reducing interference
Protection methods
Hot standby (HSB) provides equipment
protection only
Frequency, Space, Polarization diversities
provide some propagation protection as well
Loop protection offers both equipment and
full propagation protection
12

Maintenance and troubleshooting facilities
Monitoring of transmission quality with built-in
BER measurement and ITU-T G.826 statistics
Alarms display provided with detailed alarm
information
Multilevel loopback and test facilities
Configuration backup between indoor and
outdoor units
Node software download
Updating OU and IU software using either
local or remote software download
Upgrading radio capacity or modulation mode
with local or remote download of SW license
keys
13
Outdoor unit
14
Electrical Structure of Outdoor Unit ...1

Power Supply Unit (platform unit)
Modem (platform unit)
embedded microprocessor system

digital signal processing (DSP ASIC)
analog signal processing (Tx and Rx filters and amplifiers)
analog measurements and controls
single-cable (Flexbus) interface, and A/D and D/A converters (two CIAD ASICs)
Intermediate Frequency Unit (IFU)

Microwave Unit (MWU)
one oscillator (VCO) for both Tx and Rx

based mainly on GaAs MMIC (Monolithic Microwave Integrated Circuits)
technology
Waveguide antenna filter (diplexer)

Antennas, and couplers and waveguides for one-antenna HSB
15
Electrical Structure of Outdoor Unit ...2

Transmission
Interface
Line interface
Multiplexing
Cross-connection
NMS
Modem
Radio parts
Frame coding
Modulation method
Capacity/channel
filtering
AD/DA-converters
IQ-modulator/demodulator
(Up/down converting)
Amplification/attenuation
MW filtering
Antenna
C
I
OU
IU
2-16x2M
MUX ASIC
Line
.
Inter. face
.
FlexBus
FlexBus
2M
CI
CI
CI
Power
16
Frame
C
I
micropros
DC/DC
DC/DC
DSP
ASIC
TX
filt.
MIX
LO
LO
LO
RX
filt.
IF
738 GHz
pi/4-QPSK
HPA
Dup
lex
LNA
Ant
Block diagram of Outdoor Unit
17
Mechanical structure of Outdoor Unit

Compact sandwich structure no cables inside
(except antenna filter cables at 7/8 GHz) !!!!
Antenna filter
Heat sink
IFU cover
Modem
MWU IFU
18
Power Supply
Common Indoor units

19
Indoor units
Main characteristics of the Indoor Unit concept include:
Several different indoor unit types
FlexiHopper (Plus)
7-38 GHz, 2-16x2M
Integrated indoor units in Nokia base stations &

MetroHub transmission node
Modular 19-inch stand-alone indoor unit
Flexbus concept
Single-cable IU-OU connections for easy site

configurations
Multiple OUs supported with a single IU
FlexiHopper and MetroHopper radios can share
the same indoor unit
IU-IU interconnections via single cable
Transmission and add/drop capacity separated
16x2Mbit/s transmission capacity with all IU models

Add/drop capacity varies according to IU configuration
Common indoor unit platform
Support for all frequencies

Same IUs for FlexiHopper & MetroHopper radios
20
MetroSite/MetroHubMetroHopper
58 GHz, 4x2M
Indoor unit types
19-inch indoor units

(FIU 19, FIU 19E)
Nokia Talk-family integrated
indoor unit (RRIC)
(NO LONGER AVAILABLE)
Nokia UltraSite/MetroSite/MetroHub
integrated indoor unit (FXC RRI)
Nokia WCDMA UltraSite/MetroSite

integrated indoor unit (IFUE)
21
FIU 19(E) Indoor unit ...1
FIU 19
FIU 19RJ
22
FIU 19(E) Indoor unit ...2
FIU19E
23
FIU 19 Indoor unit
MP:
LMP:
PWR:
-+:
Q1-1, Q1-2:
FB1, FB2:
24
Measurement point interface (SMB connector)

Local management port (BQ connector)
Power switch
Power supply connector (Molex connector)
Q1 network management interface (TQ connector)
Flexbus interfaces 1 and 2 with DC power feed to OU
(50 TNC connector)
FIU 19E SNMP management

FIU 19E indoor unit implements an Ethernet interface for connection
to an IP DCN
It provides an SNMP interface to any NMS system supporting it

Nokia Hopper Manager can be connected remotely to a FIU 19E
using a LAN connection
FIU 19E also supports Ethernet payload traffic via optional Ethernet
plug-in unit (as of release C2.0)
BQ, TQ connectors replaced by RJ-45
25
10BaseT connection for IP-based DCN
19-inch Indoor unit

FIU 19(E) for 19 mechanics or Nokia Extratalk site support cabinet
Supports up to 4 FlexiHoppers and/or MetroHoppers (including one protected

FlexiHopper)
Modular structure (add/drop capacity upgrade, etc.)
Up to 16 x 2Mbit/s add/drop capacity
2Mbit/s cross-connection capability
2/3 U
Plug-in-unit
Plug-in-unitinterface
interfacemodules
modules
4x2M tributaries (75 and 120 )
4x2M tributaries (75 and 120 )
Flexbuses 3 and 4
Flexbuses 3 and 4
Auxiliary data channels
Auxiliary data channels
Ethernet traffic channels (FIU
Ethernet traffic channels (FIU
19E)
19E)
26
FIU 19(E) configuration
27
FIU 19(E) plug-in units 1
FIU 19E C2.0 and later
28
FIU 19(E) plug-in units 2

4x2Mbit/s balanced 120-ohm
4x2Mbit/s balanced 120-ohm 4x2Mbit/s unbalanced 75-ohm
TQ connector
(slots 13)
SMB connector
Flexbus plug-in unit
(slots 13)
Aux Data plug-in unit
RJ45 connector
(slots 13)
Ethernet plug-in
unit
ETH-1 ETH-2
(slot 3
TNC connector
only)
RJ45 connector
Requires separate OU power supply)
29
(slots 13)
(slot 2
only)
(FIU 19E C2.0 and later)
RJ45 connector
Also: 16 x 2Mbit/s Interface Circuit PIU (expansion unit EXU slots A-B)
Aux Data plug-in unit

Aux Data PIU offers 2 Aux Slow and 2 Aux Fast interfaces for transport of auxiliary data
in the overhead channels of the radio signal
Only one Aux Slow channel and one Aux Fast channel in the PIU can be used at the
same time
Only one Aux Slow channel and one Aux Fast channel can be simultaneously connected to the same Flexbus
FIU 19(E) can support two Aux Data PIUs
Units cannot reside simultaneously in slots 2 and 3 must be in slots 1+2 or slots 1+3
Aux Slow channel:
Max. 4800 bit/s at 2 x 2M radio capacity, max. 9600 bit/s at 4 x 2M or higher capacity
V.11 or RS-232 electrical interface, RJ-45 connector
Aux Fast channel:
Max. 64 kbit/s (all radio capacities)
V.11 or G.703 electrical interface, RJ-45 connector
In addition, Aux Data PIU offers 4 programmable I/O channels and/or relay control outputs
(TTL-type connections, each to a single pin on the interface)
An internal alarm can be exported to some external device
An external alarm can be imported to the PIU (for example, an open-door or fire alarm)
Optionally, any channel can operate instead as a user-controlled output (for example,
to turn on equipment rack lights)
30
Engineering order-wire
Engineering order-wire (EOW) can be used for service purposes if mobile phone
coverage is lost or not available at FIU 19(E) site
Nokia T4E Service Telephone (product code TD21652.50) supports EOW
Service Telephone is connected to FIU 19(E) via Aux Data plug-in unit
Supports selective calling from one phone to another or to multiple phones
EOW utilizes Aux Fast channel in the radio overhead for speech and signalling
Refer to Technical Note 67 in NOLS for more information
IP EOW
IP DCN network can be used to carry IP voice calls when Aux Fast channel is used as
a PPP data channel in FIU 19E (see section Management using TCP/IP connection)
Hop LAN PPP link cannot be used to carry voice calls due to its low capacity
Use of IP EOW requires suitable IP phones, as well as configuring FIU 19E into the IP
DCN network
IP EOW available as of FIU 19E C3.0
Aux Data plug-in unit is not needed for this application
Refer to Technical Note 99 in NOLS for more information
31
Ethernet plug-in unit

Ethernet PIU offers 2 Ethernet ports for transport of Ethernet traffic in the radio signal,
as an alternative to E1 traffic
EPIU supports up to two microwave radio links with Ethernet traffic
Up to 32 Mbit/s of radio path capacity can be configured for Ethernet traffic
The capacity of the radio links can also be shared between packet-based Ethernet
traffic and traditional E1 traffic
Ethernet interfaces:
Each 10/100Base-T interface can be configured to work at either 10 or 100 Mbit/s
Each interface can operate in either half-duplex or full-duplex mode
Available radio link capacity in each Flexbus interface can be divided between the E1
signals and the Ethernet channels (with 2 Mbit/s granularity)
The resulting Ethernet capacity can then be allocated to one Ethernet port or divided
up between the two ports
EPIU provides transparent Ethernet bridging over the radio hop
EPIU can be used in the following configurations: single hop, 2OU protected mode,
and 2IU protected mode
EPIU restrictions:
EPIU is only supported by FIU 19E starting with C2.0 HW release (earlier FIU 19E
releases cannot be upgraded to support EPIU)
Only one EPIU can be used, in PIU slot 2 of FIU 19E
32
Flexbus & 2Mbit/s cross-connection

Three
Threeof
ofthe
the2M
2Mcrosscrossconnection
connection
field
fieldedges
edgesare
aremultiplexed
multiplexedto
to
serial
Flexbus
signals
(37
serial Flexbus signals (37
Mbit/s)
Mbit/s)
One
Oneof
ofthe
the2M
connection
field
fieldedges
edgesprovides
providesup
upto
to16
16
xx
2Mbit/s
2Mbit/ssimultaneous
simultaneous
interfaces
interfaces
2M CrossConnection
33
Up
Upto
to16
16xx2Mbit/s
2Mbit/sdata
dataininserial
serialformat
format
to
tooutdoor
outdoorunit
unitor
orto
toanother
anotherindoor
indoor
unit
unit
Flexbus & protection

Three
Threeof
ofthe
the2M
connection
field
fieldedges
edgesare
aremultiplexed
multiplexedto
to
serial
Flexbus
signals
(37
serial Flexbus signals (37
Mbit/s)
Mbit/s)
One
Oneof
ofthe
the2M
connection
field
fieldedges
edgesprovides
providesup
upto
to16
16
xx
2Mbit/s
2Mbit/ssimultaneous
simultaneous
Interfaces
Interfaces
Protection
Protection
switch
switch
2M Cross
Connection
Flexbuses
Flexbuses11and
and22can
can
be
be
configured
configuredfor
for
protection
protection
34
Up
Upto
to16
16xx2Mbit/s
2Mbit/sdata
dataininserial
serialformat
format
to
tooutdoor
outdoorunit
unitor
orto
toanother
anotherindoor
indoor
unit
unit
19 protected Indoor unit
Modular structure enables easy configuration changes

Protected
ProtectedFIU
FIU19(E)
19(E)with
with16
16xx2M
2Madd/drop
add/drop
capacity
capacity
2U
Expansion
Expansionunit
unit(EXU)
(EXU)
for
for16
16xx2Mbit/s
2Mbit/sadd/drop
add/drop
&&baseband
branching
baseband branching
35
Protecting
ProtectingFIU19(E)
FIU19(E)
for
for1+1
1+1FIU19
FIU19
configuration
configuration
16
16xx2M
2MIC
IC
plug-in
unit
plug-in unit
FIU 19 Mechanics
Processor board
Power supply
Interface board
Plug-in unit
slots
36
RRIC Indoor unit
RRIC for Talk-family BTS
Supports two FlexiHopper or MetroHopper radios

Up to 4 x 2 Mbit/s add/drop capacity to the transmission unit (TRUx) of BTS
Grooming at 8 kbit/s cross-connection level via TRUx of the BTS
Support for loop protection provided by TRUx
Flexbus 3 interconnects RRIC1 to RRIC2 for internal bypass
37
RRIC interfaces
38
FXC RRI Indoor unit
FXC RRI for UltraSite BTS, MetroSite BTS,

and MetroHub transmission node
Supports two FlexiHopper or MetroHopper radios
2 Mbit/s cross-connections between Flexbus
interfaces (TNC 50 connectors)
Up to 16 x 2 Mbit/s add/drop capacity to BTS
Grooming at 8 kbit/s cross-connection level
Supports loop protection for the BTS
Supports hot stand-by (HSB) for FB1 and FB2
Fits into any transmission slot of BTS or Hub
39
IFUE Indoor unit

Plug-in unit for UltraSite/MetroSite WCDMA
BTS, or Stand-alone AXC
Supports three FlexiHopper or
MetroHopper radios
Flexbus interfaces 1-3 offer up to 16 x 2
Mbit/s plus DC power to OU (TNC 50
connectors)
2 Mbit/s cross-connections between
Flexbus interfaces
Up to 16 x 2 Mbit/s total add/drop capacity
to the BTS
Hot stand-by (HSB) support for FB1 and
FB2
Local management via LMP port (BQ
connector)
Remote management via backplane
40
Location of IFUE
in AXC module of Supreme BTS
41
FIFA Indoor unit

FIFA is the indoor unit integrated into Flexi EDGE BTS
FIFA plugs into the BTS System Module ESMA
42
FTFA Indoor unit

FTFA is the indoor unit integrated into
Flexi WCDMA BTS
FTFA mounts onto the BTS System
Module FSMB
43
FIFA & FTFA Indoor units

Support two FlexiHopper or MetroHopper radios
Flexbus interfaces provide up to 16 x 2 Mbit/s plus DC power to OU
2 Mbit/s cross-connections between Flexbus interfaces
Up to 16 x 2 Mbit/s total add/drop capacity to Flexi EDGE BTS, up to 8 x 2
Mbit/s add/drop capacity to Flexi WCDMA BTS
Support hot stand-by (HSB), also HSB with space diversity, as well as
frequency diversity and polarization diversity
F/D
to/from
Flexi
BTS
FB1
Flexbus
FB2
Control
CC
F/D
44
Flexbus
Protection methods
45
Protection methods 1
Equipment protection
Equipment protection protects a single transmission link against faults in the
equipment. In equipment protection a pair of Nokia FlexiHopper Outdoor Units
(method 1) and also a pair of Indoor Units (method 2) are protecting each other
Equipment protection involves two outdoor units in hot standby (HSB)
protection mode. One OU is active while the other is passive in hot standby
Equipment protection can also be used with one antenna (1-antenna HSB)
Equipment protection can be implemented by the following methods:
1. Hot standby with 1 Indoor Unit (1IU HSB)
2. Hot standby with 2 Indoor Units (2IU HSB)
46
Protection methods 2
Propagation protection
Propagation protection is a means to reduce the influence of propagation
phenomena on transmission quality
The propagation protection method typically used in FlexiHopper radio is hot
standby plus space diversity (HSB+SD), where two redundant radio paths are
formed with the aid of two height-separated antennas at each end of the hop
A pair of outdoor units and possibly also a pair of indoor units are used at
both ends. Only one of the transmitters is sending at a time, but both
receivers are active
Due to redundant units, equipment protection is also provided along with
propagation protection
Propagation protection can be implemented by the following methods:
1. Hot standby with 1 Indoor Unit + Space diversity (1IU HSB+SD)
2. Hot standby with 2 Indoor Units + Space diversity (2IU HSB+SD)
3. 1 Indoor Unit with Frequency diversity (1IU FD)
4. 2 Indoor Units with Frequency diversity (2IU FD)
5. 1 Indoor Unit with Polarisation diversity (1IU PD)
6. 2 Indoor Units with Polarisation diversity (2IU PD)
47
Key elements of data fault recovery 1

Forward Error Correction (FEC)
FEC is always turned on
Interleaver (IL)
Interleaving is selectable between Off, 2-depth,
and 4-depth modes
Diversity switch (DS)
DS is active only in diversity applications (space,
frequency, or polarization diversity)
IU
OU
FEC
DS
48
IL
TX
RX

Forward error correction (FEC) and interleaving
FlexiHopper radios use FEC and interleaving to improve signal quality
With FEC, redundant information is inserted into the transmitted data
stream according to an algorithm which allows the receiver to detect and
correct errors in real time up to a certain threshold without the need
for retransmission
FEC uses Reed-Solomon coding RS(63,59) which provides 4 redundancy symbols for every 59 data symbols (6.4% coding redundancy)
FEC is continuously on
With interleaving, symbols in one transmit data block are distributed over
several adjacent blocks, to minimize vulnerability to burst-type errors
interleaving is selectable between off, 2-depth and 4-depth modes
with 2-depth interleaving, symbols are distributed over two blocks;
with 4-depth interleaving, symbols are distributed over four blocks;
4-depth mode provides maximum error-correction effectiveness
When FEC is used together with interleaving, burst-type errors can also be
corrected more effectively
49
FEC & Interleaving

Tx data
FEC encoding
Interleaving
Radio frame
Interference
De-interleaving
FEC decoding:
X errors detected, N corrected
Corrected frame
50

Diversity Switch
In diversity mode the better of two signals at the receiver is selected on a frameby-frame basis, based on FEC correction/detected error information
OU A
Rx data
FEC information frame by frame
E1 Line interface
DS
OU B
FEC information frame by frame
51
1IU HSB (+SD) protection (1/2)
52

One transmitter ON at a time
TX frequencies are the same in both transmitters
Could be implemented by using one antenna (no SD)
Equipment protection (OU)
Diversity switch is in use at the receiving end (SD)
Lazy TX changeover protection option
53
54
55
1IU FD/PD protection (1/2)
56

Both transmitters ON at the same time
FD requires two separate frequencies - PD can work with one
Could be implemented by using one antenna *
Equipment protection (OU)
Diversity switch in use at the receiving end
57
58
59
2IU/2OU protected chaining station
60
TX changeover
In HSB mode (with or without space diversity) transmitter
changeover can occur for 3 reasons:
1) Fault situation
2) Forced control
3) Lazy TX changeover
61
Lazy TX changeover 1
Lazy transmitter changeover protects against transmitter faults which can
not be detected by the equipment itself (for example a faulty antenna)
When far-end BER value is greater than zero, the system starts a period timer
according to selected quality class and BER value. If the BER value persists over
the threshold of the started primary period, the transmitter changeover is made
If the BER value is still greater than zero after the changeover, the system starts
a secondary period according to selected quality class and BER value.
The secondary period is always longer than the primary period, to establish
hysteresis in order to prevent continuous changeover cycling
If the BER after the changeover is 1000 times worse than before the changeover,
the system makes an immediate changeover back to the previous transmitter
Lazy changeover feature is based on the far-end BER, which is the result of the
radio's internal process. This BER can not be measured
Note: Lazy changeover is prevented if both directions have poor signal levels
(worse than BER-3). In this case the last started period will perform the TX
changeover
Lazy TX changeover settings include ON/OFF selection and 5 different
predefined classes for primary and secondary periods
62
Lazy TX changeover 2
Example: If the BER value stays above the BER level for a time period
specified in the quality class for that BER level, TX changeover will occur
BER-3
BER-4 limit crossed

start BER-4 period
BER-4 period expired

make TX changeover
BER-4
BER-5
BER-4 period
63
Indoor Unit changeover 1

With all protection methods (HSB or FD/PD diversity) it is possible to use Indoor
Unit equipment protection (HSB)
One of the indoor units is the active (working) unit and the other one is the
passive (protecting) unit
Active (working) indoor unit controls the whole system and makes decisions about
Indoor Unit changeovers and Outdoor Unit Tx and Rx changeovers
Active unit sends commands and information to the passive unit to keep it upto-date in case of needed changeover
Passive (protecting) indoor unit observes and measures the Rx state, waits for
commands from active indoor unit and sends information of its own status to
active unit
Indoor Unit changeover is based on fault events in the system. The active indoor
unit checks and maintains the status of both indoor units, and if the passive unit
is in better shape active unit makes the Indoor Unit changeover
Only exception is when the active IU is plugged out or becomes not operational
then the passive IU activates itself. In this case the plugged-out unit changes
to passive state and disables its transmitter
64

Fault events are handled in priority order by the active unit. Changeover will be
made only if the passive unit has no active alarms
The fault events in priority order:
1. IU missing or not operational IU is removed, power turned OFF or HW
reset command issued
2. IU Forced control user has set active Indoor Unit with Hopper Manager
forced controls. Forced control is deactivated if priority 1 fault (IU missing or not
operational) will occur
3. 16x2M plug-in unit missing plug-in unit not installed correctly or it is broken
4. EXU missing EXU (Expansion Unit) is not installed correctly or is broken
5. Transmitter oscillator error Indoor Unit Tx oscillator is faulty
6. Hardware register error Indoor Unit memory or register value is corrupted,
which may cause unpredictable results
7. IU receiver lock lost frame lock lost in both Flexbus interfaces in active
Indoor Unit.
8. Fault in 16x2M plug-in unit the number of faults in both 16x2M plug-in units
are compared and if the number in passive unit is smaller for 10 seconds, that
IU is activated
65

After changeover the system activates protection lost alarm, including
information about the (new) passive indoor unit fault. Other alarms of that unit
show the actual reason
After the fault has been corrected (e.g. unit replaced and commissioned) the
system activates HSB protection method and clears the alarms
If the passive indoor unit becomes faulty, the system activates protection lost
alarm and Indoor Unit changeover is not possible (except if active indoor unit is
removed or becomes not operational)
Note: Active indoor unit will not make changeover if IU settings are different
(60s after startup or after setting change)
Alarm "NE: Operation Mode: Fault in changeover function" will be active
until settings have been copied from active to passive IU
Note: If passive units 16x2M IC plug-in unit is not installed correctly, it may cause
bit errors
66
ATPC and ALCQ 1

ATPC and ALCQ are both techniques that enable the radio transmitter to increase
or decrease the transmit power automatically, based on feedback about the
received signal quality at the other end of the hop
ATPC Automatic Transmit Power Control
ALCQ Adaptive Level Control with Quality measurement
When ATPC or ALCQ is in use, the radio always tries to transmit at the minimum
power needed for adequate reception at the far end
The idea is to monitor the received signal level together with the bit error ratio
(BER) of the receiver, and to adjust the far-end transmitter output power to adapt
to the variable fading conditions
The maximum transmit power allowed for the hop, however, is specified (set)
with the element manager
The controlled use of transmit power reduces interference between neighboring
systems, and allows more efficient utilization of radio frequencies than the constant
power level approach
67
ATPC and ALCQ 2

ATPC controls the Tx power level so as to maintain the far-end Rx signal level
above a certain user-defined threshold
This threshold is based on the modulation method and capacity being used
ALCQ is more sophisticated, and also monitors the BER of the receiver
In addition, ALCQ applies a novel pseudo-error monitoring mechanism
The bit errors detected by the FEC decoder, which are invisible to the user, are
interpreted as pseudo-errors and used as an additional input for ALCQ
operation
This method can respond to the degradation of Rx signal quality before actual
bit errors occur over the radio relay
The selection between ATPC and ALCQ (or the choice not to use transmit power
control at all) can be made with the element manager
68
Configuration backup
FlexiHopper (Plus) outdoor unit and FIU 19(E) indoor unit support
configuration backup
Important configuration settings of one unit can be copied onto other units
for backup
Backup information can be restored in order to recover from fault
situations or to quickly commission a unit which has been replaced
Backups can be made automatically or manually with Hopper Manager
Configuration backup possibilities:
Outdoor unit settings backed up to the indoor unit
Indoor unit settings backed up to all outdoor units, and to the protecting
indoor unit (if present)
69
Dual capacity using different polarizations

With FlexiHopper, dual capacity can be achieved by combining two separate radio
hops using only one frequency combining one hop with vertical polarization and
another with horizontal polarization
Antenna supporting dual polarization (or 2 antennas at 90 angle to each other)
In case of equipment transmission fault a receiver can lock onto wrong (opposite
polarization) signal. This can be prevented by using different scrambling polynomials
in each hop
Advantages:
Possibility to double capacity of the hop without increasing use of bandwidth
Possibility to save on equipment and site costs by using only one antenna with
two radios at both ends of the hop
Disadvantages:
Hop unavailability objectives are harder to achieve due to propagation effects
Error performance targets are harder to achieve
Usable maximum hop lengths are shorter due to increased sensitivity to
propagation disturbances
70
Scrambling polynomial selection

FlexiHopper (Plus) supports scrambling
polynomial selection
Using different scrambling polynomials
can prevent accidental locking to the
wrong signal which is using the same
frequency
polarization diversity applications
dual capacity using different
polarizations
frequency reuse in chaining
configurations
71
Site configuration examples

72
Site configuration elements 1
73
Site configuration elements 2
74
Unprotected stations with FIU 19(E)
75
Chaining station
One Indoor Unit for two Outdoor

Units
Transmission and 2Mbit/s crossconnect integrated in IU
n x 2Mbit/s
BTS or Mux
76
Branching station
One Indoor Unit for three Outdoor
Units
Transmission and 2Mbit/s crossconnect integrated in IU
n x 2Mbit/s
BTS
77
Use of separate 2M
cables minimised
Protected stations with FIU 19(E) 1
78
Protected stations with FIU 19(E) 2
Slot 2 contains Ethernet PIU

Slot 3 contains Flexbus PIU
No 2M cables needed between IUs
When four Flexbus interfaces are in use,
the signals connected to FB1 & FB2 are
the same (OUs are in protected mode)
79
HSB protection
FIU19 provides many
protection options:
OU protection alone
IU + OU protection
1-antenna HSB
Protecting FlexiHopper OU
80
Protecting FlexiHopper OU and FIU19
Site configurations for Talk-family BTS

with RRIC indoor unit
81
Site configurations with RRIC
Chaining station with grooming capability
82
Branching station
Site configurations for Nokia MetroSite BTS
One FXC RRI integrated in the BTS
(BTS supports only one transmission unit)
FXC RRI in MetroSite EDGE BTS
83
1 - 2 x Nokia FlexiHopper (Plus) OU
Site configurations for Nokia UltraSite BTS
1 - 4 x FXC RRI integrated in the BTS
Tail sites, chain sites, loop sites, hub sites,

loop protection, grooming, etc.
FXC RRI in UltraSite EDGE BTS

84
Site configurations for Nokia MetroHub
1 - 5 x FXC RRI integrated in the node
Hub sites, loop protection, grooming, etc.
FXC unit family also offers E1 and STM-1

interface units, which can be combined
freely with FXC RRI to create complex
transmission solutions
FXC RRI in MetroHub Transmission Node
85
MetroHub station
Fast expansion of capacity
Nokia
MetroHopper
10 Flexbus radio interfaces with 5 FXC

RRI indoor units
E1 or E1/T1 interface cards as alternative
8 kbit/s cross-connection and grooming
Power supply and battery back-up
Installation outdoors or indoors
Nokia
FlexiHopper
Nokia
MetroHub
FXC RRI
86
nx2M add/drop capacity

with FXC E1 units
Site configurations for Flexi EDGE BTS

FIFA in Flexi EDGE BTS
Tail site
Protected
tail site
Chain site
87
Co-siting with Flexi WCDMA BTS

Flexi WCDMA BTS FB 2
Flexi EDGE BTS
2G and 3G
tail sites
FIFA in Flexi EDGE BTS

FB 1
Flexi WCDMA BTS FB 2
Flexi EDGE BTS
FB 1
88
FTFA in Flexi WCDMA BTS
Installation planning
The angle between two radio hops must be 0

i.e., the two radio signals should be diverging, not converging
89
FlexiHopper Management
90
Management with Hopper Manager

Easy-to-use Windows based graphical user interface
Commissioning, maintenance, troubleshooting
Capacity programming
Software download
Output power adjustment
Graphical display for 2Mbit/s cross-connection
etc.
Features
Integration wizard
Automatic fading margin measurement
Site documentation package
etc.
Use on site or remotely via Q1 bus
Nokia NMS / NetAct support
Hopper Manager can reside on Node
Manager Server
91
Hopper Manager features 1

Hopper Manager is an element manager for the following units:
FlexiHopper (Plus) & MetroHopper outdoor units
FIU 19(E) & RRIC indoor units
Management connection can be local or remote
Local LMP connection is fast and all functions are available
Remote connection is usually slower (max 9600 bps) and
certain functions are disabled, like far-end settings and
Commissioning Wizard
Hopper Manager functionality:
Configuration management
Configure every setting of each supported unit (IU & OU)
Manage all near-end units as well as hop settings
Configure also far-end units that are part of the hop
Commissioning Wizard for quick, easy node configuration
Performance management
Monitor counters, statistics and measurements
Fault management
Display alarms and obtain problem-solving help
92
Hopper Manager features 2

Hopper Manager functionality (cont)
Software management
Download software to all manageable units also far-end units
License management
Manage e-licensing of optional equipment features
(Hopper Manager version C4.7 and later)
One-click license installation
93
Element Managers for FlexiHopper
94
Indoor Unit + radio
Node Manager(s)
(local connection)
Node Manager(s)
used via the NMS
(remote connection)
FIU 19(E) + FlexiHopper (Plus)
Hopper Manager
Hopper Manager
RRIC + FlexiHopper (Plus)

[in Talk-family BTS]
Hopper Manager
Hopper Manager
FXC RRI + FlexiHopper (Plus)

[in MetroSite BTS]
FXC RRI Manager
FXC RRI Manager

[in UltraSite BTS]
UltraSite BTS Hub Manager

+ FXC RRI Manager
UltraSite BTS Hub Manager

+ FXC RRI Manager

[in MetroHub node]
MetroHub Manager
+ FXC RRI Manager
MetroHub Manager
+ FXC RRI Manager
IFUE + FlexiHopper (Plus)

[in UltraSite WCDMA BTS]
AXC-FB Hopper Manager
AXC-FB Hopper Manager
FIFA/FTFA + FlexiHopper (Plus)

[in 2G/3G Flexi BTS]
FlexiHub Manager
FlexiHub Manager
SW licensing
The following features are currently under license in the Nokia Hopper family:
FlexiHopper (older releases):
16-state modulation (32-TCM)

as of FlexiHopper C6.0
as of FlexiHopper Plus C2.2
FlexiHopper (as of release C2.5):
Transmission capacity upgrades

FlexiHopper 4E1
16-state modulation
FlexiHopper & FlexiHopper 4E1
FIU 19(E):
Flexbus 2 utilization
SNMP support
OSPF support
as of FIU 19E C3.0
OSPF license is bundled with SNMP license

FIU 19E C2.0 HW supports C3.0 SW, but then requires SW licensing as well
95
Upgrading outdoor units with licenses

T58
FlexiHopper Plus
Note! 16-state modulation

is not possible at 4E1 capacity
T55
FlexiHopper
T54
FlexiHopper 4E1
T54
FlexiHopper 4E1
T54
Capacity
Capacity
upgrade
upgrade
4E1
to
4E1 to
8E1
8E1
Capacity
Capacity
upgrade
upgrade
4E1
to
4E1 to
8E1
8E1
FlexiHopper 4E1
T54
FlexiHopper 4E1
96
1616state
state
modul
modul
ation
ation
Capacity
Capacity
upgrade
upgrade
4E1 to
4E1 to
16E1
16E1
Capacity
Capacity
upgrade
upgrade
4E1 to
4E1 to
16E1
16E1
Capacity
Capacity
upgrade
upgrade
8E1
to
8E1 to
16E1
16E1
T58
FlexiHopper Plus
T55
FlexiHopper
1616state
state
modul
modul
ation
ation
1616state
state
modul
modul
ation
ation
1616state
state
modul
modul
ation
ation
T58
FlexiHopper Plus
T58
FlexiHopper Plus
Transmission Loader 1
Nokia Transmission Loader is a SW tool for efficiently performing mass upgrades of
software on a network of Q1 transmission elements
Instead of performing upgrades individually for each NE with node managers,
Transmission Loader automates the task and speeds it up by performing multiple
upgrades in parallel
It is designed to work in the background with a minimum of manual intervention
It allows handling of network upgrades centrally from the OMC (it is designed to
reside on Node Manager Server)
By greatly reducing manual work, Transmission Loader is able to generate large

savings in maintenance time and operating expenses
Transmission Loader C1.4 currently supports most 2G and 3G network architectures,
including TCP/IP connections, and has successfully been taken into use in several
large networks
97
Transmission Loader 2
Transmission Loader can perform a network scan to provide the user with a list of all
supported elements in the network, with their current software versions
Transmission Loader enables semi-automated SW downloads:
User can define up to 25 parallel tasks
Up to 5 parallel downloads can be made through one BSC (to different BCFs)
SW is copied between similar NEs on a site, avoiding repeated slow downloads
Transmission Loader supports the following transmission elements:
FlexiHopper, FlexiHopper Plus, and MetroHopper radios
FIU19 and FIU19E indoor units
FXC RRI and other ITN units integrated in 2G BTS
IFUE unit integrated in 3G BTS
Note that some older versions of these units may not support
remote SW download or activation, requiring local upgrade.
98
Network management
In the network, FlexiHopper can be managed via local Q1 connection (e.g.,
from BTS) or remote Q1 channel (e.g., from BSC)
FlexiHopper also supports transporting the Q1 channel in the frame overhead of the
radio signal to the far end of the hop (in a supplementary channel in the radio frame
which is dedicated to Q1 use)
Q1 branching options in each node are determined by the Q1 branching structure of
the indoor unit
This facilitates the use of FlexiHopper in Nokia/NSN networks which are managed via
NetAct
When used with FIU 19E, FlexiHopper also supports SNMP management over
an IP DCN
99
FlexiHopper supports transporting the IP management channel (PPP) in the frame

overhead of the radio signal to the far end of the hop
The PPP channel can be routed over the radio hop through either the fast (AUX Fast)
or slow (Hop LAN) auxiliary data channel in the radio frame
This allows FlexiHopper radios to be used in mixed-vendor networks where network
management is IP-based
Management using Nokia Q1 connection

Nokia Q1 management configuration
100
Introduction to Q1
Q1 is a protocol used for managing NOKIA transmission equipment
master-slave
half duplex
asynchronous
Nokia proprietary
Following tasks can be performed with Q1:

Fault Management (Alarm collection)
Performance Management (Statistics collection)
Configuration Management (Remote configuration of
network elements)
101
Q1 in GSM Networks
NetAct
NetAct
NetAct
BTS polling
Q3
Talk BTS
Q3
BSC
BSC
Q1polling
LapD
BSC polling
OMUSIG
Q1
Q1 NE
NE
2G BTS
Q1polling
Q1
Q1 NE
NE
BSC
BSC
E1
MetroHub
BTS
polling
LMU
UltraSite BTS
102
Q1 bus
Master-slave type bus where master polls slaves one by one
Slave can not send unless polled by master

Q1 management bus uses 4-wire V.11 electrical interface
Slaves are connected to Q1 bus in parallel

Management address range is 0 - 4094
NE's on the same Q1 bus must each have a unique address

4095 is common broadcast address
Slaves
Master
103
uP
uP
uP
Nokia Q1 vs. classic Q1
104
Nokia Q1 is an extended version of "classic" Q1 protocol

designed to better support the functional organization found in
newer equipment (e.g., multiple FE's)
Slaves are now connected to Q1 bus in series
newer NE's have two Q1 interfaces, connected internally by
branching bridge (to permit point-to-point Q1 cabling)
Q1 interfaces remain electrically the same (V.11) but connectors
are physically different (e.g., TQ type)
Local Management Port (LMP) provided for local management
independent from Q1 bus interfaces, separate Q1 address
local management does not interfere with remote polling
LMP interface is electrically V.28
Management address range is 0 - 3999
addresses 4000 - 4094 reserved for "special use"
addresses 4070 - 4089 reserved as local "hardware" addresses
(for default connecting)
Combining classic Q1 and Nokia Q1
In the same site, there may be some NE's using "classic" Q1 and some NEs
using Nokia Q1
In that case, it is recommended that Nokia Q1 devices are the first slaves on
the Q1 bus while "classic" Q1 devices are placed at the end of the bus
Q1 BUS
MASTER
CPU
CPU
105
CPU
CPU
CPU
CPU
CPU
CPU
CPU
Characteristics of BTS polling

BTS polling
BTS sends a status inquiry to polled equipment
Typically Q1 bus is local using 9600 bit/s speed
Different BTS types have different master :
BCFx in Talk-family BTS

BOIx in UltraSite BTS
VTxx in MetroSite BTS
EACB and OMU in 2nd Gen. BTS
OMU in PrimeSite
In the BSC an OMUSIG has to be created
106
Characteristics of BSC polling

BSC polling
BSC is the master collecting data from transmission equipment
18 service channels available (allocated by BSC)
Data rate of Q1 channel can be 1200, 2400, 4800 or 9600 bit/s
Maximum number of transmission units under one BSC is 1024,
but 30 is maximum recommended in a single Q1 channel
Polling cycle increases with the amount of equipment being polled
(average is 0.6 sec per unit; BSC waits up to 1 sec for response)
In the BSC a Q1 channel has to be created
107
BTS polling vs. BSC polling
108
Both types of polling support essentially similar features and functionality
BTS polling recommended for transmission nodes at BTS sites

simplified network planning and site commissioning
no need to set up Q1 channels between BSC and BTS sites
Q1 transmission capacity saved
no clear advantage in using BSC polling
BSC polling usually used for transmission equipment at BSC sites

such as DN2, MetroHub, FIU19, etc.
if BSC is co-located with a BTS rather than with cross-connect
equipment, then BTS polling could still be implemented there
Q1 connections in FIU 19(E)

Two ways to manage FIU 19: (1) Locally via Q1 interface
from
BTS
Q1-1
FB1
SW6
SW1
FB2
SW5
Q1-2
SW3
SW2
SW4
chaining
to Q1-1
of next FIU
CPU
LMP
109
SW7
FB3
SW8
EOC's to
Flexbus
Interfaces
Remote management of FIU 19(E)

Two ways to manage FIU 19: (2) Remotely via EOC in radio frame
from
BSC
FB1
Q1-1
SW1
SW5
SW6
FB2
SW7
Q1-2
SW3
SW2
SW4
chaining
to Q1-1
of next FIU
CPU
LMP
110
FB3
SW8
EOC's to
Flexbus
Interfaces
to next
site
Using Nokia Q1 bus: chaining FIU 19(E)

Q1-1
FB1
FB2
FB3
Q1-2
CPU
LMP
IU 1
Q1-1
FB1
FB2
FB3
Q1-2
CPU
LMP
111
IU 2
Using Nokia Q1 bus: FIU 19(E) 1+1 protection

Q1-1
Q1-2
CPU
LMP
IU A (master)
Q1-1
Q1-2
CPU
LMP
IU B (slave)
112
Backplane
Q1 connections in RRIC
FB1
to/from TRUx
FB2
FB3
from TRUx
CPU
RRIC
LMP
113
Q1 connections in FIFA
Flexbus
master
switch
Flexbus 1
switch
Flexi BTS
connection
Processor
switch
Flexbus 2
switch
CPU
FIFA
114
Flexbus
overhead
Flexbus
overhead
Talk-Family BTS
MetroHopper
FlexiHopper
Talk BTS
Q1 cable
Flexbus
Q1 polling
Flexbus
TRUA
BTS
BCF
Flexbus
Processor
O&M
RRIC2
FB3
CPU
EI (V.11)
Flexbus
FIU19
Processor
CPU
Dir 1
Q1 cable
Dir 2
Dir 3
Talk BTS
FIU19
default local
Q1 address
TRUA 4080
RRIC1 4084
RRIC2 4085
FB1
BTS
CPU
FB2
Q1 polling
E1
115
FB1
Flexbus
Q1-1
Processor
FB1
FB2
Q1-2
CPU
FB3
FB2
FB3
RRIC1
UltraSite BTS polling

UltraSite
Q1 hybrid
Q1_EOC
Q1_1
External
Q1_2
FXC E1
Q1_EOC
INT to EXT
Q1 Int
Internal
Flexbus
FXC RRI
(BOI)
BTS/Q1
Flexbus
Q1_EOC
Processor
FXC RRI
LMU
LMU
Q1_EOC
E1
CPU
EXT/Q1
FXC RRI
LMP
UltraSite
UltraSite Hub has only one Q1 address

Transmission unit located in slot 1 is the master
If Q1 address of TRE1 of BCF is set to 4080 in BSC, then UltraSite

automatically performs BTS polling
116
UltraSite BSC polling
UltraSite
Q1_EOC
Q1_1
Flexbus
External
FXC E1
Q1_2
Q1_EOC
INT to EXT
Q1 Int
to next
site
from
BSC
Q1 hybrid
Internal
from
BSC
Flexbus
FXC RRI
(BOI)
Q1_EOC
Processor
FXC RRI
Q1_EOC
to next
site
E1
CPU
FXC RRI
LMP
UltraSite
If Q1 address of TRE1 of BCF is set in the range 0 - 3999 in BSC, and

also defined in a BSC Q1 channel, then BSC polling will be performed
117
MetroSite
MetroSite FXC E1 Q1 hybrid
Q1_1
Q1_EOC
External
Q1_2
INT to EXT
Q1 Int
Internal
Flexbus
Prosessor
MetroSite
MetroHub
Q1_EOC
CPU
Q1 polling
LMP
(2) Q1 cable
(1) E1 or
(1) E1
MetroHub
(2) Q1 cable
Q1 hybrid
Q1_1
Q1_EOC
External
Q1 to MetroHub in E1 EOC or via external Q1 cable
FXC E1
Q1_2
Q1_EOC
FXC RRI
Q1_EOC
Prosessor
FXC RRI
Q1_EOC
CPU
FXC RRI
LMP
118
MetroHub has only one Q1 address

Transmission unit located
in slot 1 is the master
Hopper
FlexiHopper
Flexbus Q1 polling
Flexbus
BTS polling
to
repeater site
Repeater Site
FIU19
Q1 to FIU19 in Flexbus overhead

UltraSite
Repeater Site
UltraSite Q1 hybrid
FXC E1
Q1_EOC
INT to EXT
Radio hop
FB2
Flexbus
Q1-1
Prosessor
Q1-2
Internal
FXC RRI
(BOI)
Q1_EOC
Processor
FXC RRI
Q1_EOC
CPU
FXC RRI
LMP
119
FB1
External
Q1_2
Q1 Int
FIU19
Q1_EOC
Q1_1
FB3
CPU

Q1
polling
n*E1
BSC
BSC
Transmission
equipment
at BSC
Flexbus
FlexiHopper
FIU19
Flexbus
Q1 polling
Q1 from BSC in E1 frame
MetroHub
FlexiHopper

MetroHub Q1 hybrid
Q1_1
FIU19
FB_EOC
FB1
External
Flexbus
Q1_2
FB2
E1_EOC
FXC RRI
FXC RRI
Q1 from BSC in E1 frame
CPU
FXC RRI
LMP
120
Q1-1
Prosessor
Q1-2
FB3
Prosessor
Flexbus
CPU
Q1 polling in UltraSite 3G BTS

ATM Cross-Connect node (AXC) polls Q1 network elements at local site
either stand-alone AXC, AXC Compact, or AXC integrated into UltraSite
3G BTS
AXC contains a Q1 Support Function (Q1SF) which implements Q1 polling
Q1SF acts as local Q1 bus master
Q1SF forwards Q1 messages to NetAct (Q1 over IP via 3G DCN)
Q1 Agent in NetAct acts as a mediation device between Q1SF and NetAct
Q1 buses, nodes, etc. are defined in Q1 Agent
(speed of local Q1 bus is configured in Q1SF)
Internal Q1 bus in AXC extends to integrated transmission units such as IFUE
External Q1 bus can be connected from the Q1 port on the front panel of AXU
card to local network elements such as FIU 19(E)
121
Q1 polling in AXC
IFUE is connected to
internal Q1 bus of AXC
FIU 19(E) is one Q1
network element that
can be connected to
external Q1 bus of AXC
122
Management using TCP/IP connection

IP DCN management principles
123
General IP DCN information

Ethernet plug-in unit interfaces
(10/100Base-T) are not part of IP
DCN
IP DCN connection
via 10Base-T Ethernet
interface (half duplex)
IP DCN is used mainly for:

Network management with IP traffic (O&M = operation & maintenance)
IP DCN consists of:
IP Routing (Internet Protocol, IPv4)
IP DCN (IP Data Communication Network as part of telecom network)
IP DCN allows the use of:
SNMP (Simple Network Management Protocol) as an alternative to Nokia NetAct
IP applications FTP (File Transfer Protocol), TFTP (Trivial FTP), Hopper Manager
connection over IP network (=> manager sessions over internet), etc.
IP phone calls voice calls (VoIP voice over IP), IP EOW (Engineering order-wire)
IP DCN is supported by FIU 19E as of version C1.5
124
IP DCN data channels

C3.0
FIU
C2.0
FIU
AUX Fast
Hop LAN
10Base-T
C2.0
FIU
AUX Fast
IP Routing: FIU 19E is

able to route IP packets
between its 10Base-T
Ethernet interface and 3
PPP interfaces
Hop LAN
PPP link is a bi-directional point-to-point data channel between two IP routers

AUX Fast and Hop LAN data channels are alternative PPP data channels
inside the radio frame overhead they have nothing to do with E1 or Ethernet
payload traffic
FIU 19E supports 3 PPP data links in 3 radio directions
Hop LAN only works when FIU 19E is connected to radio outdoor unit
AUX Fast also works if Flexbus is directly connected to another FIU 19E
AUX Fast data channel is not supported on FIU 19E C1.5
125
C1.5
FIU
PPP link capacities in FIU 19E

AUX Fast and Hop LAN data channels use the radio frame
overhead and their speed depends on radio link capacity
Radio link
AUX Fast capacity
Hop LAN capacity
16 x 2M
512 kbit/s
80 kbit/s
8 x 2M
256 kbit/s
57 kbit/s
4 x 2M
128 kbit/s
28 kbit/s
2 x 2M
64 kbit/s
14 kbit/s
Hop LAN only works when FIU 19E is connected to radio outdoor unit
AUX Fast also works if Flexbus is directly connected to another FIU 19E
AUX Fast data channel is not supported on FIU 19E C1.5
126
AUX & PPP cross-connections
Each router interface

(Ethernet, ppp0-2) has
its own IP address &
IP subnet mask
FIU 19E
AUX Fast
uP
Hop LAN
ppp0
ppp1
10Base-T
ppp2
Default
gateway
setting
127
FB1
FB2
FB3
AUX & PPP

cross-connections
Hop LAN
works only
when radio
is attached
AUX Fast
also works
if Flexbus
is directly
connected
to another
FIU 19E
Benefits of IP DCN network

Support for existing transport protocols and their applications, such
as OSI and TCP/IP family

Utilization of capacities and applications of the public internet
Flexibility to separate from or integrate into an operators network
Harmonized guidelines for DCN site solutions
Harmonized implementation of an O&M interface in individual
network elements
Connecting consecutive links to same IP DCN over the radio link
with IP routing functionality
Connecting external equipment to same IP DCN over the radio link
Quick user interactions with Hopper Manager
Automated clock equalization with Network Timing Protocol (NTP)
IP DCN ensures good fit into operators existing network
Harmonized DCN solutions reduce operating costs, due to common
look & feel
128
Basic IP routing principles 1
Each radio hop and its end points (near-end and far-end Flexbus interfaces)
constitute an IP subnet (mini-network) with its own IP addresses and network mask
Size of the subnet (number of addresses) is determined by the subnet mask
First available IP address in the subnet space (host ID = all 0s) is that of the
subnet itself and the last IP address (host ID = all 1s) is the broadcast address
Remaining addresses in between can be allocated to individual interfaces
129
Basic IP routing principles 2
Internal router in FIU 19E is a member of each network (subnet) in which it has an interface
FIU 19E can be identified by the IP address of any of its router interfaces
Function of a router is to handle transfer of traffic between different networks
Routing table defines how traffic is routed to a particular destination in another network
Router is aware of all networks which are directly connected to it (neighbouring IP
subnets), and can automatically route IP traffic to these destinations
However, router must be configured to handle indirect destinations as well
Every IP subnet downstream which is indirectly connected to the router must have a
routing table entry indicating the next interface in the route to which traffic should be sent
(far-end IP address in the hop to neighbouring subnet)
All traffic to remote destinations not listed in the routing table gets transfered to the default
gateway, typically the next interface (far-end IP address) in the link upstream
130
IP routing example
For IP management traffic to reach the last FIU 19E in the chain (192.168.1.38) from the
first FIU 19E (192.168.1.10), the router in the first unit must have the following entry:
dest 192.168.1.36 mask 255.255.255.252 nextHop 192.168.1.34
Default gateway for the first FIU 19E is interface 192.168.1.30 on the standalone router
131
Unnumbered IP links
As of release 2.7, FIU 19E also supports unnumbered IP links

This means that Flexbus interfaces no longer need to have individual IP addresses,
and an IP subnet does not need to be defined for each radio hop
The PPP link over a radio hop can be enabled at each end simply with a check box
FIU 19E is identified using a single IP address, that of its DCN interface
This greatly simplifies the configuration of static routing in the radio network
132
Introduction to OSPF
Static routing is supported by FIU 19E as of version C1.5
Dynamic routing with OSPF protocol is supported as of FIU 19E version C2.1 (=>
C2.0 HW running C3.0 SW)
As of FIU 19E C3.0 SW, OSPF is E-licensed feature (bundled along with SNMP support)
No licence needed for static routing support
OSPF (Open Shortest Path First)

Dynamic routing protocol
Automatic calculation of routing table
Dynamic updates to routing table
no need to create or update routing table manually
Interior Gateway Protocol (IGP) working inside autonomous system
e.g., large company network, network administered by local network administrator
Suitable for large and medium-size networks (more than 10 routers in network)
Considerations for OSPF
133
OSPF router is not able to learn routes from routers that use static routing
Static routing can be used simultaneously with OSPF, but
routing table must be configured manually to include static routes if there is at least
one static router in the network
Proxy ARP should be disabled when using OSPF
OSPF vs. static routing

Static routing:
Cumbersome to configure (manually)
Does not adapt automatically when adding new links and nodes
Cannot adapt to link/node failures
Routing table entries must be manually added to every FIU 19E in IP DCN
Suitable for small IP networks does not scale to larger networks
OSPF dynamic routing:
Optimal routing automatically calculates shortest path to destination and
creates routing table
Automatically adapts to network topology changes and recalculates routing
table
Informs attached routers about network topology changes
Robust, flexible, quick to adapt to changing network conditions
Suitable for larger networks
134
OSPF concepts
OSPF Router ID
uP
identifies router in the network
router ID is typically one of router interface IP addresses
Router priority
10Base-T
used when selecting a designated router for a LAN
priority value range is 0-255, default value 10
router that has highest priority is elected as designated router
Link cost
each output interface of router is assigned a link cost value
link cost is used in calculating optimal path from router to destination network
link cost value is 100M/link speed (bits/s)
examples: for 10Base-T Ethernet interface, cost = 10
for ppp link, cost = 1000 (200 to 7000 ?)
OSPF areas
network can be divided into multiple OSPF areas identified by area ID
area 0 is base area, called OSPF backbone
max 50 routers inside one area
intra area router has interfaces in only one area
area border router (ABR) has interfaces in more than one area
ABR must have one interface to area 0 (backbone)
135
ppp0
ppp1
ppp2
Configuring routing: Overview

Network planning needed:
IP addresses
Subnetting
Configuring each network element/router:
Assign IP address and network mask for
each router interface
Define default gateway
Create AUX-PPP cross-connections
Additional configuration for static routing:
Creating static routes in routing table of
each node
Routing table contents is basically different
at each node
Additional settings for each OSPF router:
Define router ID and priority
Create OSPF areas and define area ranges
Enable OSPF at each interface and assign
its area ID
Define link cost for each output interface
136
Area 0
Area 1
Area 3
Area 2
Summary
In this learning element, we have covered:
The main features and functions of FlexiHopper (Plus) radios
The different site configurations available with FlexiHopper (Plus)
137
The different types of indoor units commonly used with the FlexiHopper
(Plus) outdoor unit, and their main characteristics
The various protection methods available with FlexiHopper (Plus)
The management options available for FlexiHopper (Plus)

01 FT43131EN01GLN0 Flexihopper Overview

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

01 FT43131EN01GLN0 Flexihopper Overview

Enviado por

Direitos autorais:

Formatos disponíveis

Cellular transmission solutions

for coverage and capacity

Nokia FlexiHopper (Plus)

Nokia Siemens Networks

Nokia Siemens Networks

FlexiHopper (Plus) features

Nokia Siemens Networks

Nokia FlexiHopper radios

Nokia Siemens Networks

FlexiHopper radio family

For example, FlexiHopper 4E1 can be upgraded to FlexiHopper Plus

Nokia Siemens Networks

FlexiHopper features (1)

Nokia Siemens Networks

Dual modulation modes

Nokia Siemens Networks

Note that 16-state

FlexiHopper features (2)

Nokia Siemens Networks

Flexbus single-cable interconnections

Nokia Siemens Networks

FlexiHopper features (3)

Nokia Siemens Networks

Integrated radio and 2M cross-connect

Nokia Siemens Networks

FlexiHopper features (4)

Nokia Siemens Networks

FlexiHopper features (5)

Nokia Siemens Networks

Nokia Siemens Networks

Electrical Structure of Outdoor Unit ...1

embedded microprocessor system

Intermediate Frequency Unit (IFU)

one oscillator (VCO) for both Tx and Rx

Waveguide antenna filter (diplexer)

Nokia Siemens Networks

Electrical Structure of Outdoor Unit ...2

Nokia Siemens Networks

Block diagram of Outdoor Unit

Nokia Siemens Networks

Mechanical structure of Outdoor Unit

Nokia Siemens Networks

Common Indoor units

Nokia Siemens Networks

Integrated indoor units in Nokia base stations &

Single-cable IU-OU connections for easy site

Transmission and add/drop capacity separated

16x2Mbit/s transmission capacity with all IU models

Common indoor unit platform

Support for all frequencies

Nokia Siemens Networks

Indoor unit types

19-inch indoor units

Nokia WCDMA UltraSite/MetroSite

Nokia Siemens Networks

FIU 19(E) Indoor unit ...1

(NO LONGER AVAILABLE)

(NO LONGER AVAILABLE)

Nokia Siemens Networks

FIU 19(E) Indoor unit ...2

Nokia Siemens Networks

FIU 19 Indoor unit

Nokia Siemens Networks

Measurement point interface (SMB connector)