BSS administer

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

Administer

Radio Network Administration

DN9812407

Issue 19-2Approval Date 2011-08-27

Confidential

2 DN9812407Issue 19-2


Id:0900d805808c839aConfidential

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

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

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

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

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

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

Copyright © Nokia Siemens Networks 2011. All rights reserved

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

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

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

The same text in German:

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

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

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

DN9812407 3



Table of contentsThis document has 54 pages.

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

1 Creating D-channels on Abis interface . . . . . . . . . . . . . . . . . . . . . . . . . . 81.1 Creating an O & M signalling link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2 Creating a telecom signalling link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Adding a new BTS site under the BSC . . . . . . . . . . . . . . . . . . . . . . . . . 102.1 Creating the radio network object instances . . . . . . . . . . . . . . . . . . . . . 102.2 Activating the O & M link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3 Downloading the software build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.4 Taking the new BTS site into operation . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 Adding a new BTS to the BSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.1 Creating a new BTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.2 Creating a set of power control parameters. . . . . . . . . . . . . . . . . . . . . . 153.3 Creating a set of handover control parameters . . . . . . . . . . . . . . . . . . . 163.4 Defining and adding the adjacent GSM cells . . . . . . . . . . . . . . . . . . . . . 173.5 Defining and adding the adjacent WCDMA RAN cells <option> . . . . . . 193.6 Defining and adding the TD-SCDMA RAN adjacent cells <option>. . . . 213.7 Defining and adding the LTE adjacent cells. . . . . . . . . . . . . . . . . . . . . . 233.8 Creating the TRXs and their logical radio time slots . . . . . . . . . . . . . . . 233.9 Taking the new BTS into operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4 Adding a new TRX to the BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.1 Creating a BCCH TRX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.2 Taking the new TRX into operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

5 Deleting network elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.1 Deleting a TRX from the BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.2 Deleting a BTS from the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.3 Deleting a BTS site from the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

6 Modifying the Location Area (LA) or the Cell Identity (CI) of a BTS. . . . 31

7 Modifying the BTS site type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

8 Activating the hopping modes of a BTS. . . . . . . . . . . . . . . . . . . . . . . . . 35

9 Modifying the BCCH frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

10 Modifying the frequency of other than the BCCH TRX . . . . . . . . . . . . . 38

11 Modifying the O & M signalling link or its ET-PCM . . . . . . . . . . . . . . . . 40

12 Modifying the telecom signalling link or ET-PCM of the TRX . . . . . . . . 41

13 Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE and Flexi Multiradio only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

14 Locking and unlocking radio network objects . . . . . . . . . . . . . . . . . . . . 4314.1 Locking radio network objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4314.2 Unlocking radio network objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4 DN9812407



15 Errors in radio network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 4615.1 I/O errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4615.2 Errors due to inadequacies in radio network administration resources . 4715.3 Errors in distributing the BSS radio network data to the BTS site. . . . . . 4715.4 Checking errors in distributing the modified BSS radio network configura-

tion data within the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

16 Radio Network Configuration for Packet Abis. . . . . . . . . . . . . . . . . . . . . 5016.1 Create ETP-PCU Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5016.2 Create SCTP associations for OMUSIG & TRXSIG . . . . . . . . . . . . . . . . 5016.3 Create D-channels for OMUSIG & TRXSIG . . . . . . . . . . . . . . . . . . . . . . 5016.4 Create Abis HDLC links (only in case of Packet Abis over TDM) . . . . . . 5116.5 Create BCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5116.6 Open Abis HDLC links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5216.7 Create BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5216.8 Create HOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5216.9 Create POC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5316.10 Create TRX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5316.11 Attach software package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5316.12 Activate GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5416.13 Unlock/activate created objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

DN9812407 5



List of figuresFigure 1 RTSLs in a TRX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

6 DN9812407



DN9812407 7

Radio Network Administration Summary of changes

Id:0900d805808c8398Confidential

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

Changes made between issues 19-2 and 19-1Information on feature RG301613-004:BTS site type modification restriction and BSC support for FSM3 module has been updated in the chapter Modifying the BTS site type and Adding a new BTS site under the BSC.

Changes made between issues 19-1 and 19-0Step to modify PCM Port IDs parameter has been removed in the chapter Adding a new BTS site under BSC .

Changes made between issues 19-0 and 18-4A new chapter Radio Network Configuration for Packet Abis has been added.

A new section Defining and adding the LTE adjacent cells in chapter Adding a new BTS to the BSC has been added.

Changes made between issues 18-4 and 18-3Flexi Multiradio BCF information has been updated in chapter Adding a new BTS site under the BSC.

Information on Modification of the BTS site type for Flexi Multiradio has been updated in chapter Modifying the BTS site type.

Flexi Multiradio Information has been added in chapter Adding an External input and output text.

Changes made between issues 18-3 and 18-2The instructions for modifying the LA or CI information to the adjacent cell lists have been clarified in chapter Modifying the Location Area (LA) or the Cell Identity (CI) of a BTS.

Changes made between issues 18-2 and 18-1In the Creating D-channels on Abis interface chapter, information on usage of multi-plexed link with BTSplus has been added and the ZDSE command has been modified.

In the Adding a new BTS site under the BSC chapter, information on PCM Port IDs parameter has been added.

In the Adding a new BTS to the BSC chapter, a step to create the BTSplus BTS (EQC) using the BTS HW parameter has been added.

Changes made between issues 18-1 and 18-0Information on InSite BTS has been removed.

8 DN9812407


Id:0900d8058078a2edConfidential

Creating D-channels on Abis interface

1 Creating D-channels on Abis interfaceThe D-channels on the Abis interface are the O & M signalling link (OMU link, OMUSIG) and the telecom signalling link (TRX link, TRXSIG). You must create the O & M signal-ling link before creating a BCF. The telecom signalling link is needed before a TRX is created. If you are adding a new BTS site, it is practical to create both links first before creating the BCF, although the TRX link is not needed until before creating the TRX.

After creating the links, activate them by setting them to working state (WO). You can do this immediately after creating the links or just before unlocking the created objects. Sometimes during activation the state of the link becomes BL-SYS instead of WO. However, when you unlock the TRXs, the link will change to WO state.

For more information on radio network administration, see Radio Network Configuration Management.

The Base Station commissioning is described in BTS Product Documentation. For Flexi EDGE and Flexi Multiradio Base Stations, you can use BSS20847: Automatic Commis-sioning of the Flexi EDGE and Flexi Multiradio BTSs to automatically configure the Abis allocations at the Base Station. For more information, see Flexi EDGE BTS Commis-sioning in the Flexi EDGE Base Station Product Documentation or Commissioning Flexi Multiradio BTS GSM/EDGE document.

In the case of the BTSplus you can use multiplexed OMU link and TRX links, which means that several links are multiplexed into the same Abis allocation.

1.1 Creating an O & M signalling linkSteps

1 Check the BCSU for signalling capacity (EEI).ZEEI::<unit type>;

2 Create the O & M signalling link (DSE).ZDSE:<D-channel link set name>,<D-channel link set number>:<unit type>,<unit index>:<service access point identifier>,<terminal end point identifier>:<bit rate>,<PCM-TSL>,<SUB-TSL>:<D-channel type>,<D-channel parameter set>;

3 Activate the new link (DTC).ZDTC:<D-channel link set name>:<D-channel state change>;

Further information

Example:

1. Find a suitable BCSU with signalling capacity available for the new link.ZEEI::BCSU;

2. Create an O & M signalling link. This procedure is not always recommended at this point. For more information, see the tip on creating O & M links. ZDSE:OMU23:BCSU,1:62,0:64,33–31;

DN9812407 9

Radio Network Administration Creating D-channels on Abis interface

Id:0900d8058078a2edConfidential

3. Change the new link to working state.This only needs to be done now if you are modifying the O & M signalling or the ET-PCM.ZDTC:OMU23:WO;As a default, the command changes the state of the primary D-channel.

t If you are adding a new BTS site to the network, go to section Adding a new BTS site under the BSC. You can activate the O & M link later according to the procedure before activating the software build, or before unlocking the radio network objects at the latest.

1.2 Creating a telecom signalling linkSteps

1 Check the BCSU for signalling capacity (EEI).ZEEI::<unit type>;

2 Create the telecom signalling link (DSE).ZDSE:<D-channel link set name>,<D-channel link set number>:<unit type>,<unit index>:<service access point identifier>,<terminal end point identifier>:<bit rate>,<PCM-TSL>,<SUB-TSL>:<D-channel type,<D-channel parameter set>;

3 Activate the new link (DTC).ZDTC:<D-channel link set name>:<D-channel state change>;

Further information

Example:

1. Find a suitable BCSU with signalling capacity available for the new link.ZEEI::BCSU;

2. Create a new telecom signalling link. ZDSE:TRX23:BCSU,1:0,5:64,33–30;

3. Change the new link to working state.ZDTC:TRX23:WO;As a default, the command changes the state of the primary D-channel.

10 DN9812407


Id:0900d805808c83adConfidential

Adding a new BTS site under the BSC

2 Adding a new BTS site under the BSCBefore you startBefore you can create a BCF according to these instructions, you must create the D-channels used on the Abis interface. The O & M signalling link has to be created for all site types. To create a TRX, you must also create the telecom signalling link for all site types. You can create both links first before proceeding to step 1 of this procedure, although the telecom signalling link is not needed until before creating the TRX.

