dn70622773.pdf

Nokia Siemens Networks Flexi BSC, S15, Site Documentation for TCSM3i, issue 07

Swapping BSC and TCSM with Flexi BSC and TCSM3i

DN70622773

Issue 1-0

2 DN70622773Issue 1-0


Id:0900d805804aff11

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

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

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

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

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

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

Copyright © Nokia Siemens Networks 2010/10/29. All rights reserved

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

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

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

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

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

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

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

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

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

DN70622773Issue 1-0

3


Id:0900d805804aff11

Table of ContentsThis document has 23 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 Overview of swapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.1 Identical swap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2 Traffic migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3 Traffic migration method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.1 Network planning requirements to the Flexi BSC . . . . . . . . . . . . . . . . . 113.2 Site engineering plan of the Flexi BSC (S14) . . . . . . . . . . . . . . . . . . . . 123.3 Installation and commissioning of the Flexi BSC. . . . . . . . . . . . . . . . . . 123.4 Application software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.5 Export data from the old BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.6 Datafill preparation/adjustment for the Flexi BSC . . . . . . . . . . . . . . . . . 153.7 Integration of the Flexi BSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.8 Pre-testing of the Flexi BSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.9 Radio network rehome from the old BSC to the Flexi BSC (S14) . . . . . 163.10 Verification and recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.11 Decommissioning and removal of the old BSC . . . . . . . . . . . . . . . . . . . 16

4 Product dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5 Changeout of the TCSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4 DN70622773Issue 1-0


Id:0900d805804aff11

List of FiguresFigure 1 BSC3i 1000/2000 capacity steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

DN70622773Issue 1-0

5


Id:0900d805804aff11

List of TablesTable 1 The GSM/EDGE BSC product family . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Table 2 Flexi BSC maximum capacity steps in S14 hardware environment . . . 17Table 3 BSC3i 660 capacity steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Table 4 Radio network configurations supported by S14 - BSCi, BSC2i, BSC3i 660

20Table 5 Radio network configurations supported by S14 - BSC3i 1000, BSC3i

2000, and Flexi BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

6 DN70622773Issue 1-0


Id:0900d805804aff11

DN70622773Issue 1-0

7

Swapping BSC and TCSM with Flexi BSC and TCSM3i Summary of changes

Id:0900d805804913e2

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

First issueThis is the first issue of Swapping BSC and TCSM with Flexi BSC and TCSM3i, DN70622773, based on an earlier document (DN0618236).

8 DN70622773Issue 1-0


Id:0900d8058047bb7b

Introduction

1 IntroductionThis document describes the overall process of swapping an older M92 mechanic-based BSC with an M98 mechanic-based Flexi BSC. The M92 mechanic-based BSCs are the following:

• BSCE • BSCi • BSC2 • BSC2i

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

There are three main Flexi BSC product configurations: BSC3i 660, BSC3i 1000/2000 and Flexi BSC (S14). The product configuration is described specifically if the topic area is configuration-specific. The second generation Packet Control Units (PCU2s) are not included, however, as PCU-related swap procedures are described in GPRS/ EDGE Hardware Implementation.

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

This document describes the product variants up to the S14 software release level.

For more information, refer to:

BSC = Base Station Controller, a general term for all BSC versions

General name Product name Explanation

BSC/BSC2 BSCE *) First generation DX 200 BSC (BSCE)

BSC2 *) Second generation DX 200 BSC2

BSCi/BSC2i BSCi High capacity (upgraded) version of the first generation DX 200 BSC (BSCE)

BSC2i High capacity version of the second generation DX 200 BSC2

Flexi BSC product family BSC3i 660 660 TRX one-cabinet configuration, upgradable to Flexi BSC

BSC3i 1000/2000 1000 TRX one-cabinet or 2000 TRX two-cabinet configuration, upgrad-able to Flexi BSC

Flexi BSC 3000 TRX one-cabinet configuration (S14)

Note

*) The hardware and software support for the older products (BSCE and BSC2) has already ended. However, this document applies also to swapping of these products to Flexi BSC product family.

