BSC_PCU HW Implementation for PS Traffic (GPRS_EDGE)_Ver1_9

DN09114009BSC/PCUHWImplementationforPStraffic(GPRS/EDGE)Copyright2013NokiaSolutionsandNetworks.Allrightsreserved.CONFIDENTIALAPPROVED1.91 (149)

BSC/PCU HWImplementation for PStraffic (GPRS/EDGE)Release Delivery: HW UpgradeProduct Family: Radio ControllersProduct:BSC3i 1000/2000, Flexi BSCRelease: S16 onwards

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of itsproducts and services. We would like to encourage you as our customers and users to join us inworking towards a cleaner, safer environment. Please recycle product packaging and follow therecommendations for power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental serviceswe offer, please contact us at Nokia Solutions and Networks for additional information.


Table of Contents1 Purpose .................................................................................................................................................. 62 Scope of applications .............................................................................................................................. 73 Using the document ................................................................................................................................ 8

3.1 General info ....................................................................................................................................................... 83.2 Upgrade macro .................................................................................................................................................. 8

3.2.1 Structure ...................................................................................................................................... 83.2.2 Communication ............................................................................................................................ 93.2.3 Log files ....................................................................................................................................... 9

4 Introduction ........................................................................................................................................... 124.1 PCU Plug-in unit variants ................................................................................................................................. 16

4.1.1 PCU, Packet Control Unit (C72070) ............................................................................................ 164.1.2 PCU_S, Packet Control Unit, S-Variant (C74840) ........................................................................ 174.1.3 PCU_T, Packet Control Unit, T-Variant (C105254) ...................................................................... 174.1.4 PCU2_U, Packet Control Unit, U-Variant (C10108872) ................................................................ 174.1.5 PCU_B, Packet Control Unit, B-Variant (C104512) ...................................................................... 174.1.6 PCU2_D, Packet Control Unit, D-Variant (C108407) .................................................................... 174.1.7 PCU2_E, Packet Control Unit, E-Variant (C110629) .................................................................... 18

4.2 BSCi Hardware ................................................................................................................................................ 184.3 BSC2i Hardware .............................................................................................................................................. 184.4 BSC3i 660 Hardware ....................................................................................................................................... 194.5 BSC3i 1000/2000 Hardware ............................................................................................................................. 204.6 Upgraded Flexi BSC Hardware ........................................................................................................................ 214.7 New delivery Flexi BSC Hardware .................................................................................................................... 22

5 Pre-requirements .................................................................................................................................. 245.1 Pre-requirements & Actions needed prior upgrade ............................................................................................ 245.2 Restrictions ..................................................................................................................................................... 245.3 Needed documentation .................................................................................................................................... 255.4 Needed equipment .......................................................................................................................................... 255.5 HIT and upgrade macros.................................................................................................................................. 25

5.5.1 System requirements for HIT ...................................................................................................... 255.5.2 Installing HIT .............................................................................................................................. 255.5.3 Installing HIT upgrading macros .................................................................................................. 255.5.4 HIT settings................................................................................................................................ 265.5.5 Connection settings .................................................................................................................... 275.5.6 Starting the HIT application / macro execution ............................................................................. 46

6 Fallback copying of the current package ................................................................................................ 547 BSC configuration printout (pre-check) .................................................................................................. 558 Preparation for the upgrade ................................................................................................................... 56

8.1 GSWB extension ............................................................................................................................................. 568.2 Power upgrade to PSC6-D ............................................................................................................................... 588.3 Command calendar.......................................................................................................................................... 588.4 Check and copy databases to disks .................................................................................................................. 598.5 Licence installation and feature activation ......................................................................................................... 59

9 PCU (GPRS/EDGE) HW upgrade.......................................................................................................... 619.1 BSCi BCSU Unit Upgrade ................................................................................................................................ 63

9.1.1 PCU Track 9 PCM Configuration ................................................................................................ 649.1.2 BSCi PCU PCM cables, Track 9 ................................................................................................. 65

9.2 BSC2i BCSU Unit upgrade ............................................................................................................................... 679.2.1 PCU Track 9 PCM Configuration in BSC2i .................................................................................. 689.2.2 PCU Track 8 PCM Configuration in BSC2i .................................................................................. 699.2.3 BSC2i PCU PCM-Cables, track 9................................................................................................ 699.2.4 BSC2i PCU PCM-Cables, Track 8 .............................................................................................. 70

9.3 BSC3i 660 (GSWB) BCSU Unit upgrade .......................................................................................................... 719.3.1 PCU_B Track 6 PCM Configuration in BSC3i .............................................................................. 729.3.2 PCU_B Track 7 PCM Configuration in BSC3i .............................................................................. 73


9.3.3 PCU2_D Track 6 PCM Configuration in BSC3i ............................................................................ 749.3.4 PCU2_D Track 7 PCM Configuration in BSC3i ............................................................................ 769.3.5 PCU2_E Track 6 PCM Configuration in BSC3i ............................................................................ 779.3.6 PCU2_E Track 7 PCM Configuration in BSC3i ............................................................................ 77

9.4 BSC3i 660 (GSW1KB) BCSU Unit upgrade ...................................................................................................... 789.4.1 PCU_B Track 6 PCM Configuration in BSC3i 660 ....................................................................... 799.4.2 PCU_B Track 7 PCM Configuration in BSC3i 660 ....................................................................... 819.4.3 PCU2_D Track 6 PCM Configuration in BSC3i 660 ..................................................................... 829.4.4 PCU2_D Track 7 PCM Configuration in BSC3i 660 ..................................................................... 839.4.5 PCU2_E Track 6 PCM Configuration in BSC3i 660...................................................................... 849.4.6 PCU2_E Track 7 PCM Configuration in BSC3i 660...................................................................... 84

9.5 BSC3i 1000/2000 BCSU Unit upgrade .............................................................................................................. 859.5.1 PCU2_D Track 3 PCM Configuration in BSC3i 1000/2000 ........................................................... 879.5.2 PCU2_D Track 4 PCM Configuration in BSC3i 1000/2000 ........................................................... 889.5.3 PCU2_D Track 5 PCM Configuration in BSC3i 1000/2000 ........................................................... 909.5.4 PCU2_E Track 3 PCM Configuration in BSC3i 1000/2000 ........................................................... 919.5.5 PCU2_E Track 4 PCM Configuration in BSC3i 1000/2000 ........................................................... 929.5.6 PCU2_E Track 5 PCM Configuration in BSC3i 1000/2000 ........................................................... 939.5.7 PCU_B Track 6 PCM Configuration in BSC3i 1000/2000 ............................................................. 949.5.8 PCU_B Track 7 PCM Configuration in BSC3i 1000/2000 ............................................................. 959.5.9 PCU2_D Track 6 PCM Configuration in BSC3i 1000/2000 ........................................................... 979.5.10 PCU2_D Track 7 PCM Configuration in BSC3i 1000/2000 ........................................................... 989.5.11 PCU2_E Track 6 PCM Configuration in BSC3i 1000/2000 ......................................................... 1009.5.12 PCU2_E Track 7 PCM Configuration in BSC3i 1000/2000 ......................................................... 100

9.6 Upgraded Flexi BSC BCSU Unit upgrade ....................................................................................................... 1019.6.1 PCU2_D Track 3 PCM Configuration in upgraded Flexi BSC ..................................................... 1039.6.2 PCU2_D Track 4 PCM Configuration in upgraded Flexi BSC ..................................................... 1049.6.3 PCU2_D Track 5 PCM Configuration in upgraded Flexi BSC ..................................................... 1059.6.4 PCU2_E Track 3 PCM Configuration in upgraded Flexi BSC ..................................................... 1069.6.5 PCU2_E Track 4 PCM Configuration in upgraded Flexi BSC ..................................................... 1079.6.6 PCU2_E Track 5 PCM Configuration in upgraded Flexi BSC ..................................................... 1079.6.7 PCU2_D Track 6 PCM Configuration in upgraded Flexi BSC ..................................................... 1089.6.8 PCU2_D Track 7 PCM Configuration in upgraded Flexi BSC ..................................................... 1099.6.9 PCU2_E Track 6 PCM Configuration in upgraded Flexi BSC ..................................................... 1109.6.10 PCU2_E Track 7 PCM Configuration in upgraded Flexi BSC ..................................................... 111

