system library

Nokia Siemens Networks WCDMA RAN, Rel. RU10, System Library, v. 4

WCDMA RAN Direct Configuration Operations

DN70227178

Issue 2-1Approval Date 2009/04/15

2 DN70227178Issue 2-1


Id:0900d805806b8d3c

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

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

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

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

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

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

Copyright © Nokia Siemens Networks 2009. All rights reserved

f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

DN70227178Issue 2-1

3


Id:0900d805806b8d3c

Table of ContentsThis document has 57 pages.

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

1 System-level description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 Description of direct configuration operations . . . . . . . . . . . . . . . . . . . . . 91.2 Architecture of direct configuration operations. . . . . . . . . . . . . . . . . . . . 111.2.1 Architectural roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.3 System-level functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.3.1 Direct activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.3.2 Small configuration change with RNC Element Manager . . . . . . . . . . . 15

2 Radio network configuration management objects . . . . . . . . . . . . . . . . 162.1 RNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.2 IUCS, IUPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3 IUR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.4 IPQM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.5 TQM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.6 Connection configuration (COCO). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.7 Frequency measurement control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.8 Handover path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.9 WBTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.10 WCEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.11 Adjacency for WCDMA cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.12 WSMLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.13 WLCSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.14 WANE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.15 WSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.16 CMOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.17 WRAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.18 IPNB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3 Radio network configuration management in RNC . . . . . . . . . . . . . . . . 213.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.1.1 Roles in RNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.1.2 Radio network configuration management event. . . . . . . . . . . . . . . . . . 223.2 Radio network configuration management functionality in OMS . . . . . . 233.2.1 WBTS resource reservation during a management operation. . . . . . . . 233.2.2 Operation history in the RNC RNW database . . . . . . . . . . . . . . . . . . . . 233.2.3 Support for optional features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.2.4 Updating CM information in RNC and BTS . . . . . . . . . . . . . . . . . . . . . . 233.2.5 Administrative cell locking/unlocking . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.2.6 Feedback caused by RNW CM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.3 RNW configuration data validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.4 Direct activation of a RNW plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.5 ATM-based Iub link configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.5.1 COCO creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.5.2 COCO modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4 DN70227178Issue 2-1


Id:0900d805806b8d3c

3.5.3 COCO deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.5.4 COCO connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.5.5 COCO disconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.5.6 COCO information inquiry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.5.7 O&M link (IPOA) creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.6 IP-based Iub link configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.6.1 IPNB creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.6.2 IPNB modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.6.3 IPNB deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.7 Dual Iub link configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4 Optional functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

5 Features per release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

6 Management data for Direct Configuration Operations . . . . . . . . . . . . . 426.1 Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426.2 Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426.3 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

7 Limitations and restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

8 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

DN70227178Issue 2-1

5


Id:0900d805806b8d3c

List of FiguresFigure 1 Architecture of direct configuration operations from NetAct. . . . . . . . . . 11Figure 2 Architecture of configuration operations from EM and LMT. . . . . . . . . . 12

6 DN70227178Issue 2-1


Id:0900d805806b8d3c

List of TablesTable 1 Adjacency objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Table 2 Direct activation requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Table 3 Features related to direct configuration operations . . . . . . . . . . . . . . . . 41Table 4 RNC alams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Table 5 OMS alams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

DN70227178Issue 2-1

7

WCDMA RAN Direct Configuration Operations Summary of changes

Id:0900d8058060a061

Summary of changesChanges between issues 2-0 and 2-1New chapters Radio network configuration management in RNC and Radio network configuration management objects have been added.

Minor editorial changes have been made.

Changes between issues 1-1 and 2-0A new feature, RAN1199: RNC GUI for BTS Connection Resources, has been added.

The use of BTS manager has been extended.

Minor editorial changes have been made.

Changes between issues 1-0 and 1-1Editorial changes have been made.

8 DN70227178Issue 2-1


Id:0900d8058060a061

Summary of changes

DN70227178Issue 2-1

9

WCDMA RAN Direct Configuration Operations System-level description

Id:0900d805806e3178

1 System-level description

1.1 Description of direct configuration operationsRadio network configuration management includes creating, modifying and deleting network managed objects; cell locking and unlocking; and resetting Wideband Code Division Multiple Access (WCDMA) Base Transceiver Station (BTS).

Configuration management can be done by mass operations performed and controlled by NetAct or with smaller parameter changes. Smaller day-to-day parameter changes and site creations and expansion procedures are performed with network element specific Element Managers or direct activation operations from NetAct. In a mass oper-ation, Radio Network (RNW) configuration changes are distributed to the network as plan files with separate download and activation procedures. For more information on mass operations, see WCDMA RAN Mass Operations.

Radio Network Controller (RNC) RNW configuration can be managed locally with an RNC Element Manager application called RNC RNW Object Browser. The RNC RNW Object Browser provides the user with a general view on the managed objects in the radio network. The RNC RNW Object Browser can be used for the following operations:

• configuring and modifying an RNC • creating a new WCDMA Base Station (WBTS) site and modifying, deleting, and

resetting a WBTS • creating, modifying, and deleting a WCDMA Cell (WCEL), and locking and unlocking

a WCEL • creating, modifying, and deleting an Intra-frequency Adjacency (ADJS), Inter-fre-

quency Adjacency (ADJI), and Inter-system Adjacency (ADJG) • creating, modifying, and deleting an Intra-frequency Handover Part (HOPS), Inter-

frequency Handover Part (HOPI), and Inter-system Handover Part (HOPG) • creating, modifying, and deleting a an Intra-frequency Measurement Control

(FMCS), Inter-frequency Measurement Control (FMCI), and Inter-system Measure-ment Control (FMCG)

• creating, modifying, and deleting a WCDMA Location Services Entity (WLCSE) • creating, modifying, and deleting a WCDMA Authorized Network (WANE), WCDMA

Subscriber Group (WSG), and WCDMA Serving Mobile Location Centre (WSMLC) • creating, modifying, and deleting a Connection Configuration Object (COCO) • creating IP over ATM Termination point • opening fault management • viewing RNC, WBTS and WCEL alarm details • viewing license and option states • viewing WBTS connection resources

If the RNW configuration is changed with the RNC RNW Object Browser, the RNC sends a notification of the parameter change to NetAct, so that NetAct can update the new parameter value to the RNW configuration data.

ATM Cross-connection (AXC) and BTS configuration can be managed with AXC and BTS element managers. The BTS Site Manager is used to manage both WCDMA FlexiBTS and UltraSite WCDMA BTS. BTS Site Manager for FlexiBTS includes BTS Manager for BTS management and Transport Manager for transmission management (FTM). BTS Site Manager for UltraSite includes only BTS Manager for BTS manage-

10 DN70227178Issue 2-1


Id:0900d805806e3178

System-level description

ment. AXC is managed with AXC Manager. The BTS Manager connects to BTS with BTS Manager - BTS O&M interface which uses XML formatted messages over HTTP. The AXC and Transport Manager use NWI3 interface. File Transfer Protocol (FTP) is used for file transferring.

With the BTS Manager the user can:

• monitor BTS HW and SW configuration and state • monitor BTS alarms • monitor licensing status • monitoring clock synchronization • commission BTS • update BTS SW • block and unblock BTS and/or some of its HW • reset BTS • fetch PM data and log files • execute tests and fetch test reports • execute user authentication

With the AXC and Transport Manager the user can:

• monitor alarms • fetch performance data • import, export, and delete licences • view own permissions • execute test functions (loopbacks) • save log files for troubleshooting • import and export site configuration files for commissioning • change individual parameter (for example, adding/removing IP routes or Cross-Con-

nections) • execute troubleshooting actions like reboot and recovery • save commissioning reports

If the AXC or FTM configuration is changed with Transport Manager, NetAct does not get information of the changed configuration. However, NetAct can upload AXC or FTM configuration data regularly to have up-to-date configuration data in NetAct.

BTS Manager can be used for occasional local configuration changes. NetAct is not informed of the local changes.BTS manager can be used also remotely through the RNC (RAN1246: WBTS EM Manager Launch from RNC).

It also possible to perform direct operations from NetAct to individual RNC and BTS parameter settings in the RNW configuration.

DN70227178Issue 2-1

11


Id:0900d8058060a068

1.2 Architecture of direct configuration operations

Figure 1 Architecture of direct configuration operations from NetAct

Network Management

Interface

WCDMA BTS

BTS O&M Interface

RNC

RNC RNW

Configuration data

NetAct

UIRadio Access

Configurator

RNC Configuration

Management

BTS Configuration

Management

BTS

Configuration data

12 DN70227178Issue 2-1


Id:0900d8058060a068

Figure 2 Architecture of configuration operations from EM and LMT

1.2.1 Architectural roles

UserThe user triggers the configuration management operations with NetAct Radio Access Configurator CM Editor application, or with network element specific Element Manager or Local Management Tool (LMT), either locally or remotely.

NetActNetAct controls the direct activation configuration management operations. NetAct also provides a data storage for network element configuration data.

RNCThe RNC is the target element for RNW configuration management operations. It also provides a local data storage for RNC RNW configuration.

The RNC mediates BTS configuration change requests to BTS in 3GPP NBAP inter-face. RNC provides data storage for BTS RNW configuration.

Network Management

Interface

BTS

BTS O&M Interface

RNC

RNC RNW

Configuration data

NetAct

UI

RNC Configuration

Management

Radio Access

Configurator

EM

LMT

LMT

BTS

Configuration data

AXC

AXC

Configuration data

BTS Configuration

Management

AXC Configuration

Management

DN70227178Issue 2-1

13


Id:0900d8058060a068

BTSThe BTS is the target element for BTS configuration management operations. It also provides a local data storage for BTS configuration.

AXCThe AXC is the target element for AXC configuration management operations. It also provides a local data storage for AXC configuration.

14 DN70227178Issue 2-1


Id:0900d8058060a073

1.3 System-level functionalities

1.3.1 Direct activationDirect activation is executed when the operator wants to make small configuration changes to the network with NetAct. These small configuration changes can be targeted to the RNC and/or BTS parameters.

Direct activationActor: NetAct Radio Access Configurator user

Tools: NetAct Radio Access Configurator

Frequency: Several times a day

1. Select a network element and modify a certain parameter with NetAct Radio Access Configurator CM Editor.

2. NetAct sends configuration change request to the RNC.3. The RNC checks the new parameter value and stores the parameter to the RNW

database.4. In the case of an RNC parameter, RNC takes the parameter into use.5. In the case of a BTS configuration parameter,

a) The RNC sends the new parameter values to the BTS.b) The BTS checks the parameter and stores the new parameter value.c) The BTS takes the parameter into use.d) The BTS sends acknowledgement to the RNC.e) If the parameter change can not be activated without clearing the traffic from the

cell, the BTS starts the Block Resource (3GPP NBAP) procedure and resets.6. The RNC sends acknowledgement to NetAct, and NetAct shows the status of the

operation to the user.7. NetAct updates new parameter values to NetAct RNW configuration data.

The network element configuration has been changed. New object/parameter values have been taken into use and stored to NetAct, the RNC RNW database (and BTS con-figuration data).

Object creation and deletion and WCEL lock and unlock operations with direct activation are similar to parameter modification.

DN70227178Issue 2-1

15


Id:0900d8058060a070

1.3.2 Small configuration change with RNC Element ManagerRNC Element Manager RNC RNW Object Browser can be used to make small configu-ration changes to the network. These small configuration changes can be targeted to the RNC and/or BTS parameters.

