01 Mn3515eu50mn 0001 Hw Intro Nodeb

HW introduction NodeB PF2 Siemens/NEC

MN3515EU50MN_0001 © 2006 Siemens AG

1

Contents 1 Node B product range FDD 3 1.1 Node B platform 1 5 1.2 Node B platform 2 6 2 Main features 7 2.1 Node B PF 2 racks and shelters 10 2.2 Node B PF 2 common modules 10 2.3 Transport network layer characteristics 12 3 Node B NB-440/441 overview 15 3.1 Features and technical data 16 3.2 Technical data 20 3.3 Rack and shelf configuration 24 4 Node B NB-880/881 overview 29 4.1 Applications and services 31 4.2 Advantages for operator 31 4.3 Siemens NB-880/881 introduction strategy 32 4.4 Key features and technical data 32 4.5 Rack and shelf configuration 33 5 NB PF2 modules 37 5.1 The Core Controller 39 5.2 Node B synchronization 60 5.3 Channel Coding card (CHC) 63 5.4 Digital Radio Interface Card (DRIC) 76 5.5 Combined Amplifier and Transceiver module (CAT) 80 5.6 Repeater card (REP) 84 5.7 Transceiver card (TRX) 86 5.8 Linear Power Amplifier (LPA) 88 5.9 Tower Mounted Amplifier (TMA) 90 5.10 Duplex Amplifier Multi-Coupler (DUAMCO) 94 5.11 4-port Ethernet Hub (EH4) 98

HW introduction NodeB PF2

Siemens/NEC HW introduction NodeB PF2

MN3515EU50MN_0001© 2006 Siemens AG

2

5.12 Alarm Collection Terminal Modules (ACT) 100 5.13 Connection to the Iub interface 104 5.14 Over-Voltage Protection for External Rest Line (OERF) 108 5.15 Power supply and battery backup 110 5.16 The service2 shelter for NB-441 and NB-881 112 5.17 System expansion 118 5.18 Node B NB-440/441 and NB-880/881 technical data 120 6 Node B 860 123 6.1 Features and Technical Data 124 6.2 Main Features 125 6.3 Hardware Architecture 126 7 Node B 580 131 7.1 Features and Technical Data 132 7.2 Main Features 132 7.3 Hardware Architecture 134 7.4 Supported modules within UMR4.0 US 134 8 Node B NB-341 137 8.1 NB-341 modules 138 9 New hardware components from UMR4.0 147 9.1 Macro Radio Server RS-880 149 9.2 Macro Remote Radio Head (RRH-m) 156 9.3 Power Supply for Remote Radio Heads (PSR) 161 10 19“ Micro Radio Server (RSU-380) 162 11 Micro Radio Server (RS-381) 164 12 Abbreviations 167



3

1 Node B product range FDD



4

Overview of the UTRAN Product Range Siemens/NEC UTRAN products provide a family of macro and micro FDD Node Bs for area coverage as well as hotspot cells and a corresponding RNC: Node B Platform 1 • Macro FDD Node B (NB-530) • Macro FDD Node B (NB-540) Node B Platform 2 • Micro FDD Node B (NB-341) • Macro FDD Node B (NB-420) • Macro FDD Node B (NB-860) • Macro FDD Node B (NB-440/NB-441) • Macro FDD Node B (NB-880/NB-881/NB-881 HR) • Macro Radio Server (RS-880) • 19“ Micro Radio Server (RSU-380) • Micro Radio Server (RS-381) • Macro Remote Radio Head (RRH-m) All types of Node B incorporate features for the optimum re-use of the existing 2G infrastructure, such as transmission links, operational procedures, and operation and maintenance interfaces.



5

NEC/Siemens provide a complete family of Node Bs comprising FDD macro Node B for area coverage, Node Bs for mini and micro cells. All types of Node B incorporate features for the optimal re-use of the existing GSM infrastructure (e.g. transmission links, operational procedures, O&M interface, etc.) in order to enable the smooth introduction of UMTS in existing networks.

1.1 Node B platform 1 1.1.1 Macro FDD Node B (NB-530) The FDD Macro Node B NB-530 is Siemens/ NEC´s start up solution for a fast introduction of UMTS. Advantages: • High flexibility with a number of possible configurations ranging from 1/0/0 one

carrier one sector solution to a full blown 3-carrier, 3-sector configuration by using the capacity of an extension rack.

• Easy to upgrade to the next generation by more powerful hardware and software.

• High capacity with up to 30 channel cards (with extension rack) each carrying 24 AMR voice channels.

• High power (20W) per carrier • RX and TX diversity for improvement of link quality and on-the-air combining of

transmit power (40W with optional Tx-diversity for 1carrier configurations). Early availability

1.1.2 High capacity macro FDD Node B (NB-540) The size of the NB-540 is equal to the NB-530 and it provides double the maximum capacity of the NB-530, i.e., 4/4/4 with one rack. The NB-540 on the 2nd generation platform will powerfully satisfy market requirements.



6

1.2 Node B platform 2 1.2.1 Compact FDD Node B (NB-420/440/441 and NB-

860/880/881/881 HR) The compact FDD Node B is specifically designed for the mass roll-out of the UTRAN. This small-sized Node B standing on the 2nd generation platform will adapt the latest market demands derived from a start-up experience with UMTS networks. Key features of the NB-420/440/441 and NB-860/440/441 are: • NB-420 and NB-860: Medium capacity: 1-rack: (1/1/1); • NB-440/441 and NB-880/881: High capacity: 1-rack: (2/2/2) and 2-racks

(2/2/2/2/2/2); • Upgradable to 3 frequencies (NB-440/441 and NB-880/881); • High power (20...40W); • Rx and Tx diversity (opt.); Redundant core modules and TRX cross connect. The NB-440/441 and NB-880/881 is smaller, less heavy and provides higher capacity than the start-up Node B NB-530. The hardware will be completely redesigned for lower cost and provisions for future upgrades. The compact Node B will be available as an indoor version (NB-440 and NB-880) as well as for outdoor deployments (NB-441 and NB-881). The devices show a new shelf design allowing maximum scalability.



7

2 Main features



8

The NB-420/440/441 and NB 860/880/881 have a modular structure and operates up to 4 carriers in 1 cabinet (NB-88x only). The minimum configuration is one cabinet: • NB-420/440 and NB-860/880 base rack for indoor installation, • NB-441 and NB-881 base shelter for outdoor installation. The outdoor cabinet consists of a double shelter. It includes a service area to accommodate AC/DC modules, backup batteries and link equipment. The NB-441 and NB-881 offers a service2 shelter for installing further backup batteries and link equipment. A maximum of 3 sectors is supported in a NB single rack/shelter. Different cell configurations up to 2/2/2 are possible without extension rack in a NB-440/441, in a NB-880/881 cell configurations up to 4/4/4 are possible without extension rack. Two linear-pole antennas or one cross-pole antenna are supplied for each sector. The antennas can be complemented by one Dual Tower Mounted Amplifiers (DTMA) or two Tower Mounted Amplifiers (TMA) per sector as low-noise amplifiers. The radio-frequency band for RX and TX signals includes • 2110 to 2170 MHz for downlink signals • 1920 to 1980 MHz for uplink signals. A continuous spectrum within a 15 MHz band is supported. The maximum cell range is 50 km. The base rack/shelter supports up to 960 channel elements (CE). The capacity is highly scalable, i.e. it can be increased in steps of 48 CEs with CHC48 and 96 CEs with CHC96. The NB-420/440/441 is equipped with REP, TRX, and LPA modules (REP-TRX-LPA concept), the NB-860/880/881 is equipped with DRIC and CAT modules (DRIC-CAT concept). Using the REP-TRX-LPA concept, the supplied Multi Carrier Power Amplifier (MCPA) is designed for operation with • one UMTS FDD carrier per antenna with a nominal output power of 20 W or • two UMTS FDD carriers per antenna with 20 W as the nominal average total

output power, i.e. each carrier will be radiated with 10 W per antenna (hardware-prepared).



9

Using the DRIC-CAT concept, the supplied Combined Amplifier and Transceiver (CAT) with 20W output power is designed for operation with • one UMTS FDD carrier per antenna with a nominal output power of 20W or • two UMTS FDD carriers per antenna with 20W as the nominal average total

output power, i.e. each carrier will be radiated with 10W per antenna (hardware-prepared).

Diversity: • RX diversity is a basic feature. • TX diversity is optional (hardware-prepared). The interface between the CAT module and DRIC complies with the publicly available Common Public Radio Interface (CPRI) specification. Using CPRI offers the following benefits: • Varying Radio Base Station architectures for very flexible solutions, e.g.

distributed architectures and remote tower mounted radio concepts • Additional deployment scenarios • Efficient network deployment The CPRI interface specification is available for download from http://www.cpri.info/spec.html The NB-420/440/441 and NB-860/880/881 offers a remote down tilt functionality consisting of a RET (Remote Electrical Tilt) module to adjust phase shifts within the antenna. The result of the superposition is a variable tilt of the resulting beam. This improves the radio and baseband capacity by adapting the cell size to different load scenarios without any time delay. The RNC and the connected Node Bs can be arranged in a star, cascade, hub or loop configuration (see TED:UTRAN common). The E1/J1 lines can be used with Inverse Multiplexing for ATM (IMA) in all these configurations. IMA provides for transport of a high bit rate ATM cell stream on several low bit rate physical links. The NB-420/440/441 and NB-860/880/881 supports two forms of transmission re-use for UMTS – GSM Co-location which are mutually exclusive: • Circuit Emulation Service (CES)

CES offers a cost-effective way to co-locate Node Bs and GSM base stations using a common ATM-based transmission network.

• Fractional ATM (FRAC) Fractional ATM over circuit-switched networks (GSM) provides transport of Iub timeslots.

For a detailed description see TED:UTRAN common.



10

2.1 Node B PF 2 racks and shelters Following Node Bs are provided with the same type of racks (and shelters): • NB-420 and NB-860 • NB-440 and NB-880 • NB-441 and NB-881

2.2 Node B PF 2 common modules 2.2.1 Core Controller (CC) The CC handles signal transmission and data controlling of the base rack/shelter and manages the data exchange with the RNC and the CHC. The CC has E-1 or E-1 and STM-1 Interfaces. Up to 2 STM-1 lines are directly connected to the CC at the front panel. Up to 16 E-1 lines are connected to the CC via Iub Connector (IUBCON) or Overvoltage Protection and Tracer (OVPT) or IUB.

2.2.2 Duplex Amplifier Multi-Coupler (DUAMCO) The DUAMCO includes duplexers, low-noise amplifiers (LNA) and multi-couplers. The duplexer combines the transmit and receive paths with the common antenna connector. The duplex filter provides receive and transmit band filtering. The receive path consists of an LNA followed by a power splitter providing four identical outputs for the TRX units. The power supply and the signaling of the TMA are provided by the DUAMCO via triplexers at the antenna outputs. The DUAMCORT and the DUAMCORET are available for the NB-420/440/441 and NB-860/880/881. Both types have the same functionality. In addition, the DUAMCORET supports, in combination with the DTMARET, DC supply and signaling function for a Remote Antenna Down tilt unit.

2.2.3 Channel Coding Card (CHC) The CHC card is a base-band signal processing block mounted on the B-SHF. It per-forms error correction coding and channel coding of transmission data. The CHC also performs the de-spreading, chip synchronization, Rake composition, error correction decoding, and de-multiplexing of received data. The CHC card can simultaneously perform channel coding and decoding for both the traffic channel and the control channel in one card. There are two types of CHC: CHC48 with 48 Coding Elements and CHC96 with 96 Coding Elements.



11

2.2.4 Tower Mounted Amplifier (TMA) The TMA is installed outside the Node B cabinet close to the TX/RX antenna. This amplifier is optional but highly recommended as it compensates cable losses in uplink and thus ensures lower noise disturbance. The result is an improved link quality and link availability at cell borders. The TMA feeds the overall Node B downlink signal to one TX/RX antenna and filters the overall uplink signal coming from the same TX/RX antenna. Due to the full duplex architecture of the TMA, only one feeder cable is required for the TX and RX signal between the TMA outside and the DUAMCO inside Node B. The signaling interface between the TMA and the DUAMCO is provided via the RF interface feeder connector by means of a triplexer. Status information from the TMA is passed on to the O&M interface via this interface. In addition to the TMA, a Dual TMA (DTMA) is provided for the NB-420/440/441 and NB-860/880/881. The DTMA includes two TMA units in a single housing and is very efficient in combination with a cross-polarized antenna. A DTMA including RET (Remote Electrical Tilt) control is available. Antennas with a remote down tilt functionality improve the radio and baseband capacity by adapting the cell size to different load scenarios.



12

2.3 Transport network layer characteristics The next table shows the transport network layer characteristics for the NB-420/440/441 and NB-860/880/881. For a detailed description of the UTRAN Transport Network Management see TED:UTRAN common.



13

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 1 Transport network layer characteristics for the NB-420/440/441 and NB-860/880/881



14



15

3 Node B NB-440/441 overview



16

3.1 Features and technical data The Macro FDD Node B NB-440/441 is specifically designed for the mass roll-out of the UTRAN. This Node B is based on the 2nd-generation platform and incorporates the latest market demands derived from start-up experience with UMTS networks. The devices feature a shelf design which allows for maximum scalability. The Node B can be further upgraded up to a 2/2/2 configuration in one rack/shelter. The NB-441 is the outdoor variant of the NB-440. It is a fully self-contained Node B including any provision for quick and easy outdoor deployment. Key features of the NB-440/441 include: • High capacity: 1 rack/shelter (2/2/2) • High power: up to 40W per carrier with Tx diversity • RX diversity (strongly recommended) and TX diversity (hardware-prepared,

optional) The UMTS Terrestrial Radio Access Network (UTRAN) consists of Node Bs and RNCs, as standardized by 3GPP. Node B links up to the RNC via dedicated E1/J1 and/or STM-1 connections. ATM is used as the transmission protocol. Data traffic is packed into AAL2 cells, whereas signaling traffic is transferred using the AAL5 protocol. This chapter gives an overview of the main features, functional units and technical data of Macro Node B NB-440/441.



17

Fig. 2 Node B NB-440

Fig. 3 Node B NB-441



18

3.1.1 Redundancy In order to prevent any interruption of operation and assure maximum system reliability, redundancy concepts are incorporated in the configuration of the NB-440/441.

3.1.1.1 Redundancy configuration and operation of equipment The following describes the redundant configuration of each function part in Node B and its operation.

Repeater Card (REP) The two REP cards REP-0 and REP-1 are both active. They are both connected to all the CHC and TRX cards installed. The activation status of the two REP cards is communicated to all CHC and TRX cards via DC line. On the downlink path, the CHC cards select the route for data transmission depending on the activation status of both REP cards. On the uplink path, the TRX cards transfer data to both REP cards. When both REP cards are active, the data from the REP-0 card is usually selected by the CHC cards.

Digital Radio Interface Card (DRIC) Optionally, a second DRIC may be inserted for redundancy reasons. The DRIC supports cold redundancy. Hot redundancy is hardware-prepared.

Core Controller (CC) The NB-440/441 can be equipped with a redundant CC. During standard operation of the Node B, one CC is active and the second is in standby mode. Switch-over between the active core controller and the standby core controller can either be initiated on operator request or as an emergency switchover that is triggered via the Redundancy Switch Control (RSC) in case the active CC fails.

Transceiver Card (TRX) The TRX card has two almost independent uplink paths and two almost independent downlink paths. RX diversity is implemented via these two RX paths. If one of the RX paths fails, a sensitivity degradation occurs but all services can be still provided.

Channel Coding Card (CHC) All CHC cards are for active use. If a card fails, the capacity is reduced, but the services will continue to be provided.

Duplexer Amplifier Multi-Coupler (DUAMCO) The DUAMCO has two independent RX paths to support RX diversity for one sector. If one path fails, a sensitivity reduction of the uplink occurs.



19

*) The redundant REP card is optional (*2) The redundant CC card is optional. The cold redundancy provides an automatic procedure for the OAM data alignment of the standby CC via the CC-Link. For the switchover, a single reset of the standby CC is necessary. Due to the restart of the standby CC all connections belonging to the own NodeB are lost as well as to co-located NodeBs and GSM BTSs. (*3) The redundant DRIC card is optional for upgraded NB-440/441 with DRIC-CAT concept. The semi-hot redundancy provides a switchover procedure whereby the provided service may be degraded during the switchover. Stable connections are maintained. The hot redundancy provides a switchover procedure whereby the impact on the provided service is negligible.

Fig. 4 Redundancy concept

Tower Mounted Amplifier (TMA) If a TMA is installed, the LNA within the DUAMCO is switched off (MUCO mode). If the TMA‘s LNA fails, the RX signal will be bypassed within the TMA and the DUAMCO switches on its LNAs (AMCO mode). However, a sensitivity reduction for the uplink can occur because the feeder losses will no longer be compensated.



20

3.2 Technical data 3.2.1 Electrical and mechanical specifications The table below shows the electrical and mechanical specifications of the NB-440/441.

3.2.2 Model units - parameter overview

3.2.3 Performance

Fig. 5 Electrical and mechanical specifications



21

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 6 General characteristics of the NB-440/441



22

3.2.4 Capacity There are several types of Node B with different numbers of sectors and carriers. The table below shows the capacity of each type of NB-440/441. The Channel Coding Card can simultaneously perform the channel coding and decoding for both traffic channels and control channels in one card. The number of channel elements (CE) includes the number of both traffic channels and control channels. Mixed operation of CHC96 and CHC48 is also possible within one shelf.



23

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Number of services per CHC card

Capacity of the NB-440/441

Fig. 7 Capacity of the NB-440/441 and Number of services per CHC card



24