To create the D-channel signalling links, see procedure Creating D-channels on Abis interface.

You can also create the MetroSite, UltraSite , Flexi EDGE, Flexi Multiradio, Flexi Multi-radio 10 and Flexi Compact types of BCFs with a reference BCF. For more information on creating a BCF, see the EFC MML command.

You can also define synchronisation settings for the Talk-family, MetroSite, UltraSite, Flexi EDGE Flexi Multiradio, Flexi Multiradio 10 and Flexi Compact types of BCFs, when you create the BCF. If BSS Synchronisation is going to be used for the BCF or if the BCF is a part of a Multi BCF cell, then synchronisation settings of the BCF(s) must be defined to the BSC's radio network database (BSDATA). For more information, see Activating and Testing Recovery for BSS and Site Synchronisation and BSS Synchro-nisation Recovery Improvement.

If the site type is BTSplus, you shall identify the PORT IDs of Abis PCMs in the BCF when the BCF is created or modified later.


To add a new BTS site under the BSC, you must complete the following procedures in this order:

2.1 Creating the radio network object instancesSteps

1 Create the BCF object instance for all site typesZEFC:<BCF identification>,<site type>,<site_subtype>:<D-channel link set name>;

2 Create the BTS object instance(s). See the procedure Adding a new BTS to the BSC.

3 Create the TRX object instances.See the procedure Adding a new TRX to the BTS.

Further information

Example:

1. Create the BCF(not for BTSplus ).

DN9812407 11

Radio Network Administration Adding a new BTS site under the BSC


• ZEFC:2,D:DNAME=OMU23; • Create the BCF for Flexi Multiradio 10 BTS • EFC:1,M,R:DNBR=2:::CS=TOP;

Create the BCF for Flexi COMPACT • EFC:1,M,C:DNBR=2:::;You can modify the default values for the BCF-specific parameters generated by the BSC radio network management system with the EFM and EFT commands.The radio network management system creates the BCF to the administrative state LOCKED. The administrative state of Flexi EDGE BTS and Flexi Multiradio BTS is also LOCKED after creation, but it is created as Automatic Unlock Allowed by default. It means that when the BTS site has been commissioned and it indicates the start up for the BSC, the BSC automatically changes the administrative state of the BCF to UNLOCKED.

2. Modification of PCM Port IDs parameter for BTSplus.ZEFM:1::::PORT0=1,PORT6=3;

3. Create the BTS(s).See the procedure Adding a new BTS to the BSC.

4. Create the TRXs.See the procedure Adding a new TRX to the BTS.

To add a BTS site under the BSC, you must next activate the O & M link.

2.2 Activating the O & M linkSteps

1 Activate the O & M link (DTC).ZDTC:<D-channel link set name>:<D-channel state change>;

Further information

Example:

1. Set the O & M link of the site to the normal operational state.ZDTC:OMU23:WO;As a default, the command changes the state of the primary D-channel.You can also activate the O & M link later, before unlocking the radio network objects, but then the software build downloading will only be executed after the unlocking commands.

To add a BTS site under the BSC, you must next download the software build.

2.3 Downloading the software buildIf the initial BCF software build has been defined for the site type in advance in the BCF software management system with the EWS command, the system downloads and acti-vates the initial BCF software build automatically during the BCF creation. This means that you do not have to manually operate the BCF software build handling at all. For more information, see BCF Software Handling.

12 DN9812407



Adding a new BTS site under the BSC

Steps

1 Create a BCF software build (EWC).ZEWC:<build id>:<master file name>,<master file extension>,<subdirectory name>;

2 Attach the software build to the BCF (EWA).ZEWA:<number of BCF>:<build status>:<build id>;

3 Check the state of the build attachment (EWI).ZEWI:<number of BCF>;

4 Activate the BCF (EWV).ZEWV:<number of BCF>:<build status>;

Further information

Example:

1. Create a BCF software build.ZEWC:B_9_0:MF=BTS_S300,EXT=214,SDIR=PACK_2;

2. Attach the software build to the BCF.ZEWA:2:BU:B_9_0;Attaching the software build initiates the software background downloading to the BTS site. The build cannot be activated with the EWV command until the background downloading is completed and the build is transferred to the BCF's non-volatile memory. The build downloading time depends on the O & M D-channel (64/32/16 kbit) used and on the size of the downloaded build.You can monitor the downloading on the display of the service terminal with the BCF Reset Phase Monitoring service terminal extension. For more information, see BCF Reset Phase Monitoring.

3. Check the state of the build attachment.ZEWI:2;The attachment is complete when the state of the activity in the command execution printout is NONE.

4. Activate the BCF with the new software build.ZEWV:2:BU;The command changes the default software build of the BCF. Normally, the build activation command causes a BCF restart with the new build, but in this case the BCF is not restarted because the administrative state of the BCF is LOCKED.The system rejects the build activation command if the software background down-loading procedure is still going on. In that case, the new build is not changed to the default build, and the activation command must be given again later.

To add a BTS site under the BSC, you must next take the new BTS site into operation.

DN9812407 13

Radio Network Administration Adding a new BTS site under the BSC


2.4 Taking the new BTS site into operationSteps

1 Unlock the BCF (EFS).ZEFS:<BCF identification>:<administrative state>;

Further information

Example:

1. Take the new site into operational use by unlocking the new BCF.ZEFS:2:U;The BCF unlocking operation causes the BCF site reset. The default software build of the BCF and BSS radio network configuration data stored in the BSC is trans-ferred to the BTS site. The software build of the BCF is not transferred to the BTS site if the BCF software build has been successfully transferred to the BCF's non-volatile memory in connection with the build attachment (the EWA command). When the Flexi EDGE BCF and Flexi Multiradio BCF are created to be Automatic Unlock Allowed by default, this step is not necessary. The BTS site will be unlocked automatically after the BTS site is commissioned. The BTSs' objects and TRXs' objects under the BCF shall be unlocked before the commissioning. The power control parameter set and the handover control parameter set should exist.

14 DN9812407


Id:0900d805807ddac7Confidential

Adding a new BTS to the BSC

3 Adding a new BTS to the BSCTo add a new BTS to the BSC, you must complete the following procedures in this order.


3.1 Creating a new BTSThe use of 'SEG' radio network object requires that SEGMENT USAGE option is in use.

Steps

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

a Create the BTS (EQC).ZEQC:<BCF identification>,<BTS identification>:<cell identity>,<frequency band in use>:<network colour code>,<BTS colour code>:<mobile country code>,<mobile network code>,<location area code>;

b Create the BTS with SEGMENT identification (EQC).ZEQC:<BCF identification>,<BTS identification>,<SEG identification>:<cell identity>,<frequency band in use>:<network colour code>,<BTS colour code>:<mobile country code>,<mobile network code>,<location area code>;

c Create the BTSplus BTS (EQC).ZEQC:<BCF identification>,<BTS identification>:<cell identity>,<frequency band in use>,<cell number in BTS HW>:<network colour code>,<BTS colour code>:<mobile country code>,<mobile network code>,<location area code>;

Further information

Example:

1. Create a new BTS.ZEQC:BCF=2,BTS=24:CI=33,BAND=900:NCC=3,BCC=4:MCC=111,MNC=02,LAC=3344;orZEQC:BCF=2,BTS=24,SEG=33:CI=33,BAND=900:NCC=3,BCC=4:MCC=111,MNC=02,LAC=3344;

2. Create BTSplus BTS.ZEQC:BCF=2,BTS=24:CI=33,BAND=900,CHW=3:NCC=3,BCC=4:MCC=111,MNC=02,LAC=3344;orZEQC:BCF=2,BTS=24,SEG=33:CI=33,BAND=900,CHW=3:NCC=3,BCC=4:MCC=111,MNC=02,LAC=3344;

Use the default values for a set of BTS-specific parameters generated by the BSC radio network management system or use a reference BTS for copying the corresponding parameter values. Any BTS created in the BSC can be used as a reference BTS.

DN9812407 15

Radio Network Administration Adding a new BTS to the BSC


You can modify the values for the BTS-specific parameters with the commands EQA, EQB, EQE, EQF, EQG, EQH, EQJ, EQK, EQM, EQT, EQV, EQN, EQX and EQY.

The radio network management system creates the BTS to the administrative state LOCKED.

To add a new BTS as a new cell to the BSC, you must next create a set of power control parameters.

3.2 Creating a set of power control parametersThe cell cannot be brought into use if the parameters controlling the power control pro-cedure are not defined.

Create a power control parameter set by using the default values generated by the BSC radio network management system or by using a reference cell for copying the corre-sponding parameter values. Any cell of the BSC with defined power control parameters can be used as a reference cell. If the cell uses only one band, one of the reference cell's bands must be the same.

Steps

1 Create the power control parameter set (EUC).ZEUC:<BTS identification>;

or

ZEUC:<SEG identification>;

or

ZEUC:<BTS identification>,<reference BTS identification>;

or

ZEUC:<SEG identification>,<reference SEG identification>;

2 Modify the power control parameters (EUG, EUA, EUQ, EUS, EUM and EUB).You can modify the power control parameters with commands

EUG, EUA, EUM, EUQ, EUS and EUB.

Further information

Example:

1. Create the power control parameter set.ZEUC:BTS=24;orZEUC:SEG=25;orZEUC:BTS=24,REF=103;orZEUC:SEG=25,RSEG=104;

