Abis Autoconfiguration

Abis Autoconfiguration

DN98941771Issue 5-0 en

# Nokia Corporation 1 (23)

BSC3119Nokia BSC/TCSM, Rel. S12, ProductDocumentation, v.1

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is intended for the useof Nokia's customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be reproduced or transmitted in any form or means without theprior written permission of Nokia. The document has been prepared to be used by professionaland properly trained personnel, and the customer assumes full responsibility when using it.Nokia welcomes customer comments as part of the process of continuous development andimprovement of the documentation.

The information or statements given in this document 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 document areadequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the document.

Nokia's liability for any errors in the document is limited to the documentary correction of errors.NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENTOR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARYLOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright according tothe applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

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

Copyright © Nokia Corporation 2007. All rights reserved.

2 (23) # Nokia Corporation DN98941771Issue 5-0 en


Contents

Contents 3

List of tables 4

List of figures 5

Summary of changes 7

1 Overview of Abis Autoconfiguration 91.1 BSC pre-configuration for Abis Autoconfiguration 101.2 Autoconfiguration as an automated process 111.3 Restrictions to the Abis Autoconfiguration operating tasks 131.4 Behaviour of Abis Autoconfiguration alarms 14

2 Adding a new Nokia InSite base station and a TRX with AbisAutoconfiguration 17



Contents

List of tables



List of figures



List of figures



Summary of changes

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

Changes made between issues 5 and 4

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

The instructions for adding a new Nokia InSite base station and a TRX with AbisAutoconfiguration have been moved here from BSS Integration.


The document has been revised throughout to comply with the latestdocumentation standards. The instructions for adding a new Nokia InSite basestation and a TRX with Abis Autoconfiguration have been moved to BSSIntegration.

No changes have been made in the document due to new features.


UltraSite and MetroSite do not support the ABIS Autoconfiguration feature.Therefore these site type references have been removed. MetroSite examples arereplaced with InSite examples

Section Adding an extension TRX has been removed.

Other changes

Structural changes made to the document for S10.



Summary of changes



1 Overview of Abis Autoconfiguration

Abis autoconfiguration refers to the simplification and automation of BTScommissioning and integration. The autoconfiguration solution providesoperators with efficient and straightforward procedures to automatically configurethe transmission while expanding and maintaining the network. The Nokia InSiteBase Station supports Abis Autoconfiguration.

Autoconfiguration is an alternative for end-to-end transmission capacityallocation in a network that contains Nokia InSite BTSs. Autoconfigurationaddresses the circuit allocation of the BSC's 1.5 or 2 Mbit/s (ET) unit, theconfiguration of the base station's integrated transmission unit, and thedownloading of the base station parameters. Abis loop tests are performed toverify that the commissioning has been successful and that the equipmentoperates correctly.

Abis Autoconfiguration requires an MML, Abis Interface Configuration MML(ES), with which the autoconfiguration pools are handled. The MML includescommands for creating and deleting AC pools and for displaying informationabout them. All commands related to this MML are optional.

Note

TRX tests are not performed on Nokia InSite BTSs.

Abis Autoconfiguration can also be used when splitting a Base Station System(BSS).

Optionality of Abis Autoconfiguration

Abis Autoconfiguration is optional in the BSC. The functionality is controlledwith one PRFILE parameter, ABIS_AUTOCONF_IN_USE, in class 2(SYSTEM_FUNCT_CONFIGUR). The operator cannot change the parametervalue.

If autoconfiguration is not allowed, the operator cannot use the pool managementMMI or create radio network objects for autoconfiguration.



Overview of Abis Autoconfiguration

More information on Abis Autoconfiguration

For Abis autoconfiguration instructions, see Adding a new Nokia InSite basestation and a TRX with Abis Autoconfiguration.

1.1 BSC pre-configuration for Abis Autoconfiguration

Ideally, the BSC is configured using Nokia NetAct and therefore the user at theBSC site does not need to carry out any configuration tasks. The BSC can also beconfigured with the MML.

To pre-configure the BSC with the MML, follow these steps:

1. Make sure that the BSC is operational or under commissioning.

2. Create the radio network objects and the O & M and TRX signalling linksinto the BSC's radio network database without predefined Abis circuitallocation, using either:. Nokia NetAct. BSC MML commands

