RNC 2600 Engineering

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

WCDMA RNC Engineering Description DN0938143 Issue 1-4 Approval Date 2010-09-23

Confidential

WCDMA RNC Engineering Description

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 DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, 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 Spannung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen. Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverletzungen 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.

2

Id:0900d805807f6a85 Confidential

DN0938143 Issue 1-4


Table of contents This document has 117 pages. Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

DN0938143 Issue 1-4

1

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

2

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

3 3.1 3.2 3.3

IPA2800 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internal Messaging and Resource Allocation. . . . . . . . . . . . . . . . . . . . . Computing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redundancy Principles for IPA2800 Network Elements . . . . . . . . . . . .

13 15 16 17

4 4.1 4.1.1 4.1.2 4.1.3 4.2 4.3 4.4 4.4.1 4.5

Mechanical Construction of the IPA2800 Network Elements. . . . . . . . . Cabinets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EC216 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IC186/-B. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dimensions of Cabinets in Floor Rail on Free-standing Installations. . . Subracks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Plug-in Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Cabling Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cooling Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21 21 22 23 24 27 28 29 30 30

5 5.1 5.2 5.3 5.3.1

Cabinet and Subrack Descriptions for RNC2600. . . . . . . . . . . . . . . . . . RNC2600 Cabinet Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment in the Subracks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RNC2600 Upgrades and Expansions in RN5.0 . . . . . . . . . . . . . . . . . . . Optional Expansions for RNC2600 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31 31 33 36 36

6 6.1 6.2 6.3 6.3.1 6.3.2 6.4 6.4.1 6.4.2

Cabinet and Subrack Descriptions for RNC450. . . . . . . . . . . . . . . . . . . RNC450 Cabinet Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment in the subracks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RNC450 Upgrades and Expansions in RN5.0 . . . . . . . . . . . . . . . . . . . . Mandatory Upgrades for RNC450 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optional Upgrades and Expansions for RNC450 . . . . . . . . . . . . . . . . . RNC450 Upgrades and Expansions in RN4.0 . . . . . . . . . . . . . . . . . . . . Mandatory Upgrades for RNC450 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optional Upgrades and Expansions for RNC450 . . . . . . . . . . . . . . . . .

37 37 39 42 42 42 42 42 43

7 7.1 7.1.1 7.1.2 7.1.3 7.1.4 7.1.5 7.2 7.3 7.3.1

Cabinet and Subrack Descriptions for RNC196. . . . . . . . . . . . . . . . . . . RNC196 Cabinet Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RNC196 Step 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RNC196 Step 6 and RNC196 Step 7. . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Upgrade to RNC196 Step 6 and RNC196 Step 7 . . . . . . . . . RNC196 Step 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Upgrade to RNC196 Step 8 . . . . . . . . . . . . . . . . . . . . . . . . . Equipment in the Subracks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrades and Expansions for RNC196 in RN5.0 . . . . . . . . . . . . . . . . . Mandatory Upgrades for RNC196 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

44 44 45 47 49 52 54 57 60 60


3


4

7.3.2 7.4 7.4.1 7.4.2

Optional Upgrades for RNC196 . . . . . . . . . . . . . . . . . . . Upgrades and Expansions for RNC196 in RN4.0 . . . . . . Mandatory Upgrades for RNC196 . . . . . . . . . . . . . . . . . Optional Upgrades for RNC196 . . . . . . . . . . . . . . . . . . .

8 8.1 8.2 8.2.1 8.2.2 8.2.3 8.2.4 8.2.5 8.2.6 8.2.7 8.2.8 8.2.9 8.3 8.3.1 8.3.2 8.3.3 8.4 8.4.1 8.4.2 8.4.3 8.4.4 8.5 8.5.1 8.5.2 8.5.3 8.6

Functional Unit Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Functional Unit Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Management, Control Computer and Data Processing Units . . . . . . . . . 62 DMCU, Data and Macro Diversity Combining Unit . . . . . . . . . . . . . . . . . 62 GTPU, Gateway Tunneling Protocol Unit . . . . . . . . . . . . . . . . . . . . . . . . 64 ICSU, Interface Control and Signalling Unit . . . . . . . . . . . . . . . . . . . . . . 67 Integrated OMS, Operation and Maintenance Server and its sub-units . 70 ESA24, Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 ESA12, Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 OMU, Operation and Maintenance Unit and Its Subunits . . . . . . . . . . . . 75 RRMU, Radio Resource Management Unit . . . . . . . . . . . . . . . . . . . . . . 80 RSMU, Resource and Switch Management Unit . . . . . . . . . . . . . . . . . . 83 Switching and Multiplexing Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 A2SU, AAL2 Switching Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 MXU, Multiplexer Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 SFU, Switching Fabric Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Network Interface Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 NIP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 NIS1 / NIS1P. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 NPS1 / NPS1P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 NPGE / NPGEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Timing, Power Distribution and Hardware Management Subsystems . 100 TBU, Timing and Hardware Management Bus Unit . . . . . . . . . . . . . . . 100 HMS, Hardware Management Subsystem . . . . . . . . . . . . . . . . . . . . . . 104 Power Distribution Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 EHU, External Hardware Alarm Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . 111

9 9.1 9.2 9.3 9.4 9.5 9.6 9.7 9.8

Interfaces to the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Power Supply and Grounding Interfaces . . . . . . . . . . . . . . . . . . . . . . . 112 PDH TDM Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 SDH TDM Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 External Synchronisation Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 External HW Alarm Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Ethernet/LAN Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Mouse, Keyboard, VDU, SCSI and Printer Interfaces . . . . . . . . . . . . . 117 RS232 Service Terminal Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 117


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

. . . . . . 60 . . . . . . 61 . . . . . . 61 . . . . . . 61

DN0938143 Issue 1-4


List of figures Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Figure 22 Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 Figure 28 Figure 29 Figure 30 Figure 31 Figure 32 Figure 33 Figure 34 Figure 35 Figure 36 Figure 37 Figure 38 Figure 39 Figure 40 Figure 41 Figure 42

DN0938143 Issue 1-4

Block diagram of the RNC2600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Block diagram of the RNC450 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 EC216 cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 IC186-B cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Dimensions of the EC216 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Dimensions of the IC186-B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Dimensions of EC216 / IC186-B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 SRA1 subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Layout options for the RNC2600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 RNAC cabinet in RNC2600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 RNBC cabinet in RNC2600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Layout options for the RNC450 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 RNAC cabinet in RNC450 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 RNBC cabinet in RNC450 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Layout options for the RNC196 (with optional cabling cabinet) . . . . . . . 44 RNAC cabinet - RNC196 step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 RNBC cabinet - RNC196 steps 2-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 RNAC cabinet - RNC196 steps 6 and 7. . . . . . . . . . . . . . . . . . . . . . . . . 48 RNBC cabinet - RNC196 steps 6 and 7. . . . . . . . . . . . . . . . . . . . . . . . . 49 Configuration steps RNC196 step 6 and 7 with mandatory hardware changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 RNAC cabinet - RNC196 step 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 RNBC cabinet - RNC196 step 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Configuration step RNC196 step 8 with mandatory hardware changes 56 DMCU's interfaces - CDSP-DH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 DMCU's interfaces - CDSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 GTPU's interfaces - CCP18-C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 GTPU's interfaces - CCP18-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 GTPU's interfaces - CCP10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 ICSU's interfaces - CCP18-C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 ICSU's interfaces - CCP18-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 ICSU's interfaces - CCP10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Integrated OMS interfaces (MCP18-B) . . . . . . . . . . . . . . . . . . . . . . . . . 71 Integrated OMS storage device interfaces. . . . . . . . . . . . . . . . . . . . . . . 72 SCSI connection principle for integrated OMS storage devices (MCP18-B) 73 ESA24's interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 ESA12's interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 OMU's interfaces - CCP18-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 OMU's interfaces - CCP10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 OMU's storage devices' interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 SCSI connection principle for OMU storage devices - CCP18-A and HDS-B 79 SCSI connection principle for OMU storage devices - CCP10, HDS-A and MDS-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 RRMU's interfaces - CCP18-C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81


5


Figure 43 Figure 44 Figure 45 Figure 46 Figure 47 Figure 48 Figure 49 Figure 50 Figure 51 Figure 52 Figure 53 Figure 54 Figure 55 Figure 56 Figure 57 Figure 58 Figure 59 Figure 60 Figure 61 Figure 62 Figure 63 Figure 64 Figure 65 Figure 66 Figure 67 Figure 68 Figure 69 Figure 70 Figure 71

6

RRMU's interfaces - CCP18-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 RRMU's interfaces - CCP10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 RSMU's interfaces - CCP18-C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 RSMU's interfaces - CCP18-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 RSMU's interfaces - CCP10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 ATM connections to SFU - RNC450 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 A2SU's interfaces - AL2S-D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 A2SU's interfaces - AL2S-B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 MXU's interfaces - MX1G6 and MX1G6-A . . . . . . . . . . . . . . . . . . . . . . . 91 MXU's interfaces - MX622 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 SFU's interfaces - SF20H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 SFU's interfaces - SF10E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 SFU's interfaces - SF10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 NIP1's interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 NIS1's interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 NPS1(P) interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 NPGE(P) interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 TSS3/-A's interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 TBUF's interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Connection principle of the duplicated clock distribution bus . . . . . . . . 104 Block diagram of the HMS subsystem . . . . . . . . . . . . . . . . . . . . . . . . . 105 Connection principle of the duplicated HMS bus . . . . . . . . . . . . . . . . . 106 PD30/PD20's interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 General power distribution principle for RNC . . . . . . . . . . . . . . . . . . . . 110 DC/DC converter structure in a plug-in unit . . . . . . . . . . . . . . . . . . . . . 111 Power supply interfaces of CPD120-A with DC/I principle . . . . . . . . . . 113 Power supply interfaces of CPD120-A with DC/C principle . . . . . . . . . 114 Power supply interfaces of CPD80-B with two connection alternatives and optional ETS grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Power supply interfaces of CPD80-A and their connection alternatives: DC/I and DC/C principle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116


