Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
SRAL XD
System Technical Description
CODE: TD-040203-1
VERSION 12.0
INDEX
1. Introduction .................................................................................................................................0
1.1. Scope ................................................................................................................................ 0
1.2. Related Documents........................................................................................................... 0
1.3. Revision Information ......................................................................................................... 0
2. System Overview ..........................................................................................................................0
2.1. Introduction ....................................................................................................................... 0
2.2. Indoor Unit......................................................................................................................... 0
2.2.1. IDU Plug-in ................................................................................................................ 0
2.2.2. IDU SingleBoard2...................................................................................................... 0
2.2.3. Outdoor Access Unit ................................................................................................. 0
2.3. Outdoor Unit...................................................................................................................... 0
2.3.1. Normal Density ODU................................................................................................. 0
2.3.2. High Density / High Performance ODU ..................................................................... 0
2.3.3. High Density enhanced ODU .................................................................................... 0
2.4. Configurations ................................................................................................................... 0
2.4.1. Unprotected terminal ................................................................................................. 0
2.4.2 Protected terminal ......................................................................................................... 0
2.4.3 Add-Drop/Repeater ....................................................................................................... 0
2.4.4 2x(1+0) .......................................................................................................................... 0
2.4.5 Ring ............................................................................................................................... 0
2.5 Installation ......................................................................................................................... 0
3. System Description ......................................................................................................................0
3.1. IDU Plug-In........................................................................................................................ 0
3.1.1. Access Card .............................................................................................................. 0
3.1.2. Controller................................................................................................................... 0
3.1.3. BaseBand.................................................................................................................. 0
3.2. IDU SingleBoard2 ............................................................................................................. 0
3.3. Outdoor Access Unit ......................................................................................................... 0
3.4. Outdoor Unit...................................................................................................................... 0
3.4.1. ODU ND .................................................................................................................... 0
3.4.2. ODU HD/HP .............................................................................................................. 0
3.4.3. ODU HDe .................................................................................................................. 0
3.5. Frequency Setting ............................................................................................................. 0
3.6. Output Power .................................................................................................................... 0
3.6.1. Coupling loss............................................................................................................. 0
3.7. Radiating System .............................................................................................................. 0
4. Cross Connect Functionality.......................................................................................................0
4.1. Cross Connection Matrix on IDU PI 16xE1 ....................................................................... 0
4.2. Cross Connection Matrix on IDU Plug-in 32xE1 ............................................................... 0
4.3. Preservation of the cross-connection matrix ..................................................................... 0
5. Ethernet functionalities ...............................................................................................................0
5.1. Switching........................................................................................................................... 0
5.1.1. Filtering...................................................................................................................... 0
5.1.2. Forwarding ................................................................................................................ 0
ITP MWR Product Management
1. Introduction
1.1. Scope
Scope of this document is to give an overview of SRAL XD product family focusing on architectural
aspect and main features.
In order to have a complete description of the performance of the equipment refer to SRAL XD
System Technical Specification (TS-310706-1)
For a complete description of the available features for each Software Version Release refer to the
latest version of Customer Feature List and Customer Release Note
2. System Overview
2.1. Introduction
SRAL XD is a PDH MW equipment able to transmit a traffic load from 2xE1 to 32xE1 in the
frequency bands 7- 38 GHz according to ETSI radio channel arrangements.
The equipment adopts a split configuration composed of one Indoor Unit connected to one
or two Outdoor Units, by means of a coaxial cable.
The ODU is directly connected to the rear of antenna by means of four retaining latches
without using any waveguide.
The IDU (Indoor Unit) provides traffic and auxiliary channels interfaces and performs
baseband and control processing independently from operating frequency.
The ODU (Outdoor Unit) performs the Mo-Demodulation and houses the RF Tx/Rx unit.
It is independent from traffic capacity.
The indoor unit provides the tributaries input and output interfaces as well as interfaces for
service channels, network maintenance facilities, alarms and connection to the power
supply.
The Indoor Unit performs baseband processing, scrambler/descrambler and FEC
functionalities.
The IDU also equips the Switching logic offering protection against multipath fading and
hardware failure.
The unit adopts a 1U high case that can be mounted in a 19” or 600 mm rack. All the
connectors for the traffic, service channels and maintenance operation are in the front of
the equipment.
Three different IDU versions are available
Plug-In
Single Board2
Outdoor Access Unit
IDU Plug-in
IDU SingleBoard2
ITP MWR Product Management
The Plug-In version has been designed to provide a full set of configurations:
• (1+0)
• 2x(1+0) unprotected terminal
• Add-Drop / Repeater
• Ring
• (1+1) hot stand-by protected terminal
• (1+1) Frequency/Polarization Diversity protected terminal
The IDU adopts a modular architecture composed of four cards housed in a 1U high shelf:
The listed configurations are related to the maximum hardware capacity: the wanted set of
features can be enabled by means of a user fee mechanism.
In the following figure the different cards are shown and the description of the relevant
interfaces is provided.
ITP MWR Product Management
12 03 01
C C C O
ODU CABLE H H B D
s A B L U '
PS
SRAL XD CAUTION
Vbattery
LCT T M C
E N / ODU CABLE
S / M H H B D
' A L '
T W J B U
P
S
CAUTION
Vbattery
10 11 09 04 02
or or or
34Mbit/s 2Mbit/s
A A A A
06 07 08 06 07 08 06 07 08 06 07 08
B B B B
Such architecture allows to upgrade an unprotected configuration, just adding in the same
shelf an additional base-band card which can be individually supplied.
In case of failure in a Protected configuration the BaseBand can be replaced without traffic
interruption.
In this version the Baseband Card also houses the Hitless Switch logic providing an error free
connection in case of fading.
• 8xE1 (1+0)
ITP MWR Product Management
• 16xE1(1+0)
• 16xE1(1+1)Hsby
The listed configurations are related to the maximum hardware capacity: the wanted set of
features can be enabled by means of a user fee mechanism.
The Outdoor Access Unit implements all access and baseband functions in a waterproof case
suitable for outdoor installation.
The mechanical structure of the OAU consists of a compact sealed box suitable for wall
mounting and pole mounting.
ITP MWR Product Management
Suitable flanges are foreseen for the installation of the OAU into ETSI and/or 19” rack.
ITP MWR Product Management
90
PC CONNECTION CONNECTOR
POWER SUPPLY
CONNECTOR
CONNECTION PANEL
GROUNDING POINT
DIMENSIONS IN MILLIMETERS
1. IDU-ODU cable interface management (power supply and in/out base-band signals
interfacing);
2. Modulation of base-band digital signal received from the IDU;
3. Demodulation of received RF signal and delivery of recovered base-band signal to
IDU;
4. Supervision and configuration/management of the ODU;
5. Management of the communication channel from/to IDU CONTROLLER.
The Outdoor Unit adopts a Frequency Division Duplexing technique as showed in the
relevant ETSI recommendations. RF transmitter and Receiver frequencies can be set by
the user by means of SW command.
Any change of Tx (Rx) frequency automatically involves the change of Rx (Tx) frequency
according to the ODU shifter.
(DOWN VIEW)
(SIDE VIEW)
290
269 164
238 15
5
232 140
(FRONT VIEW)
ODU HP/HD
(DOWN VIEW)
(SIDE VIEW)
281
(FRONT VIEW)
123
267 238
2.4. Configurations
One ODU
One Antenna
One IDU
One coaxial cable for IDU-ODU interconnection
Tributaries
(1+0)
Two ODUs
One or two antennas
One IDU
One coaxial cable for each IDU-ODU interconnection
In (1+1)HSby one transmitter is working, while the other one is in stand-by; both receivers
are active and the best ODU source is selected.
When an HW failure is detected the system actuates the hardware switch:
⇒ On IDU Plug-in, TX (BB+ODU) and RX chain (BB+ODU) are switched
independently according to the occurrence of the fault
⇒ On IDU Single Board2, both TX (BB+ODU) and RX chain (BB+ODU) are switched
at the same time
This switch cannot avoid “error bursts” during the protection switching, because it is a
hardware switch, controlled by alarm signals generated by already happened hardware
defects
Both ODUs are connected to a single antenna via a power splitter, balanced (3dB
symmetric loss) or un-balanced (stand-by channel loss ~ 10 dB, main channel loss ~ 1
dB).
Either remote or separate mounting is available.
Main
Hsby
Tributaries
Main
Tributaries
Hsby
F1
Tributaries F2
(1+1)Frequency Diversity
2.4.3 Add-Drop/Repeater
Add/Drop-Repeater system type is characterized by two different radio directions each one
employs one ODU.
This system allows partially dropping and/or adding tributaries to the radio payload
(ADD/DROP mode) or to redirect the whole payload from one radio direction to another
one without any access tributary management (Repeater mode) This configuration is used
in the sites where local traffic is collected.
ITP MWR Product Management
Tributaries
PassThrough
Localy AddDropped
AddDrop
2.4.4 2x(1+0)
This solution provides an equivalent two radios back-to-back configuration.
In this case the two directions are treated as separated ones but they are managed by just
one IDU
Tributaries W Tributaries E
2X(1+0)
2.4.5 Ring
RING system type (supported only by 32xE1units) is characterized by two different radio
directions and it employs two ODUs.
ITP MWR Product Management
Its function is to perform a path protection (‘SNCP like’ mechanism): the payload is
transmitted towards the two opposite directions, but it is received from the best direction;
the choice of the receiving direction is based on AIS signal.
B
B’
A
Tributaries ’
Ring
For each E1 terminated on the Access side (A), there is a switch selecting the best of the
two signals coming from the two Base Band units; the transmitted signal is “duplicated” from
the Access side towards both the BB units. B and B’ may be different E1 lines on the two BB
units (for example, line 3 on BB1 and line 26 on BB2).
Each switch is independent from the other ones and switching takes places according to AIS
detection at E1 level; for each protected connection it is possible to set the switch in
automatic mode (switch based on path AIS detection) or to force the position on one of the
two sides by LCT/NMS.
In this way any physical interruption in a Network ring configuration can be bypassed.
2.5 Installation
Indoor unit fits in 19’’ racks and cabinets, as well as in ETSI cabinets or directly on a
desk/wall.
The interconnection between the outdoor unit and the indoor part is a single coaxial cable
carrying full duplex traffic, DC power supply, service traffic as well as operation and
maintenance data.
The ODU can be either mounted directly to the antenna or mounted separately and
connected by a flexible waveguide.
Two Outdoor units, in a protected (1+1) configuration, can be connected to a single
antenna using a power splitter.
In the following pictures, several installation alternatives regarding ODUs and
antennas are shown:
ITP MWR Product Management
INTEGRATED ANTENNA
OUTDOOR
ASSEMBLY
(1+0) Integrated
INTEGRATED ANTENNA
FLEXIBLE WAVEGUIDE
ODU
ODU
INTEGRATED
ANTENNA
(1+1) INTEGRATED
SUPPORTING FRAME
BRAIDED COAXIAL
CABLE
(1+1) Integrated
INTEGRATED ANTENNA
ODU
FLEXIBLE
WAVEGUIDE
(1+1) FRAME
In the following pictures, examples regarding fully outdoor system are shown:
IN/OUT BRAIDED
COAXIAL CABLE
OAU UNIT
(1+0) Integrated
ITP MWR Product Management
INTEGRATED ANTENNA
ODU
FLEX WAVEGUIDE
VERTICAL (1+0)
FRAME
BRAIDED
COAXIAL CABLE
OAU UNIT
3. System Description
The Access Card that represents the physical access of the equipment for the Tributary
streams from the public network, it also includes all the alarms and service channels interfaces.
A memory key containing the configuration parameter is equipped onto this unit.
One Controller Card that includes all the control and supervisory functions. It also contains a
EEPROM for inventory/user data and alarm history
One BaseBand Card, that includes all the base band processing, cable protection and IDU-
ODU auxiliary service channel management
The modular architecture allows obtaining all the other configurations of the IDU (2×(1+0), A/D-
RPT, Ring, (1+1) FD, PD and H/S) by duplicating only the BaseBand unit.
A – 1U Subrack
B – Access Card
C – Controller
D – BaseBand 1
E – Baseband 2(opt.)
Alarm Service
Access
To ODU BB2 Tributaries
BB1
Controller
ITP MWR Product Management
The cards are housed in a 1U high subrack which provides electrical interconnections between
them by means of its backplane.
Cross connect function allows to cross-connect the tributaries signals. Each local E1 input port
can be switched to any E1 tributary output port, at the other side of the link. Cross connect E1
configuration must be set by using suitable software commands, issued via LCT or Netviewer.
E1 tributary can be also connected in path protection mode, used only in Ring system type,
allowing the selection of the E1 signal between the two received signals according to the AIS
selection criteria.
Stuffing / destuffing
Multiplexing of tributary signals (after the stuffing block) into an aggregate frame for backplane
connection. De- multiplexing of the same signals is required in the opposite direction on the
aggregate frame received from BaseBand boards.
Access Card also houses the memory key containing the licence fees (Configuration: (1+ 0) or
(1+1)1 / Traffic Capacity: NxE1 / Modulation format: HD or ND) and all Configuration Parameters.
All Access Card versions provide the same service channel interfaces:
• 2 x User/ Dext Channel (Sw selectable)
• Alarm interfaces.
1
(1+1) licence enables 1+1, Ring, 2x(1+0) and Add-drop/Repeater System Types
ITP MWR Product Management
3.1.2. Controller
The Controller implements the system control functionalities. The main functions are:
Collection of alarms and working parameters from the system units (IDU and ODU);
transmission of this information to a local PC or to a network supervision system
Activation of system commands coming from a local PC or from a network supervision system
(status forcing, modification of equipment parameters, etc.)
Storage on a Memory key of the system configurations and on EEPROMs the inventory / user
data and alarms history.
Routing of messages among controllers and the network supervision system manager
Electrical and protocol translation between the radio environment (which uses a proprietary
protocol channel, embedded in the radio frame, to transport management information) and the
supervision system (which requests that this information is available on a public connector, with
a standard protocol).
Measuring the IDU temperature2: the measurement has 1°C resolution and is updated once
every 15 s.
2
functionality supported by Controller Unit code 634-001/74 from HW edition n°8
ITP MWR Product Management
External I/F
Stuffing BackPlane
Mux I/F
AIS In/Los
D- Emb
Dropping
DEmb to Controller
D- Emb
aDDING DeStuffing BackPlane
DeMux I/F
External I/F
Access Card functional architecture
3.1.3. BaseBand
Regeneration of the 2 Mbit/s input tributary signals in compliance with Rec. G.703 and HDB3 ->
NRZ conversion
Generation of the aggregate frame and multiplexing of the input tributary signals into one main
stream
Scrambling (212-1 length stream seeded at the beginning of each frame, 215-1 for E3)
FEC insertion (Reed Solomon type, with a correction capacity of up to 5 errored bytes per frame)
Interleaving
Generation of a 128 kbit/s auxiliary service channel for the transmission of data channels, alarms
etc., between the IDU and the ODU (inserted into the main stream)
Generation of the switching command for the Tx HW switch
Automatic level control on the signal incoming from the ODU.
Power Supply conversion and distribution
Carry out the hitless switching function between the two aggregate signals when the equipment
has been set to the protected configuration.
Send and receive the following signals from the ODU via the connecting coaxial cable:
– Aggregate stream
– power supply voltage for the ODU
ITP MWR Product Management
From
access unit MUX / Service Scrambling Hitless I/F
DEMUX Drop-Insert FEC Switch cable
Interleaving to ODU
From
access
unit
HW Control
Logic to ODU
to CTRL
BaseBand 16xE1
BaseBand 32xE1
BaseBand E3
Each of these cards has to be used in conjunction with the relevant Access Card. The Ethernet
Access Card works in conjunction with BaseBand 16xE1.
ITP MWR Product Management
The SingleBoard2 IDU adopts a monolithic architecture, consisting in a single replacement unit,
tailored on a selected set of features. It is available in the following hardware versions:
8xE1 (1+0)
16xE1(1+0)
16xE1(1+1)Hsby
The listed configurations are related to the maximum hardware capacity: the wanted set of features
can be enabled by means of a user fee mechanism, within this constraint. Protected Configuration
is provided with ODU redundancy only.
In the Figure the block diagram of the IDU architecture is shown.
CONTROL BUS
SIGNAL BUS
POWER SUPPLY BUS
The Power Section provides the interface to the external Power Supply.
The Control Section is in charge of the management of the complete system, and provides the
interfaces to the supervision systems.
Tributary Section interfaces the equipment to external tributaries and user-available signals.
Regeneration of the 2 Mbit/s input tributary signals in compliance with Rec. G.703 and HDB3 ->
NRZ conversion
Generation of the aggregate frame and multiplexing of the input tributary signals into one main
stream
Scrambling (212-1 length stream seeded at the beginning of each frame, 215-1 for E3)
FEC insertion (Reed Solomon type (152,142), with a correction capacity of up to 5 errored bytes
per frame)
ITP MWR Product Management
Interleaving
Generation of a 128 kbit/s auxiliary service channel for the transmission of data channels, alarms
etc., between the IDU and the ODU (inserted into the main stream)
Automatic level control on the signal incoming from the ODU.
Power Supply conversion and distribution
3.3. Outdoor Access Unit
The Outdoor Access Unit implements all access and baseband functions in a waterproof case
suitable for outdoor installation.
The mechanical structure of the OAU consists of a compact sealed box suitable for wall mounting
and pole mounting.
Suitable flanges are foreseen for the installation of the OAU into ETSI and/or 19” rack.
The OAU works with all ODU versions in all the frequency bands.
The connection between the waterproof unit and the ODU is performed by means of a coaxial
cable carrying traffic, power supply and management information.
ITP MWR Product Management
IF+RF block: it is responsible for up/down conversion of In-Phase and Quadrature signals to
the desired RF/IF frequency.
The Outdoor Unit adopts a Frequency Division Duplexing technique as showed in the relevant
ETSI recommendations. RF transmitter’s and Receiver’s frequencies can be set by the user
through the system Controller by means of SW command. Tx and Rx frequencies are joined by the
shifter value: any change of Tx (Rx) frequency automatically involves the change of Rx (Tx)
frequency according to the ODU’ shifter.
The figure below shows the ODU functional view.
POWER BUS
CONTROL BUS
SIGNAL BUS
DUPLEXER
RSSI IDU / ODU CABLE ANTENNA
ITP MWR Product Management
The RF unit and the Duplexer are the only frequency dependent blocks. Within a frequency band,
typical a quarter of band tunability is obtained trough independent Tx/Rx synthesized VCOs with a
step size of 250 kHz. Three external interfaces are available:
IDU/ODU Cable allows the connection of the coaxial cable carrying traffic power and
supervision information
RSSI (Received Signal Strength Indicator) interface allows to get information about the
received RF signal level by a standard voltmeter as measuring instrument.
Antenna interface allow the direct connection of an antenna or of flexible waveguide. It
adopts a standard PBR or PDR flange depending on the frequency bands.
3.4.1. ODU ND
The Normal Density ODU is composed of two main boards and the duplexer.
RSSI
ANTENNA I/F
Power
Section ⊗
ATPC
I
F SINTH TX VCO
VCO XN
Cable
C I/F
A
B µC? C
L
E
SINTH RX VCO XN
M
O
AGC
D
E
M
⊗ LN
The High Density/ High Performance ODU allows the selection, via SW, of the modulation format:
16 TCM or 4QAM.
The Outdoor Unit is composed by the following subunits:
Power
Supply
To/From Duplexer
To/From IDU
MODEM/IF
UNIT MWTF
Dual VCO
The aggregated signals, coming/sent from/to the IDU are treated in the Modem/IF subunit. The IF
signal is filtered and sent to the transmitter to be up-converted to the microwave band. An output
power control facility moves the transmitted power level in Output Power range. The Rx IF signal,
coming from the receiver is demodulated and sent to the IDU. The IF unit houses the cable
equalizer, the PLL circuits, a frequency reference oscillator (TCXO) and a microprocessor
controller unit for the management of the hardware inside the ODU. The dual VCO unit provides a
very low phase noise UHF signals to synchronize a couple of RF VCOs placed in the Microwave
Transceiver Front-end (MWTF). The MWTF interfaces the microwave filter diplexer which insures
the required decoupling between transmitter and receiver subunits.
This ODU, besides the same functionalities of ODU HD/HP3, provides also the support of 32xE1
capacity in 28MHz with 16TCM modulation.
Moreover, it is fully backward compatible with ODU HD/HP, in order to be used as spare part of the
previous family.
The High Density enhanced ODU is composed of two main boards.
• Modem unit: it is in charge for power supply function, control function, cable interface
management and modem function (4QAM/16TCM modulation). This board contains all
processing which is common for all RF bands
• RF/IF unit: it is in charge for up and down conversion from the modulated signal to RF
frequency. The RF/IF unit architecture is different for each band.
3
Except the 2xE1 capacity in 3.5MHz that is not supported
ITP MWR Product Management
The system provides two different setting modes of the operating frequencies:
Continuous frequency: The user can set for the transmission frequency every value comprised
into the operating band of the equipment with a step of 250 Khz. It is necessary to set manually the
values of the transmission and reception RF frequencies. It is sufficient to set one of the two RF
frequency values, because the system automatically calculates and sets the other one according
to the shift frequency. The user can set every value of the frequency, but this value must be within
the operating band of the ODU (TF Min and TF Max).
Frequency plan: The user can arrange a channelling plan that stays inside the operating band
of the equipment. The numbers of the channel are dependent on operating band and transmission
capacity.
Each couple TX Freq- RX freq is identified by a Channel Number that can be used to set the
operating frequency.
Fixed/RTPC
This power setting mode allows the user to select the output power of Tx chain, with 1dB
granularity, within the Output Power Range allowed by the ODU version.
ATPC
ATPC (Automatic Transmit Power Control) feature allows to modify the remote transmit power
automatically, in order to limit interference while guaranteeing certain quality performance in the
local radio unit, even if a fading event has affected the radio channel: the far side terminal sends a
signal regarding the received signal level and the near side terminal adjust its transmit power in
order to meet a wanted RSL (named ATPC Threshold, can be set by the user) on the far side. The
remote ODU ask an increasing or decreasing of the TX power on the basis of the comparison of
received signal power compared to ATPC Threshold value.
If the received power is in the range ATPC_Th ± 3dB, the command transmitted to the remote side
is not o modify the transmit power (note that the value 3dB is fixed). For lower received power
levels the command is to increase the power (1 dB) whereas for higher power levels the command
is to decrease the power (by 1 dB). In ATPC mode the output power can be modified in the range
PminATPC ÷ PmaxATPC. The parameter Pmin ATPC can be set by the user in all ODU version.
Pmax ATPC is fixed to maximum output power provided by the ODU for ND ODU, while it can be
configured by the user for the ODU HD/HP and HDe by means of the parameter ATPC Range
(note that PminATPC+ATPC Range has to be less or equal to PTmax provided by the ODU).
Received Power
PmaxATPC
PminATPC
ITP MWR Product Management
ITP MWR Product Management
In (1+1) H/S System Type, if ATPC is disabled, it is necessary to specify the value of the coupling
loss (Coupling Loss parameter) for the RF connection of ODU, since RF TX power should be the
same for the active and protection chain.
This value depends on the hardware used for the implementation of the (1+1) Hot-Standby
protection (allowed range of RF couplers loss is between 0 dB and 15 dB).
Coupling loss parameter is used to increase the internal Tx power of the same value of the RF
coupling loss, in order to have the desired power level after the RF coupler.
For instance, when the unbalanced coupler is used, the coupling loss parameter for the Stand-by
ODU is set to 10 dB, so that when the switch occurs its tx power is increased of 10 dB (anyway it
can’t be raised over Pmax ; PS-by ODU =min (Pmax , PAct-ODU + 10)).
ITP MWR Product Management
The system in both (1+ 0) and (1+1) configurations allows integrated as well as separately
mounted antennas. In case of integrated mounting, the outdoor unit is directly mounted onto the
rear of antenna without any waveguide connection. The antenna is provided with a bracket to be
mounted on a pole. The antenna mounting supports the outdoor unit, which is easily removable by
means of simple retaining latches.
In case of remote mounting, a flexible waveguide is provided for the connection of antenna to the
ODU
ITP MWR Product Management
The (1+1) hot stand-by configuration on a single antenna is provided by means of a coupler in
Balanced or Unbalanced version. The supporting frame can be mounted directly on the rear of the
antenna or separated (pole, wall).
ITP MWR Product Management
PROTECTION COVER
O-RING
PROTECTION COVER
The cross-connect functionality is available only for Plug-In version. It allows, by means of SW
setting, to cross connect the tributary interface toward the Radio Interface, both in Unprotected and
Protected configuration.
Tributary Side
Radio Side 1
Radio Side 2
“Unrestricted” Cross Connection functionality for all System Types (1+0, 1+1, Add-
drop/Repeater) is provided.
Added tributaries: it is possible to add/drop all 16 Radio tributaries for each Radio side.
Pass-through signals: it is possible to cross connect all tributary signals “West side” of any
position with tributary signals “East side” of any position
ITP MWR Product Management
1 1
16 16
1 16
Tributaries
For all system types (1+0, 1+1 Hot Stand-by/FD, A-D/Repeater, Ring) a full cross-connection
matrix is supported: each of the 32 E1 lines of the Access (tributary) side can be connected to any
of the 32 E1 lines Base Band side.
In case of Ring system type with 32xE1 radio capacity the cross-connection matrix supports only
32 connections of any type (theoretically 48 connections should be available) because of the
following limitation: each connection involving a tributary line reduces by one unit the amount of
available pass-through connections and vice-versa.
32 32
1 32 Tributaries
ITP MWR Product Management
This functionality simplifies the configuration of the NE when changing from one system type to
another.
In the following table the behavior of the cross-connection matrix in case of system type change
(keeping the same access unit) from type A to type B and viceversa is shown:
5. Ethernet functionalities
Ethernet functionalities are available on IDU Plug-In platform by means of a dedicated Access
Card, featuring a mixed TDM and Ethernet interface: 8xE1 and 4x10/100 BaseT, and supporting
L2 switching and QoS management.
The selected on-air capacity (trunk port capacity), is shared between Ethernet Traffic and PDH
traffic as showed in the diagram below.
Radio Capacity
LAN port 1
S LAN port 1
LAN port 2
R Ethernet LAN port 2
LAN port 3
A (Trunk capacity) LAN port 3
LAN port 4 L LAN port 4
X
TDM
TDM D
TDM
The capacity reserved for Ethernet traffic is dynamically shared among the 4 LAN ports according
to QoS setting.
Ethernet frames transmitted towards the radio are inserted in a NxE1 channel, with N configurable
between 1 and 16, with a resolution of a single E1. N synchronous E1 signals are generated by a
framer, according to the configured Trunk side capacity, while a proprietary mapping of the
Ethernet frames into the NxE1 channel is performed by a mapper device. On the receiving side, N
E1 de-framers and a demapper retrieve the original Ethernet frame transmitted by the remote
station.
A block scheme of the Data interface unit is shown in the following figure.
ITP MWR Product Management
E1Framer/Deframer
Mapper/Demapper
Cross To BB card
Connect
Scheduler
Trunk Ports
Switching Block
Each LAN port can be individually enabled/disabled .LAN interface is auto sensing (10 or 100
Mbit/s, half or full duplex); in any case it is possible, via management software, to set half/ full-
duplex or auto-sensing mode as well as 10, 100 Mbit/s capacity. Ethernet frames with a length up
to 1536 bytes are supported by LAN ports.
5.1. Switching
The DATA Access unit implements an Ethernet bridge that has the function of Ethernet switch and
manages the access on Ethernet interface to the BB cross-connection matrix.
The L2 Switching is performed among the following Ethernet ports:
Four LAN ports: input/output ports on LAN network of the traffic Ethernet frames
Trunk port: it is the input/output port of the Ethernet traffic towards the radio link.
Each LAN port can be enabled/disabled and configured by the user, while the Trunk port
is always enabled.
The switching can be performed on the basis of the MAC Address or the VLAN ID.
The switching functionalities are subdivided in Filtering the Ethernet frames and Forwarding them
among the available ports.
5.1.1. Filtering
Filtering is performed according to the source MAC address of the incoming packets.
Source MAC addresses received from LAN Ports are stored, along with the corresponding port the
frame was received from (LAN and Trunk), in a data-base (MAC DB) which is continuously
updated (Auto-learning mode). Each entry is stored within a configurable aging-time.
ITP MWR Product Management
Frames received from a port are discarded if the destination MAC address matches one of the
MAC addresses contained in the data-base and the input port is equal to the one contained in the
data-base.
Also frames received from or sent to a disabled port are discarded.
In case of VLAN-based switching, filtering rules are based on VLAN ID, too (see following section).
5.1.2. Forwarding
All filtered frames are forwarded among the ports according to the selected forwarding mode:
- if it contains a VLAN tag that is not included in the list of the VLAN tags associated to the input
port
- if the destination MAC address is stored in the MAC DB and the corresponding port is not
included within the ports associated to the VLAN ID contained in the frame.
Each received frame containing a VLAN ID associated to the input port is sent:
- to only one of the other ports associated to the VLAN ID contained in the frame, if the destination
MAC address is stored in the MAC DB and the corresponding port is included within the ports
associated to the VLAN ID contained in the frame
- to all the other ports associated to the VLAN ID contained in the frame, if the destination MAC
address is unknown.
- if the frame contains a VLAN tag, there is the replacement of the VLAN ID contained in the frame
with the VLAN ID associated to the input port
- if the frame does not contain a VLAN tag, there is the insertion, into the frame, of a VLAN ID
equal to that associated to the input port.
Frames entering the switch from the Trunk port contain a VLAN tag otherwise they are discarded.
Frames are internally forwarded according to the same rules explained for the selective VLAN
forwarding mode. VLAN tag is removed from Ethernet frames exiting from LAN ports, whereas
frames exiting from Trunk port keep their VLAN tag.
5.2. Scheduling
QoS management is provided by Scheduling in upstream direction (from User side to Radio side)
used to transmit data frames with different priority on the radio channel, according to one of the
following criteria or possibly a combination of them:
• first arrived first served (no priority);
• LAN port;
• content of the Ethernet User Priority field in the Ethernet frames (“802.1p”);
• content of the ToS/DiffServ field of IPv4 packets or the Traffic Class field of IPv6 packets
(“IP based”).
The last three criteria are separately enabled on a per port basis according to software
configurations. In case of more than one criterion enabled, LAN port has the lowest priority, while it
is possible to select the priority classification between “802.1p” and “IP based”.
In the scheduler, up to 4 different queues are available, according to the selected criteria and the
enabled options.
ITP MWR Product Management
F F Queue 1
I O
L R
T W Queue 2
E A
R R Queue 3
I D
N I Queue 4
G N
G
SCHEDULER
Selection of the frame to be transmitted from the different queues towards the radio is done
according to a fixed priority scheme or using a WFQ algorithm with fixed weights.
If Fixed priority is selected, frames with higher priority are always transmitted first.
WFQ allows to share the channel bandwidth among the four different priority levels. The four
weights are fixed and respectively equal to 8, 4, 2 and 1.
ITP MWR Product Management
6. Management
6.1. DCN
In the SRAL XD product line, system concept and embedded software architecture have been
designed to permit a user-friendly and effective local and remote terminals’ management.
TCP/IP Communication protocols and standard physical interfaces have been adopted to simplify
and speed up DCN implementation and to allow an easy integration in 3rd party Management
Systems.
OMC
DCN
SRAL XD
The management information are stored and processed by the NE controller and made available
externally to the network operator through standard interfaces:
■ Q LAN 10/100BaseT:
The Q LAN interface carries the Transmission Network Management (TNM) information used by
Operation and Maintenance Center (OMC) to manage the network nodes. The Q channel can
operate with auto-negotiation both half duplex and full duplex, both 10 BaseT or 100 BaseT.
VLAN
VLAN
HUB
VLAN
The V LAN interface together with the Q LAN makes available the connection, throughout Tx/Rx
crossover cables, among more equipment Controllers of the same site and the OMC without
applying external elements.
QLAN VLAN
QLAN VLAN
QLAN VLAN
Allows to carry the management information through a data network. The standard PPP over
HDLC is the protocol of this channel for the interconnection with third part equipment (routers).
The D-ext channel also allows the connection with SRA L equipped with V.11 card.
55
Not available on Outdoor Access Unit
ITP MWR Product Management
NE
The interface is fully routed and routing protocol announcements are supported (dynamic routing
and associated announcements can be switched on or off by NMS for this interface).
■ D-Embedded Channel7
It is a 64kbps channel framed in a single time slot inside one E1 stream. The time slot and the
specific E1 stream8 can be set via software. D-Embedded channel is used to carry the
management information between two NEs, that are not connected by means of any other
transmission media.
6
Not available on Outdoor Access Unit
7 In case of IDU PI 16xE1 in 2x(1+0) or Add/Drop system types, two D-emb channels are available.
8
In case of IDU PI 16xE1, only tributaries 1÷4 Radio-side can be used for D-emb channel transport; in case of IDU 32xE1 any
tributary radio-side can be used for D-emb channel transport.
ITP MWR Product Management
PSTN
D-Embedded
D-Embedded
NE
NE NE
R Channel
■ V bus Channel
The V bus interface is available on IDU Plug-in controller in order to interconnect SRA L equipment
located in the same station. The V bus channel utilizes a proprietary protocol. Up to 32
independent SRA L units placed in the same site can be connected to the V-bus 120Ω cable.
■ R Channel
R channel is a 64 kbps out of band channel accessible only via the controller, that carries
management IP packets over the radio interface.
The interface is fully routed and routing announcements are supported (dynamic routing and
associated announcements can be switched on or off by NMS for this interface). Standard PPP
protocols over HDLC
R CHANNEL
O User CHANNEL
D
U Payload
RS 232
DEmbedded
Traffic
provided for local management and maintenance. This interface can be also used for DCN
purpose.
ITP MWR Product Management
In order to increase efficiency and reduce staff training time, NetViewer supports different
interfaces to the Data Communication Networks (DCN) giving a wide level of freedom for creating
networks of different sizes. For controlling DCN, often designed with devices based on SNMP
protocol such as routers and interface converters, the SNMP device management performed by
NetViewer allows the complete monitoring of all the Network Elements included in the network.
NetViewer supplies the HTTP interface enabling the user to access it via Internet and Intranet
using browsers as Netscape and Microsoft Explorer for supervisioning the SRAL XD networks.
The tunnelling of IP over OSI allows a SRAL XD network to be connected to the TMN of a SDH
network
This integration gives the big advantage of having an integrated solution for the management of a
mixed PDH-SDH network. This advantage is further highlighted by the fact that the Nokia Siemens
Networks SDH operating system can also perform the network control layer facilities.
Nokia Siemens Networks Management System portfolio also comprises TNMS Core (Nokia
Siemens Networks SDH TMN platform) and Radio Commander (Nokia Siemens Networks Mobile
TMN platform).
Also devices of different vendors based on SNMP protocol can be managed by NetViewer.
ITP MWR Product Management
INTRANET
INTERNET
Local Management and Maintenance of the SRAL XD is performed by LinkViewer, the Element
Manager running on LCT.
7.1 Security
The access to the equipment, by means of LCT/NMS, is allowed to authorized users on the basis
of three different user classes:
Read Only:
Read/Write:
Admin
The configuration of the Security (enabling status and password) is stored into the equipment
memory.
Password of both FTP and Telnet Admin user is the same as TNMP Admin user class password. It
isn’t possible to directly modify the FTP and/or Telnet Admin password, but any change in the
TNMP Admin password affect s both the FTP and Telnet Admin password.
NE embedded SW includes an SSH server running SSH-2 protocol version and supporting file
transfer and remote command execution. SSH functionalities (enabled/ disabled via TNMP
configuration) allow user authentication and traffic encryption between two hosts, thus improving
the security of communication.
User authentication/ authorization is password-based (the password is linked to TNMP Admin
password).
File transfer is carried via sftp protocol (same users and passwords used by FTP are supported),
whereas remote command execution is carried via ssh: this sw tool is similar to TELNET but
commands, passwords and data are encrypted.
The Accounting log functionality allows storing in the NE (non volatile memory) a list of up to 120
records of relevant log actions (login or logout) performed by users.
When the reserved memory is full, a new log action will cause the oldest one to be deleted
(overwritten by the new one). Each record will include the following information fields:
IP address of the user;
user class (Admin, Read Write or Read Only);
log action;
date and time of the log action.
The accounting Log file is available uploading a file via FTP.
The Status and Config function allows checking the operating status of the equipment and
configuring, according to the available hardware and license, all the system, operating and network
parameters.
In case of protected configuration it is needed to set the TX/Rx channel for just one ODU, the
second one will be aligned automatically by the SW command RF Channel Self Alignment
ITP MWR Product Management
The SRAL XD provides a set of feature for support during commissioning activities in order to
monitor the performance of the NE during a stated period of time and the correct working of
protection switching allowing to force each available switch.
PM R ecording duration
(192 15’ periods)
From Start Tim e
Tim e
G et results
It allows forcing the switch position for a certain period (selected by the user). The following
options are available:
- Single sequence
- Periodic (for Hot Stand-by System Types): the switch is forced every n days (n=0÷400), in order
to verify the integrity of the complete Stand-by transmission chain.
Stand By
Working
Repetition Period
ITP MWR Product Management
This feature supports the recovery of the recent history of the appliance: the Network Element
controller saves in its volatile memory the last 4000 events and pseudo-events.
It is possible to retrieve both a subset of events and pseudo-events to complete a missing portion
of the Network Element history (for example in case of temporary disconnection of the NE from the
NMS) and the complete saved “history” (for example a local download from NE not connected to a
network management system)
7.3.4 Measurement
The NE allows the measurement of the following parameters by means of both LCT/NMS:
Inner temperature of the ODU
Inner temperature of the IDU (functionality supported by Controller Unit of IDU Plug-in10):
Received power (RF RX) and transmitted power (RF TX)
Statistic measures of the Ethernet traffic interface (only for DATA Access unit)
The system allows the execution of the analysis and the recording on file of the performance data.
Several types of performance data are available:
quality and unavailability counters, applied to the aggregated radio signal, measured in
according to ITU- T G.826 recommendation
RSPI (Radio Synchronous Physical Interface) parameters, applied to each transceiver, and
mainly related to the received and transmitted power
RPS (Radio Protection Switching) event counters, applied to each switching functionality
Measurements periods are 15 minutes or 24 hours; besides the current periods, the NE stores the
last 16 completed 15 minute periods and the last 4 completed 24 hour periods.
There are 3 major measurement points:
10
Code 634-001/74 from HW edition n°8
ITP MWR Product Management
Radio Interface #1
Protection
Switching
Radio Interface #2
Mesurement Point
After protection
Configuration of performance data is possible in case of login (via NMS or LCT) with read/write
privileges; collected data can be displayed on a quarter of hour basis (current quarter of an hour
and sixteen previous ones) or on a daily basis (current 24 hours and previous four intervals of 24
hours).
Netviewer /LCT allow recording on file of the performance data referred to quarters of hour,
according to the selected System type.
The SRAL XD equipment is provided with an alarm system, with different signaling modes (via
software, LED, connector outputs), that starting from an alarm signal allows to the operator to
identify quickly the failed module or function.
Software Alarms are reported on LCT/NMS and are organized in different groups:
Physical
TX/RX
Tributary
Network
Station
Each board is equipped with some LEDs reporting alarms related to the board.
Moreover, the IDU is equipped with an Alarms Connector carrying a number of signal lines,
associated to these main functionalities:
11
Functionality supported by IDU Plug-in and OAU
12 2 input alarm lines are supported by OAU.
ITP MWR Product Management
Delivery11 to the outside of radio equipment of the 412, externally supplied, alarm lines
transported via radio link from the far-end
7.5 Maintenance
Local loop-back
The E1 tributary signal can be looped back in the base-band unit at the E1 input interface level.
This type of loop-back when activated allows testing the integrity of the circuitry related to line
interface access.
E1 E1
Local loop-back
Remote loop-back
Each E1 tributary stream can be looped back in the remote station, just before the E1 output
interface. This type of loop-back when activated allows testing connection integrity between two
terminals, with the only exception of the E1 physical output drivers of the remote terminal.
E1 E1
Remote loop-back
Each available E1 tributary (i.e., each enabled tributary) can be looped back either locally or
remotely by properly configuration.
The SRAL XD implements SNTP according to RFC 2030. This protocol is designed to synchronize
the clock on the NE with the clock on network time servers, thus offering synchronization accuracy
higher than the one obtained via Netviewer synchronization mechanism.
The NE performs a clock update by placing a SNTP request to the configured server in the
following occasions:
- At NE controller reset (if the address is already set to a meaningful value).
-Every 2 hours (related to 50 ppm clock precision combined with a requirement to avoid
corrections greater than 0.5 seconds that would bring to a wrong interval duration in performance
monitoring data) since the last NE controller reset.
- When the IP address of the time server is changed. In such a case an additional “asynchronous”
request is performed; then the next request will be performed respecting the 2-hour period with the
origin corresponding to the controller reset.
If the SNTP is disabled the NE synchronization is performed via Netviewer.
Use of NAPT (Network Address Protocol Translation) for F interface allows saving the IP address
to be reserved to LCT: a private IP address is assigned to LCT, and the NE completely masks the
private IP address when it communicates with another NE of the “public” network.
In the following figure the effects of NAPT on the IP packets routing process is shown:
LAN ...
R1
interface
interface
When NAPT is enabled, the private IP address of the LCT is changed into the NE IP address by
the NAPT process. F interface is hidden to the router by the NAPT protocol; the real LCT IP
address is “masked” by NAPT and it is not present in the routing table.
When NAPT is disabled (default condition) a “public” IP address must be reserved to LCT.
7.8 OSPF
NE supports not only RIP as dynamic routing protocol, but also the Open Shortest Path First
(OSPF) Version 2. The selection between RIP and OSPF is enabled via SW license and the two
protocols are mutually exclusive (cannot run at the same time in the same NE).
ITP MWR Product Management
OSPF is a link-state routing protocol, whereas RIP is a distance-vector routing protocol. The
former runs directly over IP, whereas the latter uses UDP as intermediate layer.
OSPF offers several advantages compared to RIP:
• Routers using OSPF have a better knowledge of the network topology than routers using RIP,
so forwarding decisions can be more accurate.
• It is possible to use variable length sub-netting; this results in saving IP addresses.
• It is possible to reduce both the protocol traffic and the router processing time by applying
network summarizations (this implies a proper network addresses design).
• There is no theoretical limit to the number of hops the protocol is allowed to handle.
• In stable network conditions a very low traffic is generated to keep all the routers updated.
• When the network topology changes, OSPF should reach a new stable situation in a shorter
time than RIP.
• Inter-working with 3rd party equipment supporting OSPF is easier and faster (no need of static-
routes setting)
8 Software Download
The equipment software is composed by the set (build software) of all the units’ software.
The equipment units, provided with software/firmware, are the following ones:
Controller unit
FPGA module(s) of BB unit
FPGA module of Access unit
ODU
The unit that manages the equipment operation is the Controller unit. It is a unit with
microprocessor, provided with two banks of non volatile memory, over which it is uploaded the
equipment software: one bank is active, the other one is a standby one.
The standby bank ensures the redundancy of the equipment software and it operates if the active
bank fails; the system uses the standby bank also for the download of the equipment build
software.
The ODU is provided with a non volatile memory bank (two banks on ODU HDe), over which the
system uploads the corresponding unit software only.
Into the FPGA modules of the Access and BB units, the system uploads the firmware at the
starting-up of the Controller unit.
From LCT/NMS, it is possible via FTP to execute the download of the equipment build software,
without any interruption of Controller operation.
The download procedure via FTP uploads the software build on the standby bank of the Controller
unit only; the system keeps running the pre-existing software on the active bank of the Controller
unit and on the other units.
To make active the new build software, it is necessary to execute the switching of the banks on the
Controller unit.
The switching operation runs the new version of the Controller unit software; on the other units, the
system keeps on execution the pre-existing software. Then, the Controller unit executes the
ITP MWR Product Management
comparison between the versions of the unit software present into the build software uploaded
over the active bank and the versions of the unit software currently on progress, signalling the
possible misalignment situations.
From NetViewer/LCT, the user can, by means of manual command, execute the software
alignment of every unit: this procedure consists in the download operation of the unit
software/firmware (ODU SW or FPGA firmware) from the active bank of the Controller unit to the
unit (Access, BB or ODU) memory.
The download of the build software can be executed as through local mode as through remote
one:
local download: from LCT (on F interface or on Ethernet Q/V interface)
remote download: from LCT and from NetViewer
ITP MWR Product Management
The Engineering Order Wire (EOW) is an external unit used to provide a Voice Service Channel
and inter-working capabilities between SRAL XD and other MW appliances.
The EOW external unit is composed of a standard 1U high IDU that may be mounted on a
standard rack.
The subrack can be equipped with one or two EOW cards.
EOW Layout
4 wires
intra-office
analogue link
SRAL XD SRAL XD
SRA4 SRA4
V11 V11
10 VoIP
Voice Service Channel via IP on a single link is available through V LAN interface. Recommended
voice codings are G.723 and G.729 in order to reduce the bandwidth occupation of the voice
channel. Anyway, Nokia Siemens Networks strongly advice to utilise VOIP phones that have been
tested and homologated in conjunction with Nokia Siemens Networks MW equipment.
ITP MWR Product Management
ITP MWR Product Management
11 Alarm converter
Alarm Converter is a device which collects 24 external alarms and provides 24 output commands.
The Alarm Converter, 1/2 U high, adopts a monolithic architecture, consisting of a single
replacement unit; and it is supplied with dedicated brackets suitable for assembly in 19"or ETSI N3
racks.
On the frontal the following connectors are present:
- 1 sub-D 3W3 connector for the -48V power supply
- 1 RJ-45 connectors for the Ethernet interface (Q interface)
- 1 sub-D 9 connector for LCT interface (F interface)
- 1 sub-D 25 connector for the 24 inputs
- 1 sub-D 25 connector for the 24 outputs
A dual-color LED (green/red) is available on the front panel to indicate power On/ Card Fail
condition.
LCT
Siemens MNG COMMAND OUTPUTS ALARM INPUTS Card -48V Battery
Fail
_
+
An example of appliance scenario concerning Alarm remotization is shown in the following figure:
ITP MWR Product Management
Node D
CMD 1-8 (from Node A)
Alarm CMD 9-16 (from Node B)
converter CMD 17-24 (from Node C)
Q interface
Q interface EMS
Microwave
DCN network
Q interface
Q interface Q interface