3.3 Rack and shelf configuration This section describes the cabinet and shelf configuration for • NB-440 (indoor installation)

– base rack • NB-441 (outdoor installation)

– base shelter – service2 shelter

3.3.1 NB-440 base rack Each NB-440 base rack consists of • one Air Link Shelf (A-SHF) • one Base Shelf (B-SHF) Fig. 8 shows the front view of an NB-440 base rack for indoor application with REP-TRX-LPA concept. The DC panel is installed in the middle of the rack between the two shelves. For the indoor rack, the functionality of the EMI panel is provided by the rack ceiling.

3.3.2 NB-441 base shelter The outdoor cabinet NB-441 is a double shelter divided into two separate frames which provides space for a service area. Each NB-441 base shelter consists of • Frame for service equipment

– one Air Link Shelf (A-SHF) – one Base Shelf (B-SHF)

• Frame for service equipment – AC/DC sub-rack – Battery tray – 6 HU (Height Unit) for link equipment (link equipment is optional)

Fig. 9 shows the front view of an NB-441 base shelter for outdoor application with REP-TRX-LPA concept. The DC panel is installed in the middle of the rack between the two shelves.



25

The A-SHF contains:Up to six Linear Power AmplifiersUp tp three DUAMCO Modules (Dual Amplifier Multi Coupler), with two submodules, including the RX-AMP (two operational modes: with a TTA or without a TTA) and the RX-MON.

The B-SHF contains:Up to six Transceiver Cards (TRX)Up to 10 Channel Coding Cards (CHC)Up to two Repeater Cards (REP)Up to 2 Core Controllers (CC) with E1- or E-1 and STM-1 Interface and Flash Memory

The FAN units contains:Two Fans each

The DC-Panel contains:11 BreakersAlarm Collection Terminal ModulesUp to two Ethernet HubsInterfaces for the CAN bus and alarm connectors

In addition to the units, the Node B has Tower Top Amplifiers (TTAs) and antennas.

Fig. 8 NB-440 rack and shelves with REP, TRX and LPA

Fig. 9 NB-441 rack and shelves with REP, TRX and LPA



26

3.3.3 NB PF2 / REP-TRX-LPA concept 3.3.3.1 Repeater card (REP) The REP card is positioned between CHC cards and TRX cards to provide a multiplexing function for the base-band signals.

3.3.3.2 Transceiver card (TRX) The TRX consists of a Transceiver Baseband Block (TRX BB) and a Radio Frequency Block (RF). The RF is subdivided into a Transmitter Block (TX) and a Receiver Block (RX). The TRX BB spreads and scrambles digital signals received from the REP. The TX uses a quadrature modulator to convert these base-band spread signals into radio frequency signals. The RX performs coherent detection of radio frequency signals received from the DUAMCO. The TRX BB converts and demodulates them into digital signals. The TRX supplies high-precision digital processing by high-speed sampling as fast as eight times the chip rate. Carrier leakage in the TX part is prevented by applying a frequency offset to the base-band I and Q signals to block DC, thus improving the TX ON/OFF ratio and modulation accuracy. Carrier leakage in the RF part is minimized by the common local oscillation circuit for the transmitter and receiver.

3.3.3.3 Linear Power Amplifier (LPA) The LPA amplifies the transmitter radio frequency signals from the TRX to a specified level for each sector. Operation and maintenance information such as alarms and product identification data (PID) is supported by a CAN bus interface. The supplied Multi Carrier Power Amplifier (MCPA) is designed for operation with one UMTS FDD signal per carrier with a nominal output power of 20 W or two UMTS FDD signals per carrier with 20 W as the nominal average output power, i.e. 10 W for each signal.



27

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 10 Node B functional overview with REP, TRX and LPA



28



29

4 Node B NB-880/881 overview



30

With this release, a new hardware concept (DRIC-CAT) is introduced replacing the transceiver cards (TRX), power amplifier (LPA) and repeater card (REP). This concept enables newest available technologies in linear amplifier research such as digital predistortion. This features a noticeably higher efficiency resulting in a lower power consumption of the whole Node B. The modules DRIC (Digital Radio Interface Card) and CAT (Combined Amplifier and Transceiver) are connected by a digital high-speed interface called the Common Public Radio Interface (CPRI). The CPRI is already prepared to support Remote Radio Heads (Tower Mounted Radio Concept). The NB-880/881 is the Siemens UMTS FDD Macro Node B, hence utilizing W-CDMA technology. It adheres to all relevant UMTS standards, specified by 3GPP. Macro Node Bs are the most important ones in early network roll-out phases, as they provide the initially needed coverage. The two versions for indoor usage (NB-880) and outdoor usage (NB-881) grant the operator the flexibility needed for site acquisition. The NB-880 offers a high upgradeability in terms of frequencies, sectors, channel elements and features. The NB-880 is based on the same HW platform like the smaller brother NB-860, which is designed for scenarios where either less capacity is needed or a size limitations applies The NB-880/881 can be used for coverage, high mobility and speech-oriented scenarios, as well as for high data traffic, small-cell and high capacity-oriented deployments. Maximum Configuration: • Upgradeable up to 4/4/4@960VC and 6 sector configurations using Remote

Radio Heads



31

4.1 Applications and services NB-880 is an UMTS-FDD Macro indoor Node B. NB-881 is an UMTS-FDD Macro outdoor Node B. This implies all applications and service aspects. Some of them are: • Medium to large cells (0-50km) • Medium to high capacity • High mobility • HSDPA for high downlink data rates (up to 14.4Mbps peak data rate under ideal

conditions) • High variability due to additional support of Remote Radio Heads and usability

of different power amplifiers 20W and 40W output power. • Customization of Node B to the operators need possible

4.2 Advantages for operator • Experiences from the earlier NB-530/531 and predecessor NB-440/441 makes

the NB-880/881 a highly reliable product • Low power consumption by the usage of very efficient power amplifier and high

integrated modules • Low number of different modules to save costs for spare parts, training and

logistics • NB-880/881 is very compact compared to its performance • Wide range of possible configurations in order to adapt to operator’s need • NB-881 also includes space to include batteries, AC/DC power supply and link

equipment • 3rd generation HW platform guarantees future-proof product, e.g. full HSDPA

support. By the usage of CHC-96 only SW download is required to support HSDPA. For the NB-440/441 is will be required to add a CHC-96 to support HSDPA

• Platform is based on the CPRI interface (standard digital interface which connects the baseband part of the Node B to the RF part) and is supporting radio over fiber application (Remote RF Heads)



32

4.3 Siemens NB-880/881 introduction strategy • The NB-880/881 is part of UMR3.5, hence and the required SW is also released

within UMR3.5 • NB-880/881 operates only on UMR3.5 SW or higher • NB-880/881 is based on the 3rd generation HW platform, which is the

successor of the NB-440/441. • The NB-440/441 can be upgraded to the functional set of the NB-880/881 by

upgrading with DRIC and CAT. • Very flexible and modular product, which is able to grow with the demand (from

1/0/0 up to 4/4/4).

4.4 Key features and technical data • up to 4/4/4 in one rack/shelf • up to 960 gross VC in one rack/shelf, • up to 80W per sector-80W per cell with TX-Div possible.. • RX diversity included, TX diversity HW prepared • High flexibility in terms of line interfaces allow the operator to choose the right

capacity and features for rollout • Advanced transport capabilities from the beginning to save transmission line

costs: - Inverse multiplex access (IMA) for up to 2 times 8 E1 lines - Fractional ATM and Circuit Emulation Service (CES) for co-location with GSM equipment - Star, chain and loop configurations including usage of STM-1 technology

• Redundancy for core controller (line interfaces) and DRIC card as well as load sharing between channel cards minimize the downtime of Node Bs in the field

• Support of the standardized CPRI interface (future proven) • Power consumption reduction of up to 25% by the usage of higher integrated

technology and higher efficient power amplifiers • Channel Card can handle both Traffic and Common Channels, this helps the

operator to utilize the baseband resources much better • No dedicated reservation of resources for HSDPA required, improves the

flexibility and saves the investment • Call Context Migration and CHC Defragmentation features increase the

efficiency of baseband resource usage and reduces the required number of Channel Cards in the Node B



33

• Very compact size: - dimensions of NB-880: 1400x600x450 - dimensions of NB-881: 1499x1270x700

• Low level of TX Spurious emission ensures the isolation is easily reached in case of GSM BTS collocation scenario

• Support of Remote Electrical Tilt (optional) reduces OPEX costs for the down tilt adjustment and provides an alternative redundancy concept in operator’s network. The RET functionality is from the beginning fully AISG compliant. The standard interface helps to save CAPEX costs by the flexibility in the antenna choice.

• HSDPA prepared, HSDPA enables high data rate downlink traffic applications (up to several Mbps peak data rates).

4.5 Rack and shelf configuration This section describes the cabinet and shelf configuration for • NB-880 (indoor installation)

– base rack • NB-881 (outdoor installation)

– base shelter – service2 shelter

4.5.1 NB-880 base rack Each NB-880 base rack consists of • one Air Link Shelf (A-SHF) • one Base Shelf (B-SHF) Fig. 8 shows the front view of an NB-440 base rack for indoor application with DRIC-CAT concept. The DC panel is installed in the middle of the rack between the two shelves. For the indoor rack, the functionality of the EMI panel is provided by the rack ceiling.



34

4.5.2 NB-881 base shelter The outdoor cabinet NB-441 is a double shelter divided into two separate frames which provides space for a service area. Each NB-881 base shelter consists of • Frame for service equipment

– one Air Link Shelf (A-SHF) – one Base Shelf (B-SHF)

• Frame for service equipment – AC/DC sub-rack – Battery tray – 6 HU (Height Unit) for link equipment (link equipment is optional)

Fig. 11 shows the front view of an NB-881 base shelter for outdoor application with DRIC-CAT concept. The DC panel is installed in the middle of the rack between the two shelves.

4.5.2.1 NB-881 Shelter with reduced height (NB-881 HR) The NB-881 with reduced height is variant of the NB-881 with a shelter which height is below 1.150 m. Shelter and base do not exceed 1.500 m. The NB-881 HR is equipped with DRIC-CAT concept and features a 2 carriers/sector configuration. Configurations with the RRH-m and RRH-p (HW-prepared) are possible as well as the use of HSDPA. The shelter is divided into three separate frames. The whole feature set, functionality and configurations are offered like in the NB-881 with normal height. The height reduction is achieved by distributing the boards/modules and panels of the NB-881 onto 3 racks within the shelter. The height reduced NB-881 does not require neither an Extension Rack nor additional Service2 Shelters for battery backup and LE. Fig. 12shows the front view of an NB-881 shelter with reduced height. The DC panel is installed in the upper part of the middle rack. The EMI panel is located at the bottom of the shelter.



35

Fig. 11 NB-880/881

Fig. 12 NB-881 Shelter with reduced height (NB-881 HR)



36

Fig. 13 Node B functional overview with DRIC and CAT



37

5 NB PF2 modules



38

The system configuration of the Node B PF2 contains the following units: Common units: Core Controller (CC) Channel Card (CHC) Duplex Amplifier Multi-Coupler (DUAMCO) Over-Voltage Protection and Tracer (OVPT) Alarm Collection Terminal Modules (ACT) Cooling System (FAN) Additional units: Mains Supply Unit (MSU) Heater (441 only) AC/DC Rectifiers (441 only) Battery Tray (441 only) Smoke Detector (441 only) Panels Optional units: Tower Mounted Amplifier (TMA) Ethernet Hub (EH4) Over-Voltage Protection for External Rest Line (OERF) Different modules and concepts: • REP-TRX-LPA concept of NB-420/440/441 - Repeater (REP) - Transceiver Card (TRX) - Linear Power Amplifier (LPA) • DRIC-CAT concept of NB-860/880/881 - Digital Radio Interface Card (DRIC) - Combined Amplifier and Transceiver Module (CAT) This chapter provides a functional description of each unit.



39

5.1 The Core Controller 5.1.1 The Core Controller (CC1/CC2) The Core Controller (CC1/CC2) • supports signal transmission and data controlling of the base rack/shelter • manages the data exchange with the RNC and the Channel Coding card

(CHC). The CC consists of three mandatory boards: • CPU board • ATM board • LIU (Line Interface) board for PDH (Plesiochronous Digital Hierarchy) lines If an STM-1(o) interface is used on the Iub interface, a Core Controller equipped with an additional STM-1 board for optical STM-1 must be used. The following Iub connectivities are offered: • 8 x E1/J1: at ports 8...15 • 16 x E1/J1: at ports 0...15 • 16 x E1/J1 and 2 x STM-1: at ports 0...15/ STM-1 ports 0..1 The Core Controller supports Inverse Multiplexing for ATM (IMA). The RNC and the connected Node Bs can be arranged in a star, cascade, hub and loop configuration (see TED:UTRAN Common). A second CC may be inserted for redundancy reasons. Cold redundancy is supported by most CC types and requires a certain firmware version. The Clk-In interface can be used to synchronize the CC with an external clock (SMA connector). The Clk-Out synchronizes the outer device with the CC clock. A standard 10BaseT Ethernet interface connects the CC to the outside world (i.e. the LMT - Local Maintenance Terminal) via a twisted pair cable (CAT5). The external Ethernet interface of the CC must have a unique IP address. Details of the Core Controller’s four boards are described below.

CPU Board The CPU board controls the whole Node B. From the CPU’s point of view, the ATM board, the LIU board and the STM-1 board are peripheral devices operated by the operating system Linux. These peripheral devices communicate using either a message passing principle or memory-mapped access.



40

The main communication bus inside the CC is the PCI bus. Configuration and data exchange with the LIU during operation and the ATM processing are performed via the PCI bus. The three CAN buses are used to send alarm messages, mount and supervise information.

ATM board The CPU board is able to configure and exchange data with the whole ATM unit over the PCI bus. A PCI bus bridge converts the PCI protocol to the individual bus interfaces of the ATM devices. The ATM board communicates with the LIU board by using 16 full duplex differential lines. Two different PDH protocols are supported: E1 and J1. Another major internal bus system between the ATM devices is the UTOPIA bus interface. The UTOPIA buses transport the AAL2 and AAL5 traffic between the lub and the baseband units.

LIU board The LIU board contains devices for: • generating the line clocks • amplifying the line signals • jitter/wander attenuation The clock unit selects the best clock source from various line interface units or from an external clock source and synchronizes the OC-VCXO (Oven controlled - voltage controlled xtal (crystal) oscillator) clock. All baseband clocks and other timing signals for the BB are derived from the OC-VCXO reference clock. The duplex device uses the UTOPIA bus interface for communication between the ATM board and the BB boards on the B-SHF.

STM-1 board The STM-1 board consists of two independent STM-1 interfaces. Just one STM-1 interface is used for the connection to the RNC. The other STM-1 interface can be used to collect the traffic from other Node Bs, e.g., in a cascade configuration. The transceiver modules transform optical information to electrical information and vice versa. An ATM framer device recovers the transmission clock, attenuates jitter and wander effects on the line and frames ATM cells. The ATM framer device communicates with the ATM processing unit via a UTOPIA-2 bus. The CPU exchanges data with the STM-1 board via a PCI bus system. A PCI bus is also used for transporting configuration data and alarm or status messages. A PCI bus bridge interfaces to the STM-1 framer devices.



41

5.1.2 The Core Controller CC3 The Core Controller CC3: • supports signal transmission and data controlling of the Node B • manages the data exchange with the RNC and the Channel Coding Card

(CHC).

The CC consists of three mandatory functional blocks: • CPU functional block • ATM functional block • LIU (Line Interface Unit) block for SDH/PDH (Synchronous/Plesiochronous

Digital Hierarchy) lines. If an STM-1/OC-3 interface is used on the Iub interface, a Core Controller equipped with an additional STM1(o)/OC-3 board must be used.

The following Iub connectivities are offered: • 8 x E1/J1/T1 • 16 x E1/J1/T1 • 16 x E1/J1/T1 and 2 x STM1/OC-3 • 2 x STM1 The Core Controller supports Inverse Multiplexing for ATM (IMA). The RNC and the connected Node Bs can be arranged in a star, cascade, hub and loop configuration (see TED:UTRAN Common). The loop configuration is only possible with additional external SDH equipment. A second CC may be inserted for redundancy reasons (cold redundancy). The Clk-In interface can be used to synchronize the CC with an external clock (1.0/2.3 connector). The Clk-Out signal is the same as the Clk-In signal and can be used e.g. for the second CC. A standard 10/100Base-T Ethernet interface connects the CC to the outside world (i.e. the LMT - Local Maintenance Terminal) via a twisted pair cable (CAT5). The external Ethernet interface of the CC must have a unique IP address. The default IP address can be customized by using the serial interface (RS-232) during system start or by data base.



42

Characteristics of the CC3

Details of the Core Controller’s four boards are described below.

Mother board The mother board comprises the CPU, ATM and clock generation functionality. The Central Processing Unit (CPU) controls the O&M and C-Plane of the Node B. It handles basically the NBAP, ALCAP, and the O&M messages within the Node B and toward the RNC.

The ATM block The ATM block is responsible for the complete ATM switching which also includes the termination and conversation of the ATM adaption layers AAL2 and AAL5. The master clock part is generating the Node B internal clocks for the digital cards and RF modules. It also distributes these clocks via the B-Shelf backplane to the corresponding cards and modules. The high stable clock signals are realized by an OC-VCXO [Oven Controlled-Voltage Controlled Xtal (crystal) Oscillator]. The reference signal is taken from the LIU board(s) or the external clock synchronization port.

E1/J1/T1 LIU boards The LIU board contains devices for: • Generating the line clocks • Amplifying the line signals • Jitter/wander attenuation In addition to the physical line termination including the galvanic isolation and over voltage protection, the E1/J1/ T1 LIU provides the following functionalities: • Inverse Multiplexing for ATM (IMA) • Circuit Emulation Service (CES) Fractional ATM

