bss integration[1]

BSS Integration

dn9812243Issue 18-0 en

# Nokia CorporationNokia Proprietary and Confidential

1 (100)

BSC3119Nokia BSC/TCSM, Rel. S12, ProductDocumentation

The information in this documentation is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia's customers only for the purposes of the agreement under which the documentationis submitted, and no part of it may be reproduced or transmitted in any form or means without theprior written permission of Nokia. The documentation has been prepared to be used byprofessional and properly trained personnel, and the customer assumes full responsibility whenusing it. Nokia welcomes customer comments as part of the process of continuous developmentand improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products cannot be considered binding butshall be defined in the agreement made between Nokia and the customer. However, Nokia hasmade all reasonable efforts to ensure that the instructions contained in the documentation areadequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the documentation.

Nokia's liability for any errors in the documentation is limited to the documentary correction oferrors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL(INCLUDING MONETARY LOSSES), that might arise from the use of this documentation or theinformation in it.

This documentation and the product it describes are considered protected by copyrightaccording to the applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

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

Copyright © Nokia Corporation 2006. All rights reserved.

2 (100) # Nokia CorporationNokia Proprietary and Confidential


BSS Integration

Contents

Contents 3

List of tables 5

List of figures 6

Summary of changes 7

1 Overview of BSS integration 9

2 A interface protocol layers 11

3 A interface configuration with TCSM2 and TCSM3i 13

4 ET indexes in BSC3i and in high and low cabinet BSCs 23

5 Creating the A interface 315.1 Connecting the A interface ET 315.2 Creating the transcoder devices 345.2.1 Creating the TCSM2 355.2.2 Creating the TCSM3i 445.2.3 Creating TCSM3i for combi BSC3i/TCSM3i installation 475.3 Creating Ater Connection to Multimedia Gateway 525.4 Creating the MTP 545.5 Creating the SCCP 565.6 Creating the speech channels 59

6 Synchronising the A interface 63

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

8 Creating the Abis interface 73

9 Initialising base stations 759.1 Creating LAPD links and a base station, and initialising the base station

parameters 769.2 Attaching the BCF software build to the BCF 839.3 Attaching the BTS hardware database to the BTS 849.4 Taking the base station into use 86

10 Testing BSS integration 8910.1 Testing local blocking of a TRX 8910.2 Testing the supervision of the TCSM2 (ETSI/ANSI) 9010.3 Testing the supervision of the TCSM3i (ETSI/ANSI) 9110.4 Testing IMSI Attach 9110.5 Testing location updating 9210.6 Testing MS to MS call 9210.7 Testing MS to MS call, B busy 93



3 (100)

Contents

10.8 Testing MS to MS call, A subscriber IMSI detach 9410.9 Testing successful handover: free TCHs 9410.10 Testing unsuccessful handover: no free TCHs 9510.11 Testing radio resource queuing in handover 95

11 Test logs for BSS integration 97



BSS Integration

List of tables

Table 1. Circuit types supported by the TCSM3i 14

Table 2. Allocation of different channels on the Ater-interface in the case of 16 kbit/sTRAU frame submultiplexing (circuit type G) 15

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

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

Table 5. ET indexes with GSWB in high cabinet BSC 29

Table 6. Default synchronisation ETs 31

Table 7. Possible combinations of circuit pools 41

Table 8. TR3E/A roles 44

Table 9. Possible combinations of circuit pools (TCSM3i) 46

Table 10. BSS specifications 97

Table 11. Creating the A interface 98

Table 12. Creating the Abis interface 98

Table 13. Initialising the base stations 99

Table 14. Testing BSS integration 100



5 (100)

List of tables

List of figures

Figure 1. The three layers of CCS7/SS7 Signalling between MSC and BSC 11

Figure 2. A interface configuration example 14

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

Figure 4. A interface time slot allocation (ANSI) 21

Figure 5. ET4C-B cartridges with GSWB and ET2A/ET2A-T/ET2E-S/SC/ET2E-T/ET2E-TC indexes in BSC3i 25

Figure 6. ET4C-B cartridges with GSW1KB and ET4A/ET4E/ET4E-C indexes inBSC3i 26

Figure 7. ET4C-B cartridges with GSW1KB and ET2A/ET2A-T/ET2E-S/SC/ET2E-T/ET2E-TC indexes in BSC3i 27

Figure 8. ET5C cartridges and ET2E/A indexes in BSC2 28

Figure 9. TCSM2 rack and cartridges (ETSI) 36

Figure 10. TCSM2 rack and cartridges (ANSI) 37

Figure 11. Configuration of the TCSM3i for combined BSC3i/TCSM3i installation 48

Figure 12. Ater interface with MGW 52

Figure 13. Multiplexed and non-multiplexed A interface with 8 kbit GSWB 59

Figure 14. Transmission equipment at Q1 service channel 70

Figure 15. Abis interface 73

Figure 16. BTS software directories 83

Figure 17. The test arrangements 89



BSS Integration

Summary of changes

Summary of changes

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

Changes made between issues 18 and 17-1

Information on TCSM3i added to chapter A interface configuration with TCSM2and TCSM3i.

Information on BSC3i 1000/2000 added to chapter ET indexes in BSC3i and inhigh and low cabinet BSCs.

New topics Creating the TCSM3i , Creating TCSM3i for combi BSC3i/TCSM3iinstallation and Creating Ater Connection to Multimedia Gateway added tochapter Creating the A interface.

Changes made between issues 17-1 and 17

Editorial changes.

Changes made between issues 17 and 16

New ET4 plug-in types added.

Instructions for checking and changing the synchronisation of Nokia TalkFamily,UltraSite and MetroSite BTSs added to chapter Initialising base stations.

Instructions Creating LAPD links and Creating a base station and initialising itsparameters combined into one procedure.

Instructions on how to create a Nokia InSite to be Autoconfigured are movedfrom chapter Initialising base stations to Abis Autoconfiguration.

The document has been revised throughout to comply with the latestdocumentation standards.



7 (100)

Summary of changes



BSS Integration

1 Overview of BSS integration

BSS Integration instructions are intended to be used during the integration of theTCSM -BSC-BTS system in the final location.

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

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

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

. Integrating 2GBSS to NetAct in NetAct documentation

Creating a connection to the SGSN is described in SGSN Integration in SGSNdocumentation. Creating the connection in BSC is described in Enabling GPRSin BSC in BSC documentation.

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

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

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

BSS integration procedure

The main phases of the testing are executed in the order presented here. BSSintegration consists of the following phases:

1. Creating the A interface

2. Synchronising the A interface



9 (100)

Overview of BSS integration

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

4. Creating the Abis interface

5. Creating X.25 or LAN connections. See Integrating 2GBSS to NetAct inNetAct documentation (for BSC2i and BSC3i).

6. Initialising base stations

7. 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 and in high and low cabinet BSCs



BSS Integration

2 A interface protocol layers

In the ETSI environment, the A interface is defined in accordance with CCITT#7Signalling System. In the ANSI environment, the A interface is defined inaccordance 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 SystemApplication Part (RSAP; with ANSI), as shown in figure The three layers ofCCS7/SS7 Signalling between MSC and BSC (ETSI) .

Figure 1. The 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 asignalling link, a signalling link set, and a signalling route set.

The SCCP complements the services of the MTP by providing connectionlessand connection-oriented network services. It consists of SCCP subsystems.

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

MSC BSCTCSM

BSSAP / RSAP

MTP

SCCP

MTP

SCCP

BSSAP / RSAP

Signalling linksthrough connected



11 (100)

A interface protocol layers

For an overview, see Overview of BSS integration.



BSS Integration

3 A interface configuration with TCSM2and TCSM3i

The A interface configuration can be made in many different ways depending onthe equipment, or capacity and redundancy requirements. For example, thetranscoder can be either TCSM2 or TCSM3i. Likewise, it is possible toimplement only one PCM , E1 (used in ETSI environment) or T1 (used in ANSIenvironment) line between the MSC and the BSC or to use several separate PCMlines for redundancy or capacity purposes. See Figure A interface configurationexample.

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



13 (100)

A interface configuration with TCSM2 and TCSM3i

Figure 2. A interface configuration example

TCSM3i

Table 1. Circuit types supported by the TCSM3i

Circuittype

Supported channels and speech codingalgorithms

Capacity unit on Aterinterface

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

FR data traffic

16 kbit/s

TCSM3iEQUIPMENT

MSC

TCSM3iUNIT

Aterinterface

Ainterface

TCSM3iUNIT

DN0626652

BSC

E1/T1

E1/T1

0

0

1

2

3

4

1

2

3

4

E1/T1

E1/T1



BSS Integration

Table 1. Circuit types supported by the TCSM3i (cont.)

Circuittype

Supported channels and speech codingalgorithms

Capacity unit on Aterinterface

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

