9500MPR R. 3.1 Description

9500MPR (Microwave Packet Radio) ETSI R 3.
1 description - Page 1
All Rights Reserved Alcatel-Lucent 2011
9500 MPR
9500 MPR (Microwave Packet
Radio) (ETSI) R 3.1 Description
STUDENT GUIDE
TWT63042-R 3.1-SG1-SEN- I1.0 Issue 1.00
All rights reserved Alcatel-Lucent 2011
Passing on and copying of this document, use and communication of its contents
not permitted without written authorization from Alcatel-Lucent
9500MPR (Microwave Packet Radio) ETSI R 3.1 description - Page 2
9500MPR (Microwave Packet Radio) ETSI R 3.1 description
9500 MPR ETSI
2
Empty page
Switch to notes view!
This page is left blank intentionally
9500 MPR ETSI
3
Terms of Use and Legal Notices
1. Safety Warning
Both lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to wear
conductive jewelry while working on the products. Always observe all safety precautions and do not work on the equipment
alone.
The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.
2. Trade Marks
Alcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent.
All other trademarks, service marks and logos (Marks) are the property of their respective holders, including Alcatel-Lucent.
Users are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning the Mark. The
absence of a Mark identifier is not a representation that a particular product or service name is not a Mark.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to change
without notice.
3. Copyright
This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No other
use or transmission of all or any part of this document is permitted without Alcatel-Lucents written permission, and must
include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may be used,
copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from Alcatel-Lucent.
Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it includes or describes, and
is expressly prohibited from modifying the information or creating derivative works without the express written consent of
Alcatel-Lucent.
4. Disclaimer
In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including lost
profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not Alcatel-Lucent has
been advised of the possibility of such damages.
Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an endorsement, nor
a recommendation.
This course is intended to train the student about the overall look, feel, and use of Alcatel-Lucent products. The information
contained herein is representational only. In the interest of file size, simplicity, and compatibility and, in some cases, due to
contractual limitations, certain compromises have been made and therefore some features are not entirely accurate.
Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment and
its operation, or contact your nearest Alcatel-Lucent representative for more information.
The Alcatel-Lucent products described or used herein are presented for demonstration and training purposes only. Alcatel-Lucent
disclaims any warranties in connection with the products as used and described in the courses or the related documentation,
whether express, implied, or statutory. Alcatel-Lucent specifically disclaims all implied warranties, including warranties of
merchantability, non-infringement and fitness for a particular purpose, or arising from a course of dealing, usage or trade
practice.
Alcatel-Lucent is not responsible for any failures caused by: server errors, misdirected or redirected transmissions, failed
internet connections, interruptions, any computer virus or any other technical defect, whether human or technical in nature
5. Governing Law
The products, documentation and information contained herein, as well as these Terms of Use and Legal Notices are governed by
the laws of France, excluding its conflict of law rules. If any provision of these Terms of Use and Legal Notices, or the application
thereof to any person or circumstances, is held invalid for any reason, unenforceable including, but not limited to, the warranty
disclaimers and liability limitations, then such provision shall be deemed superseded by a valid, enforceable provision that
matches, as closely as possible, the original provision, and the other provisions of these Terms of Use and Legal Notices shall
remain in full force and effect.
9500 MPR ETSI
4
Blank Page
9500 MPR ETSI
5
Course Outline
About This Course
Course outline
Technical support
Course objectives
1. Topic/Section is Positioned Here
Xxx
Xxx
Xxx
1. Product Overview
Module 1. 3JK Introduction
Module 2. 3JK Architecture
Module 3. 3JK Management System
2. Functional Description
Module 1. 3JK MSS Node HW Architecture
Module 2. 3JK ODU300 HW Architecture
Module 3. 3JK MPT-HC HW Architecture
Module 4. 3JK MPT-HC V2 HW Architecture
Module 5. 3JK MPT-MC HW Architecture
Module 6. 3JK MSS Terminal HW Architecture
9500 MPR ETSI
6
Course Outline [cont.]
9500 MPR ETSI
7
Course Objectives
Welcome to 9500MPR (Microwave Packet Radio) ETSI R 3.1 description
Upon completion of this course, you should be able to:
Configure and manage the 9500MPR
9500 MPR ETSI
8
Course Objectives [cont.]
9500 MPR ETSI
9
About this Student Guide
Conventions used in this guide
Where you can get further information
If you want further information you can refer to the following:
Technical Practices for the specific product
Technical support page on the Alcatel website: http://www.alcatel-lucent.com
Note
Provides you with additional information about the topic being discussed.
Although this information is not required knowledge, you might find it useful or
interesting.
Technical Reference
(1) 24.348.98 Points you to the exact section of Alcatel-Lucent Technical Practices
where you can find more information on the topic being discussed.
Warning
Alerts you to instances where non-compliance could result in equipment damage or
personal injury.
9500 MPR ETSI
10
About this Student Guide [cont.]
9500 MPR ETSI
11
Self-assessment of Objectives
At the end of each section you will be asked to fill this questionnaire
Please, return this sheet to the trainer at the end of the training
Contract number :
Course title :
Client (Company, Center) :
Language : Dates from : to :
Number of trainees : Location :
Surname, First name :
Did you meet the following objectives ?
Tick the corresponding box
Please, return this sheet to the trainer at the end of the training
Instructional objectives
Yes (or
globally
yes)
No (or
globally
no)
Comments
1 To be able to:
Describe the basic concepts of
9500MPR

2 To be able to:
Describe the main functionalities
of the 9500MPR

3 To be able to:
Describe the management system of
the 9500MPR

4 To be able to :
Describe the functionality of each unit
of the MSS

5 To be able to:
Describe the functionality of the ODUs

6 To be able to:
understand all the menus available
with the LCT

7 To be able to:
Configure a NE starting from scratch

8 To be able to:
Activate and evaluate the performance
monitoring application

9 To be able to:
Performa the troubleshooting of the
9500MPR

10 To be able to:
Perform the SW download of the 9500MPR

9500 MPR ETSI
12
Self-assessment of Objectives [cont.]
Instructional objectives
Yes (or
Globally
yes)
No (or
globally
no)
Comments

Thank you for your answers to this questionnaire
Other comments
Section 1 Module 1 Page 1

All Rights Reserved 2011, Alcatel-Lucent
3JK Edition 3.0
Do not delete this graphic elements in here:
Module 1
Introduction
3JK Edition 3.0
Section 1
Product Overview
3JK Edition 3.0
9500 MPR ETSI 9500MPR (Microwave Packet Radio) ETSI R 3.1 description
Product Overview Introduction
1 1 2
Blank Page
Updated to rel.3.0 ALU University,
Vimercate
2011-02-01 02
Updated to rel.3.1 ALU University 2011-08-25 03
First edition ALU University,
Marcoussis
2010-07-21 01
Remarks Author Date Edition
Document History
3JK Edition 3.0
1 1 3
Module Objectives
Upon completion of this module, you should be able to:
Describe the Basic Concepts of the 9500 MPR.
3JK Edition 3.0
1 1 4
Module Objectives [cont.]
3JK Edition 3.0
1 1 5
Table of Contents
Page
1 Understanding the 9500MPR Innovations 7
1.1 Classification of the New Generation Products 8
1.2 Presentation 9
1.3 Multiservice Aggregation Layer 12
1.4 Service Awareness 13
1.5 Packet Node 14
1.6 Service-driven Packet Adaptive Modulation 15
1.7 Power Consumption Reduction 16
1.8 Hybrid or Packet Mode: for Efficient Data Transport 17
1.9 Packet node: Minimizing Equipment at Each Site 19
Blank Page 20
2 MPR in New Market Segments 21
2.1 The Most Effective Solution 22
2.2 MPR-e Enabling Zero-Footprint Microwave Configurations 24
2.3 MPR in Last Mile 25
2.4 LTE and Full Ethernet 3G Ready 26
2.5 From Current PDH/SDH Network to Packet Transport Network Evolution 27
2.6 MPR addresses All Microwave Applications in Aggregation 28
2.7 MPR addresses Metro Ring/Partial Mesh Application 29
Blank Page 30
3 System Description 31
3.1 Alcatel-Lucent 9500 Microwave Packet Radio 32
3.2 9500 MPR System Family 33
3.3 9500 MPR Key Features 35
3.4 9500 MPR Node 37
3.5 9500 MPR Terminal 46
3.6 OutDoor Unit 300 51
3.7 Microwave Packet Transport 53
4 Radio Configuration 59
4.1 Radio Configuration 60
5 System Configuration 61
5.1 Example of System configurations 62
Blank Page 67
End of Module 68
3JK Edition 3.0
1 1 6
Table of Contents [cont.]
Page
3JK Edition 3.0
1 1 7
1 Understanding the 9500MPR
Innovations
3JK Edition 3.0
1 1 8
1 Understanding the 9500MPR Innovations
1.1 Classification of the New Generation Products
Alcatel-Lucent microwave product acronyms are derived as
follows:
9 5
9 5
0 0
0 0
MPR
MPR
Means radio
product
5 for Radio Cross-Connect
M = Microwave
P = Packet
R = Radio
Frequency Band
3JK Edition 3.0
1 1 9
BTS
Microwave
RNC
BSC
Microwave
Metro
Backhauling
Microwave for
backbone
Backbone
Last Mile Aggregated Link
Node B
ALU 9500 MPR, currentl y is the best combination of features/prices in the
Backhauling environment (from Last Mile to Metro Networks)
1.2 Presentation
9400AWY
9600 family
9600USY
9600LSY
9500 MXC
9500MXC 9500MPR
9400 family
9500 MPR
3JK Edition 3.0
1 1 10
9500MPR
9600USY
7
38
Capacity
F
r
e
q
u
e
n
c
y
MBps
4 34 45 64 155 311 622 1240 2480
2
4
4,7
6L
6U
7
8
10
11
13
GHz
9600LSY
MDR 8000
6L
6U
U
r
b
a
n

p
l
a
t
f
o
r
m
s
T
r
u
n
k
i
n
g
p
l
a
t
f
o
r
m
s
9500MXC
1.2 Presentation [cont.]
9400AWY
3JK Edition 3.0
1 1 11
1.2 Presentation [cont.]
The 9500 MPR innovative solutions mainly are:
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 service assigned, independently by the type of interface
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
3JK Edition 3.0
1 1 12
1.3 Multiservice Aggregation Layer
nxE1
Ethernet
ISAM, WiMAX
2G
Aggregated traffic
over Ethernet
Packet Backhaul network
Ethernet aggregation layer
Access network
Any TDM/Ethernet interfaces
nxE1
3G
HSDPA
Voice on R99
9500 MPR
GSM
Single technology throughout the network: Ethernet as convergence layer
TDM networking Packet networking
Stacking Converging
Maximizing the available bandwidth
9500 MPR aggregates and carries over a COMMON PACKET LAYER: TDM 2G, 3G, SDH 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.
3JK Edition 3.0
1 1 13
1.4 Service Awareness
High Priority Queue;
Guaranteed bit rate
Low Priority Queue;
Remaining bit rate
SERVICE AGGREGATION and OVERBOOKING:
Service aggregation using statistical
multiplexing, obtaining dramatic band
reduction
SERVICE QUALITY MANAGEMENT:
Service scheduler queuing packets according to
the quality of service assigned.
HIGH for real-time traffic, LOW for Broadband
Constant bit rate services
Revenue based on real-time
communication
Constant bit rate services
Revenue based on real-time
communication
Variable bit rate services
Revenue based on access
to contents
Variable bit rate services
Revenue based on access
to contents
Voice, Video Telephony
HiSpeed @, VideoD & Gaming
Decoupling access technology from transport technology: manage services
SERVICE CLASSIFICATION: Voice, Broadband
INPUTS : Any interfaces (E1, Ethernet)
PACKETIZATION PROCESSING:
TDM Standard CEoEth [MEF8]
SDH
ATM Standard PWE3
Ethernet Native
Service awareness means the ability to discriminate the different traffic types carried over the converged
Ethernet stream. Our traffic flow can be composed by E1s, STM-1, ATM and/or IP/Eth, coming from
different sources, and therefore having different requirements. For instance ATM traffic from a 3G base
stations 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 case of the non real time variable
bit rate one, optimize the band with overbooking of the radio scarce resource.
3JK Edition 3.0
1 1 14
1.5 Packet Node
Address new data services in the best way: packet natively
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 GBps).
3JK Edition 3.0
1 1 15
1.6 Service-driven Packet Adaptive Modulation
9500 MPR
9500 MPR
Mobile
2G,3G,4G
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
Guarantee 100%
Fully exploit the air bandwidth for any access technology
3JK Edition 3.0
1 1 16
1.7 Power Consumption Reduction
Adaptive modulation:
Increases the power efficiency
Thanks to higher modulation schemes used in different MPR releases
(see graph)
Reduces antenna size by 50%: Less visual impact
Native packets at the air reduce power consumption and antenna size
(*) Compared to last-generation TDM microwave
platform in lab environment
Nodal capability:
Reduces floor space by
50%*: Collapses 6 direction
radio node into only 2
physical units
To reduce power consumption,
rethink network architecture
4%
10%
40%
Cumulated:
40%
14%
22%
85%
Cumulated
125%
2
3
4
5
6
7
8
9
10
11
12
20
30
40
50
60
70
80
90
MPR
R1.1
MPR
R1.2
MPR
R2.0
MPR
R2.1
MPR
R2.2
Power(Watt)
Node consumption Througput perWatt(1+0with mixed6Eth and10xE1)
Mpbs/Watt
P
o
w
e
r
(
W
a
t
t
)
M
p
b
s
/
W
a
t
t
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.
3JK Edition 3.0
1 1 17
1.8 Hybrid or Packet Mode: for Efficient Data Transport
9500 MPR is able to work in:
TDM or Hybrid mode ,
Enable mixed E1 and Ethernet Layer 2
Same simplicity in architecture, same operation, same performances and quality
as any Hybrid/TDM microwave
Packet mode
Ethernet as convergence layer
Simplify and optimized use of infrastructure for any access technology
Common Hardware applicable for both mode
Simple upgrade of OS (through Network management) : from Hybrid OS to Packet OS.
9500 MPR offer Hybrid and Packet with single Hardware solution
3JK Edition 3.0
1 1 18
1.8 Hybrid or Packet Mode: for Efficient Data Transport
[cont.]
TDM
9500 MPR
9500 MPR
GigE
GigE
nxE1/T1
nxE1/T1
IMA/n x E1/T1
IMA/n x E1/T1
Native handoff
Mobile
2G,3G,4G
Fixed
Private
Business office
Phone
DSL
Eth
ATM
TDM
Eth
ATM
9500 MPR can operate in Hybrid or Packet Mode with same hardware
Enabling possibility for smooth migration from Hybrid mode to Packet mode
Packet domain
GbE
9500 MPR
TDM
TDM
Eth
ATM
ATM
GigE handoff
GigE
Network Management E2E Provisioning
SDH domain
E1/STM-1/Eth
MW radio
Converged
Packet networking
DSL Digital Subscriber Line
E1 2.048 Mb/s interface
Eth Ethernet
GigE Gigabit Ethernet
IMA Inverse Multiplexing over ATM
MPLS Multiprotocol Label Switching
PDH Plesiochronous Digital Hierarchy
T1 1.544 Mb/s interface
3JK Edition 3.0
1 1 19
1.9 Packet node: Minimizing Equipment at Each Site
9500 MPR
MSS-8
Up to 6 ODUs connected to a single subrack, with over 6 GB capacity throughput
Single packet matrix provides 16 GB switching capacity, with no need for an
external switch
Any traffic mix in any direction, with no need to duplicate I/O cards
Local traffic
ATM, TDM, Ethernet
Hub site
Protected or
high-capacity
backhaul link
Access
Repeater site
Access
Access
9500 MPR
9500 MPR
9500 MPR
Access
Nodal solution minimize equipment, reduce power consumption and cabling
I/O input/output
MSS Microwave Service Switch
ODU outdoor unit
3JK Edition 3.0
1 1 20
Blank Page
3JK Edition 3.0
1 1 21
2 MPR in New Market Segments
3JK Edition 3.0
1 1 22
2.1 The Most Effective Solution
Full outdoor
Point to point
IDU Nodal-IDU
Networking and MW
-Hybrid solution
TDM native quality
--low cost ptp-
Tree/star/spoke topology
- Physical link protection (1+1)
-link availability 99.999
- Nodal configuration
Dedicated system
for full outdoor
applications
Split mount application
P2p + external
networking gear
Today seldom used in mobile backhauling,
mainly in WiMax/enterprise applications
Represents the vast majority
of the MW market
Today addressed with 2 boxes; MW + SDH/SONET
gear, trend moving toward MPLS based technology
Current
Market
offering
Common ODU
9500 MPR
MPLS networking gear
Segments
Growth are
LTE driven
9500 MPR Release 2 : Multipurpose ODU, to address all applications
3JK Edition 3.0
1 1 23
2.1 The Most Effective Solution [cont.]
MPLS
MPLS
Stand Alone Integrated MW in
fiber Node
Carrier Ethernet
Carrier Ethernet
Nodal
Split-Mount
Hybrid
Connectivity
Optimize
E1 and Ethernet
Site
NO IDU
MSS-1c
Any BS
Any CPE
MSS-4/8 SAR/TSS
Single MW solution
across multiple use
Multi purpose Microwave Radio Concept
Optimize
Ethernet Only
Site
Optimize
Fixed/Mobile
Convergence
Optimize
Microwave Nodal
Site
Optimize
MPLS Node
Site
3JK Edition 3.0
1 1 24
2.2 MPR-e Enabling Zero-Footprint Microwave Configurations
9500 MPR-e
MPT MPT
MPR-e enable zero footprint configurations in Ethernet Only sites
Gigabit Ethernet Gigabit Ethernet
Ethernet Only Site
Nodal Site
9500 MPR-e 9500 MPR
Optimize
IP/MPLS Route
9500 MPR-e
3JK Edition 3.0
1 1 25
2.3 MPR in Last Mile
Up to 12 ODUs
Up to 6 ODUs
Extended 9500 MPR packet transport family to cover last mile access MSS-1c
Low cost, rack length, Very low power consumption, MW radio protection, Hybrid & Packet operational modes
Multipurpose ODU the MPT; to cover all MW applications under a single platform
Zero foot print for Ethernet applications, common to all MSS platform, enables integrated solution for MPLS metro
network
Introducing 9500 MPR-e stand-alone full outdoor
Existing compatibility with 9500 MXC
- Introducing backward compatibility to 9400 AWY to address existing hybrid deployments
3JK Edition 3.0
1 1 26
2.4 LTE and Full Ethernet 3G Ready
Traffic
Classification
(CoS)
802.1p bits
IPV4 DiffSerf
IPV6 Diffserv
VLAN-ID
Ethertype
MPLS Exp. bits
Queue #8
HPQ+CAC
DWRR
Scheduler
RF
Traffic
From
Core
Voice, signalling, NMS, CBR Best Effort classes
Queue #7
Queue #6
Queue #5
Queue #4
Queue #3
Queue #2
Queue #1
Radio
Framer &
Modem
Guaranteed
throughput @
4QAM
CPU
(core)
D
A
T
A

A
W
A
R
E

P
R
O
C
E
S
S
I
N
G
P
A
C
K
E
T

F
R
A
G
M
E
N
T
A
T
I
O
N
HPQ + Call Admission Control per radio direction is the only way to guarantee
Voice (high priority) performances
3JK Edition 3.0
1 1 27
2.5 From Current PDH/SDH Network to Packet Transport
Network Evolution
IP/MPLS
IP/MPLS
NG-SDH
NG-SDH
PDH/SDH/ETH
PDH/SDH/ETH
Packet
Microwave
Packet
Microwave
Current
Mix of techno in the RAN
Deploy Packet Microwave
In Hybrid Mode (9500 MPR)
In the access connecting to
existing SDH aggregation
E2E Circuit emulation/PW
Focus on MPLS aggregation
Integrated 9500 MPR Microwave
solution in IP/MPLS 7705 SAR nodes
MPLS
MPLS
9500 MPR
9500 MPR-e
SAR
Microwave
Networking
Solution
Microwave
Transmission
Solution
Evolution
Converge to a Pseudo Wire
infrastructure
Enable Packet Mode in
Packet Microwave (9500-MPR)
Deploy MPLS in the aggregation
IP/MPLS
Access
(tree, star)
Aggregation
(ring/mesh)
MPT
MSS
9500 MPR and 9500 MPR-e in any network topology
3JK Edition 3.0
1 1 28
2.6 MPR addresses All Microwave Applications in Aggregation
Eth
TDM
Eth
ATM
TDM
MSS 1c
Eth
9500 MPR
MSS-8
MPT
MPT
MSS-4
9500 MPR-e
9500 MPR
MPT
MPT
or
ODU300
9500 MPR
Eth
MPT
or
ODU300
MPT
MPT
or
ODU300
MPT
or
ODU300
Mobile Antenna
Mobile Antenna
Mobile Antenna
Mobile Antenna
Eth
ATM
TDM
9500 MPR
Packet Microwave
Hybrid, Packet and Full outdoor with a single product 9500 MPR
3JK Edition 3.0
1 1 29
2.7 MPR addresses Metro Ring/Partial Mesh Application
MW Access
Network
Eth
TDM
Eth
ATM
TDM
Eth
Mobile Antenna
Mobile Antenna
7705-SAR single node solution for
MW and fiber aggregation rings. Can
be also used as access network hub
connected to the far end with as
9500 MPR node.
9500 MPR
7705 SAR-8
9500 MPR-e
Ring/Partial mesh
IP/MPLS Metro Network
7705 SAR-18
9500 MPR-e
7705 SAR-8
9500 MPR-e
7705 SAR-M
7705 SAR-8
IP/MPLS
3JK Edition 3.0
1 1 30
Blank Page
3JK Edition 3.0
1 1 31
3 System Description
3JK Edition 3.0
1 1 32
3.1 Alcatel-Lucent 9500 Microwave Packet Radio
E1, STM-1, ATM-IMA and Eth
No performance
degradation
3JK Edition 3.0
1 1 33
3.2 9500 MPR System Family
9500 MPR radio system family supports, in a common platform,
PDH E1, SDH STM1, ATM-IMA traffic and packet data (Ethernet) applications.
Outdoor transceivers are available
in the frequency range from 6 GHz up to 38 GHz and 80 GHz.
For the Outdoor transceiver,
1+0 is the optimized configuration, with branching systems outside the ODU,
1+1 configuration is obtained with external dedicated mechanical arrangement.
MSS-8
(2U height)
(19 rack
length)
MSS-4
(1 U height)
(19 rack
length)
MSS-1c
(1U height)
(half 19 rack
length)
Zero-
footpri
nt
Up to 12 with
ethernet
cable
Up to 6 with
ethernet
cable
Up to 2 with
ethernet cable
Ge MPT
Up to 6 with
coaxial cable
Up to 2 with
coaxial cable
- - ODU
300
Up to xx
coaxial cable
Up to x with
coaxial cable
- - AWY
ODU
ODU 300
MPT
AWY-ODU
MSS-4 MSS-8
No IDU
MSS-1c
Backward compatibility with hybrid installed base
3JK Edition 3.0
1 1 34
3.2 9500 MPR System Family [cont.]
9500 MPR
Microwave Packet Radio
Three types of
OutDoor Unit
ODU 300
MPT
AWY-ODU
Three types of MSS
(Microwave Service Switch)
MSS-8
( 8 slots )
MSS-4
( 4 slots )
MSS-1c
( Terminal InDoor Unit )
MPT
MPR-e
Stand alone
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 AWY ODU) or
with one coaxial cable for the power supply and one Ethernet optical or electrical cable (with MPT).
3JK Edition 3.0
1 1 35
3.3 9500 MPR Key Features
3JK Edition 3.0
1 1 36
3.3 9500 MPR Key Features [cont.]
Link Aggregation Group (Radio/Ethernet):
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.
3JK Edition 3.0
1 1 37
3 System description
3.4 9500 MPR Node
The 9500 MPR Node supports up to 6 RF links for operation on the same or different frequency bands using
the MSS-8 Unit.
The ODU for each link is connected to 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.
3JK Edition 3.0
1 1 38
3.4 9500 MPR Node [cont.]
Local traffic
NxE1 TDM
NxIMA ATM
NxF/Gig Ethernet
Operational modes
Hybrid and packet mode
Microwave trunk
MSS-8: up to 12 ODUs
MSS-4: up to 6 ODUs
Highest switching capacity (16 Gb/s)
and capacity throughput (>4 Gb/s) in
the market, and E1 termination (up to
192xE1s)
5x less space in nodal configuration
(compared to traditional hybrid-only
nodes)
6x less power consumption in
6 directions packet node (compared
to traditional hybrid systems)
NE: 9500 MPR
MSS-4/8 MSS-4/8
MSS-8/-4
9500 MPR-e
9500 MPR
9500 MPR
9500 MPR
Split mount Hybrid or packet node
NE: 9500 MPR
Commercial
I tem
MSS-4
MSS-8
Operates as:
Microwave Service Switch 4/8 (MSS-4 / MSS-8)
3JK Edition 3.0
1 1 39
Slot 1 reserved for Core-E Main
Slot 2 reserved for Core-E Spare
Slot 3 to 8 Universal (any Tributary unit or Modem unit or MPT Access
unit)
Slot 8 can be equipped also with AUX peripheral card
Slot 9 reserved for FANS
The cards belonging to a protected configuration must be installed on the
same row (the Main card is on the left side, the Spare card is on the right
side)
MSS-8
Slot 1 Slot 2
Slot 3 Slot 4
Slot 5 Slot 6
Slot 7 Slot 8
S
l
o
t

