RNC 2600 Engineering

Nokia Siemens Networks WCDMA RAN, Rel. RU20, Operating Documentation, Issue 04

WCDMA RNC Engineering Description

DN0938143

Issue 1-4Approval Date 2010-09-23

Confidential

2 DN0938143Issue 1-4


Id:0900d805807f6a85Confidential

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2010. All rights reserved

f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

DN0938143Issue 1-4

3



Table of contentsThis document has 117 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 About WCDMA RNC Engineering Description. . . . . . . . . . . . . . . . . . . . 10

2 RNC Hardware Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3 IPA2800 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.1 Internal Messaging and Resource Allocation. . . . . . . . . . . . . . . . . . . . . 153.2 Computing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.3 Redundancy Principles for IPA2800 Network Elements . . . . . . . . . . . . 17

4 Mechanical Construction of the IPA2800 Network Elements. . . . . . . . . 214.1 Cabinets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.1.1 EC216 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224.1.2 IC186/-B. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.1.3 Dimensions of Cabinets in Floor Rail on Free-standing Installations. . . 244.2 Subracks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.3 Plug-in Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.4 Cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294.4.1 General Cabling Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.5 Cooling Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

5 Cabinet and Subrack Descriptions for RNC2600. . . . . . . . . . . . . . . . . . 315.1 RNC2600 Cabinet Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315.2 Equipment in the Subracks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.3 RNC2600 Upgrades and Expansions in RN5.0 . . . . . . . . . . . . . . . . . . . 365.3.1 Optional Expansions for RNC2600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

6 Cabinet and Subrack Descriptions for RNC450. . . . . . . . . . . . . . . . . . . 376.1 RNC450 Cabinet Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376.2 Equipment in the subracks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396.3 RNC450 Upgrades and Expansions in RN5.0 . . . . . . . . . . . . . . . . . . . . 426.3.1 Mandatory Upgrades for RNC450 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426.3.2 Optional Upgrades and Expansions for RNC450 . . . . . . . . . . . . . . . . . 426.4 RNC450 Upgrades and Expansions in RN4.0 . . . . . . . . . . . . . . . . . . . . 426.4.1 Mandatory Upgrades for RNC450 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426.4.2 Optional Upgrades and Expansions for RNC450 . . . . . . . . . . . . . . . . . 43

7 Cabinet and Subrack Descriptions for RNC196. . . . . . . . . . . . . . . . . . . 447.1 RNC196 Cabinet Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447.1.1 RNC196 Step 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457.1.2 RNC196 Step 6 and RNC196 Step 7. . . . . . . . . . . . . . . . . . . . . . . . . . . 477.1.3 Hardware Upgrade to RNC196 Step 6 and RNC196 Step 7 . . . . . . . . . 497.1.4 RNC196 Step 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527.1.5 Hardware Upgrade to RNC196 Step 8 . . . . . . . . . . . . . . . . . . . . . . . . . 547.2 Equipment in the Subracks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577.3 Upgrades and Expansions for RNC196 in RN5.0 . . . . . . . . . . . . . . . . . 607.3.1 Mandatory Upgrades for RNC196 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

4 DN0938143Issue 1-4



7.3.2 Optional Upgrades for RNC196 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607.4 Upgrades and Expansions for RNC196 in RN4.0. . . . . . . . . . . . . . . . . . 617.4.1 Mandatory Upgrades for RNC196 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617.4.2 Optional Upgrades for RNC196 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

8 Functional Unit Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628.1 Functional Unit Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628.2 Management, Control Computer and Data Processing Units . . . . . . . . . 628.2.1 DMCU, Data and Macro Diversity Combining Unit . . . . . . . . . . . . . . . . . 628.2.2 GTPU, Gateway Tunneling Protocol Unit . . . . . . . . . . . . . . . . . . . . . . . . 648.2.3 ICSU, Interface Control and Signalling Unit . . . . . . . . . . . . . . . . . . . . . . 678.2.4 Integrated OMS, Operation and Maintenance Server and its sub-units . 708.2.5 ESA24, Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738.2.6 ESA12, Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748.2.7 OMU, Operation and Maintenance Unit and Its Subunits . . . . . . . . . . . . 758.2.8 RRMU, Radio Resource Management Unit . . . . . . . . . . . . . . . . . . . . . . 808.2.9 RSMU, Resource and Switch Management Unit . . . . . . . . . . . . . . . . . . 838.3 Switching and Multiplexing Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868.3.1 A2SU, AAL2 Switching Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888.3.2 MXU, Multiplexer Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 908.3.3 SFU, Switching Fabric Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 928.4 Network Interface Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 958.4.1 NIP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968.4.2 NIS1 / NIS1P. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978.4.3 NPS1 / NPS1P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978.4.4 NPGE / NPGEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998.5 Timing, Power Distribution and Hardware Management Subsystems . 1008.5.1 TBU, Timing and Hardware Management Bus Unit . . . . . . . . . . . . . . . 1008.5.2 HMS, Hardware Management Subsystem . . . . . . . . . . . . . . . . . . . . . . 1048.5.3 Power Distribution Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078.6 EHU, External Hardware Alarm Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . 111

9 Interfaces to the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1129.1 Power Supply and Grounding Interfaces . . . . . . . . . . . . . . . . . . . . . . . 1129.2 PDH TDM Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1169.3 SDH TDM Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1169.4 External Synchronisation Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 1169.5 External HW Alarm Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1179.6 Ethernet/LAN Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1179.7 Mouse, Keyboard, VDU, SCSI and Printer Interfaces . . . . . . . . . . . . . 1179.8 RS232 Service Terminal Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

DN0938143Issue 1-4

5



List of figuresFigure 1 Block diagram of the RNC2600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 2 Block diagram of the RNC450 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 3 EC216 cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Figure 4 IC186-B cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Figure 5 Dimensions of the EC216 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Figure 6 Dimensions of the IC186-B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Figure 7 Dimensions of EC216 / IC186-B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Figure 8 SRA1 subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Figure 9 Layout options for the RNC2600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Figure 10 RNAC cabinet in RNC2600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Figure 11 RNBC cabinet in RNC2600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Figure 12 Layout options for the RNC450 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Figure 13 RNAC cabinet in RNC450 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Figure 14 RNBC cabinet in RNC450 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Figure 15 Layout options for the RNC196 (with optional cabling cabinet) . . . . . . . 44Figure 16 RNAC cabinet - RNC196 step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Figure 17 RNBC cabinet - RNC196 steps 2-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Figure 18 RNAC cabinet - RNC196 steps 6 and 7. . . . . . . . . . . . . . . . . . . . . . . . . 48Figure 19 RNBC cabinet - RNC196 steps 6 and 7. . . . . . . . . . . . . . . . . . . . . . . . . 49Figure 20 Configuration steps RNC196 step 6 and 7 with mandatory hardware

changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Figure 21 RNAC cabinet - RNC196 step 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Figure 22 RNBC cabinet - RNC196 step 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Figure 23 Configuration step RNC196 step 8 with mandatory hardware changes 56Figure 24 DMCU's interfaces - CDSP-DH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Figure 25 DMCU's interfaces - CDSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Figure 26 GTPU's interfaces - CCP18-C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Figure 27 GTPU's interfaces - CCP18-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Figure 28 GTPU's interfaces - CCP10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Figure 29 ICSU's interfaces - CCP18-C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Figure 30 ICSU's interfaces - CCP18-A. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Figure 31 ICSU's interfaces - CCP10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Figure 32 Integrated OMS interfaces (MCP18-B) . . . . . . . . . . . . . . . . . . . . . . . . . 71Figure 33 Integrated OMS storage device interfaces. . . . . . . . . . . . . . . . . . . . . . . 72Figure 34 SCSI connection principle for integrated OMS storage devices (MCP18-B)

73Figure 35 ESA24's interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Figure 36 ESA12's interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Figure 37 OMU's interfaces - CCP18-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Figure 38 OMU's interfaces - CCP10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Figure 39 OMU's storage devices' interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Figure 40 SCSI connection principle for OMU storage devices - CCP18-A and HDS-B

79Figure 41 SCSI connection principle for OMU storage devices - CCP10, HDS-A and

MDS-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Figure 42 RRMU's interfaces - CCP18-C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

6 DN0938143Issue 1-4



Figure 43 RRMU's interfaces - CCP18-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Figure 44 RRMU's interfaces - CCP10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Figure 45 RSMU's interfaces - CCP18-C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Figure 46 RSMU's interfaces - CCP18-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Figure 47 RSMU's interfaces - CCP10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Figure 48 ATM connections to SFU - RNC450 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Figure 49 A2SU's interfaces - AL2S-D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Figure 50 A2SU's interfaces - AL2S-B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Figure 51 MXU's interfaces - MX1G6 and MX1G6-A . . . . . . . . . . . . . . . . . . . . . . . 91Figure 52 MXU's interfaces - MX622 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Figure 53 SFU's interfaces - SF20H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Figure 54 SFU's interfaces - SF10E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Figure 55 SFU's interfaces - SF10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Figure 56 NIP1's interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Figure 57 NIS1's interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Figure 58 NPS1(P) interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Figure 59 NPGE(P) interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Figure 60 TSS3/-A's interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Figure 61 TBUF's interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Figure 62 Connection principle of the duplicated clock distribution bus . . . . . . . . 104Figure 63 Block diagram of the HMS subsystem . . . . . . . . . . . . . . . . . . . . . . . . . 105Figure 64 Connection principle of the duplicated HMS bus . . . . . . . . . . . . . . . . . 106Figure 65 PD30/PD20's interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Figure 66 General power distribution principle for RNC . . . . . . . . . . . . . . . . . . . . 110Figure 67 DC/DC converter structure in a plug-in unit . . . . . . . . . . . . . . . . . . . . . 111Figure 68 Power supply interfaces of CPD120-A with DC/I principle . . . . . . . . . . 113Figure 69 Power supply interfaces of CPD120-A with DC/C principle . . . . . . . . . 114Figure 70 Power supply interfaces of CPD80-B with two connection alternatives and

optional ETS grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Figure 71 Power supply interfaces of CPD80-A and their connection alternatives:

DC/I and DC/C principle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

DN0938143Issue 1-4

7



List of tablesTable 1 Computing platform hierarchy levels for IPA2800 RNC . . . . . . . . . . . . 16Table 2 Redundancy principles of the functional units in the RNC . . . . . . . . . . 19Table 3 Number of units in RNC2600 subracks . . . . . . . . . . . . . . . . . . . . . . . . . 34Table 4 Maximum number of units in the RNC2600 for each configuration step 34Table 5 Numbers of units in RNC450 subracks . . . . . . . . . . . . . . . . . . . . . . . . . 39Table 6 Maximum number of units in the RNC450 for each configuration step . 40Table 7 Minimum hardware level and configuration expansion for RNC196 step 6

51Table 8 Minimum hardware level and configuration expansion for RNC196 step 7

51Table 9 Minimum hardware level and configuration expansion for RNC196 step 8

57Table 10 Number of units in RNC196 subracks . . . . . . . . . . . . . . . . . . . . . . . . . . 57Table 11 Maximum number of units in RNC196 for each configuration step . . . . 59

8 DN0938143Issue 1-4



DN0938143Issue 1-4

9

WCDMA RNC Engineering Description Summary of changes


Summary of changesChanges between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Issue 1-4In Table 1 Computing Platform Hierarchy Levels, operating system for MCP18-B has been corrected to Linux.

Issue 1-3Reference to Hardware upgrades from RNC196 step 7 to step 8 removed because this document is not ready.

Issue 1-2MCP18-B removed.

added text to clarify the difference between Upgrade and Expansion in Chapter 1. Added Chaper 5.3 RNC2600 Upgrades and Expansions in RN5.0.Chaper 6.3.1, added Minimum hardware requirement for all configurations in RN5.0: the disk size for Inte-grated OMS must be at least 147 GB. Added reference to Hardware Expansion for RNC450 and Upgrading RNC450 to RNC2600Chaper 6.3.2, Added reference to Hardware Expansion for RNC450 and Upgrading RNC450 to RNC2600Chaper 6.4.1, Added reference to Hardware Expansion for RNC450 and Upgrading RNC450 to RNC2600Chaper 7.3.1, added Minimum hardware requirement for all configurations in RN5.0: the disk size for Integrated OMS must be at least 147 GB. Chaper 7.3.2, Added reference to Hardware Expansion for RNC196.Chaper 7.4.1, Added reference to Hardware Expansion for RNC196.

Issue 1-1Chapter 1: Noted that the upgrades supported in RN4.0 are also supported in RN5.0. Added RNC196 step 5 to step 6 and 7. Added Full CDSP-DH upgrade.

Chapter 6.3.3 Optional upgrades and expansions for RNC450:Noted that the upgrades supported in RN4.0 are also supported in RN5.0. Added full CDSP-DH upgrade.

Chapter 6.4.2 Optional upgrades and expansions for RNC450: Added Full CDSP-DH upgrade.

Chapter 7.1.4 RNC196 step 8 and chapter 7.1.5 Hardware upgrade to RNC196 step 8 was updated according to new architecture.

Chapter 7.3.2 Optional upgrades for RNC196: Added RNC196 step 7 to step 8 upgrade. Added Full CDSP-DH upgrade. Noted that the upgrades supported in RN4.0 are also supported in RN5.0.

Issue 1-0Issue 1-0 is the first issue for the RNC2600 network element with RN5.0 software.

The main, optional change from RN4.0 is that the functional unit OMS can be selected between the current integrated OMS or an external standalone OMS network element. For RN5.0 new deliveries, the standalone OMS is recommended.

With the integrated OMS, its plug-in unit MCP18-B and the related two HDDs must also be removed, as well as all SCSI connections between OMS and the HDD, and the LAN connection between OMS and the Ethernet Switch (ESA24).

10 DN0938143Issue 1-4


Id:0900d80580751dacConfidential

About WCDMA RNC Engineering Description

1 About WCDMA RNC Engineering DescriptionThis Engineering Description provides the basic information needed for the installation planning of the WCDMA RNC. It does not include the installation planning instructions for the site power supply equipment or for the PDH and alarm distribution frames.

WCDMA RNC Engineering Description provides the following information:

• System architecture • Mechanical construction of the network element • Cabinet and subrack descriptions for RNC2600 • Cabinet and subrack descriptions for RNC450 • Cabinet and subrack descriptions for RNC196 • Functional unit descriptions • Interfaces to the environment

New deliveries, expansions, and upgradesThis document describes the hardware configurations, mechanics, and electromechan-ics for RNC2600 new deliveries and expansions, as well as upgrades and expansions for previously delivered RNC450 and RNC196 at RN5.0 and RN4.0 hardware level. Cabinet mechanics used in the different delivery types are described in section Mechan-ical construction of the IPA2800 network elements. Hardware configurations for RNC450 are described in section Cabinet and subrack descriptions for RNC450 and for RNC196 (Upgrading to RNC196 step 6 and 7, upgrading RNC196 step 7 to step 8) in section Cabinet and subrack descriptions for RNC196.

For more information on upgrades at RN5.0 hardware level, see Upgrading from RN4.0 OMS to RN5.0 OMS and Upgrading from integrated RNC OMS to standalone RNC OMS.

For more information on upgrades at RN4.0 hardware level, see Upgrading RNC450 to RNC2600, Replacing CDSP-C with CDSP-DH and Enabling HSDPA Capacity Enhancement in CDSP-DH and SFU and IP Upgrade.

Full CDSP-DH upgrade is supported at RN4.0 and RN5.0 hardware level, see Replacing CDSP-C with CDSP-DH and Enabling HSDPA Capacity Enhancement in CDSP-DH and SFU and IP Upgrade.

All upgrades supported in RN4.0 are also supported in RN5.0.

The term “expansion” in this document means that extra hardware is added to RNC to provide new configuration step, for example from RNC2600 step 1 to RNC2600 step 3. Term “upgrade” means that existing hardware is some how changed to provide the use of new feature or capacity level, for example from RNC196 step 5 to RNC196 step 6/7, RNC196 step 7 to 8, IP upgrade, etc.

Other related documentationThe site requirements for the RNC are described in the document Installation Site Requirements for MGW and RNC. It provides the following information:

• Technical specifications • General hardware platform requirements • Equipment room requirements • Site power supply • Grounding and bonding

DN0938143Issue 1-4

11

WCDMA RNC Engineering Description About WCDMA RNC Engineering Description

Id:0900d80580751dacConfidential

• Electromagnetic compatibility • Operational environment • Ventilation in the equipment rooms • Specifications of interfaces to the environment

For information on changes in previous releases, which have been removed in this release, see Upgrades and expansions for RNC196 in RN3.0/RN2.2 and NEMU, Network Element Management Unit and its subunits in WCDMA RNC Engineering Description documents for previous releases and Product Description for RNC2600.

12 DN0938143Issue 1-4


Id:0900d805807031f0Confidential

RNC Hardware Changes

2 RNC Hardware ChangesThis section summarises the differences in the hardware implementation between RN4.0 and RN5.0.

New plug-in unitsCompared to RNC2600 on RN4.0 level, RNC2600 on RN5.0 level contains the following new plug-in units:

• TSS3-A clock plug-in unit Implemented to RN5.0 based RNC2600, with special instructions available for and can be used with RN4.0 softwareDue to 2N redundancy a mixed configuration of TSS3 and TSS3-A is not allowed

Functional units changes

• As of RN5.0, the functional unit OMS can be selected between the current integrated OMS or an external standalone OMS network element. For RN5.0 new deliveries, the standalone OMS is recommended.

DN0938143Issue 1-4

13

WCDMA RNC Engineering Description IPA2800 System Architecture


3 IPA2800 System ArchitectureThe IPA2800 network elements have a distributed processing architecture based on a modular software and hardware structure. The distribution of processes is achieved by using a multi-processor system, in which the functions of the network element are divided among several functional units. In the IPA2800 network element, each functional unit usually consists of one plug-in unit, which has a fixed capacity. The capacity reserved for a given function can be increased by simply installing additional units of the appropriate type to the configuration – another benefit from the modular structure.

Each functional unit has a separate task group to handle. For example, the ATM Switch Matrix has been organised as a separate unit, Switch Fabric Unit (SFU), and it is con-trolled by another unit, called Resource and Switch Management Unit (RSMU). The key operation and maintenance functions are performed by the Operation and Maintenance Unit (OMU), the external SDH STM-1 and Ethernet interfaces are provided by the Network Interface Units (NPS1(P)) and (NPGE(P)), respectively, and so on.

Each functional unit has its own, separate hardware and software; some of them are equipped with a dedicated Pentium®II, Pentium®III or Pentium®M 745-type computer. These units are referred to as computer units, some of which have storage devices as dedicated sub-units. The hardware of the functional units and the tasks each unit handles are described in more detail in chapter Functional unit descriptions. Further information is available in the Product Description.

The figures below present the block diagrams of the Radio Network Controller, RNC2600 and RNC450, their functional units and the internal and external interfaces.

14 DN0938143Issue 1-4



IPA2800 System Architecture

Figure 1 Block diagram of the RNC2600

RSMU

SFU

ICSU

DMCU

DN70618302

MANAGEMENT, CONTROL COMPUTERAND DATA PROCESSING UNIT

SWITCHING AND MULTIPLEXING UNIT

NETWORK INTERFACE UNIT

MXU

DMCU

ICSU

MXU

EHU

NPGE(P)

OMS*

HDD*

OMU

WDU

MXU

TBU

Ethernet

Ethernet

Ethernet

NPS1(P)

SWU

* Optionally, the integrated OMS and the related HDDs can be removed as of RN5.0.

DN0938143Issue 1-4

15



Figure 2 Block diagram of the RNC450

3.1 Internal Messaging and Resource AllocationIn terms of network element architecture, perhaps the most significant single feature of the ATM technology is that it allows for relatively easy designing of switching devices with high capacity and low delay. A primary bottleneck in the design of the 2nd genera-tion systems, the switching capacity is no longer such a limiting factor in 3rd generation systems. This is reflected in the architecture of the RNC in the following ways:

• Nearly all of the network element's internal traffic is routed through its switching fabric. In the IPA2800 network elements, the message bus between its units consists of standard ATM virtual channels routed through the switching fabric.However, the IPA2800 has timing and Hardware Management (alarm) buses separate from the ATM connections. The timing bus has been separated to ensure that the strict timing requirements of the ATM technology are met, while an individual Hardware Management bus ensures that some basic functions in the network

SFU

TBU

EHU

NIS1

DMCU

