Вы находитесь на странице: 1из 149

BSC/PCU HW

Implementation for PS
traffic (GPRS/EDGE)
Release Delivery: HW Upgrade
Product Family: Radio Controllers
Product:BSC3i 1000/2000, Flexi BSC
Release: S16 onwards

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its
products and services. We would like to encourage you as our customers and users to join us in
working towards a cleaner, safer environment. Please recycle product packaging and follow the
recommendations 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 services
we offer, please contact us at Nokia Solutions and Networks for additional information.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

1 (149)

Table of Contents
1
2
3

Purpose .................................................................................................................................................. 6
Scope of applications .............................................................................................................................. 7
Using the document ................................................................................................................................ 8
3.1
3.2

General info....................................................................................................................................................... 8
Upgrade macro .................................................................................................................................................. 8
3.2.1
Structure ...................................................................................................................................... 8
3.2.2
Communication ............................................................................................................................ 9
3.2.3
Log files ....................................................................................................................................... 9

Introduction ........................................................................................................................................... 12
4.1

4.2
4.3
4.4
4.5
4.6
4.7

PCU Plug-in unit variants ................................................................................................................................. 16


4.1.1
PCU, Packet Control Unit (C72070) ............................................................................................ 16
4.1.2
PCU_S, Packet Control Unit, S-Variant (C74840) ........................................................................ 17
4.1.3
PCU_T, Packet Control Unit, T-Variant (C105254) ...................................................................... 17
4.1.4
PCU2_U, Packet Control Unit, U-Variant (C10108872) ................................................................ 17
4.1.5
PCU_B, Packet Control Unit, B-Variant (C104512) ...................................................................... 17
4.1.6
PCU2_D, Packet Control Unit, D-Variant (C108407).................................................................... 17
4.1.7
PCU2_E, Packet Control Unit, E-Variant (C110629) .................................................................... 18
BSCi Hardware................................................................................................................................................ 18
BSC2i Hardware .............................................................................................................................................. 18
BSC3i 660 Hardware ....................................................................................................................................... 19
BSC3i 1000/2000 Hardware ............................................................................................................................. 20
Upgraded Flexi BSC Hardware ........................................................................................................................ 21
New delivery Flexi BSC Hardware .................................................................................................................... 22

Pre-requirements .................................................................................................................................. 24
5.1
5.2
5.3
5.4
5.5

6
7
8

Pre-requirements & Actions needed prior upgrade ............................................................................................ 24


Restrictions ..................................................................................................................................................... 24
Needed documentation .................................................................................................................................... 25
Needed equipment .......................................................................................................................................... 25
HIT and upgrade macros.................................................................................................................................. 25
5.5.1
System requirements for HIT ...................................................................................................... 25
5.5.2
Installing HIT .............................................................................................................................. 25
5.5.3
Installing HIT upgrading macros.................................................................................................. 25
5.5.4
HIT settings................................................................................................................................ 26
5.5.5
Connection settings .................................................................................................................... 27
5.5.6
Starting the HIT application / macro execution............................................................................. 46

Fallback copying of the current package ................................................................................................ 54


BSC configuration printout (pre-check) .................................................................................................. 55
Preparation for the upgrade ................................................................................................................... 56
8.1
8.2
8.3
8.4
8.5

GSWB extension ............................................................................................................................................. 56


Power upgrade to PSC6-D ............................................................................................................................... 58
Command calendar.......................................................................................................................................... 58
Check and copy databases to disks.................................................................................................................. 59
Licence installation and feature activation ......................................................................................................... 59

PCU (GPRS/EDGE) HW upgrade.......................................................................................................... 61


9.1
9.2

9.3

BSCi BCSU Unit Upgrade ................................................................................................................................ 63


9.1.1
PCU Track 9 PCM Configuration ................................................................................................ 64
9.1.2
BSCi PCU PCM cables, Track 9 ................................................................................................. 65
BSC2i BCSU Unit upgrade............................................................................................................................... 67
9.2.1
PCU Track 9 PCM Configuration in BSC2i .................................................................................. 68
9.2.2
PCU Track 8 PCM Configuration in BSC2i .................................................................................. 69
9.2.3
BSC2i PCU PCM-Cables, track 9................................................................................................ 69
9.2.4
BSC2i PCU PCM-Cables, Track 8 .............................................................................................. 70
BSC3i 660 (GSWB) BCSU Unit upgrade .......................................................................................................... 71
9.3.1
PCU_B Track 6 PCM Configuration in BSC3i .............................................................................. 72
9.3.2
PCU_B Track 7 PCM Configuration in BSC3i .............................................................................. 73

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

2 (149)

9.3.3
PCU2_D Track 6 PCM Configuration in BSC3i ............................................................................ 74
9.3.4
PCU2_D Track 7 PCM Configuration in BSC3i ............................................................................ 76
9.3.5
PCU2_E Track 6 PCM Configuration in BSC3i ............................................................................ 77
9.3.6
PCU2_E Track 7 PCM Configuration in BSC3i ............................................................................ 77
BSC3i 660 (GSW1KB) BCSU Unit upgrade ...................................................................................................... 78
9.4.1
PCU_B Track 6 PCM Configuration in BSC3i 660 ....................................................................... 79
9.4.2
PCU_B Track 7 PCM Configuration in BSC3i 660 ....................................................................... 81
9.4.3
PCU2_D Track 6 PCM Configuration in BSC3i 660 ..................................................................... 82
9.4.4
PCU2_D Track 7 PCM Configuration in BSC3i 660 ..................................................................... 83
9.4.5
PCU2_E Track 6 PCM Configuration in BSC3i 660...................................................................... 84
9.4.6
PCU2_E Track 7 PCM Configuration in BSC3i 660...................................................................... 84
BSC3i 1000/2000 BCSU Unit upgrade.............................................................................................................. 85
9.5.1
PCU2_D Track 3 PCM Configuration in BSC3i 1000/2000 ........................................................... 87
9.5.2
PCU2_D Track 4 PCM Configuration in BSC3i 1000/2000 ........................................................... 88
9.5.3
PCU2_D Track 5 PCM Configuration in BSC3i 1000/2000 ........................................................... 90
9.5.4
PCU2_E Track 3 PCM Configuration in BSC3i 1000/2000 ........................................................... 91
9.5.5
PCU2_E Track 4 PCM Configuration in BSC3i 1000/2000 ........................................................... 92
9.5.6
PCU2_E Track 5 PCM Configuration in BSC3i 1000/2000 ........................................................... 93
9.5.7
PCU_B Track 6 PCM Configuration in BSC3i 1000/2000 ............................................................. 94
9.5.8
PCU_B Track 7 PCM Configuration in BSC3i 1000/2000 ............................................................. 95
9.5.9
PCU2_D Track 6 PCM Configuration in BSC3i 1000/2000 ........................................................... 97
9.5.10
PCU2_D Track 7 PCM Configuration in BSC3i 1000/2000 ........................................................... 98
9.5.11
PCU2_E Track 6 PCM Configuration in BSC3i 1000/2000 ......................................................... 100
9.5.12
PCU2_E Track 7 PCM Configuration in BSC3i 1000/2000 ......................................................... 100
Upgraded Flexi BSC BCSU Unit upgrade ....................................................................................................... 101
9.6.1
PCU2_D Track 3 PCM Configuration in upgraded Flexi BSC ..................................................... 103
9.6.2
PCU2_D Track 4 PCM Configuration in upgraded Flexi BSC ..................................................... 104
9.6.3
PCU2_D Track 5 PCM Configuration in upgraded Flexi BSC ..................................................... 105
9.6.4
PCU2_E Track 3 PCM Configuration in upgraded Flexi BSC ..................................................... 106
9.6.5
PCU2_E Track 4 PCM Configuration in upgraded Flexi BSC ..................................................... 107
9.6.6
PCU2_E Track 5 PCM Configuration in upgraded Flexi BSC ..................................................... 107
9.6.7
PCU2_D Track 6 PCM Configuration in upgraded Flexi BSC ..................................................... 108
9.6.8
PCU2_D Track 7 PCM Configuration in upgraded Flexi BSC ..................................................... 109
9.6.9
PCU2_E Track 6 PCM Configuration in upgraded Flexi BSC ..................................................... 110
9.6.10
PCU2_E Track 7 PCM Configuration in upgraded Flexi BSC ..................................................... 111
New delivery Flexi BSC BCSU Unit upgrade................................................................................................... 111
9.7.1
PCU2_E Index 8 PCM Configuration in new delivery Flexi BSC ................................................. 113
9.7.2
PCU2_E Index 10 PCM Configuration in new delivery Flexi BSC ............................................... 114
9.7.3
PCU2_E Index 12 PCM Configuration in new delivery Flexi BSC ............................................... 114
9.7.4
PCU2_E Index 4 PCM Configuration in new delivery Flexi BSC ................................................. 115
9.7.5
PCU2_E Index 6 PCM Configuration in new delivery Flexi BSC ................................................. 116

9.4

9.5

9.6

9.7

10
11

PEP Interface creation......................................................................................................................... 117


ET HW upgrade .................................................................................................................................. 118
11.1
11.2
11.3
11.4

12

Actions after upgrade & Post conditions .............................................................................................. 124


12.1
12.2
12.3
12.4
12.5
12.6

13

BSC2i ET HW upgrade .................................................................................................................................. 118


ET5C-4 Cartridge........................................................................................................................................... 118
BSC2i ET Configuration ................................................................................................................................. 120
BSC2i ET PCM-Cables .................................................................................................................................. 123
Implementation of the new optional feature ..................................................................................................... 124
PCU2 Scheduling weight parameters ............................................................................................................. 124
Check and update PCU boot software ............................................................................................................ 125
12.3.1
Chorus PCU boot SW versions ................................................................................................. 125
12.3.2
PCU2 boot SW versions ........................................................................................................... 126
Cartridge Marking Labels ............................................................................................................................... 127
BSC configuration printout (post-check) .......................................................................................................... 127
Fallback copying of the current package ......................................................................................................... 128

Appendix ............................................................................................................................................. 129


13.1
13.2

Appendix1: SW64B Jumper settings............................................................................................................... 129


Appendix2: PCU, PCU_S and PCU_T Jumper settings ................................................................................... 130

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

3 (149)

13.3
13.4
13.5
13.6
13.7
13.8
13.9

Appendix3: PCU2_U Jumper settings ............................................................................................................. 132


Appendix4: PCU_B Jumper settings ............................................................................................................... 134
Appendix5: PCU2_D Jumper settings ............................................................................................................. 136
Appendix6: PCU2_E Jumper settings ............................................................................................................. 139
Appendix7: EURO Connector is connected to PCU card ............................................................................. 141
Appendix8: Updating the boot packages of PCU, PCU_S, PCU_T, PCU_B pre-processor PIU(s) ..................... 142
Appendix9: Updating the boot packages of PCU2 pre-processor PIU(s) .......................................................... 146

Contact:
Contact your local Nokia Solutions and Networks support

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

4 (149)

Summary of changes:
1.0-0
1.1-0
1.2-0
1.3-0
1.4-0
1.5-0

1.6-0
1.7-0
1.8-0
1.9-0

st

1 approved version
Added CR75 details
Added connection settings for Linux in chapter 5.5.5.2.
Added note regarding COM issue in HIT3.3 in chapter
5.5.5.1.2 and 5.5.5.2.2.
Updated Memory requirements in Flexi BSC and BSC3i
in chapter 5.1.Also modified the contents in chapter 5.2.
Removed note regarding COM issue from chapters
5.5.5.1.2 and 5.5.5.2.2.Also updated the hit version as
3.4-0.
Added PCU2E strapping details for BSC3i 1000/2000,
BSC3i 660 GSW1KB, BSC3i 660 GSWB in appendix 6.
Updated appendix 6 by adding PCU2_E PCM interface
configuration pinheader details of all BSC variants.
Correction for PR NA05452928 updated in chapter 9.5.
The amount of PCU2-Es in BSCU updated in chapter 4.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

5 (149)

PURPOSE

This document describes the implementation of the Nokia DX200 GPRS/EDGE BSC Hardware . The
GPRS/EDGE Feature's functional descriptions are included in the documentation (NED). The Plug-in unit jumper
settings 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 the
Gb-interface to the SGSN, as well as how to set up the radio network for the GPRS/EDGE use, see NED
documentation.
NOTE! The BSCi and BSC2i (M92 HW) are not supported in S16.1 or newer releases

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

6 (149)

SCOPE OF APPLICATIONS

This document applies to BSC running with S16 software level onwards. Upgrade procedure allows to
install/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:
Local connection (COM)
Telnet
SSH
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 the
PCU OSW is controlled by license keys.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

7 (149)

USING THE DOCUMENT

3.1

General info

The BSC/PCU HW implementation for PS traffic (GPRS/EDGE) can be done using the HIT (Holistic Integration
Tester) 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 software
and the instructions are included in this manual. It is recommended that the HIT User's Manual is gone through
before starting the program.
When using the HIT for upgrading BSC, these instructions should be followed for a more detailed description of
the different phases, which take place during the upgrade. The upgrade macro menu dialog is designed to follow
closely this document.
NOTE: The commands executed by the HIT macro do not always match exactly with the commands presented in
the manual. This is because sometimes the automated tasks of the HIT macro require more commands and
different 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 commands
until 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 / HW
upgrade can be selected. Regardless of which macro (SW or HW upgrade) is wanted to run, the user always
starts with the same main macro.
Example of macro structure:
UPGMAIN.HIT
o Select wanted upgrade:
SOFTWARE UPGRADES
SW upgrade S15 -> S16

HARDWARE UPGRADES

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

8 (149)

HW upgrade 1
HW upgrade 2

Under each upgrade / tool there is an upgrade specific menu which describes the steps which can be executed
individually:
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 appear
at beginning of the name of the step. If step execution fails for some reason, macro stops and user can correct
the 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-run
the incomplete step from the menu. In this case, the user must complete that certain step manually, using this
documentation as guide. When the step has been completed manually, user can continue the macro execution
from next available step. Note, that in the upgrade menu, there will be Man. sign instead of Done. sign at
beginning 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 restart
whole macro.

3.2.2

Communication

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

3.2.3

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

Error situations

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

Macro completion

Log files

The upgrade macro provides different log files, from where the user can verify the executed steps in macro and
the success of the different steps & commands executed in the macro. There are three different kind of
information / log files:
Log file from HIT Response window (<BSC_C-NUMBER>.log)

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

9 (149)

This log contains all the information of the macro execution (each MML
command and the whole output of the macro execution)

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

Macro writes separate log files for following steps:


Configuration printout (PRE)
Firmware
Plug-in unit software upgrade
Safecopy
Transfer software to BSC
Configuration printout (PRE)

o
-

The same information can be found from both from a main log file
and 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.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

10 (149)

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 macro

Execution status (Done).

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. When
macro execution is started again, the log writing is continued from the end of existing log files. All previously
written log information remains intact and nothing is overwritten.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

11 (149)

INTRODUCTION

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

Fallback copying of the current software

BSC configuration printout (pre-check)

Preparation for the upgrade

GSWB extension (only for BSC2i)

Power upgrade to PSC6-D (only for BSC3i1000 or upgraded Flexi


BSC)

Command calendar

Check and copy databases to disks

Licence installation and feature activation

PCU (GPRS/EDGE) HW upgrade


o

BSCi BCSU unit upgrade

BSC2i BCSU unit upgrade

BSC3i 660 (GSWB) BCSU unit upgrade

BSC3i 660 (GSW1kB) BCSU unit upgrade

BSC3i 1000/2000 BCSU unit upgrade

Upgraded Flexi BSC BCSU unit upgrade

New delivery Flexi BSC BCSU unit upgrade

ET HW upgrade
o

BSC2i ET HW upgrade

ET5C-4 cartridge

BSC2i ET configuration

BSC2i ET PCM cables

Actions after upgrade & post conditions


o

Implementation of the new optional feature

Polling interval parameter

PCU2 scheduling weight parameters

Check and update PCU boot software

Cartridge marking labels

BSC configuration printout (post-check)

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

12 (149)

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 are
installed.
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 solved
before 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 units
in test bed before site visit.
During the macro execution the new PCU plug-in units will be created into hardware database. During this step
there 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 to
HW 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 be
deleted from the HW configuration.
The Nokia GSM/EDGE BSC product family:

Mech.

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

M92

BSC
variant
BSCi

M92

BSC2i

BSC2i, ANSI
version

BSCi

BSC2i, ETSI
version
M98

M98

BSC3i 660
BSC3i
1000
BSC3i
2000

BSC3i, ANSI
version

Flexi BSC

Flexi BSC,
ANSI version

BSC3i, ETSI
version

Flexi BSC, ETSI


version

High Capacity (upgraded and improved) version of


the first generation Base Station Controller
American National Standards Institute (ANSI)
version of the High Capacity, Base Station
Controller, DX 200 BSC2
European Telecommunications Standards Institute
(ETSI) version of the High Capacity, Base Station
Controller, DX 200 BSC2
American National Standards Institute (ANSI) High
Capacity version of the Base Station Controller,
BSC3i
European Telecommunications Standards Institute
(ETSI) High Capacity version of the Base Station
Controller, BSC3i
American National Standards Institute (ANSI) Flexi
BSC family based High Capacity Base Station
Controller
European Telecommunications Standards Institute
(ETSI) Flexi BSC family based High Capacity Base
Station Controller

Please note that there is in total of 6 different product variants of the Base Station Controller BSC3i 660, BSC3i
1000, BSC3i 2000, Flexi BSC) supported by S16 release. Only High Capacity BSC level of M92 mechanics BSC
is 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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

13 (149)

PCU statistics

PCU and BSC product variants


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

PCU

Packet Control Unit, a general term for all PCU versions

General name

Name of HW
Explanation
product variant

First Generation
PCU
Packet Control Unit - PCU-S
PCU1
PCU-T
PCU-B

First generation PCU for BSCi and BSC2i


First generation PCU for BSCi and BSC2i
First generation PCU for BSCi and BSC2i
First generation PCU for BSC3i, includes two
logical PCUs

Second Generation PCU2-U


Packet Control Unit - PCU2-D
PCU2

Second generation PCU for BSCi and BSC2i

PCU2-E

Second generation PCU for BSC3i & Flexi BSC,


includes two logical PCUs
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 enough
capacity (see chapter 8.6). Installing the first PCU plug-in unit into the BCSU(s) requires three SW64B plug-in
units in the GSWB (GSWB size 192 PCM(s)), installing the second PCU plug-in unit requires four SW64B plug-in
units in the GSWB (GSWB size 256 PCM(s)). If Gb over Frame Relay is used, then the operator also has to
consider the need for E1/T1 (ET) extensions.
Support of PCU2
PCU2 is a high capacity embedded plug-in unit that provides additional processing power and extended
functionality from BSS11.5 onwards. Second Generation PCU(s) have an enhanced design architecture that
enables the network to meet the real time traffic requirements of new services and provide means to new
enhanced 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, BSC3i
1000/2000, upgraded Flexi BSC and PCU2-E for BSC3i 660, BSC3i 1000/2000 and Flexi BSC.
PCU2-E
The PCU2-E plug-in unit can be used in various applications, which need DSP(s). The main application for PCU2E 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 the
maximum Abis connectivity with PCU2-E in any other configuration than Flexi BSC 3000/4200 (BSC3i 660, BSC3i
1000, 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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

14 (149)

PCU2-E can reside in BSC3i and Flexi BSC network elements. In upgraded Flexi BSC network element there can
maximum of two PCU2-Es in one cartridge (due to power supply restrictions) if power supply plug-in unit is not
upgraded to PSC6-D. But in new delivery Flexi BSC network element there can be up to 5 PCU2-Es in one BCSU
unit. Also in upgraded Flexi BSC network element there can be up to 5 PCU2-Es in one BCSU unit when BCSU
unit 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 bus
and amount of memory is 1 GB, no local bus SDRAM and boot FLASH
is on local bus)

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)

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

New voltages on boards


o

Changes to PCM MUX

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 after
PCU2-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 be
installed into BSC one by one. BCSU(s) are equipped with PCU(s) according traffic needs, i.e. PCU are added to
BCSU(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 have
different 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 and
according to traffic needs.
Asymmetrical PCU HW configuration introduces a definition of the primary spare BCSU. With Asymmetrical PCU
HW configuration the primary spare BCSU is configured to have enough PCU HW units to take over any of the
active BCSUs. The system will keep the primary spare BCSU as the spare BCSU by performing related BCSU
switchovers as soon as the BCSU statuses allow this. A related alarm is raised if the primary spare BCSU unit is
not in SP-EX state.
BSC DX platform keeps the primary spare unit as the SP-EX BCSU whenever possible. The BSC DX platform
automatically performs a prepared switchover in order to restore the primary spare BCSU to SP-EX state as soon
as 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 platform
cancels the alarm, when the primary spare unit is in SP-EX again.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

15 (149)

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 the
new 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/s
PCM line for the TRAU frames, internal 4 Mbit/s PCM line for the Frame Relay, the clock unit for the basic timing
signals, side selection and identification logic. The PCM interface is in the front panel (euroconnector). Two RJ45
connectors for the Ethernet and one for the RS232 interfaces are in the front panel. Other signals are in the
backplane connectors.
PCU:
two 2.048 Mbit/s PCM lines interfacing to the DSP processors,
two 2.048 Mbit/s PCM lines interfacing to the PowerQuicc II processor
two 10/100 BaseTx type Ethernet interfaces

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

16 (149)

PowerQuicc II Processor
DSP Processor with daughter card
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 Access
Control) interfaces in the BSC.
The PCU unit receives and transmits TRAU frames to the Base Stations and Frame Relay packets (Sub-network
Service) 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 RJ45
connectors: one for the RS232 interface and two for the LAN (Ethernet) interfaces. Other signals are in the
backplane 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 (DMC
backplane).
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 the
Motorola PowerQuicc II family processor MPC. One PQII block is connected to two 10/100BaseTx Ethernet PHY
interfaces, and the other block shares the same interfaces for redundancy reasons. Ethernet PHY interfaces are
connected to the backplane of the cartridge. The LAN interfaces are implemented using the PowerQuicc II
integrated Ethernet controller.
PCU_B implements both Gb and RLC (Radio Link Control) / MAC (Medium Access Control) interfaces in the
BSC.
The PCU unit receives and transmits TRAU frames to the Base Stations and Frame Relay packets (Sub-network
Service) 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 PCI
motherboard 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.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

17 (149)

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 PCI
motherboard 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 PCU
configuration 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 PCU
plug-in units installed in every BCSU unit).

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

18 (149)

BSC2i
4th SW64B
PLUG-IN UNIT
AND THE SWBUS4
FRONT PANEL
CONNECTOR
IS ADDED
TO THE GSWB UNITS

BCE
E

BCB
E

CC19V

R2A1-S

PSA20_0

PSA20_1

PSA20_2

PSA20_3

PSFP0

PSFP1

PSFP2

PSFP3

GSWB 0 GSWB 1 CLS


SW1C1 CLOC

SW1C0
01

37

19

CLS
CLAC
01

ET
5C
2

13

ET
5C
3

25

152

ET
5C
4
6

01
120

37

CBD 8

MCMU 0

MCMU 1

BCSU 3

BCSU 4

MC1C

MC1C

MC1C

MC1C

27

01

01

27

OMU

BCSU 5

MC1C

SD3C-S

BCSU 6

MC1C
01

2nd PCU, PACKET


CONTROL UNIT, IS
ADDED TO THE BCSU.
PCM CONNECTION TO
THE GSWB IS MADE
FROM THE PLUG-IN
UNITS FRONT PANEL,
USING CFNxxx CABLES

ET
5C
0

13

01

BCSU 0

BCSU 7

MC1C

MC1C

058

BCSU 8
MC1C
27

01

27

BCSU 1

BCSU 2

MC1C

MC1C

01

27

GPRS/EDGE OPTION

4.4

27

ET
5C
1

MC1C

01

27

088

ET
5C
5
01
5

ET
5C
6
13
5

ET
5C
7
5

030

ET
5C
8
5

002
S10 provides two new ET5C
CARTRIDGES

BSC3i 660 Hardware

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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

19 (149)

BSCC
CPGO

CPRJ45

CPGO

PDFU 2

PDFU 3

PDFU-A

PDFU-A

PDFU-A

PDFU-A

GSWB 0 GSWB 1
SW1C-C

SW1C-C

CLOC-B

PDFU 1

CLS 0,1

PDFU 0

MCMU 0 MCMU 1
CC4C-A

CC4C-A

FTRB 0

CC3C-A

OMU
CM2C-A

FTRB 1

BCSU 0

BCSU 1

BCSU 2

CC3C-A

CC3C-A

CC3C-A

BCSU 3

BCSU 4

BCSU 5

CC3C-A

CC3C-A

CC3C-A

FTRB 2

4.5

BCSU 6

FTRB 3

ET4C 0

ET4C 1

ET4C-B
(32*ET2E/A)

ET4C-B
(30*ET2E/A)

BSC3i 1000/2000 Hardware

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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

20 (149)

4.6

Upgraded Flexi BSC Hardware

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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

21 (149)

upgraded BSC3i 3000/4200


(CC3C-A used as BCSU)

BSCC

CPGO

PDFU

L
A

CPETS-G / CPETS-E /
CPETC-E

CPRJ45-A

PDFU

0 CPETS-H /
CPETS-F /
CPETC-F

L
A

PDFU

PDFU

C SW10C-A
L

PDFU

L
A

L
A

CM2C-A

CC4C-A

OMU
CPETS-G /
1 CPETS-E /
CPETC-E
CPETS-G /
2 CPETS-E /
CPETC-E

FTRB 1

CC3C-A

BCSU 2

BCSU 1

BCSU 0

CC3C-A

CC3C-A

CC3C-A

BCSU 5

BCSU 4

BCSU 3

FTRB 3

GTIC
1

GTIC
0

4
C

GT4C-A

C
L

CPETS-G /
1 CPETS-E /
CPETC-E
CPETS-G /
2 CPETS-E /
CPETC-E

SW10C-A

SW10C-A

3
CC4C-A

0
CC4C-A

FTRB 1

FTRB 0
6

CC3C-B

CC3C-B

BCSU 2

BCSU 1

BCSU 0

CC3C-B

CC3C-B

CC3C-B

BCSU 5

BCSU 4

BCSU 3

FTRB 3

FTRB 2

8
GT4C-A

GT4C-A

BCSU 6

GTIC
1

GTIC
0

4
C

CC3C-A

C
L

REAR SIDE

4.7

BCSU 6
5

REAR SIDE

New delivery Flexi BSC Hardware


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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

CC3C-B

5
9

MCMU MCMU
1
0

CC3C-B

CPETS-G /
3 CPETS-E /
CPETC-E
4 CPETS-H /
CPETS-F /
CPETC-F

FTRB 2

8
GT4C-A

CM2C-A

C
L

OMU

FTRB 0
6

10

CC4C-A

CC3C-A

PDFU

GSW2KB GSW2KB
1
0

MCMU MCMU
1
0

CC3C-A

CPETS-G /
3 CPETS-E /
CPETC-E
4 CPETS-H /
CPETS-F /
CPETC-F

PDFU

GSW2KB GSW2KB
1
0

10

CPETS-G / CPETS-E /
CPETC-E

CPRJ45-A

PDFU

0 CPETS-H /
CPETS-F /
CPETC-F

SW10C-A

BSCC

CPGO

0
0

upgraded BSC3i 3000/4200


(CC3C-B used as BCSU)

22 (149)

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

CPETS-G/
CPETS-E/
CPETC-E

BSCC-E
T0.8

CPRJ45-A T0.4