DN0938143 Issue 1-4


List of tables Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11

DN0938143 Issue 1-4

Computing platform hierarchy levels for IPA2800 RNC . . . . . . . . . . . . 16 Redundancy principles of the functional units in the RNC . . . . . . . . . . 19 Number of units in RNC2600 subracks . . . . . . . . . . . . . . . . . . . . . . . . . 34 Maximum number of units in the RNC2600 for each configuration step 34 Numbers of units in RNC450 subracks . . . . . . . . . . . . . . . . . . . . . . . . . 39 Maximum number of units in the RNC450 for each configuration step . 40 Minimum hardware level and configuration expansion for RNC196 step 6 51 Minimum hardware level and configuration expansion for RNC196 step 7 51 Minimum hardware level and configuration expansion for RNC196 step 8 57 Number of units in RNC196 subracks . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Maximum number of units in RNC196 for each configuration step . . . . 59


7


8


DN0938143 Issue 1-4


Summary of changes

Summary of changes Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues. Issue 1-4 In Table 1 Computing Platform Hierarchy Levels, operating system for MCP18-B has been corrected to Linux. Issue 1-3 Reference to Hardware upgrades from RNC196 step 7 to step 8 removed because this document is not ready. Issue 1-2 MCP18-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 Integrated 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-1 Chapter 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-0 Issue 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).

DN0938143 Issue 1-4


9

About WCDMA RNC Engineering Description


1 About WCDMA RNC Engineering Description This 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 upgrades This document describes the hardware configurations, mechanics, and electromechanics 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 Mechanical 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 documentation The site requirements for the RNC are described in the document Installation Site Requirements for MGW and RNC. It provides the following information: • • • • •

10

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

Id:0900d80580751dac Confidential

DN0938143 Issue 1-4


• • • •

About WCDMA RNC Engineering Description

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.

DN0938143 Issue 1-4

Id:0900d80580751dac Confidential

11

RNC Hardware Changes


2 RNC Hardware Changes This section summarises the differences in the hardware implementation between RN4.0 and RN5.0. New plug-in units Compared 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 software Due to 2N redundancy a mixed configuration of TSS3 and TSS3-A is not allowed

Functional units changes •

12

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.

Id:0900d805807031f0 Confidential

DN0938143 Issue 1-4


IPA2800 System Architecture

3 IPA2800 System Architecture The 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 controlled 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.

DN0938143 Issue 1-4


13



ICSU

MXU NPS1(P)

DMCU NPGE(P)

SFU ICSU Ethernet Ethernet

SWU

RSMU

MXU MXU

DMCU

OMU

Ethernet

WDU

OMS*

TBU EHU

HDD* * Optionally, the integrated OMS and the related HDDs can be removed as of RN5.0. SWITCHING AND MULTIPLEXING UNIT NETWORK INTERFACE UNIT MANAGEMENT, CONTROL COMPUTER AND DATA PROCESSING UNIT DN70618302

Figure 1

14

Block diagram of the RNC2600


DN0938143 Issue 1-4



ICSU A2SU GTPU MXU ICSU

DMCU NIP1

RRMU MXU

DMCU E1/T1/JT1 Iu Iur ATM Iub

GTPU

RSMU OMS */ NEMU

ETHERNET 100 BASE Tx

SFU

OMU

ICSU Hard disk

FDU

WDU

A2SU

A2SU MXU

DMCU Iu Iur Iub

STM-1 ATM

NIS1

DMCU

GTPU

TBU EHU SWITCHING AND MULTIPLEXING UNIT NETWORK INTERFACE UNIT MANAGEMENT, CONTROL COMPUTER AND DATA PROCESSING UNIT

* OMS replaces NEMU in RN3.0

DN01128754

Figure 2

3.1

Block diagram of the RNC450

Internal Messaging and Resource Allocation In 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 generation 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: •

DN0938143 Issue 1-4

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


15


•

3.2


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 functional 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.

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

Level

Type

Processor

Operating system

PIUs

Communication to upper level/other units

Level 4

Management computer

Intel P M 745

Linux

MCP18-B

TCP/IP

Control computer

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

DMX with POSIX

CCP18-C/ CCP18-A/ CCP10

LAN/Ethernet, ATM virtual channels

Chorus

MX1G6/-A,

ATM virtual channels

Level 3

Intel PIII

Intel PIII (CCP10) Level 2

Unit computer

Motorola PowerQuicc II

SF10E, AL2S-D/-B, CDSP-C/-B/DH, NP2GE-B, NP8S1-B

Level 1

Table 1

Control processor

8-bit microcontroller

No OS needed

Embedded in all PIUs

Selected case by case

Computing platform hierarchy levels for IPA2800 RNC Management computer unit MCP18-B and control computer unit CCP18-C/CCP18A/CCP10 The MCP18-B and CCP18-C / CCP18-A / CCP10 plug-in units are used as the management computer units and control computer units, respectively, in the IPA2800 network elements. Both are single board computers with an onboard PCI bus. The

16


DN0938143 Issue 1-4



MCP18-B and CCP18-C / CCP18-A are based on Pentium M 745 1800 MHz microprocessor. 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 Elements The 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 units Different 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 corresponding 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 level In the Intel processors, the following methods are used to ensure proper operation: • • • •

DN0938143 Issue 1-4

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


17


• • • •


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 redundancy Some 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 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. 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 interface 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 interfaces, 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 Management Subsystems Virtually 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 redundant 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.

18


DN0938143 Issue 1-4



RNC FU

Redundancy principle

RSMU

2N

Plug-In unit variant choices for RNC196 or RNC450

Plug-In unit variant choices for RNC2600

2 * CCP10

2 * CCP18-A

or

or

2 * CCP18-A

2 * CCP18-C

or 2 * CCP18-C MXU

2N

2 * MX622-B

2 * MX1G6-A

or 2 * MX662-C or 2 * MX622-D as same subrack WO-SP pair OMU

2N

2 * CCP10

2* CCP18-A

or 2 * CCP18-A SFU

2N

2 * SF10

2 * SF20H

or 2 * SF10E TBU

2N

2 * TSS3 or 2 * TSS3-A

2 * TSS3 or 2 * TSS3-A

in subracks 1-2 and in subracks 1-2 and 2 * TBUF in other subracks

2 * TBUFin other subracks

WDU / OMU

2N

Mixed use of WDW18, WDW18S, WDW36 , WDW73 or WDW147

WDW147

ICSU

N+1

Mixed use of CCP10, CCP18-A, and CCP18-C

CCP18-A

Mixed use of

N/A

A2SU

SN+

or CCP18-C

AL2S-B and AL2SD 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

DN0938143 Issue 1-4

Redundancy principles of the functional units in the RNC


19



RNC FU

Redundancy principle

Plug-In unit variant choices for RNC196 or RNC450

Plug-In unit variant choices for RNC2600

NIP1

No redundancy (Transport redundancy organised by call routing).

NI16P1A

N/A

NIS1

No redundancy (Transport redundancy 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 redundancy 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

No redundancy

MCP18-B

MCP18-B

OMS

1)

SWU

Optional 2N (for 1 * ESA12 LAN connectivity) 2) or

1-2 * ESA24

1-2 * ESA24

Table 2 1)

2)

20

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

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. Equipment database does not recognise ESA24 as a functional unit and HMS does not supervise it.


DN0938143 Issue 1-4


Mechanical Construction of the IPA2800 Network Elements

4 Mechanical Construction of the IPA2800 Network Elements The 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

Cabinets The equipment of the IPA2800 network elements is housed in EC216 or IC186/-B equipment 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 structure 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 accordance with Telcordia GR-63-CORE Zone 4, and the EMC emission and immunity characteristics comply with the EN 300386 and CFR 47, FCC Part 15 standards, respectively. NEBS compliance NEBS 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

DN0938143 Issue 1-4

Id:0900d805807031ff Confidential

21



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-63CORE 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): •

• •

22

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 connectors for redundant incoming and outgoing supply lines plus circuit breakers for the latter


DN0938143 Issue 1-4



• • • • •

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 shelves CS216-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 installation. They have levers with an active locking mechanism, plus separate locks for securing the levers to their places.

4.1.2

IC186/-B Air Guide CPD80-B Cabinet Power distribution Side Cover Plates

Cable Support

Doors Plug-in units

Fan tray + Cover plate Subrack

Adjustment foot

DN02179668

Figure 4

IC186-B cabinet

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

DN0938143 Issue 1-4


23


• • •

• • • • •


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 connectors 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 installation. 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 Installations The 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.

