Building and Extending EDGE

Building and Extending EDGECoverage

DN00275994 © Nokia Corporation 1 (46)Issue 4-0 en Nokia Proprietary and Confidential

Building and Extending EDGE Coverage

The information in this documentation is subject to change without notice and describes onlythe product defined in the introduction of this documentation. This documentation is intendedfor the use of Nokia's customers only for the purposes of the agreement under which thedocumentation is submitted, and no part of it may be reproduced or transmitted in any form ormeans without the prior written permission of Nokia. The documentation has been prepared tobe used by professional and properly trained personnel, and the customer assumes fullresponsibility when using it. Nokia welcomes customer comments as part of the process ofcontinuous 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 cannot be considered bindingbut shall be defined in the agreement made between Nokia and the customer. However, Nokiahas made all reasonable efforts to ensure that the instructions contained in the documentationare adequate 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 orthe information in it.

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

NOKIA logo is a registered trademark of Nokia Corporation.

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

Copyright © Nokia Corporation 2006. All rights reserved.

2 (46) © Nokia Corporation DN00275994Nokia Proprietary and Confidential Issue 4-0en

Contents

Contents 3

List of figures 5

1 About this document 71.1 NetAct compatibility and capacity information 71.2 Prerequisites 7

2 EDGE features and Nokia NetAct support for EDGE 92.1 Dynamic Abis Pool 92.2 Multi-BCF in the EDGE capable radio network 102.3 Overview of planning EDGE mobilisation 10

3 Enabling EDGE in the Nokia BSS 133.1 Preconditions for the operation 133.1.1 Preconditions in the Nokia BSS 133.1.2 Preconditions in Nokia NetAct 133.2 Building EDGE Coverage 143.2.1 Creating new MetroSites, UltraSites or FlexiEDGE 143.2.2 Adding EDGE TRXs to MetroSites, UltraSites or FlexiEDGE 143.2.3 Creating the Dynamic Abis Pool 143.2.4 Creating Multi-BCF sites 15

4 Planning EDGE mobilisation 174.1 Planning EDGE mobilisation using an external planning tool 174.1.1 Overview of this procedure 174.1.2 Uploading BSS data from NetAct 184.1.3 Exporting actual BSS data to XML or CSV file(s) 194.1.4 Importing XML or CSV file(s) 194.1.5 Creating GPRS disabling plan 194.1.6 Creating DAP creation plan 194.1.7 Creating EDGE activation plan 204.1.8 Creating GPRS enabling plan 204.1.9 Exporting the plans 204.1.10 Importing the plans 214.1.11 Verifying the plans 214.2 Planning EDGE mobilisation using CM Editor 224.2.1 Overview of this procedure 224.2.2 Uploading BSS data from NetAct 234.2.3 Exporting actual BSS data to XML file(s) 234.2.4 Creating GPRS disabling plan 234.2.5 Creating DAP creation plan 234.2.6 Creating EDGE activation plan 244.2.7 Creating GPRS enabling plan 254.2.8 Verifying the plans 25

5 Implementing EDGE mobilisation 275.1 Preconditions 27



5.2 Overview of the mobilisation procedure 275.3 Activating maintenance mode 285.4 Provisioning GPRS disabling plan to network 295.5 Provisioning DAP creation plan to network 295.6 Provisioning EDGE activation plan to network 315.7 Provisioning GPRS enabling plan to network 315.8 Verifying actual configuration 325.9 Turning off maintenance mode 33

6 EDGE mobilisation rollback 356.1 Rollback for entire network 35

7 Verifying network performance 377.1 Dynamic Abis report (280) 387.2 EGPRS KPI report (226) 387.3 EGPRS RLC statistics report (275) 387.4 WCDMA adjacencies having high HO failure ratio report (159) 397.5 Common BCCH, Multi-BCF HO (151) 397.6 Other common BCCH reports 39

8 Rehosting EDGE BTSs 41

9 Where to find more information 43

Index 45


List of figures

Figure 1. Nokia NetAct tool set for planning, building, and optimising EDGEcoverage 11

Figure 2. Planning EDGE mobilisation using an external planning tool 18

Figure 3. Planning EDGE mobilisation using CM Editor 22

Figure 4. Implementing EDGE mobilisation 28