STM1/OC-3 board The STM1/OC-3 board consists of two independent interfaces. Just one interface is used for the connection to the RNC. The other interface can be used to collect the traffic from other Node Bs, e.g., in a cascade configuration. The transceiver modules transform optical information to electrical information and vice versa.



43

An ATM framer device recovers the transmission clock, attenuates jitter and wander effects on the line and frames ATM cells. The ATM framer device communicates with the ATM processing unit via a UTOPIA-2 bus. The CPU exchanges data with the STM1/OC-3 board via a PCI bus system.

5.1.3 Core Controller redundancy This chapter serves as short introduction to the Node B Core Controller Redundancy feature. The chapter is subdivided into the following sections:

• In general • Customer benefits • Inter-working / dependencies • Prerequisites

5.1.3.1 In general The Node B Core Controller Redundancy feature introduces a comprehensive redundancy concept for the Core Controller (CC) of the Node B PF2. Switchovers between the active core controller and the standby core controller can either be initiated on operator request or as an emergency switchover that is triggered via the Redundancy Switch Control (RSC) if the active CC fails. The Core Controller Redundancy includes redundancy for the E1/J1-line interface and the STM-1 line interface.

5.1.3.2 Customer benefits This redundancy feature for the core controller improves Node B availability significantly by: • minimizing service interruption for its own Node B • minimizing transmission interruption to associated Node Bs and GSM BTSs An automated switchover is started as soon as a hardware or software failure has been detected in an active CC. Maximum out-of-service time in this case is less than 6 minutes due to Node B reset.

5.1.3.3 Functional description The Core Controller (CC) of the Node B handles both the Call Processing (CP) and the OAM protocols. In addition, it switches the ATM traffic toward subordinate Node Bs in the hub or cascaded networking configurations, as well as the transmission of the Time Division Multiplex (TDM) traffic to collocated GSM base stations. A failure within the core controller causes not only a breakdown of its own Node B but also a loss of connection to the associated Node Bs and GSM base stations.



44

Therefore, this feature introduces a cold redundancy concept for the core controller of the 2nd Node B platform that significantly improves the availability of the Node Bs. The Node Bs are equipped with two redundant CCs. During standard operation of the Node B, one CC is active, and the second is in standby mode. The cold redundancy provides an automatic procedure for the OAM (Operation and Maintenance) data alignment of the standby CC via the CC-Link. For the switchover, a single standby CC reset is necessary. Due to the restart of the standby CC all connections belonging to the corresponding Node B are lost as well as to collocated Node Bs and GSM BTSs.

5.1.4 Hardware overview The redundancy solution is based on the existing hardware, implying that both CCs, the active and the standby CC possess the same hardware. These two CC modules have the same functionality and are installed in two different slots of the B-Shelf of the Node B. Cold redundancy is supported by most CC types and requires a certain firmware version. The active CC has physical access to the E1/J1 and the STM-1 line interfaces. The switching process differs between E1/J1 and STM-1 interfaces. When the E1 interface is used, the standby CC is disconnected from the E1/J1 line interface. The RSC generates a signal indicating whether the unit is in active or standby mode and switches the relays at the CCs for the Iub interfaces, the line drivers for the UTOPIA and the clock distribution busses on/off. Both CCs contain an integrated relay. When the STM-1 interface is used, the standby CC has physical access to the STM-1 line interface but is only listening. Active and standby CC are physically connected to the external interfaces but only the active CC is allowed to communicate with the external/collocated nodes.

5.1.5 Modes of the core controllers A CC is in the active mode when the board has finished its boot phase and the operational software is running. The active CC provides all services and supports all of the Node B features. The active CC controls its own Node B and maintains all connections to subsequent/collocated Node Bs and GSM BTSs. It is connected to the external interfaces of the Node B, e.g. to the E1/J1 and/or the STM-1 interface and to the internal interfaces, for instance the CC-Base Band (CC-BB) interface. Only the RSC of the active CC can trigger a switchover to the standby CC and acts according to the current hardware signals and software flags. The inactive CC is disconnected from the external and internal interfaces. It communicates with the active CC via the CC-Link and/or via the Controller Area Network (CAN).



45

The inactive CC can be in one of the following modes: • Not installed: means that the CC is not available, e.g. because the board is not

connected to the backplane of the Node B • Faulty: means that the board is connected to the backplane but it is out of order

and has to be exchanged before a switchover is possible • Standby: means that the software is loaded and the startup was successful, but

no operational software is running; software and OAM data can be downloaded via the CC-Link. The standby CC only acts as active CC after a reset.

The following failures cause an emergency switchover: • critical or major hardware failure of the active CC, e.g. of the E1 / STM-1

interfaces, in which case failure implies a real hardware defect and not only a non-working line interface status

• software errors, only in cases where no separate software escalation is available to support recovery levels

Fig. 14 CC (Example: CC-OMAFV1)



46

5.1.6 Switching between the Core Controllers Operators at the Radio Commander (RC) are always informed about the modes of both CCs and can initiate a switchover when necessary. For the takeover, the active CC and consequence the standby CC have to be reset before the switchover between the active CC and the standby CC is made. Due to the restart of both CCs all connections belonging to its own Node Bs are lost, as well as the connections to the collocated Node Bs and GSM BTSs. The switchover leads to a transmission interruption, because all information which is stored in the active CC (ATM and CES buffers) will be lost at switchover and the transmission protocols (CES and physical layer) need additional time for resynchronization. The redundancy feature automatically aligns the OAM data of the standby CC via the CC-Link. The switching behavior depends on the current CC mode and on a certain action, which can be triggered by either the operator or the CC software. Fig. 15 provides an overview of a CC mode transition due to a certain action. The normal and the emergency switchovers are described in the following. Switching on operator request is called a normal switchover and is rejected during a software or database update, or whenever the standby CC is not aligned. Operator commands are not accepted during the switchover. In the event of a hardware or software failure in an active CC, an automatic switchover, a so-called emergency switchover, is triggered via the RSC. The emergency switchover initiates a hardware reset of the standby CC, thus it becomes active after a restart. This makes a local service team unnecessary for triggering the switchover. The operator is always informed about the mode of both CCs (via RC) and is able to react immediately after a CC failure has been detected (e.g. initiating the exchange of the faulty CC).



47

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

*) The startup behavior after system reset (push button) and power on is the same. During this startup the CC-N is preferably the active CC if no error occurs. The CC-N is on the left hand side (of the B-Shelf) and comes up first after reset, while the CC-E is on the right hand side and comes up second after reset.

Fig. 15 Overview of possible CC mode transitions



48

5.1.7 Redundancy and communication links The two CC modules with identical functionality are installed in two different slots of the Node B’s B-Shelf, where one CC module is active and the other one is inactive i.e. in standby, faulty or not-installed mode. Both CCs are connected by the CC Link which is implemented as a twisted pair 100 Mbps Ethernet link that provides a communication interface between the two main processors. A fail-safe mechanism prevents the active CC board from any interference to a faulty CC module. The basic concept for the E1/J1 line interface is illustrated in Fig. 16. Only the active CC module is connected to the external and internal interfaces, while the inactive CC is disconnected from the external and internal interfaces (either by hardware or software) except for the CC link to the active CC and the CAN bus. The basic concept for the STM-1 line interface is illustrated in Fig. 17. Both CCs are physically connected to the external interfaces via the optical splitter, thus both CCs are capable of receiving ATM cells. However, only the active CC is allowed to communicate with the external/collocated Nodes. Internal interfaces are only connected to the active CC.

Redundancy switching behavior (based on RSC) The redundancy switch control logic (RSC) on the CCs is responsible for the switching process. It generates a signal indicating whether the unit is active or in standby and switches the relays for the Iub interface and the line drivers of the UTOPIA and clock distribution busses on and off. A switch logic link between the two CCs controls the switching process. This ensures that only one CC can be active at any one time which means that only the active CC is in receive/transmit state. The standby CC is in receive state and its transmit process is suppressed. For this, the transmitter of the standby CC must be switched off. The switch-off process is controlled by the RSC.



49

Fig. 16 CC redundancy concept for the E1/J1 interface

Fig. 17 CC redundancy concept for STM-1 Interface

5.1.8 Interface connection and switching 5.1.8.1 Iub interface (E1/J1) The Iub interface is connected to the CCs via relays with only one CC monitoring the Iub interface at any particular time. The relays of the standby CC are switched off, thus preventing the reception and transmission of data. Switching of the relays is done by the RSC logic unit. If a redundancy switchover from CC-N to CC-E is initiated, the relays on CC-N will be switched off at the next rising edge of the 10 ms frame synchronization pulse, and at the same time those of the CC-E will be switched on. During normal operation the software on the active core is able to control the relays by setting dedicated register bits, which causes the control logic to switch the relays on and off (CC-N switch relays and CC-E switch relays). For the inactive core, switching of the relays is always inhibited by hardware logic.



50

5.1.8.2 Iub interface (STM-1) The Iub interface (STM-1 line) passes the EMI panel of the Node B and terminates into the optical splitter. Behind this optical splitter, the STM-1 line is physically split up for connection to the active CC and the inactive CC. Each STM-1 line requires 2 optical splitters (Rx and Tx paths are separated). This means that 2 STM-1 lines need 4 optical splitters. This splitter redundancy prevents a single point of failure. A long-term reliability (100 000 hours at least) is assured by the fact that the optical splitter is a passive component.

5.1.8.3 Main principles of STM-1 redundancy The basic configuration of the CC redundancy for the STM-1 line interface is illustrated in Fig. 18. The optical splitter uses standard connectors of type LSH and for the CC connection a standard connector of type F3000.

5.1.8.4 Electrical characteristics of transceiver module The LIU board of the CC hosts the transceiver module. Three broad application categories are defined: Intra-office, short haul and long haul. The main attributes of these categories are the source nominal wavelength and the cable length (distance). (For more detailed information refer to table 1 of ITU-T G.957). The short-haul category requires a cable length of 15 km and an attenuation range from 0 to 12 dB. This leads to a maximum allowed attenuation of 0.8 dB/km. The long haul category requires a minimum cable length of 40 km (at 1310 nm wavelength) or 80 km (at 1550 nm wavelength) and the attenuation is in a range from 10 to 28 dB for both cable lengths. This leads to a maximum attenuation of 0.7 dB/km at 1310 nm and of 0.35 dB/km at 1550 nm. The optional use of a fiber cable which is optimized for 1310 nm as well as for 1550 nm is described in ITU-T G.652 in more detail. For those types of fibers that satisfy this recommendation, an attenuation coefficient attribute of 0.5 dB/km (at 1310 nm) and 0.4 dB/km (at 1550 nm) is specified. Fig. 19 provides an overview of short haul and long haul cable attributes with reference to the corresponding specification.



51

Fig. 18 CC redundancy concept for the STM-1 interface

Fig. 19 Fiber cable attributes (acc. to ITU-T G.957 and G.652)

The intra-office category is not relevant here. CAN bus and IP/Ethernet link The IP/Ethernet stack of both CCs toward the HUB can be enabled. The CAN bus of the standby CC can be enabled. UTOPIA bus (CC/CSI), clock distribution bus, clock control link There is no difference compared to the non-redundant CC.



52

5.1.9 Architectural aspects The base rack configuration and optical splitter location is illustrated for the Node B 440/880 in Fig. 20. The Mounting Kit for Fiber Optic Cabling MK:FOCx consists of a bracket for mounting adapters, which are required for connecting the fiber optic cables of the Iub interface to the Core Controller with an optical interface module. The base shelter configuration and optical splitter location are illustrated for the Node B 441/881 in Fig. 21.

5.1.10 Software overview Both CCs, the active and the inactive, support the redundancy feature as well as the same software functions/features if they have the same UMR 3.5 software load. The RSC ensures that only one of them is active. The active CC can be updated remotely via the RC or locally via the LMT. The standby CC is updated via the active CC. After a software or database update, the active CC must be reset before the new configuration can be activated. As soon as the new CC configuration has been activated it provides the new configuration to the standby CC. The decision as to when to download the new configuration is made by the standby CC itself. The active CC provides the following information for the alignment of the standby CC: • Non-On-Board (NOB) file, containing the remote inventory data • Node B database • software load, identified by its software ID • PM files • log data The OAM data (PM files and log data) is aligned between both core controllers at regular intervals. Persistent changes in the database, starting new software loads or NOB file downloads are all initiated via operator commands.



53

Fig. 20 NB-440/880 base rack configuration and optical splitter location

Fig. 21 NB-44/8811 base shelter configuration and optical splitter location



54

5.1.11 Operation and maintenance (software-driven) 5.1.11.1 Redundancy concept The OAM tasks of the Node B are based on the hardware design. The essential surrounding in which the switchover behavior is embedded consists of the switching logic, the CAN Bus interface and the CC link. The CAN Bus is used in a master/slave approach where one master communicates with several slaves. The active CC takes over the master role while all peripheral cards act as a slave. Due to this arrangement the standby CC has only a passive role from the OAM point of view. Only one IP address can be used to access the CC. Consequently, the active CC can be directly accessed, the standby CC only indirectly with the help of the active CC and the CC-link. This system restriction must be considered (see software and database update) when a software or database update is made on the active CC. Due to the cold redundancy approach, the standby CC starts 10 seconds later than the active CC. The active CC does provide the required services and support of any feature. The standby CC does not provide any service or support of any feature.

5.1.11.2 Reset and switchover behavior of the redundant CCs The redundant CCs operate in so-called active / standby mode. A reset of one side affects the other side in a different manner. That means a reset of the active side causes a switching to the standby CC, whereas the reset of the standby CC does not affect the active side. The standby CC restarts again in standby mode. A radio commander switchover procedure for the operator allows toggling of the active / standby side in order to avoid a system wide impact when the active side is reset. A reset caused by the internal fault management of the CC may lead to an emergency switchover, see also chapter "Emergency Switchover Procedure".

5.1.11.3 Switchover procedures A switchover affects different system resources or system functionality that needs to be prepared for a cold redundancy.



55

Fig. 22 Example of the OAM interfaces

CAN bus There is a two-way approach that can handle the cold redundancy requirements, mainly the monitoring and detection of the hardware errors. The standby CC is isolated from the CAN-BUS point of view and only connected when the standby CC becomes active.

CC OAM interfaces The CC is embedded in an IP-based network. At switchover, the CC uses different methods to guarantee the connectivity from the IP point of view. The OMC (operator) has access to the active CC by using one unique IP address. This address does not change in the event of a switchover. A hub is mainly used to provide permanent connectivity between the CC and LMT/3rd party equipment. Without using a hub the LMT is directly connected to either CC-N or CC-E. Both CCs have different IP addresses for access via LMT. For 3rd party equipment, a routing function is provided by the active CC. The IP addresses for connections between CC, OMC, LMT and 3rd party equipment are used as follows:

Connection between CC and OMC In general, the IP addresses of the active / standby CC are identical, implying that by means of the RSC the standby CC is physically disconnected from the OMC. With this method only the active CC can be accessed.



56

Connection between CC and LMT The operator has unlimited access on the physical layer to both CCs by using 2 different IP addresses.

Connection between CC and 3rd party equipment A 3rd party manager uses the CC IP routing function to access a 3rd party equip-ment. The routing function will only be provided by the active CC. On the other hand, at the standby CC the 3rd party IP address is not configured. At switchover the active CC configures the 3rd party IP address in order to provide the required routing function. From the OAM access point of view, the following basic conditions have an impact on the CC cold redundancy: • The LMT IP address assignment is based on the physical slot number of the

CC. • The LMT that is primarily used for a direct CC connection must provide an IP

address selection to access either the CC-N or CC-E. • In general, only the 3rd party and IUB IP addresses are stored in the info model. • At startup the side information and working status of the CCs must be known

before the IP addresses are set. For example, the setting of the LMT-IP addresses based on the physical slot number (Side0 /Side1), whereas the 3rd party IP address assignment is based on the working status. On the standby CC the 3rd party IP address are not configured.

5.1.12 Normal switchover procedure A normal switchover will be initiated by the operator at the LMT or OMC. Use the RedundancySwitch command at the LMT, see CML:Node B. A normal switchover will be rejected when a software or database update is running or the standby CC is not aligned. During the switchover phase, commands entered by the operator are not accepted.

5.1.13 Emergency switchover procedure At emergency switchover a hardware reset is initiated that leads to a switchover to the standby side. An emergency switchover is triggered by the following failures: • Total hardware outage of the active CC. • Essential hardware resources of the active CC fail, for example E1 / STM-1

interfaces. Only failures caused by a hardware defect fall into this category, but not those generated by the pure line interface status.

• Software errors if no separate software escalation is supported by using different recovery levels.



57

5.1.14 Software and database update The software and database updates can be initiated either by the OMC or LMT. The LMT-based procedure for the NB-440 is described in two chapters of the Installation and Test Manual (ITMN): ITMN:NB-440 (software update) / ITMN:NB-440 (database update). The procedures for the other Node B types are described in the respective ITMNs. The transaction of the software download includes the download to both CC sides. After a successful transaction the software can be activated by the operator. The following paragraph describes the update procedure for the OMC. First, the new software load will be downloaded to the active CC and cross copied to the standby side. Activation of the update requires a reset of the active CC. After activation of the active CC a supervision timer is triggered to check whether successful communication between the CC and the OMC is accomplished. When the communication attempt was not successful during the supervision time the Node B initiates a fallback to the last running software load. After communication between the active CC and OMC is established, the new software load is marked as the running software load on the active and standby CC. The standby side receives the trigger from the active CC via the CCLink.