Table 1 The GSM/EDGE BSC product family

DN70622773Issue 1-0

9

Swapping BSC and TCSM with Flexi BSC and TCSM3i Introduction

Id:0900d8058047bb7b

1. Installing Flexi BSC and TCSM3i2. Flexi BSC Commissioning3. BSS Integration4. Rehosting GSM BTS Sites in Nokia Siemens NetAct Product Documentation5. Site Documentation for Flexi BSC6. Hardware Configuration Management7. Transmission Management in BSS8. TCSM Support in BSC9. Commissioning TCSM210. Rehosting BSCs in Nokia Siemens NetAct Product Documentation

10 DN70622773Issue 1-0


Id:0900d805804f4d06

Overview of swapping

2 Overview of swappingSwapping out a BSC/BSC2 with a Flexi BSC involves site preparation and Flexi BSC (S14) installation (see Installing Flexi BSC and TCSM3i) and a process to integrate the Flexi BSC to the network (see Flexi BSC Commissioning and BSS Integration), a process to migrate the BTS from the BSC/BSC2 to the Flexi BSC; and, finally, the removal of the BSC/BSC2 from the network.

The process related to the installing and commissioning of the Flexi BSC can be found in the manuals mentioned above. These documents focus on the process of integrating the Flexi BSC (S14) and migrating of the BTS off the old BSC/BSC2. In general, there are two ways to do this: identical swap and traffic migration.

2.1 Identical swapThe Identical swap method can be used to build the Flexi BSC with identical network settings to the old BSC/BSC2. This means that the Flexi BSC uses the same identical configurations in the A, Gb, Q3, and SPC as in the old BSC/BSC2 and with proper Exchange Terminal (ET) / Base Station Controller Signalling Unit (BCSU) adjustment such that the external networks (MSC, SGSN, and OSS) are not affected at all. This type of swap requires a flash cut method in which all the physical transmissions to the old BSC/BSC2 are cut over to the Flexi BSC (S14) at once. In practice, this method is never used because the pretesting on the Flexi BSC is limited and the flash cut of all the sites to the Flexi BSC at once is risky. Therefore, this method is not recommended and not discussed further in this document.

2.2 Traffic migrationThe traffic migration method is used to build the Flexi BSC as a new BSC in the network and then gradually migrate the traffic from the old BSC/BSC2 to the Flexi BSC (S14). The Flexi BSC (S14) appears in the network as a new BSC, and changes to the MSC, OSS, and SGSN are needed. The sites are created and rehomed in the Flexi BSC and MSC with BSS Split application (see Rehosting GSM BTS Sites in Nokia Siemens NetAct Product Documentation) with a new BSC ID. If it is necessary, the location area code (LAC) can be changed too, but typically it is not changed. Because the BTS site is migrated using the BSS Split application, the network planning efforts are minimal. The method also allows pretesting, makes a more controlled cutover possible, and does not cause a full BSC outage during the rehoming process. Therefore, this is the recom-mended method of swapping a BSC/BSC2 with a Flexi BSC. The rest of this document covers this method in more detail.

DN70622773Issue 1-0

11

Swapping BSC and TCSM with Flexi BSC and TCSM3i Traffic migration method

Id:0900d8058047f04a

3 Traffic migration method

3.1 Network planning requirements to the Flexi BSCBSC nameThe Flexi BSC needs a new name.

SPC, LACFollowing the process of migrating the traffic from the BSC/BSC2 to the Flexi BSC, a new signalling point code (SPC) is needed to do the preliminary integration of the Flexi BSC to the core network. If needed, an additional location area code (LAC) can be allo-cated to the Flexi BSC, which simplifies the migration process.

BCSU/ET redistributionAs the number of the Base Station Controller Signalling Units (BCSUs) and Exchange Terminals (ETs) and the ET numbering are different between a BSC/BSC2 and a Flexi BSC, you have to plan carefully before the traffic migration process can start. The ETs allocated for Ater, Gb, external Sync, and A-bis would have to be reconsidered, as well as the LapD distribution among the BCSUs. The network elements of the Flexi BSC product family, with the exception of BSC3i 660, support additionally STM-1/OC-3 optical connections, and the transition from pulse code modulation (PCM) connections to synchronous digital hierarchy (SDH) / synchronous optical network (SONET) connec-tions should be separately reviewed.