24


DN0938143 Issue 1-4


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.

DN0938143 Issue 1-4


25



600

50

IC186 Primary area for routing cables

50 500

180

Secondary area for routing cables

100

Secondary area for routing cables

50 70

50

DN02133818

Figure 6

FRONT

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 installation When 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.

26


DN0938143 Issue 1-4


Figure 7


Dimensions of EC216 / IC186-B

Dimensions of cabinets in installation on floor rails The 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

Subracks The 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 subracks, except for upgrades from previously delivered RNCs to RNC196 step 6 and

DN0938143 Issue 1-4


27



RNC196 step 7. Each of the two subracks has an individual configuration, with N+1redundant 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).

DN99572546

Figure 8

4.3

SRA1 subrack

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

28


DN0938143 Issue 1-4



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 connections, however, are made from the front panels, normally by means of standard RJ45 connectors. The plug-in units of the IPA2800 network elements are designed to support hot-swapping. 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 insertion/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 connections. 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): • •

4.4

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)

Cabling The 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 cables The 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 cables The site (outgoing) cables are all the cables which leave the network element. They include: • • • •

DN0938143 Issue 1-4

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


29


•


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 Principles The 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 completely 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 connectors in the cabling cabinets.

4.5

Cooling Equipment Each 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 plugin units and other hardware units.

30


DN0938143 Issue 1-4


Cabinet and Subrack Descriptions for RNC2600

5 Cabinet and Subrack Descriptions for RNC2600 5.1

RNC2600 Cabinet Types The 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.

Left-to-right configuration 1200mm

600mm

RNAC

RNBC

Right-to-left configuration

RNBC

RNAC

Front side of the cabinets DN0624966

Figure 9

Layout options for the RNC2600

RNC2600 has three configuration steps: •

•

•

RNC2600/Step 1 Configuration step 1 of RNC2600 implements the minimum capacity and it consists of cabinet mechanics for RNAC and a fully equipped RNAC cabinet. RNC2600/Step 2 Configuration 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 3 Configuration 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:

DN0938143 Issue 1-4

Id:0900d8058072d088 Confidential

31


• •


The NISx units with STM-1 interfaces are replaced with NPGE(P) units with IP interface 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. RNAC

* Optionally, the

SFU 0

integrated OMS and the two related HDDs can be removed as of RN5.0

ICSU 0 RSMU 0 SWU 0 OMS * DMCU 0 DMCU 1 MXU 0 PD30 MXU 1 DMCU 2 DMCU 3 WDU 0 (OMU) HDD 0 (OMS) * OMU 0 NPGEP 0 / NPS1P 0 NPGEP 2 TBUF TSS3/-A

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

1

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

ICSU 1 RSMU 1 SWU 1 ICSU 2 DMCU 4 DMCU 5 MXU 2 PD30 MXU 3 DMCU 6 DMCU 7 WDU 1 (OMU) HDD 1 (OMS) * OMU 1 NPGEP 1 / NPS1P 1 NPGEP 3 TBUF TSS3/-A

SFU 1

2

RNC2600/ Step 1

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

ICSU 3 ICSU 4 ICSU 5 ICSU 6 EHU DMCU 8 DMCU 9 DMCU 10 MXU 4 PD30 MXU 5 DMCU 11 DMCU 12 ICSU 7 NPGEP 4 / NPS1P 2 NPGEP 6 / NPS1P 4 TBUF TBUF

3

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

ICSU 8 ICSU 9 ICSU 10 ICSU 11 ICSU 12 DMCU 13 DMCU 14 DMCU 15 MXU 6 PD30 MXU 7 DMCU 16 DMCU 17 ICSU 13 NPGEP 5 / NPS1P 3 NPGEP 7 / NPS1P 5 TBUF TBUF

4

38

38 DN0938743

Figure 10

32

RNAC cabinet in RNC2600


DN0938143 Issue 1-4






Figure 11

5.2

DN0938143 Issue 1-4


RNBC

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

RNC2600/ Step 2 38

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

38

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

RNC2600/ Step 3 38

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

38

DN0938755

RNBC cabinet in RNC2600

Equipment in the Subracks

The configurations of the subracks are shown in the tables below.


33


Unit type

RNAC configuration step 1


RNBC configuration step 2

RNBC configuration step 3

Min.

Max. conf.

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 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

Configuration steps

DMCU / CDSP-DH

RNC2600/Step 1

RNC2600/Step 2

RNC2600/Step 3

18

28

38

EHU / EHAT

1 for all configurations

ICSU / CCP18-C

14

26

38

MXU / MX1G6-A

8

12

16

0-6

0-10

0-14

NPS1P / NP8S1-B a)/b)

Table 4

34

Maximum number of units in the RNC2600 for each configuration step


DN0938143 Issue 1-4



Unit type

Configuration steps RNC2600/Step 1

RNC2600/Step 2

RNC2600/Step 3

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


- / PD30

4

6

RSMU / CCP18-C


SFU / SF20H


TBU / TSS3/-A


TBU / TBUF

6

10

HDS-B


WDU / WDW147 (OMU)


HDD / WDW147 (OMS) c)


SWU / ESA24 a) OMS / MCP18-B c)

Table 4

8

14

1-2 for all configurations 1 for all configurations


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 RNC2600 In 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 plugin units. For more information, see section Interfaces to the environment. The back interface units located at the rear side of the cabinet are described below: •

•

•

DN0938143 Issue 1-4

BISFA Back 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. BISFB Back interface unit SFP type B for MX1G6-A with 4 SFP connectors for cabling to SFU. BISFB-A Back interface unit SFP type B for MBMS upgrades to RNC196, IC186/IC186-B mechanics.


35


•

•

5.3 5.3.1


BISFC Back 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. BISFD Back interface unit SFP type D for SF20H with 8 SFP connectors for NPGE(P), NPS1(P) and MXU units.

RNC2600 Upgrades and Expansions in RN5.0 Optional Expansions for RNC2600 The 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.

36


DN0938143 Issue 1-4




RNC450 Cabinet Types The 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.


600mm

RNAC

RNBC


RNBC

RNAC


Figure 12

Layout options for the RNC450

RNC450 has three configuration steps: •

•

•

RNC450 step 1 Configuration step 1 of RNC450 implements the minimum capacity and it consists of cabinet mechanics for RNAC and a fully equipped RNAC cabinet. RNC450 step 2 Configuration 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 3 Configuration 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:

DN0938143 Issue 1-4


37


•

• •


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.

TSS3 EHU OMU 1 ICSU 2 ICSU 3 TSS3

B: HDD 1 OMS

TBUF

OMU 0 ICSU 0 ICSU 1 TBUF

B: HDD 0 OMS

SFU 0

DMCU 0 DMCU 1 ESA24 0 (SWU 0) OMS ICSU 22 RSMU 0 MXU 0 PD30 MXU 1 A2SU 0 A2SU 1 A: WDU 0 OMU

SFU 1

DCMU 4 DMCU 5 ICSU 4 ICSU 5 ICSU 6 DMCU 6 DMCU 7 DMCU 8 MXU 4 PD30 MXU 5 A2SU 3 DMCU 9 DMCU 10 NIS1P 10/NIP 1 0/NPGE(P) 0 GTPU 1 / ICSU25 NIS1P 0/NPGE(P) 6 NIS1P 2 TBUF TBUF DMCU 11 DMCU 12 ICSU 7 ICSU 8 ICSU 9 DMCU 13 DMCU 14 DMCU 15 MXU 6 PD30 MXU 7 A2SU 4 DMCU 16 DMCU 17 NIS1P 11/NPGE(P) 1 GTPU 2 / ICSU26 NIS1P 1/NPGE(P) 7 NIS1P 3 TBUF TBUF

Configuration step 1

DMCU 2 DMCU 3 ESA24 1 (SWU 1) GTPU 0 / ICSU24 ICSU 23 RSMU 1 MXU 2 PD30 MXU 3 A2SU 2 A: WDU 1 OMU

RNAC

DN70621159

Figure 13

38

FRONT VIEW

RNAC cabinet in RNC450


DN0938143 Issue 1-4

-/ NPGE(P) 5 DMCU 37 ICSU 19 ICSU 20 ICSU 21 DMCU 38 DMCU 39 DMCU 40 MXU 14 PD30 MXU 15 A2SU 8 DMCU 41 DMCU 42 DMCU 43 GTPU 7 / ICSU31 NIS1P 10 NIS1P 11 TBUF TBUF -/ NPGE(P) 4 DMCU 30 ICSU 16 ICSU 17 ICSU 18 DMCU 31 DMCU 32 DMCU 33 MXU 12 PD30 MXU 13 A2SU 7 DMCU 34 DMCU 35 DMCU 36 GTPU 6 / ICSU30 NIS1P 6 NIS1P 10 TBUF TBUF -/ NPGE(P) 3 DMCU 25 ICSU 13 ICSU 14 ICSU 15 DMCU 26 DMCU 27 MXU 10 PD30 MXU 11 A2SU 6 DMCU 28 DMCU 29 GTPU 4 / ICSU28 GTPU 5 / ICSU29 NIS1P 5 NIS1P 7 TBUF TBUF