Figure 5. Example of alarm 3068 30

Figure 6. Example of alarm 3068 32


About this document

1 About this documentThis document describes the tasks involved in bringing EDGE into use in theGSM radio network:

• Plan the required radio network capacity and coverage.

• Plan EDGE coverage. This involves planning of the Dynamic Abis Poolsfor transmission and EGPRS parameters.

• Create the new EDGE capable objects in the network and in the NetActdatabase.

• Activate EDGE functionality in the GSM radio network.

• Verify network performance.

• EDGE mobilisation rollback.

1.1 NetAct compatibility and capacity information

For information on NetAct system and capacity, and the compatibility betweenNetAct and network element releases, see the NetAct Compatibility and CapacityInformation document.

1.2 Prerequisites

This section lists the functionality required to perform the operations described inthis document. Read this section carefully to avoid unnecessary troubleshootinglater.

The following Nokia NetAct applications are required to perform the tasksdescribed in this document:

• CM Operations Manager

• CM Editor



Note

• CM Analyser

• NetAct Planner (optional)

GPRS must be activated before implementing EDGE. For more information, seeEnabling GPRS in the GSM Radio Network.


EDGE features and Nokia NetAct support for EDGE

2 EDGE features and Nokia NetActsupport for EDGE

This chapter provides a brief overview of the Nokia EDGE network architecture,the respective EDGE features in the Nokia BSS, and the support in Nokia NetActtools for building and optimising EDGE coverage.

In the Nokia solution, EDGE is deployed as an overlay of the GPRS packet coreto enable higher data rates. This means that GPRS must be activated in thenetwork before implementing EDGE.

The EDGE supported features that can be managed via Nokia NetAct areintroduced briefly in the following section.

2.1 Dynamic Abis Pool

The Dynamic Abis feature makes it possible to define common transmissionresources for EDGE capable TRXs situated in the same Abis ET PCM. Thiscommon resource is called the Dynamic Abis Pool (DAP).

DAP is supported on the GSM 900 and GSM 1800 bands as well as GSM 800 andGSM 1900 bands.

There are fixedly allocated transmission resources for Abis signalling links andtraffic channels in Abis ET PCM as before but extra transmission resourcesneeded for EGPRS data are reserved from the Dynamic Abis pool.

DAP is required for EDGE and it must be enabled in the BSCs. See Dynamic AbisPool Handling (dn01444) for instructions on how to handle Dynamic Abis poolsin the BSC.



2.2 Multi-BCF in the EDGE capable radio network

Multi-BCF is an optional Nokia BSS feature that allows the combination ofseveral BTSs into one logical cell, increasing the capacity of a cell whilemaintaining the maximum spectral efficiency. Multi-BCF is supported on theGSM 900 and GSM 1800 bands, as well as GSM 800 and GSM 1900 bands.

For EDGE, the Multi-BCF feature provides an evolution path from Talk FamilyBTSs to co-sited EDGE capable Nokia UltraSites, FlexiEDGE or MetroSites. TheMulti-BCF sites can accommodate Nokia Talk Family BTSs and NokiaUltraSites. Unlike Talk Family BTSs, UltraSite base stations can accommodateEDGE TRXs. FlexiEDGE can be defined in the Multi-BCF configuration onlywith UltraSites. Multi-BCF makes it possible to increase the cell capacity for TalkFamily and UltraSite BTSs to 36 TRXs while requiring no extra BCCH at theMulti-BCF site.

2.3 Overview of planning EDGE mobilisation

The following figure shows an overview of the interworking NetAct tool set usedfor EDGE mobilisation. Note that NetAct Planner is used here to create the EDGEplan. If NetAct Planner is not available, this plan is created using CM Editor.


EDGE features and Nokia NetAct support for EDGE

Figure 1. Nokia NetAct tool set for planning, building, and optimising EDGEcoverage

If you have NetAct Planner and the Traffic Data for Radio Planner functionalityin your NetAct system, you can use cell level CS and HSCSD traffic datacollected in the NetAct databases as a basis for planning EGPRS coverage,capacity, and the required network configuration changes with NetAct Planner.The traffic data can be transferred from NetAct to the NetAct Planner database.

Actualparameters

Nokia NetAct Configurator andAdministrator