9.7 New delivery Flexi BSC BCSU Unit upgrade ................................................................................................... 1119.7.1 PCU2_E Index 8 PCM Configuration in new delivery Flexi BSC ................................................. 1139.7.2 PCU2_E Index 10 PCM Configuration in new delivery Flexi BSC ............................................... 1149.7.3 PCU2_E Index 12 PCM Configuration in new delivery Flexi BSC ............................................... 1149.7.4 PCU2_E Index 4 PCM Configuration in new delivery Flexi BSC ................................................. 1159.7.5 PCU2_E Index 6 PCM Configuration in new delivery Flexi BSC ................................................. 116

10 PEP Interface creation......................................................................................................................... 11711 ET HW upgrade .................................................................................................................................. 118

11.1 BSC2i ET HW upgrade .................................................................................................................................. 11811.2 ET5C-4 Cartridge........................................................................................................................................... 11811.3 BSC2i ET Configuration ................................................................................................................................. 12011.4 BSC2i ET PCM-Cables .................................................................................................................................. 123

12 Actions after upgrade & Post conditions .............................................................................................. 12412.1 Implementation of the new optional feature ..................................................................................................... 12412.2 PCU2 Scheduling weight parameters ............................................................................................................. 12412.3 Check and update PCU boot software ............................................................................................................ 125

12.3.1 Chorus PCU boot SW versions ................................................................................................. 12512.3.2 PCU2 boot SW versions ........................................................................................................... 126

12.4 Cartridge Marking Labels ............................................................................................................................... 12712.5 BSC configuration printout (post-check) .......................................................................................................... 12712.6 Fallback copying of the current package ......................................................................................................... 128

13 Appendix ............................................................................................................................................. 12913.1 Appendix1: SW64B Jumper settings ............................................................................................................... 12913.2 Appendix2: PCU, PCU_S and PCU_T Jumper settings ................................................................................... 130


13.3 Appendix3: PCU2_U Jumper settings ............................................................................................................. 13213.4 Appendix4: PCU_B Jumper settings ............................................................................................................... 13413.5 Appendix5: PCU2_D Jumper settings ............................................................................................................. 13613.6 Appendix6: PCU2_E Jumper settings ............................................................................................................. 13913.7 Appendix7: EURO Connector is connected to PCU card ............................................................................. 14113.8 Appendix8: Updating the boot packages of PCU, PCU_S, PCU_T, PCU_B pre-processor PIU(s) ..................... 14213.9 Appendix9: Updating the boot packages of PCU2 pre-processor PIU(s) .......................................................... 146

Contact:

Contact your local Nokia Solutions and Networks support


Summary of changes:

1.0-0 1st approved version1.1-0 Added CR75 details1.2-0 Added connection settings for Linux in chapter 5.5.5.2.1.3-0 Added note regarding COM issue in HIT3.3 in chapter

5.5.5.1.2 and 5.5.5.2.2.1.4-0 Updated Memory requirements in Flexi BSC and BSC3i

in chapter 5.1.Also modified the contents in chapter 5.2.1.5-0 Removed note regarding COM issue from chapters

5.5.5.1.2 and 5.5.5.2.2.Also updated the hit version as3.4-0.

1.6-0 Added PCU2E strapping details for BSC3i 1000/2000,BSC3i 660 GSW1KB, BSC3i 660 GSWB in appendix 6.

1.7-0 Updated appendix 6 by adding PCU2_E PCM interfaceconfiguration pinheader details of all BSC variants.

1.8-0 Correction for PR NA05452928 updated in chapter 9.5.1.9-0 The amount of PCU2-Es in BSCU updated in chapter 4.


1 PURPOSE

This document describes the implementation of the Nokia DX200 GPRS/EDGE BSC Hardware . TheGPRS/EDGE Feature's functional descriptions are included in the documentation (NED). The Plug-in unit jumpersettings are described in the document; Jumper Settings of the Plug-in Units in BSC3i and in TCSM3i.

The GPRS/EDGE Network Integration is not within the scope of this document. For details on how to integrate theGb-interface to the SGSN, as well as how to set up the radio network for the GPRS/EDGE use, see NEDdocumentation.NOTE! The BSCi and BSC2i (M92 HW) are not supported in S16.1 or newer releases


2 SCOPE OF APPLICATIONS

This document applies to BSC running with S16 software level onwards. Upgrade procedure allows toinstall/replace/remove any type of PCU plug-in unit in all BSC models.With the procedure documented, the upgrade may be done locally at the BSC site or remotely via NetAct.Following connection types are supported:

x Local connection (COM)x Telnetx SSHx Via Netact (SSH)

Note: in S16 level onwards, via Netact (SSH) is only allowed.

All existing PCU units (PCU1, PCU2) can be used with the basic SW release. As with earlier SW releases thePCU OSW is controlled by license keys.


3 USING THE DOCUMENT

3.1 General info

The BSC/PCU HW implementation for PS traffic (GPRS/EDGE) can be done using the HIT (Holistic IntegrationTester) software tool. Optional way is to make the upgrade manually by following this documentation.

The HIT software automates most of the tasks necessary for the software or hardware upgrade. The HIT softwareand the instructions are included in this manual. It is recommended that the HIT User's Manual is gone throughbefore starting the program.

When using the HIT for upgrading BSC, these instructions should be followed for a more detailed description ofthe different phases, which take place during the upgrade. The upgrade macro menu dialog is designed to followclosely this document.

NOTE: The commands executed by the HIT macro do not always match exactly with the commands presented inthe manual. This is because sometimes the automated tasks of the HIT macro require more commands anddifferent command syntaxes, than are presented in the manual.

When using the HIT, the MML commands are executed automatically. It is not necessary to type any commandsuntil it is specifically requested by HIT.

3.2 Upgrade macro

3.2.1 Structure

All the SW & HW macros are gathered under one main macro (UPGMAIN.HIT), from which the wanted SW / HWupgrade can be selected. Regardless of which macro (SW or HW upgrade) is wanted to run, the user alwaysstarts with the same main macro.Example of macro structure:UPGMAIN.HIT

o Select wanted upgrade:

SOFTWARE UPGRADES

x SW upgrade S15 -> S16

x

HARDWARE UPGRADES


x HW upgrade 1

x HW upgrade 2

x

Under each upgrade / tool there is an upgrade specific menu which describes the steps which can be executedindividually:SW upgrade S15 -> S16 (selected from main menu)

o Select wanted step

Make fallback

Check Firmware

Make pre-check

Copy SW

When a step is completed successfully, the user is brought back to upgrade menu and a Done. -sign will appearat beginning of the name of the step. If step execution fails for some reason, macro stops and user can correctthe error manually and then continue macro execution normally.

If macro or computer freezes totally during step execution and macro needs to be restarted, user cannot re-runthe incomplete step from the menu. In this case, the user must complete that certain step manually, using thisdocumentation as guide. When the step has been completed manually, user can continue the macro executionfrom next available step. Note, that in the upgrade menu, there will be Man. sign instead of Done. sign atbeginning of name of the manually executed step.

Note!Once, user enters from main menu to upgrade menu, only way to get back to the main menu is to restartwhole macro.

3.2.2 Communication

The macro communicates with user by using the HIT Pop-up windows.

- Asking the user to give information (e.g. paths, file names, etc.) & other userselections.

- Error situations

