int_adm_rnw

WCDMA RAN, Rel. RU40, Operating Documentation, Issue 04

Administering WCDMA Radio NetworksDN03471515

Issue 09AApproval Date 2013-09-12

Confidential

2 DN03471515Issue 09A

Administering WCDMA Radio Networks

Id:0900d80580a4d302Confidential

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 Solutions and 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 trans-mitted in any form or means without the prior written permission of Nokia Solutions and 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 Solutions and 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 Solutions and Networks and the customer. However, Nokia Solutions and 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 Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks, explain issues which may not be covered by the document.

Nokia Solutions and Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Solutions and Networks BE LIABLE FOR ERRORS IN THIS DOCU-MENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, 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.

NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright 2013 Nokia Solutions and Networks. 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.

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their compo-nents.

If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Solutions and Networks for any additional informa-tion.

DN03471515 3



Table of ContentsThis document has 84 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 Radio network management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 Configuring the RNC object for IPA-RNC for the first time . . . . . . . . . . . 8

3 Configuring the RNC object for multicontroller RNC for the first time . . 10

4 General instructions for managing objects. . . . . . . . . . . . . . . . . . . . . . . 124.1 Creating objects in database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.2 Editing object parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144.3 Deleting objects from database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5 Basic operations for managed objects. . . . . . . . . . . . . . . . . . . . . . . . . . 185.1 RNC object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185.2 RNAC object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195.3 RNPS object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205.4 RNHSPA object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215.5 RNRLC object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225.6 RNTRM object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235.7 RNMOBI object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245.8 RNFC object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255.9 RNCERM object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265.10 IUO object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275.11 IPQM object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.12 IUCS object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.12.1 IUCSIP object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.13 IUPS object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315.13.1 IUPSIP object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315.14 CBCI object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.15 IUR object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345.16 CMOB object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.17 COCO object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365.18 IPNB object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385.19 FMC object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395.20 HOP object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405.21 TQM object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415.22 WRAB object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425.23 WAC object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435.24 PFL object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445.25 PREBTS object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455.26 VBTS site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465.26.1 VCEL object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465.27 WBTS site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485.27.1 WCEL object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.27.1.1 Adjacency (ADJx) for a WCDMA cell. . . . . . . . . . . . . . . . . . . . . . . . . . . 515.28 WSMLC object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

4 DN03471515



5.29 WLCSE object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555.30 WANE object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565.31 WSG object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

6 Special operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586.1 Locking or unlocking WCEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586.2 Requesting WBTS reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606.3 Retrieving active alarms of selected object. . . . . . . . . . . . . . . . . . . . . . . 626.4 Viewing BTS Connection Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 636.5 Viewing Overview pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646.5.1 Viewing WBTSs Overview page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646.5.2 Viewing WCELs Overview page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666.5.3 Viewing Adjacencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676.5.4 Viewing IPNBs Overview page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696.5.5 Viewing IURs Overview page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706.5.6 Viewing COCOs Overview page (IPA-RNC). . . . . . . . . . . . . . . . . . . . . . 726.5.7 Viewing IUCSIPs Overview page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736.5.8 Viewing IUPSIPs Overview page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756.5.9 Viewing IADAs Overview page (Flexi Direct OMS). . . . . . . . . . . . . . . . . 76

7 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797.1 Troubleshooting the O&M connection between OMS and IPA-RNC . . . 797.2 Troubleshooting RNC objects in OMS Element Manager Topology Brows-

er. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

DN03471515 5

Administering WCDMA Radio Networks Summary of changes


Summary of changesChanges between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues. For more information, see Guide to WCDMA RAN Operating Documentation.

g IPA-RNC, mcRNC, Flexi Direct RNC and BTS parameter descriptions in PDF format have been removed from WCDMA Operating Documentation.From this issue on, the parameter descriptions, including changes in parameters, are delivered in Excel format in a separate parameter document set in NOLS Product Infor-mation Center.

Changes between issues 09 (2013-03-22, RU40) and 09A (2013-09-20, RU40)RNCERM object has been added.

Deletion prerequisites have been added for the following objects:

WAC object PFL objectChanges between issues 08I (2012-11-23, RU30) and 09 (2013-03-22, RU40)Configuring the RNC object for multicontroller RNC for the first time has been updated to include the new default _nokadmin user at login.The following objects have been updated for RU40:

IUO object CBCI objectAny possible mcRNC and Flexi Direct content will be finalized by mcRNC and Flexi Direct RNC piloting phase.

Changes between issues 08H (2012-08-24, RU30) and 08I (2012-11-23, RU30)All managed objects in Basic operations for managed objects have been improved with clearer descriptions.

VBTS site and WBTS site have a warning added about deleting the WBTS and WCEL object in OMS Element Manager.

WBTS site has been updated with the following:

WCEL unlocking instructions have been added ADJS description has been added ADJx description has been improved and more information has been added to

Before you start

6 DN03471515



Summary of changes

DN03471515 7

Administering WCDMA Radio Networks Radio network management

Id:0900d80580a1cabcConfidential

1 Radio network managementRadio network administration deals with managing a number of logical configuration management objects in order to control their physical counterparts in the radio access network (RAN). For example, the user may create a WCDMA base station (WBTS) object, and adjust the parameters of the object, in order to control the behavior of a certain base station in the field. The logical objects correspond to:

network elements (for example, radio network controller (RNC), WCDMA base station (WBTS)

the interfaces between the elements (for example, Iur) virtual objects (for example, WCDMA SMLC)The logical objects created with the OMS Element Manager Web UI are hierarchically related to each other, and this imposes an order in which they must be created. The RNC is the topmost object in the hierarchy and consequently has to be created first in the radio network plan. OMS Element Manager WebUI provides online help to assist you in carrying out the tasks. You can access the online help by clicking the Help button. See Using OMS Element Manager for more information.

g With the introduction of new products in the system and the documentation library, product naming practices are being harmonized. RNC is used when referring to all three controller products: IPA-RNC, Multicontroller RNC (mcRNC), and Flexi Direct RNC. Each product is referred to with its own name wherever applicable, that is, IPA-RNC, mcRNC, or Flexi Direct RNC. If IPA-RNC is mentioned in a document title or category heading, the material is IPA-RNC-specific, and RNC is used throughout the document to refer to IPA-RNC only. IPA-RNC MML command documents are an example of such usage.

The preferred order of radio network managed object creation and editing:

RNC, RNAC, RNPS, RNHSPA, RNRLC, RNTRM, RNMOBI, RNFC, RNCERM, IUO, IPQM, IUCS, IUCSIP, IUPS, IUPSIP, CBCI, IUR, CMOB, COCO (IPA-RNC only), IPNB, FMCS, FMCI, FMCG, HOPS, HOPI, HOPG, HOPL, TQM, WRAB, WAC, PFL, PREBTS (IPA-RNC only), VBTS, VCEL, WBTS, WCEL, ADJS, ADJD, ADJI, ADJG, ADJL, WSMLC, WLCSE, WANE, WSG

Deletion is in the reverse order of creation and editing. By deleting a certain object, all of the objects under it in the hierarchy are also deleted.

g Different restrictions apply for different objects. Whereas it is impossible to create certain objects independently (for example, WCEL), other objects (for example, COCO) can be created without being related to the hierarchy right away.

g All procedures require the use of the OMS Element Manager. You can launch Parame-ter Editor from the OMS Element Manager.

8 DN03471515


Id:0900d8058093d4c1Confidential

Configuring the RNC object for IPA-RNC for the first time

2 Configuring the RNC object for IPA-RNC for the first timePurposeWhen the OMS Element Manager is first taken into use after IPA-RNC commissioning, the very first task is to configure the IPA-RNC by setting the required parameters. The RNC requires two parameters, RNCid and OMSIPAddress, to establish a connection to the OMS.

See Radio network management for the preferred order of object creation and editing.

The OMS Element Manager provides online help to assist you in carrying out the tasks. You can access the online help by clicking the Help button.

g This does not apply to the mcRNC.

g The IPA-RNC object cannot be created using the Parameter Editor.Before you startOMU and OMS have to be configured to the operators O&M network. For more informa-tion, see Configuring IP connection for RNC.

In order to create the initial IPA-RNC configuration and get the IPA-RNC integrated to the OMS, follow these steps from the WO-EX OMU service terminal session.

Steps

1 Start a remote service terminal session using MML terminal (DDS) from the WO-EX OMU.ZDDS:OMU,;

2 Load RUOSTEQX STE to a free command character (In this example,'1').0000-MAN>ZLE:1,RUOSTEQX;

3 Give CR-command to create initial IPA-RNC configuration that enables IPA-RNC to connect to OMS using BTS O&M interface.0000-MAN>Z1CR:,,;

g RNC-ID is not modifiable after this without clearing the entire database using empty database files.g If empty spaces are needed for the RNCName parameter, they must be replaced with ~ characters. The service terminal does not allow empty spaces.g is the Southbound IP address.

4 Verify that the proper data was entered into the RNW Database.0000-RUO>Z1C;

DN03471515 9

Administering WCDMA Radio Networks Configuring the RNC object for IPA-RNC for the firsttime

Id:0900d8058093d4c1Confidential

5 Release RUOSTEQX0000-RUO>ZL:1;Expected outcomeThe IPA-RNC can start establishing BTS O&M connection to OMS. The rest of the RNW data can be then set with Parameter Editor or using RNW Plan download.

10 DN03471515


Id:0900d805809ab93cConfidential

Configuring the RNC object for multicontroller RNC for the first time

3 Configuring the RNC object for multicon-troller RNC for the first timeWhen the OMS Element Manager is first taken into use after mcRNC commissioning, the very first task is to configure the mcRNC by setting the required parameters.

The mcRNC needs two parameters in its Radio Network Database (RNCId and OMSI-PAddress parameters for the mcRNC object) to establish connection to the OMS. The configuration is done manually by the operator from the command line (an SSH session to the mcRNC/CFPU) after commissioning. There is an SCLI that takes RNC_ID and OMS_IP_ADDRESS parameters as input. The execution of the script results in the first rnc object creation and establish OMS connectivity.

The SCLI command takes two arguments:

--rncid --omsipadd See Radio network management for the preferred order of object creation and editing.

g The omsconn command can only work successfully if the system services are up and running. (Insert command to check if vital RUs (recovery units) of the system are in Active/Enabled state). At least the DB RU (QNDBRNWServer) and the O&M Services RU (QNOMUSingle) should be active and enabled for the configuration command to work successfully. To verify, on the command line enter zusi -ru.

Steps

1 Open SSH connection to multicontroller RNC IP address.

2 On the command prompt, run the following SCLI command:set omsconn rncid omsipadd

Example:set omsconn rncid 89 omsipadd 10.9.168.113Expected outcomeSuccessful operation displays:

DIRECT ACTIVATION: SUCCESS-------------------->>>>>>>

g is the Southbound IP address.

3 Exit the SCLI subshell by using quit SCLI command.

4 Verify that the mcRNC appears in the OMS Topology Tree.Expected outcomeThe BTS O&M connection of mcRNC and OMS is established and the mcRNC is visible in the OMS Topo;ogy Tree View. The rest of the RNW data can be then set with Param-eter Editor or using RNW Plan download.

DN03471515 11

Administering WCDMA Radio Networks Configuring the RNC object for multicontroller RNC forthe first time

Id:0900d805809ab93cConfidential

5 Alternatively, verify that the connection has been established using the following command in shell bash full:# netstat -net | grep 8002

12 DN03471515


Id:0900d80580a1caa8Confidential

General instructions for managing objects

4 General instructions for managing objects

4.1 Creating objects in databasePurposeThis procedure enables you to create objects under RNC in Radio Network database.

Before you startTo perform this operation you need to be authorized and have CMPlanManagement-manage permissions. You can create objects only under selected RNC.

Steps

1 Log into OMS Element Manager.For instructions, see Logging into OMS Element Manager.

2 Browse the Topology Tree and select RNC or managed object under RNC.

3 Select Create New Object > from the context menu.Choose the type of object that you want to create. The list of available objects depends on selected object. For RNC all managed objects are available. If you selected for example WBTS, only WCEL object can be created. You can also select the group of objects (for example COCOs group) and create the object in this group.

Expected outcomeParameter Editor opens showing parameters with default values for created object.

4 To use the filter: enter text in Filter text box or click one or more buttons: Manda-tory, Modified, Invalid or Empty.

Expected outcomeThe list of parameters is changed immediately when you enter text in the Filter text box or click filter buttons. To cancel filtering click X icon next to Filter text box and unselect filter buttons. Mandatory shows only mandatory parameters, Modified shows those parameters that were modified during current editing session, Invalid shows parame-ters with invalid value and Empty shows parameters without value.

g Note that Modified button displays only those parameters that were modified during current editing session. If you click Apply current editing session ends and when you edit again those parameters, they will not be in Modified group anymore.

g To refresh the parameters table click Reload button. Note that reloading does not cancel filtering.Further informationMandatory, Modified, Invalid and Empty button are toggle buttons. That means clicking them changes their state to ON or OFF. When the toggle is ON the button changes color and filter is active.

DN03471515 13

Administering WCDMA Radio Networks General instructions for managing objects

Id:0900d80580a1caa8Confidential

5 Select parameter group by clicking appropriate tab in the tabbed bar.Expected outcomeParameters from selected parameter group are displayed in a table. Note that if you use filtering, number of group tabs may differ. Tabs that are visible show only those param-eter groups where filtered parameters were found.

6 Edit parameters values by clicking on the field in Value column for parameter you want to edit.

Expected outcomeThe pop up list appears with information about minimum, maximum and default values for the parameter. The step value tells you how the value can change. For example if step is 1, the difference between consecutive values can be at least 1.

g You can select all parameters by selecting Select All from context menu.

7 To set default value: select parameter and choose Set Default Value from the context menu.

Further informationYou can select several parameters using CTRL or SHITF key.

If you want to change the parameter value back to previous, select parameters that you changed to default and select Back to Initial State from the context menu.

8 To display parameter description: select parameter and select Show Description from the context menu.

Expected outcomeThe Help pane opens on the right of the OMS Element Manager Web UI showing Details of selected parameter. You can view information about short name of parame-ter, its description, description of its value, type of modification and related parameters.

To close the Details pane, click arrow icon on top of the Help pane.

9 Click Apply button to save changes to all parameters.Expected outcomeA new managed object is created.

Unexpected outcomeErrors are displayed. If the creation fails, you are informed what is wrong (for example not all mandatory parameters are set or Object Identifier is missing). You can also close the Parameter Editor tab to cancel the operation.

14 DN03471515


Id:0900d805809bfa7aConfidential

4.2 Editing object parametersPurposeThis procedure enables you to edit object related parameters.

Before you startTo perform this operation you need to be authorized and have CMPlanManagement-manage permissions. Only 5 simultaneous Parameter Editor applications can be opened during one session.

Steps


2 Browse the Topology and select RNC or managed object.Expected outcomeThe Parameter Editor button becomes active.

Further informationYou must select a managed object or Network Element. The Parameter Editor button will not become active if you selected a group of objects (for example WBTSs).

3 Click Parameter Editor button or select Edit Parameters from the context menu.Expected outcomeThe Parameter Editor application loads to a new tab showing all object parameters.

4 To use the filter: enter text in Filter text box or click one or more buttons: Manda-tory, Modified, Invalid or Empty.

Expected outcomeThe list of parameters in a table is changed immediately when you enter text in the Filter text box or click filter buttons. To cancel filtering click X icon next to Filter text box and unselect filter buttons. Mandatory shows only mandatory parameters, Modified shows those parameters that were modified during current editing session, Invalid shows parameters with invalid value and Empty shows parameters without value.

g Note that Modified button displays only those parameters that were modified during current editing session. If you click Apply current editing session ends and when you edit again those parameters, they will not be in Modified group anymore.

g To refresh the parameters table click Reload button. Note that reloading does not cancel filtering.

DN03471515 15



Further informationMandatory, Modified, Invalid and Empty button are toggle buttons. That means clicking them changes their state to ON or OFF. When the toggle is ON the button changes color and filter is active.

5 Select parameter group by clicking appropriate tab in the tabbed bar.Expected outcomeParameters from selected parameter group are displayed in a table. Note that if you use filtering, number of group tabs may differ. Tabs that are visible show only those param-eter groups where filtered parameters were found.

g Parameter lists and Items are marked with an icon and with or marking in Value column. You can double click on their name or click the arrow icon next to their name to expand the list. Repeat the operation to collapse the list. If there is no arrow icon it means that the list is empty.

Parameter structures are marked with an icon but they have marking in Value column. There are also and items.

6 Edit parameters values by clicking on the field in Value column for parameter you want to edit.

Expected outcomeThe pop up list appears with information about minimum, maximum and default values for the parameter. The step value tells you how the value can change. For example if step is 1, the difference between consecutive values can be at least 1. If parameter can have only specific values without constant step, a list of those values is displayed in the list.

g You can select all parameters by selecting Select All from context menu.

g You can navigate through the parameter list by using arrow keys on your keyboard.

g When you edit parameters that requires WCEL locking (for example HSDPADynamicResourceAllocation) it will be locked automatically and you will be informed by pop up window.

7 To set default value: select parameter and choose Set Default Value from the context menu.

Further informationYou can select several parameters using CTRL or SHIFT keys.

If you want to change the parameter value back to previous, select parameters that you changed to default and select Back to Initial State from the context menu.

16 DN03471515



8 To display parameter description: select parameter and select Show Description from the context menu.

Expected outcomeThe Help pane opens on the right of the OMS Element Manager Web UI showing Details of selected parameter. You can view information about short name of parame-ter, its description, description of its value, type of modification and related parameters.

To close the Details pane, click arrow icon on top of the Help pane.

9 To add parameter to the parameter list or an item to the structure : select the parameter list and choose Add Parameter from the context menu or select struc-ture or item list and choose Add Item from the context menu.

Expected outcomeThe parameter/item is added to the list and arrow icon shows next to the list icon. It means that you can expand and collapse the list/structure.

10 To export parameters to XML file: click Export button.Expected outcomeThe new browser window opens and XML file is being prepared. Once preparation is finished you are prompted by default browser pop up window whether you want to open or save XML file with exported parameters. Note that you can export parameters of one object a time. All parameters are exported regardless which parameter tab is currently active. The exported XML file is a configuration plan for selected object.

g If you click Export button after changing parameters without clicking Apply button, a pop up window appears. It informs you that the current parameter configuration has not yet been applied and asks you whether you want to export the current configuration (with changes) or original configuration (without changes).

11 Click Apply button to save changes to all parameters.Further informationIf you made changes to parameters and you close the Parameter Editor tab, the pop up window will appear with warning that closing the applications will cancel all changes. Click Yes to close application and cancel changes, or No to keep Parameter Editor opened.

12 To close Parameter Editor application: click Close buttonExpected outcomeIf you have made changes without saving them with Apply button, the pop up window will ask you whether you are sure you want to close Parameter Editor without saving changes.

DN03471515 17


Id:0900d805809bfa74Confidential

4.3 Deleting objects from databasePurposeThis procedure enables you to delete objects from the Radio Network database.

Before you startTo perform this operation you need to be authorized and have RNWCMManagement-manage permissions.

Steps


2 Browse the Topology and select managed object or RNC.Further informationIf you selected RNC please note that if this RNC is connected to OMS, you will not be able to delete it from topology.

3 Select Delete from context menu or Remove from Topology for RNC.Expected outcomeDelete pop up appears asking you to confirm the operation. If you want to cancel dele-tion, click No button. You cannot delete real working and connected RNC from topology.

Further informationIf the object cannot be deleted from the topology or you did not select an object but for example object group, the Delete option will be inactive in context menu.

4 Click Yes button to confirm the operation.Expected outcomeDelete from topology request is sent and status of the operation is shown in Feedback pane. When it is finished, the object is removed from topology database.

18 DN03471515


Id:0900d80580a4e7d6Confidential

Basic operations for managed objects

5 Basic operations for managed objects

5.1 RNC objectPurposeRadio Network Controller (RNC) object refers to the type of parameters of the logical object of RNC.

There is only one RNC object. That object is a network topology object.The RNC object is created during the commissioning phase. The RNC object needs to be created first, and after that the child objects of the RNC can be created. The RNC object defines for example OMS IP address with which the RNC establishes an O&M connection. The RNC managed object contains RNC level parameters, that is:

commissioning parameters system Information parameters Radio network configuration management objects Location Services (LCS) Time of Arrival Window Endpoint (TOAWE) related parameters Time of Arrival Window Startpoint (TOAWS) related parameters.This procedure enables you to create, edit, or delete a RNC object.

Before you startYou can create objects only under selected RNC.

For information on IPA-RNC parameters, see WCDMA Radio Network Configuration Parameters.

For information on mcRNC parameters, see Multicontroller Radio Network Configura-tion Parameters.

Steps

1 Create RNC object.For IPA-RNC, see Configuring the RNC object for IPA-RNC for the first time.

For multicontroller RNC, see Configuring the RNC object for multicontroller RNC for the first time.

2 Edit RNC object.See Editing object parameters

3 Delete RNC object.Deleting RNC object is not allowed. OMS Element Manager denies the operation.

DN03471515 19


Id:0900d80580a4e82cConfidential

5.2 RNAC objectPurposeRadio Network Admission Control (RNAC) object is an RNC level managed object.RNAC object maintains:

admission control parameters Packet Data Convergence Protocol (PDCP) power control/ balancing/ allocation related parameters. This procedure enables you to create, edit, or delete a RNAC object.

g Only one RNAC object can be created.Before you startYou can create objects only under selected RNC.



Steps

1 Create RNAC object.See Creating objects in database

2 Edit RNAC object.See Editing object parameters

3 Delete RNAC object.Deleting RNAC object is not allowed. OMS Element Manager denies the operation.

20 DN03471515


Id:0900d80580a4e840Confidential

5.3 RNPS objectPurposeRadio Network Packet Scheduler (RNPS) object is an RNC level managed object.RNPS object that maintains mandatory:

Packet Scheduler parameters Dynamic Link Optimization related parameter.This procedure enables you to create, edit, or delete a RNPS object.

g Only one RNPS object can be created.Before you startYou can create objects only under selected RNC.



Steps

1 Create RNPS object.See Creating objects in database

2 Edit RNPS object.See Editing object parameters

3 Delete RNPS object.Deleting RNPS object is not allowed. OMS Element Manager denies the operation.

DN03471515 21



5.4 RNHSPA objectPurposeRadio Network High Speed Packet Access (RNHSPA) object is an RNC level man-agedobject. RNHSPA object maintains High Speed Packet Access related parameters, such as:

High Speed Packet Access (HSPA) High Speed Uplink Packet Access (HSUPA) Continuous Packet Connectivity (CPC) Fractional Dedicated Physical Channel (F-DPCH).This procedure enables you to create, edit, or delete a RNHSPA object.

g Only one RNHSPA object can be created.Before you startYou can create objects only under selected RNC.



Steps

1 Create RNHSPA object.See Creating objects in database

2 Edit RNHSPA object.See Editing object parameters

3 Delete RNHSPA object.Deleting RNHSPA object is not allowed. OMS Element Manager denies the operation.

22 DN03471515



5.5 RNRLC objectPurposeRadio Network Radio Link Control (RNRLC) object is an RNC level managed object.RNRLC object maintains Radio Link Control parameters.

This procedure enables you to create, edit, or delete a RNRLC object.

g Only one RNRLC object can be created.Before you startYou can create objects only under selected RNC.



Steps

1 Create RNRLC object.See Creating objects in database

2 Edit RNRLC object.See Editing object parameters

3 Delete RNRLC object.Deleting RNRLC object is not allowed. OMS Element Manager denies the operation.

DN03471515 23



5.6 RNTRM objectPurposeRadio Network Transmission (RNTRM) object is an RNC level managed object. RNTRM object maintains transmission parameters.

This procedure enables you to create, edit, or delete a RNTRM object.

g Only one RNTRM object can be created.Before you startYou can create objects only under selected RNC.



Steps

1 Create RNTRM object.See Creating objects in database

2 Edit RNTRM object.See Editing object parameters

3 Delete RNTRM object.Deleting RNTRM object is not allowed. OMS Element Manager denies the operation.

24 DN03471515



5.7 RNMOBI objectPurposeRadio Network MOBIlity (RNMOBI) object is an RNC level managed object. RNMOBI object maintains mobility management parameters:

handover compressed mode mobile device control related.This procedure enables you to create, edit, or delete a RNMOBI object.

g Only one RNMOBI object can be created.Before you startYou can create objects only under selected RNC.



Steps

1 Create RNMOBI object.See Creating objects in database

2 Edit RNMOBI object.See Editing object parameters

3 Delete RNMOBI object.Deleting RNMOBI object is not allowed. OMS Element Manager denies the operation.

DN03471515 25


Id:0900d80580a4e84aConfidential

5.8 RNFC objectPurposeRadio Network Feature Control (RNFC) object is an RNC level managed object. RNFC object maintains RNC level feature control parameters.

This procedure enables you to create, edit, or delete a RNFC object.

g Only one RNFC object can be created.Before you startYou can create objects only under selected RNC.



Steps

1 Create RNFC object.See Creating objects in database

2 Edit RNFC object.See Editing object parameters

3 Delete RNFC object.Deleting RNFC object is not allowed. OMS Element Manager denies the operation.

26 DN03471515



5.9 RNCERM objectPurposeRadio Network Centralized Entity Resource Management (RNCERM) object defines the parameters needed to implement the mechanism to balance the BTS load between CSCP(s). The load control parameters define data related to the following:

list of BTSs ID that are not allowed to be selected for BTS resource re-balancing high threshold for CSCP CPU load maximum number of BTSs that are allowed to be selected for BTS resource re-bal-

ancing maximum number of AMR calls could be dropped in one BTS, while performing the

selective BTS resource re-balancing time period for CSCP/BTS load measurement cycle threshold for the ratio of the number of overloaded time slots to total number of time

slots in load measurement period

See RAN2591: Selective BTS Resource Re-Balancing in mcRNC for more information.

This procedure enables you to create, edit, or delete an RNCERMobject.


g Applicable only to the multicontroller RNC.For information on mcRNC parameters, see Multicontroller Radio Network Configura-tion Parameters.

Steps

1 Create RNCERM object.See Creating objects in database

2 Edit RNCERM object.See Editing object parameters

3 Delete RNCERM object.

g If rebalancing start operation is ongoing, deletion is not allowed.See Deleting objects from database

DN03471515 27



5.10 IUO objectPurposeIU Operator (IUO) object maintains data related to the Iu Operator (for example, PLMN identity, Shared area PLMN identity).

This procedure enables you to create, edit, or delete a IUO object.




g If the IMSI-based handover is in use, you need to configure up to four Shared Area PLMN IDs per IUO object.Steps

1 Create IUO object.See Creating objects in database

2 Edit IUO object.See Editing object parameters

3 Delete IUO object.See Deleting objects from database

28 DN03471515



5.11 IPQM objectPurposeIP QoS Measurement (IPQM) object is used in configuring the:

IP based Iu-PS features IP based Iu-CS featuresThe IPQM object defines the UMTS traffic class to DSCP mapping to be used for the IP connections at the Iu interface. IPQM reference needs to be given in the CN definitions if the IP transport is used at the interface towards the corresponding CN element.

This procedure enables you to create an IPQM object.

For more information and IPQM parameters, see RAN75: IP Based Iu-CS and RAN750: IP Based Iu-PS in WCDMA RAN, Rel. RU10, Feature Descriptions.




Steps

1 Create IPQM object.See Creating objects in database

2 Edit IPQM object.See Editing object parameters

3 Delete IPQM object.

g The IPQM object cannot be deleted if the object is related to any IUCS/IUPS object.See Deleting objects from database

DN03471515 29


Id:0900d80580a4e85eConfidential

5.12 IUCS objectPurposeIUCS interface (IUCS) object contains control and status parameters needed to estab-lish and maintain connection towards MGW.

This procedure enables you to create, edit, or delete a IUCS object.

Before you startATM and IP transmission configuration towards MGW must be created first. See Signal-ling Transport over IP (M3UA) and Activating IP based Iu-CS in Activating RAN75 and RAN750: IP based Iu-CS and IP based Iu-PS. It is possible to create IUCS object without creating underlying transmission configuration but the connection shall not be functional before the necessary transmission configuration actions in RNC have been done.

g If the Nokia multi-operator RAN feature is in use, you have to create and configure one IUCS object per operator.You need to be authorized to perform this operation. You can create objects only under selected RNC.



Steps

1 Create IUCS object.See Creating objects in database

2 Edit IUCS object.See Editing object parameters

3 Delete IUCS object.

g The IUCS object cannot be deleted, if the object is related to any WCEL object.

g If there is an IUPS object with the same PLMN id, delete IUPS object first.See Deleting objects from database

5.12.1 IUCSIP object

PurposeDestination IP address list for IUCS (IUCSIP) object contains the destination IP address list for the IUCS object. IUCSIP is used to configure how IUCS user plane address received from the CN is mapped to the IP-based route configured in the RNC.

30 DN03471515



This procedure enables you to create, edit, or delete a IUCSIP object.

Before you startYou can create objects only under selected IUCS.

Steps

1 Create IUCSIP object.See Creating objects in database

2 Edit IUCSIP object.See Editing object parameters

3 Delete IUCSIP object.See Deleting objects from database

DN03471515 31



5.13 IUPS objectPurposeIUPS interface (IUPS) object contain control and status parameters needed to establish and maintain connection towards SGSN.

This procedure enables you to create, edit, or delete a IUPS object.




Steps

1 Create IUPS object.See Creating objects in database

2 Edit IUPS object.See Editing object parameters

3 Delete IUPS object.

g The IUPS object cannot be deleted, if the object is related to any WCEL object.See Deleting objects from database

5.13.1 IUPSIP object

PurposeDestination IP address list for IUPS (IUPSIP) object contains the destination IP address list for the IUPS object. IUPSIP is used to configure the way that the Iu-PS user plane address received from the CN is mapped to IP-based route configured in the RNC.

This procedure enables you to create, edit, or delete a IUPSIP object.

Before you startYou can create objects only under selected IUPS object.

Steps

1 Create IUPSIP object.See Creating objects in database

2 Edit IUPSIP object.See Editing object parameters

32 DN03471515



3 Delete IUPSIP object.See Deleting objects from database

DN03471515 33



5.14 CBCI objectPurposeCell Broadcast Center (CBCI) object maintains the data related to the cell broadcast center used in the service area broadcast feature. The CBCI object is used for configur-ing the Iu-BC interface.

This procedure enables you to create, edit, or delete a CBCI object.

Before you startYou need to be authorized to perform this operation. You can create objects only under selected RNC.

g You can configure CBCI parameters only if Service Area Broadcast Protocol (SABP) is in use.g If several operators share an RNC, each operator needs to configure its own cell broad-cast centres (CBC). With MORAN, the operator may create up to four CBCI objects.

SAB cannot be used with MOCN.

g If the IMSI-based handover is in use, you need to configure corresponding IUO object with Shared Area PLMN IDs.For information on IPA-RNC parameters, see WCDMA Radio Network Configuration Parameters.


Steps

1 Create CBCI object.See Creating objects in database

2 Edit CBCI object.See Editing object parameters

3 Delete CBCI object.See Deleting objects from database

34 DN03471515



5.15 IUR objectPurposeIUR interface (IUR) object contains neighboring RNC-related parameters. The IUR object is used for establishing connection from an RNC to a neighboring RNC.The maximum number of IUR managed objects in RNC is 32. When the type of the neigh-boring element is defined as I-HSPA Adapter - when feature RAN1759: Support for I-HSPA sharing and Iur mobility enhancements is activated, the maximum number of Iur interfaces increases to 300.

This procedure enables you to create, edit, or delete an IUR object.

Before you startATM and IP transmission configuration towards neighbor RNC must be created first. See Activating RAN76: IP based Iur. It is possible to create IUR object without creating underlying transmission configuration but the connection shall not be functional before the necessary transmission configuration actions in RNC have been done.



You can create objects only under selected RNC.

Steps

1 Create IUR object.See Creating objects in database

2 Edit IUR object.See Editing object parameters

3 Delete IUR object.See Deleting objects from database

DN03471515 35



5.16 CMOB objectPurposeCongestion Management OBject (CMOB) contains radio network parameters used in traffic restriction. Traffic restriction is introduced in the optional feature RAN1128: Dynamic Access Class Restriction, which means that this object is optional as well. One CMOB object contains parameters for one restriction area. One WCDMA cell can be connected up to three restriction areas, which must be of different types (CS-DSAC, PSDSAC and RNAR). The maximum number of CMOB objects under one RNC is 13.If feature RAN801: Radio Network Access Regulation Function is enabled in the RNC, the RNC creates three 'forced' CMOB objects during the RNC startup or during the RNC object creation.An optional CMOB allows its parameters to be utilized in WCDMA cell definitions.

RNW CM supports limiting access rights to the network (allowed/restricted) broadcastto all user equipment (UE) in the system information message on an access level basis.In a normal situation, the network access is allowed for all access levels. If network access needs to be limited because of the aforementioned reasons, the operator can activate the access control algorithm, which allows and restricts the network access of access levels 0 to 9 users at predefined intervals.

An optional CMOB allows its parameters to be utilized in WCDMA cell definitions.

This procedure enables you to create, edit, or delete a CMOB object.

Before you startThe CMOB object can be created only when feature RAN801: Radio Network Access Regulation Function has been installed in RNC.




Steps

1 Create CMOB object.See Creating objects in database

2 Edit CMOB object.See Editing object parameters

3 Delete CMOB object.

g The CMOB objects 1 ... 3 which are used by the system cannot be deleted.

g If any CMOB object is used in a WCEL, deletion is not allowedSee Deleting objects from database

36 DN03471515



5.17 COCO objectPurposeCOnnection COnfiguration (COCO) object reserves local ATM transmission resources for WCDMA BTS (WBTS). The COCO object displays the transmission resources in the Iub interface but not the actual network topology.This procedure enables you to create, edit, or delete a COCO object.

g Applicable to IPA-RNC only.IPNB (IP Node-B) and COCO objects are alternative to each other, and only one can be used to connect to a certain WBTS.

For information Dual Iub, see RAN1449: Dual Iub for Flexi WCDMA BTS in WCDMA RAN, Rel. RU10, Feature Descriptions.

g It is possible to create a COCO without relating it to a WBTS. In such a case, only the ATM layer is configured.This procedure enables you to create, edit, or delete a COCO object.

Before you startThe ATM interface should be created along with an access profile. For information on creating the ATM resources, see Creating ATM resources in RNC.



Steps

1 Create COCO object.See Creating objects in database

a) In Parameter Editor, set the following parameters: identifier for the COCO (Connection Configuration ID) ATM interface identifier (Interface ID) virtual path identifier (VPI)

