31143242 Swapping Old Gen Bsc and Tcsms With a New Gen Nokia

Swapping Old Generation NokiaBSCs and TCSMs with a NewGeneration BSC3i and TCSM3i

DN0618236Issue 2-0 en

# Nokia Siemens Networks 1 (33)

BSC3189-3.0Nokia BSC3i, Rel. S13, Site Documentation, v.3

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

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

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

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

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

Copyright © Nokia Siemens Networks 2009. All rights reserved.

2 (33) # Nokia Siemens Networks DN0618236Issue 2-0 en

Swapping Old Generation Nokia BSCs and TCSMs with a NewGeneration BSC3i and TCSM3i

Contents

Contents 3

List of tables 4

List of figures 5

Summary of changes 7

1 Introduction 9

2 Overview of swapping 112.1 Identical swap 112.2 Traffic migration 11

3 Traffic migration method 133.1 Network planning requirements to the BSC3i 133.2 Site engineering plan of the new BSC3i 153.3 Installation and commissioning of BSC3i 153.4 Application software 153.5 Export data from the old BSC 153.6 Datafill preparation/adjustment for BSC3i 203.7 Integration of the BSC3i 213.8 Pre-testing of the BSC3i 213.9 Radio network rehome from the old BSC to the BSC3i 223.10 Verification and recovery 223.11 Decommissioning and removal of the old BSC 22

4 Product dimensions 23

5 Changeout of the TCSM 33



Contents

List of tables

Table 1. The Nokia GSM/EDGE BSC product family 9

Table 2. BSC3i 660 capacity steps 24

Table 3. Overview of the different BSC configuration limitations 26

Table 4. Overview of the different BSC configuration limitations, High CapacityBSC 27



List of figures

Figure 1. BSC3i 1000/2000 capacity steps 25

Figure 2. ET4C-B cartridges and ET2A/ET2E-S/SC indexes in BSC3i 30

Figure 3. ET5C cartridges and ET2E/A indexes in BSC2 31



List of figures

Summary of changes

Changes between document issues are cumulative. Therefore, the latestdocument issue contains all changes made to previous issues.

Changes between issues 1-0 and 2-0

Misprints corrected and other minor editorial changes made in all sections.



Summary of changes

1 Introduction

This document describes the overall process of swapping an M92mechanic-based BSC installed in a rack with an M98 mechanic-basedBSC installed in a cabinet. The M92 mechanic-based BSCs are thefollowing:

. BSCE

. BSCi

. BSC2

. BSC2i

The M98 mechanic-based BSC is BSC3i.

Hereafter, an M92 mechanic-based BSC is referred to as BSC/BSC2, andan M98 mechanic-based BSC is referred to as BSC3i. The terms BSC,BSCi, BSC2i, and BSC3i are explained in the table below.

Table 1. The Nokia GSM/EDGE BSC product family

General name Product name Explanation

BSC - Base Station Controller, a generalterm for all Nokia GSM/EDGE BSCversions

BSCi BSCi High Capacity (upgraded andimproved) version of the firstgeneration Nokia DX 200 BSC

BSC2i BSC2i, ANSI version American National StandardsInstitute (ANSI) High Capacityversion of the Nokia DX 200 BSC2

BSC2i, ETSI version European TelecommunicationsStandards Institute (ETSI) HighCapacity version of the Nokia DX200 BSC2



Introduction

Table 1. The Nokia GSM/EDGE BSC product family (cont.)

General name Product name Explanation

BSC3i BSC3i, ANSI version American National StandardsInstitute (ANSI) High Capacityversion of the Nokia GSM/EDGEBSC3i

BSC3i, ETSI version European TelecommunicationsStandards Institute (ETSI) HighCapacity version of the Nokia GSM/EDGE BSC3i

There are two main BSC3i product configurations: BSC3i 660 and BSC3i1000/2000. The product configuration is described specifically if the topicarea is configuration-specific. The second generation Packet Control Units(PCU2s) are, however, not included, as PCU-related swap procedures aredescribed in GPRS/EDGE Hardware Implementation.

