BSS Integration

GSM/EDGE BSS, Rel. RG20(BSS), Operating Documentation, Issue 05

Integrate and configure

BSS Integration

DN9812243

Issue 21-1Approval Date 2010-11-25

Confidential

2 DN9812243Issue 21-1

BSS Integration

Id:0900d805808a0773Confidential

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 2011. All rights reserved

f Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-satzes.

DN9812243 3

BSS Integration


Table of contentsThis document has 114 pages.

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

1 Overview of BSS integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 A interface protocol layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3 A interface configuration with TCSM2 and TCSM3i. . . . . . . . . . . . . . . . 11

4 ET indexes in BSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

5 Creating the A interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595.1 Connecting the A interface ET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595.2 Connecting the optical A interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615.3 Connecting the PWE interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635.4 Creating the transcoder devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635.4.1 Creating the TCSM3i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645.4.2 Creating TCSM3i for combined BSC/TCSM installation . . . . . . . . . . . . 685.4.3 Creating the TCSM2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715.5 Creating Ater Connection to Multimedia Gateway. . . . . . . . . . . . . . . . . 795.6 Creating the MTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825.7 Creating the SCCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855.8 Creating the speech channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

6 Synchronising the A interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

7 Adding DN2, SSS, DMR and BBM to the service channel . . . . . . . . . . 93

8 Creating the Abis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

9 Initialising base stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979.1 Creating LAPD links and a base station, and initialising the base station pa-

rameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979.2 Attaching the BCF software build to the BCF . . . . . . . . . . . . . . . . . . . 1009.3 Attaching the BTS hardware database to the BTS . . . . . . . . . . . . . . . 1029.4 Taking the base station into use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

10 Testing BSS integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10510.1 Testing local blocking of a TRX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10510.2 Testing the supervision of the TCSM2 (ETSI/ANSI) . . . . . . . . . . . . . . 10610.3 Testing the supervision of the TCSM3i (ETSI/ANSI) . . . . . . . . . . . . . . 10610.4 Testing IMSI Attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10710.5 Testing location updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10710.6 Testing MS to MS call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10710.7 Testing MS to MS call, B busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10810.8 Testing MS to MS call, A subscriber IMSI detach . . . . . . . . . . . . . . . . 10910.9 Testing successful handover: free TCHs . . . . . . . . . . . . . . . . . . . . . . . 10910.10 Testing unsuccessful handover: no free TCHs . . . . . . . . . . . . . . . . . . 11010.11 Testing radio resource queuing in handover . . . . . . . . . . . . . . . . . . . . 110

11 Test logs for BSS integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

4 DN9812243

BSS Integration


List of figuresFigure 1 Three layers of CCS7/SS7 signalling between MSC and BSC. . . . . . . . 10Figure 2 A interface configuration example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Figure 3 Time slot allocation for full-rate traffic on Ater 2 Mbit/s interface with the