2. If necessary, modify the power control parameters with the EUG, EUA, EUM, EUQ, EUS and EUB <option> commands. For more information, see Power Control Parameter Handling (EU).

16 DN9812407




To add a new BTS as a new cell to the BSC, you must next create a set of handover control parameters.

3.3 Creating a set of handover control parametersUse the default values generated by the BSC radio network management system or use a reference cell for copying the corresponding parameter values. Any cell of the BSC with defined handover control parameters can be used as a reference cell.

Steps

1 Create the handover control parameter set (EHC).ZEHC:<BTS identification>;

or

ZEHC:<SEG identification>;

or

ZEHC:<BTS identification>,<reference BTS identification>;

or

ZEHC:<SEG identification>,<reference SEG identification>;

2 Modify the handover control parameters (EHG, EHA, EHS, EHQ, EHI, EHD, EHN, EHX, EHY, EHP and EHB).You can modify the handover control parameters with commands

EHG, EHA, EHS, EHQ, EHI, EHD, EHN, EHX, EHY, EHP and EHB

Further information

Example:

1. Create the handover control parameter set.ZEHC:BTS=24;or ZEHC:SEG=25;or ZEHC:BTS=24,REF=103;or ZEHC:SEG=25,RSEG=104;

2. If necessary, modify the handover control parameters with the EHG, EHA, EHS, EHQ, EHI, EHD, EHN, EHX, EHY, EHP, and EHB commands. For more information, see EH - Handover Control Parameter Handling.

When adding a new BTS to the BSC, you can define and add the adjacent GSM cells and the adjacent WCDMA RAN cells next.

If you do not want to define adjacencies, move on to creating the TRXs and their logical radio time slots.

DN9812407 17



3.4 Defining and adding the adjacent GSM cellsWhen defining the adjacent GSM cells of a cell, you must define the adjacencies in both incoming and outgoing directions. Otherwise handovers are only possible in one direc-tion. You can define the adjacent GSM cells either by entering the adjacent cell identification or by entering the Mobile Country Code (MCC), Mobile Network Code (MNC), location area code (LAC) and cell identity (CI) of the adjacent GSM cell. MCC and MNC are only required if the adjacent GSM cell is in a different Public Land Mobile Network (PLMN).

Adjacent GSM cells can be located in the same BSC or in some other BSC, in the same PLMN or some other PLMN.

Steps


a Define and add an adjacent GSM cell under the same BSC (EAC).ZEAC:<BTS identification>::<adjacent cell identification>;

or

ZEAC:<SEG identification>::<adjacent cell identification>;

b Define and add an adjacent GSM cell under a different BSC in the same PLMN area (EAC).ZEAC:<BTS identification>::<location area code>,<cell identity>:<network colour code>,<BTS colour code>,<BCCH frequency>;

or

ZEAC:<SEG identification>::<location area code>,<cell identity>:<network colour code>,<BTS colour code>,<BCCH frequency>;

c Define and add an adjacent GSM cell under a different BSC in a different PLMN area (EAC).ZEAC:<BTS identification>::<mobile country code>,<mobile network code>,<location area code>,<cell identity>:<network colour code>,<BTS colour code>,<BCCH frequency>;

or

ZEAC:<SEG identification>::<mobile country code>,<mobile network code>,<location area code>,<cell identity>:<network colour code>,<BTS colour code>,<BCCH frequency>;


a Define the adjacency in the other direction, under the same BSC (EAC).ZEAC:<BTS identification>::<adjacent cell identification>;

or

ZEAC:<SEG identification>::<adjacent cell identification>;

18 DN9812407




b Define the adjacency in the other direction, under a different BSC in the same PLMN area (EAC).ZEAC:<BTS identification>::<location area code>,<cell identity>:<network colour code>,<BTS colour code>,<BCCH frequency>;

or

ZEAC:<SEG identification>::<location area code>,<cell identity>:<network colour code>,<BTS colour code>,<BCCH frequency>;

c Define the adjacency in the other direction, under a different BSC in a different PLMN area (EAC).ZEAC:<BTS identification>::<mobile country code>,<mobile network code>,<location area code>,<cell identity>:<network colour code>,<BTS colour code>,<BCCH frequency>;

or

ZEAC:<SEG identification>::<mobile country code>,<mobile network code>,<location area code>,<cell identity>:<network colour code>,<BTS colour code>,<BCCH frequency>;

Further information

Example:

1. Define and add an adjacent GSM cell under the same BSC.ZEAC:BTS=24::ABTS=128;orZEAC:SEG=25::ASEG=127;If the adjacent GSM cell is located in the same BSC, the system automatically checks the mutual validity of adjacent GSM cell data between the corresponding cell-specific data in BSDATA. If necessary, the system rejects the adjacent GSM cell definition command.If the MCC + MNC + LAC + CI (Mobile Country Code, Mobile Network Code, Location Area Code and Cell Identity) of the given adjacent GSM cell is not found in the BSDATA of the BSC, the radio network management system marks the adjacent GSM cell as a cell of some other BSC in the network. If a BTS with the same MCC + MNC + LAC + CI is later created to the BSC, the radio network management

DN9812407 19



system updates the adjacent GSM cell relation to be an adjacency between the cells in the same BSC.You must also define the BCCH frequency (with parameter FREQ) if the adjacent GSM cell does not have a BCCH TRX yet.Define and add an adjacent GSM cell under a different BSC.ZEAC:BTS=24::LAC=120,CI=13000:NCC=7,BCC=3,FREQ=100;orZEAC:SEG=24::LAC=120,CI=13000:NCC=7,BCC=3,FREQ=100;orZEAC:BTS=24::MCC=11,MNC=12,LAC=120,CI=13000:NCC=7,BCC=3,FREQ=100;orZEAC:SEG=24::MCC=11,MNC=12,LAC=120,CI=13000:NCC=7,BCC=3,FREQ=100;The base station identity code (BSIC) = NCC + BCC. If the warning

/ *** BCC + NCC + BCCH TRX FREQUENCY NOT UNIQUE IN ADJACENCY DEFINITIONS *** /appears in the output, use the EAT command to determine the adjacent GSM cell pairs whose parameter combination is no longer unique in the outgoing adjacent GSM cells of one cell.

2. Define the adjacency in the other direction, under the same BSC.For defining the adjacency within a BSS, enter the same command with the BTS or SEG and ABTS or ASEG parameter values reversed.ZEAC:BTS=128::ABTS=24;orZEAC:SEG=128::ASEG=24;Define the adjacency in the other direction, under a different BSC.ZEAC:BTS=128::LAC=150,CI=11000:NCC=6,BCC=5,FREQ=120;orZEAC:SEG=128::LAC=150,CI=11000:NCC=6,BCC=5,FREQ=120;orZEAC:BTS=128::MCC=15,MNC=16,LAC=150,CI=11000:NCC=6,BCC=5,FREQ=120;orZEAC:SEG=128::MCC=15,MNC=16,LAC=150,CI=11000:NCC=6,BCC=5,FREQ=120;

When adding a new BTS to the BSC, you can define and add the adjacent WCDMA RAN cells next, or move on to creating the TRXs and their logical radio time slots.

3.5 Defining and adding the adjacent WCDMA RAN cells <option>PurposeWhen defining the adjacent WCDMA RAN cells of a GSM cell, you must define the adja-cencies in both incoming and outgoing directions. Otherwise handovers are only possible from GSM to WCDMA RAN if the WCDMA RAN cell does not have the GSM cell as an adjacent cell in the RNC.

Adjacent WCDMA RAN cells can be located in an RNC in some other Public Land Mobile Network (PLMN) area or in an RNC in the same PLMN area as the GSM cell. You can define the adjacent WCDMA RAN cells either by entering the whole adjacent

20 DN9812407




WCDMA RAN cell identification or by excluding Mobile Country Code (MCC) and Mobile Network Code (MNC).

Before you startMake sure that the GSM-WCDMA Inter-System Handover is active in BSC. For more information on the activation of GSM-WCDMA Inter-System Handover, see Testing BSS10101 and BSS11107: GSM-WCDMA Interworking.

Steps

1 Check that GSM-WCDMA Inter-System Handover is active (WOS).ZWOS:<parameter class>,<parameter number>;


a Define and add an adjacent WCDMA RAN cell under the same PLMN area (EAE).ZEAE:<BTS identification>:<adjacent cell index>:<radio network controller identifier>,<cell identification>:<location area code>,<service area code>,<WCDMA downlink carrier frequency>,<scrambling code>;

or

ZEAE:<SEG identification>:<adjacent cell index>:<radio network controller identifier>,<cell identification>:<location area code>,<service area code>,<WCDMA downlink carrier frequency>,<scrambling code>;

b Define and add an adjacent WCDMA RAN cell under a different PLMN area (EAE).ZEAE:<BTS identification>:<adjacent cell index>:<mobile country code>,<mobile network code>,<radio network controller identifier>,<cell identification>:<location area code>,<service area code>,<WCDMA downlink carrier frequency>,<scrambling code>;

or

ZEAE:<SEG identification>:<adjacent cell index>:<mobile country code>,<mobile network code>,<radio network controller identifier>,<cell identification>:<location area code>,<service area code>,<WCDMA downlink carrier frequency>,<scrambling code>;

Further information

Example:

1. ZWOS:2,739;

2. Define and add an adjacent WCDMA RAN cell:

DN9812407 21



• under the same PLMN area.

ZEAE:BTS=24:INDEX=0:RNC=2340,CI=5670:LAC=130,SAC=567,FREQ=10,SCC=30;