- Manual execution steps (i.e. when macro expects user to do some actionsmanually (e.g. copy some files, install new HW /cabling etc.)

- Macro completion

3.2.3 Log files

The upgrade macro provides different log files, from where the user can verify the executed steps in macro andthe success of the different steps & commands executed in the macro. There are three different kind ofinformation / log files:

- Log file from HIT Response window (.log)


o This log contains all the information of the macro execution (each MMLcommand and the whole output of the macro execution)

o User can accept the default log-file name or specify a new one. Macrogives following pop-up window for selection:

o Macro writes separate log files for following steps:x Configuration printout (PRE)

x Firmware

x Plug-in unit software upgrade

x Safecopy

x Transfer software to BSC

x Configuration printout (PRE)

o The same information can be found from both from a main log fileand from these specified smaller log files.

- Log file from HIT Message window (Messages.log)

o The contents of the message window are saved after macro execution.


o Information about errors in macro execution- Log print of HIT (TimeTable.log) This is a shorter description of the execution

of the macro, and the log contains information about:

o Starting an execution step in macroo Execution status (Done).o Completion of execution step in macro

If macro execution is stopped for some reason, the log files still remain in the folder the user has specified. Whenmacro execution is started again, the log writing is continued from the end of existing log files. All previouslywritten log information remains intact and nothing is overwritten.


4 INTRODUCTION

NOTE! The BSCi and BSC2i ( M92 HW) are not supported in S16.1 or newer releasesThe BSC/PCU HW implementation consists of the following steps:

- Fallback copying of the current software

- BSC configuration printout (pre-check)

- Preparation for the upgrade

o GSWB extension (only for BSC2i)o Power upgrade to PSC6-D (only for BSC3i1000 or upgraded Flexi

BSC)

o Command calendaro Check and copy databases to diskso Licence installation and feature activation

- PCU (GPRS/EDGE) HW upgrade

o BSCi BCSU unit upgradeo BSC2i BCSU unit upgradeo BSC3i 660 (GSWB) BCSU unit upgradeo BSC3i 660 (GSW1kB) BCSU unit upgradeo BSC3i 1000/2000 BCSU unit upgradeo Upgraded Flexi BSC BCSU unit upgradeo New delivery Flexi BSC BCSU unit upgrade

- ET HW upgrade

o BSC2i ET HW upgradeo ET5C-4 cartridgeo BSC2i ET configurationo BSC2i ET PCM cables

- Actions after upgrade & post conditions

o Implementation of the new optional featureo Polling interval parametero PCU2 scheduling weight parameterso Check and update PCU boot softwareo Cartridge marking labelso BSC configuration printout (post-check)


o Fallback copying of the current software

The total upgrade time is 3-4 hours (for a fully configured BSC: 8+1 BCSU) depending on which options areinstalled.During the GPRS/EDGE BSC upgrade, the traffic is handled normally.The modified units should be carefully monitored the day after the upgrade. Possible problems must be solvedbefore any further actions are performed in the GPRS/EDGE Radio network set up procedure.

The possibility to run GPRS/EDGE macro remotely is added to be able to reduce site visits.When PCU upgrade is to be done remotely, it is strongly recommended to test new PCU_x/PCU2_x plug-in unitsin test bed before site visit.During the macro execution the new PCU plug-in units will be created into hardware database. During this stepthere is no need to switch off power or check/install cables as instructed by the macro.

Note!If the PCU plug-in units will be swapped with PCU2 plug-in units, the new PCU2 units has to be created toHW database and the bearer channels should be terminated to the PCU2 plug-in units.After the GPRS traffic has swapped to new PCU2 units successfully, the old PCU plug-in units can bedeleted from the HW configuration.

The Nokia GSM/EDGE BSC product family:Mech. BSC

variantBase Station Controller, a general term for all GSM/EDGE BSC versions

M92 BSCi BSCi High Capacity (upgraded and improved) version ofthe first generation Base Station Controller

M92 BSC2i BSC2i, ANSIversion

American National Standards Institute (ANSI)version of the High Capacity, Base StationController, DX 200 BSC2

BSC2i, ETSIversion

European Telecommunications Standards Institute(ETSI) version of the High Capacity, Base StationController, DX 200 BSC2

M98 BSC3i 660BSC3i1000BSC3i2000

BSC3i, ANSIversion

American National Standards Institute (ANSI) HighCapacity version of the Base Station Controller,BSC3i

BSC3i, ETSIversion

European Telecommunications Standards Institute(ETSI) High Capacity version of the Base StationController, BSC3i

M98 Flexi BSC Flexi BSC,ANSI version

American National Standards Institute (ANSI) FlexiBSC family based High Capacity Base StationController

Flexi BSC, ETSIversion

European Telecommunications Standards Institute(ETSI) Flexi BSC family based High Capacity BaseStation Controller

Please note that there is in total of 6 different product variants of the Base Station Controller BSC3i 660, BSC3i1000, BSC3i 2000, Flexi BSC) supported by S16 release. Only High Capacity BSC level of M92 mechanics BSCis supported in S16 release, in S16.1 M92 models are not supported

The PCU controls the GPRS radio resources and acts as the key unit in the following procedures:- GPRS radio resource allocation and management

- GPRS radio connection establishment and management

- Data transfer

- Coding scheme selection


- PCU statistics

PCU and BSC product variantsThe PCU hardware is positioned at the BSC site as a plug-in unit in each BCSU. Table Nokia GSM/EDGE PCUproduct family lists the available PCU variants and table PCU(s) in BSC product variants shows the amount ofPCU(s) for each BSC product variant.

PCU Packet Control Unit, a general term for all PCU versionsGeneral name Name of HW

product variantExplanation

First GenerationPacket Control Unit -PCU1

PCU First generation PCU for BSCi and BSC2iPCU-S First generation PCU for BSCi and BSC2iPCU-T First generation PCU for BSCi and BSC2iPCU-B First generation PCU for BSC3i, includes two

logical PCUsSecond GenerationPacket Control Unit -PCU2

PCU2-U Second generation PCU for BSCi and BSC2iPCU2-D Second generation PCU for BSC3i & Flexi BSC,

includes two logical PCUsPCU2-E Second generation PCU for BSC3i & Flexi BSC,

includes one logical PCU

When installing the PCU(s) to BSCi and BSC2i, the operator has to make sure that the GSWB has enoughcapacity (see chapter 8.6). Installing the first PCU plug-in unit into the BCSU(s) requires three SW64B plug-inunits in the GSWB (GSWB size 192 PCM(s)), installing the second PCU plug-in unit requires four SW64B plug-inunits in the GSWB (GSWB size 256 PCM(s)). If Gb over Frame Relay is used, then the operator also has toconsider the need for E1/T1 (ET) extensions.

Support of PCU2PCU2 is a high capacity embedded plug-in unit that provides additional processing power and extendedfunctionality from BSS11.5 onwards. Second Generation PCU(s) have an enhanced design architecture thatenables the network to meet the real time traffic requirements of new services and provide means to newenhanced functionality (GERAN) beyond GPRS and EGPRS.There are three PCU2 plug-in unit variants: PCU2-U for BSCi and BSC2i, PCU2-D for BSC3i 660, BSC3i1000/2000, upgraded Flexi BSC and PCU2-E for BSC3i 660, BSC3i 1000/2000 and Flexi BSC.

PCU2-EThe PCU2-E plug-in unit can be used in various applications, which need DSP(s). The main application for PCU2-E will be to work as a packet control unit for GPRS/EDGE system.PCU2-E supports 1024 16k Abis sub channels in BSC3i 3000 configuration. Due to PCM line limitations themaximum Abis connectivity with PCU2-E in any other configuration than Flexi BSC 3000/4200 (BSC3i 660, BSC3i1000, BSC3i 2000) is 512 channels. PCU2-D/U supports 256 Abis sub channels per logical PCU.PCU2-E is supported on the following BSC3i configurations:

- Flexi BSC 3000/4200 (new delivery & supported upgrade path)

- BSC3i 2000

- BSC3i 1000

- BSC3i 660 with GSW1KB

- BSC3i 660 with GSWB


PCU2-E can reside in BSC3i and Flexi BSC network elements. In upgraded Flexi BSC network element there canmaximum of two PCU2-Es in one cartridge (due to power supply restrictions) if power supply plug-in unit is notupgraded to PSC6-D. But in new delivery Flexi BSC network element there can be up to 5 PCU2-Es in one BCSUunit. Also in upgraded Flexi BSC network element there can be up to 5 PCU2-Es in one BCSU unit when BCSUunit has new power supply plug-in unit PSC6-D.

The PCU2-E plug-in unit is slightly based on PCU2-D plug-in unit. Changes in PCU2-E compared to PCU2-D are:- One logical PCU on PWB (PCU2-D had two logical units)

- MPC 8567 (next generation PQIII is used) as a host processor (one piece)

o Memory system is different from PCU2-E (e.g. DDR2 is its own busand amount of memory is 1 GB, no local bus SDRAM and boot FLASHis on local bus)

o One RS-232 service terminal on front panel- Used DSP type is TMC320TCI6482 (Himalaya)

o Six DSPs in PCU2-E (daughter board system is not used anymore)o Each DSP has 256 MB DDR2 memory

- DSP MPC 8567 interconnect is done with sRIO

- PCU2-E has PCI-to-PCI bridge (Actel PCI FPGA is not used anymore)