GPRS/EDGE/DAPIn M98 network elements (Flexi BSC product family), plug-in unit PCU2-E used only in the Flexi BSC (S14) has one logical PCU (1 x 1024 TCH) per plug-in unit, and plug-in units PCU2-D and PCU-B have two logical PCUs per plug-in unit (2 x 256 TCH). In the Flexi BSC, the number of logical PCUs in a BCSU is higher than in M92 network elements BSC/BSC2.

In an upgraded Flexi BSC network element with 3000 TRX capacity there can be up to 3 PCU2-Es in one cartridge, due to power supply restrictions if the power supply plug-in unit is not upgraded to PSC6-D. But in a new delivery Flexi BSC network element with 3000 TRX capacity there can be up to 5 PCU2-Es in one BCSU unit. Also in an upgraded Flexi BSC network element there can be up to 5 PCU2-Es in one BCSU unit when the BCSU unit has a new power supply plug-in unit PSC6-D.

Therefore, planning in regards to the network service entity identifier (NSEI) and dynamic Abis pool (DAP) has to be made before the traffic migration process. That is, which logical PCU in the Flexi BSC takes over the role of a certain PCU in the BSC/BSC2 or how to configure the Gb interfaces of the Flexi BSC PCUs and how to rehost the cells and DAPs into the PCUs. Moreover, you should consider if increased data traffic is expected on the Flexi BSC (S14), which would demand more capacity on the (E)GPRS territories, DAPs, and/or Gb interface.

In addition, bringing up the Flexi BSC alongside the BSC/BSC2 requires additional need for NSEIs, network service virtual connection identifiers (NS-VCIs), and data link con-nection identifiers (DLCIs) datafill for the Flexi BSC (S14). One option from the (E)GPRS point of view is to swap the cells from the BSC/BSC2 to the Flexi BSC (S14) in PCU level (create Gb interface with the same parameters, then swap all the cells of a certain PCU and make a new cross-connection for the frame relay).

12 DN70622773Issue 1-0


Id:0900d8058047f04a

Traffic migration method

TCSM AterAs the Flexi BSC has higher traffic capacity than the BSC/BSC2, you should consider if additional capacity is needed on the A-interface, which leads to two planning scenarios:

1. Additional TCSMs are added to the footprint (TCSM2 or TCSM3i).New added TCSMs are integrated to the Flexi BSC following the integration process, and they are used during the acceptance testing of the Flexi BSC. During the traffic migration process, the existing TCSMs connected to the BSC2 are recon-nected to the Flexi BSC.

2. No additional TCSMs are added.For the acceptance testing of the Flexi BSC, the existing TCSM(s) from the BSC/BSC2 have to be reconnected to the Flexi BSC. During the traffic migration process, the remaining TCSM(s) connected to the BSC/BSC2 are gradually recon-nected to the Flexi BSC as the traffic migrates.

IP planningThe Flexi BSC comes with the integrated LAN switches, and additional planning of the IP configuration is needed, such as Spanning Tree Protocols, maintenance of the IP address for the ESB cards, and so on. For further information, see the standard proce-dures in Installing Flexi BSC and TCSM3i, in BSC3i Commissioning, and in BSC Site IP Connectivity Guidelines.

3.2 Site engineering plan of the Flexi BSC (S14)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 further information, see Installing Flexi BSC and TCSM3i.

3.3 Installation and commissioning of the Flexi BSCThis is a standard procedure. For further information, see BSC3i Commissioning, and BSS Integration.

3.4 Application softwareIf the old BSC is on S11.5 or S12 level, some optional application software functionality has licence key-based activation and usage control. If the licence key-controlled func-tionality is needed for the Flexi BSC (S14), new licence keys should be ordered. Other-wise, file-based application software and additional software parameters are introduced to the Flexi BSC (S14) as usual.