or

ZEAE:SEG=25:INDEX=0:RNC=2340,CI=5670:LAC=130,SAC=567,FREQ=10,SCC=30;

• under a different PLMN area.

ZEAE:BTS=24:INDEX=0:MCC=200,MNC=300,RNC=2340,CI=5670:LAC=130,SAC=567,FREQ=10,SCC=30;

or

ZEAE:SEG=25:INDEX=0:MCC=200,MNC=300,RNC=2340,CI=5670:LAC=130,SAC=567,FREQ=10,SCC=30;

To add a new BTS to the BSC, you must create the TRXs and their logical radio time slots.

3.6 Defining and adding the TD-SCDMA RAN adjacent cells <option>PurposeWhen defining the adjacent TD-SCDMA RAN adjacent cells of a GSM cell, you must define the adjacencies in both incoming and outgoing directions. Otherwise handovers are only possible from GSM to TD-SCDMA RAN if the TD-SCDMA RAN cell does not have the GSM cell as an adjacent cell in the RNC.

TD-SCDMA RAN adjacent cells can be located in an RNC in some other Public Land Mobile Network (PLMN) area or in an RNC in the same PLMN area as the GSM cell. You can define the TD-SCDMA RAN Adjacent cells either by entering the whole TD-SCDMA RAN adjacent cell identification or by excluding Mobile Country Code (MCC) and Mobile Network Code (MNC).

Before you startMake sure that the GSM-WCDMA Inter-System Handover is active in BSC. For more information on the activation of GSM-WCDMA Inter-System Handover, see Testing BSS10101 and BSS11107: GSM-WCDMA Interworking.

Steps

1 Check that TD-SCDMA interworking, idle mode licence is “ON” or “CONF” (W7I).ZW7I:FEA,FULL:FEA=1022;

22 DN9812407





a Define and add a TD-SCDMA RAN adjacent cell under the same PLMN area (EAF).ZEAF:<BTS identification>:<adjacent cell index>:<radio network controller identifier>,<cell identification>:<location area code>,<service area code>,<TD-SCDMA downlink carrier frequency>,<cell parameter>;

or

ZEAF:<SEG identification>:<adjacent cell index>:<radio network controller identifier>,<cell identification>:<location area code>,<service area code>,<TD-SCDMA downlink carrier frequency>,<cell parameter>;

b Define and add a TD-SCDMA RAN adjacent cell under a different PLMN area (EAF).ZEAF:<BTS identification>:<adjacent cell index>:<mobile country code>,<mobile network code>,<radio network controller identifier>,<cell identification>,<location area code>,<service area code>,<TD-SCDMA downlink carrier frequency>,<cell parameter>;

or

ZEAF:<SEG identification>:<adjacent cell index>:<mobile country code>,<mobile network code>,<radio network controller identifier>,<cell identification>,<location area code>,<service area code>,<TD-SCDMA downlink carrier frequency>,<cell parameter>;

Further information

Example:

1. ZW7I:FEA,FULL:FEA=1022;

2. Define and add a TD-SCDMA RAN adjacent cell: • Under the same PLMN area.

ZEAF:BTS=24:INDEX=0:RNC=2340,CI=5670:LAC=130,SAC=567,FREQ=10,CPA=4;

or

ZEAF:SEG=25:INDEX=0:RNC=2340,CI=5670:LAC=130,SAC=567,FREQ=10, CPA=4;

DN9812407 23



• Under a different PLMN area.

ZEAF:BTS=24:INDEX=0:MCC=200,MNC=300,RNC=2340,CI=5670:LAC=130,SAC=567,FREQ=10, CPA=4;

or

ZEAF:SEG=25:INDEX=0:MCC=200,MNC=300,RNC=2340,CI=5670:LAC=130,SAC=567,FREQ=10, CPA=4;

To add a new BTS to the BSC, you must create the TRXs and their logical radio time slots.

3.7 Defining and adding the LTE adjacent cellsPurposeTo create new LTE adjacent cells to BSC RNW database.

Before you startLTE System Information license must be installed to BSC.

Steps

1 Adding the LTE adjacent cell (EAN).ZEAN:<SEG identification>:<lte adjacent cell index>:<mobile country code>,<mobile network code>,<LTE adjacent cell tracking area code>:<LTE adjacent cell downlink carrier frequency>;

Example:

1. ZEAN:SEG=6:INDEX=0:MCC=210,MNC=214,TAC=7:FREQ=16383;

3.8 Creating the TRXs and their logical radio time slotsSteps

1 Create the TRXs and their logical radio time slots.See procedure Adding a new TRX to the BTS.

Further informationAfter creating the TRXs you can take the new BTS into operation.

3.9 Taking the new BTS into operationSteps

1 Unlock the BTS (EQS).ZEQS:<BTS identification or BTS name>:<administrative state>;

24 DN9812407




Further information

Example:

1. Unlock the BTS.ZEQS:BTS=24:U;

DN9812407 25

Radio Network Administration Adding a new TRX to the BTS

Id:0900d805807948ebConfidential

4 Adding a new TRX to the BTSYou can increase the traffic capacity of a non-hopping, DFCA hopping, or an RF hopping BTS online, that is, by adding a new TRX without disturbing calls that are currently on. If the BTS has an activated BB or antenna hopping facility, adding a new TRX requires locking the BTS.

You can also modify the telecom signalling link or the ET-PCM of the TRX by deleting and then creating the TRX again with new D-channel or PCM values.

When you add a new TRX, the radio network management system creates a TRX and sets it to the administrative state LOCKED. As a default, the system creates the radio time slots and sets them to the administrative state UNLOCKED.

The procedure is slightly different for creating BCCH TRXs than for creating traffic TRXs. When creating a traffic TRX, the RTSL parameter is not obligatory.

The Base Station commissioning is described in BTS Product Documentation. For Flexi EDGE and Flexi Multiradio Base Stations, you can use BSS20847: Automatic Commis-sioning of the Flexi EDGE and Flexi Multiradio BTSs to automatically configure the Abis allocations at the Base Station. For more information, see Flexi EDGE BTS Commis-sioning in the Flexi EDGE Base Station Product Documentation or Commissioning Flexi Multiradio BTS GSM/EDGE document.

For information on Dynamic Abis, see Dynamic Abis.


Before you startBefore creating a TRX according to these instructions, the telecom signalling link must be created. If you have not already created the link together with the O & M signalling link, you must do it now before creating the TRX.

4.1 Creating a BCCH TRXSteps

1 Create a TRX and its logical RTSLs.When creating a traffic TRX, the RTSL parameter is not obligatory.

Steps

a Create a TRX to any BTS (ERC)ZERC:<BTS identification>,<TRX identification>::<frequency>,<training sequence code>,<Abis speech circuit>:<D-channel telecom link set name>:<RTSL types from 0 to 7>;

26 DN9812407



Adding a new TRX to the BTS

Further information

Example:

1. Create a TRX to any BTSZERC:BTS=24,TRX=5::FREQ=99,TSC=4,PCMTSL=22–24:DNAME=TRX23:CH0=MBCCHC,CH1=SDCCH;

Figure 1 RTSLs in a TRXControl channels and RTSL(s) of the NOTUSED type have no Abis allocation. In other words their Abis allocation is reserved for signalling.An E-TRX can have ERACH, SDCCH or traffic channels as its radio timeslot types.

You can modify the values for the TRX-specific parameters with the ERM, ERT, and ERY <option> commands.

4.2 Taking the new TRX into operationSteps

1 Check the D-channels of the TRXs (DTI).ZDTI;

The command has no parameters.

2 Unlock the TRXs (ERS).ZERS:<BTS identification or BTS name>,<transceiver identification>:<administrative state>;

Several TRXs can be unlocked at the same time with the wild card characters & and &&, if the higher objects (BTS or BCF) are still locked.

Further information

Example:

1. Check that the D-channels of the TRXs are in the normal functional state (the TRX link in BL-SY and the OMU link in WO-EX state).ZDTI;If they are not, activate the links with the DTC command as explained in the proce-dure Creating D-channels on Abis interface.

PCM-22

TSL-24

TSL-25

0

CH0

MBCCHC

0

CH4

TCHF

1

CH1

SDCCH

1

CH5

TCHF

2

CH2

TCHF

2

CH6

TCHF

3

CH3

TCHF

3

CH7

TCHF

Subslot

Subslot

DN9812407 27

Radio Network Administration Adding a new TRX to the BTS


2. Change the administrative state of each new TRX to UNLOCKED.ZERS:BTS=24,TRX=5:U;orZERS:BTS=24,TRX=5&6:U; meaning TRXs 5 and 6,orZERS:BTS=24,TRX=5&&9:U; meaning TRXs from 5 to 9.

28 DN9812407


Id:0900d8058062a6e9Confidential

Deleting network elements

5 Deleting network elementsFor more information on radio network administration, see Radio Network Configuration Management.

5.1 Deleting a TRX from the BTSYou can delete a TRX from a non-hopping, DFCA hopping, or an RF hopping BTS without disturbing the ongoing calls of the other TRXs of the BTS. If the BTS has an acti-vated BB or antenna hopping facility, deleting a TRX requires locking the BTS.

To save time, several TRXs can be locked with the same command.