TCSM2 (ETSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 4 A interface time slot allocation (ANSI) . . . . . . . . . . . . . . . . . . . . . . . . . . 17Figure 5 ET cartridges in the BSCC cabinet of BSC3i 1000 . . . . . . . . . . . . . . . . . 36Figure 6 ET cartridges in the BSCD extension cabinet of BSC3i 2000. . . . . . . . . 37Figure 7 ET cartridges in the new delivery Flexi BSC. . . . . . . . . . . . . . . . . . . . . . 38Figure 8 ET cartridges in the upgraded Flexi BSC . . . . . . . . . . . . . . . . . . . . . . . . 39Figure 9 GTIC cartridges in TCSM3i for combined BSC/TCSM installation . . . . . 41Figure 10 ET4C-B cartridges with GSWB and ET2A/ET2A-T(B)/ET2E-S/SC/ET2E-

T(B)/ET2E-TC(B) indexes in BSC3i 660. . . . . . . . . . . . . . . . . . . . . . . . . 54Figure 11 ET4C-B cartridges with GSW1KB and ET4A/ET4E/ET4E-C indexes in

BSC3i 660. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Figure 12 ET4C-B cartridges with GSW1KB and ET2A/ET2A-T(B)/ET2E-

S/SC/ET2E-T(B)/ET2E-TC(B) indexes in BSC3i 660 . . . . . . . . . . . . . . . 56Figure 13 ET5C cartridges and ET2E/ET2A indexes in BSC2i. . . . . . . . . . . . . . . . 57Figure 14 TCSM3i ET (ET16 or ETIP) units and transcoder units . . . . . . . . . . . . . 65Figure 15 Configuration of the TCSM3i for combined BSC/TCSM installation . . . . 68Figure 16 TCSM2 rack and cartridges (ETSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Figure 17 TCSM2 rack and cartridges (ANSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Figure 18 Ater interface with MGW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Figure 19 Multiplexed and non-multiplexed A interface with 8 kbit GSWB . . . . . . . 87Figure 20 Transmission equipment at Q1 service channel . . . . . . . . . . . . . . . . . . . 93Figure 21 Abis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Figure 22 BTS software directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Figure 23 The test arrangements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

DN9812243 5

BSS Integration


List of tablesTable 1 Circuit types supported by the TCSM3i . . . . . . . . . . . . . . . . . . . . . . . . 12Table 2 Allocation of different channels on the Ater-interface in the case of 16 kbit/s

TRAU frame submultiplexing (circuit type G) . . . . . . . . . . . . . . . . . . . . 12Table 3 Channel allocation for circuit type H on the Ater-interface . . . . . . . . . . 13Table 4 Channel allocation for circuit type I on the Ater-interface . . . . . . . . . . . 14Table 5 ET indexes in BSC3i 1000/2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Table 6 ET indexes in BSC3i 1000/2000 (ETSI ETS2, two active and two standby

STM-1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Table 7 ET indexes in BSC3i 1000/2000 (ETSI ETS2, one active and one standby

STM-1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Table 8 ET indexes in BSC3i 1000/2000 (ANSI ETS2, two active and two standby

OC-3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Table 9 ET indexes in BSC3i 1000/2000 (ANSI ETS2, one active and one standby

OC-3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Table 10 ETIP and ET indexes in BSC3i 1000/2000 when transmission redundancy

is in use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Table 11 ETIP and ET indexes in BSC3i 1000/2000 when HW redundancy is in use

26Table 12 ETIP and ET indexes in new delivery Flexi BSC when transmission redun-

dancy is in use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Table 13 ETIP and ET indexes in upgraded Flexi BSC when transmission redundan-

cy is in use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Table 14 ETIP and ET indexes in new delivery Flexi BSC when HW redundancy is

in use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Table 15 ETIP and ET indexes in upgraded Flexi BSC when HW redundancy is in

use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Table 16 ET indexes in new delivery Flexi BSC when transmission redundancy is in

use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Table 17 ET indexes in upgraded Flexi BSC when transmission redundancy is in

use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Table 18 ET indexes in new delivery Flexi BSC cartridges when HW redundancy is

in use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Table 19 ET indexes in upgraded Flexi BSC cartridges when HW redundancy is in

use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Table 20 ET indexes in TCSM3i for combined BSC/TCSM installation . . . . . . . . 40Table 21 ET indexes (ETS2) in TCSM3i for combined BSC/TCSM installation with

upgraded and new delivery Flexi BSC when transmission redundancy is used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Table 22 ET indexes (ETS2) in TCSM3i for combined BSC/TCSM installation with upgraded and new delivery Flexi BSC when HW redundancy is used . 45

Table 23 ET indexes (ETIP) in TCSM3i for combined BSC/TCSM installation with upgraded and new delivery Flexi BSC when transmission redundancy is used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Table 24 ET indexes (ETIP) in TCSM3i for combined BSC/TCSM installation with upgraded and new delivery Flexi BSC when HW redundancy is used . 50

Table 25 ET indexes with GSWB in BSCi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Table 26 Default synchronisation ETs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Table 27 TR3E/TR3A/TR3T roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

6 DN9812243

BSS Integration


Table 28 Possible combinations of circuit pools (TCSM3i) . . . . . . . . . . . . . . . . . . 67Table 29 Possible combinations of circuit pools . . . . . . . . . . . . . . . . . . . . . . . . . . 76Table 30 TCSM3i capacity with four TR3E unequipped . . . . . . . . . . . . . . . . . . . . 79Table 31 Circuit pools and supported codecs (with SubChannel bit information)

when using MGW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Table 32 BSS specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Table 33 Creating the A interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Table 34 Creating the Abis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Table 35 Initialising the base stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Table 36 Testing BSS integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

DN9812243 7

BSS Integration Summary of changes

Id:0900d8058086ac41Confidential

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

Changes made between issues 21-2 and 21-1The document is updated with the information on mcBSC.

Chapter Overview of BSS integration has been modified.

Changes made between issues 21-1 and 21-0In chapter ET indexes in BSC, some sections have been modified and editorial changes have been done.

Changes made between issues 21-0 and 20-0The document is updated with the information on Flexi BSC, TCSM3i, Flexi Multiradio BTS, and BTSplus BTS.

Chapters Overview of BSS integration, Creating the A interface, Synchronising the A interface and Initialising base stations have been modified.

Changes made between issues 20-0 and 19-1In chapter Overview of BSS integration, information on Multimedia Gateway and Flexi BSC has been added.

In chapter A interface configuration with TCSM2 and TCSM3i, information on the ETIP1-A plug-in unit, the Multipoint A interface and the Ater interface has been added.

In chapter ET indexes in BSC, information on ETIP1-A plug-in unit, and ETIP and ET indexes in BSC3i 1000/2000 and Flexi BSC has been added.

In chapter Creating the A interface, instructions for using ETIP plug-in unit has been added.

Chapter Synchronising the A interface has been slightly modified.

Changes made between issues 19-2 and 19-1In chapter Creating the A interface, section Creating the SCCP, more information on using segmentation was added.

Changes made between issues 19-1 and 19-0Chapter Initialising base stations: added information on Flexi EDGE Base Station auto-matic unlock.

8 DN9812243

BSS Integration

Id:0900d8058086ac4fConfidential

Overview of BSS integration

1 Overview of BSS integrationBSS integration instructions are intended to be used during the integration of the TCSM-BSC-BTS system in the final location.

The BSS integration testing can be started when the commissioning of the different network elements has been done.

The purpose of the BSS integration tests is to ensure that the BSC, TCSM, and BTS operate correctly together in the GSM/GPRS/EDGE network. When the BSS integration tests have been performed, the base station subsystem can be taken into use.

There are different product variants of the Base Station Controller: BSCi, BSC2i, BSC3i660, BSC3i 1000, BSC3i 2000, Flexi BSC and mcBSC. Flexi BSC has two vari-ants: upgraded Flexi BSC and new delivery Flexi BSC.

In the Flexi BSC, new HW elements CP1D-A ( New processor unit with multicore capa-bility), ETP(Exchange Terminal for Packet Transmission for Packet Abis over TDM and Packet Abis over Ethernet) and ETP-A (Packet gateway for AoIP) are introduced to support 4200 TRX, Packet Abis over ETH or TDM and Packet gateway for AoIP.

There are ETIP1-A plug in unit and ESB24-D plug-in unit. The ETIP1-A plug in unit provides one active and one protecting Gigabit Ethernet interface. The ETIP1-A is rep-resented by two functional units: Exchange terminal for IP transmission unit ETIP and Ethernet Exchange Terminal unit (EET). The EET represents a functional unit of a physical GigE Ethernet interface.

The ESB24-D plug-in unit is used with Ethernet based Message Bus (EMB) as a collec-tor of EMB LANs from the CPU units in both new delivery and upgraded Flexi BSC. ESB24-D can also be used as a generic LAN switch in the new delivery Flexi BSC.

The mcBSC (Multicontroller BSC) can be used in two ways. It can be used as a totally new BSC option for new installations with standalone multicontroller BSC modules.

Thesecond one is - capacity can be flexibly extended for the existing installed Flexi BSC base using the new HW module implementation of the Multicontroller. In this case, mcBSC enables the evolution of installed Flexi BSCs towards multicontroller capability.

Transcoding functionality is usually performed in a separate standalone network element (TCSM2/TCSM3i/mcTC), and the interface between the Base Station Control ler (BSC) and the transcoder (TC) is called Ater. As an alternative to standalone 2G transcoders MGW offers the Ater interface (2G transcoder) functionality. Thus transcod ing can be performed also by the transcoder located in the Multimedia Gateway (MGW).In creation of the Ater connection to the Multimedia Gateway, no configuration or controlling the TCSM is needed. The TCSM and the transcoder in the MGW are con figured differently in the BSC. For information, see Multimedia Gateway Product Docu mentation. The mcTC is used as a transcoding solution for standalone and combined mcBSC cases. TCSM2 and TCSM3i can be used in parallel with mcTC in combined mcBSC. Combined BSC/TCSM installation is also supported here.

As a part of capacity upgrade for TCSM3i, IC209-A cabinet is used to allow the equip-ping of five full shelf wide transcoder cartridge. Cabling Cabinet is not equipped with E1 balanced interfaces if new Rear Cabling Modules are used. TC1C-A is the new cartridge for TCSM3i and ETP-A is the new Exchange Terminal for Packet Transport. The capacity in one S15 standalone TCSM3i cabinet is 14400 channels.The capacity of one S15 combined TCSM3i cabinet in full configuration is 16800 channels, but 16320 channels is the maximum capacity reached, due to the channel sales configuration step.

DN9812243 9

BSS Integration Overview of BSS integration

Id:0900d8058086ac4fConfidential

Creating a connection to the network management system for BSC2i and BSC3i is described in the following documents:

• Integrating 2GBSS to NetAct in NetAct documentation

Creating a connection to the SGSN is described in SGSN Integration in SGSN docu-mentation. Creating the connection in BSC is described in Enabling GPRS in BSC in BSC documentation.

Creating a connection to the Cell Broadcast Centre is described in BSC-CBC Integration in BSC documentation.

Creating TCP/IP connections through LAN switches for BSC3i is described in BSC Site IP Connectivity Guidelines in BSC documentation.

For more information on the effects due to mcBSC, please check BSS21341: A over IP and BSS21454: Packet Abis over Ethernet in BSC documentation.

Any detected fault should be reported with a Nokia problem report and the report should be sent to the Customer Service Centre.

BSS integration procedureThe main phases of the testing are executed in the order presented here. BSS integra-tion consists of the following phases:

1. Creating the A interface2. Synchronising the A interface3. Adding DN2, SSS, DMR and BBM to the service channel4. Creating the Abis interface5. Creating X.25 or LAN connections. See Integrating 2GBSS to NetAct in NetAct doc-

umentation (for BSC2i and BSC3i).6. Initialising base stations7. Testing BSS integration

Test logs can be filled in during the testing.

For more information on BSS integration, see also:

• A interface protocol layers • A interface configuration with TCSM2 and TCSM3i • ET indexes in BSC3i, BSC2i and BSCi

10 DN9812243

BSS Integration

Id:0900d805805ceddcConfidential

A interface protocol layers

2 A interface protocol layersIn the ETSI environment, the A interface is defined in accordance with CCITT#7 Signal-ling System. In the ANSI environment, the A interface is defined in accordance with ANSI SS7 Signalling System. Three protocol layers are used: the Message Transfer Part (MTP), the Signalling Connection Control Part (SCCP), and the BSS Application Part (BSSAP; with ETSI) or the Radio System Application Part (RSAP; with ANSI), as shown in the figure below.

Figure 1 Three layers of CCS7/SS7 signalling between MSC and BSC

The MTP's task is to provide a reliable means of data transmission. It consists of a sig-nalling link, a signalling link set, and a signalling route set.

The SCCP complements the services of the MTP by providing connectionless and con-nection-oriented network services. It consists of SCCP subsystems.

The BSSAP/RSAP uses the services of the MTP and the SCCP. It takes care of actual GSM/DCS-related interaction between the MSC and the BSS. Typical tasks of the BSSAP/RSAP are for example call control, location updates, handover management, and paging. It has no counterparts in terms of BSC MMI but is created along with the SCCP.

For an overview, see Overview of BSS integration.

MSC BSCTCSM

BSSAP / RSAP

MTP

SCCP

MTP

SCCP

BSSAP / RSAP

Signalling linksthrough connected

DN9812243 11

BSS Integration A interface configuration with TCSM2 and TCSM3i

Id:0900d805805ceddfConfidential

3 A interface configuration with TCSM2 and TCSM3iThe A interface configuration can be made in many different ways depending on the equipment, or capacity and redundancy requirements. For example, the transcoder can be either TCSM2 or TCSM3i. Likewise, it is possible to implement only one PCM, E1 (used in ETSI environment), or T1 (used in ANSI environment) line between the MSC and the BSC or to use several separate PCM lines for redundancy or capacity purposes. The following figure illustrates an A interface configuration example.

With both TCSM2 and TCSM3i, the A interface is always multiplexed.

Figure 2 A interface configuration example

Signalling can also be performed using IETF signalling transmission (SIGTRAN). For more information, see SIGTRAN Configuration for the A Interface.

Multipoint A Interface enables one BSC to be connected to several core network elements (MSCs or MSC Servers). Even though one core network element fails, the network can stay operational with reduced capacity. For more information, see Multi-point A Interface in BSC.

TCSM3i for combined BSC/TCSM installationIn combined BSC/TCSM installation, no E1 or T1 interfaces are used as Ater interfaces between the BSC and TCSM3i. Instead, internal serial broadband interfaces (SBI) or Hotlinks are used. STM-1/OC-3 or IP/Ethernet (GigE) interfaces are used as external A interfaces.

MSC

TCSM3iEQUIPMENT

TCSMunit

Aterinterface

Ainterface

TCSMunit

DN0626652

0

0

1

2

3

4

1

2

3

4

BSC

E1/T1or

STM-1/OC-3or

IP/EthernetMSC

MSCMSC

E1/T1or

IP/Ethernetor

Int. PCM

E1/T1or

STM-1/OC-3or

IP/Ethernet

E1/T1or

IP/Ethernetor

Int. PCM

12 DN9812243

BSS Integration


A interface configuration with TCSM2 and TCSM3i

In TCSM3i for combined BSC/TCSM installation with a Flexi BSC, a mixed ETS2 and ETIP1-A configuration (STMU and SET, and ETIP and EET units) is possible in A-inter-faces.

TCSM3i

The TCSM3i uses an allocation with 16 kbit/s traffic channels for the use of HR speech, FR speech, EFR speech, AMR (FR and HR) speech traffic, and FR data traffic. An example is shown in the table below.

Circuit type

Supported channels and speech coding algo-rithms

Capacity unit on Ater interface

G HR speech, FR speech, EFR speech, AMR-FR speech, AMR-HR speech, or AMR-WB speech

FR data traffic

16 kbit/s

H HR speech, FR speech, EFR speech, AMR-FR speech, AMR-HR speech, or AMR-WB speech

FR data traffic

HSCSD max 2* FR data traffic

32 kbit/s

I HR speech, FR speech, EFR speech, AMR-FR speech, AMR-HR speech, or AMR-WB speech

FR data traffic

HSCSD max 4* FR data traffic

64 kbit/s

Table 1 Circuit types supported by the TCSM3i

Bits

TS 1 2 3 4 5 6 7 8

01 LAPD 2 3 4

02 5 6 7 8 Channels of:

03 9 10 11 12 PCM1

04 13 14 15 16

05 17 18 19 20

06 21 22 23 24

07 1 2 3 4


09 9 10 11 12 PCM2

10 13 14 15 16

11 17 18 19 20

12 21 22 23 24

13 1 2 3 4

Table 2 Allocation of different channels on the Ater-interface in the case of 16 kbit/s TRAU frame submulti-plexing (circuit type G)

DN9812243 13



The basic requirement for high-speed circuit-switched data (HSCSD) data transmission capability is that the associated BSC is equipped with an 8 kbit/s switching network or Bit Group Switch. Channel allocations for TCSM3i configured to transmit the data exclu-sively at the maximum rate of 32 kbit/s (type H) and 64 kbit/s (type I) are shown in the following tables. The same allocations accept also speech channels (FR/EFR, HR) instead of data, allowing an optimised use of transmission capacity for mixed speech/data use. The capacity unit reserved for an HSCSD connection on the A-inter-face is:

• 8–32 kbit/s (4 bits of a timeslot) for a 2 × 16 kbit/s channel • 8–64 kbit/s (an entire timeslot) for a 4 × 16 kbit/s channel


15 9 10 11 12 PCM3

16 13 14 15 16

17 17 18 19 20

18 21 22 23 24

19 1 2 3 4


21 9 10 11 12 PCM4

22 13 14 15 16

23 17 18 19 20

24 21 22 23 24

F

Table 2 Allocation of different channels on the Ater-interface in the case of 16 kbit/s TRAU frame submulti-plexing (circuit type G) (Cont.)

Bits

TS 1 2 3 4 5 6 7 8

00 TS 0

01 LAPD - 2

02 3 4

03 5 6

04 7 8

05 9 10 Channels of:

06 11 12 PCM1

07 13 14

08 15 16

09 17 18

10 19 20

11 21 22

Table 3 Channel allocation for circuit type H on the Ater-interface

14 DN9812243

BSS Integration



12 23 24

13 1 2

14 3 4

15 5 6

16 7 8

17 9 10 Channels of:

18 11 12 PCM2

19 13 14

20 15 16

21 17 18

22 19 20

23 21 22

24 23 24

F

Bits

TS 1 2 3 4 5 6 7 8

00 TS 0

01 LAPD -

02 2

03 3

04 4

05 5

06 6

07 7

08 8

09 9

10 10

11 11 Channels of:

12 12 PCM1

13 13

14 14

15 15

16 16

17 17

18 18

Table 4 Channel allocation for circuit type I on the Ater-interface

Table 3 Channel allocation for circuit type H on the Ater-interface (Cont.)

DN9812243 15



TCSM2, ETSIProvided that the BSC is equipped with an 8 Kbit group switch (GSWB), four separate A interface lines can be put into one highway PCM, making it possible to have up to 120 full-rate speech channels in one highway PCM cable. In half-rate configuration the maximum number of speech channels is 210. The combination of half-rate and full-rate can also be used.

The maximum efficiency is achieved if the recommendation for time slot allocation is followed (shown in the figure Time slot allocation for full-rate traffic on Ater 2 Mbit/s inter-face with the TCSM2 (ETSI)).

Signalling channels, and possibly network management system connections, are always allocated beginning from the end of the frame. This optimises the number of the traffic channels available for the fourth tributary. This is due to the fact that only the time slots preceding the first signalling time slot can be used as speech channels in the fourth tributary.

For example, if signalling links are allocated to time slots 31 and 27, only the time slots 25 and 26 are available for the fourth tributary - even if time slots 30, 29, and 28 are not used at all.

19 19

20 20

21 21

22 22

23 23

24 24

F

Table 4 Channel allocation for circuit type I on the Ater-interface (Cont.)

16 DN9812243

BSS Integration



Figure 3 Time slot allocation for full-rate traffic on Ater 2 Mbit/s interface with the TCSM2 (ETSI)

TCSM2, ANSIBecause of multiplexing, four A interface T1s can be put to one highway T1, making it possible to have up to 96 traffic channels between the transcoder and the BSC as shown in figure A interface time slot allocation (ANSI). However, one channel is required for the LAPD channel and normally one 64 kbit time slot is used for SS7 signalling. This leaves 91 channels for traffic.

BIT->

TS-> LINK MANAGEMENT0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

LAPD

TCH.4

TCH.8

TCH.12

TCH.16

TCH.20

TCH.24

TCH.28

x

TCH.4

TCH.8

TCH.12

TCH.16

TCH.20

TCH.24

TCH.28

x

TCH.4

TCH.8

TCH.12

TCH.16

TCH.20

TCH.24

TCH.28

TCH.1

TCH.5

TCH.9

TCH.13

TCH.17

TCH.21

TCH.25

TCH.29

TCH.1

TCH.5

TCH.9

TCH.13

TCH.17

TCH.21

TCH.25

TCH.29

TCH.1

TCH.5

TCH.9

TCH.13

TCH.17

TCH.21

TCH.25

TCH.29

TCH.2

TCH.6

TCH.10

TCH.14

TCH.18

TCH.22

TCH.26

TCH.30

TCH.2

TCH.6

TCH.10

TCH.14

TCH.18

TCH.22

TCH.26

TCH.30

TCH.2

TCH.6

TCH.10

TCH.14

TCH.18

TCH.22

TCH.26

TCH.30

TCH.3

TCH.7

TCH.11

TCH.15

TCH.19

TCH.23

TCH.27

TCH.31

TCH.3

TCH.7

TCH.11

TCH.15

TCH.19

TCH.23

TCH.27

TCH.31

TCH.3

TCH.7

TCH.11

TCH.15

TCH.19

TCH.23

TCH.27

TCH.31

A-PCM 1

A-PCM 2

A-PCM 3

(A-PCM 4)AUX1: selectable (TCH.1-3)

AUX2: selectable (TCH.4-7)



#7 signalling (TCH.16-19)



1 2 3 6 84 5 7

DN9812243 17



Figure 4 A interface time slot allocation (ANSI)


Trunk 3 1 2 3 4 5 6 7 8

TS 1 TCH 1TS 2 TCH 2TS 3 TCH 3TS 4 TCH 4TS 5 TCH 5TS 6 TCH 6TS 7 TCH 7TS 8 TCH 8TS 9 TCH 9TS 10 TCH 10TS 11 TCH 11TS 12 TCH 12TS 13 TCH 13TS 14 TCH 14TS 15 TCH 15TS 16 TCH 16TS 17 TCH 17TS 18 TCH 18TS 19 TCH 19TS 20 TCH 20TS 21 TCH 21TS 22 TCH 22TS 23 TCH 23TS 24 TCH 24

Trunk 2 1 2 3 4 5 6 7 8

TS 1 TCH 1TS 2 TCH 2TS 3 TCH 3TS 4 TCH 4TS 5 TCH 5TS 6 TCH 6TS 7 TCH 7TS 8 TCH 8TS 9 TCH 9TS 10 TCH 10TS 11 TCH 11TS 12 TCH 12TS 13 TCH 13TS 14 TCH 14TS 15 TCH 15TS 16 TCH 16TS 17 TCH 17TS 18 TCH 18TS 19 TCH 19TS 20 TCH 20TS 21 TCH 21TS 22 TCH 22TS 23 TCH 23TS 24 TCH 24

Trunk 4 1 2 3 4 5 6 7 8TS 1 TCH 1TS 2 TCH 2TS 3 TCH 3TS 4 TCH 4TS 5 TCH 5TS 6 TCH 6TS 7 TCH 7TS 8 TCH 8TS 9 TCH 9TS 10 TCH 10TS 11 TCH 11TS 12 TCH 12TS 13 TCH 13TS 14 TCH 14TS 15 TCH 15TS 16 TCH 16TS 17 TCH 17TS 18 TCH 18TS 19 TCH 19TS 20 TCH 20TS 21TS 22TS 23TS 24 SS7

23 TCHs

24 TCHs

24 TCHs

20 TCHs

1 2 3 4 5 6 7 8

TS 1 LAPD TCH 2 TCH 3 TCH 4 Trunk 1

TS 2 TCH 5 TCH 6 TCH 7 TCH 8





TS 7 TCH 1 TCH 2 TCH 3 TCH 4 Trunk 2

















TS 24 SS7

Trunk 1 1 2 3 4 5 6 7 8

TS 1TS 2 TCH 2TS 3 TCH 3TS 4 TCH 4TS 5 TCH 5TS 6 TCH 6TS 7 TCH 7TS 8 TCH 8TS 9 TCH 9TS 10 TCH 10TS 11 TCH 11TS 12 TCH 12TS 13 TCH 13TS 14 TCH 14TS 15 TCH 15TS 16 TCH 16TS 17 TCH 17TS 18 TCH 18TS 19 TCH 19TS 20 TCH 20TS 21 TCH 21TS 22 TCH 22TS 23 TCH 23TS 24 TCH 24

Highway T1(to BSC)

A Interface(to MSC)

TCSM2

18 DN9812243

BSS Integration

Id:0900d80580820876Confidential

ET indexes in BSC

4 ET indexes in BSCIn new delivery Flexi BSC both STM-1/OC-3 interfaces (optical) and IP/Ethernet (GigE) interfaces (optical or electrical) are supported in the whole cabinet wide cartridge mechanics together with E1/T1 interfaces. Cartridge mechanics is divided to sub car-tridges, which are used same way as smaller cartridges in earlier delivered BSCs. In upgraded Flexi BSC one-cabinet configuration is supported with full range (16+16) of STM-1/OC-3 interfaces and IP/Ethernet (8 + 8 GigE) interfaces. In the upgraded Flexi BSC it is possible to extend the configuration with a second cabinet also to full support for 800 E1/T1 interfaces to earlier delivered BSCs.

The Exchange Terminals (ETs) of the BSC3i 1000/2000 and the upgraded Flexi BSC are housed in GT6C-A and/or GT4C-A cartridges. One GT4C-A cartridge can contain up to eight ET plug-in units and a GT6C-A cartridge can contain up to four ET plug-in units. ET16 plug-in units can be installed to six ET cartridges with indexes ETC 0 to ETC 5 in BSC3i 2000. Additionally, ET16 units can also be equipped to GTIC cartridges to achieve a maximum of 800 E1/T1 interfaces amount in the two-cabinet configuration and 384 E1/T1 interface amount in the one-cabinet configuration.

The ET16 and ETIP1-A units are installed to GTIC cartridge starting from the right in mixed ET16 or ETIP1-A and ETS2 equipping. In the incoming direction, the ET decodes the 2048 Mbit/s in European Telecommunications Standards Institute (ETSI) signal or 1544 Mbit/s American National Standards Institute (ANSI) signal of a circuit into data signals.

In the outgoing direction, the ET receives a binary PCM signal from the switching network and generates the PCM frame structure. The resulting signal is converted into a line code (HDB3 in the ETSI environment, B8ZS or AMI in the ANSI environment) and transmitted further onto the 2048 Mbit/s (ETSI) or 1544 Mbit/s (ANSI) circuit.

The ETS2 plug-in unit contains up to two active and two redundant optical STM-1/OC-3 interfaces. All optical components have 2N redundancy for transmission protection. A maximum of 16 active optical interface can be achieved with 8 plug-in units, if two active interface per unit is used or with 16 plug-in units if one active interface is used per unit.

The ETS2 units are equipped to GTIC cartridges in the first equipment cabinet. The GTIC cartridges can also be used for E1/T1 connectivity with ET16 units. The ETS2 unit is responsible for framing, mapping, and multiplexing of PCMs into channelised way in optical interfaces (VC12). One STM-1 interface consists of 63 E1s (ETSI) and one OC-3 interface consists of 84 T1s (ANSI). PCMs are handled in the same way as ETs in the ET16 plug-in unit.

Equipment protection for ETS2 (MSP 1 + 1 protective units) is provided if two STMU units (functional units for ETS2) are configured with consecutive indexes. For example, STMU-0 and STMU-1 comprise a pair of STMUs.

Integrated E1/T1 over IP application software offers an integrated solution for BSC3i and TCSM3i based transcoders to send/receive TDM frame timeslots via a packet-switched network. Integrated E1/T1 over IP is based on the circuit emulation service over packet-switched networks (CESoPSN) technology and it is implemented in the ETIP1-A plug-in unit. The ETIP1-A can be equipped to the ETS2 and ET16 cartridges to replace the E1/T1 or STM-1/OC-3 unit. This improves the BSC connectivity. The operator has more alternatives to select transmission technology in different interfaces of the BSC environment. The ETIP-A plug-in unit can be used in the Abis and Ater inter-faces in the BSC3i and in the A and Ater interfaces in TCSM3i based transcoders. The

DN9812243 19

BSS Integration ET indexes in BSC


capacity of one ETIP1-A plug-in unit in the BSC3i environment is 126 E1 PCMs or 168 T1 PCMs.

ETC cartridge Slot ETs

ETC 0 01 512-527

02 528-543

03 544-559

04 560-575

ETC 1 01 576-591

02 592-607

03 608-623

04 624-639

ETC 2 01 1344-1359

02 1360-1375

03 1376-1391

04 1392-1407

05 1600-1615

06 1616-1631

07 1632-1647

08 1648-1663

ETC 3 01 1664-1679

02 1680-1695

03 1696-1711

04 1712-1727

05 1728-1743

06 1744-1759

07 1760-1775

08 1776-1791

ETC 4 01 1920-1935

02 1936-1951

03 1952-1967

04 1968-1983

05 1984-1999

06 2000-2015

07 2016-2031

08 2032-2047

ETC 5 01 1280-1295

02 1296-1311

Table 5 ET indexes in BSC3i 1000/2000

20 DN9812243

BSS Integration


ET indexes in BSC

Slot STM-1 inter-face of ETS2

Optical inter-face

STMU index

ET numbers (ETSI)

Control PCM (TSLs)

GTIC 0

01 0 0 0 64-126 640 (0-15)

0 1 0 64-126 640 (0-15)

1 0 0 192-254 640 (0-15)

1 1 0 192-254 640 (0-15)

02 0 0 2 320-382 640 (16-31)

0 1 2 320-382 640 (16-31)

1 0 2 448-510 640 (16-31)

1 1 2 448-510 640 (16-31)

03 0 0 4 1088-1150 641 (0-15)

0 1 4 1088-1150 641 (0-15)

1 0 4 1216-1278 641 (0-15)

1 1 4 1216-1278 641 (0-15)

04 0 0 6 1408-1470 641 (16-31)

0 1 6 1408-1470 641 (16-31)

1 0 6 1472-1534 641 (16-31)

1 1 6 1472-1534 641 (16-31)

GTIC1

01 0 0 16 1344-1406 896 (0-15)

0 1 16 1344-1406 896 (0-15)

1 0 16 1600-1662 896 (0-15)

1 1 16 1600-1662 896 (0-15)

02 0 0 18 1664-1726 896 (16-31)

0 1 18 1664-1726 896 (16-31)

1 0 18 1728-1790 896 (16-31)

1 1 18 1728-1790 896 (16-31)

03 0 0 20 1792-1854 897 (0-15)

0 1 20 1792-1854 897 (0-15)

1 0 20 1856-1918 897 (0-15)

1 1 20 1856-1918 897 (0-15)

Table 6 ET indexes in BSC3i 1000/2000 (ETSI ETS2, two active and two standby STM-1)

DN9812243 21



04 0 0 22 1920-1982 897 (16-31)

0 1 22 1920-1982 897 (16-31)

1 0 22 1984-2046 897 (16-31)

1 1 22 1984-2046 897 (16-31)


Optical inter-face

STMU index

ET numbers (ETSI)

Control PCM (TSLs)

GTIC 0

01 0 0 0 64-126 640 (0-15)

0 1 0 64-126 640 (0-15)

02 0 0 2 192-254 640 (16-31)

0 1 2 192-254 640 (16-31)

03 0 0 4 320-382 641 (0-15)

0 1 4 320-382 641 (0-15)

04 0 0 6 448-510 641 (16-31)

0 1 6 448-510 641 (16-31)

05 0 0 8 1088-1150 642 (0-15)

0 1 8 1088-1150 642 (0-15)

06 0 0 10 1216-1278 642 (16-31)

0 1 10 1216-1278 642 (16-31)

07 0 0 12 1408-1470 643 (0-15)

0 1 12 1408-1470 643 (0-15)

08 0 0 14 1472-1534 643 (16-31)

0 1 14 1472-1534 643 (16-31)

GTIC1

01 0 0 16 1344-1406 896 (0-15)

0 1 16 1344-1406 896 (0-15)

02 0 0 18 1600-1662 896 (16-31)

0 1 18 1600-1662 896 (16-31)

Table 7 ET indexes in BSC3i 1000/2000 (ETSI ETS2, one active and one standby STM-1)


Optical inter-face

STMU index

ET numbers (ETSI)

Control PCM (TSLs)

Table 6 ET indexes in BSC3i 1000/2000 (ETSI ETS2, two active and two standby STM-1) (Cont.)

22 DN9812243

BSS Integration


ET indexes in BSC

03 0 0 20 1664-1726 897 (0-15)

0 1 20 1664-1726 897 (0-15)

04 0 0 22 1728-1790 897 (16-31)

0 1 22 1728-1790 897 (16-31)

05 0 0 24 1792-1854 898 (0-15)

0 1 24 1792-1854 898 (0-15)

06 0 0 26 1856-1918 898 (16-31)

0 1 26 1856-1918 898 (16-31)

07 0 0 28 1920-1982 899 (0-15)

0 1 28 1920-1982 899 (0-15)

08 0 0 30 1984-2046 899 (16-31)

0 1 30 1984-2046 899 (16-31)

Slot OC-3 inter-face of ETS2

Optical inter-face

STMU index

ET numbers (ANSI)

Control PCM (TSLs)

GTIC 0

01 0 0 0 2048-2131 640 (0-15)

0 1 0 2048-2131 640 (0-15)

1 0 0 2132-2215 640 (0-15)

1 1 0 2132-2215 640 (0-15)

02 0 0 2 2216-2299 640 (16-31)

0 1 2 2216-2299 640 (16-31)

1 0 2 2300-2383 640 (16-31)

1 1 2 2300-2383 640 (16-31)

03 0 0 4 2384-2467 641 (0-15)

0 1 4 2384-2467 641 (0-15)

1 0 4 2468-2551 641 (0-15)

1 1 4 2468-2551 641 (0-15)

Table 8 ET indexes in BSC3i 1000/2000 (ANSI ETS2, two active and two standby OC-3)


Optical inter-face

STMU index

ET numbers (ETSI)

Control PCM (TSLs)

Table 7 ET indexes in BSC3i 1000/2000 (ETSI ETS2, one active and one standby STM-1) (Cont.)

DN9812243 23



04 0 0 6 2552-2635 641 (16-31)

0 1 6 2552-2635 641 (16-31)

1 0 6 2636-2719 641 (16-31)

1 1 6 2636-2719 641 (16-31)

GTIC1

01 0 0 16 2720-2803 896 (0-15)

0 1 16 2720-2803 896 (0-15)

1 0 16 2804-2887 896 (0-15)

1 1 16 2804-2887 896 (0-15)

02 0 0 18 2888-2971 896 (16-31)

0 1 18 2888-2971 896 (16-31)

1 0 18 2972-3055 896 (16-31)

1 1 18 2972-3055 896 (16-31)

03 0 0 20 3056-3139 897 (0-15)

0 1 20 3056-3139 897 (0-15)

1 0 20 3140-3223 897 (0-15)

1 1 20 3140-3223 897 (0-15)

04 0 0 22 3224-3307 897 (16-31)

0 1 22 3224-3307 897 (16-31)

1 0 22 3308-3391 897 (16-31)

1 1 22 3308-3391 897 (16-31)


Optical inter-face

STMU index

ET numbers (ANSI)

Control PCM (TSLs)

GTIC 0

01 0 0 0 2048-2131 640 (0-15)

0 1 0 2048-2131 640 (0-15)

02 0 0 2 2132-2215 640 (16-31)

0 1 2 2132-2215 640 (16-31)

Table 9 ET indexes in BSC3i 1000/2000 (ANSI ETS2, one active and one standby OC-3)


Optical inter-face

STMU index

ET numbers (ANSI)

Control PCM (TSLs)

Table 8 ET indexes in BSC3i 1000/2000 (ANSI ETS2, two active and two standby OC-3) (Cont.)

24 DN9812243

BSS Integration


ET indexes in BSC

03 0 0 4 2216-2299 641 (0-15)

0 1 4 2216-2299 641 (0-15)

04 0 0 6 2300-2383 641 (16-31)

0 1 6 2300-2383 641 (16-31)

05 0 0 8 2384-2467 642 (0-15)

0 1 8 2384-2467 642 (0-15)

06 0 0 10 2468-2551 642 (16-31)

0 1 10 2468-2551 642 (16-31)

07 0 0 12 2552-2635 643 (0-15)

0 1 12 2552-2635 643 (0-15)

08 0 0 14 2636-2719 643 (16-31)

0 1 14 2636-2719 643 (16-31)

GTIC1

01 0 0 16 2720-2803 896 (0-15)

0 1 16 2720-2803 896 (0-15)

02 0 0 18 2804-2887 896 (16-31)

0 1 18 2804-2887 896 (16-31)

03 0 0 20 2888-2971 897 (0-15)

0 1 20 2888-2971 897 (0-15)

04 0 0 22 2972-3055 897 (16-31)

0 1 22 2972-3055 897 (16-31)

05 0 0 24 3056-3139 898 (0-15)

0 1 24 3056-3139 898 (0-15)

06 0 0 26 3140-3223 898 (16-31)

0 1 26 3140-3223 898 (16-31)

07 0 0 28 3224-3307 899 (0-15)

0 1 28 3224-3307 899 (0-15)

08 0 0 30 3308-3391 899 (16-31)

0 1 30 3308-3391 899 (16-31)


Optical inter-face

STMU index

ET numbers (ANSI)

Control PCM (TSLs)

Table 9 ET indexes in BSC3i 1000/2000 (ANSI ETS2, one active and one standby OC-3) (Cont.)

DN9812243 25



Slot GbE interface

ETIP index

EET number

ET numbers (ETSI)

ET numbers (ANSI)

Control PCM (TSLs)

GTIC 0

01 0 0 0 64-126

192-254

2048-2131

2132-2215

640 (0-3)

1 0 1 64-126

192-254

2048-2131

2132-2215

640 (0-3)

02 0 2 4 320-382

448-510

2216-2299

2300-2383

640 (16-19)

1 2 5 320-382

448-510

2216-2299

2300-2383

640 (16-19)

03 0 4 8 1088-1150

1216-1278

2384-2467

2468-2551

641 (0-3)

1 4 9 1088-1150

1216-1278

2384-2467

2468-2551

641 (0-3)

04 0 6 12 1408-1470

1472-1534

2552-2635

2636-2719

641 (16-19)

1 6 13 1408-1470

1472-1534

2552-2635

2636-2719

641 (16-19)

GTIC1

01 0 16 32 1344-1406

1600-1662

2720-2803

2804-2887

896 (0-3)

1 16 33 1344-1406

1600-1662

2720-2803

2804-2887

896 (0-3)

02 0 18 36 1664-1726

1728-1790

2888-2971

2972-3055

896 (16-19)

1 18 37 1664-1726

1728-1790

2888-2971

2972-3055

896 (16-19)

03 0 20 40 1792-1854

1856-1918

3056-3139

3140-3223

897 (0-3)

1 20 41 1792-1854

1856-1918

3056-3139

3140-3223

897 (0-3)

04 0 22 44 1920-1982

1984-2046

3224-3307

3308-3391

897 (16-19)

1 22 45 1920-1982

1984-2046

3224-3307

3308-3391

897 (16-19)

Table 10 ETIP and ET indexes in BSC3i 1000/2000 when transmission redundancy is in use

26 DN9812243

BSS Integration


ET indexes in BSC

Slot GbE interface

ETIP index

EET number

ET numbers (ETSI)

ET numbers (ANSI)

Control PCM (TSLs)

GTIC 0

01 0 0 0 64-126

192-254

2048-2131

2132-2215

640 (0-3)

02 0 2 4 320-382

448-510

2216-2299

2300-2383

640 (16-19)

03 0 4 8 1088-1150

1216-1278

2384-2467

2468-2551

641 (0-3)

04 0 6 12 1408-1470

1472-1534

2552-2635

2636-2719

641 (16-19)

05 0 9 18 1344-1406

1600-1662

2720-2803

2804-2887

642 (0-3)

06 0 11 22 1664-1726

1728-1790

2888-2971

2972-3055

642 (16-19)

07 0 13 26 1792-1854

1856-1918

3056-3139

3140-3223

643 (0-3)

08 0 15 30 1920-1982

1984-2046

3224-3307

3308-3391

643 (16-19)

GTIC1

01 0 1 2 64-126

192-254

2048-2131

2132-2215

896 (0-3)

02 0 3 6 320-382

448-510

2216-2299

2300-2383

896 (16-19)

03 0 5 10 1088-1150

1216-1278

2384-2467

2468-2551

897 (0-3)

04 0 7 14 1408-1470

1472-1534

2552-2635

2636-2719

897 (16-19)

05 0 8 16 1344-1406

1600-1662

2720-2803

2804-2887

898 (0-3)

06 0 10 20 1664-1726

1728-1790

2888-2971

2972-3055

898 (16-19)

07 0 12 24 1792-1854

1856-1918

3056-3139

3140-3223

899 (0-3)

08 0 14 28 1920-1982

1984-2046

3224-3307

3308-3391

899 (16-19)

Table 11 ETIP and ET indexes in BSC3i 1000/2000 when HW redundancy is in use

DN9812243 27



Slot GbE interface

ETIP index

EET number

ET numbers (ETSI)

ET numbers (ANSI)

Control PCM (TSLs)

GTIC 0

10 0 0 0 64-126

192-254

2048-2131

2132-2215

392 (0-3)

1 0 1 64-126

192-254

2048-2131

2132-2215

392 (0-3)

11 0 2 4 1536-1598

1600-1662

2216-2299

2300-2383

392 (16-19)

1 2 5 1536-1598

1600-1662

2216-2299

2300-2383

392 (16-19)

12 0 4 8 1792-1854

1856-1918

2384-2467

2468-2551

393 (0-3)

1 4 9 1792-1854

1856-1918

2384-2467

2468-2551

393 (0-3)

13 0 6 12 1280-1342

1344-1406

2552-2635

2636-2719

393 (16-19)

1 6 13 1280-1342

1344-1406

2552-2635

2636-2719

393 (16-19)

GTIC1

10 0 16 32 1920-1982

1984-2046

2720-2803

2804-2887

384 (0-3)

1 16 33 1920-1982

1984-2046

2720-2803

2804-2887

384 (0-3)

11 0 18 36 768-830

832-894

2888-2971

2972-3055

384 (16-19)

1 18 37 768-830

832-894

2888-2971

2972-3055

384 (16-19)

12 0 20 40 1024-1086

1088-1150

3056-3139

3140-3223

385 (0-3)

1 20 41 1024-1086

1088-1150

3056-3139

3140-3223

385 (0-3)

13 0 22 44 512-574

576-638

3224-3307

3308-3391

385 (16-19)

1 22 45 512-574

576-638

3224-3307

3308-3391

385 (16-19)

Table 12 ETIP and ET indexes in new delivery Flexi BSC when transmission redun-dancy is in use

28 DN9812243

BSS Integration


ET indexes in BSC

Slot GbE interface

ETIP index

EET number

ET numbers (ETSI)

ET numbers (ANSI)

Control PCM (TSLs)

GTIC 0

01 0 0 0 64-126

192-254

2048-2131

2132-2215

640 (0-3)

1 0 1 64-126

192-254

2048-2131

2132-2215

640 (0-3)

02 0 2 4 320-382

448-510

2216-2299

2300-2383

640 (16-19)

1 2 5 320-382

448-510

2216-2299

2300-2383

640 (16-19)

03 0 4 8 1088-1150

1216-1278

2384-2467

2468-2551

641 (0-3)

1 4 9 1088-1150

1216-1278

2384-2467

2468-2551

641 (0-3)

04 0 6 12 1408-1470

1472-1534

2552-2635

2636-2719

641 (16-19)

1 6 13 1408-1470

1472-1534

2552-2635

2636-2719

641 (16-19)

GTIC1

01 0 16 32 1344-1406

1600-1662

2720-2803

2804-2887

896 (0-3)

1 16 33 1344-1406

1600-1662

2720-2803

2804-2887

896 (0-3)

02 0 18 36 1664-1726

1728-1790

2888-2971

2972-3055

896 (16-19)

1 18 37 1664-1726

1728-1790

2888-2971

2972-3055

896 (16-19)

03 0 20 40 1792-1854

1856-1918

3056-3139

3140-3223

897 (0-3)

1 20 41 1792-1854

1856-1918

3056-3139

3140-3223

897 (0-3)

04 0 22 44 1920-1982

1984-2046

3224-3307

3308-3391

897 (16-19)

1 22 45 1920-1982

1984-2046

3224-3307

3308-3391

897 (16-19)

Table 13 ETIP and ET indexes in upgraded Flexi BSC when transmission redun-dancy is in use

DN9812243 29



Slot GbE interface

ETIP index

EET number

ET numbers (ETSI)

ET numbers (ANSI)

Control PCM (TSLs)

GTIC 0

10 0 0 0 64-126

192-254

2048-2131

2132-2215

392 (0-3)

11 0 2 4 1536-1598

1600-1662

2216-2299

2300-2383

392 (16-19)

12 0 4 8 1792-1854

1856-1918

2384-2467

2468-2551

393 (0-3)

13 0 6 12 1280-1342

1344-1406

2552-2635

2636-2719

393 (16-19)

14 0 9 18 1920-1982

1984-2046

2720-2803

2804-2887

394 (0-3)

15 0 11 22 768-830

832-894

2888-2971

2972-3055

394 (16-19)

16 0 13 26 1024-1086

1088-1150

3056-3139

3140-3223

395 (0-3)

17 0 15 30 512-574

576-638

3224-3307

3308-3391

395 (16-19)

GTIC1

10 0 1 2 64-126

192-254

2048-2131

2132-2215

384 (0-3)

11 0 3 6 1536-1598

1600-1662

2216-2299

2300-2383

384 (16-19)

12 0 5 10 1792-1854

1856-1918

2384-2467

2468-2551

385 (0-3)

13 0 7 14 1280-1342

1344-1406

2552-2635

2636-2719

385 (16-19)

14 0 8 16 1920-1982

1984-2046

2720-2803

2804-2887

386 (0-3)

15 0 10 20 768-830

832-894

2888-2971

2972-3055

386 (16-19)

16 0 12 24 1024-1086

1088-1150

3056-3139

3140-3223

387 (0-3)

17 0 14 28 512-574

576-638

3224-3307

3308-3391

387 (16-19)

Table 14 ETIP and ET indexes in new delivery Flexi BSC when HW redundancy is in use

30 DN9812243

BSS Integration


ET indexes in BSC

Slot GbE interface

ETIP index

EET number

ET numbers (ETSI)

ET numbers (ANSI)

Control PCM (TSLs)

GTIC 0

01 0 0 0 64-126

192-254

2048-2131

2132-2215

640 (0-3)

02 0 2 4 320-382

448-510

2216-2299

2300-2383

640 (16-19)

03 0 4 8 1088-1150

1216-1278

2384-2467

2468-2551

641 (0-3)

04 0 6 12 1408-1470

1472-1534

2552-2635

2636-2719

641 (16-19)

05 0 9 18 1344-1406

1600-1662

2720-2803

2804-2887

642 (0-3)

06 0 11 22 1664-1726

1728-1790

2888-2971

2972-3055

642 (16-19)

07 0 13 26 1792-1854

1856-1918

3056-3139

3140-3223

643 (0-3)

08 0 15 30 1920-1982

1984-2046

3224-3307

3308-3391

643 (16-19)

GTIC1

01 0 1 2 64-126

192-254

2048-2131

2132-2215

896 (0-3)

02 0 3 6 320-382

448-510

2216-2299

2300-2383

896 (16-19)

03 0 5 10 1088-1150

1216-1278

2384-2467

2468-2551

897 (0-3)

04 0 7 14 1408-1470

1472-1534

2552-2635

2636-2719

897 (16-19)

05 0 8 16 1344-1406

1600-1662

2720-2803

2804-2887

898 (0-3)

06 0 10 20 1664-1726

1728-1790

2888-2971

2972-3055

898 (16-19)

07 0 12 24 1792-1854

1856-1918

3056-3139

3140-3223

899 (0-3)

08 0 14 28 1920-1982

1984-2046

3224-3307

3308-3391

899 (16-19)

Table 15 ETIP and ET indexes in upgraded Flexi BSC when HW redundancy is in use

DN9812243 31



Slot STM-1/OC-3 inter-face of ETS2

Optical inter-face

STMU index

SET number ET numbers (ETSI)

ET numbers (ANSI)

Control PCM (TSLs)

GTIC 0

10 0 0 0 0 64-126 2048-2131 392 (0-15)

0 1 0 1 64-126 2048-2131 392 (0-15)

1 0 0 2 192-254 2132-2215 392 (0-15)

1 1 0 3 192-254 2132-2215 392 (0-15)

11 0 0 2 8 1536-1598 2216-2299 392 (16-31)

0 1 2 9 1536-1598 2216-2299 392 (16-31)

1 0 2 10 1600-1662 2300-2383 392 (16-31)

1 1 2 11 1600-1662 2300-2383 392 (16-31)

12 0 0 4 16 1792-1854 2384-2467 393 (0-15)

0 1 4 17 1792-1854 2384-2467 393 (0-15)

1 0 4 18 1856-1918 2468-2551 393 (0-15)

1 1 4 19 1856-1918 2468-2551 393 (0-15)

13 0 0 6 24 1280-1342 2552-2635 393 (16-31)

0 1 6 25 1280-1342 2552-2635 393 (16-31)

1 0 6 26 1344-1406 2636-2719 393 (16-31)

1 1 6 27 1344-1406 2636-2719 393 (16-31)

GTIC1

10 0 0 16 64 1920-1982 2720-2803 384 (0-15)

0 1 16 65 1920-1982 2720-2803 384 (0-15)

1 0 16 66 1984-2046 2804-2887 384 (0-15)

1 1 16 67 1984-2046 2804-2887 384 (0-15)

11 0 0 18 72 768-830 2888-2971 384 (16-31)

0 1 18 73 768-830 2888-2971 384 (16-31)

1 0 18 74 832-894 2972-3055 384 (16-31)

1 1 18 75 832-894 2972-3055 384 (16-31)

12 0 0 20 80 1024-1086 3056-3139 385 (0-15)

0 1 20 81 1024-1086 3056-3139 385 (0-15)

1 0 20 82 1088-1150 3140-3223 385 (0-15)

1 1 20 83 1088-1150 3140-3223 385 (0-15)

Table 16 ET indexes in new delivery Flexi BSC when transmission redundancy is in use

32 DN9812243

BSS Integration


ET indexes in BSC

13 0 0 22 88 512-574 3224-3307 385 (16-31)

0 1 22 89 512-574 3224-3307 385 (16-31)

1 0 22 90 576-638 3308-3391 385 (16-31)

1 1 22 91 576-638 3308-3391 385 (16-31)


Optical inter-face

STMU index


ET numbers (ANSI)

Control PCM (TSLs)

Table 16 ET indexes in new delivery Flexi BSC when transmission redundancy is in use (Cont.)


Optical inter-face

STMU index


ET numbers (ANSI)

Control PCM (TSLs)

GTIC 0

01 0 0 0 0 64-126 2048-2131 640 (0-3)

0 1 0 1 64-126 2048-2131 640 (0-3)

1 0 0 2 192-254 2132-2215 640 (0-3)

1 1 0 3 192-254 2132-2215 640 (0-3)

02 0 0 2 8 320-382 2216-2299 640 (16-19)

0 1 2 9 320-382 2216-2299 640 (16-19)

1 0 2 10 448-510 2300-2383 640 (16-19)

1 1 2 11 448-510 2300-2383 640 (16-19)

03 0 0 4 16 1088-1150 2384-2467 641 (0-3)

0 1 4 17 1088-1150 2384-2467 641 (0-3)

1 0 4 18 1216-1278 2468-2551 641 (0-3)

1 1 4 19 1216-1278 2468-2551 641 (0-3)

04 0 0 6 24 1408-1470 2552-2635 641 (16-19)

0 1 6 25 1408-1470 2552-2635 641 (16-19)

1 0 6 26 1472-1534 2636-2719 641 (16-19)

1 1 6 27 1472-1534 2636-2719 641 (16-19)

GTIC1

01 0 0 16 64 1344-1406 2720-2803 896 (0-3)

0 1 16 65 1344-1406 2720-2803 896 (0-3)

1 0 16 66 1600-1662 2804-2887 896 (0-3)

1 1 16 67 1600-1662 2804-2887 896 (0-3)

Table 17 ET indexes in upgraded Flexi BSC when transmission redundancy is in use

DN9812243 33



02 0 0 18 72 1664-1726 2888-2971 896 (16-19)

0 1 18 73 1664-1726 2888-2971 896 (16-19)

1 0 18 74 1728-1790 2972-3055 896 (16-19)

1 1 18 75 1728-1790 2972-3055 896 (16-19)

03 0 0 20 80 1792-1854 3056-3139 897 (0-3)

0 1 20 81 1792-1854 3056-3139 897 (0-3)

1 0 20 82 1856-1918 3140-3223 897 (0-3)

1 1 20 83 1856-1918 3140-3223 897 (0-3)

04 0 0 22 88 1920-1982 3224-3307 897 (16-19)

0 1 22 89 1920-1982 3224-3307 897 (16-19)

1 0 22 90 1984-2046 3308-3391 897 (16-19)

1 1 22 91 1984-2046 3308-3391 897 (16-19)


Optical inter-face

STMU index


ET numbers (ANSI)

Control PCM (TSLs)

Table 17 ET indexes in upgraded Flexi BSC when transmission redundancy is in use (Cont.)


Optical inter-face

STMU index


ET numbers (ANSI)

Control PCM (TSLs)

GTIC 0

10 0 0 0 0 64-126 2048-2131 392 (0-15)

1 0 0 2 192-254 2132-2215 392 (0-15)

11 0 0 2 8 1536-1598 2216-2299 392 (16-31)

1 0 2 10 1600-1662 2300-2383 392 (16-31)

12 0 0 4 16 1792-1854 2384-2467 393 (0-15)

1 0 4 18 1856-1918 2468-2551 393 (0-15)

13 0 0 6 24 1280-1342 2552-2635 393 (16-31)

1 0 6 26 1344-1406 2636-2719 393 (16-31)

14 0 0 9 36 1920-1982 2720-2803 394 (0-15)

1 0 9 38 1984-2046 2804-2887 394 (0-15)

15 0 0 11 44 768-830 2888-2971 394 (16-31)

1 0 11 46 832-894 2972-3055 394 (16-31)

16 0 0 13 52 1024-1086 3056-3139 395 (0-15)

1 0 13 54 1088-1150 3140-3223 395 (0-15)

Table 18 ET indexes in new delivery Flexi BSC cartridges when HW redundancy is in use

34 DN9812243

BSS Integration


ET indexes in BSC

17 0 0 15 60 512-574 3224-3307 395 (16-31)

1 0 15 62 576-638 3308-3391 395 (16-31)

GTIC1

10 0 0 1 4 64-126 2048-2131 384 (0-15)

1 0 1 6 192-254 2132-2215 384 (0-15)

11 0 0 3 12 1536-1598 2216-2299 384 (16-31)

10 0 3 14 1600-1662 2300-2383 384 (16-31)

12 0 0 5 20 1792-1854 2384-2467 385 (0-15)

1 0 5 22 1856-1918 2468-2551 385 (0-15)

13 0 0 7 28 1280-1342 2552-2635 385 (16-31)

1 0 7 30 1344-1406 2636-2719 385 (16-31)

14 0 0 8 32 1920-1982 2720-2803 386 (0-15)

1 0 8 34 1984-2046 2804-2887 386 (0-15)

15 0 0 10 40 768-830 2888-2971 386 (16-31)

1 0 10 42 832-894 2972-3055 386 (16-31)

16 0 0 12 48 1024-1086 3056-3139 387 (0-15)

1 0 12 50 1088-1150 3140-3223 387 (0-15)

17 0 0 14 56 512-574 3224-3307 387 (16-31)

1 0 14 58 576-638 3308-3391 387 (16-31)


Optical inter-face

STMU index


ET numbers (ANSI)

Control PCM (TSLs)

Table 18 ET indexes in new delivery Flexi BSC cartridges when HW redundancy is in use (Cont.)


Optical inter-face

STMU index


ET numbers (ANSI)

Control PCM (TSLs)

GTIC 0

01 0 0 0 0 64-126 2048-2131 640 (0-3)

1 0 0 2 192-254 2132-2215 640 (0-3)

02 0 0 2 8 320-382 2216-2299 640 (16-19)

1 0 2 10 448-510 2300-2383 640 (16-19)

03 0 0 4 16 1088-1150 2384-2467 641 (0-3)

1 0 4 18 1216-1278 2468-2551 641 (0-3)

Table 19 ET indexes in upgraded Flexi BSC cartridges when HW redundancy is in use

DN9812243 35



04 0 0 6 24 1408-1470 2552-2635 641 (16-19)

1 0 6 26 1472-1534 2636-2719 641 (16-19)

05 0 0 9 36 1344-1406 2720-2803 642 (0-3)

1 0 9 38 1600-1662 2804-2887 642 (0-3)

06 0 0 11 44 1664-1726 2888-2971 642 (16-19)

1 0 11 46 1728-1790 2972-3055 642 (16-19)

07 0 0 13 52 1792-1854 3056-3139 643 (0-3)

1 0 13 54 1856-1918 3140-3223 643 (0-3)

08 0 0 15 60 1920-1982 3224-3307 643 (16-19)

1 0 15 62 1984-2046 3308-3391 643 (16-19)

GTIC1

01 0 0 1 4 64-126 2048-2131 896 (0-3)

1 0 1 6 192-254 2132-2215 896 (0-3)

02 0 0 3 12 320-382 2216-2299 896 (16-19)

10 0 3 14 448-510 2300-2383 896 (16-19)

03 0 0 5 20 1088-1150 2384-2467 897 (0-3)

1 0 5 22 1216-1278 2468-2551 897 (0-3)

04 0 0 7 28 1408-1470 2552-2635 897 (16-19)

1 0 7 30 1472-1534 2636-2719 897 (16-19)

05 0 0 8 32 1344-1406 2720-2803 898 (0-3)

1 0 8 34 1600-1662 2804-2887 898 (0-3)

06 0 0 10 40 1664-1726 2888-2971 898 (16-19)

1 0 10 42 1728-1790 2972-3055 898 (16-19)

07 0 0 12 48 1792-1854 3056-3139 899 (0-3)

1 0 12 50 1856-1918 3140-3223 899 (0-3)

08 0 0 14 56 1920-1982 3224-3307 899 (16-19)

1 0 14 58 1984-2046 3308-3391 899 (16-19)


Optical inter-face

STMU index


ET numbers (ANSI)

Control PCM (TSLs)

Table 19 ET indexes in upgraded Flexi BSC cartridges when HW redundancy is in use (Cont.)

36 DN9812243

BSS Integration


ET indexes in BSC

Figure 5 ET cartridges in the BSCC cabinet of BSC3i 1000

PDFU PDFU

DN0671322

CPGO

BSCC

CPETx CPRJ45-A

FTRB 1FTRB 0

FTRB 3FTRB 2

5

4

3

2

1

00 6

FRONT VIEW

30

GS

W2

KB

0

GS

W2

KB

186

CLO

C

30

MCMU0

MCMU1

OMU

6

4 80

BCSU0

BCSU1

BCSU2

4 80

BCSU3

BCSU4

BCSU5

0 2

ET

C0

ET

C1

10

LA

NU

0

LA

NU

1

CL

AC

0

GTIC0

GTIC1

4 96

4

3

2

1

0

CPETx

CPETx

CPETx

CPETx

CPETx

DN9812243 37



Figure 6 ET cartridges in the BSCD extension cabinet of BSC3i 2000

PDFU PDFU

DN0671319

CPETx

BSCD

CPETx

FTRB 1FTRB 0

FTRB 3FTRB 2

5

4

3

2

1

0

0 6

FRONT VIEW

3

10

4 80

BCSU6

BCSU7

4 80

BCSU8

BCSU9

BCSU10

0

CLA

C1

ETC2

ETC3

ETC4

ETC5

LA

NU

3

LA

NU

2

30 6 9

6

38 DN9812243

BSS Integration


ET indexes in BSC

Figure 7 ET cartridges in the new delivery Flexi BSC

PDFU 0PDFU-B

DN70590321

FTRB 1FTRB 0

FTRB 3FTRB 2

5

4

3

2

1

00 6

FRONT VIEW

30

GSW2KB-A0

96

4 80

BCSU0

OMU

BCSU3

BCSU5

0 4 96

4

0

CPETx

GTIC0

ETC0

ETC1 C

LS

0

GSW2KB-A1

GTIC1

ETC2

ETC3 C

LS

1

30 96

PDFU 1PDFU-B

6

MC

MU

0

MC

MU

1

CPETx

CPETx

1

2

3

CPETx

CPETx

0 4 96

BCSU1

LA

NU

0

BCSU4

BCSU6

BCSU2

LA

NU

1

BSCC

CPRJ45-ACPGO/CPETx

CPETx CPETx

DN9812243 39



Figure 8 ET cartridges in the upgraded Flexi BSC

TCSM3i for combined BSC/TCSM installationThe TCSM3i for combined BSC/TCSM installation refers to a way to configure TCSM3i by equipping TCSM3i with a BSC3i or Flexi BSC. The combined BSC/TCSM consists of one BSC3i 1000/2000/upgraded or new delivery Flexi BSC cabinet (also called master BSC) and one TCSM3i cabinet.

Note that when two or more TCSM3i cabinets are used the master BSC needs to be BSC3i 1000 or Flexi BSC.

PDFUPDFU

CPGOT0.8

BSCC

CPETxT0.0

CPRJ45-AT0.4

FTRB 1 FTRB 0

FTRB 3 FTRB 2

5

4

3

2

1

006

Rear view

3 0

GSW2KB0

GSW2KB1

8 6

CL

OC

3 0

MCMU0

MCMU1

OMU

6

48 0

BCSU0

BCSU1

BCSU2

48 0

BCSU3

BCSU4

BCSU5

0

LA

NU

0

LA

NU

1

10

CL

AC

0

GTIC0

GTIC1

49 6

4

3

2

1

0

CPETx

CPETx

CPETx

CPETx

CPETx

BCSU6

DN70623936

40 DN9812243

BSS Integration


ET indexes in BSC

The A interface is implemented by using the STM-1/OC-3 (SDH/SONET) or IP/Ethernet (GigE) interfaces instead of the ET16 (E1/T1) interface. Furthermore, the ET16 units in BSC's and TCSM3i's Ater interface are not used in this configuration.

Two duplicated hotlink cables are used between the BSC and the TCSM3i cabinet. In this application each hotlink cable carries 48 2Mbit/s PCM lines. The capacity of one STM-1 interface is 63 E1 PCMs and one OC-3 interface 84 T1 PCMs. BSC software treats STM-1/OC-3 interfaces as normal E1/T1 PCM lines.

The TCSM3i for combined BSC/TCSM installation with upgraded Flexi BSC brings some modifications to the structure of the BSC3i and TCSM3i: In BSC3i, the TCSA 0 cabinet replaces BCSU 6, the TCSA 1 cabinet replaces BCSU 5, and the TCSA 2 cabinet replaces BCSU 4 in the Group Switch GSW2KB. In TCSM3i, control PCM cables for STMUs/ETIPs both in the TCSA 0 and in the TCSA 1 cabinet are moved to other locations in the GSW2KB. Control PCM cables and control PCM allocations for STMUs/ETIPs in the TCSA 2 cabinet remain the same.

In the TCSM3i for combined BSC/TCSM installation, the ETIP1-A plug-in unit is con-nected to the BSC GSW by a hotlink and it is controlled by a separate LAPD link.

The capacity of one ETIP1-A plug-in unit in the TCSM3i for combined BSC/TCSM instal-lation environment is 126 E1 PCMs or 168 T1 PCMs.


Optical inter-face

STMU index

ET numbers (ETSI)

ET numbers (ANSI)

Control PCM (TSLs)

GTIC 2

05 0 0 32 3392-3454

3392-3475

882 (0-15)

0 1 32 3392-3454

3392-3475

882 (0-15)

1 0 32 3456-3518

3476-3559

882 (0-15)

1 1 32 3456-3518

3476-3559

882 (0-15)

06 0 0 34 3520-3582

3560-3643

882 (16-31)

0 1 34 3520-3582

3560-3643

882 (16-31)

GTIC3

05 0 0 36 3584-3646

3644-3727

890 (0-15)

0 1 36 3584-3646

3644-3727

890 (0-15)

1 0 36 3648-3710

3728-3811

890 (0-15)

1 1 36 3648-3710

3728-3811

890 (0-15)

Table 20 ET indexes in TCSM3i for combined BSC/TCSM installation

DN9812243 41



Figure 9 GTIC cartridges in TCSM3i for combined BSC/TCSM installation

06 0 0 38 3712-3774

3812-3895

890 (16-31)

0 1 38 3712-3774

3812-3895

890 (16-31)


Optical inter-face

STMU index

ET numbers (ETSI)

ET numbers (ANSI)

Control PCM (TSLs)

Table 20 ET indexes in TCSM3i for combined BSC/TCSM installation (Cont.)

CPGO

TCSA 2

FTRB 3FTRB 2

5

4

3

2

1

00 6

30 6

CL

AC

3

0

TC2C 13

6

60

0

9

6

FTRB 1FTRB 0

GTIC8

GTIC9

GTIC10

TC2C 12

TC2C 15TC2C 14

TC2C 17TC2C 16

CPGO

TCSA 1

FTRB 3FTRB 2

5

4

3

2

1

00 6

30 6

CLA

C2

0

TC2C 7

6

60

0

9

6

FTRB 1FTRB 0

GTIC5

GTIC6

GTIC7

TC2C 6

TC2C 9TC2C 8

TC2C 11TC2C 10

CPGO

TCSA 0

FTRB 3FTRB 2

5

4

3

2

1

00 6

30 6

CLA

C1

0

TC2C 1

6

60

0

9

6

FTRB 1FTRB 0

GTIC2

GTIC3

GTIC4

TC2C 0

TC2C 3TC2C 2

TC2C 5TC2C 4

PDFU 0 PDFU 1 PDFU 0 PDFU 1 PDFU 0 PDFU 1


Optical inter-face

STMU index

SET number

ET numbers (ETSI)

ET numbers (ANSI)

Ater PCMs in GSW2KB / GSW2KB-A*)

Control PCM (TSLs ) in GSW2KB / GSW2KB-A *)

TCSA 0 cabinet

GTIC 2

Table 21 ET indexes (ETS2) in TCSM3i for combined BSC/TCSM installation with upgraded and new delivery Flexi BSC when transmission redundancy is used

42 DN9812243

BSS Integration


ET indexes in BSC

05 0 0 32 128 3392-3454 3392-3475

1280-1327 / 1664-1711

1586 (0-15) / 1714 (0-15)

0 1 32 129 3392-3454 3392-3475

1280-1327 / 1664-1711

1586 (0-15) / 1714 (0-15)

1 0 32 130 3456-3518 3476-3559

1280-1327 / 1664-1711

1586 (0-15) / 1714 (0-15)

1 1 32 131 3456-3518 3476-3559

1280-1327 / 1664-1711

1586 (0-15) / 1714 (0-15)

06 0 0 34 136 3520-3582 3560-3643

1280-1327 / 1664-1711

1586 (16-31) / 1714 (16-31)

0 1 34 137 3520-3582 3560-3643

1280-1327 / 1664-1711

1586 (16-31) / 1714 (16-31)

GTIC 3

05 0 0 36 144 3584-3646 3644-3727

1536-1583 / 1728-17775

1594 (0-15) / 1722 (0-15)

0 1 36 145 3584-3646 3644-3727

1536-1583 / 1728-17775

1594 (0-15) / 1722 (0-15)

1 0 36 146 3648-3710 3728-3811

1536-1583 / 1728-17775

1594 (0-15) / 1722 (0-15)

1 1 36 147 3648-3710 3728-3811

1536-1583 / 1728-17775

1594 (0-15) / 1722 (0-15)

06 0 0 38 152 3712-3774 3812-3895

1536-1583 / 1728-17775

1594 (16-31) / 1722 (16-31)

0 1 38 153 3712-3774 3812-3895

1536-1583 / 1728-17775

1594 (16-31) / 1722 (16-31)

TCSA 1 cabinet

GTIC 5


Optical inter-face

STMU index

SET number

ET numbers (ETSI)

ET numbers (ANSI)



Table 21 ET indexes (ETS2) in TCSM3i for combined BSC/TCSM installation with upgraded and new delivery Flexi BSC when transmission redundancy is used (Cont.)

DN9812243 43



05 0 0 40 160 3776-3838 3896-3979

768-815 / 1408-1455

882 (0-15) / 1458 (0-15)

0 1 40 161 3776-3838 3896-3979

768-815 / 1408-1455

882 (0-15) / 1458 (0-15)

1 0 40 162 3840-3902 3980-4063

768-815 / 1408-1455

882 (0-15) / 1458 (0-15)

1 1 40 163 3840-3902 3980-4063

768-815 / 1408-1455

882 (0-15) / 1458 (0-15)

06 0 0 42 168 3904-3966 4064-4147

768-815 / 1408-1455

882 (16-31) / 1458 (16-31)

0 1 42 169 3904-3966 4064-4147

768-815 / 1408-1455

882 (16-31) / 1458 (16-31)

GTIC 6

05 0 0 44 176 3968-4030 4148-4231

832-879 / 1472-1519

890 (0-15) / 1466 (0-15)

0 1 44 177 3968-4030 4148-4231

832-879 / 1472-1519

890 (0-15) / 1466 (0-15)

1 0 44 178 4032-4094 4232-4315

832-879 / 1472-1519

890 (0-15) / 1466 (0-15)

1 1 44 179 4032-4094 4232-4315

832-879 / 1472-1519

890 (0-15) / 1466 (0-15)

06 0 0 46 184 4096-4158 4316-4399

832-879 / 1472-1519

890 (16-31) / 1466 (16-

31)

0 1 46 185 4096-4158 4316-4399

832-879 / 1472-1519

890 (16-31) / 1466 (16-

31)

TCSA 2 cabinet

GTIC 8


Optical inter-face

STMU index

SET number

ET numbers (ETSI)

ET numbers (ANSI)




44 DN9812243

BSS Integration


ET indexes in BSC

*) The 1st Ater PCM area and Control PCM numbers are for GSW2KB in upgraded Flexi BSC. The 2nd Ater PCM areas and Control PCMs are for GSW2KB-A in new delivery Flexi BSC.

05 0 0 48 192 4160-4222 4400-4483

1024-1071 / 1152-1199

1202 (0-15) / 1202 (0-15)

0 1 48 193 4160-4222 4400-4483

1024-1071 / 1152-1199

1202 (0-15) / 1202 (0-15)

1 0 48 194 4224-4286 4484-4567

1024-1071 / 1152-1199

1202 (0-15) / 1202 (0-15)

1 1 48 195 4224-4286 4484-4567

1024-1071 / 1152-1199

1202 (0-15) / 1202 (0-15)

06 0 0 50 200 4288-4350 4568-4651

1024-1071 / 1152-1199

1202 (16-31) / 1202 (16-31)

0 1 50 201 4288-4350 4568-4651

1024-1071 / 1152-1199

1202 (16-31) / 1202 (16-31)

GTIC 9

05 0 0 52 208 4352-4414 4652-4735

1152-1199 / 1216-1263

1210 (0-15) / 1210 (0-15)

0 1 52 209 4352-4414 4652-4735

1152-1199 / 1216-1263

1210 (0-15) / 1210 (0-15)

1 0 52 210 4416-4478 4736-4819

1152-1199 / 1216-1263

1210 (0-15) / 1210 (0-15)

1 1 52 211 4416-4478 4736-4819

1152-1199 / 1216-1263

1210 (0-15) / 1210 (0-15)

06 0 0 54 216 4480-4542 4820-4903

1152-1199 / 1216-1263

1210 (16-31) / 1210 (16-31)

0 1 54 217 4480-4542 4820-4903

1152-1199 / 1216-1263

1210 (16-31) / 1210 (16-31)


Optical inter-face

STMU index

SET number

ET numbers (ETSI)

ET numbers (ANSI)




DN9812243 45




Optical inter-face

STMU index

SET number

ET numbers (ETSI)

ET numbers (ANSI)



TCSA 0 cabinet

GTIC 2

05 0 0 32 128 3392-3454 3392-3475

1280-1327 / 1664-1711

1586 (0-15) / 1714 (0-15)

1 0 32 130 3456-3518 3476-3559

1280-1327 / 1664-1711

1586 (0-15) / 1714 (0-15)

06 0 0 34 136 3520-3582 3560-3643

1280-1327 / 1664-1711

1586 (16-31) / 1714 (16-31)

07 0 0 37 148 3584-3646 3644-3727

1536-1583 / 1728-17775

1587 (0-15) / 1715 (0-15)

1 0 37 150 3648-3710 3728-3811

1536-1583 / 1728-17775

1587 (0-15) / 1715 (0-15)

08 0 0 39 156 3712-3774 3812-3895

1536-1583 / 1728-17775

1587 (16-31) / 1715 (16-31)

GTIC 3

05 0 0 36 144 3584-3646 3644-3727

1536-1583 / 1728-17775

1594 (0-15) / 1722 (0-15)

1 0 36 146 3648-3710 3728-3811

1536-1583 / 1728-17775

1594 (0-15) / 1722 (0-15)

06 0 0 38 152 3712-3774 3812-3895

1536-1583 / 1728-17775

1594 (16-31) / 1722 (16-31)

07 0 0 33 132 3392-3454 3392-3475

1280-1327 /1664-1711

1595 (0-15) / 1723 (0-15)

1 0 33 134 3456-3518 3476-3559

1280-1327 /1664-1711

1595 (0-15) / 1723 (0-15)

08 0 0 35 140 3520-3582 3560-3643

1280…1327 /1664…1711

1595 (16-31) / 1723 (16-31)

Table 22 ET indexes (ETS2) in TCSM3i for combined BSC/TCSM installation with upgraded and new delivery Flexi BSC when HW redundancy is used

46 DN9812243

BSS Integration


ET indexes in BSC

TCSA 1 cabinet

GTIC 5

05 0 0 40 160 3776-3838 3896-3979

768-815 / 1408-1455

882 (0-15) / 1458 (0-15)

1 0 40 162 3840-3902 3980-4063

768-815 / 1408-1455

882 (0-15) / 1458 (0-15)

06 0 0 42 168 3904-3966 4064-4147

768-815 / 1408-1455

882 (16-31) / 1458 (16-31)

07 0 0 45 180 3968-4030 4148-4231

832-879 / 1472-1519

883 (0-15) / 1459 (0-15)

1 0 45 182 4032-4094 4232-4315

832-879 / 1472-1519

883 (0-15) / 1459 (0-15)

08 0 0 47 188 4096-4158 4316-4399

832-879 / 1472-1519

883 (16-31) / 1459 (16-31)

GTIC 6

05 0 0 44 176 3968-4030 4148-4231

832-879 / 1472-1519

890 (0-15) / 1466 (0-15)

1 0 44 178 4032-4094 4232-4315

832-879 / 1472-1519

890 (0-15) / 1466 (0-15)

06 0 0 46 184 4096-4158 4316-4399

832-879 / 1472-1519

890 (16-31) / 1466 (16-

31)

07 0 0 41 164 3776-3838 3896-3979

768-815 / 1408-1455

891 (0-15) / 1467 (0-15)

1 0 41 166 3840-3902 3980-4063

768-815 / 1408-1455

891 (0-15) / 1467 (0-15)

08 0 0 43 172 3904-3966 4064-4147

768-815 / 1408-1455

891 (16-31) / 1467 (16-

31)

TCSA 2 cabinet

GTIC 8

05 0 0 48 192 4160-4222 4400-4483

1024-1071 / 1152-1199

1202 (0-15) / 1202 (0-15)

1 0 48 194 4224-4286 4484-4567

1024-1071 / 1152-1199

1202 (0-15) / 1202 (0-15)


Optical inter-face

STMU index

SET number

ET numbers (ETSI)

ET numbers (ANSI)



Table 22 ET indexes (ETS2) in TCSM3i for combined BSC/TCSM installation with upgraded and new delivery Flexi BSC when HW redundancy is used (Cont.)

DN9812243 47



*) The 1st Ater PCM area and Control PCM numbers are for GSW2KB in upgraded Flexi BSC. The 2nd Ater PCM areas and Control PCMs are for GSW2KB-A in new delivery Flexi BSC.

06 0 0 50 200 4288-4350 4568-4651

1024-1071 / 1152-1199

1202 (16-31) / 1202 (16-31)

07 0 0 53 212 4352-4414 4652-4735

1152…1199 / 1216-1263

1203 (0-15) / 1203 (0-15)

1 0 53 214 4416-4478 4736-4819

1152-1199 / 1216-1263

1203 (0-15) / 1203 (0-15)

08 0 0 55 220 4480-4542 4820-4903

1152-1199 / 1216-1263

1203 (16-31) / 1203 (16-31)

GTIC 9

05 0 0 52 208 4352-4414 4652-4735

1152-1199 / 1216-1263

1210 (0-15) / 1210 (0-15)

1 0 52 210 4416-4478 4736-4819

1152-1199 / 1216-1263

1210 (0-15) / 1210 (0-15)

06 0 0 54 216 4480-4542 4820-4903

1152-1199 / 1216-1263

1210 (16-31) / 1210 (16-31)

07 0 0 49 196 4160-4222 4400-4483

1024-1071 / 1152-1199

1211 (0-15) / 1211 (0-15)

1 0 49 198 4224-4286 4484-4567

1024-1071 / 1152-1199

1211 (0-15) / 1211 (0-15)

08 0 0 51 204 4288-4350 4568-4651

1024-1071 / 1152-1199

1211 (16-31) / 1211 (16-31)


Optical inter-face

STMU index

SET number

ET numbers (ETSI)

ET numbers (ANSI)



Table 22 ET indexes (ETS2) in TCSM3i for combined BSC/TCSM installation with upgraded and new delivery Flexi BSC when HW redundancy is used (Cont.)

48 DN9812243

BSS Integration


ET indexes in BSC

Slot GbE interface

ETIP index

EET number

ET numbers (ETSI)

ET numbers (ANSI)



TCSA 0 cabinet

GTIC 2

05 0 32 64 3392-3454

3456-3518

3392-3475

3476-3559

1280-1327 / 1664-1711

1586 (0-3) / 1714 (0-3)

1 32 65 3392-3454

3456-3518

3392-3475

3476-3559

1280-1327 / 1664-1711

1586 (0-3) / 1714 (0-3)

06 0 34 68 3520-3582 3560-3643

1280-1327 / 1664-1711

1586 (16-19) / 1714 (16-19)

1 34 69 3520-3582 3560-3643

1280-1327 / 1664-1711

1586 (16-19) / 1714 (16-19)

GTIC 3

05 0 36 72 3584-3646

3648-3710

3644-3727

3728-3811

1536-1583 / 1728-17775

1594 (0-3) / 1722 (0-3)

1 36 73 3584-3646

3648-3710

3644-3727

3728-3811

1536-1583 / 1728-17775

1594 (0-3) / 1722 (0-3)

06 0 38 76 3712-3774 3812-3895

1536-1583 / 1728-17775

1594 (16-19) / 1722 (16-19)

1 38 77 3712-3774 3812-3895

1536-1583 / 1728-17775

1594 (16-19) / 1722 (16-19)

TCSA 1 cabinet

GTIC 5

Table 23 ET indexes (ETIP) in TCSM3i for combined BSC/TCSM installation with upgraded and new delivery Flexi BSC when transmission redundancy is used

DN9812243 49



05 0 40 80 3776-3838

3840-3902

3896-3979

3980-4063

768-815 / 1408-1455

882 (0-3) / 1458 (0-3)

1 40 81 3776-3838

3840-3902

3896-3979

3980-4063

768-815 / 1408-1455

882 (0-3) / 1458 (0-3)

06 0 42 84 3904-3966 4064-4147

768-815 / 1408-1455

882 (16-19) / 1458 (16-19)

1 42 85 3904-3966 4064-4147

768-815 / 1408-1455

882 (16-19) / 1458 (16-19)

GTIC 6

05 0 44 88 3968-4030

4032-4094

4148-4231

4232-4315

832-879 / 1472-1519

890 (0-3) / 1466 (0-3)

1 44 89 3968-4030

4032-4094

4148-4231

4232-4315

832-879 / 1472-1519

890 (0-3) / 1466 (0-3)

06 0 46 92 4096-4158 4316-4399

832-879 / 1472-1519

890 (16-19) / 1466 (16-19)

1 46 93 4096-4158 4316-4399

832-879 / 1472-1519

890 (16-19) / 1466 (16-19)

TCSA 2 cabinet

GTIC 8

05 0 48 96 4160-4222

4224-4286

4400-4483

4484-4567

1024-1071 / 1152-1199

1202 (0-3) / 1202 (0-3)

1 48 97 4160-4222

4224-4286

4400-4483

4484-4567

1024-1071 / 1152-1199

1202 (0-3) / 1202 (0-3)

Slot GbE interface

ETIP index

EET number

ET numbers (ETSI)

ET numbers (ANSI)



Table 23 ET indexes (ETIP) in TCSM3i for combined BSC/TCSM installation with upgraded and new delivery Flexi BSC when transmission redundancy is used (Cont.)

50 DN9812243

BSS Integration


ET indexes in BSC

06 0 50 100 4288-4350 4568-4651

1024-1071 / 1152-1199

1202 (16-19) / 1202 (16-19)

1 50 101 4288-4350 4568-4651

1024-1071 / 1152-1199

1202 (16-19) / 1202 (16-19)

GTIC 9

05 0 52 104 4352-4414

4416-4478

4652-4735

4736-4819

1152-1199 / 1216-1263

1210 (0-3) / 1210 (0-3)

1 52 105 4352-4414

4416-4478

4652-4735

4736-4819

1152-1199 / 1216-1263

1210 (0-3) / 1210 (0-3)

06 0 54 108 4480-4542 4820-4903

1152-1199 / 1216-1263

1210 (16-19) / 1210 (16-19)

1 54 109 4480-4542 4820-4903

1152-1199 / 1216-1263

1210 (16-19) / 1210 (16-19)

Slot GbE interface

ETIP index

EET number

ET numbers (ETSI)

ET numbers (ANSI)



TCSA 0 cabinet

GTIC 2

05 0 32 64 3392-3454

3456-3518

3392-3475

3476-3559

1280-1327 / 1664-1711

1586 (0-3) / 1714 (0-3)

Table 24 ET indexes (ETIP) in TCSM3i for combined BSC/TCSM installation with upgraded and new delivery Flexi BSC when HW redundancy is used

Slot GbE interface

ETIP index

EET number

ET numbers (ETSI)

ET numbers (ANSI)



Table 23 ET indexes (ETIP) in TCSM3i for combined BSC/TCSM installation with upgraded and new delivery Flexi BSC when transmission redundancy is used (Cont.)

DN9812243 51



06 0 34 68 3520-3582

3584-3646

3560-3643

3644-3727

1280-1327 / 1664-1711

1536-1583 / 1728-17775

1586 (16-19) / 1714 (16-19)

07 0 36 72 3648-3710

3712-3774

3728-3811

3812-3895

1536-1583 / 1728-17775

1587 (0-3) / 1715 (0-3)

GTIC 3

05 0 33 66 3392-3454

3456-3518

3392-3475

3476-3559

1280-1327 /1664-1711

1594 (0-3) / 1722 (0-3)

06 0 35 70 3520-3582

3584-3646

3560-3643

3644-3727

1280-1327 /1664-1711

1536-1583 / 1728-17775

1594 (16-19) / 1722 (16-19)

07 0 37 74 3648-3710

3712-3774

3728-3811

3812-3895

1536-1583 / 1728-17775

1595 (0-3) / 1723 (0-3)

TCSA 1 cabinet

GTIC 5

05 0 38 76 3776-3838

3840-3902

3896-3979

3980-4063

768-815 / 1408-1455

882 (0-3) / 1458 (0-3)

06 0 40 80 3904-3966

3968-4030

4064-4147

4148-4231

768-815 / 1408-1455

832-879 / 1472-1519

882 (16-19) / 1458 (16-19)

07 0 42 84 4032-4094

4096-4158

4232-4315

4316-4399

832-879 / 1472-1519

883 (0-3) / 1459 (0-3)

GTIC 6

Slot GbE interface

ETIP index

EET number

ET numbers (ETSI)

ET numbers (ANSI)




52 DN9812243

BSS Integration


ET indexes in BSC

05 0 39 78 3776-3838

3840-3902

3896-3979

3980-4063

768-815 / 1408-1455

890 (0-3) / 1466 (0-3)

06 0 41 82 3904-3966

3968-4030

4064-4147

4148-4231

768-815 / 1408-1455

832-879 / 1472-1519

890 (16-19) / 1466 (16-19)

07 0 43 86 4032-4094

4096-4158

4232-4315

4316-4399

832-879 / 1472-1519

891 (0-3) / 1467 (0-3)

TCSA 2 cabinet

GTIC 8

05 0 44 88 4160-4222

4224-4286

4400-4483

4484-4567

1024-1071 / 1152-1199

1202 (0-3) / 1202 (0-3)

06 0 46 92 4288-4350

4352-4414

4568-4651

4652-4735

1024-1071 / 1152-1199

1152…1199 / 1216-1263

1202 (16-19) / 1202 (16-19)

07 0 48 96 4416-4478

4480-4542

4736-4819

4820-4903

1152…1199 / 1216-1263

1203 (0-3) / 1203 (0-3)

GTIC 9

05 0 45 90 4160-4222

4224-4286

4400-4483

4484-4567

1024-1071 / 1152-1199

1210 (0-3) / 1210 (0-3)

06 0 47 94 4288-4350

4352-4414

4568-4651

4652-4735

1024-1071 / 1152-1199

1152…1199 / 1216-1263

1210 (16-19) / 1210 (16-19)

Slot GbE interface

ETIP index

EET number

ET numbers (ETSI)

ET numbers (ANSI)




DN9812243 53



BSC3i 660BSC3i 660 can have up to two ET4C-B cartridges in basic configuration.

With the 256 PCM Bit Group Switch (GSWB), the two ET4C-B cartridges have space for 62 * (2*2) Mbit ET PCM's plug-in units in ETSI or 62 * (2*1.5) Mbit ET PCM's plug-in units in ANSI (32 pcs in ET4C 0, 30 pcs in ET4C 1). This makes it possible to have a maximum of 124 ET PCMs in one BSC3i 660. See figure ET4C-B cartridges with GSWB and ET2A/ET2A-T(B)/ET2E-S/SC/ET2E-T(B)/ET2E-TC(B) indexes in BSC3i 660.

With the 1024 PCM Bit Group Switch (GSW1KB), the two ET4C-B cartridges have space for 64 * (4*2) Mbit ET PCM's plug-in units in ETSI or 64 * (4*1.5) Mbit ET PCM's plug-in units in ANSI (32 pcs in ET4C 0 and 32 pcs in ET4C 1). This makes it possible to have a maximum of 256 ET PCMs in one BSC3i 660. See figure ET4C-B cartridges with GSW1KB and ET4A/ET4E/ET4E-C indexes in BSC3i 660.

With the GSW1KB Bit Group Switch it is also possible to mix ET2 and ET4 plug-in units in the BSC3i 660, so that each BSC3i 660 equipped with GSW1KB can have both ET2 and ET4 plug-in units with the restriction that one ET4C-B shelf must be equipped with either ET2 plug-in units or ET4 plug-in units. See figure ET4C-B cartridges with GSW1KB and ET2A/ET2A-T(B)/ET2E-S/SC/ET2E-T(B)/ET2E-TC(B) indexes in BSC3i 660.

07 0 49 98 4416-4478

4480-4542

4736-4819

4820-4903

1152…1199 / 1216-1263

1211 (0-3) / 1211 (0-3)

Slot GbE interface

ETIP index

EET number

ET numbers (ETSI)

ET numbers (ANSI)




54 DN9812243

BSS Integration


ET indexes in BSC

Figure 10 ET4C-B cartridges with GSWB and ET2A/ET2A-T(B)/ET2E-S/SC/ET2E-T(B)/ET2E-TC(B) indexes in BSC3i 660

FTRB 0 FTRB 1

PDFU-A0

PDFU-A1

PDFU-A2

PDFU-A3

BSCC

GSWB1

GSWB0

CPRJ45 CPGOCPGO

BCSU 6

MCMU1

MCMU0

OMU

BCSU 0 BCSU 1 BCSU 2

FRONT VIEW

CL

S0

,1


0

1

2

3

4FTRB 2 FTRB 3

TO

5

3233

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

ET4C 0

3435

3637

3839

4041

4243

4445

4647

4849

5051

5253

5455

5657

5859

6061

6263

9697

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

9899

100101

102103

104105

106107

108109

110111

112113

114115

116117

118119

120121

122123

124125

126127

ET4C 1

160161

162163

164165

166167

168169

170171

172173

174175

176177

178179

180181

182183

184185

186187

188189

190191

224225

226227

228229

230231

232233

234235

236237

238239

240241

242243

244245

246247

248249

250251

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

ET4C 1ET4C 0

GSWB:

GSWB:

GSWB:

GSWB:

DN9812243 55



Figure 11 ET4C-B cartridges with GSW1KB and ET4A/ET4E/ET4E-C indexes in BSC3i 660

FTRB 0 FTRB 1

PDFU-A0

PDFU-A1

PDFU-A2

PDFU-A3

BSCC

GSW1KB1

GSW1KB0

CPRJ45 CPGOCPGO

BCSU 6

MCMU 1MCMU 0 OMU


FRONT VIEW

CLS

0,1


0

1

2

3

4

0 3 6 8

0 3 6 9

0 4 8

0 3 6

0 6

FTRB 2 FTRB 30 6

0 4 8

0 7

0 4 8

T0

5

256257258259

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

ET4C 0

ET4C 1

260261262263

264265266267

268269270271

272273274275

276277278279

280281282283

284285286287

288289290291

292293294295

296297298299

300301302303

304305306307

308309310311

312313314315

316317318319

384385386387

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

388389390391

392393394395

396397398399

400401402403

404405406407

408409410411

412413414415

416417418419

420421422423

424425426427

428429430431

432433434435

436437438439

440441442443

444445446447

320321322323

324325326327

328329330331

332333334335

336337338339

340341342343

344345346347

348349350351

352353354355

356357358359

360361362363

364365366367

368369370371

372373374375

376377378379

380381382383

448449450451

452453454455

456457458459

460461462463

464465466467

468469470471

472473474475

476477478479

480481482483

484485486487

488489490491

492493494495

496497498499

500501502503

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

ET4C 1(32oET4)

ET4C 0(32oET4)

GS

W1K

B

504505506507

508509510511

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

ET

4x

GS

W1K

BG

SW

1K

BG

SW

1K

B

56 DN9812243

BSS Integration


ET indexes in BSC

Figure 12 ET4C-B cartridges with GSW1KB and ET2A/ET2A-T(B)/ET2E-S/SC/ET2E-T(B)/ET2E-TC(B) indexes in BSC3i 660

BSC2iThe BSC2i can have up to seven ET5C cartridges, each having space for 16 2Mbit ET PCM's plug-in units. This makes it possible to have a maximum of 112 2Mbit ET PCMs in one BSC2i; see the following figure.

FTRB 0 FTRB 1

PDFU-A0

PDFU-A1

PDFU-A2

PDFU-A3

BSCC

GSW1KB1

GSW1KB0

CPRJ45 CPGOCPGO

BCSU 6

MCMU 1MCMU 0 OMU


FRONT VIEW

CL

S0

,1


0

1

2

3

4

0 3 6 8

0 3 6 9

0 4 8

0 3 6

0 6

FTRB 2 FTRB 30 6

0 4 8

0 7

0 4 8

T0

5

256257

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

ET4C 0

ET4C 1

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

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

ET4C 1(32oET2)

ET4C 0(32oET2)

GS

W1

KB

:G

SW

1K

B:

GS

W1

KB

:

ET

2x

258259

260261

262263

264265

266267

268269

270271

272273

274275

276277

278279

280281

282283

284285

286287

384385

386387

388389

390391

392393

394395

396397

398399

400401

402403

404405

406407

408409

410411

412413

414415

320321

322323

324325

326327

328329

330331

332333

334335

336337

338339

340341

342343

344345

346347

348349

350351

448449

450451

452453

454455

456457

458459

460461

462463

464465

466467

468469

470471

472473

474475

476477

478479

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

ET

2x

GS

W1

KB

:

DN9812243 57



Figure 13 ET5C cartridges and ET2E/ET2A indexes in BSC2i

BSCiIn BSCi (used only in the ETSI environment), there can be seven ET1C cartridges and two ET5C cartridges. Each ET1C cartridge can contain eight ET1E plug-in units and each ET5C cartridge can contain eight ET2E plug-in units, making it possible to have up to 88 2Mbit ET PCMs in one BSCi.

MCMU0 MCMU1

OMU

BCSU0

WDDC0

WDDC1

BCSU1

BCSU7

BCSU6BCSU5

BCSU4BCSU3

BCSU2

BCSU8

GSWB1GSWB0 CLOC0

CLAC0

PSA20_0PSFP0

PSA20_1PSFP1

PSA20_2PSFP2

PSA20_3PSFP3

ET5C0

BCBE BCEE

ET5C1

3233

3435

3637

3839

4849

5051

5253

5455

GSWB:

GSWB:

4041

4243

4445

4647

5657

5859

6061

6263

GSWB:

GSWB:

ET5C5

GSWB:

GSWB:

120121

122123

124125

126127

128129

130131

132133

134135

ET5C6

GSWB:

GSWB:

136137

138139

140141

142143

144145

146147

148149

150151

ET5C4

GSWB:

GSWB:

104105

106107

108109

110111

112113

114115

116117

118119

ET5C3

GSWB:

GSWB: 8081

8283

8485

8687

9697

9899

100101

102103

ET5C2

7273

7475

7677

7879

8889

9091

9293

9495

GSWB:

GSWB:

ET5C7

GSWB:

GSWB:

224225

226227

228229

230231

232233

234235

236237

238239

ET5C8

GSWB:

GSWB:

240241

242243

244245

246247

248249

250251

252253

254255

58 DN9812243

BSS Integration


ET indexes in BSC


Car-tridge

ET1

C0

ET1

C1

ET1

C2

ET1

C3

ET1

C4

ET1

C5

ET1

C6

ET1

C0

ET1

C1

PCM Index

32 40 48 56 72 80 88 96/97 112/113

33 41 49 57 73 81 89 98/99 114/115

34 42 50 58 74 82 90 100/101 116/117

35 43 51 59 75 83 91 102/103 118/119

36 44 52 60 76 84 92 104/105 120/121

37 45 53 61 77 85 93 106/107 122/123

38 46 54 62 78 86 94 108/109 124/125

39 47 55 63 79 87 95 110/111 126/127

Table 25 ET indexes with GSWB in BSCi

DN9812243 59

BSS Integration Creating the A interface

Id:0900d805807d47d0Confidential

5 Creating the A interfaceIn this phase the MSC, the transcoder, and the BSC are configured to enable the MSC and the BSC to communicate properly with each other.

For more information on connecting a BSC to other core network elements, see Multi-point A Interface in BSC.


5.1 Connecting the A interface ETEach A interface needs its own ET. The ETs used for the A interface must be the ones that supply synchronisation to the BSC's CLS units. There are three such ETs per BSC, and their default unit numbers are shown in the table below. It is possible to use any other ET for the synchronisation by changing the position of the corresponding synchro-nisation cable in the ET cartridge.

*RoHS compliant ET2A-TB, ET2E-TB and ET2E-TCB units are created to the equip-ment database as ET2A-T , ET2E-T and ET2E-TC.

Steps

1 Check that the ET is connected (WUP).ZWUP:<PCM numbers>;

If the ET is already connected, it has a controlling BCSU (Base Station Controller Sig-nalling Unit) and process info. The controlling process can be SC7PRB A interface, ABIPRB Abis interface, SI1PRB ISDN Abis interface, or ERATES Gb interface.

BSC type ET type GSW type Default synchronisation ETs

BSCi ET1E, ET1E-C, ET2E, ET2E-C, ET2E-S/SC, ET2E-T(B), ET2E-TC(B)*

GSWB 32,33,34

BSC2i ET2E/A, ET2E-C, ET2E-S/SC, ET2E-T(B), ET2A-T(B), ET2E-TC(B)*

GSWB 32,40,48

(only even ETs possible)

BSC3i ET2A, ET2E-S/SC, ET2E-T(B), ET2A-T(B), ET2E-TC(B)*

GSWB 32, 96, 160, 224

(only even ETs possible)

ET4A, ET4E, ET4E-C

GSW1KB

BSC3i 1000, BSC3i 2000

ET16 GSW2KB 512, 576, 528, 592

Flexi BSC ET16 GSW2KB-A 368, 640, 256, 624

Table 26 Default synchronisation ETs

60 DN9812243

BSS Integration


Creating the A interface

Example: ZWUP:32&33&36;

EXECUTION STARTED

BSC VAPPU 2004-10-18 08:39:25

PCM COMP PROC INFO_1 INFO_2 INFO_3 ADD_INFO PAGE 1 32 BCSU SC7PRB ETPCM - - VIRTUAL_PCMS 32H 01B1H 0000H 0000H 0000H 1280 - 1281 33 BCSU ABIPRB ETPCM - - VIRTUAL_PCMS 32H 01BFH 0000H 0000H 0000H 1288 - 1295 36 BCSU ERATES ETPCM - - 32H 010AH 0000H 0000H 0000H

TOTAL OF 3 PCM CIRCUITS

COMMAND EXECUTED

2 To implement this step, choose one of the following alternatives:

a If ET is already connected

Then

Check that the ET is in WO state and restart the ET (USU).The state of the ET can be changed with command USC.

The ET must be restarted to ensure that the correct ET software is loaded into the unit.

ZUSU:ET,<pcm_index>,C=TOT;

Note that all ET's in the same plug-in unit will be restarted concurrently.

b If ET is not connected

Then

Connect the ET (WUC).ZWUC:ET,<unit index>:<plug-in unit type>,0:IF=A:BCSU,<bcsu index>;


Parameter Explanation

plug-in unit type Type of the ET:

ETSI: ET1E, ET1E-C, ET2E, ET2E-C, ET2E-S, ET2E-SC, ET2E-T*, ET2E-TC*, ET4E, ET4E-C, or ET16

ANSI: ET2A, ET2A-T*, ET4A, or ET16

DN9812243 61



Note that you have to select the line interface (T1 or E1) in ET16 with a micro switch. For more information see ET16 C109519 in Jumper Settings of the Plug-in Units in BSC3i and in TCSM3i.

If the controlling BCSU is not already in WO-EX state, the state of the BCSU must be changed to WO-EX. Once the BCSU's state is WO-EX, the state of the ET can be changed to WO-EX, too.

t When using ET2E/A, ET2E-C, ET2E-S/SC, ET2E-T(B), ET2A-T(B), or ET2E-TC(B) plug-in units, connect the even-numbered ET before the odd-numbered.

When using ET4A, ET4E, ET4E-C, or ET16 plug-in units, first connect the first logical ET of the cartridge.

3 Check and change the functional modes for the ET if needed.The status of the frame alignment mode must be the same at both ends of the PCM line.

For ET1E cards the frame alignment mode is set by strapping.

For ET2E/A, ET2E-C, ET2E-S/SC, ET2E-T(B), ET2A-T(B), ET2E-TC(B), ET4A, ET4E, ET4E-C, or ET16 the frame alignment mode is set by MML. The frame alignment mode strapping in them is used only during the unit restart when the software cannot be loaded for some reason.

Steps

a Output the functional modes of the ET2E/A, ET2E-C, ET2E-S/SC, ET2E-T(B), ET2A-T(B), ET2E-TC(B), ET4A, ET4E, ET4E-C, or ET16 (ETSI: YEI, ANSI: YEH).

• ETSI:ZYEI:ET,<unit index>;

• ANSI:This means the values of the strappings to be programmed:ZYEH:<unit type>,<unit index>;

b Change the functional mode if needed (ETSI: YEC, ANSI: YEG).

• ETSI:ZYEC:ET,<unit index>:NORM,<frame alignment mode>;

• ANSI:Note that the T1 functional modes have to be the same at both ends of the T1 line.ZYEG:<unit type>,<unit index>:<superframe mode>,<line code type>,<outgoing signal level>;

Further informationNext, create the transcoder devices.

5.2 Connecting the optical A interfacePurposeThis section describes how to configure the A interface when STM-1/OC-3 optical trans-mission is used. STM-1/OC-3 interface is an optical interface to SDH network that

62 DN9812243

BSS Integration



increases the connectivity of the network element. One STM-1 (ETSI) interface can carry 63 E1 PCMs and one OC-3 (ANSI) interface 84 T1 PCMs.

STM-1/OC-3 interfaces are implemented with ETS2 plug-in units, each of which can handle two interfaces.

For more information, see Configuring the STM-1/OC-3 interface in STM-1/OC-3 (SDH/SONET) Interface.

Steps

1 Create the cartridge, functional unit, ET groups and plug-in units for the ET groups.For detailed instructions and commands, see Creating and managing ETS2s in Creating and Managing BSC Hardware.

2 Connect the ET (WUC).ZWUC:<unit type>,<unit index>:<piu type>,<piu index>:IF=<interface>:<controlling unit type>,<controlling unit index>:;

Example: ETSI:

ZWUC:ET,64&&126:ETS2,0:IF=A:BCSU,1:;


ANSI:



3 Check the ET configuration (YAI).ZYAI:<exchange terminal type>,<exchange terminal index>:;

Example: ZYAI:SET,0:;

4 Check the functional mode of exchange terminal (YEI or YEH).The mode should be the same at both ends of the connection. Check the current PDH frame alignment mode at the remote end of the connection and compare it to the current mode at the local end. In an ETSI environment, the default value of E1 frame alignment mode is CRC4. In an ANSI environment, the default value of T1 frame alignment mode is ESF .

ETSI:

ZYEI:<unit type>;

ANSI:

ZYEH:<unit type>;

DN9812243 63



5 Change the functional mode, if needed (YEC or YEG).ETSI:

ZYEC:<unit type>,<unit index>:<functional mode>,<frame alignment mode>:;

ANSI:

ZYEG:<unit type>,<unit index>:<superframe mode>;

5.3 Connecting the PWE interfacePurposeThis section describes how to connect the A interface when IP/Ethernet (GigE) trans-mission is used. The IP/Ethernet interfaces are implemented with ETIP plug-in units.

For more information, see Creating the unit connections in ETIP/PWT User Guide.

When there is no existing IP/Ethernet based Ater interface connection between BSC and TCSM3i, the user needs to configure BSC and TCSM3i locally. When you do this for the first time use one of the Ater interface master TR3E/TR3A/TR3T plug-in units, otherwise remote connections are not possible later.

Steps

1 Create the cartridge, functional unit, ET groups and plug-in units for the ET groups.For detailed instructions and commands, see Creating and managing ETIPs in Creating and Managing BSC Hardware.

2 Connect the ET (WUC).ZWUC:<unit type>,<unit index>:<piu type>,<piu index>:IF=<interface>:<controlling unit type>,<controlling unit index>:;

Example: ETSI:

ZWUC:ET,64&&126:ETIP1_A,0:IF=A:BCSU,1:;


ANSI:



5.4 Creating the transcoder devicesIn this phase the transcoder is configured. The transcoder is needed between the MSC and the BSC for speech compression. It compresses 64 kbit speech time slots coming from the MSC to 16 or 8 kbit speech time slots going to the BSC. Decompression is carried out in the opposite direction.

64 DN9812243

BSS Integration



Choose one of the following procedures, depending on the type of TCSM and the type of configuration used.

5.4.1 Creating the TCSM3i

PurposeWhen the standalone TCSM3i is created into the BSC hardware database, its functional unit is TCSM and both transcoder types are controlled by the BSC via the LAPD link. The TCSM3i software is also kept in the BSC hard disks from where it can be down-loaded to the TCSM3i whenever necessary.

One transcoder based on TCSM3i hardware consists of one TR3E (ETSI), TR3A (ANSI), or TR3T (ETSI or ANSI) plug-in unit and either one ET16 or one ETIP plug-in unit (as Ater interface). ETP-A unit for the Packet Transport is included in the stand alone TCSM3i, also mixed with ET16 and ETIP plug-in units (as A interface).

In TCSM3i, both ET16 and ETIP plug-in units are equipped only with supervised TR3E/TR3A/TR3T units.

When IP/Ethernet (GigE) connections are used as Ater interfaces, Ater PCM cablings are delivered in a general optional set for ETIP used as Ater interface. The ETIP1-A plug-in unit on the Ater interface is always HW protected, so an optional set for HW pro-tection is always used in Ater interfaces for standalone TCSM3i with IP/Ethernet (GigE) interfaces

One TCSM3i can handle a maximum of four TC-PCMs on the A interface when 16 Kbit/s submultiplexing is used on Ater interface. 8 Kbit/s Ater submultiplexing is not supported by the TCSM3i.

One TCSM3i cabinet can contain up to 96 transcoder units in 6 cartridges as shown in the figure below. The same principles apply in both ET16 and ETIP configurations.

DN9812243 65



Figure 14 TCSM3i ET (ET16 or ETIP) units and transcoder units

For more information on TCSM3i cabinet configurations, please refer TCSM3i cabinet configuration and capacity.

As shown in the following table, a certain number of TR3E/TR3A/TR3T units act as masters who supervise the ET16 plug-in units. When the master TR3E/TR3A/TR3T plug-in units are taken into use, the ET16 plug-in units are also equipped.

TC2C 0

slots:

slots:

slots:

TR3E

1

TR3E

2

TR3E

3

TR3E

4

TR3E

5

TR3E

6

TR3E

7

TR3E

8

TR3E

9

TR3E

10

TR3E

11

TR3E

12

TR3E

13

TR3E

14

TR3E

15

TR3E

16

ET16

17 18 19

1 2 3 4

TC2C 1

TR3E

1

TR3E

2

TR3E

3

TR3E

4

TR3E

5

TR3E

6

TR3E

7

TR3E

8

TR3E

9

TR3E

10

TR3E

11

TR3E

12

TR3E

13

TR3E

14

TR3E

15

TR3E

16

ET16

17 18 19

5 6 7 8

ET16

TC2C 3

TR3E

1

TR3E

2

TR3E

3

TR3E

4

TR3E

5

TR3E

6

TR3E

7

TR3E

8

TR3E

9

TR3E

10

TR3E

11

TR3E

12

TR3E

13

TR3E

14

TR3E

15

TR3E

16

ET16

17 18 19

13 14 15 16

ET16

TC2C 2

TR3E

1

TR3E

2

TR3E

3

TR3E

4

TR3E

5

TR3E

6

TR3E

7

TR3E

8

TR3E

9

TR3E

10

TR3E

11

TR3E

12

TR3E

13

TR3E

14

TR3E

15

TR3E

16

ET16

17 18 19

9 10 11 12

TC2C 5

TR3E

1

TR3E

2

TR3E

3

TR3E

4

TR3E

5

TR3E

6

TR3E

7

TR3E

8

TR3E

9

TR3E

10

TR3E

11

TR3E

12

TR3E

13

TR3E

14

TR3E

15

TR3E

16

ET16

17 18 19

21 22 23 24

ET16

TC2C 4

TR3E

1

TR3E

2

TR3E

3

TR3E

4

TR3E

5

TR3E

6

TR3E

7

TR3E

8

TR3E

9

TR3E

10

TR3E

11

TR3E

12

TR3E

13

TR3E

14

TR3E

15

TR3E

16

ET16

17 18 19

17 18 19 20

ETC 0

1 2 3 4 5 6 7 8

ET16

ET16

ET16

ET16

ET16

ET16

ET16

ET16

1 5 9 13 17 19 21 23

slots:

ETC 1

1 2 3 4 5 6 7 8

ET16

ET16

ET16

ET16

ET16

ET16

ET16

ET16

2 4 6 8 10 12 14 16

ETC 2

1 2 3 4 5 6 7 8

ET16

ET16

ET16

ET16

ET16

ET16

ET16

ET16

3 7 11 15 18 20 22 24

Slot number Role when using ET16 Role when using ETIP

1 Cartridge master Cartridge master

2 Cabinet head master (only in cartridge 2.0)

Cabinet head master (only in cartridge 2.0)

3 - Ater ETIP master

4 - A ETIP master

Table 27 TR3E/TR3A/TR3T roles

66 DN9812243

BSS Integration



* acts as a cartridge master when two BSCs are connected to one cartridge

To ensure that the TCSM3i capacity is fully exploited, its transcoding functions can be shared between several BSCs. This is achieved by connecting two BSCs to one TCSM3i cartridge. In this kind of configuration one BSC uses the first eight TR3E/TR3A/TR3T plug-in units and the other BSC the last eight TR3E/TR3A/TR3T plug-in units. Additional ET16 plug-in units must be installed to the TCSM3i for the second BSC Ater interface to the TCSM3i cartridge.

For more information on configuring ETIP plug-in unit and creating the IP/Ethernet (GigE) configuration, see ETIP/PWT User Guide.

Steps

1 Create the cabinet clock cartridge (WTC).ZWTC:<cartridge type>, coordinate of cartridge>:P1;

2 Create the TCSM3i cabinet (WTJ).ZWTJ:TCSA,1D:AL=1D1-0-4R1,PDFU=4;

3 Create the TCSM and ET cartridges (WTC).ZWTC:<cartridge type>,<coordinate of cartridge>:P1;

4 Create the TCSM unit (WTU).ZWTU:<unit identification>:<coordinate of cartridge>;

Note that the indexes of the BSC site ET and the TCSM have to be the same.

5 Create the TR3E/TR3A/TR3T plug-in units (WTP).ZWTP:TCSM,<unit index>:<piu type>,<piu index>,<track>::GENERAL,8,<PCM>,<TSL type>,<TSL>;

5 Master Master


8 - A ETIP master

9 Master* Master*


12 - A ETIP master

13 Master Master


16 - A ETIP master

Slot number Role when using ET16 Role when using ETIP

Table 27 TR3E/TR3A/TR3T roles (Cont.)

DN9812243 67



6 Create the ET16 or ETIP plug-in units (WTP).ZWTP:TCSM,<unit index>:<piu type>,0,1; (A interface ET)

ZWTP:TCSM,<unit index>:<piu type>,1,17; (Ater interface ET)

7 Set the number of through connected channels (WGS).ZWGS:<highway pcm>:<number of through connected channels>;

8 Create transcoder PCMs (WGC).ZWGC:<highway pcm number>,<tc_pcm number>:POOL=<transcoder pcm pool numbers>:BCSU,<controlling unit index>;

The table below shows which A-interface pools support which codecs and application software.

9 Connect the TR3E/TR3A/TR3T to the BSC (WUC).This command creates the LAPD link between the BSC and the TR3E/TR3A/TR3T. A circuit group DTCSM and the circuit to it are created at the same time.

ZWUC:TCSM,<unit index>:<piu type>,<piu index>;

10 Change the state of the TCSM3i to WO-EX (USC).This command automatically changes the state of the TCSM LAPD link to WO-EX. If the TCSM3i software does not exist or is different from that in the BSC, it is downloaded in this phase.

11 Check the state of the TCSM3i LAPD link (DTF).ZDTF:TCSM,<unit index>:OMU;

The transcoder has less PCM types than the BSC has pools. This results in the fact that when you are checking the PCM circuits from the transcoder end, the PCM types are different than the pools in the BSC.

Supported codecs and software Supported A-interface pools

FR, HR, EFR, AMR, 14.4D, AEC, TFO, NS, TTY

1 (FR), 3 (DR), 5 (EFR&FR), 7 (EFR&DR), 20 (EFR&DR&D144), 23 (AMR), 28 (EFR&DR&AMR&D144)

FR, HR, EFR, AMR, HSCSD, 14.4D, AEC, TFO, NS, TTY

10 (HS2), 21 (HS2&D144)

FR, HR, EFR, AMR, HSCSD, 14.4D, AEC, TFO, NS, TTY

13 (HS4), 22 (HS4&D144), 32 (EFR&DR&AMR&HS4&D144)

AMR-WB 37,38,40

Table 28 Possible combinations of circuit pools (TCSM3i)

68 DN9812243

BSS Integration



12 Add through connected channels (WGA).ZWGA:<highway pcm circuit>:<tc_pcm circuit>;

13 Output and check the through connected channels (WGO).ZWGO:<highway pcm number>:<output mode>;

Further informationFor more detailed information on the commands, see Configuring the TCSM3i in Creating and Managing the BSC Hardware.

5.4.2 Creating TCSM3i for combined BSC/TCSM installationThe growing capacity of the BSC results in the increased transmission capacity between the BSC and the MSC. For example, the BSC3i 2000 has a capacity of 12000 erlangs. This means the user has to configure 99/124 PCM cables between the BSC and the transcoders, translating to 396/496 A-interface PCM cables. To avoid using such a huge number of PCM cables, synchronous transmission on optical media (cable) is intro-duced.

In the ETSI environment, synchronous transmission is standardised by Synchronous Digital Hierarchy (SDH). Interface to optical media is called STM-N, where N defines the transmission speed.

In ANSI environment synchronous transmission is standardised by SONET and inter-face is called OC-x, where x defines the transmission speed. One STM-1 interface can handle 63 E1 PCM's capacity and one OC-3 interface can handle 84 T1 PCM's capacity.

Figure 15 Configuration of the TCSM3i for combined BSC/TCSM installation

g For the details on TCSM3i combined upgrade procedure, please refer the SW Release documentation: BSC/TCSM HW implementation for combined installation.

Remote BSC is connected to master BSC by using traditional PCM cable

Remote BSC (A)Master BSCcabinet

TCSM3i cabinet

MSCET unit

ET unitPCM cable

STMU

STMU

STMU

Remote BSC (B) is connected to master BSC by using optical cable

Remote BSC (B)

TR3E PIU

Optical transmission

DN9812243 69



TCSM3i for combined BSC/TCSM implements same transcoding functionality and features as standalone version. It is possible to distribute TCSM3i's capacity between several BSCs. The BSC3i which is combined or installed together with the TCSM3i is called the Master BSC. A Remote BSC is located away from the TCSM3i and its Ater PCMs are connected to TCSM3i cabinet via Master BSC's E1/T1 PCM lines, optical STM-1/OC-3, or IP/Ethernet (GigE) connections.

1. Creating TCSM unit to Master BSCThe Master BSC must always be a BSC3i 1000, BSC3i 2000 or Flexi BSC.

2. Sharing TCSM3i for combined BSC/TCSM transcoding capacity to remote BSCA Remote BSC can be BSC3i 1000, BSC3i 2000, Flexi BSC, or even older models. If the remote BSC does not support IP/Ethernet (GigE) or optical interfaces, ET inter-faces can be used.If the BSC in a combined BSC/TCSM installation is BSC3i 1000, it is possible to install up to three TCSM3i cabinets. With Flexi BSC there can only be one TCSM3i cabinet.

The procedure below contains the ETSI command examples for creating the transcoder into the Master BSC. You can find more detailed information in the document BSC3i upgrade for combined BSC/TCSM in the release binder.

Steps

1 Create the CLAB.ZWTC:CLAC_B,1D1-0:;

ZWTU:CLAB,2:1D1-0;

ZWTP:CLAB,2:CLAB_S,0,3;

ZWTU:CLAB,3:1D1-0:;

ZWTP:CLAB,3:CLAB_S,1,4;

2 Create the TCSA cartridge.ZWTJ:TCSA,1D:AL=1D1-0-3R1,PDFU=2;

3 Create the STMU or ETIP.

a) Create the cartridge:ZWTC:GT4C_A,1D1-3:AL=1D1-0-2S3;

b) Create the functional unit:ZWTU:<STMU or ETIP>,32:1D1-3;

c) Create the plug-in unit:ZWTP:STMU,32:ETS2,0,5:LAPD,8,882,TSL,0&&15;orZWTP:ETIP,32:ETIP1_A,0,5:LAPD,8,882,TSL,0&&3;