5.1.15 Data alignment Beside the software download mechanism initiated by the OMC or LMT, a steady data alignment via the CC-Link is necessary to avoid a data loss during a switchover. The data alignment includes the following data types: • PM file • LOG data • Change of persistent data in the database The alignment of the data types that are not directly changed by the operator, for example PM and LOG Files may be done on a time period basis whereas the change of operator settable attributes must be included in the transaction of the set command. The data alignment does not include the NOB file since it can only be changed and downloaded by the operator. The transaction of the NOB file download includes the download to both CC sides. In the event of a fresh CC installation, the NOB file needs to be newly downloaded to the active CC. An unsuccessful alignment causes a reset of the standby side with an implicit data alignment. Only after a successful data alignment is the OST (Operational state) of the standby side enabled again.



58

5.1.16 State management The CC does not have an Administrative State in order to maximize the service availability. A total outage can be avoided when a CC side is accidentally locked that is still able to provide service and a failure of the active CC occurs. Beside the standard state and status, information will be added that is used in the Info Model, like OST, AVS and ALS the STB. All the state and status information reflects the current CC behavior. Two different MOIs are provided for active and standby CC. As stated above, beside the standard state and status information used in the Info Model like OST, AVS and ALS, the STB is added. All the state and status information reflects the current CC behavior. After an emergency switchover, the standby CC (formerly active CC) restarts hardware error detection procedures and afterwards indicates its status information to the (new) active CC.

5.1.17 Info model Beside a second instance of the CC, the redundancy scheme includes a switchover capability to change the working state directly from active to standby. Furthermore, each CC instance provides a reset procedure to reset the CC individually.

5.1.18 Configuration data The standby CC is included in the standard configuration that represents the maximum hardware installation.

5.1.19 Remote inventory During installation of the redundant CC the NOB file is downloaded from the LMT, including the Remote Inventory (RI) records for the redundant CC. The existing NOB file on the active CC has to be updated accordingly.



59

5.1.20 Functional split 5.1.20.1 Node B PF2 The Node B supports the RC data alignment that also replicates all of the call processing related data to the standby CC to back up all stable connections. The Node B offers backward compatibility to deployed Node Bs.

5.1.20.2 RC/ToolSet The RC/Tool Set handles the OAM data alignment, as well as the operator-initiated switchover commands for the new CC software load. The active/standby configuration of the CC allows fault processing on the active side. Since the standby side is isolated from the external signals, the full functionality can only be checked when the standby side is activated. However, no automatic switchover is supported from the Node B. Instead, the operator has to decide in which time period a switchover has to be initiated from the RC with the help of a scheduled switchover command.

5.1.20.3 LMT The LMT handles the operator-initiated switchover commands for the new CC software load. A hub configuration is mainly used to provide permanent connectivity between the CC and the LMT/OEM equipment.

5.1.20.4 Man-machine interface The redundant CC is included in the panels of the RC and the LMT. Operators are informed about the mode of both CCs. RC and LMT both support the new action, which is switching between the active and the standby CC. An additional alarm message informs about the failure of a single CC.

5.1.21 Operating the feature The following operations can/must be initiated by the operator: 1. Perform normal switchover, e.g. with RedundancySwitch command at the LMT

⇒ "Normal Switchover Procedure" / CML:Node B 2. Perform software and database update ⇒ "Software and Database Update" NB-

440: ITMN:NB-440 3. Perform data alignment of the NOB file ⇒ "Data Alignment"



60

5.2 Node B synchronization All clock signals in the Node B are derived from a high-accuracy 38.4 MHz master clock. The master clock generator on the LIU board consists of an oven-controlled VCXO (OC-VCXO) which is synchronized with a high-accuracy reference clock signal by a Phase Locked Loop (PLL). The reference clock is derived from the Iub interface (E1/J1or STM-1) or from an external reference connected via the external synchronization input. External clock synchronization is supported via a coax-connector on OVPT. The clock signal is applied to the Sync Input at the front panel of the Core Controller (CC-N) via a 50 & coax cable. Termination is possible by applying a 75 & coaxial load to the Sync Output of the Core Controller. If the redundant Core Controller is present, both CC-E are interconnected according as shown below.

Termination is at CC-E in this case. Possible synchronization clock input signals are • 1544 kHz, 2048 kHz (TTL level), CCV3 additionally supports 1 Hz (TTL level) • 10 MHz, Sine, 1 V (RMS) The synchronization of the Node B is monitored by means of a proper state management function, which is implemented in the Node B. It is possible to configure clock priorities to the different clock sources online.

5.2.1 Unknown Initial value of clock accuracy state attribute after system start-up.



61

5.2.2 Normal regulation - medium accuracy In this state, the OC-VCXO is synchronized to the reference line by a PLL using a medium time constant (PI controller, loop frequency 2 MHz). If the relative deviation between OC-VCXO and reference clock drops below the high accuracy threshold, the ’normal regulation mode high accuracy’ is entered. If the frequency deviation exceeds the medium accuracy threshold, the holdover mode medium accuracy is entered. In case of loss of the Iub line or if the limit of the OC-VCXO pulling range is reached, the ’hold over medium accuracy’ is entered as well.

Fig. 23 Node B synchronization states



62

5.2.3 Normal regulation - high accuracy In this state the OC-VCXO is synchronized to the reference clock by a PLL using a long time constant (PI controller, loop frequency 160 µHz). The reason for the long time constant is the suppression of possible jitter/wander on the Iub line. If the frequency accuracy of the Iub line is within the limits specified in ITU-T G.811 and the jitter/wander is within the limits for a E1 line according to ITU-T G.823, a frequency accuracy of <50ppb according to 3GPP TS 25.104/25.141 is achieved. A transition to the ‘hold over mode high accuracy’ can occur under the following conditions: a) The reference source is considered to be not reliable anymore. b) The Iub line is lost or the limit of the OC-VCXO pulling range is reached. Furthermore the OC-VCXO setting values filtered by a low pass filter with a cut-off frequency of 5.5 µHz, to generate a long term averaged OC-VCXO setting value, the so called learned setting.

5.2.4 Holdover mode - high accuracy In this state the regulation process is stopped and the last valid OC-VCXO setting is held. The frequency accuracy in this mode depends on the ageing (0.5 ppb/day) and temperature stability (20ppb over operating temperature range) of the OC-VCXO. The ‘normal regulation mode high accuracy’ is entered again only if the Iub line is considered reliable again. If this is not the case within the maximum free run time, the ‘hold over mode medium accuracy‘ is entered.

5.2.5 Holdover mode - medium accuracy In this mode the OC-VCXO setting is set either to the learned value (if available) or to the factory calibration value. In the latter case the frequency accuracy depends on the ageing of the OC-VCXO since factory calibration. If an Iub line is present and the frequency deviation falls below the medium accuracy threshold value, the ‘normal regulation mode medium accuracy’ is entered.



63

5.3 Channel Coding card (CHC) The main function of the CHC card is channel coding and decoding. It can simultaneously perform channel coding and decoding for both the traffic channels and the control channels (common channels) in one card. On the uplink path, the CHC card receives and dispreads the uplink data transmitted from the DRIC on the serial link. The CHC card de-codes the dispread data depending on its symbol rate and channel type. The decoded data is transmitted to the CC via the UTOPIA bus. On the downlink path, the CHC receives and terminates the ATM-formatted data transmitted from the CC via the UTOPIA bus. The CHC encodes the received data depending on its symbol rate and channel type. The encoded data is transmitted to the DRIC. The CHC card equalizes the multi-path propagation via the rake receiver and maximum ratio combining. The B-SHF of the NB-880/NB-881 supports up to 10 CHCs. The required number of cards depends on: • the volume of bearer service capacity (traffic functions) • the sectorization and cell range (control functions) Three types of Channel Coding Cards can be used in the NB-880/881: • The higher integrated Channel Coding Card CHC96 offering a processing

capacity of 96 channel elements and 144 AMR equivalent (Adaptive Multi-Rate equivalent) per card. The CHC96 also supports HSDPA, offering the same processing capacity as in non-HSPDA mode. It simultaneously processes non-HSDPA channels and HSDPA channels. In the first release HSDPA is supported for 1 cell/sector in case of 2/2/2 configuration, only.

• The Channel Coding Card CHC48 offering a processing capacity of 48 channel elements and 72 AMR equivalent per card

• The newly developed hs-CHC (description: see Chapter 2, "hs-CHC"). The hs-CHC simultaneously supports HSDPA-specific channels and functions as well as normal channels. The hs-CHC’s maximum performance is equal to 96 CEs and an AMREQ of 144.

For AMR services, the available CE are limiting the processing capacity, while for higher data rates the available AMR equivalent are limiting the processing capacity of the CHC. The higher integrated CHC is fully hardware- and software-interface compatible to the CHC48. The NB-880/881 can be equipped with a mixture of higher CHC96 and CHC48.



64

RACH resources for the uplink path and FACH/PCH resources for the downlink path must be assigned to each cell. Generally, the required resources for the uplink path are dominant. The number of required RACH resources depends on the size of the cell radius R: • R ≤ 5 km: 8 CE/cell (CHC48) or 6 CE/cell (CHC96), max. 6 cells per CHC • 5 km < R ≤ 20 km: 16 CE/cell (CHC48) or 6 CE/cell (CHC96), max. 3 cells per

CHC • R > 20 km: 48 CE/cell (CHC48) or 6 CE/cell (CHC96), max. 1 cell per CHC General characteristics of the CHC card.

Number of services per CHC



65

Block diagram of the CHC

Fig. 24 Channel Coding Card CHCFV1

Control and UTOPIA interface block The control block consists of the main processor, peripheral ICs and memory units. It performs UTOPIA interface control and overall intra-card supervision and control. The control block exchanges control data with the CC card. The UTOPIA interface block interfaces with the CC card and terminates the lub user plane. On the downlink path, it receives transport channel data and control data from the CC card and transfers it to the coder block. On the uplink path, it receives de-coded data and control data from the de-coder block and transfers it to the CC card.

CAN block The CAN block consists of a CAN microprocessor, a transceiver and a memory unit. It performs supervision and control data communication with the CC card on a CAN bus.

Coder block The coder block receives downlink transport channel data from the UTOPIA interface block and performs coding procedures. It sends the encoded data to the DRIC interface block.



66

Searcher block The searcher block receives uplink data from the DRIC interface block. It performs channel path estimation, tracking, and RACH preamble detection. The searcher block provides path information to the finger block.

Finger block The finger block receives uplink data from the DRIC interface block, and performs dispreading and rake combining based on the path information provided from the searcher block. It sends the rake combined data to the de-coder block. The rake receiver has 8 fingers.

Decoder block The decoder block receives rake combined data from the finger block, and performs decoding procedures. It sends the de-coded data to the UTOPIA interface block.

5.3.1 CHC combined mode The combined mode improves the channel card capacity by a combined support of common and dedicated channels on a single channel card. This provides a more efficient usage of the Node B hardware resources.

5.3.2 Resource consumption rules From a hardware point of view the channel card is structured into a number of independent resource subpools. Within the following logical model for the channel card resources has been defined that is valid for CHC FV 1 and FV 2.



67

Downlink

Resources

Uplink

Resources

Coder DSP

24 CE, 36 AMReq

Finger ASIC,Decoder DSP,SearcherASIC,SearcherDSP:8 CE, 12 AMReq





Coder DSP

24 CE, 36 AMReq


Fig. 25 Logical model for channel card resources

41611384 kbit/s DL/64 kbit/s UL



1111AMR Voice

725484Common channels (RACH+FACH+PCH) for very large cell size

245164Common channels (RACH+FACH+PCH) for large cell size

12584Common channels (RACH+FACH+PCH) for normal cell size

Uplink AMR equivalents

Downlink AMR equivalents

Uplink (UL)ChannelElements (CE)

Downlink (DL) Channel Elements (CE)

Channel type

Fig. 26 Resource requirements of different transport channels



68

The different resource pools are mutually independent. A dedicated channel has to be completely placed into one of the downlink subpools whereas uplink subpools can be pooled to support also bearers with 384 kbit/s uplink bit rate. CHC FV1 can combine 2 uplink resource subpools and CHC FV2 can combine 3 uplink resource subpools. Furthermore, an appropriate number of uplink subpools can be bundled together for the support of common channels with larger cell range whereas downlink common channels can be distributed over the two subpools. Each subpool could handle common and dedicated channels when the CHC works in combined mode. Furthermore, the resource requirements of common and dedicated channels is asym-metrically because the common channels require mainly uplink processing resources whereas the dedicated channels require mainly downlink processing resources (be-cause the downlink rate is usually larger than the uplink rate, see Fig. 25). This asymmetry of the resource requirements of common and dedicated channels can be used to improve the resource utilization applying the combined mode. For example, considering a scenario where 3 large cells have to be supported together with bearers that have a data rate of 384 kbit/s downlink and 64 kbit/s uplink the following allocation strategies could be supported: • Strategy a:

1 CHC-C supporting the common channels of 3 large cells and additionally 2 CHC-T supporting 8 x 384 kbit/s data bearers

• Strategy b: 3 combined CHC-C/T each supporting the common channels of one cell and additionally 4 x 384 kbit/s data bearers

Therefore, for strategy a 8 x 384 kbit/s can be supported whereas in strategy b 12 x 384 kbit/s can be supported. It can be shown that the distribution of common channels over channel cards provides a higher total resource utilization than the concentration of common channels on the minimum number of channel cards as long as the downlink traffic is larger than the uplink traffic, which is usually the case. Therefore, the common channels should be distributed over as many channel cards as possible, i.e., we will only support strategy b. However the common channels belonging to one cell are never separated, i.e. the different common channels of one cell are always put together on the same CHC.



69

5.3.3 Supported combinations On a single CHC-C/T card the following common channel combinations have to be supported: • OTSR with normal cell size • 1 normal cell • 1 large cell • 2 normal cells • 2 large cells • 1 normal cell + 1 large cell • 3 normal cells • 2 normal cells + 1 large cell • 1 normal cell + 2 large cells • 4 normal cells • 5 normal cells All other combinations either occupy a whole channel card or can be composed from these basic configurations by several channel cards.

5.3.4 Channel allocation strategy 5.3.4.1 Allocation of common channels between channel cards The CC waits a certain time until most of the channel cards have finalized their boot phase and then the CC decides how the channel cards will be initialized (common channel allocation). This startup sequence is also beneficial with the CHC96, because this card has different resource pools for common and dedicated channels and therefore, the common channels can be allocated on a CHC96. The startup sequence is illustrated in Fig. 27.

5.3.5 Allocation of common channels within a channel card Besides the global allocation of common channels between channel cards, a channel card internal resource allocation of common channels onto subpools is required. This strategy should distribute the common channels over the two subpools to maximize the number of high bit rate dedicated channels that can be supported.



70

5.3.6 Allocation of dedicated channels between channel cards The following algorithms may be used for the allocation of DCHs to CHC-C/T channel cards • Load Balancing: The load with respect to the no. of occupied uplink channel

elements that are allocated for dedicated channels will be balanced. This provides the lowest number of call losses when a CHC failure occurs

• Overflow Algorithm: The dedicated channels will be allocated with highest priority (priority 1) on the first CHC, with priority 2 on CHC 2 and so on. Minimizes the no. of call losses for new call requests

• More complex algorithms may be used when bearers with higher uplink than downlink rates may become available

5.3.7 Allocation of dedicated channels on one channel card The allocation of the dedicated channels onto a channel card is optimized by a defragmentation of the resources. Therefore, no concrete algorithm has to be defined here.

5.3.8 Reallocation strategy Since the dedicated channels are allocated in an arbitrary sequence the unoccupied resources will be distributed over different channel cards and different subpools of channel cards. Therefore, the resources have to be reallocated using the following procedures: • Channel card defragmentation • Call context migration These procedures have to be supported for the channel cards that serve dedicated channels.



71

Start CHCsetup

Round robin allocationof common channels