Before you startBefore deleting a TRX, apply the forced handover procedure to minimise traffic in the TRX. As a result of the system's forced handover procedure, the TRX is barred, no new calls are established on the TRX, and the system tries to hand over the possible ongoing calls to the neighbouring TRXs. When all calls on the TRX are handed over to other cells or the time limit controlling the forced handover procedure expires, the administrative state of the TRX is updated to LOCKED.

Steps

1 Lock the TRX (ERS).ZERS:<BTS identification or BTS name>,<transceiver identification>:<administrative state>:<forced handover>;

Several TRXs can be locked at the same time with the wild card characters & and &&.

2 Delete the TRX (ERD).ZERD:<BTS identification or BTS name>,<transceiver identification>;

Further information

Example:

1. Lock the TRX with forced handover.ZERS:BTS=24,TRX=2:L:FHO;orZERS:BTS=24,TRX=2&3:L:FHO; meaning TRXs 2 and 3,orZERS:BTS=24,TRX=2&&6:L:FHO; meaning TRXs from 2 to 6.

2. Delete the TRX.ZERD:BTS=24,TRX=2;You can also delete a TRX by specifying the TRX frequency (IFREQ) in the command instead of the TRX identification.The command deletes the TRX and the related RTSLs from the BSDATA. The D-channel(s) and the speech ET-PCM time slots used by the deleted TRX can now be used for other purposes.

DN9812407 29

Radio Network Administration Deleting network elements


5.2 Deleting a BTS from the BSCBefore you startBefore deleting a BTS, apply the forced handover procedure to minimise traffic in the BTS. As a result of the system's forced handover procedure the BTS is barred, no new calls are established on the BTS, and the system tries to hand over the possible ongoing calls to the neighbouring BTSs. When all calls on the BTS have been handed over to other cells or the time limit controlling the forced handover procedure expires, the admin-istrative state of the BTS is updated to LOCKED.

Steps

1 Lock the BTS (EQS).ZEQS:<BTS identification>:<administrative state>:<forced handover>;

2 Check the state of the BTS (EEI).ZEEI:<BTS identification>;

3 Delete the BTS (EQD).ZEQD:<BTS identification>;

Further information

Example:

1. Lock the BTS with forced handover.ZEQS:BTS=24:L:FHO;

2. Wait until the BTS is in the LOCKED state. Check the state.ZEEI:BTS=24;

3. Delete the BTS.ZEQD:BTS=24;The command deletes the BTS and all related lower-level radio network object instances from the BSDATA. The D-channel and PCM circuits used by the deleted TRX can now be used for other purposes. Incoming adjacent cells are not deleted, but the system saves the adjacent cell definitions as inter-BSS adjacencies. This is useful, for example, in case of a BSS split.You can also define in a parameter that the incoming adjacency relations concerning the deleted BTS are deleted from the BSDATA. The command is then ZEQD:BTS=24:Y;

5.3 Deleting a BTS site from the BSCBefore you startBefore you can delete a BTS site, you must delete the BTS.

30 DN9812407



Deleting network elements

Steps

1 Delete the BTS.Delete the BTS as described in the procedure Deleting a BTS from the BSC.

2 Delete the BCF (EFD).ZEFD:<BCF identification>;

It is not necessary to lock the BCF before deleting.

Further information

Example:

1. Delete the BTS as described in the procedure Deleting a BTS from the BSC.2. Delete the BCF

ZEFD:2;The command deletes the BCF from the BSDATA. The D-channel (O & M signalling link) used by the deleted BCF can now be used for other purposes.

DN9812407 31

Radio Network Administration Modifying the Location Area (LA) or the Cell Identity(CI) of a BTS

Id:0900d8058079cd9dConfidential

6 Modifying the Location Area (LA) or the Cell Identity (CI) of a BTSSteps

1 Lock the BTS (EQS).ZEQS:<BTS identification or BTS name>:<administrative state>:<forced handover>;

2 Modify the LA or the CI of the BTS (EQE).ZEQE:<BTS identification>:<location area code>,<cell identity>;

3 Modify the LA or CI information to the adjacent cell lists (EAM).ZEAM:<BTS identification>::<location area code>,<cell identity>:<new location area code>,<new cell identity>;

or

ZEAM:<SEG identification>::<location area code>,<cell identity>:<new location area code>,<new cell identity>;

Note that you must give the commands for each BTS ID or SEG ID which have the modified cell defined as an adjacent cell.


Further information

Example:

1. Lock the BTS by applying the forced handover procedure.ZEQS:BTS=24:L:FHO;

2. Wait until the BTS is in the LOCKED state (check the state with the EEI command) and then modify the location area or the cell identity of the BTS.ZEQE:BTS=24:LAC=3344,CI=13000;

3. Modify the cell LA or CI information to the adjacent cell lists of the other cells in the BSC and in the other BSCs of the network which have the modified cell defined as an adjacent cell.Give the command for each BTS ID or SEG ID which have the modified cell defined as an adjacent cell:ZEAM:BTS=250::LAC=3344,CI=14000:NEWLAC=3344,NEWCI=13000;ZEAM:BTS=269::LAC=3344,CI=14000:NEWLAC=3344,NEWCI=13000;or:ZEAM:SEG=124::LAC=3344,CI=14000:NEWLAC=3344,NEWCI=13000;ZEAM:SEG=245::LAC=3344,CI=14000:NEWLAC=3344,NEWCI=13000;


32 DN9812407


Id:0900d8058079cd9dConfidential

Modifying the Location Area (LA) or the Cell Identity (CI) of a BTS

You must also modify the LA or CI parameters in the NSS. In the case of a Nokia Siemens Networks MSC, you can update the parameters via NetAct.


DN9812407 33

Radio Network Administration Modifying the BTS site type

Id:0900d805808cdac5Confidential

7 Modifying the BTS site typeWhen reconfiguring the radio network, it may become useful to modify the BTS site type.

You can modify the site type from Talk-family to UltraSite, from Talk-family to Flexi EDGE, from UltraSite to Flexi EDGE and from UltraSite or Flexi EDGE to Flexi Multiradio but not vice versa.

you can modify the Site type from Flexi Multiradio BTS, Flexi EDGE BTS, UltraSite BTS to Flexi Compact BTS without deleting the BCF object. you can modify TalkFamily, 2nd Generation, PrimeSite, MetroSite, InSite, BTSplus BTS and Flexi Multiradio 10 BTS to Flexi Compact BTS by deleting and re-creating BCF.

Modification from Flexi Compact BTS to any other site types than Flexi Multiradio 10 BTS is not possible.

If you are modifying the site to be another type the OMU link of the BCF cannot be in working state.

If You are modifying UltraSite to Flexi Multiradio, the extended cell cannot be used. If you are modifying Flexi EDGE to Flexi Multiradio, the extended cell cannot be used.

If you are modifying from UltraSite and Flexi EDGE to Flexi Multiradio extended CCCH, extended BCCH and DPTRXs cannot be configured.

g Flexi EDGE is available only when the Flexi EDGE licence state is ON or CONFIG and Flexi Multiradio is available only when the Flexi Multiradio licence state is ON or CONFIG.

The system also checks for unsupported software in connection with the modification command and rejects the command if necessary.

Steps

1 Lock the BTSs (EQS).ZEQS:<BTS identification or BTS name>:<administrative state>:<forced handover>;

2 Lock the BCF (EFS).ZEFS:<BCF identification>:<administrative state>;

3 Perform the hardware operations at the site.

4 Modify the site type (EFM).ZEFM:<BCF identification>:<site type>;

5 Check the BCF SW build (EWL).ZEWL; (The command has no parameters.)

34 DN9812407


Id:0900d805808cdac5Confidential

Modifying the BTS site type

6 Check the BCF HW database (IWX).Check and activate the hardware database according to the instructions given in the pro-cedure Adding a new BTS site under the BSC, section Activating the hardware data-base.

7 Unlock the BTSs (EQS).ZEQS:<BTS identification or BTS name>:<administrative state>;

8 Unlock the BCF (EFS).ZEFS:<BCF identification>:<administrative state>;

Further information

Example:

1. Lock the BTSs under the BCF by applying the forced handover procedure.ZEQS:BTS=24:L:FHO;

2. Lock the BCF.ZEFS:2:L;

3. Perform the hardware operations at the site.4. Modify the site type from Talk-family to UltraSite.

ZEFM:2:TYPE=P;

5. Check the BCF software build.ZEWL;If the initial software build is not correct, download the software build according to the instructions given in the procedure Adding a new BTS site under the BSC, section Downloading the software build.

6. Check and activate the hardware database according to the instructions given in the procedure Adding a new BTS site under the BSC, section Activating the hardware database.

7. Unlock the BTSs.ZEQS:BTS=24:U;

8. Unlock the BCF.ZEFS:2:U;


DN9812407 35

Radio Network Administration Activating the hopping modes of a BTS

Id:0900d8058062a6f2Confidential

8 Activating the hopping modes of a BTSYou can activate the hopping mode of a BTS by activating the following modes:

• BB hopping mode • RF hopping mode • Antenna hopping mode • DFCA hopping mode

Before you startTo activate the hopping modes you must lock the BTS.

Steps for activating the hopping modes of a BTSTo activate the hopping modes, refer the following document for instructions.

• For BB hopping mode, see Activating IFH in a BB hopping cell in Activating and Testing BSS7005: Intelligent Frequency Hopping.

• For RF hopping mode, see Activating IFH in a RF hopping cell in Activating and Testing BSS7005: Intelligent Frequency Hopping.

• For Antenna hopping mode, see Antenna Hopping in BSS11134: Antenna Hopping. Antenna hopping can be used with or without RF frequency hopping.