d) Connect the plug-in unit:ZWUC:STMU,32:ETS2,0::BCSU,0;orZWUC:ETIP,32:ETIP1_A,0::BCSU,0;

e) Change the STMU state to WO-EX with the MML command USC.

70 DN9812243

BSS Integration



4 Create the SBMUX.ZWTU:GSW,0:1D1-3:MAS=MCMU;

ZWTU:GSW,1:1D1-6:MAS=MCMU;

ZWTP:GSW,0,1D1-3:SBMUX_A,0,1;




5 Create the TCSM unit.

a) Create the cartridge:ZWTC:TC2C_A,1D2-0:AL=1D1-0-2R3;

b) Create the functional unit:ZWTU:TCSM,1280:1D2-0;

c) Create the TR3E plug-in unit:ZWTP:TCSM,1280,1D2-0:TR3E,0,1::GENERAL,8,1280,TSL,1;

d) Create a LAPD link to the TR3E plug-in unit:ZWUC:TCSM,1280:TR3E,0:;After this link is created, this event information is sent to NetAct.

6 Create the A-interface ET units into the STMU or ETIP.

a) Create the functional units:ZWTU:ET,3392&&3454:1D1-3:UNIT=STMU,IND=32:IF=0;orZWTU:ET,3392&&3454:1D1-3:UNIT=ETIP,IND=32;Note that the ET range in ANSI is from 3392 to 3475.