T0.0

PDFU 0
PDFU-B

CLS 0

PDFU 1
PDFU-APDFU-B

ETC 1

ETC 0

GTIC 0

SGC1C-A

GSW2KB-A
0

ETC 3

ETC 2

GTIC 1

SGC1C-A
6

MCMU 1

FTRB 1 (FTRB-A)
OMU
CC3C-A

GSW2KB-A
1

FTRB 0 (FTRB-A)
MCMU 0

CLS 1

BCSU 0
CC3C-B

DC3C-B

BCSU 5

BCSU 3

LANU 0

BCSU 1

BC1C-B

BCSU 6

BCSU 4
BC1C-B

FTRB 2 (FTRB-A)
LANU 1

FTRB 3 (FTRB-A)

BCSU 2

REAR VIEW

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

23 (149)

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 Requirements
for 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 Asymmetrical
HW 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 other
type of PCU2 plug-in units). However, if macro is stopped during installation and started again, the installation can
be 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 maximum
two PCU2-E plug-in units can be installed to one cartridge. Power supply plug-in unit must be upgraded to PSC6D if three or more PCU2-E plug-in units are needed This upgrading can be done already before starting the
upgrade (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 from
PCU2-E cards before recreation.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

24 (149)

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)

5.4

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

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

needed amount of PSC6-D plug-in units when planned to install more than two
PCU2-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 approximately
5MB.

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 software
has 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 installation
of the software is done by executing the SETUP.EXE -program and following the instructions of the installation
program.

5.5.3

Installing HIT upgrading macros

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

25 (149)

After the HIT program has been installed, it is necessary to install the upgrading macros. The upgrading macros
are included in the Release Binder which can be found from NOLS (Nokia Online Services). Release binder
contains 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 will
appear:

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 user
executable 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 communications
port. This needs to be done, because some PCs communications port handling is unreliable with this setting
active.
It is recommended that you contact your local PC support for instructions on how to turn off the use of FIFO
buffers.
If you are familiar with the settings of the PC, here's an example of how to turn the use of FIFO buffers off. In
Windows 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) and


double-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 press
OK

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 is
recommended to use the network element name for the devices.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

26 (149)

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:
Local connection (COM)
Telnet
SSH
Via Netact (SSH)
Note: in S16 level onwards, via Netact (SSH) is only allowed.
5.5.5.1
1.1.1.1.1

Connection settings for Windows


5.5.5.1.1 Configuration example for creating Telnet / SSH / NetAct connection

Select Device > Set Configuration from menu.


Following window appears

Select New

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

27 (149)

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 in
Type/Protocol: field. Default port for telnet is 23 and for SSH is 22.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

28 (149)

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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

29 (149)

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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

30 (149)

Select Terminal sheet and define the MML log file.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

31 (149)

If connection type is Telnet, press OK.


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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

32 (149)

After defining SSH related parameters, Press OK.


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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

33 (149)

Note! COM connection is selected


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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

34 (149)

Select Terminal sheet and define the MML log file.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

35 (149)

Press OK.

5.5.5.2
1.1.1.1.3

Connection settings for Linux


5.5.5.2.1 Configuration example for creating Telnet / SSH / NetAct connection

Select Edit> Devices > from menu


Following window appears

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

36 (149)

Select New

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

37 (149)

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 in
Type/Protocol: field. Default port for telnet is 23 and for SSH is 22.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

38 (149)

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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

39 (149)

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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

40 (149)

Select Terminal sheet and define the MML log file.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

41 (149)

If connection type is Telnet, press OK.


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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

42 (149)

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 menu
Following window appears

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

43 (149)

Note! COM connection is selected


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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

44 (149)

Select Terminal sheet and define the MML log file.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

45 (149)

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 are
printed out. It is recommended to keep Messages window as big as possible to able to follow up the macro
execution. The important information is printed out to the messages window.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

46 (149)

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 to
execute. Clicking CANCEL in main menu aborts the macro execution.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

47 (149)

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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

48 (149)

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 to
NetAct server.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

49 (149)

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.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

50 (149)

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

ZWQO:RUN;
Check from the output that all the computer units which are currently in use are running on correct
software package with the status BU. If the software package status is FB or NW, find out the cause
for 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 following
commands:

ZAHO;
ZABO;
ZEOL;
ZEOE;
Alarm printings can be skipped and macro asks user about the wanted action with following pop-up:

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

51 (149)

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 upgrade
execution. The same MML connection usage for interrogate or modification purposes may confuse the macro
execution.

The procedure dialog is divided in main chapters, which may also contain sub-chapters. Chapters and their subchapters 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.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

52 (149)

Select a step to run and press OK.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

53 (149)

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 current
package.
Manually, the fallback copying can be made following the document: Fallback copying in BSC. The document
can be found from NED.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

54 (149)

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. The
checking can be made by using the macro (S16UPGMAIN.HIT) or manually following the instructions from BSC
configuration printout-document delivered in Release Binder.
For macro execution, choose the BSC configuration printout (pre) step in BSC/PCU HW implementation for PS
traffic procedure.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

55 (149)

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 an
hour. GSWB hardware is installed first by using MCMU-0 for the HW extension and then by making an MCMU
switchover. 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 SWICOPprocess properly.
Change the state of the MCMU from SP-EX to state SE-NH:

ZUSC:MCMU,<index>:TE,;
ZUSC:MCMU,<index>:SE,;
ZUSC:MCMU,<index>:SE,;
Switch the MCMU cartridge power off from the PSC3 power supply.
Print the GSWB hardware configuration with commands:

ZWTI:P:MCMU,<index>;
ZWTI:P:GSW,<index>;
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. Connectors
in the motherboard of the cartridge are tight, and if the plug-in unit's connector is not
in full contact with the motherboard, the fault may appear later on, when the BSC has
been 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 to
the back of the SW1C cartridge (see cable lists in the BCSU section for details). 1/4
EURO Connector of CFNPCM cable is connected to the PCU card and 1/8
connector to the GSWB.
5. BSC2E and BSC2i optional: Install the PCM cables for the ET5C cartridges

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

56 (149)

6. After the GSWB HW and PCM cables are installed, switch the GSWB cartridge
power on again.
When installing the PCM cabling, avoid sharp bends and make sure that the cables are not pulled too tight. The
BSC may be carrying traffic during the HW upgrade and, therefore, special care must be taken to avoid
disconnecting other cables or connectors.
Create an SW64B plug-in unit(s):

ZWTP:GSW,<index>:SW64B,2,4;
and/or

ZWTP:GSW,<index>:SW64B,3,5;
Switch the MCMU cartridge power on from the PSC3 power supply.
Change the MCMU state to TE-EX:

ZUSC:MCMU,<index>:SE,;
ZUSC:MCMU,<index>:TE,;

00

01

02

03

04

05

PSC1

SW64B

SW64B

SW64B

SW64B

SWBUS4

06

07

Picture 12. The GSWB SW1C cartridge


Run diagnostics.

ZUDU:MCMU,<index>;
If diagnostics fail, follow the steps described in Diagnosis Reports, Alarm Reference Manual. Once the
diagnostics have been passed, change the MCMU state to SP-EX.

ZUSC:MCMU,<index>:SP,;
Make an MCMU switchover.

ZUSC:MCMU,<WO_index>:SP,;

Repeat these steps also for MCMU-1 unit.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

57 (149)

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 unit
amount per BCSU is more than two. After the power upgrade, maximum amount (five pieces) of PCU2-E can be
installed to each BCSU unit.
Change the BCSU state from SP-EX to SE-NH:

ZUSC:BCSU,<index>:TE,;
ZUSC:BCSU,<index>:SE,;
ZUSC:BCSU,<index>:SE,;
Switch the BCSU cartridge power off from the PSC6-A or PSC6-B power supply. Remove old plug-in unit and
install the new PSC6-D to same track.
Delete PSC6-A or PSC6-B equipment information with following command:

ZWTQ:<BCSU_index>:<PSC6-A/PSC6-B>,0:;
Create new PSC6-D plug-in unit.

ZWTP:<BCSU_index>:PSC6_D,0,1;
Switch the BCSU power on after new equipment is created and change the BCSU state to TE-EX.

ZUSC:BCSU,<index>:SE,;
ZUSC:BCSU,<index>:TE,;
Alter BCSU has restarted to TE-EX state, execute the diagnostic:

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

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

ZUSC:BCSU,<index>: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 calendar
tasks must be stopped before the upgrade.
Check the current tasks with command:

ZICL;
The calendar tasks are to be stopped with command:

ZICB:<id>:BLOCK;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

58 (149)

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:<active_package>:%,%;
ZIWX::WB,NODEF:<active_package>:%,%;
ZIWL::WSB,NODEF::LICENCE,200,2,<initials>;
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:


DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

59 (149)

ZW7L:<licence_file_name>: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. for
NetAct licence management purpose in later OSS releases.
More information of licences in the BSC can be found from Technical Bulletin: SW Bulletin licensing.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

60 (149)

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 are
possible to install) are handled separately.
1)

First, macro asks if change to BCSU unit PCU configuration is needed or not. If NO is chosen the
unit 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 delete
existing 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 only
for PCU2-E usage.
When PCU2-D or PCU2-E plug-in unit installation is chosen in case of BSC3i 1000/2000, upgraded Flexi BSC or
new deliver Flexi BSC, the macro asks from user whether the new Packet Abis feature PCU installation is

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

61 (149)

needed or not. If No is chosen, the PCU unit will be equipped as using normal functions (PCUDSP and
PCUPPC). 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 (with
remove -function of this macro) and then re-created (by using add) with the packet Abis mode. Note that when
deleting the PCU2_Es, if Gb over IP is in use the IP addresses of the affected PCU's (along with the Gb over IP
configuration) 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 is
activated, it will be taken out of use for PCU installation phase because BCSU switchovers cannot be executed
successfully 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 next
BCSU 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.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

62 (149)

9.1

BSCi BCSU Unit Upgrade

GPRS/EDGE hardware is installed using a spare BCSU for the HW upgrade and by making BCSU switchovers
until 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 and
PCU_T Jumper settings or Appendix3, PCU2_U Jumper settings).
First, change the BCSU state from SP-EX to SE-NH:

ZUSC:BCSU,<index>:TE,;
ZUSC:BCSU,<index>:SE,;
ZUSC:BCSU,<index>:SE,;
Switch the BCSU cartridge power off from the PSC3 power supply.
Create GB interface to BCSU if needed:

ZQRA:BCSU,<index> :<PCU_type>,<PCU_index> :IFETH0::UP;


ZQRA:BCSU,<index> :<PCU_type>,<PCU_index> :IFETH1::UP;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

63 (149)

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 to
the EQUIPM database with the following MML-command (used Plug-in unit can be PCU, PCU_S, PCU_T or
PCU2_U):

ZWTP:BCSU,0:<PCU_type>,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;
ZWTP:BCSU,1:<PCU_type>,4,9::PCUDSP,4,160,TSL,0&&31:PCUDSP,4,161,TSL,0&&31:
PCUPPC,4,162,TSL,0&&31:PCUPPC,4,163,TSL,0&&31;
ZWTP:BCSU,2:<PCU_type>,4,9::PCUDSP,4,164,TSL,0&&31:PCUDSP,4,165,TSL,0&&31:
PCUPPC,4,166,TSL,0&&31:PCUPPC,4,167,TSL,0&&31;
ZWTP:BCSU,3:<PCU_type>,4,9::PCUDSP,4,168,TSL,0&&31:PCUDSP,4,169,TSL,0&&31:
PCUPPC,4,170,TSL,0&&31:PCUPPC,4,171,TSL,0&&31;
ZWTP:BCSU,4:<PCU_type>,4,9::PCUDSP,4,172,TSL,0&&31:PCUDSP,4,173,TSL,0&&31:
PCUPPC,4,174,TSL,0&&31:PCUPPC,4,175,TSL,0&&31;
ZWTP:BCSU,5:<PCU_type>,4,9::PCUDSP,4,176,TSL,0&&31:PCUDSP,4,177,TSL,0&&31:
PCUPPC,4,178,TSL,0&&31:PCUPPC,4,179,TSL,0&&31;
ZWTP:BCSU,6:<PCU_type>,4,9::PCUDSP,4,180,TSL,0&&31:PCUDSP,4,181,TSL,0&&31:
PCUPPC,4,182,TSL,0&&31:PCUPPC,4,183,TSL,0&&31;
ZWTP:BCSU,7:<PCU_type>,4,9::PCUDSP,4,184,TSL,0&&31:PCUDSP,4,185,TSL,0&&31:
PCUPPC,4,186,TSL,0&&31:PCUPPC,4,187,TSL,0&&31;
ZWTP:BCSU,8:<PCU_type>,4,9::PCUDSP,4,188,TSL,0&&31:PCUDSP,4,189,TSL,0&&31:
PCUPPC,4,190,TSL,0&&31:PCUPPC,4,191,TSL,0&&31;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

64 (149)

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

ZWUC:BCSU,<index>:<PCU_type>,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

Use

1.10
0
1.10
1

BCBE

BCSU 0 / PCU

089.27F 09R1

BCBE

SW1C 0

151.01B 04R8

CFN016

PCM

BCBE

BCSU 0 / PCU

089.27F 09R3

BCBE

SW1C 1

123.01B 04R8

CFN012

PCM

1.10
2
1.10
3

BCBE

BCSU 1 / PCU

027.01F 09R1

BCBE

SW1C 0

151.01B 04S1

CFN025

PCM

BCBE

BCSU 1 / PCU

027.01F 09R3

BCBE

SW1C 1

123.01B 04S1

CFN022

PCM

1.10
4
1.10
5

BCBE

BCSU 2 / PCU

027.27F 09R1

BCBE

SW1C 0

151.01B 04S2

CFN023

PCM

BCBE

BCSU 2 / PCU

027.27F 09R3

BCBE

SW1C 1

123.01B 04S2

CFN020

PCM

Cable list for BCEE rack:

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

65 (149)

No.

Rack

FE

Connector

Rack

FE

Connector

Type

Use

2.10
0
2.10
1

BCEE

BCSU 3 / PCU

061.01F 09R1

BCBE

SW1C 0

151.01B 04S3

CFN030

PCM

BCEE

BCSU 3 / PCU

061.01F 09R3

BCBE

SW1C 1

123.01B 04S3

CFN026

PCM

2.10
2
2.10
3

BCEE

BCSU 4 / PCU

061.27F 09R1

BCBE

SW1C 0

151.01B 04S4

CFN026

PCM

BCEE

BCSU 4 / PCU

061.27F 09R3

BCBE

SW1C 1

123.01B 04S4

CFN022

PCM

2.10
4
2.10
5

BCEE

BCSU 5 / PCU

027.01F 09R1

BCBE

SW1C 0

151.01B 04S5

CFN033

PCM

BCEE

BCSU 5 / PCU

027.01F 09R3

BCBE

SW1C 1

123.01B 04S5

CFN030

PCM

2.10
6
2.10
7

BCEE

BCSU 6 / PCU

027.27F 09R1

BCBE

SW1C 0

151.01B 04S6

CFN030

PCM

BCEE

BCSU 6 / PCU

027.27F 09R3

BCBE

SW1C 1

123.01B 04S6

CFN026

PCM

2.10
8
2.10
9

BCEE

BCSU 7 / PCU

000.01F 09R1

BCBE

SW1C 0

151.01B 04S7

CFN036

PCM

BCEE

BCSU 7 / PCU

000.01F 09R3

BCBE

SW1C 1

123.01B 04S7

CFN032

PCM

2.11
0
2.11
1

BCEE

BCSU 8 / PCU

000.27F 09R1

BCBE

SW1C 0

151.01B 04S8

CFN033

PCM

BCEE

BCSU 8 / PCU

000.27F 09R3

BCBE

SW1C 1

123.01B 04S8

CFN030

PCM

See Appendix7, EURO Connector is connected to PCU


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

ZUSC:BCSU,<index>:SE,;
ZUSC:BCSU,<index>:TE,;
After PCU installation, boot software checking is done. If update is needed, macro executes update according
instructions 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,<index>:C=DSK;
Alter restart execute diagnostic:

ZUDU:BCSU,<index>;
If diagnostic fail, follow the steps described in Diagnosis Reports, Alarm Reference Manual. Once the
diagnostics have been passed, change the BCSU state to SP-EX:

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

ZUSC:BCSU,<index>:SP,;
Repeat these steps for all BCSU(s).
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

66 (149)

9.2

BSC2i BCSU Unit upgrade

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

ZUSC:BCSU,<index>:TE,;
ZUSC:BCSU,<index>:SE,;
ZUSC:BCSU,<index>: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 and
PCU_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,<index> :<PCU_type>,<PCU_index> :IFETH0::UP;


ZQRA:BCSU,<index> :<PCU_type>,<PCU_index> :IFETH1::UP;

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

ZUSC:BCSU,<index>:SE,;
ZUSC:BCSU,<index>:TE,;
After PCU installation, boot software checking is done. If update is needed, macro executes update according
instructions 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.
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

67 (149)

ZUSU:BCSU,<index>:C=DSK;
Alter restart execute diagnostic:

ZUDU:BCSU,<index>;

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

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

ZUSC:BCSU,<index>: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 be
defined 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 can
be PCU, PCU_S, PCU_T or PCU2_U):

ZWTP:BCSU,0:<PCU_type>,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;
ZWTP:BCSU,1:<PCU_type>,4,9::PCUDSP,4,160,TSL,0&&31:PCUDSP,4,161,TSL,0&&31:
PCUPPC,4,162,TSL,0&&31:PCUPPC,4,163,TSL,0&&31;
ZWTP:BCSU,2:<PCU_type>,4,9::PCUDSP,4,164,TSL,0&&31:PCUDSP,4,165,TSL,0&&31:
PCUPPC,4,166,TSL,0&&31:PCUPPC,4,167,TSL,0&&31;
ZWTP:BCSU,3:<PCU_type>,4,9::PCUDSP,4,168,TSL,0&&31:PCUDSP,4,169,TSL,0&&31:
PCUPPC,4,170,TSL,0&&31:PCUPPC,4,171,TSL,0&&31;
ZWTP:BCSU,4:<PCU_type>,4,9::PCUDSP,4,172,TSL,0&&31:PCUDSP,4,173,TSL,0&&31:
PCUPPC,4,174,TSL,0&&31:PCUPPC,4,175,TSL,0&&31;
ZWTP:BCSU,5:<PCU_type>,4,9::PCUDSP,4,176,TSL,0&&31:PCUDSP,4,177,TSL,0&&31:
PCUPPC,4,178,TSL,0&&31:PCUPPC,4,179,TSL,0&&31;
ZWTP:BCSU,6:<PCU_type>,4,9::PCUDSP,4,180,TSL,0&&31:PCUDSP,4,181,TSL,0&&31:
PCUPPC,4,182,TSL,0&&31:PCUPPC,4,183,TSL,0&&31;
ZWTP:BCSU,7:<PCU_type>,4,9::PCUDSP,4,184,TSL,0&&31:PCUDSP,4,185,TSL,0&&31:
PCUPPC,4,186,TSL,0&&31:PCUPPC,4,187,TSL,0&&31;
ZWTP:BCSU,8:<PCU_type>,4,9::PCUDSP,4,188,TSL,0&&31:PCUDSP,4,189,TSL,0&&31:
PCUPPC,4,190,TSL,0&&31:PCUPPC,4,191,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

68 (149)

ZWUC:BCSU,<index>:<PCU_type>,4;
DMCT2-S terminators are already installed in the High Capacity BSCi and BSC2i. Check that terminators are
installed. 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 be
defined 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 can
be PCU, PCU_S, PCU_T or PCU2_U):

ZWTP:BCSU,0:<PCU_type>,3,8::PCUDSP,4,152,TSL,0&&31:PCUDSP,4,153,TSL,0&&31:
PCUPPC,4,154,TSL,0&&31:PCUPPC,4,155,TSL,0&&31;
ZWTP:BCSU,1:<PCU_type>,3,8::PCUDSP,4,192,TSL,0&&31:PCUDSP,4,193,TSL,0&&31:
PCUPPC,4,194,TSL,0&&31:PCUPPC,4,195,TSL,0&&31;
ZWTP:BCSU,2:<PCU_type>,3,8::PCUDSP,4,196,TSL,0&&31:PCUDSP,4,197,TSL,0&&31:
PCUPPC,4,198,TSL,0&&31:PCUPPC,4,199,TSL,0&&31;
ZWTP:BCSU,3:<PCU_type>,3,8::PCUDSP,4,200,TSL,0&&31:PCUDSP,4,201,TSL,0&&31:
PCUPPC,4,202,TSL,0&&31:PCUPPC,4,203,TSL,0&&31;
ZWTP:BCSU,4:<PCU_type>,3,8::PCUDSP,4,204,TSL,0&&31:PCUDSP,4,205,TSL,0&&31:
PCUPPC,4,206,TSL,0&&31:PCUPPC,4,207,TSL,0&&31;
ZWTP:BCSU,5:<PCU_type>,3,8::PCUDSP,4,208,TSL,0&&31:PCUDSP,4,209,TSL,0&&31:
PCUPPC,4,210,TSL,0&&31:PCUPPC,4,211,TSL,0&&31;
ZWTP:BCSU,6:<PCU_type>,3,8::PCUDSP,4,212,TSL,0&&31:PCUDSP,4,213,TSL,0&&31:
PCUPPC,4,214,TSL,0&&31:PCUPPC,4,215,TSL,0&&31;
ZWTP:BCSU,7:<PCU_type>,3,8::PCUDSP,4,216,TSL,0&&31:PCUDSP,4,217,TSL,0&&31:
PCUPPC,4,218,TSL,0&&31:PCUPPC,4,219,TSL,0&&31;
ZWTP:BCSU,8:<PCU_type>,3,8::PCUDSP,4,220,TSL,0&&31:PCUDSP,4,221,TSL,0&&31:
PCUPPC,4,222,TSL,0&&31:PCUPPC,4,223,TSL,0&&31;

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

ZWUC:BCSU,<index>:<PCU_type>,3;

9.2.3

BSC2i PCU PCM-Cables, track 9

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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

69 (149)

No.

Rack

FE

Connector

Rack

FE

Connector

Type

Use

1.100
1.101

BCBE
BCBE

BCSU 0 / PCU
BCSU 0 / PCU

030.27F 09R1
030.27F 09R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 04R8
120.19B 04R8

CFN020
CFN018

PCM
PCM

1.102
1.103

BCBE
BCBE

BCSU 1 / PCU
BCSU 1 / PCU

002.01F 09R1
002.01F 09R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 04S1
120.19B 04S1

CFN026
CFN024

PCM
PCM

1.104
1.105

BCBE
BCBE

BCSU 2 / PCU
BCSU 2 / PCU

002.27F 09R1
002.27F 09R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 04S2
120.19B 04S2

CFN024
CFN022

PCM
PCM

Cable list for BCEE rack:


No.

Rack

FE

Connector

Rack

FE

Connector

Type

Use

2.100
2.101

BCEE
BCEE

BCSU 3 / PCU
BCSU 3 / PCU

088.01F 09R1
088.01F 09R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 04S3
120.19B 04S3

CFN016
CFN014

PCM
PCM

2.102
2.103

BCEE
BCEE

BCSU 4 / PCU
BCSU 4 / PCU

088.27F 09R1
088.27F 09R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 04S4
120.19B 04S4

CFN018
CFN016

PCM
PCM

2.104
2.105

BCEE
BCEE

BCSU 5 / PCU
BCSU 5 / PCU

058.01F 09R1
058.01F 09R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 04S5
120.19B 04S5

CFN024
CFN022

PCM
PCM

2.106
2.107

BCEE
BCEE

BCSU 6 / PCU
BCSU 6 / PCU

058.27F 09R1
058.27F 09R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 04S6
120.19B 04S6

CFN022
CFN020

PCM
PCM

2.108
2.109

BCEE
BCEE

BCSU 7 / PCU
BCSU 7 / PCU

030.01F 09R1
030.01F 09R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 04S7
120.19B 04S7

CFN028
CFN026

PCM
PCM

2.110
2.111

BCEE
BCEE

BCSU 8 / PCU
BCSU 8 / PCU

030.27F 09R1
030.27F 09R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 04S8
120.19B 04S8

CFN026
CFN024

PCM
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

Use

1.110
1.111

BCBE
BCBE

BCSU 0 / PCU
BCSU 0 / PCU

030.27F 08R1
030.27F 08R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 04R7
120.19B 04R7

CFN020
CFN018

PCM
PCM

1.112
1.113

BCBE
BCBE

BCSU 1 / PCU
BCSU 1 / PCU

002.01F 08R1
002.01F 08R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 05R1
120.19B 05R1

CFN026
CFN024

PCM
PCM

1.114
1.115

BCBE
BCBE

BCSU 2 / PCU
BCSU 2 / PCU

002.27F 08R1
002.27F 08R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 05R2
120.19B 05R2

CFN024
CFN022

PCM
PCM

Cable list for BCEE rack:

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

70 (149)

No.

Rack

FE

Connector

Rack

FE

Connector

Type

Use

2.120
2.121

BCEE
BCEE

BCSU 3 / PCU
BCSU 3 / PCU

088.01F 08R1
088.01F 08R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 05R3
120.19B 05R3

CFN016
CFN014

PCM
PCM

2.122
2.123

BCEE
BCEE

BCSU 4 / PCU
BCSU 4 / PCU

088.27F 08R1
088.27F 08R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 05R4
120.19B 05R4

CFN018
CFN016

PCM
PCM

2.124
2.125

BCEE
BCEE

BCSU 5 / PCU
BCSU 5 / PCU

058.01F 08R1
058.01F 08R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 05R5
120.19B 05R5

CFN024
CFN022

PCM
PCM

2.126
2.127

BCEE
BCEE

BCSU 6 / PCU
BCSU 6 / PCU

058.27F 08R1
058.27F 08R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 05R6
120.19B 05R6

CFN022
CFN020

PCM
PCM

2.128
2.129

BCEE
BCEE

BCSU 7 / PCU
BCSU 7 / PCU

030.01F 08R1
030.01F 08R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 05R7
120.19B 05R7

CFN028
CFN026

PCM
PCM

2.130
2.131

BCEE
BCEE

BCSU 8 / PCU
BCSU 8 / PCU

030.27F 08R1
030.27F 08R3

BCBE
BCBE

SW1C 0
SW1C 1

120.01B 05R8
120.19B 05R8

CFN026
CFN024

PCM
PCM

See Appendix7, EURO Connector is connected to PCU

9.3

BSC3i 660 (GSWB) BCSU Unit upgrade

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

ZUSC:BCSU,<index>:TE,;
ZUSC:BCSU,<index>:SE,;
ZUSC:BCSU,<index>:SE,;
Switch the BCSU cartridge power off from the PSC6-A or PSC6-B power supply.
Check that all the PCU plug-in unit jumpers are set according to the instructions (Appendix4, PCU_B Jumper
settings, Appendix5, PCU2_D Jumper settings or Appendix6, PCU2-E Jumper settings)
PCU2-E supported only 4M full mode PCM(s). There is a limit of one PCU2-E PIU on a BCSU. Exceeding the limit
may damage the power supply.
1. Install the PCU_B/PCU2_D/PCU2_E to BCSU track 6, see chapters 9.3.1, 9.3.3 or 9.3.5.
2. Install the PCU_B/PCU2_D/PCU2-E to BCSU track 7, see chapters 9.3.2, 9.3.4 or 9.3.6.
Create GB interface to BCSU if needed:

ZQRA:BCSU,<index> :<PCU_type>,<PCU_index> :IFETH0::UP;