Small configuration change with RNC Element ManagerActor: Element Manager user

Tools: RNC RNW Object Browser

Frequency: Several times a day

1. Select a network element and modify a certain parameter with the RNC RNW Object Browser.

2. The RNC checks the new parameter value and stores the parameter to the RNW database.

3. In the case of an RNC parameter, the RNC takes the parameter into use.4. In the case of a BTS configuration parameter:

a) The RNC sends the new parameter values to the BTS.b) The BTS checks the parameter and stores the new parameter value.c) The BTS takes the parameter into use.d) If the parameter can not be activated without clearing the traffic from the cell, the

BTS starts the Block Resource (3GPP NBAP) procedure and resets.e) The BTS sends acknowledgement to the RNC.

5. The RNC sends a notification of the changed parameter to NetAct.6. NetAct updates the new parameter value to NetAct RNW configuration data.

The network element configuration has been changed. New parameter values have been taken into use and stored to NetAct and the RNC RNW database (and BTS con-figuration data).

Object creation and deletion and WCEL lock and unlock operations with RNC Element Manager are similar to parameter modification.

16 DN70227178Issue 2-1


Id:0900d805806e31de

Radio network configuration management objects

2 Radio network configuration management objectsEach controlled network element and conceptual entity in the network is represented by a logical object, each of which has an object collection of its own and is associated with a number of parameters that define its behavior. As illustrated in Figure Logical structure of the RNW management objects some object types are divided into subtypes. For example, Frequency Measurement Control (FMC) is divided into Intra-Frequency Mea-surement Control (FMCS), Inter-Frequency Measurement Control (FMCI), and Inter-System Measurement Control (FMCG). Because the set of parameters differs from one subtype to another, each of these subtypes has to be an object in its own right.

The logical objects are hierarchically related to each other, as reflected in the structure tree of the RNC RNW Object Browser. The object hierarchy dictates the order in which it is possible to create objects. It is not possible, for example, to create an ADJx object before the corresponding WCEL objects have been created. A WCEL object, in turn, can only be created if a WBTS object has already been created.

The object hierarchy is also enforced when objects are deleted. For example, when a WBTS object is deleted, all the WCEL objects under it are automatically deleted. The logical structure of the RNW management objects is shown in Figure Logical structure of the RNW management objects. Radio network managed objects and their logical relations are stored in the RNC RNW database.

2.1 RNCRNC refers to the logical object of RNC. Exceptionally, there are no create or delete operations associated with the RNC object. The RNC managed object contains RNC level parameters.

2.2 IUCS, IUPSThe IUCS managed object contains connection settings towards a particular MGW. The IUPS managed object contains connection settings towards a particular SGSN.

These objects contain the configuration for the Iu-CS and Iu-PS interfaces. For instruc-tions on configuring these interfaces, see Configuring Iu-CS parameters of RNC and Configuring Iu-PS parameters of RNC in Administering Radio Networks. The maximum number of IUCS and IUPS core managed objects in RNC is 32.

2.3 IURThe IUR managed object contains neighboring RNC-related parameters. For instruc-tions on configuring this interface, see Configuring Iur parameters of RNC and in Admin-istering Radio Networks. The maximum number of IUR managed objects in RNC is 32.

2.4 IPQMThis object is used in configuring the features IP Based Iu-CS and IP Based Iu-PS. The maximum number of IPQM managed objects in RNC 8.

DN70227178Issue 2-1

17

WCDMA RAN Direct Configuration Operations Radio network configuration management objects

Id:0900d805806e31de

2.5 TQMThis object is used for configuring feature RAN1253: Iub Transport QoS. The maximum number of TQM managed objects in RNC is 4.

2.6 Connection configuration (COCO)A logical connection configuration object (COCO) is created to reserve local transmis-sion resources for each WCDMA BTS. A COCO object displays the transmission resources at the Iub interface, but not the actual radio network topology.

This object is needed only when ATM transport is used for the BTS. Before creating a COCO, the corresponding ATM interface has to be created. For instructions on creating an ATM interface, see Creating ATM resources in RNC in Managing ATM Resources in RNC.

The maximum number of radio network COCO objects in the RNW database follows the number of supported BTSs under the RNC.

For more information about connection configuration, see Creating radio network con-nection configuration (ATM, Dual Iub) and Modifying radio network connection configu-ration parameters in Administering Radio Networks.

2.7 Frequency measurement controlA frequency measurement control (FMC) object contains information concerning the fre-quency measurement functionality of RNC. The maximum number of frequency mea-surement objects within one category is 100. 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.

There are three types of FMC objects:

• FMCS = object for intra-frequency measurement control • FMCI = object for inter-frequency measurement control • FMCG = object for inter-system frequency measurement control (optional)

2.8 Handover pathA handover path (HOP) object stores the values used in handover and call drop decision making. The maximum number of HOP objects within one category is 100. A logical HOP object is created so that its parameters can be used in adjacent WCDMA cell def-initions. One HOP can be related to several adjacency objects of the same group.

There are three types of HOP objects:

• 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)

For more information about handover, see Handover control in WCDMA RAN RRM Handover Control.

18 DN70227178Issue 2-1


Id:0900d805806e31de


2.9 WBTSA WCDMA BTS (WBTS) is the logical object of the WCDMA base station. A logical WBTS object is created to manage BTS-related telecom and radio resource configura-tion. 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 RNC.

For more information on transport configuration, see .

The maximum number of the WBTS’s in the RNW database is 2800.

Supported NodeB capacity

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, see RAN1623: Carrier Connectivity Optimised RNC450 in WCDMA RAN System, Rel. RAS06, Feature Descriptions.

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

2.10 WCELA WCDMA 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 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) • used WRAB

Supported WCDMA cell capacity

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 .

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 more information on license-controlled capacity, see RAN1198: RNC2600 SW License Key Controlled Capacity in WCDMA RAN, Rel. RU10, Feature Descriptions.

2.11 Adjacency for WCDMA cellAn adjacency for a WCDMA cell (ADJ) refers to a handover relationship between two WCDMA cells.

DN70227178Issue 2-1

19

WCDMA RAN Direct Configuration Operations Radio network configuration management objects

Id:0900d805806e31de

Adjacencies are defined for neighboring cells. Depending on the type of cells for which this relationship is defined, there are three different 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)

Handover path objects must be created before they can be used by ADJx objects.

2.12 WSMLCA 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 Signalling Unit (ICSU) is configured using WSMLC parameters. In the RNW database, there can be only one WSMLC object.

WSLMC and WLCSE objects can only be created if feature RAN2.0041: LCS – Cell Coverage Based (RTT) with Geographical Coordinates is supported.

For more information, see .

2.13 WLCSEWCEL-related parameters needed by location algorithms are defined in a WLCSE object collection. The WLCSE parameters must be defined for each cell that is used in location calculation in RNC. The parameters must also be defined for cells controlled by the neighboring RNCs that are used in location calculation in the locating RNC.

A WLCSE object in a WLCSE object collection is identified by using the UTRAN cell identifier, which must be unique in the RNC (in the RNW database). In the RNW data-base, there can be a total of 6000 WLCSE objects of which 2800 are for the RNCs own cells and 3200 for the neighboring RNCs' cells.

WSLMC and WLCSE objects can only be created if feature RAN2.0041: LCS – Cell Coverage Based (RTT) with Geographical Coordinates is supported.


2.14 WANEA WANE object contains parameters used in IMSI-based handover, which is an optional feature.

Type of adjacency Total number of adja-cency objects per WCDMA cell

Maximum number of adjacency objects within one category

ADJS 31 86800

ADJD 32 44800

ADJI 48 134400

ADJG 32 89600

Table 1 Adjacency objects

20 DN70227178Issue 2-1


Id:0900d805806e31de


WANE objects can only be created if feature RAN2.0060: IMSI Based Handover is sup-ported.

For more information, see Functionality of IMSI-based handover in WCDMA RAN RRM Handover Control.

2.15 WSGA WSG object contains parameters used in IMSI-based handover, which is an optional feature.

WSG objects can only be created if feature RAN2.0060: IMSI Based Handover is sup-ported.

For more information, see Functionality of IMSI-based handover in WCDMA RAN RRM Handover Control.

2.16 CMOBRNW CM supports limiting access rights to the network (allowed/restricted) that is broadcast to all user equipment (UE) in the system information message on access level basis. In a normal situation, the network access is allowed for all access levels. If the 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.

A CMOB object contains RNW 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 3 restriction areas, which must have different types (CS-DSAC, PS-DSAC and RNAR). The maximum number of CMOB objects under one RNC is 13. If feature RAN801: Radio Network Access Regu-lation Function is enabled in RNC, RNC creates three 'forced' CMOB objects during RNC startup or RNC object creation.

For more information, see RAN801: Radio Network Access Regulation Function in RAS05.1 Operability Features.

2.17 WRABA WRAB object contains connection-based quality control parameters. The parameters define the service bearer and signalling bearer quality targets and the related power control thresholds for each transport channel configuration.

The maximum number of WRABs in the RNW database is 5.

2.18 IPNBAn IPNB object contains the NBAP link configuration for the WBTS with the IP-based Iub interface.


DN70227178Issue 2-1

21

WCDMA RAN Direct Configuration Operations Radio network configuration management in RNC

Id:0900d805806e317c

3 Radio network configuration management in RNC

3.1 OverviewRadio network configuration management (RNW CM) offers the operator means to control the configuration and functionality of network elements in RAN. Radio network configuration management is a general (non-optional) feature.

RNW CM consists of mass operations performed and controlled by NetAct as well as single managed object changes and site creation/expansion procedures performed with the RNC RNW Object Browser. For more information on RNW CM mass operations, see WCDMA RAN Mass Operations.

RNW CM performs tasks that are triggered by different events within the system. These include NodeB audit procedure and NodeB resource status indication.

The Radio Access Network (RAN) is made up of a number of physical network elements (NEs) (for example, RNC and WCDMA BTS) as well as a number of conceptual entities (for example, adjacencies and handover paths). RNW CM refers to the operation of con-figuring these network elements and conceptual entities. In the RNC object model, the managed physical network elements and the conceptual entities are treated as logical objects.

RNW CM includes creating, modifying, and deleting network managed objects, locking and unlocking cells, and resetting WCDMA BTS. All of these procedures are accessible through the RNC RNW Object Browser. The radio network configuration can be changed locally in the RNC using the RNC RNW Object browser, or remotely from NetAct.

RNW CM provides also services for updating cell states. A cell's administrative state can be updated by a user making a cell lock or unlock operation. The operational state is updated by the system and visible to the user. RNW CM provides statistics for cell state changes.

To have a functioning RNW, the needed RNW objects must be created and the transport layer must be configured. For more information about the transport layer and connection configuration, see .

3.1.1 Roles in RNC

RNW maintenance engineerThe RNW maintenance engineer is the operator/user of NetAct or the RNW Object Browser, who triggers configuration management procedures by making administrative updates to RNC RNW.

The RNW maintenance engineer manages a number of logical configuration manage-ment objects to control their physical counterparts in the radio access network (RAN). For example, the RNW maintenance engineer may create a WCDMA base station (WBTS) object, and adjust the parameters of the object to control the behavior of a certain base station in the field.

22 DN70227178Issue 2-1


Id:0900d805806e317c

Radio network configuration management in RNC

RNC application softwareRNC offers services for storing RNW configuration data to the RNC RNW database in different configuration situations in logical RNW objects as well as keeping radio network configuration up-to-date.