b) Create the plug-in units into the ET unit:ZWTP:ET,3392&&3454:<ETS2 or ETIP1_A>,0,5:ETT00,8,3392&&3454,TSL,0;

c) Connect the ET units:ZWUC:ET,3392&&3454:<ETS2 or ETIP1_A>,0:IF=A:BCSU,0;

d) Change the ET state to WO-EX with the MML command USC.

7 Create transcoder configuration.

a) Set the number of through connections.ZWGS:1280:1;

b) Create the TC-PCM with the MML command WGC:ZWGC:1280,1:POOL=1:BCSU,1;ZWGC:1280,2:POOL=1:BCSU,4;ZWGC:1280,3:POOL=1:BCSU,5;ZWGC:1280,4:POOL=1:BCSU,6;

t The fifth TC-PCM can be used in ANSI environment.

c) Create the through connections.ZWGA:1280-30:1-24;

DN9812243 71



d) Change TCSM3i state from SE-NH to TE-EX with the MML command USC.e) The TR3E starts downloading its software from the BSC.

After successfully downloading software, run the diagnostics with the MML command UDU and change the TCSM state to WO-EX with the command USC.

8 Create circuit group.ZRCC:TYPE=CCS,NCGR=ATERTEST,CGR=1:DIR=IN,NET=NA0,SPC=200,LSI=AINA0;