EDGE relatedobjects andparameters

Build and optimise EDGE coverage- Download and activate EDGE software in BTSs- Complete radio network plan- Mass download EDGE radio network plan- Manage Multi-BCF, DAP parameter configurations and parameter modifications

Planning tool- Plan EDGE enabled sites- Plan Multi-BCF sites

Upload currentnetwork configuration

BSS

EGPRS networkplan

EDGE plansto network

GPRS BB

EDGETRX

Segment

BSC SGSN

Multi-BCF site

Trafficmeasurementdata

Nokia NetActReporter-Collect traffic measurement data- Verify EDGE performance

TRX

BTS BTS

BCF BCF



For information on how manage and activate software in network elements, seeManaging Network Element Software.


Enabling EDGE in the Nokia BSS

3 Enabling EDGE in the Nokia BSSThis chapter describes the tasks involved in deploying EDGE in the Nokia BSS.

3.1 Preconditions for the operation

Before you can start with the actual procedure, the following preparations mustbe ready.

3.1.1 Preconditions in the Nokia BSS

The following preparations need to be ready before you start the actual operation.

• The necessary Dynamic Abis, EGPRS, and GPRS options have beenactivated in the BSCs and the BSC is operational or under commissioning.For details regarding the required EGPRS and GPRS options in the BSC,see GPRS in BSC (dn99565086).

• The S10.5ED (or later) software is active in the BSCs.

• PCU cards have been installed in the BSCs.

• There are several connected, empty Abis ET PCMs lines in the BSC.

• If Multi-BCF is used, Multi-BCF options must be set in the BSC. For moreinformation, see Maintaining Multi-BCF Sites.

• BTS EDGE transmission configuration is commissioned. DAP timeslotsare configured to the Abis allocation.

3.1.2 Preconditions in Nokia NetAct

• The Nokia NetAct software required in the operation has been installed.

• Nokia NetAct is fully functional.

• The necessary EDGE specific options have been uploaded from thenetwork.



Note

Note

3.2 Building EDGE Coverage

You can build EDGE coverage by adding EDGE TRXs to existing MetroSites, orby adding new MetroSites, UltraSites or FlexiEDGE. UltraSites can be co-sitedwith old TalkFamily BTSs.

Dynamic Abis Pool (DAP) is required for EDGE. Instructions for DAP creationare given in this section.

EDGE does not require Multi-BCF. EDGE can be activated on non-Multi-BCFsites.

3.2.1 Creating new MetroSites, UltraSites or FlexiEDGE

For details on how to create BTS sites and update the BTS hardware database, seeCreating BTS Sites.

UltraSites or MetroSites and FlexiEDGE with EDGE capability can be co-sitedwith TalkFamily BTSs. It is also possible to create Multi-BCF sites. For moreinformation, see Maintaining Multi-BCF Sites.

3.2.2 Adding EDGE TRXs to MetroSites, UltraSites or FlexiEDGE

EDGE TRXs can be added to MetroSites, UltraSites or FlexiEDGE. For moredetails, see Extending GSM BTS Sites.

3.2.3 Creating the Dynamic Abis Pool

Dynamic Abis feature is a mandatory feature to enable EGPRS support in theBSC and in the PCU. DAP must be created in the same PCU where the Gbinterface is used in the BTS.

The First TSL and Last TSL parameters of DAP must be exactly the same as inthe BTS. This can be configured with Node Manager. For more information, seeEGPRS Implementation Guide for GSM/EDGE BSS (dn03300436).

If Dynamic Abis is used, you must define the pool to be used by the TRX. It mustbe located on the same PCM as TRXSIG and the fixed traffic timeslots.


Enabling EDGE in the Nokia BSS

Note

• In BSC S10.5ED and S11, Dynamic Abis usage cannot be modified later.If you want to change the TRX’s usage of Dynamic Abis, the TRX must bedeleted and created again.

• In BSC S11.5, Dynamic Abis of the TRX can be modified, if TRX islocked.

In BSC S10.5ED and S11, CM Operations Manager automatically deletes and re-creates TRX when Dynamic Abis is added or modified for TRX in a plan.

In BSC S11.5, TRX deletion and creation is not required when Dynamic Abis isadded or modified for TRX.