FR data traffic

HSCSD max 2* FR data traffic

32 kbit/s

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

FR data traffic

HSCSD max 4* FR data traffic

64 kbit/s

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

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

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



15 (100)


Table 2. Allocation of different channels on the Ater-interface in thecase of 16 kbit/s TRAU frame submultiplexing (circuit type G)(cont.)

12 21 22 23 24

13 1 2 3 4


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

The basic requirement for high-speed circuit-switched data (HSCSD) datatransmission capability is that the associated BSC is equipped with an 8 kbit/sswitching network or Bit Group Switch. Channel allocations for TCSM3iconfigured to transmit the data exclusively at the maximum rate of 32 kbit/s (typeH) and 64 kbit/s (type I) are shown in the following tables. The same allocationsaccept also speech channels (FR/EFR, HR) instead of data, allowing an optimiseduse of transmission capacity for mixed speech/data use. The capacity unitreserved for an HSCSD connection on the A-interface 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



BSS Integration

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

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

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



17 (100)


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

22 19 20

23 21 22

24 23 24

F

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

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



BSS Integration

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

17 17

18 18

19 19

20 20

21 21

22 22

23 23

24 24

F

TCSM2, ETSI

Provided that the BSC is equipped with an 8 Kbit group switch (GSWB), fourseparate A interface lines can be put into one highway PCM, making it possibleto 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. Thecombination of half-rate and full-rate can also be used.

The maximum efficiency is achieved if Nokia's recommendation for time slotallocation is followed (shown in the figure Time slot allocation for full-rate trafficon Ater 2 Mbit/s interface with the TCSM2 (ETSI) ).

Signalling channels, and possibly network management system connections, arealways allocated beginning from the end of the frame. This optimises the numberof the traffic channels available for the fourth tributary. This is due to the fact thatonly the time slots preceding the first signalling time slot can be used as speechchannels in the fourth tributary.

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



19 (100)


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

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



BSS Integration

TCSM2, ANSI

Because 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 andthe 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 slotis used for SS7 signalling. This leaves 91 channels for traffic.

Figure 4. A interface time slot allocation (ANSI)


Trunk 3 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 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 8TS 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



21 (100)




BSS Integration

4 ET indexes in BSC3i and in high and lowcabinet BSCs

BSC3i 1000/2000

The Exchange Terminals (ETs) of the BSC3i 1000/2000 are housed in GT6C-Aand/or GT4C-A cartridges. One GT4C-A cartridge can contain up to eight ETplug-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 toETC 5 in BSC3i 2000. Additionally, ET16 units can also be equipped to GTICcartridges to achieve a maximum of 800 E1/T1 interfaces amount in the two-cabinet configuration and 384 E1/T1 interface amount in the one-cabinetconfiguration.

The ET16 units are installed to GTIC cartridge starting from the right in mixedET16 and ETS2 equipping. In the incoming direction, the ET decodes the 2048Mbit/s in European Telecommunications Standards Institute (ETSI) signal or1544 Mbit/ s American National Standards Institute (ANSI) signal of a circuitinto data signals.

In the outgoing direction, the ET receives a binary PCM signal from theswitching network and generates the PCM frame structure. The resulting signal isconverted into a line code (HDB3 in the ETSI environment, B8ZS or AMI in theANSI environment) and transmitted further onto the 2048 Mbit/s (ETSI) or 1544Mbit/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 transmissionprotection. A maximum of 16 active optical interface can be achieved with 8plug-in units, if two active interface per unit is used or with 16 plug-in units if oneactive 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 PCMsinto channelized way in optical interfaces (VC12). One STM-1 interface consistsof 63 E1s (ETSI) and one OC-3 interface consists of 84 T1s (ANSI). PCMs arehandled in the same way as ETs in the ET16 plug-in unit.



23 (100)

ET indexes in BSC3i and in high and low cabinet BSCs

BSC3i 660

BSC3i 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 havespace for 62 * (2*2) Mbit ET PCM's plug-in units in ETSI or 62 * (2*1.5) MbitET PCM's plug-in units in ANSI (32 pcs in ET4C 0, 30 pcs in ET4C 1). Thismakes it possible to have a maximum of 124 ET PCMs in one BSC. See figureET4C-B cartridges with GSWB and ET2A/ET2A-T/ET2E-S/SC/ET2E-T/ET2E-TCindexes in BSC3i.

With the 1024 PCM Bit Group Switch (GSW1KB), the two ET4C-B cartridgeshave 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 BSC. Seefigure ET4C-B cartridges with GSW1KB and ET4A/ET4E/ET4E-C indexes inBSC3i.

With the GSW1KB Bit Group Switch it is also possible to mix ET2 and ET4plug-in units in the BSC3i, so that each BSC3i equipped with GSW1KB can haveboth ET2 and ET4 plug-in units with the restriction that one ET4C-B shelf mustbe equipped with either ET2 plug-in units or ET4 plug-in units. See figure ET4C-B cartridges with GSW1KB and ET2A/ET2A-T/ET2E-S/SC/ET2E-T/ET2E-TCindexes in BSC3i.



BSS Integration

Figure 5. ET4C-B cartridges with GSWB and ET2A/ET2A-T/ET2E-S/SC/ET2E-T/ET2E-TC indexes in BSC3i

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

CLS0,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:



25 (100)


Figure 6. ET4C-B cartridges with GSW1KB and ET4A/ET4E/ET4E-C indexesin BSC3i

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

CLS0,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)

GSW1KB

504505506507

508509510511

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

ET4x

GSW1KB

GSW1KB

GSW1KB



BSS Integration

Figure 7. ET4C-B cartridges with GSW1KB and ET2A/ET2A-T/ET2E-S/SC/ET2E-T/ET2E-TC indexes in BSC3i

BSC2

A low cabinet BSC, the BSC2, can have up to seven ET5C cartridges, eachhaving space for 16 2Mbit ET PCM 's plug-in units. This makes it possible tohave a maximum of 112 2Mbit ET PCMs in one BSC; see figure ET5Ccartridges and ET2E/A indexes in BSC2.

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

CLS0,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)

GSW1KB:

GSW1KB:

GSW1KB:

ET2x

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

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

ET2x

GSW1KB:



27 (100)


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

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



BSS Integration

High cabinet BSC

In a high cabinet BSC (used only in the ETSI environment), there can be sevenET1C cartridges and two ET5C cartridges. Each ET1C cartridge can containeight 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 BSC. Seetable ET indexes with GSWB in high cabinet BSC.

Table 5. ET indexes with GSWB in high cabinet BSC

Car-tridge

ET1

C0

ET1

C1

ET1

C2

ET1

C3

ET1

C4

ET1

C5

ET1

C6

ET1

C0

ET1

C1

PCMIndex

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




29 (100)




BSS Integration

5 Creating the A interface

In this phase the MSC, the transcoder, and the BSC are configured to enable theMSC and the BSC to communicate properly with each other.


5.1 Connecting the A interface ET

Each A interface needs its own ET. The ETs used for the A interface must be theones that supply synchronisation to the BSC's CLS units. There are three suchETs per BSC, and their default unit numbers are shown in the table below. It ispossible to use any other ET for the synchronisation by changing the position ofthe corresponding synchronisation cable in the ET cartridge.

Table 6. Default synchronisation ETs

BSC type ET type GSW type Default synchronisation ETs

BSC ET1E, ET1E-C,ET2E, ET2E-C,ET2E-S/SC, ET2E-T, ET2E-TC

GSWB 32,33,34

BSC2 ET2E/A, ET2E-C,ET2E-S/SC, ET2E-T, ET2A-T, ET2E-TC

GSWB 32,40,48

(only even ETs possible)

BSC3i ET2A, ET2E-S/SC,ET2E-T, ET2A-T,ET2E-TC

ET4A, ET4E, ET4E-C

ET16

GSWB

GSWB1KB

GSWB2KB

32, 96, 160, 224

(only even ETs possible)



31 (100)

Creating the A interface

Steps

1. Check that the ET is connected (WUP).

ZWUP:<PCM numbers>;

If the ET is already connected, it has a controlling BCSU (Base StationController Signalling Unit) and process info. The controlling process canbe SC7PRB A interface, ABIPRB Abis interface, SI1PRB ISDN Abisinterface, or ERATES Gb interface.

Example 1.

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:

. When: ET is already connected

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 isloaded into the unit.

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



BSS Integration

Note

All ET's in the same plug-in unit will be restarted concurrently.

. When: ET is not connected

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 ET-16

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

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

Note

When using ET2E/A, ET2E-C, ET2E-S/SC, ET2E-T, ET2A-T, or ET2E-TCplug-in units, the even-numbered ET must be connected before the odd-numberedone.

When using ET4A, ET4E, or ET4E-C plug-in units, the first logical ET of theET4C cartridge. The first ET must be divisible by four.

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 ofthe PCM line.

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