Features can be activated and deactivated through configuration management inter-faces with feature-specific activation parameters.

RNC RNW configuration management in OMU handles cell state information and number of link connection statuses. Any changes in these statuses are informed to the OMS and NetAct counterparts. OMU CM recognizes a number of fault conditions and communicates these with RNC Fault Management services. For more information, see WCDMA RAN Fault Management.

RNW CM uses the feature and option management functionality for checking optional feature states to allow a particular configuration. For more information, see Licence-based Feature Management.

RNW CM performs a number of updates based on the system functionality by other network elements and general configuration changes during the normal operation of RNC. These activities are between network elements as well as within the RNC IPA plat-form. In both cases events to OMS and NetAct can be triggered.

Reconfiguring the RNC or reconfiguration support to the BTS are examples of these functionalities.

OMSOMS offers the users a graphical user interface: RNC RNW Object Browser. It can be used to configure the managed objects, thus determining how the radio access network functions. For more information, see RNC RNW Object Browser in Administering Radio Networks .

RNW object management in OMS provides the functionality to read and modify RNW topology and parameters. In RNC RNW Object Browser startup, the current RNW topology is read from the RNC RNW database over an EMT connection between RNC OMU and OMS, and the data is stored to the Object Browser’s memory. Managed object modification is also done over an EMT connection from OMS (Object Browser) to OMU.

The RNC RNW Object Browser includes RNW connection configuration management. The RNW Connection Configuration dialog enables the user to monitor, add and edit BTS connection configurations and their parameters. For more information, see Using Element Manager in RNC OMS.

CM events are mediated from RNC to the Object Browser and NetAct via OMS. The functionality is provided by Event Management in OMS.

3.1.2 Radio network configuration management eventRadio network events/CM events originate from RNC OMU and are mediated via OMS to Object Browsers and NetAct. A CM event is sent as a consequence of managed object parameter change (modification), managed object creation, and managed object deletion. An update may also be caused by state updates made by the system.

RNC OMU has buffer for events. OMS will follow the CM event sending progress and request resending from OMU if the event is not successfully delivered to OMS or NetAct.

DN70227178Issue 2-1

23


Id:0900d8058060a07d

3.2 Radio network configuration management functionality in OMSThe RNW CM functionality in OMS provides ways to manage the RNW database and maintain the consistency of the configuration both in the RNW database system and in RNC.

3.2.1 WBTS resource reservation during a management operationOMU CM controls BTS resource management in RNC. BTS configuration in RNC is reserved for each individual configuration operation that is related to a WBTS, WCEL, or ADJS/I/G/D object. Configuration reservation is needed to preserve the consistency of the managed data. Several RNW Object Browser instances can be used to perform configuration changes in RNC. The resource reservation functionality ensures that those parallel instances do not perform operations to the same BTS at the same time.

3.2.2 Operation history in the RNC RNW databaseThe RNW database is located in the OMU CU in the RNC. The RNW database contains the configuration data and the control parameters of the RAN controlled by the RNC.

The following information is stored for each managed object:

• the date and time of the last configuration action • the origin of the management operation (RNW plan, RNW Object Browser, or Direct

Activation)

Adjacency object types (ADJS/I/G/D) are an exception. These objects do not have an object-specific record of the time and date of the last configuration action. Each adja-cency object type has only one record of that information within the parent WCEL object. The record is common for all the adjacency object instances of the same type.

3.2.3 Support for optional featuresA configuration interface is provided for a licensed feature whose feature state is On or Config in RNC. If the feature is not controlled by a license, a configuration interface is provided for an optional feature that is indicated to be active by a separate control parameter.

Licence information is also used to restrict configuration operations. OMS CM prevents illegal configuration according to the feature status information provided by license man-agement services.

OMU CM provides OMS counter processes optional feature state information.

OMU CM SW performs data validation when data is received from OMS. Data validation in OMU is more comprehensive than the validation done in OMS.

RNW CM provides license information to RNW Plan Management in RNW plan opera-tions. For more information on license and option management, see Licence-based Feature Management.

3.2.4 Updating CM information in RNC and BTSOMU CM is responsible for updating the changed configuration and parameter data to all interested entities and domains within RNC. If any such update does not succeed,

24 DN70227178Issue 2-1


Id:0900d8058060a07d

possible errors related to a specific configuration operation is returned to the operator. Typically these operations are creation/modification/deletion/state changes of the RNW object instance.

Also changes to RNW may affect the update of incoming adjacencies or delete incoming adjacencies procedures.

OMU CM keeps track of local BTSs as well as cell status, and triggers in RNC several update procedures towards BTS. Typically such an operation can be, for example, Cell setup, Cell reconfiguration, common channel setup, or System information update request.

3.2.5 Administrative cell locking/unlockingAn administrative state configuration service is provided to the operator through different interfaces. The user can manually lock and unlock a cell resource through the RNC Element Manager dialog. Cell locking in the BTS site can be used to restrict the use of a cell, for example, because of a major parameter change. The BTS shutdown proce-dure is used for avoiding the loss of traffic. The BTS O&M decides the used timer according to the local site configuration. The system provides feedback of the operation to the user in the Object Browser. For more information, see .

3.2.6 Feedback caused by RNW CMCM sends feedback to the RNW Object Browser as a reply for a management operation.

Each feedback message contains information of the requested operation status. If the CM operation is stopped because of any error during the process, the operation is not continued further. A feedback message containing the error status in a suitable field of the feedback message is sent.

The db status field indicates the following:

• main status, which indicates the status of RNW data checking • db status, which indicates the status of the requested database operation • delivery status, which indicates the status of parameter distribution in the system • coco status, which indicates the status of the connection configuration operation • ef status, which indicates the status of the RNW event • conf data status, which indicates the status of the configuration data update • sys info status, which indicates status of system information request update • cell init status, which indicates the status related to cell configuration procedures • common measurement status, which indicates whether measurements were

started, terminated, or restarted successfully or unsuccessfully

DN70227178Issue 2-1

25


Id:0900d8058060a080

3.3 RNW configuration data validationConfiguration data parameters are checked in the RNC RNW Object Browser and by the RNW Configuration management in OMU.

Configuration data validation can be divided into the following subcategories:

• Checking required by the feature functionality • Parameter data value checking • Parameter range checks

Consistency checkThe RNW database consistency check is a service that is requested by plan manage-ment during the download of the RNW plan. The same consistency rules apply to the configuration tasks done by Element Manager.

In principle, the parameter data in different RNW objects is compared to each other to confirm that the data is consistent according to the parameter relationship definitions (for more information, see WCDMA Radio Network Configuration Parameters)

RNW configuration consistency check rulesFor more information on rules applied in consistency check, see Appendix.

26 DN70227178Issue 2-1


Id:0900d8058060a083

3.4 Direct activation of a RNW planThe direct activation of the RNW plan makes it possible to update single objects directly to the active database (ACTdb) without a need for separate RNW plan download (pre-activation) and activation.

NetAct sends the object data to RNC which checks the data content and makes the modification directly to the active database. NetAct can send direct activation requests for the following objects and operations:

Only one object is accepted in each direct activation.

WCEL lock, unlock, create, modify, and delete

WBTS create, modify, and delete

COCO create, modify, and delete

WLCSE create, modify, and delete

Adjacencies (ADJI, ADJS, ADJG, ADJD) create, modify, and delete

Table 2 Direct activation requests

DN70227178Issue 2-1

27


Id:0900d805806e31ba

3.5 ATM-based Iub link configurationA logical connection configuration object (COCO) is created to reserve local transmis-sion resources for the WCDMA BTS. Before creating a COCO, the corresponding ATM interface has to be created. For instructions on creating an ATM interface, see Creating ATM resources in RNC in Managing ATM Resources in RNC.

A COCO object displays the transmission resources at the Iub interface, but not the actual radio network topology.

The maximum number of radio network COCO objects in the RNW database follows the number of supported BTSs under the RNC.

The process of creating a connection configuration consists of two separate phases:

1. ATM layer configuration/ATM layer checkThe ATM layer Virtual Path (VP) and Virtual Channel (VC) termination point config-uration can be created to the system through MML commands or from NetAct with the ATM plan interface. The ATM layer VP and VC level entities can be also config-ured to the system during COCO object creation.

2. Control/user plane configuration (COCO - WBTS connection)Control/user plane configuration is initiated during COCO creation if the COCO ID or ATM interface/VPI/VCI triplet of the CNBAP link is found in a WCDMA BTS object.

The connection configuration link categories are the following:

• C-NBAP, one for the WCDMA BTS • D-NBAP, there is one for the FlexiBTS type of BTS or one D-NBAP link to each

WAM unit of the UltraSite BTS. The maximum number of D-NBAP signalling links in the COCO is 6.

• AAL2 signalling = the signalling link for the AAL2 user plane/user data connections. There is one AAL2 signalling link to the FlexiBTS type of the BTS and for the Ultra-Site BTS that has the BTS AAL2 multiplexing feature enabled (AXU-B/C/D), or one AAL2 signalling link to each WAM unit of the Ultra Site BTS with AXU-A. The maximum number of AAL2 signalling links in the COCO is 6.

• AAL2 user plane/user data (AAL2 Path), the AAL2 user plane connection leads to the AAL2 termination point in the WBTS. The maximum number of AAL2 user plane connections in the COCO is 18.

Connection configuration operations are mainly user-originated. A COCO object can be managed in the COCO GUI in the RNC RNW Object Browser (see figure below), or with a RNW plan. For more information on the use of the RNC RNW configuration, see WCDMA RAN Mass Operations.

The following functionalities are provided by connection configuration management:

• COCO creation • COCO modification • COCO deletion • COCO connect • COCO disconnect • COCO information inquiry • O&M link (IPOA) creation

28 DN70227178Issue 2-1


Id:0900d805806e31ba

3.5.1 COCO creationCOCO object creation can be started by the operator through RNW plan management interfaces or in the COCO GUI. This operation creates a COCO object in the RNW database and the needed resources to the system by using IPA platform services and databases.

For more information, see Managing ATM Resources in RNC.

1. COCO object creation requestThe request for creating the COCO object and the related connections is sent to the connection configuration manager. The request may include the automatic ATM VP/VC link termination point creation option enabled. The related ATM interface and its access profile as well as the physical layer entities (SDH/PDH) have to be created beforehand in the system.

2. Plan operation checkThe plan operation situation is inquired from RNW plan management. If a plan oper-ation is already ongoing, the whole COCO operation will be interrupted.

3. Parameter checkParameters are checked to guarantee that the COCO has been properly configured and that the COCO configuration does not exceed the scope of the current license. If an incorrect configuration is detected, the whole scenario is aborted and an acknowledgement message is sent to the service request with corresponding error status values.

4. ATM layer resource configurationIf the ATM termination point configuration option is enabled, the needed ATM termi-nation points are created in the system before creating the COCO object in the RNW database. ATM termination points are created by the ATM resource manager provided by the IPA platform and stored to the ATM resource management data-base.The VPLtp(s) can be used by several COCO objects and the VPLtp can exist in the system when the automatic ATM configuration option is used. If the ATM termination point configuration is not enabled, the system verifies that ATM termination points existiin the system. Each COCO can have from one (default) to six VCLtps in use.ATM layer parameters can be configured with MML commands, the ATM plan inter-face, or part of COCO configuration when the COCO GUI or RNW plan manage-ment can be used.If AAL2 user plane links are bundled, the needed bundle is also created in this phase of COCO object creation. For more information, see RAN1099: Dynamic Scheduling for HSDPA with Path Selection and RAN1100: Dynamic Scheduling for NRT DCH with Path Selection in WCDMA RAN System, Rel. RAS06, Feature Descriptions.