DAP parameters can be modified later. For example, the size of the DAP can bemodified even if it has been attached to TRX. DAP size modification requires alsothat the DAP size in Abis allocation must be modified accordingly.

For operating instructions on how to create Dynamic Abis Pool, see DynamicAbis Pool Handling (dn01444).

3.2.4 Creating Multi-BCF sites

Multi-BCF sites can be created, but this is an optional feature. See MaintainingMulti-BCF Sites for details on this operation.


Planning EDGE mobilisation

Note

4 Planning EDGE mobilisationTo plan changes in your radio network, you can use CM Editor. CM Editor hassearch and mass modify functionalities, which enable you also to create larger-scale parameter change plans.

You can also plan parameter changes with any external planning tool available,provided that the interfaces are compliant with the Nokia NetAct solution XML(RAML 2.0) or CSV.

For more information on the XML (RAML 2.0) interface, refer to the documentXML Interface for Radio Access Planning Data.

For more information on the CSV interface, refer to the document CSV Interfacefor Radio Access Planning Data.

4.1 Planning EDGE mobilisation using an externalplanning tool

This section describes how EDGE mobilisation can be planned using an externalplanning tool.

If you do not have a planning tool, the EDGE mobilisation plans can be createdusing CM Editor. For more information, see 4.2 Planning EDGE mobilisationusing CM Editor.

4.1.1 Overview of this procedure

The following figure illustrates the procedure for planning EDGE mobilisation.



Figure 2. Planning EDGE mobilisation using an external planning tool

4.1.2 Uploading BSS data from NetAct

Upload the BSC configuration with CM Operations Manager. This is done tomake NetAct and network information consistent.

Export actual BSS data toXML file(s)

Start

Upload BSS data fromNetAct

Importing XML file(s)

CM OperationsManager

Create GPRS disablingplan

Create DAP creation plan

Create GPRS enablingplan

Create EDGE activationplan


Planning tool

Planning tool

Planning tool

Planning tool

Planning tool

Export the plansPlanning tool

Import the plansCM Operations

Manager

Verify the plansCM Analyser

End



For instructions, see Uploading actual configurations in CM Operations ManagerHelp.

4.1.3 Exporting actual BSS data to XML or CSV file(s)

With CM Operations Manager, you can export the actual configuration to anXML (RAML 2.0) or CSV file.

To export actual configuration

• Export the actual configuration to an XML (RAML 2.0) or CSV file withCM Operations Manager.

For instructions, see CM Operations Manager Help.

4.1.4 Importing XML or CSV file(s)

Import the XML (RAML 2.0) or CSV files into an external planning tool.

4.1.5 Creating GPRS disabling plan

Create the GPRS disabling plan in an external planning tool. Modify the GPRSEnabled parameter to false.

4.1.6 Creating DAP creation plan

Create the DAP creation plan in an external planning tool.



Note

The parameters needed in the DAP plan for the EDGE TRXs are: PCM CircuitID, DAP ID, First TSL, Last TSL, BCSU ID, and PCU ID.


The maximum size for DAP is 12 timeslots.

Rules for DAP creation:

• The DAP must be on the same PCM as the Abis PCM of the TRX.

• The DAP NSEI must be the same as the BTS NSEI. This means that DAPBCSU and PCU must be the same as the FRBC’s BCSU and PCU that theBTS is using. The FRBC is where the child NSVC’s NSEI is the same asthe BTS’s NSEI.

For detailed information on the parameters in Nokia NetAct, see BSS RNWParameters and MSC RNW Parameters.

4.1.7 Creating EDGE activation plan

Create the EDGE activation plan in an external planning tool.

Modify the EGPRS parameters of BTS and TRX. It is mandatory to set the BTSparameter EGPRS Enabled to true, and define the TRX parameter DAP ID. OtherEGPRS parameters are optional.


4.1.8 Creating GPRS enabling plan

Create the GPRS enabling plan in an external planning tool. Modify the GPRSEnabled parameter to true.

4.1.9 Exporting the plans

Export the plans from the external planning tool.



To export the plans

• Export the plans to an XML (RAML 2.0) or CSV file.

4.1.10 Importing the plans

Import the XML (RAML 2.0) or CSV file containing the plans to NetAct.

To import the plan in CM Operations Manager