9
Supports 6 Unprotected links or
1 Protected and 4 Unprotected links or
2 Protected and 2 Unprotected links or
3 Protected links
3JK Edition 3.0
1 1 40
Simplified block diagram of the MSS-8
3JK Edition 3.0
1 1 41
Slot 1 reserved for Core-E Main
Slot 2 reserved for Core-E Spare
Slot 3 and 4 Universal (any Tributary unit or Modem unit or MPT Access
unit)
Slot 4 can be equipped also with AUX peripheral card
Slot 5 reserved for FANS
In case of protected configuration the Main card is on the left side, the
Spare card is on the right side.
MSS-4
Slot 1 Slot 2
Slot 3 Slot 4
S
l
o
t

5
Supports 2 Unprotected links or
1 Protected link
3JK Edition 3.0
1 1 42
Simplified block diagram of the MSS-4
3JK Edition 3.0
1 1 43
MSS implements functionalities of grooming, routing, switching and
protection, exploiting a packet oriented technology.
The Core-E platform, with symmetrical cross-connection functions,
manages different radio directions, with the possibility to add-drop
tributaries in case of local TDM/Ethernet accesses. Core-E platform is
based on packet technology (Ethernet Switch) with a generic interface
serial GbEth between Core-E and peripherals
The peripherals are independent modules connecting the Core-E to a
set of different external interfaces, through a high speed serial bus.
The available peripherals are:
32xE1 PDH access unit, ASAP access unit (ATM 16xE1), AUX peripheral unit
STM-1 local access module
Modem unit (to interface the ODU300)
MPT Access card and MPT Access card with PFoE (to interface the MPT)
AWY Access card (to interface the ODU AWY)
The TDM incoming traffic is converted into Ethernet packets and then
sent to the Ethernet switch; the packet overhead is optimized before to
be sent in the air.
32E1/DS1 PDH access unit: provides the external interfaces for up to 32xE1 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; it contains the switch for the EPS Core-E protection and the
DC/DC converter unit.
STM-1 local access module: 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; it contains the switch for the EPS
Core-E protection and the DC/DC converter unit.
ASAP access unit: provides the 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
"special" Ethernet traffic is managed by MPR following to RFC 4717 (IETF ATM PseudoWire
EdgetoEdgeeEmulation, PWE3) with N-1 encapsulation format.
AUX peripheral unit: provides the external interfaces for Service Channels access and Housekeeping alarms.
Modem unit: 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 and the DC/DC converter unit.
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-MC through an electrical Ethernet traffic connector.
AWY access card: this unit is used to interface the ODU AWY. It sends/receives standard Ethernet packets
to/from both Core-E modules. It contains the logic for the EPS Core-E protection and the DC/DC converter
unit.
3JK Edition 3.0
1 1 44
Stacking Configuration
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.
3JK Edition 3.0
1 1 45
Stacking Configuration [cont.]
With the Core protection max. 2 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.
3JK Edition 3.0
1 1 46
3.5 9500 MPR Terminal
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.
3JK Edition 3.0
1 1 47
3.5 9500 MPR Terminal [cont.]
Traditional
point-to-point IDU
(e.g., 9400 AWY
IDU)
Local traffic
4x F/Gig Ethernet
10xE1
Operational modes
Hybrid and packet mode
Microwave trunk
2xMPT ODU connections
(electrical/optical Ethernet)
50% space reduction compared to
traditional terminal IDU in 1+0
configuration
4x less space for MW radio
protection with single size IDU
7x more capacity then 64 Mb/s
(32xE1) traditional terminals
NE: 9500 MPR
MSS-1c MSS-1c
MSS-8/-4
MSS-1c
MSS-1c
MSS-1c
MSS-1c
Point-to-point link Last mile/remote site for node
NE: 9500 MPR
Commercial
I tem
Operates as:
MSS-1c
Microwave Service Switch 1 Terminal (MSS-1c)
3JK Edition 3.0
1 1 48
Packet Radio Solution for Tail
Cost effective solution
Compact : 1U rack size
Fully part of MPR family
Low power consumption (13 W)
Eth
TDM
MPT
MPT
MSS 8
ODU300
MPT
MSS 8
ODU300
MSS 8
MSS 1c
MPT
MSS-1c + MPT: Compact and Low Consumption Solution for Tail
MSS-1c Characteristics:
- 10 x E1 (hybrid TDMtoTDM and Packet Mode TDMtoETH)
- 4 GEthernet user ports
- Up to 2 MPT
1+0,
1+1,
repeater configurations.
- L2 switch
QoS (IEEE 802.1p),
Diffserv,
VLAN management.
- SynchE
- Housekeeping
- 2 ports for TMN chaining
3JK Edition 3.0
1 1 49
Simplified block diagram of the MSS-1c
ETHERNET
SWITCH
FPGA
PFoE
E1 INTERFACE
IWF
LIU
8
2
8 E1
2 E1
Lightning
Protection
PSU
Power
supply
LCT RJ45
NMS1 RJ45
NMS2 RJ45
FAN unit connector
4x 10/100/1000
Ethernet ports
MPT1 (opt. Int.)
MPT2 (opt. Int.)
MPT1 (elect. Int.)
MPT2 (elect. Int.)
R
A
D
I
O
I
N
T
E
R
F
A
C
E
HK
(not supported
in the current
release)
MSS-1c
MSS1-c platform:
symmetrical Cross-connection function
able to manage different radio directions
add-drop tributaries in case of local PDH/Ethernet accesses
2 x Electrical GbEth + 2 x Optical GbEth
Peripherals
10 x E1 local access function (2 x Sub-D 37 pins)
MPT Access function (to MPT)
3JK Edition 3.0
1 1 50
Compact IDU (MSS-1c) implements functionalities of grooming, routing,
switching and protection, exploiting a packet oriented technology.
The MSS-1c, with symmetrical cross-connection functions, manages different
radio directions, with the possibility to add-drop tributaries in case of local
PDH/Ethernet accesses. MSS-1c is based on packet technology (Ethernet Switch)
with a generic interface serial GbEth between Ethernet Switch and peripherals
The peripherals are independent functions inside the compact IDU (MSS-1c)
connecting the Ethernet Switch to a set of different external interfaces,
through a high speed serial bus. The available peripherals are:
10 x E1 local access function
MPT Access function (to interface the Microwave Packet Transport)
The PDH incoming traffic is converted into Ethernet packets and then sent to
the Ethernet switch; the packet overhead is optimized before to be sent in the
air.
10E1/DS1 local access function: provides the external interfaces for up to 10xE1 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.
3JK Edition 3.0
1 1 51
3.6 OutDoor Unit 300
335,9 Mbit/s 150 E1 6 256 QAM
304,7 Mbit/s 136 E1 5 128 QAM
161,0 Mbit/s 72 E1 4 16 QAM
56 MHz
172,0 Mbit/s 77 E1 6 256 QAM
151,7 Mbit/s 68 E1 5 128 QAM
126,1 Mbit/s 56 E1 5 64 QAM
107,3 Mbit/s 48 E1 4 32 QAM
83,6 Mbit/s 37 E1 4 16 QAM
41,1 Mbit/s 18 E1 2 4 QAM
28 MHz
62,3 Mbit/s 27 E1 5 64 QAM
41,1 Mbit/s 18 E1 4 16 QAM
19,9 Mbit/s 8 E1 2 4 QAM
14 MHz
30,5 Mbit/s 13 E1 5 64 QAM
19,9 Mbit/s 8 E1 4 16 QAM
9,3 Mbit/s 4 E1 2 4 QAM
7 MHz
Ethernet Throughput (1518 bytes) # E1 (TDM2TDM) ETSI Class FCM Mode Channel
ODU300 (Static Modulation) : Radio capacity, channelling and modulation
The table summaries the relations among Radio capacity, channelling scheme and modulation (Static
Modulation).
3JK Edition 3.0
1 1 52
ODU300 (Adaptative Modulation) : Radio capacity, channelling and modulation
3.6 OutDoor Unit 300 [cont.]
30,5 Mbit/s 13 E1 5 64 QAM
19,9 Mbit/s 8 E1 4 16 QAM
9,3 Mbit/s 4 E1 2 4 QAM
7 MHz
62,3 Mbit/s 27 E1 5 64 QAM
41,1 Mbit/s 18 E1 4 16 QAM
19,9 Mbit/s 8 E1 2 4 QAM
14 MHz
126,1 Mbit/s 56 E1 5 64 QAM
83,6 Mbit/s 37 E1 4 16 QAM
41,1 Mbit/s 18 E1 2 4 QAM
28 MHz
Ethernet Throughput
(1518 bytes)
# E1 (Note)
(TDM2TDM)
ETSI Class ACM Mode Channel Spacing
Note:
The Admission Control for TDM flows (cross-connected to radio direction working in Adaptive Modulation)
can be enabled or disabled.
When the Admission Control is enabled, the check is performed taking into account the capacity of the 4
QAM modulation scheme for the relevant Channel Spacing.
When the Admission Control is disabled, the check is performed taking into account the capacity of the
highest modulation scheme for the relevant Channel Spacing (64 QAM for 4-16-64 QAM range or 16 QAM for
4-16 QAM range).
3JK Edition 3.0
1 1 53
2 9500MPR Family
3.7 Microwave Packet Transport
It is a new multipurpose ODU to address any microwave application,
extremely compact in size providing:
MPT MC up to 200Mbps
MPT HC/MPT-HC V2 up tp 440Mbps
MPT GC millimeter wave
MPT-xx can be deployed in stand-alone configuration (9500 MPR-e) or
it can be deployed in split mount solution connected to any MSS-x IDU.
Up to 12 MPT connected to an MSS-8; highest density ever
Up to 6 MPT connected to an MSS-4; highest density ever
Up to 2 MPT HC/MC connected to MSS-1c
9500 MPR-e it is the stand alone, full outdoor application of the MPT xx
to address full Ethernet site backhauling (fix or mobile alike).
Deployed together with 7705SAR or 1850 TSS to address converged MPLS
metro networks reducing the number of deployed equipment.
What is MPT ?
3JK Edition 3.0
1 1 54
3.7 Microwave Packet Transport [cont.]
Local traffic
Gig Ethernet
Microwave capacity
MPT-GC up to 1 Gb/s
Millimeter wave
MPT-MC
Typical 157 Mb/s, 64-byte Ethernet 240 Mb/s
MPT-HC up to 530 Mb/s
Typical 350 Mb/s, 64-byte Ethernet 530 Mb/s
Single solution to operate as
standalone and split-mount
Interconnect Cable
Gig Ethernet
CAT-5 electrical or optical
NE: 9500 MPR-e
MSS-1c
NE: 9500 MPR
MPT
9500 MPR-e network element
stand-alone solution
9500 MPR network element
split-mount solution
MSS-8/-4
Commercial
I tem
Operates as:
3JK Edition 3.0
1 1 55
MPT-HC/MPT-HC V2/MPT-MC : Radio capacity, channelling scheme
and modulation (Static Modulation) (1/2)
86,7 Mbit/s 41 6 256 QAM (NB3)
73,5 Mbit/s 34 5 128 QAM
62,0 Mbit/s 29 5 64 QAM
50,3 Mbit/s 23 4 32 QAM
40,7 Mbit/s 19 4 16 QAM
19,9 Mbit/s 9 2 4 QAM
14
40,6 Mbit/s 19 6 256 QAM (NB3)
35,4 Mbit/s 16 5 128 QAM
29,6 Mbit/s 13 5 64 QAM
24,2 Mbit/s 11 4 32 QAM
19,4 Mbit/s 9 4 16 QAM
8,8 Mbit/s 4 2 4 QAM
7
Typical Ethernet Throughput
(1518 bytes)
# E1
(TDM2TDM)
ETSI Class FCM Mode Channel Spacing
(MHz)
Modulation).
N.B.1: New ETSI mask.
N.B.2: MPT-MC does not support this Channel Spacing.
N.B.3: MPT-MC does not support this FCM mode.
3JK Edition 3.0
1 1 56
and modulation (Static Modulation) (2/2)
339,4 Mbit/s 160 6 256 QAM
298,2 Mbit/s 141 5 128 QAM
252,2 Mbit/s 119 5 64 QAM
195,6 Mbit/s 92 4 32 QAM
159,3 Mbit/s 75 4 16 QAM
56 (NB2)
220,1 Mbit/s 104 5 128 QAM
186,1 Mbit/s 88 5 64 QAM
40 (NB2)
180,2 Mbit/s 85 6 256 QAM (NB3)
151,9 Mbit/s 71 5 128 QAM
128,4 Mbit/s 60 5 64 QAM
106,9 Mbit/s 50 4 32 QAM
83,5 Mbit/s 39 4 (NB1) 16 QAM
41,1 Mbit/s 19 2 (NB1) 4 QAM
28
Typical Ethernet Throughput
(1518 bytes)
# E1
(TDM2TDM)
ETSI Class FCM Mode Channel Spacing
(MHz)
Modulation).
N.B.1: New ETSI mask.
N.B.3: MPT-MC does not support this FCM mode.
3JK Edition 3.0
1 1 57
and modulation (Adaptive Modulation) (1/2)
62,0 Mbit/s 64 QAM to 256 QAM 5 64 QAM
14
7
Typical Ethernet
Throughput
(1518 bytes)
Modulation range ETSI Class ACM Mode
Reference
Channel Spacing
(MHz)
Note:
The Admission Control for TDM flows (cross-connected to radio direction working in Adaptive
Modulation) can be enabled or disabled.
When the Admission Control is enabled, the check is performed taking into account the capacity of the
lowest modulation scheme for the relevant Channel Spacing.
highest modulation scheme for the relevant Channel Spacing.
3JK Edition 3.0
1 1 58
and modulation (Adaptive Modulation) (2/2)
56 (NB1)
186,1 Mbit/s 64 QAM to 128 QAM 5 64 QAM 40 (NB1)
128,4 Mbit/s 64 QAM to 256 QAM 5 64QAM
106,9 Mbit/s 32 QAM to 256 QAM 4 32QAM
28
Typical Ethernet
Throughput
(1518 bytes)
Modulation range ETSI Class ACM Mode
Reference
Channel Spacing
(MHz)
Note:
The Admission Control for TDM flows (cross-connected to radio direction working in Adaptive
Modulation) can be enabled or disabled.
When the Admission Control is enabled, the check is performed taking into account the capacity of the
lowest modulation scheme for the relevant Channel Spacing.
highest modulation scheme for the relevant Channel Spacing.
3JK Edition 3.0
1 1 59
4 Radio Configuration
3JK Edition 3.0
1 1 60
4 Radio Configuration
4.1 Radio Configuration
1+0 unprotected
1+1 Hot-Standby (HSB)
two types of coupler for ODU300:
3 dB/3 dB balanced coupler or 1.5 dB/6.0 dB unbalanced coupler
two types of coupler for MPT-HC/MPT-MC:
3 dB/3 dB balanced coupler or 1 dB/10 dB unbalanced coupler
1+1 Hot-Standby Space Diversity (HSB SD) (no coupler)
1+1/2x(1+0) Frequency Diversity (FD) (co-polar)
1+1/2x(1+0) Frequency Diversity (FD) (hetero-polar)
N.B.: MPT-MC does not support the FD configuration.
N.B.: In 1+1 configuration the 2 Outdoor Units must be of the same types.
3JK Edition 3.0
1 1 61
5 System Configuration
3JK Edition 3.0
1 1 62
5.1 Example of System configurations
PDH/ATM Over Ethernet Packet Node
Mapping of 32 E1 TDM and 16 E1 ATM on Ethernet
MSS
Ethernet
Switch
Ethernet
Switch
3
2

E
1

T
D
M
P
e
r
i
p
h
e
r
a
l
3
2

E
1

T
D
M
P
e
r
i
p
h
e
r
a
l
E
m
b
e
d
d
e
d
E
T
H
i
n
t
e
r
f
a
c
e
s
E
m
b
e
d
d
e
d
E
T
H
i
n
t
e
r
f
a
c
e
s
1
6

E
1

A
T
M
P
e
r
i
p
h
e
r
a
l
1
6

E
1

A
T
M
P
e
r
i
p
h
e
r
a
l
3JK Edition 3.0
1 1 63
5.1 Example of System configurations [cont.]
PDH/SDH/ATM and Ethernet Terminal Packet Transport
32 E1 TDM and 16 E1 ATM Access, 1 Radio Direction
MSS
Ethernet
Switch
Ethernet
Switch
MW ODU
Peripheral
MW ODU
Peripheral
E
m
b
e
d
d
e
d
E
T
H
i
n
t
e
r
f
a
c
e
s
E
m
b
e
d
d
e
d
E
T
H
i
n
t
e
r
f
a
c
e
s
3
2

E
1

T
D
M
P
e
r
i
p
h
e
r
a
l
3
2

E
1

T
D
M
P
e
r
i
p
h
e
r
a
l
1
6

E
1

A
T
M
P
e
r
i
p
h
e
r
a
l
1
6

E
1

A
T
M
P
e
r
i
p
h
e
r
a
l
3JK Edition 3.0
1 1 64
PDH/SDH/ATM and Ethernet Add/Drop N1 Packet Node
Ethernet and 32 E1 TDM and 16 E1 ATM Local Access, 2 unprotected links
MSS
Ethernet
Switch
Ethernet
Switch
MW ODU
Peripheral
MW ODU
Peripheral
E
m
b
e
d
d
e
d
E
T
H
i
n
t
e
r
f
a
c
e
s
E
m
b
e
d
d
e
d
E
T
H
i
n
t
e
r
f
a
c
e
s
MW ODU
Peripheral
MW ODU
Peripheral
3
2

E
1

T
D
M
P
e
r
i
p
h
e
r
a
l
3
2

E
1

T
D
M
P
e
r
i
p
h
e
r
a
l
1
6

E
1

A
T
M
P
e
r
i
p
h
e
r
a
l
1
6

E
1

A
T
M
P
e
r
i
p
h
e
r
a
l
3JK Edition 3.0
1 1 65
PDH/SDH/ATM and Ethernet Terminal Packet Node
Ethernet and 32 E1 TDM and 16 E1 ATM Local Access, 1 protected link
MSS
Ethernet
Switch
Ethernet
Switch
MW ODU
Peripheral
MW ODU
Peripheral
E
m
b
e
d
d
e
d
E
T
H
i
n
t
e
r
f
a
c
e
s
E
m
b
e
d
d
e
d
E
T
H
i
n
t
e
r
f
a
c
e
s
MW ODU
Peripheral
MW ODU
Peripheral
3
2

E
1

T
D
M
P
e
r
i
p
h
e
r
a
l
3
2

E
1

T
D
M
P
e
r
i
p
h
e
r
a
l
1
6

E
1

A
T
M
P
e
r
i
p
h
e
r
a
l
1
6

E
1

A
T
M
P
e
r
i
p
h
e
r
a
l
3JK Edition 3.0
1 1 66
PDH/SDH/ATM and Ethernet Add/Drop Packet Node
Ethernet and 32 E1 TDM and 16 E1 ATM Local Access,
1 unprotected link and 1 protected link
MSS
Ethernet
Switch
Ethernet
Switch
E
m
b
e
d
d
e
d
E
T
H
i
n
t
e
r
f
a
c
e
s
E
m
b
e
d
d
e
d
E
T
H
i
n
t
e
r
f
a
c
e
s
MW ODU
Peripheral
MW ODU
Peripheral
3
2

E
1

T
D
M
P
e
r
i
p
h
e
r
a
l
3
2

E
1

T
D
M
P
e
r
i
p
h
e
r
a
l
1
6

E
1

A
T
M
P
e
r
i
p
h
e
r
a
l
1
6

E
1