5. COCO object creation in RNW databaseAfter successful ATM TP and VCC bundle configuration the COCO object is created in the RNW database.

6. WBTS check/COCO connectIf the corresponding WBTS for the COCO object is found in the RNW database, the operation continues with control/user plane creation.If the RNW database does not contain a WBTS object for this COCO, the control and user plane configuration part is skipped. A COCO object without control and user plane is called 'unconnected COCO'.

DN70227178Issue 2-1

29


Id:0900d805806e31ba

7. WBTS reservationThe WBTS object is reserved from the database system for this operation to prevent other users from attempting to update the object at the same time.

8. Control/user plane configurationControl/user plane configuration consists of two phases. In the first phase, the fol-lowing terminations for control plane links are created: • C-NBAP, one link connected to the master WAM of the WCDMA BTS • D-NBAP, one link to each WAM. The maximum number of D-NBAP signalling

links in the COCO is 6. • AAL2 signalling, signalling link for the AAL2 user plane/user data connections.

If the BTS AAL2 multiplexing feature is not enabled, there is one link to each WAM. The maximum number of AAL2 signalling links per COCO is 6.

The IPA platform provides control channel management services to create these ter-minations and the information is stored to the file.The AAL2 user plane connection is leading to the AAL2 termination point in the WBTS. The maximum number of the AAL2 user plane connections in the COCO is 18.If AAL2 user plane links are bundled, the ATM end points are associated with the created bundle(s) in this phase.AAL2 user plane-related numbering on the Iub interface can either be set manually or generated during the connection configuration creation. The numbering related to each AAL2 user plane VCC is A2EA (AAL type 2 endpoint address) and AAL2 path identification.The digit analyses of the Iub interface are created in the tree (IubDATree) given in COCO creation.User plane configuration consists of the creation of the following resources:a) route(s)b) ATM end point(s) and VCC bundle(s)c) AAL2 path IDs and A2EA addresses to each AAL2 user plane VCCd) digit analysisWhen creating the needed resources, the IPA platform services are used for: • configuring the needed ATM layer resources for the COCO • configuring the needed ATM end points • creating and deleting ATM routes • creating digit analysis for routes • inquiring information from the platform database • inquiring signalling links • unblocking the AAL2 path • storing ATM configuration informationIf the control/user plane configuration is executed successfully, the relation between the COCO and the WBTS logical objects is created in the RNW database.For more information, see Managing ATM Resources in RNC and Configuring Routing and Digit Analysis in RNC.

9. AAL2 path unblockingThe AAL2 path has to be unblocked before any AAL2 data channels can be reserved from the related AAL2 VCC. Unblocking is performed by using the IPA

30 DN70227178Issue 2-1


Id:0900d805806e31ba

platform service. The AAL2 path is identified by the AAL2 path id (related to the AAL2 user plane VCC – ATM end point).The alarm 7761 RNW O&M SCENARIO FAILURE indicates that the AAL2 path is not yet unblocked successfully. The alarm is set for each user plane link and cleared after successful unblocking.

10. COCO updateControl/user plane configuration data is updated to the COCO object in the RNW database.

11. WCEL state updateIf the COCO was successfully connected to the WBTS object (link configuration and COCO – WBTS relation creation), the state of the related WBTS is updated.

12. WBTS releaseThe reservation of the WBTS object, done at the beginning of the operation in the RNW database, is released.

13. COCO eventThe connection configuration manager informs the RNW Object Browser and NetAct through OMS about the COCO object creation by sending an event.

14. COCO creation acknowledgementAn acknowledgement message is sent to the service request with corresponding error status values.

3.5.2 COCO modificationCOCO object modification can be started by the operator through RNW plan manage-ment interfaces or in the COCO GUI. This operation modifies the parameters in the COCO object. Some parameter modifications request object locking (locking the related WBTS).

1. COCO object modification requestThe request for modification of the COCO object and the related connections is sent to the connection configuration manager. The user may define whether the cre-ation/deletion of the corresponding ATM termination points for the new/deleted links is performed as well.All COCO parameters are included in the modification request. The connection con-figuration manager checks the need for the modification against the current config-uration.If the COCO is related to the WBTS (actual links are already being created), the user is responsible for checking and changing the WCEL states related to the WBTS if necessary. The related WCELs must be locked before the COCO modification for the connected COCO can be executed. The connection configuration manager checks the state information, but does not initiate any state change actions for the active WCELs in a local operation.

2. Plan operation checkThe plan operation situation is inquired from RNW plan management. If a plan oper-ation is already ongoing, the whole COCO operation will be interrupted.

3. COCO checkThe connection configuration manager reads the COCO parameters from the RNW database. If the object does not exist, the scenario is aborted and an acknowledge-ment message is sent to the service request with corresponding error status values.

4. Parameter checkThe parameter check in the COCO modification operation consists of:

DN70227178Issue 2-1

31


Id:0900d805806e31ba

• checking the input, that is, the new COCO parameters, as in COCO creation • determining the modified parts by comparing the new input parameters with the

old COCO object in the database5. WBTS reservation

If the COCO is related to the WBTS, the connection configuration manager checks whether all WCELs are in the locked state if the modified parameters request object locking. If not, and if the modification operation is originated by plan management and automatic object locking is enabled, automatic object locking is executed.The WBTS object is reserved from the database system for this operation to prevent other users from attempting to update the object at the same time.

6. Control/user plane deletionOld control/user plane resources are deleted according to the modification list in COCO parameter checking. In the following cases, the old CU plane will be deleted: • TPI (IF/VPI/VCI) is modified. • The PCR or CDVT values of the VCC are changed. • The related AAL2 signalling TPI is changed for AAL2 UP link. • The AAL2 UP Usage value of AAL2 UP link is changed. • The MDCR or UBR share values of the UBR+ VCC are changed. • The AAL2 path type or VCC bundle usage is changed. • The service category is changed.

7. ATM modificationIf the automatic ATM layer configuration was included in the request, the following required actions (subscenarios) are started: • The ATM layer of the removed NBAP, AAL2 signalling and AAL2 UP links is

removed as well. • ATM termination point modifications are performed (changes to the PCR and

CDVT values, MDCR and UBR share for UBR+ link). • New termination points are created in the system.

8. VCC bundle modificationWhen a VCC bundle is taken into use, the system creates a corresponding bundle. When a VCC bundle is taken out of use, the system deletes the corresponding bundle. The system deletes and recreates the corresponding ATM end points during modification.

9. Control/user plane (re)configurationIf the COCO object is related to the WBTS, the control/user plane configuration for the new and modified parts of the connection configuration must be created.

10. AAL2 path unblockingFor the connected COCO, the AAL2 paths of the new AAL2 UP links have to be unblocked. The unblocking is performed so that also the previously created AAL2 paths that are still in the blocked state are unblocked at this phase.If the unblocking fails the alarm 0x7761 is set to indicate that the AAL2 path is not yet unblocked successfully. The alarm is set for each user plane link. If the unblocking fails, alarm 7761 RNW O&M SCENARIO FAILURE indicates that the AAL2 path is not yet unblocked successfully. The alarm is set for each user plane link.

11. COCO updateThe connection configuration manager modifies the COCO object in the RNW data-base. All successfully performed operations are updated to the database.

32 DN70227178Issue 2-1


Id:0900d805806e31ba

12. WCEL state updateIf the modification was successful, the WCEL states are updated to 'connection con-figuration ready'.


14. COCO eventThe connection configuration manager informs the RNW Object Browser and NetAct through OMS about the COCO object modification by sending an event.

15. COCO modification acknowledgementOMS is informed about the result of the modification procedure.

3.5.3 COCO deletionDeleting a COCO object can be requested by the operator through RNW plan manage-ment interfaces or the COCO GUI. This operation removes certain COCO objects from the RNW database and deletes the related resources from the system.

1. COCO deletion request2. Plan operation check

The plan operation situation is inquired from RNW plan management. The proce-dure is the same as in COCO creation.

3. COCO checkThe connection configuration manager reads the COCO parameters from the RNW database.

4. WBTS reservationThe WBTS object is reserved from the database system for this operation to prevent other users from attempting to update the object at the same time.

5. Control/user plane deletionIf the COCO object is related to the WBTS object, the control/user plane is deleted first.If parts of the deletion fail, the following steps are executed:a) User plane resources (digit analysis, AAL2 Path ids and A2EA addresses, end

points, end point groups, and routes) are deleted from the system.b) Control plane resources (terminations for C-NBAP, D-NPAB, and AAL2 signal-

ing links) are deleted.c) COCO object data in the RNW database is updated according to the deleted

resources.d) WCELs' states are changed to 'failure in connection configuration' state.e) The WBTS object reservation is released.Note that any unsuccessfully deleted parts of the COCO object are kept in the RNW database, and the deletion request can be repeated, for example, in case of a tem-porary failure in the system.

6. ATM deletionIf automatic ATM layer handling is enabled, the ATM resources are removed from the system, including the ATM resource management database.

DN70227178Issue 2-1

33


Id:0900d805806e31ba

7. COCO removalThe COCO object is removed from the RNW database and a COCO deletion event is sent to OMS/NetAct.If the control/user plane configuration and the ATM configuration was only partly deleted, the deleted parts are removed from the COCO object with a modify opera-tion. In that case the COCO object is not removed from the database. A modify event is sent.

8. WCEL state updateIf the database action was successful and the WBTS was related to the COCO, WCEL states are changed to the 'waiting for connection configuration' (BL-WF-COCO) state.


10. COCO deletion acknowledgeThe user is informed about the result of the deletion procedure.

3.5.4 COCO connectThis operation is executed when a WBTS is created or modified and the COCOId is associated with the WBTS.

1. COCO checkThe connection configuration manager reads the COCO parameters from the RNW database. If the object does not exist, the scenario is aborted and an acknowledge-ment message is sent to the service request with corresponding error status values.

2. Control/user plane configurationSee step 2 in COCO creation.

3. AAL2 path unblockingSee step 9 in COCO creation.

4. COCO updateThe control/user plane data is updated in the COCO object in the RNW database.

5. WCEL state updateIf the COCO was successfully connected to the WBTS object (link configuration and COCO-WBTS relation creation), the states of the related WBTSs are updated.

6. COCO eventThe connection configuration manager informs the RNW Object Browser and NetAct through OMS about the COCO object connection by sending an event.

7. COCO connection acknowledgementAn acknowledgement message is sent to the service request with corresponding error status values.

3.5.5 COCO disconnectThis operation is executed when a WBTS is deleted or modified and the COCOId is associated with the WBTS.

In the disconnect operation control/user plane and database relations are removed as in COCO deletion (see COCO deletion), but the COCO object is not deleted from the database, and ATM layer resources remain in the system.

34 DN70227178Issue 2-1


Id:0900d805806e31ba

3.5.6 COCO information inquiryWhen the COCO dialog is opened in the RNC RNW Object Browser, the COCO-related data is fetched from the RNW database and IPA platform storages by the connection configuration manager.

3.5.7 O&M link (IPOA) creationFor each WBTS, the IP over ATM connection is required to carry O&M traffic, for example, alarms. The O&M link is not part of tje COCO object, but the needed ATM layer resources can be created in the COCO GUI by choosing New IP over ATM. The con-nection configuration manager is responsible for creating the resources to the system. For more information, see Integrating RNC.