3.5 Export data from the old BSCThis data is needed for planning the Flexi BSC (S14). See the MML reference for retriev-ing this data below:

DN70622773Issue 1-0

13


Id:0900d8058047f04a

MML reference for the old BSC data

1. CircuitsZRCI; (circuit groups)ZRCI:SEA=3:NCGR=<circuit_group_name>:PRINT=5; (all data regarding the circuit group(s) by name)ZWUP; (PCM circuit information)ZWGO; (transcoder PCM information)

2. A interfaceZNET; (signalling network item states)ZNSI:<signalling_network>,<signalling_point_codes>:P; (signalling link set data)ZNHI:<signalling_network>,<signalling_point_codes>; (SCCP sub-system states)ZNEL; (signalling link states)ZNPI; (data on all service indicators on all signalling networks)ZOBI:<network_of_affected_subsystem>:<network_of_concerned_signalling_point>:A; (SCCP signalling point broadcast status)ZOBL:<network_of_affected_subsystem>:<network_of_local_subsystem>:A; (SCCP subsystem local broadcast status)ZDRI; (synchronization unit information)

3. Gb interfaceZFUI; (frame relay bearer channel data)ZFNO; (frame relay bearer channel signalling parameter data)ZEBP; (routing area information in the BSDATA)ZFXO:BCSU=0&&8:BTS; (network service virtual connection data in the BCSUs)

4. Q3 interfaceZQNI; (O&M network configuration)ZQCI; (physical channel data)ZQBI; (OSI network address data)ZQBL; (network NSAP data)ZQDI::MAX; (OSI application data)ZQEI; (connectionless network service data)ZQGI; (physical channel group data)ZQLI; (linkage data)ZQLP; (linkage information about manual adjacencies)ZQQI; (OSI access control data)ZQSI; (physical channel states)ZQTI; (analog terminal equipment data)ZQXI; (X.25 interface parameter data)ZQWI::ALL; (Q1 service channel configuration and equipment)ZIFO:OMU:OBSERV:1&&120; (control file information of the OBSERV application of the OMU)ZIFO:OMU:MEASUR:1&&300; (control file information of the MEASUR application of the OMU)ZIFI:OMU:OBSERV; (information of the OBSERV application of the OMU)ZIFI:OMU:MEASUR; (information of the MEASUR application of the OMU)

14 DN70622773Issue 1-0


Id:0900d8058047f04a


5. Alarm settingsZARO:C,P; (rules of the preventing rulebase of the centralized part of the alarm system)ZARO:C,S; (rules of the supporting rulebase of the centralized part of the alarm system)ZARO:D,P; (rules of the preventing rulebase of the distributed part of the alarm system)ZARO:D,S; (rules of the supporting rulebase of the distributed part of the alarm system)ZABO; (information about blocked alarms)ZEOE; (list of blocked alarms)

6. External alarms configuredZWAT; (device types and alarm texts of all defined external alarms)ZWAP; (opened alarm connections)

7. BSC level parametersZEEO:ALL; (all BSC parameters in the BSDATA)ZWOI; (PRFILE parameter data)ZWOS; (FIFILE parameter data and feature activation status)ZEGO; (timers and parameters)

8. Command calendar settingsZICL::COM; (contents of the command calendar)

9. Q1 supervision for transmission elementsZQWI::ALL; (Q1 service channel configuration and equipment)ZQWL; (transmission equipment configuration on Q1 service channels)ZQUL; (software builds)ZQUO; (network element group data)

10. Software load for BSC, BTSZWQO:CR; (software packages created in the network element)ZEWO:1&&248; (software configurations of the BCFs)ZEWL; (existing BCF software builds)

11. Licences and featuresZW7I:LIC,LIM; (codes and names of all installed licences)ZW7I:LIC,FULL; (all information about all installed licences)ZW7I:FEA,LIM:LIC=xxx; (codes and names of all the features covered by licence 'xxx')

12. Semi-permanent connections and UTPFIL patchingsZRBI:ALL; (semipermanent broadband connections)