A
T
M
P
e
r
i
p
h
e
r
a
l
MW ODU
Peripheral
MW ODU
Peripheral
MW ODU
Peripheral
MW ODU
Peripheral
3JK Edition 3.0
1 1 67
Blank Page
3JK Edition 3.0
1 1 68
End of Module
Introduction
3JK Edition 2.0
Module 2
Architecture
3JK Edition 2.0
Section 1
Product Overview
3JK Edition 2.0
Product Overview Architecture
1 2 2
Blank Page
First edition External Consultant 2007-07-30 01
Document History
3JK Edition 2.0
1 2 3
Objectives
Objectives: to be able to
describe the main functionalities of the 9500 MPR
Node and Terminal.
3JK Edition 2.0
1 2 4
Objectives [cont.]
3JK Edition 2.0
1 2 5
Table of Contents
Page
1 MSS Architecture 7
1.1 9500 MPR Architecture 8
1.2 MSS 9
1.3 Flash Cards with Licences 11
1.4 ODUs 12
1.5 MSS-ODU300 cable (Interfaces and Traffic) 13
1.6 MPT 14
1.7 MSS-MPT Cable (Interfaces and Traffic) 15
1.7.1 MPT-HC connectivity 16
1.7.2 MPT-HC V2 connectivity 19
1.7.3 MPT-MC connectivity 23
Blank Page 26
2 Traffic Profiles 27
2.1 Managed Services and profiles 28
2.1.1 TDM to TDM flow 29
2.1.2 TDM to ETH flow 30
2.1.3 SDH to SDH flow 31
2.1.4 ETH to ETH flow 32
2.1.5 ATM to ATM flow 33
2.1.6 ATM to ETH flow 34
2.2 Traffic profiles 35
2.3 TDM2TDM 38
2.4 TDM2Eth 40
2.5 SDH2SDH 42
2.6 ATM Traffic Management 44
2.7 ETH2ETH 47
2.8 Ethernet Traffic Management 48
3 Traffic Management (QoS) 51
3.1 Quality Of Services (QoS) in the MPR Node 52
3.1.1 QoS in the Core-E 53
3.1.2 Radio Air Block QoS 55
3.1.3 How 9500 MPR manage QoS 57
3.1.4 Flows classification 59
3.2 Quality Of Services (QoS) in the MPR Terminal 63
3.2.1 QoS in the MSS-1c 64
3.2.2 Flows classification 66
3.3 Quality Of Services (QoS) in the MPT 68
3.3.1 Radio Air Block QoS for MPR Node 69
3.3.2 Radio Air Block QoS for MPR Terminal 70
3.3.3 Radio Air Block QoS Scheduler 71
3.4 Quality Of Services (QoS) in the MPR-e 72
Blank Page 74
4 LAG (Link Aggregation Group) 75
4.1 LAG overview 76
4.1.1 Link aggregation on Radio ports (Radio LAG) 77
4.1.2 Link aggregation on User Ethernet ports (Ethernet LAG) 79
Blank Page 80
5 Synchronisation 81
5.1 Synchronisation 82
5.2 Clock Source Selection and Distribution 88
5.3 Differential/Adaptative clock recovery 89
5.4 Synchronisation Interface 92
5.5 Synchronisation Interface 93
5.6 Synchronisation Interface in MPR-e 97
6 Cross-connections 98
3JK Edition 2.0
1 2 6
Page
6.1 Cross-connection 99
6.2 E1 Cross-connection 101
6.3 STM-1 Cross-connections 102
6.4 Radio-Radio Cross-connection 103
6.5 Ethernet Cross-connection 104
6.6 ATM PW Cross-connection 105
6.7 ATM Light Cross-connection Provisioning 106
6.8 MAC SA of ATM PW Generated by ASAP Unit 107
Blank Page 108
7 Protections with ODU300 109
7.1 Protections with ODU300 110
7.2 RPS Switching Criteria 113
7.3 EPS Switching Criteria 114
7.4 HSB Switching Criteria 115
Blank Page 116
8 Protections with MPT-HC/MPT-HC V2 117
8.1 Protections with MPT-HC/MPT-HC V2 118
Blank Page 124
9 XPIC (with MPT-HC V2 only) 125
9.1 XPIC (with MPT-HC V2 only) 126
10 Protection with MPT-MC 129
10.1 Protection with MPT-MC 130
11 Core-E protection 135
11.1 Core-E protection 136
11.2 Core-E protection Switching Criteria 140
12 Ring Protection 141
12.1 ERPS operation 142
End of Module 148
3JK Edition 2.0
1 2 7
1 MSS Architecture
3JK Edition 2.0
1 2 8
1 MSS Architecture
1.1 9500 MPR Architecture
16 Gb/s
Ethernet Switch
16 Gb/s
Ethernet Switch
MW ODU
Peripheral
MW ODU
Peripheral
S
D
H
/
T
D
M
P
e
r
i
p
h
e
r
a
l
S
D
H
/
T
D
M
P
e
r
i
p
h
e
r
a
l
NxE1 TDM Stream
2xSTM-1 Stream
SDH or TDM over Ethernet standard
mapping
Standard Gigabit Ethernet
Patented data-aware algorithms:
Service type is recognized
Bandwidth Optimization
Latency control
BER improvement
Microwave Transport
ATM
Peripheral
ATM
Peripheral
ATM PseudoWiring
ASAP board
NxE1 ATM-IMA
E
m
b
e
d
d
e
d
E
T
H
i
n
t
e
r
f
a
c
e
s
E
m
b
e
d
d
e
d
E
T
H
i
n
t
e
r
f
a
c
e
s
This chart shows the architecture of MPR equipment. The core of the device is a 10 gb/s Ethernet switch
able to manage several kinds of peripheral [TDM, ETHERNET (embedded) and ATM-IMA (from R.1.3)] and
interface the packetized tributaries with the MW ODU through an apposite peripheral endowed of
patented data-aware algorithms for bandwidth optimization and BER improvement.
3JK Edition 2.0
1 2 9
1 MSS Architecture
1.2 MSS
Controller PSU
4x10/100/1000
Ethernet
LIU
Flash
RAM
Core-E
GbEth
AUX
Peripheral
Module
Access
Peripherals
Radio
Peripherals
MPT Access Module
(Giga Ethernet
interface)
(to MPT-HC/MPT-MC)
2 SFPs
(Optional)
LIU
MSS-8 MSS-4
GbEth
ASAP Access
Module
GbEth
32xE1 Access
Module
ETHERNET
SWITCH
MODEM Module
(IF interface)
(to ODU300)
GbEth
GbEth
2xSTM-1
Access
Module
Core-E platform:
add-drop tributaries in case of local PDH/ASAP/Ethernet accesses
4 x Electrical GbEth + 2 optional SFPs
Peripherals (6 modules in MSS-8; 2 modules in MSS-4)
32 x E1 PDH access module (SCSI 68 32E1)
2 x STM-1 access module (2 optional electrical or optical SFP)
ASAP (ATM 16xE1) access module (SCSI 68 16E1)
AUX peripheral module
Modem module (to ODU300)
MPT Access module (to MPT)
3JK Edition 2.0
1 2 10
1 MSS Architecture
1.2 MSS [cont.]
MSS-1c
ETHERNET
SWITCH
FPGA
PFoE
E1 INTERFACE
IWF
LIU
Up to
16E1
(*)
Lightning
Protection
PSU
Power
supply
LCT RJ45
NMS1 RJ45
NMS2 RJ45
FAN unit connector
4x 10/100/1000
Ethernet ports
MPT1 (opt. Int.)
MPT2 (opt. Int.)
MPT1 (elect. Int.)
MPT2 (elect. Int.)
R
A
D
I
O
I
N
T
E
R
F
A
C
E
HK
(not supported
in the current
release)
MSS-1c
(*) Two variants of MSS-1c are available:
MSS-1c providing 10E1 and 4 User ethernet ports
MSS-1c 16E1 providing 16E1 and 4 User Ethernet ports. This version is HW ready to manage up to 2 STM-
1 frames (instead of 2 Ethernet ports) not supported by the current SW Release
MSS1-c platform:
add-drop tributaries in case of local PDH/Ethernet accesses
2 x Electrical GbEth + 2 x Optical GbEth
Peripherals
10 x E1 local access function (2 x Sub-D 37 pins)
MPT Access function (to MPT)
3JK Edition 2.0
1 2 11
1 MSS Architecture
1.3 Flash Cards with Licences
The licences are stored in the Flash card installed in the Core-E.
Different types of licence according to:
Capacity
Service: TDM2TDM or TDM2ETH
Static Modulation (FCM) or Adaptive Modulation (ACM)
Note: The Flash card stores
1. The License
2. The Equipment Software
3. The Equipment MIB
4. The Equipment MAC Address.
3JK Edition 2.0
1 2 12
1 MSS Architecture
1.4 ODUs
Several types of ODU are available: ODU300 , MPT-HC (High Capacity) ,
MPT-MC (Medium Capacity)
Both ODUs are designed for direct-antenna mounting.
ODU300 and MPT-HC/MPT-HC V2 support:
Modulation rates from 4 QAM to 256 QAM
Bandwidths from 7 to 56 MHz
Frequency bands from 6 to 38 GHz
MPT-MC support:
Modulation rates from 4 QAM to 128 QAM
Bandwidths from 7 to 28 MHz
3JK Edition 2.0
1 2 13
1 MSS Architecture
1.5 MSS-ODU300 cable (Interfaces and Traffic)
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 separatly 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.
3JK Edition 2.0
1 2 14
1 MSS Architecture
1.6 MPT
Two types of MPT are available:
MPT-MC
MPT-HC/MPT-HC V2
Both MPTs are designed for
direct-antenna mounting.
MPT-MC support:
Modulation rates from QPSK to 128 QAM
Bandwidths from 3,5 to 28 MHz
MPT-HC/MPT-HC V2 support:
Modulation rates from QPSK to 256 QAM
Bandwidths from 3,5 to 56 MHz
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).
MPT-HC V2 is XPIC-ready (by the installation of a dedicated module).
3JK Edition 2.0
1 2 15
1 MSS Architecture
1.7 MSS-MPT Cable (Interfaces and Traffic)
Electrical connection
(for MPT-MC, MPT-HC and MPT-HC V2)
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.
Optical connection
(only for MPT-HC and MPT-HC V2)
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 500 m.
Note: 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.
3JK Edition 2.0
1 2 16
1.7.1 MPT-HC connectivity
CAT5e
RJ45
Coaxial cable
QMA and N
Ethernet CAT5e
Ethernet CAT5e
and RJ45
Power extractor
MPT Access Card
MPT-HC electrical connectivity (up to 100m)
MPT Access Card PoE
2 MPT per MPT Access Card
2x 1000BaseT port with Power over CAT5e cable
(Electrical connectivity Data+Power over a single CAT cable)
2x SFP ports for optical connection option
2x Coax connection
(power feed in case of Optical connection)
3JK Edition 2.0
1 2 17
1.7.1 MPT-HC connectivity [cont.]
Fiber
LC-LC
Coaxial cable
QMA-N
fiber
Coaxial cable
N-N
Pigtail
RJ45-N
MPT-HC optical connectivity (up to 350m)
Pigtail: N-RJ45 two wires Transition Connector, Reference: 3CC52159AAxx
3JK Edition 2.0
1 2 18
1.7.1 MPT-HC connectivity [cont.]
Coaxial cable
Up to 100m
Ethernet CAT5e
Coaxial cable
+lightning
arrestor
+ low pass
filter
+ pigtail
battery
Up to 350m
Optical cable
+lightning
arrestor
+ low pass
filter
+ pigtail
battery
MPT-HC connectivity to CORE-E
Low Pass Filter: Reference: 1AB251350001
Lightning Arrestor: Reference: 3CC50030AAAA
3JK Edition 2.0
1 2 19
1.7.2 MPT-HC V2 connectivity
MPT-HC V2 One cable (MPT Access unit to MPT-HC V2)
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 max cable length is 100 m.
The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool
(1AD160490001).
3JK Edition 2.0
1 2 20
1.7.2 MPT-HC V2 connectivity [cont.]
MPT-HC V2 Two cables (MPT Access unit to MPT-HC V2)
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 MPT-
HC V2
Note: In case of length lower than 100m and presence in the field of 1 coaxial alredy installed and free it
is recomended to use the coax cable to minimise the installation effort.
The second cable is an Ethernet optical cable.
The Ethernet optical cable is preassembled and available in different lengths (up to 450 m).
Note: A special cord adapter must be connected to the coaxial cable on the MPT-HC V2.
3JK Edition 2.0
1 2 21
MPT-HC V2 Two cables (MPT Access unit to MPT-HC V2)
Two cables connect an MPT Access unit in the MSS to its MPT-HC V2:
HC V2
Note: A special cord adapter must be connected to the coaxial cable on the MPT-HC V2.
3JK Edition 2.0
1 2 22
MPT-HC V2 Two cables (Core-E unit to MPT-HC V2)
Two cables connect the MPT:
one optical cable connected to port#5 or port #6 of the Core-E unit
a coaxial cable connected to the station battery to provide the power supply.
3JK Edition 2.0
1 2 23
1.7.3 MPT-MC connectivity
Ethernet CAT5e
Twin power injector
(Not real colour)
Option 2 Option 1
MSS4/8
MSS-1c
MPT-MC electrical connectivity (up to 100m)
Both injectors include:
Powering of two MPT
Lightning protection
DC protection
LEDs for power output
Power Injector plug-in
Power Injector box
3JK Edition 2.0
1 2 24
1.7.3 MPT-MC connectivity [cont.]
Up to 100m Coaxial cable
N-N
Ethernet CAT5e
Up to 350m
Coaxial cable
Optical connection
LC-xx
battery battery
NB: lightning arrestor is same as MXC
+lightning
arrestor
+ low pass
filter
+ pigtail
+lightning
arrestor
+ low pass
filter
+ pigtail
MPT-HC stand-alone connectivity
Low Pass Filter: Reference: 1AB251350001
Lightning Arrestor: Reference: 3CC50030AAAA
3JK Edition 2.0
1 2 25
1.7.3 MPT-MC connectivity [cont.]
Battery 1
Battery 2
Power Injector plug-in
Power +
data
Power injector box
Cable 2x1 mm
Same as MSS-1c
Both injectors include:
powering of two MPT
lightning protection
DC protection
LEDs for power output
MPT-MC stand-alone connectivity (up to 100m)
3JK Edition 2.0
1 2 26
Blank Page
3JK Edition 2.0
1 2 27
2 Traffic Profiles
3JK Edition 2.0
1 2 28
2 Traffic Profiles
2.1 Managed Services and profiles
Association of managed services and profiles:
TDM to TDM This is the typical service associated to a traditional TDM
network in which E1 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 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. STM-1 traffic is transparently transported, switched and
terminated inside a MPR network.
ETH to ETH 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 auto-learning algorithm, VLANs etc.
ATM to ATM 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 This profile allows the ATM service to be terminated and
encapsulated into an Ethernet stream towards an IP/MPLS Core Network.
3JK Edition 2.0
1 2 29
2.1.1 TDM to TDM flow
Definition: This service identifies a flow inside MPR network, in which
E1 is transported, switched and terminated.
Application: Typical microwave 2G backhauling application, in which
E1s are terminated before entering into aggregation network.
3JK Edition 2.0
1 2 30
2.1.2 TDM to ETH flow
Definition: E1 TDM input signals are packetized according to MEF8 standard;
E1s are transported, switched and provided to an external ETH network in
standard format (MEF-8).
Application:
a) Typical microwave 2G backhauling application, in which E1s are terminated before
entering into aggregation network, where aggregation network is a packet network.
E1s are not terminated at the end of the microwave backhauling and an end-to-end
circuit emulation services could be established between 9500 MPR and the service
router in front of BSC/RNC
b) 9500 MPR without ODU (MSS-8 or MSS-4 stand alone) provides the same level of
feature of a site aggregator box, grooming together different services (in this
particular case E1 TDM) into the common Ethernet layer
3JK Edition 2.0
1 2 31
2.1.3 SDH to SDH flow
Definition: This service identifies a flow inside MPR network, in which
STM-1 is transparently transported, switched and terminated.
Application: Typical microwave transport application.
3JK Edition 2.0
1 2 32
2.1.4 ETH to ETH flow
Definition: Ethernet traffic is transported and switched automatically
by the standard auto-learning algorithm of the built-in MPR 10 Gbit
Ethernet switch.
Application: Typical microwave 3G backhauling/WiMax application, in
which transport of Ethernet packets coming from basestations is
requested.
3JK Edition 2.0
1 2 33
2.1.5 ATM to ATM flow
Definition: 9500 MPR terminates the native IMA/ATM and performs
encapsulation/extraction of those ATM flows into/from ATM PW packets
according to RFC 4717. The 9500MPR facing the aggregation network,
the original ATM flows are re-built on ASAP board.
transport of Ethernet packets coming from 3G base station is
requested.
3JK Edition 2.0
1 2 34
2.1.6 ATM to ETH flow
Definition: 9500 MPR terminates the native IMA/ATM and ATM traffic,
encapsulated in Ethernet frames, is transported into IP/MPLS Core
Network.
transport of Ethernet packets coming from 3G base station is requested.
3JK Edition 2.0
1 2 35
2 Traffic Profiles
2.2 Traffic profiles
Six kinds of traffic profiles have been identified:
TDM2TDM ( 9500MPR 9500MPR, internal TDM )
TDM2Eth ( 9500MPR TDM to Ethernet )
SDH2SDH ( 9500 MPR-E 9500 MPR-E, internal to the MPR network )
ATM2ATM ( 9500MPR 9500MPR, internal ATM )
ATM2Eth ( 9500MPR ATM to Ethernet )
DATA ( Ethernet to Ethernet )
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
ATM2ATM and ATM2ETH profiles are managed in compliancy with the RFC 4717 (IETF ATM PWE3 -Pseudo
Wire Edge to Edge Emulation) standard.
3JK Edition 2.0
1 2 36
2 Traffic Profiles
2.2 Traffic profiles [cont.]
Cases 1, 2, 3
Case 1 for E1
The E1 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-E
network. The Circuit Emulation Service is TDM2TDM in Node 1 and Node 2. The Cross connections to be
implemented are PDH-Radio type.
Case 1 for STM-1
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-E
network. The Circuit Emulation Service is SDH2SDH in Node 1 and Node 2. The Cross connections to be
implemented are SDH-Radio type.
Case 2
The E1 stream is inserted in Node 1 and extracted in Node 2. One IWF is inside the 9500 MPR-E, but 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 to be implemented are PDH-Radio type in Node 1 and Radio-Eth
type in Node 2.
Case 3
The E1 stream is inserted/extracted in Node 1. One IWF is inside the 9500 MPR-E, but 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 to be implemented are PDH-Eth type in Node 1.
3JK Edition 2.0
1 2 37
2 Traffic Profiles
2.2 Traffic profiles [cont.]
Cases 4, 5
Cases 4 and 5
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-E 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-E Ethernet switch.
3JK Edition 2.0
1 2 38
2 Traffic Profiles
2.3 TDM2TDM
E1 traffic packetized only internally to 9500MPR equipment
E1
BSC
PDH
RADIO
RADIO
RADIO
BTS
E1
BTS
E1
BTS
E1
Flow Id present (user defined)
intermediate node configuration (E1 provisioning):
node by node (building Cross-connection tables based on Flow Id)
bandwidth guaranteed (according to QoS Highest Queue Priority association)
no flooding-autolearning necessary
3JK Edition 2.0
1 2 39
2 Traffic Profiles
2.3 TDM2TDM [cont.]
Both the IWFs belong to 9500MPR and the packets are not supposed to
exit the 9500 MPR network.
The IWF parameters listed above, have predetermined values and dont
need to be provisioned.
Mac addresses are determined as consequences of the cross connections.
Payload size is fixed to 121 bytes
ECID will be the same value as Flow Id
TDM clock source: clock recovery differential,
Flow Id provisioned by ECT/NMS
ECID = Emulated Circuit Identifier
IWF = Inter-Working Function
3JK Edition 2.0
1 2 40
2 Traffic Profiles
2.4 TDM2Eth
E1 traffic both internal and external to 9500MPR equipment
E1
BSC
E1 Eth
Eth
PSN
BTS
BTS
BTS
E1
E1
all the parameters must be configured compliant with the MEF8 standard
adaptive or differential clock recovery supported
bandwidth guaranteed (according to QoS Highest Queue Priority association)
destination MAC added before going into whole network (MEF8 compliant)
3JK Edition 2.0
1 2 41
2 Traffic Profiles
2.4 TDM2Eth [cont.]
Only one of the IWFs belongs to 9500MPR and the packets are supposed
to exit the 9500MPR network.
MAC addresses: in all involved nodes are determined as consequences of the
cross connections; the only exception is the Ethernet Terminal Node (the
node where the TDM2ETH traffic goes through an user Ethernet port). In
such ETN the source address is the node Mac address, the destination Mac
address will be provisioned by ECT/NMS.
Payload size: fixed to 256 bytes
ECID : provisioned by ECT/NMS, 2 different values may be used for each
direction
TDM clock source is provisioned by ECT/NMS: clock recovery adaptive, clock
recovery differential
Flow Id is provisioned by ECT/NMS (One Vlan is assigned to each bi-
directional circuit emulated E1 flow)
ECID = Emulated Circuit Identifier
3JK Edition 2.0
1 2 42
2 Traffic Profiles
2.5 SDH2SDH
STM-1 traffic packetized only internally to 9500 MPR-E equipment.
STM-1
STM-1
If there are intermediate nodes in each node build the Cross-connection tables based on Flow Id.
Bandwidth guaranteed (according to QoS Highest Queue Priority association)
No flooding-autolearning necessary
Both the IWFs belong to 9500 MPR-E and the packets are not supposed to exit the 9500 MPR-E network.
3JK Edition 2.0
1 2 43
2 Traffic Profiles
2.5 SDH2SDH [cont.]
The IWF parameters listed above, have predetermined values and dont
need to be provisioned.
Mac addresses are determined as consequences of the cross connections.
Payload size is fixed
ECID will be the same value as Flow Id
Clock source: clock recovery differential/node timing
Flow Id provisioned by ECT/NMS
3JK Edition 2.0
1 2 44
2 Traffic Profiles
2.6 ATM Traffic Management
Three Ethernet CoS are foreseen for ATM PW flows, derived from ATM
Service Category configured for the related VP/VC at ATM layer (by
ATM Traffic Descriptor):
CBR
UBR+ (MDCR > 0)
UBR
By proper mapping of these CoSs to Core Switch and Modem Switch
(refer to Figure 65.), the native ATM QoS can be emulated.
ATM PW flow-based packet queueing is performed inside the ASAP unit,
its Ethernet flow CIR/PIR/MBS/EBS parameters are also derived from
configured ATM TD.
ATM PW flows that have been classified as CBR and UBR+ will be
subjected to admission control and then have guaranteed bandwidth;
the required bandwidth will be derived from Ethernet flow CIR, taking
in account the ATM PW encapsulation and air frame structure.
3JK Edition 2.0
1 2 45
2 Traffic Profiles
2.6 ATM Traffic Management [cont.]
ATM Traffic Management - General block diagram
3JK Edition 2.0
1 2 46
2 Traffic Profiles
2.6 ATM Traffic Management [cont.]
Block diagram for ATM Ingress (ATM -> Packet) direction
In figure is shown a more detailed block diagram of the ASAP unit in Ingress.
3JK Edition 2.0
1 2 47
2 Traffic Profiles
2.7 ETH2ETH
None of the IWFs belongs to 9500MPR.
None of the parameters listed in the previous slide has to be configured
(the 9500 MPR is transparent).
Eth
Eth
RNC
Eth
Eth
WiMAX
(NodeB)
WiMAX
(NodeB)
WiMAX
(NodeB)
Eth
Eth
Eth
RNC
PSN
PSN
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.
3JK Edition 2.0
1 2 48
2 Traffic Profiles
2.8 Ethernet Traffic Management
Ethernet Traffic
The Ethernet traffic is all the traffic entered the MPR network from
user Ethernet ports.
By ECT/NMS it is possible to define the way to manage the Ethernet
traffic according to one of the following options:
802.1D (MAC Address bridge)
802.1Q (Virtual Bridge)
3JK Edition 2.0
1 2 49
2 Traffic Profiles
2.8 Ethernet Traffic Management [cont.]
In case of change of the bridge type from 802.1Q to 802.1D, the
content of the VLAN table and the VLAN assigned to the user Ethernet
ports, remains stored in the NE MIB.
To change the configuration from 802.1Dto 802.1Q, it is necessary to
configure all the Ethernet ports in Admit all mode to avoid hits on
the traffic on that specific port.
Bridge type change
3JK Edition 2.0
1 2 50
2 Traffic Profiles
2.8 Ethernet Traffic Management [cont.]
Reserved Multicast Addresses
Forward
CCM and LTM Group Destination MAC Addresses (IEEE
802.1ag)
01-80-C2-00-00-30 - 01-
80-C2-00-00-3F
Forward Reserved for GARP Application
01-80-C2-00-00-22 - 01-
80-C2-00-00-2F
Forward GVRP Address (IEEE 802.1Q) 01-80-C2-00-00-21
Forward GMRP Address (Clause 10 of IEEE 802.1D) 01-80-C2-00-00-20
Forward Reserved
01-80-C2-00-00-11 - 01-
80-C2-00-00-1F
Forward All LANs Bridge Management Group Address 01-80-C2-00-00-10
Discard Reserved for future standardization 01-80-C2-00-00-0F
Discard IEEE 802.1AB LLDP multicast address 01-80-C2-00-00-0E
Discard Reserved for future standardization
01-80-C2-00-00-04 - 01-
80-C2-00-00-0D
Discard IEEE 802.1X PAE address 01-80-C2-00-00-03
Discard
Clause 43 (Link Aggregation) and Clause 57 (OAM) of
IEEE 802.3
01-80-C2-00-00-02
Flow-Control enabled: Peer
Flow-Control disabled: Discard
Clause 31 (MAC Control) of IEEE 802.3 01-80-C2-00-00-01
MSS-8/MSS-4: Forward
MSS-1c: Discard
Bridge Group Address 01-80-C2-00-00-00
Action Function
Reserved Multicast
Address
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.
The actions taken by the system can be:
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.
3JK Edition 2.0
1 2 51
3 Traffic Management (QoS)
3JK Edition 2.0
1 2 52
3.1 Quality Of Services (QoS) in the MPR Node
MSS
Ethernet
Switch
Ethernet
Switch
MW ODU
Peripheral
MW ODU
Peripheral
T
D
M
P
e
r
i
p
h
e
r
a
l
T
D
M
P
e
r
i
p
h
e
r
a
l
E
m
b
e
d
d
e
d
E
T
H
i
n
t
e
r
f
a
c
e
s
E
m
b
e
d
d
e
d
E
T
H
i
n
t
e
r
f
a
c
e
s
MW ODU
Peripheral
MW ODU
Peripheral
The QoS function inside MPR is the result of a distributed implementation
on the Core Switch and on the Radio Interface
Radio Air Block
Scheduler
CAC
Core Packet
Scheduler
Connection
Admission
Control
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
3JK Edition 2.0
1 2 53
3.1.1 QoS in the Core-E
Traffic
Classification
(CoS)
802.1p bits
IPV4 DiffSerf
IPV6 Diffserv
VLAN-ID
Ethertype
MPLS Exp. bits
Queue #8
HPQ+CAC
DWRR
Scheduler
Queue #7
Queue #6
Queue #5
Queue #4
Queue #3
Queue #2
Queue #1
D
A
T
A