DN70227178Issue 2-1

35


Id:0900d8058060a089

3.6 IP-based Iub link configurationThe IP transport option is introduced in 3GPP Release 5 as an alternative to ATM trans-port. This option affects the architecture of the transport in terms of protocols, function-ality and network configuration. The following figure presents the protocol stacks.

There are two managed objects related to IP-based Iub link configuration that have special relevance: IPNB and TQM.

The IPNB (IP Iub NBAP) object contains the C-NBAP and D-NBAP definitions for the IP Iub interface. There is reservation for one C-NBAP and six D-NBAP link attributes in the object.

One IPNB can be connected to the WBTS object. When the IPNB is connected to the WBTS, the COCO object cannot be connected to the WBTS, and vice versa. The maximum number of IPNB objects is the same as the maximum number of WBTS objects.

Control plane configuration is done with an IPNB object. IP parameters needed for the user plane are modified in the WBTS object.

The TQM (Transport QoS Management) managed object contains mapping information from the RAB characteristics to the ATM and IP transport QoS differentiation. The infor-mation is used in UTRAN transport bearer establishment. The maximum number of TQM objects in the RNC is 4. Configuring a TQM object is not mandatory for the operator because it is related to an optional feature.

IPNB operationsIP-based Iub link configuration can be done locally with the RNC GUI (RNC RNW Object Browser) or through the RNW plan interface from NetAct. Configuration is possible only if a valid license for the feature is available. The prerequisite for successful IPNB oper-ations is that the IP layer is already configured either through the local MML interface (for more information, see Configuring IP Connection for RNC) or through the IP plan interface from NetAct.

3.6.1 IPNB creation1. IPNB object creation request

The request for creating the IPNB object and the related connections is sent to the connection configuration manager.

2. Plan operation checkThe plan operation situation is inquired from RNW plan management. If a plan oper-ation is already ongoing, the whole IPNB operation will be interrupted.

3. Parameter checkParameters are checked to guarantee that the IPNB object has been properly con-figured, and that the IPNB configuration does not exceed the scope of the current license. If an incorrect configuration is detected, the whole scenario is aborted and an acknowledgement message is sent to the service request with corresponding error status values.

4. IPNB object creation to the RNW databaseThe connection configuration manager creates the IPNB object in the RNW data-base.

36 DN70227178Issue 2-1


Id:0900d8058060a089

5. WBTS checkThe connection configuration manager checks if the corresponding WBTS for the IPNB object is found in the RNW database, and that IP-based Iub is allowed as its transport media, which is defined with a WBTS parameter (IubTransportMedia).

6. WBTS reservationThe WBTS object is reserved from database system for this operation to prevent other users from attempting to update this object at the same time.

7. IPNB connectThe IPNB object is connected with the WBTS object by the connection configuration manager if the WBTS check was successful.

8. NBAP link creationThe connection configuration manager requests NBAP link creation from the IPA platform.

9. WBTS releaseThe reservation of the WBTS object in the RNW database, done at the beginning of the operation, is released.

10. IPNB eventThe connection configuration manager informs the RNW Object Browser and NetAct through OMS about the IPNB object creation by sending an event.

11. IPNB creation acknowledgementAn acknowledgement message is sent to the service request with corresponding error status values.

3.6.2 IPNB modification1. IPNB object modification request

The request for modifying the IPNB object and the related connections is sent to the connection configuration manager.


3. Parameter checkParameters are checked to guarantee that the IPNB object has been properly con-figured. If an incorrect configuration is detected, the whole scenario is aborted and an acknowledgement message is sent to the service request with corresponding error status values.

4. WBTS checkThe connection configuration manager checks if the IPNB is already connected with a WBTS.


6. IPNB disconnectIf the IPNB is already connected with a WBTS, and if C-NBAP or D-NBAP signalling traffic parameters need to be modified, the connection configuration manager will disconnect the IPNB from the WBTS.

7. NBAP link deletionIf the IPNB was disconnected from the WBTS, the corresponding NBAP links are deleted.

DN70227178Issue 2-1

37


Id:0900d8058060a089

8. IPNB connectIf IPNB disconnect was performed, the connection configuration manager will recon-nect the IPNB to the WBTS.

9. NBAP link creationThe connection configuration manager requests NBAP link re-creation from the IPA platform with new parameters.

10. IPNB object modification to the RNW databaseThe connection configuration manager modifies the IPNB object in the RNW data-base. If the IPNB object was not connected to any WBTS, the modified parameters are simply updated in the IPNB object in the RNW database.


12. IPNB eventThe connection configuration manager informs the RNW Object Browser and NetAct through OMS about the IPNB object modification by sending an event.


3.6.3 IPNB deletion1. IPNB object deletion request

The request for deleting the IPNB object and the related connections is sent to the connection configuration manager.


3. WBTS checkThe connection configuration manager checks if the IPNB is already connected with a WBTS.


5. IPNB disconnectIf the IPNB is already connected with a WBTS, the connection configuration manager will disconnect the IPNB from the WBTS.

6. NBAP link deletionIf the IPNB was disconnected from the WBTS, the corresponding NBAP links are deleted.

7. IPNB object deletion from the RNW databaseThe connection configuration manager deletes the IPNB object from the RNW data-base. If the IPNB object was not connected to any WBTS, the IPNB object is simply deleted from the RNW database.


38 DN70227178Issue 2-1


Id:0900d8058060a089

9. IPNB eventThe connection configuration manager informs the RNW Object Browser and NetAct through OMS about the IPNB object deletion by sending an event.


DN70227178Issue 2-1

39


Id:0900d8058060a08f

3.7 Dual Iub link configurationThe Dual Iub feature provides transport bearers towards one BTS over both ATM and IP. With the Dual Iub feature, the HSPA traffic is carried over the IP transport and common channels, and R99 DCH transport bearers are carried over the ATM transport channel.

OperationsDual Iub-based Iub interfaces are configured by combining an ATM-based Iub configu-ration and an IP-based Iub configuration.

ATM Iub configuration is performed according to basic ATM configuration rules. For more information, see ATM-based Iub link configuration.

The IPNB object is not configured for a Dual Iub-based Iub feature. The IP configuration for the user plane is done in the WBTS object. The IP layer has to be configured first.

40 DN70227178Issue 2-1


Id:0900d8058060a096

Optional functionalities

4 Optional functionalitiesThe 'Direct Activation of RNW changes using NWI3' feature is optional. To activate the feature related NetAct, a license has to be purchased.

RNC GUI for BTS Connection Resources is optional.

RNC, AXC, and BTS Element Managers are part of the operating software.

For ATM based Iub link connection configuration the following optional features are available:

• RAS05.1/RN2.2 • RAN1020: Route Selection (feature replaced with RAN759:Path Selection

feature) • RAN935: BTS AAL2 Multiplexing for Flexi WCDMA BTS

• RAS05.1 ED/RN2.2ED • RAN619:Flexible Connection of VPCs for WBTS

• RAS06/RN3.0 • RAN759:Path Selection • RAN1095: UBR+ for Iub User Plane • RAN1099: Dynamic Scheduling for HSDPA with Path Selection • RAN1100: Dynamic Scheduling for NRT DCH with Path Selection

For IP based Iub link connection configuration the following optional features are avail-able:

• RU10/RN4.0 • RAN74: IP Based Iub for Flexi WCDMA BTS • RAN1192: UBR+ for Control Plane and Iu/Iur User Plane • RAN1253: Iub Transport QoS • RAN1449: Dual Iub for Flexi WCDMA BTS

DN70227178Issue 2-1

41

WCDMA RAN Direct Configuration Operations Features per release

Id:0900d8058060a09f

5 Features per releaseThe following table lists the features related to this functional area. The features are arranged according to the release in which they were introduced. Note that a feature may belong to more than one functional area.

RAN1.5

RAN1.041: Graphical User Interface

RAN04

RAN656: WCEL Lock and Unlock from NetAct

RAS05

None

RAS05.1

RAN1152: WCEL Lock and Unlock During RNW Plan Activation

RAS05.1 ED

None

RAS06

RAN1084: Direct Activation of RNW changes using NWI3

RAN1199: RNC GUI for BTS Connection Resources

RU10

RAN1246: WBTS EM Manager Launch from RNC

Table 3 Features related to direct configuration operations

42 DN70227178Issue 2-1


Id:0900d8058060a0a3

Management data for Direct Configuration Operations

6 Management data for Direct Configuration Operations

6.1 AlarmsThe object causing alarms 77xx is the WBTS or a combination of WBTS and WCEL. Other alarms are not targeted to any particular object. For more information about the alarms listed below, see RNC Base Station Alarms (7000-7900).

For more information about OMS alarms, see RNC OMS Alarms.

6.2 CountersThere are no counters related to this functional area.

6.3 ParametersThe following CM parameters are given for each RNW managed object:

• Object identifier • Time stamp

Alarm number Alarm name

2868 LIMITED UE ACCESS TO RADIO NETWORK

3295 LICENSE CAPACITY EXCEEDED

3325 INCONSISTENCY IN CONFIGURATION PARAMETERS

7761 RNW O&M SCENARIO FAILURE

7762 RNW DATABASE OPERATION FAILURE

7771 WCDMA CELL OUT OF USE

7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS

7776 HSDPA FAILURE IN WCEL

7780 HSUPA FAILURE IN WCEL

7781 NETWORK ELEMENT CONFIGURATION ERROR

Table 4 RNC alams

Alarm number Alarm name

71055 NETWORK ELEMENT RESTARTED

71057 RNW NOTIFICATION MISSING

Table 5 OMS alams

DN70227178Issue 2-1

43

WCDMA RAN Direct Configuration Operations Management data for Direct Configuration Operations

Id:0900d8058060a0a3

• Change origin

For more information on RNW configuration management parameters, see WCDMA Radio Network Configuration Parameters.

44 DN70227178Issue 2-1


Id:0900d8058060a0ab

Limitations and restrictions

7 Limitations and restrictionsDirect activationThe 'Direct Activation of RNW changes using NWI3' feature allows the following opera-tions to the following objects:

• WCEL: lock, unlock, create, modify, and delete • WBTS: create, modify, and delete • COCO: create, modify, and delete • WLCSE: create, modify, and delete • Adjacencies (ADJI, ADJS.ADJG): create, modify, and delete

NetAct user can give one direct activation request per RNC at a time. The request can include one object and one operation. However, it is possible to modify several param-eters with one modification command.

Automatic object locking can not be used in direct operations. If parameter modification requires object locking, object has to be locked by changing the AdmCellState param-eter value to ‘Locked’ in the modification request. Object unlocking requires an own direct activation operation.

Direct activation request can not be executed during plan operations (plan upload, roll-back, download or activation).

RNW configuration plan management

• Only one RNW plan can be processed at a time. • Local changes may be restricted during RNW plan operations because of RNW db

reservations. • Local changes made by the Object Browser are overwritten if a NetAct user modifies

the same parameters before downloading and activating the new RNW plan. • Direct activation of a RNW plan makes it possible to update only the specified single

objects directly to the active database (ACTdb) without a need for a separate RNW plan.

DN70227178Issue 2-1

45

WCDMA RAN Direct Configuration Operations Appendix

Id:0900d805806dc6ac

8 AppendixRNW configuration consistency check rulesThe table below shows the list of rules applied in consistency check.

Object Operation Check

RNC Create/ Modify

• RNC - RncId (RNC Identifier) is not modifiable