Additionally, this document describes the overall process of swapping anolder mechanic-based Transcoder Submultiplexer (TCSM) with an M98mechanic-based TCSM3i. Hereafter, an older mechanic-based TCSM isreferred to as TCSM/TCSM2 and an M98 mechanic-based BSC is referredto as TCSM3i.

This document describes the product variants up to the S12 softwarerelease level.

For more information, refer to:

1. Installing BSC3i and TCSM3i

2. BSC3i Commissioning

3. BSS Integration

4. Rehosting GSM BTS Sites in Nokia NetAct Product Documentation

5. Site Documentation for BSC3i

6. Hardware Configuration Management

7. Transmission Management in BSS

8. TCSM Support in BSC

9. Commissioning TCSM2

10. Commissioning TCSM3i

11. Rehosting BSCs in Nokia NetAct Product Documentation



2 Overview of swapping

Swapping out a BSC/BSC2 with a BSC3i involves site preparation andnew BSC3i installation (see Installing BSC3i and TCSM3i); a process tointegrate the BSC3i to the network (see BSC3i Commissioning) and BSSIntegration, a process to migrate the BTS from the BSC/BSC2 to theBSC3i; and, finally, the removal of the BSC/BSC2 from the network.

The process related to the installing and commissioning of the BSC3i canbe found in Installing BSC3i and TCSM3i and BSC3i Commissioning.These documents focus on the process of integrating the new BSC3i andmigrating of the BTS off the old BSC/BSC2. In general, there are two waysto do this: identical swap and traffic migration.

2.1 Identical swap

The Identical swap method is used to build the BSC3i with identicalnetwork settings to the old BSC/BSC2. This means that the BSC3i usesthe same identical configurations in the A, Gb, Q3, and SPC as in the oldBSC/BSC2 and with proper Exchange Terminal (ET) / Base StationController Signalling Unit (BCSU) adjustment such that the externalnetworks (MSC, SGSN, and OSS) are not affected at all. This type of swaprequires a flash cut method in which all the physical transmissions to theold BSC/BSC2 are cut over to the new BSC3i at once. In practice, thismethod is never used because the pretesting on the BSC3i is limited andthe flash cut of all the sites to the BSC3i at once is risky. Therefore, thismethod is not recommended and not discussed further in this document.

2.2 Traffic migration

The traffic migration method is used to build the BSC3i as a new BSC inthe network and then gradually migrate the traffic from the old BSC/BSC2to the new BSC3i. The new BSC3i appears in the network as a new BSC,and changes to the MSC, OSS, and SGSN are needed. The sites are



Overview of swapping

created and rehomed in the BSC3i and MSC with BSS Split application(see Rehosting GSM BTS Sites in Nokia NetAct Product Documentation)with a new BSC ID. If it is necessary, the location area code (LAC) can bechanged too, but typically it is not changed. Because the BTS site ismigrated using the BSS Split application, the network planning efforts areminimal. The method also allows pretesting, makes a more controlledcutover possible, and does not cause a full BSC outage during therehoming process. Therefore, this is the recommended method ofswapping a BSC/BSC2 with a BSC3i. The rest of this document coversthis method in more detail.



3 Traffic migration method

3.1 Network planning requirements to the BSC3i

BSC name

The BSC3i needs a new name.

SPC, LAC

Following the process of migrating the traffic from the BSC/BSC2 to theBSC3i, a new signalling point code (SPC) is needed to do the preliminaryintegration of the BSC3i to the core network. If needed, an additionallocation area code (LAC) can be allocated to the BSC3i, which simplifiesthe migration process.

BCSU/ET redistribution

As the amount of the Base Station Controller Signalling Units (BCSUs)and Exchange Terminals (ETs) and the ET numbering are differentbetween a BSC/BSC2 and a BSC3i, you have to plan carefully before thetraffic migration process can start. The ETs allocated for Ater, Gb, externalSync, and A-bis would have to be reconsidered, as well as the LapDdistribution among the BCSUs. BSC3i 1000/2000 supports additionallySTM-1/OC-3 optical connections, and the transition from pulse codemodulation (PCM) connections to synchronous digital hierarchy (SDH) /synchronous optical network (SONET) connections should be separatelyreviewed.

