Figure 90. E1 Traffic - Alcatel-Lucent 9500 MPR User Manual

Indoor: mss-8/mss-4 + outdoor: odu300 / mpt-hc / mpthc v2 / mpt-mc
Hide thumbs Also See for 9500 MPR:
Table of Contents

Advertisement

2.8.16.2 TDM2Eth
E1 traffic both internal and external to 9500 MPR-E equipment.
E1
BTS
E1
BTS
Flow Id present (user defined)
All the parameters must be configured compliant with the MEF8 standard
Adaptive or differential clock recovery supported
Bandwidth guaranteed (according to QoS o Highest Queue Priority association)
Destination MAC added before going into whole network (MEF8 compliant)
Only one of the IWFs belongs to 9500 MPR-E and the packets are supposed to exit the 9500 MPR-E
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: is fixed to 256 bytes
ECID: provisioned by ECT/NMS, 2 different values may be used for each direction (ECID = Emulated
Circuit Identifier)
TDM clock source is provisioned by ECT/NMS: clock recovery adaptive, clock recovery differential,
clock loopback (TDM line in)
Flow Id is provisioned by ECT/NMS (One Vlan is assigned to each bi-directional circuit emulated E1
flow)
For this case the expected latency for 1 hop is 3.5 msec for 256 bytes.
User Manual
Product information and planning
E1
BTS

Figure 90. E1 Traffic

PSN
PSN
Eth
Eth
3DB18809AAAA Issue 1
E1
BSC
9500 MPR Rel. 3.1
181/980

Advertisement

Table of Contents
loading

Table of Contents