• For DFCA (Dynamic Frequency and Channel Allocation) hopping mode, see Acti-vating and Testing BSS11052: Dynamic Frequency and Channel Allocation.

For more information on frequency hopping, see Frequency Hopping. And for more information on radio network administration, see Radio Network Configuration Manage-ment.

36 DN9812407



Modifying the BCCH frequency

9 Modifying the BCCH frequencyWhen modifying the BCCH TRX or when frequency hopping is used on the BTS, the BTS must be locked.

t Identify the TRX with the TRX identification with frequency (IFREQ) param-eter. When identifying the TRX by frequency, the problems caused by a possible BCCH reconfiguration can be avoided. For more information on BCCH reconfiguration, see Overview of Radio Network Recovery and State Management.

Steps

1 Lock the BTS (EQS).ZEQS:<BTS identification or BTS name>:<administrative state>:<forced handover>;

2 Lock the BCCH TRX (ERS).ZERS:<BTS identification or BTS name>,<TRX identification with frequency>:<administrative state>;

3 Modify the BCCH frequency (ERM).ZERM:<BTS identification>,<TRX identification with frequency>:<frequency>;

4 Check that the frequency and the BSIC (NCC+BCC) of adjacent cells of all the BTSs remain unique (EAT).ZEAT;

The command has no parameters.

5 Unlock the TRX (ERS).ZERS:<BTS identification or BTS name>,<TRX identification with frequency>:<administrative state>;


Further information

Example:

1. Lock the BTS by applying the forced handover procedure.ZEQS:BTS=24:L:FHO;

2. Lock the BCCH TRX. Identify the TRX by the old BCCH frequency.ZERS:BTS=24,IFREQ=30:L;

DN9812407 37

Radio Network Administration Modifying the BCCH frequency


3. Modify the BCCH frequency.ZERM:BTS=24,IFREQ=30:FREQ=100;The system updates the data related to the adjacent cells within the BSC according to the new BCCH frequency.

4. Check that the frequency and the BSIC (Base Station Identity Code, NCC + BCC) of the adjacent cells of all the BTSs in the BSDATA remain unique after the BCCH frequency modification.ZEAT;

5. Unlock the BCCH TRX.ZERS:BTS=24,IFREQ=100:U;



38 DN9812407



Modifying the frequency of other than the BCCH TRX

10 Modifying the frequency of other than the BCCH TRXWhen modifying the TRX frequency, the TRX must first be locked by applying the forced handover procedure. When frequency hopping is used on the BTS, the BTS must first be locked.

t Identify the TRX with the TRX identification with frequency (IFREQ) param-eter. When identifying the TRX by frequency, the problems caused by a possible BCCH reconfiguration can be avoided. For more information on BCCH reconfiguration, see Overview of Radio Network Recovery and State Management.

Steps

1 Lock the BTS if hopping is used (EQS).ZEQS:<BTS identification or BTS name>:<administrative state>:<forced handover>;

2 Lock the TRX (ERS).ZERS:<BTS identification or BTS name>,<TRX identification with frequency>:<administrative state>:<forced handover>;

3 Modify the frequency value (ERM).ZERM:<BTS identification>,<TRX identification with frequency>:<frequency>;

4 Unlock the TRX (ERS).ZERS:<BTS identification or BTS name>,<TRX identification with frequency>:<administrative state>;

5 Unlock the BTS if hopping is used (EQS).ZEQS:<BTS identification or BTS name>:<administrative state>;

Further information

Example:

1. If hopping is used, lock the BTS by applying the forced handover procedure.ZEQS:BTS=24:L:FHO;

2. Lock the TRX. If the BTS did not have to be locked, apply the forced handover pro-cedure now. Identify the TRX by the old frequency.ZERS:BTS=24,IFREQ=45:L:FHO;orZERS:BTS=24,IFREQ=45:L; (if the BTS was locked in step 1, that is, if frequency hopping is used.)

3. Modify the TRX frequency. Identify the TRX by the old frequency.ZERM:BTS=24,IFREQ=45:FREQ=120;

DN9812407 39

Radio Network Administration Modifying the frequency of other than the BCCH TRX


4. Unlock the TRX.ZERS:BTS=24,IFREQ=120:U;

5. If hopping is used, unlock the BTS.ZEQS:BTS=24:U;


40 DN9812407


Id:0900d8058062a6fbConfidential

Modifying the O & M signalling link or its ET-PCM

11 Modifying the O & M signalling link or its ET-PCMA new O & M signalling link or its ET-PCM needs to be created or a previously created one modified when you are changing the Abis allocation. The Abis allocation is modified when, for instance, the network is being expanded. Normally a previously created unused link is not available, and you have to start from creating a new link.

Steps

1 If necessary, create and activate a new O & M signalling link.See Creating D-channels on Abis interface.

2 Modify the BCF or the TRX to use the new link.

• In all site types, modify the BCF to use the new link.ZEFM:<BCF identification>:<D-channel link set number>;

Further information

Example:

1. If necessary, create and activate a new O & M signalling link. See Creating D-channels on Abis interface.

2. Modify the BCF to use the new link. The BCF is modified in all site types. • Modify BCF 2 to use the new D-channel link set 24.

ZEFM:2:DNBR=24;


DN9812407 41

Radio Network Administration Modifying the telecom signalling link or ET-PCM of theTRX

Id:0900d8058062a6feConfidential

12 Modifying the telecom signalling link or ET-PCM of the TRXThe telecom signalling link or the TRX's ET-PCM needs to be modified when you are changing the Abis allocation. The Abis allocation is modified when, for instance, the network is being expanded.

Steps

1 Delete the TRX.See the procedure Deleting a TRX from the BTS.

2 Create the TRX again with the new D-channel or PCM.See the procedures Creating D-channels on Abis interface and Adding a new TRX to the BTS.

Further informationFor more information on radio network administration, see Radio Network Configuration Management.

42 DN9812407


Id:0900d8058078a675Confidential

Adding an external input and output text (MetroSite, Ul-traSite, Flexi EDGE and Flexi Multiradio only)

13 Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE and Flexi Multiradio only)You can define external input texts for some BTS alarms. In the MetroSite, UltraSite, Flexi EDGE and Flexi Multiradio BTSs you can define the texts at the BSC using the IO_TEXT object. For other site types, the external alarm texts are defined at the physical BTS site.

Steps

1 Check if a suitable text already exists (EFP).ZEFP;

2 If there is no suitable text, create a new text (EFE).ZEFE:<text ID>:<text string>;

3 Connect the text to the BCF.

Steps

a Connect the input parameters into BSDATA (EFX).ZEFX:<BCF identification>:<external input number>:<route>:<text ID>;

b Connect the output parameters (EFM).ZEFM:<BCF identification>:<text ID of the output from OUT1 to OUT6>;

Further information

Example:

1. Check if a suitable text already exists.ZEFP;As a default, the command outputs all texts in the BSDATA.

2. If there is no suitable text, create a new text.ZEFE:TID=10:TEXT=”SMOKE ALARM”;

3. Connect the text to the BCF. You can do this online, that is, the BCF does not have to be locked.a) Connect the input parameters into BSDATA.

ZEFX:2:INBR=3:ROU=ACT:TID=10;

b) Connect the output parameters.ZEFM:2:OUT1=10;


DN9812407 43

Radio Network Administration Locking and unlocking radio network objects


14 Locking and unlocking radio network objects

14.1 Locking radio network objectsLocking the TRXYou can lock the TRX with the command ERS.

Locking the TRX sets the TRX and its RTSLs to the administrative state LOCKED. No traffic is carried on a LOCKED TRX.

Locking the TRX is needed when modifying some TRX-specific parameters in the radio network, for instance, when modifying the frequencies, or when deleting a TRX.

To save time, several TRXs can be locked with the same command.

To avoid cutting calls in the network, lock the TRX by applying the system's forced handover procedure, controlled by the forced handover (FHO) parameter. In a forced handover, the TRX is barred, no new calls are established on the TRX and the system tries to hand over the possible ongoing calls to the other TRXs of the BTS. When all calls on the TRX have been handed over to other cells or the time limit controlling the forced handover procedure expires, the administrative state of the TRX is updated to LOCKED.

Locking the BTSYou can lock the BTS with command EQS.

Locking the BTS sets the BTS to the administrative state LOCKED. All TRXs under the BTS change to the BL-USR (blocked-user) operational state, but remain UNLOCKED if they have not been locked with their own locking command. No traffic is carried on a LOCKED BTS.

Locking the BTS is needed when modifying some BTS-specific parameters in the radio network, for instance, when modifying the location areas, cell identities, frequencies and hopping modes or when deleting the BTS.

To avoid cutting calls in the network, lock the BTS by applying the system's forced handover procedure, controlled by the forced handover (FHO) parameter. In a forced handover, the BTS is barred, no new calls are established on the BTS, and the system tries to hand over the possible ongoing calls to the neighbouring BTSs. When all calls on the BTS have been handed over to other cells or the time limit controlling the forced handover procedure expires, the administrative state of the BTS is updated to LOCKED.

Locking the BTS siteYou can lock the BTS site with the EFS command.

Locking the BTS site sets the BCF in the administrative state LOCKED. All lower-level objects under the BCF change to the BL-USR (blocked-user) operational state, but remain UNLOCKED if they have not been locked with their own locking commands. No traffic is carried on a LOCKED BCF.