- More PCM interfaces (3 x 8M interfaces or 6 x 4M interfaces)

o Changes to PCM MUX- New voltages on boards

o Changes to power block- 2 x 10/100/1000 BaseT Ethernet interfaces on backplane

Asymmetrical PCU HW configuration

Note!BSC3i/PCU HW implementation procedure does not use asymmetrical PCU configuration. However afterPCU2-E plug-in unit installation the asymmetrical configuration feature is activated.

Asymmetrical PCU HW Configuration optimizes PCU plug-in unit configuration possibilities. PCU(s) can beinstalled into BSC one by one. BCSU(s) are equipped with PCU(s) according traffic needs, i.e. PCU are added toBCSU(s) in granularity of one until full PCU PIU amount is reached in the BSC.Because it shall be allowed that PCU plug-in unit is installed to the BSC one by one, each BCSU unit can havedifferent number of PCU PIU(s) (0...max). However it is recommended to increase PCU capacity in BCSU(s)evenly to keep load in BCSUs in balance.Asymmetrical PCU HW configuration allows operator to add and activate PCU HW in granularity of one andaccording to traffic needs.Asymmetrical PCU HW configuration introduces a definition of the primary spare BCSU. With Asymmetrical PCUHW configuration the primary spare BCSU is configured to have enough PCU HW units to take over any of theactive BCSUs. The system will keep the primary spare BCSU as the spare BCSU by performing related BCSUswitchovers as soon as the BCSU statuses allow this. A related alarm is raised if the primary spare BCSU unit isnot in SP-EX state.BSC DX platform keeps the primary spare unit as the SP-EX BCSU whenever possible. The BSC DX platformautomatically performs a prepared switchover in order to restore the primary spare BCSU to SP-EX state as soonas state of BCSU allows that.If the primary spare unit is not in SP-EX state, the BSC DX platform raises an alarm. The BSC DX platformcancels the alarm, when the primary spare unit is in SP-EX again.


Asymmetrical PCU HW Configuration supports both PCU1 and PCU2 PIU variants.

More information about features can be found from document Features Under Development which Introduces thenew features and describes the benefits.

4.1 PCU Plug-in unit variants

4.1.1 PCU, Packet Control Unit (C72070)

The PCU is a plug-in unit that implements Gb, RLC (Radio Link Control) and MAC (Medium Access Control)interfaces in a BSC.The PCU's PCM cables are connected to the PCU's front panel. The cable type is CFN.The PCU unit receives and transmits TRAU frames to the Base Stations, and Frame Relay packets to the SGSN(Serving GPRS Support Node). The unit interfaces to the 16-bit DMC bus. Other interfaces are: internal 4 Mbit/sPCM line for the TRAU frames, internal 4 Mbit/s PCM line for the Frame Relay, the clock unit for the basic timingsignals, side selection and identification logic. The PCM interface is in the front panel (euroconnector). Two RJ45connectors for the Ethernet and one for the RS232 interfaces are in the front panel. Other signals are in thebackplane connectors.

PCU:x two 2.048 Mbit/s PCM lines interfacing to the DSP processors,x two 2.048 Mbit/s PCM lines interfacing to the PowerQuicc II processorx two 10/100 BaseTx type Ethernet interfaces


x PowerQuicc II Processorx DSP Processor with daughter cardx 16-bit wide DMC-interface.

4.1.2 PCU_S, Packet Control Unit, S-Variant (C74840)

The PCU_S variant has the same features as the PCU, but has a higher capacity processor.PCU_S is a new PCU variant, which implements both Gb and RLC (Radio Link Control) / MAC (Medium AccessControl) interfaces in the BSC.The PCU unit receives and transmits TRAU frames to the Base Stations and Frame Relay packets (Sub-networkService) to the SGSN (Serving GPRS Support Node).The unit interfaces to the 16-bit DMC bus and 4 Mbit/s PCM line.In the front panel of the PCU, there is an euroconnector for the PCM interface. There are also three RJ45connectors: one for the RS232 interface and two for the LAN (Ethernet) interfaces. Other signals are in thebackplane connectors.

4.1.3 PCU_T, Packet Control Unit, T-Variant (C105254)

The PCU_T variant has the following differences compared to the PCU_S: newer version of MPC8260 processor 256 Mbytes of SDRAM memory

4.1.4 PCU2_U, Packet Control Unit, U-Variant (C10108872)

The Second Generation Packet Control Unit (PCU2_U plug-in unit) is a PCU based plug-in unit variant (DMCbackplane).The unit interfaces to the DMC bus and 4 / 8 Mbit/s PCM line.

4.1.5 PCU_B, Packet Control Unit, B-Variant (C104512)

The Packet Control Unit (PCU_B plug-in unit) is a PCU based plug-in unit variant with a PCI motherboard bus.Logically, it contains two PCU functions integrated in one plug-in unit.The PCU_B has two microprocessor blocks. The blocks are identical and work independently. The block uses theMotorola PowerQuicc II family processor MPC. One PQII block is connected to two 10/100BaseTx Ethernet PHYinterfaces, and the other block shares the same interfaces for redundancy reasons. Ethernet PHY interfaces areconnected to the backplane of the cartridge. The LAN interfaces are implemented using the PowerQuicc IIintegrated Ethernet controller.PCU_B implements both Gb and RLC (Radio Link Control) / MAC (Medium Access Control) interfaces in theBSC.The PCU unit receives and transmits TRAU frames to the Base Stations and Frame Relay packets (Sub-networkService) to the SGSN (Serving GPRS Support Node).The unit interfaces to the PCI bus and 4 Mbit/s PCM line.

4.1.6 PCU2_D, Packet Control Unit, D-Variant (C108407)

The Second Generation Packet Control Unit (PCU2_D plug-in unit) is a PCU based plug-in unit variant with a PCImotherboard bus. Logically, it contains two PCU functions integrated in one plug-in unit.The unit interfaces to the PCI bus and 4 / 8 Mbit/s PCM line.


4.1.7 PCU2_E, Packet Control Unit, E-Variant (C110629)

The Second Generation Packet Control Unit (PCU2_E plug-in unit) is a PCU based plug-in unit variant with a PCImotherboard bus. Logically, it contains one PCU functions integrated in one plug-in unit.The unit interfaces to the PCI bus and 4 / 8 Mbit/s PCM line.PCU2-E can reside in BSC3i network element.

4.2 BSCi Hardware

The following picture describes BSCi hardware for the S11.5 release in GPRS feature. The S11.5 PCUconfiguration is the same from the S9 onwards for PCU configuration:

4.3 BSC2i Hardware

The following picture describes BSC2i hardware changes for the S11.5 release GPRS/EDGE feature (two PCUplug-in units installed in every BCSU unit).


01 13 3725

CBD 8

152

01120

088

058

030

002

0 1 2 3

4 5 6 7

0 1 2 3

4 5 6 7

0 1 2 3

4 5 6 7

0 1 2 3

4 5 6 7

0 1 2 3

4 5 6 7

0 1 2 3

4 5 6 7

0 1 2 3

4 5 6 7

PSA20_0PSFP0

PSA20_1PSFP1

PSA20_2PSFP2

PSA20_3PSFP3

01 19

MCMU 0MC1C

01

MCMU 1MC1C

27 01 27

01 27

01

01

ET5C0

01

ET5C1

13

CLSCLAC

ET5C2

ET5C3

ET5C4

27

OMUMC1C

01 13

2727

27

SD3C-S

01

CLSCLOC

37

BCBE

BCEE

27

BSC2i

CC19V R2A1-S

ET5C5

ET5C6

2nd PCU, PACKETCONTROL UNIT, ISADDED TO THE BCSU.PCM CONNECTION TOTHE GSWB IS MADEFROM THE PLUG-INUNITS FRONT PANEL,USING CFNxxx CABLES

S10 provides two new ET5CCARTRIDGES

0 1 2 3

4 5 6 7

0 1 2 3

4 5 6 7

4th SW64BPLUG-IN UNITAND THE SWBUS4FRONT PANELCONNECTORIS ADDEDTO THE GSWB UNITS

ET5C7

ET5C8

GPRS/EDGE OPTION

GSWB 0SW1C0

GSWB 1SW1C1

BCSU 3MC1C

BCSU 4MC1C

BCSU 5MC1C

BCSU 6MC1C

BCSU 7MC1C

BCSU 1MC1C