on channel cards (onlyallocation and

reservationbut no channel setup

Initialize CHC and inform CHC aboutallocated common channels (no setup)

CHC resourceindication

Time out forstartup

End ofCHC setup

Increase CHCnumber by one

CHC number :=CHC number -1

CHC number > 0 ?no

Fig. 27 Channel card initialization sequence

5.3.9 Channel card defragmentation Channel card defragmentation is a channel card internal procedure to concentrate the bearers within a minimum number of subpools in order to get free resources for new high bit rate bearers, i.e. the bearers are reallocated from one resource subpool to another resource subpool. Channel card defragmentation can be independently applied to uplink and downlink resources to achieve a best packaging of the uplink and downlink bearers as illustrated in the following figure. This is illustrated in Fig. 28.

5.3.10 Call context migration Call context migration is a procedure handled by the Core Controller in order to concentrate the bearers on certain channel cards to obtain some spare capacity. This is illustrated in Fig. 29. This procedure should be supported also for the CHC-C/T. The call context migration shall be triggered when a card is locked or when the bit rate of an already existing bearer has to be increased. It is currently not supported for the scenario that an incoming bearer request cannot be handled due to a lack of resources. I.e. ongoing calls are handled with a higher quality of service than new call requests.



72

5.3.11 Redundancy handling The channel coding cards provide redundancy by means of load sharing. When the combined mode channel card fails the following failure handling procedure shall be applied (see Fig. 30) I.e., the common and dedicated channels are reallocated on the remaining boards. The reallocation shall fulfill the following requirements: • Common channels shall be reestablished as fast as possible • The number of common channels that have to be reestablished shall be

minimized • The number of dedicated channels that have to be reestablished shall be

minimized • Dedicated channels shall be saved if possible. A unique procedure for the reestablishment of dedicated channels shall be implemented irrespectively whether a channel card fails or is rebooted. This reduces the development and test effort. When a dedicated channel cannot be reestablished due to a lack of resources the Node B should send a radio link failure towards the RNC with the corresponding failure cause. In general the redundancy algorithm should minimize the impact on common and dedicated channels in case of channel card failure.



73

Common Channels

DL

UL

Dedicated Channels

Free Resources

2 3 12 3 1Defrag-men-tation

2 3 1

21 3

3 21 3 DL

UL

CHC1

CHC1

Fig. 28 Illustration of channel card defragmentation

Common ChannelsDedicated Channels

Free Resources

CallContext

Migration

4 5 6

354 6 DL

ULCHC2

2 3 1

3 21 3 DL

ULCHC1

DL

ULCHC2

2 3 1

3 21 3 DL

ULCHC1

54 6

4 5 6

Fig. 29 Illustration of call context migration

C H C - C /T

C H C -

C /T

F a i lu r e

C H C -

C /T . . .

C H C - D is -

a b le d

C H C - C /T

C H C -

C /T . . .

C o m m o n C h a n n e ls

D e d ic a te d C h a n n e ls

Fig. 30 Redundancy handling of CHC-C/T



74



75

5.3.12 MMI requirements The Node B should indicate to the OMC-B and LMT whether a channel card serves also common channels or only traffic channels. Furthermore, this should be also indicated by the LED on the front panel of the CHC. Finally, it is very essential to indicate to the operator the uplink and downlink channel elements and AMR equivalents that are available for the dedicated traffic channels which depends on the actual allocation of the common channels on the different channel cards. This allows the network operator to verify the efficiency of the combined mode in certain network configurations.

O&M Parameters

Parameter Semantics description

Type and reference

Managed Object Class (MOC)

Access Default para-meter

Operator configurable

CCH_on_CHC Indicates whether a CHC serves common

channels

Boolean Ch Read None Only readable

No_of_Traffic_CE_UL Indicates the total number of

uplink CEs available for

traffic

Integer (0, 1, …,

96)

Ch Read None Only readable

No_of_Traffic_CE_DL Indicates the total number of downlink CEs available for

traffic

Integer (0,1, …,

96)


No_of_Traffic_AMReq_UL Indicates the total number of

uplink AMR equivalents available for

traffic

Integer (0,1, …,

144)


No_of_Traffic_AMReq_DL Indicates the total number of downlink AMR

equivalents available for

traffic

Integer (0, 1, …,

144)




76

5.4 Digital Radio Interface Card (DRIC) The Digital Radio Interface Card (DRIC) provides a multiplexing, routing and splitting function of the baseband signals and the spreading functionality in the downlink direction. The DRIC comprises 6 digital radio interfaces which are CPRI-compliant (Common Public Radio Interface). Alternatively to normal redundancy, there is a HW-preparation for 50/50 redundancy using the loadsharing principle. The control as well as the operation and maintenance information is received by the DRIC via the UTOPIA or CAN interface and forwarded via the CPRI interface to the CATs and/ or RRHs. The NB-880/NB-881 can be equipped with the DRIC12_12 as well as with the DRIC24_24oe. Since the DRIC24_24oe is downwards compatible, mixed configurations are possible. The two types of DRIC differ in the following way:

5.4.1 DRIC characteristics

5.4.1.1 Capacity characteristics of the DRIC12_12 / DRIC24_24oe



77

Fig. 31 DRIC Card

Fig. 32 Block diagram of the DRIC



78

5.4.1.2 Characteristics of the CPRI interface DRIC and CAT are solely linked by the CPRI. There is no extra clock line from DRIC to CAT.



79

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 33 DRIC-CAT Interface Diagram and Characteristics of the CPRI



80

5.5 Combined Amplifier and Transceiver module (CAT)

The CAT module is a radio-frequency (RF) unit. On the downlink path it receives the digital I/Q (Inphase/Quadrature) baseband signal from separate input I/Q data streams via the CPRI from the Digital Radio Interface Card (DRIC). The CAT module performs channel filtering, upconverts this signal to the required transmitting frequency. This also amplifies the generated RF signal to a nominal output power level at the 7/16 antenna connector of the DUAMCO. On the uplink path, the CAT module receives RF signals from the DUAMCO, downconverts the signals, and transmits the resulting I/Q data stream via the CPRI. On the downlink path, the CAT works either as a single-carrier power amplifier or as a multi-carrier power amplifier. The entire average output power capability is the same in both cases. The CAT module applies advanced amplifier concepts such as adaptive Digital Predistortion (DPD). The CAT amplifies the downlink signal to a nominal level depending on the type of CAT. There are two types of CAT modules: CAT40 and CAT20, providing a different number of TX and RX carrier paths. The CAT40 offers a higher output power of 40 W and increased carrier capability enabling additional cell configurations (hardware-prepared for up to 4/4/4 compared to the CAT20. The CAT40 supports 2 independent RX paths each with dual carrier capability (suited for dual carrier Rx-diversity). CAT20 and CAT40 modules can be mixed within one NB-880/881. The NB-440/NB-441 can also be equipped with the next generation CAT ngCAT. The ngCAT can operate either as CAT40 or as CAT20. It covers the full functionality of the CAT40 but benefits from a higher efficiency and lower OPEX. The ngCAT provides: • at least 4 TX carrier paths • at least 8 RX carrier paths • 20 W or 40 W operation, depending on Node B configuration The ngCAT is HW-prepared to support future features like: • higher bandwidth (60 MHz) • additional antenna carriers per CAT • additional cells per Node B



81

5.5.1 CAT20 / CAT40 characteristics

5.5.1.1 RF interface characteristics of the CAT20/40 module



82

5.5.1.2 Supported configurations using CAT40



83

Fig. 34 CAT20 module

Fig. 35 Block diagram of the CAT module



84

5.6 Repeater card (REP) The Repeater (REP) provides a repeater function for the base-band signals and is in-stalled between the CHC cards and the TRX cards. At least one REP card must be installed in the B-SHF. An additional card can be installed for redundancy. On the downlink path, the REP card multiplexes the downlink data on Time Division (TD) basis, and sends them to the TRX cards. The REP separates these downlink signals according to their originating users and multiplexes them to the destination sector. On the uplink path, the REP card receives the signals from the TRX cards and sends them to the CHC cards. The REP card splits these uplink signals and distributes all signals to each CHC card.

REPTX The REPTX receives the downlink packet signal from the CHC cards. It synchronizes the signals with the internal clock, sorts them according to antennas, prioritizes them, and sends them to the TRX cards.

REPRX The REPRX receives the uplink signals from the TRX cards. It synchronizes the signals with the internal clock, checks them for parity errors, performs format conversion if necessary, and sends them to the CHC cards.

Control Block The control block consists of the main processor, peripheral ICs and memory units. It performs UTOPIA interface control and overall intra-card supervision and control. The control block communicates the control data to the CC card.

UTOPIA Interface Block The UTOPIA interface block interfaces the CC card. It receives control data from the CC card and transfers it to the control block, and vice versa.

CAN Controller The CAN controller consists of a CAN microprocessor, a transceiver and a memory unit. It communicates supervision and control data to the CC card via a CAN bus.

CHC Interface Block On the downlink path, the CHC interface block receives packet data from the CHC card, de-serializes it and transmits it to the REPTX. On the uplink path, the CHC interface block receives data from the REPRX, serializes it and sends the data to the CHC card.

TRX Interface Block On the downlink path, the TRX interface block receives packet data from the REPTX, serializes it and transmits it to the TRX card. On the uplink path, the TRX interface block receives data from the TRX card, de-serializes it and sends the data to the REPTX.



85

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Block diagram of the REP card

Fig. 36 Block diagram of the REP card



86

5.7 Transceiver card (TRX) The TRX card consists of: The TRX card consists of: • Transceiver Base Band Block (TRX BB) • Radio Frequency Block (RF)

The Radio Frequency Block (RF) consists of: – Transmitter Block (TX) – Receiver Block (RX)

On the uplink path, the RX block limits the bandwidth of the RF signal received from the DUAMCO. The RF signal is subsequently converted into an IF signal and sent to the TRX BB. The ASIC unit of the TRX BB converts and de-modulates the IF signal into a digital I/Q baseband signal that is sent to the REP card. On the downlink path, the I/Q baseband signal received from the REP card is spread and scrambled by the ASIC part of the TRX BB unit. The ASIC generates a QPSK signal and converts it into an IF signal. The TX block subsequently converts the IF signal over two intermediate stages into an RF signal that is sent to the LPA. The TX part is prevented from carrier leakage by applying frequency offset to the base band I/Q signals, thus the modulation accuracy can be improved. The constant level of gain of the RF signal is ensured by the Power Level Control Loop (PLC). Both the uplink and the downlink path have a diversity configuration. Since TX diversity is optional (hardware-prepared), one TX circuit is not used for single TX. The B-SHF provides six slots for TRX cards. At least one card must be installed. The required number of TRX cards depends on sectorization and configuration. The TRX card sends a report to the CC if an output level abnormality such as level degradation is detected. It is possible to start or stop output from each branch of diversity. The TRX card measures the total output power used for downlink signals. The output level can be adjusted by using hardware or software. Adjustment for each branch of diversity is also possible. Output with scrambling or without modulation can be selected. Modulation mode can be selected for each branch of diversity. The TRX card can be blocked locally. The card or carrier can also be blocked from the OMC or the LMT. If an attempt is made to block a card or a carrier that is actually used for transmission, the carrier or card is usually set to reserved-for-blocking state and blocking finishes when the transmission ends. At power-on, the TRX card locks transmission and receiving frequencies to the predetermined values. It is possible to lock the transmitting and receiving frequencies used by the synthesizer to the predetermined values. The TRX card supports fixed duplex spacing of 190 MHz between uplink and downlink carrier frequency. The TRX card provides a carrier raster function. With the carrier raster function, the sending and receiving frequencies can be shifted forward or backward in increments of 200 kHz. The TRX card can change transmission and receiving frequencies. Fig. 38 shows the block diagram of the TRX card.



87

Fig. 37 Transceiver TRX

Fig. 38 Block diagram of the TRX



88

5.8 Linear Power Amplifier (LPA) The LPA amplifies the downlink signal received from the TRX. The Multi Carrier Power Amplifier (MCPA) is designed for operation with • one UMTS FDD carrier per antenna with a nominal output power of 20 W or • two UMTS FDD carriers per antenna with 20 W as the nominal average sum

output power, i.e., each carrier will be radiated with 10Wper antenna (hardware-prepared).

To be capable of supporting two carriers, the LPA’s signal path comprises of a combiner and a power amplifier enabling two separate signals from the TRX cards to be combined before amplification. The LPA amplifies RF signals received from the TRX to the predetermined output level. If the LPA detects that the input level exceeds the predetermined limit, it stops the output to protect the internal system from damage. The LPA detects the rate of distortion caused by multi-carrier amplification and suppresses the distortion rate so that it does not exceed the limits given by the 3GPP standards. This is done by the so-called feed-forward approach. Operation and maintenance information such as alarms, status mode and PID is supported by a CAN bus. If the power amplifier is used in a single-carrier configuration, the unused RF input must be terminated by a 50 W terminator. The nominal gain of the LPA is 44.1 dB. The LPA delivers the following RF output power level: • one carrier: 44.1 dBm • two carriers: 41.1 dBm for each carrier, therefore the average sum output power

is always 44.1 dBm



89

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 39 Linear Power Amplifier LPA-MCAFV1



90

5.9 Tower Mounted Amplifier (TMA) The TMA is an optional but highly recommended unit as it compensates cable losses in the uplink and thus ensures lower noise disturbance. High selectivity filters ensure high TX/RX isolation enabling the reception of low signal levels in the uplink. It therefore improves link quality and link availability at the cell borders.



91

5.9.1 The TMA performs the following functions • Amplifying the uplink signal received from the TX/RX antenna with a low-noise

figure. The receive path consists of a low-noise amplifier (LNA) and the RX part of the duplex filters.

• Feeding the overall Node B downlink signal transmitted to the TX/RX antenna. The transmit path consists of the TX part of the duplex filters.

The LNA has two parallel gain elements: • If a single failure occurs, operation continues with reduced gain. • If both gain elements fail, or the supply of the TMA fails, the LNA is bypassed by

a fail-safe switch. There are three variants: • TMA

The TMA is always installed outside the Node B cabinet and close to the antenna. The TMA thus achieves fixed sensitivity independently of feeder cable length. With the DUAMCO acting as a combiner inside the cabinet, only one feeder cable is required for the TX signal and RX signal. In addition, the feeder cable supplies the TMA with 12 V DC and alarm signals.

• DTMA In addition to the TMA, a Dual Tower Mounted Amplifier (DTMA) is provided for the NB-440/441 and NB-880/881. The DTMA includes two TMA units in a single housing and is very efficient in combination with a cross-polarized antenna. The RET module is only contained in the DTMARET variant.



92

• DTMARET A DTMA including RET control (DTMARET, see Fig. 3.1) is available to support a Remote Electrical Tilt (RET) module (2-wire bi-directional bus with 9.6 kbps). The DTMA provides the interface to the DUAMCO and the RS485 interface to the RET module. The IF converter in the DTMA evaluates and routes the signals coming from the DUAMCO to the DTMA itself or to the RET module. The signals are sent via the HDLC protocol. The RET module sends information and alarms on the RS485 interface via the DTMA to the DUAMCO. The RET capable DUAMCO receives/sends the RET specific commands from/to the CC. The power supply of the RET module is integrated within the DTMA. The nominal DC voltage for the DTMA and the RET module is 12 V. The technical solution consists of an RET module containing a stepper motor which adjusts a phase shift within the antenna. The stepper motor is controlled via an RS485 interface connected to the TMA. Signaling and DC power from the DUAMCO to the RET module via the TMA and vice versa is transported through the antenna feeder cable. The stepper is located directly under the antenna. For more information on the whole Remote Antenna Down tilt feature see TED:UTRAN common.

The TMA is a two-port RF unit. Two TMA modules are required for each sector to support the RX main path and the RX diversity path. The TMA consists of one duplexer subsystem, a triplexer, a LNA with a fail-safe path and a bias & signaling board. TMA signaling and DC power supply are provided through the antenna cable. The DTMA is a four-port RF unit that consists of two identical TMA sub-modules. One sub-module is used for the RX main path and the other for the RX diversity path. One DTMA module is thus required for each sector. Each DTMA sub-module consists of two RF ports, a duplexer subsystem, a triplexer, a LNA with a fail-safe path and a bias & signaling board. For each sub-module, signaling and DC power supply are provided through the associated antenna cables. Fig. 40 shows the block diagram of the DTMA. In addition to the DTMA, the DTMARET contains the RS485 interface and the IF converter within the TMA main sub-module. Fig. 41 shows the block diagram of the DTMARET. One TMA unit can handle UMTS downlink signals with a total signal RMS power of +46 dBm and a signal peak power of +61 dBm. The DC for the TMA/DTMA is supplied via the inner conductor of the Node B 7/16 connector. The status monitoring and alarm signals are exchanged via the coaxial feeder cable. The information is modulated on a carrier in a low MHz range.



93

Block diagram of the DTMARETConcept of TMA and DTMA

Fig. 40 TMA and DTMA

Fig. 41 DTMA-F Characteristics of TMA/DTMA/DTMARET



94

5.10 Duplex Amplifier Multi-Coupler (DUAMCO) On the uplink path, the Duplex Amplifier Multi-Coupler (DUAMCO) amplifies the receive signal from the antennas and splits it up to the diversity receivers. The receive path consists of a Low Noise Amplifier (LNA) followed by a power splitter providing four identical outputs for the TRX input. On the downlink path, the signal received from the LPA is sent to the antenna. The transmit path consists of a duplexer, a triplexer and an antenna-monitoring unit for the TMAs. The triplexer provides the TMA’s DC power and the signaling to the RF antenna feeder connection. The duplexer combines the transmit and receive paths to the common antenna connector. The duplex filter provides receive and transmit band filtering. Two types of DUAMCO are available for the NB-420/440/441 and NB-860/880/881: DUAMCORT (see Fig. 42) The DUAMCORT module consists of two electrically identical modules (0/1). Each module has a transmit path and a receive path with a single connector for the antenna feeder cable, i.e., one antenna connector per module is available. DUAMCORET The DUAMCORET has the same functionality as the DUAMCORT. In addition, it supports, in combination with the DTMARET, DC supply and signaling function for a Remote Antenna Down tilt (RET) module. A triplexer is integrated in one of the antenna paths to provide these functions. The control and alarm signals of the RET module are embedded within an HDLC protocol. The DUAMCO de-modulates the messages and translates them into CAN protocol and vice versa. The gain of each receive path is adjustable for an amplifier multicoupler (AMCO) configuration or multicoupler (MUCO) configuration: • MUCO mode

The MUCO mode is used if TMA units are installed. A built-in attenuator ensures constant attenuation between the TMA and the DUAMCO independently of cable losses.

• AMCO mode The AMCO mode is used if no TMA is mounted. In this mode, the LNA in the DUAMCO amplifies the uplink signal.

Operation and maintenance information such as alarms, status mode and PID is sup-ported by a CAN bus. Calibration data is also accessible via a CAN bus allowing compensation of the DUAMCO’s frequency response in the TRX modules. RX outputs should be terminated if they are not used. Disconnecting an RX output termination does not result in a serious loss in the other outputs. To adjust the cable and feeder losses use the DIP-Switch Settings for Mode and Attenuation as shown in Fig. 42.



95

Attenuation part of the table is valid for all DUAMCOs, RET setting is valid for DUAMCOs with RET-option only

Fig. 42 Duplex Amplifier Multi-Coupler DUAMCORTFV3

Tables are valid for all DUAMCOs

Fig. 43 DUAMCO characteristics



96

5.10.1 Attenuation adjustment Antenna cable type and length are decisive for the attenuation in the relevant frequency spectrum. The next page shows the appropriate formula to calculate the attenuation and the attenuation adjustment. The calculation of value is valid for all versions of DUAMCOs



97

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Attenuation Adjustment:Antenna cable type and length are decisive for the attenuation in the rele-vant frequency spectrum. The calculation of value is validfor all versions of DUAMCOs

Fig. 44 Block diagram of DUAMCO with RX and TX diversity (DUAMCORT)



98

5.11 4-port Ethernet Hub (EH4) The 4-port Ethernet Hub (EH4) has the functionality of an Ethernet repeater hub. No switching function is required. The Ethernet Hub provides four ports for communication routing between: Core Controller (CC) Core Controller Redundancy (CC-Red) Local Maintenance Terminal (LMT) External Ethernet equipment If additional devices are connected to the network, a second Ethernet Hub must be installed. Thus, 6 ports are available for operational service. The Ethernet Hub EH4 is a 10BaseT Ethernet repeater. The repeater function is contained in an integrated circuit. The hub supports 4 RJ-45 ports with the same functionality. The ports and the data input/output pins of the integrated circuit are galvanically isolated by transformers. An integrated quartz oscillator provides the internal system clock. Hence no synchronization to any Node B clock is required. The maximum power consumption of the EH4 is 5 W.



99

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 45 Example for a Ethernet Hub configuration



100

5.12 Alarm Collection Terminal Modules (ACT) The physical function of the ACT is to interface the alarm and command signals between the CAN BUS and the alarm/command connectors of Node B. The ACT is not redundant, but the Node B subsystem will still work even if the ACT fails. The ACT functionality is provided by a set of modules: • a processor board (ACTP) • an interface board for external signals (ACTA) • several interface modules for internal signals (ACTCB, ACTCS, ACTCS2) The interface for operator-specific alarms (site inputs and site outputs) is supported by the Node B base rack/shelter. For this purpose, an ACT master module (ACTM) is installed in each base rack/shelter. The ACTM module consists of an ACTP board and an ACTA board. If no site inputs/outputs are required, an ACTP suffices. The ACTCM, a different kind of master module, is required for controlling the alarm collection in the service area of the NB-441 or NB-881 base shelter and the NB-441 or NB-881 service2 shelter.



101

ACTMFV1 (side view)

ACTMFV1 (top view)

ACTPV3 (front view)

Fig. 46 ACTMFV1 - this module consists of the ACTAFV1 and ACTPV3 and is located at the EMI-Panel

Fig. 47 ACTCBFV1 with connectors



102

The ACTCM consists of an ACTP board and an ACTCS board. The ACTP performs the following tasks: • interfacing the CAN bus • collecting all alarms for units which have no access to the operation and

maintenance bus or to the CC • collecting so-called cabinet-specific alarms (for example Door open, Smoke,

FAN) • supervising the temperature via an external temperature sensor KTY19 • adjusting the rack address The ACTA performs the following special tasks: • collecting so-called operator-available alarms (24 site inputs and 8 site outputs). • indoor lightning protection The rack address is selected via a switch located at the ACTP board of the single rack/shelter section. The optional mounting kit OPEXAL can be used to prevent overvoltage on the external alarm lines which are routed to the Alarm Collection Terminal Master (ACTM) of the Base cabinet. The alarm interfaces of ACTM itself support the indoor lightning protection level. Therefore, OPEXAL is only required for the rack applications if outdoor lightning protection requirements shall be fulfilled. For detailed information about respective connectors refer HWMN: Node B Cards/Modules.



103

ACT modules in the NB-441 and NB-881 base shelter. The same types of ACTM and ACTCB are used for the NB-440 and NB-880 base rack.

ACT modules in the NB-441 and NB-881 service2 shelters.The cabinet inputs of the ACTC can be used forLE alarms, battery breaker alarms etc. An ACTCM must be built in the first service2shelter, while an ACTCS2 must be installed inthe other service2 shelters.

Fig. 48 ACT modules of NB-441 and NB-881

5.12.1 ACTPV3 switch setting for rack-ID

Fig. 49 ACTPV3 Switch Setting for Rack-ID



104

5.13 Connection to the Iub interface The NB-440/441 and as well NB-880/881 is connected to the Iub interface via the IUBCON. The IUBCON can easily be replaced by the OVPT, an optional unit. Both modules have almost the same functionality. However, only the OVPT provides outdoor lightning protection via gas dischargers. This section describes both modules.

5.13.1 Iub Connector (IUBCON) The Iub connector module serves as a physical interface between the Node B’s internal modules and the Iub cables from the RNC or other external devices, e.g. the LMT. The IUBCON is plugged in on the EMI panel. The IUBCON module supports the following features: • 8 Iub lines for uplink and downlink • support of 120 Ω and 100 Ω symmetrical connections (twisted pair) or 75 Ω

coaxial connections • external synchronization clock (coaxial connectors) • monitoring of the lub lines and external clock synchronization • lightning protection for the Ethernet interface • stress relief (clamp blocks) and grounding facility for external cable and

shielding The type of IUBCON depends on the cable used for the lub interface, either • symmetrical lines with 100/120 Ω impedance, or • coaxial lines with 75 Ω impedance Two IUBCON modules can be installed on the EMI panel of a Base Rack/Shelter to provide interfaces for 16 Iub lines.



105

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 50 IUBCON; Connector location



106

5.13.2 Over-Voltage Protection and Tracer (OVPT) The OVPT module provides the interface of the lub lines between the base cabinet and the peripheral lub cables. The OVPT also protects the ports from overvoltage. The module can be used instead of the IUBCON module and is located outside the EMI shielding. Two different connection types are possible at the lub interface: • E1 2048 kbit/s 120 Ω • J1 1544 kbit/s 100 Ω The OVPT module supports the following features: • lightning protection of lub lines and external clock synchronization • current limiting as part of fine protection • monitoring of the lub lines and external clock synchronization • support of 120 Ω and 100 Ω symmetrical connections • lightning protection for the Ethernet interface • stress relief (clamp blocks) and grounding facility for external cable and

shielding The OVPT module consists of two boards: • one board for coarse protection (surge arrester) of the lub lines, the tracer

connector and protection for the Ethernet interface • one board for fine protection (current limiting resistors) and the interface to the

EMI panel The type of OVPT depends on the cable used for the lub interface, either • symmetrical lines with 100/120 Ω impedance, or • coaxial lines with 75 Ω impedance For detailed information about respective connectors refer HWMN: Node B Cards/Modules.



107

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 51 left: OVPTE1J1SFV1 / right: OVPTE1CFV1; with Iub and Clock Interface



108

5.14 Over-Voltage Protection for External Rest Line (OERF)

If a fatal error occurs within the application software and the Node B is stuck, a remote restart of Node B hardware can be initiated from the operation and maintenance center via a discrete line. The Over-Voltage Protection for External Reset Line (OERF) module protects the modules of the Node B which are connected to the external reset line against lightning disturbance. The OERF module is located in the EMI-Panel.



109

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 52 Over-Voltage Protection for External Rest Line (OERF)



110

5.15 Power supply and battery backup This chapter gives an overview of the power supply conditions including input power and some examples of estimated power consumption.

5.15.1 Power supply A nominal voltage of -48V DC (-40.5 V to -57.0 V) is required to operate the modules of the NB-420/440/441 and NB-860/880/881. This DC voltage is delivered by • an external (customer) power source for the base rack of the NB-420/440 and

NB-860 indoor cabinet • the service area of the base shelter of the NB-441 and NB-881 outdoor cabinet. Any DC voltage other than the nominal -48 V DC required by specific boards is generated onboard by a special power supply unit. DC/DC converter alarms are processed on the modules themselves and forwarded to the CC board. The DC supply of all service2 shelters that are connected to the same NB-441 and NB-881 base shelter is limited to 25 ampere by a breaker. This value includes all fans, ACTC and link equipment units installed in the service2 shelters. Node B is protected against over current/lightning, overvoltage and undervoltage.

5.15.2 Power consumption For detailed information about power consumption refer TED: UTRAN NB440/441 and TED: UTRAN NB880/881.

5.15.3 Battery backup mode for NB-441 and NB-881 At least one battery set must be installed in an NB-441 and NB-881 base shelter to avoid distortion of the Node B subsystem caused by a short interruption of the AC mains supply. If the backup battery fails, operation continues as long as the AC/DC converters supply the power. In the case of AC mains interruption, the NB-441 and NB-881 base section can be powered by a battery system consisting of up to 7 battery sets with 92 Ah capacity each. These battery sets are installed as follows: • 1 x 92 Ah @ -48 V in the service area of the base shelter • 3 x 2 x 92 Ah @ -48 V in three service2 shelters With a DC power consumption of 3000 W and one battery set with 92 Ah installed in the service area of the base shelter, a backup time of about 60 minutes can be achieved. For detailed information about Battery Backup Mode for NB-441 and NB-881 refer TED: UTRAN NB440/441 and TED:UTRAN NB880/881.



111

MSU:DC150AV1; terminals and connectorsMSU:DC80AV3; terminals and connectors

Fig. 53 Power supplies for NB-440 and NB-880

MSU:AC1PHFV1; terminals and connectors MSU:AC3PHV2; terminals and connectors

Fig. 54 Power supplies for NB-441 and NB-881



112

5.16 The service2 shelter for NB-441 and NB-881 Additional battery backup Additional height units for link equipment Up to three NB-441 and NB-881Service Shelters can be installed to a NB-441 and NB-881 Base Shelter.

5.16.1 AC/DC system for the NB-441 and NB-881 The AC/DC system for the NB-441 or NB-881 (outdoor application) consists of: • 1 to 5 converter modules to achieve a DC power of 1600W up to 8000W. • 1 additional converter module for redundancy purposes (N+1 redundancy) • Controller board with battery supervision, rectifier supervision, and alarm

interface. • Interfaces for AC Input, DC Output and Control Output The number of AC/DC converters required in each AC/DC subrack depends on the effective power required for the base shelter. The AC/DC converter is used as a connection module if Node B is directly supplied by the AC mains. The AC/DC rectifier module converts the AC mains voltage (nominal voltages 230 Vac) to the -48 V DC supply voltage. The nominal DC output power of 1 AC/DC converter module is 1600W for + 50 °C ambient temperature. At least 2 AC/DC converter modules must be installed into the AC/DC subrack of the NB-441 NB-881 base shelter, while up to 6 converters can be installed. Each empty AC/DC slot must be closed with an appropriate cover (dummy module). For the power supply, n+1 redundancy is implemented by N plus one AC/DC converters that work in load-sharing mode. If one AC/DC converter fails, the remaining N modules can supply the connected hardware without restrictions. The maximum DC current is limited to 160 A to • supply the Node B equipment including link equipment • to charge the backup batteries that are connected to the same AC/DC subrack The charging current for all installed battery sets is limited by the DC battery controller to 10% of nominal capacity of all installed battery sets with a maximum value of 30 A.



113

Fig. 55 left: AC/DCAV1; right: AC/DCDV1

Fig. 56 DC and Battery Controller DCBCTRLDV1



114

The AC power supply for an NB-441 or NB-881 base station consists of: • 1 base shelter with maximum module configuration and 6 LEs with a total power

consumption of 540 W (battery trickle charge) • 3 service2 shelters:

– 1 service2 shelter with 2 HU link equipment, two battery sets and one fan (power consumption: nominal 325 W, max. 370 W (battery: trickle charge)) – 2 service2 shelters with battery only and one fan per shelter (power consumption: nominal 290 W, max. 380 W (battery: trickle charge))



115

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 57 DCBCTRLAV1



116

5.16.2 AC/DC and battery system for outdoor application The base shelter of the NB-441 and NB-881 for outdoor application includes a service area containing: • 1 AC/DC subrack • 1 battery tray • 1 frame (optional) for 6 HUs for link equipment The installation of 1 battery set is mandatory. Up to 6 additional battery sets can be added depending on the DC power consumption and the requested backup time. The additional NB-441 and NB-881 service2 shelter provides space for • · 2 battery trays and additional HU (Height Unit) for link equipment or • · 1 battery tray and additional HU (Height Unit) for link equipment or • · additional HU (Height Unit) for link equipment



117

Fig. 58 left: NB-441 and NB-881 Service2 Shelter (no Battery Unit); right: NB-441 and NB-881 Service2 Shelter for 2/2/2 configuration

Fig. 59 left: NB-441 and NB-881 Service2 Shelter (1 Battery Unit); right: NB-441 and NB-881 Service2 Shelter (2 Battery Units)



118

5.17 System expansion Node B can be flexibly expanded to cope with increasing traffic. The system can be expanded with any of the following expansion types or any combination of them. The maximum possible expansion differs according to the expansion type. • Channel expansion

A maximum of 960 channel elements can be accommodated in an NB-440/441 or NB-880/881 system consisting of a base rack/shelter.

• Carrier expansion A maximum of 2 carriers per sector can be assigned to an NB-440/441 or NB-880/881 system consisting of a base rack/shelter.

• Sector expansion A maximum of 3 sectors with 2 carriers can be assigned to an NB-440/441 or NB-880/881 system consisting of a base rack/shelter.

A system expansion usually requires additional hardware modules. The following features can be activated by pure software download/licensing from the LMT or OMC (Operation and Maintenance Center): • Number of cells supported by the DRIC • Number of channel elements supported by the Node B For some expansion types, software and hardware has to be updated. Both hardware and software expansions are described in this section.

5.17.1 Hardware expansion Each type of hardware expansion requires specific units of equipment to be added. See Fig. 60 for details concerning the DRIC-CAT concept and REP-TRX-LPA concept. The procedures for the different types of hardware expansion for the DRIC-CAT concept are as follows: • Sector expansion

Install additional CATs, DUAMCOs and TMA (optional). Connect the CAT with the DUAMCO ports and add the additional TMA (optional but highly recommended).

• Channel expansion An additional CHC96 increases the capacity by 96 CEs: from 96 to 192 CEs or from 192 to 284 CEs. Install a new CHC96 in a slot. Electrically connect the card via the back plane.

• Carrier expansion Install a new CAT in a slot. Install the RF connection via the front of the rack/shelter and connect the module electrically via the back plane.



119

After installation, a new card takes approximately 180 seconds before starting operation. The procedures for the different types of hardware expansion for the REP-TRX-LPA concept are as follows: • Channel / Carrier expansion

Install a card in a slot. Electrically connect the card via the back plane. • Sector expansion

Install additional LPAs, TRXs, DUAMCOs and TMA (optional). Connect the LPAs and/or TRX cards with the DUAMCO ports and add the additional TMA (optional but highly recommended).

After installation, a new card takes approximately 180 seconds before starting operation.

Units of expansion (DRIC-CAT concept)

Units of expansion (REP-TRX-LPA concept)

Fig. 60 Units of expansion



120

5.18 Node B NB-440/441 and NB-880/881 technical data The following page shows the basic technical data for NB-440/441 and NB-880/881.



121

5.18.1 NB-440/441 technical data

Performance

Frequencies up to 2 in one rackSectors up to 3 Output-power up to 2x20 W per sectorChannel Elements up to 960E1 up to 16STM-1 up to 2

Physical & Environment

NB-440: Dimensions (H-W-D) 1400x600x450mm3

Operation Temperature -5 °C .. 45 °CNB-441: Dimensions (H-W-D) 1499x1270x700mm3

Operation Temperature -33 °C .. 50 °C

Fig. 61 NB 440/441 Technical Data

5.18.2 NB-880/891 technical data

Performance

Frequencies up to 4 in one rackSectors up to 6 Output-power up to 2x40 W per sectorChannel Elements up to 960E1 up to 16STM-1 up to 2


NB-880: Dimensions (H-W-D) 1400x600x450mm3

Operation Temperature -5 °C .. 45 °CNB-881: Dimensions (H-W-D) 1499x1270x700mm3

Operation Temperature -33 °C .. 50 °C

Fig. 62 NB 880/881 Technical Data



122



123

6 Node B 860



124

6.1 Features and Technical Data The indoor Macro FDD Node B NB-860 is a further development of the Node B 420 and provides macro capacity in micro-sized housing (<245 l). The NB-860 and the NB-880/881 use the same base band and RF modules, which simplifies distribution of spare parts and training of the maintenance staff of both. The NB-860 uses the hardware concept (DRIC-CAT), which enables newest available technologies in linear amplifier research such as digital predistortion. This features a noticeably higher efficiency resulting in a lower power consumption of the whole Node B. The modules DRIC (Digital Radio Interface Card) and CAT (Combined Amplifier and Transceiver) are connected by a digital high-speed interface called the Common Public Radio Interface (CPRI). The CPRI interface is a unique radio driven interconnect point in radio base stations, which offers the following benefits: • Varying Radio Base Station architectures for very flexible solutions, e.g.

distributed architectures and remote tower mounted radio concepts • Additional deployment scenarios • Efficient network deployment The technology leading Common Public Radio Interface (CPRI) is the base for new and versatile Node B architectures. Now, sites can be flexibly planned with Node B Radio Server and Remote Radio Heads (RRH) or the standard Macro or Micro Node B scenario. The NB-860 can be combined with a 6-carrier Siemens BTS for a UTRAN-FDD and GSM/DCS collocation solution. Furthermore, two NB-860s can be combined for site sharing purposes. Key features of the NB-860 include: • High capacity: 1 shelf (2/2/2) • High power: up to 40 W per carrier • RX diversity (strongly recommended) Node B links up to the RNC via dedicated E1/J1 and/or STM-1 connections. ATM is used as the transmission protocol. Data traffic is packed into AAL2 cells, whereas signaling traffic is transferred using the AAL5 protocol. The rack is designed for stacking two single racks one upon the other. The rack’s mechanical structure carries safely the load of a second fully equipped rack (NB-860/BTS).



125

6.2 Main Features The NB-860 has a modular structure and operates up to 2 carrier frequencies in 1 cabinet. RF features A maximum of 3 sectors is supported in a single rack. Different cell configurations up to 2/2/2 are possible. Two linear-pole antennas or one cross-pole antenna are supplied for each sector. The antennas can be complemented by one Dual Tower Mounted Amplifier (DTMA) or two Tower Mounted Amplifiers (TMA) per sector as low-noise amplifiers. The NB-860 supports up to 384 channel elements (CE) in UL. The capacity is highly scalable. The evolution is based on DRIC and CAT introducing the CPRI interface towards Radio Server (RS) and Remote Radio Heads (RRH) on the same hardware platform. The CPRI interface specification is available for download from http://www.cpri.info/spec.html Using the DRIC-CAT concept, the supplied Combined Amplifier and Transceiver (CAT) with 40W(CAT40) or 20W(CAT20) output power is designed for operation with • one UMTS carrier per antenna with a nominal output power of 40/20 W or • two UMTS carriers per antenna with 40/20 W as the nominal average sum

output power, i.e., each carrier will be radiated with 20/10 W per antenna (hardware-prepared).

The DRIC24_24OE (Digital Radio Interface Card) enables the Node B 860 to provide the following features: • 24 antenna carriers (hardware-prepared) for uplink and downlink • Flexible support of electrical and optical CPRI-compliant interfaces • Support of Remote Radio Heads in any mixed configuration with CATs • High spreading capacity of 3072 channel elements in DL • TX-diversity for every configuration • Capability of performing the 16 QAM-modulation scheme in order to support the

HSDPA feature. The RET (Remote Electrical Tilt) functionality is fully integrated into the NB-860. RX diversity is a basic feature.



126

6.3 Hardware Architecture The Macro Node B NB-860 features compactness and flexible expandability with modular shelf configurations. The highly integrated cards/modules/components (especially CHC96 and the DRIC and CAT modules) noticeably reduce the system complexity. The configuration of the Macro Node B NB-860 consists of one rack. This rack contains only one shelf for both baseband and RF modules. The NB-860 is equipped with DRIC and CAT modules (DRIC-CAT concept). The Combined Amplifier and Transceiver (CAT) module integrates the transmitter and receiver functions. The Digital Radio Interface Card (DRIC) comprises the spreading functionality as well as the multiplexing, routing and splitting function of the baseband signals in the DL. A Node B with a DRIC24_24OE can be connected to Remote Radio Heads (RRH) to reduce feeder and amplifier losses. In the DRIC-CAT concept, the modules on the shelf are configured as follows, • Duplexer Amplifier Multi-Coupler (DUAMCO) • Combined Amplifier and Transceiver Module (CAT) • Digital Radio Interface Card (DRIC) • Channel Coding Card (CHC) • Core Controller (CC)

6.3.1 Rack and Shelf Configuration

Maximum card configuration



127

Fig. 63 NB-860 indoor cabinet (DRIC-CAT concept)

Fig. 64 NB-860 Function blocks



128

6.3.2 Site Sharing The Siemens/NEC UTRAN solution provides several kinds of equipment sharing to deploy the UMTS network very quickly and efficiently. The most common kinds of equipment sharing are site/mast sharing, Node B sharing, and Core Network sharing. Two NB-860 can be combined in a site-sharing configuration. Both Node Bs have independent access to the -48 V power supplies. Each NB-860 has its own alarm handling. However, the OMC indicates that the two Node Bs are combined. The two NB-860 are mechanically connected by a coupling and distance-creating unit that is not an integral part of the rack.

6.3.3 Co-Location The Siemens/NEC UTRAN concept of collocation enables the operator to minimize the number of sites by using UMTS equipment in combination with GSM base stations. The NB-860 can be combined with a 6-carrier Siemens BTS to form a collocation solution for GSM/DCS and UTRAN-FDD equipment. In this configuration, the NB-860 is mounted on top of the BTS rack. The NB-860 is mechanically connected to the BTS via a mounting device. This device substitutes the top cover of the BTS and is open at the front and at the back. The antenna cables of the BTS run from the top of the BTS to the back of the base stations. Both base stations have independent access to the -48 V power supplies. Each base station has its own alarm handling. However, the OMC indicates that the NB-860 and the BTS are combined.



129

Fig. 65 Site-sharing solution of two NB-860

Fig. 66 NB-860 and 6-carrier Siemens BTS co-location solution



130



131

7 Node B 580



132

7.1 Features and Technical Data The Node B 580 covers the configurations for the US market. In this framework the described Node B functionality is limited to the frequency division duplex (FDD) mode, macro cell coverage and UMTS1900 band. The applied radio frequency (RF) bands are for • Downlink: 1930 MHz – 1990 MHz (60MHz) • Uplink: 1850 MHz – 1910 MHz (60MHz) TX – RX Separation: 80 MHz Due to the fact that in later releases the UMTS1900 and UMTS850 band will be supported within one Node B, a new Node B type NB-580 is introduced. The radio communications capability of a Node B is strongly related with the number of available sectors /cells.

7.2 Main Features The NB-580 has a modular structure and operates up to 2 carrier frequencies in one cabinet. The Main Features are the same as for the NB-860. Using the DRIC-CAT concept, the supplied Combined Amplifier and Transceiver (CAT) with 40W(CAT40) or 20W(CAT20) output power is designed for operation with • one UMTS carrier per antenna with a nominal output power of 40/20 W or • two UMTS carriers per antenna with 40/20 W as the nominal average sum

output power, i.e., each carrier will be radiated with 20/10 W per antenna (hardware-prepared). The NB-580 supports within the release UMR4.0 US only the 1900 MHz FDD frequency band. Be aware that the NB-580 is the only Node B supported within UMR4.0 US.



133

Fig. 67 Node B-580 for 1900 MHz

Fig. 68 Node B-580 for 850 MHz and 1900 MHz with two A-shelves



134

7.3 Hardware Architecture The figure 48 on the right shows the two A-Shelves of the NB-580. The upper one is the A-Shelf for the 850 MHz band Air Link Modules that is not supported in UMR4.0 US. The lower A-Shelf can be equipped with Air Link Modules for the 1900 MHz band. At the bottom of the Node B the B-Shelf is placed, which has the same Baseband capacity as the B-Shelf of the NB-88x. The B-Shelf of the NB-580 provides the following slots: • 2 Core Controller slots • 10 Channel Coding card slot • 2 DRIC slots Each A-Shelf of the NB-580 provides slots for: • 6 CAT modules • 3 DUAMCO modules Please note that 850 MHz modules, as well as1900 MHz modules, fit only in their belonging shelf. The modules, which can be installed in the NB-580, are described in the following chapter.

7.4 Supported modules within UMR4.0 US Within UMR4.0 US the number of supported modules for A- and B-Shelf is reduced in comparison to the world market releases due to the fact that only the DRIC-CAT concept and the latest versions of Core Controller modules and Channel Coding cards is supported.

7.4.1 B-Shelf Modules For UMR4.0 US there are no new B-Shelf modules. Only the number of supported modules for the NB-580 is reduced.

7.4.1.1 Core Controller Modules (CC) Only the third generation of Core Controller Modules is supported within UMR4.0 US. The Core Controller accomplishes the signal transmission and data controlling of the Node B NB-580 and manages the data transfer to the Radio Network Controller (RNC) and the Channel Coding Card (CHC). Within UMR4.0 US the Iub-interface supports only the T1-interface. 2 Core Controller Modules may be installed for redundancy purposes.



135

7.4.1.2 Channel Coding Cards (CHC) The main functions of Channel Coding card (CHC) are: • the channel coding & decoding procedure defined by 3GPP (Coder and

Decoder) • the CDMA Rake Receiver function, incl. dispreading and combining of multiple

receive paths (Finger) and searching new propagation paths (Searcher), receiving the Mobile Station Random Access Channel.

The Node B NB-580 supports 2 types of Channel Coding cards: CHC96FVx is able to support simultaneous HSDPA specific channels, as well as Dedicated Channels (DCHs). The performance for Dedicated Channels (DCHs) is 96 channel elements and AMREQ of 144. HSDPA specific channels are not supported in UMR4.0 US. CHC-HS96FVx The High Speed Channel Coding Card supports simultaneous HSDPA specific channels and functions, as well as normal channels. The performance for Dedicated Channels (DCHs) is 96 channel elements and AMREQ of 144. HSDPA specific channels are not supported in UMR4.0 US.

7.4.1.3 Digital Radio Interface Cards (DRIC) The Digital Radio Interface Card combines the functionality of the former REP card and the digital functionality of several TRX cards. The DRIC has 6 CPRI compliant Digital Radio Interfaces for 6 CATs. The B-Shelf of NB-580 provides 2 slots for installation of up to 2 DRIC cards. • DRIC12-12FVX Provides 12 downlink paths and 12 uplink paths. • DRIC24-24OEFVx Total capacity of 24 AxC in the DL – as well as in the UL-

direction.

7.4.2 A-Shelf Modules Within UMR4.0 US two new A-Shelf 1900 MHz modules are introduced due to the new supported frequency band in the range of 1900 MHz. The new modules are the ‘Combined Amplifier and Transceiver’ with 40W and the ‘Duplexer Amplifier Multi-Coupler’ with Remote Electrical Tilt functionality.

7.4.2.1 Combined Amplifier and Transceiver The CAT amplifies the downlink signal to a nominal level dependent of the type of CAT. The different types of CAT provide a different number of TX and RX carrier paths. The CAT is connected to the DRIC via the CPRI compliant Digital Radio Interface (DRIF). The CAT is controlled and monitored via the DRIF interface by the CC. The A-Shelf 1900 MHz of the NB-580 provides 6 slots for installation of up to 6 CAT modules.



136

CAT40-3-4UFVx Combined Amplifier and Transceiver – Multi Carrier for up to 3 TX carrier paths and 2 independent dual carrier paths capable of supporting a dual carrier RX-diversity scheme for operation within a bandwidth of 15 MHz in the UMTS1900 frequency band. The CAT amplifies the downlink signal to a nominal level of equal or less than +46dBm (40W) measured at the antenna port of the Node B. 1 CAT module is required at least for each sector.

7.4.2.2 Duplexer Amplifier Multi Coupler (DUAMCO) The Duplexer Amplifier Multi Coupler module consists of two electrically identical modules. Each module has a transmit path and a receive path with a single connector for the antenna feeder cable. The A-Shelf 1900 MHz of the NB-580 provides 3 slots for installation of 1 to 3 DUAMCO modules.

DUAMCORETUFVx For 2 antennas with RX-Diversity, TX-Diversity and signaling for RET Module. The DUAMCORETUFVx provides 2 (1 in each antenna branch) Filter RF input ports and 2 (1 in each antenna branch) Filter RF output ports. TX-Diversity must be administered in the Node B Data Base. 1 DUAMCORETUFVx is required for each sector



137

8 Node B NB-341



138

8.1 NB-341 modules • 1 Power Amplifier (LPA) • 1 DUAMCO and TX-Amplifier • 1 Channel Card (CHC) • 1 TRX • 1 Core Controller (CC) • 1 Mains Supply • 1 Over Voltage Protection (OVP) • 1 Maintenance Board (MAINT)

8.1.1 NB-341 concept Identical look and feel for operation and maintenance • Same Feature Set available for all Node Bs • Reduces the spare part sizes, Reduces cost, simplifies training of service

people

8.1.2 Supported cell ranges normal cell size and large cell size for normal cells: search range of the searcher for RACH: 10km usual cell range radius: 5km (8 CEs / 8 AMREQs needed for common channels in UL). for large cells: search range of the searcher for RACH: 20km usual cell range radius: <20km (16 CEs / 16 AMREQs needed for common channels in UL)

8.1.3 Channel capacity Depending on the installed CHC: 48 or 96 CE



139

Fig. 69 Node B NB-341 w/o Booster and with Booster

LNA(1)

Duplexer/Filter

(1)

MainsSupply

OverVoltage

Protection

CAN 1

Iub

48/110/230V

alarmUu

LPA(1)

CC(1)

Mainte-nance Board

-48 V

CHC(1)

UTOPIA II Bus (ATM)

Clock Distribution Bus

LVDSTRX(1)

CAN2 Bus (O&M)

RF Cabling

Booster (1)Optional: 48/110/230V

Enclosure

RF-Part BB-Part

Iub

Fig. 70 NB-341 Modules



140

8.1.3.1 Physical interfaces on the right side of the NB-341

Interface Location Interface Name Signal Number of

Systems Connector Type

RF IN (red) RF input 1 TNC × 1

RF OUT (blue) RF output 1 TNC × 1

TX OUT Transmission output 1 TNC × 1

BOOSTER CTRL Booster monitor and control signal

1 Waterproof multi-pin connector × 1

Photocoupler input DC signal for external alarms (8 items)

Waterproof multi-pin connector × 1

Relay make contact output DC signal for external control (2 items)

EXT ALM/ CTRL

External Ethernet port (ANT-TILT)

1

PWRIN 100 VAC±10% (50 or 60 Hz) 220 VAC-10% to 240 VAC+10% (47 to 63 Hz)


FG Frame ground 1 Fastened with a screw

J1 (1.5 Mbps balanced) 2 lines Screw-less terminal board

Right side of the NB-341

Iub

STM-1 (155 Mbps optical fiber) 2 lines SC connector

8.1.3.2 Physical interfaces on the right side of the booster Interface Location Interface Name Signal Number of


CTRL Booster monitor and control signal


RF IN (blue) RF input 1 TNC × 1

RF OUT (red) RF output 1 TNC × 1

PWR IN 100 VAC±10% (50 or 60 Hz) 220 VAC-10% to 240 VAC+10% (47 to 63 Hz)

1 Waterproof multi-pin connector ×

Right side of the Booster

FG Frame ground 1 Fastened with a screw



141

Booster

NB-341

Fig. 71 Physical Interfaces on the Right Side of the NB-341 and the Booster

8.1.4 Cabling w/o and w/ booster

Fig. 72 NB-341 RF Cabling



142

8.1.4.1 Physical interfaces on the left side of the NB-341

Interface Location Interface Name Signal Number of


ANT1 (RX1) Reception signal (RX1) 1 N × 1 Left side of the NB-341

ANT0 (TX0/RX0) Transmission/reception signal (TX0/RX0)

1 N × 1

8.1.5 Pin assignment of the external monitor and control interface connector

Pin No. Signal Name Remark Pin

No. Signal Name Remark Pin No.

Signal Name Remark

1 CONT0+ 11 ALM_IN3- 21 RX- 2 CONT0- 12 ALM_IN4+ 22 RX+ 3 CONT1+ 13 ALM_IN4- 23 TX- 4 CONT1-

See Note 1.

14 ALM_IN2- 24 TX+

See Note 3.

5 ALM_IN0+ 15 ALM_IN5+ - - - 6 ALM_IN0- 16 ALM_IN6+ - - - 7 ALM_IN1+ 17 ALM_IN6- - - - 8 ALM_IN1- 18 ALM_IN7+ - - - 9 ALM_IN2+ 19 ALM_IN7- - - - 10 ALM_IN3+

See Note 2.

20 ALM_IN5-

See Note 2.

- - -

NOTES: 1. "CONTxx" represents an output port of the external control interface. 2. "ALM_INxx" represents an input port of the external alarm interface. 3. "RXx" and "TXx" represent external Ethernet ports (ANT-TILT).



143

Fig. 73 Physical Interfaces on the Left Side of the NB-341

8.1.6 RF block diagram

Ant. 0

Ant. 1

b) w/ Booster

Fig. 74 NB-341 RF Block Diagram



144

8.1.6.1 Interface A: O&M interfaces, TX monitor and power switch and Interfaces B (Iub)

Fig. 75 Interface A: O&M-Interfaces, TX-Monitor and Power Switch and Interfaces B (Iub)



145

Fig. 76 Node B NB-341 block diagram

Frequencies 1Sectors 1/0/0 or omnicell, RX-DiversityOutput-power max: 0,5 W w/o Booster, 10 W w/ BoosterCell Radius up tp 10 km with BoosterChannel Elements 48Iub-Interface: Standard 2x E1/J1, optional 2x E1/J1 and 2xSTM-1

Fractional ATM, Circuit Emulation Service CESConfigurations: star, loop, cascade, hub

Dimensions (H-W-D) 500x425x200mm3

Booster (H-W-D) 190x420x200mm3

Weight Rack 30 kg, Booster 12 kgOperation Temperature -33 °C .. 45 °CPower Supply: - 48 V DC or 100V/220-240V AC single phasePower Consumption: NB-341 max 250/280 W DC/AC,

Booster max. 210/230 W DC/AC, Heater 340 W Cooling Passive Cooling with Heat ExchangerNumber of external Alarm Inputs/Outputs: 8/2


Performance

Fig. 77 NB-341 Technical Data



146



147

9 New hardware components from UMR4.0



148

This chapter provides an overview of Node B hardware components that are newly available within UMR4.0 and with compatibility from UMR4.0.

HW Component Manual Macro Radio Server (RS-880) The Macro Radio Server RS-880 provides the full functionality of the NB-880 in conjunction with Remote Radio Heads (RRHs). A complete base band shelf with DC-Panel is mounted into a server rack reducing the acoustic noise emission and the necessary space for installation. The RF functionality of the Node B is incorporated in a Remote Radio Head (RRH). The RS/RRH configuration represents a versatile Node B architecture for flexible site planning. RS and RRHs interact via the technology leading Common Public Radio Interface (CPRI). Now, sites can be flexibly planned.

TED:UTRAN Common TED:UTRAN Radio Server

Macro Remote Radio Head (RRH-m) The macro Remote Radio Head (RRH-m) is an outdoor unit outside the Node B/Radio Server representing a highly integrated future proven solution for RF functionality. Based on the technology leading Common Public Radio Interface (CPRI), the RRH-m is fully compatible with the classic Node B architecture. It can be connected to NB-880/881, NB-860, and RS-880. The RRHm comprises the complete RF functionality of a Node B in one unit, equal to the three modules CAT, DUAMCO, and TMARET.

TED:UTRAN Common TED:UTRAN Radio Server TED:UTRAN NB-880/881 TED:UTRAN NB-860

CAT40 The supplied Combined Amplifier and Transceiver with 40W (CAT40) output power is designed for operation with one UMTS FDD carrier per antenna with a nominal output power of 40W or two UMTS FDD carriers per antenna with 40W as the nominal average sum output power, i.e., each carrier will be radiated with 20Wper antenna (hardware-prepare).

TED:UTRAN Radio Server TED:UTRAN NB-880/881 TED:UTRAN NB-860

DRIC24_24oe The DRIC24_24OE (Digital Radio Interface Card) has an optical and electrical interface to support the RRH as well as the CAT module. Mixed configurations are possible. It also provides the HW-preparation for HSDPA. The DRIC24_24OE has a high spreading capacity of 3072 channel elements and supports up to 24 antenna carriers (hardware-prepared) for uplink and downlink.

TED:UTRAN Radio Server TED:UTRAN NB-880/881 TED:UTRAN NB-860



149

9.1 Macro Radio Server RS-880 9.1.1 Features and technical data The devices feature a shelf design which allows for maximum scalability. The Radio Server RS-880 provides the full functionality of the NB-880 in conjunction with Remote Radio Heads. A complete base band shelf with DC-Panel is mounted into a server rack reducing the acoustic noise emission and the necessary space for installation. The RF functionality of the Node B is incorporated in a Remote Radio Head (RRH). The RS/RRH configuration represents a versatile Node B architecture for flexible site planning. RS and RRHs interact via the technology leading Common Public Radio Interface (CPRI). Now, sites can be flexibly planned with Remote Radio Heads (RRH).



150

RS/RRH configurations offer the following benefits: • RS is centralized in a hotel and RRHs are distributed in the coverage area • RS can be combined with Macro, Micro and Pico Remote Radio Heads (the

combination with Micro and Pico Radio Head in further releases) • Flexible number of sectors and antenna sites • Multi-site configuration (with softer HO) • Reduced signaling and transmission costs due to softer HO • Baseband (resource) pooling to reduce CAPEX costs • Feeder loss in the downlink direction is diminished by the short distance

between RRH antenna connector and RRH. The uplink quality is also improved superseding a TMA.

• Reduced power consumption and optimizations in operation and maintenance • Easy site acquisition due to reduced requirements Radio Server locations

(flexible fiber optic cable, long distances between Radio Server and antenna location possible, low acoustic noise emission for radio server)

Key features of the RS-880 with RRHs include: • High capacity: 1 rack (1/1/1/1/0/0) or (2/2/2) • High power: up to 12.5 W per RRH • RX diversity (strongly recommended) and TX diversity (hardware-prepared,

optional) Node Bs/Radio Server and RNCs form the UMTS Terrestrial Radio Access Network (UTRAN), as standardized by 3GPP. A Radio Server links up to the RNC via dedicated E1/J1 and/or STM-1 connections. ATM is used as the transmission protocol. Data traffic is packed into AAL2 cells, where as signaling traffic is transferred using the AAL5 protocol.



151

Fig. 78 RS-880 indoor cabinet

Fig. 79 Block diagram of the RS-880 with RRH



152



153

9.1.2 Main features The RS-880 has a modular structure and operates up to 2 carriers in 1 cabinet in conjunction with RRHs. The design is prepared for up to 3 carriers. The next Fig. shows the system concept of Radio Server RS-880 and Remote Radio Head (RRH). A maximum of 4 sectors is supported in a single rack. Different cell configurations up to 1/1/1/1/0/0 or 2/2/2 are possible. The system is hardware-prepared to support up to 12 sectors with 1 carrier by DRIC load-sharing or up to 6 sectors with 2 carriers and DRIC redundancy. Two linear-pole antennas or one cross-pole antenna are supplied for each sector. The radio-frequency band for RX and TX signals includes • 2110 to 2170 MHz for downlink signals • 1920 to 1980 MHz for uplink signals. A continuous spectrum within a 15 MHz band is supported. The maximum cell range is 50 km. The rack supports up to 960 channel elements (CE). The capacity is highly scalable, i.e., it can be increased in steps of 48 CEs. The Radio Server Architecture is based on the publicly available CPRI interface between Radio Server (RS) and Remote Radio Heads (RRH). The CPRI interface is a unique radio driven interconnect point in radio base stations. Using CPRI offers the following benefits: • Varying Radio Base Station architectures for very flexible solutions, e.g.,

distributed architectures and remote tower mounted radio concepts • Additional deployment scenarios

The DRIC24_24OE (Digital Radio Interface Card) enables the RS-880 to provide the following features:

• Up to 24 antenna carriers (hardware-prepared) for uplink and downlink • Support of optical CPRI-compliant interfaces by means of SFP (Small

Formfactor Pluggable) technology • High spreading capacity of 3072 channel elements • RX diversity is a basic feature. TX-diversity for every configuration, limited only

by the number of DL Antenna-carriers (hardware-prepared and optional). • Capability of performing the 16 QAM-modulation scheme in order to support the

HSDPA feature. The RET (Remote Electrical Tilt) functionality is fully integrated into the RRH.



154

Iub Interface Configurations The RNC and the connected Radio Servers can be arranged in a star, cascade, hub or loop configuration. The E1/J1 lines can be used with Inverse Multiplexing for ATM (IMA) in all these configurations. IMA provides for transport of a high bit rate ATM cell stream on several low bit rate physical links.

System reliability The following cards and modules are redundant to assure maximum system reliability: • Semi-hot redundancy for the Digital Radio Interface Card (DRIC) • Cold redundancy for the Core Controller (CC) • Load-sharing (pooling of the resources) for the Channel Coding Card (CHC) The RS-880 supports an emergency configuration in the case of a mains power supply loss. This mechanism enables the RS-880 to maintain the operation and service as long as possible.

UMTS – GSM Co-location The RS-880 supports two forms of transmission re-use for UMTS – GSM Co-location which are mutually exclusive: • Circuit Emulation Service (CES)

CES offers a cost-effective way to co-locate Radio Server and GSM base stations using a common ATM-based transmission network.

• Fractional ATM (FRAC) Fractional ATM over circuit-switched networks (GSM) provides transport of Iub timeslots.

9.1.2.1 Technical data



155

9.1.3 Hardware architecture The configuration of the RS-880 consists of one rack containing the baseband modules. The RF modules are located in the Remote Radio Head unit. The RS-880 is equipped with one or two Digital Radio Interface Cards (DRIC). The DRIC enables a CPRI-compliant digital radio interface to the Radio Equipment integrated in the Remote Radio Head. The digital transmission via a fiber cable reduces feeder and amplifier losses as well as noise. The modules on the shelf are configured as follows, see Block diagram: Digital Radio Interface Card (DRIC) Channel Coding Card (CHC) Core Controller (CC) The functions and technical data are already described under "Main Features". The RRHs with the dotted line are hardware-prepared. The typical power consumption of the RS-880:



156

9.2 Macro Remote Radio Head (RRH-m) The macro Remote Radio Head (RRH-m) is an outdoor unit outside the Node B/Radio Server representing a highly integrated future proven solution for RF functionality. Based on the technology leading Common Public Radio Interface (CPRI), the RRH-m is fully compatible with the classic Node B architecture. It can be connected to NB-880/NB-881/NB-881HR, NB-860, RSU-380, RS-381, and RS-880. The RRH-m comprises the complete RF functionality of a Node B in one unit, equal to the three modules CAT, DUAMCO, and TMARET. The RRH-m is placed between the Node B/Radio Server and two antennas. It provides two CPRI-compliant optical interfaces for connection to the DRIC. This requires a DRIC of type DRIC24_24OE which supports an optical interface in addition to the electrical one. The RRH-m is controlled and monitored by the CC via the CPRI interface. The RRH-m offers the following features: • One RRH-m serves one sector • RET functionality is supported • External alarms are supported • TX-diversity using 2 RRH-ms per sector (hardware-prepared) • CPRI cascading (hardware-prepared) • Up to 3 RF carriers for operation within a bandwidth of 15 MHz The RRH-m can be installed outside the Node B/Radio Server in the following ways: • Pole mounting, below or behind antenna • Wall mounting • Roof top For a detailed description please see TED:UTRAN RS-880/RRHs, TED:UTRAN RSU-380/RRHs, and TED:UTRAN RS-381/RRHs.



157

Fig. 80 Radio server RS-880 with RRH

Fig. 81 Block diagram of the RRH unit



158

9.2.1 General characteristics of the RRH-m

Fig. 82 General characteristics of the RRH-m



159

Fig. 83 RF interface characteristics of the RRH-m

CPRI PSR RET DC

Ext. Equipment Service Panel

TX Test

Antenna

Fig. 84 Remote Radio Head, Interfaces and Connectors



160

9.2.2 Cell configurations

Cell configuration Node B Type variant Power/cell [W]

"1/0/0" 880/881 RRH 12,5

"1/1/0" 880/881 RRH 12,5

"1/1/1" 880/881 RRH 12,5

"2/0/0" 880/881 RRH 6,25

"2/2/0" 880/881 RRH 6,25

"2/2/2" 880/881 RRH 6,25

"1/0/0; 1/0/0" 880/881 CAT-RRH 20 ; 12.5

"1/0/0; 1/0/0" 880/881 CAT-RRH 40 ; 12.5

"1/1/0; 1/1/0" 880/881 CAT-RRH 20 ; 12.5

"1/1/0; 1/1/0" 880/881 CAT-RRH 40 ; 12.5

"1/1/1; 1/1/1" 880/881 CAT-RRH 20 ; 12.5

"1/1/1; 1/1/1" 880/881 CAT-RRH 40 ; 12.5

"2/0/0; 2/0/0" 880/881 CAT-RRH 20 ; 6.25

"2/0/0; 2/0/0" 880/881 CAT-RRH 20 ; 6.25

"1/1/1/1/0/0" 880/881 RRH 12,5

"1/0/0" 860 RRH 12,5

"1/1/0" 860 RRH 12,5

"1/1/1" 860 RRH 12,5

"2/0/0" 860 RRH 6,25

"2/2/0" 860 RRH 6,25

"2/2/2" 860 RRH 6,25

"1/0/0" RS RRH 12,5

"1/1/0" RS RRH 12,5

"1/1/1" RS RRH 12,5

"2/0/0" RS RRH 6,25

"2/2/0" RS RRH 6,25

"1/1/1/1/0/0" RS RRH 12,5



161

9.3 Power Supply for Remote Radio Heads (PSR)

AC/DC- Panel

BAT

AC/D

C c

ontro

ller

AC/D

C m

odul

e

AC/D

C m

odul

e

AC/D

C m

odul

e

EMI FilterAC

EMI FilterAC

MSU

Connection pannel

PSR

Power Supply for Remote Radio Heads (PSR)

Technical Data:• Nominal output voltage: –48 V • Modular design with AC/DC controller and rectifiers• AC/DC module: 1200W each, n+1 redundancy • Full lightning protection for AC and DC lines • Battery back up time

- 120 minutes for 3 RRH typical operation - 60 minutes for 6 RRH typical operation - 40 minutes for 6 RRH worst case operation

• Alarming of PSR itself routed via RRH to O&M (AC breakdown, battery breakdown, DC voltage out ofrange, high and Over temperature, over voltage on ACor DC line, door open, fan

Physical characteristics:• Dimensions w x d x h = 770 x 500 x 760 mm • Weight123 kg fully equipped • Full outdoor capability

- Ingress protection IP55 • Temperature range: -33 - +50°C

Fig. 85 PSR technical data and physical characteristics

LMT802.3

10Mbit/s

-48V, 0V CPRI

ANT1 ANT0 RET

RRH RRH RRH

IPv4 dataconnection Optional for

redundancy

AC/DC

AC Input

Battery Backup

-48/0V

Distribution

Data/alarms

PSRRadio

server

PSR alarms aremapped via RRH on CPRI

Fig. 86 RS RRH PSR setup and alarming concept



162

10 19“ Micro Radio Server (RSU-380) The Radio Server Unit is a low cost and zero footprint scenario for operators who want to upgrade their existing GSM equipment to UMTS. The RSU-380 is a 19’’ module with a height of 3 HU which can be mounted into an already existing GSM service rack by a minimum installation procedure. The RSU-380 is based on the RS-880 technology, sharing the following modules: • 1 CC3 • up to 2 CHC96 • 1 DRIC24_24oe The Radio Server RSU-380 provides medium capacity in conjunction with Remote Radio Heads (RRHs). The RF functionality of the Node B is incorporated in a Remote Radio Head (RRH). The RS/RRH configuration represents a versatile Node B architecture for flexible site planning. RS and RRHs interact via the technology leading Common Public Radio Interface (CPRI). Now, sites can be flexibly planned with Remote Radio Heads (RRH). Key features of the RSU-380 with RRHs include: • Max. configuration: up to 192 CES using 2 CHCs • RSU-380: up to 1/1/1/1/0/0 configuration • Operation with up to 4 RRH-m, 6 RRH-pi respectively (HW-prepared) • High power: up to 12.5 W per RRH • Low weight (<15 kg) • RX diversity supported by RRH-m and RRH-pi (HW-prepared) • HSDPA For a detailed description please see TED:UTRAN RSU-380/RRHs.



163

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 87 Radio Server Unit RSU-380



164

11 Micro Radio Server (RS-381) The Radio Server RS-381 provides medium capacity in conjunction with Remote Radio Heads (RRHs). The RF functionality of the Node B is incorporated in a Remote Radio Head (RRH). The RS/RRH configuration represents a versatile Node B architecture for flexible site planning. RS and RRHs interact via the technology leading Common Public Radio Interface (CPRI). Now, sites can be flexibly planned with Remote Radio Heads (RRH). The outdoor Radio Server RS-381 also contains the baseband part of the NB-88x product line with same following modules: Core Controller (CC), Channel Coding Card (CHC) and Digital Radio Interface Card (DRIC). It operates with the macro Remote Radio Heads (RRH-m) and is hardware-prepared for micro and pico Remote Radio Heads (RRM-pi). The RS-381 is a solution for requirements of small to medium capacity and for zero footprint locations. Therefore it can be wall or pole mounted. The power supply of the NB-381 can either be • an AC-variant, feeding up to one RRH-m (optional battery box available) or • a DC-variant, provided by PSR (Power Redundant Supply). The PSR performs

an AC/CD conversion and enables a battery backup time up to 1 h. Key features of the RS-381 with RRHs include: • Max. configuration: up to 192 CES using 2 CHCs • Capacity: 1/0/0 upgradable to 1/1/1 and 2/0/0 configuration • Operation with up to 4 RRH-m, 6 RRH-pi respectively (HW-prepared) • High power: up to 12.5 W per RRH • Low weight (< 20 kg) • RX diversity supported by RRH-m and RRH-pi (HW-prepared) • HSDPA For a detailed description please see TED:UTRAN RS-381/RRHs.



165

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 88 Radio Server RS-381



166



167

12 Abbreviations



168

A ALS Alarm Status AMR Adaptive Multi-Rate ASIC Application Specific Integrated Circuit ATM Asynchronous Transfer Mode AVS Availability Status

B BTS Base Transceiver Station

C CAN Controller Area Network CC Core Controller CC-BB CC-Base Board CC-E Core Controller - Emergency CC-N Core Controller - Normal CE Channel Element CES Circuit Emulation Service CHC Channel Coding Card CHC-C Channel Coding Card – Control CHC-C/T Channel Coding Card – Control/Traffic CHC-T Channel Coding Card Traffic CMISE Common Management Information Service Element CP Call Processing CPICH Common Pilot Channel CSI Core Shelf Interface

D DL Downlink DSP Digital Signal Processor DTMA Dual Tower Mounted Amplifier DTMARET Dual Tower Mounted Amplifier supporting Remote Electrical

Tilt DUAMCO Duplexer Amplifier Multi Coupler DUAMCORET Duplexer Amplifier Multi Coupler supporting Remote

Electrical Down tilt



169

E EEPROM Electrical Erasable Programmable Read Only Memory EMI Electro Mechanical Interface

F FACH Forward Access Channel FRS Feature Request Sheet

G GSM Global System for Mobile Communication

H HDLC High-Level Data Link Control HW Hardware

I ID Identifier IDT Inventory Data Table IP Internet Protocol ITU-T International Telecommunications Union -

Telecommunications Standardization Sector (formerly CCITT)

J K L LIU Line Interface Unit LMT Local Maintenance Terminal LNA Low Noise Amplifier

M N NOB Remote Inventory File for equipment without onboard info

element Node B PF2 2nd platform Node B

O OAM Operation & Maintenance OB-RIU Onboard Remote Inventory Unit OEM Original Equipment Manufacturer OMC Operating and Maintenance Center



170

OMC Operation and Maintenance Center OST Operational State

P PAM Pulse Amplitude Modulation PCH Paging Channel PF Platform PM Performance Management

Q R RACH Random Access Channel RADAR Radio Detection and Ranging RC Radio Commander RC Radio Commander RET Remote Electrical Tilt RI Remote Inventory RNC Radio Network Controller RSC Redundancy Switch Control Rx Receive

S SBY Standby STB Standby Status STM Synchronous Transfer Mode SW Software

T TDM Time Division Multiplex TMA Tower Mounted Amplifier Tx Transmit

U UL Uplink UMR UMTS Release UTOPIA Universal Test & Operations Physical Interface for ATM UTRAN UMTS Terrestrial Radio Access Network



171

V W X Y Z



172

01 Mn3515eu50mn 0001 Hw Intro Nodeb

Documents

Transcript of 01 Mn3515eu50mn 0001 Hw Intro Nodeb