GPRS/EDGE/DAP

In the BSC3i, the number of logical PCUs in a BCSU can be higher than ina BSC/BSC2, namely four. That is, the maximum number of PCU-B plug-inunits (including two logical PCUs) is two per BCSU. The number of theneeded PCU-B plug-in units (either one per BCSU or two per BCSU)depends on the active PCUs in the BSC/BSC2. Therefore, planning inregards to the network service entity identifier (NSEI) and dynamic Abis



Traffic migration method

pool (DAP) has to be made before the traffic migration process. That is,which logical PCU in the BSC3i takes over the role of a certain PCU in theBSC/BSC2 or how to configure the Gb interfaces of the BSC3i PCUs andhow to rehost the cells and DAPs into the PCUs. Moreover, you shouldconsider if increased data traffic is expected on the new BSC3i, whichwould demand more capacity on the (E)GPRS territories, DAPs, and/or Gbinterface.

In addition, bringing up the BSC3i along the side of the BSC/BSC2requires additional need for NSEIs, network service virtual connectionidentifiers (NS-VCIs), and data link connection identifiers (DLCIs) datafillfor the new BSC3i. One option from the (E)GPRS point of view is to swapthe cells from the BSC/BSC2 to the new BSC3i in PCU level (create Gbinterface with the same parameters, then swap all the cells of a certainPCU and make a new cross-connection for the frame relay).

TCSM Ater

As the BSC3i has higher traffic capacity than the BSC/BSC2, you shouldconsider if additional capacity is needed on the A-interface, which leads totwo planning scenarios:

1. Additional TCSMs are added to the footprint (TCSM2 or TCSM3i).

New added TCSMs are integrated to the BSC3i following theintegration process, and they are used during the acceptance testingof the BSC3i. During the traffic migration process, the existingTCSMs connected to the BSC2 are reconnected to the BSC3i.

2. No additional TCSMs are added.

For the acceptance testing of the BSC3i, the existing TCSM(s) fromthe BSC/BSC2 have to be reconnected to the BSC3i. During thetraffic migration process, the remaining TCSM(s) connected to theBSC/BSC2 are gradually reconnected to the BSC3i as the trafficmigrates.

IP planning

The BSC3i comes with the integrated LAN switches, and additionalplanning of the IP configuration is needed, such as Spanning TreeProtocols, maintenance of the IP address for the ESB cards, and so on.For further information, see the standard procedures for BSC3i in InstallingBSC3i and TCSM3i, in BSC3i Commissioning, and in BSC Site IPConnectivity Guidelines.



3.2 Site engineering plan of the new BSC3i

In this step, the site engineering plan is performed for issues such as:

. planning for location of the new/old equipment

. digital distribution frame (DDF) / digital cross-connect (DXC)planning of the new/old equipment

This is a standard procedure for installing a new BSC. For furtherinformation, see Installing BSC3i and TCSM3i.

3.3 Installation and commissioning of BSC3i

This is a standard procedure. For further information, see BSC3iCommissioning, and BSS Integration.

3.4 Application software

If the old BSC is on S11.5 or S12 level, some optional application softwarefunctionality has licence key-based activation and usage control. If thelicence key-controlled functionality is needed for the new BSC3i, newlicence keys should be ordered. Otherwise, file-based application softwareand additional software parameters are introduced to the new BSC3i asusual.

3.5 Export data from the old BSC

This data is needed for planning the new BSC3i. See the MML referencefor retrieving this data below:

MML reference for the old BSC data

Circuits

ZRCI;

ZRCI:SEA=3:NCGR=<circuit_group_name>:PRINT=5;

ZWUP:GSW;




ZWGO:

A interface

ZNET;

ZNSI:<network_number>;

ZNHI:<network_number>;

ZNEL;

ZNPI;

ZOBI:<network_number>;

ZOBL:<network_number>;

ZDRI;

Gb interface

ZFUI;