-/ NPGE(P) 2 DMCU 18 ICSU 10 ICSU 11 ICSU 12 DMCU 19 DMCU 20 DMCU 21 MXU 8 PD30 MXU 9 A2SU 5 DMCU 22 DMCU 23 DMCU 24 GTPU 3 / ICSU27 NIS1P 4 NIS1P 6 TBUF TBUF


Figure 14

6.2

Unit type

Table 5

DN0938143 Issue 1-4


RNBC



DN70621174

FRONT VIEW

RNBC cabinet in RNC450

Equipment in the subracks

The configurations of the subracks are shown in the tables below.

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

Numbers of units in RNC450 subracks


39


Unit type


RNAC

RNBC

Min

Max

SR 1

SR 2

SR 3

SR 4

SRs 1–4

conf.

conf.

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.

Table 5

Numbers of units in RNC450 subracks (Cont.)

Unit type

Configuration steps RNC450 step 1 RNC450 step 2 RNC450 step 3

A2SU

5

7

9

DMCU

18

30

44

EHU


ESA24


Table 6

40



DN0938143 Issue 1-4



Unit type

Configuration steps RNC450 step 1 RNC450 step 2 RNC450 step 3

GTPU

3

6

8

ICSU b)

10

16

22

MXU

8

12

16

OMS a)


OMS Hard disk HDD a)


NIP1


NIS1

4

6

6

NIS1P

6

10

12

NPGE(P)

4

6

8

OMU


OMU Hard disk WDU


PD30

4

6

RRMU b)


RSMU


SFU


TBUF TSS3

6

10

8

14


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 integrated 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.

Table 6


For information on the capacities of the alternative configurations, see RNC450 capacity in Product Description for RNC450. 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 RNC450 In 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 document. The back interface units located at the rear side of the RNAC cabinet are described below: •

DN0938143 Issue 1-4

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


41


•

•

6.3 6.3.1


unit. CPSY-A (for TSS3/-A 0) and CPSY-B (for TSS3/-A 1) are equipped in the same network element. CPAL-A Back 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 BIE1C The 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 connector panel is installed in the SRBI-C behind the NIP1 0 installation position in RNAC subrack 3, slot 15.

RNC450 Upgrades and Expansions in RN5.0 Mandatory Upgrades for RNC450 Minimum hardware requirement for all configurations in RN5.0: the disk size for Integrated 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 RNC450 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. 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. For more information, prerequisites and the instructions, see Hardware Expansion for RNC450 and Upgrading RNC450 to RNC2600.

6.4 6.4.1

RNC450 Upgrades and Expansions in RN4.0 Mandatory Upgrades for RNC450 In 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 information, prerequisites and the instructions, see Hardware Expansion for RNC450 and Upgrading RNC450 to RNC2600.

42


DN0938143 Issue 1-4


6.4.2

Optional Upgrades and Expansions for RNC450 •

•

•

•

•