BCSU 2MC1C

BCSU 8MC1C

BCSU 0MC1C

4.4 BSC3i 660 Hardware

The following picture describes BSC3i hardware changes for the S11.5 release GPRS/EDGE feature (two PCUplug-in units installed in every BCSU unit).


4.5 BSC3i 1000/2000 Hardware

The following picture describes BSC3i hardware changes for the S12 release GPRS/EDGE feature (five PCUplug-in units installed in every BCSU unit).

PDFU 0PDFU-A

MCMU 1CC4C-A

MCMU 0CC4C-A

OMUCM2C-A

GSWB 0SW1C-C

CLS

0,1

CLO

C-B

BSCC

BCSU 1CC3C-A

BCSU 0CC3C-A

GSWB 1SW1C-C

BCSU 2CC3C-A

BCSU 4CC3C-A

BCSU 3CC3C-A

BCSU 5CC3C-A

BCSU 6CC3C-A

ET4C 0ET4C-B

(32*ET2E/A)

ET4C 1ET4C-B

(30*ET2E/A)

FTRB 0 FTRB 1

FTRB 2 FTRB 3

CPRJ45 CPGOCPGO

PDFU 1PDFU-A

PDFU 2PDFU-A

PDFU 3PDFU-A


4.6 Upgraded Flexi BSC Hardware

The following picture describes BSC3i hardware changes for the release GPRS/EDGE feature (fivePCU plug-in units installed in every BCSU unit).


4.7 New delivery Flexi BSC Hardware

The following picture describes BSC3i hardware changes for the release GPRS/EDGE feature (fivePCU plug-in units installed in every BCSU unit).

REAR SIDE

FTRB 0

1

0

C CL

CC3C-A CC3C-A

BCSU 1 BCSU 0

SW10C-ASW10C-A

GSW2KB0

GSW2KB1

0

0

08

CC4C-A CC4C-A

CC3C-ACC3C-A

BCSU 4 BCSU 3CC3C-A

BCSU 5

CC3C-A

BCSU 2

3

BSCC

0

CM2C-A

OMU

48

06 3

MCMU0

MCMU1

2

3

4

5

GT4C-A

GTIC1

GT4C-A

GTIC0

C CL

L LA

L LA

CPRJ45-ACPGO

10

0469

CC3C-A

BCSU 6

CPETS-G / CPETS-E /CPETC-E

0

1

2

3

4

CPETS-G /CPETS-E /CPETC-E

CPETS-H /CPETS-F /CPETC-F

PDFU PDFU PDFU PDFU

upgraded BSC3i 3000/4200(CC3C-A used as BCSU)

FTRB 1

FTRB 2FTRB 348

6

CPETS-G /CPETS-E /CPETC-ECPETS-G /CPETS-E /CPETC-E


REAR SIDE

FTRB 0

1

0

C CL

CC3C-B CC3C-B

BCSU 1 BCSU 0

SW10C-ASW10C-A

GSW2KB0

GSW2KB1

0

0

08

CC4C-A CC4C-A

CC3C-BCC3C-B

BCSU 4 BCSU 3CC3C-B

BCSU 5

CC3C-B

BCSU 2

3

BSCC

0

CM2C-A

OMU

48

06 3

MCMU0

MCMU1

2

3

4

5

GT4C-A

GTIC1

GT4C-A

GTIC0

C CL

L LA

L LA

CPRJ45-ACPGO

10

0469

CC3C-B

BCSU 6

CPETS-G / CPETS-E /CPETC-E

0

1

2

3

4

CPETS-G /CPETS-E /CPETC-E


PDFU PDFU PDFU PDFU

upgraded BSC3i 3000/4200(CC3C-B used as BCSU)

FTRB 1

FTRB 2FTRB 348

6

CPETS-G /CPETS-E /CPETC-ECPETS-G /CPETS-E /CPETC-E



PDFU-APDFU 1PDFU-B

PDFU 0

BSCC-E

PDFU-B

CPRJ45-A

CC3C-B

DC3C-B

CC3C-A

FTRB 1 (FTRB-A) FTRB 0 (FTRB-A)

FTRB 3 (FTRB-A) FTRB 2 (FTRB-A)

SGC1C-A

GSW2KB-A 1

BCSU 0OMU

MC

MU

1

MC

MU

0

BC1C-B

BCSU 5 BCSU 3 BCSU 1

LAN

U0

CPGO/CPETS-G/CPETS-E/CPETC-E

CPETS-G/CPETS-E/CPETC-E

BC1C-B

BCSU 6 BCSU 4 BCSU 2

LAN

U1

GTIC 1

CLS

1

ETC 2ETC 3

SGC1C-A

GTIC 0

CLS

0

ETC 0ETC 1 GSW2KB-A 0

0

0

0

0

0

48

6

6

T0.0T0.8 T0.4

REAR VIEW


5 PRE-REQUIREMENTS

5.1 Pre-requirements & Actions needed prior upgrade

Make sure that following requirements are met before starting the upgrade:- Software level need to be S16 or newer

- All the available Change Deliveries are installed

- The password of the BSC with full authority 250 in all command classes

- The password of the NetAct communication server (if planned to be used)

- SW new licences

Verify that memory amounts in Flexi BSC products are according to Technical Note : Minimum HW Requirementsfor BSC S1xx Release:BSC3i 660 and BSC3i 1000/2000

- 1 GB (1024 in Mbytes) in OMU and MCMU units

- 1GB (1024 in Mbytes) in BCSU units

Flexi BSC (both upgraded and initial)- 2 GB (2048 in Mbytes) in OMU, MCMU and BCSU units

5.2 Restrictions

In case of PCU2-E plug-in unit, swap is not possible. After PCU2-E unit installation new feature AsymmetricalHW installation is activated (primary spare unit is defined).PCU2-E installation requires also that the track where installation will be done must be empty (contains no othertype of PCU2 plug-in units). However, if macro is stopped during installation and started again, the installation canbe continued from the next BCSU which has free track available.Upgraded Flexi BSC hardware contains PSC6-A or PSC6-B power supplies. With these power supplies maximumtwo PCU2-E plug-in units can be installed to one cartridge. Power supply plug-in unit must be upgraded to PSC6-D if three or more PCU2-E plug-in units are needed This upgrading can be done already before starting theupgrade (chapter 8.2) or during upgrade together with PCU2-E installations.Note:-If user is doing Packet Abis upgrade and wants to upgrade/recreate PCU2-E plug-in units to Packet Abis in use;traffic from these PCU2-E cards needs to redirect to other PCU's and IP interfaces need to delete manually fromPCU2-E cards before recreation.


5.3 Needed documentation

To perform the upgrade successfully, the following documentation is required:- BSC/PCU HW implementation for PS traffic (GPRS/EDGE) procedure (this

document)

- HIT Users manual

- Technical Support Note: Minimum HW Requirements for BSC S1xx Release.

- Fallback copying instructions of DX200 BSC (NED)

- Creating and managing BSC hardware (NED)

- TCSM documents (if TCSM is configured to the current BSC)

- BSC configuration printout

5.4 Needed equipment

To perform the upgrade successfully, the following hardware are required:- PC with installed HIT and upgrading macros

- SIM cards of the network and mobile phone(s)

- needed amount of PCU plug-in units which are to be installed/swapped

- SW64B plug-in units for GSWB extension (optional) and corresponding PCUcabling.

- needed amount of PSC6-D plug-in units when planned to install more than twoPCU2-E plug-in units to each BCSU

5.5 HIT and upgrade macros

5.5.1 System requirements for HIT

HIT 3.4-0 swup is designed to operate on Windows and Linux.The HIT installation requires approximately 20MB disk space, of which the documentation occupies approximately5MB.

5.5.2 Installing HIT

It is necessary to go through this section only if the HIT release 3.4-0 swup has not been installed. If the softwarehas already been installed, proceed to the next section: Installing HIT upgrading macros.HIT release 3.4-0 swup is delivered in Release Binder found from NOLS (Nokia Online Services). The installationof the software is done by executing the SETUP.EXE -program and following the instructions of the installationprogram.

5.5.3 Installing HIT upgrading macros


After the HIT program has been installed, it is necessary to install the upgrading macros. The upgrading macrosare included in the Release Binder which can be found from NOLS (Nokia Online Services). Release bindercontains all the macros used in different upgrades related to SW.