ZQRA:BCSU,<index> :<PCU_type>,<PCU_index> :IFETH1::UP;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

71 (149)

Switch the BCSU cartridge power on from the PSC6-A or PSC6-B power supply.
Change the BCSU state to TE-EX.

ZUSC:BCSU,<index>:SE,;
ZUSC:BCSU,<index>:TE,;
After PCU installation, boot software checking is done. If update is needed, macro executes update according
instructions 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,<index>:C=DSK;
Alter restart execute diagnostic:

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

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

ZUSC:BCSU,<index>:SP,;
In case of PCU2-E installation, BCSU-0 (primary spare unit) is changed to SP-EX state and after that switchover
will be done to BCSU unit to be upgraded next.

Repeat these steps for all BCSU(s).


9.3.1

PCU_B Track 6 PCM Configuration in BSC3i

Install the PCU_B to BCSU track 6. 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_B plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU_B,3,6::PCUDSP,4,130,TSL,0&&31,1:PCUDSP,4,131,TSL,0&&31,1:P
CUPPC,4,67,TSL,0&&31,0;
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

72 (149)

ZWTP:BCSU,0:PCU_B,4,6::PCUDSP,4,128,TSL,0&&31,1:PCUDSP,4,129,TSL,0&&31,1:P
CUPPC,4,66,TSL,0&&31,0;
ZWTP:BCSU,1:PCU_B,3,6::PCUDSP,4,134,TSL,0&&31,1:PCUDSP,4,135,TSL,0&&31,1:P
CUPPC,4,71,TSL,0&&31,0;
ZWTP:BCSU,1:PCU_B,4,6::PCUDSP,4,132,TSL,0&&31,1:PCUDSP,4,133,TSL,0&&31,1:P
CUPPC,4,70,TSL,0&&31,0;
ZWTP:BCSU,2:PCU_B,3,6::PCUDSP,4,138,TSL,0&&31,1:PCUDSP,4,139,TSL,0&&31,1:P
CUPPC,4,75,TSL,0&&31,0;
ZWTP:BCSU,2:PCU_B,4,6::PCUDSP,4,136,TSL,0&&31,1:PCUDSP,4,137,TSL,0&&31,1:P
CUPPC,4,74,TSL,0&&31,0;
ZWTP:BCSU,3:PCU_B,3,6::PCUDSP,4,142,TSL,0&&31,1:PCUDSP,4,143,TSL,0&&31,1:P
CUPPC,4,79,TSL,0&&31,0;
ZWTP:BCSU,3:PCU_B,4,6::PCUDSP,4,140,TSL,0&&31,1:PCUDSP,4,141,TSL,0&&31,1:P
CUPPC,4,78,TSL,0&&31,0;
ZWTP:BCSU,4:PCU_B,3,6::PCUDSP,4,146,TSL,0&&31,1:PCUDSP,4,147,TSL,0&&31,1:P
CUPPC,4,83,TSL,0&&31,0;
ZWTP:BCSU,4:PCU_B,4,6::PCUDSP,4,144,TSL,0&&31,1:PCUDSP,4,145,TSL,0&&31,1:P
CUPPC,4,82,TSL,0&&31,0;
ZWTP:BCSU,5:PCU_B,3,6::PCUDSP,4,150,TSL,0&&31,1:PCUDSP,4,151,TSL,0&&31,1:P
CUPPC,4,87,TSL,0&&31,0;
ZWTP:BCSU,5:PCU_B,4,6::PCUDSP,4,148,TSL,0&&31,1:PCUDSP,4,149,TSL,0&&31,1:P
CUPPC,4,86,TSL,0&&31,0;
ZWTP:BCSU,6:PCU_B,3,6::PCUDSP,4,154,TSL,0&&31,1:PCUDSP,4,155,TSL,0&&31,1:P
CUPPC,4,91,TSL,0&&31,0;
ZWTP:BCSU,6:PCU_B,4,6::PCUDSP,4,152,TSL,0&&31,1:PCUDSP,4,153,TSL,0&&31,1:P
CUPPC,4,90,TSL,0&&31,0;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU_B,3;
ZWUC:BCSU,<index>:PCU_B,4;

9.3.2

PCU_B Track 7 PCM Configuration in BSC3i

Install the PCU_B to BCSU track 7. 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_B plug-in unit is created to the EQUIPM database with the following MML-command:

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

73 (149)

ZWTP:BCSU,0:PCU_B,5,7::PCUDSP,4,158,TSL,0&&31,1:PCUDSP,4,159,TSL,0&&31,1:P
CUPPC,4,217,TSL,0&&31,0;
ZWTP:BCSU,0:PCU_B,6,7::PCUDSP,4,156,TSL,0&&31,1:PCUDSP,4,157,TSL,0&&31,1:P
CUPPC,4,216,TSL,0&&31,0;
ZWTP:BCSU,1:PCU_B,5,7::PCUDSP,4,194,TSL,0&&31,1:PCUDSP,4,195,TSL,0&&31,1:P
CUPPC,4,219,TSL,0&&31,0;
ZWTP:BCSU,1:PCU_B,6,7::PCUDSP,4,192,TSL,0&&31,1:PCUDSP,4,193,TSL,0&&31,1:P
CUPPC,4,218,TSL,0&&31,0;
ZWTP:BCSU,2:PCU_B,5,7::PCUDSP,4,198,TSL,0&&31,1:PCUDSP,4,199,TSL,0&&31,1:P
CUPPC,4,221,TSL,0&&31,0;
ZWTP:BCSU,2:PCU_B,6,7::PCUDSP,4,196,TSL,0&&31,1:PCUDSP,4,197,TSL,0&&31,1:P
CUPPC,4,220,TSL,0&&31,0;
ZWTP:BCSU,3:PCU_B,5,7::PCUDSP,4,202,TSL,0&&31,1:PCUDSP,4,203,TSL,0&&31,1:P
CUPPC,4,93,TSL,0&&31,0;
ZWTP:BCSU,3:PCU_B,6,7::PCUDSP,4,200,TSL,0&&31,1:PCUDSP,4,201,TSL,0&&31,1:P
CUPPC,4,92,TSL,0&&31,0;
ZWTP:BCSU,4:PCU_B,5,7::PCUDSP,4,206,TSL,0&&31,1:PCUDSP,4,207,TSL,0&&31,1:P
CUPPC,4,95,TSL,0&&31,0;
ZWTP:BCSU,4:PCU_B,6,7::PCUDSP,4,204,TSL,0&&31,1:PCUDSP,4,205,TSL,0&&31,1:P
CUPPC,4,94,TSL,0&&31,0;
ZWTP:BCSU,5:PCU_B,5,7::PCUDSP,4,210,TSL,0&&31,1:PCUDSP,4,211,TSL,0&&31,1:P
CUPPC,4,223,TSL,0&&31,0;
ZWTP:BCSU,5:PCU_B,6,7::PCUDSP,4,208,TSL,0&&31,1:PCUDSP,4,209,TSL,0&&31,1:P
CUPPC,4,222,TSL,0&&31,0;
ZWTP:BCSU,6:PCU_B,5,7::PCUDSP,4,214,TSL,0&&31,1:PCUDSP,4,215,TSL,0&&31,1:P
CUPPC,4,253,TSL,0&&31,0;
ZWTP:BCSU,6:PCU_B,6,7::PCUDSP,4,212,TSL,0&&31,1:PCUDSP,4,213,TSL,0&&31,1:P
CUPPC,4,252,TSL,0&&31,0;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU_B,5;
ZWUC:BCSU,<index>:PCU_B,6;

9.3.3

PCU2_D Track 6 PCM Configuration in BSC3i

Install the PCU2_D to BCSU track 6. 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.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

74 (149)

The PCU_D plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_D,3,6::PCUDSP,4,130,TSL,0&&31:PCUDSP,4,131,TSL,0&&31:PC
UPPC,4,67,TSL,0&&31;
ZWTP:BCSU,0:PCU2_D,4,6::PCUDSP,4,128,TSL,0&&31:PCUDSP,4,129,TSL,0&&31:PC
UPPC,4,66,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,3,6::PCUDSP,4,134,TSL,0&&31:PCUDSP,4,135,TSL,0&&31:PC
UPPC,4,71,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,4,6::PCUDSP,4,132,TSL,0&&31:PCUDSP,4,133,TSL,0&&31:PC
UPPC,4,70,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,3,6::PCUDSP,4,138,TSL,0&&31:PCUDSP,4,139,TSL,0&&31:PC
UPPC,4,75,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,4,6::PCUDSP,4,136,TSL,0&&31:PCUDSP,4,137,TSL,0&&31:PC
UPPC,4,74,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,3,6::PCUDSP,4,142,TSL,0&&31:PCUDSP,4,143,TSL,0&&31:PC
UPPC,4,79,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,4,6::PCUDSP,4,140,TSL,0&&31:PCUDSP,4,141,TSL,0&&31:PC
UPPC,4,78,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,3,6::PCUDSP,4,146,TSL,0&&31:PCUDSP,4,147,TSL,0&&31:PC
UPPC,4,83,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,4,6::PCUDSP,4,144,TSL,0&&31:PCUDSP,4,145,TSL,0&&31:PC
UPPC,4,82,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,3,6::PCUDSP,4,150,TSL,0&&31:PCUDSP,4,151,TSL,0&&31:PC
UPPC,4,87,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,4,6::PCUDSP,4,148,TSL,0&&31:PCUDSP,4,149,TSL,0&&31:PC
UPPC,4,86,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,3,6::PCUDSP,4,154,TSL,0&&31:PCUDSP,4,155,TSL,0&&31:PC
UPPC,4,91,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,4,6::PCUDSP,4,152,TSL,0&&31:PCUDSP,4,153,TSL,0&&31:PC
UPPC,4,90,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_D,3;
ZWUC:BCSU,<index>:PCU2_D,4;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

75 (149)

9.3.4

PCU2_D Track 7 PCM Configuration in BSC3i

Install the PCU2_D to BCSU track 7. 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_D plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_D,5,7::PCUDSP,4,158,TSL,0&&31:PCUDSP,4,159,TSL,0&&31:PC
UPPC,4,217,TSL,0&&31;
ZWTP:BCSU,0:PCU2_D,6,7::PCUDSP,4,156,TSL,0&&31:PCUDSP,4,157,TSL,0&&31:PC
UPPC,4,216,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,5,7::PCUDSP,4,194,TSL,0&&31:PCUDSP,4,195,TSL,0&&31:PC
UPPC,4,219,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,6,7::PCUDSP,4,192,TSL,0&&31:PCUDSP,4,193,TSL,0&&31:PC
UPPC,4,218,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,5,7::PCUDSP,4,198,TSL,0&&31:PCUDSP,4,199,TSL,0&&31:PC
UPPC,4,221,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,6,7::PCUDSP,4,196,TSL,0&&31:PCUDSP,4,197,TSL,0&&31:PC
UPPC,4,220,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,5,7::PCUDSP,4,202,TSL,0&&31:PCUDSP,4,203,TSL,0&&31:PC
UPPC,4,93,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,6,7::PCUDSP,4,200,TSL,0&&31:PCUDSP,4,201,TSL,0&&31:PC
UPPC,4,92,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,5,7::PCUDSP,4,206,TSL,0&&31:PCUDSP,4,207,TSL,0&&31:PC
UPPC,4,95,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,6,7::PCUDSP,4,204,TSL,0&&31:PCUDSP,4,205,TSL,0&&31:PC
UPPC,4,94,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,5,7::PCUDSP,4,210,TSL,0&&31:PCUDSP,4,211,TSL,0&&31:PC
UPPC,4,223,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,6,7::PCUDSP,4,208,TSL,0&&31:PCUDSP,4,209,TSL,0&&31:PC
UPPC,4,222,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,5,7::PCUDSP,4,214,TSL,0&&31:PCUDSP,4,215,TSL,0&&31:PC
UPPC,4,253,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,6,7::PCUDSP,4,212,TSL,0&&31:PCUDSP,4,213,TSL,0&&31:PC
UPPC,4,252,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_D,5;
ZWUC:BCSU,<index>:PCU2_D,6;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

76 (149)

9.3.5

PCU2_E Track 6 PCM Configuration in BSC3i

Install the PCU2_E to BCSU track 6. 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_E plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,4,6::PCUDSP,4,128&&131,TSL,0&&31:PCUPPC,4,66&&67,TSL,
0&&31:;
ZWTP:BCSU,1:PCU2_E,4,6::PCUDSP,4,132&&135,TSL,0&&31:PCUPPC,4,70&&71,TSL,
0&&31;
ZWTP:BCSU,2:PCU2_E,4,6::PCUDSP,4,136&&139,TSL,0&&31:PCUPPC,4,74&&75,TSL,
0&&31;
ZWTP:BCSU,3:PCU2_E,4,6::PCUDSP,4,140&&143,TSL,0&&31:PCUPPC,4,78&&79,TSL,
0&&31;
ZWTP:BCSU,4:PCU2_E,4,6::PCUDSP,4,144&&147,TSL,0&&31:PCUPPC,4,82&&83,TSL,
0&&31;
ZWTP:BCSU,5:PCU2_E,4,6::PCUDSP,4,148&&151,TSL,0&&31:PCUPPC,4,86&&87,TSL,
0&&31;
ZWTP:BCSU,6:PCU2_E,4,6::PCUDSP,4,152&&155,TSL,0&&31:PCUPPC,4,90&&91,TSL,
0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_E,4;

9.3.6

PCU2_E Track 7 PCM Configuration in BSC3i

Install the PCU2_E to BCSU track 7. 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_E plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,6,7::PCUDSP,4,156&&159,TSL,0&&31PCUPPC,4,216&&217,TS
L,0&&31:;
ZWTP:BCSU,1:PCU2_E,6,7::PCUDSP,4,192&&195,TSL,0&&31:PCUPPC,4,218&&219,TS
L,0&&31;
ZWTP:BCSU,2:PCU2_E,6,7::PCUDSP,4,196&&199,TSL,0&&31:PCUPPC,4,220&&221,TS
L,0&&31;
ZWTP:BCSU,3:PCU2_E,6,7::PCUDSP,4,200&&203,TSL,0&&31:PCUPPC,4,92&&93,TSL,
0&&31;
ZWTP:BCSU,4:PCU2_E,6,7::PCUDSP,4,204&&207,TSL,0&&31:PCUPPC,4,94&&95,TSL,
0&&31;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

77 (149)

ZWTP:BCSU,5:PCU2_E,6,7::PCUDSP,4,208&&211,TSL,0&&31:PCUPPC,4,222&&223,TS
L,0&&31;
ZWTP:BCSU,6:PCU2_E,6,7::PCUDSP,4,212&&215,TSL,0&&31:PCUPPC,4,252&&253,TS
L,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_E,6;

9.4

BSC3i 660 (GSW1KB) BCSU Unit upgrade

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

ZUSC:BCSU,<index>:TE,;
ZUSC:BCSU,<index>:SE,;
ZUSC:BCSU,<index>:SE,;
Switch the BCSU cartridge power off from the PSC6-A or PSC6-B power supply.
Check that all the PCU plug-in unit jumpers are set according to the instructions (Appendix4, PCU_B Jumper
settings, Appendix5, PCU2_D Jumper settings or Appendix6, PCU2-E Jumper settings)
PCU2-E supported only 4M full mode PCM(s) with GSW1KB. There is a limit of one PCU2-E PIU on a BCSU.
Exceeding the limit may damage the power supply.
1. Install the PCU_B/PCU2_D/PCU2-E to BCSU track 6, see chapters 9.4.1, 9.4.3 or 9.4.5.
2. Install the PCU_B/PCU2_D/PCU2_E to BCSU track 7, see chapters 9.4.2, 9.4.4 or 9.4.6.
Create GB interface to BCSU if needed:

ZQRA:BCSU,<index> :<PCU_type>,<PCU_index> :IFETH0::UP;


ZQRA:BCSU,<index> :<PCU_type>,<PCU_index> :IFETH1::UP;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

78 (149)

Switch the BCSU cartridge power on from the PSC6-A or PSC6-B power supply.
Change the BCSU state to TE-EX.

ZUSC:BCSU,<index>:SE,;
ZUSC:BCSU,<index>:TE,;
After PCU installation, boot software checking is done. If update is needed, macro executes update according
instructions 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,<index>:C=DSK;
Alter restart execute diagnostic:

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

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

ZUSC:BCSU,<index>:SP,;
In case of PCU2-E installation, BCSU-0 (primary spare unit) is changed to SP-EX state and after that switchover
will be done to BCSU unit to be upgraded next.

Repeat these steps for all BCSU(s).

9.4.1

PCU_B Track 6 PCM Configuration in BSC3i 660

Install the PCU_B to BCSU track 6. One PCM is used for the Abis and one for the Gb interface. PCMs will be
defined with two plug-in unit functions: PCUDSP and PCUPPC.
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

79 (149)

The PCU_B plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU_B,3,6::PCUDSP,4,66,TSL,0&&31:PCUDSP,4,67,TSL,0&&31:PCUPP
C,4,97,TSL,0&&31,2;
ZWTP:BCSU,0:PCU_B,4,6::PCUDSP,4,64,TSL,0&&31:PCUDSP,4,65,TSL,0&&31:PCUPP
C,4,96,TSL,0&&31,2;
ZWTP:BCSU,1:PCU_B,3,6::PCUDSP,4,74,TSL,0&&31:PCUDSP,4,75,TSL,0&&31:PCUPP
C,4,105,TSL,0&&31,2;
ZWTP:BCSU,1:PCU_B,4,6::PCUDSP,4,72,TSL,0&&31:PCUDSP,4,73,TSL,0&&31:PCUPP
C,4,104,TSL,0&&31,2;
ZWTP:BCSU,2:PCU_B,3,6::PCUDSP,4,82,TSL,0&&31:PCUDSP,4,83,TSL,0&&31:PCUPP
C,4,113,TSL,0&&31,2;
ZWTP:BCSU,2:PCU_B,4,6::PCUDSP,4,80,TSL,0&&31:PCUDSP,4,81,TSL,0&&31:PCUPP
C,4,112,TSL,0&&31,2;
ZWTP:BCSU,3:PCU_B,3,6::PCUDSP,4,90,TSL,0&&31:PCUDSP,4,91,TSL,0&&31:PCUPP
C,4,121,TSL,0&&31,2;
ZWTP:BCSU,3:PCU_B,4,6::PCUDSP,4,88,TSL,0&&31:PCUDSP,4,89,TSL,0&&31:PCUPP
C,4,120,TSL,0&&31,2;
ZWTP:BCSU,4:PCU_B,3,6::PCUDSP,4,130,TSL,0&&31:PCUDSP,4,131,TSL,0&&31:PCU
PPC,4,161,TSL,0&&31,2;
ZWTP:BCSU,4:PCU_B,4,6::PCUDSP,4,128,TSL,0&&31:PCUDSP,4,129,TSL,0&&31:PCU
PPC,4,160,TSL,0&&31,2;
ZWTP:BCSU,5:PCU_B,3,6::PCUDSP,4,138,TSL,0&&31:PCUDSP,4,139,TSL,0&&31:PCU
PPC,4,169,TSL,0&&31,2;
ZWTP:BCSU,5:PCU_B,4,6::PCUDSP,4,136,TSL,0&&31:PCUDSP,4,137,TSL,0&&31:PCU
PPC,4,168,TSL,0&&31,2;
ZWTP:BCSU,6:PCU_B,3,6::PCUDSP,4,146,TSL,0&&31:PCUDSP,4,147,TSL,0&&31:PCU
PPC,4,177,TSL,0&&31,2;
ZWTP:BCSU,6:PCU_B,4,6::PCUDSP,4,144,TSL,0&&31:PCUDSP,4,145,TSL,0&&31:PCU
PPC,4,176,TSL,0&&31,2;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU_B,3;
ZWUC:BCSU,<index>:PCU_B,4;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

80 (149)

9.4.2

PCU_B Track 7 PCM Configuration in BSC3i 660

Install the PCU_B to BCSU track 7. One PCM is used for the Abis and one for the Gb interface. PCMs will be
defined with two plug-in unit functions: PCUDSP and PCUPPC.
The PCU_B plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU_B,5,7::PCUDSP,4,70,TSL,0&&31:PCUDSP,4,71,TSL,0&&31:PCUPP
C,4,101,TSL,0&&31,2;
ZWTP:BCSU,0:PCU_B,6,7::PCUDSP,4,68,TSL,0&&31:PCUDSP,4,69,TSL,0&&31:PCUPP
C,4,100,TSL,0&&31,2;
ZWTP:BCSU,1:PCU_B,5,7::PCUDSP,4,78,TSL,0&&31:PCUDSP,4,79,TSL,0&&31:PCUPP
C,4,109,TSL,0&&31,2;
ZWTP:BCSU,1:PCU_B,6,7::PCUDSP,4,76,TSL,0&&31:PCUDSP,4,77,TSL,0&&31:PCUPP
C,4,108,TSL,0&&31,2;
ZWTP:BCSU,2:PCU_B,5,7::PCUDSP,4,86,TSL,0&&31:PCUDSP,4,87,TSL,0&&31:PCUPP
C,4,117,TSL,0&&31,2;
ZWTP:BCSU,2:PCU_B,6,7::PCUDSP,4,84,TSL,0&&31:PCUDSP,4,85,TSL,0&&31:PCUPP
C,4,116,TSL,0&&31,2;
ZWTP:BCSU,3:PCU_B,5,7::PCUDSP,4,94,TSL,0&&31:PCUDSP,4,95,TSL,0&&31:PCUPP
C,4,125,TSL,0&&31,2;
ZWTP:BCSU,3:PCU_B,6,7::PCUDSP,4,92,TSL,0&&31:PCUDSP,4,93,TSL,0&&31:PCUPP
C,4,124,TSL,0&&31,2;
ZWTP:BCSU,4:PCU_B,5,7::PCUDSP,4,134,TSL,0&&31:PCUDSP,4,135,TSL,0&&31:PCU
PPC,4,165,TSL,0&&31,2;
ZWTP:BCSU,4:PCU_B,6,7::PCUDSP,4,132,TSL,0&&31:PCUDSP,4,133,TSL,0&&31:PCU
PPC,4,164,TSL,0&&31,2;
ZWTP:BCSU,5:PCU_B,5,7::PCUDSP,4,142,TSL,0&&31:PCUDSP,4,143,TSL,0&&31:PCU
PPC,4,173,TSL,0&&31,2;
ZWTP:BCSU,5:PCU_B,6,7::PCUDSP,4,140,TSL,0&&31:PCUDSP,4,141,TSL,0&&31:PCU
PPC,4,172,TSL,0&&31,2;
ZWTP:BCSU,6:PCU_B,5,7::PCUDSP,4,150,TSL,0&&31:PCUDSP,4,151,TSL,0&&31:PCU
PPC,4,181,TSL,0&&31,2;
ZWTP:BCSU,6:PCU_B,6,7::PCUDSP,4,148,TSL,0&&31:PCUDSP,4,149,TSL,0&&31:PCU
PPC,4,180,TSL,0&&31,2;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU_B,5;
ZWUC:BCSU,<index>:PCU_B,6;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

81 (149)

9.4.3

PCU2_D Track 6 PCM Configuration in BSC3i 660

Install the PCU2_D to BCSU track 6. 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 PCU2_D plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_D,3,6::PCUDSP,4,66,TSL,0&&31:PCUDSP,4,67,TSL,0&&31:PCUP
PC,4,97,TSL,0&&31;
ZWTP:BCSU,0:PCU2_D,4,6::PCUDSP,4,64,TSL,0&&31:PCUDSP,4,65,TSL,0&&31:PCUP
PC,4,96,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,3,6::PCUDSP,4,74,TSL,0&&31:PCUDSP,4,75,TSL,0&&31:PCUP
PC,4,105,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,4,6::PCUDSP,4,72,TSL,0&&31:PCUDSP,4,73,TSL,0&&31:PCUP
PC,4,104,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,3,6::PCUDSP,4,82,TSL,0&&31:PCUDSP,4,83,TSL,0&&31:PCUP
PC,4,113,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,4,6::PCUDSP,4,80,TSL,0&&31:PCUDSP,4,81,TSL,0&&31:PCUP
PC,4,112,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,3,6::PCUDSP,4,90,TSL,0&&31:PCUDSP,4,91,TSL,0&&31:PCUP
PC,4,121,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,4,6::PCUDSP,4,88,TSL,0&&31:PCUDSP,4,89,TSL,0&&31:PCUP
PC,4,120,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,3,6::PCUDSP,4,130,TSL,0&&31:PCUDSP,4,131,TSL,0&&31:PC
UPPC,4,161,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,4,6::PCUDSP,4,128,TSL,0&&31:PCUDSP,4,129,TSL,0&&31:PC
UPPC,4,160,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,3,6::PCUDSP,4,138,TSL,0&&31:PCUDSP,4,139,TSL,0&&31:PC
UPPC,4,169,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,4,6::PCUDSP,4,136,TSL,0&&31:PCUDSP,4,137,TSL,0&&31:PC
UPPC,4,168,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,3,6::PCUDSP,4,146,TSL,0&&31:PCUDSP,4,147,TSL,0&&31:PC
UPPC,4,177,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,4,6::PCUDSP,4,144,TSL,0&&31:PCUDSP,4,145,TSL,0&&31:PC
UPPC,4,176,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_D,3;
ZWUC:BCSU,<index>:PCU2_D,4;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

82 (149)

9.4.4

PCU2_D Track 7 PCM Configuration in BSC3i 660

Install the PCU2_D to BCSU track 7. 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 PCU2_D plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_D,5,7::PCUDSP,4,70,TSL,0&&31:PCUDSP,4,71,TSL,0&&31:PCUP
PC,4,101,TSL,0&&31;
ZWTP:BCSU,0:PCU2_D,6,7::PCUDSP,4,68,TSL,0&&31:PCUDSP,4,69,TSL,0&&31:PCUP
PC,4,100,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,5,7::PCUDSP,4,78,TSL,0&&31:PCUDSP,4,79,TSL,0&&31:PCUP
PC,4,109,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,6,7::PCUDSP,4,76,TSL,0&&31:PCUDSP,4,77,TSL,0&&31:PCUP
PC,4,108,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,5,7::PCUDSP,4,86,TSL,0&&31:PCUDSP,4,87,TSL,0&&31:PCUP
PC,4,117,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,6,7::PCUDSP,4,84,TSL,0&&31:PCUDSP,4,85,TSL,0&&31:PCUP
PC,4,116,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,5,7::PCUDSP,4,94,TSL,0&&31:PCUDSP,4,95,TSL,0&&31:PCUP
PC,4,125,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,6,7::PCUDSP,4,92,TSL,0&&31:PCUDSP,4,93,TSL,0&&31:PCUP
PC,4,124,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,5,7::PCUDSP,4,134,TSL,0&&31:PCUDSP,4,135,TSL,0&&31:PC
UPPC,4,165,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,6,7::PCUDSP,4,132,TSL,0&&31:PCUDSP,4,133,TSL,0&&31:PC
UPPC,4,164,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,5,7::PCUDSP,4,142,TSL,0&&31:PCUDSP,4,143,TSL,0&&31:PC
UPPC,4,173,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,6,7::PCUDSP,4,140,TSL,0&&31:PCUDSP,4,141,TSL,0&&31:PC
UPPC,4,172,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,5,7::PCUDSP,4,150,TSL,0&&31:PCUDSP,4,151,TSL,0&&31:PC
UPPC,4,181,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,6,7::PCUDSP,4,148,TSL,0&&31:PCUDSP,4,149,TSL,0&&31:PC
UPPC,4,180,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_D,5;
ZWUC:BCSU,<index>:PCU2_D,6;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