33 (100)


For ET2E/A, ET2E-C, ET2E-S/SC, ET2E-T, ET2A-T, ET2E-TC, ET4A,ET4E, or ET4E-C the frame alignment mode is set by MML. The framealignment mode strapping in ET2E/A, ET2E-C, ET2E-S/SC, ET2E-T,ET2A-T, ET2E-TC, ET4A, ET4E, or ET4E-C is used only during the unitrestart 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, ET2A-T, ET2E-TC, ET4A, ET4E, or ET4E-C(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 alignmentmode>;

. ANSI:

Note that the T1 functional modes have to be the same at bothends of the T1 line.

ZYEG:<unit type>,<unit index>:<superframemode>,<line code type>,<outgoing signallevel>;

Further information:

Next, create the transcoder devices.

5.2 Creating the transcoder devices

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



BSS Integration

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

5.2.1 Creating the TCSM2

The TCSM2 is a functional unit of the BSC. The BSC monitors the TCSM2 byusing a LAPD link which is connected from the TCSM2's Transcoder Controller(TRCO) to the BSC's Operation and Maintenance Unit (OMU). The LAPD linkis 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 linkusing the first two bits in time slot one (for ETSI, see figure Time slot allocationfor full-rate traffic on Ater 2Mbit/s interface with the TCSM2 (ETSI) and forANSI, figure A interface time slot allocation (ANSI) ). In addition to monitoring,the LAPD link is also used for configuring, alarms, remote MMI sessions, and forsoftware downloading to the TCSM2.

The TCSM2 software is kept in the BSC's hard disks and consists of threemodules; software for the TRCO units, for the ET2E/A, ET2E-C, ET2E-S/SC,ET2E-T, ET2A-T, or ET2E-TC 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 theBSC.

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



35 (100)


Figure 9. 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



BSS Integration

Figure 10. TCSM2 rack and cartridges (ANSI)

The TCSM2 rack, transcoder and ET cartridges along with the plug-in units arecreated to the BSC's equipment database. It is important to create theconfiguration and especially the transcoder ETs correctly to the BSC since theyare used to define the type and the number of the A interface PCMs (in ETSI) orT1s (in ANSI). This information is used by the transcoder when it configures itsPCMs/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)

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



37 (100)


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

Steps

1. Create the rack for TCSM2 (WTJ).

ZWTJ:TC2E,<rack or cabinet coordinate>:PSFP=2,PSA=2;


rack or cabinet coordinate Coordinate of the TCSM2.

2. Create a cartridge for the TC1C (WTC).

ZWTC:TC1C,<cartridge coordinate>:P1=<coordinate>;


cartridge coordinate Coordinate of the transcoder unit. See figure TCSM2rack and cartridges (ETSI) or TCSM2 rack andcartridges (ANSI).

3. Create the TCSM unit (WTU).

ZWTU:TCSM,<unit index>:<cartridge coordinate>;


cartridge coordinate Coordinate of the transcoder unit. See figure TCSM2rack and cartridges (ETSI) or TCSM2 rack andcartridges (ANSI).

4. Create transcoder controller plug-in unit, TRCO (WTP).

ZWTP:TCSM,<unit index>:TRCO,0,0::GENERAL,2,<unitindex>,TSL,1;

5. Create TR16/TR12 plug-in units (WTP).

Two plug-in units are needed for each A interface PCM/T1:



BSS Integration

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


piu type ETSI: TR16, ANSI: TR12.

piu index Index of the TR16/TR12.

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

6. Create the ET1TC cartridge (WTC).

ZWTC:ET1TC,<cartridge coordinate>;


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

7. Create the unit ET1TC cartridge (WTU).

ZWTU:TCSM,<unit index>:<coordinate of cartridge>;


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

8. Create ET2E/A, ET2E-C, ET2E-S/SC, ET2E-T, ET2A-T, or ET2E-TCplug-in units (WTP).

ZWTP:TCSM,<unit index>,<unit coordinates>:<piutype>,<index>,<track>;


unit coordinates Coordinate of the ET1TC cartridge.



39 (100)



piu type ETSI: ET2E, ET2E-C, ET2E-S/SC, ET2E-Tor 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 figureTCSM2 rack and cartridges (ETSI) or TCSM2 rackand cartridges (ANSI).

9. Check that the A interface ETs and the connectable plug-in units of theTCSM2 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 fromET number one. The highway PCM is not connected.

Note

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

10. Set the number of through connected channels (WGS).

ZWGS:<highway pcm>:<number of through connectedchannels>;

11. Create transcoder PCMs (WGC).

ZWGC:<highway pcm number>,<tc_pcm number>:POOL=<transcoder pcm pool numbers>:BCSU,<controlling unit index>;



BSS Integration


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.

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

Table 7. Possible combinations of circuit pools

Supported codecs and software Supported A-interface pools

FR, HR, EFR, AEC, HSCSD, NS 3 (DR), 7 (EFR & DR), 10 (HS2), 13 (HS4), 20 (EFR &DR & D144), 21 (HS2 & D144), 22 (HS4 & D144)

FR, EFR, AEC, TFO, NS 1 (FR), 5 (EFR & FR)

HR, AEC, TFO, NS 2 (HR)

AMR, AEC, NS 23 (AMR)

FR, HR, EFR, AEC, HSCSD, TTY 3 (DR), 7 (EFR & DR), 10 (HS2), 13 (HS4), 20 (EFR &DR & D144), 21 (HS2 & D144), 22 (HS4 & D144)

FR, EFR, AEC, TFO, TTY 1 (FR), 5 (EFR & FR)

AMR, AEC, TTY 23 (AMR)

12. Connect the TRCO to the BSC (WUC).

This command creates the LAPD link between the BSC and the TCSM2. Acircuit 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 toWO-EX. If the TCSM2 software does not exist or is different from that inthe BSC, it is downloaded in this phase.

14. Check the state of the TCSM2 LAPD link (DTF).



41 (100)


ZDTF:TCSM,<unit index>:OMU;

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

Example 2. Printout from the BSC (ETSI)

ZWGO:36;

EXECUTION STARTED

ET_PCM 36 TC_PCM POOL TYPE

ET_PCM_TSLS

TCSM-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 3. 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 & D144

PCM-2 AMR

PCM-3 HR


PCM-5 NU

PCM-6 NU

PCM-7 NU

/* COMMAND EXECUTED */

Example 4. Printout from the BSC (ANSI)

ZWGO:32&&35;

EXECUTION STARTED


ET_PCM_TSLS



BSS Integration

TCSM-32 TCSM2 1 - NU -

2 23 AMR 1 && 6

3 5 EFR&FR 7 && 12

4 21 EFR&FR&HS2&D144 13 && 22


32 - 24 <--> 2 - 24


ET_PCM_TSLS

TCSM-33 TCSM2 1 - NU -

2 13 EFR&FR&HS4 2 && 20


33 - 24 <--> 2 - 16


ET_PCM_TSLS

TCSM-34 TCSM2 1 5 EFR&FR 1 && 6

2 10 EFR&FR&HS2 7 && 18

3 13 EFR&FR&HS4 19 && 23


-

ET_PCM 35 THROUGH CONNECTIONS

TCSM-35 TCSM2 -

COMMAND EXECUTED

Example 5. Printout from the transcoder (ANSI-C)

ZDDX:TCSM,32:"ZRD";

TCSM_032:LUC> ZRD

/* TRANSCODER PCM TYPES */

GROUP SWITCH GSWB

PCM TYPE

PCM-1 NU

PCM-2 AMR

PCM-3 FR & EFR & D144


PCM-5 NU

PCM-6 NU

PCM-7 NU

/* COMMAND EXECUTED */

15. Add through connected channels (WGA).

ZWGA:<highway pcm circuit>:<tc_pcm circuit>;



43 (100)


16. Output and check the through connected channels (WGO).

ZWGO:<highway pcm number>:<output mode>;


Next, create the MTP.

5.2.2 Creating the TCSM3i

Although the TCSM3i has over 12 times more capacity and is more compact, theTCSM2 and TCSM3i are very similar transcoders from the BSC point of view.They both support the same features, but the TCSM3i allows for more dynamicpool configuration.

When the TCSM2 or TCSM3i is created into the BSC hardware database, itsfunctional unit is TCSM and both transcoder types are controlled by the BSC viathe LAPD link. The TCSM3i software is also kept in the BSC hard disks fromwhere it can be downloaded to the TCSM3i whenever necessarry. The TCSM3isoftware consists of four modules: O&M software, DSP software, ET16 software,and FPGA.

One important difference between the TCSM2 and TCSM3i is hardwareplanning. Instead of several plug-in units one transcoder based on TCSM3ihardware consists of only one TR3E (ETSI) or TR3A (ANSI) plug-in unit andone ET16 plug-in unit. Note that ET16 units are equipped only with supervisedTR3E/A units. One TCSM3i can handle a maximum of four TC-PCMs on the Ainterface when 16 Kbit/s submultiplexing is used on Ater interface. 8 Kbit/ssubmultiplexing is not supported by the TCSM3i.

One TCSM3i cabinet can contain up to 96 transcoder units in 6 cartridges.

As shown in the following table, a certain number of TR3E/A units act as masterswho supervise the ET16 plug-in units. When the master TR3E/A plug-in units aretaken into use, the ET16 plug-in units are also equipped.

Table 8. TR3E/A roles

Slot number TR3E/A role

1 Cartridge master

2 Cabinet head master (only in cartrixge 2.0)

5 Master



BSS Integration

Table 8. TR3E/A roles (cont.)

Slot number TR3E/A role

9 Master*

13 Master

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

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

Steps

1. Create the TCSM3i cabinet (WTJ).

ZWTJ:TCSA,1C:AL=1C1-0-4R1,PDFU=4;

2. Create the TCSM, ET16 and cabinet clock cartridges (WTC).

ZWTC:<cartridge type>,<coordinate of cartridge>:P1;

3. Create the TCSM unit (WTU).

ZWTU:<unit identification>:<coordinate ofcartridge>;

Note

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

4. Create the TR3A/E plug-in units (WTP).

ZWTP:TCSM,<unit index>:TR3E,0,1::GENERAL,4,<unitindex>,TSL,1;

5. Create the ET16 plug-in units (WTP).



45 (100)


ZWTP:TCSM,<unit index>:ET16,0,1; (A interface ET16)

ZWTP:TCSM,<unit index>:ET16,1,17; (Ater interface ET16)




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 andapplication software.

Table 9. Possible combinations of circuit pools (TCSM3i)

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), 22 (HS4&D144), 32(EFR&DR&AMR&HS4&D144)