• The value of parameter SIB18 priority must not be higher than value of parameter SIB11/12 priority

• EmergencyCallISHOSupport and IntelligentEmergencyCallISHOSupport are not allowed both tried to enable if emisho and iemisho options are supported

• AMRwithHSDSCH is not allowed to set to enabled if special value ‘Not defined’ is set to the parameter RTWithHSDPAFmcsIdentifier or RTWithHSDPAFmciIdentifier or RTWithHSD-PAFmcgIdentifier or RTWithHSDPAHopsIdentifier or AdjdRTWithHSDPAHopsId

• If Wireless Priority Service feature is enabled, then AdjgSIB shall be set to the default value for every outgoing ADJG whose parameter ADJGid equals 0 of every WCEL

• The value of DelayThresholdMin always has to be less than the value of DelayThreshold-Mid, unless DelayThresholdMax has value “HSUPA CC mechanism disabled”.

• The AMRWithEDCH parameter is valid only if AMRWithHSDSCH is enabled

• AMRwithEDCH is not allowed to set to enabled if special value ‘Not defined’ is set to the parameter RTWithHSPAFmcsIdentifier.

• Value of the parameter ThresholdMaxEDPDCHSR1920kbps must be higher than value of the parameter ThresholdMaxEDPDCHSR960kbps

• Multi CN cannot be run simultaneously with Flexible Iu

• When the Flexible Iu feature is activated, maximum 8 CN nodes can be configured as default CNs for routing

• HSDPA dynamic resource allocation cannot be disabled when HSDPA 14Mbps per user is enabled.

• Initial bitrate for HSDPA UL DCH for NRT with streaming must be bigger than or equal to minimum allowed bitrate for HSDPA UL DCH for NRT with streaming.

• If parameter HSPA QoS Enabled indicates that HSPA QoS is used for NRTs, or HSPA streaming is in use, HSDPA Dynamic Resource Allocation must be enabled.

• The value of FAST UE THRESHOLD must be greater than the value of FAST UE CANCEL.

• LCS Support for Anchoring can be enabled only when parameter LCS Functionality is enabled

• LCS Support for Anchoring can be enabled only when Operational Mode of LCS is RNC Centric Mode

• PLMN ID defined in GlobalCNID of IU item must be found in IU operator list.

46 DN70227178Issue 2-1


Id:0900d805806dc6ac

Appendix

• PLMNID defined in IU operator list should be unique.

• Priorities for streaming RABs must be bigger than priority for interactive signaling RABs.

• Priority for interactive signaling RABs must be bigger than RT over NRT priority thresholds if RT over NRT is used for that specific ARP category.

• Priority for interactive signaling RABs must be bigger than priorities for other interactive and backgroud RABs.

• Priorities with HSPA NBR at uplink direction must form continuous block of priorities used for NRTs.

• Priorities with HSPA NBR at downlink direction must form continuous block of priorities used for NRTs.

RNC - CBCList

• If RAN sharing is disabled then only one CBCItem can be defined.

• RNC - CBCList - CBCItem - CBCPLMNList - CBCPLMNId (CBC PLMN id) must be unique in the whole CBCList

• If CBC is defined, at least one IP address must be defined

• If service Area Broadcast option is not bought , CBC can't be defined

• RAN sharing and IMSI HO not supported, only 1 PLMN id allowed for the only CBC

• PLMN id defined for the CBC must be found in IU list

• It's not allowed to remove the CBC item or remove PLMN id from the CBC item if WCEL(s) with 3 SCCPCH (SAB activated) mapped (same PLMN id) to it

IMSI based Handover feature

• It's not allowed to remove the CBC item or remove PLMN id from the CBC item if WCEL(s) with 3 SCCPCH (SAB activated) mapped (same PLMN id) to it

• RNC - DefaultAuthorisedNetworkId (Identifier of the Default Authorised Network) has to point to existing WANE object if the value is other than 0

HSDPA feature:

• The value of parameter HSDPAMinAllowedBitrateUl must be lower than or equal to param-eter HSDPAInitialBitrateUl

• If parameter HSDPADynamicResourceAllocation is modified, all HSDPA wcels has to be locked

• If HSDPADynamicResourceAllocation change to enable, the rule ptx_target >= ptx_target_ps_max >= ptx_target_ps_min should be matched in all hsdpa WCELs

• If HSDPAServCellWindow is modified, FMCS- EDCHRemEcNoOffset cannot get value which is 0.5dB~1.5dB lower than HSDPAServCellWindow.

• If HSDPA16KBPSReturnChannel is off, 16 kbps value is not allowed for following parame-ters: HSDPAminAllowedBitrateUL and HSDPAinitialBitrateUL

• HSDPAChaTypeSwitchWindow should have smaller value than value used in HSDPASer-vCellWindow

DN70227178Issue 2-1

47


Id:0900d805806dc6ac

IU Create/ Modify

(All the checking rules apply to both IUCS and IUPS, if it doesn’t specify IUCS and IUPS)

• IU - GlobalCNId (Global CN Id) must be unique within all IU

• IU - GlobalCNId (Global CN Id) modification is prohibited

• If RAN sharing is not enabled then the same IU - GlobalCNId - PLMNid - MNC (Mobile Network Code) must be defined for each Iu

• If RAN sharing feature is enabled, Flex IU is disabled for one operator's some CN domain (CS or PS), and MCN feature disabled, then same IU - GlobalCNId - PLMNid - MNC (Mobile Network Code) cannot be defined for the operator's the CN domain

• if MCN and RAN sharing options OFF, and IuFlex not in use,only one IU of each domain type is allowed

• if IUCS doesn't exists, user cannot define IUPS core

• if primary plmn_id is same, the secondary plmn list definitions must be same

• Primary PLMNid cannot be same as one of the secondary PLMNid

• Modify any items of secondary plmn list is denied if WCEL(s) mapped to it

• NRIminforCSCN cannot be greater than NRImaxforCSCN, NRIminforPSCN cannot be greater than NRImaxforPSCN

• At least one of the min/max pairs (NRIMaxforCSCN/NRIMinforCSCN, NRIMaxforPSCN/ NRIMinforPSCN) cannot have 1023 (not used) value for all configured CN nodes of one operator whose corresponding NRI length is set to non-zero

• If FLexible IU feature is deactivated, maximum number of defined CNs is 8

• Subnet_id cannot be defined if no IP addresses are given.

• The IPQM must exist if it is defined in IU

IU delete • IU can not be removed if it is mapped to the WCEL(s)

IUR Create/ Modify

• IURNRncId (Neighbour RNC identifier) and IUR - NeighbouringPLMNidList - Neighbouring-PLMNid (Neighbouring PLMN identity) must be unique within all IUR

• Inside each IUR, NeighbouringPLMNid (Neighbouring PLMN identity) must be unique.

• At least one NeighbouringPLMNid must be defined for IUR

• IUR - NRncSignPointCode (Signalling point code of neighbour RNC) and IUR - NRncNet-workInd (Network indicator of neighbour RNC) must be unique within all IUR in the DB

48 DN70227178Issue 2-1


Id:0900d805806dc6ac

Appendix

WBTS Create/ Modify

• Maximum amount of WBTS objects is 2800 for RNC2600. As for RNC450/196, the maximum is defaultly 384, and 512 or 600 if the corresponding options are bought.

• WBTSId must be unique under RNC

• SharedHSDPAFlowControlAllocation should be greater than or equal to the value of the SharedHSDPAallocation in the same WBTS.

• WBTS - ATMInterfaceID (ATM interface identifier) / VPI / VCI and WBTS - COCOId (Con-nection Configuration Identifier) references have to be unique within all WBTS objects

• WBTS - IPBasedRouteIdIub reference have to be unique within all WBTS objects

• If the referred COCO object exists, then WBTS - COCOId and WBTS - ATMInterfaceID / VPI / VCI have to be the same as given for COCO if they are defined.

• WBTS - ATMInterfaceID (ATM interface identifier) / VPI / VCI and WBTS - COCOId (Con-nection Configuration Identifier) modification requires WCEL object locking when the COCO is related to the WBTS

• DedicatedMeasReportPeriod or RRMULDCHActivityFactor or IubTransportMedia or Dedi-MeasRepPeriodCSdata or DediMeasRepPeriodPSdata requires WCEL object locking to all WCELS related to WBTS if WBTS is connected with COCO or IPNB

• IPNBId or IPBasedRouteIdIub requires WCEL object locking to all WCELS related to WBTS, if WBTS is connected with IPNB

• If IubTransportMedia is not ATM and WBTS is connected with COCO, IPBasedRouteIdIub modification requires WCEL object locking.

• MaxNumberEDCHLCG must be higher than value of parameter WCEL-NumberED-CHReservedSHOBranchAdditions

• NBAPCommMode is unmodifiable.

• Window size for interference measurement to start LHOs has to be equal to or greater than Radio Resource Indication Period in WBTS cell.

• When IubTransportMedia is not ATM, IP Subnet id must be defined.

WBTS delete • WBTS cannot be deleted if some WCELs are still under it.

WCEL Create/ Modify

• Maximum amount of WCEL objects in the RNW database is 2800.

• If NBAPCommMode (NBAP Communication Mode) mismatchs with NEtype (Ne-type), WCEL Creation and modification are not allowed.

• If AMRDirReCell (Usage of Directed Retry of AMR call Inter-system Handover) is enabled and the target cell of directed retry of AMR call is the cell whose ADJGid (Inter-system adja-cency identifier) has value zero, then AdjgSIB(Include in System Information ) shall be default (yes)

• Not modifiable WCEL parameters: CId (Cell identifier), LcrId (Local cell resource identifier), UARFCN (UTRA Absolute Radio Frequency Channel Number), WCELGlobalCNid (Global CN Id)

DN70227178Issue 2-1

49


Id:0900d805806dc6ac

• WCEL object locking required before the modification: NbrOfSCCPCHs (Number of SCCPCHs), , CellRange (if BTS with 3GPP interface is involved), PtxCellMax (Cell maximum transmission power), EbNoSetIdentifier, AICHTraTime, PI_amount, PRACH-ScramblingCode, RACHCapacity, PowerOffsetSCCPCHTFCIIf NBAPCommMode is NB/RSXXX, Following parameters requeste wcel object locking before the modification.Cell Reconfig Parameters: • PtxPrimarySCH • PtxSecSCH • PtxPrimaryCPICH • PtxPrimaryCCPCHPRACH parameters:: • AllowedPreambleSignatures • AllowedRACHSubChannels • PtxAICHSCCPCH parameters: • ToAWS_CCH • ToAWE_CCH • PtxSCCPCH1, PtxSCCPCH2, PtxSCCPCH3 • PtxPICH

• WCEL - UARFCN (UTRA Absolute Radio Frequency Channel Number) and WCEL PriScr-Code (Primary downlink scrambling code) pair must be unique under WBTS

• WCEL - CId (Cell identifier) must be unique under RNC

• WCEL - WCELGlobalCNid (Global CN Id) has to be found in RNC - IuList

• At least WCEL - WCELGlobalCNid - WCELCSCNId (CS Core Network Identity) must be given with WCEL - WCELGlobalCNid - WCELPLMNid (PLMN identity)

• WCEL and Intra-Frequency neighbouring WCEL must have different scrambling code and the same frequency

• WCEL and additional intra-frequency adjacency WCEL must have different scrambling code and the same frequency

• WCEL and Inter-frequency neighbouring WCEL must have same frequency

• Value of FachLoadMarginCCH must be less than value of FachLoadThresholdCCH if both are not 0