83 (149)

9.4.5

PCU2_E Track 6 PCM Configuration in BSC3i 660

Install the PCU2_E to BCSU track 6. 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 PCU2_E plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,4,6::PCUDSP,4,64&&67,TSL,0&&31:PCUPPC,4,96&&97,TSL,0&
&31:;
ZWTP:BCSU,1:PCU2_E,4,6::PCUDSP,4,72&&75,TSL,0&&31:PCUPPC,4,104&&105,TSL,
0&&31:;
ZWTP:BCSU,2:PCU2_E,4,6::PCUDSP,4,80&&83,TSL,0&&31:PCUPPC,4,112&&113,TSL,
0&&31:;
ZWTP:BCSU,3:PCU2_E,4,6::PCUDSP,4,88&&91,TSL,0&&31:PCUPPC,4,120&&121,TSL,
0&&31:;
ZWTP:BCSU,4:PCU2_E,4,6::PCUDSP,4,128&&131,TSL,0&&31:PCUPPC,4,160&&161,TS
L,0&&31:;
ZWTP:BCSU,5:PCU2_E,4,6::PCUDSP,4,136&&139,TSL,0&&31:PCUPPC,4,168&&169,TS
L,0&&31:;
ZWTP:BCSU,6:PCU2_E,4,6::PCUDSP,4,144&&147,TSL,0&&31:PCUPPC,4,176&&177,TS
L,0&&31:;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_E,4;

9.4.6

PCU2_E Track 7 PCM Configuration in BSC3i 660

Install the PCU2_E to BCSU track 7. 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 PCU2_E plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,6,7::PCUDSP,4,68&&71,TSL,0&&31:PCUPPC,4,100&&101,TSL,
0&&31:;
ZWTP:BCSU,1:PCU2_E,6,7::PCUDSP,4,76&&79,TSL,0&&31:PCUPPC,4,108&&109,TSL,
0&&31:;
ZWTP:BCSU,2:PCU2_E,6,7::PCUDSP,4,84&&87,TSL,0&&31:PCUPPC,4,116&&117,TSL,
0&&31:;
ZWTP:BCSU,3:PCU2_E,6,7::PCUDSP,4,92&&95,TSL,0&&31:PCUPPC,4,124&&125,TSL,
0&&31:;
ZWTP:BCSU,4:PCU2_E,6,7::PCUDSP,4,132&&135,TSL,0&&31:PCUPPC,4,164&&165,TS
L,0&&31:;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

84 (149)

ZWTP:BCSU,5:PCU2_E,6,7::PCUDSP,4,140&&143,TSL,0&&31:PCUPPC,4,172&&173,TS
L,0&&31:;
ZWTP:BCSU,6:PCU2_E,6,7::PCUDSP,4,148&&151,TSL,0&&31:PCUPPC,4,180&&181,TS
L,0&&31:;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_E,6;

9.5

BSC3i 1000/2000 BCSU Unit upgrade

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

ZUSC:BCSU,<index>:TE,;
ZUSC:BCSU,<index>:SE,;
ZUSC:BCSU,<index>:SE,;
Switch the BCSU cartridge power off from the PSC6-A or PSC6-B power supply.
Check that all the PCU plug-in unit jumpers are set according to the instructions (Appendix4, PCU_B Jumper
settings, Appendix5, PCU2_D Jumper settings or Appendix6, PCU2-E Jumper settings)

Install the PCU2_D/PCU2_E to BCSU track 3, see chapters 9.5.1 or 9.5.4.


Install the PCU2_D/PCU2_E to BCSU track 4, see chapters 9.5.2 or 9.5.5.
Install the PCU2_D/PCU2_E to BCSU track 5, see chapters 9.5.3 or 9.5.6.
Install the PCU_B/PCU2_D/PCU2-E to BCSU track 6, see chapters 9.5.7, 9.5.9 or 9.5.11.
Install the PCU_B/PCU2_D/PCU2_E to BCSU track 7, see chapters 9.5.8, 9.5.10 or 9.5.12.
Create GB interface to BCSU if needed:

ZQRA:BCSU,<index> :<PCU_type>,<PCU_index> :IFETH0::UP;


ZQRA:BCSU,<index> :<PCU_type>,<PCU_index> :IFETH1::UP;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

85 (149)

If more than two PCU2-E plug-in units are to be installed, also new power must be changed in this step (PSC6-D).
See more information from chapter 8.2.
Switch the BCSU cartridge power on (PSC6-A/PSC6-B/PSC6-D) to power supply.
Change the BCSU state to TE-EX:

ZUSC:BCSU,<index>:SE,;
ZUSC:BCSU,<index>:TE,;
After PCU installation, boot software checking is done. If update is needed, macro executes update according
instructions 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,<index>:C=DSK;
Alter restart execute diagnostic:

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

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

ZUSC:BCSU,<index>:SP,;
In case of PCU2-E installation, BCSU-0 (primary spare unit) is changed to SP-EX state and after that switchover
will be done to BCSU unit to be upgraded next.

Repeat these steps for all BCSU(s).

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

86 (149)

9.5.1

PCU2_D Track 3 PCM Configuration in BSC3i 1000/2000

Install the PCU2_D to BCSU track 3. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_D plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,650,TSL,0&&31:<PCUDSP/PCUPA
B>,8,651,TSL,0&&31:PCUPPC,8,654,TSL,0&&31;
ZWTP:BCSU,0:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,648,TSL,0&&31:<PCUDSP/PCUPA
B>,8,649,TSL,0&&31:PCUPPC,8,652,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,674,TSL,0&&31:<PCUDSP/PCUPA
B>,8,675,TSL,0&&31:PCUPPC,8,678,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,672,TSL,0&&31:<PCUDSP/PCUPA
B>,8,673,TSL,0&&31:PCUPPC,8,676,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,698,TSL,0&&31:<PCUDSP/PCUPA
B>,8,699,TSL,0&&31:PCUPPC,8,702,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,696,TSL,0&&31:<PCUDSP/PCUPA
B>,8,697,TSL,0&&31:PCUPPC,8,700,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,722,TSL,0&&31:<PCUDSP/PCUPA
B>,8,723,TSL,0&&31:PCUPPC,8,726,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,720,TSL,0&&31:<PCUDSP/PCUPA
B>,8,721,TSL,0&&31:PCUPPC,8,724,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,746,TSL,0&&31:<PCUDSP/PCUPA
B>,8,747,TSL,0&&31:PCUPPC,8,750,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,744,TSL,0&&31:<PCUDSP/PCUPA
B>,8,745,TSL,0&&31:PCUPPC,8,748,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,1002,TSL,0&&31:<PCUDSP/PCUPA
B>,8,1003,TSL,0&&31:PCUPPC,8,1006,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,1000,TSL,0&&31:<PCUDSP/PCUPA
B>,8,1001,TSL,0&&31:PCUPPC,8,1004,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,770,TSL,0&&31:<PCUDSP/PCUPA
B>,8,771,TSL,0&&31:PCUPPC,8,774,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,768,TSL,0&&31:<PCUDSP/PCUPA
B>,8,769,TSL,0&&31:PCUPPC,8,772,TSL,0&&31;
ZWTP:BCSU,7:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,794,TSL,0&&31:<PCUDSP/PCUPA
B>,8,795,TSL,0&&31:PCUPPC,8,798,TSL,0&&31;
ZWTP:BCSU,7:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,792,TSL,0&&31:<PCUDSP/PCUPA
B>,8,793,TSL,0&&31:PCUPPC,8,796,TSL,0&&31;
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

87 (149)

ZWTP:BCSU,8:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,818,TSL,0&&31:<PCUDSP/PCUPA
B>,8,819,TSL,0&&31:PCUPPC,8,822,TSL,0&&31;
ZWTP:BCSU,8:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,816,TSL,0&&31:<PCUDSP/PCUPA
B>,8,817,TSL,0&&31:PCUPPC,8,820,TSL,0&&31;
ZWTP:BCSU,9:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,842,TSL,0&&31:<PCUDSP/PCUPA
B>,8,843,TSL,0&&31:PCUPPC,8,846,TSL,0&&31;
ZWTP:BCSU,9:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,840,TSL,0&&31:<PCUDSP/PCUPA
B>,8,841,TSL,0&&31:PCUPPC,8,844,TSL,0&&31;
ZWTP:BCSU,10:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,1330,TSL,0&&31:<PCUDSP/PCUP
AB>,8,1331,TSL,0&&31:PCUPPC,8,1334,TSL,0&&31;
ZWTP:BCSU,10:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,1328,TSL,0&&31:<PCUDSP/PCUP
AB>,8,1329,TSL,0&&31:PCUPPC,8,1332,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_D,7;
ZWUC:BCSU,<index>:PCU2_D,8;

9.5.2

PCU2_D Track 4 PCM Configuration in BSC3i 1000/2000

Install the PCU2_D to BCSU track 4. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_D plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,658,TSL,0&&31:<PCUDSP/PCUPA
B>,8,659,TSL,0&&31:PCUPPC,8,662,TSL,0&&31;
ZWTP:BCSU,0:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,656,TSL,0&&31:<PCUDSP/PCUPA
B>,8,657,TSL,0&&31:PCUPPC,8,660,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,682,TSL,0&&31:<PCUDSP/PCUPA
B>,8,683,TSL,0&&31:PCUPPC,8,686,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,680,TSL,0&&31:<PCUDSP/PCUPA
B>,8,681,TSL,0&&31:PCUPPC,8,684,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,706,TSL,0&&31:<PCUDSP/PCUPA
B>,8,707,TSL,0&&31:PCUPPC,8,710,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,704,TSL,0&&31:<PCUDSP/PCUPA
B>,8,705,TSL,0&&31:PCUPPC,8,708,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,730,TSL,0&&31:<PCUDSP/PCUPA
B>,8,731,TSL,0&&31:PCUPPC,8,734,TSL,0&&31;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

88 (149)

ZWTP:BCSU,3:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,728,TSL,0&&31:<PCUDSP/PCUPA
B>,8,729,TSL,0&&31:PCUPPC,8,732,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,754,TSL,0&&31:<PCUDSP/PCUPA
B>,8,755,TSL,0&&31:PCUPPC,8,758,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,752,TSL,0&&31:<PCUDSP/PCUPA
B>,8,753,TSL,0&&31:PCUPPC,8,756,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,1010,TSL,0&&31:<PCUDSP/PCUPA
B>,8,1011,TSL,0&&31:PCUPPC,8,1014,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,1008,TSL,0&&31:<PCUDSP/PCUP
AB>,8,1009,TSL,0&&31:PCUPPC,8,1012,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,778,TSL,0&&31:<PCUDSP/PCUPA
B>,8,779,TSL,0&&31:PCUPPC,8,782,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,776,TSL,0&&31:<PCUDSP/PCUPA
B>,8,777,TSL,0&&31:PCUPPC,8,780,TSL,0&&31;
ZWTP:BCSU,7:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,802,TSL,0&&31:<PCUDSP/PCUPA
B>,8,803,TSL,0&&31:PCUPPC,8,806,TSL,0&&31;
ZWTP:BCSU,7:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,800,TSL,0&&31:<PCUDSP/PCUPA
B>,8,801,TSL,0&&31:PCUPPC,8,804,TSL,0&&31;
ZWTP:BCSU,8:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,826,TSL,0&&31:<PCUDSP/PCUPA
B>,8,827,TSL,0&&31:PCUPPC,8,830,TSL,0&&31;
ZWTP:BCSU,8:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,824,TSL,0&&31:<PCUDSP/PCUPA
B>,8,825,TSL,0&&31:PCUPPC,8,828,TSL,0&&31;
ZWTP:BCSU,9:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,850,TSL,0&&31:<PCUDSP/PCUPA
B>,8,851,TSL,0&&31:PCUPPC,8,854,TSL,0&&31;
ZWTP:BCSU,9:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,848,TSL,0&&31:<PCUDSP/PCUPA
B>,8,849,TSL,0&&31:PCUPPC,8,852,TSL,0&&31;
ZWTP:BCSU,10:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,1338,TSL,0&&31:<PCUDSP/PCUP
AB>,8,1339,TSL,0&&31:PCUPPC,8,1342,TSL,0&&31;
ZWTP:BCSU,10:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,1336,TSL,0&&31:<PCUDSP/PCU
PAB>,8,1337,TSL,0&&31:PCUPPC,8,1340,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_D,9;
ZWUC:BCSU,<index>:PCU2_D,10;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

89 (149)

9.5.3

PCU2_D Track 5 PCM Configuration in BSC3i 1000/2000

Install the PCU2_D to BCSU track 5. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_D plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,666,TSL,0&&31:<PCUDSP/PCUPA
B>,8,667,TSL,0&&31:PCUPPC,8,670,TSL,0&&31;
ZWTP:BCSU,0:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,664,TSL,0&&31:<PCUDSP/PCUPA
B>,8,665,TSL,0&&31:PCUPPC,8,668,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,690,TSL,0&&31:<PCUDSP/PCUPA
B>,8,691,TSL,0&&31:PCUPPC,8,694,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,688,TSL,0&&31:<PCUDSP/PCUPA
B>,8,689,TSL,0&&31:PCUPPC,8,692,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,714,TSL,0&&31:<PCUDSP/PCUPA
B>,8,715,TSL,0&&31:PCUPPC,8,718,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,712,TSL,0&&31:<PCUDSP/PCUPA
B>,8,713,TSL,0&&31:PCUPPC,8,716,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,738,TSL,0&&31:<PCUDSP/PCUPA
B>,8,739,TSL,0&&31:PCUPPC,8,742,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,736,TSL,0&&31:<PCUDSP/PCUPA
B>,8,737,TSL,0&&31:PCUPPC,8,740,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,762,TSL,0&&31:<PCUDSP/PCUPA
B>,8,763,TSL,0&&31:PCUPPC,8,766,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,760,TSL,0&&31:<PCUDSP/PCUPA
B>,8,761,TSL,0&&31:PCUPPC,8,764,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,1018,TSL,0&&31:<PCUDSP/PCUP
AB>,8,1019,TSL,0&&31:PCUPPC,8,1022,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,1016,TSL,0&&31:<PCUDSP/PCUP
AB>,8,1017,TSL,0&&31:PCUPPC,8,1020,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,786,TSL,0&&31:<PCUDSP/PCUPA
B>,8,787,TSL,0&&31:PCUPPC,8,790,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,784,TSL,0&&31:<PCUDSP/PCUPA
B>,8,785,TSL,0&&31:PCUPPC,8,788,TSL,0&&31;
ZWTP:BCSU,7:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,810,TSL,0&&31:<PCUDSP/PCUPA
B>,8,811,TSL,0&&31:PCUPPC,8,814,TSL,0&&31;
ZWTP:BCSU,7:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,808,TSL,0&&31:<PCUDSP/PCUPA
B>,8,809,TSL,0&&31:PCUPPC,8,812,TSL,0&&31;
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

90 (149)

ZWTP:BCSU,8:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,834,TSL,0&&31:<PCUDSP/PCUPA
B>,8,835,TSL,0&&31:PCUPPC,8,838,TSL,0&&31;
ZWTP:BCSU,8:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,832,TSL,0&&31:<PCUDSP/PCUPA
B>,8,833,TSL,0&&31:PCUPPC,8,836,TSL,0&&31;
ZWTP:BCSU,9:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,858,TSL,0&&31:<PCUDSP/PCUPA
B>,8,859,TSL,0&&31:PCUPPC,8,862,TSL,0&&31;
ZWTP:BCSU,9:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,856,TSL,0&&31:<PCUDSP/PCUPA
B>,8,857,TSL,0&&31:PCUPPC,8,860,TSL,0&&31;
ZWTP:BCSU,10:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,1594,TSL,0&&31:<PCUDSP/PCU
PAB>,8,1595,TSL,0&&31:PCUPPC,8,1598,TSL,0&&31;
ZWTP:BCSU,10:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,1592,TSL,0&&31:<PCUDSP/PCU
PAB>,8,1593,TSL,0&&31:PCUPPC,8,1596,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_D,11;
ZWUC:BCSU,<index>:PCU2_D,12;

9.5.4

PCU2_E Track 3 PCM Configuration in BSC3i 1000/2000

Install the PCU2_E to BCSU track 3. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_E plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,8,3::<PCUDSP/PCUPAB>,8,648&&651,TSL,0&&31:PCUPPC,8,6
52&654,TSL,0&&31;
ZWTP:BCSU,1:PCU2_E,8,3::<PCUDSP/PCUPAB>,8,672&&675,TSL,0&&31:PCUPPC,8,6
76&678,TSL,0&&31;
ZWTP:BCSU,2:PCU2_E,8,3::<PCUDSP/PCUPAB>,8,696&&699,TSL,0&&31:PCUPPC,8,7
00&702,TSL,0&&31;
ZWTP:BCSU,3:PCU2_E,8,3::<PCUDSP/PCUPAB>,8,720&&723,TSL,0&&31:PCUPPC,8,7
24&726,TSL,0&&31;
ZWTP:BCSU,4:PCU2_E,8,3::<PCUDSP/PCUPAB>,8,744&&747,TSL,0&&31:PCUPPC,8,7
48&750,TSL,0&&31;
ZWTP:BCSU,5:PCU2_E,8,3::<PCUDSP/PCUPAB>,8,1000&&1003,TSL,0&&31:PCUPPC,
8,1004&1006,TSL,0&&31;
ZWTP:BCSU,6:PCU2_E,8,3::<PCUDSP/PCUPAB>,8,768&&771,TSL,0&&31:PCUPPC,8,7
72&774,TSL,0&&31;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

91 (149)

ZWTP:BCSU,7:PCU2_E,8,3::<PCUDSP/PCUPAB>,8,792&&795,TSL,0&&31:PCUPPC,8,7
96&798,TSL,0&&31;
ZWTP:BCSU,8:PCU2_E,8,3::<PCUDSP/PCUPAB>,8,816&&819,TSL,0&&31:PCUPPC,8,8
20&822,TSL,0&&31;
ZWTP:BCSU,9:PCU2_E,8,3::<PCUDSP/PCUPAB>,8,840&&843,TSL,0&&31:PCUPPC,8,8
44&846,TSL,0&&31;
ZWTP:BCSU,10:PCU2_E,8,3::<PCUDSP/PCUPAB>,8,1328&&1331,TSL,0&&31:PCUPPC
,8,1332&1334,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_E,8;

9.5.5

PCU2_E Track 4 PCM Configuration in BSC3i 1000/2000

Install the PCU2_E to BCSU track 4. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_E plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,10,4::<PCUDSP/PCUPAB>,8,656&&659,TSL,0&&31:PCUPPC,8,
660&662,TSL,0&&31;
ZWTP:BCSU,1:PCU2_E,10,4::<PCUDSP/PCUPAB>,8,680&&683,TSL,0&&31:PCUPPC,8,
684&686,TSL,0&&31;
ZWTP:BCSU,2:PCU2_E,10,4::<PCUDSP/PCUPAB>,8,704&&707,TSL,0&&31:PCUPPC,8,
708&710,TSL,0&&31;
ZWTP:BCSU,3:PCU2_E,10,4::<PCUDSP/PCUPAB>,8,728&&731,TSL,0&&31:PCUPPC,8,
732&734,TSL,0&&31;
ZWTP:BCSU,4:PCU2_E,10,4::<PCUDSP/PCUPAB>,8,752&&755,TSL,0&&31:PCUPPC,8,
756&758,TSL,0&&31;
ZWTP:BCSU,6:PCU2_E,10,4::<PCUDSP/PCUPAB>,8,776&&779,TSL,0&&31:PCUPPC,8,
780&782,TSL,0&&31;
ZWTP:BCSU,7:PCU2_E,10,4::<PCUDSP/PCUPAB>,8,800&&803,TSL,0&&31:PCUPPC,8,
804&806,TSL,0&&31;
ZWTP:BCSU,8:PCU2_E,10,4::<PCUDSP/PCUPAB>,8,824&&827,TSL,0&&31:PCUPPC,8,
828&830,TSL,0&&31;
ZWTP:BCSU,9:PCU2_E,10,4::<PCUDSP/PCUPAB>,8,848&&851,TSL,0&&31:PCUPPC,8,
852&854,TSL,0&&31;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

92 (149)

ZWTP:BCSU,10:PCU2_E,10,4::<PCUDSP/PCUPAB>,8,1336&&1339,TSL,0&&31:PCUPP
C,8,1340&1342,TSL,0&&31;

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

ZWUC:BCSU,<index>:PCU2_E,10;

9.5.6

PCU2_E Track 5 PCM Configuration in BSC3i 1000/2000

Install the PCU2_E to BCSU track 5. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_E plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,12,5::<PCUDSP/PCUPAB>,8,664&&667,TSL,0&&31:PCUPPC,8,
668&670,TSL,0&&31;
ZWTP:BCSU,1:PCU2_E,12,5::<PCUDSP/PCUPAB>,8,688&&691,TSL,0&&31:PCUPPC,8,
692&694,TSL,0&&31;
ZWTP:BCSU,2:PCU2_E,12,5::<PCUDSP/PCUPAB>,8,712&&715,TSL,0&&31:PCUPPC,8,
716&718,TSL,0&&31;
ZWTP:BCSU,3:PCU2_E,12,5::<PCUDSP/PCUPAB>,8,736&&739,TSL,0&&31:PCUPPC,8,
740&742,TSL,0&&31;
ZWTP:BCSU,4:PCU2_E,12,5::<PCUDSP/PCUPAB>,8,760&&763,TSL,0&&31:PCUPPC,8,
764&766,TSL,0&&31;
ZWTP:BCSU,5:PCU2_E,12,5::<PCUDSP/PCUPAB>,8,1016&&1019,TSL,0&&31:PCUPPC
,8,1020&1022,TSL,0&&31;
ZWTP:BCSU,6:PCU2_E,12,5::<PCUDSP/PCUPAB>,8,784&&787,TSL,0&&31:PCUPPC,8,
788&790,TSL,0&&31;
ZWTP:BCSU,7:PCU2_E,12,5::<PCUDSP/PCUPAB>,8,808&&811,TSL,0&&31:PCUPPC,8,
812&814,TSL,0&&31;
ZWTP:BCSU,8:PCU2_E,12,5::<PCUDSP/PCUPAB>,8,832&&835,TSL,0&&31:PCUPPC,8,
836&838,TSL,0&&31;
ZWTP:BCSU,9:PCU2_E,12,5::<PCUDSP/PCUPAB>,8,856&&859,TSL,0&&31:PCUPPC,8,
860&862,TSL,0&&31;
ZWTP:BCSU,10:PCU2_E,12,5::<PCUDSP/PCUPAB>,8,1592&&1595,TSL,0&&31:PCUPP
C,8,1596&1598,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_E,12;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

93 (149)

9.5.7

PCU_B Track 6 PCM Configuration in BSC3i 1000/2000

Install the PCU_B to BCSU track 6. One PCM is used for the Abis and one for the Gb interface. PCMs will be
defined with two plug-in unit functions: PCUDSP and PCUPPC.
The PCU_B plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU_B,3,6::PCUDSP,4,130,TSL,0&&31,1:PCUDSP,4,131,TSL,0&&31,1:P
CUPPC,4,137,TSL,0&&31,2;
ZWTP:BCSU,0:PCU_B,4,6::PCUDSP,4,128,TSL,0&&31,1:PCUDSP,4,129,TSL,0&&31,1:P
CUPPC,4,136,TSL,0&&31,2;
ZWTP:BCSU,1:PCU_B,3,6::PCUDSP,4,146,TSL,0&&31,1:PCUDSP,4,147,TSL,0&&31,1:P
CUPPC,4,153,TSL,0&&31,2;
ZWTP:BCSU,1:PCU_B,4,6::PCUDSP,4,144,TSL,0&&31,1:PCUDSP,4,145,TSL,0&&31,1:P
CUPPC,4,152,TSL,0&&31,2;
ZWTP:BCSU,2:PCU_B,3,6::PCUDSP,4,162,TSL,0&&31,1:PCUDSP,4,163,TSL,0&&31,1:P
CUPPC,4,169,TSL,0&&31,2;
ZWTP:BCSU,2:PCU_B,4,6::PCUDSP,4,160,TSL,0&&31,1:PCUDSP,4,161,TSL,0&&31,1:P
CUPPC,4,151,TSL,0&&31,2;
ZWTP:BCSU,3:PCU_B,3,6::PCUDSP,4,178,TSL,0&&31,1:PCUDSP,4,179,TSL,0&&31,1:P
CUPPC,4,185,TSL,0&&31,2;
ZWTP:BCSU,3:PCU_B,4,6::PCUDSP,4,176,TSL,0&&31,1:PCUDSP,4,177,TSL,0&&31,1:P
CUPPC,4,184,TSL,0&&31,2;
ZWTP:BCSU,4:PCU_B,3,6::PCUDSP,4,258,TSL,0&&31,1:PCUDSP,4,259,TSL,0&&31,1:P
CUPPC,4,265,TSL,0&&31,2;
ZWTP:BCSU,4:PCU_B,4,6::PCUDSP,4,256,TSL,0&&31,1:PCUDSP,4,257,TSL,0&&31,1:P
CUPPC,4,264,TSL,0&&31,2;
ZWTP:BCSU,5:PCU_B,3,6::PCUDSP,4,274,TSL,0&&31,1:PCUDSP,4,275,TSL,0&&31,1:P
CUPPC,4,281,TSL,0&&31,2;
ZWTP:BCSU,5:PCU_B,4,6::PCUDSP,4,272,TSL,0&&31,1:PCUDSP,4,273,TSL,0&&31,1:P
CUPPC,4,280,TSL,0&&31,2;
ZWTP:BCSU,6:PCU_B,3,6::PCUDSP,4,1074,TSL,0&&31,1:PCUDSP,4,1075,TSL,0&&31,1
:PCUPPC,4,1081,TSL,0&&31,2;
ZWTP:BCSU,6:PCU_B,4,6::PCUDSP,4,1072,TSL,0&&31,1:PCUDSP,4,1073,TSL,0&&31,1
:PCUPPC,4,1080,TSL,0&&31,2;
ZWTP:BCSU,7:PCU_B,3,6::PCUDSP,4,1154,TSL,0&&31,1:PCUDSP,4,1155,TSL,0&&31,1
:PCUPPC,4,1161,TSL,0&&31,2;
ZWTP:BCSU,7:PCU_B,4,6::PCUDSP,4,1152,TSL,0&&31,1:PCUDSP,4,1153,TSL,0&&31,1
:PCUPPC,4,1160,TSL,0&&31,2;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

94 (149)

ZWTP:BCSU,8:PCU_B,3,6::PCUDSP,4,1170,TSL,0&&31,1:PCUDSP,4,1171,TSL,0&&31,1
:PCUPPC,4,1177,TSL,0&&31,2;
ZWTP:BCSU,8:PCU_B,4,6::PCUDSP,4,1168,TSL,0&&31,1:PCUDSP,4,1169,TSL,0&&31,1
:PCUPPC,4,1176,TSL,0&&31,2;
ZWTP:BCSU,9:PCU_B,3,6::PCUDSP,4,1186,TSL,0&&31,1:PCUDSP,4,1187,TSL,0&&31,1
:PCUPPC,4,1193,TSL,0&&31,2;
ZWTP:BCSU,9:PCU_B,4,6::PCUDSP,4,1184,TSL,0&&31,1:PCUDSP,4,1185,TSL,0&&31,1
:PCUPPC,4,1192,TSL,0&&31,2;
ZWTP:BCSU,10:PCU_B,3,6::PCUDSP,4,1202,TSL,0&&31,1:PCUDSP,4,1203,TSL,0&&31,
1:PCUPPC,4,1209,TSL,0&&31,2;
ZWTP:BCSU,10:PCU_B,4,6::PCUDSP,4,1200,TSL,0&&31,1:PCUDSP,4,1201,TSL,0&&31,
1:PCUPPC,4,1208,TSL,0&&31,2;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>: PCU_B,3;
ZWUC:BCSU,<index>: PCU_B,4;