ZFNO;

ZEBP;

ZFWO:BCSU=0&&8:BTS;

Q3 interface

ZQNI;

ZQCI;

ZQBI;

ZQBL;

ZQDI::MAX;

ZQEI;

ZQGI;



ZQLI;

ZQLP;

ZQQI;

ZQSI;

ZQTI;

ZQXI;

ZQWI::ALL;

ZIFO:OMU:OBSERV:1&&120;

ZIFO:OMU:MEASUR:1&&300;

ZIFI:OMU:OBSERV;

ZIFI:OMU:MEASUR;

Alarm settings

ZARO:C,P;

ZARO:C,S;

ZARO:D,P;

ZARO:D,S;

ZABO;

ZEOE;

External alarms configured

ZWAT;

ZWAP;

BSC level parameters

ZEEO:ALL;




ZWOI;

ZWOS;

ZEGO;

Command calendar settings

ZICL::COM;

Q1 supervision for transmission elements

ZQWI::ALL; (channels and equipment)

ZQWL; (equipment)

ZQUL; (transmission equipment the SW builds)

ZQUO; (network element group data of the transmission equipment theSW builds)

Software load for BSC, BTS

ZWQO:CR;

ZEWO:BCF=1&&248;

ZEWL;

Licences and features

ZW7I:LIC,LIM; (codes and names of all licences)

ZW7I:LIC,FULL; (all information about all licences)

ZW7I:FEA,LIM:LIC=xxx; (repeat this for all licence codes "xxx")

Semi-permanent connections and UTPFIL patchings

ZRBI:ALL;

Feature files and activated features

ZEEO:ALL;

ZWOI;



ZWOS;

ZEGO;

TCP/IP settings

ZQRI;

ZQRL;

ZQRJ;

ZQRS:OMU;

Multi-vendor settings

These settings are customer/vendor-specific and should be reviewed caseby case. Interface-based settings (A, Abis, Gb, and Q3) are describedseparately in previous sections.

Radio network

ZEEI::BCSU;

ZEEL;

ZEEP;

ZEEI; (If SEG_USAGE = FALSE)

ZEEI:SEG=ALL; (If SEG_USAGE = TRUE)

ZEFO:1&&248:ALL;

ZEQO:BTS=1&&248:ALL;

ZERO:BTS=1&&248;

ZEBO;

ZDSB;

ZDSI;

ZDTI;




ZDTF:TCSM:OMU;

ZEWL;

ZEWP:ID=<build id>;

ZEVL;

ZEWO:1&&248;

ZEAO:BTS=1&&248;

ZEAT;

ZEHO:BTS=1&&248;

ZEUO:BTS=1&&248;

ZECP;

ZESO;

ZEXQ;

ZEXI;

ZEYI::1;

ZESI;

ZESI:ID=1&&470:TRXS;

Other settings that need changes

Change the settings according to your system or network.

3.6 Datafill preparation/adjustment for BSC3i

Based on the data exported from the old BSC, the issues presented in thefollowing sections should be reviewed.

A interface (transcoder)

At least one transcoder is needed for pretesting.



The A interface redimensioning may be needed.

The A interface ET plan may need to be adjusted as the BSC3i ETnumbering is different.

Abis interface

The Abis interface ET plan may need to be adjusted, as the BSC3i ETnumbering and the number of ETs is different.

Gb interface

Gb interface redimensioning may be needed.

The Gb interface ET plan may need to be adjusted, as the BSC3i ETnumbering is different.

O&M interface

No foreseeable changes.

Radio network

As mentioned in the BSS split document Rehosting GSM BTS Sites inNokia NetAct Product Documentation, the tasks related to creating RadioNetwork (RNW) and Gb interface objects and so on are a prerequisite torehoming the BTS sites. The RNW objects the BSS split does not handlecan be managed by using the NetAct RAC CM Editor.

3.7 Integration of the BSC3i

In this step, the datafill is downloaded from the standard datafill templatesto the new BSC3i. This requires the datafill and support from the MSC,SGSN, and OSS too.

3.8 Pre-testing of the BSC3i