The data is sent to the RNC RNW database. The data is stored in the RNC RNW database and the ATM layer is created into the system. Control and user plane-related resources are created into the system if the COCO object was related to the WBTS.

The COCO object and the corresponding ATM layer configuration is found in the system. If the COCO creation was successful and the WBTS that the user wanted to relate to the COCO was found, the system relates the COCO and the WBTS objects.

The WBTS object does not have to be created before the COCO object is created. Also when the WBTS object is created afterwards, the system relates the objects to each other in the same way that it does if the WBTS already exists when the COCO object is created. Once the COCO and the WBTS have been related in the RNC RNW database, the Control/User plane configuration is done.

g If the ATM layer is created using IPA-RNC (not applicable for mcRNC) with MML com-mands, make sure that the administrative state of the VP/VC Link termination points is

DN03471515 37



unlocked. The usage information of the related ATM termination points should be free. If you use the automatic ATM configuration option, the termination points are created unlocked by default.

For further information, see Creating ATM resources in RNC and Digit analysis and routing in RNC.

2 Edit COCO object.See Editing object parameters

3 Delete COCO object.See Deleting objects from database

38 DN03471515



5.18 IPNB objectPurposeIP Node-B (IPNB) object contains the NBAP link configuration for the WBTS with the IP based Iub interface. IPNB and COCO objects are alternative to each other, and only one can be used to connect to a certain WBTS. The maximum number of radio network IPNB objects in the RNW database follows the number of the supported BTSs under the RNC.