A
W
A
R
E

P
R
O
C
E
S
S
I
N
G
P
A
C
K
E
T

F
R
A
G
M
E
N
T
A
T
I
O
N
8 queues
Classifier
Slot 3
Slot 4
Slot 5
Slot 6
Slot 7
Slot 8
Slot 3
Slot 4
Slot 5
Slot 6
Slot 7
Slot 8
Ethernet User ports
(egress)
Ethernet User ports
(ingress)
U1 U2 U3 U4
U1 U2 U3 U4
Per egress port QoS
The figure shows an overview of the QoS implementation inside the switch.
The Quality of Service feature of the Ethernet switch provides eight internal queues per port to support
eight different traffic priorities. Typically the high-priority traffic experiences less delay than that low-
priority in the switch under congested conditions.
For each egress port according to method of QoS classification configured in the switch, the packets are
assigned to each queue. The higher priority queue Q8 is reserved for TDM flows; the remaining queues
are shared by all Ethernet flows according the classification mechanism configured by CT/NMS.
For generic Ethernet flows in the switch it is possible by CT/NMS to assign the priority to each packet
according to the information in:
1. IEEE std 802.1p: the packet is examined for the presence of a valid 802.1P user-priority tag. If the
tag is present the correspondent priority is assigned to the packet.
2. DiffServ: each packet is classified based on DSCP field in the IP header to determine the priority.
802.1P priority Queue
111, 110 Q5 (higher priority)
101 Q4
100 Q3
011, 000 Q2
010, 001 Q1

DiffServ priority Queue
111000, 110000, 101110, 101000 Q5 (higher priority)
100110, 100100, 100010, 100000 Q4
011110, 011100, 011010, 011000 Q3
010110, 010100, 010010, 010000
001110, 001100, 001010, 001000
000000
Q2
All remaining values Q1

3JK Edition 2.0
1 2 54
3.1.1 QoS in the Core-E [cont.]
Core-E Scheduler
The scheduler algorithm cannot be configured.
HQP scheduler algorithm is used on queues Q8, Q7 and Q6.
Deficit Weighted Round Robin (DWRR) is used on the other queues with
the following weights:
1 Q1
2 Q2
4 Q3
8 Q4
16 Q5 (higher priority)
WEIGHT QUEUE
3JK Edition 2.0
1 2 55
3.1.2 Radio Air Block QoS
The scheduler algorithm implemented inside the Radio Interface is High Queue
Pre-empt: when a packet arrives in the higher priority queue it is immediately
transmitted.
The Radio Air Block QoS is implemented by MPT itself (not in the MSS).
Switch Radio Interface
In the figure is shown an overview of the QoS implementation inside the Radio Interface module.
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 according to the information inside the
packet as 802.1P field, DiffServ field, Ethertype or 802.1Q VLAN_ID.
QoS based on IEEE std. 802.1p
When 802.1p QoS mechanism is adopted, the reference is the standard IEEE 802.1D-2004 Annex G User
priorities and traffic classes that defines 7 traffic types and the corresponding user priority values.
Considering that in the Radio Interface module for generic Ethernet traffic there are five egress queues
the mapping 802.1p value to queue is the following:
QoS based on DiffServ
802.1p priority Queue
101 Q4
100 Q3
011, 000 Q2
010, 001 Q1

100110, 100100, 100010, 100000 Q4
011110, 011100, 011010, 011000 Q3
010110, 010100, 010010, 010000
001010, 001100, 001010, 001000, 000000 Q2

3JK Edition 2.0
1 2 56
3.1.2 Radio Air Block QoS [cont.]
Radio Air Block Scheduler
HQP scheduler algorithm will be used on Q8, Q7 and Q6.
Deficit Weighted Round Robin (DWRR) algorithm will be used for the
other five queues.
By default, the DWRR algorithm is used with the following weights:
1 Q1
2 Q2
4 Q3
8 Q4
Weight Queue
3JK Edition 2.0
1 2 57
3.1.3 How 9500 MPR manage QoS
Eight Queues per Output Port
Classification
Voice -> MACDA+VLAN
ATM PWE3 -> MACDA+VLAN
TMN -> VLAN
ETHERNET
No priority -> all queue #1
1p
DiffServ
Ethernet based frame
#4
#3
#2
#1
#8
#7
#6
#5
HPQ
DWRR
ETHERNET
ETHERNET
ETHERNET
ATM UBR
ETHERNET
TDM
VoIP
TDM2ETH
ATM CBR, VBRrt
TMN
ATM VBRnrt, UBR+
ETHERNET
Schedul er
type
Servi ce type MPR QoS
L2 switch on Core unit
3JK Edition 2.0
58
1 2 58
Eight Queues per Radio Direction
Classification
Voice -> MACDA+VLAN
ATM PWE3 -> MACDA+VLAN
TMN -> VLAN
ETHERNET
No priority -> all queue #1
1p
DiffServ
Open platform ready for additional services
Air block base entities
Fragmentation
Fair scheduling (Jumbo)
#4
#3
#2
#1
#8
#7
#6
#5
HPQ
DWRR
ETHERNET
ETHERNET
ETHERNET
ATM UBR
ETHERNET
TDM
VoIP
TDM2ETH
ATM CBR, VBRrt
TMN
ATM VBRnrt, UBR+
ETHERNET
Schedul er
type
Servi ce type MPR QoS
Modem unit (Radio side)
3.1.3 How 9500 MPR manage QoS [cont.]
3JK Edition 2.0
1 2 59
3.1.4 Flows classification
For Radio Air Block QoS:
All TMN traffic flows are assigned to the Q6 egress priority queue.
For both Core-E QoS and Radio Air Block QoS:
All the TDM2TDM traffic flows will be assigned to the highest egress
priority queue (Q8).
All the TDM2ETH traffic flows will be assigned to the Q7 egress priority
queue.
All the MEF-8 ETH2ETH traffic flows will be assigned to the Q5 egress
priority queue.
3JK Edition 2.0
1 2 60
For generic Ethernet flows in the switch and the modem it is possible by
CT/NMS to assign the priority to each packet according to the information in:
IEEE 802.1p: the packet is examined for the presence of a valid 802.1P user-
priority tag. If the tag is present the correspondent priority is assigned to the
packet.
DiffServ: each packet is classified based on DSCP field in the IP header to
determine the priority.
3.1.4 Flows classification [cont.]
Q1 010, 001
Q2 011, 000
Q3 100
Q4 101
Q5 (higher priority) 111, 110
Queue 802.1P priority
Q1 All remaining values
Q2 010110, 010100, 010010, 010000
001110, 001100, 001010, 001000
000000
Q3 011110, 011100, 011010, 011000
Q4 100110, 100100, 100010, 100000
Q5 (higher priority) 111000, 110000, 101110, 101000
Queue DiffServ priority
When 802.1p QoS mechanism is adopted,
the reference is the standard IEEE 802.1D-2004 Annex G User priorities and traffic classes that defines 7
traffic types and the corresponding user priority values.
3JK Edition 2.0
1 2 61
ATM PW flows will be assigned to Ethernet switch and modem egress
priority queues according to their CoS , as below reported:
Q1 BackGround (UBR)
Q6 Best Effort (UBR+)
Q7 (higher priority) Guaranteed (CBR)
Switch Egress Queue ATM PW CoS
3JK Edition 2.0
1 2 62
Jumbo frames:
While there is no physical limitation to the number of ports that can
receive jumbo frame,
if more jumbo flows are transmitted toward the same port into two
different queues the QoS could work in wrong way.
It is recommended to forward jumbo frame only in the queue Q1 (lower
priority).
3JK Edition 2.0
1 2 63
3.2 Quality Of Services (QoS) in the MPR Terminal
The QoS function inside MPR is the result of a distributed implementation
on the MSS-1c Switch and on the MPT
MSS-1c
Ethernet
Switch
Ethernet
Switch
T
D
M
I
n
t
e
r
f
a
c
e
s
T
D
M
I
n
t
e
r
f
a
c
e
s
E
m
b
e
d
d
e
d
E
T
H
i
n
t
e
r
f
a
c
e
s
E
m
b
e
d
d
e
d
E
T
H
i
n
t
e
r
f
a
c
e
s
Radio
Interface
Radio
Interface
Radio Air Block
Scheduler
CAC
Core Packet
Scheduler
Connection
Admission
Control
MPT
9500MPR uses a Connection Admission Control (CAC) for committed services and two schedulers in series (on MSS-1c embedded
L2 switch and on MPT)
The two schedulers need to jointly interoperate to guarantee determistic behavior of the services
3JK Edition 2.0
1 2 64
3.2.1 QoS in the MSS-1c
Traffic
Classification
(CoS)
802.1p bits
IPV4 DiffSerf
IPV6 Diffserv
VLAN-ID
Ethertype
MPLS Exp. bits
HPQ+CAC
DWRR
Scheduler
Queue #4
Queue #3
Queue #2
Queue #1
D
A
T
A

A
W
A
R
E

P
R
O
C
E
S
S
I
N
G
P
A
C
K
E
T

F
R
A
G
M
E
N
T
A
T
I
O
N
4 queues
Classifier
Per egress port QoS
U1 U2 U3 U4
TMN1 TMN2 CT
10E1
The figure shows an overview of the QoS implementation inside the switch.
The Quality of Service feature of the Ethernet switch provides four internal queues per port to support
four different traffic priorities. Typically the high-priority traffic experiences less delay than that low-
priority in the switch under congested conditions.
For each egress port according to method of QoS classification configured in the switch, the packets are
assigned to each queue. The higher priority queue Q4 is reserved for TDM flows; the remaining queues
are shared by all Ethernet flows according the classification mechanism configured by CT/NMS.
For generic Ethernet flows in the switch it is possible by CT/NMS to assign the priority to each packet
according to the information in:
1. IEEE std 802.1p: the packet is examined for the presence of a valid 802.1P user-priority tag. If the
tag is present the correspondent priority is assigned to the packet.
2. DiffServ: each packet is classified based on DSCP field in the IP header to determine the priority.
802.1P priority Queue
101 Q4
100 Q3
011, 000 Q2
010, 001 Q1

100110, 100100, 100010, 100000 Q4
011110, 011100, 011010, 011000 Q3
010110, 010100, 010010, 010000
001110, 001100, 001010, 001000
000000
Q2