9.5.8

PCU_B Track 7 PCM Configuration in BSC3i 1000/2000

Install the PCU_B to BCSU track 7. One PCM is used for the Abis and one for the Gb interface. PCMs will be
defined with two plug-in unit functions: PCUDSP and PCUPPC.
The PCU_B plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU_B,5,7::PCUDSP,4,134,TSL,0&&31,1:PCUDSP,4,135,TSL,0&&31,1:P
CUPPC,4,141,TSL,0&&31,2;
ZWTP:BCSU,0:PCU_B,6,7::PCUDSP,4,132,TSL,0&&31,1:PCUDSP,4,133,TSL,0&&31,1:P
CUPPC,4,140,TSL,0&&31,2;
ZWTP:BCSU,1:PCU_B,5,7::PCUDSP,4,150,TSL,0&&31,1:PCUDSP,4,151,TSL,0&&31,1:P
CUPPC,4,157,TSL,0&&31,2;
ZWTP:BCSU,1:PCU_B,6,7::PCUDSP,4,148,TSL,0&&31,1:PCUDSP,4,149,TSL,0&&31,1:P
CUPPC,4,156,TSL,0&&31,2;
ZWTP:BCSU,2:PCU_B,5,7::PCUDSP,4,166,TSL,0&&31,1:PCUDSP,4,167,TSL,0&&31,1:P
CUPPC,4,173,TSL,0&&31,2;
ZWTP:BCSU,2:PCU_B,6,7::PCUDSP,4,164,TSL,0&&31,1:PCUDSP,4,165,TSL,0&&31,1:P
CUPPC,4,172,TSL,0&&31,2;
ZWTP:BCSU,3:PCU_B,5,7::PCUDSP,4,182,TSL,0&&31,1:PCUDSP,4,183,TSL,0&&31,1:P
CUPPC,4,189,TSL,0&&31,2;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

95 (149)

ZWTP:BCSU,3:PCU_B,6,7::PCUDSP,4,180,TSL,0&&31,1:PCUDSP,4,181,TSL,0&&31,1:P
CUPPC,4,188,TSL,0&&31,2;
ZWTP:BCSU,4:PCU_B,5,7::PCUDSP,4,262,TSL,0&&31,1:PCUDSP,4,263,TSL,0&&31,1:P
CUPPC,4,269,TSL,0&&31,2;
ZWTP:BCSU,4:PCU_B,6,7::PCUDSP,4,260,TSL,0&&31,1:PCUDSP,4,261,TSL,0&&31,1:P
CUPPC,4,268,TSL,0&&31,2;
ZWTP:BCSU,5:PCU_B,5,7::PCUDSP,4,278,TSL,0&&31,1:PCUDSP,4,279,TSL,0&&31,1:P
CUPPC,4,285,TSL,0&&31,2;
ZWTP:BCSU,5:PCU_B,6,7::PCUDSP,4,276,TSL,0&&31,1:PCUDSP,4,277,TSL,0&&31,1:P
CUPPC,4,284,TSL,0&&31,2;
ZWTP:BCSU,6:PCU_B,5,7::PCUDSP,4,1078,TSL,0&&31,1:PCUDSP,4,1079,TSL,0&&31,1
:PCUPPC,4,1085,TSL,0&&31,2;
ZWTP:BCSU,6:PCU_B,6,7::PCUDSP,4,1076,TSL,0&&31,1:PCUDSP,4,1077,TSL,0&&31,1
:PCUPPC,4,1084,TSL,0&&31,2;
ZWTP:BCSU,7:PCU_B,5,7::PCUDSP,4,1158,TSL,0&&31,1:PCUDSP,4,1159,TSL,0&&31,1
:PCUPPC,4,1165,TSL,0&&31,2;
ZWTP:BCSU,7:PCU_B,6,7::PCUDSP,4,1156,TSL,0&&31,1:PCUDSP,4,1157,TSL,0&&31,1
:PCUPPC,4,1164,TSL,0&&31,2;
ZWTP:BCSU,8:PCU_B,5,7::PCUDSP,4,1174,TSL,0&&31,1:PCUDSP,4,1175,TSL,0&&31,1
:PCUPPC,4,1181,TSL,0&&31,2;
ZWTP:BCSU,8:PCU_B,6,7::PCUDSP,4,1172,TSL,0&&31,1:PCUDSP,4,1173,TSL,0&&31,1
:PCUPPC,4,1180,TSL,0&&31,2;
ZWTP:BCSU,9:PCU_B,5,7::PCUDSP,4,1190,TSL,0&&31,1:PCUDSP,4,1191,TSL,0&&31,1
:PCUPPC,4,1197,TSL,0&&31,2;
ZWTP:BCSU,9:PCU_B,6,7::PCUDSP,4,1188,TSL,0&&31,1:PCUDSP,4,1189,TSL,0&&31,1
:PCUPPC,4,1196,TSL,0&&31,2;
ZWTP:BCSU,10:PCU_B,5,7::PCUDSP,4,1206,TSL,0&&31,1:PCUDSP,4,1207,TSL,0&&31,
1:PCUPPC,4,1213,TSL,0&&31,2;
ZWTP:BCSU,10:PCU_B,6,7::PCUDSP,4,1204,TSL,0&&31,1:PCUDSP,4,1205,TSL,0&&31,
1:PCUPPC,4,1212,TSL,0&&31,2;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU_B,5;
ZWUC:BCSU,<index>:PCU_B,6;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

96 (149)

9.5.9

PCU2_D Track 6 PCM Configuration in BSC3i 1000/2000

Install the PCU2_D to BCSU track 6. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_D plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_D,3,6::<PCUDSP/PCUPAB>,4,130,TSL,0&&31:<PCUDSP/PCUPA
B>,4,131,TSL,0&&31:PCUPPC,4,137,TSL,0&&31;
ZWTP:BCSU,0:PCU2_D,4,6::<PCUDSP/PCUPAB>,4,128,TSL,0&&31:<PCUDSP/PCUPA
B>,4,129,TSL,0&&31:PCUPPC,4,136,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,3,6::<PCUDSP/PCUPAB>,4,146,TSL,0&&31:<PCUDSP/PCUPA
B>,4,147,TSL,0&&31:PCUPPC,4,153,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,4,6::<PCUDSP/PCUPAB>,4,144,TSL,0&&31:<PCUDSP/PCUPA
B>,4,145,TSL,0&&31:PCUPPC,4,152,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,3,6::<PCUDSP/PCUPAB>,4,162,TSL,0&&31:<PCUDSP/PCUPA
B>,4,163,TSL,0&&31:PCUPPC,4,169,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,4,6::<PCUDSP/PCUPAB>,4,160,TSL,0&&31:<PCUDSP/PCUPA
B>,4,161,TSL,0&&31:PCUPPC,4,151,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,3,6::<PCUDSP/PCUPAB>,4,178,TSL,0&&31:<PCUDSP/PCUPA
B>,4,179,TSL,0&&31:PCUPPC,4,185,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,4,6::<PCUDSP/PCUPAB>,4,176,TSL,0&&31:<PCUDSP/PCUPA
B>,4,177,TSL,0&&31:PCUPPC,4,184,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,3,6::<PCUDSP/PCUPAB>,4,258,TSL,0&&31:<PCUDSP/PCUPA
B>,4,259,TSL,0&&31:PCUPPC,4,265,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,4,6::<PCUDSP/PCUPAB>,4,256,TSL,0&&31:<PCUDSP/PCUPA
B>,4,257,TSL,0&&31:PCUPPC,4,264,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,3,6::<PCUDSP/PCUPAB>,4,274,TSL,0&&31:<PCUDSP/PCUPA
B>,4,275,TSL,0&&31:PCUPPC,4,281,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,4,6::<PCUDSP/PCUPAB>,4,272,TSL,0&&31:<PCUDSP/PCUPA
B>,4,273,TSL,0&&31:PCUPPC,4,280,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,3,6::<PCUDSP/PCUPAB>,4,1074,TSL,0&&31:<PCUDSP/PCUPA
B>,4,1075,TSL,0&&31:PCUPPC,4,1081,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,4,6::<PCUDSP/PCUPAB>,4,1072,TSL,0&&31:<PCUDSP/PCUPA
B>,4,1073,TSL,0&&31:PCUPPC,4,1080,TSL,0&&31;
ZWTP:BCSU,7:PCU2_D,3,6::<PCUDSP/PCUPAB>,4,1154,TSL,0&&31:<PCUDSP/PCUPA
B>,4,1155,TSL,0&&31:PCUPPC,4,1161,TSL,0&&31;
ZWTP:BCSU,7:PCU2_D,4,6::<PCUDSP/PCUPAB>,4,1152,TSL,0&&31:<PCUDSP/PCUPA
B>,4,1153,TSL,0&&31:PCUPPC,4,1160,TSL,0&&31;
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

97 (149)

ZWTP:BCSU,8:PCU2_D,3,6::<PCUDSP/PCUPAB>,4,1170,TSL,0&&31:<PCUDSP/PCUPA
B>,4,1171,TSL,0&&31:PCUPPC,4,1177,TSL,0&&31;
ZWTP:BCSU,8:PCU2_D,4,6::<PCUDSP/PCUPAB>,4,1168,TSL,0&&31:<PCUDSP/PCUPA
B>,4,1169,TSL,0&&31:PCUPPC,4,1176,TSL,0&&31;
ZWTP:BCSU,9:PCU2_D,3,6::<PCUDSP/PCUPAB>,4,1186,TSL,0&&31:<PCUDSP/PCUPA
B>,4,1187,TSL,0&&31:PCUPPC,4,1193,TSL,0&&31;
ZWTP:BCSU,9:PCU2_D,4,6::<PCUDSP/PCUPAB>,4,1184,TSL,0&&31:<PCUDSP/PCUPA
B>,4,1185,TSL,0&&31:PCUPPC,4,1192,TSL,0&&31;
ZWTP:BCSU,10:PCU2_D,3,6::<PCUDSP/PCUPAB>,4,1202,TSL,0&&31:<PCUDSP/PCUP
AB>,4,1203,TSL,0&&31:PCUPPC,4,1209,TSL,0&&31;
ZWTP:BCSU,10:PCU2_D,4,6::<PCUDSP/PCUPAB>,4,1200,TSL,0&&31:<PCUDSP/PCUP
AB>,4,1201,TSL,0&&31:PCUPPC,4,1208,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_D,3;
ZWUC:BCSU,<index>:PCU2_D,4;

9.5.10

PCU2_D Track 7 PCM Configuration in BSC3i 1000/2000

Install the PCU2_D to BCSU track 7. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_D plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_D,5,7::<PCUDSP/PCUPAB>,4,134,TSL,0&&31:<PCUDSP/PCUPA
B>,4,135,TSL,0&&31:PCUPPC,4,141,TSL,0&&31;
ZWTP:BCSU,0:PCU2_D,6,7::<PCUDSP/PCUPAB>,4,132,TSL,0&&31:<PCUDSP/PCUPA
B>,4,133,TSL,0&&31:PCUPPC,4,140,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,5,7::<PCUDSP/PCUPAB>,4,150,TSL,0&&31:<PCUDSP/PCUPA
B>,4,151,TSL,0&&31:PCUPPC,4,157,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,6,7::<PCUDSP/PCUPAB>,4,148,TSL,0&&31:<PCUDSP/PCUPA
B>,4,149,TSL,0&&31:PCUPPC,4,156,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,5,7::<PCUDSP/PCUPAB>,4,166,TSL,0&&31:<PCUDSP/PCUPA
B>,4,167,TSL,0&&31:PCUPPC,4,173,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,6,7::<PCUDSP/PCUPAB>,4,164,TSL,0&&31:<PCUDSP/PCUPA
B>,4,165,TSL,0&&31:PCUPPC,4,172,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,5,7::<PCUDSP/PCUPAB>,4,182,TSL,0&&31:<PCUDSP/PCUPA
B>,4,183,TSL,0&&31:PCUPPC,4,189,TSL,0&&31;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

98 (149)

ZWTP:BCSU,3:PCU2_D,6,7::<PCUDSP/PCUPAB>,4,180,TSL,0&&31:<PCUDSP/PCUPA
B>,4,181,TSL,0&&31:PCUPPC,4,188,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,5,7::<PCUDSP/PCUPAB>,4,262,TSL,0&&31:<PCUDSP/PCUPA
B>,4,263,TSL,0&&31:PCUPPC,4,269,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,6,7::<PCUDSP/PCUPAB>,4,260,TSL,0&&31:<PCUDSP/PCUPA
B>,4,261,TSL,0&&31:PCUPPC,4,268,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,5,7::<PCUDSP/PCUPAB>,4,278,TSL,0&&31:<PCUDSP/PCUPA
B>,4,279,TSL,0&&31:PCUPPC,4,285,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,6,7::<PCUDSP/PCUPAB>,4,276,TSL,0&&31:<PCUDSP/PCUPA
B>,4,277,TSL,0&&31:PCUPPC,4,284,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,5,7::<PCUDSP/PCUPAB>,4,1078,TSL,0&&31:<PCUDSP/PCUPA
B>,4,1079,TSL,0&&31:PCUPPC,4,1085,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,6,7::<PCUDSP/PCUPAB>,4,1076,TSL,0&&31:<PCUDSP/PCUPA
B>,4,1077,TSL,0&&31:PCUPPC,4,1084,TSL,0&&31;
ZWTP:BCSU,7:PCU2_D,5,7::<PCUDSP/PCUPAB>,4,1158,TSL,0&&31:<PCUDSP/PCUPA
B>,4,1159,TSL,0&&31:PCUPPC,4,1165,TSL,0&&31;
ZWTP:BCSU,7:PCU2_D,6,7::<PCUDSP/PCUPAB>,4,1156,TSL,0&&31:<PCUDSP/PCUPA
B>,4,1157,TSL,0&&31:PCUPPC,4,1164,TSL,0&&31;
ZWTP:BCSU,8:PCU2_D,5,7::<PCUDSP/PCUPAB>,4,1174,TSL,0&&31:<PCUDSP/PCUPA
B>,4,1175,TSL,0&&31:PCUPPC,4,1181,TSL,0&&31;
ZWTP:BCSU,8:PCU2_D,6,7::<PCUDSP/PCUPAB>,4,1172,TSL,0&&31:<PCUDSP/PCUPA
B>,4,1173,TSL,0&&31:PCUPPC,4,1180,TSL,0&&31;
ZWTP:BCSU,9:PCU2_D,5,7::<PCUDSP/PCUPAB>,4,1190,TSL,0&&31:<PCUDSP/PCUPA
B>,4,1191,TSL,0&&31:PCUPPC,4,1197,TSL,0&&31;
ZWTP:BCSU,9:PCU2_D,6,7::<PCUDSP/PCUPAB>,4,1188,TSL,0&&31:<PCUDSP/PCUPA
B>,4,1189,TSL,0&&31:PCUPPC,4,1196,TSL,0&&31;
ZWTP:BCSU,10:PCU2_D,5,7::<PCUDSP/PCUPAB>,4,1206,TSL,0&&31:<PCUDSP/PCUP
AB>,4,1207,TSL,0&&31:PCUPPC,4,1213,TSL,0&&31;
ZWTP:BCSU,10:PCU2_D,6,7::<PCUDSP/PCUPAB>,4,1204,TSL,0&&31:<PCUDSP/PCUP
AB>,4,1205,TSL,0&&31:PCUPPC,4,1212,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_D,5;
ZWUC:BCSU,<index>:PCU2_D,6;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

99 (149)

9.5.11

PCU2_E Track 6 PCM Configuration in BSC3i 1000/2000

Install the PCU2_E to BCSU track 6. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_E plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,4,6::<PCUDSP/PCUPAB>,4,128&&131,TSL,0&&31:PCUPPC,4,1
36&137,TSL,0&&31;
ZWTP:BCSU,1:PCU2_E,4,6::<PCUDSP/PCUPAB>,4,144&&147,TSL,0&&31:PCUPPC,4,1
52&153,TSL,0&&31;
ZWTP:BCSU,2:PCU2_E,4,6::<PCUDSP/PCUPAB>,4,160&&163,TSL,0&&31:PCUPPC,4,1
68&169,TSL,0&&31;
ZWTP:BCSU,3:PCU2_E,4,6::<PCUDSP/PCUPAB>,4,176&&179,TSL,0&&31:PCUPPC,4,1
84&185,TSL,0&&31;
ZWTP:BCSU,4:PCU2_E,4,6::<PCUDSP/PCUPAB>,4,256&&259,TSL,0&&31:PCUPPC,4,2
64&265,TSL,0&&31;
ZWTP:BCSU,5:PCU2_E,4,6::<PCUDSP/PCUPAB>,4,272&&275,TSL,0&&31:PCUPPC,4,2
80&281,TSL,0&&31;

ZWTP:BCSU,6:PCU2_E,4,6::<PCUDSP/PCUPAB>,4,1072&&1075,TSL,0&&31:PCUPPC,
4,1080&1081,TSL,0&&31;
ZWTP:BCSU,7:PCU2_E,4,6::<PCUDSP/PCUPAB>,4,1152&&1155,TSL,0&&31:PCUPPC,
4,1160&1161,TSL,0&&31;
ZWTP:BCSU,8:PCU2_E,4,6::<PCUDSP/PCUPAB>,4,1168&&1171,TSL,0&&31:PCUPPC,
4,1176&1177,TSL,0&&31;
ZWTP:BCSU,9:PCU2_E,4,6::<PCUDSP/PCUPAB>,4,1184&&1187,TSL,0&&31:PCUPPC,
4,1192&1193,TSL,0&&31;
ZWTP:BCSU,10:PCU2_E,4,6::<PCUDSP/PCUPAB>,4,1200&&1203,TSL,0&&31:PCUPPC
,4,1208&1209,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_E,4;

9.5.12

PCU2_E Track 7 PCM Configuration in BSC3i 1000/2000

Install the PCU2_E to BCSU track 7. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_D plug-in unit is created to the EQUIPM database with the following MML-command:
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

100 (149)

ZWTP:BCSU,0:PCU2_E,6,7::<PCUDSP/PCUPAB>,4,132&&135,TSL,0&&31:PCUPPC,4,1
40&141,TSL,0&&31;
ZWTP:BCSU,1:PCU2_E,6,7::<PCUDSP/PCUPAB>,4,148&&151,TSL,0&&31:PCUPPC,4,1
56&157,TSL,0&&31;
ZWTP:BCSU,2:PCU2_E,6,7::<PCUDSP/PCUPAB>,4,164&&167,TSL,0&&31:PCUPPC,4,1
72&173,TSL,0&&31;
ZWTP:BCSU,3:PCU2_E,6,7::<PCUDSP/PCUPAB>,4,180&&183,TSL,0&&31:PCUPPC,4,1
88&189,TSL,0&&31;
ZWTP:BCSU,4:PCU2_E,6,7::<PCUDSP/PCUPAB>,4,260&&263,TSL,0&&31:PCUPPC,4,2
68&269,TSL,0&&31;
ZWTP:BCSU,5:PCU2_E,6,7::<PCUDSP/PCUPAB>,4,276&&279,TSL,0&&31:PCUPPC,4,2
84&285,TSL,0&&31;
ZWTP:BCSU,6:PCU2_E,6,7::<PCUDSP/PCUPAB>,4,1076&&1079,TSL,0&&31:PCUPPC,
4,1084&1085,TSL,0&&31;
ZWTP:BCSU,7:PCU2_E,6,7::<PCUDSP/PCUPAB>,4,1156&&1159,TSL,0&&31:PCUPPC,
4,1164&1165,TSL,0&&31;
ZWTP:BCSU,8:PCU2_E,6,7::<PCUDSP/PCUPAB>,4,1172&&1175,TSL,0&&31:PCUPPC,
4,1180&1181,TSL,0&&31;
ZWTP:BCSU,9:PCU2_E,6,7::<PCUDSP/PCUPAB>,4,1188&&1191,TSL,0&&31:PCUPPC,
4,1196&1197,TSL,0&&31;
ZWTP:BCSU,10:PCU2_E,6,7::<PCUDSP/PCUPAB>,4,1204&&1207,TSL,0&&31:PCUPPC
,4,1212&1213,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_E,6;

9.6

Upgraded Flexi BSC BCSU Unit upgrade

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

ZUSC:BCSU,<index>:TE,;
ZUSC:BCSU,<index>:SE,;
ZUSC:BCSU,<index>:SE,;
Switch the BCSU cartridge power off from the PSC6-A or PSC6-B power supply.
Check that all the PCU plug-in unit jumpers are set according to the instructions (Appendix4, PCU_B Jumper
settings, Appendix5, PCU2_D Jumper settings or Appendix6, PCU2-E Jumper settings)
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

101 (149)

Install the PCU2_D/PCU2_E to BCSU track 3, see chapters 9.6.1 or 9.6.4.


Install the PCU2_D/PCU2_E to BCSU track 4, see chapters 9.6.2 or 9.6.5.
Install the PCU2_D/PCU2_E to BCSU track 5, see chapters 9.6.3 or 9.6.6.
Install the PCU2_D/PCU2-E to BCSU track 6, see chapters 9.6.7 or 9.6.9.
Install the PCU2_D/PCU2_E to BCSU track 7, see chapters 9.6.8, or 9.6.10.
Create GB interface to BCSU if needed:

ZQRA:BCSU,<index> :<PCU_type>,<PCU_index> :IFETH0::UP;


ZQRA:BCSU,<index> :<PCU_type>,<PCU_index> :IFETH1::UP;

If more than two PCU2-E plug-in units are to be installed, also new power must be changed in this step (PSC6-D).
See more information from chapter 8.2.
Switch the BCSU cartridge power on (PSC6-A/PSC6-B/PSC6-D) to power supply.
Change the BCSU state to TE-EX:

ZUSC:BCSU,<index>:SE,;
ZUSC:BCSU,<index>:TE,;
After PCU installation, boot software checking is done. If update is needed, macro executes update according
instructions 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,<index>:C=DSK;
Alter restart execute diagnostic:

ZUDU:BCSU,<index>;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

102 (149)

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

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

ZUSC:BCSU,<index>:SP,;
In case of PCU2-E installation, BCSU-0 (primary spare unit) is changed to SP-EX state and after that switchover
will be done to BCSU unit to be upgraded next.

Repeat these steps for all BCSU(s).

9.6.1

PCU2_D Track 3 PCM Configuration in upgraded Flexi BSC

Install the PCU2_D to BCSU track 3. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_D plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,650,TSL,0&&31:<PCUDSP/PCUPA
B>,8,651,TSL,0&&31:PCUPPC,8,654,TSL,0&&31;
ZWTP:BCSU,0:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,648,TSL,0&&31:<PCUDSP/PCUPA
B>,8,649,TSL,0&&31:PCUPPC,8,652,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,674,TSL,0&&31:<PCUDSP/PCUPA
B>,8,675,TSL,0&&31:PCUPPC,8,678,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,672,TSL,0&&31:<PCUDSP/PCUPA
B>,8,673,TSL,0&&31:PCUPPC,8,676,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,698,TSL,0&&31:<PCUDSP/PCUPA
B>,8,699,TSL,0&&31:PCUPPC,8,702,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,696,TSL,0&&31:<PCUDSP/PCUPA
B>,8,697,TSL,0&&31:PCUPPC,8,700,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,722,TSL,0&&31:<PCUDSP/PCUPA
B>,8,723,TSL,0&&31:PCUPPC,8,726,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,720,TSL,0&&31:<PCUDSP/PCUPA
B>,8,721,TSL,0&&31:PCUPPC,8,724,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,1170,TSL,0&&31:<PCUDSP/PCUPA
B>,8,1171,TSL,0&&31:PCUPPC,8,1174,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,1168,TSL,0&&31:<PCUDSP/PCUPA
B>,8,1169,TSL,0&&31:PCUPPC,8,1172,TSL,0&&31;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

103 (149)

ZWTP:BCSU,5:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,850,TSL,0&&31:<PCUDSP/PCUPA
B>,8,851,TSL,0&&31:PCUPPC,8,854,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,848,TSL,0&&31:<PCUDSP/PCUPA
B>,8,849,TSL,0&&31:PCUPPC,8,852,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,7,3::<PCUDSP/PCUPAB>,8,1554,TSL,0&&31:<PCUDSP/PCUPA
B>,8,1555,TSL,0&&31:PCUPPC,8,1558,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,8,3::<PCUDSP/PCUPAB>,8,1552,TSL,0&&31:<PCUDSP/PCUPA
B>,8,1553,TSL,0&&31:PCUPPC,8,1556,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_D,7;
ZWUC:BCSU,<index>:PCU2_D,8;

9.6.2

PCU2_D Track 4 PCM Configuration in upgraded Flexi BSC

Install the PCU2_D to BCSU track 4. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_D plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,658,TSL,0&&31:<PCUDSP/PCUPA
B>,8,659,TSL,0&&31:PCUPPC,8,662,TSL,0&&31;
ZWTP:BCSU,0:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,656,TSL,0&&31:<PCUDSP/PCUPA
B>,8,657,TSL,0&&31:PCUPPC,8,660,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,682,TSL,0&&31:<PCUDSP/PCUPA
B>,8,683,TSL,0&&31:PCUPPC,8,686,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,680,TSL,0&&31:<PCUDSP/PCUPA
B>,8,681,TSL,0&&31:PCUPPC,8,684,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,706,TSL,0&&31:<PCUDSP/PCUPA
B>,8,707,TSL,0&&31:PCUPPC,8,710,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,704,TSL,0&&31:<PCUDSP/PCUPA
B>,8,705,TSL,0&&31:PCUPPC,8,708,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,730,TSL,0&&31:<PCUDSP/PCUPA
B>,8,731,TSL,0&&31:PCUPPC,8,734,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,728,TSL,0&&31:<PCUDSP/PCUPA
B>,8,729,TSL,0&&31:PCUPPC,8,732,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,1178,TSL,0&&31:<PCUDSP/PCUPA
B>,8,1179,TSL,0&&31:PCUPPC,8,1182,TSL,0&&31;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

104 (149)

ZWTP:BCSU,4:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,1176,TSL,0&&31:<PCUDSP/PCUP
AB>,8,1177,TSL,0&&31:PCUPPC,8,1180,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,858,TSL,0&&31:<PCUDSP/PCUPA
B>,8,859,TSL,0&&31:PCUPPC,8,862,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,856,TSL,0&&31:<PCUDSP/PCUPA
B>,8,857,TSL,0&&31:PCUPPC,8,860,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,9,4::<PCUDSP/PCUPAB>,8,1562,TSL,0&&31:<PCUDSP/PCUPA
B>,8,1563,TSL,0&&31:PCUPPC,8,1566,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,10,4::<PCUDSP/PCUPAB>,8,1560,TSL,0&&31:<PCUDSP/PCUP
AB>,8,1561,TSL,0&&31:PCUPPC,8,1564,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_D,9;
ZWUC:BCSU,<index>:PCU2_D,10;

9.6.3

PCU2_D Track 5 PCM Configuration in upgraded Flexi BSC