This procedure enables you to create, edit, or delete a IPNB object.

Before you startCreate the IPQM object if not created already. For more information, see Creating IPQM object.




Steps

1 Create IPNB object.See Creating objects in database

a) Give BTS IP as a Destination Address.b) In the DNBAP list enter '1' for the Communication Control Port identifier.c) Enter the minimum SCTP port.d) The NBAP DSCP default value is 34.For information on parameters, see RAN74: IP based Iub for Flexi WCDMA BTS in WCDMA RAN, Rel. RU10, Feature Descriptions and WCDMA radio network configura-tion parameters.

2 Edit IPNB object.See Editing object parameters

3 Delete IPNB object.See Deleting objects from database

DN03471515 39



5.19 FMC objectPurposeFrequency Measurement Control (FMC) object (FMCS, FMCI, FMCG (optional)) allows its parameters to be utilized in WCDMA cell definitions.

FMCS - object for intra-frequency measurement control FMCI - object for inter-frequency measurement control FMCG - object for inter-system frequency measurement control (optional)FMCobject contains information concerning the frequency measurement functionality of the RNC. A logical FMC object is created so that its parameters can be used in WCDMA cell definitions. One FMC can be related to several WCDMA cells. FMC objects must be created before they can be used by WCELs.

This procedure enables you to create, edit, or delete a FMCx object.