• Value of RachLoadMarginCCH must be less than value of RachLoadThresholdCCH if both are not 0

• InitialBitRateDL should not be greater than the value of MaxBitRateDLPSNRT.

• InitialBitRateDL should not be smaller than the value of MinAllowedBitRateDL.

• InitialBitRateUL should not be greater than the value of MaxBitRateULPSNRT.

• InitialBitRateUL should not be smaller than the value of MinAllowedBitRateUL.

• MaxBitRateDLPSNRT should not be smaller than value of MinAllowedBitRateDL

• MaxBitRateULPSNRT should not be smaller than value of MinAllowedBitRateUL

• MinAllowedBitRateDL should not be greater than value of MaxBitRateDLPSNRT

• MinAllowedBitRateUL should not be greater than value of MaxBitRateULPSNRT

• RACH_Tx_NB01max parameter value must always be higher than the value of the RACH_Tx_NB01min parameter

• SinterSearchConn should not be greater than value of SintraSearchConn

• SinterSearchConn should not be smaller than SSearchRatConn

50 DN70227178Issue 2-1


Id:0900d805806dc6ac

Appendix

• If the maximum cell range (CellRange) is greater than 10 km, AICH Transmission Timing is 1 and Rx Diversity Indicator is 1. If AICH Transmission Timing has value 0 or four antennas are used (Rx Diversity Indicator = 2), the maximum value can be 10 km.

• WCEL - DirectedRRCEnabled and WCEL - DirectedRRCForHSDPALayerEnabled cannot be enabled simultaneously If RNC - DirectedRRCForHSDPALayerEnhanc is disabled

• SectorID: Two (or more) cells can belong to the same sector if DirectedRRCForHSDPALay-erEnhanc is enabled and the following cell parameters are identical for the cells in question. (Note that the RNC is not able to check whether the antenna beams of the cells are directed equally): . Transmission power of primary CPICH (CPICHtxPwr) • Target for total transmitted power (PtxTarget) • Offset for transmitted power (PtxOffset) • Target for received power (PrxTarget) • Offset for received power (PrxOffset) • Mobile Country Code (MCC) • Mobile Network Code (MNC)

• WCEL object can not be created or modified with a relation to CMOB that does not exist. Relation from WCEL to CMOB is defined with parameters 'RNARGroupId', 'CSGroupId' and 'PSGroupId'.

• WCEL parameter RNARGroupId can contain only either ‘not defined’ value or identifier for CMOB whose type is ‘RNAR’

• WCEL parameter CSGroupId can contain only either ‘not defined’ value or identifier for CMOB whose type is ‘CS-DSAC’

• WCEL parameter PSGroupId can contain only either ‘not defined’ value or identifier for CMOB whose type is ‘PS-DSAC’

• If ADJG is defined, RtFmcgIdentifier (RT FMCG Identifier) should be defined.

• If RtFmcgIdentifier (RT FMCG Identifier) is defined, NrtFmcgIdentifier (NRT FMCG Identi-fier) should be defined.

• If NrtFmcgIdentifier (NRT FMCG Identifier) is defined, RtFmcgIdentifier (RT FMCG Identi-fier) should be defined.

• If ADJI is defined, RtFmciIdentifier (RT FMCI Identifier) should be defined.

• If RtFmciIdentifier (RT FMCI Identifier) is defined, NrtFmciIdentifier (NRT FMCI Identifier) should be defined

• If NrtFmciIdentifier (NRT FMCI Identifier) is defined, RtFmciIdentifier (RT FMCI Identifier) should be defined.

• RtFmcsIdentifier and RtFmcsIdentifier (RT/NRT FMCS Identifier) should be defined.

• WCEL - EbNoSetIdentifier (Eb/No parameter set identifier) identifies the WRAB object

• LHOWinSizeONInterference: the value of it is not 0. If NBAPCommMode is NB/RSXXX, it should be equal to or greater than PrxTotalReportPeriod and PtxTotalReportPeriod. Other-wise, it must be equal to or greater than RRIndPeriod

• AMRUnderTxTotal shall be smaller than AMRTargetTxTotal

• AMRTargetTXtotal shall be smaller than AMROverTxtotal

• AMRUnderTxNC shall be smaller than AMRTargetTxNC

• AMRTargetTxNC shall be smaller than AMROverTxNC

• AMRUnderTxNonHSPA shall be smaller than AMRTargetTxNonHSPA

• AMRTargetTxNonHSPA shall be smaller than AMROverTxNonHSPA

• AMRUnderSC shall be smaller than AMRTargetSC

• AMRTargetSC shall be smaller than AMROverSC

• AMRUnderTransmission shall be smaller than AMRTargetTransmission

DN70227178Issue 2-1

51


Id:0900d805806dc6ac

• AMRTargetTransmission shall be smaller than AMROverTransmission

Service Area Broadcast feature:

• If WCEL - NbrOfSCCPCHs (Number of SCCPCHs) is 3 (SAB feature active): • The following SAB related parameters must be given: WCEL • SACB (Service Area Code for SAB), CTCHCapaHighPri, KforCTCH, NforCTCH • RNC - CBCList - CBCItem (CBC Item) have to be defined

• WCEL - SACB (Service Area Code for SAB) must be unique in RNC

HSDPA feature:

• If HSDPA enabled parameter value is enabled: • Hsdpa_fmcs_id has to be defined • RT_hsdpa_fmcs_id must be defined If AMRWithHSDSCH is enabled. • Obligatory parameters must be defined: ptx_target_hsdpa, ptx_max_hsdpa, and

ptx_offset_hsdpa . No outgoing ADJS cells hsdpa_hops_id value is hops_id_t_not_def

• No outgoing ADJS cells rt_hsdpa_hops_id value is hops_id_t_not_def_c if AMRWith-HSDSCH is enabled

• No outgoing ADJD cells hsdpa_hops_id value is hops_id_t_not_de • No outgoing ADJD cells rt_hsdpa_hops_id value is hops_id_t_not_def_c if AMRWith-

HSDSCH is enabled. . If ADJI is defined, hsdpa_fmci_id value fmci_id_t_not_def is not allowed

• If ADJI is defined and AMRWithHSDSCH is enabled, rt_hsdpa_fmci_id value fmci_id_t_not_def_c is not allowed

• If ADJG is defined, hsdpa_fmcg_id value fmcg_id_t_not_def is not allowed • If ADJG is defined and AMRWithHSDSCH is enabled, rt_hsdpa_fmcg_id value

fmcg_id_t_not_def_c is not allowed • If the parameter Directed RRC connection setup enabled = 2, no more than 2 of the

same SectorIDs per BTS can exist in the cells where the parameter has this value. • Dynamic target threshold PtxTargetPS is applicable only if HSDPA Dynamic Resource

Allocation is enabled and HSDPA is enabled. • PtxTargetPSMax must be lower than or equal to the PtxTarget. • PtxTargetPSMax must be greater than or equal to the PtxTargetPSMin. . PS CN

ID has to be defined • HSDPA option must be supported

• Parameters that require object locking in modification: • HSDPAEnabled • PtxMaxHSDPA • HSPDSCHCodeSet • MaxNbrOfHSSCCHCodes

52 DN70227178Issue 2-1


Id:0900d805806dc6ac

Appendix

• If HSUPA enabled parameter value is enabled: • HSDPAEnbale must be enabled • HSUPAXUSERSENABLED must be enabled • HSDPADynamicResourceAllocation must be enabled • Hsdpa_fmcs_id has to be defined • Rt_hsdpa_fmcs_id must to be defined if AMRWithHSDSCH is enabled, • PrxLoadMarginEDCH must be lower than or equal to the value of the PrxMaxTarget-

BTS. • PrxTargetPSMax must be lower than or equal to the PrxTarget. • PrxTargetPSMax must be greater than or equal to the PrxTargetPSMin. • PrxLoadMarginDCH must be lower than or equal to the value of the PrxLoadMargin-

MaxDCH. • MaxNumberEDCHCell must be higher than value of NumberEDCHReservedSHO-

BranchAdditions. • NumberEDCHReservedSHOBranchAdditions must be lower than value of HSUPAX-

UsersEnabled. • If HSUPA is activated, it must be activated in all cells that use the same frequency

(UARFCN) in the same BTS. • If HSUPA is deactivated, it must be deactivated in all cells that use the same frequency

(UARFCN) in the same BTS.

• Parameters that require object locking in modification: • HSUPAEnabled • PrxLoadMarginEDCH • SIRDPCCHOffsetEDPCH • MaxTotalUplinkSymbolRate • TargetNSEDCHToTotalEDCHPR

HSPA Multi NRT RABs feature:

• If WCEL - HspaMultiNrtRabSupport (HSPA multi NRT RAB Support) is enabled: • HSDPAenabled (HSDPA enabled ) must be enabled • HSDPA option supported • HSPA Multi NRT RABs option supportedHSDPA 64 User feature:

• If WCEL - HSDPA64UsersEnabled (HSDPA 64 users enabled ) is enabled: • HSDPAenabled (HSDPA enabled ) must be enabled • HSDPA option supported • HSDPA 64 Users option supported

• Parameters that require object locking in modification: • HSDPA64UsersEnabled QoS Aware HSPA Scheduling feature:

• If the value of HSPAQoSEnabled is 1(QoS prioritization for HSPA NRT connections): • HSDPAEnbale must be enabled • HSDPADynamicResourceAllocation must be enabled

• Parameters that require object locking in modification: • HSPAQoSEnabledStreaming QoS for HSPA feature:

• If the value of HSPAQoSEnabled is 2(HSPA streaming is in use): • HSDPAEnbale must be enabled • HSDPADynamicResourceAllocation must be enabled • NBAPCommmode should not has value 1 (NB/RSxxx)

• Parameters that require object locking in modification: • HSPAQoSEnabled

DN70227178Issue 2-1

53


Id:0900d805806dc6ac

WCEL Unlock • If NBAPCommMode (NBAP Communication Mode) mismatchs with NEtype (Ne-type), WCEL Unlock is not allowed.

• If HSDPAEnabled is enabled, HSDPA licence state should be ‘ON’

• If HSDPADynamicResourceAllocation is enabled, HSDPA and HSDPA Dynamic Resource Allocation licence state should be ‘ON’

• If max code value in HSPDSCHCodeSet: • Between 5 and 10, HSDPA 15 Codes or HSDPA 10 Codes licence state should be ‘ON’ • Bigger than 10, HSDPA 15 Codes licence state should be ‘ON’

• If HSUPAEnabled is enabled: • The HSDPA licence state should be ‘ON’ • The HSDPA Dynamic Resource Allocation licence state should be ‘ON’ • The HSUPAXUsersEnabled related licence HSUPA X Users licence state should be

‘ON’ • . The AAL2UPUsage on the connected COCO should be HSUPA or HSPA type

• If the value of HSPAQoSEnabled is 1(QoS prioritization for HSPA NRT connections): • The HSDPA licence state should be ‘ON’ • The HSDPA Dynamic Resource Allocation licence state should be ‘ON’ • The QoS Aware HSPA Scheduling licence should be ‘ON’

• If the value of HSPAQoSEnabled is 2(HSPA streaming is in use): • The HSDPA licence state should be ‘ON’ • The HSDPA Dynamic Resource Allocation licence state should be ‘ON’ • The QoS Aware HSPA Scheduling licence state should be ‘ON’ • The HSPA with Streaming QoS Support licence state should be ‘ON’