IuIurIub

E1/T1/JT1ATM

ICSU

RRMU

RSMU

OMU

WDUFDU

A2SU

GTPU

OMS */NEMU

IuIurIub

STM-1ATM

Harddisk

ETHERNET

100 BASE Tx

DN01128754

MANAGEMENT, CONTROL COMPUTERAND DATA PROCESSING UNIT

SWITCHING AND MULTIPLEXING UNIT

NETWORK INTERFACE UNIT

MXU

A2SU

GTPU

DMCU

ICSU

A2SU

GTPU

DMCU

ICSU

NIP1

MXU

MXU

DMCU

* OMS replaces NEMU in RN3.0

16 DN0938143Issue 1-4




element can be carried out without any support from its control units when the network element is being taken into use, upgraded or serviced, or during normal operation.

• Virtually all DSPs (Digital Signal Processors) in the system can be used by any control computer. In the IPA2800 network elements, the DSPs are organised as pools whose services are available to the control computers through the ATM virtual message bus. This ensures optimal use of the system's DSP resources. As a consequence, the plug-in units containing DSPs have been separated from the control computers on the func-tional unit level and they form functional units of their own.This kind of architecture has been achieved by enabling the routing of the user data of a call multiple times through the switching fabric while it is being processed.

3.2 Computing SystemThe computing system of the IPA2800 network elements consists of various micropro-cessor based computers and microcontrollers with either proprietary or standard oper-ating systems, as well as standard message transfer protocols. It is organised according to a four-level hierarchy, as shown in the table below.

Management computer unit MCP18-B and control computer unit CCP18-C/CCP18-A/CCP10The MCP18-B and CCP18-C / CCP18-A / CCP10 plug-in units are used as the man-agement computer units and control computer units, respectively, in the IPA2800 network elements. Both are single board computers with an onboard PCI bus. The

Level Type Processor Operating system

PIUs Communica-tion to upper level/other units

Level 4 Management computer

Intel P M 745

Intel PIII

Linux MCP18-B TCP/IP

Level 3 Control computer

Intel Pentium M (CCP18-C / CCP18-A)

Intel PIII (CCP10)

DMX with POSIX

CCP18-C/ CCP18-A/ CCP10

LAN/Ethernet, ATM virtual channels

Level 2 Unit computer Motorola Power-Quicc II

Chorus MX1G6/-A,

SF10E,

AL2S-D/-B, CDSP-C/-B/-DH,

NP2GE-B, NP8S1-B

ATM virtual channels

Level 1 Control proces-sor

8-bit microcon-troller

No OS needed

Embedded in all PIUs

Selected case by case

Table 1 Computing platform hierarchy levels for IPA2800 RNC

DN0938143Issue 1-4

17



MCP18-B and CCP18-C / CCP18-A are based on Pentium M 745 1800 MHz micropro-cessor.

As of RN5.0, the functional unit OMS can be selected between the current integrated OMS or an external standalone OMS network element. For RN5.0 new deliveries, the standalone OMS is recommended.

For more information on the MCP18-B and CCP18-C / CCP18-A / CCP10 plug-in units, see the individual Plug-in Unit Descriptions online.

3.3 Redundancy Principles for IPA2800 Network ElementsThe reliability of the operations in the IPA2800 network elements has been ensured by backing up all crucial parts of the system following various redundancy principles, as described in the sections below. Functional unit-specific redundancy principles are named in chapter Functional unit descriptions.

Redundancy of the functional unitsDifferent redundancy techniques are used for backing up different types of functional units. The Operation and Maintenance Unit, the main Switch Fabric, the radio resource and switch control units along with all crucial databases are backed up according to the 2N redundancy principle, that is, by duplication according to the hot-standby method. When a defect is detected in an active functional unit, a spare unit is set active by an automatic recovery function. The spare unit is designated for only one active unit, and the software in the unit pair is kept synchronised.

Most units with 2N redundancy, except for most of the subrack-specific Timing Buffers and multiplexers, are located in the two first subracks of the network element. The two units of a mutually redundant pair are placed in different subracks. Switchover can be performed between units of a redundant unit pair independently of the other correspond-ing pairs, which means that no subrack-level switchover procedure is needed in the network element.

The STM-1 network interface units can optionally use 2N redundancy. Until RN3.0, NIS1 unit is the default non-redundant unit. As of RN4.0, NPS1 and NPGE units are the default non-redundant units. These can be turned into redundant, 2N duplicate, units (NIS1P or NPS1P and NPGEP, respectively) providing additional equipment protection by adding another NIS1, NPS1 or NPGE unit to the network element or by changing the cabling of the existing two units. In NIS1, the SDH transmission protection is ensured by the MSP 1+1, bidirectional protection switching mode, where the traffic is carried via two multiplex sections.

The signalling units, AAL2 switch, and the units handling user or control plane functions are backed up according to the N+1 or SN+ principle. N+1 principle means that there is one spare unit available ready to take over the tasks of a faulty unit. Load sharing, SN+, means that the workload is shared between all devices, and if one malfunctions, the other units are able to carry the full load.

Ensuring reliability at unit levelIn the Intel processors, the following methods are used to ensure proper operation:

• Error correcting RAM in critical parts • ECC in read-write memories • Parity checks in data transmission on the PCI bus • Reporting on certain error events in data transactions on the system bus

18 DN0938143Issue 1-4




• Memory area protection (standard Intel processor capability) • Time-out supervision • Continuous supervision of the functioning of processes including restarts, when

required • Continuous testing of operations (as a background run) in all computer units

Units without nominal redundancySome of the functional units of the network element do not have redundancy at all. These are units which interface the network element to the environment. As of RN4.0, the non-redundant units are NPGE, NPS1 and integrated OMS. As of RN5.0, the func-tional unit OMS can be selected between the current integrated OMS or an external standalone OMS network element. For RN5.0 new deliveries, the standalone OMS is recommended. Integrated or standalone OMS is left without backup because a failure in it does not prevent the switching or cause any drop in the capacity available; the network element only loses both its local and upper-level operation and maintenance interface.

The network interfaces are more crucial to the whole system. The PDH network inter-face units are organised as pools of resources, with several units available at a time to handle an assignment. It is recommended that connections to any given direction will be divided between two or more units located in different subracks. This ensures that a failure in, for example, one of the power supply plug-in units will not interrupt the traffic to one direction altogether. If there is surplus capacity available for the network inter-faces, it is recommended that it be used for backing up the crucial connections and sharing the load between all the network interfaces available for connections towards that direction.

Redundancy of the power distribution, timing distribution, and Hardware Manage-ment SubsystemsVirtually the entire power distribution chain from the rectifiers and power feed cables to individual pieces of equipment in the cabinets has been duplicated to minimise the risk of downtime due to power failures in the IPA2800 equipment or cabling. The redundancy for the power supply from the rectifiers to the cabinets has been achieved by duplicating the power inputs in each cabinet, along with the input cables. The two units are placed in different subracks. On the other hand, each cabinet is equipped with a duplicated power distribution system, which allows feeding the voltages to units that are backing each other up through two separate distribution lines.

Likewise, the IPA2800 network elements have a duplicated alarm collection (or Hardware Management) and clock distribution system organised by means of redun-dant system clock or timing buffer unit in each subrack and separate, redundant cables for the alarm collection and clock distribution buses. The synchronisation reference can be fed to each IPA2800 network element from up to five inputs, three from line interfaces and two from external sources.

DN0938143Issue 1-4

19



RNC FURedundancy prin-ciple

Plug-In unit variant choices for RNC196 or

RNC450

Plug-In unit variant choices

for RNC2600

RSMU 2N 2 * CCP10

or

2 * CCP18-A

or

2 * CCP18-C

2 * CCP18-A

or

2 * CCP18-C

MXU 2N 2 * MX622-B

or

2 * MX662-C

or

2 * MX622-D

as same subrack WO-SP pair

2 * MX1G6-A

OMU 2N 2 * CCP10

or

2 * CCP18-A

2* CCP18-A

SFU 2N 2 * SF10

or

2 * SF10E

2 * SF20H

TBU 2N 2 * TSS3 or 2 * TSS3-A

in subracks 1-2 and

2 * TBUF

in other subracks

2 * TSS3 or 2 * TSS3-A

in subracks 1-2 and

2 * TBUFin other subracks

WDU / OMU 2N Mixed use of WDW18, WDW18-S, WDW36 , WDW73 or WDW147

WDW147

ICSU N+1 Mixed use of CCP10, CCP18-A, and CCP18-C

CCP18-A

or

CCP18-C

A2SU SN+ Mixed use of

AL2S-B and AL2S-D

N/A

DMCU SN+ Mixed use of CDSP-C and CDSP-DH

CDSP-DH

GTPU SN+ Mixed use of CCP10, CCP18-A, and CCP18-C

N/A

Table 2 Redundancy principles of the functional units in the RNC

20 DN0938143Issue 1-4




NIP1 No redundancy (Transport redun-dancy organised by call routing).

NI16P1A N/A

NIS1 No redundancy (Transport redun-dancy organised by call routing and/or MSP1+1).

NI4S1-B N/A

NIS1P 2N (Transport redundancy organised by MSP1+1 and call routing).

2 * NI4S1-B N/A

NPGE No redundancy NP2GE-B NP2GE-B

NPGEP 2N 2 * NP2GE-B 2 * NP2GE-B

NPS1 No redundancy (Transport redun-dancy organised by routing).

NP8S1-B NP8S1-B

NPS1P 2N (Transport redundancy organised by routing and MSP and/or MSP1+1).

2 * NP8S1-B 2 * NP8S1-B

EHU No redundancy EHAT EHAT

OMS 1) No redundancy MCP18-B MCP18-B

SWU Optional 2N (for LAN connectivity) 2)

1 * ESA12

or

1-2 * ESA24

1-2 * ESA24

1) As of RN5.0, the functional unit OMS can be selected between the current integrated OMS or an external standalone OMS network element. For RN5.0 new deliveries, the standalone OMS is recommended.

2) Equipment database does not recognise ESA24 as a functional unit and HMS does not supervise it.

RNC FURedundancy prin-ciple

Plug-In unit variant choices for RNC196 or

RNC450

Plug-In unit variant choices

for RNC2600

Table 2 Redundancy principles of the functional units in the RNC (Cont.)

DN0938143Issue 1-4

21

WCDMA RNC Engineering Description Mechanical Construction of the IPA2800 Network Ele-ments

Id:0900d805807031ffConfidential

4 Mechanical Construction of the IPA2800 Network ElementsThe mechanical construction of the IPA2800 network elements is based on M2000 mechanics platform, which follows a standard hierarchy:

• Cabinets • Cooling and power supply equipment • Subracks • Plug-in units • Internal cables

The system is based on IEC/ETSI standards for metric dimensioning, along with EN, UL, and Telcordia recommendations for advanced features in terms of safety, protection against interference, stability, and durability. Particular attention has been paid to thermal resistance.

4.1 CabinetsThe equipment of the IPA2800 network elements is housed in EC216 or IC186/-B equip-ment cabinets. Each cabinet has space for four subracks, the cabinet-specific power distribution panels plus the subrack-specific cooling equipment, all of which are installed at the factory, along with the plug-in units and intracabinet cables.

The RNC features two different equipment cabinets:

• RNC Cabinet A (RNAC) • RNC Cabinet B (RNBC)

The cabinets are dimensioned according to ETS 300119-2 and IEC 60917-2 standards. The emphasis of its design is on easy transportability and suitability for installations in premises with a normal or even lower room height. Due to the simple mechanical struc-ture with relatively few components, the cabinet is easy to assemble and disassemble when necessary.

The employment of thin sheet steel technology in its manufacture, along with the use of aluminium or sheet metal profile as the material for the doors makes the cabinet frame light in weight. When fully equipped, the weight of a single cabinet is circa:

• EC216: 260 kg • IC186/-B: 230 kg

The cabinets meet the IEC 60950 and UL 60950 safety requirements, along with the EN 300019-1-3, Class 3.1E environmental requirements. Based on a riveted (EC216) or welded (IC186/-B) frame structure, the earthquake resistance of the cabinet is in accor-dance with Telcordia GR-63-CORE Zone 4, and the EMC emission and immunity char-acteristics comply with the EN 300386 and CFR 47, FCC Part 15 standards, respectively.

NEBS complianceNEBS stands for Network Equipment Building System. It is a set of Telcordia (former Bellcore) Standards, whose purpose is to unify HW requirements and help Telephone companies to evaluate the suitability of products for use in their networks. Compliance

22 DN0938143Issue 1-4



Mechanical Construction of the IPA2800 Network Ele-ments

to NEBS is usually inquired by RBOC:s (Regional Bell Operator Company) in the USA. The IPA2800 Network Element Hardware is NEBS Level 3 compliant, covering GR-63-CORE and GR-1089-CORE in Central Office or equivalent premises, as applicable for type 2 ports, as specified in GR-1089-CORE.

4.1.1 EC216

Figure 3 EC216 cabinet

The EC216 cabinet consists of the following parts (see figure above):

• Riveted self-supporting cabinet frame made of sheet metal with incorporated mounting flanges for subrack installation and equipment place for CPD120-A cabinet power supply units

• Doors manufactured of sheet metal profile (2 pcs) • Two CPD120-A power distribution units at the top of the cabinet, complete with con-

nectors for redundant incoming and outgoing supply lines plus circuit breakers for the latter

DN0938143Issue 1-4

23



• Side cover plates at the ends of the cabinet rows • Vertical grounding bars • Adjustable feet for permanent installation • FTRA-B Fan units • CAIND-A Network Element Alarm indicator (only in the first cabinet).

• CS216-A cable shelvesCS216-A cable shelves are equipped under the two topmost subracks in the backside of the RNAC cabinet. CPAL-A, CPSY-A and CPSY-B panels are equipped below the CS216-A.

The cabinet doors can be easily removed, for example, for the duration of the installa-tion. They have levers with an active locking mechanism, plus separate locks for securing the levers to their places.

4.1.2 IC186/-B

Figure 4 IC186-B cabinet

The IC186/-B cabinet consists of the following parts (see figure above):

SideCover Plates

Plug-inunits

Subrack

Adjustment foot

Cable Support

Fan tray +Cover plate

Doors

DN02179668

CPD80-B CabinetPower distribution

Air Guide

24 DN0938143Issue 1-4




• Welded, self-supporting cabinet frame made of sheet metal, with incorporated mounting flanges for subrack installation

• Doors manufactured of aluminium profile (4 pcs) • Two CPD80-B power distribution units at the top of the cabinet, complete with con-

nectors for redundant incoming and outgoing supply lines plus circuit breakers for the latter

• Side cover plates at the ends of the cabinet rows • Grounding flanges between adjacent cabinets (4 pcs) • Vertical grounding bars (2 pcs) • Horizontal grounding bars (5 pcs) • Adjustable feet for permanent installation (4 pcs)

The cabinet doors can be easily removed, for example, for the duration of the installa-tion. They have levers with an active locking mechanism, plus separate locks for securing the levers to their places.

4.1.3 Dimensions of Cabinets in Floor Rail on Free-standing InstallationsThe cabinets can be installed either on floor rails or free-standing. The final installation height of the cabinets varies somewhat, depending on whether they are installed on rails or free-standing.

The equipment room must have a height of at least 2300 mm (86.8 in) with EC216 and 1900 mm (74.8 in) with IC186/-B, so that the cabinets can be lifted to upward position from the horizontal position they are transported in.

The minimum distance between an RNC cabinet and another cabinet row is 700 mm (27.6 in). If installed to the end of an existing row, the minimum distance between the end of a cabinet row and the wall is 1000 mm (39.4 in) for working area.

The dimensions of the EC216 cabinet, and the needed space for conducting cables from the top or bottom of the cabinet are shown in the figure below.

DN0938143Issue 1-4

25



Figure 5 Dimensions of the EC216

The dimensions of the IC186/-B cabinet and the needed space for conducting cables from the top or bottom of the cabinet are shown in the figure below.

26 DN0938143Issue 1-4




Figure 6 Dimensions of the IC186-B

For more information on requirements of the equipment room and layout, see sections Operational environment and Equipment room layout in Installation Site Requirements for MGW and RNC.

Dimensions of cabinets in free-standing installationWhen installed free-standing, the cabinets stand on adjustable feet. The dimensions of the cabinet frame adjustment range provided by the feet are shown in the below figure.

600

DN02133818 FRONT

180

100

70

500

50

50

50

50

Primary areafor routing cables

Secondary areafor routing cables

Secondary areafor routing cables

IC186

DN0938143Issue 1-4

27



Figure 7 Dimensions of EC216 / IC186-B

Dimensions of cabinets in installation on floor railsThe height of the cabinet rows, when installed on floor rails, is the following:

• EC216: 2060 mm (81.1 in) plus the height of the rail and accessories • IC186/-B: 1760 mm (69.3 in) plus the height of the rail and accessories

For example, if 75-mm (3 in) high rails are used, the total height of the EC216 cabinets is 2135 mm (84.1 in).

4.2 SubracksThe RNC uses the following subrack types:

EC216:

• SRA3: all subracks • SRBI-C: all subracks

IC186-B:

• SRA1-B / SRA1-A: subracks 1-2 in RNAC • SRA2-B / SRA2-A: subracks 3-4 in RNAC and 1-4 in RNBC • SRBI-B: subracks 3-4 in RNAC and 1-4 in RNBC

RNAC subracks 1 and 2 house nearly all 2N redundant equipment in the network element. Units which make up a mutually redundant pair are placed in separate sub-racks, except for upgrades from previously delivered RNCs to RNC196 step 6 and

28 DN0938143Issue 1-4




RNC196 step 7. Each of the two subracks has an individual configuration, with N+1-redundant units or those with no redundancy equipped in some of the slots.

RNAC subracks 3 and 4 and all RNBC subracks feature N+1 redundant units or those with no backup at all, with 2N redundant pairs of MXU units in each subrack as the only exceptions. A 2N redundant MXU is located in the same subrack as all tributary units connected to them are in the same subrack.

The differences between the different subrack types are:

• In comparison to SRA1, SRA2 and SRA3 integrate more of the internal cabling of the subrack, such as signals from the MXUs to tributary units, into its back interface unit.

• SRBI-C is equipped behind the SRA3 and SRBI-B is equipped behind the SRA2 subrack to provide modular backplane connections using BIE1T or BIE1C connector panels.

The subracks are designed according to the ETS 300119-4 standard, with particular attention paid to durability even under demanding conditions, along with compact dimensioning for optimal use of cabinet space. Their simple attachment mechanism makes it easy to demount the subrack and replace it with a new one in case it gets broken.

The IPA2800 network elements provide full EMC protection on the cabinet level.

All subracks are installed in the cabinets at the factory. The dimensions of the subracks are (H x W x D):

• 300 x 500 x 300 mm (11.8 x 19.7 x 11.8 in).

Figure 8 SRA1 subrack

4.3 Plug-in UnitsThe printed circuit boards of the plug-in units are multi-layered and covered with a pro-tective coating. They enable the use of both soldered and pressfit through-hole compo-nents, along with surface-mounted ones. The plug-in units are generally connected to

DN99572546

DN0938143Issue 1-4

29



the other parts of the system by means of backplane connectors of Hard Metric type, which are designed in accordance with the IEC 1076-4-101 standard. Some of the con-nections, however, are made from the front panels, normally by means of standard RJ-45 connectors.

The plug-in units of the IPA2800 network elements are designed to support hot-swap-ping. They are equipped with various LED indicators for monitoring the unit's condition; one indicator found in each unit, for example, shows that the unit is separated from the system and can be extracted from the subrack.

The printed boards of the plug-in units come in two sizes (H x D):

• 115 x 285 mm (4.5 x 11.2 in; TBUF and TSS3/-A units) • 265 x 285 mm (10.4 x 11.2 in; all other plug-in units)

The front panels of the units are made of aluminium. They are equipped with inser-tion/extraction levers, which help to manage the friction encountered at their installation, caused by the high number of connector pins typically needed for the backplane con-nections. The levers are a highly appropriate feature, since the force to be overcome for a single plug-in unit may be as high as 400 N, equal to the weight of 41 kilograms.

Like their printed boards, the front panels of the plug-in units come in two sizes (H x W):

• 145 x 25 mm (5.71 x 0.98 in; TBUF and TSS3/-A units) • 295 x (n x 25) mm (11.61 x (n x 0.98) in; all other plug-in units)