Steps

1 Create FMCx object.See Creating objects in database

2 Edit FMCx object.See Editing object parameters

3 Delete FMCx object.

g If an FMC object is used in a WCEL or VCEL, deletion is not allowed.See Deleting objects from database

40 DN03471515



5.20 HOP objectPurposeHandOver Path (HOP) object stores the values used in handover and call drop decision making. A logical handover path object (HOPS, HOPI, HOPG (optional), HOPL(optional)) allows its parameters to be utilized in adjacent WCDMA cell definitions.

HOPS - object for intra-frequency HOP, which contains, for example, parameters that affect hard handover decision and call drop decision procedures

HOPI - object for inter-frequency handover path HOPG - object for inter-system handover path (optional) HOPL - object for inter-system handover path to LTE network (optional)This procedure enables you to create, edit, or delete a HOPx object.




Steps

1 Create HOPx object.See Creating objects in database

2 Edit HOPx object.See Editing object parameters

3 Delete HOPx object.

g If a HOPobject is used in an adjacency or VCEL, deletion is not allowed.See Deleting objects from database

DN03471515 41



5.21 TQM objectPurposeTransport QoS Management (TQM) object implements the Transport Network Layer (TNL) QoS differentiation mapping function based on the Radio Network Layer (RNL) traffic prioritization strategy. With the ATM transport the AAL2 Path Type and the AAL2 priority information is configured based on the RNL RAB characteristics and the air inter-face channel type. With the IP transport the DSCP mapping is provided. The mapping information is utilized at the UTRAN transport bearer establishment for the given RAB.