9 Add circuit to CGR.ZRCA:CGR=1:ETPCM=1280,CRCT=1-1&&-31:CCSPCM=1;

ZRCA:CGR=1:ETPCM=1280,CRCT=2-1&&-31:CCSPCM=2;



10 Change the circuit states.ZCEC: ETPCM=1280,CRCT=1-1&&-31:BL;

ZCEC: ETPCM=1280,CRCT=1-1&&-31:WO;

ZCEC: ETPCM=1280,CRCT=2-1&&-31:BL;






Further informationFor detailed instructions on how to configure the remote BSC, see Configuring TCMS3i for combined BSC/TCSM installation

5.4.3 Creating the TCSM2The TCSM2 is a functional unit of the BSC. The BSC monitors the TCSM2 by using a LAPD link which is connected from the TCSM2's Transcoder Controller (TRCO) to the BSC's Operation and Maintenance Unit (OMU). The LAPD link is allocated to the 2 Mbit/s PCM frame (ETSI) or 1.5 Mbit/s T1 frame (ANSI) that carries the TCH/CCS7 between the MSC and the BSC. It is a 16 kbit/s link using the first two bits in time slot one (for ETSI, see figure Time slot allocation for full-rate traffic on Ater 2Mbit/s interface with the TCSM2 (ETSI) and for ANSI, figure A interface time slot allocation (ANSI)). In addition to monitoring, the LAPD link is also used for configuring, alarms, remote MMI sessions, and for software downloading to the TCSM2.