4.4 CablingThe cabling of the network element consists of interconnection cables (intermediate cables) and station cables (outgoing cables) as described below. All connections to the Switch Fabric, multiplexing units, and the wideband network interfaces are made by means of high-frequency (HF) cables. Elsewhere in the system, the type of the cables used has been determined on the basis of the requirements of the associated hardware, following standard practices in the industry.

Interconnection cablesThe interconnection cables comprise all cables running inside and between the cabinets which form a single network element. The interconnection cables are cut to length and equipped with connectors. They comprise the following cables:

• Power supply cables • ATM connection cables • Hardware Management Bus cables • Synchronisation and timing cables • SCSI cables between storage devices and their master units • LAN/Ethernet cables

Site cablesThe site (outgoing) cables are all the cables which leave the network element. They include:

• Trunk circuit cables from the network interfaces • Power supply cables • Grounding cables • I/O cables

30 DN0938143Issue 1-4




• TCP/IP cables

The site cables connect directly to the plug-in units, to back interface units located at the rear side of the IC186/-B cabinets or to units in the cabling cabinet.

4.4.1 General Cabling PrinciplesThe general cabling principles for the IPA2800 network elements are as follows:

• The interconnection cables between plug-in units in the same subrack (intrasubrack cables) are delivered completely installed in the cabinets.

• The interconnection cables between different subracks in the same cabinet or between the equipment cabinet and the cabling cabinet (intracabinet cables) run directly from subrack to subrack/cabling cabinet. These cables are delivered com-pletely installed in the cabinets, as individual cable sets for each cabinet type. However, if the cabling cabinet is delivered separately, also the intracabinet cables for it are delivered in separate boxes.

• The interconnection cables running between different cabinets (intercabinet cables) are led directly from one cabinet to another through the cable path. These cables are delivered with one end of each cable installed in an appropriate cabinet. The interconnection cables are delivered as prefabricated cable sets.

• The site cables can be routed to the environment through the opening at the bottom (raised floor installations) or top plate (normal installation) of the cabinet. These cables must be installed at the site.

All the cables entering the cabinet(s), except for the DC power feed cables, must have protective wires which are grounded to the frame of the network element at the connec-tors in the cabling cabinets.

4.5 Cooling EquipmentEach subrack in the network element is provided with a dedicated fan tray cooling unit, since forced cooling is needed in the cabinets due to the high thermal density. There are two fan tray variants:

• FTRA-B in EC216, controlled by PD30 • FTRA in IC186/-B, controlled by PD20

The fan trays have eight separate fans with an aggregate capacity sufficient to ensure N+1 redundancy (if one of the fans fails, this will not cause any rise in the temperature) and air deflectors, which help to spread the cool air evenly through the subrack.

The FTRA-B fan trays are controlled by the PD30 power supply plug-in units and the FTRA fan trays are controlled by the PD20 plug-in units on the basis of messages sent by OMU. OMU, in turn, is supported by the Hardware Management System, which collects alarms from FTRA/-Bs and controls the temperature inside each plug-in unit. In case high temperatures are detected, OMU will automatically instruct the PD30/PD20s (via the HMS bus) to increase the rotation speed of the fans so that the temperature can be restored to an appropriate level.

Like the subracks, FTRA/-B fan trays are fixed to the cabinets by attaching them to the mounting flanges. In case of a severe fault, a fan tray can be hot-swapped without any need for plug-in unit switch-over procedures. For more information, see Replacing plug-in units and other hardware units.

DN0938143Issue 1-4

31

WCDMA RNC Engineering Description Cabinet and Subrack Descriptions for RNC2600

Id:0900d8058072d088Confidential

5 Cabinet and Subrack Descriptions for RNC2600

5.1 RNC2600 Cabinet TypesThe RNC2600 features two different equipment cabinets, RNAC and RNBC, of the type EC216. The subracks of the cabinets are assigned with numbers starting from 1 at the top of cabinet and ending to 4 at its bottom.

The RNAC and RNBC cabinets can be configured from left to right or from right to left. The positions of the cabinets in the two different layout options are shown in the figure below.

Figure 9 Layout options for the RNC2600

RNC2600 has three configuration steps:

• RNC2600/Step 1Configuration step 1 of RNC2600 implements the minimum capacity and it consists of cabinet mechanics for RNAC and a fully equipped RNAC cabinet.

• RNC2600/Step 2Configuration step 2 of RNC2600 consists of a fully equipped RNAC cabinet and cabinet mechanics for RNBC cabinet; all four subracks for RNBC cabinet, all needed plug-in unit types for subracks 1 and 2 of RNBC cabinet, and cover plates for subracks 3 and 4 of RNBC cabinet. Configuration step 2 of RNC2600 includes no plug-in units for subracks 3 and 4 in RNBC, not even PD30s or TBUFs. Cover plates fill the front sides of subracks 3 and 4 entirely.

• RNC2600/Step 3Configuration step 3 of RNC2600 consists of all needed plug-in unit types equipped at RNAC and RNBC cabinets.

In addition to the RNC2600 configuration steps:

DN0624966

1200mm

RNBCRNAC600mm

Left-to-right configuration

Right-to-left configuration

RNBC RNAC

Front side of the cabinets

32 DN0938143Issue 1-4



Cabinet and Subrack Descriptions for RNC2600

• The NISx units with STM-1 interfaces are replaced with NPGE(P) units with IP inter-face units or NPS1(P) units with SDH STM-1 interfaces.

• Optional second ESA24 can be ordered separately.

The following figures present the hardware configuration options and configuration steps for the RNC cabinets.

Figure 10 RNAC cabinet in RNC2600

RNAC

38

DN0938743

38

ICS

U0

19181716151413121110987654321

1

TS

S3/-

AT

BU

F

SF

U0

RS

MU

0S

WU

0O

MS

*D

MC

U0

DM

CU

1M

XU

0P

D30

MX

U1

OM

U0

WD

U0

(OM

U)

HD

D0

(OM

S)

*

DM

CU

2

38

ICS

U1

19181716151413121110987654321

2

TB

UF

TS

S3/-

A

SF

U1

RS

MU

1S

WU

1IC

SU

2D

MC

U4

DM

CU

5M

XU

2P

D30

MX

U3

DM

CU

7

OM

U1

DM

CU

6

38

ICS

U5

19181716151413121110987654321

3

TB

UF

TB

UF

ICS

U6

EH

UD

MC

U8

DM

CU

9D

MC

U1

0M

XU

4P

D30

MX

U5

DM

CU

12

ICS

U7

DM

CU

11

38

ICS

U10

19181716151413121110987654321

4

ICS

U11

ICS

U12

DM

CU

13

DM

CU

14

DM

CU

15

MX

U6

PD

30

MX

U7

DM

CU

17

ICS

U13

DM

CU

16

DM

CU

3W

DU

1(O

MU

)H

DD

1(O

MS

)*

NP

GE

P6

/N

PS

1P

4

NP

GE

P4

/N

PS

1P

2N

PG

EP

7/

NP

S1P

5

NP

GE

P5

/N

PS

1P

3

ICS

U3

ICS

U4

ICS

U8

ICS

U9

TB

UF

TB

UF

NP

GE

P0

/N

PS

1P

0N

PG

EP

2

NP

GE

P1

/N

PS

1P

1N

PG

EP

3RNC2600/Step 1

Optionally, theintegrated OMSand the tworelated HDDs canbe removed as ofRN5.0

*

DN0938143Issue 1-4

33



Figure 11 RNBC cabinet in RNC2600

5.2 Equipment in the SubracksThe configurations of the subracks are shown in the tables below.

RNBC

DN0938755

RNC2600/Step 2

RNC2600/Step 3

38

ICS

U16

19181716151413121110987654321

1

TB

UF

ICS

U17

ICS

U1

8D

MC

U18

DM

CU

19

DM

CU

20

MX

U8

PD

30

MX

U9

NP

GE

P10

/N

PS

1P

8

DM

CU

21

DM

CU

22

ICS

U14

ICS

U15

NP

GE

P8

/N

PS

1P

6

ICS

U19

38

ICS

U22

19181716151413121110987654321

2

TB

UF

ICS

U23

ICS

U24

DM

CU

23

DM

CU

24

DM

CU

25

MX

U10

PD

30

MX

U11

NP

GE

P11

/N

PS

1P

9

DM

CU

26

DM

CU

27

ICS

U20

ICS

U21

NP

GE

P9

/N

PS

1P

7

ICS

U25

38

ICS

U2

8

19181716151413121110987654321

3

TB

UF

TB

UF

ICS

U29

ICS

U30

DM

CU

28

DM

CU

29

DM

CU

30

MX

U1

2P

D30

MX

U13

NP

GE

P14

/N

PS

1P

12

DM

CU

31

DM

CU

32

ICS

U26

ICS

U27

NP

GE

P12

/N

PS

1P

10

ICS

U31

38

ICS

U34

19181716151413121110987654321

4

TB

UF

ICS

U35

ICS

U36

DM

CU

33

DM

CU

34

DM

CU

35

MX

U6

PD

30

MX

U7

NP

GE

P15

/N

PS

1P

13

DM

CU

16

DM

CU

17

ICS

U32

ICS

U33

NP

GE

P13

/N

PS

1P

11

ICS

U13

TB

UF

TB

UF

TB

UF

34 DN0938143Issue 1-4




a) As of RN5.0, the functional unit OMS can be selected between the current integrated OMS or an external standalone OMS network element. For RN5.0 new deliveries, the standalone OMS is recommended.

Unit type RNAC configuration step 1 RNBC configu-ration step 2

RNBC configu-ration step 3

Min.conf.

Max. conf.

SR 1 SR 2 SR 3 SR 4 SR 1 SR 2 SR 3 SR 4 RNAC RNAC - RNBC

DMCU / CDSP-DH 4 4 5 5 5 5 5 5 18 38

EHU / EHAT — — 1 — — — — — 1 1

ICSU / CCP18-C 1 2 5 6 6 6 6 6 14 38

MXU / MX1G6-A 2 2 2 2 2 2 2 2 8 16

NPS1P / NP8S1-B 0-1 0-1 0-2 0-2 0-2 0-2 0-2 0-2 0-6 0-14

NPS1 / NP8S1-B 0-1 0-1 0-2 0-2 0-2 0-2 0-2 0-2 0-6 0-14

NPGEP / NP2GE-B 0-2 0-2 0-2 0-2 0-2 0-2 0-2 0-2 0-8 0-16

NPGE / NP2GE-B 0-2 0-2 0-2 0-2 0-2 0-2 0-2 0-2 0-8 0-16

OMU / CCP18-A 1 1 — — — — — — 2 2

- / PD30 1 1 1 1 1 1 1 1 4 8

RSMU / CCP18-C 1 1 — — — — — — 2 2

SFU / SF20H 1 1 — — — — — — 2 2

TBU / TSS3/-A 1 1 — — — — — — 2 2

TBU / TBUF 1 1 2 2 2 2 2 2 6 14

HDS-B 1 1 — — — — — — 2 2

WDU / WDW147 (OMU)

1 1 — — — — — — 2 2

HDD / WDW147 (OMS) 1)

1 1 — — — — — — 2 2

SWU / ESA24 1 0-1 — — — — — — 1-2 1-2

OMS / MCP18-B a) 1 — — — — — — — 1 1

Table 3 Number of units in RNC2600 subracks

Unit type Configuration steps

RNC2600/Step 1 RNC2600/Step 2 RNC2600/Step 3

DMCU / CDSP-DH 18 28 38

EHU / EHAT 1 for all configurations

ICSU / CCP18-C 14 26 38

MXU / MX1G6-A 8 12 16

NPS1P / NP8S1-B a)/b) 0-6 0-10 0-14

Table 4 Maximum number of units in the RNC2600 for each configuration step

DN0938143Issue 1-4

35



a) Units are optional.

b) NPS1 and NPS1P units and NPGE and NPGEP units are mutually exclusive.

c) As of RN5.0, the functional unit OMS can be selected between the current integrated OMS or an external standalone OMS network element. For RN5.0 new deliveries, the standalone OMS is recommended.

For information on the capacities of the alternative configurations, see RNC2600 capacity in Product Description for RNC2600.

Back interface units at the rear of the cabinets in RNC2600In RNC2600, the cabling cabinet is not used. Connections are made either from the back interface units located at the rear side of the cabinets or from the front panels of the plug-in units. For more information, see section Interfaces to the environment. The back inter-face units located at the rear side of the cabinet are described below:

• BISFABack interface unit SFP type A for SF20H with 24 SFP connectors for cabling to NPGE(P), NPS1(P) and MXU units. BISFA also contains an RJ-45 connector for cabling between redundant SFUs.

• BISFBBack interface unit SFP type B for MX1G6-A with 4 SFP connectors for cabling to SFU.

• BISFB-ABack interface unit SFP type B for MBMS upgrades to RNC196, IC186/IC186-B mechanics.

NPS1 / NP8S1-B a)/b) 0-6 0-10 0-14

NPGEP / NP2GE-B a)/b) 0-8 0-12 0-16

NPGE / NP2GE-B a)/b) 0-8 0-12 0-16

OMU / CCP18-A 2 for all configurations

- / PD30 4 6 8

RSMU / CCP18-C 2 for all configurations

SFU / SF20H 2 for all configurations

TBU / TSS3/-A 2 for all configurations

TBU / TBUF 6 10 14

HDS-B 2 for all configurations

WDU / WDW147 (OMU) 2 for all configurations

HDD / WDW147 (OMS) c) 2 for all configurations

SWU / ESA24 a) 1-2 for all configurations

OMS / MCP18-B c) 1 for all configurations


RNC2600/Step 1 RNC2600/Step 2 RNC2600/Step 3


36 DN0938143Issue 1-4




• BISFCBack interface unit SFP type C for NP2GE-B and NP8S1-B plug-in units. The back interface unit contains 4 SFP connectors for cabling to SFU and an RJ-45 connector for ETH service terminal for debugging the NP2GE-B or NP8S1-B.

• BISFDBack interface unit SFP type D for SF20H with 8 SFP connectors for NPGE(P), NPS1(P) and MXU units.

5.3 RNC2600 Upgrades and Expansions in RN5.0

5.3.1 Optional Expansions for RNC2600The optional hardware expansion changes the RNC2600 configuration step 1 to step 2/3, and step 2 to step 3.

For instructions on how to add RNBC expansion cabinet and configuration steps RNC2600/Step 2 and RNC2600/Step 3 to RNC configuration, see Hardware Expansion for RNC2600.

In addition to these three configuration steps, the following optional expansions are available for RNC2600:

• NPS1(P) expansion:There are no NPS1(P) units included in the basic configuration of RNC2600 by default.

• NPGE(P) expansion:There are no NPGE(P) units included in the basic configuration of RNC2600 by default.

• SWU expansion:One optional SWU can be ordered separately.

For instructions, see also Hardware Expansion for RNC2600.

DN0938143Issue 1-4

37




6.1 RNC450 Cabinet TypesThe RNC450 features two different equipment cabinets, RNAC and RNBC, of the type EC216. The subracks of the cabinets are assigned with numbers starting from 1 at the top of cabinet and ending to 4 at its bottom.

The RNAC and RNBC cabinets can be configured from left to right or from right to left. The positions of the cabinets in the two different layout options are shown in the figure below.

Figure 12 Layout options for the RNC450

RNC450 has three configuration steps:

• RNC450 step 1Configuration step 1 of RNC450 implements the minimum capacity and it consists of cabinet mechanics for RNAC and a fully equipped RNAC cabinet.

• RNC450 step 2Configuration step 2 of RNC450 consists of a fully equipped RNAC cabinet and cabinet mechanics for RNBC cabinet; all four subracks for RNBC cabinet, all needed plug-in unit types for subracks 1 and 2 of RNBC cabinet and cover plates for subracks 3 and 4 of RNBC cabinet. Configuration step 2 of RNC450 includes no plug-in units for subracks 3 and 4 in RNBC, not even PD30s or TBUFs. Cover plates fill the front sides of subracks 3 and 4 entirely.

• RNC450 step 3Configuration step 3 of RNC450 consists of all needed plug-in unit types equipped at RNAC and RNBC cabinets.

In addition to the RNC450 configuration steps:

DN0624966

1200mm

RNBCRNAC600mm



RNBC RNAC


38 DN0938143Issue 1-4




• Two NISx units with STM-1 interfaces are included in the basic configuration of RNC450 configuration step 1. Additional NISx units can be ordered separately. NIS1P 10-11 can be configured in RNAC or RNBC.

• One optional NIP1 unit with E1, T1, JT1 interfaces can be ordered separately. • Optional second ESA24 can be ordered separately.

The following figures present the hardware configuration options and configuration steps for the RNC cabinets.

Figure 13 RNAC cabinet in RNC450

RNAC

DN70621159 FRONT VIEW

DM

CU

5

DC

MU

4

ICS

U4

ICS

U5

ICS

U6

DM

CU

6

DM

CU

7

DM

CU

8

MX

U4

PD

30

MX

U5

A2S

U3

DM

CU

9

DM

CU

10

NIS

1P

10/N

IP1

0/N

PG

E(P

)0

TB

UF

TB

UF

DM

CU

12

DM

CU

11

ICS

U7

ICS

U8

ICS

U9

DM

CU

13

DM

CU

14

DM

CU

15

MX

U6

PD

30

MX

U7

A2S

U4

DM

CU

16

DM

CU

17

NIS

1P

11/N

PG

E(P

)1

GT

PU

2/IC

SU

26

NIS

1P

1/N

PG

E(P

)7

NIS

1P

3

GT

PU

1/

ICS

U2

5

SF

U0

ES

A2

40

(SW

U0

)

ICS

U22

RS

MU

0

MX

U0

PD

30

MX

U1

A2S

U0

OM

U0

DM

CU

0

DM

CU

1

OM

S

ICS

U1

ICS

U0

A2S

U1

SF

U1

ES

A2

41

(SW

U1

)

ICS

U23

RS

MU

1

MX

U2

PD

30

MX

U3

A2

SU

2

B:

HD

D1

OM

SA

:W

DU

1O

MU

OM

U1

DM

CU

2

DM

CU

3

GT

PU

0/IC

SU

24

ICS

U3

ICS

U2

EH

U

NIS

1P

0/N

PG

E(P

)6

NIS

1P

2

TB

UF

TB

UF

TB

UF

TS

S3

TS

S3

TB

UF

B:

HD

D0

OM

SA

:W

DU

0O

MU

Configurationstep 1

DN0938143Issue 1-4

39



Figure 14 RNBC cabinet in RNC450

6.2 Equipment in the subracksThe configurations of the subracks are shown in the tables below.

DN70621174

RNBC

FRONT VIEW

TB

UF

TB

UF

TB

UF

TB

UF

TB

UF

TB

UF

TB

UF

TB

UF

DM

CU

25

-/N

PG

E(P

)3

ICS

U13

ICS

U14

ICS

U15

- DM

CU

26

DM

CU

27

MX

U10

PD

30

MX

U11

A2S

U6

DM

CU

28

DM

CU

29

GT

PU

4/IC

SU

28

GT

PU

5/IC

SU

29

DM

CU

18

-/N

PG

E(P

)2

ICS

U10

ICS

U11

ICS

U12

DM

CU

19

DM

CU

20

DM

CU

21

MX

U8

PD

30

MX

U9

A2S

U5

DM

CU

22

DM

CU

23

DM

CU

24

GT

PU

3/IC

SU

27

DM

CU

30

ICS

U16

ICS

U17

ICS

U18

DM

CU

31

DM

CU

32

DM

CU

33

MX

U12

PD

30

MX

U13

A2S

U7

DM

CU

34

DM

CU

35

DM

CU

36

GT

PU

6/IC

SU

30

DM

CU

37

-/N

PG

E(P

)5

ICS

U19

ICS

U20

ICS

U21

DM

CU

38

DM

CU

39

DM

CU

40

MX

U14

PD

30

MX

U15

A2S

U8

DM

CU

41

DM

CU

42

DM

CU

43

GT

PU

7/IC

SU

31

NIS

1P

10

NIS

1P

11

-/N

PG

E(P

)4

NIS

1P

6

NIS

1P

10

NIS

1P

5

NIS

1P

7

NIS

1P

4

NIS

1P

6

Configurationstep 2

Configurationstep 3

Unit type RNAC RNBC Min Max

SR 1 SR 2 SR 3 SR 4 SRs 1–4 conf. conf.

A2SU 2 1 1 1 1 5 9