The configurable transport layer differentiation applies for the following transport bearers:

Common channels (FACH, RACH, PCH) Signalling Radio Bearer (SRB / DCCH over DCH) CS traffic (AMR, CS-T data, CS-NT data) Packet data connections with the R99 DCH, E-DCH and HS-DSCHTQM object also contains the Activity Factor transport layer Connection Admission Control (CAC) reservation scaling attributes. The CAC reservations for the Streaming HSPA and Nominal Bit Rate (NBR) bearers can be scaled with QoSPriority (HSPA SPI) basis.

This procedure enables you to create, edit, or delete a TQM object.

Before you startRAN1253: Iub Transport QoS license needs to be active. For more information on the TQM object, see RAN1253: Iub Transport QoS in WCDMA RAN, Rel. RU10, Feature Descriptions.




Steps

1 Create TQM object.See Creating objects in database

2 Edit TQM object.See Editing object parameters

3 Delete TQM object.

g If TQM object is related to any WBTS object, deletion is not allowed.See Deleting objects from database

42 DN03471515



5.22 WRAB objectPurposeWCDMA Radio Access Bearer (WRAB) object contains connection-based quality control parameters. The parameters define the service bearer and signaling bearer quality targets and the related power control thresholds for each transport channel con-figuration.

This procedure enables you to create, edit, or delete a WRAB object.




Steps

1 Create WRAB object.See Creating objects in database

2 Edit WRAB object.See Editing object parameters

3 Delete WRAB object.

g If any WRAB object is associated with any WCELs or VCELs, deletion is not allowed.See Deleting objects from database

DN03471515 43



5.23 WAC objectPurposeWCEL Admission Control (WAC) object serves for storing:

cell-specific UL load control parameters admission control parameters several state transition control parametersin RNW database of an RNC. Cell-based tuning helps to better cope with high UL load, which is especially useful in case of mass-events when cell load tends to be very high. Operators can also manage state transitions differently in various frequency bands. Operator can configure 20 WAC objects which include different sets of load control AC and several state transition control parameters.

Each of WCELs or a VCEL can be associated with the selected WAC object.

This procedure enables you to create a WAC object.




Steps

1 Create WAC object.See Creating objects in database

2 Edit WAC object.See Editing object parameters

3 Delete WAC object.

g If WAC object is associated with any WCELs or VCEL, deletion is not allowed.See Deleting objects from database

44 DN03471515



5.24 PFL objectPurposePreferred Frequency Layer (PFL) object defines preferred frequency layers for differ-ent UE capability and service combinations (for example, HSDPA capable UE with NRT service).

This procedure enables you to create, edit, or delete a PFL object.

Before you startThe PFL object can be created only when feature RAN2172: Multi-Band Load Balancing has been installed in the RNC. PFL object is under RNC object.




Steps

1 Create PFL object.See Creating objects in database

2 Edit PFL object.See Editing object parameters

3 Delete PFL object.

g If PFL object is associated with any WCEL, deletion is not allowed.See Deleting objects from database

DN03471515 45



5.25 PREBTS objectPurposePREdefined BTS (PREBTS) object supports BTS autoconnection functionality. The PREBTS object contains all the parameters needed for autoconnection. It optimizes the visibility of autoconnection parameters and provides more flexibility to introduce param-eter level checks.When the BTS connects to the RNC by sending DHCP request, it indi-cates its hardware ID and the RNC uses that as a search key for PREBTS objects to find out the final BTS ID to be given for the BTS.

g Applicable to IPA-RNC only.This procedure enables you to create, edit, or delete a PREBTS object.

Before you startThe PREBTS object can be created only when feature RAN1298: BTS Autoconnection has been installed in the RNC. The PREBTS object is under the RNC object.



Steps

1 Create PREBTS object.See Creating objects in database

2 Edit PREBTS object.See Editing object parameters

3 Delete PREBTS object.See Deleting objects from database

46 DN03471515



5.26 VBTS sitePurposeVirtual WCDMA BTS (VBTS) object manages a virtual WCDMA BTS site and increases the system capacity. The common configuration for all WCDMA and I-HSPA BTSs is controlled by neighboring network elements.

This procedure enables you to create, edit, or delete a VBTS object.

Before you startThis object is mandatory when RAN1231 HSPA-over-Iur or RAN1824: Inter-frequency Handover over Iur feature is used.




Steps

1 Create VBTS object.See Creating objects in database

2 Edit VBTS object.See Editing object parameters

3 Delete VBTS object.See Deleting objects from database

f If you delete a VBTS object, all objects created underneath will also be deleted.

5.26.1 VCEL object

PurposeVirtual WCDMA Cell (VCEL) changes the configuration of the Virtual WCDMA BTS (VBTS) site.The common configuration for all WCDMA and I-HSPA cells is controlled by neighboring network elements.

Before you startOnly one instance of the VCEL object is allowed under one VBTS object.This object is mandatory when RAN1231 HSPA-over-Iur or RAN1824: Inter-frequency Handover over Iur feature is used.

HOPS, FMCS, WRAB objects must be created before a VCEL is created.

You can create objects only under selected VBTS.

DN03471515 47



Steps

1 Create VCEL object.See Creating objects in database

2 Edit VCEL object.See Editing object parameters

3 Delete VCEL object.See Deleting objects from database

48 DN03471515



5.27 WBTS sitePurposeWCDMA BTS (WBTS) is the logical object of the WCDMA base station.A logical WBTS object is created to manage a BTS-related telecom and radio resource configuration of a physical WCDMA BTS (WBTS) site and to increases the system capacity.

A WBTS can host 24 WCDMA cells.

Depending on the transport technology used for the WBTS (ATM or IP), either COCO objects (ATM transport) or IPNB objects (IP transport) can be related to the WBTS object.

It is possible to create a WBTS without a reference to any COCO objects when the WBTS is not yet integrated to the RNC (IPA-RNC only).

For more information, see ATM-based Iub link configuration.

For the current maximum number of WBTSs, see the following documents:

For RNC196, the maximum number of WBTSs is 384 in the basic configuration, but if the optional feature RAN607: Connectivity Support for 512 BTSs is enabled, the maximum number of the WBTSs is 512.

For RNC450, the maximum number of WBTSs that can be configured by the operator depends on the availability of feature RAN1623: Carrier Connectivity Optimised RNC450. For more information on that feature, see RAN1623: Carrier Connectivity Opti-mised RNC450 in WCDMA RAN System, Rel. RAS06, Feature Descriptions.

For RNC2600 the maximum number of WBTSs is 1600 with the RU20 feature RAN1795 RNC2600 coverage optimized solution. For more information on license-controlled capacity, see RAN1198: RNC2600 SW License Key Controlled Capacity in WCDMA RAN, Rel. RU10, Feature Descriptions.

Before you startCreating a WCDMA BTS site using system defaults refers to a range of predefined values which are used in order to speed up the WBTS creation procedure. You still have to fill in identification information for the WCDMA BTS and other required parameters for which there are no default values. You are not limited to default values; once a param-eter has been given a default value, you can change it if necessary.

g The logical objects in the RNC RNW database are hierarchically related to each other, and the hierarchy dictates the order in which it is possible to create new objects. WCEL objects are always created under a certain WBTS object, never independently. However, you do not have to create all WCEL objects that should belong to a WBTS at once; it is possible to change the configuration at a later stage, for example by adding WCEL objects to a WBTS object.

g At least one HOPS, FMCS, WRAB, and IUCS object has to be created in advance, if WCDMA cells are created in the WBTS creation procedure.You can create objects only under selected RNC.


DN03471515 49




Steps

1 Create WBTS site.Select Create New Object > WBTS from the context menu.

OrAlternatively, the WBTS can be created using an existing WBTS as reference.

a) Select the WBTS whose parameters should be used in the new WBTS.b) Select WBTS > Use as Reference to Create New Object

g Identify the transmission resources by giving the desired COCO or IPNB identification or the ATM interface/VPI/C-NBAP VCI triplet. If a COCO or IPNB object is found in the system, the WBTS is connected to it during the creation procedure. COCO or IPNB object can also be created later on and the reference can also be left empty.

The COCO object is created for the Iub connections with ATM transport or with RAN1449: Dual Iub feature configuration. With full IP based Iub (RAN74 IP Based Iub for Flexi WCDMA BTS or RAN1634 IP Based Iub for UltraSite WCDMA BTS) the IPNB object needs to be created. Either COCO or IPNB can be related to the WBTS.

See Creating objects in database

2 Edit WBTS site.See Editing object parameters

3 Delete WBTS site.See Deleting objects from database

f If you delete a WBTS object, all objects created underneath will also be deleted.

5.27.1 WCEL object

PurposeWCDMA Cell (WCEL) is the logical object of the WCDMA cell. A logical cell object is created to define the configuration of the WCDMA BTS site.

The following Radio network configuration management objects have to be created before creating WCELs:

a parent WBTS IUCS (CS CN node to be used) IUPS (PS CN node to be used) FMCSs for RT and NRT traffic (also FMCI/FMCG if needed) WRABFor the current maximum number of WCDMA cells, see the following documents:

50 DN03471515



For RNC196, the maximum number of the WCDMA cells that can be configured by the operator is 1152. For the number of operational cells, see WCDMA RNC Product Description for RNC196

For RNC450, the maximum number of WCDMA cells that can be configured by the operator depends on the availability of feature RAN1623: Carrier Connectivity Opti-mised RNC450. For more information, see RAN1623: Carrier Connectivity Optimised RNC450 in WCDMA RAN System, Rel. RAS06, Feature Descriptions.

For RNC2600, the maximum number of WCDMA cells that can be configured by the operator is 4800 due to RAN1795: RNC 2600 coverage optimized solution. The real allowed maximum count of working WCDMA cells is dependent on both RNC HW con-figuration and capacity licenses.

For more information on license-controlled capacity, see RAN1198: RNC2600 SW License Key Controlled Capacity in WCDMA RAN, Rel. RU10, Feature Descriptions.

Before you startWCEL objects can only be created under a WBTS. The WCDMA cell remains locked and is not used in active traffic until you have changed its state to unlocked.

To unlock the WCEL, perform the following:

Find the WCEL object in Topology Tree (RNC > WBTS > WCEL), right click it and select Administrative State Change - Unlock Cell

Find the WCEL object in WCELs Overview Page (Home tab), right click it and select Administrative State Change - Unlock Cell

IUCS, WRAB, and FMC objects must be created before a WCEL is created.

You can create objects only under selected WBTS.

Steps

1 Create WCEL object.Select WBTS > Create New Object > WCEL from the context menu.

OrAlternatively, the WCEL can be created using an existing WCEL as reference.

a) Select the WCEL whose parameters should be used in the new cell.b) Select WCEL > Use as Reference to Create New Object.See Creating objects in database

2 Edit WCEL object.See Editing object parameters

3 Delete WCEL object.See Deleting objects from database

DN03471515 51



5.27.1.1 Adjacency (ADJx) for a WCDMA cell

PurposeAn ADJacency for a WCDMA cell (ADJx) refers to a handover relationship between two WCDMA cells.

Logical adjacency object [ADJS/ADJD/ADJI/ADJG/ADJL] for WCDMA cell is created to define a new neighboring cell.

Adjacencies for cells controlled by the same RNC are called internal adjacencies. External adjacencies refer to adjacency relationships between cells controlled by differ-ent RNCs.

Depending on the type of cells for which this relationship is defined, there are three dif-ferent types of adjacencies:

ADJS - object for intra-frequency adjacency ADJD - object for additional intra-frequency adjacency ADJI - object for inter-frequency adjacency ADJG - object for inter-system adjacency (optional) ADJL - object for inter-system adjacency to LTE networkBefore you startHandover path objects must be created before they can be used by ADJx objects.

You can create objects only under selected WCEL.The ADJG object can only act as an external adjacency.The ADJD object can only be configured when feature RAN1266: Soft Handover Based on Detected Set Reporting has been installed. Additional intra-fre-quency adjacencies (ADJDs) cannot be included in the system information mes-sages.HSDPA HOPS for AMR multi-service can be specified only if RAN827: HSDPA with Simultaneous AMR Voice Call feature is activated.The ADJL object can only be configured when feature RAN2067: LTE interworking has been installed. Prior to ADJL object creation, at least one HOPL object must be created.

In consequence of the 3GPP limitation in sending neighbor cell information in system information block (SIB) type 11, 11bis, and 12 the total amount of adjacencies that can be configured is lower than the amount of ADJx objects. Therefore configuring too many ADJx objects may exceed the size of SIB11 and thus cause a cell to get blocked. See feature description RAN1323: Extension of SIB11 (SIB11bis).

SIB11, SIB11bis, and SIB12 messages can contain information on a maximum of 96 cells, but the physical size of SIB data (no more than 3552 bits) has capacity only for 47 cells when all optional information elements in SIB11 are in use and 35 cells if HCS is used. HCS is controlled with the useofHCS parameter.3GPP R6 introduces System Information Block type 11bis (SIB11bis) which provides extension segment for SIB11. SIB11bis doubles the maximum number of neighbor cells in the SIB from 47/35 to 94/70 cells without/with HCS respectively.

If the system information data exceeds 3552 bits, the scheduling of the system informa-tion blocks fails. The cell is blocked by the system and alarm 7771 WCDMA CELL OUT OF USE (BCCH scheduling error) is reported for the cell.HSDPA HOPS for AMR multi-service can be specified only if RAN827: HSDPA with Simultaneous AMR Voice Call feature is activated.