When you use BSC MML commands, you create the signalling linkswithout predefined Abis circuit allocation by giving the needed parametersduring the BCF/TRX creation. In Nokia NetAct, the creation of thesignalling links (TSL values 0-0) is separated from the BCF/TRX creation.

For more information, see section Creating a base station and initialisingits parameters of BSS Integration.

3. As a default, the radio network objects are in locked state in the BSC afterthe creation. Therefore the BSC does not activate the BTS after theautoconfiguration has been completed. If you want the BTS toautomatically be operative in the network, you must unlock the radionetwork objects before the autoconfiguration starts.

4. Create the transmission objects related to the Nokia InSite BTS. The Q1addresses are saved to the BSC.

For more information on the creation, see section Creating a base stationand initialising its parameters of BSS Integration.

5. If necessary, install, create, and connect the Abis ET unit, which terminatesthe PCM line in the BSC. The physical installation of the ET units requiresthat the BSC MML is used. (Note that this is not in the scope of thismanual).

For more information on the creation, see Abis Interface Configuration orBSS Integration.



6. Create the autoconfiguration pool into the ET-PCM using either NokiaNetAct (Q3) or the BSC MML. The size of the pool can be 3 - 31 TSLs(ETSI) or 3 - 24 TSLs (ANSI). You can create one or several pools to thesame PCM. There is a limitation, controlled by the system, which allowsyou to create a maximum of four autoconfiguration pools/BCSU.

A pool is created as a continuous block of 64 kbit time slots. It cannot bedivided into two PCMs. The BSC reserves the circuits so that they cannotbe used for other purposes without deleting the pool first. The BSCautomatically creates and activates a 64 kbit access channel into the lasttime slot of the AC pool. The access channel is used for communicationbetween the uncommissioned base stations and the BSC. The BSC is readyto serve the accessing BTS after the access channel has been created.

For more information on the creation, see the step Create anautoconfiguration pool of BSS Integration.

Note

In GSM Office there can be only one autoconfiguration pool in one ET portand the pool's last time slot (access channel) has to be the last time slot of theET port.

1.2 Autoconfiguration as an automated process

The following steps are executed during installation and commissioning:

1. The Installation Engineer installs the new Nokia InSite, connects thetransmission link, and powers-up the uncommissioned BTS (Note that thisis not in the scope of this manual). For more information, see theappropriate InSite user manual or Overview of Nokia Autoconfiguration inGSM Office.

2. The BTS performs autodetection to find out the number and type of itsunits.

3. The Installation Engineer starts Nokia Autoconfiguration in the GSMOffice by giving the autoconfiguration request command with the InSiteBTS Manager that is running on a laptop PC. The Installation Engineerprovides the required configuration parameters and launches NokiaAutoconfiguration.

4. The new base station starts the autoconfiguration process either




. by searching for capacity directly from the BSC (port scan) througha local transmission unit, or

. by connecting to a hub transmission node which has already scannedthe AC pool information.

The hub transmission node acts as an AC pool server for anyautoconfiguring client BTS. When the client BTS connects to the hubtransmission node, the hub node (or several nodes) is used to create thetransmission circuit between the accessing BTS and the BSC's ET port(s).The capacity for the circuit is reserved from the AC pool.

5. The BTS startup continues with a O & M signalling link activation. TheBSC updates the allocated Abis circuits to the radio network database andLAPD channel definition files in the memory and on the hard disks. TheBSC also informs Nokia NetAct about the allocated circuits.

6. The success of the autoconfiguration process is tested automatically. TheBTS requests the BSC to perform Abis loop tests. An Abis loop test isexecuted for each time slot, one after another.

7. The 7758 (ABIS AUTOCONFIGURATION COMPLETED) noticeincluding the testing status is set. The notice is BCF specific.

Note

TRX tests are not performed on Nokia InSite BTSs.

If all time slots of the pool (except for the access channel) are allocated, theBSC finally automatically deletes the pool (autodelete).

Note

BTS testing is not done if the autoconfiguration procedure fails.