• Import the plan in an XML (RAML 2.0) or CSV file with CM OperationsManager.


4.1.11 Verifying the plans

Check that the EDGE mobilisation plan is correct.

To verify the plan using CM Analyser

1. Check the consistency of radio network parameters in the plan with CMAnalyser. Run the EDGE rule set. For more information, see CheckingEDGE consistency in Rules and Rule Syntax for Radio AccessConfigurator.

For instructions, see CM Analyser Help.

2. If autocorrection was used, missing, extraneous, or inconsistent objects andparameters are updated to the plan. If autocorrection was not used, correctthe errors with CM Editor.

For instructions, see CM Editor Help.

3. Repeat the checks until no errors are found.



4.2 Planning EDGE mobilisation using CM Editor

If you do not have an external planning tool, you can use CM Editor to create theEDGE mobilisation plans. This section describes how EDGE mobilisation can beplanned using CM Editor.

4.2.1 Overview of this procedure

The following figure illustrates the procedure of planning EDGE mobilisation.

Figure 3. Planning EDGE mobilisation using CM Editor

Start



CM Editor

CM Editor

CM Editor

CM Editor

CM Analyser Verify the plans

Export actual BSS data toXML file(s)

Upload BSS data fromNetAct

Create GPRS disablingplan

Create DAP creation plan

Create EDGE activationplan

Create GPRS enablingplan

End



4.2.2 Uploading BSS data from NetAct

Upload the BSC configurations with CM Operations Manager. This is done tomake NetAct and network information consistent.

For instructions, see Uploading actual configurations in CM OperationsManager Help.

4.2.3 Exporting actual BSS data to XML file(s)

To make a backup of the network configuration you can export the actualconfiguration to an XML (RAML 2.0) file with CM Operations Manager. Theobject classes that need to be backed up are: BTS, TRX, POC, ADCE, and DAP.

To export actual configuration

• Export the actual configuration to an XML (RAML 2.0) file with CMOperations Manager.


4.2.4 Creating GPRS disabling plan

Create the GPRS disabling plan with CM Editor. Using the Search and Modifyfunctionality of CM Editor, modify the GPRS Enabled parameter to false for allthe BTSs in the BSC.

For more information, see CM Editor Help.

4.2.5 Creating DAP creation plan

Create the DAP creation plan with CM Editor.

To create DAP creation plan with CM Editor

1. Create a plan.

2. The parameters needed in the DAP plan for the EDGE TRXs are describedbelow:



Note

DAP parameters: PCM Circuit ID, DAP ID, First TSL, Last TSL, BCSUID, and PCU ID


The maximum size for DAP is 12 timeslots.

Rules for DAP creation:

• The DAP must be on the same PCM as the Abis PCM of the TRX.

• The DAP NSEI must be the same as the BTS NSEI. This means that DAPBCSU and PCU must be the same as the FRBC’s BCSU and PCU that theBTS is using. The FRBC is where the child NSVC’s NSEI is the same asthe BTS’s NSEI.


For more information on using CM Editor, see CM Editor Help.

4.2.6 Creating EDGE activation plan

Create the EDGE activation plan with CM Editor.

To create EDGE activation plan with CM Editor

1. Create a plan.

2. Insert BTSs, their TRXs, and POCs that have been selected to be EDGEactivated.

3. Modify the EGPRS parameters of BTS and TRX. It is mandatory to set theBTS parameter EGPRS Enabled to true, and define the TRX parameterDAP ID. Other EGPRS parameters are optional.


For more information on using CM Editor, see CM Editor Help.



4.2.7 Creating GPRS enabling plan

Create the GPRS enabling plan with CM Editor. Using the Search and Modifyfunctionality of CM Editor, modify the GPRS Enabled parameter to true for allthe BTSs in the BSC.

For more information, see CM Editor Help.

4.2.8 Verifying the plans

Check that the EDGE mobilisation plan is correct.

To verify the plan using CM Analyser







Implementing EDGE mobilisation

Note

5 Implementing EDGE mobilisationThis chapter guides you through the actual implementation phase of EDGEmobilisation. During this phase, changes are made to the live network.

Implementing EDGE mobilisation to the live network causes network downtimefor the duration of the operation. The mobilisation phase should be implementedduring a low traffic period, for example, during the night.