To install the macros into PC, execute the macros.exe program. When the exe file is run the following dialog willappear:

Specify the folder to which the macros will be installed, press Unzip and the macros will be installed.This zipped executable file includes the whole upgrade macro and the needed directory structure. The only userexecutable file, UPGMAIN.HIT, is extracted to root directory of macro folder.

5.5.4 HIT settings

Before running HIT, it is recommended that the 'use of FIFO buffers' be turned off from the used communicationsport. This needs to be done, because some PCs communications port handling is unreliable with this settingactive.It is recommended that you contact your local PC support for instructions on how to turn off the use of FIFObuffers.If you are familiar with the settings of the PC, here's an example of how to turn the use of FIFO buffers off. InWindows 2000, the use of FIFO buffers is turned off in the following way:

1. Start Control Panel

2. From Control Panel select System

3. In the System Properties dialog select Hardware/Device Manager

4. In Device Manager select desired communications port (usually COM1) anddouble-click it

5. In Communications Port (COMx) Properties dialog select Port Settings

6. In Port Settings select Advanced

7. In Advanced Port Settings dialog deactivate the 'Use FIFO buffers' and pressOK

8. Close all the opened dialogs by pressing OK

When opening the HIT program the first time, remember to check/create the used device (ref. Hitguide.doc). It isrecommended to use the network element name for the devices.


5.5.5 Connection settings

When opening the HIT program the first time, remember to check/create the used devices (ref. Hitguide.doc).When the macro is started, the available devices are listed to select device to be connected.

Following connection types are supported:x Local connection (COM)x Telnetx SSHx Via Netact (SSH)

Note: in S16 level onwards, via Netact (SSH) is only allowed.

5.5.5.1 Connection settings for Windows1.1.1.1.1 5.5.5.1.1 Configuration example for creating Telnet / SSH / NetAct connection

Select Device > Set Configuration from menu.Following window appears

Select New


Give name for connection and IP address of OMU or NetAct server.Note!DX_TELNET is selected for telnet connection and SSH is selected for SSH connection inType/Protocol: field. Default port for telnet is 23 and for SSH is 22.


In case of Telnet or SSH connection option, select Login,Q/A sheet and define the username and password ofBSC MML session.


Note!In case of NetAct via SSH connection option, select Login sheet and define the username and password ofNetAct communication server and BSC MML session.


Select Terminal sheet and define the MML log file.


If connection type is Telnet, press OK.In SSH connection, define also settings of SSH sheet. Define security level to medium or low level.


After defining SSH related parameters, Press OK.

1.1.1.1.2 5.5.5.1.2 Configuration example for creating COM connectionSelect Device > Set Configuration from menu.Following window appears


Note! COM connection is selected

Select Login,Q/A sheet and define the username and password of BSC MML session.


Press OK.

5.5.5.2 Connection settings for Linux1.1.1.1.3 5.5.5.2.1 Configuration example for creating Telnet / SSH / NetAct connection

Select Edit> Devices > from menuFollowing window appears


Select New


Give name for connection and IP address of OMU or Net Act server.

Note! DX_TELNET is selected for telnet connection and SSH is selected for SSH connection inType/Protocol: field. Default port for telnet is 23 and for SSH is 22.


In case of Telnet or SSH connection option, select Login,Q/A sheet and define the username and password ofBSC MML session.


In case of NetAct via SSH connection option, select Login sheet and define the username and password ofNetAct communication server and BSC MML session.


If connection type is Telnet, press OK.

In SSH connection, define also settings of SSH sheet. Define security level to medium or low level.


After defining SSH related parameters, Press OK.1.1.1.1.4 5.5.5.2.2 Configuration example for creating COM connection

Select Edit> Devices > from menuFollowing window appears


Note! COM connection is selectedSelect Login,Q/A sheet and define the username and password of BSC MML session.


Press OK.

5.5.6 Starting the HIT application / macro execution

First of all, close List and Macro windows, as those are not needed. In Response window all MML commands areprinted out. It is recommended to keep Messages window as big as possible to able to follow up the macroexecution. The important information is printed out to the messages window.


Open file UPGMAIN.HIT from the location it was extracted and press Green Arrow to start the execution.

At the beginning, the main menu is shown and macro prompts user to choose which upgrade toexecute. Clicking CANCEL in main menu aborts the macro execution.


Choose connection type to BSC. This option is displayed only if the procedure can be also executed via NetAct. IfNetAct is selected, the macro asks communication servers username, password and BSC C-number.


Select ini file from the list.

Select target network element from the list.Note!

If NetAct connection has been chosen, choose the correct device which contains IP address definition toNetAct server.


User may choose the location where the macro log files should be saved.

Also, user can define whether to use default log file name or define own.


The status of the current BSC software package is checked. Note that the current software packagemust be with status BU before the actual upgrade can be started. The software status is to bechecked with command:

ZWQO:RUN;

Check from the output that all the computer units which are currently in use are running on correctsoftware package with the status BU. If the software package status is FB or NW, find out the causefor the setting.

If the status of the package is something else than BU, macro gives following pop-up window:

The status can be changed to BU with command:

ZWSC:STAT=NW:STAT=BU;

The active and blocked alarms (DX200 and BTS alarms) can be printed out with followingcommands:

ZAHO;ZABO;ZEOL;ZEOE;

Alarm printings can be skipped and macro asks user about the wanted action with following pop-up:


Some environment information is checked with following commands:ZQRI;ZIWQ:,OMU:WS=0,;ZDCD;ZUSI:ALL;ZWTI:P:OMU;ZUSI:BCSU;ZWTI:P:GSW,0;ZYE?

This information is gathered for BSC type analysis.

IMPORTANT!If MML session is needed during upgrade, open another MML connection than specified for the upgradeexecution. The same MML connection usage for interrogate or modification purposes may confuse the macroexecution.

The procedure dialog is divided in main chapters, which may also contain sub-chapters. Chapters and their sub-chapters correspond directly to the document. Select the chapter to run and press OK.Note!In order to complete upgrade successfully, the chapters and steps must be executed in ascending order.


Select a step to run and press OK.


6 FALLBACK COPYING OF THE CURRENT PACKAGE

A fallback copying of the running software package must be made before the upgrade.A fallback copying from the old SW can be made by running macro step Fallback copying of the currentpackage.Manually, the fallback copying can be made following the document: Fallback copying in BSC. The documentcan be found from NED.


7 BSC CONFIGURATION PRINTOUT (PRE-CHECK)

The information about the BSC configurations and conditions are collected.Precondition checking is recommended to do during the daytime before the actual upgrade will be started. Thechecking can be made by using the macro (S16UPGMAIN.HIT) or manually following the instructions from BSCconfiguration printout-document delivered in Release Binder.For macro execution, choose the BSC configuration printout (pre) step in BSC/PCU HW implementation for PStraffic procedure.


8 PREPARATION FOR THE UPGRADE

8.1 GSWB extension

This step is executed only when more group witch capacity is needed for PCU installations in case of BSCi,BSC2i or BSC3i 660 with GSWB.This step can only be executed if upgrade is made locally at the site. The execution time of this step is half anhour. GSWB hardware is installed first by using MCMU-0 for the HW extension and then by making an MCMUswitchover. In this step, also the new fourth SW64B plug-in unit is installed.

First, change the state of the MCMU-0 to SP-EX:ZUSC:MCMU,0:SP,;

The GSWB extension must be installed first to the GSW-0 to ensure that GSWB size is updated to the SWICOP-process properly.

Change the state of the MCMU from SP-EX to state SE-NH:ZUSC:MCMU,:TE,;ZUSC:MCMU,:SE,;ZUSC:MCMU,:SE,;

Switch the MCMU cartridge power off from the PSC3 power supply.

Print the GSWB hardware configuration with commands:ZWTI:P:MCMU,;ZWTI:P:GSW,;

Set the SW64B jumpers according to the Appendix1, SW64B Jumper settings.

Install the SW64B card or cards to track four/five in the GSWB:

1. Switch the GSWB cartridge power off from the PSC1 power supply.

2. Install the SW64B plug-in unit(s) to the SE-NH MCMU's SW1C GSWB cartridge(track four/five). Ensure that the plug-in unit is firmly installed in it's place. Connectorsin the motherboard of the cartridge are tight, and if the plug-in unit's connector is notin full contact with the motherboard, the fault may appear later on, when the BSC hasbeen taken into use.