DN0938143 Issue 1-4


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 personnel 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 element For more information, prerequisites and the instructions, see Upgrading RNC450 to RNC2600. SFU upgrade In 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 upgrade IP 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 (CDSPDH 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.


43




RNC196 Cabinet Types The 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 configuration. 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.


600mm

RNAC

CEXT

RNBC

RNAC

CEXT

RNBC


RNBC

CEXT

RNAC

RNBC

CEXT

RNAC


Figure 15

44

Layout options for the RNC196 (with optional cabling cabinet)

Id:0900d80580751db8 Confidential

DN0938143 Issue 1-4



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 5 Previously 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.

DN0938143 Issue 1-4


45

NIP1 2/ NPGE(P) 1 NIP1 3 ICSU 3 ICSU 4 ICSU 5 DMCU 6 DMCU 7 DMCU 8 MXU 4 PD20 MXU 5 DMCU 9 DMCU 10 DMCU 11 A2SU 2 iICSU 6 GTPU 1 / ICSU25 NIS1(P) 3 TBUF TBUF

NIP1 0/ NPGE(P) 0 NIP1 1 ICSU 0 ICSU 1 ICSU 2 DMCU 0 DMCU 1 DMCU 2 MXU 2 PD20 MXU 3 DMCU 3 DMCU 4 DMCU 5 A2SU 1 GTPU 0 / ICSU24 NIS1(P) 2 TBUF TBUF

Figure 16

46 DN70621517

NIS1(P) 4/ NPGE(P) 6 NIS1(P) 6 NIS1(P) 0 A2SU 0 RRMU 0 RSMU 0 MXU 0 PD20 EHU ESA12 / ESA24 0 NEMU


TBUF

TSS3

TSS3

WDU 0 (OMU) WDU 1 (OMU) TBUF

HDD 0 (NEMU/OMS) OMU 0

HDD 1 (NEMU/OMS) OMU 1

FDU (OMU)

SFU 0

SFU 1 NIS1(P) 5/ NPGE(P) 7 NIS1(P) 7 NIS1(P) 1 Optional ESA24 1 RRMU 1 RSMU 1 MXU 1 PD20

Cabinet and Subrack Descriptions for RNC196 WCDMA RNC Engineering Description

RNAC


FRONT VIEW

RNAC cabinet - RNC196 step 1

DN0938143 Issue 1-4



NIP1 10/ NPGE(P) 5 NIP1 11 ICSU 16 ICSU 17 ICSU 18 DMCU 36 DMCU 37 DMCU 38 MXU 12 PD20 MXU 13 DMCU 39 DMCU 40 DMCU 41 A2SU 6 GTPU 5 / ICSU29 DMCU 42 DMCU 43 TBUF TBUF




RNBC

7.1.2





DN70621532

FRONT VIEW

Figure 17

RNBC cabinet - RNC196 steps 2-5

RNC196 Step 6 and RNC196 Step 7 The 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.

DN0938143 Issue 1-4


47

DMCU 42 ICSU 3 ICSU 4 ICSU 5 DMCU 6 DMCU 7 DMCU 8 MXU 4 PD20 MXU 5 DMCU 9 DMCU 10 DMCU 11 A2SU 2 NISx 1 GTPU 1 NISx 3 TBU 1 TBU 0

NIP1 0 (Optional) DMCU 34 ICSU 0 ICSU 1 ICSU 2 DMCU 0 DMCU 1 DMCU 2 MXU 2 PD20 MXU 3 DMCU 3 DMCU 4 DMCU 5 A2SU 1 NISx 0 GTPU 0 NISx 2 TBU 1 TBU 0

Figure 18

48 SFU 1 DMCU 26 DMCU 27 A2SU 8 Optional ESA24 1 ICSU 23 RSMU 1 MXU 14 PD20 MXU 15 GTPU 6 EHU A: WDU 1 (OMU) B: HDD 1 (OMS) OMU 1 ICSU 20 ICSU 21 TBU 1 TBU 0

DMCU 18 DMCU 19 A2SU 7 A2SU 0 ICSU 22 RSMU 0 MXU 0 PD20 MXU 1 ESA12 / ESA24 0 OMS A: WDU 0 (OMU) B: HDD 0 (OMS) OMU 0 ICSU 6 ICSU 19 TBU 1 TBU 0

SFU 0


RNAC


DN70623803

FRONT VIEW

RNAC cabinet - RNC196 steps 6 and 7


DN0938143 Issue 1-4







DMCU 43 ICSU 16 ICSU 17 ICSU 18 DMCU 36 DMCU 37 DMCU 38 MXU 12 PD20 MXU 13 DMCU 39 DMCU 40 DMCU 41 A2SU 6 GTPU 5 NIS1P 9 NIS1P 11 TBU 1

TBU 0

DMCU 35 ICSU 13 ICSU 14 ICSU 15 DMCU 28 DMCU 29 DMCU 30 MXU 10 PD20 MXU 11 DMCU 31 DMCU 32 DMCU 33 A2SU 5 GTPU 4 NIS1P / NIS1 8 NIS1P / NIS1 10 TBU 1 TBU 0

ICSU 10 ICSU 11 ICSU 12 DMCU 20 DMCU 21 DMCU 22 MXU 8 PD20 MXU 9 DMCU 23 DMCU 24 GTPU 7 A2SU 4 GTPU 3 NIS1P 5 NIS1P 7 TBU 1

TBU 0

DMCU 25 ICSU 7 ICSU 8 ICSU 9 DMCU 12 DMCU 13 DMCU 14 MXU 6 PD20 MXU 7 DMCU 15 DMCU 16 DMCU 17 A2SU 3 GTPU 2 NIS1P / NIS1 4 NIS1P / NIS1 6 TBU 1 TBU 0

RNBC

DN70623815

Figure 19

7.1.3

FRONT VIEW

RNBC cabinet - RNC196 steps 6 and 7

Hardware Upgrade to RNC196 Step 6 and RNC196 Step 7 An 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.

DN0938143 Issue 1-4


49



The configuration of the RNC must be at least RNC196 step 5 before the RNC196 configuration 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.

= unit relocated or removed = unit added = unit upgraded to newest variant

TBU 0 TBU 1

NISx 4 NISx 6 NIS1P 5 NIS1P 7

TBU 0 TBU 1 TBU 0


TBU 1

NISx 8 NISx 10 NIS1P 9 NIS1P 11


TBU 0

GTPU 7



TBU 1

DMCU 25

NIP1 10 NIP1 11 ICSU 16 ICSU 17 ICSU 18 DMCU 36 DMCU 37 DMCU 38 MXU 12 PD20 MXU 13 DMCU 39 DMCU 40 DMCU 41 A2SU 6 GTPU 5 DMCU 42 DMCU 43

DMCU 43


DMCU 35


-


Figure 20


TBU 0 TBU 1 TBU 0 TBU 1 TBU 0 TBU 1 TBU 0 TBU 1

DMCU 18 NISx 4 DMCU 19 NISx 6 NISx 0 A2SU 7 A2SU 0 RRMU 0 RSMU 0 MXU 0 PD20 EHU MXU 1 ESA12 / ESA24 0 NEMU HDD 0 WDU 0 (NEMU) (OMU) OMU 0 ICSU 6 WDU 0 (OMU) ICSU 19 NIS1P 5 DMCU 26 NIS1P 7 DMCU 27 NISx 1 A2SU 8 ESA24 1 (Optional) RRMU 1 RSMU 1 MXU 1 MXU 14 PD20 MXU 15 FDU GTPU 6 EHU HDD 0 WDU 0 (NEMU) (OMU) OMU 1 WDU 1 ICSU 20 (OMU) ICSU 21

NIP1 2 DMCU 42 NIP1 3 ICSU 3 ICSU 4 ICSU 5 DMCU 6 DMCU 7 DMCU 8 MXU 4 PD20 MXU 5 DMCU 9 DMCU 10 DMCU 11 A2SU 2 ICSU 6 NISx 1 GTPU 1 NISx 3

Configuration Step 1

RNBC

NIP1 0 Optional NIP1 1 DMCU 34 ICSU 0 ICSU 1 ICSU 2 DMCU 0 DMCU 1 DMCU 2 MXU 2 PD20 MXU 3 DMCU 3 DMCU 4 DMCU 5 A2SU 1 NISx 0 GTPU 0 NISx 2

SFU 1

SFU 0

RNAC


= unit upgraded to newest variant

DN0638349

Configuration steps RNC196 step 6 and 7 with mandatory hardware changes

RNC196 step 6 RNC196 step 6 can be achieved with the following hardware changes. 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.

50


DN0938143 Issue 1-4



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 MX622C/-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 locations In RN4.0, upgrade CDSP-C units to CDSP-DH

FDU

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

NIP1

NI16P1A

RRMU

Remove excessive NIP1 units – 1 unit remains 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 standalone OMS is recommended.

Table 7

Minimum hardware level and configuration expansion for RNC196 step 6

RNC196 step 7 RNC196 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


A2SU

AL2S-D

Upgrade remaining 7 AL2S-B units to AL2S-D

GTPU

CCP18-C

Upgrade remaining 6 CCP10 units to CCP18C/CCP18-A

CCP18-A ICSU

CCP18-C CCP18-A

Table 8

DN0938143 Issue 1-4

Upgrade remaining 19 CCP10 units to CCP18C/CCP18-A



51


Functional unit


Minimum HW level

RRMU

Configuration expansion step 7 In RN4.0, removed and reconfigured as ICSU units

RSMU

CCP18-C

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

CCP18-A MXU

MX622-D

DMCU

CDSP-C

OMU

CCP18-A

OMU WDU HDD

HDS-B

OMS

MCP18-B

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

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 standalone OMS is recommended.

Table 8

7.1.4


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

52


DN0938143 Issue 1-4

Figure 21

DN0938319

DN0938143 Issue 1-4 TBUF TBUF

TBUF

PD20 MXU 3 DMCU DMCU A2SU -ICSU 25 GTPU NPS1P 0 NISx 2 TBUF

- /0NPGE(P) 0 NIP1 -NIP1 1 ICSU 0 ICSU 1 ICSU 2 DMCU DMCU 1 DMCU 2 MXU 2

EHU ) 1 (OMS) 1 (NEMU/OMS HDD HDD B: A: WDU 1 (OMU) OMU 1 20(OMU) ICSU WDU 1 ICSU 21 TBUF TSS3

55 NIS1P NISx NPGEP 1 7 7 27 NPGEP 3 DMCU NIS1P NISx -NISx 1 NPS1P 3 Optional ESA24 1 ICSU RRMU231 RSMU 1 14 MXU 1 PD20 15 MXU FDU (OMU) ICSU 24

SFU 1

TBUF

TSS3

NEMU 0 (OMS) ) 0 (NEMU/OMS B: HDD HDD A: WDU 0 (OMU) OMU 0 ICSU WDU 60 (OMU) ICSU 19

-NIS1P NISx 4 4 NPGEP 0 DMCU NISx 6 619 NPGEP 2 NIS1P -NISx 0 NPS1P 2 -A2SU RRMU220 ICSU RSMU 0 MXU 0 PD20 MXU EHU 1 ESA240 ESA12 /ESA24 ESA24 ESA12/

SFU 0

CPD80-B 0

PD20 MXU 5 DMCU DMCU DMCU A2SU ICSU ICSU 26 GTPU NPS1P 1 NISx 3

1 2 / NPGE(P) -NIP1 -NIP1 3 ICSU 3 ICSU 4 ICSU 5 DMCU 6 DMCU 7 DMCU 8 MXU 4

WCDMA RNC Engineering Description Cabinet and Subrack Descriptions for RNC196

CPD80-B 1

1 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

2

38

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

38

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

38

RNAC cabinet - RNC196 step 8

FRONT VIEW


53

1

1

7.1.5

54 TBUF

2

2

2 3

3

3

DN0938322

Figure 22 TBUF

4

4

4

4

5

5

5

5

6

6

6

6

7

7

7

7

8

8

8

8

PD20 MXU 7 DMCU DMCU DMCU A2SU ICSU 27 DMCU 2 NPS1P -DMCU TBUF


3

A2SU GTPU ICSU 29 DMCU 3 -NPS1P -DMCU TBUF

1

2

PD20 MXU 9 DMCU DMCU DMCU ICSU 28

3 6 / NPGE(P) -NIP1 7 NIP1 ICSU 10 ICSU 11 ICSU 12 DMCU DMCU 21 DMCU 22 MXU 8

1

PD20 MXU 11 DMCU DMCU DMCU A2SU GTPU ICSU 30 -DMCU 4/ NPGEP(P) 6 NPS1P -DMCU TBUF TBUF


CPD80-B 0

PD20 MXU 13 DMCU DMCU DMCU A2SU GTPU ICSU 31 DMCU 5/ NPGE(P) 7 -NPS1P -DMCU TBUF TBUF



CPD80-B 1

9 10 11 12 13 14 15 16 17 18 19

1

38

9 10 11 12 13 14 15 16 17 18 19

2

38

3 9 10 11 12 13 14 15 16 17 18 19

38

4 9 10 11 12 13 14 15 16 17 18 19

38

FRONT VIEW

RNBC cabinet - RNC196 step 8

Hardware Upgrade to RNC196 Step 8

An overview of the configuration for the RNC196 configuration step 8 is shown in the figure and sections below.


DN0938143 Issue 1-4



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 configuration 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 configuration 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.

DN0938143 Issue 1-4


55

56

1. 2. 3. 4.

Figure 23 38

Id:0900d80580751db8 Confidential 38 TBUF

TBUF

38

TBUF

NPS1P / NPGEP(P)

ICSU

TBUF

TBUF

ICSU NPS1P

38

TBUF

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

NPS1P/ NPGE(P)

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

ICSU

4 ICSU

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

PD20 MXU 7 DMCU 15 DMCU DMCU 16 DMCU 17 A2SU 3 GTPU 2 -DMCU 4 NIS1(P) -DMCU 6 NIS1(P)

TBUF

ICSU NPS1P

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

PD20 MXU 9 DMCU 23 DMCU 24 DMCU 7 GTPU A2SU 4 GTPU 3 DMCU 5 -NIS1P NIS1P -DMCU 7

CPD80-B 0

PD20 MXU 11 DMCU 31 DMCU 32 DMCU 33 A2SU 5 GTPU 4 NIS1(P) 8 / -DMCU NPGEP(P) 6 -DMCU 10 NIS1(P)

3 2 4 / NPGE(P) -NIP1 DMCU NIP1 5 25 ICSU 7 ICSU 8 ICSU 9 DMCU 12 DMCU 13 DMCU 14 MXU 6

TSS3

RNAC

PD20 MXU 13 DMCU 39 DMCU 40 DMCU 41 A2SU 6 GTPU 5 9/ DMCU -NIS1P NPGE(P) 7 DMCU 11 -NIS1P

2

3 6 - / NPGE(P) NIP1 -NIP1 7 ICSU 10 ICSU 11 ICSU 12 DMCU 20 DMCU 21 DMCU 22 MXU 8

TBUF

1

4 8 / NPGE(P) -NIP1 NIP1 9 35 DMCU ICSU 13 ICSU 14 ICSU 15 DMCU 28 DMCU 29 DMCU 30 MXU 10

TBUF

NEMU 0 (OMS) ) 0 (NEMU/OMS B: HDD HDD A: WDU 0 (OMU) 0 OMU ICSU WDU 60 (OMU) ICSU 19

CPD80-B 1

5 10 / NPGE(P) -NIP1 NIP1 1143 DMCU ICSU 16 ICSU 17 ICSU 18 DMCU 36 DMCU 37 DMCU 38 MXU 12

TBUF

EHU ) 1 (OMS) 1 (NEMU/OMS HDD HDD B: A: WDU 1 (OMU) 1 OMU 20(OMU) ICSU WDU 1 ICSU 21 TBUF TSS3

SFU 0 DMCU NISx 4 418 NPGEP 0 NIS1P DMCU NISx 6 619 NPGEP 2 NIS1P NISx A2SU0 7 NPS1P 2 A2SU 0 0 RRMU22 ICSU RSMU 0 MXU 0 PD20 MXU EHU 1 ESA240 ESA12 /ESA24 ESA24 ESA12/

SFU upgrade (SF10E)

TBUF

ICSU NPS1P

SFU 1 5 5 26 NPGEP 1 DMCU NISx NIS1P 7 7 27 NPGEP 3 DMCU NIS1P NISx NISx NPS1P 3 A2SU1 8 Optional ESA24 1 1 RRMU23 ICSU RSMU 1 14 MXU 1 PD20 Pd20 15 MXU FDU (OMU) ICSU GTPU 6

CPD80-B 0

TBUF

ICSU NPS1P

PD20 MXU 3 DMCU 3 DMCU 4 DMCU 5 DMCU A2SU 1 -NIS1(P) 0 GTPU 0 2 2 NISx NIS1(P)


IP upgrade (NP2GE-B)

PD20 MXU 5 DMCU 9 DMCU 10 DMCU 11 A2SU 2 NIS1(P) ICSU 1 GTPU 1 3 3 NISx NIS1(P)



RNBC CPD80-B 1

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


38

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

38

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



38

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

HSPA upgrade (CDSP-DH)

38

ICSU upgrade (CCP18-C)

NPS1(P) upgrade (NP8S1(P))

DN0938697

Configuration step RNC196 step 8 with mandatory hardware changes

Configuration step RNC196 step 8

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

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

RNC196 step 7 RNC196 step 7 with IP / Iu-PS not totally IP based RNC196 step 7 with IP / Iu-PS totally IP based RNC196 step 7 with all IP optional upgrade

DN0938143 Issue 1-4



5. RNC196 step 7 with HSPA optional upgrade 6. RNC196 step 7 with full CDSP-DH upgrade (all CDSP-Cs are replaced with CDSPDH) Functional unit

Minimum HW level


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 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.

a) The number depends on the desired configuration.