DMCU 2 2 7 7 5–7 a) 18 44

Table 5 Numbers of units in RNC450 subracks

40 DN0938143Issue 1-4




EHU — 1 — — — 1 1

GTPU — 1 1 1 1 3 7

ICSU e) 3 3–4 3–4 3–4 3–5 f) 12 32

MXU 2 2 2 2 2 8 16

OMS d) 1 — — — — 1 1

ESA24 1 0–1 — — — 1 2

OMS HDD d) 1 1 — — — 2 2

NIP1 — — 0–1 — — 0 1

NIS1 — — 1–2 1–2 0–2 b) 2 6

NIS1P — — 1–3 c) 1–3 c) 0–2 2 12

NPGE(P) — — 1–2 1–2 0–1 2 8

OMU 1 1 — — — 2 2

OMU WDU 1 1 — — — 2 2

PD30 1 1 1 1 1 4 8

RRMU e) 1 1 — — — 2 2

RSMU 1 1 — — — 2 2

SFU 1 1 — — — 2 2

TBUF 1 1 2 2 2 6 14

TSS3 1 1 — — — 2 2

a) In RNBC Sr2, there are 5 DMCU units.

b) 0–2 unprotected NIS1 units in RNBC Sr1 or Sr3. Maximum number of unprotected NIS1 units is 6.

c) NIS1P 10-11 can be configured in RNAC or RNBC.

d) Integrated OMS replaces NEMU as of RN3.0 new deliveries. As of RN5.0, the functional unit OMS can be selected between the current integrated OMS or an external standalone OMS network element. For RN5.0 new deliveries, the standalone OMS is recommended.

e) ICSU replaces RRMU in both subracks after RN4.0 software release upgrade.

f) In RNBC Sr2, there are 3–5 ICSU units. In other RNBC subracks, there are 3–4 ICSU units.

Unit type RNAC RNBC Min Max


Table 5 Numbers of units in RNC450 subracks (Cont.)


RNC450 step 1 RNC450 step 2 RNC450 step 3

A2SU 5 7 9

DMCU 18 30 44

EHU 1 for all configurations

ESA24 2 for all configurations


DN0938143Issue 1-4

41




For information on equipping rules for interface units NIS1P, NIS1, and NIP1 in RNC450, see NIS1P, NIS1, and NIP1 equipping rules in Equipment Lists for RNC450.

Back interface units at the rear of the RNAC cabinet in RNC450In RNC450, the cabling cabinet is not used. Connections are made either from the back interface units located at the rear side of the RNAC cabinet or from the front panels of the plug-in units. For more information, see Interfaces to the environment in this docu-ment. The back interface units located at the rear side of the RNAC cabinet are described below:

• CPSY-A and CPSY-BBack interface units for synchronisation with 2 pieces of BNC connectors and 3 pieces of RJ45 connectors for external synchronisation inputs and outputs in each

GTPU 3 6 8

ICSU b) 10 16 22

MXU 8 12 16

OMS a) 1 for all configurations

OMS Hard disk HDD a)

2 for all configurations

NIP1 1 for all configurations

NIS1 4 6 6

NIS1P 6 10 12

NPGE(P) 4 6 8

OMU 2 for all configurations

OMU Hard disk WDU


PD30 4 6 8

RRMU b) 2 for all configurations

RSMU 2 for all configurations

SFU 2 for all configurations

TBUF 6 10 14

TSS3 2 for all configurations

a) Integrated OMS replaces NEMU as of RN3.0 new deliveries. As of RN5.0, the functional unit OMS can be selected between the current inte-grated OMS or an external standalone OMS network element. For RN5.0 new deliveries, the standalone OMS is recommended.

b) ICSU replaces RRMU in both subracks after RN4.0 software release upgrade.


RNC450 step 1 RNC450 step 2 RNC450 step 3


42 DN0938143Issue 1-4




unit. CPSY-A (for TSS3/-A 0) and CPSY-B (for TSS3/-A 1) are equipped in the same network element.

• CPAL-ABack interface unit for alarms with one D25 connector for EXAU-A / EXAU controls, one D37 connector for general current/voltage outputs, 2 pieces of D37 connectors for voltage controlled inputs, and one D25 connector for current controlled alarm inputs.CPAL-A, CPSY-A and CPSY-B units are equipped below the CS216-A cable shelves, which are located under the two topmost subracks in the backside of the RNAC cabinet.

• BIE1T or BIE1CThe rear of the subracks are fitted with SRBI-C, subrack for back interface. If the optional NIP1 0 is used, BIE1T balanced connector panel or BIE1C coaxial connec-tor panel is installed in the SRBI-C behind the NIP1 0 installation position in RNAC subrack 3, slot 15.


6.3.1 Mandatory Upgrades for RNC450Minimum hardware requirement for all configurations in RN5.0: the disk size for Inte-grated OMS must be at least 147 GB.

Before RN5.0 software upgrade, all AL2S-B plug-in units in A2SU functional units must be replaced with the plug-in unit variant AL2S-D.

For more information, prerequisites and the instructions, see Hardware Expansion for RNC450 and Upgrading RNC450 to RNC2600.

6.3.2 Optional Upgrades and Expansions for RNC450As of RN5.0, the functional unit OMS can be selected between the current integrated OMS or an external standalone OMS network element. For RN5.0 new deliveries, the standalone OMS is recommended.

The upgrades supported in RN4.0 are also supported in RN5.0

Full CDSP-DH upgrade (replacing all CDSP-C with CDSP-DH) is supported.



6.4.1 Mandatory Upgrades for RNC450In RN4.0 software release, the RRMU functional unit is removed from configuration and is configured as ICSU unit. RRMU functions are divided between the RSMU, ICSU, and OMU functional units. The location service feature moves to RSMU.


DN0938143Issue 1-4

43



6.4.2 Optional Upgrades and Expansions for RNC450 • Upgrading RNC450 to RNC2600

This optional upgrade changes an RNC450 hardware configuration to an RNC2600 hardware configuration. As a prerequisite, the RN4.0 software upgrade must have been installed. This is a major upgrade which should be planned thoroughly in advance and only performed during a time of low traffic, by experienced site person-nel and by strict adherence to the prerequisites and upgrade process. Automated macros are available to support the upgrade process. Some of the main changes to functional unit and plug-in unit configuration are • NIS1(P) / NIP1 functional units are replaced by NPS1(P) functional units, using

new NP8S1-B plug-in units • All CDSPx plug-in units are replaced by CDSP-DH plug-in units • All MXU functional units receive the new MX1G6-A plug-in unit • SF10 and SF10E units are replaced with SF20H units • GTPU and A2SU units are removed and count of ICSU units increases • Existing functional units are relocated inside the network elementFor more information, prerequisites and the instructions, see Upgrading RNC450 to RNC2600.

• SFU upgradeIn SFU upgrade, the SF10 plug-in units are replaced by the SF10E plug-in units in the RNAC cabinet. The SFU upgrade is prerequisite for IP upgrade. New RNAC cabinet deliveries in RN4.0 use the SF10E plug-in unit, so they do not require an SFU upgrade.For more information, see SFU and IP Upgrade.

• IP upgradeIP upgrade deploys IP over Ethernet (IPoE) transport for the Iu-CS, Iu-PS and Iur interfaces of an RNC. This is achieved by equipping new NP2GE-B plug-in units into an RNC cabinet and recreating existing ATM interfaces as Ethernet interfaces. The NP2GE-B plug-in units can be equipped in a cabinet into slots specified in upgrade documentation. The SFU upgrade must be completed before starting the IP upgrade.For more information, see SFU and IP Upgrade.

• Replacing CDSP-C with CDSP-DH (RAN1266, RAN1258)CDSP-C plug-in units for DMCU can be replaced with CDSP-DH plug-in units (RAN1266) in existing installations in the following cases: • To expand the existing DMCU configuration with new units • To replace a broken unit • To enable DMCU for the feature RAN1258: HSDPA 14 Mbps per User (CDSP-

DH is mandatory equipment for RAN1258)Mixed CDSP-C and CDSP-DH configurations are allowed. However, only specific CDSP-DH units in the network element can be enabled for the RAN1258 feature.For more information, see Replacing CDSP-C with CDSP-DH and Enabling HSDPA Capacity Enhancement in CDSP-DH.

• Full CDSP-DH upgrade (replacing all CDSP-C with CDSP-DH is supported). For more information, see Replacing CDSP-C with CDSP-DH and Enabling HSDPA Capacity Enhancement in CDSP-DH.

44 DN0938143Issue 1-4


Id:0900d80580751db8Confidential



7.1 RNC196 Cabinet TypesThe RNC196 features two different equipment cabinets, RNAC and RNBC, of the type IC186-B or IC186. The subracks of the cabinets are assigned with numbers starting from 1 at the top of cabinet and ending to 4 at its bottom.

In RNC196, it is possible to include an optional cabling cabinet CEXT in the RNC con-figuration. For more information on the cabling cabinet, see section Cabinets in WCDMA RNC Engineering Description for previous releases.

The RNAC and RNBC cabinets can be configured from left to right or from right to left. CEXT can be placed on either side of the RNAC and RNBC cabinets, at the end of the row, but not in between. The positions of the cabinets in different layout options are shown in the figure below.

Figure 15 Layout options for the RNC196 (with optional cabling cabinet)

DN0426042

RNBCCEXT RNAC

CEXTRNACRNBC

RNBCCEXT RNAC

1500mm

RNBC CEXTRNAC600mm




DN0938143Issue 1-4

45



RNC196 has eight configuration steps. RNC cabinets delivered up to RN2.1 HW level featured five configuration steps. In RN2.2/RN3.0 two new configuration expansion steps are introduced for RNC196: configuration step 6 and step 7. In RN5.0, the eighth configuration expansion step is introduced.

RNC196 configuration step 1 is supported in RN2.2/RN3.0, but is not available for new deliveries. Configuration expansion steps 2–5 are also available for RNC196 in RN2.2/RN3.0 level expansion deliveries, with the exception that configuration step 2 does not include the RNBC expansion cabinet. The RNBC expansion cabinet must be ordered at RN2.1 level.

The following sections present the hardware configuration options and configuration steps for the RNC196 cabinets.

Notation RNC196 step 5 is used to refer to configuration steps 1–5. Notation RNC196 step 7 is used to refer to both RNC196 step 6 and RNC196 step 7. Notation RNC196 step 8 is used to refer to configuration step 8.

7.1.1 RNC196 Step 5Previously delivered RNC cabinets feature five configuration steps and are configured as shown in the figures RNAC cabinet - RNC196 step 1 and RNBC cabinet - RNC196 steps 2-5.

46 DN0938143Issue 1-4




Figure 16 RNAC cabinet - RNC196 step 1

RNAC

DN70621517

TS

S3

TB

UF

TB

UF

TS

S3

TB

UF

TB

UF

SF

U1

NIS

1(P

)1

RR

MU

1

RS

MU

1

MX

U1

PD

20

FD

U(O

MU

)

HD

D1

(NE

MU

/OM

S)

OM

U1

WD

U1

(OM

U)

SF

U0

NIS

1(P

)0

RR

MU

0

RS

MU

0

MX

U0

PD

20

EH

U

ES

A12

/E

SA

24

0

NE

MU

HD

D0

(NE

MU

/OM

S)

OM

U0

WD

U0

(OM

U)

NIP

11

NIP

10

/N

PG

E(P

)0

ICS

U0

ICS

U1

ICS

U2

DM

CU

0

DM

CU

1

DM

CU

2

MX

U2

PD

20

MX

U3

DM

CU

3

DM

CU

4

DM

CU

5

A2S

U1

GT

PU

0/IC

SU

24

NIS

1(P

)2

NIP

13

NIP

12

/N

PG

E(P

)1

ICS

U3

ICS

U4

ICS

U5

DM

CU

6

DM

CU

7

DM

CU

8

MX

U4

PD

20

MX

U5

DM

CU

9

DM

CU

10

DM

CU

11

A2S

U2

iIC

SU

6

GT

PU

1/

ICS

U2

5

NIS

1(P

)3

Configurationstep 1

A2S

U0

Op

tio

na

lE

SA

24

1

NIS

1(P

)5

/N

PG

E(P

)7

NIS

1(P

)7

NIS

1(P

)4

/N

PG

E(P

)6

NIS

1(P

)6

-

TB

UF

TB

UF

FRONT VIEW

DN0938143Issue 1-4

47



Figure 17 RNBC cabinet - RNC196 steps 2-5

7.1.2 RNC196 Step 6 and RNC196 Step 7The following figures show the maximum configuration after RNC196 configuration steps 6 and 7 are taken into use. The two configuration steps are presented in the same figures as the functional unit positions are the same. The two configuration steps differ in the type of plug-in unit variant used: in RNC196 step 7, the newest variants are required for all units.

DN70621532

RNBC

FRONT VIEW

NIP

17

NIP

16

/N

PG

E(P

)3

ICS

U10

ICS

U11

ICS

U12

DM

CU

20

DM

CU

21

DM

CU

22

MX

U8

PD

20

MX

U9

DM

CU

23

DM

CU

24

DM

CU

25

A2

SU

4

GT

PU

3/IC

SU

27

DM

CU

26

DM

CU

27

NIP

15

NIP

14

/N

PG

E(P

)2

ICS

U7

ICS

U8

ICS

U9

DM

CU

12

DM

CU

13

DM

CU

14

MX

U6

PD

20

MX

U7

DM

CU

15

DM

CU

16

DM

CU

17

A2

SU

3

GT

PU

2/IC

SU

26

DM

CU

18

DM

CU

19

NIP

19

NIP

18

/N

PG

E(P

)4

ICS

U13

ICS

U14

ICS

U15

DM

CU

28

DM

CU

29

DM

CU

30

MX

U10

PD

20

MX

U11

DM

CU

31

DM

CU

32

DM

CU

33

A2

SU

5

GT

PU

4/IC

SU

28

DM

CU

34

DM

CU

35

NIP

111

NIP

11

0/

NP

GE

(P)

5

ICS

U16

ICS

U17

ICS

U18

DM

CU

36

DM

CU

37

DM

CU

38

MX

U12

PD

20

MX

U13

DM

CU

39

DM

CU

40

DM

CU

41

A2

SU

6

GT

PU

5/IC

SU

29

DM

CU

42

DM

CU

43

Configurationstep 2

Configurationstep 3

Configurationstep 4

Configurationstep 5

TB

UF

TB

UF

TB

UF

TB

UF

TB

UF

TB

UF

TB

UF

TB

UF

48 DN0938143Issue 1-4




Figure 18 RNAC cabinet - RNC196 steps 6 and 7

RNAC

DN70623803

TB

U0

TB

U1

TB

U0

TB

U1

TB

U0

TB

U1

SF

U1

A2S

U8

ICS

U2

3

RS

MU

1

MX

U14

PD

20

GT

PU

6E

HU

B:H

DD

1(O

MS

)A

:W

DU

1(O

MU

)

OM

U1

ICS

U20

ICS

U21

SF

U0

A2S

U7

ICS

U2

2

RS

MU

0

MX

U0

PD

20

MX

U1

ES

A12

/E

SA

24

0

OM

S

A:W

DU

0(O

MU

)B

:H

DD

0(O

MS

)

OM

U0

ICS

U6

ICS

U19

DM

CU

34

NIP

10

(Op

tio

na

l)

ICS

U0

ICS

U1

ICS

U2

DM

CU

0

DM

CU

1

DM

CU

2

MX

U2

PD

20

MX

U3

DM

CU

3

DM

CU

4

DM

CU

5

A2S

U1

GT

PU

0

NIS

x2

DM

CU

42

- ICS

U3

ICS

U4

ICS

U5

DM

CU

6

DM

CU

7

DM

CU

8

MX

U4

PD

20

MX

U5

DM

CU

9

DM

CU

10

DM

CU

11

A2S

U2

NIS

x1

GT

PU

1

NIS

x3

Configurationstep 1

A2S

U0

Op

tio

na

lE

SA

24

1

DM

CU

26

DM

CU

27

DM

CU

18

DM

CU

19

NIS

x0

TB

U0

TB

U1

MX

U15

FRONT VIEW

DN0938143Issue 1-4

49



Figure 19 RNBC cabinet - RNC196 steps 6 and 7

7.1.3 Hardware Upgrade to RNC196 Step 6 and RNC196 Step 7An overview of the configurations for the RNC196 configuration steps 6 and 7 is shown in the figure and sections below. For more information on the hardware changes and detailed instructions on how to carry out the configuration step expansion, see document Hardware upgrades from RNC196 step 5 to steps 6 and 7.

The configuration steps differ in the requirements for plug-in unit variant level. See the tables Minimum hardware level for RNC196 step 6 and Minimum hardware level for RNC196 step 7 for more information. Both of the configuration expansion steps require cabling and configuration changes to the RNC.

DN70623815

RNBC

FRONT VIEW

-- ICS

U10

ICS

U11

ICS

U12

DM

CU

20

DM

CU

21

DM

CU

22

MX

U8

PD

20

MX

U9

DM

CU

23

DM

CU

24

GT

PU

7

A2

SU

4

GT

PU

3

NIS

1P

5

NIS

1P

7

DM

CU

25

- ICS

U7

ICS

U8

ICS

U9

DM

CU

12

DM

CU

13

DM

CU

14

MX

U6

PD

20

MX

U7

DM

CU

15

DM

CU

16

DM

CU

17

A2

SU

3

GT

PU

2

NIS

1P

/N

IS1

4

NIS

1P

/N

IS1

6

DM

CU

35

- ICS

U13

ICS

U14

ICS

U15

DM

CU

28

DM

CU

29

DM

CU

30

MX

U10

PD

20

MX

U11

DM

CU

31

DM

CU

32

DM

CU

33

A2

SU

5

GT

PU

4

NIS

1P

/N

IS1

8

NIS

1P

/N

IS1

10

DM

CU

43

- ICS

U16

ICS

U17

ICS

U18

DM

CU

36

DM

CU

37

DM

CU

38

MX

U12

PD

20

MX

U13

DM

CU

39

DM

CU

40

DM

CU

41

A2

SU

6

GT

PU

5

NIS

1P

9

NIS

1P

11

Configurationstep 2

Cstep 3

onfiguration

Cstep 4

onfiguration

Cstep 5

onfiguration

TB

U0

TB

U1

TB

U0

TB

U1

TB

U0

TB

U1

TB

U0

TB

U1

50 DN0938143Issue 1-4




The configuration of the RNC must be at least RNC196 step 5 before the RNC196 con-figuration step 6 and 7 expansions.

g In the following figure Configuration steps RNC196 steps 6 and 7 with mandatory hardware changes: in slots which show two functional unit names, the lower one shows the functional unit equipped in that slot in configuration steps 1–5 and the upper one shows the functional unit equipped in that same slot after the mandatory hardware changes have been carried out in the expansion to RNC196 step 6 and 7.

Figure 20 Configuration steps RNC196 step 6 and 7 with mandatory hardware changes

RNC196 step 6RNC196 step 6 can be achieved with the following hardware changes. For detailed infor-mation on the hardware changes and instructions on how to carry out the expansion, see document Hardware upgrades from RNC196 step 5 to steps 6 and 7.

RNAC RNBC

Configuration

Step 1

Configurationstep 2

Configurationstep 5

ICS

U3

ICS

U4

ICS

U5

DM

CU

6

DM

CU

7

DM

CU

8

MX

U4

PD

20

MX

U5

DM

CU

9

DM

CU

10

TB

U1

TB

U0

NIP

13

NIP

12

A2S

U2

DM

CU

11

GT

PU

1

NIS

x3

ICS

U6

SF

U0

A2S

U0

A2S

U7

RR

MU

0

RS

MU

0M

XU

0

PD

20

NE

MU

HD

D0

(NE

MU

)

OM

U0

TB

U1

TB

U0

DM

CU

18

DM

CU

19

WD

U0

(OM

U)

Configurationstep 4

ICS

U0

ICS

U1

ICS

U2

DM

CU

0

DM

CU

1

DM

CU

2

MX

U2

PD

20

MX

U3

DM

CU

3

DM

CU

4

TB

U1

TB

U0

NIP

11

NIP

10

A2S

U1

DM

CU

5

GT

PU

0

NIS

x2

- ICS

U13

ICS

U14

ICS

U15

DM

CU

28

DM

CU

29

DM

CU

30

MX

U10

PD

20

MX

U11

DM

CU

31

DM

CU

32

TB

U1

TB

U0

NIP

19