• If the value of MaxNbrOfHSSCCHCodes is biggen than 1 • The HSDPA licence state should be ‘ON’ • The HSDPA Dynamic Resource Allocation licence state should be ‘ON’ • The HSDPA Code Multiplexing licence state should be ‘ON’ • The HSDPA 15 Codes or HSDPA 10 Codes licence state should be ‘ON’

• If the value of CellRange • . Between 20Km and 35Km, Extended cell 35km or Extended cell 60km or Extended

cell 180km licence state should be ‘ON’ • Between 35Km and 60Km, Extended cell 60km or Extended cell 180km licence state

should be ‘ON’ • Bigger than 60Km, Extended cell 180km licence state should be ‘ON’

• If the value of HSDPA64UsersEnabled is enabled: • The HSDPA licence state should be ‘ON’ • The HSDPA 64 Users per Cell licence state should be ‘ON’

• If the value of MaxTotalUplinkSymbolRate is 2 (3840 kbps, 2*SF2) • At lease one HSUPA X Users licence state should be ‘ON’ • The HSDPA 2.0 Mbps licence state should be ‘ON’

• If HSUPA is activated, it must be activated in all cells that use the same frequency (UARFCN) in the same BTS.

• If HSUPA is deactivated, it must be deactivated in all cells that use the same frequency (UARFCN) in the same BTS.

54 DN70227178Issue 2-1


Id:0900d805806dc6ac

Appendix

ADJS Create/ Modify

• The maximum amount of ADJS under the WCEL is 31

• ADJS – RtHopsIdentifier and NrtHopsIdentifier have to refer to the existing HOPS object (Intra-frequency Handover Path)

• The scrambling code must be different between the ADJS and the source WCEL

• The same scrambling code is not allowed for other ADJS of the source WCEL

• The same scrambling code is not allowed for any ADJD of the source WCEL

• ADJS has to have unique target WCEL among ADJSs under the source WCEL

• ADJS has to have different target WCEL from any ADJD under the source WCEL

• The following parameters have to be the same in ADJS and the target WCEL: AdjsLAC, AdjsRAC, AdjsScrCode, AdjsTxPwrRACH and AdjsCPICHTxPwr

• UARFCN of the source and target WCEL must be the same

• The parameters related to the target WCELexcept AdjsRNCid (AdjsMCC, AdjsMNCLength, AdjsMNC, and AdjsCI) can not be modified when the target cell is under the same RNC

• When the source WCEL is HSDPA enabled, HSDPAHopsIdentifier must be defined.

• When the source WCEL is HSDPA enabled and HSDPA with AMR is enabled in the RNC, RTWithHSDPAHopsIdentifier must be defined

• If HSDPAHopsIdentifier is defined, the referred HOPS should exist

• If RTWithHSDPAHopsIdentifier is defined, the referred HOPS should exist

ADJD Create/ Modify

• Option 'Detected Set Reporting Based SHO' must be supported.

• The maximum amount of ADJD under the WCEL is 32

• AdjdRTHopsId and AdjdNRTHopsId have to refer to the existing HOPS object (Intra-fre-quency Handover Path)

• The scrambling code must be different between the ADJD and the source WCEL

• The same scrambling code is not allowed for other ADJD of the source WCEL

• The same scrambling code is not allowed for any ADJS of the source WCEL

• ADJD has to have unique target WCEL among ADJDs under the source WCEL

• ADJD has to have different target WCEL from any ADJS under the source WCEL

• The following parameters have to be the same in ADJD and the target WCEL: AdjdMCC, AdjdMNCLength, AdjdMNC, AdjdLAC, AdjdRAC, AdjdScrCode, AdjdCPICHTxPwr

• UARFCN of the source and target WCEL must be the same

• The parameters related to the target WCEL except AdjdRNCId (AdjdMCC, AdjdMNC-Length, AdjdMNC, and AdjdCI) can not be modified when the target cell is under the same RNC

• When the source WCEL is HSDPA enabled, AdjdHSDPAHopsId must be defined

• When the source WCEL is HSDPA enabled and HSDPA with AMR is enabled in the RNC, AdjdRTWithHSDPAHopsIdmust be defined

• If AdjdHSDPAHopsId is defined, the referred HOPS should exist

• If AdjdRTWithHSDPAHopsId is defined, the referred HOPS should exist

DN70227178Issue 2-1

55


Id:0900d805806dc6ac

ADJI Create/ Modify

• The maximum amount of ADJI under the WCEL is 48

• The maximum number of inter-frequency neighbour cells that can be included in the System Information is 32.

• ADJI – RtHopiIdentifier and NrtHopiIdentifier have to refer to the existing HOPI object (Inter-system Handover Path)

• UARFCN of the source WCEL and ADJI must be different (WCEL – UARFCN, ADJI - Adji-UARFCN)

• The scrambling code and UARFCN combination have to be unique within the ADJI objects under the same source WCEL

• ADJI with the same target WCEL must not exist

• The following parameters have to be the same in ADJI and target WCEL: AdjiLAC, AdjiRAC, AdjiScrCode, AdjiTxPwrRACH, AdjiTxPwrDPCH, AdjiCPICHTxPwr and AdjiUAR-FCN

• The parameters related to the target cell except AdjiRNCid (AdjiMCC, AdjiMNCLength, AdjiMNC, and AdjiCI) can not be modified when the target cell is under the own RNC

• UARFCN is not allowed to be modified when target cell is under own RNC

• RT+NRT FMCI must be defined for the source WCEL

• When the source WCEL is HSDPA enabled,, the source cell’s HSDPAFmciIdentifier must be defined

• When the source WCEL is HSDPA enabled and HSDPA with AMR is enabled in the RNC, the source cell’s RTWithHSDPAFmciIdentifier must be defined

ADJG Create/ Modify

• The maximum amount of ADJG under the WCEL is 32

• BCCH and BSIC must be different between separate ADJG definition

• ADJG - BandIndicator is not modifiable

• ADJG with the same target WCEL must not exist

• If ADJGId is 0 and parameter AMRDirReCell of the FMCG that the source WCEL points with RtFmcgIdentifier has value "enabled", AdjgSIB is not allowed to be 'no', i,e, the ADJG must be included in System Information.

• If the ADJG is GAN specific (BCCH and BSIC is same as RNC parameters GANetwAR-FCN, GANetwNCC and GANetwBCC), AdjgSIB must be 'no', i.e., GAN specific ADJG cannot be included in System Information.

• If option 'UTRAN - GAN interworking' is ON and option 'GSM ISHO' is OFF, only GAN specific ADJG can be configured.

• Normal ADJG (not GAN specific) – RtHopgIdentifier and NrtHopgIdentifier have to refer to the existing HOPG object (Inter-system Handover Path)

• As for normal ADJG (not GAN specific), RT+NRT FMCG must be defined for the source WCEL

• If AdjgBandIndicator has value ‘0’, the full GSM band range 0~1023 is allowed;if AdjgBand-Indicator has value ‘1’, only GSM1900 band range is allowed.

• When the ADJG is not GAN specific and the source WCEL is HSDPA enabled, the source cell’s HSDPAFmcgIdentifier must be defined

• When the ADJG is not GAN specific, the source WCEL is HSDPA enabled and HSDPA with AMR is enabled in the RNC, the source cell’s RTWithHSDPAFmcgIdentifier must be defined

• If WireLessPriorityService in RNC is enabled, and ADJGId is 0, AdjgSIB is not allowed to be 'no', i,e, the ADJG must be included in System Information.

56 DN70227178Issue 2-1


Id:0900d805806dc6ac

Appendix

FMCS Create/ Modify

• EDCHRemEcNoOffset should have at least 2 dB bigger value than defined inEDCHRe-mEcNoOffset to avoid frequent channel type switches between DCH and E-DCH.

• EDCHRemEcNoOffset cannot get value which is 0.5dB~1.5dB lower than value defined in HSDPAServCellWindow

• HHoRscpThreshold should be less than HHoRscpCancel

FMCI Create/ Modify

• The value of NcellSearchPeriod must be lower than the value of MaxMeasPeriod

FMCG Create/ Modify

• The value of NcellSearchPeriod must be lower than the value of MaxMeasPeriod

FMCG Modify • If AMRDirReCell is modified to "enabled", for all the WCELs using the FMCG with RtFmcgI-dentifier, their outgoing GSM neighbor cell definition for ADJGId 0 must have not 'no' AdjgSIB parameter.

FMC(S/I/G) Delete • FMC(S/I/G) object cannot be referred from any WCEL object

HOP(S/I/G) Delete • HOP(S/I/G) object cannot be referred from any ADJ(S/I/G) object

WSMLC Create/ Modify

• The LCSInterfaceOption parameter can be changed to iupc_c only if either NW_AGPS_SUPPORT or AGPS_SUPPORT option is enabled and IUPC_INTERFACE option is enabled.

• NW_AGPS_SUPPORT can be enabled only if LCSInterfaceOption is iupc_c.

• The NetworkIndicatorForSAS/SignallingPointCodeOfSAS parameters can be changed to valid value only if either NW_AGPS_SUPPORT or AGPS_SUPPORT option is enabled and sas_if_option parameter is set to iupc_c

• The LCSInterfaceOption parameter can be changed to adif_c only if either NW_AGPS_SUPPORT or AGPS_SUPPORT option is enabled and ADIF_INTERFACE option is enabled

• PreferredAGPSMethod can be changed to UE base method only if UEBasedAGPS is enabled.

• PreferredAGPSMethod can be changed to NW Based Method only if NetworkBasedAGPS is enabled.

• Parameter OperationalMode can select SAS Centric mode only when LCSInterfaceOption has value Iupc

• Parameter OperationalMode can’t select SAS Centric mode when LCS Support for Anchor-ing has value enabled

• The priority of Shape is unique under CIRTTEmergencyShapeList and CIRTTShapeList separately if the value is not 0 (disabled)

• At least one shape priority is valid ( not 0) under CIRTTEmergencyShapeList and CIRTTShapeList separately

• the selected shapes in the list (CIRTTShapeList, CIRTTEmergencyShapeList) have priori-ties in descending sequence without gaps,

WSMLC Delete • WLCSE object should not exist

WLCSE Create • WSMLC object must be found in RNC

• Max amount of WLCSE objects in RNW database is 6000

WANE Delete • WANE object cannot be deleted if it is referred from WSG

• WANE object cannot be deleted if RNC - DefaultAuthorisedNetworkId refers to it

WSG Create/ Modify

• WSG object can be created and modified when the related WANE object is found in the database or if WANE id is default

DN70227178Issue 2-1

57


Id:0900d805806dc6ac

CMOB Create • No more than 2 CMOB objects whose parameter 'RestrictionGroupType' is 'RNAR' can be created.

• No more than 4 CMOB objects whose parameter 'RestrictionGroupType' is 'CS-DSAC' can be created.

• No more than 4 CMOB objects whose parameter 'RestrictionGroupType' is 'PS-DSAC' can be created.

• Forced CMOB can't be created by user.

CMOB Modify • CMOB parameter ‘RestrictionGroupType’ can not be changed

CMOB Delete • CMOB can not be deleted if there are relations to it from WCEL objects

• forced CMOB can't be deleted by user

WRAB modify • WRAB can not be modified if there are some unlocked WCELs related

WRAB delete • WRAB can not be deleted if there is association with some WCELs

IPQM delete • IPQM can not be deleted if there are relations to it from IU objects

TQM delete • TQM can not be deleted if there are relations to it from WBTS objects

system library

Documents