The test results can be read from the report history or the report printer of theBSC. The 7758 (ABIS AUTOCONFIGURATION COMPLETED) notice can beseen in both the BSC and Nokia NetAct and it is saved in the alarm history aswell. The tests can also be repeated with the BSC's MML. For more informationon the Abis loop test, see Scheduled Radio Network Test Handling (UC) andSingle Radio Network Test Handling (UB).



1.3 Restrictions to the Abis Autoconfigurationoperating tasks

There are certain restrictions related to the task-based instructions:

BCF creation

. The autoconfigure parameter (AC) can only be used with Nokia InSite.

. The bit rate parameter (BR) is obligatory if the BCF is created to beautoconfigured. If the BCF is not created to be autoconfigured, thisparameter cannot be used.

. You cannot give the D-channel link set number (DNBR) parameter, if theBCF is created to be autoconfigured.

. The D-channel link set name must be unique. A new O &M signalling linkwith the given name is created during the BCF creation.

TRX creation

. If the BCF is waiting for Abis autoconfiguration, you can only create theTRX under it to be autoconfigured.

. You cannot give the parameter value ISDN to the TRX transmission type(TRA) parameter, if the TRX is created to be autoconfigured (theparameter autoconfiguration value is Y).

. You cannot give the Abis speech circuit parameter if the TRX is created tobe autoconfigured.

. You cannot give the D-channel telecom link set number (DNBR)parameter if the TRX is created to be autoconfigured.

. The name of the D-channel telecom link set must be unique. A newtelecom signalling link with the given name is created during the TRXcreation.

. The bit rate (BR) parameter is obligatory if the TRX is created to beautoconfigured. You cannot give this parameter if the TRX is not created tobe autoconfigured.

. You can give the combi link (CL) parameter only if the parametertransceiver identification value is 1 and the TRX is created to beautoconfigured. If the combi link option (combined O & M and Telecomsignalling channel) is used, the bit rate values of the O & M link and thetelecom link of TRX-1 must be identical.




1.4 Behaviour of Abis Autoconfiguration alarms

Initial stage, all objects created to be autoconfigured:

BCF L BL-USR

BTS L BL-USR

TRX L BL-USR

No active alarms.

Unlocking the objects (TRX first, then BTS, then BCF):

BCF U BL-WAC

BTS U BL-WAC

TRX U BL-WAC

When the BCF is unlocked, the BSC sets the alarm 7756 (BLOCKEDBECAUSE WAITING FOR ABIS AUTOCONFIGURATION) (BCF specific).

Locking the objects that are waiting for autoconfiguration:

BCF L BL-USR

BTS L BL-USR

TRX L BL-USR

When the BCF is locked, the BSC cancels the alarm 7756 (BLOCKEDBECAUSE WAITING FOR ABIS AUTOCONFIGURATION) (BCF specific).

The autoconfiguration is done and it has been successful to TRX (unlockedobjects before AC):

BCF U WO

BTS U WO

TRX U WO

When the autoconfiguration has successfully been finished, the BSC cancels theBCF-specific alarm 7756 (BLOCKED BECAUSE WAITING FOR ABISAUTOCONFIGURATION).

The autoconfiguration is done and it is unsuccessful:

BCF U BL-WAC

BTS U BL-WAC

TRX U BL-WAC

If the BSC does not receive the message BTS_OMU_STARTED within the timelimit, the BSC cancels the autoconfiguration procedure and sets the 7757 (ABISAUTOCONFIGURATION FAILED) alarm for that BCF. In addition, the 7756(BLOCKED BECAUSE WAITING FOR ABIS AUTOCONFIGURATION)alarm is still active.



If the objects have been locked, the 7756 (BLOCKED BECAUSE WAITINGFOR ABIS AUTOCONFIGURATION) alarm is not active.

Locking the objects after unsuccessful autoconfiguration:

BCF L BL-USR

BTS L BL-USR

TRX L BL-USR

When the BCF is locked, the BSC cancels the 7756 (BLOCKED BECAUSEWAITING FOR ABIS AUTOCONFIGURATION) alarm. The 7757 (ABISAUTOCONFIGURATION FAILED) alarm is not cancelled. The 7757 (ABISAUTOCONFIGURATION FAILED) alarm is active as long as theautoconfiguration has succeeded or the BCF is deleted.