NIP

18

A2

SU

5

DM

CU

33

DM

CU

34

DM

CU

35

GT

PU

4

Configurationstep 3

SF

U1

NIS

x1

RR

MU

1

RS

MU

1M

XU

1

PD

20

OM

U1

TB

U1

TB

U0

FD

U

ICS

U20

ICS

U21

NIS

1P

5

NIS

1P

7

ES

A24

1(O

ptio

nal)

HD

D0

(NE

MU

)W

DU

0(O

MU

)

ICS

U10

ICS

U11

ICS

U12

DM

CU

20

DM

CU

21

DM

CU

22

MX

U8

PD

20

MX

U9

DM

CU

23

DM

CU

24

TB

U1

TB

U0

NIP

17

NIP

16

A2

SU

4

DM

CU

25

DM

CU

26

DM

CU

27

GT

PU

3

ICS

U7

ICS

U8

ICS

U9

DM

CU

12

DM

CU

13

DM

CU

14

MX

U6

PD

20

MX

U7

DM

CU

15

DM

CU

16

TB

U1

TB

U0

NIP

15

NIP

14

A2

SU

3

DM

CU

17

DM

CU

18

DM

CU

19

GT

PU

2

ICS

U16

ICS

U17

ICS

U18

DM

CU

36

DM

CU

37

DM

CU

38

MX

U12

PD

20

MX

U13

DM

CU

39

DM

CU

40

TB

U1

TB

U0

NIP

111

NIP

110

A2

SU

6

DM

CU

41

DM

CU

42

DM

CU

43

GT

PU

5

EH

U

ES

A12

/E

SA

24

0

= unit relocated or removed

= unit added

= unit upgraded to newest variant

Configuration step 6

= unit upgraded to newest variant

Configuration step 7

DN0638349

NIS

x0

NIS

x4

NIS

x6

MX

U1

ICS

U6

WD

U0

(OM

U)

ICS

U19

A2S

U8

DM

CU

26

DM

CU

27

MX

U14

MX

U15

GT

PU

6

EH

U

WD

U1

(OM

U)

DM

CU

34

Optio

nal

NIS

x0

DM

CU

42

- NIS

x1

DM

CU

43

- NIS

1P

9

NIS

1P

11

DM

CU

35

- NIS

x8

NIS

x10

NIS

x4

NIS

x6

DM

CU

25

-

-- NIS

1P

5

NIS

1P

7

GT

PU

7

DN0938143Issue 1-4

51



RNC196 step 7RNC196 step 7 can be achieved with the hardware changes listed below, required in addition to the hardware changes made for configuration step RNC196 step 6. For detailed information on the hardware changes and instructions on how to carry out the expansion, see document Hardware upgrades from RNC196 step 5 to steps 6 and 7.

Functional unit Minimum HW level Configuration expansion step 6

A2SU AL2S-B Add 2 AL2S-D units

GTPU CCP10 Add 3 CCP18-C/CCP18-A units

ICSU CCP10 Add 2 CCP18-C/CCP18-A units

MXU MX622-D Add 2 MX622-D units

or

Add 2 MX622-D units and upgrade all MX622-C/-B units to MX622-D

NISx NI4S1-B Add up to 8 new NISx units

OMU CCP18-A Upgrade 2 CCP10 units to CCP18-A

OMU WDU HDD HDS-B Upgrade 2 OMU HDS/-A units to 2 HDS-B units

DMCU CDSP-C Reconfigure existing CDSP-Cs to new loca-tions

In RN4.0, upgrade CDSP-C units to CDSP-DH

FDU Remove MDS-A (replaced by OMU's USB con-nection for external USB devices. The USB memory stick can be used only with CCP18-A.)

NIP1 NI16P1A Remove excessive NIP1 units – 1 unit remains

RRMU In RN4.0, remove and reconfigure as ICSU units

RSMU CCP10

OMS MCP18-B Integrated OMS replaces NEMU as of RN3.0

As of RN5.0, the functional unit OMS can be selected between the current integrated OMS or an external standalone OMS network element. For RN5.0 new deliveries, the stand-alone OMS is recommended.

Table 7 Minimum hardware level and configuration expansion for RNC196 step 6


A2SU AL2S-D Upgrade remaining 7 AL2S-B units to AL2S-D

GTPU CCP18-C

CCP18-A

Upgrade remaining 6 CCP10 units to CCP18-C/CCP18-A

ICSU CCP18-C

CCP18-A

Upgrade remaining 19 CCP10 units to CCP18-C/CCP18-A


52 DN0938143Issue 1-4




7.1.4 RNC196 Step 8The following figures show the maximum configuration after RNC196 configuration step 8 is taken into use.

RRMU In RN4.0, removed and reconfigured as ICSU units

RSMU CCP18-C

CCP18-A

Upgrade 2 CCP10 units to CCP18-C/CCP18-A

MXU MX622-D

DMCU CDSP-C In RN4.0, upgrade CDSP-C units to CDSP-DH

OMU CCP18-A

OMU WDU HDD HDS-B

OMS MCP18-B Integrated OMS replaces NEMU as of RN3.0.




DN0938143Issue 1-4

53



Figure 21 RNAC cabinet - RNC196 step 8

CPD80-B 0 CPD80-B 1

Op

tio

na

lE

SA

24

ES

A1

2/

ES

A2

4

NIS

1P

4N

IS1

P5

MX

U0

RS

MU

0

SF

U0

NE

MU

OM

U0

WD

U0

(OM

U)

PD

20

ES

A24

TB

UF

TS

S3

1

FD

U(O

MU

)

PD

20

TB

UF

2

DM

CU

MX

U3

MX

U2

DM

CU

DM

CU

DM

CU

ICS

U

DM

CU

A2

SU

EH

U

PD

20

TB

UF

TB

UF

3

NIP

10

NIP

11

A2

SU

ICS

U

ICS

U

MX

U1

RS

MU

1

SF

U1

OM

U1

WD

U1

(OM

U)

DM

CU

MX

U5

MX

U4

DM

CU

DM

CU

DM

CU

ICS

U

DM

CU

DM

CU

A2S

U

PD

20

TB

UF

TB

UF

4

NIP

12

NIP

13

ICS

U

ICS

U

GT

PU

GT

PU

NIS

x2

NIS

x3

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

HD

D0

(NE

MU

/OM

S)

HD

D1

(NE

MU

/OM

S)

TS

S3

-IC

SU

TS

S3

RR

MU

0R

RM

U1

NIS

1P

6N

IS1

P7

NIS

x0

NIS

x1

TS

S3

-MX

U5

MX

U4

DM

CU

8

DM

CU

7

DM

CU

6

ICS

U5

- - -PD

20

ICS

U3

ICS

U4

NP

S1P

1

-MX

U3

MX

U2

DM

CU

2

DM

CU

1

-ICS

U2

- - -PD

20

ICS

U0

ICS

U1

NP

S1P

0

RS

MU

0

NE

MU

TB

UF

TS

S3

PD

20

TB

UF

TB

UF

TB

UF

MX

U14

OM

U1

TB

UF

TB

UF

TS

S3

ICS

U2

5IC

SU

26

MX

U0

PD

20

RS

MU

1

OM

U0

SF

U0

SF

U1

ICS

U2

2IC

SU

23

-/

NP

GE

(P)

0-

/N

PG

E(P

)1

--

WD

U0

(OM

U)

WD

U1

(OM

U)

WD

U0

(OM

U)

WD

U1

(OM

U)

ICS

U6

ICS

U1

9

ICS

U2

0

ICS

U2

1

NIS

x5

NIS

x6

NIS

x7

NIS

x0

NIS

x1

NIS

1P

6

NIS

1P

5

NIS

1P

7

NIS

x0

NIS

x1

NP

GE

P2

NP

GE

P1

NP

GE

P3

NP

S1P

2N

PS

1P

3-

-- DM

CU

27

DM

CU

19

FD

U(O

MU

)M

XU

15

ICS

U24

EH

U

EH

UE

HU

MX

U1

ES

A12/E

SA

24

0

-O

ption

alE

SA

24

1

NIS

x4

NIS

1P

4N

PG

EP

0-

A:

WD

U1

(OM

U)

A:W

DU

0(O

MU

)

B:

HD

D1

(OM

S)

B:

HD

D0

(OM

S)


54 DN0938143Issue 1-4




Figure 22 RNBC cabinet - RNC196 step 8

7.1.5 Hardware Upgrade to RNC196 Step 8An overview of the configuration for the RNC196 configuration step 8 is shown in the figure and sections below.

CPD80-B 0 CPD80-B 1

DM

CU

MX

U7

MX

U6

DM

CU

DM

CU

DM

CU

ICS

U

DM

CU

DM

CU

A2

SU

PD

20

TB

UF

TB

UF

1

NIP

14

NIP

15

ICS

U

ICS

U

DM

CU

DM

CU

DM

CU

MX

U9

MX

U8

DM

CU

DM

CU

DM

CU

ICS

U

DM

CU

DM

CU

A2

SU

PD

20

TB

UF

TB

UF

2

NIP

16

NIP

17

ICS

U

GT

PU

ICS

U

DM

CU

DM

CU

DM

CU

MX

U11

MX

U10

DM

CU

DM

CU

DM

CU

ICS

U

DM

CU

DM

CU

A2

SU

PD

20

TB

UF

TB

UF

3

NIP

18

NIP

19

ICS

U

GT

PU

ICS

U

DM

CU

DM

CU

DM

CU

MX

U13

MX

U12

DM

CU

DM

CU

DM

CU

ICS

U

DM

CU

DM

CU

A2

SU

PD

20

TB

UF

TB

UF

4

NIP

11

0

NIP

111

ICS

U

GT

PU

ICS

U

DM

CU

DM

CU

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

-MX

U13

MX

U12

DM

CU

38

DM

CU

37

DM

CU

36

ICS

U1

8

- - -PD

20

ICS

U1

6

ICS

U31

ICS

U1

7

-MX

U11

MX

U10

DM

CU

30

DM

CU

29

DM

CU

28

ICS

U1

5

- - -PD

20

ICS

U1

3

ICS

U30

ICS

U1

4

-MX

U9

MX

U8

DM

CU

22

DM

CU

21

-ICS

U1

2

-

-PD

20

ICS

U1

0

ICS

U29

ICS

U11

-MX

U7

MX

U6

DM

CU

14

DM

CU

13

DM

CU

12

ICS

U9

- - -PD

20

ICS

U7

ICS

U27

ICS

U8

TB

UF

TB

UF

TB

UF

TB

UF

TB

UF

TB

UF

TB

UF

TB

UF

-/

NP

GE

(P)

2-

/N

PG

E(P

)3

-/

NP

GE

(P)

4-

/N

PG

E(P

)5

--

--

ICS

U28

-NP

S1P

2- -N

PS

1P

3

--- -

NP

S1P

4/N

PG

EP

(P)

6N

PS

1P

5/N

PG

E(P

)7


DN0938143Issue 1-4

55



Configuration step 8 differs in the requirements for plug-in unit variant level. See the table Minimum hardware level for RNC196 step 8 for more information. The configura-tion expansion step requires cabling and configuration changes to the RNC.

The configuration of the RNC must be at least RNC196 step 7 before the RNC196 con-figuration step 8 expansion.

g In the following figure Configuration step RNC196 step 8 with mandatory hardware changes: in slots which show two functional unit names, the lower one shows the functional unit equipped in that slot in RNC196 step 7 and the upper one shows the functional unit equipped in that same slot after the mandatory hardware changes have been carried out in the expansion to RNC196 configuration step 8.

56 DN0938143Issue 1-4




Figure 23 Configuration step RNC196 step 8 with mandatory hardware changes

Configuration step RNC196 step 8Configuration step 8 can be achieved with the following hardware changes.

There are five possible starting configurations for upgrading RNC196 step 7 to step 8:

1. RNC196 step 72. RNC196 step 7 with IP / Iu-PS not totally IP based3. RNC196 step 7 with IP / Iu-PS totally IP based4. RNC196 step 7 with all IP optional upgrade

CPD80-B 0 CPD80-B 1

RNAC

CPD80-B 0 CPD80-B 1

RNBC

DM

CU

MX

U7

MX

U6

DM

CU

DM

CU

DM

CU

ICS

U

DM

CU

DM

CU

A2S

U

PD

20

TB

UF

TB

UF

1

NIP

14

NIP

15

ICS

U

GT

PU

ICS

U

DM

CU

DM

CU

DM

CU

MX

U9

MX

U8

DM

CU

DM

CU

DM

CU

ICS

U

DM

CU

DM

CU

A2S

U

PD

20

TB

UF

TB

UF

2

NIP

16

NIP

17

ICS

U

GT

PU

ICS

U

DM

CU

DM

CU

DM

CU

MX

U11

MX

U1

0

DM

CU

DM

CU

DM

CU

ICS

U

DM

CU

DM

CU

A2S

U

PD

20

TB

UF

TB

UF

3

NIP

18

NIP

19

ICS

U

GT

PU

ICS

U

DM

CU

DM

CU

DM

CU

MX

U1

3

MX

U1

2

DM

CU

DM

CU

DM

CU

ICS

U

DM

CU

DM

CU

A2S

U

PD

20

TB

UF

TB

UF

4

NIP

110

NIP

111

ICS

U

GT

PU

ICS

U

DM

CU

DM

CU

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

Op

tio

na

lE

SA

24

ES

A12

/E

SA

24

NIS

1P

4N

IS1

P5

MX

U0

RS

MU

0

SF

U0

NE

MU

OM

U0

WD

U0

(OM

U)

PD

20

ES

A2

4

TB

UF

TS

S3

1

FD

U(O

MU

)

PD

20

TB

UF

2

DM

CU

MX

U3

MX

U2

DM

CU

DM

CU

DM

CU

ICS

U

DM

CU

DM

CU

A2S

U

EH

U

PD

20

TB

UF

TB

UF

3

NIP

10

NIP

11

A2S

U

ICS

U

ICS

U

MX

U1

RS

MU

1

SF

U1

OM

U1

WD

U1

(OM

U)

DM

CU

MX

U5

MX

U4

DM

CU

DM

CU

DM

CU

ICS

U

DM

CU

DM

CU

A2S

U

PD

20

TB

UF

TB

UF

4

NIP

12

NIP

13

ICS

U

ICS

U

GT

PU

GT

PU

NIS

x2

NIS

x3

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

38

HD

D0

(NE

MU

/OM

S)

HD

D1

(NE

MU

/OM

S)

TS

S3

-IC

SU

TS

S3

RR

MU

0R

RM

U1

NIS

1P

6N

IS1

P7

NIS

x0

NIS

x1

TS

S3

DM

CU

39

MX

U1

3

MX

U1

2

DM

CU

38

DM

CU

37

DM

CU

36

ICS

U1

8

DM

CU

40

DM

CU

41

A2

SU

6

PD

20

ICS

U1

6

GT

PU

5

ICS

U1

7

DM

CU

9

MX

U5

MX

U4

DM

CU

8

DM

CU

7

DM

CU

6

ICS

U5

DM

CU

10

DM

CU

11

A2S

U2

PD

20

ICS

U3

ICS

U4

GT

PU

1

NIS

1(P

)3

DM

CU

31

MX

U11

MX

U1

0

DM

CU

30

DM

CU

29

DM

CU

28

ICS

U1

5

DM

CU

32

DM

CU

33

A2

SU

5

PD

20

ICS

U1

3

GT

PU

4

ICS

U1

4

DM

CU

3

MX

U3

MX

U2

DM

CU

2

DM

CU

1

DM

CU

0

ICS

U2

DM

CU

4

DM

CU

5

A2

SU

1

PD

20

ICS

U0

ICS

U1

GT

PU

0

NIS

1(P

)2

DM

CU

23

MX

U9

MX

U8

DM

CU

22

DM

CU

21

DM

CU

20

ICS

U1

2

DM

CU

24

A2

SU

4

PD

20

ICS

U1

0

GT

PU

3

ICS

U11

DM

CU

15

MX

U7

MX

U6

DM

CU

14

DM

CU

13

DM

CU

12

ICS

U9

DM

CU

16

DM

CU

17

A2

SU

3

PD

20

ICS

U7

GT

PU

2

ICS

U8

TB

UF

TB

UF

TB

UF

TB

UF

TB

UF

TB

UF

TB

UF

TB

UF

RS

MU

0

NE

MU

TB

UF

TS

S3

Pd

20

TB

UF

TB

UF

TB

UF

MX

U14

OM

U1

TB

UF

TB

UF

TS

S3

NIS

1(P

)0

NIS

1(P

)1

MX

U0

PD

20

RS

MU

1

OM

U0

SF

U0

SF

U1

ICS

U2

2IC

SU

23

-/

NP

GE

(P)

2-

/N

PG

E(P

)3

-/

NP

GE

(P)

4-

/N

PG

E(P

)5

-/

NP

GE

(P)

0-

/N

PG

E(P

)1

DM

CU

42

DM

CU

34

DM

CU

43

DM

CU

35

WD

U0

(OM

U)

WD

U1

(OM

U)

WD

U0

(OM

U)

WD

U1

(OM

U)

ICS

U6

ICS

U1

9

ICS

U2

0

ICS

U2

1

NIS

x5

NIS

x6

NIS

x7

NIS

x0

NIS

x1

NIS

1P

6

NIS

1P

5

NIS

1P

7

NIS

x0

NIS

x1

NP

GE

P2

NP

GE

P1

NP

GE

P3

NP

S1P

2N

PS

1P

3A

2S

U7

A2

SU

8

DM

CU

26

DM

CU

27

DM

CU

19

FD

U(O

MU

)M

XU

15

GT

PU

6

EH

U

EH

UE

HU

MX

U1

ES

A12/E

SA

24

0

A2

SU

0O

ptio

nalE

SA

24

1

NIS

x4

NIS

1P

4N

PG

EP

0D

MC

U18

-D

MC

U25

GT

PU

7

--- -

NIS

1(P

)6

NIS

1(P

)4

NIS

1P

5

NIS

1P

7

A:W

DU

1(O

MU

)A

:W

DU

0(O

MU

)

B:H

DD

1(O

MS

)B

:H

DD

0(O

MS

)

--- -

NIS

1(P

)10

NIS

1(P

)8

/

NP

GE

P(P

)6

NIS

1P

9/

NP

GE

(P)

7

NIS

1P

11

ICS

U

ICS

U

NP

S1

P

ICS

U

NP

S1

P

NP

S1

P

ICS

UIC

SU

NP

S1

P

ICS

U

ICS

U

SFU upgrade (SF10E)

IP upgrade (NP2GE-B)




HSPA upgrade (CDSP-DH)

DN0938697

ICS

U

DM

CU

34

NP

S1

P/

NP

GE

P(P

)N

PS

1P

/

NP

GE

(P)

ICSU upgrade (CCP18-C)

NPS1(P) upgrade (NP8S1(P))

DN0938143Issue 1-4

57



5. RNC196 step 7 with HSPA optional upgrade6. RNC196 step 7 with full CDSP-DH upgrade (all CDSP-Cs are replaced with CDSP-

DH)

7.2 Equipment in the SubracksThe table below shows the configurations of the subracks for RNC196 step 5, RNC196 step 7 and RNC196 step 8. The RNC196 step 7 covers both RNC196 step 6 and RNC196 step 7 maximum configurations.


SFU SF10E Remove 2 SF10 units

and

Replace with 2 SF10E units

Note: Only if starting from 1), 5) or 6) above

A2SU Remove all remaining AL2S-D units

GTPU Remove all CCP18-A units

ICSU CCP18-C Add 8 CCP18-C units, unless starting from 3) or 4) above

NPS1(P) NP8S1-B Remove all remaining NI16P1A / NI4S1-B units

and

Add up to 6 NP8S1-B plug-in units a)

DMCU CDSP-DH Remove all CDSP-C units

and

Replace with up to 18 CDSP-DH units

Note: exactly 18 CDSP-DH must be equipped

OMS MCP18-B Integrated OMS replaces NEMU as of RN3.0


a) The number depends on the desired configuration.


Unit type Conf. RNAC RNBC Min Max


A2SU RNC196 step 5 1 — 1 1 1 3 7

RNC196 step 7 2 1 1 1 1 5 9

RNC196 step 8 — — — — — — —

Table 10 Number of units in RNC196 subracks

58 DN0938143Issue 1-4




DMCU RNC196 step 5 — — 6 6 8 12 44

RNC196 step 7 2 2 7 7 5–7 a) 18 44

