ADCP-75-192 Issue 1 December 2005 Digivance CXD Multi-Band Distributed Antenna System Operation Manual 1343155 Rev A
ADCP-75-192 Issue 1 December 2005 Digivance CXD Multi-Band Distributed Antenna System Operation Manual 1343155 Rev A
ADCP-75-192 • Issue 1 • December 2005 • Preface COPYRIGHT 2005, ADC Telecommunications, Inc. All Rights Reserved Printed in the U.S.A. REVISION HISTORY ISSUE DATE Issue 1 12/2005 REASON FOR CHANGE Original release LIST OF CHANGES The technical changes incorporated into this issue are listed below. SECTION IDENTIFIER - - DESCRIPTION OF CHANGE Original release TRADEMARK INFORMATION ADC and Digivance are registered trademarks of ADC Telecommunications, Inc.
ADCP-75-192 • Issue 1 • December 2005 • Preface TABLE OF CONTENTS Content Page FRONT MATTER ABOUT THIS MANUAL ...................................................................... vii RELATED PUBLICATIONS .................................................................... vii ADMONISHMENTS ....................................................................... viii GENERAL SAFETY PRECAUTIONS.............................................................. viii SAVE WORKING DISTANCES ......................
ADCP-75-192 • Issue 1 • December 2005 • Preface TABLE OF CONTENTS Content 7 Page 6.1 Full Band Hub Down Converter (FBHDC) ............................................. 2-17 6.2 Forward Simulcast Card (FSC) .................................................... 2-18 6.3 Hub Upconverter Card (HUC) ..................................................... 2-19 6.4 Reverse Simulcast Card (RSC) .................................................... 2-20 6.5 Hub Reference Module (HRM) 6.6 Ethernet Hub .....
ADCP-75-192 • Issue 1 • December 2005 • Preface TABLE OF CONTENTS Content Page 7.14 Enabling / Disabling RAN slots.................................................... 3-15 7.15 Forward/Reverse Target Delay .................................................... 3-16 7.16 FSC Attenuator Offsets ......................................................... 3-16 7.17 Target Simulcast Degree........................................................ 3-16 7.18 Module Attenuators .........................................
ADCP-75-192 • Issue 1 • December 2005 • Preface TABLE OF CONTENTS Content Page 7.2 Restore..................................................................... 5-5 7.3 Adding/Removing SNMP Traps ..................................................... 5-6 8 UPDATING SPARE CPUS ............................................................... 5-6 9 MIB EXTRACTION .................................................................... 5-7 SECTION 6 AUTONOMOUS SOFTWARE FUNCTIONALITY 1 INTRODUCTION .........
ADCP-75-192 • Issue 1 • December 2005 • Preface ABOUT THIS MANUAL This Operation Manual provides the following information: • An overview of the Digivance CXD system. • A description of the basic system components including the Digital Chassis, RF Chassis, RAN, CPU, STF2, FBHDC, HUC, SIF, FSC, RSC, RDC, RUC, APEC, DPEC, cPCI Power Supplies, and RFA. • Procedures for turning-up the system and verifying that the system is functioning properly.
ADCP-75-192 • Issue 1 • December 2005 • Preface ADMONISHMENTS Important safety admonishments are used throughout this manual to warn of possible hazards to persons or equipment. An admonishment identifies a possible hazard and then explains what may happen if the hazard is not avoided. The admonishments — in the form of Dangers, Warnings, and Cautions — must be followed at all times.
ADCP-75-192 • Issue 1 • December 2005 • Preface Caution This system is a RF Transmitter and continuously emits RF energy. Maintain 3 foot minimum clearance from the antenna while the system is operating. Wherever possible, shut down the RAN before servicing the antenna. Caution: Always allow sufficient fiber length to permit routing of patch cords and pigtails without severe bends. Fiber optic patch cords or pigtails may be permanently damaged if bent or curved to a radius of less than 2 inches (50 mm).
ADCP-75-192 • Issue 1 • December 2005 • Preface In order to maintain compliance with FCC regulations, shielded cables must be used with this equipment. Operation with non-approved equipment or unshielded cables is likely to result in interference to radio & television reception. ETL: This equipment complies with ANSI/UL 60950-1 Information Technology Equipment. This equipment provides the degree of protection specified by IP24 as defined in IEC Publication 529. Ethernet signals not for outside plant use.
ADCP-75-192 • Issue 1 • December 2005 • Preface GUI HCP HLP HRM HUC IEL LED MHz MPE NIPR/S NMS NOC Node PA PC PCS PDU PPS RAN RDC RF RMA RSC RUC RX SIF SMR STF TX UL VAC VDC VSWR WECO WDM Graphical User Interface Hardware Control Process High Level Process Hub Reference Module Hub Up Converter Injection/Extraction Locking Light Emitting Diode Mega Hertz Maximum Permissible Exposure Network IP Receiver/Sender Network Management System Network Operations Center Any CPU in the Digivance CXD system Power Ampl
ADCP-75-192 • Issue 1 • December 2005 • Preface Blank Page xii 2005, ADC Telecommunications, Inc.
ADCP-75-192 • Issue 1• December 2005 • Section 1: Overview SECTION 1: OVERVIEW Content 1 INTRODUCTION .................................................................... 1-1 2 DIGIVANCE CXD SYSTEM OVERVIEW ...................................................... 1-1 3 1 Page 2.1 Basic Components ............................................................. 1-2 2.2 General Description ............................................................ 1-2 2.3 Local Service Interface ....................
ADCP-75-192 • Issue 1 • December 2005 • Section 1: Overview 2.1 Basic Components Figure 1-1 illustrates a Digivance system with RAN’s distributed over a desired geographical area, connected back to a Wireless Service Provider (WSP) base station(s) at a Hub locale. The illustration shows a dual-band SMR A and SMR B configuration with variable digital simulcasting as a reference.
ADCP-75-192 • Issue 1• December 2005 • Section 1: Overview In the reverse path, the antenna receives RF signals from a mobile and sends those signals into the RFA which contains a diplexer and Low Noise Amplifier. The output of the RFA is connected the RAN Down Converter (RDC) which down converts the RF back to IF and digitizes the signals. The DIF signals are passed to the SIF, which sends digital optical signals from the RAN to the HUB SIF.
ADCP-75-192 • Issue 1 • December 2005 • Section 1: Overview The Digivance CXD Element Management System is a Web based system that provides the various control and monitoring functions required for local management of each CXD system. The user interface into the EMS is a PC-type laptop computer loaded with a standard Web browser. The EMS is resident on the Hubmaster CPU and is accessible through an Ethernet connection. Operation is effected through the EMS Graphical User Interface (GUI).
ADCP-75-192 • Issue 1• December 2005 • Section 1: Overview 3.2 Control and Monitoring Software The Digivance CXD EMS or customer supplied NMS using the Digivance CXD/NXD SNMP Agent is used to provision and configure the system for operation. This includes initializing the system, setting up the Hub and RAN element identification schemes, tenant processing, setting alarm thresholds, and setting forward and reverse path RF gain adjustments.
ADCP-75-192 • Issue 1 • December 2005 • Section 1: Overview Table 1-2. Digital Chassis 4:1 Simulcast Power Consumption MODULE # OF MODULES POWER Digital Chassis 1 76.0 Watts CPU 1 20.5 Watts STF2 1 3.5 Watts SIF 4 15.5 Watts RSC 1 9.0 Watts Total Power 170 Watts Table 1-3 lists the typical power consumption of the respective modules for the RF Chassis. Table 1-3. Digital Chassis Power Consumption MODULE POWER RF Chassis 55.0 Watts FBHDC 11.0 Watts HUC 8.0 Watts FSC 13.
ADCP-75-192 • Issue 1• December 2005 • Section 1: Overview The RAN is powered by 120 or 240 Vac (50 or 60 Hz) and must be hard-wired to the AC power source through a breaker box. The RAN is pre-wired for 120 VAC operation but can be converted to 240 VAC operation if required. On an optional basis, a back-up battery kit is available for the RAN. The battery-backup system powers the RAN if the AC power source is disconnected or fails. 3.4.
ADCP-75-192 • Issue 1 • December 2005 • Section 1: Overview 3.4.
ADCP-75-192 • Issue 1• December 2005 • Section 1: Overview 4. Base Station Interface Module (BIM). The BIM is a multi-port transition module used to interface with the Tenant’s base station sector. The BIM accepts either duplexed or nonduplexed RF from the base station sector and provides the Digivance CXD-Hub RF section separate transmit and receive paths. 5. Ethernet hub with twenty four (24) ports. 6. -48 VDC Power Distribution Unit. 7. Hub Reference Module (HRM).
ADCP-75-192 • Issue 1 • December 2005 • Section 1: Overview 3.6.4 System Interface (STF2) The System Interface (STF2) module, using four I2C busses, provides the ability to communicate between the CPU and other modules. The STF2 also communicates with the GPS modules found both in the Master Hub Reference Module and internal to the RAN STF2. In the HUB, the STF2 communicates with chassis fans for monitoring purposes.
ADCP-75-192 • Issue 1• December 2005 • Section 1: Overview 1. Interface to a low power forward BTS RF path. 2. Handles duplexed and non-duplexed signals. 3. Gain adjust for optional reverse path configurations. The BIM is controlled via an I2C connection from its respective CPU. 3.6.11 Hub Reference Module (HRM) The HRM generates the RF reference and fiber clocking for distribution within the Hub.
ADCP-75-192 • Issue 1 • December 2005 • Section 1: Overview 3.7.2 System Interface (STF2) The STF2 module provides the ability to communicate between the CPU and other modules (RDC, RUC, RFA interface controller) using four I2C busses. The STF2 also contains the GPS module. 3.7.3 Sonet Interface (SIF) The SIF module provides the optical interface between the Hub and RAN’s. The SIF has an optical transceiver module installed that provides the optical transmit and receive functions.
ADCP-75-192 • Issue 1• December 2005 • Section 1: Overview 3.7.9 DC Power Entry Card (DPEC) The DPEC is used to distribute DC power to the cPCI power supplies in the RAN when supporting battery backup. It has a built in EMI filter and fuse holder and provides an access point for fan monitoring and control. 3.7.10 CompactPCI RAN Power Supply (cPCI P/S) The CompactPCI (cPCI) Power Supplies provide +/-12V, 5V and 3.3 V DC power to the cPCI backplane for use by the RAN modules.
ADCP-75-192 • Issue 1 • December 2005 • Section 1: Overview • VSWR (all bands): 1.5:1 typ, 1.65:1 max • Maximum power input: 200W (average) 1000W (peak) • Passive Intermodulation Distortion: -153dBc (maximum) 3.8 Communication Interfaces 3.8.1 I2C I2C is a bi-directional serial bus that provides a simple, efficient method of data exchange between devices. It is used for the board level communications protocol. I2C interfaces are used for communication to the following modules: 1.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description SECTION 2: DESCRIPTION Content 1 Page INTRODUCTION .................................................................... 2-1 2 DIGITAL CHASSIS ................................................................... 2-2 3 RF CHASSIS....................................................................... 2-5 4 RADIO ACCESS NODE (RAN) ........................................................... 2-9 4.1 5 6 7 ELEMENTS COMMON TO HUB AND RAN ...
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description 2 DIGITAL CHASSIS The Digivance Digital Chassis is a rack-mounted cPCI shelf capable of housing 8 industry standard cPCI circuit card modules. The Digital Chassis houses cooling fans and specific modules designed for use in the Digivance CXD system. The backplane of the Digital Chassis provides for distribution of signals between modules including the reference clock, communications, control and data signals.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description ( 1) M O D ULE A N D P O R T S T A T US IN D IC A T O R S ( 3 ) 5 / 6 D IF I/ O ( 3 - 8 ) ( 2 ) 7 / 8 D IF I/ O ( 3 - 8 ) ( 11) - 4 8 VD C IN P UT ( 10 ) 12 VD C O UT P UT (6 ) 1 HZ R EF ER EN C E ( 4 ) 3 / 4 D IF I/ O ( 3 - 8 ) ( 9 ) F A N S T A C H O M E T E R IN P UT S ( 5 ) 1/ 2 D IF I/ O ( 3 - 8 ) ( 8 ) 9 / 10 D IF O UT P UT ( 3 - 8 ) ( 7 ) I2 C B US S E S Figure 2-2. Digital Chassis – Rear Connectors Table 2-1.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description The main purpose of the Module/Port status indicators shown in Figure 2-3 is to provide the user instant feedback on the success or failure of a new connection. It also provides path status to aid in troubleshooting missing or degraded connections. The references for the back connectors of the Digital Chassis are shown in the Table 2-2.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Figure 2-4 shows an empty Digital Chassis from the front. Slots on the left are numbered from 1 to 8 starting at the bottom of the chassis. Slots on the right of the chassis are used for the cPCI power supplies used to power the chassis and modules and the cPCI fan assembly. Mounting of modules and circuit cards into the Digital Chassis should be done in accordance with Table 2-3. Figure 2-4. Digital Chassis - Front Table 2-3.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Figure 2-5 Digivance CXD RF Chassis Modules and circuit cards are placed into the RF Chassis and are mated using standard cPCI connectors on the backplane of the chassis. Data and signals are transported over busses on the backplane of the chassis to other modules and ports on the backside of the chassis.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description ( 2 ) F S C 2 D IF O U T P UT 1- 8 ( 1) MO D U LE A ND P O R T S T A T U S IN D IC AT O R S ( 4 ) R E F E R E N CE /C LO C K ( 3 ) HUC 2 D IF IN P U T ( 5 ) I2 C D AIS Y C HAIN ( 5 - 8 ) ( 6 ) I2 C DA IS Y C HA IN ( 1- 4 ) ( 11) - 4 8 V D C IN P U T ( 10 ) 12 V D C O U T P U T ( 9 ) F S C 1 DIF O U T P UT S ( 1- 8 ) ( 8 ) F AN S T AC HO ME T E R O UT P U T S ( 7 ) HU C 1 D IF IN P UT Figure 2-6.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Figure 2-7 shows the RF Chassis viewed from the rear. The references for the back connector of the RF Chassis are shown in Table 2-5. ( 3 ) R E F E R E N C E LE D ( 4 ) C LO C K LE D ( 2 ) F S C 2 O UT P UT LE D ( 1) H UC 2 P R I/ D IV LE D ( 5 ) H UC 1 P R I/ D IV LE D ( 6 ) F S C 1 OUT P UT LE D Figure 2-7. RF Chassis – Rear Indicators Table 2-5. RF Chassis References – Rear Indicators REF No.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Figure 2-8. RF Chassis – Front Table 2-6. RF Chassis Slot Assignments SLOT MODULE 8 7 FSC 6 FBHDC 5 HUC 4 4 3 FSC 2 FBHDC 1 HUC RADIO ACCESS NODE (RAN) The Radio Access Node (RAN) is the remote hardware that transmits and receives radio signals. It consists of a cabinet, RAN Chassis, a Central Processing Unit (CPU), a System Interface (STF2), a Sonet Interface (SIF), RAN Down Converter (RDC or RDC2), RAN Up Converter (RUC2.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description 4.1 RAN cabinet The CXD RAN standard and extended cabinets, shown in Figure 2-9 and Figure 2-10, are NEMA-3R enclosures (with removable dust filter) that provides the following basic functions: • Houses the various electronic modules including the following RAN Chassis and Backplane − Central Processing Unit (CPU) − System Interface (STF2) − Sonet Interface (SIF) − RAN Down Converter (RDC or RDC2) − RAN Up Converter (RUC2.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Figure 2-10. CXD RAN Extended Cabinet • Provides a point for terminating the coaxial antenna cable, the fiber optic cable, the AC power cable, and ground cable. • Provides AC power surge protection • Provides lightning protection • Provides limited storage for fiber optic pigtails. The CXD RAN cabinets are weather-tight but contact with salt-air mist should be avoided as it may degrade the MTBF of the product.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Figure 2-11. Hubmaster and Slave Block Diagram There is one Hubmaster (HM) CPU per system. All CPUs at the Hub, with the exception of the Hubmaster CPU, are Slave CPUs. The CPU used in the RAN is also a Slave CPU to the Hubmaster CPU. The CPU is shown in Figure 2-12. The references for the CPU are shown in Table 2-7.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Table 2-7. CPU User Interface REF No. USER INTERFACE DESIGNATION DEVICE FUNCTIONAL DESCRIPTION 1 Universal Serial Bus Connector USB connector Front panel Input/Output for keyboard connectivity. 2 COM 1 Connector RJ-11C connector Front panel interface for COM1.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description ( 2 ) RE S E T S W IT CH ( 1) G P S LE D ( 3 ) S T AT US LE D 1 ( 4 ) S T AT US LE D 2 ( 15 ) T O W E R LIG HT ALARM CO NNE CT O R ( 5 ) DO O R ALARM CO NNE CT O R ( 6 ) G P S CO MMS CO NNE CT O R ( 7 ) RE CT IF IE R CO MMS CO NNE CT O R ( 14 ) G P S ANT E NNA CO NNE CT O R ( RAN O NLY) ( 8 ) I2 C CO MM LE D ( 9 ) I2 C E RRO R LE D ( 13 ) I2 C CO NNE CT O RS ( 10 ) F AULT LE D ( 12 ) P O W E R LE D ( 11) HO T S W AP LE D Figure 2-13.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Table 2-8. STF2 User Interface, continued REF No. USER INTERFACE DESIGNATION DEVICE FUNCTIONAL DESCRIPTION 9 I2C Error LED’s Single-colored LED (Red) On each I2C RJ-45 connector. Status indicator turns red when no response on port. 10 Fault LED Single-colored LED (Red) Status indicator turns red when module has failed or upon startup until the module has completed initialization.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description The SIF module is able to support up to four independent 15 MHz Digital IF (DIF) data streams (15 MHz band blocks) consisting of either four (4) forward path signals and four (4) reverse path signals in a non-diversity configuration, or two (2) forward path signals and four (4) reverse path signals in a receive-diversity configuration. The references for the SIF are shown in Table 2-9. Table 2-9. SIF User Interface REF No.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Figure 2-15. SFP Optical Transceiver Module 6 HUB SPECIFIC MODULES This section describes the various controls and indicators for Hub specific modules. 6.1 Full Band Hub Down Converter (FBHDC) The Full Band Hub Down Converter (FBHDC), shown in Figure 2-16, down converts the forward RF carrier to an intermediate frequency (IF) that can be digitized. Each FBHDC can support up to 15 MHz of contiguous spectrum.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Table 2-10. FBHDC User Interface REF No. USER INTERFACE DESIGNATION DEVICE FUNCTIONAL DESCRIPTION 1 IF1 and Tx1 Connectors SMA Connector Connect to FSC and BIM, respectively. If direct connect is desired, supply -4dBm composite power to Tx1 (-7 dBm for iDEN). 2 IF2 and Tx2 Connectors SMA Connector Additional downlink path (see Ref(1)). 3 Fault LED Single-colored LED (Red) Status indicator turns red when module has failed.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description ( 1) E XP AN S IO N P O RT ( 2 ) IF CO N NE CT O R S 1- 8 ( 4 ) F AULT LE D ( 3 ) P O W E R LE D Figure 2-17. Forward Simulcast Card Table 2-11. FSC User Interface REF No.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description ( 1) P R IM A R Y P A T H LO C KE D LE D ( 6 ) D IVE R S IT Y P A T H LO C KED LE D ( 2 ) P R IM A R Y P A T H S M A C ON N E C TO R ( 5 ) D IVER S IT Y P A TH S M A C O N N E C TO R ( 3 ) F A ULT LED ( 4 ) P O WE R LE D Figure 2-18. HUC Module Table 2-12. HUC User Interface REF No.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description ( 1) D IF IN P UT LE D 1- 8 ( 2 ) D IF O UT P UT LE D 1- 4 ( 5 ) F A ULT LE D ( 4 ) P O WE R LE D ( 3 ) H O T S WA P LE D Figure 2-19. RSC Module The DIF input and output LEDs describe the status of the digital signal. The RSC defaults to using two 4:1 digital simulcast groups. To determine the relationship between the RSC channel LED number and the signal type, use the guidelines in Table 2-13. Table 2-13. RSC User Interface REF No.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Table 2-13. RSC User Interface, continued REF No. USER INTERFACE DESIGNATION DEVICE FUNCTIONAL DESCRIPTION 3 Hot Swap LED Single-colored LED (Blue) Status indicator turns blue when board can be hot swap extracted. 4 Power LED Single-colored LED (Green) Status indicator turns green when module has power. 5 Fault LED Single-colored LED (Red) Status indicator turns red when module has failed. 6.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description ( 1) G P S IN (2 ) GP S AUXILLARY ( 8 ) RS - 2 3 2 CO NNE CT O R ( 3 ) CLO CK T E S T P O INT S ( 7 ) 1 HZ LE D ( 4 ) F AULT LE D ( 6 ) P LL LO CK LE D ( 5 ) P O W E R LE D Figure 2-20. Hub Reference Module Front Panel Table 2-14. HRM Front Panel User Interface REF No. USER INTERFACE DESIGNATION DEVICE FUNCTIONAL DESCRIPTION 1 GPS Input Connector SMA connector Input of GPS antenna signal.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Table 2-15. HRM Rear Panel User Interface REF No. USER INTERFACE DESIGNATION DEVICE FUNCTIONAL DESCRIPTION 1 Clock Out (A1-8, B18) RJ-45 Sample clock, Reference clock, and 1PPS output connectors (x16) 2 Power LED Single-colored LED (Green) Status indicator turns green when module has power. 3 Fault LED Single-colored LED (Red) Status indicator turns red when module has failed.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description 6.7 BTS Interface Module (BIM) The Base Station Interface Module provides the following BTS interface functionality: • Interface to a low power forward BTS RF path. • Handles duplexed and non-duplexed signals. • Forward path gain adjustment. • Reverse path gain adjustment. The BIM, shown in Figure 2-23, is a 1RU module that mounts into the HUB Base Rack.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description The BIM is designed to support the desired interface to the wireless service provider BTS. The BIM can support all duplex or simplex configurations. The standard BIM input power level is low power; -10 to +26 dBm composite. A high power option can be ordered to support a BTS feed 42 to 47 dBm composite per connection. Dual receive and transmit diversity is also provided in the BIM. There are three typically configurations for the BIM Module.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description WSP Equipment CXD Hub Equipm ent -4 dBm composite (max) Tx TX1 FBHDC Test IF1 CH1 DIF Output (x8) FSC DAS Interface Equipment BTS Sector Fwd1D Receive Pri RxP Pri Out DIF Input Pri Rx0 BIM RxD HUC DIF Input Div Rx1 Receive Div Div Out Figure 2-25.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Table 2-18.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description 7 RADIO ACCESS NODE (RAN) SPECIFIC MODULES This section describes the various controls and indicators for RAN specific modules. 7.1 Ran Down Converter (RDC or RDC2) The RAN Down Converter (RDC), shown in Figure 2-28, takes RF signals from a primary and secondary antenna and down converts the signals into IF. Signals are input into the card over coax cable terminated with SMA connectors on to the front panel of the module.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description 7.2 Ran Up Converter (RUC2.X or RUC3) The RAN Up Converter (RUC), shown in Figure 2-29, takes IF signals from a DIF signal generated by a SIF and up converts the signals to RF. The RF outputs of the RUC are connected to the RFA’s using coax cable jumpers. The RUC is used to monitor and control the RFA and communicates over the provided cable using I2C. The references for the RUC user interface are shown in Table 2-20.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Table 2-20. RUC User Interface, continued REF No. USER INTERFACE DESIGNATION DEVICE FUNCTIONAL DESCRIPTION 7 PA CNTL 2/4 I2C flatpack Connector I2C Communications to RFA 8 PA CNTL 1/3 I2C flatpack Connector I2C Communications to RFA 7.3 AC Power Entry Controller The AC Power Entry Controller (APEC) is used for installations requiring AC power only. It has a 100-240 VAC input and has an EMI filter to condition the signal.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Table 2-21. APEC User Interface REF No. USER INTERFACE DESIGNATION DEVICE FUNCTIONAL DESCRIPTION 1 AC Power Input Connector 3-wire AC power cord connector Provides AC power into the cPCI chassis 2 Fan Power Connector 20 pin enclosed header connector Provides power to chassis and enclosure fans.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description ( 2 ) B AT T E RY DIS CO NNE CT S W IT CH ( 1) B AT T E R Y C O NNE C T O R ( 3 ) I2 C INT E RF ACE ( F UT URE ) ( 4 ) R F A ( AC ) IN P UT P O W E R C O NNE CT O R ( 9 ) F AN P O W E R CO NNE CT O R ( 5 ) D C INP U T P O W E R LE D ( 8 ) B AT T E RY P O W E R LE D ( 6 ) CHAS S IS F AN LE D ( 7 ) R AN F AN LE D Figure 2-31, DC Power Entry Controller (DPEC) Table 2-22. DPEC User Interface REF No.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description 7.5 CompactPCI Power Supply (cPCI P/S) 7.5.1 AC cPCI Power Supply The AC cPCI P/S distributes power to the CXD Ran Chassis cPCI modules. It is used in the RAN Chassis for applications requiring AC only (no battery backup option). The AC cPCI is shown in Figure 2-32 and the user reference is shown in Table 2-23. ( 1) P O WE R LE D ( 2 ) F A ULT LE D Figure 2-32. RAN Chassis AC cPCI Power Supply Table 2-23. AC cPCI P/S User Interface 7.5.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description ( 1) P O WE R LE D ( 2 ) F A ULT LE D Figure 2-33. RAN Chassis DC cPCI Power Supply Table 2-24. DC cPCI P/S User Interface REF No. USER INTERFACE DESIGNATION DEVICE FUNCTIONAL DESCRIPTION 1 Power LED Single-colored LED (Green) Status indicator turns green when power supply has power. 2 Alarm LED Single-colored LED (Yellow) Status indicator turns yellow when power supply has failed 7.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description The RFA consists of an electronic component circuit board assembly and fan assembly that are mounted within a sheet metal enclosure. The metal enclosure provides a mounting point for the electronic components and controls RF emissions. Except for the fan assembly, the electronic components are not user replaceable. All controls, indicators, and switches are mounted on the RFA front panel for easy access.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description ( 1) R F A F A NS ( 10 ) I2 C CO N N E CT O R ( 2 ) A C INP U T ( 9 ) P O W E R LE D ( 8 ) P A F AU LT LE D ( 7 ) AC F A U LT LE D (3 ) RF T X P O RT ( 6 ) 2 8 V D C C O NN E C T O R ( 4) RF RX P O RT ( 5 ) A NT E N N A C O N NE C T O R Figure 2-35. Single-Band 10 Watt RF Assembly Module Front Panel Table 2-25. Single-Band 10 Watt RFA User Interface REF No.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Table 2-25. Single-Band 10 Watt RFA User Interface, continued 7.6.2 REF No. USER INTERFACE DESIGNATION DEVICE FUNCTIONAL DESCRIPTION 6 28 VDC Connector DB-9 connector Connects to fan assembly in AC configuration. Connects to DPEC when battery backup is used.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Table 2-26. Dual-Band 10 Watt RFA User Interface 7.6.3 REF No.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description ( 1) RF A F ANS ( 2 ) ANT E NNA CO NNE CT O R ( 10 ) I2 C CO NNE CT O R ( 3 ) AC INP UT ( 4 ) RF T X1 P O RT ( 9 ) P O W E R LE D ( 5 ) RF RX1 P O RT ( 8 ) P A F AULT LE D ( 6 ) 2 8 VDC CO NNE CT O R ( 7 ) AC F AULT LE D Figure 2-37. Single-Band 20 Watt RF Assembly Module Front Panel Table 2-27. Single-Band 20 Watt RFA User Interface REF No.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description 7.7 Specifications The specifications for the Digivance CXD are provided in Table 2-28. All specifications apply after a five minute warm-up period. Table 2-28.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Table 2-28. Digivance CXD Specifications, continued PARAMETER Gain flatness Band flatness Channel flatness SPECIFICATION REMARKS ±2.0 dB across freq. Range ±1 dB variation across any 1.25 MHz channel Gain Variation ± 3 dB Over frequency, temperature, and unit-to-unit.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Table 2-28. Digivance CXD Specifications, continued PARAMETER SPECIFICATION Input IP3 -16 dBm Noise figure 800/850/900 MHz 1900 MHz 5 dB 6 dB Minimum RF output level REMARKS 10 dBm -5 dBm Absolute maximum Operational maximum Automatic Gain Limiting (AGC) Range Maximum input signals 25 dB -38 dBm Peak signal input Reverse path VSWR 2.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Table 2-28. Digivance CXD Specifications, continued PARAMETER SPECIFICATION Backplane connections RJ-45 Power Input ±48 VDC Power Consumption RF Chassis FBHDC HUC FSC 55.0 Watts 11.0 Watts 7.7 Watts 13.5 Watts REMARKS Floating Typical Fans and 12 VDC P/S Base Station Interface Module (BIM) Dimensions (HxWxD) 1.75 x 19.0 x 7.1 Inches 1.75 x 17.1 x 7.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Table 2-28.
ADCP-75-192 • Issue 1 • December 2005 • Section 2: Description Blank Page 2-46 2005, ADC Telecommunications, Inc.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup SECTION 3: NETWORK AND SYSTEM INSTALLATION AND SETUP Content Page 1 INTRODUCTION .................................................................... 3-2 2 NETWORKING OVERVIEW.............................................................. 3-2 3 NODE IDENTIFICATION SCHEMES ........................................................ 3-3 4 IDENTIFICATION USING THE NETWORK IP RECEIVER/SENDER SYSTEM ...............
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup 11 1 CONFIGURING THE HUB “SLAVE” AND RAN NODES............................................ 3-24 11.1 Managing The Hub Node MIB ..................................................... 3-24 11.2 Managing the RAN Node MIB ..................................................... 3-26 INTRODUCTION This section discusses the steps necessary to setup the Digivance CXD system communications and operating parameters.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup A CPU called the Hubmaster is a special Hub node that controls tenant processing for Digivance CXD nodes on its subnet. For a definition of tenant sectors, see Section 6.1. The Hubmaster also functions as a time server for a Digivance CXD subnet (using Network Timing Protocol), and can be set up to provide DHCP (Dynamic Host Configuration Protocol) and DNS (Domain Name Service) to its subnet as well.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup Table 3-1.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup • Ensure that FBHDC modules are connected to FSC modules. (See Hub Installation and Maintenance Manual for details) • An RF chassis in a Hub rack contains enough slots for 2 sets of tenant RF equipment, where a set of tenant RF equipment consists of one FSC, one HUC and up to two FBHDC’s.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup 6.2 BTS Connection MIB Within the Hubmaster node, the BTS Connection MIB is used to create new tenant base station sector instances (simply called "tenants" from here on) to be configured, monitored, and controlled in the Digivance CXD system.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup US1900D (4) - PCS band D US1900E (5) - PCS band E US1900F (6) - PCS band F US800AAPP (7) - Cellular A and A'' bands US800BBP (8) - Cellular B and B' bands US800AP (9) - Cellular A' band US800SMRA (10) – SMR 800 band (806-821/851-866MHz) US800SMRUpper (11) – SMR 800 band Extended (818-824/862-869MHz) US900SMRB(12) – SMR 900 band US1900G (13) - PCS band G The MIB field is: transceptBtsConnectionTable.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup transceptBtsConnectionTable.transceptBtsConnectionHdcXI2cBus and transceptBtsConnectionTable.transceptBtsConnectionHdcXI2cSlot, where X = 1 or 2. • The FBHDC module belonging to this tenant is cabled to a single FSC module, which is located in a chassis slot directly above the tenant's FBHDC module. Select the I2C Bus and Slot of the FSC module to that of its corresponding BIM. Set the I2C slot value to “2”.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup 6.2.9 Composite Mode The Digivance CXD default forward gain balance is called “composite mode”. In this mode, a composite RF signal will have gain of +42dB (Cell/SMR) and +45dBm (PCS) through the system. The maintainer is responsible for ensuring the desired signal level into the system. See Table 3-3 for sample input and output signal strengths: Table 3-3.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup • The Tenant ID sub-string is comprised of four particular pieces of information: Tenant Name, BTS ID, BTS Sector, and Tenant Band. These four pieces of information form the Tenant ID sub-string, where each piece of information is delimited by a single character (currently a colon ":"). • The IP Address sub-string indicates the IP Address of the CPU node that transmits the pathtrace string.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup Figure 3-2. Tracing Pathtrace, Two Tenants 6.3.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.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup In the Hub, the RSC module receives the pathtrace strings from several RDC’s into its FPGA from its DIF input connection. The RSC HCP reports the received input pathtrace strings in its MIB for use by higher-level processes, as described in sections below. The RSC has the added responsibility of determining the "majority inputs" to determine the most-prevalent input pathtrace based on Tenant ID sub-strings.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup 7 TENANT CONFIGURATION The Tenant OAM MIB is the primary interface for configuring the operating parameters of tenants in the Digivance CXD system. The Tenant OAM MIB is used exclusively at the Hubmaster node, where any changes made to operating parameters are validated and pushed down to the proper node(s) by Tenant processing. 7.1 Setting Protocol transceptTenantOAMTable.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup 7.6 Setting RAN Forward Gain Offset transceptTenantOAMTable.transceptTenantRanForwardGainOffsetX, where X = 1-8 The RAN Forward Gain Offset is a parameter in the Tenant OAM MIB that allows the target RAN Gains for this tenant to be adjusted. This effectively allows the cell coverage provided by a given RAN to be adjusted.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup 7.11 Using Tenant Mode transceptTenantOAMTable.transceptTenantMode Tenant Mode is a parameter in the Tenant OAM MIB that will allow the tenant to be put into a special mode such as "disabled", or "test",. This functionality is not currently supported in the Digivance CXD software. 7.12 Enabling / Disabling Delay Compensation transceptTenantOAMTable.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup 7.15 Enabling / Disabling RAN slots transceptTenantOAMTable.transceptTenantRanDisableX, where X = 1-8 The RAN paths belonging to a tenant can be disabled using the RAN Enable/Disable parameters of the Tenant OAM MIB. Doing so will disable the PA in the RAN. These MIB fields are enumerated types with values "Enabled" = 0, and "Disabled" = 1.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup 8 • TransceptTenantMoreAttenTable.transceptTenantRdcYAttenOffsetDiversity - Y = RAN 1-8. • TransceptTenantMoreAttenTable.transceptTenantBimForwardAttenZOffset - Z = Path 1-2. • TransceptTenantMoreAttenTable.transceptTenantHdcChXAttenOffset - X = Channel 1-8.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup 8.2 Bracketing of Lost RANs When a RAN CPU is removed from the network, or if tenant processing is unable to communicate with one of its RANs, then that RAN ID in the Hostname table is bracketed. For example hostname would be reported as [hostname]. In addition, the RAN ID in the Address table is also reported in a different fashion when a RAN is "lost".
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup There are two main ways to access the output of NIPR/S for use in the identification of related nodes. The most accessible way is to utilize SNMP to view the Hub Node MIB and RAN Node MIB at the Hubmaster node. To get an unbroken list of Digivance CXD IP addresses that the Hubmaster is currently servicing, telnet into the Hubmaster node on port 7401. No user name or password is necessary.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup There are two default user accounts that come standard in the Digivance CXD network. The “operator” account has access to the Digivance CXD binaries and is used for regular maintenance. The “root” account has full access privileges to the entire file system. In addition, the “operator” account has “sudo” privileges, which may be modified by the network operator to tailor operator access.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup • Domain Name Server (/usr/sbin/named). • Node IP Receiver/Sender (/usr/sbin/niprs) server-side properties discussed in Section 9.2. • Digivance CXD Tenant processing (/usr/bin/tenantscan and /usr/bin/tenant). 10.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup domains serially will achieve the desired result (i.e. Digivance CXD, Digivance CXD-4XDG22, etc.). 10.1.5 DNS Forwarding The script will prompt “Enter a list of upstream DNS servers, one per line: (control-d when done)” to set up DNS forwarding. It is expecting as input the IP address of each Domain Name Server that the Hubmaster node can connect to. If there are no upstream DNS servers, leave this entry blank.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup 10.2.2 Incorporating Existing LAN DHCP Using a pre-existing LAN DHCP server is ideal when the Digivance CXD network only contains one Hubmaster node. In this configuration, there is no need for a router between the Hubmaster and the rest of the LAN, since all nodes are on the same subnet.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup 10.2.5 Incorporating Existing LAN DNS The method of incorporating an existing LAN DNS begins with configuring the Hubmaster DNS forwarding as outlined in Section 10.1.5 and continues with some maintenance at the upstream DNS. At a minimum, the upstream DNS needs to be updated with each Hubmaster node’s IP address and full hostname (including its domain).
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup 11.1.4 Hostname transceptHubNodeTable.transceptHubNodeHostname This entry shows the hostname of the CPU occupying a specific index of the Hub Node MIB. This entry is automatically set up by Digivance CXD system software. Changing hostnames on Digivance CXD nodes is not recommended, but can be accomplished by logging into the target node. 11.1.5 IP Address transceptHubNodeTable.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup For cases where a GPS receiver is not present and it is desired to manually enter the GPS coordinates, the Hub Node MIB contains two MIB fields to configure the GPS longitude and latitude settings. Since only the Hubmaster node in the Digivance CXD system contains a GPS receiver, these MIB fields will not be used for Hub Slave nodes.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup 11.2.4 Site ID transceptRanNodeTable.transceptRanNodeSiteID This entry displays the RF Network’s Site ID where each RAN is installed. In conjunction with the Pole Number, this is the mechanism used to pinpoint any RAN’s physical location. GPS can also be used, where available. The Site ID may be 64 characters long. Note: For tenant information propagation to occur, this field must be populated. 11.2.
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup from this MIB, the operator must set the “Clean” value to 1. The old node information will be removed. No further action is required. Note that if the node is present and valid, it will reappear within seconds, even if it is cleared. 11.2.9 RAN Disable transceptRanNodeDisableTable.transceptRanNodeDisableRanState This entry in the RAN Node MIB allows a given RAN to have all of its PAs disabled(*).
ADCP-75-192 • Issue 1 • December 2005 • Section 4: BTS Integration SECTION 4: BTS INTEGRATION Content Page 1 BTS VALIDATION ................................................................... 4-1 2 PATH BALANCING ................................................................... 4-1 2.1 1 Forward Path Balancing ......................................................... 4-2 2.2 Reverse Path Balancing ......................................................... 4-4 2.
ADCP-75-192 • Issue 1 • December 2005 • Section 4: BTS Integration Hub RAN RUC Attn FBHDC Composite Input Power PA Output Loss PA Output Power RUC Attn Offset RAN Output Power Figure 4-1. FBHDC Direct Cable Balancing Table 4-1 shows the recommended power levels and gains for the various CXD bands. Table 4-1.
ADCP-75-192 • Issue 1 • December 2005 • Section 4: BTS Integration 2.1.2 BIM Input High Power duplexed interfaces requires the use of the High Power Attenuator and the BIM Module. A block diagram of the forward path balancing components is shown in Figure 4-2.
ADCP-75-192 • Issue 1 • December 2005 • Section 4: BTS Integration The BIM input balancing procedure is as follows: 1. Insert signals into the HP Attenuator at the recommended input level (composite). 2. If the input level is lower than the recommended value, adjust the transceptTenantMoreAttenTable.transceptTenantBimForwardAttenZOffset fields in the Tenant OAM MIB by a comparable amount. For example: If the PCS composite input is 44 dBm, enter a -30 into the transceptTenantMoreAttenTable.
ADCP-75-192 • Issue 1 • December 2005 • Section 4: BTS Integration 2.3 Functional RAN Call Verification At the completion of BTS integration, it is recommended that the coverage area be driven to insure all RANs are operational. The following procedure is recommended: 1. Place calls on all RF channels supported by targeted RAN sector 2. Ensure hand-offs between RANs and RAN to tower are functional. Page 4-5 2005, ADC Telecommunications, Inc.
ADCP-75-192 • Issue 1 • December 2005 • Section 4: BTS Integration Blank Page 4-6 2005, ADC Telecommunications, Inc.
ADCP-75-192 • Issue 1 • December 2005 • Section 5: Software Updates SECTION 5: SOFTWARE UPDATES Content 1 1 Page SOFTWARE RELEASE DELIVERABLE ....................................................... 5-1 2 RELEASE NOTES .................................................................... 5-1 3 UPGRADING EXISTING SYSTEM.......................................................... 5-2 3.1 Preliminary Steps ............................................................. 5-2 3.2 Upgrade Steps ..............
ADCP-75-192 • Issue 1 • December 2005 • Section 5: Software Updates 3 UPGRADING EXISTING SYSTEM The most common upgrade scenario is one where an existing, fielded, operational system is having all of its CPUs upgraded to the next version of software. Some important notes regarding this type of upgrade: 3.
ADCP-75-192 • Issue 1 • December 2005 • Section 5: Software Updates • Test scripts being run to ensure that processes are running as expected. • If the autonomous actions taken by the upgrade executable discover that the upgrade was not successful, the upgrade executable will report this information in the log file located at /var/log/opencell-upgrade. Otherwise, a successful status message will be reported to that log.
ADCP-75-192 • Issue 1 • December 2005 • Section 5: Software Updates On the upgraded RAN CPU, verify PAs are functioning and power levels are as expected. Refer to the above "Preliminary Steps" section for details. 5 FAILED UPGRADES In the case of a failed upgrade, it will be desirable to attempt to return the target CPU to its previous revision by uninstalling the most recent software upgrade. This action will be accomplished with the use of a downgrade script that is installed as part of the upgrade.
ADCP-75-192 • Issue 1 • December 2005 • Section 5: Software Updates Upgrading a CPU does not require that a restore of the backed up files be performed unless a problem is encountered. Any data contained in the MIBmap files and any configuration data in the system configuration files will remain untouched through a software upgrade. The only time that backup data needs to be recovered is when an upgrade has failed and the CPU is being reverted to the previous version using the downgrade script.
ADCP-75-192 • Issue 1 • December 2005 • Section 5: Software Updates • address should be the IP address of a trap-sink (an SNMP manager that can receive traps); there can be any number of trap-sinks – simply enter one line per trap sink. • domain is that of the ADC system subnet on which nsupdate is being run. After completing the desired number of lines, finish by entering two blank lines and then a Ctrl-D.
ADCP-75-192 • Issue 1 • December 2005 • Section 5: Software Updates • In the event that a spare CPU cannot be updated because of the above restriction, the CPU will have to be upgraded on a standalone chassis that is not resident on the fielded system or be returned to the factory for upgrading. • It is NOT possible to update a spare Hub Master CPU while the fielded system's Hub Master is still installed, because two Hub Masters in the same domain will cause chaos on the network.
ADCP-75-192 • Issue 1 • December 2005 • Section 5: Software Updates Blank Page 5-8 2005, ADC Telecommunications, Inc.
ADCP-75-192 • Issue 1 • December 2005 • Section 6: Autonomous Software Functionality SECTION 6: AUTONOMOUS SOFTWARE FUNCTIONALITY Content 1 1 Page INTRODUCTION .................................................................... 6-1 2 FORWARD GAIN MANAGEMENT.......................................................... 6-1 3 REVERSE AUTOMATIC GAIN CONTROL ..................................................... 6-2 4 FORWARD DELAY MANAGEMENT ........................................................
ADCP-75-192 • Issue 1 • December 2005 • Section 6: Autonomous Software Functionality 3 REVERSE AUTOMATIC GAIN CONTROL The Digivance CXD system autolimits any strong in-band signal which reaches the RAN at a peak input level of greater than -38 dBm relative to the antenna port. The process does this by monitoring A/D overflows and adding attenuation in the RDC when these overflow occur. “AGC events” are logged on the CPU running the RDC process. Attenuation is backed out as the signal strength subsides.
ADCP-75-192 • Issue 1 • December 2005 • Section 6: Autonomous Software Functionality 7.1 Noise Test The front-end noise will be monitored by reading the noise power value from the reverse channels in the RAN SIF module belonging to the tenant-sector being analyzed. The in-band noise power (N) and total signal power (S+N) will be measured and analyzed in the SIF using an FFT analysis, as follows: The RCM software will generate faults if the integrated power levels are below the specified thresholds. 7.
ADCP-75-192 • Issue 1 • December 2005 • Section 6: Autonomous Software Functionality 8 PA OVERPOWER PROTECTION PA Overpower Protection (POP) is a software function that prevents damage to the PA as well as preventing the PA from exceeding FCC spurious output limits. POP measures the PA Output Power once per second from the RUC/PA MIB.
ADCP-75-192 • Issue 1 • December 2005 • Section 7: MIB Structure SECTION 7: MIB STRUCTURE Content 1 Page 1 MIB RELATIONSHIPS ................................................................. 7-1 2 HARDWARE RELATIONSHIPS ........................................................... 7-2 2.1 Hub/RAN Connection Relationships: ................................................ 7-3 2.2 Tennant Relationships ..........................................................
ADCP-75-192 • Issue 1 • December 2005 • Section 7: MIB Structure MIB RELATIONSHIPS HUB MASTER HUB NODE MIB HUB CONFIG MIB RAN NODE TENANT OAM MIB FGC MIB RGC MIB BTS CONNECTION MIB RAN NODE MIB NODE PATH MIB HUB NODE BUS SCANNER MIB NETWORK NODE MIB PATHTRACE MIB RGC MIB NODE PATH MIB NETWORK NODE MIB PATHTRACE MIB HRM MIB BUS SCANNER MIB GPS MIB STF MIB PSI MIB HDC MIB BIM MIB HUC MIB FSC MIB RSC MIB SIF MIB WD MIB SIF MIB RDC MIB FGC MIB EQUIPMENT MIB HUB RF CONN MIB EQUIPMEN
ADCP-75-192 • Issue 1 • December 2005 • Section 7: MIB Structure Each Hub/RAN node contains a Bus Scanner process whose responsibility is to discover the presence/absence of hardware modules and to start/stop HCP’s to manage those hardware modules. The Bus Scanner MIB reports the information defining the hardware “discovered” at that node. Each node contains a Network Node process to manage information about that CPU, where the interface is the Network Node MIB.
ADCP-75-192 • Issue 1 • December 2005 • Section 7: MIB Structure Tenant processing determines the location of its related nodes and hardware using a process called the Tenant Scan process that polls the Equipment MIB’s located at each node in the network. If the Equipment MIB indicates that there is hardware belonging to that tenant on that node, then the Tenant process in the Hubmaster will add that node to its "managed node" list.
ADCP-75-192 • Issue 1 • December 2005 • Section 8: General Information SECTION 8: GENERAL INFORMATION Content 1 Page 1 WARRANTY/SOFTWARE ............................................................... 8-1 2 SOFTWARE SERVICE AGREEMENT ........................................................ 8-1 3 REPAIR/EXCHANGE POLICY ............................................................ 8-1 4 REPAIR CHARGES ...................................................................
ADCP-75-192 • Issue 1 • December 2005 • Section 8: General Information 4 REPAIR CHARGES If the defect and the necessary repairs are covered by the warranty, and the applicable warranty period has not expired, the Buyer’s only payment obligation is to pay the shipping cost to return the defective Product. ADC will repair or replace the Product at no charge and pay the return shipping charges.
ADCP-75-192 • Issue 1 • December 2005 • Section 8: General Information 7 CUSTOMER INFORMATION AND ASSISTANCE PHONE: EUROPE Sales Administration: +32-2-712-65 00 Technical Assistance: +32-2-712-65 42 EUROPEAN TOLL FREE NUMBERS Germany: 0180 2232923 UK: 0800 960236 Spain: 900 983291 France: 0800 914032 Italy: 0800 782374 U.S.A.
ADCP-75-192 • Issue 1 • December 2005 • Section 8: General Information Blank Page 8-4 2005, ADC Telecommunications, Inc.
www.adc.