Locking the BCF is rarely needed when modifying the radio network, but when modifying the BTS site type, for instance, the BCF has to be locked after the BTSs have been locked by applying forced handover. The BCF also needs to be locked before it can be deleted.

44 DN9812407



Locking and unlocking radio network objects

14.2 Unlocking radio network objectsUnlocking the TRXYou can unlock the TRX with the ERS command.

Unlocking an object causes a reset. Unlocking a higher-level object also resets all the UNLOCKED lower-level objects under it.

You can monitor the operational states of the TRXs and RTSLs with the EEI, EEL, and ERO commands. Active alarms concerning the TRXs are cancelled in the initialisation. If the TRX is still found faulty after the initialisation, the corresponding alarm indications are generated again to the BSC alarm printer, sent to NetAct, and automatic radio network recovery actions are initiated.

Possible fatal anomalies in the communication between the BTS and the BSC during the initialisation phase are indicated via the BSC alarm printer and NetAct.

You can unlock several TRXs with the same command if the BTS or BCF is in LOCKED admistrative state.

If the related BCF and BTS are in the administrative state UNLOCKED, the TRX state transition from LOCKED to UNLOCKED causes a reset of the TRX on the BTS site.

The system sets the operational states of the TRX and UNLOCKED RTSLs to BL-RST (BLOCKED - RESET). After the successful TRX reset procedure, the operational states of the TRXs and the RTSLs receive the value WORKING. The operational state value WORKING indicates that the objects have been initialised and are available for call control purposes.

Unlocking the BTSYou can unlock the BTS with the EQS command.


You can monitor the operational states of the BTS, TRXs and the RTSLs with the EEI,EEL, EQO, and ERO commands. Active alarms concerning the TRXs of the BTS are cancelled in the initialisation. If some of these TRXs are still found faulty after the initial-isation, the corresponding alarm indications are generated again to the BSC alarm printer, sent to NetAct, and automatic radio network recovery actions are initiated.

Possible fatal anomalies in the communication between the BTS and the BSC during the initialisation phase are indicated via the BSC alarm printer and NetAct.

If the related BCF is in the administrative state UNLOCKED, the BTS state transition from LOCKED to UNLOCKED causes resets on the BTS site for all UNLOCKED TRXs of the BTS.

The system sets the operational states of the BTS, UNLOCKED TRXs and the RTSLs to BL-RST (BLOCKED - RESET). After a successful BTS reset procedure, the opera-tional states of the BTSs, TRXs and RTSLs receive the value WORKING. The WORKING state value means that the objects have been initialised and are available for call control purposes.

Unlocking the BTS siteYou can unlock the BTS site with the EFS command.


DN9812407 45

Radio Network Administration Locking and unlocking radio network objects


You can monitor the operational states of the BCF, BTSs, TRXs and RTSLs with the EEI, EEL, EFO, EQO, and ERO commands. Active alarms concerning the BSS are cancelled in the initialisation. If faults still exist in the BSS after the initialisation, the cor-responding alarm indications are generated again to the BSC alarm printer, sent to NetAct, and automatic BSS radio network recovery actions are initiated.

You can also monitor various phases of BCF operations on the display of the service terminal with the service terminal extension BCF Reset Phase Monitoring. For more information, see BCF Reset Phase Monitoring.

Possible fatal anomalies in the communication between the BTS and the BSC during the initialisation phase are indicated via the BSC alarm printer.

The system downloads the default software build of the BCF to the BTS site if the build is not available in the BCF's non-volatile memory. The logical radio network configura-tion is sent to the BTS site according to the BSDATA.

The system sets the operational states of the BCF, UNLOCKED BTSs, TRXs and the RTSLs to BL-RST (BLOCKED-RESET) state. After a successful BTS site reset proce-dure, the operational states of the BCF, BTSs, TRXs and RTSLs receive the value WORKING. The WORKING state value means that the objects have been initialised and are available for call control use.

46 DN9812407



Errors in radio network configuration

15 Errors in radio network configurationThe MML program block executes main level checks for management command param-eters given by the user.

If a command can be executed, the MMI sends a management task to the BSC Radio Network Configuration Management and if the command is acceptable, the BSS Radio Network Configuration Database (BSDATA) is updated. BSS Radio Network Configura-tion Plan Database (PDDATA) is also updated if a radio network plan has been down-loaded.

For more information on File Based Plan Provisioning, see File Based Plan Provisioning System Feature Description in the GSM/EDGE BSS System Documentation.

If the given data is invalid or the system reports a discrepancy between the given data and the existing data in the database, the command is rejected and the databases are not updated. In that case, the reason for the command rejection is displayed as a response to the given MML command. When the BSDATA is first updated successfully, some of the radio network configuration data are also distributed according to the BSC's database to the call control applications of the BSC, and to the BTS site via the Abis O& M links or the telecom LAPD links.

If there are errors in distributing the modified configuration data within the BSC or from the BSC to the BTS site, the reason for the failure is displayed as a response to the given MML command. If there are errors in updating the BTS site, a corresponding error message is also generated via the local alarm printer.

If errors occur in distributing the radio network configuration data inside the BSS, the modified data remains in the BSDATA, and thus there is a discrepancy between the BSDATA and the applications in the BSC or a discrepancy between the BSDATA and the BTS site. This kind of discrepancy concerning the radio network configuration data has to be solved by the user with the help of the MMI.

The following sections describe errors that can occur during the execution of an MML command.


15.1 I/O errorsI/O errors often occur if the output terminal is out of order. The error message indicates the location of the fault.

Steps

1 Re-enter the command.The error can also be caused by a temporary disturbance, so re-entering the command may help.

DN9812407 47

Radio Network Administration Errors in radio network configuration


15.2 Errors due to inadequacies in radio network administra-tion resourcesSteps

1 Re-enter the command.The error can be caused by a momentary shortfall in resources, so re-entering the command after a while may help.

Further informationThe momentary shortfall can be caused by another simultaneous MML session in the BSC, or NetAct activity connected with the BSS radio network configuration handling, or by a simultaneous BSS radio network recovery action in the BCF. The shortfall can, however, also be of a more permanent nature. For instance, the storage area of the BSDATA has become full. For more information on the maximum capacity of the BSDATA, see Capacity of the radio network.

15.3 Errors in distributing the BSS radio network data to the BTS siteIn these error cases, the modification is made successfully to the BSDATA, but the BTS site is not updated correctly. The text

/*** BTS SITE NOT UPDATED ***/

and a DX error code can be found in the MML error message. The impact of the failure depends heavily on the given command and on the functional state of the related radio network resources.

You should never ignore these failures because the system cannot always recover from failures of this kind by itself.

Steps

1 Locate the fault.The MML error text message or the error message on the local alarm printer help in locating the fault. These error messages contain a DX error code indicating the detailed reason for the failure. The descriptions of DX error codes are in General Error Messages of System.

2 Solve the discrepancy between the BSC's database and the BTS.The most common reason for the failure of a command is that the BTS site does not acknowledge the new configuration data. The BTS site may reject the O & M message for various reasons. There may be a discrepancy between the BSC's logical database and the equipment configured on the BTS site, or the BTS site does not support the application software that are configured for the BTS according to the BSC's database. In these error cases, the discrepancy between the BSC's database and the BTS has to be solved with the BSC's MMLs. For more information on these MMLs, see BCF Hardware Database Handling (EV).

48 DN9812407



Errors in radio network configuration

3 Correct the BCF hardware database.If necessary, correct the BCF hardware database located on a BTS site with the BCF MMI. For more information, see BCF Remote MMI overview in BCF Remote MMI User's Manual. It is also possible that the configuration data cannot be relayed to the BTS site due to failures in the transmission system between the BSC and BTS site. The radio network data is sent to the BTS site via the BCF's O & M D-channel or the TRXs' telecom D-channel (System Information messages). The functional status of related D-channels must be checked (the DTI command) if the sending of an O & M message or System Information messages fails. Usually the situation is solved by resetting the BCF, BTS or TRX in question, using the BSC's lock/unlock commands.

4 Re-enter the command.The error can also be caused by a temporary disturbance on the BTS site, so re-entering the command after a while may help.

15.4 Checking errors in distributing the modified BSS radio network configuration data within the BSCIn these error cases, the modification is made successfully to the BSDATA, but the BSC's call control program block(s) is not updated correctly. The impact of the failure depends heavily on the given command and on the functional state of the related radio network resources. You should never ignore these failures because the system cannot always recover from failures of this kind by itself.

Steps

1 Locate the fault.The MML error message helps to locate the fault. The response to the MML command contains a DX error code indicating the detailed reason for the failure. The MML error message is one or several of the following:

/*** BCSU UPDATE ERROR ***//*** BCSU-xxx NOT UPDATED ***//*** DX ERROR: <nbr> ***/

/*** CBHPRB NOT UPDATED ***//*** DX ERROR: <nbr> ***/

/*** RRMPRB NOT UPDATED ***//*** DX ERROR: <nbr> ***/

/*** OMC NOT UPDATED ***//*** DX ERROR: <nbr> ***/

/*** BTS SITE NOT UPDATED ***//*** DX ERROR: <nbr> ***/

/*** ADJACENT CELLS NOT UPDATED ***//*** DX ERROR: <nbr> ***/

DN9812407 49

Radio Network Administration Errors in radio network configuration


/*** PCU NOT UPDATED ***//*** DX ERROR: <nbr> ***/