13. Feature files and activated featuresZEEO:ALL; (all BSC parameters in the BSDATA)ZWOI; (PRFILE parameter data)ZWOS; (FIFILE parameter data and feature activation status)ZEGO; (timers and parameters)

14. TCP/IP settingsZQRI; (configured network interfaces)ZQRH; (TCP/IP parameter information)ZQRJ; (DNS parameters)ZQRS:OMU; (active Internet connections of the OMU)

DN70622773Issue 1-0

15


Id:0900d8058047f04a

15. Multi-vendor settingsThese settings are customer/vendor specific and should be reviewed case by case. Interface-based settings (A, Abis, Gb, and Q3) are described separately in previous steps.

16. Radio networkZEEI::BCSU; (the number of TRXs and links under BCSUs)ZEEL; (BSC network information)ZEEI; (radio network configuration when the segment usage option is off)ZEEI:SEG=ALL; (radio network configuration under all segments when the segment usage option is off)ZEFO:1&&248:ALL; (BCF parameters of BCFs 1-248)ZEQO:BTS=1&&248:ALL; (BTS parameters of BTSs 1-248)ZERO:BTS=1&&248; (TRX parameters under BTSs 1-248)ZEBO; (BCCH frequency lists)ZDSB; (BSC D-channel data)ZDSI; (D-channel link set data)ZDTI; (D-channel working states)ZDTF:TCSM:OMU; (TCSM D-channel working states of the OMU)ZEWL; (existing BCF software builds)ZEWP:ID=<build_id>; (BCF software build contents)ZEVL; (existing BCF hardware databases)ZEWO:1&&248; (software configurations of the BCFs)ZEAO:BTS=1&&248; (adjacent cells under BTSs 1-248)ZEAT; (adjacent cell data)ZEHO:BTS=1&&248; (handover control parameters of BTSs 1-248 when the segment usage option is off)ZEUO:BTS=1&&248; (power control parameters of BTSs 1-248 when the segment usage option is off)ZECP; (display cell broadcast messages in a short format)ZESO; (information on autoconfiguration pools)ZEXQ; (SMLC parameters)ZEXI; (LMU areas in the database)ZEYI::1; (current pool lists in all speech codecs)ZESI; (information on dynamic Abis pools)ZESI:ID=1&&470:TRXS; (information on connected TRXs at the pools 1-470)

17. Other settings that need changes Modify the settings according to your system or network.

3.6 Datafill preparation/adjustment for the Flexi BSCBased on the data exported from the old BSC, the issues presented in the following 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 Flexi BSC ET numbering is dif-ferent.

16 DN70622773Issue 1-0


Id:0900d8058047f04a


Abis interfaceThe Abis interface ET plan may need to be adjusted, as the Flexi BSC ET numbering and the number of ETs is different.

Gb interfaceGb interface redimensioning may be needed.

The Gb interface ET plan may need to be adjusted, as the Flexi BSC ET numbering is different.

O&M interfaceNo foreseeable changes.

Radio networkAs mentioned in the BSS split document Rehosting GSM BTS Sites in NetAct Product Documentation, the tasks related to creating radio network (RNW) and Gb interface objects and so on are a prerequisite to rehoming the BTS sites. The RNW objects the BSS split does not handle can be managed by using the NetAct RAC CM Editor.

3.7 Integration of the Flexi BSCIn this step, the datafill is downloaded from the standard datafill templates to the Flexi BSC (S14). This requires the datafill and support from the MSC, SGSN, and OSS too.

3.8 Pre-testing of the Flexi BSCThis is a standard procedure. For further information, see BSC3i Commissioning.

3.9 Radio network rehome from the old BSC to the Flexi BSC (S14)When you are confident that the Flexi BSC is ready for traffic, you can start moving all the traffic from the old BSC to the Flexi BSC. The rehoming process is described in Rehosting GSM BTS Sites in NetAct Product Documentation.

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

3.10 Verification and recoveryAfter each gradual rehoming, an agreed verification procedure should be executed. If the BTS does not handle any calls after the cut over to the new BSC, you can move the BTS back to the old BSC or continue troubleshooting. For further information, see Rehosting GSM BTS Sites in NetAct Product Documentation.