8. Connect the TR3A/E to the BSC (WUC).

This command creates the LAPD link between the BSC and the TR3A/E.A circuit group DTCSM and the circuit to it are created at the same time.

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

9. Change the state of the TCSM3i to WO-EX (USC).

This command automatically changes the state of the TCSM LAPD link toWO-EX. If the TCSM3i software does not exist or is different from that inthe BSC, it is downloaded in this phase.



BSS Integration

10. 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 inthe fact that when you are checking the PCM circuits from the transcoderend, the PCM types are different than the pools in the BSC.

11. Add through connected channels (WGA).

ZWGA:<highway pcm circuit>:<tc_pcm circuit>;

12. Output and check the through connected channels (WGO).

ZWGO:<highway pcm number>:<output mode>;


For more detailed information on the commands, see Configuring the TCSM3i inCreating and Managing the BSC Hardware.

5.2.3 Creating TCSM3i for combi BSC3i/TCSM3i installation

The growing capacity of the BSC results in the incerased transmission capacitybetween the BSC and the MSC. For example, the S12 level high capacity BSC3i2000 has a capacity of 11880 erlangs. This means the user has to configure 99/124 PCM cables between the BSC and the transcoders, tanslating to 396/496 A-interface PCM cables when Full Rate (FR) coding is used. To avoid using suchhuge amounts of PCM cables, synchonous transmission on optical media (cable)is introduced.

In the ETSI environment, synchronous transmission is standardised bySynchronous 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 andinterface is called OC-x, where x defines the transmission speed. One STM-1interface can handle 63 E1 PCM's capacity and one OC-3 interface can handle 84T1 PCM's capacity.



47 (100)


Figure 11. Configuration of the TCSM3i for combined BSC3i/TCSM3iinstallation

The Combi BSC3i/TCSM3i implements same transcoding functionality andfeatures as standalone version. In some cases, the BSC equipped in the sameroom as the TCSM3i cabinet may not use all the transcoding capacity from theTCSM3i cabinet. In such cases, it is possible to distribute TCSM3i's capacitybetween several BSCs. If the BSC is located in teh same room as the TCSM3i, itis called the Master BSC. A Remote BSC is located away from the TCSM3i andits Ater PCMs are connected to TCSM3i cabinet via Master BSC's GSW2KB.

1. Creating TCSM unit to Master BSC

The Master BSC must always be a BSC3i 1000 or BSC3i 2000.

2. Sharing Combi TCSM3i transcoding capacity to remote BSC

A Remote BSC can be BSC3i 1000 or BSC3i 2000 or even older models.If the remote BSC does not support optical interfaces, ET interfaces can beused.

The procedure below is to create the transcoder into the Master BSC.

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)

TR3A/E PIU

Optical transmission



BSS Integration

Steps

1. Create TCSM3i.

a. Create the cabinet:

ZWTJ:TCSA,1A:AL=1A1-0,PDFU=2;

b. Create the cartridge:

ZWTC:TC2C,1C030-01:P1=1C030-01;

c. Create the functional unit:

ZWTU:TCSM,1280:1C030-01;

d. Create the TR3E plug-in unit:

ZWTP:TCSM,1280,1C030-01:TR3E,0,0:: GENERAL,2,1280,TSL,1;

e. 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 NokiaNetAct.

2. Create the SBMUX.

WTU:GSW,0:1J1-10:MAS=MCMU;

WTU:GSW,1:1J1-20:MAS=MCMU;

WTP:GSW,0,1J1-10:SBMUX_A,0,1;




3. Create the STMU.

a. Create the cartridge:

WTC:GT4C_A,1A1-20:AL=1A1-10,P1=1A1-20;

b. Create the functional unit:

WTU:STMU,0:1A1-20;

c. Create the ETS2 plug-in unit:

WTP:STMU,0:ETS2,0,0:LAPD,8,500,TSL,0&&16

d. Connect the ETS2:

WUC:STMU,0:::BCSU,0;

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



49 (100)


4. Create the A-interface ET units into the STMU.

a. Create the functional units:

ZWTU:ET,3392&&3454::UNIT=STMU,INDEX=0:IF=0;

b. Create the plug-in units into the ET unit:

ZWTP:ET,3392&&3454:ETS2,0,0:ETT00,8,3392&&3454,TSL,0;

c. Connect the ET units:

ZWUC:ET,3392&&3454:ETS2,0,0:IF=A:BCSU,0;

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

5. Create the CLAB.

ZWTC:CLAC_B,1B1-0:;

ZWTU:CLAB,0:1B1-0;

ZWTP:CLAB,0:CLAB_S,0,03;

ZWTU:CLAB,1:1B1-0:;

ZWTP:CLAB,1:CLAB_S,1,04;

6. Create transcoder configuration.

a. Set amount of through connections by MML command WGS

b. Create the TC-PCM by MML command WGC:

ZWGC:1280,1:POOL=1:BCSU,1;





Note

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

c. Create the through connections by MML command WGA.

d. Change TCSM3i state from SE-NH to TE-EX by MML commandUSC.

e. The TR3E starts downloading its software from the BSC.



BSS Integration

After successfully downloading software, you can run thediagnostics (when needed) and change the TCSM state to WO-EXby MML command USC.

7. Create circuit group.

RRC:TYPE=CCS,NCGR=ATERTEST,CGR=1:DIR=IN,NET=NA0,SPC=200,LSI=AINA0;

8. Add circuit to CGR.

RCA:CGR=1:ETPCM=1280,crct=1-1&&-31:CCSPCM=1;





Note that this command is needed only when the fifth TC-PCM is created.

9. Change the circuit states.

CEC: ET_PCM=1280,CRCT=1-1&&-31:BL;

CEC: ET_PCM=1280,CRCT=1-1&&-31:WO;











51 (100)




5.3 Creating Ater Connection to Multimedia Gateway

Multimedia Gateway (MGW) implements the same base transcodingfunctionality and features as TCSM2. The only exeption is that MGW does notsupport 8kbit/s submultiplexing on Ater interface. There is no O&M LAPD linkbetween BSC and MGW so BSC does not control MGW at all. This means thatthe user is responsible for creating identical transcoder configurations to bothBSC and MGW. Since there is no LAPD link, there is no need to equip TCSMfunctional unit into the BSC HW database.

Figure 12. Ater interface with MGW

RAN CN

BSC Nokia or otherMSC

MGW

2G TC

BSC NSS

Ater

A

8k/16k/32k/64k

64k/56k

16k/32k/64k

Ater

TCSM



BSS Integration

Steps




ZWGC: <highway pcm number>,<tc_pcm number>:

POOL=<transcoder pcm pool numbers>:BCSU,<controlling unit index>;

Note

The MGW does not support the same pools as in BSC. For more information onpools supported by MGW, see Multimedia Gateway (MGW) FunctionalDescription in Nokia Multimedia Gateway Product Documentation.

Example 6. Printout of transcoder configurations

ZWGO:100:;

EXECUTION STARTED


ET_PCM_TSLS