2 Adding a new Nokia InSite base stationand a TRX with Abis Autoconfiguration

For an overvierw, see Overview of Abis Autoconfiguration.

Steps

1. Create a BCF to be autoconfigured (EFC).

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

EFC:<identification of BCF>,<site type>:<d-channellink set name>,<autoconfigure>,<bit rate>;

Note

No similar D-channel link set name can be created before this command isgiven.

Note

If you want the new site to automatically be operative after theautoconfiguration, unlock the BCF by giving the autoconfiguration requestcommand with the BTS Manager before the Installation Engineer starts theautoconfiguration at the site. If you unlock the BCF before theautoconfiguration is completed, alarm 7756 (BLOCKED BECAUSEWAITING FOR ABIS AUTOCONFIGURATION) is set.

2. Create a BTS (EQC).

As a default, the administrative state of the new BTS is 'Locked' (L).



Adding a new Nokia InSite base station and a TRX with Abis Autoconfiguration

Abis Autoconfiguration does not change the usage of the EQC command.

EQC:<identification of BCF>,<identification of BTS>,<BTS name>:<cell identity>,<frequency band in use>:<network colour code>,<BTS colour code>:<mobilecountry code>,<mobile network code>,<location areacode>;

Note

The BTS-specific parameters power control and handover controlmust be created before you can unlock the BTS, although AbisAutoconfiguration is not related to these parameters in any way. Thecommands used to create the parameters are: EUC (power control, POC) andEHC (handover control, HOC). For more information, see Handover ControlParameter Handling and Power Control Parameter Handling.

3. Create a TRX to be autoconfigured (ERC).

As default, the administrative state of the created new TRX is 'Locked' (L).

ERC:<identification of the BTS>,<identification ofthe TRX>:<autoconfiguration>:<frequency>,<trainingsequence code>:<d-channel telecom link set name>:<bitrate>,<combi link>,<RTSL type>;

Note

If you want the new TRX to automatically be operative afterautoconfiguration, unlock the TRX by giving the autoconfiguration requestcommand with the BTS Manager before the installation engineer starts theautoconfiguration at the site.

Note

When creating an InSite TRX to be autoconfigured, it is recommended thatthe Compressed Abis time slot allocation solution be used. Use the SIGNparameter in the ERC command. This solution is particularly advisable in lowtraffic areas in the case of BTSs with one TRX, where it is essential to havecoverage. For more information, see Nokia BSS transmission configuration.



4. Create an autoconfiguration pool (ESC).

The Abis interface ET-PCM must be created before the autoconfiguration(AC) pool. For more information, see Abis Interface Configuration (ES) orBSS Integration.

ZESC:<circuit(s)>;

Note

For GSM Office the AC Pool must extend to TSL 31 or TSL 24 (E1 or T1,respectively). With the GSM Office solution, you can only create one AC pool/ ET and the AC pool's last timeslot has to be the last timeslot of the ET-PCM.

Note

An AC Pool cannot be created on a timeslot which is reserved for existing Dchannel links.

To delete an autoconfiguration pool, use the ESD command. Enter theparameter circuit or pool id.

5. Display information on autoconfiguration pool (ESO).

To display information on autoconfiguration pools, use the ESO command.Enter the parameter circuit, pool id or PCM number

The following information is displayed for each pool:. pool id. PCM and time slot to identify the location of the pool. number of free time slots in the pool (access channel is reserved). name, number, and time slot of the access channel. unit type and index of the unit controlling the access channel.

Further information

Example

ZEFC:12,I:DNAME=OMU12,AC=Y,BR=64;




ZEQC:BCF=12,BTS=12,NAME=CENTRUM1:CI=33,BAND=900:NCC=3,BCC=4:MCC=111,MNC=02,LAC=3344;

ERC:BTS=12,TRX=1:AC=Y,:FREQ=23,TSC=0:DNAME=AC1:BR=64,CL=Y,CH0=MBCCHC;

ZESC:CRCT=32–1&&–31;

Examples of the ESO command:

ZESO:CRCT=72-9;

ZESO:CRCT=72-9&&-20;

ZESO:ID=1;

ZESO:ID=1&&5;

ZESO:PCM=72&75;

ZESO;

Expected outcome