5.1 Preconditions

• DAPs have been planned using Node Manager. For more information, seeEGPRS Implementation Guide for GSM/EDGE BSS (dn03300436).

• Plans for GPRS disabling, DAP creation, EDGE activation, and GPRSenabling are ready and verified.

• BTS EDGE transmission configuration is commissioned. DAP timeslotsare configured to the Abis allocation.

5.2 Overview of the mobilisation procedure

The following figure illustrates the procedure of implementing EDGEmobilisation.



Figure 4. Implementing EDGE mobilisation

5.3 Activating maintenance mode

Maintenance Mode is an optional feature, which allows you to filter out alarmsfrom objects under maintenance. You can activate the maintenance mode for oneobject or one object and its subnetwork. You can deactivate the maintenancemode only from the object from which it was activated.

Provision GPRS disablingplan to network

End

Activate maintenancemode

Provision DAP creationplan to network

Top-level UserInterface

Provision EDGEactivation plan to network

Provision GPRS enablingplan to network

Turn off maintenancemode





Top-level UserInterface

Verify actual configurationCM Analyser

Start



To activate maintenance mode with Top-level User Interface

1. Select the desired object in a Top-level User Interface view.

2. Open the object pop-up menu and select Maintenance Mode → Activatefor MO and Subnetwork.

For more information, see Top-level User Interface Help.

The colour of the object changes to the colour of the Maintenance Mode Root andthe colour of the subnetwork objects changes to the colour of the MaintenanceMode Child.

5.4 Provisioning GPRS disabling plan to network

Provision the GPRS disabling plan to the network using CM Operations Manager.

To provision the GPRS disabling plan to network

1. In CM Operations Manager, select the plan and the objects you want toprovision. Then Provision dialog box will appear. Click on the start button.

2. When the activation operation is finished, check the operation history forerrors.

3. If the plan was not activated for some objects because of errors, repeat theoperation for those objects.


5.5 Provisioning DAP creation plan to network

Provision the DAP creation plan to the network using CM Operations Manager.



To provision the DAP creation plan to network

1. In CM Operations Manager, select the plan and the objects you want toprovision. Then Provision dialog box will appear. Click on the startbutton.Confirmation dialog will appear click on yes button




During DAP provisioning, you should use an alarm monitoring software tomonitor Alarm 3068 (EGPRS DYNAMIC ABIS POOL FAILURE). RemoveDAP objects that are sending these alarms. See the example error message below:

Figure 5. Example of alarm 3068

In the above error example, the first three fields marked here with red colouridentify the DAP, BCSU and PCU. In this particular case, the error is related toDAP 114 (72 in hex), which is connected to the PCU with index 4 on BCSU 5.The sixth field with value 03 in the example indicates the reason for the alarm:

• (1) no resources in PCU

• (2) connection error

• (3) information update error

• (4) PCU not ready

• (5) other

To remove DAP objects that are sending the 3068 alarm

1. Delete the DAP object.

<HIST> RVSDBSC01 MCMU-0 SWITCH 2003-08-13 00:54:23.03** ALARM ........ RC0_BG (0300) 3068 EGPRS DYNAMIC ABIS POOL FAILURE

0072 5d 4d FF 04 03 65535d 255d 65535d 255d



2. Provision failed DAPs using CM Operations Manager.


5.6 Provisioning EDGE activation plan to network

Provision the EDGE activation plan to the network using CM OperationsManager.

To provision the EDGE activation plan to network

1. In CM Operations Manager, select the EDGE Activation plan and theobjects you want to provision. The Provision dialog box will appear. Clickon the start button. Confirmation dialog will appear click on yes button.




5.7 Provisioning GPRS enabling plan to network

Provision the GPRS enabling plan to the network using CM Operations Manager.

To provision the GPRS enabling plan to network

1. In CM Operations Manager, select the plan and the objects you want toprovision.






During the provisioning of the GPRS enabling plan, you should use an alarmmonitoring software to monitor Alarm 3068 (EGPRS DYNAMIC ABIS POOLFAILURE). Remove DAP objects that are sending these alarms. See the exampleerror message below:

Figure 6. Example of alarm 3068