1 5 EFR&FR 1 && 8

2 5 EFR&FR 9 && 16

THROUGH CONNECTIONS

-

COMMAND EXECUTED

Example 7. Setting the number of through connections

ZWGS: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 ?



53 (100)


Example 8. Creating a TC_PCM

ZWGC:100,:POOL=5:BCSU,5:;

EXECUTION STARTED

/*** TCSM NOT EQUIPPED -

THIS CONFIGURATION IS POSSIBLE ONLY

WHEN TRANSCODING IS PROVIDED BY SOME OTHER DEVICE ***/

CONFIRM COMMAND EXECUTION: Y/N ? Y


ET_PCM_TSLS

1 5 EFR&FR 1 && 8

UPDATING FILES TO DISK. WAIT 4 SECONDS.

COMMAND EXECUTED

5.4 Creating the MTP

Steps

1. Create signalling links (NCC).

It is strongly recommended to have at least two signalling links in the Ainterface. Furthermore, the links should not be controlled by the same BaseStation Controller Unit (BCSU).

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


parameter set number ETSI: value 0 is recommended.

ANSI SS7: value 2 must be used.

2. Create the local signalling point code (NRP).

ZNRP:<signalling network>,<bsc signalling pointcode>,<bsc signalling point name>,SEP:STAND=<ss7standard>:<number of spc subfields>;



BSS Integration


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.

3. Create the signalling link set (NSC).

ZNSC:<signalling network>,<msc signalling pointcode>,<msc signalling link set name>:<signalling linknumber>,<signalling link code>;

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

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

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 theprevious step.

ZNSA:<signalling network>,<msc signalling pointcode>,<msc signalling link set name>:<signalling linknumber>,<signalling link code>;

5. Create the signalling route set (NRC).

ZNRC:<signalling network>,<msc signalling pointcode>,<msc signalling point name>,<parameter setnumber>,<load sharing status>,<restrictionstatus>:,,,0;


parameter set number Value 1 is recommended.

load sharing status D is recommended.

restriction status R is recommended.



55 (100)


6. Allow activation of the signalling links (NLA).

ZNLA:<signalling link numbers>;

7. Allow activation of the signalling route (NVA).

ZNVA:<signalling network>,<msc signalling pointcode>:;

8. Change signalling link states (NLC).

ZNLC:<signalling link numbers>,ACT:;

9. Change route set state (NVC).

ZNVC:<signalling network>,<msc signalling pointcode>::ACT;


Next, Creating the SCCP.

5.5 Creating the SCCP

The parameter values shown in the table apply in each step in this procedure.


subsystem number ETSI: FE, ANSI: DE.

subsystem name ETSI: BSSAP, ANSI: RSAP.

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).



BSS Integration

ZNFD:<signalling network>,<bsc signalling pointcode>,<signalling point parameter set number>:<subsystem number>,<subsysten name>,<subsystemparameter set number>,;


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.

3. Define SCCP for the MSC's signalling point (NFD).

ZNFD:<signalling network>,<msc signalling pointcode>,<signalling point parameter set number>:<subsystem number>,<subsystem name>,<subsystemparameter set number>;

See the previous step for recommended parameter values.

4. Modify broadcast status of SCCP signalling points (OBM).

ZOBM:<signalling network>,<BSC signaling pointcode>,<subsystem name>::Y;




5. Modify the local broadcast status of SCCP subsystems (OBC).

ZOBC:<signalling network>,<MSC signaling pointcode>,<subsystem name>::Y;



57 (100)





6. Change the SCCP state at BSC side (NGC).

ZNGC:<signalling network>,<bsc signalling pointcode>:ACT;

7. Change the SCCP state at MSC side (NGC).

ZNGC:<signalling network>,<msc signalling pointcode>:ACT;

8. Change subsystem state at BSC side (NHC).

ZNHC:<signalling network>,<bsc signalling pointcode>:<subsystem>:ACT;

The value of the parameter subsystem is BSSAP in ETSI and RSAP inANSI.

9. Change subsystem state at MSC side (NHC).

ZNHC:<signalling network>,<msc signalling pointcode>:<subsystem>:ACT;

The value of the parameter subsystem is BSSAP in ETSI and RSAP inANSI.


Next, Creating the speech channels.



BSS Integration

5.6 Creating the speech channels

Speech circuits are used to carry the actual user data through the A interface. Onecircuit is needed for each ongoing call. With conventional hunting the circuit ischosen by the MSC which means the MSC has to know the circuits of the BSCand their status. That is why the circuits must be identified by both the MSC andthe BSC. This is accomplished by using CIC codes. A CIC code consists of theCCSPCM and the time slot of the circuit. The CIC codes must be the same atboth ends.

Reversed Hunting can be activated here. The following instructions apply whenactivating it in a new BSC. If you want to change the BSC to use ReversedHunting instead of normal hunting, see Activating and Testing BSS10005:Reversed Hunting.

For more information on Reversed Hunting, see Circuit configuration on the Ainterface in Half Rate, and A interface circuit allocation in Radio ChannelAllocation.

Figure 13. Multiplexed and non-multiplexed A interface with 8 kbit GSWB

Steps

1. Create a circuit group (RCC).

BSCGSWB

MultiplexedA interface

Speech circuits

Non-multiplexedA interface

ET 32

ET 34

ETPCM 32

ETPCM 34



59 (100)


ZRCC:TYPE=CCS,NCGR=<ciruit group name>,CGR=<circuitgroup number>:DIR=<direction>,NET=<signallingnetwork>,SPC=<msc signalling point code>,LSI=<linesignalling>;

Note

The circuit group name must have the same name as the one created for MSC.


direction To activate Reversed Hunting: OUT.

If you do not want to activate Reversed Hunting: IN.

line signalling DUMMY, AINA0, AINA1, AIIN0, AIIN1, DSS01.

2. Add circuits to the circuit group (RCA).

If more speech circuits are needed they must be added to the previouslycreated circuit group.

. ETSI:

In multiplexed cases:

ZRCA:NCGR=<circuit group name>:ETPCM=<etpcm>,CRCT=<circuit(s)>,CRCTSTEP=1:CCSPCM=<number ofPCM system>:;

In non-multiplexed cases:

ZRCA:CGR=1:ETPCM=<etpcm>,CRCT=<circuits>:CCSPCM=<number of PCM system>:;



BSS Integration

Note

One to six (ETSI) or one to seven (ANSI) transcoder PCMs can be used towardsthe MSC if the BSC is equipped with the GSWB. The amount of PCMs and TSLsdepends 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 havePCMs 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 onAter 2Mbit/s interface with the TCSM2 (ETSI) and A interface time slotallocation (ANSI).

. ANSI:

ZRCA:NCGR=<circuit group name>,ETPCM=<etpcm>,CRCT=<circuit(s)>,CIC=<circuit identificationcode>,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>;

Note

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).



61 (100)


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;

4. Change the state of the speech circuits (CEC).

Immediately after creation the circuits are in NU-US state. The state mustbe 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 .



BSS Integration

6 Synchronising the A interface


Before you start

The PCM (or T1 in ANSI) circuits have been connected into operation betweenthe MSC and the BSC. Normally all three of these PCM/T1 circuits are used forsynchronisation. The synchronisation input with the highest priority (2M1)should be in the state CONNECTED and in use (USED INPUT). The other inputs2M2 and 2M3 should be in the state CONNECTED. In CL3TG synchronisationunit there is fourth 2M input. The CL3TG unit also contains two synchronisationinputs (FS1 and FS2) for an external synchronisation source. For moreinformation, see CL3TG , Plug-in unit descriptions.

Steps

1. Check the state of the synchronisation (DRI).

ZDRI;

Expected outcome

Normally, it gives the following output:

CL1TG:

INPUT STATE USED INPUT PRIORITY

----- --------------- ---------- ----------

2M1 CONNECTED 2M1 7

2M2 CONNECTED - 6

2M3 CONNECTED - 5

SYNCHRONISATION UNIT WORKING MODE ......... HIERARCHIC SYNCHRONISATION

FUNCTION AUTOMATIC RETURN FROM PLESIOCHRONOUS OPERATION .......... ON

SYNCHRONISATION UNIT 0 OSCILLATOR CONTROL WORD VALUE ....... 31896

FUNCTION AUTOMATIC USE OF REPAIRED INPUTS ........................ ON

SYNCHRONISATION UNIT 1 OSCILLATOR CONTROL WORD VALUE ....... 31635

SYNCHRONISATION UNIT 0 OSCILLATOR CONTROL MODE ............. NORMAL

SYNCHRONISATION UNIT 1 OSCILLATOR CONTROL MODE ............. NORMAL

TIMER: SYNCHRONISATION SIGNAL MALFUNCTION TOLERANCE TIME ... 5 MIN

TIMER: REPAIRED SYNCHRONISATION INPUT OBSERVATION TIME ..... 10 MIN