The BSC is ready to serve the new accessing BTS after the steps Create a BCF tobe autoconfigured,Create a BTS,Create a TRX to be autoconfigured and Createan autoconfiguration pool have been completed. The Installation Engineer usesthe BTS Manager to give the system information relevant for the Abisautoconfiguration. The new base station starts the autoconfiguration procedure.

From the BSC point of view a successful Abis autoconfiguration procedure canbe explained as follows. It is assumed here that the site has already been'Unlocked' before step 1 and that the alarm 7756 BLOCKED BECAUSEWAITING FOR ABIS AUTOCONFIGURATION is set for the BCF.

1. The BTS or hub transmission node looks for the access channel and findsit.

2. The BSC sends a report about the autoconfiguration pool sizes to the hubnode or the BTS.

3. The BTS asks the BSC to allocate traffic and signalling circuits for theTRX

4. The BSC allocates the circuits for the O & M link.

5. The BSC activates the O & M link.



6. The BSC allocates the circuits for telecom link(s).

7. The BSC activates the telecom link(s).

8. The BSC allocates the speech circuits of the TRXs.

9. Information about allocated circuits is sent to the BTS.

10. The BTS continues its boot up from the commission state to the OMUSIGlink establishment waiting state.

11. Alarm 7756 (BLOCKED BECAUSE WAITING FOR ABISAUTOCONFIGURATION) is cancelled for the BCF.

12. Possible BTS software downloads are done.

13. Configuration data is sent to the BTS.

14. Abis loop tests are done.

15. State changed information is sent from the BTS to the BSC (TRX specific).

16. The BTS informs the BSC about the completion of the configuring phase.

17. The operational state of the TRX is changed to working (WO) if it wasunlocked in the beginning.

18. A new BTS is ready for traffic.

Unexpected outcome

The BSC does not allow the BTS access procedure to continue

If the BSC has some other active access sequence, for example, some other NokiaInSite is accessing at the same time, the BSC puts the request to a queue. If theBSC cannot serve the queuing Nokia InSite during the defined period of time, itdiscards the request. The BTS tries to access the BSC constantly until it is served.

Unexpected outcome

Autoconfiguration procedure fails and alarm 7757 is set

The alarm printout gives an error code which should be checked. The followinglist gives possible reasons for a failure:

. The pool is not found.

. The BSC's BSC ID is wrong.

. The BCF has not been created in the BSC.

. The BCF is not waiting for the autoconfiguration.




. The TRX is not waiting for the autoconfiguration.

. The TRX has already been autoconfigured.

. There are no TRXs to autoconfigure.

. Links cannot be combined.

. Allocation cannot be optimised.

. There is no room for circuits in the pool.

. The BCF cannot be reserved for autoconfiguration.

. Modifying the OMUSIG has failed.

. Activating the OMUSIG has failed.

. Modifying the TRXSIG has failed.

. Activating the TRXSIG has failed.

. The traffic channel allocation has failed.

. The message from the BTS is missing.

. The BTS has interrupted the scenario.

These are general level error codes. For more details, see the computer log of theMarker and Cellular management Unit (MCMU) and act according to the morespecific error data, for example, link number, trx_id, bcf_id, incorrect BSC's C-number, pool id or incorrect access channel id. Try the Abis autoconfigurationagain after you have found and solved the reason behind the error.

To create the Abis autoconfiguration pool again:

1. Check if the Abis autoconfiguration pool has been created.

Use the MML command ZESO (interrogation)

2. Create the Abis Autoconfiguration pool if it does not exist yet.

Use the MML command ZESC (creation).

3. Start the autoconfiguration of the BTS site.

Unexpected outcome

Testing fails



The automated testing is performed in the BSC during the Abis autoconfigurationprocedure. The testing can also be done separately without any connection to theAbis autoconfiguration procedures. For more information on Abis loop tests, seeScheduled Radio Network Test Handling (UC) and Single Radio Network TestHandling (UB).

The failure of testing does not affect Abis autoconfiguration as such. Althoughthe testing might fail, the BSC regards the Abis allocation as successful and doesnot cancel it if the BTS sends a message telling that the BTS has been started viathe O & M link that was just allocated.




Documents

Abis Autoconfiguration