3.11 Decommissioning and removal of the old BSCFollow the local procedure for the removal of the old BSC.

DN70622773Issue 1-0

17

Swapping BSC and TCSM with Flexi BSC and TCSM3i Product dimensions

Id:0900d8058047c8c4

4 Product dimensionsWhat is new in the Flexi BSC product familyFlexi BSC (S14) is introduced in the Flexi BSC product family.

The Flexi BSC product family is based on the more modern DX 200 M98 mechanics, and it has been designed to offer an enhanced radio access service in an optimal and compact package. It is a stable, mature, and highly reliable product where the best parts of the latest DX 200 multiprocessing platform have been used to enable the packing of more circuit and packet switching capacity to only one cabinet solution. It suits well into equipment rooms where additional space is limited.

The three main product configurations of the Flexi BSC product family have many benefits compared to the existing BSCi/BSC2i. The new generation mechanics is more modern than the mechanics of the earlier BSCs. Even the cabinet is designed to resist fire and earthquake. Due to very high capacity, new BSCs needs less space than the previous variants. In practice, this means that it can fit into a nearly full BSC site better than the earlier BSCs. This means savings in site hunting, acquisition, construction works, and implementation, including installation planning, installation, commissioning, and integration. The Flexi BSC (S14) has less BSS borders too, which means that the whole area/hot spot is under the same BSC.

Number of the BCSUsThe Flexi BSC can be configured with a maximum of 6+1 Base Station Controller Sig-nalling Units (BCSUs) (Flexi BSC and BSC3i 660) or a maximum of 10+1 BCSUs (BSC3i 2000), while the BSC2i can have 8+1 BCSUs.

Flexi BSCIn S14 first deliveries, the Flexi BSC is available in a compact one-cabinet configuration for up to 3000 TRX configurations. It can be equipped flexibly with a number of packet control units (PCUs) and trunk circuits according to operator needs. The following table presents the main capacity figures of the Flexi BSC.

Flexi BSC TRXs 1)

1...500 ...1000 ...1500 ...2000 ...2500 ...3000, maximum

BTS sectors (BTS)

500 1000 1500 2000 2500 3000

BTS sites (BCF)

500 1000 1500 2000 2500 3000

Active BCSUs 1 2 3 4 5 6

TCH for GPRS/EDGE 2)

5120 10420 15360 20480 25600 30720

GigE Ethernet interfaces 3)

12 12 12 12 12 12

STM-1/OC-3 interfaces 3)

16 16 16 16 16 16

E1/T1 inter-faces 4)

800 800 800 800 800 800

Table 2 Flexi BSC maximum capacity steps in S14 hardware environment

18 DN70622773Issue 1-0


Id:0900d8058047c8c4

Product dimensions

BSC3i 1000/2000The following table presents the main capacity figures of the BSC3i 1000/2000 on S12 level.

Maximum number of LAPD links

1024 2048 3072 4096 5120 6144, maximum

Maximum number of SS7 links:

64 kbit/s 8 16 16 16 16 16

128 kbit/s 4 8 12 16 16 16

256 kbit/s 2 4 6 8 10 12

512 kbit/s 2 4 6 8 10 12

1024 kbit/s 1 2 3 4 5 6

2 Mbit/s 2 4 6 8 10 12

Notes

1) Software is scalable in 1 TRX steps with licence keys

2) Abis 16 kbit/s channels for GPRS/EDGE

3) Active interfaces; doubled for redundancy: 12 + 12 or 16 + 16

4) Above 48 requires a cabling cabinet

Table 2 Flexi BSC maximum capacity steps in S14 hardware environment (Cont.)

DN70622773Issue 1-0

19


Id:0900d8058047c8c4

Figure 1 BSC3i 1000/2000 capacity steps

BSC3i 660The following table presents the main capacity figures of the BSC3i 660 on S11.5 level.

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 SS7

links

64 kbit/s

128 kbit/s

256 kbit/s

512 kbit/s