63 (100)

Synchronising the A interface

COMMAND EXECUTED

CL3TG:

INPUT STATE USED INPUT PRIORITY

----- --------------- ---------- ----------

2M1 CONNECTED 2M1 7

2M2 CONNECTED - 6

2M3 CONNECTED - 5

2M4 CONNECTED - 4

FS1 DISCONNECTED - 3

FS2 DISCONNECTED - 2

SYNCHRONIZATION UNIT WORKING MODE ......... HIERARCHIC SYNCHRONIZATION

FUNCTION AUTOMATIC RETURN FROM PLESIOCHRONOUS OPERATION .......... ON

FUNCTION AUTOMATIC USE OF REPAIRED INPUTS ........................ ON

SYNCHRONIZATION UNIT 0 OSCILLATOR CONTROL WORD VALUE ....... 31595

SYNCHRONIZATION UNIT 1 OSCILLATOR CONTROL WORD VALUE ....... 32211

SYNCHRONIZATION UNIT 0 OSCILLATOR CONTROL MODE ............. NORMAL

SYNCHRONIZATION UNIT 1 OSCILLATOR CONTROL MODE ............. NORMAL

TIMER: SYNCHRONIZATION SIGNAL MALFUNCTION TOLERANCE TIME ... 5 MIN

TIMER: REPAIRED SYNCHRONIZATION INPUT OBSERVATION TIME ..... 10 MIN

COMMAND EXECUTED

2. Create or delete synchronisation inputs if necessary (DRC, DRD).

ZDRC:<synchronization input>;

ZDRD:<synchronization input>;


synchronization input 2M1, 2M2, 2M3 (and 2M4 in CL3TG).

The number of synchronisation inputs depends on how many PCM/T1circuits are connected between the MSC and the BSC. The maximumamount of synchronisation inputs is 3 in CL1TG and 4 in CL3TG.

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 tocorrect them.



BSS Integration

Steps

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

. When: The synchronisation units are not in synchronousoperation mode.

Force the synchronisation units to use a specific input(DRS).

ZDRS::U=<2M1 - 2M4>;. When: The CL1TG will search the entire control range in

order to lock the units to a certain input.

Wait for the alarm to be cancelled (which may take acouple of minutes) and remove the forced use of input(DRS).

ZDRS::U=OFF;. When: Operation mode is not hierarchical.

Check that the operation mode has been set tohierarchical (DRM).

ZDRM:H;. When: The settings of the ETs are not correct.

Check the settings of the ETs.

The TCL signal should be 8 kHz. In ET1E it is selected bystrapping, but in ET2E it is 8kHz permanently.

. When: The control words of both CL1TGs and CL3TGsapproach the values 0 to 65534.

Check the connection of the PCM/T1.

It is possible that the incoming PCM/T1 circuit is connectedto a loop.

5. Change the synchronisation inputs.

Steps

a. Disconnect the incoming signal from the first input.

Expected outcome



65 (100)


This will cause normal PCM/T1 circuit alarms. After a time delay ofmore than the timer: SYNCHRONISATION SIGNALMALFUNCTION TOLERANCE TIME allows, bothsynchronisation units will change to the second input. This can beseen in the LEDs of the CL1TG/CL3TG plug-in units and on thealarm printer:

2641

FAILURE IN SYNCHRONISATION SIGNAL

0630

SYNCHRONISATION SIGNAL CHANGED

b. Disconnect the incoming signal from the second output.

Expected outcome

The results should be similar to the earlier ones.

6. Go to plesiochronous mode of operation.

Disconnect the incoming signal from the third input (the lastsynchronisation input has been disconnected) in CL1TG or fourth inCL3TG.

Expected outcome

The synchronisation units will go to PLESIOCHRONOUS OPERATIONmode. All synchronisation input indicators in the active CL1TG/CL3TGunit will extinguish, only the current indicator light is on. All 3/4 inputindicators in the passive CL1TG/CL3TG unit are lit, but not the currentindicator light. The alarm printer will print out the following:

2641


2631

OPERATION MODE CHANGED TO PLESIOCHRONOUS

7. Return to synchronous mode of operation.

Return the PCM/T1 circuits to their normal state one by one starting fromthe circuit with the lowest priority.

Expected outcome



BSS Integration

The synchronisation units will synchronise themselves to the input 2M3/2M4 after a time delay of more than the timer REPAIREDSYNCHRONISATION INPUT OBSERVATION TIME. On the alarmprinter the following alarms will be cancelled:

2641


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.



67 (100)




BSS Integration

7 Adding DN2, SSS, DMR and BBM to theservice channel

The connection between the BSC and the managed equipment is establishedeither through a BSC-BTS O & M link or a Q1 service channel. The possibleequipment types at a Base Transceiver Station (BTS) site include Base StationInterface Equipment (BIE), Transmission Unit (TRU), Digital Microwave RadioLink (DMR), and other transmission equipment (TRE).

All equipment with the same alarm unit type must have a unique index in theBSC concerned. All equipment in the same channel must have a unique address.

DN2 The Q1 service channel comes in TSL31 bits 7-8 to the 2Mport of the DN2 interface unit (IU2). The Q1 service channelis forwarded through an extra loop connection to the ControlUnit (CU); either one port of the IU2 is connected to the 2Minterface of the CU or two IU2 ports are connected togetherwith a local cable. The supported baud rates of the servicechannel are 1200, 2400 and 4800.

SSS The Supervisory Substation is located in the same rack withother transmission equipment, normally with the DN2. TheQ1 service channel is forwarded to the SSS with a local cable.

DMR The Digital Microwave Radio link cannot pick the Q1 servicechannel from a time slot. The Q1 service channel is forwardedto the DMR with a local cable from another source, normallyDN2. The supported baud rates of the service channel are1200, 2400, 4800, and 9600.

BBM The Baseband Modem cannot pick the Q1 service channelfrom a time slot. The Q1 service channel is forwarded to theBBM through an Integrated Line Terminal (ILT) plug-in unitfrom the DN2.

TRE Other types of transmission equipment, for example opticalline equipment, are handled in the BSC with the commonname Transmission Equipment (TRE).



69 (100)

Adding DN2, SSS, DMR and BBM to the service channel

Figure 14. Transmission equipment at Q1 service channel


Steps

1. Create the service channel (QWC).

ZQWC:<service channel number>, [S | P def]:<baudrate>,<bandwidth>,<used bits>:<external PCM-TSL>,<sub tsl>;

If you want to utilise Q1 bus protection in BSC, you must create secondarychannels 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>;

MMI SYSTEM

MMLDN2

ILT

SSS

DMR

TRE

BBM

TRE Q1ch

Q1ch

Nokia NetActLocalQ1bus

X.25/

LAN



BSS Integration

Addresses have to be set locally to the equipment with a hand-held serviceterminal.

3. Change the state of the service channel (QWS).

ZQWS:<service channel number>:AL;



71 (100)

Adding DN2, SSS, DMR and BBM to the service channel



BSS Integration

8 Creating the Abis interface


In this phase, the ET is connected to the Abis interface to connect the basestations to the BSC (see the figure below).

Figure 15. Abis interface

Steps

1. Check that the ET is connected (WUP).

The ET must be connected before it can be used. See Connecting the Ainterface ET for how to check if the ET is already connected.

Check that the ET is connected with the WUP command.

BTSBSC

ET TRU

Abis interface

OMU

TRX 1

TRX 2

TRX 3

OMUSIG

TRXSIG1 + 8 TCHs

TRXSIG2 + 8 TCHs

TRXSIG3 + 8 TCHs



73 (100)

Creating the Abis interface


. When: ET is already connected

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 isloaded into the unit.

ZUSU:ET,<pcm_index>,C=TOT;. When: ET is not connected

Connect the ET (WUC).

ZWUC:ET,<ET index>:<plug-in unit type>,0:IF=ABIS:BCSU,<BSCU index>;


plug-in unit type Type of the ET:

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

ANSI: ET2A, ET2A-T, or ET4A.

Steps

i. Change the state of the BCSU to WO-EX.

ii. Change the state of the ET to WO-EX.

3. Check and change the frame alignment mode (ETSI)/T1 functionalmode (ANSI) for ET if needed.

See Connecting the A interface ET for more information about configuringthe frame alignment mode/T1 functional mode.



BSS Integration

9 Initialising base stations

Each base station has one LAPD link called OMUSIG (see figure Abis interface). It is connected to the Operation and Maintenance Unit (OMU) of the basestation and used for O&M purposes like remote sessions to the BTS, softwareup- and downloading, transferring of alarms, and transferring of configurationinformation.

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 slotsare used for signalling. 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 theBSC's radio network database. In terms of BSC, a base station consists of BCF,BTSs, TRXs, and handover and power control parameters.