3. Install an SWBUS3 / SWBUS4 bus extender to the GSWB.

4. Install new PCM cables for the PCU/PCU_S/PCU_T plug-in units. Connect them tothe back of the SW1C cartridge (see cable lists in the BCSU section for details). 1/4EURO Connector of CFNPCM cable is connected to the PCU card and 1/8connector to the GSWB.

5. BSC2E and BSC2i optional: Install the PCM cables for the ET5C cartridges


6. After the GSWB HW and PCM cables are installed, switch the GSWB cartridgepower on again.

When installing the PCM cabling, avoid sharp bends and make sure that the cables are not pulled too tight. TheBSC may be carrying traffic during the HW upgrade and, therefore, special care must be taken to avoiddisconnecting other cables or connectors.

Create an SW64B plug-in unit(s):ZWTP:GSW,:SW64B,2,4;

and/orZWTP:GSW,:SW64B,3,5;

Switch the MCMU cartridge power on from the PSC3 power supply.Change the MCMU state to TE-EX:

ZUSC:MCMU,:SE,;ZUSC:MCMU,:TE,;

PSC

1

SW

64B

SW

64B

SW

64B

02 03 04 05 060100 07

SWBUS4

SW

64B

Picture 12. The GSWB SW1C cartridge

Run diagnostics.ZUDU:MCMU,;

If diagnostics fail, follow the steps described in Diagnosis Reports, Alarm Reference Manual. Once thediagnostics have been passed, change the MCMU state to SP-EX.

ZUSC:MCMU,:SP,;

Make an MCMU switchover.ZUSC:MCMU,:SP,;

Repeat these steps also for MCMU-1 unit.


8.2 Power upgrade to PSC6-D

This step is executed only in BSC3i 1000 or upgraded Flexi BSC and needed only when PCU2-E plug in unitamount per BCSU is more than two. After the power upgrade, maximum amount (five pieces) of PCU2-E can beinstalled to each BCSU unit.

Change the BCSU state from SP-EX to SE-NH:ZUSC:BCSU,:TE,;ZUSC:BCSU,:SE,;ZUSC:BCSU,:SE,;

Switch the BCSU cartridge power off from the PSC6-A or PSC6-B power supply. Remove old plug-in unit andinstall the new PSC6-D to same track.

Delete PSC6-A or PSC6-B equipment information with following command:ZWTQ::,0:;

Create new PSC6-D plug-in unit.ZWTP::PSC6_D,0,1;

Switch the BCSU power on after new equipment is created and change the BCSU state to TE-EX.ZUSC:BCSU,:SE,;ZUSC:BCSU,:TE,;

Alter BCSU has restarted to TE-EX state, execute the diagnostic:ZUDU:BCSU,;

If diagnostics fail, follow the steps described in Diagnosis Reports, Alarm Reference Manual. Once thediagnostics have been passed, change the BCSU state to SP-EX:

ZUSC:BCSU,:SP,;

Change the working BCSU to SP-EX.ZUSC:BCSU,:SP,;

Make switchover to next BCSU unit to start the upgrade for next one.Repeat these steps for all BCSU(s).

8.3 Command calendar

The command calendar tasks may disturb the GPRS/EDGE HW upgrade. Because of this, all command calendartasks must be stopped before the upgrade.

Check the current tasks with command:ZICL;

The calendar tasks are to be stopped with command:ZICB::BLOCK;


8.4 Check and copy databases to disks

In this step BSC databases are to be copied to disks with following commands.ZDBC:BSDATA,0;ZDBC:OEDATA,0;ZDBC:EQUIPM,0;ZDBC:ILDATA,0;

8.5 Licence installation and feature activation

All the new SW licences needs to be transferred to roots LICENCE directory. If not done yet, do it now.

The LICENCE directory is checked in the root of BSCs disks and created if needed.ZIWX::WS,NODEF::%,%;ZIWX::WB,NODEF::%,%;

ZIWX::WS,NODEF::%,%;ZIWX::WB,NODEF::%,%;

ZIWL::WSB,NODEF::LICENCE,200,2,;

Licence files from root directory are printed.ZIWX::WS,NODEF:LICENCE:%,XML;

Print out installed licences based on their state:ZW7I:FEA:FSTATE=OFF;

LOADING PROGRAM VERSION 1.14-0

FEATURE INFORMATION:

FEATURE CODE FEATURE NAME---------------------------------------- 4 EDGE

COMMAND EXECUTED

ZW7I:FEA:FSTATE=ON;

LOADING PROGRAM VERSION 1.14-0

FEATURE INFORMATION:

FEATURE CODE FEATURE NAME---------------------------------------- 12 PCU

COMMAND EXECUTED

New licences can be installed with the command:


ZW7L::ON;

The command above installs all the licences in the LICENCE directory and sets their (feature and capacity)activation status ON.

Licence manager software creates another LICENCE sub directory to package directory for future usage, i.e. forNetAct licence management purpose in later OSS releases.

More information of licences in the BSC can be found from Technical Bulletin: SW Bulletin licensing.


9 PCU (GPRS/EDGE) HW UPGRADE

The new PCU types to be installed are defined in this step.Macro starts PCU installation from BCSU unit index 0. All the BCSU unit tracks (where PCU plug-in units arepossible to install) are handled separately.

1) First, macro asks if change to BCSU unit PCU configuration is needed or not. If NO is chosen theunit will be skipped.

2) Secondly, all the possible actions for BCSU units PCU tracks are listed.

If the new PCU type differs from existing PCU type, the PCU will be replaced (swapped) with new type. To deleteexisting PCU, REMOVE should be selected. If no actions are planned for track in question, choose SKIP -option.When PCU2-E plug-in unit is chosen, the corresponding track will be reserved from each BCSU unit onlyfor PCU2-E usage.

When PCU2-D or PCU2-E plug-in unit installation is chosen in case of BSC3i 1000/2000, upgraded Flexi BSC ornew deliver Flexi BSC, the macro asks from user whether the new Packet Abis feature PCU installation is


needed or not. If No is chosen, the PCU unit will be equipped as using normal functions (PCUDSP andPCUPPC). If Yes is chosen, the PCU unit will be equipped for functions PCUPAB and PCUPPC.

If an existing PCU2_E wants to be used for packet Abis, the existing PCU2_E needs to be first deleted (withremove -function of this macro) and then re-created (by using add) with the packet Abis mode. Note that whendeleting the PCU2_Es, if Gb over IP is in use the IP addresses of the affected PCU's (along with the Gb over IPconfiguration) need to be deleted manually prior the deletion of the PCU's.

IMPORTANT!Macro supports also power upgrade to PSC6-D if more than two PCU2-E plug-in units are planned to be installed(see more information in chapter 8.2).

new feature Asymmetrical HW configuration cannot be used during PCU installation or removal. If feature isactivated, it will be taken out of use for PCU installation phase because BCSU switchovers cannot be executedsuccessfully while feature is used.

Note that the following alarm appears to BCSU during PCU2-E installation.

AURA MCMU-0 SWITCH 2009-01-29 09:30:28.98

* ALARM ........ GBA_BX

(0001) 3502 PRIMARY SPARE BCSU UNIT MISSING

When installation needs to be interrupted (macro is stopped), the installation can be continued from the nextBCSU which has free track available.After successful PCU installation for every BCSU unit, the asymmetrical configuration feature can be taken in use(by defining primary spare BCSU) and alarm 3502 is to be cancelled.


9.1 BSCi BCSU Unit Upgrade

GPRS/EDGE hardware is installed using a spare BCSU for the HW upgrade and by making BCSU switchoversuntil every unit is upgraded. (BSCi model: see section 4.2)

All the BCSU plug-in unit tracks are in use in BSCi. That is why the second PCU cannot be installed to the BCSU.

Check that all the PCU plug-in unit jumpers are according to the instructions (Appendix2, PCU, PCU_S andPCU_T Jumper settings or Appendix3, PCU2_U Jumper settings).

First, change the BCSU state from SP-EX to SE-NH:ZUSC:BCSU,:TE,;ZUSC:BCSU,:SE,;ZUSC:BCSU,:SE,;

Switch the BCSU cartridge power off from the PSC3 power supply.

Create GB interface to BCSU if needed:ZQRA:BCSU, :, :IFETH0::UP;ZQRA:BCSU, :, :IFETH1::UP;