2 Mbit/s

1 ...200

384

none

128

6

384

none

128

12

384

none

128

16

384

none

128

16

384

none

128

16

800

8

288

16

800

8

288

16

2

10

...400

4

20

...600

6

30

...800

8

40

...1000

10

50

...1200

12

60

...1800

18

90

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

8

4

2

2

1

16

8

4

4

2

16

12

6

6

3

16

16

8

8

4

16

16

10

10

5

16

16

12

12

6

16

16

16

16

9

Maximum

2000

11

20

100

800

8

288

16

448 896 1344 1792 2240 2688 4032... 4480

16000

2000

2000

25600

16

16

16

16

10

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

BTS 110 220 330 440 550 660

BCF 84 168 252 336 420 504

BCSUs (1 redundant included)

2 3 4 5 6 7

Logical PCUs - - - - - -

Table 3 BSC3i 660 capacity steps

20 DN70622773Issue 1-0


Id:0900d8058047c8c4

Product dimensions

Configuration comparisonVarious configurations are likely to exist in operators' networks. To assist in establishing which BSC configurations are supported on S14 level, the following tables show the BSC configurations and their capability.

With PCU step 1

2 4 6 8 10 12

With PCU step 2

4 8 12 16 20 24

Maximum number of 16 kbit/s Abis channels for (E)GPRS use

1024 2048 3072 4096 5120 6144

Maximum radio TSL

880 1760 2640 3520 4400 5280

Maximum number of SS7 links:

64 kbit/s 8 16 16 16 16 16

128 kbit/s 4 8 12 16 16 16

256 kbit/s 2 4 6 8 10 12

Maximum number of of LAPD links (BCF-SIG+TRX-SIG+ET)

206 412 618 824 1030 1236

ET4 (4PCMs) maximum

64 64 64 64 64 64

Table 3 BSC3i 660 capacity steps (Cont.)

BSC Configuration (S12) BSCi BSC2i BSC3i 660

Maximum radio network configuration 248 BCF

512 BTS

512 TRX

248 BCF

512 BTS

512 TRX

248/504 BCF

660 BTS

660 TRX

Allowed CPU type in OMU CP6LX/

CP6MX

CP6LX/

CP6MX

CP710-A/

CP710-AB

Allowed CPU type in MCMU CP6LX/

CP6MX

CP6LX/

CP6MX

CP710-A/

CP710-AB/

CP710-AC

Allowed CPU type in BCSU CP6LX/

CP6MX

CP6LX/

CP6MX

CP710-A/

CP710-AB/

CP710-AC

Table 4 Radio network configurations supported by S14 - BSCi, BSC2i, BSC3i 660

DN70622773Issue 1-0

21


Id:0900d8058047c8c4

Allowed Group Switch type / Maximum number of internal PCMs

GSWB/128

GSWB/192

GSWB/128

GSWB/192

GSWB/256

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

GSW1KB/512 (S11.5/S12)

Number of AS7 plug-in units in BCSUs (variant letter and number of units)

V 3 U 0-1

V 2-3

B 3 (S10.5/ S10.5ED)

C 1 (S11/S11.5)

Maximum number of external PCMs (E1/T1) 56/88 80/112/144 124 (ET2s) / 256 (ET4s)

Maximum number of STM-1/OC-3 interfaces - - -

Maximum number of GigE Ethernet inter-faces

- - 4 (ESB26, S11.5)

Type of LapD and Q1 terminal in OMU AS7-V AS7-V/

AS7-VA/

AS7-X

AS7-B (S10.5/S10.5ED)

AS7-C (S11/S11.5)

Minimum number of WO-EX BCSUs 1-8 1-8 1-6

Number of BCFSIG LapD links per BCSU 32 32 84

Number of TRXSIG LapD links per BCSU 64 64 110

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

117 124 170 (AS7-B) / 206 (AS7-C)

Maximum number of TCHs per BCSU 512 512 880

BSC Configuration (S12) BSCi BSC2i BSC3i 660

Table 4 Radio network configurations supported by S14 - BSCi, BSC2i, BSC3i 660 (Cont.)