The descriptions of the DX error codes are in General Error Messages of System. When solving this kind of error situation, you should always first make sure, with the help of radio network management MML display commands, that the related radio network data in the BSC's database is valid and reasonable.

2 Solve the discrepancy between the BSC's database and other program blocks.It is possible that the call control program block rejects the modified data due to their internal data validity checkings. In these error cases, the discrepancy between the BSC's database and the other program blocks in the BSC has to be solved on the basis of the given error code in the failed MML command response.

3 Re-enter the command.Some of these errors can be caused by a temporary disturbance, so re-entering the command after a while may help.

4 Recreate the logical radio network object in question.In some cases the data in call control program blocks is corrupted in a way which is not corrected by repeating the given command. In that case, the problem can be solved by deleting the logical radio network object in question from the BSC's database and by creating it again using MML commands.

5 Check the functional state of the BCSU.It is also possible that the BCSU to be updated is not in the normal functional state (WO-EX). The computer unit(s) that is not updated successfully is indicated in the failed MML command response. Possible DX alarms of these units must be checked. In the case of BCSU(s) update problems, the failed MML command has to be given after the BCSU(s) is again in the normal functional state. These kinds of failures can also be recovered from by restarting the computer(s) listed in the failed MML command response.

50 DN9812407


Id:0900d805807fbfb4Confidential

Radio Network Configuration for Packet Abis

16 Radio Network Configuration for Packet Abis

16.1 Create ETP-PCU ConnectionPrerequisitesPacket Abis over TDM or Packet Abis over Ethernet licence is in ON or CONF statePCU SW must support packet abisPCU is not connected to ETP alreadyTotal amount of PCUs does not exceed in the ETP

1 Create ETP-PCU Connection with command ESK.ZESK:<ETP type>,<ETP group id>:<Unit>,<Unit Index>:<Plugin Unit>,<Plugin Unit Index>;

Example:

1. Create connection between given ETP and PCU.ZESK:ETPE,4:BCSU,2:PCU,3;

16.2 Create SCTP associations for OMUSIG & TRXSIG

1 Create SCTP associations (IUA) for OMUSIG and TRXSIG with command OYX.ZOYX:<SCTP association name>:<SCTP user>:<ROLE>:<UNIT IDENTIFICATION>:<SCTP parameter set>;

Example: ZOYX:SCTP2:IUA:S:BCSU,1:SS7::;

2 Configure the IP address to the association with command OYP.ZOYP:<SCTP user>:<Association indentification>:<Source address>,<source port>:<Destination address>,<destination port>;

Example: ZOYP:IUA:SCTP2:"10.125.77.70",:"10.125.76.163",22,:;

3 Configure DCSP value as “0” for the default SCTP port 9900 (IUA).ZQ8N:132::9900:0;

16.3 Create D-channels for OMUSIG & TRXSIG

1 Create the D-channels with parameters SAPI and TEI with command DWP.ZDWP:<DCHANNEL NAME>:<UNIT IDENTIFICATION>:<SAPI>:<TEI>:<ASSOCIATION NAME>:<STREAM>;

DN9812407 51

Radio Network Administration Radio Network Configuration for Packet Abis


Example: for OMUSIG:

ZDWP:OM205:BCSU,1:62,0:SCTP2,:;

for TRXSIG:

ZDWP:TR206:BCSU,1:0,4:SCTP3,:;

2 Association activation with command OYS.ZOYS:<Association name>;

D-channel activation is not needed, once the association is activated the D-channel becomes active.

16.4 Create Abis HDLC links (only in case of Packet Abis over TDM)

1 Create Abis HDLC link with command ESX.ZESX:HNBR=<HDLC link identification>,[HNAME=<HDLC link name> | <no name> def],HPCM = <external pcm>,HTSL = <start tsl>,HBAND=<HDLC link bandwith>;

Example: Create a HDLC link with size 5, starting from the PCM 30 and time slot 0.

ZESX:HNBR=21,HNAME=HDLC21,HPCM=30,HTSL=0,HBAND=5;

16.5 Create BCF

1 Create BCF with command EFC.

• for Packet Abis over EthernetZEFC:<BCF identification>,<site type>,<Abis Interface Connection Type>:<D-channel link set name>,:::::<ETP group ID>,<BTS C/U-plane IP address>,<BTS IPv4 subnet mask length for C/U-plane>,<BTS M-plane IP address>,< BTS IPv4 subnet mask length for M-plane>::;

• for Packet Abis over TDMZEFC:<BCF identification>,<site type>,<Abis Interface Connection Type>:<D-channel link set name>,:::::<ETP group ID>,<BCF HDLC ID list>,<BTS C/U-plane IP address>,<BTS IPv4 subnet mask length for C/U-plane>,<BTS M-plane IP address>,< BTS IPv4 subnet mask length for M-plane>::;

Example: for Packet Abis over Ethernet

ZEFC:231,E,2:DNAME=O312,:::::ETPGID=0,BCUIP=10.125.113.98,SMCUP=24,BMIP=10.125.113.98,SMMP=24,::;

for Packet Abis over TDM

52 DN9812407




ZEFC:231,E,2:DNAME=O312,:::::ETPGID=0,BHIDL=1,BCUIP=10.125.113.98,SMCUP=24,BMIP=10.125.113.98,SMMP=24,::;

g An additional parameter “BCF HDLC ID list - BHIDL” gets added for PA over TDM BCF creation and new Packet Abis parameters are shown to user if Packet Abis over TDM or Packet Abis over Ethernet licence is in ON or CONF state.

16.6 Open Abis HDLC links

1 Unlock HDLC links (only in case of Packet Abis over TDM).ZESS:<HDLC link identification>:<HDLC link adminstrative state>;

Example: ZESS:HNBR=22:STATE=U;

16.7 Create BTS

1 Create BTS with command EQC.ZEQC:<BCF identification>,<BTS identification>,<SEG name>,<reference BTS name>:<cell identity>,<frequency band in use>,<cell number in BTS HW>,<network colour code>,<BTS colour code>,<mobile country code>, <mobile network code>,<location area code>:<BTS hopping mode>,<underlay BTS hopping mode>,<hopping sequence number 1>,<hopping sequence number 2>:<GPRS enabled>,<packet service entity identifier>;

Example: ZEQC:BCF=20,BTS=1,SEGNAME=BIGCENTRUM020,NAME=CENTRUM1:CI=12,BAND=900,CHW=0:NCC=2,BCC=4:MCC=111,MNC=22,LAC=34567:HOP=RF,UHOP=N,HSN1=3,HSN2=1:GENA=Y,PSEI=13;

16.8 Create HOC

1 Create HOC with command EHC.ZEHC:<BTS identification>,<BTS name>,<SEG identification>,<SEG name>:<reference BTS identification>,<reference BTS name>,<reference SEG identification>,<reference SEG name>;

Example: Create handover control parameters with default values for BTS-1 when the segment usage option is off.

ZEHC:BTS=1;

DN9812407 53

Radio Network Administration Radio Network Configuration for Packet Abis


16.9 Create POC

1 Create POC with command EUC.ZEUC:<BTS identification>,<BTS name>,<SEG identification>,<SEG name>:<reference BTS identification>,<reference BTS name>,<reference SEG identification>,<reference SEG name>:<pc upper threshold dl Rx qual DHR>,<pc upper threshold ul Rx qual DHR>,<pc lower threshold dl rx qual DHR>,<pc lower threshold ul Rx qual DHR>;

Example: ZEUC:BTS=1;

g The parameters AC,DAP, PCMTSL, SIGN, BR, CL can not be given if packet abis is in use.

16.10 Create TRX

1 Create TRX with command ERC.ZERC:<BTS identification>,<transceiver identification>::<frequency>,<training sequence code>,<Abis speech circuit>:<RTSL type 0>,<RTSL type 1>,<RTSL type 2>;

Example: ZERC:BTS=1,TRX=1::FREQ=99,TSC=4,PCMTSL=21-5:DNBR=23:CH0=MBCCHC,CH1=NOTUSED,CH2=CCCHE;

g The parameters AC,DAP, PCMTSL, SIGN, BR, CL can not be given if packet abis is in use.

16.11 Attach software package

1 Attach software package to BCF with command EWA.ZEWA:<number of BCF>:<build status>:<build id>;

2 Activate the BCF with the software build with command EWV.ZEWV:<number of BCF>:<build status>;

g for more details please refer chapter 2) Adding a new BTS site under the BSC section 2.3) Downloading the software build

54 DN9812407




16.12 Activate GPRS

1 Activate GPRS with command EQV.ZEQV:<BTS identification>:<GPRS enabled>,<routing area code>:<network service entity identifier>:<DTM enabled>;

Example: ZEQV:BTS=21:GENA=Y,RAC=10,BFG=1,EXKEEP=10::EAW=MO&WE&FR,EAS=08-00, EAE=18-00:DENA=Y;

16.13 Unlock/activate created objects

1 Unlock the TRXs with command ERS.ZERS:<BTS identification or BTS name>,<transceiver identification>:<administrative state>;

g Several TRXs can be unlocked at the same time with the wild card characters & and &&, if the higher objects (BTS or BCF) are still locked.

2 Unlock the BTS with command EQS.ZEQS:<BTS identification or BTS name>:<administrative state>;

3 Activate the BCF with command EWV.ZEWV:<number of BCF>:<build status>;

4 Unlock the BCF with command EFS.ZEFS:<BCF identification>:<administrative state>;

Documents

BSS administer