Escolar Documentos
Profissional Documentos
Cultura Documentos
Product Overview
Module 1
Introduction
Module 2
Architecture
Section 2
Functional Description
Module 1
Module 2
Module 3
Module 4
Module 5
Module 6
MPT-GC
Module 7
Protection
Section 3
Terms
Module 1
Acronyms
Document History
Edition
Date
Author
Remarks
3.4
2012-06-14
AL University
First edition
4.0
2012-07-30
AL University
Page
1 Understanding the 9500MPR Innovations
1.1 Classification of the New Generation Products
1.2 Classification of the New Generation Products
1.3 Presentation
1.4 Multiservice Aggregation Layer
1.5 Service Awareness
1.6 Packet Node
1.7 Service-driven Packet Adaptive Modulation
1.8 Power Consumption Reduction
1.9 Hybrid or Packet Mode: for Efficient Data Transport
2 MPR in New Market Segments
2.1 The Most Effective Solution
2.2 MPR-e Enabling Zero-Footprint Microwave Configurations
2.3 MPR in Last Mile
2.4 LTE and Full Ethernet 3G Ready
2.5 PDH/SDH Network to Packet Transport Network Evolution
2.6 MPR addresses All Microwave Applications in Aggregation
2.7 MPR addresses Metro Ring/Partial Mesh Application
3 System Description
3.1 Alcatel-Lucent 9500 Microwave Packet Radio
3.2 9500 MPR System Family
3.3 9500 MPR Key Features
3.4 9500 MPR Node
3.5 9500 MPR Terminal
4 Radio Configuration
4.1 Radio Configuration
5 System Configuration
5.1 Example of System configurations
6 Management Systems
6.1 Network Management
7
8
9
10
13
14
15
16
17
18
21
22
24
25
26
27
28
29
31
32
33
35
37
46
51
52
53
54
59
60
Page
Notes:
Multiservice aggregation layer - the capacity to use Ethernet as a common transmission layer to
transport any kind of traffic, independently by the type of interface. Ethernet becomes the convergence
layer.
Service awareness - traffic handling and quality management, queuing traffic according to the type
of
Packet node - no service aggregation limits with all traffic aggregated in packets, in term of: capacity,
type of service requirements and type of interface
Service-driven adaptive modulation- fully exploit the air bandwidth in its entirety by changing
modulation scheme according to the propagation availability and allocate transport capacity, discriminating
traffic by different services, only possible in a packet-based environment
Notes:
9500 MPR aggregates and carries over a COMMON PACKET LAYER: TDM 2G, 3G, LTE and IP/Ethernet.
This allows sharing of common packet transmission infrastructures, regardless of the nature of carried traffic.
Due to the nature of Ethernet, each service can be discriminated based on several parameters like quality of
service.
Mapping different access technologies over Ethernet is achieved by standardized protocols like circuit
emulation and pseudo-wire.
ISAM (Indexed Sequential Access Method) - a method for indexing data for fast retrieval
WCDMA (Wideband Code Division Multiple Access) interface standard found in 3G mobile
telecommunications networks.
WiMAX (Worldwide Interoperability for Microwave Access) - telecommunications protocol that provides fixed
and mobile Internet access
HSDPA (High Speed Data Packet Access) - add on to R99/UMTS networks which adds a shared high speed
downlink packet channel
UMTS (Universal Mobile Telecommunications System 3rd generation mobile cellular technology for GSMbased networks.
Notes:
Service awareness means the ability to discriminate the different traffic types carried over the converged
Ethernet stream. Our traffic flow can be composed of E1, E3, STM-1, ATM, DS1, DS3, and/or IP/Eth, coming
from different sources, and therefore having different requirements. For instance, DS1 or ATM traffic from a
3G base station can carry voice (high priority, real time service) and data (lower priority and possibly non
real time with high variability load, such as internet browsing, music download or video streaming).
Service awareness is what allows identifying the traffic types, and in the case of non real time variable bit
rate one, optimize the band with overbooking of the radio scarce resource.
Notes:
9500 MPR offers a SINGLE PACKET MATRIX able to switch, aggregate and handle any of the possible
incoming traffic types with virtually no capacity limits (up to 10 GB/s).
Note: The TDM can be also E3.
The MSS can also provide Gigabit Ethernet (GigE) and metallic uplinks.
Packets can be transported over Ethernet or PDH in any direction, avoiding service aggregation bottlenecks
in terms of capacity, service types and interface types.
Notes:
Traffic with high priority will always have bandwidth available, like voice (deterministic approach)
Broadband traffic is discriminated by QoS dynamically, with modulation scheme changes driven by
propagation conditions.
Notes:
This true packet product is not based on TDM (circuit-based) technology, so it efficiently transports multimedia
traffic by handling packets natively while still supporting legacy TDM. It also adapts packets to the air
conditions and quality required by different service types. This product improves packet aggregation, increases
bandwidth, and optimizes Ethernet connectivity.
Notes:
DSL
E1
E3
34 Mb/s interface
Eth
Ethernet
GigE
Gigabit Ethernet
IMA
MPLS
PDH
T1
Notes:
Extended 9500 MPR packet transport family to cover last mile access MSS-1c
n
Multipurpose ODU the MPT; to cover all MW applications under a single platform
n
Low cost, rack length, Very low power consumption, MW radio protection, Hybrid & Packet operational modes
Zero foot print for Ethernet applications, common to all MSS platform, enables integrated solution for MPLS metro
network
Notes:
CAC (Call Admission Control) - prevents oversubscription of VoIP networks. It is used in the call set-up phase
and applies to real-time media traffic as opposed to data traffic.
DWRR (Deficit Weighted Round Robin) - is a scheduling method for packets of variable size. A maximum
packet size number is subtracted from the packet length, and packets that exceed that number are held back
until the next visit of the scheduler.
Notes:
IMA (Inverse Multiplexing over ATM) - a standardized technology used to transport ATM traffic over a bundle
of T1 or E1 cables where a stream of Asynchronous Transfer Mode cells is spread over multiple physical
links.
Notes:
9500 MPR in the stand alone (zero-footprint) architecture is built by only one unit for Ethernet applications:
Outdoor Unit.
Outdoor Unit is connected to the MPLS metro networks equipment with one coaxial cable for the power
supply and one Ethernet optical or electrical cable (with MPT).
9500 MPR in the split mount architecture is built by two separate units:
MSS (Microwave Service Switch): indoor unit for split mount and stand alone configurations (Ethernet
uplink)
Outdoor Unit.
MSS and Outdoor Unit are connected with a single standard coaxial cable (with ODU300) or with one
coaxial cable for the power supply and one Ethernet optical or electrical cable (with MPT).
Notes:
Link Aggregation groups a set of ports so that two network nodes can be interconnected using
multiple links to increase link capacity and availability between them.
When aggregated, two or more physical links operate as a single logical link with a traffic
capacity that is the sum of the individual link capacities.
This doubling, tripling or quadrupling of capacity is relevant where more capacity is required
than can be provided on one physical link.
Link aggregation also provides redundancy between the aggregated links. If a link fails, its
traffic is redirected onto the remaining link, or links.
If the remaining link or links do not have the capacity needed to avoid a traffic bottleneck,
appropriate QoS settings are used to prioritize traffic so that all high priority traffic continues to
get through.
The Link Aggregation is performed according to 802.3ad and can be applied to Radio ports and
to User Ethernet ports.
Notes:
The 9500 MPR Node supports up to 18 RF links for operation on the same or different frequency bands using
the MSS-8.
The ODU for each link is connected to a plug-in card inside the site aggregator.
Other plug-in cards provide line interface access (TDM and native IP), management, and so on.
9500 MPR Node supports a mix of non-protected and protected or diversity operation for single link, repeater or
star radio configurations.
Notes:
Microwave Service Switch - 4/8 (MSS-4 / MSS-8)
Notes:
Supports unprotected or protected links
Notes:
Supports unprotected or protected links
Notes:
32E1/DS1 card: provides the external interfaces for up to 32xE1/T1 tributaries, manages the
encapsulation/reconstruction of PDH data to/from standard Ethernet packets and sends/receives standard
Ethernet packets to/from both Core-E modules.
ASAP card: provides external interfaces to transport 16xE1 ATM traffic, with E1/IMA physical layer, in an MPR
network. ATM traffic is transported within MPR network as "special" Ethernet traffic. This traffic is managed by
the MPR using RFC 4717 (IETF ATM PseudoWire EdgetoEdgeeEmulation, PWE3) with N-1 encapsulation format.
AUX card: provides the external interfaces for Service Channels access and Housekeeping alarms.
STM-1 card: provides the external interfaces for up to 2 electrical or optical STM-1 signals, manages the
encapsulation/reconstruction of SDH data to/from standard Ethernet packets and sends/receives standard
Ethernet packets to/from both Core-E modules.
EAS Peripheral (P8ETH) card: provides access for customer Ethernet traffic and supports the following traffic
external interfaces:
4xEthernet SFP 4x1000 Base-X optical, Base-T, or Copper Cable access directly available on the EAS
module. Interfaces can be 1000BASE-LX (GbE LX 10 km) or 1000BASE-SX (GbE SX 550 m) or 1000BASECX (GbE CX 25 m)
Modem 300: this unit is used to interface the ODU300. It sends/receives standard Ethernet packets to/from
both Core-E modules, manages the radio frame (on Ethernet packet form) generation/termination, the interface
to/from the alternate Radio module (for RPS management), the cable interface functions to ODU; it contains
the logic for the EPS Core-E protection, the RPS logic.
MPT access card (with PFoE): this unit is used to interface the MPT. PFoE (Power Feed over Ethernet) is used to
carry the power supply to the MPT-HC through an electrical Ethernet traffic connector.
The optional +24 Vdc/-48 Vdc Converter unit (to be installed in transport slot 4, 6 or 8 of MSS-8 can be used to
power the MSS for +24 Vdc office applications.
Notes:
To manage more directions the Stacking configuration can be realized by installing up to 3 MSS,
interconnected through the Ethernet ports in the Core-E module. In the example of Figure are shown two
interconnected MSS.
Notes:
With the Core protection max. 3 MSS can be interconnected as shown in figure.
To implement this configuration the LOS alarm on the Ethernet ports must be enabled as switching criterion of
the Core protection. To enable this alarm the Ethernet LOS Criteria feature has to be enabled.
Notes:
The 9500 MPR Terminal supports up to 2 RF links for operation on the same or different frequency bands
using the MSS-1c Unit.
The ODU for each link is connected to MSS-1c Unit inside the site aggregator.
9500 MPR Terminal supports non-protected and protected or diversity operation for single link radio
configurations.
Notes:
Microwave Service Switch - 1 Terminal (MSS-1c)
Notes:
MSS-1c Characteristics:
10xE1 or 16xE1/T1 depending on the hardware variant (hybrid TDMtoTDM and Packet Mode TDMtoETH)
4 GEthernet user ports
Up to 2 MPT
1+0
1+1
repeater configurations
L2 switch
SynchE
Housekeeping
2 ports for TMN chaining
Notes:
MSS-1c platform:
Peripherals
Notes:
E1/T1 local access function: provides the external interfaces for up to 16xE1/T1 tributaries, manages the
encapsulation/reconstruction of PDH data to/from standard Ethernet packets and sends/receives standard
Ethernet packets to/from Ethernet Switch.
MPT access function: this function is used to interface the Microwave Packet Transport (MPT). The interface
to the MPT is a standard GbEth interface (electrical or optical). It sends/receives standard Ethernet packets
to/from Ethernet Switch.
Notes:
The 1+1 configuration with MPT-MC does not require any interconnection cable between the two ODUs.
The 1+1 configuration with MPT-HC, MPT-HC V2, MPT-XP, or 9558HC can be implemented with or without
an interconnection cable between the two ODUs.
Notes:
Providing a single managed network reduce the operational expenditure of a network directly improving the
margin in the P&L of an Operator.
Alcatel-Lucent offers a unified management system capable to manage the entire access and transport
network under a single Network Management Suite: the 1350 OMS.
9500 MPR together with all other Microwave and Optical transmission Network Element is fully integrated
into 1350 OMS Network Management System providing all the tools required to operate the network.
Notes:
9500 MPR can be managed:
Document History
Edition
Date
Author
Remarks
3.4
2012-07-01
AL University
First edition
4.0
2012-09-15
AL University
Page
1 MSS Architecture
1.1 Flash Cards with Licenses
1.2 MSS-ODU300 cable (Interfaces and Traffic)
1.3 MPT
1.4 MSS-MPT Cable (Interfaces and Traffic)
1.4.1 MPT-HC connectivity
1.4.2 MPT-HCV2 connectivity
1.4.3 MPT-MC connectivity
2 MPR-e/MSS-1c Architecture
2.1 MSS-1c
2.2 ODUs
2.3 MSS-MPT Cable (Interfaces and Traffic)
2.3.1 MPT-HC Connectivity
2.3.2 MPT-HC V2 Connectivity (1+0 configuration)
2.3.3 MPT-HC V2 Connectivity (1+0 XPIC configuration)
2.4 MPT-HC V2 Electrical Interface with Power Injector
2.5 MPT-HC V2 Optical Interface
2.5.1 MPT-MC connectivity
3 Traffic Profiles
3.1 Managed Services and profiles
3.2 Traffic profiles
3.3 TDM2TDM
3.4 TDM2Eth
3.5 SDH2SDH
3.6 ATM Traffic Management
3.7 ETH2ETH
3.8 Ethernet Traffic Management
4 Traffic Management
4.1 QoS Overview
4.2 QoS Configuration Overview
5 LAG (Link Aggregation Group)
5.1 LAG overview
5.1.1 Link aggregation on Radio ports (Radio LAG)
5.2 L1 LAG
5.3 L2 LAG
5.4 L2 Ethernet LAG
6 Synchronization
6.1 Synchronization
6.2 Clock Source Selection and Distribution
6.3 Differential/Adaptative clock recovery
6.4 Synchronization Interface
6.5 Synchronization Interface
7 Cross-connections
7.1 Cross-Connections
7.2 TDM2TDM Mode
7.3 TDM2Eth Mode
7.4 Cross-connection
8 MPR Management
8.1 9500 MPR Management
8.2 MPR IP addresses
8.3 TMN communication channels
8.4 TMN interfaces (9500 MPR Node)
8.5 LCT Connection
8.6 MPR Capability IP Parameters
Copyright 2012 Alcatel-Lucent. All Rights Reserved.
Edition 3.0
Section 1 Module 2 Page 5
7
8
9
10
11
12
15
19
23
24
26
27
28
30
32
33
34
35
37
38
44
48
50
52
54
57
58
61
62
64
71
72
73
74
77
79
83
84
89
90
93
94
99
100
101
102
103
105
106
107
109
110
111
112
Page
Notes:
A single 50 ohm coaxial cable connects a ODU300 Radio Interface to its ODU. The max. cable length is up to
150 m. ODU cable, connectors and grounding kits are separately provided.
The ODU cable carries DC power (-48 Vdc) for the ODU and five signals:
Tx telemetry
Rx telemetry
Reference signal to synchronize the ODU IQ Mod/Demod oscillator
311 MHz IQ modulated signal from the ODU300 Radio Interface (transmit IF)
126 MHz IQ modulated signals from the ODU (receive IF)
Signal extracting and merging is carried out in N-Plexers within the ODU300 Radio Interface and ODU.
Notes:
MPT-HC V2 is similar to MPT-HC from architecture standpoint and can be used as spare part of the MPT-HC.
The differences are:
MPT-HC V2 can be natively Ethernet powered through a proprietary PFoE (or as alternative by using two
cables, one coaxial cable for the Power Supply and one optical cable for the Ethernet Traffic (as MPT-HC).
Notes:
One cable connect an MPT Access unit in the MSS to its MPT.
This cable is an electrical Gigabit Ethernet cable with Power Feed over Ethernet (Not for MPT-HC).
The max cable length for electrical Ethernet connection is 100 m.
Two cables connect an MPT Access unit in the MSS to its MPT.
One cable is a 50 ohm coaxial cable to send the -48 V power supply to the MPT-HC/MPT-HC V2.
The second cable is an optical Gigabit Ethernet cable.
The max cable length for optical Ethernet connection is 350 m.
Notes:
2x Coax connection
(power feed in case of Optical connection)
2x SFP ports for optical connection option
2x 1000BaseT port with Power over CAT5e cable
(Electrical connectivity Data+Power over a single CAT cable)
Notes:
Pigtail: N-RJ45 two wires Transition Connector.
Notes:
MPT-HC must be connected to a fuse or a breaker on a customer power distribution box. The recommended value
is 3 Amps.
Notes:
One electrical Ethernet cable connects an MPT Access unit in the MSS to its MPT-HC V2 (the MPT Access unit
provides the PFoE).
Notes:
Two cables connect an MPT Access unit in the MSS to its MPT-HC V2:
One cable is a 50 ohm coaxial cable to send the power supply to the MPT-HC V2:
for length lower or equal to 100 m the power cable can be CAT5E cable to send the power supply to
the MPT-HC V2 . The Ethernet electrical cable is provided with connectors to be mounted on site with
the specific RJ45 tool (1AD160490001);
for length higher than 100m, the cable is a 50 ohm coaxial cable to send the power supply to the MPTHC V2
Note: In case of length lower than 100m and presence in the field of 1 coaxial already installed and free it is
recommended to use the coax cable to minimize the installation effort.
Notes:
Two cables connect an MPT Access unit in the MSS to its MPT-HC V2:
One cable is a 50 ohm coaxial cable to send the power supply to the MPT-HC V2:
n
for length lower or equal to 100 m the power cable can be CAT5E cable to send the power supply to
the MPT-HC V2 . The Ethernet electrical cable is provided with connectors to be mounted on site with
the specific RJ45 tool (1AD160490001);
for length higher than 100m, the cable is a 50 ohm coaxial cable to send the power supply to the MPTHC V2
Note: In case of length lower than 100m and presence in the field of 1 coaxial already installed and free it is
recommended to use the coax cable to minimize the installation effort.
Notes:
MPT-HC V2 must be connected to a fuse or a breaker on a customer power distribution box. The recommended
value is 3 Amps.
Notes:
Notes:
The MPT-HC must be connected to a fuse or a breaker on a customer power distribution box. The recommended
value is 3 Amps.
Notes:
Notes:
MPT-HC V2 is similar to MPT-HC from architecture standpoint and can be used as spare part of the MPT-HC.
The differences are:
MPT-HC V2 can be natively Ethernet powered through a proprietary PFoE (or as alternative by using two
cables, one coaxial cable for the Power Supply and one optical cable for the Ethernet Traffic (as MPT-HC).
Notes:
By using the optional DC Extractor, installed close to the MPT-HC, the interconnection between the MSS and
the MPT-HC can be made with a single electrical Ethernet cable by using the Power Feed over Ethernet
(Ethernet traffic and Power Supply on the same cable).
The DC Extractor then separates the Power Supply from the Ethernet traffic, which are separately send to
the MPT-HC.
Notes:
One electrical Ethernet cable connects an MPT Access unit in the MSS to its MPT-HC V2 (the MPT Access unit
provides the PFoE).
The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool
(1AD160490001).
Notes:
One cable is a 50 ohm coaxial cable to send the power supply to the MPT-HC V2:
for length lower or equal to 100 m the power cable can be CAT5E cable to send the power supply to
the MPT-HC V2 . The Ethernet electrical cable is provided with connectors to be mounted on site with
the specific RJ45 tool (1AD160490001);
for length higher than 100m, the cable is a 50 ohm coaxial cable to send the power supply to the MPTHC V2
In case of length lower than 100m and presence in the field of 1 coaxial already installed and free it is
recommended to use the coax cable to minimize the installation effort.
MPT-HC V2 must be connected to a fuse or a breaker on a customer power distribution box. The recommended
value is 3 Amps.
Notes:
Two MPT-HC V2 are installed and connected to the power injector, and interconnected through the
XPIC and RPS cables.
Notes:
If MPT-HC V2 final installation will be in optical on the pole mounting don't insert SFP module,
use a simple Ethernet cable connected to the RJ45 port for provisioning phase.
Verify on the PC, that the MCT application has been installed.
Launch the MCT by double clicking on file MctStarter.jar, located under the path created by the
operator during the local copy and under \\WebEML MPR TCO
4.4\9500MCT_V02.0X.XX\MctStarter.jar
Notes:
MPT-HC must be connected to a fuse or a breaker on a customer power distribution box. The recommended value
is 3 Amps.
Notes:
TDM to TDM This is the typical service associated to a traditional TDM network in which E1/T1
traffic is transported, switched and terminated inside a MPR network.
TDM to ETH This is the service allowing the TDM traffic to be aggregated and output in a
single ETH stream. On this service specific algorithms are applied in order the E1/T1 is
transported, switched and provided to an external ETH network in standard format (MEF-8).
SDH to SDH This is the typical service associated to a traditional SDH transport network. STM1 traffic is transparently transported, switched and terminated inside a MPR network.
ETH to ETH (ETSI) DATA (ANSI) This is not a real CES due to the native IP architecture of
MPR. Ethernet traffic is directly managed by the L2 switch on the Core board, thanks to the autolearning algorithm, VLANs etc.
ATM to ATM (ETSI) This profile allows the management of the ATM services inside a 9500
MPR network. E1s IMA/ATM are terminated/reconstructed at the borders of the 9500 MPR cloud;
encapsulation/extraction of ATM streams into/from ATM PW packets is performed according to
RFC 4717.
ATM to ETH (ETSI) This profile allows the ATM service to be terminated and encapsulated
into an Ethernet stream towards an IP/MPLS Core Network.
Notes:
Definition: This service identifies a flow inside MPR network, in which E1/T1 is transported,
switched and terminated.
Notes:
Definition: E1/T1 TDM input signals are packetized according to MEF8 standard; E1/T1s are
transported, switched and provided to an external ETH network in standard format (MEF-8).
Notes:
Definition: This service identifies a flow inside MPR network, in which STM-1 is transparently
transported, switched and terminated.
Notes:
Definition: Ethernet traffic is transported and switched automatically by the standard autolearning algorithm of the built-in MPR 10 Gbit Ethernet switch.
Notes:
TDM2TDM and TDM2ETH profiles are managed in compliancy with Metro Ethernet Forum specifications
MEF 8- Implementation Agreement for the Emulation of PDH Circuits over Metro Ethernet Networks
Same behavior than PDH/SDH transmission devices (QoS)
Reduced impact of the packetization overhead
Same Radio performances than PDH/SDH devices
Notes:
Case 1 for E1/T1 (TDM2TDM over MPR network)
The E1/T1 stream is inserted in Node 1 and extracted in Node 2. In this case the two IWFs used to
packetize the traffic for the Ethernet switch in the Core-E module are both internal to the 9500 MPR network.
The Circuit Emulation Service is TDM2TDM in Node 1 and Node 2. The Cross connections are PDH-Radio
type.
The STM-1 stream is inserted in Node 1 and extracted in Node 2. In this case the two IWFs used to
packetize the traffic for the Ethernet switch in the Core-E module are both internal to the 9500 MPR network.
The Circuit Emulation Service is SDH2SDH in Node 1 and Node 2. The Cross connections are SDH-Radio type.
Case 2 (TDM2Eth)
The E1/T1 stream is inserted in Node 1 and extracted in Node 2. One IWF is inside the 9500 MPR, the
second IWF is external to the 9500 MPR-E network. The Circuit Emulation Service is TDM2ETH in Node 1 and
Node 2. The Cross connections are PDH-Radio type in Node 1 and Radio-Eth type in Node 2.
Case 3 (TDM2Eth)
The E1/T1 stream is inserted/extracted in Node 1. One IWF is inside the 9500 MPR, but the second IWF is
external to the 9500 MPR network. The Circuit Emulation Service is TDM2ETH in Node 1 and Node 2. The
Cross connections to be implemented are PDH-Eth type in Node 1.
Copyright 2012 Alcatel-Lucent. All Rights Reserved.
Edition 3.0
Section 1 Module 2 Page 45
Notes:
In these cases Ethernet packets enter Node 1 and are extracted in Node 2. In case 4 the Ethernet packets
encapsulate the E1 stream; in case 5 the packets are native Ethernet packets. None of the IWFs belongs to
the 9500 MPR network. The Circuit Emulation Service is ETH2ETH in Node 1 and Node 2. No Cross
connections must be implemented. The path is automatically implemented with the standard auto-learning
algorithm of the 9500 MPR Ethernet switch.
Notes:
Case 6 for E1/T1 (TDM2TDM over Ethernet)
The E1/T1 stream is inserted in Node 1 and extracted in Node 2. In this case the two IWFs used
to packetize the traffic for the Ethernet switch in the Core-E module are both internal to the 9500
MPR network. The Circuit Emulation Service is TDM2TDM in Node 1 and Node 2. The Cross
connections are PDH-Eth type.
Notes:
no flooding-autolearning necessary
Notes:
Notes:
destination MAC added before going into whole network (MEF8 compliant)
Notes:
Notes:
In figure is shown a more detailed block diagram of the ASAP unit in Ingress.
Notes:
Any packet belonging to an Eth2Eth TDM flow is treated as any other Ethernet packet with the only
exception of giving it an higher priority based on the MEF 8 Ethertype.
Notes:
The table summarizes the actions taken for specific reserved multicast addresses. Frames identified with
these destination addresses are handled uniquely since they are designed for Layer 2 Control Protocols.
Discard - The system discards all ingress Ethernet frames and must not generate any egress Ether-net
Frame carrying the reserved multicast address.
Forward - The system accepts all ingress Ethernet frames as standard multicast frames and for-wards
them accordingly.
Peer - The system acts as a peer of the connected device in the operation of the relevant Layer 2 Control
Protocol.
Notes:
9500MPR uses a Connection Admission Control (CAC) for committed services and two schedulers in
series (on Core embedded L2 switch and on Radio peripheral)
The two schedulers need to jointly interoperate to guarantee determistic behavior of the services
The QoS function inside 9500 MPR-E is the result of a distributed implementation in the switch in the Core-E
unit and Radio Interface unit. Both those QoS functions are properly configured in order to get the wished
behavior on Ethernet flows that will be transmitted towards the Radio.
The QoS configuration is the same for all the involved units:
Core-E
EAS
Modem unit (to interface the ODU300)
MPT-HC/MPT-HC V2/MPT-XP/MPT-MC
Notes:
In the figure is shown an overview of the QoS implementation inside the Core-E unit and Modem unit which
is used to interface the ODU300.
The QoS feature provides eight internal queues to support different traffic priorities. The QoS function can
assign the packet to one of the eight egress transmit queues.
Notes:
In case the configuration of radio interfaces changes from 1+0 to 1+1, the Radio QoS of Spare
interface takes the queue sizes of the Radio QoS of Main interface. The previous configuration of
queue sizes of the Radio QoS of Spare interface is lost.
In case of the configuration of radio interfaces changes from 1+1 to 1+0, the Radio QoS of Main
interface maintains the previous configuration of queue sizes, while the Spare interface takes the
default queue sizes according to the configured Modem Profile.
When a radio port is added to the L1 LAG port, all custom QoS and queue size configuration is
lost.
When a radio port is removed from a L1 LAG port, the NE QoS settings are applied to the radio
port. The queue sizes are set to the default values.
Notes:
In order to give an estimation of the maximum delay, that an Ethernet frame can experience
when entering the specific queue in case of congestion of radio interface, the WebEML shows a
read-only value, which is the queue size configured by the operator converted in a time value
(msec).
Notes:
The weights can be changed, from the WebEML user interface.
Notes:
It is recommended to forward the jumbo frame only in the queue Q1 (lower priority).
Notes:
In this example, user traffic is split up into radio channels. Main advantages:
Throughput. The overall radio Ethernet throughput is more than 1 Gbit/sec (4 x 350 Mbit/s,
being this the value for 256QAM@56 MHz)
Protection. In case of a failure of one of the three channels, all the traffic is redirected on
the remaining link (with a throughput of around 0.35 Gbit/sec). The discarded or dropped
traffic is the one with lower priority: high priority traffic is still running on the remaining
active channels.
Notes:
In Layer1 Link Aggregation, the Distributor performs a packet-based traffic distribution over
multiple links regardless of the content of the packets.
The Distributor takes into account the number of bytes sent over a specific link and loads links
according to the available bandwidth. As a consequence, Layer1 Link Aggregation allows a traffic
load balancing independently of traffic content. Since the distribution does not depend on Layer2
or Layer3 header content, this kind of Link Aggregation is called Layer1 (i.e., associated to the
physical layer).
Notes:
The following radio configurations are supported:
Notes:
Radio L2 LAG ports configured in Active/Standby mode are NOT recommended in this release of the
9500 MPR.
Notes:
One MPT per MPT plug-in.
Notes:
The Ethernet ports involved in a LAG cannot be used as TMN In-band interface.
Notes:
After a user Ethernet port has been added to an Ethernet L2 LAG port, the following user Ethernet
port parameters may not be modified:
Notes:
With MSS-1c and with MPR-e the SSM are transparency forwarded in most of the configurations.
Notes:
On the radio channel, a 9500 MPR transfers the reference clock to an adjacent MPR device through the radio
carrier frequency at physical layer.
End-to-end scenarios where time-of-day/phase alignment are requested are fully supported, as 1588 PTP v2
is carried transparently by MPR across the microwave backhauling network.
Both for Hybrid and Packet working modes, the Clock can be received at hand-off or delivered at the cell site.
Synch-Eth, E1, PDH and BITS clock modes are available.
Notes:
The availability of the Clock in the Network represents the most common scenario, characterized by a time
source available at the ingress of the microwave backhauling network, derived from the primary reference
clock.
Synchronization (frequency) is delivered to the cell site using any of the options available on MPR, depending
on the operators need. Worth repeating ingress and egress methods can be mixed (i.e. Synch-Eth at the
ingress, E1/T1 at the egress) via a simple configuration.
Notes:
9500 MPR has an embedded reference clock which is distributed to each board of the network element.
Such clock is generated in the Clock Reference Unit (CRU) of the core unit (controller).
Notes:
Differential: used in case of clock distribution on the whole network. Its more reliable than Adaptive; also
used in TDM2TDM traffic (MPR to MPR).
Adaptive: simpler network, but performances depends on the PDV (Packet Delay Variation) in the Network.
Always used when the reference clock isnt distributed on the whole network.
Node Timing: this feature (called either network clock re-timing or node timing or, according to G. 8261
wording, network-synchronous operation for service clock) introduces an additional possibility to recover E1
clock.
Node timing is a way to recover TDM clock quite popular in the industry of service routers and site
aggregator boxes. This feature inside the 9500 MPR platform is adding interworking capabilities with
third parties service routers and circuit emulations gateway.
In node-timing working mode, all the E1s are re-sampled with the network element clock. This means
that, as also reported in G8261, this method does not preserve the service timing (E1 clock).
Notes:
If the NODE TIMING is enabled, the CT still propose the possible selection between ACR and
DCR: in this specific case, the meaning of this option is not related to the clock recovery
algorithms but rather to the MRF8 frame format.
Notes:
Notes:
Each Module will mute its own Synchronization clock in case of Fail Alarm.
The Signal Degrade Alarm relevant to the selected Synchronization Source, or the relevant Card
Fail, causes the switching of the Synchronization Source.
For each available sync source, the CRU detects the signal Degrade Alarm on each available sync
source. Such Signal Degrade alarm raises also in case of muted (missing) clock.
Notes:
The cross-connections between slots and between slot and Ethernet user ports are realized with a
Layer-2 Ethernet Switch inside the Core-E unit.
The decision made by the switch to forward the received packet is based on the destination MAC
address.
E1 Cross-connections
Ethernet interface
STM-1 Cross-connections
Radio interface
Radio-Radio Cross-connections
Ethernet frames, coming from a radio direction, can be cross-connected to another radio
direction.
Notes:
TDM2TDM
The E1 data stream is inserted into one Node and extracted in another Node.
The two Internal Working Functions (IWF) used to packetize the traffic for the Ethernet switch in the
CSM-E/Core-E are internal in the radio.
Notes:
TDM2Eth
Ethernet Signal Flow - The Ethernet is inserted into customer access ports on the CSM-E/Core-E
EAS/P8ETH in one Node and extracted from customer access ports on the CSM-E/Core-E EAS/P8ETH
in another Node.
E1/T1 Signal Flow - The E1 port data stream is inserted into one Node and extracted in another Node.
Notes:
The cross-connections between slots and between slot and Ethernet user ports are realized with a Layer-2
Ethernet Switch inside the Main Core-E.
The decision made by the switch to forward the received packet is based on the destination MAC address.
Radio interface
Ethernet interface
Notes:
Refer to the attached diagram as an example of the IP address assignment.
Notes:
Refer to the attached diagram as an example of the IP address assignment.
Notes:
With the introduction of TMN In-Band two new IP interfaces are added to those already available.
NE Local IP Address
The NE Local IP Address can be reused on one of the other TMN interfaces. These interfaces
must have different IP subnets.
Document History
Edition
Date
Author
Remarks
3.4
2012-07-01
AL University
First edition
4.0
2012-07-30
AL University
Page
1 Microwave Service Switch (MSS-8)
1.1 MSS-8 Overview
1.2 MSS-8 Cards
2 Microwave Service Switch (MSS-4)
2.1 MSS-4 Overview
2.2 MSS-4 Cards
3 Control and Switching Module/Core-E
3.1 CSM-E/Core-E Card
3.2 CSM-E/Core-E Card Block Diagram
3.3 CSM-E/Core-E Card Status LED
3.4 CSM-E/Core-E Card LEDs
4 Ethernet Access Switch/P8ETH
4.1 P8ETH/EAS Card
4.2 P8ETH/EAS Card Block Diagram
4.3 P8ETH/EAS Card Status LED
4.4 EAS/P8ETH Card LEDs
5 P32E1DS1 (DS1/PDH) Card
5.1 P32E1DS1 (DS1/PDH) Card
5.2 P32E1DS1 (DS1/PDH) Card Block Diagram
5.3 P32E1DS1 (DS1/PDH) Card Status LED
5.4 DS3/P2E3DS3 Card
5.5 DS3/P2E3DS3 Card Block Diagram
5.6 DS3/P2E3DS3 Card Status LED
6 MPTACC Card
6.1 MPTACC Card
6.2 MPTACC Card Block Diagram
6.3 MPTACC Card Status LED
6.4 MPTACC Card LEDs
7 MOD300 Card
7.1 MOD300 Card
7.2 MOD300 Card Block Diagram
7.3 MOD300 Card Status LED
7.4 MOD300 Card LEDs
8 AUX Card
8.1 AUX Card
8.2 AUX Card Block Diagram
8.3 AUX Card Status LED
8.4 AUX Card LEDs
9 2xSTM-1 Local Access Card
9.1 2xSTM-1 Local Access Card
9.2 2xSTM-1 Local Access Card Block Diagram
10 ASAP Card
10.1 ASAP Card
10.2 ASAP Card Block Diagram
10.3 ASAP Card Status LED
10.4 ASAP Card LEDs
11 Fan Card
11.1 Fan Card
11.2 Fan 2U Card with Alarms LEDs
12 +24/-48 Volt Power Converter
12.1 +24/-48 Volt Power Converter
13 Power Extractor
13.1 Power Extractor
14 Power Injector
14.1 Power Injector
Copyright 2012 Alcatel-Lucent. All Rights Reserved.
Edition 3.0
Section 2 Module 1 Page 5
7
8
9
11
12
13
15
16
21
22
23
25
26
27
28
29
31
32
33
34
35
36
37
39
40
41
42
43
45
46
47
48
49
51
52
53
54
55
57
58
59
61
62
63
64
65
67
68
69
71
72
73
74
75
76
Page
14.2 Power Injector Plug-in
14.3 LEDs
15 MPT power unit
15.1 MPT power unit
15.2 MPT power unit block diagram
15.3 LEDs
16 MPT extended power unit
16.1 MPT extended power unit
16.2 MPT extended power unit block diagram
16.3 LEDs
17 Microwave Service Switch (MSS-1c)
17.1 MSS-1c
17.2 MSS-1c Block Diagram
17.3 MSS-1c Status LED
17.4 MSS-1c
18 Distributors/Patch Panels
18.1 E1/T1 RJ-45 120 Ohm Patch Panel
18.2 32E1 SCSI 75 Ohm Patch Panel
18.3 E1/T1 Tributaries (Protected Pair)
18.4 E1/T1 D-Connector Patch Panel
77
78
79
80
82
83
85
86
88
89
91
92
93
94
95
97
98
99
100
101
Notes:
General Rules:
Notes:
General Rules:
Notes:
Controller
Layer 2+ Ethernet Switch, VLAN management and MAC based
Notes:
The SFP must be installed after the Configuration File has been downloaded. If the SFP has been
installed before, withdraw it and then installed it again.
Notes:
For the correct operation of the EoSDH SFP it is necessary to disable the autonegotiation via
WebEML or via the Configuration File.
Notes:
Based on packet technology with 7 GbEth serial internal interfaces between Core-E and peripherals
(jumbo frames 9728 bytes allowed)
The Core-E unit has the option to equip two SFPs (in port #5, port #6). These ports can be also used
to connect directly an MPT-HC/MPT-HCV2.
Notes:
The CSM-E/Core-E consists of microprocessor and Ethernet switch circuits. The Ethernet Switch
provides a Quality of Service (QOS) mechanism to control all streams.
If QoS is disabled, all traffic inside the switch has the same priority. This means that for each switch
port there is only one queue, first in, first out (FIFO)
Disabled
DiffServ priorities are based on one of eight tags, each identifying one of eight traffic types and
corresponding user priority values.
802.1 priorities are set based on IEEE 802.1D-2004 Annex G User Priorities and Traffic Classes
that defines seven traffic types and corresponding user priority values.
Notes:
Check front-panel LED indications
INDICATOR
Link (L)
Green
STATUS
Off
Link Up
DEFINITION
Link Down
Activity (A)
Off
Blinking Yellow
No Tx/Rx activity
Tx/Rx activity
Red
At least one alarm is present on the NE with major severity is present on the NE
Red
At least one alarm is present on the NE with minor severity is present on the NE
Yellow
At least one alarm is present on the NE with warning severity is present on the NE
Yellow
Status (S)
Off
Green Blinking
Green
Yellow
Red
Blinking Red
LEDs provide summary alarm indications, which can help narrow down the location and type of failure.
The LEDs on the CSM-E/Core-E front panel for each Ethernet connector are a good indicator of correct connectivity and activity on
the Ethernet port.
Where a Status LED on a plug-in is off (unlit), but power to the MSS-8 is confirmed by LEDs on other plug-ins, check the seating of
the affected plug-in.
Copyright 2012 Alcatel-Lucent. All Rights Reserved.
Edition 3.0
Section 2 Module 1 Page 23
Notes:
MSS-8 shelf:
Supports three protected pairs of P8ETH/EAS cards or six unprotected P8ETH/EAS cards.
P8ETH/EAS is supported in slots 3-8 for unprotected radio configurations.
MSS-4 shelf:
Supports one protected pair of P8ETH/EAS cards or two unprotected P8ETH/EAS cards.
P8ETH/EAS is supported in slots 3 and 4 for unprotected radio configurations.
In protected radio configurations, a pair of P8ETH/EASs are required.
Notes:
If more than six local Ethernet accesses are required (built into the Core-E), the EAS (P8ETH) offers
an additional four 10/100/1000 Ethernet interfaces plus 4 1 GbEth optical
Notes:
In a radio link containing a DS3 connection, a maximum of five DS1 connections can be assigned.
Additional DS1 connections may be added to separate links that do not contain DS3 connections.
Notes:
In the TX direction, the P32E1DS1 card processes and encapsulates up to 32 input lines into 2
Ethernet packets.
In the RX direction, the P32E1DS1 card extracts data from the Ethernet data packets and processes
the data to provide up to 32 output lines.
Termination of 32 E1/T1 signals (32 E1/T1 bi-directional interfaces on the front panel)
Framed E1/T1 bi-directional alarm management
Encapsulation/Extraction of PDH data flows into/from standard Ethernet packets
The module communicates with the CSM-E/Core-E Gigabit Ethernet Serial copper bi-directional
interfaces on the backplane.
Notes:
Notes:
In a radio link containing a DS3 connection, a maximum of five DS1 connections can be assigned.
Additional DS1 connections may be added to separate links that do not contain DS3 connections.
Notes:
Main functions:
Notes:
The MPT Access Unit is the interface for two MPT: MPT-HC or MPT-MC.
Two MPT-HC or MPT-MC can be connected to one MPT Access unit.
The two MPT can be configured in unprotected or protected configuration.
The connection to the MPT-HC can be realized:
one DC power Supply connector to send the power supply to the MPT-HC
one Gigabit Ethernet connector (electrical or optical) to send the Ethernet traffic and the
Ethernet control frames to the MPT-HC
or by using only one electrical Ethernet cable with the enabling of the PFoE (Power Feed over
Ethernet) function (Ethernet traffic + Power Supply on the same cable).
Notes:
In Tx direction, the MODEM Module generates the IF signal to be sent to an MXC Out Door Unit.
Digital Framer
Classification of incoming packets from the Core-E (QoS)
Fragmentation
Air Frame Generation (synchronous with NE clock)
Digital Modulator
TX Analog Chain
DAC & low pass filtering
Modulation to 311 MHz IF TX
In Rx direction, the MODEM 300 Module terminates the IF signal coming from the ODU300
extracting the original CBR and then the original Ethernet packets to be given the Core-E which
distributes them to the proper Module.
RX Analog Chain
126 MHz IF RX demodulation to I & Q
low pass filtering & ADC
Digital Demodulator
Carrier & CK recovery
Equalization
Error Correction
Digital Deframer
RPS (hitless)
Defragmentation
Copyright 2012 Alcatel-Lucent. All Rights Reserved.
Edition 3.0
Section 2 Module 1 Page 47
Notes:
Service Channels
Using the CT/NMS, the user can enable/disable the 64 kbit/s Service Channel interfaces. The default is disabled:
When enabled, Service Channel interfaces 1 and 2can be configured to transport the following protocol:
Synchronous 64 Kb/s RS422/V.11 DCE co-directional
Radio Service Channels
On each radio direction three 64 kbit/s out-of-band channels are dedicated to Service Channel transmission.
Alarm-Housekeeping
13 Alarm-Housekeeping pins are provided:
Notes:
Service Channels access and Housekeeping alarms are available with the optional Auxiliary
peripheral unit.
The Auxiliary peripheral unit on front panel is equipped with four connectors:
Notes:
EOW - Engineering Express Order Wire
Notes:
The STM-1 unit can be used in two different working modes, addressing two different network scenarios:
STM-1 channelized, provision card as SDHCHAN
STM-1 transparent, provision card as SDHAC
The STM-1 channelized interface works as a terminal multiplexer; it terminates or originates the SDH frame.
It multiplexes NxE1 into an STM-1 electrical/optical line connection. The clock source can be Loop time or
Node time. Typical application is a direct connection to SDH add-drop multiplexers (ADMs). STM-1 card
manages one 155 Mbit/s STM1 interface and up to 63xE1. Standard VC4 mapping of lower-order E1 traffic
streams to/from STM-1 is applied, that means that a VC4 directly maps up to 63xVC12 into an STM-1 signal
(in turn each VC12 contains 1xE1).
When protection of the unit is required (1+1 EPS protection), two STM-1 units must be installed.
Clock source from the incoming STM-1 signal can be selected as Network Element source clock. In the event
the clock source is lost, clocking falls back to the internal clock or to other of any synch in options.
In the Tx direction, the STM-1 Local Access unit processes and encapsulates up to 2xSTM-1 input lines into
an Ethernet packet that is sent to the Core-E card(s).
In the Rx direction, the STM-1 Local Access unit extracts data from the Ethernet data packets and processes
the data to provide up to 2 STM-1 output lines.
Notes:
The ASAP card is used to transport 16xE1 ATM traffic, with E1/IMA physical layer.
ATM PW Ethernet traffic is managed by MPR is such a way to emulate the native QoS that would
be applied by ATM equipment.
VCC mode
It is possible to assign at every VC one specific QoS. Policing and shaping at ATM level has
performed VC mode only
The VC of the same class level (CBR / UBR+ / UBR) are managed in the same radio tail
than are available 3 different radio tails
VPC mode
It is possible to transport max 48 VP for every IMA group. It is possible to manage only VP
switching (=only VPI change)
All the VC inside the VP must have same QoS (= for ex. all CBR or all UBR)
The radio QoS (= radio tails) and QoS ATM (=policing and shaping) are managed at VP level.
Notes:
The 16xE1 ATM streams enter the ASAP unit on the front panel.
The block diagram is divided into 3 parts:
LIU/Framer
Network Processor
Confederation FPGA
The main functions implemented by the LIU/Framer are:
Internal termination supported: 75 ohm, 120 ohm.
Line code supported: HDB3.
Pulse shape: digitally programmable
Framing to G.704 E1 signals and to CRC-4 multi-frame alignment signals.
Detection of alarm conditions as loss of signal, loss of frame, loss of signaling multi-frame and
loss of CRC multi-frame.
The Network Processor is the heart of the ASAP card and provides the implementation of the
protocols to be supported as well as data forwarding. ATM-IMA over PseudoWire, SAToP (like on
the PDH card), CESoP, ML-PPP can be supported by the SW application controlling the Data Path
and running on a different MIPS processor embedded on the same chip.
The main function implemented in the confederation FPGA is the clock management.
The right-hand side is the backplane with the 1 Gb bus shared among the other slots and hence
common with the other units (PDH units and Modem units).
Notes:
Power Injector box: stand-alone box, powered through two connectors on the front providing power
supply redundancy.
Notes:
Two DC connectors in the front (for box version), or power from the back panel (for plug-in
version).
Notes:
Check front-panel LED indications
INDICATOR
Link (L)
STATUS
Off
Green
DEFINITION
Link Down
Link Up
Activity (A)
Off
Blinking Yellow
No Tx/Rx activity
Tx/Rx activity
Red
Red
At least one alarm is present on the NE with minor severity (not supported)
Yellow
At least one alarm is present on the NE with warning severity (not supported)
Yellow
MPT1
MPT2
Off
Green
Yellow
Red
MPT
MPT
MPT
MPT
is
is
is
is
(not supported)
Document History
Edition
Date
Author
Remarks
3.4
2012-07-01
AL University
First edition
4.0
2012-07-30
AL University
Page
1 Outdoor Unit
1.1 ODU300 Construction and Mounting
1.2 ODU300 Characteristics
2 ODU300 Block Diagram
2.1 ODU300 Block Diagram
3 Outdoor Installations
3.1 ODU300 and Antenna
3.2 ODU300 Mounting Options
3.3 Installing the ODU
3.4 Direct-Mounted ODUs
3.5 Remote-Mounted ODUs (solution 1)
3.6 Remote-Mounted ODUs (solution 2)
3.7 Waveguide Flange Data
3.8 ODU300 External Connectors
7
8
9
11
12
13
14
15
16
17
18
19
21
22
Notes:
The ODUs include a waveguide antenna port, Type-N female connector for the ODU cable, a BNC female
connector (with captive protection cap) for RSSI access, and a grounding stud.
The ODUs, are designed for direct antenna attachment via an 9500MPR-specific mounting collar supplied
with the antennas.
ODU polarization is determined by the position of a polarization rotator fitted within the mounting collar.
A remote ODU mounting kit is available as an option. These may be used to connect an ODU to a standard
antenna, or to a dual-polarized antenna for co-channel link operation.
configurations, a direct-mounting coupler is used. They are available for equal or unequal loss operation.
Equal loss is nominally 3 dB.
ODUs are frequency-band specific, but within each band are capacity-independent up to their design
maximums.
Notes:
The quadrature modulated 311 MHz IF signal from the MSS is extracted at the N-Plexer and passed via a cable AGC
circuit to an IQ demodulator/modulator.
Here the 311 MHz IF is demodulated to derive the separate I and Q signals using the 10 MHz synchronizing reference
signal from the MSS.
These I and Q signals modulate a Tx IF, which has been set to a specific frequency between 1700 and 2300 MHz, such
that when mixed with the Tx local oscillator signal (TXLO) in the subsequent mixer stage, it provides the selected
transmit frequency. Both the IF and Tx local oscillators are synthesizer types.
Between the IQ modulator and the mixer, a variable attenuator provides software adjustment of Tx power.
After the mixer, the transmit signal is amplified in the PA (Power Amplifier) and passed via the diplexer to the antenna
feed port.
A microprocessor in the ODU supports configuration of the synthesizers, transmit power, and alarm and performance
monitoring. The ODU microprocessor is managed under the NCC microprocessor, with which it communicates via the
telemetry channel.
A DC-DC converter provides the required low-voltage DC rails from the -48 Vdc supply.
In the receive direction, the signal from the diplexer is passed via the LNA (Low Noise Amplifier) to the Rx mixer, where
it is mixed with the receive local oscillator (RXLO) input to provide an IF of between 1700 and 2300 MHz. It is then
amplified in a gain-controlled stage to compensate for fluctuations in receive level, and in the IF mixer, is converted to a
126 MHz IF for transport via the ODU cable to the MSS.
The offset of the transmit frequencies at each end of the link is determined by the required Tx/Rx split. The split options
provided are based on ETSI plans for each frequency band. The actual frequency range per band and the allowable
Tx/Rx splits are range-limited within 9500MPR-E to prevent incorrect user selection.
A power monitor circuit is included in the common port of the diplexer assembly to provide measurement of transmit
power. It is used to confirm transmit output power for performance monitoring purposes, and to provide a closed-loop
for power level management over the specified ODU temperature and frequency range.
Notes:
The ODU mounts directly to an Antenna: Non-protected.
Notes:
ODUs can be installed separately from its antenna, using a remote-mount to support the ODU, and a flexiblewaveguide or coaxial cable to connect the ODU to its antenna:
The remote mount allows use of standard, single or dual polarization antennas.
The mount can also be used to remotely support a protected ODU pairing installed on a coupler. The coupler
connects to the remote mount assembly in the same way as an ODU.
The remote mount clamps to a standard 112 mm (4) pole-mount, and is common to all frequency bands.
Figure shows an ODU installed on a remote mount.
Flexible waveguides are frequency band specific and are normally available in two lengths, 600 mm (2 ft) or
900 mm (3 ft). Both flange ends are identical, and are grooved for a half-thickness gasket, which is supplied
with the waveguide, along with flange mounting bolts.
Notes:
Table lists the antenna port flange types used with the ODU300, plus their mating flange options and
fastening hardware for remote mount installations.
Notes:
For all set-ups, one ground wire must be installed to ground the ODU.
Document History
Edition
Date
Author
Remarks
3.4
2012-06-14
AL University
First edition
4.0
2012-07-30
AL University
Page
1 Outdoor Units
1.1 MPT-HC Construction and Mounting
1.2 MPT-HC Characteristics
2 MPT-HC Block Diagram
2.1 MPT-HC Block Diagram
3 Outdoor Installations
3.1 Installing the MPT-HC
3.2 6-7-8 GHz MPT-HC: integrated antenna (1+0)
3.3 11-38 GHz MPT-HC: integrated antenna (1+0)
3.4 6-7-8 GHz MPT-HC: integrated antenna (1+1)
3.5 11-38 GHz MPT-HC: integrated antenna (1+1)
3.6 6-7-8 GHz MPT-HC: non-integrated antenna (1+0)
3.7 11-38 GHz MPT-HC: non-integrated antenna (1+0)
3.8 6-7-8 GHz MPT-HC: non-integrated antenna (1+1)
3.9 11-38 GHz MPT-HC: non-integrated antenna (1+1)
3.10 MPT-HC External Connectors
3.11 DC Extractor
7
8
13
15
16
17
18
19
20
21
22
23
24
25
26
27
32
Notes:
With embedded diplexer for cost optimization and different mechanics from 11-38 GHz (6 GHz), where the
branching (diplexer) is internal to the MPT-HC cabinet; this type of MPT-HC is identified by one Logistical Item
only;
Notes:
With external diplexer: due to a vary high number of shifters the diplexer is external for the flexibility of the
shifter customization (7 GHz and 8 GHz), where MPT-HC is composed by two independent units:
Each of this type of MPT-HC is identified by two Logistical Items, one for the BRANCHING assembly and
another for the RF TRANSCEIVER assembly.
To read the BRANCHING assembly identification label it is necessary to separate the BRANCHING assembly
from the RF TRANSCEIVER assembly.
Notes:
With embedded diplexer for cost optimization (11 GHz to 38 GHz), where the branching (diplexer) is internal
to the MPT-HC cabinet; this type of MPT-HC is identified by one Logistical Item only.
Notes:
The MPT-HC is broken down into the following sections:
Common Belt section. This section is Frequency independent, and all the features relevant to this unit are
common to all the MPT RF options.
RF section that is frequency dependent.
The MPT-HC interface is based on a Gb Ethernet, that can be either optical or electrical depending on the
needs and the cable length. If the optical port has/have to be used (data and/or RPS port), the
corresponding SFP plug-in must be installed by opening the Cobox.
Warning: A waterproofing tape is glued on the waveguide of the MPT-HC. It must never be removed.
Ref. in
figure
Interface
Connector
(1)
waveguide
(2)
male N 50 ohm
(3)
(4)
(5)
Co-box
11
13-15
18-25
38
WR75
WR62
WR42
WR28
Warning: A waterproofing tape is glued on the waveguide of the MPT-HC. It must never be removed.
Ref. in
figure
Interface
Connector
(1)
waveguide
(2)
male N 50 ohm
(3)
(4)
(5)
Co-box
WR112
WR112
Warning: A waterproofing tape is glued on the waveguide of the MPT-HC. It must never be removed.
Ref. in
figure
Interface
Connector
(1)
waveguide
(2)
male N 50 ohm
(3)
(4)
(5)
Co-box
6
WR137
Notes:
Notes:
The DC Extractor, installed close to the MPT-HC, allows to interconnect the MSS and the MPT-HC with a
single electrical Ethernet cable by using the Power Feed over Ethernet solution (Ethernet traffic and Power
Supply on the same cable).
The DC Extractor then separates the Power Supply from the Ethernet traffic, which are separately sent to the
MPT-HC.
The two cables, interconnecting the DC Extractor to the MPT-HC (the Power Supply cable to be connected to
the DC Out connector of the DC Extractor and Ethernet cable to be connected to the Data Out connector of
the DC Extractor), are provided, already terminated (2 m long), with the DC Extractor itself
Document History
Edition
Date
Author
Remarks
3.4
2012-06-14
AL University
First edition
4.0
2012-07-30
AL University
Page
1 Outdoor Units
1.1 MPT-HC V2 Characteristics
1.2 MPT-XP Characteristics
1.3 MPT-HC V2/MPT-XP XPIC
2 MPT-HC V2/MPT-XP/9558HC block diagram
2.1 MPT-HC V2/MPT-XP block diagram
2.2 MPT-HC V2/MPT-XP RF section block diagram
3 Outdoor Installations
3.1 Installing the MPT-HC V2/MPT-XP
3.2 MPT-HC V2 External Connectors
7
8
10
11
13
14
15
17
18
19
Notes:
Two mechanical solutions are adopted:
With embedded diplexer for cost optimization, where the branching (diplexer) is internal to the MPT-HC
V2 cabinet; this type of unit is identified by one Logistical Item only.
With external diplexer: due to a high number of shifters the diplexer is external for the flexibility of the
shifter customization, where MPT-HC V2 is composed by two independent units: the BRANCHING
assembly (containing the diplexer) and the RF TRANSCEIVER assembly (containing the RF section);
each of this type of MPT-HC V2 is identified by two Logistical Items, one for the BRANCHING assembly
and another for the RF TRANSCEIVER assembly. To read the BRANCHING assembly identification label it
is necessary to separate the BRANCHING assembly from the RF TRANSCEIVER assembly.
Notes:
The common belt section is frequency-independent. It is the digital section of the MPT-HC V2/MPTXP.
There are two architecture types for the RF section, the differences between these two
architectures are on the Rx side:
For 7/8 GHz, there are two frequency conversions between RF input frequency and baseband
frequency
The power comes from office power. Input voltage range is -28 to -58 Vdc.
Note: RF interface for connection of antenna or coupler. Remove the plastic cover.
Warning: A waterproofing tape is glued on the waveguide of the MPT-HCV2. It must never be removed.
11
13-15
18-25
38
WR137
WR75
WR62
WR42
WR28
Notes:
RF interface for connection of antenna or coupler. Remove the plastic cover.
Warning: A waterproofing tape is glued on the waveguide of the MPT-HC V2. It must never be removed.
FREQUENCY GHz ->
8
WR112
Notes:
During equipment line-up, through a multimeter it is possible to easily point the antenna until the
measured voltage is the maximum, corresponding to the maximum radio Rx field.
Document History
Edition
Date
Author
Remarks
3.4
2012-06-14
AL University
First edition
4.0
2012-07-30
AL University
Page
1 Outdoor Units
1.1 MPT-MC Construction and Mounting
1.2 MPT-MC Characteristics
2 MPT-MC Block Diagram
2.1 MPT-MC Block Diagram
3 Outdoor Installations
3.1 Installing the MPT-MC
3.2 7-8 GHz MPT-MC: integrated antenna (1+0)
3.3 6 and 11-38 GHz MPT-MC: integrated antenna (1+0)
3.4 7-8 GHz MPT-MC: integrated antenna (1+1)
3.5 6 and 11-38 GHz MPT-MC: integrated antenna (1+1)
3.6 MPT-MC: non-integrated antenna (1+0)
3.7 7-8 GHz MPT-MC: non-integrated antenna (1+1)
3.8 6 and 11-38 GHz MPT-MC: non-integrated antenna (1+1)
3.9 MPT-MC External Connectors
7
8
10
13
14
15
16
17
18
19
20
21
22
23
24
Notes:
With embedded diplexer for cost optimization (6 GHz and from 11 GHz to 38 GHz), where the branching
(diplexer) is internal to the MPT-MC cabinet; this type of MPT-MC is identified by one Logistical Item only.
With external diplexer: due to a vary high number of shifters the diplexer is external for the flexibility of the
shifter customization (7 GHz and 8 GHz), where MPT-MC is composed by two independent units:
Each of this type of MPT-MC is identified by two Logistical Items, one for the BRANCHING assembly and
another for the RF TRANSCEIVER assembly.
To read the BRANCHING assembly identification label it is necessary to separate the BRANCHING assembly
from the RF TRANSCEIVER assembly.
Notes:
Static radio profiles:
bandwidths: 3.5, 7, 14, 28, 40, and 56 MHz
modulations: 4, 8, 16, 32, 64, 128, and 256 QAM
Notes:
The MPT-MC breaks down into the following sections:
Common Belt section. This section is Frequency independent, and all the features relevant to this unit are
common to all the MPT RF options.
RF section that is frequency dependent.
The MPT-MC is similar to MPT-HC from architecture standpoint. It has limited capacity vs. MPT-HC and is
natively Ethernet powered (no Power extractor required).
Notes:
WARNING: A waterproofing tape is glued on the waveguide of the MPT-MC. It must never be removed.
With embedded diplexer for cost optimization (6 GHz and from 11 GHz to 38 GHz), where the branching
(diplexer) is internal to the MPT-MC cabinet; this type of MPT-MC is identified by one Logistical Item only.
FREQUENCY GHz ->
11
13-15
18-25
38
WR75
WR62
WR42
WR28
Notes:
WARNING: A waterproofing tape is glued on the waveguide of the MPT-MC. It must never be removed.
With external diplexer: due to a vary high number of shifters the diplexer is external for the flexibility of the
shifter customization (7 GHz and 8 GHz), where MPT-MC is composed by two independent units:
Each of this type of MPT-MC is identified by two Logistical Items, one for the BRANCHING assembly and
another for the RF TRANSCEIVER assembly.
To read the BRANCHING assembly identification label it is necessary to separate the BRANCHING assembly
from the RF TRANSCEIVER assembly.
FREQUENCY GHz ->
Waveguide type ->
WR112
WR112
Notes:
Connector usage:
Banana plugs (M3) and (M4): output is a 0 to +5V DC voltage proportional to the radio Rx field. During
equipment line-up, through a multimeter it is possible to easily point the antenna until the measured
voltage is the maximum, corresponding to the maximum radio Rx field.
Document History
Edition
Date
Author
Remarks
3.4
2012-06-14
AL University
First edition
4.0
2012-07-30
AL University
Page
1 Outdoor Unit
1.1 MPT-GC Characteristics
2 MPT-GC Block Diagram
2.1 MPT-GC Block Diagram
2.2 MPT-GC Link Description
3 Outdoor Installations
3.1 Installing the MPT-GC
3.2 MPT-GC External Connectors
7
8
9
10
12
13
14
15
Notes:
The Ethernet interface traffic is bridged across the link via an embedded switch. The SONET/SDH
traffic is handled separately within the radio and does not pass through the internal switch.
The SONET/SDH and Ethernet traffic are aggregated within the radio unit for transmission over the air
to the far end of the link.
Depending on configuration, the available Ethernet bandwidth can exceed 1000Mbps. To utilize the
full Ethernet capacity, the radio contains an internal Primary and Secondary Ethernet radio interface.
This allows copper or Ethernet SFP interfaces to be assigned to the Primary or Secondary channel
within the radio. An internal radio link aggregator handles this functionality.
The portion of the radio bandwidth that is not used by SONET/SDH is available for use by Ethernet as
shown in the table below.
The following table describes the basic function of each switch port
Notes:
Item
Description
Reset Button
Ground
10
Carrying/Lifting Hook
Document History
Edition
Date
Author
Remarks
3.4
2012-07-01
AL University
First edition
4.0
2012-07-30
AL University
Page
1 Protections with ODU300
1.1 Protections with ODU300
1.2 RPS Switching Criteria
1.3 EPS Switching Criteria
1.4 HSB Switching Criteria
2 Protections with MPT-HC V2/MPT-XP
2.1 Protections with MPT-HCV2/MPT-XP
2.2 RPS Switching Criteria
2.3 EPS Switching Criteria
2.4 HSB Switching Criteria
3 MSS-4/MSS-8 XPIC (with MPT-HC V2 /MPT-XP only)
3.1 MSS-4/MSS-8 XPIC (with MPT-HCV2/MPT-XP only)
4 Protection with MPT-MC
4.1 Protection with MPT-MC
4.2 RPS Switching Criteria
4.3 EPS Switching Criteria
4.4 HSB Switching Criteria
5 Core-E protection
5.1 Core-E protection
5.2 User Ethernet interfaces protection
5.3 TMN Local Ethernet interface protection
5.4 Core-E protection
5.5 Core-E protection Switching Criteria
7
8
11
12
13
15
16
20
21
22
23
24
27
28
30
31
32
33
34
35
36
37
38
Legend:
1
2
3
RPS
EPS
HSB
Legend:
2 EPS
Notes:
In the figure Ethernet port 2 of one MPT-HCV2/MPT-XP is connected to Ethernet port 2 of the second MPT-HC
V2/MPT-XP.
Notes:
MPT-HCV2/MPT-XP supports a further embedded functionality called "Enhanced RPS". Enhanced RPS is a
frame-based protection mechanism, aimed to reach a quick reaction time and increasing significantly the
quality of the radio interface in the Rx side.
It assumes the alignment between the 2 received radio channels and it is based on frame by frame selection
of the "best" frame between the frames received from the Main and the Spare radio channel.
The Enhanced RPS assumes that the "classical" RPS criteria are used to give indication about the "preferred"
channel, whose frame has to be selected, when the frame-based choice between the 2 streams is not
possible (e.g. due to the frame alignment error).
The Enhanced RPS switching criterion depends on the presence of errors in the decoded LDPC word.
Notes:
Where there is a cross configuration (EPS on Spare & TPS on main), HSB (TPS) will switch and align with EPS
position, if there is an inter-MPT coupling link failure.
Notes:
The actual improvement will depend on the native discrimination provided at antenna alignment,
and any reduction of this discrimination caused by atmospheric effects (fading).
Notes:
Since there is no coupling link in the current release the TPS Operator Commands are not
supported.
Notes:
MPT-MC supports a further embedded functionality called "Enhanced RPS". Enhanced RPS is a
frame-based protection mechanism, aimed to reach a quick reaction time and increasing
significantly the quality of the radio interface in the Rx side.
The Enhanced RPS assumes that the "classical" RPS criteria are used to give indication about the
"preferred" channel, whose frame has to be selected, when the frame-based choice between the
2 streams is not possible (e.g. due to the frame alignment error).
The Enhanced RPS switching criterion depends on the presence of errors in the decoded LDPC
word.
Notes:
All the switching criteria coming from both the Core units, are available (via back panel) to each peripheral in
order to allow to each logic to take the same decision.
Notes:
In case of stand-by Flash Card realignment in progress, the application SW refuses/removes a manual switch
command.
$OO5LJKWV5HVHUYHG$OFDWHO/XFHQW##<($5
@@COURSENAME 3DJH
$OOULJKWVUHVHUYHG$OFDWHO/XFHQW
3DVVLQJRQDQGFRS\LQJRIWKLVGRFXPHQWXVHDQGFRPPXQLFDWLRQRILWV
FRQWHQWVQRWSHUPLWWHGZLWKRXWZULWWHQDXWKRUL]DWLRQIURP$OFDWHO/XFHQW
$OO5LJKWV5HVHUYHG$OFDWHO/XFHQW##<($5
@@COURSENAME 3DJH