In the above error example, the first three fields marked here with red colouridentify the DAP, BCSU and PCU. In this particular case, the error is related toDAP 114 (72 in hex), which is connected to the PCU with index 4 on BCSU 5.The sixth field with value 03 in the example indicates the reason for the alarm:

• (1) no resources in PCU

• (2) connection error

• (3) information update error

• (4) PCU not ready

• (5) other

To remove DAP objects that are sending the 3068 alarm

1. Delete the DAP.

2. Provision failed DAPs using CM Operations Manager.


5.8 Verifying actual configuration

Check that the radio network actual configuration is correct.

<HIST> RVSDBSC01 MCMU-0 SWITCH 2003-08-13 00:54:23.03** ALARM ........ RC0_BG (0300) 3068 EGPRS DYNAMIC ABIS POOL FAILURE

0072 5d 4d FF 04 03 65535d 255d 65535d 255d



To verify actual configuration in CM Analyser






5.9 Turning off maintenance mode

Maintenance Mode is an optional feature, which allows you to filter out alarmsfrom objects under maintenance. You can activate the maintenance mode for oneobject or one object and its subnetwork. You can deactivate the maintenancemode only from the object from which it was activated.

To deactivate maintenance mode with Top-level User Interface

1. Select the desired Maintenance Mode Root in a Top-level User Interfaceview.

2. Open the object pop-up menu and select Maintenance Mode →Deactivate.

For more information, see Top-level User Interface Help.

The colour of the object(s) changes to represent the most severe alarm active inthe object(s). However, if there are overlapping maintenance mode activations,some objects might still remain in the maintenance mode.


EDGE mobilisation rollback

6 EDGE mobilisation rollbackThis chapter describes a rollback procedure for an individual site and for an entirenetwork.

6.1 Rollback for entire network

To rollback the entire network

1. Provision the GPRS disabling plan with CM Operations Manager.

2. Provision the backup of EDGE activation plan with CM OperationsManager

3. Provision the backup of DAP creation plan with CM Operations Manager

4. Provision the GPRS enabling plan with CM Operations Manager.

For more information on the CM Operations Manager application, see CMOperations Manager Help.


Verifying network performance

7 Verifying network performanceOnce EDGE has been activated for your customers and there is EGPRS traffic inthe network, verify that the packet and circuit switched services are functioningas expected by monitoring alarms and creating performance measurementreports.

Verify the success of EDGE activation by checking:

• DAP alarms, BTS alarms, Segment specific alarms

• Quality of service monitoring for EDGE

• Network Doctor for BSS reports for EDGE and Multi-BCF. Note thatNetwork Doctor for BSS is an optional tool in NetAct Reporter.

Nokia NetAct Tracing is a separate and optional tool that enables on-line and off-line GSM and GPRS tracing and trace management either regionally or globally(within the management scope of several regional NetActs). Trace function givesdetailed information on calls which are related to the defined IMSI/MSISDN orIMEI numbers. In Tracing, EDGE is visible in the following reports:

• GPRS Flow Control report provides useful information concerning theresource consumption (bucket size) and quality related transactions (leakrate). Leak rate is always associated with downlink.

• GPRS Number of MCS changes report provides the number of networkcaused (unknown reason) MCS (Modulation Coding Scheme) changes.

• GPRS Data transferred per MCS (UL/DL) report provides informationconcerning the error and resend rate and the amount of data transferred datawith each MCS. Coding schemes CS-1 and CS-2 are first supported in S9-release. In S10, EGPRS was introduced with MCS1-9. S11 providescoding schemes 3 and 4.



7.1 Dynamic Abis report (280)

The Dynamic Abis functionality allocates Abis transmission capacity to cellswhen extra capacity is needed by EGPRS, instead of reserving a full fixedtransmission link per TRX. The Dynamic Abis measurement used for the reportprovides information on the usage of DAP both in uplink and downlinkdirections.

This report can be used to:

• Find pools where the pool capacity is not adequate and to reconfigure cellsfor using pools where capacity is available.

• Check which cells are in the pool.

For detailed information on the report, see BSS Network Doctor Reports(dn98614186) in Network Doctor documentation.

7.2 EGPRS KPI report (226)

Key performance indicators (KPIs) provide information on the availability ofservice, the volume of service, and the quality of service. The EGPRS KPI reportallows you to generate an EGPRS KPI table with various object and timeaggregation levels.