Install the PCU2_D to BCSU track 5. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_D plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,666,TSL,0&&31:<PCUDSP/PCUPA
B>,8,667,TSL,0&&31:PCUPPC,8,670,TSL,0&&31;
ZWTP:BCSU,0:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,664,TSL,0&&31:<PCUDSP/PCUPA
B>,8,665,TSL,0&&31:PCUPPC,8,668,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,690,TSL,0&&31:<PCUDSP/PCUPA
B>,8,691,TSL,0&&31:PCUPPC,8,694,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,688,TSL,0&&31:<PCUDSP/PCUPA
B>,8,689,TSL,0&&31:PCUPPC,8,692,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,714,TSL,0&&31:<PCUDSP/PCUPA
B>,8,715,TSL,0&&31:PCUPPC,8,718,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,712,TSL,0&&31:<PCUDSP/PCUPA
B>,8,713,TSL,0&&31:PCUPPC,8,716,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,738,TSL,0&&31:<PCUDSP/PCUPA
B>,8,739,TSL,0&&31:PCUPPC,8,742,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,736,TSL,0&&31:<PCUDSP/PCUPA
B>,8,737,TSL,0&&31:PCUPPC,8,740,TSL,0&&31;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

105 (149)

ZWTP:BCSU,4:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,1186,TSL,0&&31:<PCUDSP/PCUP
AB>,8,1187,TSL,0&&31:PCUPPC,8,1190,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,1184,TSL,0&&31:<PCUDSP/PCUP
AB>,8,1185,TSL,0&&31:PCUPPC,8,1188,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,866,TSL,0&&31:<PCUDSP/PCUPA
B>,8,867,TSL,0&&31:PCUPPC,8,870,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,864,TSL,0&&31:<PCUDSP/PCUPA
B>,8,865,TSL,0&&31:PCUPPC,8,868,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,11,5::<PCUDSP/PCUPAB>,8,1570,TSL,0&&31:<PCUDSP/PCUP
AB>,8,1571,TSL,0&&31:PCUPPC,8,1574,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,12,5::<PCUDSP/PCUPAB>,8,1568,TSL,0&&31:<PCUDSP/PCUP
AB>,8,1569,TSL,0&&31:PCUPPC,8,1572,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_D,11;
ZWUC:BCSU,<index>:PCU2_D,12;

9.6.4

PCU2_E Track 3 PCM Configuration in upgraded Flexi BSC

Install the PCU2_E to BCSU track 3. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_E plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,8,3,1::<PCUDSP/PCUPAB>,8,648&&651,TSL,0&&31:PCUPPC,8
,652&&655,TSL,0&&31:<PCUDSP/PCUPAB>,8,744&&747,TSL,0&&31:;
ZWTP:BCSU,1:PCU2_E,8,3,1::<PCUDSP/PCUPAB>,8,672&&675,TSL,0&&31:PCUPPC,8
,676&&679,TSL,0&&31:<PCUDSP/PCUPAB>,8,952&&955,TSL,0&&31:;
ZWTP:BCSU,2:PCU2_E,8,3,1::<PCUDSP/PCUPAB>,8,696&&699,TSL,0&&31:PCUPPC,8
,700&&703,TSL,0&&31:<PCUDSP/PCUPAB>,8,976&&979,TSL,0&&31:;
ZWTP:BCSU,3:PCU2_E,8,3,1::<PCUDSP/PCUPAB>,8,720&&723,TSL,0&&31:PCUPPC,8
,724&&727,TSL,0&&31:<PCUDSP/PCUPAB>,8,1000&&1003,TSL,0&&31:;
ZWTP:BCSU,4:PCU2_E,8,3,1::<PCUDSP/PCUPAB>,8,1168&&1171,TSL,0&&31:PCUPP
C,8,1172&&1175,TSL,0&&31:<PCUDSP/PCUPAB>,8,1192&&1195,TSL,0&&31:;
ZWTP:BCSU,5:PCU2_E,8,3,1::<PCUDSP/PCUPAB>,8,848&&851,TSL,0&&31:PCUPPC,8
,852&&855,TSL,0&&31:<PCUDSP/PCUPAB>,8,872&&875,TSL,0&&31:;
ZWTP:BCSU,6:PCU2_E,8,3,1::<PCUDSP/PCUPAB>,8,1552&&1555,TSL,0&&31:PCUPP
C,8,1556&&1559,TSL,0&&31:<PCUDSP/PCUPAB>,8,1576&&1579,TSL,0&&31:;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

106 (149)

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

ZWUC:BCSU,<index>:PCU2_E,8;

9.6.5

PCU2_E Track 4 PCM Configuration in upgraded Flexi BSC

Install the PCU2_E to BCSU track 4. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_E plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,10,4,1::<PCUDSP/PCUPAB>,8,656&&659,TSL,0&&31:PCUPPC,
8,660&&663,TSL,0&&31:<PCUDSP/PCUPAB>,8,752&&755,TSL,0&&31:;
ZWTP:BCSU,1:PCU2_E,10,4,1::<PCUDSP/PCUPAB>,8,680&&683,TSL,0&&31:PCUPPC,
8,684&&687,TSL,0&&31:<PCUDSP/PCUPAB>,8,960&&963,TSL,0&&31:;
ZWTP:BCSU,2:PCU2_E,10,4,1::<PCUDSP/PCUPAB>,8,704&&707,TSL,0&&31:PCUPPC,
8,708&&711,TSL,0&&31:<PCUDSP/PCUPAB>,8,984&&987,TSL,0&&31:;
ZWTP:BCSU,3:PCU2_E,10,4,1::<PCUDSP/PCUPAB>,8,728&&731,TSL,0&&31:PCUPPC,
8,732&&735,TSL,0&&31:<PCUDSP/PCUPAB>,8,1008&&1011,TSL,0&&31:;
ZWTP:BCSU,4:PCU2_E,10,4,1::<PCUDSP/PCUPAB>,8,1176&&1179,TSL,0&&31:PCUPP
C,8,1180&&1183,TSL,0&&31:<PCUDSP/PCUPAB>,8,1200&&1203,TSL,0&&31:;
ZWTP:BCSU,5:PCU2_E,10,4,1::<PCUDSP/PCUPAB>,8,856&&859,TSL,0&&31:PCUPPC,
8,860&&863,TSL,0&&31:<PCUDSP/PCUPAB>,8,880&&883,TSL,0&&31:;
ZWTP:BCSU,6:PCU2_E,10,4,1::<PCUDSP/PCUPAB>,8,1560&&1563,TSL,0&&31:PCUPP
C,8,1564&&1567,TSL,0&&31:<PCUDSP/PCUPAB>,8,1584&&1587,TSL,0&&31:;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_E,10;

9.6.6

PCU2_E Track 5 PCM Configuration in upgraded Flexi BSC

Install the PCU2_E to BCSU track 5. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_E plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,12,5,1::<PCUDSP/PCUPAB>,8,664&&667,TSL,0&&31:PCUPPC,
8,668&&671,TSL,0&&31:<PCUDSP/PCUPAB>,8,760&&763,TSL,0&&31:;
ZWTP:BCSU,1:PCU2_E,12,5,1::<PCUDSP/PCUPAB>,8,688&&691,TSL,0&&31:PCUPPC,
8,692&&695,TSL,0&&31:<PCUDSP/PCUPAB>,8,968&&971,TSL,0&&31:;
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

107 (149)

ZWTP:BCSU,2:PCU2_E,12,5,1::<PCUDSP/PCUPAB>,8,712&&715,TSL,0&&31:PCUPPC,
8,716&&719,TSL,0&&31:<PCUDSP/PCUPAB>,8,992&&995,TSL,0&&31:;
ZWTP:BCSU,3:PCU2_E,12,5,1::<PCUDSP/PCUPAB>,8,736&&739,TSL,0&&31:PCUPPC,
8,740&&743,TSL,0&&31:<PCUDSP/PCUPAB>,8,1016&&1019,TSL,0&&31:;
ZWTP:BCSU,4:PCU2_E,12,5,1::<PCUDSP/PCUPAB>,8,1184&&1187,TSL,0&&31:PCUPP
C,8,1188&&1191,TSL,0&&31:<PCUDSP/PCUPAB>,8,1208&&1211,TSL,0&&31:;
ZWTP:BCSU,5:PCU2_E,12,5,1::<PCUDSP/PCUPAB>,8,864&&867,TSL,0&&31:PCUPPC,
8,868&&871,TSL,0&&31:<PCUDSP/PCUPAB>,8,888&&891,TSL,0&&31:;
ZWTP:BCSU,6:PCU2_E,12,5,1::<PCUDSP/PCUPAB>,8,1568&&1571,TSL,0&&31:PCUPP
C,8,1572&&1575,TSL,0&&31:<PCUDSP/PCUPAB>,8,1592&&1595,TSL,0&&31:;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_E,12;

9.6.7

PCU2_D Track 6 PCM Configuration in upgraded Flexi BSC

Install the PCU2_D to BCSU track 6. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_D plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_D,3,6::<PCUDSP/PCUPAB>,4,274,TSL,0&&31:<PCUDSP/PCUPA
B>,4,275,TSL,0&&31:PCUPPC,4,277,TSL,0&&31;
ZWTP:BCSU,0:PCU2_D,4,6::<PCUDSP/PCUPAB>,4,272,TSL,0&&31:<PCUDSP/PCUPA
B>,4,273,TSL,0&&31:PCUPPC,4,276,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,3,6::<PCUDSP/PCUPAB>,4,298,TSL,0&&31:<PCUDSP/PCUPA
B>,4,299,TSL,0&&31:PCUPPC,4,301,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,4,6::<PCUDSP/PCUPAB>,4,296,TSL,0&&31:<PCUDSP/PCUPA
B>,4,297,TSL,0&&31:PCUPPC,4,300,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,3,6::<PCUDSP/PCUPAB>,4,386,TSL,0&&31:<PCUDSP/PCUPA
B>,4,387,TSL,0&&31:PCUPPC,4,389,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,4,6::<PCUDSP/PCUPAB>,4,384,TSL,0&&31:<PCUDSP/PCUPA
B>,4,385,TSL,0&&31:PCUPPC,4,388,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,3,6::<PCUDSP/PCUPAB>,4,410,TSL,0&&31:<PCUDSP/PCUPA
B>,4,411,TSL,0&&31:PCUPPC,4,413,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,4,6::<PCUDSP/PCUPAB>,4,408,TSL,0&&31:<PCUDSP/PCUPA
B>4,,409,TSL,0&&31:PCUPPC,4,412,TSL,0&&31;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

108 (149)

ZWTP:BCSU,4:PCU2_D,3,6::<PCUDSP/PCUPAB>,8,1042,TSL,0&&31:<PCUDSP/PCUPA
B>,8,1043,TSL,0&&31:PCUPPC,8,1046,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,4,6::<PCUDSP/PCUPAB>,8,1040,TSL,0&&31:<PCUDSP/PCUPA
B>,8,1041,TSL,0&&31:PCUPPC,8,1044,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,3,6::<PCUDSP/PCUPAB>,8,786,TSL,0&&31:<PCUDSP/PCUPA
B>,8,767,TSL,0&&31:PCUPPC,8,790,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,4,6::<PCUDSP/PCUPAB>,8,784,TSL,0&&31:<PCUDSP/PCUPA
B>,8,784,TSL,0&&31:PCUPPC,8,788,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,3,6::<PCUDSP/PCUPAB>,8,1298,TSL,0&&31:<PCUDSP/PCUPA
B>,8,1299,TSL,0&&31:PCUPPC,8,1302,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,4,6::<PCUDSP/PCUPAB>,8,1296,TSL,0&&31:<PCUDSP/PCUPA
B>,8,1297,TSL,0&&31:PCUPPC,8,1300,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_D,3;
ZWUC:BCSU,<index>:PCU2_D,4;

9.6.8

PCU2_D Track 7 PCM Configuration in upgraded Flexi BSC

Install the PCU2_D to BCSU track 7. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: <PCUDSP/PCUPAB> or PCUPAB and PCUPPC.
The PCU2_D plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_D,5,7::<PCUDSP/PCUPAB>,4,286,TSL,0&&31:<PCUDSP/PCUPA
B>,4,287,TSL,0&&31:PCUPPC,4,289,TSL,0&&31;
ZWTP:BCSU,0:PCU2_D,6,7::<PCUDSP/PCUPAB>,4,284,TSL,0&&31:<PCUDSP/PCUPA
B>,4,285,TSL,0&&31:PCUPPC,4,288,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,5,7::<PCUDSP/PCUPAB>,4,311,TSL,0&&31:<PCUDSP/PCUPA
B>,4,312,TSL,0&&31:PCUPPC,4,313,TSL,0&&31;
ZWTP:BCSU,1:PCU2_D,6,7::<PCUDSP/PCUPAB>,4,309,TSL,0&&31:<PCUDSP/PCUPA
B>,4,310,TSL,0&&31:PCUPPC,4,312,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,5,7::<PCUDSP/PCUPAB>,4,389,TSL,0&&31:<PCUDSP/PCUPA
B>,4,399,TSL,0&&31:PCUPPC,4,401,TSL,0&&31;
ZWTP:BCSU,2:PCU2_D,6,7::<PCUDSP/PCUPAB>,4,396,TSL,0&&31:<PCUDSP/PCUPA
B>,4,397,TSL,0&&31:PCUPPC,4,400,TSL,0&&31;
ZWTP:BCSU,3:PCU2_D,5,7::<PCUDSP/PCUPAB>,4,422,TSL,0&&31:<PCUDSP/PCUPA
B>,4,423,TSL,0&&31:PCUPPC,4,425,TSL,0&&31;
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

109 (149)

ZWTP:BCSU,3:PCU2_D,6,7::<PCUDSP/PCUPAB>,4,420,TSL,0&&31:<PCUDSP/PCUPA
B>,4,421,TSL,0&&31:PCUPPC,4,424,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,5,7::<PCUDSP/PCUPAB>,8,1050,TSL,0&&31:<PCUDSP/PCUPA
B>,8,1051,TSL,0&&31:PCUPPC,8,1054,TSL,0&&31;
ZWTP:BCSU,4:PCU2_D,6,7::<PCUDSP/PCUPAB>,8,1048,TSL,0&&31:<PCUDSP/PCUPA
B>,8,1049,TSL,0&&31:PCUPPC,8,1052,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,5,7::<PCUDSP/PCUPAB>,8,794,TSL,0&&31:<PCUDSP/PCUPA
B>,8,795,TSL,0&&31:PCUPPC,8,798,TSL,0&&31;
ZWTP:BCSU,5:PCU2_D,6,7::<PCUDSP/PCUPAB>,8,798,TSL,0&&31:<PCUDSP/PCUPA
B>,8,793,TSL,0&&31:PCUPPC,8,796,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,5,7::<PCUDSP/PCUPAB>,8,1306,TSL,0&&31:<PCUDSP/PCUPA
B>,8,1307,TSL,0&&31:PCUPPC,8,1310,TSL,0&&31;
ZWTP:BCSU,6:PCU2_D,6,7::<PCUDSP/PCUPAB>,8,1304,TSL,0&&31:<PCUDSP/PCUPA
B>,8,1305,TSL,0&&31:PCUPPC,8,1308,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_D,5;
ZWUC:BCSU,<index>:PCU2_D,6;

9.6.9

PCU2_E Track 6 PCM Configuration in upgraded Flexi BSC

Install the PCU2_E to BCSU track 6. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_E plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,4,6,1::<PCUDSP/PCUPAB>,4,272&&275,TSL,0&&31:PCUPPC,4
,276&&279,TSL,0&&31:<PCUDSP/PCUPAB>,4,280&&283,TSL,0&&31:;
ZWTP:BCSU,1:PCU2_E,4,6,1::<PCUDSP/PCUPAB>,4,296&&299,TSL,0&&31:PCUPPC,4
,300&&303,TSL,0&&31:<PCUDSP/PCUPAB>,4,304&&307,TSL,0&&31:;
ZWTP:BCSU,2:PCU2_E,4,6,1::<PCUDSP/PCUPAB>,4,384&&387,TSL,0&&31:PCUPPC,4
,388&&391,TSL,0&&31:<PCUDSP/PCUPAB>,4,392&&395,TSL,0&&31:;
ZWTP:BCSU,3:PCU2_E,4,6,1::<PCUDSP/PCUPAB>,4,408&&411,TSL,0&&31:PCUPPC,4
,412&&415,TSL,0&&31:<PCUDSP/PCUPAB>,4,416&&419,TSL,0&&31:;
ZWTP:BCSU,4:PCU2_E,4,6,1::<PCUDSP/PCUPAB>,8,1040&&1043,TSL,0&&31:PCUPP
C,8,1044&&1047,TSL,0&&31:<PCUDSP/PCUPAB>,8,1056&&1059,TSL,0&&31:;
ZWTP:BCSU,5:PCU2_E,4,6,1::<PCUDSP/PCUPAB>,8,784&&787,TSL,0&&31:PCUPPC,8
,788&&791,TSL,0&&31:<PCUDSP/PCUPAB>,8,800&&803,TSL,0&&31:;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

110 (149)

ZWTP:BCSU,6:PCU2_E,4,6,1::<PCUDSP/PCUPAB>,8,1296&&1299,TSL,0&&31:PCUPP
C,8,1300&&1303,TSL,0&&31:<PCUDSP/PCUPAB>,8,1312&&1315,TSL,0&&31:;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_E,4;

9.6.10

PCU2_E Track 7 PCM Configuration in upgraded Flexi BSC

Install the PCU2_E to BCSU track 7. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_D plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,6,7,1::<PCUDSP/PCUPAB>,4,284&&287,TSL,0&&31:PCUPPC,4
,288&&291,TSL,0&&31:<PCUDSP/PCUPAB>,4,292&&295,TSL,0&&31:;
ZWTP:BCSU,1:PCU2_E,6,7,1::<PCUDSP/PCUPAB>,4,308&&311,TSL,0&&31:PCUPPC,4
,312&&315,TSL,0&&31:<PCUDSP/PCUPAB>,4,316&&319,TSL,0&&31:;
ZWTP:BCSU,2:PCU2_E,6,7,1::<PCUDSP/PCUPAB>,4,396&&399,TSL,0&&31:PCUPPC,4
,400&&403,TSL,0&&31:<PCUDSP/PCUPAB>,4,404&&407,TSL,0&&31:;
ZWTP:BCSU,3:PCU2_E,6,7,1::<PCUDSP/PCUPAB>,4,420&&423,TSL,0&&31:PCUPPC,4
,424&&427,TSL,0&&31:<PCUDSP/PCUPAB>,4,428&&431,TSL,0&&31:;
ZWTP:BCSU,4:PCU2_E,6,7,1::<PCUDSP/PCUPAB>,8,1048&&1051,TSL,0&&31:PCUPP
C,8,1052&&1055,TSL,0&&31:<PCUDSP/PCUPAB>,8,1064&&1067,TSL,0&&31:;

ZWTP:BCSU,5:PCU2_E,6,7,1::<PCUDSP/PCUPAB>,8,792&&795,TSL,0&&31:PCUPPC,8
,796&&799,TSL,0&&31:<PCUDSP/PCUPAB>,8,808&&811,TSL,0&&31:;
ZWTP:BCSU,6:PCU2_E,6,7,1::<PCUDSP/PCUPAB>,8,1304&&1307,TSL,0&&31:PCUPP
C,8,1308&&1311,TSL,0&&31:<PCUDSP/PCUPAB>,8,1320&&1323,TSL,0&&31:;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_E,6;

9.7

New delivery Flexi BSC BCSU Unit upgrade

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

ZUSC:BCSU,<index>:TE,;
ZUSC:BCSU,<index>:SE,;
ZUSC:BCSU,<index>:SE,;
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

111 (149)

Switch the BCSU cartridge power off from the PSC6-AB, PSC6-AC or PSC6-D power supply.
Check that all the PCU plug-in unit jumpers are set according to the instructions (Appendix6, PCU2-E Jumper
settings)
Note!
In new delivery BSC several BCSU units are locating in same cartridge and track indexes are not same in
every BCSU unit. The BCSU-0 units track index is used in chapter names.
Install the PCU2_E to BCSU track 3, see chapters 9.7.1.
Install the PCU2_E to BCSU track 4, see chapters 9.7.2.
Install the PCU2_E to BCSU track 5, see chapters 9.7.3.
Install the PCU2-E to BCSU track 6, see chapters 9.7.7.
Install the PCU2_E to BCSU track 7, see chapters 9.7.8.
Create GB interface to BCSU if needed:

ZQRA:BCSU,<index> :<PCU_type>,<PCU_index> :IFETH0::UP;


ZQRA:BCSU,<index> :<PCU_type>,<PCU_index> :IFETH1::UP;

Switch the BCSU cartridge power on from PSC6-AB, PSC6-AC or PSC6-D power supply.
Change the BCSU state to TE-EX:

ZUSC:BCSU,<index>:SE,;
ZUSC:BCSU,<index>:TE,;
After PCU installation, boot software checking is done. If update is needed, macro executes update according
instructions in chapter 11.3.
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,<index>:C=DSK;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

112 (149)

Alter restart execute diagnostic:

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

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

ZUSC:BCSU,<index>:SP,;
In case of PCU2-E installation, BCSU-0 (primary spare unit) is changed to SP-EX state and after that switchover
will be done to BCSU unit to be upgraded next.

Repeat these steps for all BCSU(s).

9.7.1

PCU2_E Index 8 PCM Configuration in new delivery Flexi BSC

Install the PCU2_E to BCSU track 3. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_E plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,8,3,::<PCUDSP/PCUPAB>,4,16&&19,TSL,0&&31:PCUPPC,4,20
&&23,TSL,0&&31:<PCUDSP/PCUPAB>,4,24&&27,TSL,0&&31;
ZWTP:BCSU,1:PCU2_E,8,2,::<PCUDSP/PCUPAB>,8,496&&499,TSL,0&&31:PCUPPC,8,
500&&503,TSL,0&&31:<PCUDSP/PCUPAB>,8,504&&507,TSL,0&&31::;
ZWTP:BCSU,2:PCU2_E,8,2,::<PCUDSP/PCUPAB>,8,752&&755,TSL,0&&31:PCUPPC,8,
756&&759,TSL,0&&31:<PCUDSP/PCUPAB>,8,760&&763,TSL,0&&31::;
ZWTP:BCSU,3:PCU2_E,8,18,::<PCUDSP/PCUPAB>,8,1008&&1011,TSL,0&&31:PCUPP
C,8,1012&&1015,TSL,0&&31:<PCUDSP/PCUPAB>,8,1016&&1019,TSL,0&&31::;
ZWTP:BCSU,4:PCU2_E,8,18,::<PCUDSP/PCUPAB>,8,1248&&1251,TSL,0&&31:PCUPP
C,8,1252&&1255,TSL,0&&31:<PCUDSP/PCUPAB>,8,1256&&1259,TSL,0&&31;
ZWTP:BCSU,5:PCU2_E,8,28,::<PCUDSP/PCUPAB>,8,1504&&1507,TSL,0&&31:PCUPP
C,8,1508&&1511,TSL,0&&31:<PCUDSP/PCUPAB>,8,1512&&1515,TSL,0&&31;
ZWTP:BCSU,6:PCU2_E,8,28,::<PCUDSP/PCUPAB>,8,1760&&1763,TSL,0&&31:PCUPP
C,8,1764&&1767,TSL,0&&31:<PCUDSP/PCUPAB>,8,1768&&1771,TSL,0&&31;

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

ZWUC:BCSU,<index>:PCU2_E,8;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

113 (149)

9.7.2

PCU2_E Index 10 PCM Configuration in new delivery Flexi BSC

Install the PCU2_E to BCSU track 4. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_E plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,10,4,::<PCUDSP/PCUPAB>,4,28&&31,TSL,0&&31:PCUPPC,4,3
2&&35,TSL,0&&31:<PCUDSP/PCUPAB>,4,36&&39,TSL,0&&31;
ZWTP:BCSU,1:PCU2_E,10,3,::<PCUDSP/PCUPAB>,8,480&&483,TSL,0&&31:PCUPPC,8
,484&&487,TSL,0&&31:<PCUDSP/PCUPAB>,8,488&&491,TSL,0&&31::;
ZWTP:BCSU,2:PCU2_E,10,3,::<PCUDSP/PCUPAB>,8,736&&739,TSL,0&&31:PCUPPC,8
,740&&743,TSL,0&&31:<PCUDSP/PCUPAB>,8,744&&747,TSL,0&&31::;
ZWTP:BCSU,3:PCU2_E,10,19,::<PCUDSP/PCUPAB>,8,992&&995,TSL,0&&31:PCUPPC,
8,996&&999,TSL,0&&31:<PCUDSP/PCUPAB>,8,1000&&1003,TSL,0&&31::;
ZWTP:BCSU,4:PCU2_E,10,19,::<PCUDSP/PCUPAB>,8,1232&&1235,TSL,0&&31:PCUPP
C,8,1236&&1239,TSL,0&&31:<PCUDSP/PCUPAB>,8,1240&&1243,TSL,0&&31;
ZWTP:BCSU,5:PCU2_E,10,29,::<PCUDSP/PCUPAB>,8,1488&&1491,TSL,0&&31:PCUPP
C,8,1492&&1495,TSL,0&&31:<PCUDSP/PCUPAB>,8,1496&&1499,TSL,0&&31;
ZWTP:BCSU,6:PCU2_E,10,29,::<PCUDSP/PCUPAB>,8,1744&&1747,TSL,0&&31:PCUPP
C,8,1748&&1751,TSL,0&&31:<PCUDSP/PCUPAB>,8,1752&&1755,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_E,10;

9.7.3

PCU2_E Index 12 PCM Configuration in new delivery Flexi BSC

Install the PCU2_E to BCSU track 5. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_E plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,12,5,::<PCUDSP/PCUPAB>,4,40&&43,TSL,0&&31:PCUPPC,4,4
4&&47,TSL,0&&31:<PCUDSP/PCUPAB>,4,48&&51,TSL,0&&31;
ZWTP:BCSU,1:PCU2_E,12,4,::<PCUDSP/PCUPAB>,8,464&&467,TSL,0&&31:PCUPPC,8
,468&&471,TSL,0&&31:<PCUDSP/PCUPAB>,8,472&&475,TSL,0&&31::;
ZWTP:BCSU,2:PCU2_E,12,4,::<PCUDSP/PCUPAB>,8,720&&723,TSL,0&&31:PCUPPC,8
,724&&727,TSL,0&&31:<PCUDSP/PCUPAB>,8,728&&731,TSL,0&&31::;
ZWTP:BCSU,3:PCU2_E,12,20,::<PCUDSP/PCUPAB>,8,976&&979,TSL,0&&31:PCUPPC,
8,980&&983,TSL,0&&31:<PCUDSP/PCUPAB>,8,984&&987,TSL,0&&31::;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

114 (149)

ZWTP:BCSU,4:PCU2_E,12,20,::<PCUDSP/PCUPAB>,8,1216&&1219,TSL,0&&31:PCUPP
C,8,1220&&1223,TSL,0&&31:<PCUDSP/PCUPAB>,8,1224&&1227,TSL,0&&31;
ZWTP:BCSU,5:PCU2_E,12,30,::<PCUDSP/PCUPAB>,8,1472&&1475,TSL,0&&31:PCUPP
C,8,1476&&1479,TSL,0&&31:<PCUDSP/PCUPAB>,8,1480&&1483,TSL,0&&31;
ZWTP:BCSU,6:PCU2_E,12,30,::<PCUDSP/PCUPAB>,8,1728&&1731,TSL,0&&31:PCUPP
C,8,1732&&1735,TSL,0&&31:<PCUDSP/PCUPAB>,8,1736&&1739,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_E,12;