RNC196 step 8 1 1 2 3 11 18 18

EHU RNC196 step 5 1 — — — — 1 1

RNC196 step 7 — 1 — — — 1 1

RNC196 step 8 — 1 — — — 1 1

GTPU RNC196 step 5 — — 1 1 1 2 6

RNC196 step 7 — 1 1 1 1–2 b) 4 8

RNC196 step 8 — — — — — — —

ICSU h) RNC196 step 5 1 1 3 4 3 9 21

RNC196 step 7 3 3 3 3 3 12 24

RNC196 step 8 3 4 4 4 17 32 32

MXU RNC196 step 5 1 1 2 2 2 6 14

RNC196 step 7 2 2 2 2 2 8 16

RNC196 step 8 2 2 2 2 8 16 16

OMS f) RNC196 step 5 1 — — — — 1 1

RNC196 step 7 1 — — — — 1 1

RNC196 step 8 0–1 — — — — — 1

OMS HDD e) RNC196 step 5 1 1 — — — 2 2

RNC196 step 7 1 1 — — — 2 2

RNC196 step 8 0–1 0–1 — — — — 2

ESA24 c) 1 0–1 — — — 1 2

ESA12 c) 1 — — — — 1 1

NIP1 RNC196 step 5 1 — 0–2 0–2 0–2 — 12

RNC196 step 7 1 — — — — 1 1

RNC196 step 8 — — — — — — —

NIS1 RNC196 step 5 1–3 0–1 0–1 0–1 — 2 6

RNC196 step 7 — — 1–2 1–2 0–2 d) 2 6

RNC196 step 8 — — — — — — —

NIS1P RNC196 step 5 1–3 1–3 0–1 0–1 — 2 8

RNC196 step 7 — — 1–2 1–2 0–2 2 12

RNC196 step 8 — — — — — — —

NPGE(P) RNC196 step 5 0–1 0–1 0–1 0–1 0–1 — 8

RNC196 step 7 — — — — — — —

RNC196 step 8 — — 0–1 0–1 0–6 — 8



Table 10 Number of units in RNC196 subracks (Cont.)

DN0938143Issue 1-4

59



NPS1(P) RNC196 step 5 — — — — — — —

RNC196 step 7 — — — — — — —

RNC196 step 8 — — 0–1 0–1 0-4 0 6

OMU 1 1 — — — 2 2

OMU WDU 1 1 — — — 2 2

OMU FDU h) RNC196 step 5 — 1 — — — 1 1

PD20 1 1 1 1 1 4 8

RRMU f) 1 1 — — — 2 2

RSMU 1 1 — — — 2 2

SFU 1 1 — — — 2 2

TBUF 1 1 2 2 2 6 14

TSS3 1 1 — — — 2 2

a) In RNBC Sr2, there are 5 DMCUs.

b) In RNBC Sr2, there are 2 GTPUs.

c) RNC196 is configured with either ESA24 or ESA12.

d) 0-2 NIS1 units in RNBC Sr1 or Sr3: maximum number of NIS1 units is 6.

e) Integrated OMS replaces NEMU in RN3.0.

As of RN5.0, the functional unit OMS can be selected between the current integrated OMS or an external stand-alone OMS network element. For RN5.0 new deliveries, the standalone OMS is recommended.

f) ICSU replaces RRMU in both subracks after RN4.0 software release upgrade.

g) In RNBC Sr2, there are 6 DMCUs.

h) RNC196 step 5 only: FDU is removed when adding configuration step RNC196 step 6 and RNC196 step 7.



Table 10 Number of units in RNC196 subracks (Cont.)


Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8

A2SU 3 4 5 6 7 9 9 —

DMCU 12 20 28 36 44 44 44 18

EHU 1 for all configurations



GTPU 2 3 4 5 6 8 8 —

ICSU a) 7 10 13 16 19 22 22 32

MXU 6 8 10 12 14 16 16 16

Table 11 Maximum number of units in RNC196 for each configuration step

60 DN0938143Issue 1-4





7.3 Upgrades and Expansions for RNC196 in RN5.0

7.3.1 Mandatory Upgrades for RNC196Minimum hardware requirement for all configurations in RN5.0: the disk size for Inte-grated OMS must be at least 147 GB.

Before RN5.0 software upgrade, all AL2S-B plug-in units in A2SU functional units must be replaced with the plug-in unit variant AL2S-D.

7.3.2 Optional Upgrades for RNC196As of RN5.0, the functional unit OMS can be selected between the current integrated OMS or an external standalone OMS network element. For RN5.0 new deliveries, the standalone OMS is recommended.

OMS b)

* OMS replaces NEMU as of RN3.0


OMS HDD b) 2 for all configurations

NIP1 4 6 8 10 12 1 1 —

NIS1 6 for all configurations —

NIS1P 8 for all configurations 12 12 —

NPGE(P) 4 5 6 7 8 — — 8

NPS1(P) — — — — — — — 6

OMU 2 for all configurations

OMU WDU 2 for all configurations

OMU FDU 1 for all configurations — — —

PD20 4 5 6 7 8 8 8 8

RRMU a) 2 for all configurations —

RSMU 2 for all configurations

SFU 2 for all configurations

TBUF 6 8 10 12 14 14 14 14

TSS3 2 for all configurations

a) ICSU replaces RRMU in both subracks after RN4.0 software release upgrade.

b) As of RN5.0, the functional unit OMS can be selected between the current integrated OMS or an external standalone OMS network element. For RN5.0 new deliveries, the standalone OMS is recommended..


Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8

Table 11 Maximum number of units in RNC196 for each configuration step (Cont.)

DN0938143Issue 1-4

61



RNC196 step 7 to step 8 upgrade is supported. For more informaiton, see Hardware Expansion for RNC196.

Full CDSP-DH upgrade (replacing all CDSP-C with CDSP-DH) is supported. For more information, see Replacing CDSP-C with CDSP-DH and Enabling HSDPA Capacity Enhancement in CDSP-DH.

The upgrades supported in RN4.0 are also supported in RN5.0.

7.4 Upgrades and Expansions for RNC196 in RN4.0

7.4.1 Mandatory Upgrades for RNC196In RN4.0 software release, the RRMU functional unit is removed from configuration and is configured as ICSU unit. RRMU functions are divided between the RSMU, ICSU, and OMU functional units. The location service feature moves to RSMU. For more informai-ton, see Hardware Expansion for RNC196.

7.4.2 Optional Upgrades for RNC196 • RRMU to ICSU

When the RRMU functional unit is removed, its CCP10/CCP18-A/CCP18-C plug-in units are released. They can be configured as ICSU, which means that ICSU capacity increases by two plug-in units. For more informaiton, see Hardware Expan-sion for RNC196.

• SFU upgradeIn SFU upgrade, the SF10 plug-in units are replaced by the SF10E plug-in units in the RNAC cabinet. The SFU upgrade is prerequisite for IP upgrade.For more information, see SFU and IP Upgrade.

• IP upgradeIP upgrade deploys IP over Ethernet (IPoE) transport for the Iu-CS, Iu-PS and Iur interfaces of an RNC. This is achieved by equipping new NP2GE-B plug-in units into an RNC cabinet and recreating existing ATM interfaces as Ethernet interfaces. The NP2GE-B plug-in units can be equipped in a cabinet into slots specified in upgrade documentation. The SFU upgrade must be completed before starting the IP upgrade.For more information, see SFU and IP Upgrade.

• Replacing CDSP-C with CDSP-DH (RAN1266, RAN1258)CDSP-C plug-in units for DMCU can be replaced with CDSP-DH plug-in units (RAN1266) in existing installations in the following cases: • to expand the existing DMCU configuration with new units • to replace a broken unit • to enable DMCU for the feature RAN1258: HSDPA 14 Mbps per User (CDSP-

DH is mandatory equipment for RAN1258)Mixed CDSP-C and CDSP-DH configurations are allowed. However, only specific CDSP-DH units in the network element can be enabled for the RAN1258 feature.For more information, see Replacing CDSP-C with CDSP-DH and Enabling HSDPA Capacity Enhancement in CDSP-DH.

62 DN0938143Issue 1-4


Id:0900d8058070322fConfidential

Functional Unit Descriptions

8 Functional Unit Descriptions

8.1 Functional Unit CategoriesThe functional units of the RNC fall into four general categories according to their main functions:

• Management, control computer and data processing units • Switching and multiplexing units • Network element interface units • Units in the timing, power distribution, and hardware management subsystems

The units in the first three categories make up the hardware system blocks which are responsible for the main functions of the network element, such as switching, signalling, and database handling. The units in the last category are mainly blocks in the different subsystems, which are needed for the operation and maintenance of the network element, such as clock signal distribution, power distribution, and Hardware Manage-ment System. All these subsystems are controlled up to a degree by one of the computer units of the network element, the Operation and Maintenance Unit (OMU).

NotationsThe following notations are used throughout this chapter:

• The index numbers of the plug-in units run from left to right and top to bottom. • Even though the CCP18-A and CCP10 plug-in units are all equipped with onboard

LAN/Ethernet and SCSI interfaces, these are included in the functional unit interface lists only when the LAN or SCSI facility is actually used (in OMU unit only).

8.2 Management, Control Computer and Data Processing UnitsThe management and control computer units are on the highest level in the computing hierarchy of the IPA2800 network elements. Their tasks are roughly the following:

• Operation and maintenance, including control of the Hardware Management System (or alarm system) and activation of appropriate recovery and diagnostics procedures when a fault occurs

• Switch fabric control and ATM circuit hunting • Control of some of the signal processing units • Maintenance of the radio network configuration and recovery • Monitoring of the MS connections • Handling of signalling functions and management of the associated protocols • Interfacing with both local users and the higher-level network management system

The management and control computer unit category comprises the following functional units:

8.2.1 DMCU, Data and Macro Diversity Combining UnitPurpose: Although from the technical point of view DMCU is a signal processing

unit, it performs some control plane functions besides its signal pro-cessing tasks. Its tasks are the following:

DN0938143Issue 1-4

63

WCDMA RNC Engineering Description Functional Unit Descriptions


• WCDMA L1 functions, including macro diversity combining and outer loop power control

• RLC-U and RLC-C protocol processing • MAC-C and MAC-D protocol processing • PDCP protocol processing • GTP termination • encryption • HSDPA with CDSP-DH

All DSPs and RISC processors of the unit are automatically allocated within the RNC according to the capacity need.

Redundancy: SN+

Type: Signal processing unit with no sub-units

Plug-in unit: CDSP-DH / CDSP-C / CDSP-B

Configurable Dynamic Signal Processing Platform

Interfaces: ATM interface to MXU

Figure 24 DMCU's interfaces - CDSP-DHDN7088176

LED

SLAVE 3

SLAVE 2

SLAVE 1

MASTER

RS-232 CONNECTORS:

SLAVE 1

MASTER

LAN / ETHERNET:

SLAVE 2

SLAVE 3

BACKPLANE:

-TIMING & SYNC- HMS- POWER SUPPLY- MXU

64 DN0938143Issue 1-4




Figure 25 DMCU's interfaces - CDSP

8.2.2 GTPU, Gateway Tunneling Protocol UnitPurpose: GTPU facilitates RNC connections towards the SGSN by performing

those RNC-specific Iu user plane functions which are related to GTP protocols. These include:

• Routing based on GTP tunnel ID • UDP/IP protocol termination

Redundancy: SN+

Type: Computer unit with no sub-units

Plug-in unit: CCP18-C / CCP18-A / CCP10

Control Computer, Pentium M (CCP18-C / CCP18-A)

Control Computer, Pentium III (CCP10)


CDSP DN00256144

INTERFACES:

BACKPLANE:

- TIMING & SYNC- HMS- POWER SUPPLY- MXU

SERVICE TERMINAL

DN0938143Issue 1-4

65



Figure 26 GTPU's interfaces - CCP18-C

BACKPLANE:

- HMS- LAN / ETHERNET- POWER FEED- JTAG/ISP

INTERFACES:

DN70391828

RESET SWITCH

SERVICE TERMINAL

66 DN0938143Issue 1-4




Figure 27 GTPU's interfaces - CCP18-A

BACKPLANE:

- HMS- SCSI (TO STORAGEDEVICES INSUBRACKS)

- LAN / ETHERNET- POWER FEED- JTAG/ISP

INTERFACES:

USB

DN0621415

RESET SWITCH

SERVICE TERMINAL

DN0938143Issue 1-4

67



Figure 28 GTPU's interfaces - CCP10

8.2.3 ICSU, Interface Control and Signalling UnitPurpose: ICSU handles signalling functions and the associated traffic control

functions, including the following tasks:

• Admission control • Radio resource management • Handover control • Packet scheduling • Signalling protocols to Iu, Iub, and Iur interfaces, including NBAP,

RNSAP, and RANAP • Monitoring and recovery of the signalling links

Redundancy: N+1

Type: Computer unit with no sub-units


Control Computer, Pentium M (CCP18-C / CCP18-A)



CCP10 DN00249775

INTERFACES:

BACKPLANE:

- TIMING & SYNC- HMS- POWER SUPPLY- MXU- SCSI (NOT USED)- LAN (NOT USED)

SERVICE TERMINAL

68 DN0938143Issue 1-4




Figure 29 ICSU's interfaces - CCP18-C

BACKPLANE:


INTERFACES:

DN70391828

RESET SWITCH

SERVICE TERMINAL

DN0938143Issue 1-4

69



Figure 30 ICSU's interfaces - CCP18-A

BACKPLANE:



INTERFACES:

USB

DN0621415

RESET SWITCH

SERVICE TERMINAL

70 DN0938143Issue 1-4




Figure 31 ICSU's interfaces - CCP10

8.2.4 Integrated OMS, Operation and Maintenance Server and its sub-unitsIntegrated OMS replaces NEMU as of RN3.0.

As of RN5.0, the functional unit OMS can be selected between the current integrated OMS or an external standalone OMS network element. For RN5.0 new deliveries, the standalone OMS is recommended.

Purpose: Integrated OMS provides the following facilities:

• Local user interface • Interface towards the higher level network management system • O&M functions which are not handled by other computer units of the

RNC • Post-processing support for measurement and statistics • Peripheral device control

Integrated OMS is equipped with storage devices for storing measure-ment and statistical data, and an Ethernet switch with 12 or 24 physical LAN interfaces for connections to the upper-level network management system and the site LAN. Both facilities are implemented as separate plug-in units and described in separate sections which follow this one.

CCP10 DN00249775

INTERFACES:

BACKPLANE:


SERVICE TERMINAL

DN0938143Issue 1-4

71



Redundancy: None

Type: Computer unit, with dedicated storage devices and the Ethernet Switch unit (ESA12/ESA24) as sub-units.

Plug-in unit: MCP18-B

Management Computer, Pentium M 745 (MCP18-B)

MCP18-B Interfaces: Small Computer Systems Interface (SCSI)

LAN/Ethernet to NMS, OMU and Site LAN via ESA24/ESA12

LAN/Ethernet to OMU via ESA24/ESA12

USB *

VDU

*) The USB ports can be used to connect a keyboard, a mouse or a bootable device to the MCP18-B. USB-PS/2 adapters are not sup-ported.

Figure 32 Integrated OMS interfaces (MCP18-B)

Integrated OMS storage devicesPurpose: Integrated OMS is equipped with dedicated hard disks, which serve as

a storage for the measurement and statistical data it collects.

Redundancy: 2N (hard disk drive)

Type: Sub-unit to integrated OMS

BACKPLANE:



INTERFACES:

SVGA

USB

DN05226345

RESET SWITCH

72 DN0938143Issue 1-4




Plug-in unit: HDS-B

Hard Disk Drive with SCSI Interface

Interfaces: Small Computer System Interface (SCSI)

Figure 33 Integrated OMS storage device interfaces

Configuration and redundancy principles of integrated OMS storage devicesIntegrated OMS has a duplicated hard disk unit for storing all crucial measurement and statistical data. The disks are connected to integrated OMS by means of two SCSI buses, the connection principles of which are shown in the figure below.

DN00256429

LED

BACKPLANE:

- HMS- POWER

SUPPLY

- SCSI

INTERFACES:

DN0938143Issue 1-4

73



Figure 34 SCSI connection principle for integrated OMS storage devices (MCP18-B)

8.2.5 ESA24, Ethernet SwitchRNC can have either ESA24 or ESA12 LAN/Ethernet switch.

Purpose: ESA24 is an Ethernet switch, which provides physical LAN/Ethernet interfaces for connections between OMU, integrated OMS and the other units of the network element. The ESA24 upgrade increases LAN switching capacity. Redundant ESA24 is needed for AGPS feature.

Redundancy: None/2N


Plug-in unit: ESA24

Ethernet Switch

Capacity/ Performance 24 physical 10/100 Base-T Ethernet interfaces

Interfaces: LAN/Ethernet to OMU, integrated OMS, and site LAN

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

RNC SUBRACK 1

RNC SUBRACK 2

RNAC

WD

U1

(OM

S)

DN0938779

BUS END POINT

WD

U0

(OM

S)OMS

SCSI 1

SCSI 0

74 DN0938143Issue 1-4




Figure 35 ESA24's interfaces

8.2.6 ESA12, Ethernet SwitchRNC can have either ESA24 or ESA12 LAN/Ethernet switch.

Purpose: ESA12 is an Ethernet switch which provides physical LAN/Ethernet interfaces for connections between OMU, integrated OMS and the other units of the network element.

Redundancy: None


Plug-in unit: ESA12

Ethernet Switch

Capacity/ Performance 12 physical 10/100 Base-T Ethernet interfaces

Interfaces: LAN/Ethernet to OMU, integrated OMS, and site LAN

ESA24 DN03451956

INTERFACES:

LAN

BACKPLANE:

- HMS (NOT USED)- POWER SUPPLY- LAN

SERVICE TERMINAL

- TIMING & SYNC(NOT USED)

DN0938143Issue 1-4

75



Figure 36 ESA12's interfaces

8.2.7 OMU, Operation and Maintenance Unit and Its SubunitsPurpose: OMU handles all RNC's crucial upper-level system maintenance func-

tions, such as hardware configuration management, Hardware Man-agement System (HMS) supervision, and the associated centralised recovery functions. It also serves as an interface between integrated OMS and the other units of the network element.

In the event of a fault, OMU automatically activates appropriate recovery and diagnostics procedures within RNC.

In addition, OMU is responsible for the maintenance of the radio network configuration. It monitors the status of the network, separates faulty units from the system if necessary, automatically initiates the associated recovery procedures, and houses the databases that contain information on the radio network configuration.

OMU has dedicated storage devices, which house the entire system software and the event buffer for intermediate storing of alarms, along with the radio network configuration files.

Redundancy: 2N

Type: Computer unit with a dedicated storage device unit as a sub-unit.

ESA12 DN02179274

INTERFACES:

12 x LAN / ETHERNET

BACKPLANE:

- HMS (NOT USED)- POWER SUPPLY

- TIMING & SYNC(NOT USED)

76 DN0938143Issue 1-4




Plug-in unit: CCP18-A / CCP10

Control Computer, Pentium M (CCP18-A)


Interfaces: ATM virtual channels to MXU

LAN/Ethernet via ESA24/ESA12 to integrated OMS

Duplicated Small Computer Systems Interface (SCSI)

Service Terminal interface

Multiplexer Interface

Duplicated Hardware Management System (HMS) interface

Figure 37 OMU's interfaces - CCP18-A

BACKPLANE:



INTERFACES:

USB

DN0621415

RESET SWITCH

SERVICE TERMINAL

DN0938143Issue 1-4

77



Figure 38 OMU's interfaces - CCP10

OMU's storage devicesPurpose: OMU has two dedicated hard disk units, which serve as a redundant

storage for the entire system software, the event buffer for intermediate storing of alarms, and the radio network configuration files.

Backup copies are made onto a USB memory stick that is connected to the CCP18-A front plate. Only memory sticks can be used.

Redundancy: 2N (HDS-B)

none (MDS-A/B)

Type: Sub-unit to OMU

Plug-in unit: HDS-A/-B: Hard Disk Drive with SCSI Interface

MDS-A/-B : Magneto Optical Drive with SCSI Interface

External devices: USB memory stick, one for each OMU (for CCP18-A only)

Interfaces: Small Computer System Interface (SCSI)

Universal Serial BUS (USB, CCP18-A)

DN00249799CCP10

INTERFACES:

BACKPLANE:

- TIMING & SYNC- HMS- POWER SUPPLY- MXU- SCSI- LAN

SERVICE TERMINAL

78 DN0938143Issue 1-4




Figure 39 OMU's storage devices' interfaces

Configuration and redundancy principle of OMU's storage devicesThe two mutually redundant WDUs are connected simultaneously to both OMUs by means of separate SCSI buses. This ensures that a spare unit is immediately available for either one of the mutually redundant OMUs, eliminating the need for OMU switchover in case of a memory unit failure.

The USB stick is an optional external device that is not automatically delivered. Only the USB memory stick that is connected to the active OMU can be used. For OMU switcho-ver, two USB memory sticks are needed: one for each OMU.

The connection principle for the memory units is illustrated in the figures below.

DN02179305

HDS /-AMDS /-A

INTERFACES:

BACKPLANE:

- HMS- POWER SUPPLY- SCSI

DN0938143Issue 1-4

79



Figure 40 SCSI connection principle for OMU storage devices - CCP18-A and HDS-B

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

RNAC SUBRACK 1

RNAC SUBRACK 2

RNAC

DN0640747 BUS END POINT

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

SCSI 1

SCSI 0

WD

U0

(OM

U)

OM

U0

WD

U1

(OM

U)

OM

U1

80 DN0938143Issue 1-4




Figure 41 SCSI connection principle for OMU storage devices - CCP10, HDS-A and MDS-A

8.2.8 RRMU, Radio Resource Management UnitPurpose: RRMU performs RNC-wide paging and IPA2800 messaging.

Redundancy: 2N

Type: Computer unit

Plug-in unit: CCP18-C / CCP18-A / CCP18-A / CCP10

Control Computer, Pentium M (CCP18-C/CCP18-A)



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

RNC SUBRACK 1

RNC SUBRACK 2

RNAC

DN99573042 BUS END POINT

SCSI 0 SCSI 1

WD

U0

(OM

U)

FD

U(O

MU

)

OM

U1

WD

U1

(OM

U)

OM

U0

DN0938143Issue 1-4

81



Figure 42 RRMU's interfaces - CCP18-C

BACKPLANE:


INTERFACES:

DN70391828

RESET SWITCH

SERVICE TERMINAL

82 DN0938143Issue 1-4




Figure 43 RRMU's interfaces - CCP18-A

BACKPLANE:



INTERFACES:

USB

DN0621415

RESET SWITCH

SERVICE TERMINAL

DN0938143Issue 1-4

83



Figure 44 RRMU's interfaces - CCP10

8.2.9 RSMU, Resource and Switch Management UnitPurpose: RSMU controls the switch fabrics in RNC and establishes connections

for calls according to requests from the signalling computer units (ICSUs). It also handles DSP resource management.

ATM switching management functions comprise:

• Establishment of both internal and external connections via SFU, including ATM circuit hunting

• Management and control of SFU, A2SU and MXU • Transmission resource management.

DSP resource management tasks comprise:

• Supervision and management of the DMCU units, including the necessary software upload procedures

• Allocation of the DSPs and associated computer resources to differ-ent tasks, such as microdiversity combining and data traffic

• Management of the ATM connections within DMCU

Redundancy: 2N

Type: Computer unit

CCP10 DN00249775

INTERFACES:

BACKPLANE:


SERVICE TERMINAL

84 DN0938143Issue 1-4





Control Computer, Pentium M (CCP18-C/CCP18-A)



Figure 45 RSMU's interfaces - CCP18-C

BACKPLANE:


INTERFACES:

DN70391828

RESET SWITCH

SERVICE TERMINAL

DN0938143Issue 1-4

85



Figure 46 RSMU's interfaces - CCP18-A

BACKPLANE:



INTERFACES:

USB

DN0621415

RESET SWITCH

SERVICE TERMINAL

86 DN0938143Issue 1-4




Figure 47 RSMU's interfaces - CCP10

8.3 Switching and Multiplexing UnitsSwitching and multiplexing in RNC is based on the Asynchronous Transfer Mode (ATM) technology with full support to the various traffic types used in the network. The units in this category are the following:

• ATM Switching Fabric Units (SFUs) which are used for switching the calls processed by the network element

• Multiplexer Units (MXUs), for connecting the low-bit-rate network interface units, along with the computer units and signal processing units (which typically have small to moderate bandwidth requirements) to the ATM switch fabric

• AAL2 Switching Units (A2SUs), which ensure efficient transport of information with limited transfer delay for low-to-moderate bit-rate units connected to the main switch fabric.

In addition, the units in this block provide the ATM interface, which serves as the main message bus between the units in the network element. Upper-level control functions for all three units are performed by the RSMU functional unit.

CCP10 DN00249775

INTERFACES:

BACKPLANE:


SERVICE TERMINAL

DN0938143Issue 1-4

87



MXU's connections within the RNCThe figure below shows how the ATM connections in RNC are allocated to its various units in RNC450. The SFU switching fabric has 16 ports for connections to the other units in the network element, with an aggregate capacity of 10Gbit/s (equivalent to 64STM-1 lines); each port, in turn, has a capacity of 622 Mbit/s. The connections through the ports are allocated in the following manner:

RNC2600, RNC450, RNC196 step 6, RNC196 step 7 and RNC196 step 8

• 2–6 (12 redundant) ports are used for the external STM-1 connections provided by the NIS1, NPGE and NPS1 units.

• Eight ports are used for connections to the low-bit-rate network interface units and the computer units via the mutually redundant MXU pairs. One MXU pair requires one port.

The equipment of RNC is organised as groups of units around its MXU pairs, with each group connecting to a MXU pair of its own. When adding the RNC196 configuration step 6, the MXU 1 is moved to RNAC subrack 1 and a new MXU pair, MXU 14 and MXU 15 are added to RNAC subrack 2. After the configuration step RNC196 step 6 upgrade, both MXU pairs in RNAC subracks 1–2 serve the subracks they are located in.

The figure below shows the MXU pairs and the devices connecting to each MXU pair in RNC450. The number of units included in each subrack is given after each unit.

88 DN0938143Issue 1-4




Figure 48 ATM connections to SFU - RNC450

8.3.1 A2SU, AAL2 Switching UnitPurpose: A2SU unit handles the ATM adaptation layer type 2, AAL2, switching.

A2SU is an AAL type 2 CPS minipacket switching unit, which is used in association with the Multiplexing Unit (MXU) for facilitating connections between the main Switch Fabric (SFU) and the low-to-moderate bit-rate units (computer units, signal processing units and low-bit-rate network interface units).

The function of the A2SU unit is to switch the AAL type 2 CPS minipack-ets. The AAL 2 minipackets coming into and going out of A2SU are embedded in ATM cells. Before the switching the AAL 2 minipackets are removed from the ATM cells, and after the switching they are packed again into ATM cells.

Redundancy: SN+

OMU

DN01128575

2-12 pcs

SFU

DMCU

0-1 pcs ***

3 pcs

5-7 pcs*

1 pcs

1-2 pcs **

2 pcs A2SU

1 pcs RSMU

1 pcs OMU

1 pcs RRMUMXU

1

DMCU

A2SU

GTPU

ICSU

NIP 1

MXU

3-8

ICSU2 pcs

DMCU2 pcs

NIS 1

5 DMCUs in RNBC Sr2*

2 GTPUs in RNBC Sr2**

*** 1 NIP1 in RNAC Sr3

1 pcs A2SU

1 pcs RSMU

1 pcs

1 pcs RRMUMXU

2

ICSU2 pcs

DMCU2 pcs

DN0938143Issue 1-4

89



Type: Signal processing unit

Plug-in unit: AL2S-D / AL2S-B

AAL type 2 switching unit


Figure 49 A2SU's interfaces - AL2S-DDN7088176

LED

SLAVE 3

SLAVE 2

SLAVE 1

MASTER

RS-232 CONNECTORS:

SLAVE 1

MASTER

LAN / ETHERNET:

SLAVE 2

SLAVE 3

BACKPLANE:

-TIMING & SYNC- HMS- POWER SUPPLY- MXU

90 DN0938143Issue 1-4




Figure 50 A2SU's interfaces - AL2S-B

8.3.2 MXU, Multiplexer UnitPurpose: The MXU units enable connection of the low-to-medium bit-rate signal

processing units and computer units, as well as low-bit-rate network interface units, to the ATM switch fabric. The task of MXU is to perform the multiplexing and demultiplexing of ATM cells and perform ATM layer management and processing functions such as header translation, UPC/NPC parameter control, OAM functions, traffic management, per-formance monitoring and collection of performance data.

Redundancy: 2N

Type: Multiplexer unit

Plug-in unit: MX1G6-A / MX1G6 / MX622-D / MX622-C / MX622-B

ATM Multiplexer plug-in unit 622 Mbit/s

Capacity: 622 Mbit/s

Interfaces: ATM interfaces to:

• SFU switching block • SFU unit computer • Control computer units (including DMCU)

AL2S-B DN00249833

INTERFACES:

BACK PLANE:

- TIMING & SYNC- HMS- POWER SUPPLY- MXU

SERVICE TERMINAL

DN0938143Issue 1-4

91



• Network interfaces • A2SU • Connection between the passive MXU via the active one to OMU

(for OAM purposes)

Figure 51 MXU's interfaces - MX1G6 and MX1G6-AMX1G6/ MX1G6-ADN70170272

SERVICE TERMINAL

INTERFACES:

BACKPLANE:

- TIMING & SYNC

- HMS

- POWER FEED

- SFU

- TRIBUTARY UNITS

- REDUNDANCY INTERFACE

- BOUNDARY SCAN INTERFACE

LED

92 DN0938143Issue 1-4




Figure 52 MXU's interfaces - MX622

8.3.3 SFU, Switching Fabric UnitPurpose: SFU serves as the main switch fabric of the network element. It

operates according to a non-blocking connection principle, which means that a connection can be established any time provided that the needed input and output capacity is available. SFU supports both point-to-point and point-to-multipoint connection topologies, as well as differ-entiated handling of various ATM service categories.

Redundancy: 2N

Type: Switching fabric

Plug-in unit: SF20H, SF10E, SF10

ATM Switch Fabric Plug-in Unit 10 Gbit/s

Capacity: 10 Gbit/s

Interfaces: ATM interfaces to:

• NI4S1 network interfaces • Low-bit-rate network interfaces and control computers (via MXUs) • OMU from the unit computer of SFU (for OAM purposes and

software uploads, via MXUs)

MX622 DN02179344

SERVICE TERMINAL

INTERFACES:

BACKPLANE:

- TIMING & SYNC

- HMS

- POWER FEED

- SFU

- TRIBUTARY UNITS

- SFU UNIT COMPUTER

- OMU FROM PASSIVE MUXVIA THE ACTIVE ONE

LED

DN0938143Issue 1-4

93



Figure 53 SFU's interfaces - SF20H

ETH

SER

DN70166955 SF20H

LED

94 DN0938143Issue 1-4




Figure 54 SFU's interfaces - SF10E

INTERFACES:

LAN (TESTING ONLY)

SERVICETERMINAL

SFP (SFPIF2G5)

BACKPLANE:

- TIMING & SYNC

- HMS

- POWER SUPPLY

- SWITCH PORT TOTRIBUTARY UNITS

- OMU (FROM UNIT

COMPUTER VIAMXU)

DN70498095

DN0938143Issue 1-4

95



Figure 55 SFU's interfaces - SF10

8.4 Network Interface UnitsThese units serve as the trunk network interfaces of the network element and execute physical layer and ATM layer functions, such as policing, statistics, Operation Adminis-tration Maintenance (OAM), buffer management, and scheduling. The category com-prises the following units:

• NIP1, Network Interface Unit PDH • NIS1 / NIS1P, Network Interface Unit STM-1 • NPS1 / NPS1P • NPGE / NPGEP

One network interface unit contains more than one physical interface. Each interface can be configured to be used as an Iu, Iub, or Iur interface within the total connection capacity of the network element.

g To ensure at least partial backup for the power supply to the network interfaces, SDH/TDM trunk connections from RNC to any direction should be divided between at least two, preferably even more units, which are located in different subracks.

DN02179356

INTERFACES:

BACKPLANE:

- TIMING & SYNC

- HMS

- POWER SUPPLY

- SWITCH PORT TOTRIBUTARY UNITS

- OMU (FROM UNITCOMPUTER VIAMXU)

SF10

SERVICE TERMINAL

LAN

96 DN0938143Issue 1-4




8.4.1 NIP1NIP1 is optional in RNC450, RNC196 step 6 and RNC196 step 7.

Purpose: This ATM network interface unit contains PDH E1/T1/JT1 interfaces with Inverse Multiplexing for ATM (IMA) function, which allows for flexible grouping of physical links to logical IMA groups. Normally, the PDH lines are used for connections between RNC and the BTSs.

Redundancy: None

Type: Interface unit

Plug-in unit: NI16P1A

ATM Network Interface 16 × PDH E1/T1/JT1

Capacity/ performance: Sixteen physical PDH electrical interfaces, each with a band-width of:

• 2048 kbit/s (E1) or • 1544 kbit/s (T1/JT1)


Clock reference output to TSS3/-A

Figure 56 NIP1's interfacesNI16P1A

INTERFACES:

BACKPLANE:

- TIMING & SYNC- HMS- POWER SUPPLY- MXU- E1 / T1 / JT1- CLOCK

REFERENCEOUTPUT TO TSS3

SERVICE TERMINAL

LAN(NOT USED)

DN02179492

DN0938143Issue 1-4

97



8.4.2 NIS1 / NIS1PPurpose: NIS1 provides SDH STM-1 interfaces and handles bit timing, line

coding, and timing recovery.

Redundancy: NIS1: none (organised by routing and/or MSP 1+1)

NIS1P: 2N


Plug-in unit: NI4S1-B

Network Interface 4 × 155 Mbit/s STM-1

Capacity/ performance: Four physical SDH STM-1 interfaces, with a bandwidth of 155,52 Mbit/s for each

Interfaces: ATM interface to SFU

Clock reference output to TSS3/-A

Figure 57 NIS1's interfaces

8.4.3 NPS1 / NPS1PPurpose: NPS1(P) provides SDH STM-1/STM-4 interfaces and an RJ45 connec-

tor, and handles multiprotocol packet processing at wire speed and network connectivity.

NI4S1-B DN02179368

INTERFACES:

BACKPLANE:

- TIMING & SYNC- HMS- POWER SUPPLY- SFU- CLOCK

REFERENCEOUTPUT TO TSS3

LAN (NOT USED)

STM-1

SERVICE TERMINAL

98 DN0938143Issue 1-4




Note that RN4.0 SW does not support STM-4 interface.

Redundancy: NPS1: none (organised by routing)

NPS1P: 2N (organised by routing and MSP and/or MSP 1+1)


Plug-in unit: NP8S1, NP8S1-B

Network Interface 8 × 155 Mbit/s STM-1 or Network Interface 2 × 622 Mbit/s STM-4; one RJ45 connector


Capacity/ performance: Eight optical STM-1/OC-3 interfaces, with a bandwidth of 155,52 Mbit/s each, or two optical STM-4/OC-12 interfaces, 622,08 Mbit/s each


Interfaces: Fast Ethernet physical layer interface

Switch fabric interface

Timing and synchronization interface

Hardware management system interface

ATM interface to SFU

Figure 58 NPS1(P) interfacesDN70550849 NP8S1-B, NP8S1-A, NP8S1

1

2

3

4

5

6

7

8

STM-1 /STM-4*

Tx

Rx

Tx

Rx

Tx

Rx

Tx

Rx

Tx

Rx

Tx

Rx

Tx

Rx

Tx

Rx

STM-1

SERVICE TERMINAL

INTERFACES:

BACKPLANE:

- TIMING & SYNC

- HMS

- POWER SUPPLY

- SFU

- CLOCK REFERENCE

OUTPUT TO TSS3- LAN 1-5

CLASS 1 LASER PRODUCTIEC/EN 60825-1

* STM-4 interface cannot be used

DN0938143Issue 1-4

99



8.4.4 NPGE / NPGEPPurpose: NPGE(P) provides Ethernet interfaces and handles multiprotocol

packet processing at wire speed.

Redundancy: NPGE: none

NPGEP: 2N


Plug-in unit: NP2GE, NP2GE-B

2 × Gigabit Ethernet interface 1000Base-LX/T (optical/electrical), 2 × Fast Ethernet interface 10/100 Base-T (electrical)

Capacity/ performance: Two 1000Base-LX/T (optical or electrical) Gigabit Ethernet interfaces and two 10/100 Base-T (electrical) Fast Ethernet interfaces

Interfaces: Fast Ethernet physical layer interface

Switch fabric interface

Timing and synchronization interface

Hardware Management System interface

ATM interface to SFU

Figure 59 NPGE(P) interfaces

100 DN0938143Issue 1-4




8.5 Timing, Power Distribution and Hardware Management SubsystemsThe timing, power distribution, and Hardware Management Subsystems form the lowest level in the computing hierarchy of the IPA2800 network elements. Each subsystem is composed of a redundant master unit and a duplicated data distribution/collection bus. In each case, the bus actually extends through some lower level units to virtually all of the network element's plug-in units, which are equipped with dedicated hardware blocks supporting the core parts of the subsystem.

The clock distribution and Hardware Management subsystems in the network element use the same two types of plug-in units, namely:

• TSS3/-A, Timing and Synchronization, SDH Stratum 3 • TBUF, Timing Buffer.

The clock system meets Stratum 3 level accuracy requirement, as defined in the Bellcore TA-NWT-1244 standard.

The power distribution subsystem in the network element uses the following type of plug-in units:

RNC450 with EC216:

• PD30, Power Distribution Plug-in Unit 30 A* • CD120-A, Cabinet Power Distributor 120 A

* Note that with PD30, FTRA-B is required.

RNC196 with IC186-B:

• PD20, Power Distribution Plug-in Unit 20 A • CDP80-B, Cabinet Power Distributor 80 A

8.5.1 TBU, Timing and Hardware Management Bus UnitThe Timing and Hardware Management Bus Unit (TBU) is responsible for the network element synchronisation, timing signal distribution and message transfer functions in the hardware management system. TBU is a duplicated functional unit that consists of two plug-in units in each subrack as well as a serial bus spanning all plug-in units of the network element. The two plug-in units, the Timing and Synchronisation, SDH Stratum 3 (TSS3/-A) and Timing Buffer (TBUF) and their functions are described below.

TSS3/-A, Timing and Synchronisation, SDH Stratum 3

g New clock plug-in unit variant TSS3-A is implemented in RN5.0 based RNC2600 deliveries. However, TSS3-A can be used with RN4.0 software if Bridge HMX1BNGX version inside the plug-in unit is newer than in RN4.0 release package. Refer to technical note TS-RNC-HW-066 for more detail.

g Due to 2N redundancy a mixed configuration of TSS3 and TSS3-A is not allowed. The same variant must be used for both clock units in each RNC.

Purpose: TSS3/-As generate the clock signals necessary for synchronising the functions of RNC. Normally, TSS3/-A operates in a synchronous mode, that is, it receives an input timing reference signal from an upper level of the network and adjusts its local oscillator to the long time mean value by filtering jitter and wander from the timing signal. It transmits the ref-

DN0938143Issue 1-4

101



erence to the plug-in units in the same subrack, as well as to the TBUF units, which distribute the signals to units not directly fed by TSS3/-As.

TSS3/-A has inputs for both synchronisation references from other network elements via the network interfaces, and for those from external sources (options are 2048 kbit/s, 2048 kHz, 64+8 kHz, 1544 kHz, or 1544 kbit/s (TSS3-A)). TSS3-A input is 5 V tolerant.

If all synchronisation references are lost, TSS3/-A can operate by inde-pendently generating the synchronisation reference for the units in the network element.

TSS3/-As are also involved in the functioning of the HMS bus. They convey HMS messages through the HMS bridge node to the HMS master node. Each OMU has one master node.

TSS3-A is designed to conform ITU-T G813, G.703 and Bellcore GR-1244 recommendation.

Redundancy: 2N

Type: Functional unit with TBUF units as sub-units

Plug-in unit: TSS3/-A

Timing and Synchronisation, SDH Stratum 3

Interfaces: Synchronisation reference interfaces:

• Three line inputs (from STM-1 or PDH lines) • Two external inputs (2048 kbit/s, 2048 kHz, 64+8 kHz, 1544 kHz, or

1544 kbit/s (TSS3-A)) • Eight outputs to cabinet timing buses • One output to subrack timing bus • One external timing output (2048 kHz, 2048 kbit/s (TSS3-A), 1544

kHz (TSS3-A), or 1544 kbit/s (TSS3-A))