Table 9

7.2


Equipment in the Subracks The 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.

Unit type

A2SU

Table 10

DN0938143 Issue 1-4

Conf.

RNAC

RNBC

Min

Max

SR 1

SR 2

SR 3

SR 4

SRs 1–4

conf.

conf.

RNC196 step 5

1

—

1

1

1

3

7

RNC196 step 7

2

1

1

1

1

5

9

RNC196 step 8

—

—

—

—

—

—

—

Number of units in RNC196 subracks


57


Unit type

Conf.


RNAC

RNBC

Min

Max

SR 1

SR 2

SR 3

SR 4

SRs 1–4

conf.

conf.

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

RNC196 step 5

1

—

—

—

—

1

1

RNC196 step 7

—

1

—

—

—

1

1

RNC196 step 8

—

1

—

—

—

1

1

RNC196 step 5

—

—

1

1

1

2

6

RNC196 step 7

—

1

1

1

1–2 b)

4

8

RNC196 step 8

—

—

—

—

—

—

—

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

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

RNC196 step 5

1

—

—

—

—

1

1

RNC196 step 7

1

—

—

—

—

1

1

RNC196 step 8

0–1

—

—

—

—

—

1

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

RNC196 step 5

1

—

0–2

0–2

0–2

—

12

RNC196 step 7

1

—

—

—

—

1

1

RNC196 step 8

—

—

—

—

—

—

—

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

—

—

—

—

—

—

—

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

—

—

—

—

—

—

—

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

DMCU

EHU

GTPU

ICSU h)

MXU

OMS f)

OMS HDD e)

NIP1

NIS1

NIS1P

NPGE(P)

Table 10

58

Number of units in RNC196 subracks (Cont.)


DN0938143 Issue 1-4


Unit type

Conf.


RNAC

RNBC

Min

Max

SR 1

SR 2

SR 3

SR 4

SRs 1–4

conf.

conf.

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

—

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

NPS1(P)

OMU FDU h)

RNC196 step 5

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 standalone 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.)

Unit type

Configuration steps 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


ESA24


ESA12


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

DN0938143 Issue 1-4

Maximum number of units in RNC196 for each configuration step


59



Unit type

Configuration steps Step 1

Step 2

Step 3

OMS b)

Step 4

Step 5

Step 6

Step 7

Step 8

1

1

—


* OMS replaces NEMU as of RN3.0 OMS HDD b)


NIP1

4

6

8

NIS1

10

12


NIS1P

—


12

12

—

NPGE(P)

4

5

6

7

8

—

—

8

NPS1(P)

—

—

—

—

—

—

—

6

—

—

—

8

8

8

OMU


OMU WDU


OMU FDU


PD20

4

5

6

RRMU a)

7

8


—

RSMU


SFU


TBUF

6

TSS3

8

10

12

14

14

14

14


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..

Table 11

Maximum number of units in RNC196 for each configuration step (Cont.) For information on the capacities of the alternative configurations, see RNC196 capacity in Product Description for RNC196.

7.3 7.3.1

Upgrades and Expansions for RNC196 in RN5.0 Mandatory Upgrades for RNC196 Minimum hardware requirement for all configurations in RN5.0: the disk size for Integrated 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 RNC196 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.

60


DN0938143 Issue 1-4



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 7.4.1

Upgrades and Expansions for RNC196 in RN4.0 Mandatory Upgrades for RNC196 In 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 informaiton, see Hardware Expansion for RNC196.

7.4.2

Optional Upgrades for RNC196 •

•

•

•

DN0938143 Issue 1-4

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 Expansion for RNC196. SFU upgrade In 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 upgrade IP 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 (CDSPDH 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.


61

Functional Unit Descriptions


8 Functional Unit Descriptions 8.1

Functional Unit Categories The 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 Management 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). Notations The following notations are used throughout this chapter: • •

8.2

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).

Management, Control Computer and Data Processing Units The 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 Unit Purpose:

62

Although from the technical point of view DMCU is a signal processing unit, it performs some control plane functions besides its signal processing tasks. Its tasks are the following:

Id:0900d8058070322f Confidential

DN0938143 Issue 1-4



• • • • • • •

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

LAN / ETHERNET: MASTER SLAVE 1 SLAVE 2 SLAVE 3

LED RS-232 CONNECTORS: MASTER SLAVE 1 SLAVE 2 SLAVE 3

BACKPLANE: -TIMING & SYNC - HMS - POWER SUPPLY - MXU DN7088176

Figure 24

DN0938143 Issue 1-4

DMCU's interfaces - CDSP-DH


63



INTERFACES:

BACKPLANE: -

TIMING & SYNC HMS POWER SUPPLY MXU

SERVICE TERMINAL

CDSP

Figure 25

8.2.2

DN00256144

DMCU's interfaces - CDSP

GTPU, Gateway Tunneling Protocol Unit Purpose:

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)

Interfaces:

64



DN0938143 Issue 1-4



INTERFACES:

RESET SWITCH

SERVICE TERMINAL

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

DN70391828

Figure 26

DN0938143 Issue 1-4

GTPU's interfaces - CCP18-C


65



INTERFACES:

USB

RESET SWITCH

SERVICE TERMINAL

BACKPLANE: - HMS - SCSI (TO STORAGE DEVICES IN SUBRACKS) - LAN / ETHERNET - POWER FEED - JTAG/ISP DN0621415

Figure 27

66

GTPU's interfaces - CCP18-A


DN0938143 Issue 1-4



INTERFACES:

BACKPLANE: -

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

SERVICE TERMINAL

CCP10

Figure 28

8.2.3

DN00249775

GTPU's interfaces - CCP10

ICSU, Interface Control and Signalling Unit Purpose:

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

Plug-in unit:

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

Interfaces:

DN0938143 Issue 1-4



67



INTERFACES:

RESET SWITCH

SERVICE TERMINAL


DN70391828

Figure 29

68

ICSU's interfaces - CCP18-C


DN0938143 Issue 1-4



INTERFACES:

USB

RESET SWITCH

SERVICE TERMINAL


Figure 30

DN0938143 Issue 1-4

ICSU's interfaces - CCP18-A


69



INTERFACES:

BACKPLANE: -


SERVICE TERMINAL

CCP10

Figure 31

8.2.4

DN00249775

ICSU's interfaces - CCP10

Integrated OMS, Operation and Maintenance Server and its subunits 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 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 measurement 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.

70


DN0938143 Issue 1-4



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 supported.

INTERFACES: SVGA

USB

RESET SWITCH


Figure 32

Integrated OMS interfaces (MCP18-B)

Integrated OMS storage devices

DN0938143 Issue 1-4

Purpose:

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


71


Plug-in unit:


HDS-B Hard Disk Drive with SCSI Interface

Interfaces:

Small Computer System Interface (SCSI) INTERFACES:

BACKPLANE: - HMS - POWER SUPPLY - SCSI

LED

DN00256429

Figure 33

Integrated OMS storage device interfaces

Configuration and redundancy principles of integrated OMS storage devices Integrated 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.

72


DN0938143 Issue 1-4



RNAC 2

3

4

5

6

7