This is a standard procedure. For further information, see BSC3iCommissioning.




3.9 Radio network rehome from the old BSC to theBSC3i

When you are confident that the BSC3i is ready for traffic, you can startmoving all the traffic from the old BSC to the BSC3i. The rehoming processis described in Rehosting GSM BTS Sites in Nokia NetAct ProductDocumentation.

The rehoming of the BTS sites impacts the service. The size of the impactdepends on how fast the physical transmission can be swapped over.Typically, the transmission time is about 20–30 sites over one night. Therehoming of all the sites from the BSC can take several nights.

3.10 Verification and recovery

After each gradual rehoming, an agreed verification procedure should beexecuted. If the BTS does not handle any calls after the cut over to thenew BSC, you can move the BTS back to the old BSC or continuetroubleshooting. For further information, see Rehosting GSM BTS Sites inNokia NetAct Product Documentation.

3.11 Decommissioning and removal of the old BSC

Follow the local procedure for the removal of the old BSC.



4 Product dimensionsWhat is new in the BSC3i

The BSC3i is based on the more modern DX 200 M98 mechanics, and ithas been designed to offer an enhanced radio access service in anoptimal and compact package. It is a stable, mature, and highly reliableproduct where the best parts of the latest DX 200 multi-processingplatform have been used to enable the packing of more circuit and packetswitching capacity to only one cabinet solution. It suits well into equipmentrooms where additional space is limited.

The BSC3i has many benefits compared to the existing BSC/BSC2. Firstof all, the BSC3i mechanics is more modern than the mechanics of theearlier BSCs. Even the cabinet is designed to resist fire and earthquake.Due to only one cabinet, the BSC3i 660 or BSC3i 1000 needs less spacethan the previous variants. In practice, this means that it can fit into anearly full BSC site better than the earlier BSCs. This means savings insite hunting, acquisition, construction works, and implementation,including installation planning, installation, commissioning, and integration.The new BSC3i has less BSS borders too, which means that the wholearea/hot spot is under the same BSC.

Number of the BCSUs

The BSC3i can be configured with a maximum of 6+1 Base StationController Signalling Units (BCSUs) (BSC3i 660) or a maximum of 10+1BCSUs (BSC3i 2000), while the BSC(2) can have 8+1 BCSUs. Theconfiguration of the BSC/BSC2 on BCSU 7 and 8 must be replanned to theBCSUs in the BSC3i 660.

Capacity

BSC3i has more capacity than the older BSC variants.

BSC3i 660

The following table presents the main capacity figures of the Nokia BSC3i660 on S11.5 level.



Product dimensions

Table 2. BSC3i 660 capacity steps

BSC3i TRXs 1...110 ...220 ...330 ...440 ...550 ...660

BTS 110 220 330 440 550 660

BCF 84 168 252 336 420 504

BCSUs (1redundantincluded)

2 3 4 5 6 7

Logical PCUs - - - - - -

With PCUstep 1

2 4 6 8 10 12

With PCUstep 2

4 8 12 16 20 24

Maximumnumber of 16kbit/s Abischannels for(E)GPRS use

1024 2048 3072 4096 5120 6144

Maximumradio TSL

880 1760 2640 3520 4400 5280

Maximumnumber ofSS7 links

8 16 16 16 16 16

64 kbit/s 4 8 12 16 16 16

128 kbit/s 2 4 6 8 10 12

256 kbit/s

Maximumnumber of ofLAPD links(BCFSIG+TRXSIG+ISDN+ET)

206 412 618 824 1030 1236

ET4 (4PCMs)maximum

64 64 64 64 64 64

BSC3i 1000/2000

The following table presents the main capacity figures of the Nokia BSC3i1000/2000.



Figure 1. BSC3i 1000/2000 capacity steps

BSC configuration comparison

A number of different configurations is likely to exist currently in networks.To assist in reviewing each BSC's configuration and capacity limitations,you can review the following table. The weakest Packet Control Unit(PCU) determines the maximum radio network configuration.

DN0660357

Maximum number of 16 kbit/s

