Filter
Top Products
ADCP-75-192 • Issue 2 • June 2007
Page 20
© 2007, ADC Telecommunications, Inc.
In each of the simulcasted RANs, the RUC module receives the pathtrace string into its FPGA
from one of its two DIF input connections. The RUC HCP then reports the received pathtrace
strings in its MIB for use by tenant processing and other higher-level processes.
Figure 9. Tracing Pathtrace, Two Tenants
2.4.4 Pathtrace Reverse Transmission
The RDC is the originator of the pathtrace string in the reverse paths of the system. However, it
is desirable to maintain continuity between the forward and reverse pathtrace strings. To
manage this, the Pathtrace Process that runs in the RAN CPUs is responsible for reading
pathtrace strings from the RUC MIB, parsing out the Tenant ID sub-strings from the pathtrace
strings, and writing the Tenant IDs into the MIBs of the RDCs that are associated with the
RUCs.
The RDC HCP creates up to two new pathtrace strings (primary/diversity(if present)) starting
with the Tenant ID that was provided in its MIB by the Pathtrace Process. The RDC HCP
appends its own CPU IP Address to the pathtrace strings, and then appends the primary/
diversity flags (“P” or “D”). Finally, the RDC transmits the pathtrace strings out on up to two
outputs. The pathtrace strings are then transmitted back to the Hub reverse modules belonging
to this tenant.
FSC
T1
RSC
T1
HDC 1
T1
HDC 2
T1
HUC
T1
1
5
6
P
P
D
D
BIM
T1
P
D
10
9
FSC
T2
RSC
T2
HDC 1
T2
RUC
T1/T2
RDC
T1
P
D
RDC
T2
HDC 2
T2
HUC
T2
3
7
8
P
P
D
D
BIM
T2
P
D
10
9
MUX
ADD 3
MUX
ADD 4
DROP 1
DROP 2
DROP 3
DROP 4
DROP 3
DROP 4
FIC
SIF
FIC
SIF
Operator setup at
hubmaster through
BTS Connection MIB.
Set at node level by
HUB RF Connection MIB.
PATH TRACE CONTENTS
Tenant,BTS#,sector,band,IP_of_FSC
Tenant,BTS#,sector,band,IP_of_RDC,P
Tenant,BTS#,sector,band,IP_of_RDC,D
LEGEND
ADD ‘n’
DROP ‘x’
DROP ‘n’
ADD ‘x’
P
D
ADD 1
ADD 2
ADD 3
ADD 4
P.T.
HLP
Digital Rear I/O port
RF SMA (no PT)
DIF, Tenant 2
DIF, Tenant 1
Set by Software
Optical link
7
21947-A
HUB
RAN