52 DN03471515



Steps

1 Create ADJx object.Select WBTS > WCEL > ADJS/ADJI/ADJG/ADJD/ADJL from the context menu.

See Creating objects in database

Steps (internal adjacency)

a Select the target WCDMA cell from the Available cells list.Target UTRAN cell identity and other target cell related parameters are automati-cally defined. You can also insert Target UTRAN Cell identity of the target cell as well as identification parameters for the RNC manually.

b Specify handover paths for real time, non-real time, HSDPA and HSDPA for AMR multi-services separately.

g HSDPA HOPS for AMR multi-service can be specified only if RAN827: HSDPA with Simultaneous AMR Voice Call feature is activated.c Specify handover paths.d Specify whether the adjacency should be included in the system information

messages or not.All adjacent cells are used in measurement control even if the adjacency is not included in the system information.

g Additional intra-frequency adjacencies (ADJDs) cannot be included in the system information messages.Steps (external adjacency)

e Insert the Target Cell identity of the target cell as well as identification param-eters for the external RNC manually.

f For external adjacencies, define only the outgoing adjacencies.g Specify handover paths.

g HSDPA HOPS for AMR multi-service can be specified only if RAN827: HSDPA with Simultaneous AMR Voice Call feature is activated.h Specify whether the adjacency should be included in the system information

messages or not.All adjacent cells are used in measurement control even if the adjacency is not included in the system information.

g Additional intra-frequency adjacencies (ADJDs) cannot be included in the system information messages.

2 Edit ADJx object.See Editing object parameters

DN03471515 53



3 Delete ADJx object.See Deleting objects from database

54 DN03471515



5.28 WSMLC objectPurposeWCDMA Serving Mobile Location Centre (WSMLC) object contains general purpose parameters used in the positioning methods. The actual SMLC device does not exist, but the SMLC functionality in the Interface Control and Signaling Unit (ICSU) is config-ured using WSMLC parameters. In the RNW database, there can be only one WSMLC object. WSLMC objects, just as WLCSE object can only be created if feature RAN2.0041: LCS Cell Coverage Based (RTT) with Geographical Coordinates is sup-ported.

For more information, see LCS Cell Coverage Based (RTT) with Geographical Coor-dinates in /LCS/.

WSMLC object is also linked to the following features:

RAN223: UE Based A-GPS Using External Reference Network RAN815: Point-to-Point Iupc Interface RAN875: Network Based A-GPS Using External Reference Network.This procedure enables you to create, edit, or delete a WSMLC object.




Steps

1 Create WSMLC object.See Creating objects in database

2 Edit WSMLC object.See Editing object parameters

3 Delete WSMLC object.If WLCSE object is created, WSMLC deletion is not allowed.

See Deleting objects from database

DN03471515 55



5.29 WLCSE objectPurposeWCDMA Location Services Entity (WLCSE) object defines WCEL-related parameters needed by location algorithms.

In the RNW database, there can be a total of 8000 WLCSE objects, of which 4800 are for the RNCs own cells and 3200 for the neighboring RNCs' cells.WLCSE objects, just as WSLMC ones can only be created if feature RAN2.0041: LCS - Cell Coverage Based (RTT) with Geographical Coordinates is supported.For more information, see LCS Cell Coverage Based (RTT) with Geographical Coordinates in /LCS/.

This procedure enables you to create, edit, or delete a WLCSE object.

Before you start

g The WSMLC object has to be created before the WLCSE can be created.You can create objects only under selected RNC.

The WLCSE parameters must be defined for each cell used in location calculation in the RNC.The parameters must also be defined for cells controlled by the neighboring RNCs used in location calculation in the locating RNC.A WLCSE object in a WLCSE object col-lection is identified by using the UTRAN cell identifier, which must be unique in the RNC (in the RNW database).



Steps

1 Create WLCSE object.See Creating objects in database

2 Edit WLCSE object.See Editing object parameters

3 Delete WLCSE object.See Deleting objects from database

56 DN03471515



5.30 WANE objectPurposeWCDMA Authorized Network (WANE) object is created to authorize WCDMA networks for RAN2.0060: IMSI Based Handover. WANE is a group of authorized networks which are considered equal to the home network of the subscriber. A WANE object contains parameters used in IMSI-based handover, which is an optional feature.

This procedure enables you to create, edit, or delete a WANE object.

Before you startThe WANE object belongs to IMSI-based handover.




Steps

1 Create WANE object.See Creating objects in database

2 Edit WANE object.See Editing object parameters

3 Delete WANE object.All WSG objects under related WANE should be deleted before deleting a WANE object.

See Deleting objects from database

DN03471515 57



5.31 WSG objectPurposeWCDMA Subscriber Group (WSG) object belongs to IMSI-based handover. WSG object identifies the subscriber group for the IMSI-based handover feature. WSG objects can only be created if feature RAN2.0060: IMSI Based Handover is supported.

This procedure enables you to create, edit, or delete a WSG object.

Before you startThe WANE (WCDMA authorized network) object must be created before creating the WSG object.




Steps

1 Create WSG object.See Creating objects in database

2 Edit WSG object.See Editing object parameters

3 Delete WSG object.See Deleting objects from database

58 DN03471515


Id:0900d80580a1cab2Confidential

Special operations

6 Special operations

6.1 Locking or unlocking WCELPurposeThis procedure enables you to lock or unlock WCEL.

Before you startYou need to be authorized to perform this operation. This is possible only for WCEL objects.

Steps


2 Browse the Topology Tree and select RNC or WBTS object.Expected outcomeThe WCELs Overview Page button becomes active.

3 Click WCELs Overview Page button or select Show Overview Page > WCELs from the context menu.

Expected outcomeThe WCELs Overview Page application loads to a new tab and lists all WCELs under selected RNC or WBTS.

4 Select one or more WCEL objects (to select several WCELs use CTRL or SHIFT key or select Select All from the context menu).

Expected outcomeRows with selected WCELs change their color.

g Note that the table rows have two colors to make them easier to read. Selecting WCEL changes selected rows color to another (third) one.Further informationFor more information about opening Overview pages, see Viewing WCELs Overview page.

You can also change WCELs state directly from Topology by selecting State Change option from the context menu.

DN03471515 59

Administering WCDMA Radio Networks Special operations

Id:0900d80580a1cab2Confidential

5 Select Administrative State Change > Lock Cell or Unlock Cell from the context menu.

Expected outcomeAn Administrative State Change pop up window appears. If you want to cancel admin-istrative state change operation, click No.

6 Select Yes to confirm the action.Expected outcomeThe state change request is sent and the status of operation is shown in the Feedback pane with icon and its color (green for success, red for failure). Note that performing mass operation (locking/unlocking multiple WCELs) may take more time and operation may not be successful for all WCELs. Such situation is indicated by orange icon in the Feedback pane. You can see details of the operation by clicking the icon in Feedback pane.

60 DN03471515


Id:0900d805809a23dcConfidential

6.2 Requesting WBTS resetPurposeThis procedure enables you to request a WBTS reset or multiple WBTSs reset.

Before you startYou need to be authorized to perform this operation. This is possible only for WBTS objects.

Steps

1 Log into OMS Element Manager .For instructions, see Logging into OMS Element Manager.

2 Browse the Topology Tree and select RNC or WBTS.Expected outcomeThe WBTSs Overview Page button becomes active.

3 Click WBTSs Overview Page button or select Show Overview Page > WBTSs from the context menu.

Expected outcomeThe WBTSs Overview Page application loads to a new tab and lists all WBTSs under selected RNC.

4 Select one or more WBTS objects (to select severa

int_adm_rnw

Documents

Transcript of int_adm_rnw