9.7.4

PCU2_E Index 4 PCM Configuration in new delivery Flexi BSC

Install the PCU2_E to BCSU track 6. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_E plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,4,6,::<PCUDSP/PCUPAB>,4,52&&55,TSL,0&&31:PCUPPC,4,56
&&59,TSL,0&&31:<PCUDSP/PCUPAB>,4,60&&63,TSL,0&&31;
ZWTP:BCSU,1:PCU2_E,4,5,::<PCUDSP/PCUPAB>,8,448&&451,TSL,0&&31:PCUPPC,8,
452&&455,TSL,0&&31:<PCUDSP/PCUPAB>,8,456&&459,TSL,0&&31::;
ZWTP:BCSU,2:PCU2_E,4,5,::<PCUDSP/PCUPAB>,8,704&&707,TSL,0&&31:PCUPPC,8,
708&&711,TSL,0&&31:<PCUDSP/PCUPAB>,8,712&&715,TSL,0&&31::;
ZWTP:BCSU,3:PCU2_E,4,21,::<PCUDSP/PCUPAB>,8,960&&963,TSL,0&&31:PCUPPC,8
,964&&967,TSL,0&&31:<PCUDSP/PCUPAB>,8,968&&971,TSL,0&&31::;
ZWTP:BCSU,4:PCU2_E,4,21,::<PCUDSP/PCUPAB>,8,1200&&1203,TSL,0&&31:PCUPP
C,8,1204&&1207,TSL,0&&31:<PCUDSP/PCUPAB>,8,1208&&1211,TSL,0&&31;
ZWTP:BCSU,5:PCU2_E,4,31,::<PCUDSP/PCUPAB>,8,1456&&1459,TSL,0&&31:PCUPP
C,8,1460&&1463,TSL,0&&31:<PCUDSP/PCUPAB>,8,1464&&1467,TSL,0&&31;
ZWTP:BCSU,6:PCU2_E,4,31,::<PCUDSP/PCUPAB>,8,1712&&1715,TSL,0&&31:PCUPP
C,8,1716&&1719,TSL,0&&31:<PCUDSP/PCUPAB>,8,1720&&1723,TSL,0&&31;

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

ZWUC:BCSU,<index>:PCU2_E,4;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

115 (149)

9.7.5

PCU2_E Index 6 PCM Configuration in new delivery Flexi BSC

Install the PCU2_E to BCSU track 7. One PCM is used for the Abis and one for the Gb interface. The Packet
Abis feature usage requires different function for Abis interface: PCUPAB.
PCM(s) will be defined with two plug-in unit functions: PCUDSP or PCUPAB and PCUPPC.
The PCU2_D plug-in unit is created to the EQUIPM database with the following MML-command:

ZWTP:BCSU,0:PCU2_E,6,7,::<PCUDSP/PCUPAB>,4,128&&131,TSL,0&&31:PCUPPC,4,
132&&135,TSL,0&&31:<PCUDSP/PCUPAB>,4,136&&139,TSL,0&&31;
ZWTP:BCSU,1:PCU2_E,6,6,::<PCUDSP/PCUPAB>,8,432&&435,TSL,0&&31:PCUPPC,8,
436&&439,TSL,0&&31:<PCUDSP/PCUPAB>,8,440&&443,TSL,0&&31::;
ZWTP:BCSU,2:PCU2_E,6,6,::<PCUDSP/PCUPAB>,8,688&&691,TSL,0&&31:PCUPPC,8,
692&&695,TSL,0&&31:<PCUDSP/PCUPAB>,8,696&&699,TSL,0&&31::;
ZWTP:BCSU,3:PCU2_E,6,22,::<PCUDSP/PCUPAB>,8,944&&947,TSL,0&&31:PCUPPC,8
,948&&951,TSL,0&&31:<PCUDSP/PCUPAB>,8,952&&955,TSL,0&&31::;
ZWTP:BCSU,4:PCU2_E,6,22,::<PCUDSP/PCUPAB>,8,1184&&1187,TSL,0&&31:PCUPP
C,8,1188&&1191,TSL,0&&31:<PCUDSP/PCUPAB>,8,1192&&1195,TSL,0&&31;
ZWTP:BCSU,5:PCU2_E,6,32,::<PCUDSP/PCUPAB>,8,1440&&1443,TSL,0&&31:PCUPP
C,8,1444&&1447,TSL,0&&31:<PCUDSP/PCUPAB>,8,1448&&1451,TSL,0&&31;
ZWTP:BCSU,6:PCU2_E,6,32,::<PCUDSP/PCUPAB>,8,1696&&1699,TSL,0&&31:PCUPP
C,8,1700&&1703,TSL,0&&31:<PCUDSP/PCUPAB>,8,1704&&1707,TSL,0&&31;
After the PCU hardware has been created, connect the functional unit.

ZWUC:BCSU,<index>:PCU2_E,6;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

116 (149)

10

PEP INTERFACE CREATION.

Note: This creation is required only for PCU2_E cards with PCUPAB functionality implemented. PCU2_E cards
uses PEP Eth link to communicate with ETP cards. PCU2_D cards use PEP HDLC links to communicate with
ETP cards. So this creation is not required for this.
PCU2_E cards are used in following BSC variants.
1. Initial Flexi BSC
2. BSC 3i 1000/2000.
3. Upgraded Flexi BSC.
Macro asks user VLAN name, VLAN ID, IP address and subnet mask. Network Interfaces, IP addresses will be
created for all working BCSUs. Only Network interfaces will be created to spare BCSU. During switch over all IP
addresses will be shifted from working BCSUs to spare BCSUs network interface. Network interface will be
created in both IFETH0 and IFETH1.
Create PCU interface with following commands.

ZQRA:<unit type>,<unit index>:<plug-in unit type>,<plug-in unit index>:<PCU


interface name>::UP;
Example,

ZQRA:BCSU,2:PCU2E,10:IFETH0::UP;
Create the PEP interface with the following commands:

ZQRA:BCSU,<unit index>:PCU2E,<index>:<vlan name>,<vlan id>,<PCU interface


name>,::UP;
ZQRN:BCSU,<unit index>:PCU2E,<index>:<vlan name>,:"<IP adress>",<subnet
mask>,L,I::;
ZQRP:BCSU,<unit index>:PCU2E,<index>:<vlan name>:"<IP adress>":TAG,"PEP":;
Example:

ZQRA:BCSU,2:PCU2E,10:VLAN22,22,IFETH0,::UP;
ZQRN:BCSU,2:PCU2E,10:VLAN22,:"10.0.2.22",24,L,I::;
ZQRP:BCSU,2:PCU2E,10:VLAN22:"10.0.2.22":TAG,"PEP":;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

117 (149)

11

ET HW UPGRADE

11.1

BSC2i ET HW upgrade

Four optional ET5C cartridges can be installed to the bottom of the BSC extension rack. The maximum number of
external ET_PCM is then increased from 80 to 144 PCM(s).
New ET2 type ET plug-in units can be equipped into the same ET cartridge with previous variants. The existing
exchange terminals can be replaced with the new variants without the need to change any cabling connectors or
other mechanics. This backward compatibility is the reason why there are three different variants. The following
table shows the different ET-variants and relations with the existing units.

New plug-in unit


ET2E-T

C105507

ET2E-TC

C105508

ET2A-T

C105509

Existing plug-in unit


ET2E
ET2E-S
ET2E-C
ET2E-SC
ET2A

C08709
C08901
C08763
C08902
C08781

New ETSI variant (E1) ET2 type ET plug-in units: ET2E-T and ET2E-TC

New ANSI variant (T1) ET2 type ET plug-in unit: ET2A-T

Verify the ET2A-T, ET2E-T and ET2E-TC EPROM versions. When ET2A-T, ET2E-T or ET2E-TC plug-in units are
installed, select the EPROM according to the used application. DX200 TCSM2A/E - Transcoder requires a
different EPROM than the DX200 BSC.
BSC2i in the field are not necessarily equipped with the bottom shelf (CS6A-T C23697) of the BCEE-rack. This
shelf is included in the standard configuration in BSC2i. When upgrading the BSC, the bottom shelf is needed for
the extra ET5C cartridges. Install the shelf to the rack.
Install ET5C cartridges to the bottom of the BSC's extension rack. Connect the power, PCM, and alarm cables
according to the cable list. Set the ET plug-in unit strappings and install ET plug-in units to the ET5 cartridge. Set
ET5C cartridge strappings properly.
When installing the cabling, avoid sharp bends and make sure that the cables are not pulled too tight. The BSC
may be carrying traffic during the upgrade and, therefore, special care must be taken to avoid disconnecting other
cables or connectors.

11.2

ET5C-4 Cartridge

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

118 (149)

If the BSC2i is not equipped with an ET5C-4 cartridge (part of the large capacity BSC feature), instructions for
installation and creation of ET5C-4 ETs can be found from customer documentation Creating and managing
BSC hardware (NED).

ZWTC:ET5C,1B120-37:AL=1B120-01-4;
ZWTU:ET,104:1B120-37;
ZWTU:ET,105:1B120-37;
ZWTU:ET,106:1B120-37,
ZWTU:ET,107:1B120-37;
ZWTU:ET,108:1B120-37;
ZWTU:ET,109:1B120-37;
ZWTU:ET,110:1B120-37;
ZWTU:ET,111:1B120-37;
ZWTU:ET,112:1B120-37;
ZWTU:ET,113:1B120-37;
ZWTU:ET,114:1B120-37;
ZWTU:ET,115:1B120-37;
ZWTU:ET,116:1B120-37;
ZWTU:ET,117:1B120-37;
ZWTU:ET,118:1B120-37;
ZWTU:ET,119:1B120-37;
ZWTP:ET,104:<ET_TYPE>,0,0::ETT00,4,104,TSL,0:;
ZWTP:ET,105:<ET_TYPE>,0,0::ETT00,4,105,TSL,0:;
ZWTP:ET,106:<ET_TYPE>,0,1::ETT00,4,106,TSL,0:;
ZWTP:ET,107:<ET_TYPE>,0,1::ETT00,4,107,TSL,0:;
ZWTP:ET,108:<ET_TYPE>,0,2::ETT00,4,108,TSL,0:;
ZWTP:ET,109:<ET_TYPE>,0,2::ETT00,4,109,TSL,0:;
ZWTP:ET,110:<ET_TYPE>,0,3::ETT00,4,110,TSL,0:;
ZWTP:ET,111:<ET_TYPE>,0,3::ETT00,4,111,TSL,0:;
ZWTP:ET,112:<ET_TYPE>,0,4::ETT00,4,112,TSL,0:;
ZWTP:ET,113:<ET_TYPE>,0,4::ETT00,4,113,TSL,0:;
ZWTP:ET,114:<ET_TYPE>,0,5::ETT00,4,114,TSL,0:;
ZWTP:ET,115:<ET_TYPE>,0,5::ETT00,4,115,TSL,0:;
ZWTP:ET,116:<ET_TYPE>,0,6::ETT00,4,116,TSL,0:;
ZWTP:ET,117:<ET_TYPE>,0,6::ETT00,4,117,TSL,0:;
ZWTP:ET,118:<ET_TYPE>,0,7::ETT00,4,118,TSL,0:;
ZWTP:ET,119:<ET_TYPE>,0,7::ETT00,4,119,TSL,0:;
ET5C-4 Cable lists:
No.

Rack

FE

Connector

FE

Connector

Type

Use

2.13

BCEE

PSFP 2

148.03B P6

BCEE

ET5C 4

120.37B _PL1

POWER

2.14

BCEE

PSFP 3

148.27B P6

BCEE

ET5C 4

120.37B _PL2

2.69
2.65
2.66
2.67
2.68

BCEE
BCEE
BCEE
BCEE
BCEE

ET5C 4
ET5C 4
ET5C 4
ET5C 4
ET5C 4

120.37B
120.37B
120.37B
120.37B
120.37B

BCEE
BCBE
BCBE
BCBE
BCBE

CLAC
SW1C0
SW1C1
SW1C0
SW1C1

120.01B 03R5
120.01B 03S3
120.19B 03S3
120.01B 03S5
120.19B 03S5

CVKT01
2
CVKT00
8
CFB008
CEB013
CEB011
CEB013
CEB011

04S1
00V1
00V5
00V3
00V7

Rack

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

POWER
AL/CLK
PCM
PCM
PCM
PCM

119 (149)

11.3

BSC2i ET Configuration

Create hardware for ET5Cs:

ZWTC:ET5C,1B002-01:AL=01B120-01-5;
ZWTU:ET,120:1B002-01;
ZWTU:ET,121:1B002-01;
ZWTU:ET,122:1B002-01;
ZWTU:ET,123:1B002-01;
ZWTU:ET,124:1B002-01;
ZWTU:ET,125:1B002-01;
ZWTU:ET,126:1B002-01;
ZWTU:ET,127:1B002-01;
ZWTU:ET,128:1B002-01;
ZWTU:ET,129:1B002-01;
ZWTU:ET,130:1B002-01;
ZWTU:ET,131:1B002-01;
ZWTU:ET,132:1B002-01;
ZWTU:ET,133:1B002-01;
ZWTU:ET,134:1B002-01;
ZWTU:ET,135:1B002-01;
ZWTP:ET,120:<ET_TYPE>,0,0::ETT00,4,120,TSL,0;
ZWTP:ET,121:<ET_TYPE>,0,0::ETT00,4,121,TSL,0;
ZWTP:ET,122:<ET_TYPE>,0,1::ETT00,4,122,TSL,0;
ZWTP:ET,123:<ET_TYPE>,0,1::ETT00,4,123,TSL,0;
ZWTP:ET,124:<ET_TYPE>,0,2::ETT00,4,124,TSL,0;
ZWTP:ET,125:<ET_TYPE>,0,2::ETT00,4,125,TSL,0;
ZWTP:ET,126:<ET_TYPE>,0,3::ETT00,4,126,TSL,0;
ZWTP:ET,127:<ET_TYPE>,0,3::ETT00,4,127,TSL,0;
ZWTP:ET,128:<ET_TYPE>,0,4::ETT00,4,128,TSL,0;
ZWTP:ET,129:<ET_TYPE>,0,4::ETT00,4,129,TSL,0;
ZWTP:ET,130:<ET_TYPE>,0,5::ETT00,4,130,TSL,0;
ZWTP:ET,131:<ET_TYPE>,0,5::ETT00,4,131,TSL,0;
ZWTP:ET,132:<ET_TYPE>,0,6::ETT00,4,132,TSL,0;
ZWTP:ET,133:<ET_TYPE>,0,6::ETT00,4,133,TSL,0;
ZWTP:ET,134:<ET_TYPE>,0,7::ETT00,4,134,TSL,0;
ZWTP:ET,135:<ET_TYPE>,0,7::ETT00,4,135,TSL,0;
In a Next step ET5C-6 cassette is created. Check the hardware and PCM cabling of ET5C-6 cartridge.

ZWTC:ET5C,1B002-13:AL=01B120-01-6;
ZWTU:ET,136:1B002-13;
ZWTU:ET,137:1B002-13;
ZWTU:ET,138:1B002-13;
ZWTU:ET,139:1B002-13;
ZWTU:ET,140:1B002-13;
ZWTU:ET,141:1B002-13;
ZWTU:ET,142:1B002-13;
ZWTU:ET,143:1B002-13;
ZWTU:ET,144:1B002-13;
ZWTU:ET,145:1B002-13;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

120 (149)

ZWTU:ET,146:1B002-13;
ZWTU:ET,147:1B002-13;
ZWTU:ET,148:1B002-13;
ZWTU:ET,149:1B002-13;
ZWTU:ET,150:1B002-13;
ZWTU:ET,151:1B002-13;
ZWTP:ET,136:<ET_TYPE>,0,0::ETT00,4,136,TSL,0;
ZWTP:ET,137:<ET_TYPE>,0,0::ETT00,4,137,TSL,0;
ZWTP:ET,138:<ET_TYPE>,0,1::ETT00,4,138,TSL,0;
ZWTP:ET,139:<ET_TYPE>,0,1::ETT00,4,139,TSL,0;
ZWTP:ET,140:<ET_TYPE>,0,2::ETT00,4,140,TSL,0;
ZWTP:ET,141:<ET_TYPE>,0,2::ETT00,4,141,TSL,0;
ZWTP:ET,142:<ET_TYPE>,0,3::ETT00,4,142,TSL,0;
ZWTP:ET,143:<ET_TYPE>,0,3::ETT00,4,143,TSL,0;
ZWTP:ET,144:<ET_TYPE>,0,4::ETT00,4,144,TSL,0;
ZWTP:ET,145:<ET_TYPE>,0,4::ETT00,4,145,TSL,0;
ZWTP:ET,146:<ET_TYPE>,0,5::ETT00,4,146,TSL,0;
ZWTP:ET,147:<ET_TYPE>,0,5::ETT00,4,147,TSL,0;
ZWTP:ET,148:<ET_TYPE>,0,6::ETT00,4,148,TSL,0;
ZWTP:ET,149:<ET_TYPE>,0,6::ETT00,4,149,TSL,0;
ZWTP:ET,150:<ET_TYPE>,0,7::ETT00,4,150,TSL,0;
ZWTP:ET,151:<ET_TYPE>,0,7::ETT00,4,151,TSL,0;
In a Next step ET5C-7 cassette is created. Check the hardware and PCM cabling of ET5C-7 cartridge.

ZWTC:ET5C,1B002-25:AL=01B120-01-13;
ZWTU:ET,224:1B002-25;
ZWTU:ET,225:1B002-25;
ZWTU:ET,226:1B002-25;
ZWTU:ET,227:1B002-25;
ZWTU:ET,228:1B002-25;
ZWTU:ET,229:1B002-25;
ZWTU:ET,230:1B002-25;
ZWTU:ET,231:1B002-25;
ZWTU:ET,232:1B002-25;
ZWTU:ET,233:1B002-25;
ZWTU:ET,234:1B002-25;
ZWTU:ET,235:1B002-25;
ZWTU:ET,236:1B002-25;
ZWTU:ET,237:1B002-25;
ZWTU:ET,238:1B002-25;
ZWTU:ET,239:1B002-25;
ZWTP:ET,224:<ET_TYPE>,0,0::ETT00,4,224,TSL,0;
ZWTP:ET,225:<ET_TYPE>,0,0::ETT00,4,225,TSL,0;
ZWTP:ET,226:<ET_TYPE>,0,1::ETT00,4,226,TSL,0;
ZWTP:ET,227:<ET_TYPE>,0,1::ETT00,4,227,TSL,0;
ZWTP:ET,228:<ET_TYPE>,0,2::ETT00,4,228,TSL,0;
ZWTP:ET,229:<ET_TYPE>,0,2::ETT00,4,229,TSL,0;
ZWTP:ET,230:<ET_TYPE>,0,3::ETT00,4,230,TSL,0;
ZWTP:ET,231:<ET_TYPE>,0,3::ETT00,4,231,TSL,0;
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

121 (149)

ZWTP:ET,232:<ET_TYPE>,0,4::ETT00,4,232,TSL,0;
ZWTP:ET,233:<ET_TYPE>,0,4::ETT00,4,233,TSL,0;
ZWTP:ET,234:<ET_TYPE>,0,5::ETT00,4,234,TSL,0;
ZWTP:ET,235:<ET_TYPE>,0,5::ETT00,4,235,TSL,0;
ZWTP:ET,236:<ET_TYPE>,0,6::ETT00,4,236,TSL,0;
ZWTP:ET,237:<ET_TYPE>,0,6::ETT00,4,237,TSL,0;
ZWTP:ET,238:<ET_TYPE>,0,7::ETT00,4,238,TSL,0;
ZWTP:ET,239:<ET_TYPE>,0,7::ETT00,4,239,TSL,0;

In Next step ET5C-8 cassette is created. Check the hardware and PCM cabling of ET5C-8 cartridge.

ZWTC:ET5C,1B002-37:AL=01B120-01-14;
ZWTU:ET,240:1B002-37;
ZWTU:ET,241:1B002-37;
ZWTU:ET,242:1B002-37;
ZWTU:ET,243:1B002-37;
ZWTU:ET,244:1B002-37;
ZWTU:ET,245:1B002-37;
ZWTU:ET,246:1B002-37;
ZWTU:ET,247:1B002-37;
ZWTU:ET,248:1B002-37;
ZWTU:ET,249:1B002-37;
ZWTU:ET,250:1B002-37;
ZWTU:ET,251:1B002-37;
ZWTU:ET,252:1B002-37;
ZWTU:ET,253:1B002-37;
ZWTU:ET,254:1B002-37;
ZWTU:ET,255:1B002-37;
ZWTP:ET,240:<ET_TYPE>,0,0::ETT00,4,240,TSL,0;
ZWTP:ET,241:<ET_TYPE>,0,0::ETT00,4,241,TSL,0;
ZWTP:ET,242:<ET_TYPE>,0,1::ETT00,4,242,TSL,0;
ZWTP:ET,243:<ET_TYPE>,0,1::ETT00,4,243,TSL,0;
ZWTP:ET,244:<ET_TYPE>,0,2::ETT00,4,244,TSL,0;
ZWTP:ET,245:<ET_TYPE>,0,2::ETT00,4,245,TSL,0;
ZWTP:ET,246:<ET_TYPE>,0,3::ETT00,4,246,TSL,0;
ZWTP:ET,247:<ET_TYPE>,0,3::ETT00,4,247,TSL,0;
ZWTP:ET,248:<ET_TYPE>,0,4::ETT00,4,248,TSL,0;
ZWTP:ET,249:<ET_TYPE>,0,4::ETT00,4,249,TSL,0;
ZWTP:ET,250:<ET_TYPE>,0,5::ETT00,4,250,TSL,0;
ZWTP:ET,251:<ET_TYPE>,0,5::ETT00,4,251,TSL,0;
ZWTP:ET,252:<ET_TYPE>,0,6::ETT00,4,252,TSL,0;
ZWTP:ET,253:<ET_TYPE>,0,6::ETT00,4,253,TSL,0;
ZWTP:ET,254:<ET_TYPE>,0,7::ETT00,4,254,TSL,0;
ZWTP:ET,255:<ET_TYPE>,0,7::ETT00,4,255,TSL,0;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

122 (149)

11.4

BSC2i ET PCM-Cables

ET5C-5 and ET5C-6 Cable lists:


No.

Rack

FE

Connector

FE

Connector

Type

Use

2.70

BCEE

PSFP 2

148.03B P7

Rack
BCEE

ET5C 5

002.01B_PL1

POWER

2.71

BCEE

PSFP 3

148.27B P7

BCEE

ET5C 5

002.01B_PL2

2.72
2.73
2.74
2.75
2.76

BCBE
BCBE
BCBE
BCBE
BCEE

SW1C 0
SW1C 0
SW1C 1
SW1C 1
CLAC

120.01B 03S7
120.01B 04R1
120.19B 03S7
120.19B 04R1
120.01B 04R5

BCEE
BCEE
BCEE
BCEE
BCEE

ET5C 5
ET5C 5
ET5C 5
ET5C 5
ET5C 5

002.01B 00V1
002.01B 00V3
002.01B 00V5
002.01B 00V7
002.01B 04S1

CVKT02
2
CVKT02
5
CEB032
CEB033
CEB031
CEB032
CFB025

2.77

BCEE

PSFP 2

148.03B P8

BCEE

ET5C 6

002.13B_PL1

2.78

BCEE

PSFP 3

148.27B P8

BCEE

ET5C 6

002.13B_PL2

2.79
2.80
2.81
2.82
2.83

BCBE
BCBE
BCBE
BCBE
BCEE

SW1C 0
SW1C 0
SW1C 1
SW1C 1
CLAC

120.01B 04R3
120.01B 04R5
120.19B 04R3
120.19B 04R5
120.01B 03R7

BCEE
BCEE
BCEE
BCEE
BCEE

ET5C 6
ET5C 6
ET5C 6
ET5C 6
ET5C 6

002.13B 00V1
002.13B 00V3
002.13B 00V5
002.13B 00V7
002.13B 04S1

CVKT02
2
CVKT02
5
CEB033
CEB033
CEB031
CEB031
CFB024

POWER
PCM
PCM
PCM
PCM
AL/CLK 5)
POWER
POWER
PCM
PCM
PCM
PCM
AL/CLK
6)

ET5C-7 and ET5C-8 Cable lists:


No.

Rack

FE

Connector

FE

Connector

Type

Use

2.84

BCEE

PSFP 2

148.03B P9

Rack
BCEE

ET5C 7

002.25B_PL1

POWER

2.85

BCEE

PSFP 3

148.27B P9

BCEE

ET5C 7

002.25B_PL2

2.86
2.87
2.88
2.89
2.90

BCBE
BCBE
BCBE
BCBE
BCEE

SW1C 0
SW1C 0
SW1C 1
SW1C 1
CLAC

120.01B 05S1
120.01B 05S3
120.19B 05S1
120.19B 05S3
120.01B 04S5

BCEE
BCEE
BCEE
BCEE
BCEE

ET5C 7
ET5C 7
ET5C 7
ET5C 7
ET5C 7

002.25B 00V1
002.25B 00V3
002.25B 00V5
002.25B 00V7
002.25B 04S1

CVKT02
5
CVKT02
2
CEB031
CEB031
CEB029
CEB029
CFB023

2.91

BCEE

PSFP 2

148.03B P10

BCEE

ET5C 8

002.37B_PL1

2.92

BCEE

PSFP 3

148.27B P10

BCEE

ET5C 8

002.37B_PL2

2.93
2.94
2.95
2.96
2.97

BCBE
BCBE
BCBE
BCBE
BCEE

SW1C 0
SW1C 0
SW1C 1
SW1C 1
CLAC

120.01B 05S5
120.01B 05S7
120.19B 05S5
120.19B 05S7
120.01B 03S7

BCEE
BCEE
BCEE
BCEE
BCEE

ET5C 8
ET5C 8
ET5C 8
ET5C 8
ET5C 8

002.37B 00V1
002.37B 00V3
002.37B 00V5
002.37B 00V7
002.37B 04S1

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

CVKT02
5
CVKT02
2
CEB030
CEB030
CEB028
CEB028
CFB022

POWER
PCM
PCM
PCM
PCM
AL/CLK13)
POWER
POWER
PCM
PCM
PCM
PCM
AL/CLK
14)

123 (149)

12

ACTIONS AFTER UPGRADE & POST CONDITIONS

12.1

Implementation of the new optional feature

Once the HW has been upgraded to the required level, the installation continues with the optional feature
upgrade. The GPRS/EDGE features are delivered separately via licences and installed in chapter 8.4.
More information of feature implementation and handling licences can be found from NED documentations.

12.2

PCU2 Scheduling weight parameters

There are different radio network parameters for priority based scheduling in PCU1 and PCU2 units. In the PCU2
new bucket round-robin (BRR) scheduling algorithm replaces priority based scheduling used with PCU1.
To meet same functionality the Scheduling Step Size parameters should be converted to Scheduling Weight
parameters according table below.

Scheduling Step Size


PCU1
1
2
3
4
5
6
7
8
9
10
11
12

Scheduling Weight
PCU2
60
30
20
15
12
10
9
8
7
6
5
5

46:87 POLLING_INTERVAL_DG should be changed to 4 to meet RTT requirements with PCU2_D and PCU2_U
packet control units.
Check the QOS parameters with command:
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

124 (149)

ZEEO:QOS;
Modify the scheduling weight parameters if needed:

ZEEV::BGSW1=<DHP>;
ZEEV::BGSW2=<DNP>;
ZEEV::BGSW3=<DLP>;

