Abis Autoconfiguration

Abis Autoconfiguration

dn98941771Issue 3a-0 en

# Nokia CorporationNokia Proprietary and Confidential

1 (30)

2003330Nokia BSC S10.5 ED, Vers. 2, ProductDocumentation

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

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

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

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

NOKIA logo is a registered trademark of Nokia Corporation.

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

Copyright © Nokia Corporation 2003. All rights reserved.

2 (30) # Nokia CorporationNokia Proprietary and Confidential



Contents

Contents 3

List of tables 4

List of figures 5

Summary of changes 7

1 Introduction to Abis Autoconfiguration 91.1 Overview of Abis Autoconfiguration 91.2 Optionality of Abis Autoconfiguration 101.3 MML commands and parameters used with Abis Autoconfiguration 101.4 Abis Autoconfiguration alarms 111.5 BSC preconfiguration 111.6 Autoconfiguration as an automated process 13

2 Restrictions to the Abis Autoconfiguration operating tasks 15

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

3.1 Creating a BCF to be autoconfigured 173.2 Creating a BTS 183.3 Creating a TRX to be autoconfigured 193.4 Creating an autoconfiguration pool 203.5 Deleting and outputting information on autoconfiguration pools 203.6 Expected outcome 22

4 Behaviour of Abis Autoconfiguration alarms 254.1 The autoconfiguration of a site 25

5 Troubleshooting for Abis Autoconfiguration 275.1 The BSC does not allow the BTS access procedure to continue 275.2 Autoconfiguration procedure fails and alarm 7757 is set 275.3 Testing fails 28

Glossary 29



3 (30)

Contents

List of tables




List of figures



5 (30)

List of figures

Summary of changes

Summary of changes

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

Changes made between issues 3 and 2

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.

Changes made between issues 2 and 1

Chapter 2 References

Added references to Nokia InSite and Nokia UltraSite User Manuals.

Chapter 4 Introduction to the feature Abis Autoconfiguration

Deleted the word 'new' from the subheadings.

Chapter 4.2 Parameters for MMLs

Deleted the word 'new'Added two sentences about the examples in the manual.

Other changes

Added BTS site types Nokia InSite and Nokia UltraSite, where necessary. Addeda note, that TRX tests are not performed on Nokia InSite BTSs troughout thedocument.

First issue

This is the first issue of the document Abis Autoconfiguration.



7 (30)

Summary of changes

1 Introduction to 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 the BSC feature 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

Note

TRX tests are not performed on Nokia InSite BTSs.

The Abis Autoconfiguration feature can also be used when splitting a BaseStation System (BSS).

1.1 Overview of Abis Autoconfiguration

. Restrictions to the Abis Autoconfiguration operating tasks

. Adding a new Nokia InSite base station and a TRX with AbisAutoconfiguration

. Behaviour of alarms

. Troubleshooting for Abis Autoconfiguration



9 (30)

Introduction to Abis Autoconfiguration

1.2 Optionality of Abis Autoconfiguration

Abis Autoconfiguration is an optional feature in the BSC. The feature iscontrolled with 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.

1.3 MML commands and parameters used with AbisAutoconfiguration

The Abis Autoconfiguration feature requires an MML, Abis InterfaceConfiguration MML , with which the autoconfiguration pools are handled. TheMML includes commands for creating and deleting AC pools and for displayinginformation about them. All commands related to this MML are optional.

Abis Interface Configuration (command group ES)

The commands of the ES command group are used to create autoconfigurationpools and to delete and output information on them.

For more information, see Abis Interface Configuration .

Base Control Function Handling (command group EF)

The commands of the EF command group are used when a new Nokia InSite basestation and the TRX are created with the Abis Autoconfiguration feature.

For more information, see Base Control Function Handling .

Base Transceiver Station Handling in BSC (command group EQ)

The commands of the EQ command group are used to create a BTS.

For more information, see Base Transceiver Station Handling in BSC .

Transceiver Handling (command group ER)

The commands of the ER command group are used to create the TRX.

For more information, see Transceiver Handling .




Creation of BCF (EFC)

There are two parameters for the creation of the BCF (EFC): Autoconfigure(AC) and Bit Rate of O & M link (BR) .

Creation of TRX (ERC)

There are three parameters for the creation of the TRX (ERC): Autoconfigure(AC) , Bit Rate of telecom link (BR) , and Combined O & M and telecomsignalling link(CL) .

1.4 Abis Autoconfiguration alarms

The Abis Autoconfiguration feature introduces two alarms and a notice:

. alarm 7756 (BLOCKED BECAUSE WAITING FOR ABISAUTOCONFIGURATION)

. alarm 7757 (ABIS AUTOCONFIGURATION FAILED)

. notice 7758 (ABIS AUTOCONFIGURATION COMPLETED).

For more information, see Behaviour of alarms .

1.5 BSC preconfiguration

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

To preconfigure 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.



11 (30)


For more information, see Adding a new Nokia InSite base station and aTRX with Abis Autoconfiguration .

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 to goautomatically alive to the network, you must unlock the radio networkobjects before the autoconfiguration starts.