The TCSM2 software is kept in the BSC's hard disks and consists of three modules; software for the TRCO units, for the ET2E/A, ET2E-C, ET2E-S/SC, ET2E-T(B), ET2A-T(B), or ET2E-TC(B) units, and for the TR16 (ETSI) or TR12 (ANSI) units. These software modules are downloaded to the TCSM2 when necessary, that is when there is no software in the TCSM2 or it is different from that in the BSC.

72 DN9812243

BSS Integration



One TCSM2 rack can contain up to eight transcoder units as shown in figures TCSM2 rack and cartridges (ETSI) and TCSM2 rack and cartridges (ANSI). Each transcoder unit consists of the transcoder cartridge and one ET cartridge having up to four ET2E/A, ET2E-C, ET2E-S/SC, ET2E-T(B), ET2A-T(B), or ET2E-TC(B) plug-in units.

Figure 16 TCSM2 rack and cartridges (ETSI)

TCSM2

0 1 2 3

TC1C

tracks: 0

TRCO

1

TR16

2

TR16

3

TR16

4

TR16

5

TR16

6

TR16

7

TR16

8

TR16

9

TR16

10

TR16

11

TR16

12

TR16

13

TR16

14

TR16

15

PSC1

ET1TC

tracks: 3210

tracks: 7654

ET2E

ET2E

ET2E

ET2E

ET2E

ET2E

ET2E

ET2E

(TCSM2 0) (TCSM2 2)

(TCSM2 1) (TCSM2 3)

(TCSM2 4) (TCSM2 6)

(TCSM2 5) (TCSM2 7)

POWER INPUT BLOCK

TC1C 0

TCSM2 0

TC1C 2

TCSM2 2

TC1C 1

TCSM2 1

TC1C 3

TCSM2 3

TC1C 4

TCSM2 4

TC1C 6

TCSM2 6

TC1C 5

TCSM2 5

TC1C 7

TCSM2 7

ET indexes and tracks: (higher part)ETs 0 and 1: track 0ETs 2 and 3: track 1ETs 4 and 5: track 2ETs 6 and 7: track 3

ET indexes and tracks: (lower part)ETs 0 and 1: track 4ETs 2 and 3: track 5ETs 4 and 5: track 6ETs 6 and 7: track 7

Coordinates of the cartridges:ET 0: nnc120-01 nn = rowET 1: nnc120-13 c = rackET 2: nnc120-49ET 3: nnc120-61TC1C 0: nnc088-01TC1C 1: nnc088-37TC1C 2: nnc058-01TC1C 3: nnc058-37TC1C 4: nnc030-01TC1C 5: nnc030-37TC1C 6: nnc002-01TC1C 7: nnc002-37

DN9812243 73



Figure 17 TCSM2 rack and cartridges (ANSI)

The TCSM2 rack, transcoder and ET cartridges along with the plug-in units are created to the BSC's equipment database. It is important to create the configuration and espe-cially the transcoder ETs correctly to the BSC since they are used to define the type and the number of the A interface PCMs (in ETSI) or T1s (in ANSI). This information is used by the transcoder when it configures its PCMs/T1s during restart.

The procedure consists of the following phases:

• Configuring the hardware for the TCSM2 (steps 1–8) • Connecting the TCSM2 functional units (steps 9–14) • Configuring the TCSM2 (steps 15–16)

In this procedure, parameter unit index refers to the number of the ET in the BSC.

Steps

1 Create the rack for TCSM2 (WTJ).ZWTJ:TC2E,<rack or cabinet coordinate>:PSFP=2,PSA=2;

Coordinates of the cartridges:

ET 0: nnc120-01 nn = rowET 1: nnc120-13 c = rackET 2: nnc120-49ET 3: nnc120-61TC1C 0: nnc088-01TC1C 1: nnc088-37TC1C 2: nnc058-01TC1C 3: nnc058-37TC1C 4: nnc030-01TC1C 5: nnc030-37TC1C 6: nnc002-01TC1C 7: nnc002-37

ET indexes and tracks: (lower part)

ETs 0 and 1: track 4ETs 2 and 3: track 5ETs 4 and 5: track 6ETs 6 and 7: track 7

ET indexes and tracks: (higher part)

ETs 0 and 1: track 0ETs 2 and 3: track 1ETs 4 and 5: track 2ETs 6 and 7: track 3

TCSM2

TCSM2 0

(TCSM2 0)

(TCSM2 1)

(TCSM2 2)

(TCSM2 3)

(TCSM2 4)

(TCSM2 5)

(TCSM2 6)

(TCSM2 7)

TCSM2 2

TCSM2 4

TCSM2 6 TCSM2 7

TC1C

tracks:

TRCO

TR12

TR12

TR12

TR12

TR12

TR12

TR12

TR12

TR12

TR12

TR12

TR12

TR12

TR12

PSC1

ET1TC

tracks: 3

ET2A

2

ET2A

1

ET2A

0

ET2A

tracks: 7

ET2A

6

ET2A

5

ET2A

4

ET2A

TCSM2 1

TCSM2 3

TCSM2 5

TC1C 0

0 1 2 3

TC1C 2

TC1C 4

TC1C 6 TC1C 7

TC1C 1

TC1C 3

TC1C 5

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

POWER INPUT BLOCK


rack or cabinet coordinate Coordinate of the TCSM2.

74 DN9812243

BSS Integration



2 Create a cartridge for the TC1C (WTC).ZWTC:TC1C,<cartridge coordinate>:P1=<coordinate>;

3 Create the TCSM unit (WTU).ZWTU:TCSM,<unit index>:<cartridge coordinate>;

4 Create transcoder controller plug-in unit, TRCO (WTP).ZWTP:TCSM,<unit index>:TRCO,0,0::GENERAL,2,<unit index>,TSL,1;

5 Create TR16/TR12 plug-in units (WTP).Two plug-in units are needed for each A interface PCM/T1:

ZWTP:TCSM,<unit index>:<piu type>,<piu index>,<track>;

6 Create the ET1TC cartridge (WTC).ZWTC:ET1TC,<cartridge coordinate>;

7 Create the unit ET1TC cartridge (WTU).ZWTU:TCSM,<unit index>:<coordinate of cartridge>;


cartridge coordinate Coordinate of the transcoder unit. See figure TCSM2 rack and cartridges (ETSI) or TCSM2 rack and car-tridges (ANSI).


cartridge coordinate Coordinate of the transcoder unit. See figure TCSM2 rack and cartridges (ETSI) or TCSM2 rack and car-tridges (ANSI).


piu type ETSI: TR16, ANSI: TR12.

piu index Index of the TR16/TR12.

track Track of the TR16/TR12. For the right values, see figure TCSM2 rack and cartridges (ETSI) or TCSM2 rack and cartridges (ANSI).


cartridge coordinate Coordinate of the ET1TC cartridge. See figure TCSM2 rack and cartridges (ETSI) or TCSM2 rack and car-tridges (ANSI).

DN9812243 75



8 Create ET2E/A, ET2E-C, ET2E-S/SC, ET2E-T, ET2A-T, or ET2E-TC plug-in units (WTP).ZWTP:TCSM,<unit index>,<unit coordinates>:<piu type>,<index>,<track>;


9 Check that the A interface ETs and the connectable plug-in units of the TCSM2 are connected in the right order.They should be connected in the following order:

a) A interface ET. See Connecting the A interface ET.b) At least one ET of the TCSM2.c) TRCO of the TCSM2.

The ETs of the TCSM2 must be connected in ascending order starting from ET number one. The highway PCM is not connected.

g To delete the TCSM2, disconnect the units in reverse order.


11 Create transcoder PCMs (WGC).ZWGC:<highway pcm number>,<tc_pcm number>:POOL=<transcoder pcm pool numbers>:BCSU,<controlling unit index>;


coordinate of cartridge Coordinate of the ET1TC cartridge. See figure TCSM2 rack and cartridges (ETSI) or TCSM2 rack and cartridges (ANSI).


unit coordinates Coordinate of the ET1TC cartridge.

piu type ETSI: ET2E, ET2E-C, ET2E-S/SC, ET2E-T* or ET2E-TC*.

ANSI: ET2A or ET2A-T*.

piu index Index of the ET2E/A.

track Track of the ET2E/A. For the right values, see figure TCSM2 rack and cartridges (ETSI) or TCSM2 rack and cartridges (ANSI).

76 DN9812243

BSS Integration



The table below shows which A-interface pools support which codecs and application software.

12 Connect the TRCO to the BSC (WUC).This command creates the LAPD link between the BSC and the TCSM2. A circuit group DTCSM and the circuit to it are created at the same time.

ZWUC:TCSM,<unit index>:TRCO,0;

13 Change the state of the TCSM2 to WO-EX (USC).This command automatically changes the state of the TCSM LAPD link to WO-EX. If the TCSM2 software does not exist or is different from that in the BSC, it is downloaded in this phase.

14 Check the state of the TCSM2 LAPD link (DTF).ZDTF:TCSM,<unit index>:OMU;

The transcoder has less PCM types than the BSC has pools. This results in the fact that when you are checking the PCM circuits from the transcoder end, the PCM types are different than the pools in the BSC. The following execution printouts illustrate this:

Example: Printout from the BSC (ETSI)ZWGO:36;EXECUTION STARTED


pool type. ANSI: NU = not used.

Used in the first pool if the TCSM2A-C is in use.

controlling unit index Index of the BCSU controlling the speech circuits.

Supported codecs and software Supported A-interface pools Circuit type

FR, HR, EFR, AMR, 14.4D, HSCSD, AEC, TFO, NS, TTY

1 (FR)

2 (HR)

3 (DR)

5 (EFR & DR)

7 (EFR & DR)

20 (EFR & DR & D144)

23 (AMR)

G

10 (HS2)

21 (HS & D144)

H

13 (HS4)

22 (HS4 & D144)

I

Table 29 Possible combinations of circuit pools

DN9812243 77



ET_PCM 36 TC_PCM POOL TYPE ET_PCM_TSLSTCSM-36 TCSM2 1 21 EFR&DR&HS2&D144 1 && 16 2 23 AMR 17 && 24 3 2 HR 25 && 28 4 22 EFR&DR&HS4&D144 29 && 30 THROUGH CONNECTIONS NR64 = 1 36 - 31 <--> 1 - 16

COMMAND EXECUTED

Example: Printout from the transcoder (ETSI)ZDDX:TCSM,36:"ZRD";

TCSM_036:LUC> ZRD

/* TRANSCODER PCM TYPES */

GROUP SWITCH GSWB

PCM TYPE

PCM-1 EFR & FR & HR & HS2 & D144PCM-2 AMRPCM-3 HRPCM-4 EFR & FR & HR & HS4 & D144PCM-5 NUPCM-6 NUPCM-7 NU

/* COMMAND EXECUTED */

Example: Printout from the BSC (ANSI)ZWGO:32&&35;

EXECUTION STARTED

ET_PCM 32 TC_PCM POOL TYPE ET_PCM_TSLSTCSM-32 TCSM2 1 - NU - 2 23 AMR 1 && 6 3 5 EFR&FR 7 && 12 4 21 EFR&FR&HS2&D144 13 && 22 THROUGH CONNECTIONS NR64 = 2 32 - 24 <--> 2 - 24

ET_PCM 33 TC_PCM POOL TYPE ET_PCM_TSLSTCSM-33 TCSM2 1 - NU - 2 13 EFR&FR&HS4 2 && 20 THROUGH CONNECTIONS NR64 = 4 33 - 24 <--> 2 - 16

ET_PCM 34 TC_PCM POOL TYPE ET_PCM_TSLS

78 DN9812243

BSS Integration



TCSM-34 TCSM2 1 5 EFR&FR 1 && 6 2 10 EFR&FR&HS2 7 && 18 3 13 EFR&FR&HS4 19 && 23 THROUGH CONNECTIONS NR64 = 1 -

ET_PCM 35 THROUGH CONNECTIONSTCSM-35 TCSM2 -

COMMAND EXECUTED

Example: Printout from the transcoder (ANSI-C)ZDDX:TCSM,32:"ZRD";

TCSM_032:LUC> ZRD

/* TRANSCODER PCM TYPES */

GROUP SWITCH GSWB

PCM TYPE

PCM-1 NUPCM-2 AMRPCM-3 FR & EFR & D144PCM-4 EFR & FR & HR & HS2 & D144PCM-5 NUPCM-6 NUPCM-7 NU

/* COMMAND EXECUTED */

15 Add through connected channels (WGA).ZWGA:<highway pcm circuit>:<tc_pcm circuit>;

16 Output and check the through connected channels (WGO).ZWGO:<highway pcm number>:<output mode>;

Further informationNext, create the MTP.

Limitations in Multimedia Gateway (MGW) line card IW1S1 capacityWhen using TDM over STM-1 (IW1S1/IW1S1-A units) for user plane traffic, the capacity may be limited. The total IW1S1 capacity in U3B & U3C is 1602 timeslots.