8

9 10 11 12 13 14 15 16 17 18 19

WDU 0 (OMS)

1

OMS RNC SUBRACK 1

SCSI 0

SCSI 1

WDU 1 (OMS)

RNC SUBRACK 2

DN0938779

BUS END POINT

Figure 34

8.2.5

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

ESA24, Ethernet Switch RNC 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

Type:


Plug-in unit:

ESA24 Ethernet Switch

Capacity/ Performance Interfaces:

DN0938143 Issue 1-4

24 physical 10/100 Base-T Ethernet interfaces

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


73



INTERFACES:

LAN

SERVICE TERMINAL

BACKPLANE: - TIMING & SYNC (NOT USED) - HMS (NOT USED) - POWER SUPPLY - LAN ESA24

Figure 35

8.2.6

DN03451956

ESA24's interfaces

ESA12, Ethernet Switch RNC 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

Type:


Plug-in unit:

ESA12 Ethernet Switch

Capacity/ Performance Interfaces:

74

12 physical 10/100 Base-T Ethernet interfaces

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


DN0938143 Issue 1-4



INTERFACES:

BACKPLANE: - TIMING & SYNC (NOT USED) - HMS (NOT USED) - POWER SUPPLY

12 x LAN / ETHERNET

ESA12

Figure 36

8.2.7

DN02179274

ESA12's interfaces

OMU, Operation and Maintenance Unit and Its Subunits Purpose:

OMU handles all RNC's crucial upper-level system maintenance functions, such as hardware configuration management, Hardware Management 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.

DN0938143 Issue 1-4

Redundancy:

2N

Type:

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


75



Plug-in unit:

CCP18-A / CCP10 Control Computer, Pentium M (CCP18-A) Control Computer, Pentium III (CCP10)

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

INTERFACES:

USB

RESET SWITCH

SERVICE TERMINAL


Figure 37

76

OMU's interfaces - CCP18-A


DN0938143 Issue 1-4



INTERFACES:

BACKPLANE: -

TIMING & SYNC HMS POWER SUPPLY MXU SCSI LAN

SERVICE TERMINAL

CCP10

Figure 38

DN00249799

OMU's interfaces - CCP10

OMU's storage devices Purpose:

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: Interfaces:

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

Small Computer System Interface (SCSI) Universal Serial BUS (USB, CCP18-A)

DN0938143 Issue 1-4


77



INTERFACES: BACKPLANE: - HMS - POWER SUPPLY - SCSI

MDS /-A

HDS /-A

DN02179305

Figure 39

OMU's storage devices' interfaces

Configuration and redundancy principle of OMU's storage devices The 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 switchover, two USB memory sticks are needed: one for each OMU. The connection principle for the memory units is illustrated in the figures below.

78


DN0938143 Issue 1-4



RNAC

1

2

3

4

5

6

7

8

9 10 11 12 13 14 15 16 17 18 19

RNAC SUBRACK 1

OMU 0

WDU 0 (OMU)

SCSI 0

SCSI 1

1

2

3

4

5

6

7

8

9 10 11 12 13 14 15 16 17 18 19

DN0640747

Figure 40

DN0938143 Issue 1-4

OMU 1

WDU 1 (OMU)

RNAC SUBRACK 2

BUS END POINT

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


79



RNAC 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

WDU 0 (OMU)

OMU 0

1

RNC SUBRACK 1

DN99573042

Figure 41

8.2.8

WDU 1 (OMU)

RNC SUBRACK 2

SCSI 1

OMU 1

FDU (OMU)

SCSI 0

BUS END POINT

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

RRMU, Radio Resource Management Unit Purpose:

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) Control Computer, Pentium III (CCP10)

Interfaces:

80



DN0938143 Issue 1-4



INTERFACES:

RESET SWITCH

SERVICE TERMINAL


DN70391828

Figure 42

DN0938143 Issue 1-4

RRMU's interfaces - CCP18-C


81



INTERFACES:

USB

RESET SWITCH

SERVICE TERMINAL


Figure 43

82

RRMU's interfaces - CCP18-A


DN0938143 Issue 1-4



INTERFACES:

BACKPLANE: -


SERVICE TERMINAL

CCP10

Figure 44

8.2.9

DN00249775

RRMU's interfaces - CCP10

RSMU, Resource and Switch Management Unit Purpose:

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: • • •

DN0938143 Issue 1-4

Supervision and management of the DMCU units, including the necessary software upload procedures Allocation of the DSPs and associated computer resources to different tasks, such as microdiversity combining and data traffic Management of the ATM connections within DMCU

Redundancy:

2N

Type:

Computer unit


83



Plug-in unit:

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

Interfaces:


INTERFACES:

RESET SWITCH

SERVICE TERMINAL


DN70391828

Figure 45

84

RSMU's interfaces - CCP18-C


DN0938143 Issue 1-4



INTERFACES:

USB

RESET SWITCH

SERVICE TERMINAL


Figure 46

DN0938143 Issue 1-4

RSMU's interfaces - CCP18-A


85



INTERFACES:

BACKPLANE: -


SERVICE TERMINAL

CCP10

Figure 47

8.3

DN00249775

RSMU's interfaces - CCP10

Switching and Multiplexing Units Switching 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.

86


DN0938143 Issue 1-4



MXU's connections within the RNC The 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.

DN0938143 Issue 1-4


87



2 pcs

A2SU

1 3-8

1 pcs

RSMU

1 pcs

RRMU

MXU

NIP 1

0-1 pcs ***

ICSU

3 pcs

DMCU

DMCU

A2SU

1 pcs

5-7 pcs* ICSU

2 pcs 2 pcs

MXU SFU

DMCU

GTPU 1 pcs

OMU

1 pcs

A2SU

2

1-2 pcs **

2-12 pcs NIS 1

1 pcs

RSMU

1 pcs

RRMU

2 pcs

ICSU

2 pcs

DMCU

1 pcs

MXU

OMU

* 5 DMCUs in RNBC Sr2 ** 2 GTPUs in RNBC Sr2 *** 1 NIP1 in RNAC Sr3

DN01128575

Figure 48

8.3.1

ATM connections to SFU - RNC450

A2SU, AAL2 Switching Unit Purpose:

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 minipackets. 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:

88

SN+


DN0938143 Issue 1-4



Type:

Signal processing unit

Plug-in unit:

AL2S-D / AL2S-B AAL type 2 switching unit

Interfaces:


LAN / ETHERNET: MASTER SLAVE 1 SLAVE 2 SLAVE 3

LED RS-232 CONNECTORS: MASTER SLAVE 1 SLAVE 2 SLAVE 3

BACKPLANE: -TIMING & SYNC - HMS - POWER SUPPLY - MXU DN7088176

Figure 49

DN0938143 Issue 1-4

A2SU's interfaces - AL2S-D


89



INTERFACES: BACK PLANE: -

TIMING & SYNC HMS POWER SUPPLY MXU

SERVICE TERMINAL

AL2S-B

Figure 50

8.3.2

DN00249833

A2SU's interfaces - AL2S-B

MXU, Multiplexer Unit Purpose:

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, performance 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: • • •

90

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


DN0938143 Issue 1-4



• • •

Network interfaces A2SU Connection between the passive MXU via the active one to OMU (for OAM purposes)

INTERFACES: BACKPLANE: - TIMING & SYNC - HMS - POWER FEED - SFU - TRIBUTARY UNITS - REDUNDANCY INTERFACE - BOUNDARY SCAN INTERFACE LED

SERVICE TERMINAL

DN70170272

Figure 51

DN0938143 Issue 1-4

MX1G6/ MX1G6-A

MXU's interfaces - MX1G6 and MX1G6-A


91



INTERFACES: BACKPLANE: - TIMING & SYNC - HMS - POWER FEED - SFU - TRIBUTARY UNITS - SFU UNIT COMPUTER - OMU FROM PASSIVE MUX VIA THE ACTIVE ONE LED

SERVICE TERMINAL

MX622

Figure 52

8.3.3

DN02179344

MXU's interfaces - MX622

SFU, Switching Fabric Unit Purpose:

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 pointto-point and point-to-multipoint connection topologies, as well as differentiated 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: • • •

92

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)


DN0938143 Issue 1-4



LED

ETH SER

DN70166955

Figure 53

DN0938143 Issue 1-4

SF20H

SFU's interfaces - SF20H


93



INTERFACES: BACKPLANE: - TIMING & SYNC - HMS - POWER SUPPLY - SWITCH PORT TO TRIBUTARY UNITS - OMU (FROM UNIT COMPUTER VIA MXU) LAN (TESTING ONLY) SERVICE TERMINAL

SFP (SFPIF2G5)

DN70498095

Figure 54

94

SFU's interfaces - SF10E


DN0938143 Issue 1-4



INTERFACES: BACKPLANE: - TIMING & SYNC - HMS - POWER SUPPLY - SWITCH PORT TO TRIBUTARY UNITS - OMU (FROM UNIT COMPUTER VIA MXU)

LAN SERVICE TERMINAL

SF10

Figure 55

8.4

DN02179356

SFU's interfaces - SF10

Network Interface Units These units serve as the trunk network interfaces of the network element and execute physical layer and ATM layer functions, such as policing, statistics, Operation Administration Maintenance (OAM), buffer management, and scheduling. The category comprises 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.