12.3

Check and update PCU boot software

The PCU boot software versions are checked and updated in this step.

12.3.1

Chorus PCU boot SW versions

The versions of the Chorus PCU boot software can be checked with commands:

ZWTI:P:BCSU,<unit_index>
ZDDS:OMU;
ZRS:3<bcsu_index(hex)>,x0BF
where x=PCU index(hex)+1
rgndump -p -o ffe00210 -l 10
exit
ZE

First check PCUs index. The output can be, for example, BCSU,0:

ZWTI:P:BCSU,0
LOADING PROGRAM VERSION 19.33-0
/* IDENTIFY PLUG-IN UNIT TYPE:
PCU_S
4
PCU_T
3
CP6LX
0
AS7_X
2
AS7_X
1
AS7_X
0
MBIF_UA 1
MBIF_UA 0
PSC3
0
Press CTRL+Y to interrupt the command.
Access to OMU Service Terminal with command:

ZDDS:OMU;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

125 (149)

Access to PCU Service Terminal with command, e.g. BCSU,0 and PCU_S:
00-MAN>ZRS:30,50BF

LINK TO 0030 ESTABLISHED


WELCOME TO DX 200 SERVICE TERMINAL SESSION
0030-$ rgndump -p -o ffe00210 -l 10
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
ffe00210: 50 43 53 30 31 2e 50 41 43 20 31 2e 31 34 2d 30 PCS01.PAC 1.14-0
0030-$ exit

The PCU boot version is shown on the right column of the printout.
If the PCU boot version is not correct, upgrade cannot be done and PCU/PCU_S boot SW MUST be updated
before the upgrade. See Appendix8, Updating the boot packages of PCU pre-processor PIUs.

12.3.2

PCU2 boot SW versions

The versions of the PCU2 boot SWs can be checked with commands:

ZWTI:P:BCSU,<unit_index>;
ZDDS:OMU;
ZRS:3<bcsu_index(hex)>,x0BE
where x=PCU index(hex)+1
ssv
exit
ZE
:
First check PCUs index. The output can be, for example, for BCSU,0:

WTI:P:BCSU,9
/* IDENTIFY PLUG-IN UNIT TYPE:
PSC6_B 0
CP816_A 0
PCU2_D 12
PCU2_D 11
PCU2_D 10
PCU2_D 9
PCU2_D 8
PCU2_D 7
PCU_B
4
PCU_B
3
PCU_B
6
PCU_B
5
AS7_C 14
AS7_C 13

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

126 (149)

Press CTRL+Y to interrupt the command.


Access to OMU Service Terminal with command:

ZDDS:OMU;

Access to PCU Service Terminal with command, e.g. BCSU,9 and PCU2_D index 12:

00-MAN>ZRS:39,D0BE
LINK TO 0039 ESTABLISHED
WELCOME TO IMS GW SERVICE TERMINAL DIALOGUE, BCSU-39, PCU-12,
2008-2-20 16:42:47
Disclaimer :- IMS GW SERVICE TERMINAL IS A SPECIALIST TOOL.
UNAUTHORIZED USAGE MAY CAUSE DAMAGE.
BCSU/39/PCU/12/OSE>ssv
---------------------------------------------------------------> Command ssv executed on [20/2/2008 16:43:29:503156] <--------------------------------------------------------------PQ2 Boot Image Software Version:
6.33-0
PQ2 RAM Image Software Version:
8.63-0
DSP RAM Image Software Version:
8.63-0
DSP Diagnostics Image Software Version: 8.63-0
DSP Boot Image Software Version:
8.63-0
BCSU/39/PCU/12/OSE>
If the PCU boot version is not correct, upgrade cannot be done and PCU2 boot SW MUST be updated before the
upgrade. See Appendix9, Updating the boot packages of PCU2 pre-processor PIUs.

12.4

Cartridge Marking Labels

Each BSC cartridge is provided with a marking label, which indicates e.g. the cartridge name, the PCM interface
number, functional unit number or plug-in unit names, depending on the cartridge and its function. All marking
labels, except for the ET1TC and ET5C cartridge labels are filled in at the factory.
Due to the multiple plug-in unit configuration and allocation options offered, the labels for the ET1TC and ET5C
cartridges have been left partially blank. The only details shown are the name of the cartridge and the positions of
the plug-in units. The boxes left blank are to be filled in at the site, in accordance with the equipment configuration
installed into each cartridge.
Attach the new cartridge marking labels to the BSC racks. The labels are delivered as a set in a separate bag.

12.5

BSC configuration printout (post-check)

The information about the BSC configurations and conditions are collected.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

127 (149)

The checking can be made by using the macro (S16UPGMAIN.HIT) or manually following the instructions from
BSC configuration printout-document delivered in Release Binder.
For macro execution, choose the BSC configuration printout (pre) step in BSC/PCU HW implementation for PS
traffic procedure.

12.6

Fallback copying of the current package

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

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

128 (149)

13

APPENDIX

13.1

Appendix1: SW64B Jumper settings

SW64B C 08790, jumpers of the plug-in unit:

Jumpers of plug-in unit SW64B Versions 1 - 4

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

129 (149)

Jumpers of plug-in unit SW64B Version 5


Standard settings:

Jumper
block
W3
W4
W5

13.2

Jumper
1-2
3-4
1-2
3-4
1-2
3-4

Appendix2: PCU, PCU_S and PCU_T Jumper settings

PCU, PCU_S and PCU_T plug-in unit Jumpers settings:

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

130 (149)

Standard Settings:

Jumper
block

Jumper

W5

W6

W7 *

13 - 14

* Boundary scan test is controlled by the jumper block W7. Jumper in pins 1314.
Jumper W2 Interchangeabilty code setting:
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

131 (149)

Jumper
W2: 1-8
2-7
3-6
4-5

Interchangeabilty Code
A
X
X
X
X

B
X
X
X

C
X
X
X

D E F G H
- X - X - X X - X - - - X X X X X
X = Jumper on

J
X
X
X
-

K
X
X
-

L
X
X
-

M
X
-

N
X
X
-

P
X
-

R
X
-

Jumper W1, Selection of the base address 500 000 H, Track 9:

Jumper
block

Jum
per

W1

6-7
5-8
3-10
1-12

W1

W1

6-7
5-8
3-10
2-11
1-12
6-7
5-8
4-9
1-12

Selection
Criteria

Base
Address

BCSU, Track 09
(BSCE, BSCi,
BSC2A/E,BSC2
i)

500 000H

BCSU, Track 08
(2 nd PCU,
BSC2i)

400 000H

BCSU, Track 07
(2 nd PCU,
BSC2A/E)

300 000H

Example, Track 9 / Base address 500 000H:

Track 9

13.3

Appendix3: PCU2_U Jumper settings

PCU2_U plug-in unit Jumpers settings:

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

132 (149)

Jumper W2, Selecting place of the PCM, MII_MUX mode and type of the PCM (4M /8M):

Jumper

Setting

W2 1 12
W2 2 11
W2 3 10
W2 4 - 9
W2 5 - 8
W2 6 - 7

Meaning

X
-

Not in use
4Mbit/s PCM
Not in use

X = Jumper
on

Jumper W4, Selection of the base address in the DMC bus:

Jumper setting W4

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

Base

Selection

133 (149)

1-12

2-11

3-10

4-9

5-8

6-7

Address
300 000 H

Criteria
BCSU, Track 07
2 nd PCU, BSC2A/E
BCSU, Track 08
2 nd PCU, BSC2i
BCSU, Track 09
1 st PCU,
BSC/BSC2
P

400 000 H

500 000 H

X = Jumper is on

Jumper W5, Interchangeability code settings:

ICC
code

Jumper setting W5
W5: 4
-5

A
X
B
X
C
X
D
X
E
X
F
X
G
X
H
X
J
K
L
M
N
P
R
X = Jumper on

13.4

W5: 3
-6

W5: 2
-7

W5: 1
-8

X
X
X
X
X
X
X
X
-

X
X
X
X
X
X
X
X
-

X
X
X
X
X
X
X
X

Appendix4: PCU_B Jumper settings

PCU_B plug-in unit Jumpers settings:

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

134 (149)

Jumper groups, LED indicators and the DIP-switch group of the PCU_B
Note!
In the figure above, the circuit board of the PCU2_D is presented primary side up. The DIP-switch group
used for selecting interchangeability code (W201) is located on the secondary side of the circuit board of
the PCU2_D, and the location of the DIP-switch is indicated with a dash line. The detailed presentation of
the DIP-switch shows the group as it is seen on the secondary side.
Standard settings (W4, W5):
Jumper groups W4 and W5 is used for testing. In normal operation, the jumper
groups have no settings (see the table below).

Jumper

Setting

Meaning

W4: ALL
W5: ALL

OFF
OFF

For testing purposes


For testing purposes

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

135 (149)

Interchangeability code settings (W203):


A 4-switch DIP-switch group (W203) is used for setting the interchangeability
code of the plug-in unit, when required. (see the table below).

13.5

ICC
code

Jumper setting W203


Switch
1 (MSB)

Switch
2

Switch
3

Switch
4 (LSB)

A
B
C
D
E
F
G
H
J
K
L
M
N
P
R

OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
ON
ON
ON
ON
ON
ON
ON

OFF
OFF
OFF
OFF
ON
ON
ON
ON
OFF
OFF
OFF
OFF
ON
ON
ON

OFF
OFF
ON
ON
OFF
OFF
ON
ON
OFF
OFF
ON
ON
OFF
OFF
ON

OFF
ON
OFF
ON
OFF
ON
OFF
ON
OFF
ON
OFF
ON
OFF
ON
OFF

Appendix5: PCU2_D Jumper settings

PCU2_D plug-in unit Jumpers settings:

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

136 (149)

Note!
In the figure above, the circuit board of the PCU2_D is presented primary side up. The DIP-switch group
used for selecting interchangeability code (W201) is located on the secondary side of the circuit board of
the PCU2_D, and the location of the DIP-switch is indicated with a dash line. The detailed presentation of
the DIP-switch shows the group as it is seen on the secondary side.
There are two switches for jumper settings on the primary side of the
PCU2-D: The 6-pin W5 is used for indicating the place of the PCM,
selecting MII-MUX mode, and for selecting 4M or 8M PCM. The 6-pin W6
is used for selecting of the emulator, disabling the watchdog , and for
selecting the debugging mode. There are also two switches that the user
does not have to set, namely: W1 for testing side selection and W2 for
JTAG chain selection. In addition, there are two emulators, W3 (PQII_1)
and W4 (PQII_0).
Jumper W5, Selecting place of the PCM Block, MII_MUX mode and type of the PCM (4M /8M):

Selection
Criteria
The PCM in place
Setting MII-MUX
mode
4M/8M

Setting
1-6
2-5
3-4

Explanation
0 = PCM5; PCM from cartridge cross connection
1 = PCM3; PCM straight from Group Switch
0 = MII-MUX active
1 = MII-MUX bypass
0 = 4M

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

137 (149)

1 = 8M
0 = the jumper is off; 1 = the jumper is on
Jumper W6, Selection of emulator, watchdog and debugger mode:

Jumper
Selection of
emulator

Setting
1-6

Watchdog disabled

2-5

Debugger mode

3-4

Meaning
0 = Emulator not in place
1 = Emulator in place
0 = Watchdog not disabled
1 = Watchdog disabled
0 = Debugger mode not
selected
1 = Debugger mode selected

0 = the jumper is off; 1 = the jumper is on

Interchangeability code settings (W201):


A 4-switch DIP-switch group (W201) is used for setting the interchangeability
code of the plug-in unit, when required. (see the table below).

ICC
code
A
B
C
D
E
F
G
H
J
K
L
M
N
P
R

Jumper setting W201


Switch
1 (MSB)

Switch
2

Switch
3

Switch
4 (LSB)

OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
ON
ON
ON
ON
ON
ON
ON

OFF
OFF
OFF
OFF
ON
ON
ON
ON
OFF
OFF
OFF
OFF
ON
ON
ON

OFF
OFF
ON
ON
OFF
OFF
ON
ON
OFF
OFF
ON
ON
OFF
OFF
ON

OFF
ON
OFF
ON
OFF
ON
OFF
ON
OFF
ON
OFF
ON
OFF
ON
OFF

PCU2-D jumper settings in BSC3i


The following information is specifically for BSC3i network elements.
W5
The table below presents the use of W5 for PCU2-D in BSC3i.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

138 (149)

0 = the jumper is off; 1= the jumper is on


W6
The table below presents the use of W6 for PCU2-D in BSC3i.

13.6

Appendix6: PCU2_E Jumper settings


PCU2_E plug-in unit Jumpers settings:

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

139 (149)

Standard settings are presented in the table below, the jumpers must be set as
shown during normal operation.
There are no alternative settings available on the plug-in unit, except for jumper
W1.
DIP switch SW1 is used for setting the interchangeability code of the plug-in unit
when required, see the table below.

PCM interface configuration pinheader (W1):


In BSC3i 660 GSWB model:
Strapping
group

Strapping

Setting in
BSC3i 660
GSWB

Function

W1

1-4

OFF

PCM interface 4Mbit/s

W1

2-3

ON

Shared PCM (J5 row 6/7) used, interfaces 4Mbit/s

In BSC3i 660 GSW1KB model


Strapping
group

Strapping

Function

1-4

Setting in
BSC3i 660
GSW1KB
ON

W1
W1

2-3

OFF

4M/8M shared PCM mode not in use

PCM interface 4Mbit/s

In BSC3i 1000/2000 model:


Strapping
group

Strapping

Setting in
BSC3i
1000/2000

Function

W1

1-4

ON

PCM interface 4Mbit/s ( in tracks 6-7)

OFF

PCM interface 8Mbit/s ( in tracks 3-5)

OFF

4M/8M shared PCM mode not in use

W1

2-3

In Upgraded Flexi BSC:


Strapping
group

Strapping

Setting in
Upgraded Flexi
BSC (M98 HW)

Function

W1

1-4

ON

PCM interface 4Mbit/s. Selected in slots 6-7 in BCSU-0--3

OFF

PCM interface 8Mbit/s. Selected in slots 3-5 in BCSU-0--3 and in slots 03-07
in BCSU's 4--6

OFF

4M/8M shared PCM mode not in use

W1

2-3

In New delivered Flexi BSC:


Strapping
group

Strapping

Setting in New
Flexi BSC

Function

W1

1-4

ON

PCM interface 4Mbit/s . Selected for PCU2-E's in slots 03-07 in BCSU-0

OFF

PCM interface 8Mbit/s. Selected for PCU2-E's in slots 03-07 in BCSU-1--6

OFF

4M/8M shared PCM mode not in use

W1

2-3

RS-232 port speed and IPETC support(W12):

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

140 (149)

Strapping
group

Strapping

Setting in Flexi
BSC

Function

W12

1-2

OFF

RS-232 port speed 9600 bps (Default)

W12

3-4

OFF

IPETC cartridge usage disabled (Default)

MPC 8567 control pinheader (W13):


Strapping
group

Strapping

Default setting
in Flexi BSC

Function

W13

1-2

OFF

MPC 8567 emulator disabled. (Default)

W13

3-4

OFF

MPC 8567 watchdog enabled. (Default)

The interchangeability is set with a dip-switch packet S1:


Code

S1 1: 1-8

S1 1: 2-7

S1 1: 3-6

(MSB)

S1 1: 4-5
(LSB)

OFF

OFF

OFF

OFF

OFF

OFF

OFF

ON

OFF

OFF

ON

OFF

OFF

OFF

ON

ON

OFF

ON

OFF

OFF

OFF

ON

OFF

ON

OFF

ON

ON

OFF

OFF

ON

ON

ON

ON

OFF

OFF

OFF

ON

OFF

OFF

ON

ON

OFF

ON

OFF

ON

OFF

ON

ON

ON

ON

OFF

OFF

ON

ON

OFF

ON

ON

ON

ON

OFF

Note! The use of letters I, O and Q as interchangeability codes is not allowed.

13.7

Appendix7: EURO Connector is connected to PCU card

This picture shows how the EURO Connectors are connected to PCU, PCU_S and PCU_T card. The 1/8
EURO Connectors are connected to GSWB.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

141 (149)

13.8

Appendix8: Updating the boot packages of PCU, PCU_S, PCU_T, PCU_B


pre-processor PIU(s)

Begin the updating by connecting to the OMU. You can establish the connection to the OMU either through a
direct service terminal session or a remote session through another computer unit in the BSC. It is also possible
to do the update through the NMS/OSS provided that you proceed with extreme caution.
Note!
It is, highly recommended that you program all FLASH memory circuits locally.
The update includes following steps:
1. Change the working state of the computer unit BCSU into TE-EX.
2.

Establish a service terminal session through the OMU to the PCU plug-in unit to
be updated.

3.

Load files needed to the PCU plug-in unit.

4.

Reprogram the PCU's FLASH.

5.

Change the working state back into SP-EX.

6.

Repeat the steps for all BCSUs

Relationship for PCU type and SW module:


PCU type
PCU
PCU_S
PCU_T
PCU_B

SW module name
PBOPCU02.IMG
PBOPCS01.IMG
PBOPCT01.IMG
PBOPCB01.IMG

Before starting the updating procedure, check that:


The PBOPCxxx.IMG and CSXFLP1X.IMG files are in the LFILES directory on the OMU disk and the
RCBUGGGX service terminal extension program is in the current BLCODE directory.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

142 (149)

Activate the RCBUGGGX service terminal extension:

ZDDE:OMU:"ZLEL:U:0,W0-BLCODE/RCBUGGGX.IMG";
Begin the updating of the PCU pre-processor computer units by listing all available BCSU units and checking their
working states. Start the updating from the current spare unit (in SP-EX working state).

ZUSI:BCSU;
Change the working state of the BCSU into TE-EX:

ZUSC:BCSU,<index>:TE;
Establish a remote service terminal session from the OMU to the computer unit to be updated. First check PCU
index:

ZWTI:P:BCSU,<unit_index>
The output can be, for example, for BCSU,0:

ZWTI:P:BCSU,0
LOADING PROGRAM VERSION 19.33-0
/* IDENTIFY PLUG-IN UNIT TYPE:
PCU_S
4
PCU_T
3
CP6LX
0
AS7_X
2
AS7_X
1
AS7_X
0
MBIF_UA 1
MBIF_UA 0
PSC3
0
Press CTRL+Y to interrupt the command.
Access to OMU Service Terminal with command:

ZDDS:OMU;
Access to PCU Service Terminal with command, e.g. BCSU,0 and PCU:

ZRS:3<BCSU_index(hex)>,x0BF

x = PCU index+1

00-MAN> ZRS:30,50BF
Load the PBOPCU02.IMG or PBOPCS01.IMG or PBOPCT01.IMG or PBOPCB01.IMG to the PCU plug-in unit's
RAM disk and load also the FLASH memory programming software flprog. The needed commands are:
For PCU

00-$ dxfload -n PBOPCU02 -o -d -u 0 /pbopcu02.img


00-$ dxfload -n CSXFLP1X -o -d -u 0 /bin/flprog.gz
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

143 (149)

For PCU_S

00-$ dxfload -n PBOPCS01 -o -d -u 0 /pbopcs01.img


00-$ dxfload -n CSXFLP1X -o -d -u 0 /bin/flprog.gz
For PCU_T

00-$ dxfload -n PBOPCU02 -o -d -u 0 /pbopct01.img


00-$ dxfload -n CSXFLP1X -o -d -u 0 /bin/flprog.gz
For PCU_B

00-$ dxfload -n PBOPCS01 -o -d -u 0 /pbopcb01.img


00-$ dxfload -n CSXFLP1X -o -d -u 0 /bin/flprog.gz
Note!
If in this phase you get error loading failed 0x369B (ram disk full), there is not enough space
in ram memory.
Example:

0036-$ dxfload -n PBOPCU02 -o -d -u 0 /pbopcu02.img


Loading file 00000000 PBOPCU02 from 0000 to /pbopcu02.img
Loading failed: 0x369B
Check the bin directory:

00-$ ls /bin
Example:

0030-$ ls /bin
LGLVST.gz
ticdrv.gz
rcgsta.gz
naomic.gz
dmxrecv.gz
bsysld.gz
yshell.gz
supervise.gz
svator.gz

clog.gz
abator.gz
ticker.gz
renfst.gz
olog.gz
dmxsend.gz
ch1sup.gz
ch4dsp.gz

gbhtor.gz
diecho.gz
actorinfo.gz
tlnetd.gz
reyska.gz
p2dspm.gz
dxfload.gz
frhtor.gz

qalarm.gz
mcctdm.gz
dmxmon.gz
actorstart.gz
vixser.gz
spqcho.gz
pq2dsp.gz
puzage.gz

The following extensions can safely be deleted, if necessary:

LGLVST.gz
abator.gz
frhtor.gz
dmxmon.gz
actorinfo.gz
tlnetd.gz
actorstart.gz
clog.gz
olog.gz
renfst.gz
DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)
Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

144 (149)

gbhtor.gz
Delete all these extensions at the same time:

00-$ cd /bin
00-$ rm actorinfo.gz actorstart.gz LGLVST.gz clog.gz dmxmon.gz olog
renfst.gz tlnetd.gz gbhtor.gz frhtor.gz abator.gz
After this you can try the loading again with dxfload command.
Program the new PBOPCU02.IMG or PBOPCS01.IMG IMG or PBOPCT01.IMG or PBOPCB01.IMG
to the FLASH memory of the PCU plug-in unit:
For PCU

00-$ flprog /pbopcu02.img


For PCU_S

00-$ flprog /pbopcs01.img


For PCU_T

00-$ flprog /pbopct01.img


For PCU_B

00-$ flprog /pbopcb01.img


Ending the updating process of the computer unit
When the FLASH memory of the PCU plug-in unit has been successfully programmed, change the
computer unit back into the original SP-EX working state and terminate the remote terminal session.
Terminate the remote service terminal session by giving the following command:

00-$ exit
Change the updated computer unit back into the SP-EX working state:

ZUSC:<BCSU>,<index>:SP:C=DSK;
After you have programmed the first PCU plug-in unit, check that the computer unit restarts properly
into the SP-EX working state.
Caution:
If there are problems with the restarting, contact the Nokia Customer Service. Do not continue
updating the other pre-processor units.
Repeat the procedure beginning from the section Programming new boot loader to PCU FLASH
memory to update the rest of the pre-processor units in the BSC.
When continuing the updating, keep a record of the computer units you have updated.
Start from the spare unit. When the updating is complete, perform switchover and update the
computer unit which is now spare state.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

145 (149)

Program the FLASH memory of the plug-in unit only when the computer unit is in TE-EX working
state.

13.9

Appendix9: Updating the boot packages of PCU2 pre-processor PIU(s)

Begin the updating by connecting to the OMU. You can establish the connection to the OMU either
through a direct service terminal session or a remote session through another computer unit in the
BSC. It is also possible to do the update through the NMS/OSS provided that you proceed with
extreme caution.
Note!

It is, highly recommended that you program all FLASH memory


circuits locally.
The update includes following steps:
1.

Change the working state of the computer unit BCSU into TE-EX.

2.

Establish a service terminal session through the OMU to the PCU plug-in unit to
be updated.

3.

Reprogram the PCU's FLASH.

4.

Change the working state back into SP-EX.

5.

Repeat the steps for all BCSUs

Relationship for PCU type and SW module:


PCU type
PCU2_D
PCU2_U
PCU2-E

SW module name
IGWBTPQD.IMG
IGWBTPQU.IMG
IGWBTPQE.IMG

Before starting the updating procedure, check that:


The IGWBTPQx.IMG files are in the LFILES directory on the OMU disk and the RCBUGGGX
service terminal extension program is in the current BLCODE directory.
Activate the RCBUGGGX service terminal extension:

ZDDE:OMU:"ZLEL:U:0,W0-BLCODE/RCBUGGGX.IMG";
Begin the updating of the PCU pre-processor computer units by listing all available BCSU units and
checking their working states. Start the updating from the current spare unit (in SP-EX working
state).

ZUSI:BCSU;
Change the working state of the BCSU into TE-EX:

ZUSC:BCSU,<index>:TE;

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

146 (149)

Establish a remote service terminal session from the OMU to the computer unit to be updated. First
check PCU index:

ZWTI:P:BCSU,<unit_index>
The output can be, for example, for BCSU,0:

ZWTI:P:BCSU,0
LOADING PROGRAM VERSION 19.33-0
/* IDENTIFY PLUG-IN UNIT TYPE:
PCU_S
PCU_T
CP6LX
AS7_X
AS7_X
AS7_X
MBIF_UA
MBIF_UA
PSC3

4
3
0
2
1
0
1
0
0

Press CTRL+Y to interrupt the command.


Access to OMU Service Terminal with command:

ZDDS:OMU;

Access to PCU Service Terminal with command, e.g. BCSU,0 and PCU:

ZRS:3<BCSU_index(hex)>,x0BF

x = PCU index(hex)+1

00-MAN> ZRS:30,50BF
Load the IMWBTPQx .IMG to the FLASH memory with command:

BCSU/0/PCU/0/OSE>ubs
Example:

BCSU/0/PCU/0/OSE>ubs
---------------------------------------------------------------> Command ubs executed on [1/1/1970 0:7:53:180001] <--------------------------------------------------------------SDL ubs: Current Boot Image Software Version :
"IGWBTPQC.elf
2.2P10_DMX"
SDL ubs: Downloaded Boot Image Software Version : "IGWBTPQC.elf
2.2P12_DMX"
Do you wish to upgrade boot software....(Y/N):y

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

147 (149)

SDL ubs: Upgrading Boot Software ...


SDL ubs: Writing data size 0x53f00 to address 0xffe10000
SDL ubs: Writing data size 0x1784 to address 0xfff00000
SDL ubs: Writing data size 0x260 to address 0xffe63f00
SDL ubs: Boot Software has been upgraded.
SDL ubs: New Boot file would be applied when PCU is rebooted.
---------------------------------------------------------Ending the updating process of the computer unit
When the FLASH memory of the PCU plug-in unit has been successfully programmed, change the computer unit
back into the original SP-EX working state and terminate the remote terminal session.
Terminate the remote service terminal session by giving the following command:

BCSU/0/PCU/0/OSE>exit
Change the updated computer unit back into the SP-EX working state:

ZUSC:<BCSU>,<index>:SP:C=DSK;
After you have programmed the first PCU plug-in unit, check that the computer unit restarts properly into the SPEX working state.
Caution:
If there are problems with the restarting, contact the Nokia Customer Service. Do not continue updating the other
pre-processor units.
Repeat the procedure to the rest of the pre-processor units in the BSC.
When continuing the updating, keep a record of the computer units you have updated.
Start from the spare unit. When the updating is complete, perform switchover and update the computer unit,
which is now spare state.
Program the FLASH memory of the plug-in unit only when the computer unit is in TE-EX working state.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

148 (149)

Disclaimer
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 Solutions and 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 Solutions and
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 Solutions
and 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 Solutions and Networks and the customer.
However, Nokia Solutions and 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 Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks,
explain issues which may not be covered by the document.
Nokia Solutions and Networks will correct errors in this documentation as soon as possible. IN
NO EVENT WILL NOKIA SOLUTIONS AND 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.
NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia
Corporation. Other product names mentioned in this document may be trademarks of their
respective owners, and they are mentioned for identification purposes only.
Copyright 2013 Nokia Solutions and Networks. All rights reserved.

DN09114009 BSC/PCU HW Implementation for PS traffic (GPRS/EDGE)


Copyright 2013 Nokia Solutions and Networks. All rights reserved.
CONFIDENTIAL
APPROVED 1.9

149 (149)