9.1.1 PCU Track 9 PCM Configuration

Install the PCU to BCSU track 9. Connect two internal 4M PCM cables (cables which are coming from the GSWB)to the PCU. See cable lists for details. One PCM is used for the Abis and one for the Gb interface.PCM(s) will be defined with two plug-in unit functions: PCUDSP and PCUPPC. The PCU plug-in unit is created tothe EQUIPM database with the following MML-command (used Plug-in unit can be PCU, PCU_S, PCU_T orPCU2_U):

ZWTP:BCSU,0:,4,9::PCUDSP,4,156,TSL,0&&31:PCUDSP,4,157,TSL,0&&31:PCUPPC,4,158,TSL,0&&31:PCUPPC,4,159,TSL,0&&31;










After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,:,4;

9.1.2 BSCi PCU PCM cables, Track 9

PCU PCM- Cables, Cable list for BCBE rack:

No. Rack FE Connector Rack FE Connector Type Use1.100

BCBE BCSU 0 / PCU 089.27F 09R1 BCBE SW1C 0 151.01B 04R8 CFN016 PCM

1.101

BCBE BCSU 0 / PCU 089.27F 09R3 BCBE SW1C 1 123.01B 04R8 CFN012 PCM

1.102

BCBE BCSU 1 / PCU 027.01F 09R1 BCBE SW1C 0 151.01B 04S1 CFN025 PCM

1.103


1.104


1.105


Cable list for BCEE rack:


No. Rack FE Connector Rack FE Connector Type Use2.100

BCEE BCSU 3 / PCU 061.01F 09R1 BCBE SW1C 0 151.01B 04S3 CFN030 PCM

2.101


2.102


2.103


2.104


2.105


2.106


2.107


2.108


2.109


2.110


2.111


See Appendix7, EURO Connector is connected to PCUSwitch the BCSU cartridge power on from the PSC3 power supply.Change the BCSU state to TE-EX.

ZUSC:BCSU,:SE,;ZUSC:BCSU,:TE,;

After PCU installation, boot software checking is done. If update is needed, macro executes update accordinginstructions in chapter 11.4.PCU plug-in units software can be updated also after PCU installation in chapter 11.3.

BCSU unit needs to be restarted after boot update.ZUSU:BCSU,:C=DSK;

Alter restart execute diagnostic:

ZUDU:BCSU,;

If diagnostic fail, follow the steps described in Diagnosis Reports, Alarm Reference Manual. Once thediagnostics have been passed, change the BCSU state to SP-EX:

ZUSC:BCSU,:SP,;

Change the working BCSU to SP-EX:

ZUSC:BCSU,:SP,;

Repeat these steps for all BCSU(s).


9.2 BSC2i BCSU Unit upgrade

GPRS/EDGE hardware is installed using a spare BCSU for the HW upgrade and by making BCSU switchoversuntil every unit is upgraded. First, change the BCSU state from SP-EX to SE-NH:

ZUSC:BCSU,:TE,;ZUSC:BCSU,:SE,;ZUSC:BCSU,:SE,;

Switch the BCSU cartridge power off from the PSC3 power supply.

Check that all the PCU plug-in unit jumpers are according to the instructions (Appendix2, PCU, PCU_S andPCU_T Jumper settings or Appendix3, PCU2_U Jumper settings).

1. Install the PCU to BCSU track 9, see chapters 9.2.1 and 9.2.3.

2. Install the PCU to BCSU track 8, see chapters 9.2.2 and 9.2.4

Create GB interface to BCSU if needed:ZQRA:BCSU, :, :IFETH0::UP;ZQRA:BCSU, :, :IFETH1::UP;

Switch the BCSU cartridge power on from the PSC3 power supply.Change the BCSU state to TE-EX.

ZUSC:BCSU,:SE,;ZUSC:BCSU,:TE,;

After PCU installation, boot software checking is done. If update is needed, macro executes update accordinginstructions in chapter 11.4.PCU plug-in units software can be updated also after PCU installation in chapter 11.3.

BCSU unit needs to be restarted after boot update.


ZUSU:BCSU,:C=DSK;

Alter restart execute diagnostic:ZUDU:BCSU,;

If diagnostics fail, follow the steps described in Diagnosis Reports, Alarm Reference Manual. Once thediagnostics have been passed, change the BCSU state to SP-EX:

ZUSC:BCSU,:SP,;

Change the working BCSU to SP-EX:ZUSC:BCSU,:SP,;

Repeat these steps for all BCSU(s).

9.2.1 PCU Track 9 PCM Configuration in BSC2i

Install the PCU to BCSU track 9. Connect two internal 4M PCM cables (cables which are coming from the GSWB)to the PCU. See cable lists for details. One PCM is used for the Abis and one for the Gb interface. PCMs will bedefined with two plug-in unit functions: PCUDSP and PCUPPC.

The PCU plug-in unit is created to the EQUIPM database with the following MML-command (used plug-in unit canbe PCU, PCU_S, PCU_T or PCU2_U):












ZWUC:BCSU,:,4;

DMCT2-S terminators are already installed in the High Capacity BSCi and BSC2i. Check that terminators areinstalled. Check that MC1C interchangeability code is C or D.

9.2.2 PCU Track 8 PCM Configuration in BSC2i

Install the PCU to BCSU track 8. Connect two internal 4M PCM cables (cables which are coming from the GSWB)to the PCU. See cable lists for details. One PCM is used for the Abis and one for the Gb interface. PCM(s) will bedefined with two plug-in unit functions: PCUDSP and PCUPPC.

The PCU plug-in unit is created to the EQUIPM database with the following MML-command (used plug-in unit canbe PCU, PCU_S, PCU_T or PCU2_U):











ZWUC:BCSU,:,3;

9.2.3 BSC2i PCU PCM-Cables, track 9

BSC2i PCU PCM-Cables, Cable list for BCBE rack:


No. Rack FE Connector Rack FE Connector Type Use1.100 BCBE BCSU 0 / PCU 030.27F 09R1 BCBE SW1C 0 120.01B 04R8 CFN020 PCM1.101 BCBE BCSU 0 / PCU 030.27F 09R3 BCBE SW1C 1 120.19B 04R8 CFN018 PCM

1.102 BCBE BCSU 1 / PCU 002.01F 09R1 BCBE SW1C 0 120.01B 04S1 CFN026 PCM1.103 BCBE BCSU 1 / PCU 002.01F 09R3 BCBE SW1C 1 120.19B 04S1 CFN024 PCM

1.104 BCBE BCSU 2 / PCU 002.27F 09R1 BCBE SW1C 0 120.01B 04S2 CFN024 PCM1.105 BCBE BCSU 2 / PCU 002.27F 09R3 BCBE SW1C 1 120.19B 04S2 CFN022 PCM

Cable list for BCEE rack:

No. Rack FE Connector Rack FE Connector Type Use2.100 BCEE BCSU 3 / PCU 088.01F 09R1 BCBE SW1C 0 120.01B 04S3 CFN016 PCM2.101 BCEE BCSU 3 / PCU 088.01F 09R3 BCBE SW1C 1 120.19B 04S3 CFN014 PCM

2.102 BCEE BCSU 4 / PCU 088.27F 09R1 BCBE SW1C 0 120.01B 04S4 CFN018 PCM2.103 BCEE BCSU 4 / PCU 088.27F 09R3 BCBE SW1C 1 120.19B 04S4 CFN016 PCM





See Appendix7, EURO Connector is connected to PCU

9.2.4 BSC2i PCU PCM-Cables, Track 8

BSC2i PCU PCM-Cables, Cable list for BCBE rack:

No. Rack FE Connector Rack FE Connector Type Use1.110 BCBE BCSU 0 / PCU 030.27F 08R1 BCBE SW1C 0 120.01B 04R7 CFN020 PCM1.111 BCBE BCSU 0 / PCU 030.27F 08R3 BCBE SW1C 1 120.19B 04R7 CFN018 PCM

1.112 BCBE BCSU 1 / PCU 002.01F 08R1 BCBE SW1C 0 120.01B 05R1 CFN026 PCM1.113 BCBE BCSU 1 / PCU 002.01F 08R3 BCBE SW1C 1 120.19B 05R1 CFN024 PCM

1.114 B

Documents

BSC_PCU HW Implementation for PS Traffic (GPRS_EDGE)_Ver1_9