3JK Edition 2.0
1 2 65
3.2.1 QoS in the MSS-1c [cont.]
MSS-1c Scheduler
The scheduler algorithm cannot be configured.
HQP scheduler algorithm is used on queues Q4.
Deficit Weighted Round Robin (DWRR) is used on the other queues with
the following weights:
1 Q1
2 Q2
WEIGHT QUEUE
3JK Edition 2.0
1 2 66
All the TDM traffic flows will be assigned to the highest egress priority queue
(Q4)
For generic Ethernet flows in the switch it is possible by CT/NMS to assign the
priority to each packet according to the information in:
IEEE 802.1p: the packet is examined for the presence of a valid 802.1P user-
priority tag. If the tag is present the correspondent priority is assigned to the
packet.
DiffServ: each packet is classified based on DSCP field in the IP header to
determine the priority.
3.2.2 Flows classification
Q1 011, 010, 001, 000
Q2 101, 100
Q3 (higher priority) 111, 110
Queue 802.1P priority
Q1 All remaining values
Q2 100110, 100100, 100010, 100000
011110, 011100, 011010, 011000
Q3 (higher priority) 111000, 110000, 101110, 101000
Queue DiffServ priority
When 802.1p QoS mechanism is adopted,
the reference is the standard IEEE 802.1D-2004 Annex G User priorities and traffic classes that defines 7
traffic types and the corresponding user priority values.
3JK Edition 2.0
1 2 67
Jumbo frames:
While there is no physical limitation to the number of ports that can
receive jumbo frame,
if more jumbo flows are transmitted toward the same port into two
different queues the QoS could work in wrong way.
It is recommended to forward jumbo frame only in the queue Q1 (lower
priority).
3JK Edition 2.0
1 2 68
3.3 Quality Of Services (QoS) in the MPT
The Radio QoS is implemented by
MPT itself (not in the MPT Access unit and not inside the MSS-1c).
The set of MPT Radio QoS features is the same of the one specified for
the Modem unit with the exception of:
the ATM CBR and UBR+ CoS:
in MPT they are sent to queue #5 and queue #4 respectively
(and not to queue #7 and queue #6).
3JK Edition 2.0
1 2 69
3.3.1 Radio Air Block QoS for MPR Node
The scheduler algorithm implemented inside the MPT is High Queue Pre-empt:
when a packet arrives in the higher priority queue it is immediately
transmitted.
In the figure is shown an overview of the QoS implementation inside the MPT.
Considering that in the MPT for generic Ethernet traffic there are five egress queues the mapping
802.1p value to queue is the following:
101 Q4
100 Q3
011, 000 Q2
010, 001 Q1

100110, 100100, 100010, 100000 Q4
011110, 011100, 011010, 011000 Q3
010110, 010100, 010010, 010000
001010, 001100, 001010, 001000, 000000 Q2

3JK Edition 2.0
1 2 70
3.3.2 Radio Air Block QoS for MPR Terminal
transmitted.
In the figure is shown an overview of the QoS implementation inside the MPT.
101 Q4
100 Q3
011, 000 Q2
010, 001 Q1

100110, 100100, 100010, 100000 Q4
011110, 011100, 011010, 011000 Q3
010110, 010100, 010010, 010000
001010, 001100, 001010, 001000, 000000 Q2

3JK Edition 2.0
1 2 71
3.3.3 Radio Air Block QoS Scheduler
Deficit Weighted Round Robin (DWRR) algorithm will be used for the
other five queues.
1 Q1
2 Q2
4 Q3
8 Q4
Weight Queue
3JK Edition 2.0
1 2 72
3.4 Quality Of Services (QoS) in the MPR-e
transmitted.
In the figure is shown an overview of the QoS implementation inside the MPR-e.
101 Q4
100 Q3
011, 000 Q2
010, 001 Q1

100110, 100100, 100010, 100000 Q4
011110, 011100, 011010, 011000 Q3
010110, 010100, 010010, 010000
001010, 001100, 001010, 001000, 000000 Q2

3JK Edition 2.0
1 2 73
3.4 Quality Of Services (QoS) in the MPR-e [cont.]
For the other 5 queues can be selected, by the MCT, the HQP mode or
the DWRR (Deficit Weighted Round Robin) mode.
If the DWRR has been selected, the weight to be assigned to each
queue can be configured by the MCT.
1 Q1
2 Q2
4 Q3
8 Q4
Weight Queue
3JK Edition 2.0
1 2 74
Blank Page
3JK Edition 2.0
1 2 75
4 LAG (Link Aggregation Group)
3JK Edition 2.0
1 2 76
4 LAG (Link Aggregation Group)
4.1 LAG overview
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.
3JK Edition 2.0
1 2 77
4.1 LAG overview
4.1.1 Link aggregation on Radio ports (Radio LAG)
Link aggregation can be applied to radio ports (in this case it is named
Radio Link Aggregation).
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.
3JK Edition 2.0
1 2 78
4.1 LAG overview
4.1.1 Link aggregation on Radio ports (Radio LAG) [cont.]
One MPT per MPT plug-in.
3JK Edition 2.0
1 2 79
4.1 LAG overview
4.1.2 Link aggregation on User Ethernet ports (Ethernet LAG)
Link aggregation can be applied to Ethernet user ports (electrical or
optical ) on the same Core-E unit.
The LACP protocol is supported.
Note 1: the Ethernet ports involved in a LAG cannot be used as TMN In-band interface.
3JK Edition 2.0
1 2 80
Blank Page
3JK Edition 2.0
1 2 81
5 Synchronisation
3JK Edition 2.0
1 2 82
5 Synchronisation
5.1 Synchronisation
Packet microwave
nodal configuration
9500 MPR
Line clock
(ACR/DCR, NTP)*

E1/T1
SvncE Eth
Synch in/out
ports
(external source)
2 MHz
5 MHz
10MHz
9500 MPR
9500 MPR
9500 MPR
Line clock
E1/T1
SyncE
Eth
Synch in/out
ports
(external source)
2 MHz
5 MHz
10 MHz
Synchronisation transferred through radio carrier at physical layer
Given Sync Source, 9500 MPR can deliver synchronization at the far end under any format
Any Sync IN, any Sync OUT
*Adaptive and differential clock
recovery, node timing protocol
1588v2
TOD
Transparent
transport of
protocol
1588v2
TOD
Transparent
transport of
protocol
Synch delivery
options
Synch source
options
Time source
options
Time delivery
options
Access type
Mobile
2G,3G,4G
Fixed
Private
Business
Office
Phone
DSL
MSS-8 and MSS-4
3JK Edition 2.0
1 2 83
5 Synchronisation
5.1 Synchronisation [cont.]
Synchronization Status Messages and Quality Level Determination
Compliant to G.8264
SSM can be applied to Ethernet user port or to radios
When SSM are applied to radios, the radio direction with best synchronization
quality is selected.
9500MPR inserted in a ring delivers the synchronizations taken from the best
of West or East radio
9500MPR can be positioned inside a microwave ring (where traffic
management is done by an external gear).
MSS-8 and MSS-4
Radio 1
Reference
selector
Quality
Level (QL)
Quality
Level (QL)
Quality Level
Radio 2
9500MPR synchro delivery:
1. synchE
2. E1/DS1
3. 2/5/10 MHz
Determine and select the
highest quality source
Note: With MSS-1c and with MPR-e the SSM are transparency forwarded in most of the configurations.
3JK Edition 2.0
1 2 84
5 Synchronisation
Packet microwave
nodal configuration
9500 MPR
Line clock
(ACR/DCR, NTP)*

E1/T1
SvncE Eth
9500 MPR
9500 MPR
9500 MPR
Line clock
E1/T1
SyncE
Eth
1588v2
TOD
Transparent
transport of
protocol
1588v
2 TOD
Transparent
transport of
protocol
Synch delivery
options
Synch source
options
Time source
options
Time delivery
options
Access type
Mobile
2G,3G,4G
Fixed
Private
Business
Office
Phone
DSL
MSS-1c
3JK Edition 2.0
1 2 85
5 Synchronisation
Packet microwave
nodal configuration
9500 MPR
SvncE Eth
9500 MPR
9500 MPR
9500 MPR
SyncE
Eth
1588v2
TOD
Transparent
transport of
protocol
1588v
2 TOD
Transparent
transport of
protocol
Synch delivery
options
Synch source
options
Time source
options
Time delivery
options
Access type
Mobile
2G,3G,4G
Fixed
Private
Business
Office
Phone
DSL
MPR-e
3JK Edition 2.0
1 2 86
5 Synchronisation
Network Synchronisation in Mobile Backhauling
On the radio channel, a 9500 MPR transfers the reference clock to an adjacent MPR device through the
radio carrier frequency at physical layer.
This method offers two main advantages:
No bandwith is consumed for the synchronisation distribution,
Total immunity to the network load.
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.
3JK Edition 2.0
1 2 87
5 Synchronisation
Network Clock Available
Differential Clock Recovery
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.
3JK Edition 2.0
1 2 88
5 Synchronisation
5.2 Clock Source Selection and Distribution
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).
3JK Edition 2.0
1 2 89
5 Synchronisation
5.3 Differential/Adaptative clock recovery
TDM data flow is fragmented and the fragments are transmitted over a
Packet Switched Network (PSN).
The received fragments need to be reassembled in the original TDM
data flow at the original bit rate.
Two main methods can be used to recover at the RX site, the original
bit rate:
Differential clock recovery with or without the Node Timing: recalculation
of the original clock based of the Delta respect to a reference clock that is
available at both Tx and Rx site (Differential: used in case of clock
distribution on the whole network. Its more reliable than Adaptive; also used
in TDM2TDM/SDH2SDH traffic (MPR to MPR)). This method can be selected for
each E1/STM-1 stream.
Adaptive clock recovery with or without the Node Timing: based on the
average rate at which the packets (fragments) arrive at RX site (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). This method can be selected for each E1
stream.
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).
Recovered E1 clock is according to G. 823 synchronization masks.
3JK Edition 2.0
1 2 90
5 Synchronisation
5.3 Differential/Adaptative clock recovery [cont.]
The available clock recovery techniques with TDM2TDM profile are:
DCR: differential clock recovery
Node timing
The available clock recovery techniques with TDM2ETH profile are:
ACR: adaptive clock recovery (if a common reference clock is not available)
DCR: differential clock recovery
Node timing
Note: in meshed networks (rings) do not close the synchronisation configuration.
N.B.: 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.
3JK Edition 2.0
1 2 91
5 Synchronisation
5.3 Differential/Adaptative clock recovery [cont.]
End
System1 IWF
IWF
End
System2
PSN
PSN
End
System1 IWF
IWF
End
System2
PSN
PSN
Adaptative clock recovery
Differential clock recovery
Differential clock recovery
Common reference clock IS available at both Ends.
IWF system, at RX side, generate output clock based on RTP TimeStamps which are sent together with
each Fragments.
Adaptative clock recovery
Common reference clock is NOT available at both Ends.
IWF system, at RX side, generate output clock based on data arrival rate: TDM clock is slowly adjusted to
maintain the average fill level of a jitter buffer at its midpoint.
3JK Edition 2.0
1 2 92
5 Synchronisation
5.4 Synchronisation Interface
Each Network Element must have a reference clock (NEC), which will
be distributed to each circuit of the NE. Such clock is a 25 MHz
generated in the Clock Reference Unit (CRU) function.
The NEC is locked to a Synchronization Source.
Both for all MSS and MPR-e, the sources can be:
1. Free Run Local Oscillator.
2. Any E1 available at input traffic interfaces (the specific E1 port has to be
chosen). No E1 coming from the ASAP card can be used as Synch source.
3JK Edition 2.0
1 2 93
5 Synchronisation
5.5 Synchronisation Interface
3. SynchrE: Any Synchronous Ethernet clock source available at enabled User
Ethernet traffic interfaces (both electrical and optical) configured in
synchronous operation mode (the specific User Ethernet port has to be
chosen).
From ITU-T G.8264 point of view, the MSS is a Synchronous Ethernet equipment
equipped with a system clock (NEC) following the ITU-T G.8262 recommendation.
A User Ethernet interface configured in synchronous operation mode can work only
at 1Gigabit/s.
In the particular case of electrical User Ethernet interfaces, these interfaces
perform link auto negotiation to determine the master and slave clocks for the link.
The clock slave role must be configured as part of auto negotiation parameters in
order to use the interface as Synchronous Ethernet clock source.
N.B.: SSM is not supported, therefore MPR cannot be included in a Synch-E ring.
4. The Symbol Rate of the Rx signal of any available Radio direction (the
specific Radio Port has to be chosen).
3JK Edition 2.0
1 2 94
5 Synchronisation
5.5 Synchronisation Interface [cont.]
The NEC also provides a Sync Out port on the Core-E Module.
The other sources can be:
5. A specific synchronization signal available from the dedicated Sync-In port,
which can be configured according to the following options:
2.048 MHz, electrical levels according G.703, clause 13
5 MHz, + 6 dBm 50 ohm, sine-wave
10 MHz, + 6 dBm 50 ohm, sine-wave
1.024 MHz, electrical levels according to G.703, clause 13 with the following
exceptions:
timing properly scaled from 2.048 MHz to 1.024 MHz.
For only MSS-8 and MSS-4
3JK Edition 2.0
1 2 95
5 Synchronisation
Some rules have to be followed while configuring the Primary and
Secondary clock sources.
All the NEC has to be configured as Master or Slave.
Only one Master is allowed in the network.
If Master,
The Restoration Mode can be Revertive and Not Revertive
The Primary sources must be chosen among 1), 2), 3) or 5).
If the selected Master Primary Source is 1)
then the Master Secondary Source doesn't need to be selected because the Primary is never
supposed to fail.
If the selected Master Primary Source is 2), 3) or 5)
then Master Secondary Source must be selected among 1), 2), 3) or 5).
If Slave,
The Restoration Mode is fixed to Revertive.
The Primary Source must chosen between 3), 4) or 5)
Slave primary sources is allowed to be 3) or 5)
The Secondary Source can be chosen among 1), 2), 3) or 5).
Each Module will mute its own Synchronization clock in case of Fail Alarm.
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.
The Signal Degrade Alarm relevant to the selected Synchronization Source, or the relevant Card Fail, causes
the switching of the Synchronization Source.
3JK Edition 2.0
1 2 96
5 Synchronisation
The synchronization of each E1 ATM port in the ASAP unit can be
configured (by the Craft Terminal) in two ways:
Loop-timed: the transmit clock is derived from the E1 clock source received
Node-timed: the transmit clock is the NE clock
The E1 ports belonging to the same IMA group must have the same
configuration.
Synchronization for E1 ports with ASAP unit
3JK Edition 2.0
1 2 97
5 Synchronisation
5.6 Synchronisation Interface in MPR-e
The MPT can be configured to be synchronized in two different modes:
SynchE (Synchronous Ethernet).
With this mode for the electrical interface the selection among
Autonegotiation/Master/Slave must be performed.
PCR (Proprietary Clock Recovery): the time stamp inside the Ethernet
frame is used.
With this mode the Source MAC address and the Destination MAC address
must be assigned.
Only for MPT in stand-alone
3JK Edition 2.0
1 2 98
6 Cross-connections
3JK Edition 2.0
1 2 99
6 Cross-connections
6.1 Cross-connection
Making any-service cross connections is as simple as drawing a row
By TCO or by NM
CORE-E
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.
3JK Edition 2.0
1 2 100
6 Cross-connections
6.1 Cross-connection [cont.]
Making any-service cross connections is as simple as drawing a row
By TCO or by NM
E1 Service
Ethernet
Service
TDM2ETH
MEF8
Service
MSS-1c
STM-1 Service
The cross-connections are realized with a Layer-2 Ethernet Switch inside the MSS-1c.
The decision made by the switch to forward the received packet is based on the destination MAC address
3JK Edition 2.0
1 2 101
6 Cross-connections
6.2 E1 Cross-connection
Each E1 can be cross connected independently
E1 can be cross connected to any of the following interfaces:
Radio interface
Ethernet interface
Each E1 (board #, port #) must be associated to a signal flow ID
3JK Edition 2.0
1 2 102
6 Cross-connections
6.3 STM-1 Cross-connections
Each STM-1 can be cross connected independently
STM-1 can be cross connected to the following interface:
Radio interface
Each STM-1 (board #, port #) must be associated to an unique signal flow ID
3JK Edition 2.0
1 2 103
6 Cross-connections
6.4 Radio-Radio Cross-connection
Ethernet frames, coming from a radio direction, can be cross-
connected to another radio direction.
3JK Edition 2.0
1 2 104
6 Cross-connections
6.5 Ethernet Cross-connection
All flows different from the TDM2TDM and TDM2ETH ones are managed
as the standard Ethernet packets: if the 802.1Q is enabled the related
management is performed looking the VLAN and then, according to the
destination address, each packet is switched to the correct port: radio,
user Ethernet or E1/DS1. If the 802.1Q is not enabled only the
destination address is considered.
For each radio interface, the bandwidth assigned, globally, to the
Ethernet traffic is the consequence, with a given radio capacity, of the
number of E1/DS1 cross-connected on that radio interface. Hence the
available bandwidth for Ethernet flows will be the configured radio
bandwidth decreased by bandwidth used by each TDM2TDM and
TDM2ETH.
3JK Edition 2.0
1 2 105
6 Cross-connections
6.6 ATM PW Cross-connection
Cross-connection of ATM PW flows involves the following levels of
operation:
an ATM PW is composed of two unidirectional flows, so its cross-connection is
internally managed by NE as two unidirectional flow cross-connections
for ATM PW flow with guaranteed bandwidth, an admission control check
must be performed in each flow direction: there shall be enough available
bandwidth on both directions
VLAN-based settings in terms of Ethernet switch and Radio QoS are then
performed (as the same VLAN can be used for ATM PW flows with same CoS
and path).
The minimum bandwidth foreseen for an ATM PW flow corresponds to the
case of PCR, SCR or MDCR of 1 cell/s rate, with max 1 cell for frame.
3JK Edition 2.0
1 2 106
6 Cross-connections
6.7 ATM Light Cross-connection Provisioning
In this release when a cross-connection toward a radio direction with
MPT is involved, the related provisioning is performed in almost the
same way as with ODU300, with the following main differences:
MAC DA is also explicitly provisioned in the NE acting as TPE role
admission control, in terms of checking bandwidth required bt ATM PW flow
against the available bandwidth on radio interface, is never performed
3JK Edition 2.0
1 2 107
6 Cross-connections
6.8 MAC SA of ATM PW Generated by ASAP Unit
MAC Source Address of ATM PW frames generated by ASAP peripheral
should be assigned to be equal to:
the internal MAC Address of slot hosting that ASAP peripheral in case of cross-
connection towards radio interface
the NE Mac Address in case of cross-connection towards Ethernet interface.
In this release it is accepted to assign always the NE Mac Address as
MAC Source Address of ATM PW frames generated by ASAP peripheral.
3JK Edition 2.0
1 2 108
Blank Page
3JK Edition 2.0
1 2 109
7 Protections with ODU300
3JK Edition 2.0
1 2 110
7.1 Protections with ODU300
Supported Protection types :
1) RPS (Radio Protection Switching) Hitless for each radio direction (RPS-RX)
RPS is distributed in 9500 MSS modules before termination of 9500 MSS frame.
2) EPS (Equipment Protection Switching) for each module type
Both Working and Spare modules send its own signal to the Core-E.
Core-E selects the best signal.
3) HSB-TPS (Hot StandBy - Transmission Protection Switch)
Spare ODU module is squelched.
3JK Edition 2.0
1 2 111
7.1 Protections with ODU300 [cont.]
1
2
2
3
2
Legend:
1 RPS
2 EPS
3 HSB
3JK Edition 2.0
1 2 112
7.1 Protections with ODU300 [cont.]
2
2
Legend:
2 EPS
3JK Edition 2.0
1 2 113
7.2 RPS Switching Criteria
The switching criteria are:
SF (Signal Fail): generated from transmission and equipment alarms affecting the Rx
radio section:
Rx Fail
Demodulator Fail
IDU-ODU cable loss
LOF of aggregate signal radio side
Main and spare ODU, IDU HW failures (card fail)
HBER (high BER)
EW (Early Warning)
3JK Edition 2.0
1 2 114
7.3 EPS Switching Criteria
Peripheral Card Fail (switching off of the peripheral included)
Peripheral Card Missing
LOS of all the tributaries (of course only in case of PDH local access peripheral
protection) managed via SW.
3JK Edition 2.0
1 2 115
7.4 HSB Switching Criteria
The switching criteria are :
Radio Interface Peripheral Card Fail (switching off of the peripheral included)
Radio Interface Peripheral Card Missing
MSS-ODU cable loss
ODU TX chain alarm (this is an OR of the following alarms: LOS at ODU input,
modFail, txFail, ODU card fail)
3JK Edition 2.0
1 2 116
Blank Page
3JK Edition 2.0
1 2 117
8 Protections with MPT-HC/MPT-HC V2
3JK Edition 2.0
1 2 118
8.1 Protections with MPT-HC/MPT-HC V2
To implement the 1+1 configuration an optical cable must be connected
from one MPT-HC/MPT-HC V2 to the second MPT-HC/MPT-HC V2. In the
figure Ethernet port 2 of one MPT-HC/MPT-HC V2 is connected to
Ethernet port 2 of the second MPT-HC/MPT-HC V2.
Supported Protection types:
1) RPS (Radio Protection Switching) Hitless for each radio direction
RPS is implemented directly on the two MPT-HC/MPT-HC V2.
2) EPS (Equipment Protection Switching) for the MPT-HC/MPT-HC V2
EPS protects the MPT-HC/MPT-HC V2 and the cables connecting it to the MSS.
3JK Edition 2.0
1 2 119
8.1 Protections with MPT-HC/MPT-HC V2 [cont.]
1
2 3
2
2
2
Legend:
1 RPS
2 EPS
3 HSB
3JK Edition 2.0
1 2 120
8.1 Protections with MPT-HC/MPT-HC V2 [cont.]
2
2
3JK Edition 2.0
1 2 121
SF (Signal Fail): generated from transmission and equipment alarms affecting
the Rx radio section
Rx Fail
Demodulator Fail
inter-MPT coupling link failure
HBER (high BER) based on the demodulated erroneous blocks ratio
EW (Early Warning) based on MSE
Moreover, MPT-HC 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.
3JK Edition 2.0
1 2 122
MPT Access Card Fail status
IDU-ODU Connection Failure
ICP alarm
Mated MPT Access card Failure
3JK Edition 2.0
1 2 123
ICP alarm
Incompatible Shifter alarm
Incompatible Frequency alarm
Incompatible Power alarm
Incompatible Modulation Parameters alarm
Inter-MPT coupling link failure. 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.
3JK Edition 2.0
1 2 124
Blank Page
3JK Edition 2.0
1 2 125
9 XPIC (with MPT-HC V2 only)
3JK Edition 2.0
1 2 126
9.1 XPIC (with MPT-HC V2 only)
The MPT-HC V2 supports Co-channel Dual Polarized (CCDP) operation
using a built-in Cross-polarized Interference Cancellation (XPIC)
function (this function is implemented by installing the RPS+XPIC
external module). Two links are operated on the same radio channel,
with one using the vertical polarization, the other the horizontal. XPIC
typically provides 20 dB improvement in polarization discrimination.
The actual improvement will then depend on the native discrimination
provided at antenna alignment, and any reduction of this discrimination
caused by atmospheric effects (fading).
XPIC working mode supports modulation scheme 128 QAM and 256 QAM
with channel spacing 28 MHz or 56 MHz.
Adaptive Modulation and ATPC are not supported with the XPIC
function.
Radio configuration supported:
Single 2+0 XPIC
Double 1+1 HSB co-channel XPIC
3JK Edition 2.0
1 2 127
9.1 XPIC (with MPT-HC V2 only) [cont.]
3JK Edition 2.0
1 2 128
9.1 XPIC (with MPT-HC V2 only) [cont.]
3JK Edition 2.0
1 2 129
10 Protection with MPT-MC
3JK Edition 2.0
1 2 130
10.1 Protection with MPT-MC
Supported Protection types:
1) RPS (Radio Protection Switching) Hitless for each radio direction
RPS is implemented by the virtual cable (No physical interconnection cable must
be installed between the MPT-MC. The 1+1 messages are exchanged inside the MSS-
4/MSS-8.
2) EPS (Equipment Protection Switching) for the MPT-MC
EPS protects the MPT-MC and the cables connecting it to the MSS.
3JK Edition 2.0
1 2 131
10.1 Protection with MPT-MC [cont.]
Note: Since there is no coupling link in the current release the TPS Operator Commands are not supported.
Only Operator Commands for EPS are supported.
3JK Edition 2.0
1 2 132
SF (Signal Fail): generated from transmission and equipment alarms affecting
the Rx radio section
Rx Fail
Demodulator Fail
inter-MPT coupling link failure
HBER (high BER) based on the demodulated erroneous blocks ratio
EW (Early Warning) based on MSE
Moreover, 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. 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.
3JK Edition 2.0
1 2 133
ICP alarm
3JK Edition 2.0
1 2 134
ICP alarm
Incompatible Shifter alarm
Incompatible Frequency alarm
Incompatible Power alarm
Incompatible Modulation Parameters alarm
3JK Edition 2.0
1 2 135
11 Core-E protection
3JK Edition 2.0
1 2 136
11.1 Core-E protection
The logic of this protection is distributed in each access and radio
peripheral unit. All the switching criteria coming from both the Core
units, are available (via backpanel) to each peripheral in order to allow
to each logic to take the same decision.
Both the Cores (main and spare) send their signals to all the traffic
peripherals.
Core protection supports two different types of protection:
Traffic/services protection (protection of all the transport functions with the
exception of the control platform)
Control Platform protection
In order to provide this protection the Flash Cards on the two Core
boards are kept aligned (in terms of SW and configuration data) both in
case of new operations done by the management systems and in case of
Flash Card replacement.
3JK Edition 2.0
1 2 137
11.1 Core-E protection [cont.]
User Ethernet interfaces protection
In order to support User Ethernet interfaces protection using an
external device, the User Ethernet ports of the Core in standby status
are switched off.
The switch on of the User Ethernet interfaces when the Core in standby
status becomes active, due to operator commands or automatic switch,
is done within 5 seconds. In case of Optical Ethernet interface, the
Lambda, Link Length, Connector and Gigabit Ethernet Compliance Code
information are read from the active Core.
3JK Edition 2.0
1 2 138
TMN Local Ethernet interface protection
In order to support TMN Local Ethernet interface protection using an
external device, the relevant Ethernet port of the Core in standby
status is switched off.
The switch on of the TMN Local Ethernet interface when the Core in
standby status becomes active, due to operator commands or
automatic switch, is done within 5 seconds.
In order to avoid impact on the Core, the external device used for the
TMN Local Ethernet interface protection is kept separate from the one
used for protection of User Ethernet interface. External synchronization
interface protection
3JK Edition 2.0
1 2 139
External synchronization interface protection
The Protection of the external synchronization interface is supported.
The output port on the stand-by Core is muted.
Node-Timed PDH interface protection
In case of node-timed PDH interface the protection of the NE Clock
provided by Core is supported.
Core protection restoration mode
The restoration mode is always revertive: the Core main becomes
active as soon as it has recovered from failure or when a switch
command is released.
3JK Edition 2.0
1 2 140
11.2 Core-E protection Switching Criteria
Core Card Fail
Core Card Missing
Control Platform operational status failure
Flash Card realignment in progress
Flash Card failure
If the Ethernet LOS Criteria feature has been enabled the following
additional switching criteria are added:
Card Fail of SFP optical module
Card Missing of SFP optical module
LOS of any Electrical User Ethernet interfaces, including the LOS of the forth
User Ethernet interface working as TMN Local Ethernet interface.
Note: In case of stand-by Flash Card realignment in progress, the application SW refuses/removes a manual
switch command.
3JK Edition 2.0
1 2 141
12 Ring Protection
3JK Edition 2.0
1 2 142
12 Ring Protection
12.1 ERPS operation
The protection switching mechanism is based on the Automatic
Protection Switching protocol for Ethernet ring topologies (called R-
APS). This protocol is used to coordinate the protection actions over
the ring.
The fundamentals of this ring protection switching architecture are:
principle of loop avoidance.
utilization of learning, forwarding, and address table mechanisms defined in
the Ethernet flow forwarding function.
The loop avoidance in the ring is achieved by guaranteeing that, at any
time, traffic may flow on all but one of the ring links. This particular
link is called the Ring Protection Link (RPL).
Under normal conditions this link is blocked, i.e., not used for traffic.
One designated node, the RPL Owner, is responsible to block traffic
over the RPL.
Under a ring failure condition, the RPL owner is responsible to unblock
the RPL, allowing the RPL to be used for traffic.
3JK Edition 2.0
1 2 143
12 Ring Protection
12.1 ERPS operation [cont.]
3JK Edition 2.0
1 2 144
12 Ring Protection
3JK Edition 2.0
1 2 145
12 Ring Protection
Two ERPS Control Processes are instantiated on each rings node. Each instance
selects its own RPL and RPL Owner.
The ERPS Control Process controls the forwarding function to perform the
following actions:
to disable forwarding over the set of VLANs assigned to the ERPS instance
corresponding to blocked ring links;
to flush the learned MAC address table.
Only revertive switching mechanism is supported.
The Wait-to-Restore is managed by the RPL Owner, it is configured by the
operator in 1 minute steps between 1 and 12 minutes. The default value is 5
minutes.
A Guard Timer is used to prevent ring nodes from receiving outdated R-APS
messages. During the duration of the guard timer, all received R-APS messages
are ignored by the ERPS Control Process. The period of the guard timer may be
configured by the operator in 10 ms steps between 10 ms and 2 seconds, with a
default value of 500 ms.
The Holdoff timer is not managed and fixed to 0 since no server layer
protection switching mechanism are present. The Ethernet MAC (ETH) layer,
where the ERPS take place, is supported by radio links acting as Ethernet PHY
(ETY) layer in 1+0 configuration.
Since the ERPS instances operate per VLAN on a logical ring protecting a set
of VLANs, this set must consequently be configured.
Note: In case of a double failure, if the restoring of the two failures takes place at the same time, an out
of service equal to the WTR could occur. To note that a switching off of a single NE causes a double failure
in the Ring.
3JK Edition 2.0
1 2 146
12 Ring Protection
3JK Edition 2.0
1 2 147
12 Ring Protection
3JK Edition 2.0
1 2 148
End of Module
Architecture
3JK Issue 2.0
Module 3
Management System
3JK Issue 2.0
Section 1
Product Overview
9500 MPR ETSI
3JK Issue 2.0
Product Overview Management System
1 3 2
Blank Page
Marcoussis
2010-07-21 01
Document History
3JK Issue 2.0
1 3 3
Module Objectives
describe the Management System of the 9500 MPR.
3JK Issue 2.0
1 3 4
3JK Issue 2.0
1 3 5
Table of Contents
Page
1 Management System 7
1.1 Network Management 8
Blank Page 10
2 MPR Management 11
2.1 9500 MPR Management 12
2.2 MPR IP addresses 13
2.3 TMN communication channels 15
2.4 TMN interfaces (9500 MPR Node) 16
2.5 LCT Connection 17
2.6 MPR Capability IP Parameters 18
Answer the Questions 21
Annexe: Example of MPR IP Addresses 22
End of Module 23
3JK Issue 2.0
1 3 6
3JK Issue 2.0
1 3 7
1 Management System
3JK Issue 2.0
1 3 8
1 Management System
1.1 Network Management
1350 OMS 1350 OMS
Access & Transport
Network Management
Multi-protocol management
SNMP
Q3
QB3*
TL1
All Access and Transport
Integrated in a single
Network Management Suite
9600 LSY 9600 LSY
9600 USY
9400 AWY
1650SMC
1662SMC
1642EM
New
9500 MPR
1850TSS
9500 MXC
1350 Open Management Suite
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.
9500 MPR can also be managed by Alcatel-Lucent 5620 SAM.
3JK Issue 2.0
1 3 9
1 Management System
1.1 Network Management [cont.]
TMN Platforms (common remote management evolution)
1
3
5
0