HMS interface

102 DN0938143Issue 1-4




Figure 60 TSS3/-A's interfaces

TBUF, Timing BufferPurpose: The TBUF unit is a clock buffer which distributes the synchronisation

signals generated by TSS3/-As to those plug-in units that are not directly fed by TSS3/-As.

TBUFs are also involved in the functioning of the HMS bus. They convey HMS messages through the HMS bridge node to the HMS master node. Each OMU has one master node.

Redundancy: 2N

Type: Functional unit, sub-unit of TSS3/-A

Plug-in unit: TBUF

Timing Buffer

Interfaces: Synchronisation reference interfaces:

• One input from TSS3/-A or another TBUF • One output to subrack timing bus • One output to another TBUF

DN0938143Issue 1-4

103



HMS interface

Figure 61 TBUF's interfaces

Connection principle and redundancy for the timing and synchronisation distri-bution bus RNC has two separate timing and synchronisation distribution buses to ensure 2N redundancy for the internal timing signal distribution. Each bus has its own system clock (a TSS3/-A plug-in unit), distribution cabling, and timing buffers (TBUF plug-in units).

The two TSS3/-A units backing up each other are placed in different subracks (subracks 1 and 2), each of which is powered by a power supply plug-in unit of its own to ensure redundancy for the power supply. Each of these subracks is also equipped with a TBUF plug-in unit, which connects the equipment in the subrack to the other clock distribution bus. The RNAC subracks 3 and 4 and all RNBC subracks have two separate TBUF units, which connect to different clock distribution buses by means of cables of their own.

In order to function correctly, the differential buses need terminations in the ends of the bus by means of a termination cable. Due to the expansion of the network element through the configuration steps, the end of the bus and similarly the termination point changes. When a new subrack is taken into use in a configuration step, the cabling must always be moved to the new subrack.

Duplicated buses need two terminations, which means that four terminators altogether in each cabinet are required for the HMS and the timing and synchronisation distribution bus.

The clock distribution principle in the network element is shown in the figure below.

TBUF DN02179371

INTERFACES:

BACKPLANE:

- ONE CLOCKREFERENCEINPUT FROMTSS3 OR TBUF

- ONE TIMING &SYNC OUTPUTTO SUBRACKTIMING BUS

- ONE TIMING &SYNC OUTPUTTO ANOTHERTBUF

- HMS

104 DN0938143Issue 1-4




Figure 62 Connection principle of the duplicated clock distribution bus

8.5.2 HMS, Hardware Management SubsystemThe Hardware Management Subsystem has three hierarchically organised layers of equipment. The upmost level in the hierarchy is formed by the Hardware Management Master Nodes (HMMNs), one in each OMU, which control the whole subsystem. TSS3/-As and TBUFs in the subracks have separate Hardware Management System Bridge nodes (HMSBs), which form the next, intermediate level in the hierarchy. As the name suggests, they serve as bridges which connect HMMNs to the lowest-level blocks in the hierarchy, Hardware Management System Slave Nodes. Implemented as dedicated

RNAC RNBC

HMS BUS 0

HMS BUS 1

HMS BUS 0

HMS BUS 1

DN70680727

RNBC

SUBRACK1

RNBC

SUBRACK2

RNBC

SUBRACK3

RNBC

SUBRACK4

RNAC

SUBRACK1

RNAC

SUBRACK2

RNAC

SUBRACK3

RNAC

SUBRACK4

In RNC2600/Step1 In RNC2600/Step3

BUS STARTING POINT

DN0938143Issue 1-4

105



hardware blocks in all plug-in units, the latter are independent from the other blocks of the plug-in unit, for example, in terms of the power supply.

A block diagram which illustrates the HMS subsystem implementation is shown in the figure below.

Figure 63 Block diagram of the HMS subsystem

Connection principle and redundancy of the HMS busRNC has also two mutually redundant hardware management buses, which are imple-mented by means of the same plug-in units as the timing and synchronisation buses, TSS3/-As and TBUFs. The routing of the hardware management buses, however, differs somewhat from that of the timing and synchronisation buses.

The hardware management bus is organised in such a way that TSS3/-As and TBUFs are on an equal level of the subsystem; both act as parallel HMS bridges which convey messages to the HMS master node. Each OMU has one master node.

HMSB 1TSS3

PIU

HMSS

PIU

HMSS

PIU

HMSSHMSS

HMMN

OMU 1

BACKPLANE BUS

BACKPLANE BUS

SUBRACK 2

HMSS

HMSB 0TBUF

HMSS

HMSB 1TBUF

PIU

HMSS

PIU

HMSS

PIU

HMSSHMSS

HMMN

OMU 0

BACKPLANE BUS

BACKPLANE BUS

SUBRACK 1

CABINET 1 CABINET 2

HMSS

HMSB 0TSS3

HMSS

HMSB 1TBUF

PIU

HMSS

PIU

HMSS

PIU

HMSS

BACKPLANE BUS

BACKPLANE BUS

SUBRACK 4

HMSS

HMSB 0TBUF

HMSS

HMSB 1TBUF

PIU

HMSS

PIU

HMSS

PIU

HMSS

BACKPLANE BUS

BACKPLANE BUS

SUBRACK 4

HMSS

HMSB 0TBUF

HMSS

HMSB 1TBUF

PIU

HMSS

PIU

HMSS

PIU

HMSS

BACKPLANE BUS

BACKPLANE BUS

SUBRACK 1

HMSS

HMSB 0TBUF

HMSS

TO OTHER RACKS

HMSB = HMS BRIDGEHMSS = HMS SLAVE NODEHMMN = HARDWARE MANAGEMENT MASTER NODE

DN99573245

106 DN0938143Issue 1-4




In order to function correctly, the differential buses need terminations in the ends of the bus by means of cabling. Due to the expansion of the network element through the con-figuration steps, the end of the bus and similarly the termination point changes. When a new subrack is taken into use in a configuration step, the cabling must always be moved to the new subrack.

Duplicated buses need two terminations, which means that four terminators altogether in each cabinet are required for the HMS and the timing and synchronisation distribution bus.

The connection principle of the HMS buses in the network element is shown in the figure below.

Figure 64 Connection principle of the duplicated HMS bus

RNAC RNBC

HMS BUS 0

HMS BUS 1

HMS BUS 0

HMS BUS 1

DN70680715

RNBC

SUBRACK1

RNBC

SUBRACK2

RNBC

SUBRACK3

RNBC

SUBRACK4

RNAC

SUBRACK1

RNAC

SUBRACK2

RNAC

SUBRACK3

RNAC

SUBRACK4

In RNC2600/Step1 In RNC2600/Step3

DN0938143Issue 1-4

107



8.5.3 Power Distribution SubsystemThe power distribution subsystem in the network element uses the following type of plug-in units:

EC216:

• PD30, Power Distribution Plug-in Unit 30 A* • CD120-A, Cabinet Power Distributor 120 A

* Note that with PD30, FTRA-B is required.

IC186-B:

• PD20, Power Distribution Plug-in Unit 20 A • CDP80-B, Cabinet Power Distributor 80 A

Purpose: The Power Distribution Subsystem distributes the -48V power from the rectifiers or batteries to the equipment inside the RNC cabinets. This subsystem consists of two CPD120-A or CPD80-B / CPD80-A power distribution panels at the top of each cabinet, one PD30/PD20 power distribution plug-in unit in each subrack, and the associated cabling. See Cable Lists for RNC for a visual representation of the power feed to each subrack.

The PD30/PD20 unit also controls the cooling equipment of its own subrack on the basis of messages sent by OMU.

Redundancy: Power distribution subsystem is duplicated by providing two indepen-dent feeding input branches from cabinet level to plug-in unit level.

Type: Power distribution

Plug-in unit: CPD120-A: Cabinet Power Distributor 120 A

and

PD30: Power Distribution Plug-in Unit 30 A

CPD80-B / CPD80-A: Cabinet Power Distributor 80 A

and

PD20: Power Distribution Plug-in Unit 20 A

Interfaces: One input for each of the two CPD120-As or CPD80-B/-As; or one dupli-cated input from the site power supply to the CPD80

Four outputs to subracks (in CPD120-A/CPD80-B/-A) or four duplicated outputs to subracks (in CPD80)

Outputs to four groups of plug-in units (in PD30/PD20)

Four duplicated inputs from CPD80 (in PD20)

Fan tray control and alarm interface

108 DN0938143Issue 1-4




Figure 65 PD30/PD20's interfaces

Power distribution principle and redundancyTo ensure 2N redundancy for the power distribution lines, the RNC cabinets are provided with two independent feeding input branches. In EC216, each feeding branch connects to a dedicated CPD120-A.

Each CPD120-A unit contains:

• Connectors for one of the two mutually redundant supply lines from the batter-ies/rectifiers. In this way the two independent input branches are kept separate until the subrack level.

• Connectors for four supply lines to the subracks. Each subrack is supplied by a line from both CPD120-As, giving 2N redundancy.

• Circuit breakers for the outgoing supply lines, each with 30-A rating

The CPD120-A allows for either grounding the 0V lead from the battery or for a use of a separate grounding cable to achieve floating battery voltage. From the CPD120-A unit, the voltage is fed through the subrack-specific PD30 power distribution plug-in units, which have individual 10-A fuses for each outgoing distribution line, to the other plug-in units in a likewise manner as to the cabinets, that is, through two mutually redundant supply lines. The two distribution lines are finally combined in the power converter

DN00256417

LED

FUSES

DN0938143Issue 1-4

109



blocks of individual plug-in units, which adapt the voltage so that it is appropriate for the plug-in unit components.

In the IC186-B cabinet, each branch connects to a dedicated CPD80-B / CPD80-A unit, which contains:

• Connectors for one of the two mutually redundant supply lines from the batter-ies/rectifiers. In this way the two independent input branches are kept separate until the subrack level.

• Connectors for four supply lines to the subracks. Each subrack is supplied by a line from both CPD80-B / -As, giving 2N redundancy.

• Circuit breakers for the outgoing supply lines, each with 20-A rating

In the IC186 cabinet both feeding branches connect into the same CPD80 unit, which contains

• Connectors for the two mutually redundant supply lines from the batteries/rectifiers • Connectors for the four duplicated supply lines to the subracks • Circuit breakers for the outgoing supply lines, each with 20-A rating

The CPD80-B/-A /CPD80 power distribution unit allows for either grounding the 0V lead from the battery or for a use of a separate grounding cable to achieve floating battery voltage.

From the power distribution unit, the voltage is fed through the subrack-specific PD20 power distribution plug-in units, which have individual 8-A fuses for each outgoing dis-tribution line, to the other plug-in units in a similar manner as to the cabinets, that is, through two mutually redundant supply lines. The two distribution lines are finally combined in the power converter blocks of individual plug-in units. The power converter blocks adapt the voltage so that it is appropriate for the plug-in unit components.

g Operating voltages must be fed in each cabinet of the network element using two separate pairs of supply cables.

The general power distribution principle for RNC is shown in the figure below. The internal DC/DC converter structure of the plug-in units is shown in the second figure.

110 DN0938143Issue 1-4




Figure 66 General power distribution principle for RNC

Power distributionplug-in unit

Main fusesor circuitbreakersin powersystem

-UB2

Terminal blocksand circuitbreakers

Filter

Protection area ofthe main fuse

Protection area of the circuitbreaker at the cabinet level

Protection areaof the glasstube fuse

at thesubrack level

DC

UB1

UB2

BOV 0

BOV 1

-UB1

-UB2

SMDfuseson PCB

-UB1

Backplane SubrackCabinet

Glass tubefuses in front

panel

Plug-in unit

Protectionarea of the fuse

at theplug-in unit

level

DC

UB1

UB2

dn02180104

DN0938143Issue 1-4

111



Figure 67 DC/DC converter structure in a plug-in unit

For information on power consumption, see Installation Site Requirements for MGW and RNC.

8.6 EHU, External Hardware Alarm UnitPurpose: The purpose of the External Hardware Alarm Unit is to receive external

alarms and send indications of them as messages via HMS to the external alarm handler located in OMU.

Another function of EHU is to drive the optional External Hardware Alarm panel (EXAU-A / EXAU), the cabinet integrated lamp, and possible other external equipment.

Redundancy: None

Plug-in unit: EHAT

External Hardware Alarm Terminal

Interfaces: Interfaces include 32 voltage controlled inputs, 8 current controlled inputs, 16 general purpose 20 mA current outputs. Connections to external devices via CPSAL/-B back interface unit located at the rear of the RNAC cabinet or CPAL back interface unit in the cabling cabinet.

Location: One unit per network element, in RNAC subrack 1.

EXAU-A / EXAU, External hardware alarm unitThe optional peripheral EXAU-A / EXAU provides a visual alarm of the fault indications of RNC. The EXAU-A / EXAU unit is located in the equipment room.

CAIND/-A, Cabinet alarm indicatorThe CAIND/-A is located on top of the RNAC cabinet and provides a visual alarm indi-cating the network element with a fault.

INPUTCIRCUIT

ENABLE=

=ON/OFF

ENABLE=

=ON/OFF

ALARMCIRCUIT

UO 1

UO 2

GND

GND

B 0V

B 0V

UB 1

UB 2

POWER CONTROL FROM HMS NODE

ALARM TO HMS NODE

DC/DC CONVERTER STRUCTUREIN A PLUG-IN UNIT

dn02179535

112 DN0938143Issue 1-4


Id:0900d805807292abConfidential

Interfaces to the Environment

9 Interfaces to the EnvironmentRNC has the following interfaces to the network it is used in:

• Power supply and grounding interfaces • PDH/TDM trunk circuit interfaces (E1/T1/JT1) • SDH/TDM trunk circuit interfaces (STM-1/OC-3) • External synchronisation and HW alarm interfaces • Ethernet/LAN interfaces to integrated OMS. As of RN5.0, the functional unit OMS

can be selected between the current integrated OMS or an external standalone OMS network element. For RN5.0 new deliveries, the standalone OMS is recom-mended.

• Interfaces for peripheral devices (keyboard, mouse, VDU, printer, external storage device)

• Service terminal interfaces

There are two locations for making the connections:

• Rear side of the cabinet (the back interface units) • Front side of the cabinet (front panels of the plug-in units)

These connections are briefly described in the following sections. For more information, see Cabinet Interfaces and External Cables of MGW and RNC and Installation Site Requirements for the MGW and RNC..

g The cables leaving the network element are not included in the network element delivery.

9.1 Power Supply and Grounding InterfacesThe interfaces for the power supply and grounding are located on the back panel of the CPD120-A / CPD80-B / CPD80-A / CPD80 cabinet power distribution units at the top of the cabinet. Each cabinet is equipped with two cabinet distribution units. The power supply cables can be routed from top or bottom of the cabinet regardless of the location of the unit.

The requirements for the power supply and grounding cables are described in sections Site power supply and Grounding and bonding of the Installation Site Requirements. Installation alternatives for the power supply and grounding cables are described in section Installing the site power supply cables and grounding the network element in Installing the MGW and RNC.

DN0938143Issue 1-4

113

WCDMA RNC Engineering Description Interfaces to the Environment


(A) and (B): the two alternatives for connecting the grounding cable(2) The CPD120-A is grounded to the cabinet grounding busbar with a grounding strip.

Figure 68 Power supply interfaces of CPD120-A with DC/I principle

DN05158732

22

DC/I

A

B

-UB2

+UB1

+UB2

-UB1

114 DN0938143Issue 1-4




(1): Grounding strip between the +UB terminal connector on the CPD120-A on the top of the cabinet and the horizontal grounding busbar of the cabinet(2): The CPD120-A is grounded to the cabinet grounding busbar with a grounding strip.

Figure 69 Power supply interfaces of CPD120-A with DC/C principle

DN05160839

-UB2

B0V

B0V

-UB1

1 21 2

DC/C

DN0938143Issue 1-4

115



Figure 70 Power supply interfaces of CPD80-B with two connection alternatives and optional ETS grounding

-UB2

+UB2

+UB1

-UB1

-UB2

+UB2

+UB1

-UB1

+UB2

+UB1

DN02180143

CPD80-B 1

CPD80-B 1

CPD80-B 0

CPD80-B 0

For optionalETS 300 253B0V grounding

116 DN0938143Issue 1-4




Figure 71 Power supply interfaces of CPD80-A and their connection alternatives: DC/I and DC/C principle

9.2 PDH TDM InterfacesThe network element's PDH connections from the NIP1 units are made via BIE1C / BIE1T connector panels at the rear side of the cabinets. The BIE1C / BIE1T connector panels are located directly behind the NIP1 units that they serve. It is possible to cable the back interface units directly into the environment or, alternatively, the cables can be routed through the cabling cabinet panels.

The numbers of the PDH/TDM lines and the plug-in unit connectors they connect to are listed in the Cable Lists for RNC.

The PDH and TDM circuit cables are usually cut and connected at the installation site, but they can also be prepared at the factory. Cables with one connector are usually prepared at the site.

9.3 SDH TDM InterfacesThe connectors for the STM-1/OC-3 cables are located on the front panels of the NIS1 or NP8S1-B plug-in units. The STM-1/OC-3 connections are routed to the BISFC panel. The BISFC panel is located at the backside of the RNAC cabinet. The use of the BISFC panel is optional. It is possible to route the STM-1 cables to the environment directly from the front panels of the NIS1 or NP8S1-B units or from the BISFC panel.

9.4 External Synchronisation InterfacesThe synchronisation interfaces are located on the TSS3/-A plug-in unit. The connections can be routed through the external synchronisation connector panel CPSY-A (TSS3/-A 0), CPSY-B (TSS3/-A 1), or CPSAL-B / CPSAL depending on the configuration. The back interface units CPSY-A, CPSY-B and CPSAL-B are located at the rear side of the RNAC cabinet.

RNC's external synchronisation interfaces support 2.048 Mbit/s and 2.048 MHz connec-tions.

REAR SIDE

+UB0

-UB0

REAR SIDE

+UB0

-UB0

DN01154291

+UB1

-UB1

+UB1

-UB1

DC/I DC/C

DN0938143Issue 1-4

117



9.5 External HW Alarm InterfacesThe external hardware alarms interfaces are located on the EHAT plug-in unit. The con-nections can be routed through the alarms connector panel or unit CPAL-A or CPSAL-B / CPSAL depending on the configuration. The CPAL-A and CPSAL/-B units are located at the rear side of the RNAC cabinet. The units also have EXAU-A / EXAU panel control.

9.6 Ethernet/LAN InterfacesThe external LAN/Ethernet connections are routed directly out of the plug-in unit front panel connectors.

The connectors for RNC's Ethernet/LAN interfaces to the NetAct, site LAN, and other destinations, for example, to printers, are placed on both the front panels and back inter-face units of the ESA24 plug-in unit, whereas ESA12 has connectors only on the front panel. The connection to OMS is protected by the MCP18-B's firewall.

The ESA24 has 24 LAN interfaces of which 22 are at the backplane connectors and 2 on the front panel (RJ45 connectors). There is also one additional serial port on the front panel (RJ45 connector). The ESA12 has 12 LAN interfaces, up to nine of which can be used for connections to the environment.

g A cabinet is configured with either the ESA24 or ESA12.

Although AL2S-D / AL2S-B, CCP18-C / CCP18-A / CCP10, CDSP-DH / CDSP-C, MX1G6-A / MX1G6, MX622-D / MX622-C / MX622-B, NI4S1-B, and SF10E / SF10 units include a LAN interface, they are provided for test use only.

9.7 Mouse, Keyboard, VDU, SCSI and Printer InterfacesThe MCP18-B plug-in unit has separate interfaces for a VDU and external storage devices. It also has four USB ports that can be used to connect a keyboard, mouse or a bootable device to the MCP18-B. USB-PS/2 adapters are not supported.

The form and pin-out of the SVGA and USB interfaces follow standard industry prac-tises. The MCP18-B's SCSI interface's pin-out follows the industry standard for Wide Ultra3 SCSI. The SCSI bus is terminated by means of an active onboard terminator in MCP18-B.

9.8 RS232 Service Terminal InterfacesRNC's service terminal interfaces are intended to be used for temporary service opera-tions, for example, debugging. For more information, see section Functional unit descriptions.

RNC 2600 Engineering

Documents

Transcript of RNC 2600 Engineering