DN0938143 Issue 1-4


95


8.4.1


NIP1 NIP1 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 bandwidth of: • • Interfaces:

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

ATM interface to MXU Clock reference output to TSS3/-A

INTERFACES: LAN (NOT USED)

BACKPLANE: -

TIMING & SYNC HMS POWER SUPPLY MXU E1 / T1 / JT1 CLOCK REFERENCE OUTPUT TO TSS3

SERVICE TERMINAL

NI16P1A

Figure 56

96

DN02179492

NIP1's interfaces


DN0938143 Issue 1-4


8.4.2


NIS1 / NIS1P Purpose:

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

Type:

Interface unit

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

INTERFACES: STM-1

BACKPLANE: -

TIMING & SYNC HMS POWER SUPPLY SFU CLOCK REFERENCE OUTPUT TO TSS3

LAN (NOT USED) SERVICE TERMINAL

NI4S1-B

Figure 57

8.4.3

NPS1 / NPS1P Purpose:

DN0938143 Issue 1-4

DN02179368

NIS1's interfaces

NPS1(P) provides SDH STM-1/STM-4 interfaces and an RJ45 connector, and handles multiprotocol packet processing at wire speed and network connectivity.


97



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)

Type:

Interface unit

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 Note that RN4.0 SW does not support STM-4 interface.

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 Note that RN4.0 SW does not support STM-4 interface. Interfaces:

Fast Ethernet physical layer interface Switch fabric interface Timing and synchronization interface Hardware management system interface ATM interface to SFU CLASS 1 LASER PRODUCT IEC/EN 60825-1

INTERFACES: BACKPLANE:

1

Tx Rx

2

Tx Rx

3

STM-1 / STM-4*

-

TIMING & SYNC HMS POWER SUPPLY SFU CLOCK REFERENCE OUTPUT TO TSS3 - LAN 1-5

Tx Rx

4 5 6 7 8

Tx Rx Tx

STM-1

Rx Tx Rx Tx Rx Tx Rx

SERVICE TERMINAL

* STM-4 interface cannot be used

98

DN70550849

NP8S1-B, NP8S1-A, NP8S1

Figure 58

NPS1(P) interfaces


DN0938143 Issue 1-4


8.4.4


NPGE / NPGEP Purpose:

NPGE(P) provides Ethernet interfaces and handles multiprotocol packet processing at wire speed.

Redundancy:

NPGE: none NPGEP: 2N

Type:

Interface unit

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

DN0938143 Issue 1-4

NPGE(P) interfaces


99


8.5


Timing, Power Distribution and Hardware Management Subsystems The 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: • •

8.5.1

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

TBU, Timing and Hardware Management Bus Unit The 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:

100

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-


DN0938143 Issue 1-4



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 independently 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 GR1244 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

DN0938143 Issue 1-4


101


Figure 60


TSS3/-A's interfaces

TBUF, Timing Buffer Purpose:

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: • • •

102

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


DN0938143 Issue 1-4



HMS interface INTERFACES: BACKPLANE: - ONE CLOCK REFERENCE INPUT FROM TSS3 OR TBUF - ONE TIMING & SYNC OUTPUT TO SUBRACK TIMING BUS - ONE TIMING & SYNC OUTPUT TO ANOTHER TBUF - HMS

TBUF

Figure 61

DN02179371

TBUF's interfaces

Connection principle and redundancy for the timing and synchronisation distribution 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.

DN0938143 Issue 1-4


103



RNAC

RNBC

RNAC SUBRACK1

RNBC SUBRACK1

RNAC SUBRACK2

RNBC SUBRACK2

RNAC SUBRACK3

RNBC SUBRACK3

RNAC SUBRACK4

RNBC SUBRACK4

DN70680727

In RNC2600/Step1 HMS BUS 0 HMS BUS 1


BUS STARTING POINT

Figure 62

8.5.2

Connection principle of the duplicated clock distribution bus

HMS, Hardware Management Subsystem The 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

104


DN0938143 Issue 1-4



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. CABINET 1 HMMN OMU 0 HMSS

CABINET 2

SUBRACK 1 PIU HMSS

PIU HMSS

SUBRACK 1

PIU HMSS

PIU HMSS

HMSB 0

PIU HMSS

PIU HMSS

HMSB 0

TSS3

TBUF

BACKPLANE BUS

HMSS

BACKPLANE BUS

HMSS

HMSB 1

HMSB 1

TBUF

TBUF

BACKPLANE BUS

HMSS

HMMN OMU 1 HMSS

BACKPLANE BUS

HMSS

SUBRACK 2 PIU HMSS

PIU HMSS

PIU HMSS

HMSB 0 TBUF

BACKPLANE BUS

HMSS

HMSB 1 TSS3

BACKPLANE BUS

HMSS

SUBRACK 4

SUBRACK 4

PIU HMSS

PIU HMSS

PIU HMSS

PIU HMSS

HMSB 0 TBUF

HMSS

HMSS

PIU HMSS

HMSB 0 TBUF

BACKPLANE BUS

HMSS

HMSB 1 TBUF

PIU HMSS BACKPLANE BUS

HMSB 1 TBUF

BACKPLANE BUS

HMSS

BACKPLANE BUS

TO OTHER RACKS

DN99573245

HMSB = HMS BRIDGE HMSS = HMS SLAVE NODE HMMN = HARDWARE MANAGEMENT MASTER NODE

Figure 63

Block diagram of the HMS subsystem

Connection principle and redundancy of the HMS bus RNC has also two mutually redundant hardware management buses, which are implemented 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.

DN0938143 Issue 1-4


105



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 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 connection principle of the HMS buses in the network element is shown in the figure below. RNAC

RNAC SUBRACK1

RNBC SUBRACK1

RNAC SUBRACK2

RNBC SUBRACK2

RNAC SUBRACK3

RNBC SUBRACK3

RNAC SUBRACK4

RNBC SUBRACK4

DN70680715

Figure 64

106

RNBC



Connection principle of the duplicated HMS bus


DN0938143 Issue 1-4


8.5.3


Power Distribution Subsystem The 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 independent 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 duplicated 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

DN0938143 Issue 1-4


107



FUSES

LED

DN00256417

Figure 65

PD30/PD20's interfaces

Power distribution principle and redundancy To 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 batteries/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

108


DN0938143 Issue 1-4



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 batteries/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 distribution 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.

DN0938143 Issue 1-4


109



Protection area of the main fuse

Protection area of the circuit breaker at the cabinet level

-UB2 -UB2 Main fuses or circuit breakers in power system

DC

BOV 0

Filter

DC UB2

UB2

SMD fuses on PCB

Glass tube fuses in front panel

Terminal blocks and circuit breakers

BOV 1 Power distribution plug-in unit

Cabinet

Protection area of the fuse at the plug-in unit level

UB1

UB1

-UB1

-UB1

Protection area of the glass tube fuse at the subrack level

Backplane

Plug-in unit

Subrack

dn02180104

Figure 66

110

General power distribution principle for RNC


DN0938143 Issue 1-4



B 0V B 0V

ENABLE = INPUT CIRCUIT

UO 1 GND

= ON/OFF

UB 1 UB 2

DC/DC CONVERTER STRUCTURE IN A PLUG-IN UNIT

ENABLE =

UO 2 GND

= ON/OFF POWER CONTROL FROM HMS NODE

ALARM TO HMS NODE

ALARM CIRCUIT

dn02179535

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 Unit Purpose:

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 unit The 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 indicator The CAIND/-A is located on top of the RNAC cabinet and provides a visual alarm indicating the network element with a fault.

DN0938143 Issue 1-4


111

Interfaces to the Environment


9 Interfaces to the Environment RNC 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 recommended. 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 Interfaces The 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.

112

Id:0900d805807292ab Confidential

DN0938143 Issue 1-4



B

-UB2 +UB2 -UB1

+UB1

A 2

2

DC/I DN05158732

(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

DN0938143 Issue 1-4

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


113



-UB2 B0V -UB1

1

2

1

B0V

2

DC/C DN05160839

(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

114

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


DN0938143 Issue 1-4



For optional ETS 300 253 +UB2 B0V grounding +UB1

CPD80-B 1 -UB2 +UB2

-UB1 +UB1 CPD80-B 0

CPD80-B 1 -UB2 +UB2

Figure 70

DN0938143 Issue 1-4

DN02180143 -UB1 +UB1 CPD80-B 0 Power supply interfaces of CPD80-B with two connection alternatives and optional ETS grounding


115



DC/I

DC/C +UB1

+UB0 -UB0 -UB1

+UB0 -UB0

+UB1 -UB1

DN01154291

REAR SIDE

Figure 71

9.2

REAR SIDE

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

PDH TDM Interfaces The 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 Interfaces The 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 Interfaces The 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 connections.

116


DN0938143 Issue 1-4


9.5


External HW Alarm Interfaces The external hardware alarms interfaces are located on the EHAT plug-in unit. The connections can be routed through the alarms connector panel or unit CPAL-A or CPSALB / 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 Interfaces The 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 interface 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 Interfaces The 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 practises. 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 Interfaces RNC's service terminal interfaces are intended to be used for temporary service operations, for example, debugging. For more information, see section Functional unit descriptions.

DN0938143 Issue 1-4


117

RNC 2600 Engineering

Recommend Documents