This report is normally used so that you first run the report with average timeaggregation and when you find an interesting BTS, zoom into that by using thedaily or hourly time aggregation.


7.3 EGPRS RLC statistics report (275)

This report generates information on RLC (Radio Link Control), which is theprotocol used in (E)GPRS between the mobile station and the base station system.



Verifying network performance

7.4 WCDMA adjacencies having high HO failure ratioreport (159)

This report generates information on handover (HO) failures.


7.5 Common BCCH, Multi-BCF HO (151)

This report generates information about intra-segment and inter-segmenthandovers.

For detailed information on the report, see BSS Network Doctor Reports(dn98614186) in Network Doctor Documentation.

7.6 Other common BCCH reports

For single segment troubleshooting and analysis, the following reports can beused:

• Cell doctor (211)

• Cell analyser (210)

In addition to the fore mentioned reports, also the following report is supported:

• Segment configuration (052)

Also other reports support segment as an aggregation level where applicable.

For detailed information on these reports, see BSS Network Doctor Reports(dn98614186) in Network Doctor documentation.


Rehosting EDGE BTSs

8 Rehosting EDGE BTSsThis chapter describes what aspects need to be taken into account when rehostingEDGE BTSs.

When rehosting EDGE BTSs, the following issues need to be taken into account:

• The necessary EDGE and GPRS option must be active in the target BSC.

• The GPRS columns and EGPRS columns need to be defined. Define alsothe correct RAC value.

• The DAP object that will be used in the target BSC must be created beforecreating other RNW managed objects.

• The DAP ID of an existing DAP object needs to be given for the targetTRXs.

For basic instructions on how to rehost BTS sites, see Rehosting GSM BTS Sites.


Where to find more information

9 Where to find more informationFor information on the tasks involved in bringing EDGE into use in the radionetwork, see:

• Enabling GPRS in the GSM Radio Network

• Managing Network Element Software

• EGPRS Implementation Guide for GSM/EDGE BSS (dn03300436). Thisdocument shows the whole EDGE implementation.

For more information on Dynamic Abis Pool, see:

• Dynamic Abis Pool Handling (dn10444)

For more information on rehosting, see:

• Rehosting GSM BTS Sites

For more information on radio network parameters, see:

• BSS RNW Parameters

• MSC RNW Parameters

For more information on reports, see:

• BSS Network Doctor Reports (dn98614186)

Other useful references:

• XML Interface for Radio Access Planning Data

• CSV Interface for Radio Access Planning Data

• Maintaining Multi-BCF Sites

• GPRS in BSC (dn99565086)

• GPRS Handling in the BSC (dn99565074)



• Nokia NetAct Planner 5.0 User Reference Guide (dn0494485), in theNetAct Planner document set

• Common BCCH Control in BSC (dn0176501)


IndexB

BSS dataexporting 19, 23uploading 18, 23

C

Common BCCH 44creating

DAP creation plan 19, 23EDGE activation plan 20, 24

D

Dynamic Abis Pool 7, 9, 14

E

exportingactual BSS data 19, 23plans 20

G

GPRScreating disabling plan 19, 23creating enabling plan 20, 25enabling 8plans 27provisioning disabling plan 29

I

importingplans 21XML files 19

M

maintenance modeactivating 28turning off 33

MetroSites 14Multi -BCF 10, 13, 15

P

PCU 13, 14, 30, 32planning mobilisation

using CM Editor 22

using external planning tool 17preconditions 27prerequisites 7provisioning

DAP creation plan 29EDGE activation plan 31GPRS disabling plan 29GPRS enabling plan 31

R

reportsCommon BCCH, Multi -BCF HO (151). 39Dynamic Abis (280) 38EGPRS KPI (226) 38EGPRS RLC statistics (275) 38other common BCCH 39WCDMA adjacencies having high HO failure ratio

(159) 39rollback

entire network 35for EDGE mobilisation 35

U

UltraSites 10, 14uploading BSS data 18, 23

V

verifyingactual configuration 32performance 37plans 21, 25

DN00275994 ©Nokia Corporation 45 (46)Issue 4-0 en Nokia Proprietary and Confidential

Building and Extending EDGE

Documents

Transcript of Building and Extending EDGE