For more information on this limitation, see the section IW1S1 and IW1S1-A with MX622 capacity limitation for user plane traffic in Routing and Digit Analysis in MGW in the Mul-timedia Gateway Product Documentation.

DN9812243 79



Degradation of TCSM3i capacity can be totally avoided if SDH multiplexer is used between TCSM3i and MGW.

The maximum capacity of TCSM3i in combined installation can not be fully used due to the limitation of MGW line card. A maximum of 7896 channels of the TCSM3i capacity can be used in ETSI environment. An alternative to overcome the ill effects of this limi-tation is to leave four TR3E plug-in units in every TC2C cartridge unequipped in the TCSM3i for combined BSC/TCSM. This results in the MGW supporting the TCSM3i with a maximum of 7680 channels in an ETSI installation.

5.5 Creating Ater Connection to Multimedia GatewayMultimedia Gateway (MGW) implements the same base transcoding functionality and features as TCSM. However, MGW does not support the same pool set as the BSC. Fur-thermore, MGW and TCSM3i do not support 8kbit/s submultiplexing on Ater interface, but TCSM2 does.

There is no O&M LAPD link between BSC and MGW so BSC does not control MGW at all. This means that the user is responsible for creating identical transcoder configura-tions to both BSC and MGW. Since there is no LAPD link, there is no need to equip TCSM functional unit into the BSC HW database.

Capacity TR3E TC2C

TR3E 1 120 120

TR3E 2 120 240

TR3E 3 120 360

TR3E 4 80 440

TR3E 5 0 440

TR3E 6 89 529

TR3E 7 120 649

TR3E 8 120 769

TR3E 9 93 862

TR3E 10 0 862

TR3E 11 58 920

TR3E 12 120 1040

TR3E 13 120 1160

TR3E 14 120 1280

TR3E 15 0 1280

TR3E 16 0 1280

TCSM3i Capacity 7680

Table 30 TCSM3i capacity with four TR3E unequipped

80 DN9812243

BSS Integration



Figure 18 Ater interface with MGW

Steps


2 Create transcoder PCMs (WGC).ZWGC: <highway pcm number>,<tc_pcm number>:POOL=<transcoder pcm pool numbers>:BCSU, <controlling unit index>;

RAN CN

BSC Nokia or otherMSC

MGW

2G TC

BSC NSS

Ater

A

8k/16k/32k/64k

64k/56k

16k/32k/64k

Ater

TCSM

Pool number

Supported codecs SubChannel

1 FR (Full Rate) 16 kbit/s

3 DR* 16 kbit/s

5 EFR (Enhanced Full Rate) & FR 16 kbit/s

7 EFR & DR* 16 kbit/s

10 HS2 (HSCSD max 2 x FR data) & EFR & DR* 32 kbit/s

13 HS4 (HSCSD max 4 x FR data) & EFR & DR* 64 kbit/s

Table 31 Circuit pools and supported codecs (with SubChannel bit information) when using MGW

DN9812243 81



g *DR means Dual Rate, that is, both GSM-FR (FR) and GSM-HR (HR, Half Rate) codecs are defined to be supported by the pool. However, in MGW, HR is an optional feature and is supported only if the user has purchased a separate HR licence; whereas FR is always supported.

For more information, see Multimedia Gateway (MGW) Functional Description in Multi-media Gateway Product Documentation.

Example: Printout of transcoder configurationsZWGO:100:;

EXECUTION STARTED

ET_PCM 100 TC_PCM POOL TYPE ET_PCM_TSLS 1 5 EFR&FR 1 && 8 2 5 EFR&FR 9 && 16 THROUGH CONNECTIONS -

COMMAND EXECUTED

Example: Setting the number of through connectionsZWGS:100:2:;

EXECUTION STARTED

/*** TCSM NOT EQUIPPED - THIS CONFIGURATION IS POSSIBLE ONLY WHEN TRANSCODING IS PROVIDED BY SOME OTHER DEVICE ***/

CONFIRM COMMAND EXECUTION: Y/N ?

Example: Creating a TC_PCMZWGC:100,:POOL=5:BCSU,5:;

EXECUTION STARTED

20 EFR & DR & D144 (14.4 kbit/s data speed)* 16 kbit/s

21 HS2 & EFR & DR & D144* 32 kbit/s

22 HS4 & EFR & DR & D144* 64 kbit/s

23 AMR (HR AMR & FR AMR) 16 kbit/s

28 EFR & DR & AMR & D144* 16 kbit/s

32 EFR & DR & AMR & HS4 & D144* 64 kbit/s

37 AMR & FR AMR-WB 16 kbit/s

Pool number

Supported codecs SubChannel

Table 31 Circuit pools and supported codecs (with SubChannel bit information) when using MGW (Cont.)

82 DN9812243

BSS Integration



/*** TCSM NOT EQUIPPED - THIS CONFIGURATION IS POSSIBLE ONLY WHEN TRANSCODING IS PROVIDED BY SOME OTHER DEVICE ***/

CONFIRM COMMAND EXECUTION: Y/N ? Y

ET_PCM 100 TC_PCM POOL TYPE ET_PCM_TSLS 1 5 EFR&FR 1 && 8

UPDATING FILES TO DISK. WAIT 4 SECONDS.

COMMAND EXECUTED

5.6 Creating the MTPSteps

1 Create signalling links (NCC).It is strongly recommended to have at least two signalling links in the A interface. Fur-thermore, the links should not be controlled by the same Base Station Controller Unit (BCSU).

ZNCC:<signalling link number>:<external PCM-TSL>,<link bit rate>:BCSU,<unit number>:<parameter set number>;

2 Create the local signalling point code (NRP).ZNRP:<signalling network>,<bsc signalling point code>,<bsc signalling point name>,SEP:STAND=<ss7 standard>:<number of spc subfields>;


parameter set number ETSI: value 0 is recommended.

ANSI SS7: value 2 must be used.


ss7 standard ETSI: ITU-T is usually used.

ANSI: ANSI is recommended.

number of spc subfields ETSI: value 1 is usually used.

ANSI: value 3 is usually used.

DN9812243 83



3 Create the signalling link set (NSC).To implement this step, choose one of the following alternatives:

a Create the signalling link set for the control plane directly to the MSS.ZNSC:<signalling network>,<msc signalling point code>,<msc signalling link set name>:<signalling link number>,<signalling link code>;

The signalling link code of the signalling link must be the same as the code of the corresponding link in the MSC.

You can add up to four signalling links to the signalling link set. Repeat the last three parameters for each signalling link.

b Create the signalling link set for the Ater interface transparently via the MGW to the MSC Server.ZNSC:<signalling network>,<mgw signalling point code>,<mgw signalling link set name>:<signalling link number>,<signalling link code>;

The parameters signalling network and signalling point code define the network element where the signalling link set leads to.

4 Add links to the signalling link set (NSA).This step is needed only if all the links were not added to the link set in the previous step.

ZNSA:<signalling network>,<msc or mgw signalling point code>,<msc or mgw signalling link set name>:<signalling link number>,<signalling link code>;

5 Create the signalling route set (NRC).To implement this step, choose one of the following alternatives:

a Create the signalling route set for the control plane directly to the MSS.ZNRC:<signalling network>,<msc signalling point code>,<msc signalling point name>,<parameter set number>,<load sharing status>,<restriction status>:,,,0;

b Create the signalling route set for the Ater interface transparently via the MGW to the MSC Server.Direct connections:

ZNRC:<signalling network>,<mgw signalling point code>,<mgw signalling point name>,<parameter set number>,<load sharing status>,<restriction status>:,,,0;


parameter set number Value 1 is recommended.

load sharing status D is recommended.

restriction status R is recommended.

84 DN9812243

BSS Integration



STP configurations:

ZNRC:<signalling network>,<mss signalling point code>,<mss signalling point name>,<parameter set number>,<load sharing status>,<restriction status>:<mgw signalling transfer point code>,<mgw signalling transfer point name>,0;

6 Allow activation of the signalling links (NLA).ZNLA:<signalling link numbers>;

7 Allow activation of the signalling route (NVA).To implement this step, choose one of the following alternatives:

a Allow activation of the signalling route for the control plane directly to the MSS.ZNVA:<signalling network>,<msc or mss and mgw signalling point code>:;

b Allow activation of the signalling route for the Ater interface transparently via the MGW to the MSC Server.ZNVA:<signalling network>,<msc or mss signalling point code>:<signalling network>,<mgw signalling point code>;

8 Change signalling link states (NLC).ZNLC:<signalling link numbers>,ACT:;

9 Change route set state (NVC).To implement this step, choose one of the following alternatives:

a Change route set state for the control plane directly to the MSS.ZNVC:<signalling network>,<msc or mss and mgw signalling point code>::ACT;

b Change route set state for the Ater interface transparently via the MGW to the MSC Server.ZNVC:<signalling network>,<msc or mss signalling point code>:<signalling network>,<mgw signalling point code>:ACT;

Further informationNext, create the SCCP.


parameter set number Value 0 is recommended in STP configurations, value 1 for direct connections

load sharing status D is recommended.

restriction status N is recommended in STP configurations, R for direct con-nections.

DN9812243 85



5.7 Creating the SCCPThe parameter values shown in the table apply in each step in this procedure.

Steps

1 Create service (NPC).ZNPC:<signalling_network>,03,SCCP:Y:Y,208,10F;

2 Define SCCP for the BSC's own signalling point (NFD).ZNFD:<signalling network>,<bsc signalling point code>,<signalling point parameter set number>:<subsystem number>,<subsysten name>,<subsystem parameter set number>,;

3 Define SCCP for the MSC's or MSS's signalling point (NFD).ZNFD:<signalling network>,<msc or mss signalling point code>,<signalling point parameter set number>:<subsystem number>,<subsystem name>,<subsystem parameter set number>;

See the previous step for recommended parameter values.

4 Modify broadcast status of SCCP signalling points (OBM).ZOBM:<signalling network>,<bsc signalling point code>,<subsystem name>::Y;


subsystem number ETSI: FE, ANSI: DE.

subsystem name ETSI: BSSAP, ANSI: RSAP.


signalling point parameter set number ETSI: value 1 is recommended.

ANSI: no recommended value.



subsystem parameter set number ETSI: value 1 is recommended.

ANSI: no recommended value.




86 DN9812243

BSS Integration



5 Modify the local broadcast status of SCCP subsystems (OBC).ZOBC:<signalling network>,<msc or mss signalling point code>,<subsystem name>::Y;

6 Change the SCCP state at BSC side (NGC).ZNGC:<signalling network>,<bsc signalling point code>:ACT;

7 Change the SCCP state at MSC side (NGC).ZNGC:<signalling network>,<msc or mss signalling point code>:ACT;

8 Change subsystem state at BSC side (NHC).ZNHC:<signalling network>,<bsc signalling point code>:<subsystem>:ACT;

The value of the parameter subsystem is BSSAP in ETSI and RSAP in ANSI.

9 Change subsystem state at MSC or MSS side (NHC).ZNHC:<signalling network>,<msc or mss signalling point code>:<subsystem>:ACT;

The value of the parameter subsystem is BSSAP in ETSI and RSAP in ANSI.

Further informationSegmentation has to be used when Inter-System Handover (ISHO) is active.

Parameter 14 XUDT_USED determines whether the connectionless SCCP uses the segmentation. The recommended value is YES.

Parameter 15 UDT_DENIED determines whether unit data (UDT) is sent as a single extended unit data (XUDT) message. The recommended value is NO.

Parameter 26 LUDT_USED determines whether all messages are sent as long unit data (LUDT) messages without segmentation. The recommended value is NO.

Parameter 27 CO_SEGM_USED determines whether the connection oriented SCCP uses the segmentation. The recommended value is YES.

You can modify the values of SCCP signalling point parameter set with command ZOCM.

For more instructions, see section Optimising SCCP configuration in Common Channel Signalling (MTP, SCCP and TC).

Next, Creating the speech channels.




DN9812243 87



5.8 Creating the speech channelsSpeech circuits are used to carry the actual user data through the A interface. One circuit is needed for each ongoing call. With conventional hunting the circuit is chosen by the MSC which means the MSC has to know the circuits of the BSC and their status. That is why the circuits must be identified by both the MSC and the BSC. This is accom-plished by using CICcodes. A CIC code consists of the CCSPCM and the time slot of the circuit. The CIC codes must be the same at both ends.

Reversed Hunting can be activated here. The following instructions apply when activat-ing it in a new BSC. If you want to change the BSC to use Reversed Hunting instead of normal hunting, see Activating and Testing BSS10005: Reversed Hunting.

For more information on Reversed Hunting, see Circuit configuration on the A interface in Half Rate, and A interface circuit allocation in Radio Channel Allocation.

Note that Multipoint A Interface cannot be used if Reversed Hunting is activated.

Figure 19 Multiplexed and non-multiplexed A interface with 8 kbit GSWB

Steps

1 Create a circuit group (RCC).ZRCC:TYPE=CCS,NCGR=<ciruit group name>,CGR=<circuit group number>:DIR=<direction>,NET=<signalling network>,SPC=<msc signalling point code>,LSI=<line signalling>;

Note that the circuit group name must have the same name as the one created for MSC. In addition the circuit group SPC must be the same peer entity (e.g. MSC/MSS) with which the BSC is carrying 3GPP 48.008 BSSAP signalling.

BSCGSWB

MultiplexedA interface

Speech circuits

Non-multiplexedA interface

ET 32

ET 34

ETPCM 32

ETPCM 34


direction To activate Reversed Hunting: OUT.

If you do not want to activate Reversed Hunting: IN.

line signalling DUMMY, AINA0, AINA1, AIIN0, AIIN1, DSS01.

88 DN9812243

BSS Integration



2 Add circuits to the circuit group (RCA).If more speech circuits are needed they must be added to the previously created circuit group.

• ETSI:In multiplexed cases:ZRCA:NCGR=<circuit group name>:ETPCM=<etpcm>,CRCT=<circuit(s)>,CRCTSTEP=1:CCSPCM=<number of PCM system>:;In non-multiplexed cases:ZRCA:CGR=1:ETPCM=<etpcm>,CRCT=<circuits>:CCSPCM=<number of PCM system>:;Note that one to six (ETSI) or one to seven (ANSI) transcoder PCMs can be used towards the MSC if the BSC is equipped with the GSWB. The amount of PCMs and TSLs depends on channel types: 8 Kbit/s (HR), 16 Kbit/s, 32 Kbit/s (HS2), 64 Kbit/s (HS4, through connected signalling channels). The same transcoder unit can have PCMs of different types, and the channels can be of a multimode type.For more information, see the figures Time slot allocation for full-rate traffic on Ater 2Mbit/s interface with the TCSM2 (ETSI) and A interface time slot allocation (ANSI).

• ANSI:ZRCA:NCGR=<circuit group name>,ETPCM=<etpcm>,CRCT=<circuit(s)>,CIC=<circuit identification code>,CICDIR=<direction of CIC>;

3 Activate Reversed Hunting (optional).If you do not want to activate Reversed Hunting, go to step 4.

Steps

a Create route (RRC).ZRRC:EXT:ROU=<route number>,OUTR=AINTF,STP=1,NCGR=<circuit group name>;

g Route is created only if Reversed Hunting is used.

The route number must be the same as the circuit group number.

b Activate circuit group (CRM).ZCRM:NCGR=<circuit group name>:WO;

c Create circuit group for null PCM and add circuits (RCC, RCA).ZRCC:TYPE=SPE,NCGR=<circuit group name>,CGR=<circuit group number>:FORMAT=0,HUNTED=N;

ZRCA:NCGR=<circuit group name>,CRCT=0–0&-1;

d Activate Reversed Hunting (WOA).ZWOA:2,643,A;

DN9812243 89



4 Change the state of the speech circuits (CEC).Immediately after creation the circuits are in NU-US state. The state must be changed to WO-EX before the circuits can be used.

ZCEC:ETPCM=<etpcm>,CRCT=<circuit>:<state>;

ZCEC:ETPCM=<circuit>,CRCT=<circuit>:WO;


state If Reversed Hunting is used: BA.

If Reversed Hunting is not used: BL.

90 DN9812243

BSS Integration

Id:0900d805807f6fecConfidential

Synchronising the A interface

6 Synchronising the A interfaceFor an overview, see Overview of BSS integration.

Before you startThe A and Ater interface transport has been connected into operation between the core Network and the BSC. In the BSC the user has to select the ETs that will be used as synchronisation inputs and install the synchronisation cables between the selected ETs and the clock unit.

Normally three ETs are used for synchronisation. The synchronisation input with the highest priority (2M1) should be in the state CONNECTED and in use (USED INPUT). The other inputs (2M2 and 2M3) should be in the state CONNECTED.

Steps

1 Check the state of the synchronisation (DRI).ZDRI;

Expected outcomeNormally, it gives the following output:

CL1TG:

INPUT STATE USED INPUT PRIORITY----- --------------- ---------- ----------2M1 CONNECTED 2M1 72M2 CONNECTED - 62M3 CONNECTED - 5SYNCHRONISATION UNIT WORKING MODE ......... HIERARCHIC SYNCHRONISATIONFUNCTION AUTOMATIC RETURN FROM PLESIOCHRONOUS OPERATION .......... ONSYNCHRONISATION UNIT 0 OSCILLATOR CONTROL WORD VALUE ....... 31896FUNCTION AUTOMATIC USE OF REPAIRED INPUTS ........................ ONSYNCHRONISATION UNIT 1 OSCILLATOR CONTROL WORD VALUE ....... 31635SYNCHRONISATION UNIT 0 OSCILLATOR CONTROL MODE ............. NORMALSYNCHRONISATION UNIT 1 OSCILLATOR CONTROL MODE ............. NORMALTIMER: SYNCHRONISATION SIGNAL MALFUNCTION TOLERANCE TIME ... 5 MINTIMER: REPAIRED SYNCHRONISATION INPUT OBSERVATION TIME ..... 10 MINCOMMAND EXECUTED

2 Create or delete synchronisation inputs if necessary (DRC, DRD).ZDRC:<synchronization input>;

ZDRD:<synchronization input>;

The number of possible synchronisation inputs depends on how many transport lines are connected between the core network and the BSC. The maximum number of A/Ater lines that can be used as synchronisation lines is 3 if CL1TG is used.


synchronization input 2M1, 2M2, 2M3

DN9812243 91

BSS Integration Synchronising the A interface


3 Change the supervision timers for the inputs if necessary (DRS).Use the DRS command.

4 Check if there are any faults.The following steps include typical faults and instructions on how to correct them.

Steps

a To implement this step, choose one of the following alternatives:

1 If The synchronisation units are not in synchronous operation mode.

Then

Force the synchronisation units to use a specific input (DRS).ZDRS::U=<2M1 - 2M4>;

2 If The CL1TG will search the entire control range in order to lock the units to a certain input.

Then

Wait for the alarm to be cancelled (which may take a couple of minutes) and remove the forced use of input (DRS).ZDRS::U=OFF;

3 If Operation mode is not hierarchical.

Then

Check that the operation mode has been set to hierarchical (DRM).ZDRM:H;

4 If The settings of the ETs are not correct.

Then

Check the settings of the ETs.The TCL signal should be 8 kHz. In ET1E it is selected by strapping, but in other ET variants it is 8kHz permanently.

5 If The control words of both CL1TGs approach the values 0 to 65534.

Then

Check the connection.It is possible that the incoming circuit is connected to a loop.

5 Change the synchronisation inputs.

Steps

a Disconnect the incoming signal from the first input.

Expected outcomeThis will cause normal circuit alarms. After a time delay of more than the timer: SYN-CHRONISATION SIGNAL MALFUNCTION TOLERANCE TIME allows, both syn-

92 DN9812243

BSS Integration


Synchronising the A interface

chronisation units will change to the second input. This can be seen in the LEDs of the CL1TG plug-in units and on the alarm printer:

2641 FAILURE IN SYNCHRONISATION SIGNAL

0630 SYNCHRONISATION SIGNAL CHANGED

b Disconnect the incoming signal from the second output.

Expected outcomeThe results should be similar to the earlier ones.

6 Go to plesiochronous mode of operation.Disconnect the incoming signal from the third input (the last synchronisation input has been disconnected) in CL1TG.

Expected outcomeThe synchronisation units will go to PLESIOCHRONOUS OPERATION mode. All syn-chronisation input indicators in the active CL1TG unit will extinguish, only the current indicator light is on. All 3/4 input indicators in the passive CL1TG unit are lit, but not the current indicator light. The alarm printer will print out the following:


2631 OPERATION MODE CHANGED TO PLESIOCHRONOUS

7 Return to synchronous mode of operation.Return the circuits to their normal state one by one starting from the circuit with the lowest priority.

Expected outcomeThe synchronisation units will synchronise themselves to the input 2M3/2M4 after a time delay of more than the timer REPAIRED SYNCHRONISATION INPUT OBSERVATION TIME. On the alarm printer the following alarms will be cancelled:


2631 OPERATION MODE CHANGED TO PLESIOCHRONOUS

8 Check possible slips in the synchronous mode of operation (YMO).ZYMO:ET,<index>:SLI;

The observation begins daily at 00.00 and should normally show no slips.

9 Check oscillator adjustments.The CL1TG has no adjustments in the synchronous mode of operation.

DN9812243 93

BSS Integration Adding DN2, SSS, DMR and BBM to the service chan-nel

Id:0900d805805cedebConfidential

7 Adding DN2, SSS, DMR and BBM to the service channelThe connection between the BSC and the managed equipment is established either through a BSC-BTS O & M link or a Q1 service channel. The possible equipment types at a Base Transceiver Station (BTS) site include Base Station Interface Equipment (BIE), Transmission Unit (TRU), Digital Microwave Radio Link (DMR), and other trans-mission equipment (TRE).

All equipment with the same alarm unit type must have a unique index in the BSC con-cerned. All equipment in the same channel must have a unique address.

DN2 The Q1 service channel comes in TSL31 bits 7-8 to the 2M port of the DN2 interface unit (IU2). The Q1 service channel is forwarded through an extra loop connection to the Control Unit (CU); either one port of the IU2 is connected to the 2M interface of the CU or two IU2 ports are con-nected together with a local cable. The supported baud rates of the service channel are 1200, 2400 and 4800.

SSS The Supervisory Substation is located in the same rack with other trans-mission equipment, normally with the DN2. The Q1 service channel is forwarded to the SSS with a local cable.

DMR The Digital Microwave Radio link cannot pick the Q1 service channel from a time slot. The Q1 service channel is forwarded to the DMR with a local cable from another source, normally DN2. The supported baud rates of the service channel are 1200, 2400, 4800, and 9600.

BBM The Baseband Modem cannot pick the Q1 service channel from a time slot. The Q1 service channel is forwarded to the BBM through an Inte-grated Line Terminal (ILT) plug-in unit from the DN2.