4. Create the transmission objects related to the Nokia InSite BTS. The Q1addresses are saved to the BSC (Note that this is not in the scope of thismanual).

For more information on the creation, see Adding a new Nokia InSite basestation and a TRX with Abis Autoconfiguration .

5. If necessary, install, create, and connect the Abis ET unit, whichterminates the PCM line in the BSC. The physical installation of the ETunits requires that the BSC MML is used. (Note that this is not in the scopeof this manual).

For more information on the creation, see the task Creating anautoconfiguration pool or Abis Interface Configuration or BSSIntegration .

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/BCSUs.

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 non-commissioned base stations and the BSC. The BSC isready to serve the accessing BTS after the access channel has been created.

For more information on the creation, see .Adding a new Nokia InSite basestation and a TRX with Abis Autoconfiguration

Note

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




1.6 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 non-commissioned BTS (Note thatthis is 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 (BCF specific).



13 (30)


Note

TRX tests are not performed on Nokia InSite BTSs.

If all time slots of the pool (except for the access channel) are allocated, the BSCfinally 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 the NMS and it is saved in the alarm history as well.The tests can also be repeated with the BSC's MML. For more information on theAbis loop test, see Scheduled Radio Network Test Handling and Single RadioNetwork Test Handling .




2 Restrictions to the AbisAutoconfiguration operating 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, this parametercannot be used.

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

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

TRX creation

If the BCF is waiting for Abis autoconfiguration, you can create the TRX under itonly 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 (the parameterautoconfiguration value is Y).

You cannot give the Abis speech circuit parameter if the TRX is created to beautoconfigured.

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

The name of the D-channel telecom link set must be unique. A new telecomsignalling link with the given name is created during the TRX creation.



15 (30)

Restrictions to the Abis Autoconfiguration operating tasks

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 to beautoconfigured.

You can give the combi link (CL) parameter only if the parameter transceiveridentification value is 1 and the TRX is created to be autoconfigured. If the combilink option (combined O & M and Telecon signalling channel) is used, the bit ratevalues of the O & M link and the telecom link of TRX-1 must be identical.




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

3.1 Creating a BCF to be autoconfigured

As a default, the operational state of the new BCF is 'Locked' (L). Since youcannot create the TRXs if the operational state of the BSC is 'Unlocked', you mustfirst create the entire BCF site (BCF, BTS, and the TRXs) before you can changethe state of the BCF to 'Unlocked'.

Steps

1. Create a BCF and a Nokia InSite (EFC)

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 is given.

Note

If you want the new site to become alive automatically 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 the autoconfigurationis completed, alarm 7756 (BLOCKED BECAUSE WAITING FOR ABISAUTOCONFIGURATION) is set.



17 (30)

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

For more information on BCF creation, see Base Control FunctionHandling

Example 1. Creating a BCF to be autoconfigured

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

3.2 Creating a BTS

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

This feature does not change the usage of the EQC command.

Steps

1. Create a BTS (EQC ).

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 the AbisAutoconfiguration feature is not in any way related to these parameters. 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 .

For more information on BTS creation, see Base Transceiver StationHandling in BSC .

Example 2. Creating a BTS

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




3.3 Creating a TRX to be autoconfigured

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

Steps

1. Create TRX-1 (ERC )

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

Note

If you want the new TRX to become alive automatically after autoconfiguration,unlock the TRX by giving the autoconfiguration request command with the BTSManager before the installation engineer starts the autoconfiguration at the site.

Note

When creating an InSite TRX to be autoconfigured, it is recommended that theCompressed Abis time slot allocation solution be used. Use the SIGN parameterin the ERC command. This solution is particularly advisable in low traffic areasin the case of BTSs with one TRX, where it is essential to have coverage. Formore information, see Nokia BSS transmission configuration .

For more information on TRX creation, see Transceiver Handling .

Example 3. Creating a TRX to be autoconfigured

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



19 (30)


3.4 Creating an autoconfiguration pool

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

Steps

1. Create an AC pool (ESC )

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 can not be created on a timeslot which is reserved for existing Dchannel links.

For more information on creating, deleting and interrogatingautoconfiguration pools, see Abis Interface Configuration .

Example 4. Creating an autoconfiguration pool

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

3.5 Deleting and outputting information onautoconfiguration pools

Steps

1. Delete the autoconfiguration pool




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

2. Display information on autoconfiguration pool

To display information on autoconfiguration pools, use the ESOcommand. 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.

Example 5. Displaying information on autoconfiguration pools

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;

Note

For more information on Abis Interface Configuration MML, see Abis InterfaceConfiguration .



21 (30)


3.6 Expected outcome

The BSC is ready to serve the new accessing BTS after the operating tasksCreating a BCF to be autoconfigured , Creating a BTS , Creating a TRX to beautoconfigured and Creating an autoconfiguration pool have been completed.The Installation Engineer uses the BTS Manager to give the system informationrelevant for the Abis autoconfiguration. The new base station starts theautoconfiguration 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.

Steps

1.

The BTS or hub node looks for the access channel and finds it.

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

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.



23 (30)


A new BTS is ready for traffic.




4 Behaviour of Abis Autoconfigurationalarms

4.1 The autoconfiguration of a site

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



25 (30)

Behaviour of Abis Autoconfiguration alarms

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 during 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 on.

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

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 on as long as the autoconfigurationhas succeeded or the BCF is deleted.




5 Troubleshooting for AbisAutoconfiguration

5.1 The BSC does not allow the BTS access procedureto continue

If the BSC has some other active access sequence, for example, some other NokiaInSite is accessing at the same time, the BSC takes 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 constantly until it is served.

5.2 Autoconfiguration procedure fails and alarm 7757is 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.



27 (30)

Troubleshooting for Abis Autoconfiguration

. 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 cleared the reason for the error.

To create the Abis autoconfiguration pool again:

1. Interrogate the Abis autoconfiguration pool to check it has been created.

Use the MML command ZESO (interrogation)

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

Use the MML command ZESC (creation).

3. Start the autoconfiguration on the BTS site.

5.3 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 and Single Radio Network TestHandling .

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.




Glossary

Access Channel The generic Access Channel is used for communication between non-commissioned base stations and a BSC. From the BSC point of view the AccessChannel is a 64 kbit LAPD channel located in a BCSU, with a special SAPI value(SAPI = 61, TEI = 0).

AC pool Autoconfiguration pool is a block of time slots used for autoconfiguration. It isdefined in the BSC and is routed through the transmission network. The AC poolis used for free allocation of transmission capacity.

BCF Base Control Function is a functional unit in the base station. Its main tasks arebase station operation and maintenance functions, that is, software loading, unitconfiguration, and alarm handling. The BCF communicates with the BSC via theAbis O & M interface. The BCF is also an object in the BSDATA (BSS RadioNetwork Configuration Database).

BCSU Base Station Controller Signalling Unit performs those BSC functions that arehighly dependent on the volume of traffic. It consists of two parts correspondingto the A and Abis interfaces.

BTS Base Transceiver Station (cell) is a network element that provides the transceiverfunctions of the BSS. One BTS can consist of one or more transceivers (TRX).The BTS is also an object in the BSDATA.

BCF ID Each BCF under the same BSC has an unique number from 1 up to the maximumnumber of BCFs. The number comes from the radio network plan.

BSC ID The BSC id is the BSC's C-number. It is a unique identification given by thelogistics.

BSDATA BSS Radio Network Configuration Database (BSDATA) contains the permanentconfiguration data and the control parameters of the BSS radio network. Itprovides other processes with the means of updating and inquiring permanentdata stored in the BSC and specific to the radio network.

Circuit A digital circuit is used for transferring PCM signals or other digital signals, thestructure of which complies with the frame structure of a standardized PCMgroup. A circuit is identified with PCM, time slot and bits in the time slot.

BTS Manager A BTS Manager is a software tool for installation engineer at a BTS site.

ET The Exchange Terminal is a unit for supervising electrical synchronisation andadaptation of an external 1.5 or 2 Mbit/s link.

ET-PCM The GSM speech channels are submultiplexed in the ET-PCM, that is, there areseveral channels in one time slot.



29 (30)

Glossary

LAPD Link Access Protocol for D-channel(s). It is also used for Access Channel

MMI Man Machine Interface (MMI) is a system consisting of software and peripheraldevices. The operator uses it to perform operation and maintenance functions inthe exchange.

MML Man Machine Language is a text based language with a standardised structure,designed to facilitate direct user control of a system.

NMS Network Management System is a system for the management of cellularswitches, base station controllers, and related transmission systems. NokiaNetAct is used to operate the BSC.

Nokia Q1 The Nokia Q1 interface is used to connect exchanges to network elements whichsupport only the network element function, not the mediation function. Theservice channel between the BSC and transmission equipment can be regarded asa Q1 interface.

O & M signallinglink

O & M signalling link is one type of LAPD signalling link. O & M signalling linkis used for downloading BCF software, monitoring and controlling purposes.

PCM Pulse Code Modulation is a process in which a signal is sampled, and eachsample is quantized independently of other samples and converted by encoding toa digital signal.

Q3 The Q3 interface is an object-based management interface between theOperations and Maintenance Centre (OMC) and the network elements (NEs) in atelecommunications management network (TMN). The OMC and the NEscommunicate with each other through this interface.

TSL A time slot is a cyclic interval that can be recognized and defined uniquely.

TRX A transceiver is a base station's unit, which is a combination of transmitting andreceiving equipment. The transceiver transmits and receives a radio carrier andhandles baseband and frame functions. The transceiver is also an object in theBSDATA. The TRX object collection contains transceiver-specific parameters.

Telecom signallinglink

Telecom signalling link is a telecom signalling channel from the BSC to theTRXs. Telecom signalling is used for carrying signalling information betweenMSC to MS, BSC to MS and BSC to BTS. Telecom signalling is used forlocation updates, call control, handover, paging, uplink/downlink measurementresults/controls, etc.




Abis Autoconfiguration

Documents

Transcript of Abis Autoconfiguration