The procedure is slightly different depending on the type of the base station. Themain difference between the integration of Nokia PrimeSite and the base stationsof other generations is that in PrimeSite, each TRX also has an OMU link inaddition to a TRX link. This is due to the fact that each TRX is actually a basestation.

Another difference is that the hardware database is attached only to Nokia 2ndgeneration and Talk-family base stations. In the other types, the TEI of the TRXlinks is the same as the TRX number in the BSC. The TEI of the OMU links isalways 1.

The following instructions apply to Nokia 2nd generation, Talk-family,PrimeSite, UltraSite EDGE, MetroSite, Flexi EDGE, and InSite base stations.




75 (100)

Initialising base stations

9.1 Creating LAPD links and a base station, andinitialising the base station parameters

A LAPD link can be created either to a certain physical Base Station ControllerSignalling Unit (BCSU) or to a logical BCSU address. When the link is created toa logical BCSU address the actual controlling unit may not necessarily be the onegiven in the command. The concept of logical BCSU address was introduced toeliminate the effect of BCSU switchovers to radio network planning. In terms ofMMI commands, only the command name is different with logical BCSUaddresses.

It depends on the type of the BTS which links must be created. For moreinformation, 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 signallinglink (OMUSIG) and TRX signalling links (TRXSIG). If you are creating a64kbit link, do not give <SUB-TSL> .

ZDSE:<D-channel link set name>:BCSU,<unit index>:<service access point identifier>,<terminal endpointidentifier>:<bitrate>,<PCM-TSL>,<SUB-TSL>;


service access point identifier 62 for OMUSIG, 0 for TRXSIG.

terminal endpoint identifier Must the same as defined in the BTS. Usually thesame as the TRX number. For OMU link, the value is1.

If logical BCSUs are used, use the DSL command with the sameparameters.

2. Create a base control function (EFC).

The base control function (BCF) is a logical counterpart of the actual basestation. It is connected to the OMUSIG link created earlier.



BSS Integration

As a default, the operational state of the new BCF is 'Locked' (L). Sinceyou cannot create the TRXs if the operational state of the BSC is'Unlocked', you must first create the entire BCF site (BCF, BTS, and theTRXs) before you can change the state of the BCF to 'Unlocked'.

. All site types except Nokia PrimeSite and Nokia InSite if it is beingautoconfigured:

ZEFC:<bcf identification>,<site type>:DNAME=<D-channel link set name>;

. Nokia PrimeSite:

ZEFC:<bcf identification>,<site type>;


The BCF parameters can be modified later with the EFM and EFTcommands if needed.

3. Create a base transceiver station (EQC).

A base transceiver station (BTS) is a logical counterpart of a sector in abase station site. It should not be confused with a base station even thoughthey have the same abbreviation.

ZEQC:BCF=<BCF identification>,BTS=<BTSidentification>,NAME=<BTS name>,:CI=<cellidentity>,BAND=<frequency band in use>:NCC=<networkcolour code>,BCC=<BTS colour code>:MCC=<mobilecountry code>,MNC=<mobile network code>,LAC=<location area code>:;

Note

The BTS parameters can be modified later with the EQE , EQF , EQG , EQH , EQJ, EQK , and EQM commands. The BTS must be locked when modifying the BTSparameters.

4. Create a transceiver (ERC).

A transceiver (TRX) is a logical counterpart of the transmitter-receiverequipment in the base station. It is connected to the TRXSIG link createdearlier.



77 (100)


. All site types except Nokia PrimeSite and Nokia InSite if it is beingautoconfigured:

ZERC:BTS=<BTS identification>,TRX=<transceiveridentification>::FREQ=<frequency>,TCS=<training sequence code>,PCMTSL=<Abisspeech circuit>:DNAME=<D-channel telecom linkset name>:CH0=<RTSL type 0>,SIGN=<subslots forsignalling>;

. Nokia PrimeSite:

To create a TRX to the Nokia PrimeSite BTS you must also definethe D-channel O&M link set number.

ZERC:<BTS identification>,<TRXidentification>::FREQ=<frequency>,TCS=<training sequence code>,PCMTSL=<Abisspeech circuit>:<D-channel telecom link setname>,<D-channel O&M link set number>:<RTSLtypes from 0 to 7>;

5. Create default power control parameters of the BTS (EUC).

Each cell must have a power control parameter set.

ZEUC:BTS=<BTS identification>;


You can modify the power control parameters with the EUG , EUA , EUQ ,and EUS commands.

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 thecell.

Create the adjacent cells.



BSS Integration

. Adjacent cell located in the same BSC:

ZEAC:BTS=<BTS identification>:ABTS=<adjacentcell identification>;

. Adjacent cell located in a different BSC:

ZEAC:BTS=<BTS identification>:LAC=<locationarea 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 Nokia PrimeSite if necessary(EFM).

Note

The synchronisation needs to be checked in the case of Nokia PrimeSite.

Check that the synchronisation is suitable. The default is the internal clockof the BTS.

Change the synchronisation of the BCF to external synchronisation ifnecessary:

ZEFM:<BCF identification>:ESS=<externalsynchronisation source>,MCT=<master clock trx>;

When ESS values and their meanings are:

. 0: BTS internal.

master-TRX is not synchronised to external PCM

master-TRX uses its own internal clock to generate a clock signal toslave-TRXs

. 2: PCM external.

master-TRX is synchronised to external PCM

master-TRX uses an external clock to generate a clock signal toslave-TRXs

. 3: other external.

This parameter value is meant for example for GPS (GlobalPositioning System) and it may be used for synchronisation in thefuture.



79 (100)


MCT values and their meanings are:

. 0 indicates that the site is not synchronised (stand-alone)

. 1-16 indicates that the site is synchronised

Note

If you change ESS to have value 2, then you must give MCT a value between 1and 16. Also keep in mind that when you modify the master clock TRX, the BCFmust be locked.

9. Check and change the synchronisation of Nokia TalkFamily, UltraSite,Flexi EDGE, and MetroSite BTSs if necessary (EFM).

Check that the synchronisation is suitable. The default is the internal clockof the BTS.

Change the synchronisation of the BCF to external synchronisation ifnecessary.

If the synchronisation settings are not defined or synchronisation is notenabled for the BCF(s) in the BSC Radio Network database, then the BTSsite's own synchronisation settings are valid.

There are three alternative ways to define synchronisation for the BTS (andLMU) via BSC: the internal clock of the BTS, BSS synchronisation, andSite synchronisation.

For further information on changing synchronisation settings of basestations, see Activating and Testing BSS11073: Recovery for BSS and SiteSynchronisation.

For instructions on changing the BTS site's synchronisation settings, seethe relevant BTS documentation.


Example 9. Create a BCF according to the Abis time slot allocation shownin the table.

0 LINK MANAGEMENT

1 TRXSIG1 OMUSIG TCH.2 TCH.3 TRX 1



BSS Integration

0 LINK MANAGEMENT

2 TCH.4 TCH.5 TCH.6 TCH.7

3 TRXSIG2 TCH.1 TCH.2 TCH.3 TRX 2


1. Create LAPD links

ZDSE: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 BCF

ZEFC: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 TRXs

ZERC: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.

Example 10. Create a 1+1 site using Nokia PrimeSite base stations.

The Abis time slot allocation is shown in the following table.

0 LINK MANAGEMENT

1 TCH.0 TCH. 1 TCH.2 TCH.3 TRX 1



81 (100)


0 LINK MANAGEMENT


3 TCH.0 TCH.1 TCH.2 TCH.3 TRX 2

TCH.4 TCH.5 TCH.6 TCH.7

25 TRX.1 OMU.1 TRX.2 OMU.2

1. Create LAPD links.

ZDSE:B0101:BCSU,0:62,1:16,33-25,2;

ZDSE:B0102:BCSU,0:62,1:16,33-25,6;

ZDSE:T0101:BCSU,0:0,1:16,33-25,0;

ZDSE:T0102:BCSU,0:0,2:16,33-25,4;

2. Create BCF.

ZEFC:1,F;

3. Create BTSs.

. ETSI:

ZEQC:BCF=1,BTS=1,NAME=CELL1,:CI=1,BAND=900:NCC=0,BCC=0:MCC=512,MNC=18,LAC=1:;

ZEQC:BCF=1,BTS=2,NAME=CELL2,:CI=2,BAND=900:NCC=0,BCC=0:MCC=512,MNC=18,LAC=2:;

. ANSI:

ZEQC:BCF=1,BTS=1,NAME=C1,:CI=1,BAND=1900:NCC=0,BCC=0:MCC=512,MNC=18,LAC=1:;

ZEQC:BCF=1,BTS=2,NAME=C2,:CI=2,BAND=1900:NCC=0,BCC=0:MCC=512,MNC=18,LAC=2:;

4. Create TRXs.