BSC Configuration (S12 andS14 Flexi BSC) BSC3i 1000 BSC3i 2000 Flexi BSC

Maximum radio network configuration 1000 BCF

1000 BTS

1000 TRX

2000 BCF

2000 BTS

2000 TRX

3000 BCF

3000 BTS

3000 TRX

Allowed CPU type in OMU CP816-A CP816-A CP816-A

Allowed CPU type in MCMU CP816-A/

CP816-AC

CP816-A/

CP816-AC

CP816-A/

CP816-AC

Allowed CPU type in BCSU CP816-A/

CP816-AC

CP816-A/

CP816-AC

CP816-A/

CP816-AC

Allowed Group Switch type / Maximum number of internal PCMs

GSW2KB/2048 GSW2KB/2048 GSW2KB/2048

Number of AS7 plug-in units in BCSUs (variant letter and number of units)

C 2 C 2 D 2

Maximum number of external PCMs (E1/T1) 384 800 800

Maximum number of STM-1/OC-3 interfaces 16 16 16

Maximum number of GigE Ethernet interfaces 12 12 12

Type of LapD and Q1 terminal in OMU AS7-C AS7-C AS7-D

Table 5 Radio network configurations supported by S14 - BSC3i 1000, BSC3i 2000, and Flexi BSC

22 DN70622773Issue 1-0


Id:0900d8058047c8c4

Product dimensions

VDU/LPTThe visual display unit (VDU) and the line printer (LPT) ports for the Flexi BSC are in the CPRJ45-A connector panel, which is located at the Flexi BSC cabinet top.

The VDU can be connected to the CPRJ45-A panel by using the CNM cable, which is a CNI-type (straight-connected) cable provided with an RJ45 connector and a D9 connec-tor. For more details, see Installing Flexi BSC and TCSM3i.

ESBCabling and Ethernet connectors at the cabinet top in the Flexi BSC.

External alarmsNo difference as such; different HWAT plug-in unit version (HWAT-B in Flexi BSC, HWAT-A in BSC3i 1000/2000 and BSC3i 660).

SynchronisationNo difference in external synchronisation.

Exchange TerminalsIn Flexi BSC, there can be 50 ET16 plug-in units offering 800 external PCM connections. Optionally it is possible to have 16 external optical STM-1/OC-3 connections or external GigE Ethernet connections.

In BSC3i 1000/2000, there can be 50 ET16 plug-in units offering 800 external PCM con-nections. Optionally it is possible to have 16 external optical STM-1/OC-3 connections.

BSC3i 660 has two Exchange Terminal (ET) cartridges. This makes it possible 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 number of ET PCMs is 256.

The BSC2 and BSC2i can have up to nine ET5C cartridges, each having space for 16 Mbit ET PCM connections from 8 ET2 plug-in units. This makes it possible to have a maximum of 144 2Mbit ET PCMs in one BSC. Note also that the BSCE can have up to 56 2Mbit ET PCMs, and the BSCi can have up to 88 2Mbit ET PCMs.

Minimum number of WO-EX BCSUs 1-5 1-10 1-6

Number of BCFSIG LapD links per BCSU 200 200 500

Number of TRXSIG LapD links per BCSU 200 200 500

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

448 448 1024

Maximum number of TCHs per BCSU 1600 1600 4000

BSC Configuration (S12 andS14 Flexi BSC) BSC3i 1000 BSC3i 2000 Flexi BSC

Table 5 Radio network configurations supported by S14 - BSC3i 1000, BSC3i 2000, and Flexi BSC (Cont.)

DN70622773Issue 1-0

23

Swapping BSC and TCSM with Flexi BSC and TCSM3i Changeout of the TCSM

Id:0900d80580483605

5 Changeout of the TCSMThe recommended traffic migration path, instead of the identical swap, is the following:

1. Commissioning a new TCSM3i2. 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 Transmission Management:

• 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

dn70622773.pdf

Documents

site documentation

swapping bsc

safety instructions

product names

mentioned hardware

applicable safety standards

customer comments

software products