Abis channels for (E)GPRS use

Maximum radio TSL

Maximum number of LAPD

links (BCFSIG + TRXSIG +

ISDN + ET/SET)

Example 1

with maximum number of PCMs

E1 / T1

STM-1 / OC-3

Example 2

E1 / T1

STM-1 / OC-3

BSC3i 1000/2000 TRXs

BTS

Logical PCUs:

With PCU step 1

With maximum number of PCUs

BCF

BCSUs(1 redundant included)

Maximum number of SS7links64 kbit/s128 kbit/s256 kbit/s512 kbit/s2 Mbit/s

1 ...200

384none

1286

384none

12812

384none

12816

384none

12816

384none

12816

8008

28816

8008

28816

210

...400

420

...600

630

...800

840

...1000

1050

...1200

1260

...1800

1890

2 3 4 5 6 7 10

1600 3200 4800 6400 8000 9600 14400

2560 5120 7620 12800 15360

200 400 600 800 1000 1200 1800...

...

...

...

...

200 400 600 800 1000 1200 1800...

...

...

...

... 2304010240

84221

168442

1612663

1616884

161610105

161612126

161616169

Maximum2000

11

20100

8008

28816

448 896 1344 1792 2240 2688 4032... 4480

16000

2000

2000

25600

1616161610



Product dimensions

The configurations B, C, and D can be supported only if the FeatureBSS6009 Large Capacity BSC is activated. An exception is the newdeliveries in configuration D.

Table 3. Overview of the different BSC configuration limitations

BSC ConfigurationsA BSC with no extra TRXs-BSCE B Large capacity BSC-BSC2E

Supported in BSC types BSCE

BSC2E

BSC2A

BSCE

BSC2E

BSC2A

Maximum radio networkconfiguration

128 BCF 128

BTS 128 TRX

200 BCF 248

BTS 256 TRX

Maximum number of PrimeSites 128 256

Allowed CPU type in OMU /Minimum size of memory inmegabytes

CP4HX/256

CP4HL/256

CP6LX/256

CP6MX/256

CP4HX/256

CP4HL/256

CP6LX/256

CP6MX/256


CP4HX/256

CP4HL/256

CP6LX/256

CP6MX/256

CP4HX/256

CP4HL/256

CP6LX/256

CP6MX/256


CP4HX/128

CP4HL/128

CP6LX/128

CP6MX/128

CP4HX/128

CP4HL/128

CP6LX/128

CP6MX/128

Allowed Group Switch type /Maximum number of PCMs

GSWB/128 GSWB/128

Number of AS7-U plug-in units inBCSUs

2-3 3

Number of AS7-V plug-in units inBCSUs

- -

Number of AS7-B plug-in units inBCSUs

- -

Number of AS7-C plug-in units inBCSUs

- -

Maximum number of externalPCMs

56 56/BSCE; 80/112/BSC2



Table 3. Overview of the different BSC configuration limitations (cont.)

BSC ConfigurationsA BSC with no extra TRXs-BSCE B Large capacity BSC-BSC2E

Type of LapD and Q1 terminal inOMU

AS7-U AS7-U

Minimum number of WO-EXBCSUs

1-8 8

Number of BCFSIG LapD links perBCSU

16 32

Number of TRXSIG LapD links perBCSU

16 32

Maximum number of LapD linksper BCSU (BCFSIG+TRXSIG+ISDN+ET-LAPD)

64 64

Maximum number of SDCCHs perBCSU

384 384

Maximum number of TCHs perBCSU

256 256

Table 4. Overview of the different BSC configuration limitations, HighCapacity BSC

BSC Configurations(S11.5)

C High Capacity BSC-BSCi

D High Capacity BSC-BSC2i

E High Capacity BSC-BSC3i 660

Supported in BSC Types BSCE BSC2E

BSC2A

BSC3i

Maximum radio networkconfiguration

248 BCF 512

BTS 512 TRX

248 BCF 512

BTS 512 TRX

504 BCF *Note1

660 BTS 660 TRX

Maximum number ofPrimeSites

256 256 256