O
M
S
9500 MPR can be managed:
by Alcatel-Lucent 1350 OMS Network Management System,
by Alcatel-Lucent 5620 SAM.
3JK Issue 2.0
1 3 10
Blank Page
3JK Issue 2.0
1 3 11
2 MPR Management
3JK Issue 2.0
1 3 12
2 MPR Management
2.1 9500 MPR Management
E1 TDM Service, STM-1 SDH Service, ATM services and Ethernet services
can be managed end To end :
End to End Provisioning
End To End Monitoring
SDH/MPLS
Packet
Microwave
9500 MPR
Ethernet
Ethernet
TDM
TDM
9500 MPR
9500 MPR
E2E traffic management
Packet
Microwave
9500 MPR
9500 MPR
9500 MPR
Ethernet
Ethernet
1350 OMS
NMS
3JK Issue 2.0
1 3 13
2 MPR Management
2.2 MPR IP addresses
The NE has the following IP addresses:
NE IP address: it is the Controller IP address (default IP address = 10.0.1.2
with fixed mask 255.255.255.255);
TMN IP address: it is the IP address relevant to the Ethernet TMN port
(default IP address = 10.0.1.2 with mask 255.255.255.0);
TMN Port 4 IP address: the Port 4 can be used not for traffic, but for TMN.
Two TMN In-band addresses (by using the Ethernet traffic ports)
IP address assignment rules:
the TMN IP addresses of 2 NEs connected through a radio link must belong to
2 different subnetworks;
the TMN IP addresses of 2 NEs connected through an Ethernet cable must
belong to the same subnetwork.
MPR Node
(with MSS8 & MSS4)
As example of the IP address assignment refer to the attached diagram.
3JK Issue 2.0
1 3 14
2 MPR Management
2.2 MPR IP addresses [cont.]
The NE has the following IP addresses:
NE IP address: it is the Controller IP address (default IP address = 10.0.1.2
with fixed mask 255.255.255.255);
TMN IP address (NMS1): it is the IP address relevant to the NMS1 TMN port
TMN IP address (NMS2): it is the IP address relevant to the NMS2 TMN port
IP address assignment rules:
the TMN IP addresses of 2 NEs connected through a radio link must belong to
2 different subnetworks;
the TMN IP addresses of 2 NEs connected through an Ethernet cable must
belong to the same subnetwork.
MPR Terminal
(with MSS1c)
As example of the IP address assignment refer to the attached diagram.
3JK Issue 2.0
1 3 15
2 MPR Management
2.3 TMN communication channels
On the 9500 MPR Terminal three types of TMN communication channels
are present:
TMN channel carried by 64 kbits/sec channel inside Radio frame;
TMN channel carried locally by Ethernet frames in NMS1/NMS2 TMN ports (on
the front panel of the MSS-1c).
TMN channel carried inside a User Ethernet traffic frame defined with a VLAN
identifier (TMN In-Band).
On the 9500 MPR Node three types of TMN communication channels are
present:
TMN channel carried by 64 kbits/sec channel inside Radio frame;
TMN channel carried by Ethernet frames in Ethernet tributary 4 (on the front
panel of the Core-E module).
Two TMN In-band interfaces
3JK Issue 2.0
1 3 16
2 MPR Management
2.4 TMN interfaces (9500 MPR Node)
With the introduction of TMN In-Band two new IP interfaces are added to those already available.
NE Local IP Address
TMN Local Ethernet interface, IP/subnet
TMN Out-of-Band interface on User Ethernet port 4, IP/subnet
TMN In-Band interface #1, IP/subnet
TMN In-Band interface #2, IP/subnet
User Ethernet port 4 can then used as:
pure Ethernet traffic interface
pure Out-of-band TMN Local Ethernet interface
Ethernet traffic interface carrying TMN In-Band traffic
The NE Local IP Address can be reused on one of the other TMN interfaces. These interfaces must have
different IP subnets.
3JK Issue 2.0
1 3 17
2 MPR Management
2.5 LCT Connection
9500MPR Terminal can be controlled by a LCT connected to the MSS-
1c.
The connection can be performed by using:
The dedicated CT Ethernet port.
The NMS1/NMS2 TMN ports.
The TMN In-Band inside any User Ethernet traffic port defined with a VLAN
identifier.
9500MPR Node can be controlled by a LCT connected to the Core-E
unit.
The connection can be performed by using:
The dedicated NMS Ethernet port
Traffic Ethernet port, configured as TMN port.
3JK Issue 2.0
1 3 18
Traffic
NMS radio channel
MPR has routing capability. From an IP point of view it is a router.
Each port can activate OSPF or static routing.
In case of OSPF each address must belong to an OSPF area.
With an internal DHCP server, MPR gives an address to the CT connected to the CT port.
Traffic
NMS radio channel
Traffic
NMS radio channel
An address with a
subnet mask for the
craft terminal port
Craft Terminal
port: RJ45
An address with a subnet
mask for the Ethernet
Tributary 4 port
Ethernet Tributary 4
port: RJ45
2 MPR Management
2.6 MPR Capability IP Parameters
MPR Node
(with MSS8 & MSS4)
3JK Issue 2.0
1 3 19
An address with a
subnet mask for the
craft terminal port
Craft Terminal
port: RJ45
An address with a subnet
mask for the
NMS1/NMS2 TMN ports
NMS1 & NMS2 TMN
ports: RJ45
Traffic
NMS radio channel
Each port can activate static routing.
With an internal DHCP server, MPR gives an address to the CT connected to the CT port.
Traffic
NMS radio channel
2 MPR Management
2.6 MPR Capability IP Parameters [cont.]
MPR Terminal
(with MSS1c)
3JK Issue 2.0
1 3 20
An address with a
subnet mask for the
craft terminal port
Craft Terminal
port: RJ45
Traffic
NMS radio channel
Each port can activate static routing.
With an internal DHCP server, MPR gives an address to the CT connected to the FE port of
the GEthernet Generic Device.
2 MPR Management
2.6 MPR Capability IP Parameters [cont.]
MPR-e Stand-alone
MPT Interconnections
With/without
Power Injector Box
GEthernet
Generic
Device
FE
GE
E
t
h
e
r
n
e
t
c
o
n
n
e
c
t
i
o
n
3JK Issue 2.0
1 3 21
Answer the Questions
How many IP addresses can be assigned to the NE?
Which bit rate has been assigned to the TMN RF channel in the Radio
frame?
Which connections are available for the LCT?
3JK Issue 2.0
1 3 22
MPR IP Addresses
- Example -
Annexe
Annexe: Example of MPR IP Addresses
All Rights Reserved Alcatel-Lucent @@YEAR
@@PRODUCT @@COURSENAME
@@SECTIONTITLE @@MODULETITLE
@@SECTION @@MODULE 20
1 Management System
Example of MPR IP addresses
Node A
ETH Generator
PDH Generator
Node E
Node B
Node C
Node D
0.0.0.1 OSPF AREA
OFF NMS P4
00:20:60:05:02:07 NE MAC
10.0.10.1 NMS IP
10.0.3.1 NE IP
VLAN ID
11 12 13 14
10 11
1+1 HSB
1+1 FD
Traffic E1+ETH
TMN
Traffic E1 TDM2ETH
Traffic ETH
Port Number
VLAN ID
Traffic E1 TDM2TDM
VLAN ID
11 12 13 14 27 28 41 42
1 2 3 4 17 18 3132
1 2
VLAN ID
27 28
1,2,
1,2,
5 6 7 8
VLAN ID
41 42
ETH 2
ETH 1
ETH 1
ETH 2
0.0.0.1 OSPF AREA
OFF NMS P4
00:20:60:05:02:08 NE MAC
10.0.30.2 NMS IP
10.0.3.2 NE IP
0.0.0.1 OSPF AREA
OFF NMS P4
00:20:60:27:02:07 NE MAC
10.0.30.3 NMS IP
10.0.3.3 NE IP
0.0.0.1 OSPF AREA
10.0.5.4 NMS P4
00:20:60:27:02:05 NE MAC
10.0.4.4 NMS IP
10.0.3.4 NE IP
0.0.0.1 OSPF AREA
OFF NMS P4
00:20:60:05:02:06 NE MAC
10.0.4.5 NMS IP
10.0.3.5 NE IP
0.0.0.1 OSPF AREA
10.0.5.6 NMS P4
00:20:60:05:02:05 NE MAC
10.0.6.6 NMS IP
10.0.3.6 NE IP
10.0.10.1 DEFAULT GATEWAY
10.0.10.100 PC IP
10.0.6.6 DEFAULT GATEWAY
10.0.6.100 PC IP
Node F
TDM A
TDM C
TDM B
TDM C
TDM A
TDM B
Syncro Scheme
Net Mask 255.255.255.0
Example of MPR IP addresses
3JK Issue 2.0
1 3 23
End of Module
Management System
3JK Edition 1.00
Module 1
MSS HW Hardware Architecture
3JK Edition 1.00
Section 2
Functional Description
3JK Edition 1.00
9500 MPR 9500MPR R 2.1 Operation and Maintenence
Functional Description MSS HW Hardware Architecture
2 1 2
Blank Page
First edition External Consultant 2007-07-30 01
Document History
3JK Edition 1.00
2 1 3
Objectives
Objectives: to be able to
describe the functionality of each unit of the MSS-4/MSS-8.
3JK Edition 1.00
2 1 4
Objectives [cont.]
3JK Edition 1.00
2 1 5
Table of Contents
Page
1 PDH Local Access Unit 7
1.1 PDH Local Access unit 8
Blank Page 10
2 2xSTM-1 Local Access unit 11
2.1 2xSTM-1 Local Access unit 12
Blank Page 14
3 ASAP unit 15
3.1 ASAP unit 16
4 Modem unit (to interface ODU300) 19
4.1 Modem unit (to interface ODU300) 20
Blank Page 22
5 MPT Access Unit (with PFoE) 23
5.1 MPT Access Unit (with PFoE) 24
6 AUX peripheral unit 27
6.1 AUX peripheral unit 28
Blank Page 34
7 Core-E unit 35
7.1 Core-E unit 36
8 EAS unit 41
8.1 EAS unit 42
Blank Page 44
9 +24 Vdc/-48 Vdc Converter unit 45
9.1 +24 Vdc/-48 Vdc Converter unit 46
10 Power Extractor 47
10.1 Power Extractor 48
11 Power Injector 49
11.1 Power Injector 50
11.2 Versions 51
11.3 Connectors 53
11.4 LEDs 54
12 Distributors 55
12.1 Distributor 56
End of Module 66
3JK Edition 1.00
2 1 6
Page
3JK Edition 1.00
2 1 7
1 PDH Local Access Unit
3JK Edition 1.00
2 1 8
1.1 PDH Local Access unit
CESoP
32 E1
LIUs
32 E1 module
wk Core-E
sp Core-E
wk Core-E
sp Core-E
FPGA
(Ceres)
In the TX direction, the E1 PDH card (E1 Access) processes and encapsulates up to 32 E1 input lines into an
Ethernet packet that is sent to the Core-E card(s).
In the RX direction, the E1 Access card extracts data from the Ethernet data packets and processes the data
to provide up to 32 E1 output lines.
The 32xE1 Local Access Module performs the following macro functions:
Termination of 32 E1 signals (32 E1 bi-directional interfaces according ITU-T G.703 on the front panel)
Framed E1 bi-directional alarm management
Bi-directional Performance Monitoring on Framed E1
Encapsulation/Extraction of those PDH data flows into/from standard Ethernet packets Inter Working
Function
Reconstruction of the original PDH Timing meeting G823/824 Req.
Selection of the Active Core-E
Sending/getting those std Eth packets to the Core-E module
Communication with the Controller for provisioning and status report
The module communicates with the Core-E modules through two GbEth Serial copper bi-directional
interfaces on the backplane. The spare Core-E in not implemented.
3JK Edition 1.00
2 1 9
1.1 PDH Local Access unit [cont.]
E1
17-32
E1
1-16
3JK Edition 1.00
2 1 10
Blank Page
3JK Edition 1.00
2 1 11
2 2xSTM-1 Local Access unit
3JK Edition 1.00
2 1 12
2.1 2xSTM-1 Local Access unit
2xSTM-1 Local Access unit
The STM-1 unit can be used in two different working modes, addressing two different network scenarios:
STM-1 channelized
STM-1 transparent
The STM-1 channelized mode is available by provision the unit as "SDHCHAN" and the STM-1 transparent mode is
available by provision the unit as "SDHACC".
The STM-1 unit can support 1 channelized STM-1 or up to 2 transparent STM-1 interfaces.
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).
Link options include:
1+0 non-protected operation
1+1 EPS protection (available ONLY with the optical interface)
When the 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.
The 2xSTM-1 Local Access Unit performs the following macro functions:
Transparent or channelized transport of the STM-1
Encapsulation/Extraction of the STM-1 into/from standard Ethernet packets Inter Working Function
Reconstruction of the original STM-1 Timing
Selection of the Active Core-E
Sending/getting those std Eth packets to the Core-E module
Communication with the Controller for provisioning and status report
The unit communicates with the Core-E modules through two GbEth Serial copper bi-directional interfaces on the
backplane.
3JK Edition 1.00
2 1 13
2.1 2xSTM-1 Local Access unit [cont.]
3JK Edition 1.00
2 1 14
Blank Page
3JK Edition 1.00
2 1 15
3 ASAP unit
3JK Edition 1.00
2 1 16
3 ASAP unit
3.1 ASAP unit
The ASAP unit is used to transport 16xE1 ATM traffic, with E1/IMA physical layer, in an MPR network.
The ASAP units are unprotected (No 1+1 EPS is available).
ATM traffic is transported within MPR network as "special" Ethernet traffic.
This "special" Ethernet traffic is managed by MPR following to RFC 4717 (IETF ATM PseudoWire
EdgetoEdgeeEmulation, PWE3) with N-1 encapsulation format.
ATM PW Ethernet traffic is managed by MPR is such a way to emulate the native QoS that would be applied
by an ATM equipment; in addition to that, specific techniques, similar to those applied to TDM2ETH traffic,
are applied to have air bandwidth optimisation (ATM PW Header Compression) and reduce Cell Error Rate
degradation due to packetization.
3JK Edition 1.00
2 1 17
3 ASAP unit
3.1 ASAP unit [cont.]
Main Characteristics
16xE1 G.704 supporting ATM/IMA
IMA protocol 1.1
Node-timed/loop-timed E1 port synch
ATM PWE3 encapsulation with N-to-one (N=1) encapsulation format (RFC
4717)
Max 8 IMA group
Max 16 E1 per IMA group
The IMA group must be in the same ASAP card
Ingress/Egress VPI translation
Transport of ATM traffic can be done in VCC mode or VPC mode (all the
nodes of the MPR chain must have the same mode):
VCC mode
VPC mode
Interfaces
16 E1 G.704 - SCSI Connectors
75 ohm or 120 ohm (at NE level)
VCC mode
It is possible to transport max 48 VC for every IMA group. It is possible to manage VC switching (= VCI and
VPI change)
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) is managed only at VP level.
N.B.: The sum of VP + VC configured on a single ASAP card must be <128.
3JK Edition 1.00
2 1 18
3 ASAP unit
3.1 ASAP unit [cont.]
The 16xE1 ATM streams enter the ASAP unit on the front panel.
The block diagram is divided in 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).
3JK Edition 1.00
2 1 19
4 Modem unit (to interface ODU300)
3JK Edition 1.00
2 1 20
4.1 Modem unit (to interface ODU300)
Analog Chain
GbE Serial from/to Alternate
Radio Board for RPS
TX
MODULATOR
RX
DEMOD
MODEM
ASIC
DAC
/ 2
DAC
I
Q
IF RX
311 Mhz
ADC
/ 2
ADC
I
Q
126 Mhz
IF cable
interface
AIR FRAMER
PDH/Data
management
IDU/ODU
communication
EPS
TX
AIR deFRAMER
PDH/Data
management
ODU/IDU
communication
RPS
RX
FPGA
(Guinnes)
IF TX
In Tx direction, the MODEM Module generates the IF signal to be sent to an MXC Out Door Unit. Such signal
contains a Constant Bit Rate signal built with the Ethernet packets coming from the Core-E; those packets
are managed in a different way depending on their own native nature.
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
Equalisation
Error Correction
Digital Deframer
RPS (hitless)
Defragmentation
3JK Edition 1.00
2 1 21
4.1 Modem unit (to interface ODU300) [cont.]
Transmitter connected to the antenna
3JK Edition 1.00
2 1 22
Blank Page
3JK Edition 1.00
2 1 23
5 MPT Access Unit (with PFoE)
3JK Edition 1.00
2 1 24
5.1 MPT Access Unit (with PFoE)
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:
by using two connectors:
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).
If the optical port has to be used, an SFP plug-in must be installed.
N.B.: If has been enabled port #1 (optical or electrical), the associated Power Supply port is #1.
N.B.: If has been enabled port #2 (optical or electrical), the associated Power Supply port is #2.
The connection to the MPT-MC is realized 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).
3JK Edition 1.00
2 1 25
5.1 MPT Access Unit (with PFoE) [cont.]
Main functions:
Provide the power supply interface and the Ethernet interface
Provide the Power Feed over Ethernet function
Lightning and surge protection
Ethernet and power interface supervision
EPS/HSB management function
Clock distribution function
L2 packet based Proprietary clock algorithm
Ethernet link quality monitor function
Radio Link Quality notification through MPR Protection Protocol frames
Communication with Core controller for provisioning and status report
3JK Edition 1.00
2 1 26
5.1 MPT Access Unit (with PFoE) [cont.]
Note 1: The GREEN and YELLOW colours of the Card Status LED have different meaning, if two MPT (HC or
MC) are connected:
no MPT in 1+1 EPS protection is provisioned:
YELLOW colour is not applicable (traffic impact if peripheral is plugged-out)
1 MPT in 1+1 EPS protection is provisioned, with mated MPT provisioned on other MPT Access peripheral:
GREEN if provisioned MPT is EPS Active
YELLOW if provisioned MPT is EPS Standby (no traffic impact if peripheral is plugged-out)
1 MPT in 1+1 EPS protection is provisioned, with mated MPT provisioned on other MPT Access peripheral,
1 MPT in 1+0 is provisioned on same MPT Access peripheral:
2 MPTs in 1+1 EPS protection are provisioned, with mated MPTs provisioned on other MPT Access
peripheral:
GREEN if at least one of provisioned MPT is EPS Active
YELLOW if both MPTs are EPS Standby (no traffic impact if peripheral is plugged-out)
2 MPTs in 1+1 EPS protection on the same MPT Access peripheral are provisioned:
Warning: The optional SFP plug-in, which has to be installed in the MPT Access unit, contains a Class 1 laser
source. The laser source is placed in the left side of the SFP plug-in.
According to the IEC 60825-1 the explanatory label is not sticked on the equipment due to the lack of space.
3JK Edition 1.00
2 1 27
6 AUX peripheral unit
3JK Edition 1.00
2 1 28
6.1 AUX peripheral unit
AUX peripheral unit block diagram
Service Channels access and Housekeeping alarms are available with the optional Auxiliary peripheral unit.
Only one Auxiliary peripheral can be equipped. It can be installed in Slot 8 of MSS-8 or Slot 4 of MSS-4.
The Auxiliary peripheral unit on front panel is equipped with four connectors:
one connector to manage the Service Channel 1
one connector to manage the Service Channel 2
one connector to manage the housekeeping alarms
one connector for EOW (not used in the current release)
3JK Edition 1.00
2 1 29
6.1 AUX peripheral unit [cont.]
Service Channels
By CT/NMS the user can enable/disable the 64 kbit/s Service Channel
interfaces. By default they are disabled.
When enabled, the Service Channel interface 1 can be configured to
transport the following protocol:
1) Synchronous 64 Kb/s RS422/V.11 DCE co-directional
When enabled, the Service Channel interface 2 can be configured to
transport the following protocol:
1) 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 the transmission of the Service Channels.
3JK Edition 1.00
2 1 30
Alarm-Housekeeping
13 Alarm-Housekeeping pins are provided:
6 pins are configured as inputs
7 pins are configured as outputs.
3JK Edition 1.00
2 1 31
Input alarms
The polarity of each input Alarm-Housekeeping is configurable. The
state of each alarm input is configurable in order to be active, if the
voltage on the input is high (open contact) or if the voltage is low
(closed contact). This second option is the default value.
It is possible to assign one user label for each input.
3JK Edition 1.00
2 1 32
Output alarms
By default the presence of active alarm corresponds to closed relay
contact with a common wire available to the customer. By CT/NMS the
polarity can be changed independently for each alarm (both normally
closed and normally open contacts are available on the I/O connector).
When the power supply is down (and also when the power supply is on
but the SW has not yet initialized the HW), all the relays of the outputs
of the alarms/housekeeping are in the "open" state (HW default
condition).
The Output Housekeeping can be managed in Manual mode only: in
Manual mode the output state of each housekeeping is controlled by
the operator.
It is possible to assign one user label for each output.
Note: the Automatic mode is not supported in this release.
3JK Edition 1.00
2 1 33
3JK Edition 1.00
2 1 34
Blank Page
3JK Edition 1.00
2 1 35
7 Core-E unit
3JK Edition 1.00
2 1 36
7 Core-E unit
7.1 Core-E unit
2 SPFs
(option)
Based on packet technology with 7 GbEth serial internal interfaces between Core-E and peripherals
(jumbo frames 9728 bytes allowed)
4x10/100/1000 Ethernet electrical embedded interface (RJ45): port #1 to port #4
2 optional SFPs: port #5 and port #6.
The Ethernet ports of the Core-E can be configured in 2 ways:
to be used as GigaEthernet interface for Ethernet traffic (Note: for port#5 and port#6 the optional SFP
must be installed);
to be used to connect an MPT: MPT-HC or MPT-MC to port#1 to port#4; an MPT-HC only to port#5 and
port#6.
The flash card stores the licence type, the equipment software, the equipment MIB and the equipment MAC
address.
Main Functions
Controller
Layer 2+ Eth Switch, VLAN management & MAC based
Ethernet MAC learning
x-connect function for PDH and Data payload traffic;
For any packetized flow, the switch will be in charge to manage the EPS also.
QoS management.
Selection of the synchronization Ck to be distributed to all plug-in.
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.
3JK Edition 1.00
2 1 37
7 Core-E unit
7.1 Core-E unit [cont.]
(optional)
Warning: The optional optical SFP plug-in, which has to be installed in port #5 and port #6 of the Core-E
unit, contains a Class 1 laser source. The laser source is placed in the left side of the SFP plug-in. According
to the IEC 60825-1 the explanatory label is not sticked on the equipment due to the lack of space.
3JK Edition 1.00
2 1 38
7 Core-E unit
Available SFPs for port #5 and port #6
The following SFPs are available:
1000BASE-LX (optical interface for Ethernet traffic)
1000BASE-SX (optical interface for Ethernet traffic)
1000BASE-T (electrical interface for Ethernet traffic)
2xE1 (electrical interface for 2 E1 streams)
EoSDH (optical interface for STM-1 signal with Ethernet traffic encapsulation)
3JK Edition 1.00
2 1 39
7 Core-E unit
2xE1 SFP
The 2xE1 SFP is an SFP module supporting MEF8 circuit emulation of up to 2
E1.
This module supports:
differential clock recovery
node timing
loop timing
This module is Synchronous Ethernet capable and it is compliant to optical
SFP 1000BASE-X. It can deliver the clock recovered from one of two
tributaries to hosting card through the standard SFP pin-out.
SFP module supports TDM2TDM and TDM2ETH services.
The port, in which the SFP has been installed, must be enabled by the
WebEML as an optical port, then all the configuration must be done with an
Enhanced Configuration File.
Note: 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.
3JK Edition 1.00
2 1 40
7 Core-E unit
EoSDH SFP
The Ethernet over SDH SFP is an SFP module supporting the delivery of
Ethernet traffic over SDH layer by GFP encapsulation.
The module is compliant to 1000BASE-X specification and support one STM1
interface.
The NE manages the EoSDH SFP as an optical User Ethernet interface.
Synchronous operation mode and SSM support are not available, when EoSDH
SFP is hosted as optical User Ethernet interface.
Note: For the correct operation of the EoSDH SFP it is necessary to disable the autonegotiation via WebEML
or via the Configuration File.
3JK Edition 1.00
2 1 41
8 EAS unit
3JK Edition 1.00
2 1 42
8 EAS unit
8.1 EAS unit
In case more than 6 local Ethernet accesses are needed (built-in in the Core-E unit), EAS unit (P8ETH)
offers additional eight 10/100/1000 Ethernet interfaces.
An embedded 10 Gbit/sec L2 switch is present on the unit.
There are 4 Electrical 10/100/1000 base-T electrical ports and 4 optical SFP (LX and SX).
3JK Edition 1.00
2 1 43
8 EAS unit
8.1 EAS unit [cont.]
3JK Edition 1.00
2 1 44
Blank Page
3JK Edition 1.00
2 1 45
9 +24 Vdc/-48 Vdc Converter unit
3JK Edition 1.00
2 1 46
9 +24 Vdc/-48 Vdc Converter unit
9.1 +24 Vdc/-48 Vdc Converter unit
When office power configuration consists of +24 Vdc a +24/-48 volt power converter is required to condition
office power to -48 Vdc for the MSS-4/8 shelf.
The power converter resides in slot 3 or 4 of the MSS-4 shelf and either slot 4, 6, or 8 in the MSS-8 shelf.
Office power (+24 Vdc) is connected to the PDU which in turn connects to the power converter.
The output of the Power Converter (-48 Vdc) is then connected to the MSS-4/8 shelf power connector(s).
The Power Converter supports both unprotected and protected power arrangements.
The same PDU power cables are used to connect between the PDU and the power converter.
Keyed power cables are used to connect between the power converter and the MSS-4/8 shelf.
3JK Edition 1.00
2 1 47
10 Power Extractor
3JK Edition 1.00
2 1 48
10 Power Extractor
10.1 Power Extractor
The Power 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 Power Extractor then separates the Power Supply from the Ethernet
traffic, which are separately sent to the MPT-HC.
The two cables, interconnecting the Power Extractor to the MPT-HC (the Power Supply cable to be
connected to the DC Out connector of the Power Extractor and Ethernet cable to be connected to the Data
Out connector of the Power Extractor), are provided, already terminated (2 m long), with the Power
Extractor itself.
3JK Edition 1.00
2 1 49
11 Power Injector
3JK Edition 1.00
2 1 50
11 Power Injector
11.1 Power Injector
The Power Injector is an indoor device designed to deliver the DC
power supply to MPT by using the same cable carrying the Ethernet
traffic.
The Power Injector receives at the input the Ethernet traffic and the
power supply on two dedicated connectors and sends to the output on
one connector the Power Supply + Ethernet Traffic. This solution,
called PFoE (Power Feed over Ethernet), is proprietary.
The Power Injector can supply up to 2 MPT.
The two Power Supply Sources provide power supply redundancy.
3JK Edition 1.00
2 1 51
11 Power Injector
11.2 Versions
Power Injector plug-in: installed in the MSS shelf and powered through
the backplane.
The Power Injector plug-in is not managed by MSS.
The Plug-in just needs an empty slot to be inserted in.
As consequence, no specific commissioning activity is needed to insert
a Power Injector plug-in on a existing MSS shelf.
3JK Edition 1.00
2 1 52
11 Power Injector
11.2 Versions [cont.]
Power Injector box: stand-alone box, powered through two connectors
on the front providing power supply redandancy.
The box can be mounted in a rack by means of a separate bracket.
The bracket can support two boxes side by side.
Height: 1,3 U.
3JK Edition 1.00
2 1 53
11 Power Injector
11.3 Connectors
Two DC connectors in the front (for box version), or power from the
backpanel (for plug-in version).
Two RJ45 for the data in (DATA)
Two RJ45 for the data + DC out (DC+DATA)
3JK Edition 1.00
2 1 54
11 Power Injector
11.4 LEDs
Two LEDs indicate the presence of DC voltage on each Ethernet output.
3JK Edition 1.00
2 1 55
12 Distributors
3JK Edition 1.00
2 1 56
12 Distributors
12.1 Distributor
The Distributor subracks available are shown in the next pages.
3JK Edition 1.00
2 1 57
12 Distributors
12.1 Distributor [cont.]
Protection Panel 32E1 SCSI 68 - 1.0/2.3 75 ohm (Front/Rear)
3JK Edition 1.00
2 1 58
12 Distributors
Protection Panel RJ45 120 ohm (Front/Rear)
3JK Edition 1.00
2 1 59
12 Distributors
Protection Panel 32E1 SCSI 68 - 1.6/5.6 75 ohm (Front)
3JK Edition 1.00
2 1 60
12 Distributors
Protection Panel 32E1 BNC 75 ohm (Front)
3JK Edition 1.00
2 1 61
12 Distributors
Connector support 1.6/5.6 75 ohm Panel 1U
3JK Edition 1.00
2 1 62
12 Distributors
Connector support BNC 75 ohm Panel 1U
3JK Edition 1.00
2 1 63
12 Distributors
Support 19 Inch modules 120 ohm Panel 3U
3JK Edition 1.00
2 1 64
12 Distributors
E1 Protection SCSI 68/Sub-D 37 (Front/Rear)
3JK Edition 1.00
2 1 65
How many E1 streams are available on the front panel of the PDH
access unit?
When the Power Emission Status LED of the Modem unit is green ON in
the HSB configuration?
Which information is stored in the Flash Card installed in the Core-E
unit?
3JK Edition 1.00
2 1 66
End of Module
MSS HW Hardware Architecture
3JK Issue 2.0
Module 2
ODU300 HW Architecture
3JK Issue 2.0
Section 2
9500 MPR ETSI
3JK Issue 2.0
Functional Description ODU300 HW Architecture
2 2 2
Blank Page
Marcoussis
2010-10-28 01
Document History
3JK Issue 2.0
2 2 3
Module Objectives
Describe the functionality of the ODU 300.
3JK Issue 2.0
2 2 4
3JK Issue 2.0
2 2 5
Table of Contents
Page
1 Outdoor Units 7
1.1 ODU300 Construction and Mounting 8
1.2 ODU300 Characteristics 9
2 Outdoor Installations 11
2.1 Installing the ODU 12
2.2 Direct-Mounted ODUs 13
2.3 Remote-Mounted ODUs (solution 1) 14
2.4 Remote-Mounted ODUs (solution 2) 15
2.5 Waveguide Flange Data 17
2.6 Grounding the ODU 18
2.7 ODU external connectors 19
End of Module 22
3JK Issue 2.0
2 2 6
3JK Issue 2.0
2 2 7
1 Outdoor Units
3JK Issue 2.0
2 2 8
1 Outdoor Units
1.1 ODU300 Construction and Mounting
Construction comprises:
Cast aluminium base (alloy 380)
Pressed aluminium cover (sheet grade alloy 1050)
Base and cover passivated and then polyester powder coated
Compression seal for base-cover weatherproofing
Carry-handle
ODU300 Housing
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-E-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.
ODUs are fixed for Tx High or Tx Low operation.
Where two ODUs are to be connected to a single antenna for hot-standby or frequency diversity
configurations, a direct-mounting coupler is used. They are available for equal or unequal loss
operation. Equal loss is nominally 3 dB.
Unequal is nominally 1/6 dB.
The ODU assembly meets the ASTME standard for a 2000 hour salt-spray test, and relevant IEC, UL, and
Bellcore standards for wind-driven rain.
ODUs are frequency-band specific, but within each band are capacity-independent up to their design
maximums.
3JK Issue 2.0
2 2 9
1 Outdoor Units
1.2 ODU300 Characteristics
4, 16, 64 QAM Modulation support (Adaptive modulation)
4, 16, 32, 64, 128, 256 QAM Modulation support (Static modulation)
L6, U6, 7, 8, 11, 13, 15, 18,
23, 26, 28, 38 GHz
Frequency Band options
General Specification
150 meters MSS to ODU Maximum IF 10.3 mm Cable length [NB]
126 MHz Receive
311 MHz Transmit Intermediate Frequency
IF Specifications
[NB] Longer distances are possible using higher specification cable.
3JK Issue 2.0
2 2 10
1 Outdoor Units
1.2 ODU300 Characteristics [cont.]
Remote mount via flex/elliptical
waveguide
6-38 GHz, optional
Proprietary direct mount for antenna
diameters 0.3 to 1.8m
Remote mount for antenna diameters
>1.8m
6-38 GHz, standard Polarisation, field
selectable Antenna
Mounting
Standard EIA rectangular waveguide,
refer to ODU System specifications
Vertical (standard) or Horizontal
6-38 GHz Antenna port Interface
BNC AGC monitor point
N-Type IF cable connector
ODU Interfaces
3JK Issue 2.0
2 2 11
2 Outdoor Installations
3JK Issue 2.0
2 2 12
2.1 Installing the ODU
The type is ODU300.
All ODUs are designed for direct-mounting to a collar supplied with direct-
fit antennas.
All ODUs can also be installed with standard antennas using a remote-
mount kit.
For single-antenna protected operation a coupler is available to support
direct mounting of the two ODUs to its antenna, or to support direct
mounting onto a remote-mounted coupler.
On the next slides, information are given concerning:
Direct-Mounted ODUs
Remote-Mounted ODUs
Grounding the ODU
3JK Issue 2.0
2 2 13
2.2 Direct-Mounted ODUs
The ODU is attached to its mounting collar using four mounting bolts,
which have captive 19 mm (3/4) nuts for fastening.
The ODU mounts directly to its antenna mount, as shown in Figure.
Pressed-Cover ODU and Mounting Collar
3JK Issue 2.0
2 2 14
2.3 Remote-Mounted ODUs (solution 1)
ODUs can be installed separately from its antenna, using a remote-mount to support the ODU, and a
flexible-waveguide or coaxial cable to connect the ODU to its antenna:
a flexible waveguide is required.
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.
3JK Issue 2.0
2 2 15
2.4 Remote-Mounted ODUs (solution 2)
3JK Issue 2.0
2 2 16
2.4 Remote-Mounted ODUs (solution 2) [cont.]
3JK Issue 2.0
2 2 17
2.5 Waveguide Flange Data
Flange thickness + Hole
depth - 2mm
6 6H M3x0.5 4 4 x M3 WR28 PBR320 UBR320 28/32/38
GHz
depth - 2mm
6 6H M3x0.5 4 4 x M3 WR42 PBR220 UBR220 18/23/26
GHz
depth - 2mm
8 6H M4x0.7 4 4 x M4 WR62 PBR140 UBR140 15 GHz
depth - 2mm
8 6H M4x0.7 4 4 x M4 WR75 PBR120 UBR120 13 GHz
depth - 2mm
8 6H M4x0.7 8 8 x M4 WR90 PDR100 UDR100 11 GHz
depth - 2mm
8 6H M4x0.7 8 8 x M4 WR112 PDR84 UDR84 7/8 GHz
depth - 2mm
10 6H M5x0.8 8 8 x M5 WR137 PDR70 UDR70 6 GHz
Bolt Length Required
Hole
Depth
mm
Thread
Spec
Bolt
Type
Bolts
Reqd
Spring
Washers
Reqd
Waveguide
Type
WaveguideM
ating Flange
Radio
Flange
Freq Band
Table lists the antenna port flange types used with the ODU300, plus their mating flange options and
fastening hardware for remote mount installations.
UDR/PDR flanges are rectangular; UBR/PDR flanges are square.
On the ODU, the two flange styles are:
UDR. 6-hole or 8-hole (6/8 bolt holes depending on frequency range/waveguide type), flush-face
flange with threaded, blind holes.
UBR. 4-hole flush-face flange with threaded, blind holes.
The corresponding mating flange styles are:
PDR. 6-hole or 8-hole flange with gasket groove and clear holes.
PBR. 4-hole flange with a gasket groove and clear holes.
All fastening hardware is metric.
3JK Issue 2.0
2 2 18
2.6 Grounding the ODU
For all set-ups, one ground wire must be installed to ground the ODU.
The lightning surge suppressor is integrated in the ODU.
3JK Issue 2.0
2 2 19
2.7 ODU external connectors
Vertical Polarization Horizontal Polarization
Waveguide feed head
RSSI connector
IF cable
connector
(to Indoor Unit)
IF cable connector
(to Indoor Unit)
RSSI
connector
3JK Issue 2.0
2 2 20
2.7 ODU external connectors [cont.]
RSSI Monitoring Point
The ODU has a capped BNC female connector to access RSSI during antenna
alignment.
There is a linear relationship of voltage to RSSI, as shown in the table below;
an RSSI of 0.25 Vdc is equivalent to -10 dBm RSSI, and each additional 0.25
Vdc RSSI increase thereafter corresponds to a 10 dBm decrease in RSSI.
The lower the voltage the higher RSSI and better aligned the antenna is.
The RSSI figures in dBm are identical to the RSL figures displayed in A9500
MPR Craft Terminal.
RSSI Table
-100 -90 -80 -70 -60 -50 -40 -30 -20 -10 RSSI (dBm)
2.5 2.25 2.0 1.75 1.5 1.25 1.0 0.75 0.5 0.25 BNC (Vdc)
Measurement Units
3JK Issue 2.0
2 2 21
Which modulations are supported in the ODU?
Which is the maximum length of the IF cable?
Can the ODU be directly connected to the antenna?
When must be used the RSSI monitoring point?
3JK Issue 2.0
2 2 22
End of Module
ODU300 HW Architecture
3JK Issue 2.0
Module 3
MPT-HC HW Architecture
3JK Issue 2.0
Section 2
9500 MPR ETSI
3JK Issue 2.0
Functional Description MPT-HC HW Architecture
2 3 2
Blank Page
First edition ALU Universitu,
Marcoussis
2010-10-28 01
Document History
3JK Issue 2.0
2 3 3
Module Objectives
Describe the functionality of the MPT-HC.
3JK Issue 2.0
2 3 4
3JK Issue 2.0
2 3 5
Table of Contents
Page
1 Outdoor Units 7
1.1 MPT-HC Construction and Mounting 8
1.2 MPT-HC Characteristics 13
Blank Page 14
2.1 Installing the MPT-HC 16
2.2 6-7-8 GHz MPT-HC: integrated antenna (1+0) 17
2.3 11-38 GHz MPT-HC: integrated antenna (1+0) 18
2.4 6-7-8 GHz MPT-HC: integrated antenna (1+1) 19
2.5 11-38 GHz MPT-HC: integrated antenna (1+1) 20
2.6 6-7-8 GHz MPT-HC: non-integrated antenna (1+0) 21
2.7 11-38 GHz MPT-HC: non-integrated antenna (1+0) 22
2.8 6-7-8 GHz MPT-HC: non-integrated antenna (1+1) 23
2.9 11-38 GHz MPT-HC: non-integrated antenna (1+1) 24
2.10 MPT-HC external connectors 25
2.11 DC Extractor 30
End of Module 32
3JK Issue 2.0
2 3 6
3JK Issue 2.0
2 3 7
1 Outdoor Units
3JK Issue 2.0
2 3 8
1 Outdoor Units
1.1 MPT-HC Construction and Mounting
MPT-HC (Microwave Packet Transport) is a Microwave Equipment
capable to transport the Ethernet traffic over an RF radio channel.
The MPT-HC includes a waveguide antenna port, type-N female
connector for the DC connection, a maintenance connector (with
captive protection cap) for RSSI access, 1 electrical GE interface, 2 GE
optical interfaces (1 for data, 1 for for RPS) and a grounding stud.
The MPT-HC can be installed on an integrated antenna or on standard
poles, wall or pedestal mount, with an appropriate fastening system.
The MPT-HC (one or two depending on the configuration 1+0 or 1+1,
each one with a solar shield) incorporates the complete RF transceiver
and can be associated with an integrated or separate antenna.
The MPT-HC can be rapidly installed on standard poles with an
appropriate fastening system. The pole mounting is the same for 1+0 or
1+1 configurations from 6 to 38 GHz.
3JK Issue 2.0
2 3 9
1 Outdoor Units
1.1 MPT-HC Construction and Mounting [cont.]
For 6 GHz & 7/8 GHz, the MPT-HC polarization is determined by the
rotation of the MPT-HC in 1+0 configuration and by the position of a
polarization rotator fitted within the coupler in 1+1 configuration.
For 11 GHz to 38 GHz, the MPT-HC polarization is determined by the
rotation of the polarization rotator fitted in the antenna port of the
MPT-HC in 1+0 configuration and by the position of a polarization
rotator fitted within the coupler in 1+1 configuration.
Where two MPT-HC have to be connected to a single antenna for hot-
standby or frequency diversity configurations, a direct-mounting
coupler is used. They are available for equal or unequal loss operation.
Equal loss is nominally 3 dB. Unequal is nominally 1/10 dB.
Three mechanical solutions are adopted.
3JK Issue 2.0
2 3 10
1 Outdoor Units
11-38 GHz MPT-HC housing
With embedded diplexer for cost optimisation (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.
3JK Issue 2.0
2 3 11
1 Outdoor Units
6 GHz MPT-HC housing
With embedded diplexer for cost optimisation 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;
3JK Issue 2.0
2 3 12
1 Outdoor Units
7-8 GHz MPT-HC housing
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: the
BRANCHING assembly (containing the diplexer) and the RF TRANSCEIVER assembly (containing the RF
section); 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.
3JK Issue 2.0
2 3 13
1 Outdoor Units
1.2 MPT-HC Characteristics
4, 16, 32, 64, 128, 256 QAM Modulation support (Adaptive modulation)
L6, U6, 7, 8, 11, 13, 15, 18,
23, 26, 38 GHz
20 m (to interconnect the two MPT-HC) Optical cable to be used in 1+1
configuration
100 m with electrical cable
500 m with optical cable
Ethernet cable
> 200 m with cable diam. = 10.3 mm
< 200 m with cable diam. = 6.85 mm
Power Supply cable
Cable lenght
3JK Issue 2.0
2 3 14
Blank Page
3JK Issue 2.0
2 3 15
3JK Issue 2.0
2 3 16
2.1 Installing the MPT-HC
MPT-HC is designed for direct-mounting to a collar supplied with direct-
fit antennas. MPT-HC can also be installed with standard antennas using
a remote-mount kit.
direct mounting of the two MPT-HC to its antenna, or to support direct
Installation with integrated antenna
Installation with non-integrated antenna
3JK Issue 2.0
2 3 17
2.2 6-7-8 GHz MPT-HC: integrated antenna (1+0)
3JK Issue 2.0
2 3 18
2.3 11-38 GHz MPT-HC: integrated antenna (1+0)
3JK Issue 2.0
2 3 19
2.4 6-7-8 GHz MPT-HC: integrated antenna (1+1)
3JK Issue 2.0
2 3 20
2.5 11-38 GHz MPT-HC: integrated antenna (1+1)
3JK Issue 2.0
2 3 21
2.6 6-7-8 GHz MPT-HC: non-integrated antenna (1+0)
3JK Issue 2.0
2 3 22
2.7 11-38 GHz MPT-HC: non-integrated antenna (1+0)
3JK Issue 2.0
2 3 23
2.8 6-7-8 GHz MPT-HC: non-integrated antenna (1+1)
3JK Issue 2.0
2 3 24
2.9 11-38 GHz MPT-HC: non-integrated antenna (1+1)
PROTECTION
MPT-HC
RF coupler
MAIN
MPT-HC
3JK Issue 2.0
2 3 25
2.10 MPT-HC external connectors
Views of MPT-HC with embedded diplexer (11-38 GHz)
(1)
RF
connection
(2)
Power Supply
(3)
Eth.
connection
(4)
Second MPT-HC
connection in 1+1
RJ45
Place to install the
optional SFP plug-in
SFP for 1+1
configuration
CO-BOX
(5)
WARNING: A waterproofness tape is glued on the waveguide of the MPT-HC. It must never be removed.
(1) RF interface for connection of antenna or coupler waveguide
(2) Connector for power supply coaxial cable male N 50 ohm
(3) Hole for Ethernet connection (in the co-box) Gland for Cat5e or optical cable (optional)
(4) Hole for connection to a second MPT-HC in 1+1 (in the co-box) Not used
(5) Co-box
ODC Hole for connection to a second
MPT-HC in 1+1 (in the co-box)
(4)
Gland for Cat5e or optical
cable (optional)
Hole for Ethernet connection (in the co-
box)
(3)
male N 50 ohm Connector for power supply coax. cable (2)
waveguide RF interface for connection of antenna or
coupler
(1)
Connector Interface Ref. in
figure
WR75
11
WR62
13-15
WR42
18-26
WR28 Waveguide type ->
38 FREQUENCY GHz ->
3JK Issue 2.0
2 3 26
(3)
Eth.
connection
(4)
Second
MPT-HC
Connection
in 1+1
(2)
Power Supply
2.10 MPT-HC external connectors [cont.]
Views of MPT-HC with embedded diplexer (7 GHz and 8 GHz)
OPENING THE CO-BOX
RJ45 for electrical
connection
optional SFP for
optical connection
SFP for 1+1
configuration
(1)
RF
connection
CO-BOX
(5)
(5) Co-box
(4)
cable (optional)
box)
(3)
coupler
(1)
figure
WR112
8
7 FREQUENCY GHz ->
3JK Issue 2.0
2 3 27
(3)
Eth.
connection
(4)
Second
MPT-HC
Connection
in 1+1
(2)
Power Supply
(1)
RF
connection
Views of MPT-HC with embedded diplexer (6 GHz)
RJ45 for electrical
connection
optional SFP for optical
connection
SFP for 1+1
configuration
OPENING THE CO-BOX
CO-BOX
(5)
(5) Co-box
(4)
cable (optional)
box)
(3)
coupler
(1)
figure
6 FREQUENCY GHz ->
3JK Issue 2.0
2 3 28
A voltmeter, such as a multimeter, is used to measure RSSI voltage.
Use the Light service kit cable for the power monitoring in addition to a
voltmeter.
Connect a voltmeter to the MPT-HC through the Light service kit cable.
The RSSI voltage provides a direct relationship with RSL, as follows:
-100 -90 -80 -70 -60 -50 -40 -30 -20 -10 RSL (dBm)
0.14 0.59 1.11 1.71 2.3 2.9 3.5 4.12 4.71 5 Service kit cable (Vdc)
Measurement (with MPT-HC) Units
3JK Issue 2.0
2 3 29
MPT Service Cord
Optional cable (P/N 3CC52191AA**).
Connector usage:
(M1) LEMO connector, to be plugged into LEMO connector on MPT-HC/MPT-MC.
banana plugs (M3) and (M4): output is a 0 to +5V DC voltage proportional to the radio Rx field. During
equipment lineup, 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.
(M2) RJ45 connector, to connect the MCT directly to the MPT.
3JK Issue 2.0
2 3 30
2.11 DC Extractor
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.
3JK Issue 2.0
2 3 31
Which modulations are supported in the MPT-HC?
Which is the maximum length of the Power Supply cable?
Can the MPT-HC be directly connected to the antenna?
3JK Issue 2.0
2 3 32
End of Module
MPT-HC HW Architecture
3JK Issue 2.0
Module 4
MPT-HC V2 HW Architecture
3JK Issue 2.0
Section 2
9500 MPR ETSI
3JK Issue 2.0
Functional Description MPT-HC V2 HW Architecture
2 4 2
Blank Page
First edition ALU Universitu,
Marcoussis
2010-10-28 01
Document History
3JK Issue 2.0
2 4 3
Module Objectives
Describe the functionality of the MPT-HC V2.
3JK Issue 2.0
2 4 4
3JK Issue 2.0
2 4 5
Table of Contents
Page
1 Outdoor Units 7
1.1 MPT-HC V2 Construction and Mounting 8
1.2 MPT-HC V2 Characteristics 11
Blank Page 12
2.1 Installing the MPT-HC V2 14
2.2 MPT-HC V2 external connectors 15
End of Module 20
3JK Issue 2.0
2 4 6
3JK Issue 2.0
2 4 7
1 Outdoor Units
3JK Issue 2.0
2 4 8
1 Outdoor Units
1.1 MPT-HC V2 Construction and Mounting
MPT-HC V2 is similar to MPT-HC from architecture standpoint and can
be used as spare part of the MPT-HC.
The differences vs MPT-HC are:
MPT-HC V2 can be natively Ethernet powered through a proprietary PFoE
MPT-HC V2 is capable to host external modules (RPS module or XPIC_RPS
module)
Two mechanical solutions are adopted.
3JK Issue 2.0
2 4 9
1 Outdoor Units
1.1 MPT-HC V2 Construction and Mounting [cont.]
MPT-HC V2 housing (6 GHz and 11 GHz to 38 GHz)
With embedded diplexer for cost optimisation (6 GHz and 11 GHz to
38 GHz), where the branching (diplexer) is internal to the MPT-HC V2
cabinet; this type of MPT-HC V2 is identified by one Logistical Item
only.
3JK Issue 2.0
2 4 10
1 Outdoor Units
1.1 MPT-HC V2 Construction and Mounting [cont.]
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 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.
3JK Issue 2.0
2 4 11
1 Outdoor Units
1.2 MPT-HC V2 Characteristics
4, 16, 32, 64, 128, 256 QAM Modulation support (Adaptive modulation)
L6, U6, 7, 8, 11, 13, 15, 18,
23, 26, 38 GHz
to interconnect the two MPT-HC V2 Cable to be used in 1+1 configuration
100 m with electrical cable
500 m with optical cable
Ethernet cable (Note 2)
> 200 m with cable diam. = 10.3 mm
< 200 m with cable diam. = 6.85 mm
Power Supply cable (Note 1)
Cable lenght
Note 1: The PS cable is used if the PFoE solution is not adopted.
Note 2: The Ethernet electrical cable is used with the PFoE solution.
3JK Issue 2.0
2 4 12
Blank Page
3JK Issue 2.0
2 4 13
3JK Issue 2.0
2 4 14
2.1 Installing the MPT-HC V2
MPT-HC V2 is designed for direct-mounting to a collar supplied with
direct-fit antennas. MPT-HC V2 can also be installed with standard
antennas using a remote-mount kit.
direct mounting of the two MPT-HC V2 to its antenna, or to support
direct mounting onto a remote-mounted coupler.
3JK Issue 2.0
2 4 15
2.2 MPT-HC V2 external connectors
Views of MPT-HC V2 with embedded diplexer (6 GHz and 11-38 GHz)
(1)
MPT-HC V2 basic
(2)
(3)
MPT-HC V2 equipped with XPIC-RPS module MPT-HC V2 equipped with RPS module
(2)
(3) (2)
(3)
(4)
(4)
(5)
RF interface for connection of antenna or coupler. Remove the plastic cover.
WARNING: A waterproofness tape is glued on the waveguide of the MPT-HC V2. It must never be
removed.
LC + Q-XCO RPS connector (Connection to a second MPT-HC V2
in 1+1)
(4)
Round proprietary XPIC connector (Connection to a second MPT-HC V2) (5)
LC + Q-XCO Optical Ethernet connection (3)
RJ45 + R2CT Connector for power supply cable or for PFoE
(Power Supply + Ethernet Traffic) cable
(2)
Waveguide RF interface for connection of antenna or coupler (1)
figure
WR137
6
WR75
11
WR62
13-15
WR42
18-26
38 FREQUENCY GHz ->
3JK Issue 2.0
2 4 16
2.2 MPT-HC V2 external connectors [cont.]
Views of MPT-HC V2 with embedded diplexer (7 GHz and 8 GHz)
MPT-HC V2 equipped with XPIC-RPS module MPT-HC V2 equipped with RPS module
(2)
(3)
MPT-HC V2 basic
(1)
(2)
(3)
(4)
(2)
(3)
(4)
(5)
RF interface for connection of antenna or coupler. Remove the plastic cover.
WARNING: A waterproofness tape is glued on the waveguide of the MPT-HC V2. It must never be
removed.
WR112
8
7 FREQUENCY GHz ->
LC + Q-XCO RPS connector (Connection to a second MPT-HC V2
in 1+1)
(4)
Round proprietary XPIC connector (Connection to a second MPT-HC V2) (5)
LC + Q-XCO Optical Ethernet connection (3)
RJ45 + R2CT Connector for power supply cable or for PFoE
(Power Supply + Ethernet Traffic) cable
(2)
Waveguide RF interface for connection of antenna or coupler (1)
figure
3JK Issue 2.0
2 4 17
voltmeter.
Connect a voltmeter to the MPT-HC V2 through the Light service kit cable.
-100 -90 -80 -70 -60 -50 -40 -30 -20 -10 RSL (dBm)
Measurement (with MPT-HC V2) Units
3JK Issue 2.0
2 4 18
MPT Service Cord
Connector usage:
(M1) LEMO connector, to be plugged into LEMO connector on MPT-HC V2/MPT-MC.
3JK Issue 2.0
2 4 19
Which modulations are supported in the MPT-HC V2?
Can the MPT-HC V2 be directly connected to the antenna?
3JK Issue 2.0
2 4 20
End of Module
MPT-HC V2 HW Architecture
3JK Issue 2.0
Module 5
MPT-MC HW Architecture
3JK Issue 2.0
Section 2
9500 MPR ETSI
3JK Issue 2.0
Functional Description MPT-MC HW Architecture
2 5 2
Blank Page
Marcoussis
2010-10-28 01
Document History
3JK Issue 2.0
2 5 3
Module Objectives
Describe the functionality of the MPT-MC.
3JK Issue 2.0
2 5 4
3JK Issue 2.0
2 5 5
Table of Contents
Page
1 Outdoor Units 7
1.1 MPT-MC Construction and Mounting 8
1.2 MPT-MC Characteristics 12
2.1 Installing the MPT-MC 14
2.2 7-8 GHz MPT-MC: integrated antenna (1+0) 15
2.3 6 and 11-38 GHz MPT-MC: integrated antenna (1+0) 16
2.4 7-8 GHz MPT-MC: integrated antenna (1+1) 17
2.5 6 and 11-38 GHz MPT-MC: integrated antenna (1+1) 18
2.6 MPT-MC: non-integrated antenna (1+0) 19
2.7 7-8 GHz MPT-MC: non-integrated antenna (1+1) 20
2.8 6 and 11-38 GHz MPT-MC: non-integrated antenna (1+1) 21
2.9 MPT-MC external connectors 22
Blank Page 27
End of Module 28
3JK Issue 2.0
2 5 6
3JK Issue 2.0
2 5 7
1 Outdoor Units
3JK Issue 2.0
2 5 8
1 Outdoor Units
1.1 MPT-MC Construction and Mounting
MPT-MC (Microwave Packet Transport) is a Microwave Equipment
capable to transport the Ethernet traffic over an RF radio channel.
The MPT-MC includes a waveguide antenna port, type-N female
connector for the DC connection, a maintenance connector (with
captive protection cap) for RSSI access, 1 electrical GE interface, 2 GE
optical interfaces (1 for data, 1 for for RPS) and a grounding stud.
The MPT-MC can be installed on an integrated antenna or on standard
poles, wall or pedestal mount, with an appropriate fastening system.
The MPT-MC (one or two depending on the configuration 1+0 or 1+1,
each one with a solar shield) incorporates the complete RF transceiver
and can be associated with an integrated or separate antenna.
The MPT-MC can be rapidly installed on standard poles with an
appropriate fastening system. The pole mounting is the same for 1+0 or
1+1 configurations from 6 to 38 GHz.
3JK Issue 2.0
2 5 9
1 Outdoor Units
1.1 MPT-MC Construction and Mounting [cont.]
Two mechanical solutions are adopted.
3JK Issue 2.0
2 5 10
1 Outdoor Units
6 and 11-38 GHz MPT-MC housing
With embedded diplexer for cost optimisation (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.
3JK Issue 2.0
2 5 11
1 Outdoor Units
7-8 GHz MPT-MC housing
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: the
BRANCHING assembly (containing the diplexer) and the RF TRANSCEIVER assembly (containing the RF
section); 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.
3JK Issue 2.0
2 5 12
1 Outdoor Units
1.2 MPT-MC Characteristics
4, 16, 32, 64, 128 QAM Modulation support (Adaptive modulation)
4, 16, 32, 64, 128 QAM Modulation support (Static modulation)
L6, U6, 7, 8, 11, 13, 15, 18,
23, 26, 38 GHz
100 m Ethernet cable (Power Feed over
Ethernet)
Cable lenght
3JK Issue 2.0
2 5 13
3JK Issue 2.0
2 5 14
2.1 Installing the MPT-MC
MPT-MC is designed for direct-mounting to a collar supplied with direct-
fit antennas. MPT-MC can also be installed with standard antennas using
a remote-mount kit.
direct mounting of the two MPT-MC to its antenna, or to support direct
Installation with integrated antenna
Installation with non-integrated antenna
3JK Issue 2.0
2 5 15
2.2 7-8 GHz MPT-MC: integrated antenna (1+0)
3JK Issue 2.0
2 5 16
2.3 6 and 11-38 GHz MPT-MC: integrated antenna (1+0)
3JK Issue 2.0
2 5 17
2.4 7-8 GHz MPT-MC: integrated antenna (1+1)
MAIN
MPT-MC
RF
COUPLER
3JK Issue 2.0
2 5 18
2.5 6 and 11-38 GHz MPT-MC: integrated antenna (1+1)
MAIN
MPT-MC
RF COUPLER
3JK Issue 2.0
2 5 19
2.6 MPT-MC: non-integrated antenna (1+0)
3JK Issue 2.0
2 5 20
2.7 7-8 GHz MPT-MC: non-integrated antenna (1+1)
PROTECTION
MPT-MC
RF COUPLER
3JK Issue 2.0
2 5 21
2.8 6 and 11-38 GHz MPT-MC: non-integrated antenna (1+1)
3JK Issue 2.0
2 5 22
2.9 MPT-MC external connectors
Views of MPT-MC with embedded diplexer (6 and 11-38 GHz)
(2)
Eth.
connection
RF
Connection
(1)
WARNING: A waterproofness tape is glued on the waveguide of the MPT-MC. It must never be removed.
(2) Ethernet electrical cable R2CT
R2CT Ethernet electrical cable (2)
waveguide RF interface for connection of antenna or coupler (1)
Connector Interface Ref. in figure
WR137
6
WR75
11
WR62
13-15
WR42
18-26
38 FREQUENCY GHz ->
3JK Issue 2.0
2 5 23
2.9 MPT-MC external connectors [cont.]
Views of MPT-MC with embedded diplexer (7 GHz and 8 GHz)
Eth. Elec.
Connect.
(2)
RF
Connection
(1)
WARNING: A waterproofness tape is glued on the waveguide of the MPT-MC. It must never be removed.
(2) Ethernet electrical cable R2CT
WR112
8
7 FREQUENCY GHz ->
R2CT Ethernet electrical cable (2)
waveguide RF interface for connection of antenna or coupler (1)
Connector Interface Ref. in figure
3JK Issue 2.0
2 5 24
voltmeter.
Connect a voltmeter to the MPT-MC through the Light service kit cable.
-100 -90 -80 -70 -60 -50 -40 -30 -20 -10 RSL (dBm)
Measurement (with MPT-MC) Units
3JK Issue 2.0
2 5 25
MPT Service Cord
Connector usage:
(M1) LEMO connector, to be plugged into LEMO connector on MPT-HC/MPT-MC.
3JK Issue 2.0
2 5 26
Which modulations are supported in the MPT-MC?
Can the MPT-MC be directly connected to the antenna?
3JK Issue 2.0
2 5 27
Blank Page
3JK Issue 2.0
2 5 28
End of Module
MPT-MC HW Architecture
3JK Issue 2.0
Module 6
MSS Terminal HW Architecture
3JK Issue 2.0
Section 2
9500 MPR ETSI
3JK Issue 2.0
Functional Description MSS Terminal HW Architecture
2 6 2
Blank Page
Marcoussis
2010-07-01 01
Document History
3JK Issue 2.0
2 6 3
Module Objectives
Describe the functionality of each function of the MSS-1c.
3JK Issue 2.0
2 6 4
3JK Issue 2.0
2 6 5
Table of Contents
Page
1 MSS-1c Indoor Unit 7
1.1 MSS-1C 8
1.2 MSS Access Block Diagram 10
1.3 MSS-1c Features 11
1.4 MSS-1c Front and Rear Views 14
1.5 MSS-1c and Fan Unit 15
1.6 MSS-1c to MPT Interconnection 16
2 Distributors 21
2.1 Integrated DDF 22
2.2 Alternative Distributor Subracks 23
2.3 E1 SFP Modules 26
End of Module 28
3JK Issue 2.0
2 6 6
3JK Issue 2.0
2 6 7
1 MSS-1c Indoor Unit
3JK Issue 2.0
2 6 8
1.1 MSS-1C
The MSS-1c provides user port interface, cross-connection and switching
management.
The cross-connection matrix implements all the cross-connections between the
User ports (4 Ethernet ports and 10 E1 or 16 E1 streams according to the
hardware variant) and the Radio port. The matrix is a standard Ethernet
switch, based on VLAN, assigned by the MCT.
The 10xE1 enter the LIU and then the IWF, which manages the
encapsulation/reconstruction of PDH data to/from standard Ethernet packets
and sends/receives standard Ethernet packets to/from the Ethernet switch.
The Radio Interface interfaces the MPT-HC or the MPT-MC. The radio interface
is a standard GbEth interface electrical for MPT-MC, electrical or optical for
MPT-HC. It sends/receives standard Ethernet packets to/from the Ethernet
switch.
In case of electrical radio interface, on the same cable is also sent the power
supply for the MPT by using the Power Feed over Ethernet (PFoE) function.
Note: Two variants of MSS-1c are available:
MSS-1c providing 10E1 and 4 User ethernet ports
MSS-1c 16E1 providing 16E1 and 4 User Ethernet ports. This version is HW ready to manage up to 2 STM-
1 frames (instead of 2 Ethernet ports) not supported by the current SW Release
3JK Issue 2.0
2 6 9
2xGE user ports
Optical or electrical SFP
1.1 MSS-1C [cont.]
2x NMS
Ports RJ45
Local CT
RJ45
2x 10/100/1000 BaseT
User ports
HouseKeeping
RJ45
E1s
2x Sub-D 37 pins
2x MPT connections
RJ45 Ethernet Powering
2x MPT connections
Optical SFP
Power Supply
3JK Issue 2.0
2 6 10
1.2 MSS Access Block Diagram
3JK Issue 2.0
2 6 11
1.3 MSS-1c Features
More radio and site scalability and flexibility for installation teams:
Limited need for factory presetting channel frequency or bandwidth
Supports cellular mobile networks, and microcellular network back and
common carrier, private carrier and data networks, and utility haul
applications.
2G, 2.5G, and 3G network compatible
Outdoor Unit capacity and modulation independent
Outdoor Unit can support either split-mount and full-outdoor architecture
with the same hardware
Flexible aggregate capacity sharing between E1 and Ethernet
Adaptive packet transport that improves performance for priority services
Output power agility
ATPC
Adaptive Modulation
Packet-based internal cross-connect
TDM MEF8 encapsulation
Electrical GE interfaces
Software-based configuration
High Switching Capacity
3JK Issue 2.0
2 6 12
1) Line Side loopback: this loopback routes data from the output of the Tx Data
Awareness block (after compression) to the input of the Rx data awareness
(decompression).
This is an internal loopback. It is a Loop and Continue.
It is possible to enable this loopback only at aggregate level.
When this loopback is activated the behavior is the following:
TDM2TDM and TDM2ETH flows are forwarded back to MSS-1c with source and
destination MAC address swapped. For TDM2ETH flows the loopback works only
if the ECID Tx and ECID Rx are the same. In case of ECID Tx different from
ECID Rx the loopback doesn't work.
Generic Ethernet flows are dropped. (This includes the ETH2ETH flows).
1.3 MSS-1c Features [cont.]
Loopbacks with MPT
3JK Issue 2.0
2 6 13
2) Radio facing loopback: remote loopback allows an over-the-air loopback test to
be performed when the modem is operating in a continuous mode.
This is a line external loopback and connects the Receive data interface to the
Transmit data interface. This loopback is a Loop and Continue.
It is possible to enable this loopback only at aggregate level.
When this loop is enabled the expected behavior is the following:
TDM2TDM and TDM2ETH flows are looped back with source and destination MAC
address swapped. For TDM2ETH flows the loopback works only if the ECID Tx
and ECID Rx are the same. In case of ECID Tx different from ECID Rx the
loopback doesn't work.
Generic Ethernet flows are dropped. (This includes the ETH2ETH flows).
1.3 MSS-1c Features [cont.]
Loopbacks with MPT [cont.]
3JK Issue 2.0
2 6 14
1.4 MSS-1c Front and Rear Views
MSS-1c Front View
MSS-1c Rear View
See the notes below
(9-16) (*)
(*) Depending on the MSS-1c variant.
Note 1: To use the User Ethernet Ports 3 and 4 an SFP plug-in (electrical or optical) must be installed.
Note 2: The meaning of the six LEDs is:
LED M: Major Alarm (red)
LED m: Minor Alarm (red) (not supported in the current release: permanently OFF)
LED W: Warning (yellow) (not supported in the current release: permanently OFF)
LED MPT1: MPT Status (green/red/yellow)
LED MPT2: not supported
LED A: Abnormal condition (yellow)
LED A is ON in the following conditions: Tx Power muted by operator
ACM frozen by operator
MPT loopback active
LED MPT1 can be:
GREEN: MPT is emitting power as expected according the known configuration
YELLOW: MPT is not emitting power due to a forced Squelch condition
RED: MPT is ABNORMALLY emitting power
SWITCHED OFF: MPT is not emitting power according with the known configuration
At start-up the MSS-1c:
lights on all the alarm LEDs (Major, Minor, Warning and Abnormal)
lights on the MPT LED as yellow, then this LED will be GREEN, RED or YELLOW, as explained above.
3JK Issue 2.0
2 6 15
1.5 MSS-1c and Fan Unit
An optional Fan unit must be used to dissipate the MSS-1c
in special case when the ambient temperature is > +50C.
The MSS-1c and the Fan unit are mounted on a bracket compatible with 19" rack.
Height is 1.3U.
The Fan unit is powered by the MSS-1c with a cable placed on the rear side. The
cable is provided with the Fan unit.
The Fan unit includes two fans.
One bi-color LED on the front panel gives the status of the Fan unit:
- Fans alarm = OFF <-> LED = green
Fans alarm = ON <-> LED = red
Note:
Installation position: the MSS-1c on the right and the Fan unit on the left.
3JK Issue 2.0
2 6 16
1.6 MSS-1c to MPT Interconnection
MPT-HC electrical connection (up to 100m)
One electrical Ethernet cable connects the MSS-1c to its MPT-HC.
The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45
tool (1AD160490001).
Note: With the MPT-HC the Power Extractor must be installed close to the MPT-HC. In this case the
interconnection between the MSS-1c and the MPT-HC is made with a single electrical Ethernet cable by
using the Power Feed over Ethernet (Ethernet traffic and Power Supply on the same cable). The Power
Extractor then separates the Power Supply from the Ethernet traffic, which are separately send to the
MPT-HC.
3JK Issue 2.0
2 6 17
1.6 MSS-1c to MPT Interconnection [cont.]
MPT-HC optical connection (up to 350m)
One optical Ethernet cable connects the MSS-1c to its MPT-HC.
A coaxial cable connects the MPT-HC to the MSS-1c or to Station battery.
3JK Issue 2.0
2 6 18
MPT-HC V2 electrical connection (up to 100m)
One electrical Ethernet cable connects the MSS-1c to its MPT-HC V2.
The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool
(1AD160490001).
3JK Issue 2.0
2 6 19
MPT-HC V2 optical connection
(optical cable + power
supply cable to MSS-1c)
(optical cable + power supply
cable to Station battery)
(Note 2)
Two cables connect the MSS-1c to its MPT-HC V2:
HC V2.
Note: A special adapter cord must be connected to the coaxial cable on the MPT-HC V2.
Note 2: MPT-HC must be connected to a fuse or a breaker on a customer power distribution box. The
recommended value is 3 Amps.
3JK Issue 2.0
2 6 20
MPT-MC optical connection (up to 100m)
One electrical Ethernet cable connects the MSS-1c to its MPT-MC.
The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45
tool (1AD160490001).
3JK Issue 2.0
2 6 21
2 Distributors
3JK Issue 2.0
2 6 22
2 Distributors
2.1 Integrated DDF
The integrated DDF are mounted in the MSS rack and support the
connectors of the tributary cables.
There is also a 1U version (non-EMC)
Connector support 1.6/5.6 75 ohm Panel 1U
3JK Issue 2.0
2 6 23
2 Distributors
2.2 Alternative Distributor Subracks
They are an alternative to the previous cables, and combine protection
and distribution
They are connected to MSS with:
- one SCSI68-SCSI68 cord in 16 E1 1+0 up to
- four SCSI68-SCSI68 cords in 32 E1 1+1
available in 1.0/2.3 , RJ45 , 1.6/5.6 , BNC
(these available Distributor subracks are shown in the next pages)
3JK Issue 2.0
2 6 24
2 Distributors
2.2 Alternative Distributor Subracks [cont.]
Protection Panel 32E1 SCSI 68 - 1.0/2.3 75 ohm (Front/Rear)
Protection Panel RJ45 120 ohm (Front/Rear)
3JK Issue 2.0
2 6 25
2 Distributors
2.2 Alternative Distributor Subracks [cont.]
Protection Panel 32E1 SCSI 68 - 1.6/5.6 75 ohm (Front)
Protection Panel 32E1 BNC 75 ohm (Front)
3JK Issue 2.0
2 6 26
2 Distributors
2.3 E1 SFP Modules
various cords are available:
cord RJ45 plug - free 120 ohms
cord RJ45 plug - 2 x RJ45 plugs
cord RJ45 plug - 4 x coax free
Y protection cord RJ45
3JK Issue 2.0
2 6 27
How many E1 streams are available on the front panel
of the PDH access function ?
How many TMN accesses are available on the front
panel of the MSS-1c subrack ?
3JK Issue 2.0
2 6 28
End of Module
MSS Terminal HW Architecture
@@COURSENAME - Page 1
@@COURSENAME
@@PRODUCT
1
Last But One Page
@@COURSENAME - Page 2
Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent

9500MPR R. 3.1 Description

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

9500MPR R. 3.1 Description

Загружено:

Авторское право:

Доступные форматы

9500MPR (Microwave Packet Radio) ETSI R 3.

Section 1 Module 1 Page 1

Вам также может понравиться