ZERC:BTS=1,TRX=1::FREQ=55,TSC=0,PCMTSL=33-1:DNAME=T0101,ONAME=B0101:CH0=MBCCB;

ZERC:BTS=2,TRX=2::FREQ=66,TSC=0,PCMTSL=33-3:DNAME=T0102,ONAME=B0102:CH0=MBCCB;



BSS Integration


Next, attach the BCF software build to the BCF.

9.2 Attaching the BCF software build to the BCF

Base station software is kept in the BSC's hard disks. There are 40 directories forBTS software builds and one directory for BTS hardware databases (see figureBTS software directories ). Usually, only some of the directories are needed sincethe base stations can use the same builds with each other.

Figure 16. 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 buildto it from the floppy disk.

IWX , IWY , IBC

2. Create BTS software build (EWC).

ZEWC:<build id>:MF=<master file name>,EXT=<masterfile extension>,SDIR=<subdirectory name>;

3. Set initial software build; optional (EWS).

BTS SW files

AS8_8_14_0

ROOT

SCMANA BCF_PACK

PACK_0 PACK_39 HWDATA...

BTS SW files BTS HW databases



83 (100)


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 thesoftware 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. Thecommand cuts all ongoing calls in the reseted BTS site. Confirm by YES(Y) or NO (N).


Next, attach the BTS hardware database to the BTS.

9.3 Attaching the BTS hardware database to the BTS

Note

This is done only for Nokia 2nd generation and 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 start

Before proceeding, you must have suitable hardware database files available. SeeBTS documentation on how to prepare a BTS hardware database.



BSS Integration

Steps


. When: The BTS does not yet have a valid hardware database

Once the BTS hardware configuration is available, copy it to theBSC.

The database files are:

HWDATA_T.<ext>Database file in text format

HWDATAOM.<ext>Database file in binary format

. When: The BTS already has a valid hardware database

Upload the hardware database to the BSC (EVU).

If the BTS already has a valid hardware database, it can be uploadedto 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 tothe BSC, the database must be created.

ZEVC:<database id>:NAME=<file name>,EXT=<fileextension>;

3. Attach hardware database to the BCF (EVA).

ZEVA:<bcf identity>:<database id>;


. When: The hardware database has already been downloaded to theBTS

Activate the hardware database without downloading (EVV).

ZEVV:<bcf identity>:PAS:NODL;. When: The hardware database is not in the flash

Activate the hardware database with site reset (EVV).



85 (100)


The Operation and Maintenace Unit (OMU) link must beoperational 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 inuse. Site reset is needed to take it into use:

ZEVV:<bcf identity>:PAS:NORST;


Next, take the base station into use.

9.4 Taking the base station into use

In 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 theTRX links to WO-EX:

ZDTC:<D-channel link set name>:,WO;


D-channel link set name Name of the LapD link.

2. Unlock the TRXs (ERS).

If the higher level objects are already unlocked the transition from lockedto unlocked causes a TRX reset in the BTS site. Otherwise, the reset is notdone.

ZERS:BTS=<BTS identification>,TRX=<transceiveridentification>:U;

3. Unlock the BTSs under the BCF (EQS).



BSS Integration

If the BCF is already unlocked the transition from locked to unlockedcauses 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 outcome

The transition from locked to unlocked causes a BCF reset. While the BCFis 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 norcontrollable by MML.

5. Monitor BCF reset.

Monitor the phases of the BCF reset with the service terminal extensionBCF PHASE MONITORING, RPHASESX.

Steps

a. Take the extension into use with the service terminal command.

ZDDS;ZLE:<character>,RPHASESX

character Command character for the extension. Must notbe used by other extensions.

b. Go to the extension command group.

Z<character>

c. Start monitoring.

DC:<bcf_nbr>

Expected outcome

The reset is over when all its components and the BCF itself are in WO(working) state.

6. Unlock the BCF (EFS).

ZEFS:<BCF identification>:U;



87 (100)




BSS Integration

10 Testing BSS integrationBefore you start

The test requires one of each network element (BTS, BSC, MSC, and HLR ), andin fault conditions a PCM/T1 analyser (PC with GSM Protocol Analyser to traceA/Abis messages). All the network elements and connections must be operativeand the network configuration valid.

Figure 17. 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 TestCases.


10.1 Testing local blocking of a TRX

The purpose of the test is to verify the correct working of the BSS in localblocking (OMU MMI) of a TRX

BTS BSC

Abis

MS

MS

MS

BTS

Protocol Analyzerfor G.703 i/f

A and Abis monitor

A

TO MSC,HLR, VLR

TCSM



89 (100)

Testing BSS integration

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 stateand operative.

4. Lock the TRX locally from the BTS OMU MMI.

5. Unlock the TRX locally from the BTS OMU MMI.

6. Check any new alarms in the system.

Expected outcome

1. An alarm concerning a TRX lock is raised.

2. When the TRX is locked locally an announcement concerning this state isalso sent to the BSC, and the BSC MML also shows that the TRX is lockedand 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 theTCSM2.

Steps

1. Verify that transmission is working correctly and there are notransmission 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 hardwarein the racks.

Use the service terminal command ZGT .

4. Cause a channel fault to the transcoder unit.



BSS Integration

Do this for example by pulling out a TR16 (ETSI) or TR12 (ANSI) plug-inunit.


Expected outcome

Alarm 2952 TRANSCODER PLUG-IN UNIT FAILURE is active.

10.3 Testing the supervision of the TCSM3i (ETSI/ANSI)

The purpose of the text is to verify the correct working of the supervision of theTCSM3i.

Steps

1. Verify that transmission is working correctly and there are notransmission alarms active in the BSC.

2. Check the settings of the TCSM3i with remote MML ZDDT.

Use the command ZDDT .

3. Check that the TCSM3i hardware configuration matches thehardware in the racks.

Use the service terminal comman ZGT .

4. Cause a channel fault to the transcoder unit.

Do this for example by pulling out a TR3E (ETSI) or TR3A (ANSI) plug-in unit.


Expected outcome

Alarm 2952 TRANSCODER PLUG-IN UNIT FAILURE is active.

10.4 Testing IMSI Attach

The purpose of the test is to verify the correct working of the BSS in IMSI attach .



91 (100)


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 updating

The purpose of the test is to verify the correct working of the BSS in locationupdating.

Steps



3. Supply the PIN to the mobile station.


Expected outcome

The mobile station finds the network and ends on service state.

10.6 Testing MS to MS call

The purpose of the test is to verify the correct working of the BSS in a basic call.

Steps




BSS Integration


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 outcome

The call is successful and speech quality is good.

10.7 Testing MS to MS call, B busy

The purpose of the test is to verify the correct working of the BSS in a basic callwhen 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 atsubscriber A's MS.

5. Check that there are no hanging resources.


Expected outcome

Subscriber A receives the busy tone.



93 (100)


10.8 Testing MS to MS call, A subscriber IMSI detach

The purpose of the test is to verify the correct working of the BSS in a basic callwhen 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 TCHs

The purpose of the test is to verify the correct working of the BSS in a successfulhandover, where free TCHs are available.

Steps



3. Check that there are free TCHs in the BTS where the subscriber Awillmove.



6. Make a handover to subscriber A.



BSS Integration

7. Verify speech quality.


Expected outcome

The handover is successful and speech quality is good all the time.

10.10 Testing unsuccessful handover: no free TCHs

The purpose of the test is to verify the correct working of the BSS in anunsuccessful handover, where no free TCHs are available.

Steps



3. Make sure that there are no free TCHs in the BTS where subscriber Awill move.



6. Make a handover attempt to subscriber A.


Expected outcome

The handover fails and the call is released by the network unless the originalchannel is still adequate to continue the call.

10.11 Testing radio resource queuing in handover

The purpose of the test is to verify the correct working of the BSS in a successfulhandover, where a radio resource has to be queued.

Steps




95 (100)





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 outcome

The handover is successful after queuing and the call continues.



BSS Integration

11 Test logs for BSS integration

While integrating the BSS, record confirmation on test execution and possiblecomments in the test logs.

Part of the logs can be used as a check list while testing.

Table 10. BSS specifications

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:



97 (100)

Test logs for BSS integration

Table 11. Creating the A interface

Observations:

Corrective actions:

Checked by:

Date:

Approved by:

Date:

Table 12. Creating the Abis interface

Observations:

Corrective actions:



BSS Integration

Table 12. Creating the Abis interface (cont.)

Checked by:

Date:

Approved by:

Date:

Table 13. Initialising the base stations

Observations:

Corrective actions:

Checked by:

Date:

Approved by:

Date:



99 (100)

Test logs for BSS integration

Table 14. Testing BSS integration

TEST NUMBER:

Observations / used parameter values:

TESTING STATUS (OK/NOK):

Corrective actions/remarks:

Tested by:

Date:




BSS Integration

bss integration[1]

Documents