Allowed CPU type inOMU / Minimum size ofmemory in megabytes

CP6LX/256

CP6MX/256

CP6LX/256

CP6MX/256

CP710/256

Allowed CPU type inMCMU / Minimum size ofmemory in megabytes

CP6LX/256

CP6MX/256

CP6LX/256

CP6MX/256

CP710/256

Allowed CPU type inBCSU / Minimum size ofmemory in megabytes

CP6LX/128

CP6MX/128

CP6LX/128

CP6MX/128

CP710/256



Product dimensions

Table 4. Overview of the different BSC configuration limitations, HighCapacity BSC (cont.)





Allowed Group Switchtype / Maximum numberof PCMs

GSWB/128

GSWB/192

GSWB/128

GSWB/192

GSWB/256

GSWB/256

(S10.5/S10.5ED/S11)

GSW1KB/512

(S11.5)

Number of AS7-U plug-inunits in BCSUs

- 0-1 -

Number of AS7-V plug-inunits in BCSUs

3 2-3 -

Number of AS7-B plug-inunits in BCSUs

- - 3

Number of AS7-C plug-inunits in BCSUs

- - 1

Maximum number ofexternal PCMs

56/88 80/112/144 124/256

Type of LapD and Q1terminal in OMU

AS7-V AS7-V AS7-B

/S10.5/S10.5ED

AS7-C (S11/S11.5)

Minimum number of WO-EX BCUs

1-8 1-8 1-6

Number of BCFSIG LapDlinks per BCSU

32 32 84 *Note2

Number of TRXSIG LapDlinks per BCSU

64 64 110

Maximum number ofLapD links per BCSU(BCFSIG+TRXSIG+ISDN+ET-LAPD)

117 124 206 *Note3

Maximum number ofSDCCHs per BCSU

768 768 1760

Maximum number ofTCHs per BCSU

512 512 880

Notes

Note 1: The maximum number of the 504 BCF objects is supported with AS7-C and GSW1KB hardware.With AS7-C and GSWB/256 hardware the maximum number of the supported BCF objects is 378. With AS7-B and GSWB/256 hardware, the maximum number of the supported BCF objects is 248.



Table 4. Overview of the different BSC configuration limitations, HighCapacity BSC (cont.)





Note 2: The maximum number of 84 BCFSIG LapD links per BCSU is supported with AS7-C and GSW1KBhardware. With AS7-B or GSWB/256 hardware, the maximum number of the supported BCFSIG LapD linksper BCSU is 43.

Note 3: The maximum number of the 206 LapD links per BCSU is supported with AS7-C and GSW1KBhardware. With AS7-B or GSWB/256 hardware, the maximum number of the supported LapD links perBCSU is 170.

VDU/LPT

The visual display unit (VDU) and the line printer (LPT) ports for BSC3i arein the CPRJ45 panel, which is located on top of the BSC3i cabinet.

The VDU can be connected to the CPRJ45 panel by using the CNM cable,which is a CNI-type (straight-connected) cable provided with an RJ45connector and a D9 connector. For more details, see Installing BSC3i andTCSM3i.

ESB

Cabling and Ethernet connectors on top of the cabinet in BSC3i.

External alarms

No difference as such; different HWAT plug-in unit version.

Synchronisation

No difference in external synchronisation.

ET numbering

BSC3i 660 has two Exchange Terminal (ET) cartridges. This makes itpossible to have a maximum of 124 2 Mbit ET pulse code modulations(PCMs) or 124 1.5 Mbit ET PCMs in one BSC3i with ET2 plug-in units(each having two logical PCMs). In S11.5 with new GSW1KB and ET4(four logical PCMs each), the maximum amount of ET PCMs is 256 (seeFigure ET4C-B cartridges and ET2A/ET2E-S/SC indexes in BSC3i). InBSC3i 1000/2000 there can be 50 ET16 plug-in units offering 800 externalPCM connections. Optionally it is possible to have 16 external opticalSTM-1/OC-3 connections.



Product dimensions

Figure 2. ET4C-B cartridges and ET2A/ET2E-S/SC indexes in BSC3i