TRE Other types of transmission equipment, for example optical line equip-ment, are handled in the BSC with the common name Transmission Equipment (TRE).

Figure 20 Transmission equipment at Q1 service channel


MMI SYSTEM

MML

DN2

ILT

SSS

DMR

TRE

BBM

TRE Q1ch

Q1ch

NetActLocalQ1bus

X.25/

LAN

94 DN9812243

BSS Integration

Id:0900d805805cedebConfidential

Adding DN2, SSS, DMR and BBM to the service chan-nel

Steps

1 Create the service channel (QWC).ZQWC:<service channel number>, [S | P def]:<baud rate>,<bandwidth>,<used bits>:<external PCM-TSL>,<sub tsl>;

If you want to utilise Q1 bus protection in BSC, you must create secondary channels for all the primary Q1 channels that are to be protected.

2 Add equipment to the service channel (QWA).ZQWA:CH=<service channel number>:DN2=<DN2 index>:<alarm unit address 1>;

ZQWA:CH=<service channel number>:BBM=<BBM index>:<alarm unit address 2>;

ZQWA:CH=<service channel number>:DMR=<DMR index>:<alarm unit address 3>;

ZQWA:CH=<service channel number>:SSS=<SSS index>:<alarm unit address 4>;

ZQWA:CH=<service channel number>:TRE=<TRE index>:<alarm unit address 5>;

Addresses have to be set locally to the equipment with a hand-held service terminal.

3 Change the state of the service channel (QWS).ZQWS:<service channel number>:AL;

DN9812243 95

BSS Integration Creating the Abis interface

Id:0900d805805cedeeConfidential

8 Creating the Abis interfaceFor an overview, see Overview of BSS integration.

In this phase, the ET is connected to the Abis interface to connect the base stations to the BSC (see the figure below).

Figure 21 Abis interface

Steps

1 Check that the ET is connected (WUP).The ET must be connected before it can be used. For how to check if the ET is already connected, see Connecting the A interface ET.

Check that the ET is connected with the WUP command.


a If ET is already connected

Then

Check that the ET is in WO state and restart the ET (USU).The state of the ET can be changed with command USC.

The ET must be restarted to ensure that the correct ET software is loaded into the unit.

ZUSU:ET,<pcm_index>,C=TOT;

b If ET is not connected

Then

Connect the ET (WUC).ZWUC:ET,<ET index>:<plug-in unit type>,0:IF=ABIS:BCSU,<BSCU index>;

BTSBSC

ET TRU

Abis interface

OMU

TRX 1

TRX 2

TRX 3

OMUSIG

TRXSIG1 + 8 TCHs

TRXSIG2 + 8 TCHs

TRXSIG3 + 8 TCHs

96 DN9812243

BSS Integration

Id:0900d805805cedeeConfidential

Creating the Abis interface


Steps

a Change the state of the BCSU to WO-EX.

b Change the state of the ET to WO-EX.

3 Check and change the frame alignment mode (ETSI)/T1 functional mode (ANSI) for ET if needed.For more information about configuring the frame alignment mode/T1 functional mode, see Connecting the A interface ET.


plug-in unit type Type of the ET:

ETSI: ET1E, ET1E-C, ET2E, ET2E-C, ET2E-S, ET2E-SC, ET2E-T*, ET2E-TC*, ET4E, ET4E-C, ET16, ETS2 or ETIP1_A

ANSI: ET2A, ET2A-T*, ET4A, ET16, ETS2 or ETIP1_A.

DN9812243 97

BSS Integration Initialising base stations

Id:0900d805807d4158Confidential

9 Initialising base stationsEach base station has one LAPD link called OMUSIG (see figure Abis interface). It is connected to the Operation and Maintenance Unit (OMU) of the base station and used for O&M purposes like remote sessions to the BTS, software up- and downloading, transferring of alarms, and transferring of configuration information.

Each TRX has one LAPD link called TRXSIG and up to eight traffic channels. There can be fewer traffic channels if some of the TRXs' radio interface time slots are used for sig-nalling. The bit rate of the LAPD links can be either 16 or 64 kbit/s. Also 32 kbit/s is possible for TRX links.

In this phase, the LAPD links are created and the base stations are created to the BSC's radio network database. In terms of BSC, a base station consists of BCF, BTSs, TRXs, and handover and power control parameters.

The hardware database is attached only to Talk-family base stations. In the other types, the TEI of the TRX links is the same as the TRX number in the BSC. The TEI of the OMU links is always 1.

In the case of Flexi EDGE base stations, the TRXSIG links and traffic channels data created in the BSC can be downloaded and used by the Flexi EDGE base station auto-matically. For more information, see Flexi EDGE BTS Commissioning in the Flexi EDGE Base Station Product Documentation.

The following instructions apply to Talk-family, UltraSite EDGE, MetroSite, Flexi EDGE, Flexi Multiradio and BTSplus base stations.


9.1 Creating LAPD links and a base station, and initialising the base station parametersA LAPD link can be created either to a certain physical Base Station Controller Signal-ling Unit (BCSU) or to a logical BCSU address. When the link is created to a logical BCSU address the actual controlling unit may not necessarily be the one given in the command. The concept of logical BCSU address was introduced to eliminate the effect of BCSU switchovers to radio network planning. In terms of MMI commands, only the command name is different with logical BCSU addresses.

It depends on the type of the BTS which links must be created. For more information, see Creating D channels on Abis interface.

Steps

1 Create LAPD links (DSE).Create 16, 32 or 64 kbit LAPD links. Create the links for O&M signalling link (OMUSIG) and TRX signalling links (TRXSIG). If you are creating a 64kbit link, do not give <SUB-TSL>.

ZDSE:<D-channel link set name>:BCSU,<unit index>:<service access point identifier>,<terminal endpoint identifier>:<bitrate>,<PCM-TSL>,<SUB-TSL>;

98 DN9812243

BSS Integration


Initialising base stations

If logical BCSUs are used, use the DSL command with the same parameters.

2 Create a base control function (EFC).The base control function (BCF) is a logical counterpart of the actual base station. It is connected to the OMUSIG link created earlier.

As a default, the operational state of the new BCF is 'Locked' (L). It is recommended that you first create the entire BCF site (BCF, BTS, and the TRXs) and unlock the TRXs and BTSs of the BCF, before you change the state of the BCF to 'Unlocked'.

In the case of Flexi EDGE Base Station, the administrative state of BCF is also 'Locked' after creation, but it is created as 'Automatic Unlock Allowed' by default. It means that when the BTS site has been commissioned and it indicates the start up for the BSC, the BSC automatically changes the administrative state of the BCF to 'Unlocked'.

• All site types if it is being autoconfigured:ZEFC:<bcf identification>,<site type>:DNAME=<D-channel link set name>;

Further informationThe BCF parameters can be modified later with the EFM and EFT commands if needed.

3 Create a base transceiver station (EQC).A base transceiver station (BTS) is a logical counterpart of a sector in a base station site. It should not be confused with a base station even though they have the same abbrevi-ation.

ZEQC:BCF=<BCF identification>,BTS=<BTS identification>,NAME=<BTS name>,:CI=<cell identity>,BAND=<frequency band in use>:NCC=<network colour code>,BCC=<BTS colour code>:MCC=<mobile country code>,MNC=<mobile network code>,LAC=<location area code>:;

Further informationThe BTS parameters can be modified later with the EQE, EQF, EQG, EQH, EQJ, EQK, and EQM commands.

4 Create a transceiver (ERC).A transceiver (TRX) is a logical counterpart of the transmitter-receiver equipment in the base station. It is connected to the TRXSIG link created earlier.

• All site types if it is being autoconfigured:ZERC:BTS=<BTS identification>,TRX=<transceiver identification>::FREQ=<frequency>,TCS=<training sequence


service access point identifier 62 for OMUSIG, 0 for TRXSIG.

terminal endpoint identifier Must the same as defined in the BTS. Usually the same as the TRX number. For OMU link, the value is 1.

DN9812243 99



code>,PCMTSL=<Abis speech circuit>:DNAME=<D-channel telecom link set name>:CH0=<RTSL type 0>,SIGN=<subslots for signalling>;

Further informationThe TRX parameters can be modified later with the ERM command.

5 Create default power control parameters of the BTS (EUC).Each cell must have a power control parameter set.

ZEUC:BTS=<BTS identification>;

Further informationYou can modify the power control parameters with the EUG, EUA, EUQ, and EUS com-mands.

6 Create default handover control parameters (EHC).Each cell must have a handover parameter set.

ZEHC:BTS=<BTS identification>;

You can modify the handover control parameters with the EHG, EHA, EHS, EHQ, EHI, EHD, EHN, EHX, EHY, EHP commands.

7 Create neighbouring cell information (EAC).Define the list of cells where mobiles can make a handover when using the cell.

Create the adjacent cells.

• Adjacent cell located in the same BSC:ZEAC:BTS=<BTS identification>:ABTS=<adjacent cell identification>;

• Adjacent cell located in a different BSC:ZEAC:BTS=<BTS identification>:LAC=<location area code>,CI=<cell identification>:NCC=<network colour code>,BCC=<BTS colour code>,FREQ=<BCCH frequency>,:

The adjacent cell parameters can be modified with the EAM command.

8 Check and change the synchronisation of TalkFamily, UltraSite, Flexi EDGE, and MetroSite BTSs if necessary (EFM).Check that the synchronisation is suitable. The default is the internal clock of the BTS.

Change the synchronisation of the BCF to external synchronisation if necessary.

If the synchronisation settings are not defined or synchronisation is not enabled for the BCF(s) in the BSC Radio Network database, then the BTS site's own synchronisation settings are valid.

There are three alternative ways to define synchronisation for the BTS (and LMU) via BSC: the internal clock of the BTS, BSS synchronisation, and Site synchronisation.

For further information on changing synchronisation settings of base stations, see BSS Synchronisation.

100 DN9812243

BSS Integration



For instructions on changing the BTS site's synchronisation settings, see the relevant BTS documentation.

Further information

Example: Create a BCF according to the Abis time slot allocation shown in the table.

1. Create LAPD linksZDSE:B0001:BCSU,0:62,1:16,33-1,2;ZDSE:T0101:BCSU,0:0,1:16,33-1,0;ZDSE:T0102:BCSU,0:0,2:16,33-3,0;

2. Create BCFZEFC:1,P:DNAME=B0001;

3. Create BTS • ETSI:

ZEQC:BCF=1,BTS=1,NAME=BTS1:CI=1,BAND=900:NCC=0,BCC=0:MCC=214,MNC=1,LAC=1:;

• ANSI:ZEQC:BCF=1,BTS=1,NAME=CELL1:CI=1,BAND=1900:NCC=0,BCC=0:MCC=214,MNC=1,LAC=1:;

4. Create TRXsZERC:BTS=1,TRX=1::FREQ=100,TSC=0,PCMTSL=33-1:DNAME=T0001:SIGN=2,CH0=MBCCHC,CH1=NOTUSED;ZERC:BTS=1,TRX=2::FREQ=55,TSC=0,PCMTSL=33-3:DNAME=T0002:SIGN=1,CH0=NOTUSED;

The TRX parameters can be modified with the ERM command.

Further informationNext, attach the BCF software build to the BCF.

9.2 Attaching the BCF software build to the BCFBase station software is kept in the BSC's hard disks. There are 40 directories for BTS software builds and one directory for BTS hardware databases (see figure BTS software directories). Usually, only some of the directories are needed since the base stations can use the same builds with each other.

0 LINK MANAGEMENT

1 TRXSIG1 OMUSIG TCH.2 TCH.3 TRX 1

2 TCH.4 TCH.5 TCH.6 TCH.7

3 TRXSIG2 TCH.1 TCH.2 TCH.3 TRX 2

4 TCH.4 TCH.5 TCH.6 TCH.7

DN9812243 101



Figure 22 BTS software directories

Steps

1 Copy the BCF software build to the BSC's disks (IWX, IWY, IBC).Find an unused BCF software directory and copy the BCF software build to it from the floppy disk.

IWX, IWY, IBC

2 Create BTS software build (EWC).ZEWC:<build id>:MF=<master file name>,EXT=<master file extension>,SDIR=<subdirectory name>;

3 Set initial software build; optional (EWS).ZEWS:<site type>:<build id>;

4 Attach build to the BCF (EWA).If the Operation and Maintenance Unit (OMU) link is working, background downloading of the build to the base station is started. Otherwise, the build is only administratively attached to the BCF and the software is downloaded later.

ZEWA:<number of BCF>:BU:<build id>;

5 Activate the build (EWV).If the BCF is in unlocked state it is restarted as the build is activated. Otherwise, only the state of the build is changed to DEF.

ZEWV:<number of BCF>:BU;

6 Confirm the execution of the command.The program asks for a confirmation to execute the command. The command cuts all ongoing calls in the reseted BTS site. Confirm by YES (Y) or NO (N).

Further informationNext, attach the BTS hardware database to the BTS.

BTS SW files

AS8_8_14_0

ROOT

SCMANA BCF_PACK

PACK_0 PACK_39 HWDATA...

BTS SW files BTS HW databases

102 DN9812243

BSS Integration



9.3 Attaching the BTS hardware database to the BTS

t This is done only for Talk-family base stations.

The BTS hardware database contains the base station's hardware configuration. Hardware database files are kept in the BSC's hard disks in BCF_PACK\HWDATA directory as shown in figure BTS software directories.

Before you startBefore proceeding, you must have suitable hardware database files available. For infor-mation on how to prepare a BTS hardware database, see BTS documentation.

Steps


a If The BTS does not yet have a valid hardware database

Then

Once the BTS hardware configuration is available, copy it to the BSC.The database files are:

HWDATA_T.<ext> Database file in text format

HWDATAOM.<ext> Database file in binary format

b If The BTS already has a valid hardware database

Then

Upload the hardware database to the BSC (EVU).If the BTS already has a valid hardware database, it can be uploaded to the BSC instead of copying new files with the command EVU.

2 Create BCF hardware database (EVC).Once the hardware database files have either been copied or uploaded to the BSC, the database must be created.

ZEVC:<database id>:NAME=<file name>,EXT=<file extension>;

3 Attach hardware database to the BCF (EVA).ZEVA:<bcf identity>:<database id>;


a If The hardware database has already been downloaded to the BTS

Then

Activate the hardware database without downloading (EVV).ZEVV:<bcf identity>:PAS:NODL;

b If The hardware database is not in the flash

Then

DN9812243 103



Activate the hardware database with site reset (EVV).The Operation and Maintenace Unit (OMU) link must be operational before the downloading.

ZEVV:<bcf identity>:PAS:SITE;

c Activate the hardware database without site reset (EVV).After this command the hardware database is in the flash but not in use. Site reset is needed to take it into use:

ZEVV:<bcf identity>:PAS:NORST;

Further informationNext, take the base station into use.

9.4 Taking the base station into useIn this phase, the base station is taken into use by unlocking it.

Steps

1 Change status of BTS D-channels (DTC).Change the state of the Operation and Maintenance (OMU) link and the TRX links to WO-EX:

ZDTC:<D-channel link set name>:,WO;

2 Unlock the TRXs (ERS).If the higher level objects are already unlocked the transition from locked to unlocked causes a TRX reset in the BTS site. Otherwise, the reset is not done.

ZERS:BTS=<BTS identification>,TRX=<transceiver identification>:U;

3 Unlock the BTSs under the BCF (EQS).If the BCF is already unlocked the transition from locked to unlocked causes a BTS reset in the BTS site. Otherwise, the BTSs are not reset.

ZEQS:BTS=<BTS identification>:U;

4 Unlock the BCF (EFS).ZEFS:<BCF identification>:U;

Expected outcomeThe transition from locked to unlocked causes a BCF reset. While the BCF is resetting, all its components and the BCF itself are in BL-RST (blocked-reset) state. During that time, the BCF is not available for traffic nor controllable by MML.


D-channel link set name Name of the LapD link.

104 DN9812243

BSS Integration



The reset is over when all its components and the BCF itself are in WO (working) state.

DN9812243 105

BSS Integration Testing BSS integration

Id:0900d805805cedf4Confidential

10 Testing BSS integrationBefore you startThe test requires one of each network element (BTS, BSC, MSC, and HLR), and in fault conditions a PCM/T1 analyser (PC with GSM Protocol Analyser to trace A/Abis mes-sages). All the network elements and connections must be operative and the network configuration valid.

Figure 23 The test arrangements

The test cases are described in a general level. For more detailed information, refer to BSC SW release material: BSC System Test Cases and BSC Release Test Cases.


10.1 Testing local blocking of a TRXThe purpose of the test is to verify the correct working of the BSS in local blocking (OMU MMI) of a TRX

Steps

1 Check the status of the signalling network with a BSC MML.

2 Check current alarms in the system.

3 Check that the TRX and the BTS to be tested are in the working state and opera-tive.

4 Block the TRX locally from the BTS OMU MMI.

5 Unblock the TRX locally from the BTS OMU MMI.

6 Check any new alarms in the system.

Expected outcome

1. An alarm concerning a TRX block is raised.

BTSBSC

Abis

MS

MS

MS

BTS

Protocol Analyzerfor G.703 i/f

A and Abis monitor

A

TO MSC,HLR, VLR

TCSM

106 DN9812243

BSS Integration


Testing BSS integration

2. When the TRX is blocked locally an announcement concerning this state is also sent to the BSC, and the BSC MML also shows that the TRX is blocked and not available for traffic.

10.2 Testing the supervision of the TCSM2 (ETSI/ANSI)The purpose of the test is to verify the correct working of the supervision of the TCSM2.

Steps

1 Verify that transmission is working correctly and there are no transmission alarms active in the BSC.

2 Check the settings of the TCSM2 with remote MML ZDDT.Use the command ZDDT.

3 Check that the TCSM2 hardware configuration matches the hardware in the racks.Use the service terminal command ZGT.

4 Cause a channel fault to the transcoder unit.Do this for example by pulling out a TR16 (ETSI) or TR12 (ANSI) plug-in unit.


Expected outcomeAlarm 2952 TRANSCODER PLUG-IN UNIT FAILURE is active.

10.3 Testing the supervision of the TCSM3i (ETSI/ANSI)The purpose of the test is to verify the correct working of the supervision of the TCSM3i.

Steps

1 Verify that transmission is working correctly and there are no transmission alarms active in the BSC.

2 Check the settings of the TCSM3i with remote MML ZDDT.Use the MML command ZDDT.

3 Check that the TCSM3i hardware configuration matches the actual hardware.Use the service terminal command ZGT.

4 Block one DSP unit.Use the following command:

DN9812243 107



ZUB:DSP,0;


Expected outcomeAlarm 3991 TR3 DSP LOCALLY BLOCKED is active.

You can unblock the DSP unit with the command ZUF:DSP,0;

10.4 Testing IMSI AttachThe purpose of the test is to verify the correct working of the BSS in IMSI attach.

Steps



3 Power up the mobile station.


Expected outcome

1. The mobile station finds the BTS.2. IMSI_ATTACH message is seen in the Abis interface.

10.5 Testing location updatingThe purpose of the test is to verify the correct working of the BSS in location updating.

Steps



3 Supply the PIN to the mobile station.


Expected outcomeThe mobile station finds the network and ends on service state.

10.6 Testing MS to MS callThe purpose of the test is to verify the correct working of the BSS in a basic call.

108 DN9812243

BSS Integration



Steps



3 Make a call from subscriber A (the calling subscriber) to subscriber B (the called subscriber).

4 Make subscriber B answer the call.

5 Verify speech quality.

6 Clear the call at subscriber A's mobile station.


Expected outcomeThe call is successful and speech quality is good.

10.7 Testing MS to MS call, B busyThe purpose of the test is to verify the correct working of the BSS in a basic call when subscriber B is busy.

Steps



3 Make a call from subscriber A to subscriber B (subscriber B is busy).

4 After observing the busy tone at subscriber A's MS, clear the call at subscriber A's MS.

5 Check that there are no hanging resources.


Expected outcomeSubscriber A receives the busy tone.

DN9812243 109



10.8 Testing MS to MS call, A subscriber IMSI detachThe purpose of the test is to verify the correct working of the BSS in a basic call when subscriber A makes IMSI detach during speech.

Steps



3 Make a call from subscriber A to subscriber B.

4 Answer the call at subscriber B's MS.

5 Make IMSI detach (subscriber A).


Expected outcome

1. There are no hanging resources.2. The call is set up as required and subscriber A releases the call.

10.9 Testing successful handover: free TCHsThe purpose of the test is to verify the correct working of the BSS in a successful han-dover, where free TCHs are available.

Steps



3 Check that there are free TCHs in the BTS where the subscriber A will move.



6 Make a handover to subscriber A.

7 Verify speech quality.

110 DN9812243

BSS Integration




Expected outcomeThe handover is successful and speech quality is good all the time.

10.10 Testing unsuccessful handover: no free TCHsThe purpose of the test is to verify the correct working of the BSS in an unsuccessful handover, where no free TCHs are available.

Steps



3 Make sure that there are no free TCHs in the BTS where subscriber A will move.



6 Make a handover attempt to subscriber A.


Expected outcomeThe handover fails and the call is released by the network unless the original channel is still adequate to continue the call.

10.11 Testing radio resource queuing in handoverThe purpose of the test is to verify the correct working of the BSS in a successful han-dover, where a radio resource has to be queued.

Steps





DN9812243 111



5 Reserve one TCH with one more MS and block other TCHs.

6 Make a handover attempt to subscriber A.

7 Release the occupied TCH for the handover attempt.


Expected outcomeThe handover is successful after queuing and the call continues.

112 DN9812243

BSS Integration


Test logs for BSS integration

11 Test logs for BSS integrationWhile integrating the BSS, record confirmation on test execution and possible comments in the test logs.

Part of the logs can be used as a check list while testing.

BSC C number:

BSC name:

BSC Software release (xx.yy-zz):

TCSM2/TCSM3i C number:

TCSM2/TCSM3i Software release (xx.yy-zz):

BTS Software release:

Checked by:

Approved by:

Table 32 BSS specifications

Observations:

Corrective actions:

Checked by:

Date:

Table 33 Creating the A interface

DN9812243 113

BSS Integration Test logs for BSS integration


Approved by:

Date:

Table 33 Creating the A interface (Cont.)

Observations:

Corrective actions:

Checked by:

Date:

Approved by:

Date:

Table 34 Creating the Abis interface

Observations:

Corrective actions:

Checked by:

Table 35 Initialising the base stations

114 DN9812243

BSS Integration


Test logs for BSS integration


Date:

Approved by:

Date:

Table 35 Initialising the base stations (Cont.)

TEST NUMBER:

Observations / used parameter values:

TESTING STATUS (OK/NOK):

Corrective actions/remarks:

Tested by:

Date:

Table 36 Testing BSS integration

Date post:	02-Nov-2014
Category:	Documents
Upload:	de-dao-van
View:	164 times
Download:	19 times

BSS Integration

Documents