The BSC2 and BSC2i can have up to nine ET5C cartridges, each havingspace for 16 Mbit ET PCM connections from 8 ET2 plug-in units. Thismakes it possible to have a maximum of 144 2Mbit ET PCMs in one BSC(see Figure ET5C cartridges and ET2E/A indexes in BSC2). Note also thatthe BSCE can have up to 56 2Mbit ET PCMs, and the BSCi can have up to88 2Mbit ET PCMs.

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15

16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

160161

162163

164165

166167

168169

170171

172173

174175

176177

178179

180181

182183

184185

186187

188189

190191

ET4C 0

ET4C 1

BCSU0

BCSU1

BCSU2

BCSU3

BCSU4

BCSU5

GSWB0

GSWB1

CLS0,1

BCSU6

MCMU0

MCMU1

OMU

PDFU-A0

PDFU-A3

PDFU-A2

PDFU-A1

CPGOCPGO CPRJ45

FTRB 1FTRB 0

FTRB 3FTRB 2

0

1

2

3

4

5

TO

BSCC - FRONT VIEW GSWB

GSWB

ET4C 1

224225

226227

228229

230231

232233

234235

236237

238239

240241

242243

244245

246247

248249

250251

ET4C 0

9697

9899

100101

102103

104105

106107

108109

110111

112113

114115

116117

118119

120121

122123

124125

126127

3233

3435

3637

3839

4041

4243

4445

4647

4849

5051

5253

5455

5657

5859

6061

6263

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15

16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

DN0659176



Figure 3. ET5C cartridges and ET2E/A indexes in BSC2

PSA20_0PSFP0

PSA20_1PSFP1

PSA20_2PSFP2

PSA20_3PSFP3

GSW B0 GSW B1

CLOC0

MCMU1

OMU

BCSU3 BCSU4

BCSU1 BCSU2

BCSU0

BCBE BCEE

MCMU0

WDDC1

WDDC0

CLAC0

BCSU7 BCSU8

BCSU5 BCSU6

ET5C0

3233

3435

3637

3839

4849

5051

5253

5455

GSWB:

GSWB:

ET5C1

4041

4243

4445

4647

5657

5859

6061

6263

GSWB:

GSWB:

ET5C2

7273

7475

7677

7879

8889

9091

9293

9495

GSWB:

GSWB:

ET5C3

8081

8283

8485

8687

9697

9899

100101

102103

GSWB:

GSWB:

ET5C4

104105

106107

108109

110111

112113

114115

116117

118119

GSWB:

GSWB:

ET5C5

120121

122123

124125

126127

128129

130131

132133

134135

GSWB:

GSWB:

ET5C6

136137

138139

140141

142143

144145

146147

148149

150151

GSWB:

GSWB:

ET5C7

224225

226227

228229

230231

232233

234235

236237

238239

GSWB:

GSWB:

ET5C8

240241

242243

244245

246247

248249

250251

252253

254255

GSWB:

GSWB:

DN0659188



Product dimensions

5 Changeout of the TCSM

The recommended traffic migration path, instead of the identical swap, isthe following:

1. Commissioning a new TCSM3i

2. Adding a TCSM (TCSM3i)

3. Deleting a TCSM (TCSM2)

Follow the instructions in Hardware Configuration Management:

. adding a TCSM

. deleting a TCSM

For further information, see the instructions in BSS TransmissionManagement:

. configuring a new transcoder

. modifying an existing transcoder configuration

For A interface-related issues, see BSS Integration:

. creating the A interface

. synchronising the A interface

For additional information, see:

. Commissioning TCSM2

. Commissioning TCSM3i

. TCSM Support in BSC

. Rehosting BSCs in Nokia NetAct Product Documentation

. Rehosting GSM BTS Sites in Nokia NetAct Product Documentation



Changeout of the TCSM

31143242 Swapping Old Gen Bsc and Tcsms With a New Gen Nokia

Documents

Transcript of 31143242 Swapping Old Gen Bsc and Tcsms With a New Gen Nokia